Inbound processing.

[Former Member]

Hi experts,

what are the steps invloved in Idoc inbound processing?

A sample process code to just extract data from the destination system .

[Former Member]

http://www.idocs.de/

http://www.sapgenie.com/ale/whitepaper.htm

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm

http://www.sappoint.com/ppt/ale.ppt

below details might help you.

WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.

WE05 View IDocs

WE19 EDI test tool. Use to test inbound Function module changes.

WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing

WE30 Create IDoc extension type

WE31 Segment create

WE57 Assign function module to logical message and IDoc type

WE60 IDoc type documentation tool

WE82 Link Release detail to Extension IDoc Type

BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)

BALA ALE Application Distribution

BALM ALE Master Data Distribution

ALE and Idoc technologies by Arvind Nagpal. There are also some interesting articles by Arpit Nigam in SDN and Kevin Wilson in www.sapgenie.com

reward points for helpful

[Former Member]

Sunitha,

check this below link.......... it gives a good idea for you... steps are clearly explained

http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

[Former Member]

Hi,

Inbound processing is a runtime component of XI’s ccBPM that links the Integration Engine to the

Business Process Engine. It defines the way how XI messages are handed over to receive steps of process

instances. The messages can thereby either start a new process instance or can be bound to a running

process instance using a correlation.

The usage of inbound processing with buffering may impact the delivery of messages the following way:

�� Even if the process instance does not provide a receive step at the present stage of the execution,

the message might be buffered and delivered later to the process instance.

�� If a process instance has long running open correlations, messages might be delivered to the

process instance being buffered even though the process instance does not provide any further

receive step. In this case, if the relevant process has not been carefully designed by the developer,

messages might not be delivered anymore! Messages not being delivered to a running process

instance can be monitored in CCMS (Unprocessed XML Messages). Narrow down the duration

of correlations to the strict minimum is a good development practice.

regards,

vasavi.

reward if helpful.

[Former Member]

Hi Sunitha,

For Inbound ALE Configurations: (Example)

Create Idoc segments – Transaction WE31.

Idoc segments

zmara02

zmatk01

zmarc02

zmarm02

Zmara02

-

---

Fields Data Length Data element

matnr 18 matnr

matkl 9 matkl

meins 3 meins

brgew 15 brgew

Zmatk01

-

---

Fields Data Length Data element

matnr 18 matnr

maktx 40 maktx

spras 1 spras

Zmarc02

-

---

Fields Data Length Data element

matnr 18 matnr

werks 4 werks

bwtty 1 bwtty_d

Zmarm02

-

---

Fields Data Length Data element

matnr 18 matnr

umren 6 umren

umrez 6 umrez

volum 15 volum

Create Idoc type – Transaction WE30.

Idoc type Idoc segments

Z_mat_idoc Parent - zmara02

Child - zmatk01

zmarc02

zmarm02

Create Message Type – Transaction WE81.

Message type

z_msg_type_01

Assign Message Type to Idoc type – Transaction WE82.

Idoc type Message type

z_mat_idoc z_msg_type_01

Create a function module through SE37

z_idoc_input_type_01

Assign characteristic of function module BD51

Assign fn module to Idoc type and Message Type WE57

Idoc type Message type Fn Module

z_mat_idoc z_msg_type_01 z_idoc_input_type_01

Create Inbound process code and assign inbound function module – Transaction WE42.

Process code Inbound function module

zmat z_idoc_input_type_01

Create a distribution Model - Transaction BD64

Create distribution model for distribution of messages from cpb105_01 to cpa105 with the message type of z_msg_type_01.

Update inbound parameters of the Partner profile – Transaction WE20

For the Logical system A for the above message type update the partner profile

inbound parameter and specify the process code of ZWCH..

For Outbound ALE Configurations: (Example)

IDoc definitions and necessary ALE configurations settings for the outbound .

Create Idoc segments – Transaction WE31.

Create Idoc type – Transaction WE30.

Create Message Type – Transaction WE81.

Assign Message Type to Idoc type – Transaction WE82.

Create a distribution Model - Transaction BD64

Update outbound parameters of the Partner profile – Transaction WE20

For the Logical system A for the above two message types update the partner profile.

For each message type specify the Port and the IDoc types.

( Note : Port definition need to maintained using transaction WE21 and

it has to be defined as a Transactional RFC port with RFC destination for

system specified, which need to be maintained using SM59 ).

Regards,

Azhar.