MTO (Make-To-Order) cost booking

Query:

IN MTO scenario if a sales order costing is done in current month then the cost is debited to a sales order and credited to a cost center and If delivery (posting of goods) and the revenue happen for same order in the subsequent month. How will u ensure that there is no mismatch between costs in CO and FI

Answer :

To ensure that there is no mismatch, set up the RA (result analysis and settlement). Assign it to your requirement type (for automatic determination only). If there is a change in period, the costs will be treated as WIP.

Contributed by: Sameer Dumbre

How to maintain number range for Customer account group?

Assignment of customer number range is two step process. We have to be sure if the number range will be Internal or External, this has to be configured in system.
Prerequiste - Account group is already created.

Tcode - OVZC.
Click on modifiable mode of number range and create the number range for an object may be like 'AA' 10000- 20000.
T-code - OBAR.
Assign the object - AA to account group

How to maintain number range?

Number ranges assign numbers to individual commercial object database records (e.g. purchase document, addresses, etc.).

A number range object must have been defined for the commercial object in question to enable number ranges to be used. Number ranges can then be determined for the number range object.The numbers assigned by the number range create a unique key for the database records in the system.

A number can be external or internal. If number range is set to external number for the objct will be maintained externally and in case of internal number range the number range will be proposed by the system.

I have created a quick guide to maintain number range for excise invoice.

Use T-code - SNRO

Enter object - J_1IEXCLOC

Click on number range

Enter series group.

Click on midify mode of Number range and then add a new line to number range and save.

Make sure you have assigned this number range to the object in my case it will be excise invoice.

Create Sets for DIP profile.

Create Sets required to book cost via DIP (Dynamic Item Processor) profile.

The dynamic item processor (DIP) is a tool that the system uses to group data (for example, line items that are produced when posting goods movements, completion confirmations or surcharges) in dynamic items during resource-related billing and quotation creation. The dynamic item processor profile (DIP profile) controls amongst other things how the system groups the data in dynamic items.

Use
You can use the DIP profile for the following purposes:

Quotation Creation
- Service quotations for the component Service Management (SM)
- Quotation creation for the component Project System (PS)
Billing
- Resource-related billing
- Flat-rate billing with listing of expenses (source SAP help).

I have taken example of Cost element for maintain sets but these steps are applicable for practically every objects where sets are required to be maintained.

Prerequisite :- You havve already created a DIP profile and assigned.
to deteremine cost element you should have maintained structuring checkbox for Object number in ODP1 (configuration of DIP profile) under Characterstics.

Enter T-code - GS02 and enter the set name. I have used set as SET1 as an example. Enter table name -  AD01ATTR
Hit Enter

Input field name - KSTAR

Enter data, it can either be cost element range or individual cost element in each line.

These sets are assigned in Transaction code ODP1 under material determination - Criteria.

Job done so now when you run DP81 or DP90 only those cost element will be picked that is maintained in GS01.

How to search path of a transaction code in SAP

If you want to search SAP path of a transaction code enter T-code :- Search_sap_menu. A dialogue box is opened enter Transactio code (t-code) in dialogue box. System will give you all option of paths available.

LSMW manual for Data Migration

LSM Workbench

The LSM Workbench is an SAP-based tool that supports transferring data from non-SAP systems ("Legacy Systems") to SAP systems once or periodically. Furthermore, the LSM Workbench provides a recording function that allows generating a "data migration object" in an entry or change transaction.

Basic Principles of the LSM Workbench

The LSM Workbench was developed on the basis of the R/2-R/3 Migration Workbench that has been used many hundred times in the past and is still used presently.

The following concepts and techniques from the R/2-R/3 Migration Workbench were adopted:

Business objects instead of individual tables or field contents are migrated.

The conversion rules to be defined are flexible and can be customized in the frame of migration customizing to meet the actual situation in the project in the user system.

Preprogrammed conversion programs are not delivered. These programs are rather generated on the basis of the defined rules.

The LSM Workbench was developed on the basis of the following principles:

Most of the functions should reside in the SAP system. No collection of individual programs on different platforms.

The quality and consistence of the data imported into the SAP system should be more important than speed and performance of data migration.

Existing knowledge and coding should be used.

The developed "mapping" and rules should be reusable and thus be used repeatedly in projects.

On this basis, a concept was developed that is represented in the following chart:

Schematic Flow of Data Migration with the LSM Workbench

The main advantages of the LSM Workbench:

·         Part of the SAP system and thus independent of individual platforms

·         Creation of data migration objects on the basis of recorded transactions

·         Interface for data on fronted

·         Mass uploading of the Data to overcome the time factor of Data Entry



Process

1.     Transaction Code        LSMW

\


1.     On the initial screen, you can create new project, subprojects and objects via Edit -> Create new entry or using  (Create Entry) Button.

• Project: An ID with a maximum of 10 characters to name your data transfer project. If you want to transfer data from   several legacy systems, you may create a project e.g. for every legacy system.
• Subproject: An ID with a maximum of 10 characters that is used as further structuring attribute.
• Object: An ID with a maximum of 10 characters to name the business object. 

2.     Now Create Project, Subproject and Object with help of  (Create Entry) Button.

Press “Continue”  button.

 

Press “Continue”  button.

After Creation of project, Subproject and Object click “Continue” button.













These are the sequence of steps we have to follow to create an Object.

Basic Principles of the LSM Workbench

The LSM Workbench was developed on the basis of the R/2-R/3 Migration Workbench that has been used many hundred times in the past and is still used presently.

The following concepts and techniques from the R/2-R/3 Migration Workbench were adopted:

Business objects instead of individual tables or field contents are migrated.

The conversion rules to be defined are flexible and can be customized in the frame of migration customizing to meet the actual situation in the project in the user system.

Preprogrammed conversion programs are not delivered. These programs are rather generated on the basis of the defined rules.

The LSM Workbench was developed on the basis of the following principles:

Most of the functions should reside in the SAP system. No collection of individual programs on different platforms.

The quality and consistence of the data imported into the SAP system should be more important than speed and performance of data migration.

Existing knowledge and coding should be used.

The developed "mapping" and rules should be reusable and thus be used repeatedly in projects.

On this basis, a concept was developed that is represented in the following chart:

Schematic Flow of Data Migration with the LSM Workbench

4.      Maintain Object Attributes

           After executing first step the screen appears as

Here Select Batch input Recording button. Don’t select others.

5.     Recording of a transaction appears as

Click on Create button to create recording.

After that it will ask for Transaction Code to which we are developing the LSMW process.

Material Creation

Create the material using the T.Code MM01 using the all required values.

Main Points you have to taken care while creation the Recording

·         Do not mouse while Scrolling the windows

·         While recording any data into SAP field you have to enter once manually, don’t use copy and paste functions.

·         Type the values in the field even through selected from pull-down

·         If any error occurred during the creation of material start the process from beginning and do not save present record.

·         Enter all the required fields before going to next view in recording

·         To Choose any View or any Row Press F9 through Keyboard.

6.     After the Recording of the Data the Recording information appears like this and click “Default All” button

After that click Save and made excel file for recorded fields.

For Extracting excel file from SAP system follow the below steps

Click on Systemà Listà Saveà Local file.

After that download the file into Spreadsheet or Excel.

Prepare Excel sheet as per Recording.

While preparing excel file the following steps need to follow:

·         While recording whatever fields entered by us kept those fields only in excel other fields remove from excel including repeated fields also.

·         Fields sequences are very important and avoid duplications.

·         Convert Excel into Text (Tab delimited) file.

After excel sheet preparation, come back to SAP screen and click on Back button.

After the above step Click again BACK button, it will goes to next screen and again Click SAVE and BACK button.

7.     Maintain Source Structures

After that Indicator automatically goes to the next option and click “execute”. Create new Structure by clicking “Create a Structure”.

After source structure creation “Save” and “Back”.

                                       

8.     Maintain Source Fields

Execute this operation by clicking “Continue” Button. The Screen appears like this

Click “Copy Fields” to add our fields to the structure. A window appears in that select appropriate option.

It asks for the file in which Field names are stored as First line of Data File.

After that all the fields copies in to source structure.  Appears as

Note: Field length it will create as the recorded information field length. For that you have changed it into standard width.

Double Click on the Field name and change the Length of Field.

Make the all the necessary changes with field length. Click “Save” and “Back”.

9.     Maintain Structure Relations

Execute this step by clicking “Continue” and then click   “Change”.

After that click “Save” and “Back”.

10.     Maintain Field Mapping and Conversion Rules

The structural relationships define the relationships between source and target structures.

In this process we are mapping the data fields to fields created in Recording Process of Recording process.

By Selecting “Extras->Auto-Field Mapping” the system automatically assigns the fields to predefined fields. If any of the fields are not mapped automatically we have to map it by manually.

Automatic Field Options

Manual Source Field Assignment

By selecting the source field a relation will be established and this field data assigned to SAP Field.

Assign constant values to the fields for which we are not providing the input through Data File by clicking “Constant” Button.

Click “SAVE” and “BACK”.

Note: Please check is all our providing fields data is properly assigned to the SAP fields or not.

11.     Maintain Fixed Values, Translations, User-Defined Routines

No need to do any operation on this process step. Just manually select next process step.

12.     Specify Files

In this process step, you have to specify the name and description of the file in which the information about Data to be uploaded in Tab Delimited format. The Screen will appear as.

Double click on “Legacy Data” and provide the Data file to upload as show in window with selected attributes.

After filing the proper information click “Enter”. Click “SAVE” and “BACK.

13.     Assign Files

In this process step, Select “Change” button and “SAVE” and “BACK”. No other operation required in this step.

1


4.      Read Data

In this process SAP system reads the data from the file, which we are provided as Data File in Assign File Process.

Click “Execute” button.

After that it will show the records in the Data and displays this report.

After that Come to “Process Step” by Clicking “BACK” button.

15.     Display Read Data

In this step system will provide view of the data we are uploading into SAP.

It will prompt for the displaying of all the record or some. By Clicking “Enter”, it displays all the records it reads.

16.      Convert Data

LSMW coverts all the data into SAP Field view. In this process step click “Execute” button and come back to “Process Steps” by clicking “BACK” button.

17.      Display Converted Data

In this process step, System converts the Field name into Description of Field name view for users to understand whether the Data is properly assigned or not.

After this Come back to “Process Steps” by clicking “BACK” button.

18.     Create Batch Input Session

In this step we are creating the batch input folder for executing of the uploading process Code

“Keep Batch Input Folder(s)?” Click “Execute” Button. Then it will create Batch input Session for execution of process. Then Click “Enter” it comes back to Process Steps.

19.     Run Batch Input Session

In this step we are executing the batch session we are created in previous step.

Select the Session we want to process and Click “Process” Button. A window will display and choose appropriate options.

Process Mode:

·         Process/Foreground – It will waits for confirmation at each field entry.

·         Display errors only – It will display only error

·         Background – Done in Background meanwhile we can do other work.

If the process executes successfully, it shows status as  else shows  error in uploading.

We can also check error log by Clicking “Log” button.

Note:  If any problem occurs in data uploading process related to Field sequnce or incorrect data in field, modify the file and continue the process steps from “Specify Files”.  

Note: If the error caused because of the Recording process then you have to again develop the recording.

     

3.     Next screen appears as