Setting Up Profile Options for Budgetary Control and Integration in Oracle Projects

1. PA: Enable Budget Integration and Budgetary Control Feature

Internal name: PA_BC_ENABLED
This profile option controls whether the budgetary controls windows and processes are
displayed and run. This profile is optional and the default value is "No".

The possible values are:

• Yes - The budgetary control windows and processes are displayed.
• No  - The budgetary control windows and processes are not displayed.

Important: You must set this value to "Yes" to enable Oracle Projects budgetary controls and budget integration features.

This profile option can be set by the system administrator at the site level only.

2. PA: Days to Maintain BC Packets

Internal name: PA_MAINTAIN_FC_PACKETS

This profile option specifies the number of days that the system maintains the results of transaction funds checks.

This profile option is optional and the default value is 3.

It applies to both integrated and non-integrated budgets which use budgetary controls. 

You can use the Funds Check Results window to view funds check results for transactions that are not older than the number of days that you specify for profile option. However, the funds check results for transactions that pass funds check are available for online viewing in the Funds Check Results window until the number of days is exceeded and either of the following events occurs:

• You run the concurrent program PRC: Maintain Budgetary Control Balances.
• You create a baseline version for any project with budget integration.

You can view summarized funds check results using the Budget Funds Check Results window.

Important: Because it results in additional data being stored, increasing this value may slow the performance of the funds check process.

This profile option can be set by the site administrator at the site level only.

3. PA: Allow Override of Budget Accounts

Internal name: PA_OVERRIDE_BUDGET_ACCOUNT
This profile option enables you to control whether accounts generated by the Project Budget Account workflow process can be manually overridden by users.
This profile option is optional, and the default value is "No".  It is only applicable for integrated budgets which require mapping project budget amounts to a GL budget account.  It is not require for non-integrated budgets.
The possible values are:

• Yes - Users can manually override accounts.
• No - Users cannot override accounts.

When enabled, you should not update the account for a budget line if the budget line is associated with transactions. Updating the account on such lines will cause the baseline process to fail.

Important: If you update account derivation rules for budgets in Oracle Subledger Accounting, then you must carefully consider the affect of the updates on existing integrated budgets. The baseline process fails if a revised account derivation rule overwrites accounts for budget lines that are associated with transactions.

This profile option can be set by the system administrator at the site level only.

4. PSA: Budgetary Control Report Template

Internal name: PSA_BC_REPORT_TEMPLATE

Use this profile option to enable users to view funds check results from Oracle Purchasing and Oracle Payables after a funds check.

You should select "Budgetary Control Results Template" as the value for this profile option to enable users to view standard funds check results from Oracle Purchasing and Oracle Payables after a funds check.

This profile option can be set by the system administrator at the site, application, responsibility, and user levels. Users may also update the user level setting.

5. GL Ledger Name

Internal name: GL_SET_OF_BKS_NAME
Use this profile option to specify your ledger.  The ledger you use should be enabled for budgetary controls and the subledger accounting method assigned to your ledger should be enabled for encumbrance accounting (See Note 1314706.1)
This profile can be set by the system administrator at the responsibility, application and site levels.