BAdI /IBP/ECC_SAVE_FIELD_CATALOG.

[former_member310060]

Hello all,

I'am looking for some help on how to use BAdI /IBP/ECC_SAVE_FIELD_CATALOG to enhance the SDI Interface. What I am especially looking for, is the transfer of sales order field ABGRU (reason of rejection) and also Custom Attributes or other fields from this page (https://help.sap.com/viewer/32589988daa3489199b279ac73bf2033/1902/en-US/c0bcd546dbb34530b35f9918335d...).

I'm not really familiar with the usage of BADIs yet, so maybe some of you can help me out? I know it's a more general question, but I don't know where to start.

best regards

Bastian

[lingaiahvanam · Accepted solution]

Hi,

Sales orders are collected and transformed from SAP S/4HANA into the database table /IBP/ORDER_EXT. Additional sales orders attribute not included in this database table are collected and transformed using the field catalog, with the database table /IBP/SLDFCAT_EXT. The field catalog also contains predefined customer fields, which you can fill in using the BAdI /IBP/ECC_SAVE_FIELD_CATALOG.

The customizing setting for the availability check rule is transferred to IBP as a part of the sales field catalog, and is transformed and considered in the order-based planning runs in IBP. You can check this customizing setting in SAP S/4HANA in Customizing under Sales and Distribution Basic Functions Availability Check and Transfer of Requirements Availability Check Availability Check with ATP Logic or Against Planning Define Default Settings Field Avail. Check rule.

I would suggest providing this information to the CPI consultant, they will analyze the source and target filed mapping via custom logic.

Additionally, check the following SAP note.

https://launchpad.support.sap.com/#/notes/2609739

Best Regards,

Lingaiah