10.1 Registration of SLAs with Accounting Hub Service

Topics:

• Registration of SLAs

Note:

Before registering the Account Content with ERP Service, you must configure details in Details, Event Types, and Attribute tabs. For more information, see the Adding a Subledger Application section.

Figure 10-1 Periodic Operational Activities

To register the SLAs with Accounting Hub Service, complete the following steps:

1. Once the necessary attributes are configured and saved, the SLA status changes to Ready for Registration.
2. From the Sub Ledger Application Summary window, select the required SLA to be registered and click theActions drop-down in the Product Information link and select Download Template. A file with the XLSM extension is downloaded to the client machine. This XLSM file maintains the template in XlaSourceSystemSetup.xlsm with Subledger Application details filled in.

   In the Instructions sheet, the details are explained. Note that the XLSM file must not be manually modified. The details are provided only to aid with the users' understanding of the content of the files and how it participates in the integration process.

   In the Source System sheet, the Name and Short Name given in the Sub Ledger Application window are displayed.

   Note:

   The Name or Short Name, which appears in the row, must have the event type name along with the Subledger Application Name following the EVENT_TYPE_NAME_SLA_NAME pattern, as shown in the preceding image. The Transaction Type name is appended with the SLA name to maintain the uniqueness of transaction types across all subledger applications. The Short Name is limited by AHCS specifications to 30 characters and those employed by FSDF integration for AHCS must consider this.

   In the Transaction Information sheet, those Transaction Type Names and Short Names against which Journal Display is set to Yes is displayed through the AHCS user interface.

   In the Line Information sheet, those Transaction Type Names, and Short Names against which Journal Display is set to Yes are displayed through the AHCS user interface.

   Note:

   The three mandatory columns are listed in a greyed area for both Transaction Information and Line Information.
3. Click Validate in the Source System tab of the XLSM file to check if there are any errors in the template. Note that this step must be performed manually.

   Note:

   The XLSM files must not be manually modified. If you want to make changes to the files, make the required changes using the SLA user interface and follow the steps to download the template again.
4. Click Generate ZIP, in the Source System tab of the XLSM file, to compress required content and prepare the ZIP file. Note that this step must be performed manually.
5. Upload the ZIP file thus generated to your instance of AHCS. See the AHCS User-Documentation for details on how to perform this.

   Note:

   In AHCS, map the Entered Amount and Entered Currency in the Manage Accounting Attributes window to Transaction Amount and Transaction Currency before proceeding with the configuration of accounting rules.
6. Once the generated ZIP file is uploaded to your instance of AHCS, download the data template generated by AHCS corresponding to the SLA registered through the Download Data Template Function in AHCS.

   See the Oracle Financials Documentation for details on how to perform this.

7. Click Register from the Actions list.
8. Drag the data template generated by AHCS File from your instance of AHCS into the window.

   Alternatively, you can click Browse and select the file.

   After successful completion, the SLA definition is registered.