Requisition Approval Workflow Failing After Upgrade - 3103: Attribute 'DOCUMENT_ID' Does Not Exist (Doc ID 1111660.1)

Last updated on APRIL 08, 2025

Applies to:

Symptoms

Submitting a Requisition for Approval, the workflow failed at  Use Requisition Encumbrance checked.

Replication Steps:
1. Create the requisition and submit it for Approval
2. Note the workflow has gone into an Error State.

Error Message:
3103: Attribute 'DOCUMENT_ID' does not exist for item 'REQAPPRV/XXXXX-XXXXXX'.


Other: Requested that a requisition be created, and then the funds check conducted outside of the Approval process, using the Enter Requisitions form.

Following error was encountered:

"Your Budgetary Control action completed with exceptions."

Result Message: Procedure PSA_BC_XLA_PUB.Budgetary_Control returns an error without any details to the calling procedure PO_ENCUMBRANCE_POSTPROCESSING.execute_gl_call. Please contact your support representative.


FND: Debug Log Enabled was then set, and the error was replicated.

The following was seen in the FND_LOG_MESSAGES table.

Invalid AAD = XLA_00201_AAD_S_000006_PKG
xla_exceptions_pkg.application_exception: ValidateAAD
20-MAY-2010 17:08:12 - The application accounting definition Purchasing Encumbrance Application Accounting Definition owned by Oracle is not validated. Please validate the application accounting definition or update the application accounting definitions contained in the subledger accounting method XXX Encumbrance Accrual.
The application accounting definition Purchasing Encumbrance Application Accounting Definition owned by Oracle is not validated. Please validate the application accounting definition or update the application accounting definitions contained in the subledger accounting method XXX Encumbrance Accrual.

Changes

Upgrade to 12.1.2

Cause

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