Delta load error in quantity of sales overview cube 0sd_c03

Hi All,
The quantity(0quant_b) is fetching properly for full upload.But when delta load is done 0quant_b is not fetching correctly.
For example,
quantity was changed from 100 to 120 for an order. When delta is run, only 100 is uploaded instead of 120. In PSA it is showing 120. If a full upload is run it is fetching 120.
I was wondering what could be the reason for a mismatch. I would really appreciate for any clues provided.
Thanks,
Jerry

Hi Jerry,
Please understand the following:
If you have the initial quantity in the R/3 system as 100 and this is loaded to the BW system in the your model(PSA then Infocube) there is no mechanism in your model where in delta can be handled.
The quantity is now changed to 120 in R/3 side now you are expecting this to be captured into the InfoCube which in your model is not possible.
The reason is that in BW the delta handling will be as follows(taking your example):
100 is the initial quantity and this will be flown in to the target with no issues.
Now the quantity is changed to 120 in R/3 side, this will be flown till PSA as 120 itself.
But a field called ROCANCEL will be populated as New record.
This should be mapped to the field RECCORDMODE in DSO on which the delta will be captured.
where I mean to say DSO is mandatory in between. In DSO as I told in the previous post the delta handling will be done as the (new image - before image), in your case it is 120 -100 = 20.
As the property of the InfoCube is addition this 20 will get summed up in to the InfoCube making the quantity 120.
If there is no DSO in between this record will not be considered in the Infocube so you will be left with 100.
Hope this explains your query in detail.
Thanks & Regards,
Vishnu

Similar Messages

Open Orders data in Sales Overview Cube

Hi All,
I am using Sales Overview cube to store all the Orders(inclucing Open orders), Deliveries and billing data. I am using seperate ODSs(for all the infosources) to store both the header and item level data for some reporting requirements.
But I am very confused how the cube gonna store the data of open orders i.e if we are loading data on monday and we got Order 100 as open order. But on tuesday the order was completley processed and it is no longer an open order. So what will happen when I load data on tuesday. How does the changes to Order 100 reflect in the cube?
Any help would be highly appreciated and rewarded!!!
Best Regards,
Nene.

hi Nene
All orders where delivery qty is less than Order qty are open orders
All the orders which appear in the transaction V.15 in R/3 are Backorders
Execute the transaction after giving sales order, dist chan and division
All orders with document type RE are returns
Suggestion :
1. Create a restriction in ur queries with document types = OR,,,, other order types( Not RE..see last )and and Order qty < dly qty for open orders
2. You can extract data from V.15 into a BW customised table and check the entries to identify the backorders
Routine in update rule may help to distinguish backorders
3. You can use filter to identify the items returned from the customers
For document type = RE
Assign points if useful
Regards
N Ganesh

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

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

Query Runtime Statistics - Delta Load Errors

Good Morning,
We recently upgraded our BI system to 7.0. One of the consultants who was here activated some standard business content, as the title of my subject shows, Query Runtime Statistics. The Infocube that is being loaded in the process chain he activated is: 0TCT_C01.   This load utilizes 4 individual delta loads, coming from Datasources: 0TCT_DSA1, 0TCT_DSO1, 0TCT_DSO2, and 0TCT_DSO3.
The problem we're having is that at least 2 of these frequently fail ( 0TCT_DSO2 and 0TCT_DSO3 ).
The failure messages we get is that some of the data coming in for object 0TCTSTATOBJ (Query Runtime Object) is always bad.   Some example values of the data that it is trying to load include:
FILTER(1)
TABELLE(1)
GENERISCHER NAVIGATIONSBLOCK(1
I'm not seeing anything in particular that would indicate these as being invalid values. The ()'s I wouldn't think would be causing it, given that those are in our system as acceptable characters (checked RSKC to verify) and there's nothing else that looks out of place (aside from the values coming in as German). Has anyone else come across an error like this for this particular statistics load? Manually changing these erroneous in the PSA is not an option given the frequency of the failures.
Any help would be greatly appreciated. If I need to clarify or relay any additional information, please let me know as well. Thanks

Sita,
I greatly appreciate your response. However, I probably should have provided some additional technical information regarding the issue.
The values I posted actually are from the PSA. These values that are given are telling the person what Java object the report being used, has had an issue (may not just be reporting issues, but general statistics for the use of these java objects, not sure yet).
I am aware that when BI gets an invalid character, it replaces it (in the display screen) with a #. Unfortunately, we do have # in our permitted characters and the reason why that doesn't work to qualify what was entered is because while it shows up in your display screen as a #, in the background it still sees it as the invalid char.   Subsequently, you won't always be able to see what that invalid char is. We've encountered this many times over the years with our Sales Orders when a Rep (or someone within the company) enters invalid characters (typically they do a copy and paste from Excel using a different Font, or are using arabic or other foreign characters).
Given that the values we're recieving are in German, my only conclusion is that the words themselves contain german characters often used in certain letters. For example, the letter U can sometimes have what they call an umlout (spelling may be off on that). An umlout almost looks like a quotation mark that is placed directly above the letter itself.   Another common letter in German is the ß symbol.
We may be able to bypass our problem by entering in these german characters, but I guess I was looking for more than just a "hack" solution and was curious if anyone else out there has had a similar issue on their system and if they were able to come up with a solution other than trying to guess and add in "special characters" that are not normally used in the english language.
Again, my appologies for not being more descriptive and thank you again for replying.

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

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.

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.

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.

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

CO-PA Delta load - Errors in source system RSM 340

Hi,
We are facing a unique error when we do a CO-PA delta load. The error message is as follows:
"Errors in source system RSM 340,The selected data source is locked by another process RD 156"
The load completes successfully with 0 delta records fetched. When we re - trigger this after sometime, the load goes through.
Can anyone explain as to why this issue occurs ? Basically, looking at the root cause.
We are pulling data from CE1XXXX table, the delta for which is pulled into BW with the setting of 30 minutes safety delta. Just wanted to understand how is it that in this scenario we are faced with a lock issue ? It is also confirmed that while the delta load is initiated the transactions are being passed into the CE1XXXX table.
Thanks,
Amit Mitra

Hi PK,
caller 09 error mainly because of source(target system) and destination(bw system) not configured correctly.
i think you get the error message as follows. file is in the client workstation as like.
better you contact basis people. they will resolve this.
hope this help you
Regards
Harikrishna N

Error in Delta load; error in source system

Hi,
I'm extracting from 0FI_AA_11.
Performed a full load.
Then initialized without data transfer.
When i run delta (0 records) , it fails with 'error in source system' .
Strangely, when I run delta again in REPEAT mode, it runs succesfully.
this is happening everytime i run delta.
Please help

FI_AA_11 is sure capable of handling delta.
It does have some dependencies with master data and these are pretty awkward sometimes.
I don't know when you are running your deltas (during opening hours from the office?) but in your process chain also the MD objects must be present.

Master Delta Load - Error "38 Duplicate records found"

Hi Guys,
In one of our delta uploads for a Master data we are getting error "38 Duplicate records found". I checked the PSA data but there were no duplicate records in that.
Once the data upload fails I manually update the failed packet and it goes fine.
Please any one have solution for this.

Hi
You can see the check box in the Processing tab page. Make a tick mark for the check box Ignore Duplicate Data Records indicator . When multiple data records that have the same key are transferred, the last data record in the request is updated to BI. Any other data records in the request with the same key are ignored.
Help says that:
To maintain consistency, ignoring duplicate data records is only possible if the data is updated serially. A serial update is when data is first updated into the PSA then, after it has been successfully written to the PSA, it is updated into the master data or text tables of the InfoObject.
If a DataSource transfers potentially duplicate data records or if you manually set the Ignore Duplicate Data Records indicator, the PSA Only update type is automatically selected in the scheduler.
hope it clears ur doubt, otherwise let me know.
u can see the same in my previous thread
Re: duplicate records found while loading master data(very urgent)
Regards
Kiran

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 Load error

Hello All,
I have a custom table in R/3 that I have created a datasource on and delta enabled it on a timestamp field(char 16). I have successfully replicated the datasource to the BW system and created the custom infosource, transfer rules and data store object.
I created and ran the "Init" infopackage.
The initial data load came across fine. However the "Delta" infopackage load run is not working correctly.
Even if I enter new entries in the custom table in R/3 the infopackage runs successfully(green status),but no new records come across. Shows 0 records transferred.
I ran the extractor checker(RSA3) in the R/3 system. It works fine for the full load but when I run it with update mode D (Delta) it pops an error message box " Error occurred during the extraction". When I look at the log in RSA3 I see a more detailed error message "Could not determine BW release of logical system".
I am not quite sure how to fix this. Appreciate any input from folks in this forum.
Thanks for your help in advance.
Regards
-Saif Alam

Hi Saiful,
In RSA3, did you enter a (correct) value in field 'Target sys'? The entered value is checked against table ROOSGEN.
Regards,
Marco

Delta load error in quantity of sales overview cube 0sd_c03

Similar Messages

Maybe you are looking for