EGL: After Performing Open Period Mass Update To Migrate to Subsystem, Opening Calendar for Subsystem Calendar (i.e. AP) Shows Incorrect Calendar ID. (Doc ID 2992794.1)

Last updated on DECEMBER 13, 2023

Applies to:

Symptoms

User creates a new Calendar ID that goes from January to December year and generate for two (2) years.
New Ledgers are also created and are linked to a new Ledger Group, which to linked to an existing Business Unit in Ledgers for a Unit.
Open Periods Mass Update page for GL is run and to migrate to subsystem modules. 
After this, it has been noted that open period for GL shows the correct Calendar ID, but not for subsystem i.e. AP.

Steps to replicate:

1.  Create a new Calendar ID going from July to June fiscal year, and build for 2 years.
       Calendar ID = 1A
        Years built = 2023 and 2024

2.  Create a new Ledger.  Ledger LOC2.

3.  Create a new Ledger Group (LOC2) and link Ledger LOC2.

4.  In Ledgers for a Unit, link Ledger Group LOC2 to Business Unit US003, with Journal Generator Default option selected.

5.  Using Open Period Mass Update page, for new Calendar 1A, Unit US003 and Ledger Group LOC2, apply and migrate to AP subsystem.

6.  Test:
      - Open Period Mass Update for Product AP does not display any rows.
      - Open Period Update though displays the correct periods.

7.  Create and post a voucher.
     (Accounts Payables > Vouchers > Add/Update > Regular Entry)

8.  Generate Journal from the voucher.

9.  Check Voucher Accounting Entries, note Journal ID assigned for the voucher accrual.
     (Accounts Payable > Review Accounts Payable Info > Vouchers > AP Accounting Entries)

10.  Open journal in GL Create/Update Journal Entries page.  
         Journal Date = 2023-11-02
         Fiscal Year = 2024
         Period = 5
     (General Ledger > Journal > Journal Entries > Create/Update Journal Entries)

NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample (based up made up data used in the Product name test environment).
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.