R12.2 Encumbrance Budget Should Not Baselined Successfully With Task Having End dated Code Combination. (Doc ID 2031971.1)

Last updated on JULY 27, 2015

Applies to:

Oracle Project Management - Version 12.2.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Budgeting & Forecasting

Encumbrance Budget is baselined successfully with Task having enddated code combination.

The Funds check message in Budgets : “The subledger accounting validation failed. The cause can be an invalid code combination ID or some invalid data that prevented the system from creating an accounting journal for the event. Please contact your System Administrator to review the debug log.”

The budget is baselined and status is working.  The PRC: Transfer Journal Entries to GL does not transfer journals to GL on the end dated combination.
Invoice is matched against the project & task having active code combination, the validation process puts on Encumbrance Accgt Fail.

The End dates are removed from the code combination, the Budget is deleted and copied from the previous version and it baselines successfully.
The budget status is working.
The invoice is validated.

In another case,
The end dates are removed from the code combination, the budget is deleted and copied from previous version and it does not baselines.
The Funds check message in Budgets : “The subledger accounting validation failed. The cause can be an invalid code combination ID or some invalid data that prevented the system from creating an accounting journal for the event. Please contact your System Administrator to review the debug log.”
The budget status is rejected.

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