SAP ABAP Data Element RSAN_WB_DT_ODS_SEL_FLAG (Restriction of DataStore Object)
Hierarchy
SAP_BW (Software Component) SAP Business Warehouse
   BW-EI-APD (Application Component) Analysis Process Designer
     RSAN_WB (Package) APD - Tool - User Interface
Basic Data
Data Element RSAN_WB_DT_ODS_SEL_FLAG
Short Description Restriction of DataStore Object  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type AS4FLAG    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Restrict. 
Medium 15 Restriction 
Long 20 Restriction 
Heading 20 Restriction 
Documentation

Use

You use this node to save calculation results from an analysis process in a DataStore object for direct update. With this data target you can use a DataStore object like a folder in the file system and store calculation results there under different names.

By entering values for single characteristics on the Target Area tab page, you can restrict the target area accordingly. This enables you to perform a type of versioning for the data in the DataStore object. The rest of the characteristics for which you enter no values, have to to be filled from the analysis process. When the analysis process is executed, the data in the target area is completely replaced with the newly determined data. If you do not restrict the target area, the entire content of the table for the DataStore object is deleted.

In the field assignment on the data flow arrow before the data target nodes, the key fields that were not defined in the Target Area tab page appear as the target structure, along with all data fields for the DataStore object. Key fields always have to be filled in field assignment. The assignment of data fields is optional. Unassigned data fields are set to their initial values by the system.

The update works as follows (in detail):

  • When the analysis process is executed, the data in the target area is first deleted; the data for the analysis process is then calculated and written to the target area.
  • In order to process mass data, the data from the analysis process is processed internally in technical packages. During writing, the data from each package is saved in the database. If the analysis process terminates during execution, the system cannot determine which of the data had already been written at that point in time. It may be that the data in the target area has been completely deleted or is only partially available.
    Eliminate the cause of the error and begin execution again.
  • If the input table contains several records for the same key, the system will terminate the analysis process. If necessary, use another transformation to aggregate the data before the data target.
  • Currently, field values are not checked for validity before writing. This means that data is expected to be in the following format:
    • For characteristics with master data tables, only valid characteristic values are transferred.
    • The data is in internal format: NUMC fields contain leading zeros; with dates, all digits are filled; for fields with a conversion exit the data is available in internal format.

      It may be that these checks are improved in subsequent releases.

Activities

  1. On the Data Target tab page, select the DataStore object for direct update that is to be filled.
  2. On the Target Area tab page, enter fixed values to restrict the key area.

    All of the data that is located in the key area selected on the Target Area tab page in the DataStore object is deleted before the data from the running analysis process is written. If you do not enter fixed values for the individual key fields, all of the data that matches the selection conditions of other fixed values is deleted.

  3. Explicity define the field assignment for this data target by double clicking on the inbound data flow arrow.

Example

You have modeled an analysis process that performs a customer evaluation. The result of the evaluation is an attribute Customer Class with the values: gold/silver/bronze. The analysis process delivers a table with columns Business Partner and Customer Class:

Business partner    Customer class

4711    Gold

4712    Silver

4713    Bronze

So that you can trace changes between customer classes, this evaluation should be executed once a month, and the result for each month saved.

To do this, create a DataStore object of type direct update with the key fields Calendar Month and Business Partner. Incorporate a Customer Class field in the data part. You then have a place in which to store the customer class for the business partner each month.

In this example, the target area is all dates in a month. On the Target Area tab page for the month, enter a value such as June 2003. In the field assignment on the inbound data flow arrow, you can now only assign the Business Partner and Customer Class fields.

Execute the analysis process. The result of the evaluation can be found in the DataStore object under "June 2003". If you want to perform the evaluation in July, copy the analysis process and, on the Target Area tab page in the data target, change the value from "June 2003" to "July 2003".

Further tips

  • Specifiying a value on the Target Area tab page is similar to specifying a constant in field assignment on the inbound data flow arrow. The difference is the restriction of the target area in which data is deleted and rewritten. Here only those characteristics are taken into account that are identified on the Target Area tab page.
  • At the moment, queries on DataStore objects for direct update are not supported as master data IDs (SID) are not calculated when you update to a DataStore object for direct update. Create an InfoSet for the DataStore object to report on it.

History
Last changed by/on SAP  20130604 
SAP Release Created in 350