ra_interface_lines_all 接口表各字段说明

note:Description and Usage of Fields in RA_INTERFACE_LINES Table [ID 1195997.1]

核心内容:

Field Name and Description Validation and Destination User should provide data when... 
and Reference Information
INTERFACE_LINE_ID

This column is used by AutoInvoice and should be left null. AutoInvoice defaults a value in this column using the RA_CUSTOMER_TRX_LINES_S sequence.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
CUSTOMER_TRX_LINE_ID

Never

Users should not populate this field. The AutoInvoice process takes care of providing a value in this field.

INTERFACE_LINE_CONTEXT

AutoInvoice uses this field to understand the data you pass into fields INTERFACE_LINE_ATTRIBUTE1-15

The value you provide here should exist as a Context Flexfield Code in the Descriptive Flexfields form.

Responsibility: Receivables Manger 
Navigation: Setup > Financials > Flexfields > Descriptive > Segments

Query for Application = Receivables, Title = Line Transaction Flexfield to see valid values.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
INTERFACE_HEADER_CONTEXT and 
RA_CUSTOMER_TRX_LINES_ALL. 
INTERFACE_LINE_CONTEXT

Mandatory

AutoInvoice uses this field to understand the context of the data passed into the INTERFACE_LINE_ATTRIBUTE* fields.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

INTERFACE_LINE_ATTRIBUTE1 to 
INTERFACE_LINE_ATTRIBUTE15

Depending on which fields are associated to the segments of the descriptive flexfield identified by INTERFACE_LINE_CONTEXT,  then those INTERFACE_LINE_ATTRIBUTE* should be populated.

Validation: 
Combination of INTERFACE_LINE_CONTEXT + 
INTERFACE_LINE_ATTRIBUTE* fields must not already exist in 
RA_INTERFACE_LINES_ALL and 
RA_CUSTOMER_TRX_LINES_ALL.

Destination: 
RA_CUSTOMER_TRX_ALL. 
INTERFACE_HEADER_ATTRIBUTE1-15* and

RA_CUSTOMER_TRX_LINES_ALL. 
INTERFACE_LINE_ATTRIBUTE1-15

* When you import transactions with multiple lines using 
AutoInvoice, the attributes of the first line from the ordered 
lines of the invoice will be used as the Invoice Transaction Flexfield.

Mandatory

Depending on which INTERFACE_LINE_ATTRIBUTE* fields are associated to the segments of the descriptive flexfield identified by INTERFACE_LINE_CONTEXT, then those attribute fields need to be populated.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

REFERENCE_LINE_ID

This field is used to provide a reference to a transaction line that you are either:

  • crediting
  • associating against a deposit/guarantee
Validation: 
Must exist in 
RA_CUSTOMER_TRX_LINES_ALL. 
CUSTOMER_TRX_LINE_ID

Destination:

  • For a Credit Memo, RA_CUSTOMER_TRX_ALL. 
    PREVIOUS_CUSTOMER_TRX_ID
  • For an Invoice against a Deposit 
    RA_CUSTOMER_TRX_ALL. 
    INITIAL_CUSTOMER_TRX_LINE_ID
Optional/ Conditional

When providing reference to another transaction, you populate either 
this field or a combination of REFERENCE_LINE_ATTRIBUTE* 
fields but not both.

  • For Applied Credit Memos, this field contains the RA_CUSTOMER_TRX_LINES_ALL. 
    CUSTOMER_TRX_LINE_ID of the transaction being credited.
  • For an Invoice against a Deposit, this field contains the RA_CUSTOMER_TRX_LINES_ALL. 
    CUSTOMER_TRX_LINE_ID of the deposit/guarantee
  • For On-Account Credit Memos, this field should not be populated.

* When capturing Reference information you populate either REFERENCE_LINE_ID or 
REFERENCE_LINE_CONTEXT + REFERENCE_LINE_ATTRIBUTE* fields and what fields you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1110573.1
Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables

REFERENCE_LINE_CONTEXT

If you are providing values in any of the fields REFERENCE_LINE_ATTRIBUTE1-15 then you need to identify the context in which you are providing those values.

The value you provide here should exist as a Context Flexfield Code in the Descriptive Flexfields form.

Responsibility: Receivables Manger 
Navigation: Setup > Financials > Flexfields > Descriptive > Segments

Query for Application = Receivables, Title = Line Transaction Flexfield to see valid values.

Validation: 
Must exist in 
RA_CUSTOMER_TRX_LINES_ALL. 
INTERFACE_LINE_CONTEXT or 
RA_INTERFACE_LINES_ALL. 
INTERFACE_LINE_CONTEXT

Destination: 
None

Optional/Conditional*

If you are identifying the transaction to reference by using a combination of REFERENCE_LINE_ATTRIBUTE* fields then this field is required.

If you are identifying the transaction to reference using the REFERENCE_LINE_ID, then this field is not required.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

Note 1110573.1
Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables

REFERENCE_LINE_ATTRIBUTE1 to REFERENCE_LINE_ATTRIBUTE15

Depending on which INTERFACE_LINE_ATTRIBUTE* fields are associated to the segments of the descriptive flexfield identified by REFERENCE_LINE_CONTEXT,  you map those same fields to the corresponding REFERENCE_LINE_ATTRIBUTE* fields and populate those.

Validation: 
Must exist in 
RA_CUSTOMER_TRX_LINES_ALL. 
INTERFACE_LINE_ATTRIBUTE1-15 or 
RA_INTERFACE_LINES_ALL. 
INTERFACE_LINE_ATTRIBUTE1-15

Destination: 
None

Optional/Conditional

When providing reference to another transaction, and you populate the REFERENCE_LINE_CONTEXT, then the associated combination of REFERENCE_LINE_ATTRIBUTE* fields are required.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

Note 1110573.1
Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables

LINK_TO_LINE_ID

This column is used by AutoInvoice and should be left null. During processing, AutoInvoice will populate this field with a value which will point to a particular row identified by the fields 
RA_INTERFACE_LINES_ALL.LINK_TO_LINE_ATTRIBUTE1-15 
and LINK_TO_LINE_CONTEXT.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
LINK_TO_CUST_TRX_LINE_ID

Never

Users should not populate this field. The AutoInvoice process takes care of providing a value in this field.

LINK_TO_LINE_CONTEXT

If you are providing values in any of the fields LINK_TO_LINE_ATTRIBUTE1-15 then you need to identify the context in which you are providing those values.

The value you provide here should exist as a Context Flexfield Code in the Descriptive Flexfields form.

Responsibility: Receivables Manger 
Navigation: Setup > Financials > Flexfields > Descriptive > Segments

Query for Application = Receivables, Title = Line Transaction Flexfield to see valid values.

Validation: 
None

Destination: 
None

Optional/Conditional

If you provide values in a  combination of LINK_TO_LINE_ATTRIBUTE* fields then this field is required.

This field should only be populated for records with LINE_TYPE = ‘TAX‘ or ‘FREIGHT‘ at the invoice line level.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

LINK_TO_LINE_ATTRIBUTE1 to 
LINK_TO_LINE_ATTRIBUTE15

Depending on which INTERFACE_LINE_ATTRIBUTE* fields are associated to the segments of the descriptive flexfield identified by LINK_TO_LINE_CONTEXT,  you map those same fields to the corresponding LINK_TO_LINE_ATTRIBUTE* fields and populate those.

Validation: 
The transaction that you link to must have a LINE_TYPE = 
‘LINE‘. You can only link at most one freight line to another 
transaction. You cannot link a transaction that has a 
LINE_TYPE = ‘LINE‘ or ‘CHARGES‘ to another transaction.

Destination: 
None

Optional/Conditional

Only populated when you want to link a TAX or FREIGHT line to a specific row in the interface table, only records with LINE_TYPE = ‘TAX‘ or ‘FREIGHT‘ should have these fields populated.

Populate the appropriate LINK_TO_LINE_ATTRIBUTE* fields to map to the INTERFACE_LINE_ATTRIBUTE* values you want this record to link to. The combination of INTERFACE_LINE_ATTRIBUTE* values must identify a record which has LINE_TYPE = ‘LINE‘

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

ATTRIBUTE_CATEGORY

To capture additional flexfield information at the transaction line level, you can optionally use the ATTRIBUTE* fields.

If you are providing values in any of the fields ATTRIBUTE* then you need to identify the context in which you are providing those values.

The value you provide here should exist as a Context Flexfield Code in the Descriptive Flexfields form.

Responsibility: Receivables Manger 
Navigation: Setup > Financials > Flexfields > Descriptive > Segments

Query for Application = Receivables, Title = Invoice Line Information to see valid values.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
ATTRIBUTE_CATEGORY

Optional

If you provide any data in the ATTRIBUTE* fields then you need to indicate the context of that data and populate this field.

ATTRIBUTE1 to ATTRIBUTE15

Depending on which fields are associated to the segments of the descriptive flexfield identified by ATTRIBUTE_CATEGORY, those ATTRIBUTE* fields should be populated

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
ATTRIBUTE1-15

Optional

Only populated when you want to capture additional flexfield information at the Invoice Line level.

HEADER_ATTRIBUTE_CATEGORY

To capture additional flexfield information at the transaction header level, you can optionally use the HEADER_ATTRIBUTE* fields.

If you are providing values in any of the fields HEADER_ATTRIBUTE* then you need to identify the context in which you are providing those values.

The value you provide here should exist as a Context Flexfield Code in the Descriptive Flexfields form.

Responsibility: Receivables Manger 
Navigation: Setup > Financials > Flexfields > Descriptive > Segments

Query for Application = Receivables, Title = Transaction Information to see valid values.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
ATTRIBUTE_CATEGORY

Optional 
If you want to provide any data in the HEADER_ATTRIBUTE* fields then you need to indicate the context of that data and populate this field.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

HEADER_ATTRIBUTE1 to HEADER_ATTRIBUTE15

Depending on which fields are associated to the segments of the descriptive flexfield identified by HEADER_ATTRIBUTE_CATEGORY, those HEADER_ATTRIBUTE* fields should be populated

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
ATTRIBUTE1-15

Optional

Populate if you want to capture additional flexfield information at the Transaction Header level.

Reference: 
Note 1068344.1, Setting Up Receivables Descriptive Flexfields

HEADER_GDF_ATTR_CATEGORY

This field is reserved for country-specific functionality.

Validation: 
Performed by Oracle Global Financials

Destination: 
RA_CUSTOMER_TRX_ALL. 
ATTRIBUTE_CATEGORY

Optional

When necessary, this is populated by a Localization or Globalization feature

HEADER_GDF_ATTRIBUTE1 to 
HEADER_GDF_ATTRIBUTE30

These fields are reserved for country-specific functionality.

Validation: 
Performed by Oracle Global Financials

Destination: 
RA_CUSTOMER_TRX_ALL. 
GLOBAL_ATTRIBUTE1-30

Optional

When necessary, these fields are populated by a Localization or Globalization feature

LINE_GDF_ATTR_CATEGORY

This field is reserved for country-specific functionality.

Validation: 
Performed by Oracle Global Financials

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
GLOBAL_ATTRIBUTE_CATEGORY

Optional

When necessary, this is populated by a Localization or Globalization feature

LINE_GDF_ATTRIBUTE1 to 
LINE_GDF_ATTRIBUTE20

These fields are reserved for country-specific functionality.

Validation: 
Performed by Oracle Global Financials

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
GLOBAL_ATTRIBUTE1-20

Optional

When necessary, these fields are populated by a Localization or Globalization feature

INVENTORY_ITEM_ID

Contains the ID of the item being invoiced.

Validation: 
Must exist in 
MTL_SYSTEM_ITEMS. 
INVENTORY_ITEM_ID and 
MTL_SYSTEM_ITEMS. 
INVOICE_ENABLED_FLAG = ‘Y‘.

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
INVENTORY_ITEM_ID

Optional/Conditional*

If you need to pass information on a particular inventory item and your Transaction Batch Source is setup with Inventory Item = Id:

then populate INVENTORY_ITEM_ID.

If you do not need to pass Inventory Item information, you do not have to populate this field.

* When capturing Inventory item information you populate either INVENTORY_ITEM_ID or MTL_SYSTEM_ITEMS_SEG* fields 
and what fields you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

MTL_SYSTEM_ITEMS_SEG1 to 
MTL_SYSTEM_ITEMS_SEG20

Contains the System Item segments that identify a particular inventory item

Validation: 
Valid combination of System Item Flexfield segment values

Destination: None

Optional/Conditional*

If you need to pass information on a particular inventory item and your Transaction Batch Source is setup with Inventory Item = Segment:

then  populate the appropriate MTL_SYSTEM_ITEMS_SEG* fields to identify an inventory item in MTL_SYSTEM_ITEMS.

If you do not need to pass Inventory Item information, you do not have to populate any of the MTL_SYSTEM_ITEMS_SEG* fields.

* When capturing Inventory item information you populate either INVENTORY_ITEM_ID or MTL_SYSTEM_ITEMS_SEG* fields 
are what fields you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

TERRITORY_ID

This field is optional, and allows you to capture the Sales territory associated to an invoice.

Validation: 
Must exist in RA_TERRITORIES.TERRITORY_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
TERRITORY_ID

Optional/Conditional*

If you need to capture Sales Territory information, and your Transaction Batch Source is setup with Sales Territory = Id:

then populate TERRITORY_ID.

If you do not need to capture Sales Territory information, you do not have to populate this field

* When capturing Territory information you populate either TERRITORY_ID or TERRITORY_SEGMENT* fields 
and what fields you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

TERRITORY_SEGMENT1 to 
TERRITORY_SEGMENT20

These fields are optional, and allow you to capture the Sales territory segments associated to an invoice.

Validation: 
Valid combination of Territory Flexfield segment values 
from RA_TERRITORIES

Destination: 
None

Optional/Conditional*

If you need to capture Sales Territory information, and your Transaction Batch Source is setup with Sales Territory = Segment:

then populate the appropriate TERRITORY_SEGMENT* fields to identify a sales territory.

If you do not need to capture Sales Territory information, you do not have to populate any of the TERRITORY_SEGMENT* fields.

* When capturing Territory information you populate either TERRITORY_ID or TERRITORY_SEGMENT* fields 
and what fields you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

ORIG_SYSTEM_BATCH_NAME

You can optionally keep track of the batch name associated to this transaction from the feeder system

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
ORIG_SYSTEM_BATCH_NAME

Optional

If you need to record the original batch name associated to this transaction, enter the value here, otherwise you may leave this field blank.

ORIG_SYSTEM_BILL_CUSTOMER_REF

This field contains the Bill To Customer Reference for this transaction.

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
ORIG_SYSTEM_REFERENCE

Destination: 
None

Mandatory/Conditional*

If the setup of your transaction batch source is Bill to Customer = Value:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Bill to information is mandatory, so you must provide this information either in ORIG_SYSTEM_BILL_CUSTOMER_ID or ORIG_SYSTEM_BILL_CUSTOMER_REF and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 1097846.1, AutoInvoice Error: Invalid bill to customer reference (ORIG_SYSTEM_BILL_CUSTOMER_REF)

ORIG_SYSTEM_BILL_CUSTOMER_ID

This field contains the Bill To Customer ID for this transaction.

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
CUST_ACCOUNT_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
BILL_TO_CUSTOMER_ID

Mandatory/Conditional*

If the setup of your transaction batch source is Bill to Customer = Id:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Bill to information is mandatory, so you must provide this information either in ORIG_SYSTEM_BILL_CUSTOMER_ID or ORIG_SYSTEM_BILL_CUSTOMER_REF and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 1097862.1, AutoInvoice Error: Invalid bill to customer id (ORIG_SYSTEM_BILL_CUSTOMER_ID)

ORIG_SYSTEM_BILL_ADDRESS_REF

This field contains the Address Reference associated to the Bill-To Customer entered in either ORIG_SYSTEM_BILL_CUSTOMER_REF or 
ORIG_SYSTEM_BILL_CUSTOMER_ID.

Validation: 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_ADDRESS_REF = 
HZ_PARTY_SITES.ORIG_SYSTEM_REFERENCE 
and CUSTOMER_REF = 
HZ_CUST_ACCOUNTS. 
ORIG_SYSTEM_REFERENCE and 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = 
HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and 
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = 
HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and 
RA_SITE_USES.SITE_USE_CODE = ‘BILL_TO‘

Destination: 
None

Mandatory/Conditional*

If the setup of your transaction batch source is Bill to Address = Value:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Bill to information is mandatory, so you must provide this information either in ORIG_SYSTEM_BILL_ADDRESS_REF or ORIG_SYSTEM_BILL_ADDRESS_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 365287.1, AutoInvoice Error: The Bill To Address Reference Must Exist In Receivables, And It Must Be Assigned To The Bill To Customer (ORIG_SYSTEM_BILL_ADDRESS_REF)

ORIG_SYSTEM_BILL_ADDRESS_ID

This field contains the Address ID associated to the Bill-To Customer entered in either ORIG_SYSTEM_BILL_CUSTOMER_REF or 
ORIG_SYSTEM_BILL_CUSTOMER_ID.

Validation: RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_ADDRESS_ID = HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID 
and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_CUSTOMER_ID = 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID and 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = 
HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and 
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = 
HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and 
RA_SITE_USES.SITE_USE_CODE = ‘BILL_TO‘

Destination: 
RA_CUSTOMER_TRX_ALL. 
BILL_TO_ADDRESS_ID

Mandatory/Conditional*

If the setup of your transaction batch source is Bill to Address = Id:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* Bill to information is mandatory, so you must provide this information either in ORIG_SYSTEM_BILL_ADDRESS_REF or ORIG_SYSTEM_BILL_ADDRESS_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 1097925.1, AutoInvoice Error: The Bill To address id must exist in Oracle Receivables, and it must be assigned to the Bill To customer ORIG_SYSTEM_BILL_ADDRESS_ID

ORIG_SYSTEM_BILL_CONTACT_REF

This field contains contact reference for the customer you entered in either ORIG_SYSTEM_BILL_CUSTOMER_REF or 
ORIG_SYSTEM_BILL_CUSTOMER_ID

Validation: 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_CUSTOMER_ID = 
HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_CONTACT_REF = 
RA_CONTACTS.ORIG_SYSTEM_REFERENCE

Destination: 
None

Optional/Conditional*

If it is necessary to capture customer contact information and your transaction batch source is Bill To contact = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing contact information you populate either ORIG_SYSTEM_BILL_CONTACT_REF or ORIG_SYSTEM_BILL_CONTACT_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 747900.1, AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID)

ORIG_SYSTEM_BILL_CONTACT_ID

This field contains contact Id for the customer you entered in either ORIG_SYSTEM_BILL_CUSTOMER_REF or 
ORIG_SYSTEM_BILL_CUSTOMER_ID

Validation: 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_CUSTOMER_ID = 
HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_BILL_CONTACT_ID = HZ_CUST_SITE_USES.CUSTOMER_SITE_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
BILL_TO_CONTACT_ID

Optional/Conditional*

If it is necessary to capture customer contact information and your transaction batch source is Bill To contact = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing contact information you populate either ORIG_SYSTEM_BILL_CONTACT_REF or ORIG_SYSTEM_BILL_CONTACT_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 747900.1>>, AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID)

ORIG_SYSTEM_SHIP_CUSTOMER_REF

This field contains the Ship To Customer Reference for this transaction.

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
ORIG_SYSTEM_REFERENCE

Destination: 
None

Optional/Conditional*

If the setup of your transaction batch source is Ship to Customer = Value:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Ship to information is optional, if you need to capture this information populate either ORIG_SYSTEM_SHIP_CUSTOMER_ID or ORIG_SYSTEM_SHIP_CUSTOMER_REF and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

ORIG_SYSTEM_SHIP_CUSTOMER_ID

This field contains the Ship To Customer Id for this transaction.

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
CUST_ACCOUNT_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
SHIP_TO_CUSTOMER_ID

Optional/Conditional*

If the setup of your transaction batch source is Ship to Customer = Id:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Ship to information is optional, if you need to capture this information populate either ORIG_SYSTEM_SHIP_CUSTOMER_ID or ORIG_SYSTEM_SHIP_CUSTOMER_REF and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

ORIG_SYSTEM_SHIP_ADDRESS_REF

This field contains the Address Reference associated to the Ship-To Customer entered in either ORIG_SYSTEM_SHIP_CUSTOMER_REF or 
ORIG_SYSTEM_SHIP_CUSTOMER_ID.

Validation: 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_ADDRESS_REF = 
HZ_PARTY_SITES. 
ORIG_SYSTEM_REFERENCE and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CUSTOMER_ID = 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID and 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = 
HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and 
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = 
HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and 
HZ_CUST_SITE_USES.SITE_USE_CODE = ‘SHIP_TO‘

Destination: 
None

Optional/Conditional*

If the setup of your transaction batch source is Ship to Address = Value:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Ship to information is optional, if you need to capture this information populate either ORIG_SYSTEM_SHIP_ADDRESS_REF or ORIG_SYSTEM_SHIP_ADDRESS_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 219868.1, AutoInvoice Error: The Supplied Ship To Address Reference Must Exist In Oracle Receivables And It Must Agree With The Supplied Ship To Customer (ORIG_SYSTEM_SHIP_ADDRESS_REF)

ORIG_SYSTEM_SHIP_ADDRESS_ID

This field contains the Address Id associated to the Ship-To Customer entered in either ORIG_SYSTEM_SHIP_CUSTOMER_REF or 
ORIG_SYSTEM_SHIP_CUSTOMER_ID.

Validation: RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_ADDRESS_ID = HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID 
and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CUSTOMER_ID = 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID and 
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = 
HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and 
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = 
HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and 
HZ_CUST_SITE_USES.SITE_USE_CODE = ‘SHIP_TO‘

Destination: 
RA_CUSTOMER_TRX_ALL. 
SHIP_TO_ADDRESS_ID

Optional/Conditional*

If the setup of your transaction batch source is Ship to Address = Id:

then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or line level ‘FREIGHT‘.

* Ship to information is optional, if you need to capture this information either in ORIG_SYSTEM_SHIP_ADDRESS_REF or ORIG_SYSTEM_SHIP_ADDRESS_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 262735.1, AutoInvoice Error: The supplied ship to address id must exist in Oracle Receivables, and it must agree with the supplied ship to customer (ORIG_SYSTEM_SHIP_ADDRESS_ID)

ORIG_SYSTEM_SHIP_CONTACT_REF

This field contains contact reference for the customer you entered in either ORIG_SYSTEM_SHIP_CUSTOMER_REF or 
ORIG_SYSTEM_SHIP_CUSTOMER_ID

Validation: RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CUSTOMER_ID = 
HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CONTACT_REF = 
HZ_CUST_ACCOUNT_ROLES. 
ORIG_SYSTEM_REFERENCE

Destination: 
None

Optional/Conditional*

If it is necessary to capture customer contact information and your transaction batch source is Ship To contact = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing contact information you populate either ORIG_SYSTEM_SHIP_CONTACT_REF or ORIG_SYSTEM_SHIP_CONTACT_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 747900.1, AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID)

ORIG_SYSTEM_SHIP_CONTACT_ID

This field contains contact Id for the customer you entered in either ORIG_SYSTEM_SHIP_CUSTOMER_REF or 
ORIG_SYSTEM_SHIP_CUSTOMER_ID

Validation: 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CUSTOMER_ID = 
HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and 
RA_INTERFACE_LINES_ALL. 
ORIG_SYSTEM_SHIP_CONTACT_ID = HZ_CUST_SITE_USES.CUSTOMER_SITE_ID

Destination: RA_CUSTOMER_TRX_ALL. 
SHIP_TO_CONTACT_ID

Optional/Conditional*

If it is necessary to capture customer contact information and your transaction batch source is Ship To contact = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing contact information you populate either ORIG_SYSTEM_SHIP_CONTACT_REF or ORIG_SYSTEM_SHIP_CONTACT_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 747900.1, AutoInvoice Error: The Bill To Contact Id Must Exist In Oracle Receivables, And It Must Be Assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID)

ORIG_SYSTEM_SOLD_CUSTOMER_REF

This field contains the Sold To Customer Reference

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
ORIG_SYSTEM_REFERENCE

Destination: 
None

Optional/Conditional*

If it is necessary to capture Sold-To information and your transaction batch source is Sold To Customer = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing Sold-To information you populate either ORIG_SYSTEM_SOLD_CUSTOMER_REF or ORIG_SYSTEM_SOLD_CUSTOMER_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 1161925.1, AutoInvoice Error: Invalid sold to customer reference (ORIG_SYSTEM_SOLD_CUSTOMER_REF)

ORIG_SYSTEM_SOLD_CUSTOMER_ID

This field contains the Sold To Customer Id

Validation: 
Must exist in 
HZ_CUST_ACCOUNTS. 
CUST_ACCOUNT_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
SOLD_TO_CUSTOMER_ID

Optional/Conditional*

If it is necessary to capture Sold-To information and your transaction batch source is Sold To Customer = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When capturing Sold-To information you populate either ORIG_SYSTEM_SOLD_CUSTOMER_REF or ORIG_SYSTEM_SOLD_CUSTOMER_ID and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1097660.1, Troubleshooting AutoInvoice Customer, Address and Contact Errors and Exceptions

Note 1161925.1, AutoInvoice Error: Invalid sold to customer reference (ORIG_SYSTEM_SOLD_CUSTOMER_REF)

BATCH_SOURCE_NAME

This field contains the name of the batch source for this transaction. AutoInvoice uses your batch source to determine your transaction and batch numbering method as well as AutoInvoice processing options.

Validation: 
Must exist in RA_BATCH_SOURCES_ALL.NAME 
and RA_BATCH_SOURCES_ALL. 
BATCH_SOURCE_TYPE = ‘FOREIGN‘

Destination: 
the batch name is used to derive an Id, which is stored in 
RA_BATCHES_ALL.BATCH_SOURCE_ID and 
RA_CUSTOMER_TRX_ALL.BATCH_SOURCE_ID

Mandatory

It is mandatory to provide a batch source name for every interface record created.

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

Note 1068008.1, Creating Transaction Batch Sources Used For AutoInvoice [Video]

SET_OF_BOOKS_ID

This field contains the ledger ID for this transaction.

Validation: 
Must exist in 
AR_SYSTEM_PARAMETERS_ALL. 
SET_OF_BOOKS_ID

Destination: 
RA_CUSTOMER_TRX_ALL.SET_OF_BOOKS_ID

Optional

If no value is provided, AutoInvoice defaults the ledger from the System Options window for the organization that is specified in the ORG_ID column.

LINE_TYPE

This field identifies the type of transaction line this record is.

Validation: 
Must be ‘LINE‘, ‘TAX‘, ‘FREIGHT‘ or ‘CHARGES‘

Destination: RA_CUSTOMER_TRX_LINES_ALL.LINE_TYPE

Mandatory

AutoInvoice cannot determine the type of line you are providing unless you populate this column with the proper value.

For Credit Memos, the value here should match the LINE_TYPE of the invoice line being credited.

DESCRIPTION

This field contains a string that provides a description of the transaction line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
DESCRIPTION

Mandatory
CURRENCY_CODE

This field contains the currency code for this transaction. You must enter a value in this column.

Validation: 
Must exist in FND_CURRENCIES. 
CURRENCY_CODE

Destination: 
RA_CUSTOMER_TRX_ALL. 
INVOICE_CURRENCY_CODE and 
AR_PAYMENT_SCHEDULES_ALL. 
INVOICE_CURRENCY_CODE

Mandatory

The value you enter here must exist in FND_CURRENCIES.CURRENCY_CODE

Reference: 
see common Currency related errors in 
Note 1089172.1, Troubleshooting Autoinvoice Import - Execution Report Errors (Request Status = Completed)

AMOUNT

For Invoices, this field contains the Revenue Amount associated to this transaction.

For Credit Memos, this field contains the amount to Credit.

Validation: 
If LINE_TYPE = ‘CHARGES‘, then this column must be 
null. AutoInvoice will correct revenue amounts that have 
the wrong currency precision.

Destination:

If Create Clearing is set to No for this transaction batch 
source (i.e., suspense/clearing account not used): 
RA_CUSTOMER_TRX_LINES_ALL. 
EVENUE_AMOUNT 
and 
RA_CUSTOMER_TRX_LINES_ALL. 
EXTENDED_AMOUNT.

If Create Clearing is set to Yes for this transaction batch 
source (suspense/clearing account used): 
RA_CUSTOMER_TRX_LINES_ALL. 
REVENUE_AMOUNT

Mandatory*

*A value should be provided for records with LINE_TYPE = LINE, 
TAX, FREIGHT

CUST_TRX_TYPE_NAME

This field contains the Transaction Type name of this transaction.

Validation: 
RA_CUST_TRX_TYPES_ALL. 
NAME

Destination: None

Mandatory/Conditional*

If your transaction batch source is Transaction Type = Value, then populate this field, otherwise leave it null.

* When providing transaction type information you populate either CUST_TRX_TYPE_NAME or CUST_TRX_TYPE_ID, and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1090878.1, Troubleshooting Transaction Types In Oracle Receivables

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

CUST_TRX_TYPE_ID

This field contains the Transaction Type Id of this transaction.

Validation: 
Must exist in 
RA_CUST_TRX_TYPES_ALL. 
CUST_TRX_TYPE_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
CUST_TRX_TYPE_ID

Mandatory/Conditional*br /> 
If your transaction batch source is Transaction Type = Id, then populate this field, otherwise leave it null.

* When providing transaction type information you populate either CUST_TRX_TYPE_NAME or CUST_TRX_TYPE_ID, and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1090878.1, Troubleshooting Transaction Types In Oracle Receivables

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

TERM_NAME

This field contains the payment term name for this transaction

Validation: 
Must exist in RA_TERMS.NAME

Destination: 
None

Mandatory/Conditional*

If your transaction batch source is Payment Terms = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When providing payment terms information you populate either TERM_NAME or TERM_ID, and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1083494.1, Troubleshooting Payment Terms In AutoInvoice

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

TERM_ID

This field contains the payment term Id for this transaction

Validation: 
Must exist in RA_TERMS.TERM_ID

Destination: 
RA_CUSTOMER_TRX_ALL.TERM_ID

Mandatory/Conditional*

If your transaction batch source is Payment Terms = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When providing payment terms information you populate either TERM_NAME or TERM_ID, and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1083494.1, Troubleshooting Payment Terms In AutoInvoice

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

RECEIPT_METHOD_NAME

This field contains the name of the Payment Method associated to this transaction. Providing information in this field allows this transaction to be processed by Automatic Receipts later on.

Validation: 
Must exist in AR_RECEIPT_METHODS.NAME 
and must belong to the bill-to customer or the parent.

Destination: 
None

Optional/Conditional*

If you want this transaction to be processed for payment later on by the Automatic Receipts process, then populate the Payment Method information. Otherwise, you can leave this field blank. When not provided, AutoInvoice always defaults the payment method using the following hierarchy:
1. primary receipt method of the parent primary bill-to site 
2. primary receipt method of the parent customer 
3. primary receipt method of the bill-to site 
4. primary receipt method of the bill-to customer

Depending on your transaction batch source setup, if Payment Method = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When providing payment method information you populate either RECEIPT_METHOD_NAME or RECEIPT_METHOD_ID, and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1071284.1, Setting Up Receipt Class And Method For AutoInvoice

Note 1098583.1, Troubleshooting AutoInvoice Receipt Method, Payment Method, Credit Card and Bank Account Errors

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

RECEIPT_METHOD_ID

This field contains the name of the Payment Method Id associated to this transaction. Providing information in this field allows this transaction to be processed by Automatic Receipts later on.

Validation: 
exist in 
AR_RECEIPT_METHODS. 
RECEIPT_METHOD_ID and 
must belong to the bill-to customer or the parent.

Additionally, the receipt method must have at least one 
bank account in the same currency as the transaction or 
have its Receipts Multi-Currency flag set to Yes

Destination: 
RA_CUSTOMER_TRX_ALL. 
RECEIPT_METHOD_ID

Optional/Conditional*

If you want this transaction to be processed for payment later on by the Automatic Receipts process, then populate the Payment Method information. Otherwise, you can leave this field blank. When not provided, AutoInvoice always defaults the payment method using the following hierarchy:
1. primary receipt method of the parent primary bill-to site 
2. primary receipt method of the parent customer 
3. primary receipt method of the bill-to site 
4. primary receipt method of the bill-to customer

Depending on your transaction batch source setup, if Payment Method = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

* When providing payment method information you populate either RECEIPT_METHOD_NAME or RECEIPT_METHOD_ID, and what field you are required populate is dependent upon your transaction batch source setup.

Reference: 
Note 1071284.1, Setting Up Receipt Class And Method For AutoInvoice

Note 1098583.1, Troubleshooting AutoInvoice Receipt Method, Payment Method, Credit Card and Bank Account Errors

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

CONVERSION_TYPE

Enter the exchange rate type for this transaction.

Validation: 
Must exist in GL_DAILY_CONVERSION_TYPES. 
CONVERSION_TYPE

Destination: 
RA_CUSTOMER_TRX_ALL. 
EXCHANGE_RATE_TYPE

Mandatory

If the currency of the transaction is the same as the functional currency, set EXCHANGE_RATE_TYPE = ‘User‘

CONVERSION_DATE

Enter the exchange rate date for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
EXCHANGE_DATE

Optional

If the currency of the transaction is the same as the functional currency, leave this field blank. Otherwise, enter the exchange rate date for this transaction.

If a date is required but is not provided, then AutoInvoice will do the following:

  • for an Invoice, it uses the transaction date as the default
  • for a Credit Memo, it uses the conversion date of the invoice being credited
CONVERSION_RATE

Enter the exchange rate for this transaction.

Validation: 
If RA_INTERFACE_LINES_ALL. 
CONVERSION_TYPE = ‘User‘ then this column must
not be null; otherwise, it must be null.

Destination: 
RA_CUSTOMER_TRX_ALL. 
EXCHANGE_RATE

Mandatory/Conditional*

If EXCHANGE_RATE_TYPE = ‘User‘ then you must provide a value in this field, If the currency of the transaction is the same as the functional currency, 
set CONVERSION_RATE to 1.

If EXCHANGE_RATE_TYPE <> ‘User‘ leave this field blank, the rate will be picked up from the Currency rate table for the CONVERSION_DATE provided.

CUSTOMER_TRX_ID

This column is used by AutoInvoice and should be left null. AutoInvoice populates a value into this column once it has determined how to group transaction lines using your grouping rules.

Validation: 
None

Destination: 
CUSTOMER_TRX_ID in the following tables: 
RA_CUSTOMER_TRX_ALL 
AR_PAYMENT_SCHEDULES_ALL 
RA_CUSTOMER_TRX_LINES_ALL 
RA_CUST_TRX_LINE_GL_DIST_ALL

Never

Users should not populate this field. AutoInvoice process takes care of generating a value in this field.

TRX_DATE

Enter the transaction date for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL.TRX_DATE

Optional/Conditional*

When using an Invoicing Rule in Arrears, leave this column blank.

For an invoice or debit memo, enter the invoice date. 
For a Credit Memo, enter the date to credit the transaction

When this field is left null, AutoInvoice does the following: 
For an invoice/debit memo - use the general ledger date 
For a credit memo - use the following hierarchy: 
1. credit memo general ledger date 
2. general ledger date for the REC distribution of the invoice being credited 
3. Run date of AutoInvoice  
whichever is later.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

Reference: 
Note 201241.1, Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date, Rule Date

Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

GL_DATE

Enter the date you want to use for this transaction to get posted to the General Ledger

Validation: 
Must be in an open or future enterable accounting period 
and the period must exist in GL_PERIOD_STATUSES. 
If ‘Post To GL‘ is set to No on the transaction type of the 
transaction being passed, column must be NULL.
If your invoice uses Bill in Arrears as the invoicing rule, 
then the GL_DATE column should be NULL.

Destination: 
RA_CUST_TRX_LINE_GL_DIST_ALL.GL_DATE

Optional/Conditional*

This column should be left null for:

  • transaction types with Post To GL = No
  • Invoices with Rules
  • LINE_TYPE = TAX or FREIGHT

You may optionally populate this field for:

  • LINE_TYPE = LINE or CHARGES
  • Header Level Freight

Reference: 
Note 201241.1, Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date, Rule Date

DOCUMENT_NUMBER

Contains the document number for this transaction.

Validation: 
Number must not already exist in Oracle Receivables

Destination: 
RA_CUSTOMER_TRX_ALL. 
DOC_SEQUENCE_VALUE

Conditional

Depending upon the type of document sequence associated to this transaction type, if set to:

  • Automatic, then you should not provide a value in this column.
  • Manual, then you should provide a value in this column

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
Note 1086565.1, How To Setup Document Sequences In Receivables

TRX_NUMBER

Contains the transaction number for this transaction.

Validation: 
not already exist in 
RA_CUSTOMER_TRX_ALL.TRX_NUMBER for 
the same BATCH_SOURCE_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
TRX_NUMBER and 
AR_PAYMENT_SCHEDULES_ALL. 
TRX_NUMBER

Conditional

Depending upon your transaction batch source setup, if Automatic Transaction Numbering is:

  • checked, then you should not provide a value for this column
  • unchecked, then you should provide a value for this column

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

LINE_NUMBER

Contains a line number identifier.

N/A Never

Users should not populate this field. The AutoInvoice process takes care of providing a value in this field, and uses the Line Ordering logic provided in the Line Ordering Rule.

QUANTITY

Contains the quantity

Validation: 
For Debit Memos lines with LINE_TYPE = ‘CHARGES‘, 
quantity must be 1. 
For Credit Memo lines with LINE_TYPE = ‘CHARGES‘, 
this column must be 1 or -1. 
For Credit Memo lines with LINE_TYPE = ‘LINE‘ and 
CREDIT_METHOD_FOR_ACCT_RULE = ‘UNIT‘ then this
column must not be null.

Destination: 
for an invoice: 
RA_CUSTOMER_TRX_LINES_ALL. 
QUANTITY_INVOICED

for a credit memo: 
RA_CUSTOMER_TRX_LINES_ALL. 
QUANTITY_CREDITED

Conditional

This field contains units shipped for an invoice and units credited for a credit memo. When this field is provided, AutoInvoice uses this value multiplied with  UNIT_SELLING_PRICE to determine the line AMOUNT.

This field is Mandatory for credit memos if CREDIT_METHOD_FOR_ACCT_RULE = UNIT

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

QUANTITY_ORDERED

Contains the original number of units ordered for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
QUANTITY_ORDERED

Optional

For Credit memos, do not enter a value, as AutoInvoice will reference the invoice being credited.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

UNIT_SELLING_PRICE

Contains the selling price per unit for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
UNIT_SELLING_PRICE

Conditional

This field contains price per unit, when this field is provided and AMOUNT is null, then AutoInvoice uses this value multiplied by QUANTITY to determine the line AMOUNT.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

UNIT_STANDARD_PRICE

Contains the standard price per unit for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
UNIT_STANDARD_PRICE

Optional

This field should not be populated for Credit memos.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘

PRINTING_OPTION

Contains the Printing Option associated to this transaction.

Validation: 
Must exist in AR_LOOKUPS.LOOKUP_CODE and 
AR_LOOKUP.LOOKUP_TYPE = 
‘INVOICE_PRINT_OPTIONS‘

Destination: 
RA_CUSTOMER_TRX_ALL. 
PRINTING_OPTION

Optional

When not provided, AutoInvoice uses the value setup for the transaction type.

INTERFACE_STATUS

Contains the Status of an Interface record:

  • null = new (unprocessed) 
    Note: Interface records with errors, may also have a value null, and  corresponding record(s) in RA_INTERFACE_ERRORS_ALL
  • P = Purge (these rows have been processed and can be purged)
N/A Never

Users should not populate this field. The AutoInvoice process takes care of providing a value in this field and sets it to ‘P‘ when a record has been processed and can be purged by the system.

REQUEST_ID

Contains the Concurrent Request Id of the AutoInvoice process

Validation: 
None

Destination: 
The REQUEST_ID column in the following tables:
RA_CUSTOMER_TRX_ALL 
RA_CUSTOMER_TRX_LINES_ALL 
RA_CUST_TRX_LINE_GL_DIST_ALL 
AR_PAYMENT_SCHEDULES_ALL 
AR_RECEIVABLE_APPLICATIONS_ALL 
AR_ADJUSTMENTS_ALL 
RA_CUST_TRX_LINE_SALESREPS_ALL

Never

Users should not populate this field.  AutoInvoice takes care of generating a value for this field during the import process.

RELATED_BATCH_SOURCE_NAME

Contains the batch source name of a related transaction.

Validation: 
RA_INTERFACE_LINES_ALL. 
RELATED_BATCH_SOURCE_NAME = RA_BATCH_SOURCES_ALL.NAME and 
RA_INTERFACE_LINES_ALL. 
RELATED_TRX_NUMBER 
= RA_CUSTOMER_TRX_ALL. 
TRX_NUMBER and 
RA_BATCH_SOURCES_ALL. 
BATCH_SOURCE_ID = 
RA_CUSTOMER_TRX_ALL. 
BATCH_SOURCE_ID

Destination: 
None

Optional

For business reasons, you may need to "relate" one transaction to another, by providing either: 
RELATED_CUSTOMER_TRX_ID or 
RELATED_BATCH_SOURCE_NAME + RELATED_TRX_NUMBER

If you are relating this transaction to another, and you are not providing a RELATED_CUSTOMER_TRX_ID, then you must provide a value in this field, so that AutoInvoice can identify a unique transaction by TRX_NUMBER and BATCH_SOURCE_NAME.

For credit memos, leave this field blank.

RELATED_TRX_NUMBER

Contains transaction number of a related transaction.

Validation: 
RA_INTERFACE_LINES_ALL. 
RELATED_BATCH_SOURCE_NAME = RA_BATCH_SOURCES_ALL.NAME and 
RA_INTERFACE_LINES_ALL. 
RELATED_TRX_NUMBER 
= RA_CUSTOMER_TRX_ALL. 
TRX_NUMBER and 
RA_BATCH_SOURCES_ALL. 
BATCH_SOURCE_ID = 
RA_CUSTOMER_TRX_ALL. 
BATCH_SOURCE_ID

Destination: 
None

Optional

For business reasons, you may need to "relate" one transaction to another, by providing either: 
RELATED_CUSTOMER_TRX_ID or 
RELATED_BATCH_SOURCE_NAME + RELATED_TRX_NUMBER

If you are relating this transaction to another, and you are not providing a RELATED_CUSTOMER_TRX_ID, then you must provide a value in this field, so that AutoInvoice can identify a unique transaction by TRX_NUMBER and BATCH_SOURCE_NAME.

For credit memos, leave this field blank.

RELATED_CUSTOMER_TRX_ID

Contains transaction ID of a related transaction.

Validation: 
Must exist in 
RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID

Destination: 
RA_CUSTOMER_TRX_ALL. 
RELATED_CUSTOMER_TRX_ID

Optional

For business reasons, you may need to "relate" one transaction to another, by providing either: 
RELATED_CUSTOMER_TRX_ID or 
RELATED_BATCH_SOURCE_NAME + RELATED_TRX_NUMBER

For credit memos, leave this field blank.

PREVIOUS_CUSTOMER_TRX_ID

Contains the transaction ID of the transaction being credited.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
PREVIOUS_CUSTOMER_TRX_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field to point to the invoice being credited once it has identified the ID via the values in the REFERENCE_LINE_ATTRIBUTE fields.

CREDIT_METHOD_FOR_ACCT_RULE

This contains the method for crediting a transaction which uses an accounting rule.

Validation: 
Must be either ‘PRORATE‘, ‘LIFO‘, ‘UNIT‘ or NULL

Destination: 
RA_CUSTOMER_TRX_ALL. 
CREDIT_METHOD_FOR_RULES

Mandatory for Credit Memos against Invoices with Rules

This field is only used by credit memos against invoices with rules.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
Note 1110573.1, Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables

CREDIT_METHOD_FOR_INSTALLMENTS

This contains the method for crediting a transaction that uses split payment terms.

Validation: 
Must be either ‘PRORATE‘, ‘LIFO‘, ‘FIFO‘ or NULL.

Destination: 
RA_CUSTOMER_TRX_ALL. 
CREDIT_METHOD_FOR_INSTALLMENTS

Mandatory for Credit Memos against Invoices with Installments

This field is only used by credit memos against invoices with installments.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
Note 1110573.1, Troubleshooting Credit Memos in the Transaction Workbench and AutoInvoice in Receivables

REASON_CODE

Contains the credit memo reason code for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
REASON_CODE and 
RA_CUSTOMER_TRX_ALL. 
REASON_CODE

Optional/Conditional*

Only for Credit Memos

If your transaction batch source is setup with Memo Reason = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the reason for a credit memo, populate either REASON_CODE or REASON_CODE_MEANING, and what field you are required populate is dependent upon your transaction batch source setup

REASON_CODE_MEANING

Contains the meaning of the reason code for this transaction.

Validation: 
Must exist in AR_LOOKUPS.MEANING. This lookup type 
is either INVOICING_REASON or 
CREDIT_MEMO_REASON

Destination: 
None

Optional/Conditional*

Only for Credit Memos

If your transaction batch source is setup with Memo Reason = Value, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ 
or for line level ‘FREIGHT‘.

* When providing the reason for a credit memo, populate either REASON_CODE or REASON_CODE_MEANING, and what field you are required populate is dependent upon your transaction batch source setup

EXCEPTION_ID

Contains a tax exception id.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
ITEM_EXCEPTION_RATE_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field when a tax exception occurs.

EXEMPTION_ID

Contains a tax exemption id.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
TAX_EXEMPTION_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field when this transaction is partially or fully exempt from tax.

SHIP_DATE_ACTUAL

Contains the shipment date for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
SHIP_DATE_ACTUAL

Optional

If you want to capture the Shipment date, enter a value. For credit memos, AutoInvoice uses the earliest shipment date from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

FOB_POINT

Contains Enter the freight on board point for this transaction.

Validation: 
Must exist in AR_LOOKUPS.LOOKUP_CODE and 
AR_LOOKUPS.LOOKUP_TYPE = ‘FOB‘.

Destination: 
RA_CUSTOMER_TRX_ALL.FOB_POINT

Optional

If you want to capture FOB information, enter a value. For credit memos, AutoInvoice uses the FOB point from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

SHIP_VIA

Enter the ship via code for shipping carrier of this transaction.

Validation: ORG_FREIGHT.FREIGHT_CODE = 
RA_INTERFACE_LINES_ALL.SHIP_VIA and 
ORG_FREIGHT.ORGANIZATION_ID = 
RA_INTERFACE_LINES_ALL.WAREHOUSE_ID.

Destination: RA_CUSTOMER_TRX_ALL.SHIP_VIA

Optional

If you want to capture Carrier information, enter a value. For credit memos, AutoInvoice uses the ship via code from the transaction you are crediting

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
Note 1096942.1, How To Setup And Troubleshoot Freight In AutoInvoice And The Transactions Form

WAYBILL_NUMBER

Contains the waybill number for this transaction.

Validation: None 
Destination: RA_CUSTOMER_TRX_ALL.WAYBILL
Optional

If you want to capture waybill information, enter a value. For credit memos, AutoInvoice uses the waybill number from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

INVOICING_RULE_NAME

Contains the invoicing rule name for this transaction.

Validation: 
Must exist in RA_RULES.NAME and 
RA_RULES.RULE_ID = -2 or -3.

If INVOICING_RULE_ID is not null, then this field must 
also be populated.

If LINE_TYPE = ‘CHARGES‘ then this column must be null.

Destination: 
None

Optional/Conditional*

Only for transactions with Invoicing rules.

If your transaction batch source is setup with Invoicing Rule = Value, then populate this field, otherwise leave it null. Valid values are: ‘Advance Invoice‘ and ‘Arrears Invoice‘

For credit memos, AutoInvoice uses the invoicing rule from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Invoicing Rule, populate either 
INVOICING_RULE_NAME or INVOICING_RULE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

INVOICING_RULE_ID

Enter the invoicing rule ID for this transaction.

Validation: 
Must exist in RA_RULES.RULE_ID and 
RA_RULES.RULE_ID = -2 or -3.

If INVOICING_RULE_ID is not null, then this field must 
also be populated.

If LINE_TYPE = ‘CHARGES‘ then this column must be null.

Destination: 
RA_CUSTOMER_TRX_ALL. 
INVOICING_RULE_ID

Optional/Conditional*

Only for transactions with Invoicing rules.

If your transaction batch source is setup with Invoicing Rule = Id, then populate this field, otherwise leave it null. Valid values are: -2 (for Advance Invoice) and -3 (for Arrears Invoice)

For credit memos, AutoInvoice uses the invoicing rule from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Invoicing Rule, populate either INVOICING_RULE_NAME or INVOICING_RULE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

ACCOUNTING_RULE_NAME

Contains the accounting rule name for this transaction.

Validation: 
Must exist in RA_RULES.NAME and 
RA_RULES.TYPE = ‘A‘ or ‘ACC_DUR‘

Destination: 
None

Optional/Conditional*

Only for transactions with Invoicing rules.

If your transaction batch source is setup with Accounting Rule = Value, then populate this field, otherwise leave it null.

For credit memos, AutoInvoice uses the accounting rule from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Accounting Rule, populate either ACCOUNTING_RULE_NAME or ACCOUNTING_RULE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

ACCOUNTING_RULE_ID

Contains the accounting rule ID for this transaction.

Validation: 
Must exist in RA_RULES.RULE_ID and 
RA_RULES.TYPE = ‘A‘ or ‘ACC_DUR‘

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
ACCOUNTING_RULE_ID

Optional/Conditional*

Only for transactions with Invoicing rules.

If your transaction batch source is setup with Accounting Rule = Id, then populate this field, otherwise leave it null.

For credit memos, AutoInvoice uses the accounting rule from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Accounting Rule, populate either ACCOUNTING_RULE_NAME or ACCOUNTING_RULE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

ACCOUNTING_RULE_DURATION

Contains the accounting duration for this transaction.

Validation: 
Accounting periods must be defined for the duration of the accounting rule in GL_PERIODS and 
RA_INTERFACE_LINES_ALL.GL_DATE and 
RA_INTERFACE_LINES_ALL.RULE_START_DATE 
must be in a period that has a status of ‘Open‘ or ‘Future‘. 
The value in this column must be a positive integer.

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
ACCOUNTING_RULE_DURATION

Mandatory for Invoices with Variable Duration Rules

If an invoice is using an Accounting rule with a variable duration, AutoInvoice cannot derive the number of periods from the rule alone, which is why you need to provide a value.

For credit memos, do not populate this field.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

RULE_START_DATE

Contains the date that you want to start the accounting rule for this transaction.

Validation: None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
RULE_START_DATE

Optional

Only relevant for Invoices using Accounting Rules.

If your rule is defined with Specific Date, do not enter a value in this column.

If not provided, AutoInvoice will derive the Rule Start date.

For credit memos do not enter a value in this column.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
Note 1116934.1, How To Setup And Troubleshoot Invoicing Rules and Accounting Rules

RULE_END_DATE

Enter the date that you want to end the accounting rule for this transaction. 
This column is required if the accounting rule is either Daily Revenue Rate, All Periods or Daily Revenue Rate, Partial Periods.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
RULE_END_DATE

Conditional

If your invoice is using Accounting Rules that have type: 
Daily Revenue Rate, All Periods or 
Daily Revenue Rate, Partial Periods then you need to pass in a value for this field in records where LINE_TYPE = LINE.

For credit memos do not enter a value in this column.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘

Reference: 
For more information about rule start dates, see: Determining Dates, Oracle Receivables 
User Guide.

PRIMARY_SALESREP_NUMBER

Contains the primary salesperson number for this transaction.

Validation: 
Must exist in RA_SALESREPS. 
SALESREP_NUMBER

Destination: None

Conditional*

If your system options is setup to Require Salesperson then this field is Mandatory.

If your transaction batch source is setup with Salesperson = Number, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Salesperson information, populate either PRIMARY_SALESREP_NUMBER or PRIMARY_SALESREP_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

PRIMARY_SALESREP_ID

Contains the primary salesperson ID for this transaction.

Validation: 
Must exist in RA_SALESREPS. 
SALESREP_ID

Destination: RA_CUSTOMER_TRX_ALL. 
PRIMARY_SALESREP_ID

Conditional*

If your system options is setup to Require Salesperson then this field is Mandatory.

If your transaction batch source is setup with Salesperson = Id, then populate this field, otherwise leave it null.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing the Salesperson information, populate either PRIMARY_SALESREP_NUMBER or PRIMARY_SALESREP_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

SALES_ORDER

Contains the Sales order number for this transaction. If you are using Oracle Order Management, this provides a link back to the Order.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL. 
SALES_ORDER

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the sales order number from the transaction you are crediting.

SALES_ORDER_LINE

Contains sales order line number for this transaction. If you are using Oracle Order Management, this provides a link back to the Order line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
SALES_ORDER_LINE

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the sales order line number from the transaction you are crediting.

SALES_ORDER_DATE

Contains the date of the sales order for this transaction.If you are using Oracle Order Management, this provides a link back to the Order date.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
SALES_ORDER_DATE

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the sales order date  from the transaction you are crediting.

SALES_ORDER_SOURCE

Contains the source of the sales order for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
SALES_ORDER_SOURCE

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the source of the sales order from the transaction you are crediting.

SALES_ORDER_REVISION

Contains the sales order revision for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
SALES_ORDER_REVISION

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the revision of the sales order from the transaction you are crediting.

PURCHASE_ORDER

Contains the purchase order number for this transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_ALL. 
PURCHASE_ORDER

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the purchase order from the transaction you are crediting.

PURCHASE_ORDER_REVISION

Contains the purchase order revision for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
PURCHASE_ORDER_REVISION

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the revision of the purchase order from the transaction you are crediting.

PURCHASE_ORDER_DATE

Contains the date of the purchase order for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
PURCHASE_ORDER_DATE

Optional

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

For credit memos, AutoInvoice uses the purchase order date from the transaction you are crediting.

AGREEMENT_NAME

Contains the name of the customer agreement for this transaction.

Validation: 
Must exist in SO_AGREEMENTS.NAME

Destination: 
None

Optional/Conditional*

If your transaction batch source is setup with Agreement = Value, then populate this field, otherwise leave it null.

If a value is not provided, and the invoice is drawn against a commitment that has an agreement,  AutoInvoice will use this agreement information.

For credit memos, AutoInvoice uses the customer agreement from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Agreement information, populate either AGREEMENT_NAME or AGREEMENT_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

AGREEMENT_ID

Contains the customer agreement ID for this transaction.

Validation: 
Must exist in SO_AGREEMENTS.ID

Destination: 
None

Optional/Conditional*

If your transaction batch source is setup with Agreement = Id, then populate this field, otherwise leave it null.

If a value is not provided, and the invoice is drawn against a commitment that has an agreement, AutoInvoice will use this agreement information.

For credit memos, AutoInvoice uses the customer agreement from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Agreement information, populate either AGREEMENT_NAME or AGREEMENT_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

MEMO_LINE_NAME

Contains the name of the standard memo line for this transaction.

Validation: 
Must exist in AR_MEMO_LINES_ALL.NAME

Destination: 
None

Optional/Conditional*

If your transaction batch source is setup with Memo Line Rule = Value, then populate this field, otherwise leave it null.

For credit memos, AutoInvoice uses the memo line from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Memo Line information, populate either MEMO_LINE_NAME or MEMO_LINE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

MEMO_LINE_ID

Contains the standard memo line ID for this transaction.

Validation: 
Must exist in AR_MEMO_LINES_ALL. 
MEMO_LINE_ID

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
MEMO_LINE_ID

Optional/Conditional*

If your transaction batch source is setup with Memo Line Rule = Id, then populate this field, otherwise leave it null.

For credit memos, AutoInvoice uses the memo line Id from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Memo Line information, populate either MEMO_LINE_NAME or MEMO_LINE_ID and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

COMMENTS

Contains comments.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL.COMMENTS

Optional

Enter additional comments you‘d like to capture.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

INTERNAL_NOTES

Contains internal notes for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
INTERNAL_NOTES

Optional

Enter internal notes you‘d like to capture.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

INITIAL_CUSTOMER_TRX_ID

Contains the CUSTOMER_TRX_ID identifying the deposit or commitment from which this transaction is drawn from..

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
INITIAL_CUSTOMER_TRX_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field with the CUSTOMER_TRX_ID of the commitment or deposit drawn from by the invoice.

USSGL_TRANSACTION_CODE_CONTEXT

This column is not currently used by AutoInvoice.

N/A Never

This field is currently not used.

USSGL_TRANSACTION_CODE

Contains the Federal/Government transaction code for this transaction.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
DEFAULT_USSGL_TRANSACTION_CODE

Optional
ACCTD_AMOUNT

Do not enter a value. Receivables does not currently use this column.

N/A Never

This field is currently not used.

CUSTOMER_BANK_ACCOUNT_ID

This column is obsolete in R12.

N/A Obsolete

See information listed in PAYMENT_TRXN_EXTENSION_ID below.

CUSTOMER_BANK_ACCOUNT_NAME

This column is obsolete in R12.

N/A Obsolete

See information listed in PAYMENT_TRXN_EXTENSION_ID below.

UOM_CODE

Contains the unit of measure code for this transaction.

Validation: 
Must exist in MTL_UNITS_OF_MEASURE. 
UOM_CODE. If

Destination: RA_CUSTOMER_TRX_LINES_ALL.UOM_CODE

Conditional*

If your transaction batch source is setup with Unit of Measure = Id, then populate this field, otherwise leave it null.

If you provide data in INVENTORY_ITEM_ID or MTL_SYSTEM_ITEMS_SEG* fields, then you must provide a value in UOM_CODE or UOM_NAME (depending on you batch source setup).

For credit memos, AutoInvoice uses the unit of 
measure from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Bank Account information, populate either UOM_CODE or UOM_NAME and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1132807.1, Troubleshooting Unit of Measure Issues with AutoInvoice

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

UOM_NAME

Contains the unit of measure name for this transaction.

Validation: 
Must exist in 
MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE

Destination: 
None

Conditional*

If your transaction batch source is setup with Unit of Measure = Value, then populate this field, otherwise leave it null.

If you provide data in INVENTORY_ITEM_ID or MTL_SYSTEM_ITEMS_SEG* fields, then you must provide a value in UOM_CODE or UOM_NAME (depending on you batch source setup).

For credit memos, AutoInvoice uses the unit of 
measure from the transaction you are crediting.

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

* When providing Bank Account information, populate either UOM_CODE or UOM_NAME and what field you are required populate is dependent upon your transaction batch source setup

Reference: 
Note 1132807.1, Troubleshooting Unit of Measure Issues with AutoInvoice

Note 1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice

DOCUMENT_NUMBER_SEQUENCE_ID

Contains the document sequence ID for this transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_ALL. 
DOCUMENT_SEQUENCE_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field if applicable, once it determines the Document Sequence associated to this transaction.

Reference: 
Note 1086565.1, How To Setup Document Sequences In Receivables

VAT_TAX_ID

Contains the VAT tax ID of the transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL.VAT_TAX_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field if applicable.

LAST_PERIOD_TO_CREDIT

Contains the last period number from which you want to start 
crediting. This is only valid for Credit Memos using Credit Method = ‘UNIT‘

Validation: 
Must be between 0 and the invoice‘s accounting rule 
duration (inclusive).

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
LAST_PERIOD_TO_CREDIT

Conditional

This is only for Credit memos that have CREDIT_METHOD_FOR_ACCT_RULE = ‘UNIT‘

This field should not be populated for records with LINE_TYPE = ‘TAX‘ or for line level ‘FREIGHT‘.

PAYING_CUSTOMER_ID

Contains the Customer ID of the customer who is paying for this transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_ALL.PAYING_CUSTOMER_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field once it determines the Paying customer information.

PAYING_SITE_USE_ID

Contains the Site ID of the customer who is paying for this transaction

Destination: RA_CUSTOMER_TRX_ALL.PAYING_SITE_USE_ID

Validation: 
None

Destination: RA_CUSTOMER_TRX_ALL.PAYING_SITE_USE_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field once it determines the Paying customer‘s Site information.

SALES_TAX_ID

Contains the Sales Tax Id of the transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL.SALES_TAX_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field once it determines the Paying customer information.

CREATED_BY 
CREATION_DATE 
LAST_UPDATED_BY 
LAST_UPDATE_DATE 
LAST_UPDATE_LOGIN

Contains information to help audit when/who created/updated information.

Validation: 
None

Destination: 
None

Never

Users should not populate these fields. The AutoInvoice process takes care of deriving and populating these fields using the information from the system date and User Id.

LOCATION_SEGMENT_ID

Contains the Location Segment Id of the transaction.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL. 
LOCATION_SEGMENT_ID

Never

Users should not populate this field. AutoInvoice defaults a value into this column if you are crediting a sales tax line.

MOVEMENT_ID

Contains the Intrastate movement ID number that is tied to 
the shipment information.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL. 
MOVEMENT_ID

Optional

If you need to capture information on the movement statistics that are tied to the shipment 
information and passed through AutoInvoice populate this column.

ORG_ID

Contains the ID of the organization that this transaction belongs to.

Validation: 
ORG_ID should match the value of the MO: Operating Unit profile option

Destination: None:

Mandatory*

This column is mandatory in a multiple organization environment.

AMOUNT_INCLUDES_TAX_FLAG

Flag that controls whether the amount for this transaction line includes tax.

Validation: 
If this is a tax code and Allow Override is set to No, this 
should be equal to either the setting of the Amount 
Includes Tax option for this tax code or null. Additionally, 
if Allow Override is set to No the Amount Includes Tax 
flag at the line level must equal the Allow Override flag for 
this tax code.

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
AMOUNT_INCLUDES_TAX_FLAG

Optional

If this column is set to ‘Y‘, this line is assigned to a tax inclusive tax code. If this is a tax group, this column should be null.

AutoInvoice only uses this column if the tax code assigned to this line has Allow Override set to Yes for the Tax Inclusive calculation.

Populate this column for invoices only.

For regular credit memos, AutoInvoice always 
uses the AMOUNT_INCLUDES_TAX_FLAG value from the invoice that you are 
crediting.

RESET_TRX_DATE_FLAG

Flag the indicates whether the transaction date should be reset upon failure or not.

Validation: 
Y or N

Destination: 
None

Optional

When set to Y, and AutoInvoice rejects an invoice line and re-import is not done on the same day, then AutoInvoice will null out the provided data in TRX_DATE and re-derive it for the current date. This is done to ensure that TRX_DATE and GL_DATE are synchronized.

When set to N, AutoInvoice retains the value passed in TRX_DATE.

PAYMENT_SERVER_ORDER_NUM

This column is obsolete in R12.

N/A Obsolete

See information listed in PAYMENT_TRXN_EXTENSION_ID below.

APPROVAL_CODE

This column is obsolete in R12.

N/A Obsolete

See information listed in PAYMENT_TRXN_EXTENSION_ID below.

ADDRESS_VERIFICATION_CODE

Contains the credit card address verification code provided by Oracle Payment Server.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
ADDRESS_VERIFICATION_CODE

Optional/Conditional*

When importing transactions associated to payments via a Credit Card, you can populate this field.

WAREHOUSE_ID

Identifies the ship-from location and can be used to control taxation.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
WAREHOUSE_ID

Optional

When passing in INVENTORY_ITEM_ID, you need to provide warehouse Id information for LINE_TYPE = LINE.

Within the US, the Warehouse ID is important when calculating tax on the Origin / Modified Origin state sales tax. Outside the US, you can use Tax Groups and Conditions to build a schedule of multiple conditional taxes based on both the 
ship-from and ship-to County/County/State or Provinces.

Reference: 
Note 1089026.1, AutoInvoice Error: Invalid Warehouse ID (WAREHOUSE_ID) (xxx)

TRANSLATED_DESCRIPTION

Contains text for an alternate or translated (in another language, for MLS installations) description of this transaction line

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
TRANSLATED_DESCRIPTION

Optional:

If necessary, you can capture an alternate description or a translated description for an Invoice line.

CONS_BILLING_NUMBER

Contains the consolidated billing number..

Validation: 
Must not already exist in 
AR_CONS_INV_ALL.CONS_BILLING_NUMBER and 
AR_CONS_INV_ALL.CONS_INV_TYPE=‘MINV‘

Destination: AR_CONS_INV_ALL.CONS_BILLING_NUMBER

Optional

If using the Balance Forward Billing feature, and the consolidated bill has been generated outside of the Oracle Receivables application, and you need to capture this information, then you should pass in a value.

BILLING_DATE

Contains the Billing date used for this transaction

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
BILLING_DATE

Optional/Conditional

If using the Balance Forward Billing feature, and the billing cycle associated to the payment term of this transaction has Billing type:

  • EVENT, then you are required to pass in a Billing date
  • RECURRING, then you should not pass in a value and AutoInvoice handles deriving the billing_date for you.
PROMISED_COMMITMENT_AMOUNT

Contains the amount of an existing deposit to use as payment towards a specific transaction.

Validation: None

Destination: None

Optional

When an order is imported into Receivables with a value in this column, Receivables adjusts the resulting invoice‘s remaining balance and reduces the deposit balance by the lesser of the promised amount, the commitment balance, or the remaining amount due on the invoice.

If this column has no value, then the commitment adjustment will be for the lesser of the total outstanding commitment or the total balance of the transaction.

PAYMENT_SET_ID

Contains a unique internal ID number that matches prepaid invoices with 
their prepayment receipts. This column should be populated only within a 
prepayments flow.

Validation: 
Must exist in AR_RECEIVABLE_APPLICATIONS_ALL. 
PAYMENT_SET_ID

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
PAYMENT_SET_ID

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field during the prepayments matching process.

ORIGINAL_GL_DATE

Contains the GL_DATE column before AutoInvoice modifies it.

Validation: None 
Destination: None
Never

Users should not populate this field. The AutoInvoice process takes care of populating this field.

CONTRACT_LINE_ID

Identifies the contract line from Oracle Contracts Core that is associated with this line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
CONTRACT_LINE_ID

Optional

Passed in by Oracle Contracts.

CONTRACT_ID

Identifies the contract line from Oracle Contracts Id associated with this line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
CONTRACT_ID

Optional

Passed in by Oracle Contracts.

SOURCE_DATA_KEY1 to 
SOURCE_DATA_KEY5

Contains group attributes that link one or more transaction lines into groups used for line-level cash application.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
SOURCE_DATA_KEY1-5

Optional

Enter line group attributes that link one or more transaction lines into groups.

Receivables uses groups during line-level cash application.

Reference: 
See: Applying Receipts in Detail, Oracle Receivables User Guide

INVOICED_LINE_ACCTG_LEVEL

Identifies accounting level for invoiceable lines in original system.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
INVOICED_LINE_ACCTG_LEVEL

Optional
OVERRIDE_AUTO_ACCOUNTING_FLAG

This column controls whether the code combination ID of the Accounting Flexfield for this accounting distribution, populated by the feeder system, should override AutoAccounting. This flag is only relevant withint the Revenue Accounting feature.

Validation: 
Value should be Y or N.

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
OVERRIDE_AUTO_ACCOUNTING_FLAG

Optional

When set to Y, indicates that you are passing the GL account and AutoAccounting should not be used.

TAX_REGIME_CODE

Contains the Tax Regime Code to be used for the calculation of taxes for this transaction line.

Validation: 
Should exist in ZX_REGIMES_B. 
TAX_REGIME_CODE

Destination: 
ZX_LINES.TAX_REGIME_CODE

Optional

If you are not passing in Manual Tax lines, then you do not have to provide this information.

If passing in Manual tax lines, you have the option of either providing: 
1) TAX_CODE, or 
2) TAX_REGIME_CODE + 
    TAX + 
    TAX_STATUS_CODE + 
    TAX_RATE_CODE + 
    TAX_JURISDICTION_CODE

Do not populate for Credit Memos, AutoInvoice will use the tax information from the Invoice you are crediting.

TAX

Contains the Tax Code to be used for the calculation of taxes for this transaction line.

Validation: 
Should exist in ZX_TAXES_B.TAX

Destination: 
ZX_LINES.TAX

Optional

If you are not passing in Manual Tax lines, then you do not have to provide this information.

If you pass a value in TAX_REGIME_CODE, then you need to provide this value to properly identify the tax information you are providing.

TAX_STATUS_CODE

Contains the Tax Status Code to be used for the calculation of taxes for this transaction line.

Validation: 
Should exist in ZX_STATUS_B. 
TAX_STATUS_CODE

Destination: 
ZX_LINES.TAX

Optional

If you are not passing in Manual Tax lines, then you do not have to provide this information.

If you pass a value in TAX_REGIME_CODE, then you need to provide this value to properly identify the tax information you are providing.

TAX_RATE_CODE

Contains the Tax Rate Code to be used for the calculation of taxes for this transaction line.

Validation: 
Should exist in ZX_RATES_B. 
TAX_RATE_CODE

Destination: 
ZX_LINES.TAX_RATE_CODE

Optional

If you are not passing in Manual Tax lines, then you do not have to provide this information.

If you pass a value in TAX_REGIME_CODE, then you need to provide this value to properly identify the tax information you are providing.

TAX_JURISDICTION_CODE

Contains the Tax Jurisdiction Code to be used for the calculation of taxes for this transaction line.

Validation: 
Should exist in ZX_JURISDICTIONS_B. 
TAX_JURISDICTION_CODE

Destination: 
ZX_LINES. 
TAX_JURISDICTION_CODE

Optional

If you are not passing in Manual Tax lines, then you do not have to provide this information.

This value is relevant for US Sales tax where taxes are based upon location/jurisdiction.

If you pass a value in TAX_REGIME_CODE, then you need to provide this value to properly identify the tax information you are providing.

TAXABLE_AMOUNT

Contains the Taxable Amount for this transaction line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
TAXABLE_AMOUNT

Optional

Enter the amount of the invoice which can be taxed.

TAXABLE_FLAG

Contains a flag that indicates whether or not E-Business Tax Engine should calculate taxes for this transaction line.

Validation: 
Must be Y or N

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
TAXABLE_FLAG

Mandatory

When you pass manual tax lines via AutoInvoice, you should pass this value as N.

When passed in as Y, you are telling AutoInvoice to invoke the E-Business Tax engine to calculate taxes.

TAX_RATE

Contains tax rate.

Validation: 
None

Destination: RA_CUSTOMER_TRX_LINES_ALL.TAX_RATE

Optional

This field should be populated only for records with LINE_TYPE = ‘TAX‘

If you want to pass in manual tax lines, you have the option of providing either TAX_RATE or the AMOUNT of the tax.

TAX_CODE

Contains tax code. For manual tax lines, you must include either a tax code, or a combination of the tax regime, tax, tax status, tax jurisdiction, and tax rate code.

Validation: 
Must exist in AR_VAT_TAX.TAX_CODE

Destination: 
None

Optional

This field should be populated for records with LINE_TYPE = ‘TAX‘

For manual tax lines, you must include either a tax code, or a combination of the tax regime, tax, tax status, tax jurisdiction, and tax rate code.

For credit memos, AutoInvoice will use the Tax code associated to the invoice being credited.

TAX_PRECEDENCE

This column is obsolete in R12.

N/A Obsolete
TAX_EXEMPT_FLAG

Contains the flag to control whether or not to calculate taxes on a tranasaction line.

Validation: 
Must exist in AR_LOOKUPS.LOOKUP_CODE. Lookup 
type is TAX_CONTROL_FLAG.

Destination: RA_CUSTOMER_TRX_LINES_ALL. 
TAX_EXEMPT_FLAG

Optional/Conditional

May be populated only for LINE_TYPE = ‘LINE‘.

Enter ‘E‘ if you want AutoInvoice to exempt an invoice line that would normally be taxed and your system option ‘Use Customer Exemptions‘ is set to Yes. If you enter ‘E‘ you must enter a value for TAX_EXEMPT_REASON_CODE or 
TAX_EXEMPT_REASON_CODE_MEANING, depending on your batch source option.

Enter ‘R‘ if you want AutoInvoice to force tax on an invoice line, ignoring any exemption certificates that may be on file.

Enter ‘S‘ if you want tax to be calculated as 
per the normal procedures set up in Receivables.

For all other line types and credit memos, do not enter a value in this column.

TAX_EXEMPT_REASON_CODE

Contains  the tax exempt reason code for this transaction.

Validation: 
Must exist in AR_LOOKUPS.LOOKUP_CODE. Lookup 
type is TAX_REASON.

Destination: RA_CUSTOMER_TRX_LINES_ALL. 
TAX_EXEMPT_REASON_CODE

Optional/Conditional*

If LINE_TYPE = ‘LINE‘ and TAX_EXEMPT_FLAG = ‘E‘ then you need to pass in the reason for the exemption.

If your transaction batch source is setup with Memo Reason = Id (take note that there isn‘t a specific field for Tax Exempt Reason), then populate this field, otherwise leave it null.

For all other line types, do not enter a value in this column.

For credit memos do not enter a value in this column.

* When providing Exemption reason information, populate either TAX_EXEMPT_REASON_CODE or TAX_EXEMPT_REASON_CODE_MEANING 
and what field you are required populate is dependent upon your transaction batch source setup

TAX_EXEMPT_REASON_CODE_MEANING

Contains the tax exempt reason code meaning for this transaction

Validation: 
Must exist in AR_LOOKUPS.MEANING. Lookup type is 
TAX_REASON.

Destination: 
None

Optional/Conditional*

If LINE_TYPE = ‘LINE‘ and TAX_EXEMPT_FLAG = ‘E‘ then you need to pass in the reason for the exemption.

If your transaction batch source is setup with Memo Reason =Value (take note that there isn‘t a specific field for Tax Exempt Reason), then populate this field, otherwise leave it null.

For all other line types, do not enter a value in this column.

For credit memos do not enter a value in this column.

* When providing Exemption reason information, populate either TAX_EXEMPT_REASON_CODE or TAX_EXEMPT_REASON_CODE_MEANING 
and what field you are required populate is dependent upon your transaction batch source setup

TAX_EXEMPT_NUMBER

Contains the tax exempt number for this transaction.

Validation: None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
TAX_EXEMPT_NUMBER

Optional/Conditional*

If LINE_TYPE = ‘LINE‘ and TAX_EXEMPT_FLAG = ‘E‘ then you need to pass in the tax exemption number.

For all other line types, do not enter a value in this column.

For credit memos, do not enter a value in this column.

LEGAL_ENTITY_ID

Contains the Legal Entity ID associated to this transaction

Validation: 
Should exist in 
XLE_LE_OU_LEDGER_V.LEGAL_ENTITY_ID and 
XLE_LE_OU_LEDGER_V.OPERATING_UNIT_ID = ORG_ID associated to this transaction.

Destination: 
RA_CUSTOMER_TRX_ALL. 
LEGAL_ENTITY_ID

Optional
PARENT_LINE_ID

Contains the original parent order line from Oracle Order Management.

Validation: 
None

Destination: 
None

Optional

This information is passed in from Order management. Child invoice lines inherit contingencies from the parent line, and cannot be updated.

DEFERRAL_EXCLUSION_FLAG

Contains flag indicating whether Revenue may or may not be deferred for this transaction line.

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
DEFERRAL_EXCLUSION_FLAG

Optional
PAYMENT_TRXN_EXTENSION_ID

Contains Payment Transaction Extension Id which indicates payment has been obtained using Oracle iPyaments.

This field contains information that used to be stored in now obsolete columns: 
  ? CUSTOMER_BANK_ACCOUNT_ID 
  ? CUSTOMER_BANK_ACCOUNT_NAME 
  ? PAYMENT_SERVER_ORDER_NUM 
  ? APPROVAL_CODE

Instead of these fields, Autoinvoice requires you to populate the 
PAYMENT_TRXN_EXTENSION_ID. You can obtain this by calling the IBY_FNDCPT_TRXN_PUB.Create_Transaction_Extension before 
populating the Autoinvoice tables.

Validation: 
Should exist in IBY_FNDCPT_TX_EXTENSIONS. 
TRXN_EXTENSION_ID

Destination: 
RA_CUSTOMER_TRX_LINES_ALL. 
PAYMENT_TRXN_EXTENSION_ID

Optional

Value can be obtained by calling IBY_FNDCPT_TRXN_PUB. 
Create_Transaction_Extension before populating the AutoInvoice tables.

PAYMENT_ATTRIBUTES

Contains payment attributes for the customer

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
PAYMENT_ATTRIBUTES

Never

Users should not populate this field. The AutoInvoice process takes care of populating this field.

APPLICATION_ID

Contains the application id

Validation: 
None

Destination: 
RA_CUSTOMER_TRX_ALL. 
APPLICATION_ID

Optional
TRX_BUSINESS_CATEGORY 
PRODUCT_FISC_CLASSIFICATION 
PRODUCT_CATEGORY 
PRODUCT_TYPE 
LINE_INTENDED_USE 
ASSESSABLE_VALUE 
USER_DEFINED_FISC_CLASS 
TAXED_UPSTREAM_FLAG

These fields are used to support usage of E-Business tax features from an upstream application such as Oracle Leasing

Validation: 
None

Destination: 
The fields are used to populate temporary tables used by the E-Business Tax Engine to calculate taxes.

Optional

Upstream applications that use AutoInvoice takes care of populating these fields.

DOCUMENT_SUB_TYPE 
DEFAULT_TAXATION_COUNTRY 
TAX_INVOICE_DATE 
TAX_INVOICE_NUMBER

These fields are used to support European VAT Localization features

Validation: 
None

Destination: 
The fields are used to populate temporary tables used by the E-Business Tax Engine to calculate taxes.

Optional

Upstream applications with European localizations takes care of populating these fields.

PAYMENT_TYPE_CODE

Contains Payment Type Code from Order Management.

Validation: 
Should exist in OE_PAYMENT_TYPES.PAYMENT_TYPE_CODE
时间: 2024-10-14 00:49:09

ra_interface_lines_all 接口表各字段说明的相关文章

java 字节码文件详解

每一个class字节码文件都唯一对应一个类或接口,class文件中记录中类或接口的基本信息,但反之不成立,不是每一个类或接口都有一个唯一对应的字节码文件,首先类或接口的字节码可以不以文件的方式存储,可以直接从内存中生成字节码,而不产生.class文件,动态代理的原理就是直接内存中生成字节码流,根据加载字节码流进行类加载操作,类实例化,生成代理对象. 字节码文件记录的信息:魔术,class文件主次版本,常量池数量及常量池表,类或接口的访问标志,类索引,超类索引,接口数量及接口表,字段数量及字段表,

EBS的常用模块接口表

AP接口表:AP_INVOICES_INTERFACEAP_INVOICE_LINES_INTERFACE涉及的请求:应付款管理系统开放接口导入涉及案例: 运费导AP.费用导AP PO接口表:申请:PO_REQUISITIONS_INTERFACE_ALL涉及请求:导入申请 采购:po_headers_interfacepo_lines_interfacepo_distributions_interface涉及的请求:Import Standard Purchase Orders 接收:rcv_

EBS与外围系统数据的交互方式——接口表与API的区别

外围系统导入到EBS目前有两种方式,一种是通过EBS系统每个模块的标准接口表,比如GL模块中的gl_interface标准接口表,当外部数据插入到这张表之后,运行系统标准日记账导入请求,将数据加载到正是表中:第二种方式,是通过调用API的方式,比如AP模块有应付发票的API,可以通过先将数据加载到一张临时表中,然后按照API里面的参数要求,将临时表中的字段与其一一对应,运行API,将临时表中的数据插入到正式表中. 通过上述例子,可以从中找到两者区别,第一种方式是将数据导入到EBS系统的标准接口表

SQL查询字段添加括号报错:Operand should contain 1 column(s)

SQL语句:查询连个字段的信息 SELECT (menu_id,menu_captions) FROM bsdb.menulist a WHERE a.menu_id like ('2_'); 然后,因为这是在存储过程中的一个语句所以,在执行存储过程的时候编译不会报错,但是执行的时候却汇报错:Operand should contain 1 column(s):原因不好解释: 下面是官方发解释(MYSQL):https://dev.mysql.com/doc/refman/5.0/en/row-

SqlServer给一个表增加多个字段语法

添加字段语法 alter table table_name add column_name +字段类型+ 约束条件 给一个表增加多个字段: use NatureData go alter table XunHu add MaleCount varchar(50) null, FemaleCount varchar(50) null, SubadultCount varchar(50) null, LarvaeCount varchar(50) null, TraceType varchar(50

查询字段描述sql-postgresql

查询字段描述sql SELECT 'comment on column ' || n.nspname ||'.'|| c.relname || '.' || a.attname ||' is '''|| col_description(a.attrelid,a.attnum) ||''';' FROM pg_class as c join pg_attribute as a on a.attrelid = c.oid join pg_namespace n on c.relnamespace=n

passwd、shadow、group结构及各字段含义

/etc/password结构 sample:root:x:0:0:root:/root:/bin/bash 账号名称 密码 UID GID 用户信息说明 家目录 Shell root x 0 0 root /root /bin/bash /etc/shadow结构: sample:root:$1$/30QpE5e$y9N/D0bh6rAACBEz.hqo00:14126:0:99999:7::: 账号名称 密码 最近更动密码的日期 密码不可被更动的天(0代表随时可以变动) 密码需要重新变更的天

快学Scala 第二十一课 (初始化trait的抽象字段)

初始化trait的抽象字段: trait Logged { println("Logged constructor") def log(msg: String){ println("Logged")} } trait FileLogger extends Logged { var filename: String override def log(msg: String) { println("filename:" + filename) } }

Sql Server将一列字段拼接成字符串方法

最近在项目中遇到个问题,需要将表中某列字段合并成字符串输出,如果直接通过代码全部读取出来,再遍历进行拼接显然不是最好的方法,所以想着能否在数据读取的时候直接拼接好返回,网上搜了可通过for xml来实现. 首先,准备好需要的数据,脚本如下: if exists (select * from sysObjects where id=object_id('Student')) drop table Student go create table Student ( Id int, Name varc