This document lists error messages from the Customer Interface program in Oracle Receivables. There are over 50 specific error messages explained in detail to help users troubleshoot issues inserting or updating customer profile information through the interface. Common issues addressed include invalid or duplicate fields, missing required fields, and reference values that do not exist in lookup tables.
This document lists error messages from the Customer Interface program in Oracle Receivables. There are over 50 specific error messages explained in detail to help users troubleshoot issues inserting or updating customer profile information through the interface. Common issues addressed include invalid or duplicate fields, missing required fields, and reference values that do not exist in lookup tables.
This document lists error messages from the Customer Interface program in Oracle Receivables. There are over 50 specific error messages explained in detail to help users troubleshoot issues inserting or updating customer profile information through the interface. Common issues addressed include invalid or duplicate fields, missing required fields, and reference values that do not exist in lookup tables.
This document lists error messages from the Customer Interface program in Oracle Receivables. There are over 50 specific error messages explained in detail to help users troubleshoot issues inserting or updating customer profile information through the interface. Common issues addressed include invalid or duplicate fields, missing required fields, and reference values that do not exist in lookup tables.
This document lists all error messages generated by the Customer Interface program. Customer Interface error messages appear in the Exception Records section of the Customer Interface Transfer report.
The text of each error message in this section appears in bold text; additional information appears in plain text.
Error Messages A1 - The customer reference for update does not exist in HZ_CUST_ACCOUNTS - Please specify a customer reference that exists in HZ_CUST_ACCOUNTS. You attempted to update a value in the column ORIG_SYSTEM_CUSTOMER_REF. However, a value does not exist in HZ_CUST_ACCOUNTS to uniquely identify this customer in your original system.
a1 - Customer record for insert must have validated profile record defined - A customer level profile must exist in RA_CUSTOMER_PROFILES_INTERFACE for new customers and each Bill-To Business Purpose.
a7 - Duplicate record within the interface table
A2 - The address reference for update does not exist in HZ_CUST_ACCT_SITES - Please specify an address reference that exists in HZ_CUST_ACCT_SITES. You attempted to update a value in the column ORIG_SYSTEM_ADDRESS_REF. However, this address reference does not exist in HZ_CUST_ACCT_SITES. Enter the value that represents the customer Bill- To address for which you are inserting or updating customer profile information.
a2 - TAX_PRINTING_OPTION has an invalid value - Enter a valid tax printing option (for example: European Tax Format; Itemize By Line; Itemize and Summarize; Summarize by Tax Code; Summarize By Tax Name; Total Tax Only).
A3 - Customer reference for insert is already defined in HZ_CUST_ACCOUNTS - Please specify a customer reference that does not exist in HZ_CUST_ACCOUNTS. Each customer attribute must be unique. See: Creating Unique Customer References.
a3 - The customer profile for this customer reference already exists - Each customer attribute must be unique. See: Creating Unique Customer References.
A4 - Site use for this address reference already exists in the database
a4 - The customer profile class for update does not exist - Enter profile class information.
A5 - Customer Number already assigned to a different customer - You attempted to insert a value in the column CUSTOMER_NUMBER that already exists in HZ_CUST_ACCOUNTS. This value must be unique within HZ_CUST_ACCOUNTS.
a8 - Conflicting profile classes specified for this customer/site
B1 - ORIG_SYSTEM_ADDRESS_REF is mandatory when specifying an address - Enter the value that represents the customer bill-to address for which you are inserting or updating customer profile information. For update, this address reference must exist in HZ_CUST_ACCT_SITES_ALL.
b1 - Both TRX_CREDIT_LIMIT and OVERALL_CREDIT_LIMIT must be populated - You must provide values for both the TRX_CREDIT_LIMIT and OVERALL_CREDIT_LIMIT columns or leave both columns null.
B2 - ADDRESS1 is mandatory when specifying an address - If you entered a value in ORIG_SYSTEM_ADDRESS_REF,
you must also enter a value in ADDRESS1.
b2 - TRX_CREDIT_LIMIT may not be greater than the OVERALL_CREDIT_LIMIT - The value you enter for a customer's transaction credit limit cannot be greater than their overall credit limit.
B3 - COUNTRY is mandatory when specifying an address - Enter a value in HZ_LOCATIONS.COUNTRY.
b3 - DUNNING_LETTER_SET_NAME must have a unique value
B4 - SITE_USE_CODE is mandatory when inserting an address - Enter the business purpose for this customer's address. For example, Bill-To, Ship-To, Statements, or Dunning.
b4 - COLLECTOR_NAME must have a unique value - This value must be unique in
B5 - PRIMARY_SITE_USE_FLAG is mandatory when inserting an address - If you are importing an address and a business purpose, you must provide a value for this column. This is a Yes/No flag to indicate whether this is the primary site for this address.
b5 - STANDARD_TERM_NAME must have a unique value - Enter the standard payment terms for this customer. This column is found in the RA_CUSTOMER_PROFILES_INT_ALL table.
B6 - CUSTOMER_CLASS_CODE is not defined in AR_LOOKUPS - The value you entered for the customer class for this customer does not exist in Receivables. This column is found in the RA_CUSTOMERS_INTERFACE_ALL table.
b6 - STATEMENT_CYCLE_NAME must have a unique value - Enter a valid statement cycle to associate with this customer. Use statement cycles that you previously defined in the Statement Cycles window. This column is found in the RA_CUSTOMER_PROFILES_INT_ALL table.
B7 - CUSTOMER_PROFILE_CLASS_NAME has an invalid value - Enter a unique profile class name to associate with this customer. Use profile classes that you previously defined in the Customer Profile Classes window. This column is found in the RA_CUSTOMER_PROFILES_INT_ALL table.
b7 - BANK_ACCOUNT_NUM is mandatory when creating a new bank account - This column is found in the RA_CUSTOMER_BANKS_INTERFACE table.
B8 - STATE is not defined in AR_LOCATION_VALUES - You must enter a value for each address component on which your tax location flexfield structure is based. This column is found in the RA_CUSTOMERS_INTERFACE_ALL table.
b8 - AUTO_REC_INCL_DISPUTED_FLAG has an invalid value - Must equal 'Y' (Yes) or 'N' (No). This column is found in the RA_CUSTOMER_PROFILES_INT_ALL table.
B9 - COUNTRY is not defined in fnd_territories - The value you entered for the country column does not exist in the table FND_TERRITORIES. This column is required in the RA_CUSTOMERS_INTERFACE_ALL table.
b9 - PAYMENT_GRACE_DAYS must be a positive value
B0 - SITE_USE_CODE is not defined in AR_LOOKUPS - Use business purposes you previously defined in the Receivables QuickCodes window.
C1 - This customer reference has two different customer names defined
C2 - This customer reference has two different customer numbers defined
C3 - This customer reference has two different parent customer references
C5 - Customer reference has two different customer class codes defined - Use customer classes that you defined in the QuickCodes window.
C6 - This customer reference has two identical primary site uses defined
D1 - Address reference has two different ADDRESS1 values
D2 - Address reference has two different ADDRESS2 values
D3 - Address reference has two different ADDRESS3 values
D4 - Address reference has two different ADDRESS4 values
D5 - Address reference has two different cities
D6 - Address reference has two different postal codes
D7 - Address reference has two different states
D8 - Address reference has two different provinces
D9 - Address reference has two different counties
D0 - Address reference has two different countries
E1 - Address reference has two identical site use codes
E2 - Address reference has two different customers
e2 - Bill_to_orig_address_ref should only be defined for Ship-to Addresses
e3 - Bill_to_orig_address_ref is not a valid bill-to address
F1 - ORIG_SYSTEM_TELEPHONE_REF mandatory for telephone information - This column is required.
f1 - You may have only one active Dunning site use for each customer
F2 - TELEPHONE is mandatory when specifying telephone information
f2 - For each customer, you may only have one active "Statements" type - You can only assign one type of business purpose (e.g. 'statements') to each address.
F3 - TELEPHONE_TYPE is mandatory when specifying telephone information
f3 - For each customer, you may only have one active Legal site - You can only assign one type of business purpose (e.g. 'Legal') to each address.
F4 - TELEPHONE_TYPE is not defined in AR_LOOKUPS - Please use the Receivables Lookup window to define a new telephone.
f4 - Clearing Days must be greater than or equal to zero
F5 - Telephone reference for insert is already defined in HZ_CONTACT_POINTS. Please specify a unique telephone reference.
f5 - Address language is not installed - The language used by a customer site must exist in FND_LANGUAGES.
F6 - Telephone reference for update does not exist in HZ_CONTACT_POINTS - Please specify a telephone reference that exists in HZ_CONTACT_POINT.
f6 - Address reference has different languages - An address can only have one language defined.
f7 - Duplicate telephone reference in table RA_CONTACT_PHONES_INTERFACE
f8 - A bank and branch with this bank number and branch number already exists
f9 - Customer Prospect Code must be either CUSTOMER or PROSPECT
G1 - ORIG_SYSTEM_CONTACT_REF mandatory for contact information
g1 - This customer reference has two different customer prospect codes
G2 - LAST_NAME is mandatory when specifying a contact
G3 - CONTACT_TITLE is not defined in AR_LOOKUPS
G4 - Contact reference for insert is already defined in HZ_CUST_ACCOUNT_ROLES. Please enter a unique contact reference.
G5 - Contact reference for update is not defined in HZ_CUST_ACCOUNT_ROLES. Please specify a contact reference that exists in HZ_CUST_ACCOUNT_ROLES.
G6 - The address reference specified is not defined for this customer
G7 - CONTACT_JOB_TITLE must be defined in AR_LOOKUPS
H1 - Contact reference has two different first names
H2 - Contact reference has two different last names
H3 - Contact reference has two different titles
H4 - Contact reference has two different job titles
H5 - Contact reference has two different customers
H6 - Contact reference has two different addresses
I1 - Telephone reference has two different phone numbers
I2 - Telephone reference has multiple extensions
I3 - Telephone reference has two different types
I4 - Telephone reference has two different area codes
I6 - Telephone reference has two different customers
I7 - Telephone reference has two different addresses
J1 - SITE_USE_CODE is not updatable
J2 - PRIMARY_SITE_USE_FLAG is not updatable
J3 - LOCATION is not updatable - You cannot update this column.
J4 - CUSTOMER_TYPE is not defined in AR_LOOKUPS
J5 - PRIMARY_SITE_USE_FLAG has an invalid value - Value must be Y or N.
J6 - CUSTOMER_NUMBER must be null when auto-numbering is set to "Yes"
J7 - CUSTOMER_NUMBER is mandatory when auto-numbering is set to "No"
J8 - INSERT_UPDATE_FLAG has an invalid value - Value must be Y or N.
J9 - CUSTOMER_STATUS must have a value of 'A' or 'I'
K1 - Concurrent request failed
K3 - This customer reference has two different customer types defined - Multiple rows with the same customer reference must have the same customer type (Internal or External).
L1 - COLLECTOR_NAME is mandatory when no profile class specified
L2 - TOLERANCE is mandatory when no profile class specified
L3 - DISCOUNT_TERMS is mandatory when no profile class specified
L4 - DUNNING_LETTERS is mandatory when no profile class specified
L5 - INTEREST_CHARGES is mandatory when no profile class specified
L6 - STATEMENTS is mandatory when no profile class specified
L7 - CREDIT_BALANCE_STATEMENTS mandatory when no profile class specified
L9 - DUNNING_LETTER_SET_NAME is mandatory when DUNNING_LETTERS is "Yes"
L0 - CHARGE_ON_FINANCE_CHARGE_FLAG mandatory when INTEREST_CHARGES is Yes
M1 - INTEREST_PERIOD_DAYS is mandatory when INTEREST_CHARGES is "Yes"
M0 - CREDIT_BALANCE_STATEMENTS has an invalid value
N1 - CREDIT_HOLD has an invalid value
N2 - CREDIT_RATING has an invalid value
N3 - RISK_CODE has an invalid value
N4 - STANDARD_TERM_NAME which contains the payment terms has an invalid value
N5 - OVERRIDE_TERMS has an invalid value
N6 - DUNNING_LETTER_SET_NAME has an invalid value
N7 - STATEMENT_CYCLE_NAME has an invalid value
N8 - ACCOUNT_STATUS has an invalid value
N9 - PERCENT_COLLECTABLE has an invalid value
N0 - AUTOCASH_HIERARCHY_NAME which contains the AutoCash rule has an invalid value
O1 - STATEMENT_CYCLE_NAME is mandatory when STATEMENTS is "Yes"
O2 - LOCATION must be null when auto-numbering is set to "Yes"
O3 - LOCATION is mandatory when auto-numbering is set to "No"
O4 - CREDIT_CHECKING is mandatory when profile class is null
O5 - CHARGE_ON_FINANCE_CHARGE_FLAG must be null if INTEREST_CHARGES is No
O6 - INTEREST_PERIOD_DAYS must be null if INTEREST_CHARGES is "No"
O7 - INTEREST_PERIOD_DAYS must be greater than zero
P1 - The Postal Code is not in the defined range of system option - Refer to the System Options window, Tax tabbed region for the postal code range that you defined. (Address Validation system option is set to Error if you receive this message.)
P2 - Warning: The Postal Code is not in the defined range of system option - Refer to the System Options window, Tax tabbed region for the postal code range that you defined. This message also indicates that the Address Validation system option is set to Warning.
R1 - CUST_SHIP_VIA_CODE is not defined in ORG_FREIGHT
R2 - CUSTOMER_CATEGORY_CODE is not defined in AR_LOOKUPS
R3 - CUSTOMER_CATEGORY_CODE is not enabled in AR_LOOKUPS
R4 - CUST_TAX_CODE is not defined in AR_VAT_TAX
R5 - CUST_TAX_REFERENCE cannot be null when CUST_TAX_CODE is 'EXEMPT'
R6 - SITE_USE_TAX_CODE is not defined in AR_VAT_TAX
R7 - SITE_USE_TAX_REFERENCE is required when SITE_USE_TAX_CODE is 'EXEMPT'
R8 - Invalid demand class code - You define demand classes in the Demand Classes window.
R9 - SITE_SHIP_VIA_CODE not defined in ORG_FREIGHT
Q1 - A new location was created for a value in an address segment field - You must enter values that have already been defined in AR_LOCATION_VALUES if Address Validation is set to 'Error' and you are calculating sales tax.
Q2 - Validation failed for the key location flexfield structure
S3 - The address reference specified is not valid for this customer
S4 - Payment Method is not defined in AR_RECEIPT_METHODS
S5 - A bank account does not exist for the specified customer
S6 - The end date specified cannot be before the start date
S7 - The address specified must have an active BILL_TO site defined
T1 - Customer payment method already active between the dates specified - Customer payment method conflicts with another payment method (overlapping date range).
T2 - Customer site payment method already active between the dates specified - Customer site payment method conflicts with another payment method (overlapping date range).
T3 - Customer already has a primary payment method for specified dates - Only one primary payment method can exist at either the customer or Bill-To address level.
T4 - Customer site has a primary payment method on the dates specified - Only one primary payment method can exist at either the customer or Bill-To address level.
T5 - This customer payment method is already active in this date range
T6 - Multiple primary payment methods defined
V2 - The bank account specified must be of type 'EXTERNAL'
V3 - Customer bank account is already active between the dates specified
V4 - Customer site bank account already active between these dates
V5 - This customer already has primary bank account for specified dates
V6 - Customer site can have only 1 primary bank account for the dates specified
V7 - Duplicate rows exist in Interface table for this Customer Bank and date range
V8 - Duplicate primary customer banks defined within the interface table
W1 - BANK_NAME is mandatory when creating a new bank account
W2 - BANK_BRANCH_NAME is mandatory when creating a new bank account
W3 - BANK_ACCOUNT_CURRENCY_CODE is mandatory creating a new bank account
W4 - BANK_ACCOUNT_CURRENCY_CODE is not defined in FND_CURRENCIES
W5 - Bank number already exists
W6 - Duplicate bank number in interface table.
W7 - Primary flag should be 'Y' or 'N'.
W8 - Duplicate bank and branch name in interface table.
W9 - Duplicate Location
W0 - Bank and branch name already exists.
X1 - AUTO_REC_INCL_DISPUTED_FLAG mandatory when profile class is null - You must specify whether to include debit items that have been placed in dispute when you create automatic receipts for your customers if profile class is null.
X2 - TAX_PRINTING_OPTION is mandatory when no profile class specified
X3 - GROUPING_RULE_NAME is mandatory when no profile class is specified
X4 - CHARGE_ON_FINANCE_CHARGES_FLAG has an invalid value - Must equal Y or N.
X5 - GROUPING_RULE_NAME has an invalid value - Use grouping rules that you defined in the Grouping Rules window.
X6 - CURRENCY_CODE has an invalid value - Use currency codes that you defined in the Currencies window.
X7 - CREDIT_BALANCE_STATEMENTS is mandatory when STATEMENTS is "Yes" - Enter Y or N to specify whether to
send statements to customers with credit balances.
X8 - CREDIT_BALANCE_STATEMENTS must be "No" when STATEMENTS is "No" - Setting STATEMENTS to No
indicates you will not send statements to this customer.
X9 - STATEMENT_CYCLE_NAME must be null when STATEMENTS is "No" - Setting STATEMENTS to No indicates you will not send statements to this customer.
X0 - OVERRIDE_TERMS is mandatory when no profile class is specified
Z1 - CREDIT_BALANCE_STATEMENTS must be null when STATEMENTS is null - A null value for STATEMENTS indicates you will not send statements to this customer.
Z2 - STATEMENT_CYCLE_NAME must be null when STATEMENTS is null - A null value for STATEMENTS indicates you will not send statements to this customer.
Z3 - CHARGE_ON_FINANCE_CHARGE_FLAG must be null when INTEREST_CHARGES is null - A null value for
INTEREST_CHARGES indicates you will not calculate finance charges for this customer.
Z4 - INTEREST_PERIOD_DAYS must be null when INTEREST_CHARGES is null - A null value for
INTEREST_CHARGES indicates you will not calculate finance charges for this customer.
Z5 - DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is null - A null value for DISCOUNT_TERMS indicates you will not allow discounts for this customer.
Z6 - DISCOUNT_GRACE_DAYS must be positive
Z7 - DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is "No" - Setting DISCOUNT_TERMS to No
indicates you will not allow discounts for this customer.
Z8 - DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is "No" - Setting DUNNING_LETTERS to
No indicates you will not send dunning letters to this customer.
Z9 - DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is null
Z0 - CURRENCY_CODE is mandatory when a profile amount value is populated
