CIF Product Master Data Done Incorrectly

[former_member491157]

Dear Experts,

Please may you help me understand the reason why CIF of product master data from ECC to APO is not working properly.

The issue seems to be that whatever procurement type I set for the material on ECC side (E, F or X) it flows as type "P" into SAP APO. Even if after initial transfer of product master data to SAP APO I change the procurement type of material on ECC side, that change is not reflected on SAP APO side.

How may I debug the issue and understand what is the root problem causing this inconsistency?

[I310607 · Accepted solution]

HI Azat,

debug /SAPAPO/CIF_PROD_INBOUND - and see whether EFXor P is received to the IT_CIF_MATLOC structure.

Debugging steps of the material transfer are available here: https://wiki.scn.sap.com/wiki/x/CxFiGQ

Are there any user exit custom codes you use?

Best Regards,

Gergely

[former_member491157 · Accepted solution]

Good afternoon, Gergely,

Thanks for the tips and guidance regarding debugging /SAPAPO/CIF_PROD_INBOUND, I will look into it.

Indeed, there is a user exit implemented EXIT_/SAPAPO/SAPLCIF_PROD_001. The initial idea of that user exit implementation was to switch the procurement type to "P" on APO side for those materials, which were marked for deletion on ECC side (field LVORM set to "X").

Now, the problem is that the business wants the reverse process to happen when the deletion flag (LVORM) is removed on ECC side. I.e. if on ECC side the material is active (LVORM is set to blank), APO should change the procurement type from "P" to the procurement type of material indicated in ECC (E,F,X). For some yet unknown reason this does not happen.

I apologize in advance if my explanation does not add clarity.

[I310607 · Accepted solution]

Hi Azat,

I believe that debugging the code can reveal what happens before and after calling the BADI exit.

Set up your integration model consisting of only 1 matloc, and toggle the deletion flag at ERP side. If needed, use CFM9 transaction.

You can as well stop the inbound queue at SCM side in SMQ3 transaction, and then you will have SMQ2 transaction with the stopped inbound data for a quicker debugging.

Best Regards

Gergely