
In such case reprocess the tRFC/IDOC with the help of SAP BASIS, and then job will finish successfully. In case of any failed tRFC’s/IDOC’s, the error message will be like “Error in writing the partition number DP2” or “Caller 01, 02 errors”. Go to RSA1 -> select source system -> System -> Connection check. INFO PACKAGE FAILURE: The following are the reasons for Info Pack failure.Ĭheck the source system connection with the help of SAP BASIS, if it is not fine ask them to rebuild the connection. Go to PSA -> select request -> select error records -> edit the records and save.Then run the DTP. 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. After increasing the space in the F fact table we can restart the job.Įrroneous 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. Table size needs to be increased before performing any action in BW.

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. 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.īefore restarting the Job/ repeating the DTP step, make sure about the reason for failure. After successful competition of the job uncheck the Handle Duplicate records option and activate. Go to the info provider -> DTP step -> Update tab -> check handle duplicate records -> activate -> Execute DTP. Before restarting the job after deleting the bad DTP request, we have to handle the duplicate records. Select the step-> right click and select “Display Message”-> there we will get the message which gives the reason for ABEND.Ī DTP can failure due to following reasons, in such case we can go for restarting the job.ĭuplicate records: In case of duplication in the records, we can find it in the error message along with the Info Provider’s name.
