LSMW CA01- Object 170, Method - 0001, Program - RCPTRA01, Prog - B

[Former Member]

Dear ALL,

I am tring to Run LSMW for CA01- Object 170, Method - 0001, Program - RCPTRA01, Prog - B.

Follwing Source Structure, Fields & Files are maintained.

Header

MATNR Material Number

PLNNR Key for Task List Group

PLNAL Group Counter

KTEXT Task list description

PLNME Unit of Measure for The Task List

Operation

MATNR Material Number

PLNNR Key for Task List Group

PLNAL Group Counter

VORNR Operation/Activity Number

STEUS Control key

ARBPL Work center

LTXA1 Operation short text

BMSCH Base Quantity

MEINH Unit of Measure for Activity/Operation

UMREN Denominator for conversion from unit to base unit (BTCI)

UMREZ Numerator for converting from unit to base unit (BTCI)

VGE01 Standard Value (Batch Input)

LAR01 Unit for the standard value (batch input)

VGW01 Activity Type

VGE02 Standard Value (Batch Input)

LAR02 Unit for the standard value (batch input)

VGW02 Activity Type

VGE03 Standard Value (Batch Input)

LAR03 Unit for the standard value (batch input)

VGW03 Activity Type

VGE04 Standard Value (Batch Input)

LAR04 Unit for the standard value (batch input)

VGW04 Activity Type

VGE05 Standard Value (Batch Input)

LAR05 Unit for the standard value (batch input)

VGW05 Activity Type

VGE06 Standard Value (Batch Input)

LAR06 Unit for the standard value (batch input)

VGW06 Activity Type

Master Inspection Characteristics

PLNNR Key for Task List Group

PLNAL Group Counter

VORNR Operation/Activity Number

MERKNR Inspection Characteristic Number

VERWMERKM Master Inspection Characteristics

QPMK_ZAEHL Plant For Master Inspection Characteristics

MKVERSION Version No of Master Inspection Characteristics

STELLEN No. of Decimal Places

MASSEINHSW Measurement Unit in Which Quantitative Data Is Maintained

SOLLWERT Target Value for a Quantitative Characteristic

TOLERANZOB Upper Specification Limit

TOLERANZUN Lower Specification Limit

PMETHODE Inspection Method

QMTB_WERKS Plant for Inspection Method

PMTVERSION Version No of Inspection Method

STICHPRVER Sampling Procedure in Inspection Characteristic

Following is the assignment,

BI000 - Header

BI001 - Header

BIMPL - Header

BIPKO - Header

BIPPO - Operation

BIPMK - Master Inspection Characteristics (MIC)

All other settings are maintained as constant.

Data is being able to read & convert.

While running Batch Input in front mode it is observered that only header data is uploaded and Operation & MIC data is not being uploaded.

System also not throwing any error.

Let me know what would be the reason of Operation & MIC data is not being uploaded.

Thanks

[Dsk · Accepted solution]

Hi Prasanth.

1. i think your are missing the Record types

2. go to se38 > program name > click documentation.

it has more details kindly read and proceed as per that instruction.

later let me know if you need any help.

Reg

dsk

[Former Member · Accepted solution]

Can you please let me know where we can maintain this "Record Type".

I am not able to see it in "Maintain Field Mapping and Conversion Rules"

Regards,

[Former Member · Accepted solution]

Hi,

I'm Facing same problem, data on Operation didn't get populated.

Kindly advise what steps needs to be done.

Thanks,

Jay

[Former Member · Accepted solution]

Hello Guys,

I know this post is a little bit old, but maybe some other users run into trouble again, so i'll post my solution.

I want to migrate data „create routing – CA01“.

I used the structures:

• BI000
• BI001
• BIMPL
• BIPKO
• BIPPFL
• BIPPO

First of all you have to use the same values of PLNNR(NODATA), PLNAL(‘1’), PLNTY (‘N’) for the structures BIMPL, BIPKO, BIPFL, BIPPO.

Here I run into trouble because at first I assigned the NODATA Entry to PLNNR, but instead a empty string (‘’) is needed.

Same PLNFL for BIPPO, BIPFL where I used a fixed value ‘00000’.

After this assignments I was able to transfer the data to the Batch Input Session.

Best regards,

Nikolaus

[Former Member · Accepted solution]

Hi Nikolaus,

I'm not able to create routing with operations.

Can you help with more details?

[andrea_brusarestelletti]

Hello,

I know that it could seem a stupid suggestion, but I spent a lot of hours woking on this LSMW and trying to make it run: check that all the leading zeros of the fields that you set as costants and from the files are filled, with particular attention to field PLNAL: in transaction screens and in tables it shows up with one character, but the LSMW structures record it with two characters. Same thing for fiels VORNR.

Hope to be useful.

Best regards,

Andrea