IDOC Segment for AFS Material Additional Data EANs

[Former Member]

Hello experts,

Is there a IDOC segment that will allow the loading of Grid Values and their associated EAN/UPC numbers? I am currently using IDOC Basic Type : u201C/AFS/MATMAS06u201D. I am talking about the values that can be entered manually if you go to MM01 - Additional Data - Additional EANs.

If not, do you simply use the BAPI : u201CAFSSaveDatau201D u2013 Function Module : u201C/AFS/BAPI_MATERIAL_SAVEDATAu201D u2013 Tables : u201CINTERNATIONALARTNOSu201D

Thanks for the help.

[sudha_naik · Accepted solution]

Hello

To load the EAN numbers for the SKU, we can use the segments /AFS/E1MEANM, where we can fill the following fields

MSGFN

J_3AKORDX

/AFS/EANBLOCK

/AFS/CAT_APPL

Hope this information helps.

Regards

Sudha

[Former Member]

So can you load the EAN/UPC numbers themselves directly associated with the corresponding Grid Value?

Let us say I have a two dimensional grid with 32-32, 32-34, 32-36. Can I fill the structure similar to what I have below?

J_3AKORDX = '3232'

/AFS/EANBLOCK = '1234567800002653'

/AFS/CAT_APPL = ''

J_3AKORDX = '3234'

/AFS/EANBLOCK = '1234567800002654'

/AFS/CAT_APPL = ''

J_3AKORDX = '3236'

/AFS/EANBLOCK = '1234567800002656'

/AFS/CAT_APPL = ''

I am assuming the u201CJ_3AKORDXu201D is the Grid Values, u201C/AFS/EANBLOCKu201D is the EAN/UPC number, and u201C/AFS/CAT_APPLu201D would be Category if needed. I am a little confused because the IDOC documentation says that u201C/AFS/EANBLOCKu201D is the Category value. Is that the same as a EAN or UPC number?

[sudha_naik]

/AFS/E1MEANM is a child segment of E1MEANM. E1MEANM contain the field named EAN11, and this field contain the EAN numbers and the /AFS/E1MEANM contain the SKU details.

So the segment hierarchy will be

E1MARMM

-- > E1MEANM (with field EAN11)

-

---

> /AFS/E1MEANM (with fields specific to SKU's)

Hence for the example mentioned, field EAN11 of segment E1MEANM should contain the EAN number and the fields of segment /AFS/E1MEANM should contain the AFS specific details like grid and category value.

J_3AKORDX = '3232'

/AFS/EANBLOCK = '1234567800002653' -- This is wrong, this should contain the category value itself as given in the SAP Documentation.

/AFS/CAT_APPL = ''

To understand the correct formation of data, we can create an IDoc for a material (with additional EANs) via BD10 and review the segment structure.

Regards

Sudha

Edited by: Sudha Naik on Apr 4, 2011 10:13 PM

[Former Member]

This looks like it is going to work for me. Thanks so much for the help!