My Oracle Support Banner

Transfer Journal Entries To General Ledger Program For Purchasing Does Not Transfer Entries (Doc ID 1540190.1)

Last updated on MARCH 04, 2024

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

While attempting to run the 'Transfer Journal Entries to GL' from Purchasing Responsibility to transfer the PO encumbrance entry to GL,
the data does not get transferred to GL and GL_TRANSFER_STATUS_CODE = N.


Replication Steps:
The issue can be reproduced at will with the following steps:
1. Run the program Transfer Journal Entries to GL' from Purchasing Responsibility
2. The program doesn't pick the PO transaction which are having ACCOUNTING_ENTRY_STATUS_CODE=F

Other:

The entries for Encumbrance Obligations against purchase orders - it is not month end based transactions.

Turning on FND Logging and then running the transfer process showed the following:

______________________________________________________________________
l_dev_phase = COMPLETE
l_dev_status = WARNING
selecting from gl interface XLA_GLT_1734634
Data found  in Gl interface with Error Status and journal import request failed. Request Id = 35978567
BEGIN of procedure BUILD_MESSAGE
p_appli_s_name = XLA
p_msg_name = XLA_GLT_GLLEZL_FAILED
p_token_1 = REQUEST_ID
p_value_1 = 35978567
p_token_2 = LEDGER_NAME
p_value_2 = COSD
p_entity_id =
p_event_id =
p_ledger_id =
p_ae_header_id =
p_ae_line_num =
p_accounting_batch_id =
BEGIN of procedure STACK_ERROR
p_appli_s_name = XLA
p_msg_name = XLA_GLT_GLLEZL_FAILED
p_entity_id =
p_event_id =
p_ledger_id =
p_ae_header_id =
p_ae_line_num =
p_accounting_batch_id =
l_msg_number = 95293
END of procedure STACK_ERROR
END of procedure BUILD_MESSAGE
recover_batch.Begin
Found 1 batches to recover
Updating XLA_AE_HEADERS

_______________________________________________________________________

Also seen in the Journal Import Execution Report were the following entries:

Error Code                     Source        Date        Currency      Entered Debit     Entered Credit Accounting Flexfield/CCID
------------------------------ ------------- ----------- -------- ------------------ ------------------ ----------------------------
EF01, EF03                     Purchasing    19-MAR-13   USD                       0                  0 10100.46145.52396.xx
EF01, EF03                     Purchasing    19-MAR-13   USD                       0                  0 10100.46145.52396.xx
EF01, EF03                     Purchasing    19-MAR-13   USD                       0                  0 10100.46145.52396.xx
EF01, EF03                     Purchasing    19-MAR-13   USD                       0                  0 10100.46145.52396.xx
EF01, EF03                     Purchasing    19-MAR-13   USD                       0                  0 10100.46145.52396.xx

 

Flexfield Error Codes
---------------------
EF01    This Accounting Flexfield is inactive for this accounting date.
EF02    Detail posting not allowed for this Accounting Flexfield.
EF03    Disabled Accounting Flexfield.

From this, it can be seen that either account dates are not valid or code_combination_id is disabled.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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