Some fields not updated in MARA table

[former_member218528]

Hi Everyone,

         I was assigned a task to update entries to whole MARA table fields through BAPI_MATERIAL_SAVEDATA . While creating or updating ,some of the fields are not updating.These are the fields below which are not being updated.

STOFF     -     Hazardous material number

ERGEW   -     Allowed packaging weight

ERGEI     -     Unit of weight (allowed packaging weight)

ERVOL    -     Allowed packaging volume

ERVOE    -     Volume unit (allowed packaging volume)

GEWTO   -     Excess Weight Tolerance for Handling unit

VOLTO     -     Excess Volume Tolerance of the Handling Unit

VHART    -     Packaging Material Type

KZGVH    -     Packaging Material is Closed Packaging

I have filled the respective fields in BAPI_MARA structure for the above fields and their corresponding BAPIUPDATE structures in BAPI_MARAX

HAZ_MAT_NO          -     Hazardous material number

ALLOWED_WT         -     Allowed packaging weight

PACK_WT_UN         -     Unit of weight (allowed packaging weight)

ALLWD_VOL            -     Allowed packaging volume  

PACK_VO_UN         -     Volume unit (allowed packaging volume)

WT_TOL_LT             -     Excess Weight Tolerance for Handling unit

VOL_TOL_LT            -     Excess Volume Tolerance of the Handling Unit

SH_MAT_TYP          -     Packaging Material Type

CLOSED_BOX         -     Packaging Material is Closed Packaging

Can anyone please help me on this..?

Thanks and Regards,

     Rohan

[raymond_giuseppi]

Did you analyze the RETURN table to build a report/log of the execution?

[former_member218528]

Hi Raymond,

                  Thank you for responding.I have uploaded the MARA table entries with some required fields.My client is happy with the fields i have migrated.As an ABAP consultant I still want to know why the fields are not being updated.I have took an screen shot of return messages from returnmessages table.

Please find the whether it may be useful ..

Regards,

   Rohan

[JL23]

you can only maintain fields with this BAPI which you can also enter manually in MM01/MM02

And the messages say that those fields are not open for input, 

[former_member218528]

Thank you Juergen Lins.If we consider first messages in this thread,the field ( STOFF - Hazardous material number ) is an open field in MM01 / MM02. Even though I am passing value to this corresponding field in BAPI and marking Update flag,the record in the table is not being updated.

Regards,

     Rohan

[JL23]

The field is located in the warehouse management view, did you select this view for being processed?

[former_member218528]

Yes I have selected this view.I have filled that in the HEADDATA structure.

Regards,

    Rohan

[JL23]

can you check in OMSR whether this field has an ALE field group assigned and what the maintenance status shows

[former_member218528]

Please find the below Screen shot ..

Regards,

    Rohan

[JL23]

looks good and should work if you selected either storage location view or WM view .

I think you should analyze this isolated with a very small new LSMW.

I just did it an it worked right away.

What I did:

I first searched for a material with a value in field MARA-STOFF using SE16N

Remembered the Haz-Mat Number and removed it from the material using MM02.

I then created a small LSMW.

In the source structure just 2 fields: MATNR and STOFF

in the field mapping I used only constants for just 4 fields

E1BPMATHEAD-MATERIAL = '91007229'.

E1BPMATHEAD-STORAGE_VIEW = 'X'.

E1BP_MARA-HAZ_MAT_NO = '0000000835'.

E1BP_MARAX-HAZ_MAT_NO = 'X'.

My source file was a random file that I took from my PC, as the only thing that matters for this test is that there is something in a source file, but I do not make use of that data.

So I just read 1 record

I convert 1 record

And the result has only the content from my constants.

If this works for you then you know that it is in general possible to update that field with this BAPI and you can concentrate on your coding.

IF it doesn't work this way either, then we can just hope to get some more info from the application log that helps further or at least it confirms that we have to look somewhere else.