Error in FI_AP03 Delta Load

Hi BW Experts,
We are loading data for Spend analysis from 0fi_ap_3 to data targets 0fiap_o03 and zfiapglo. But the delta was failing for last 3 days and the error message stating is ERROR WHEN READING FROM THE QRFC QUEUE. I checked for no. of LUW entries in SMQ1 there are 13593. There are 4 LUW's with date 10/19/2004. The init. was done on 01/10/2004.
Please suggest what to do to get the delta records other than initialization.
It's very very urgent issue.
reddy.

Hi Reddy,
did you already check sm21 (the syslog of your R/3 system) as well as the joblog via sm37 and/or additionally st22. May be there is something wrong with memory options, disk space, the database ....
Let us know the details.
Here some little hints for error analysis while loading data. /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Hope it helps!
regards
Siggi

Similar Messages

Error while implementing Delta Load

Hello Experts,
I need your help.
I am trying to extract data from SAP R/3 to BI system.
The R/3 system contains data from 1999-2008 fiscal year. I extracted data for fiscal yr 2007,2006 and 2005 successfully and created a delta info package
In the delta info package I didn't specify any fiscal year limit under the Data selection tab.
I started a background job which needs to run daily. Now my issue is the load came up with an error stating time limit exceeded. I believe the number of data packets exceeded. The request showed a warning sign and it got stuck there. I tried to delete that request and consequently delete the whole delta info package and creating a delta package freshly.
But when I tried to start the process of extraction, the following message popped up. Please tell me what I need to next.
Init. select. for field name currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB
Message no. RSM1070
Diagnosis
Init. selection for field name with the 'From value' and the 'To-value' , is currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB.
Procedure
Wait until the init. selection is completed; check the load status in the Monitor.
Thank you. Appreciate your help.
Raj

Hello guys,
I tried to delete the delta request by right clicking on the infopack and hitting manage, and then selecting the particular request and hitting delete.
But when I tried to create a new infopack and initialize it it constantly gave me the same error saying that I need to delete the previous request.
There is another place where you need to delete the request from.
You need to double click on the delta infopackage and on the top menu click on
Scheduler > Initialization options for Source System > Now select the particular delta request and delete it.
This solves the problem and helps you to reintialize the delta load using the new delta infopackage

Unknown error message at delta load

We are working with the IPC 3.0, SP17 in a stand alone version. For data loading we are using always the initial load. Since the condition data get more and more, it needs to much time for loading that with the initial load and we want to use the delta load now. When I have made the customization in the R3 system, now I have the problem that I get always the following error messages:
java.lang.Exception: A901 is not existing in global scheme. (A901 is a customer condition table, but for SAP tables I get the error message, too)
java.lang.Exception: Specified source/destination Type doesn't exist in Scheme
I do not found any documentation about this error messages.
Can someone help me ?

It's an error in some third-party software you installed, possibly called "Remote Advisor."

MAster Data - Delta Load Error?

Hi,
I am having error in 0COSTCENTER delta load. In the Info Package of 0COSTCENTER, it was not selected to PSA. It was selected to InfoObject directly.
Since this is a delta load for Master data, how can i correct this error?
Thanks!
Venkata

Hi Venkat,
You can done a full upload without affecting Delta upload. Make a test on Dev or Qual and you will see that a full on Master Data does not stop delta process.
Ciao.
Riccardo.

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

ODS to ODS delta load error

HI
Im loading data into a consolidated ODS from 5 based ODS's. Im doing a delta load from the base to the top level ODS.
recently i made change in the cons ODS.I added a key figure to the ODS(not a key field). Now when i try loading delta again, it gives an error.something which says 'ORA 14400 Inserted partition key does not map to any partition'
has anyone of you come across such an issue.
help will be appreciated
jpjp

HI JP
This is an error on oracle partitioning.. please check the note.
ORA-14400 means=
ORA-14400 occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please look in to this note..
Note 722188 - FAQ: Oracle partitioning
Note :991181 search this tooo
Hope it helps little
Regards
AK

"Error occurred in the data selection" on init delta load ODS- InfoCube

Hi, gurus and experts!
I'm trying to do Init delta load from 0FIAR_O03 ODS into 0FIAR_C03 InfoCube in PRD env. by InfoPackage "Initialize with delta transfer (with data transfer)". Immediately after the load was started I got error
"Error occurred in the data selection"
with details
"Job terminated in source system --> Request set to red".
Where are no any short dumps. There are 1 activated init load in ODS - nearly 6 500 000 records.
Any ideas about error? And the way I can load data?

Hi Gediminas Berzanskis,
I faced the similar error when I tried to load data from an ODS which contained huge amount of data to a Cube. Even in your case the volume of data is more (around 6.5 million records). The error could be due to the table space issue, please contact your Basis team to check if enough table space exist for both the data targets.
Meanwhile you may also check the RFC connection of the Myself source system.
You can replicate the DSO datasource once and then reactivate the transfer rules using the program RS_TRANSTRU_ACTIVATE_ALL.
Try load with a small amount of data with a Full load option and then with a delta option..
Hope this Helps,
Prajeevan (XLNC)

Delta Loads failling after system copy with error in source system(RSM340)

Hi Guru's
We recently performed system copy in BI side.I am facing same issue in couple of chains.Process chains are failing at delta loads with error in source system(ERROR IN SOURCE SYSTEM-message no-RSM340 ).When I go for repeat option ,delta loads are running fine.I did some research regarding RSM340 and I found note:1576331.
But my system is not showing any 'Time Inconsistencies'.So.I was not able to find any clue about it.
Could anybody help me out in this aspect.
Thanks!!!
Kuldeep

Hi,
Check whether the profiles that ran in background have the following authorizations.
The RFC user on BW, receiving data from OLTP system, should have S_BI-WHM_RFC and S_RS_ALL in the user profile.
The RFC user on OLTP, receiving request from BW system, should have S_BI-WX_RFC, S_IDOC_ALL, and, B_ALE_ALL in the user profile.
Regards .

Delta load Error in LO Cockpt

Hi
If I get Error while Delta Load using V3 unserialized update in LO Cockpit....How can I rectify the problem ?
Thanks,
Abhi

Hi Pradeep,
This is the interview Question what I have.
In General, When we extract data from R3 LO Cockpit to BW ( Deltas )every load won't be success.
1. If I get an error in Scheduling the Job Control .. what I have to do ? Where I have to look ?
Is there any place to look otherthan SM37,Delta Queue(RSA7) and Update Tables(SM13)
2.While Delta loading...I have the data in Update tables but I didn't find in Delta Queue. How can I sove this problem ?
Please Clear my Doubts. Points will be awarded.
Regards,
Abhi.

Error in activating init flag for delta load

Hi everybody, I am trying to activate the init flag for delta load, when I schedule the infopak it is taking too long to execute and the status is remaining in yellow for a week. I checked in details tab the error message is u201C no data available in source system u201C Please helpu2026

Hi Vinod,
When there is no data available in the source system, you will have yellow flag for the delta init request. Check for the delta queue entry (RSA7) on the source system. Delta mechanism starts working once this flag is created. After that schedule the delta infopackage.
Also check on the source system whether there is any data avilable in the application tables related to this datasource. Take the help of functional consultants if required.
Regards,
Sreenivas.

Sales Document Delta Load Error - Status procedure could not be set

Hello,
I am getting the following error message during the sales document delta loads. It errors out in SMQ2 with this message - "Error in Validation (Details: transaction SMW01)"
In SMW01, I get this message:
<b>The status procedure CRMORD_I could not be set from item category XXX</b>.
Message no. CRM_ORDERADM_I503
Diagnosis
Possible causes are:
1. The system administrator has not assigned the status profile CRMORD_I to the object type.
2. Initial statuses that should be set in the status profile CRMORD_I cannot be set at present.
3. The current user RFCUSER does not have the authorization to set application statuses.
Detailed error messages can be found in the following error log for status management.
System response
The status profile is not set in the document.
Procedure
Set the status profile in Customizing so that these cases do not occur.
This status profile has been assigned to the item category mentioned and the RFCUSER has full authorization (SAP_ALL)
Do any of you know what else could be the problem here?
Thanks,
MAX

Dear All,
I met similar error before, it happens when you change the item category in ECC but there is a status profile assigned to the item
category in CRM with an active status set.
In CRM, when the item category is changed, the system can only change (or delete) the status profile if there is no user status set for this item. So for example, if there is already a status set for an item (Say, E0001 'Open' is active) in CRM, so a change of the user status profile is impossible. If you need to change the item type, then you have to make sure that there is no active user status in the item.
Please see note [1113116] point 2. This is a restriction in CRM. If you try to make the same changes directly in CRM you will also get the same error.
It is not allowed to change the item category if the document has been saved and the status profile of the new item category is different from the old one.
That is the reason why the error occurs when the data reaches CRM frm ECC.
In order to prevent that there are sysfails in the inbound queue you can implement note [1438966] - after this is implemented you will not have the queues failing but you will get the error message in the sales order in CRM.
You should ensure that the configuration for alternative item categories is R/3 is the same as in CRM and in this case all the alternative item categories should have no status profile or all the same status profile configured.
I hope this could be helpful.
Best regards,
Maggie

0COORDER - Delta Load Error

Hi,
We are having 0COORDER as a regular delta load. Today we are facing error message: <b>68 duplicate records found in the master data</b>. I am updating data in series from PSA to data target.
Can you please let me advice, how can i correct this data load error in Master data?
Best Regards,
Venkat.

You should choose the option of ignore duplicate records to let this master data complete sucsessfully. I wouldnt recommend this until you find the root cause for the duplicate records. If you ignore the duplicate records, it is only going to load the first record and the ignore the records with the same key combination. What if the record with correct values came in after the incorrect record. This may lead to some inconsistency. So please check with functional folks and try to analyze the root cause.

Delta Load Error in the Data Extraction

Hi BI Guru`s,
The issue is with the extractor 2LIS_13_VDKON (Pricing conditions), The regular delta till 22.07.2010 has run successfully, But on 23.07.2010 the delta got failed with the error message " Data Package 58 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missi" for one of the Datapacket. We have repeated the load even though we got the same error message, Since the client is retailer we will be having the delta records of 200 million ( approx. 23369612) in a day. Since because of this error we could't load any of the delta from that day onwards.
Need Help on this:
1. How to get the old delta
2. How to re-initialize the process for delta. (Pls keep it in mind the volume of the records).
Thanks in Advance,
Venkat

Hi,
Here we need decrease the datapacket size as well as prallel proceesing .
than we need to load the historical data through dalta repetition
hope..helpful for you!
Regards!
Malli.

Delta loading error - how to correct

Hi,
A error occurs on a delta loading based on 2LIS_02_ITM datasource.
The PSA had not been loaded because of a dump due to a tablespace overflow.
I can't reinitialize this delta because there are too much data and I can't reload from the PSA which had not been loaded.
The tablespace error is now corrected.
What can I do to reload this delta without loosing data?
Thand in advanced for your help.
Best regards,
Bertrand

Hi.......
So request not even came till PSA also.........right.......that u mean to say........there is no failed request also in the target or in the target?........U can make the QM status red of the failed load...........delete the request from the target......and try to repeat the IP..........just check whether the system asking u for repeat delta or not...........it should ask ......bcoz records r not transfered in the BI side..........otherwise ........u hav to go for a Full repair.......but for that u hav to know that what range of records are missed.......u can give a tentative larger range.......
1) Delete init flag
2) Do Full repair(After filling the set up table)
3) Do init without data transfer
4) Delta.....
Hope this helps.......
Regards,
Debjani......

InfoPackage delta load error, but repeat successfully

Hi,
we are facing a strange behavior when executing a infopackage.
The datasource is created via RSO2 using delta = AIMD. We use a programm to select the data and insert it in the deltaqueue.
So the data is already in the queue when we start the infopackage. We only using a dummy function module to trigger the transfer of the data.
So the problem is:
When we start a delta load, it brings up an error (RSM340 - Error in Sourcesystem), but when we make a repair or execute the infopackage again, (immediately or a few minutes later) the load works.
We have checked everything, joblogs, idocs, trfc, authorizations and everything is ok. All jobs are being executed in the sourcesystem correctly and the idoc´s are sent back to the BW.
We are on a SAP BW 7.31 SP7 system.
Does anyone has an idea, where to look or whats could go wrong?
Kindly regards
Maximilian Müller

Hi,
Have you checked your info pack job log details at ecc side, SM37.
if check there you may know more details about your issue.
From failed info pack monitor--> menu Environment-->job overview--> job in the source system, enter ecc user id and password, you will get your ecc job, select job and click on log details, see and share here if you see nay abnormal messages.
Thanks

Error in FI_AP03 Delta Load

Similar Messages

Maybe you are looking for