Conversion of Historical Data for Reporting Currencies and Secondary Ledgers

Conversion of Historical Data for Reporting Currencies and Secondary Ledgers

When defining a new subledger reporting currency or secondary ledger for an active primary ledger, you can use the SLA Secondary/ALC Ledger Historic Upgrade program to initialize journals.

You can determine the period from which to create ledger balances by selecting the first period for conversion. The journals are created from the selected period onwards. The first period of historic conversion should be the earliest period for which you have open transactions.

When a subledger level secondary or reporting ledger is added to an existing primary ledger, the accounting in the secondary or reporting ledger fails in the following scenarios:

• When a final accounted transaction is reversed: A Payables invoice is created and final accounted in the primary ledger. Then, a new subledger level secondary or reporting ledger is added to this primary ledger. The same invoice is cancelled. When the Create Accounting program is run, accounting for the invoice cancellation fails for the secondary or reporting ledger, as the accounting program does not find the corresponding Invoice accounting entry to generate the transaction reversal entry (Invoice cancellation accounting) for the secondary or reporting ledger.
• When a Payment accounting entry needs to be created using business flows: A Payables invoice is created and final accounted in the primary ledger. Then, a new subledger level secondary or reporting ledger is added to this primary ledger. A payment is generated against the same invoice. When the Create Accounting program is run, accounting for this payment fails for the secondary or reporting ledger, as the accounting program cannot find the corresponding upstream entry (Invoice accounting) to generate the downstream entry (Payment accounting) for the secondary or reporting ledger.

A new subledger level secondary/reporting ledger should not be added to an existing primary ledger that already has final accounted subledger journal entries.

Running the SLA Secondary/ALC Ledger Historic Upgrade Program

Use this procedure to run the SLA Secondary/ALC Ledger Historic Upgrade program.

Prerequisites:

Create initial balances for new ledgers:

Note: The SLA Secondary/ALC Ledger Historic Upgrade program creates journals in Oracle Subledger Accounting. These journals are created with a posting status of Posted and are never actually posted to Oracle General Ledger. To maintain historic balances in Oracle General Ledger, you must initialize balances for the new reporting currency ledger or secondary ledger.

To create initial balances for a:

• Reporting Currency Ledger: Run the Reporting Currency: Create Opening Balance Journals in Reporting Currency program. For more information on running this program, see the Implementation Considerations, Oracle General Ledger User's Guide topic within theOracle General Ledger User's Guide.
• Secondary Ledger: Use the Consolidation Workbench to copy initial balances. For more information on using the Consolidation Workbench, refer to the Oracle Financials Implementation Guide.

Restrictions:

• The program cannot be used for a secondary ledger whose subledger accounting method is different from that of the primary ledger.
• The program should be run immediately after creation of the new secondary/reporting currency ledger so that no new transactions are made between the creation of the new secondary/reporting ledger and running of the historic upgrade program.
• All fully accounted transactions of the primary ledger must be transferred to Oracle General Ledger before running the program.

To run the SLA Secondary/ALC Ledger Historic Upgrade program:

1. Navigate to the Submit Request form.
2. Select SLA Secondary/ALC Ledger Historic Upgrade from the LOV in the Name field.
3. Enter the parameters as follows:
   
   1. Primary Ledger: Select the primary ledger.
   2. Reporting/Secondary Ledger: Select the reporting/secondary ledger.
   3. Upgrade Start Period: Select the first period from which you wish to run the historic upgrade.
   4. Secondary Conversion Option: Select the secondary conversion option to be used when running a historic upgrade for a secondary ledger. The options are Derive from Original Transaction Rate and Use Initialization Rate.
   5. Secondary Currency Conversion Type: Select the currency conversion type or rate type to be used when running a historic upgrade for a secondary ledger.
   6. Secondary Currency Conversion Date: Select the conversion date to be used when running a historic upgrade for a secondary ledger.
   7. Mode:
      
      • Final: Select this value after you run the program in the Validation mode.
        This mode creates the journal entries within Oracle Subledger Accounting.
      • Validation: Select this value to run the program in Validation mode.
        
        Important: It is recommended to first run the program in Validation mode so that the program runs the validations that must be checked before performing the historic upgrade. If validations fail, you can view them within the log file and take action. After the program runs successfully in the Validation mode, you can run it in Final mode.
        
      • Recovery: Select this value to purge results after a concurrent request is terminated while in Final mode.
        
        Important: If you terminate the program while it is running in Final mode, then you must first run the program in Recovery mode before running the program again in Final mode. Recovery mode purges any upgrade data that may have been created during the terminated concurrent request.
        
   
   Note: In the case of a reporting currency ledger, the conversion option, rate type, and rate date are picked up from the ledger relationships defined in the Accounting Setup Manager.
   

Running the Upgrade Historical Subledger Transaction Accounting Program on Demand

Oracle Subledger Accounting provides a concurrent program, Upgrade Historical Subledger Transaction Accounting, that allows the historical accounting data conversion to be done independently for each subledger.

You must run the concurrent program Upgrade Historical Subledger Transaction Accounting instead of using the On Demand Upgrade Patch.

To run the Upgrade Historical Subledger Transaction Accounting, enter the following parameters:

1. Select or enter the Application name. The list shows the application attached to the responsibility from where the concurrent program is submitted.
2. Enter the name of the Ledger. The list shows all Primary ledgers.
3. Enter the Start Period Name. The list shows all periods not yet upgraded and associated with the ledger selected in the above parameter.
4. Enter the Number of Workers. The value should be greater than 1. Otherwise, the application inputs the default value of 1.
5. Enter the Batch size. The default value is 1000.

** Copied from here under link

https://docs.oracle.com/cd/E18727_01/doc.121/e13628/T149412T521412.htm