Inbound Process Code

[Former Member]

How can I create inbound process codes for ale?

[Former Member]

Go to Tcode WE42

WE42 is to create the inbound process code and link the message type to the inbound code.

Refer the following Link

Hope this Helps

Vinodh Balakrishnan

[Former Member]

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: "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 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, for example, MAT1.

In our case, the process code would be XAMP.

[Former Member]

Hi Friend,

The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.

3.2.1. Link Message Type to Function Module (WE57) Client independent

To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:

• Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)

• Select an entry (EG. IDOC_INPUT_ORDERS) and copy

• Type in module name Z_IDOC_INPUT_ZINVRV

• Type in basic IDoc type as ZINVRV01

• Type in message type as ZINVRV

• Type object type as IDOCINVOIC (Invoice document) - Used for workflow

• Direction should be set to 2 for inbound

• Enter and save

3.2.2. Define FM settings (BD51) Client independent

• Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)

• Click on New entries

• Type in the name of the new function module Z_IDOC_INPUT_ZINVRV

• Enter 0 for mass processing in the output column

• Save and Exit

3.2.3. Maintain process codes (WE42) Client dependent

A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.

To maintain the process code follow these steps:

• Log on to the appropriate receiving system client

• Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)

• Choose Inbound with ALE service

• Choose Processing with function module

• Click on Processing with function module and choose create icon

• Click on New Entries

• Type in process code ZINR and give it a description and save

• Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.

• Enter your process code ZINR

• Enter your function module Z_IDOC_INPUT_ZINVRV

NOTE: The next 6 steps are used in workflow error handling.

• Enter IDPKFIDCMT in object type

• Enter MASSINPUTFINISHED in End event

• Enter IDOCINVOIC in IDoc object type

• Enter INPUTERROROCCURREDFI in IDoc start event

• Enter INPUTFINISHEDFI in IDoc End event

• Enter IDOCINVOIC in Application object type

You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.

To set up the workflow area please consult the Workflow config guide.

3.3. Create inbound partner profile

For each message type you need to maintain the inbound partner profiles.

3.3.1. Maintain receiving system partner profile (WE20) Client dependent

To maintain inbound partner profiles read the document ALE configuration procedure:

• Add the message type ZINVRV with process code ZINR.

• Enter the output mode (background, immediately) for inbound processing and NO message code.

• Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.