Inbound
Processing: Procedure
Purpose
Configure inbound processing when you want to implement a new business process will receive data by IDoc. An example is EDI inbound processing of standard orders.
Prerequisites
Only activate the Type Linkage for the IDoc Interface once, because an event is always triggered when an IDoc is received (exception: port type "tRFC"). This takes place in Customizing, activity Activate event-receiver linkage for IDoc inbound processing.
Process Flow
...
1. The inbound IDoc is linked to the required processing type using the process code in the partner profiles. You can decide whether a workflow or a function module is triggered when an IDoc is received.
The process
codes supplied with the standard system are already assigned to workflows or
function modules. You can display this assignment with SAP Menu
®
Tools
®
IDoc Interface/ALE
®
Development
® IDoc ®
Inbound Processing
®
Inbound Procedure
Code.
This is also the initial screen for new assignments when you want to define
new IDoc types or processing types. For further
information, see
Define New IDoc Types.
A vendor receives a purchase order for a material using an IDoc of type ORDERS01. The vendor has assigned the function module IDOC_INPUT_ORDERS, which converts the IDoc data to the corresponding application data, to the ORDERS message using the process code ORDE. The vendor, therefore, selects the direct path using a function module.
There are
IDoc types for which inbound processing only takes place in NetWeaver, for
example TXTRAW02. These IDoc types are only processed by workflow. The
corresponding tasks are grouped together in task group TG70000016. Inbound processing by workflow in logistics is
located in task group TG20000011. Task groups make the search for tasks in the
Business
Workflow Explorer.
2. For exception handling in inbound processing you must assign the possible agentsto the corresponding tasks. You have the following alternatives:
¡ You must classify all tasks as general tasks in IDoc Customizing.
¡ You maintain the allocation for each individual task using transaction PFTC_DIS. The section Exception Handling: Procedure describes which tasks are used.