Handling DELTA to YTD cube

Hi All,
Our Data flow is a follows:
*Currently the load is a Full Load.
Source system --->Montly Actuals cube ---> YTD Actuals cube (Year till date cube)
Requirement is to change the current load from Full to DELTA load
My question is while we load DELTA from Monthly Actuals cube to YTD Cube, is there any different approach how the DELTA load needs to be handled? Is there any different approach in handling DELTA to YTD cube?
Please advise,
Regards,
Rama

Hi Rama,
I already posted this issue in fourm i got reply from people since the YTD data is always changed as times going on. It is not a good way to calculate it in Cube or Object. It is better to calculate when query is executed
But my requirement is in Cube level to calculate YTD amount for the value coming from New commision amount, source is Cube and target is also cube.
In detail i have a info object 0FISCVARNT which gets the month and year data i.e 1/2010,2/2010 etc
I have a New Comission Field(XYNEW_AMT) say 100,200
and a YTD field XYTD_AMT
Say When data is loaded through the 1st request
0FISCVARNT XYNEW_AMT XYTD_AMT
1/2010 100 100
2/2010 200 300
3/2010 300 600
When data comes in the second request
0FISCVARNT XYNEW_AMT XYTD_AMT
4/2010 100 700
5/2010 200 900 (Actually it should populate this value)
If you have any related solution. Please assist me.
Regards
Murali

Similar Messages

How will the system handle delta in the below scenario

How will the system handle delta in the below scenario
Day 1
DS--->DSO
PSA
Document Number| Customer | sales value
1001| RAMLAL | 10000
Your change log for DSO will read
Req1| 1001|RAMLAL|10000|N
DSO(overwrite)
1001|RAMLAL|10000|
Day 1
DSO--->Cube
Req1| 1001|RAMLAL|10000|
Day2
DS--->DSO
PSA
Document Number| Customer | sales value
1001| RAMLAL | 30000
Your change log for DSO will read
Req2 | 1001 | RAMLAL | -10000 | X
Req2 | 1001 | RAMLAL | 30000
DSO(Overwrite)
1001 | RAMLAL | 30000
Day 2
DSO--->Cube
Req1|1001|RAMLAL|10000|
Req2|1001|RAMLAL|20000|
Please explain with example
Scenario 1: Req1 & Req2 are deleted ONLY from change log on Day 3
On Day 4:
DS--->DSO
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000|C
What will happen to the Sales Value in the cube?
What will happen to the Req1&Req2 in the cube?
Thanks
Tanya

Tanya,
Please explain with example
Scenario 1: Req1 & Req2 are deleted ONLY from change log on Day 3
On Day 4:
DS--->DSO
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000|C
What will happen to the Sales Value in the cube?
What will happen to the Req1&Req2 in the cube?
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 10000 |C
--> Here 1000 is not correct value, as 1000 is change to 3000. It should be 3000. record should be as below.
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 30000 |C
--> As this data related to sales, and i hope you are using standard ABR extractors(Business Content).
ABR datasources delivers before and after images.
Before image:
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | -3000 |C
Before image:
Document Number| Customer | sales value|STOR_NO(ROCANCEL)
1001| RAMLAL | 0 |C --> value changed from 3000 to Zero.
If you are loading in additive or Overwrite into an ODS total sales for 1001 at end of day 4 will be Zero.
Hope it helps
Srini

Exception not handled by the Collaxa Cube system

Hi!
i have plsql procedure and i published it as a web service using JDev 10.1.3, web service is deployed on OC4J 10.1.3. When i call it directly, everything works fine. When i make a BPEL process jast wrapping this web service (receive, assign, invoke, assign, reply - that`s all) the web service is invoked fine without error, but then error appears in the bpel process:
Exception not handled by the Collaxa Cube system. An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException at com.collaxa.cube.engine.delivery.DeliveryHelper.saveAttachments(DeliveryHelper.java:436) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.saveAttachments(WSIFOperation_ApacheAxis.java:3521) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.populateOutMsgParts(WSIFOperation_ApacheAxis.java:1403) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.buildResponseMessages(WSIFOperation_ApacheAxis.java:1303) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISRPCStyle(WSIFOperation_ApacheAxis.java:1815) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1613) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1083) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452) at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:120) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:153) at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:486) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:520) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:435) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132) at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:101) at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:479) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:120) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:70) at _ngDoInitiate._jspService(_ngDoInitiate.java:289) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824) at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) at _displayProcess._jspService(_displayProcess.java:792) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222) at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) ". Exception: java.lang.NullPointerException Handled As: com.collaxa.cube.CubeException
i found similar problem calling axis web service, but this web service runs on OC4J ... any suggestions what to do?
Thanks,
Tomas

User,
I'd probably try the [url http://forums.oracle.com/forums/forum.jspa?forumID=212]BPEL Forum for this one.
Regards,
John

How to handle delta failure in COPA?

HI FOLKS
I appreciate if any one can take me through how to handle delta load failure in COPA?Also I need whether we have any other method for 2004 release...to handle delta issue in COPA.......
no doubt Step by step walk through will definetely gain full points...
Regards
GTR

Hi Indu,
I will try to implement this HowTo and see what happens. I hope, it works with it.
Thanks for your advice.
Kind regards,
Ali

How to handle delta failed process chain steps

Hi All,
I have a query regarding process chains were in processstep has delta load and there is dependency between the predeseccor and successor process steps,then
if the delta load fails due to any one of the following reasons
1) due to remote_icp locked the prtclr Infoobject the process step is executing .
2) due to any psa records errors and so on
Then how to handle delta and see that correct delta records were updated .
Because again for the nextday loads if the previous delta is incorrect it will give pop-up message that it is not possible.
If any suugestions pl guide me.
thanks
Venkat
[email protected]

1)Remove the lock by force from sm12 or wait till the lock is gone.Then see if the delta data has come till the PSA.Mark failed delta load RED and back it out from target.Then read everything in manually from PSA to target.
In process chains u can go the monitor entry for the failed load by..highlight chain..click log icon..give selection..for proper selection..see the failed node..right click..display messages..click on process monitor.
Sometimes even if infopackage is run successful manually,next steps in the chain do not kick off.
Use Siggi's excellent blog on this..(it works really well)
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
2)Make request RED and back it out from target.
Correct records in the PSA and read everything in manually from PSA to data target.
Then use Siggi's blog.
If data hasnt come to PSA do a delta repeat.
Always check yesterday's chain run about 1-2 hrs before today's chain kicks off.
cheers,
Vishvesh
Message was edited by: Vishvesh

Delta update from cube to cube

How will be delta calculated for Cube to cube load, as in case of ODS changelog table.
Thanks in Adv
Shrish.

Hi
Regarding Generic Extraction:
You can find the Safety interval in R/3 -> RSO2 -> Data source -> Delta. Generally if the delta is based on calday option then it is 1 day and for timestamp based it depends on the data load frequency.
this is from help.
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.

Interview Q: 'how did you handle delta'

Hi BW experts,
I've been asked this question in the interviews, 'how did you handle delta?' I know how to create delta. What is the right answer for this type of question? should I start explaining what/how we did in my previous company?
I'd appreciate and assign points, if someone can provide the answer for this.
Thanks,
Sam

The answer depends on what you have been talking about, I mean the previous discussion you had with the the interviewer. There are different way of handling delta... example:
1. The extractor itself handles delta and it send you the before and after image of the changes.
2. sometimes you load the data direclty to ODS and depending on the key you have in ods, the delta is being handled.
3. In somecases, you may not need to worry about handling delta at all (full load)... going back to the quesion you asked, that depends on the discussion you had with him/her.
thanks.
Wond

Loading full (DTP)to Dso and then Delta to info cube

Hi Experts,
I am loading data from Oracle and the data voulme is very huge.
The only option i could have in the infopackege (to PSA) is Full load.
I am loading a FULL DTP to DSO and the a Delta DTP to cube.
So for the next load i should delete the request in PSA and DSO and keep the request in the cube.
How could i delete the request in DSO without deleting the request in cube?
Is there any alternate solution to improve the load time?
Please advise.
Thank you.
Priya

hai priya,
u r loading the data to dso and after that from dso to cube, is it correct ???
if it is correct u have to do full load to cube also,
otherwise there is another option is please choose 'write optimized DSO' instead of Standard DSO
if still u r not cleared plz post clear information so that i can suggest u

Delta Load to cube

Hi All,
I have an issue in the delta load to cube.From Nov 11 onwards the delta load is not picking any data.It shows 0 from 0 records in the monitor screen.Could anyone please help me on this.
Thanks in advance,
Drisya

hi Drisya,
actiavte the transfer rules & update rules once & then load the data.
u said that 0 from 0 records it is showing .Is it showing status yellow OR green?
2. ur loading data from ODS to cube OR directly to cube
If it is yellow force that to red
actiavte transfer structure & update rules and do loading again.
If ur loading through ODS do export generic data sorce at ODS level by right click
Thanks,
kiran

Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Dear experts,
For Cube : 0CRM_PRI - Service Orders and Confirmations: Item
Source data is from Two ODS
1. Confirmations (Item Data) : 0CRM_CNFI and
2. Service Orders: Item Data : 0CRM_PROI
I have done Init upload to this cube from both this ODS.
I am not getting delta option to this.
When I am trying update Delta after init from ODS message is No new deltas in DataStore object 0CRM_PROI for update. No delta option available . It is showing Initial and Full Update option only.
How i can initiate delta option for this Cube ? Please update us.
Thanks in advance.
Regards,

Hi,
you can use DTP's to laod data from ODS to cube .. it will take deltas ..
With a data transfer process, you can transfer data either in full extraction mode or in delta mode. In full mode, the entire dataset of the source is transferred to the target; in delta mode, only the data that was posted to the source since the last data transfer is transferred. The data transfer process controls delta handling and therefore allows you to fill several targets with different deltas from one source. With a data transfer process, you do not need to explicitly initialize the delta method as you do when copying data with an InfoPackage.
or you can create a sepeate Ip for delta apart form full and init .. that will laod delat data in cube ..
Regards,
shikha

Number of new delta records into cube

Hi,
The deltas are running for the cube. Client wants to know how many number of records are loaded in the cube for each load.
I mean when the delta load (process chain) completes it should send an email with number records loaded in to cube.
Please any one help me out on this issue. Thanks for your help in advance.
Thanks,
Raj.

I have tried for 0MAT_PLANT as yours.You can see the record count as 67 records. I have tested this on BI 7.0 SP 16
.I got mine as follows:
Test mail
Process ZI_8SMATGMP2_full_Man Of Type Execute InfoPackage Has Status Successfully completed (Process Chain Temp) Log for This Process: Data successfully updated Diagnosis The request has been updated successfully. InfoSource : ZNK_OP_MAT_PLANT Data type : Transaction Data Source system: BW1110 Log of Respective Background Job: Job started Step 001 started (program RSPROCESS, variant &0000000048822, user ID BTC_GBL_BW) Data saved successfully Start InfoPackage ZPAK_43YOZD7INDYOXD6WA8VV2Z257 InfoPackage ZPAK_43YOZD7INDYOXD6WA8VV2Z257 created request REQU_49G2VHO86U1Q27NQC52VN7F8G InfoPackage ZPAK_43YOZD7INDYOXD6WA8VV2Z257 Started In Process Chain ZTEMP; Generated Request: REQU_49G2VHO86U1Q27NQC52VN7F8G Job finished Information for Process Master data table: 0MAT_PLANT Data Type (D- Trans.Data, H - Hier., M - Mast. Data, T-Text): D PSA Table: 8SMATGMP2_BA
Number of Data Records Received: 67 Number of selected data records: 67 Request Number: REQU_49G2VHO86U1Q27NQC52VN7F8G
Edited by: Manga Paidikondala on Apr 11, 2008 12:35 PM

How to load delta for 0PC_C01 cube?

Hi all,
I am working on Product Cost Controlling Infoarea. In that I am working on cubes
CO-PC: Cost Object Controlling :0PC_C01 Having Info sources 0CO_PC_02,0CO_PC_01 when I am scheduling Infopak it is having update option only " Full Update".
I have done the FULLUPDATE. But the problem is now I have to do "Delta Update"
What i have to do ?
how I will load delta into Infocube?
Plaese suggest me regarding this.
Points will be Rewrding.
Thanks,
kiran.

Hi Kiran,
hwat version of BI in?
if its not 7 you can try this...
Do you have the option to dona n Init in your infopackage?
If yea, run an init. Only if you have have an init for a target, does the new infopackage (which you will hve to make to do a delta after an init), gives you an option of a delta.
Let me know if it workeed.
Tke cre
Message was edited by:
Tessy Thomas

Delta - Purchasing , Inventory Cubes

I want to set up the delta mechanism for 0PUR_C01 , OPUR_O01 , 0PUR_C08 , 0IC_C03 and 0COPC_C04 business content cubes.
In RSA7 , for the relevant datasources , I see 0 records. Can some one tell me , how to enable the delta for these datasources:
2LIS_02_ITM
2LIS_02_SGR
2LIS_02_SCN
2LIS_02_CGR
2LIS_03_BF
2LIS_03_UM
0CO_PC_ACT_02
0CO_PC_ACT_05
Thanks

Hello Jimmy,
Assuming that you have installed these from the business content and the respective datasources on r/3 side are also active(i.e u can see all of these in rsa6),
you need to run the setup on r/3 side in the logistic cockpit section for the respective application component.
The set up tables when filled, can be pulled(the data) in bw with initialisation option.
Once the init requests in these cubes are loaded, you need to set up delta jobs on the r/3 side. please refer to the types in the earlier answers/posts like direct delta etc.
once the delta jobs are scheduled on r/3 side, you can view them in rsa7. the delta queues are populated after the delta runs on r/3 side and seen in rsa7.
these then can be pulled in bw by schduling bw jobs with delta options.
the selections used in inits can be automatically picked up in these delta jobs(on bw side).
hope it helps..
thanks,

Delta load to cubes from Datamart

Hi Gurus:
We load data from ODS (Datamart) to cubes. I did the INIT & few Delta lods were also done.
I found a bug in the update rule & that has been fixed. I want to DELETE whatever small data in the cube and then do a FULL load from ODS to cube. Can I do this & will that impact delta setup...
Please suggest. I will be happy to assign the points.
Thanks.

Hi,
Yes you Can.
Delete the Requests loaded from the ODS.
Delete the Datamart Status in the ODS.
Just load the Data from ODS to CUbe with Option Init with Data Transfer.
If you have a huge amt of Data first go for Full and then Init without Data Transfer.
Thanks,
-VIjay

What happend to past delta data if we delete Delta INIT from Cube? safe ?

Hi Friends,
we have a cube where delta data is loaded daily from ODS.
So, cube have many delta requests and data is compressed.
Now have some problem and need to delete Delta INIT from this Cube and run fresh delta INIT again into Cube from ODS. Is that safe ?
If we do this...is there is any problem with past delta data availble in the Cube?
Please confirm..
Thanks
Tony

Hi,
I told you to check this before deleting the init as it very tough to manage it after that.
Now those delta request are missed and I dont think can be retrieved without doing a full repair with proper selection.
If you do a new init then there should be no request without a check for data mart status??
So you found it before deleting the init??Then you should not have deleted the init as I told earlier.
The only option is too reload the whole histroy again if you are not able to load it through selections in infopackage.
First do a selective deletion from the cube for the same selections and then schedule the full load for those selections from DSO.make sure these selections cover the whole scenario.
You cannot do anything else now to correct it.
If you data is not huge in cube then delete the whole data and reload it.
Schedule multiple loads from the DSO at the same time through different infopackages.
this will save time as weill will do the loads in quick time.
Thanks
Ajeet

Handling DELTA to YTD cube

Similar Messages

Maybe you are looking for