Selecting Customers | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Creating and Updating Ship-to Customers (WCST) |
Creating and Updating Sold-to Customers (WCST)
Purpose: The system creates a sold to customer record automatically when you:
• enter an order for a new customer through order entry, or the Generic Order Interface (Order API), or
• enter a quote for a new customer through quote entry, or the order API; see Entering Pre-Order Quotes.
• enter a catalog request for a new customer, or
• process an Add request through the Generic Customer API.
Although most customers are added to the system by the means listed above, you can also add new customers to the system through Work with Customers, described here.
Outbound customer API: You can generate a customer download XML message when you create, change, or delete a customer. See the Generic Customer Download API for more information.
Communication with Oracle Retail Customer Engagement: If you use the Oracle Retail Customer Engagement customer integration, Oracle Retail Customer Engagement is the system of record for customer information, and Order Management System synchronizes customer information between the two systems. When you search for a customer in Order Management System, the Oracle Retail Customer Engagement database is searched first; and when you create or update a customer through customer maintenance, Order Management System sends the new or updated name, address, email, and phone number information to Oracle Retail Customer Engagement. See the Customer Engagement Customer Integration for more information.
In this chapter:
• First Create Sold To Customer Screen
• Second Create Customer Sold To Screen
• Display/Update Bill to Screen
• More Customer Sold To Options Screen
• Work with Ticklers Screen (sold to customer view)
• Display Customer Promotions Screen
• Display Customer Price Group Promotions Screen
• Display One Time Use Promotions Screen
First Create Sold To Customer Screen
Purpose: You use two Create Customer Sold-to screens to create new customers.
How to display this screen: Select Create at the Select Customer Sold To Screen.
Field |
Description |
A unique number to identify a customer. The system assigns a customer number automatically when you create a new Sold To Customer record. The system assigns the customer number whether or not you complete the customer record. Numeric, 9 positions; display-only, assigned by the system. |
|
A code assigned by the system to identify duplicate customers and detect fraudulent addresses. When you create a new customer, the system creates the standard match code automatically, based on selected elements of the customer's name and address. The match code is compared against match codes in the Fraud tables; if there is a match, the order is placed on hold. Also, the system updates the match code automatically when you change any of the related elements. The system uses the match code when determining whether to use an existing customer or create a new customer on orders you receive through the order API; see Remote Order Values (F70). Alphanumeric, 15 positions; display-only. |
|
The date you create the customer record. The system uses the job date for this value, and assigns this date as soon as you select Create. Numeric, 6 positions (in user date format), display-only, assigned by the system. |
|
Name |
The following 5 fields are available for you to enter the customer's full name: A title (such as “Mrs.” or “Dr.”) that precedes the customer's name. The prefix prints on labels and forms. If the Validate Prefix (I27) system control value is selected, your entry is validated against the Prefix table; see Working with Prefix Codes (WPFX). Alphanumeric, 3 positions; optional. The Sold-to customer's first name. Alphanumeric, 15 positions; optional. The initial of the customer's middle name. Alphanumeric, 1 position; optional. |
|
The customer's last name. Alphanumeric, 25 positions; required if company name is not present. An addition to the customer's full name (such as “M.D.,” “Fr.,” or “III”). The suffix prints on labels and forms, but is not accessible to scans. Alphanumeric, 3 positions, optional. |
The name of the company associated with the customer placing the order. Alphanumeric, 30 positions; required if last name is not present. |
|
The customer's street address. This is the primary delivery address. Shipping to a Post Office Box To ship to a Post Office Box, enter POST OFFICE BOX, POST BOX, or any variation of PO BOX (with or without spaces or non-alphabet characters, such as P.O. BOX), and the box number in the customer’s street address. During order processing, the system validates that the carrier can ship to a post office box (as defined in the Ship Via table). Example: Enter P.O. Box 9999 in the Street field to indicate delivery to a post office box instead of a home or company address. Note: If you type POST OFFICE BOX, POST BOX, or any variation of PO BOX in the customer’s street address during order entry or through the Order API, the system automatically selects the PO box field for the customer. However, if you remove this text from the customer’s street address, the system does not automatically unselect the PO box flag. Note: When you create a customer outside of order processing, you need to select the PO box field manually. Alphanumeric, 32 positions; required. |
|
The apartment number or suite number associated with the customer's delivery address. Follow these steps to enter an apartment or suite address: • Type APT to indicate an apartment or STE to indicate a suite. • Insert a space and type the number of the apartment or suite, for example: APT 4 or STE 116. Addresses must conform to United States Parcel Service (USPS) address formatting field description standards. For example, always precede the apartment or suite number with the appropriate abbreviation (for example, APT or STE). Alphanumeric, 10 positions; optional. |
|
Three additional lines of the customer's delivery address. If the address represents a post office box, you must type P.O. Box on the first line to meet USPS delivery regulations. Alphanumeric, three 32-position lines; optional. |
|
The postal or zip code for this customer. This code represents a delivery area. The system calls a user-defined program to validate postal code formats outside the Order Management System environment if you set the External Postal Code Validation (E62) system control value to Y. Required only if the Require postal code? flag is selected for the country; see Setting Up the Country Table (WCTY). If a postal code is required for the country, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Note: The system fills in the City and State fields appropriately if you set up the Postal Code/City/State table and you enter a valid postal code. Alphanumeric, 10 positions; required or optional based on country. |
|
The city where the customer lives or receives mail or shipments. Alphanumeric, 25 positions; required. |
|
The state or province where the customer lives or receives mail or shipments. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required only if the Require state? flag is selected for the country. The system validates that the state you enter is assigned to the SCF for the postal code. Alphanumeric, 2 positions; required or optional based on country. |
|
The code for the customer's country. Country codes are defined in and validated against the Country table. The Default Country for Customer Address (B17), if any, from the System Control table defaults here when you create a new customer; however, you can override the default. Alphanumeric, 3 positions; required. |
|
Identifies a business (commercial) or residential address. Used to calculate shipping charges for shippers that use rate tables (such as U.P.S.). The Default Delivery Code for New Order Entry Customers (D13) system control value defaults here; however, you can override this default. Valid values: • Business = Business rate table determines shipping charges. • Residential = Residential rate table determines shipping charges. • No distinction = No distinction between business and residence. Note: Only Business and Residential are valid values for U.P.S. The system defines the shipper on an order as U.P.S. if the Type field in the Ship Via table = U; see Working with Ship Via Codes (WVIA). Required. |
|
A flag that identifies the customer's delivery address as a Post Office box. Whenever you identify an address as a PO box, orders must ship by Parcel Post. Valid values are: • selected = The address is a Post Office box. • unselected (default) = The address is not a Post Office box. Shipping to a Post Office Box To ship to a Post Office Box, enter POST OFFICE BOX, POST BOX, or any variation of PO BOX (with or without spaces or non-alphabet characters, such as P.O. BOX), and the box number in the customer’s street address. During order processing, the system validates that the carrier can ship to a post office box (as defined in the Ship Via table). Example: Enter P.O. Box 9999 in the Street field to indicate delivery to a post office box instead of a home or company address. Note: If you type POST OFFICE BOX, POST BOX, or any variation of PO BOX in the customer’s street address during order entry or through the Order API, the system automatically selects the PO box field for the customer. However, if you remove this text from the customer’s street address, the system does not automatically unselect the PO box flag. Note: When you create a customer outside of order processing, you need to select the PO box field manually. |
|
A code that categorizes customers at a high level for reporting purposes. You can use customer class codes to: • send offers to a limited group of customers • restrict item sales to a group of customers • bypass normal item reservation (If the customer is assigned to a class flagged to bypass reservation, then the bypass setting applies even if the Bypass res (Bypass reservation) setting for the customer is unselected) • determine whether to prompt for user-defined fields in order entry You can define a Default Customer Class in Order Entry (D63) to assign to all customers you create through order entry. |
|
|
Required? The Require Customer Class in OE, WCAT, and WCST (H85) system control value defines whether this field is required. Secured? The Maintenance of Customer Class Field (B07) secured feature defines whether you can enter or maintain the customer class field at this screen. Note: If the Require Customer Class in OE, WCAT, and WCST (H85) is selected and the customer does not have a customer class code assigned, a user who does not have authority based on the Maintenance of Customer Class Field (B07) secured feature cannot update a customer. See Setting Up the Customer Class Table (WCCL) on working with customer classes. Alphanumeric, 2 positions; optional. |
A user-defined code to identify a group of customers further for reporting purposes. Alphanumeric, 3 positions; optional. |
|
A number that identifies a sales representative who takes an order. You can use Salesrep information for tracking and reporting sales activity and commissions. This number appears during order entry when you enter a new order for this customer. Salesrep numbers are defined in and validated against the Salesrep table. See Working with Sales Representatives (WSLS). If you prompt on this field, the system displays the Select Salesrep window where you can review and select a valid salesrep. The window indicates whether the salesrep is active and if a home store has been assigned to the salesrep. Numeric, 7 positions; optional. |
|
Defines whether the Outbound Email XML Message (CWEmailOut) sent to this sold to customer is also sent to the email address of the salesrep assigned to the customer. • Selected = Do not send Outbound Email (CWEmailOut) messages sent to the sold to customer to the email address of the salesrep assigned to the customer. The system sets the sold_to_suppress_sales_rep_email attribute in the CWEmailOut message to Y, indicating a copy of the message was not sent to the salesrep. • Unselected = Send Outbound Email (CWEmailOut) messages sent to the sold to customer to the email address of the salesrep assigned to the customer. The system sets the sold_to_suppress_sales_rep_email attribute in the CWEmailOut message to N, indicating a copy of the message was sent to the salesrep. The system sends a CWEmailOut message to the email address of the salesrep assigned to the customer for the following notification_types: - order confirmations (notification_type OC). - shipment and return confirmations (notification_type SC and RC). - backorder notices (notification_type B1, B2, B3). - soldout notifications (notification_type S1). |
|
Changed |
The date of the most recent update to the customer's record. The system uses the starting date of the ORDR_ASYNC job that was running at the time of the update. Note: This field is on the Change and Display screens only. Numeric, 6 positions (in user date format); display-only. |
Indicates the preferred method of correspondence for the primary email address. Valid values are: • O1 (Email) = Email is the preferred method of correspondence. • O2 (Order-only email) = Use email for order-related correspondence only; generate a document for other correspondence. • O3 (No email) = Do not use email for any correspondence; generate a document instead. • O4 (Do not ask the customer) = Do not ask the customer for his/her email address; the customer has already been asked and has declined to provide it. The system does not generate any email correspondence to the customer, even if an email address is specified. For a new customer, this value defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override the default. Note: The above values use the letter O, not the number 0 (zero). |
|
|
Email notifications: See When Does the System Generate an Email Notification? for an overview. Outbound email API: The opt in/opt out settings controls the generation of the Outbound Email XML Message (CWEmailOut) using the same logic as the generation of outbound emails. See Outbound Email API for an overview. Updating from an external system: See Receiving Customer Email Status Updates From an External System for an overview and the required setup. Alphanumeric, 2 positions; required. |
Informational. Language codes are defined in and validated against the Language table; see Working with Language Codes (WLAN) for more information. Alphanumeric, 3 positions; optional. |
|
This code specifies how often, and under what conditions, you send mail to the customer. You can use this code to indicate the customer's mail preferences with more precision than the Mail flag, discussed below, permits. Mail codes are defined in and validated against the Mail/Call Code table. See Working with Mail/Call Codes (WMCC). After you create a sold-to customer at this screen, the value in the Mail flag defaults into the mail code field if you have not entered a mail code. You must define this value (either Y or N) in the Mail/Call Code table or the screen displays an error message. Alphanumeric, 3 positions; optional. |
|
This code specifies how often, and under what conditions, you call the customer. Call codes are defined in and validated against the Mail/Call Code table. See Working with Mail/Call Codes (WMCC). Alphanumeric, 3 positions; optional. |
|
This field is not currently implemented. Alphanumeric, 3 positions; optional. |
|
Controls whether the customer receives future catalogs. Not to be confused with the three-position, alphanumeric Mail code field described above. This field is selected or N for new customers (added through order entry or a catalog request), depending on the value in the Default Mail Name (D10) system control value. Also defaults into the mail code on the first Create Customer Sold To screen, although you can override it. Valid values are: • selected = Mail catalogs to the customer • unselected = Do not mail catalogs to the customer |
|
Controls whether to include the customer's name in lists you sell to other companies for their own catalog mailings. This field is selected or N for new customers (added through order entry or a catalog request), depending on the value in the Default Rent Name (D11) system control value. Valid values are: • selected = You can sell the customer's name to another company • unselected = Do not sell the customer's name to another company |
|
Informational only. This field displays only if the Third Phone Number Type (L53) system control value is set to FAX. • selected = Do not fax the customer. • unselected = Authorized to fax the customer. |
|
Identifies the customer's status. You can still place orders for inactive customers. This information is useful for exception reporting you might conduct on your house list. Valid values are: • selected = Customer is inactive. • unselected (default) = Customer is active. |
|
Identifies whether the customer is commercial for reporting purposes. Valid values are: • selected = This is a commercial customer. • unselected (default) = This is a non-commercial customer. |
|
Controls how credit checking is performed for the customer during order entry. Valid values are: • Hold = The system places the customer's orders on hold automatically so you can review, then manually release each order. • Bypass = Orders for the customer are not included in the credit check function in order entry; however, the customer is still subject to other fraud-checking, as described in for the Fraud Checking (A68) system control value. • Fraud = The system places the customer's orders on “fraud” hold automatically so you can review each order and release it as needed. |
|
|
Entering the customer's name in the Fraud table does not by itself set this field to Fraud, although the system still holds all of the customer's orders for fraud. The system generates a report that identifies all held orders and their reason codes. You can review this information through Order Inquiry. See Releasing Held Orders for more information about held orders and reason codes. The Maintenance of Hold/Fraud/Bypass Flag (A57) secured feature controls access to this field. If you attempt to change this field and you do not have proper authority, an error message indicates: Not authorized to maintain. Alphanumeric, 1 position; optional. |
Controls when to reserve items for the customer. This feature lets you reserve inventory selectively for direct and wholesale customers and manage distribution of large quantities of merchandise. It is useful to assign a consistent customer class to customers flagged to bypass reservation, so that you can easily scan for these customers in Working with Interactive Reservation (MIRV). Valid values are: • selected = The customer bypasses reservation; you need to use Working with Interactive Reservation (MIRV) to reserve items for the customer. Important: Use this flag only if the Use OROB for Fulfillment Assignment (M31) system control value is unselected; if this system control value is selected, the system uses the Bypass reservation flag to send items to Oracle Retail Order Broker for fulfillment assignment; see Brokered Backorders. • unselected (default) = The system reserves inventory in the normal way for all orders for this customer (either through regular order entry or batch reservation, depending on the setting of the Immediate Reservation (A64) system control value) unless the customer is assigned to a customer class flagged to bypass reservation. Determining whether to bypass reservation based on customer-level setting or customer class setting: • If the Bypass res flag for the customer is selected, the customer always bypasses reservation regardless of whether there is a Class specified for the customer, or the class’s Bypass reservation setting • If the Bypass res flag for the customer is unselected, the customer still bypasses reservation if there is a Class specified for the customer and the class is flagged to Bypass reservation. See Setting Up the Customer Class Table (WCCL) for more information on customer class. |
|
Controls whether the system cancels items that are not in stock (backordered items) automatically with the first shipment on the order. Select this field for customers who want only one shipment on an order. The setting appears in the Auto can B/O field during order entry. Valid values are: • selected = Cancel backordered items automatically with the first shipment on the order. • unselected (default) = Do not cancel backordered items. |
|
Controls the level of sales history to capture for each customer. Valid values are: • No Item Tracking = Do not track the sale of items for the customer. • Sold To Tracking Only = Track item history for the customer placing the order (Sold To customer) only. • Sold To + Ship To Tracking = Track item history for the customer placing the order (Sold To customer) and the customer receiving the order (Ship To customer). The Default Item History Tracking (B18) system control value controls how this field defaults when you create a new customer. You can change this value at any time through Work with Customers, even after entering orders, to gain visibility to the ship-to customers' item history. Optional. |
Duplicate customer: A pop-up window appears if the system identifies the new customer as a “duplicate.” Here, you can select an existing customer record or select Accept to create a new customer record from the name and address information you entered.
Second screen: Select OK to advance to the Second Create Customer Sold To Screen.
Second Create Customer Sold To Screen
How to display this screen: Select OK at the First Create Sold To Customer Screen.
Continue entering information on this screen to complete creation of a new customer.
Field |
Description |
Customer |
A unique number to identify the customer. Numeric, 9 positions; display-only. |
The bill-to account assigned this customer. You can assign only one bill-to record to a sold-to customer; however, multiple sold-to customer records can use the same bill-to customer record. See Creating and Updating Bill-to Customers (WCBT). If a sold-to customer is assigned a bill-to customer in this field, that bill-to customer is added to each new order for the customer. Numeric, 7 positions; optional. |
|
An additional way to identify a customer, such as a customer or membership number in another system. Alternate Customer Number Label Description The field label on this screen is based on the name you enter in the Alternate Customer Number Label Description (H95) system control value; if you do not enter a name in this system control value, the field label is Alt cust. Example: If you enter the field label name MEMBER# in the system control value, the field label on this screen is MEMBER#. Secured Feature The Change Alternate Customer Number (B11) secured feature controls whether you can change this entry; if you prohibit access to this feature, the system displays an error message if you try to change the value: Not authorized to add/change Alt Customer #. |
|
|
Alternate Customer Number Cross Reference The alternate customer number at this screen is normally duplicated in the Alternate Customer # Cross Reference table. The system uses this table as a means to track each alternate customer number that has ever been assigned to the customer. Whenever you enter a value in the Alt cust field, the system creates a matching record in the Alternate Customer # Cross Reference table. See Working with Alternate Customer Number Cross-References for more information. Automatic Alternate Customer Number Assignment The Assign Alternate Customer # (I88) system control value controls whether the system automatically assigns an alternate customer number each time a customer is created by any means. See that system control value for more information. |
|
Possible to delete the alternate customer #? • If the Display Alternate Customer Cross Reference Window (I84) system control value is selected, you cannot delete an existing alternate customer number; however, you can replace the alternate customer number. You can also delete alternate customer number cross-references through the Working with Alternate Customer Number Cross-References option. • If the Display Alternate Customer Cross Reference Window (I84) system control value is unselected, you can delete an existing alternate customer number only if there are no additional cross references stored in the Alternate Customer # Cross Reference table besides the one that matches the Alt cust itself. In this situation, when you delete the Alt cust, the system also deletes the matching Alternate Customer # Cross Reference record. Numeric, 7 positions; optional or display-only, as described above. |
The customer's day, evening and third (fax or mobile) phone numbers. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mbl (mobile) number. You can define a telephone number format to map to the phone numbers operators enter into the system. Telephone number formats are defined by arranging numbers and special characters such as hyphens and parenthesis in the same order and position as the numbers in a phone number would display. When an operator enters a phone number, the system compares the number of numeric characters in the phone number with the telephone number formats you have defined. In order to match a format, the phone number must have the same number of numeric positions as a telephone number format. If the system cannot find a match, the phone number does not map to a telephone number format and is displayed as it was entered by the operator. |
|
|
Telephone Number Format Example An operator enters a phone number containing 10 numbers: 5085550100 The telephone number format used in the United States to represent an area code, local exchange and local phone number is: (508) 555-0100 When an operator enters a phone number containing 10 numbers (as in the example), the phone number displays so that the first 3 numbers are in parenthesis and a hyphen is between the sixth and seventh numbers, regardless of how the operator entered it into the system. If an operator enters a phone number containing 6 numbers, for example 5550100 and no format exists for 6 numbers, the phone number would display as it was entered (5550100). See Work with Telephone Number Format Screen. |
|
The system calls a user-defined program to validate phone numbers outside of Order Management System if you set the External Validation for Phone Number (E64) system control value to Y. The system provides a “hook” to the program when an operator clicks OK on a screen containing a phone number associated with a country. You can use this program to validate phone number rules for a specific country: for example, if a phone number for a country should only contain 6 numbers and the operator enters more than 6, the screen displays an error message. Phone numbers that are not associated with a country, for example, phone numbers in the Bank, Salesman, Warehouse and Ship Via tables, are not validated. The program validates phone numbers based on the following parameters: • Company • Country • State • City • Phone Number Alphanumeric, 14 positions; optional. |
The extension of the customer's phone or fax number. Numeric, 4 positions; optional. |
|
The warehouse code to default to the Order Header for new orders created for this sold-to customer. In this situation, the system reserves inventory for the order from this warehouse only. The warehouse must be an allocatable warehouse (the Allocatable flag for the warehouse is selected). Warehouse codes are defined in and validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). Numeric, 3 positions; optional. |
|
The van route assigned to the sold to customer, indicating the customer qualifies for van delivery on orders that contain the Reserve warehouse. See Van Delivery Processing for an overview. The van route must be a valid van route for the Reserve warehouse. You cannot enter a van route if a Reserve warehouse is not specified. Van routes are defined in and validated against the Warehouse Van Route table. See Work with Van Routes Screen. Alphanumeric, 4 positions; optional. |
|
The sequence number assigned to the van route in order to route the van deliveries. You cannot enter a van sequence number if a Van route is not specified. This field is informational only. Numeric, 4 positions; optional. |
|
Source (Current, Original) |
A unique code to identify a segment of your customer base (list of customers) targeted for an offer (catalog, newspaper or television advertisement). Source codes can be used to analyze sales and determine the effectiveness of advertising or catalog offerings. You may set up special prices or discounts for a source code. See Working with Source Codes (WSRC). The following two fields are available for source codes: The source code used by the customer on the most recent order. You can change this value. Alphanumeric, 9 positions; optional. A code that identifies how you first acquired the customer. The system retains the source code used on a new customer's first order or catalog request, depending on how you first acquired the customer. If the Update Original Source Code for Recipient Customers (F90) system control value is selected and the Original source code field for the customer is blank, the system updates the Original source code field for a recipient customer with the source code defined on the order header for the customer sold to. Alphanumeric, 9 positions; display-only. |
This code identifies the source of the customer based on how you and the customer first established contact (Original mail type) and whether the customer then purchased merchandise from you (Current mail type). Valid values are: • Buyer = a customer who places an order (the “sold-to” customer). A customer is coded as a buyer when this customer places an order, if the order is accepted. Note: - The system does not update a customer’s mail type to Buyer when you accept a quote for the customer; see Entering Pre-Order Quotes. - The mail type is not set to Buyer until the order async processing takes place; until that time, the mail type is Suspect. • Catalog request = a person who requested a catalog. The system assigns this mail type to customers that you add through: - Work with Customers; or - a catalog request order type, if the order is accepted. The system compares the order type with the Order Type to Process as Catalog Request/Item Samples (E08) system control value to determine if an order is a catalog request. - Work with Catalog Requests (see Entering Catalog Requests (WCAT)) |
|
|
• Recipient = the customer who receives the order (also known as the Ship To customer). The system tracks the mail type only for ship to customers that you add to an order by selecting Accept/Add Recip or Sold To/Recip. Note: The system does not update a customer’s mail type to Recipient when you accept a quote that contains the customer as a ship to customer; see Entering Pre-Order Quotes. • Suspect = a customer whose name you acquired through a telemarketing effort or a public or industry listing, or a customer who places an order that is then rejected. Also, when you create a new customer through order entry or the order API, the customer’s mail type is initially set to Suspect until the order async process completes its updates; at that time, the mail type is set to Buyer. Entity: If the Track Customer History at Entity Level (F89) system control value is selected, the system also tracks the mail type separately for each entity based on the first activity for the customer within the entity. For example, if the first activity for a customer within entity 100 is to place and accept an order, the mail types for this customer/entity are set to Buyer, even though the customer-level current and original may be set differently. |
|
There are two categories of mail type, as follows: The customer's current status. Note: The only time that the system updates the current mail type at either the customer or entity level is to change the code to a Buyer if an existing customer places and accepts an order. Alphanumeric, 1 position; display-only, updated by the system. The original status of the customer. Note: You cannot change the original mail type, and the system never updates it automatically after initial creation and any related async processing (that is, to change the mail type from Suspect to Buyer for a new customer created through order entry or the order API). The only exception to the above rule is if you happen to enter an order for a customer and reject it (producing an original mail type of Suspect), and then enter an order and accept it on the same day; in this case only, the original mail type changes to Buyer. Display-only, updated by the system. |
Identifies a customer name that you “plant” in a list to ensure that the company buying the list pays you for each use. Valid values are: • selected = This customer is a seed. • unselected = This customer is not a seed. Note: Flagging a customer as a seed on your house rental list does not prevent you from placing orders for the customer. |
|
A customer number that remains in the system after you merge duplicate customer records. Duplicate match codes can result when two customers have similar demographic information. For example, Gerald Smith and Geraldine Smith live at the same address. Duplicates may also occur during order entry when customers use variations of their first names on different orders. For example, John Jones places orders on two occasions, and gives John as his first name on one order, Jack as his first name on another order. When duplicate customers exist in the database, you can run a merge program that combines the duplicate customer information into a single (target) customer record. You can, optionally, retain the source customer as a ghost customer. See Working with Merge/Purge Sold-to Names (MMCS) for more information on the merge/purge function. |
|
|
If you enter a ghost customer number in order entry, a pop-up window warns you that the customer you entered is a ghost customer. If you press Enter to advance to the order header screen, the target customer defaults on the order. For example, if you enter 202, a ghost customer, the Ghost Customer Number Warning Window opens, informing you that customer 202 has been merged into customer 137. When you continue with the order process, customer 137 defaults on the Work with Order screen. Ghost customers do not display on any scan screens in order entry, order maintenance, order inquiry, catalog requests, customer maintenance, working with return authorizations, or working with customer memberships. If you enter a ghost customer number in any maintenance function, the system does not display any history, such as orders or catalog requests, because all history has been merged to the target customer. Valid values are: • selected = This is a ghost record. • unselected = This is not a ghost record. |
|
Note: If this field is selected, you can change it; if you unselect, the system no longer considers the customer a ghost, and no pop-up window opens in order entry when you enter the customer’s number. If this field is unselected, you cannot change it; ghost customers can be created only when performing a merge/purge. |
Identifies whether the customer as an associate or member who is eligible to receive special pricing on merchandise. The Default Associate Code (D09) system control value determines the default value of field for new customers. Valid values are: • selected = The customer is an associate customer. • unselected = The customer is not an associate customer. Secured Feature The Change Associate Customer Flag (B10) secured feature controls whether you can change this entry; if you prohibit access to this feature, an error message indicates if you try to change the value: Not authorized to change Associate Customer. |
|
Birth Month/Day |
The sold to customer’s birth month and birth day. Valid birth months are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. Valid birth days are 1-31. The system validates the birth day against the selected birth month. The system stores the birth month and day in the Customer Sold To table. The birth year does not display on the screen; however, it defaults to 1900 in the Customer Sold To table unless it has been updated through the Customer Engagement Customer Integration. Birth Month: Numeric, 2 positions (01-12 in table); required if you define a birth day. Birth Day: Numeric, 2 positions; required if you define a birth month. Birth Year (in table only): Numeric, 4 positions; optional. |
The discount applied automatically to the regular offer price for items on each order the customer places. Note: If the customer has a Price discount % and is also flagged as an Associate (see above), then the system applies the Price discount % to the regular offer price, not to the associate price. Example: Customer is flagged as an associate and also has a Price discount % of 10%. The regular offer price of an item is $100.00, and the associate price is $95.00. The system applies the 10% discount to the regular offer price of $100.00, resulting in a price to the customer of $90.00. Numeric, 5 positions with 2 place decimal; optional. |
|
The customer's pricing column. Items may be set up on the system with special (discounted) prices for different price columns. When the customer orders this item, the customer pays the discounted price automatically if the customer's pricing column and the item's pricing column are the same. Numeric, 2 positions; optional. |
|
The customer price group to use for quantity price matrix pricing, customer price group pricing, or as a qualifier for a promotion. You can assign the price group through customer maintenance, or by passing the code through the order API or customer API. Customer price groups are defined in and validated against the Customer Price Group table. If you do not assign a customer price group to a customer, the system assigns the customer price group defined in the Customer Price Group Code for CPG Pricing Only (L58) system control value to the customer. For more information: See: • Working with Customer Price Groups (WCPG) • Working with Quantity Price Matrix (WQPM) • Customer Price Group Pricing • Working with Promotions (WPRO) • Generic Order Interface (Order API) Alphanumeric, 4 positions; optional. |
|
The tax status of this customer. Valid values are: • Exempt = The customer is not required to pay tax on purchases. If the order is shipping to a Canadian address, it is exempt from both GST and PST. • GST Only = The customer is a Canadian customer and subject to the Goods and Services Tax on purchases only, not PST. See Working with GST Tax Exemption Status (MGTX) for information on how tax is calculated in this case. • Non Taxable = The system determines the customer’s tax status in order entry based on whether you enter a Resale/Exempt # and on the shipping address. • PST Only = The customer is a Canadian customer and subject to the Provincial Services Tax only, not GST. See Working with GST Tax Exemption Status (MGTX) for information on how tax is calculated in this case. |
|
|
• Resale = The customer is a reseller and not subject to tax. If the order is shipping to a Canadian address, it is exempt from both GST and PST. • Standard Tax = The customer is subject to all taxes. Canadian customers are subject to both GST and PST tax. If you select a tax code of Exempt or Resale, an Tax identification is also required. The customer's tax code and tax identification number defaults in order entry. At that time the system validates that the customer's Expiration date (Tax identification expiration date), if one has been entered, has not passed; if so, an error message indicates that you need to change the customer's tax information before proceeding with the order. The tax-related fields on this screen override any information you enter for specific states or provinces. You should enter either customer-level tax information or state/province-level tax information. See Working with Customer Tax Status for a complete description of how customer tax information defaults in order entry. Required if a Tax identification code is entered. |
The customer's VAT exemption number. The system checks this field only if the Tax Included in Price (E70) system control value is selected; if so, and if the order would normally be subject to VAT, this number provides a VAT exemption for the customer. The VAT number is not subject to the Expiration date and cannot be overridden in order entry. See Working with Customer Tax Status for a complete description of how customer tax information defaults in order entry. Alphanumeric, 20 positions; optional. |
|
The customer’s tax identification number, typically the resale or exempt certificate number assigned to a customer who is identified as tax exempt (E) or as a reseller (R); otherwise, the tax identification number does not control taxability. Any combination of letters, numbers, or special characters is accepted. If you enter a tax identification number, the expiration date is also required. Alphanumeric, 30 positions; required if customer is defined as tax exempt or as a reseller. |
|
The date the customer's exempt or reseller tax identification expires. In evaluating the customer's tax status, either at the customer level or for a specific state, the system validates that any date entered in this field has not passed, or that this date is blank. See Working with Customer Tax Status for a complete description of how customer tax information defaults in order entry. Numeric, 6 positions (in user date format); required if a Tax identification code is entered. |
|
Four optional message lines. Where do these messages display? These messages display on the: • Customer Selection Screen as one 80-position field. Note: The system does not add or remove any spaces when displaying these messages as one 80-position field; enter the text as you wish it to display. For example: If a word ends at the end of a message, put a space at the beginning of the next message so that the next word is separated from the previous word. If a word splits between the end of one message and the beginning of the next message, do not add a space at the end of the first message or the beginning of the next message. • Display Pop Up Msgs For Window in order entry for this customer unless the customer advanced to the order from the Customer Selection Screen. Secured feature: The Access to Customer Pop-up Messages (A79) secured feature controls whether you can create or change a customer message. If this secured feature is set to *ALLOW, you can create or change a customer message. If this secured feature is set to *EXCLUDE, the message fields are display-only. Alphanumeric, 20 positions each field; optional. |
|
The customer's primary email address.This address, along with any other email addresses for the customer, is stored in the Customer Sold To Email table. A plus sign (+) indicates that there are additional email addresses on record for the customer. See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Entering a new email address: If you overwrite the existing email address in this field, the system flags your entry as the primary email address for the customer, but retains the previous email address in the Customer Sold To Email table. In order to delete the previous email address from this table, you need to prompt in order to display the Select Customer Email Address Screen and delete the previous email address there. See Working with Customer Email Addresses for an overview. Deleting the email address: Similar to entering a new email address, if you delete the email address at this screen, the system removes the primary email flag for the address but retains the address in the Customer Sold To Email table. Follow the steps described above to delete the email address from this table. |
|
|
Defaulting in order entry: The customer’s primary email address defaults in order entry. See Working with an Order-Level Email Address for an overview. Email notifications: See When Does the System Generate an Email Notification? for an overview of how the system determines when to generate an email notification to the customer, and which email address to use. Email format: See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Alphanumeric, 50 positions; optional. |
The customer's job title. This field is not currently implemented. Alphanumeric, 26 positions; optional. |
|
Four additional fields you can use to enter any type of information about the customer. Alphanumeric, 10 positions per field; optional. |
Screen Option |
Procedure |
Work with customer address information |
Press Page Up to advance to the First Create Sold To Customer Screen, Change Customer Sold To screen (1 of 2), or the Display Customer Sold To screen (1 of 2), depending on whether you are creating, changing, or displaying a customer. |
Work with ship-to customers |
Select Ship To’s to advance to the Work with Customer Ship Tos Screen. |
Work with bill-to customers |
Select Bill To. If the customer already has a bill-to customer, you advance to the Work with Bill To Customers Screen. If the customer does not already have a bill-to customer, you advance to the Create Bill-to Customer Screen. |
Work with customer subscriptions |
Select Subscriptions to advance to the Work with Subscriptions Screen. |
Work with more customer sold to options |
Select More options to advance to the More Customer Sold To Options Screen. |
Work with contract pricing |
Select Contract Pricing to advance to the Work with Contract Price Screen. |
Work with customer tax status in specific states or provinces |
Select Customer Tax to advance to the Work with Customer Tax Screen. See Working with Customer Tax Status for an overview. |
Review mail history |
Select Mail History to advance to the Display Customer Mail History Screen. See Reviewing Customer History for an overview of customer history. |
Enter and resolve customer actions |
Select Customer Actions to advance to the Edit Customer Actions Window. |
Work with customer profile |
Select Customer Profile to advance to the Work with Customer Profile Screen. |
Review item history |
Select Item History to advance to the Customer Sold To Item History Screen. See Reviewing Customer History for an overview of customer history. |
Review order history |
Select Order History to advance to the Display Customer Order History Screen. See Reviewing Customer History for an overview of customer history. |
Exclude customers from using certain payment methods |
Select Pay Type Excl. to advance to the Exclude Pay Types By Customer Screen. |
Work with customer notes |
Select Notes to advance to the Edit Customer Notes Screen. |
To change: Select Change for a customer at a scan screen or enter a customer number at the Select Customer Sold To Screen to change it. You advance to the first Change Customer screen. Select OK at the first Change Customer screen to advance to the second Change Customer screen.
See Selecting Customers for more information.
Customer Workflow Management window: The Customer Workflow Management Window automatically opens when you select Change for a customer if open or in use ticklers exist for the sold to customer. Select Ticklers at this window to advance to the Work with Ticklers Screen (sold to customer view) where you can review and work with ticklers associated with the sold to customer.
Field descriptions: See First Create Sold To Customer Screen and Second Create Customer Sold To Screen for field descriptions.
Match code update: You can change customer information on either Change Customer screen. If you change any of the information that the system extracts for the match code, the match code is updated also.
Affected functions: Several functions are affected when you change sold to information:
• The system records the change in the Customer Address Change table. You can review address changes in this table by selecting Previous Address at a work with customer sold-to scan screen; see Reviewing Customer Address Changes. The system also writes a line in the Customer Notes table about the nature of the change and the date.
• A pop-up window opens if the Sold-to customer is linked to a permanent Bill-to account and the Update Bill-to Address with Sold-to Address Changes system control value is selected. The pop-up window allows you to apply the Sold-to address changes to the Bill-to address. See Display/Update Bill to Screen.
On the first Change Customer Sold To screen, you can change all the fields except the customer number, match code, or entered date.
On the second Change Customer Sold To screen, you can change all the fields except the customer number, customer name, original source code, or original mail type.
Purpose: Use this screen to update a Bill-to address when you make changes to its linked Sold-to address.
You can also update bill-to address changes with sold-to address changes in the MBS Work table if the old address of the sold-to customer is an exact match of the old address of the bill-to customer. The MBS Work table includes address information from the National Change of Address (NCOA) Service. See Loading Address Updates.
The system creates a permanent Bill-to record for a Sold-to customer when the person being billed for the order is different from the customer who placed the order.
See Creating and Updating Bill-to Customers (WCBT).
How to display this screen: You advance to this screen whenever you make a change to a customer linked to a bill-to account in customer maintenance or order entry if the Update Bill-to Address with Sold-to Address Changes (E13) system control value is selected. See First Create Sold To Customer Screen for field descriptions.
Completing this screen: This screen displays the name and address of the Sold-to customer with its changes in the upper half of the window, and its linked Bill-to record without the changes in the bottom half of the window.
Select Accept to update the Bill-to address with the changes made to the Sold-to address; otherwise, select Reject.
The following Bill-to fields update when you change their linked Sold-to customer fields:
• prefix
• first name
• middle initial
• last name
• suffix
• company
• street
• apt/suite
• address line 2
• address line 3
• address line 4
• postal code
• city
• state
• country
• delivery code
• PO box
• day phone number/extension
• eve phone number/extension
• mobile or fax phone number/extension
More Customer Sold To Options Screen
Purpose: Use this screen to advance to additional options available when working with a sold to customer.
How to display this screen: Select More options at the First Create Sold To Customer Screen, the Second Create Customer Sold To Screen, or the related change or display customer maintenance screens.
Option |
Procedure |
Work with customer email addresses |
Select Customer Email Addresses to advance to the Work with Customer Email Address Screen. |
Work with customer email correspondence |
Select Customer Email Correspondence to advance to the Work with Email by Customer Sold To Number Screen. |
Work with customer address change history |
Select Customer Address Change History to advance to the Display Address Changes Screen. |
Work with customer user-defined fields |
Select Customer User Defined Fields to advance to the Work with User Fields Screen. |
Work with ticklers associated with the sold to customer |
Select Work with Ticklers to advance to the Work with Ticklers Screen (sold to customer view). |
Work with customer ownership |
Select Customer Ownership. • If the customer is currently associated with customer ownership records, you advance to the Work with Customer Ownership Screen. • If the customer is currently not associated with customer ownership records, you advance to the Create Customer Ownership Screen. |
Work with alternate customer number cross references |
Select Work with Alternate Customer Cross Reference to advance to the Work with Alternate Customer # Screen. See Working with Alternate Customer Number Cross-References for an overview. |
Review promotions for which the customer is eligible |
Select Customer Promotions to advance to the Display Customer Promotions Screen, where you can review promotions for which the customer is eligible through direct customer assignment and advance to subsequent screens providing information on promotions. |
Review one-time use promotions applied to the customer’s orders |
Select One Time Use Promotions to advance to the Display One Time Use Promotions Screen. |
Review the customer’s loyalty account information |
Select Loyalty Account. When you select this option, the system retrieves the sold to customer’s information from Oracle Retail Customer Engagement. • If Oracle Retail Customer Engagement finds a loyalty card assigned to the customer, the system advances you to the Display Loyalty Account Screen. If more than one loyalty card is assigned to the customer in Oracle Retail Customer Engagement, the system displays loyalty account information for the first card assigned to the customer. • If Oracle Retail Customer Engagement does not find a loyalty card for the customer, the system advances you to the Customer Loyalty Registration Window, where you can select to enroll the customer in the Oracle Retail Customer Engagement Loyalty program. • If a Relate ID is not defined for the customer in the Customer Sold To table, the system displays an error message similar to the following: This customer does not have a Loyalty card. • If a connection could not be made to Oracle Retail Customer Engagement, the system displays an error message similar to the following: Unable to connect to ORCE. Note: This option displays only if the Use ORCE Loyalty (M06) system control value is selected; see Customer Engagement Loyalty Integration. |
Review the customer’s purchase history from Oracle Retail Customer Engagement |
Select Purchase History. When you select this option, the system retrieves the sold to customer’s information from Oracle Retail Customer Engagement and advances you to the Display Purchase History Screen where you can review the completed sales and returns transactions from Oracle Retail Customer Engagement. If a connection could not be made to Oracle Retail Customer Engagement, the system displays an error message similar to the following: Unable to connect to ORCE. Note: This option displays only if the ORCE Customer Integration (L37) system control value is set to INTERACT; see Customer Engagement Purchase History Integration. |
Review the customer’s wish list from Oracle Retail Customer Engagement |
Select Wish List. When you select this option, the system retrieves the sold to customer’s wish list information from Oracle Retail Customer Engagement and advances you to the Display Wish List Screen where you can review the items on the customer’s wish list from Oracle Retail Customer Engagement that exist in Order Management System. The message No items in wish list displays if no wish list items are returned from Oracle Retail Customer Engagement. Note: This option displays only if the Use ORCE Wish List (M26) system control value is selected and the ORCE Customer Integration (L37) system control value is set to INTERACT; see Customer Engagement Customer Wish List Integration. |
Work with Ticklers Screen (sold to customer view)
Purpose: Use this screen to review, work with, and resolve ticklers associated with a sold to customer.
Secured feature: If you do not have authority to the Update All Ticklers (B09) secured feature, you cannot update a tickler that is not assigned to you or your tickler groups or an error message indicates: Not authorized to change.
This secured feature controls updating a tickler by:
• selecting Change for a tickler to change it.
• selecting Delete for a tickler to delete it.
• selecting In process for a tickler to assign the tickler to yourself.
• selecting Resolve for a tickler to resolve it.
If you do not have access to this feature, you can update only ticklers assigned to you or your tickler groups. However, you can still release an order associated with the tickler from hold.
See Workflow Management Overview and Setup for an overview and required setup for workflow management processing.
How to display this screen:
• select Cust sold to at the Work with Ticklers Screen (order view).
• select Ticklers at the Customer Workflow Management Window (which opens when you advance to the Changing Sold To Customers screen or Select Orders For Return Authorization Screen.
• select the Work with Ticklers option from the More Customer Sold To Options Screen.
Field |
Description |
Sold to |
The number and description of the sold to customer associated with the ticklers on this screen. Sold to number: Numeric, 9 positions; display-only. Sold to description: Alphanumeric, 40 positions; display-only. |
S (tickler status) |
The status of the tickler. Valid values: • Open = Open; the tickler is open and is available to work on in the assigned tickler work queue. • In Process = In process; the tickler is currently being worked on by the assigned user. • Resolved = Resolved; the tickler has been resolved. Optional. |
P (tickler priority) |
The priority of the tickler, indicating how important the issue associated with the tickler is to resolve (1 is the lowest priority and 9 is the highest priority). Numeric, 1 position; optional. |
Assigned (assign date) |
The date the tickler was assigned to the user or tickler user group. Numeric, 7 positions (in user date format); optional. |
Ev (tickler event code) |
The code for the tickler event that created the tickler. Valid values: • BO = Backorders • CO = Cancelled orders • HO = Held orders • MN = Manually created • NO = New orders • OO = Aged open orders • SO = Sold out orders • UP = Unconfirmed pick tickets • VP = Voided pick tickets • WF = Remote workflow See System Delivered Tickler Events. Alphanumeric, 2 positions; optional. |
Cat (tickler category) |
The tickler category assigned to the tickler. Tickler categories are defined in and validated against the Tickler Category table; see Working with Tickler Category (WTCT). Alphanumeric, 3 positions; optional. |
Tickler# |
The tickler number assigned to the tickler, from the Tickler Number number assignment record. Numeric, 9 positions; optional. |
User group |
The group ID of the tickler user group assigned to the tickler. Tickler user groups are defined in and validated against the Tickler User Group table; see Working with Tickler User Groups (WTUG). Tickler group ID: Alphanumeric, 10 positions; display-only. |
User |
The user ID of the user assigned to the tickler. Users are defined in and validated against the User table; see Working with User Records (WUSR). User ID: Alphanumeric, 10 positions; display-only. |
Sts (order status) |
The status of the order. Valid values: • blank = open • A = archived to optical disk. This option is not currently implemented. • C = cancelled • H = held Note: The system highlights the held status in a different color (for example fuchsia) if the sold to customer is a new customer, based on purchase history. A new customer has placed an order, but no orders have shipped (# orders LTD is equal to or greater than 1 and # sales LTD is equal to 0 in the Customer Sold To Order History table). • P = purged • S = suspended • X = closed Alphanumeric, 1 position; display-only. |
Order # |
The order associated with the tickler. Numeric, 9 positions; display-only. |
Bill to |
The bill to customer associated with the tickler. Numeric, 9 positions; display-only. |
Screen Option |
Procedure |
Change a tickler |
Select Change for a tickler to advance to the Change Tickler Screen. |
Delete a tickler |
Select Delete for a tickler to delete it. You can only delete MN (manually created) ticklers. |
Display a tickler |
Select Display for a tickler to advance to the Display Tickler Screen. See the Change Tickler Screen for field descriptions. |
Release the order associated with the tickler from hold |
Select Release for a tickler to advance to the Release Reason Prompt Pop-Up Window (order header hold), Release Recipient Hold Reason Pop-Up Window (recipient hold), and/or Release Order Payment Method Window (pay type hold). If you release an order from hold for an HO (held order) tickler, the system automatically resolves the tickler. Also, the system evaluates any other ticklers associated with the order to determine if they can be resolved. |
|
If you select Release for a tickler not associated with a held order, an error message indicates: Order not on hold. If you select Release for a tickler not associated with an order, an error message indicates: Tickler not eligible for this option. Note: You must have authority to the Release Held Orders (ERHO) menu option to release the order from hold. |
Select a tickler to work on |
Select In process for a tickler to change the status of the tickler from open (O) to in use (I). You can only select to work with a tickler that is in an open status; if you select In process for a tickler that is in an in use (I) or resolved (R) status, an error message indicates: Tickler status cannot be changed - resolved or already in process. Selecting this option automatically assigns the tickler to the user and creates a tickler history record. |
Enter or review tickler work notes |
Select Notes for a tickler to advance to the work notes screen, based on the note type defined for the tickler. Note type A advances you to the Edit Customer Actions Window. Note type B advances you to the Work with Bill To Notes Screen. Note type O advances you to the Work with Order Messages Screen. Note type S advances you to the Edit Customer Notes Screen. Note type T advances you to the Work with Tickler Notes Screen. |
Review the tickler source |
Select Detail for a tickler to advance to the source screen, based on the tickler event associated with the tickler. BO, CO, HO, NO, OO, SO, UP, VP, and WF ticklers advance you to the Order Inquiry Header Screen. You cannot view the source for MN ticklers: Requested tickler has no source reference. |
Review tickler history |
Select History for a tickler to advance to the Work with Tickler History Screen. |
Resolve a tickler |
Select Resolve for a tickler to advance to the Resolve Tickler Window. |
Review procedures for a tickler |
Select Procedure for a tickler to advance to the Work with Tickler Event Rule Procedure Screen. You cannot add or change tickler procedures when you advance from the Work with Tickler screen. You cannot review procedures for MN ticklers. |
Create a tickler for the MN (manually created) tickler event |
Select Create to advance to the Create Tickler Screen. Note: To create a MN tickler, you must have authority to the Create Manual Tickler (B13) secured feature. |
Review the number of ticklers in the work queue, based on the selection criteria you have defined |
Select Count to advance to the Current Tickler Count Window. |
Toggle between displaying open and in use ticklers or resolved ticklers |
Select Open/Resolved. The system toggles between displaying: • ticklers in an open or in process status. • tickler in a resolved status. |
Display Customer Promotions Screen
Purpose: Use this screen to review promotions for which the customer is eligible through direct customer number assignment, or advance to subsequent screens providing more information on promotions for which the customer is eligible.
Note: This screen does not display all promotions for which the customer might be eligible through source code, offer, order total, or other criteria; it lists promotions only if the customer is assigned directly by customer number.
For more information: See Working with Promotions (WPRO).
How to display this screen: Select Customer Promotions at the More Customer Sold To Options Screen.
Field |
Description |
Promotion |
A code to identify a promotion for which the customer is eligible through direct customer number assignment. Alphanumeric, 7 positions; optional. |
Description |
The description of the promotion. Alphanumeric, 30 positions; display-only. |
Start date |
The date when the promotion first becomes effective. Numeric, 6 positions (in user date format); display-only. |
End date |
The last date when the promotion is effective. Numeric, 6 positions (in user date format); display-only. |
Type |
The type of promotion. Valid values are: • Additional freight • BOGO • Freight • Item Category • Order • Tiered discount • ' ' = messaging or reporting promotion Display-only. |
Option |
Procedure |
Display promotions for which the customer is eligible through a customer price group |
Select Promotions by Price Group to advance to the Display Customer Price Group Promotions Screen. Note: This option is available only if the customer is assigned to a customer price group that is assigned to a promotion. |
Display or work with all promotions |
Select Promotions to advance to the Work with Promotions Screen. |
Display Customer Price Group Promotions Screen
Purpose: Use this screen to review promotions for a customer price group. When you display this screen through:
• Work with Customers: This screen is available only if the customer is eligible for one or more promotions through customer price group assignment.
Note: This screen does not display promotions for which the customer is eligible through other criteria besides customer price group. Promotions for which the customer is eligible through direct customer number assignment are listed at the Display Customer Promotions Screen. Other promotions for which the customer might be eligible through other criteria, such as source code, offer, or total order value, are not listed at either of these screens.
• Work with Customer Price Group: This screen displays promotions to which the customer price group is assigned.
For more information: See Working with Promotions (WPRO).
How to display this screen:
• Select Promotions by Price Group at the Display Customer Promotions Screen.
• Select Promotions for a customer price group at the Work with Customer Price Groups Screen.
Field |
Description |
Promotion |
A code to identify a promotion for which the customer you are reviewing is eligible through customer price group assignment, or to which the customer price group you are reviewing is assigned. Alphanumeric, 7 positions; optional. |
Description |
The description of the promotion. Alphanumeric, 30 positions; display-only. |
Start date |
The date when the promotion first becomes effective. Numeric, 6 positions (in user date format); display-only. |
End date |
The last date when the promotion is effective. Numeric, 6 positions (in user date format); display-only. |
Type |
The type of promotion. Valid values are: • Additional freight • BOGO • Freight • Item Category • Order • Tiered discount • ' ' = messaging or reporting promotion Display-only. |
Option |
Procedure |
Display or work with all promotions |
Select Promotions to advance to the Work with Promotions Screen. |
Display One Time Use Promotions Screen
Purpose: Use this screen to review the one-time-use promotions used by the customer.
About one-time-use promotions: You can use the Use once field to flag a promotion for one-time use, indicating that a customer cannot use the same promotion to discount more than one order. You can also override the one-time-use restriction in order entry if you have the required authority under the Override One Time Use Promotion (J08) secured feature. See Working with Promotions (WPRO) for more general information on promotions, and see Cautions for One-Time-Use Promotions for additional notes.
How to display this screen: Select the One Time Use Promotions option at the More Customer Sold To Options Screen.
Field |
Description |
Customer |
A number to identify the customer, the customer’s name, and the company name, if any. Customer number: numeric, 9 positions; display-only. Customer company and name: alphanumeric, 41 positions; display-only. |
Date |
The order date, which might differ from the entered date. Numeric, 6 positions (in user date format); display-only. |
Order # |
A unique number assigned by the system to identify the order and ship-to. Order number: numeric, 8 positions; display-only. Ship-to: numeric, 3 positions; display-only. |
Promotion |
The code identifying the promotion. A promotion is listed on this screen for each order on which it was applied. Promotion codes are defined in and validated against the Promotion table; see Working with Promotions (WPRO) for more information. Alphanumeric, 7 positions; display-only. |
Description |
The description of the promotion, as set up through Working with Promotions (WPRO). Alphanumeric, 30 positions; display-only. |
Type |
The type of promotion. Possible types are: • Additional freight • BOGO • Freight • Item Category • Order • Tiered discount See Working with Promotions (WPRO) for a discussion of each type. |
Selecting Customers | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Creating and Updating Ship-to Customers (WCST) |
CS03_03 OMSCS 18.1 April 2019 OTN