Using AutoInvoice (Oracle Receivables Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

AutoInvoice Validation

AutoInvoice validates your data for compatibility with Receivables. It ensures that the columns in Receivables' Interface tables reference the appropriate values and columns in Receivables. To learn more about the validation AutoInvoice performs for each column in the AutoInvoice tables, see: Table and Column Descriptions.

Existence

For some columns, AutoInvoice ensures that the values are already defined in Receivables. However, AutoInvoice does not validate against any effectivity date or status.

Batch Sources

You do not have to pass values for all of the fields that are referenced in the Transaction Sources window. If you want AutoInvoice to ignore any of these values for a specific batch source, you can set the field to 'None' in the Transaction Sources window. You use transaction batch sources that have a type of 'Imported' when importing transactions into Receivables. See: Transaction Batch Sources.

Uniqueness

AutoInvoice ensures that the invoice number you supply is unique within a given batch source and the document number you supply is unique within the associated sequence type.

AutoInvoice also ensures that the Transaction Flexfield you supply is unique. For more information, refer to Transaction Flexfields.

Precision

Precision is the number of digits to the right of the decimal point that are used in regular currency transactions. AutoInvoice ensures that the amount and the accounted amount you supply have the correct precision for a given currency.

Cross Validation

AutoInvoice ensures that certain column values agree with each other. These values can be within an interface table or multiple interface tables.

For example, if you specify in your batch source that you do not want to use accounting rules, AutoInvoice ignores any values you supply for invoicing rule, accounting rule, and accounting rule duration. However, if you do import transactions that use accounting rules, AutoInvoice requires that these transactions also include an invoicing rule.

Validation for Lines With Rules

Besides validating dates, AutoInvoice also validates and rejects lines if:

The accounting rule has overlapping periods

All of the accounting periods do not exist for the duration of your accounting rule

For more information, see: Importing Invoices with Rules.

Create Transactions with Invalid or Incorrect Data

You can specify whether AutoInvoice will reject or partially create transactions that have an invalid line, invalid tax rate, or a GL date in a closed period. For example, you import an invoice with three invoice lines and one of the lines is invalid. If the value of the Invalid Line field for this batch source is set to 'Create Invoice', AutoInvoice will create the invoice with only the two valid lines. You can then use the Transaction window to add the line that was rejected. If Invalid Line is set to 'Reject Invoice,' AutoInvoice will not import this transaction or any of its lines into the interface tables. Transactions that fail validation appear in the AutoInvoice Validation report.

The values you enter in the AutoInvoice Processing Options alternative region of the Transaction Sources window determine how AutoInvoice will process transactions with invalid data. See: Transaction Batch Sources.