Commitment Control to Project Costing Process

Use the Commitment Control to Project Costing Application Engine process (PC_KK_TO_PC) to post budget transactions in PeopleSoft Project Costing that you enter directly into Commitment Control. Rows are eligible to post in Project Costing if both of these conditions exist:

  • The Project Costing distribution status of the journal line is N (new).

  • The ledger group type is either expenses or revenue.

After you post budget journals directly into Commitment Control, if Projects Budgeting is enabled at the installation level and you run the Commitment Control to Project Costing process, the system:

  • Populates the Project Transaction Interface table.

  • Triggers the Budget Loader Application Engine process (PC_BUDGET_IN) that populates the Project Budgeting tables (PC_BUD_PLAN, PC_BUD_ITEM, and PC_BUD_DETAIL).

  • Updates the Project Costing Distribution Status field (PC_DISTRIB_STATUS) value to D (distributed) on the Commitment Control Budget Journal Line table (KK_BUDGET_LN).

If you create a budget journal in Commitment Control and run the Commitment Control to Project Costing process and if Projects Budgeting is enabled at the installation level and no current active budget plan exists for that project, then the system:

  • Modifies the Project Costing Distribution Status field value of the journal row to D (distributed).

  • Creates a budget plan in PeopleSoft Project Costing with an active status.

For example, assume that you post Journal A and Journal B to Commitment Control. Both journals have identical ChartField values. The Commitment Control to Project Costing process creates one active budget plan that contains both journals.

If you subsequently unpost the budget journal in Commitment Control and run the Commitment Control to Project Costing process, the system:

  • Resets the Project Costing Distribution Status field value for the journal row back to N (new) if the original Project Costing Distribution Status field for the row was D.

  • Modifies the status of the existing budget plan to Inactive.

  • Creates a new budget plan with an active status that represents the reversal of the previous budget plan.

    The new budget plan contains the same amounts as the previous plan but with the multiplier signs reversed.

  • Sends the new budget rows to the Project Transaction Interface table and Project Budgeting tables.

For example, assume that you post Journal A to Commitment Control and run the Commitment Control to Project Costing process. The process creates Budget Plan A as the active budget plan. Then you unpost Journal A in Commitment Control and run the Commitment Control to Project Costing process. The system changes the status of Budget Plan A to Inactive and creates Budget Plan B as the active budget plan, which represents the reversal of Budget Plan A.

If you create a budget journal in Commitment Control and run the Commitment Control to Project Costing process and if Projects Budgeting is enabled at the installation level and an active budget plan already exists in PeopleSoft Project Costing, then the system:

  • Modifies the status of the existing budget plan in PeopleSoft Project Costing to Inactive.

  • Creates a new budget plan in PeopleSoft Project Costing with an active status.

  • Sends the new budget rows to the Project Transaction Interface table and Project Budgeting tables.

  • Modifies the Project Costing Distribution Status field value for the journal row to D.

For example, assume that you post Journal A to Commitment Control and run the Commitment Control to Project Costing process. The process creates Budget Plan A as the active budget plan. Then you post Journal B and run the Commitment Control to Project Costing process. The system changes the status of Budget Plan A to Inactive, and creates Budget Plan B as the active budget plan.

You must define the project ID, activity ID, and Project Costing business unit as key ChartFields if you create budgets directly in Commitment Control and send them to Project Costing by using the Commitment Control to Project Costing process.

The Commitment Control to Project Costing process uses the analysis groups for the revenue budget and the cost budget that are specified on the Project Costing Definition page for the project. The process uses the first analysis type listed in the appropriate analysis group. For example, assume that you use the RBUD (Revenue Budget Group) analysis group for revenue budgets and the BUD (Budgets) analysis group for cost budgets. The analysis type RB1 (Revenue Budget 1) is listed first in the RBUD analysis group. Therefore, the process uses RB1 to post revenue budgets to the budget plan and the Project Transaction table.

When you generate a budget plan by using the Commitment Control to Project Costing process, the budget item default value is Other.

Note:

If you create a budget journal in Commitment Control and Projects Budgeting is enabled at the installation level, you cannot change the default budget item in the project budget. In this way the system prevents you from changing the budget item from Other to another value, which would result in changing the ChartField values to correspond to the new budget item.

If you create budgets in PeopleSoft Project Costing, you must also adjust the budgets in Project Costing.

If you create a new budget journal in Commitment Control and Projects Budgeting is not enabled at the installation level, the Commitment Control to Project Costing process sends transaction rows to the Project Transaction Interface table and does not create a budget plan.

Related Topics