topic Re: Inbound Idoc in Application Development and Automation Discussions

Inbound Idoc

Former Member — Mon, 07 Jan 2008 19:43:53 GMT

Hi,

I am having problem with Inbound IDoc. I am sending data from another system to R3. In the other system the status = 03.

Coming to R3, I am not able to see any Idoc in WE05 itself. Any ideas? However, this worked some days back but not now.....

Thanks.

Re: Inbound Idoc

Former Member — Mon, 07 Jan 2008 20:11:45 GMT

give the same dates in we05, when u ran that idoc date.

Re: Inbound Idoc

Former Member — Mon, 07 Jan 2008 20:12:50 GMT

See what happened to the IDOC in your Bridge, or if Bridge is down.

Vinodh Balakrishnan

Edited by: Vinodh Balakrishnan on Jan 7, 2008 3:13 PM

Re: Inbound Idoc

Former Member — Mon, 07 Jan 2008 20:18:31 GMT

Vinod:

How to see if the bridge is down?

Re: Inbound Idoc

Former Member — Mon, 07 Jan 2008 20:21:44 GMT

You say that the status is just '03', which is passed to port.

Try to run program 'rbdmoind' and change the IDOC status to '12', which means dispatch is OK.

Times this might help.

Worst case scenario, bring the bridge down and start them again.

Vinodh Balakrishnan

Re: Inbound Idoc

Former Member — Mon, 07 Jan 2008 20:45:50 GMT

In the receiving system, I executed the program, and it listed the IDocs that have not yet been sent.THose are the ones whose status = 03.

Now, How do I change the status = 12 and how do I stop and run the Bridge?

Re: Inbound Idoc

Former Member — Tue, 08 Jan 2008 05:21:04 GMT

hi,

first run the program RBDIMOND.if u get status -12.

if it is still 03 then check trfc log sm58.

if u found any entries then test the RFC destination and fix the problem and restart the failed trfc entries.

if u found no entries check system log sm21.

Reward if it is usful,

Thanks,

Srikanth.A

Re: Inbound Idoc

Former Member — Wed, 09 Jan 2008 16:20:19 GMT

Srikanth:

I checked SM58 and it says ABAP/4 Open SQL array insert results in duplicate database records.

Program RSEOUT00

Any idea on how to fix this issue?

Re: Inbound Idoc

Former Member — Thu, 10 Jan 2008 06:28:44 GMT

HI Naga,

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