Common Elements Used for Commitment Control Processing

Field or Control	Description
	Click the Revenue Line Source icon 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. 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. Oracle suggests 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 (CONVER_DATA1_SS), 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.