Show TOC

Creating an Inbound Process CodeLocate this document in the navigation structure

Procedure

The inbound process code, that is, its attributes, indicates how an inbound IDoc is processed. A process code has the following attributes:

  • Processing type (for example, should the inbound function module be called immediately, or should a workflow or work item be started?);

    Standard way: "ALE, function module called directly"

  • Name of inbound function module;

  • Error processing attributes (objects and events; see the section on objects, and so on, 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 SAP 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 typically not 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, for example, MAT1. In our case, the process code would be XAMP.