Process Chain Monitoring - Approach and Correction
The process chain monitoring is an important activity in Business Warehouse
management mainly during support. So it is necessary to know different errors which
occurs during monitoring and take necessary actions to correct process chains in order to
support smoothly.
some points to remember while monitoring:
1.
In case of running local chain, right click and go to process monitor to check if there is
any failure in any process step. It may happen that there might be failure in one of the
parallel running process in the chain.
2.
Right click and select Display messages option to know more about reason of the
failure in any step of process chain.
3.
Try to correct step which takes longer time to complete by comparing with other
processes which are running in parallel.
4.
Check the lock entries on Targets in SM12 transaction. This will give you an idea for all
the locks for the target.
5.
Perform RSRV check to analyze the error and correct it in relevant scenarios.
Monitoring - Approach and Correction
Description
Approach/Analysis
Correction
Failure in the
Trigger the chain ahead if indexes
Delete Index or Go to the target and check if
are already deleted in other process
Create Index
any load is running
chain
step
Compare the last run time of
job. If it taking more time,
Long running check system logs in SM21
Delete Index or and server processes in
SM51
Create Index
job
Check the SM12 transaction
entries for any locks on
target from some other step
Attribute
change run
failure
Roll up failure
Check the error message
Inform BASIS team with system log
and server processes details
Stop the delete index or create index
and repeat it once lock is released
Check the lock on Master Data
objects used in Infocube and repeat
the step
Error message roll up failed
Wait till attribute change run is
due to Master Data table lock
completed and start the roll up again
in attribute change run
-
Open RSDDBIAMON2 transaction to
check any issues in BI Accelerator
server.
Failure in Full data load
SQL error
Manually delete the indexes of target
and start the load again
This happens generally due
insufficient memory space
available while reading data
from tables.
Coordinate with BASIS team to
analyze the database space (DB02)
and take necessary action to reduce
the database size.
Check the data in PSA table
for any lower case letter or
special characters etc
Ask concerned R/3 person to correct
the data at R/3 side and load the
data again
Incorrect data
records in PSA It is very important to check
the PSA table to have
table
complete data in PSA before
reconstruction. Otherwise all
the data will not be updated
in target.
On immediate basis, delete the
request from target, correct the data
in PSA table and reconstruct the
request
Delta data load Failure
Delta load failed without any
error message.
Wait till last delta load is completed
Go to infopackage and check or correct it then start the
for last delta load in target if infopackage again.
it is successful or not.
Make sure that all data records are
PSA update failed due to job
available in PSA table and
termination or target lock
reconstruct the request
Delta load job failed in R/3
system or EDWH system
after all data has come to
PSA table
Delete the request from targets and
reconstruct it.
Delta load job failed at R/3
side without data PSA table
Make the status of the request Red
in process monitor and repeat the
delta load again. Make sure that data
is not doubled as repeat delta brings
last successful records as well. Check
the update mode of all key figures
i.e. overwrite or addition mode for
this.
Delta load job failed in EDWH Remove data mart tick from below
system without data PSA
source and start the delta package
table
again.
Or make the status of the load to
Red in case all key figures are in
overwrite mode.
Long running
delta load
Check the R/3 job in SM37 if Ask BASIS team to release the job
it is not released
from R/3 system
Compare the last successful
Ask BASIS team to repair the R/3
delta load time along with
connection
R/3 connection
Activation failure due to
incorrect value in the ODS
field.
Correct the data in PSA or check the
update logic for the corresponding
source field
Activation job termination
Try to activate the data manually
else check the jobs in SM37. If most
of the activation jobs are failing,
contact BASIS team.
DSO Activation
Some process types are not
triggered even if above
Miscellaneous process type is completed.
Triggering line doesnt show
any status.
Table Name
Usage
Check the process type
RSPCPROCESSLOG
log
Check the main chain for
RSPCCHAIN
local chain
Chain logs takes time to update in
chain log table i.e.
RSPCPROCESSLOG. Check the
system performance with BASIS
team as well.
