Matid between APO and EWM

[former_member481265]

Hi all,

I wanted to know does the Matid for a part 'A' will be the same in APO and all EWM instances.

we currently have a APO system and 3 instances of EWM system,when I look up field MATID for a given part in /SAPAPO/MATKEY table the matid is same in APO and all EWM instances even when the part creation between APO and EWM is on seperate dates (some 2 months apart).

So I have 2 questions regarding this:

1) Can we assume that the Matid will always be the same between APO and all EWM.

2) if first is true how does SAP assigns the same matid.

Regards,

AJ

[former_member481265]

Actually when the Material is created in ECC a 16Char Guid is created and updated in table NDBSMATG16.

Now when the material is CIFed from ECC to EWM/APO this 16char GUID is sent which gets converted in APO/EWM system to 22 Char GUID resulting it to be same across systems.

Thanks for your input.

Regards,

Akshat Jain

[jonnakutiraju]

Akshat Jain, Thanks for the information.

I have the same problem when checking the Table /SCWM/T_VAL_SPLT in EWM. This table shows the MATID (with GUID) but it does not show the Material code on the front end. Note: It shows the Material number when you double-click on each line.

So, I went through Table NDBSMATG16 in ECC (which you have mentioned) and it shows the same MATID with material code. It was resolved my issue.I hope it will resolve the issue with others also.

Thank you

Raju Jonnakuti

[I310607]

Hi AJ,

what I would recommend is to create test environments and set up test cases and see if MATIDs will be the same. This could be a subject of a nice blog about the test results anyway 😉

I can give you some general ideas and hints.

- MATID + MANDT fields are together adding up as a key in /SAPAPO/MATKEY. Independently from which application APO/EWM are using the MATID, they will use the same MATID if they are on the same client.

- The function module, that creates /SAPAPO/MATKEY entries is /SAPAPO/DM_PRODUCTS_POST.
Guid creation takes place at:

CALL METHOD /scmb/cl_guid_map=>map_and_insert_guid
EXPORTING
iv_id_name = 'MATID'
iv_guid = <ls_matkey>-matid
EXCEPTIONS
mapping_does_not_exist = 1
others = 2.

Class: /SCMB/CL_GUID_MAP method: MAP_AND_INSERT_GUID

More technical information about products: https://wiki.scn.sap.com/wiki/x/wg0MDg

Best!
Gergely

[former_member481265]

Hi Gergely,

I was able to identify why the matid is same across multiple EWM and APO system for the same material number.

Actually when the Material is created in ECC a 16Char Guid is created and updated in table NDBSMATG16.

Now when the material is CIFed from ECC to EWM/APO this 16char GUID is sent which gets converted in APO/EWM system to 22 Char GUID resulting it to be same across systems.

Thanks for your input.

Regards,

Akshat Jain