Budgetary Control: Functional Overview

Metalink Note: 817974.1

Budgetary controls enable you to monitor and control expense commitment transactions entered for
a project, based on a project cost budget. Expense commitment transactions are transactions for
non-inventory items. Oracle Projects enforces budgetary controls for:
Project-related purcase re!uisitions and purcase orders entered in Oracle Purcasing
"ontingent #or$er purcase orders entered in Oracle Purcasing
%upplier invoices entered in Oracle Payables
Project-related prepayments not matced to a purcase order and te application of unmatced
prepayments to supplier invoices
Budgetary Controls or !"#ense $e#orts
Budgetary controls are enforced for supplier invoices entered in Oracle Payables. &o#ever, because
expense reports are generally entered after costs are already incurred' budgetary controls are not
enforced for project-related expense reports entered in Payables. (erefore, you sould ensure tat
your procedures for approving expense report expenditures include veri)cation of available funds
according to your business re!uirements.
Budgetary Control For %re#ay&ents
Oracle Projects enforces budgetary controls only for unmatced prepayments and for applications of
unmatced prepayments to supplier invoices.
Budgetary and 'ransaction (alidation
*ou can optionally de)ne budget accounts for project budget lines at a iger level tan transaction
accounts. *ou must ensure tat transaction accounts roll up to budget accounts #itin te budget
account ierarcy in Oracle +eneral ,edger. %imilarly, if you de)ne your o#n rules in Oracle
%ubledger -ccounting to over#rite accounts, ten you must ensure tat te rules derive transaction
accounts tat roll up to budget accounts.
Note: Oracle +eneral ,edger does not allo# you to post encumbrance journal entries to summary
accounts.
Online Funds C)ecking
.en budgetary controls are enabled for a project, a funds cec$ is performed for all project-related
expense commitment transactions before te transactions are processed. -fter a transaction is
approved, te funds cec$ process immediately updates te funds available balances to account for
te approved transaction.
(e funds available for a transaction are calculated by subtracting te actual and commitment
balances from te budget amounts for a given budget category. (e funds cec$ process is based on
te budgetary control settings.
Budget and !ncu&*rance +ournals ,n-uiry
*ou can vie# budget and encumbrance subledger journal entries from te Oracle %ubledger
-ccounting /n!uiry menu in Oracle Purcasing, Oracle Payables, and Oracle Projects.
0rom te Oracle %ubledger /n!uiry menu, coose %ubledger 1ournal Entries. 0rom te
%ubledger 1ournal Entries page you can coose o# you #ant to run te in!uiry. /f you coose to vie#
data #en any option is met, you must minimally specify eiter te ledger or +, date. *ou can
coose eiter Budget or Encumbrance as te Balance (ype. *ou can select additional options as
needed.
0or additional information about encumbrance event classes and event types, see:
/ntegrating #it Oracle %ubledger -ccounting, Oracle Projects Fundamentals and 2ata tat Oracle
Projects Prede)nes for Oracle %ubledger -ccounting, Oracle Projects Fundamentals.
Note: *ou cannot drill do#n from te subledger accounting level to see details of te journal entries.
Budgetary Control .ettings
*ou use budgetary control settings to de)ne te degree to #ic transactions are controlled 3control
levels4 and #en budget amounts can be spent 3time intervals4.
'i&e ,ntervals
- time interval de)nes te budget amounts and te transactions to be included in te available funds
calculation. (ime interval settings identify te beginning period and te ending period included in te
calculation. (e amount type identi)es te beginning period and a boundary code identi)es te
ending period.
/vaila*le Funds Calculation
(e available funds calculation is based on te values you enter for te follo#ing settings:
-mount (ype 3beginning budget period4
Boundary "ode 3ending budget period4
(ransaction +, 2ate
(e funds cec$ process determines available funds by summing te budget amounts and
subtracting actual and committed transaction amounts for a de)ned time interval. (e -mount (ype
de)nes te start of a time interval. *ou select from te follo#ing amount types:
%eriod 'o 0ate: (e funds cec$ routine uses funds available from te start of te period in #ic
te transaction +, date falls.
1ear 'o 0ate: (e funds cec$ routine uses funds available from te start of te year in #ic te
transaction +, date falls.
%ro2ect 'o 0ate: (e funds cec$ routine uses funds available from te start of te project. (e
Boundary "ode determines te end of a time interval. *ou select from te follo#ing boundary codes:
%eriod: (e funds cec$ routine uses funds to te end of te period tat includes te transaction
+, date.
1ear: (e funds cec$ routine uses funds to te end of te year in #ic te transaction +, date
falls.
%ro2ect: (e funds cec$ routine uses funds available to te end of te project.

(e follo#ing table so#s te valid combinations of amount types and boundary codes tat you can
set up for a budget, depending on te budget5s time pase.
Budget 'i&e %)ase /&ount 'y#e Boundary Code
P- Period, +, Period, or
6one
Project (o 2ate Project
P- or +, Periods Project (o 2ate *ear
P- or +, Periods Project (o 2ate Period
P- or +, Periods *ear (o 2ate *ear
P- or +, Periods *ear (o 2ate Period
P- or +, Periods Period (o 2ate Period
Note: .en budgetary controls are enabled, you cannot enter budget amounts using user-de)ned
date ranges.
Control 3evels
*ou use budgetary control levels to set te degree of control te system imposes on project
commitment transactions. *ou can enter default control levels at te project type, project template,
and project levels. *ou can also de)ne default values for resource lists.
*ou select from te follo#ing control levels:
/*solute: (e transaction is rejected if su7cient funds are not available.
/dvisory: (e transaction is accepted #en su7cient funds are not available, but a te system
issues a #arning noti)cation tat available funds are exceeded.
None: (e transaction is accepted and no funds cec$ is performed.
*ou can set control levels at te project, tas$, resource group, and resource levels: *ou can enter
di8erent values at eac level. 0or example, you can select te -bsolute setting at te project level
and te -dvisory setting at te resource level.
2epending on te budget entry metod used, you can override te default control level for a project,
and for individual tas$s, resource groups, and resources after you create a cost budget baseline. (e
follo#ing table depicts #eter you can override control levels at te project, tas$, and resource
levels, depending on te budget entry level and #eter te budget is categori9ed by resources.
Budget
!ntry 3evel
Categori4ed *y
$esources
Override at
%ro2ect 3evel
Override at
'ask 3evel
Override at $esource 3evel
or $esource 5rou# 3evel
Project *es *es 6o *es
Project 6o *es 6o 6o
(op (as$ *es *es *es *es
(op (as$ 6o *es *es 6o
,o#est (as$ *es *es *es *es
,o#est (as$ 6o *es *es 6o
(op (as$ and
,o#est (as$
*es *es *es *es
(op (as$ and
,o#est (as$
6o *es *es 6o


Funds C)eck $ollu#
.en control levels are eiter -bsolute or -dvisory, te funds cec$ process )rst tests te lo#est
budget level to determine te availability of funds. /f funds are available for a transaction at te
lo#est level, te funds cec$ tests te next level in te budgetary control ierarcy. (e process
continues until te transaction passes all levels or fails at any level. /f a transaction fails funds cec$
at a level #it a control level of -bsolute, te process is discontinued. &o#ever, if te control level is
-dvisory, an insu7cient funds #arning noti)cation is generated and te funds cec$ process
continues to te next level.
(e ierarcy of levels for te funds cec$, from lo#est to igest level, is as follo#s:
1. :esource
6. :esource +roup
7. ,o#est (as$
4. (op (as$
8. Project
Note: ;id-level tas$s are not included in te rollup succession.
!ntering Budget /&ounts or Controlled Budgets
*ou must enter ra# cost or burdened cost for cost budgets and revenue amounts for revenue budgets
#en you enter budget amounts for budgets tat ave budgetary Budgeting and 0orecasting <-=>=
controls enabled. -dditional consideration is re!uired #en your budget entry metod uses a
resource list and #en burdening is enabled for your project.
!ntering Cost and $evenue /&ounts
.en you enable a budget for budgetary controls, you must enter ra# cost or burdened cost
amounts for cost budgets or revenue amounts for revenue budgets. /f you enter only !uantities, te
baseline process fails because it does not use !uantity for budgetary control purposes. (e baseline
process uses only amounts from te Burdened Cost and Revenue amount types. 0or example, if you
enter revenue budget amounts only for te Hours and Currency amount types, te baseline process
fails. *ou must enter amounts for te Revenue amount type.
Budget /&ounts or $esources
/f te budgetary control level for resources or resource groups is -bsolute or -dvisory, and no budget
amount is entered for a resource or resource group, ten Oracle Projects treats te entered budget
amount as 9ero. -s a result, transactions tat map to resources #it no budget amounts fail te funds
cec$ at an -bsolute level and pass te funds cec$ #it a #arning at an -dvisory level. - budget
entry category called Unclassifed is available at te resource list level. (is category enables you to
enter one budget amount for a group of resources. *ou can selectively control costs for some
resources #itin a resource group by entering speci)c budget amounts for tose resources. *ou can
ten use te ?nclassi)ed category to budget for te remaining resources #itin te resource group.
(e ?nclassi)ed category serves as a budget line for any resource for #ic a speci)c budget line
does not exist.
Burden Cost /&ounts
/f burdening is enabled for a project, ten all funds cec$s are performed using te transaction
burdened cost. Oracle Projects provides te follo#ing metods of accounting for burden costs:
%ame Expenditure /tem
%eparate Expenditure /tem
.a&e !"#enditure ,te&
.en you account for burden cost on te same expenditure item as ra# costs, te funds cec$
process calculates te burden cost amounts for a transaction and adds tem to te ra# cost amount.
(e process ten maps te burdened transaction amount to a budget line and performs te
necessary funds cec$s.
.en you use te %ame Expenditure /tem metod of accounting for burden costs, enter budget
amounts for te burdened transaction costs.
.e#arate !"#enditure ,te&
.en you account for burden costs as separate expenditure items, te funds cec$ process
calculates te burden cost amounts for eac burden cost component and separately maps eac
burden amount and te ra# cost amount to a budget line. /ndividual funds cec$s are performed for
eac component. /f any component fails te funds cec$, ten te entire transaction is rejected.
.en you use te %eparate Expenditure /tem metod of accounting for burden costs and you are not
using a resource list for budget entry, enter budget amounts for te burdened transaction costs. (e
burden costs and te ra# cost are mapped to budget lines using te same mapping rules and are
terefore mapped to te same line. .en you use tis burden accounting metod and you are
budgeting using a resource list, te burden costs are not mapped using te resource for te ra# cost.
*ou must ensure tat eac burden cost component maps to a budget line #it te desired budgetary
control setting. (o do tis, de)ne your burden cost components as resources on your resource list and
ten use tese resources to enter budget amounts for burden costs. (is allo#s you to enter a
budgetary control setting for eac burden cost component and a control setting for budget lines
de)ned for ra# costs. /f you do not #ant to impose budgetary controls on burden cost amounts, you
can assign a control setting of None for all budget lines for burden component resources. -n
alternative to de)ning resources on your resource list for burden cost components is to use te
?nclassi)ed budget entry category to budget for burden cost amounts. /f a budget line cannot be
found for te burden cost components and an ?nclassi)ed budget line exists, ten te funds cec$
process maps te burden costs to te ?nclassi)ed line.
Budget 0e9nition .trategies
Oracle Projects budgetary controls only apply to expense commitment transactions. Budgetary
controls do not apply to oter project-related transactions suc as timecards, expense reports, or
inventory item purcases. (erefore, #en you enable budgetary controls for a project, it is
recommended tat you use one of te follo#ing strategies for de)ning cost budget amounts:
%trategy One: 2e)ne t#o budgets: an overall project cost budget and anoter budget for expense
commitment transactions.
%trategy (#o: 2e)ne one cost budget, #it budget lines tat trac$ and control only expense
commitment transactions.
0e9ne 'wo Budgets
2e)ne te follo#ing t#o budgets:
Overall %ro2ect Cost Budget
2e)ne an overall project cost budget. 3(ypically, te -pproved "ost Budget type is used to de)ne an
overall cost budget4. (e overall cost budget trac$s all project costs. 2o not enable budgetary
controls for te -pproved "ost Budget type.
Budget or !"#ense Co&&it&ent 'ransactions
2e)ne a separate budget for expense commitment transactions. /t is recommended tat you create a
user-de)ned budget type for te commitment budget. .en you enable budgetary controls for your
project, use te user-de)ned budget type.
(e commitment cost budget trac$s and controls te project5s expense commitment transactions.
(e commitment cost budget amounts are a subset of te budget amounts de)ned for te overall
cost budget.
0e9ne One Cost Budget
(e second approac for implementing budgetary controls uses one cost budget for all anticipated
project costs. (e budget includes separate budget lines for expense commitment transactions and
all oter anticipated project costs. (ypically, te -pproved "ost Budget type is used to de)ne a
project5s overall cost budget. (erefore, #en you de)ne a project, enable budgetary controls using
tis budget type. -fter you create a baseline, you must ensure tat budgetary control settings are
properly de)ned for all budget lines entered for your expense commitment transactions. /t is
recommended tat a control setting of 6one be entered for all oter budget lines. (is elps reduce
confusion, as funds cec$s are not performed for transactions mapping to tese lines.
'ransaction %rocessing :it) Controlled Budgets
.en a transaction is carged to a project, te funds cec$ processes are activated in bot Oracle
+eneral ,edger and Oracle Projects. 0unds cec$s are activated for ne# transactions and for adjusted
transactions. *ou can revie# Oracle Projects funds cec$ results online. :esults are displayed for
transactions tat pass te funds cec$ and for transactions tat fail te funds cec$.
Funds C)eck /ctivation ,n Oracle %urc)asing and Oracle %aya*les
/n Oracle Purcasing and Oracle Payables, funds cec$ processes are activated #en you select te
"ec$ 0unds option for a transaction, and also during te transaction approval process.
,&#ortant: 2o not cange project attributes on any purcasing or payables document #it existing
accounting entries. (is results in funds validation errors and incorrect budgetary control data. *ou
must reverse any existing accounting entries before you modify te project attributes on te
document.
Funds C)eck /ctivation in Oracle %ro2ects
/n Oracle Projects, budgetary controls only apply to expense commitment transactions. *ou interface
project-related expense commitment transactions from Oracle Purcasing and Oracle Payables to
Oracle Projects as supplier costs.
-fter you interface actual supplier costs to Oracle Projects, you can adjust te expenditure items in
Oracle Projects. (e follo#ing types of adjustments can a8ect te available funds for a project:
(ransfer
%plit
:everse
:ecalculate burden cost 3for example, due to a burden multiplier cange4
(e process P:": 2istribute %upplier "ost -djustments is used to recost supplier costs after you ma$e
adjustments. (is process performs a funds cec$ for transactions meeting all of te follo#ing
criteria.
(e supplier cost originated in Oracle Purcasing or Oracle Payables
(e transaction is carged to a project #it budgetary controls enabled
(e transaction is an expense item
.en you cange a burden multiplier, you must run one of te follo#ing processes to perform a
funds cec$ for te canged burden amounts. (e process you run depends on te burdening
metod for te project.
P:": 2istribute (otal Burdened "osts
:un tis process if te project is set up to account for total burdened costs.
P:": "reate and 2istribute Burden (ransactions
:un tis process if te project is set up to account for burden costs by burden cost component.
/f funds are available for te adjusted expenditure amounts, ten te adjustment item is cost
distributed. /f funds are not available for an item, ten te item is not distributed and an exception is
reported.
/f an item is not cost distributed as a result of a funds cec$ failure, ten you must perform one of te
follo#ing actions and rerun te process P:": 2istribute %upplier "ost -djustments:
/ncrease budget amounts so funds are available for te expenditure item.
2ecrease te budgetary control level from -bsolute to -dvisory or 6one for te budget level
causing te funds cec$ failure.
0or an adjusted item, undo te cange tat increased te expenditure item amount. 0or example, if
you increased a burden cost rate, ten set te rate bac$ to its original value.
0or a transferred item, transfer te item to a tas$ #itin te same project, or to anoter project or
project tas$ tat as su7cient funds available or tat does not ave budgetary controls enabled.
(iewing 'ransaction Funds C)eck $esults
-fter a funds cec$ runs in Oracle Projects, you can vie# te results from te (ransaction 0unds
"ec$ :esults #indo#. :esults are displayed for bot transactions tat passed te funds cec$ and
transactions tat failed te funds cec$.
'ransaction Funds C)eck $esults :indow
(o revie# transaction funds cec$ results, perform te follo#ing steps:
1. 6avigate to te 0ind (ransaction 0unds "ec$ :esults #indo#.
6. Enter selection criteria.
7. "oose te 0ind button to display te (ransaction 0unds "ec$ :esults #indo#.
4. %elect a budget level tab to vie# information for a speci)ed budget level.
'ransaction Funds C)eck ;eader ,nor&ation
(e eader region of te (ransaction 0unds "ec$ :esults #indo# displays transactions tat ave
undergone a funds cec$. (is region is a folder-type region. -ll of te details about te transaction
can be displayed, including te speci)c funds-cec$ )elds so#n in te table belo#:
Field Na&e 0escri#tion
Pac$et /2 /denti)er assigned to te budgetary control
pac$et
%tatus 0unds cec$ status
2ocument
(ype
(ype of document 3for example, purcase
re!uisition4
@ersion
6umber
Budget version number
(e #indo# displays funds cec$ information by budget level for te selected transaction. - tab is
displayed for eac project budget level. (e information displayed at eac budget level includes
budget, available funds, transaction amounts, and a status message for te funds cec$ results.
Note: ?se te P-: 2ays to ;aintain B" Pac$ets pro)le option to control o# long funds cec$ results
are retained for online vie#ing. %ee:
Funds C)eck 0etail ,nor&ation
(e detail region displays te )elds so#n in te table belo#:
Field Na&e 0escri#tion
-ccount /denti)er of te +, account 3#en
budget integration is used4
Budget Budget total used for funds cec$
based on te de)ned budgetary
control time interval
-ctuals "ommitment transactions interfaced
to Projects
"ommitments -pproved commitment transactions
not yet interfaced to Projects
-vailable Balance -vailable funds before te funds
cec$
(ransaction -mount -mount of te transaction
6e# -vailable
Balance
-vailable balance after te funds
cec$
0unds "ec$
:esults
0unds cec$ status information

Maintaining Budgetary Control Balances
Oracle Projects maintains budgetary control balances for all projects tat use budgetary controls. 0or
eac budget line, te budget amount, te commitment transactions total, and te total actuals
related to commitment transactions are maintained. (e system also calculates available funds for
eac budget category and budget period. .en you create a baseline from te original budget
version, te system creates initial balances. .en you run te P:": ;aintain Budgetary "ontrol
Balances process, te balances are updated. (e updated balances are displayed in te Budget 0unds
"ec$ :esults #indo#. /t is recommended tat you use te sceduling options to run te ;aintain
Budgetary "ontrol Balances process regularly. (o determine o# often to scedule te process,
consider te number of project-related commitments your business creates eac day as #ell as your
online in!uiry business needs.
(iewing Budgetary Control Balances
?se te Budget 0unds "ec$ :esults and "ommitment -mounts #indo#s to vie# budgetary control
balances online.
Budget Funds C)eck $esults :indow
(is #indo# displays budget, actuals, commitments, and available funds balances for eac budget
level. (e #indo# includes a tabbed region for eac project budget level. (e levels can include te
follo#ing: project, top tas$, tas$, resource group, and resource. *ou can use te #indo# to revie#
project-to-date transactions and to plan future expenditures. *ou can also use te information in tis
#indo#, along #it te (ransaction 0unds "ec$ :esults #indo#, to troublesoot transaction funds
cec$ failures. "oose te "ommitments button to display te commitments total for te selected
line, summari9ed by commitment type.
(e follo#ing table so#s te )elds in eac tabbed region of te Budget 0unds "ec$ :esults #indo#.
-ll )elds are for display only.
Field Na&e 0escri#tion
"ontrol ,evel Budgetary control level for a budget line
Budget Budget amount for a budget line
-ctuals "ommitment transactions interfaced to
Oracle Projects
"ommitments -pproved commitment transactions not
yet interfaced to Oracle Projects
0unds -vailable -vailable funds 3budget amount less
actuals and commitments4 based on te
de)ned time interval
%tart 2ate Beginning period date for amounts in a
budget line
End 2ate Ending period date for amounts in a
budget line
:esult 3reserved for future use4
Co&&it&ent /&ounts :indow
(o revie# commitment amounts by commitment type, perform te follo#ing steps:
1. 6avigate to te Budgets #indo# from te Projects 6avigator.
6. Auery te project cost budget.
7. "oose te &istory button to vie# te budget version istory.
4. %elect @ie# 0unds "ec$ :esults from te (ools menu.
8. %elect a budget level tab to vie# budget lines for a speci)ed budget level.
<. "oose te "ommitments button to vie# te commitment details for a selected line.
(e follo#ing table so#s te )elds te "ommitment -mounts #indo#. -ll )elds are
for display only.
Field Na&e 0escri#tion
:e!uisition (otal purcase re!uisition commitments recorded
against a budget line
Purcase Order -mount of purcase order commitments recorded
against a budget line
%upplier /nvoice -mount of supplier invoices recorded against a
budget line tat ave not been interfaced from
Payables to Projects
(otal (otal commitments for a budget line
Modiying Controlled Budget /&ounts
.en you modify a project budget, budgetary control balances are created for te ne# budget
version. 2uring te baseline process, all existing project transactions are mapped to a budget line in
te ne# version. - funds cec$ is performed for all transactions subject to budgetary controls to
ensure tat transaction totals do not exceed available funds calculated using te ne# budget
amounts. (e baseline process fails if te budget amounts for te ne# budget version cause a
budgetary control violation.
(o identify te cause of a failure, !uery te draft budget version using te Budget 0unds "ec$
:esults #indo#. -ny budget line #it a negative amount in 0unds -vailable and an -bsolute control
level causes te baseline to fail.
/d2usting Budgetary Control 3evels
.en you create a baseline for a project budget for te )rst time, Oracle Projects creates default
budgetary control level settings for eac budget level based on te values in te Budgetary "ontrols
option. *ou can override te default control level values for te baseline budget version. .en you
create subse!uent baselines for te project budget, Oracle Projects uses te revised budgetary
control level settings and not te default settings. 0or example, if you override te budgetary control
level for a tas$, Oracle Projects does not reset te tas$ to te default value te next time tat you
create a baseline for te budget.
/f you add ne# tas$s to te project or ne# resource groups or resources to te resource list assigned
to te budget, te next time you create a baseline for te budget, Oracle Projects automatically
creates default budgetary control settings for te ne# tas$s, resource groups, or resources. *ou can
override te default control level values for te baseline budget version.
(o adjust budgetary control levels, perform te follo#ing steps:
1. 6avigate to te Budgets #indo# from te Projects 6avigator.
6. Auery your project cost budget.
7. "oose te &istory button to vie# te budget version istory.
4. %elect Budgetary "ontrols from te (ools menu.
8. "ange control level values as re!uired.
<. %ave your #or$.
7. /f you are budgeting using a resource list, coose te :esources button on te Budgetary "ontrol
#indo# to override te default values for resource groups and resources.
,&#ortant: *ou can select te Reset e!aults button on te Budgetary "ontrol #indo# to restore te
default budgetary control settings for te project. .en you select te Reset e!aults button, Oracle
Projects resets all budgetary control settings to te default values, including any settings tat you
ave manually overridden.
0eault Budgetary Controls and C)anging t)e Budget !ntry Met)od
*ou can cange te budget entry metod for a budget after you create a baseline version. /f te
budget entry level for te ne# budget entry metod is di8erent from te budget entry level for te
current budget entry metod, Oracle Projects resets to te budgetary controls to te default
budgetary control level settings #en you create te next budget baseline. 0or example, if te
budget entry level of te current budget entry metod is "op "as#s and te budget entry level for te
ne# budget entry metod is $o%est "as#s, Oracle Projects resets te budgetary controls to te
default budgetary control level settings #en you create te next budget baseline.
Budgetary Controls Cross C)arge $estriction
- transaction is subject to te budgetary controls de)ned for only te ledger in #ic te transaction
originates. (erefore, #en budgetary controls are enabled for a project, you cannot enter cross
carge transactions tat cross ledgers.
(e follo#ing scenario illustrates te need for tis restriction:
(#o ledgers are de)ned in an installation of Oracle -pplications.
/n ,edger One 3,=4, budgetary controls are enabled in Oracle +eneral ,edger and Oracle Payables.
/n ,edger (#o 3,B4, budgetary controls are not enabled in any application.
Project - is de)ned in ,= and budgetary controls are enabled for te project. /f you enter a
commitment transaction in ,B for Project -, te transaction is not funds cec$ed, because budgetary
controls are not enabled in ,B.
Funds C)eck $esult Messages
(e follo#ing table lists funds cec$ result codes and messages, and provides information on
responding to eac message.
$esult
Code
$esult 'e"t Corrective /ction
0=>> /nsu7cient
0unds
Ensure tat funds are
available
0=>= 6o budget exists at te resource
level
Ensure tat a budget exists at
te resource level
0=>B 6o budget exists at te resource
group level
Ensure tat a budget exists at
te resource group level
0=>C 6o budget exists at te tas$
level
Ensure tat a budget exists at
te tas$ level
0=>D 6o budget exists at te top tas$
level
Ensure tat a budget exists at
te top tas$ level
0=>E 6o budget exists at te project
level
Ensure tat a budget exists at
te project level
0=>< 6o budget exists at te project
account level
Ensure tat a budget exists at
te project account level
0=>F (e transaction failed funds cec$
at te resource level
/ncrease te budget at te
resource level or cange te
budgetary control level to
&dvisory or None
0=>G (e transaction failed funds cec$
at resource group level
/ncrease te budget at te
resource group level or
cange te budgetary control
level to &dvisory or None
0==> (e transaction failed funds cec$
at te tas$ level
/ncrease te budget at te
tas$ level or cange te
budgetary control level to
&dvisory or None
0=== (e transaction failed funds cec$
at te top tas$ level
/ncrease te budget at te top
tas$ level or cange te
budgetary control level to
&dvisory or None
0==B (e transaction failed funds cec$
at te project level
/ncrease te budget at te
project level or cange te
budgetary control level to
&dvisory or None
0==C (e transaction failed funds cec$
at project account level
/ncrease te budget amount
at te project account level
0==D (e transaction failed to populate
burden cost
"ontact your system
administrator for assistance
0==F 0unds cec$ failed because of
invalid budget versions
"reate a baseline version for
te project budget
0=B> 0unds cec$ failed during setup
and summari9ation
"ontact your system
administrator. *our system
administrator can run funds
validation #it P- debug on to
identify te error.
0=B= (e resource list is invalid or null /f te project budget is
categori9ed by resource, ten
ensure tat you assign a
resource list to te budget
0=BB (e amount type or boundary code
is invalid
?pdate te amount type or
boundary code in te
budgetary control settings for
te project
0=BC (e amount type or boundary code
is invalid for no time pase
(o create a budget #itout
time pases, select an
amount type of Project to
ate and a boundary code of
Project in te budgetary
control settings for te project
0=BD /nvalid boundary code for amount
type Project (o 2ate
"ontact your Oracle Projects
super user for assistance. *our
Oracle Projects super user can
verify te amount type and
boundary code combination
for te project.
0=BE /nvalid boundary code for amount
type *ear (o 2ate
%elect eiter 'ear or Period as
te boundary code in te
budgetary control settings for
te project
0=BH /nvalid boundary code for amount
type Period (o 2ate
%elect Period to ate as te
boundary code in te
budgetary control settings for
te project
0=BF 0unds cec$ failed because of
invalid resource list member
@erify tat te resource list
member is included in te
resource list. /f te member is
included in te list, ten
ensure tat te resource list
member is valid.
0=BG %tart date or end date is null for
te speci)ed date range
0or a budget #it a Project to
ate amount type and Project
boundary code, ensure tat a
budget line exists for te
period or tat you specify
bot a start date and an end
date for te project. 0or oter
amount type and boundary
code combinations, ensure
tat a budget exists for te
period associated #it te
transaction.
0=C> %tart date or end date is null for
te speci)ed P- period
0or a budget #it a Project to
ate amount type and Project
boundary code, ensure tat a
budget line exists for te
period or tat you specify
bot a start date and an end
date for te project. /n
addition, ensure tat te P-
period is valid.
0=C= 0unds cec$ failed because of
invalid budget entry metod
Ensure tat te Burdened
Cost option is enabled for te
budget entry metod
0=CB "ould not map to a budget line
#ile deriving budget account
Ensure tat budget lines are
generated for all periods
0=CD %tart date or end date is null for
te speci)ed +, period
0or a budget #it a Project to
ate amount type and Project
boundary code, ensure tat a
budget line exists for te
period or tat you specify
bot a start date and an end
date for te project. 0or a
budget #it a time pase of
($ Period, ensure tat te
period is valid and tat it is
not set up as an adjustment
period.
0=C< 0unds cec$ failed #ile calculating
start date or end date
"ontact your system
administrator. *our system
administrator can trace te
process to obtain additional
information.
0=CH 6o matcing re!uisition #as found
for tis purcase order
"ontact your system
administrator. 2ata issues
can cause tis error.
0=CF 6o matcing purcase order #as
found for tis invoice
"ontact your system
administrator. 2ata issues
can cause tis error.
0=D> 0ailed due to fatal error #ile
inserting burden cost
"ontact your system
administrator. *our system
administrator can trace te
process to obtain additional
information.
0=D= "ould not ac!uire loc$: funds
cec$s are running concurrently
:etry te funds cec$
0=DB 0unds cec$ failed because of
unexpected error
"ontact your system
administrator. *our system
administrator can trace te
process to obtain additional
information.
0=DC 0unds cec$ failed because budget
baselining is in progress
:etry te funds cec$ after
te baseline process for te
budget is complete
0=E> (e +, funds cec$ failed for te
cec$ funds mode
2ecrease te project budget
or increase te +, budget
0=E= (e +, funds cec$ encountered
fatal errors
"ontact your system
administrator. *our system
administrator can trace te
process to obtain additional
information.
0=EE (e +, funds cec$ failed for te
full mode
2ecrease te project budget
or increase te +, budget
0=E< (e +, funds cec$ failed for te
partial mode
2ecrease te project budget
or increase te +, budget
0=<> 0unds cec$ failed to generate te
return code
"ontact your system
administrator. *our system
administrator can trace te
process to obtain additional
information.
0=<B 0unds cec$ failed to update "ontact your system
budget account balances administrator. *our system
administrator can trace te
process to obtain additional
information.
0=<E 6o budget account on ra# line Ensure tat a budget account
exists
0=<< 6o baselined budget version exists
for tis project
"reate a baseline version for
te project budget
0=<F Encumbrance accounting event
could not be created
"ontact your system
administrator. *our system
administrator can revie# te
log )les to obtain additional
information.
(is error relates to setup for
Oracle %ubledger -ccounting.
/f you modi)ed a prede)ned
application accounting
de)nition, ten you must
revalidate it. /n addition,
verify any modi)cations to te
prede)ned subledger
accounting setup.
0=<G -ccount canged for a budget line
#it an existing transaction
Ensure tat account as not
been canged for a budget
line #it an existing
transaction
0=H> (ransaction failed in full mode - related transaction in te
process failed. 0ix te related
distribution line tat failed
funds cec$ and ten rerun
te funds cec$.
0=HB Oracle %ubledger -ccounting
application failed
"ontact your system
administrator. *our system
administrator can revie# te
log )les to obtain additional
information.
(is error relates to setup for
Oracle %ubledger -ccounting.
/f you modi)ed a prede)ned
application accounting
de)nition, ten you must
revalidate it. /n addition,
verify any modi)cations to te
prede)ned subledger
accounting setup.
0=HC 2istribution record missing in
+eneral ,edger table
"ontact your system
administrator. *our system
administrator can revie# te
log )les to obtain additional
information.
(is error relates to setup for
Oracle %ubledger -ccounting.
/f you modi)ed a prede)ned
application accounting
de)nition, ten you must
revalidate it. /n addition,
verify any modi)cations to te
prede)ned subledger
accounting setup.
********************************************************************************
Budgetary Control and Budget Integration-Technical Overview
Metalink Note: 8353!"
Main Tables, Views and Packages Used For Budgetary Control and Funds Check:
Tables
BUDGT!"# C$%T"$& ' Main Tables:
P!(BUDGT(&)%*
P!(BUDGT(!CCT(&)%*
P!(BUDGT(V"*)$%*
P!(BUDGT(%T"#(MT+$D*
P!(BUDGT(T#P*
P!(BC(B!&!%C*
P!(BUDGT!"#(C$%T"$&*
P!(BUDGT!"#(C$%T"$&($PT)$%*
P!(G&(%CUMB"!%C(T#P*
FU%D* C+C,
P!(BC(C$MM)TM%T*(!&&
P!(BC(B!&!%C*
P!(BC(P!C,T*
GM*(BC(P!C,T*
G&(BC(P!C,T*
G&(%CUMB"!%C(T#P*
P!(BC(P!C,T(!"")V!&($"D"
#e$cri%tion o& Ta'le$
P!(BC(C$MM)TM%T*(!&&
! -ulti.org /iew which will retrie/e data 0or your current o1erating unit and ignore data in other
o1erating units2 +olds all the co--it-ent transactions 3"e4uisitions, P$s and Payables5 that are 0unds
checked2
P!(BC(B!&!%C*
*tores actual, budget and encu-brance balances 1er 1ro6ect, task, 1eriod, budget /ersion and resource2
Budget balances are created during the budget baselining 1rocess2
!ctuals and encu-brances accounting entries are created by -aintain 1ro6ect balances 1rogra-2
G&(%CUMB"!%C(T#P*
*tores in0or-ation about encu-brance ty1es, including their )Ds and descri1tions2
P!(BC(P!C,T*
+olds all the transactions that are co1ied 0ro- G&(BC(P!C,T*2
G&(BC(P!C,T*
General &edger7s -ain table 0or the Budgetary Control 0eature2
GM*(BC(P!C,T*
$racle Grants !ccounting7s -ain table 0or the budgetary control 0eature2
P!(BC(P!C,T(!"")V!&($"D"
,ee1s track o0 the order in which in which the budgetary control 1ackets need to be 1rocessed2
P!(BUDGT!"#(C$%T"$&*
Used to store the controls le/els that are used to regulate how the 0unds are reser/ed 0or transactions
P!(BUDGT!"#(C$%T"$&($PT)$%*
*tores all the de0ault budgetary control le/els and ti-e inter/als

(iew$
P!(P"8(FC("*U&T*(V
P!("*(FC("*U&T*(V
P!("*(G"P(FC("*U&T*(V
P!(T!*,(FC("*U&T*(V
P!(T$P(T!*,(FC("*U&T*(V
P!(P"$8CT(B!&(V
)elea$e * ON+,
P!(9&!(BC(BUDGT(&)%*(V
P!(9&!(BC(P,T(!P(DT!)&(V
P!(9&!(BC(P,T(P$(DT!)&(V
P!(9&!(BC(P,T(":(DT!)&(V
P!(9&!(CD&(&)%*(V
-ackage$ and -rocedure$
P!(BGT(B!*&)%(P,G . P!FCB!&B21ls
Create 1a(bc(balances records 0ro- P!(BUDGT(&)%* and to clean u1 P!(BC(P!C,T*
P!(BUDGT(!CC$U%T(P,G . P!BD!CGB21ls
Generate the !ccount Code CC)D 0or e/ery Budget &ine de1ending u1on the calling -ode 1ara-eter2
P!(BUDGT(FU%D(P,G . P!BBF%DB21ls
Procedure called 0ro- budgets 0or-s2 This 1rocess will /eri0y i0 0unds check is re4uired or not2
P!(FU%D*(C$%T"$&(P,G . P!BCFC,B21ls
This is the Main 0unds check 0unction which calls all the other 0unctions and 1rocedures
P!(FU%D*(C$%T"$&(P,G; . P!BCP,T*21ls
This !P) gets the *tart and nd date based on a-ount ty1e and boundary code
P!(BUDGT!"#(C$%T"$&*(P,G . P!9BCC"B21ls
)nserts records into P!(BUDGT!"#(C$%T"$&*
G&(FU%D*(C+C,"(P,G . G&FBCFCB21ls
Funds Check !P) 0or any 1rocess that needs to 1er0or- Funds Check and<or Funds "eser/ation
P!(#!"(%D("$&&$V"(P,G . P!B"&#"B21ls
=ecute the #ear nd Budget "ollo/er 1rocess
P!(*>P" . P!FCU!B21ls
Based on TPC 31a(budget(entry(-ethods2ti-e(1hase(code 5, returns the start date
!dditional 1ackages
P!(FC("*(M!P. P!FC"MPB21ls
P!(BC(C$*T)%G . P!BCC*TB21ls
P!(BUDGT(PVT . P!PMBUVB21ls
P!(FU%D*(C$%T"$&(UT)&* . P!FCUT&*21ls

-roce$$e$ and their &unction$
;2Funds Checking Process
*te1;: !ll transactions that need to be 0unds checked are grou1ed into
BC Packets
*te1?: The transaction 1rocess calls the 0unds checker
*te1@: The 0unds checker calculates the burdened cost a-ount2
*te1A: Burden costs are added to BC Packets2
*te1B: BC Packet entries are -a11ed to e=isting budget lines using the standard P*) resource -a11ing
rules2
*te1C: ach BC Packet entry is 0unds checked 0or each budget le/el that has a control le/el o0 !bsolute or
!d/isory2
*te1D: Funds checker u1dates the 1acket entries with the 0unds check results
*te1E: Control 1asses back to the transaction 1rocessor which /alidates the results o0 all 0unds checks
1er0or-ed 0or the transaction2
*te1F: The Maintain Balances concurrent 1rocess 1eriodically reads the a11ro/ed BC Packet entries and
u1dates the actual costs, co--it-ent costs, and a/ailable 0unds balances 0or the 1ro6ect at all 1ro6ect
le/els2
The 1rogra- 1er0or-s the 0ollowing tasks:
Deletes entries in BC Packets which ha/e been 1osted and e=ceed the P!: Days to -aintain BC Packets
1ro0ile /alue U1dates<)nserts records in P!(BC(B!&!%C* )nserts records in
P!(BC(C$MM)TM%T*
%ote: )t is reco--ended that this 1rocess be sub-itted with re1eat 1ara-eters2
?2Transaction Processing:
Transactions are 0unds checked as 0ollows:
Co--it-ents in P$ and !P:
Funds checked online during docu-ent a11ro/al
*u11lier )n/oice !d6ust-ents:
*u11lier )n/oice !d6ust-ents entered in Pro6ects are 0unds checked during cost distribution
*u11lier )n/oice !d6ust-ents entered in Payables are 0unds checked during in/oice rea11ro/al
%ote: ! baselined budget -ust e=ists or the transactions will be re6ected by the 0unds check 1rocess2
@2Transaction Processing with G& Budgetary Controls enabled:
)0 Budgetary Controls are enabled in P! and G& and the P! budget is %$T integrated to the G& budget,
transactions are 0unds checked by both P! and G& inde1endently2
G& 0unds checks will be 1er0or-ed as 0ollows:
Transactions originating in P$ and !P:
G& Funds Check 1er0or-ed during docu-ent a11ro/al a0ter the P! Funds Check
!d6ust-ents originating in P!:
P! Funds Check 1er0or-ed during cost distribution
G& Funds Check 1er0or-ed during !P docu-ent a11ro/al
Changes in ";? V* ";;2B2;GM
!2 Funds Manage-ent:
;2$racle Contract Co--it-ent integration is not su11orted in ";?
?2Fundscheck will be 1er0or-ed only during budget baseline 30or the newly baselined /ersion 5 and not
during sub-it 2
B2 ncu-brance !ccounting:
Budgetary Control accounting e/ents are raised to account encu-brances 0or
)ntegrated Budgets ' to check and reser/e 0unds against the G& Funding budget
Transactions ' "e4uisitions, Purchase $rders, )n/oice co--it-ents 2
ncu-brance . For burden a-ounts 0or co--it-ents are accounted under Purchasing and Payables
a11lications as 0ollows
Ty1e o0 Co--it-ent !11lication . /ent ntity /ent Classes
"e4uisition Purchasing ' "e4uisition Burden 0or "e4uisition
Purchase $rders Purchasing ' Purchase $rder Burden 0or Purchase $rders
Blanket, *cheduled "eleases Purchasing ' "elease Burden 0or "elease
)n/oices, Credit Me-os, Debit Me-os Payables ' !P )n/oices Burden 0or )n/oices
Pre1ay-ents Payables ' !P )n/oices Burden 0or Pre1ay-ents
Pre1ay-ent !11lications Payables ' !P )n/oices Burden 0or Pre1ay-ent !11lications
Total Burdened Cost =1enditures Total Burdened Cost
Total Burdened Cost !d6ust-ent
Burden Cost =1enditures Burden Cost

C2 Budget Baseline Processing:
;2$/erride budget account :
. De0ine account deri/ation rules in *&! to o/erride the budget account
. !ccount change not allowed i0 transactions e=ist
?2ach budget line 1rocessed unlike su--ariHed budget data in ";;i
@2>hen budget a11ro/al work0low is enabled, 0unds /alidation occurs a0ter a11ro/al is obtained 2

D2 #ear nd Budget "ollo/er Processing:
;2#ear nd Budget "ollo/er 1rocess generates li4uidation entries to re-o/e the 1ro6ect reser/ation 0or the
0unding budget 0or the closing 0iscal year2 These entries are now 1osted to the last 1eriod o0 the indi/idual
accounts2
?2)0 a budget line is being established 0or the 0irst 1eriod o0 the new 0iscal year, #ear nd Budget "ollo/er
1rocess no longer trans0ers the account in0or-ation 0ro- the 1re/ious year to the new 1eriod2 !ccount
generator is called to deri/e the budget line account2

2 Transaction Processing:
;2Budget account can be di00erent 0ro- the transaction 3charge5 account
?2Un-atched 1re1ay-ent a11lications are now 0unds checked during in/oice /alidate 1rocess
@2!ccounting is now 1art o0 the transaction 1rocessing 0low 2
A2%o u1date 0or a budget line is allowed i0 a transaction e=ists against the budget line

F2 Data Model Changes:
;2Changed Tables :
. %ew colu-ns are added to ca1ture encu-brance accounting e/ents to the 0ollowing tables:
P!(BUDGT(&)%*
P!(BC(P!C,T*
P!(BC(C$MM)TM%T*(!&&
. %ew colu-ns are added to the 0ollowing tables 0or budget -a11ing:
P!(C$*T(D)*T")BUT)$%(&)%*
P!(BC(P!C,T*
P!(BC(C$MM)TM%T*(!&&
.%ew /iews ha/e been created as data e=tract ob6ects 0or the encu-brance e/ent classes
G2 For- *tructure :
ncu-brance ty1e 0ield and associated /alidations ha/e been re-o/ed 0ro- the budgetary controls
integration window on Pro6ect Ty1e and Pro6ects 0or-2
Troubleshooting "eco--endations
;2 For baseline<check 0unds o0 budget, result colu-n on the dra0t su--ary record 3Budget 0or-: IBy
accountJ tab on the budgetary controls window5 indicates 1rocessing status2
?2 For re.baseline with Pro6ects 0unds check /alidation 0ailures, use Budget 0or- 3 Tools .K View 0unds
check results5
@2For Debug logs, e=ecute the 1rocess with F%D<P*!<P! debug $%2 Debug log generated hel1s you to
identi0y the 0ailure 1oint2
A2rror: Budget baseline<check 0unds 1rocessing 0ails with I )n/alid code co-bination id or so-e in/alid
data that 1re/ented the syste- 0ro- creating an accounting 6ournal 0or the e/entJ
Cause: Possible issues could be that the I!11lication !ccounting De0initionJ 3!!D5 is in/alid or that the
!!D is not attached to the I*ub &edger !ccounting MethodJ 3*&!M52 This usually ha11ens a0ter a 1atch
has been a11lied that in/alidated the *&! seed de0inition2
B2rror: Transaction 1rocessing 0ailed with I$racle *ubledger !ccounting engine 0ailedJ
or
IDistribution record -issing in General &edger tableJ 2
Cause: *a-e as abo/e
"e0erences :
;2$racle Pro6ects ;;i Mini.1ack + . Docu-entation *u11le-ent
?2$racle Pro6ects . )-1le-entation Guide
@2$racle Pro6ect Manage-ent . User Guide
A2$racle Purchasing . User Guide
B2$racle Payables . User Guide
C2Metalink .eT"M Technical "e0erence
.ntity relationshi1 diagra-s:
.Tables and Views
.Packages
LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLndLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL
Oracle %ro2ects = .te#s to &ake t)e %ro2ect Budgetary Control eatures
work
Blog: Real World Oracle Apps
URL: http://realworldoracleapps.blogspot.com/2008/05/steps-to-make-project-budgetary-
cotrol.html
!ubl"shed o behal# o# Ra$"shakar !achapagesa:
% &et the $alue o# the pro#"le !' : (able )udget *tegrat"o ad )udgetary +otrol
% (able )udgetary +otrol " the &et o# )ooks w"dow ad choose a de#ault (cumbrace accout
% ,or the )udget +otrol -roup .&tadard/ " -L meu0 eter !rojects as the source ad 1otal )urdeed +ost as
the category ad choose the #ud check le$el o# . 2oe/
% (sure th"s "s the $alue o# the pro#"le at the appl"cat"o or respos"b"l"ty #or the pro#"le opt"o .)udgetary
+otrol -roup/
% +heck .Use !3 (cumbrace " !ayables ,"ac"al 3pt"o ad eter $alues #or !3 ad *$o"ce ecumbrace
type.
% * !urchas"g meu0 3pe the (cumbrace year ad per"od. * !urchas"g0 there are 2 ,orms. 3e #or 3pe
ad +lose !er"ods ad the other #or +otrol !urchas"g !er"ods. Use the +otrol !urchas"g !er"od to ope the
(cumbrace 4ear ad the correspod"g -L per"od. 1h"s "s a pre re5u"s"te #or ecumbrace to work. Use the
3pe ad +lose !er"ods #or cotroll"g !urchas"g !er"od.
% +omplete the set ups #or !roject type0 budgetary cotrol tab ad create project templates ad projects us"g
the set up.
% (sure that the budget etry method allows the etry o# 1otal )urdeed cost. 4ou do ot ha$e to burde the
trasact"os. &ystem populates the raw cost budget "to th"s #"eld #or budgetary cotrol check.
% (sure the pre re5u"s"te -L patches 62o 7885879 ad 2002508: are " the appl"cat"o. 1hese patches are
"cluded " !' ; as cumulat"$e compoets.
% (ter trasact"os " '! ad $er"#y the process. Upo sa$"g the "$o"ce0 a$"gate to the 1ools ;eu ad cl"ck .
+heck ,uds/ meu. &ystem w"ll d"splay a message whether the "$o"ce ad "ts d"str"but"o l"es w"ll pass or #a"l
#uds check.
% <al"date the "$o"ce ormally. ,uds check w"ll be per#ormed upo $al"dat"o based o the amout type ad
boudary code assoc"ated w"th the !roject ad the cotrol le$els chose #or the project0 task0 resource group
ad resource l"st le$el.
% *$o"ces that #a"led the #uds check upo $al"dat"o w"th the reaso code .,uds check"g could ot be
per#ormed/ caot be maually released. 4ou eed to ehace the #uds a$a"lable.
% 4ou ca $"ew the 1rasact"o ,uds +heck Results " !rojects regardless o# the "ter#ace #rom '!.
% ,or each l"e that "s passed #uds check0 " the abo$e w"dow0 the system w"ll d"splay 2 rows: 7 w"th the status
.!assed #uds check/ ad the other w"th the status .'ppro$ed/
% *ter#ace $al"dated ad accouted "$o"ce d"str"but"o l"es to !rojects ormally.
% &chedule to ru the process !R+: ;a"ta" )udgetary +otrol )alaces based o bus"ess re5u"remets. =he
th"s process "s ru0 the system purges deta"ls o# ,uds check results d"splay. +hoose to ru th"s process "
cojuct"o w"th the $alue o# pro#"le opt"o #or !': >ays to ma"ta" )+ packets
% 4ou caot chage the budget amout type #or budgetary cotrol " the !rojects w"dow a#ter suppl"er "$o"ce
costs are "curred. ?owe$er0 you ca chage the cotrol $alues ad amout type ad boudary codes. *# you do0
system w"ll prompt the user to re basel"e the curret $ers"o o# the cost budget used.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ed@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+ournal .till Fails Funds C)eck ,n /dvisory .etu#
Metalink Note: 414898.1
.olution:
=."ec$ te value of te pro)le : Budgetary "ontrol +roup
B. +o to Budgets -I2e)ne -I"ontrol and !uery te value from te above pro)le.
/f at budgetary control level te funds cec$ is absolute ten te fund cec$ #ill be absolute.
*ou can de)ne absolute or advisory budgetary control at te individual account level. &o#ever, if
you ave budgetary control options de)ned at anoter level, suc as by source and category, or for
a summary template tat includes te detail account, te budgetary control options for te account
migt override any oter options.
2epending on o# you de)ne budgetary control options, conJicts migt arise tat te funds cec$er
must resolve. 0or example, you enter absolute budgetary control for all transactions a8ecting
"ompany >=, and advisory budgetary control for journal entry source Project ;anagement and
category .or$ Orders. /f you use 1ournal /mport to import a Project ;anagement .or$ Order carged
to "ompany >= into +eneral ,edger, te funds cec$er must resolve te conJict bet#een budgetary
control options. (e table belo# so#s te type of funds cec$ing te system performs if te
budgetary control options you ave de)ned by journal entry source, category, and user conJict #it
tose for a particular account.
1E %ource, "ategory,
or ?ser0unds
"ec$ing Option
%ummary or 2etail
-ccount 0unds
"ec$ Option %et to
6one
%ummary or 2etail
-ccount 0unds
"ec$ Option %et to
-dvisory
%ummary or 2etail
-ccount 0unds
"ec$ Option %et to
-bsolute
6one 6one 6one -bsolute
-dvisory 6one -dvisory -bsolute
-bsolute 6one -bsolute -bsolute
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@(2>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@