My Oracle Support Banner

R12: FINANCIAL PLAN RULES VIOLATED There is no budget year defined in General Ledger for this Projects budget line. You must define a budget year in General Ledger in order to successfully baseline the project budget (Doc ID 2662037.1)

Last updated on MAY 03, 2020

Applies to:

Oracle Project Costing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

1 Using top-down budget integration and control with Oracle Projects Costing integrating with General Ledger.

Budget approval and baseline is processed via Workflow.


2 When modify the  "Approved Cost Budgets" that  created in the previous  year, that the budgets fail to Baseline!

In the WF notification is :

'FINANCIAL PLAN RULES VIOLATED
There is no budget year defined in General Ledger for this Projects budget line. You must define a budget year in General Ledger in order to successfully baseline the project budget'

 

3 The profile option 'FV: Federal Enabled' is set to 'No' at Site

Oracle® Projects Fundamentals
 
Integrating with the Budget Execution Module of Oracle Federal Financials
When you create a baseline project budget, you can populate the budget execution interface table to integrate with the Budget Execution module of Oracle Federal Financials.
When the profile option FV: Federal Enabled is set to Yes, the Project Budget Workflow process calls the Federal Integration Client Extension. You can modify the default logic supplied with the client extension to populate the Budget Execution Interface table with the appropriate values. You can have approval workflow notification sent to your Budget Execution analyst.

The problem does not replicate with the projects created in this Financial Year.

 4  Another message received is: "Budget XXXXXXXXXXX is the current budget defined in GL but there is no budget defined for the year 20XX (current) in projects for the project YYYYY."




 

Situation has been initially detected in an instance with the following version

DB Version: 12.1.0.2.0
Release: 12.1.3
Patch Set: R12.PA.B.3

Latest Patchset/RUP: 22687240 (R12.PJ_PF.B.DELTA.7) Projects Upd Pack 7 for 12.1



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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