Entering a Manual Transaction
Entering a manual transaction involves selecting a transaction batch, then opening the Transactions window. The Transactions window displays the individual transactions processed by Oracle Sales Compensation. You use the Transactions window to enter, view, modify, or reverse transactions. All transactions, both those collected by Oracle Sales Compensation and those entered manually are displayed.
Oracle Sales Compensation uses the information in each manual transaction line to calculate a compensation payment based on the amount of sales credit you assign. When you save the transaction, Oracle Sales Compensation automatically assigns a transaction number to each manual transaction.
To manually enter a transaction:
1. Navigate to the Transactions window.
By default, choose Maintain Transactions from the Salespeople menu, select a transaction batch, then choose Transactions.
The transactions in the batch you selected are displayed in the Transactions window.
2. Enter the appropriate information for this transaction.
Transaction: The unique number automatically assigned to this transaction by the system. You cannot enter or change this number.
Type: Identifies the type of manual transaction (e.g. manual adjustment, invoice, or order).
Status: When you first enter a manual transaction, the default mode is Unprocessed. In this mode, you enter one or more manual transaction lines, which are assigned Unprocessed status. Manual transactions can have a status of: Unprocessed, Classified, Failed Classification, Rolled Up, Failed Rollup, Populated, Failed Populated, Calculated, or Failed Calculation (see About Manual Transaction Processing for a description of each mode). Manual transactions that calculate without error are set to Calculate. You cannot change a calculated transaction. You cannot enter or change the status value.
Salesperson Name: The name of the salesperson to whom this transaction is assigned.
Salesperson Number: The number of the salesperson to whom this transaction is assigned.
Process Period: You can enter a valid period in this field. Oracle Sales Compensation calculates the compensation payment based on the compensation plan effective for this period for the salesperson named in the transaction line. You can assign different processing periods to different transaction lines in a batch, if necessary; however, a period must be defined in your set of books to be valid. See Selecting the Set of Books for more information about defining periods in your set of books.
Note: If you need to adjust orders or invoices in prior periods, you can backdate the manual transaction. Oracle Sales Compensation recalculates all compensation payments forward of a period, using the period you specify in the Rollup Period field. Calculations could also be affected if a different compensation plan or rollup chain is effective during the prior period.
Functional Amount: Enter the amount of sales credit you want to assign to the salesperson. This amount should be in the functional currency.
Curr: This field shows the foreign currency code that applies for the transaction. Use the list of values to select an enabled currency for this field. You can see all available currencies, whether they are enabled or disabled.
Note: Even if a currency code is disabled, Oracle Sales Compensation will accept transactions in that currency from Oracle Receivables and perform calculations. If you select a disabled currency for a transaction from a source other than Oracle Receivables, Oracle Sales Compensation gives you an error message.
Reval Rate: The revaluation rate is the rate that is used to calculate the conversion from the foreign amount (see Foreign Amount below) to the functional currency.
Oracle Sales Compensation obtains revaluation rates from Oracle General Ledger. If you want to add a revaluation rate for a particular currency, then you must do so in Oracle General Ledger.
Note: For more information about revaluation rates, see the Oracle General Ledger Reference and the Oracle General Ledger User's Guide.
Comments: Optionally, enter a descriptive purpose for the batch of manual transaction lines you are entering. These comments are printed on all default manual transaction reports and compensation statements.
Several additional fields from the CN_COMMISSION_LINES table are available that describe how Oracle Sales Compensation calculated the transaction. These fields may be helpful for auditing purposes.
3. Tab to the brackets to view or enter the descriptive flexfield if one is defined for this form.
Because you may have customized this window to suit the specific manual transaction needs of your sales organization, you may need to enter more information in this window than is explained in this section.
Note: For more information about descriptive flexfields, see the Oracle Application Object Library Reference Manual.
