DELTA AND INIT TO CUBE Simple

Please help me with this, I have a bad red delta request coming from billing ods in bmw cube so i deleted the request, but bmw cube has other green request coming from order and delivery which is fine green and success.
now to resolve this i deleted the red delta request of billing and also deleted every thing from ods and i redo the set up table and did init to billing ods but now when init goes to bmw cube it fails please tell me the exact step to resolve this please tell me how can i set up the delta again so that init from billing ods goes to cube
help me with navigation step.i do not want to delete the entire data from cube to resolve this
thanks
soniya
soniya

Let me try to get it.
Your ODS has delta coming in for a specific fiscal period? Is there no overlap (meaning one billing document coming in as new into the ODS and cube is not changed in the next period)?
If not, there may be a problem.
Consider the case where you had a document which came in earlier (successful) request, and is there in the cube (say with a original qty of 25). Now, say your last delta had a change to it (of qty increased by 5, say), and this delta failed to go to the cube. Now you are doing a full load with repair for this period.
Since you are doing a full load, it will bring a qty of 30; however your cube has the earlier record (with a value 25), so instead of total 30 (correct) you will end up with a value of 55(incorrect).
The difference here is that your delta which failed had a qty of 5 (incremental amount) for this doc, but now you are bringing the qty of 30 with a full load.
This is a theortical scenario which can cause inconsistency to your data. If there is no case where an earlier existing record was being changed in the last delta (ie last delta had all new records) then you should be ok.

Similar Messages

Delta and init deletion

Hi,
I had a COPA load which got failed and trying to delete the Delta and init but its not allowing me to do that..
I have changed the request to red...
Kindly can anyone will help..
Thanks

Hi,,
First of All Please check whether you have authorization to delete data from ODS/Cube
Make sure that there is enough space (DB02) in the system to do deletion. And also make sure that there is free back ground processor before starting the job.Go to SM37, find deletion job and check logs. Maybe there will be some messages which tell you why request was not deleted
Apply Note:592620 and follow Case 1. Try this in Development and then go ahead. You need to open the client inorder to do it.
I would like to ask actually whats the error u r facing, Is the request failed due to some error record.
Bear in mind if the error request has any successive requests (later requests than the error request) then they would also get deleted so you need to reconstruct them
So be careful.

Delta and Init Upload

Hello Friends
I have some confusion regarding the difference b/w delta upload and Init load.
Are they related to each other, if yes then how? Cant get a clear explanation for this.
Secondly, If i have loaded data into a cube from an ODS with request no for eg. R1 and other req no with R2. If after the successful request and data going into the cube..after some time i change the req. R1 status from green to red, will i be able to view the data in the cube coming from req R1?
Need ur comments
Regards
Rohit

Hi Rohit
Have quick look at the follwoing thread it was already discussed
Re: init delta
Re: Delta and INIT loads
Coming to your issue yes you are able to see the data bcz once the data is
suceesfully loaded in to the cube .it will maintain the data .It wont bother about
ods request..
Regards
R M K
Assining points is the only way of saying thanx in SDN ***

Delta and Init Process when R/3 is connected to multiple BW systems

I have a scenarion where one R/3 system connected to 2 BW systems.
In R/3 we plan to have a LO extractor feeding delta to 2 BW systems. I understand delta works fine as delta queue in RSA7 is target system specific.
How are the initializations handled?
What happens if delta in one of the BW system breaks and we need to re-Init?
How would re-init from one BW system affect the delta/init in the other BW?

Hey. I'm assuming both BWs are pointing to the same system/client. I do not have actual experience doing this as I would be very hesitant to have multiple BW systems trying to get delta data from the same source (especially with how logistics behaves).
I know this isn't answering your true question, but could you connect BW system B to pulling the data from BW system A? So something like:
R/3 (logistics) => BW A 1st layer DSO
BW A 1st layer DSO => BW A reporting DSOs/Cubes
BW A 1st layer DSO => BW B reporting DSOs/Cubes
In this way, reporting in BW systems A and B are from the same DSO stage. This would help with any synch/data consistency issues. If A or B reporting providers get corrupted, or whatever, either could be reloaded from BW A 1st layer DSO and everything is still in synch.
Not sure if this helps you or not, but thought I would offer it up as this would probably be my approach.
Thanks

Question on Deltas after Init and Full load

Hi
We have an ODS X pushing data to two cubes A & B. ODS X data is initialized to Cube A long back and deltas are loading every day. Now We have recently created Cube B and made a fulll load from ODS X and loading the Deltas from ODS X with same info package we are using to load the deltas in to cube A. Do we get any data inconsistencies if we load like this ? Do I need to make a new init for Cube B to get proper deltas ? I'm hoping that Deltas will automatically take care of reversal in Cube B too...Please advice.
Thanks
Sam

This looks fine, since u have already done full load from X to B, and currently loading delta to both A n B , it is fine, no need for new init.
Regards,
Rathy

How can I delete all delta request and init from InfoCube?

Hi,
We are working with an extractor that support deltas, but we are presenting problems with it, some changes in the data are not displayed. For this reason we are thinking change this type of processing and make a full load (with the full updating the changes are shown).
For this reason we need to delete all requests of delta and its init. But in manage option of the infocube we cant see the init and the first deltas.
If I delete the initialization information at info package (menu option scheduler-> initialization). With this only we will delete the Initialization. I need to delete the data in the infocube.
I would appreciate your help.
Regards,
Victoria

Hi Victoria,
You can either display all the requests in the manage tab and delete from there. Or you can use the Automatic Request Deletion option in the Data Target tab of the InfoPackage. See here for details:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65a8e07211d2acb80000e829fbfe/content.htm
Hope this helps...

Doubt on Deltas from ODS to CUBE

Hello Experts.
I have few Questions on Deltas. from ODS to CUBE
I have 3 Cubes ( X, Y, Z ) which gets Deltas from ODS ( A ) . i have extended the cube X so i have deleted data and Reloaded it. I have to do Deltas from ODS to Cubes from now on.
in the ODS manage ( there is Tick all connected data Targets to this Request is been Delted now ).
if i reinitalize the delta with out Data Transfer. will only the data which come now on to ODS( A ) will be going to cubes( X,Y,Z ) are all the data in ODS will go to Cubes.
Please Advice me.
Thanks
Sharp

Hi,
When you are loading the delta from the ODS, the data is taken from the changelog. These records are the + and - records generated as a result of the new data loaded and activated in the ODS. So, if there were any changes made to the existing records these will flow to the cubes as well.
If you do the init without data transfer, you need to couple that with the full load to create the initial status of data in the cubes.
Hope this helps...

Delta with reversal into cube from LO extractors

Hi SDN,
In our LO extraction design we have write-optimized DSO used as EDW as the first layer in BI. Then data is sent to Business Content infocubes, such as 0PUR_C01 though we are using their copies and instead of Update Rules/Transfer Rules, we are using PSA, Transformation, Write Optimized DSO, another transformation and onto the cube. DS and all other objects in the data flow are BI 7.
What we are not clear about is the role or ROCANCEL when passed to both STORNO and RECORDMODE and its impact on the cube after the write-optimized DSO. Some key figures are reversed for 'R' but others are not.
We had thought that 2LIS_02_ITM via a Write Optimized DSO will pass on STORNO and RECORDMODE to the cube which should have reversed all key figures in the cube if the value is 'R'. But it is not happening. Whatever key figures were reversed in the source system, they remained reversed, others are still there and adding another row in the cube with some positive values.
Can anyone shed light on this or provide reference to documentation regarding delta processing in the cube, especially from LO extractors like 2LIS_02_ITM, etc.?
Thanks
SM

Friends,
Thanks for the reply.
My question is more fundamental.
In 3.5 There was expected to be no DSO between Source system and the cube. How were the Update, add and delete handled then?
As I see it, write-optimized DSO is no hindrance because essentially the data is coming into the cube as if there was no DSO in the middle. I do not see SAP suggesting a DSO anywhere between the source and business content cubes, especially in our case dealting with 2LIS_02_ITM, SCL, etc. to handle delta.
Are you saying that no delta management is possible without inserting a DSO before the cube? Please realize that WO DSO only brings data request by request without any summation and overwrite confusion.
What I puzzled at is the lack of comprehensive unfied and detail information either in documentation or a blog.
Please advise.
SM

Question regarding deltas and filling of setup tables

Hello Friends,
We are using the Sales Order Item Datasource 2LIS_11_VAITM. We have transported it to BI Production. We have initialized the delta and the deltas are running for the past 3-4 months.
Now we had a new requirement which was getting satisfied by the Sales Order Header and Sales Order Header Status DataSources, 2LIS_11_VAHDR & 2LIS_11_VASTH respectively.
Now we wan to transfer both these (header & header status) DataSources to BI Procution. My question is:
1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?
2) Do we have to reload the entire Sales data again from scratch.
3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
Regards,
Prem.

Hi,
1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?.
Yes you need to refill the setuptables, because if you want to load deltas, you need to do Init then deltas, other wise first time when you are filled setup tables, (first load init with the existing data in setuptables) from that day to till date you can do full then you can set delta.
It is better and good to fill setup tables and load.
2) Do we have to reload the entire Sales data again from scratch.
Any way you need down time to load the other 2 datasources, and also for 11 application you are filling setuptables.So for perfectness it is better to load from first.
3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
If you transport the new datasources then delta won't distrub in BW. If you did any changes to DataSource and trying to transport it to production then it will give error, because LBWQ and RSA7 will have data so first you need to clear it and then transport it.
Thanks
Reddy

OBIEE 11g, BI Apps EBS: What are default security variables and Init Block

Hi,
We are implementing BI Apps 7.9.6.3 [OBIEE 11.1.1.1.5 with EBS modules]. Out of the box RPD and mappings.
There are many VARIABLES and INIT BLOCKS in the RPD. Some of them are mainly for Siebel, Jd Edwards etc.
I need to know what are the default variables and Init Block configures in RPD. Also it will be highly appreciated if anyone can point out what segments we should configure if we need to implement security with simple database table authentication with SSO?
Thanks in advance.

You should review this doc for the options for EBS/OBIA security:
http://docs.oracle.com/cd/E20490_01/bia.7963/e19042.pdf
If helpful, pls mark as correct or helpful.

Delta and full uploads in the same data target?????

I have found that delta load and full update from different infopackages are getting loaded into the same data target that is ODS object. when do we go for such situation, can any one explain me in detail or give me some documents to know more about it.

Hi,
You have not clearly mentioned that those infopackages are ctrated on the same Datasource or not.
This way of uploading is very common when we need to upload some data from R/3 and some other data from Flat file into the Info cube. And GenerallyFlat file data would not be given in Before image and after image way, thats why we need to do full uplaod. The deleetion of already uploaded flat file data fromt he cube (before new upload from flat file ) depends up on whether the data to be uploaded from flat file system is always new data or not. And generally R/3 Extractor is capable of giving deltas, thats why only delta loads to the cube.
With rgds,
Anil Kumar Sharma .P

R/3 extraction.{direct delta and queued delta and V3}

Hi,
I am new to BW.Can anyone explain me about R/3 extraction in detail and steps to extract from R/3 to BW.
I understood direct delta.But i couldn't understand queued delta.Can anyone please explain queued delta and also V3.Are queued delta and V3 same?
Detail explanation or links will help a lot.
Thanks,
Sunny.

Hi Sunny,
Procurement - MM :
MM is a part of SCM. There are several section in this, say Procurement, manufacturing, vendor evaluation etc... All can be found under follwoing link.
Please find the procedure and important links for LO extraction..
LO'S Procedure:
Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
Go to transaction RSA3 and check the data.
Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
Now you can go to your data target and see the delta record.
Re: LO-Cockpit V1 and V2 update
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Also Refer this link:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Inventory.. dwload go thru it
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
*Steps*:
1st delet the septup table----lbwg(for application 3)(need to cleanup the setup tables in r/3 side by using (LBWG for AC:03)
1) Fill setup table (fill up the set up tables BX, BF and UM by using (MCNB,OLI1BW and OLIZBW).
for BX(Open stock)-tcode--MCNB,
for BF Tcode(oli1bw)
for UM tcode(olizbw)
after that pull data to BW with (Once the data is ready in RSA3, then in BW you have to set up compression for zero marker update for the Cube (coz is related to Noncummulative Keyfiger scenario) then load BX data. onces its completed load normally the BF and UMs.
BW side:-
make the compression
for BX load normally
and BF&UM(step table data):-compression with zero mark update(select that check box option)
after completion of compression do delta(Note: for deltas follow the compression normally)
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/c5/a26f37eb997866e10000009b38f8cf/frameset.htm
SD - Enterprise Sales and Distribution
SD comes under CRM application component (ERP Analytics).
sd flow
salesorder:
VBRK - header
VBAP - item
VBEP - scheduling
delivery:
LIKP - header
LIPS - item
billing:
VBRK - header
VBRP - item
shipement
VTTK - header
VTTP - item
customer data
SD links FI table
salesarea data general data companycode data
knvp kna1 knb1
material master data
SD link to MM table
salesdata Basic data salestext data
MARC MARA STXH(Textfile header)
MVKE MAKT STXL
process:
1.sales reresntive enter sales order in R/3 system, it sotres the transaction into three
SD tables.
2.delivery due list is executed for all sales orders and delivers are created in table LIKP, LIPS.
A goodsissue updating MKPF & MSEG.
3.invoice due list is then executed for all deliviers. after an invoice is created, which creates an acct.doc ( BKPF & BSEG, FI TABLES) and set up the receivalbe in table BSID (open tem).
4.The receivalbe is cleared when paymen check is required. anoher acct.doc is created ( BKPF & BSEG) the open receivable is cleared and table BSAD (closed line item) is updated
First u select application component.. SD,MM,FI,PM
then got to rsa5.. u can install data source...
after next step RSA6-Display data sources
Then select our ds which we need to enhance then click on the
append structure (application tool bar)
u can see start with ZAGTFIGL_4 ( fi example)
u given component name and component type ( here given to existing
data element)
save + activate....
then go to the t code CMOD...>there select the project
name--> go to the exit in RSAP0001->
or also u can goto tcode se37 fuction module.. EXIT_SAPLRSAP_001
transactional data
click on display...
then u can see INCLUDE ZXRSAU01( program ) double click it.....
then u can change option click it.
So please follow the link below:
http://help.sap.com/saphelp_nw70/helpdata/en/c5/bbe737a294946fe10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/17/cd5e407aa4c44ce10000000a1550b0/frameset.htm
Check these links,
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
http://www.erpgenie.com/abap/tables_sd.htm
http://www.erpgenie.com/abap/tables_mm.htm
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Re: LO-Cockpit V1 and V2 update
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Regards
CSM Reddy

Difference: Full load, Delta Load & INIT load in BW

Hi Experts,
I am new to SAP BW Data warehousing.
What is the difference between Full load, Delta Load & INIT load in BW.
Regards
Praveen

Hi Pravin,
Hope the below helps you...
Full update:
A full update requests all the data that corresponds with the selection criteria you have determined in the scheduler.
You can indicate that a request with full update mode is a full repair request using the scheduler menu. This request can be posted to every data target, even if the data target already contains data from an initialization run or delta for this DataSource/source system combination, and has overlapping selection conditions.
If you use the full repair request to reload the data into the DataStore object after you have selectively deleted data from the DataStore object, note that this can lead to inconsistencies in the data target. If the selections for the repair request do not correspond with the selections you made when selectively deleting data from the DataStore object, posting this request can lead to duplicated data records in the data target.
Initialization of the delta process
Initializing the delta process is a precondition for requesting the delta.
More than one initialization selection is possible for different, non-overlapping selection conditions to initialize the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the data
relevant for the delta process to the Business Information Warehouse in steps.
For example, you could load the data for cost center 1000 to BI in one step and the data for cost center 2000 in another.
The delta requested after several initializations contains the upper amount of all the successful init selections as the selection criterion. After this, the selection condition for the delta can no longer be changed. In the example, data for cost
centers 1000 and 2000 were loaded to BI during a delta.
Delta update
A delta update requests only the data that has appeared since the last delta. Before you can request a delta update you first have to initialize the delta process. A delta update is only possible for loading from SAP source systems. If a delta update fails (status red in the monitor), or the overall status of the delta request was set to red manually, the next data request is carried out in repeat mode. With a repeat request, the data that was loaded incorrectly or incompletely in the failed delta request is extracted along with the data that has accrued from this point on. A repeat can only be requested in the dialog screen. If the data from the failed delta request has already been updated to data targets, delete the data from the data targets in question. If you do not delete the data from the data targets, this could lead to duplicated data records after the repeat request.
Repeat delta update
If the loading process fails, the delta for the DataSource is requested again.
Early delta initialization : This is a advanced concept, but just for your information ...
With early delta initialization you can already write the data to the delta queue or to the delta tables in the application while the initialization is requested in the source system. This enables you to initialize the delta process, in other
words, the init request, without having to stop posting the data in the source system. You can only carry out early delta initialization if this is supported by the extractor for the DataSource that is called in the source system with this data
request. Extractors that support early delta initialization were first supplied with.

Delta and LBWE

Hi Gurus
I have understood the delta mechanisam for LO extraction ( LBWE >>>Job control ) where we first have to select direct delta ( for full load ) and queued delta ( for subsequent delta load ) Am i right?
now when we load the data we create 3 info pkg.
1.full load
2.Init
3.delta load
so would you pl tell me whats the difference between update mode we are giving on infopkg level and the things we are doing in LBWE under job control.? Pl help me to clear this doubt.
second thing is when we do extraction other then LO ( may be generic / from table / from FM ) why are we not going to LBWE and how we are managing delta in those case as job control will not there as we are not using LBWE.
pl help.

Hi krishna,
For the first question,
The update mode in the infopackage tells the system to identify the way it can bring the data into BW that is, if you select the full load it brings all the records or if you specify initialize delta process, it brings in all the history data and if you specify delta process, it brings in only the changed or recently created records.
The selection of the queue delta or direct delta in LBWE is to tell the system how to store the transaction data in the BW delta queue in source system(like R3)like if you say queue delta, then all the sales orders which you have created in OLTP system(R3 system)gets piled up in delta queue in the order in which they are created.So, setting in LBWE is totally different from setting in Info package.
For the second question, Only for Logisitics we use LBWE like for eg. Materials management , sales and distribution, etc and in other areas like FI and CO,there are standard settings through which you can get delta and i think you shall set up once those settings in source system and the delta is taken care of.
Hope it helps.
Message was edited by: Rao

Deleted bad delta and former good deltas form data mart to targets(5)?

Hi experts,
My process chain failed in continues for 5 days due to DSO activation issue. On further analysis I found a bad request with status red on july 3rd and their is no psa to fix it.
I deleted the bad request that is loaded on july 3rd with status red and all the god requests with status green on july 4th,5th,6th,7th and 8th.
The data load is going from data mart to 5 different targets (3cubes and 2 DSO's) and i deleted the requests listed above with all the 5 targets.
Know When I try to run new delta it is saying that 'new delta is not possible and asking for the previous deltas'
What to do know? Should I delete the init and reinit with out data transfer and load my new delta? I am affraid that I may loose data if i do this.
Thanks in advance.
Sharat.

Murali,
I have the failed delta in the targets (3cubes and 2 ods). I deleted the bad delta and the former good ones after july 3rd from all the five targets by verifying the technical name of the requests in the targets.
How should I proceed know?
Can I do a full repair request and new delta? or delete the init and reinit without data transfer and do a full repair and a new delta?
Please let me know. Thank you for your help.
Sharat.

DELTA AND INIT TO CUBE Simple

Similar Messages

Maybe you are looking for