Direct DSO.

Hi
Im not sure whether the data will be overwritten for the same key fields in Direct DSO. Please find below my Direct DSO design:
Key fields : 0DOC_NUMBER, 0S_ORD_ITEM, 0VBELV, GSS1POSNN
Data fields : GSS1STS (Status), GS1JBDATE (Date)
The direct DSO is updated through a program. I just want to find out what will happen if we have the same key fields, the data will be overwritten or added.
Regards
Sadeesh

Hello,
Direct DSO has just the active table. And data is written in the DSO as per the normal table concept.
Hence data with same will be overwritten, if you use the correct (modify) ABAP statement.
I think below is some relevant info:
Definition
The DataStore object for direct update differs from the standard DataStore object in terms of how the data is processed. In a standard DataStore object, data is stored in different versions (active, delta, modified), whereas a DataStore object for direct update contains data in a single version. Therefore, data is stored in precisely the same form in which it was written to the DataStore object for direct update by the application. In the BI system, you can use a DataStore object for direct update as a data target for an analysis process. More information: Analysis Process Designer.
The DataStore object for direct update is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Structure
The DataStore object for direct update consists of a table for active data only. It retrieves its data from external systems via fill or delete APIs.
The following APIs exist:
RSDRI_ODSO_INSERT: Inserts new data (with keys not yet in the system).
RSDRI_ODSO_INSERT_RFC: see above, can be called up remotely
RSDRI_ODSO_MODIFY: inserts data having new keys; for data with keys already in the system, the data is changed.
RSDRI_ODSO_MODIFY_RFC: see above, can be called up remotely
RSDRI_ODSO_UPDATE: changes data with keys in the system
RSDRI_ODSO_UPDATE_RFC: see above, can be called up remotely
RSDRI_ODSO_DELETE_RFC: deletes data
The loading process is not supported by the BI system. The advantage to the way it is structured is that it is easy to access data. Data is made available for analysis and reporting immediately after it is loaded.
Creating a DataStore Object for Direct Update
When you create a DataStore object, you can change the DataStore object type under Settings in the context menu. The default setting is Standard. You can only switch between DataStore object types Standard and Direct Update if data does not yet exist in the DataStore object.
Integration
Since you cannot use the loading process to fill DataStore objects for direct update with BI data (DataSources do not provide the data), DataStore objects are not displayed in the administration or in the monitor. However, you can update the data in DataStore objects for direct update to additional InfoProviders.
If you switch a standard DataStore object that already has update rules to direct update, the update rules are set to inactive and can no longer be processed.
Since a change log is not generated, you cannot perform a delta update to the InfoProviders at the end of this process.
The DataStore object for direct update is available as an InfoProvider in BEx Query Designer and can be used for analysis purposes.
Regards,
Shashank
Edited by: Shashank Dighe on May 29, 2009 9:21 AM

Similar Messages

Are these key fields in 'Direct Update' DSO table in BW on HANA (BW740SP7) correct?

Pls see below for a very strange behaviour of all active tables of type 'Direct Update' DSO in our system.
Is this a bug or is this somehow supposed to be like this (i.e. a feature)?
DSO definition:
Active table of type 'Column Store' - note fields marked as 'Key' different from DSO definition:
The DSO table content:
In ABAP executing the following select on the DSO table:
The result is garbage (the content of QQQPARST0 lands in /BIC/QQQPAFL0 and QQQSCPRO lands in /BIC/QQQPARA0):

Dear Sundaresan,
thanks for this suggestion, but I have posted the question in the following forums:
SAP Business Warehouse: What is this with the 'Direct' DSO table in BW on HANA (BW740SP7)
SAP BW powered by HANA: Direct Update DSO keyfields in RSA1 <> SE11 & SELECT returns garbage
ABAP for SAP HANA: Direct Update DSO keyfields in RSA1 <> SE11 & SELECT returns garbage
So far no real luck but maybe soon
Greetings

BW Datasource on an Infoset Query based on 2 DSO Active tables

Hello,
We have created a Datasource in the BW system over an Infoset query (through SQ02) built on 2 DSO tables.
In RSA3, this datasource is working fine - it shows us some data (close to 1000 records).
The issue is when i try and run a infopackage for the datasource.
The request times out and no records are fetched.
I have added all the users to the Infoset user group - so, no issue with the authorization.
IDoc Statuses changes from 53 --> 62 --> 64 --> 50.
The extraction process does not complete - does not get the no. of records sent.
Can anybody point to a probable cause here?
Thank you.

IDoc logs do not say much.
Status Record 53: IDoc was successfully transferred
Status Record 62: IDoc passed to application; Direct call started
Status Record 64: IDoc ready to be transferred to application; No filter, no conversion
Status Record 50: IDoc added
Then, it does not go any further.
We're using the Datasource on the Infoset query because we could not use the traditional BW infoset.
Datsource is used to feed a DSO as we directly could not use anything else (we're trying with an expert routine also).
The issue is that the base DSO tables are huge and querying on them (using SELECT) is taking a very long time.
So, we thought of using an Infoset to create a view and then populatet he data.
In an traditional infoset, we could not specify a condition with a range. So, the infoset query through SQ02.
I have not tried using an APD, but that might be a good option.
Only thing, we'll have to use a Direct DSO - which i am not sure will satisfy our requirement.
Thank you.

Differentiate the types of DSo Objects

Hi Friends,
can u pls differentiate the standard,wtrite optimised and direct dso objects. in wat scenarios we should use the different types of dso objects.
thanks
kumar

please check in SDN before posting

How can i Read and Delete data in Infocube

Can some help me how to read and delete data in infocube before loading data from direct DSO.
I should be able to read and delete condition with combination (0FISCPER, 0COMP_CODE).
Let us say we load JAN, comp _ code : 0001 (10 records )and JAN comp _ code :003 (30 records ) and JAN, comp _ code : 004 (20 records ) to infocube
second time if DSO gets data of JAN, comp _ code : 0001 (40 records ) it doent need to be 10 old + 30 new, it can be 9 old 21 new lay i need to delete 1 old rec which i dont need. so that is the reason i want delet all JAN, comp _ code : 0001 recods before loading.
Can some one help me

Hello,
You could use the selective deletion available with the cube to get the selective data for 0FISCPER, 0COMP_CODE combination deleted.
If you go in the manage of cube & Content tab, you would find the selective deletion option at the bottom of screen.
If you enter the option, you could give your selections for deleting the records and run the job.
Please let me know if you need any more help.
Regards,
Pankaj

Does APD support delta load?

Hello experts,
does the APD support delta load of data in case the data target is
1. a DSO?
2. an InfoCube?
Many thanks in advance,
Marco

Hello Marco,
As far as APD is concern with data source DSO's, it supports only Direct update DSO..& Direct update DSO not support Delta ,hence have an intermediate standard DSO before the Cube which will capture the Deltas....
The flow should be like,
Direct DSO-->Standard DSO --->Cube
Hope it clears your doubt scenariowise.
Thanks,
Santosh

Current fiscal year period in BEx

Hi,
I have a requirment. i have a BEx query, that query is a source of APD and data is store in direct DSO.
i need to run this query every month and load current fiscal yer period data into the DSO.
i need BEx variable to filter the data for current fiscal year period.
I have fiscal year period char. in query definaton
Please help me to get this.
Thanks.
Edited by: Pria Gupta on Nov 24, 2011 2:18 AM

Use variable 0F_CUFPE Current Period of Fiscal Year (Formula Variable)
Re: how to get default value fiscal year period in Variable
Regards,
Sushant

Direct update DSO filed is missing in RSINPUT

Hi Experts
I am facing an issue while maintaining data for Direct Update DSO.
I create a Direct Update DSO with some key fields and two data fields , the two data fields are the same type with'CHAR' and the same length with '01'. Actually , they are flags for different purposes.
when I am trying to maintain data for this DSO in t_code RSINPUT, only one data field presents.
as showing above , field RL000966 is missing in RSINPUT.
I need maintain two flags in one record , please tell me how to do?
Thanks.

Hi,
Check whether the infoobject RL000966 is an attribute only infoobject !!
If "attribute only" is checked then uncheck it and then try .
Regards.

Loading complex report data into a direct update DSO using APD

Dear All,
Recently, I had a requirement to download the report data into a direct update DSO using an APD. I was able to perform this easily when the report was simple i.e it has few rows and columns. But I faced problems If the report is a complex one. Summing up, I would like to know how to handle the scenarios in each of the following cases:
1.   How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
      key fields of DSO and the remaining to the data fields? Correct me.
2.   What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
      system and then include these in the DSO data fields to accommodate the extracted data ?
3.   How do I handle the Free Characteristics and Filters ?
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
     use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
     shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
I would appreciate if someone can answer my questions clearly.
Regards,
D. Srinivas Rao

Hi ,
PFB the answers.
1. How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
key fields of DSO and the remaining to the data fields? Correct me.
--- Yes , you can use the elements in the ROWS in the Key fields, but in case you get two records with same value in the ROWS element the data load will fail. So you basically need to have one value that would be different for each record.
2. What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
system and then include these in the DSO data fields to accommodate the extracted data ?
Yes you would need to create new Infoobjects for the CKF's and RKF's in the Report and include them in your DSO.
3. How do I handle the Free Characteristics and Filters ?
The default filters work in the same way as when you yourself execute the reoprt. But you cannot use the Free characterisitics in the APD. only the ROWS and cloumns element which are in default layout can be used.
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
--- Yes you would need to create 10 different APD's. Its very simple to create, you can copy an APD. but it would be for sure a maintance issue. you would have to maintain 10 APD's.
Please revert in case of any further queries.

How to delete the request in Direct Update DSO

Dear Gurus,
I have a situation where I have an invalid characteristic loaded into the Direct update DSO. This is related to Spend Performance Management. This DSO is loaded through a data source with the option Without Archive. So, I cant see any request in this DSO. This DSO will then supply data to another DSO which is standard DSO.
The data Activation job in the standard DSO is failing.
My question is I have to delete the request from the Direct Update DSO and then load it to Standard DSO. I have already repaired the data in PSA.
Your Kind help is greatly appreciated.
-Mohan Kumar

You must be using some fill or delete APIs to fill the data in Direct update DSO.You can't create transformation to fill the data in DIrect Update DSO as you do in Standard DSO.You will not see request number under the manage tab for direct update dso for any load.
Whenever you will fill the Direct update DSO next time,previous data gets deleted automatcally. For Direct update DSO there can only be a Full Update.So just load the data using API's and previous data will get deleted automatically
Edited by: shyam agarwal on Mar 2, 2012 7:48 AM

Can I write data into DSO directly ( by editing it)

Hi Gurus,
Here I have an issue where I was asked to create an object in BI7 where I can enter data directly into that object regularly i.e day to day basis. Is it possible if yes please give me the navigations and links if available to fix my issue.
Best Regards
Mohan Kumar

Hi Mohan,
Writing data directly into DSO means, we had a scenario where in the user will be entering the data at the transaction sceen and the same moment it need to get into the DSO. For that we have used the transactional ODS which can be used to writing purpose. But one thing with that isit can have only the active data table.
Regards
Vijay

Use Custom Extension Web Item to Retrieve DSO Data Directly

Hi experts,
Is it possible to use Custom Extension Item in BEx WAD to retrieve DSO data directly? The idea is to display master data for a line item (e.g. customer name, id, address etc.) in the header section of a Web Template. If it is possible, how can I implement that?
If not, is there any other possibility to fulfill the requirement?
Thanks in advance.
Regards,
Joon

Hi experts,
any update on this?
Thanks,
Joon

What is the main difference of Direct update DSO and Write optimized DSO

What is the main difference of Direct update DSO and Write optimized DSO?

Hi chandra:
Check this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
You can find another difference on page 147, section "Reclustering DataStore Objects" of the document "Enterprise Data Warehousing"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a?quicklink=index&overridelayout=true
>You can only use reclustering for standard DataStore objects and DataStore objects for direct update. You cannot use reclustering for write-optimized DataStore objects. User-defined multidimensional clustering is not available for write-optimized DataStore objects
Regards,
Francisco Milán.
Edited by: Francisco Milan on Aug 11, 2010 7:09 PM

Can i load data directly into DSO without PSA?

hi friends,
can i load data into DSO directly without PSA(without infopackage), if possible ple let me know where can i do that in dtp?
regards
ss

Suneel,
Why don't you try it to see if error DTP is possible with a flat file ds or not?
Or, extrapolate logically -
- An error DTP is based on a regular DTP.
- In any situation where you can have a DTP, why can you not have an error DTP? I would think there would be no reason for this.
At this point of my reasoning I will give it a try to validate if my assumption (DTP possible==>Error DTP possible) is correct or not.
regards,

Difference between - Write Optimized and Direct Update DSO

Hi Gurus,
I know the similarities of the Write Optimized and Direct Update DSO.
But I want to know what is the difference between the both.
Can any expert let me know the difference between the both please.
Thanks

Hi,
Write Optimised DSO:
Write optimsed DSO has been designed to be the initial staging of the source system data from where the data could be transfered to the standard DSO or the Infocube.
The Data is immediately written to the further data targets.We can save the activation time.Reporting also possible on this.
SAP recommends to use Write-Optimized DataStore as a EDW inbound layer, and update the data into further targets such as standard DataStore objects or InfoCubes.
Direct Update DSO:
Dat a store object for direct update conatains daya in a single version.therefore data is stored same form in which it was written to DSO for direct update by the application.We can use this type of DSO for APD.
In IP we can use this dso and directly we can enter the data using RSINPUT.
Thanks
Madhavi

Direct DSO.

Similar Messages

Maybe you are looking for