PeopleSoft Enterprise Commitment Control 9.1 PeopleBook

Setting Up Commitment Control Source Transaction Types

This chapter provides an overview of source transaction type setup and discusses how to define source transaction types.

Understanding Source Transaction Type Setup

Much of the documentation in this chapter 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 Enterprise 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.

PeopleSoft delivers the following source transactions types specific to its enterprise applications:

Source Transaction Type	Description
AP_ACCT_LN	Voucher (gain, loss, close)
AP_ACCTDSE	Voucher (discount earned)
AP_VCHR_NP	Voucher (non-prorated item)
AP_VOUCHER	Voucher
AR_MISCPAY	Direct Journal Payments
AR_REVEST	Receivables
BI_INVOICE	Billing Invoice
CM_TRNXTN	Cost Management Transaction
EX_EXCLOSE	Close Expense Reports
EX_EXSHEET	Expense Sheet
EX_TRVAUTH	Travel Authorization
GENERIC	Generic Transaction
GL_BD_JRNL	General Ledger Budget Entry
GL_JOURNAL	General Ledger Journal
GM_FA	Facilities and Administration
GM_FA_UPG	Facilities and Administration (For Upgrade Budget Processor only)
HR_PAYROLL	Payroll Transaction
PC_BUDGET	Project Budget
PC_JOURNAL	Project Journal
PO_POENC	Purchase Order
PO_POENCNP	PO (non-prorated item)
PO_PROCARD	Procurement Card
PO_RAENC	Receipt Accruals - Encumbrance
PO_RAEXP	Receipt Accruals - Expense
REQ_PRECNP	Purchase Requisition - Non-prorated
REQ_PREENC	Purchase Requisition

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.

Warning! Do not add source transaction types or change the values in any of the Source Transactions component pages other than the Options page. Any changes that you make require corresponding changes to other tables and PeopleSoft applications. If you do need to change any of these values, the modifications should be performed only by programmers with extensive experience in PeopleSoft application code, usually with the help of PeopleSoft configuration experts.

Defining Source Transaction Types

To define source transaction types, use the Source Transaction Definition component (KK_SOURCE_TRAN).

In this section we discuss how to:

Define basic source transaction type parameters.
Define source transaction fields.
Define source transaction page transfers.
Define source transaction selection criteria.
Define source transaction status fields.
Define source transaction referenced record keys.
Define source transaction page events.
Define source transaction options.

Pages Used to Define Source Transaction Types

Page Name	Definition Name	Navigation	Usage
Source Transactions - Definition	KK_SOURCE_TRAN1	Commitment Control, Define Control Budgets, Source Transactions, Definition	Specify the Commitment Control source transaction amount type, the related reference transaction type, their header and line records, and the key record for the reference transaction type.
Source Transactions - Fields	KK_SOURCE_TRAN2	Commitment Control, Define Control Budgets, Source Transactions, Fields	Specify the source transaction header and line fields that the Budget Processor uses to perform budget checking and exception handling.
Source Transactions - Page Transfers	KK_SOURCE_TRAN3	Commitment Control, Define Control Budgets, Source Transactions, Page Transfers	Specify information about transfers between the originating source transaction pages and the budget exception handling pages. The values entered on this page allow for push-button transfer of information between the source transaction type's entry, inquiry, and adjustment pages and budget exception handling pages. These values indicate where the results of budget-checked transactions are transferred.
Source Transactions - Selection Criteria	KK_SOURCE_TRAN4	Commitment Control, Define Control Budgets, Source Transactions, Selection Criteria	Specify field name and field value criteria for selecting source transactions for budget-checking.
Source Transactions - Status Fields	KK_SOURCE_TRAN5	Commitment Control, Define Control Budgets, Source Transactions, Status Fields	Specify source transaction header fields to update with budget-checking results.
Source Transactions - Referenced Record Keys	KK_SOURCE_TRAN6	Commitment Control, Define Control Budgets, Source Transactions, Referenced Record Keys	Link identical key fields whose object names are different in the source transaction than they are in the reference transaction. Use this page when, for example, the name of a key field for purchase orders is different from the name of the same key field for referenced requisitions.
Source Transactions - Page Events	KK_SOURCE_TRAN7	Commitment Control, Define Control Budgets, Source Transactions, Page Events	Specify system data that enables exception handling and budget inquiry to display budget-checking results and source transaction information. Page events use common components and dynamic programs for exception handling. You can also define up to two source header fields that can be used as criteria filters in the activity log inquiry.
Source Transactions - Options	KK_SOURCE_TRAN8	Commitment Control, Define Control Budgets, Source Transactions, Options	Define budget-checking options for the source transaction type. Your choices override the Commitment Control options that you defined for control budget definitions, control ChartFields, and control budget attributes.

Defining Basic Source Transaction Type Parameters

Access the Source Transactions - Definition page (Commitment Control, Define Control Budgets, Source Transactions, Definition).

Commitment Control Amount Type

Determines which Commitment Control ledger is updated by the source transaction. It can be one of the following:

Actuals and Recognized: Actual amount of the expenditure or the recognized revenue. Transactions update the expense or recognized ledger, depending on the ledger group.

Actuals, Recognize and Collect: Amount of revenue booked and collected.

Budget: Amount of revenue budgeted.

Collected Revenue: Amount of revenue collected.

Dynamic: You specify the amount type when you enter the transaction. Applies to General Ledger journals.

Encumbrance: Amount of the funds that you are legally obligated to spend when you create a transaction, such as a contract or a purchase order. Not an actual transaction.

Planned: Amount that you plan to spend. This amount is only an estimate and not an actual transaction. You can also use it to record third-party source transactions that precede pre-encumbrance documents. The latter usage requires configuring an existing source transaction type or defining a new one.

Pre-Encumbrance: Amount that records the funds that you intend to expend but are not legally obligated to expend. This occurs, for example, when you create a requisition. It is not an actual transaction.

Note. With the exception of source transaction types that have been assigned the Dynamic amount type, a source transaction type always updates the Commitment Control ledger indicated by the Commitment Control amount type defined here. An accounts payable voucher, for example, updates the expense or recognized and collected ledgers, if the Commitment Control amount type defined for it is (as it should be) Actuals, Recognized and Collected.

Note. If the source transaction contains a line whose account value does not belong in the amount type assigned for the transaction (such as a revenue account in a purchase order transaction line, where purchase orders are defined as encumbrance amount types), the Budget Processor does not update the Commitment Control ledger table with that line.

Referenced Source Transaction

The transaction type that is reversed, in full or in part, when the transaction type defined on this page is processed.

For example, an encumbrance transaction (such as a purchase order) usually reverses a related pre-encumbrance (such as a purchase requisition). The amount of the pre-encumbrance's value that would be reversed when the encumbrance is processed depends on whether or not you use quantity or amount-based liquidation. You make that selection on the Ledgers for a Unit - Commitment Control Options page.

Header Record and Line Record

The Budget Processor uses these to select and process data for the source transaction type. The header and line records determine the prompts on the Fields page.

Update Header Record and Update Line Record

The Budget Processor updates the status fields on these records with the results of budget checking.

Note. The update header record and update line record are physical tables or they can be SQL views if they only reference a single table. The header record and line records may be views based on the same physical table as the update header record and update line record.

Referenced Record Key Record

The record that contains the key fields that link the source transaction to the record that contains the referenced source transaction. For example, for a source transaction type of Voucher, the DISTRIB_LINE record contains the key fields that link vouchers to the purchase orders stored in the PO_LINE_DISTRIB record.

The Referenced Record Key Record field field value is usually the same as the Update Line Record field value, but the Referenced Record Key Record field could point to a sibling table instead (for example, if you require requisitions for some purchase orders, but not for others).

The referenced record key record entered here determines the Source Transaction Field Names that prompt on the Referenced Record Keys page.

Source TAO Record

The temporary table used in the budget processor application engine program to store the source header and line data.

KK Source Header Record

This table stores the KK Source Header data that is specific to the source product. The record structure maintains the same key structure as the product header record which provides a better access path to the product information.

Note. The KK product header tables do not replace the KK source header (KK_SOURCE_HEADER).

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Fields

Access the Source Transactions - Fields page (Commitment Control, Define Control Budgets, Source Transactions, Fields).

The Budget Processor must know which source transaction header record fields and line record fields map to which Commitment Control fields.

The Commitment Control fields that map to fields on the source transaction header record are Accounting Date and the following:

Order By

The field that the Budget Processor uses to control the order (ascending) in which source documents are processed. If no Order By field is specified, the transactions are processed in the order of the fields defined as key fields on the "Header Record" which is specified on the "Definition" tab.

For example for AP_VOUCHER, the key fields on VOUCHER are BUSINESS_UNIT and VOUCHER_ID. If you do not specify a value in the "Order By" field, the Budget Processor orders by BUSINESS_UNIT and VOUCHER_ID.

The Commitment Control fields that map to fields on the source transaction line record are GL Business Unit (general ledger business unit), Budget Date, Base Currency, Monetary Amount, Foreign Currency, Foreign Amount, and the following fields:

Statistical Amount	The field that represents the transaction's quantity, as opposed to amount. This is used to calculate the amount to liquidate from the referenced transaction if quantity-based liquidation is used. If no statistical amount field is specified, monetary amount-based liquidation is used regardless of other option settings.
Closed Status	The field on the line record that defines whether the transaction is open or closed. When a transaction is closed, the Budget Processor liquidates all of its remaining unliquidated Commitment Control ledger amounts.
Closed Value	Closed Status field value that indicates the transaction has been closed.
Effective Date Lookup	This is the effective date field that is used to determine the effective date of the budget definition.
Quantity	Field used for statistical budgeting.

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Page Transfers

Access the Source Transactions - Page Transfers page (Commitment Control, Define Control Budgets, Source Transactions, Page Transfers).

This page indicates the parameters required to enable the dynamic use of the PeopleCode Transfer function for page transfers.

Page Transfer Identifier

Indicates the type of page to transfer to. The available types include:

To Exception Header: Exception handling header page specific to the source transaction.
To Exception Header SearchBox: Search dialog for the exception handling header page specific to the source transaction.
To Source Adjustment: Page where source transactions are corrected.
To Source Adjustment 2: Additional page where transactions are corrected.
To Source Entry: Page where the source transactions are entered.
To Source Entry 2: Additional page where transactions are entered.
To Source Inquiry: Page to inquire upon a source transaction.
To Source Inquiry 2: Additional page to inquire upon a source transaction.

Search Keys 01 through Search Key 10

Search keys to be used in the PeopleCode Transfer function. These prompt off of the fields available in the Source Transactions record (KK_SOURCE_TRAN).

The Menu Name, Menu Bar Name, Item Name, Panel Name, and Menu Action indicate the navigation to be used for the page transfer.

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Selection Criteria

Access the Source Transactions - Selection Criteria page (Commitment Control, Define Control Budgets, Source Transactions, Selection Criteria).

Indicate the Selection Criteria that the Budget Processor uses to select transactions for budget checking.

Use the Thru (through) check box to manipulate the operand for multiple selection criteria. If the Field Name on two adjacent lines is the same, but there is a different Field Value leave the check box on the second line deselected to indicate an OR operation between the two values. Select the Thru check box to indicate a range of field values.

If the field names on two or more adjacent lines are different, the system forces the Thru check box to be deselected, and an AND operation is in effect between the lines. Only transactions that meet the field name and field value conditions for both (or all) of the adjacent lines are selected for budget-checking.

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Status Fields

Access the Source Transactions - Status Fields page (Commitment Control, Define Control Budgets, Source Transactions, Status Fields).

For each source transaction header status field that you want updated by the results of budget checking, indicate the Field Name, Valid Value, and Error Value. The only values that you cannot alter are those for the BUDGET_HDR_STATUS (Budget Header Status) field, which the Budget Processor always populates with V (for valid) or E (for error).

If you enter only a Valid Value, the status field is updated only if there are no budget errors. If you enter only an Error Value, the status field is updated only if there are budget errors. If you enter both values, the field is populated by the results of the budget check.

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Referenced Record Keys

Access the Source Transactions - Referenced Record Keys page (Commitment Control, Define Control Budgets, Source Transactions, Referenced Record Keys).

To link two identical but differently named key fields that have to be referenced to one another, indicate the source transaction type's field under Source Transaction Field Name and indicate the referenced transaction key field name under Field Name. The value in the Referenced Record Key Record field on the Source Transactions - Definition page determines the prompts for the Source Transaction Field Name.

Note. Only in rare circumstances should these values be changed, and then only by programmers with extensive experience in PeopleSoft application code.

Defining Source Transaction Page Events

Access the Source Transactions - Page Events page (Commitment Control, Define Control Budgets, Source Transactions, Page Events).

The data displayed on this page enables exception handling to display the appropriate values for specific source transactions using common functions in the PeopleCode behind the exception and inquiry pages.

Source Header View	Links the source transaction header data with the Budget Processor header data.
Source Header ID Field Name	Represents the source transaction document for display purposes.
Source Header ID Label	Label for the Source Header ID field. For display purposes.
Source Lines View	Links the source transaction line data with Budget Processor line data.
Source Line # Prompt View	Used as % editable for the line field on the source transaction's Line Exceptions page.
Source Line # Field Name	Highest level line number field for the source transaction type.
Source Exception Line View	Links the source transaction line data with Budget Processor line data and budget exception data.
Source Drill Down Page	Displays source transaction line drill down page.
Message Number	Message catalog number for the displayed name for the source transaction line drill-down. System data ranges from #1022 to #1038 for the 17 source transaction types.
Message Set Number	Message catalog set for the drill-down page's displayed title (auto-defaulted to 18021).

Note. You should change these values only in rare circumstances. Only programmers with extensive experience in PeopleSoft application code should make changes to these values.

Activity Log Search Criteria

Selections for both the 1st Source Header ID Field and the 2nd Source Header ID Field are derived from the key fields of the Header Record that is defined on the Definition tab of the Source Transactions page. The values in the two fields must be different.

Select a value that corresponds to the field. Selections for 1st and 2nd Source Header ID Prompt are views that are delivered by PeopleSoft.

Note. The fields are referenced in the Page Events tab under activity log search criteria. The page is delivered configured and you usually will not change any of the setup. This information is provided for use only in the event that you want to change the search criteria.

When the data type of the Source Header ID field is either Date, Time or DateTime, the corresponding Source Header ID Prompt becomes disabled.

The following two tables list the delivered 1st and 2nd source header IDs and the prompt tables associated with them.

1st Source Header ID and Associated Prompt Tables

This table is a list of the 1st Source Header Field inquiry criteria and is the same as the value that is setup in the KK_PANEL_EVENT.KK_HEADER_ID_FIELD).

KK_SOURCE_TRAN	RECNAME_HEADER	KEYS OTHER THAN (BU AND HEADER ID)	VIEWS
AP_ACCT_LN	VCHR_ACT_HDR_VW	VOUCHER_ID	KK_ALOG_AP_VW
AP_ACCTDSE	VCHR_ACT_DSE_VW	VOUCHER_ID	KK_ALOG_AP_VW
AP_VCHR_NP	VCHR_HDR_NP_VW	VOUCHER_ID	KK_ALOG_AP_VW
AP_VOUCHER	VCHR_KK_VW	VOUCHER_ID	KK_ALOG_AP_VW
AR_MISCPAY	ARCC_PAY_HDR_VW	DEPOSIT_ID	KK_ALOG_ARM_VW
AR_REVEST	AR_CC_TRAN_VW	CUST_ID	KK_ALOG_ARR_VW
BI_INVOICE	BI_ACCT_KK_VW	INVOICE	KK_ALOG_BI_VW
CM_TRNXTN	CM_KK_HDR_VW	INV_ITEM_ID	KK_ALOG_CM_VW
EX_EXCLOSE	EX_SHEET_HDR	SHEET_ID	KK_ALOG_EXP1_VW
EX_EXSHEET	EX_SHEET_HDR	SHEET_ID	KK_ALOG_EXP1_VW
EX_TRVAUTH	EX_TAUTH_HDR	TRAVEL_AUTH_ID	KK_ALOG_EXP2_VW
GENERIC	COMCNTL_TRN_HDR	TRANS_NBR	KK_ALOG_GEN_VW
GL_JOURNAL	JRNL_HEADER	JOURNAL_ID	KK_ALOG_GL_VW
GL_BD_JRNL	KK_BUDGET_HDR	JOURNAL_ID	KK_ALOG_BD_VW
GM_FA	GM_PRJ_RHDR_VW	PROJECT_ID	KK_ALOG_GM_VW
GM_FA_UPG	GM_PRJ_RHDR_UPG	PROJECT_ID	KK_ALOG_GM_VW
HR_PAYROLL	HR_KK_HDR	RUN_DT	NA
PC_COLL	INTFC_PC_KK_VW	INTFC_ID	KK_ALOG_PC_VW
PC_ENC	INTFC_PC_KK_VW	INTFC_ID	KK_ALOG_PC_VW
PC_JOURNAL	INTFC_PC_KK_VW	INTFC_ID	KK_ALOG_PC_VW
PC_PREENC	INTFC_PC_KK_VW	INTFC_ID	KK_ALOG_PC_VW
PO_CCBATCH	CC_LINE1_TAO	EMPLID	KK_ALOG_PO4_VW
PO_PROCARD	CC_TRANS_LINE	EMPLID	KK_ALOG_PO4_VW
PO_POENC	PO_HDR	PO_ID	KK_ALOG_PO1_VW
PO_POENCNP	PO_HDR_NP	PO_ID	KK_ALOG_PO1_VW
PO_RAENC	RECV_ENC_HDR_VW	RECEIVER_ID	KK_ALOG_PO3_VW
PO_RAEXP	RECV_EXP_HDR_VW	RECEIVER_ID	KK_ALOG_PO3_VW
REQ_PRECNP	REQ_HDR_NP	REQ_ID	KK_ALOG_PO2_VW
REQ_PREENC	REQ_HDR_PR	REQ_ID	KK_ALOG_PO2_VW

2nd Source Header ID and Associated Prompt Tables

This table is a list of key fields for the 2nd Source Header ID. The first field that is listed under "KEYS OTHER THAN (BU AND HEADER ID) is delivered as the 2nd Source Header ID field. NONE indicates that there is no other key field.

KK_SOURCE_TRAN	RECNAME_HEADER	KEYS OTHER THAN (BU AND HEADER ID)	VIEWS
AP_ACCT_LN	VCHR_ACT_HDR_VW	NONE	NA
AP_ACCTDSE	VCHR_ACT_DSE_VW	NONE	NA
AP_VCHR_NP	VCHR_HDR_NP_VW	NONE	NA
AP_VOUCHER	VCHR_KK_VW	NONE	NA
AR_MISCPAY	ARCC_PAY_HDR_VW	DEPOSIT_BU PAYMENT_SEQ_NUM	KK_ALOG_ARM_VW1 KK_ALOG_ARM_VW2
AR_REVEST	AR_CC_TRAN_VW	ITEM ITEM_LINE ITEM_SEQ_NUM CC_GROUP_SEQ_NUM	KK_ALOG_ARR_VW1 KK_ALOG_ARR_VW2 KK_ALOG_ARR_VW3 KK_ALOG_ARR_VW4
BI_INVOICE	BI_ACCT_KK_VW	ACCOUNTING_DT	NA
CM_TRNXTN	CM_KK_HDR_VW	DT_TIMESTAMP SEQ_NBR	KK_ALOG_CM_VW_2
EX_EXCLOSE	EX_SHEET_HDR	NONE	NA
EX_EXSHEET	EX_SHEET_HDR	NONE	NA
EX_TRVAUTH	EX_TAUTH_HDR	NONE	NA
GENERIC	COMCNTL_TRN_HDR	TRANS_DT	NA
GL_JOURNAL	JRNL_HEADER	JOURNAL_DATE UNPOST_SEQ	KK_ALOG_GL_VW_2
GM_FA	GM_PRJ_RHDR_VW	ACTIVITY_ID RESOURCE_ID	KK_ALOG_GM_VW_1 KK_ALOG_GM_VW_2
GM_FA_UPG	GM_PRJ_RHDR_UPG	ACTIVITY_ID RESOURCE_ID	KK_ALOG_GM_VW_1 KK_ALOG_GM_VW_2
HR_PAYROLL	HR_KK_HDR	SEQNUM KK_AMOUNT_TYPE ACCOUNTING_DT	KK_ALOG_HR_VW_1 KK_ALOG_HR_VW_2
PC_COLL	INTFC_PC_KK_VW	KK_DISTRIB_STATUS PROCESS_INSTANCE	KK_ALOG_PC_VW_1 KK_PROC_INS_VW1
PC_ENC	INTFC_PC_KK_VW	KK_DISTRIB_STATUS PROCESS_INSTANCE	KK_ALOG_PC_VW_1 KK_PROC_INS_VW1
PC_JOURNAL	INTFC_PC_KK_VW	KK_DISTRIB_STATUS PROCESS_INSTANCE	KK_ALOG_PC_VW_1 KK_PROC_INS_VW1
PC_PREENC	INTFC_PC_KK_VW	KK_DISTRIB_STATUS PROCESS_INSTANCE	KK_ALOG_PC_VW_1 KK_PROC_INS_VW1
PO_CCBATCH	CC_LINE1_TAO	CREDIT_CARD_VENDOR CRDMEM_ACCT_NBR TRANS_NBR SEQUENCENO TRANS_DT LINE_NBR DTTM_STAMP	KK_ALOG_PO3_VW1 KK_ALOG_PO3_VW2 KK_ALOG_GEN_VW KK_ALOG_PO3_VW3 KK_ALOG_PO3_VW4
PO_POENC	PO_HDR	NONE	NA
PO_PROCARD	CC_TRANS_LINE	CREDIT_CARD_VENDOR CRDMEM_ACCT_NBR TRANS_NBR SEQUENCENO TRANS_DT LINE_NBR DTTM_STAMP	KK_ALOG_PO3_VW1 KK_ALOG_PO3_VW2 KK_ALOG_GEN_VW KK_ALOG_PO3_VW3 KK_ALOG_PO3_VW4
PO_RAENC	RECV_ENC_HDR_VW	RECV_LN_NBR RECV_SHIP_SEQ_NBR DISTRIB_LINE_NUM DST_ACCT_TYPE APPL_JRNL_ID ACCOUNTING_PERIOD FISCAL_YEAR ORIGINAL_TRANS DT_TIMESTAMP	KK_ALOG_PO4_VW1 KK_ALOG_PO4_VW2 KK_ALOG_PO4_VW3 KK_ALOG_PO4_VW4 KK_ALOG_PO4_VW5 KK_ALOG_PO4_VW6 KK_ALOG_PO4_VW7 KK_ALOG_PO4_VW8
PO_RAEXP	RECV_EXP_HDR_VW	RECV_LN_NBR RECV_SHIP_SEQ_NBR DISTRIB_LINE_NUM DST_ACCT_TYPE APPL_JRNL_ID ACCOUNTING_PERIOD FISCAL_YEAR ORIGINAL_TRANS DT_TIMESTAMP	KK_ALOG_PO4_VW1 KK_ALOG_PO4_VW2 KK_ALOG_PO4_VW3 KK_ALOG_PO4_VW4 KK_ALOG_PO4_VW5 KK_ALOG_PO4_VW6 KK_ALOG_PO4_VW7 KK_ALOG_PO4_VW8
REQ_PRECNP	REQ_HDR_NP	NONE	NA
REQ_PREENC	REQ_HDR_PR	NONE	NA

Defining Source Transaction Options

Access the Source Transactions - Options page (Commitment Control, Define Control Budgets, Source Transactions, Options).

Note. You can adjust the field values on this page at any time. The selections you make here for the commitment control option override the options you selected at the budget attributes, control ChartField, or control budget definition.

Commitment Control Option	Select the degree of budgetary control: Control: Transactions that cause budget exceptions generate errors or warnings. Control Initial Document: Control expenditures against the initial document only. Transactions are stopped and error messages issued only if budget constraints would be exceeded when the initial document is processed. Transactions that pass budget checking on the initial document, such as a purchase requisition, are automatically passed on all subsequent documents, such as a purchase order or payment voucher, even if budget constraints are exceeded at the time they are processed. Default from Higher Level: Commitment Control is set to default from a higher level, such as the budget attributes, control ChartField, or control budget definition level. Track w/o Budget (Tracking without Budget): Track transactions even if there is no budget set up. If a budget row exists and there are exceptions, issue warnings. Also Track. Tracking w/ Budget (Tracking with Budget): Track transaction amounts against a budget but do not issue error exceptions unless there is no corresponding budget row. Pass if budget row exists, even for a zero amount, but issue warnings for exceptions.
Override Budg Checking Option (override budget checking option)	Allow Override: Select to allow users with override security access to pass a transaction manually if it failed budget checking. Do not Allow Override: Select to make this transaction type inaccessible to any budget or transaction override. This is only effective if the override event is inactive within commitment control security. Note. Override budget checking option is only applicable when commitment control security for the override event is notactive. When you are using commitment control security for the override event, the setting for this option is not evaluated. Only the commitment control security rules are evaluated to determine whether a user can override a budget checking exception. If you are not using commitment control security, then this field is evaluated and when set to Allow Override, the user is permitted to override budget exceptions that are considered overridable. The list of overridable versus non-overridable exceptions is in the Managing Budget Exceptions chapter. See Managing Budget Exceptions.
Update Transaction Log	Select a value to determine whether the source transaction type updates the Commitment Control Transaction Log (KK_TRANS_LOG). The Commitment Control Transaction Log provides the ability to track historical budget-checking activity at the untranslated document level. This table records all successful budget-checking transactions sequentially, including reversal entries. For example, if you budget check a purchase order with Fund 100 and then change the Fund to 200 and re-budget-check the purchase order, you can use the Commitment Control Transaction Log to see this history. Each time you budget-check a transaction, a sequence number on the record increments by 1. You can use the Commitment Control Transaction Log table in conjunction with data in the KK_SOURCE_HDR table, the KK_SOURCE_LN table, and the KK_ACTIVITY_LOG table to research historical activity, reconcile discrepancies, and attest to the accuracy of accounting data maintained within the Commitment Control ledgers.
Skip Budget Processor Edits	Select one of these values to determine whether source transaction lines that have a budget line status of V or W coming into the budget checking process undergo budget attribute edit and budget checking routines. These are the monetary and budget attributes related edits. Configuration related edits, such as edits for ChartFields not in the tree or budget definition not found continue to be logged. Do not re-edit valid lines Re-edit valid lines Because Purchasing and Expenses are the only products that manage the budget line status field on documents, this option is displayed for only the Source Transaction Definitions listed below: PO_POENC PO_POENCNP REQ_PREENC For all other definitions, the field is not available on the page and the systems defaults to Re-edit valid lines. If the ChartFields, amounts, or dates associated with a source line are changed, the budget line status is changed to N so that the line is rechecked. Note. Valid lines are still picked up and processed by the budget processor. This feature simply suppresses the Budget Attribute and Budget Checking related exceptions. Any setup related errors associated with the source lines is still logged. For example: The Budget is Closed and the Budget Date is Out of Bounds exceptions are suppressed. However, setup related errors, such as the account is not defined in the translation tree or a budget definition could not be found is logged.

Commitment Control Amount Type	Determines which Commitment Control ledger is updated by the source transaction. It can be one of the following: Actuals and Recognized: Actual amount of the expenditure or the recognized revenue. Transactions update the expense or recognized ledger, depending on the ledger group. Actuals, Recognize and Collect: Amount of revenue booked and collected. Budget: Amount of revenue budgeted. Collected Revenue: Amount of revenue collected. Dynamic: You specify the amount type when you enter the transaction. Applies to General Ledger journals. Encumbrance: Amount of the funds that you are legally obligated to spend when you create a transaction, such as a contract or a purchase order. Not an actual transaction. Planned: Amount that you plan to spend. This amount is only an estimate and not an actual transaction. You can also use it to record third-party source transactions that precede pre-encumbrance documents. The latter usage requires configuring an existing source transaction type or defining a new one. Pre-Encumbrance: Amount that records the funds that you intend to expend but are not legally obligated to expend. This occurs, for example, when you create a requisition. It is not an actual transaction. Note. With the exception of source transaction types that have been assigned the Dynamic amount type, a source transaction type always updates the Commitment Control ledger indicated by the Commitment Control amount type defined here. An accounts payable voucher, for example, updates the expense or recognized and collected ledgers, if the Commitment Control amount type defined for it is (as it should be) Actuals, Recognized and Collected. Note. If the source transaction contains a line whose account value does not belong in the amount type assigned for the transaction (such as a revenue account in a purchase order transaction line, where purchase orders are defined as encumbrance amount types), the Budget Processor does not update the Commitment Control ledger table with that line.
Referenced Source Transaction	The transaction type that is reversed, in full or in part, when the transaction type defined on this page is processed. For example, an encumbrance transaction (such as a purchase order) usually reverses a related pre-encumbrance (such as a purchase requisition). The amount of the pre-encumbrance's value that would be reversed when the encumbrance is processed depends on whether or not you use quantity or amount-based liquidation. You make that selection on the Ledgers for a Unit - Commitment Control Options page.
Header Record and Line Record	The Budget Processor uses these to select and process data for the source transaction type. The header and line records determine the prompts on the Fields page.
Update Header Record and Update Line Record	The Budget Processor updates the status fields on these records with the results of budget checking.