Skip to Content
Author's profile photo Konstantin Chernega

How to integrate additional custom fields for ME objects

Hello folks,

Finally I have a little bit of inspiration to create a blog post ­čÖé . Today I’d like to show you how to integrate custom information from an IDOC to your ME object, i.e. material, shop order etc, as a ME custom field by slightly brushing MEINT workflow and using modified XSLT.

First of all you’d have to create a placeholder for custom data in ME by adding custom field to a ME object. Let’s assume that we want to add some characteristics for material even though there is a dedicated IDOC type for this – CLFMAS. I just want to show the sequence of steps and logic that can be used to add custom information for any ME object, i.e. BOM, Shop Order etc. Thus we should go to Custom Data Maintenance in ME and add couple of custom fields there:


These fields are visible now and can be used in Material Maintenance on Custom Data tab:


Now MEINT integration workflow for MATMAS idoc has to be customized to accept the information from IDOC fields and add it to Material creation WS request to ME. I’ll customize Z_MATMAS03 worflow, therefore I need to go to SAPMEINT Workflow Configuration and check which XSLT is used for the workflow I’m interested in:


After this I need to find the XSLT in MII Workbench, save a copy to a new MII project and modify it by adding <CustomFieldList> block:


You could add more complex XSLT logic here, but for simplicity I’m assuming that COLOR and TYPE idoc fields are always there.

Next step is to reference my custom XSLT in Z_MATMAS03 workflow which I’m customizing:


That’s it. Now we can test the setup by sending IDOC with COLOR and TYPE fields:


..and voilà:


… the custom data fields are integrated and are available in ME Material Maintenance.

Hope this short guide will help you guys to understand how MEINT works and how it can be tweaked/customized to integrate required information from ECC to ME that is specific to your implementation.

Thanks for reading. Any advises/questions/comments and ratings will be highly appreciated.

Best Regards,
Konstantin Chernega

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Dmitry Chizhikov
      Dmitry Chizhikov

      Hello Konstantin,

      Thank you for this post.

      From ERP side, I guess, we still have to use Classes of 001 type? Am I right?



      Author's profile photo Konstantin Chernega
      Konstantin Chernega
      Blog Post Author

      Hi Dmitry,

      The article is not about ERP classes, but rather about a technic to integrate any IDOC xml field to ME and store it as Custom Data. If you are talking about standard integration of material classifications - then yes, they should be of type 001 as per Transfer of Material Classification Data SAP ME help topic.


      Author's profile photo Dmitry Chizhikov
      Dmitry Chizhikov

      Hi Konstantin,

      I agree with you, the source of custom data is probably the topic for another article!

      Thank you,


      Author's profile photo Former Member
      Former Member

      Hi Konstantin,

      thanks for this how-to.

      I tried to save three custom data fields in the routing step (Z_SETUP_TIME, Z_MACHINE_TIME AND Z_LABOUR_TIME). So I modified the ProductionOrderRequestLOIPRO03.xslt.

      Nevertheless the data is not beeing saved in the custom fields of the Routing Step.

      Can anybody help me out?

      Best regards

      Author's profile photo Filip Celikovsky
      Filip Celikovsky

      I know this post is very old, but we were dealing with the similar issue. And found a solution. As I hate unanswered questions, I will paste our findings her.

      In our case it was LOIPRO04 and we needed to save the custom field for router step (router operation). And the XML part specifying custom fields has to be in sch:RouterStepList/sch:RouterStep/sch:RouterOperationList/sch:RouterOperation node: