Scribd
Upload
46 views10 pages

PC Correction SAP APO

When process chains fail, common reasons include IDOC issues preventing data transfer between systems, duplicate data records, objects being locked, and target data stores being inactive. Resolutions involve checking source connections, deleting request IDs, handling duplicate keys, releasing locks, and activating required objects.

Uploaded by

avinash
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
46 views10 pages

PC Correction SAP APO

When process chains fail, common reasons include IDOC issues preventing data transfer between systems, duplicate data records, objects being locked, and target data stores being inactive. Resolutions involve checking source connections, deleting request IDs, handling duplicate keys, releasing locks, and activating required objects.

Uploaded by

avinash
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

When the process chains run, sometime they fail due to different reasons.

Following are
few examples of process chain failure and the resolution:

1.      PC: Z_XXXX had failed at IP loading steps with error msg “Job terminated in source
system”. We checked the Source system connection. When we found it ok, we processed
the data from R3 (RA7) through t.code bd87. Then we ran program
RS_TRANSTRU_ACTIVATE_ALL. We replicated the data sources and finally
repeated the failed steps.  It was fixed and it finished successfully.

Error Message:

        

                Reason: IDOC issue. Data is not coming from Source, R3(RA7 client 100) to BW
(BA9)

               Correction:

            1st step:-> Check Source system connection through t.code: sm59
                               

               

               No red should come.

•        2nd step:-> t.code :bd87 in R3

                   

                                                                                                       
                         

Expand the selection portion and then right click and click on ’ process’

•        3rd step :-> Run program RS_TRANSTRU_ACTIVATE_ALL ,click on execute, give info
source and source system from the  below screen into the new one and execute

                       

•        4th step :->Go to rsa1, find the Data Source and click on replicate metadata
                         

•                      5th step:-> Repeat the step where it has failed in the process chain.

       If we get error msg as: Data Source 0WBS_ELEMT_ATTR has to be replicated. Error in
source system, we need to do the above steps (3rd, 4th n 5th).

2.     PC: Z_XXXX failed  in the DTP step ZFMP_C4_TEXT / RP1CLNT900 -> ZFMP_GAGA  showing the 
error as “ZFMP_GAGA : Duplicate data records”

                                                                                                     

                

•        Correction: We went to the target ZFMP_GAGA, deleted the request id and changed the
DTP by handling the duplicate record keys and then repaired the process.
                        

                           

   

•        Activate

•        Go to the DTP and “Repair” it.

•        Go to the new dtp that has been started-> click on variant. We will find ‘handle duplicate
record keys ‘checked ‘. We need to uncheck it and then activate it again.
                           

3. In the PC: Z_XXXX, the IP: ZPAK_7IVGS4VQX74NXT4PQFX67VOWL failed twice because the object
requested was locked.

                                  
                            

•        Went to sm12 ,saw the lock and then repeated the step but had the same error
   
                                                                                                                                                       
                            

                                                                                                                                                      

                   

4.      The PC: Z_XXXX had failed. It failed in ODS activation step. We tried to activate it
manually but it failed again and again.
           

                                                                                                                                                             
                                    

Reason: The target DSO Z_ODPSG2 was inactive

                         

•        Correction: The ODS was migrated and the Step


DTP_DAELS2O23YC3DK9AA1GK18VAM was killed as it was stuck and then the step was
repeated and finally it was passed.                            
                           

 
                                       

You might also like