13.1 Creating an SLA in the New User Interface

To create an SLA, follow these steps:
  1. Login to the AFCS application.
  2. On the Home page, click SLA Configuration link. The SLA Summary page is displayed.
  3. Click Create SLA button and the Set Up New SLA page is displayed.
  4. From the Set Up New SLA page, click Create SLA and Define Product Information page is displayed.
  5. Provide the following Details information:
    • Specify a unique Subledger Application Name.
    • 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.

      Note:

      Users must mark the Journal intent data in the Stage Accounting Entries as P for the SLA process to be executed.
    • Select the Product 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 Save to save the Product information.
    • Click Continue.

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

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

  6. 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 Save and Add another Event Type to add another new event type.
    • Click Export icon to export the list of event types added in the SLA.
    • Click Continue.

    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.
  7. 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
      • Data Type
    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 Save and Add another Attribute to add another new attribute.
    8. Click Export icon to export the list of attributes added in the SLA.
    9. Click Submit.
  8. From the SLA Summary page, search and navigate to the updated SLA.
  9. On the Set up New SLA page, select Register SLA

    Note:

    Before proceeding with Header Mapping, you must register the SLA. For more information, see the Registering Accounting Content with your ERP Service section.
  10. Follow the steps mentioned on the Import ERP Data page, to register an SLA.
  11. Click Continue and the Map Header Data page is displayed.
  12. Provide the following Header Mapping details:
    1. From the Map Header Data page, click Map Column and the Map columns for Future Transactions - Header Mapping window is displayed.
    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.

      Note:

      You must use a Header ID which is unique only within a Business or an As-of-date for Subledger applications.
    5. Click Mark as Done.

      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. Click Continue and Map Line Data page is displayed.
  13. Provide the following Line Mapping details:
    1. From the Map Line Data page, click Map Column and the Map columns for Future Transactions - Line Mapping window is displayed.
    2. Select the required Data Mapping . 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.
    3. Specify the header data mapping name in Specify the line data mapping name field. This is auto-populated. You can change it as required.
    4. Define the mapping from the list of subledger attributes and account attributes using the corresponding check boxes. Only selected subledger attributes will be used.
  14. Click Continue.
    In Assign Ledger, 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.

    Note:

    Only the Text related header attributes are displayed for selection.

    Note:

    In case of multiple ledger assignment, users must configure multiple ledger only from the Ledger Configuration legacy User Interface.
    For more information, see theConfiguring a SLA section.
  15. Click Submit SLA Configuration and the status of SLA is displayed as Configured in the SLA Summary page.
  16. Click Publish.
    The SLAs which have connectors are auto generated. You cannot modify seeded connectors. A confirmation message is displayed after the SLA is published. The status of the SLA changes to Available.