Oracle Receivables

Customer Interface
Documentation
Supplement
RELEASE 11

August 1998

Enabling the Information Age

OracleR Receivables Customer Interface Documentation Supplement
Copyright E 1988, 1998, Oracle Corporation. All rights reserved.
Primary Authors: Stephen Damiani, Vikram Ahluwalia
Major Contributors: Christopher Andrews, Alan Fothergill
The Programs (which include both the software and documentation) contain proprietary
information of Oracle Corporation; they are provided under a license agreement containing
restrictions on use and disclosure and are also protected by copyright, patent and other intellectual
property law. Reverse engineering of the Programs is prohibited. No part of this document may be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose,
without the express written permission of Oracle Corporation.

The information contained in this document is subject to change without notice. If you find any
problems in the documentation, please report them to us in writing. Oracle Corporation does not
warrant that this document is error free.

RESTRICTED RIGHTS LEGEND

Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use,
duplication and disclosure of the Programs shall be subject to the licensing restrictions set forth in the
applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition
Regulations are ’restricted computer software’ and use, duplication and disclosure of the Programs
shall be subject to the restrictions in FAR 52.227–14, Rights in Data –– General, including Alternate III
(June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.”

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other
inherently dangerous applications. It shall be licensee’s responsibility to take all appropriate fail–safe,
back up, redundancy and other measures to ensure the safe use of such applications if the Programs
are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the
Programs.
Oracle is a registered trademark, and Context, Financial Analyzer, Oracle7, Oracle8, Oracle Alert,
Oracle Applications, Oracle Discoverer, Oracle Financials, Object Library, Oracle Work in Process,
Oracle Workflow, SmartClient, PL/SQL, SQL*Calc, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net,
SQL*Plus, SQL*Report, SQL*ReportWriter, Oracle Web Employees, and SQL*QMX are trademarks or
registered trademarks of Oracle Corporation.

All other company or product names are mentioned for identification purposes only, and may be
trademarks of their respective owners.
Customer Interface Documentation Supplement
This document lists all of the error codes that can be generated by the
Customer Interface program. The appropriate messages will appear in
the Exception Records section of the Customer Interface Transfer report
when the program encounters errors. All errors in this document are
listed in alphabetical order.
This is all new documentation for Release 11 and can be used with your
Release 11 Oracle Receivables User’s Guide or Receivables online help.
For more information about the Customer Interface tables, see
Customer Interface Table Descriptions and Validation in the Oracle
Receivables User’s Guide or the Oracle Receivables Applications Technical
Reference Manual.

Error Codes
A1 – The customer reference for update does not exist in
RA_CUSTOMERS
a1 – Customer record for insert must have validated profile record
defined
a7 – Duplicate record within the interface table
A2 – The address reference for update does not exist in
RA_ADDRESSES
a2 – TAX_PRINTING_OPTION has an invalid value
A3 – Customer reference for insert is already defined in
RA_CUSTOMERS
a3 – The customer profile for this customer reference already exists
A4 – Site use for this address reference already exists in the database
a4 – The customer profile class for update does not exist
A5 – Customer Number already assigned to a different customer
a8 – Conflicting profile classes specified for this customer/site
B1 – ORIG_SYSTEM_ADDRESS_REF is mandatory when specifying an
address
b1 – Both TRX_CREDIT_LIMIT and OVERALL_CREDIT_LIMIT must
be populated
B2 – ADDRESS1 is mandatory when specifying an address

Customer Interface Documentation Supplement –1

 b2 – TRX_CREDIT_LIMIT may not be greater than the
OVERALL_CREDIT_LIMIT
B3 – COUNTRY is mandatory when specifying an address
b3 – DUNNING_LETTER_SET_NAME must have a unique value
B4 – SITE_USE_CODE is mandatory when inserting an address
b4 – COLLECTOR_NAME must have a unique value
B5 – PRIMARY_SITE_USE_FLAG is mandatory when inserting an
address
b5 – STANDARD_TERM_NAME must have a unique value
B6 – CUSTOMER_CLASS_CODE is not defined in AR_LOOKUPS
b6 – STATEMENT_CYCLE_NAME must have a unique value
B7 – CUSTOMER_PROFILE_CLASS_NAME has an invalid value
b7 – BANK_ACCOUNT_NUM is mandatory when creating a new
bank account
B8 – STATE is not defined in AR_LOCATION_VALUES
b8 – AUTO_REC_INCL_DISPUTE_FLAG has an invalid value
B9 – COUNTRY is not defined in fnd_territories
b9 – PAYMENT_GRACE_DAYS must be a positive value
B0 – SITE_USE_CODE is not 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 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

–2 Oracle Receivables
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
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
F3 – TELEPHONE_TYPE is mandatory when specifying telephone
information
f3 – For each customer, you may only have one active Legal site
F4 – TELEPHONE_TYPE is not defined in AR_LOOKUPS
f4 – Clearing Days must be greater than or equal to zero
F5 – Telephone reference for insert is already defined in RA_PHONES
f5 – Address language is not installed
F6 – Telephone reference for update does not exist in RA_PHONES
f6 – Address reference has different languages
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

Customer Interface Documentation Supplement –3

 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 RA_CONTACTS
G5 – Contact reference for update is not defined in RA_CONTACTS
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
J4 – CUSTOMER_TYPE is not defined in AR_LOOKUPS
J5 – PRIMARY_SITE_USE_FLAG has an invalid value
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

–4 Oracle Receivables
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
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
has an invalid value

Customer Interface Documentation Supplement –5

 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
P2 – Warning: The Postal Code is not in the defined range of system
option
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
R9 – SITE_SHIP_VIA_CODE not defined in ORG_FREIGHT

–6 Oracle Receivables
Q1 – A new location was created for a value in an address segment
field
Q2 – Validation failed for the key location flexfield structure
S1 – The customer reference specified is invalid
S2 – The address reference specified is invalid
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
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 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

Customer Interface Documentation Supplement –7

 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
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
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 be null when STATEMENTS
is ”No”
X0 – OVERRIDE_TERMS is mandatory when no profile class is
specified
Z1 – CREDIT_BALANCE_STATEMENTS must be null when
STATEMENTS is null
Z2 – STATEMENT_CYCLE_NAME must be null when STATEMENTS
is null

–8 Oracle Receivables
Z3 – CHARGE_ON_FINANCE_CHARGE_FLAG must be null when
INTEREST_CHARGES is null
Z4 – INTEREST_PERIOD_DAYS must be null when
INTEREST_CHARGES is null
Z5 – DISCOUNT_GRACE_DAYS must be null when
DISCOUNT_TERMS is null
Z6 – DISCOUNT_GRACE_DAYS must positive
Z7 – DISCOUNT_GRACE_DAYS must be null when
DISCOUNT_TERMS is ”No”
Z8 – DUNNING_LETTER_SET_NAME must be null when
DUNNING_LETTERS is ”No”
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

Customer Interface Documentation Supplement –9

Reader’s Comment Form
Oracle Receivables Customer Interface Documentation Supplement

Oracle Corporation welcomes your comments and suggestions on the quality and usefulness
of this publication. Your input is an important part of the information we use for revision.
• Did you find any errors?
• Is the information clearly presented?
• Do you need more information? If so, where?
• Are the examples correct? Do you need more examples?
• What features did you like most about this manual? What did you like least about it?
If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,
and page number below:

Please send your comments to:

Oracle Applications Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, CA 94065 USA
Phone: (650) 506–7000 Fax: (650) 506–7200
Or, send electronic mail to appsdoc@us.oracle.com.
If you would like a reply, please give your name, address, and telephone number below:

Thank you for helping us improve our documentation.