Purpose: Use this screen to work with settings related to the order API or the generic customer API.
• Allow Price Overrides
• Duplicate Checking for Customers (F71-F77, H88 and I11):
- Exact Match Required on First Name for Remote Orders (F71)
- Exact Match Required on Last Name for Remote Orders (F72)
- Exact Match Required on Company for Remote Orders (H88)
- Exact Match Required on Street Address for Remote Orders (F73)
- Exact Match Required on Address Line 2 for Remote Orders (F75)
- Exact Match Required on Apartment for Remote Orders (F74)
- Exact Match Required on City for Remote Orders (F76)
- Exact Match Required on State for Remote Orders (F77)
- Exact Match Required on Email Address for Remote Orders (I11)
Duplicate Checking for Customers (F71-F77, H88 and I11)
Purpose: Leave each of the following fields unselected if a sold-to or bill-to customer record you receive through the order API or the generic customer API should be treated as a match an existing customer on your system with the same match code, even if the particular field in the customer address is not an exact match.
Example: |
You receive an order for a customer whose match code is the same as existing customer # 30303 in your company. Each of the address fields also match exactly with the exception for the first name, which is spelled differently. • If you leave the Exact Match on First Name (f71) system control value unselected, the system considers the two customer records a match and uses customer # 30303 to build the order tables. • If you select the Exact Match on First Name (f71) system control value, the system would not use customer # 30303 to build the order tables; instead, the system would treat the customer information received through the order API as a new customer if even one character of the customer's first name is different. |
Select each of the following fields if a customer record you receive through the order API or customer API should be treated as a match to an existing customer only if the particular field matches exactly.
Exact Match Required on First Name for Remote Orders (F71)
Exact Match Required on Last Name for Remote Orders (F72)
Exact Match Required on Company for Remote Orders (H88)
Exact Match Required on Street Address for Remote Orders (F73)
If selected, duplicate checking for the Generic Customer API and Generic Order Interface (Order API) does not include the following roadway descriptives in the match if it is the last word in the street address:
• STREET and ST
• LANE and LN
• DRIVE and DR
• AVENUE, AV, and AVE
• ROAD and RD
• PARKWAY and PKWY
• BOULEVARD and BLVD
• TURNPIKE, TNPK, and TPKE
• HIGHWAY and HWY
• BYPASS, BY, and BYP
• EXPRESSWAY and EXP
• FREEWAY and FWY
• HEIGHTS and HTS
• JUNCTION and JCT
• PLACE and PL
• TERRACE and TER
• CIRCLE and CIR
• COURT and CT
Examples:
• If the street address is 109 COTTAGE LANE, the system does not include LANE in the exact match logic. In this situation, the system considers 109 COTTAGE LANE, 109 COTTAGE LN, and 109 COTTAGE ROAD an exact match.
• If the street address is 109 COTTAGE LANE ROAD, the system includes LANE in the exact match logic and does not include ROAD in the exact match logic. In this situation, the system considers 109 COTTAGE LANE RD and 109 COTTAGE LANE ROAD an exact match, but does not consider 109 COTTAGE LANE or 109 COTTAGE ROAD an exact match.
Exact Match Required on Apartment for Remote Orders (F74)
Exact Match Required on Address Line 2 for Remote Orders (F75)
If selected, duplicate checking for the Generic Customer API and Generic Order Interface (Order API) does not include the following roadway descriptives in the match if it is the last word in the address line:
• STREET and ST
• LANE and LN
• DRIVE and DR
• AVENUE, AV, and AVE
• ROAD and RD
• PARKWAY and PKWY
• BOULEVARD and BLVD
• TURNPIKE, TNPK, and TPKE
• HIGHWAY and HWY
• BYPASS, BY, and BYP
• EXPRESSWAY and EXP
• FREEWAY and FWY
• HEIGHTS and HTS
• JUNCTION and JCT
• PLACE and PL
• TERRACE and TER
• CIRCLE and CIR
• COURT and CT
Examples:
• If the street address is 109 COTTAGE LANE, the system does not include LANE in the exact match logic. In this situation, the system considers 109 COTTAGE LANE, 109 COTTAGE LN, and 109 COTTAGE ROAD an exact match.
• If the street address is 109 COTTAGE LANE ROAD, the system includes LANE in the exact match logic and does not include ROAD in the exact match logic. In this situation, the system considers 109 COTTAGE LANE RD and 109 COTTAGE LANE ROAD an exact match, but does not consider 109 COTTAGE LANE or 109 COTTAGE ROAD an exact match.
Exact Match Required on City for Remote Orders (F76)
Exact Match Required on State for Remote Orders (F77)
Exact Match Required on Email Address for Remote Orders (I11)
Customer sold to: When performing duplicate email checking for a sold to customer, the system compares the email address passed in the message against the email addresses in the Customer Sold To Email table to determine if it is a duplicate.
• If a single email address is passed in the message, the system uses this email.
• If more than one email address is passed, the system uses the email address flagged as primary. If more than one email address is flagged as primary, the system uses the primary email address with the highest sequence number.
• If more than one email address is passed and none of them are flagged as primary, the system uses the email address with the lowest sequence number.
• If no email address is passed and the customer has an email address defined, the system does not consider the customer a match.
Customer ship to: When performing duplicate email checking for a ship to customer, the system compares the email address passed in the message against the email addresses in the Customer Ship To table.
Customer bill to: When performing duplicate checking for a bill to customer, the system compares the email address passed in the message against the email addresses in the Customer Bill To table.
Note: In evaluating a match for the email address, the system does not consider case. For example, an address of jsmith@funmail.com is considered a match for an address of JSMITH@FUNMAIL.COM.
For more information:
• Working with Source Codes (WSRC) for more information on defining a pricing method for a source code.
• Setting Up Match Codes (MMCH) for more information on match codes.
