How to identify what are all the errors appears in process chain,

Question

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Answer 1

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. 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.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. 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’.
         4. Goto ‘data selection’ tab and change the range.
Tip: change the last 4 digits for from to ‘0000’and the last 4 digit for to     ‘9999’.
        5. Repeat the ip.
         6. 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.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. 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.
         5. Delete the ‘red’ request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. 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).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select ‘Initialize delta process’ try going for ‘with data transfer’.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto ‘processing tab’ and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. 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.
         1. Goto ‘maintain variant’.
         2. Check for the ‘QM’ status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g – ‘green’.
         5. 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.
         1. We can see the locked entries and in the transaction SM12.
         2. 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.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. 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.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is ‘Transaction Recorded’ it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is ‘Transaction executing’ then it means its fine wait.
         6. 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.
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.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu