How AutoInvoice Validates Imported Transactions

Use the AutoInvoice Options and Import Information sections of an Imported transaction source to define how AutoInvoice validates imported transaction lines.

You don't have to pass values for all of the fields that are referenced in the transaction source. If you don't want AutoInvoice to pass certain data, then where available you can set the related option to None.

Note: Even if you set a transaction source data option to None in order to avoid importing this information into the interface tables, AutoInvoice can still validate and reject transaction lines with invalid data.

Settings That Affect the Validation of Imported Transactions

These settings affect the validation of imported transactions:

• Invalid Line field: Indicate how AutoInvoice handles imported transactions with invalid lines by selecting either Reject Invoice or Create Invoice.

  • If you select Reject Invoice, AutoInvoice doesn't import this transaction or any of its lines into the interface tables.

  • If you select Create Invoice, AutoInvoice creates a transaction with valid lines only. For example, you import an invoice with three invoice lines and one of the lines is invalid. AutoInvoice creates the invoice with the two valid lines only and rejects the invalid line. You can use the Edit Transaction page to add the rejected line.

• Accounting Date in a Closed Period field: Indicate how AutoInvoice handles imported transactions that have lines in the interface lines table that are in a closed accounting period.

  • Select Adjust to have AutoInvoice automatically adjust the accounting dates to the first accounting date of the next open or future enterable period.

  • Select Reject to reject these transaction lines.

• In the Import Information sections, where applicable select Number, Value, Segment, or ID for each option to indicate how AutoInvoice validates information:

  • Select Number to import a record into the interface tables using its assigned number.

  • Select Value to import a record into the interface tables using its actual name.

    Note: Use Value if you intend to use the transaction source to import data from a non-Oracle system.

  • Select Segment to use the flexfield segment.

  • Select ID to use the internal identifier of the record.

• Select Amount or Percent to indicate how AutoInvoice validates Sales Credits and Revenue Account Allocations on transaction lines.

How Imported Transactions Are Validated

AutoInvoice validates imported transactions based on the settings of the assigned Imported transaction source. Transactions that fail validation appear in the Import AutoInvoice Validation report.

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 the transaction source indicates that a revenue scheduling rule can't be used, AutoInvoice ignores any values passed for invoicing rule, revenue scheduling rule, and revenue scheduling rule duration.

AutoInvoice performs these validations on transaction lines with revenue scheduling rules:

• Requires that these transactions also include an invoicing rule, if you import transactions that use revenue scheduling rules.

• Rejects lines, if the revenue scheduling rule has overlapping periods.

• Rejects lines, if the designated accounting periods don't exist for the duration of the revenue scheduling rule.