Inbound Idoc issue

[Former Member]

Hi ABAPers,

I am facing an issue in receiving the inbound idocs.

I have done the following operations:

1. Created a segment type similar to that in the sending system & released it.

2. Created an IDoc type similar to the one in the sending system & released it.

3. Created a message type similar to that in sending system.

4.Assingned the IDoc type to the message type.

5. Added the inbound function module name through BD51.

6.Assigned Basic type & message type to FM name.

7. Created an inbound process code,gave "Process by Function module" as process type & the FM name.

8. Assigned the logical message to the process code.

9. Added the message type to the partner profile's inbound parameters & gave the process code in the inbound options.

The parnter profile is the profile on the sending system.

Please let me know if I have missed any step in the configuration. Now, in the sending system, the Idoc status is 03 but there is no Idoc coming to the recieving system.

Please assist.

Thanks & Regards,

Prakash.K

[Jay71]

Hi,

Did u configure the sender and receiver ports in both source and destination systems.

if u did this then what is the control segment containing in the source system where the idoc status is 3. it will show you the target partner as well.

Jayaram

[Former Member]

Hi Jay,

The ports configurations seems to ok because another person also created Idocs using similar ports & partner profiles. The Idocs are going fine in his object.

Also, the sender & reciever info is displayed in the control segment of the Idoc.

Thanks & Regards,

Prakash.K

Edited by: Prakash K on Jul 21, 2009 7:36 AM

[Former Member]

Hi,

please go to sender system and check whether IDoc has been send correctly. State 03 just means "Data passed to port". So look into SM58 if any IDoc stuck in the RFC layer. Normally IDoc state should be 12 "Dispatch okay". A Report scheduled in sender system normally converts the IDoc states from 03 to 12.

If IDoc was sent successfully from sender system it must be in your receiver system. Check BD87 / WE02.

Regards,

Kai

[Former Member]

Hi,

No good yet. Its not in BD87 or WE02. I checked the RFCs too. There is no entry for my IDOC there.

[Former Member]

hi,

1. goto sender system

2. open IDoc in Status 03

a) Check Port in the IDoc (maybe u used an fileport or something else)

b) Check Receiving System through port.

3.) Check Longtext of Status 03 and check tab statusdetails.

what is inserted in the 1. Parameter ?

4.) Check Table: ARFCSSTATE and look for your TRFC ID. If found look into SM58 tcode, too.

In case you are using QueuedRFC - check SMQ1 transaction, too.

Good luck,

Gordon

Edited by: Gordon Breuer on Jul 21, 2009 4:00 PM

Edited by: Gordon Breuer on Jul 21, 2009 4:02 PM

[Former Member]

Hi Gordon,

I have verfied that tRFC port is used.

I tested the connection for the port. Its working fine.

I checked the 1st Parameter in Status Details : it read 0AED649613804A65B61E02FE. No clue what this means??

I checked the entry in ARFCSSTATE table. No entry exists in it.

Please advice.

Thanks & Regards,

Prakash.K

[Former Member]

Hi All,

The problem is solved. I must apologize to all of you for this. It turns out to be a commit work problem. I did not give commit work after Master_Idoc_Distribute. However, I could see the Idoc in the outbound Idocs in WE02.

Dunno how??

Anyways, this definitely added more knowledge into my repository. Thanks all for the help.

Regards,

Prakash.K