Understanding Source Transaction Type Setup

Much of the documentation in this topic is for information only, and no modifications should be made to the pages unless stated otherwise. Any changes to most of the pages constitutes a customization and should be performed by a programmer with extensive experience in Oracle's PeopleSoft application code, usually with the help of PeopleSoft configuration experts.

For the Budget Processor to know how to process a source transaction, such as a purchase order or billing invoice, it needs to recognize the transaction as belonging to one of the source transaction types defined for Commitment Control.

Source transaction types define the following parameters:

• The commitment control amount type (pre-encumbrance, encumbrance, expenditure, and so forth) associated with the transaction type.

• The records and fields in which each type of transaction is stored.

• The source transaction temporary table used in the budget processor application engine program.

• The transaction type that gets referenced (for reversal or liquidation) by the transaction, along with the records and fields in which the referenced transaction is stored.

• The order in which source transactions of a type are processed.

  If nothing is specified, the Budget Processor processes the transaction based on the keys defined on the header record.

• The details required for the PeopleCode "Transfer()" function to perform page transfers from source transaction entry, inquiry, and adjustment pages to the appropriate budget exception handling pages, and vice versa.

• Criteria that enable the Budget Processor to select particular transactions for budget checking (such as purchase requisitions with a status code of open, approved, or cancelled).

• The source transaction record fields that the Budget Processor updates with the budget-checking status.

• The records and fields accessed to display source transaction information on budget exceptions pages and to provide links to the source transaction drill-down pages.

• Budgetary control options (control, control initial document, track with budget, track without budget, or default from higher level) and budget-checking override options for the transaction type.

• The option to update the Commitment Control Transaction Log to provide an audit trail of all budget-checking activity for the source transaction type.

• The option to skip monetary and budget attributes related edits for source transactions lines that have previously been budget checked and have a status of V or W; however, configuration related edits, such as ChartField not found in tree, are still logged.

These definitions appear on the Source Transactions component. Because these definitions depend on the data structure of other PeopleSoft applications, all but the budgetary control options, budget-checking override options, and transaction log option come predefined for each delivered source transaction type, and should not be changed except in special circumstances, such as when you configure Commitment Control to work with third-party source applications. You should therefore use the Source Transactions component primarily to review and familiarize yourself with the parameters that define each source transaction type.

However, you can freely change the budgetary control options, budget-checking override options, and transaction log option on the Options page without affecting other applications. The budgetary control options you select here override the options you set at higher levels in the control budget options hierarchy. Likewise, the budget-checking override options you select here can disable budget-checking override ability for a transaction type, even for users with override security access.