Error : Processing is overdue

[venkatraju_m]

when loaing data to psa from SAP R/3 .

RSMO - 7777 From 0 and request status is showing Yellow.

complete message given below.

Errors while sending packages from OLTP to BI

Diagnosis

No IDocs could be sent to BI using RFC.

System Response

There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.

Further analysis:

Check the TRFC log.

You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".

Error handling:

If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.

Edited by: venkatraju m on Feb 7, 2008 7:57 AM

[former_member345199]

Hi,

Try this.

Transact RFC error

tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).

Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC

queue thats under outbound processing and click on display the IDOC which is on the menu bar.

Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)

place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'

(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)

Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you

to the particular TRFC request for that Idoc.

OR

Go into the JOB Overview of the Load there you should be able to find the Data Package ID.

(For this in RSMO Screen> Environment> there is a option for Job overview.)

This Data Package TID is Transaction ID in SM58.

OR

SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with

Transaction ID.

In the Status Text column you can see two status

Transation Recorded and Transaction Executing

Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually

execute the "Execute LUWs"

OR

Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed

for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->

EDIT ---> Execute LUW

Thanks,

JituK

[venkatraju_m]

i checked in SM58

fuction module IDOC_INBOUND_ASYNCHRONOUS status text is red.

message is like this "No service for system SYSTEM NAME , client XXX in Integration Directory'"

[former_member345199]

Hi,

I am not sure about this message. But this may be something related to connectivity or Authorizations for the user executing this load for that particular client.

thanks,

JituK

[Former Member]

Hi Mr.Venkatraju,

Even i had the same issue this morning .

Just ask your BASIS team to refresh the RFC connections and the issue will be resolved.

Log out and log in once they refresh the connection and check it out.

regards

Vikram

[Former Member]

Hi Guys,

I am getting the same error, I have the required authorization and refreshing RFC connection didnt help to resolve this problem.

Please let me know if there is any other solution to this issue....

Thanks,

Points will be rewarded...

Edited by: Sushant on Apr 21, 2008 6:57 PM

[Former Member]

RClick on the sourcesystem - Do a CHECK - It should return OKAY if connections are correct.

[venkatraju_m]

Source system is ok

[Former Member]

Hi,

Check the TRFC connection..

In monitor RSMO screen - in menubar - envoirnment - TRFC - source system - execute.. Check in the status text whether any transaction recorded..if so , in the menubar – EDIT- Execute LUW(F6).

Regards,

Siva.

[venkatraju_m]

In TC SM 58 i checked the status text " No service for system SAPID1, client 800 in Integration Directory"

[Former Member]

Check in BD87 and also in SM58. Check the RFC conection.

Khaja