LEARN SAP BI

All SAP BI Information at One Place

WEDNESDAY, 29 JANUARY 2014

SAP BW Production Support Issues with

Resolutions
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.
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.
2.

INFO PACKAGE FAILURE:

The following are the reasons for Info Pack failure.

Source System Connection failure

tRFC/IDOC failure

Communication Issues

Processing the IDOC Manually in BI

Check the source system connection with the help of SAP BASIS, if it
is not fine ask them to rebuild the connection. After that restart the
job (Info Pack).

Go to RSA1 -> select source system -> System -> Connection check.

In case of any failed tRFCs/IDOCs, the error message will be like

Error in writing the partition number DP2 or Caller 01, 02 errors.
In such case reprocess the tRFC/IDOC with the help of SAP BASIS,
and then job will finish successfully.

If the data is loading from the source system to DSO directly, then
delete the bad request in the PSA table, then restart the job

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.

Time Stamp Verification:

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 source system -> If it is in
active, then we have to check whether there any struck/failed
tRFCs/IDOCs
If the request is in Cancelled status in Source system -> Check the Info
Pack status in BW system -> If IP status is also in failed state/cancelled
state -> Check the data load type (FULL or DELTA) -> if the status is full
then we can turn the Info Package status red and then we can
repeat/restart the Info package/job. -> If the load is of Delta type then we
have to go RSA7 in source system-> (Compare the last updated time in
Source System SM37 back ground job)) Check the time stamp -> If the
time stamp in RSA7 is matching then turn the Info Package status to Red
-> Restart the job. Itll fetch the data in the next iteration
If the time stamp is not updated in RSA7 -> Turn the status into Green ->
Restart the job. Itll fetch the data in the next iteration.
Source System

BW System

Source
System
RSA7
Time stamp
matching
with SM37
last updated
time

Source
System
SM37
Time stamp
matching
with RSA7
time stamp

I/P Status
RED(Cancelled)

I/P Status
(Active)

I/P Status
RED(Cancelled)

I/P Status
(Cancelled)

Time stamp
matching
with SM37
last updated
time

Time stamp
matching
with RSA7
time stamp

I/P Status
RED(Cancelled)

I/P Status
(Active)

Time stamp
is not
matching
with SM37
last updated
time

Time stamp
is not
matching
with RSA7
time stamp

I/P Status
RED(Cancelled)

I/P Status
(Cancelled)

Time stamp
is not
matching
with SM37
last updated
time

Time stamp
is not
matching
with RSA7
time stamp

Action
Turn the
I/P Status
into Red
and
Restart
the Job
Turn the
I/P Status
into Red
and
Restart
the Job
Turn the
I/P status
into
Green
and
Restart
the job
Turn the
I/P status
into
Green
and
Restart

the job

Processing the IDOC Manually in BI:

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.
Note: 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.

DSO Activation Failure:

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

4.

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
Failure in Drop Index/ Compression step:

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.
6. Change Run Job finishes with error RSM 756
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
A. Execute. The Transformation status will be turned into Active.

Then we can restart the job. Job will be completed successfully.

8. Process Chain Started from the yesterdays failed step:
In few instances, process chain starts from the step which was failed in the
previous iteration instead of starting from the Start step.
In such cases we will have to delete the previous days process chain log,
to start the chain form the beginning (from Start variant).

Go To ST13-> Select the Process Chain -> Log -> Delete.

Or we can use Function Module for Process Chain Log Deletion:
RSPROCESS_LOG_DELETE.
Give the log id of the process chain, which we can get from the ST13
screen.
Then we can restart the chain.
Turning the Process Chain Status using Function Module:
At times, when there is no progress in any of the process chains which is
running for a long time without any progress, we will have to turn the
status of the entire chain/Particular step by using the Function Module.
Function Module: RSPC_PROCESS_FINISH
The program "RSPC_PROCESS_FINISH" for making the status of a particular
process as finished.
To turn any DTP load which was running long, so please try the following
steps to use the program "RSPC_PROCESS_FINISH" here you need to enter
the following details:
LOG ID: this id will be the id of the parent chain.
CHAIN: here you will need to enter the chain name which has failed
process.
TYPE: Type of failed step can be found out by checking the table
"RSPCPROCESSLOG" via "SE16" or "ZSE16" by entering the Variant &
Instance of the failed step. The table "RSPCPROCESSLOG" can be used to
find out various details regarding a particular process.
INSTANCE & VARIANT: Instance & Variant name can be found out by right
clicking on the failed step and then by checking the "Displaying Messages
Options" of the failed step & then checking the chain tab.
STATE: State is used to identify the overall state of the process. Below
given are the various states for a step.
R Ended with errors
G Successfully completed
F Completed
A Active
X Canceled
P Planned
S Skipped at restart
Q Released
Y Ready

Undefined
J Framework Error upon Completion (e.g. follow-on job missing)
9. Hierarchy save Failure:
When there a failure in Hierarchy Save, then we have to follow the below
process.
If there is issues with Hierarchy save, we will have to schedule the Info
packages associated with the Hierarchies manually. Then we have to run
Attribute Change Run to update the changes to the associated Targets.
Please find the below mentioned the step by step process.
ST13-> Select Failed Process Chain -> Select Hierarchy Save Step ->
Right click Display Variant -> Select the info package in the hierarchy ->
Go to RSA1 -> Run the Info Package Manually -> Tools -> Run
Hierarchy/Attribute Change Run -> Select Hierarchy List (Here you can find
the List of Hierarchies) -> Execute.
SAP BI/BW Data Load Errors and Solutions for a support Project:

1) BW Error: Failure occurred when delta Update is going on from one data target to
another data target.

Possible Causes:
1.

1. TRFC error

2.

2. Data is incorrect-error records.

3.

3. Locked by ALEREMOTE or user.

Solution: In Monitor check the technical status of the request for red status and then,
delete the request from the data target.

If its delta update, in the source data target reset the delta. Retrigger the Info Package
to load data again.
If its Full update, restart job again after deleting error request from the data target.

2) BW Error: Master job abended with error code or PR1 batch job did not run or get
delayed.

Possible Causes: This can be because of changes to Maestro or some changes to job.

Solution: Maestro jobs are handled by Production Services, if job is abended with an
error code, BASIS team looks at Maestro problems. If Job is an issue, SAP support team
investigates it.

3) BW Error: Database Errors: Enable to extend Table, enable to extend the Index.
For example.
Database error text: "ORA-01653: unable to extend table
SAPR3./BIC/AZUSPYDO100 by 8192 in table space PSAPODS2D"
Possible Causes: This is due to lack of space available to put further data.

Solution: This is Database error. Short dump message indicates this error message.
Ticket is raised for DBA Elizabeth Mayfield who provides the space required. If the update
mode is delta, technical status of job is changed to red and request is deleted from the
data target. InfoPackage for Delta update is triggered again to get delta from R/3 back. If
its full update, request is deleted from the data target and InfoPackage is triggered again
to get full update.

We can navigate to relevant short dump from monitor or execute transaction

ST22.

Once DBA confirms that space issue is corrected, job is rerun to get data from source again.

4) BW Error: Dead Lock:

Possible Causes: This can happen when SMON is running or any DBA
Solution: Contact the DB People Ticket is raised for DBA who can adjust the schedules
for SMON process.
If the update mode is delta, technical status of job is changed to red and request is
deleted from the datatarget. Infopackage for Delta update is triggered again to get delta
from R/3 back. If its full update,request is deleted from the datatarget and Infopackage
is triggered again to get full update.

5) BW Error: Time Stamp errors:

Possible Causes: This can happen when there is some changes done on datasource and
datasource is not replicated.
Solution: Execute T code SE38 in BW give programme name as
RS_Transtrucuture_activate and execute the programme. Give InfoSource and Source
System and activate. This will replicate the datasource and its status is changed to
active. Once this is done, delete the request by changing technical status to red and
trigger InfoPackage to get delta back from source system.

Replicate datasource as shown in the screen shot below.

Go to SE38 and execute program RS_Transtrucuture_activate ,mention source and name

of the Infosource.

Delete request from the datatarget and trigger Infopackage again.to get either delta or
full data.

6) BW Error: Error log in PSA- Error occurred while writing to PSA.:

Possible Causes: This is because of corrupt data or data is not in acceptable format to
BW.
Solution: Check the cause of the error in Monitor in detail tabsrip.This gives the record
number and Infoobject having format issue. Compare the data with correct values and
determine the cause of failure. Change the QM status of request in datatarget to red and
delete the request. Correct the incorrect data in PSA and then upload data into data
target from PSA.

Step1:
If the request is directly into datatarget, take data in PSA also to correct this issue.
Delete error request from datatarget and Go to PSA to investigate the issue.
Look for messages in Monitor, which may give name of the Info Object causing the error.
Normally # character in the last is not permitted in BW.
Filter the records based on Status and start correcting the records. Once they are
complete, upload data from PSA back into datatarget.

7) BW Error: Duplicate data error in Master data upload:

Short Dump message:

"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLRSDRO " or "LRSDROF07 "
"START_RSODSACTREQ_ACTIVATE"

Possible Causes: This can happen if there are duplicate records from the source
system. BW do not allow duplicate data records.

Solution:
To check for records which are duplicate in master data characteristic, Go to RSRV
transaction

Select name of the characteristic and execute, this will give first 50 records for the
problem. Remove duplicates from the Master data and then upload data back by
triggering Infopackage again.

8) BW Error: Error occurred in the data selection

Possible Causes: This can occur due to either bug in the infopackage or incorrect data
selection In the infopackage.

Solution: Data selection checked in the infopackage and job is started again after
changing the technical status to red and deleting the error request from the data target.

There was bug found in one Infopackage eg.

Value Type field was getting changed after the job runs once. Everytime this need to be
corrected.

9) BW Error: Processing (data packet): No data:

Possible Causes: This can be because of some issue with source system with datasource.
Delta update program can be one of the issue.

Solution: Go to R/3 source system, See how many records are there in delta in RSA7
transaction. If the records are Zero and you are sure that number of records can not be
zero, then check for update Program which might not be running or stucked. Check for
BD87 ,SMQ1, SM58 for solution to error. Error logs can suggest the solution to problem.

10) BW Error: Process Chain failed

Possible Causes: Errors occurred in one of the job in the process chain

Solution: Attend failure manually and go to process chain log for today and right click on
the next job and select Repeat Option. This will execute all remaining jobs in process
chain.

11) BW Error: Errors occurred in (IDocs and TRFC)

Non Updated IIDOCs found in the source system.

Possible Causes: This can happen when in source system job is terminated or source
system or BW is not available for whole period of data upload. This can also happen if
resources are not sufficient in source system.

Solution: IIDOCs need to be processed manually either in OLTP or in BW depending on

the failure. Error message in monitor in status tabstrip will take you to either BW or OLTP
wherever there is a problem. Process IDOCs, this will start the left over packets and will
finish the load.
This situation we have to check the Idocs so we have to check Idoc in WE05 and know
the status these are WE51, WE52, WE53 may be and next goto WE 19 there we have to
execute the exist Idoc with successfully loaded Idoc.

Go to Transaction ST22 or see relevant short dump in the monitor.

Execute transaction WE02 to see Non updated IDOCs.

Process them if they have yellow status.

12) BW Error: Processing (data packet): Errors occurred-Update ( 0 new / 0

changed ) : Errors occurred-Error records written to application log.

Possible Causes: This can be because of data not acceptable to datatarget although
data reached PSA.

Solution: Data checked in PSA for correctness and after changing the bad data data
uploaded back into datatarget from PSA.
Change QM status of request to red in datatarget and delete request from the
datatarget to edit PSA data. Go to PSA associated with this request and edit records to fix
the error reported in Monitor in Details tabstrip.

Reload data from PSA back into datatarget.

13) BW Error: Process Chains: Errors occurred in Daily Master Data

Possible Causes: This occurs when Transaction data is loaded before Master data.

Solution: Ensure to load Master data before Transaction data. Reload data depending on
update mode (Delta/Full Update)

14) BW Error: Errors occurred-Transfer rules ( 0 Records ) :

Possible Causes: These errors happen when the transfer rules are not active and
mapping the data fields is not correct

Solution: Check for transfer rules ,make relevant changes and load data again.

15) BW Error: Missing messages -Processing end: Missing messages

Possible Causes: This can be because of incorrect PSA data, transfer structure, transfer
rules, update rules and ODS.

Solution: Check PSA data, Transfer structure, transfer rules, Update rules or datatarget
definition.

16) BW Error: Other (messages): Errors occurred in data selection

Possible Causes: The 'valid from' date is smaller than the mimimum date, The 'valid
from' date is smaller than the mimimum date, Error in node time interval with the ID
00000011 . Details in next message, The 'valid from' date is smaller than the mimimum
date.

Solution: Change the selection option and reload data.

17) BW Error: Activation of ODS failed

Possible Causes: This happens when data is not acceptable to ODS definition. Data need to be
corrected in PSA

Solution: Check for Infoobject, which has caused this problem in the monitor details
tabstrip. Delete request from datatarget after changing QM status to red. Correct data in
PSA and update data back to datatarget from PSA.

18) BW Error: Source System not available

Possible Causes: This can happen when request IDOC is sent source system ,but the
source system for some reason is not available

Solution: Ensure that source system is available. Change technical status of request to
red and delete request from datatarget. Trigger Infopackage again to get data from
source system