Outbound/Inbound Trigger Prog.?

[Former Member]

Hi Experts,

I know the Selection Prog.(IDoc_Outbound_<IDoctype>) in Outbound direction and Posting Prog.(IDoc_Inbound_<IDoctype>) in Inbound direction, then,

1-What is Outbound Trigger Program, Does ABAPers writes it? One Prog. name as example pls.!

2-1-What is Inbound Trigger Program, Does ABAPers writes it? One Prog. name as example pls.!

ThanQ.

[Former Member]

The IDOC_OUTPUT* and IDOC_INPUT* programs are linked to the message type and idoc type via process code. WE82 links message type to idoc type, and WE64 links message type and process code. Message type, idoc type and process code are linked together in the partner profile for a particular inbound / outbound idoc process.

Now as for the triggering of Idoc, it works differently in inbound and outbound cases.

<b>Methods of Outbound Idoc triggering</b>

1. If the IDoc is created automatically through output via transaction (like edi order response, or invoice). Then the triggering program will be EDI_PROCESSING for EDI and ALE_PROCESSING for ALE scenarios. These programs read the NAST entry (created during output proposal) for the output type and then determine the correct outbound parameters from a unique partner profile matching the NAST record and then trigger the outbound process code.

2. We can trigger an outbound IDoc using MASTER_IDOC_DISTRIBUTE. Here we need to create the IDoc data body within the program and pass on receiver, sender, message type parameters to MASTER_IDOC_DISTRIBUTE which then creates it.

3. Manually creating a preconfigured IDoc message via transaction WE19

<b>Methods of inbound IDoc triggering</b>

Inbound IDocs are triggered by either external systems (edi, wms etc) or can be triggered by inhouse applications in SAP to post a application document.

1. EDI_DATA_INCOMING can create a IDoc from a file on the OS layer. It just needs a IDoc flat file containing control and data records, it will create an Idoc from it if the control record successfully matches a inbound partner profile parameters.

2. IDOC_INBOUND_ASYNCHRONOUS can be triggered by external/internal programs to creae IDoc withing SAP, whereas IDOC_INBOUND_SYNCHRONOUS can be used by inhouse SAP programs to create inbound Idoc.

3. WE19 can create and post an existing inbound Idoc to application

[Former Member]

ThanQ Vishnu.

1-So, in real world(on an average), Which ones are mostly used, in either directions on general scenarios?

2-For instance, Can I take like, MASTER_IDOC_DISTRIBUTE for outbound and IDOC_INBOUND_ASYNCHRONUS for inbound as Triggering Prog.s?

ThanQ.

Message was edited by:

Srinivas

[Former Member]

Hi Experts,

Any response from any one?

ThanQ.

[Former Member]

It depends on business case:

Case 1: A customer wants a order acknowledgment for his order, another wants a invoice in EDI formats. In this case you will enable IDoc output through output determination in VA01 and VF01 transactions, you will assign ORDERS, INVOIC message types. The triggering function module would be EDI_PROCESSING

Case 2: A business wants to distribute its material data from its main ERP system where all materials are maintained to non SAP warehouse management systems, price cataloging systems, all of which require some part of material master. For this you will enable ALE, create distribution model with the other systems as receivers, generate partner profiles and activate change pointers, which will trigger MATMAS idoc type whenever important fields on material master are changed via MM* trxns. Here internally you are using MASTER_IDOC_DISTRIBUTE or externally BD10 transaction.

Case 3: You are getting EDI messages from your business partners like payment advices, orders etc. You would need to create IDocs and post the documents to respective transactions like VA01 etc. You are getting the EDI message in a file and map it to ORDERS idoc file on OS. Now you can use EDI_INCOMING data, and if all other configurations like partner profile, inbound process code, message and idoc types are setup, you will be able to post the payment advice or create a sales order

Case 4: You have to post a transaction internally within the system, then you will use IDOC_INBOUND_ASYNCHRONOUS or SYNCHRONOUS.

Case 5: You want to directly trigger SAP from an external system, posting an inbound IDoc, you would need to call IDOC_INBOUND_ASYNCHRONOUS via tRFC connection and ALE

So it all depends on what the business requirement is.

Case 3.

[Former Member]

ThanQ Vishnu.

[Former Member]

Methods of inbound IDoc triggering

Inbound IDocs are triggered by either external systems (edi, wms etc) or can be triggered by inhouse applications in SAP to post a application document.

1. EDI_DATA_INCOMING can create a IDoc from a file on the OS layer. It just needs a IDoc flat file containing control and data records, it will create an Idoc from it if the control record successfully matches a inbound partner profile parameters.

2. IDOC_INBOUND_ASYNCHRONOUS can be triggered by external/internal programs to creae IDoc withing SAP, whereas IDOC_INBOUND_SYNCHRONOUS can be used by inhouse SAP programs to create inbound Idoc.

I have a query regarding the above .Please le tme know in detail how this function will be called .What setting do we need to make related to Startrfc if the idoc is received in idoc format and what configurations are needed for this setup