Start date

Defines the start date of the period of validity of this aggregation definition.

Only records whose reference date falls between Start date and End date are considered active for aggregation.

If no reference date is used, these dates are typically left empty or ignored.

End date

Defines the end date of the period of validity of this aggregation definition.

Only records whose reference date falls between Start date and End date are considered active for aggregation.

If no reference date is used, these dates are typically left empty or ignored.

Code

Short, unique identifier for the aggregation definition. Used in configurations, filters and scheduling to select a specific definition.

Transferred to archive?

Indicates whether this aggregation definition has been archived.

When set to Yes, the record is treated as archived; depending on BO configuration, archived records may become read-only and can be excluded from regular usage.

System code

Internal primary key of the record. This is a technical identifier used by the system and integrations; it is unique per record and cannot be edited by end users.

Property set code

Identifies the property set (data partition) to which this aggregation definition belongs. This controls in which property set the definition is visible and which data it can access.

Business object type

Indicates the technical business object type for this record. This is mainly used by the framework to distinguish between system BOs and user-defined BOs or to interpret references in generic functionality.

Data aggregation parameters

Mandatory reference to the Aggregation Parameters BO containing two Comment fields used to store the container parameters and the report SX parameters.

In addition, the Aggregation Parameters BO has a required reference to the Aggregation Properties BO, which contains the SQL definition used for the aggregation.

Name

Descriptive name of the aggregation definition. Used in the UI to recognize and select the correct definition.

User-defined type

Indicates the user-defined subtype of this business object, if the BO supports user-defined types. It allows multiple functional variants of the same underlying BO definition to be distinguished and handled differently.

System status

Internal lifecycle status of the record, managed by the framework.

System status is used by generic logic (e.g. archiving, scheduling, DAM status changes) and is not intended to be changed directly by end users.

User-defined status

Functional status of the aggregation definition. This status is configured in Field definer and is typically used to trigger DAM processing (e.g. “DAM update” status), control scheduling, and indicate whether the definition is under construction, ready, or inactive.

Reference date

Date that is used as the reference point when evaluating time-aware data (such as Start date / End date validity). The reference date determines which time-sliced records are considered “current” for this aggregation.

Inserted by

User account that created the record. This field is filled automatically at insertion time and cannot be edited.

Modified by

User account that last modified the record. Updated automatically each time the record is saved.

Modification date-time

Date and time of the last modification of the record. Updated automatically whenever the record is changed.

Insertion date-time

Date and time when the record was created. This is a technical audit field, set automatically by the system.

Update count

Technical counter that is incremented on every update of the record.

Code

Unique identifier of the aggregation properties record.

This value is referenced by the DAM solution extensions via the parameter properties.bo.code. It replaces the file name / ID that was used when the configuration was stored in a properties file. Each set of DAM SQL definitions must have a distinct Code.

Description

Optional descriptive text for this aggregation properties record.

Used to clarify the purpose or scope of this specific configuration (for example, which report or benchmark entity it serves).

Comment

Free text field for consultant / implementer comments about this aggregation setup.

Can be used to record implementation notes, version info, or constraints that are not obvious from the SQL itself.

Properties

Full DAM configuration content for this record, in the same format as the original properties file.

This field contains:

Technically it is a large text field that mirrors the content of the original *.properties file; the DAM solution extensions read these key–value pairs at runtime to know how to aggregate and where to write the results.

Data aggregation properties

Select the Data aggregation properties record whose Code corresponds to the DAM configuration you want to use for this aggregation definition (for example the record used previously by aggregation.properties.bo.code=IPD in ReportSX / CalculateSX).

It is used to link the Aggregation definition to the Data aggregation properties BO record that contains the SQL configuration to fill data and details.

System status

Internal lifecycle status of the record, managed by the framework.

System status is used by generic logic (e.g. archiving, scheduling, DAM status changes) and is not intended to be changed directly by end users.

System code

Internal primary key of the record. This is a technical identifier used by the system and integrations; it is unique per record and cannot be edited by end users.

Property set code

Identifies the property set (data partition) to which this aggregation definition belongs. This controls in which property set the definition is visible and which data it can access.

Business object type

Indicates the technical business object type for this record. This is mainly used by the framework to distinguish between system BOs and user-defined BOs or to interpret references in generic functionality.

Code

Short, unique identifier for the aggregation definition. Used in configurations, filters and scheduling to select a specific definition.

ContainerSX

Stores the old ContainerSX parameters in text form.

Large text field (comment-style) that contains all configuration formerly provided via the ContainerSX parameter string or property file.

Typical content: key–value pairs controlling how the benchmark structure (definition/data levels) is created or updated when the BOM or SX logic runs.

Name

Descriptive name (up to 255 characters) summarizing the purpose or scope of this parameter set.

User-defined business object

Identifies the user-defined business object (UDBO), if any, to which the aggregation parameters are functionally tied.

User-defined status

Links these parameters to a specific user-defined status in the BO’s status model, typically the status that triggers aggregation.

ReportSX

Large text field (comment-style) that contains all the configuration formerly provided for ReportSX: the general keys (such as debug, execute.on.status.change) and, crucially, the keys that instruct DAM how to fill data and details levels using SQL statements (via the Data aggregation properties BO).

Inserted by

User account that created the record. This field is filled automatically at insertion time and cannot be edited.

Modified by

User account that last modified the record. Updated automatically each time the record is saved.

Modification date-time

Date and time of the last modification of the record. Updated automatically whenever the record is changed.

Insertion date-time

Date and time when the record was created. This is a technical audit field, set automatically by the system.

Update count

Technical counter that is incremented on every update of the record.