GLLEZL Journal Import Creates AP journals For End Of Period Date And Not Transaction Date As Needed
Last updated on JULY 02, 2012
Applies to:Oracle General Ledger - Version 12.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Jul-2012***
EXECUTABLE:GLLEZL - Journal Import
Importing Date from Accounts Payable into Oracle General Ledger.
Data is created in Accounts Payable (Invoice) on a specific date. This is what is expected and needed to be the date of the records as they are brought into general ledger.
When looking at the data in the journal that is created, it is created with a journal effective date of the end of the period.
This is a new setup
Business Need is to have the journal effective date the same day as the data is created for in the sub-ledger due to currency conversion issues.
When viewing the data in the gl_interface table the date is also seen as the last day of the period... to see this the following was done:
To be able to stop the application from import - so we can view the data as it is placed in the gl_interface table. Please do the following.
1) Change the profile "Concurrent Hold Request" to Yes.
Responsibility = System Administrator
Navigation = Profile/System
Query on the profile option 'Concurrent Hold Requests'.Set it to Yes at the User level and Save
2) Create new invoice - submit the gl transfer process for it.
3) Go to View > Requests > Find
The Transfer Journal Entries to GL program should be on hold... Release the hold to allow it to process.
4) The Journal import program should show as ON HOLD after the transfer program submits it.. Do Not release the hold on this program at this time.
5) Provide sql output for the following query.. in a parsed excel file with column headers for readability.
The data in this case shows the accounting_date in the gl_interface as also being the last day of the period and not the needed actual transaction date. This data is being provided by the Sub Ledger Accounting (SLA) module to General Ledger with this date. This is a SLA setup issue for the specific subledger that is seeing this issue.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms