R12/XTR:: Journal Import From Treasury To GL Does Not Validate Combination Rules In Gl_interface, ETC

(Doc ID 1414926.1)

Last updated on FEBRUARY 01, 2017

Applies to:

Oracle Treasury - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.

Symptoms

Issue 1: You have JEA setup with many GL Account codes in Oracle Treasury. Oracle GL decides to End date one of the segment which is being used in the JEA setup.User is unaware of the Change, creates Journals and now ready to Transfer Journals to GL.Navigates to: Daily Journals, query Journals for the Company and then clicks: Transfer Journals, At this stage it errors as:
VALUE 2601425 IN SEGMENT NATURAL ACCOUNT HAS EXPIRED

ACTUAL BEHAVIOR
In the Transfer Journals to GL window after clicking on the Transfer to GL button the "Program - Revaluation/Accrual Related Journal Processing" creates the Treasury journals which are then imported to GL with the Journal Import process. The Journal Import process does not do any validations for the journals not meeting the Cross Validation Rules or Security Rules.

You have JEA setup with many GL Account codes in Oracle Treasury. Oracle GL decides to End date one of the segment which is being used in the JEA setup.User is unaware of the Change, creates Journals and now ready to Transfer Journals to GL.Navigates to: Daily Journals, query Journals for the Company and then clicks: Transfer Journals, At this stage it errors as:

VALUE 2601425 IN SEGMENT NATURAL ACCOUNT HAS EXPIRED

And for the line of Journal it opens up the GL SEGMENT sub form where he can change the Segment value to the correct value and saves it. However when he transfer the Journal to the GL, GL still has Journal with the :
SEGMENT NATURAL ACCOUNT HAS EXPIRED Value.
This creates many confusions. Issue therefore is:
1. If a Segment Natural Account Has Been Expired in GL then such Error should come at much early stage or at least at the stage of Generate Journal stage?
2. If we allow on Treasury form some change in the segment value then the same must be Carried forward to GL?
This needs to be suitably resolved.

EXPECTED BEHAVIOR
-----------------------
Expect the Journal Import process to do validation and show errors for journals not meeting the Cross Validation Rules or Security Rules.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In Treasury navigate to the Daily journals review journals created and note that some accounts are not meeting the Cross Validation Rules or Security Rules.
2. Navigate to Transfer Journals to GL window and click on Transfer to GL button the "Program - Revaluation/Accrual Related Journal Processing" creates the Treasury journals in the GL_INTERFACE table.
3. Go to GL responsibility and submit the Journal Import process for Treasury source and no validation error is listed.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot rely on the Journal Import process to validate accounts for Cross Validation Rules or Security Rules.

Issue 2: To view or change a journal:

Issue 3: Reallocating Suspense Journal Entries:

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms