Underlying Data Structure of PeopleSoft Commitment Control

Commitment Control uses the ledger and ledger group structure of General Ledger to store control budgets in the Commitment Control Ledger Data table (LEDGER_KK). Each control budget definition (or set of budgets sharing the same rules) is defined in the system as a Commitment Control ledger group consisting of Commitment Control ledgers, each of which stores a different amount type, such as pre-encumbrance, encumbrance, and expenditure.

A simple organization might have the following budget configuration:

• An expenditure Commitment Control ledger group consisting of a budget ledger, pre-encumbrance ledger, encumbrance ledger, and expenditure ledger.

  That is to say, it consists of a ledger for control budget amounts and a ledger for each transaction amount type you process against your control budgets as shown in the following table:

  Ledger Group	Budget Ledger	Pre-encumbr Ledger	Encumbr Ledger	Expenditure Ledger
  ORG	ORG_BUD	ORG_PRE	ORG_ENC	ORG_EXP

  Some expenditure ledger groups may also include a planned ledger, which can be used for planned expenditures that have not yet solidified to the point of the need for the issuing of a requisition.

• A revenue Commitment Control ledger group consisting of a revenue estimate budget ledger, a revenue recognized ledger, and a revenue collected ledger, as shown in the following table:

  Ledger Group	Budget Ledger	Recognized Ledger	Collected Ledger
  REVEST	REVEST_BUD	REVEST_REC	REVEST_COL

In other words, within a control budget definition, each amount type has its own bucket, and this structure is reflected in the ledger group and ledger structure.

The way control budget data is actually stored in the Commitment Control Ledger Data table is similar to this example:

Ledger	Fiscal Year	Acct Period	Fund	Account	DeptID	Budget Period	Posted Total Amt
ORG_BUD	2009	1	100	50000	1000	2009	100000
ORG_PRE	2009	1	100	50000	1000	2009	30000
ORG_ENC	2009	3	100	50000	1000	2009	50000
ORG_EXP	2009	3	100	50000	1000	2009	25000
REVEST_BUD	2009	1	100	40000	1000	2009	125000
REVEST_REC	2009	1	100	40000	1000	2009	30000
REVEST_COL	2009	2	100	40000	1000	2009	50000

Each time a budget-checked transaction updates the Commitment Control Ledger Data table, it updates the posted total amount.

Note:

The remaining available budget balance is not a stored amount, but is calculated when you run budget checking.

Using the ledger table structure in General Ledger for Commitment Control setup enables you to take advantage of other General Ledger processes, such as revaluation, ChartField translation, allocations, and summary ledgers. However, be aware that Commitment Control ledgers and ledger groups do not function in all respects as do General Ledger detail ledgers and ledger groups.

Commitment Control documentation often uses synonymously the terms amount type and ledger.

Also, the Commitment Control Ledger Data table at times is referred to as the Commitment Control ledger or budget ledger. It is important to remember these distinctions, as well as the synonymous use of these terms when a particular aspect of Commitment Control budget is being discussed.

Note:

Ledgers defined by the Commitment Control ledger template can have different sets of ChartFields than do General Ledger detail ledgers. These can include General Ledger and Projects ChartFields, as well as the Budget Period ChartField.