EGL: Equitization Process Going to Error Due to Document Sequence Error in Journals When 'Effective-Date Ownership Sets' is Set to 'by Period End Date(s)' for Equitization Group and Document Sequencing is Enabled.
(Doc ID 1535560.1)
Last updated on FEBRUARY 08, 2019
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.1 version, Consolidation and Equitization
Equitization process (GLPQEQTZ) going to error (Journal Processing Error. One or more journals are not posted) due to document sequence error in journals.
Normally we run the process with effective date 'by Process Request As Of Date' but now due to Subsidiary Ownership change we change the option to 'by Period End Date(s)'.
After changing the option the process is going to error as stated above.
Document sequencing is enabled at Overall Installation Options and General Ledger Definition but still for some journals error 'Document Sequence Number is required' is coming.
Message Log shows:
Journal Processing Error.
One or more journals are not posted: <Journal ID> on <Journal Date> for <Business unit>
Equitization Processes ended. Requests Completed: 0 Successfully, 1 Errors.
Field Name: DOC_SEQ_DATE
Field Long Name: Document Sequence Date
Message Text: Document Sequence Number is required.
Steps to Replicate:
- Change the Subsidiary Ownership in General Ledger > Consolidate Financial Data > Consolidation > Subsidiary Ownership and add a new Effective Dates row.
- Navigate to General Ledger > Consolidate Financial Data > Equitization > Equitization Groups and make sure 'Effective-Date Ownership Sets' is 'by Period End Date(s)'.
- Run the Equitization process (GLPQEQTZ). Message Log is showing: Journal Processing Error. One or more journals are not posted.
- Open one of the generated Equitization journals in General Ledger > Journals > Journal Entry > Create/Update Journal Entries > Errors tab
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