Oracle Apps Guide Logo
Define Fiscal Year Calendar in Oracle Apps

Define a New Fiscal Year or Month in Oracle Apps R12

A step-by-step guide to updating your accounting calendar in General Ledger.

Back to Learning Center

Article Overview

Properly defining your accounting calendar is a critical task in Oracle General Ledger. This guide provides a clear, step-by-step process for adding new periods to your calendar, which is essential for opening a new fiscal year or creating adjustment periods for year-end entries.

Step-by-Step Guide

Step 1: Navigate to the Accounting Calendar Setup

Log in to Oracle with the General Ledger Super User responsibility. Navigate to the Accounting Calendar form.

Oracle navigation menu for Accounting Calendar

Step 2: Query the Existing Calendar

Once in the 'Accounting Calendar' form, place your cursor in the 'Calendar' field, query for your existing calendar (e.g., 'Accounting'), and execute the query.

Accounting Calendar form with queried data

Step 3: Add a New Period

Scroll to the last row and a new blank line will appear. Here you can define your new period. This is where you would add a new month for the next fiscal year or an adjustment period.

Adding a new line for a new period in the calendar

Step 4: Fill in Period Details and Save

Fill in all the required fields for the new period, such as Prefix, Type, Year, Period Number, From/To dates, and Name. If it is an adjustment period, check the 'Adjusting' checkbox. Once complete, save your work.

Saving the newly added calendar period

Validation Query

After adding new periods, you can use the following SQL query to check the status of periods across GL, PO, and AP modules. You will need to provide a `set_of_books_id` when prompted.

SQL Query
select a.period_name,
       a.period_num,
       a.gl_status,
       b.po_status,
       c.ap_status
from
   (select period_name, period_num, 
    decode(closing_status,'O','Open',
                          'C','Closed',
                          'F','Future',
                          'N','Never',
           closing_status) gl_status
    from gl_period_statuses
    where application_id = 101
    and start_date >= '01-JAN-98' -- Modify date range as needed
    and end_date < '01-JAN-99'   -- Modify date range as needed
    and set_of_books_id = &&set_of_books_id) a,
   (select period_name, 
    decode(closing_status,'O','Open',
                          'C','Closed',
                          'F','Future',
                          'N','Never',
           closing_status) po_status
    from gl_period_statuses
    where application_id = 201
    and start_date >= '01-JAN-15' -- Modify date range as needed
    and end_date < '01-JAN-16'   -- Modify date range as needed
    and set_of_books_id = &&set_of_books_id) b,
   (select period_name,
    decode(closing_status,'O','Open',
                          'C','Closed',
                          'F','Future',
                          'N','Never',
           closing_status) ap_status
    from gl_period_statuses
    where application_id = 200
    and start_date >= '01-JAN-15' -- Modify date range as needed
    and end_date < '01-JAN-16'   -- Modify date range as needed
    and set_of_books_id = &&set_of_books_id) c
where a.period_name = b.period_name
and   a.period_name = c.period_name
order by a.period_num