Processing Oracle General Ledger Adjustment Periods

You can include adjustment periods from an Oracle General Ledger source system in the Oracle ERP Cloud when loading balances to an Oracle Enterprise Performance Management Cloud application.

You can include adjustment periods from an Oracle General Ledger source system in the Oracle ERP Cloud when loading balances to an EPM Cloud application.

Adjustment periods are additional periods that are related to regular periods from the source. An "adjustment period" refers to any accounting period set up to adjust balances prior to the closing period of the year. These periods are adjusted to "per12" and consequently are referred to as "per13". Typically, dates within the adjustment period overlap regular accounting periods. A customer might use a "Year Open Period" that refers to the first period in the accounting calendar to adjust last year’s balance carried forward amount. Additionally, the customer can set up the last period of the accounting calendar as the "Year Close Period" to adjust transactions made in the current accounting calendar.

In Data Management, adjustments are processed in Period Mappings where you indicate how the adjustment period maps to the period in the target application. The method for how adjustments gets processed is specified in the data load rule. This feature enables you to map Oracle General Ledger source periods in Data Management simply by pointing to the calendar and periods from the Oracle General Ledger application to the period in the EPM application.

When setting up the data load rule, you can either load to regular and adjustment periods when an adjustment period mapping exist or load an adjustment period only when an adjustment period mapping exists.

For example, when you map period 13 to December/Period 12, and select the Include Adjustment Period option, then the following occurs:

• For YTD balances, period 13 becomes the ending balance.
• For PTD balances, period 13 and December/Period12, are added.

To include adjustment periods from an Oracle General Ledger source system:

1. On the Setup tab, under Integration Setup, select Period Mapping.

2. Select the Source Mapping tab.

3. From Source System, select the Oracle General Ledger source system.

4. From Target Application, select the EPM Cloud application to which the adjustment applies.

5. From Mapping Type, select Adjustment.

6. Click Add.

7. In Source Period Key, specify the last day of the month to be mapped from the Oracle General Ledger source system.

   Use the date format based on the locale settings for your locale. For example, in the United States, enter the date using the MM/DD/YY format.

   You can also click and browse to and select the source period key.

   When you select the Source Period Key, Data Management populates the Source Period and Source Period Year fields automatically.

8. In Adjustment period, specify the name of the adjustment period from the Oracle General Ledger source.

   For example, if the adjustment period from the Oracle General Ledger is Adj-Dec-16, then enter: Adj-Dec-16 in this field.

9. In Target Period Key, specify the last day of the month to be mapped from the target system.

   Use the date format based on the locale settings for your locale. For example, in the United States, enter the date using the MM/DD/YY format.

   You can also click and browse to and select the target period key.

   When you select the Target Period Key, Data Management populates the Target Period Name, Target Period Month, and Target Period Year fields automatically.

   

10. Click Save.

11. On the Workflow tab, under Data Load, select Data Load Rule.

12. From the POV Bar, select the location to use for the data load rule.

    Data load rules are processed within the context of a point of view. The default point of view is selected automatically. The information for the point of view is shown in the POV bar at the bottom of the screen.

13. Click Add.

14. In Name, enter the name of the data load rule.

15. In Category, specify the default category value.

    The categories listed are those that you created in the Data Management setup.

    See Defining Category Mappings.

16. In Period Mapping Type, select the period mapping type for each data rule.

    Valid options:

    • Default—The Data Rule uses the Period Key and Prior Period Key defined in Data Management to determine the source General Ledger periods mapped to each Data Management period included in a Data Rule execution.

    • Explicit—The Data Rule uses the Explicit period mappings defined in Data Management to determine the source General Ledger periods mapped to each Data Management period included in a data load rule execution. Explicit period mappings enable support of additional Oracle General Ledger data sources where periods are not defined by start and end dates.

17. From Include Adjustment Period, select one of the following options for processing adjustment periods:

    • No—Adjustment periods are not processed. The system processes only regular period mappings (as setup for "default" and "explicit" mappings). No is the default option for processing adjustments.

    • Yes—If Yes is selected, then the regular period and adjustment period are included. If the adjustment period does not exist, then only the regular period is processed.

    • Yes (Adjustment Only)—If Yes (Adjustment Only) is selected, the system processes the adjustment period only. However, if the adjustment period does not exist, the system pulls the regular period instead.

      

18. Click Save.

Note: