Need immediate help: Idocs not showing up in productive PI

[Former Member]

Hi gurus,

we are trying to go productive today with our pi 7.0 server. now we are facing the problem, that the idocs from our productive system don't get into the pi. in the productive erp system we can see them leaving with green status, but in sxmb_moni they don't show up. can anyone please help?

regards,

michael

[Former Member · Accepted solution]

OK, thanks, but this didn't help either. We are still not getting the idocs in pi. would you say it's rather a problem in pi or in R/3?

Regards,

Michael

[Former Member · Accepted solution]

hi michael

tRFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

To check the status of the tRFC calls, choose

Tools -> IDoc Interface/ALE-> Administration -> Monitoring->ｮ Troubleshooting -> RFC Queue (SM58) and specify any additional selection criteria.

basically The program RSARFCEX restarts unsuccessful tRFC calls.

regards

kummari

[Former Member · Accepted solution]

This is a problem with R/3 configuration. Check the XI configuration guide part: "Configuring Business Systems". Re-check if all the steps are in place.

[Former Member · Accepted solution]

I am not sure about it but you can have a look. In your sending R/3 system use tcode SXMB_ADM and there under Integration Engine Configuration check if the Role of Business System has been assigned as Application system also check if the Corresponding Integ. Server there is an entry or not e.g. dest://abc

[Former Member]

hi michael,

pls check the below blog for some errors in XI production environment

hope it helps you

regards

kummari

[Former Member]

hi michael,

Go to transaction SM59 --> TCP/IP Connections --> AI_RUNTIME_JCOSERVER and test the connection.

If there are errors, try deleting and recreating the same

Alternatively, you can also do a restart of the J2EE engine

regards

kummari

[Former Member]

What exactly does this report do? Do I have to run it in R/3 or in PI?

[Former Member]

hi,

The program RSARFCEX will work if executed on the system from which tRFC call is originated (R/3).

In receiving system unless it will be in qRFC or it is processed in queues like in XI,you won't see any thing

In the standard SAP system, if tRFC errors occur, a background job is generated to re-establish the connection. In certain circumstances this could result in a large number of background jobs being started that completely block background processing.

regards

kummari

[Former Member]

IDOC Adapter: Error reading own Business System ID

[prateek]

Check the following transactions in XI server. SLDAPICUST

and SLDCHECK

Regards,

Prateek

[Former Member]

Thanks for the fast answers!! In SM58 we are getting errors, the message number is: SR053

What could that be?

[santhosh_kumarv]

what is the Status Text of the error message?

[Former Member]

hi,

Run the Report RSARFCEX which is part of the standard jobs that the basis should schedule to solve temporary error due e.g. to network problems or unavailability of the target system (this sometimes happen when you link a sap system with a non sap system via idoc).

regards

kummari

[santhosh_kumarv]

Hi,

1. Check in SM58 of R3.

2. Check if the RFC Destination is pointing to the correct PI system in R3 and also using the correct logon credentials.

Thanks

SaNv...

[Former Member]

Few things to cross check.

1. Have you imported the IDOC in PI

2. Have you uploaded the metadata in PI by suing tcode IDX2.

Check by tcode IDX5 in you PI system by entering the IDOC number.

[prateek]

Chech transaction sm58 in R3 for errors.

Regards,

Prateek