regd production support errors in sap BI 7.0 This question is Not Answered.

krishna casukhela Apr 24, 2012 9:34 AM Hi guys I want a complete list of all production support errors related to BI & ECC. In addition to the ones what I mentioned, pls let me know if I missed out any. 1) trfc error 2) idoc error 3) caller 70 is missing[SID gen failure] 4) HACR error 5) Incorrect data in psa 6) Time stamp error 7) Table space issue I would appreciate if any could provide me links in addition to what I mentioned. regards krishna Re: regd production support errors in sap BI 7.0

1.

2.

3.

4.

5.

6.

7.

1. Job Cancellation in R/3 Source System.. We need to re-trigger the load again as job might be either in sleep or cancelled state and the re-trigger the load , also first delete the Red request from the manage tab of the Info Provider and then re-trigger the InfoPackage.(you can follow the same steps when when DTP fails) 2. Incorrect data in PSA... well first thing that should come to your mind when seeing this error DTP is correct the erroneous PSA data if we know the correct data or Create an error stack and load the correct data and Also, ask ECC team to look in to the wrong data 3. DSO Activation Failed..May be due to lock Sometimes another user/ Process chain try to load data from same DSO before activate DSO step is complete. In such case we need to stop load DTP job by cancelling the job in SM37. After successful activation of DSO ,we can manually load it or repeat PC. Also we can try to manually activate the request. 4. System response "Caller 70" is missing. Generally occurs due to missing I-DOCS and same can be checked in BD87, Also check where the problem is whether it is REQ or Info IDOCs that are missing for this error but generally repeating the step always resolve this issue but you have to trigger the IDocs yourself if it is getting struck in worst possible scenario 5. Inactive Transformations and DTP Activate them either by Transport transformations from Dev to Prod or directly if you have the access 6. Transactional RFC Error(tRFC) Non Updated IDOCs in the Source System also you will have to execute LUWs. Ask Basis team to clear LUWs in the system. 7. Error occurred due to Short Dump try to analyze the dump first in ST22 and check for further analysis in SM21 and check ztta roll area parameter if memory issue ..Repeat step generally works.

8.

8. Inconsistency in Delta Administration.. Delta is corrupted for data source Executed the program RSSM_OLTP_INIT_DELTA_UPDATE to solve this issue 9. 9. PC fail at Save hierarchy step. Repeat chain will work, but it is not a permanent solution, but the Permanent solution is check in RSH1 see that hierarchy in M state, try activating that particular hierarchy and then repeat the step, it will work 10. 10. Issues related to triggering of chains. ..Create a background job to trigger the chain daily. 11. 11. Process chain getting stuck at load PSA step for longer time Check the PID for the job->sm66 find there that PID>Lock work process->process overview for detail display analysis. Try to manually load Infopackage. If the system is very slow we need to contact Basis team to look in to the issue 12. 12. For ACR related issues. RSA1->apply hierarchy/Att. Change run-> check the infobject list or see in monitor in case of any issue. 13. 13. Oracle database Error: In that scenario you will have to change the parallel processing option in DTP, if number>3 then it might lead to database lock issue and if number is low and then it run very slow ( Thanks to Laksh Arora for keeping track of issues..Laksh Arora Thanks, Vinod

Sandeep Chauhan Dec 6, 2012 7:31 AM We are facing issues while loading data from SAP R/3 Production System to SAP BI Production System. Process Chains are failing giving errors. Background jobs in the SAP R3 production system executes successfully but the process chains in SAP BI Production system remains in active mode with no data or fails with error Processing overdue. Please find below the screen shot for your reference.

We have checked the RFC connection and its working fine. Kindly help us in resolving the issue ASAP, as it is affecting our reports for the end users. ins in active mode with no data or fails with error Processing overdue. Please find below the screen shot for your reference.

untitled1.JPG53.1 K

untitled.JPG44.4 K 52 Views
o

Topics: Business Intelligence , Enterprise Data Warehousing/Business Warehouse

Average User Rating (0 ratings)

Re: active mode with no data or fails with error Processing overdue.

KR CHowthary Dec 6, 2012 7:47 AM (in response to Sandeep Chauhan) hi sandeep can u plz check at SM58/SMQ1..seems like some Queues are stuck at R/3 Side, if you dont have authorized, ask basis help he can do it.

regads
o

Report Abuse
o

Like(0)

Re: active mode with no data or fails with error Processing overdue.

Sandeep Chauhan Dec 6, 2012 9:04 AM (in response to KR CHowthary) hie KR Thanks for you reply, in Transaction RFC i execute LUW. but still having same. every day we have running the 12 process chain, on a average ramdomly 5 to 6 process chain is fails , due to process overdue . what is the coz to show this error. how to over come this problem last 1 week i am facing the problem. Looking forward to hearing from you and appreciate your consideration Regards SC

Report Abuse

Like(0) Re: active mode with no data or fails with error Processing overdue.

KR CHowthary Dec 6, 2012 9:54 AM (in response to Sandeep Chauhan) Hi Sandeep, plz check at ST22 for short dump, its may give detailed info about error. that would be more elaborate to understand as i know it will be a burden on server or servers will be busy during that period.

if ur client or user allow to run process chains other timings.. let run and check one process chain which failed regards.

Report Abuse

Like(0) Re: active mode with no data or fails with error Processing overdue.

KR CHowthary Dec 6, 2012 9:57 AM (in response to Sandeep Chauhan) experts saying as I f this happens Regularly u may contact your Basis Person to increase the number of Background processes, or U can also check this problem can also happen if multiple infosources are trying to update one infoprovider, or if you are loading the cube without dropping the Index. http://scn.sap.com/thread/188103 http://scn.sap.com/message/4996139 http://sap.ittoolbox.com/groups/technical-functional/sap-bw/bw-batchjobs-processing-is-overdue-169072

regards

Report Abuse

Like(0) Re: active mode with no data or fails with error Processing overdue.

Oliver Uy Dec 6, 2012 8:54 AM (in response to Sandeep Chauhan) Check the link below http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=145719978 o Report Abuse Like(0) Re: active mode with no data or fails with error Processing overdue.
o

Tammy Powlas Dec 6, 2012 11:04 AM (in response to Sandeep Chauhan) This question belongs in the BW space Please post these types of questions there This thread will be moved Tammy (Moderator) o Report Abuse Like(0) Re: active mode with no data or fails with error Processing overdue.
o

Prashanth Konduru Dec 6, 2012 1:39 PM (in response to Sandeep Chauhan) Hi Sandeep, This may be caused due to the crunch in the system resource... As you said you are running 5-6 Process chains in parallel and the loads in parallel this may be causing the issue where the loads are getting hung and failing with process over due.

Check for short dumps in ST22, check SM58 -to find the cause of the issue. Check the source system job completed or not before processing the hung Idocs and TRFCs. Do one thing - keep an eye on the SM66 and SM51 screens and check which systems are getting burdened while these Process chains run in your Production environment. Involve BASIS as well at the time of these loads are processing so that they can monitor at the data base level as well to find the root cause of the issue. Regards KP