Beruflich Dokumente
Kultur Dokumente
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.
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.
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 #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:
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.
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.
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.
3.
4.