DTP Failure

Select the step-> right click and select “Display Message”-> there we will get the message which gives the reason for ABEND.

A DTP can failure due to following reasons, in such case we can go for restarting the job.

• System Exception Error
• Request Locked
• ABAP Run time error.
• Duplicate records
• Erroneous Records from PSA.

Duplicate records:

            In case of duplication in the records, we can find it in the error message along with the Info Provider’s name. Before restarting the job after deleting the bad DTP request, we have to handle the duplicate records. Go to the info provider -> DTP step -> Update tab -> check handle duplicate records -> activate -> Execute DTP. After successful competition of the job uncheck the Handle Duplicate records option and activate.

DTP Log Run:

• If a DTP is taking log time than the regular run time without having the back ground job, then we have to turn the status of the DTP into Red and then delete the DTP bad request (If any), repeat the step or restart the job.

• Before restarting the Job/ repeating the DTP step, make sure about the reason for failure.
• If the failure is due to “Space Issue” in the F fact table, engage the DBA team and also BASIS team and explain them the issue. Table size needs to be increased before performing any action in BW. It’ll be done by DBA Team. After increasing the space in the F fact table we can restart the job.

Erroneous Records from PSA:

     When ever a DTP fails because of erroneous records while fetching the data from PSA to Data Target, in such cases data needs to be changed in the ECC. If it is not possible, then after getting the approval from the business, we can edit the Erroneous records in PSA and then we have to run the DTP.

Go to PSA -> select request -> select error records -> edit the records and save.

Then run the DTP.