Creating an Inbound Processing Code (SAP Library

Creating an Inbound Processing Code

The inbound process code can be thought of as the name given to the ways and means of processing an incoming IDoc, i.e. the process code’s attributes. A process code has the following attributes:

Processing type (e.g. should the inbound function module be called immediately, or should a Workflow or work item be started?);

- Standard: "ALE, function module called directly"

Name of inbound function module;
Error processing attributes (objects and events; see the section on objects etc. for error handling);
Application object type used for ALE links;

- the object type created or changed by the inbound function module. Example: An inbound ORDERS IDoc, containing a customer’s purchase order, creates a customer order in the receiving R/3 System. Here the application object type is BUS2032, the object type for customer orders in the BOR (Business Object Repository).

The application event to be triggered (dealt with in the section on advanced techniques) is not generally used.

Example

For an example, have a look at the process code MATM used for material master data.

Naming Convention

The naming convention for process codes is to use the first four letters of the message type to which it applies. Example: MATM for message type MATMAS; if there is a conflict, use the first three letters and a number, e.g. MAT1.

In our case, the process code would be XAMP.