CUSTOMER INTERFACE STATUS ERROR Codes

Checked for relevance on 08-dec-2008

Problem Description
-------------------

You are running Customer Interface racust and there are an error message in the
Interface_status column, but you don ' t know what it means.


Solution Description
--------------------

Interface_status appears in the following tables:
Ra_customers_interface_all
Ra_customer_profiles_int_all
Ra_contact_phones_int_all
Ra_customer_banks_int_all
Ra_cust_pay_method_interface

These are the message codes and their meaning:

A1--> the customer reference for update does not exist in Ra_customers

A2--> The address reference for update does not exist in ra_addresses

A3--> Customer Reference for insert are already defined in Ra_customers

A4--> Site Use to this address reference already exists in the database

A5--> customer number already assigned to a different customer

B1--> Orig_system_address_ref is mandatory when specifying a address

B2--> ADDRESS1 is mandatory when specifying a address

B3--> COUNTRY is mandatory when specifying a address

B4--> Site_use_code is mandatory when inserting a address

B5--> Primary_site_use_flag is mandatory when inserting a address

B6--> customer_class_code isn't defined in ar_lookups

B7--> Customer_profile_class_name has an invalid value

B8--> state isn't defined in Ar_location_values

B9--> COUNTRY isn't defined in fnd_territories

B0--> site_use_code isn't defined in ar_lookups

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

C6--> This customer reference has two identical primary site uses defined

D1--> Address Reference has two different values

D2--> Address Reference has two different values

D3--> Address Reference has two different values

D4--> Address Reference has two different values

D5--> Address reference has two different

D6--> Address reference has two different postal codes

D7--> Address reference has two different

D8--> Address reference has two different

D9--> Address reference has two different

D0--> Address reference has two different

E1--> Address Reference has two identical site use codes

E2--> Address reference has two different

F1--> ORIG_SYSTEM_TELEPHONE_REF Mandatory for telephone information

F2--> Telephone is mandatory when specifying telephone information

F3--> Telephone_type is mandatory when specifying telephone information

F4--> telephone_type isn't defined in ar_lookups

F5--> Telephone Reference for insert are already defined in Ra_phones

F6--> Telephone Reference for update does not exist in Ra_phones

G1--> orig_system_contact_ref Mandatory for contacts information

G2--> last_name is mandatory when specifying a contacts

G3--> contact_title isn't defined in ar_lookups

G4--> Contacts Reference for inserts is already defined in Ra_contacts

G5--> Contacts Reference for update isn't defined in Ra_contacts

G6--> The address reference specified are not defined to this customer

G7--> Contact_job_title must is defined in Ar_lookups

H1--> Contact Reference has two different

H2--> reference has two different last names

H3--> Contact Reference has two different titles

H4--> Contact Reference has two 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

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 updateable

J2--> Primary_site_use_flag is not updateable

J3--> LOCATION is not updateable

J4--> customer_type isn't defined in ar_lookups

J5--> Primary_site_use_flag has an invalid value

J6--> Customer_number must was null when Auto-numbering was set to Yes

J7--> Customer_number is mandatory when auto-numbering be set to "No"

J8--> Insert_update_flag has an invalid value

J9--> Customer_status must have a ' a ' or ' I '

K1--> Concurrent request failed

K3--> This customer reference has two different customer types defined

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"

M3--> Collector_name has an invalid value

M4--> credit_checking has an invalid value

M5--> Tolerance has an invalid value

M6--> discount_terms has an invalid value

M7--> Dunning_letters has an invalid value

M8--> Interest_charges has an invalid value

M9--> statements has an invalid value

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 the 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 was null when Auto-numbering was set to Yes

O3--> LOCATION is mandatory when auto-numbering be set to "No"

O4--> credit_checking is mandatory when profile class is null

O5--> Charge_on_finance_charge_flag must being null if Interest_charges is No

O6--> interest_period_days must being null if Interest_charges is "No"

O7--> interest_period_days must be greater than zero

P1--> Postal Code isn't in the defined range of system options

Q1--> A new location is created for a value in the Address Segment field

Q2--> Validation failed for the key location Flexfield

R1--> cust_ship_via_code isn't defined in Org_freight

R2--> customer_category_code isn't defined in ar_lookups

R3--> customer_category_code isn't enabled in Ar_lookups

R4--> cust_tax_code isn't defined in Ar_vat_tax

R5--> cust_tax_reference cannot being null when Cust_tax_code is ' exempt '

R6--> site_use_tax_code isn't defined in Ar_vat_tax

R7--> site_use_tax_reference is required when Site_use_tax_code is ' exempt '

R8--> Invalid Demand Class code.

R9--> site_ship_via_code not defined in Org_freight

S1--> The customer reference specified is invalid

S2--> The address reference specified is invalid

S3--> The address reference specified are not valid to this customer

S4--> Payment method isn't defined in Ar_receipt_methods

S5--> A Bank account does not exist for the specified customer

S6--> The end date specified cannot is before the start date

S7--> The address specified must have a active Bill_to site defined

T1--> Customer Payment method already active between the dates specified

T2--> Customer Site payment method already active between the dates specified

T3--> Customer already has a primary payment method for specified dates

T4--> Customer site has a primary payment method on the dates specified

T5--> This customer payment be already active in this date range

T6--> Multiple Primary payment methods

V2--> The bank account specified must is 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 Run

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 isn't 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

X2--> tax_printing_option is mandatory when no profile class specified

X3--> Grouping_rule_name is mandatory when no profiles class is specified

X4--> Charge_on_finance_charges_flag has an invalid value

X5--> Grouping_rule_name has an invalid value

X6--> Currency_code has an invalid value

X7--> Credit_balance_statements is mandatory when statements is "yes"

X8--> credit_balance_statements must be ' no ' when statements is ' no '

X9--> Statement_cycle_name must being null when statements is "No"

X0--> override_terms is mandatory when no profiles class is specified

Y1--> Party_number must being null when auto-numbering is set

Y2--> Party_number is mandatory when auto-numbering be set to "No"

Y3--> Party number already assigned to a different party.

Y4--> This party reference has two different party numbers defined
Ra_customers_interface.

Y5--> Person_flag has an invalid value

Y6--> party Site number already assigned to a different address

Y7--> Address reference has two different party site numbers defined
Ra_customers_interface.

Y8--> Party_site_number must being null when auto-numbering is set

Y9--> Party_site_number is mandatory when auto-numbering be set to "No"

Z1--> credit_balance_statements must being NULL when statements is NULL

Z2--> Statement_cycle_name must being NULL when statements is NULL

Z3--> Charge_on_finance_charge_flag must being null when interest_charges is NULL

Z4--> interest_period_days must being null when interest_charges is NULL

Z5--> discount_grace_days must being null when discount_terms is NULL

Z6--> Discount_grace_days must positive

Z7--> discount_grace_days must being null when Discount_terms is "No"

Z8--> Dunning_letter_set_name must being null when Dunning_letters is "No"

Z9--> Dunning_letter_set_name must being null when dunning_letters is NULL

Z0--> Currency_code is mandatory when a profile amount value is populated

A1--> Customer record for insert must have validated profiles record defined

A2--> Tax_printing_option has an invalid value

A3--> the customer profile for this customer reference already exists

A4--> The Customer profile class for update does not exist

A7--> Duplicate record within the interface table

A8--> Conflicting Profile classes specified for this customer/site

B1--> Both Trx_credit_limit and Overall_credit_limit must be populated

B2--> Trx_credit_limit May is greater than the Overall_credit_limit

B3--> Dunning_letter_set_name must have a unique value

B4--> Collector_name must have a unique value

B5--> standard_term_name must have a unique value

B6--> Statement_cycle_name must have a unique value

B7--> Bank_account_num is mandatory when creating a new BANK account

B8--> Auto_rec_incl_dispute_flag has an invalid value

B9--> payment_grace_days must be a positive value

E2--> Bill_to_orig_address_ref should only is defined for ship-to

E3--> Bill_to_orig_address_ref isn't a valid bill-to address

F1--> you could have only one active Dunning site to each customer

F2--> for each customer, or only have one active "statements" type

F3--> for each customer, you could only have one active Legal site

F4--> Clearing days must is greater than or equal to zero

F5--> address language are not installed

F6--> address reference has different languages

F7--> Duplicate Telephone reference in table Ra_contact_phones_interface

F8--> A Bank and branch with the this bank number and branch number already exists

F9--> customer prospect Code must be either customer or prospect

G1--> This customer reference has two different customer prospect codes

U5--> Contact Reference has two different e-mail addresses

W2--> Credit_classification must have a valid value

W3--> You cannot update the party_type using Customer Interface.
Please don't specify a value for Party_type when the
Insert_update_flag is set to U.

W4--> When you create a person party_type, you must provide
Person_first_name or Person_last_name.

Y0--> Contact_job_title is not defined

Y1--> phone_country_code isn't defined in Hz_phone_country_codes

Y2--> This customer are already assigned to a different party

Y3--> This customer are already assigned to a different party

Y4--> lockbox_matching_option must have a valid value

Y6--> Telephone_type cannot is updated from telex to any other TYPE or any
Other type to telex.

Y7--> you to cannot update this address. A printed, posted, or applied
Transaction with a associated tax line exists

Y8--> Address_category_code does not exist. Please enter a valid adress
Category code or define a new one using the receivables lookups
Window.

Y9--> Address_category_code is not enabled. Enable this address
Category by updating the Enabled flag in the receivables lookups
Window.