Friday, February 19, 2016

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

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 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 drilldown for these transactions.
3. Please use sweep datafix 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.

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('01.01.2016', ''),
     xah.period_name     = '???-16'  ----its JAN-16
where xah.application_id = 707
 and xah.event_type_code = 'RECEIVE'
 and xah.event_id in (300586735, 300586736, 300586739, 300586740)
 and xah.ledger_id = &ledger_id
 and xah.gl_transfer_status_code = 'N';
              I - Incomplete, N - No action, P - Processed, U – Unprocessed

              D - Draft, E - Error, I - Invalid, P - Processed, R - Related event in error, U - Unprocessed, F - Final

No comments: