Create Accounting - Cost Management with Error 95325 The GL Date DD-MON-YYYY is not in an Open or a Future Enterable Period. Please select a valid Period (Doc ID 1317253.1)
Symptoms
Cause
Solution
References
Oracle Cost Management - Version 12.0.0 and later
Oracle Order Management - Version 12.2.5 to 12.2.5 [Release 12.2]
Information in this document applies to any platform.
Cost Management - SLA
SLA - Subledger Accounting - Cost Management
Subledger Accounting Program Report
95325-The GL date is not in an open or a future enterable period. Please select a valid GL date or open the period.
Subledger Accounting
When attempting to run Create Accounting - Cost Management process, the following error occurs:
ERROR
-----------------------
Error Number/Error Message
95325 The GL date DD-MON-YYYY is not in an open or a future enterable period. Please select a valid GL date or open the period.
STEPS
1. Connect to Cost Management - SLA Responsibility.
2. Go to SLA
3. Run the Create Accounting - Cost Management process and review the Subledger Accounting Program Report, is possible to see transactions with the Error 95325.
Normally, this kind of issue is on the SLA transfer to GL and the reasons could be:
- Wrong or missing Account Segment setup to prevent GL transfer. Need to correct the setup.
- GL Period was Closed and customer failed to examine the Subledger Period Close Exceptions Report, Create Accounting-Cost management report output, and take corrective actions before closing the Period.
Whenever a GL period is closed, there will be SLA exception reports launched. Customer is expected to examine those reports and correct them before closing a GL period.
- Backdated transactions where the TRANSACTION_DATE does not equal CREATION_DATE
To implement the solution, please execute the following steps:
important Observations:
----------------------------
1. It is highly recommended to re-open GL Period to prevent Reconciliation issues with Inventory Period Close and Accrual Reconciliation.
2. Missing posting the Accounting in the correct Period are really not a Bug to Oracle. And their resolutions are purely Functional based on each customer expectation and local laws.
3. Deleting Journals will introduce a SERIOUS CORRUPTION: GL balances will not match the subledger data. Same is available for changing the period.
Deleting journals or changing the period is not permitted at all if the budgetary control is used. (not possible in GL)
4. As workaround customer can post and reverse these journals.
Reopen GL Period
---------
1. Go to General Ledger Responsibility
2. Setup > Open/Close
Option1
---------
1. Ensure to take a backup of the system before applying the recommended solution.
2. Run the following in a TEST environment first:
In order to remove the exceptions, re-open the GL Period WITHOUT changing the GL Balance.
3. Launch "Create Accounting - Cost Management" in Final mode WITHOUT posting to General Ledger.
Responsibility: Cost Management
Navigation Path: SLA > Submit New Request > Run Create Accounting Cost Management
- Ledger =
- Process Category =
- End Date =
- Mode = Final
- Errors only = No
- Report = Summary
- Transfer to General Ledger = Yes
- Post in General Ledger = No
- General Ledger Batch Name =
- Include User Transaction Identifiers =
4. Find the unposted GL batches using GL responsibility
Responsibility = General Ledger Super User GUI
GUI Navigation = Journals/Enter
GUI Form Name = GLXJEENT (Enter Journals)
1. Query the Batch by entering the name of the Batch in the Find Journals screen and click on the [Find] button.
2. The batch appears on the Enter Journals screen. You select the batch and click on the [Review Journal] button.
You place the cursor in a journal line field and you click on the red X icon and delete all the lines in the journal.
5. Close the GL Period again.
6. Note: Deleting the Journals is at customer Responsibility, if there is no need for the Journals to go to GL.
Option2
---------
1. Change the posting date in the GL Batch. In order to achieve the control on the GL batch.
Note: review Oracle General Ledger User Guide to unfreeze Subledger Sourcing, which is not allowed by General Ledger by default.
2. Confirm the data is corrected when viewed in the Oracle Applications.
3. If you are satisfied that the issue is resolved, migrate the solution as appropriate to other environments.
Option3
---------
Sweep transaction to an Open GL period
Note:
If reopening a closed periods not feasible, then review the following Action Plan:
1. Events created in closed GL period can be identified using below query:
SELECT xe.*
FROM xla_ae_headers xah,
xla_events xe,
xla_ae_lines xal,
xla_accounting_errors xae,
gl_code_combinations_kfv gcc
WHERe xae.application_id=707
AND xe.application_id=707
AND xal.application_id=707
AND xah.application_id=707
AND xae.ledger_id=&ledger_id
AND xae.ae_header_id=xah.ae_header_Id
AND xah.ae_header_Id=xal.ae_header_id
AND xae.event_id=xe.event_id
AND xe.event_id=xah.event_id
AND xah.GL_TRANSFER_STATUS_CODE='N'
AND xal.code_combination_id=gcc.code_combination_id
2. A Note of Caution : It is to be understood that sweeping of transactions with the above approach would not change the transaction date in Material/WIP subledgers and hence there could be discrepancy between these periods in the Materials Subledger Vs SLA/GL.
It could also impact drill down for these transactions.
3. Please use sweep datafix script "SWEEP_TRANSACTTIONS.txt" from Note 883557.1 for updating records whose xah.accounting_entry_status_code='F'.
Use the following for pending transactions have xah.accounting_entry_status_code='I'
4. The following is to transfer (Sweep) these pending to current period.
a. Take back up of the relevant events that are in error with message 95325
This will only fix events that have errored due to corresponding period being closed. Customer could choose to add other filtering criteria to narrow down further, if required.
CREATE TABLE XE_Sweep_bkup_orcl AS
SELECt xe.*
FROM xla_events xe, xla_accounting_errors xae
WHERe xe.application_id = 707
AND xae.application_id = 707
-- AND ENTITY_CODE =
AND xe.event_id = xae.event_id
AND xe.upg_batch_id IS NULL
AND xae.message_number = 95325
AND xae.ledger_id = &Ledger_id
AND xe.event_status_code = 'U'
AND xe.process_status_code = 'I'
b. Verify the events from the backup table to ensure they are the ones that would like to sweep.
c. Sweep them to next period by providing appropriate date in the next open period
Update xla_events
SET EVENT_DATE = '&New_date',
transaction_date = '&New_date',
REFERENCE_DATE_1 = '&New_date',
CREATED_BY = -11111
WHERe application_id = 707
AND Event_id IN (SELECT event_id FROM XE_Sweep_bkup_orcl);
d. Verify the Numbers of records updated.
e.
COMMIT;
f. Rerun Create Accounting - Cost Management and verify that these transactions get accounted successfully.
Note
-----
If the SLA events already in Final mode (accounting_entry_status_code='F').
Then also use the below data fix in xla_ae_headers table :
The following is an example:
update xla_ae_headers xah
set xah.accounting_date = to_date('&dd.mm.yyyy', 'dd.mm.yyyy'),
xah.period_name = '&period_name' ----enter period_name
where xah.application_id = 707
and xah.event_type_code = 'RECEIVE'
and xah.event_id in (&event_id, &event_id, &event_id, &event_id.....)
and xah.ledger_id = &ledger_id
and xah.gl_transfer_status_code = 'N';
-------------------------------------------------------------------------------------------------------------------------
EVENT_STATUS_CODE MEANINGS:
I - Incomplete, N - No action, P - Processed, U – Unprocessed
PROCESS_STATUS_CODE MEANINGS:
D - Draft, E - Error, I - Invalid, P - Processed, R - Related event in error, U - Unprocessed, F - Final
Option4
---------
Ignore / bypass OLD unprocessed SLA events transactions
Review (Doc ID 1985044.1) How to ignore / bypass old SLA events that need not be processed during execution of Create Accounting - Cost Management
