1.

CONVERSION ISSUES
2. LOADING ISSUES
3. PERFORMANCE ISSUES
4. RETRACTION/LOCKING ISSUES
5. GENERAL
1. CONVERSION ISSUES

1. IDocs or TRFC Error Sending packages from OLTP to BW lead to errors Diagnosis: No IDocs
could be sent to the SAP BW using RFC. System response there are IDocs in the source system
ALE outbox that did not arrive in the ALE inbox of the SAP BW. Further analysis: Check the
TRFC log. You can get to this log using the wizard or the menu path "Environment -> Transact.
RFC -> in source system". Removing errors: If the TRFC is incorrect, check whether the source
system is completely connected to the SAP BW. Check especially the authorizations of the
background user in the source system. Analysis: If we see at the error message we find that the
failure is due to Non-arrival of IDOCs from Source System to BW. Resolutions: Reload the Master
Data manually again from Info-package at RSA1.

2) PROCESSING IS OVERDUE FOR PROCESSED IDocs: Diagnosis IDocs were found in the
ALE inbox for Source System that are not Updated. Processing is overdue. Error correction:
Attempt to process the IDocs manually. You can process the IDocs Manually using the Wizard or
by selecting the IDocs with incorrect Status and processing them manually. Analysis: After
looking at all the above error messages we find that the IDocs are found in the ALE inbox for
Source System that are not Updated. Resolutions: We can process the IDocs manually

3) ERROR AT SOURCE SYSTEM ASKING FOR REPLICATION OF DATASOURCES: Analysis:

If we see at the error message we find that the System is asking us to replicate the Data Source
System. Action to be taken: Go to RSA1 initial Screen & press Source System tab at LHS.
Reason for Failure: Diagnosis User ALEREMOTE is preventing you from loading texts to
characteristic 0COSTCENTER. The lock was set by a master data loading process with the
Request number (Data Package number) REQU_3XXXXXXXXXXXXXXXXXXXX (000001) on
20071001, 071055(985111).

4) System response: For reasons of consistency, the system cannot allow the update to continue,
and it has terminated the process. Procedure Wait until the process that is causing the lock is
complete. You can call transaction SM12 to display a list of the locks. If a process terminates, the
locks that have been set by this process are reset automatically. Analysis: After looking at all the
above error messages we find that the user is “Locked”. Action to be taken: Wait for sometime &
try reloading the Master Data manually again from Info-package at RSA1.

5) DATA ERROR: Analysis: After looking at all the above error messages we find 1st – That it is a
PC File Source System. 2nd - That there are Duplicate Data Records leading to error. Action to
be taken: We have to delete this Request & then rectify the Data in the Data source at the Source
System Level. After this we have to manually load the data.

6) OTHER TYPE OF DATA ISSUE: Detail Error Message Diagnosis 1 data records were marked
as incorrect in the PSA. The additional checking and processing of the 2 data package was
terminated in a customer routine. This was done intentionally or was due to a short dump being
intercepted. System response the data package was not updated. Procedure Correct the
incorrect data records in the data package (for example by manually editing them in PSA
maintenance). You can find the error message for each record in the PSA by double-clicking on
the record status. Analysis: After looking at all the above error messages we find that the PSA
contains incorrect record. Action to be taken: To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data
target from here.

7) Alfa Conversion Error: Analysis: Request REQU 3XXXXXXXXXXXXXXXXX, data package

001409 incorrect with status 9. Request REQU_3XXXXXXXXXXXXXXXXXXX, data package
001415 not correct Activation of data records from ODS object ZXXXXX10 terminated
Communication error (RFC call) occurred Action to be taken: Go to Transfer Rules. There select
that particular Info objects and double clicks on that. Go to routine there call function. DATA:
l_s_errorlog TYPE rssm_s_errorlog_int. CALL FUNCTION
'CONVERSION_EXIT_ALPHA_INPUT' EXPORTING INPUT = TRAN_STRUCTURE-zXXXX (Info
objects name) IMPORTING OUTPUT = RESULT.

8) Errors occurred in (IDocs and TRFC) Non Updated IDOCs 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: IDOCs need to be processed manually either in OLTP or in
BW depending on the failure. Error message in monitor in status tab strip 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 IDOCs in
WE05 and know the status these are WE51, WE52, WE53 may be and next go to WE 19 there
we have to execute the exist IDOCs with successfully loaded IDOCs. 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.

9) Caller 70 missing Possible Causes: IDOCs not processed completely. Solution: IDOCs
Problem, Either wait till time out & process IDOCs from detail monitor screen, or go to BD87 &
process IDOCs with status = YELLOW ( be careful while processing IDOCS from BD87, choose
only relevant IDOCs

10) We have created a user in quality system and transported the roles from dev to quality. User
type is Communication. In development system it worked fine while accessing the web reports
with this user. But in quality system the same user while accessing the web reports it says “No
namespace available" No authorization. Sol: You can check if the role has authorization for the
multiprovider. Also make sure you are giving proper inputs while executing the report. There are
chances that if you specify a range in your selection, the user is not authorized to view some of
those values. Also make sure your report has all the authorization relevant infoobjects from the
infoprovider, restricted by the appropriate authorization variables.

11) Am working on Reporting Authorizations. I have created authorizations for the Cube with
Required infoobjects and required values and i have created new user and role maintenance. In
that Role maintenance, Authorization Tab. i have added below components and updated Activity,
Reporting name, Type of Reporting component etc also. At the same time 1 profile is created
automatically. S_RS_AUTH S_RS_COMP S_RS_COMP1 S_RS_ICUBE

1) Now at the time of opening BEx it will showing the error like RFC Error (your not
having the Authorization due to RFC connection to your SYST)
2) if i add the SAP_ALL in the profile, now i am able to logon to BEx, but now in the report
it will showing all the values Ex Customer No: C100, C200.. to C1000 data available in
the Cube. but in the Authorization i have restricted C100 , C200 to C500 Only Please any
body tell me how to view particular user view particular data. Solution: Add one more
authorization object called S_RS_IOBJ. And add the info object Customer with restricted
values. You have to add S_RFC, authorization object for RFC connection, then no need
to include SAP_ALL.

12) If i want to delete the authorization object using rssm it shows `''Could not delete profile
RSR_00006134 from the C757446. user master Solution: the message says, that this
authorization Object is still in use in the profile RSR_00006134. Usually the newly defined
authorization object is inserted and generated into the SAP_ALL, SAP_NEW - Profile
automatically. Thus it's almost impossible an authorization object as soon it is saved. Check in
transaction SUIM for roles or profiles and look in which role/profile the object is used.

13) I am getting errors when opening a workbook. Actually the original query is changed after that
workbook was created. So When I am trying to run the workbook now, there are so many errors.
What should be done in order to reflect those changes done to the query into that workbook?
Solution: You should:
1. open the workbook with errors,
2. open the query that is contained in this workbook and has been changed,
3.execute this query,
4.save workbook.
2. LOADING ISSUES

1) ERROR WHILE LOADING PC FILE FROM DESKTOP / APPLICATION SERVER Analysis:

After looking at all the above error messages we find 1st – That it is a PC File Source System.
2nd – For uploading data from the PC File it seems that the file was not kept at the application
server & the job was scheduled in Background. Action to be taken: For running the job in
Background Transfer files to Application server & then load it from there. OR Else if you want to
load file from your desktop then don’t schedule the job in background instead select “Schedule
Immediately” option in the Info-Package.

2) JOB FAILURE AT SOURCE SYSTEM Diagnosis The background processing was not finished
in the source system. It is possible that the background processing in the source system was
terminated. System response There are incomplete data packets present. Further analysis: Go to
the background processing overview in the source system. You can get to this with the Wizard or
the menu path Environment -> Job Overview -> In the source system (This is the alternate path to
see the “Job Overview” at the Source System. Once there, check whether the background job
really was terminated. Note Please make sure that the correct date of request has been selected
in the selection screen of the overview. Action to be taken: At source system you can see the
reason for the Job Failure. Thus we need to take the action accordingly.

3) ERROR ASKING FOR INITIALIZATION Analysis: After looking at all the above error
messages we find that if we want to load data with the delta update you must first initialize the
delta process. Action to be taken: If you want to load data with the delta update you must first
initialize the delta process. Afterwards the selection conditions that were used in the initialization
can no longer be changed. But Initialization is a typical process that should not be carried out
without confirming with the onsite person in any case.

4) ERROR RELATED TO ACTIVATION Analysis: Here we can see that the Activation of ODS
has failed as the Request Status in the ODS may not be green. Action To be Taken: Go Right
Click on it◊ Select your ODS Object ◊to RSA1 & Select ‘Manage’. Select the Red Request & see
the reason for its failure. Rectify the error & then go for its activation.

5) TRANSACTION JOB FAILES GIVING MESSAGE: “NO SID FOUND FOR CERTAIN DATA
RECORD” Action to be taken: Load Master data for YXXXXXX. To load it, select its Info package
& at schedule tab select “Immediate” & start loading. - After this come to RSMO & select this
failed job. - Click on Detail tab. - Since in this case we see that the data is only getting loaded in
ODS & not in PSA thus we have to reload data manually through Info package. - If we have PSA
here then we need to take the following action:
1) Expand nodes under Detail tab.
2) Expand node “Processing (data packet): Everything OK”
3) Right click on “Data Package 1 (13321 Records ): Everything OK” under it.
4) Select Manual update option in the dropdown menu.

6) Fiscal Year Variant Error: Action to be taken: Go To SPRO: SAP Reference Maintain Fiscal
Year◊General BW settings◊Business Information Warehouse◊IMG Select Existing Z4 value and
Click on Periods Give the Calendar year◊Variant from which year you want then enter on that and
give the values as you want.

7) Table Space Errors Due to space problem these types of errors occur. So we will contact Basis
People. They will resolve these types of Problems by increasing the space.

8) Are there any new features to master data loading, which related to Language, IF so, please
let me know in detail. Solution: For master data loading you need to load the attributes and text
as per your data source you can give the text data. which are stores in the T tables. In the
language you can load what ever language you requires... if it is not supporting other than
EN..You can ask baisi to change the system settings and language as blank.
9) am loading data from Flat File to DSO.I got the following error while activating Data in DSO.
"No SID found for value ' 0500136A' of characteristic 0MAT_SALES" I have checked in Material
sales master data I have the value 0500136A in .If you see above error it showing some space in
front of 0500136A.I am not seeing that space in master data. It was edited again and loaded to
DSO and activated Then I got same error. Is it problem with Excel File formatting related. Please
throw some light on the issue. Solution: Edit your file do the changes and load the data and check
how the data is looking in PSA. Before loading do the Preview which we will get in the external
tab of the info package. It will shows all the errors which u will get if u load the data.

10) We are getting error when loading data into PSA. Error message is RSAR130 Error 5 when
adding to PSA .please suggest some possible solutions. We are facing this issue in Production
system. Solution: This error message is not very informative...though looks like a IDOCs error to
me. Please use tcodes ST22 to see the short dump. Also, you can find more details in SM37.

11) The ODS shows green under the status bar, however have a errors in the details TAB Under
the details tab the error message is as follows: (from Info Cube/ODS A99OP001 in Target system
P21CLNT300 : with errors ) Solution: It seems that some updates were done on the source
system side and while entering the value character has been entered which is not identified by
the BW system. The data has to be corrected in the source system, you will have to confirm it
with your client that what the data should be and for the time being you can load it till PSA and
correct the data in PSA, and push it manually. Give the PSA details to your client, it will contain
the data in source system format, and they will know what value has to be changed.

12) Error: Process overdue Solution: In the monitor, details tab, right mouse click on the red data
packet and manual update Some times, the system will let you update manual when right click on
the data packet which is red. Some times, the message popup and said can not update request, it
is in a data target. Then follow as below. Double click on the data target. In the Manage Data
Target, select the request and click delete button. When the request is deleted, arrow back to the
monitor. In the Details tab, right click the packet and click manual update. Usually all data packet
will be process in the background and turn green.

13) Failure Message: Activation of M records from ODS object YGTTPVAR terminated Solution:
Go to Monitor screen to check the failed record and click on it to see the Header. Double click on
data target in the above screen to go to the data target Double click takes you to the “Manage
Data Target” screen, click on Request tab and look for the records in red and delete them Go to
the following screen and double click on Data Target Following screen comes up and click on
Start:

14) How to delete the requests from PSA Solution: Go to PSA At the top level of the tree, search
the IP OFI_AR_3 Right click on Customer: Item level and chose “Delete PSA Data Once deletion
finish you go back and refresh the window and you will see the PSA empty

15) Error occurred in the source system Solution: IP 2LIS_12_VCITM_DELTA IP

2LIS_12_VCSCL_DELTA
1. Turned in red the delta.
2. Deleted bad request from data targets
3. Reran the request

16) Info package: 2LIS_11_VASCL_DELTA Error: Value 0001CL100000000000 not contained in

the master data table for YSHIPTO_S Solution:
1. Click on Detail tab.
2. It shows that data packet 5 and 12 contain incorrect value.
3. Click the PSA icon, the second icon on the menu bar. Input record count more than in
the packet to bring up all records in that packet. E.g. Data record no = 1 To = 16000 And
Continue. . High light Column Sales document and find 000067014.
 6.system bring back with found sales document highlighted. Exit from the pop up dialog
box.
7. Double click the highlighted record line.
8. Blank out all the fields except the first 3 fields which are grayed out.
9. Step 8 simulates ‘Delete’ record from PSA.
10. Repeat step 8 for all records which have ship to value ‘0’. 10. Once done save the
PSA and reprocess the data packets.

17) IP 0FI_AR_3 (Delta load) Error message from the source system
1) Go to Data Targets, and search for YGTGD004
2) Right mouse click on the ODS FIAR: Line Item and select Delete data Click on YES on
the next screen Select Delete entries Click on the check box
3) Next do a search on the data target ZANGDFIAR Right mouse click on the Accounts
Receivables cube and select Delete data Select Yes on the next screen Select Delete
entries on the next screen Hit the Check box on this screen Select Fact table and dims
4) Manually turn red to delta or delta init extract to red • Click on the Total option • Click
on Yes Select option Status NOT OK Click YES 3) Delete the entry in the initialization
option for source system via menu item Scheduler. • Go to the info Package • Go to
Scheduler – Initialization options for the source system Select the Info Package and
delete Click Yes Click Yes again
5) Check to see if the if there is an entry for 0FI_AR_3 in tcode RSA7 in R/3 and tcode
SMQ1 in R/3 (RSA7 in BW) (SMQ1 in R/3) If any entries exist, as shown above. Delete
6) Reinitialize delta in BW • From the monitor, click on the 0FI_AR_3 job. Go to the
Header tab and copy the below Go to Info Sources. Click on Info Sources . Do a search
for 0FI_AR_3
7) Double click on 0FI_AR_3 (Initial Load) and run the job NOTE: Info Source
8YGTGD004 gets triggered after a successful load of 0FI_AR_3 (Initial Load). Please
ensure the following:
1. The subsequent loading of 8YGTGD004 occurs successfully.
2. Info Cube ZANGDFIAR is available for reporting.

18) Error occurred in the source system Solution: Info source: 2LIS_11_VAITM ( Sales Order
Item Data (As of 2.0B) ) Info package: 2LIS_11_VAITM_DELTA
1. Search the IP
2. Right click in Source System + Replicate Data source
3. Activate transfer rules for an Info Source
4. Open the system
5. Right click in the Source system and chose change transfer rules
6. Click in Activate button ( Match icon)
7. Click in the paper icon to create a new one and type “Do not transport, activating
transfer rules” Once the update rules are activated. Make sure to
1) Close the system
2) Re-run the IP
3) Delete the dummy workbench request using TCODE SE10 Right click +
Delete

19) Error occurred in the source system Solution: Info source: YGTDS_GTDP_PLAW10 ( Shelf
Stable DP PLAW10 ) Info package: 9GTDP_PLAW10 - DPA -Istwerte Ladung für letzte Woche
(German) 9GTDP_PLAW10 - Load Actuals for last week ( English) Delete bad request from both
Data Targets Open a ticket for AMS SAP DSP team.

20) Error occurred when reading SID for Info Object '0INSP_LOT ' with value '010000106826 '
Info package name = IS_05_QVUDN_DELTA_QM_Usage_Decision_01 Master data to be fixed =
0INSP_LOT Master data description to be fixed = Inspection lot number Incorrect Value =
010000106826 Solution:
 1. Run again Info Package 0INSP_LOT_ATTR_QM_Insp_Lot_Num to load in Info Object
'0INSP_LOT ' the missing Inspection lot.
2. Once this has been completed, please run again Info package
2LIS_05_QVUDN_DELTA_QM_Usage_Decision_01.

21) Error: 0EMPLOYEE Error when writing in PSA Info source: 0EMPLOYEE Info package:
YGTHR_0EMPLOYEE_ATTR Error: Error when writing in PSA Solution:
1. Employee info package is part of the info package group ‘GTHR_Master_Data_Daily’
which is critical master data. Without this being successfully complete, transaction data
will not run.
2. Copy info package ‘YGTHR_0EMPLOYEE_ATTR’ from the Header tab and green
arrow back to BW Administrator Workbench: Modeling
3. Search the info package in the info package group. Once found click arrow down to
locate the info package group.
4. Double click on the info package group ‘GTHR_Master_Data_Daily’.
5. In the Schedule, click Jobs.
6. Click Execute .
7. High light the Job name which is released. Click Job on the menu bar and select
Schedule job and Repeat.
8. Unclick Periodic job and click immediate and save.
9. If refresh, the job will be running.
3. PERFORMANCE ISSUES

1): Failure occurred When delta Update is going on from one data target to another data target.
Possible Causes:
1. TRFC error
2. data is incorrect-error records.
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 it’s Full update, restart job again after deleting error request from the data target.

2) Maestro 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) Database Errors: Enable to extend Table, enable to extend the Index. 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. Info package for Delta update
is triggered again to get delta from R/3 back. If it’s full update, request is deleted from the data
target and Info package is triggered again to get full update. Once DBA confirms that space issue
is corrected, job is rerun to get data from source again.

4) 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 data target. Info package for Delta update is triggered again to get delta from R/3 back. If it’s
full update, request is deleted from the data target and Info package is triggered again to get full
update.

5) Time Stamp errors: Possible Causes: This can happen when there is some changes done on
data source and data source is not replicated. Solution: Execute T code SE38 in BW give
program name as RS_Transtrucuture_activate and execute the program. Give Info source and
Source System and activate. This will replicate the data source and its status is changed to
active. Once this is done, delete the request by changing technical status to red and trigger Info
package to get delta back from source system. Replicate data source as shown in the screen
shot below. Go to SE38 and execute program RS_Transtrucuture_activate ,mention source and
name of the Info source. Delete request from the data target and trigger Info package again. to
get either delta or full data.

6) 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 Info object having format issue.
Compare the data with correct values and determine the cause of failure. Change the QM status
of request in data target to red and delete the request. Correct the incorrect data in PSA and then
upload data into data target from PSA.

7) 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 Info
package again.
8) Error occurred in the data selection Possible Causes: This can occur due to either bug in the
info package or incorrect data selection In the info package. Solution: Data selection checked in
the info package and job is started again after changing the technical status to red and deleting
the error request from the data target. Value Type field was getting changed after the job runs
once. Every time this need to be corrected.

9) Processing (data packet): No data: Possible Causes: This can be because of some issue with
source system with data source. Delta update program can be one of the issues. 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, and SM58 for solution
to error. Error logs can suggest the solution to problem.

10) 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) 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 data target although data reached PSA. Solution: Data checked in PSA for correctness and
after changing the bad data uploaded back into data target from PSA. Change QM status of
request to red in data target and delete request from the data target to edit PSA data. Go to PSA
associated with this request and edit records to fix the error reported in Monitor in Details tab
strip. Reload data from PSA back into data target.

12) 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)

13) 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.

14) Error when writing data into ODS: DB_TABLE_SET_LOCK-1- Info package: YGT_MV_ACT –
Full ODS: YGTTPVAR Solution: Because Selection Criteria is too big; we have to change in
“Processing” tab and chose the 3rd option “Only PSA” and Update subsequently in data targets
and save the changes. We have to do the same for the 5 IP’s
1. Make a search of the ODS YGTTPVAR
2. Right click and delete data in ODS
3. Click Yes The following window will appear: Chose “Delete entries”, the following
window appear, click the green arrow to continue
4. Once deletion is complete then start the IPG again “TP_Infopackage_group_adhoc”

15) How to activate transfer rules for an Info Source Solution: If you get the error below, you have
to activate the update rules for the Info Source Start by opening the system with TCODES SCC4
and SE03 Once the system is open, Click on the Info Package (IP) which needs the update rules
activated. Click on the header tab and copy (ctrl+c) the data target From Modeling, click on Data
Targets and do a search for the data target (ctrl + v) Click here Right Mouse click on the data
target and select Change Click on the activate button Note: The system might ask you for a
workbench request. If this happens create a dummy workbench request and proceed. Once the
update rules are activated. Make sure to
4) Close the system
5) Re-run the IP
6) Delete the dummy workbench request using TCODE SE10
16) How to initialize the Delta – INIT Solution: Search the init IP
1. Double click in the IP
2. Scheduler menu
3. Click in Initialization options for source system The following window will appear Delete
the only request that appear Click in Yes in this window Close the window Go to
Schedule tab and click start button

17) How to reload a failed hierarchy info package Error: Hierarchy package prompts you to select
a hierarchy when attempting to reload it Solution:
1) Select the failed package, go to the header tab, and Copy the hierarchy.
2) Go to the Select hierarchy tab and do a search for the hierarchy, which was copied in
the step above
3) If no entries are found, click the button available hierarchies from OLTP
4) Once found, select the hierarchy and save it
5) Lastly, go to the Schedule tab and start the IP

18). How to reprocess a failed request I (try first) Solution: Click the failed request. On the menu
item->Click - Edit -> Init update -> setting for further update Click as follow in the pop up box.
From menu item, Click – Edit -> Update/Reversal -> Read everything in manually Click arrow
‘Incorrect data packets are now updated again. A background job will be created to reprocess the
request. Refresh and if successful the status will be green.

19) How to reprocess a failed request II (update from PSA) Solution: Click the failed request, and
go to the header tab Next double click on the data target. Go to the Requests tab and delete
failed request. Note: You must delete the bad requests from all data targets Exit the monitor and
click on PSA. Next, do a search for the request #. Right mouse click on the request and click Start
the update immediately. A background job will be created to reprocess the request. Refresh and if
successful the status will be green.

20) Activate and fill aggregates Solution: In order to speed the activation for aggregates, follow
the next procedure: 1. Make a search of the cube 2. Right click and chose “Manage” 3. Go to
“Performance” tab and click in “Refresh Statistics” button The following window will appear
Monitor this background job in SM37 and once this job finish, you can start with the aggregates
activation. Go to “Roll up” tab and click in “Aggregates” button The following window will appear:
Select all the Aggregates on the right side as showed below Click in the match icon “Activate and
fill” The next window will appear Click in the green arrow to “Fill aggregate” Chose option “Now”
to start immediately Then a job is scheduled Close the window.

21) To change the owner of a job: Solution: Select a modifiable job to change: From the top pull
down menu select JOB -> CHANGE Select the step with the user ID that needs to be changed
From the menu, select STEP -> CHANGE You can now edit the user and change to BW_ADMIN
Check and Save Exit and save the job.

22) How to activate aggregates for COPA

1. Once COPA ran
2. Open the system
3. Make a search of the cube YGTFCPA01
4. Right click and “Manage”
5. Go to “Environment” option from the menu and chose “Automatic request processing”
6. The following window will appear Check the option “Roll up data in the aggregate” and
save it Following window will appear Click in the little paper Click in save button to
continue Run statistics Go to performance tab and click in “Refresh Statistics” button A
job is going to be created Continue Monitor the job created in SM37 Once this job finish
Go to “Roll up” tab and click in “Aggregates” button. Select all the aggregates Click in the
match button “Activate and Fill” Click green arrow to continue Click “Now” A batch job
was now schedule Monitor the job
23) How to delete a record in the request in PSA Info source: 2LIS_03_BF - Delta IM Movements
Info package: YGTDS_2LIS_03_BF (Material movements from Inventory Control Error: Value '!S?
0X<40 ' (Hex ' ') of char. 0BATCH contains unauthorized characters. (In Details tab of the IP)
Note: For this kind of error is necessary to open a ticket in order the market provide us with their
approval to proceed with the deletion. Solution: First delete the bad request from data target: Next
find the packet number(s) of where the error occurred in the monitor by looking at the Details tab
in the monitor for that Info Package: Next, go to the PSA and search and open the bad request.
Open the PSA Data Packet and search for the string in the error. System bring back with found
sales document highlighted. Exit from the pop up dialog box. Double click the highlighted record
line. Blank out all the fields except the first 3 fields which are grayed out. Step 8 simulates ‘Delete’
record from PSA. Once done save the PSA and reprocess the data packets. Edit + Background
Edit + Read everything in manually If the following message appear: In this example, the error
message in the monitor is: Data Packet 3: Arrived in BW; Processing: Value '!S?0X<40 ' (Hex ' ')
of char. 0BATCH” 0BATCH is the Batch Number column. Do a column search for a portion of the
string that doesn’t contain special characters such as “!”, for instance, “<40”. Once the record is
found, delete all data in that row and save it.

24) Delete a bad request from info cube with aggregate Solution: When you have to delete a bad
request form an info cube with aggregates (rollup) you have to proceed as following:
1) Run the transaction RSA1, select the option 'Data Target' and select the info cube.
2) Click on the button to check the aggregates.
3) Select the aggregate that you need to switched off:
4) After select the aggregate (see above) you have to click on the button to deactivate it.
The status of the aggregate should turned to red. Note: If you want do delete the bad
request without proceed as above you will receive the following error message:
5) Return to transaction RSA1, select info cube, right mouse click and select the option
'Manage', find the request that need to be delete.
6) Delete the bad request.
7) Proceed with the steps 1 and 2.
8) Select the aggregate that you need to switched on.
9) After select the aggregate you have to click on the button to activate it.
10) Return to transaction RSA, select info cube, right mouse click and select the option
'Manage', select 'Rollup'
11) Select the option 'Selection' and run the job in background to fill the aggregates
again.

25. No SID found for value '000010012801 ' of characteristic 0COORDER Info source:
YGTDS_2LIS_03_BF (Material movements from Inventory Control) Info package: 2LIS_03_BF -
Delta IM Movements Data Target: YGTDSO40 Info object: 0COORDER Solution: Modeling + Info
Object + Search the Info object 0COORDER Right click + Activate Master Data This message will
appear (Master data for characteristic 0COORDER has been activated. Double click in Data
Target YGTDSO40 + Requests Delete the request in red Go back Go to monitor Edit + Setting for
further update + Packet should be processed in the background Wait until bad request is
deleted… Edit + Update Reversal + Read everything manually Wait….. Click Yes Background
processing successfully scheduled Then you can see the IP running again Now in green =) 26.
Error: 2LIS_11_VASCL yellow status for a long time Info source: 2LIS_11_VASCL (Sales Order
Schedule Line (As of 2.0B)) Info package: 2LIS_11_VASCL_DELTA Error: Yellow status for a
long time Action: Solution:
1. Double click Details tab, there is a data packet which is yellow. It may be hanged.
2. Double click Status tab. Double click traffic light of Total. Click Yes. Click red traffic
light and Save Click Yes. Status of Total becomes red.
3. Click the data packet which is yellow as the following: Data Packet 2: Arrived in BW;
Processing: This data packet was not updated in all data target Right click and select
Manual update. Processing will go on in the background. When it is done, the data
packet will turn green. If more than one packet is yellow, sometimes the procedure needs
to be repeated as case by case basis. When all data packets are green, the status light in
the right hand side should be green. If not the manual turning of Total status light should
be undone by resetting back the Total status light to ‘Delete status, back to request
statuses. Double click Status tab. Double click traffic light of Total. Click Yes and Click
‘Delete status, back to request status’ in Set Overall status box and save. Click Yes, the
status should be green.
4. RETRACTION/LOCKING ISSUES

1) 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 data target definition.

2) Other (messages): Errors occurred in data selection Possible Causes: The 'valid from' date is
smaller than the minimum date; The 'valid from' date is smaller than the minimum date, Error in
node time interval with the ID 00000011. Details in next message, The 'valid from' date is smaller
than the minimum date. Solution: Change the selection option and reload data.

3) 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 Info object, which has caused
this problem in the monitor details tab strip. Delete request from data target after changing QM
status to red. Correct data in PSA and update data back to data target from PSA.

4) 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
data target. Trigger Info package again to get data from source system.

5) Object corrupted- Delta Management of Master data lost but allows Full update. “Update Mode
R not supported. “ Possible Causes: This happened during mass failures due to database space
issue. Solution: Reinitialization or there is one program for repair of Info object. During
reinitialization ensure to use option of Only PSA, avoid duplicate data targetsuently into data
targets. Go to Transaction code RSRV to check consistency of Info object.

6) Error while opening file from the source system. Possible Causes: This happens when either
file is open or file is not deposited on server or not available. Solution: Arrange for file, delete
error request from data target and trigger Info package to load data from file.

7) Object locked by user Possible Causes: This can happen when user or ALEREMOTE is
accessing the same table. Solution: Change the technical status of job to red, delete request from
data target and trigger Info package again. If its delta update it will ask for repeat delta, Click on
Yes button.

8) While load is going on in R/3 table is locked Possible Causes: This happens when some data
source is accessing R/3 transparent table and some transaction takes place in R/3 Solution:
Change the technical status of job to red in the monitor and retrigger the job again from R/3.

9) Change run already started by ALEREMOTE Possible Causes: This can happen due to
overlapping of same request to Program. Solution: Go to Transaction Code RSATTR; see if it’s
running. Once it’s finished, repeat the job.
5. GENERAL

1).In case a chain or load fails what is the reporting structure you follow before correction, general
steps during correction(from a process point of view) and post correction what is the reporting
matrix (please provide names and mail ids of people you inform to)? Solution: The BW on-call
person generally checks the system around 5:30-6:00 am CDT. Additionally, if the chain fails at
certain points as defined in the Batch Monitor, whoever is on-call for BW is paged. Emails are
also sent to them and anyone else specified in the Batch Monitor. We may also (but not
necessarily) receive a failure email message from the chain in BWP. At that point, we assess the
problem and are normally able to get everything going before any deadlines (see A4 below). The
reporting of the error largely depends upon the type of error. For example, if it was "Sending
packages from OLTP to BW lead to errors", we just follow the directions (you have already been
given) and resume the chain. If it fails due to system-type errors, we inform Basis, our
management, the rest of the BW team and usually Rob. If it fails due to a master data problem,
we usually inform our management and the appropriate functional person so that they can check
on it and aid in resolving.

2). Is load and chain corrections done in the production system? Do you inform anybody before
solving the problem? Solution: Generally speaking, we do not need to change anything like
infopkgs or chains to correct problems in BWP. We usually only need to run something again or
to run something manually, but not change anything that you would normally transport. Se A1 and
A4 regarding informing others.

3). Is there a reporting structure in case all loads are successful on a daily or weekly basis? If yes
whom do you inform? Solution: As mentioned in our meeting, we have success/failure messages
set up in the chains. You should receive messages Mon-Fri from BWP upon successful
completion for master data, GL, AP, PCA, COPA, AR, Inventory, HR, and CWT. Once we see
that everything is complete, we send an email to our management and copy the BW team stating
that everything is complete. Or, if there was some problem that delayed the chain in any area, we
report that the chains are not complete, usually indicate the area and why the delay and also
indicate about when we estimate that everything will be complete. We generally send this
message prior to 7:30 am CDT so the information is known for the morning meeting. All loads are
generally complete before 7 am CDT. Our current deadline is noon CDT. If there is a significant
delay, we will also add a message to SM02 stating the area and estimated availability so that
users will be aware.

4). How do you re-schedule a process chain in case of failure? By maintaining date and time in
variant or is any other process followed? Solution: You need to be careful on this. You will more
than likely need to resume a failed chain within it at the point of the failure or just beyond the
failure, depending on what the failure was and what you did to correct it. If you reschedule the
chain at that point, you will mess things up. Now, there are times when the start of the job failed in
SM37. This means that the chain did not even start (See E1 below). In that case, you copy the
failed job (in sm37) and start it immediately. All process chains and mat_plant_full are scheduled
to start via jobs in SM37 - not directly from the Start process in the chains.

5). Do you send out reports on process chain performance on a predefined time line? Like
monthly or quarterly? Solution: No, there are no reports sent out. We maintain the document
"BWP Load Times and Chain Information.xls". When a new area (like HR, COPA, etc.) is added
to the daily chains in production, we generally let them run a week or so, and then we update the
document with the appropriate timing information/changes. Also, if we make performance
improvements to any of the chains or if we notice that the chains are consistently completing
earlier/later than the previous "normal", we will update that information as well.

6). Can you please out line the steps followed in the EDS-SK ticketing system with regards to
process chains only? Solution: Because we are paged and emailed directly from BWP for
problems and, additionally, since the on-call person generally checks the system around 5:30-
6:00 am CDT, we are not notified by the help desk nor are any tickets entered. As described
above, we correct the problem or report it to the appropriate parties if it is not in our domain. If
Basis assistance is needed, we will request a Basis ticket through Acxiom. If functional
assistance is required, we do not generally open a ticket. The application program for the
extraction of the data was called using update mode R. However, this is not supported by the Info
Source. Update mode R is not supported by the extraction Apothem data extraction is terminated.
Delete the initial request from package and schedule initial delta load and also schedule delta
load.

7). Time stamp error. Solution: activate the data source and replicate the data source and load.

8). Data error in PSA. Solution: Modify the in PSA error data and load.

9). RFC connection failed. Solution: raise the ticket to BASIS team to provide the connection.

10). Short dump error. Solution: delete the request and load once again.
a) Loads can be failed due to the invalid characters
b) Can be because of the deadlock in the system
c) Can be because of previous load failure, if the load is dependant on other loads
d) Can be because of erroneous records
e) Can be because of RFC connections….. (Solution: raise the ticket to BASIS team to
provide the connection)
f) Can be because of missing master data.
g) Can be because of no data found in the source system
h) Invalid characters while loading. When you are loading data then you may get some
special characters like @#$%…e.t.c.then BW will throw an error like Invalid characters.
Then you need to go through this RSKC transaction and enter all the Invalid chars and
execute. it will store this data in RSALLOWEDCHAR table. Then reload the data. You
won’t get any error because now these are eligible chars. done by RSKC.
i) ALEREMOTE user is locked Normally; ALEREMOTE gets locked due to a sm59 RFC
destination entry having the incorrect password. You should be about to get a list of all
sm59 RFC destinations using ALEREMOTE by using transaction se16 to search field
RFCOPTIONS for a value of “*U=ALEREMOTE”. You will need to look for this
information in any external R/3 instances that call the instance in which ALEREMOTE is
getting locked as well.
j) Lower case letters not allowed. Look at your info object description: Lowercase Letters
allowed
k) extraction job aborted in r3 It might have got cancelled due to running for more than
the expected time, or may be cancelled by R/3 users if it is hampering the performance.
l) Data source not replicated if the new Data Source is created in the source system, you
should replicate this Data Source in ‘dialog’ mode. During the replication, you can decide
whether this Data Source should be replicated as the 3.x Data Source or as the new Data
Source. If you do not run the replication in ‘dialog’ mode, the Data Source is not
replicated.
m) ODS Activation Error ODS activation errors can occur mainly due to following reasons
1. Invalid characters (# like characters)
2. Invalid data values for units/currencies etc
3. Invalid values for data types of char & key figures.
4. Error in generating SID values for some data

11). Duplicate record found. 0 recordings used in table /BIC/XFRCWFDOC Solution: Delete the
request from both data targets make it to Red. And repeat from PSA and make request to green.

12). While loading data from FOO15ARL to FOB15ARL (FIAR: Line Items ODS) failed due to #
symbols contain Reference Document No and Allocation Num (because these two REfDocNum
and Allocation Num contain space) Solution: error due to space included for Reference Document
Num and Allocation Num. edit the psa (deleted the # symbols) request and loaded the data from
PSA

13). While delta updating from Sales ODS (FOO02ORD) to Sales Cubes, we found some sales
documents contain ‘! ‘for Voyage Number. Solution: Edit the psa (deleted the! symbols) request
and loaded the data from PSA

14) Difference between the lis and lo’s. Solution: A. LIS works on transparent table concept and
LO’s works on Cluster table concept. B. Each data source i.e. 2lis_11_s264 is splitted in to
multiple data sources like 2lis_11_vahdr, 2lis_11_vaitm, 2lis_11_vascl, with this we can give
more detailed level of information to the end users. C. LIS works under Push mechanism where
as Lo works on PULL Mechanism. d. When we r doing delta then two transparent tables will
come into picture i.e. SBIW1 and SBIW2 in LIS. Where as in Los structures called LBWQ
(Extractor queue), SM13 (Update queue) and RSA3 (delta queue). e. Lis uses V1 and V2 where
as LO uses V3 update methods.

15) How to work with LO’s or procedure for Los. Solution:

1. Go to tcode LBWE
2. Choose the Data source i.e. extractor which suits to ur business scenario.
3. U need maintain the DS i.e. where u can add or remove the fields 4m d extract
structure.... we can add d fields simply transferring fields from Communication Structure
to the Extract Structure.
4. U has generated the Data Source.
5. Activate the Data source.
6. Choose which type of update is needed i.e. it could be either Direct, Unserialised V3 or
Queued delta.
7. Delete the setup tables by tcode LBWG.
8. Run statistical setup by tcode OLI*BW, * depends upon the application say 2-
purchasing, 11-sales order, 12-shipment, 13-billing.... etc. go to RSA6 in R/3 system and
say transport the DS.
9.Go to BW system->source system in Modeling say replicate DS and activate the
transfer rules and do all d need work on BW side.

16) How to delete the statistical data. Solution: Through Tcode LBWG.

17) How to check the data when we run Full and Init and Delta. Solution: RSA3 for full and Init.
RSA7 for Delta loads.

18) What r the settings the could be made when we r doing statistical setup. Solution: We should
make sure that there wont any users using the corresponding data source (2lis_11_vahdr), and
make sure that there should not be any data in the structures like RSA7, SM13, LBWQ for that
corresponding data source.

19) What r the different update methods. Solution: Direct: When ever new records r posted in to
the Extractor structure that will be moved to delta queue by passing the SM13 and LBWQ
structures. We will opt this delta type when data to be handled is less in volume and scheduling
frequency time is less. Here one record is equal to 1 LUW. This update uses V1 update method
from extract structure to the RSA7. In all the update methods documents from extract structure
will be V1 only to the next immediate structure. Unserialised V3. When ever new records r posted
in to the Extractor structure that will be moved SM13 i.e. update queue and from there to delta
queue. Here one record is equal to 1 LUW. This update uses V1 update method from extract
structure to SM13 and V3 job from SM13 to the RSA7. Queued Delta. When ever new records r
posted in to the Extractor structure that will be moved LBWQ i.e. Extractor queue and from there
to delta queue. Here 10000 records is equal to 1 LUW, and this might vary depending on the size
of the each record. This update uses V1 update method from extract structure to SM13 and V3
job from SM13 to the RSA7.
20) Difference between V1, V2 and V3 updates. Solution: V1: (synchronous) If records enters in
serial manner as shown above, if any error in record 2 then record3 won’t be processed until
unless record2 is successfully updated. V2: The records enter the structure in asynchronous way,
if record1 fails then there won’t be any affect on record2. This method also reduces the time of
update considerably. It is a background. V3 = V2 + scheduling of the update.

21) Significance of Start process. (Job schedule screen in LBWE) Where v can do settings
regarding scheduling of updates like
a. How frequently we r scheduling the update.
b. After which event the update should start.
c. Date of schedule …etc

22) How to Data source enhancement i.e. transactional data. This question is very important in
these days. Solution: I will explain by coating one example. For instance we r using SD data
source called 2lis_11_vahdr. But end user needs profit-centre (PRCTR) field in the Data source
for reporting purpose. Then u need to go for enhancement y because PRCTR field is not there
communication structures MCVBAK and MCVBUK (these structures can be seen when v click on
maintain Data source in LBWE screen. U can c on pooled tables list in communication structure).
PRCTR exists in MARC table. ABAPer will Give u required structure that will contain this PRCTR
field. We have to go to SE11 (Abap Data dictionary screen), there v need to enter one of the
communication structure name, it could be MCVBAK or MCVBUK, say we have taken MCVBAK,
then v need to append that structure to it, save it and activate. Go to LBWE screen and to
maintain data source where we need to transfer the field from communication structure to the
Extract structure. (From right of the screen to the left of the screen). This is the way in which we
enhance the Standard structure. Then v need write the code for populating the data on the
structure for that appended structure. Go to RSA6->2lis_11_vahdr->function enhancement-> (it
will takes us to CMOD screen) where v need to give the project name say ZBW. Then say create,
then click on Enhancement assignment select RSAP0001, double click on this it will take to
another screen where v have to Select the exit among the four, in our case
EXIT_SAPLRSAP_001 for Data source enhancement. (002 if Master data enhancement), Then v
need to write simple ABAP code for populating the data on to the Data source. Then v need to
replicate the data source in BW side. https://www.sdn.sap.com/irj/sdn/weblogs?
blog=/pub/wlg/1262 Read this weblog it is also very helpful.

23) GENERIC DATASOURCE Solution: First question will be on this will be like this “y u have
gone for generic Data source”. Then our answer should be like this “the data source which r
delivered by SAP is not suitable for business need so generated our own generic data sources”.

24) Tcode for Generic. Solution: RSO2.

25) Types of Generic Solution: We can create data source based on View, Table, SAP Query or
ABAP Query, and Function Module.

26) Scenario for Generic Data source. Solution: One of the Manager who using reports wanted to
have the reports which will him the list customers and sales document numbers created by them.
In this case we can use of VIEW where kna1 and vbak tables were combined in the View
definition or else u can say, “ABAPer had given the required view”.

27) How to create the generic Data source. Solution: Go to RS02, select the Transactional Data,
it will takes us to the next screen, where we need to give application component name say SD
(01), then give the name of the Data source that u wanted, select view and give the view name.
Below that field we need give 3 descriptions. Then save and activate the data source. Go back to
the RSA6 screen transport it to BW system. Replicate the DS. Note: If v won’t replicate DS in BW
system after the enhancement is done, if v run the Info package then the system will give an error
“source system is not replicated”.
28) RFC connection lost. A) We can check out in the SM59 t-code RFC Destination + R/3
connection CRD client (our r/3 client) double click..test connection in menu

29) Invalid characters while loading. A) Change them in the PSA & load them.

30) ALEREMOTE user is locked.

1) Ask your Basis team to release the user. It is mostly ALEREMOTE.
2) Password Changed
3) Number of incorrect attempts to login into ALEREMOTE.
4) USE SM12 t-code to find out are there any locks.

31) Lower case letters not allowed. A) Uncheck the lower case letters check box under "general"
tab in the info object.

32) While loading the data I am getting message that 'Record the field mentioned in the error
message is not mapped to any info object in the transfer rule'. A)

33) Object locked. A) It might be locked by some other process or a user. Also check for
authorizations

34) "Non-updated IDOCs found in Source System". A) Check whether any TRFC s strucked in
source system. You can check it in SM58. If no TRFC s are there then better trigger the load
again i.e., change the status to red, delete the bad request and run the load. Check whether the
load is Delta or Full. If it is full just go ahead with the above step. If it is Delta check whether it is
source system or BW. If it is source system go for repeat delta. If it is BW then you need to reset
Data Mart status.

35) While loading master data, one of the data package has a red light error message: Master
data/text of characteristic ZCUSTSAL already deleted. A)

36) Extraction job aborted in r3 A) It might have got cancelled due to running for more than the
expected time, or may be cancelled by R/3 users if it is hampering the performance.

37) Request couldn't be activated because there is another request in the psa with a smaller sid
A)

38) Repeat of last delta not possible. A) Repeat of last delta is not an option, but a mandate, in
case the delta run failed. In such a case, we can’t run the simple delta again. The system is going
to run a repeat of last delta, so as to collect the failed delta's data again as well as any data
collect till now right from failure. For repeat of last delta to be run, we should have the previous
delta failed. Let’s assume, in your case, I am not sure, if the delta got failed or deleted. If this is a
deletion, then we need to catch hold of the request and make the status to red. This is going to
tell the system that the delta failed(although it ran successfully, but you are forcing this message
to the system). Now, if you run the delta info package, it will fetch the data related to 22nd plus all
the changes from there on till today. An essential point here, you should not have run any deltas
after 22nd till now. Then only repeat of last delta is going to work. Otherwise only option is to run
a repair full request with data selections, if we know selection parameters.

39) Data source not replicated A) Replicate the data source from R/3 through source system in
the AWB & assign it to the info source and activate it again.

40) Data source/transfer structure not active. A) Use the function module
RS_TRANSTRU_ACTIVATE_ALL to activate it

41) ODS activation error. A) ODS activation errors can occur mainly due to following reasons-
 1.Invalid characters (# like characters)
2.Invalid data values for units/currencies etc
3.Invalid values for data types of char & key figures.
4. Error in generating SID values for some data.

42) CHANGE THE OWNER OF A JOB Select a modifiable job to change: From the top pull down
menu select JOB -> CHANGE Select the step with the user ID that needs to be changed From
the menu, select STEP -> CHANGE You can now edit the user and change to BW_ADMIN Check
and Save Exit and save the job.

42) HOW TO INIZIALIZE ODS YGTGD046 THAT FAILED Solution: Info package: Init. package
for update by ODS YGTGD046 Error: Processing is overdue ODS YGTGD046 is feeding ODS
YGTGD022 ODS YGTGD033 is feeding ODS YGTGD005 1. We have to delete data first from
YGTGD022/ YGTGD005 Make a search ODS 22 Right click and chose “Delete data” Click Yes
Once you delete data Make a search of ODS 46 Right click and chose “Update ODS data in data
target” The little window will appear Chose “Initial update” and hit “Update” button Go to
“Scheduler” menu and chose “Initialization options for source system” Next window will appear
Click in the record in red and hit the trash icon to delete it Click yes Click yes Go to schedule tab
and click “Start” button

43) NO ACCESS PERMISSION AS TABLE IS ALREADY LOCKED Error: No access permission

as table is already locked Solution: Some times just by restarting info package, data is loaded
and problem is solved.
1. Other times restarting still gives red light and data load failed because of the table is
locked. In that scenario, follow below to solve it.
2. Click on the lock icon (key) on the menu bar.
3. High light the characteristics, right click and delete lock. Once the lock is deleted
restart the info package, it should work now.

44) ODS 33 UPDATE RELATED ISSUE System: AA4 Info package: 2LIS_11_VASCL_DELTA
There is a problem scheduling updates from the PSA for ODS YGTGD033. The Error "Request
REQU_3PM0HXUHXP8Y8YKSUDAQRD3Q (107.399) has not or not correctly been updated:
Please edit" does not allow scheduling anything above the date of 5/14, besides when trying to
load data into ODS YGTGD033, data target is not appearing in the data target tab Reason: The
PSA update was not made on preceding day 5/13 though the info cubes were updated.
Resolution: Force the QM status for day the info package ran to red and subsequently delete the
request from all cubes. This allowed us to continue pushing psa requests to the ODS. Steps:
1. Find the Info Package (2LIS_11_VASCL_DELTA):
2. Click on Monitor
3. Filter on Date for which we want to check when the info package ran
4. Click on Execute
5. Check for the last 4 characters of the Request to match with the Request in the Error
Message
6. If this match, click on the Status tab and click on the highlighted button
7. click Yes on next message:
8. On next screen select the following screen:
9. Continue on updating the updates on ODS