9.3 Event and Journal Grouping
Note:
This is the part of the SLA Header and Line Mapping sections.Event or Transaction types refer to accounting events that are captured when transactions are committed or processed. While creating a subledger, different transaction types are created so that all the transactions can be classified into one or the other event type and are used for creating journal lines. Examples of transaction types can be withdrawal, deposits, servicing, fees, charges, and so on.
Note:
To use pre-packaged SLAs, you must standardize transaction types to those defined in the SLA before processing.The Subledger Event Grouping functionality is introduced to the group data, based on a few seeded dimensions while extracting and then posting them to AHC. Grouping is based on dimensions and significance. Similarly, while loading the data from AHC to STG_GL_DATA, aggregation based on the dimensions and the basic primary key columns of the GL data table help in maintaining the uniqueness of the table without any errors.
Grouping functionality includes combining data based on some preseeded columns in both header and line-level data. When data is grouped on some dimensions and transaction numbers are not considered for grouping, there is a requirement to regenerate the transaction numbers. As aggregate columns are different in header and line level, aggregation happens separately for header and line data. However, the only connection between the line and header data is the transaction number. Therefore, to maintain the connection, pair up the corresponding header and line connectors along with a mapping table, which maintains actual transaction numbers with a map to newly generated or replaced transaction numbers.
- Event Group Summary
- Defining an Event Group
- Managing Group Attributes