10.2 Adding a Subledger Application

This section describes how to add a Subledger Application (SLA).

To add an SLA, complete the following steps:

  1. Click Add.
  2. Provide the following Details information:
    • Specify a unique Subledger Application Name.
    • Describe the Subledger Application.
    • Specify a unique code for Subledger Application.
    • Select the Event Class as Transaction or Passthrough. Based on the selected Event Class, the Products or Entity list is updated.
    • Select the Products or Entity
    • The Publish Future Dated Events option specifies if future-dated journals (where header event date corresponding to accounting date in FAH/GL is greater than as-of date) will be published or not. By default, this option is enabled. If this option is disabled, AFCS will only publish non-future-dated journals from what has been sourced.

      Note:

      It is recommended to not modify this option after it is set. If there is a business-case to change this, raise a service request on My Oracle Support.
    • By default Yes is selected to group the events. Select No to post the line records as is without journal grouping.
    • Click Next.

      Acknowledge the confirmation message. The SLA details are successfully saved.

      The status of the subledger changes to Draft and Created By details are added.

  3. Provide the following Event Types details:
    • From the list of event types available, select the required event type or use the search box to search for an event type.
    • Click Add Event Type to add your own event type and provide the following details.
      • Name
      • Code
      • Description
      • Event Class
    • Click Save. A new event type is added to the list of Event Types.
    • Click Next.

    Note:

    You can add or modify the Event Type for an SLA even after it is registered or in configured status. In case of modification or addition, the same has to be performed in the ERP as well.

    Note:

    If an Event Type is added or modified after SLA is registered/configured and if the same Event Type is not present in the ERP, SLA execution fails. To proceed further, you need to add or modify the same Event Type in the ERP and re-run the SLA.
  4. Provide the following Attributes details:
    1. From the list of attributes available in the application, select the required attribute use the search box to search for an attribute.
    2. Click Add Attribute to add your own attribute and provide the following details:
    3. Enter the following details:
      • Name
      • Physical Name
      • Domain
    4. Select the Attribute Type. You have Header and Line as options.
    5. Select the Event Class. You have Passthrough and Transaction as options.
    6. Click Save. A new attribute is added to the list of Attributes.
    7. 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. Provide the following Header Mapping details:
    1. Select the required Data Mapping from the left menu.
    2. Enter the Header Data Mapping Name in Specify the Header Data Mapping Name field. This is auto-populated. You can change it as required.
    3. Define the mapping from the list of subledger attributes and account attributes using the corresponding check boxes. Only selected subledger attributes will be used.
    4. From the Account Attributes drop down, search for the attribute that you wish to add or modify, the search result is displayed. Select the corresponding attribute either from the Header entity or from the Contracts entities list.

      Note:

      Points to consider during entity attribute selection:
      • AFCS will now permit explicit choice of whether header attributes are picked from header entity or contracts entities .
      • This only applies to attributes that are currently present as standard in the header entity.
      • This provision is not to afford users the option of leaving contract-grain attributes unchanged; it only seeks to remove the requirement to have such change registered in advance of SLA data publishing.
      • All other activities where contract information or any attribute at that grain is relevant, including Balance Reconciliation, will remain unchanged.
      • Wherever contract-grain attributes are required, they will continue to be read from contract entities.
    5. Click Next .

      Note:

      Here, you can see the list of product tables and the respective columns. Ensure that the data selected in the product and transaction tables is available in the staging tables too.
  6. Provide the following Line Mapping details:
    1. Select the required Data Mapping from the left menu. Here, you can see the list of transaction tables and the respective columns. Ensure that the data selected in the product and transaction tables is available in the staging tables too.
    2. Specify the header data mapping name in Specify the line data mapping name field. This is auto-populated. You can change it as required.
    3. Define the mapping from the list of subledger attributes and account attributes using the corresponding check boxes. Only selected subledger attributes will be used.
  7. Click Next.
    In Ledger Name Assignment, select the ledgers relevant to the Sub Ledger Application and the assignment attributes to perform ledger name assignment. Also, select the Default Ledger for the SLA. The ledger names are fetched from ERP. Each SLA can now have multiple ledger names configured based on the attributes.
    For more information, see theConfiguring a SLA section.
  8. Click Next.
    Under Review, you can view the details of the SLAs. The Review tab, also displays the details of the connectors defined for the current SLA.
  9. Click Publish.
    The SLAs which have connectors are auto generated. You cannot modify seeded connectors.
  10. Click Yes to acknowledge the conformation message.
    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.
    A confirmation message is displayed after the SLA is published. The status of the SLA changes to Available.
    To unpublish an SLA, see Unpublishing SLAs.
  12. Click the SLA; navigate to Product Information > Review to view the SLA connectors.
    For more details, see the Creating Connectors section.