Autoinvoice Date Issues (So many dates in interface table)

Resolving Autoinvoice Date Issues

There are just so many dates and so many ways to derive all the dates.  Receivables Transactions have General Ledger (GL) Date (GL_DATE), Transaction Date(TRX_DATE), Ship Date(ship_date_actual), Sales Order Date(sales_order_date), and Rule Start dates to name a few.  There are also several ways to get your dates, with Autoinvoice you can enter your GL Date and Transaction Date in the columns of RA_INTERFACE_LINES_ALL table or you can allow the AutoInvoice process to derive the dates.

If the dates are not provided in the interface tables they will be derived based on your setups.  Date Derivation of the General Ledger date and Transaction date during the process of AutoInvoice depends on the following date columns in the RA_INTERFACE_LINES_ALL table:

• GL_DATE
• TRX_DATE
• SHIP_DATE_ACTUAL
• SALES_ORDER_DATE
• RULE_START_DATE 

AutoInvoice determines the General Ledger date for invoices using the following criteria:

• Does a GL date exist for this invoice in the interface table?
• Does the invoice use rules?
• What is the setting of the Derive Date option for this Transaction Batch Source (Yes or No)?   (Receivables Responsibility > Setup > Transaction > Sources)
• What is the setting of the GL Date in a Closed Period option for this Transaction Batch Source (Adjust or Reject)?  (Receivables Responsibility > Setup > Transaction > Sources)

If you elected to derive the rule start date, AutoInvoice first uses the ship date in the interface table. If the ship date does not exist, AutoInvoice uses the sales order date. If the sales order date does not exist, AutoInvoice uses the date you entered in the Run AutoInvoice window.  The following diagram illustrates this process.