My Oracle Support Banner

Troubleshooting Transaction Flexfields in AutoInvoice (Doc ID 1077555.1)

Last updated on OCTOBER 01, 2018

Applies to:

Oracle Receivables - Version 11.5.10.0 and later
Information in this document applies to any platform.
Executable:RAXMTR - AutoInvoice Master Program
Executable:RAXTRX - AutoInvoice Import Program
Form:FNDFFMDC.FMB - Define Descriptive Flexfield Segments


Purpose

Oracle Receivables (AR): AutoInvoice Information Center > Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 > Note 1077555.1

This note was created to facilitate troubleshooting issues regarding Transaction flexfields in AutoInvoice.

AutoInvoice relies heavily on transaction flexfields to validate and process interface data. The combination of values in the descriptive flexfield segments uniquely identifies each transaction line. The primary types of transaction flexfields used in AutoInvoice are:

These are discussed in detail in Note 1068344.1, Setting Up Receivables Descriptive Flexfields.  It is very important that you review this note to ensure that you populated the proper fields as part of your data load for AutoInvoice.

The following table shows how data from interface columns end up in core AR tables.

Descriptive Flexfield Field in RA_INTERFACE_LINES_ALL Table Name Field name in core AR tables
Invoice Transaction Flexfield INTERFACE_LINE_CONTEXT RA_CUSTOMER_TRX_ALL INTERFACE_HEADER_CONTEXT
  INTERFACE_LINE_ATTRIBUTE1-15 RA_CUSTOMER_TRX_ALL INTERFACE_HEADER_ATTRIBUTE1-15
Transaction Information HEADER_ATTRIBUTE_CATEGORY RA_CUSTOMER_TRX_ALL ATTRIBUTE_CATEGORY
  HEADER_ATTRIBUTE1-15 RA_CUSTOMER_TRX_ALL ATTRIBUTE1-15
Invoice Line Information ATTRIBUTE_CATEGORY RA_CUSTOMER_TRX_LINES_ALL ATTRIBUTE_CATEGORY
  ATTRIBUTE1-15 RA_CUSTOMER_TRX_LINES_ALL ATTRIBUTE1-15
Line Transaction Flexfield INTERFACE_LINE_CONTEXT RA_CUSTOMER_TRX_LINES_ALL INTERFACE_LINE_CONTEXT
  INTERFACE_LINE_ATTRIBUTE1-15 RA_CUSTOMER_TRX_LINES_ALL
INTERFACE_LINE_ATTRIBUTE1-15

Link-To Transaction Flexfield LINK_TO_LINE_CONTEXT none none
  LINK_TO_LINE_ATTRIBUTE1-15 RA_CUSTOMER_TRX_LINES_ALL The values in the attribute fields are used to identify a particular row in RA_CUSTOMER_TRX_LINES_ALL and are used to retrieve a CUSTOMER_TRX_LINE_ID value, which is then stored in LINK_TO_LINE_ID
Reference Transaction Flexfield REFERENCE_LINE_CONTEXT none none
  REFERENCE_LINE_ATTRIBUTE1-15 RA_CUSTOMER_TRX_LINES_ALL The values in the attribute fields are used to identify a particular row in RA_CUSTOMER_TRX_LINES_ALL and are used to retrieve a CUSTOMER_TRX_LINE_ID value, which is then stored in REFERENCE_LINE_ID

Issues regarding Transaction flexfields in AutoInvoice are typically setup related, please review the symptoms listed below.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 1. Troubleshooting Flexfield related errors encountered during Importing
      a. Error: APP-11914 Duplicate Transaction Flexfield
            i. Check for duplicates within the interface table
            ii. Check for duplicates existing in the core AR transaction tables
      b. Error: APP-00778 Invalid context field value (OE) passed to flexfield routine FDFDFA
      c. Error: None of the transaction flexfield contexts you have provided for this request have enabled segments
      d. Error: All enabled segments of Transaction Flexfield must have a value.
      e. Contra Charging related issues
            i. Duplicate Transaction Flexfield errors
            ii. All enabled segments of Transaction Flexfield must have a value (..)
 2. Troubleshooting Unexpected Behavior re. Transaction Flexfields
      a. Data in ATTRIBUTE1-15 fields are not transferred into core AR table fields.
      b. Value set validation is not done against segments of the Transaction Flexfield
      c. Attributes from Order Entry are truncated when transferred into AR tables
      d. ATTRIBUTE1-15 descriptive flexfield inheritance from Invoice to Credit Memo
      f. Defaulting not occurring for Transaction Flexfields
      g. Data passed in for Distributions or Sales Credits are ignored by AutoInvoice
      h. RA_CUSTOMER_TRX_ALL.INTERFACE_HEADER_CONTEXT is populated inconsistently with BATCH_SOURCE_NAME
 3. Still Have Questions?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.