Idoc sender issue

[Former Member]

Hi,

I have an issue in Idoc sender scenario.

The flow is Idoc to BPM to Flat file.

Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.

Which transaction to use to trace Idoc in XI?

I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.

Regards,

Anirudh.

[Former Member]

Hi,

In Xi level...if you want trace IDOCS use IDX5 tcode

R/3 levels use we05 and we02 for Displaying IDOCS

rEGARDS

[samiullah_qureshi]

Hi

Go through following ALE step, check whether you missed any of these steps:

Steps for ALE settings:-

Steps for XI

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the R3 system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto IDX1.

Create a new port.

Give the port name.

Give the client number for the R3 system.

Select the created Rfc Destination.

Step 3)

Goto IDX2

Create a new Meta data.

Give the Idoc type.

Select the created port.

Steps for R3.

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the XI system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto WE21.

Create a port under transactional RFC.(R3->XI)

Designate the RFC destination created in prev step.

Step 3)

Goto SALE.

Basic settings->Logical Systems->Define logical system.

Create two logical systems(one for XI and the other for R3)

Basic settings->Logical Systems->Assign logical system.

Assign the R3 logical system to respective client.

Step 4)

Goto WE20.

Partner type LS.

Create two partner profile(one for XI the other for R3).

Give the outbound or inbound message type based on the direction.

Step 5)

Goto WE19

Give the basic type and execute.

fill in the required fields.

Goto IDOC->edit control records.

Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

Click outbound processing.

Step 6)

Go to SM58

if there are any messages then there is some error in execution.

Goto WE02.

Check the status of the IDOC.

Goto WE47.

TO decode the status code.

Step 7)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

Regards

Sami

[former_member556603]

Hi,

Which transaction to use to trace Idoc in XI?

*Transaction to use to trace IDOC is : IDX5 for IDOC monitoring

• IDX2 Meta Data Overview in IDoc Adapter*

WE05 IDoc Lists

And check the Payload in SXMB_MONI

Some IDOC Transactions:

WE60 Documentation for IDoc types

BD87 Status Monitor for ALE Messages

IDX1 Port Maintenance in IDoc Adapter

IDX2 Meta Data Overview in IDoc Adapter

WE05 IDoc Lists

WE02 Display IDoc

WE19 Test tool

WE09 Search for IDocs by Content

WE20 Partner Profiles

WE21 Port definition

Thanks,

Satya Kumar

Edited by: SATYA KUMAR AKKARABOYANA on May 12, 2008 2:31 PM

[Former Member]

hi,

you can use IDX5 tcode in xi to resolve your issue

go thru the below links for complete idea

Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

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

http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp

http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm

idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi

idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping

IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii

pls reward points if solution found helpfull

regards

chandra.k

[Former Member]

Hi

IDX5 -> monitocr idoc adapter

WE02 - Transaction for idoc list display

WE05 - Transaction for idoc list display

SM59 - To create RFC destination

cheers

Edited by: vemuganti naga phalguna on May 12, 2008 1:38 PM

[Former Member]

Hi,

The transaction to check the status of the idoc in XI system is "IDX5".

And also you can test the idoc in transaction "WE19"..........

You can check the idoc processing status in WE02, WE05, SM58.........

Hope this will solve u r problem

Regards

Sai

Reward with points if helpful

[Former Member]

You can check the payload of the message in SXMB_MONI or through IDX5 for IDOC monitoring.

[prateek]

Check sm58 at R3

Regards,

Prateek

[Former Member]

Hi,

idx5,u can trace.

Regards,

rao