This content has been marked as final. Show 6 replies
Thanks for your reply, but those links do not have any information regarding the gl_transfer_run_id.
looks like the GL_TRANSFER_RUN_ID column is not available in Release 12 under XLA_AE_HEADERS or any other XLA tables, however if you check the XLA_AE_HEADERS table, there is anew column available that was not present in 11i ....which is ACCOUNTING_BATCH_ID.
I am not sure whether this replaces the GL_TRANSFER_RUN_ID or it is a different reference ...
The architecture had a change in Release 12, hence the way the journal entries are transferred are different as well ...which might have caused this backend change ...
(Note: I cannot find any oracle reference to claim that GL_TRANSFER_RUN_ID is Obsolete ... you can raise an SR with oracle and get that confirmation ...)
xla_ae_headers.accounting_batch_id is for create accounting.
Consider xla_ae_headers.group_id for GL Transfer. Other columns to consider for GL Transfer are gl_transfer_status_code and gl_transfer_date
In Summary: to track the GL transfer status of accounting entries in R12, the following should work:
GROUP_ID for current data (that is UPG_BATCH_ID is null) in table XLA_AE_HEADERS
For upgraded data, GL_TRANSFER_RUN_ID will still be present in table AP_AE_HEADERS_ALL or table XLA_GL_TRANSFER_BATCHES_ALL
But upg_batch_id is NULL or -9999 (coz UNDO accounting) is R12 data. If any other then migrated.
Also at present there are GL interface tables (XLA_GL_<group_id>) are present.
Not sure when Oracle will stop to retain them.
These have been added for debugging purpose.
To drop them you need to run "Purge Temporary Journal Import Interface Tables Created by Subledger Accounting"