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 |
| Short Description | Data Target "DataStore Object for Direct Write" |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | STRG | Character String of Variable Length |
| Length | 0 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| 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 | Text |
| Medium | 20 | Description |
| Long | 40 | Description |
| Heading | 60 | Description |
Documentation
Use
You use this node to save the results from an analysis process in a DataStore object for direct update. Every time the analysis process is run, all data in the DataStore object is first deleted and then the result is calculated and written to the DataStore object again. Thus every calculation of an analysis process corresponds to a full update with the previous deletion of the data that already exists.
If you want to compare multiple calculation results with one another, use the DataStore object for direct update as a temporary buffer for the calculation result of the analysis process. Execute the analysis process. Check the data in the DataStore object as needed. If the calculation result is okay, use an update rule to write the data to an InfoCube or a standard DataStore object.
Enhanced functionality
On the Target Area tab page, you can partition the DataStore object into several subareas. The analysis process then only deletes and writes data in each case in a partition. Use the target area if you want to parallelize the processing of an analysis process manually.
Example: You want to perform an ABC classification of customers per business area. To do this, an analysis process is created for each business area. Each analysis process reads only the data for a business area and writes the calculation result for just that business area. In this case, select the business area characteristic to restrict the partition and specify a characteristic value to restrict the partition. The analysis process then only writes data to this one partition. Additional analysis processes can write data to other partitions. If you create a separate analysis process for each business area, parallel processing can be started.
Runtime behavior
- When data is written, records are always inserted (INSERT). The analysis process is terminated if the inbound table contains several records for the same key. If necessary, use another transformation to aggregate the data in accordance with the key fields of the DataStore object before it is written to the data target.
- To enable mass data to be processed, data from the analysis process is processed internally in technical packages. When the data is written to the target area, the system saves the data of each package in the database. If, however, the analysis process terminates during execution, it is not possible to establish which data has been written to the target area up until the termination occurred. The data in the target area may be entirely deleted or may only exist partially.
In such cases, resolve the cause of the error and then restart execution. - Currently no lock is set when writing to a transactional DataStore object. This means that several analysis processes can write data to different partitions in the DataStore object. You need to ensure that no two analysis processes are writing data to the same partition in the same DataStore object.
- Currently, no validity check is performed on the field values before they are written to the target area. This means that the data is expected to have the following format:
- In the case of characteristics with master data tables, only valid characteristic values are transferred.
- The data exists in the internal format: NUMC fields contain leading zeros; for a date, all figures are filled; for fields with a conversion routine like ALPHA conversion, the conversion has already been performed.
System bahavior may be changed in subsequent releases to incorporate checks for the above properties (in order to ensure data consistency) and the termination of the analysis process where data consistency cannot be ensured.
Note
- Technically, a DataStore object can be used as both a data source and a data target in the same analysis process. However, as data is always deleted in the target area before data is read, this approach cannot be used to change a data field in a DataStore object.
- You can only use the key fields of the DataStore object to determine the target area.
- Fields that you have already defined as restricting the target area in the settings for the target area, can no longer be selected in field assignment for this data target.
- Entering a value in the Target Area tab page occurs in a similar way to entering a constant in the field assignment on the incoming dataflow arrow. The difference is the restriction of the target area in which the data is deleted and then into which new data is filled. For this, the only characteristics considered are those specified in the Target Area tab page. If the characteristic value is determined in field assignment, all data is deleted anyway.
- Queries are not currently supported on DataStore objects for direct update as master data IDs (SID) are not determined when data is updated to the transactional DataStore object. To do this, create an InfoSet for the DataStore object for reporting.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30B |
