Commitment Control Detail Tracking Ledger Groups
Most organizations budget at a translated level that is higher than the source transactions that they budget check. Because the Budget Processor translates source transactions to the budgeted ChartField value level, standard Commitment Control ledger groups do not store transaction-level ChartField values for commitments. And although expenditure transactions are stored in the actuals or recording ledger with their untranslated, or transaction-level ChartFields, the pre-encumbrance and encumbrance transactions are not recorded in the actuals ledger at all.
To capture detail ledger rows and record transactions at an untranslated level for such nonactuals transactions, you define a commitment control ledger group as a detail ledger group by selecting the Commitment Detail Ledger check box on the Commitment Control Options page of the Ledger for a Unit component. Detail ledgers must also be set to the Track without Budget option on the Control Budget Options page. Tracking only is performed; no budget checking is done, no warnings are issued, and no validation of (RSA is performed for a detail ledger group.
Note:
No budget checking is done and no errors or warnings are issued for detail budget ledgers. This is the case even if control options might be set in the budget definition or budget attributes and even if the control option is set to control.
On the other hand, if the Track w/o Budget option is selected but the detail option is not selected for the budget ledger (it is not a detail ledger), the system checks to determine whether the budget row exists, and if so, perform budget checking and issue warnings.
When you budget check a transaction, the Budget Processor updates the ledgers in the standard Commitment Control ledger group at the translated level and the ledgers in the Commitment Control detail ledger group at the untranslated level. You can therefore inquire and report on nonactuals transactions at the detail level, without having to use the transaction activity logs.
For example, a requisition in the amount of 450 has Account 6842000, DeptID 615, Budget Period 2009Q2. Account 6842000 rolls up to Account 6840000 for budgeting. The Budget Processor updates the pre-encumbrance ledger for the expenditure control budget with the following ledger row: Account 6840000, DeptID 615, Budget Period 2009Q2, amount 450. It also updates the pre-encumbrance ledger in the detail ledger group with the following detail ledger row: Account 6842000, DeptID 615, Budget Period 2009Q2, amount 450.
Note:
If you use entry events with PeopleSoft Purchasing, the Entry Event Processor (FS_EVENTGEN) generates entry event accounting lines for pre-encumbrance and incumbrance Purchasing transactions by selecting transaction rows from the Commitment Control detail ledger group. Entry events generate accounting lines to record the pre-encumbrance and encumbrances in the actuals ledger. To facilitate this, you must select the Commitment Detail Ledger check box for the Commitment Control detail ledger group when you assign Commitment Control ledger groups to a business unit and GL ledger group in the Ledgers for a Unit component. The Entry Event Processor looks for this selection to identify the ledger group that contains pre-encumbrance and encumbrance transactions from Purchasing. Also note that funding source with entry event functionality is not supported.