Topics:
· Accounting Balance Ingestion
To add a Subledger, do as follows:
1. Click Add to create a new Subledger. A New Page is displayed.
2. In Details,
a. Enter the following details fields:
o Specify a unique Subledger Application Name
o Describe the Subledger Application
o Specify a unique code for Subledger Application
o Specify the Ledger Name
b. Select the Event Class, either Transaction or Passthrough.
c. Select the Products and click Next.
Based on the selected Event Class, the Product list is updated.
The "Save Successful" Confirmation Message is displayed. The SLA details are successfully saved.
The status of the Subledger is changed to Draft and Created By details are added.
3. In Event Types,
a. From the list of event types available in the application, select the required event type.
b. Click Add Event Type to add a new event type if not available.
A New window is displayed.
c. Enter the following details:
o Name
o Code
o Description
d. Select the Event Class. Either Passthrough or Transaction.
e. Click Save.
A new event type is added to the list of Event Types.
f. Search for an Event Type in the Search Field Box.
g. Click Next.
4. In Attributes,
a. From the list of attributes available in the application, select the required attribute.
b. Click Add Attribute to add a new attribute if not available.
A New window is displayed.
c. Enter the following details:
o Name
o Physical Name
o Domain
d. Select the Attribute Type. Either Header or Line.
e. Select the Event Class. Either Passthrough or Transaction.
f. Click Save.
A new attribute is added to the list of Attributes.
g. Search for an Attribute in the Search Field Box.
h. Click Next.
NOTE:
Before proceeding with Header Mapping, you must register the SLA.
For more information, see the Registering Accounting Content with your ERP Service Section.
5. In Header Mapping,
a. Select the required Data Mapping from the Left Menu.
b. Enter the Header Data Mapping Name in Specify the Header Data Mapping Name Field. This is auto-populated field. You can change as required
c. Define the mapping from list of Subledger Attributes and Account Attributes using the corresponding check-box. Only selected Subledger attribute will be used.
d. Click Next.
NOTE:
Here, you can see the list of Product tables and respective columns. You must ensure that the data selected in the Product and Transaction Tables is available in the Staging Tables too.
6. In Line Mapping,
a. Select the required Data Mapping from the Left Menu. Here, you can see the list of Transaction Tables and respective columns. You must ensure that the data selected in the Product and Transaction Tables is available in the Staging Tables too.
b. Specify the header data mapping name in Specify the line data mapping name Field. This is auto-populated field. You can change as required.
c. Define the mapping from list of Subledger Attributes and Account Attributes using the corresponding check-box. Only selected Subledger attribute will be used.
7. Click Yes to configure or click No to retain the existing mapping when the "Do you want to proceed with Header and Line Mapping changes?" confirmation message is displayed.
For more information, see the SLA Configuration Section.
8. Click Next.
In Review, you can view the details of the SLAs. In the Review Tab, the details of the connectors defined for the SLA (current SLA) can be viewed.
9. Click Publish.
The SLAs which have connectors are auto-generated. You cannot modify the Seeded Connector.
10. Click Yes to continue when the "Do you want to Proceed? Subledger application will not be available for any modification and will be locked for execution." confirmation message is displayed.
A pipeline is automatically created for the SLA in Process Management. Execute the Pipeline using the As of Date parameter.
For more details, see the Executing the SLA Pipelines Section.
11. Click Yes to continue.
The "Publish Successful" Confirmation Message is displayed after the SLA is published. The status changes to Available.
12. Click the SLA to view the Connector Page.
For more details, see the Creating Connectors Section.
The AFCS has a predefined process to extract the General Ledger Balance from your ERP Financials Cloud Service and ingest it into AFCS. This is achieved by executing the GL Balances Process.
Before executing the GL Balances Process, perform the following to ensure that the files are available on the ERP Financial Cloud Service:
1. Define an extract job in the BI Cloud Console for the following BIV objects:
§ FscmTopModelAM.FinGlAccountsCodeComboAM.CodeCombinationPVO
§ FscmTopModelAM.FinGlInquiryBalancesAM.BalancePVO
The extract path must be chosen as Universal Content Manager (UCM) for the BI Cloud Console Extract and the specified columns must be selected in a specified order according to the above-listed sheets.
2. Schedule an extract job for the BIVs created in the previous step.
3. After the files are extracted, download a sample extract file for all the BIV Object extracts and check for column orders.
If the column order is not matching, then update the column order in the EDDs as per the respective extracted data files.
The GL Balances Process consists of components that perform the following tasks.
1. General Ledger Balance Extraction - Downloads extracted data files from the ERP Financial Cloud Service.
2. Balance Ingestion - Loads data from the downloaded files to AFCS.
To execute the GL Balances Process, follow these steps:
1. To execute, navigate to Process Modeller UI using Process Orchestration Option.
2. Search for GL Balances Process and execute using the As of Date Parameter.
For more details on how to view the execution status in the Process Monitor Window, see the Managing Processes Section.