Hi All...here is the list of SAP BI Production Support issues along with the resolution. Hope it will be helpful for
the people who are working in support environment.
1. 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 Providers 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. Itll be done by DBA Team. After increasing the space in the
F fact table we can restart the job.
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.
2.
Info Pack Long Run: If an info pack is running long, then check whether the job is finished
at source system or not. If it is finished, then check whether any tRFC/IDOC struck/Failed
with the help of SAP BASIS. Even after reprocessing the tRFC, if the job is in yellow status
then turn the status into Red. Now restart / repeat the step. After completion of the job
force complete.
Before turning the status to Red/Green, make sure whether the load is of Full/Delta and also the time
stamp is properly verified.
Select Info Package-> Process Monitor -> Header -> Select Request -> Go to source System
(Header->Source System) -> Sm37-> give the request and check the status of the request in the
BW System
Source System
RSA7
Source System
SM37
Action
I/P Status
RED(Cancelled)
Time stamp
Time stamp
Turn the I/P Status
matching with SM37 matching with RSA7 into Red and
last updated time
time stamp
Restart the Job
I/P Status
RED(Cancelled)
I/P Status
(Cancelled)
Time stamp
Time stamp
Turn the I/P Status
matching with SM37 matching with RSA7 into Red and
last updated time
time stamp
Restart the Job
I/P Status
RED(Cancelled)
I/P Status
RED(Cancelled)
I/P Status
(Cancelled)
When there is an IDOC which is stuck in the BW and successfully completed the background job in the source
system, in such cases we can process the IDOC manually in the BW.
Go to Info Package -> Process Monitor -> Details -> select the IDOC which is in yellow
status(stuck) -> Right click -> Process the IDOC manually -> itll take some time to get
processed.
******Make sure that we can process the IDOC in BW only when the back ground job is completed in the
source system and stuck in the BW only.
3.
When there is a failure in DSO activation step, check whether the data is loading to DSO from PSA or from the
source system directly. If the data is loading to DSO from PSA, then activate the DSO manually as follows
Right click DSO Activation Step -> Target Administration -> Select the latest request in DSO -> select
Activate -> after request turned to green status, Restart the job.
If the data is loading directly from the source system to DSO, then delete the bad request in the PSA
table, then restart the job
4.
When there is a failure in Drop Index/ compression step, check the Error Message. If it is failed
due to Lock Issue, it means job failed because of the parallel process or action which we have
performed on that particular cube or object. Before restarting the job, make sure whether the
object is unlocked or not.
There is a chance of failure in Index step in case of TREX server issues. In such cases engage BASIS team
and get the info reg TREX server and repeat/ Restart the job once the server is fixed.
Compression Job may fail when there is any other job which is trying to load the data or accessing
from the Cube. In such case job fails with the error message as Locked by ...... Before restarting
the job, make sure whether the object is unlocked or not.
5. Roll Up failure:
Roll Up fails due to Contention Issue. When there is Master Data load is in progress, there is a
chance of Roll up failure due to resource contention. In such case before restarting the job/ step,
make sure whether the master data load is completed or not. Once the master data load finishes
restart the job.
When there is a failure in the attribute change run due to Contention, we have to wait for the other job (Attribute
change run) completion. Only one ACR can run in BW at a time. Once the other ACR job is completed, then we
can restart/repeat the job.
We can also run the ACR manually in case of nay failures.
Go to RSA1-> Tool -> Apply Hierarchy/Change Run -> select the appropriate Request in the list for which we
have to run ACR -> Execute.
7. Transformation In-active:
In case of any changes in the production/moved to the production without saving properly or any
modification done in the transformation without changing, in such cases there is a possibility of
Load failure with the error message as Failure due to Transformation In active.
In such cases, we will have to activate the Transformation which is inactive.
Go to RSA1 -> select the transformation -> Activate
In case of no authorization for activating the transformation in production system, we can do it by using the
program - RSDG_TRFN_ACTIVATE
Try the following steps to use the program "RSDG_TRFN_ACTIVATE here you will need to enter
certain details:
Transformation ID: Transformations Tech Name (ID)
Object Status: ACT
Type of Source: Source Name
Source name: Source Tech Name
Type of Target: Target Name
Target name: Target Tech Name
1. Execute. The Transformation status will be turned into Active.
Then we can restart the job. Job will be completed successfully.