Required value "BOM_TYPE" missing; enter a value in the BOM_TYPE field (Message 10015) SAP ME 15.5

[yurika_seko]

We are upgrading our SAP ME system from ME15.1 to ME 15.5 and when we send over a notification from S4 to ME, we get an error "Required value "BOM_TYPE" missing; enter a value in the BOM_TYPE field (Message 10015)".

IDOC type is INOTIF, BOM_TYPE is maintained in ME in value maintenance. We do not get this error in 15.1 with the same payload. I could not find anything on the INOTIF integration in the change log .

[yurika_seko]

Thank you for your response. I just looked over the how to guides and indeed, I do not see INOTIF as a supported IDOC type. It is very strange, as we have been using it since we installed the ME systems years ago. There is also INOTIF available in SAPMEINT Workflow Configuration with standard transactions pointing to Service Order handlers. Do you know what may be an alternative to INOTIF for service Orders? Why is INOTIF available int the workflow configuration? thank you so much !

[yurika_seko]

Just wanted to give an update: I downloaded the services (java:com.sap.me.integration.ERPServiceOrderHandler) from both upgraded/non-upgraded systems, ran the payloads through in soapUI, I was able to reproduce the missing BOM_TYPE error on the non-upgraded service by blanking out the BomType from my payload, so it looked like ME was just not seeing the BomType that was being sent over. I took a closer look and realized that the BomType is missing it's namespace . It works fine in the non-upgraded service, but whatever changed made to the new service must be more strict as that is what is causing the issue. I added the 'me:' namespace and it is working as expected now.

******************************************************************************************

******************************************************************************************

Thank you!

Yurika

[sergiy_katerinich]

INOTIF does not look like a standard IDOC supported by SAPMEINT. Please check SAPMEINT How-To Guide:

https://help.sap.com/doc/ef0a2d2ff87a4e1dbae203a25a29822b/15.5/en-US/sap_me_15_1_sp05_meint_how_to_g...