Technical Data
Function Is |
Changed |
In Release |
Software Component ● Component: SAP NetWeaver ● Release 7.0 |
Assignment to Application Component |
BW-WHM Warehouse Management |
Country Setting |
Valid for all countries |
The ODS object was renamed to DataStore object.
With SAP NetWeaver 7.0, the following new features are available for DataStore objects:
Now you can delete active requests in a DataStore object in parallel. Up to now, the requests were deleted serially within an LUW. This can now be processed by package and in parallel.
Now you can set the runtime parameters of DataStore objects by object and then transport them into connected systems. The following parameters can be maintained:
● Package size for activation
● Package size for SID determination
● Maximum wait time before a process is designated lost
● Type of processing
○ Serial
○ Parallel (batch)
○ Parallel (dialog)
● Number of processes to be used
● Server/server group to be used
In addition to the configuration of object-specific settings, there is also the option of setting default values. This are always used when there is no object-specific entry.
For the request operations executed on DataStore objects (activation, rollback and so on), there is now a separate, detailed monitor.
In previous releases, request-changing operations are displayed in the extraction monitor. When the same operations are executed multiple times, it will be very difficult to assign the messages to the respective operations.
In order to guarantee a more simple error analysis and optimization potential during configuration of runtime parameters, as of release SAP NetWeaver 7.0, all messages relevant for DataStore objects are displayed in their own monitor.
The monitor offers the following functionality:
● All operations for a request at a glance
● Hierarchical display of messages: messages are assigned to the triggering data package or main process
● Detailed information at runtime of the individual processes or operations, along with display of runtime statistics:
○ Process with shortest/longest runtime
○ Average runtime
○ Executed database operations
● Detailed information on runtime environment or runtime parameters
Up to now it was necessary to activate the data loaded into a DataStore object to make it visible to reporting or to be able to update it to further InfoProviders. As of SAP NetWeaver 7.0, a new type of DataStore object is introduced: the write-optimized DataStore object.
The objective of the new object type is to save data as efficiently as possible in order to be able to further process it as quickly as possible without addition effort for generating SIDs, aggregation and data-record based delta.
Data that is loaded into write-optimized DataStore objects is available immediately for further processing. The activation step that has been necessary up to now is no longer required. Note here that the loaded data is not aggregated. If two data records with the same logical key are extracted from the source, both records are saved in the DataStore object. The record mode responsible for aggregation remains, however, so that the aggregation of data can take place at a later time in standard DataStore objects.
Furthermore, during loading, for reasons of efficiency, no SID values can be determined for the loaded characteristics. The data is still available for reporting. However, in comparison to standard DataStore objects, you can expect to lose performance because the necessary SID values have to be determined during evaluation.
The data that is already maintained is no longer used and has to be transferred from the maintenance view RSCUSTA2 into the new configuration interface.
Check the settings in Customizing at SAP Customizing Implementation Guide ® SAP NetWeaver ® SAP ® Business Intelligence ® Performance Settings ® Maintain Runtime Parameters of DataStore Objects.
