{"id":6014,"date":"2021-04-16T23:44:43","date_gmt":"2021-04-16T21:44:43","guid":{"rendered":"https:\/\/www.ho2-gmbh.de\/news\/sap-po-generic-idoc-outbound-interface\/"},"modified":"2024-03-13T14:01:34","modified_gmt":"2024-03-13T13:01:34","slug":"sap-po-generic-idoc-outbound-interface","status":"publish","type":"post","link":"https:\/\/www.ho2-gmbh.de\/en\/news\/sap-po-generic-idoc-outbound-interface\/","title":{"rendered":"SAP PO: Generic Idoc Outbound Interface"},"content":{"rendered":"

As you can see in the picture we have a\u00a0SAP PO – Generic IDoc Outbound Interface with multiple IDoc Operation in our iFlow.<\/p>\n

Introduction<\/h2>\n

Often you have the requirement to create a set of IDoc interfaces as a kind of template implementation, especially for EDI communication scenarios.<\/p>\n

Regarding the EDI use case, you might have created a single iFlow receiving the partner’s data and separate the incoming messages over operations.<\/p>\n

For the other direction you realize the IDoc sender adapter requires a dedicated IDoc outbound interface with only one operation. So we cannot provide a single template interface with multiple operations for sending data to the partner, which is resolved here SAP PI B2B Add-on 3.0 \u2013 Outbound<\/a> by using EDI separator. I want to engage the sending system in order to build the\u00a0SAP PO – Generic IDoc Outbound Interface…<\/p>\n

My workaround is inspired by the blog post “Michal\u2019s PO tips: How to send messages directly to AEX (ICO) \u2013 adapter independent \u2013 SOAPUI version”<\/a> to implement the BAdI IDOC_XML_ENVELOPE_OU in order to wrap the XML IDoc into the SOAP envelope and adding the XI headers.<\/p>\n

If you are also searching for a solution to either…<\/p>\n

    \n
  1. provide generic IDoc outbound interfaces<\/li>\n
  2. create acknowledgements per partner profile and not per IDoc sender channel (additional adapter module required for ALEAUDs)<\/li>\n
  3. setup a simple solution to create the serialization context for IDocs (based on Xpath)
    \n-> Configuration instead of function module development<\/li>\n
  4. have a generic and single HTTP endpoint for XML-HTTP IDoc ports instead of creating multiples (one endpoint for each SAP PO outbound interface)<\/li>\n
  5. avoid header mappings for outbound interfaces in order to set the XI Party (KB: 1941832 – Resolve logical receiver party<\/a>) or replace the virtual receiver L<\/strong>ogical S<\/strong>ystem (KB: 2728276 – Resolve logical receiver service for LS receiver<\/a>)<\/li>\n
  6. send the IDoc to a dedicated iFlow having a virtual receiver, which could e.g. represent a dedicated SAP process. This helps to separate IDoc iFlows into business responsibilities and you could create IDoc iFlows without any dependency to any other IDoc interface.
    \n(I know, it increases the amount of point2point interfaces, but if you ask business, I’m not sure they are interested in using as many integration patterns as possible \ud83d\ude42
    \n-> Less discussion about impact and regression testing after changing existing interfaces<\/li>\n
  7. use HTTP based communication instead of TRFC \/ ressource adapter configuration for sending IDocs, but still want the full\/better SAP PO functionality (see restrictions) compared to the restricted default XML-HTTP port behavior
    \nor<\/li>\n
  8. overcome the 16 character serialization context length<\/li>\n<\/ol>\n

    …this BAdI implementation and some little customizing might help you to achieve it with only a single iFlow.<\/p>\n

    BTW: No metadata is required anymore if you send it over HTTP-XML…<\/p>\n

    Please bear with me in case you find issues regarding the ABAP part,I\u2019m still on beginner level.
    \nI’m happy receive your ideas\/use cases and feel free to provide any optimization proposals.<\/p>\n

    Warning: This BAdI is not yet used in production. So adjust it to your needs and test it carefully before using it in productive <\/b>environments<\/b> – No warranty for <\/b>correctness, performance and no<\/b> support can be provided! This is no SAP code. So it is 100% in your responsibility to troubleshoot and correct it in case of any issue.<\/b><\/p>\n

    Restrictions<\/h2>\n