IDoc status

[Former Member]

Dear Experts,

We have created one custom type IDoc.

If we trigger, Idoc status is reaching 03 ( Data passed to Port OK).

But what has to be done to make Idoc reach the status 12 ( Dispatched OK)?

What checks should be done from RFC connection configuration side?

Kiran.

[Former Member]

Dear Experts,

We have created one custom type IDoc.

If we trigger, Idoc status is reaching 03 ( Data passed to Port OK).

But what has to be done to make Idoc reach the status 12 ( Dispatched OK)?

What checks should be done from RFC connection configuration side?

Kiran.

[Former Member]

Hi Kiran,

1) Idoc status is reaching 03 ( Data passed to Port OK) - This status really not ensures that data is received at the receiver system. This means data is just delivered to RFC. If User ID has sm problems and because of which data is stuck still the status will be displayed as 03.

2) status 12 ( Dispatched OK) - If everything goes out well from the sender and data is pushed out status changes to 12. This doesn't mean that IDOC succsfully posted in receiver.

Regards

Shital

[Former Member]

Hello,

Execute the report RBDMOIND . If the idoc is sent to destination system successfully the status will become 12.

In production scenario this report is scheduled to run in background periodically.

Regards

Arindam

[Former Member]

Hi,

Execute the program RBDMOIND. yoc can check the corresponding log in SM58.

Thanks,

Asit Purbey.

[Former Member]

hi,

use this link..

.

[Former Member]

Kiran,

12 is not a mandatory status that you need to have. If you are able to get 03 status, its well and good which implements the functionality of the status 12.

03 status signifies that the Idoc is already in middlware. Now, you need to check either the middleware or the target system

Hope you got it.

Thanks,

Babu Kilari