Idoc not getting posted into XI

[Former Member]

Hello Experts,

I am trying IDoc-XI-File senario...

I have configured, ALE on backend system. Configured IDX1 and IDX2 in XI system.

At sender the Idoc has been sent without any errors.

But when I check in XI using SXMB_MONI there are no messages. Idoc is not getting posted into XI.

Please suggest as I am struck at this point. I am using XI 7.0

Thanks

Suma

[Former Member · Accepted solution]

Hi,

check the status of idoc in WE05 in R3 system.

See the status code and find its description in we47 and plz paste the status...

regards

PrasHant

[Former Member]

Thanks for your valuble replies

[former_member189440]

Hi Suma,

first u have to assign the business system of scenario to the ABAP technical system in your SLD.and then assign your logical system(receiver).then u will get the required output.

[former_member181962]

Take the idoc number.

Goto IDX5 transaction of the XI system.

Give the Idoc number in the selection screen and the date on which it was triggered and execute.

Then double click on the message id .

You will be taken to the SXMB_MONI report.

Regards,

Ravi

[aashish_sinha]

Hi,

Log in to sender system, go to transaction WE19 (test tool to generate IDoc), generate IDoc of the required message type

In the following screen follow the steps : Give Receiver and Sender System Info(Port, Partner No, Port Type and Message Type) and click on Continue

Now put some entry into the IDoc before you send

-Now click on Standard outbound processing button then : Click on continue again continue. In the last window Idoc sent to Sap system or external program information should appear else you may have to check Receiver and Sender System Info(Port, Partner No, Port Type and Message Type) for valid entry.

Execute Transaction WE05; enter correct date/time frame and logical message type. Hopefully the Idoc Status should be 3 (successful), if not check the status code and correct the error and reprocess the message. You can use transaction code SM58 with enter correct date/time frame and execute. Here if it is successful then nothing should be available in the list else it will show the relevant Status / Message. WE02 transaction can be used to get the error info.

Log in to Xi system and execute transaction SXMB_MONI and check for the XML messages. Use your source and destination system to filter messages

Check the destination directory, it should have file with the name specified. Check the file; it should have data for all segments

Hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Hi,

Have to check all the discussions still if ur getting any error please update the thread to help u out.

Regards,

Phani

[Former Member]

In WE05 the satus is 03 and in WE42 it sates as "IDoc passed to Port ok".

Please check the following settings:

1. So you see a green flag in TS WE02 in your R/3 system?

Ans: Yes

2. Are there no errors in TS SM58 in your R/3 system?

Ans: Yes

3. No message showing in SXMB_MONI?

Yes

Check WE02 in XI system. If the message shows there, change the engine type of the XI system to HUB using TS SXMB_ADM --> Integration Engine config --> Change specific configuration data

There is no message shown in WE02 in XI

[Former Member]

Please open TS IDX2 in your XI system, delete the IDoc metadata for the correct system and resend the IDoc. Is the metadata now updated automatically?

Is the business system in your SLD correctly configured?

Does the RFC destination in TS SM59 (R/3) point to the correct XI system?

[Former Member]

Hey,

In your XI system check in transaction SU53.

If it shows authorization succesful than its fine,

But, if it shows that certain objects are not assigned to the user(the one you have mentioned in RFC destination on R3 side) than assign those objects to the user.

reward points if useful.

regards,

Milan.

[Former Member]

Hi,

Kindly verify the ALE steps that you have performed...

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)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

Step 6)

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 7)

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.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

SAP r3

sm59(status check)(no message)

WE02(status check)

WE05(status check)

BD87(status check)

Xi

IDx5(Idoc check)

SU53(authorization check)

Reward points if helpful...

PrasHaNt

[former_member556603]

Hi Suma,

Once u go through the duscussions...

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

Thanks,

Satya

Edited by: SATYA KUMAR AKKARABOYANA on Jun 2, 2008 1:30 PM

[Former Member]

Please check the following settings:

1. So you see a green flag in TS WE02 in your R/3 system?

2. Are there no errors in TS SM58 in your R/3 system?

3. No message showing in SXMB_MONI? Check WE02 in XI system. If the message shows there, change the engine type of the XI system to HUB using TS SXMB_ADM --> Integration Engine config --> Change specific configuration data