This post shows how to administer DataStore object (advanced). This post also shows how to delete and compress requests of a DataStore object (advanced).
You can display technical information about the contents of a DataStore object using the Manage DataStore Object function. You can perform administrative tasks, such as delete requests. As a prerequisite, the DataStore object must be active.
- Open your advanced DataStore Object (Advanced) and choose the Manage the DataStore Object (Advanced) icon.
- The system displays all requests that are loaded to the DataStore object. You can group the requests by day, month, or year. The status displays as cumulative. The DM flag indicates whether the deltas have been updated to other connected InfoProviders. A flag is not shown for full updates or if an InfoProvider is not connected. The TSNs (transaction sequence numbers) display in a monotonously ascending order.
- Choose the request to call the detail view. You can view details about individual load requests here. You can also view logs and call the monitor.
- You can activate load requests. To activate multiple load requests using a single activation request, choose Activate.
- You can delete load requests. You can delete multiple requests at one time. Load requests cannot always be deleted. Double-clicking a request to display the details of the request, a process log, and a history.
- Choose Environment → Display New Data in the main menu to view the content of the inbound table. Choose Display Active Data to view the content of the table of active data. Choose Display Change Log to view the content of the change log.
- Choose Environment → Delete Active Data in the main menu, to delete data from the active table, and if required, rebuild the data later. This also applies to the data of the inbound table and the change log.
DATASTORE OBJECT (ADVANCED) ADMINISTRATION
In a cube like DataStore Object (advanced), you can delete requests only if they are not activated.
In a DSO-like DataStore Object (advanced), you can just roll back requests because the system must use the change log to find out how the data looked like before the load.
If a request has already been loaded to a subsequent target, you cannot delete it. First you must delete it from the subsequent target and then you can delete it from the source InfoProvider.
After implementation of the SAP note #2253065, the RSDSO_REMOVE_REQS_PC program is available in your BW on HANA system. This program internally calls Function Module M, RSDSO_REMOVE_REQUESTS_API to delete change log requests in batch.
DSO ACTIVATION ON STANDARD DSO
You have performed loads to your DSO. For each load, you will find the following two request IDs:
● Load request (created at the time of loading)
● Activation request (created at the time of activation)
If you have more than one DTP load request that is yet to activate, and you have decided to activate only one request, then this request ID will help to selectively process the records from the new table to active and change log table.
DSO activation is like your DTP load processing, where the new table acts as a source and your active table and change log table act as targets. When you select the get delta request by request in DTP settings, the delta requests from the source are processed one after another and it will create separate request IDs for each run.
There are basic SQL operations that are logically performed at the back end while activating the ODS:
Rollback takes place when you delete an activate request.
The following list looks at each operation in detail and how it is associated with the record modes:
● On Active table, SQL operations such as Insert, Update, Delete and Select are performed.
● On Change log table, only Insert operation are performed.
● On New table, SQL operations such as Insert, Select, and Truncate are performed.
Note: Activation of DSO always refers (queries) to the Active table because the change log is a temporary storage area used for delta mechanism.
Some cases, like selective deletion, only perform on an Active table. The data remains in change log but if you load the same data again it creates a new record with the record mode N, and it does not update the old record already present in the change log table.
This indicates that the DSO activation refers to Active table only.