Hello Guru's I am working on Write Optimised dso.

we have triggered full load from r/3 to Write Optimised DSO then we loaded to Cube. Now i would like to load the delta load to Write Optimised DSO and then to Cube. Can any one please explain me how does delta load works for Write Optimised DSO . i also need to create a process chain for daily load for write optimised Dso. thanks PK ANSWER : 1) hi, As far as i know Write Opt DSO does not support Delta. Whenever we use Write Optimised DSO,it supports only FULL Load. Hence when we want to capture Delta we use one more DSO on top of the Write Optimiised DSO. i.e DSO1->DSO2->Cube Where DSO1=WriteOptimised DSO2=Standard DSO. the Standard DSO suports DeltaS. Again this Scenerio is mostly used for APD Scenerios. Rgds

2) Not sure if you got the answer to this but just came across this thread and found it unanswered thus thought to reply. Well Write opt DSo doenst support (after image before image) delta bt support request level delta. Taking your case where in you need before image after image in that case you need to have a standard DSO before loading data to the cube ie 1 )R/3 to Write Opt DSO 2) Write Opt DSO to Stnd DSO 3) Stnd DSO to cube

Here the Write Opt DSO support request level delta ie the request that are loaded new and are not updated will only be loaded to standard DSO and here the after image before image would work and finally after loading the data to the cube the aggregation result would be fine as the delta in cube would be fetched from the change log table of the standard dso.

Thanks Puneet 3) Hi, The Write optimized dso dont have change log table.it havenot maintain the delta recards.it have over write funtionality.so need to change the option in DTP. Follow these steps: i) you load the data to DSO through DTP u need to chose the Full option. then every time new request is updated ii) Load the Data from DSO to cube through DTP u need to chose the Delta option . then it will update delta records to cube. it will help you Regards Suman

How to delete a inactive transformation in BI Productive System

Hi, When I transported the transformation from our BI development system (R/3 source DEV001) to our BI productive system (R/3 source PRD002), the system create two transformations in the productive system, one assigned to DEV001 and other assigned to PRD002. The first transformation is inactive because the source system DEV001 doesn't exist in BI productive system. How can I delete this inactive transformation in the productive system?. Thanks.!

The only way that you'd be able to delete the Transformation in the production environment that's pointing to your R3 development environment DataSource, without also deleting the Tranformation pointing to the R3 production environment DataSource, would be to have the client opened and manually delete. Open the client ---> delete the transformation. Send the delete transport from Dev to prod.