PeopleSoft Receivables 9.1 PeopleBook

Using Commitment Control Processing in PeopleSoft Receivables

This chapter provides an overview of revenue estimate processing, lists prerequisites, and discusses how to perform commitment control processing in PeopleSoft Receivables.

Understanding Revenue Estimate Processing

This section discusses:

Revenue estimate processing.
The Revenue Estimate Application Engine process (AR_REV_EST).
Special condition handling during the Revenue Estimate process.

Revenue Estimate Processing

The role of PeopleSoft Receivables in the commitment control process is to create source transactions for the revenue entries in the control budgets. A budget in PeopleSoft Receivables is a fixed income allocation (that is, a revenue estimate) with two monetary buckets: a recognized revenue bucket and a collected revenue bucket. Recognized revenue is revenue that has been billed to the customer but for which payment has not yet been received. It is open receivables. Collected revenue is cash that has been received as payment. The combined amounts should eventually match the total estimated amount, which is your budget.

Most receivable functions that you perform update one of the two revenue buckets. In some cases, they update both. This diagram demonstrates that the functions create a debit memo, a credit memo, ITEM match items, a write-off credit item, a write-off debit item, an earned discount, and an unearned discount, all of which update the recognized revenue bucket. Direct journal entries, match cash items, and item payments update the collected revenue bucket.

Recognized and collected revenue bucket updates by Receivables functions

You run the following processes to update the control budgets:

The Revenue Estimate process, which creates the source transactions for the control budget ledger for all activity except direct journals.
The Budget Processor Application Engine process (FS_BP), which updates the revenue buckets and creates the commitment control budget lines.

The Receivable Update Application Engine process (ARUPDATE) automatically runs the Revenue Estimate process and Budget Processor when it completes if you enabled commitment control for PeopleSoft Receivables. If you have errors in the source transaction or budget checking errors, then you must run the Budget Processor after you correct the errors. If you choose to delete the activity's source transactions, then you must rerun the Revenue Estimate process before you run the Budget Processor again. You only need to rerun these processes if you have corrected errors.

Note. The Revenue Estimate process does not change the distribution of PeopleSoft Receivables accounting entries in PeopleSoft General Ledger. If you enabled commitment control for PeopleSoft Receivables and for the general ledger business unit associated with the receivables business unit, then you must budget check the entries before you distribute them to PeopleSoft General Ledger.

The Revenue Estimate Application Engine Process

The Revenue Estimate process uses the revenue accounting lines in the Item Distribution (PS_ITEM_DST) table to generate the source transactions for the control budget ledger. It generates one source transaction for each revenue line. If the activity does not generate a revenue line, the Revenue Estimate process searches the preceding activity for a revenue account and follows these rules:

If the activity is a Create a Debit Memo (IT-01), Create a Credit Memo (IT-02), or Create an Overdue Charge (FC-01) activity, the process uses the revenue account for that activity.

If it cannot find a revenue account, then the transaction causes an error. Enter the revenue account manually on the Revenue Estimate Correction page.
If the activity is a Transfer Item to Customer (TR-02) activity and the item was transferred to a customer in the same business unit, the process uses the revenue account of the from item.
If the item is system-generated (for example, an underpayment or an overpayment), then no revenue account exists and the process does not generate a source transaction.

When you create the write-off for an underpayment or overpayment, the system updates the revenue buckets.

Special Condition Handling During the Revenue Estimate Process

This section describes how the Revenue Estimate process generates source transactions for these special conditions:

Overpayments.
Underpayments.
Prepayments.
Draft processing.
Write-offs on maintenance worksheets and in automatic maintenance.
Source transactions for PeopleSoft Billing and PeopleSoft Contracts items.
Directly journaled payments.
Realized gains and losses.
Unpost groups.
Items with value-added tax (VAT).
Multiple revenue lines.

Overpayments

If you have an overpayment (MT-05, WS-04, WS-05, or WS-06 item activities) and you leave the cash or credit on-account, the process does not create source transactions for the overpayment amount. When you apply the remaining cash or credit to an item, it updates the collected revenue bucket. However, if you write off an overpayment, the process updates both the recognized and collected revenue buckets.

Here is an example of revenue estimate entries for on-account overpayments:

Transaction	Recognized	Collected
Original 100.00 item	–100.00
110.00 payment		–100.00

Here is an example of revenue estimate entries for writing off an overpayment:

Transaction	Recognized	Collected
Original 100.00 item	–100.00
110.00 payment		–100.00
Write-off of 10.00	–10.00	–10.00

Note. You cannot combine cash and a credit memo when you create an overpayment. If you have an overpayment, the entire amount should come from cash or the entire amount should come from a credit memo. This is necessary because the system updates the buckets differently depending on whether the overpayment is from cash or a credit memo. If you combine them, it cannot determine how to update the buckets.

Underpayments

If you have an underpayment and you pay off the item and create an adjustment item, the process updates the collected revenue bucket with the full item amount at that time. When you pay for the adjustment of the item, the system does not create any further source transactions.

Here is an example of revenue estimate entries for an underpayment with an adjustment:

Transaction	Recognized	Collected
Original 100.00 item	–100.00
90.00 payment and 10.00 adjustment		–100.00
Apply 10.00 payment to the adjustment	No entries

When you have an underpayment and you write off the remainder of the item, the process creates one source transaction that updates the collected revenue bucket for the amount of the payment. It also creates another source transaction that debits the recognized bucket for the write-off.

Here is an example of revenue estimate entries for an underpayment and a write off:

Transaction	Recognized	Collected
Original 100.00 item	–100.00
90.00 payment		–90.00
10.00 write-off item	10.00

Prepayments

When you create the prepayment item (WS-04), the Revenue Estimate process does not create source transactions for the control budget. When you create the IT-01 item for the prepayment, the Revenue Estimate process generates the source transactions that update both the collected and the recognized bucket. It uses the accounts from the new item to create the entries.

Here is an example of revenue estimate entries for a prepayment:

Transaction	Recognized	Collected
100.00 Prepayment (WS-04)
100.00 Item (IT-01)	–100.00	–100.00

If you create prepayments using the draft worksheet, the process is the same except that it does not create the source transactions when you create the IT-01 item if the cash for the draft has not been recognized yet. When the cash is recognized at the discount date or at the due date, the process looks to see if an IT-01 item already exists for the prepayment and generates the source transactions. If you void, dishonor, or cancel the remittance for a draft with prepayments, the process reverses transactions only if the prepayment was already applied to an item.

Draft Processing

When the process creates source transactions for the Pay an Item (DM-01), Write-off an Overpayment (DM-08), and Write-off an Underpayment (DM-09) activities on the draft worksheet, it places them in two holding tables (PS_ARCC_HLDTRN_HDR and PS_ARCC_HLDTRN_TBL) until the cash is recognized for the draft. When the cash is recognized either at the discount date or at the due date, it moves the source transactions from the holding tables to the application tables (PS_AR_CC_TRAN_HDR and PS_AR_CC_TRAN_TBL) that hold the source transactions for budget processing.

The process also uses the holding tables when you void or dishonor a draft or when you cancel a draft remittance.

Write-offs on Maintenance Worksheets and in Automatic Maintenance

If you write off an item on a maintenance worksheet or if the Automatic Maintenance Application Engine process (AR_AUTOMNT) writes off an item, the system uses the reason for the write-off item to determine which bucket to update. You define which buckets to update in the automatic entry type for the write-off system functions for maintenance groups.

Source Transactions for PeopleSoft Billing and PeopleSoft Contracts Items

If you enter your invoices (IT-01 or IT-02 items) in PeopleSoft Billing, PeopleSoft Receivables creates the source transactions for them in the recognized revenue bucket as long as PeopleSoft Receivables generates the accounting entries. When PeopleSoft Billing creates the accounting entries, PeopleSoft Receivables does not create the source transactions to update the recognized bucket. You must create the source transactions in PeopleSoft Billing.

If PeopleSoft Billing is creating the accounting entries, to enable PeopleSoft Receivables to process payments against items coming from PeopleSoft Billing or PeopleSoft Contracts/Projects, you must run the Load GL Accounting Entries process (BILDGL01) in PeopleSoft Billing, which performs budget checking. If the invoice is not budget checked prior to coming into PeopleSoft Receivables, then PeopleSoft Receivables issues an error message on the payment worksheet indicating that the item has not successfully passed budget checking.

When you a apply payment to an item interfaced from PeopleSoft Billing that has been budget checked, the Revenue Estimate process uses the revenue lines in the PeopleSoft Billing accounting entry table (PS_BI_ACCT_ENTRY) to generate the source transactions for the collected bucket.

When an invoice comes from PeopleSoft Contracts/Projects and PeopleSoft Contracts manages the revenue, even if the invoice was budget checked successfully, if you did not run the Load GL process in Billing then the PeopleSoft Receivables Revenue Estimate process will skip the transaction when processing a payment.

When an item has an associated contract line in PeopleSoft Contracts, then the Revenue Estimate process uses the revenue lines that reside on the PeopleSoft Contracts accounting line tables. PeopleSoft General Ledger updates and budget checks the recognized revenue lines for the budget when you post the PeopleSoft Contracts journals in PeopleSoft General Ledger. The process looks for the revenue lines in these tables to populate the revenue collected bucket:

Contracts Accounting Line Projects table (PS_CA_ACCTG_LN_PC), which contains the revenue lines for rate-based contracts.
Contracts Accounting Line table (PS_CA_ACCTG_LINE), which contains the revenue lines for amount based contracts.

The process uses the most recent revenue entry that was posted for the contract line in the Contracts Accounting Line table (PS_CA_ACCTG_LINE). You should use the same revenue distribution lines for amount-based contracts throughout the life of the contract. At least one revenue event must be posted in PeopleSoft Contracts before you apply the first payment to the item associated with the contract line. If there are no posted revenue lines for the contract line, the process does not update the collected revenue bucket and the process generates an error message.

If you receive an error, you should post some revenue lines for the contract line in PeopleSoft Contracts and then rerun the Revenue Estimate process.

Directly Journaled Payments

When you journal a payment directly to the general ledger, the system uses the information in the PS_PAY_MISC_DST table to update the recognized and collected buckets. No source transactions for direct journals will appear in the revenue estimate tables: PS_AR_CC_TRAN_HDR and PS_AR_CC_TRAN_TBL. Therefore, you do not need to run the Revenue Estimate process for directly journaled payments.

Realized Gains and Losses

If you apply a payment to an item in a foreign currency and either a realized gain or loss exists, then the process creates an additional transaction to adjust the amount in the collected bucket.

Here is an example of revenue estimate entries for a transaction with realized gain or loss:

Transaction	Recognized	Collected
Original Item	–100.00
Payment		–100.00
Realized Gain or Loss		2.00

Unpost Groups

When you unpost a group, the Revenue Estimate process creates source transactions to reverse the original entries in the revenue budget.

Items with VAT

If an item contains a VAT amount or sales tax, only the base amount of the transaction updates the revenue buckets. For example, if the total item is 108.00 EUR and the VAT amount is 8.00 EUR, then the process updates the revenue budgets with 100.00 EUR.

Multiple Revenue Lines

If an item has multiple revenue lines and it is completely paid by one payment, the system uses the same amounts for each revenue account as the original revenue lines.

If an item has multiple revenue lines and you make a partial payment, the system provides a page in the worksheet components where you can specify how to distribute the revenue amount. This page is available only if you selected Allow Manual Distribution in the Multiple Revenue Line field for the business unit. If you do not enable manual distribution, the system automatically prorates the payment amount across the remaining revenue balances.

Prerequisites

Before you can run the revenue estimate processes, you must perform the following tasks:

Enable commitment control accounting for PeopleSoft Receivables on the Installation Options - Installed Products page.
Set up the system for commitment control accounting.
Review the source transaction definition for the commitment control transactions for the Revenue Estimate process and for direct journal payments.
If the system function for an item entry type specifies that the revenue estimate bucket is user-defined, specify which bucket to update for each entry reason.
If the system function for an automatic entry type specifies that the revenue estimate bucket is user-defined, specify which bucket to update for each entry reason.
Make sure the user-defined accounting lines (revenue lines) contain ChartFields in the control budget ledger.
Define the defaults for revenue estimate processing for each business unit by TableSet on the Receivables Options - General 2 page.
Disable PeopleSoft Billing and PeopleSoft Contracts on the Installed Products page if you do not have those products installed on your system.

Disabling these products improves performance because the Revenue Estimate process does not search records in PeopleSoft Billing or PeopleSoft Contracts for revenue lines.

Defining Additional General Options

Defining Options for Installed PeopleSoft Applications

Setting Up Basic Commitment Control Options

Setting Up Commitment Control Source Transaction Types

Performing Commitment Control Processing

This section provides overviews of the commitment control process flow and of budget checking error correction and warnings, lists common elements, and discusses how to:

Review revenue estimate entries.
Correct revenue estimate errors.
Run the Revenue Estimate process.
Run the Budget Processor.
View budget checking exceptions for revenue estimate source transactions.
View direct journal exceptions.

Understanding the Commitment Control Process Flow

Perform these tasks for revenue estimate and budget checking processing:

Note. These steps do not apply to direct journal payments.

Run the Receivable Update process to post groups, create accounting entries, create the source transactions, and budget check the source transactions.

Note. The Receivables Update process runs the Revenue Estimate process and budget checks the transactions only if you have enabled commitment control for PeopleSoft Receivables and the general ledger business unit associated with the receivables business unit.
(Optional) Review the source transactions.
Correct errors in the source transactions if needed.

For example, you might post some revenue lines for a contract line in PeopleSoft Contracts.
Run the Revenue Estimate process again if you corrected errors in source transactions.

In some cases, you need to unpost the original group and correct the accounting lines. If this is the case, you run the Receivable Update process to post the group again and it automatically runs the Revenue Estimate process.

See Understanding Budget Checking Error Correction and Warnings.

Note. You can run the Budget Processor process at the same time if you do not want to review the source transactions before you budget check the transactions.
Run the Budget Processor process again if you corrected errors in the source transactions.
View budget checking errors and warning exceptions and resolve them.
Run the Budget Processor again if you corrected errors or overrode the exceptions.

Journaling Payments Directly to the General Ledger

Understanding Budget Checking Error Correction and Warnings

Transactions typically fail the budget checking process because the amount of the source transactions exceeds the amount in the control budget and the commitment control option for the budget. If this occurs, you have two options:

Credit the revenue estimate budget amount.
Mark the entire transaction to bypass budget checking on the Commitment Control, Revenue Estimate Exceptions, or Misc Payment Exceptions page for the transaction.

After you mark it, you must run the Budget Processor process again.

A transaction could also fail because you provided a revenue account that is not in the revenue estimate budget. If this is the case, you need to perform the following tasks:

Set the group that included the source transactions to unpost.
Run the Receivable Update process, which reruns the Revenue Estimate process and the Budget Processor.

The Revenue Estimate process deletes the source transactions and does not create new sources transactions.
Recreate the items with the correct data.
Run the Receivable Update process again, which reruns the Revenue Estimate process and the Budget Processor.

If you run the Budget Processor when you run the Receivable Update process or from the Budget Processor page, use the message log to see if you have received any warnings. Alternatively, go directly to the budget exception pages to see if you have any warnings. Select Only Warnings Exist in the Process Status field, when you search for exceptions to display only transactions with warnings.

If you budget check transactions from an online page, such as the Direct Journal Payments - Accounting Entries page or the Corrections page for the Revenue Estimate process, the system displays a warning message for any type of warning including the warning for negative expense budgets. Users must go to the appropriate budget exceptions page to determine the type of warning. If there is a warning status at the line level, you can drill directly down to the warning on the exception page by clicking the Budget Check Options button.

Note. You receive the warning message when you budget check transactions online only if you selected the Pop Up Error/Warning Message check box on the Installation Options - Commitment Control page.

See Also

Unposting Groups

Running Receivable Update

Defining PeopleSoft Receivables Processing Options

Running the Revenue Estimate Process

Running the Budget Processor

Entering and Posting Commitment Control Budget Journals

Common Elements Used in This Section

	Click the Revenue Line Source button to access the accounting entries inquiry page, where you can review the original accounting entries for the item activity. Note. This option is not available for transactions with errors on the Revenue Estimate Correction page.
Accounting Date	Displays the accounting date for the item activity.
Amount and Base Amount (for all source transactions)	Displays the total amount of the source transactions for the item in the entry currency and the base currency.
Amount (for a single source transaction)	Displays the entry amount and currency of the item activity.
Base Amount (for a single source transaction)	Displays the base amount and currency of the item activity.
Budget Date	Displays the default budget date for entries to the recognized bucket is the accounting date for the item. Although you can change the budget date, we recommend that you do not in order to keep the entries in the control budget ledger synchronized with the entries to the actual ledger. For entries to the collected bucket, the default varies based on your selection on the Receivables Options - General 2 page for synchronizing budget dates. If you selected Yes, the date for entries to the collected bucket matches the date for entries to the recognized bucket for the item. Otherwise, it is the accounting date for the current transaction. We recommend that the budget date for entries to the two buckets be the same so that the entries fall in the same budget period.
Budget Status (for all activity source transactions)	Displays the status of all the source transactions in the budget checking process. Values are: Error: At least one of the source transactions failed to pass budget checking. Not Chk'd (not checked): The Budget Processor has not processed the source transactions. Valid: All the source transactions passed budget checking and the process created the journal lines in the ledger.
Budget Status (for a single source transaction)	Displays the status of a single budget line entry. Values are: Error: The budget line failed to pass budget checking. Not Chk'd (not checked): The Budget Processor has not processed the line. Valid: The budget line passed budget checking and the process created the journal line in the ledger. Warning: The Budget Processor issued a warning for a line, but also updated the control budget ledger.
Entry Type and Reason	Displays the entry type and reason that you assigned to the item activity.
GL Unit	Displays the general ledger unit that is linked to the receivables business unit for the item.
Group Unit, Group ID, and Group Type	Displays the business unit and ID for the group, and the group type for the item activity.
Ledger Grp (ledger group) and Ledger	Displays the General ledger group and ledger for the entries. These values appear only if the process created multibook entries.
Posted Date	Displays the date that you posted the item activity.
Rev Estimate (revenue estimate)	Indicates whether the source transactions for the item activity updated the Collected, Recognized, or Both buckets.
Sequence	Displays the sequence number for the item in the item group.
Status	Indicates whether source transactions passed the revenue estimate process successfully or if they were in error. If an error exists, the Status field displays the reason. Values are: Corrected: You corrected the source transactions on the Revenue Estimate Correction page. Error: A source transaction has an unknown error. Gen by BI (generated by billing): The process did not find revenue lines for invoices, credit memos, debit memos, or overdue charge invoices (IT-01, IT-02, or FC-01 activities) in the PS_ITEM_DST table, but it found them in the PS_BI_ACCT_ENTRY table. The process does not need to generate the source transactions because PeopleSoft Billing generates them for the recognized revenue bucket. Out of BU (out of business unit): The process could not create the source transactions because the item was transferred out of the business unit. The accounts were not available to update. Processed: The process successfully generated source transactions for the item. No Itm Rev (no item revenue lines): The process could not create the source transactions because no item revenue lines were associated with the current item activity or with the previous item activity. Transferred: The process could not create the source transactions because it could not find the from item for a transferred item. (The process obtains the revenue accounts from the from item.) No Rev: The process could not create the source transactions because no user-defined revenue lines were set up for the item entry type or automatic entry type that you associated with the system function. Skip: The system skips the request when the process runs. Err Exists (error exists): The process could not create the source transactions because an error exists in a previous activity that affects the current activity. Correct the errors and run the process again.
View/Update Conversations	Click this link to access the Conversations page, where you can view and update existing conversations associated with the item. If there are multiple conversations, you can select the conversation you want to view or update on the View/Update Conversations search page. You can also add, delete, or edit existing conversation entries on the Conversations page.

Pages Used for Commitment Control Processing

Page Name	Definition Name	Navigation	Usage
Revenue Estimate Review	AR_CC_TRAN	Accounts Receivable, Receivables Update, Revenue Estimates, Review Transactions by Item, Revenue Estimate Review	View source transactions that the Revenue Estimate process created for all activities for an item. You can view both completed transactions and transactions with errors. However, you can change only the budget date for the transactions.
Revenue Estimate by Activity	AR_CC_TRAN_ACT	Accounts Receivable, Receivables Update, Revenue Estimates, Review Trans by Activity, Revenue Estimate by Activity	View source transactions that the Revenue Estimate process created for a single item activity. You can view both completed transactions and transactions with errors. However, you can change only the budget date for the transactions.
Revenue Estimate Correction	AR_CC_TRAN_ERROR	Accounts Receivable, Receivables Update, Revenue Estimate, Correct Transactions, Revenue Estimate Correction	Correct source transactions for the commitment control ledger that have errors. You can also flag the transactions to bypass budget checking before you process them or if they fail budget checking.
Revenue Estimate	REV_EST_REQUEST	Accounts Receivable, Receivables Update, Revenue Estimates, Create Transactions, Revenue Estimate	Recreate the source transactions for the control budget and optionally budget check the transactions.
Budget Processor	AR_CC_REQUEST	Accounts Receivable, Receivables Update, Revenue Estimates, Budget Check Transactions, Budget Processor	Rerun the Budget Processor process independently of the Revenue Estimate process.
Revenue Estimate Exceptions	KK_XCP_HDR_AR1	Commitment Control, Review Budget Check Exceptions, Revenues, Revenue Estimate, Revenue Estimate Exceptions	View budget checking errors or warning exceptions for receivables source transactions. Users who have authority can also override the budget error exceptions.
Refine Inquiry Criteria (transaction exceptions)	KK_XCP_TR_ADV_SEC	Click Advanced Budget Criteria on the Revenue Estimate Exceptions or Misc Payment Exceptions pages.	Refine selection criteria for budgets to view.
Commitment Control	KK_XCP_TRAN_SEC	Click the Budget Check Details button on the Revenue Estimate Exceptions or the Misc Payment Exceptions pages.	View details about a source transaction with exceptions, including the amount type and override information.
Receivables Revenue Estimate Line Drill Down	KK_DRL_AR1_SEC	Click the View Exception Details button on the Revenue Estimate Exception page for a specific budget line.	View line details for receivables items with budget exceptions.
Line Exceptions	KK_XCP_LN_AR1	Commitment Control, Review Budget Check Exceptions, Revenues, Revenue Estimate, Line Exceptions	View individual transaction lines in a receivables source transaction with budget checking errors or warning exceptions.
Exception Details (lines)	KK_XCP_TRAN_SEC3	Click the View Exception Details button on the Line Exceptions page for the source transaction.	View budget and exception details for a transaction line.
Misc Payment Exceptions	KK_XCP_HDR_AR2	Commitment Control, Review Budget Check Exceptions, Revenues, Direct Journal, Misc Payment Exceptions	View individual transaction lines in a source transaction for a direct journal payment with budget checking errors or warning exceptions.
Receivables Miscellaneous Payment Line Drill Down	KK_DRL_AR2_SEC	Click the View Exception Details button on the Misc Payment Exception page for a specific budget line.	View line details for direct journal payments with budget error exceptions.
Direct Journal Exceptions - Line Exceptions	KK_XCP_LN_AR2	Commitment Control, Review Budget Check Exceptions, Revenues, Direct Journal, Line Exceptions	View individual transaction lines in a source transaction for a direct journal payment with budget checking errors or warning messages.

Reviewing Revenue Estimate Entries

Access the Revenue Estimate Review page or the Revenue Estimate by Activity page (Accounts Receivable, Receivables Update, Revenue Estimates, Review Transactions by Item, Revenue Estimate Review).

Use the Item Activity scroll area to view each activity for an item on the Revenue Estimate Review page. Use the Revenue Estimate scroll area to see source transactions for an item activity. The Revenues grid displays information for each source transaction.

Click the Budget Check button to run the Budget Processor, which checks the source transactions and creates the entries in the revenue bucket for the budget. This button is available only if the transactions have no revenue estimate errors. It is not available if you already ran the Budget Processor.

Note. The system displays a warning message if transactions passed budget checking but receive a warning status.

Correcting Revenue Estimate Entries

Access the Revenue Estimate Correction page (Accounts Receivable, Receivables Update, Revenue Estimate, Correct Transactions, Revenue Estimate Correction).

The page shows the source transactions for a single item activity. It shows only transactions with errors from the Revenue Estimate process or the Budget Processor.

Revenue Estimate

The Revenue Estimate group box displays information about the source transactions that the Revenue Estimate process generated.

	Click the Delete Revenue Estimates button to delete all the source transactions for the item activity. This action resets the Revenue Estimate process so that it can process the activity again. This button is not available if the Correction Complete check box is selected. Note. If you delete an individual line, it will not update the control budget.
	Click the Budget Check button to run the Budget Processor, which checks the source transactions and creates entries in the revenue bucket for the budget. This button is available only after you correct the errors and select Correction Complete. It is not available if you have already run the process. Note. The system displays a warning message if transactions passed budget checking but received a warning status.
	Click the Budget Check Options button to open the Commitment Control page, where you can flag the source transactions in error to bypass budget checking. You must have authority to override budget checking. Click the Go to Transaction Exception link on the Commitment Control page to go to the budget exception page to view details about the budget checking error or warning. This button appears only if the item activity has a budget checking error.
Correction Complete	Select after you correct the errors so that the Budget Processor will check the source transactions the next time you run the process.
Max/Min Rev Amount (maximum or minimum revenue amount)	Displays the minimum or maximum amount permitted for the activity. You receive an error message when you save the page if the total of the revenue estimate lines exceeds the maximum or minimum revenue amount. If the activity credits revenue, the amount cannot exceed the maximum amount. If the activity debits revenue, the amount cannot exceed the minimum amount.

Revenues

The Revenues grid displays information for each source transaction. Change information in this grid as needed to correct the transaction.

The Revenue Estimate process may generate errors for several reasons. The following table lists the reasons and the corresponding resolutions:

Error	Resolution
You transferred the item from one business unit to another. Since different business units might use different revenue accounts, the process does not know which revenue accounts to use.	Enter the revenue accounts manually.
The system could not find revenue lines for the current item activity or in a previous activity for the item.	Enter the revenue lines manually.
The process could not find the From transfer information for a transferred item.	Enter the revenue lines manually.
You applied a payment to an item that was interfaced from PeopleSoft Billing and the item has an associated contract line in PeopleSoft Contracts for an amount-based contract. The process could not find any revenue lines for the contract in the PeopleSoft Contracts PS_CA_ACCTG_LINE table.	You must first post some revenue lines for the contract line in PeopleSoft Contracts and then run the Revenue Estimate process again.

Running the Revenue Estimate Process

Access the Revenue Estimate page (Accounts Receivable, Receivables Update, Revenue Estimates, Create Transactions, Revenue Estimate).

From Date and To	Enter the beginning and ending accounting date of the item activities to include in the run.
Send Transactions Generated	Select to run the Budget Processor automatically immediately following the revenue estimate process.
Specify Transaction Type	Select the source transaction type that the budget processor uses to read the source data and to perform budget checking. The page displays the default source transaction type specified on the Receivables Options - General 2 page. This check box is available only if you select the Send Transactions Generated check box.

Running the Budget Processor

Access one of the following pages to run the Budget Processor:

The Budget Processor page (Accounts Receivable, Receivables Update, Revenue Estimates, Budget Check Transactions, Budget Processor) to run the process for all source transactions that were processed successfully after correcting the errors.

Also run it for transactions that the Revenue Estimate process created for direct journals.
The Revenue Estimate page to run the Budget Processor process along with the Revenue Estimate process.

If you run it with the Revenue Estimate process and you have errors in the source transactions, then you must run it again after you correct the errors.
The Revenue Estimate Review page to run the process for all source transactions for a single item.
The Revenue Estimate Correction page or the Revenue Estimate by Activity page to run the process for all source transactions for a single item activity.

See Also

Running the Revenue Estimate Process

Reviewing Revenue Estimate Entries

Correcting Revenue Estimate Entries

Viewing Budget Checking Exceptions for Revenue Estimate Source Transactions

Access the Revenue Estimate Exceptions page (Commitment Control, Review Budget Check Exceptions, Revenues, Revenue Estimate, Revenue Estimate Exceptions).

Use the pages in the Revenue Estimate component (KK_XCP_AR1) to review the budget exceptions and, if you have authority, to override specific budgets for a failed transaction as well as all budgets for a failed transaction.

Click the View Related Links button at the top of the page to open a page that has the following options:

Go to Source Entry and Go to Source Adjustment: Open the Revenue Estimate - Correction page, where you can change the source transaction and run the Budget Processor.

Go to Source Inquiry: Opens the Revenue Estimate - Review page, where you can view the source transaction and run the Budget Processor.

The process to use the Revenue Estimate component is similar to using the Generic Exceptions component (KK_XCP_GEN).

Viewing Direct Journal Exceptions

Access the Misc Payment Exceptions page (click the View Exception Details button on the Misc Payment Exception page for a specific budget line).

Use the pages in the Direct Journal component (KK_XCP_AR2) to review the budget exceptions. If you have authority, use the pages to override specific budgets for a failed transaction as well as all budgets for a failed transaction.

Click the View Related Links button at the top of the page to open a page that has links to the Directly Journalled Payments page, where you can change the source transaction and run the Budget Processor process.

The process to use the Direct Journal component is similar to using the Generic Exceptions component.