asaassa

Troubleshooting Fund Check/Budgetary Control

Guide -Part 1
Troubleshooting Details A) Common Setup

Profile Options
PA: Enable Budgetary Controls
PA: Allow Override of Budget Accounts
PA: Days to Maintain BC Packets
PSA: Budgetary Control Report Template (R12)

i)Bottom-Up Budgeting Setup/Processing Steps

Perform the following tasks to implement Bottom-Up Budgeting:

1. Define the Project Budget Account Workflow process
2. Define the Allow Override of Budget Accounts profile option
3. Define the Enable Budgetary Controls profile option
4. Define the GL budget
5. Define Integration for the Project Type/Project
6. Define the Project Budget
7. Generate accounting information for each budget line
8. Optionally, override the generated account for specific budget lines
9. Baseline the Project Budget
10. Run the Program: Create Journals process
11. Post the GL journal batches

ii)Bottom-Up Budgeting Integration Definition

Field Descriptions:

Allow Override at Project Level - Default or Dictate settings for projects using this project type.
Budget Type - Select from the defined project budget types. The list of values will not include project budget types
that have baselined budget versions.
Balance Type - For Bottom-Up Budgeting the Balance Type must be Budget.
Non-Project Budget - Select a defined General Ledger budget. The list of values will only include GL budgets with a
status of Open or Current.
Remaining Fields - All remaining fields should be null

iii)Bottom-Up Budgeting Troubleshooting Tips

1. Account Generation Fails

Verify the Budget Account Workflow definition.
Is Dynamic Insertion enabled in General Ledger.
2. Budget Baseline Process Fails
Will the resulting budget journals reduce GL available funds to less than zero.
Does the budget contain a new or changed budget amount for a closed GL Period.

j)Top-Down Budgeting Setup

Perform the following tasks to implement Top-Down Budgeting:

-Define the Project Budget Account Workflow process

-Define the Allow Override of Budget Accounts profile option
-Define the Enable Budgetary Controls profile option
-Define the PA: Days to Maintain BC Packets profile option
-Define the PA encumbrance type
-Define the GL/CC budget
-Setup encumbrance in GL, PO, AP
-Define Integration for the Project Type/Project
-Define the Project Budget
-Generate accounting information for each budget line
-Optionally, override generated accounts
-Baseline the Project Budget

jj)Top-Down Budgeting Restrictions

-Supported for Oracle General Ledger and Oracle Contract Commitment funding only
-The budget entry method must be time phased by GL Period.
-Project budget amounts in open GL Periods.
-A budget line must exist for each budget period
-Cross Charge transactions are not supported

jjj)Top-down Budgeting Troubleshooting Tips

1.Transaction Fails Funds Check

Does a Baselined Budget exist.
Do budget lines exist for all project levels that have a control level other than None.
Is the transaction amount greater than available funds.
Was the PRC: Update Project Summary Amounts After Resource List Change ran after a new resource member was
added.
2.Account Generation Fails
Verify the Budget Account Workflow definition.
Is Dynamic Insertion enabled in General Ledger.
3. Budget Baseline Process Fails
Will the resulting budget journals reduce GL available funds to less than zero.
Does the budget contain a new or changed budget amount for a closed GL Period.
Is the Budget amount greater than current actual plus commitment balances.

k)Non-Integrated Budgets Setup

-Enable BC in GL and encumbrance accounting in Oracle Payables or/and Oracle Purchasing

-Define the PA: Enable Budgetary Controls profile option
-Define the PA: Days to Maintain BC Packets profile option
-Enable Budgetary Controls for Project Type/Project
-Define Control Level Defaults and Time Intervals
-Create and Baseline a Cost Budget
-Update the Control Levels for your Baselined Budget
Resource List
Project/Task
Resource Groups/Resources

kk)Non-Integrated Budgets Troubleshooting Tips

1. Transaction Fails Funds Check

Baselined Budget must exist.
Budget Line must exist if control level is not None.
Available funds must exceed transaction amount.
PRC: Update Project Summary Amounts After Resource List Change must be ran when a new resource member is
added.
2. Budget Baseline Process Fails
Budget amount must be greater than current actual plus commitment balances.
3. The following processes fail to interface transactions:
Interface Usage and Miscellaneous Costs to GL
Interface Total Burdened Costs to GL

The Maintain Budgetary Control Balances process must be ran.

4. Data corruption in funds-related tables and cause failures during funds validation processing

Either BC in GL or encumbrance accounting in AP or PO have been changed ( disabled)

l)Troubleshooting Baseline/Transactions Failures

-Use the Transactions Funds Check Results form to review funds check failures
-Use the Transactions Funds Check Results form to review funds check failures that occur during transaction
processing.
-Review Funds Check Result Messages and identify the corrective action see Note 445119.1 and/or Oracle Project
Management User Guide pag 6-111
-Always check PA_BC_PACKETS table,where funds check errors are present

B)General Troubleshooting

1.See Note 296559.1 -Common Tracing Techniques within the Oracle

2. Note 301372.1 - How to Generate a Raw Trace File Including Binds and Waits for a Concurrent Program for
11.5.10

3. To debug workflow issues verify/check

-Note 224308.1 -Account Generator & Workflow Frequently Asked Questions
-Note.116375.1-Workflow How to Get Information Required to Run wfstatus/wfstat.sql
-Note 187071.1- bde_wf_item.sql - Runtime Data of a Single Workflow Item

C)Troubleshooting Budget Workflow

1.PABDACWF ORA-20002: 3136: Item 'PABDACWF/#SYNCH' Cannot be Accessed

See Note 744359.1 for solution
2. ORA-20002: 3135: 'Wf_Engine.Notification' is not permitted in synchronous processes
See Note 334232.1 for solution
3. Unable to baseline a budget through workflow budget remains in 'In progress" status
See Note 552483.1 for solution

4. Modifying Existing Budget Gets Rejected in Workflow With ORA-1422

See Note 396515.1 for solution
5. PAWFBUI - PAXBUEBU: Error ORA-6502 In Workflow When Budget Is Baselined
See Note 336055.1 for solution
6. Workflow background process for PAWFBUI has performance issues
Apply Bi -monthly rollup Patch 7364558 or consolidated
Patch 7584055 This patch fixes critical fund check issues

D)Troubleshooting Budget/Fund check

1.For code issues/fixes see Note 745300.1 -Fund Check and Budgetary Control Troubleshooting Guide part 2
2.Check latest fund check consolidated Patch 7584055 applicable on top of 11i.PJ_PF.M
3.For Budget/Fund check datafixes see unpublished Note 820963.1-Troubleshooting Guide for Funds
Check/Budgetary Controls Data Issues
4. Note.732309.1-R12.0.6+ Oracle Projects Funds Check Data Collection Transaction Data Test:
5. Note.423519.1-11i Oracle Project Costing Funds Check Data Collection Data Collection Test: