This chapter covers the following topics:
This flow helps user to baseline the budget.
PLSQL Flow
PJT_Baseline_Budget_PLSQL
The following are the prerequisites for executing the flows:
This flow assumes that all mandatory setups for creating, managing and maintaining budgets through PL SQL API are already done and assumption is that user is actively using the Oracle Project Management Budgeting & Forecasting features.
The user and responsibility used must have all required security functions needed to baseline the budget.
An approved contract project exists with customer agreement.
Financial plan types have been added to the project and working plan versions are already available.
Required funding is available for the project, if a revenue budget is to be baselined.
The following profile options must be set:
Profile | Value |
---|---|
HR: Business Group | Vision Corporation |
HR: Security Profile | Vision Corporation |
MO: Operating Unit | Vision Services |
MO: Security Profile | Vision Corporation |
MO: Default Operating Unit | Vision Services |
GL Ledger Name | Vision Services (USA) |
The following predefined data must be used:
Entity | Field Name | Field Value |
---|---|---|
PA_SET_GLOBAL_INFO | Version Number | 1 |
User Id | 1319 | |
Resp Id | 53321 |
The following data must be set up:
Entity | Field Name | Field Value |
---|---|---|
PA_BUDGET_PUB_BASELINE_BUDGET_Main | ||
API Version Number | 1 | |
Commit | F | |
PM Product Code | MSPROJECT | |
PA Project Id | 14044 | |
Mark As Original | Y | |
Fin Plan Type Id | 10192 |
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact/Method | Component Set | Main Component |
---|---|---|---|---|
PJT_Baseline_Budget | Baselines budget version. | PLSQL | - | PA_BUDGET_PUB_BASELINE_BUDGET_Main |