Invalid Value Errors-SDI Inbound integration

[ebrahim_bhika]

Hi Experts

When running inbound integration with SDI, the integration job finishes successfully however there are multiple warnings with regards Invalid values within the Tables. These are errors such as Invalid value 'AF1' in table IBP_LOCATION_MATERIAL column DISPO and Invalid value 'ZFRT' in table IBP_MATERIAL column MTART.

What can be done to remove these warnings as these are standard fields which are mapped to external master master data attributes within the Order Based Planning Area and are being integrated.

Regards

[AyanBishnu · Accepted solution]

Hello Ebrahim Bhika

DISPO in table IBP_LOCATION_MATERIAL is where the MRP controller is updated in S4 and MTART is the field material type in the table IBP_MATERIAL.

So please check first if the MRP controller 'AF1' exists in the material master and also check the table IBP_MRP_CONTROLLER and see if the value for is correcty maintained in the table. Refer to the URL taggged above.

Also for 'ZFRT please check if the material type exists and is correctly maintained in the table IBP_MATERIAL_TYPE. From the mentioned error it seems like the values like 'AF1' MRP controller and 'ZFRT material type either doesnt exists in the material master for the list of product location that you are trying to use for SDI inbound or those values are not correctlty maintained in thier respective primary table IBP_MATERIAL_TYPE and IBP_MRP_CONTROLLER. Please check how this data is updating the stagging table.

Also while definfing the IM for the intial transfer make sure that you input the right MRP type and other restrictions so that it covers material and material lcoation combination having the above to values.

Let me know if that works.

[ramguevara]

Hi,

If you are using the IBP add ons in SAP side, did you make sure to run the program in tcode /IBP/ECC_INT_TRANS?

this preloads configuration table (mostly text fields) for the tables you mention above.

the contents of this "Config initialization tables" was not really documented and I came across them through an issue like you.

Regards,

Ram

[ebrahim_bhika]

Thanks Ram and Ayan

The issue seems to be with regards to the Population of the configuration tables with the /IBP/ECC_MDCKTABFILL transaction

Regards