Top Banner
LEGACY SYSTEM MIGRATION WORKBENCH STEPS TO DATA MIGRATION MATERIAL MASTER DATA Version 1.6 August 1999 /home/website/convert/temp/convert_html/544c097baf7959b0438b57fb/document.doc 1
49
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Apostila LSMW - Price

LEGACY SYSTEM MIGRATION WORKBENCH

STEPS TO DATA MIGRATION

MATERIAL MASTER DATA

Version 1.6August 1999

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 1

Page 2: Apostila LSMW - Price

CONTENTS

I Investigation of SAP’s Data Migration Tools...................................................................41 Goal.........................................................................................................................................................4

2 Benefits....................................................................................................................................................4

3 Expected deliverables..............................................................................................................................4

II Deliverables.........................................................................................................................51 Scope/Purpose.........................................................................................................................................5

2 Intended Audience...................................................................................................................................5

3 Functionality............................................................................................................................................5

4 Suitability of tasks...................................................................................................................................5

5 Business Objects supported.....................................................................................................................5

6 Limitations...............................................................................................................................................6

7 Advantages..............................................................................................................................................6

8 Other Sources..........................................................................................................................................6

III Example 1 - Upload material master data using standard program................................71 STEP 1 – MAINTAIN OBJECT ATTRIBUTES...................................................................................8

2 STEP 2 – MAINTAIN SOURCE STRUCTURES.................................................................................8

3 STEP 3 – MAINTAIN SOURCE FIELDS.............................................................................................9

4 STEP 4 – MAINTAIN STRUCTURE RELATIONS...........................................................................10

5 STEP 5 – MAINTAIN FIELD MAPPING AND CONVERSION RULES.........................................11

6 STEP 6 – MAINTAIN FIXED VALUES, TRANSLATIONS, USER-DEFINED ROUTINES.........16

7 STEP 7 – SPECIFY FILES...................................................................................................................17

8 STEP 8 – ASSIGN FILES.....................................................................................................................19

9 STEP 9 – READ DATA........................................................................................................................19

10 STEP 10 – DISPLAY READ DATA....................................................................................................20

11 STEP 11 – CONVERT DATA..............................................................................................................21

12 STEP 12 – DISPLAY CONVERTED DATA.......................................................................................21

13 STEP 13 – START DIRECT INPUT SESSION...................................................................................22

IV Example Two – Using header and detailed file for material master data......................27

V Example three – Using Batch Input Recording to import material master data...........34

VI Appendix...........................................................................................................................401 Appendix 1 – List of standard programs...............................................................................................40

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 2

Page 3: Apostila LSMW - Price

I Investigation of SAP’s Data Migration Tools

1 GoalInvestigate the SAP supplied Data Migration tools: the Legacy Data Migration Workbench and the Data Transfer Workbench.(This document concerns the Legacy Data Migration Workbench).

2 BenefitsIncrease the ease of use of these standard tools through the Toolkit and the Field guide and therefore increase their use on PwC SAP projects possibly reducing development effort and complexity. Increase knowledge of standard tools in PwC and develop “expert” resources.

3 Expected deliverables1) Field Guide for each of the Tools containing the following information: Explanation of the scope and purpose. Suitability for certain tasks (i.e. Complex data conversion, Simple data dumping). List of Business objects supported (i.e. Material Master, Sales Order… ). How data input is achieved; Direct Input, BDC, Call Transaction or other. Whether a sample file producing program using real data is available. Whether it

works. Documentation on the file formats that a functional person could understand (linking

the fields to screen fields). Documentation on use, including an overview of the whole process.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 3

Page 4: Apostila LSMW - Price

II Deliverables

1 Scope/Purposea) Discover what the LSMW functionality are, hence what does it do.b) Discover its suitability in regards to data conversion.c) Find out what business objects it supports.d) Discover how the Legacy Data Migration Workbench (LSMW) work, hence successfully

use it to convert and upload data into SAP.

2 Intended AudienceThis document is intended for people with an understanding of SAP data uploads using BDC and basic ABAP programming.

3 FunctionalityThe core functionality of the LSM Workbench is to import data from the legacy system, convert them into the target SAP format and import it into SAP.NOTE: The LSMW does NOT extract or clean the legacy data for you.

4 Suitability of tasksThe LSM Workbench converts data by generating a conversion program based on the mapping conversion rules you define. Types of mapping conversion rules it can do is: Direct 1:1 field mapping I.e. Source data => target data Addition of prefix/suffix I.e. Source data + P/S => target data Filter out blank data in a field Use a lookup table to convert data either:

1:1 translation I.e. X1 -> Kg, X2 -> Ea Interval translation 2000 - 2999 -> NSW, 3000 - 3999 -> Vic

5 Business Objects supportedThe LSMW uses four methods of importing the data into SAP.

I. Standard Batch/ Direct Input.This uses SAP standard programs to import data. This is where the LSMW is linked to the Data Transfer Workbench as both uses the same to import the business objects. (i.e. material master data)Refer to Appendix 1for the list of business objects and SAP standard programs the LSMW uses to import data. The standard programs will import data using either batch input or direct input, depending on the program chosen. For more details on the Standard program, refer to the Data Transfer Workbench guide.

II. Batch Input RecordingThis import method uses a recording as a basis for the import program. It requires you to record the transaction you will be using to input the data. Hence, if what you want to import is not covered by the above SAP standard programs, you can use the Batch Input Recording import method to import data. This creates a session and import data into SAP using Batch input.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 4

Page 5: Apostila LSMW - Price

III. BAPIYou can choose to import data using BAPIs (Business Application Programming Interfaces).

IV. IDocsYou can also choose to import data using IDocs (Intermediate Documents)

6 LimitationsThe limitations of the LSM Workbench is that: The LSMW can’t extract data from the legacy system. It cannot be used to extract

data. It cannot be used for outbound interface.. Ie send information outwards from SAP.

E.g. HR updating of phones in SAP. Can’t update it to the telephone directory if it is external to SAP.

The LSMW cannot detect if configuration change has occurred in the system if Direct input method is employed.

The level of support form the resources is limited. At the moment there is very few notes on it in the OSS. There is not much information available on it.

It is not 100% flexible. 7 AdvantagesThe advantages of using the LSM Workbench are: It is a part of R/3 and thus independent of individual platforms It has a variety of technical possibilities of data conversion: Data consistency due to standard import techniques:

Batch input Direct input BAPIs (Business Application Programming Interfaces) IDocs (Intermediate Documents)

The import technique to be used in an individual case depends on the business object. Generation of the conversion program is on the basis of defined rules Clear interactive process guide Interface for data in spreadsheet format Creation of data migration objects on the basis of recorded transactions Charge-free for SAP customers and SAP partners Don’t need to test the program, need only to validate mapping and conversion rules.

8 Other SourcesFor a more in-depth look at the functionality of the LSM Workbench, refer to the SAP guide – ‘Data Migration of Non-SAP systems to R/3. Quick Introduction to

Working with the Legacy System Migration Workbench Version 1.6’. July 1999. The SAP provided presentation slides, The internally created LSM Workbench Presentation. Also refer to the Data transfer Workbench documentation and slides.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 5

Page 6: Apostila LSMW - Price

III Example one - Upload material master data using standard program.

To start, type in the transaction code: LSMW.Click on the ‘Create’ button to create a project.

Enter the Project, subproject, object and their descriptions. If you require more than one subproject, place the cursor on the subproject field and press create. The same applies for the object. Once this is complete, click on the ‘Continue’ button to go to the next screen.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 6

Maintaining source structures and fields.

Mapping source fields to target fields.

Upload legacy data (internal table), and converting data using the mapping rules defined in earlier steps. Ready to be imported into SAP.

Which of these step appears will depend on the attributes defined in Step 1.

Click to

execute the

step

Click to toggle

between edit

and display

CreateContinu

e

Page 7: Apostila LSMW - Price

You will be presented with the screen above. As illustrated above, Steps 1 to 12 will always appear. Steps 13 to 20 being displayed will depends on what data migration attributes you choose in Step 1.

1 STEP 1 – MAINTAIN OBJECT ATTRIBUTES

Start with step 1. Here, you choose the attributes of your conversion program. In this instance, the Standard Batch/direct input for Material master data is chosen. The data transfer will occur once.

2 STEP 2 – MAINTAIN SOURCE STRUCTURES

Before starting with the conversion, research on the mapping conversion rules and the legacy data format was done. In Step 2, create the source structure. I.e. the structure in that your source data will be placed into.To create a structure, click on the ‘Source structure’ and select ‘Create’. The below screen appears.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 7

Save

Create Delete

Page 8: Apostila LSMW - Price

Enter your structure table name and description and click on the ‘Continue’ button.Once your structure is defined, it should look like the above screen.

3 STEP 3 – MAINTAIN SOURCE FIELDS

Once the structure of the legacy data is defined, it’s fields will need to be defined in Step 3. Determine what fields the legacy data requires and define them here. To create a field, select the ‘Material_table’ tab and click ‘Create’. The below screen appears for you to enter in the field attributes.

The ‘Identifying field value’ field is used for documentation purposes. This is where you place the legacy system name of the field so you can reference it back to the legacy system.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 8

Create

Copy source

fields from other

sources

Table Maintenance

Page 9: Apostila LSMW - Price

After defining the legacy data (source) structures and field, the mapping between the legacy data and SAP begins. In step 4, the relationship between the source and target structure is defined.

You can also define your fields in a table format if you don’t wish to do it the other way. To get to this screen, click on the ‘Table Maintenance’ button.

4 STEP 4 – MAINTAIN STRUCTURE RELATIONS

In this instance, only one structure was defined. To assign the source structure to the target structure, click on the ‘Relationship’ button. If you have defined more than one structure, it will query you which structure you want to assign. However, in this instance, we have one structure so it’s automatically assigned when you press the ‘Relationship’ button.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 9

Create

relationshi

p

Page 10: Apostila LSMW - Price

As describe above, the first hierarchical target structure holds the batch input session data, the child of this structure holds the transaction data and its child structure is the main place where data transfer takes place.

5 STEP 5 – MAINTAIN FIELD MAPPING AND CONVERSION RULES

Once the relationship between the structures are establish, the conversion rules between the source and target fields are defined. This is done so in Step 5. In the above screen, a constant was defined for the target transaction code field. To create a constant containing the transaction code, select the field ‘TCODE’, click on the ‘Rules’ button and select the ‘Constant’ radiobutton. The below screen appears.

Click ‘Okay’ to continue. The below screen will appear, asking for the constant value.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 10

Create

relationship

Choose rules

Check Syntax

Page 11: Apostila LSMW - Price

Enter the constant value and continue.To assign a source field to a target field, place the cursor on the relevant target field. Select the ‘Select field’ button. A popup screen will appear with all the source field available to be assigned.

Select the relevant source field. The default conversion rule for the source and target field is ‘Transfer (move)’. Hence , the code would become: Target field = Source field.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 11

Page 12: Apostila LSMW - Price

To add a prefix to a source field whilst transferring it to the target field, first assign a source field to the target field then, select the ‘Rule’ button. The below screen appears.

Select the ‘Prefix’ radiobutton. As we don’t wont to move any fields which are blank, select the check box ‘Only if source field is not initial’. A popup screen will appear asking for the prefix.

Enter your prefix and continue.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 12

Page 13: Apostila LSMW - Price

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 13

Page 14: Apostila LSMW - Price

To create a ‘Fixed value (reusable)’, select the target field you want to become a fixed value. Click on the ‘Rules’ button. The below screen will appear.

Select the ‘Fixed value (reusable)’ radiobutton and continue. You will be presented with the screen below asking for the name of the fixed value.

It will automatically default to a radio button. Select the default and continue.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 14

Page 15: Apostila LSMW - Price

Enter the fixed value you want the field to be and continue.Save the conversion rules you’ve created. Before exiting this step, press on the Syntax check button to ensure that ‘The conversion program could be generated successfully’.

6 STEP 6 – MAINTAIN FIXED VALUES, TRANSLATIONS, USER-DEFINED ROUTINES

To maintain your reusable rules and user-defined routines, this is done is step 6. If you have any reusable rules or user defined routines, it would appear here. To maintain them, select the rule you want to maintain and select the ‘Edit’ button.

If you selected to change a fixed value the above screen would appear.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 15

Page 16: Apostila LSMW - Price

If you choose to maintain a translation, the above screen appears. However if you’ve chosen to maintain a user-defined routine, the below screen will appear.

7 STEP 7 – SPECIFY FILES

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 16

Page 17: Apostila LSMW - Price

Once you’ve completed mapping the conversion rules, you’ll need to define where the legacy files going to uploaded from in Step 7. In this instance, the legacy file is to be uploaded from the local C:\ drive. Place the cursor on the ‘Legacy data – On the PC (frontend)’ tab and press the ‘Create’ button. The below screen will appear.

Enter the file path of the legacy data and its description. Select the file contents, delimiter, file structure, file type and code page which most describes the format of the legacy data file and Continue.

There will be a default file path in the ‘Read data – File for read data’ section. Select this tab and press ‘Edit’. Change the file path to be similar to the above. Continue. Once the legacy file is uploaded into SAP, and before the conversion, it is placed in this file. Leave the ‘Converted data – File for converted data’ file path as default.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 17

Page 18: Apostila LSMW - Price

If your file was from the server, select the ‘Legacy data – On the R/3 Server (application server)’ you would be presented with the above screen. Enter the relevant details and continue.Save your changes and continue to Step 8.

8 STEP 8 – ASSIGN FILES

In this instance, only one file was defined, hence it is automatically assigned to the source structure table. This means that the data in the legacy file will be uploaded into the Material_table structure. Save and continue to the next step.

9 STEP 9 – READ DATA

Once the file path to the legacy system is defined, it will need to be uploaded into SAP. Step 9 reads the data and uploads it into the Material_table structure. You’ll be present with the above screen. You can either choose to read a limited number of records by entering the record number into the select-option box, or read all the data by leaving the Transaction number select-option clear and press on the ‘Continue’ button.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 18

Execute

Page 19: Apostila LSMW - Price

Once the legacy data is read, the above screen will appear telling you how many records were read. If the read was unsuccessful, it will tell you what might be wrong with your data. The read records will now be placed into the ‘Read data’ file path defined earlier.

10 STEP 10 – DISPLAY READ DATA

After you’ve completed uploading the data, it can be viewed in Step 10. Choose the record lines you want to view.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 19

Page 20: Apostila LSMW - Price

Note: that the data you are viewing is the legacy data, loaded into the format of the source structure and fields.

11 STEP 11 – CONVERT DATA

Once you’ve viewed the data and is happy that it is loaded in correctly, proceed to Step 11 to convert the data using the mapping rules you’ve defined in Step 5 and 6. Again, you have the option of choosing a range within your data to convert, or converting every thing by pressing the ‘Continue’ button.

When the conversion process is complete, the above screen will appear informing you of how many records were successfully converted. The converted data are now placed in the ‘Converted data’ file path defined in Step 7.

12 STEP 12 – DISPLAY CONVERTED DATA

Step 12 allows you to view the data after it is converted. Choose the number of line to view and continue.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 20

Execute

Page 21: Apostila LSMW - Price

Once the line number you want to view is chosen. The converted data is displayed. this is a good opportunity to ensure that your conversion rule is correct and is as required. Once you’re happy with the data, proceed to the next step.

13 STEP 13 – START DIRECT INPUT SESSION

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 21

Page 22: Apostila LSMW - Price

You’ve now gone through all 12 Steps. These are the preparation steps in getting your data ready to be inputted into SAP. Step 13 will start the Input process. Press on ‘Edit’ to continue.

The above popup screen appears. If you choose to direct input via the program RMDATIND the below screen will appear. For more details on how the Direct input program and transaction, refer to the ‘Transferring of Data via Direct Input’ slide from the Data Transfer Workbench presentation.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 22

Page 23: Apostila LSMW - Price

Enter in the relevant details and press ‘Continue’. The LSMW will go through a series of popup screen informing you of the status as it progress through the data input. Once it is completed, it will tell you whether the whole process is successful or if there is any errors.When the process completes, and errors exists, it takes you to the below screen and highlights the records in error.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 23

Page 24: Apostila LSMW - Price

Hence, from the above, we’ll know that 17 of the 20 records has been created. Hence material number 469 to 488 are created.To check that the records are created, goto transaction code SE11, view the table MARA (display).

From the above, we note that from material number 469 to 488 is created with the exception of material numbers 470, 475 and 482.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 24

Page 25: Apostila LSMW - Price

If you’ve chosen to enter the data through the Transaction BMV0, you’ll need to have the data uploaded from the server.

See the Data Transfer Workbench for details on how to upload using transaction code BMV0.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 25

Page 26: Apostila LSMW - Price

IV Example Two – Using header and detailed file for material master data

Create an object to work in.

Select Step one and choose the standard batch/direct input import technique for material master data. Save.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 26

Page 27: Apostila LSMW - Price

Create the structures as illustrated above. When you create the second structure, the below screen will appear asking what level is it in relation to the first structure. Choose sub-ordinate.

Create the fields as displayed above. Note that there has to be a common field between them. In this case, it’s the old material master (S_BISMT) field. The reason why this field was chosen was because the material number field will be created internally in SAP. Hence, another key field was required. The H_STYPE fields and D_STYPE field is simply a record indicator, indicating whether it’s a header or detailed record.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 27

Page 28: Apostila LSMW - Price

Define the structure relationship. Select the structure, select the ‘Relationship’ button and choose the source structure as required.

The conversion rules used here is the same as the previous example. the main difference being that the source fields are coming from different tables. The structure BMM00 is the header structure. Hence, the header source structure and fields are mapped to here. The structure

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 28

Page 29: Apostila LSMW - Price

below this are the details header, hence the detail source structures and fields are mapped to the relevant fields.

When mapping fields in the header structure, only the source fields in source header structure are available. However, once we move on to the detailed structures, all fields are available.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 29

Page 30: Apostila LSMW - Price

Define the legacy files.

Once the legacy file is defined, it needs to be mapped to the source structures. To assign the legacy file to the source structure, select ‘Assignment’ and select the relevant file. The below screen will appear to choose from.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 30

Page 31: Apostila LSMW - Price

When you’ve completed defining the files and doing the necessary preparation work, it’s time to read the files. Execute Step 9. Once it’s completed, a report similar to the screen above should display. Note that it has read in two files and wrote it to the one ‘read’ file.

View the read data to ensure that everything is loaded properly. Note here that two shades of line has appear. the yellow lines indicates the header structure and the blue indicates the detail.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 31

Page 32: Apostila LSMW - Price

Now that the legacy data is read, it’s time to convert it. Execute step 11. A similar screen to above should appear.

View the converted data. Note that it is sorted by structure. Once you’re happy with the converted data, continue with the rest of the steps.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 32

Page 33: Apostila LSMW - Price

V Example three – Using Batch Input Recording to import material master data.

Create an object. Then select Goto -> Recordings.

You’ll be presented with a screen similar to below. Place the cursor on the ‘Recordings’ branch and select ‘Create’, to create a recording.

Enter in the name and description of the recording. Once this is done, the next screen is presented.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 33

Page 34: Apostila LSMW - Price

Enter the transaction code for the first screen of the transaction you want to records. Once you press continue, this will goto the transaction screen you indicated above. Go through the steps you would normally go through to create the transaction. When you save the transaction, the recording stops. You will then be presented with the below screen.

Create the name for your target fields. To create the name, double click on the field and the below screen appears.

Enter the name and description of the field. The default value is the value you entered for it in the transaction. Once you’ve completed naming the fields, save the recording and exit back to the front screen. Now you can enter the LSMW to start on Step 1.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 34

Page 35: Apostila LSMW - Price

Because we’re doing the batch input using a recording, select the ‘Batch Input Recording’ button. Then select the recording you want to use. Note: The only real difference between using the Standard Batch / Direct Input method and the Batch Input Recording method is this first step.Following the consequent steps as you would with the Standard programs.

Create the source structure.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 35

Page 36: Apostila LSMW - Price

Create the fields. In this case, it was copied from ‘Demo_1’ of the same subproject. To do this, select the structure, then press on the ‘Copy’ button. The below screen appears.

Choose to ‘Copy from other object’. The below screen will prompt you which other project.

Enter the source structure you want to copy from the other object and continue. Save the step before exiting.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 36

Page 37: Apostila LSMW - Price

Now define the structure relations. Because it’s a recording, only one target structure, hence source structure can be defined. Save and continue.

Map the source fields to the target fields as you would with the standard batch/direct input methods.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 37

Page 38: Apostila LSMW - Price

The consequent steps (i.e. steps 6 to 12) are exactly the same as the standard batch/ direct input method.If you want to check if configuration changes has occurred in the system, select the ‘Personal Menu’ button. Select the ‘Check converted data against customising’ checkbox and execute this step.

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 38

Page 39: Apostila LSMW - Price

VI Appendix

1 Appendix 1 – List of standard programsProgram

Obj. Description Mth. Description Name Typ

0001 Long Text 0001 No Selection /SAPDMC/SAP_LSMW_IMPORT_TEXTS D

0010 GL acc. master data 0001 Heir. Structure RFBISA00 B

0002 Flat Structure RFBISA00 B

0020 Material master data 0000 RMDATIND D

0030 Material BOM 0001 Create RCSBI010 B

0002 Change RCSBI020 B

0003 Create Variant RCSBI030 B

0004 With long text RCSBI040 B

0040 Vendor master data 0001 General RFBIKR00 B

0002 Retail RFBIKR00 B

0050 Customer master data 0000 RFBIDE00 B

0060 Purchasing info rec. 0000 RM06IBI0 B

0070 Condition Record 0000 RV14BTCI B

0080 Purchase Requisition 0000 RM06BBI0 B

0090 Sales Document 0000 RVINVB10 B

0100 Financial documents 0000 RFBIBL00 B

0110 Goods Movement 0000 RM07MMBL B

0120 Manual Reservation 0000 RM07RRES B

0130 Classification 0000 RCCLBI03 D

0001 Batch Input RCCLBI02 B

0002 Direct Input RCCLBI03 D

0140 Class 0000 Direct Input RCCLBI01 B

0150 Characteristics 0000 Batch Input RCCTBI01 B

0160 Fixed assets 0001 Batch Input RAALTD01 B

0002 Direct Input RAALTD11 D

0170 Routing 0000 Direct Input RCPTRA01 B

0180 Planned indep. reqmts 0000 RM60IN00 D

0001 Batch Input RMMM60BI B

0190 Doc. purch. info rec 0000 Batch Input RCVBI010 B

0210 Storage bin (WM) 0000 RLPLAT00 B

0220 Warehouse Stock (WM) 0000 RLBEST00 B

0230 Equipment 0000 IBIP B

0300 Rental Unit 0000 RFVIMEDI D

0310 Rental Agreement 0000 RFVIMVDI D

0555 HR master data 0000 Batch Input RPUSTD00 B

0777 HR Planning 0000 Batch Input RHALTD00 B

0800 Do not use ! 0000 IBIP

7060 Purchasing info rec 0000 RM06IBI0 B

7170 Routing 0000 RCPTRA01 B

/tt/file_convert/544c097baf7959b0438b57fb/document.doc 39