Document Base Table (DBT)

Use

The document base table (DBT) is a repository for data received from external systems and required for document creation. This typically includes transaction data from POS systems, sales meter readings, and dip readings.

To improve performance and reduce data volume, data can be held in the DBT at an aggregated level. Subsequent processes, such as invoicing, settlement with clearing houses, and stock adjustment use the data held in the DBT.

This graphic is explained in the accompanying text.

Features

Aggregation of Source Data

The level of aggregation is determined by the fields that the DBT contains.

Example Example

The meter readings upload provides sales volume data as recorded on a specific day at a specific time. If the fields for meter reading, day, and time are contained in the DBT, no aggregation occurs. However, if the time field is not contained in the DBT, readings for the day are aggregated.

You can add extra fields to the DBT to include data from additional source table fields. This allows greater flexibility for subsequent processes.

End of the example.

In the pre-aggregation step, the system checks for additional aggregation parameters specified in the assigned aggregation schema .

This graphic is explained in the accompanying text.

For dealer-owned products (such as candies and newspapers), less information is needed than for fuels. Therefore, it is not necessary to create a new entry in the DBT when a price change is uploaded from the POS system. Instead, you can use a business add-in to specify that the average price of dealer-owned materials is used for subsequent processes.

It is also possible to manipulate the "pre-aggregated" data before it is passed to the DBT.

This graphic is explained in the accompanying text.

If a payment card transaction is uploaded and then a cancellation of this transaction is uploaded before a subsequent process uses the original data, a zero record would be saved to the DBT and made available to subsequent processes. To avoid the posting of zero values, for example within the partner invoicing process, you can define a method to delete entries with zero quantity and net value.

Completion Strategy

You can define a completion strategy to enable the deletion report to identify data that is no longer required for document creation.

Note Note

Once data held in the DBT has been used in a document, the Oil & Gas System creates a link between the document and the data source (that is, the relevant detailed transaction file, the meter reading history table, or the dip reading history table). The link is stored in a separate table, called the document transaction link table (DTLT).

End of the note.

Activities

In Customizing for the Industry Solution Oil & Gas (Downstream) , you:

Define subsequent processes by choosing SSR Document Base Table Define subsequent processes.
Define completion strategies and link these to subsequent processes by choosing SSR Document Base Table Completion Strategy Define completion strategy.
Assign completion strategies to processes by choosing SSR Document Base Table Completion strategy Assign completion strategy for .....(name of process) .
Define aggregation schemas by choosing SSR (Service Station Retailing) Document Base Table Aggregation Schema Define Aggregation Schema.
Assign aggregation schemas to completion strategies by choosing SSR (Service Station Retailing) Document Base Table Completion Strategy Define completion strategy .
Define additional aggregation parameters by choosing SSR (Service Station Retailing) Document Base Table Aggregation Schema Maintain Business Add-Ins for Aggregation Schema Definitions Business Add-In to Fill the Aggregation Variable Key.
Define the manipulation of aggregated data prior to saving to the DBT by choosing SSR ( Service Station Retailing) Document Base Table Aggregation Schema Maintain Business Add-Ins for Aggregation Schema Definitions Business Add-In to Manipulate Entries after Aggregation .

To remove processed data from the DBT, run report ROIR_DELETE_DBT. This deletes all data that is no longer required according to the completion strategy assigned to the process.