Chapter 19: Setting Up Customer Service Values

Purpose: The Customer Service section of the System Control file defines parameters that control:

• Returns and refunds

• Credit card authorization

• Forms printing

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 Customer Service System Control Values

This table describes briefly each system control value for the Customer Service application area and lists the control value, a short definition, other 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 have more than one company on your system, make a copy of this table for each company on your system.

Company: _____________________________________________________________

System Control Value	Description	Your Value
Default Item History Tracking (B18)	Defines how the system tracks item purchase history for new customers entered through Catalog Requests.	Code:
Alternate Pay Type (B51)	Defines the pay type that to use to credit returned items after the grace period has expired.	Number:
Return Grace Period (B52)	Defines the number of days allowed for items to be returned in order to generate a refund.	Number:
Refund Check Bonus % (B69)	Defines the percentage used when calculating a refund used as a bonus credit.	Percentage:
Bonus Credit Bonus % (B70)	Defines the percentage used when calculating the value of a bonus merchandise credit.	Percentage:
Define Special Forms (C03):
Return Acknowledgement (C04)	Indicates if the system collects data for a return acknowledgment card.	Yes/No:
Automatic Generation of Gift Acknowledgement (B92)	Indicates if the system prints a gift acknowledgment card when the pick slip is printed.	Code:
Gift Order Acknowledgement Print Program (B90)	Defines the system name for the gift card letter.	Code:
Auto Soldout Cancel Reason (C20)	Defines the default cancel reason code used when the system identifies an item as “sold-out.”	Code:
Print Credit Card Credit Acknowledgments (C35)	Defines whether to print a credit card acknowledgment if there is a refund/balance due on a credit card order.	Yes/No:
FTC -- # of Days to Add for Special Handling (C67)	Defines the number of days to add to the expected PO receipt date to determine the expected delivery date for items with special handling.	Number:
FTC -- # of Days to Add for Drop Ships (C68)	Defines the number of days from the arrival date that drop ship items are expected to be shipped.	Number:
FTC -- Action after Second Notification (C70)	Defines the action to be taken with the order after the second backorder notification card has been sent.	Code:
FTC -- # of Days for Items without Expected Ship Date (C71)	Defines the number of days to add to the arrival date to determine the expected ship date for items without an expected ship date.	Number:
Label 1-Up Printing Program (C83)	Defines the name of the program that is used to print 1-up labels for catalog requests and House List.	System name:
Label 4-Up Printing Program (C84)	Defines the name of the program that is used to print 4-up labels for catalog requests and House List.	System name:
Backorder Card Print Program (D04)	Defines the name of the program that is used to print backorder cards.	System name:
Days after 2nd Backorder Notification to Cancel Order (D07)	Defines the number of days after the second backorder notification to cancel the order if the SCV FTC-Action after Second Notification is set to CANCEL	Number:
Update of Current Source Code in Customer File (D08)	Defines when to update the Current source code field in the Customer file.	Code:
Default Associate Code (D09)	Defines the default value for the Associate field for new customers entered through Order Entry and Catalog Requests.	Code:
Default Mail Name (D10)	Defines the default value for the Mail name field to be assigned to new customers entered through Order Entry and Catalog Requests.	Yes/No:
Default Rent Name (D11)	Defines the default value for the Rent name field for new customers entered through Order Entry and Catalog Requests.	Yes/No:
Credit Card Credit Acknowledgment Print Program (D22)	Defines the name of the program that produces acknowledgments for a credit issued to a credit card.	System name:
Refund Check Print Program (D23)	Defines the name of the program that produces refund checks.	System name:
Merchandise Credit Print Program (D29)	Defines the program the system uses to print merchandise credits.	System name:
Bonus Credit Print Program (D30)	Defines the program name the system uses to print bonus credits.	System name:
Sale Credit Print Program (D31)	Defines the program name the system uses to print sale credits.	System name:
Customer Return Label Print Program (D35)	Defines the print program name the system uses to print a customer return label for item returns.	System name:
Default Source Code for Batch Catalog Requests (D37)	Defines the default source code to use when processing catalog requests through an interface.	Code:
Display Customer Notes in LIFO Sequence (D55)	Defines whether recently-entered customer notes appear first	Yes/No:
Number of Days to Delay Initial Backorder Notice (D89)	Defines the number of days to allow for purchase order receipt and order shipment before a backorder notice to the customer is required.	Number:
Update a Bill-to Address with Sold-to Address Changes (E13)	Defines whether to pop-up a window when you change a Sold-to address with a permanent Bill-to account, allowing you to apply the Sold-to changes to the Bill-to address.	Yes/No:
Call Tag Print Program (E17)	Defines the program the system uses to print call tags.	System name:
Print Letters Using OfficeVision/400 (E26)	This option is not currently supported.	Yes/No:
Print Alpha $ Amount on Refund Check (E30)	Defines whether the system prints an alphanumeric and a numeric dollar amount on refund checks.	Yes/No:
Edit for Duplicate Catalog Requests (E46)	Defines whether the system checks for duplicate catalog requests when you create a new catalog request.	Yes/No:
Prompt for Mandatory Demographics in Order Maintenance (E60)	Defines whether the system prompts you to complete a mandatory demographic profile field in Order Maintenance.	Yes/No:
FTC--Number of Days Prior to Next Backorder Date to Generate Second Notice (E67)	Defines the number of days before a second backorder notice is due to print the notice or write the backorder record.	Number:
FTC--Second Notice Output (E68)	Defines whether to print second backorder notices, create records in the Backorder Cancellation Pending file, or both.	Value:
Number of Days to Add for Accepted Delays (E69)	Defines the number of days to extend the next backorder date if a customer accepts a delay on a backorder pending cancellation.	Number:
Use Item Freight Exemption File (E73)	Defines whether the system excludes items defined in the Work with Freight Exempt Items (WFEI) menu option from freight.	Yes/No:
Soldout Notification Print Program (E75)	Defines the program the system uses to print soldout notification cards.	System name:
Gift Certificate Print Program (E76)	Defines the program the system uses to print gift certificates.	System name:
Unconditional Suppression of Backorder Card (F19)	Defines whether to include items flagged to suppress backorder cards on a first backorder card if another item on the order generates the card.	Yes/No:
Require Exchange Item at Time of Receipt (F42)	Defines whether an exchange item is required at the time of creation or receipt of a receipt authorization.	Yes/No:
Use Streamlined Return Authorizations (F44)	Defines whether you use the standard or streamlined return authorization process.	Yes/No:
Postal Code Scan Length (F61)	Identifies the number of positions in the zip or postal code to consider when searching for a customer.	Number:
Display Customer Action Notes/Messages in RA (F64)	Defines whether the Edit Customer Actions pop-up window or an indicator that there are order messages displays in Work with Return Authorizations.	Yes/No:
Track Customer History at Entity Level (F89)	Defines whether you break out customer history related to orders based on the entity associated with each order.	Yes/No:
Individual Position for Consumer Customers (G02)	Defines the individual position for the system to use when determining whether to automatically create and/or assign an individual customer in order entry.	Code:
Create Bank Interface Record (G12)	Defines whether the system creates a bank reconciliation transaction when you generate refund checks in Process Refunds.	Yes/No:
Display First Membership Order Total (G14)	Defines whether to display a pop-up window indicating the estimated dollar total for the first membership order when you enter a membership item in order entry.	Yes/No:
Populate Marketing/PO Interface Trigger File (G33)	Defines the types of order, customer service, or purchase order activity that triggers an update to he Marketing/PO Interface Trigger file, which you can then use to drive an interface download.	Code:
Require Return Reason Code for all Call Tags (G67)	Defines whether the system requires you to enter a return reason code when you create a call tag.	Yes/No:
Display Action Notes in Order Inquiry (G74)	Defines whether the Edit Customer Actions window displays in order inquiry if there are unresolved customer action notes.	Yes/No:
Backorder Notification E-Mail Program (G95)	Defines the program used to create backorder notices to send customers via email.	Program:
Soldout Notification E-Mail Program (G96)	Defines the program used to create soldout notifications to send customers via email	Program:
Default Opt In/Opt Out Flag (G97)	Defines the default value of the Opt in/Opt out field, which determines the preferred method of correspondence for storefront customers.	Code:
Require Reason in CTI (G98)	Defines whether they system requires an order inquiry reason code when you return to the CTI Customer Selection screen from order inquiry/maintenance.	Program:
Gift Certificate E-Mail Program (H07)	Defines the program to generate email, rather than printed, gift certificates.	System name:
Credit Card Credit Acknowledgement E-Mail Program (H08)	Defines the program to generate email, rather than printed, credit card credit acknowledgements.	System name:
Create Random Gift Certificate/Coupon Numbers (H09)	Defines whether the system assigns gift certificate and coupon numbers sequentially, or assigns non-sequential numbers to help prevent fraud.	Yes/No:
E-Mail Order Confirmations for All Orders (H51)	Defines whether the system sends an email confirmation when any order is accepted or maintained or only when a customer accepts or maintains an order on the web storefront.	Yes/No:
E-Mail Shipment Confirmations for All Orders (H52)	Defines whether the system sends an email confirmation when any order or return is shipped or only when an e-commerce order or return is shipped.	Yes/No:
Return Confirmation E-Mail Program (H53)	Defines the program name to generate email, rather than printed, return confirmations.	System name:
Enable Catalog Request at Individual Level (H81)	Defines whether catalog requests can be entered for individual customers.	Yes/No:
Require Customer Class in OE, WCAT, and WCST (H85)	Defines whether the customer class is required in order entry, catalog requests, and customer maintenance.	Yes/No:
Update Customer Sold to with Bill to Account Number for New E-Commerce Orders (H87)	Defines whether to assign the bill-to number from an e-commerce order to the customer sold-to on the order.	Yes/No:
Assign Unreferenced Email (H93)	Defines whether to search for a matching customer for an incoming email based on the email address.	Code:
Use Workflow Management (H96)	Defines whether the workflow management module is enabled.	Yes/No:
Write Outbound Email to Email Repository (H99)	Defines whether to keep a record of outbound email notifications in the Correspondence History file.	Yes/No:
Email Presentation (I01)	Defines whether to delete blank lines or paragraph spacing from inbound emails you store in Correspondence History, or to leave the spacing.	Code:
Display Alternate Shipping Charges by Via Window in OM (I02)	Defines whether to offer the customer a choice of shippers in order maintenance.	Yes/No:
Include Special Handling in Alternate Shipping Charges by Via (I03)	Defines whether to include special handling charges in the freight totals displayed in the pop-up window in order entry.	Yes/No:
Vendor for E-Mail Gift Certificate (I04)	Defines the vendor number the system uses to process electronic gift certificates.	Number:
Include All Customer Inquiry Triggers for DMT (I09)	Indicates if the system creates a record in the DMT Customer Inquiry file for a CI (customer inquiry) trigger record when a corresponding OH (order header) trigger record exists in the Marketing Download Trigger file.	Yes/No:
Confirmation Email Directory Address (I19)	Specifies the directory address that identifies the originating email address to use when generating email notifications.	System name:
Validate Prefix (I27)	Specifies whether to validate a customer’s prefix against the Prefix file.	Yes/No:
Additional Charge Group Code for Freight (I29)	Specifies the additional charge Group that identifies a negative additional charge applied to an Amazon order as a freight adjustment rather than a merchandise adjustment.	Code field:
Gift Certificate Pricing Method (I54)	Indicates how the system determines the gift certificate amount.	Code:
SmartLabel/SmartPost Values (I60)
SmartLabel Merchant ID (I46)	Specifies the Client ID for the SmartLabel barcode on the pick slip if you use SmartLabel returns processing.	Code:
SmartLabel Item Weight Limit (I48)	Specifies the Client ID for the USPS barcode on the pick slip if you use SmartLabel returns processing.	Code:
SmartLabel Item Weight Limit (I48)	Specifies the maximum item shipping weight to print a SmartLabel on a pick slip if you use SmartLabel returns processing.	Weight:
SmartLabel Scanned Return Input Mode (I61)	Specifies whether to use order maintenance or return authorizations for processing SmartLabel returns.	Code:
SmartLabel FTP Script for ARN Import (I62)	Specifies the FTP script to use for populating the SmartLabel ARN file.	Code:
SmartPost Application ID Prefix (J77)	Specifies the application prefix ID to use when generating the barcode on a SmartPost pick slip.	Number:
SmartPost Application ID (J78)	Specifies the application ID to use when generating the barcode on a SmartPost pick slip.	Number:
SmartPost USPS Service Type (J79)	Specifies the service type that indicates the description to print above the barcode on a SmartPost pick slip.	Number:
Generate Sale Credit for Orders with Sale Items (I64)	Indicates whether to generate sale credits as refunds for sale items.	Yes/No:
Stored Value Card Processing Values (I71)
Use Streamlined Stored Value Card Billing (I23)	Indicates if the system sends pick control records containing physical stored value card items to billing once you assign numbers to the physical cards.	Yes/No:
Stored Value Card Modulus Checking Method (I24)	Indicates if the system performs a calculation against the digits of the stored value card number to ensure that the card is valid.	Code:
Stored Value Card Activation Pricing Method (I25)	Indicates how the system determines the stored value card issue amount.	Code:
Stored Value Card Activation Authorization Service (I26)	Defines the service bureau used to process stored value card activation requests.	Code:
Stored Value Card Email Notification Program (I30)	Defines the program used to generate Stored Value Card email notifications.	System name:
Use Stored Value Card Batch Processing (I50)	Defines whether stored value card activation and stored value card authorization reversal transactions are processed immediately or in batch.	Yes/No:
Generate SVC Refund for all Merchandise Credit Refunds (I72)	Indicates whether the system generates a stored value card refund in place of a merchandise credit refund.	Yes/No:
Default SVC Refund Item Number (I73)	Defines the stored value card item the system adds to an order in order to process the stored value card refund.	Code:
Price Override Reason for SVC Refund Item (I74)	Defines the price override reason code the system defaults to the order line added to the order to process the stored value card refund.	Code:
Default Pick Generation Template for SVC Refund Processing (I75)	Defines the pick slip generation template the system uses the process the stored value card item that was added to an order during refund processing.	Number:
Hold Reason for Stored Value Cards with Insufficient Funds (J18)	Defines the hold reason the system assigns to a “catch-all” stored value card pay type when a balance inquiry performed during batch authorization indicates the card amount is less than the amount to authorize.	Code:
Perform Balance Inquiry during Batch Authorizations (J19)	Indicates whether the system performs a balance inquiry against a stored value card pay type before performing a batch authorization against the stored value card pay type.	Yes/No:
Perform Authorization Reversal during Deposit Processing (J20)	Indicates whether the system performs a stored value card authorization reversal during deposits processing if the authorization amount is greater than the deposit amount.	Yes/No:
Retain Unused Stored Value Card Authorization After Deposit (J21)	Defines whether the system automatically voids a partially deposited stored value card authorization.	Yes/No:
Remove Stored Value Card Number After Activation (J22)	Defines whether the system removes the stored value card number from the Stored Value Card file once the stored value card has been activated.	Yes/No:
Use Swipe Card Entry for SVC Activations (J44)	Defines whether you wish to assign stored value card numbers to physical cards by manually entering the stored value card numbers on the Stored Value Card Assignment screen or by swiping the cards through a magnetic strip reader to default to the SVC Swipe Assignment screen	Yes/No:
Combine Stored Value Cards on One Pick Ticket (J53)	Defines whether the system combines all physical stored value cards on an order ship to on one pick slip.	Yes/No:
Use Loyalty Membership Program (I81)	Indicates whether the background jobs should evaluate customers’ eligibility for loyalty membership programs.	Yes/No:
Loyalty Membership Activation Notification Email Program (I82)	Indicates the program to use to generate email notifications when customers qualify for loyalty memberships.	System name:
Loyalty Membership Deactivation Notification Program (I83)	Indicates the program to use to generate email notifications when customers no longer qualify for loyalty memberships.	System name:
Display Alternate Customer Cross Reference Window (I84)	Indicates whether to attempt to match customers on alternate customer number based on the single number specified in the Customer Sold To file (the “primary”), or to give equal priority to any of the alternate customer numbers stored in the Alternate Customer # Cross Reference file.	Yes/No:
Amazon FTP Download Script (I87)	Indicates the FTP script to use for extracting and downloading Amazon information.	Code:
Assign Alternate Customer # (I88)	Indicates whether to automatically assign an alternate customer to each newly created customer.	Yes/No:
Defer Purge During Customer API (I89)	Indicates whether to automatically delete customers when you receive a valid deletion request through the generic customer API, or to retain deletion requests for review.	Yes/No:
Default Customer for Customer API (I90)	Indicates the customer record to use as a guideline for which fields should retain their current values if new information is not received through the generic customer API.	Number:
Disregard Soldout Controls for Non-Allocatable Warehouses (J27)	Defines whether the system disregards soldout control rules for inventory reserved against a non-allocatable warehouse.	Yes/No:
SKU Cross Reference Type (J55)	Indicates whether to automatically create a SKU cross reference record whenever you create a new SKU.	Code:
Search SKU Cross Reference (J56)	Indicates whether to display the SKU Cross Reference Selection screen when you prompt on the Item field in order entry.	Yes/No:
Send RA Message for RA Create (J57)	Defines when the system creates the Generic WMS Customer Return XML Message (CWCustomerReturn) during non-streamlined return processing.	Code:
Send RA Message for Negative Quantity in OE/OM (J58)	Defines whether the system generates a Generic WMS Customer Return XML Message (CWCustomerReturn) when a return is created by entering a negative quantity on an order line in order entry/maintenance, or through the Generic Order Interface (Order API).	Yes/No:
Send RA Message for RA Delete (J59)	Defines whether the system generates a Generic WMS Customer Return XML Message (CWCustomerReturn) when an RA is deleted.	Yes/No:
FTC - First Notice Output (J70)	Defines whether to immediately print first backorder notices, create first backorder notice records in the Backorder Cancellation Pending file, or both.	Code:
Additional Charge Code for Pre Billed Amount Returns (J74)	Indicates the additional charge code to use for return of a pre-billed item.	Code:
Additional Charge Code for Pre Billed Amount Soldouts (J75)	Indicates the additional charge code to use for cancellation or sellout of a pre-billed item.	Code:
Prevent Storing the Customer’s Last CC# and Exp Date (J86)	Defines whether the system prevents the storing of the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History and Customer Ship To Order History files.	Yes/No:
Use Costing Method for Returns (K22)	Defines whether the cost of a return is based on the original invoice detail cost or the current costing method cost.	Yes/No:
Include Held Orders in DMT Order Files (K52)	Defines whether to include held, non-fraud orders when extracting order-related updates in the DMT download files.	Yes/No:
Include All Customer Merge/Purge Triggers in DMT (L17)	Defines whether the customer sold to merge/purge process creates triggers in the Marketing Download Trigger file.	Yes/No:
Stored Value Card Merchant ID for Activations (L69)	Defines the merchant ID the system sends to the service bureau for stored value card activation transactions.	Code:
Require Order Message Entry (L73)	Defines whether the system requires the entry of an order message before you exit Order Inquiry, Order Maintenance, or both.	Code:
Use Credit Card Authorization Values (L75)
Use Auto Authorization Interface (C14)	Indicates if you use the Auto Authorization Interface.	Yes/No:
Use Credit Card Encryption (I97)	Defines whether the system encrypts the credit card number in the CWDirect database, providing additional security of credit card data.	Code:
Require Credit Card Token (L40)	When using Credit Card Tokenization, defines whether the system will accept a credit card number that has not been replaced with a token.	Yes/No:
Tokenization IJCT Job (L41)	Defines the integration layer job used to transmit register token messages between CWDirect and the authorization service during the Credit Card Tokenization Process.	Code field:
Preauthorize Backorders (D32)	Defines whether to transmit a completely backordered order for initial authorization to determine whether it is a fraud order.	Yes/No:
Authorize Only Merchandise for Drop Ship Picks (C92)	Determines the amount to authorize for drop ship purchase orders and drop ship pick slips.	Yes/No:
Use Credit Card Vendor Response Entity Ship Via Dollar Limits (F94)	Defines whether the system performs an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order.	Yes/No:
Credit Card Authorization AVS Hold Exemption/Bypass (E61)	Defines whether to hold orders more than once for address verification.	Yes/No:
Display Partial Credit Card Number in Logs (J16)	Defines how the system masks the credit card data in the ECLG and MQJAVALOGS XML log files when credit card encryption is enabled.	Yes/No:
$ Threshold for Automatic Authorization # Assignment (K36)	Defines the dollar threshold the system uses to determine when the system automatically assigns the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to a credit card payment.	Dollar amount:
Authorization Number for Authorizations Under $ Threshold (K37)	Defines the authorization number the system automatically applies to credit cards that require authorizations that are below the dollar threshold defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value.	Code field:
Authorization Number for Authorizations Under $1.00 (I08)	Defines the authorization number the system automatically applies to credit card authorizations that are under one dollar.	Code:
Default Credit Card Authorization Number for Soft Declines (F93)	Defines the credit card authorization number the system defaults to a credit card authorization that is declined, but is under a specified dollar amount.	Code:
Default Vendor Response for Automatic Authorizations (G10)	Defines the vendor response code to assign to authorizations that you approve without receiving a response from the authorization service.	Code:
Maximum Number of Retries on Credit Card Orders (E74)	Defines the maximum number of times to attempt authorization for an order.	Number:
Authorization Service for Authorization Inquiries (K29)	Defines the authorization service for which you perform an authorization inquiry against a credit card to receive a response for an online authorization transaction that did not complete during order entry so that the credit card does not have to go out for authorization during batch authorization.	Code:
On-line Authorizations (B89)	Defines whether the system performs online credit card authorization during order entry.	Yes/No:
Online Auth Verification Only (I96)	Defines whether the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.	Yes/No:
Authorize Full Amount During Order Entry (G99)	Defines whether the credit card payment method on the order is authorized for the entire dollar amount defined for the card or the shippable amount defined for the card when you perform online authorization during order entry.	Yes/No:
Number of Times to Retry On Line Authorizations (B93)	Defines the number of times an authorization transmission can be performed during Immediate Authorization.	Number:
Online Auth Reserve $ Threshold (L74)	Defines the reserved dollar amount the system uses to determine whether to process an online authorization.	Dollar amount:
Send Data for Level II/III Discounting (I12)	Defines whether the system sends level II and level III discounting information to Paymentech during credit card deposit.	Yes/No:
Void Unused CC Authorization After Initial Deposit (K05)	Defines whether the system automatically voids a partially deposited credit card authorization.	Yes/No:
Bank# for A/R Credit Card Deposits (C56)	Defines the bank number to use when posting credit card deposits and direct bank disbursements.	Code:
Deposit Service for Conditional Deposits (L13)	Defines the deposit service that sends deposits as Conditional (transaction type Conditional, action code B) when subsequent deposit transactions are made against the same order number and authorization code or the deposit amount is greater than the available authorization amount.	Code field:
Preload Deposits (L78)	Defines whether billing or deposits creates records in the CC Deposit Transaction file and CC Deposit History file, based on the records in the Invoice Payment Method file.	Yes/No:

Default Item History Tracking (B18)

Purpose: Use this screen to define how the system tracks item purchase history for customers added to the system though catalog requests or Work with Customers.

MSR0051 OPEN Change System Control Value 11/17/93 12:06:03     Description . : Default Item History Tracking   Code . . . . . NONE SOLD TO SOLD+SHIP     Narrative . . . Application . : C/S Applic group . Sequence# . . .             F3=Exit F12=Cancel

Code field: Enter the code that defines how the system tracks item purchase history for customers added to the system automatically from a request for a catalog mailing, or that you enter through Work with Customers. The value you specify defaults into a numeric value in the Track item history field in the Customer file, but it can be overridden.

Valid values are:

• NONE: Do not perform item tracking. (numeric code 1)

• SOLD TO: Perform item tracking only for the Sold-to Customer (who places the order or requests the catalog) level only. (numeric code 2)

• SOLD+SHIP: Perform item tracking for the Sold To Customer and Ship To Customer (who receives the merchandise ordered). (numeric code 3)

Sold-to vs. ship-to customer: The sold-to customer is the customer who places the order or who requested the catalog; the ship-to customer is the customer who receives the merchandise ordered (although this can be the same customer).

This feature allows you to review mail order and item history information for the ship-to customer from the sold-to customer record. Tracking ship-to customer history allows you to target future offers to ship-to customers based on the information captured by the system.

Changing the code: You cannot review item history for any customer that has a 2 in this field. However, if you change the sold-to customer's Item history tracking value to a 3 at any time, you will be able to review all item history for a ship-to customer.

Alternate Pay Type (B51)

Purpose: Use this screen to define the payment type to use after the grace period for issuing refunds for returns has passed.

MSR0054 CHANGE Change System Control Value 6/01/04 14:34:06 Description . : Alternate Pay Type Number . . . . 03 07 09 13 17 19 Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the payment type that to use after the grace period for issuing refunds for returns has passed.

The eligible pay types display to the right of this field; you can enter one of the following pay types:

• stored value card (pay category 2, Card type S)

• coupon/credit (pay category 5)

• A/R (pay category 3)

This payment type can be overridden in Return Processing. This is 2-position, numeric field.

Pay type codes are defined in and validated against the Pay Type file. See Accounts Payable Chapter 5: Working with Pay Types (WPAY).

Return Grace Period (B52)

Purpose: Use this screen to define the number of days allowed for items to be returned once they are shipped in order to generate a refund.

MSR0054 OPEN Change System Control Value 1/12/94 15:16:22     Description . : Return Grace Period   Number . . . . Narrative . . . Application . : C/S Applic group . Sequence# . . .                 F3=Exit F12=Cancel

Number field: Enter the number of days (up to 7 positions, numeric) from the ship date that items are allowed to be returned. If a customer returns an item after the number of days defined for this control value, the customer receives whatever form of reimbursement your company has established as its policy for late returns.

The default type of reimbursement is defined in the Alternate Pay Type (B51) system control value.

For more information: See Customer Service Part I: Managing Returns.

Refund Check Bonus % (B69)

Purpose: Use this screen to define the percentage to be used when calculating the value of a refund check if it is returned to be used as a bonus credit.

MSR0057 OPEN Change System Control Value 1/12/94 15:22:16     Description . : Refund Check Bonus %   Percentage . . Narrative . . . Application . : C/S Applic group . Sequence# . . .             F3=Exit F12=Cancel

Percentage field: Enter the percentage amount to add to a customer's refund if the customer uses the refund as payment towards another order. This percentage is added to refund checks that you change to bonus credits through the Work with Refunds function. This feature enables you to refund the customer an additional amount if the customer does not cash the refund check, but instead, uses the credit towards a purchase.

The customer receives the original refund amount plus a percentage of the refund. This is a 5-position field with a 2-place decimal.

For example, if the refund check is for $50.00 and the percentage defined for this value is 10%, the total amount of the refund (if applied as a payment) is $55.00.

For more information: See Customer Service Part I: Managing Returns.

Bonus Credit Bonus % (B70)

Purpose: Use this screen to define the percentage to be used when calculating the value of a bonus merchandise credit.

MSR0057 OPEN Change System Control Value 1/12/94 15:27:45     Description . : Bonus Credit Bonus %   Percentage . . Narrative . . . Application . : C/S Applic group . Sequence# . . .             F3=Exit F12=Cancel

Percentage field: Enter the percentage amount to add to a customer's credit if the customer requests that the credit may be turned into a merchandise credit to be used as a payment towards another order.

The customer may request a bonus merchandise credit in lieu of a refund check, credit card credit, or some other form of credit. You may change the type of refund to a merchandise credit through the Work with Refunds function.

The credit can be for any pay type: an A/R credit, credit card credit, etc. The customer receives the original credit amount plus a percentage of the credit. This is a 5-position field with a 2-place decimal.

For example, if the credit is for $80.00 and the percentage defined for this value is 15%, the total amount of the merchandise credit (if applied as a payment) is $92.00.

For more information: See Customer Service Part I: Managing Returns.

Define Special Forms (C03)

Purpose: Use this screen to indicate the forms the system should generate.

CSR0389 ENTER Define Special Forms 3/28/95 9:36:37 System Delivered Company Return Acknowledgement . . (Y/N) Gift Acknowledgment . . (Y/N) Gift Acknowledge Print Program Application Code . . . . . C/S Application Group. . . . . ALL F3=Exit F12=Cancel

Return Acknowledgement (C04)

If you enter Y in this field, the system collects customer data for a return acknowledgment, which prints when a returned item is received by the warehouse.

If you enter N, return acknowledgments are not printed.

Note: This system control value is not currently implemented.

Automatic Generation of Gift Acknowledgement (B92)

Enter the code that indicates whether to print Gift Acknowledgements for Gift orders (The Gift field on the order header is set to Y) when you generate pick slips, when you bill the orders, or not at all. The system prints gift acknowledgements only if the sold-to customer would not receive a shipment notification email.

Valid values are:

• P = The system prints gift acknowledgments for Gift orders when you generate pick slips, provided the Gift Order Acknowledgement Print Program (B90) system control value is set to a valid program name and the sold-to customer is not eligible to receive a shipment notification email. See Working with Pick Slip Generation (WPSG) for more information on generating pick slips and gift acknowledgements.

• B = The system prints gift acknowledgments for Gift orders when you bill the orders, provided the Gift Order Acknowledgement Print Program (B90) system control value is set to a valid program name and the sold-to customer is not eligible to receive a shipment notification email. See Working with the BILL_ASYNC Job for more information on the updates made and processes run through the billing async job.

• N = The system does not print gift acknowledgements regardless of whether the sold-to customer is eligible to receive a shipment notification email.

When is the customer eligible to receive a shipment notification email? See Shipment and Return Confirmation Emails for a discussion.

Gift Order Acknowledgement Print Program (B90)

Enter the system name of the letter that supplies the text for Gift Acknowledgements. This is a 6-position, alphanumeric field. To generate gift order acknowledgment, the system control value, Automatic Generation of Gift Acknowledgement (B92), must be set to P or B and the customer must not be eligible to receive a shipment email notification. The base print program is FLR0389.

Auto Soldout Cancel Reason (C20)

Purpose: Use this screen to define the Cancellation Reason code assigned to sold out items during the Process Auto Sold Outs program.

MSR0054 OPEN Change System Control Value 5/23/94 12:28:10 Description . : Auto Soldout Cancel Reason Number . . . . 01 02 03 04 Narrative . . .   Application . : C/S Applic group : Sequence# . . :   F3=Exit F12=Cancel

Number field: Enter the Cancellation Reason code to identify the reason for selling out an item during Processing Auto Soldout Cancellations (MASO).

When you run this program, the system checks the value in the S/O control field in the Item record, which specifies to sell out the item immediately, when the on-hand quantity (in the warehouse) reaches zero, or when the on-hand plus the on-order quantities (ordered on purchase orders) reach zero.

The system changes the status of the appropriate items to “sold out,” and uses the default Cancellation Reason code to track the reason for selling out the item. Additionally, the system prints sold out notification cards for all orders that contain items that were sold out through the Auto Sold Outs program. The Cancellation Reason code you enter here is stored in the Cancel reason code field in the Order Detail file and displayed at the Display Order Line History Screen.

Cancellation reason codes are defined in and validated against the Cancel Reason file; see Customer Service Chapter 5: Establishing Cancel Reason Codes (WCNR).

Print Credit Card Credit Acknowledgments (C35)

Purpose: Use this screen to define whether the system prints credit card credit acknowledgment cards if there is a refund or balance due on a credit card order.

MSR0052 OPEN Change System Control Value 3/28/95 14:29:14 Description . : Print Credit Card Credit Acknowledgments Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to print acknowledgment cards automatically for refund (credit) or balance due (debit) transactions against an order paid with a credit card. Credit card credits print when you enter Y in the Generate C/C credits field at the Process Refunds Screen.

If you are printing credit card credits, you must complete the Credit Card Credit Acknowledgment Print Program (D22) system control value.

This card notifies the customer of any credits against the credit card for an order.

Note: This field does not control whether you generate credit card credit email notifications or the Outbound Email XML Message (CWEmailOut); as long as you specify a valid program in the Credit Card Credit Acknowledgement E-Mail Program (H08).

Enter N if you do not want to print these notices.

FTC -- # of Days to Add for Special Handling (C67)

Purpose: Use this screen to define the number of days added to the expected PO receipt date for items with special handling.

MSR0054 OPEN Change System Control Value 3/28/95 10:08:02 Description . : FTC -- # Of Days to Add for Special Handling Number . . . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the number of days for the system to add to the expected PO receipt date for items with special handling. The system performs this calculation for FTC (Federal Trade Commission) or backorder notifications, which you use to advise the customer about an out of stock item and specify the date when the item will arrive. This allows the customer to cancel the order, if desired. In general, you set up the system to notify mail order customers immediately about a backordered item, while you advise customers who order by phone at the time they place their order; see Customer Service Chapter 1: Establishing Order Types (WOTY).

Example: The customer places a mail order for a trophy, which is currently backordered. Because you received the order through the mail and there is a backorder, you must send a backorder notification to the customer.

The arrival date on this card takes into account PO layering (in which previous backorders are fulfilled before the new order) and special handling (engraving the name plate on the trophy). If the vendor is expected to ship the trophies to you on April 1st and the value in this field is 19, the date on the backorder notification is April 20.

For more information: See Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications for more information on PO layering and backorder cards.

FTC -- # of Days to Add for Drop Ships (C68)

Purpose: Use this screen to define the number of days added to the expected arrival date for drop shipped items.

MSR0054 OPEN Change System Control Value 3/28/95 10:08:02 Description . : FTC -- # Of Days to Add for Drop Ships Number . . . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the number of days for the system to add to the expected arrival date for drop shipped items. A drop shipped item is an item that you sell, but do not stock in your warehouse. Instead, your vendor ships the item directly to the customer.

Use this field to define the additional time it takes for your vendor to ship a drop shipped item. The system performs this calculation for backorder notifications in which you notify the customer that an item is backordered and when you expect it to arrive. This allows the customer to cancel the order, if desired.

The expected ship date for drop ship items is calculated by adding the current date + FTC -- # of Days to Add for Drop Ships (C68) + the Lead days for the vendor item.

Note: Items shipped through CWCollaborate use a different calculation for expected ship date. See the Assign Drop Ship Expected Ship Date (I59) system control value for more information.

In general, you set up the system to notify mail order customers immediately about a backordered item, while you advise customers who order by phone at the time they place their order.

Displayed where? The system displays the expected ship date on screens and includes it in notifications and reports if the Assign Drop Ship Expected Ship Date (I59) is set to Y. See that system control value for more information.

For more information:

• setting up the Order Type file: Customer Service Chapter 1: Establishing Order Types (WOTY)

• PO layering and backorder cards: Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications

FTC -- Action after Second Notification (C70)

Purpose: Use this screen to define the next action to take after you have sent the second backorder notification to a customer for a backordered item.

MSR0051 OPEN Change System Control Value 3/28/95 12:01:07 Description . : FTC -- Action after second notification Code . . . . . CANCEL CONTINUE STOP Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Code field: Enter one of these codes to define the action to take after issuing the second backorder notification for an item:

CANCEL	The order appears on the Backorder Cancellation Register that the system produces when you generate backorder cards. You can cancel the backordered item through Order Maintenance, or contact the customer to suggest another item. The date that an order is eligible to appear on the Backorder Cancellation Register is based on the value in the Days after 2nd Backorder Notification to Cancel Order (D07) system control value. For more information: See Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications. Note: You must have this system control value set to CANCEL to use the Work with Backorders Pending Cancellation menu option. See the description of the FTC--Second Notice Output (E68) system control value.
CONTINUE	The system issues another backorder notification at the appropriate time, which is: • the same number of days as previous backorder notices, or • when the delivery date changes, or • when you miss the promised delivery date
STOP or blank	The system does not issue further backorder notifications.

FTC -- # of Days for Items without Expected Ship Date (C71)

Purpose: Use this screen to define the number of days added to the expected arrival date for items with no open purchase orders.

MSR0054 OPEN Change System Control Value 3/28/95 11:51:06 Description . : FTC - # Of Days for Items without Expected Ship Date Number . . . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the number of days for the system to add to the expected arrival date for an item that is not in stock and for which there are no open (unreceived) purchase orders. The system performs this calculation for backorder notifications in which you notify the customer that an item is out of stock and specify the date when it will arrive. This allows the customer to cancel the order, if desired.

Note: Although you can enter any value in this field, the FTC rule for this situation is 30 days maximum.

E-Commerce item availability: If you use the E-Commerce Interface, you can send availability information to the web storefront when:

• you submit the ECAVAIL periodic function (program name ECR0144). This periodic function downloads the current available quantity for every item and SKU for which you have downloaded information to your web storefront.

• an item’s availability falls below a specified Item Availability Web Threshold, triggering an interactive download.

• an E-Commerce Item Availability Request Message (CWItemAvail) is received from the web storefront.

A flag in the item availability information indicates whether the date expected was based on an actual purchase order, or was defaulted based on the FTC -- # of Days for Items without Expected Ship Date (C71) system control value:

• 1 = date was defaulted based on the FTC -- # of Days for Items without Expected Ship Date (C71) system control value.

• 0 = actual purchase order date from the PO Layering (POLAYR) file. Note: The system also sets this flag to 0 if the Include Projected Returns in Available Quantity for Download (J62) is set to N, the Include Projected Returns in Available Quantity for OE (L68) system control value is set to Y, and the item/SKU:

• has a soldout control value with a status of 2 (include on-order quantity in soldout calculation),

• has no available quantity, and

• is associated with a Projected return quantity.

Examples:	Item AB100 has available quantity of 100 and an open purchase order that is due on May 15, 2002. Result: Quantity available = 100 Date expected = 05152002 Default delivery date = 0
	Item CB200 has no available quantity, and there are no open purchase orders. The current date is May 1, 2002, and the FTC - # Of Days for Items without Expected Ship Date system control value is set to 30 days. Result: Quantity available = 0 Date expected = 05312002 Default delivery date = 1

For more information:

• how purchase order layering works, and how to generate backorder notices: Purchase Order Layering and Backorder Notifications

• an overview of downloads to the web storefront through the e-commerce interface: E-Commerce Download Overview

• the Item Availability Response process: E-Commerce Item Availability Processing

• using this value to have the system calculate the expected ship date for backordered items in order entry: the Calculate Expected Date in OE if No PO (J61) system control value

• E-Commerce Item Availability Request Message (CWItemAvail)

• E-Commerce Item Availability Response Message (CWAvailResponse) layout

• set items: Entering Set Information (WSET)

Label 1-Up Printing Program (C83)

Purpose: Use this screen to define the name of the program that prints a single row of labels for catalog mailings.

MSR0053 OPEN Change System Control Value 3/28/95 9:56:26 Description . : Label 1-Up Printing Program System name . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

System name field: Enter the name of the program that prints 1-up labels, which are labels that print in a single row. You can print 1-up labels for catalog requests or when you generate your house list, which is a segment of your customer base to whom your list broker sends catalogs.

The standard 1-up printing programs (to print “1 across” labels) are:

MSR0613: This program prints a six-line label with city, state, and country (country is spelled out in full) on the last line. This format does not conform to Post Office requirements, which specify that the bottom line of the address should show only the country.

MSR1273: This program prints a seven-line label with country (spelled out in full) on the last line if the address is in a foreign country (the country is different from the Default Country for Customer Address (B17)). This format conforms to Post Office requirements. It requires a label form that allows seven lines of address information.

MSR1286: This program prints a seven-line label that includes the individual customer and the individual’s mail stop, if any. The label also includes country (spelled out in full) on the last line if the address is in a foreign country (the country is different from the Default Country for Customer Address (B17)) and conforms to Post Office requirements. You would use this format only if you take catalog requests for individual customers; see Enable Catalog Request at Individual Level (H81).

This field is required if printing this type of label; otherwise, complete the Label 4-Up Printing Program (C84) system control value, in which the system prints a row consisting of 4 labels.

Label 4-Up Printing Program (C84)

Purpose: Use this screen to define the name of the program that prints 4 labels per row for catalog mailings.

MSR0053 OPEN Change System Control Value 3/28/95 9:56:26 Description . : Label 4-Up Printing Program System name . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

System name field: Enter the name of the program that prints 4-up labels, which are labels that print 4 labels to a row. You may print 4-up labels for catalog requests or when you generate your house list, which is a segment of your customer base to whom your list broker sends catalogs.

The standard 4-up printing programs (to print “4 across” labels) are:

MSR0614: This program prints six-line labels with city, state, and country (country is spelled out in full) on the last line. This format does not conform to Post Office requirements, which specify that the bottom line of the address should show only the Country.

MSR1274: This program prints a seven-line label with country (spelled out in full) on the last line if the address is in a foreign country (the country is different from the Default Country for Customer Address (B17)). This format conforms to Post Office requirements. It requires a label form that allows seven lines of address information.

MSR1287: This program prints a seven-line label that includes the individual customer and the individual’s mail stop, if any. The label also includes country (spelled out in full) on the last line if the address is in a foreign country (the country is different from the Default Country for Customer Address (B17)) and conforms to Post Office requirements. You would use this format only if you take catalog requests for individual customers; see Enable Catalog Request at Individual Level (H81).

This field is required if printing this type of label; otherwise, complete the Label 1-Up Printing Program (C83) system control value, in which the system prints one label per row.

Backorder Card Print Program (D04)

Purpose: Use this screen to define the name of the program to prints backorder notification cards.

MSR0053 OPEN Change System Control Value 3/28/95 10:46:48 Description . : Backorder Card Print Program System name . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

System name: Enter the name of the program to print backorder notification cards. The standard backorder card print program is BOR0008. If you have the Validate Prefix (I27) system control value set to Y, the base backorder notification print program is BOR0037.

The FTC requires you to send backorder notices to notify customers when an item is currently out of stock, and when you expect the item to arrive. Generally, you need to generate backorder notices immediately for mail orders, while you can inform customers who phone in their orders if an item is out of stock.

Backorder cards print when you run the Generate Backorder Cards option (fast path = GBOC). See Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications.

Days after 2nd Backorder Notification to Cancel Order (D07)

Purpose: Use this screen to define the number of days after the second backordered item notification that the system includes the order on the Backorder Cancellation Register.

MSR0054 OPEN Change System Control Value 3/28/95 13:53:04 Description . : Days after 2nd Backorder Notification to Cancel Order Number . . . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the number of days after generating the second backorder notification to include the order on the Backorder Cancellation Register.

Complete this field only if you entered CANCEL in the FTC -- Action after Second Notification (C70) system control value.

The order containing the backordered item appears on the Backorder Cancellation Register the next time you generate backorder notices. You can cancel the item through Order Maintenance or contact the customer to suggest another item.

For more information: See Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications.

Update of Current Source Code in Customer File (D08)

Purpose: Use this screen to define when the system updates the customer record with the current source code.

MSR0051 OPEN Change System Control Value 3/28/95 12:59:36 Description . : Update of Current Source Code in Customer file Code . . . . . O H N Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Code field: Enter the code that defines when the system updates the Current source code field in the Sold To Customer record.

Choices are: O (Order Entry), H (House List), or N (Do not update).

Update during order entry: Enter O to update the Current source code field in the Sold To Customer record when entering an order. The system updates the Current source code field with the code you enter in the Source field on the Order Entry screen.

The source code identifies a segment of your customer base (house list) to whom you mail a catalog.

Update when generating house list: Enter H to update the Current source code field in the Sold To Customer record when you generate your house list. A house list is a list of names extracted from your customer base, to whom you mail a catalog. You assign a source code to each list of names you generate from your house list.

If using this method, the system updates the Current source code field as soon as you include the customer in a new catalog mailing, but before the customer places a new order for items in the catalog.

Do not update: Enter N if you do not want to update the Current source code field. If so, the Current source code field always has the same value as the Original source code field. The Original source code field is never updated because it enables you to track how you first obtained the customer name.

Default Associate Code (D09)

Purpose: Use this screen to define the value that defaults to the Associate field for new customers.

MSR0052 OPEN Change System Control Value 3/28/95 13:34:09 Description . : Default Associate Code Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter the value you want to load into the Associate field for new customers entered through Order Entry or Catalog Requests.

A customer identified as an “associate” receives the associate price defined for items rather than the regular price. An associate customer is typically a member who is eligible for discounted prices.

Enter Y in this field to identify all new customers as “associates;” otherwise, enter N. You may override the default value, as needed.

Leave this field blank if the operator must complete the Associate field when entering an order or a catalog request for a new customer.

Default Mail Name (D10)

Purpose: Use this screen to define the value that defaults to the Mail field for new customers.

MSR0052 OPEN Change System Control Value 3/28/95 13:44:34 Description . : Default Mail Name Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter the value you want to load into the Mail field for new customers entered through order entry or catalog requests. This value also defaults when you create a new individual; see Creating and Updating Individuals.

The value in the Mail field indicates whether the customer receives future catalogs.

Enter Y in this field to indicate that you mail catalogs to the customer; otherwise, enter N. You can override the default as needed.

Leave this field blank if the operator must complete the Mail field when entering an order or a catalog request for a new customer.

Entity: If you track customer history by entity, you can set the Mail flag separately for individual entities. See Track Customer History at Entity Level (F89).

Default Rent Name (D11)

Purpose: Use this screen to define the value that defaults to the Rent field for new customers.

MSR0052 OPEN Change System Control Value 3/28/95 13:44:34 Description . : Default Rent Name Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter the value you want to load into the Rent field for new customers entered through order entry or catalog requests. This value also defaults when you create a new individual; see Creating and Updating Individuals.

The value in the Rent field indicates whether you can sell the customer's name to another company for their catalog mailings.

Enter Y in this field to indicate that the customer's name can be sold; otherwise, enter N. You may override the default value, as needed.

Leave this field blank if the operator must complete the Rent field when entering an order or a catalog request for a new customer.

Credit Card Credit Acknowledgment Print Program (D22)

Purpose: Use this screen to identify the program that prints credit card acknowledgment cards.

MSR0053 OPEN Change System Control Value 3/28/95 14:47:06 Description . : Credit Card Credit Acknowledgment Print Program System name . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

System name field: Enter the name of the program that prints credit card acknowledgment cards, which are produced for a refund or balance due transaction against a credit card order. This card notifies the customer of any activity against the credit card for an order.

The standard program for printing credit card credit acknowledgments is program number CSR0559. Credit card credits print when you enter Y in the Generate C/C credits field at Processing Refunds (MREF). You can also generate emails or the Outbound Email XML Message (CWEmailOut) to notify customers of credit card credits.

If you are printing credit card credits, you must complete the Print Credit Card Credit Acknowledgments (C35) system control value.

Alternate currency pricing: The refund amount that prints on the credit card acknowledgement card is in the alternate (foreign) currency if the Use Alternate Currency Pricing (H89) system control value is set to Y and a currency code and conversion rate are defined in the Order Header Extended file.

Refund Check Print Program (D23)

Purpose: Use this screen to identify the program that prints refund checks.

MSR0053 OPEN Change System Control Value 3/28/95 14:47:06 Description . : Refund Check Print Program System name . . Narrative . . . Application . : C/S Applic group . Sequence# . . . F3=Exit F12=Cancel

System name field: Enter the name of the program that prints refund checks, which are produced for an overpayment, cancellation, sellout, or return on an order.

The standard program for printing refund checks is program number CSR0836. Refund checks print when you enter Y in the Generate refund checks field at Processing Refunds (MREF).

Merchandise Credit Print Program (D29)

Purpose: Use this screen to define the program to print merchandise credits.

MSR0053 CHANGE Change System Control Value 7/09/97 14:45:54 Description . : Merchandise Credit Print Program System name . . Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the program name the system uses to print merchandise credits. The base program is CSR0571.

You might issue a merchandise credit when the customer paid for the order with a coupon or credit, or when the customer prepaid on the order but returned merchandise after a grace period. Enter Y in the Generate Merchandise Credits field at Processing Refunds (MREF) to generate merchandise credits.

If you leave this field blank the system does not print merchandise credits, and just lists the credits on the Coupon/Credit Register.

Bonus Credit Print Program (D30)

Purpose: Use this screen to define the program to print bonus credits.

MSR0053 CHANGE Change System Control Value 7/11/97 14:41:42 Description . : Bonus Credit Print Program System name . . Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the program name the system uses to print bonus credits. The base program is CSR0575.

Bonus credits are incentives for customers to choose merchandise credits as their form of refund. For example, if the customer is due a refund check for $50.00 and the bonus credit percentage defined is 10%, the total amount of the refund (if applied as a payment) is $55.00.

Enter Y in the Generate Merchandise Credits field at Processing Refunds (MREF).

If you leave this system control value blank the system does not print bonus credits., and just includes the bonus credits on the Coupon/Credit Register.

Sale Credit Print Program (D31)

Purpose: Use this screen to define the program to print sale credits.

MSR0053 CHANGE Change System Control Value 7/11/97 14:49:35 Description . : Sale Credit Print Program System name . . Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the program name the system uses to print sale credits. The base program is CSR0574.

The system generates a sale credit for a return if:

• the Generate Sale Credit for Orders with Sale Items (I64) system control value is set to Y, and

• the item is flagged as a Sale item in the Item Offer or SKU Offer for the order detail line, and

• the pay type:

• is a coupon/credit pay category (category 5), or

• has an Alt refund type (Alternate refund type) that is a coupon/credit pay category, or

• has an Alt refund category (Alternate refund category) of coupon/credit

You might issue a sale credit when the customer paid for a sale item on an order with a coupon or credit, or when the customer prepaid for a sale item on the order, but returned the sale item after a grace period. Enter Y in the Generate Merchandise Credits field at Processing Refunds (MREF) to generate sale credits.

If you leave this field blank the system does not print sale credits, and just lists the sale credits on the Coupon/Credit Register.

Customer Return Label Print Program (D35)

Purpose: Use this screen to define the print program to print a customer return label automatically when you perform a return in order entry or order maintenance.

MSR0053 CHANGE Change System Control Value 6/16/99 12:40:09 Description . : Customer Return Label Print Program System name . . Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the print program name you wish the system to use to print a customer return label when you perform a return in order entry or order maintenance.

When entering the return in order entry or order maintenance, you must use a return disposition value that has the Affect inventory field set to Y in order to produce a label.

A separate spool file prints for each unit returned.

There are 2 standard programs for printing customer return labels:

INR0919 (without UPC code): This program prints 1-up labels (single row of labels). The contents of this customer return label are:

• item number, followed by SKU code, if any

• the returned quantity

• the location in the warehouse to return the item to stock

INR1839 (with UPC code): This program prints 1-up labels (single row of labels). The contents of this customer return label are:

• item number, followed by SKU code, if any

• the returned quantity

• the location in the warehouse to return the item to stock

• UPC barcode assigned to the item/SKU, in numeric format. If more than 1 UPC code is defined for the item/SKU, the system uses this hierarchy to determine which UPC code to default:

• UPC code defined for UPC type E13. If more than one UPC code is defined for type E13, default the first UPC code in alphanumeric sequence for that type.

• UPC code defined for UPC type E8. If more than one UPC code is defined for type E8, default the first UPC code in alphanumeric sequence for that type.

• UPC code defined for UPC type UA. If more than one UPC code is defined for type UA, default the first UPC code in alphanumeric sequence for that type.

• UPC code defined for UPC type UE. If more than one UPC code is defined for type UE, default the first UPC code in alphanumeric sequence for that type.

Sample customer return label INR0919:

2L04SKU1 RED WMNS LRGE 1 R010101

Sample customer return label INR1839:

2L04SKU1 RED WMNS LRGE 1 R010101 200411172

Determining location: The location is determined by the disposition code entered for the return. The disposition code identifies how you should handle the returned item (return to active inventory, where to place the item, etc.). The disposition code uses either the item's primary warehouse location (as defined in the Item record) or identifies the specific warehouse and location in which to place the item. If you override the default location, the customer return label prints the location you specify.

Note: The Creating Item Labels (PILB) menu option also uses this system control value to print item labels. If you do not specify a program in this system control value, you cannot print item labels using this menu option.

Default Source Code for Batch Catalog Requests (D37)

Purpose: Use this screen to define the batch source code to use for catalog requests that you receive through an interface.

MSR0051 CHANGE Change System Control Value 7/20/99 15:02:09 Description . : Default Source Code for Batch Catalog Requests Code . . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the source code to use for catalog requests that you receive through an interface, such as the phone, e-commerce, or catalog request interface, if a source code is not already specified.

For more information:

• phone interface: Order Entry Chapter 31: Using the Phone Interface

• e-commerce interface: E-Commerce Interface, Chapter 76: Working with E-Commerce Job Control (EJCT)

• catalog request interface: Customer Service Chapter 112: Working with the Catalog Request Interface (WCRU)

Display Customer Notes in LIFO Sequence (D55)

Purpose: Use this screen to define whether the most recently entered customer notes display first or whether they display in the order in which they were entered.

MSR0052 CHANGE Change System Control Value 2/12/96 15:06:20 Description . : Display customer notes in LIFO sequence. Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 103 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if the latest notes entered for the customer should appear before earlier notes; otherwise, enter N to display the notes in the sequence in which they were entered.

If you enter Y in this field, the notes are listed in LIFO (last-in, first-out) sequence, which means that they appear in descending date sequence.

Example:

Note	Date
Call customer about order #301458.	02/12/96
Credit given to customer for postage.	12/10/95
New customer -- discount 5%.	05/22/95

If you leave this field blank or enter N, the notes appear in FIFO (first-in, first-out) sequence, which means that they appear in ascending date sequence. This way, the notes entered first appear first. The more recent notes appear towards the bottom.

Example:

Notes	Date
New customer -- discount 5%.	05/22/95
Credit given to customer for postage.	12/10/95
Call customer about order #301458.	02/12/96

Note: Customer notes default to FIFO (earliest-to-latest) sequence.

You can enter, change, display or delete customer notes by:

• using option 23 or F23 in Work with Customers (fast path = WCST)

• pressing F10 from Order Entry, Order Maintenance or Order Inquiry, then selecting the Customer Messages option.

Sample Customer Notes screen:

OER0140 CHANGE Edit Customer Notes 2/12/96 16:19:28 COMMERCIALWARE Customer : 13 PANZERA, SALVATORE Notes User Date Call customer about order #301458. LEE_H 21296 Credit given to customer for postage. ERIK_H 121095 New customer -- discount 5%. LESLIE_G 52295 F3=Exit F12=Cancel

The cursor is positioned at the first blank line on the Edit Customer Notes screen. After you enter a new note, the system checks this system control value and re-displays the notes in LIFO or FIFO sequence.

Example: This example shows a customer message screen before and after you enter a new message.

Before...

Note	Date
Call customer about order #301458.	02/12/96
Credit given to customer for postage.	12/10/95
New customer -- discount 5%.	05/22/95
Send 2 spring catalogs.	02/14/96<-- (new message)

After... (LIFO sequence):

Note	Date
Send 2 spring catalogs.	02/14/96<-- (new message)
Call customer about order #301458.	02/12/96
Credit given to customer for postage.	12/10/95
New customer -- discount 5%.	05/22/95

OR After...(FIFO sequence):

Note	Date
New customer -- discount 5%.	05/22/95
Credit given to customer for postage.	12/10/95
Call customer about order #301458.	02/12/96
Send 2 spring catalogs.	02/14/96<-- (new message)

If you enter 2 or more messages on a single day, the second message displays below the first message with no message entry date.

Example:

Note	Date
Send 2 spring catalogs.	02/14/96<-- (new message)
Send 2 1996 catalogs, too.	- (second message)
Call customer about order #301458.	02/12/96
Credit given to customer for postage.	12/10/95
New customer -- discount 5%.	05/22/95

Number of Days to Delay Initial Backorder Notice (D89)

Purpose: Use this screen to define the number of days to delay sending backorder notices to your customers when they place mail orders for merchandise that is currently out of stock.

MSR0054 CHANGE Change System Control Value 7/26/96 13:52:49 Description . : Number of Days to Delay Initial Backorder Notice Number . . . . 30 Narrative . . . Application . : ALL Applic group . C/S Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the number of days the system should delay before sending a notice to a customer who ordered backordered merchandise.

The system uses this value only when calculating backorder notification dates for order types that require immediate notification (the Immediate B/O (Immediate backorder notice) field in the Order Type file is set to Y). Typically, you would want to notify customer immediately about backordered items if they place an order through the mail or fax; you can inform customers who order by phone at the time you take their orders if an item they want is currently backordered.

The FTC requires you to notify your customers if an item they have ordered is backordered, and advise them when you expect the item to ship. You can use this System Control Value to build in a delay period if you do not believe it is necessary to notify your customers about out-of-stock items that you can ship within the given delay period.

Example: You print a notice on your order forms to allow 30 days for shipping, and set this System Control Value to 30. A customer orders an item on September 1 that is currently out of stock. The delay date for this order is October 1. You expect to receive a purchase order for this item by September 7. The system does not generate a backorder notice to the customer, because you expect to ship the item before 30 days has passed.

If the date you expect to receive this purchase order changes to October 5, or if October 1 passes and you have not received the purchase order, the system does generate a backorder notice.

Similarly, if a customer orders an item on September 1 for an item on an open purchase order dated October 20, the system does generate a backorder notice because the expected ship date exceeds the delay date.

Set this field to 0 if you do not want to build in a delay period for generating backorder notices to your customers.

Note: You should run batch purchase order layering before generating backorder cards, to be sure that all information on the system regarding purchase order arrival dates and expected ship dates on related order detail lines is correct.

For more information: See Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications for more information on generating backorder notices and running batch purchase order layering.

Update a Bill-to Address with Sold-to Address Changes (E13)

Purpose: Use this screen to define whether to open a window when you change a Sold-to address with a permanent Bill-to account, allowing you to apply the Sold-to changes to the Bill-to address.

MSR0052 CHANGE Change System Control Value 10/10/96 11:42:29 Description . : Update Bill-to Address with Sold-to Address Changes Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Updating a Bill-to Address with Sold-to Address Changes window to display in Order Entry, Order Maintenance and Work with Customers when you change a Sold-to address that is linked to a permanent Bill-to record.

Note: Because this system control value affects interactive order entry, it does not control update of the bill-to customer through e-commerce orders or the phone order load.

Enter N or leave this field blank if you do not want the pop-up window to display when you update the Sold-to customer.

Sample Display/Update Bill To screen:

Display/Update Bill to New Address (Sold To) KIM AUCLAIR SANDER HOSPITAL Delivery Code B ROBIN ROAD PO Box Y/N N Day 508 / 555 - 0100 Ext.: 123 Eve 0 / 0 - 0 Ext.: Fax 0 / 0 - 0 Ext.: LAWRENCE MA 01701 USA Bill to #: 170 KIM AUCLAIR STRESS HOSPITAL Delivery Code B ROBIN ROAD PO Box Y/N : N Day 508 / 555 - 0101 Ext.: 123 Eve 0 / 0 - 0 Ext.: Fax 0 / 0 - 0 Ext.: LAWRENCE MA 01701 USA F9=Accept F11=Reject

The Display/Update Bill to window displays the name and address of the Sold-to customer with its changes in the upper half of the window, and its linked Bill-to record without the changes in the bottom half of the window.

These fields for the bill-to customer record are updated when you change its linked Sold-to customer:

• prefix

• first name

• middle initial

• last name

• suffix

• company

• street

• apt/suite

• address line 2

• address line 3

• address line 4

• postal code

• city

• state

• country

• delivery code

• PO box

• day phone number/extension

• evening phone number/extension

• fax phone number/extension

For more information: See Customer Service Chapter 28: Creating and Updating Sold-to Customers (WCST) for more information.

You can also update bill-to address changes with sold-to address changes in the MBS Work file if the old address of the sold-to customer is an exact match of the old address of the bill-to customer. The MBS Work file contains address information from the National Change of Address (NCOA) Service.

These fields must be an exact match in order for the bill-to address to update with the sold-to address in the MBS Work file:

• Prefix

• First Name

• Middle Initial

• Last Name

• Suffix

• Company

• Street

• Apartment/Suite

• Address Line 2

• Address Line 3

• Address Line 4

• Postal Code

• City

• State

• Country

• Delivery Code

• P.O. Box

For more information: See Customer Service Chapter 145: Loading Address Updates.

Call Tag Print Program (E17)

Purpose: Use this screen to define whether to use 1-up or 2-up forms when you print call tags.

MSR0053 CHANGE Change System Control Value 7/11/97 10:23:20 Description . : Call Tag Printing Program System name . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

System name: Enter CSR0633 or leave this field blank to print call tags 2-up. Enter CSR0495 to print call tags 1-up. You can also enter your own user-defined program for call tags.

Your shipper uses call tags when picking up items that your customers are returning to you. A 2-up form has two labels to a row, and a 1-up form has one label to a row.

Sample 2-up call tag:

Tag#: 6666666 66/66/66 Tag#: 6666666 66/66/6 xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xx xxxxx xxxxxxxxxxxxxxxxxxxx xx xxxxx Order # 66666666 - 666 6666.666 Order # 66666666 - 666 6666.66 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xx xxxxx xxxxxxxxxxxxxxxxxxxx xx xxxxx Tag#: 19 7/15/97 Tag#: 20 7/15/97 PORTWAY, VALERIE PORTWAY, EDNA CLINICAL COMPUTING CLINICAL COMPUTING 11 LONGWOOD AVENUE 11 LONGWOOD AVENUE FRAMINGHAM MA 01702 FRAMINGHAM MA 01702 Order # 1237 - 1 12.000 Order # 1238 - 1 12.00 SUMMER WAREHOUSE SUMMER WAREHOUSE The Mail Order Company The Mail Order Company 12 FLAGG DR 12 FLAGG Dr FRAMINGHAM MA 01702 FRAMINGHAM MA 01702

For more information: See Processing Call Tags (MCTG).

Print Alpha $ Amount on Refund Check (E30)

Purpose: Use this screen to define whether the system prints refund checks with an alphanumeric and a numeric dollar amount.

MSR0054 OPEN Change System Control Value 3/28/95 13:53:04 Description . : Print Alpha $ Amount on Refund Check Yes/No . . . . (Y,N) Narrative . . . Application . : O/E Applic group . ALL Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter Y in this field for refund checks to print with an alphanumeric and a numeric dollar amount.

Set this field to N or leave it blank to print refund checks with only a numeric dollar amount.

An alphanumeric dollar amount prints on a Refund Check with the base Refund Check Print Program (D23), CSR0836, and any custom programs that are set up for this feature. Refund checks print when you enter Y in the Generate refund checks field at Processing Refunds (MREF).

Alternate currency pricing: If you Use Alternate Currency Pricing (H89), the system prints an alphanumeric and numeric amount on the refund checks if your Refund Check Print Program (D23) is CSR0561.

For more information: See Working with Refunds, Writeoffs and Balances Due (WREF).

Edit for Duplicate Catalog Requests (E46)

Purpose: Use this screen to define whether the system checks for duplicate records when you create a new catalog request.

MSR0052 CHANGE Change System Control Value 7/11/97 9:00:04 Description . : Edit for duplicate Catalog Requests. Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to see if there is already an existing catalog request for the customer (and, optionally, individual) when you create a new catalog request using the Work with Catalog Request menu option, phone interface, or e-commerce catalog request process.

Checking for Duplicate Catalog Requests

Note:

• The system does not display an error message at the Create Catalog Request Screen in Work with Catalog Requests or the Change Catalog Request Screen in Work with Catalog Request Interface if the catalog request is a duplicate.

• If the existing request has already been printed, and the Edit for Duplicate catalog Requests system control value is set to Y, the system changes the printed status of the existing request to N.

The Enable Catalog Request at Individual Level (H81) system control value controls whether you can specify an individual on a catalog request.

Enter N or leave this field blank if you do not want the system to check for duplicate records when you create a new catalog request.

In this case, if you enter a catalog request and a duplicate already exists, the system creates a new catalog request.

For more information:

• work with catalog requests and catalog request interface: Customer Service Chapter 109: Entering Catalog Requests (WCAT), Chapter 112: Working with the Catalog Request Interface (WCRU)

• phone interface catalog request: Order Entry: Chapter 33: Transferring Remote Orders (TPHO), Chapter 34: Loading Remote Orders (LPHO)

• e-commerce catalog request process: System Operations Chapter 76: Working with E-Commerce Job Control (EJCT)

Prompt for Mandatory Demographics in Order Maintenance (E60)

Purpose: Use this screen to define whether to prompt for completion of mandatory demographic information in order maintenance.

MSR0052 CHANGE Change System Control Value 4/24/97 15:41:29 Description . : Prompt for Mandatory Demographics in Order Maintenance Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Work with Customer Profile Screen to appear automatically in Order Maintenance if a mandatory demographic field for the customer is blank.

You create demographic fields through Chapter 16: Setting Up Customer Profiles (WPFL) in order to track personal information on your customers such as age, income, gender, etc. If you flag a demographic category as mandatory, and if you have not yet obtained the information for this field from the customer, the Work with Customer Profile screen appears automatically in Order Entry when you press F9 to accept the order. The screen prompts you to obtain the information from the customer, although you have the option of exiting the screen without completing the mandatory field.

Enter N in this field or leave it blank if you do not want the Work with Customer Profile screen to appear automatically when you maintain an order.

Note: If you define one of the valid values for the mandatory category as a default value, the Work with Customer Profile screen never opens in either Order Entry or Order Maintenance. The system defaults the selected value in this field automatically.

FTC--Number of Days Prior to Next Backorder Date to Generate Second Notice (E67)

Purpose: Use this screen to define the number of days before a second backorder notice is due to generate the notice or write the backorder record.

MSR0054 CHANGE Change System Control Value 7/29/97 11:47:22 Description . : FTC - # of days prior Next B/O Date to generate 2nd notice Number . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the number of days before the next backorder date to generate second backorder notices or write a record to the Backorder Cancellation Pending file (BOCANP).

You can use this system control value to:

• generate the backorder notice early enough in advance to be sure you notify the customer in time before the order is flagged for cancellation; or,

• generate the notice or create the record in advance, so that you can correct the backorder and ship the order without having to notify the customer.

The FTC--Second Notice Output (E68) system control value controls whether you generate second backorder notices, create a record in the file, or both.

Leave this field blank if you do not want to generate second notices in advance.

Important: The FTC -- Action after Second Notification (C70) system control value must be set to CANCEL in order for the system to generate second backorder notices or records in advance. If this system control value is not set to CANCEL, the system ignores the setting of the FTC--Number of Days Prior to Next Backorder Date to Generate Second Notice value.

FTC--Second Notice Output (E68)

Purpose: Use this field to indicate whether to generate second backorder notices, create records in a file, or both.

MSR0051 CHANGE Change System Control Value 7/29/97 13:53:01 Description . : FTC - Second Notice Output Code . . . . . FILE FILE/PRINT PRINT Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code representing whether to generate backorder notices (cards, emails, or the Outbound Email XML Message (CWEmailOut)), create records in the Backorder Cancellation Pending file (BOCANP), or both, for second notices. Valid values are:

• FILE: Generate Backorder Cards (GBOC) creates records in the Backorder Cancellation Pending file for second backorder notices. You can use the Work with Backorders Pending Cancellation menu option to work with these records or generate notices.

• FILE/PRINT: Generate Backorder Cards (GBOC) generates second notices and creates records in the Backorder Cancellation Pending file. You can use the Work with Backorders Pending Cancellation menu option to work with these records, but not to print notices.

• PRINT or blank: Generate Backorder Cards (GBOC) generates second backorder notices. You cannot use the Work with Backorders Pending Cancellation menu option.

Important: The FTC -- Action after Second Notification (C70) system control value must be set to CANCEL to use the Work with Backorders Pending Cancellation menu option. If this system control value is not set to CANCEL, the system ignores the setting of the FTC--Second Notice Output value.

Backorder Cancellation Pending file: When the system creates a record in the Backorder Cancellation Pending file for a second backorder notice, it flags the record with a type of B. This flag distinguishes backordered records in the file from orders flagged for cancellation due to credit card decline; these orders are flagged with a type of C.

Work with Backorders Pending Cancellation: You can use this menu option to review or work with backordered items that are currently flagged for cancellation. Options include:

• generating notices (if this system control value is set to FILE only)

• accepting the delay for an order or group of orders

• printing a report of items pending cancellation

• canceling backordered items

Credit card cancellations: An order may be eligible for cancellation due to both a backordered item and a credit card decline. In this situation, the credit card cancellation takes precedence; the order will not be visible through the Work with Backorders Pending Cancellation menu option.

For more information: See Purchase Order Layering and Backorder Notifications and Working with Backorders Pending Cancellation (WBPC).

Number of Days to Add for Accepted Delays (E69)

Purpose: Use this screen to indicate the number of days to extend the next backorder date for an accepted delay.

MSR0054 CHANGE Change System Control Value 7/29/97 14:53:31 Description . : # of Days to Add for Accepted Delays Number . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the number of days to add to the backorder date when you accept a delay through the Work with Backorders Pending Cancellation menu option.

When you accept a delay for a backordered item, the system:

• deletes the backorder record from the Backorder Cancellation Pending file (BOCANP)

• deletes the cancellation date from the order detail line

• writes an order transaction history message indicating that the customer has accepted the delay for the item

• adds the amount of days specified in this system control value to the next backorder date.

The order line is then eligible for reservation and fulfillment when you receive a purchase order containing the item; however, the order line is eligible for pending backorder cancellation again if you are not able to fulfill the order by that date.

You can use the Work with Backorders Pending Cancellation menu option to accept the delay for individual orders or a group of orders. You might accept the delay if the customer has told you the wait is not a problem, or if you expect to receive a purchase order containing the item within enough time so that you can fulfill the backorder(s).

Leave this field blank if you do not use the Work with Backorders Pending Cancellation menu option. If you use this menu option and the system control value is blank, the next backorder date is set to the current date when you accept a delay.

Important: The FTC -- Action after Second Notification (C70) system control value must be set to CANCEL to use the Work with Backorders Pending Cancellation menu option. If this system control value is not set to CANCEL, the system ignores the setting of the value. Additionally, the FTC--Second Notice Output (E68) system control value must be set to FILE or FILE/PRINT to create records in the Backorder Cancellation Pending file.

For more information: See Working with Backorders Pending Cancellation (WBPC).

Use Item Freight Exemption File (E73)

Purpose: Use this screen to define whether the system excludes items defined in the Work with Freight Exempt Items (WFEI) menu option from freight.

MSR0052 CHANGE Change System Control Value 7/07/97 11:36:22 Description . : Use Item Freight Exemption file Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to exclude items from freight. Any item defined as freight exempt through the Working with Freight Exempt Items (WFEI) menu option is not included in the freight calculation. You might use this menu option if you sell items such as gift certificates, memberships or subscriptions for which you would not want to charge the customer for freight.

Eligible freight methods: You can exclude items from freight using the following order level freight methods:

• Dollar chart by offer ($O) freight

• Dollar chart by source ($S) freight

• Pre-Discount $ Chart/Offer (DO) freight

• Pre-Discount $ Chart/Source (DS) freight

• Recipient (R) freight

• Percentage by source (PS) freight

• Percentage by ship via (PV) freight

• By Offer Price (OP) freight

• Freight by order weight (OW) freight

Freight exempt hierarchy: If the item qualifies for freight exemption (see Use Item Freight Exemption File (E73) Selected?, Eligible Freight Method on Order?, and Item on Order Defined in Work with Freight Exempt Items (WFEI)?), the system uses the following hierarchy to determine how the item is exempt from freight.

1.	Offer level: If an offer is defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight only if the specified offer is associated with the source code on the order header. Note: The system does not look at the offer code defined at the order line level to determine if the item is exempt from freight. In addition: • If a SKU is defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight only for those SKUs specified. • If a SKU is not defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight across all SKUs. See Freight Exempt Level: Item or SKU for more information on how to set up freight exempt items at the item or SKU level.
2.	Source code level: If a source code is defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight only if the specified source code is defined on the order header. Note: The system does not look at the source code defined at the order line level to determine if the item is exempt from freight. In addition: • If a SKU is defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight only for those SKUs specified. • If a SKU is not defined for the item on the Work with Freight Exempt Items Screen, the item is exempt from freight across all SKUs. See Freight Exempt Level: Item or SKU for more information on how to set up freight exempt items at the item or SKU level.
3.	SKU level: If an offer or source code is not defined for the item on the Work with Freight Exempt Items Screen, but a SKU is specified, then only those SKUs specified for the item are exempt from freight. See Freight Exempt Level: Item or SKU.
4.	Item level: If an offer, source code, or SKU is not defined for the item on the Work with Freight Exempt Items Screen, then the item is always exempt from freight. If the item is a SKUed item, all of the SKUs for the item are exempt from freight.

Ship via additional charges: Any additional charges associated with a ship via, such as service charges or charges for a federal express service, are still added to an order even when the order contains only freight exempt items.

Extra recipient charges: Extra recipient charges are not added to an order if the recipient has only ordered a freight exempt item.

Handling charges: If the Include Handling in Freight Charge Calculation (D77) system control value is selected and a freight exempt item is defined with a handling charge, the handling charge will not be included in the freight calculation.

Pick slips: There will be no freight charge on a pick slip, even if there are non-freight exempt items on the order, under these conditions:

• the Prorate Freight Charges (D39) system control value is set to N

• the pick slip includes only freight exempt items

• the order uses one of the freight methods listed

Enter N or leave this field blank if you do not want to exclude items defined in the Work with Freight Exempt Items (WFEI) menu option from freight.

For more information: See:

• Working with Freight Exempt Items (WFEI) for an overview and the required setup.

• Working with Weight Tables for Order Weight (WFTB) for more information on required setup for the freight by order weight method.

Soldout Notification Print Program (E75)

Purpose: Use this screen to define the soldout notification print program the system uses to print soldout notification cards.

MSR0053 CHANGE Change System Control Value 5/15/97 9:04:46 Description . : Soldout Notification Print Program System name . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

System name: Enter the program name the system uses to print soldout notification cards. The base program name defined for the soldout notification print program is CSR0475. If you have the Validate Prefix (I27) system control value set to Y, the base soldout notification print program is CSR1370.

Leave this field blank if you do not want the system to print soldout notification cards. Print Soldout Notifications (fast path = MSON) displays an error message if you try to print soldout cards and no program name has been defined:

 

No Soldout print program has been defined in SCV E75.

 

For more information: See Customer Service Chapter 115: Printing Soldout Notifications (MSON).

Gift Certificate Print Program (E76)

Purpose: Use this screen to define the program to print gift certificates.

MSR0053 CHANGE Change System Control Value 6/20/97 11:03:56 Description . : Gift Certificate printing program System name . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name: Enter the program name the system uses to print gift certificates. The base program is CSR0437.

Leave this field blank if you do not want the system to print gift certificates. Process Gift Certificates (fast path = MPGC) and Reprint Gift Certificates (fast path = MRGC) display an error message if you try to print or reprint gift certificates and no program name has been defined:

Gift Certificate print program must be defined in SCV E76.

For more information: See Customer Service Chapter 122: Working with Gift Certificates for more information on printing and reprinting gift certificates.

Unconditional Suppression of Backorder Card (F19)

Purpose: Use this screen to indicate whether items flagged to suppress a backorder notice should ever be included on a backorder notice, even if another item on the order generates the notice.

MSR0052 CHANGE Change System Control Value 3/16/98 13:27:33 Description . : Unconditional suppression of B/O Card. Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . FTC Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to exclude items or SKUs whose Sup B/O card (Suppress backorder card) field is set to Y from ever appearing on the first backorder notice for an order, even if another item on the order triggers the backorder notice.

You might use the Suppress backorder card field to flag an item such as a free gift, a promotional item, or a catalog, which should never generate a backorder card by itself.

Enter N in this field or leave it blank to have these items or SKUs appear on the first backorder card if another item on the order triggers the card.

Example:

An order includes two regular (unsuppressed) items and one item whose Suppress backorder card field is set to Y. One of the regular items is backordered. The suppressed item appears on the first backorder card, which was triggered by the unsuppressed item. Subsequently, the expected ship date for the regular backordered item changes. This change triggers another backorder card for the unsuppressed item; however, the suppressed item does not appear on the card.

If there are no unsuppressed backordered items on an order, the suppressed item will never generate a backorder notice on its own. Also, suppressed items are not eligible to be canceled through Working with Backorders Pending Cancellation (WBPC), and are not on the Order Cancellation List by Item or the Backorder Cancellation Register.

Require Exchange Item at Time of Receipt (F42)

Purpose: Use this screen to define whether you must enter an exchange item at the time of creating a return authorization or not until you process the receipt.

MSR0052 CHANGE Change System Control Value 6/17/98 9:33:57 Description . : Require Exchange Item at Time of Receipt. Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have entry of an exchange item required at the time you process the receipt of a return authorization rather than the time you create the return.

This system control value applies only when you process a return through the Work with Return Authorizations (fast path = WRTA) and Work with Return Authorization Receiving (fast path = WRAR) menu options. It does not apply when you process a return through order maintenance.

Set this field to N or leave it blank to have the exchange item always be required at the time you create a return authorization.

About return authorizations: The Work with Return Authorization menu option allows you to process the creation, receipt, and credit of a return authorization in separate steps, while order maintenance automatically processes the entire return “behind the scenes.”

Standard vs. streamlined process: If you use standard return authorization process, you must explicitly choose to perform each step of the return in the Work with Return Authorizations menu option; but if you use the streamlined process, the return authorization processes automatically as far as your authority extends.

The Use Streamlined Return Authorizations (F44) system control value controls which process you use. The secured features that control your authority to process return authorizations are described in Chapter 29: Setting Up Secured Features.

Enter Exchange Item screen: When you enter an exchange reason code rather than a return reason code for a return authorization, you advance to the Enter Exchange Item screen, where you must identify the exchange item to ship to the customer. (In certain situations, you advance to the Enter Exchange Item pop-up window rather than the full screen; however, each field is the same.) If this system control value is set to Y, you do not advance to this screen automatically until you process the receipt.

If you have create authority only (streamlined process), or if you choose to create the return only but do not receive it (standard process), the Enter Exchange Item screen does not display. The screen will display when an operator with sufficient authority processes/completes the return (streamlined process) or when you choose to receive the return (standard process, or the Work with Return Authorization Receiving menu option).

For more information: See Customer Service Chapter 87: Introducing Return Authorizations.

Use Streamlined Return Authorizations (F44)

Purpose: Use this screen to define whether you use streamlined or standard return authorization processing in the Work with Return Authorizations menu option.

MSR0052 CHANGE Change System Control Value 6/17/98 10:08:26 Description . : Use Streamlined Return Authorizations. Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to use the streamlined return authorization process in the Work with Return Authorizations menu option (fast path = WRTA).

Set this field to N or leave it blank to use the standard process.

Streamlined process: When you select an order for return authorization, you advance to the Work with Returns for Order screen. This screen displays each item on the order that has been shipped and not returned by the customer, and is thus eligible for return. If a return authorization is currently in process for the item, this fact is indicated on the screen.

When you select an item on the order for return, or choose to return the entire order, the return processes automatically as far as your authority extends. The secured features that control your authority to process return authorizations are described in Chapter 29: Setting Up Secured Features.

Standard process: When you select an order for return authorization, you advance to a screen that displays any return authorizations that are currently in progress; you can choose to process or change these returns, or create a new return authorization.

If there are currently no return authorizations in process, you can create one; then you must explicitly choose to receive and/or credit the return in separate steps.

If you attempt to perform any step in the return authorization process for which you do not have the necessary authority, an error message displays.

For more information: See Customer Service Chapter 87: Introducing Return Authorizations.

Postal Code Scan Length (F61)

Purpose: Use this screen to indicate the number of characters in the postal code to consider when scanning for a customer.

MSR0054 CHANGE Change System Control Value 1/24/05 16:35:19 Description . : Postal Code Scan Length Number . . . . 5 Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Number field: Enter the number of positions to use for searching based on postal code (or zip) code. Any additional characters in the postal code beyond this number do not affect the sequence in which matching records are presented.

Example: Most of your customers are in the U.S., so you have this system control value set to 5. Most customers know their five-position postal code (such as 01760), but do not know the full ZIP+4 (such as 01760-1234). When you scan based on postal code, customers with the full ZIP+4 are included in the search results with customers whose postal codes are just five positions; they are not listed after the five-position postal codes.

How does the system use this system control value to control scanning by postal code? Even though the system saves the full ten positions of the customer’s postal code in the related customer file, the system does not actually use this field for searching and scanning. Instead, it uses an additional, hidden Postal code scan field in the related customer file to find customers based on postal code. This hidden field includes the number of positions of the postal code that is indicated by the system control value, with any additional positions saved as blank spaces. For example, if this system control value is set to 5, and the customer’s actual postal code is 01760, this hidden field is set to 01760 with five blank spaces.

If you set this system control value to 10, the system uses the full ten positions of the postal code for scanning. As a result, customers whose postal codes include the full ZIP+4 (such as 01760-1234) are listed after customers who use the five-position postal code (such as 01760) at a scan screen.

How to use postal code scanning based on this system control value: When searching for a customer based on postal code, your entry should not exceed the number of positions indicated in this system control value. For example, if this system control value is set to 5, enter up to five positions of the postal code to search correctly:

• Enter 017 to display postal codes such as 01701, 01702, etc.

• Enter 01760 to display postal codes such as 01760, 01761, etc.

However, at most scan screens, if you enter more than five positions when scanning, your search results begin after your entry. For example, enter 01760-1234 to display postal codes starting at 01761, etc.; 01760 and any variation (01760-1234, 01760-5678, etc.) are not included in the search results. Based on the five positions indicated by this system control value, these postal codes occur after 01760 alphanumerically.

Available for customer or address types: Scanning based on the designated postal code length is available for:

• Customer Sold To

• Customer Ship To

• Customer Bill To

• Order Ship To Address

Scanning based on the designated postal code length is not available for other types of addresses, such as vendor.

Used where? The postal code length scanning applies when you search for a customer in:

• customer maintenance: see Selecting Customers

• order inquiry: see Using the Order Inquiry Scan Screens (OIOM)

• order maintenance: see Selecting an Order for Maintenance

• order entry: see Selecting Customers

• entering catalog requests: see Entering Catalog Requests (WCAT)

• return authorizations: see Selecting Orders for Return (WRTA)

• cash receipts: see Working with Cash Receipts (WCRT)

• Work with A/R Open Items (WARI)

• Using A/R Inquiry (DARI)

• Generic Customer Inquiry (Search) API

Conversion programs: When you change this setting, enter the following at a command line to reset the Postal code scan settings in the Customer Sold To, Customer Ship To, and Customer Bill To to the new length:

SBMJOB CMD(CALL PGM(CVR0348) PARM(' ')) JOB(CVR0347)

Also, enter the following at a command line to convert the scan value in the Order Ship To Address file:

SBMJOB CMD(CALL PGM(MSR1241) PARM(‘ ‘)) JOB(OEOSTAFIX)

Note: These conversion programs are not company-specific; they convert the values in all companies based on the setting of this system control value in each company.

Important: If you set this system control value to zero, the system does not update the Postal code scan field in any of the customer files. As a result, you will not be able to scan on postal code.

Display Customer Action Notes/Messages in RA (F64)

Purpose: Use this screen to define whether the Edit Customer Actions pop-up window and an indicator that there are order messages should display when you select an order in Work with Return Authorizations.

MSR0052 CHANGE Change System Control Value 7/13/98 9:33:25 Description . : Display Customer Action Notes/Messages in RA Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you would like the system to display the Edit Customer Actions pop-up window, and identify whether there are any order messages, when you select an order in the Work with Return Authorizations (fast path = WRTA) menu option.

This system control value works the same way in both standard and streamlined return authorization processing. However, this system control value does not affect the Work with Return Authorization Receiving (fast path = WRAR) or Work with Return Authorization Credits (fast path = WRAC) menu options.

Edit Customer Actions pop-up window: This window displays when you select an order for return authorization processing if there are open any customer action notes for the customer.

Edit Customer Actions Customer : 137 MARLOW, DAN W Type options, press Enter. 4=Delete 5=Display 7=Work in Process 8=Resolve 23=Detail notes Opt Action Description Rn User S Resolved LOST PACKAGE IS BEING TRACKED P LWARREN W D CUSTOMER RECEIVED DAMAGED PACKAGE D LWARREN R 4/15/99 D GIFT WRAP NEXT ORDER FREE OF CHARGE D NSULLIVAN O D LATE DELIVERY L KLETENDRE O LATE DELIVERY L LWARREN W ENTER = twice to update F3=Exit F12=Cancel

If there are order messages: The text SEE MSGS appears in the upper right corner of the screen if there are any order messages for the order you selected. This text appears on the:

• Work with Returns for Order screen (streamlined process)

• Work with Return Authorization Detail or Work with Return Authorizations screen (standard process)

To review order messages:

• Streamlined process: press F7 to advance to order inquiry and press F23 to display the messages.

• Standard process: advance to order inquiry, select the order at a scan screen, and press F23 to display the messages.

CSR0875 DISPLAY Work with Returns for Order 6/11/98 8:44:56 see msgs Customer # : 317 COMMERCIALWARE ATTN: MUNDI, GLORIA Qty Qty Qty RA Opt Ln# Item/Description CLR SIZE WDTH Shipped Rtn'd Crdtd Pend Type options, press Enter. 5=Display 8=Create/process return 9=Complete/process return(s) 24=Order line history 1 BE12345 2 0 0 DACHSHUND BEAN BAG DOLL 3 TO12345 2 0 0 DELUXE CLASSIC TOASTER 4 BL12345 SMLL 2 0 0 GOURMET BLENDER PORTABLE ONE-PINT BLENDER 5 VA12345 2 0 0 POWER-VAC F6=Create misship F7=Order Inquiry F8=Create/Return all F9=Accept F11=Reject F16=Additional charges

Set this system control value to N if you do not want the pop-up window and message indicator to appear in Work with Return Authorizations.

For more information:

• working with return authorizations: Customer Service Chapter 87: Introducing Return Authorizations

• working with customer action notes: Customer Service Chapter 144: Displaying More Options

• reviewing order messages: Customer Service Chapter 58: Reviewing Order Level Properties

Track Customer History at Entity Level (F89)

Purpose: Use this screen to define whether to break out customer history based on the entity associated with each order.

MSR0052 CHANGE Change System Control Value 2/11/99 14:16:49 Description . : Track Customer History at Entity Level Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . CST Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the system track customer history at the entity level. You might want to track history at the entity level if you offer more than one catalog with distinct identities, yet you want to share the same customer list and inventory for each.

Entity relationship: The system identifies the entity for each order based on the division defined for the source code on the order header. Each division points to an entity. Similarly, the system identifies the entity for a catalog request based on the source code defined for the catalog request.

Customer-level vs. entity-level: The system tracks information at both the customer level and the entity level if this system control value is set to Y.

Entity-related files: The system uses these entity-related files to track customer order history if this system control value is set to Y:

• Customer Sold To Entity

• Customer Ship To Entity

• Customer Sold To Item Class Entity

If this system control value is set to N or blank, the system uses these files only:

• Customer Sold To Order History

• Customer Ship To Order History

• Customer Sold To Item Class History

Screen Differences Related to Entity

Setting this system control value to Y produces these screen differences:

Customer/entity mail flags: When you prompt (F4) on the Mail flag, the system displays this window listing each entity in your company:

Customer/Entity Mail flags Entity Mail(Y/N) 1 ROBOTS ALIVE N 2 A DOG'S LIFE 3 SPECIAL KIDS F3=Exit F12=Cancel

Use this window to set the Mail flag independently for each entity. The Mail flag indicates whether the customer should receive any mailings from your company.

Default setting: If you do not manually set the Mail flag for an entity, the setting from the Default Mail Name (D10) system control value defaults when you first enter an order for the customer within an entity. However, the setting at the customer level defaults if you create the customer entity record by entering a catalog request for an entity.

Customer level: The system also stores the Mail flag setting at the customer level. The Mail flag field that appears on these screens is the customer-level setting:

• the first Create/Change/Display Customer screen in Work with Customers (fast path =WCST)

• the Change Customer Sold to Name and Address screen in order entry, available by entering 2 next to a customer at a customer scan screen

• the order header and order header/detail screens in order entry

• the Work with Expanded Address screen in order entry, available by pressing F18 at the order header screen

• the Create Catalog Request screen in Work with Catalog Requests (fast path = WCAT)

 

Note: Changing the Mail flag at any of these screens updates the customer-level setting only; to update any of the entity-level settings, you must prompt (F4) to display the Customer/Entity Mail Flags pop-up window.

Current mail type: When you prompt (F4) on the Current mail type field, the system displays this pop-up window:

Customer/Entity Mail Types Entity Current Original Entered Mail Type Mail Type Date 1 ROBOTS ALIVE R B 2/10/99 2 A DOG'S LIFE B B 2/12/99 F3=Exit F12=Cancel

You can use this pop-up window to review the mail type information for each entity in which there has been activity for the customer, or to change the current mail type.

The system sets the mail type for each entity as:

• B (buyer): the customer places an order

• S (suspect): the customer places an order that is rejected

• R (recipient): the customer is a recipient of an order

• C (catalog): the customer places a catalog request; or you create the customer through Work with Customers; or you set the mail flag for an entity but there has been no previous activity for that entity

• L (list rental): you received the customer's name from another company

The Original mail type field is set when you create the customer entity record and never changes. The Current mail type updates only to a B if the customer places and accepts an order for the entity.

Customer level: The system sets the customer-level mail types when you first create the customer, using the same logic to determine the customer-level settings as it used for the entity-level settings.

The Current mail type is available at the second Create/Change/Display Customer screen in Work with Customers (fast path = WCST).

Entity-related customer history: These additional screens are available in Work with Customers (fast path =WCST) to review customer history at the entity level:

• Display Customer Order/Entity History

• Display Customer Entity History

• Display Customer Item Class Entity

• Display Customer Item Class Entity Details

• Display Ship To Order/Entity History

• Display Ship To Entity History

Email opt-in/opt-out setting: The opt-in/opt-out flag indicates the preferred method of correspondence. If this system control value is set to Y, you set the opt-in/opt-out flag separately for each entity. In certain situations the entity-level setting, rather than the sold-to customer’s primary email address setting, controls how you correspond with the customer on order-related issues; see Determining the Opt-in/out Setting for more information. The system checks the entity associated with the source code on the order header to determine the customer’s preferred method for the entity.

If this system control value is set to N or blank, the system never checks the opt-in/opt-out setting by entity.

For more information:

• working with customers and reviewing customer order history: Customer Service Chapter 34: Reviewing Customer History

• working with catalog requests: Customer Service Chapter 109: Entering Catalog Requests (WCAT)

• entering orders: Order Entry Chapter 1: Introducing Order Entry

• working with entities: Accounts Payable Chapter 1: Working with Entities (WENT)

• generating emails to customers: When Does the System Generate an Email Notification?

Individual Position for Consumer Customers (G02)

Purpose: Use this screen to define the individual position for the system to use when determining whether to automatically create and/or assign an individual in order entry.

MSR0051 CHANGE Change System Control Value 9/21/99 11:37:02 Description . : Individual position for consumer customers Code . . . . . 123 BUY CAN INV MAN PRR RCP SEC 123 Narrative . . . Application . : O/E Applic group . CST Sequence# . . . 15 F3=Exit F12=Cancel

Code field: Enter an individual position code if you want the system to automatically create and/or assign an individual to the customer and/or the order in certain situations.

Individual position codes are defined in and validated against the Individual Position file.

For more information:

• how this system control value works together with the Individuals Required in Order Entry (E01) system control value to control individual creation and assignment in order entry

• Customer Service Chapter 40: Working with Individual Positions (WPOS)

• individuals: Customer Service Chapter 38: Creating and Updating Individuals

Create Bank Interface Record (G12)

Purpose: Use this screen to define whether the system creates a bank reconciliation transaction when you generate refund checks in Process Refunds.

MSR0052 CHANGE Change System Control Value 7/08/99 8:05:23 Description . : Create Bank Interface Record Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to create a bank reconciliation transaction when you generate refund checks in Processing Refunds (MREF).

A bank reconciliation transaction is a transaction that you can send to a bank that contains refund check information for automated reconciliation.

Once the bank processes the refund checks, the bank sends bank reconciliation transactions back to CWDirect.

You can review and work with the bank reconciliation transactions that the system creates when you generate refund checks and that the bank has sent back to CWDirect in Work with Bank Reconciliation Transactions.

Enter N or leave this field blank if you do not want the system to create a bank reconciliation transaction when you generate checks in Process Refunds.

For more information: See Customer Service Chapter 107: Working with Bank Reconciliation Transactions (WBRC) for more information on how to generate an outbound file to send transactions to the bank, and processing the inbound file from the bank.

Display First Membership Order Total (G14)

Purpose: Use this screen to define whether to display the estimated dollar total for the first membership order scheduled for generation when you create a membership for a customer in order entry.

MSR0052 CHANGE Change System Control Value 5/12/99 10:13:57 Description . : Display First Membership Order Total Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 101 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to display the Order Total pop-up window in order entry when you press F9 to accept an order in which you have ordered a membership item, creating a customer membership.

What is a customer membership? You can use a customer membership to generate periodic orders for a customer. Typically, a membership program generates orders containing the same item(s) monthly, but you can set up memberships to generate orders at different intervals, to include a rotating selection of items, and/or to include a discount that applies to each order the customer places.

How do you create a customer membership in order entry? When you enter an item flagged as a Membership, the system displays a pop-up window in which you can select the type of membership the customer wants to purchase. Depending on the type of membership program, you may be able to override the default settings (which include items, shipment intervals, and discount percentage), or you can accept all defaults for the program. Payment information can default to the membership from the order, or you can enter a separate payment method.

Note: You can also create and work with customer memberships through the Work with Customer Memberships menu option.

How do you generate membership orders? The Generate Customer Membership Orders function reviews all active customer memberships, and creates a new order for each customer membership whose release date is on or before the current date. Once you generate a membership order, you can process and fulfill it like any other order.

What does the first order total include? The order total that appears in the Order Total window includes merchandise, tax, and freight. This order total is an estimate only. The actual total when you generate the first order may vary, depending on changes to pricing, using various freight methods, including special charges, item availability, and so on.

Order Total For rotation: 1 27.94 Press Enter

Set this system control value to N or leave it blank if you do not want to display the Order Total pop-up window in order entry.

For more information:

• setting up and working with memberships: Customer Service Chapter 129: Working with Membership Programs (WWMP)

• creating memberships by selling membership items in order entry: Order Entry Chapter 22: Entering Customer Memberships

Populate Marketing/PO Interface Trigger File (G33)

Purpose: Use this screen to define what types of activity in the system should cause the system to populate the Marketing/PO Interface Trigger file.

MSR0051 CHANGE Change System Control Value 10/15/99 15:01:31 Description . : Populate Marketing/PO Interface Trigger File Code . . . . . ALL ORDER CUSTOMER ORD/CUST PO ALL Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code that indicates the types of activity that should cause the system to write a record to the Marketing Download Trigger file (IXMKDT). Valid values are:

• ORDER: Order entry or maintenance

• CUSTOMER: Customer maintenance or catalog requests

• ORD/CUST: Order entry or maintenance, customer requests, or catalog requests

• PO: Purchase order receipts, entry or maintenance

• ALL: Any of the activity listed

In addition, if the Include All Customer Merge/Purge Triggers in DMT (L17) system control value is set to Y and the Populate Marketing/PO Interface Trigger File (G33) system control value is set to CUSTOMER, ORD/CUST, or ALL, the sold to customer merge/purge process creates triggers in the Marketing Download Trigger file.

Why write trigger records? You can use the records in the Marketing Download Trigger file to drive a download process for an interface related to order, customer, or purchase order activity. The presence of the trigger record indicates that there is updated information to be collected in CWDirect. Using the trigger file allows you to schedule the update and download process at a time when there is less interactive activity, making your system usage more efficient.

Example: You would like to download current information in your house list to an external service. You could set this system control value to CUSTOMER so that each time you update a customer record in CWDirect, the system writes a trigger record. You could then run a job on a weekly basis, preferably at a time when system resources are more available, to retrieve each customer record that has an associated trigger record, and download the new customer information from CWDirect to your external service.

DMT interface: You can run the DMT marketing download trigger command to extract the records in the Marketing Download Trigger file and create corresponding records in the DMT files, which the DMT system can then retrieve.

When the system creates a marketing download trigger record, the record is assigned a trigger type, based on the type of activity that was performed. The trigger type determines what fields are populated in the Marketing Download Trigger file and what DMT file is populated when you run the marketing download trigger program.

See Working with the DMT Interface for an overview of the DMT interface.

This table displays the trigger type created based on the setting of the Populate Marketing/PO Interface Trigger File (G33) system control value and the action you performed. The trigger type determines what fields in the Marketing Download Trigger file are populated and what DMT file is populated when you run the marketing download trigger program.

SCV value:	creates trigger type:	when you:	trigger includes:	DMT file populated:
ORDER, ORD/CUST, or ALL	OH (order header)	• create a new order in order entry or accept an order in batch order entry. A separate record is created for each order ship to. • add a new ship to address (using F19) in order maintenance.	Customer sold to # Customer ship to # (if a permanent ship to address is used) Entity Order # Order ship-to #	DMT Order Header File, DMT Order Detail File DMT Customer Inquiry File (only for a recipient customer)
ORDER, ORD/CUST, or ALL	LH (order line history)	create order line history (for example, adding, cancelling, changing, exchanging, returning, shipping, or selling out an item on an order; or billing an order). Note: The system does not create an LH record if the original OH record for the order exists in the Marketing Download Trigger file.	Order # Order ship-to # Order detail sequence # Order line history sequence #	DMT Order Detail File
CUSTOMER, ORD/CUST, or ALL	CI (customer inquiry)	• create a catalog request. • create a new customer in order entry, even if you don't accept the order. • create a new customer entity record, if the Track Customer History at Entity Level (F89) system control value is set to Y.	Customer sold to # Entity #, if the activity was associated with a specific entity (for example, entry of a catalog request)	DMT Customer Inquiry File
CUSTOMER, ORD/CUST, or ALL	CS (customer status change)	change one or more of these fields for a customer sold to: • Mail name • Customer sold to entity mail name • Rent name • Deliverable code (not delivery code) • Hold/bypass/fraud • Customer class • Mail code • Call code • Email opt in/opt out Note: The system may change one of the above fields when you create a catalog request for an existing customer.	Customer sold to # Entity #, if the activity was related to a specific entity (for example, setting the mail name at the entity level)	DMT Customer Status Change File
CUSTOMER, ORD/CUST, or ALL	CA (customer address change)	change a customer sold to or change or create a permanent customer ship to address, including phone numbers and email address.	Customer sold to # Customer ship to, if the activity was related to a ship-to address	DMT Customer Address Change File
CUSTOMER, ORD/CUST, or ALL	CN (customer action note)	create, work with, or resolve a customer action note. Note: The system populates the DMT Customer Inquiry file only if a reason has been defined for the customer action note.	Customer sold to # Customer action sequence #	DMT Customer Inquiry File
CUSTOMER, ORD/CUST, or ALL	CM (customer merge)	process a sold to customer merge/purge if the Include All Customer Merge/Purge Triggers in DMT (L17) system control value is set to Y and you retain the source customer as a ghost customer.	Source customer sold-to # Target customer sold-to #	DMT Customer Merge/Purge File
	CP (customer purge)	process a sold to customer merge/purge if the Include All Customer Merge/Purge Triggers in DMT (L17) system control value is set to Y and you do NOT retain the source customer as a ghost customer.
PO or ALL	PR (PO receipt)	receive a purchase order.	PO #	not populated
PO or ALL	PA (PO entry)	create a purchase order.	PO # Warehouse # (where the PO is to be received)	not populated
PO or ALL	PM (PO maintenance)	maintain a purchase order.	PO #	not populated
In addition to the fields listed above, each marketing download trigger record also includes company number, trigger type, trigger sequence number, status, date created, and time created.

When is the trigger record created? Each of the trigger record types indicated are created when the update in CWDirect is complete. For an interactive process, such as creating or updating a customer in order entry, the trigger record is created immediately. For an update that is handled by an asynchronous job, such as purchase order receipt, the trigger record is not created until the job processing is complete.

Leave this field blank if you do not want to populate the Marketing Download Trigger file.

Require Return Reason Code for all Call Tags (G67)

Purpose: Use this screen to define whether the system requires you to enter a return reason code when you create a call tag.

MSR0052 CHANGE Change System Control Value 10/18/99 7:31:11 Description . : Require Return Reason Code for all Call Tags Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 35 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to require you to enter a return reason code when you create a call tag.

An error message displays if you create a call tag and do not define a return reason code:

 

Return Reason required for Call Tag.

 

Enter N or leave this field blank if you do not want the system to require you to enter a return reason code when you create a call tag.

For more information: See Customer Service Chapter 59: Creating Call Tags Through Order Inquiry.

Display Action Notes in Order Inquiry (G74)

Purpose: Use this screen to indicate whether the Edit Customer Actions pop-up window displays in order inquiry if there are unresolved customer action notes.

MSR0052 CHANGE Change System Control Value 3/27/00 14:48:40 Description . : Display Unresolved Action Notes in Order Inquiry. Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 6 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the Edit Customer Actions Window will display when you advance to the Order Inquiry Header Screen in order inquiry if there are unresolved customer action issues for the customer. The window will appear only once while you are working with an order in order inquiry.

Set this field to N or leave it blank if you do not want the Edit Customer Actions window to display in order inquiry.

Note: This system control value will not affect the display of the Edit Customer Actions window in order entry; this window displays in order entry when you press Enter to accept the order header information if there are unresolved customer action issues for the customer, regardless of the setting of this system control value.

Backorder Notification E-Mail Program (G95)

Purpose: Use this screen to specify the program to generate backorder notices to send to customers via email.

MSR0053 CHANGE Change System Control Value 4/24/00 17:08:18 Description . : B/O Notification E-Mail Program System name . . BOR0035 Narrative . . . . Application . : C/S Applic group . FTC Sequence# . . . 100 F3=Exit F12=Cancel

Program field: Enter the name of the program you want the system to use to create backorder notices to send to customers via email. See When Does the System Generate an Email Notification? for an overview of when the system sends an email notice, generates a spool file for printing, or generates the Outbound Email XML Message (CWEmailOut), and for information on entering the text to appear in the email. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

The base program is BOR0035.

Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for backorder notifications if the Use email API flag for the backorder notification template is set to Y. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. See Outbound Email API for an overview.

Backorder Notification Email

Sample backorder email notification:

Address information:	From: GardenPets.com
	To: bmiranda@example.com
	Backorder - Order #9594
Text from Backorder email template:	We are sorry to inform you that one or more of the items that you have ordered is on backorder. Please call GardenPets at 800 505 9587 if you would like to cancel the item or exchange the item for another one that is not on backorder. Otherwise, you can expect to receive the backordered item on the date listed below.
System generated backorder information:	Order #: 9594 - 1 Sold To: MIRANDA, BERNADETTE T Ship To: NONNIE, NONA Item: BA9678 Qty: 2 Exp Ship: 5/09/07 GARDENPET LOGO COTTON TEE
Text from Backorder email template:	Regards, Your friends at GardenPets. Visit us at gardenpets.com!

Leave this field blank if you do not need to send backorder notices by email or through the Outbound Email API.

For more information: See Purchase Order Layering and Backorder Notifications for information on generating backorder notices.

Soldout Notification E-Mail Program (G96)

Purpose: Use this screen to specify the program to create soldout notifications to send to customers via email.

MSR0053 CHANGE Change System Control Value 4/24/00 17:08:18 Description . : Soldout Notification E-Mail Program System name . . ECR0226 Narrative . . . . Application . : C/S Applic group . All Sequence# . . . 100 F3=Exit F12=Cancel

Program field: Enter the name of the program you want the system to use to create soldout notifications to send to customers via email. See When Does the System Generate an Email Notification? for an overview of when the system sends an email notice, generates a spool file for printing, or generates the Outbound Email XML Message (CWEmailOut), and for information on entering the text to appear in the email. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

The base program is ECR0226.

Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for soldout notifications if the Use email API flag for the soldout notification template is set to Y. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. See Outbound Email API for an overview.

Leave this field blank if you do not need to send soldout notifications by email or through the Outbound Email API.

For more information: See Customer Service Chapter 115: Printing Soldout Notifications (MSON) for information on generating soldout notifications.

Default Opt In/Opt Out Flag (G97)

Purpose: Use this screen to define the value that defaults in the Opt In/Opt Out field when you create a new customer or email address.

MSR0051 CHANGE Change System Control Value 4/27/00 11:57:27 Description . : Default Opt-In/Opt-Out Flag for Customer Code . . . . . O2 O1 O2 O3 Narrative . . . Application . : C/S Applic group . CST Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code which defines the default value of the Opt In/Opt Out field when you create a new customer or email address for the:

• sold-to customer

• sold to email

• sold to entity

• bill-to customer

The opt in/opt out value for a sold-to customer defaults when you create an associated individual.

Valid values are:

• O1 (All emails): Email is the preferred method of correspondence

• O2 (Order emails) or blank: Send only order-related email correspondence

• O3 (No emails): Email is not an acceptable method of correspondence

• O4 (Do not ask): Do not ask the customer for his/her email address; the customer has already been asked and has declined to provide it. The system does not generate any email correspondence to the customer, even if an email address is specified.

Note:

• The valid settings for this field each start with the letter O rather than the number 0 (zero).

E-commerce catalog requests: If the E-Commerce Catalog Request Message (CWCatRequest) received from the web storefront does not contain a value in the bill_to_opt_in flag, the system defaults the setting of this system control value. See E-Commerce Catalog Requests for additional processing information.

Outbound email API: The opt in/opt out settings controls the generation of the Outbound Email XML Message (CWEmailOut) using the same logic as the generation of outbound emails. See Outbound Email API for an overview.

You can work with this field in customer maintenance, order entry, and when entering catalog requests.

Note: If the Track Customer History at Entity Level (F89) value is selected, the system also tracks this setting at the entity level in addition to the settings for each of the customer’s email addresses.

See When Does the System Generate an Email Notification? for an overview of the part this flag plays in determining whether to send certain email notifications to customers.

Require Reason in CTI (G98)

Purpose: Use this screen to define whether the Order Inquiry Reason Codes Window displays requiring an order inquiry reason code when you return to the Customer Selection Screen after using order inquiry or order maintenance.

MSR0052 CHANGE Change System Control Value 4/24/00 17:24:51 Description . : Require Reason in CTI - Y/N Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 15 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to display the Order Inquiry Reason Codes Window requiring an order inquiry reason code when you return to the Customer Selection Screen after using order inquiry or order maintenance and you do not have authority to the Bypass CTI Reason Code Entry (B23) secured feature.

You can use order inquiry reason codes to determine why customers are inquiring about their orders or requesting maintenance on their orders. For example, if customers are inquiring about when they can expect to receive the merchandise on their orders, you can train your order entry operators to inform the customers of the expected delivery date.

Note: You can only enter an order inquiry reason code if you advance to order inquiry or order maintenance from the Customer Selection Screen. If you advance to order inquiry from the Order Inquiry Scan Screen or you advance to order maintenance from the Select Customer Sold To For Order Screen, the system does not require an order inquiry reason code regardless of the setting of the Require Reason in CTI (G98) system control value and Bypass CTI Reason Code Entry (B23) secured feature.

How do order inquiry reasons relate to the order? When you define an order inquiry reason code after maintaining or reviewing an order, the system does not assign the order inquiry reason code to the order. Instead, the system tracks the number of times a specific user maintained or reviewed an order or orders associated with a specific line of business for a specific date and a specific order inquiry reason. You can review order inquiry reason history at the Order Inquiry Reason History Screen.

For more information: See:

• Working with Order Inquiry Reason Codes (WORC) for information on creating and maintaining order inquiry reason codes.

• Computer Telephony Integration Overview for an overview on CTI.

• Bypass CTI Reason Code Entry (B23) for more information on this secured feature.

Enter N if you do not want the system to require an order inquiry reason code when you return to the Customer Selection screen after using order inquiry or order maintenance.

Gift Certificate E-Mail Program (H07)

Purpose: Use this screen to specify the program to generate email, rather than printed, gift certificates.

MSR0053 CHANGE Change System Control Value 7/12/00 12:29:53 Description . : Gift Certificate E-mail Program System name . . ECR0250 Narrative . . . Application . : C/S Applic group . FRM Sequence# . . . 15 F3=Exit F12=Cancel

System name field: Enter the name of the program to generate email gift certificates. The system generates an email gift certificate, rather than a spool file for printing, only when:

• this system control value contains a valid program name; the base program is ECR0250.

• the E-mail gift certificate field on the Work with Order Ship to Properties Screen is selected.

• there is an email address specified for the gift certificate recipient. Depending on the type of recipient for the gift certificate, you can specify the email address on a screen where you:

• work with information on a permanent shipping address for the sold-to customer, such as the Change Customer Ship To Screen (Using, Changing, or Excluding a Shipping Address) or the Create Customer Ship To Screen.

• specify a temporary shipping address for the current order only, such as the Create Order Ship to Address Screen.

• work with the sold-to customer’s address, such as the First Create Sold To Customer Screen.

If any of the above conditions are not met, the system includes the gift certificate in a spool file for printing.

Generating the emails: The emails are generated when you complete the Process Gift Certificates Screen (MPGC). By completing this screen, you also print any gift certificates that do not generate email notices as described above.

Order history message: When you generate an email gift certificate, the system writes two order history messages such as the following:

7/12/00 G Gift Certificate (111871) printed. 50.00 EKAPLAN

7/12/00 L Gift Cert to ekaplan@example.com. EKAPLAN

 

Note: The system writes a message such as the first line when you generate either a printed or an email gift certificate.

You can review order history messages at the Display Order History Screen in order inquiry or order maintenance.

Sample gift certificate email: Base gift certificate program ECR0250 uses Working with E-Mail Notification Templates (WEMT) to specify the wording of the gift certificate email notice. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

From:	GardenPets.com
To:	sbottger@example.net
Sent:	Thu 8/08/02 8:58 AM
Subject:	A Gift Certificate For You
Text you can define to print above the gift certificate information:	You have received a gift certificate from GardenPets. You can use this gift certificate to purchase items for your home and garden on our website: gardenpets.com. The purchaser of this gift certificate is displayed below. When purchasing items, enter the gift certificate number on the payment screen; you can purchase items up to the amount displayed below. We gladly accept credit cards for any additional amount.
Standard gift certificate information:	To: From: Gift Certificate Number: Gift Certificate Amount: Gift Certificate Date:	Saundra Bottger Troy Bottger 54 25.00 8/08/02
First 4 order messages whose Print flag is G (gift message)	Happy Birthday Mom! We hope you enjoy the gift card. With love, Troy and Ginger
Text you can define to print below the gift certificate information:	Regards, Your friends at GardenPets. Visit us at gardenpets.com!

Credit Card Credit Acknowledgement E-Mail Program (H08)

Purpose: Use this screen to specify the program to generate email, rather than printed, credit card credit acknowledgements.

MSR0053 CHANGE Change System Control Value 7/12/00 12:29:53 Description . : CC Credit Acknowledgement E-Mail Program System name . . ECR0258 Narrative . . . Application . : C/S Applic group . FRM Sequence# . . . 20 F3=Exit F12=Cancel

System name field: Enter the name of the program to generate email credit card credit acknowledgements. See When Does the System Generate an Email Notification? for an overview of when the system sends an email notice rather than generating a spool file for printing, and for information on entering the text to appear in the email. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

The base program is ECR0258.

Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for credit card credit notifications if the Use email API flag for the credit card credit notification template is set to Y. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. See Outbound Email API for an overview.

Note: As long as you define a valid program in this field, the system still generates credit card credit email notifications regardless of how the Print Credit Card Credit Acknowledgments (C35) system control value is set.

Leave this field blank if you do not need to send credit card acknowledgements by email or through the Outbound Email API.

For more information: See Customer Service Chapter 102: Processing Refunds (MREF) for information on how to generate credit card credit acknowledgements.

Create Random Gift Certificate/Coupon Numbers (H09)

Purpose: Use this screen to define whether to assign gift certificate and coupon numbers in sequential order, or to assign numbers non-sequentially.

MSR0052 CHANGE Change System Control Value 7/12/00 16:04:30 Description . : Create random Gift Certificate/Coupon Numbers. Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to assign “random,” or non-sequential, numbers to gift certificates and coupons. Assigning numbers non-sequentially may help you prevent fraud on a web storefront. For example, if a customer redeems gift certificate number 882, it does not mean that 883 or 884 will also be valid gift certificate numbers.

Leave this field blank or enter N if you want the system to assign gift certificate numbers sequentially.

For more information:

• Generating and Deleting Coupons (MCPN)

• Working with Gift Certificates

E-Mail Order Confirmations for All Orders (H51)

Purpose: Use this screen to define whether the system sends an email confirmation when any order is accepted, or only when a customer on the web storefront accepts or maintains an order.

MSR0052 CHANGE Change System Control Value 1/16/02 11:31:36 Description . : E-mail Order Confirmations for ALL Orders Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to send an email confirmation when any order, regardless of whether it originated at the web storefront, is accepted.

Generating confirmations: The e-commerce order process in Working with E-Commerce Job Control (EJCT) always generates an email acknowledgement or an Outbound Email XML Message (CWEmailOut) after a customer places an order at the web storefront, provided that the customer has an email address specified and the opt-in/out setting selected is 01 or 02 (see Determining the Opt-). However, the system also generates an email acknowledgement for orders that did not originate on the web storefront if:

• this system control value is set to Y, and

• the E-mail notification field for the order type is set to Y, and

• the customer’s Opt in/Opt out field is set to O1 or O2 (see Determining the Opt-in/out Setting), and

• the customer has an Email address

Order confirmation email program name: The system uses the program name defined in the Order Acknowledgement Program (G50) system control value for generating acknowledgment emails for orders.

Standard email or customized email? You can use the Working with E-Mail Notification Templates (WEMT) menu option to create an order confirmation email template. If you do not define a template, the system generates the standard order confirmation email. See below for examples.

Outbound email API: You can specify to generate a generic outbound XML message, rather than an actual email, for order notifications. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email for marketing purposes. See Outbound Email API for an overview.

Email setup: See When Does the System Generate an Email Notification? for more information on the criteria required to generate an email.

Leave this field blank or enter N if you want the system to send an email confirmation or Outbound Email XML Message (CWEmailOut) only when a customer on the web storefront accepts an order. Only orders created through the e-commerce order process in Working with E-Commerce Job Control (EJCT) generate confirmations. You can identify an order created this way by the fact that the Internet order flag in the Order Header file is set to I (Note: This field does not display on any screen).

For more information: See When Does the System Generate an Email Notification? for an overview.

E-Mail Shipment Confirmations for All Orders (H52)

Purpose: Use this screen to define whether the system sends an e-mail confirmation when any sale order or return is shipped or only when an e-commerce sale order or return is shipped.

MSR0052 CHANGE Change System Control Value 1/16/02 14:05:20 Description . : E-mail Shipment Confirmations for ALL Orders Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want to send an email confirmation or Outbound Email XML Message (CWEmailOut) when any order or return is shipped, regardless of order type.

Generating confirmations: The system generates a confirmation email or Outbound Email XML Message (CWEmailOut) when you:

• generate e-commerce shipment confirmations and return confirmations using the Send Internet Order Ship Confirmations menu option; see System Operations Chapter 95: Sending Internet Order Ship Confirmation (ESCF)

• execute the ECSHCNF periodic function; see System Operations Chapter 13: Working with Periodic Functions (WPER)

A shipment or return confirmation email is generated only if the customer’s Opt in/Opt out field is set to O1 or O2 (see Determining the Opt-in/out Setting), and the customer has an Email address.

Shipment confirmation email program name: The system uses the program name defined in the Shipment Confirmation Program (G51) system control value for generating acknowledgments for shipment confirmations.

Return confirmation email program name: The system uses the program name defined in the Return Confirmation E-Mail Program (H53) system control value for generating acknowledgments for return confirmations.

Outbound email API: You can specify to generate a generic outbound XML message, rather than an actual email, for shipment notifications. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. See Outbound Email API for an overview.

Standard email or customized email? You can use the Working with E-Mail Notification Templates (WEMT) menu option to create a shipment confirmation email template and a return confirmation email template. If you do not define a template, the system generates the standard confirmation email. See Sample Shipment Confirmation Email and Sample Return Confirmation for examples.

Leave this field blank or enter N if you want to send an email confirmation only when an e-commerce sale order or return is shipped, identified by comparing the order type with the E-Commerce Order Type (G42) system control value. Again, a shipment or return confirmation email is generated only if the customer’s Opt in/Opt out field is set to O1 or O2, and the customer has an Email address.

For more information: See When Does the System Generate an Email Notification? for an overview.

Return Confirmation E-Mail Program (H53)

Purpose: Use this screen to define the program name to generate email, rather than printed, return confirmations.

MSR0053 CHANGE Change System Control Value 1/16/02 14:08:56 Description . : Return Confirmation E-Mail Program System name . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the program name to use for generating return confirmations.

The base program name is ECR0321.

Generating return confirmations: You can generate a return confirmation email or Outbound Email XML Message (CWEmailOut) through:

• Send Internet Order Ship Confirmations menu option; see Fulfillment Chapter 95: Sending Internet Order Ship Confirmation (ESCF)

• ECSHCNF periodic function; see Chapter 13: Working with Periodic Functions (WPER)

Sample return confirmation email: See Sample Return Confirmation for an example of a return confirmation email.

Standard or customized email? The system generates an email using the template defined for the return confirmation (RC) template in the Working with E-Mail Notification Templates (WEMT) menu option. If you have not defined a template, the system emails the standard return confirmation. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

Outbound email API: You can specify to generate a generic outbound XML message, rather than an actual email, for return notifications. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. To generate the Outbound Email XML Message (CWEmailOut) rather than the actual email, set the Use email API flag for the email template; the system generates the outbound message as long as this system control value is not blank. See Outbound Email API for an overview.

Determining when to email a return confirmation: The E-Mail Shipment Confirmations for All Orders (H52) system control value determines whether to generate a return confirmation email or Outbound Email XML Message (CWEmailOut) for all orders or only for e-commerce orders.

The system generates a return confirmation email or Outbound Email XML Message (CWEmailOut) only if the customer’s Opt in/Opt out field is set to O1 or O2, and the customer has an Email address.

Leave this field blank if you do not wish to email a return confirmation or generate a Outbound Email XML Message (CWEmailOut).

For more information: See When Does the System Generate an Email Notification? for an overview.

Enable Catalog Request at Individual Level (H81)

Purpose: Use this screen to indicate whether catalog requests can be entered for specific individuals within an organization.

MSR0052 CHANGE Change System Control Value 1/25/02 10:52:31 Description . : Enable Catalog Request at Customer Individual level Yes/No . . . . Y (Y,N) Narrative . . . Application . : O/E Applic group . CST Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to enable entry of catalog requests at the individual level.

About individuals: You can use the individual customer function to track the individuals within an organization who place or originate orders. See Creating and Updating Individuals for an overview.

Differences in catalog request entry: Enabling catalog request entry for individuals adds the following options to the Create Catalog Request Screen:

• additional fields: when you press F10, the system displays the following additional fields related to the individual:

• name: prefix, first name, middle initial, last name, and suffix

• department

• position

• phone numbers: day, evening, and fax, with extensions

• email address

• mail stop

• searching for an individual: when you press F18, you advance to the Select Customer Individual Screen, where you can select an individual and the related sold-to customer for a catalog request

Information on catalog request labels: If catalog requests for individuals are enabled, the catalog request labels will include the individual’s name and mail stop. However, you must also set the Label 1-Up Printing Program (C83) and/or the Label 4-Up Printing Program (C84) to MSR1286 or MSR1287, respectively, to have the individual information print. See Processing Catalog Requests (PCAT) for samples.

Catalog request interface: You can process catalog requests that include individual information through the catalog request interface; this includes requests that come from your web storefront. See Working with the Catalog Request Interface (WCRU) for an overview.

Individual mail history: When you print a catalog request label for an individual, the system tracks this activity in the individual’s mail history rather than in the customer sold-to’s mail history. You can review catalog mailings to individuals at the Display Individual Mail History Screen rather than the Display Customer Mail History Screen.

Leave this field blank or enter N if you do not want to enter catalog requests for emails. If you try to press F10 or press F18 at the Create Catalog Request Screen, the system displays an error message; also, any catalog requests received through the catalog request interface that specify individual customer information, including requests from your web storefront, will not be processed and will remain in error status.

Require Customer Class in OE, WCAT, and WCST (H85)

Purpose: Use this screen to indicate whether the customer class is required when entering orders or catalog requests or maintaining customer records.

MSR0052 CHANGE Change System Control Value 1/16/02 10:51:29 Description . : Require Customer Class in OE,WCAT, and WCST Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have customer class required at the following screens:

• order entry and order maintenance:

• Change Cust Sold to Name & Address Screen

• Work with Order Screen (header format)

• Work with Order/Detail Screen (header/detail format)

• Expand Name/Address Screen

• Work with Order/Detail Screencatalog requests: Create Catalog Request Screen

• customer maintenance:

• First Create Sold To Customer Screen

• First Change Sold To Customer Screen

At each of these screens, the customer class defaults as follows:

• existing customer: The customer class defaults if it has already been specified.

• new customer: The customer class defaults if the Default Customer Class in Order Entry (D63) system control value specifies a customer class.

If you fail to enter a customer class and there is no default, the system displays the following error message: Customer Class required.

Important: You can use the Maintenance of Customer Class Field (B07) secured feature to control the authority to enter or change the customer class field at all of the above screens. If you set this system control value to Y, a user who does not have authority to the customer class field will not be able to enter or maintain an order or a catalog request, or perform customer maintenance for any customer that does not already have a customer class assigned. See the table below for more information.

Default Customer Class in Order Entry (D63)	Require Customer Class in OE, WCAT, and WCST (H85)	Maintenance of Customer Class Field (B07) secured feature	Result in order entry, catalog requests or customer maintenance
not specified	blank or set to N	*ALLOW	Current setting, if any, defaults; entry is optional
		*EXCLUDE	Current setting, if any, defaults; cannot enter or maintain customer class for new customers or customers without assigned class
specified	blank or set to N	*ALLOW	Current setting, if any, defaults; class defined for system control value defaults for new customers; entry is optional
		*EXCLUDE	Current setting, if any, defaults; class defined for system control value defaults for new customers; cannot enter or maintain customer class
specified	set to Y	*ALLOW	Current setting, if any, defaults; class defined for system control value defaults for new customers; entry is required for existing customers without assigned class
		*EXCLUDE	Current setting, if any, defaults; class defined for system control value defaults for new customers; cannot complete order, catalog request, or customer maintenance if there is no default customer class
not specified	set to Y	*ALLOW	Current setting, if any, defaults; entry is required for existing customers without assigned class and for new customers
		*EXCLUDE	Current setting, if any, defaults; cannot complete order, catalog request, or customer maintenance for new customers, or if there is no default customer class for existing customers

Enter N or leave this field blank if you do not want customer class to be required in order entry, order maintenance, catalog requests or customer maintenance.

For more information: See Setting Up the Customer Class File (WCCL) for a discussion of customer class.

Update Customer Sold to with Bill to Account Number for New E-Commerce Orders (H87)

Purpose: Use this screen to specify whether to assign a bill-to account number to a customer sold-to when an e-commerce order includes that bill-to customer.

MSR0052 CHANGE Change System Control Value 4/19/02 9:44:35 Description . : Upd Cust Sold to with Bill to Acct # for new ecomm orders Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to assign the bill-to customer number used on an e-commerce order to the Bill to field for the sold-to customer. This assignment takes place regardless of whether the new order creates a new bill-to customer or uses an existing bill-to customer.

Enter N or leave this field blank if you do not want the bill-to customer to be assigned to the sold-to customer. The bill-to customer will be associated only with this order.

For more information: See Selecting or Creating Bill-to Customers in E-Commerce Orders for an overview of how the system determines whether to use an existing bill-to customer for an e-commerce order or create a new one, depending on whether the customer is associated with a bill-to customer or is using an A/R payment method.

Note: This value does not control the assignment of bill-to customers through the Generic Order Interface (Order API).

Assign Unreferenced Email (H93)

Purpose: Use this screen to indicate whether the system should search for the customer related to an incoming email based on the email address that originated the email.

MSR0051 CHANGE Change System Control Value 8/16/02 16:54:46 Description . : Assign Unreferenced Email Code . . . . . *NONE *NONE *NODUPE *DUPE Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Code field: Enter the code that indicates whether the system should search for a customer whose email address matches the address on an incoming email.

Why is email address search necessary? If you use the emails repository, your customer service representatives can flag an email with identifiers, such as customer number and order number, when they forward the email to CWDirect. The system automatically assigns an inbound email if it is flagged correctly and consistently. However, these identifiers would not be specified if, for example, you configured your system to forward the emails automatically into CWDirect rather than having them sent first to customer service representatives for review, or if a customer service representative does not include email identifiers when forwarding an email. When an email arrives without email identifiers, the email can be assigned either through the email search or manually, through Working with Email (WEML).

Valid codes are:

• *NODUPE = Search for a matching email address and use the search hierarchy described below.

• *DUPE = Search for a matching email address in the Customer Sold To Email, Customer Ship To, and Customer Individual files, but put the email in error status if there is more than one matching address in all of these files.

• *NONE = Do not search for an email address. Each email received without accurate email identifiers must be assigned through Working with Email (WEML).

Search hierarchy: If this system control value is set to *NODUPE, the system performs a search for a matching customer in by checking email addresses in the following order:

1. Individual customers:

• Searching only active individuals, the system selects the individual whose Email address matches. If there is more than one matching active individual, the system selects the individual that has been created or updated most recently based on the Create date or Last change date (Note: These fields do not display on any screen).

• If more than one matching individual was updated on the same date, the system selects the individual whose sold-to number is lowest (the oldest sold-to customer).

• If there is more than one matching individual that was updated on the same date belonging to the same sold-to customer, the system selects the first individual by individual number.

2. Ship-to customers:

• The system selects the ship-to customer whose Email address matches, and whose sold-to number is lowest (the oldest sold-to customer).

• If there is more than one ship-to customer for the same sold-to customer, the system selects the first ship-to customer by ship-to number.

• Sold-to customers: The system selects the customer whose Email address matches and has been created or updated the most recently, based on the email address’s Change date and Change time, or the Create date and Create time if the email address has never been changed.

• Bill-to customers: The system selects the bill-to customer whose Email address matches. If there is more than one bill-to customer with a matching email address, the system selects the first bill-to customer by number. If there is a single sold-to customer who has been assigned the selected bill-to customer, the system also selects the sold-to customer; otherwise, only the bill-to customer is selected.

The system does not search for a vendor based on email address.

For more information: See:

• Email Repository Overview for an overview

• Working with Email (WEML) for information on working with emails that have not been assigned to a customer

Use Workflow Management (H96)

Purpose: Use this screen to define whether the workflow management module is enabled.

MSR0052 CHANGE Change System Control Value 8/20/02 15:41:41 Description . : Use Workflow Management Yes/No . . . . N (Y,N) Narrative . . . Application . : ALL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish to use workflow management.

Important: Workflow management is licensed separately. To use this feature, you must receive a new security authorization code. If you are interested in purchasing or learning more about this module, please contact your relationship manager.

Workflow management allows you to automate system events, during which tasks (ticklers) are assigned to a user for action, according to a defined set to procedures, until the issues associated with the tasks are resolved.

Enter N in this field or leave this field blank if you do not wish to use workflow management.

For more information: See Workflow Management Overview and Setup for an overview on workflow management and required setup.

Write Outbound Email to Email Repository (H99)

Purpose: Use this screen to indicate whether to keep a record of email notifications you send to customers in the email repository.

MSR0052 CHANGE Change System Control Value 8/16/02 17:18:16 Description . : Write outbound email to email repository. Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to save a copy of each outbound email notification or Outbound Email XML Message (CWEmailOut) to the Correspondence History file. Outbound email notifications include:

• order confirmations

• credit card credit acknowledgements

• soldout notifications

• shipment confirmations

• backorder notices

• gift certificate notices

• return confirmations

• order update confirmations

• stored value card notifications

Reviewing outbound emails: You can review outbound email notices at the:

• Work with Email by Order Number Screen

• Work with Email by Customer Sold To Number Screen

• Work with Email by Customer Ship To Number Screen

• Work with Email by Customer Bill To Number Screen

• Work with Email by Customer Individual Screen

At these screens, an outbound email has a Source of INT (internal) rather than EXT external. The Email category is NTF (notification). The subject line of the email indicates the type of notification that was sent. However, because the text of each type of outbound email does not vary from customer to customer, the system does not save the text in the Correspondence History Detail file; no text is available for review by entering 7 next to an outbound email at any of the screens listed above.

Outbound email API: You can specify to generate a generic outbound XML message, rather than an actual email, for order, return, or shipment notifications. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. If this system control value is set to Y and you generate the Outbound Email XML Message (CWEmailOut), you see the same type of information for these notices at the screens listed above as you would if the system had generated an actual email notification. See Outbound Email API for an overview.

Notification email category: To save outbound emails in correspondence history, you need an email category of NTF (notification). The system automatically creates this category the first time you advance to the Work with Email Category Screen.

For more information: See:

• Email Repository Overview for an overview of inbound emails

• Working with E-Mail Notification Templates (WEMT) for information on when the system generates email notifications

Email Presentation (I01)

Purpose: Use this screen to indicate whether to delete extra lines from emails stored in the emails repository.

MSR0051 CHANGE Change System Control Value 8/16/02 17:19:47 Description . : Email Text Presentation Code . . . . . 1 2 3 Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Code field: Enter the code that indicates whether to delete extra lines from emails that you store in the email repository. Valid codes are:

• 1 or blank = include blank lines; do not delete anything.

• 2 = delete blank lines, but leave paragraph spacing.

• 3 = delete all lines and paragraph spacing so that all text wraps.

You might want to eliminate blank lines (2) or all paragraph spacing (3) to save space; however, leaving some or all of the spacing can improve readability.

Sample results:

1: include blank lines:

Please respond to this customer inquiry. -----Original Message----- From: jdoe@example.com Sent: 08/09/2002 12:35:55 PM To: Elise Kaplan Cc: Subject: Re: Where is my order?   Please confirm the expected shipment date for order # 12345.   Thank you,   Jane Doe

2: delete blank lines but leave paragraph spacing:

Please respond to this customer inquiry. -----Original Message----- From: jdoe@example.com Sent: 08/09/2002 12:35:55 PM To: Elise Kaplan Cc: Subject: Re: Where is my order? Please confirm the expected shipment date for order # 12345. Thank you, Jane Doe

3: wrap all text:

Please respond to this customer inquiry. -----Original Message----- From: jdoe@example.com Sent: 08/09/2002 12:35:55 PM To: Elise Kaplan Cc: Subject: Re: Where is my order? Please confirm the expected shipment date for order # 12345. Thank you, Jane Doe

Note: This setting controls inbound emails only; the system does not retain the text of outbound email notifications. See Write Outbound Email to Email Repository (H99).

Display Alternate Shipping Charges by Via Window in OM (I02)

Purpose: Use this screen to specify whether to display a pop-up window in order maintenance to offer the customer a choice of ship vias.

MSR0052 CHANGE Change System Control Value 7/31/02 8:56:34 Description . : Display Alternate Shipping Charges by Via Window in OM Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to display the Alternate Shipping Charges by Via Window in order maintenance. You can use this window to review additional ship via choices with the customer, and allow the customer to select a different ship via based on total freight charges or delivery date. This window displays automatically in order maintenance if no items on the order are printed or shipped.

Note: The window displays only if you have specified best way shippers for order entry for the ship via on the order. See Working with Best Way Shippers for an overview.

Enter N or leave this field blank if you do not want the window to display in order maintenance.

Include Special Handling in Alternate Shipping Charges by Via (I03)

Purpose: Use this screen to specify whether to include any handling charges in the freight charges displayed in the Alternate Shipping Charges by Via Window.

MSR0052 CHANGE Change System Control Value 7/31/02 8:57:24 Description . : Include Spec Handling in Alternate Shipping Charges by Via Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to include handling charges in the freight charges displayed in the Alternate Shipping Charges by Via Window. You can use this window to review additional ship via choices with the customer, and allow the customer to select a different ship via based on total freight charges or delivery date.

For example, an order includes personalization charges of $5.00. The current ship via on the order has freight charges of $10.00, and there are two alternate ship vias available with charges of $11.00 and $9.00. If the freight charges include special handling, the charges displayed in the window are:

Ship via 1: $15.00

Ship via 2: $16.00

Ship via 3: $14.00

Enter N or leave this field blank if you do not use the Alternate Shipping Charges by Via Window, or if you do not want the handling charges included in the freight charge totals. The charges displayed in the window are:

Ship via 1: $10.00

Ship via 2: $11.00

Ship via 3: $ 9.00

Vendor for E-Mail Gift Certificate (I04)

Purpose: Use this screen to define the vendor number the system uses to process electronic gift certificates.

MSR0054 CHANGE Change System Control Value 8/08/02 13:16:53 Description . : Vendor for E-Mail Gift Certificate Number . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Number field: Enter the vendor number the system uses to process electronic gift certificates. You must enter a valid vendor number in this field.

The system generates an email gift certificate, rather than a spool file for printing, only when:

• the Gift Certificate E-Mail Program (H07) system control value contains a valid program name. The system uses the email address defined for the vendor in this system control value only if the program defined in this system control value is ECR0383.

• the E-mail gift certificate field on the Work with Order Ship to Properties Screen is selected.

• there is an email address specified for the vendor or the recipient on the order. When you process gift certificates, the system retrieves the company number and vendor’s email address from the vendor specified in this system control value. All electronic gift certificates are emailed to this vendor for further formatting and processing before being sent to the final gift recipient.

If a vendor is not defined in this system control value or an email address is not defined for the specified vendor, the system sends gift certificates to the recipient on the order. Depending on the type of recipient for the gift certificate, you can specify the email address on a screen where you:

• work with information on a permanent shipping address for the sold-to customer, such as the Change Customer Ship To Screen (Using, Changing, or Excluding a Shipping Address) or the Create Customer Ship To Screen.

• specify a temporary shipping address for the current order only, such as the Create Order Ship to Address Screen.

• work with the sold-to customer’s address, such as the First Create Sold To Customer Screen.

If any of the above conditions are not met, the system includes the gift certificate in a spool file for printing.

Sample gift certificate email: Gift certificate program ECR0383 does not use the gift certificate email notification template and instead includes the following fields using name/value pairs:

• sold to first name, last name, address, and email address

• ship to first name, last name, address, and email address

• order number

• item and description

• SKU and description

• order messages 1, 2, 3, and 4; the print code must be G (print as gift message)

• gift certificate number

• gift certificate amount

From:	GardenPets.com
To:	mmcstay@example.net
Sent:	Thu 8/08/02 8:58 AM
Subject:	A Gift Certificate For You
Fields using name/value pairs:	sold_to_fname=TROY sold_to_lname=BOTTGER sold_to_street_address=109 SAMPLE LN sold_to_address2=LOT 3 sold_to_address3= sold_to_address4= sold_to_city=TEMPLETON sold_to_state=MA sold_to_zip=01468 sold_to_email=troybottger@example.net ship_to_fname=MATTHEW ship_to_lname=MCSTAY ship_to_street_address=1829 SOUTH ST ship_to_address2=PARKSIDE APARTMENTS ship_to_address3=APT 47 ship_to_address4= ship_to_city=BLAIR ship_to_state=NE ship_to_zip=68008 ship_to_email=mmcstay@example.net order_number=00006190 item=GIFTCERT25 item_description=GIFT CERTIFICATE 25.00 sku= sku_descript= message1=Happy Birthday Matt! message2=Love, Uncle Troy message3= arrival_date=1020808 gift_certificate=0000055 amount=2500

Leave this field blank if you do not want the system to send gift certificate emails to the email address defined for a specified vendor. If you have a program defined in the Gift Certificate E-Mail Program (H07) system control value, the system sends gift certificate emails to the recipient on the order.

For more information: See Gift Certificate E-Mail Program (H07) for more information on generating email, rather than printed, gift certificates.

Include All Customer Inquiry Triggers for DMT (I09)

Purpose: Use this screen to indicate if the system creates a record in the DMT Customer Inquiry file for a CI (customer inquiry) trigger record when a corresponding OH (order header) trigger record exists in the Marketing Download Trigger file.

MSR0052 CHANGE Change System Control Value 1/07/03 15:56:39 Description . : Include all Customer Inquiry Triggers for DMT Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish the system to create a record in the DMT Customer Inquiry file for a CI (customer inquiry) trigger record when a corresponding OH (order header) trigger record exists in the Marketing Download Trigger file.

An OH (order header) trigger record corresponds to a CI (customer inquiry) trigger record if both records are for the same company, sold to customer, and optionally entity number.

Marketing Download Trigger file
Field	OH trigger record	CI trigger record
Company	555	555
Trigger type	OH	CI
Customer sold to	345	345
Entity	222	222

The Populate Marketing/PO Interface Trigger File (G33) system control value determines what type of activity in CWDirect causes the system to populate the Marketing Download Trigger file.

The system creates a CI trigger record in the Marketing Download Trigger file when you:

• create a catalog request.

• create a new customer in order entry, even if you don’t accept the order.

• create a new customer entity record, if the Track Customer History at Entity Level (F89) system control value is set to Y.

The system creates an OH trigger record in the Marketing Download Trigger file when you:

• create a new order in order entry or accept an order in batch order entry. A separate record is created for each order ship to.

• add a new ship to address (using F19) in order maintenance.

When you run the command to extract the records in the Marketing Download Trigger file to the appropriate DMT file, the system:

• creates a record in the DMT Customer Inquiry file for each CI trigger record.

• creates a record in the DMT Order Header file and DMT Order Detail file for each OH trigger record.

Flowchart: This flowchart explains when the system creates a record in the DMT Customer Inquiry file for each CI trigger record in the Marketing Download Trigger file, based on the setting of the Include All Customer Inquiry Triggers for DMT (I09) system control value.

SCV value:	trigger type:	includes:	DMT file populated:
Y	OH	Company: 555 Customer sold to #: 345 Entity: blank	DMT Order Header DMT Order Detail
	CI	Company: 555 Customer sold to #: 345 Entity: blank	DMT Customer Inquiry (even though a corresponding OH trigger record exists)
N or blank	OH	Company: 555 Customer sold to #: 345 Entity: blank	DMT Order Header DMT Order Detail
	CI	Company: 555 Customer sold to #: 345 Entity: blank	none DMT Customer Inquiry file is not populated since a corresponding OH trigger record exists
Y	OH	Company: 555 Customer sold to #: 345 Entity: blank	DMT Order Header DMT Order Detail
	CI	Company: 555 Customer sold to #: 567 Entity: blank	DMT Customer Inquiry (corresponding OH trigger record does not exist)
N or blank	OH	Company: 555 Customer sold to #: 345 Entity: blank	DMT Order Header DMT Order Detail
	CI	Company: 555 Customer sold to #: 567 Entity: blank	DMT Customer Inquiry (corresponding OH trigger record does not exist).

For more information: See Working with the DMT Interface for more information on downloading order, customer, source code, and vendor information from CWDirect to the DMT system.

Enter N in this field or leave this field blank if you wish the system to create a record in the DMT Customer Inquiry file for a CI trigger record only when a corresponding OH trigger record does not exist in the Marketing Download Trigger file for the same company, sold to customer, and optionally entity number.

Confirmation Email Directory Address (I19)

Purpose: Use this screen to specify the directory address that identifies the originating email address to use when generating email notifications.

MSR0053 CHANGE Change System Control Value 3/06/03 16:13:13 Description . : Confirmation E-mail Directory Entry Address System name . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the Address of the “from” email address to use on system-generated email notifications, as described under Configuring the iSeries as a Mail Server. The Address is part of the Directory for the user profile. The user profile does not need to specify an actual user; instead, you can use it solely to represent the return address for system-generated emails. For example, you might set up a user profile so that email notifications for this company have a “from” email address of customerservice@example_company.com. By setting this system control value differently in each company, you are able to generate email notifications with “from” addresses that identify the company.

You can also specify a unique “from” email address for individual email notification types by entity, as described below.

Directory address hierarchy for order-related emails:

1. Entity and notification type: The system uses the email address for the directory address specified through the Work with Entity Email Overrides Screen, if any (see Directory Address (“From” Email Address) Override at Entity Level for a discussion); otherwise,

2. System control value for company: If the directory address at the email notification type/entity level is blank, the system uses the Confirmation Email Directory Address system control value; otherwise,

3. System default: If directory address specified through the system control value is blank, but there is a directory entry with an address of EMAIL, the system uses the email address for this entry. EMAIL is the suggested Directory setting described under Configuring the iSeries as a Mail Server. See that section for more information on setting up the user profile for email notifications.

4. Otherwise, if there is no directory entry with an address of EMAIL, the system does not send an email notification.

Note: If the system finds a directory address that is invalid, rather than blank, at any point while going through this hierarchy, it uses the email address of the user who started the async jobs; however, if the system finds a user profile that is disabled, it advances to the next level in the hierarchy.

Directory address hierarchy for purchase order emails:

1. Purchase order directory entry: The system uses the email address for the directory address specified through the Purchase Order Email Directory Address Entry (J49), if any; otherwise,

2. System default: If directory address specified through the system control value is blank, but there is a directory entry with an address of EMAIL, the system uses the email address for this entry. EMAIL is the suggested Directory setting described under Configuring the iSeries as a Mail Server. See that section for more information on setting up the user profile for email notifications.

3. Otherwise, if there is no directory entry with an address of EMAIL, the system does not send an email notification.

Note: If the system finds a directory address that is invalid, rather than blank, at any point while going through this hierarchy, it uses the email address of the user who started the async jobs; however, if the system finds a user profile that is disabled, it advances to the next level in the hierarchy.

Important: The “from” email address is not included in the Outbound Email XML Message (CWEmailOut). See the discussion of the Outbound Email API for more information.

Validate Prefix (I27)

Purpose: Use this screen to indicate whether to validate a customer’s prefix against the Prefix file.

MSR0052 CHANGE Change System Control Value 6/16/03 11:46:16 Description . : Validate Prefix Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have prefix definitions, set up through Working with Prefix Codes (WPFX), available for selection on screens and to have the system validate your entries in the Prefix field against this file.

Why use the Prefix file? The Prefix file allows you to specify a description of up to 15 characters, rather than just the three positions of the prefix field itself. The prefix is available to print on pick slips, backorder cards, soldout notifications, and accounts receivable statements if your print program supports it. For example, you could set up a prefix code of PRF with a description of PROFESSOR. When you print a pick slip for the customer, the word PROFESSOR prints rather than the prefix code.

Which types of customers use the prefix? When you have the system validate the customer’s prefix, the validation applies to:

• sold-to customers

• ship-to customers

• customer individuals

• bill-to customers

• customer frauds

About prefix validation: When customer’s prefix has not been defined in this file, then the system displays an error message and does not let you complete your entry if you attempt to:

• create or work with a customer

• enter an order, or create one through the inbound order message, e-commerce interface, or phone order load (the error message is Invalid Prefix Code)

• create or work with a catalog request

In most cases, you can correct the prefix at a screen by selecting a code defined in the Prefix file. However, when you select an existing customer when creating a catalog request, you will not be able to complete your entry if the customer’s prefix code is invalid.

Before you set this system control value to Y, you should make sure that you have created an entry, using Working with Prefix Codes (WPFX), for each prefix you will use in your company, including prefixes such as Mr. and Ms. that do not require expansion.

Note: A blank Prefix is not considered invalid; the prefix is not required.

Which screens validate the prefix? Prefix validation takes place at the following screens:

• Order entry/order maintenance:

• Work with Order Screen (header format)

• Work with Order/Detail Screen

• Expand Name/Address Screen

• Create Customer Ship To Screen

• Change Customer Ship To Screen (Using, Changing, or Excluding a Shipping Address)

• Create Order Ship to Address Screen

• Change Order Ship to Address Screen (see Create Order Ship to Address Screen)

• Change Customer Bill To Screen (Selecting, Changing, or Excluding a Billing Account)

• Create Customer Bill To Screen

• Work with B2B Order Screen

• Change Cust Sold to Name & Address Screen

• Catalog requests:

• Create Catalog Request Screen

• Change Catalog Request Screen

• Customer maintenance:

• First Create Sold To Customer Screen

• First Change Customer Screen (see First Create Sold To Customer Screen)

• Create Ship-to Customer Screen

• Change Ship to Customer Screen

• Create Customer Individual Screen

• Change Customer Individual Screen

• Working with Bill-To Customers:

• Create Bill-to Customer Screen

• Change Bill-to Customer Screen

• Working with Customer Memberships:

• Alternate Shipping Address Screen (Change Mode)

• Customer Membership Recipient Screen (Change Mode)

• Working with Fraudulent Customers:

• Create Fraudulent Customer Screen

• Change Fraudulent Customers Screen

• Order inquiry: Change Call Tag Address Screen

Including the prefix description on forms: The prefix description appears on the following printed forms only if the print program specified supports it:

• Pick Printing Program (C37): FLR1104

• A/R Statement Print Program (B85): ACR0516 (also, the Statement Processing Program (B84) should be set to ACR0515) if the statement should include the same information as the base statement

• A/R Statement Print Program (B85): ACR0526 (also, the Statement Processing Program (B84) should be set to ACR0525) if the statement should include the customer sold-to number and the pick control number

• Backorder Card Print Program (D04): BOR0037

• Soldout Notification Print Program (E75): CSR1370

Note:

• If you specify a print program that does not support printing the prefix description, the form will print just the prefix code.

• No other forms or reports besides those listed above automatically print the full prefix description. For example, catalog request labels print the prefix code, rather than the description.

Enter N or leave this field blank if you do not want the system to make the entries in the Prefix file available on screens where you enter a customer prefix. In this case, prompting (F4) on the Prefix field does not display the contents of the Prefix file. Also, the prefix description will not be included on any printed forms.

Additional Charge Group Code for Freight (I29)

Purpose: Use this screen to specify the additional charge group code indicating that a negative additional charge on an order represents a freight adjustment rather than a merchandise adjustment.

MSR0051 CHANGE Change System Control Value 6/05/03 15:58:01 Description . : Additional Charge Group Code for Freight Code . . . . . AMZ A AMZ B BA C D DB E Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the additional charge Group that identifies a negative additional charge applied to an Amazon order as a freight adjustment rather than a merchandise adjustment.

When you apply a negative additional charge to an Amazon order:

• If the additional charge code’s Group code matches this system control value, the system:

• decreases the Adjusted freight for the order line(s) in the Amazon Order Snapshot File (IXAOSS)

• specifies the credit amount in the ODT freight amount in the Amazon Order Adjustment File (IXAADJ)

• creates an order transaction history record that includes the message AMZADJ FRT5.67, where 5.67 is the amount of the credit applied to the order

• If the additional charge code’s Group code does not match this system control value, the system:

• decreases the Adjusted price for the order line(s) in the Amazon Order Snapshot file

• specifies the credit amount in the ODT Price field in the Amazon Order Adjustment file

• creates an order transaction history record that includes the message AMZADJ PRC5.67, where 5.67 is the amount of the credit applied to the order

Leave this field blank if you do not use the Amazon Order Feed.

Gift Certificate Pricing Method (I54)

Purpose: Use this screen to indicate the price the system will use as the gift certificate amount.

MSR0051 CHANGE Change System Control Value 2/12/04 15:48:52 Description . : Gift Certificate Pricing Method Code . . . . . OFFER ORDER Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the price the system will use as the gift certificate amount.

The system applies the amount to the gift certificate when the gift certificate item is processed through billing.

OFFER indicates the offer price is the amount applied to the gift certificate.

Enter OFFER if you want the ability to discount the amount charged to purchase a gift certificate, while still applying the full amount to the gift certificate. For example, you can purchase a $25.00 gift certificate for $22.00 and still apply $25.00 to the gift certificate.

If you enter OFFER, make sure you define an offer price for each gift certificate item. If the gift certificate item you purchase does not have an offer price defined, the system uses the order line price as the amount to apply to the gift certificate. If both the offer price and order line price are $0.00, the gift certificate amount is $0.00.

ORDER indicates the order price is the amount applied to the gift certificate.

Enter ORDER if you do not wish to discount the amount charged to purchase the gift certificate. The amount applied to the gift certificate is always the order line price. For example, if the order line price is $25.00, the amount applied to the gift certificate is $25.00.

However, if the order line price is $0.00, the system uses the offer price as the amount to apply to the gift certificate. If both the order line price and offer price are $0.00, the gift certificate amount is $0.00.

Leave this field blank if you wish the system to use the ORDER price as the amount to apply to the gift certificate.

General Ledger posting: During billing, the system posts a discount to the general ledger if the offer price and the actual selling price do not match and a Merchandise discount general ledger number exists for the division associated with the order.

Sales posting with discount
	Debit		Credit
G/L Account:	Sales G/L #	Merchandise Discount G/L #	Merchandise Sales G/L #
File:	Pay Type G/L file	Division G/L file	Division G/L file
Example:	1.05	1.00	2.05

To separate the posting for gift certificate discounts from other discounts, create an item class that represents gift certificate items and define a separate Discount general ledger account number for the item class.

Sales posting with discount
	Debit		Credit
G/L Account:	Sales G/L #	Merchandise Discount G/L #	Sales G/L #
File:	Pay Type G/L file	Item Class file (gift certificate item class)	Item Class file (gift certificate item class)
Example:	1.05	1.00	2.05

For more information: See Working with Gift Certificates for more information on gift certificate processing.

SmartLabel/SmartPost Values (I60)

Purpose: Use this screen to specify values related to printing pick slips for SmartLabel returns integration or for printing SmartPost pick slips.

MSR1435 ENTER Edit SmartLabel/SmartPost Values 9/25/07 15:33:46 Mail Order Company Scanned Return Input Mode . . WRTA (WRTA, OEOM) FTP Script for ARN Import . . . NSL NEWGISTICS SMARTLABEL FTP Merchant ID . . . . . . . . . 1234 SmartLabel D-U-N-S # . . 123456789 SmartLabel Item Weight . . 70.000 SmartPost Application ID Prefix 123 SmartPost Application ID . . . . 34 SmartPost USPS Service Type . . 60 Application area . . . . . . . C/S Application group . . . . . . . ALL F3=Exit F12=Cancel

On this screen:

SmartLabel Return settings:

• SmartLabel Scanned Return Input Mode (I61)

• SmartLabel FTP Script for ARN Import (I62)

• SmartLabel Merchant ID (I46)

• SmartLabel D-U-N-S Number (I47)

• SmartLabel Item Weight Limit (I48)

SmartPost Pick Slip settings: To print the base SmartPost pick slip, enter FLR1198 in the Pick Printing Program (C37) system control value; see Printing SmartPost Pick Slips for more information on the required setup.

• SmartLabel D-U-N-S Number (I47)

• SmartPost Application ID Prefix (J77)

• SmartPost Application ID (J78)

• SmartPost USPS Service Type (J79)

SmartLabel Scanned Return Input Mode (I61)

Specifies whether to use order maintenance or work with return authorizations to process SmartLabel returns through the Processing SmartLabel Returns (PSLR) menu option. Valid values are:

• OEOM: You advance to the Work with Order Screen when you specify a barcode at the SmartLabel Returns Screen. If your entry at the SmartLabel Returns screen does not identify a shipment against an order, you advance to the Order Maintenance Selection Screen, where you can select an order for return.

• WRTA: You advance to the:

• Work with Returns for Order Screen if the Use Streamlined Return Authorizations (F44) system control value is set to Y.

• Work with Return Authorization Detail Screen if the Use Streamlined Return Authorizations (F44) system control value is set to Y and this is the first return created for the order, or the Work with Return Authorizations Screen if there is already one or more returns create for the order.

• Select Orders For Return Authorization Screen if your entry at the SmartLabel Returns screen does not identify a shipment against an order.

• blank: You cannot use the Processing SmartLabel Returns (PSLR) menu option.

SmartLabel FTP Script for ARN Import (I62)

Specifies the FTP script to use as part of the Importing Return Notifications process. The periodic function you use to import return notifications calls this script in order to populate the SmartLabel ARN file, and then uses the contents of the SmartLabel ARN file to populate the Return Notifications file. See Importing Return Notifications for more information.

Leave this field blank if you do not use SmartLabel returns processing.

SmartLabel Merchant ID (I46)

Specifies the Client ID for the SmartLabel barcode on the pick slip if you use SmartLabel returns processing.

Code field: Enter the four-position Client ID to include in the SmartLabel barcode if you use SmartLabel returns processing. This identification number is assigned by Newgistics. See Using SmartLabel Returns Processing for more information.

Note: This Client ID is different from the two-position Client ID specified in the Warehouse/Entity file and used as part of the USPS barcode on the SmartLabel. See Work with Warehouse/Entity Screen for more information on setting the Client ID for the USPS barcode.

Leave this field blank if you do not use SmartLabel returns processing.

SmartLabel D-U-N-S Number (I47)

SmartLabel returns: Specifies the Client ID for the USPS barcode on the pick slip if you use SmartLabel returns processing.

SmartPost picks: Specifies the nine-position D-U-N-S number to include in the barcode on the FedEx SmartPost label. The system prints the FedEx SmartPost label on the SmartPost pick slip (print program FLR1198 is defined in the Pick Printing Program (C37) system control value).

Code field: Enter your nine-position D-U-N-S number. Enter the nine digits only, omitting any hyphens or spaces. For example, if your D-U-N-S number is 01-234-56789, enter 0123456789.

What is the D-U-N-S number? The D-U-N-S number is a unique, nine-position ID assigned by the Dun & Bradstreet Corporation to identify business entities.

For more information: See:

• Using SmartLabel Returns Processing

• Printing SmartPost Pick Slips

Leave this field blank if you do not use SmartLabel returns processing or do not print the SmartPost pick slip.

SmartLabel Item Weight Limit (I48)

Specifies the weight limit to prevent the SmartLabel from printing on a pick slip if you use SmartLabel returns processing.

Weight field: Enter the maximum weight allowed for any single item in order to print a SmartLabel on the pick slip if you use SmartLabel returns processing. If any single item on the pick slip has a Ship weight larger than the weight limit specified here, such as 70 pounds, the pick slip will not include a SmartLabel.

The pick slip can include the SmartLabel only if the Pick Printing Program (C37) is FLR1116.

How is shipping weight determined? The system checks the Ship weight at the SKU level first; if there is no ship weight at the SKU level, the system uses the Ship wgt. (Shipping weight) at the item level.

If the item/SKU does not have a shipping weight identified, either at the SKU or the item level, the system does not suppress printing the SmartLabel based on item weight.

The system prints the SmartLabel as long as none of the items on the pick slip have a single-unit shipping weight that is over the limit. For example, if the limit is 70 pounds, and the pick slip includes two units at 35 pounds each, the SmartLabel still prints.

Leave this field blank if you do not use SmartLabel returns processing. The system does not print a SmartLabel on the pick slip, regardless of the print program used.

For more information: See Using SmartLabel Returns Processing.

SmartPost Application ID Prefix (J77)

Number field: Enter the application ID prefix to include in the barcode on the FedEx SmartPost label. The system prints the FedEx SmartPost label on the SmartPost pick slip (print program FLR1198 is defined in the Pick Printing Program (C37) system control value)

SmartPost Application ID (J78)

Number field: Enter the application ID to include in the barcode on the FedEx SmartPost label. The system prints the FedEx SmartPost label on the SmartPost pick slip (print program FLR1198 is defined in the Pick Printing Program (C37) system control value).

SmartPost USPS Service Type (J79)

Number field: Enter the USPS service type that controls the service type description to print above the barcode on the SmartPost pick slip. The system prints the FedEx SmartPost label on the SmartPost pick slip (print program FLR1198 is defined in the Pick Printing Program (C37) system control value).

• Enter 02 to print the FedEx SmartPost Label: Delivery Confirmation 1lb and Over (Default Label) or FedEx SmartPost Label: Delivery Confirmation Under 1lb.

• Enter 56 to print the FedEx SmartPost Label: Non-Delivery Confirmation Under 1lb.

Generate Sale Credit for Orders with Sale Items (I64)

Purpose: Use this screen to indicate whether to generate sale credits as refunds for sale items.

MSR0052 CHANGE Change System Control Value 3/04/04 13:32:38 Description . : Generate Sale Credit for Orders with Sale Items Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . IDC Sequence# . . . F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the system generate sale credits as refunds for returned items that are on sale.

When does the system generate a sale credit? The system generates a sale credit if:

• the returned item is flagged as a Sale item in the Item Offer or SKU Offer that applies to the order detail line, and,

• the pay type:

• is a coupon/credit pay category (category 5), or

• has an Alt refund type (Alternate refund type) that is a coupon/credit pay category, or

• has an Alt refund category (Alternate refund category) of coupon/credit

Refunds for both sale and non-sale items: Processing separate returns against a sale item and a non-sale item on the same order can generate two refunds: the refund for the sale item is a sale credit (provided the pay type meets the requirement described above), while the refund for the non-sale item follows the regular logic to determine the refund type. However, processing returns against multiple items on the order at the same time produces a sale credit if one of the items is a sale item.

For example, item AB100 is a sale item, while item BC200 is a non-sale item. If the customer returns AB100 one day and return BC200 on another day, the system generates a sale credit for the first return but not for the second return. However, if the customer returned both AB100 and BC200 at the same time, and you processed the returns against both items in a single session, the system generates a sale credit for both.

Enter N or leave this field blank if you do not want to generate sale credits for sale items.

Stored Value Card Processing Values (I71)

Purpose: Use this screen to specify values related to stored value card processing. See Stored Value Card Overview and Setup.

MSR1447 ENTER Edit Stored Value Card Processing Values 9/26/05 9:42:32 KAB Co Use streamlined billing . . . . . . . . . . . . . Y (Y/N) Use batch processing . . . . . . . . . . . . . . . Y (Y/N) Modulus checking method . . . . . . . . . . . . (MU/M10/M11) Activation pricing method . . . . . . . . OFFER (OFFER/ORDER) Activation authorization service . . . . . . . . DVT E-mail notification program . . . . . . . CSR1374 Remove card# at activation . . . . . . . . . . . . N (Y/N) Use Swipe Card Entry . . . . . . . . . . . . . . . N (Y/N) Generate SVC refunds for merch credits . . . . . . Y (Y/N) Default SVC refund item number . . . . . SVCMERCH2 Price override reason for SVC refund . . . . . . . V Default pick generation template . . . . . . 57 Perform balance inquiry during pick gen . . . . . Y (Y/N) Hold reason for insufficient funds . . . . . . . SV Perform reversal at deposit . . . . . . . . . . . Y (Y/N) Retain authorization at deposit . . . . . . . . . N (Y/N) Combine SVC on one pick ticket . . . . . . . . . . N (Y/N) F3=Exit F12=Cancel

Use Streamlined Stored Value Card Billing (I23)

Indicates if the system sends pick control records containing physical stored value card items to billing once you assign numbers to the physical cards.

Yes/No field: Enter Y in this field if you wish the system to send pick control records containing physical stored value cards to billing once you assign numbers to the physical cards; this assumes you never send pick control records containing physical stored value cards to a manifesting station to wand and bill the stored value card items.

You assign numbers to physical stored value cards by pick control number using the Working with Physical Stored Value Card Assignment (WPSA) menu option. When you press F9 at the Stored Value Card Assignment Screen to assign the numbers to the stored value cards, the system sends the associated pick control records to billing.

Enter N or leave this field blank if you typically send pick control records containing physical stored value items to your manifest station to wand and bill the stored value card items.

Note: If you change the setting of this system control value, you must stop and restart the Billing Async.

For more information: See Billing a Stored Value Card for more information on the stored value card processing the system performs when a stored value card item is billed.

Use Stored Value Card Batch Processing (I50)

Defines whether stored value card activation and stored value card authorization reversal transactions are processed immediately or in batch.

Yes/No field: Enter Y in this field if you wish to process stored value card activation and authorization reversal transactions in batch mode.

When you activate a stored value card or process a stored value card authorization reversal, the system generates a stored value card download trigger record.

• If this system control value is set to Y, the system does not process the stored value card trigger records until you submit the batch process using:

• the Transmitting Stored Value Card Transactions (SSVC) menu option.

• the SVCACT periodic function (program name PFR0076) for activations.

• the SVCREV periodic function (program name PFR0077) for authorization reversals.

• If this system control value is set to N, the SVC Activation and SVC Reversal integration layer jobs monitor for stored value card download trigger records to process immediately.

Paymentech integration: Immediate processing of stored value card activation and authorization reversal transactions is currently not implemented at this time with the CWIntegrate CWDirect/Paymentech integration; see the CWIntegrate CWDirect/Paymentech integration reference for additional information.

ValueCard integration: Enter N this system control value to have near real-time integration when sending activations and authorization reversals to CWValueCard.

For more information: See:

• Stored Value Card Purchase and Activation for more information on the processing that occurs when you activate a stored value card.

• Stored Value Card Authorization Reversal for more information on the processing that occurs when you perform a stored value card authorization reversal.

Stored Value Card Modulus Checking Method (I24)

Indicates if the system performs a calculation against the digits of the stored value card number to ensure that the card is valid.

Code field: Enter the type of modulus check you wish to perform against the stored value card number. If you define a modulus check, you can validate the stored value card number before sending the card to the service bureau for activation.

The types of modulus checks you can perform are:

M10: The system performs a modulus 10 check against the stored value card number.

M11: The system performs a modulus 11 check against the stored value card number.

MU: The system performs a user-defined check against the stored value card number. Note: If you enter MU in this field, the system verifies that a program is defined in the User Defined Modulus Check Program (E94) system control value. If a program is not defined, an error message displays: User defined modulus program not defined-SCV E94.

The system performs the modulus check against the stored value card number at the Stored Value Card Assignment Screen screen.

Note: The system cannot perform a modulus check against the number if the number contains spaces; for example: 478825 0000 121443. To perform a modulus check, you must enter the number without any spaces between the numbers; for example: 4788250000121443.

Leave this field blank if you do not wish to perform a modulus check against the stored value card number. The service bureau will perform validation against the stored value card number during the activation process. If the stored value card number is not valid, the activation request will be declined.

Stored Value Card Activation Pricing Method (I25)

Indicates the price the system will use as the stored value card issue amount.

Code field: Enter the price the system will use as the stored value card amount.

The system applies the amount to the stored value card when the stored value card item is processed through billing; see Billing a Stored Value Card.

OFFER indicates the offer price is the amount applied to the stored value card.

Enter OFFER if you want the ability to discount the amount charged to purchase the stored value card, while still applying the full amount to the card. For example, you can purchase a $25.00 stored value card for $22.00 and still apply $25.00 to the card.

If you enter OFFER, make sure you define an offer price for each stored value card item. If the stored value card item you purchase does not have an offer price defined, the system uses the order line price as the amount to apply to the stored value card. If both the offer price and order line price are $0.00, the stored value card issue amount is $0.00.

ORDER indicates the order price is the amount applied to the stored value card.

Enter ORDER if you do not wish to discount the amount charged to purchase the stored value card. The amount applied to the stored value card is always the order line price. For example, if the order line price is $25.00, the amount applied to the stored value card is $25.00.

However, if the order line price is $0.00, the system uses the offer price as the amount to apply to the stored value card. If both the order line price and offer price are $0.00, the stored value card issue amount is $0.00.

Leave this field blank if you wish the system to use the ORDER price as the amount to apply to the stored value card.

For more information: See Stored Value Card Purchase and Activation.

Stored Value Card Activation Authorization Service (I26)

Defines the service bureau used to process stored value card activation requests.

Code field: Enter the code for the service bureau used to process stored value card activation requests.

Enter RLT in this field if you use the Relate Stored Value Card Integration.

Leave this field blank if you do not offer stored value cards for purchase.

For more information: See Activating a Stored Value Card.

Stored Value Card Email Notification Program (I30)

Defines the program used to generate Stored Value Card Notification emails.

System name field: Enter the name of the program the system uses the generate Stored Value Card Notification emails. The base program name is CSR1374.

The system generates a Stored Value Card Notification email when an order containing a stored value card item is billed and:

• the stored value card is a virtual card (SVC type V). The email is sent to the recipient card holder on the order, indicating the number the customer can use to purchase merchandise using the stored value card as payment.

• the stored value card is a physical card with email notification (SVC type E). The email is sent to the recipient card holder on the order, indicating the physical card is in the process of being shipped to the customer.

Leave this field blank if you do not wish to generate Stored Value Card Notification emails. If you wish to offer stored value card items for purchase, you must create the card as a physical card (SVC type P or E). An email is required for virtual stored value cards.

Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for stored value card notifications if the Use email API flag for the email template is set to Y. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email and include promotional information. See Outbound Email API for an overview.

For more information: See Stored Value Card Notification Email for more information on defining a template for the email and to review a sample email. You can also set up an email template at the entity level as an override; see Email Template Override at Entity Level for more information.

Generate SVC Refund for all Merchandise Credit Refunds (I72)

Indicates whether the system generates a stored value card refund in place of a merchandise credit refund.

Enter Y in this field to have the system generate a stored value card refund in place of a merchandise credit refund.

The system generates a stored value card refund in place of a merchandise credit (or sale credit) in the following situations:

• The original pay type on the order was a coupon/credit pay category (category 5) and the alternate refund type defined for the pay type is blank or another coupon/credit pay category.

• The Generate Sale Credit for Orders with Sale Items (I64) system control value is set to Y, the returned item is a Sale item in the Item Offer or SKU Offer, and the pay type is a coupon/credit pay category (category 5). Note: The system continues to generate a sale credit if the Generate Sale system control value is set to Y, the returned item is a Sale item in the Item Offer or SKU Offer, and the pay type has an Alternate refund type that is a coupon/credit pay category or an Alternate refund category of coupon/credit.

In addition, regardless of the setting of the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value, the system generates a stored value card refund when:

• The alternate refund type defined for a pay type is a stored value card.

• You process a return outside the Return Grace Period (B52) and the Alternate Pay Type (B51) is a stored value card pay type.

• You change a refund to a stored value card refund (refund type V) in Working with Refunds, Writeoffs and Balances Due (WREF).

Note: If you change a refund to a merchandise credit (refund type M), bonus credit (refund type B), or sale credit (refund type S) in Work with Refunds (WREF), the system does not change the refund to a stored value card refund, regardless of the setting of the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value.

Foreign currency: If you use Multi Currency by Offer (E03) or Use Alternate Currency Pricing (H89), the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value should be set to N; otherwise, the system may generate a stored value card refund for an order in a foreign currency even though stored value cards are only allowed in US currency.

Enter N in or leave this field blank if you do not want the system to generate a stored value card refund in place of a merchandise credit refund.

For more information: See Generating Stored Value Card Refunds.

Default SVC Refund Item Number (I73)

Defines the stored value card item the system adds to an order when you process a stored value card refund.

This item represents the new stored value card that is sent to the customer for the amount of the processed refund. The system adds this item to the order at no charge and defaults the price override reason code defined in the Price Override Reason for SVC Refund Item (I74) system control value to the order line.

You can prompt on this field to display a list of available items; however, the SVC type field for the item you select must be set to P (physical stored value card) or E (physical stored value card with early notification). Additionally, the item must be a non-SKU item.

Note: The system will not generate a stored value card refund unless the stored value card refund item has available inventory. If the item does not have available inventory, the stored value card refund remains unprocessed.

The system requires a stored value card item number in this field if you entered Y in the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value.

Note: The system displays an error message if you press Enter at the Stored Value Card Processing Values (I71) umbrella system control value if the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value is set to Y and this system control value is blank: Refund Item# Required.

The system automatically generates a pick slip for the stored value card item if you define a pick slip generation template in the Default Pick Generation Template for SVC Refund Processing (I75) system control value.

Leave this field blank if you do generate stored value card refunds. The system displays an error message at the Process Refunds Screen if you select to generate stored value card credits and this system control value is blank: Sys Con Values I73 & I74 must be populated first.

For more information: See Generating Stored Value Card Refunds.

Price Override Reason for SVC Refund Item (I74)

Defines the price override reason code the system defaults to the stored value card no charge order line that is added to an order when you process a stored value card refund.

You can prompt on this field to display a list of available price override reason codes.

The system requires a price override reason code in this field if you entered Y in the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value.

Note: The system displays an error message if you press Enter at the Stored Value Card Processing Values (I71) umbrella system control value if the Generate SVC Refund for all Merchandise Credit Refunds (I72) system control value is set to Y and this system control value is blank: Override Reason Required.

The Default SVC Refund Item Number (I73) system control value defines the stored value card item the system adds to an order when you process a stored value card refund. This item represents the new stored value card that is sent to the customer for the amount of the processed refund. The system adds this item to the order at no charge and defaults the Price Override Reason for SVC Refund Item to the order line.

Price override reason code setup: The price override reason code you select to default to the stored value card refund item must have the Override item offer price field set to N. Otherwise, the system will activate the new stored value card for the price defined in the SKU Offer or Item Offer file instead of activating the new stored value card for the refund amount.

Leave this field blank if you do not generate stored value card refunds. The system displays an error message at the Process Refunds Screen if you select to generate stored value card credits and this system control value is blank: Sys Con Values I74 & I74 must be populated first.

For more information: See Generating Stored Value Card Refunds.

Default Pick Generation Template for SVC Refund Processing (I75)

Defines the pick slip generation template the system uses to automatically generate a pick slip for the stored value card item that is added to an order when you process a stored value card refund.

If you access this system control value using the Stored Value Card Processing Values (I71) umbrella system control value, you can prompt on this field in order to display a list of the available pick slip generation templates.

To create a pick slip generation template that prints a pick slip for the stored value card refund item, enter Y in the Selected items field on the Pick Slip Generation (1 of 2) screen and enter the item number defined in the Default SVC Refund Item Number (I73) system control value on the Select Items for Pick Slip screen.

Leave this field blank if you do not wish to automatically process a pick slip for a stored value card item that is added to an order when you process a stored value card refund. You will need to advance to Work with Pick Slip Generation (WPSG) to generate a pick slip for the stored value card item so that the card can be picked, activated, billed, and shipped to the customer.

Perform Balance Inquiry during Batch Authorizations (J19)

Indicates whether the system performs a balance inquiry before performing a batch authorization against a stored value card pay type during pick slip generation and drop ship processing.

Enter Y in this field if you wish to perform a balance inquiry against a stored value card pay type before performing a batch authorization against the card.

The system sends a balance inquiry request in batch format to the service bureau to determine the balance on the card.

• If the balance on the card is equal to or greater than the amount to authorize for the pay type on the order, the system continues with pick slip generation and sends a batch authorization request to the service bureau to authorize the card for the specified amount.

• If the balance on the card is less than the amount to authorize for the pay type on the order, and:

• the stored value card is the catch-all pay type on the order, the system places the order on hold, using the Hold Reason for Stored Value Cards with Insufficient Funds (J18) and does not generate a pick slip for the order. Note: If a hold reason code is not defined, a pick slip is not generated; however, the order remains in an open status.

• there is a different catch-all pay type on the order, such as a credit card, the system authorizes the stored value card for the remaining balance and authorizes the catch-all pay type for the remaining amount to authorize.

ValueCard: If you use ValueCard as your service bureau, the system does not validate that the card number sent to ValueCard is valid until after the batch balance inquiry has been performed. If the card is an invalid number, the balance inquiry response will indicate that the balance on the card is zero, instead of returning a response code of 30 Invalid Card Number.

SVC Balance Inquiry process: The setting of this system control value determines whether the SVC Balance Inquiry integration layer job is an interactive job.

• If you enter Y in this system control value, the SVC Balance Inquiry integration layer job in not an interactive job. You can change, start, and stop this process.

• If you enter N in or leave this system control value blank, the SVC Balance Inquiry integration layer job is an interactive job. You cannot change, start and stop this process.

Enter N or leave this field blank if you do not wish to perform a balance inquiry against a stored value card type before performing a batch authorization against the card during pick slip generation and drop ship processing.

Relate stored value card integration: If you use the Relate Stored Value Card Integration, select this system control value. Relate will approve an authorization for an amount that is less than the required authorization amount for an order. If you do not select this system control value, you must require another credit card payment on an order.

For more information: See Batch Authorization Balance Inquiry.

Hold Reason for Stored Value Cards with Insufficient Funds (J18)

Enter the hold reason code the system uses to place an order on hold when you Perform Balance Inquiry during Batch Authorizations (J19) and the balance remaining on a catch-all stored value card pay type is less than the amount to authorize.

A list of valid hold reason codes displays to the right of this field.

Note: The system only places the order on hold if a balance inquiry response is received from the service bureau. If the system does not receive a response from the service bureau, for example, due to communication errors, the system will continue with batch authorization.

Leave this field blank if you do not want the system uses to place an order on hold when you Perform Balance Inquiry during Batch Authorizations (J19) and the balance remaining on a catch-all stored value card pay type is less than the amount to authorize. Even though the order will not be placed on hold, the system will still not generate a pick slip for the order since the catch-all stored value card pay type cannot cover the remaining amount to authorize.

For more information: See Batch Authorization Balance Inquiry.

Perform Authorization Reversal during Deposit Processing (J20)

Indicates whether the system performs a stored value card authorization reversal during deposit processing if the authorization amount is greater than the deposit amount.

Enter Y in this field if you wish to perform a stored value card authorization reversal during deposits processing if the original authorization amount is greater than the deposit amount.

The system places the difference between the authorization amount and the deposit amount in the reversalAmount and reversalAmountText tags in the Deposit Request XML Message (CWDepositRequest).

Example: If the original authorization amount is $50.00 and the deposit amount is $30.00, the amount in the reversalAmount field is $20.00.

Enter N in this field if you do not wish to perform a stored value card authorization reversal during deposits processing if the authorization amount is greater than the deposit amount.

The reversalAmount and reversalAmountText tags in the Deposit Request XML Message (CWDepositRequest) remain blank.

Note: Enter N this system control value if you are using the CWDirect/CWValueCard integration.

For more information: See Authorization Reversal Process During Deposits for more information.

Retain Unused Stored Value Card Authorization After Deposit (J21)

Indicates whether the system automatically voids a partially deposited stored value card authorization.

Enter Y in this field if you want the system to retain a stored value card authorization after it has been partially deposited. For example, if the authorization amount is 50.00 and the deposit amount is 40.00, the system will retain the remaining 10.00 on the authorization.

Enter N in or leave this field blank if you want the system to void the remaining balance against the authorization. For example, if the authorization amount is 50.00 and the deposit amount is 40.00, the system will void the remaining 10.00 on the authorization. If there are multiple authorizations for the order, the system will not void the other authorizations.

Note: Enter N in or leave this system control value blank if you are not using CWValueCard to process stored value card transactions.

Remove Stored Value Card Number After Activation (J22)

Indicates whether the system removes the stored value card number from the Stored Value Card file once the stored value card has been activated.

Enter Y in this field if you want the system to remove the stored value card number from the Stored Value Card file once the stored value card has been activated. The system also removes the link between the stored value card number and the order number where the stored value card was purchased.

If this system control value is set to Y, the system generates the Stored Value Card Notification Email before removing the stored value card number from the Stored Value Card file. The stored value card number will be unencrypted and unformatted in the email since the customer needs to read the stored value card number for future purchases.

The Card # field on the Display Stored Value Cards Screen displays the words REMOVED BY SYSTEM.

Enter N or leave this field blank if you want the system to retain the stored value card number in the Stored Value Card file once the stored value card has been activated. The system also retains the link between the stored value card number and the order number where the stored value card was purchased.

You can review the activated stored value card number on the Display Stored Value Cards Screen.

Note: If you are using credit card encryption and you do not remove the stored value card number after activation, the stored value card number will be encrypted in the CWDirect database.

Use Swipe Card Entry for SVC Activations (J44)

Defines whether you wish to assign stored value card numbers to physical cards by manually entering the stored value card numbers on the Stored Value Card Assignment screen or by swiping the cards through a magnetic strip reader to default to the SVC Swipe Assignment screen.

Enter Y in this field if you want to assign stored value card numbers to physical cards by swiping the cards through a magnetic strip reader; the system defaults all of the data from the magnetic strip to the 64 position Stored value card number field on the SVC Swipe Card Assignment Screen. The 20 positions of the Stored value card number are sent to the service bureau for activation.

Enter N or leave this field blank if you want to assign stored value card numbers to physical cards by manually entering the card numbers in the 20 position Stored value card number field on the Stored Value Card Assignment Screen.

See Working with Physical Stored Value Card Assignment (WPSA) for more information on assigning a stored value card number to a physical stored value card.

Combine Stored Value Cards on One Pick Ticket (J53)

Defines whether the system combines all physical stored value cards on an order ship to on one pick slip.

Note: Regardless of the setting of this system control value, the system prints physical stored value cards on a separate pick slip(s) from other items on the order. In addition, if the physical stored value card item is set up as a ship alone item (Ship alone is S), the system generates a separate pick slip for each unit of a stored value card item.

In addition, this system control value controls whether the Stored Value Card Selection Screen displays in the Working with Physical Stored Value Card Assignment (WPSA) menu option.

Enter Y in this field if you want the system to generate one pick slip for all physical stored value card items on a ship to order.

In addition, the system displays the Stored Value Card Selection Screen in the Working with Physical Stored Value Card Assignment (WPSA) menu option to allow you to assign numbers to stored value cards by pick line number.

Example: An order contains the following items.

Order line#	Item	Order qty	Results
Ship to 1:
1	SVC1 (stored value card item)	1	The system generates 2 pick slips: • one pick slip containing all of the stored value card items. • one pick slip containing the regular item.
2	SVC2 (stored value card item)	2
3	REG1 (regular item)	2
Ship to 2:
1	REG2 (regular item)	2	The system generates 2 pick slips: • one pick slip containing the regular items. • one pick slip containing all of the stored value card items.
2	SVC1 (stored value card item)	2

Enter N or leave this field blank if you want the system to generate a separate pick slip for each order line containing a physical stored value card.

Note: If you wish to generate a separate pick slip for each unit of the stored value card item, set up the item as ship alone (Ship alone = S).

Example: An order contains the following items.

Order line#	Item	Order qty	Results
Ship to 1:
1	SVC1 (stored value card item)	1	The system generates 3 pick slips: • one pick slip containing the stored value card item on order line 1. • one pick slip containing the stored value card items on order line 2. • one pick slip containing the regular item.
2	SVC2 (stored value card item)	2
3	REG1 (regular item)	2
Ship to 2:
1	REG2 (regular item)	2	The system generates 2 pick slips: • one pick slip containing the regular items. • one pick slip containing the stored value card items on order line 2.
2	SVC1 (stored value card item)	2

Use Loyalty Membership Program (I81)

Purpose: Use this screen to indicate whether the background jobs should evaluate whether customers qualify for loyalty membership programs based on their order history.

MSR0052 CHANGE Change System Control Value 8/18/04 8:55:29 Description . : Use Loyalty Membership Program Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the system evaluate customers for membership in loyalty programs. Qualification for loyalty membership programs is based on the customer’s total merchandise sales or order dollars since the Effective start date of the loyalty program, plus any External sales dollars stored in the Customer Order History file. You can also set a loyalty program to subtract the dollar value of cancellations, soldouts, returns, or exchanges from the total, or to disregard this activity.

About loyalty programs: You can use loyalty programs to offer an order discount and other incentives to your best customers.

Evaluation takes place when?

• If the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to N, the ORDR_ASYNC and BILL_ASYNC background jobs evaluate the customer sold-to for each processed order to determine whether the customer qualifies for any active loyalty membership programs, and the customer API evaluates customers based on their order history, including external sales dollars.

• If the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to Y, the system evaluates the customer when you press F9, press F9, or press F21 in order entry. If you are using e-commerce, the order API, or the phone order load, the evaluation takes place when you submit the initial order message, with or without payment information.

Activate/deactivate: If this system control value is set to Y and the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to N, the background jobs and customer API continue to evaluate each customer associated with an order whenever there is order activity, such as entry, maintenance, or billing. The result can be to:

• activate a customer loyalty membership if the customer’s sales or order total, plus External sales, now make the customer qualify for the program

• deactivate a customer loyalty membership if the activity makes the customer ineligible for the loyalty program, or if the customer is now eligible for a different program

• make no change to a customer’s loyalty membership if the activity did not affect the customer’s eligibility for the current loyalty membership assignment

If the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to Y, the system does not re-evaluate a customer’s loyalty membership eligibility if there is an active loyalty membership.

Enter N or leave this field blank if you do not want the system to evaluate customers for loyalty membership eligibility. The system continues to apply the discount for any active loyalty memberships, regardless of the setting of this system control value.

For more information: See Loyalty Memberships for an overview.

Loyalty Membership Activation Notification Email Program (I82)

Purpose: Use this screen to specify the program that generates notification emails when the background jobs activate a new loyalty membership for a customer.

MSR0053 CHANGE Change System Control Value 8/18/04 9:20:21 Description . : Loyalty Membership Activation Notification Program System name . . OER1359 Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the name of the program to generate notification emails to customers when the system activates new loyalty memberships. The base program name is OER1359.

Email template: Use the Working with E-Mail Notification Templates (WEMT) menu option to set up the text to include in the email notification at the company level, or the Change Email Override Screen to set up an override template at the entity level.

“From” email address: You can use either the Confirmation Email Directory Address (I19) to specify the “from” email address to use for all emails generated in your company, or you can specify an override at the entity level by using the Working with Entity Email Overrides. However, using a different “from” email address based on entity might be confusing to your customers if the same customers commonly place orders in multiple entities within your company. In this situation, the “from” email address on an activation email might not match the entity where the customer places the majority of his or her orders.

Note: When a customer’s eligibility changes from one existing loyalty program to another (typically, because an increase in total order or sales dollars has “promoted” the customer to a higher loyalty program), the customer receives both an activation email for the new loyalty membership and a deactivation email for the old loyalty membership. Loyalty deactivation takes place only if the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to N.

Leave this field blank if you do not use loyalty memberships or do not need to generate activation notification emails.

For more information: See:

• Loyalty Memberships for an overview

• When Does the System Generate an Email Notification?

• Directory Address (“From” Email Address) Override at Entity Level

• the Loyalty Membership Deactivation Notification Program (I83)

Loyalty Membership Deactivation Notification Program (I83)

Purpose: Use this screen to specify the program that generates notification emails when the background jobs deactivate an existing loyalty membership for a customer.

MSR0053 CHANGE Change System Control Value 8/18/04 9:20:21 Description . : Loyalty Membership Activation Notification Program System name . . OER1359 Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the name of the program to generate notification emails to customers when the background jobs deactivate existing loyalty memberships. The base program name is OER1361.

Note: Loyalty deactivation takes place only if the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to N.

Email template: Use the Working with E-Mail Notification Templates (WEMT) menu option to set up the text to include in the email notification, or the Change Email Override Screen to set up an override template at the entity level.

“From” email address: You can use either the Confirmation Email Directory Address (I19) to specify the “from” email address to use for all emails generated in your company, or you can specify an override at the entity level by using the Work with Entity Email Overrides Screen. However, using a different “from” email address based on entity might be confusing to your customers if the same customers commonly place orders in multiple entities within your company. In this situation, the “from” email address on a deactivation email might not match the entity where the customer places the majority of his or her orders.

Note: When a customer’s eligibility changes from one existing loyalty program to another (typically, because an increase in total order or sales dollars has “promoted” the customer to a higher loyalty program), the customer receives both an activation email for the new loyalty membership and a deactivation email for the old loyalty membership.

Leave this field blank if you do not use loyalty memberships or do not need to generate deactivation notification emails.

For more information: See:

• Loyalty Memberships for an overview

• When Does the System Generate an Email Notification?

• Directory Address (“From” Email Address) Override at Entity Level

• the Loyalty Membership Deactivation Notification Program (I83)

Display Alternate Customer Cross Reference Window (I84)

Purpose: Use this screen to indicate whether to attempt to match customers based on the single alternate customer number specified in the Customer Sold To file (the “primary”), or to give equal priority to any of the alternate customer numbers stored in the Alternate Customer # Cross Reference file.

MSR0052 CHANGE Change System Control Value 9/03/04 11:12:45 Description . : Display Alternate Customer Cross Reference Window Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to indicate that the alternate customer number specified at the second Create/Change/Display Customer screen is the “primary” alternate customer number, and additional numbers stored in the Alternate Customer # Cross Reference file are old numbers saved for historical purposes only. If you enter a cross-reference number at a scan screen, the system displays the Alternate Customer Cross Reference window. This window indicates that your entry is out of date, and you should use the current “primary” alternate customer number to identify the customer.

Alternate Customer Cross Reference !!!Attention!!! Customer's Alternate Customer Number has been changed. Previous CST X-REF# NP is now CST X-REF# 293 F3=Exit F12=Cancel

Note: The alternate customer number field label displayed at this window and at other screens is defined by the Alternate Customer Number Label Description (H95).

If this system control value is set to Y, the system does not let you delete the customer’s “primary” alternate customer number; it is a required field.

Matching based on alternate customer number takes place only if more specific information, such as customer number, is not provided in the message.

Note: The setting of this system control value does not affect the logic of the Generic Customer Inquiry (Search) API when searching by alternate customer number. This integration always uses the Alternate Customer # Cross Reference file for searching, regardless of whether there is an “primary” alternate customer number.

Alternate customer numbers created how? Alternate customer numbers can be created or assigned through:

• creating a customer by any means, if the Assign Alternate Customer # (I88) system control value is set to Y; in this situation, the system assigns the number

• entering a specific number at the second Create or Change Customer screen in customer maintenance

• creating or updating a customer through the Generic Order Interface (Order API); in this case, the system updates the alternate customer number with the number specified in the inbound order message, if any

• creating or updating a customer through the Generic Customer API

About the Alternate Customer # Cross Reference file: The system automatically creates a record in this file for each alternate customer number assigned to a customer, and does not automatically delete any of the cross references. See Working with Alternate Customer Number Cross-References for information on the screens you use to review or work with this file.

Enter N or leave this field blank if you do not want to give a higher priority to the alternate customer number specified in the Customer Sold To file. When you search based on alternate customer number, the system checks all alternate customer numbers in the Alternate Customer # Cross Reference file, and displays all matching results. It does not indicate whether your entry was also found in the Customer Sold To file.

Summary of Alternate Customer Number Search Options

The system searches based on alternate customer number as follows at screens:

• Display Alternate Customer Cross Reference Window (I84) set to Y

• “Primary” match? If there is a single match to your entry in the “primary” alternate customer number in the Customer Sold To file, advance to a subsequent scan screen with this customer displayed as the first entry; if more than one customer has the same “primary” alternate customer number, display the most recently created customer (based on highest customer number) as the first entry at the subsequent scan screen.

• No “primary” match? If there are no “primary” matches to your entry, but there is a cross-reference match, display the Alternate Customer Cross Reference window before advancing to the subsequent scan screen, displaying the customer’s current “primary” number rather than your entry; if more than one customer has the same cross-reference number, display the most recently created customer (based on highest customer number) in the pop-up window before advancing to the subsequent scan screen.

• Display Alternate Customer Cross Reference Window (I84) set to NAdvance to a subsequent scan screen displaying all customers with matching cross-reference numbers sorted in ascending numeric order by customer number.

About interfaces: Regardless of the setting of this system control value, the system uses the same logic to select a customer based on alternate customer number as part of an interface. In this situation, there is no opportunity to display a window or indicate that the alternate customer number is not “primary,” so the system:

• selects the customer who has alternate number specified as the “primary,” if there is only one; otherwise,

• if there are multiple customers with the same “primary,” it selects the most recently created customer (indicated by the highest customer number) with a matching “primary”; otherwise,

• if there are no customers who have the specified alternate number as the “primary,” but there are matches in the Alternate Customer # Cross Reference file, it selects the customer who was assigned the matching cross-reference number most recently.

Note: Unlike other interfaces, the Generic Customer Inquiry (Search) API always uses the Alternate Customer # Cross Reference file for searching, regardless of whether there is an “primary” alternate customer number.

Scan screens: Searching by alternate customer number is available at the:

• Select Customer Bill-To Screen in Working with Cash Receipts (WCRT), Work with A/R Open Items (WARI), and Using A/R Inquiry (DARI)

• Select Customer Sold To Screen in customer maintenance

• Order Inquiry Scan Screen

• Order Maintenance Selection Screen

• Select Customer for Catalog Request Screen

• Select Customer Sold To For Order Screen

Interfaces: Matching based on alternate customer number is enabled through the:

• Generic Order Interface (Order API)

• Generic Customer History API

• email integration that is part of the Email Repository

• Generic Customer API

Amazon FTP Download Script (I87)

Purpose: Use this screen to specify the FTP script for the Amazon periodic function to use when copying Amazon files to an external server as part of your integration with Amazon.com¹.

MSR0051 CHANGE Change System Control Value 8/19/04 14:48:12 Description . : Amazon FTP Download Script Code . . . . . AMZ Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the App code that identifies the FTP script to copy Amazon files to an external server.

Extracting Amazon files: The Amazon periodic function:

1. Extracts all new records (whose Downloaded status flag is blank) from the following Amazon files into the QTEMP library:

• Amazon Order Detail (IXAOAD)

• Amazon Order Fulfillment (IXAOFF)

• Amazon Order Adjustment (IXAADJ)

2. Calls the Amazon FTP script, which moves the Amazon files from the QTEMP library to a folder under the ftproot folder on an external server. You can use your own programs or applications to transfer the data in these files and forward it to Amazon.com.

Note: The Amazon files are not saved in the QTEMP library after the FTP script moves them to the CWIntegrate server.

3. Makes an archive copy of the downloaded Amazon files in the Archive Library (C11). Each copy is named as follows, where 040820 represents the current date in YYMMDD format:

• AMOA040820 = Amazon Order Adjustment file

• AMOD040820 = Amazon Order Detail file

• AMOF040820 = Amazon Order Fulfillment file

4. Updates the following fields for the downloaded records in the Amazon Order Detail, Amazon Order Fulfillment, and Amazon Order Adjustment files:

• Downloaded status flag: set to X

• Download date: current date

• Download time: current time

Setup: The setup in CWDirect related to building an integration with Amazon.com is described in the following table:

Menu Option	Steps
Working with Periodic Functions (WPER)	Create a periodic function using the Program name PFR0078.
Working with Periodic Processes (WPPR)	Assign the periodic function to a periodic process.
iSeries Interface Setup (ISUP) and/or Working with FTP Application (WFTP)	Create an FTP script as follows: • the Internet address is the IP address of the external server where your integration with Amazon.com is installed Note: To determine the IP address, enter IPCONFIG at a command line on the CWIntegrate server. • the FTP commands are: 0001.00 user_ID password 0002.00 append qtemp/IXAOAD AmazonDownload\OrderAcknowledgement.txt 0003.00 append qtemp/IXAADJ AmazonDownload\OrderAdjustment.txt 0004.00 append qtemp/IXAOFF AmazonDownload\OrderFulfillment.txt 0005.00 quit where: • user_ID = a valid user ID on the external server • password = the correct password for the user ID Note: The FTP commands must specify the correct file names and paths to use when copying the files to the external server.
Work with System Values/Features (WSYS)	• set the Amazon FTP Download Script system control value to the App code of the FTP script • set the Archive Library (C11) system control value, if it is not already set

For more information: See Amazon Order Feed for an overview on additional functionality within CWDirect to support integration with Amazon.com.

Assign Alternate Customer # (I88)

Purpose: Use this screen to indicate whether the system should automatically assign an Alt cust # whenever it creates a new customer.

MSR0052 CHANGE Change System Control Value 8/20/04 8:55:29 Description . : Assign Alternate Customer # Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the system automatically assign an Alt cust # each time you create a new customer. The system uses the Alternate Customer # number assignment record, set up through Setting Up the Number Assignment File (WNUM), to determine the number to use when creating each customer.

How are customers created? You can create a new customer in any of the following ways:

• customer maintenance: see Creating and Updating Sold-to Customers (WCST)

• order entry: see Entering Orders Using Header Format

• catalog requests: see Entering Catalog Requests (WCAT)

• catalog request interface: see Working with the Catalog Request Interface (WCRU)

• the generic order API: see Generic Order Interface (Order API)

• the e-commerce interface: see E-Commerce Order Creation and E-Commerce Catalog Requests

• the phone order load: see Loading Remote Orders (LPHO)

• the generic customer API: see Generic Customer API

If alternate number specified: If there is an alternate customer number specified in the inbound message through the Generic Customer API or the Generic Order Interface (Order API), the system uses this number and does not automatically assign an alternate customer number when creating a new customer.

Alternate customer number cross-reference: The system also creates a record in the Alternate Customer # Cross Reference file when it assigns the alternate customer number. See Working with Alternate Customer Number Cross-References for more information.

Enter N or leave this field blank if you do not want the system to automatically assign an alternate customer number to each new customer.

Defer Purge During Customer API (I89)

Purpose: Use this screen to indicate whether to delete customers immediately based on a delete request through the generic customer API, or to save the information in the Customer API Work file so that you can review it first.

MSR0052 CHANGE Change System Control Value 8/20/04 8:55:29 Description . : Defer Purge During Customer API Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the CUSTOMR_IN process in Working with Integration Layer Processes (IJCT) retain the specified customer when it receives a Delete request through the generic customer API so that you can review the customer through the Working with Customer API (WCAI) menu option.

Deleting customers through the generic customer API: If the cst_action_type passed in the Inbound Customer Message (CWCustomerIn) is set to D (delete), the CUSTOMR_IN process creates a record for the deletion in the Customer API Work file, flagging the record with a status of P (eligible for purge), provided that it can identify the customer and that the customer is not associated with any existing orders, or any history in the Customer Sold To Order History file. If the CUSTOMR_IN finds an error, it puts the Customer API Work file record in ineligible (I) status, and assigns an error reason code. Possible error reasons are:

• 1 = No Match Found (that is, the CUSTOMR_IN process could not identify the customer to delete based on the customer number passed in the CWCustomerIn message)

• 2 = Orders Exist for Customer

• 3 = Ship to on Existing Order

• 4 = History exists

See the Customer API Report: Customers Ineligible for Purge for more information on these errors.

The system puts a Delete request in E (error) status if it cannot identify the customer based on the alternate customer number specified in the message.

To purge all Customer API Work file records in P status, press F10 at the Work with Customer API screen. You cannot select an individual request for deletion.

Set this field to N to have the CUSTOMR_IN process automatically delete customers when it receives a valid Delete request through the CWCustomerIn XML message. If there are any errors as described above, the CUSTOMR_IN process creates a Customer API Work file record and assigns an error reason as described above.

For more information: See Deleting a Customer for an overview.

Default Customer for Customer API (I90)

Purpose: Use this screen to indicate the customer record to use as a guideline indicating which fields can be overwritten with blanks when you process a customer update through the generic customer API.

MSR0054 CHANGE Change System Control Value 8/20/04 13:16:53 Description . : Default Customer for Customer API Number . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Number field: Enter the customer number that identifies the default customer for the CUSTOMR_IN process in Working with Integration Layer Processes (IJCT) to use as a guideline when processing a Change request through the generic customary API. The information specifies how to process customer updates as follows:

• For each field that is not provided in the Inbound Customer Message (CWCustomerIn), the CUSTOMR_IN process checks the corresponding field for the default customer specified here.

• If that field contains any data in the default customer record, then the CUSTOMR_IN process does not clear the information in that field for the customer being updated.

Example: The default customer has data in the home phone number field. The CUSTOMR_IN process receives a change request through the CWCustomerIn message. No home phone number is specified in the CWCustomerIn, message, and the specified customer currently has a home phone number on record. The CUSTOMR_IN process does not clear (blank out) the customer’s home phone number.

• Otherwise, if that field does not contain data in the default customer record, then the CUSTOMR_IN process clears that field when updating the customer.

Example: The default customer does not have data in the home phone number field. The CUSTOMR_IN process receives a change request through the CWCustomerIn message. No home phone number is specified in the CWCustomerIn message, and the specified customer currently has a home phone number on record. The CUSTOMR_IN process clears (blanks out) the customer’s home phone number.

Note: It does not matter what the data is in the corresponding field for the default customer record; the process simply checks to see whether there is any data.

Why use default customer? Using a default customer enables you to use the default customer API to process customer updates that do not include the customer’s complete name and address. You can receive just the information that needs to change, and leave other fields with their current values.

Regular customer validation still applies: The CUSTOMR_IN process still requires all of the same information required whenever you create or update a customer. For example, even if no city is provided through the CWCustomerIn message, the CUSTOMR_IN does not clear the City field for a customer.

Leave this field blank if you do not use the generic customer history API to process customer updates.

For more information: See the Generic Customer API for an overview.

Disregard Soldout Controls for Non-Allocatable Warehouses (J27)

Purpose: Use this screen to define whether the system disregards soldout control rules for inventory reserved against a non-allocatable warehouse.

MSR0052 CHANGE Change System Control Value 10/25/05 9:41:22 Description . : Disregard Sold-out Controls for Non-Allocatable Warehouses Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to disregard soldout control rules for inventory reserved against a non-allocatable warehouse.

You can reserve inventory against a non-allocatable warehouse if the Reserve from Non-Allocatable Warehouse (J25) system control value is set to Y.

The system evaluates the Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control value during order entry/maintenance and auto-soldout processing.

Adding items to an order: When you add an item to an order associated with a non-allocatable warehouse, the system:

• Reserves the item against the non-allocatable warehouse, regardless of the soldout control code defined for an item.

• If the item cannot be reserved, backorders the item in the non-allocatable warehouse or submits the item to the Order Broker if eligible. See the Order Broker Integration for background.

Note: You can manually sell out an item associated with a non-allocatable warehouse by entering 13 (sell out) next to the order line during order entry or maintenance.

Soldout control processing: When you perform auto-soldout control processing and the Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control value is set to Y, the system bypasses any order detail lines that are associated with a non-allocatable warehouse. See Processing Auto Soldout Cancellations (MASO).

Enter N or leave this field blank if you want the system to apply soldout control rules to inventory reserved against a non-allocatable warehouse.

Note: The system applies soldout control rules to inventory reserved against an allocatable warehouse regardless of the setting of this system control value.

SKU Cross Reference Type (J55)

Purpose: Use this screen to indicate the type of SKU cross reference to automatically create when you create a SKU.

MSR0051 CHANGE Change System Control Value 11/06/06 16:24:10 Description . : SKU Cross Reference Type Code . . . . . PSTS DMMS NSTS NUPC PSTS PUPC Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter a SKU cross reference type code if you would like the system to automatically create a SKU cross reference of this type whenever you create a new SKU. The system creates a SKU cross reference using the item and SKU codes, concatenated and with spaces removed, as the cross reference code.

Example: This system control value is set to PSTS. When you create a new SKU BLUE XLRG XLNG for item ABC12345, the system creates a SKU cross reference of type PSTS with a cross reference code of ABC12345BLUEXLRGXLNG.

About SKU cross references: You can use SKU cross references to make it easier to add items to orders using the item codes used by remote systems, such as retail outlets. When you enter or scan on the cross reference code at the SKU Cross Reference Selection Screen in order entry, the system retrieves the related item/SKU and adds it to the order. You use the Work with SKU Cross Reference # Screen to review or work with SKU cross references for an item/SKU in item maintenance.

About cross reference types: You use the Working with SKU Cross Reference Types (WSXT) menu option to define the SKU cross reference types in your company. For example, you might have a separate cross reference type for each external location that sends orders to CWDirect.The cross reference type also indicates whether you can automatically add an item to an order by simply entering the cross reference code in the Item field in order entry.

Why create cross references automatically? Having the system create SKU cross references automatically enables you to search by the regular CWDirect item code as well as any SKU cross references at the SKU Cross Reference Selection Screen in order entry.

For more information: See Work with SKU Cross Reference Type Screen for a discussion.

Leave this field blank if you do not want to create SKU cross references automatically when you create a new SKU.

Search SKU Cross Reference (J56)

Purpose: Use this screen to indicate whether to display the SKU Cross Reference Selection screen when you prompt on the Item field in order entry.

MSR0052 CHANGE Change System Control Value 11/06/06 16:46:42 Description . : Search SKU Cross Reference Yes/No . . . . Y (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want to display the SKU Cross Reference Selection Screen when you prompt on the Item field in order entry, item availability, and return authorizations. The system displays this screen only if the Display Item Alias (D56) system control value is also set to N; otherwise, if the Display Item Alias (D56) system control value is set to Y, it overrides the Search SKU Cross Reference system control value and you advance to the Alias Selection Screen when you prompt on the Item field.

Why display SKU Cross Reference Selection screen? Displaying this screen enables you to search for an item/SKU based on a cross reference to an external system, such as a retail outlet. If the SKU Cross Reference Type (J55) system control value is also set to a valid SKU cross reference type, the system automatically creates a SKU cross reference based on the CWDirect item and SKU codes whenever you create a SKU, so that you can search based on either external cross references or the CWDirect item and SKU.

Creating the SKU cross reference code: When the system creates the new SKU cross reference code as part of item/SKU creation, it uses the complete item code and SKU code(s) as the SKU cross reference code, with any blank spaces omitted. For example, when you create a SKU of BLUE 7 WIDE for item AB1234, the system creates a SKU cross reference code of AB1234BLUE7WIDE.

For more information: See Work with SKU Cross Reference Type Screen for a discussion of setting up SKU cross reference types, and see SKU Cross Reference Codes in Order Entry for a discussion of selecting items by SKU cross reference in order entry.

Enter N or leave this field blank if you do not want to display the SKU Cross Reference Selection Screen when you prompt on the Item field in order entry.

Send RA Message for RA Create (J57)

Purpose: Use this screen to define when the system generates the Generic WMS Customer Return XML Message (CWCustomerReturn) during non-streamlined return processing.

MSR0051 CHANGE Change System Control Value 11/16/06 10:45:18 Description . : Send RA Message for RA Create Code . . . . . CREATED PROCESSED BOTH Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code that identifies when you would like the system to generate the Generic WMS Customer Return XML Message (CWCustomerReturn) during non-streamlined return processing.

CREATED = The system generates the CWCustomerReturn message when the RA is created, but not yet received or credited.

PROCESSED or blank = The system generates the CWCustomerReturn message when the RA is completely processed (created, received, and credited).

BOTH = The system generates the CWCustomerReturn message when the RA is created and also when the RA is completed. However, if the return is created in one step, such as during streamlined return processing, the system generates the CWCustomerReturn message only when the RA is completed.

To generate the CWCustomerReturn message: In order to generate the Generic WMS Customer Return XML Message (CWCustomerReturn), you must:

• Enter Y in the Use PkMS Interface Values (F31) system control value.

• Enter program name IFR0086 in the PkMS Return/Case Interface Program (F38) system control value.

• Enter MQ in the PkMS Transport Type (G80) system control value.

• Enter GENERIC or GENERIC_2 in the RA Program XML Message Format (H45) system control value.

When is the CWCustomerReturn message generated? The system evaluates the Send RA Message for RA Create system control value to determine when to generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when you create a return through:

• the Work with Return Authorizations (WRTA) menu option; see Introducing Return Authorizations.

• the E-Commerce Return Request Message (CWReturn); see Creating Return Authorizations from the Web Storefront.

Regardless of the setting of the Send RA Message for RA Create system control value, the system generates the Generic WMS Customer Return XML Message (CWCustomerReturn) when the RA is completed (created, received, and credited) when:

• you create a return through interactive order entry/maintenance.

• you create a return by entering a negative quantity on an order line if the Send RA Message for Negative Quantity in OE/OM (J58) system control value is set to Y.

• you create a return through the Return Request Message (CWReturnIn); see Generic Return API.

• you use streamlined return processing and have full authority to create, receive, and credit the return.

• you create a misship return.

In addition, the system generates a Generic WMS Customer Return XML Message (CWCustomerReturn) when you delete an RA if the Send RA Message for RA Delete (J59) system control value is set to Y.

Streamlined returns: If you are using streamlined return processing, and the Send RA Message for RA Create system control value is set to CREATED or BOTH, and you only have authority to create the return, the system will generate the Generic WMS Customer Return XML Message (CWCustomerReturn) when the RA is created. In addition, if the system control value is set to BOTH, the system will also generate the Generic WMS Customer Return XML Message (CWCustomerReturn) when the RA is complete.

For more information: See CWCustomerReturn Message Generation Summary for more information on when the system generates the CWCustomerReturn message, based on the setting of the Send RA Message for RA Create (J57) system control value and whether you are using non-streamlined or streamlined return processing.

Send RA Message for Negative Quantity in OE/OM (J58)

Purpose: Use this screen to define whether the system generates a Generic WMS Customer Return XML Message (CWCustomerReturn) when a return is created by entering a negative quantity on an order line in order entry/maintenance, or through the Generic Order Interface (Order API).

MSR0052 CHANGE Change System Control Value 11/16/06 10:49:25 Description . : Send RA Message for Negative Quantity in OE/OM Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when you create a return by entering a negative quantity on an order line in interactive order entry/maintenance or through the Generic Order Interface (Order API).

When the return is processed, the system:

• creates the RA using information from the order detail line.

• Refund freight, Refund additional charges, and Refund handling defaults to N.

• Refund duty defaults to Y.

• if more than one order line is entered as a negative quantity, the system creates a separate RA for each order line; the system does not combine the negative order lines on a single RA.

• immediately creates, receives, and credits the RA in one step.

• generates a credit invoice for the RA.

Set items: If you enter an order line for a negative quantity for a set item, the system creates a separate order line for a negative quantity for the set header item and each component item; because of this, the system creates a separate RA for the set header item and each of the component items.

The system does not generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when a return is created by entering a negative quantity on an order line through the E-Commerce New Order Message (CWCreateOrder).

Enter N or leave this field blank if you do not want the system to generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when a return is created by entering a negative quantity on an order line.

Send RA Message for RA Delete (J59)

Purpose: Use this screen to define whether the system generates a Generic WMS Customer Return XML Message (CWCustomerReturn) when an RA is deleted.

MSR0052 CHANGE Change System Control Value 11/16/06 10:50:42 Description . : Send RA Message for RA Delete Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when an RA is deleted.

The system generates a separate CWCustomerReturn message for each unit on the deleted RA. 0 displays in the qty_to_return, qty_returned, and qty_credited to indicate the RA in the CWCustomerReturn message was deleted.

You can delete an RA in the Work with Return Authorizations (WRTA) menu option if you are using non-streamlined return processing and the RA has been created but not yet credited.

Enter N or leave this field blank if you do not want the system to generate a Generic WMS Customer Return XML Message (CWCustomerReturn) when an RA is deleted.

FTC - First Notice Output (J70)

Purpose: Use this screen to define how the system generates first backorder notices.

MSR0051 CHANGE Change System Control Value 5/07/07 8:34:21 Description . : FTC - First Notice Output Code . . . . . FILE FILE/PRINT PRINT Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code representing how the system generates first backorder notices (cards, emails, or the Outbound Email XML Message (CWEmailOut)).

Valid values are:

• PRINT or blank = Generate Backorder Cards (GBOC) produces first backorder notices.

• FILE = Generate Backorder Cards (GBOC) creates a record in the Backorder Cancellation Pending file for each first backorder notice. You can use the Working with Backorder First Notices (WBFN) menu option to review and generate first backorder notices.

• FILE/PRINT = Generate Backorder Cards (GBOC) produces first backorder notices and creates a record in the Backorder Cancellation Pending file for each first backorder notice. You can use the Working with Backorder First Notices (WBFN) menu option to review first backorder notices, but you can no longer print or email them.

Backorder cancellation pending file: When Generate Backorder Cards (GBOC) creates a record in the Backorder Cancellation Pending file for a first backorder notice because this system control value is set to FILE or FILE/PRINT, it flags the record with a Type of F (First Notice). This flag distinguishes first backorder notice records in the file from second backorder notice records (B B/O Card) and orders flagged for cancellation due to credit card decline (C Credit Card).

Work with First Notice (WBFN) menu option: If the FTP - First Notice Output (J70) system control value is set to FILE, you can use this menu option to review, work with, and generate first backorder notices.

For more information: See:

• Purchase Order Layering and Backorder Notifications: for more information on generating backorder notices.

• Working with Backorder First Notices (WBFN): for more information on working with and printing first backorder notices.

• Working with Backorders Pending Cancellation (WBPC): for more information on working with backorders pending cancellation.

Additional Charge Code for Pre Billed Amount Returns (J74)

Purpose: Use this screen to define the additional charge code to use for posting the return of a pre-billed item.

MSR0051 CHANGE Change System Control Value 9/18/07 15:04:28 Description . : Additional Charge Code for Pre Billed Amount Returns Code . . . . . RR A AF A1 A2 B D DD E ET F FR ... Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the additional charge code for the system to use when crediting the pre-billed amount when you process a return against the pre-bill amount item on an order.

Example: A customer orders item CO123, flagged for pre-billing based on its item category. That same day, you bill the designated pre-bill percentage of 50%, and subsequently ship the item to the customer. Later, the customer reports that the item was defective, so to improve customer satisfaction you want to refund the entire purchase price for the item. You enter a return against CO123, creating a refund for 50% of the selling price. You also enter a return against the pre-billed amount item; as a result, the system creates a negative additional charge for the remaining 50% of the purchase price, using the additional charge code specified in this system control value.

Note: The Maintenance of Pre Billed Amount Item (B18) secured feature controls the ability to process a return against the pre-billed amount item.

You use Establishing Additional Charge Codes (WADC) to set up additional charge codes.

For more information: See Pre Billed Amount Item (J72) for a general discussion on pre-billing, including methods of processing returns for pre-billed items.

Enter N or leave this field blank if you do not pre-bill items.

Additional Charge Code for Pre Billed Amount Soldouts (J75)

Purpose: Use this screen to define the additional charge code to use for crediting the pre-billed amount when you sell out a pre-billed item.

MSR0051 CHANGE Change System Control Value 9/18/07 15:07:48 Description . : Additional Charge Code for Pre Billed Amount Soldouts Code . . . . . RC A AF A1 A2 B D DD E ET F FR ... Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the additional charge code for the system to use when crediting the pre-billed amount when you sell out an item flagged for pre-billing. The system creates this negative additional charge when you use Processing Auto Soldout Cancellations (MASO) or when you sell out the pre-billable item in order entry.

Example: A customer places an order for item CO123, flagged for pre-billing based on its item category. That same day, you bill the designated pre-bill percentage of 50%. Afterward, you learn that you will not be able to fulfill any open orders for CO123 and use Processing Auto Soldout Cancellations (MASO) to sell out any open order lines. The system sells out CO123, and then applies a negative additional charge for the pre-billed amount.

You use Establishing Additional Charge Codes (WADC) to set up additional charge codes.

For more information: See Pre Billed Amount Item (J72) for a general discussion on pre-billing.

Enter N or leave this field blank if you do not pre-bill items.

Prevent Storing the Customer’s Last CC# and Exp Date (J86)

Purpose: Use this screen to define whether the system prevents the storing of the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History and Customer Ship To Order History files.

MSR0052 CHANGE Change System Control Value 2/18/08 10:45:13 Description . : Prevent storing the customer's last cc# and exp date Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to prevent the storing of the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History and Customer Ship To Order History files.

Default previous pay type: The setting of the Default Previous Pay Type in Order Entry (D64) system control value defines whether to default the last pay type used by the customer on the most recent order to the customer’s new order. If the last pay type used by the customer is a credit card pay type and the Use Tokenization field for the authorization service defined for the pay type is N, 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. In addition, 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 and Customer Ship To Order History files 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 will need to provide a credit card number and expiration date.

The table below explains when the system stores the customer’s credit card number and expiration date and when the system defaults the customer’s previous payment method to an order, based on the setting of the Default Previous Pay Type in Order Entry (D64) and Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control values.

Default Previous Pay Type SCV (D64)	Prevent Storing CC # SCV (J86)	Results
blank	blank or N	Customer Sold To Order History File Customer Ship To Order History File The system stores the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History and Customer Ship To Order History files. If you use credit card tokenization, the number may be a token rather than the actual credit card number. Order Entry The system does not default the last pay type, credit card number or expiration date used by the customer on the most recent order to the customer’s new order.
valid pay type	blank or N	Customer Sold To Order History File Customer Ship To Order History File The system stores the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History and Customer Ship To Order History files. If you use credit card tokenization, the number may be a token rather than the actual credit card number. Order Entry The system compares the pay type defined in the Default Previous Pay Type in Order Entry (D64) system control value with the last pay type defined for the customer in the Customer Sold To and Ship To Order History files, and, if they match, the system defaults the customer’s payment information to the order. If the pay type default is a credit card pay type and the Use Tokenization field for the authorization service defined for the pay type is set to N, the system defaults the last credit card number and expiration date defined for the customer in the Customer Sold To and Ship To Order History files to the order.
ALL	blank or N	Customer Sold To Order History File Customer Ship To Order History File The system stores the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To and Customer Ship To Order History files. If you use credit card tokenization, the number may be a token rather than the actual credit card number. Order Entry The system defaults the last pay type defined for the customer in the Customer Sold To and Customer Ship To Order History files to the order. If the pay type default is a credit card pay type and the Use Tokenization field for the authorization service defined for the pay type is set to N, the system defaults the last credit card number and expiration date defined for the customer in the Customer Sold To and Customer Ship To Order History files to the order.
blank	Y	Customer Sold To Order History File Customer Ship To Order History File The system does not store the customer’s credit card number and expiration date in the Customer Sold To and Customer Ship To Order History files. Order Entry The system does not default the last pay type, credit card number or expiration date used by the customer on the most recent order to the customer’s new order.
valid pay type	Y	Customer Sold To Order History File Customer Ship To Order HIstory File The system does not store the customer’s credit card number and expiration date in the Customer Sold To and Customer Ship To Order History file. Order Entry The system compares the pay type defined in the Default Previous Pay Type in Order Entry (D64) system control value with the last pay type defined for the customer in the Customer Sold To and Customer Ship To Order History files, and, if they match, the system defaults the customer’s payment information to the order. Because the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value is set to Y, the system cannot default the last credit card number and expiration date used by the customer to the order because it is not stored in the Customer Sold To and Customer Ship To Order History files.
ALL	Y	Customer Sold To Order History File The system does not store the customer’s credit card number and expiration date in the Customer Sold To Order History file. Order Entry The system defaults the last pay type defined for the customer in the Customer Sold To Order History file to the order. Because the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value is set to Y, the system cannot default the last credit card number and expiration date used by the customer to the order because it is not stored in the Customer Sold To Order History file.

Conversion program: If you enter Y in the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value, you should run the following conversion program to remove the credit card numbers and expiration dates that currently exist in the Customer Sold To Order History file:

Call CVR0719 parm(‘’ x’999F’), where 999 is the company code

If you do not run this conversion program and you enter Y in the Prevent Storing the Customer’s Last CC# and Exp Date (J86) system control value, the system will retain the credit card numbers and expiration dates that currently exist in the Customer Sold To Order History file. However, once you place a new order for a customer, the system will then clear the customer’s credit card number and expiration date from the Customer Sold To Order History file.

Enter N or leave this field blank if you want the system to store the customer’s credit card number and expiration date that was most recently used on an order in the Customer Sold To Order History file. You can review the last credit card number and expiration date used by the customer on the Display Customer Order History Screen. However:

• If you use credit card tokenization, the number stored may be a token rather than the actual credit card number.

• If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number displays in the format specified at the Credit Card Number Layout Screen for the associated pay type. For example, ************1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview.

• If the operator does not have authority to the Restrict Access to Credit Card Numbers in OI and OM (A88) secured feature, this field is blank.

• If the last credit card payment method used was Bill Me Later, the description of the Bill Me Later pay type displays. See Bill Me Later Processing for an overview.

• If the last credit card payment method used was a Direct Bank Disbursement, the description of the Direct Bank Disbursement pay type displays. See Processing Direct Bank Disbursements/Electronic Checks for an overview.

Use Costing Method for Returns (K22)

Purpose: Use this screen to define whether the cost of a return is based on the original invoice detail cost or the current costing method cost.

MSR0052 CHANGE Change System Control Value 2/20/09 14:55:02 Description . : Use Costing Method for Returns Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to base the cost of a return on the current cost of the item.

Enter N in this field if you want the system to base the cost of a return on the original invoice detail cost.

FIFO costing: If you are using FIFO costing, leave this field blank so that the cost of the return is the same as the cost of the original invoice.

Include Held Orders in DMT Order Files (K52)

Purpose: Use this screen to define whether to include held, non-fraud orders when extracting order-related updates to the DMT download files.

MSR0052 CHANGE Change System Control Value 9/29/09 12:43:04 Description . : Include Held Orders in DMT Order Files Yes/No . . . . N (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want to include all orders, regardless of whether they are open or held, when downloading information to DMT.

When you run the command to create records in the DMT Order Header File and DMT Order Detail File, the program includes all OH (order header) records in the Marketing Download Trigger File, regardless of whether the order status is open or held, or whether the order and customer are flagged for fraud.

Note: If an unprocessed OH trigger record exists for an order in the Marketing Download file, the program does not create a record in the DMT Order Detail File even if there is an eligible LH (line history) trigger record for the order. As a result, leaving this system control value set to N prevents both OH and LH records from being processed.

Enter N in this field if you want the program to select OH records for download only if:

• the order is open, or

• if the order is held, it is held with a fraud hold reason code, and the customer sold-to is flagged as a fraud with an F in the Hold/bypass/fraud field.

Note: The system writes trigger records to the Marketing Download Trigger File regardless of the setting of this system control value; it is only the extract program, described under Populating the DMT Files, that checks the setting of this system control value to determine whether to include held, non-fraud orders.

For more information: See Working with the DMT Interface for an overview and complete description of the processing and file formats.

Include All Customer Merge/Purge Triggers in DMT (L17)

Purpose: Use this screen to define whether the customer sold to merge/purge process creates triggers in the Marketing Download Trigger file.

Yes/No field: Enter Y in this field to have the customer sold to merge/purge process create triggers in the Marketing Download Trigger file.

Related SCV: If you enter Y in this field, the Populate Marketing/PO Interface Trigger File (G33) system control value must be set to CUSTOMER, ORD/CUST, or ALL in order to create triggers in the Marketing Download Trigger file.

Creating merge/purge triggers: When you use Working with Merge/Purge Sold-to Names (MMCS) to merge duplicate sold to customers into a target customer, the system creates triggers in the Marketing Download Trigger file if the Include All Customer Merge/Purge Triggers in DMT (L17) system control value is Y and the Populate Marketing/PO Interface Trigger File (G33) system control value must be set to CUSTOMER, ORD/CUST, or ALL.

The type of trigger record created depends on whether the source sold to customer is retained as a ghost customer:

• A CM (Customer Merge) trigger record is created to indicate the source customer is merged into the target customer and retained as a ghost customer.

• A CP (Customer Purge) trigger record is created to indicate the source customer is merged into the target customer and removed from the system.

When you run the DMT Marketing Download Trigger Command to populate the DMT files, the system creates a record in the DMT Customer Merge/Purge File for each CM and CP trigger record.

Enter N or leave this field blank if you do not want the customer sold to merge/purge process to create triggers in the Marketing Download Trigger file.

For more information: See:

• Working with Merge/Purge Sold-to Names (MMCS) for more information on the customer sold to merge/purge process.

• Working with the DMT Interface for more information on the DMT Extract Process.

Stored Value Card Merchant ID for Activations (L69)

Use this screen to define the merchant ID the system sends to the service bureau for stored value card activation transactions.

MSR0051 CHANGE Change System Control Value 5/22/12 9:26:07 Description . : Stored Value Card Merchant ID for Activations Code . . . . . Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the merchant ID the system sends to the service bureau for stored value card activation transactions. The system uses this merchant ID before any other merchant IDs in the Merchant ID Hierarchy.

Supported integrations: This system control value is used only by the Chase Paymentech Orbital Gateway Integration.

Leave this field blank if you do not use the Chase Paymentech Orbital Gateway Integration.

For more information: See Stored Value Card Activation > Flex Cache Activation Process.

Require Order Message Entry (L73)

Purpose: Use this screen to define whether the system requires the entry of an order message before you exit Order Inquiry, Order Maintenance, or both.

MSR0051 CHANGE Change System Control Value 8/13/12 11:37:44 Description . : Require Order Message Entry Code . . . . . B I M Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Indicate whether you want the system to require the entry of an order message before you exit Order Inquiry or Order Maintenance. Valid values are:

• B = The system requires the entry of an order message before you exit Order Inquiry or Order Maintenance.

• I = The system requires the entry of an order message before you exit Order Inquiry.

• M = The system requires the entry of an order message before you exit Order Maintenance.

• blank = The system does not require the entry of an order message before you exit Order Inquiry or Order Maintenance.

Error message: Based on the setting of this system control value, if you advance to Order Inquiry/Maintenance and do not enter an order message before trying to exit, the system prevents you from exiting and displays an error message: You must enter an order message before exiting the order.

Before you can exit, you must enter an order message on the Work with Order Messages Screen. You can enter any order message you choose and select any Print code for the message. Note: You must enter a new order message; you cannot just change an existing order message.

Secured feature: If you have authority to the Bypass Order Message Entry Requirement (B22) secured feature the system does not require the entry of an order message before you exit Order Inquiry/Maintenance, regardless of the setting of the Require Order Message Entry (L73) system control value.

Accessing Order Maintenance through Order Inquiry: If the Require Order Message Entry (L73) system control value is set to B and you access Order Maintenance through Order Inquiry, the system requires you to enter an order message when exiting both Order Maintenance and Order Inquiry.

Enter Add Reason window: If the Require Reason for Lines Added in Order Maintenance (D75) system control value is set to Y, the system displays the Enter Add Reason window when you add an item in Order Maintenance. In this situation, if the system requires the entry of an order message before you exit Order Maintenance, the system displays the order message entry error message after displaying the Enter Add Reason window.

Order Inquiry Reason Codes window: If you advance to Order Inquiry or Order Maintenance from the Customer Selection Screen and the Require Reason in CTI (G98) system control value is set to Y, the system displays the Order Inquiry Reason Codes window requiring an order inquiry reason code before you exit Order Inquiry/Maintenance. In this situation, if the system requires the entry of an order message before you exit Order Inquiry/Maintenance, the system displays the order message entry error message before displaying the Order Inquiry Reason Codes window.

Maintaining an order through E-Commerce: If you maintain an order through e-commerce, for example, you maintain the order using the E-Commerce Maintenance Request Message (CWMaintenance), the system does not require the entry of an order message, regardless of the setting of the Require Order Message Entry (L73) system control value.

Leave this field blank if you do not want the system to require the entry of an order message before you exit Order Inquiry/Maintenance.

Use Credit Card Authorization Values (L75)

Purpose: Use this screen to specify values related to authorization and deposit processing. See Using the Credit Card Authorization Interface.

MSR1539 ENTER Authorization/Deposit Values 8/16/12 8:58:27 Company# 3 General Values Online Values Use auto auth . . . . . N (Y/N) Use online auth . . . . N (Y/N) Use encryption . . . : (Y/N/C/S) Verify only . . . . . . N (Y/N) Require token . . . . . N (Y/N) Auth full amt in O/E . N (Y/N) Token IJCT job . . . . CC_TOKEN # retrys . . . . . . . Pre-authorize B/Os . . N (Y/N) $ Threshold/reserved Auth merch only for D/S N (Y/N) Use enhanced AVS . . . N (Y/N) AVS hold/bypass . . . . N (Y/N) Partial cc# in log . . N (Y/N) Deposit Values $ Threshold/auth# . . . Level II/III discount . N (Y/N) Dft auth#/under $thresh Void unused auth . . . N (Y/N) Dft auth#/under $1.00 . Deposit bank# . . . . . . . Dft auth#/soft decline Service for download . . . Dft vendor response . . Service for conditional dep Max # of retrys . . . . Service for inquiries . F3=Exit F12=Cancel

General authorization values:

• Use Auto Authorization Interface (C14)

• Use Credit Card Encryption (I97)

• Require Credit Card Token (L40)

• Tokenization IJCT Job (L41)

• Preauthorize Backorders (D32)

• Authorize Only Merchandise for Drop Ship Picks (C92)

• Use Credit Card Vendor Response Entity Ship Via Dollar Limits (F94)

• Credit Card Authorization AVS Hold Exemption/Bypass (E61)

• Display Partial Credit Card Number in Logs (J16)

• $ Threshold for Automatic Authorization # Assignment (K36)

• Authorization Number for Authorizations Under $ Threshold (K37)

• Automatic Authorization for Authorizations Under Dollar Threshold Process

• Authorization Number for Authorizations Under $1.00 (I08)

• Automatic Authorization for Authorizations Under $1.00 Process

• Default Credit Card Authorization Number for Soft Declines (F93)

• Default Vendor Response for Automatic Authorizations (G10)

• Maximum Number of Retries on Credit Card Orders (E74)

• Authorization Service for Authorization Inquiries (K29)

Online authorization values:

• On-line Authorizations (B89)

• Online Auth Verification Only (I96)

• Authorize Full Amount During Order Entry (G99)

• Number of Times to Retry On Line Authorizations (B93)

• Online Auth Reserve $ Threshold (L74)

Deposit values:

• Send Data for Level II/III Discounting (I12)

• Void Unused CC Authorization After Initial Deposit (K05)

• Bank# for A/R Credit Card Deposits (C56)

• Deposit Service for Conditional Deposits (L13)

Use Auto Authorization Interface (C14)

Indicates if you will use the Auto Authorization interface to authorize credit card orders.

Yes/no field: Enter Y in this field if you will authorize credit card orders using the Auto Authorization interface. Auto Authorization is performed during Pick Slip Generation.

• If an order receives an approved authorization, the system prints a pick slip for the order.

• If an order receives a declined authorization, the system does not print a pick slip for the order.

Once the PICK_GEN job completes, the system prints 2 versions of the Credit Card Authorization Listing; 1 report displays all of the orders that received an approved authorization, 1 report displays all of the orders that received a declined authorization.

Enter N if you will authorize credit card orders manually or performing online credit card authorization. See System Operations Chapter 49: Performing Online Credit Card Authorizations for an overview on online authorization and required setup.

Use Credit Card Encryption (I97)

Defines whether the system encrypts the credit card number in the CWDirect database for this company, providing additional security for credit card data.

Important: This system control value is automatically updated during credit card encryption installation and setup.

Code field: Valid values are:

N or blank: Credit card encryption is not enabled. Credit card numbers in the CWDirect database are not encrypted.

Note: This setting is not recommended. Credit card data should be encrypted in the database.

Y: Credit card encryption is fully enabled. All credit card numbers in the CWDirect database are encrypted. If you use credit card tokenization, the encrypted number may be a token rather than the actual credit card number. You should only update this system control value to Y after you have completed ALL credit card encryption installation and setup.

C: Credit card encryption is partially enabled. All credit card numbers in non-order related files are encrypted. However, credit card numbers in order-related files are in the process of being encrypted. When you select to work with an order, the system must first determine if the credit card number on the order has already been encrypted. The system compares the selected order number against the CC Order Encryption file to determine if the credit card number on the order is encrypted.

• If the Use order level enc flag for the order is Y, the credit card number on the order has been encrypted.

• If the Use order level enc flag for the order is N, the credit card number on the order has not been encrypted. The system will automatically encrypt the credit card number when you select to work with the credit card on the order.

• If the system cannot find the order number in this file, the system assumes the order is a new order and encrypts the credit card number in the CWDirect database.

See Credit Card Encryption Installation and Setup in the CWDirect Credit Card Encryption Reference for step-by-step instructions.

S: Credit card encryption has been enabled; however, a new encryption key has been generated and credit card numbers in order-related files are in the process of being encrypted with the new encryption key. When you select to work with an order, the system must first determine if the credit card number on the order has already been encrypted with the new encryption key. The system compares the selected order number against the CC Order Encryption file to determine if the credit card number on the order is encrypted.

• If the Use order level enc flag for the order is Y, the credit card number on the order has been encrypted with the new encryption key.

• If the Use order level enc flag for the order is N, the credit card number on the order has not been encrypted with the new encryption key. The system will automatically encrypt the credit card number using the new encryption key as you select to work with the credit card on the order.

• If the system cannot find the order number in this file, the system assumes the order is a new order and encrypts the credit card number in the CWDirect database with the new encryption key.

See Credit Card Encryption Key Switch in the CWDirect Credit Card Encryption Reference for step-by-step instructions.

Warning window: The system displays a warning window if you change this system control value from blank or N to C, Y, or S and vice versa.

WARNING Before changing this SCV make sure that you have completed the setup and run the required conversions. Press F9 to accept this change. F3=Exit F9=Accept F12=Cancel

• If you have not performed the required credit card encryption installation and setup, press F3 or F12 to exit the window without updating this system control value. See Credit Card Encryption Installation and Setup in the CWDirect Credit Card Encryption Reference for more information on the steps you must perform in order to enable credit card encryption.

• If you have performed the required credit card encryption installation and setup, press F9 to update this system control value.

Additional credit card security: Regardless of the setting of this system control value, to further secure credit card data:

• Use credit card tokenization to replace the credit card number in the CWDirect database with a token provided by the authorization service.

• You can set up a credit card number format to control which digits of the credit card number are masked on CWDirect screens and reports using a special character, such as an asterisk (*). See Credit Card Number Format for an overview.

• The system writes a record to the Credit Card Audit file (MSCCAU) whenever a user with authority to view credit card numbers displays a screen or window that includes the credit card number field, or prints a report that might include any credit card numbers.

Require Credit Card Token (L40)

When using credit card tokenization, defines whether the system will accept a credit card number that has not been replaced with a token.

Yes/No field: Enter Y in this field to require a token for credit card number. This ensures that credit card numbers are never stored in the CWDirect database and follows full PCI compliance and maximum security of sensitive data.

If the Credit Card Tokenization Process is unable to replace the card number with a token, the system:

• During interactive Order Entry/Maintenance, Customer Membership and Change Invoice Payment Method: displays the Tokenization Warning window, requiring you to enter a different form of payment.

• During web order processing: replaces the credit card number with the text TOKENIZATION FAILED and places the order in an error status with the reason Invalid Credit Card. You can correct the credit card payment method and resend the card for tokenization in batch order entry.

Enter N in or leave this field blank to allow the system to accept a credit card number that has not been replaced with a token.

Encryption: If you use Use Credit Card Encryption (I97), the system encrypts the number stored in the Credit card number field in the CWDirect database.

Note: If you change the setting of this system control value, you must stop and restart the ORDER_IN integration layer job before your change takes effect for orders received through the Generic Order Interface (Order API).

Tokenization IJCT Job (L41)

Defines the integration layer job used to transmit tokenization messages between CWDirect and the authorization service during the Credit Card Tokenization Process.

Code field: Enter the Process ID for the integration layer job used to transmit Register Token messages between CWDirect and the authorization service during the Credit Card Tokenization Process. The delivered job is CC_TOKEN.

About the CC_TOKEN job: The CC_TOKEN job is a delivered interactive job used to route the Register Token messages to the correct MQ queues and to identify how long to wait for a Register Token Response from the service bureau.

Note: You can define only one set of queues (outbound and inbound) for the CC_TOKEN job, which means you can only use a single service bureau to perform credit card tokenization.

Preauthorize Backorders (D32)

Defines whether you transmit orders that are completely backordered for credit card authorization along with orders that are shipping. This helps you to spot fraudulent orders before you place a purchase order for these items.

Yes/no field: Enter Y in this field if you will send completely backordered orders up for initial credit card authorization; otherwise, enter N.

If you enter Y in this field, completely backordered orders that contain at least one credit card payment method are added to the Credit Card Authorization Backorder (CCATBO) file when you accept a new order in Order Entry (F9 or F19).

Note: Orders are added to this file from Order Entry only, not from Order Maintenance.

A single record is added to the Credit Card Authorization Backorder file for each order, regardless of the number of recipients (shipping addresses) on the order. The amount to authorize is $1.00.

The CCATBO file contains orders with:

• all backordered items, and

• at least one credit card payment method that uses a credit card authorization service bureau

• rejected authorizations for FDR (First Data Response). Rejected authorizations for this service are transmitted each time you transmit authorizations to FDR, regardless of whether there are reserved items on the order.

During Pick Slip Generation, when you select the option to generate picks (option 9), the system checks the orders in the Credit Card Authorization Backorder file to ensure that:

• the order was not canceled

• the items were not received and reserved through EBO_ASYNC (Evaluate Backorder ASYNC). This is a background processing job that matches newly received inventory to backorders, based on order date and priority.

If backordered items were reserved, the system deletes the record from the CCATBO (Credit Card Authorization Backorder) file and adds it to the CCAT00 (Credit Card Authorization) file. However, if the order remains completely backordered, the CCATBO file is copied to the CCAT00 file and is transmitted for initial authorization.

If the credit card charge is declined, the Order status and Order hold reason code fields are updated with the vendor response. Depending on the type of response, you might not place a purchase order with your vendor for these items. However, if the order receives authorization (the charge is approved), you might order the items from your vendor.

Authorize Only Merchandise for Drop Ship Picks (C92)

Defines how charges will be authorized for drop ship picks.

Yes/no field: Enter Y in this field to authorize only the charge for merchandise plus any tax on a drop ship pick slip or a drop ship purchase order.

Enter N to authorize only the charge for merchandise plus any tax on a drop ship pick slip or purchase order, unless a drop ship item is the only item left to be shipped on the order. Then, all charges will be sent for authorization, including: merchandise, freight, tax, handling (additional charges), etc.

This is a 1-position, optional field.

For more information: See Fulfillment Chapter 4: Introducing Pick Slip Generation.

Use Credit Card Vendor Response Entity Ship Via Dollar Limits (F94)

Defines whether the system performs an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order.

Yes/No field: Enter Y in this field if you wish the system to perform an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order.

You can use the ship via dollar limit to reduce the amount of credit card fraud. For example, a credit card may receive a vendor response of “all address matching”, but you may want to perform an additional check against the ship via assigned to the order and the dollar amount that requires authorization.

When you set up a ship via dollar limit, an order will go on hold if:

• the order passes AVS, but the ship to customer is different than the sold to customer, and

• the dollar amount that requires authorization is over the specified dollar limit to hold that you have set up for the ship via on the order.

In this situation, the system places the order on hold, using the hold reason code defined for the ship via dollar limit.

The system uses this information to determine if an order should go on hold due to a ship via dollar limit:

• the authorization service code

• the AVS response code from the authorization service

• the entity associated with the order

• the ship via on the order header

The system does not place an order on ship via dollar limit hold if:

• the order does not pass AVS, regardless of whether the ship to customer is different than the sold to customer, and

• the dollar amount that requires authorization is under the specified dollar limit to hold that has been set up for the ship via on the order.

In this situation, an order can pass AVS authorization even if the AVS response code causes the order to go on hold, if the order amount is under the specified dollar limit to hold.

Online credit card authorization: The system does not perform an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order when you are performing online credit card authorization. See System Operations Chapter 49: Performing Online Credit Card Authorizations for an overview and required setup.

Enter N or leave this field blank if you do not wish the system to perform an edit against a credit card vendor response to determine if the dollar amount for the credit card authorization exceeds the dollar limit defined for the ship via on the order.

For more information: See System Operations Chapter 44: Defining Vendor Response Codes.

Credit Card Authorization AVS Hold Exemption/Bypass (E61)

Defines whether to put an order on AVS hold a second time once it has been put on AVS hold and released.

Yes/no field: Enter Y in this field if you do not want to put an order on AVS (Address Verification Service) hold more than once.

An authorization service sends an AVS response if you need to verify that the customer's billing address is legitimate. For instance, the credit card might be authorized for the order, but there might be a discrepancy regarding part of the customer's address. To use the AVS feature, you should set the Address verification field for the authorization service to Y in the Work with Authorization Services menu option. You should also use this menu option to define each AVS response code.

When this system control value is set to Y, an order does not go on AVS hold twice if, for example, an order is authorized for a second shipment but receives the same AVS response the second time.

For more information: See System Operations Chapter 41: Defining Authorization Services (WASV).

Set this field to N or leave it blank if you want orders to be held each time the authorization sends an AVS response.

Display Partial Credit Card Number in Logs (J16)

Defines how the system masks the credit card data in the ECLG and MQJAVALOGS XML log files when credit card encryption is enabled.

If credit card encryption is enabled and an XML message contains a credit card number or card security number, CWDirect masks the credit card data in the ECLG and MQJAVALOGS XML log files, based on the setting of the Display Partial Credit Card Number in Logs (J16) system control value.

Yes/No field:

• Enter Y inthe Display Partial Credit Card Number in Logs (J16) system control value in any company to have the system include the last four digits of the credit card number in the logs; for example ************1234. If the credit card number is 4 digits or less, the entire credit card number is written as ****.

• Enter N or leave the Display Partial Credit Card Number in Logs (J16) system control value blank in every company to have the system replace the credit card number in the logs with the word REMOVEDBYLOGGER.

Note:

• As long as one CWDirect company has the Use Credit Card Encryption (I97) system control value set to Y, C, or S CWDirect masks the credit card number and card security value for every CWDirect company that is located in the same environment.

• If you use credit card tokenization, the credit card number in the logs may be a token rather than the actual credit card number.

• The credit card number and card security value are unencrypted in the actual XML message until the message is transmitted to the external system. To ensure security of the credit card data during data transmission to and from CWDirect, you should configure a secure socket over your MQ queues.

$ Threshold for Automatic Authorization # Assignment (K36)

Defines the dollar threshold the system uses to determine when to automatically assign the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to a credit card payment.

Dollar amount: Enter the dollar amount the system uses to determine when to automatically assign the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to a credit card payment. Note: The dollar amount is an 11 position field with 2 decimal places.

The system automatically authorizes the credit card payment if the dollar amount requiring authorization is less than the amount defined in this system control value. The system assigns the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card payment.

Leave this field blank and complete the Authorization Number for Authorizations Under $1.00 (I08) system control value if you want the system to automatically apply an authorization number to credit cards that require authorization for less than $1.00. See the Authorization Number for Authorizations Under $1.00 (I08) system control value for more information.

Leave this field blank and the Authorization Number for Authorizations Under $1.00 (I08) system control value blank if you wish to always send credit cards that require authorization to the service bureau, regardless of the amount that requires authorization.

For more information: See Automatic Authorization for Authorizations Under Dollar Threshold Process for more information.

Authorization Number for Authorizations Under $ Threshold (K37)

Defines the authorization number the system automatically applies to credit cards that require authorizations that are below the dollar threshold defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value.

Code field: Enter the authorization number the system automatically applies to credit cards that require authorization for an amount that is less than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value.

Note: The authorization number in this system control value applies to all service bureaus you define in Work with Authorizations (WASV).

Automatic Authorization for Authorizations Under Dollar Threshold Process

When you perform credit card authorization (either batch authorization during pick slip generation or online authorization during order entry), the system determines if the authorization amount qualifies for automatic authorization.

1.

If an authorization number is defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value, the system does not send credit cards that require authorization for a dollar amount that is less than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value to the service bureau. Instead, the system automatically applies the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card. • The authorization number updates the Authorization number in the Authorization History file. • The Vendor response, Vendor response 2, and AVS response fields in the Authorization History file remain blank. • The CW (awaiting credit card authorization hold) is removed from the Hold reason field in the Order Payment Method file for the credit card, allowing the system to generate a pick slip.

2.

If the amount that requires authorization is equal to or greater than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value, the system: • during online authorization: evaluates the Online Auth Reserve $ Threshold (L74) system control value to determine whether to send the credit card to the service bureau for authorization. • during batch authorization: sends the credit card to the service bureau for authorization, regardless of the amount that requires authorization.

Deposits: When you send the credit card for deposit processing, the service bureau may decline the deposit since the original authorization was forced and not sent to the service bureau for authorization. To avoid a declined deposit:

• If the forced authorization is the only authorization associated with the order or the forced authorization amount matches the amount charged on the order, the system uses the forced authorization number for deposits.

• If the forced authorization is not the only authorization associated with the order, the system looks at the other authorization associated with the order and uses the other authorization number since this number was received from the service bureau.

Pay type dollar limits: You can set up Entity pay type dollar limits for a vendor response for each entity in your company. You can use the pay type dollar limit to force authorizations that have been declined when the dollar amount that requires authorization is greater than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value but less than the pay type dollar limit you have set up for the credit card pay type on the order. In this situation, the system assigns the authorization number defined in the Default Credit Card Authorization Number for Soft Declines (F93) system control value to the credit card payment. Note: If you are performing online credit card authorization, the system does not validate vendor response codes at the entity level. See Entity pay type dollar limits for an overview and examples.

Leave this field blank and complete the Authorization Number for Authorizations Under $1.00 (I08) system control value if you want the system to automatically apply an authorization number to credit cards that require authorization for less than $1.00. See the Authorization Number for Authorizations Under $1.00 (I08) system control value for more information.

Leave this field blank and the Authorization Number for Authorizations Under $1.00 (I08) system control value blank if you do not want the system to automatically apply an authorization number to the credit card, based on the amount requiring authorization.

Authorization Number for Authorizations Under $1.00 (I08)

Defines the authorization number the system automatically applies to credit cards that require authorizations that are under one dollar.

Code field: Enter the authorization number you wish the system to automatically apply to credit cards that require authorization for less than one dollar.

Automatic Authorization for Authorizations Under Dollar Threshold: If the $ Threshold for Automatic Authorization # Assignment (K36) and Authorization Number for Authorizations Under $ Threshold (K37) system control values are populated, the system does not look at the Authorization Number for Authorizations Under $1.00 (I08) system control value and instead, applies the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card if the amount that requires authorization is less than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value. See Automatic Authorization for Authorizations Under Dollar Threshold Process for more information.

Automatic Authorization for Authorizations Under $1.00 Process

When you perform credit card authorization (either batch authorization during pick slip generation or on-line authorization during order entry), the system determines if an authorization number is defined in the Authorization Number for Authorizations Under $1.00 system control value.

1.

If an authorization number is defined in the Authorization Number for Authorizations Under $1.00 system control value, the system does not send credit cards that require authorization for less than $1.00 to the service bureau. Instead, the system automatically applies the authorization number defined in this system control value to the credit card. • The authorization number updates the Authorization number in the Authorization History file. • The Vendor response, Vendor response 2, and AVS response fields in the Authorization History file remain blank. • The CW (awaiting credit card authorization hold) is removed from the Hold reason field in the Order Payment Method file for the credit card, allowing the system to generate a pick slip.

2.

If an authorization number is not defined in the Authorization Number for Authorizations Under $1.00 system control value, the system: • during online authorization: evaluates the Online Auth Reserve $ Threshold (L74) system control value to determine whether to send the credit card to the service bureau for authorization. • during batch authorization: sends the credit card to the service bureau for authorization, regardless of the amount that requires authorization.

Note: The authorization number in this system control value applies to all service bureaus you define in Work with Authorizations.

Deposits: When you send the credit card for deposit processing, the service bureau may decline the deposit since the original authorization was forced and not sent to the service bureau for authorization. To avoid a declined deposit:

• If the forced authorization is the only authorization associated with the order or the forced authorization amount matches the amount charged on the order, the system uses the forced authorization number for deposits.

• If the forced authorization is not the only authorization associated with the order, the system looks at the other authorization associated with the order and uses the other authorization number since this number was received from the service bureau.

Pay type dollar limits: You can set up Entity pay type dollar limits for a vendor response for each entity in your company. You can use the pay type dollar limit to force authorizations that have been declined when the dollar amount that requires authorization is greater than $1.00 but is less than the pay type dollar limit you have set up for the credit card pay type on the order. In this situation, the system assigns the authorization number defined in the Default Credit Card Authorization Number for Soft Declines (F93) system control value to the credit card payment. Note: If you are performing online credit card authorization, the system does not validate vendor response codes at the entity level. See Entity pay type dollar limits for an overview and examples.

Leave this field blank if you wish to always send credit cards that require authorization to the service bureau, regardless of the amount that requires authorization.

Default Credit Card Authorization Number for Soft Declines (F93)

Defines the credit card authorization number the system defaults when a credit card authorization is declined but is under a specified dollar amount.

Code field: Enter the credit card authorization number you wish the system to default when a credit card authorization is declined but is under a specified dollar amount.

You can use the pay type dollar limit defined for a vendor response code to force authorizations that have been declined. For example, if a credit card received a vendor response of “credit card exceeds limit,” you may want to force the authorization through anyway if the dollar amount that requires authorization is less than $50.00.

If you set up a pay type dollar limit for a vendor response code, the order receives a forced authorization if:

• The credit card on the order is declined, and

• If the $ Threshold for Automatic Authorization # Assignment (K36) and Authorization Number for Authorizations Under $ Threshold (K37) system control values are populated, the dollar amount that requires authorization is greater than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value and is less than the pay type dollar limit that you have set up for the credit card pay type on the order.

• If the $ Threshold for Automatic Authorization # Assignment (K36) and Authorization Number for Authorizations Under $ Threshold (K37) system control values are not populated, the dollar amount that requires authorization is greater than $1.00 and is less than the pay type dollar limit that you have set up for the credit card pay type on the order.

In this situation, the order receives a forced authorization, and the system defaults the credit card authorization number defined in the Default Credit Card Authorization Number for Soft Declines (F93) system control value to the Authorization number field on the Authorization History record. The system processes the authorization through CWDirect, as if the number that defaulted from this system control value was an actual authorization number. The order will be processed through pick slip generation and the system will produce pick slips for the order. The system also writes an order transaction history message indicating the authorization was forced.

Note: The system may still place the order on hold if the order does not pass AVS authorization.

An error message displays if you try to enter an authorization number that is greater than 6 characters:

Only Six Bytes Allowed for Default CC Auth Code.

Leave this field blank if you do not wish to default a credit card authorization number when a credit card authorization is declined but is under a specified dollar amount.

Online credit card authorization: The system does not default the credit card authorization number you define here when a credit card authorization is declined but is under a specified dollar amount if you are performing online credit card authorization. See Performing Online Credit Card Authorizations for an overview and required setup.

If you do not define a credit card authorization number in this field, the order is placed on hold, using the vendor response hold reason code. If the hold reason code for the vendor response is blank, or a hold reason code has not been defined for the vendor response, the order is not placed on hold and is processed through pick slip generation.

For more information: See System Operations Chapter 44: Defining Vendor Response Codes.

Default Vendor Response for Automatic Authorizations (G10)

Defines the vendor response code to use for authorizations that you approve without receiving a response from the authorization service.

Code field: Enter the code to use for authorizations that you approve without receiving a response from the authorization service. You might use this automatic authorization process if you are expecting a substantial delay before you receive the authorizations from your service bureau, and you consider the likelihood of receiving declined authorizations to be low.

When is automatic authorization possible? You can approve authorizations in this way only if all three of these assumptions are true:

• this system control value is set to a valid response code for the authorization service

• the Immediate response field for the authorization service is set to N

• you have the proper authority, as controlled by the Continue Authorization without Receipt (A90) secured feature

Process overview: You can choose the automatic authorization option during pick slip generation when the PICK_GEN job is in message wait status, assuming all three of the assumptions listed are true. When you enter 7 next to the job at the Work with Submitted Jobs screen, the system displays a message such as:

Message . . . . : Waiting to receive auths from DMGT(C R A).

Authorizations have been sent to DMGT. Press R to reconnect and receive the

authorization responses, C to cancel and not receive the responses, or A to

authorize without receipt.

 

If you enter a response of A to this message, the system processes automatic authorizations for each pick slip awaiting an authorization from this authorization service. This process involves updating each authorization record in the Credit Card Authorization Transaction file (CCAT00):

• set the status to *RCVD

• set the authorization response code to the code specified for this system control value

• set the authorization number to all 9's

• set the authorization date to the current date

The system then generates pick slips for each authorization approved in this way.

Note: You should not attempt to receive the actual authorization file from the authorization service after processing automatic authorizations using this procedure.

Otherwise, the system displays a message such as:

 

Message . . . . : Waiting to receive auths from TJ LITLE (C R)

Authorizations have been sent to TJ LITLE. Press R to reconnect and receive

the authorization responses, or C to cancel and not receive the responses.

 

Note that the “authorize without receipt” option is not provided.

For more information:

• setting up authorization services: System Operations Chapter 41: Defining Authorization Services (WASV)

• generating pick slips: Fulfillment Chapter 5: Working with Pick Slip Generation (WPSG)

Maximum Number of Retries on Credit Card Orders (E74)

Defines the maximum number of times to attempt authorization for a credit card order.

Number field: Enter the maximum number of authorization attempts to make for an order before flagging the order for cancellation.

When you define a response code for an authorization service, you can specify the number of times to attempt authorization for that response code only. For example, when setting up a response code that indicates credit card fraud, you might specify to cancel the order after one attempt; for insufficient credit limit, you might specify to cancel after several attempts. Use this system control value to define the maximum number of times to attempt authorization for all responses combined.

The order will be flagged for cancellation when the total number of responses is equal to the number you specify here. For example, if you set this field to 15, the order will be flagged for cancellation when the order receives its 15th decline.

The system uses the value in the System Control file if the # authorization attempts field for the response code is blank. For this reason, you can use the system control value as the default or global maximum for vendor response codes.

Note: If the value in the System Control file is lower than the number of attempts you define at the vendor response level, the system will flag the order for cancellation after the lower number of attempts.

Counter reset: If the order receives an approval and you make a shipment, the counter is reset to zero. For example, if:

• an order is declined five times

• an order is approved

• you make a partial shipment

• you receive a backordered item and submit the order for authorization again

In this situation, if the order is declined again this counts as decline number one, not decline number six.

Leave this field blank if you always want to use the limit defined at the vendor response level, or if you never want to flag orders for credit card cancellation automatically.

Online credit card authorizations: The system does not flag an order for cancellation when the total number of responses is equal to the number you specify here if you are using online authorization. See System Operations Chapter 49: Performing Online Credit Card Authorizations for an overview and required setup.

More about credit card cancellations: When an order is flagged for cancellation due to failed authorization, the system writes a record in the Backorder Cancellation Pending file (BOCANP). These records are flagged with a type of C, to distinguish them from orders flagged for cancellation due to backorder (type B).

To cancel these orders automatically, use the Work with Credit Card Cancellations menu option (fast path = WCCC). You can also set this function up as part of your periodic processing, using the program BOR0029.

Cancel reason code: The system cancels each order using the cancel reason code associated with the vendor response code. If the order was flagged for cancellation because it reached the maximum defined in the System Control file, the system uses the cancel reason code associated with the last vendor response received. If none of the responses received by the order was associated with a cancel reason, the system uses the Auto Soldout Cancel Reason (C20) system control value.

For more information:

• setting up authorization services: System Operations Chapter 41: Defining Authorization Services (WASV)

• processing credit card cancellations: Customer Service Chapter 78: Working with Credit Card Cancellations (WCCC)

Authorization Service for Authorization Inquiries (K29)

Defines the authorization service for which you perform an authorization inquiry against a credit card in order to receive a response for an online authorization transaction that did not complete during order entry so that the credit card does not have to go out for authorization during batch authorization.

Code field: Enter the code for the authorization service for which you perform an authorization inquiry against a credit card in order to receive a response for an online authorization transaction that did not complete during order entry so that the credit card does not have to go out for authorization during batch authorization.

You define authorization services in the Defining Authorization Services (WASV) menu option.

Leave this field blank if you do not wish to perform an authorization inquiry against a credit card before performing batch authorization during pick slip generation and drop ship processing.

When is authorization inquiry called? The system sends an authorization inquiry request to the service bureau before performing batch authorization against the credit card in the following situation:

• The Authorization service for the credit card pay type on the order matches the authorization service defined in the Authorization Service for Authorization Inquiries (K29) system control value, and

• The Online Auth Verification Only (I96) system control value is set to N or blank, and

• An authorization history record exists for the credit card pay type on the order that did not receive a response from the service bureau. The system considers an authorization history record open if an associated record exists in the Online Authorization file in a *SENT, *RDY or *RCVD status.

Note: Once an authorization inquiry is processed for an open online authorization, the system will not reprocess the online authorization transaction. If an approved response is not received for the authorization inquiry, the system will send the card out for batch authorization.

Declined authorization inquiry: If the service bureau returns a declined authorization response for the open authorization, the system:

• Updates the record in the Online Authorization file with the values in the response message.

• Updates the status of the integration layer process control record to CMP (Complete).

• Updates the authorization history record for the open authorization transaction. The system updates the Status of the authorization history record to D (Decline) and the Vendor response with the decline reason.

• Continues with batch authorization to authorize the shippable amount on the pick slip or drop ship order.

Approved authorization inquiry: If the service bureau returns an approved authorization response for the open authorization, the system:

• Updates the record in the Online Authorization file with the values in the response message.

• Updates the status of the integration layer process control record to CMP (Complete).

• Updates the authorization history record for the open authorization transaction. The system updates the Status of the authorization history record to A (Authorized) and the Vendor response with the approved reason.

• Determines if the authorized amount on the authorization history record covers the shippable amount on the pick slip or drop ship order.

• If the authorized amount covers the shippable amount, the system continues with regular processing and does not call batch authorization since an authorization is not needed.

• If the authorized amount does not cover the shippable amount, the system continues with batch authorization to authorize the shippable amount on the pick slip or drop ship order, minus the amount that has already been authorized.

For more information: See:

• Batch Authorization Inquiry Processing for more information on the batch authorization inquiry process.

• Authorization Request XML Message (CWAuthorizationRequest) for a layout of the authorization request message. The system uses this message to send the authorization inquiry request to the authorization service.

• Authorization Response XML Message (CWAuthorizationResponse) for a layout of the authorization response message. The system uses this message to receive the authorization inquiry response from the authorization service.

On-line Authorizations (B89)

Defines whether the system performs online credit card authorization during order entry.

Yes/no field: Enter Y in this field if you wish to perform online credit card authorization during order entry.

Online credit card authorization allows you to send and receive electronically the information required to authorize a credit card when the order is placed instead of when the pick slip is generated for the order.

The system performs online authorization when you press F9 to accept an order after determining if the order should go on hold.

When you perform online credit card authorization, the system:

1. Determines if the order is eligible for online authorization.

2. Determines the amount to authorize, based on the value defined in the Authorize Full Amount During Order Entry (G99) system control value.

3. Sends the authorization amount to the authorization service.

4. receives a response from the authorization service.

5. Displays the Select Authorization Response Option Window, based on the settings defined for the authorization response received. You can use this window to review the response received from the authorization service and any messages defined for the vendor response.

6. processes any end-of-order updates and sends the order to the Order Async.

7. creates a record in the Online Authorization file, based on the authorization response received.

8. creates a record in the Authorization History file, based on the authorization response received. You can review authorization history at the Display Authorization History Screen.

9. creates a record in the Void Authorization file, based on the authorization response received.

Note: If you do not receive an authorization response for the credit card payment method during order entry or you receive a declined authorization response, you can re-send the order for authorization during order maintenance at the Enter Payment Methods Screen, using the Performing Batch Authorization (SATH) menu option, or during pick slip generation if the Batch/online field for the authorization service contains a C (online and batch authorizations).

Performing Online Verification Only: If the Online Auth Verification Only (I96) system control value is set to Y, the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.

For more information: See System Operations Chapter 49: Performing Online Credit Card Authorizations for an overview on online credit card authorization and the required setup.

Enter N or leave this field blank if you wish to perform credit card authorization during pick slip generation. See Reviewing Authorizations.

Online Auth Verification Only (I96)

Defines whether the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.

Yes/No field: Enter Y in this field if you want the system to process online authorizations for $1.00 for the purpose of validating the card.

• During batch authorizations, the system processes the card for the shippable dollar amount and voids the online authorization for $1.00.

• During deposits, the system processes the deposit for the full authorization amount.

Note: In order to perform online authorization, the On-line Authorizations (B89) system control value must be set to Y. See Performing Online Credit Card Authorizations for an overview and required setup.

Orbital Gateway integration: If you are using the Chase Paymentech Orbital Gateway Integration:

• the system processes online verification authorizations for Visa, Mastercard, and Switch card for .00 instead of $1.00.

• for all other credit cards, the system processes online verification authorizations for .01 instead of $1.00.

What validation occurs during online authorization? In addition to authorizing the card for $1.00, the system may perform:

• address verification, to ensure that the billing address on the card is legitimate. See Address Verification Service (AVS) for an overview and required setup.

• card security identification, to verify that the card is present at the point of sale and to ensure that the card data from the transaction matches the data stored by the authorization service for that card. See Credit Card Security Service (CID, CVV2, CVC2) for an overview and required setup.

• card authentication, to help reduce fraud and charge back volume on card not present transactions by requiring an authentication code, indicating the cardholder is authorized to use the credit card. See Credit Card Authentication Service for an overview and required setup.

What about other card types? If the Online Auth Verification Only system control value is set to Y and an online authorization is processed for a card type other than a credit card, the system:

• Stored value card: Does not send stored value cards for online authorization. However, if this system control value is set to Y:

• You can still perform balance inquiry against a stored value card.

• You can send the stored value card for online authorization if a Bill Me Later pay type is also on the order.

• Bill Me Later: When you process an online authorization for an order containing a Bill Me Later pay type, the system always authorizes the pay types on the order for the full amount, regardless of the setting of the Authorize Full Amount During Order Entry (G99) system control value and Online Auth Verification Only (I96) system control value; see Performing Online Authorization for a Bill Me Later Order for more information.

• Debit (Switch) card: Sends the online authorization request to the service bureau for $1.00. The system will authorize the card during batch authorizations for the shippable dollar amount.

Cards requiring authorizations less than $1.00: If the credit card amount to authorize is less than $1.00 and you have defined an authorization number in the Authorization Number for Authorizations Under $1.00 (I08) system control value, the system does not send the card to the service bureau for authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $1.00 system control value to the card. If an authorization number is not defined in this system control value, the system processes an online authorization for $1.00.

What if a $1.00 authorization already exists? If the card already has an active, online authorization for $1.00, the system will not send an online authorization for the card again for $1.00. However, if the existing $1.00 authorization has expired, the system will re-send an online authorization for $1.00 to the service bureau.

What if multiple cards exist on the order? The system will send an online authorization for $1.00 for each card on the order.

Authorize Full Amount During Order Entry (G99): If the Authorize Full Amount During Order Entry (G99) system control value is set to N, the system will not process online authorizations for $1.00 for orders that only contain:

• orders lines with a future arrival date

• order lines in a held status

• order lines on backorder, canceled, closed, or sold out

• reserved order lines that are coordinate grouped with an order line on backorder, held or with a future arrival date

Backorders: If the Preauthorize Backorders (D32) system control value is set to Y, in addition to processing an online authorization for $1.00 (if the Authorize Full Amount During Order Entry (G99) system control value is set to Y), the system authorizes a completely backordered order for $1.00 during pick slip generation.

Deposits: When you submit deposits, the system processes the deposit for the full authorization amount.

The system updates the Deposit amount on the Display Authorization History Screen and Authorization History Details Window against the authorization that occurred during batch authorization. You can view the full deposit amount on the following screens:

• Display Deposit History Screen

• Display Deposit History Detail Screen

• Invoice Pay Summary Screen

• Display Invoice Pay Method Screen (Reviewing Deposit Information)

In addition, the system writes an order payment history message for the full deposit amount: Deposit confirmed $ 5.75.

Display Authorization History: The Display Authorization History screen displays the $1.00 authorization and any authorizations that occurred during batch authorization. The system voids the $1.00 authorization once the shippable dollar amount is authorized during batch authorization. During deposits, the system processes the deposit for the full authorization amount.

CSR0415 DISPLAY Display Authorization History 3/07/05 11:01:55 KAB Co Order # . . : 8090 Pay type . . : CAT 2 CC, C PAYMENTECH VISA Issue #: Start Date: 0 Credit card# : ************1443 Exp date: 905 Opt Sts Auth Amt Auth# Auth Dat Send Dat Deposit Amt Vnd Vnd AVS Rsp1 Rsp2 Rsp Type options, press Enter. 5=Display Details 8=Auth Reversals V 1.00 TST787 3/07/05 3/07/05 100 A 5.75 TST817 3/07/05 3/07/05 5.75 100 F2=Toggle Alternate Currency F3=Exit F12=Cancel

Enter N or leave this field blank if you want the system to process online authorizations for the amount eligible for authorization, based on the setting of the Authorize Full Amount During Order Entry (G99) system control value.

Example:	Online Auth Verification Only = Y	Online Auth Verification Only = N
online authorization	The system sends an online authorization request to the service bureau for $1.00.	The system sends an online authorization request to the service bureau for the full authorization amount or shippable amount, depending on the setting of the Authorize Full Amount During Order Entry (G99) system control value.
batch authorization	The system sends a batch authorization request to the service bureau for the shippable dollar amount on the order.	If the shippable dollar amount is already authorized, the system generates a pick slip and does not send an authorization request to the service bureau. Otherwise, a batch authorization is sent to the service bureau for the shippable dollar amount that requires authorization.
batch deposit	The system sends a deposit request to the service bureau for the full amount authorized on the order.

Authorize Full Amount During Order Entry (G99)

Defines whether the credit card payment method on the order is authorized for the entire dollar amount defined for the card or the shippable amount defined for the card when you perform online authorization during order entry.

Yes/No field: Enter Y in this field if you want to authorize the entire dollar amount defined for the credit card.

Enter N or leave this field blank if you want to authorize the dollar amount associated with what is shippable on the order, across all ship to customers.

Online credit card authorization allows you to send a credit card up for authorization at the time the order is placed instead of at the time the pick slip is generated for the order. The system performs online authorization when you press F9 to accept an order after determining if the order should go on hold.

Performing Online Verification Only: If the Online Auth Verification Only (I96) system control value is set to Y, the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.

In order to perform online credit card authorization, the On-line Authorizations (B89) system control value must be set to Y.

Bill Me Later Orders: When you process an online authorization for an order using a Bill Me Later pay type, the system always authorizes the pay types on the order for the full amount, regardless of the setting of the Authorize Full Amount During Order Entry (G99) system control value and Online Auth Verification Only (I96) system control value; see Performing Online Authorization for a Bill Me Later Order for more information.

For more information: Chapter 49: Performing Online Credit Card Authorizations provides an overview on online credit card authorization and explains the set up required to perform online credit card authorization.

This table explains the credit card amount the system sends for authorization based on the setting on this system control value and the payment methods assigned to the order.

Authorize full amount... Authorize full amount during order entry = Y	Authorize shippable amount... Authorize full amount during order entry = N
The system sends the entire dollar amount defined for the credit card for authorization. If the credit card is the only payment method... The amount to authorize is the order total. The order total is the sum of all charges on the order, including: merchandise, freight, additional freight, tax, handling, additional charges, GST and PST.	The system sends the dollar amount associated with what is shippable on the order, across all ship to customers, for authorization. If the credit card is the only payment method... This shippable dollar amount includes: • shippable merchandise amount, including drop ship items • tax associated with the shippable merchandise amount • total freight • total additional freight • total order level additional charges Note: The system sends the total freight and total additional freight for authorization, regardless of whether you are prorating freight charges (the Prorate Freight Charges (D39) system control value is set to Y).
If the credit card is the catch-all payment method... The amount to authorize is the remaining dollar amount not associated with another payment method on the order. The system subtracts the amount applied to any other payment methods from the order total.   order total - dollar amount associated with other payment methods = amount to authorize for this credit card	If the credit card is the catch-all payment method... The amount to authorize is the remaining shippable dollar amount not associated with another payment method on the order. The system subtracts the amount applied to any other payment methods from the shippable dollar amount.   shippable dollar amount - dollar amount associated with other payment methods = amount to authorize for this credit card
	Excluded from authorizations: • order lines with a future arrival date • order lines on backorder, canceled, closed, or sold out • reserved order lines that are coordinate grouped with an order line on backorder or with an order line with a future arrival date. • orders in a held status
Regardless of whether you are authorizing the full amount or the shippable amount... Included in authorizations: • express bill order lines • drop ship order lines • non-inventory order lines Deferred Billing If the credit card on the order is associated with a deferred pay plan, the system: • sends an authorization for $1.00 if the Authorize full amount field for the pay plan is set to N. • sends an authorization for the dollar amount available for authorization if the Authorize full amount field for the pay plan is set to Y. Installment Billing If the credit card on the order is associated with an installment pay plan, the system: • sends an authorization for the first installment amount if the Authorize full amount field for the pay plan is set to N. • sends an authorization for the dollar amount available for authorization if the Authorize full amount field for the pay plan is set to Y.
If more than one credit card is sent for authorization... The system sends for authorization the credit card defined with a dollar amount, then sends the catch-all credit card for authorization.

Number of Times to Retry On Line Authorizations (B93)

Defines the number of times an authorization is retried for a credit card order when using Immediate Authorization. This field is not currently implemented.

Online Auth Reserve $ Threshold (L74)

Defines the shippable dollar amount the system uses to determine whether to process an online authorization for the credit card payment on the order.

Enter the shippable dollar amount the system uses to determine whether to process an online authorization for the credit card payment on the order. Note: The dollar amount is an 11 position field with 2 decimal places.

Required setup: In order for the system to evaluate the Online Auth Reserve $ Threshold (L74) system control value:

• the order must be eligible for online authorization; see Performing Online Credit Card Authorizations.

• the Authorize Full Amount During Order Entry (G99) system control value must be set to N.

• the Online Auth Verification Only (I96) system control value must be set to N.

When does the system evaluate this system control value? The system evaluates this system control value:

• when you perform online authorization during order entry; see Performing Online Credit Card Authorizations during Order Entry.

• when you perform online authorization for a web order received through the Generic Order Interface (Order API); see Performing Online Credit Card Authorization on Web Orders.

The system does not evaluate this system control value during order maintenance.

Backorder under $ limit: Use this system control value in conjunction with the Backorder under $ limit option in Working with Pick Slip Generation (WPSG). This field allows you to define a dollar limit under which backorders should not print. If an order can only be partially shipped and the value is under the amount defined, the system won't print it. This is true only for partial shipments where there are still open lines on the order.

Online authorization reserve $ threshold process: When you perform online authorization, the system determines the amount requiring authorization.

1.	If the amount that requires authorization is less than the dollar amount in the $ Threshold for Automatic Authorization # Assignment (K36) system control value, the system does not send the credit card to the service bureau for online authorization and instead, automatically applies the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card. See the Authorization Number for Authorizations Under $ Threshold (K37) system control value for more information.
2.	If the $ Threshold for Automatic Authorization # Assignment (K36) system control value is blank and the amount that requires authorization is less than $1.00, the system does not send the credit card to the service bureau for online authorization and instead, automatically applies the authorization number defined in the Authorization Number for Authorizations Under $1.00 (I08) system control value to the credit card. See the Authorization Number for Authorizations Under $1.00 (I08) system control value for more information.
3.	If the amount that requires authorization is less than the dollar amount in the Online Auth Reserve $ Threshold (L74) system control value, the system determines the shippable amount on the order. • If part, but not all, of the order is shippable, the system does not send the credit card to the service bureau for online authorization. The system will send the credit card to the service bureau during batch authorization. • If the entire order is shippable, the system sends the credit card to the service bureau for online authorization.
4.	If the amount that requires authorization is equal to or greater than the dollar amount in the Online Auth Reserve $ Threshold (L74) system control value, the system sends the credit card to the service bureau for online authorization.

Order lines on hold or with a future arrival date: When determining which items on the order are shippable, the system bypasses order lines that are held or have a future arrival date; the system does not consider these lines on backorder. Example: An order has 2 order lines, each for $4.00. One order line is reserved and the other order line has a future arrival date. If the Online Auth Reserve $ Threshold (L74) system control value is $10.00, the system will send the order for online authorization for $4.00 even though the dollar amount that requires authorization is less than the dollar amount in the Online Auth Reserve $ Threshold (L74) system control value because the order line with the future arrival date is not considered on backorder.

Examples: The table below explains when the system processes an online authorization for the order, based on the settings of the $ Threshold for Automatic Authorization # Assignment (K36), Authorization Number for Authorizations Under $ Threshold (K37), Authorization Number for Authorizations Under $1.00 (I08), and Online Auth Reserve $ Threshold (L74) system control values.

K36	K37	I08	L74	Results
5.00	AK36	AI08	10.00	You enter an order eligible for online authorization. The amount that requires authorization is $8.00. The entire order is shippable. Results: The system performs online authorization against the credit card payment on the order since the amount requiring authorization is greater than the $ Threshold for Automatic Authorization # Assignment (K36). Even though the amount requiring authorization is less than the Online Auth Reserve $ Threshold (L74), because the entire order is shippable, the system performs online authorization against the credit card payment on the order.
5.00	AK36	AI08	10.00	You enter an order eligible for online authorization. The amount that requires authorization is $8.00. Part of the order is on backorder. Results: The system does not perform online authorization against the credit card payment on the order since the amount requiring authorization is less than the Online Auth Reserve $ Threshold (L74) and part of the order is not shippable.
5.00	AK36	AI08	10.00	You enter an order eligible for online authorization. The amount that requires authorization is $4.00. Results: The system does not perform online authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card payment on the order.
15.00	AK36		10.00	You enter an order eligible for online authorization. The amount that requires authorization is $8.00. Part of the order is on backorder. Results: The system does not perform online authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) system control value to the credit card payment on the order. Note: Even though the order meets the Online Auth Reserve $ Threshold (L74), the $ Threshold for Automatic Authorization # Assignment (K36) takes precedence.
		AI08	.99	You enter an order eligible for online authorization. The amount that requires authorization is $ .99. Part of the order is on backorder. Results: The system does not perform online authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $1.00 (I08) system control value to the credit card payment on the order. Note: Even though the order meets the Online Auth Reserve $ Threshold (L74), the Authorization Number for Authorizations Under $1.00 (I08) takes precedence.

Leave this field blank if you do not want the system to evaluate the shippable dollar amount on the order to determine if it should go out for online authorization. The system will still evaluate the $ Threshold for Automatic Authorization # Assignment (K36)and Authorization Number for Authorizations Under $1.00 (I08) system control values to determine whether to automatically assign an authorization number to the credit card.

Send Data for Level II/III Discounting (I12)

Defines whether the system sends level II and level III discounting information to Paymentech during credit card deposits.

Yes/No field: Enter Y in this field to have the system send level II and level III discounting information to Paymentech when you process credit card deposits.

Populating the Level II Bin Range file: The Level II Bin Range file (CCBINR) identifies those credit cards that are eligible for level II and level III discounting. When populating this file, make sure the number of digits defined for a level II bin range matches the number of digits in the credit cards you wish to discount. The system does not evaluate the leading digits of the credit card number against the level II bin range level. If the number of digits defined for the level II bin range does not match the number of digits defined for the credit card numbers, the credit cards are not eligible for level II or level III discounting.

The table below indicates the number of positions for the level II bin range, based on the type of credit card you wish discount.

For Credit Card:	Level II Bin Range must be:	Example
VISA	16 positions	Create a level II bin range where the beginning number and ending number in the range is 16 positions. For example, if the level II bin range is 4788250000000000 - 4788260000000000. • If the VISA credit card is a business card (the CC bin type business field is set to B) or corporate card (the CC bin type corporate field is set to C) that falls within this range, it will receive the level II discount. • If the VISA credit card is a purchase card (the CC bin type purchase field is set to P) or fleet card (the CC bin type fleet field is set to F) that falls within this range, it will receive the level II and level III discount.
MasterCard	16 positions	Create a level II bin range where the beginning number and ending number in the range is 16 positions. For example, if the level II bin range is 553150000000000 - 553160000000000. Any MasterCard credit card that falls within this range will receive the level II and III discount.
American Express	15 positions	Create a level II bin range where the beginning number and ending number in the range is 16 positions. For example, if the level II bin range is 34333000000000 - 34334000000000. Any American Express credit card that falls within this range, will receive the level II discount.

Note: Level III discounting with Paymentech is supported with the CWIntegrate version 3.0 Paymentech site.

Credit card encryption: If you use credit card encryption, the credit card numbers in the Level II Bin Range file are not encrypted because the credit card information comes from an outside system.

Leased line or dial up/modem connection: For Paymentech Batch Processing using a leased line or dial up/modem: the system sends level II discounting information in the Transaction File Product Record: Procurement Level 2. Additionally, if the method of payment in the Transaction File Detail Record is AX (American Express), the system sends the Transaction File Address Record to Paymentech.

Integrate connection: For Paymentech Batch Processing using CWIntegrate, the system sends level II and level III discounting information in the discountQualified XML tag in the Deposit Request XML Message (CWDepositRequest) sent to Paymentech.

Valid values are:

• LV2 = The deposit is eligible for level II discounting and the system includes the Paymentech Product record in the request.

• YES = The deposit is eligible for level II and III discounting and the system includes the Paymentech Product record in the request. In addition:

• For VISA cards, the system includes the Paymentech Visa Level III Order record and Visa Level III Line 1 Line 2 record.

• For MasterCard cards, the system includes the MCDC Level III Order record and MCDC Level III Line 1 Line 2 record.

• NO = The deposit is not eligible for level II and III discounting and the system does not include the Paymentech Product Extension record in the request.

Sending discounting information to Paymentech: When you process deposits, the system sends level II and level III discounting information to Paymentech if:

• the authorization service code is PMT (Paymentech).

• the action code is:

• B: conditional deposit

• D: deposit

• R: refund

• the method of payment is:

• MC: Mastercard

• VI: Visa (Note: If the card type is a business or corporate card, the system sends level II discounting information only; if the card type is a purchase card, the system sends both level II and level III discounting information)

• AX: American Express

• the credit card number falls within a range of credit card numbers in the Level II Bin Range file. The Level II Bin Range file identifies those credit cards that are eligible for level II and level III discounting. It is your responsibility to populate this file with data from Paymentech.

Enter N or leave this field blank if you do not want the system to send level II and III discounting information to Paymentech when you process credit card deposits.

For more information:

• Processing Auto Deposits (SDEP)

• Paymentech Processing

Void Unused CC Authorization After Initial Deposit (K05)

Defines whether the system automatically voids a partially deposited credit card authorization.

Yes/No field: Enter Y in this field if you wish the system to automatically void the remaining balance against a credit card authorization that has been partially deposited.

If there are multiple authorizations for the order, the system will not void the other authorizations.

Example: Void Unused CC Authorization After Initial Deposit (K05) is set to Y.

During order entry, you process an online authorization for an order for $50.00. When you review Authorization History for the order: • Status = A (Authorized) • Amount submitted = $50.00 • Amount available = $50.00

During order maintenance, you cancel an item on the order. The order total reduces to $40.00. You ship and confirm the order. When you review Authorization History for the order: • Status = A (Authorized) • Amount submitted = $50.00 • Amount available = $10.00 • Amount deposited = $40.00

When you submit deposits, the deposit amount is $40.00. Because the Void Unused CC Authorization After Initial Deposit (K05) system control value is set to Y and the deposit amount ($40.00) is less than the authorization amount ($50.00), the system voids the remaining authorization amount ($10.00). When you review Authorization History for the order: • Status = V (Voided) • Amount submitted = $50.00 • Amount available = .00 • Amount deposited = $40.00

Enter N or leave this field blank if you want the system to retain a credit card authorization after it has been partially deposited.

Example: Void Unused CC Authorization After Initial Deposit (K05) is set to N.

During order entry, you process an online authorization for an order for $50.00. When you review Authorization History for the order: • Status = A (Authorized) • Amount submitted = $50.00 • Amount available = $50.00

During order maintenance, you cancel an item on the order. The order total reduces to $40.00. You ship and confirm the order. When you review Authorization History for the order: • Status = A (Authorized) • Amount submitted = $50.00 • Amount available = $10.00 • Amount deposited = $40.00

When you submit deposits, the deposit amount is $40.00. Because the Because the Void Unused CC Authorization After Initial Deposit (K05) system control value is set to N and deposit amount ($40.00) is less than the authorization amount ($50.00), the system retains the remaining authorization amount ($10.00). When you review Authorization History for the order: • Status = A (Authorized) • Amount submitted = $50.00 • Amount available = $10.00 • Amount deposited = $40.00

Bank# for A/R Credit Card Deposits (C56)

Defines the bank to use for posting credit card deposits and direct bank disbursements.

Code field: Enter the number identifying the bank to use when posting credit card deposits to the General Ledger Interface file. The system debits the A/R cash G/L number for this bank when you process credit card deposits, and credits this account number when you process credit card credits.

Similarly, the system debits the A/R cash G/L number when you process direct bank disbursements, and credits the account number when you process direct bank refunds.

Bank codes are defined in and validated against the Bank file. See Working with Banks (WBNK) for more information. Also, see:

• Processing Deposits

• Processing Direct Bank Disbursements/Electronic Checks

Deposit Service for Conditional Deposits (L13)

Defines the deposit service that sends deposits as Conditional (transaction type Conditional, action code B) in the following situations:

• subsequent deposit transactions are made against the same order number and authorization code.

• the deposit amount is greater than the available authorization amount.

Code field: Enter the deposit service that sends deposits as Conditional (transaction type Conditional, action code B) when subsequent deposit transactions are made against the same order number and authorization code or the deposit amount is greater than the available authorization amount.

Leave this field blank to have the system send deposits as Regular (transaction type Purchase action code D) when subsequent deposit transactions are made against the same order number and authorization code or the deposit amount is greater than the available authorization amount.

Example 1:	Deposit Service for Conditional Deposits (L13) = SVS
	An order contains three order lines: item A for 20.00, item B for 50.00 and item C for 30.00.
	You process an online authorization for the order and receive an approved authorization for 100.00: • Authorization status = Approved • Amount authorized = 100.00 • Authorization number = 374
	You generate a pick slip for item A. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Purchase • Deposit amount = 20.00 • Authorization number = 374 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 20.00 • Authorization number = 374
	You generate a pick slip for item B. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Conditional • Deposit amount = 50.00 • Authorization number = 374 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 70.00 • Authorization number = 374
	You generate a pick slip for item C. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Conditional • Deposit amount = 30.00 • Authorization number = 374 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 100.00 • Authorization number = 374

Example 2:	Deposit Service for Conditional Deposits (L13) = blank
	An order contains three order lines: item A for 20.00, item B for 50.00 and item C for 30.00.
	You process an online authorization for the order and receive an approved authorization for 100.00: • Authorization status = Approved • Amount authorized = 100.00 • Authorization number = 254
	You generate a pick slip for item A. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Purchase • Deposit amount = 20.00 • Authorization number = 254 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 20.00 • Authorization number = 254
	You generate a pick slip for item B. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Purchase • Deposit amount = 50.00 • Authorization number = 254 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 70.00 • Authorization number = 254
	You generate a pick slip for item C. You confirm and bill the shipment. You submit deposits for the order: • Transaction type = Purchase • Deposit amount = 30.00 • Authorization number = 254 The system updates authorization history: • Authorization status = Approved • Amount authorized = 100.00 • Amount deposited = 100.00 • Authorization number = 254

Preload Deposits (L78)

Purpose: Use this screen to define whether billing or deposits creates records in the CC Deposit Transaction file and CC Deposit History file, based on the records in the Invoice Payment Method file.

Note: The system creates a record in the CC Deposit Transaction file only for pay types that have a deposit service defined.

MSR0052 CHANGE Change System Control Value 12/02/13 13:43:07 Description . : Preload Deposits Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want billing to create records in the CC Deposit Transaction file and CC Deposit History file immediately after creating records in the Invoice Payment Method file.

In addition:

• If you use the Chase Paymentech Orbital Gateway Integration, the system sends the deposit transaction to the service bureau during billing. You still need to use Processing Auto Deposits (SDEP) to process credit deposits and perform batch deposit updates. Also, you will need to use the Resubmitting Rejected Deposits (SRDP) menu option to resubmit any deposits that were not completely processed during billing and deposits.

• For all other service bureaus, the system sends the deposit transaction to the service bureau when you submit deposits using the Processing Auto Deposits (SDEP) menu option.

Note:

• The system does not perform preload deposit processing if you define a deposit service in the Deposit Service for Conditional Deposits (L13) system control value. In this situation, the system uses the regular deposit process.

• If you select the Preload Deposits (L78) system control value, you cannot use Consolidated Invoice (B49).

• If you select the Preload Deposits (L78) system control value, the Purchases transactions to generate and Purchases amount to generate fields on the Auto Deposit Screen (Send or Receive Deposits) are display only.

Leave this field blank if you want deposits (SDEP) to create records in the CC Deposit Transaction file and CC Deposit History file prior to sending out the deposit transactions.

CC Deposit Transaction Table

Preload Deposits (L78) Selected	Preload Deposits (L78) Unselected
Chase Paymentech Orbital Gateway Service Bureau During billing: • the system sends the debit deposit transaction to the service bureau. • When an approved response is received, the system updates the Status of the CC Deposit Transaction record to *RCVD, and the Vendor response 1, Vendor response 2, and Authorization code based on the response received from the service bureau. During deposits: • The system processes any credit deposit transactions. • The system processes batch deposit updates for any credit deposit transactions and any debit deposit transactions that were sent to the service bureau during billing. • Once all updates are complete, the system deletes the CC Deposit Transaction record.	All Service Bureaus During billing: The system does not create a record in the CC Deposit Transaction file. During deposits: • The system sends the deposit transaction to the service bureau. • When an approved response is received, the system updates the Status of the CC Deposit Transaction record to *RCVD, and the Vendor response 1, Vendor response 2, and Authorization code based on the response received from the service bureau. • The system processes batch deposit updates. • Once all updates are complete, the system deletes the CC Deposit Transaction record.
Any Other Service Bureau During billing: The Status is *RDY, indicating the deposit transaction is ready to be submitted for processing. During deposits: • The system sends the deposit transaction to the service bureau and processes batch deposit updates when a response is received. • Once all updates are complete, the system deletes the CC Deposit Transaction record.

CC Deposit History Table

Preload Deposits (L78) Selected	Preload Deposits (L78) Unselected
All Service Bureaus During billing: • Updates Deposit date with the billing transaction date. • Updates Deposit status to Net yet sent. During deposits: Updates Deposit status to C Confirmed.	All Service Bureaus The system does not create a record in the CC Deposit History file. During deposits: The system creates a record in the CC Deposit History file, based on the information in the Invoice Payment Method and CC Deposit Transaction files.

For more information: See Processing Auto Deposits (SDEP).

---

1. Amazon.com is a registered trademark of Amazon.com, Inc. or its subsidiaries in the United States and other countries.