Errors in Production

Question

Hi Friends,
Pls any one send me Errors in production with solutions.
Regards
Ramana

Answer 1

hi ramana
HI,
"Job Termination in the R/3 Source System
u2022 The Exact Error message is ""Job termination in source system"". The exact error message may also differ, it may be u201CThe background job for data selection in the source system has been terminatedu201D. Both the error messages mean the same. Some times it may also give u201CJob Termination due to System Shutdownu201D.
u2022 The message appears in the Job Overview in RSMO, or in u201CDisplay Messageu201D option of the Process in the PC.
" "u2022 If the job in R/3 system cancels due to some reasons, then this error is encountered. This may be due to some problem in the system. Some times it may also be due to some other jobs running in parallel which takes up all the Processors and the jobs gets cancelled on R/3 side.
u2022 The error may or may not be resulted due to Time Out. It may happen that there would be some system issues like locks/DB Issues in the source system
" "u2022 First check the job status in the Source System. It can be checked through Environment -> Job Overview -> In the Source System. This may ask you to login to the source system R/3. Once logged in it will have some pre-entered selections, check if they are relevant, and then Execute. This will show you the exact status of the job. It should show u201CXu201D under Canceled.
u2022 The job name generally starts with u201CBIREQU_u201D followed by system generated number.
u2022 Once we are confirm that this error has occurred due to job cancellation, we then check the status of the ODS, Cube under the manage tab. The latest request would be showing the QM status as Red.
u2022 We need to re-trigger the load again in such cases as the job is no longer active and it is cancelled. We re-trigger the load from BW.
u2022 We first delete the Red request from the manage tab of the InfoProvider and then re-trigger the InfoPackage.
u2022 Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
"Transact RFC Error u2013 Non Updated IDOCs in the Source System.
u2022 Message appears in the bottom of the u201CStatusu201D tab in RSMO. The error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted.
u2022 Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them.
" u2022 tRFC u2013 Transact Remote Function Call Error, occurs whenever LUWu2019s (Logical Unit of Worku2019s) are not transferred from the source system to the destination system. "u2022 Once this error is encountered, we could try to Click a complete Refresh u201CF6u201D in RSMO, and check if the LUWu2019s get cleared manually by the system.
u2022 If after u201Ccoupleu201D of Refresh, the error is as it is, then follow the below steps quickly as it may happen that the load may fail with a short dump.
u2022 Go to the menu Environment -> Transact. RFC -> In the Source System, from RSMO. It asks to login into the source system.
u2022 Once logged in, it will give a selection screen with u201CDateu201D, u201CUser Nameu201D, TRFC options.
u2022 On execution with u201CF8u201D it will give the list of all Stuck LUWu2019s. The u201CStatus Textu201D will appear Red for the Stuck LUWu2019s which are not getting processed. And the u201CTarget Systemu201D for those LUWs should be the BW Production system. Do not execute any other IDOC which is not related have the u201CTarget Systemu201D.
u2022 Right Click and u201CExecuteu201D or u201CF6u201D after selection, those LUWu2019s which are identified properly. So that they get cleared, and the load on BW side gets completed successfully.
u2022 When IDocs are stuck go to R/3, use Tcode BD87 and expand u2018IDOC in inbound Processingu2019 tab for IDOC Status type as 64 (IDoc ready to be transferred to application). Keep the cursor on the error message (pertaining to IDOC type RSRQST only) and click Process tab (F8) . Ths will push any stuck Idoc on R/3.
u2022 Monitor the load for successful completion,
and complete the further loads if any in the Process Chain.
"No SID found for a characteristics
For example consider a Transactional Data load has failed due to no SID found for the characteristic 0Customer." It might happen that the Master Data 0Customer was loaded much before the transactional data load and by the time the transactional data load was started some transactions has taken place in the OLAP sytem and a new Customer has got created. As a result the Transactional Data load which would try to get the SID for the master data would not find it would fail. Check for the Master data in the R3 system if the data is available in the R3 system load the Master data in BW and then manually load the transactional Data. If the master data is not present in the R3 system also then itu2019s a data issue and needs to be reported to OSC or the Client.
"Attribute Change Run failed - ALEREMOTEBW was locked.
u2022 The message appears in the Job Overview in RSMO, or in u201CDisplay Messageu201D option of the Process in the PC.
u2022 The exact error message would be like, u201CUser ALEREMOTE locked the load of master datas for characteristic 0CUSTOMERu201D. Here it is specifically for the 0CUSTOMER load. It may be different related to Master Data InfoObject which is getting loaded. " During the Master data Loads, sometimes a lock is set by the system user ALEREMOTE. This happens because the HACR is runnning for some other MD load at the same time when the system tries to carry out the HACr for this new MD. This is scheduling problem as due to the time clashing the error has occured. "
u2022 Check the error message completely and also check the long text of the error message, as it will tell you the exact Master Data which is locked by user ALEREMOTE.
u2022 The lock which is set is because of load and HACR timing which clashed. We first need to check RSA1 -> Tools -> HACR, where in we would get the list of InfoObjects on which HACR is currently running. Once that is finished only then, go to the Tx Code SM12. This will give you few options and couple of default entries. When we list the locks, it will display all the locks set. Delete the lock for the specific entry only else it may happen that some load which was running may fail, due to the lock released.
u2022 Now we choose the appropriate lock which has caused the failure, and click on Delete. So that the existing lock is released.
Care should be taken that we do not delete an active running job. Preferable avoid this solution
u2022 When HACR finishes for the other Master Data, trigger Attribute change run fot this Master Data.
No Data found in the soucre system It may happen that there is transaction which has taken place for particular load. Or incase of delat loads there is no changes. This would result in giving anerror message as "No data available in the source system". As a result the load would remaing hanging ie the QM status would be yellow and if not changed then the load would fail due to processing overdue. Extract the data in the source sytem and check whether the data is actually present or not. If the load is getting the data from a flat file go to the Application server i.e transaction AL11 and go to the relevant path and check whether if data is present. If data is not present then change the QM status to manually green. If the data is available check for the extractor job failure.
srinivas reddy  
Posts: 40
Registered: 7/11/07
Forum Points: 0 
   Re: errors  
Posted: Jun 13, 2008 3:41 PM    in response to: Shashank Dighe       E-mail this message      Reply 
can u tell me the solutions for above lock issues, no app found data , idoc/trfc errors
Bala Murugan A.J  
Posts: 462
Registered: 9/27/07
Forum Points: 864 
   Re: errors  
Posted: Jun 13, 2008 4:10 PM    in response to: srinivas reddy       E-mail this message      Reply 
1) IDOC or TRFC Error
We can see the following error at u201CStatusu201D Screen;
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.
Analysis:
If we see at the error message we find that the failure is due to Non-arrival of IDOCs from Source System to BW.
Action to be taken:
Reload the Master Data manually again from Info-package at RSA1.
2) PROCESSING IS OVERDUE FOR PROCESSED IDOCs
Diagnosis
IDocs were found in the ALE inbox for Source System that are not
Updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.
Analysis:
After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.
Action to be taken:
We can process the IDocs manually as shown below:
3) ERROR AT SOURCE SYSTEM ASKING FOR REPLICATION OF DATASOURCES
Analysis:
If we see at the error message we find that the System is asking us to Replicate the Data Source System.
Action to be taken:
Go to RSA1 initial Screen & press Source System tab at LHS.
Once Replication is done we have to activate the Transfer Structures in Production System. For this we have to execute a program SE38 in BW On executing we will get the following screen:-
Once you have Replicated the Data-Sources & Activated the Transfer Structure you can reload the data manually by Executing the Info-package at RSA1.
4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )
Reason for Failure:
Diagnosis
User ALEREMOTE is preventing you from loading texts to characteristic
0COSTCENTER . The lock was set by a master data loading process with the
request number (DataPcakage number)
REQU_3VB1GNF0FGRRV84IUWGFOIIG7(000001) on 20041001,071055(985111) .
System response
For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process.
Procedure
Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks.
If a process terminates, the locks that have been set by this process are reset automatically.
Analysis:
After looking at all the above error messages we find that the user is u201CLockedu201D.
Action to be taken:
Wait for sometime & try reloading the Master Data manually again from Info-package at RSA1.
5) DATA ERROR
Analysis:
After looking at all the above error messages we find
1st u2013 That it is a PC File Source System.
2nd - That there are Duplicate Data Records leading to error.
Action to be taken:
We have to delete this Request & then rectify the Data in the Data source at the Source System Level. After this we have to manually load the data.
6) OTHER TYPE OF DATA ISSUE
l Error Message
Diagnosis
1 data records were marked as incorrect in the PSA. The additional checking and processing of the 2 data package was terminated in a customer routine. This was done intentionally or was due to a short dump being intercepted.
System response
The data package was not updated.
Procedure
Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.
Analysis:
After looking at all the above error messages we find that the PSA contains incorrect record.
Action to be taken:
To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.
Resolution: - We will see how to do the go for the 2nd method: -
7) ERROR WHILE LOADING PC FILE FROM DESKTOP / APPLICATION SERVER
Analysis:
After looking at all the above error messages we find
1st u2013 That it is a PC File Source System.
2nd u2013 For uploading data from the PC File it seems that the file was not kept at the application server & the job was scheduled in Background.
Action to be taken:
For running the job in Background Transfer file to Application server & then load it from there.
OR Else if you want to load file from your desktop then donu2019t schedule the job in background instead select u201CSchedule Immediatelyu201D option in the Info-Package.
8) JOB FAILURE AT SOURCE SYSTEM
Analysis:
Diagnosis
The background processing was not finished in the source system.
It is possible that the background processing in the source system was terminated.
System response
There are incomplete data packets present.
Further analysis:
Go to the background processing overview in the source system. You can get to this with the Wizard or the menu path Environment -> Job Overview -> In the source system (This is the alternate path to see the u201CJob Overviewu201D at the Source System.
Once there, check whether the background job really was terminated.
Note
Please make sure that the correct date of request has been selected in the selection screen of the overview.
Action to be taken:
At source system you can see the reason for the Job Failure. Thus we need to take the action accordingly.
9) ERROR ASKING FOR INITIALIZATION
Analysis:
After looking at all the above error messages we find that if we want to load data with the delta update you must first initialize the delta process.
Action to be taken:
If you want to load data with the delta update you must first initialize the delta process.
Afterwards the selection conditions that were used in the initialization can no longer be changed.
But Initialization is a typical process that should not be carried out without confirming with the onsite person in any case.
10) ERROR RELATED TO ACTIVATION
Analysis:
Here we can see that the Activation of ODS has failed as the Request Status in the ODS may not be green.
Action To be Taken:
Go to RSA1 Select your ODS Object  Right Click on it & Select u2018Manageu2019.
Select the Red Request & see the reason for its failure.
Rectify the error & then go for its activation.
Error message when processing in the Business Warehouse
Diagnosis
An error occurred in the SAP BW when processing the data. The error is documented in an error message.
System response
The error message(s) was/were sent by:
Second step in the update
Second step in the update
Second step in the update
Second step in the update
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box and select the long text for further information.
Follow the instructions in the message.
11) TRANSACTION JOB FAILES GIVING MESSAGE : u201CNO SID FOUND FOR CERTAIN DATA RECORDu201D
Action to be taken:
Load Master data KU. To load it, select its Infopackage & at schedule tab select u201CImmediateu201D & start loading.
After this come to RSMO & select this failed job.
Click on Detail tab.
Since in this case we see that the data is only getting loaded in ODS & not in PSA thus we have to reload data manually through Infopackage.
If we have PSA here then we need to take the following action:
1) Expand nodes under Detail tab.
2) Expand node u201CProcessing (data packet): Everything OKu201D
3) Right click on u201CData Package 1 : Everything OKu201D under it.
4) Select Manual update option in the dropdown menu.
Hope it helps