Vous êtes sur la page 1sur 11

Data Load issues

RAM S 26 posts since Oct 13, 2004


Data Load issues Mar 29, 2008 5:00 PM
Hi EXPERTS,
Please send me few data load issues which i want to prepare for interview.
Appreciate your inputs.
Regards,RAMU.

Venkat Ambati 3,716 posts since Mar 25, 2005


Re: Data Load issues Mar 29, 2008 5:14 PM
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.

Generated by Jive on 2016-02-22Z


1

Data Load issues

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:

Generated by Jive on 2016-02-22Z


2

Data Load issues

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_3XXXXXXXXXXXXXXXXXXXX (000001) on 20071001, 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

Generated by Jive on 2016-02-22Z


3

Data Load issues

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.

Generated by Jive on 2016-02-22Z


4

Data Load issues

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.

Generated by Jive on 2016-02-22Z


5

Data Load issues

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 #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 YXXXXXX. 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:

Generated by Jive on 2016-02-22Z


6

Data Load issues

Analysis:
Request REQU 3XXXXXXXXXXXXXXXXX, data package 001409 incorrect with status 9.
Request REQU_3XXXXXXXXXXXXXXXXXXX, data package 001415 not correct
Activation of data records from ODS object ZXXXXX10 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-zXXXX(Infoobject name)
IMPORTING
OUTPUT
= RESULT.
13) Fiscal Year Variant Error:
Action to be taken:
Go To SPRO: SAP Reference IMGBusiness Information WarehouseGeneral BW
settingsMaintain Fiscal Year VariantSelect Existing Z4 value and 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.

Jitu Krishna 2,962 posts since May 12, 2005


Re: Data Load issues Mar 29, 2008 5:18 PM
Hi,
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors

Generated by Jive on 2016-02-22Z


7

Data Load issues

Common Process chain errors


For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Hope this helps.
Thanks,
JituK

MADHUSUDHAN REDDY KAMBAM 47 posts since Oct 1, 2007


Data Load issues Mar 29, 2008 7:18 PM
HI Ramu,
Errors in monitoring:
SID error :
Reason: If the corresponding master data is missing for the particular transaction data.
Check for the load timing for the respective master data, if it less than an hour then make the request red and
repeat the ip.If the data is loaded to PSA then you have to delete the request from target and manually push
the data to from PSA.
If we are required for selective update then note down the info source from header and find it in RSA1,select
the one with #Single as postfix#.
Goto #data selection# tab and change the range.
In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error:
Reason: Data source replication Failed.
In order to handle this error you should be known to IP, info source and source system.
Goto RSA1, find the data source in the source sys tab.
Right click on the data source and replicate it.
Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and
execute rs_transtru_activat_all, data source and sys name.
Delete the #red# request from the target.
Update R not supported:
Reason: The corresponding initialization flag for the ip is lost.

Generated by Jive on 2016-02-22Z


8

Data Load issues

Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen
appears delete the only request present(the initialization flag).
Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
Goto update tab and select #Initialize delta process# try going for #with data transfer#.
Reschedule the IP.
Duplicate Record Error:
Reason: Duplicate error records for the loaded master data.
Goto info package via header or via RSA1.
Goto #processing tab# and change the ip setting, selecting only PSA and ignore duplicate records and re run
the ip.
Do remember to change the ip settings back to the original once after the second step.
ODS activation failure:
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
Goto #maintain variant#.
Check for the #QM# status of the requests in the target they should be green.
Then click the ODS activation tab.
In the screen which appears put the requests for which ODS activation failed.
Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
If requests are red then delete them from target.
Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error:
Reason: No aggregate found for the respective rollup.
Click on the variant in which the error occurred.
Goto chain tab and copy the variant and instance.
Run the nestle provided program YBW05.
Put in info in there and put the status as g # #green#.
Execute and refresh the status.
Lock issue:
Reason: The same ip is been locked by other user or may be used by other process chain.
We can see the locked entries and in the transaction SM12.
Wait for the other process to get complete once the ip loads to target in that process then there is no need for
running it for the process.

Generated by Jive on 2016-02-22Z


9

Data Load issues

In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate
update.
In the box appears select update in the background.
And the manually update the failed IP#s by selecting manual update in the context menu.

Alfa confirming value error, Time conversion error, Chain didn#t start, Delay due to long running job, Poor
system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didn#t start: A scheduled chain didn#t triggered at the prescribed timing.
-For all the above error we have to raise a ticket.

Idoc or TRFC error:


Reason: An Idoc is been stuck somewhere.
Reload the Master Data manually again from Info-package at RSA1.
Release the Idoc.
In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
In the Screen if the status is #Transaction Recorded# it means its stuck goto edit and click Execute LUW or
press F6.
If status is #Transaction executing# then it means its fine wait.
Or raise ticket.
Error Due to short Dump:
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record,
page allocation, failed change run.
Viewing Short Dump:
Process terminated in the Source system:
.
Reason: Sometimes we face that a load has failed due to job Termination at
Source System.
This happens due to unavailability of the source system or some connectivity problem between source and
target systems.
1.
Make the request red.
2.
Delete the request from the data target.

Generated by Jive on 2016-02-22Z


10

Data Load issues

3.
4.

Reschedule the ip.


If still the job fails raise the ticket.

Pls assign points if it helps u


Thanks & Regards,
Madhu

Generated by Jive on 2016-02-22Z


11