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.
Transaction types are required to collect the transaction data and process it into accounting data necessary to form the Subledger information. Data from different Source Systems come together and are processed depending on these categories to form ledger information.
NOTE:
To use pre-packaged SLAs, you must standardize Transaction Types to those defined in the SLA before processing.
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 helps 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.
Grouping functionality includes the following components:
· Event Group Summary
· Defining an Event Group
· Managing Group Attributes
To understand the Subledger Event Grouping summary window, follow these steps:
1. From the Oracle Financial Services Data Foundation Integration with Accounting Hub Cloud Service window, select AHC Administration and then select Subledger Event Grouping.
The Subledger Event Grouping window is displayed with a list of pre-packaged event groups information for transmission to the Accounting Hub.
2. The Subledger Event Grouping window displays the Event Group Name, Header Connector, and Line Connectors.
a. Event Group Name: It is the generic name given to identify a Header and Line Connector mapping. The pre-packaged Subledger connectors and names are displayed.
b. Header Connector: Displays the Header Connector's name.
c. Line Connectors: Displays the Line Connector's name.
3. You can search for Subledger Event Grouping Name.
4. You can define an Event Group, Manage Group Attributes, and Delete user-defined group events.
5. Click Delete if you want to delete a Subledger Event Group.
It is not possible to delete a pre-packaged Subledger Event Group.
To define an event group, follow these steps:
1. From the Subledger Event Grouping window, click to define the event group. The Define Event Group window is displayed.
2. Enter the required details and click Save.
To manage group attributes, follow these steps:
From the Subledger Event Grouping window, click to manage group attributes. The Manage Group Attributes window is displayed with the Available Event Groups.