Purpose of Process Codes (SAP Library - IDoc Interface / Electronic Data Interchange (BC-SRV-EDI))

Purpose of Process Codes

Definition

Another name for a specific process, for example function module or workflow. IDocs are read or written in this process.

Use

In the partner profiles, the processing is never addressed directly but rather always via a process code. You can therefore replace an old process with a new one for any number of partners by assigning the existing process code to the new process.

Two types of process code are used in conjunction with the partner profiles:

Outbound Process Code - if you are using outbound processing under Message Control, the IDoc is generated in the IDoc interface. The process code names the relevant function module.

Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.

If you do not know what process code is relevant for your business process, but you know the message type, then you can display the process code defined for this message type: Choose Documentation ® Process codes in the initial node of the IDoc interface or use the F4 Help in the partner profiles after you have entered the message type.

There are also the process codes for exception handling:

System Process Code - names the workflow which is triggered in inbound or outbound processing when an exception occurs.

Status Process Code - names the exception workflow which is triggered when an incorrect status is returned by the external system.

These two types are configured centrally and not on a partner-specific basis and therefore do not have to be maintained when a new process is defined. They were introduced for the sake of completeness, so that each process in the IDoc interface is addressed via a process code.