Validate Transaction Type Against Amount
Use this feature to make sure a transaction's numeric sign matches the amount's sign on the order line. The Receivables Transaction Type attribute on an order line can contain different types of transactions, such as Invoice or Credit Memo. Each type has a positive or negative numeric sign (+ or -). For example, Invoice has a positive sign and Credit Memo has a negative sign. If Receivables Transaction Type contains Invoice, and if the amount isn't positive, then this feature prevents you from submitting the order.
If you set the Validate Transaction Type's Sign Against Amount order management parameter to Group and Validate Lines by Transaction Type, then this feature will validate order lines as a group according to the receivables transaction. This is the default behavior.
Assume you have these order lines:
| Line | Amount | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|
| 1 | -100 | My Invoice | Positive |
| 2 | -100 | My Invoice | Positive |
| 3 | 400 | My Invoice | Positive |
- The sign on lines 1 and 2 are negative but the transaction's sign is positive.
- The parameter groups the lines by default, so this feature adds up the amount for all lines, which is +200.
- +200 has a positive sign, it matches the transaction's sign, so Order Management successfully submits the order.
- The sign for the amounts on lines 1 and 2 don't match the transaction's sign but Order Management will send them to the invoicing task anyway. To fix this problem, go to the Billing work area in Oracle Receivables, then click Tasks > Manage AutoInvoice Lines. Open the ManageAutoInvoiceLines.xlsx file that the task downloaded, search for your sales order, modify the order lines' amounts so they match the transaction's sign, then upload your changes.
Consider another example:
| Line | Amount | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|
| 1 | -100 | My Invoice | Positive |
| 2 | -100 | My Invoice | Positive |
| 3 | 400 | My Invoice | Positive |
| 4 | -200 | Credit Memo | Negative |
| 5 | -200 | Credit Memo | Negative |
- Here we have two groups. One group for My Invoice, and another for Credit Memo.
- The amount on lines 4 and 5 add up to -400, which matches the transaction's sign on lines 4 and 5.
- The signs match for each group, so Order Management successfully submits the order.
- The sign for the amounts on lines 1 and 2 don't match the transaction's sign but Order Management will send them to the invoicing task anyway. You must use the ManageAutoInvoiceLines.xlsx file to fix the problem.
Consider another example:
| Line | Amount | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|
| 1 | 100 | My Invoice | Positive |
| 2 | 100 | My Invoice | Positive |
| 3 | -400 | My Invoice | Positive |
- This feature adds up the amount for all lines in the group, which is -200.
- -200 has a negative sign, it doesn't match the transaction's sign, so Order Management rejects the request to submit the order and displays an error. You must revise the order so the receivables transaction and the amount match, then resubmit the order.
Consider another example:
| Line | Amount | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|
| 1 | 700 | My Invoice | Positive |
| 2 | 600 | My Invoice | Positive |
| 3 | -400 | My Invoice | Positive |
- This feature adds up the amount for all lines, which is +900.
- +900 has a positive sign, it matches the transaction's sign, so Order Management successfully submits the order.
- The sign for the amount on line 3 doesn't match the transaction's sign on line 3 but Order Management will send it to the invoicing task anyway. You must use the ManageAutoInvoiceLines.xlsx file to fix the problem.
If you set the parameter to group, and if the Receivables Transaction Type attribute is empty on the order line, then this feature doesn’t validate the line when you submit the sales order because it can't determine whether the line is eligible to invoice.
Validate Each Line
You can also set the parameter to validate each line separately. Consider an example:
| Line | Amount | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|
| 1 | -100 | My Invoice | Positive |
| 2 | 400 | My Invoice | Positive |
- The sign on line 1 is negative but the transaction's sign is positive, they don't match, so Order Management fails to submit the order.
- You must modify the amount so its sign matches the transaction's sign, or modify the transaction so its sign matches the amount's sign.
Here's another example:
| Line | Amount | Receivables Transaction Type | Transactions Sign |
|---|---|---|---|
| 1 | 100 | My Invoice | Positive |
| 2 | 100 | My Invoice | Positive |
| 3 | 400 | - | - |
- There is no transaction sign for line 3 because Receivables Transaction Type is empty.
- This feature ignores any line where Receivables Transaction Type is empty. The signs match on lines 1 and 2, so Order Management will successfully submit the order for all 3 lines.
If Receivables Transaction Type is empty, and if the transaction's sign doesn't match the amount's sign on that line, then Order Management won't interface the line to Receivables during the invoicing task. Instead, Order Management will display an error. You must modify the transaction type so the signs match, then submit the order again.
Steps to Enable
- Go to the Setup and Maintenance work area, then click Tasks > Search.
- Search for and open the Manage Order Management Parameters task.
- Set the Validate Transaction Type's Sign Against Amount order management parameter.
Tips And Considerations
- The Receivables Transaction Type attribute on the redesigned pages and the Receivable Transaction attribute on the classic pages in Order Management contain the same data that the Transaction Type attribute in Oracle Receivables contains. They're just different labels for the same data.
- This feature validates orders regardless of whether you price them in Oracle Pricing or in some other pricing application. It also validates revisions and referenced or unreferenced return lines.
- This feature doesn't validate transfer orders. It also doesn't validate closed or cancelled order lines.
- We recommend that you include a value in the BillingTransactionTypeName attribute when you import a sales order through REST API. If you use an order management extension, then use the billingTxnTypeName attribute and use the On Save or the On Submit extension point.
- If Receivables Transaction Type contains the value Any, then this feature doesn't validate the line. To modify that value, go to the Setup and Maintenance work area, then use the Manage Transaction Type task to set the Creation Sign attribute to Any or some other value.
- If you set up your own step in your orchestration process, then Order Management might interface order lines to Receivables at different times. Validation might fail in Receivables when it creates the invoice. If this happens, you must use the ManageAutoInvoiceLines.xlsx file to fix the problem.
- You can't use the Billing work area to delete a transaction for an order line that Order Management has interfaced to Receivables. Deleting the transaction would result in stuck orders and order lines that never close because Receivables never invoices the line.
Revisions
Assume you revise an order line, the revision changes the amount's sign so that it no longer matches the transaction's sign, and then submit the revision. If you set the parameter to:
- Validate each line. Validation will fail on the invoicing task. You must modify the transaction type so the values match. If you don't do this, then Receivables won't create the invoice.
- Group and validate lines. Validation won't fail on the invoicing task. You must use the ManageAutoInvoiceLines.xlsx file to modify the amount so the values match. If you don't do this, then Receivables will not create the invoice.
Shipment Sets
This feature ignores shipment sets. For example, if you set the parameter to validate each line, then this feature validates each line even when lines are in a shipment set. The submit will fail in this example because the signs in lines 3 and 5 don't match:
| Line | Amount | Shipment Set | Receivables Transaction Type | Transaction's Sign |
|---|---|---|---|---|
| 1 | 700 | Ship Set1 | My Invoice | Positive |
| 2 | 600 | Ship Set1 | My Invoice | Positive |
| 3 | -400 | Ship Set1 | My Invoice | Positive |
| 4 | 900 | My Invoice | Positive | |
| 5 | -2400 | My Invoice | Positive |
If you set the parameter to group lines, then the submit will still fail because the sum of all lines is negative, but the transaction's sign is positive.
Key Resources
Access Requirements
You need the Update AutoInvoice Interface Lines privilege to use the ManageAutoInvoiceLines.xlsx file. See What's the difference between AutoInvoice exceptions and unprocessed lines?