SAP BI/BW Production

Issues/Errors

Created by Surapu Reddy Sankar Reddy

Table of Contents
1.How to do manual update from the data packet if the records are not
updated to the data target
3
2. How to make the failed step to green in the Process chain
3. Load has failed in the process chain
4. DSO/ODS Activation failed

14

18

5. Errors while sending packages from OLTP to BI

6. Diagnosis 44
7. No IDocs could be sent to BI using RFC. 44
System Response

44

Further analysis:

44

Error handling:

44

44

1. How to do manual update from the data packet if the records

are not updated to the data target
Reason for failure: Here 1 data packet is not updated and 2 other has updated to the
data target.
Solution In this case we can do manual update
Go to the Monitor of the data target. In the status tab ->turn the signal lights from yellow
to red.

Click on the signal button. You will get the below screen.

Here select Status NOT OK button and click on save button.

Click on save button

Go to the Details tab ->Right click on the data packet -> click on Manual update

Now you can able to see the message in below status bar simulating data
You will get this message after some seconds.
Note:Some times you will get the message not able to update to data target.In this case
you want to repeat the load itself.

Now the data package has become green

Now you can see the message in Status tab -> data successfully updated

Now once again click on the signal button -> you will be able screen -> change the once
again to back to technical status and click on save button

Refresh the screen -> now the monitor status will turn to green

In the manage screen -> request will become green

2.How to make the failed step to green in the Process chain

Solution:How to make the failed step to green in the Process chain so that the below
steps can run further. (In some cases the load step will get failed and you have done the
load step manually. You want to make the load step in the process chain green. So that
the below steps can run)
7

Ex: Here update from the PSA has failed in the Process chain and we have
triggered the Job update from PSA manually

Right click on the failed step -> select Displaying Messages -> you will get the below
screen

GO to t-code SA38 -> Give the program name > RSPC_PROCESS_FINISH

Click on execute button

After clicking on execute button you will get this screen

From the display messages of the screen of the process chain

Copy the Variant & Instance -> Paste it in the SA38 screen
10

From process chain log view you can the Log ID and process chain name as seen in the
above screen

In this case the process type update from PSA is PSAPROCESS

You can get the different process types as below
Go SE11 ->in data base table give the table name ->RSPROCESSTYPES

11

Click on Display button you will get the below screen

Click on the content button as shown above

12

Click on the F4 of TYPE field -> you will get the below screen

Based on the failed step you can select the process type
13

After filling all the above details -> Click on the execute button

Now the failed step Update from PSA has become green and the below steps will run.

3.Load has failed in the process chain

Reason for failure: Job has terminated in the Source system
Solution:
14

Right click on the failed step -> select Process Monitor -> you will get into the monitor
screen

15

In the status tab you can able to see the Error message Job termination in Source
System

By clicking on the Request in the Header tab -> you can get the request Number as show
in the below screen

16

You can see the Source system of the job running in the Header tab - > Get the details of
the Source system.
Here the source system is - ILP Client 001(ILPCLNT001)
Go to the source system ILP Client 001(ILPCLNT001) -> Go to t-code SM37
In Job name give *REQU_D9C3PQ57AAQA6JHD1TJXC9H2N and in user give * and execute
it.
Now you can able to see the Job -> in the menu click on the Job Log and analyse the job.
Based on analyse you can repeat the failed load.

17

Right click on the failed step -> you will the repeat option ->click on it

18

After the repeat ion you can see the repeated load like this.

The repeated load got successful.

4. DSO/ODS Activation failed

Reason for failure: Batch job/ Resource process was not available
Solution:
19

DSO activation failed

Right click on DSO failed activation step -> select displaying messages

In the process monitor you can able to see the error message -> Resource error. No
batch process available. Process terminated.

20

Click on the Background tab -> now click on Batch monitor -> you can able to see the
DSO activation job as in below screen

Select DSO activation job -> In the menu bar click on the Job log -> you can able to get
the job log as show below

If you analyse the job log - > you can able to find out the reason for the failure of the job
21

In this case in the 3rd line you can see the message - Resource error. No batch process
available. Process terminated.
Solution: In this case you can repeat the failed DSO activation step or you can activate
the DSO manually by going to the DSO manage.

5.Load step has failed without IDOCS updating from Source system
Reason for failure:May be due to the heavy load on the system or system performance
issues

Failed load step

Right click on the failed step -> selection Process monitor

In the above screen status tab -> you can see NON-Updated Idocs found in the Source
system

22

Solution:In this case you can repeat the failed step.

Load got successful after repeat ion

6. After the maintenance delivery the Process chain has not run
Reason for failure:DTP is not in active version
Solution:

23

Go to RSPC -> try to activate the Process chain -> it has given the error message
Processes with Error

Double click on the DTP -> It will give the error message like below

Here the DTP are not in active version

Go to t-code RSA1 -> search for the DTP and activate it
After the DTP activation completes. You can trigger the process chain.

7. How to correct the error records/special characteristics in PSA

Reason for Failure: Error records/special characteristics in PSA
24

Solution:

This load got failed with error records in the process chain

Go to the failed step -> right click & select process monitor -> you will get the below
screen

Here you can see in the status tab -> Data records were selected in the PSA

25

Go to the details tab ->expand processing -> in the red data packet you can able to see
the error record.
Record 8112: Value '20101131 ' of characteristic 0DATE is not plausible
Here info object ->0DATE(contract end date)
Wrong value ->20101131 because November month doesnt have 31 days

Go to the cube -> mange and select the failed request and delete it

26

Go to monitor ->Double click on the PSA-Pledge button

You can able to get the above pop-up screen -> in those select Erroneous records as
shown in the screen& also change the number of records to maximum so that all the
records will be selected

27

Select all the data packet and click on continue button

Double click on the record -> here also you can able to get details like in which info
object is holding special characteristic/ wrong data

Here for the info object 0DATE(contract end date)

28

Value -> 20101131

Select first record and double click it >you will get the above screen -> here you can
able to edit the record which ever the value you want

Here we have changed the contract end date to 30.11.2010 as requested by the client by
R3 side.

29

After editing the data you can click on the save button

Go to the monitor of the cube ->From the Header tab -> copy the Info source name
(ZPCONS_BL_MONTH)

30

Go to RSA1 ->Info source -> search for Info source (ZPCONS_BL_MONTH)

31

Below the info source > you can able to find the data source -> right click on the data
source ->
Select Manage -> you can able to get the below screen

Select the failed request which you want to update & click on the 3 rd button scheduler->
As shown above

A new info package will be pop- up -> you can able to see which data targets it is
updating
32

Go to the scheduler tab -> click on the start button

Select immediate start -> click on continue button

33

Now Batch job has started as shown in the below status bar -> go to the monitor

Here you can see the status has become yellow

34

In the Details tab -> you can able to see processing -> Data packages has become
yellow
One by one data package will become yellow and the data package updated -> it will

become green
After the load completed -> status will become green

35

Automatically the process chain will become successful and the below loads will get
started

Another Example:

Go to the process monitor -> in the status tab -> Data records were selected in the PSA

In the details tab ->in the process tab -> data package -> Error records
Error records Messages:
Record 7052: Value "PRASSI_0264
" (HEX
5000520041005300530049005F0030003200360034000900 ) of charac
Record 7053: Value "PRASSI_0264
" (HEX
5000520041005300530049005F0030003200360034000900) of charac
36

Go to the cube Manage -> select the error records request and delete it

Go the cube Monitor -> status tab -> double click on the PSA-Pledge

37

Select the No of records to maximum, select Erroneous records & select all the data
packets and click on continue button as above

Select one record and double click it ...you will get the below screen

For the Info Object (PRM service Session) PRASSI_0264# - Remove the # symbol

38

After editing the error record -> save it -> follow the same procedure to edit all the error
records

Go to the load - monitor screen and copy the Info source name (EX. 8PYPRMO19)

Go to the t-code RSA1-> Info source -> search for your info source (EX. 8PYPRMO19)

39

If you expand info source ->you will the data source -> right click and select Manage

You can able to see the PSA list -> select the request which you want to update to the
data target-> click on the scheduler

You will get the Info package -> click start from the schedule tab

40

Refresh the screen after the load gets completed

After the completion of load -> the process chain automatically comes down and the next
step will run

8.How to analyse Short dump

Reason for failure: Load has failed with short dump

Load step has failed

41

Right click on the failed step -> process monitor -> you can able to see this error
messages

Click on the process -> you will get this screen -> double click on the error message ->
analyse the error
Here for ex. the error message is ->Dump: Internal session terminated with a
runtimeerror (see ST22) Data Package 000322

42

If you double click the error it will take you to the t-code ST22 or you can go directly to
ST22 and based on the time you can select the short dump

Now you read the short dump and analyse -> based on the analyse you can decide what
to do
In this case there is some problem in the program. We have rectified the problem and
repeated the load

43

9.RFC connection has failed/broken from the source system

Reason for failure: The connection between the source system and BW ha
failed/broken

44

Right click on the failed load -> Display messages -> you can able to see this screen

If you got to the Individual Messages -> you can see this error message

Click on the? Mark button -> you can able to see the below error messages
Errors while sending packages from OLTP to BI
Message no. RSM2011
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC ->in source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the
authorizations of the background user in the source system.

45

Click on the process monitor -> it will take you to the monitor of the load

Here you can see the error messages like -> check TRFC log/ Error while sending
packages from OLTP to BI

Details tab screen

Solution:
To check the source system connections go to t-code RSA1

46

Go to Modeling -> Source systems-> you can able to see all the source systems & BW
systems
Select your source system -> right click and select check

You can able to see the error message as above

Example The below is the another error message for the RFC connection failure
Source system connection from ECACLNT000 to IWPCLNT001 failed.
We are getting this error when we are check from t-code - RSA1
Error when opening an RFC connection
You tried to logon to check connection ECACLNT000 to the source system.
This was not successful.
47

10.How to correct Error records in DTP

Reason for Failure:Error records are struck in Error stack

Load has failed in the Process chain

Right click on the failed and select Process monitor

Here you can see the DTP processing Terminated -> Click on that -> you will get the error
message as below

By analyzing this -> you can come to know why the DTP has failed
Here it has failed with the error records

48

Click on the Error stack as shown above

Select data packet and click on continue button

These are the error records in the Error stack

49

Double click on the error record -> you can able to see the reason why it was
failed-> Inform to client or correct it if you know what to correct

After correcting the records-> come to the failed load step -> right click select Display
Variant -> you will get the below screen

Go to the Update tab -> click on Displaying Error DTPs button -> as shown in the below
screen Error DTP will be opened.

50

Check the data targets in the Update tab and click on the execute button -> the
corrected error records will be loaded through the Error DTP -> go to the Monitor and
check it

Go to the cube mange and make the status to green

51

In the DTP also the technical status will turn into green automatically

The process chain will automatically come down and the below steps will be completed

52