My Oracle Support Banner

Encumbrance Journal Posting Fails With Error Invalid or Inactive Reserve for Encumbrance (Doc ID 1167791.1)

Last updated on MARCH 31, 2021

Applies to:

Oracle Public Sector Financials - Version and later
Information in this document applies to any platform.


Encumbrance accounting is given error Error15 Invalid or inactive reserve for encumbrance

Encumbrance Journal posting fails with “Invalid or inactive reserve for encumbrance“
The Reserve for Encumbrance Account is defined with the value '02' in the Intercompany segment.

When Posting tries to insert the Reserve for Encumbrance line, for a journal with bsv 01, the Error occurs.
Security rules are assigned that restrict access to only the value 01 for both the balancing segment and intercompany segment.
Apparently only the balancing segment is substituted for this account, leaving 02 in the Intercompany segment, which is not allowed per the security rule.

GLPPOS module: Posting
SHRD0056: Error detected in glpisl(). You have not defined any suspense account for set of books id: 1001
SHRD0008: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Warning ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PPOS0234: Posting failed to create or retrieve your reserve for encumbrance account
PPOS0237: Please check your Flexfield cross-validation rules
SHRD0173: Accounting Flexfield: 00.02.000.XXXXXXXXXX.000.XXXXXXX.0000.01.000000.000000.000000
SHRD0031: Batch Name: XXXX Payables XXXXXXX: E 128781
SHRD0034: Header Name: XXXXXXX BRL 1062
SHRD0033: Error Status: H
SHRD0174: Source Name: Payables
SHRD0175: Category Name: Purchase Invoices


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.