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 JANUARY 02, 2018

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

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.

Error:
-------
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.

Journal shows:

Field Name: DOC_SEQ_DATE
Field Long Name: Document Sequence Date
Set: 5860
Msg: 66
Message Text: Document Sequence Number is required.

Steps to Replicate:
---------------------

  1. Change the Subsidiary Ownership in General Ledger > Consolidate Financial Data > Consolidation > Subsidiary Ownership and add a new Effective Dates row.
  2. Navigate to General Ledger > Consolidate Financial Data > Equitization > Equitization Groups and make sure 'Effective-Date Ownership Sets' is 'by Period End Date(s)'.
  3. Run the Equitization process (GLPQEQTZ). Message Log is showing: Journal Processing Error. One or more journals are not posted.
  4. Open one of the generated Equitization journals in General Ledger > Journals > Journal Entry > Create/Update Journal Entries > Errors tab

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