ALE INBOUND Process Code

Question

Hi,
      In ALE INBOUND Process Code Apart from the Function Module name, what are the important things to be filled up while creating that InBound process code in WE42. What is the importance of those? what is the importance of Object Attributes in that?

Answer 1

Hi Mahesh check this may be useful to  you
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.
Link Message Type to Function Module (WE57) Client independent
u2022 Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Define FM settings (BD51) Client independent
u2022 Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
u2022 Click on New entries
u2022 Enter 0 for mass processing in the output column
u2022
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:
u2022 Log on to the appropriate receiving system client
u2022 Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
u2022 Choose Inbound with ALE service
u2022 Choose Processing with function module
u2022 Click on Processing with function module and choose create icon
u2022 Click on New Entries
u2022 Type in process code XXXXXXX and give it a description and save
u2022 Now you are asked to Please maintain codes added in ALE entry methods, enter and choose XXXXXX and copy it. You should choose a FM similar to your one.
u2022 Enter your process code XXXX
u2022 Enter your function module XXXXXX
NOTE: The next 6 steps are used in workflow error handling.
u2022 Enter IDPKFIDCMT in object type
u2022 Enter MASSINPUTFINISHED in End event
u2022 Enter IDOCINVOIC in IDoc object type
u2022 Enter INPUTERROROCCURREDFI in IDoc start event
u2022 Enter INPUTFINISHEDFI in IDoc End event
u2022 Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object XXXXXXXX, 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.
Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
u2022 Add the message type XXXXX with process code XXXX.
u2022 Enter the output mode (background, immediately) for inbound processing and NO message code.
Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
You can find all the inbound and outbound processcodes in we64.
Regards,
SMS.