Sr.
NO Failure Error Description
Attribute Change Run failed - ALEREMOTEBW
was locked.
• The message appears in the Job Overview in
RSMO, or in “Display Message” option of the
Process in the PC.
• The exact error message would be like, “User
ALEREMOTE locked the load of master datas for
characteristic 0CUSTOMER”. Here it is specifically
for the 0CUSTOMER load. It may be different related
1 ` to Master Data InfoObject which is getting loaded.
Job Termination in the R/3 Source System
• The Exact Error message is "Job termination in
source system". The exact error message may also
differ, it may be “The background job for data
selection in the source system has been terminated”.
Both the error messages mean the same. Some
times it may also give “Job Termination due to
System Shutdown”.
• The message appears in the Job Overview in
RSMO, or in “Display Message” option of the
Process in the PC.
2 System
Analysis
During the Master data Loads, sometimes a lock is
set by the system user ALEREMOTE. This happen
because the HACR is runnning for some other MD
load at the same time when the system tries to carr
out the HACr for this new MD. This is scheduling
problem as due to the time clashing the error has
occured.
• If the job in R/3 system cancels due to some
reasons, then this error is encountered. This may b
due to some problem in the system. Some times it
may also be due to some other jobs running in
parallel which takes up all the Processors and the
jobs gets cancelled on R/3 side.
• The error may or may not be resulted due to Time
Out. It may happen that there would be some syste
issues like locks/DB Issues in the source system

Incorrect Data in the PSA
• The error message will appear in the job overview
and will guide you what exactly we need to do for the
error occurred.
The message on the bottom of the “Header” tab of
the Job Overview in RSMO will have “PSA Pflege”
written on it, which will give u direct link to the PSA
data
3 Data
• It may happen some times that the incoming data
to BW is having some incorrect format, or few
records have few incorrect entries. For example,
expected value was in upper case and data is in
lower case or if the data was expected in numeric
form, but the same was provided in Alpha Numeric
• The data load may be a Flat File load or it may be
from R/3. Mostly it may seem that the Flat File
provided by the users may have incorrect format.
 • Whenever a Job fails with an error “Time Out” it
means that the job has been stopped due to some
Error occurred due to Short Dump. reason, and the request is still in yellow state. And
• We would get a Time Out Error after the time which a result of the same it resulted in Time Out error. It
is specified in the Infopackage -> Time Out settings will lead to a short dump in the system. Either in R/
(which may or may not be same for all or in BW.
InfoPackages). But by that time in between, we may • Short dump may also occur if there is some
get a short dump in the BW system or in the Source mismatch in the type of incoming data. For exampl
System R/3. say date field is not in the format which is specified
• The message appears in the Job Overview in BW, then it may happen that instead of giving an
RSMO, or in “Display Message” option of the error it may give a short dump. Every time we trigg
Process in the PC. the load.
4 Short D
 Transact RFC Error – Non Updated IDOCs in the
Source System.
• Message appears in the bottom of the “Status” tab
in RSMO. The error message would appear like
“tRFC Error in Source System” or “tRFC Error in
Data Warehouse” or simply “tRFC Error” depending
on the system from where data is being extracted.
• Sometimes IDOC are also stuck on R/3 side as
there were no processors available to process them. not transferred from the source system to the
5 Idoc
ODS Activation Failed
• The exact error message would be like “Request
REQU_3ZGI6LEA5MSAHIROA4QUTCOP8, data
package 000012 incorrect with status 9 in
RSODSACTREQ”. Some times it may accompany
with “Communication error (RFC call) occurred”
error. It is actually due to some system error.
• The message appears in the Job Overview in
RSMO, or in “Display Message” option of the
Process in the PC.
• The exact error message is “ODS Activation
Failed”.
6 Data
• tRFC – Transact Remote Function Call Error,
occurs whenever LUW’s (Logical Unit of Work’s) ar
destination system.
• During data load in ODS, It may happen sometim
that the data gets extracted and loaded completely
but then at the time of the ODS activation it may fa
giving status 9 error.
• Or due to lack of resources, or cause of an existin
failed request in the ODS. For Master Data it is fine
we have an existing failed request.
• This happens as there are Roll back Segment
errors in Oracle Database and gives an error ORA-
00060. When activation of data takes place data is
read in Active data table and then either Inserted o
Updated. While doing this there are system dead
locks and Oracle is unable to extend the extents.

Time Stamp Error.
• The message appears in the Job Overview in
RSMO, or in “Display Message” option of the
Process in the PC. As the "Data Source needs to be (TR) are showing active status when checked. But
Replicated. The Transfer rules are inactive"
7 System
Caller 70 is missing.
• The exact error message is “System response
"Caller 70" is missing”.
• It may happen that it may also log a short dump in
the system. It can be checked at "Environment ->
Short dump -> In the Data Warehouse".
8 System
• The “Time Stamp” Error occurs when the Transfe
Rules/Structure (TR/TS) are internally inactive in th
system.
• They can also occur whenever the DataSources
are changed on the R/3 side or the DataMarts are
changed in BW side. In that case, the Transfer Rul
they are actually not, it happens because the time
stamp between the DataSource and the Transfer
Rules are different.
• This error normally occurs whenever BW
encounters error and is not able to classify them.
There could be multiple reasons for the same
1) Whenever we are loading the Master Data for th
first time, it creates SID’s. If system is unable to
create SIDs for the records in the Data packet, we
can get this error message.
2) If the Indexes of the cube are not deleted, then i
may happen that the system may give the caller 70
error.
3)Whenever we are trying to load the Transactiona
data which has master data as one of the
Characteristics and the value does not exist in
Master Data table we get this error. System can ha
difficultly in creating SIDs for the Master Data and
also load the transactional data.
4) If ODS activation is taking place and at the same
time there is another ODS activation running parall
then in that case it may happen that the system ma
classify the error as caller 70. As there were no
processes free for that ODS Activation.
5) It also occurs whenever there is a Read/Write
occurring in the Active Data Table of ODS. For
example if activation is happening for an ODS and
the same time the data loading is also taking place
the same ODS, then system may classify the error
as caller 70.
6) It is a system error which can be seen under
the “Status” tab in the Job Over View.

SAP R/3 Extraction Job Failed.
• The exact error message normally can be seen in
the source system where the extraction occurs. In
BW the process for program in the PC will fail.
• This Process is placed before the InfoPackage
triggers, hence if the extraction program in R/3 is still
running or is not complete, or is failed, the
InfoPackage will not get triggered. Hence it becomes
very important to monitor such loads through RSPC
rather than through RSMO.
9 System
File not found (System Command for file check
failed).
• The error message will turn the System Command
Process in the PC “Red” and the UNIX Script which
has failed will have a specific return code which
determines that the script has failed.
•Or in some specific cases the Status tab in RSMo
would show as "No Data available in Source
10 System system."
There are certain jobs which are triggered in R/3
based upon events created there. These events ar
triggered from SAP BW via ABAP Program attache
in Process Chains. This extract job also triggers
along with it a extract status job. The extract status
job will send the status back to BW with success,
failure. Hence it is important that the extract job, an
the extract status job both get completed. This is
done so that on completion of these jobs in R/3,
extraction jobs get triggered in R/3 via Info pack fro
BW. Error may occur in the extract job or in the
extract status job.
• The system command process is placed in a PC
before the infopackage Process. Hence it will chec
for the Flat File on the application server before the
infopackage is triggered. This will ensure that when
the load starts it has a Flat File to upload.
• It may happen that the file is not available and the
system command process fails. In that case it will n
trigger the InfoPackage. Hence it is very important
monitor the PC through RSPC.
 • Many a times, particularly with respect to HACR
while the Program is doing realignment of
aggregates it needs lot of temporary table space
[PSATEMP]. If there is a large amount of data to be
processed and if Oracle is not able to extend the
tablespace it gives a dump.
• This normally happens if there are many
aggregates created on the same day or there is a
large change in the incoming Master data /
Hierarchy, so that large amount of temporary
Table space issue. memory is needed to perform the realignment.
• The Error ORA - 01653 and ORA - 01688 – • Also whenever the PSAPODS (Which houses the
Relates to issues with table space. It will give error many tables) is full, the data load / ODS Activation
as the ORA number which asks to increase the table stops and hence we may get failures.
11 System space.

This error is usually seen when the table behind

Request Yellow (or Red) and Short Dump with
DBIF_RSQL_SQL_ERROR
The Details tab in the RSMO would give a message
12 Short D as "Short Dump in the Source system"
ODS is getting updated from more than one source
system simultaneously. Here the data packets from
more than one request contain one or more commo
records. This gives rise to deadlock while updating
inserting records into the ODS table and
subsequently a short dump is encountered leading
the failure of one request. The solution is to cance
the loads and run them serially. A possible long ter
solution is to load the data up to the PSA in paralle
and then load the ODS table from the PSA in seria
(Here change the InfoPackage to option ‘PSA only
and tick ‘Update subsequent data targets’).

Here the request remains yellow (in process) and

with the same details (as seen in the details tab of
the monitor) for an abnormally long time. Many-a-
times, the port for communication is not open and r
Missing data or information IDOC from the starting the load helps. For long running jobs, it ma
13 Idoc source system not be advisable to restart the extraction

Master data load may fail due to invalid characters

(may be coming from foreign languages etc.). Here
the invalid characters need to be analyzed to verify
14 Data Invalid character error that these are actually required.

The error indicates that some master data (on whic

the hierarchy is to be created) is not loaded (or
activated) as yet. Find out the node ID and
15 Data Hierarchy load fails with error ‘Incorrect Node ID’. corresponding master data.
The error indicates that the generated Hierarchy file
Hierarchy load fails with error ‘Incorrect is Incomplete. BW when trying to load a Hierarchy
Hierarchy Structure with Consistency Check’ / file, which is not generated completely, gives this
16 Data NodeID XXXXX not included in the Hierarchy. error.

DATASET Errors: Short dump with Various
DATASET errors
17 System
Data extraction from APO or another system
remains yellow while you do not see any
18 System processes active in APO (or the other system).
19 Data Divide by Zero error
HACR performance Problem
19 PerformaHACR takes long time.
RSRV Analysis:
Indicates Index of Master data used as Dimension of
20 Performathe cube has a corrupt Index or is inconsistent.
Application Buffer problem
HACR or any load gives a dump with error
21 Applicati insufficient application memory buffer.
22 Data Itab_duplicate_key error
The DATASET Errors like DATASET cant write, ca
read etc occurs when there is a Problem with the
Unix file systems authorizations or Unix file system
full. For example: The Archive Program trying to
move file from the work directory to archive directo
and since there is no free space in the archive
directory the Program Fails. Or the Program
generating a File (Say Hierarchy file) in the work
directory does not produce a complete file since
there is no free space left in the work directory.
Thereby resulting in Partial files and load failures d
to partial files in case of Hierarchy.
There may be processes running in the APO or oth
systems that terminate any active processes. For
e.g. when the APO check-point runs, it terminates
any processes going on in the system.
If there is a code in transfer rule which any division
and in case if divide by zero error is encountered th
loads gives a short dump with error like saying “Loa
Terminated at Customer’s request”. In case of simi
error look for routines in transfer rules. The detail ta
of the monitor also tells the record number.
Normally the size of the application buffer is set
according to recommendations by SAP. However a
instances if there is large data which is coming in,
major change in R/3, or any Data error/ code error.
If Master data is not active, this table will find the
duplicate entries while loading and load will fail by
giving the short dump.
 The check for referential integrity occurs for
transaction data and master data if they are flexibly
updated. When checking for referential integrity, th
Data Referential Integrity: errors are highlighted and returned to the error
MASTER DATA (0CCust_sales) load failed as value handler. The error handler locates the original PSA
23 Data ZZZZ does not exist in master table for 0Customer. records and writes the corresponding log.

It may happen that there is transaction which has

taken place for particular load. Or incase of delat
loads there is no changes. This would result in givin
anerror message as "No data available in the sourc
system". As a result the load would remaing hangin
ie the QM status would be yellow and if not change
24 Data No Data found in the soucre system then the load would fail due to processing overdue

It might happen that the Master Data 0Customer w

loaded much before the transactional data load and
by the time the transactional data load was started
some transactions has taken place in the OLAP
No SID found for a characteristics sytem and a new Customer has got created. As a
For example consider a Transactional Data load has result the Transactional Data load which would try
failed due to no SID found for the characteristic get the SID for the master data would not find it
25 Data 0Customer. would fail.
 Resolution/Possible actions to be carried out

• Check the error message completely and also check the long text
of the error message, as it will tell you the exact Master Data which
is locked by user ALEREMOTE.
• The lock which is set is because of load and HACR timing which
clashed. We first need to check RSA1 -> Tools -> HACR, where in
we would get the list of InfoObjects on which HACR is currently
running. Once that is finished only then, go to the Tx Code SM12.
This will give you few options and couple of default entries. When
we list the locks, it will display all the locks set. Delete the lock for
the specific entry only else it may happen that some load which
was running may fail, due to the lock released.
ster data Loads, sometimes a lock is • Now we choose the appropriate lock which has caused the failure,
em user ALEREMOTE. This happens and click on Delete. So that the existing lock is released.
HACR is runnning for some other MD Care should be taken that we do not delete an active running job.
me time when the system tries to carry Preferable avoid this solution
or this new MD. This is scheduling • When HACR finishes for the other Master Data, trigger Attribute
e to the time clashing the error has change run fot this Master Data.

• First check the job status in the Source System. It can be checked
through Environment -> Job Overview -> In the Source System.
This may ask you to login to the source system R/3. Once logged in
it will have some pre-entered selections, check if they are relevant,
and then Execute. This will show you the exact status of the job. It
should show “X” under Canceled.
• The job name generally starts with “BIREQU_” followed by system
generated number.
• Once we are confirm that this error has occurred due to job
R/3 system cancels due to some cancellation, we then check the status of the ODS, Cube under the
this error is encountered. This may be manage tab. The latest request would be showing the QM status as
roblem in the system. Some times it Red.
ue to some other jobs running in • We need to re-trigger the load again in such cases as the job is
takes up all the Processors and the no longer active and it is cancelled. We re-trigger the load from BW.
elled on R/3 side. • We first delete the Red request from the manage tab of the
y or may not be resulted due to Time InfoProvider and then re-trigger the InfoPackage.
ppen that there would be some system • Monitor the load for successful completion, and complete the
ks/DB Issues in the source system further loads if any in the Process Chain.

n some times that the incoming data
g some incorrect format, or few
ew incorrect entries. For example,
e was in upper case and data is in
if the data was expected in numeric
ame was provided in Alpha Numeric.
d may be a Flat File load or it may be
tly it may seem that the Flat File
e users may have incorrect format.
• Once confirmed with the error, we go ahead and check the
“Detail” tab of the Job Overview to check which Record, field and
what in the data has the error.
• Once we make sure from the Extraction, in the Details tab in the
Job Overview that the data was completely extracted, we can
actually see here, which record, which field, has the erroneous
data. Here we can also check the validity of the data with the
previous successful load PSA data.
• When we check the data in the PSA, it will show the record with
error with traffic signal as “Red”. In order to change data in PSA, we
need to have the request deleted from Manage Tab of the
InfoProvider first, only then it will allow to change the data in PSA.
• Once the change in the specific field entry in the record in PSA is
done, we then save it. Once data in PSA is changed. We then
again reconstruct the same request from the manage tab. Before
we could reconstruct the request, it needs to have QM status as
“Green”.
• This will update the records again which are present in the
request.
• Monitor the load for successful completion,
and complete the further loads if any in the
Process Chain.
NOTE: Before changing the Data from the PSA getting it
confirmed
from the OSC/Client whether your authorised to change the
Data in the PSA.

Job fails with an error “Time Out” it
e job has been stopped due to some
e request is still in yellow state. And as
same it resulted in Time Out error. It
hort dump in the system. Either in R/3
may also occur if there is some
e type of incoming data. For example
s not in the format which is specified in • Monitor the load for successful completion, and complete the
ay happen that instead of giving an
ve a short dump. Every time we trigger
• Usually “Time Out” Error results in a Short Dump. In order to
check the Short Dump we go to the following, Environment -> Short
Dump -> In the Data Warehouse / -> In the Source System.
• Alternatively we can check the Transaction ST22, in the Source
System / BW system. And then choose the relevant option to check
the short dump for the specific date and time. Here when we check
the short dump, make sure we go through the complete analysis of
the short dump in detail before taking any actions.
• In case of Time Out Error, Check whether the time out occurred
after the extraction or not. It may happen that the data was
extracted completely and then there was a short dump occurred.
Then nothing needs to be done.
• Inorder to check whether the extraction was done completely or
not, we can check the “Extraction” in the “Details” tab in the Job
Overview. Where in we can conclude whether the extraction was
done or not. If it is a “full load” from R/3 then we can also check the
no. of records in RSA3 in R/3 and check if the same no of records
are loaded in BW.
• In the short dump we may find that there is a Runtime Error,
"CALL_FUNCTION_SEND_ERROR" which occurred due to Time
Out in R/3 side.
• In such cases following could be done.
• If the data was extracted completely, then change the QM
status from yellow to green. If “CUBE” is getting loaded then
create indexes, for ODS activate the request.
• If the data was not extracted completely, then change the
QM status from yellow to red. Re-trigger the load and
monitor the same.
further loads if any in the Process Chain.

sact Remote Function Call Error,
ver LUW’s (Logical Unit of Work’s) are
d from the source system to the
stem.
oad in ODS, It may happen sometimes
ets extracted and loaded completely,
time of the ODS activation it may fail
error.
k of resources, or cause of an existing
in the ODS. For Master Data it is fine if
xisting failed request.
s as there are Roll back Segment
e Database and gives an error ORA-
activation of data takes place data is
data table and then either Inserted or
e doing this there are system dead
cle is unable to extend the extents.
• Once this error is encountered, we could try to Click a complete
Refresh “F6” in RSMO, and check if the LUW’s get cleared
manually by the system.
• If after “couple” of Refresh, the error is as it is, then follow the
below steps quickly as it may happen that the load may fail with a
short dump.
• Go to the menu Environment -> Transact. RFC -> In the Source
System, from RSMO. It asks to login into the source system.
• Once logged in, it will give a selection screen with “Date”, “User
Name”, TRFC options.
• On execution with “F8” it will give the list of all Stuck LUW’s. The
“Status Text” will appear Red for the Stuck LUW’s which are not
getting processed. And the “Target System” for those LUWs should
be the BW Production system. Do not execute any other IDOC
which is not related have the “Target System”.
• Right Click and “Execute” or “F6” after selection, those LUW’s
which are identified properly. So that they get cleared, and the load
on BW side gets completed successfully.
• When IDocs are stuck go to R/3, use Tcode BD87 and expand
• Whenever such error occurs the data is may or may not be
‘IDOC in inbound Processing’ tab for IDOC Status type as 64 (IDoc
completely loaded. It is only while activation it fails. Hence when we
ready to be transferred to application). Keep the cursor on the error
see the details of the job, we can actually see which data package
message (pertaining to IDOC type RSRQST only) and click
failed during activation.
Process tab (F8) . Ths will push any stuck Idoc on R/3.
• We can once again try to manually Activate the ODS, here do not
• Monitor the load for successful completion,
change the QM status as in Monitor its green but within the Data
and complete the further loads if any in the Process Chain.
Target it red. Once the data is activated QM status turns into Green
.
• For successful activation of the failed request, click on the
“Activate” button at the bottom, which will open another window
which will only have the request which is/are not activated. Select
the request and then check the corresponding options on the
bottom. And then Click on “Start”
• This will set a background job for activation of the selected
request.
• Monitor the load for successful completion, and complete the
further loads if any in the Process Chain.
• In case the above does not work out, we check the size of the
Data Package specified in the InfoPackage. In InfoPackage ->
Scheduler -> DataS. Default Data Transfer. Here we can set the
size of the Data Package. Here we need to “reduce” the maximum
size of the data package. So that activation takes place
successfully.
• Once the size of the Data Package is reduced we again re trigger
the load and reload the complete data again.
• Before starting the manual activation, it is very important to check
if there was an existing failed “Red” Request. If so make sure you
delete the same before starting the manual activation.
• This error is encountered at the first place and then rectified as at
that popint in time system is not able to process the activation
process via 4 different Parallel processes. This parameter is set in
rscusta2 transaction. Later on the resources are free so the
activation completes successfully.
• As a permanent solution, ask DBA to increase the initrans
and Maxtrans on the active data table.
 • Whenever we get such an error, we first need to check the
Transfer Rules (TR) in the Administrator Workbench. Check each
rule if they are inactive. If so then Activate the same.
• You need to first replicate the relevant data source, by right click
on the source system of D/s -> Replicate Datasources.
• During such occasions, we can execute the following ABAP
Report Program “RS_TRANSTRU_ACTIVATE_ALL”. It asks for
amp” Error occurs when the Transfer Source System Name, InfoSource Name, and 2 check boxes. For
e (TR/TS) are internally inactive in the activating only those TR/TS which are set by some lock, we can
check the option for “LOCK”. For activating only those TR/TS which
o occur whenever the DataSources are Inactive, we check for the option for “Only Inactive”.
n the R/3 side or the DataMarts are • Once executed it will activate the TR/TS again within that
W side. In that case, the Transfer Rules particular InfoSource even though they are already active.
ing active status when checked. But • Now re-trigger the InfoPackage again.
lly not, it happens because the time • Monitor the load for successful completion, and complete the
n the DataSource and the Transfer further loads if any in the Process Chain.
erent.

rmally occurs whenever BW

ror and is not able to classify them.
e multiple reasons for the same
we are loading the Master Data for the
eates SID’s. If system is unable to
r the records in the Data packet, we
ror message. • If the Master Data is getting loaded for the first time then in that
es of the cube are not deleted, then it case we can reduce the Data Package size and load the Info
hat the system may give the caller 70 Package. Processing sometimes is based on the size of Data
Package. Hence we can reduce the data package size and then
we are trying to load the Transactional reload the data again. We can also try to split the data load into
s master data as one of the different data loads
s and the value does not exist in • If the error occurs in the cube load then we can try to delete the
able we get this error. System can have indexes of the cube and then reload the data again.
eating SIDs for the Master Data and • If we are trying to load the Transactional and Master Data
ransactional data. together and this error occurs then we can reduce the size of the
vation is taking place and at the same Data Package and try reloading, as system may be finding it
nother ODS activation running parallel difficult to create SID’s and load data at the same time. Or we can
se it may happen that the system may load the Master Data first and then load Tranactional Data
ror as caller 70. As there were no • If the error is happening while ODS activation cause of no
e for that ODS Activation. processes free, or available for processing the ODS activation, then
rs whenever there is a Read/Write we can define processes in the T Code RSCUSTA2.
e Active Data Table of ODS. For • If error is occurring due to Read/Write in ODS then we need to
vation is happening for an ODS and at make changes in the schedule time of the data loading.
the data loading is also taking place to • Once we are sure that the data has not been extracted
S, then system may classify the error completely, we can then go ahead and delete the red request from
the manage tab in the InfoProvider. Re-trigger the InfoPackage
m error which can be seen under again.
ab in the Job Over View. • Monitor the load for successful completion, and complete the
further loads if any in the Process Chain.
 • We login to the source system and then check the Tx Code
SM37, for the status of the job running in R/3. Here it will show the
exact status of the running job.
• Enter the exact job name, user, date, and choose the relevant
options, then execute. It will show a list of the job, which is Active
with that name. You may also find another job Scheduled for the
next load, Cancelled job if any, or previous finished job. The active
job is the one which is currently running.
• Here if the job status for the “Delay(sec.)” is increasing instead of
“Duration(sec.)” then it means there is some problem with the
extraction job. It is not running, and is in delay.
• It may happen sometimes that there is no active job and there is a
job which is in finished status with the current date/time.
• The extract job and the status job both needs to be checked,
because it may happen that the extract job is finished but the
ain jobs which are triggered in R/3 extract status job has failed, as a result of which it did not send
vents created there. These events are success status to BW. But the extraction was complete. In such
SAP BW via ABAP Program attached cases, we manually change the status of the Extract Program
ains. This extract job also triggers Process in the PC in BW to green with the help of the FM
extract status job. The extract status “ZRSPC_ABAP_FINISH”. Execute the FM with the correct name of
he status back to BW with success, the Program process variant and the status “F”. This will make the
it is important that the extract job, and Process green triggering the further loads. Here we need to check if
tus job both get completed. This is there is no previous Extract Program Process is running in the BW
n completion of these jobs in R/3, system. Hence we need to check the PC logs in detail for any
s get triggered in R/3 via Info pack from previous existing process pending.
y occur in the extract job or in the • Monitor the PC to complete the loads successfully.
job.

• Whenever the system command process fails it indicated that the

file is not present. We right click on the Process and “Display
Message” we get to see the failed script. Here we need to check
the return code.
• Here if exit_status is –1 then failure i.e. Process becomes Red,
else it becomes Green in PC.
• We need to check the script carefully for the above mentioned
exit_status. And then only conclude that the file was really not
available.
• Once confirmed that the file is not available we need to take
command process is placed in a PC appropriate actions.
package Process. Hence it will check • We need to identify the person who is responsible for FTPing the
e on the application server before the file on the Application server. A mail already goes to the
triggered. This will ensure that when responsible person, via the error message in the Process. But we
it has a Flat File to upload. also need to send a mail, regarding the same.
n that the file is not available and the • The Process Chains which are having the system command
and process fails. In that case it will not Process in them, and the corresponding actions to be taken.
oPackage. Hence it is very important to Note: If the Data is actually not going to be available in the
C through RSPC. Application Server then we need to change the QM status to
Green Manually.
s, particularly with respect to HACR
ram is doing realignment of
needs lot of temporary table space
f there is a large amount of data to be
d if Oracle is not able to extend the
gives a dump.
y happens if there are many
eated on the same day or there is a
n the incoming Master data /
that large amount of temporary
eded to perform the realignment.
er the PSAPODS (Which houses the
s full, the data load / ODS Activation
ce we may get failures.
• In case the table space is full then we need to contact the Basis
and accordingly ask for a increase in the size of the table space.
• The increase of the table space is done by changing some
parameters / allocating more space which is defined for individual
tables.
NOTE: Befotre contacting the Basis you need to make sure
that its a table space issue. Go to Sm21 Read the system log
for the corresponding time. It would give the Message as
"Unable to allocate Table space for the Table XXXX" and the
table name. This table would relevant to the particular load.

sually seen when the table behind

g updated from more than one source
aneously. Here the data packets from
e request contain one or more common
gives rise to deadlock while updating
ds into the ODS table and
a short dump is encountered leading to It may be possible that the job is set up in such a way that the
ne request. The solution is to cancel activation of data in the ODS takes place only after data is received
run them serially. A possible long term from all four regions. Thus, if the failing request is deleted the
oad the data up to the PSA in parallel correct requests will also be deleted. Hence it is required to change
the ODS table from the PSA in serial. the status of the failed job from red/yellow to green, activate the
the InfoPackage to option ‘PSA only’ ODS data and then re-start the load from the (failing) source after
te subsequent data targets’). correction of any possible errors.

est remains yellow (in process) and

details (as seen in the details tab of
or an abnormally long time. Many-a-
for communication is not open and re-
ad helps. For long running jobs, it may
ble to restart the extraction Contact the BASIS administrator to push the IDOC.

ad may fail due to invalid characters

ng from foreign languages etc.). Here,
racters need to be analyzed to verify After anaysing which are invalid characters validate the Characters
actually required. by using the transaction RSKC.

cates that some master data (on which
s to be created) is not loaded (or
yet. Find out the node ID and
master data.
cates that the generated Hierarchy file
BW when trying to load a Hierarchy
ot generated completely, gives this
After getting the Node ID and the Corresponding Master Data.
Once you get the Master Data load the same and activate the
Master data. After activating the Master Data load the hierarchy
again.
Run the Hierarchy file generation Program again and use that to
load the Hierarchy.
T Errors like DATASET cant write, cant
s when there is a Problem with the
ms authorizations or Unix file system is
ple: The Archive Program trying to
the work directory to archive directory
e is no free space in the archive
Program Fails. Or the Program
File (Say Hierarchy file) in the work
not produce a complete file since
e space left in the work directory.
ing in Partial files and load failures due
n case of Hierarchy.
processes running in the APO or other
erminate any active processes. For In this case the data extraction from these systems should be
APO check-point runs, it terminates scheduled in such a way that it does not overlap the check-point
s going on in the system. runs.

de in transfer rule which any division,

divide by zero error is encountered the
short dump with error like saying “Load
Customer’s request”. In case of similar
outines in transfer rules. The detail tab
also tells the record number.
Go to the PSA tab and see the record, in case you can correct the
error change the record manually in PSA and then choose read in
everything manually button. Now the records in PSA are read
manually into the Master data Object.

Use transaction RSRV to check the Database statistics and Index

of Cube and aggregates. Perform the check first. See the analysis.
In case of any statistics problem or Index problem it lists the errors.
Then choose the repair option to fix the errors. This should be often
checked to see if the Cube statistics and Indexes are up to
date.Contact the application team creating the aggregates and
check if some aggregates with least valuation can be deactivated. If
yes then deactivate the aggregates and then restart HACR. Don’t
be surprised if HACR completes in 5-10 minutes after the
aggregates were deactivated.

There are various master data tables P, I, H tables. You can check
all the tables related to the master data object. Use program
RSDMD_CHK* and specify the Info Object and run the analysis.
Use the repair option to fix all the inconsistencies.

ize of the application buffer is set

ecommendations by SAP. However at
ere is large data which is coming in,
in R/3, or any Data error/ code error.
is not active, this table will find the
es while loading and load will fail by
rt dump.
Contact Basis immediately if this error is encountered.
NOTE:Remember in order to increase the application buffer
size SAP system has to be shut down.
Active the Master data and restart the load.

referential integrity occurs for
ta and master data if they are flexibly
n checking for referential integrity, the
hlighted and returned to the error
error handler locates the original PSA
rites the corresponding log.
that there is transaction which has
r particular load. Or incase of delat
no changes. This would result in giving
ge as "No data available in the source
result the load would remaing hanging
us would be yellow and if not changed
would fail due to processing overdue.
n that the Master Data 0Customer was
before the transactional data load and
e transactional data load was started
ions has taken place in the OLAP
ew Customer has got created. As a
nsactional Data load which would try to
r the master data would not find it
Checked for the erroranoues records in the PSA of the IO
0CUST_SALES. Checked whether the the customer number exits
in the 0CUSTOMER. If not check in the R3 sytsem, if the data is
present load the Customer Master Data and then reload the master
Data 0CUST_sales and activate it. If the customer is not present in
the R3 system itself escalate the issue to the client as it is a data
problem.
Extract the data in the source sytem and check whether the data is
actually present or not. If the load is getting the data from a flat file
go to the Application server i.e transaction AL11 and go to the
relevant path and check whether if data is present. If data is not
present then change the QM status to manually green. If the data is
available check for the extractor job failure.
Check for the Master data in the R3 system if the data is available
in the R3 system load the Master data in BW and then manually
load the transactional Data. If the master data is not present in the
R3 system also then it’s a data issue and needs to be reported to
OSC or the Client.