Skip to Content

ALE-IDOC is one of the best proven and acceptable terminology through which communication (passing of information) is possible between two different SAP systems. However complete end-to-end scenario (Outbound – >  Inbound process) works in an asynchronous mode which sometime leads to a difficult situation where in tracking or monitoring of error related to IDOC posting becomes cumbersome.


For better monitoring and automating error tracking process in Inbound IDOC scenario, SAP has provided flexibility where in a workflow can be integrated with the inbound process .If an error occurs during the inbound process till application posting, WF will notify appropriate agent about the same or any other specific activity can be carried out based on the requirement


So let’s map such kind of requirement with a solution in SAP system and understand the process detailed manner.

Requirement
Note: Readers of this article should have basic knowledge on ALE-IDOC & Workflow for better understanding of the scenario.


A Interface needs to be developed based on ALE-IDOC terminology for Purchase Order. End-to-end scenario starting from outbound process through message control & output type method till inbound process of application posting by Function Module.

Let’s say :

               Sending system: ECCCLNT800 (Client – 800)

               Receiving system: ECCCLNT811 (Client – 811)

               IDOC Basic Type: ORDERS05

               Message Type: ORDERS

Objective is to trigger an IDOC from client 800 through message control process and receiving the same at client 811.Triggering workflow if an error occurs during application posting after receiving the IDOC.


Outbound Configuration


A: Maintain and configure message control details in t-code NACE.

     Check for condition records & output type records for NEU

    

Medium in processing routine & partner function should be ALE

B: Assumed that required configuration for logical system creation and it assignment to client is done in t-code SALE.


C: RFC destination with a name ECCCLNT811 is created and tested in SM59 which connects to client 811.


D: Port A000000058 is created in t-code WE21 with above RFC destination.


E: Partner profile maintenance: WE20. Message type ORDERS is added to the outbound parameter list


IDOC basic type and correct port provided as shown below


Under message control tab below entry is maintained.


                     EF: Application Area

                     NEU: Standard OUTPUT type for purchase order

                     ME10: OUTBOUND process code for Purchase orders.


Thanks….happy learning

Regards

Ansumesh

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply