Material Master LSMW does not update all fields.

[Former Member]

Hello Guys,

We are having some problem with Material Master LSMW, we are using Direct Input ( RMDATIND program 0020 object and BMMH1 for Main Data).

The problem is after recent changes in config for some plants couple of new fields are added to accouting view and foreign data views. Our existing LSMW is not able to update these fields although are defined by earlier developer in "Maintain source fields" and they are also mapped correctly in "Maintain field mapping and conversion rules".

When I look at "Display converted data" these fields are being passed correctly to RMDATIND, then debugged the program and found that somehow these new fields are not considered as valid input fields and hence no difference is found between existing MARC structure and new MARC structure passed by LSMW, hence NO UPDATE.

Has any one faced similar problem ? If so how do we fix it ?

[Former Member]

prem

my suggestion is, do the recording for the modified transactin and check weather r u getting the modified fields in the list of recording .

otherwise

did u assing the source structure fields to target structure fields

and is there anything in the program code which is restricting these fields

i think this info is somewhat helpful for u

Regards

naveen

[Former Member]

When you say 'new fields are added', are these standard SAP fields that were hid previously but were enabled now or you actually modified the MARC, MBEW structures?

[Former Member]

These were standard SAP Fields hid previously and are enabled now.

[Former Member]

Srini,

As said earlier fields are sap standard fields like MTUSE, MTORG, STEUC etc... more over we know that these are SAP standard fields because they are included in BMMH1 Structure, which we are using to do the load.

Found following lines in a book of LSMW

When customizing the material master, the Online Service System note 0038229 has to be applied.

Has any one done this ? I checked my system and this note is not yet applied.

[Former Member]

One more question. You said that the conversion looked ok. After this, you debugged RMDATIND and found that the values are ignored. If this is the case, do you still think LSMW is the issue? I haven't looked at the OSS note, but I though I will check with you first.

Can you tell me upto what point are the values seen in RMDATIND?

Srinivas

[Former Member]

Hi

Yes, you are right. I created this OSS note but unfortunately some one else from our company implemented it. i do not have access to check that solutions

Shylesh

[Former Member]

Srini,

In RMDATIND there is a comparision between values which are passed by using LSMW and existing system values. Some how although values for fields like STEUC are passed using LSMW by the time we come to this comparision betwen MARC entries between material and updated values, these fields are themselves lost.

For example

From LSMW for MARC we have following fields(Which can be seen after Conversion Program )

MATNR, WERKS, STEUC, HERKL..... etc

but when the comparision is made from entries in existing material, that internal table from LSMW think it is called IMARC contains only

MATNR, WERKS, HERKL ... etc ( STEUC is lost) and similarly internal table from material entry contains (think name is TMARC) MATNR, WERKS, HERKL.. etc .

Hence field in which difference was there which is STEUC is never even compared, hence LSMW Comes back saying "No changes where made" (Since no field changes were found ).

So essentially the issue is that this field/s which have come into play because of config changes, should be picked up as valid fields for comparision, think if that is done then we would be good.

[Former Member]

So basically when you are in the step 'Start Direct Input program', you see that the values are there, but in RMDATIND ignores them.

Can you please point me to the line where this comparison is happening?

In RMDATIND, there is a call to 'MATERIAL_MAINTAIN_DARK' function module. Put a breakpoint here and check the values in 'i_marc'. If you see your values until here(which I think you should), then something may be wrong in config. Check if the material types you are loading are the same ones for which they changed the screens.

Srinivas

[Former Member]

Srini,

You are right I_MARC contains field STEUC in 'MATERIAL_MAINTAIN_DARK' function module. When you say "Check if the material types you are loading are the same ones for which they changed the screens "

What do you mean ?

[Former Member]

Are you updating the exisiting materials or are you creating new materials?

The screen/field confirguration is tied to the material type. So if they configured it for one material type and you are creating a material of another material type, it will ignore the fields as they are not relevant for the one you are creating/updating. That is what I meant when I asked you about the material types.

[Former Member]

Srini,

We are trying to update the materials and these new fields which come into play are PLANT dependent and not material type dependent.

So essentially if a material 123 is extended to 2 plants "A" and "B" and if NEW config is in place for plant "B" then these fields will appear only for plant "B" and not for plant "A".

[Former Member]

Please see SAP Note 308303 for the solution!

[Former Member]

I was searching for the answer to the same question.But my problem was INDUS,MTUSE are missing while updating..

I have gone through the note 308303 mentioned by Frank.Dat was the perfect one.

Thanks Frank for your Note..

[Former Member]

hi

I have one custom field yyairsea in mara table .We have one lsmw object i want to add this field to this Lsmw object.But when we go for mapping in 5th step maintain field mapping and conversion rules,the field yyairsea is not there in structure BMMH1 .So how can i mapp this field in 5th stepor how can i add this one.

Can any body please help me out.