Chapter 13: Setting Up Order Entry Values

Purpose: The Order Entry area of the System Control file defines:

• Parameters that control Order Entry processing

• Order Entry defaults

• Interfaces in Order Entry

For more information: For instructions and screen samples on how to create, change, delete, and copy a system control value, see Chapter 12: System Control File Components.

Quick Reference of Order Entry System Control Values

The Order Entry System Control Values table briefly describes the system control values for the Order Entry application area and lists the system control value, a short definition, other system control values to which you should refer in this section, if necessary, and a column where you can indicate the value that you assigned for your company.

If you are working with multiple companies, make a copy of this table for each company on your system.

Company: ______________________________

System Control Value

Description

Your Value

Current Offer (A33)

Defines the most current offer.

Code:

Primary Upsell Category (A67)

Defines which upsell window will appear in Order Entry.

Code:

Fraud Checking (A68)

Indicates whether to include fraud checking in Credit Checking routines.

Yes/No:

Fast Track Inventory (A70)

Indicates whether to perform fast track item conversion.

Yes/No:

Default Version for Order Entry (A71)

Defines the format of the initial screen to default in Order Entry.

Code:

Page/Letter Entry (A72)

Indicates whether to use the page/letter entry format.

Yes/No:

Order Entry Batching Default (A73)

Defines the value to default in Are the Orders Batched? field in Order Entry.

Yes/No:

Allow Multi-Payment Types (A74)

Indicates if a customer can apply more than one payment type to an order.

Yes/No:

Display Order Recap (A75)

Indicates if the Order Recap screen should display at the end of an Order Entry session.

Yes/No:

Create/Assign Bill To Customers in Order Entry (A76)

Indicates whether to assign a bill-to address to an order in Order Entry.

Yes/No:

Default Ship Via (A77)

Defines the value to default in the Ship Via field in Order Entry.

Number:

Vertex Interface (A88)

Indicates if you use the Vertex® Sales Tax L Series™ product to calculate tax.

Yes/No:

Vertex Tax Method (A89)

Defines how to calculate tax.

Code:

GST Rate (A90)

Defines the default GST tax rate for orders for Canadian companies or orders shipped to Canada.

Percentage:

GST Item Status Default (A91)

Defines the default GST tax status assigned to items (subject to GST and PST tax).

Code:

Maximum Order Amount (A92)

Defines the order amount to cause an order to be placed on hold unconditionally.

Dollar Amount:

Use State Shipping Matrix (B12)

Indicates if the State Shipping Matrix should be used.

Yes/No:

Use Zip/City/State Defaulting? (B13)

Indicates whether to default City and State fields in Order Entry.

Yes/No:

Tax on Freight (B14)

Indicates whether to charge tax on freight.

Yes/No:

Tax on Handling (B15)

Indicates whether to charge tax on handling.

Yes/No:

Default Country for Customer Address (B17)

Defines the country code to default in the Country field in Order Entry.

Code:

Allow Dynamic Creation of Cash Control Numbers (B20)

Indicates whether you enter cash control numbers for checks in Order Entry. See Batch Cash? (B22).

Yes/No:

Dynamic Creation of Coupons (B21)

Indicates if you enter unnumbered or 'dummy' coupons/credits in Order Entry.

Yes/No:

Batch Cash? (B22)

Indicates if you batch cash prior to Order Entry. See Allow Dynamic Creation of Cash Control Numbers (B20).

Yes/No:

Default Order Type (B28)

Defines the default Order Type in Order Entry.

Code:

Default Order Quantity (B30)

Defines the default Quantity in Order Entry.

Quantity:

Pricing Values (B31):

Defines how to perform pricing in Order Entry. Assign sequence number to define the order for the following line-level pricing methods.

Best Way Pricing (A78)

Indicates if whether to search the pricing hierarchy to assign the lowest price to the order line.

Yes/No:

Offer Price Sequence # (A79)

Uses the price defined for the item in the Item/Offer or SKU/Offer record.

Number:

Quantity Break by SKU Sequence # (A80)

Uses the price defined for the item in the Quantity Break table at the Item/Offer or SKU/Offer level.

Number:

Column Sequence # (A81)

Uses the price defined for the item based on Column Pricing at the Item/Offer or SKU/Offer level and the column assignment defined for the customer.

Number:

Special by Source Sequence # (A82)

Uses the price defined in Special Pricing by Source Code record for each source/item combination.

Number:

Contract Sequence # (A83)

Uses the special contract price defined for the customer in the Contract Pricing file.

Number:

Customer Discount Sequence # (A84)

Uses the discount percentage established in the customer record and applies the discount to each order detail line.

Number:

Coupon Item Sequence # (A85)

Subtracts the value in the Coupon Discount $ field in the Item/Offer or SKU/Offer file from the item price.

Number:

Quantity Break/Item (A87)

Indicates whether to reprice an order by the Quantity Break by Item method.

Yes/No:

Item Volume Discount (B29)

Indicates whether to reprice an order by the Item Volume Discount method.

Yes/No:

Price Codes (D93)

Indicates whether to reprice an order based on price codes assigned to items.

Yes/No:

Price Table Sequence # (E06)

Uses the price, discount, and/or premiums defined for items or groups of items in a price table.

Number:

Price Tables (E07)

Indicates whether to reprice an order based on the information in price tables.

Yes/No:

Search Active Offers for Price (F95)

Defines whether the system searches active offers for a valid offer price when you add an item to an order.

Yes/No:

Default Price Override Reason (B35)

Defines the price override reason code to default when you enter free gifts, telemarketing specials, or accompanying items in Order Entry.

Code:

Backorder Free Gifts (B48)

Indicates whether to place items designated as free gifts on backorder if they are not available.

Yes/No:

Price Override Code for Promotional Priced Lines (B61)

Not currently implemented. The price override code that defaults in order entry for promotional priced lines is defined in system control value Default Price Override Reason (B35).

Code:

CODE-1 From Group 1 Values (B68):

Defines the system control values for the CODE-1 Interface.

Use CODE-1 Coding System (B24)

Indicates if you use the CODE-1 Address Verification Interface. See Street Name Matching Algorithm (B25) and Address Match Threshold (B26).

Yes/No:

Street Name Matching Algorithm (B25)

Defines the 'closeness' algorithm that CODE-1 uses in selecting an address. See Use CODE-1 Coding System (B24) and Address Match Threshold (B26).

Code:

Address Match Threshold (B26)

Defines the 'closeness' threshold that CODE-1 uses in accepting addresses. See Use CODE-1 Coding System (B24) and Street Name Matching Algorithm (B25).

Number:

Address Verification Data Library (B66)

Defines the name of the library including the data for the CODE-1 address system.

Code:

Address Verification Program Library (B67)

Defines the library including the programs for CODE-1 address system.

Code:

Perform Address Standardization in Customer API (I99)

Indicates whether to perform address standardization when creating or changing customer records through the generic customer API.

Yes/No:

Default Cash Pay Type (C07)

Defines the value to default in the Pay Type field when you apply a customer's refund/balance due write-off to an order.

Number:

Duplicate Item Check (C09)

Defines whether the system should notify you if a customer ordered the same item/SKU within the period specified in the Duplicate Item Days field.

Yes/No:

Default Version for Order Inquiry (C34)

Defines the format of the initial screen to default in Order Inquiry.

Code:

Default Additional Charge Code (C45)

Defines the additional charge code used when converting a balance due write-off to an additional charge during Order Entry.

Code:

Use Default Current Source Code (C46)

Indicates whether to default an existing customer's current source code in Order Entry.

Yes/No:

Duplicate Item Days (C58)

Defines the number of days used to validate whether the customer ordered the same item/SKU on different orders, if using the Duplicate Item Check (C09) feature.

Number:

Maximum Order Quantity (C60)

Defines the maximum order quantity that may be keyed on an order detail line.

Number:

Order Purge Days (C62)

Defines the number of days from the last transaction date that a closed or canceled order is eligible for deletion through the Order Purge Program.

Number:

Update Demand for Order Maintenance Transactions (C72)

Defines whether to increase or decrease demand for Order Maintenance transactions.

Yes/No:

Default Male/Female Profile Code (C74)

Defines the profile code that has been created for 'Gender.'

Code:

Default Delivery Code for New Order Entry Customers (D13)

Defines the default delivery code to be assigned to new customers entered through Order Entry and Catalog Requests.

Code:

Default “Gift Order” Flag (D14)

Defines the default gift code to be assigned to all orders.

Yes/No:

Phone Numbers (D15)

Defines which two types of telephone numbers are displayed and/or entered in Order Entry, Order Maintenance, Order Inquiry and Work with Catalog Requests.

Code:

Order Discount Percentage Limit (D16)

Defines the maximum override discount percentage that may be entered in Order Entry and Order Maintenance.

Percentage:

Default Bank for Cash Posting from Order Entry (D17)

Defines the code for the bank to which cash received from prepaid orders posts for deferred liability

Code:

Enter Offer After Item (D19)

Indicates whether the offer code is entered after the base item code during Order Entry.

Yes/No:

Load Source from Mailing History (D20)

Defines whether the source code from the most recent mailing to the customer defaults to the order detail line.

Yes/No:

Maximum Order Amount for Fraud Checking (D24)

Defines the order amount that will cause a credit card order, shipping to an address other than the sold to address, to be placed on hold if the order does not also meet the criteria for the Ship Via Priority for Ship To Mismatch (L71), and the # of Times Shipped to Same Address (D25) or the # of Days Since Last Order (D26) system control values.

Dollar Amount:

# of Times Shipped to Same Address (D25)

Defines the minimum number of times a customer must ship to a recipient address for the order not to be placed on a ship to mismatch hold if it also exceeds the dollar amount specified in the Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).

Number:

# of Days Since Last Order (D26)

Defines the minimum number of days that must pass before a customer can place and ship an order to a recipient address and not have the order placed on a ship to mismatch hold if it also exceeds the dollar amount specified in Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).

Number:

User-defined Field Prompting for Existing Customers (D33)

Controls whether the User Fields screen appears automatically for existing customers if no information has been entered previously.

Yes/No:

Display Discount on Order Recap Screen (D38)

Controls whether the Order discount field displays in order entry, order inquiry and order maintenance.

Yes/No:

Override Offer on Order Detail Line (D49)

Controls whether the system overrides the offer for items not available in the offer for the order.

Yes/No:

Display Item Alias (D56)

Defines whether the item alias rather than the item code displays in Order Entry, Order Maintenance and Order Inquiry.

Yes/No:

Capture Operator Statistics (D61)

Defines whether to collect order statistics for Order Entry operators.

Yes/No:

Perform Source Pricing Validation (D62)

Determines whether the system prevents you from ordering an item that is not associated with the special source code on the order.

Yes/No:

Default Customer Class in Order Entry (D63)

Defines a customer class to assign to new customers created through Order Entry.

Code:

Default Previous Pay Type in Order Entry (D64)

Defines whether to use the customer's previous payment method as the default in Order Entry.

Code:

Track Invoice Currency (D68)

Determines whether to track the currency conversion rate in effect when the order is billed.

Yes/No:

Default Country for International Address Format (D69)

Defines the country code to default to the Country field when you are assigned to the new customer address format.

Code:

Method for Processing Overpayments in Order Entry (D70)

Defines whether the system automatically creates refunds for overpayments on prepaid orders, applies the overpayments as contributions, or displays a pop-up window in Order Entry allowing you to specify a refund or a contribution

Code:

Use Source Code from Order Header When Creating Order Lines (D73)

Defines whether the source code defined for the order header should pull through to the order detail lines.

Yes/No:

Require Reason for Lines Added in Order Maintenance (D75)

Defines whether to require an add reason code when you add items to an order in Order Maintenance.

Yes/No:

Include Handling in Freight Charge Calculation (D77)

Defines whether the system includes handling charges in the total order amount subject to freight when using dollar chart or percentage freight calculation methods.

Yes/No:

PO Required for A/R Orders (D79)

Defines whether a purchase order number is required for accounts receivable orders.

Yes/No:

Verify Duplicate PO Numbers for A/R Orders (D80)

Defines whether the system verifies that each purchase order number for an accounts receivable customer is unique.

Yes/No:

Archive Orders to Optical Disk (D81)

Defines whether to copy purged orders to a staging library so that you can then archive the orders to optical disk storage.

Yes/No:

Extra Weight for Order Weight Freight Method (D85)

Defines the extra weight to use for each carton when calculating freight with the order weight freight method.

Weight:

Prorate Dollar Discounts and Coupons (D90)

Defines whether to prorate discount amounts across items on the order.

Yes/No:

Maximum Coupon Amount (D91)

Defines a maximum coupon amount you can enter when you press F21 to reprice an order.

Dollar Amount:

Price Override Reason for Same Price Exchanges (D92)

Defines the default price override reason code to use when you add an exchange item to an order for an item that was sold at a discount.

Code:

Individuals Required in Order Entry (E01)

Defines whether you can associate individuals who place or originate orders with the sold-to customer in Order Entry.

Yes/No:

Default Price Table (E04)

Defines the price table for the system to check if there is no price table specified for a source code, or if an item on the order is not included in the price table specified in the source code.

Code:

Price Table Level Override Code (E05)

Defines the price override reason code to use when overriding the maximum pricing level for an item on an order.

Code:

Order Type to Process as Catalog Request/Item Samples (E08)

Defines an order type you can use for catalog requests in order to code customers you create with this order type as catalog requesters rather than buyers.

Code:

Default Ship Complete Flag (E09)

Sets the default for the Ship complete flag on the Order Properties screen to Y or N.

Yes/No:

COD Charge (E12)

Defines the dollar amount to charge customers for C.O.D. payments.

Dollar Amount:

Use Prospect Finder File (E40)

Defines whether the system searches the Prospect file for address information to default on the Work with Order or Work with Order/Detail screen in Order Entry.

Yes/No:

Evaluate Promotional Items/Inserts in Order Entry/Maintenance (E48)

Defines whether to automatically add package insert items to orders in Order Entry/ Maintenance if the order qualifies.

Yes/No:

Negative Additional Charge Limit (E49)

Defines the dollar value the system uses to limit the total negative additional charges applied to an order.

Number:

Dollar Method Used to Evaluate Offer Ship Via Override (E50)

Defines whether the system looks at merchandise or order total in evaluating an order for an offer or source code-related ship via override

Code:

Future Orders Item Status (E52)

Defines the item status code the system uses to select items to take a future arrival date in Order Entry and Order Maintenance.

Code:

Default Future Orders Arrival Date (E53)

Defines the future arrival date the system defaults to items defined with a future ship status on an order.

Date:

Price Override Limit Percent (E55)

Defines the percentage of the price override limit Order Entry operators can enter for items.

Percentage:

Post Demand to Order Level Forecast Files for Soldout Items (E58)

Controls whether you update demand for items sold out in order entry.

Yes/No:

Demand Update for Non-Inventoried Items (E59)

Controls whether you update demand for items whose Non/inv flag is set to Y.

Code:

External Postal Code Validation (E62)

Defines whether the system calls a user-defined program to validate postal codes outside of CWDirect.

Yes/No:

Default Source for Internet Orders (E65)

Defines the default source code to use for an order received through the internet interface if no source code is specified on the order.

Code:

Tax Included in Price (E70)

Defines whether you process orders subject to tax-inclusive pricing and VAT.

Yes/No:

Override Offer/Page/Alias on Order Detail (E72)

Defines whether the system changes the offer code for an item to the offer including the item's page/alias.

Yes/No:

Tax Inclusive Cutoff Date (E79)

Defines the date when VAT and tax-inclusive pricing went into effect.

Date:

Default Salesrep Number (E86)

Defines the salesrep number you want to default in the Salesrep number field on the Request Order Batch screen in order entry.

Number:

Require Salesrep Number in Order Entry/Order Maintenance (E87)

Defines whether the Salesrep number field is a required field in order entry and order maintenance.

Yes/No:

Modulus 10 Check on Salesrep Number (E88)

Defines whether a modulus 10 check is performed against the salesrep number in Work with Salesreps.

Yes/No:

Display Special Format Response Descriptions in Order Entry (E90)

Defines whether to display custom special format response descriptions order entry.

Yes/No:

User Defined Modulus Check Program (E94)

Defines the program name used to validate credit card numbers entered for credit card pay types defined with an MU modulus check.

System Name:

Allow Negative Prices in Order Entry (E97)

Defines whether you can enter a negative price on order entry or order maintenance.

Yes/No:

Maximum Order Line Value (E98)

Defines the maximum order line dollar value you can enter without proper authority; a pop-up window displays if you have authority but you exceed this value.

Dollar Amount:

Sub Page Entry (E99)

Defines whether the Sub page field displays on the Create Item Offer screen in Work with Item/SKUs and on the Create Item/SKU Offer screen in Create Item/SKU Offer.

Yes/No:

Display Order Line Discount Messages (F01)

Defines whether discounted lines are highlighted and a message displays in order entry, order maintenance and order inquiry.

Yes/No:

Load Order Header Source from Mailing History (F05)

Defines whether the source code from the most recent mailing to the customer defaults onto the order header in order entry.

Yes/No:

Display SKU Description in place of SKU Element (F25)

Defines whether the SKU description displays in place of the SKU elements in order entry, order maintenance and order inquiry.

Yes/No:

Use Computer Telephony Integration (F26)

Defines whether you advance to the CTI Customer Selection screen in order entry, which you can use to receive and/or make calls if CTI is set up in your company.

Yes/No:

Update CTI Customer Call Log (F27)

Defines whether the system creates CTI customer call log entries automatically for all call activity.

Yes/No:

Select Telemarketing Specials by Item Category (F35)

Defines whether you advance through additional pop-up windows in which items are restricted by item category when you select telemarketing specials to add to an order.

Yes/No:

Telemarketing Special Price Override Reason (F36)

Defines the price override reason code that the system uses when adding a telemarketing special to an order.

Code:

Display Backordered Telemarketing Special Items (F37)

Defines whether backordered items featured as telemarketing specials for an offer display in the telemarketing specials pop-up windows in order entry.

Yes/No:

SKU Element for Order Entry Filtering (F40)

Defines the SKU element to use for filtering which item coordinates display when you are cross-selling by item coordinate in order entry.

Number:

Display Backordered Coordinate Sale Items (F41)

Defines whether backordered items display in the pop-up windows for item coordinates in order entry.

Yes/No:

Restrict Additional Charge Amount if Default Charge (F43)

Defines whether the Amount field is enterable at the Enter Additional Charges pop-up window for an additional charge code that has a default charge amount specified.

Yes/No:

Deferred and Installment Billing (F51)

Defines whether an operator can assign a deferred or installment payment plan to an order.

Yes/No:

Number of Times Flexible Payment Option is Used (F52)

Defines the number of times a credit card can be used before an order using a deferred or installment payment plan is placed on PV hold.

Number:

Number of Days Flexible Payment Option is Used (F53)

Defines the number of days a credit card can be used before an order using a deferred or installment payment plan is placed on PV hold.

Number:

Dollar Threshold for Sold To Customer Orders with Flexible Payments (F54)

Defines whether the system places an order using a deferred or installment payment plan on hold when the total open order amount and open invoice amount exceeds the amount specified.

Dollar Amount:

Net Credit Card Credits for Deferred and Installment Billing (F55)

Defines whether credit invoices are netted with debit invoices before a deposit is sent to the service bureau for an invoice associated with a deferred or installment payment plan.

Yes/No:

Retail Order Defaults (F59)

Defines whether the system defaults a retail warehouse and location to the Enter Location pop-up window for an order using an express bill ship via.

Yes/No:

Recalculate Freight Default (F62)

Defines the default setting of the Recalculate freight field in order maintenance or when you cancel an item through a separate menu option.

Yes/No:

Sort Source Codes Prompt by Description in Order Entry (F67)

Defines whether the system displays source codes alphanumerically by source code description on the Select Source screen in order entry.

Yes/No:

Pass Entity Code to Vertex (F69)

Defines whether the system passes the entity code defined for the division that is associated with the source code on the order to the Vertex Interface.

Yes/No:

Phone Interface Values (F70)

Defines system control values related to the phone interface.

Default Order Type (C93)

Defines the default order type to be assigned to all orders entered into the system through the telephone interface.

Code:

Phone Load Method (C97)

Defines how to load telephone interface orders into the system.

Code:

Tape Drive (C98)

Defines the name of the tape drive used to load telephone interface orders if the Phone Load Method (C97) system control value is set to TAPE.

System Name:

Tape Record Length (C99)

Defines the length of the records in the telephone interface input file.

Number:

Allow Price Overrides (D71)

Defines whether the system reprices items on orders processed through the phone interface based on the pricing hierarchy defined for the source code, or accepts the item price from the order.

Yes/No:

Exact Match Required on First Name for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the first name is not exactly the same.

Yes/No:

Exact Match Required on Last Name for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the last name is not exactly the same.

Yes/No:

Exact Match Required on Street Address for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the street address is not exactly the same.

Yes/No:

Exact Match Required on Address Line 2 for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the second address line is not exactly the same.

Yes/No:

Exact Match Required on Apartment for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the apartment number is not exactly the same.

Yes/No:

Exact Match Required on City for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the city is not exactly the same.

Yes/No:

Exact Match Required on State for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the state is not the same.

Yes/No:

Exact Match Required on Company for Phone Interface

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the company name is not the same.

Yes/No:

Exact Match Required on Email Address

Defines whether a customer record received through the phone interface qualifies as a match to an existing record based on match code, even if the email address is not the same.

Yes/No:

Include Spaces in Special Handling Edit for Maximum Characters (F80)

Defines whether spaces are included in the edit the system performs to determine the maximum number of characters allowed for a custom special handling line.

Yes/No:

Display Entity Description (F84)

Defines whether to display the entity associated with an order at the CTI Customer Selection screen and in order inquiry.

Yes/No:

Update Original Source Code for Recipient Customers (F90)

Defines whether the system writes the source code defined for the sold to customer to the Original source field for a recipient customer.

Yes/No:

Position Cursor on Offer Field in OE/OM (F91)

Defines whether the offer field is blank for new order detail lines, in which case the cursor is positioned there for easy entry.

Yes/No:

Maximum Warranty Order Amount (F97)

Defines the maximum dollar amount allowed for warranty items on an order before the order is placed on hold.

Dollar Amount:

Maximum Life to Date Warranty Amount for Customer (F98)

Defines the maximum life to date warranty dollar amount allowed for a customer before an order for this customer including warranty items is placed on hold.

Dollar Amount:

Default Price Override Reason for Warranty Items (G01)

Defines the price override reason code the system defaults to an order detail line when an operator adds a warranty item to an order.

Code:

Customer Class for User Defined Field Prompting (G04)

Defines the customer class which requires prompting in order entry for user-defined fields.

Code:

Include Weight of all Items in Freight by Order Weight (G05)

defines whether the system adds together the weight of all non-ship alone items and ship alone items, regardless of the item's shipper or arrival date in the freight by order weight calculation.

Yes/No:

Price Override Reason for Business to Business Orders (G08)

Defines the price override reason the system assigns to each order detail line on a business to business order.

Code:

Batch for Business to Business Orders in Error (G09)

Defines the batch order number the system assigns to each business to business order that contain errors.

Number:

Job Description for Business to Business Order Generation (G13)

Defines the job description the system uses when a business to business order is processed through the B2B_GEN batch job.

Code:

Check Interface Payment Type (G26)

Defines the pay type the system identifies as the check interface payment type.

Number:

Check Interface Additional Charge Code (G27)

Defines the additional charge code the system applies to an order that contains the check interface payment method.

Code:

Default Offer Source Code to Order Detail Line (G28)

Defines whether the system defaults the source code defined for the offer on the order detail line to the Source code field on the order detail line.

Yes/No:

Auto Update Order Priority (G45)

Defines whether to automatically set order priority on the order ship to and order detail records to 9 when an arrival date override is entered in order entry/maintenance.

Yes/No:

Order Combination Pick Selection Type (G47)

Defines whether to update the Order combination type field in the Order Ship-to file during order entry with the combination of long SKU classes in an order.

Code:

Allow Order Number Override in Phone Interface (G54)

Defines whether to use the Retail transaction number to create a new order through the phone interface, or to use the next unassigned order number from the Number Assignment file.

Yes/No:

Display Customer Affinity Upon Order Accept (G58)

Defines whether to display the Select Affinity Items pop-up window in order entry when you accept an order from a customer the system has flagged as having one or more affinity preferences

Yes/No:

Display Backordered Affinity Items (G59)

Defines whether to display items that are on backorder, or are not available, in the Select Affinity Items pop-up window.

Yes/No:

Customer Affinity Recalculation Method (G60)

Defines whether the system uses the current date, or the customer’s last order date to update the Lifetime frequency rate field in the customer affinity records when you run the Batch Affinity Update function to update records.

Code:

Calculate Freight by Order Weight for N/C Orders (G68)

Defines whether the system charges freight on an order whose merchandise total is zero, when you calculate freight using the freight by order weight freight method.

Yes/No:

Use PartSmart Interface (G69)

Defines whether the system adds items from the PartSmart system to an order in order entry and order maintenance.

Yes/No:

Use Warehouse for PartSmart Item Availability (G71)

Defines the warehouse the system uses to reserve an item from the PartSmart system in order entry and order maintenance.

Number:

Electronic Gift Certificate Pay Type (G72)

Defines the credit card pay type that represents the electronic gift certificate pay type.

Number:

Require Gift Certificate/Coupon Number (G75)

Defines whether a Gift Certificate or Coupon number is required when you enter a Gift Certificate or Coupon pay type code in order entry.

Yes/No:

Use Net Perceptions (G79)

Defines whether the system accesses the Net Perceptions database to add items returned from the database to the Item Affinity Work file.

Yes/No:

Require Phone Number in Order Entry/Order Maintenance (H01)

Defines whether you are required to enter a phone number in at least one of the phone number fields on the order header screen in order entry/maintenance.

Yes/No:

Display Telemarketing Window in Order Entry (H02)

Defines whether the Display Telemarketing Specials window displays automatically in order entry when you accept your entries after entering items.

Yes/No:

Add Accompanying Items in Order Maintenance (H28)

Defines whether the system adds accompanying items to orders in Order Maintenance.

Yes/No:

Restrict SKU Scan by Offer (H34)

Restricts SKU display on SKU Scan screen to SKUs that are included in the offer associated with the order line.

Yes/No:

Bypass Geographic Zone Searching in Order Entry/Order Maintenance (H55)

Defines whether the system skips the search for a geographic zone, which is required for shipping zone reservation in order entry or maintenance.

Yes/No:

Update Customer Individual Order History File (H79)

Defines whether to track customer individual order history in addition to sold to order history.

Yes/No:

Use President’s Club Membership (H94)

Defines whether you assign customers to the President’s Club membership.

Yes/No:

Alternate Customer Number Label Description (H95)

Defines the name of the Alternate customer number (Interface cust code) field that displays on screens in CWDirect.

Code:

Number of Months to Prompt for President’s Club Renewal (H97)

Defines the number of months CWDirect waits before a President’s Club membership expires to prompt a customer for membership renewal.

Number:

Sell Out Set if Component is Sold Out (I05)

Indicates whether to sell out the entire set if one of the components is sold out.

Yes/No:

Include Telephone Number in Customer Search (I20)

Indicates whether to consider the customer’s evening or daytime phone number when searching for an existing customer as part of order creation in e-commerce, the phone order load, and the generic order interface.

Yes/No:

Automatically Display Coordinate Items in Order Entry (I53)

Defines whether the system automatically displays the Display Coordinate Items window when an item associated with coordinate items is added to an order.

Yes/No:

Default Unknown Source Code (I58)

Defines the unknown source code on the order header that triggers the system to default a new source code to the order header, based on the source code associated with the offer on the first order detail line.

Code:

Assign Drop Ship Expected Ship Date (I59)

Indicates whether to assign and display the expected ship date for drop ship items.

Yes/No:

Promotion Code Entry Required for Discount (I63)

Indicates whether the customer must specify a promotion code in order for the discount to apply to the order.

Yes/No:

Exclude Sale Item When Prorating Discounts (I65)

Indicates whether sale items should be excluded when prorating discounts applied through promotions.

Yes/No:

QAS Address Interface Values (I66)

Defines the system control values for the QAS Address Interface.

Use QAS Address Interface (I67)

Indicates if you use the QAS Address Interface.

Yes/No:

Address Interface User Hold Code (I68)

Defines the order user hold reason code the system assigns to an order if the order does not pass address verification in batch order entry.

Code:

Address Verification Data Library (B66)

Defines the name of the library including the QAS address verification interface data.

Code:

Address Verification Program Library (B67)

Defines the name of the library including the QAS address verification interface programs.

Code:

Display QAS Address Window for Single Response (I70)

Defines whether the system displays the QAS Address window when the system finds an exact match for the CWDirect address in the QAS address management system.

Yes/No:

Suppress Confirmation after QAS Picklist Selection (J01)

Defines whether the system displays the QAS Address window during interactive address processing after you select an address from the QAS Picklist window or QAS Range window.

Yes/No:

Perform Address Standardization in Customer API (I99)

Indicates whether to perform address standardization when creating or changing customer records through the generic customer API.

Yes/No:

Batch Number for Retail Channel Orders (I78)

Defines the order batch number the system assigns to retail channel orders received into CWDirect that are in error.

Number:

Suppress Email Address Search (J09)

Indicates whether to generate order-related emails even if the operator clears the order email address field.

Yes/No:

Clear Phone Interface Files (J14)

Indicates whether to clear records from the Phone Order Expanded and Phone Order files after transferring and loading remote orders.

Yes/No:

Default Individual Email Address (J17)

Defines whether the system defaults the individual email address to the Order email address field on an order. This system control value also controls whether you can prompt on the Order email address field to see a list of email addresses associated with the sold to customer on the order.

Yes/No:

Default Cancel Reason Code for PC Memberships (J23)

Identifies the cancel reason code to use when removing the President’s Club membership item from an order because the customer does not want to enroll in or renew the membership.

Number field:

Capture Addresses for Invoice (J24)

Defines whether to create a record in the Invoice Address file for the shipping and billing address associated with each shipment.

Yes/No:

Reserve from Non-Allocatable Warehouse (J25)

Defines whether the system can reserve inventory against a non-allocatable warehouse.

Yes/No:

Tax Interface Values (J29)

Use this screen to set up system control values related to the generic tax interface.

Use Generic Tax XML Interface (J10)

Defines whether to use when to use the generic tax interface.

Code:

Use TaxAreaID Lookup Message (J11)

Defines whether to request applicable tax area ID’s before requesting the tax quotation for a selected tax area ID.

Yes/No:

Display TaxAreaID Window in OE/OM (J12)

Defines when to display a pop-up window listing tax area ID’s.

Code:

Use Standard Tax Calc if Tax Interface Communication Fails (J13)

Defines whether to use the system’s standard tax calculation logic if there is no response using the generic tax interface.

Yes/No:

Display Non-Offer-Specific Telemarketing Specials in Order Entry (J31)

Indicates whether to display telemarketing specials only when they have been set up for the offer related to the order, or to display telemarketing specials that you set up so that any order, regardless of offer, is eligible.

Yes/No:

Evaluate Loyalty Eligibility within Qualifying Order (J34)

Indicates whether to apply the loyalty discount and other benefits on the order with which the customer qualifies for the loyalty membership.

Yes/No:

Apply Loyalty at the End of Order (J35)

Indicates whether to apply the loyalty discount to order merchandise after all other applicable discounts.

Yes/No:

Fulfillment Order Type (J36)

Indicates the order type code that identifies orders you receive from a remote inventory location system.

Code field:

Apply End of Order Discounts during Repricing (J37)

Defines whether the system applies certain end-of-order discounts to the order during repricing and the initial order accept in addition to the final order accept.

Yes/No:

Copy Set Master Special Handling to Set Components (J39)

Indicates whether to automatically copy special handling instructions from the set master item to its eligible component items.

Yes/No:

Sum Price of Components for Set Master in Order Response Message (J40)

Indicates whether to sum the price of component items for sets priced at the component level in the detailed response message for the generic order API.

Yes/No:

Update Fulfillment Operations Control Totals with Offer Price (J46)

Indicates whether to update the Fulfillment Operations Control Summary file using the offer prices for merchandise because Fulfillment orders are accepted at “no charge.”

Yes/No:

Default Item Availability Screen in Order Entry (J60)

Indicates whether to advance automatically to the Display Item Availability screen in order entry before you have the option to select a customer.

Yes/No:

Calculate Expected Date in OE if No PO (J61)

Indicates whether the system should calculate an expected ship date for a backordered item that is not on any open purchase orders.

Yes/No:

Include Projected Returns in Available Quantity for Download (J62)

Indicates whether to include the Projected returns for an item in the availability calculation and indicate an expected ship date for a backordered item that is not on any open purchase orders when sending availability information to the web storefront.

Yes/No:

Search Offers for Alias (J68)

Indicates whether to search across all active offers for an alias matching the entry in the Item field.

Yes/No:

Pre Billed Amount Item (J72)

Indicates the item to add to an order as a means to pre-bill a percentage of an item price.

Code:

Price Override Reason for Pre Billed Amount Item (J73)

Indicates the price override reason code to use when adding the Pre Billed Amount Item (J72) to an order.

Code:

Restrict Pre Billed Amounts to Drop Ship Items Only (J76)

Indicates whether to add the Pre Billed Amount Item (J72) to an order if the item flagged for pre-billing is not a drop ship item.

Yes/No:

Allow Multiple Credit Card Applications (J80)

Defines whether a customer can apply for each type of credit card brand being offered.

Yes/No:

Number of Days for CC Application Request (J81)

Defines how often a credit card offer should be presented to a customer during order entry.

Number:

Exclude Business Addresses from Credit Card Applications (J82)

Defines whether customers with a business address are excluded from the credit card application process.

Yes/No:

Display SKU Description on Scan Order Detail Screens (J90)

Defines whether the system displays the first 16 positions of the SKU description in place of the SKU code on the Scan Order Detail screen in order entry, order maintenance, and order inquiry.

Yes/No:

Update Source Code from Mail History (J94)

Defines whether the system updates the source code and offer on an order line based on the most recent customer mail history associated with the item on the order line.

Yes/No:

Payment Processing Values (K21)

Use this screen to set up system control values related to online cash payment processing. See Online Cash Payment Overview and Setup for an overview and the required setup.

Pay Type for Payment Processing (K16)

Defines the pay category 1 (cash/check) pay type used for online cash payment processing with an online bill pay system.

Number:

Hold Reason for Payment Approval (K17)

Defines the hold reason code the system applies to online cash payment orders that have received approval from the online bill pay service and are waiting for the customer to pay for the order using funds from his bank account.

Code:

# of Days to Auto Cancel Orders Pending Payment (K18)

Defines when to automatically cancel an order that contains an online cash pay type that has not been paid by the customer within a specified number of days. The system evaluates the order date on orders with an online cash pay type whose Amount collected is blank and if the order date is older than the number of days defined in this system control value, the system cancels the order.

Number:

Cancel Reason Code for Orders Pending Payment (K19)

Defines the cancel reason code the system applies to orders that are automatically cancelled because the online cash pay type on the order has not been paid by the customer within the number of days defined in the # of Days to Auto Cancel Orders Pending Payment (K18) system control value.

Number:

Hold Reason Code for Suspect Order Payments (K20)

Defines the hold reason code the system applies to orders that contain an online cash pay type whose sold to customer has been flagged as suspect by the online bill pay system, indicating potential fraudulent payment activity.

Code:

Default Payment Processing Open Item Type (K24)

Defines the type of A/R open item the system creates when an unmatched online cash payment is received from the online bill pay system that the system is able to match to a sold to customer.

Code:

Third Phone Number Type (L53)

Defines whether to label a customer’s third phone number as Fax or Mobile on screens and reports.

Code:

Include Projected Returns in Available Quantity for OE (L68)

Defines whether the system includes the projected return quantity defined for an item/SKU in the expected quantity that displays in order entry, but not when calculating the available quantity when communicating with your web storefront.

Yes/No:

Tax API Default Entity (L67)

Defines the entity that the Tax API should send to Vertex in tax quotation requests.

Number:

Ship Via Priority for Ship To Mismatch (L71)

Defines the ship via priority that prompts the system to place an order on SM Ship To Mismatch hold, provided the order also exceeds the dollar amount specified in the Maximum Order Amount for Fraud Checking (D24) and the number of times shipped to the address on the order is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).

Number field:

Use Gift Card Fraud Checking (L72)

Defines whether the system places an order on hold if it contains a stored value card item and a stored value card payment method.

Yes/No:

Use Single Use Promo Codes (L95)

Defines whether you can control the use of promotions through randomly generated single-use codes.

Yes/No:

Order API/No Reprice Price Override Reason (L96)

Defines the price override reason code that controls whether an order or order line is eligible for any promotion discounting or benefits, or whether these discounts and benefits have already been applied by the web store.

Code field:

Current Offer (A33)

Purpose: Use this screen to define the offer code to use in Inventory Inquiry and Item Availability.

MSR0051 CHANGE Change System Control Value 11/09/99 10:31:20

Description . : Current Offer number

Code . . . . . OFR AAA ABC BCH CAN

CCC C96 C97 C99

DDD IS1 ITY ...

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code of the offer to use to supply an item's price in Inventory Inquiry and to track lost sale information.

Inventory Inquiry: The system displays the offer and the item's price using the offer that you define in this field.

Lost Sales: This information is captured when an operator enters a lost sale on the Item Availability screen in Order Entry. The offer to use varies, based on whether you use cross-company scanning in your company; see Order Entry Chapter 17: Inquiring into Item Availability (DIAV) for more information.

Offer codes are defined in and validated against the Offer file; see Marketing Chapter 2: Working with Offers (WOFR).

Primary Upsell Category (A67)

Purpose: Use this screen to define which upsell window should appear in Order Entry.

MSR0051 CHANGE Change System Control Value 11/09/99 10:33:08

Description . : Primary Upsell Category

Code . . . . . *NONE *NONE SOURCE CUST CLASS STATE

PAY TYPE

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code that identifies which upsell window to open in Order Entry when the customer is eligible for multiple order header upsell promotions. Valid entries are:

*NONE

SOURCE

CUST CLASS

STATE

PAY TYPE

If you leave this field blank, no upsell windows appear during Order Entry.

If a customer is eligible for more than one upsell promotion (Source, Customer Class, State, and/or Paytype), and no primary upsell category is defined here, all upsell windows for which the customer is eligible appear. Otherwise, if a customer is eligible for more than one upsell promotion and a primary upsell category is defined, only the primary upsell window appears.

Example: If SOURCE is defined here and the customer is eligible for both source and customer class, only the source upsell window opens. However, if SOURCE is defined here and the customer is eligible for customer class and state upsell promotions, both windows open.

More information about Upsell Promotions: These order header upsell promotions are defined in the Upsell Promotion file. (See Marketing Chapter 18: Working with Upsell Promotions (WUPE).) You can set up promotions in one or more categories. An upsell promotion establishes special prices for up to three items, based on one of the following categories:

• customer's source code

• customer class

• sold-to state

• payment type

• item class

• day of the week

A pop-up window appears in Order Entry if the customer or order is eligible for an Upsell Promotion. The upsell window contains up to three items, one line of text describing each upsell promotion, the price and availability of each item. No upsell window appears if there is an item restriction or if there is no available inventory.

The system tracks the demand and sale of upsell items separately from all other items. This allows you to analyze the number and dollar value of items that are sold as a part of an upsell promotion.

Fraud Checking (A68)

Purpose: Use this screen to define whether to perform fraud checking against customer name and address information during credit checking routines.

MSR0052 CHANGE Change System Control Value 11/09/99 10:35:49

Description . : Fraud Checking

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system assembles a match code for each address on the order, using the three match code algorithms defined in the Match Code file. The system then checks the match codes against the existing in the Fraud file records in order to flag fraud customers. (See Customer Service Chapter 80: Working with Customer Fraud Files (WCFD).) You must set up the standard match code and the three fraud match code algorithms (F1, F2, and F3) through the Change Match Codes function. See Customer Service Chapter 19: Setting Up Match Codes (MMCH).

The customer sold-to, bill-to, ship-to, and order address information is evaluated.

Also, the system checks the Miscellaneous Fraud file, in which fraudulent zip codes, credit cards, email addresses, IP addresses, and checks are defined. Any order with a match in this file is put on hold.

If you enter N in this field, the system does not perform fraud checking; however, it still evaluates fraudulent credit cards and checks as defined in the Miscellaneous Fraud file. If it finds a match, it puts the order on hold.

For more information: See Working with Miscellaneous Frauds (WMFF) for information on entering miscellaneous frauds. Also, see Introducing Order Hold Reason Codes for an overview of the various hold reason codes used in fraud checking.

Fast Track Inventory (A70)

Purpose: Use this screen to define whether to perform fast track item conversion in Order Entry and Order Maintenance.

MSR0052 CHANGE Change System Control Value 11/09/99 10:39:09

Description . : Fast Track Inventory

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system performs fast track item conversion in Order Entry and Order Maintenance.

If you enter N in this field, you cannot use fast track item conversion.

About fast track item entry: With fast track item entry, you enter a “dummy” item that the system converts to one of three valid items, based on a purchase date, cutoff code, and/or serial number. Fast track item processing is useful when you sell date-sensitive, warranty or upgrade items and the system, not the Order Entry operator, determines which item the customer should actually receive.

The Fast Track Inventory (A70) system control value must be set to Y for the system to perform fast track item conversion.

The system performs fast track item processing only for items defined in the Fast Track Item file; regular items are handled as usual.

Fast track items are items that are not kept in your inventory. Based on a serial number or a cutoff date, the system replaces the fast track item with one of three valid items.

Fast track items are defined in the Fast Track Item file (WFTI). The item conversion (how the system will replace the generic, fast track item with a another item) depends on the value in the Cutoff code field in the Fast Track Item record, which may contain:

D = Item conversion based on purchase date

S = Item conversion based on serial number

B = Item conversion based on purchase date and serial number

N = Item conversion based on neither factor, the system will replace the fast track item automatically with representative item #1.

Note: A “dummy” record must exist in the Item file for the fast track item. In addition, the conversion items must exist in the Item file. See Working with Existing Items (MITM).

For more information: See Merchandising Chapter 30: Working with Fast Track Items (WFTI).

Default Version for Order Entry (A71)

Purpose: Use this screen to define the format of the initial screen to display when enter an order.

MSR0051 CHANGE Change System Control Value 11/09/99 10:41:02

Description . : Default version of Order Entry

Code . . . . . HEADER HEADER HEADER/DTL

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: You can enter HEADER or HEADER/DTL as the default.

If you define HEADER as the default version, the initial screen in Order Entry is the Work with Order Screen (where you can enter name, address, and order information). The next screen to display is the Work with Order Lines Screen (Adding Items to the Order) (where you can enter item information).

If you define HEADER/DTL as the default version, the initial screen in Order Entry is the Work with Order/Detail Screen, a single, combination screen. The top half of this screen presents name and address information; the lower half of this screen presents one line for the entry of detail line information.

If you leave this field blank, it defaults to HEADER.

Page/Letter Entry (A72)

Purpose: Use this screen to define whether you use the catalog page/letter format.

If you entered Y in the Fast Track Inventory (A70), you cannot use the Page/Letter Entry (A72) system control value. Page Letter Entry changes the format of the item entry line so that Fast Track Inventory cannot be used.

MSR0052 CHANGE Change System Control Value 11/09/99 10:44:22

Description . : Page/Letter entry

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you must enter the catalog page/letter assignment for the item when entering detail lines during Order Entry and Order Maintenance, instead of entering item numbers.

For example, with page/letter format, the customer might order a jacket by requesting “...14B...”. This code consists of the page in which the item is presented and a corresponding letter.

The formats for Regular Item Entry and Page Letter Entry are shown in the following examples:

Regular item: When using regular item entry, you type the item number, and the individual SKUs. For example, with regular item entry, the customer orders a jacket by requesting “item # 5372, size = SML, color = MUL.” You enter the item number in the Item field, which is a 12-position field similar to the following example:

Ofr Item SIZE CLR STYL Qty Price N/C Ovr C/G S/H Whs

 

Page/letter entry: With Page/Letter entry each item included in the catalog is assigned a code instead of an item number. This code consists of the page in which the item is presented and a corresponding letter. The customer orders an item using the page/letter code and the desired SKU. For example, with page/letter format, the customer orders a jacket by requesting “...14B, size = SML, color = MUL...”. You enter the page/letter code in the Page/Letter field, as shown in the following example.

Pay By: N O S

Ofr Page/Letter SIZE CLR STYL Qty Price C V C/G H

1 36A 1

 

To use this feature, a page/letter assignment must be defined for each item in the Item/Offer file. See Merchandising Chapter 27: Assigning Items/SKUs to Offers.

Note: In page letter entry, you enter just the letter code, not the page number. For example, if you create a page letter of 234 for an item on page 56, you enter 234 in order entry.

Order Entry Batching Default (A73)

Purpose: Use this screen to define the default value for order batching.

MSR0052 CHANGE Change System Control Value 11/09/99 10:47:12

Description . : Order Entry Batching Default

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the default value for Are the orders batched? field on the initial Order Entry screen are set to Y.

If you enter N in this field, the default value for Are the orders batched? field is set to N.

In either case, this value can be overridden.

If you leave this field blank, this field defaults to N.

For more information: See Chapter 25: Introducing Batch Order Entry.

Allow Multi-Payment Types (A74)

Purpose: Use this screen to define whether a customer can apply more than one payment type to an order.

MSR0052 CHANGE Change System Control Value 11/09/99 10:49:04

Description . : Allow Multi Payment Types

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you can enter more than one payment type on an order during Order Entry and Order Maintenance.

If you enter N in this field, you can enter only one pay type in Order Entry and Order Maintenance.

If you leave this field blank, this field defaults to N.

For more information: See Customer Service Chapter 71: Enter Payment Methods Screen.

Display Order Recap (A75)

Purpose: Use this screen to define whether the Order Recap screen should be displayed at the end of an Order Entry session.

MSR0052 CHANGE Change System Control Value 11/09/99 10:50:24

Description . : Display Order Recap

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you advance to the Order Recap screen at the end of Order Entry; also, the system prompts for a payment method information when you press F19.

If you enter N inthis field, you cannot display the Order Recap screen.

This screen presents a summary of bill-to/ship-to address, shipping, pay type, and order total information that can be repeated to the customer prior to accepting the order. You can also enter credit card and pay type information on this screen.

If you leave this field blank, the value defaults to N.

You must set this field to Y if you want to Display Customer Affinity Upon Order Accept (G58).

For more information: See Work with Order/Recap Screen in Order Entry Chapter 4.

Sample Order Recap screen:

OER0269 ENTER Work with Order/Recap 6/23/97 10:15:40

Enter The Mail Order Company

Hold

Order#: 1169 - 001 Type: P PHONE ORDERS

Sold To: 12541 Recipient: 0 Wgt: .000

MARC JOHNSON

LEX AUTOPARTS

35 PLEASANT STREET

2

HOLLISTON MA USA

01746 Delivery R (B,R) Delivery (B,R)

Via 1 Priority 9 Arrival date 62397 Source TAN PO#

------------------------------------------------------------------------------

P T Credit Card# . Expiration date Auth#

a y Credit/Coupon# . . . . . Credit/Coupon$ . .

y p Credit/Coupon# . . . . . Credit/Coupon$ . .

e Amount . . . . . :

------------------------------------------------------------------------------

Merch Frt Frt+ Tax Hnd Chg Total

14.00 1.00 15.00

Discount 14.00- G/M 11.00 G/M% 78.57

F2=Sold To/Recip F4=Prompt F6=Bill To F7=Cust Ship To F8=Work w/detail

F9=Accept F11=Reject F14=Order Ship To F15=Payments F24=More keys

Create/Assign Bill To Customers in Order Entry (A76)

Purpose: Use this screen to define whether you want to be able to create or assign an existing customer's billing address to another customer placing an order (sold-to customer) during Order Entry.

MSR0052 CHANGE Change System Control Value 11/09/99 10:52:36

Description . : Create/Assign Bill To customers in Order Entry

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y inthis field, you can assign a bill-to address to an order in Order Entry. This bill-to address is for this order only; it is not added as a permanent bill-to address in the Customer file. If you add a bill-to address to an order in Order Entry, the order is placed on (UB type) hold for an “unreferenced bill-to.”

If you enter N in this field or leave this field blank, you must assign a bill-to address to the sold-to customer using the Work with Customer function before you can create an order for this particular bill-to/sold-to combination; otherwise, if you use an A/R payment method on the order, the system creates a bill-to using the name and address information of the sold-to customer, and assigns that customer to the order and to the customer sold-to.

E-commerce orders: When you use the new order message in the e-commerce interface to create a new sold-to customer, the system does not prevent you from assigning a bill-to customer to the order regardless of the setting of this system control value. However, you can use the Update Customer Sold to with Bill to Account Number for New E-Commerce Orders (H87) system control value to control whether the bill-to account number is assigned to the sold-to customer, or if the bill-to is assigned to that particular order only.

For more information: See Creating and Updating Bill-to Customers (WCBT) for an overview on bill-to customers.

Default Ship Via (A77)

Purpose: Use this screen to define the default shipper on the initial Order Entry screen.

MSR0054 CHANGE Change System Control Value 11/09/99 10:59:30

Description . : Default Ship Via

Number . . . . 2

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Number field: Enter the number for the shipper to default in the Ship Via field on the initial Order Entry screen.

This code must be established in the SCF/Ship Via file. See Fulfillment Chapter 32: Working with SCF/Ship Via Values (WSHV).

There are several ways the system can override the shipper specified on the order with another shipper. See Ship Via Override Hierarchy for a list of ways the system can override the shipper specified on the order with another shipper and the hierarchy in which the ship via overrides take precedence.

Vertex Interface (A88)

Purpose: Use this screen to define whether you use the Vertex® Sales Tax L Series™ to calculate tax.

MSR0052 CHANGE Change System Control Value 11/09/99 13:05:11

Description . : Vertex Interface

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y if you are using the Vertex product, Sales Tax, to calculate tax.

Enter N if you are using tax tables within CWDirect to calculate tax.

About Vertex Sales Tax L Series: The Vertex® Sales Tax L Series™ product calculates taxes on your orders and passes this information back to the system at strategic points, such as Order Entry, Order Maintenance, Reservation and Confirmation.

The appropriate tax rate is calculated at each of these points. The tax rate is determined by the shipping address on the order.

Sales Tax by Vertex is software that must be purchased separately.

Sales Tax stores the tax rates for each taxing jurisdiction in the United States and Canada, and provides the necessary reporting for each jurisdiction in which you sell or operate. When you use Salestax, you do not have to specify tax rates in the system.

Additionally, Sales Tax allows you to predefine whether freight charges are included in the taxable amount on an order.

Note: You cannot use both Vertex and tax-inclusive pricing (VAT) in the same company. See Tax Included in Price (E70) for more information on VAT.

For more information: See CWDirect/Vertex Interface for information about using Sales Tax.

Vertex Tax Method (A89)

Purpose: Use this screen to define how you access the Vertex Sales Tax calculation system: by City/State/Zip (City/St/Zp) or State/Zip (State/Zp).

You only need to complete this field if the system control value, Vertex Interface (A88), is set to Y.

MSR0051 CHANGE Change System Control Value 11/09/99 13:07:15

Description . : Vertex Tax Method

Code . . . . . CITY/ST/ZP CITY/ST/ZP STATE/ZP

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code that represents how the Vertex Sales Tax package calculates tax. Valid codes are:

CITY/STATE/ZIP indicates that tax is calculated for the state, county, and city. Additionally, the system offers city/state/zip scanning functionality when this method is selected.

A City/State/Zip scan appears when you enter an order in which the city name is not recognized. The system provides a list of cities/states/zips that are phonetically close to your entry.

STATE/ZIP indicates that tax is calculated for the state only.

For more information: See CWDirect/Vertex Interface for information about using Sales Tax.

GST Rate (A90)

Purpose: Use this screen to define the default GST (goods and service tax) rate.

MSR0057 CHANGE Change System Control Value 11/09/99 13:08:48

Description . : GST Rate

Percentage . .

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Percentage field: Enter the GST rate to default when you enter orders for Canadian companies or for orders shipped to Canada. The GST rate can be overridden in the SCF or Postal Code Tax files. This field is 5 positions with a 2-place decimal.

The default GST rate is a federal Canadian tax applied to all orders, unless exceptions exist. This tax is levied on merchandise shipped to and within Canada. This tax structure applies only to companies that operate in Canada and only to orders that are shipped within Canadian boundaries.

Example: In 1993, the current GST Rate was 7%. This tax is levied on all orders that may include merchandise and, optionally, freight charges.

The system calculates GST on an order only if a GST/PST tax method is defined in the SCF or Postal Code file.

When is GST not used? Without any overrides, GST is calculated by multiplying the GST by the taxable total on the order; however, any exceptions to this default may include:

Override by Item: The GST Tax Exemption file is used to establish tax exceptions for specific items in different provinces. This file accommodates situations in which the GST and PST apply to an item in one province, yet in another province, only the PST or the GST applies. This file is also used to define an item as non-taxable in a particular province.

Override by Province: Establishes an override at the province level that is higher or lower than the default GST Rate. You can override the GST rate that applies to a specific province in a particular SCF or postal code. In some cases, the government has made a stipulation that a particular province can be subject to a GST rate higher or lower than the average.

Override by Customer: Establishes exceptions or exemptions for a customer to GST or PST (Canadian Provincial Services Tax).

Orders subject to VAT: If you set the Tax Included in Price (E70) system control value to Y, orders to certain provinces may be subject to tax-inclusive pricing and VAT rather than GST and PST. See the description of this system control value later in this chapter for more information.

For more information:

• see Fulfillment Chapter 31: Working with SCF Codes (WSCF) for more information on working with SCF tax rates.

• see Customer Service Chapter 15: Setting Up the Postal Code File (WZIP) for more information on working with postal code tax rates.

• see Merchandising Chapter 32: Working with GST Tax Exemption Status (MGTX) for more information on working with GST item tax exemptions.

• see Customer Service Chapter 32: Working with Customer Tax Status for more information on working with customer tax status.

GST Item Status Default (A91)

Purpose: Use this screen to define the GST default tax status when a new item is created.

MSR0051 CHANGE Change System Control Value 11/09/99 13:11:18

Description . : GST Item Status Default (P,G,B,N)

Code . . . . . B P G B N

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code that defines the default tax status that applies to items subject to GST and PST tax.

The appropriate tax is calculated on all items ordered and on freight, if applicable. The defaults are:

P = Only the Provincial Services Tax (PST) applies to items. This is a province-level tax.

G = Only the Goods and Services Tax (GST) applies to items. This is a federal tax.

B = GST and PST apply to items.

N = Neither tax applies.

You can establish overrides for items being shipped to certain provinces. The Work with SCF Codes function allows you to establish GST and PST rates for a geographical area; the system then uses the default GST item status for each item. See Fulfillment Chapter 31: Working with SCF Codes (WSCF) for more information.

You can also establish GST and PST rate information for a postal code; if you define information at this level, it overrides the SCF rates. See Customer Service Chapter 15: Setting Up the Postal Code File (WZIP) for more information.

You can override the GST status for individual items by province as well. See Merchandising Chapter 32: Working with GST Tax Exemption Status (MGTX) for more information on working with GST tax exemption status for items.

Note: You must set this system control value to B to use a GST or PST tax exemption for items in provinces.

Example:

• Default GST rate in the System Control file = 7.00

• Default GST Item Status Default in the System Control file = B

Example 1

PST defined for the SCF = 5.00

GST field for the SCF is blank

no override defined for the item in the GST Tax Exemption Status file

GST of 7% and PST of 5% charged for the item (system uses default GST and GST Item Status Default from the System Control file)

Example 2

PST defined for the SCF = 5.00

GST defined for the SCF = 6.00

no override defined for the item in the GST Tax Exemption Status file

GST of 6% and PST of 5% charged for the item (system uses GST override defined for the SCF and GST Item Status Default from the System Control file)

Example 3

PST defined for SCF = 5.00

GST field for the SCF is blank

override tax status of G (calculate GST only) defined for the item in the GST Tax Exemption status file

GST of 7% only charged for the item (system uses the default GST from the System Control file and the override tax status for the item defined in the GST Tax Exemption Status file)

GST and PST are Canadian taxes that apply only to companies that operate in Canada and only to orders shipped to and within Canadian boundaries. The Goods and Services Tax (GST) is a federal tax applied to all orders, with some exceptions. The Provincial Services Tax (PST) applies only to orders shipped into a province, with some exceptions. These exceptions are explained for the control value, GST Rate (A90).

Maximum Order Amount (A92)

Purpose: Use this screen to define the order amount to cause an order to be placed on hold automatically.

MSR0056 CHANGE Change System Control Value 11/09/99 11:00:49

Description . : Maximum Order Amount

Dollar amount . 1000.00

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Dollar amount field: Enter the dollar amount to cause an order to be placed on hold automatically. This field is 12 positions with a 2-place decimal.

This dollar amount hold applies to all methods of payment.

If the total amount of the order is greater than the amount defined here, the order is placed on dollar hold (DH type hold) when Credit Checking is performed (when pressing F9 or F19 to accept a new order). These orders appear on the Release Held Orders screen and must be released from hold manually using Release Held Orders. See Customer Service Chapter 82: Selecting Held Orders (ERHO).

E-Commerce orders: You can define a separate dollar amount to cause an e-commerce order to be placed on hold automatically by entering a dollar amount in the Maximum Order Amount for E-Commerce Orders (H54) system control value.

Note: You must specify a value for the Maximum order amount system control value to have the Maximum Order Amount for E-Commerce Orders (H54) apply to e-commerce orders.

Leave this field blank if you do not want to establish a maximum dollar amount.

Use State Shipping Matrix (B12)

Purpose: Use this screen to define whether to use the State Shipping Matrix when calculating freight.

MSR0052 CHANGE Change System Control Value 11/09/99 12:46:04

Description . : Use State Shipping Matrix

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . FRT

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system checks the State Shipping Matrix when calculating freight. Freight charges defined in this matrix can override a line level freight charge calculated on an order.

Enter N, if you do not want to use the State Shipping Matrix when calculating freight.

Using the state shipping matrix: The State Shipping Matrix allows you to define the shipper assignments and freight charges, based on the ship-from and ship-to state combinations.

The State Shipping Matrix is used when this control value is set to Y and the source code uses a line-level freight method, such as Flat Rate by Item (FI), Flat Rate/Quantity (FQ), Flat Rate/Item Source (FS), Item (I), or Weight (W).

If you do not use a freight by line method, the system does not consult this matrix.

If the system finds a record in the matrix, it uses that information to override the ship via assigned to the order and/or to calculate shipping charges.

The system checks the record for the ship-to state and use the value in the Frt% field to calculate the freight charge, based on the merchandise total on the line.

Additionally, the system uses the value in the Min frt field if the calculated freight charge is under the minimum amount. An additional freight charge is calculated if a value is present in the Add'l% field. The calculation is based on the merchandise total on the line.

These calculations are performed on each line on the order, except for vendor drop ship items. The freight charge for each vendor is calculated by totaling the merchandise amount for the vendor and multiplying this total by the Frt%. The system validates this freight charge against the value in the Min frt field. The difference between the calculated freight charge and the Min frt value is added to the order in the Fr+ (additional freight) field in Order Entry.

The system also overrides the designated shipper if the ship-to state matrix record contains ship via overrides for the preferred ship via or truck via.

For more information: See Fulfillment Chapter 34: Working with State Shipping Matrix (WSSM).

Use Zip/City/State Defaulting? (B13)

Purpose: Use this screen to define whether you want the city and state fields to default during Order Entry.

MSR0052 CHANGE Change System Control Value 11/09/99 12:01:30

Description . : Use Zip/City/State defaulting?

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 100

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, when you enter a postal code in Order Entry, the system provides the associated city and state (as defined in the Postal Code/City/State file).

Additionally, the system:

• Validates your entries to the Postal Code, City, and State fields.

• Displays the Select Zip/City/State window when you prompt on the Postal code field.

You must have a completed Postal Code/City/State file. You must manually enter this information or receive a tape from a service bureau which you can use to load this file.

If you enter N in this field, the city and state do not default. Additionally, the system does not validate your entries to the Postal Code, City, and State fields or allow you to prompt on the Postal code field.

If you leave this field blank, this field defaults to N.

For more information: See Customer Service Chapter 15: Setting Up the Postal Code File (WZIP).

Tax on Freight (B14)

Purpose: Use this screen to define whether the system charges tax on freight, in addition to merchandise.

MSR0052 CHANGE Change System Control Value 11/09/99 13:22:13

Description . : Tax on Freight

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: If you enter Y in this field, the system charges tax on freight.

If you enter N in this field, tax is not calculated on freight.

If this field is left blank, the value defaults to N.

If you set this field to N, you can never charge tax on freight. An N or blank value in this field overrides all other settings in the system.

Tax on Handling (B15)

Purpose: Use this screen to define whether the system charges tax on handling, in addition to merchandise.

MSR0052 CHANGE Change System Control Value 11/09/99 13:23:41

Description . : Tax on Handling

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system charges tax on handling; however, you can override this setting for a postal code, SCF, or a specific special handling code. For more information, see:

• excluding a special handling code from tax: Establishing Additional Charge Codes (WADC)

• overriding at the postal code level: Setting Up the Postal Code File (WZIP)

• overriding at the SCF level: Working with SCF Codes (WSCF)

• tax hierarchy overview: About Tax Rates

If you enter N in this field, you can never charge tax on freight. An N or blank value in this field overrides all other settings in the system.

If this field is left blank, this value defaults to N.

Default Country for Customer Address (B17)

Purpose: Use this screen to define the country code to default on the initial Order Entry screen.

MSR0051 CHANGE Change System Control Value 11/09/99 12:03:03

Description . : Default Country for Customer Address

Code . . . . . USA ABC ASD BRZ CAN

ITY JPN USA

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 100

F3=Exit F12=Cancel

Code field: Enter the code for the county to default in the Country field on the initial Order Entry screen and the Create Customer screen.

The country specified is validated against the Country file. Valid codes appear to the right of the Code field. See Customer Service Chapter 14: Setting Up the Country File (WCTY).

Catalog requests: CWDirect defaults the country code defined in this system control value to a catalog request that is missing the country code.

Brokered backorders: The Order Broker Include Default Country Orders Only (M29) system control value controls whether you submit backordered lines to Locate for fulfillment if the orders are not shipping to the default country specified here. See Brokered Backorder Integration with Locate for background.

If you leave this field blank, no code defaults in Order Entry or Customer Maintenance.

Dynamic Creation of Coupons (B21)

Purpose: Use this screen to define whether you are able to enter unnumbered coupons or credits in Order Entry.

MSR0052 CHANGE Change System Control Value 11/09/99 11:04:47

Description . : Allow dynamic creation of coupon/credits?

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 110

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you can enter a coupon number that does not exist in the Coupon Redemption file and the system creates a coupon record. The system checks to see if the customer has redeemed the coupon number previously. If so, a message displays that the coupon has previously been redeemed.

This feature is used to support companies that insert a coupon in their offers and ensure that the coupon is only used once. A “dummy” number is assigned to the coupon (for example, 99999). When the customer tries to redeem the coupon through a phone order, the Order Entry operator enters 99999 in the Coupon # field and the amount of the coupon. Order Entry checks that coupon number 99999 has not been used previously by the customer. If not, the system creates a coupon redemption record and identifies the coupon as used.

If you enter N in this field, you can only enter system-assigned coupons. When the operator enters a coupon number and amount, Order Entry validates that the coupon has not been redeemed and checks to ensure that the amount is valid.

If you leave this field blank, this field defaults to N.

Related system control value: If system control value Require Gift Certificate/Coupon Number (G75) is set to Y, you must enter a coupon number when you use a coupon as payment method; however, you can enter a number that does not exist, and have the system create the coupon record if Dynamic Creation of Coupons is also set to Y.

For more information: See Customer Service Chapter 121: Generating and Deleting Coupons (MCPN).

Allow Dynamic Creation of Cash Control Numbers (B20)

Purpose: Use this screen to indicate whether you want to define cash control numbers for checks during Order Entry, or if you want the system to automatically display the cash control numbers entered for the Cash Batch procedure.

This control value works in conjunction with the Batch Cash? (B22) control value. If the Batch Cash feature is used, set this field to N.

MSR0052 CHANGE Change System Control Value 11/09/99 12:42:52

Description . : Allow dynamic creation of cash control numbers?

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 109

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you can enter new cash control numbers for checks during Order Entry, (meaning that a cash control number was not assigned when the cash batch was entered).

If you enter N in this field and you have set the Batch Cash? (B22) control value to Y, the batch control number from the Batch Details screen is assigned automatically during Order Entry. Order Entry validates the cash control number entered against the Order Pending Check file (created in Cash Batching). If you enter a cash control number that doesn't exist, you see an error message, and you cannot assign the cash control number.

If you leave this field blank, this field defaults to N.

For more information: See Order Entry Chapter 26: Opening a Cash Batch (WCSH).

Batch Cash? (B22)

Purpose: Use this screen to define whether you batch cash prior to Order Entry.

MSR0052 CHANGE Change System Control Value 11/09/99 12:44:14

Description . : Batch cash?

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 112

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, you can group mail orders into specific segments or batches (of 25, for example), and the system assigns a batch control number to each batch of orders and checks. Persons responsible for these procedures enter the cash control numbers, check numbers, and micra numbers (the code at the bottom of the check) for each order.

In Order Entry, the operator is prompted to open a specific batch of orders when accessing Order Entry. The orders entered in Order Entry are compared against the values in the associated cash batch. This procedure controls the Order Entry process and ensures that the information entered prior to Order Entry matches the information during Order Entry. See Order Entry Chapter 26: Opening a Cash Batch (WCSH).

If you enter Y in this control value, set the system control value, Allow Dynamic Creation of Cash Control Numbers (B20)to N.

If you enter N in this field, you can still manually batch orders, however no entry is done on the system prior to Order Entry.

If you leave this field blank, this field defaults to N.

Default Order Type (B28)

Purpose: Use this screen to define the order type to default in Order Entry.

MSR0051 CHANGE Change System Control Value 11/09/99 11:02:09

Description . : Default Order Type

Code . . . . . P B C F M

O P

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code that defines the order type to default in the Order Type field on the initial Order Entry screen.

Typical order types include:

• mail orders

• phone orders

• fax orders

• retail orders

• e-commerce orders

as well as others that you define in the Order Type file. This field is validated against the Order Type file. Codes defined in this file appear to the right of the Code field. See Customer Service Chapter 1: Establishing Order Types (WOTY).

This default can be overridden. If you leave this field blank, no order type defaults in Order Entry.

More about order types: The order type controls the appearance of the detail screen. This is a useful feature because you may have different requirements of the Order Entry detail screen when you enter a phone order for a customer versus when you enter an order from an order form. You are not restricted, however, to the default order type screen display. A function key is available allowing you to change to another format.

The order type controls whether promotional pricing and/or upsell windows open automatically in Order Entry and whether to generate soldout notification cards.

Default Order Quantity (B30)

Purpose: Use this screen to define the order quantity to default in Order Entry.

MSR0055 CHANGE Change System Control Value 11/09/99 11:06:56

Description . : Default Order Quantity

Quantity . . . 1

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Quantity field: Enter the number to default in the Quantity field on each order detail line.

If you leave this field blank, the Quantity field on the order detail line requires an entry each time an item is entered.

Pricing Values (B31)

Purpose: Use this screen to define how to perform pricing in Order Entry and Order Maintenance.

MSR0413 ENTER Edit Pricing Values 5/07/99 8:43:39

KAL Co.

Best Way Pricing . . . . . . . . . . Y (Y/N)

Search Offers for Price . . . . . . (Y/N)

Offer Price Sequence # . . . . . . . 1

Quantity Break By SKU Sequence # . . 2

Column Sequence # . . . . . . . . . 3

Special By Source Sequence # . . . . 4

Contract Sequence # . . . . . . . . 5

Customer Discount Sequence # . . . . 6

Coupon Item Sequence # . . . . . . . 7

Price Table Sequence # . . . . . . .

End of Order Pricing Options:

Item Volume Discount . . . . . . . . Y (Y/N)

Quantity Break/Item . . . . . . . . Y (Y/N)

Price Codes . . . . . . . . . . . . (Y/N)

Price Tables . . . . . . . . . . . . (Y/N)

Application Code . . PRI

Application Group. . O/E

F3=Exit F12=Cancel

Overview: You can define two basic types of pricing: line-level pricing, and order-level pricing.

Line-level pricing method: A line-level price is determined as each item is added to the order. Seven line-level pricing methods are available:

Offer Price Sequence # (A79)

Quantity Break by SKU Sequence # (A80)

Column Sequence # (A81)

Special by Source Sequence # (A82)

Contract Sequence # (A83)

Customer Discount Sequence # (A84)

Coupon Item Sequence # (A85)

Price Table Sequence # (E06) (see also end of order pricing, below)

Each pricing method is described briefly below.

Procedure: Enter a number from 1-8 (1= first, 8 = last) next to each pricing method that you use to define the order in which the system should search for a price for an item.

Leave blank any pricing methods you do not wish to use.

The value in the Best Way Pricing (A78) field controls whether the system searches for the best price or stops at the first price it finds in the pricing sequence.

Y = the system searches for the best price

N = the system stops at the first price it finds

End-of-order pricing options: An end-of-order price is applied after line-level pricing when you accept an order in Order Entry. You can display end-of-order prices in Order Entry by pressing F21. The following methods are available:

Item Volume Discount (B29)

Quantity Break/Item (A87)

Price Codes (D93)

Price Tables (E07)

You define order level pricing by typing Y next to the methods you want to use. You cannot have both Quantity Break/Item (A87) and Price Codes (D93) set to Y. If you have both Item Volume Discount (B29) and either Quantity Break/Item (A87) or Price Codes (D93) set to Y, the latter pricing method takes precedence over Item volume discount.

The source code pricing method must be set to D in order for the order-level pricing methods to be considered. See Marketing Chapter 6: Working with Source Codes (WSRC).

Pricing Logic Overview

The system uses the following steps to determine the price of an order detail line.

1. Check the Pricing method defined for the source code on the order header (See Marketing Chapter 6: Working with Source Codes (WSRC)):

Source Code Pricing Method

Procedure

C

Use item cost (go to step 6)

N

No charge (no further pricing; post the cost of inventory)

O

No charge/no cost (no further pricing; do not post the cost of inventory)

P

Use price hierarchy (go to step 2)

D

Use price hierarchy plus reprice (go to step 2)

2. Determine the line price using one of the pricing methods defined in the System Control file. Use best price if Best Way Pricing (A78) = Y, or follows the sequence specified. If the source code Pricing method = D, continue to step 3. If source code Pricing method = P, skip to step 4.

3. Reprice based on quantity by item if Quantity Break/Item (A87) = Y and source code Pricing method = D. Reprice based on price codes if Price codes = Y and source code Pricing method = D. Reprice based on price table if Price Tables (E07) = Y.

4. Apply any discount defined for the source code to all lines that have been repriced by the system and are flagged as Discountable = Y in the Item file.

5. Apply any discount defined on the order header to all lines that have been repriced by the system and are flagged as Discountable = Y in the Item file.

6. When F21 is pressed, reprice based on price table if Price tables = Y. Prorate dollar discount across the order lines if the Prorate Dollar Discounts and Coupons (D90) system control value is set to Y. If F21 is not pressed, perform these steps when F9 is pressed.

7. After the order is accepted (by pressing F9), apply any dollar discount as an additional charge if applicable, and if the Prorate Dollar Discounts and Coupons (D90) system control value is set to = N. Additionally, perform the steps described in step 6.

Best Way Pricing (A78)

The Best Way Pricing value indicates whether, when an item points to a source code that uses a pricing method of P (Regular Hierarchy), the system searches through the pricing hierarchy to calculate and assign the lowest price to the item.

When the Best Way Pricing feature is Y, each pricing method in the pricing hierarchy is evaluated and the best price is applied to the item.

Note: If this feature is set to Y, the customer always receives the best available price for the item and quantity. If the best available price is a column price, the customer receives this price even if not flagged for column pricing.

When the Best Way Pricing feature is N and the source code points to a pricing method of P (Regular Hierarchy), the system follows the sequence defined for the pricing hierarchy and stops at the first price found (no matter what the method). This price is applied to the item.

Search Active Offers for Price (F95)

Enter Y in this field or leave this field blank if you want the system to search through active offers for a valid offer price when you add an item to an order.

Alternate currency pricing: If you use alternate currency pricing (the Use Alternate Currency Pricing (H89) system control value is set to Y), the system searches for an item/SKU price only among offers in the same currency. If the item is not available in an offer in that currency, the system displays a message: Price (.00) cannot be zero for item. See Customer Service Chapter 12: Using Alternate Currency Pricing for an overview and required setup.

Enter N if you do not want the system to search through active offers for a valid offer price when you add an item to an order.

The system checks the offer on the order detail line for a price; if the system cannot find a price for the offer on the order detail line, the system does not search other offers for a price. You should set this system control value to N if you do not use offer pricing. See Merchandising Chapter 27: Assigning Items/SKUs to Offers.

Offer Price Sequence # (A79)

The offer price pricing method uses the price defined for the item in the Item/Offer or SKU/Offer record. If there are multiple effective dates for the same item/offer, the system uses the price associated with the most recent effective date that is not later than the order date.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Quantity Break by SKU Sequence # (A80)

The quantity break/SKU pricing method uses the prices defined for the item/SKU in the Quantity Break table established at the Item/Offer or SKU/Offer record. This table defines effective dates, quantities and prices for the item. The Order Entry operator can access the Quantity Break Price Table to inform the customer of the special prices established for this item, depending on order volume. If there are multiple effective dates for the same offer/ SKU/quantity, the system uses the price associated with the most recent effective date that is not later than the order date. See Merchandising Chapter 27: Assigning Items/SKUs to Offers.

The customer must order the required quantity of the same SKU to be eligible for this pricing method.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Column Sequence # (A81)

The column price pricing method uses the price defined for the item, based on the Column Pricing defined at the Item/Offer or SKU/Offer level and the column assignment defined for the customer. See Merchandising Chapter 27: Assigning Items/SKUs to Offers. When the Item/Offer or SKU/Offer uses Column Pricing, records can be established that define an effective date, quantity price, associate price, and column number. A customer can be assigned to a specific pricing column by entering a column number in the Pricing column field in the Customer record. The column price (such as “a quantity of 3 is sold at xxxx.xx”) is always given to the customer, regardless of the quantity ordered.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code for the order detail line uses a pricing method of P (Regular Hierarchy).

Special by Source Sequence # (A82)

The special pricing/source code pricing method uses the price defined in the Special Pricing by Source Code record for each source/item combination. See Marketing Chapter 6: Working with Source Codes (WSRC).

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Contract Sequence # (A83)

The contract price pricing method uses the special contract price defined for the customer in the Contract Pricing file. This record defines an item/SKU#, start and end dates, and a price for which this item may be purchased by this customer over the life of the contract. See Customer Service Chapter 31: Work with Contract Price Screen.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Customer Discount Sequence # (A84)

The customer discount pricing method uses the discount percentage established in the customer record and applies this discount to each item on the order.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Coupon Item Sequence # (A85)

The coupon/item pricing method subtracts the value in the Coupon discount $ field in the Item/Offer or SKU/Offer file from the item price. See Merchandising Chapter 27: Assigning Items/SKUs to Offers.

Define in this field the sequence in which the system should use this pricing method to price an item when the source code on the order detail line uses a pricing method of P (Regular Hierarchy).

Price Table Sequence # (E06)

The price table pricing method uses the item price in the price table defined in Price table field for the source code. See Marketing Chapter 6: Working with Source Codes (WSRC).

If an item price does not exist in the price table defined for the source code, or if there is no source code table defined, the system uses the price from the table defined in the Default Price Table (E04) system control value.

To use price table pricing, the pricing method for the source code must be set to D.

Price tables may also contain information for end of order pricing and premiums.

End of order pricing options:

Item Volume Discount (B29)

Enter Y in this field to have the system reprice an order by the Item Volume Discount method in Order Entry. Enter N if you do not wish to use this pricing method.

With this method, items are designated as eligible for a volume discount in the Item file (Discountable = Y); also, the Volume discount flag for the item/offer or SKU/offer must be set to Y. The system totals the number of volume-discountable units on the order to determine the quantity break.

Next, the system checks the Price Breaks file established at the Item/Offer or SKU/Offer level to retrieve a price for each item on the order, using the total quantity of volume-discountable units ordered.

Example: 4 items are ordered; however, only 3 of these items are eligible for the volume discount. The total number of volume discountable units ordered is 12 (6 units of one item, 2 units of another item, and 4 units of the third item). The system uses the quantity break price defined for 12 units (6+2+4) for each item on the order, including the non-discountable item.

Quantity Break/Item (A87)

Enter Y in this field to have the system reprice an order by the Quantity Break by Item method in Order Entry. This method totals the SKUs ordered for a base item and then checks the price break for that quantity in the Item Price file (Work with Item Prices Screen (Quantity Price Breaks by Offer)) to determine the price for each SKU. This method is useful if your items are heavily SKU’d. See Merchandising Chapter 27: Assigning Items/SKUs to Offers.

Note: If you order a SKU’d item, the system continues to look at the price break in the Item Price file; not the SKU Price file.

Enter N if you do not wish to use this pricing method.

The following is an example of a Quantity Break by Item for item A1 (a shirt)

• Quantity (1) - Price $8.00

• Quantity (5) - Price $6.50

• Quantity (10) - Price $5.00

If the customer orders 2 blue shirts and 3 green shirts, the price of each shirt is $6.50 because the system uses the quantity break defined for 5 units, as shown in the example above.

Price Codes (D93)

Enter Y in this field to have the system reprice items in Order Entry based on methods you define in the Price Code file. Enter N if you are not using price codes. See Marketing Chapter 19: Working with Price Codes (WPCD).

You can use price codes to define a dollar discount, discount percent, or new item price, then assign price codes to items by either source code or offer. To qualify toward the minimum quantity, items must share a price code and be shipping to the same address.

You cannot have both Quantity Break/Item (A87) and Price codes set to Y.

Promotional Pricing does not work with any order level pricing methods except for Price Codes. If the pricing method uses Promotional Pricing, these other end of order pricing methods are ignored.

Price Tables (E07)

Enter Y in this field to have the system reprice items in Order Entry or Order Maintenance based on methods you define in the Price Table file. Price tables take precedence over other end-of-order pricing methods. Enter N if you are not using price tables. See Marketing Chapter 21: Working with Price Tables (WPTB).

Price tables allow you to define price breaks for items or groups of items based on quantity or total dollars ordered. You can also specify free or reduced-price premium items to offer on qualifying orders. When you press F21 or F9, the system checks the price table defined in the source code, if any, for the item price, based on the total order of the item or group. If the order qualifies for one or more premiums, the Display Premium screen displays; you use this screen to select or deselect earned premiums according to the customer's preference. If there is no record of the item in the price table defined for the source code, or if there is no price table associated with the source code, the system checks the Default Price Table (E04) system control value.

Price table repricing and, in some cases, premium items may also apply in Order Maintenance as long as you have not printed a pick slip for any items on the order. This is the only end-of-order repricing method that functions in Order Maintenance.

If you use price table pricing, you can also specify a maximum price break to offer for certain items, but give your Order Entry operators the option of overriding that maximum in certain cases. See Price Table Level Override Code (E05).

Entity-Level Overrides to Company-Wide Pricing Defaults

You can set up pricing value overrides for any entity that should use different pricing logic from your company-wide standard. In order entry, the system checks the entity associated with the source code on the order header to determine if entity-level pricing overrides are in effect.

See Accounts Payable Chapter 1: Working with Entities (WENT) for more information.

Default Price Override Reason (B35)

Purpose: Use this screen to define the price override reason code to default in Order Entry/Maintenance when entering free gifts, telemarketing specials, accompanying items, exchange lines at no charge, or package insert items.

MSR0051 CHANGE Change System Control Value 11/09/99 11:08:17

Description . : Default price override reason

Code . . . . . A A B D G

M X Z 1

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code that represents the price override reason to default during Order Entry/Maintenance when a free gift, accompanying item line, telemarketing special, exchange line at no charge, or package insert item is added to an order.

When the system adds a line to the order automatically at “no charge” as the result of a free gift, for example, the system uses the price override reason code defined here. for the order detail line.

This code must be established in the Price Reason Code File. See Customer Service Chapter 2: Establishing Price Override Reason Codes (WPOR).

E-Commerce and order API orders: The system uses the price override reason defined in this system control value on e-commerce and order API orders if a price override reason has not been defined in the order message or in the Price Override Reason for E-Commerce (G73) system control value. Additionally, if the system uses the price override reason in this system control value, the e-commerce order response message does not contain details. See E-Commerce Order Creation and the Price Override Reason for E-Commerce (G73) system control value for more information.

If you leave this field blank, the system does not add a line to the order automatically when a price override reason is required.

Price override secured feature: If a user without authority to override price under the Price Overrides (A23) secured feature enters an item that is specified as a free gift for the source or offer associated with the order, and the user enters the default price override reason code, the system adds the item to the order at the price override amount entered.

Price override limit: If you use the price override reason code defined in the Default Price Override Reason (B35) system control value to enter a price override, the system allows you to exceed the price override limit defined in the Price Override Limit Percent (E55) system control value, regardless of your authority to the Price Overrides (A23) and Override Price Override Limit (A64) secured features.

Backorder Free Gifts (B48)

Purpose: Use this screen to define whether you wish to be able to place items that are designated as free gifts on backorder.

MSR0052 CHANGE Change System Control Value 11/09/99 11:09:37

Description . : Backorder Free Gifts

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field and the item designated as a free gift is not available, the item is added to the order with a backorder status.

If you enter N and the item designated as a free gift is not available, the free gift is not added to the order.

If you leave this field blank, this field defaults to Y.

Price Override Code for Promotional Priced Lines (B61)

This system control value is not currently implemented. The price override code that defaults in order entry for promotional priced lines is defined in system control value Default Price Override Reason (B35).

E-Commerce orders: If the price override reason defined on an e-commerce order matches the price override reason defined in this system control value, the e-commerce order response message does not contain details. See E-Commerce Order Creation.

CODE-1 From Group 1 Values (B68)

Purpose: Use this screen to define the system control values for using the CODE-1 address verification system, which performs address verification interactively during order entry, order maintenance, the generic customer API, and customer entry/maintenance.

MSR0476 ENTER Edit CODE-1 From Group 1 Values 2/28/05 16:59:56

EZK Mail Order

Use CODE-1 Coding System . . N (Y=Yes, N=No)

Street Name Matching Algorithm L (T=Tight, M=Medium, L=Loose)

Address Match Threshold . . 1 (1=High .... 9=Low)

Data Library . . . . . . . . TPSCLT_QAS

Program Library . . . . . . TPSSRV_QAS

Perform in Customer API . . Y (Y/N)

F3=Exit F12=Cancel

Overview: The CODE-1 Name/Address Coding System allows you to access Group 1 Software's name and address verification database using CWDirect. The CODE-1 database is a comprehensive address database that contains every deliverable ZIP+4 address range recorded by the United State Postal Service.

This interface prevents you from shipping to fraudulent customers who have given an incorrect address or company name. Address verification also improves the deliverability of your mail by providing the U.S. Postal Service with a more accurate and deliverable address.

QAS address interface: You can also perform address standardization using the QAS address interface; see Using the QAS Address Interface for more information on the QAS address interface.

What it does: The CODE-1 interface compares a customer's sold to, bill to and ship to addresses entered during order entry with addresses in the CODE-1 database. If there is a probable match in all name and address information on the order, based on the matching logic values set up in the System Control file, the Order Entry Header screen displays and you can continue placing the order. If there is not a probable exact match, the CODE-1 Address Verification pop-up window displays and you can either accept the new address information returned from CODE-1 or retain the original address information.

Note:

• The system submits customer addresses to CODE-1 or QAS as part of the Generic Customer API only if the Perform Address Standardization in Customer API (I99) system control value is set to Y and you are using either CODE-1 or QAS.

• See the CODE-1 Plus User's Guide for more information on the CODE-1 Address Verification product.

Using CODE-1 in Order Entry: The CODE-1 Plus Interface validates address information in order entry when you press Enter on the:

• Work with Order screen

• Customer Ship to screen

• Order Ship To screen

• Customer Bill To screen

At this time, the customer's address is compared with CODE-1's database. If there is a probable match in all name and address information on the order (based on the matching logic values set up in the System Control file), you can continue entering the order. If there is not a probable match, the CODE-1 Address Verification pop-up window displays. You can either accept the new address information returned from CODE-1 or override the CODE-1 data with the original address.

CODE-1 Address Verification window: This window displays the original customer name and address and the address information returned from the CODE-1 database.

CODE-1 Address

Name . . : MARC JOHNSON

Company . : LEX AUTOPARTS

Address . . 35 PLEASANT STREET PO Box? N (Y/N)

Apartment . 2

City/St/Zip HOLLISTON MA 01746

Delivery . R (B=Business, R=Residential)

-----------------------------------------------------------------

RESULTS FROM CODE-1 ===>

Address . : 35 PLEASANT ST PO Box? N (Y/N)

Apartment : # 2

City . . : HOLLISTON MA 01746-2606

Delivery : R (B=Business, R=Residential)

F6=Search CODE-1 F7=Use CODE-1 Address F8=Use Entered Address

Options:

• Press F6 to search for the correct city, state, postal code or street information in the CODE-1 database. See the CODE-1 Plus User's Guide for more information. Note: CODE-1 generates an internal error if you press F6 more than once.

• Press F7 to update the address and customer record with the address information returned form CODE-1.

• Press F8 to use the address you entered.

Use CODE-1 Coding System (B24)

Enter Y if you are using the CODE-1 address verification system. If you use CODE-1, address information is evaluated to ensure addresses entered in order entry are valid and deliverable addresses.

CODE-1 is software that you must purchase separately.

Using CODE-1: CODE-1 compares the sold to, bill to and ship to street addresses against valid addresses in the CODE-1 database.

If CODE-1 finds a match in the address information on the order (based on the values defined for the control values, Street Name Matching Algorithm (B25) and Address Match Threshold (B26)) you can continue placing the order.

If CODE-1 does not find a match, the system displays the CODE-1 Address Verification pop-up window. This window displays the sold to, bill to or ship to addresses as they were entered and the address that CODE-1 selected. You can either accept the new address information returned from CODE-1 or retain the original address information. Validations are performed against all residential and business addresses; no validations are performed against the customer's name.

CODE-1 also checks the 5 digit postal code and inserts the ZIP+4 code in the Postal code field. If the address is a company, it inserts the B (business code) in the Delivery field.

Street Name Matching Algorithm (B25)

Enter the level of address verification to perform interactively in order entry, order maintenance, customer API, or customer entry/maintenance against the CODE-1 database. Valid codes include:

T CODE-1 searches for a tight match and only displays a very close match to the address entered, after failing to find an equal match.

M CODE-1 searches for a medium match until it can display an address that is a close match to the address entered, after failing to find an equal match.

L CODE-1 searches for a loose match until it can display a best guess match to the address entered, after failing to find an equal match.

This field is required if you entered a Y in the Use CODE-1 Coding System (B24) system control value.

Address Match Threshold (B26)

Enter the number (1 - 9, 1 = very close, 9 = not close) that represents the degree of 'closeness' that CODE-1 uses to match an entered address. This number determines whether CODE-1 accepts the address without notification or displays the CODE-1 Address window.

• If CODE-1 returns a value that is less than or equal to the value defined here, the system accepts the modified address, without displaying the CODE-1 Address Verification pop-up window.

• If CODE-1 returns a value that is greater than the value defined here, the CODE-1 Address Verification pop-up window displays, allowing the operator to see the entered address and the CODE-1 address. The operator can either modify the entered address, use the CODE-1 address, or bypass the CODE-1 checking and use the originally entered address.

Address Verification Data Library (B66)

Enter the name of the library that contains the data objects used for the Address Verification interface. The data library supplied by Group 1 is G1C1FILES. You can obtain the name of the data library from the person who installed the CODE-1 interface.

Note: This system control value is also used by the QAS Address Verification interface; see QAS Address Interface Values (I66).

Address Verification Program Library (B67)

Enter the name of the library that contains the programs used for the Address Verification interface. The program library supplied by Group 1 is G1C1PGMS. You can obtain the name of the program library from the person who installed the CODE-1 interface.

Note: This system control value is also used by the QAS Address Verification interface; see QAS Address Interface Values (I66).

Perform Address Standardization in Customer API (I99)

Purpose: Use this value to indicate whether to use the Address Verification Interface when you receive an Add or Change request through the generic customer API.

Yes/No field: Enter Y in this field if you use an Address Verification Interface, and you would like to use the interface to verify customer addresses that you add or change through the Generic Customer API.

The address standardization occurs only if there is a single exact match; otherwise, the process does not change the customer’s address before proceeding with its regular edits.

About the customer API: Use the generic customer API to add, change, or delete customers based on XML messages from an external system. The CUSTOMR_IN process in Working with Integration Layer Processes (IJCT) processes customer API Add, Change, and Delete requests.

In the case of an Add request, the address standardization takes place before any duplicate checking.

Enter N in this field or leave it blank if you do not want to perform address verification through when creating or updating customers through the generic customer API. The system performs its standard validation when you process updates through the customer API.

Note: This system control value is also used by the QAS Address Verification interface; see QAS Address Interface Values (I66).

For more information: See the Generic Customer API.

Default Cash Pay Type (C07)

Purpose: Use this screen to define the payment type to default when applying a customer's refund/balance due write-off to an order.

MSR0054 CHANGE Change System Control Value 11/09/99 11:14:59

Description . : Default Cash Pay Type

Number . . . . 2 01 02 03 06

11 12 13 21

31 41 51 ...

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Number field: Enter the number that represents the payment type to add to the order payment methods when you apply a write-off amount as payment to the order.

When you apply the write-off amount as payment on the order by pressing F7 on the Enter Payment Method screen, the system uses the value in this field when adding a payment method to the order.

The payment method code you define in this field must exist in the Pay Types file. See Accounts Payable Chapter 5: Working with Pay Types (WPAY).

This action may be performed from the Enter Payment Methods screen in Order Entry. A value appears in the WO$ field when the customer has a positive refund due amount that has accumulated when the refund due on an order is less than the minimum required to cut a refund check for the customer.

Duplicate Item Check (C09)

Purpose: Use this screen to determine whether the system should notify the order entry operator if the customer places more than one order for the same item within a predefined period of time.

MSR0052 OPEN Change System Control Value 3/22/95 16:01:33

Description . : Duplicate Item Check

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group :

Sequence# . . :

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to use the Duplicate Item Check feature. With this feature, the system checks the value in the Duplicate Item Days (C58) system control value. If an item appears in more than one order for the customer within the specified number of days, the system displays a pop-up window. This enables you to notify the customer of the duplicate item so that the customer can cancel the item from the new order, if necessary.

Add or cancel item: Press Enter if the customer still wants to add the item to the order; otherwise, press F12 to return to the item entry field to remove the item code.

Duplicate Item for Cust window: This window displays during interactive order entry if an item appears in more than one order for the customer within the specified number of days.

Duplicate Item for Cust

 

Item: Belt

 

Warning! The item/SKU being ordered is a duplicate for the current customer placed within the last 1 days.

 

Press Enter to continue or F12 to cancel.

 

F12=Cancel

Orders processed through the phone order interface, e-commerce, and order API: If an item appears in more than one order for the customer within the specified number of days and the Hold Reason for Duplicate Items Found in Processing Remote Orders (J51) system control value specifies a valid hold reason code, the system places the order on hold using that hold reason. See that system control value for a discussion. C

Enter N if not using this feature. The system does not evaluate the customer's orders for duplicate items.

Default Version for Order Inquiry (C34)

Purpose: Use this screen to define the format of the initial screen to display when you access Order Inquiry.

MSR0051 CHANGE Change System Control Value 11/09/99 11:19:54

Description . : Default version for Order Inquiry

Code . . . . . HEADER HEADER HEADER/DTL

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: You can enter HEADER or HEADER/DTL as the default.

If you define HEADER as the default version, the initial screen in Order Inquiry is the Order Header Information screen (where you can review name, address, and order information). The next screen to display is the Detail Line Information screen (where you can review item information).

If you define HEADER/DTL as the default version, the initial screen in Order Inquiry is a single, combination screen. The top half of this screen presents name and address information; the lower half of this screen presents one line for the review of detail line information.

If you leave this field blank, this field defaults to HEADER.

For more information: See Order Entry Chapter 1: Introducing Order Entry for information on the differences between HEADER and HEADER/DETAIL formats.

Sample Header screen: Below is a sample of the screen that will display in Order Inquiry if you define HEADER as the default.

OER0194 DISPLAY Order Inquiry 10/15/97 8:51:07

The KL Mail Order Company

+--------------+

Order . : 1482 - 001 Date: 10/14/97 | Refunds: N |

Status : Open Type: P Pay Type: 1 | Msgs : N |

Hold Rsn : Ship via: 1 | Recips : 1 |

Sold To : 12682 Ship To +--------------+

HILLARD, JOSEPH P HILLARD, JOSEPH P

PORTSWITH FACTORY PORTSWITH FACTORY

7798 MAIN STREET FLOOR 4 7798 MAIN STREET FLOOR 4

FRAMINGHAM, MA 01746 USA FRAMINGHAM, MA 01746 USA

Phone: Day: Phone: Day:

Eve: Eve:

Merch : 20.00 Freight : 2.00 Add'l freight : .00

Tax . . : 1.00 Handling: .00 Add'l charges : .00

Total . . . . : 23.00 Total Cash Paid : 23.00

Balance Open . : 23.00 Total Coupon Paid: .00

Ref/Balance Due: .00 Cash Refunded : .00

Discount . . . : .00 Coupon Refunded : .00

F2=Scan lines F3=Exit F6=Detail F7=Maint order F8=Sold to F9=Ship to

F11=Bill to F14=Invoices F15=Payments F16=Charges F24=More keys

Sample Detail screen: Below is a sample of a Detail screen that will display in Order Inquiry if you define HEADER/DTL as the default.

OER0115 DISPLAY Order Inquiry 12/03/97 9:04:45

EZK Mail Order

Order# . . : 4217 - 001 Status: Open Order date: 11/25/97

Sold To (+): 294 BROWN, HANNAH E Whse: 0

Ship To (+): BROWN, HANNAH E State: MA

Merch: 399.50 Freight : 39.95 Add'l freight: .00

Tax : .00 Handling: .00 Add'l charges: .00

Type options, press Enter. Total : 439.45

5=Details 6=G/C 8=S/H 9=Reserved lines 23=Msgs 24=History 99=Letter

Opt Ln# S Item# CLR SIZE WDTH H Ord Rsv Shp Prt Price

1 MATHLAND 10 10 10 39.95

MATH CD FOR KIDS 10-14 399.50

F2=Scan lines F3=Exit F6=Header F7=Maint ord F8=Call tag F9=Ship to

F11=Bill to F14=Invoices F15=Payments F16=Charges F24=More keys

Default Additional Charge Code (C45)

Purpose: Use this screen to define the default additional charge code used when the system applies a balance due write-off as an additional charge on the order during Order Entry.

MSR0051 OPEN Change System Control Value 5/19/94 9:47:17

Description . : Default Additional Charge Code

Code . . . . . D D G H P

R

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 2

F3=Exit F12=Cancel

Code field: Enter the code that to use in Order Entry when applying a balance due write-off amount as an additional charge to the order.

A balance due write-off exists when a negative value displays in the WO$ field in the upper right of the Payment Method screen. This indicates that the customer has underpaid on previous orders by a dollar value or percentage; although the customer is shipped the order, the balance due write-off amount accumulates in the Customer record.

You can add the balance due write-off to an order during Order Entry by pressing F8 on the Payment Method screen. The system applies the entire amount of the balance due write-off as an additional charge on the order. The additional charge is added to the Additional Charges screen, using the value in the Default additional charge code field in the System Control file.

Returns: When you return an order, including additional charges, the system:

• searches the Order Additional Charge file (by matching on invoice number and charge amount) for the additional charge code originally assigned to the order. Once the original additional charge code is found, the system posts the amount to the general ledger number defined for the code in the Additional Charge Code file.

• If the system does not find the original additional charge code on the order, the system uses the account number specified for the Default Additional Charge Code (C45) system control value.

• If this system control value is blank, the system uses the account number specified for the Additional charges returns for the division.

Additional Charge codes are defined in and validated against the Additional Charges file. See Customer Service Chapter 3: Establishing Additional Charge Codes (WADC).

Use Default Current Source Code (C46)

Purpose: Use this screen to control whether the current source code for an existing customer defaults when you enter a new order for the customer.

MSR0052 OPEN Change System Control Value 5/19/94 10:02:09

Description . : Use Default Current Source Code

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 2

F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system loads the value from the Current source field for an existing sold-to customer automatically to the Source field during Order Entry. You may, however, override this default.

If you enter N or leave this field blank, the Source field on the Order Entry header screen is blank for both new and existing customers.

If both this field and the Load Order Header Source from Mailing History (F05) field are set to Y, the most recent source code from the customer's mailing history, if any, defaults. See the description of this field later in this chapter for more information.

Duplicate Item Days (C58)

Purpose: Use this screen to define the number of days during which the system checks the customer's orders for duplicate items.

MSR0054 OPEN Change System Control Value 3/28/95 16:17:04

Description . : Duplicate Item Days

Number . . . .

Narrative . . .

Application . : O/E

Applic group :

Sequence# . . :

F3=Exit F12=Cancel

Number field: Enter the number of days through which the system should check a customer's orders for duplicate items. The system displays a pop-up window if the customer previously ordered the same item within the specified period. This gives the operator a chance to notify the customer in case the customer wants to cancel the item from the new order.

This field is required if you entered Y at the Duplicate Item Check (C09) system control value. See that system control value for a discussion.

Maximum Order Quantity (C60)

Purpose: Use this screen to define the maximum number of units that you can enter on an order detail line.

MSR0054 OPEN Change System Control Value 3/24/95 15:12:48

Description . : Maximum Order Quantity

Number . . . .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Number field: Enter the maximum item quantity you can enter on a single order detail line in order entry or order maintenance. This validation can help you prevent inaccurate order line quantities due to user error (for example, entering 100 rather than 10).

The Allow Maximum Order Quantity Override (A70) secured feature controls the ability to exceed this maximum. If you have the proper authority, a pop-up window displays informing you that the order line you have just entered exceeds the maximum; you can press F9 to add the line to the order. If you press F3, F12 or Enter, an error message such as the following displays:

 

Order Qty of 10 exceeds the maximum allowed in SCV C60.

 

If you do not have proper authority, no pop-up window displays when the order line exceeds the maximum quantity. Instead, the error message displays.

Leave this field blank if you do not want the system to perform a check against the order line quantity.

The system checks the quantity on an individual order line basis, not an order-level basis. In other words, no check takes place to prevent the total unit quantity on the order from exceeding this maximum.

Order Purge Days (C62)

Purpose: Use this screen to define the number of days from the last transaction date that a closed or canceled order is eligible for deletion through the Order Purge program.

MSR0054 OPEN Change System Control Value 3/17/95 9:44:13

Description . : Order Purge Days

Number . . . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Number field: Enter the number of days from the last transaction date on a closed (shipped) or canceled order after which the order is eligible for deletion.

The system checks the Order Transaction History file for the last transaction date, which may be the date the order was canceled or the last shipment on the order occurred. The system adds the order purge days to the last transaction date to determine when the order can be purged. See Customer Service Chapter 61: Display Order History Screen.

For example, the order was canceled on 3/01/94 and the value in the Order purge days field is 120 (approximately 4 months). Therefore, the order is eligible for purging on 6/29/94.

See System Operations Chapter 60: Purging Orders (MPOR, FORP, VORP, DORP) for more information on purging orders.

Update Demand for Order Maintenance Transactions (C72)

Purpose: Use this screen to define whether the system should adjust demand for items added or canceled on an order through Order Maintenance.

MSR0052 OPEN Change System Control Value 3/17/95 10:19:48

Description . : Update Demand for Order Maintenance Transactions

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to update the customer's demand history (in the Orders buckets) for items you add or quantities you increase in order maintenance. With this setting, demand is adjusted to reflect current order activity.

Enter N in this field to capture demand only through Order Entry. The number and dollar value of items ordered are not adjusted as a result of Order Maintenance activity. With this setting, true demand is captured (and retained) for orders.

Updates to the total number of orders: If you have entered Y in this field, each time you add a line to an order in order maintenance, the system considers it an “order occurrence,” and the number of orders, as well as the dollar value of orders, increases for the offer and source code of the order line, as tracked in the Source file (MSSRC) reported in the Source Code Analysis Report (RSCA) and the Source Analysis Recap Report (RSCA). However, when you cancel a line from an order, the dollar value of orders decreases if the cancel reason reduces demand, but the number of orders decreases only if the cancelled line was the last remaining open line on the order.

Example: Adding a line to an order: C72 = Y; source code = SUMMER

$ Orders = 5000.00

# Orders = 25

In order maintenance, you maintain an order for the SUMMER source by adding a line for an item which is priced at $100.00. The system considers this an order occurrence, so increases the number of orders as well as the dollar value of orders. The new totals are:

$ Orders = 5100.00

# Orders = 26

In order maintenance, you cancel the added line, using a cancel reason which reduces demand. The $ Orders decreases, but the # Orders does not, because the cancelled line was not the last remaining open line on the order. The new totals are:

$ Orders = 5000.00

# Orders = 26

 

Example: Changing the source code on a line: C72 = Y; source code = SUMMER; system control value Default Offer Source Code to Order Detail Line (G28) = Y.

Related system control value: Default Offer Source Code to Order Detail Line (G28) determines whether the system updates the source associated with the offer you enter on a detail line if you override the order offer for a detail line, and the detail line’s offer is not associated with the source code of the order.

$ Orders = 5000.00

# Orders = 25

In order maintenance, you maintain an order for the SUMMER source by adding a line for an item which is priced at $100.00. However, you enter an offer for the detail line which is associated with source code FALL, not SUMMER. No increase takes place to the $ Orders and # Orders for the source SUMMER. The new totals are unchanged:

$ Orders = 5000.00

# Orders = 25

In order maintenance, you then maintain an order for the SUMMER source by changing an order line for an item priced at $100 to an offer associated with the FALL source code. The $ Orders value decreases, but the # Orders does not decrease, unless the line is the last remaining open line on the order. The new totals are:

$ Orders = 4900.00

# Orders = 25

In order maintenance, you then maintain the order by changing the order line associated with the FALL source to an offer associated with the SUMMER source. The system considers this an order occurrence, and updates the number of orders, as well as the dollar value of orders, for the SUMMER source:

$ Orders = 5000.00

# Orders = 26

 

Example: Changing the quantity of a line: C72 = Y; source code = SUMMER

$ Orders = 5000.00

# Orders = 26

In order maintenance, you maintain an order for the SUMMER source code by increasing the quantity of an order line from quantity = 1 to quantity = 2. The item is priced at $100.00. The system does not consider this an order occurrence because you have not added a line to the order. Dollar value of orders increases, but number of orders does not:

$ Orders = 5100.00

# Orders = 26

In order maintenance, you then maintain the order by decreasing the quantity of the order line from quantity = 2 to quantity = 1. No change occurs in the dollar value or orders; the system treats decreases in quantity the same way it treats cancellations which are set with Reduce demand = N; demand is not reduced for either the number of orders or the dollar value of orders:

$ Orders = 5100.00

# Orders = 26

 

Example: Changing the price of an item: C72 = Y; source code = SUMMER

$ Orders = 5100.00

# Orders = 26

In order maintenance, you maintain an order for the SUMMER source code by changing the price of an item (quantity = 1) from $100.00 to $150.00. The system does not consider this an order occurrence. Dollar value of orders increases, but number of orders does not. The new totals are:

$ Orders = 5150.00

# Orders = 26

Additional updates to the Source file (MSSRC): This system control value also determines whether order maintenance transactions affects the cancellation and return information captured in the Source file (MSSRC).

Cancels: If you have entered Y in this field, and you cancel an item, the dollar value and number of cancellations are affected only if you use a cancel reason code which does not reduce demand. Each time you perform a cancellation which does not reduce demand, whether for a single line (complete or partial quantity - partial lines are cancelled by changing the order quantity), or for an entire, multi-line order, the system considers this a “cancellation occurrence” and increases the number of cancellations as well as the dollar value of cancellations. If you use a cancel reason code which reduces demand, the dollar value of orders decreases, but the cancellation figures do not change. See the examples below.

Returns: If you have entered Y in this field, and you return an item (partial or complete line) using the Work with Return Authorizations (WRTA) menu option or through order maintenance, either by using the return option or by entering a negative quantity in order entry, the dollar value and number of returns increase; dollar value and number of orders do not change. Each time you perform a return, whether for an entire order or for a single line (partial or complete quantity), the system considers this a “return occurrence” and increases the number of returns as well as the dollar value of returns. See the examples below.

Cancelling a line and reducing demand: C72 = Y; Reduce demand? on cancel reason code = Y

$ Orders = 5000.00

# Orders = 25

$ Cancels = 500.00

# Cancels = 5

In order maintenance, you cancel one line (priced at $100) of an order, using a cancel reason code with the Reduce demand? code set to Y. The dollar value for orders is decreased. This is the only field affected when you reduce demand for a cancellation; the number of orders is not decreased, even if the cancelled line is the only line on an order, and the number of cancellations and dollar value of cancellations is not changed. The new totals are:

$ Orders = 4900.00

# Orders = 25

$ Cancels = 500.00

# Cancels = 5

 

Example: Cancelling a line but not reducing demand: C72 = Y; Reduce demand? on cancel reason code = N

$ Orders = 5000.00

# Orders = 25

$ Cancels = 500.00

# Cancels = 5

In order maintenance, you cancel one line (priced at $100) of an order, using a cancel reason code with the Reduce demand? code set to N. The dollar value for cancellations is increased, and the number of cancellations is increased. The dollar value for orders and the number of orders is unchanged, even if the cancelled line is the only line on an order. The new totals are:

$ Orders = 5000.00

# Orders = 25

$ Cancels = 600.00

# Cancels = 6

 

Example: Returning a partial quantity of a line: C72 = Y

$ Orders = 5000.00

# Orders = 25

$ Returns = 700.00

# Returns = 7

In order maintenance or Work with Return Authorizations, you receive and credit one unit of an item (priced at $100) for which two units were ordered and shipped. The system considers this a “return occurrence” and increases the number of returns, as well as the dollar value of the returns. The dollar value for orders and the number of orders is unchanged. The new totals are:

$ Orders = 5000.00

# Orders = 25

$ Returns = 800.00

# Returns = 8

 

Default Male/Female Profile Code (C74)

Purpose: Use this screen to identify the profile code for male or female, which load during Order Entry or when entering a request for a catalog.

MSR0054 OPEN Change System Control Value 3/22/95 14:34:24

Description . : Default Male/Female Profile Code

Number . . . .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Number field: Enter the profile number for gender (male or female). When you enter an order or catalog request for a new customer, the system:

• checks for a default characteristic for the male/female profile code

• loads the default value to the M/F (Male/Female) field

You can override the default code, if necessary.

Demographic profile codes and associated characteristics are defined in the Profile file. See Customer Service Chapter 16: Setting Up Customer Profiles (WPFL).

Although you are required to enter a value here, the M/F field on the Order Entry or Catalog Request screen are not loaded with a default value if you do not identify “Male” or “Female” as the default characteristic in the Profile Categories file.

Default Delivery Code for New Order Entry Customers (D13)

Purpose: Use this screen to define the delivery code the system defaults to new customers you enter on the system.

MSR0051 CHANGE Change System Control Value 6/25/98 10:33:04

Description . : Default Delivery Code for new Order Entry Customers

Code . . . . . B R N

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 100

F3=Exit F12=Cancel

Code field: Enter the code you want the system to default to the customer's shipping address. The delivery code controls which rate table the system uses to calculate shipping charges for shippers such as UPS. This value defaults when you create new customers in Order or Entry or through Work with Customers.

Valid values are:

B = Business: packages are shipped to a company

R = Residence: packages are shipped to the customer's home

N = No distinction between business and residence (this is not a valid value for UPS. shippers, as defined in the Ship Via file)

blank = No value defaults to the Delivery field on the Order Entry screen; the operator is required to enter a valid value in this field when creating a new customer.

The system uses the following logic to default a delivery code to a customer address:

• The system defaults the delivery code defined for the postal code on the address. See Customer Service Chapter 15: Setting Up the Postal Code File (WZIP).

• If a delivery code has not been defined for the postal code on the address, the system defaults the delivery code defined in the Customer file. See Customer Service Creating and Updating Sold-to Customers (WCST).

• If there is no delivery code defined for the customer, the system defaults the delivery code defined in the Default Delivery Code for New Order Entry Customers system control value.

Default “Gift Order” Flag (D14)

Purpose: Use this screen to define the value that defaults in the Gift field during Order Entry.

MSR0052 OPEN Change System Control Value 3/27/95 8:58:28

Description . : Default "Gift Order" flag.

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to identify all orders as “gift” orders by default; otherwise, enter N. You can override the value in this field on an order-by-order basis.

If the majority of the orders you take are gift orders, you might set this value to Y to reduce required data entry for order entry operators.

Leave this field blank if no value should default to the Gift field during order entry. The Gift field is a required field during Order Entry.

Phone Numbers (D15)

Purpose: Use this screen to identify which pair of phone numbers should appear on screens that include only two of the three phone number fields.

MSR0051 OPEN Change System Control Value 3/27/95 9:06:51

Description . : Phone Numbers

Code . . . . . DAY/EVE DAY/FAX

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Code field: Enter the code describing the types of phone number fields that you want to display on screens that include only two numbers. Set this field to:

DAY/EVE to display the daytime and evening phone number fields.

DAY/FAX to display the daytime and third phone number fields. The third phone number is labeled:

Fax if the Third Phone Number Type (L53) system control value is set to FAX or is blank.

Mobile or Mbl if the Third Phone Number Type (L53) system control value is set to MOBILE.

Note: Regardless of the setting of the Third Phone Number Type (L53) system control value, there is only one additional phone number stored besides the daytime and evening numbers.

Which screens? This system control value affects the following screens:

Work with B2B Order Screen

Order Inquiry Scan Screen

Customer Selection Screen

Work with Order Screen

Work with Order/Detail Screen

Note: If needed, you can press F18 (expanded address) during Order Entry to enter the extra phone number.

Order Discount Percentage Limit (D16)

Purpose: Use this screen to define the maximum discount amount that can be applied to an order during Order Entry or Order Maintenance.

MSR0057 OPEN Change System Control Value 1/06/95 10:56:17

Description . : Order Discount Percentage Limit

Percentage . . 25.00

Narrative . . . Defines upper limit for Order Entry discount percent.

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Percentage field: Enter the highest discount amount that can be taken on the order during Order Entry or Order Maintenance. You may leave this field blank if any discount percentage can be applied to an order.

The system checks the value in this field when you type a discount amount in the Discount % field during Order Entry or Order Maintenance. If the discount you want to apply to the order is greater than this value, the system issues the following message:

Discount % (xxx.xx) is greater than allowable limit.

This is a numeric, 5-position field with a 2-place decimal.

Default Bank for Cash Posting from Order Entry (D17)

Purpose: Use this screen to define the code for the bank to which cash received from prepaid orders posts for deferred liability.

MSR0051 OPEN Change System Control Value 3/22/95 15:17:28

Description . : Default Bank for Cash Posting from Order Entry

Code . . . . .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Code field: Enter the code for the bank where the system automatically posts cash received from prepaid orders. The system posts cash to this bank only if the Deferred Liability Cash Post Method (C48) system control value contains the value ORDER. With this setting, the system posts cash to Cash Receipts on an order-by- order basis during Order Entry.

The value in this field is ignored if the Deferred Liability Cash Post Method (C48) system control value contains the value CASH RCPT.

Bank codes are defined in and validated against the Bank file. Valid values appear to the right of this field. See Accounts Payable Chapter 6: Working with Banks (WBNK).

Enter Offer After Item (D19)

Purpose: Use this screen to determine whether the offer code is entered before or after the base item code during Order Entry.

MSR0052 OPEN Change System Control Value 3/20/95 10:08:22

Description . : Enter Offer After Item

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to enter the offer code after the base item code during order entry. With this setting, the offer field (Ofr) appears to the right of the item field (Item), but before the SKU field(s) on the detail screen.

Item Ofr SIZE CLR STYL Qty Price N/C Ovr C/G S/H Exten

BELT RRB 1

 

Enter N in this field to enter the offer code before the base item and SKU codes during Order Entry. With this setting, the Ofr (offer) field appears to the left of the Item and SKU fields on the detail screen.

Ofr Item SIZE CLR STYL Qty Price N/C Ovr C/G S/H Exten

RRB BELT 1

If both this field and the Position Cursor on Offer Field in OE/OM (F91) field are set to Y, the cursor position defaults to the Offer field, which is blank; also, the Offer field is positioned after the Item field, as in the first sample presented above. Normally, you would set one of these system control values to N to make item entry easier.

Load Source from Mailing History (D20)

Purpose: Use this screen to define whether the source code from the most recent mailing to the customer should default to the order detail line.

MSR0052 OPEN Change System Control Value 2/22/95 15:31:55

Description . : Load Source From Mailing History

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/No field: If you enter Y, the system does the following when an Order Entry or Order Maintenance operator enters an offer on the order detail line:

• searches for the specified offer code in the customer's Mail History file (See Customer Service Chapter 34: Reviewing Customer History)

• loads the source code associated with the most current mail date to the order detail line.

If the Update Source Code from Mail History (J94) system control value is set to Y, the system updates the source code and offer on an order line based on the most recent customer mail history associated with the item on the order line. Note: If the Load Source from Mailing History (D20) and Update Source Code from Mail History (J94) system control values are both set to Y, the system uses Update Source Code from Mail History Logic When Using Item.

If the Use Source Code from Order Header When Creating Order Lines (D73) system control value is set to Y, the system overrides the header-level source code on the detail line if it finds one through this process.

If the Default Offer Source Code to Order Detail Line (G28) system control value is set to Y, the system defaults the source code defined for the offer on the order detail line to the Source code field on the order detail line if a source code in the customer's mail history is not associated with the offer on the order detail line.

Track demand: The presence of a source code on the order detail line causes the system to track demand for the source code by the order detail line rather than the entire order.

Example: An order with a merchandise total of $45.00:

Header source code = A123

Order line 1: source code = B123, merchandise = $10.00

Order line 2: no source code override, merchandise = $15.00

Order line 3: no source code override, merchandise = $20.00

The system would update the history for each source code as follows:

A123: # orders = 1, $ orders = $35.00

B123: # orders = 1, $ orders = $10.00

The system updates the # orders field only once for each unique source code on the order, and updates the $ orders field with the merchandise total for all lines with that source code.

However, the system updates the Current source field in the Sold To Customer file with the source code entered on the “header” (name and address) screen.

This method of tracking demand by the order line might be useful if, for instance, your customers frequently order items from more than one catalog at the same time.

Enter N or leave this field blank if you do not want the system to default the source code from the customer's mailing history to each order detail line.

You can override the source code on the order detail line even if a source code has defaulted from the mailing history or the order header. However, freight and pricing methods are controlled by the source code on the “header” screen. The source code on the order detail line is used only for demand tracking.

For more information: See Marketing Chapter 6: Working with Source Codes (WSRC) for more information on tracking demand for source codes. Also, see the descriptions of the Update Demand for Order Maintenance Transactions (C72), Override Offer on Order Detail Line (D49), Use Source Code from Order Header When Creating Order Lines (D73), and Update Source Code from Mail History (J94) system control values.

Maximum Order Amount for Fraud Checking (D24)

Purpose: Use this screen to define the order amount to cause a credit card order, shipping to an address other than the sold-to address, to be placed on hold if the order does not also meet the criteria for the Ship Via Priority for Ship To Mismatch (L71), and the # of Times Shipped to Same Address (D25) or the # of Days Since Last Order (D26) system control values.

These system control values can help you identify fraudulent credit card orders. The system tries to identify a credit card customer shipping to different addresses within a short period to time. The system places orders that fail this credit check on a SM Ship To Mismatch hold so that you can review the orders before shipping product.

MSR0056 OPEN Change System Control Value 4/21/95 10:48:03

Description . : Maximum Order Amount for Fraud Checking

Dollar amount .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Dollar amount field: Enter the dollar amount that will cause a credit card order with different ship-to and sold-to (billing) addresses to be placed on hold. This field is 12 positions with a 2-place decimal.

The system places an order on SM Ship To Mismatch hold if the following conditions are met:

• the order contains a Credit Card pay category payment method, and

• the ship to address on the order is different from the sold to address, and

• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and

• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and

• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).

Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when pressing F9 or F19 to accept a new order).

1.

The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address.

• If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing.

• If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold.

2.

The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value.

• If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check.

3.

The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value.

• If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check.

Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step.

4.

The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR # of Days Since Last Order (D26) system control values.

• If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually through the Release Held Orders function, if appropriate. See Performing the Release.

Dollar hold check: The system also checks all orders, regardless of the payment method, for a total dollar amount exceeding the Maximum Order Amount (A92) system control value. The system places orders exceeding this amount on a DH Dollar Hold. If a credit card order matches the criteria for both a DH Dollar Hold and a SM Ship To Mismatch hold, it goes on a dollar hold first. For this reason, you should specify a greater value for the catch-all Maximum Order Amount (A92) system control value than the Maximum Order Amount for Fraud Checking (D24).

Order transaction history: The system writes a message to the Order Transaction History file (F18 in Order Inquiry) if the system places the order on SM Ship To Mismatch hold.

Date Type Transaction Note Amount User

5/02/95 H Shipments (0) LT limit (150). PAUL_P

5/02/95 H Days (14) from DLO LT limit (100). PAUL_P

5/02/95 H SYS HLD---SHIP TO MISMATCH PAUL_P

The message indicates the number of times you shipped to the same address and the number of days since the customer's last order. This helps you determine the reason why the order was placed on hold and evaluate whether you can release the order from hold using the Release Held Orders function. See Performing the Release.

Example: Examples of this credit checking process. In each example, the order payment method is a credit card.

System Control Value

Setting

Maximum Order Amount for Fraud Checking (D24)

$250.00

Ship Via Priority for Ship To Mismatch (L71)

1

# of Times Shipped to Same Address (D25)

2

# of Days Since Last Order (D26)

5

Example

Result

#1: A new customer places an order for $300.00 and has the order shipped using a shipper whose priority is 1 to the customer's home (billing) address.

The order is not held because the ship-to address is the same as the sold-to (billing) address.

The order must be both a credit card order and shipped to a different address other than the sold-to customer’s address for the system to check any of the other Fraud Checking system control values.

#2: An existing customer places a gift order for $100.00 and has it shipped using a shipper whose priority is 1 to a friend’s address.

The order is not held because the order is less than $250.00. The order must be over $250.00 to be held. In this case, the remaining system control values are not evaluated.

The order is evaluated for Fraud Checking because it is shipping to a different address other than the sold-to (billing) address, has a credit card pay type, and the priority of the ship via on the order matches the Ship Via Priority for Ship To Mismatch (L71).

#3: A new customer places a credit card order for $300.00 and has it shipped using a shipper whose priority is 1 to a work address.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), the number of times shipped to same address is less than 2 times, and the number of days since last order is less than 5 days.

The order is held because it is being shipped to a different address other than the sold-to (billing) address, the order total is greater than $250.00, the priority of the ship via on the order matches the Ship Via Priority for Ship To Mismatch (L71), and the order fails both of the remaining two criteria (shipping address and days since last order).

#4: A new customer places a credit card order for $300.00 and has it shipped using a shipper whose priority is 2 to a work address.

The order is not held because the priority of the ship via on the order does not match the Ship Via Priority for Ship To Mismatch (L71). In this case, the remaining system control values are not evaluated.

The order is evaluated for Fraud Checking because it is shipping to a different address other than the sold-to (billing) address, has a credit card pay type, and the order total is greater than $250.00.

#5: An existing customer places a gift order for $300.00 and has it shipped using a shipper whose priority is 1. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days.

The order is held because this is the first time the customer has shipped to the address on the order (gift recipient's address).

#6: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days.

The order is held because this is the first time the customer has shipped to the address on the order (using F7 in Order Entry for a Customer Ship To address).

#7: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to a neighbor's address. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days.

The order is held because this is the first time the customer has shipped to the address on the order (using F14 in Order Entry for an Order Ship To address).

#8: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered twice before, always shipping to the office address. The last order was placed about 2 months ago.

The order is not held. Although the order total is greater than $250.00 and the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), previous orders have shipped to this address (using F7 for Customer Ship To address in Order Entry), and the customer's last order was more than 5 days ago.

#9: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, and has shipped to this address before, but in each instance the operator entered the address using F14. The last order was placed about 2 months ago.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than the required value of 5.

The order is held because this is the first time the address was entered using F7 (Customer Ship To), instead of F14 (Order Ship To). The Credit Check program determines the number of times previously shipped to this address is 0.

#10: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all shipping to the office address. All orders have been placed within the last week.

The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of days since the last order is less than 5 days. The number of times shipped to the same address is greater than 2 times.

The order is held because the customer ordered before the required number of days had passed.

#11: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all shipping to the office address. In all cases the operator has entered the address using F14 (Order Ship To). The last order was placed 1 month ago.

The order is not held. Although the order total is greater than $250.00 and the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), the number of times shipped to the same address is greater than 2 times (because each order was entered using F14), and the number of days since the last order is greater than 5 days.

Important: As shown above, the system tracks the ship-to address separately at an order and a customer level. Therefore, how the operator enters the order, either using F14 to create an order ship-to address or using F7 to create a customer ship-to address, affects when an order is placed on a ship to mismatch hold.

Leave the Maximum Order Amount for Fraud Checking (D24) field blank if you do not want to evaluate an order for Ship To Mismatch hold.

# of Times Shipped to Same Address (D25)

Purpose: Use this screen to define the minimum number of times a customer must ship to a recipient address for the order not to be placed on a ship to mismatch hold if it also exceeds the dollar amount specified in Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).

This credit check feature helps you identify fraudulent credit card orders. With the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), and the # of Times Shipped to Same Address (D25) system control values, you can identify a possible bad order (over the maximum order amount) because of a frequently changing ship to address.

MSR0054 OPEN Change System Control Value 5/04/95 14:28:33

Description . : # of Times Shipped to Same Address

Number . . . .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Number field: Enter the number of times you require a customer to ship to a recipient address (a ship-to address that is different than the sold-to address) for the order not to be placed on a Ship To Mismatch hold. This system control value is used in conjunction with the Maximum Order Amount for and Ship Via Priority for Ship To Mismatch (L71) system control values. This is a 7 position numeric field.

The system places an order on SM Ship To Mismatch hold if the following conditions are met:

• the order contains a Credit Card pay category payment method, and

• the ship to address on the order is different from the sold to address, and

• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and

• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and

• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).

Determining the number of shipments:

• For gift recipient orders (F2) and customer ship to orders (F7), the system checks the number of shipments in the Customer Shipment History file. The order is not held if the number of shipments in this file is greater than or equal to the number in this field.

• For orders where there is a one-time-only address (Order Ship To) entered using F14, the system compares the address with all other one-time shipping addresses in the Order Ship To Address file. The order is not held if the number of times the address information appears in this file is greater than or equal to the number in this field. The address must be an exact match to one in this file or the system considers the address a new one and places the order on hold.

Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when pressing F9 or F19 to accept a new order).

1.

The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address.

• If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing.

• If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold.

2.

The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value.

• If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check.

3.

The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value.

• If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check.

Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step.

4.

The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR # of Days Since Last Order (D26) system control values.

• If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually through the Release Held Orders function, if appropriate. See Performing the Release.

Examples: See the examples provided for the Maximum Order Amount for Fraud Checking (D24) system control value for a description of how the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), the # of Times Shipped to Same Address (D25), and the # of Days Since Last Order (D26) system control values work together.

Leave the # of Times Shipped to Same Address (D25) field blank if you do not want to hold orders because of the delivery address.

# of Days Since Last Order (D26)

Purpose: Use this screen to define the minimum number of days that must pass before a customer can place and ship an order to a recipient address and not have the order placed on a ship to mismatch hold if it also exceeds the dollar amount specified in Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).

MSR0054 OPEN Change System Control Value 5/04/95 15:02:24

Description . : # of Days Since Last Order

Number . . . .

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Number field: Enter the number of days that must pass before a customer can place another customer ship to, order ship to, or recipient/gift order, and not have a ship to mismatch hold placed on the order. This system control value is used in conjunction with the Maximum Order Amount for Fraud Checking (D24) and Ship Via Priority for Ship To Mismatch (L71) system control values. This is a 7 position numeric field.

The system places an order on SM Ship To Mismatch hold if the following conditions are met:

• the order contains a Credit Card pay category payment method, and

• the ship to address on the order is different from the sold to address, and

• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and

• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and

• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).

Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when pressing F9 or F19 to accept a new order).

1.

The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address.

• If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing.

• If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold.

2.

The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value.

• If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check.

3.

The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value.

• If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check.

Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step.

4.

The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR # of Days Since Last Order (D26) system control values.

• If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing.

• If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually through the Release Held Orders function, if appropriate. See Performing the Release.

Examples: See the examples provided for the Maximum Order Amount for Fraud Checking (D24) system control value for a description of how the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), the # of Times Shipped to Same Address (D25), and the # of Days Since Last Order (D26) system control values work together.

Leave the # of Days Since Last Order (D26) field blank if you do not want to hold orders because of the recency of the last order.

User-defined Field Prompting for Existing Customers (D33)

Purpose: Use this screen to define whether the system displays the User Fields screen automatically during Order Entry for existing customers if no information has been entered previously on this screen.

MSR0052 OPEN Change System Control Value 7/12/95 9:30:07

Description . : User Defined Field Prompting for Existing Customers

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to display the User Fields screen each time an existing customer places a new order if no information has been entered on this screen; otherwise, enter N. If you enter N, the User Fields screen appears only for new customers.

About User Fields screen: Use the User Fields screen to capture any type of additional information about a customer during order entry. You use the User Defined Fields menu option to create this screen and link it to the Customer Sold To file (CST). You can include any type of numeric, date, or text fields in the screen. See Customer Service Chapter 20: Setting Up User-Defined Fields (WUDF).

Customer class: The Customer Class for User Defined Field Prompting (G04) system control value also plays a role in determining when the User Fields screen appears in order entry.

User Defined Field Prompting in Order Entry set to:

Customer Class for User Defined Field Prompting set to:

Result

Y

a valid customer class

prompts for any new or existing customer in the class who has not yet provided the user-defined information

Y

blank

prompts for any new or existing customer, regardless of class, who has not yet provided the user-defined information

N or Blank

a valid customer class

prompts for a new customer in the class only if you assign the class before completing the header information and pressing Enter

Note: If the Default Customer Class in Order Entry (D63) system control value is set to this same customer class, each new customer you create is assigned to the class automatically, and you always advance to the prompt screen

N or Blank

blank

prompts for any new customer

You can use the Work with Expanded Address screen in order entry to assign a customer class. This screen is available from the order header by pressing F18.

For more information:

• Customer Service Chapter 17: Setting Up the Customer Class File (WCCL)

• Order Entry Chapter 1: Introducing Order Entry

 

Example: You can build a screen to obtain information for an in-house credit card application. This screen could contain entry fields for the customer's date of birth, mother's maiden name, social security number, and operator ID.

A sample User Fields screen is presented below.

CSR0553 DISPLAY Enter User Fields 7/12/95 10:32:07

CommercialWare

Customer# . : 27 SWEENEY, LEE E

Date of Birth 041462

Mom's Maiden Nm ORMOND

SSN# 0000000015451945

CSR or Opr Id LEH

F3=Exit F12=Cancel

Display Discount on Order Recap Screen (D38)

Purpose: Use this screen to define whether the Order discount field displays in order entry, order maintenance and order inquiry.

MSR0052 CHANGE Change System Control Value 2/26/98 15:46:00

Description . : Display Discount on Order Recap Screen

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Order discount field to display on the:

• Order Recap screen in order entry

• Enter Payment Method screen in order entry and order maintenance

• order header screen in order maintenance and order inquiry (the discount is not displayed in order inquiry if you are using the Header/Detail rather than the Header format version)

The Order discount field on the Order Recap screen in order entry and on the order header screen in order maintenance and order inquiry displays the total discount applied to the order for the sold to customer only.

The Order discount field on the Enter Payment Method screen in order entry and order maintenance displays the total discount applied to the order across all ship to customers.

Enter N or leave this field blank, if you do not want the Order discount field to display in order entry, order maintenance and order inquiry.

Override Offer on Order Detail Line (D49)

Purpose: Use this screen to define whether the system:

• changes the offer code for an item to the offer used for pricing the item, and

• tracks demand (number of orders and dollar value) for the item by the offer used for the item, not the order.

An order might include an item that is not available in the offer associated with the source code on the order. For example, a customer might provide you with the source code of your current catalog when placing an order, but order an item advertised in a previous catalog. When this happens, the system prices the item based on the most current offer where the item is available.

MSR0052 CHANGE Change System Control Value 11/06/95 10:37:55

Description . : Override offer on Order Detail Line

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: If you enter Y in this field, the system overrides the offer code for the item and attributes demand for the item to the most current offer where there is a price for the item. Even if you specify a different offer when you add the item to the order, the system overrides the offer to the one where it actually found the price.

Example

Result

Item AB100 was included in offer 001 for $10.00, but this offer has expired. The item is also included in current offer 002 for $12.00.

When you add the item to the order, the system prices the item at $12.00 and overrides the offer on the order detail line to 002. Even if you entered 001 in the Offer field when adding the item, the offer would still be overridden to 002 and no message would display in order entry or order maintenance.

Important: If you have this field set to Y, then the Override Offer/Page/Alias on Order Detail (E72) system control value needs to be set to N. The two options are not compatible, since the Override Offer on Order Detail Line (D49) involves tracking demand based on the offer that provides the price, and Override Offer/Page/Alias on Order Detail (E72) involves tracking demand based on alias. See the Override Offer/Page/Alias on Order Detail (E72) for more information.

If you enter N or leave this field blank, the offer code for the item defaults to the offer associated with the source code, and the system attributes all demand to that offer. However, if you enter a different offer code when you add the item to the order or the system overrides the offer for any reason, the override offer remains on the order detail line.

For more information: See Merchandising Chapter 27: Assigning Items/SKUs to Offers, and see the Override Offer/Page/Alias on Order Detail (E72) and Search Offers for Alias (J68) system control values for discussions of situations when the system overrides the offer on the order detail line.

Display Item Alias (D56)

Purpose: Use this screen to define whether an item alias, rather than the actual item code, displays in Order Entry, Order Maintenance, Order Inquiry, and Item Availability Inquiry when a customer orders by the alias.

MSR0052 CHANGE Change System Control Value 4/18/96 13:55:42

Description . : Display Item Alias

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the item alias to display in Order Entry, Order Maintenance, Order Inquiry, and Item Availability Inquiry when a customer orders by alias.

An alias is an alternate name for an item. You might use aliases to present the same item more than once within an offer, so that you can track the effect of different placement or presentation of an item on sales. An item can have only one “true” item code, which the system uses to maintain inventory. However, you can invent various aliases for an item for any offer. You create aliases for the base item if the item has SKUs.

Note: If you enter Y in this field, the system searches for an alias in alphanumeric sequence and display the first alias it finds on the Telemarketing Specials in Order Entry. The actual item code does not display on this screen.

Prompting on the Item field: If this system control value is set to Y, when you prompt (press F4 on) the Item field in order entry, you advance to the Alias Selection Screen, which displays just the aliases associated with the offer that applies to the current offer. If you prompt on the Item field while reviewing item availability at the Display Item Availability Screen (Reviewing Item Availability), just the aliases associated with the default offer selected by the system (as described under Determining the Offer and Price) are displayed. Any items that do not have aliases set up with the selected offer are not available for selection from the Alias Selection Screen. See Ordering Items by Alias in Order Entry for more information.

Enter N or leave this field blank if you want the actual item code to display, rather than the alias. Your customers can still order the item by its alias, but the actual item code is visible to Order Entry, Order Maintenance, and Order Inquiry operators, and you do not advance to the Alias Selection Screen when you prompt on the Item field in Order Entry.

SKU cross reference? If this system control value is set to N and the Search SKU Cross Reference (J56) system control value is set to Y, you advance to the SKU Cross Reference Selection screen when you prompt on the Item field in order entry. However, if the Display Item Alias system control value is set to Y, it overrides the Search SKU Cross Reference (J56) system control value. See Work with SKU Cross Reference Type Screen for a discussion.

For more information: See Merchandising Chapter 27: Assigning Items/SKUs to Offers for more information about using aliases when assigning items or SKUs to offers; and see Ordering Items by Alias in Order Entry for more information on ordering items by alias.

Capture Operator Statistics (D61)

Purpose: Use this screen to define whether the system collects various statistics for Order Entry operators so that you can monitor and evaluate operator performance and accuracy.

MSR0052 CHANGE Change System Control Value 3/05/96 12:00:04

Description . : Capture Operator Statistics?

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to collect Order Entry operator statistics automatically; otherwise, enter N.

To view operator statistics:

• press F20 at the Select Customer Sold To for Order screen while you are in Order Entry, or

• enter DOPR in the Fast path field at the top of any menu screen, or

• select the Display Operator Statistics option from the menu.

Two sets of statistics are captured: one for the operator's current session and the other for the operator's daily totals. Information is summarized across companies so that a single set of statistics is collected for operators who enter orders for different companies.

If you are looking at the operator statistics from outside Order Entry, you see daily totals only because the operator has no current session and no current totals.

Statistics are captured for:

• Session length

• Number of orders accepted

• Number of orders rejected

• Total number of items ordered

• Average order amount

• Average number of items per order

• Average number of lines per order

The system updates the Operator Statistics Inquiry screen each time the operator presses F9 or F19 to accept an order or F11 to reject an order.

For more information: Chapter 3: Selecting Customers in the Order Entry manual.

Perform Source Pricing Validation (D62)

Purpose: Use this screen to define whether the system should prevent the operator from entering items that do not belong to an offer running a special pricing promotion.

MSR0052 CHANGE Change System Control Value 3/13/96 17:27:50

Description . : Perform Source Pricing Validation

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: If you enter Y here, the system validates each item added to the order to ensure that it is associated with the source code running the special pricing promotion. You may use this feature if you want to restrict this group of customers to ordering specific items at special prices. This applies to Order Entry and Order Maintenance.

You may set up special pricing for items by using option 6 (Special pricing) in the Source Code file. The Special Source Price file allows you to define the item that is on special, the required quantity to order, and the special price. See Marketing Chapter 6: Working with Source Codes (WSRC).

You may use this feature only if the Pricing method defined for the source code is:

P = Regular Pricing Hierarchy, as defined in the Pricing Values (B31) field of the System Control file, or

D = Regular Plus Reprice

The system performs this validation based on the source code used on the order (on the Header screen), regardless of whether you override the source code at the line level. This is because the system prices an item based on the source code used on the order. The source code override at the line level affects demand only (the number and dollar amount of items ordered).

The system issues a message if the item is not associated with the source code. You are prevented from adding the item to the order.

Item (xxxxxxxx) not valid for Source Code

If you set this value to N or leave it blank, the system uses the normal pricing hierarchy and does not prevent you from adding any items to the order.

Default Customer Class in Order Entry (D63)

Purpose: Use this screen to define a customer class to assign to new customers created through Order Entry.

MSR0051 CHANGE Change System Control Value 3/07/96 12:11:28

Description . : Default Customer Class in Order Entry

Code . . . . . 01 ANY VALID

CUSTOMER

CLASS

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter a customer class code to assign automatically to new customers or order recipients that you create through order entry and catalog requests you create through the e-commerce interface. If you leave this field blank, no class defaults to new customers. You can use customer class codes for reporting purposes, to restrict the sale of certain items, to exclude certain pay types, or to control user-defined field prompting in order entry for a group of customers.

The customer class code is a 2-position, alphanumeric code. Your entry in the code field is validated against the Customer Class file.

See Customer Service Chapter 17: Setting Up the Customer Class File (WCCL) for more information on defining and using customer class codes.

Default Previous Pay Type in Order Entry (D64)

Purpose: Use this screen to define whether to use the customer's previous payment method as the default in Order Entry.

MSR0051 CHANGE Change System Control Value 3/20/96 12:58:24

Description . : Default Previous Pay Type in Order Entry

Code . . . . . ALL ALL ANY VALID

PAY TYPE

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter ALL or a valid pay type code in this field if you want the system to default the last pay type used by the customer on the most recent order to the customer’s new order.

How is the customer’s last pay type determined? The system uses the Last pay type field in the Customer Sold To Order History file to determine the last pay type used by the customer on the most recent order. If there was more than one pay type on the order, the system uses the last pay type entered on the order. You can review the last pay type used by the customer on the most recent order on the Display Customer Order History Screen.

Default previous pay type summary:

If you enter:

The system:

ALL

The system always defaults the last pay type used by the customer on the most recent order to the customer’s new order.

a valid pay type

The system determines if the last pay type used by the customer on the most recent order matches the pay type defined in the Default Previous Pay Type in Order Entry (D64) system control value.

• If the pay types match, the system defaults the pay type to the customer’s new order.

• If the pay types do not match, the system does not default the pay type to the customer’s new order.

Note:

• The system validates the pay type code against the Pay Type file. See Accounts Payable Chapter 5: Working with Pay Types (WPAY).

• The pay type code is a 2-position, numeric field, so you should enter a leading zero if the pay type takes only one position; i.e., enter 01 for pay type 1.

blank

The system does not default the last pay type used by the customer on the most recent order to the customer’s new order.

Default pay type window: If the last pay type used by the customer on the most recent order defaults in Order Entry, a pop-up window opens when you press F9 or F19 after entering the order detail.

Last pay type used:

Window that displays:

Cash/Check

The system displays the Enter Cash Control For Window (Cash/Check Payment Type) so that the user can apply a new cash/check pay type to the order.

Credit Card

The system displays the Enter Credit Card For Window (Credit Card Payment Type) so that the user can apply a new credit card pay type to the order.

If the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value is set to N or blank, the system defaults the last credit card number and expiration date defined for the customer in the Customer Sold To Order History file to the order. If the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value is set to Y, the customer needs to provide a credit card number and expiration date.

The system does not automatically display this window for a credit card pay type if it is associated with an authorization service whose Use Tokenization field is Y.

A/R

The system displays the Missing Purchase Order Window (Accounts Receivable Payment Type) so that the user can apply a purchase order number for the A/R pay type to the order.

Coupon/Credit

The system displays the Enter Coupon/Credit For Window (Coupon/Credit Payment Type) so that the user can apply a coupon or credit to the order.

Pre-billable items: An order that includes a pre-billable item cannot include a non-credit card payment method.As a result, if there is a pre-billable item on an order, the window does not open for non-credit card payment methods. See Pre Billed Amount Item (J72) for an overview.

See Order Entry Chapter 4: Entering Orders Using Header Format for more information on completing payment information on an order.

Request Order Batch screen pay type default: If you enter a payment type to default at the Request Order Batch screen in Order Entry, it overrides any value defined here. If a credit card pay type is defined at the Request Order Batch screen, the system does not provide the customer's credit card number and expiration date.

Leave this field blank if you do not want the customer's previous pay type to default in Order Entry.

Track Invoice Currency (D68)

Purpose: Use this screen to define whether to track the currency conversion rate in effect when an order is billed.

MSR0052 CHANGE Change System Control Value 3/15/96 14:21:11

Description . : Track Invoice Currency

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Yes/no field: If you enter Y here, the system tracks the currency conversion rate in effect when orders are billed.

The system determines the currency rate by comparing the Sold To Customer's country code with the codes defined in the Currency file. If these codes match, the system writes a record to the Invoice Currency file (MSINCU) when the order goes through Billing Async.

The system also writes a currency rate record for your local currency if the local currency code is the same as the customer's country code.

The Invoice Currency file contains the following fields:

• Company code (numeric, 3 positions)

• Order number (numeric, 8 positions)

• Invoice number (numeric, 7 positions)

• Currency code (alphanumeric, 3 positions)

• Conversion rate (numeric, 11 positions with a 7-place decimal)

If you enter N or leave this field blank, the system does not track the invoice currency rate.

For more information:

• Accounts Payable Chapter 10: Working with Currency (WCUR).

• Customer Service Chapter 14: Setting Up the Country File (WCTY).

Default Country for International Address Format (D69)

Purpose: Use this screen to define the country to default for users and user classes who are assigned to alternate screens for Order Entry, Order Maintenance, Order Inquiry, Catalog Requests and Customer Maintenance. Typically, these users enter and service orders for Japanese customers.

MSR0051 CHANGE Change System Control Value 3/15/96 12:07:22

Description . : Default Country for International Address Format

Code . . . . . AUS BEL CAN ENG

JPN MEX SPN TAI

TAN USA

Narrative . . .

Application . : O/E

Applic group .

Sequence# . . .

F3=Exit F12=Cancel

Code field: Enter the country code that you want to load in the Country field for all screens that use the alternate address format.

You may assign certain users or user classes to the alternate screens if they are responsible for entering and servicing orders for your Japanese (or other foreign) customers.

Use the User Address Format file (F7 at the Work with Users Screen) to assign specific users to these screens or use the User Class Format file (F7 at the Work with User Classes Screen) to assign a group of users to these screens.

Users or user classes assigned to the alternate screens do not have access to the standard Order Entry, Order Maintenance, Order Inquiry, Catalog Requests and Customer Maintenance screens.

More information:

Chapter 3: Setting Up User Classes (WUCL)

Chapter 4: Working with User Records (WUSR)

Chapter 144: Displaying More Options of the Customer Service manual for screen samples and descriptions.

Method for Processing Overpayments in Order Entry (D70)

Purpose: Use this screen to define how you would like to handle overpayments on prepaid orders.

MSR0051 CHANGE Change System Control Value 4/10/96 12:30:28

Description . : Method for Processing Overpayments in Order Entry

Code . . . . . OE PROMPT AUTO/REFND AUTO/CONTR OE PROMPT

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter AUTO/REFND if you want to create a refund automatically when a customer overpays on a prepaid order (payment category 1).

Enter AUTO/CONTR if you want to apply all overpayments on prepaid orders automatically as contributions.

Enter OE PROMPT if you want the Overpayment Exists window to display in Order Entry when a customer overpays on a prepaid order:

Overpayment exists!

Order Total : 15.00

Amount Paid : 20.00

Soldout Merchandise : .00

Amount Overpaid : 5.00

F7=Apply as contribution

F10=Process as refund

The total overpayment amount on an order does not include the price of any soldout items; the system automatically creates a refund record for soldout merchandise.

You have the option of converting a contribution to a refund, either through Order Inquiry or the Work with Contributions function. To do so, however, you must have the proper authority.

Once you apply an overpayment as a contribution, you cannot reapply it to the order (for example, in the case of an exchange). Also, if the customer subsequently cancels the order, the contribution is not automatically included in any refund.

For more information: See the Convert Contribution Authority (A41) secured feature.

See Accounts Payable Chapter 5: Working with Pay Types (WPAY) for more information on defining a Contributions general ledger account number for prepaid payment types.

See Order Entry Chapter 13: Setting Up Order Entry Values for more information on working with the contribution pop-up window.

See Customer Service Chapter 57: Reviewing Financial Information for more information on reviewing information on contributions or converting a contribution to a refund through Order Inquiry. See Chapter 104: Working with Contributions (WCON) for more information on using the Work with Contributions function.

Use Source Code from Order Header When Creating Order Lines (D73)

Purpose: Use this screen to define whether the source code on the order header defaults automatically to the order detail lines.

MSR0052 CHANGE Change System Control Value 4/16/96 16:14:37

Description . : Use source code from order header when creating order lines

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the source code on the order header to default to each detail line on the order.

Enter N or leave this field blank if you do not want the source code on the order header to default to the order detail lines. The source code field on each detail line is blank unless you override it, either through the Load Source from Mailing History (D20) or Update Source Code from Mail History (J94) system control value or through option 2 in Order Entry or Order Maintenance.

Using a source code for each order detail line allows you to refine your demand tracking. This might be useful if your customers frequently order items from more than one catalog at once.

For more information: See Order Entry Chapter 1: Introducing Order Entry for more information on displaying or overriding the source code on an order detail line.

Require Reason for Lines Added in Order Maintenance (D75)

Purpose: Use this screen to define whether to require an add reason code when you add an item to an order in Order Maintenance.

MSR0052 CHANGE Change System Control Value 4/25/96 9:35:45

Description . : Require reason for lines added in Order Maintenance

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to require an add reason code when you add an item to an order in Order Maintenance. You define add reason codes in the Add Reason Code file, discussed in Chapter 10: Establishing Add Reason Codes (WADR) of the Customer Service manual.

When you add an item in Order Maintenance, the Enter Add Reason window displays:

Enter Add Reason

Reason . .

Enter to Continue

For more information: See Customer Service Chapter 66: Adding an Item for more information on adding an item to an order.

The system tracks the add reason codes you use. You can review this information for an order line by entering 24 next to the item in Order Inquiry; see Customer Service Chapter 55: Reviewing Order Details.

You can print a report of add reason codes used. This report, the Order Addition Audit Report, is sorted by operator. You can run this report either through a menu option or by adding it as a periodic function. See Customer Service Chapter 74: Order Status and Activity Reports for more information.

Enter N or leave this field blank if you do not want to use add reason codes.

Include Handling in Freight Charge Calculation (D77)

Purpose: Use this screen to define whether the system includes handling charges on an order in the total dollar value subject to freight charges when using dollar chart or percentage freight calculation methods.

MSR0052 CHANGE Change System Control Value 6/05/96 11:25:49

Description . : Include Handling in Freight Charge Calculation

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to include handling charges in the total dollar amount on an order subject to freight charges. You can include handling for freight calculation when using the following freight calculation methods, each defined in the Freight method field in the Source Code file:

• freight by dollar chart/source ($S)

• freight by dollar chart/offer ($0)

• recipient (R)

• percentage by source (PS)

• percentage by ship via (PV)

• offer price (OP)

See Marketing Chapter 6: Working with Source Codes (WSRC) for more information on working with source codes and freight methods.

Note: The system also includes handling charges when calculating the order total subject to service charges by ship via if this system control value is set to Y. See Fulfillment Chapter 30: Working with Ship Via Codes (WVIA) for more information on service charges by ship via.

Enter N or leave this field blank if you do not want to include handling when calculating freight using one of the freight calculation methods.

PO Required for A/R Orders (D79)

Purpose: Use this screen to define whether to require a purchase order number for accounts receivable orders in Order Entry.

MSR0052 CHANGE Change System Control Value 5/14/96 15:31:05

Description . : PO Required for A/R Orders

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you require a purchase order number from your accounts receivable customers. An accounts receivable payment type is defined as payment category 3 in the Pay Type file. See Accounts Payable Chapter 5: Working with Pay Types (WPAY). Accounts receivable payment methods also require a Bill To customer be defined for the order. See Order Entry Chapter 12: Assigning a Billing Address.

If you set this field to Y, and the operator does not enter a purchase order number on either the order header or order recap screen, the Missing Purchase Order window displays:

Missing Purchase Order!

Order # . : 2486 - 001

PO# . . . .

A purchase order# is required

on all A/R pay type orders.

F3=Exit (no update)

Enter N in this field or leave it blank if you do not want to require a purchase order number for accounts receivable orders.

Verify Duplicate PO Numbers for A/R Orders (D80)

Purpose: Use this screen to define whether to verify that each purchase order number a customer uses is unique.

MSR0052 CHANGE Change System Control Value 5/14/96 15:48:06

Description . : Verify Duplicate POs for A/R Orders

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to verify that each purchase order number you enter on an order from a sold-to customer is unique. See Order Entry Chapter 3: Selecting Customers.

Note: Purchase order numbers are usually used for accounts receivable orders (payment category = 3) but you can use them for any payment type.

If you enter a duplicate purchase order number for a customer on either the order header or order recap screen, the following message displays:

PO# (xxxxxxxxx) already exists on another order for this customer.

Similarly, if you process an order with a duplicate purchase order number through the e-commerce interface or phone order load, the order goes into error status, with an error of Duplicate PO# on the Print Phone Errors report or Order Error Listing.

Enter N in this field or leave it blank if you do not want the system to validate that purchase order numbers for a customer are unique.

Archive Orders to Optical Disk (D81)

Purpose: Use this screen to define whether you archive purged orders to an optical disk.

MSR0052 CHANGE Change System Control Value 8/07/96 9:08:44

Description . : Archive Orders To Optical Disk

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you are using an optical disk storage device to archive purged orders. If you archive orders to optical disk, you can retrieve them for Order Inquiry and Order Maintenance.

The Purge Orders function purges all closed or canceled orders with no activity for the number of days defined in the Order Purge Days (C62) system control value. If you enter Y in the Archive orders to optical disk field, the system retains these orders in a P (purged) status. You can then use the Archiving Orders to Optical Disk (AOPT) function to transfer the orders to the optical disk.

After you use the archive function, the system retains the order header record in main storage with an order status of A (archive). This allows you to select the order for inquiry or maintenance. When you select an archived order for inquiry, the system retrieves the complete order record from optical disk. If you maintain the order, the system restores the complete order record to main storage.

Note: You must have an optical disk installed on your system and use OptstorTM Optical Database Access software from the Midrange Performance GroupTM in order to use this option. Contact your MICROS representative for more information.

Enter N in this field or leave it blank if you are not using an optical disk to archive purged orders.

For more information:

Chapter 60: Purging Orders (MPOR, FORP, VORP, DORP) and Chapter 61: Archiving Orders to Optical Disk (AOPT) of the System Operations guide for more information on purging orders and using an optical disk storage device.

Chapter 52: Using the Order Inquiry Scan Screens (OIOM) and Chapter 63: Selecting an Order for Maintenance of the Customer Service manual for more information on reviewing or maintaining archived orders.

Extra Weight for Order Weight Freight Method (D85)

Purpose: Use this screen to define the extra weight per carton to use when calculating freight with the order weight method.

MSR0259 CHANGE Change System Control Value 7/23/96 16:10:31

Description . : Extra Weight for Order Weight Freight Method

Weight . . . . 1.000

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Weight field: Enter the weight for the system to use for each carton when using the order weight freight method. This freight method involves calculating the total weight of the items on the order and the number of cartons required to ship them, based on a maximum carton weight that you define for the shipper. The system then consults the freight table defined for the source code to determine the amount to charge for each carton. The system calculates freight separately for each different ship via and arrival date on the order; it also calculates freight separately for ship-alone items.

See Fulfillment Chapter 41: Working with Weight Tables for Order Weight (WFTB) for more information on working with this freight method.

Prorate Dollar Discounts and Coupons (D90)

Purpose: Use this screen to define whether to prorate coupon amounts or dollar discounts by source code or offer across items on the order.

MSR0052 CHANGE Change System Control Value 8/16/96 11:23:21

Description . : Prorate Dollar Discounts and Coupons

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to prorate dollar discounts or coupons across items on an order. This setting has the effect of ensuring that refund amounts are based on the actual price the customer paid for the item, after taking all applicable discounts.

When this field is set to Y:

• When you press F21 in order entry:

• If the Promotion Code Entry Required for Discount (I63) system control value is set to Y, you advance to the Enter Promotion/Discount Window

• If the Promotion Code Entry Required for Discount (I63) system control value is set to N, you advance to the Enter Coupon Discount Amount Window

Note: Depending on other settings in your company, you might advance to additional windows when you press F21 in order entry. See the Promotion Code Entry Required for Discount (I63) system control value for more information.

• Any dollar discount by source code or offer appears in the Discount bucket on the order totals fields, rather than as a negative additional charge, as well as reducing the selling prices of items. See Prorating Logic.

• The system writes an Order History Message to the Order Transaction History file regarding the amount of the prorated discount.

Set this fieldto N if you do not want to prorate coupons or dollar discounts. You do not advance to the Enter Promotion/Discount window or the Enter Coupon Discount Amount window when you press F21 in order entry, and any source code or offer dollar discount is added to the order as a negative additional charge. When you process a return against the order, the refund amount does not reflect the source code or offer dollar discounts. See Working with Source Codes (WSRC).

Prorating Logic

The system applies the coupon amount entered through the window, plus any applicable dollar discount for the source code or offer, to each line on a pro-rata basis. Promotion discounts set up with a Discount amount, but without specifying an Additional charge code are also prorated this way. See Working with Promotion Values (WPRO) for more information on setting up promotion discounts.

 

extended amount of the detail line before applying discounts / discountable order merchandise total = discount percentage

pre-discount unit price of the detail line - [(total discount amounts to prorate * discount percentage from above calculation) / line unit quantity] = unit selling price

Example:

An order has a discountable merchandise total of $50.00, including a single line of four units at $10.00 each. The total discount amount to prorate is $5.00.

40.00 / 50.00 = .80%

10.00 - [(5.00 * .80) / 4] = 9.00

Explanation:

40.00 / 50.00 = 80% (extended amount of detail line divided by discountable order merchandise total)

5.00 * 80% = 4.00 (total discount to prorate * discount percentage from above calculation)

4.00 / 4 = 1.00 (divide the result by the line unit quantity)

10.00 - 1.00 = 9.00 (subtract the result from the pre-discount unit price to determine the unit selling price)

When you process a return, the system uses the unit selling price to calculate the refund. When you process an exchange, the system presents the option of using the unit selling price for the exchange; see the description of the Price Override Reason for Same Price Exchanges (D92) system control value.

Note: There may a rounding discrepancy on the total discount applied to an order when you prorate against the order lines if the amounts do not divide evenly. This discrepancy should be no more than a few pennies. The likelihood of the rounding discrepancy occurring increases if there are multiple discounts that apply to an order, such as a promotion percentage discount and a dollar discount by source. You might notice this rounding discrepancy when you review the order history message, as described below.

Order History Message

The system writes a message to the Order Transaction History file when it prorates a coupon or dollar discount amount against an order.

Date Type Transaction Note Amount User

8/16/96 M TOTAL PRORATED DISCOUNT 5.00 ELISE_K

You can display order history by pressing F18 in order inquiry or at the Work with Order Lines screen in Order Maintenance. See the Display Order Line History Screen for more information.

For more information: See:

Pricing Values (B31): an overview of how the system reprices or discounts an order.

Working with Source Codes (WSRC): setting up dollar discounts by source code.

Working with Offers (WOFR): setting up dollar discounts by offer.

Working with Promotion Values (WPRO): setting up promotion discounts.

Reviewing Order Details: reviewing item pricing in order inquiry.

Canceling an Order through Order Maintenance: processing returns and exchanges through order maintenance.

Maximum Coupon Amount (D91)

Purpose: Use this screen to define the maximum coupon amount you can apply to an order at the Enter Promotion/Discount Window or the Enter Coupon Discount Amount Window.

MSR0056 CHANGE Change System Control Value 8/16/96 11:26:40

Description . : Maximum Coupon Amount

Dollar amount . 10.00

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Dollar amount field: Enter the maximum coupon amount to apply to an order in order entry at the Enter Promotion/Discount Window or the Enter Coupon Discount Amount Window. You display one of these windows by pressing F21 at the order detail screen in order entry if the Prorate Dollar Discounts and Coupons (D90) system control value is set to Y. The Promotion Code Entry Required for Discount (I63) system control value controls which of these windows displays; see that system control value for more information.

Leave this field blank if you do not prorate dollar discounts and coupons. In this situation, you should set the Prorate Dollar Discounts and Coupons (D90) system control value is to N.

Note: If the Prorate Dollar Discounts and Coupons (D90) system control value is set to Y, but you do not enter a maximum coupon amount, the window still appears in Order Entry when you press F21, but you can not enter a coupon amount.

Price Override Reason for Same Price Exchanges (D92)

Purpose: Use this screen to define the price override reason code to use when you use exchange a discounted item for a non-discounted item at the original item's selling price.

MSR0051 CHANGE Change System Control Value 8/16/96 11:29:06

Description . : Price Override Reason for Same Price Exchanges

Code . . . . . D A B D G

X Z 1

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the price override reason code for the system to use when you exchange an item sold at a discount for an item that would normally sell at a higher price, without charging the customer more for the replacement item.

When you override the price on an item in Order Entry or Order Maintenance, the system requires a price override reason code. This is a one-position, alphanumeric code, defined in and validated against the Price Override Reason file. Valid codes display on the screen. See Customer Service Chapter 2: Establishing Price Override Reason Codes (WPOR) for more information on defining codes.

The Use price of existing line field at the Enter Exchange Item Screen defines whether you override the exchange item's regular price and offer it to the customer at the discounted price of the original item. If you enter Y in this field, the system uses the price override reason code you defined in the System Control file. If you have not defined a price override reason code, a message displays:

Price Override Reason Code not found (SCV=D92).

The system does not allow you to process a same-price exchange if the price override reason code has not been defined in the System Control file.

Price override limit: If you use the price override reason code defined in the Price Override Reason for Same Price Exchanges (D92) system control value to enter a price override, the system allows you to exceed the price override limit defined in the Price Override Limit Percent (E55) system control value, regardless of your authority to the Price Overrides (A23) and Override Price Override Limit (A64) secured features.

Individuals Required in Order Entry (E01)

Purpose: Use this screen to define whether the system requires you to specify the individual within an organization who places the order for each order you enter.

MSR0052 CHANGE Change System Control Value 8/22/96 14:32:51

Description . : Individuals Required in Order Entry

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to require that an order placer be specified on each order you enter. Optionally, you can specify an originator for each order as well.

If you create a new sold-to customer in Order Entry, the Select Individuals for an Order Screen opens after you enter the header information. When you create a new sold-to customer in Order Entry which results in a duplicate sold-to record and you select the existing address, an error message displays if a placer has not been specified:

Placer Required.

Similarly, if you receive an e-commerce or phone load order without a placer specified, the order fails the phone edit with an error of Placer invalid.

Note: There are some exceptions to the requirement for individual assignment in order entry; they are described below.

Why use individuals? Tracking the individuals who place or originate orders may be useful if you primarily sell to large organizations, and a variety of people from different departments place orders with you at different times. The system tracks individual customers as subordinate records to the sold-to customer (in this case, the company or organization); this allows you to distinguish among any number of open orders for the same organization based on which individual within the organization placed the order. Typically, you would define the person who actually calls and places the order as the “Placer,” and the person who approves or requests the order as the “Originator.”

Default position: There are situations in which you do not need to specify an individual for an order. You can use the Individual Position for Consumer Customers (G02) system control value to define a professional position (such as buyer or manager) to:

• use to assign to a new individual that the system creates automatically when you create a new customer in order entry, and assigns that new individual to the order without prompting, or

• control whether an existing individual for an existing customer should be assigned to the order automatically without prompting

Using the Select Customer Individual Screen screen: This screen allows you to scan based on what you know about the individual, rather than what you know about the sold-to customer.

Summary of individual settings for order entry: The table below summarizes the possible settings related to creating or selecting individuals in order entry, based on the system control value settings and the status of the customer. The same conditions apply to orders you receive through the e-commerce interface or the remote phone order load; the Print Phone Errors report lists an error of Placer Invalid in situations where a placer is required but not included on the order.

Individuals required in order entry set to:

Individual position for consumer customers set to a valid position code?

New customer?

Need to select individual(s)?

Yes

Yes

Yes

No: Instead, the system creates an individual using the customer's name and the position defined in the System Control file, and assigns this individual to the order. (However, you can configure this process using a user exit point to control whether an individual is required based on the setting of the customer's Commercial flag, which defaults to N when a new customer is created.)

Yes

Yes

No

No: If the customer's first individual matches the position defined in the System Control file, you do not advance to this screen automatically; instead, this individual is assigned to the order. Also, the customer's name fields (first name, middle initial, last name, prefix, and suffix) are filled with the individual's name information. This setting might be useful to you for commercial customers. This automatic advancement occurs whether you select the sold-to customer at a customer scan screen, or the individual at the Select Customer Individual Screen.

 

 

 

Yes: If the customer does not already have an individual, or if the customer's first individual doesn't match the position in the System Control file, you advance to this screen automatically, and must select an individual placer for the order. If you selected an individual at the Select Customer Individual Screen, the selected individual defaults as the placer on the order.

Note: If you set the first individual's position to match the position defined in the System Control file, you are not prompted again the next time you enter an order for the customer.

Yes

No

Yes or No

Yes: You must specify an individual placer for each order you enter. If you selected an individual at the Select Customer Individual Screen, the selected individual defaults as the placer on the order. Optionally, you can also specify an originator.

No

Yes

Yes

No: The system does not create or assign an individual.

No

Yes

No

No: If the customer does not already have an individual, you do not advance to this screen automatically, and the system does not create or assign an individual; or,

If the customer's first individual matches the position defined in the System Control file, you do not advance to this screen automatically, and the individual is automatically assigned to the order. This automatic advancement occurs whether you select the sold-to customer at a customer scan screen, or the individual at the Select Customer Individual Screen.

Yes: If the customer's first individual does not match the position defined in the System Control file, you advance to this screen automatically and must select an individual placer for the order. If you selected an individual at the Select Customer Individual Screen, the selected individual defaults as the placer.

No

No

No

No: If the customer does not already have an individual, you do not advance to this screen automatically and you do not need to select an individual for the order.

Yes: If the customer has an individual, you advance to this screen automatically and you must select an individual for the order. If you selected an individual at the Select Customer Individual Screen, the selected individual defaults as the placer.

No

No

Yes

No: The system does not assign an individual to the order.

Enter N in this field or leave it blank if you do not want to require a placer for each order. You advance to the Select Individuals for Order screen only in the situations described in the table above. Similarly, a placer is required for e-commerce or phone load orders only as described above.

Option always available: You still have the option of associating a placer or originator with selected orders by completing the related fields on the Work with Order Ship To Properties screen; however, the placer is not indicated on the header and detail screens in order entry, order maintenance, and order inquiry (the placer appears in the header version of order entry only). Additionally, the placer and originator are not indicated on the Order Billing History Detail screen (see Customer Service Chapter 34: Reviewing Customer History).

Note: You cannot specify an individual placer or originator in Work with Catalog Requests. See Order Type to Process as Catalog Request/Item Samples (E08) for more information on processing catalog requests for individuals.

For more information:

Chapter 29: Setting Up Secured Features (the Delete Customer Individuals Records (A45) secured feature)

• Order Entry Chapter 3: Selecting Customers (selecting individual placers and originators in Order Entry)

• Order Entry Chapter 13: Defining Order Properties (reviewing individual information in Order Entry)

• Customer Service Chapter 26: Understanding Customer Types

• Customer Service Chapter 38: Creating and Updating Individuals

• Customer Service Chapter 39: Working with Individual Departments (WDPM)

• Customer Service Chapter 40: Working with Individual Positions (WPOS)

Default Price Table (E04)

Purpose: Use this screen to define the default price table to consult if you use price table pricing.

MSR0051 CHANGE Change System Control Value 11/26/96 14:36:44

Description . : Default Price Table

Code . . . . . 123 123 456 789

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the code representing the price table for the system to consult if you use price table pricing, and if:

• there is no price table defined for the source code, or

• there is no record of an item in the price table defined for the source code

Price tables allow you to define prices, price breaks, and premium items for items or groups of items based on total quantity or total dollars ordered. You must also select price tables on the Pricing Values (B31).

The system always uses the price from the default price table for end-of-order repricing if there is no price table price for the item available at the source code level. When you first enter the item, however, and before you press F21 or F9, the system may not use the default price table price if you have set up pricing for the group, rather than for the individual item.

In the situation of:

When you enter the item on the order, the system:

When you accept the order or press F21, the system:

A default price table is defined in the System Control file and a different price table is defined for the source code

Assigns a price from the source code table if it exists; otherwise, goes through the regular pricing routine for the item

Reprices based on the source code price table, or the default price table if the item record exists there and not in the source code table; otherwise, does not reprice based on price table

A default price table is defined in the System Control file and no price table is defined for the source code

Assigns a price from the default table if you have defined pricing at the item rather than the group level; otherwise, goes through the regular pricing routine for the item

Reprices based on the default price table if the item record exists there; otherwise, does not reprice based on price table

A price table is defined for the source code but no default table is defined in the System Control file

Assigns a price from the source code table if it exists; otherwise, goes through the regular pricing routine for the item

Reprices based on the source code price table if the item record exists there; otherwise, does not reprice based on price table

Leave this field blank if you do not use price table pricing, or if you want to define price tables at the source code level only.

See Marketing Chapter 21: Working with Price Tables (WPTB) for more information on working with price tables.

Price Table Level Override Code (E05)

Purpose: Use this screen to define the price override reason code to use when overriding the maximum price break defined for an item in a price table.

MSR0051 CHANGE Change System Control Value 11/26/96 15:16:21

Description . : Price Table Level Override Code

Code . . . . . A A B D G

X Z

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 100

F3=Exit F12=Cancel

Code Field: Enter the price override reason code to use when overriding the maximum price break level specified for an item in a price table.

If you use price table pricing (discussed in Pricing Values (B31)), you can create pricing levels for items or groups based on total quantity or dollars ordered. You can also specify a maximum price break for an item, which prevents the system from repricing the item to a lower price, even if the item would otherwise qualify. By specifying a maximum price break, but also creating pricing levels that go beyond that price break, you leave yourself the option of “unlocking” the lower price in certain situations.

For example, you create the following pricing levels for item AB100:

Level

Quantity

Price

1

1 to 9

$10.00

2

10 to 19

$9.00

3

20 to 49

$8.00

4

50+

$6.50

You ordinarily sell this item in quantities of 30 or less. You define 3 as your maximum pricing level for item AB100, so that even if a customer orders more than 49, the price goes no lower than $8.00.

One of your customers places an order for 100. You can give the Order Entry operator the option of overriding the maximum and selling the item at $6.50 each by entering the price override reason code you specify in this system control value. The system recognizes the override reason, and reprices the item after the operator presses F21 or F9.

Leave this field blank if you do not need to override maximum levels in price tables.

The price override reason code is a one-position, alphanumeric code, defined in and validated against the Price Override Reason file.

For more information: See Customer Service Chapter 2: Establishing Price Override Reason Codes (WPOR) and Marketing Chapter 21: Working with Price Tables (WPTB).

Order Type to Process as Catalog Request/Item Samples (E08)

Purpose: Use this screen to specify an order type that identifies the order as a catalog request.

MSR0051 CHANGE Change System Control Value 8/22/96 15:26:30

Description . : Order Type to process as Catalog Request/Item Samples

Code . . . . . C C M O P

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter the order type code to identify catalog requests processed through Order Entry. Customers you create or update with this order type is identified on the system as catalog requesters, because they have a mail type of C (catalog requester) rather than B (buyer).

The order type is a one-position, alphanumeric code. Order types are defined in and validated against the Order Type file; see Customer Service Chapter 1: Establishing Order Types (WOTY) for more information. You enter an order type code at the Request Order Batch screen in Order Entry to specify the type of orders you are about to enter.

It may be useful to enter catalog requests through Order Entry (rather than through Work with Catalog Requests) if you usually track individual placers or originators on orders; the Work with Catalog Requests function does not allow you to enter individual information.

If you create a customer as a gift recipient in Order Entry (by pressing F2 or F19) the customer is coded as a recipient with a mail type of R.

See Order Entry Chapter 2: Setting Defaults for more information about selecting an order type at the Request Order Batch screen.

Package insert items are not added to orders with this order type. See Marketing Chapter 22: Package Insert Processing (WPIP) for more information about package insert items.

Default Ship Complete Flag (E09)

Purpose: Use this screen to default the Ship complete flag on the Order Properties screen to Y or N.

MSR0052 CHANGE Change System Control Value 10/23/96 8:28:43

Description . : Default Ship Complete Flag

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 100

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Ship complete flag on the Work with Order Ship to Properties Screen to default to Y. Ship complete processing applies to all orders unless an operator manually overrides the Ship complete flag for an order in Order Entry or Order Maintenance to N.

Enter N or leave this field blank if you want to default the Ship complete flag on the Order Properties screen to default to N. Ship complete processing only occurs if an operator manually overrides the flag for an order in Order Entry or Order Maintenance to Y.

COD Charge (E12)

Purpose: Use this screen to define the amount you charge customers for C.O.D. (cash on delivery) orders.

MSR0056 CHANGE Change System Control Value 8/13/96 14:04:29

Description . : COD Charge

Dollar amount . 2.50

Narrative . . .

Application . : O/E

Applic group . FRT

Sequence# . . . 99

F3=Exit F12=Cancel

Dollar amount field: Enter the dollar amount to add to an order when the customer chooses a C.O.D. payment method (payment category 4). This is an 11-position numeric field with 2 decimal places. See Accounts Payable Working with Pay Types (WPAY) for information about pay categories.

The system adds this charge to the order in the Freight + bucket. This charge is visible in the order total fields after you add the payment method at either the Enter Payment Method or Order Recap screens. If you enter N in the Calculate freight field in Order Entry (or the Recalculate freight field in Order Maintenance), the system does not add the C.O.D. charge to the order.

The system posts C.O.D. charges to the Additional freight general ledger number defined in the Division file.

The system does not refund C.O.D. charges automatically. To refund the customer, you must enter a negative additional charge.

Leave this field blank if you do not want to charge customers for C.O.D. payment.

Use Prospect Finder File (E40)

Purpose: Use this screen to define whether the system searches the Prospect file for customer information to default on the Work with Order or Work with Order/Detail screen in Order Entry.

MSR0052 CHANGE Change System Control Value 3/05/97 11:16:06

Description . : Use Prospect Finder File

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to search the Prospect file for address information associated with the prospect finder number entered in the Customer field on the Select Customer Sold To For Order Screen or Customer Selection Screen in Order Entry. A prospect finder number is a number you use to define each customer in a catalog mailing. For example, a prospect finder number may consist of a source code and customer number, as in a rented mailing list. The address information retrieved from the Prospect file defaults onto the Work with Order or Work with Order/Detail screen in Order Entry. This feature is helpful if you want to save time on keying in address information.

You can populate the Prospect file with address information by loading a tape onto your system. See Marketing Chapter 41: Loading the Prospect Finder File (LPFF) for more information.

The system searches the Prospect file only if your entry begins with an alphabetical character. The system displays a message similar to the following if it cannot find the number you entered:

 

Customer Finder ART5674 does not exist.

 

Enter N or leave this field blank if you do not want the system to search the Prospect Finder file. The system searches only the Customer Sold To file for the customer record.

Evaluate Promotional Items/Inserts in Order Entry/Maintenance (E48)

Purpose: Use this screen to define whether to add promotional items/package inserts to orders automatically in Order Entry.

MSR0052 CHANGE Change System Control Value 2/17/97 10:37:10

Description . : Evaluate Promotional Items/Inserts in OE/OM

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

 

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to evaluate the existence of promotional items/package inserts and add these items to the order automatically and free of charge if the order meets the specified criteria.

Enter N in this field or leave it blank if you do not want the system to add promotional items/package inserts to orders automatically.

To maximize system processing, you should set this field to N if you do not plan to establish criteria for adding package inserts.

Note: The system does not evaluate the order for package inserts in order maintenance, only in order entry.

Definition: Promotional items/package inserts are items that can be added to an order automatically in order entry based on criteria such as customer class, source code, offer, state, and item category.

For more information: See Marketing Chapter 22: Package Insert Processing (WPIP) for more information on creating, changing, and deleting package insert criteria and associated items.

Negative Additional Charge Limit (E49)

Purpose: Use this screen to define the dollar value used to limit the total negative additional charges applied to an order.

MSR0054 CHANGE Change System Control Value 2/25/97 11:58:19

Description . : Negative Additional Charge Limit

Number . . . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Number field: Enter a dollar value in this field to define the total negative additional charges you can apply to an order. This dollar value applies towards negative charges only. Any positive additional charges that you enter do not offset the negative charges limit.

You can override the dollar limit for negative additional charges applied to an order if you have authority. See Chapter 29: Setting Up Secured Features.

A message displays if the total value of negative additional charges exceeds the dollar value and you do not have authority:

Negative additional charge exceeds the limit for this order.

Enter a 0 or leave this field blank if you do not want to limit the value of negative additional charges you can apply to an order.

Note: Additional charges that the system adds to an order (through a promotion, for example) are not included in the negative additional charge total.

Sample screen:

Enter Additional Charges

Order # : 1004 - 1

Sold To : 12541 JOHNSON, MARC

Add'l

Opt Chg Code Amount Description Billed

----------------------------------------------------------------

2=Change 4=Delete

DD 3.00- DISCOUNT N

F3=Exit F12=Cancel

Dollar Method Used to Evaluate Offer Ship Via Override (E50)

Purpose: Use this screen to define whether the system looks at merchandise or order total in evaluating an order for an offer or source code-related ship via override.

MSR0051 CHANGE Change System Control Value 3/10/97 14:29:15

Description . : Dollar method used to evaluate offer ship via override.

Code . . . . . MERCH ORDER TOTL

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Set this field to MERCH to have the system consider the merchandise total on an order only when evaluating whether the offer qualifies for a ship via override based on offer or source code. The system uses the total merchandise amount, including any discounts, and compare this figure to the dollar total you have specified for the related offer or source code (and optionally, SCF) through the Working with Offer Ship Via Assignment (WSVA) function.

For example, you enter an order with a merchandise total of $90 and an order total of $101 for source code A123, which points to offer A01. The customer placing the order lives at SCF 017. The system checks the Offer Ship Via file and finds the following related ship via overrides:

Source code

Dollar total

SCFs?

Ship via

A123

$50

no

01

A123

$75

018-021

02

A123

$100

no

 

The system selects the override with the highest dollar total for which the order qualifies. This order qualifies for the first override. It does not qualify for the second override, because the SCF of 017 does not fall into the specified range; it also does not qualify for the third override, because the merchandise total is under $100. The system changes the ship via on the order to 01.

Set this field to ORDER TOTL to have the system include the order total, including any positive or negative charges, when evaluating an order for offer or source code-related ship via override. In the above example, the system would change the ship via to 03, since the order qualifies for this override based on the order total.

Using either method, the system includes all open, held, or backordered items on the order in the total, regardless of whether there is a source code, offer, or ship via override for the individual item. However, the system does not evaluate the order for this ship via override if there is not at least one reserved line on the order. Additionally, the system evaluates the order only once, when you first press F9 to accept it (or press F19 to accept a shipping address). If you subsequently change any order information in order entry or maintenance, the system does not reevaluate the order.

If you do not enter a value in this field, the system does not evaluate orders for offer or source code-related ship via override.

See Working with Offer Ship Via Assignment (WSVA) for complete information on setting up offer or source code-related ship via overrides.

Future Orders Item Status (E52)

Purpose: Use this screen to define the item status code used to select items for a future arrival date in Order Entry and Order Maintenance.

MSR0051 CHANGE Change System Control Value 3/25/97 16:17:51

Description . : Future orders item status

Code . . . . . B F

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter the item status code used to select items for a future arrival date in Order Entry and Order Maintenance. The future arrival date defaults in the Arrival date field for this item. This is helpful if you have items that always future ship, for example, next year's IRS W-4 forms.

The system uses the date defined in the Default Future Orders Arrival Date (E53) system control value to default for future ship items.

Leave this field blank if you do not want the system to default a future arrival date to items defined with this status on an order.

Item status is defined using the Working with Item Status (WIST) menu option.

Continuity items: If the item status code for a continuity item matches the item status code defined in the Future Orders Item Status (E52) system control value, the system uses the date defined in the Default Future Orders Arrival Date (E53) system control value as the starting future arrival date for the continuity item.

Example: A continuity item contains 2 items: 1 item that ships in the first interval and another item that ships in the second interval. When you add the continuity item to the order, the system defaults the date defined in the Default Future Orders Arrival Date (E53) system control value to the future arrival date for the item that ships in the first interval. The system uses this date to calculate the future arrival date for the item that ships in the second interval.

Item Status Messages

Since an operator may not notice that an item has been assigned a future arrival date automatically, you can use the Item status message fields in Order Entry as a reminder to your operators when a future ship item is ordered. See Merchandising Chapter 6: Working with Item Cycles (WICY) for more information on creating item status messages.

Sample screen: A sample screen of an order including item status messages is shown below.

OER0187 DISPLAY Work with Order Lines 3/26/97 12:17:17

Enter The Mail Order Company

Order#: 1066 - 001 Recip sts: Suspended Pay By:

Sld To: 12541 LEX AUTOPARTS ATTN: JOHNS Shp To: LEX AUTOPARTS ATTN: JOHNS

Merch Frt Fr+ Tax Hnd Chg Total

10.00 1.00 .50 11.50

------------------------------------------------------------------------------

Ofr Item COLR SIZE OTHR Qty Price N/C Ovr C/G S/H Exten

ART 1

THIS ITEM IS A FUTURE SHIP ITEM. THE ARRIVAL DATE

USED FOR THIS ITEM IS 01/01/98.

TAX 1 5.00 0 N 5.00

002 TAX FORMS Avl: 0

TAX 1 5.00 0 N 5.00

001 TAX FORMS Avl: 0

F2=Full/Line F6=Add line F7=Name/Address F8=Scan order lines

F9=Accept F11=Reject F14=Relationships F24=More keys

Default Future Orders Arrival Date (E53)

Purpose: Use this screen to define the future arrival date the system defaults to items defined with a future ship status on an order.

MSR0874 CHANGE Change System Control Value 3/25/97 16:45:13

Description . : Default future orders arrival date

Date . . . . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Date field: Enter the future arrival date used for items defined with a future ship status on an order. The system uses the status code defined in the Future Orders Item Status (E52) system control value to determine whether an item is a future ship item. If the status of the item matches the status defined in this system control value, then the future arrival date defaults in the Arrival date field.

Note: If the date defined in this field is earlier than today's date, the system defaults today's date in the Arrival date field.

Leave this field blank if you do not want the system to default this date when an item defined with a future ship status is ordered.

Price Override Limit Percent (E55)

Purpose: Use this screen to define the percentage of the price override limit Order Entry operators can enter for items.

MSR0057 CHANGE Change System Control Value 3/31/97 10:13:43

Description . : Price Override Limit percent

Percentage . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Percentage: Enter the maximum percentage order entry operators can discount an item through a price override. The system uses the price defined in the item/offer to determine whether the price override exceeds the percentage. The override limit applies only to prices that are lower than the item/offer price. This is helpful in reducing the possibility of fraud by order entry operators.

Enter 0 (zero) or leave this field blank if you do not want to define a price override limit for items in Order Entry and Order Maintenance.

Override price override limit: The Override Price Override Limit (A64) secured feature controls the ability for Order Entry operators to override the percentage defined in this system control value.

Secured Feature Setting

Price Override Exceeds Percentage

Price Override Does Not Exceed Percentage

*EXCLUDE

A message similar to the following displays if an operator enters a price that is less than the percentage allowed:

 

Entered price exceeds override limit.

 

The system processes the order line if an operator enters a price that is greater than the percentage allowed and writes a W order transaction history record for the price override.

The system processes the order line if an operator enters a price that does not exceed the percentage.

*ALLOW

The system processes the order line and writes a W order transaction history record for the price override. The W transaction history record shows you the line on the order where a price override occurred, the price override amount and the user ID of the person who performed the price override.

The system processes the order line.

Price override example: The system uses this calculation to determine the percentage of the price override:

(offer price - price override entered) / offer price * 100 = price override percentage

Example

price override percentage = 10%

offer price = $40.00

price override = $35.00

 

(40.00 - 35.00) = 5.00

 

5.00/40.00 = .125

 

.125 * 100 = 12.50 (12.50 exceeds the 10% price override)

Price override reasons that can exceed price override limit: If you use the following price override reason codes to enter a price override, the system allows you to exceed the price override limit defined in the Price Override Limit Percent (E55) system control value, regardless of your authority to the Price Overrides (A23) and Override Price Override Limit (A64) secured features:

Default Price Override Reason (B35)

Price Override Reason for Same Price Exchanges (D92)

Post Demand to Order Level Forecast Files for Soldout Items (E58)

Purpose: Use this screen to define whether you post demand for items sold out in order entry.

MSR0052 CHANGE Change System Control Value 7/07/97 10:08:38

Description . : Post Demand to order Level Forecast files for Soldout Items

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field or leave it blank if you want to post demand updates for items that you sell out in order entry. You also update demand for these items when they sell out in order maintenance if the Update Demand for Order Maintenance Transactions (C72) system control value is set to Y.

These files are updated if this system control value is set to Y or blank:

• Offer/Drop/Period (FCODRP)

• Offer/Drop/Period/Day (FCODPD)

• Source Period (FCSCPR)

An item is sold out in order entry or order maintenance based on a soldout control value you assign to an item or SKU. Soldout control codes are user-defined, but take one of these values:

• Sell out immediately

• Sell out when on-hand quantity is zero, excluding any quantity on open purchase orders

• Sell out when on-hand quantity is zero, including any quantity on open purchase orders

The system adds an item to an order with soldout status if it matches the status defined by its soldout control code. See Chapter 113: Working with Soldout Controls (WSLD).

You can also sell out an item in order entry or order maintenance if it is currently backordered by entering 13 next to the item.

Set this field to N if you do not want to update these files for items you sell out in order entry or order maintenance.

Demand Update for Non-Inventoried Items (E59)

Purpose: Use this screen to define whether you update demand when a customer orders a non-inventory item.

MSR0051 CHANGE Change System Control Value 7/07/97 11:29:12

Description . : Demand Update for non-inventoried items.

Code . . . . . ALL NONE ITEM

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Code field: Enter ALL in this field or leave it blank if you want to always update demand for non-inventory items.

Enter ITEM in this field if you want to update demand for non-inventory items only in files in which the item and SKU codes are key fields.

Enter NONE in this field if you never want to update demand for non-inventory items.

The system considers an item as a non-inventory item if there is a Y in the Non/inv field; this includes special item types such as membership items, set master items, and gift certificates.

Demand Updates: Affected Files

The files affected by this system control value, and the effects of each setting, are presented in the table below.

 

Updates if system control value set to:

File

ALL or blank (' ')

ITEM

NONE

Cancel Reason/Offer (CNCNRO)

Y

N

N

SKU Offer Page (INSKOP)

Y

Y

N

Order/Billing History (OEBHST)

Y

Y

N

Item/SKU/Offer (FCISOF)

Y

Y

N

Customer Sold To Item Class (OECSIC)

Y

N

N

Customer Individual Order History (CSTIOH)

Y

N

N

Customer Sold To Order History (CSTOOH)

Y

N

N

Customer Ship To Order History (CSHORH)

Y

N

N

Customer Bill To (CSCBIL)

Y

N

N

Order Type/User (OEOTYU)

Y

N

N

Order Type/User History (ORDUHS)

Y

N

N

Source (MSSRC)

Y

N

N

Source Period (FCSCPR)

Y

N

N

Offer/Drop/Period (FCODRP)

Y

N

N

Offer/Drop/Period/Day (FCODPD)

Y

N

N

External Postal Code Validation (E62)

Purpose: Use this screen to define whether the system calls a user-defined program to validate postal codes outside of CWDirect.

MSR0052 CHANGE Change System Control Value 5/01/97 15:56:40

Description . : External Postal Code Validation

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to call a user-defined program to validate postal codes outside of CWDirect. You can define the validations that occur for postal codes under the program OER0966. The system provides a “hook” to the program when a user presses Enter on a screen including a postal code.

This program can be used to validate postal code rules for a specific country, for example, if a postal code for a country should only contain 6 numbers and more than 6 numbers are entered, the program passes an error message similar to the following back to CWDirect:

 

Invalid Postal Code Format

 

Once the program completes, CWDirect returns to normal processing.

Changes to these files launch the postal code validation program when a user presses Enter on a screen including a postal code:

• Customer Bill To

• Customer Ship To

• Customer Sold To

• Order Header

• Order Ship To

• Order Ship To Address

• Call Tag

• Catalog Request

The program validates postal codes based on this information:

• Company Number

• Prefix

• First Name

• Initial

• Last Name

• Suffix

• Street Address

• Apartment

• Address Line 2

• Address Line 3

• Address Line 4

• City

• State

• Postal Code

• Delivery Code

• P.O. Box

• Company Name

Enter N or leave this field blank if you do not want the system to call a user-defined program to validate postal codes outside of CWDirect.

Default Source for Internet Orders (E65)

Purpose: Use this screen to define the default source code to use for an order received through the internet interface or the e-commerce interface if the order does not already contain a source code.

MSR0051 CHANGE Change System Control Value 9/18/97 11:50:43

Description . : Default Source for Internet Orders

Code . . . . .

Narrative . . .

Application . : O/E

Applic group : ALL

Sequence# . . : 99

F3=Exit F12=Cancel

Code field: Enter the source code you want the system to assign to any orders that you receive through the internet interface or the e-commerce interface if they do not already contain a source code.

About internet orders: You can receive orders placed at a web site through the internet interface. The process you follow with this interface is similar to the phone order interface, and involves:

• receiving order header and detail information into two CWDirect files, the iCat Order file (ICATHD) and the iCat Order Detail file (ICATDT)

• using the Receive Internet Orders menu option to convert the information in these files to the Phone Order file (PHORDS)

• using batch order entry to review, correct and accept these orders.

Before you can process internet orders, you must set up an FTP application through the Work with FTP Application menu option. See Order Entry Chapter 13: Setting Up Order Entry Values manual for more information on setting up the system for and processing internet orders.

About the e-commerce interface: You can also use this system control value to define the default source code if you use the e-commerce interface. Unlike the internet interface described above, the e-commerce interface allows you to create orders and process updates interactively instead of through a batch process. See System Operations Chapter 87: E-Commerce Setup for more information on the e-commerce interface.

Leave this field blank if you do not process orders through a site on the world wide web.

Tax Included in Price (E70)

Purpose: Use this screen to define whether you process orders subject to VAT and tax-inclusive pricing.

MSR0052 CHANGE Change System Control Value 6/03/97 15:46:26

Description . : Tax Included in Price

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you process orders to countries that are subject to Value Added Tax (VAT). On orders subject to VAT, tax does not accumulate in the Tax field; instead, the customer pays a tax-inclusive price for each item and the tax is “hidden” on the order detail line in the Hidden tax field.

The logic the system uses in determining the tax rate for both VAT and non-VAT orders differs, depending on the value in this field. See below for more information on how the system determines tax in either situation.

The customer sees only the tax-inclusive pricing on orders subject to VAT. However, system updates, such as order billing history, marketing reports, sales journals, etc. displays the price net of VAT; that is, the hidden tax amount is subtracted from the item price.

Example: The tax-inclusive price for an item is $10.00. A hidden tax amount of $1.50 is captured on the order detail line for the item. System updates record a sale of $8.50 ($10.00 - $1.50).

Note: You cannot use both Vertex and tax-inclusive pricing (VAT) in the same company. See Vertex Interface (A88) for more information on Vertex.

Calculation logic to determine the tax that applies to an order if this SCV is Y:

Calculation logic to determine the tax that applies to an order if this SCV is N:

Please note that in this scenario the system applies the VAT % for the country as a conventional tax rate.

Determining the Hidden Tax

The system checks these fields to determine the hidden tax amount or rate that applies to an item:

Item percentage or amount: You can define either a VAT percentage or flat amount for each item or SKU. In the case of a percentage, the system calculates the hidden tax amount by multiplying the rate and the price the customer pays for the item. In the case of a flat amount, the system applies this amount regardless of the item price. If you process orders in multiple currencies based on offer (see Multi Currency by Offer (E03)) the system converts the hidden tax based on the conversion rate in effect for the customer's country if the hidden tax for the item is defined as an amount. For example, if the hidden tax amount for an item is set at $2.00, and the conversion rate for the customer's currency is currently 1.50, a hidden tax amount of $3.00 is added to the order detail line (2 * 1.5).

VAT percentage: If there is no hidden tax amount or percentage defined for the item/SKU, the VAT percentage defined for the customer's country applies. If there is no hidden tax information for the item/SKU and no percentage defined for the country, there is no hidden tax for the item.

You can review the hidden tax amount for an item by entering 2 next to the item in order entry or order maintenance, or by entering 5 next to the item in order inquiry. The amount that displays is the per unit amount, not the extended amount.

Tax Exemptions

An order or item may be exempt from either conventional tax or VAT based on:

• VAT exemption for a state (in states that are exempt from VAT, conventional tax applies)

• customer tax exemptions or overrides defined either through customer maintenance or order entry

• a VAT exemption for the item/SKU (this exemption also relieves the item from conventional tax)

• item tax exemptions and exceptions for U.S. states, or GST and PST item exemptions and exceptions for Canadian provinces

Reseller or nonprofit tax exemptions cause the order to be exempt from either VAT or conventional tax, whichever would apply. However, VAT exemptions defined for either the customer or item/SKU apply only to orders subject to VAT. When an order that is normally subject to VAT is tax exempt, the customer pays the regular (not the tax-inclusive) price, and no hidden tax is included in the order detail line.

Note: Customer VAT exemptions apply only if the customer's country is different from the country of your company address.

Determining the Tax-Inclusive Price

When an order is subject to tax-inclusive pricing and VAT, the system goes through the same pricing routine as it normally would, with the exception that it looks in each case for the item's tax-inclusive price rather than the conventional, tax-exclusive counterpart. If you have not set up the necessary tax-inclusive prices for an item, an error message displays in order entry when a customer subject to VAT attempts to order the item.

VAT setup

Before beginning to process orders subject to VAT, you might need to set up information in your company:

• VAT percentage rates for countries and VAT exempt flags for states

• VAT exempt flags and hidden tax rates or amounts for items/SKUs

• VAT exempt numbers for customers

• tax-inclusive prices and associate prices for item or SKU offers, price tables, telemarketing specials, promotional prices, price codes, contract prices, etc.

• the Tax Inclusive Cutoff Date (E79) system control value

Other considerations: If you change information on an order that would affect whether the order is subject to VAT, you might need to clear or reenter certain information. For example, if you change the customer's shipping address in order entry, you should clear the tax code and resale/exempt certificate numbers from the order to see if the default information has changed.

The system reevaluates hidden tax for each item when any repricing applies in order entry (for example, with price tables). However, the system does not reprice any item with a price override reason code, even one added by the system (for example, an incentive item). If you change the tax status of an order in order entry by changing the shipping address or the customer's tax code, you should delete any item with a price override reason code and reenter it.

If you need to change the tax status of an order once you have accepted it, you should cancel the order and reenter it. Reevaluating the items in order maintenance is not supported.

The system may still add tax on freight or handling on orders subject to VAT, if the related system control values are set to Y and there is no override for the SCF or postal code.

Because it is the net price that is recorded in system updates, there may be situations where a sale is recorded as credit if, for example, you define a hidden tax as a flat amount rather than a percentage, but sell the item at a reduced cost or give it to the customer free of charge. In other words, if you define the hidden tax as a percentage, when you give the item away free of charge the system calculates the percentage against a selling price of zero, which produces a hidden tax amount of zero. However, if you define the hidden tax as an amount, the system subtracts this amount from a selling price of zero, resulting in a credit.

For more information:

Setting Up the Country File (WCTY) and Setting Up the Postal Code File (WZIP) for information on countries and tax rates for postal codes

Work with Contract Price Screen and Working with Customer Tax Statusfor information on customer tax exemptions and contract pricing

Working with SCF Codes (WSCF)

Working with Offers (WOFR) and Working with Special Pricing by Source Code (WSPP)for information on special pricing by source code and telemarketing specials

Available Discounts and Promotions for information on promotional pricing, upsell promotions, price codes and price tables

Performing Initial Item Entry (MITM) and Creating Item/SKU Offers (MISO) for information on setting up items and item/offers or SKU/offers

Override Offer/Page/Alias on Order Detail (E72)

Purpose: Use this screen to define whether the system changes the offer code and alias for an item to the offer including the item's page/alias.

MSR0052 CHANGE Change System Control Value 9/15/97 12:04:12

Description . : Override Offer/Page/Alias on Order Detail

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to change the offer code and alias for an item to an offer including the item's alias.

When you enter an item or alias in order entry, the system:

• Uses the offer on the order if you order the item by entering an alias associated with that offer, or if you enter the item using the actual item code and an alias exists for the item in that offer. The entered alias is saved in the Alias field in the Order Detail file. Example: Item AB100 has an alias of 001AB100 in offer 001. If the source code on the order header points to offer 001, and you enter either AB100 or alias 001AB100 in order entry, the system uses the Alias field in the Order Detail file to store the alias 001AB100.

• If you enter an alias for an offer that is not the offer currently on the order, the system uses the offer associated with the entered alias. The entered alias is saved in the Alias field in the Order Detail file. NOTE: You can enter an alias for a different offer only if the Search Offers for Alias (J68) system control value is set to Y. Example: Item AB100 has an alias of 001AB100 in offer 001 and an alias of 002AB100 in offer 002. If the source code on the order header points to offer 001, and you enter alias 002AB100 in order entry, the system uses the Alias field in the Order Detail file to store the alias 002AB100 and uses the Offer field to store offer 002.

• If there is no alias for the offer on the order, or if the offer includes the entered alias but not the selected SKU, the system searches for a current offer that specifies an alias (and the entered SKU) and selects the most recent active offer. If there is no active offer, it selects the most recent inactive offer. If the offer includes more than one alias, the system selects the first alias that was created. The selected alias is saved in the Alias field in the Order Detail file. Example: There is no alias for item AB100 in offer 001, but there is an alias of 002AB100 for the item in offer 002. If the source code on the order header points to offer 001 and you order AB100, the system uses the Alias field in the Order Detail file to store the alias 002AB100 to store offer 002.

• If the system does not find an alias in any offer, or if there is no alias for an offer that includes the selected SKU, it uses the offer associated with the source code currently on the order and does not update the Alias field in the Order Detail file.

Once the system selects an offer including the alias (and SKU), the Offer field on the Work with Order Line screen changes to the offer including the alias (and SKU).

Related system control values:

• The Search Offers for Alias (J68) system control value controls whether the system searches all active offers for the alias entered. If this system control value is set to N, the system displays an error message if you attempt to order an item using an alias that is not associated with the offer that currently applies to the order detail line.

• If the Display Item Alias (D56) system control value is set to Y, the alias, rather than the item code, displays in order entry, order maintenance, order inquiry and item availability. If Display Item Alias (D56) is set to N, the actual item code, rather than the alias, displays. You can set the Display Item system control value to Y or N if you set the Override Offer/Page/Alias on Order Detail (E72) system control value to Y.

Important: You must set the Override Offer on Order Detail Line (D49) system control value to N if you set the Override Offer/Page/Alias on Order Detail (E72) system control value to Y, or vice versa; you cannot have both of these system control values set to Y. The two options are not compatible, since the Override Offer on Order Detail Line (D49) involves tracking demand based on the offer that provides the price, and Override Offer/Page/Alias on Order Detail (E72) involves tracking demand based on alias.

Enter N or leave this field blank if you do not want the system to change the offer code for an item to the offer including the alias (and SKU), or to search for an alias when you order an item by item code rather than alias.

Tax Inclusive Cutoff Date (E79)

Purpose: Use this screen to define the date when VAT and tax-inclusive pricing became effective for your company.

MSR0893 CHANGE Change System Control Value 6/03/97 15:59:35

Description . : Tax Inclusive Cutoff Date

Date . . . . . 5/22/97

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 99

F3=Exit F12=Cancel

Date field: Enter the first date on which VAT and tax-inclusive pricing were in effect for your company. The system uses this information only if the Tax Included in Price (E70) system control value is set to Y.

When you print pick slips, bill, or maintain any order entered prior to this date, the system retrieves the correct tax rate for the shipping address and applies conventional tax rather than VAT and tax-inclusive pricing.

Enter the date in MMDDYY format and press Enter.

Note: You must set this date to have the system print, charge, bill, or credit tax correctly on preexisting orders when you turn on tax-inclusive pricing.

Leave this field blank if the Tax included in price field is set to N or blank.

For more information:

Chapter 32: Working with SCF/Ship Via Values (WSHV)

Chapter 29: Entering Additional Item Information

Default Salesrep Number (E86)

Purpose: Use this screen to define the salesrep number you want to default in the Salesrep number field on the Request Order Batch screen in order entry.

MSR0054 CHANGE Change System Control Value 8/14/97 16:32:50

Description . : Default Salesrep #

Number . . . . 0000001 0000002 0000003 0000004

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Number field: Enter a salesrep number in this field if you want the number to default in the Salesrep number field on the Request Order Batch screen in order entry.

Leave this field blank if you do not want a salesrep number to default in the Salesrep number field on the Request Order Batch screen in order entry.

Salesrep numbers are defined in Accounts Payable Chapter 11: Working with Sales Representatives (WSLS).

Require Salesrep Number in Order Entry/Order Maintenance (E87)

Purpose: Use this screen to define whether the Salesrep number field is a required field in order entry and order maintenance.

MSR0052 CHANGE Change System Control Value 8/14/97 16:42:31

Description . : Require Salesrep # in Order Entry/Order Maintenance

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Salesrep number field in order entry and order maintenance to be a required field.

The system validates the salesrep number against the Salesrep file. An error message displays on the Work with Order and Work with Order Detail screens if a salesrep number has not been defined:

Salesman# (0) is invalid or missing.

 

Enter N or leave this field blank if you do not want the Salesrep number field in order entry and order maintenance to be a required field.

Salesrep numbers are defined in Accounts Payable Chapter 11: Working with Sales Representatives (WSLS).

Modulus 10 Check on Salesrep Number (E88)

Purpose: Use this screen to define whether a modulus 10 check is performed against the salesrep number in Work with Salesreps.

MSR0052 CHANGE Change System Control Value 8/14/97 16:57:34

Description . : Modulus 10 Check on salesrep #

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to perform a modulus 10 check against the salesrep number.

The system performs a modulus 10 check against the salesrep number when you press Enter on the Create or Change Salesrep screen in Work with Salesreps.

Enter N or leave this field blank if you do not want the system to perform a modulus 10 check against the salesrep number.

Salesrep numbers are defined in Accounts Payable Chapter 11: Working with Sales Representatives (WSLS).

Display Special Format Response Descriptions in Order Entry (E90)

Purpose: Use this screen to define whether to display custom special format response descriptions in order entry.

MSR0052 CHANGE Change System Control Value 8/06/97 9:36:23

Description . : Display Special Format Response Descriptions in OE

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to display custom special format response descriptions in order entry.

The response descriptions are below the Response field on the Custom Special Handling and Special Format Response screens in order entry/maintenance. Displaying the descriptions is helpful if you use codes to represent valid responses. For example, if you identify the color black with the code 8859, order entry operators can identify code 8859 as black by referring to the Valid response description field.

For more information:

Chapter 16: Setting Up General Usage Values, for more information on other system control values related to special handling

Chapter 9: Establishing Custom Special Handling Formats (WSHF) of the Customer Service manual for more information on establishing special handling formats

Chapter 5: Working with Item Classes (WICL) of the Merchandising manual for more information on setting up special handling restrictions by item class

Chapter 4: Entering Orders Using Header Format of the Order Entry manual for more information on entering an item with custom special handling on an order

Enter N or leave this field blank if you do not want to display custom special format response descriptions in order entry.

User Defined Modulus Check Program (E94)

Purpose: Use this screen to define the program name used to validate credit card numbers entered for credit card pay types defined with an MU modulus check.

MSR0053 CHANGE Change System Control Value 8/11/97 11:03:34

Description . : User Defined Modulus Check program

System name . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

System name field: Enter the user-defined program name used to validate credit card numbers entered for credit card pay types defined with an MU (modulus user) modulus check. A modulus check performs a calculation against the digits of the credit card number to ensure that the card is valid.

Leave this field blank if you do not want to define an MU modulus check for a credit card pay type. An error message similar to the following displays in Work with Pay Types if you enter MU in the Modulus check field:

Modulus check program has not been specified for SCV E94.

For more information: See Accounts Payable Chapter 5: Working with Pay Types (WPAY).

Allow Negative Prices in Order Entry (E97)

Purpose: Use this screen to define whether you allow the entry of negative prices in order entry or order maintenance.

MSR0052 CHANGE Change System Control Value 10/01/97 14:04:30

Description . : Allow negative prices in Order Entry

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 100

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to allow operators to enter a negative price for an item in order entry or order maintenance.

When you enter a positive quantity and a negative, price, you produce a credit for the customer. When you enter a negative quantity and a negative price, you produce an invoice for the customer.

Enter N in this field or leave it blank to prevent operators from entering a negative price for an item in order entry or order maintenance. If the operator attempts to enter a negative price, the following error message displays:

Price cannot be negative.

Maximum Order Line Value (E98)

Purpose: Use this screen to define the maximum dollar value of an order line you can enter in order entry or order maintenance.

MSR0056 CHANGE Change System Control Value 10/28/97 9:35:45

Description . : Maximum Order Line Value

Dollar amount . 500.00

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Dollar amount field: Enter the maximum dollar value you can enter on a single order detail line in order entry or order maintenance.

The Allow Maximum Order Line Value Override (A69) secured feature controls the ability to exceed this maximum. If you have the proper authority, a pop-up window displays informing you that the order line you have just entered exceeds the maximum; you can press F9 to add the line to the order. If you press F3, F12 or Enter, an error message displays:

Order line value of 1000.00 exceeds maximum allowed in SCV E98.

If you do not have proper authority, no pop-up window displays when the order line exceeds the maximum dollar value. Instead, the error message displays. See Chapter 4: Working with User Records (WUSR) for information about user authority.

Leave this field blank if you do not want the system to perform a check against the order line total.

Note: The system checks the dollar total on an individual order line basis, not an order-level basis. In other words, no check takes place to prevent the order total from exceeding this maximum.

Sub Page Entry (E99)

Purpose: Use this screen to define whether the Sub page field displays on the Create Item Offer screen in Work with Item/SKUs and on the Create Item/SKU Offer screen in Create Item/SKU Offer.

MSR0052 CHANGE Change System Control Value 10/09/97 13:16:59

Description . : Sub Page Entry (Y/N)

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Sub page field to display on the Create Item Offer Screen in Work with Item/SKUs and on the Create Item/SKU Offers Screen in Create Item/SKU Offer.

You can use the Sub page field to call an external program that creates an item alias outside of CWDirect. The system provides a “hook” to the program when a user defines a sub page code and press Enter on the Create Item Offer or Create Item/SKU Offer screens. Once the program completes, CWDirect returns to normal processing. See System Operations Chapter 28: Working with User Exit Point (WUEP) for more information on user exit points.

Enter N or leave this field blank if you do not want the Sub page field to display on the Create Item Offer and Create Item/SKU Offer screens.

Display Order Line Discount Messages (F01)

Purpose: Use this screen to define whether discounted prices are highlighted and a message displays indicating the discount percentage in order entry, maintenance and inquiry.

MSR0052 CHANGE Change System Control Value 10/07/97 14:58:39

Description . : Display Order Line Discount Messages

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have any discounted price appear in reverse video in order entry, order maintenance, and order inquiry, and have a message display comparing the discounted price with the offer price for the item. This may be useful if you want the operator to be able to tell when a discount applies to an item, and how much of a reduction in price applies.

Enter N or leave this field blank if you do not want to highlight discounted prices and display a calculation message.

What qualifies as a discount? Any price that is less than the single-unit offer price for the item is considered a discounted price, and appears highlighted and with the discount message. For example, any of these produces a highlighted price and/or discount calculation message:

• manual price overrides

• telemarketing specials

• quantity break by item

• special pricing by source code

• associate pricing

• price table pricing

If you use tax-inclusive pricing, the system compares the actual price with the tax-inclusive offer price to determine if the item is discounted.

When the message does not display: The system does not display the message or highlight price when you override the price on the order line, and:

• no item/SKU offer price exists, or

• the price override reason code’s Override item offer price is set to Y.

Enter 2 next to the item in order entry or order maintenance, or 5 next to the item in order inquiry, to review how the price was calculated for the item and other information related to the order line.

Highlighted price display:

 

BU001 CHOC LRGE 1 2.51 A 0 N 2.51

005 CHOCOLATE EASTER BUNNY Rsv: 1 Avl: 26

Discount calculation: A message displays for each discounted item:

 

Line 1: Offer = 10.00 Actual = 9.00 Discount = 1.00 : 10.00%

 

This message includes the following information:

• the order line number of the discounted item

• the offer price

• the actual price (the discounted price the customer is paying)

• the dollar amount of the discount

• the discount percentage

When appears? The discount calculation message displays when you first add the item to the order. In the case of price table repricing, the calculation message displays when you press F21.

In order inquiry, the discounted price is highlighted, but no discount calculation message displays.

To review messages for other items: A plus sign (+) in the message area of the order detail screen indicates that there are discount calculation messages related to additional items on the order; you can review these messages by positioning your cursor on the same line as the plus sign and pressing Page down. To cycle back up through the calculation messages for the items on the order, press Page up. You can review the calculation messages only for the items that are currently displaying on the order detail screen. Press Page down or Page up when your cursor is not on the same line as the plus sign to display earlier or subsequent items on the order and/or their related discount calculation messages.

If you delete a discounted item, the plus sign may remain on the screen until you press F5 to refresh.

Note: Although the discount calculation message displays when you use the header/detail version of order entry, the price itself is not highlighted. Similarly, the unit price does not display on the Scan Order Lines and the full/line order detail screens, so only the discount calculation message displays.

If you use negative prices: When you process a return or credit by entering a negative price in order entry or order maintenance, the discount calculation message is based on the difference between the item's original offer price and the negative price. For example, if the original offer price for an item is $10.00, and you enter a return by entering a positive quantity but a price of -$10.00, a message such as the following displays:

 

Line 1: Offer = 10.00 Actual = -10.00 Discount = 20.00 : 200.00%

 

The Allow Negative Prices in Order Entry (E97) system control value controls whether you can enter a negative price.

If you use negative quantity: When you process a return or credit by entering a negative quantity in order entry or order maintenance and override the item price, there is still a discount calculation message based on the difference between the price you enter and the original offer price for the item. For example, if you process a return for an item by entering a negative quantity and want to credit the customer $5.00 for an item whose original offer price is $10.00, a message such as the following displays:

Line 2: Offer = 10.00 Actual = 5.00 Discount = 5.00 : 50.00%

Load Order Header Source from Mailing History (F05)

Purpose: Use this screen to define whether the most recent source code from an existing customer's mailing history defaults in order entry.

MSR0052 CHANGE Change System Control Value 11/04/97 15:29:19

Description . : Load Order Header Source from Mailing History

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the source code from the most recent mailing in a sold-to customer's mailing history to default onto the order header in order entry. This might be useful if it is likely that the most recent mailing you made to the customer produced the order.

If both this field and the Use Default Current Source Code (C46) system control values are set to Y, and if the customer has both a current source code and mailing history, the source code from the mailing history takes precedence and will default on the order header. Some possible scenarios that could occur when both these field are set to Y, and the resulting source code defaulting:

Scenario

Source Code Defaults From:

Select an existing customer with both a current source code and mailing history

mailing history

Select an existing customer with a current source code but no mailing history

current source code

Select an existing customer with no current source code but mailing history

mailing history

Enter a prospect finder number whose Prospect Finder file record includes a source code, but the name you enter matches an existing sold-to customer in your company; you select the existing customer record at the Display Duplicate Sold-to pop-up window

prospect finder source code

Select an existing customer with neither current source code or mailing history

no default

The current source code field is available on the second Create/Change/Display Customer screen in Work with Customers. The customer's mailing history is available in Work with Customer's by pressing F15 at one of the above screens, or entering 15 next to a customer at a scan screen. See Customer Service Chapter 27: Selecting Customers for more information.

Enter N in this field or leave it blank if you do not want the source code from the most recent mailing to the customer to default in order entry. If the Use Default Current Source Code (C46) field is set to Y, the customer's current source code, if there is one, will always default.

Current source field update: The system updates this field based on your entry in the Update of Current Source Code in Customer File (D08) system control value.

Valid values for this system control value are:

O: update current source code based on source code used in order entry

H: update current source code based on assignment through house list selection (fast path = WHLS: see Marketing Chapter 36: Working with Drops (WHLS) for more information)

N: no automatic update.

Note: You can also update the current source code through Work with Customers.

Mailing history update: The system creates mailing history records when you mail a catalog to the customer, either through the catalog requests or house list selection menu options. You must choose to update mailing history when performing the house list selection for the update to take place. See Customer Service Chapter 109: Entering Catalog Requests (WCAT) for more information on catalog requests.

Display SKU Description in place of SKU Element (F25)

Purpose: Use this screen to define whether the first 14 positions of the SKU description displays in place of the SKU elements in order entry, order maintenance and order inquiry.

MSR0052 CHANGE Change System Control Value 3/06/98 11:59:32

Description . : Display SKU Description in place of SKU Element

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . DFT

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to display the first 14 positions of the SKU description (defined in the SKU description field in Work with Item/SKUs) instead of the SKU elements in order entry, order maintenance, and order inquiry. See Merchandising Chapter 39: Introducing Split SKU Setup.

Related system control value: The setting of the Display SKU Description on Scan Order Detail Screens (J90) system control value defines whether the system displays the first 14 positions of the SKU description in place of the SKU code on the Scan Order Lines screen in order entry, order maintenance, and order inquiry.

The setting of the Display SKU Description in place of SKU Element (F25) system control value overrides the setting of the Display SKU Description on Scan Order Detail Screens (J90) system control value.

The table below indicates the SKU information that displays on screens in order entry, order maintenance, and order inquiry, based on the setting of the Display SKU Description in place of SKU Element (F25) and Display SKU Description on Scan Order Detail Screens (J90) system control values:

SCV F25

SCV J90

Results

N or blank

N or blank

The system displays the SKU code on screens in order entry, order maintenance, and order inquiry.

N or blank

Y

The system displays the first 14 positions of the SKU description in place of the SKU code on the following screens:

• In order entry: Scan Order Lines screen

• In order maintenance: Scan Order Lines screen

• In order inquiry: Scan Order Detail screen

Y

Y, N or blank

The system displays the first 14 positions of the SKU description in place of the SKU code on the following screens:

In order entry:

• Scan Order Lines screen

• Work with Order Lines screen

• Work with Order Detail screen (header/detail version of order entry only)

In order maintenance:

• Scan Order Lines screen

• Work with Order Lines screen

In order inquiry:

• Scan Order Detail screen

• Order Inquiry Detail screen

The system also displays the full 40-position SKU description on these screens:

• Create SKU Offers

• Work with SKU Generator. The SKU description displays on the Work with SKU Generator screen regardless of the setting of this system control value.

Troubleshooting: Because the system displays only the first 14 positions of the SKU description when the Display SKU Description on Scan Order Detail Screens (J90) or Display SKU Description in place of SKU Element (F25) system control value is set to Y, it may look like the system displays the SKU code and not the SKU description, depending on the text you enter in the SKU description field. For example, for item/SKU SW1010 RED WMNS SMLL, if your SKU description is RED WMNS SMLL COTTON LONG SLEEVE SWEATER, the first 14 positions of the SKU description that displays is RED WMNS SMLL, which happens to also be the SKU code.

Enter N or leave this field blank if you want the SKU elements to display on the screens mentioned above. However, if the Display SKU Description on Scan Order Detail Screens (J90) system control value is set to Y, the system displays the first 14 positions of the SKU description in place of the SKU code on the following screens:

• In order entry: Scan Order Lines screen

• In order maintenance: Scan Order Lines screen

• In order inquiry: Scan Order Detail screen

Use Computer Telephony Integration (F26)

Purpose: Use this screen to define whether you will have computer telephony integration (CTI) or the Customer Selection screen available to any users.

MSR0052 CHANGE Change System Control Value 9/23/98 8:41:27

Description . : Use Computer Telephony Integration

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . INT

Sequence# . . . 999

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you will be using CTI for order entry or customer service, or if you will be using the Customer Selection Screen without installing the CTI interface.

Note: If you have multiple companies set up, a Y setting for any company enables CTI for all the of the companies.

Customer Selection screen: The Customer Selection screen contains information about the customer's address and previous orders, and allows you to advance to a number of additional screens and options, including:

• entering a new order

• performing order or customer maintenance

• reviewing item availability

• working with catalog requests or customer notes

• reviewing daily promotions

• reviewing operator statistics

• working with call log entries (see below for more information)

You might choose to use the screen even if you do not actually have the CTI interface enabled because of the additional functionality the screen provides to order entry/customer service operators.

Setting up users: You specify the CTI features each person on your system will use through settings in the user profile. Settings include:

• receiving inbound calls

• using the Customer Selection screen as the default selection screen in order entry, or having the screen “pop” only when you receive a call from a customer

• specifying the operator's extension for incoming or transferred calls

Call log: You can create a log entry for each call activity for customers, including:

• the date and time

• whether the call was completed or if the line was busy, or if there was no answer

• comments

Additionally, you can have the system create a call log entry automatically for each call. See Update CTI Customer Call Log (F27).

Important: You must contact your MICROS representative to set up or use CTI or the Customer Selection Screen.

For more information:

• setting up users for CTI: Working with User Records (WUSR)

• CTI overview: Computer Telephony Integration Overview

Set this field to N or leave it blank if you are not using either the actual CTI interface or the Customer Selection screen, or if CTI is already selected in another company on your system.

Update CTI Customer Call Log (F27)

Purpose: Use this screen to define whether the system should create call log entries automatically for all CTI activity.

MSR0052 CHANGE Change System Control Value 9/23/98 9:53:47

Description . : Update CTI Customer Call Log

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . INT

Sequence# . . . 999

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the system create a record for each CTI call you receive. See Use Computer Telephony Integration (F26).

The system creates call log entries if the operator receives a call and then performs any action from the Customer Selection Screen before disconnecting the call. For example, if the operator inquires on an order, creates a catalog request, or reviews item availability, the system creates a call log entry. However, if the operator exits the Customer Selection Screen without performing any other action, the system does not create a call log entry automatically.

If the customer calls but the operator does not receive the call (for example, if the operator has not yet ended a previous call) then the system does not create a call log entry.

For more information:

• call log entries: Work with Customer Call Log Screen (WCLL) and Log Telephone Call Screen (Entering or Changing a Call)

• setting up users for CTI: Working with User Records (WUSR)

• CTI overview: Computer Telephony Integration Overview

Set this field to N or leave it blank if you are not using either the actual CTI interface or the Customer Selection Screen or if you do not want to create call log entries automatically for each call.

Select Telemarketing Specials by Item Category (F35)

Purpose: Use this screen to define whether to advance through item category selection windows before reaching a window that displays items or SKUs on telemarketing special.

MSR0052 CHANGE Change System Control Value 5/04/98 14:27:47

Description . : Select Telemarketing Specials by Item Category

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to select items on telemarketing special in order entry or order maintenance by item category.

Why use item category? It might be easier to select by item category if you typically have such a large number of items or SKUs on telemarketing special for a particular offer that finding the correct item or SKU at the telemarketing special pop-up window is difficult. Selecting by item category allows you to first select the category the customer wants, such as petite sizes, then review the items on telemarketing special within that category, and finally select the individual item or SKU. Item categories, which are defined in and validated against the Item Category file, are codes you use to classify items or SKUs according to product relationships or compatibilities.

When this field is set to Y, you must advance through both the Select Item Category pop-up window and the Display Telemarketing Items pop-up window before you can select an item or SKU to add to the current order.

Note: The system includes items based on the item category assigned for the telemarketing special (at the Work with Telemarketing Specials Screen or the Create Order Telemarketing Specials Screen) rather than the item category, if any, assigned in the SKU file through Performing Initial Item Entry (MITM).

Set this field to N or leave it blank if you do not want to select telemarketing specials by item category in order entry or order maintenance. You advance directly to the Telemarketing Specials pop-up window.

About telemarketing specials: Telemarketing specials are available on-demand in order entry or order maintenance by pressing F10 to advance to the Display More Options screen, then entering 1 next to Telemarketing Specials. The system also displays them automatically if the Display Telemarketing Window in Order Entry (H02) system control value is set to Y. You set up telemarketing specials at the offer level if the Display Non-Offer-Specific Telemarketing Specials in Order Entry (J31) system control value is set to N; in this case, only the telemarketing specials defined for the source code on the order header are displayed. If the Display Non-Offer-Specific Telemarketing Specials in Order Entry (J31) system control value is set to Y, then you use Working with Order Telemarketing Specials (WOTS) to set up telemarketing specials; in this case, any specials set up for a specific offer are not displayed in order entry.

For more information, see:

• setting up telemarketing specials for a specific offer: Working with Offers (WOFR)

• setting up non-offer-specific telemarketing specials: Working with Order Telemarketing Specials (WOTS)

• setting up item categories: Merchandising Chapter 4: Working with Item Category Codes (WITG)

• using telemarketing specials in order entry and order maintenance, including the effects of selecting by item category: Customer Service Chapter 144: Displaying More Options

A sample window flow for selecting a telemarketing special by item category in order entry is presented below:

Select Item Category

Offer: S98 SPRING 1998

Opt Categ Description

Type option, press Enter.

1=Select specials

KITC KITCHENWARE

PC PERSONAL COMPUTING

SUBS SUBSCRIPTIONS

5 TOYS FUN STUFF FOR KIDS

F3=Exit F8=Display all specials

Display Telemarketing Items

Offer . . . : S98

Category . : TOYS FUN STUFF FOR KIDS

Opt Page# Item Description Price

Type option, press Enter

1=Display SKUs

1 10 BU001 CHOCOLATE BUNNY 3.00

Any size chocolate rabbit at one low price

3 CR123 CREATURES CD-ROM 24.95

This is the artificial life game you have been hearing about.

3 AN678 ANGEL WINGS AND HALO 14.95

3 BE234 DACHSHUND BEAN BAG DOLL 2.50

Cute dachshund beanbag doll makes a great gift for kids

F12=Cancel

Telemarketing Specials

Offer . . . : S98

Category . : TOYS FUN STUFF FOR KIDS

Type quantities, press Enter.

Qty Page# Item CLR SIZE WDTH WAS NOW SAVE M/D%

10 BU001 CHOC SMLL 10.00 3.00 7.00 70 %

CHOCOLATE EASTER BUNNY Avl: 79

Any size chocolate rabbit at one low price

10 BU001 WHIT LRGE 10.00 3.00 7.00 70 %

CHOCOLATE EASTER BUNNY Avl: 32

Any size chocolate rabbit at one low price

10 BU001 WHIT SMLL 10.00 3.00 7.00 70 %

CHOCOLATE EASTER BUNNY Avl: 160

Any size chocolate rabbit at one low price

F12=Cancel

Telemarketing Special Price Override Reason (F36)

Purpose: Use this screen to define the price override reason code to use when adding an item on telemarketing special to an order.

MSR0051 CHANGE Change System Control Value 5/04/98 15:22:23

Description . : Telemarketing Special Price Override Reason

Code . . . . . D A B D G

X Z 1

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter the price override reason code for the system to assign to items you add to an order by selecting them at the Telemarketing Specials window.

The system adds the price override reason code only if you specify a price for the telemarketing special; however, you can set up telemarketing specials for an item without a special price, so that it will display in the telemarketing pop-up windows strictly for upselling purposes.

If you leave this field blank, the system uses the price override reason code defined in the Default Price Override Reason (B35) system control value.

For more information:

• setting up telemarketing specials: Working with Offers (WOFR) and Working with Order Telemarketing Specials (WOTS)

• using telemarketing specials in order entry and order maintenance: Order Entry Chapter 16: Displaying More Options

• setting up price override reason codes: Customer Service Chapter 2: Establishing Price Override Reason Codes (WPOR)

Display Backordered Telemarketing Special Items (F37)

Purpose: Use this screen to define whether backordered items display on the pop-up windows you use to select telemarketing specials for an order.

MSR0052 CHANGE Change System Control Value 5/11/98 10:57:15

Description . : Display Backordered Telemarketing Specials

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Set this field to Y or leave it blank to display telemarketing specials that are all items and SKUs, regardless of availability, on the pop-up windows you use to add telemarketing specials to an order.

Set this field to N to display items or SKUs only if they are currently available; however, non-inventory items are always displayed.

Note: The system does not check the item's soldout status. Items that are flagged with a soldout status of “sellout immediately” are still displayed if you have inventory available.

If you use display by item category: Setting this field to Y or blank does not prevent an item category from displaying at the Select Item Category pop-up window (first window) even if all items are backordered. Similarly, this setting does not prevent a SKU’d item from displaying at the Display Telemarketing Items window (second window) even if all SKUs are backordered. The system does not check the item's availability until it gathers detail-level information.

For more information:

• setting up telemarketing specials: Working with Offers (WOFR) and Working with Order Telemarketing Specials (WOTS)

• using telemarketing specials in order entry and order maintenance: Order Entry Chapter 16: Displaying More Options

SKU Element for Order Entry Filtering (F40)

Purpose: Use this screen to define the SKU element used to filter the matching item coordinates that display in order entry.

MSR0054 CHANGE Change System Control Value 5/11/98 11:00:54

Description . : SKU Element for Order Entry Filtering

Number . . . . 2 1 2 3

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Number field: Enter the number of the SKU element you are using to filter the display of matching item coordinates in order entry.

Overview of item coordinates: You can set up item coordinates for an item in order to cross-sell related items in order entry. For example, you could set up item coordinates of pants and a skirt to cross-sell with a blazer.

Displaying coordinates in order entry: A message displays in order entry when you add an item that is linked to one or more item coordinates. You enter 14 next to the primary item to display its coordinates. In the case of the blazer, all coordinated SKUs of the pants and the skirt will display.

How filtering works: You can use filtering to restrict the SKUs that display at the pop-up window to the ones you think the customer will be most interested in purchasing. In the case of the blazer, if the customer orders the blazer in size 10, you might filter the display to size 10 SKUs of the pants and skirt only. If you use SKU element 2 for size, you would set the system control value to 2.

Example:

Item AB100 (blazer) sold in colors NAVY, WHIT and BLCK, sizes 6, 8, 10, 12, 14

Item BB100 (skirt) in the following SKUs is coordinated to the blazer:

NAVY 6, 8, 10, 12, 14

BLCK 6, 8, 10, 12, 14

The customer the blazer in NAVY, size 10

You filter on SKU element 2, size

Result: The following coordinate SKUs of the skirt display when you order the blazer:

NAVY 10

BLCK 10

Note: Even if you use filtering, you can toggle between displaying filtered SKUs and all SKUs in order entry, to accommodate cases when the customer requests a SKU that doesn't match the filtering SKU element.

If using full (non-split) SKUs: You can use filtering even if your company uses a full 14-position SKU. In this situation, you should set this system control value to 1 in order to display only those SKUs that match the ordered item's full SKU exactly.

Example:

Item BR1000 (bracelet) is available in SILVER, MULTI and GOLD.

You have set up coordinates for Item PE1000 (pendant) in SILVER, GOLD and GLDPLATE, and Item EA1000 (earrings) in SILVER and GOLD.

The customer orders the bracelet in SILVER.

Result: When you display coordinates for the bracelet, only the silver pendant and silver earrings display. However, you can press a function key to display all coordinating SKUs, including the gold, silver, and gold plate ones.

If this field is blank: This field will not ordinarily be blank, as it is a required field. However, if this field is blank, an error message will display in order entry if you attempt to filter the item coordinates that display.

For more information:

• defining the SKU element to use for auto linking of item coordinates: Chapter 14: Setting Up Inventory Values

• assigning item coordinates: Chapter 29: Entering Additional Item Information of the Merchandising manual

• selecting item coordinates in order entry: Chapter 6: Working with Items on the Order of the Order Entry manual

Display Backordered Coordinate Sale Items (F41)

Purpose: Use this screen to define whether item coordinates that are currently backordered display in order entry.

MSR0052 CHANGE Change System Control Value 5/11/98 11:03:18

Description . : Display Backordered Coordinate Sale Items

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Overview of item coordinates: You can set up item coordinates for an item in order to cross-sell related items in order entry. For example, you could set up item coordinates of pants and a skirt to cross-sell with a blazer.

Yes/no field: Enter Y in this field or leave it blank to have backordered item coordinates display in order entry. All coordinate items related to the ordered item will display, regardless of availability.

Order entry: When you enter an order for an item that is associated with any item coordinates:

• If the Automatically Display Coordinate Items in Order Entry (I53) system control value is set to Y, the system automatically displays the Display Coordinate Items Window when you add an item associated with coordinate items to an order.

• If the Automatically Display Coordinate Items in Order Entry (I53) system control value is set to N or blank, a coordinate message displays when you add an item associated with coordinate items to an order: Coordinate items exist for base item entered. You enter 14 next to the primary item to advance to the Display Coordinate Items Window.

The system will cross-sell coordinates even if the primary item is soldout, on backorder, is a drop ship item, non-inventory item, set master item, or continuity master item. Additionally, the system will cross-sell coordinates that are a drop ship item, non-inventory item, set master item, or continuity master item.

When the system does not cross-sell coordinates: The system does not cross-sell coordinates for the primary item (by displaying the coordinate message or automatically advancing to the Display Coordinate Items window) if:

• All coordinate items are backordered or soldout and the Display Backordered Coordinate Sale Items (F41) system control value is set to N. Note: The system will cross-sell coordinates that are a drop ship item, non-inventory item, set master item, or continuity master item, regardless of the setting of the Display Backordered Coordinate Sale Items (F41) system control value.

• None of the coordinate items are included in the same offer as the primary item.

• The primary item is added to the order:

• as a result of a promotion; however, the system will cross-sell coordinates if the primary item is the item that prompts the promotion.

• as a result of an upsell; however, the system will cross-sell coordinates if the primary item is the item being upsold.

• as a coordinate item of another primary item.

• as an accompanying item; however, the system will cross-sell coordinates if the primary item is the item that prompts the accompanying item.

• as a component of a set item.

• You add the primary item to the order in order maintenance.

You can still enter 14 next to the primary item to advance to the Display Coordinate Items Window; however, if all of the coordinates are on backorder or soldout or are not included in the same offer as the primary item, there are no coordinates available to select.

Enter N or leave this field blank if you do not want backordered item coordinates to display in order entry. If the item has SKUs and all SKUs are backordered, the base item will still display on the initial pop-up window where item coordinates display; however, when the next window you advance to in order to select SKUs will be blank.

Additionally, if all item coordinates associated with the primary item are on backorder and the Display Backordered Coordinate Sale Items (F41) system control value is set to N, the system does not display the coordinate message and does not automatically advance you to the Display Coordinate Items Window.

Note: If you change the setting of this system control value, you must exit out of CWDirect and then come back in before the change takes affect.

For more information:

• item coordinates overview and setup: Working with Item Coordinates

• selecting item coordinates in order entry: Display Coordinate Items Window

Restrict Additional Charge Amount if Default Charge (F43)

Purpose: Use this screen to define whether the Amount field is enterable at the Enter Additional Charges pop-up window for an additional charge code with a default charge amount defined.

MSR0052 CHANGE Change System Control Value 6/09/98 16:49:24

Description . : Restrict Additional Charge Amount If Default Charge

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . SEC

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the Amount field not enterable for any additional charge code that has a Default charge amount specified.

The Amount field is restricted from entry at the Enter Additional Charges pop-up window only. The pop-up window is available by pressing F16 in order entry, order maintenance, or Work with Return Authorizations (streamlined version only). No other screen or window is affected.

This system control values works with the Enter Amount for Order Additional Charge Code (A80) secured feature:

• If you have authority under this secured feature, you can advance to the Change Additional Charges screen (available by entering 2 next to a additional charge at the pop-up window) and override the default.

• If you do not have authority under this secured feature, you can enter an additional charge code only if it has a default charge amount specified.

Enter N or leave this field blank to leave the Amount field unrestricted. This field will be enterable as long as you have the proper authority.

For more information:

Chapter 15: Adding Miscellaneous Charges or Credits of the Order Entry manual for more information on the Enter Additional Charges pop-up window.

Chapter 3: Establishing Additional Charge Codes (WADC) of the Customer Service manual for more information on setting up additional charge codes.

Chapter 87: Introducing Return Authorizations of the Customer Service manual for more information on working with return authorizations.

Deferred and Installment Billing (F51)

Purpose: Use this screen to set up information related to deferred and installment payment plans, such as:

• whether you wish to use deferred and installment billing

• the number of times a payment plan can be used before an order is placed on hold

• the number of days a credit card can be used before an order using a payment plan is placed on hold

• the dollar threshold for a payment plan

• whether you wish to net credits with debits for orders using a deferred or installment payment plan

MSR1000 ENTER Edit Deferred/Installment Billing 8/17/98 13:54:16

The KL Mail Order Company

Use Def/Inst Billing . . . . . . (Y/N)

Number of Times FPO used . . . . . .

Number of Days FPO used . . . . .

Dollar Threshold for FPO . .

Net Credits Def/Ins Bill . . . . (Y/N)

F3=Exit F12=Cancel

Use Deferred and Installment Billing (F51)

Purpose: Enter Y in this field if you want the ability to assign a deferred or installment payment plan to an order.

When this system control value is set to Y, the:

Pay plan field displays on the Enter Payment Method screen, Work with Order Recap screen, and Enter Credit Card pop-up window to allow an operator to assign a payment plan to the order.

• the subfile option key 8 (Pay plan summary) displays on the Enter Payment Method screen which advances you to the Display Payment Plan Summary screen

Enter N or leave this field blank if you do not want the ability to assign a deferred or installment payment plan to an order.

The Pay plan field and subfile option 8 do not display in order entry or order maintenance.

Number of Times Flexible Payment Option is Used (F52)

Purpose: Enter a number in this field to define the number of times a credit card can be used before an order using a deferred or installment payment plan is placed on PV (Pay Plan Velocity) hold.

For example, if you enter 2 in this field, the system will place an order on PV hold if the credit card has been used on more than 2 orders using a deferred or installment payment plan.

If the credit card exceeds the number defined in this system control value, the system will then look at the value defined in the Number of Days Flexible Payment Option is Used (F53) system control value to determine whether an order should be placed on PV hold.

Enter 0 or leave this field blank if you do not want the system to place an order using a deferred or installment payment plan on PV hold.

Number of Days Flexible Payment Option is Used (F53)

Purpose: Enter a number in this field to define the number of days a credit card can be used before an order using a deferred or installment payment plan is placed on PV (Pay Plan Velocity) hold.

The system only determines the number of days a credit card can be used before its next use on an order using a deferred or installment payment plan if the credit card exceeded the value defined in the Number of Times Flexible Payment Option is Used (F52) system control value.

For example, if you entered 2 in the Number of Times Flexible Payment Option is Used system control value and the credit card was used on more than 2 orders using a deferred or installment payment plan, the system would then determine the last day the credit card was used. If you entered 5 in the Number of Days Flexible Payment Option is Used system control value, the system would place the order on PV hold if the credit card was used on more than 2 orders using a deferred or installment payment plan and the credit card was used less than 5 days ago.

Leave this field blank if you do not want the system to place an order using a deferred or installment payment plan on PV hold based on the number of days between each use of the credit card. The system will still place an order using a payment plan on PV hold if the order meets the number defined in the Number of Times Flexible Payment Option is Used (F52) system control value.

Dollar Threshold for Sold To Customer Orders with Flexible Payments (F54)

Enter the dollar amount you wish to system to use to determine whether an order using a deferred or installment payment plan should be placed on hold. If the total dollar amount outstanding for a sold to customer exceeds the amount defined, the system places all future orders for the customer sold to on P$ (Pay Plan Dollar Threshold) hold.

The system uses the following calculation to determine the total dollar amount outstanding for a sold to customer for orders using a deferred or installment payment plan:

 

balance open amount + open invoice amount = total outstanding dollar amount

 

Leave this field blank if you do not want the system to place orders using a payment plan on hold when the total dollar amount for the sold to customer exceeds the dollar threshold.

Net Credit Card Credits for Deferred and Installment Billing (F55)

Purpose: Enter Y in this field if you wish to net credit invoices with debit invoices before a deposit is sent to the service bureau for an invoice associated with a deferred or installment payment plan.

Netting Credit Card Credits for Deferred Billing:

When you net credit card credits for deferred billing, the system subtracts the credit invoice from the debit invoice and only sends the debit invoice to the service bureau for deposit.

Example:

Debit invoice = 69.00

 

Credit invoice = 31.50

 

The system subtracts the credit invoice from the debit invoice to determine the remaining amount to deposit: 69.00 - 31.50 = 37.50 (this is the new amount to deposit).

 

When you send the debit invoice of 37.50 to the service bureau for deposit, the system:

updates the deposit release date for both the debit invoice and the credit invoice with the date the debit invoice was deposited

updates the amount remaining to deposit for the credit invoice to 0.00

updates the amount deposited for the debit invoice to 37.50

writes a deposit history record for the debit invoice only

Netting Credit Card Credits for Installment Billing:

When you net credit card credits for installment billing, the system subtracts the credit invoice amount from the debit invoice amount. The system then divides the remaining amount to deposit for the debit invoice by the number of remaining installments to determine the amount due for each installment.

Example:

Debit invoice = 69.00

Number of installments = 3

Installment amount = 23.00

Credit invoice = 31.50

The system subtracts the credit invoice from the debit invoice to determine the remaining amount to deposit: 69.00 - 31.50 = 37.50 (this is the new amount to deposit).

The system then divides the remaining amount to deposit by the number of installments remaining to determine the installment amount: 37.50 / 3 = 12.50 (this is the amount for each installment)

 

When you send an installment amount to the service bureau for deposit, the system:

• updates the deposit release date for both the debit invoice and the credit invoice with the date of the next installment

• updates the amount remaining for the credit invoice to 0.00

• updates the amount deposited for the debit invoice to 12.50 (the amount of the first installment)

• updates the amount remaining to deposit for the debit invoice to 25.00 (37.50 - 12.50)

• updates the installment amount for the installments remaining to deposit to 12.50

writes a deposit history record for the debit invoice only

The following table explains the updates the system performs for invoices associated with a deferred or installment payment plan when you net credits and when you do not net credits.

Type of Pay Plan

Net Credits?

Result

deferred

N

The credit has a deposit release date that is the same date as the debit. The credit deposit is eligible for processing after the purchase deposit is processed.

Example:

• Ship an order on 8/1 for $100 with a deposit release date of 9/1

• Process return on 8/15 for $60: credit is for $60 and has a deposit release date of 9/1

• Process Deposits processes the credit of $60 after the debit of $100 is deposited

deferred

Y

The credit has a deposit release date that is the same date as the debit. When you process deposits, the net amount of the deposit only is processed.

Example:

• Ship an order on 8/1 for $100 with a deposit release date of 9/1

• Process return on 8/15 for $60: credit is for $60 and has a deposit release date of 9/1

• Process Deposits processes a deposit of $40 ($100 - $60)

installment

N

The credit has a deposit release date that is the same as the date you created it; however, the credit deposit is eligible for processing after the total debit deposits meet or exceed the credit invoice amount.

Example:

• Ship an order on 8/1 for $100 with 4 installments of $25, deposit release dates of 9/1, 10/1, 11/1, and 12/1

• Process first installment deposit on 9/1 for $25

• Process second installment deposit on 10/1 (total amount deposited now $50)

• Process third installment deposit on 11/1 (total amount deposited now $75)

• Process Deposits processes the credit of $60

installment

Y

The credit has a deposit release date that is the same as the date you created it. When you process deposits, the remaining installment amounts are reduced by the total credit amount.

Example:

• Ship an order on 8/1 for $100 with 4 installments of $25, deposit release dates of 9/1, 10/1, 11/1, and 12/1

• Process first installment deposit on 9/1 for $25

• Process return on 9/15 for $60: credit is for $60 and has a deposit release date of 9/15

• When you next process deposits, the amount of each remaining installment is reduced by $5 ($75 remaining installments - $60 credit = $15 / 3 installments = $5)

Enter N or leave this field blank if you do not wish to net credit invoices with debit invoices before a deposit is sent to the service bureau for an invoice associated with a deferred or installment payment plan.

For invoices associated with a deferred payment plan, the system processes the credit invoice after the debit invoice has been deposited to ensure the customer does not receive a credit before the credit card has been charged.

For invoices associated with an installment payment plan, the system processes the credit invoice once the debit invoice amount deposited is equal to or greater than the credit invoice amount.

For more information:

Chapter 4: Establishing Order Hold Reason Codes (WOHR) of the Customer Service manual for more information on order hold reason codes.

Chapter 65: Deferred/Installment Billing Overview of the System Operations manual for more information on payment plans.

Chapter 68: Processing Auto Deposits (SDEP) of the System Operations manual for more information on deposits.

Retail Order Defaults (F59)

Purpose: Use this screen to define whether the system defaults a retail warehouse and location to the Enter Location pop-up window for an order using an express bill ship via.

MSR0052 CHANGE Change System Control Value 9/15/98 12:17:18

Description . : Retail Order Defaults

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 1

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to default a retail warehouse and location to the Enter Location pop-up window for an order using an express bill ship via.

To default the warehouse: The system looks at the order type defined for the order and defaults the warehouse defined in the Retail warehouse field. If a warehouse has not been defined in the Order Type file, the system defaults the warehouse defined in the Primary warehouse field in the Item file.

To default the location: This table explains how the system defaults a location to the Location field on the Enter Location pop-up window, based on where the warehouse defaulted from.

If the warehouse defaults from...

Then the Location defaults from...

The warehouse defaults from the Retail warehouse field in the Order Type file

The location defaults from the Auto restock location field defined in the Warehouse file for the warehouse that defaulted

The warehouse defaults from the Primary warehouse field in the Item file

The location defaults from the Primary location field in the Item file

The operator manually entered a warehouse

The location defaults from the Auto restock location field defined in the Warehouse file for the warehouse that was manually entered

Note: If a location has not been defined in either the Auto restock location field in the Warehouse file or the Primary location field in the Item file, you must manually enter a location.

Enter N or leave this field blank if you do not want the system to default a retail warehouse and location to the Enter Location pop-up window for an order using an express bill ship via.

The system defaults the warehouse and location defined for the item to the Warehouse and Location fields on the Enter Location pop-up window. If a location has not been defined in the Item file, you must manually enter a location.

Recalculate Freight Default (F62)

Purpose: Use this screen to define the default setting of the Recalculate freight field in order maintenance, and for when you process backorder cancellations or item substitutions.

MSR0052 CHANGE Change System Control Value 4/28/00 16:52:00

Description . : Recalculate Freight Default

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . FRT

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Your entry in this field defaults when you:

• cancel an item through order maintenance, Working with Backorders Pending Cancellation (WBPC), or Processing Item Substitutions (PSUB)

• increase or decrease the quantity of an item in order maintenance

• sell out an item in order maintenance

If you leave this field blank, no value defaults as described above. You can override the default in each case.

The system always recalculates freight when you sell out an item through Processing Auto Soldout Cancellations (MASO).

For more information: See Customer Service Part E: Performing Order Maintenance.

Sort Source Codes Prompt by Description in Order Entry (F67)

Purpose: Use this screen to define whether the system displays source codes alphanumerically by source code description on the Select Source screen in order entry.

MSR0052 CHANGE Change System Control Value 12/01/98 10:52:29

Description . : Sort Source Codes prompt by description in OE Y/N

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to display source codes alphanumerically by source code description instead of by source code on the Select Source screen in order entry.

The system advances you to the Select Source screen when you prompt on the Source field on the Select Customer Sold To for Order screen or on the Work with Order screen in order entry.

The Select Source screen displays different information depending on whether you prompted on the Source field from the Select Customer Sold To for Order screen or from the Work with Order screen. A sample of the Select Source screen from the Select Customer Sold To for Order screen and from the Work with Order screen is displayed below.

Sample screen: A sample of the Select Source screen that you advance to when you prompt on the Source field from the Select Customer Sold To for Order screen is displayed below.

This screen displays source codes for all companies that have cross-company scanning enabled. The screen displays the source code, source code description, company where the source code is located, offer, and offer description. If the Sort Source Codes Prompt by Description in Order Entry system control value is set to Y, the system sorts the source codes by source code description, instead of by source code, as shown in the sample below.

OER0800 SELECT Select Source 12/01/98 11:07:34

Opt Source Description Cmp Ofr Description

1=Select

ALL10 ALL CUSTOMERS 555 BBQ BACKYARD SUMMER BARBEQUE

ALASKA ALASKA RESIDENTS 555 RAT NEW YEAR SPECIALS

1TIME FIRST TIME BUYERS 555 bbq NEW YEAR SPECIALS

STFL FLORIDA RESIDENTS 555 BBQ BACKYARD SUMMER BARBEQUE

STME9 MAINE RESIDENTS 555 BBQ BACKYARD SUMMER BARBEQUE

ABC1234 NEW HAMPSHIRE RESIDENTS 242 1 SUMMER DISCOUNTS

AUTOSEL NEW MAILING 395 002 OFFER 2 FOR SPRING

A123 PREMIUM BUYERS 1 1 WINTER 98

A123 RENTED LIST BUYERS 242 A01 SUMMER/FALL CATALOG

A123 SOURCE CODE FOR CLASS 395 001 FALL BOOK

A123 TMG MODS 555 001 FALL BOOK

B1 UPSELL PROMOTION 242 B01 BROOKS OFFER

CAN 0-6 MONTH BUYERS 555 CAN CANADIAN OFFER +

F3=Exit F6=Create

Sample screen: A sample of the Select Source screen that you advance to when you prompt on the Source field from the Work with Order screen is displayed below.

This screen displays the source code and the source code description. If the Sort Source Codes Prompt by Description in Order Entry system control value is set to Y, the system sorts the source codes by source code description, instead of by source code, as shown in the sample below.

MSR0430 SELECT Select Source 12/01/98 11:26:53

Opt Source Description

1=Select

ALL867 ALL CUSTOMERS

ST9876 BARGAIN BUYERS

87CAN CANADIAN BUYERS

AUTO COMPANY AUTO SELECT SOURCE

87YHG DISCOUNT BUYERS

A123 EMPLOYEE

B FIRST TIME BUYER

BBQ FALL SOURCE CODE FOR BBQ CATALOG

CAN GUARANTEED BUYER

BCY SOURCE CODE FOR JOY CATALOG

JAW SOURCE CODE FOR MAW CATALOG

9AT SOURCE CODE FOR RAT OFFER

RIVER100 RHODE ISLAND RESIDENTS +

F3=Exit F6=Create

Enter N or leave this field blank if you do not want the system to display source codes alphanumerically by source code description on the Select Source screen in order entry. Instead, the system displays source codes alphanumerically by source code on the Select Source screen in order entry.

Source codes are defined through the Working with Source Codes (WSRC) menu option.

Pass Entity Code to Vertex (F69)

Purpose: Use this screen to define whether the system passes the entity code defined for the division that is associated with the source code on the order to the Vertex Interface.

MSR0052 CHANGE Change System Control Value 10/19/98 8:31:43

Description . : Pass Entity Code to Vertex

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . TAX

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to pass the entity code defined for the division that is associated with the source code on the order to the Vertex Interface.

The Vertex Interface provides a bridge between CWDirect and the Vertex Sales Tax Compliance System to calculate the tax information on orders during order entry, order maintenance, pick slip generation, and billing.

If this system control value is set to Y, the system determines whether tax is charged to the order based on the entity associated with the order.

See Order Entry Chapter 44: CWDirect/Vertex Interface for more information on the Vertex Interface.

In order to pass the entity code to Vertex, you must have the Vertex Interface (A88) system control value set to Y and the Vertex Tax Method (A89) system control value set to CITY/ST/ZP.

Note: This system control value must be set to Y in order to have the Tax API include the Tax API Default Entity (L67) when requesting tax information without an order. You might use the Tax API to request a tax quote before creating the order in CWDirect, such as when you are in the process of creating the order on your web storefront. See the Tax API Default Entity (L67) system control value for more information.

Enter N or leave this field blank if you do not want the system to pass the entity code defined for the division that is associated with the source code on the order to the Vertex Interface.

If this system control value is set to N or blank, the system does not determine whether tax is charged to the order based on the entity associated with the order; instead the system determines whether tax is charged to an order based on the value defined in the Vertex Tax Method (A89) system control value.

Phone Interface Values (F70)

Purpose: Use this screen to work with settings related to the phone order interface.

MSR1033 ENTER Edit Phone Interface Values 2/24/03 10:24:53

EZK Mail Order

Phone load method HERRSCHNER (TAPE, COMM, EMERY, HERRSCHNER)

Tape drive . . . TAP01

Tape record length . 1035

Default order type . . . P PHONE ORDERS

Allow price overrides . . N (Y/N)

Duplicate Customer Checking

Exact match on:

First name . . . . . . . N (Y/N)

Last name . . . . . . . . N (Y/N)

Company Name . . . . . . N (Y/N)

Street address . . . . . N (Y/N)

Address line 2 . . . . . N (Y/N)

Apartment . . . . . . . . N (Y/N)

City . . . . . . . . . . N (Y/N)

State . . . . . . . . . . N (Y/N)

Email Address . . . . . . N (Y/N)

F3=Exit F12=Cancel

Phone Load Method (C97)

Purpose: Enter the code for the method by which you will receive orders on CWDirect that were taken by an outside service (such as a call center). You can load these orders onto the system from tape or through data communications. You must specify a method in this field if you use the phone interface. This is a 4-position, alphanumeric field.

Valid values for this field are:

TAPE: You receive a tape from your off-site Order Entry service. This tape provides the Phone Orders file (PHORDS). Simply mount the tape onto the appropriate tape drive (identified in the Tape drive for loading phone orders field) and run the loading program (fast path = IPHO) to create regular order files.

COMM: The service transmits the Phone Orders file to you electronically.

HERRSCHNER: You receive the Phone Order Expanded file (PHORDE). You can use the Transfer Phone Order menu option (fast path = TPHO) to convert this file to the Phone Orders file format, then proceed with phone orders processing.

EMERY: You receive the Phone Transmit file (PHXMIT). You can use Input Phone Orders menu option (fast path = IPHO) to convert this file to the Phone Orders file format, then proceed with phone orders processing.

Note: This system control value is also listed independently on additional screens as Use Tape or Communication for Loading Phone Orders.

Default Order Type (C93)

Purpose: Enter the code for the order type assigned to all orders received through the phone interface. The phone interface is used to load orders onto the system that were taken by a third party (such as a call center). An entry to this field is required. This is a 1-position alphanumeric field.

The order type code identifies the method by which the order was received. Some common order types are phone, mail, or fax. The system captures the order's original order type so that you can always identify how an order was received and obtain statistics for each order type.

Note: If an order received through the phone interface contains an order type code in the Order type field, the system uses the order type already defined for the order instead of defaulting the order type defined in this system control value. The order type defined for the order passes to the Order type field on the order header.

Valid order types display to the right of the entry field. Order types are defined in and validated against the Order Type file. See Customer Service Chapter 1: Establishing Order Types (WOTY), for more information.

Note: This system control value is also listed independently on additional screens as Default Order Type for Phone Interface.

Tape Drive (C98)

Purpose: Enter the name of the tape drive, as defined on the iSeries, on which you will mount the tape and load orders onto the system. This is a 10-position, alphanumeric field. You must complete this field if you entered TAPE in the Phone Load Method field.

When you select the Input Phone Orders from Tape/Comm option (IPHO) and your method is TAPE, the system will read the tape on the specified tape drive.

Note: This system control value is also listed independently on additional screens as Tape Drive for Loading Phone Orders.

Tape Record Length (C99)

Purpose: Enter the number for the length of a single record on the phone interface tape. This enables the system to verify that you are loading the correct file. A record typically contains order information plus header and trailer information that identify the beginning and end of a record.

This is a 7-position, alphanumeric field. You must complete this field if you entered TAPE in the Phone Load Method field.

Note: This system control value is also listed independently on additional screens as Record Length for Phone Input Tape.

Allow Price Overrides (D71)

Purpose: Enter Y in this field if you want to use the item price on the order without changing it. This may be useful if you are using the phone interface to record sales that have already taken place at a retail outlet.

Enter N or leave this field blank if you want the system to reprice items on phone orders (loaded through the phone interface) using the pricing method defined for the source code on the order. This may be useful if you are using a remote order entry service to take your orders, which you then fulfill through your own order processing. See Marketing Chapter 6: Working with Source Codes (WSRC)

Note: This system control value is also listed independently on additional screens as Allow Pricing in Phone Order Load.

Duplicate Checking for Customers (F71-F77, H88 and I11)

Purpose: Set each of the following fields to N if a customer record you receive through the phone interface 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.

For example, you receive a phone 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 set the Exact Match on First Name fieldto N, the system considers the two customer records a match and uses customer # 30303 to build the order files.

Note: The system also uses these system control values for matching customer records when you process orders through the e-commerce interface. See System Operations Chapter 87: E-Commerce Setup for more information.

Set each of the following fields to Y if a customer record you receive through the phone interface should be treated as a match to an existing customer only if the particular field matches exactly.

In the above example, you would not use customer # 30303 to build the order files; instead, the system would treat the customer information received through the phone interface as a new customer if even one character of the customer's first name is different.

Code

System Control Value

F71

Exact Match Required on First Name for Phone Interface

F72

Exact Match Required on Last Name for Phone Interface

H88

Exact Match Required on Company for Phone Interface

F73

Exact Match Required on Street Address for Phone Interface

F74

Exact Match Required on Apartment for Phone Interface

F75

Exact Match Required on Address Line 2 for Phone Interface

F76

Exact Match Required on City for Phone Interface

F77

Exact Match Required on State for Phone Interface

I11

Exact Match Required on Email Address

For more information:

• Order Entry Chapter 31: Using the Phone Interface for more information on using the phone interface to load remote orders

• Marketing Chapter 6: Working with Source Codes (WSRC) for more information on defining a pricing method for a source code

• Customer Service Chapter 19: Setting Up Match Codes (MMCH) for more information on match codes

Include Spaces in Special Handling Edit for Maximum Characters (F80)

Purpose: Use this screen to define whether spaces are included in the edit the system performs to determine the maximum number of characters allowed for a custom special handling line.

MSR0052 CHANGE Change System Control Value 1/20/99 14:40:07

Description . : Include spaces in S/H edit for maximum characters

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to include spaces in the edit the system performs to determine the maximum number of characters allowed for a custom special handling line.

For example, the custom special handling line for first name is defined with 10 as the maximum number of characters allowed. If the Include Spaces in Special Handling Edit for Maximum Characters system control value is set to Y, and the operator enters Julie Marie in this field, the system considers this name to be 11 characters and displays the error message:

 

Exceeds Maximum Characters Allowed.

 

Enter N or leave this field blank if you do not want to include spaces in the edit the system performs to determine the maximum number of characters allowed for a custom special handling line.

For example, the custom special handling line for first name is defined with 10 as the maximum number of characters allowed. If the Include Spaces in Special Handling Edit for Maximum Characters system control value is set to N or blank, and the operator enters Julie Marie in this field, the system considers this name to be 10 characters and an error message does not display.

See Customer Service Chapter 9: Establishing Custom Special Handling Formats (WSHF) for more information on setting up a custom special handling template.

See Order Entry Chapter 6: Working with Items on the Order for more information on entering an item with custom special handling on an order.

Display Entity Description (F84)

Purpose: Use this screen to define whether to display the entity description on the CTI Customer Selection screen and in order inquiry.

MSR0052 CHANGE Change System Control Value 11/17/98 16:11:21

Description . : Display Entity Description

Yes/No . . . . Y (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to display the first five positions of the entity description on the CTI Customer Selection screen, and the first 20 positions on the order inquiry header and detail screens. On the order inquiry screens, the entity is in reverse video.

Enter N or leave this field blank to omit the entity description from the screens.

See Order Entry Chapter 3: Selecting Customers for information on selecting an order through the CTI Customer Selection screen.

Update Original Source Code for Recipient Customers (F90)

Purpose: Use this screen to define whether the system writes the source code defined for the sold to customer to the Original source field for a recipient customer.

MSR0052 CHANGE Change System Control Value 11/10/98 14:58:27

Description . : Update Original Source Code for Recipient Customers

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 999

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to write the source code defined for the sold to customer to the Original source field for a recipient customer.

If a source code already exists in this field, the system retains the existing code.

Enter N or leave this field blank if you do not want the system to write the source code defined for the sold to customer to the Original source field for a recipient customer.

For more information: See Customer ServiceChapter 72: Adding a Recipient Order.

Position Cursor on Offer Field in OE/OM (F91)

Purpose: Use this screen to define whether to position the cursor to a blank offer field when you are adding an item in order entry or order maintenance.

MSR0052 CHANGE Change System Control Value 10/01/98 9:15:35

Description . : Position Cursor on Offer field in OE/OM

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . DFT

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the Offer field blank, with the cursor positioned in that field, when you are adding an item in order entry or order maintenance. In this way, the operator is required to specify the offer to use for pricing the item and to track demand.

Important: This field does not control the Offer field in the header/detail version of order entry.

You might set this field to Y if you typically take orders from multiple offers, and want to make sure that you are tracking sales to, or deriving prices from, the actual offers where the customer selects items.

Note: The cursor position and blank offer field take place on the following screens only:

• Work with Order Lines: header version of order entry only, both full-screen entry and regular formats

• Work with Order Line: available by pressing F6 to display this screen in order entry

Both order entry and order maintenance use the alternate cursor position and blank offer. This field does not affect the Offer field in the header/detail or the alternate address versions of order entry.

Enter N in this field or leave it blank to have the offer associated with the source code on the order header default to the order detail line. The cursor will be positioned in the item field.

Maximum Warranty Order Amount (F97)

Purpose: Use this screen to define the maximum dollar amount allowed for warranty items on an order before the order is placed on hold.

MSR0056 CHANGE Change System Control Value 2/18/99 10:21:14

Description . : Maximum Warranty Order Amount

Dollar amount .

Narrative . . .

Application . : O/E

Applic group . FRD

Sequence# . . . 10

F3=Exit F12=Cancel

Dollar amount field: Enter the maximum dollar amount allowed for warranty items on an order in order entry or order maintenance before the order is placed on hold.

If the dollar amount for warranty items on an order exceeds the maximum warranty order amount defined, the system places the order on warranty order hold (WO).

Since a warranty item is added to an order at no charge, the system uses the cost defined in the Costing Method (A25) system control value to determine the dollar amount of a warranty item on an order. If you are using FIFO costing, the system uses the weighted average cost. If the cost was overridden on the order detail line, the system uses the cost override.

Example

Maximum Warranty Order Amount: 30.00

warranty item 1: 20.00

warranty item 2: 15.00

If an operator entered warranty item 1 and warranty item 2 to an order, the total cost for the warranty items would equal 35.00 (20.00 + 15.00 = 35.00). Since 35.00 dollars exceeds the maximum warranty order amount, the system would place this order on warranty order hold.

If the operator overrode the cost of warranty item 1 to 10.00, the total cost for the warranty items would equal 25.00 (10.00 + 15.00 = 25.00). Since 25.00 dollars does not exceed the maximum warranty order amount, the system would not place this order on warranty order hold.

See Customer Service Chapter 43: Working with Customer Warranty Information (WCST) for more information on warranty items.

Leave this field blank if you do not want to define a maximum dollar amount allowed for warranty items on an order.

Maximum Life to Date Warranty Amount for Customer (F98)

Purpose: Use this screen to define the maximum life to date warranty dollar amount allowed for a customer before an order for the customer that includes warranty items is placed on hold.

MSR0056 CHANGE Change System Control Value 2/18/99 10:56:09

Description . : Maximum LTD Warranty Amount for Customer

Dollar amount .

Narrative . . .

Application . : O/E

Applic group . FRD

Sequence# . . . 20

F3=Exit F12=Cancel

Dollar amount field: Enter the maximum life to date warranty dollar amount allowed for a customer before orders for the customer that includes warranty items are placed on warranty customer hold (WC).

The system determines the life to date warranty dollar amount for a sold to customer using the following calculation:

 

warranty dollars shipped - warranty dollars returned = life to date warranty dollar amount

 

If the existing life to date warranty dollar amount for the sold to customer plus the dollar amount of the warranty items on the order exceeds the maximum life to date warranty dollar amount defined, the system places orders that include warranty items on warranty customer hold (WC).

Note: The system does not consider open orders that include warranty items for this sold to customer in the life to date warranty calculation.

Example

Maximum life to date warranty for a customer: 100.00

current life to date warranty dollar amount: 60.00

dollar amount of warranty items on order: 50.00

In this example, if the current life to date warranty amount for this sold to customer is 60.00, and an operator entered an order for this sold to customer that contained warranty items whose dollar amount equaled 50.00, the system would place the order on warranty customer hold since the life to date warranty amount now equaled 110.00 (60.00 + 50.00 = 110.00).

Leave this field blank if you do not want to define a maximum life to date warranty amount for a sold to customer.

See Customer Service Chapter 43: Working with Customer Warranty Information (WCST) for more information on warranty items.

Default Price Override Reason for Warranty Items (G01)

Purpose: Use this screen to define the price override reason code the system defaults to an order detail line when an operator adds a warranty item to an order in order entry or order maintenance.

MSR0051 CHANGE Change System Control Value 2/18/99 9:32:39

Description . : Default price Override Reason for Warranty Items

Code . . . . . A C E F

G P W

Narrative . . .

Application . : O/E

Applic group . DFT

Sequence# . . . 70

F3=Exit F12=Cancel

Code field: Enter the price override reason code you want the system to default to the Price override code field on the order detail line when an operator adds a warranty item to an order in order entry or order maintenance.

Warranty items are items added to an order at no charge, for example, if the burner to a grill a customer previously bought was recalled, you could add the replacement burner to the order at no charge. You can define an item as a warranty item by setting the Warranty field in the item offer or SKU offer to Y. If the item or SKU in the offer on the order detail line is defined as a warranty item, the system adds the item to the order free of charge. See Customer Service Chapter 43: Working with Customer Warranty Information (WCST) for more information on warranty items.

Note: If the operator does not have authority to the Price Overrides (A23) secured feature, an error message similar to the following displays when the operator tries to add a warranty item to an order:

 

Not authorized to perform price override.

 

Leave this field blank if you do not want the system to default a price override reason code to the Price override code field on the order detail line when an operator adds a warranty item to an order in order entry or order maintenance.

When an operator adds a warranty item to an order, the system highlights the Price override code field and the operator must manually enter a price override code.

Customer Class for User Defined Field Prompting (G04)

Purpose: Use this screen to define the customer class to which user-defined field prompting in order entry is restricted.

MSR0051 CHANGE Change System Control Value 2/09/99 12:34:42

Description . : Customer Class for User Defined Field Prompting

Code . . . . .

Narrative . . .

Application . : O/E

Applic group . CST

Sequence# . . . 35

F3=Exit F12=Cancel

Code field: Enter the code representing the customer class to be prompted for user-defined field information in order entry. The customer class is a two-position numeric field. See Customer Service Chapter 17: Setting Up the Customer Class File (WCCL).

Leave this field blank to prompt for user-defined field information regardless of customer class.

For more information: The system uses this system control value together with the User-defined Field Prompting for Existing Customers (D33) system control value to determine when to prompt for new and existing customers.

Include Weight of all Items in Freight by Order Weight (G05)

Purpose: Use this screen to define whether the system adds together the weight of all non-ship alone items and ship alone items, regardless of the item's shipper or arrival date in the freight by order weight calculation.

MSR0052 CHANGE Change System Control Value 1/05/99 9:33:47

Description . : Include weight of all items in Freight by Order weight

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . FRT

Sequence# . . . 45

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to add together the weight of all non-ship alone items and ship alone items, regardless of the item's shipper or arrival date in the freight by order weight calculation.

Calculation: The system uses the following steps below in calculating freight by order weight when the Include Weight of all Items in Freight by Order Weight system control value is set to Y.

1. Each time a user enters an item on the order, the system adds together the weight of all non-ship alone items and ship alone items, regardless of the item's shipper or arrival date. Freight-exempt items (as defined through the Working with Weight Tables for Order Weight (WFTB) menu option) are excluded if the Use Item Freight Exemption File (E73) system control value is set to Y.

 

Example: An order contains the following non-ship alone items and ship alone items with different shippers and different arrival dates:

Item

Weight

Quantity

Ship Via

Arrival Date

Total Weight

ship alone

10 lbs.

1

1

1/15

10 lbs.

non-ship alone

15 lbs.

2

2

1/15

30 lbs.

ship alone

20 lbs.

2

1

1/30

40 lbs.

 

 

 

 

Total

80 lbs.

2. The system determines how many pounds to allocate to each carton, based on the Maximum carton weight defined for the ship via on the order and the value defined in the Extra Weight for Order Weight Freight Method (D85) system control value. If more than one ship via has been defined on the order, the system uses the ship via defined on the order header.

Example:

Maximum carton weight = 30 lbs.

Extra carton weight = 1 lb.

Pounds to allocate per carton = 29 lbs. (30 - 1)

3. The system then determines how many cartons the items would require to ship.

Note: The actual number of cartons you use to ship these items may differ; these calculations are used for assigning the freight amount to the order only.

Example:

80 lbs. (step 1) divided by 29 lbs. (step 2) = 2 full cartons with a remainder of 22 lbs. in a partial carton

4. The system then consults the freight table for each full carton, and the final, partial carton, adding the freight amount from the table defined for that weight to the order for each carton. The system includes the extra weight defined in the Extra Weight for Order Weight Freight Method (D85) system control value in each carton weight.

Note: In order to assign a freight amount to the order, the system must find a record on the freight table with the correct ship via, business/residence flag, shipping zone and weight.

Example:

the freight table contains the following matching records:

 

Weight

Freight Amount

10 lbs.

$5.00

15 lbs.

$6.00

20 lbs.

$7.00

25 lbs.

$8.00

30 lbs.

$9.00

 

the system adds the following freight amounts to the order:

first carton (30 lbs.) = $9.00

second carton (30 lbs.) = $9.00

third carton (22 + 1 lbs.) = $8.00

Total freight = $26.00

Enter N or leave this field blank if you want the system to add together the weight of all non-ship alone items that have the same shipper and arrival date in the freight by order weight calculation. The system calculates freight on ship-alone items separately.

For more information: See Fulfillment Chapter 41: Working with Weight Tables for Order Weight (WFTB) for an overview.

Price Override Reason for Business to Business Orders (G08)

Purpose: Use this screen to define the price override reason code the system assigns to each order detail line on a business to business order.

MSR0051 CHANGE Change System Control Value 4/08/99 11:19:44

Description . : Price Override Reason for B2B Orders

Code . . . . . B A B C E

F G P W

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter the price override reason code you wish the system to assign to each order detail line on a business to business order.

If the system assigns a price override reason code to each order detail line on a business to business order, the system does not reprice the order line when the business to business order is processed through the phone interface. Instead, the order detail line keeps the price that was entered in business to business order entry.

You can view the price override reason code the system assigns to each order detail line in order maintenance and order inquiry.

If you manually assign a price override reason code to a business to business order detail line, the system uses this price override reason code and does not default the code defined in the Price Override Reason for Business to Business Orders system control value.

Leave this field blank if you do not want the system to assign a price override reason code to each order detail line on a business to business order.

If the system does not assign a price override reason code to each order detail line on a business to business order, the system may reprice the order line when the business to business order is processed through the phone interface.

If you manually assign a price override reason code to a business to business order detail line, the system will not reprice the order line when the business to business order is processed through the phone interface.

For more information:

• Customer Service Chapter 2: Establishing Price Override Reason Codes (WPOR).

• Order Entry Chapter 40: Working with Business to Business Order Entry Overrides

Batch for Business to Business Orders in Error (G09)

Purpose: Use this screen to define the order batch number the system assigns to each business to business order that contains errors.

MSR0054 CHANGE Change System Control Value 4/08/99 11:30:36

Description . : Batch for B2B Orders in Error

Number . . . . 555

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Number field: Enter the order batch number you wish the system to assign to each business to business order that contains errors.

If a business to business order contains errors, the system lists the order on the Business to Business Order Error Listing. You can then correct the order in Batch Order Entry by working with the orders assigned to the order batch number you have defined.

Leave this field blank if you do not wish the system to assign each business to business order that contains errors to an order batch number.

If a business to business order contains any errors, the system assigns the order to a blank (0) batch number in Batch Order Entry.

See Order Entry Chapter 39: Entering a Business to Business Order for more information.

Job Description for Business to Business Order Generation (G13)

Purpose: Use this screen to define the job description the system uses when a business to business order is processed through the B2B_GEN batch job.

MSR0051 CHANGE Change System Control Value 4/08/99 11:38:08

Description . : Job Description for B2B Order Generation

Code . . . . .

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter the job description you wish the system to use when a business to business order is processed through the B2B_GEN batch job.

You can assign the B2B_GEN batch job to a job description other than the job description used for your daily processing so that business to business orders can process separately from other daily processes.

The system processes a business to business order through the B2B_GEN batch job when you press F9 to accept the order in Business to Business Order Entry. See Order Entry Chapter 39: Entering a Business to Business Order for more information.

Leave this field blank if you wish the system to use the default job description stored in your user profile.

Check Interface Payment Type (G26)

Purpose: Use this screen to define the pay type code the system identifies as the check interface payment type.

MSR0054 CHANGE Change System Control Value 4/30/99 11:56:42

Description . : Check Interface Payment Type

Number . . . . 01 11 31 36

Narrative . . .

Application . : O/E

Applic group . PAY

Sequence# . . . 10

F3=Exit F12=Cancel

Number field: Enter a valid pay type code in this field to identify the pay type code the system identifies as the check interface payment type.

You can download any orders that contain the check interface payment method to the Western Union Download file by running the PFR0043 periodic function. This periodic function downloads any orders that contain the check interface payment method and have a blank check interface download date. The Western Union Download file allows you to send check information to an outside service for verification.

When you add the check interface payment method to an order, the system:

• requires entry of the Check number, Checking account number, and Routing number fields on the Enter Payment Method screen or the Enter Cash Control pop-up window in order entry and order maintenance.

• does not allow you to define a dollar amount for the payment method. If you try to enter a dollar amount, the system displays an error message similar to the following:

 

A check amount cannot be entered prior to check interface download processing.

 

• does not allow you to enter a credit card, A/R, or C.O.D. payment method to the order since you cannot define two payment methods on an order that have a blank dollar amount. If you try to add a credit card or A/R payment method to the order the system displays an error message similar to the following:

 

Only one catch-all pay type may be entered.

 

• places the order on CI (check interface) hold.

• adds an additional charge to the order if an additional charge code has been defined in the Check Interface Additional Charge Code (G27) system control value.

Leave this field blank if you do not want to identify a pay type code as the check interface payment type.

For more information: See Accounts Payable Chapter 5: Working with Pay Types (WPAY).

Check Interface Additional Charge Code (G27)

Purpose: Use this screen to define the additional charge code the system applies to an order that contains a check interface payment method.

MSR0051 CHANGE Change System Control Value 4/30/99 13:16:54

Description . : Check Interface Additional charge Code

Code . . . . . BA BR C CI

CK CS D DB

DD EM EN ...

Narrative . . .

Application . : O/E

Applic group . PAY

Sequence# . . . 20

F3=Exit F12=Cancel

Code field: Enter the additional charge code you wish the system to apply to an order that contains a check interface payment method.

The system automatically applies the additional charge code to an order if the payment method on the order matches the pay type defined in the Check Interface Payment Type (G26) system control value.

The system uses the dollar amount defined in the Default charge field for the additional charge code to apply to the order. If the order contains more than one ship to customer, the system applies the additional charge to the first ship to customer.

Additional charge codes are defined in and validated against the Additional Charge file. See Customer Service Chapter 3: Establishing Additional Charge Codes (WADC) for more information.

Leave this field blank if you do not want to apply an additional charge to an order that contains a check interface payment method.

Default Offer Source Code to Order Detail Line (G28)

Purpose: Use this screen to define whether the system defaults the source code defined for the offer on an order detail line to the Source code field on the order detail line when you add an item to an order in order entry and order maintenance.

MSR0052 CHANGE Change System Control Value 4/26/99 13:44:01

Description . : Default Offer Source Code To Order Detail Line

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . MRK

Sequence# . . . 10

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish the system to default the source code defined for the offer on an order detail line to the Source code field on the order detail line.

If this system control value is set to Y, the system checks if the offer on the order detail line is associated with the source code defined on the order header.

If the offer on the order detail line is associated with the source code on the order header, the system does not default the source code defined for the offer on the order detail line.

If the offer on the order detail line is not associated with the source code on the order header, the system defaults the source code defined in the Default source field for the offer defined on the order detail line to the Source code field on the order detail line.

Note: If you change the offer on an order detail line in order entry, the system defaults the source code associated with the new offer to the Source code field on the order detail line if a source code had not already been defined.

Related system control values: The following system control values affect which source code the system defaults to the Source code field on an order detail line.

• The system defaults the source code defined in the customer's mail history that is associated with the offer on the order detail line to the Source code field on the order detail line if the Load Source from Mailing History (D20) system control value is set to Y. If the system defaults the source code from the customer's mailing history, the system does not default the source code defined for the offer on the order detail line. The system defaults the source code from the customer's mailing history regardless of whether the offer on the order detail line is associated with the source code on the order header. See Load Source from Mailing History (D20).

• The system updates the source code and offer on an order line based on the most recent customer mail history associated with the item on the order line if the Update Source Code from Mail History (J94) system control value is set to Y. If the Default Offer Source Code to Order Detail Line (G28) and Update Source Code from Mail History (J94) system control values are both set to Y, the system uses Update Source Code from Mail History Logic When Using Item.

• If a source code has not been defined in the Default source field for the offer on the order detail line, the system defaults the source code defined on the order header to the Source code field on the order detail line if the Use Source Code from Order Header When Creating Order Lines (D73) system control value is set to Y.

The Post Sales G/L Using Division at Order Line Source Code (F17) system control value defines whether the system posts sales, merchandise discounts, returns, and discount returns to the division associated with the source code on the order detail line. You should set this system control value to Y, if you wish sales/shipment posting to match demand.

Enter N or leave this field blank if you do not want the system to default the source code defined for the offer on an order detail line to the Source code field on the order detail line and instead, use current functionality.

Auto Update Order Priority (G45)

Purpose: Use this screen to define whether order priority will be automatically set to 9 (highest priority) when you enter an arrival date override in order entry/maintenance.

MSR0052 CHANGE Change System Control Value 7/01/99 12:04:38

Description . : Auto Update Order Priority

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to update the order priority to 9 (highest priority) when you enter an arrival date override in order entry/maintenance.

Order priority is an optional selection criterion in pick generation, and can be used to override shipping restrictions associated with shipping zone reservation rules for climate-sensitive inventory stock. For example, a potted shrub ordered in February may be assigned an arrival date of May 1 under zone reservation rules, but the customer wants the shrub delivered in March. Updating the arrival date to March 1 would automatically update the order priority to 9, and this priority could be selected as a criterion in pick generation. See Fulfillment Chapter 53: Shipping Zone Reservation Overview, for more information on the shipping zone reservation process, and Chapter 5: Working with Pick Slip Generation (WPSG) for information on selection criteria for pick slip generation.

Enter N or leave this field blank if you do not want the system to automatically update order priority to 9 (highest priority) when you enter an arrival date override in order entry/maintenance.

Order Combination Pick Selection Type (G47)

Purpose: Use this screen to define whether to update the Order combination type field during order entry. Order combination type can be used as a criterion for pick slip generation when you want to print pick slips for items belonging to one or more long SKU classes.

MSR0051 CHANGE Change System Control Value 8/05/99 11:27:45

Description . : Order Combination Pick Selection Type

Code . . . . . L/S CLASS L/S CLASS

Narrative . . .

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter the code L/S CLASS if you want to update the Order combination type field in the Order Ship-to File during order entry, based on the long SKU class of items on an order.

Note: This field is not visible on the Order Entry screens.

If you enter a value in this field, the Selected long SKU class option will display on the Pick Slip Selection screen as a criterion for generating pick slips. This option allows you to select an order combination type which includes a single long SKU class or multiple long SKU classes for pick slip generation.

Order combination type and long SKU class: The Order combination type of an order matches the long SKU class of the items on the order.

• If all items on an order are assigned to the same long SKU class, the Order combination type code will be the same as the long SKU class code of the items.

• If the order includes items assigned to different long SKU classes, the Order combination type code will be 9999 (Mixed).

Important: Only items assigned to a long SKU class are considered for the Order combination type. An order of any Order combination type may include items with no long SKU class. If no item on an order has a long SKU class, the Order combination type field will remain blank.

Order combination type and pick slip generation: For each long SKU class selected for pick slip generation, the system will print pick slips for orders whose Order combination type matches the long SKU class selected. Each order will include items assigned to the selected long SKU class, and may also include items which are not assigned to any long SKU class.

If you select the long SKU class Mixed for pick slip generation, the system will print pick slips for orders whose order combination type is 9999 (Mixed).

Note: You must define a 9999 (Mixed) long SKU class in the Long SKU Class file to select Mixed long SKU class for pick slip generation. See Merchandising Chapter 8: Working with Long SKU Classes (WLSC), for more information.

Order combination type and zone reservation code: The Order combination type selection criterion is useful for generating pick slips for zone reservation coded (weather-sensitive) items if you have set up long SKU classes to correspond to zone reservation codes. See Fulfillment Chapter 53: Shipping Zone Reservation Overview, for more information on the zone reservation process, and Chapter 5: Working with Pick Slip Generation (WPSG) for information on selection criteria for pick slip generation.

Allow Order Number Override in Phone Interface (G54)

Purpose: Use this screen to define whether to use the Retail transaction number to assign order numbers for phone interface orders.

MSR0052 CHANGE Change System Control Value 7/29/99 16:31:32

Description . : Allow order number override in Phone Interface

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . INT

Sequence# . . . 220

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the system use the Retail transaction number field in the Phone Orders or Phone Order Expanded file as the order number for orders you receive through the phone interface.

About phone orders: You can use the phone interface to receive orders taken through a remote order entry service or retail outlet. Before you can load these orders into CWDirect, you must first populate either the Phone Orders file (PHORDS) or Phone Order Expanded file (PHORDE). Then you can use the Load Phone Orders menu option (fast path = LPHO) to use the information in either phone order file to create CWDirect orders. Finally, you use batch order entry to correct any errors in the resulting orders.

Order number assignment: If this system control value is set to Y, the system uses the Retail transaction number field in the Phone Orders or Phone Order Expanded file as the order number, as long as that order number is not already assigned to an order in your company. If the Retail transaction number is already assigned to an order, the system selects the next available order number from the Number Assignment file, as it does when you enter an order through order entry.

Order cross reference: The system creates a record in the Order Cross Reference file for each order it creates through the phone interface. This cross-reference record includes the Cross reference number (Retail transaction number) and the Order number that was assigned in CWDirect.

For example, if:

• the Retail transaction number is 5800

• the Allow order number override in phone interface field is set to Y

• there is no order # 5800 in your company

then the Cross reference number and the Order number are the same.

However, if

• the Retail transaction number is 5800

• the Allow order number override in phone interface field is set to Y

• there is already an order # 5800 in your company

• the next available order number in the number assignment file is 5850

then the Cross reference number is 5800 and the Order number is 5851.

Set this field to N or leave it blank to have the system always use the Number Assignment file to assign to new orders created through the phone interface. In this case, the system always creates an Order Cross Reference record as described in the second example, above.

For more information:

Chapter 23: Setting Up the Number Assignment File (WNUM)

• Marketing Chapter 50: Display Order Cross Reference (DOCR)

• Order Entry Chapter 31: Using the Phone Interface

Display Customer Affinity Upon Order Accept (G58)

Purpose: Use this screen to define whether the Select Affinity Items pop-up window will display in order entry when you accept an order from a customer the system has flagged as having one or more affinity preferences.

MSR0052 CHANGE Change System Control Value 4/18/00 12:23:11

Description . : Display Customer Affinity Upon Order Accept

Yes/No . . . . Y (Y,N)

Narrative . . . This value controls whether customer preferences (Affinity)

will be displayed upon acceptance of new orders.

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the system display the Select Affinity Items pop-up window when you accept an order from a customer who qualifies for affinity preferences.

Note: You must also set the Display Order Recap (A75) system control value to Y if you want the system to display the Select Affinity Items pop-up window upon acceptance of an order.

Enter N in this field if you want the system to display the Select Affinity Items window only when you select the Affinity option at the Display More Options Screen.

About customer affinity preferences: Affinity Add-on Sales is a function which identifies items that appeal to a customer’s preferences, and presents those items as potential add-on sales when the customer places an order. The Affinity function tracks each customer’s order history to determine the Customer Affinity Preferences for specific Attributes of the items you offer for sale, and specific Values of those attributes. For example, a customer might have a preference for the attribute Fabric type, and prefer linen or cotton. You can link these Item Attributes and Values to items or SKUs you offer for sale. When a customer places an order, the system suggests upsell items from your current offer which match the customer’s preferences.

For more information:

Marketing Chapter 52: Affinity Add-on Sales

• Customer Service Chapter 44: Working with Customer Affinity Preferences (WCST)

Display Backordered Affinity Items (G59)

Purpose: Use this screen to define whether the Select Affinity Items pop-up window will display items that are on backorder, or are not available.

MSR0052 CHANGE Change System Control Value 4/18/00 12:49:33

Description . : Display Backordered Customer Affinity Items

Yes/No . . . . Y (Y,N)

Narrative . . . This value controls whether customer preference (Affinity)

items will be displayed if they are backordered.

Application . : O/E

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the Select Affinity Items pop-up window display items that are backordered or unavailable as well as available customer affinity items when you accept an order from a customer who qualifies for affinity preferences.

Enter N in this field if you want the Select Affinity Items pop-up window to display only customer affinity items which are available.

About customer affinity preferences: Affinity Add-on Sales is a function which identifies items that appeal to a customer’s preferences, and presents those items as potential add-on sales when the customer places an order. The Affinity function tracks each customer’s order history to determine the Customer Affinity Preferences for specific Attributes of the items you offer for sale, and specific Values of those attributes. For example, a customer might have a preference for the attribute Fabric type, and prefer linen or cotton. You can link these Item Attributes and Values to items or SKUs you offer for sale. When a customer places an order, the system suggests upsell items from your current offer which match the customer’s preferences.

For more information:

Marketing Chapter 52: Affinity Add-on Sales

• Customer Service Chapter 44: Working with Customer Affinity Preferences (WCST)

Customer Affinity Recalculation Method (G60)

Purpose: Use this screen to determine whether the system uses the current date, or the customer’s last order date to update the Lifetime frequency rate field in the customer affinity records when you run the Batch Affinity Updates (MBAU) function to update records.

MSR0051 CHANGE Change System Control Value 4/18/00 12:51:15

Description . : Customer Affinity Recalculation Method

Code . . . . . ORDER ORDER AFFINITY

Narrative . . . Controls whether the batch affinity run date or the last

order date is used when recalculating customer affinity

Application . : C/S

Applic group . ALL

Sequence# . . . 99

F3=Exit F12=Cancel

Code field: Enter Order in this field if you want the Batch Affinity Updates function to recreate customers’ Lifetime frequency rates calculations and dates made when the customer placed his last order. If you have changed threshold values since the customer’s last order, the customer’s preference flag may be different from what it was on the date the order was actually placed.

Enter Affinity in this field if you want the Batch Affinity Updates function to update customers’ Lifetime frequency rates calculations and dates as if the customer placed an order on the current date and as if the order or return does not include an item linked to the attribute value for which you are updating information.

About Customer Affinity preferences: Affinity Add-on Sales is a function which identifies items that appeal to a customer’s preferences, and presents those items as potential add-on sales when the customer places an order. The Affinity function tracks each customer’s order history to determine the Customer Affinity Preferences for specific Attributes of the items you offer for sale, and specific Values of those attributes. For example, a customer might have a preference for the attribute Fabric type, and prefer linen or cotton. You can link these Item Attributes and Values to items or SKUs you offer for sale. When a customer places an order, the system suggests upsell items from your current offer which match the customer’s preferences.

About Batch Affinity updates: When you run the Batch Affinity Update function to update your records (the Initialize field on the Batch Affinity Update screen is set to N), the system updates all Customer Affinity Preference records for each attribute value.

For more information:

Marketing Chapter 52: Affinity Add-on Sales

• Customer Service Chapter 44: Working with Customer Affinity Preferences (WCST)

• Marketing Chapter 54: Batch Affinity Updates (MBAU)

Calculate Freight by Order Weight for N/C Orders (G68)

Purpose: Use this screen to define whether the system charges freight for orders whose merchandise total is zero, when you calculate freight by order weight.

MSR0052 CHANGE Change System Control Value 11/01/99 8:08:34

Description . : Calculate freight by order weight for n/c orders

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . FRT

Sequence# . . . 55

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish the system to charge freight for orders whose merchandise total is zero, when you calculate freight by order weight.

You may want to charge freight on an order whose merchandise total is zero, if the order contains a warranty item.

The system calculates freight on the order by order weight if the source code defined on the order header is set up to calculate freight using the order weight freight method. See Fulfillment 41: , for more information on how the system calculates freight by order weight.

Enter N or leave this field blank if you do not want the system to charge freight for orders whose merchandise total is zero, when you calculate freight by order weight.

The system only charges freight for orders whose merchandise total is greater than zero.

Use PartSmart Interface (G69)

Purpose: Use this screen to define whether the system adds items from the PartSmart system to an order in order entry and order maintenance.

MSR0052 CHANGE Change System Control Value 1/03/00 10:20:35

Description . : Use PartSmart Interface

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . INT

Sequence# . . . 220

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to add items from the PartSmart system to an order in order entry and order maintenance.

Display Selected Items (PartSmart) Window

Purpose: This window displays items and the associated order quantity from the PartSmart system that are available to add to the current order. At this window you can:

• delete any items you do not wish to add to the order

• exit out of the pop-up window without adding any items from PartSmart to the order

• add the items that display in the window to the current order

When you add items that display in this window to the current order, the system creates an order detail line for each item.

How to display the PartSmart window: Press F5 in order entry or maintenance on the Work with Order Lines Screen (Adding Items to the Order) or the Work with Order/Detail Screen.

Note: This window only displays if there are items from the PartSmart system available to add to the order.

Display Selected Items (PartSmart)

Opt Item SKU Qty

Type options, press Enter.

4=Delete

FINIS867Y 3

A BASKET FULL OF GOODIES

ITEX 2

HOSE ATTACHMENT

JUI87C 2

THE FAMOUS BBQ SAUCE

MITT8NS BLCK LRGE 3

FLAME PROOF MITTENS +

Enter=Add Lines F3=Exit F11=Delete F12=Cancel

Determining if items are available from PartSmart: The system looks at the Part Smart Work file to determine if there are items available from PartSmart to add to the order. The Part Smart Work file contains items from Part Smart that are available to add to an order based on the user ID of the operator entering the order. If the user ID matches any record in the Part Smart Work file, the system displays all items associated with the user ID in the Display Selected Items (PartSmart) window.

Field

Description

Item

A code for a unit of inventory.

Item codes are defined in and validated against the Item file.

Alphanumeric, 12 positions; optional.

SKU

The specific style of an item, such as color, size, or width.

Alphanumeric, one 14 position field (full SKU) or three 4-position fields (split SKU); optional.

Qty

The number of units being ordered.

Numeric, 5 positions; display-only.

Screen Option

Procedure

Delete an item from the Display Selected Items PartSmart window.

Enter 4 next to the item to delete it. The item is deleted from the window and you can no longer add the item to the current order.

Add the items that display in the Display Selected Items PartSmart window to the current order

Press Enter. The system creates an order detail line for each item that displays in the window.

Delete all of the items from the Display Selected Items PartSmart window.

Press F11. All of the items that display in the window are deleted and are not available to add to the current order.

PartSmart Socket Server

In order to add items from the PartSmart system to an order, you must first start the PartSmart socket server. The PartSmart Socket Server looks for order information from PartSmart and adds the order information to the Part Smart Work file.

To start: You can start the PartSmart socket server using the Start PartSmart Socket Server menu option (fast path = SPSS). When you select the Start PartSmart Socket Server menu option, the system submits a program to start the socket server. The PartSmart socket server remains active until you end the socket server.

To end: You can end the PartSmart socket server using the End PartSmart Socket Server menu option (fast path = EPSS). When you select the End PartSmart Socket Server menu option, the system submits a program to end the socket server.

Related system control value: If the Use Warehouse for PartSmart Item Availability (G71) system control value is set to Y, the system only reserves the order quantity for an item that displays on the Display Selected Items PartSmart window from the warehouse specified.

Enter N or leave this field blank if you do not want the system to add items from the PartSmart system to an order in order entry and order maintenance.

Use Warehouse for PartSmart Item Availability (G71)

Purpose: Use this screen to define the warehouse the system uses to determine the item availability for items from the PartSmart system.

MSR0054 CHANGE Change System Control Value 1/03/00 11:07:48

Description . : Use Warehouse for PartSmart Item Availability

Number . . . .

Narrative . . .

Application . : O/E

Applic group . INT

Sequence# . . . 221

F3=Exit F12=Cancel

Number field: Enter the warehouse code the system uses to determine the item availability for items from the PartSmart system.

The system displays all items from the PartSmart system that are available to add to the current order in the Display Selected Items (PartSmart) Window.

When you add an item from the PartSmart system to an order, the system determines the quantity of the item that can be reserved based on the pickable quantity in the warehouse you specified.

Note: In order to add an item to an order from the PartSmart system, the Use PartSmart Interface (G69) system control value must be set to Y.

Leave this field blank if you wish the system to determine the item availability for items from PartSmart from any allocatable warehouses in the company you are currently in.

Electronic Gift Certificate Pay Type (G72)

Purpose: Use this screen to define the credit card pay type that represents the electronic gift certificate pay type.

MSR0054 CHANGE Change System Control Value 2/15/00 8:54:23

Description . : Electronic Gift Certificate Pay Type

Number . . . . 04 05 06 29

30 32 40 41

Narrative . . .

Application . : O/E

Applic group . PAY

Sequence# . . . 30

F3=Exit F12=Cancel

Number field: Enter a valid credit card pay type number in this field to represent the electronic gift certificate pay type.

A list of valid credit card pay types (pay category 2) displays on this screen. An error message displays if you enter a number that is not a valid credit card pay type.

Electronic gift certificates are paperless certificates that can be used as payment for an order. Electronic gift certificates are similar to credit cards - the customer tells the operator the gift certificate number and the operator adds the electronic gift certificate pay type with the gift certificate number to the order.

When you enter the electronic gift certificate pay type on an order the system displays the Display Electronic Gift Certificate Window, which tells you the dollar amount remaining for the gift certificate that you can use as payment for an order.

Leave this field blank if you do not want a credit card pay type to represent an electronic gift certificate pay type.

For more information: See Customer Service Chapter 122: Working with Gift Certificates for more information on setting up gift certificates and applying an electronic gift certificate as payment to an order.

Require Gift Certificate/Coupon Number (G75)

Purpose: Use this screen to define whether you will be required to enter Gift Certificate or Coupon number when you enter a Gift Certificate or Coupon pay type code in order entry.

MSR0052 CHANGE Change System Control Value 4/01/00 12:37:43

Description . : Require Gift Certificate/Coupon Number

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . PAY

Sequence# . . . 6

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to require the entry of a Gift Certificate or Coupon number when you enter a Gift Certificate or Coupon pay type on an order.

Enter N in this field or leave it blank to allow entry of a Gift Certificate or Coupon pay type on an order without entering a Gift Certificate or Coupon number.

Related system control value: If system control value Dynamic Creation of Coupons (B21) is set to Y, you can enter a coupon number that does not exist, and the system will create a coupon record.

For more information: See Entering Orders Using Header Format.

Use Net Perceptions (G79)

Purpose: Use this screen to define whether the system will add items returned from the Net Perceptions database to the Item Affinity Work file for display and optional selection on the current order.

MSR0052 CHANGE Change System Control Value 4/01/00 12:37:08

Description . : Use Net Perceptions

Yes/No . . . . N (Y,N)

Narrative . . .

Application . : O/E

Applic group . PRI

Sequence# . . . 99

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the system add customer preference items from the Net Perceptions database to the Select Affinity Items Window which displays when you select the Customer Preferences option from the Display More Options Screen.

Enter N or leave this field blank if you do not want the system to access the Net Perceptions database for customer preferences.

Note: The Select Affinity Items pop-up window will also display when you accept an order from a customer who has been flagged as having one or more affinity preferences, if:

• system control value Display Order Recap (A75) is set to Y, and

• system control value Display Customer Affinity Upon Order Accept (G58) is set to Y.

Require Phone Number in Order Entry/Order Maintenance (H01)

Purpose: Use this screen to define whether you will be required to enter a phone number in one of the two phone number fields on the order header screen in order entry and order maintenance.

MSR0052 CHANGE Change System Control Value 4/21/00 11:28:20

Description . : Require Phone Number in OE/OM - Y/N

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . CST

Sequence# . . . 101

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want to require entry of a phone number in at least one of the two phone number fields on the order header screen in order entry and order maintenance.

Enter N or leave this field blank if you do not want at least one of the phone number fields on the order header screen to be a required field.

Order API: Phone numbers are not required when you create or update customers through the Generic Order Interface (Order API), regardless of the setting of this system control value.

Note: Labels for the two fields are either Day/Evening or Day/Fax, depending on the setting of system control value Phone Numbers (D15).

Display Telemarketing Window in Order Entry (H02)

Purpose: Use this screen to define whether to display a telemarketing special window automatically when you press F9 after entering items in order entry.

MSR0052 CHANGE Change System Control Value 5/01/00 15:38:03

Description . : Display Telemarketing Window in Order Entry-Y/N

Yes/No . . . . (Y,N)

Narrative . . .

Application . : O/E

Applic group . CST

Sequence# . . . 102

F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have a telemarketing special window open automatically when press F9 after you have entered items in order entry. This window, which allows you to upsell the customer with selected items, opens after any default pay type window that might appear if the Default Previous Pay Type in Order Entry (D64) system control value is selected.

The window does not open automatically if:

• The Upsell windows flag for the order type is not set to B (Both) or P (Promotional pricing)

• There are no eligible, current telemarketing specials

Note: The Telemarketing Specials window does not open automatically unless you press F9 at the Work with Order Lines Screen (Adding Items to the Order) or the Work with Order/Detail Screen.

The Select Telemarketing Specials by Item Category (F35) system control value controls the flow of the screens related to telemarketing specials in order entry or order maintenance.

• If this system control value is set to N or is blank, you advance directly to the Telemarketing Specials Window, where you can review detail information for each item or SKU and/or add it to the order.

• If this system control value is set to Y, you must advance through the Select Item Category Window and Display Telemarketing Items Window before you reach the Telemarketing Specials Window. See If Displaying by Item Category.

Add Accompanying Items in Order Maintenance (H28)

Purpose: Use this screen to define whether an accompanying item will be added to the order automatically when you add the original item to the order in Order Maintenance.

MSR0052 CHANGE Change System Control Value 10/23/00 15:16:51

Description . : Add Accompanying Items in Order Maintenance

Yes/