R/3 System

Accelerated Data Migration using LSMW

Exercises & solutions (FI documents)

Note: For reasons of time, it might not be possible to do all the exercises during the course. These exercises are intended as additional examples to be dealt with during the course as required. Participants can also use them to deepen their knowledge after the course.

Page 1 of 24 (Date: 28.07.13)

1

Unit: Definition of the Migration Object

In the following exercise FI documents are to be migrated to the R/3-system. In the first stage, you are going to define the migration object. 1.1 Define the migration object for the migration of FI documents 1.1.1 Call LSMW with transaction code LSMW

 Enter transaction code lsmw in the ok-code and press enter, the LSM Workbench initial screen appears; as LSMW is not part of standard R/3, it can not be started using the menu 1.1.2 Define the project – please use ProjectXX (XX = group number)

 On the LSMW initial screen, position the cursor in field project and click on icon  (create)  A dialog box appears  Enter name and description of your project  Choose Continue . The project is defined now 1.1.3 Define the subproject (for example: part 1)

 On the LSMW initial screen, position the cursor in field subproject and click on icon  (create) – if you defined a new project before, this step is done automatically  A dialog box appears  Enter name and description of your subproject  Choose Continue . The subproject is defined now 1.1.4 Define the migration object (for example: documents)

 On the LSMW initial screen, position the cursor in field object and click on icon  (create) – if you defined a new subproject before, this step is done automatically  A dialog box appears  Enter name and description of your object  Choose Continue . The object is defined now

Page 2 of 24 (Date: 28.07.13)

the list of steps is displayed  From the list of steps.13) .5 Maintain the attributes of the migration object – FI documents will be migrated with batch input program RFBIBL00 (object 0100.1. subproject and object  Press enter. A screen appears.1. choose Maintain attributes of migration object with double-click.07.  Change the mode from display mode to change mode  Set the radio button  to ‘standard batch input / direct input’  Enter object 0100 and method 0000  Save your entries  Page 3 of 24 (Date: 28. method 0000) in this exercise  Go to the LSMW initial screen  Type in project.

The structure is defined now  Save your entry 2. choose Maintain source structures.07. A screen appears.1 Define header structure DOC_HEADER (FI document header)  From the list of steps.1.1.  Save your entry  .1 Maintain source structures 2.13) . choose Maintain source structures. The structure is defined now.2 Define structure DOC_POSITION (FI document position) subordinated to structure DOC_HEADER  From the list of steps. set the radio button  to subordinated and choose continue   In the next popup. fill name and description of structure DOC_POSITION  Choose Continue  .2 Unit: Definition of the Legacy System (structures and fields) In the second step you make the source structures known to R/3 2. A screen appears.  Change the mode from display mode to change mode  Click on icon  to define a new structure  In the popup. fill name and description of structure DO_HEADER  Choose continue  .  Change the mode from display mode to change mode  Position the cursor on structure DOC_HEADER  Click on icon  (create) to define a new structure  In the first popup. 2.2 Maintain source fields Page 4 of 24 (Date: 28.

subproject ACCOUNTING. choose Maintain source fields. A screen appears where the already defined source structures (and fields) are displayed Page 5 of 24 (Date: 28. subproject ACCOUNTING. subproject. choose Maintain source fields.2. object and structure and choose continue   The fields for structure DOC_HEADER are copied now  Save the entries  2. object DOCUMENT1E.2. set the radio button  to ‘Copy from other object’ and choose continue   Fill in project. structure DOC_HEADER Fieldname DOCNUMBER DATE TYPE CURRENCY BKTXT Type C DDMY C C C Length 10 10 4 2 20 Description Document number Document date Document type Document currency Document text  From the list of steps.2.07. object DOCUMENT1E.3 Field ‘DOCNUMBER’ in structure DOC_HEADER will be used as selection parameter for upload and conversion of data later on.13) .2 Fields of DOC_POSITION (FI document position)  You can copy the fields from PROJECT00. structure DOC_POSITION Fieldname DOCNUMBER POSNUMBER POSTINGKEY ACCOUNT AMOUNT TEXT Type C C C C AMT1 C Length 10 2 4 10 15 6 Description Document number Position number Posting key Account number Amount in document currency Description of position  See above 2.2.1 Fields of DOC_HEADER (FI document header)  You can copy the fields from PROJECT00. A screen appears where the already defined source structures are displayed  Change the mode from display to change mode  Position the cursor on structure DOC_HEADER  Click on icon to copy the structure  In the popup. please set the flag in the field definition  From the list of steps.

in this case. Change mode from display mode to change mode  Double-click on field ‘DOCNUMBER’ in structure DOC_HEADER  Set the flag ‘selection parameter for read/convert data’  Choose continue  and save the entry 2.2. in the example the field ‘DOCNUMBER’ Page 6 of 24 (Date: 28.13) .4 Question to test your understanding: Does the field ‘Identifying field value’ has to be filled for one or more fields when data is stored in two files (one file per structure)?  No.5 Question to test your understanding: Which field(s) will be used for merging the files during upload?  For merging of the files. the value is needed to identify the structure of a record 2. when there is more than one source structure in one file. all fields with identical name are used.2. the field ‘Identifying field value’ only has to be filled.07.

 Position the cursor on the appropriate source structure and choose Continue .1 Establish the structure relationships between the source structures and the R/3 System: The data of DOC_HEADER is needed for structures BGR00 and BBKPF. Mapping will be shown after processing step “maintain fieldmapping and conversion rules” 3. You can have look on this to see which structures and fields of the source data have to be assigned to those of the R/3 System. Overview.  From the menu bar on the List of Steps screen. The system displays the structure relationships between both systems. BBKPF 3.  Change the mode from display mode to change mode  Position the cursor on the desired R/3 structure  Choose Create relationship (icon  ). A screen appears where the structures used in the R/3 System are displayed. choose Maintain structure relationships.2 Which of the structures are mandatory?  Check for the comment in maintenance of structure relationships  BGR00.2.3 Establish the field relationships between the source fields and the R/3 System fields Page 7 of 24 (Date: 28.3 Unit: Object Dependencies and Conversion Rules In this stage of migration.2. This displays an overview of the source structures and R/3 structures.  Save the entry  3.2 Define the object dependencies: 3. the data of DOC_POSITION is needed for structure BBSEG  From the selection list of steps.07.1 Use the migration object overview to carry out mapping on paper. 3.13) . A dialog box appears where the source structures are displayed. you define the way in which the fields are to be converted. choose Extras → Object.

Fill in the value 4.07.  From the list of steps. Position the cursor on the corresponding R/3 field 2.1. From the icon bar click on the button for constant 3. choose Maintain field mapping and conversion rules.  A screen appears  Change the mode from display mode to change mode  Constant: 1. Choose Field mapping  add source field (icon  ). Select the appropriate source field and choose continue  4. You can use your own rules and mapping here. Choose Continue   Move: 1.3. 3.3.1 Use the automatic fieldmapping to create proposals for the mapping for fields with identical names  From the list of steps choose Maintain field mapping and conversion rules  A screen appears  Change the mode from display to change mode  Choose Extras -> Auto-Fieldmapping from the menu  Set the radio buttons according to your needs and choose Continue   For each proposal decide whether to accept or not accept it via the push buttons 3. Position the cursor on the corresponding R/3 field 2.3. The system displays this field as the source field now and defaults a fieldrelated move of data Page 8 of 24 (Date: 28. check whether all source fields are mapped. the Assign source fields dialog box appears.13) . an example will be found at the end of this exercise.2 Rework the rules created and check it against the mapping of 3.

13) . Choose continue  9.07. Choose Field mapping  add source field (icon  ). value) 5. Choose Field mapping  add source field (icon  ). description. Fixed value: 1.. A dialog box appears. where you can decide how to name the parameter.. length. type.’ to the rules  Translation: 1. Select the appropriate source field and choose continue  4. set the radio button  on your selection and choose continue  4. Select the appropriate source field and choose continue  4. From the icon bar click on the button for fixed value 3.. Position the cursor on the corresponding R/3 field 2. From the icon bar click on the button ‘rule’ 6. Position the cursor on the corresponding R/3 field 2. The system displays this field as the source field now and defaults a fieldrelated move of data Page 9 of 24 (Date: 28. Position the cursor on the corresponding R/3 field 2. The system adds ‘concatenate . The system displays this field as the source field now and defaults a fieldrelated move of data 5. Enter the prefix in the dialog box 8. the Assign source fields dialog box appears. Set the radio button  to prefix and choose continue  7. maintain the rule (name. 3. 3. the Assign source fields dialog box appears. In the next screen. Choose Continue   Prefix: 1.

 To check whether all fields are mapped choose Extras -> Non-assigned source fields from the menu  there could be fields which do not need to be mapped!! 3.5 Display the possible values for R/3 field BBKPF-BUKRS  From the list of steps choose Maintain field mapping and conversion rules  Click on icon question mark behind the fieldname to display the possible field values Page 10 of 24 (Date: 28. double-click on the fieldname. set the radio button  on your selection and choose continue   If you want to enter your own code.4 Display the documentation of R/3 field BBKPF-BLART  From the list of steps. If you want to use this function. From the icon bar click on the button for translation 6. you should perform a syntax check afterwards. where you can decide how to name the translation.5.07. Choose icon  . A dialog box appears.13) . which starts the editor. choose Maintain field mapping and conversion rules  Click on icon  (information) behind the fieldname to display the documentation 3.

translation rules.1 Please maintain the values  From the list of steps choose Maintain fixed values. translation. translations. user-defined routines from the list of steps and double-click on the name of the rule (fixed value. fixed values and user routines are maintained 4. translation.2 Question to test your understanding: Which values are set for the fixed values you defined? 4.1 Question to test your understanding: What are the two possibilities to enter the maintenance of the reusable rules?  In step Maintain field mapping and conversion rules go into the editor for the specific R/3-field. userdefined routines  Enter the maintenance of the translation by double-clicking on the name and choose ‘control data’ 4. userdefined routines  Enter the maintenance of the translation by double-clicking on the name and choose ‘control data’ Page 11 of 24 (Date: 28.13) . double-click on the name of the rule (fixed value.07. translations. userdefined routines  Enter the maintenance of the fixed value by double-clicking on the name and look at / maintain field ‘value’ 4.3 Question to test your understanding: What kind of rule is used when the translation does not find a value in the translation table? Where do you set up this?  From the list of steps choose Maintain fixed values. translations.4 Unit: Migration Customizing In this stage. user defined routine) there 4.4 Question to test your understanding: Where do you mark the ‘collection’ of values for translation?  From the list of steps choose Maintain fixed values. translations. user routine)  Choose step Maintain fixed values.2.

A screen appears. enter file path and description and set the radio buttons  according to the file attributes  Choose Continue  5. choose Specify files.txt (ask your trainer for the path) DOC_POSITION: file documentposition. The flag to be set is ‘add 1:1 translation values automatically’ 5 Unit: Read the legacy system data In this stage.2 The file names for the read data and converted data are already set – please check  If you want to change them:  From the list of steps.  Change the mode from display mode to change mode  Position the cursor on line ‘read data’ or ‘converted data’ Page 12 of 24 (Date: 28.txt (ask your trainer for the path) • In each file there is data for one source table • • • • Delimiter used: tabulator Order of fields as in source structure definition Record end indicator (text file) Code page 0120  From the list of steps.1. the source data is read 5.07. choose Specify files.13) .1.1 Maintain the file names and paths (step specify files) 5.  Change the mode from display mode to change mode  Position the cursor on line ‘Legacy data on the application server’  Choose icon  to create a new specification  In the popup.1 Data on the application server: DOC_HEADER: file documentheader.

1 Have a look at the files: Do the field names match with the fields defined? Do the field values look o. The system displays the assignment 5.2 Display the read data. In both structures.  From the list of steps choose Display read data  Leave fields fromline and toline blank in the popup to display all records and choose continue  Page 13 of 24 (Date: 28.3. A dialog box appears where the source file names are displayed.2.txt  From the list of steps choose Assign files  A screen appears where the source structures are displayed  Change the mode from display mode to change mode  Position the cursor on the source structure  Choose Create assignment (icon  ). do a pickup on certain lines to check the field values.. but in the data file the value is alphanumeric?  From the list of steps choose Read data  If necessary.  Position the cursor on the appropriate source file and choose Continue  .3 Check the files and do the upload 5. The structures are strictly hierarchical.. The data is available in the form of two tables (format: text tab delimited).  From the list of steps choose Assign files.07. there is a column containing document numbers.k. Have a look at the field values – are there fields which are numeric.1 5.3. Position the cursor on the file specification and use button display ( ) to display the file.2 DOC_HEADER  documentheader. check the sequence of the records.txt DOC_POSITION  documentposition. the program for reading the source data will be regenerated  Choose icon execute on the selection screen 5.13) .? Do the upload for all records.2.2 Maintain the file assignment (step file assignment) 5. Choose icon  to change the name  In the popup enter the file path  Choose continue  5.

. Do a pickup  on one of the lines and check the values  In the file there should be: . the program for reading the source data will be regenerated  Fill in the selection criteria  Choose icon execute on the selection screen 5.07.one header record starting with LSMW.one DOC_HEADER segment (document header) per FI document .one to x DOC_POSITION segments (document position) per FI document 5...13) .3 Do the upload for the records of document ‘BC10000003’  From the list of steps choose Read data  If necessary.3.4 Display the read data again and check  From the list of steps choose Display read data  Leave fields fromline and toline blank in the popup to display all records and choose continue   Only the data for FI document BC10000003 is displayed Page 14 of 24 (Date: 28.3.

. do a pickup on certain lines to check the field values. translations.one BBKPF segment (document header) per FI document . After this.07.  From the list of steps choose Display converted data  Leave fields fromline and toline blank in the popup to display all records and choose continue   Do a pickup on one of the lines and check the values  In the file there should be: .3 Check which values for 1:1 translation have been added  From the list of steps choose Maintain fixed values. the source file for the import program exists. userdefined routines  Double-click on the translation and choose 1:1 translation values 6.2 Display the converted data. if not.1 Perform data conversion  From the list of steps.6 Unit: Data Conversion In this stage data conversion is done. redo the migration customizing and rerun the conversion  From the list of steps choose Display converted data and do a pickup  Check the field values Page 15 of 24 (Date: 28. 6. ..one BGR00 segment (batch input session header).4 Check whether the translations are correctly.13) .one to x BBSEG segments (document lines) per FI document 6. choose Convert data  If necessary. check the sequence of the records. the program for converting the data will be regenerated  Choose icon execute on the selection screen 6.

07.  Data will be posted directly in this case Page 16 of 24 (Date: 28.1 Run the batch input session  Use transaction SM35 to run the batch input session  Data will be added to the R/3 database 7. start RFBIBL00 with data transfer types “C” and “D”.3 7. the data import into the R/3 database tables is done 7.2.2 Run the import 7.2.2.3 If there were errors.4 Have a look at the migrated documents via FB03. If the session run through without problems.7 Unit: Data Import In this stage of migration. correct the field mapping. choose Start Direct Input Session.  Fill in the parameters and choose execute 7. A screen appears that is associated with the direct input program for FI documents already.1 Start the batch input program RFBIBL00 with following parameters: Data transfer type No. redo the conversion and the test the import again  see descriptions above 7.13) .2 Analyze the incorrect transactions  Use the functions of SM35 to analyze the batch input session 7. of docs per commit work Extended log B 1000 X  From the list of steps.

2 Define source structures and source fields identical to unit 2  See solution chapter 2 8. basis type FIDCCP01  Save your entries  8.07. the list of steps is displayed  From the list of steps.1.  Change the mode from display mode to change mode  Set the radio button  to IDoc (intermediate document)  Enter message type FIDCC1.1.1.8 Unit: IDoc / Recording / Additional Functions Now you should make yourself familiar with the additional functions of LSMW • • • Create recordings Import via IDoc Transport of mapping and rules 8. basis type FIDCCP01 in step “maintain object attributes”  Go to the LSMW initial screen  Type in project. some tips: Valid activities can be found in table T022 Reference activities can be found in table TTYPE Page 17 of 24 (Date: 28.3 Define the structure relations necessary  E1FIKPF  DOC_HEADER  E1FISEG  DOCUMENTPOSITON 8.1.13) . A screen appears.4 Create mapping and rules. choose Maintain attributes of migration object with double-click.1 Choose IDoc FIDCC1.1 Create a migration object for import of FI documents via IDoc FIDCC1 (basis type FIDCCP01) and perform the whole migration process 8. subproject and object  Press enter.

A screen appears.5 Please use the source files from unit 5  From the list of steps. else. endif. DOC_POSITIONPOSNUMBER. Document '. DOC_HEADER-DOCNUMBER.1.FI-IDOC: Document header (complete document) BUKRS Fixed value Fixed value BUKRS BLART DOC_HEADER-TYPE Translation BLDAT DOC_HEADER-DATE Transfer (move) Keep value in internal format BUDAT Constant '20001231' WWERT Constant '20001231' XBLNR DOC_HEADERprefix LSDOCNUMBER BKTXT DOC_HEADERTransfer (move) BKTXT WAERS DOC_HEADERTranslation CURRENCY GLVOR Constant 'GLU1' AWTYP Constant 'EBKPF' AWREF DOC_HEADERTransfer (move) DOCNUMBER E1FISEG .07. endif. E1FISEG-WRBTR = DOC_POSITION-AMOUNT.FI-IDOC: Item data for complete FI document BUZEI DOC_POSITIONTransfer (move) POSNUMBER BSCHL DOC_POSITIONTranslation POSTINGKEY SELECT SINGLE * FROM TBSL WRBTR DOC_POSITIONABAP-Coding WHERE BSCHL = E1FISEG-BSCHL. choose Specify files. E1FISEG-WRBTR = DOC_POSITION-AMOUNT * ( -1 ). else. AMOUNT if sy-subrc = 0.  Change the mode from display mode to change mode  Position the cursor on line ‘Legacy data on the application server’  Choose icon  to create a new specification Page 18 of 24 (Date: 28. SGTXT HKONT DOC_POSITIONTEXT DOC_POSITIONACCOUNT Transfer (move) Prefix '0000' 8.Account numbers have to be transferred with leading zeros Date should be transferred in internal ABAP format  Example: Target Source fields fields Fieldname Fieldname Conversion method Coding/Comment E1FIKPF . if tbsl-shkzg = 'S'. write: 'Posting key does not exist.13) . 'Position'.

choose Goto → Recordings. choose Convert data  If necessary.  Use icon  (create) to create a recording  Enter name and description of your recording Page 19 of 24 (Date: 28.2 Create a recording for transaction FB01 and perform the whole migration process 8. A dialog box appears where the source file names are displayed. the program for reading the source data will be regenerated  Choose icon execute on the selection screen 8.6 Read the source data  From the list of steps choose Read data  If necessary. In the popup.13) .7 Run the import  From the list of steps.1. The system displays the assignment 8.07.  Position the cursor on the appropriate source file and choose Continue  . enter file path and description and set the radio buttons  according to the file attributes  Choose Continue   From the list of steps choose Assign files  A screen appears where the source structures are displayed  Change the mode from display mode to change mode  Position the cursor on the source structure  Choose Create assignment (icon  ).1.2. the program for converting the data will be regenerated  Choose icon execute on the selection screen  Start step Start IDoc creation – the converted data will be written to the IDoc database  Start step Start IDoc processing – IDocs from the IDoc database will be transferred for posting  Start step Create IDoc overview to check the import 8.1 Create a recording for transaction FB01 (with 3 positions) and choose unique parameter names  On the LSMW initial screen.

2. subproject and object  Press enter. you have to assign names to all the fields to be included in the data migration. the list of steps is displayed  From the list of steps. You have to specify values for all those fields that you want to fill with your source data later on.2. The LSMW uses the specified default value for all those fields that you did not assign a parameter name to.07.13) . please define structure SOURCEDOCUMENT as follows: Fieldname DOCNUMBER DATE TYPE CURRENCY BKTXT POSTINGKEY1 ACCOUNT1 AMOUNT1 TEXT1 POSTINGKEY2 ACCOUNT2 AMOUNT2 TEXT2 POSTINGKEY3 ACCOUNT3 Type C DDMY C C C C C AMT1 C C C AMT1 C C C Length 10 10 4 2 20 4 10 15 6 4 10 15 6 4 10 Description Document number Document date Document type Currency Document text Posting key 1 Account number 1 Amount in document currency 1 Description 1 Posting key 2 Account number 2 Amount in document currency 2 Description 2 Posting key 3 Account number 3 Page 20 of 24 (Date: 28.  Change the mode from display mode to change mode  Set the radio button  to Batch Input Recording  Select the recording  Save your entries  8. A screen appears.  At the end of the recording you have to edit the results of transaction recording. choose Maintain attributes of migration object with double-click.  In the last column. The batch input recorder records the procedure while running the transaction. Choose Continue  and have the transaction recorded  run the transaction with a data record as an example.2 Choose the recording in step “maintain attributes”  Go to the LSMW initial screen  Type in project. 8.3 As with a recording a flat source structure is needed.

enter file path and description and set the radio buttons  according to the file attributes  Choose Continue   From the list of steps choose Assign files  A screen appears where the source structure is displayed  Change the mode from display mode to change mode  Position the cursor on the source structure Page 21 of 24 (Date: 28. A screen appears.  Change the mode from display mode to change mode  Position the cursor on line ‘Legacy data on the application server’  Choose icon  to create a new specification  In the popup.4 Create structure relations.07. choose Specify files. mapping and rules Source fields Fieldname Coding / comment Date as DDMMYYYY Fixed value BUKRS '31122000'  Example Target fields Fieldname Conversion method DOCUMENTS – post document via FB01 BLDAT DOCUMENT-DATE Transfer (MOVE) BLART DOCUMENT-TYPE Translation BUKRS Fixed value BUDAT WAERS NEWBS1 NEWKO1 WRBTR1 NEWBS2 NEWKO2 WRBTR2 NEWBS3 NEWKO3 WRBTR3 DOCUMENT-CURRENCY DOCUMENTPOSTINGKEY1 DOCUMENT-ACCOUNT1 DOCUMENT-AMOUNT1 DOCUMENTPOSTINGKEY2 DOCUMENT-ACCOUNT2 DOCUMENT-AMOUNT2 DOCUMENTPOSTINGKEY3 DOCUMENT-ACCOUNT3 DOCUMENT-AMOUNT3 Constant Translation Translation Transfer (MOVE) Transfer (MOVE) Translation Transfer (MOVE) Transfer (MOVE) Translation Transfer (MOVE) Transfer (MOVE) 8.2.5 Please use file document1.txt as source file.AMOUNT3 TEXT3 AMT1 C 15 6 Amount in document currency Description 3  See solution unit 2 8. please ask your trainer for the path  From the list of steps.13) .2.

3. object  On the LSMW initial screen position the cursor accordingly and use icon  (documentation) 8.3.2. user-defined routine  Choose step Maintain fixed values. Choose Create assignment (icon  ). A dialog box appears where the source file names are displayed.2 Fixed value. choose Extras → Object.4 Display the documentation for the project  On the LSMW initial screen choose button ‘Project documentation’ 8.07.5 Display the object overview  From the menu bar on the List of Steps screen. translations  Position the cursor on the name of the rule and use icon  (documentation) 8.3. choose Convert data  If necessary.3 Field mapping  Choose step Maintain field mapping and conversion rules  Position the cursor on the field name and use icon  (documentation 8. The system displays the assignment 8.13) .7 Run the import  From the list of steps. Page 22 of 24 (Date: 28. the program for converting the data will be regenerated  Choose icon execute on the selection screen  Choose Create batch input session  Choose Run batch input session  Data will be written to the database tables 8.  Position the cursor on the appropriate source file and choose Continue  . the program for reading the source data will be regenerated  Choose icon execute on the selection screen 8.3.6 Read the source data  From the list of steps choose Read data  If necessary. overview.3.1 Project.3 Add documentation on following levels 8.2. subproject. translation.

8. A dialog box appears. Select the project you want to export and choose continue  A screen appears where all reusable rules. recordings. A dialog box appears. subprojects and migration objects of the project are displayed Select the objects you want to export Choose export Enter the name of the file in which you want to store the mapping and conversion rules. 1 2 3 4 5 6 7 On the LSMW initial screen. The file is being imported and its contents are analyzed. choose Extras → Export conversion rules. Choose Transfer. recordings. import the mapping and conversion rules: 1 2 3 4 Go back to the initial screen Choose Extras → Import conversion rules. subprojects and migration objects) is displayed  for all object which already exist in the R/3 system you will see a flag (icon  ) Select the objects to be imported.4 Carry out the transport of mapping and conversion rules  First.  Now.07. Choose Import. Enter the name of the file in which the exported mapping and conversion rules are stored. Leave the data format at ASC (= default value). Choose Transfer. Leave the data format at ASC (= default value).13) . 5 6 Page 23 of 24 (Date: 28. A list of the objects determined (reusable rules. you have to export the mapping and conversion rules.

Example for mapping and rules Target Source fields fields Field Field description Type Length Field name name BBKPF – Document header for FI document (Batch-Input-Structure) BLDAT Date (Batch-Input) CHAR 008 DOC_HEADER-DATE BLART BUKRS BUDAT WAERS XBLNR Document type Company code Date (Batch-Input) Currency key CHAR CHAR CHAR CUKY 002 004 008 005 DOC_HEADER-TYPE DOC_HEADERCURRENCY DOC_HEADERDOCNUMBER DOC_HEADER-BKTXT Length 010 004 002 010 020 004 015 Conversion method Transfer (move) Translation Fixed value Constant Translation Prefix Transfer (move) Translation Transfer (move) Coding/comment Date as DDMMYYYY Value '0001' Value '31122000' Group number as prefix Reference CHAR 016 document number BKTXT Document header CHAR 025 text BBSEG – Document line FI (Batch-Input-Structure) NEWBS Posting key for CHAR 002 DOC_POSITIONnext line POSTINGKEY WRBTR Amount in CHAR 016 DOC_POSITIONdocument currency AMOUNT (Batch-InputField) SGTXT Position text CHAR 050 DOC_POSITION-TEXT NEWKO Account or CHAR 017 DOC_POSITIONmatchcode for next ACCOUNT position 006 010 Transfer (move) Transfer (move) Page 24 of 24 (Date: 28.13) .07.