The Planning Enabled ADSO Options
There are two types of DataStore Object (advanced) that can be used for entering plan values. In both cases, if manual entry of values is needed, the model property PlanningEnabled must be active.
ADSO with Direct Update and Planning Mode
Especially, for planning scenarios, an ADSO can be defined as a special type called Direct
Update. Instead of loading data via DTP, values are updated directly on the active data table
via manual input planning or planning functions.
Direct Update – Details
● The table contains the key that was chosen during creation.
● There is no change log and no activation queue.
● It cannot be used for transformation scenarios or upload scenarios.
● It is not a target for SAP BW loading processes.
● However, it can be exported to other InfoProviders.
● Reporting is possible.
ADSOs can be set to Direct Update so they can receive data from APIs. In addition, they can
also be turned on for planning. Planning data can include transaction data or commentary
(use to capture planning assumptions for example.) In such an ADSO, you need to define a
key. Records with the same key can be overwritten.
ADSO Planning on Cube Like
There is another option if you need to keep track of the changes for a while, or if you want to
switch between loading and planning: If you choose the settings Data Mart DataStore Object,
Planning-Enabled , the DataStore Object (advanced) for planning has two tables. The Inbound
table is uncompressed and stores each set of changes in an inbound request. Request IDs
close after data is written to the database. If you don’t need to identify certain requests,
activate them. Then all records with the same set of characteristic values are condensed into
one record which is stored in the Active Data table. This type of ADSO for planning can be
loaded or planned against. An open request is closed if the mode is switched.