Show TOC

Object documentationAim and Purpose of Process Codes

 

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 using a process code. You can therefore replace an old process with a new one for any number of partners by simply 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

    This names the function module or workflow which reads the IDoc data and transfers the data to the application document.

    Note Note

    If you do not know what process code is relevant for your business process, but you know the message type, you can display the process code defined for this message type: Choose Start of the navigation path SAP Menu Next navigation step Tools Next navigation step IDoc Interface/ALE Next navigation step Services Documentation Next navigation step Process Codes (WE64) End of the navigation path or use the F4 help in the partner profiles after you have entered the message type.

    End of the note.

There are also the process codes for exception handling:

  • System process code

    This specifies the workflow that is triggered in inbound or outbound processing when an exception occurs.

  • Status process code

    This specifies the workflow that is triggered during status processing when an exception occurs.

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 using a process code.