Load failures, Missing Deltas, Process Chain failures are common in daily support.

Long
Load times, Query time-outs are common for performance monitoring.

You can debug the load failures in the RSMO's detailtab and see where it
happened and what happened, later, if your load was via psa you can simulate
and debug transfer/updt-rule of a single datapacket.
2. You can check the error log in ST22 and SM21 (if it is related to Dumps)
3. You can check the error log in SM12 also (if it is related to locks)
4. You can check the error log in the SM37 and analyze the job log (JobLog which
will let you know where the job got stucked)

Time stamp error

when you link the replicate the datasources the system copies the timestamp of your r/3
datasource to the copy of your datasource in BW. THe main objective is to make sure that
when you load data the structure of the datasources are the same in BW and R/3. if you
change something in R/3 the timestamp will change in r/3. when you load again the
system checks to the two timestamp and will notice that they have not the same
timestamp. the load will fail because the bw cannot garantee at this point that the data
loaded has the correct structure..

Solution :

In Source Systems pane - navigate to your system - right click Datasource Overview -
Replicate Datasources. Then go to corresponding Infosource and activate it.

After performing all these, go to SE38 and execute this ABAP Program
RS_TRANSTRU_ACTIVATE_ALL.

Better to LogOff and LogIn.

This solves the Time Stamp Error.

if you want to know more about. check the following link.

https://www.sdn.sap.com/irj/sdn/thread?messageID=933390

regards
harikrishna N

ICould any one guide me the steps to rectify the Process chain failure at AND stage???
Steps:
1.Start
2.Data loads(9)
3.AND(failed here)

Error message:This AND process is not waiting for event RSPROCESS, parameter
3VW29DJ1PBX67PFJHD5IAEYI1

I did REPETE the chain from AND, but it failed again.

Finally I reran the chain and working now.
But all i need to know is how to rectify the probem at AND stage??

think ur chain is loading parallelly then after successfully completing both in parallel
with "AND" option then after it was loading sequential.
not worry if AND fails, AND option if for after successfull completion of parallel loads,
it starts the next process, check r u getting REPEAT option?? then start the REPEAT,
hope the chain runs successfull for remaining process.

check in table RSPCPROCESSLOG, RSPCLOGS table

execute the program /ssa/bwt
and logs tab in RSA1, analyze the process.

one of the process step failed in the process chain when I checked the logs for that
process step ( right click--> display messages) under backg there are no logs( empty) but
in sm37 error for the process chain is Time out reached for the
process chain. what is the reason for the failure please help me. loading master data.

there is a time limit for every diaolg process,whenever the processing of each data packet
excceds the required timelimit ,then you can see this error

the solution is to run the load through PSA,then the job will run as a background process
or you can reduce the data packet size ,so that the number of records proceessed will be
less, thus conserving dialog time

Peter,
Have a look at the below stuff

Types of Errors Faced During the Data Load in BW:

1) Idoc Or Trfc Error

2) Processing Is Overdue For Processed Idocs
3) Error At Source System Asking For Replication Of Data sources
4) Lock Not Set For Loading Master Data ( Text / Attribue / Hierarchy )
5) Data Error
6) Other Type Of Data Issue
7) Error While Loading Pc File From Desktop / Application Server
8) Job Failure At Source System
9) Error Asking For Initialization
10) Error Related To Activation
11) Transaction Job Fails Giving Message : “No Sid Found For Certain Data Record”
12) Alfa Conversion Error
13)Error in Fiscal Year Variant.
14) Table Space Errors

1) Idoc Or Trfc Error

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.

Resolutions:
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.
Resolutions:
We can process the IDocs manually

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.

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 “Locked”.
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 – 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

Detail 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 – That it is a PC File Source System.
2nd – 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 don’t schedule the job in
background instead select “Schedule Immediately” option in the Info-Package.

8) JOB FAILURE AT SOURCE SYSTEM

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 “Job Overview” 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:

Right Click on it◊ Select your ODS Object ◊Go to RSA1 & Select ‘Manage’.
Select the Red Request & see the reason for its failure.
Rectify the error & then go for its activation.

11) TRANSACTION JOB FAILES GIVING MESSAGE : “NO SID FOUND FOR
CERTAIN DATA RECORD”
Action to be taken:

Load Master data for YTSAVSKU. To load it, select its Infopackage & at schedule tab
select “Immediate” & 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 “Processing (data packet): Everything OK”
3) Right click on “Data Package 1 ( 13321 Records ) : Everything OK” under it.
4) Select Manual update option in the dropdown menu.

12) Alfa Conversion Error:

Analysis: Request REQU 3Z1MPLCGF15QJBYXT8RLKAFFL, data package 001409

incorrect with status 9.

Request REQU_3Z1MPLCGF15QJBYXT8RLKAFFL, data package 001415 not correct

Activation of data records from ODS object ZDCDO10 terminated

Communication error (RFC call) occurred

Action to be taken:

Go to Transfer Rules. There select that particular Info object and double click on that. Go
to routine there call function.

DATA: l_s_errorlog TYPE rssm_s_errorlog_int.

CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = TRAN_STRUCTURE-zzvbund
IMPORTING
OUTPUT = RESULT.

13) Fiscal Year Variant Error:

Action to be taken:

General BW◊Business Information Warehouse◊Go To SPRO: SAP Reference IMG

Select Existing Z4 value and◊Maintain Fiscal Year Variant◊settings Click on Periods
Give the Calendar year from which year you want then enter on that and give the values
as you want.

14) Table Space Errors: Due to space problem these types of errors occurs.
So we will contact Basis People. They will resolve these type of Problems by increasing
the space.

https://www.sdn.sap.com/irj/sdn/thread?forumID=131&threadID=115256&messageID=1
287826

Delta load

if the delta load fails then make that request red by using qm action.

now when u schedule the delta load again u get the option repeat the previous
delta again.

u can schedule it again.

if u want to reload the data agian then u have to delete the previous initillization and
the reschedule.

regards.
REPEAT DELTA

can choose the option in the infopackage level. U will have a check box- ignore duplicate
records in the processing tab of the infopackage.

For deltas.. u can check whether the extraction has been completed or not.. If yes try to
findout the reason for which the load has failed.. if not then analyze the cause for the
failure and then take the repeat of last delta after deleting the bad requests from ur data
target and do ensure then u have to chnage the QM status to RED in the monitor when u
go for the repeat delta.

When u go for the repeat delta then it will takes ur Old delta as well as the new delta data
records.

Hope it helps-