cancel
Showing results for 
Search instead for 
Did you mean: 

Material Class & Characteristic - LSMW via IDOC method help

Former Member
0 Kudos

Hello,

I'm trying to understand how the IDOC method via LSMW can help with class and characteristics...

The basic scenario is this....

1) We are going to create 1 class

2) We are going to assign 1 characteristic to the 1 class

3) The characteristic is going to have around 100 options to choose from

3) We are going to need to assign the class to over 20,000 material masters

4) We will need to choose what the correct characteristic value will be for each material /characteristic combination

Does the IDOC method for LSMW for any of the items above? If so, does anyone have documentation that shows how you use the IDOC method for this? If this LSMW IDOC doesn't help, is there anything out there that would (besides development ... maybe ecatt) ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Any one?

JL23
Active Contributor
0 Kudos

Looks like you have a bug in your system.

Implement OSS Note 1761207 - Object not found when
posting CLFMAS IDocs

and see if it works then

Former Member
0 Kudos

Implemented note - didnt work, however I made some minor changes to the structure (made the class/chara to CAPITAL letters etc)..

I was finally able to get it to work ... The only thing is now... I added a 2 characterstic... When I ran the LSMW, it added the 2nd characterstic, but it took the value of the old value and made it blank and added the new value for the new characterstic...   Is there a better way or different why I should approach multiple characterstics?

JL23
Active Contributor
0 Kudos

adding single characterstic values is not possible, you always need to submit values for all your characteristics.

Former Member
0 Kudos

Thanks for input... Just so I'm clear though... My LSMW now has 1 class, and two different Characteristics... My source file has 2 entries... Material MRO100 with charactestric Z_MRO_MANUFACTURER and a value LOWES, and material MRO100 (same material code) with characterstic MRO_PUMP_TYPE and its SUPER PUMP

When I run the LSMW, both characterstics get added to the class (which is good) , but only the value of characterstic MRO_PUMP_TYPE  is showing... Characterstic Z_MRO_MANUFACTURER has a blank value.

See attachment /screen shot for better clarity.

Former Member
0 Kudos

And if the material code has another Class setup... When running this LSMW IDOC method it will completely delete that class as well .

JL23
Active Contributor
0 Kudos

you are creating 2 IDOCs for 1 material with just 1 characteristic

but you need only 1 IDOC with 1 material and 2 characteristics

you can achieve it by  rearranging your source file.

create 2 source files

the first has only the material number

the second, is like your currrent source file (but should have the material in the first column)

or

have just one line per material,

you need 5 columns:

material ; characteristic 1, value characteristic 1,  characteristic 2, value characteristic 2,

in this second alternative you need a small coding part in your LSMW segment   E1AUSPM in __END_OF_RECORD__  event, here you you just add after the  TRANSFER_RECORD statement

following line:

E1AUSPM-ATNAM = characteristic 2.

E1AUSPM-ATWRT = characterist value 2.

TRANSFER_RECORD.

Former Member
0 Kudos

Thanks Jurgen for all your answers

sachin_yadav3
Active Participant
0 Kudos

This message was moderated.

Answers (1)

Answers (1)

JL23
Active Contributor
0 Kudos

SAP has batch input, IDOC and BAPI method to load characterstics, classes, class hierarchy and classification.

using LSMW to create a single class and a single characteristc is like using a a grab crane to pick flowers

Create characteristic with CT04 and class with CL03 manually.

then use LSMW to classify your materials e.g. with CLFMAS Idoc method

But loading means basically that the work is already prepared outside SAP, so the source file should already have  the correct characteristic with is value per material.

Former Member
0 Kudos

Hi Jurgen,

Sorry for the confusion - We are planning on manually creating the class and characteristic.... What i was wondering is:

Once i have those setup, how do you use the IDOC method with the LSMW?  Is it much different then the recording... What I'm really wondering also is how is the source file setup? When i do a recording, I setup the column structure myself... DO you do the same thing, or is there a certain structure to follow since you're using the CLFMAS IDOC?

Thanks

JL23
Active Contributor
0 Kudos

my strategy is to have as less information as possible  in a source file. the less the data, the lesser error can be made by a user.

so the source file could in your case just be of 2 fields, the material number, and the characteristic value. As you have only one class with one characteristic, you can put this info as a constant in LSMW, no need that a user need to bother about this.

After you have chosen the IDOC method and entered e.g .message type

CLFMAS with basis type CLFMAS02 then you SAP will display you the target structure in step 4 automatically, you assign your tiny source structure to any level ot the target structure.

In step 5 you can focus on following fields only:

OBTAB = MARA

OBJEK = you material number (think about leading zeros)

KLART = 001

MAFID = O

CLASS = your class

ATNAM = you characteristic

ATWRT = your classification value

Former Member
0 Kudos

Hi Jurgen,

I am running into issue when I run the IDOC - it is not finding the material number... I first tried with leading zeros and got the message below, and then tried without the leading zeros and still got the same message....

Any idea? The material MRO008 does exist in MARA.....

I tried leading zeros and even zeros after and it didnt work.. I went to se16 - mara, and unchecked the conversion button and took the format it showed there.. Still rececieved error.

I even tried a different number and still same issue....

Object MRO008(MARA) not found

Message no. C1155

Diagnosis

Object MRO008 from table MARA has not yet been created. For this reason, no class allocations can be maintained for this object.

Procedure

Create the object, and try to maintain the allocations again.