Purpose: The Enterprise Direct Commerce section of the System Control file defines parameters that control:
• system information
• program names
• program information
Note: If you do not use the e-commerce interface, you do not need to complete the system control values in this section.
Set up application area: You may need to set up the application area of EDC and group of ALL for e-commerce values if you have upgraded from an older version of CWDirect.
For more information:
• general information on e-commerce: E-Commerce Interface
• e-commerce setup: System Operations E-Commerce Setup
Quick Reference of E-Commerce System Control Values
This table describes briefly each system control value for the e-commerce interface and lists the control code, 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: ________________________________
System Control Value |
Description |
Your Value |
Defines whether you process web-based orders through the e-commerce interface. |
Yes/No: |
|
Defines the on-hand quantity to trigger download of availability information to the web storefront or through the generic inventory download API. |
Quantity: |
|
Defines the number of the batch to assign to e-commerce orders that are in error. |
Number: |
|
Defines the default order type to assign to orders you receive through the e-commerce and the generic order interfaces. |
Code: |
|
Defines the amount of time, in minutes, to hold a suspended e-commerce order before rejecting it. |
Number: |
|
Defines the pay type code to use for gift certificates on orders you process through the web storefront. |
Code: |
|
Defines the program to use for generating acknowledgments for orders you receive through the web storefront or through the generic inventory download. |
System name: |
|
Defines the program to use for generating notifications of shipments for orders you receive through the web storefront. |
System name: |
|
Defines the message to send to the web storefront for order lines that are partially reserved and partially backordered or soldout. |
Code: |
|
Defines the job queue for e-commerce order processing. |
System name: |
|
Defines the library to use for the e-commerce data download. |
System name: |
|
Specifies the price override reason code to use for e-commerce orders. |
Code: |
|
Hold Reason for Failed E-Commerce Maintenance Transactions (H11) |
Specifies the hold reason code to assign to orders when a customer attempts, and fails, to maintain it from the web storefront. |
Code |
Specifies the program to use to create order maintenance confirmations to send to customers via email. |
System name: |
|
Specifies the add reason code, if any, to use when a customer adds a new line to an order from the web storefront. |
Code: |
|
Defines the salesrep number to default to e-commerce orders if the Require Salesrep Number in Order Entry/Order Maintenance (E87) system control value is set to Y. |
Code: |
|
Defines whether the system passes the warehouse code in which an item is reserved with the reserved quantity of that item to the web storefront. |
Yes/No |
|
Defines the default recipient type for alternate ship-to addresses for the web storefront. |
Code: |
|
Defines whether the New Order Response message sent from CWDirect to a web storefront includes the order ship to number for a single ship-to order. |
Yes/No |
|
Defines the order amount that will cause an e-commerce order to be placed on hold unconditionally. |
Dollar Amount: |
|
Defines the division to include when selecting source codes for B2B e-commerce downloads. |
Code: |
|
Defines the price table to select for B2B e-commerce downloads. |
Code: |
|
Defines whether an Order Status Response Message is generated, regardless of whether an order is found that matches the order status inquiry request. |
Yes/No: |
|
Defines whether CWDirect populates the e-commerce customer merge staging files when you run the customer sold to or customer bill to merge/purge program. |
Yes/No: |
|
Defines the method the system uses to download e-commerce item availability data. |
Code: |
|
Defines whether to perform the order edit interactively for orders you receive through the e-commerce interface or the generic order API. |
Yes/No: |
|
Specifies whether the e-commerce ORDER PAYMENT/ACCEPT process should send an order response message after processing payment information for an order. |
Yes/No: |
|
Defines whether the system includes prepaid (cash/check payment category 1) payment types in the e-commerce pay type extraction. |
Yes/No: |
|
Defines whether the system overrides the ship via on a remote order with the preferred ship via defined for the ship to customer’s SCF. |
Yes/No: |
|
Defines whether the complete ship to name and address information is included in the E-Commerce Order Status Response Message (CWStatusResponse). |
Yes/No: |
|
Write Promotional Information to the Order Response Message (J38) |
Defines whether the system includes the end of order discounts and promotions that have been applied to the order in the order response message. |
Yes/No: |
Hold Reason for Duplicate Items Found in Processing Remote Orders (J51) |
Indicates the hold reason code to use for orders you receive that include an item the customer has ordered recently. |
Code: |
Include Set Components in Order Status Response Message (J83) |
Indicates whether to include set components in the E-Commerce Order Status Response Message (CWStatusResponse). |
Yes/No: |
E-mail Shipment/Return Confirmation Notification Immediately (K07) |
Indicates whether to generate shipment and return confirmation emails as soon as the shipment or return bills |
Yes/No: |
Indicates whether the e-commerce offer extract should populate the EC Item Effective Date and EC SKU Effective Date files. |
Yes/No: |
Additional System Control Values Related to E-Commerce
System Control Value |
Description |
Define the SKU element descriptions to appear on the web storefront (if you use split SKUs). Note: These system control values are available on the Edit Split SKU Values screen, available by selecting the Split SKU Inventory (A26) system control value. |
|
Specifies the program used to create backorder notices to send to customers via email. |
|
Specifies the program used to create soldout notifications to send to customers via email. |
|
Determines the default Opt in/opt out setting to use when creating a new customer. This flag indicates the customer’s preferences regarding contact by email. |
|
Defines whether CWDirect sends an email confirmation when any order is accepted or maintained or only when a customer on the web storefront accepts or maintains an order. |
|
Defines whether CWDirect sends an email confirmation when any order or return is shipped or only when an e-commerce order or return is shipped. |
|
Defines the program name to generate email, rather than printed, return confirmations. |
Get Orders from E-Commerce (G35)
Purpose: Use this screen to indicate whether you will be processing orders through the e-commerce interface.
MSR0052 CHANGE Change System Control Value 5/07/99 13:06:57
Description . : Get Orders from E-Commerce
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you will be processing internet orders through the e-commerce interface.
The EC_CLEANUP job will not run unless this field is set to Y. This job rejects any orders that seem to have been abandoned by the customer (for example, if the customer simply closed the web browser window without completing the order). See Time Limit for Suspended E-Commerce Orders (G43) for more information on the EC_CLEANUP job.
Note: You need to have this value set to Y in order to complete the download of e-commerce data from CWDirect to the web storefront, as described in Downloading E-Commerce Static Files (ESTF) and Downloading B2B E-Commerce Static Files (BBED).
Enter N in this field or leave it blank if you will not be processing e-commerce orders or downloading data to the web storefront.
Quantity Available Threshold for Inventory Downloads (G36)
Purpose: Use this screen to define the quantity available that serves as a trigger for download of availability information for the web storefront or through the generic inventory download.
MSR0055 CHANGE Change System Control Value 10/09/03 11:29:23
Description . : Qty Available Threshold for Inventory Downloads.
Quantity . . . 20 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Quantity field: Enter the quantity to trigger the download of item availability information to the web storefront or through the generic inventory download. The web storefront download allows you to display an item’s availability status to web customers if your web storefront supports it, while the generic inventory download enables you to communicate inventory information to external systems, such as through Locate.
Note: This field is also included under the Generic Integration Values (I13) system control value as the Download Threshold Quantity.
Threshold hierarchy: You can also define a Avail threshold (item-level availability threshold) for an individual item, and/or a Availability threshold (item class-level) for an item class. The system determines which threshold to use for an item by checking the:
1. item threshold
2. if there is no item threshold, the threshold for the item class assigned to the item
3. if there is no item or item class threshold, the system control value setting
Example: An item’s threshold is 20; its item class threshold is 15; and the system control value is set to 25. The interactive availability download takes place based on the item-level threshold of 20.
Interactive download: An item or SKU’s available quantity is downloaded (web) or a trigger record created (generic inventory download):
• if an item or SKU’s available quantity is greater than or equal to this threshold, and then it falls below the threshold
Example: Available quantity for item AB100 is 21, and the web threshold is 20. You enter an order line for a quantity of 2, reducing the available quantity to 19.
• once an item or SKU’s available quantity is below the threshold, each time the available quantity is reduced until it is zero
Example: After entering the order line in the above example, you enter another line on a different order for a quantity of 4, reducing the available quantity from 19 to 15.
• if an item or SKU’s available quantity is below this threshold, and then it increases to the threshold quantity or more
Example: After entering the order line in the above example, you cancel an order for 5 units, bringing the available quantity for the item from 15 to 20.
If you leave this field blank, the system checks the item-level and item class-level thresholds as described above. If all of these thresholds are blank, the system will not automatically download item availability information.
Availability Threshold for the Web Storefront
Periodic function: In addition to the interactive download, you can use the ECAVAIL periodic function to download the current available quantity of every item and SKU for which you have downloaded information to your web storefront. You should set up this function to use the program name ECR0144 (see System Operations Working with Periodic Functions (WPER)). See E-Commerce Item Availability Processing for an overview.
Item availability download method: The E-Commerce Item Availability Download Method (I10) system control value defines the method (FILE, XML, or BOTH) the system uses to download e-commerce item availability data.
Availability Threshold for the Generic Inventory Download API
Generic inventory download: If the Create Generic Inventory Download Triggers (I32) system control value is set to Y, the system creates ITW trigger records in the IL Outbound Trigger file to determine which items to include in the download. The INV_DOWNLD process in Working with Integration Layer Processes (IJCT) then generates the Inventory Download XML Message (CWInventoryDownload) based on the trigger records. However, the system does not create a trigger record if the Include Non-Allocatable Warehouses (I34) is set to N, and none of the existing Item Warehouse records for an item/SKU are non-allocatable.
Interactive trigger creation: The system creates an ITW trigger whenever an item’s available quantity breeches the appropriate threshold, as described above.
Other ways to create inventory download triggers: You can also create ITW triggers for all eligible items through Generating Outbound Interface Triggers (GOIT) or through a periodic function. See Generic Inventory Download API for more information.
Default Batch for E-Commerce Orders in Error (G41)
Purpose: Use this screen to define the order batch number to assign to e-commerce orders that are in error.
MSR0054 CHANGE Change System Control Value 5/07/99 13:41:56
Description . : Default Batch for E-Commerce orders in error
Number . . . . 666
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Number field: Enter the order batch number to assign to e-commerce orders that are in error, so that you can use batch order entry to correct the errors.
Orders you receive through the e-commerce interface go through an edit process that is similar to phone order edit or the business-to-business order edit. Any orders that fail this edit are placed in error (E) status, and assigned to the batch number you specify here. Additionally, the ECOMM_ORDR job generates the Phone Errors Report, so you can review the errors on particular orders.
You should use batch order entry periodically to check whether any orders are in error, and to correct the errors.
The system removes the order batch number from the e-commerce order once the order has been accepted (no longer in a suspended or error status).
The order confirmation email is generated regardless of whether the order is in error.
Order transaction history: When you press F9 to accept an order that is part of the e-commerce order batch, the system writes an order transaction history message indicating the user that accepted the order. The system writes an order transaction history message each time a user accepts the order so that you can track the users that changed an order in the e-commerce order batch. You can review order transaction history messages on the Display Order History Screen.
An example of the order transaction history message the system creates when a user accepts an order that is part of the e-commerce order batch is displayed below. The system includes an amount regardless of whether the change updated the order total.
Date |
Type |
Transaction Note |
Amount |
User |
8/4/14 |
4 |
Batch order changed - Ecomm. |
20.75 |
SFLYE |
Purpose: Use this screen to define the order type to assign to orders you receive through the e-commerce and the generic order interfaces.
MSR0051 CHANGE Change System Control Value 5/07/99 13:46:07
Description . : E-Commerce order type
Code . . . . . R F M P T
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Code field: Enter the order type code to assign to orders you receive through the e-commerce interface and the generic order interface. You should not use this order type code for any other types of orders.
This field controls:
• generation of shipment and return notification emails; see Shipment Confirmation Program (G51) and Return Confirmation E-Mail Program (H53)
• whether the EC_CLEANUP job “rejects” orders that seem to have been abandoned by the customer (for example, if the customer simply closed the web browser window without completing the order); see Time Limit for Suspended E-Commerce Orders (G43)
You can also use the order type for tracking and reporting.
Reserving orders against a non-allocatable warehouse: If the Retail warehouse field for the e-commerce order type contains a non-allocatable warehouse and the Reserve from Non-Allocatable Warehouse (J25) system control value is set to Y, the system allows you to reserve inventory against the non-allocatable warehouse defined for the e-commerce order type. If the item is not in stock, the system backorders the item against the non-allocatable warehouse. However, if a warehouse override is defined for the remote order, the system uses the override warehouse instead of the warehouse defined for the e-commerce order type.
For more information: Order type codes are defined in and validated against the Order Type file. See Customer Service Establishing Order Types (WOTY). Also, see Generic Order Interface (Order API) and E-Commerce Setup.
Time Limit for Suspended E-Commerce Orders (G43)
Purpose: Use this screen to define the number of minutes to wait before rejecting a suspended e-commerce order due to inactivity.
MSR0054 CHANGE Change System Control Value 5/07/99 13:52:40
Description . : Time limit for suspended E-Commerce orders
Number . . . . 10
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Number field: Enter the number of minutes to wait before rejecting a suspended e-commerce order. The system waits this amount of time after the customer has selected to “check out” at the web storefront. The cleanup is necessary for cases when customers simply close the browser window or advance to another web page without completing the order.
The EC_CLEANUP job performs the cleanup and rejection. This cleanup occurs only if the Get Orders from E-Commerce (G35) system control value is set to Y, and only for the order type defined in the E-Commerce Order Type (G42) system control value.
Default Pay Type for Gift Certificates/Coupons (G48)
Purpose: Use this screen to indicate the pay type to assign to gift certificates or coupons on orders you process through the e-commerce interface.
MSR0054 CHANGE Change System Control Value 6/29/99 15:42:01
Description . : Default Pay Type for Gift Certificates/Coupons
Number . . . . 16
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 1
F3=Exit F12=Cancel |
Number field: Enter the number representing the pay type to use on orders you process through the e-commerce interface if the customer uses a gift certificate or a coupon, but there is no gc_type specified in the order message. The system will add this pay type to the order.
Important: The number you enter must represent a pay type with a payment category of 5 (coupon/credit). See Accounts Payable Working with Pay Types (WPAY).
Order Acknowledgement Program (G50)
Purpose: Use this screen to define the program to generate email acknowledgments for orders.
MSR0053 CHANGE Change System Control Value 2/29/04 15:41:22
Description . : Order acknowledgement program.
System name . . ECR0318 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
System name field: Enter the program name to use to generate order acknowledgment emails. There are several base programs, each of which is described below. Your confirmation email will vary if you use a different program.
Leave this field blank to email the standard U.S. order confirmation to the sold to customer when an order is placed.
Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for order notifications if the Use email API flag for the order confirmation 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.
Standard Order Confirmation Email Templates
Each of the programs described below generate an email using the entity-level template, if any, defined for the order confirmation (OC) template through the Working with Entities (WENT) menu option; if there is no template set up at the entity level, the program uses the company-level template set up through the Working with E-Mail Notification Templates (WEMT) menu option. If a template has not been defined at either level, CWDirect includes only the standard order information in the email.
Standard U.S. template (ECR0318): A sample of the standard order information is presented below.
From: To: Sent: Subject: |
GardenPets.com kbottger@commercialware.com Fri. 1/19/04 7:45 AM Order Confirmation |
Text you can define to print above the order information: |
This message is to confirm that your order has been processed successfully. Please contact us at www.gardenpets.com or call our toll free number 1-888-555-1212. |
standard order information: |
Order #: 5039 - 1 Order date: 1/17/04 Sold To: BOTTGER, KAREN A Ship To: MIRANDA, BERNADETTE T Order Process Date: 1/17/04 Merchandise: 12.00 Freight....: Add’l Frt..: 5.00 Tax........: .85 Total......: 17.85
1. TERRA COTTA POT (TC487) 1 @ $12.00 - In stock. 2. WATERING CAN (BU3857) 1 @ $10.00 - Backordered 05/01/04. |
Text you can define to print below the order information: |
Regards, Your friends at GardenPets. Visit us at gardenpets.com! |
Note: The previous standard message program (ECR0130) has been replaced with this new program.
Standard U.S. template with prepayment breakout (ECR0405): If a pre-paid payment method exists on the order (pay category 1 cash/check or 5 gift certificate/coupon), the email includes a breakdown of payment methods on the order, illustrating the amount that has already been paid and the remaining amount to charge. Breakdown of payment includes:
• Order total: the total order amount
• Cash/Check: the amount assigned to pay category 1 cash/check
• GC/Coupon: the amount assigned to pay category 5 gift certificate/coupon
• Amount to be charged to credit card: the amount assigned to pay category 2 credit card (if a credit card exists on the order, this total also includes the amount assigned to pay category 3 A/R and pay category 4 COD)
• Balance on Account: The amount overpaid on the order (if a credit card does not exist on the order, this total also includes the amount assigned to pay category 3 A/R and pay category 4 COD)
If there are no pre-paid payment methods on the order, the email does not include the breakdown of payments.
Order #: 5039 - 1 Order date: 1/17/04 Sold To: BOTTGER, KAREN A Ship To: MIRANDA, BERNADETTE T Order Process Date: 1/17/04 Merchandise: 12.00 Freight....: Add’l Frt..: 5.00 Tax........: .85 Total......: 17.85
1. TERRA COTTA POT (487) 1 @ $12.00 - In stock. 2. WATERING CAN (3857) 1 @ $10.00 - Backordered 05/01/04. |
Order Total 321.00 Cash/Check 11.00 GC/Coupon 25.00 Amount to be Charged to Credit Card 285.00 |
Standard U.S. template without expected ship date (ECR0419): Identical to the standard template (ECR0318), except that:
• the expected ship date is not included next to backordered items
• the SKU description is provided for each SKU’d item.
Order #: 10122 - 1 Order date: 6/16/04 Sold To: COMMERCIALWARE ATTN: KAPLAN, ELISE Z Ship To: COMMERCIALWARE ATTN: KAPLAN, ELISE Z Order Process Date: 6/16/04 Merchandise : 23.45 Freight . . . : 2.35 Add'l Frt . . : 2.34 Tax . . . . . : 2.35 Total . . : 30.49 1. DELUXE CLASSIC TOASTER () 1 @ $15.00 - In stock. 2. SOLID PREMIUM MILK CHOCOLATE B (/CHOC LRGE) 1 @ $8.45 - No longer available. 3. SOLID PREMIUM MILK CHOCOLATE B (/WHIT LRGE) 1 @ $8.45 - Backordered. 4. COMFORT-GRIP PEN (/BLUE) 1 @ $.00 - In stock. |
Standard U.K. template (ECR0420): Identical to the standard template without expected ship date (ECR0419), except that:
• the dollar signs are omitted
• the dates are in DD/MM/YY format
Order #: 10121 - 1 Order Date: 16/06/04 Sold To: COMMERCIALWARE ATTN: KAPLAN, ELISE Z Ship To: COMMERCIALWARE ATTN: KAPLAN, ELISE Z Order Process Date: 16/06/04 Merchandise : 23.45 Freight . . . : 2.35 Add'l Frt . . : 2.34 Tax . . . . . : 2.35 Total . . : 30.49 1. DELUXE CLASSIC TOASTER () 1 @15.00 - In stock. 2. SOLID PREMIUM MILK CHOCOLATE B (/CHOC LRGE) 1 @8.45 - No longer available. 3. SOLID PREMIUM MILK CHOCOLATE B (/WHIT LRGE) 1 @8.45 - Backordered. |
Standard D.E. template (ECR0421): Identical to the standard U.K. template, except that all of the standard text is in German,
Bestellnummer: 10120 - 1 Bestelldatum: 16/06/04 Rechnungsanschrift . : COMMERCIALWARE ATTN: KAPLAN, ELISE Z Lieferanschrift . . : COMMERCIALWARE ATTN: KAPLAN, ELISE Z Bestellung vom : 16/06/04 Warenwert . . . . . . . . : 23.45 Versandkosten . . . . . . : 2.35 Zusaetzliche Versandkosten : 2.34 Mehrwertsteuer . . . . . . : 2.35 Gesamtkosten . . . . . . . : 30.49 1. DELUXE CLASSIC TOASTER () 1 @15.00 - auf Lager. 2. SOLID PREMIUM MILK CHOCOLATE B (/CHOC LRGE) 1 @8.45 - ausverkauft 3. SOLID PREMIUM MILK CHOCOLATE B (/WHIT LRGE) 1 @8.45 - nicht mehr lieferbar |
Item Status and Soldout Items
Item status: The order confirmation email or Outbound Email XML Message (CWEmailOut) includes information on whether the item is reserved:
• In stock indicates that the item is reserved.
• Backordered 99/99/99 indicates that the item is backordered. The expected ship date is indicated, calculated by adding the order date to the FTC -- # of Days for Items without Expected Ship Date (C71) if there are no open purchase orders for the item.
• If the Assign Drop Ship Expected Ship Date (I59) system control value is set to Y, drop ship items are indicated by the Exp date, calculated as follows:
• CWCollaborate items (the item’s default vendor has the Drop ship output field set to C): the expected ship date = the current date + Drop Ship Lead Days (H36) + the Lead days for the vendor item
• other drop ship items: the expected ship date = the current date + FTC -- # of Days to Add for Drop Ships (C68) + the Lead days for the vendor item
Exclude soldout items from email: The Exclude soldouts on order confirmation field for the order type indicates if the system excludes soldout items from printing on the order confirmation email or being included in the Outbound Email XML Message (CWEmailOut). For example, you may wish to exclude soldout items when printing order confirmations for phone orders, but include soldout items when printing order confirmations for e-commerce orders.
• If this field is set to Y, the system does not include soldout items on the order confirmation email or the Outbound Email XML Message (CWEmailOut) for any orders of that order type. Note: If the soldout item is the only item on the order and you exclude soldout items from the order confirmation email or the Outbound Email XML Message (CWEmailOut), the system does not generate an email or message.
• If this field is set to N, the system includes soldout items on the order confirmation email or the Outbound Email XML Message (CWEmailOut) for all orders of that order type. The message No longer available displays next to the soldout item.
Note: The system excludes soldout items from the order confirmation email for the base order confirmation programs of ECR0318 or ECR0405.
Determining When to Email an Order Confirmation
The system generates an order confirmation or the Outbound Email XML Message (CWEmailOut) for e-commerce orders if:
• the order was received from the web storefront (that is, the order was created through the e-commerce order process in Working with E-Commerce Job Control (EJCT)),
• the customer’s Opt-in/out setting is O1 or O2 (see Determining the Opt-in/out Setting), and
• the customer has an Email address
The acknowledgment is generated even if the e-commerce order is in error (E) status, and must be corrected through batch order entry. See Default Batch for E-Commerce Orders in Error (G41).
If the order did not originate at the web storefront, the system generates an order confirmation email or the Outbound Email XML Message (CWEmailOut) if:
• the E-mail notification field for the order type is set to Y, and,
• the customer’s Opt-in/out setting is O1 or O2 (see Determining the Opt-in/out Setting), and
• the customer has an Email address; and,
• the E-Mail Order Confirmations for All Orders (H51) is set to Y, or
• the order type matches the E-Commerce Order Type (G42).
The system does not validate that the customer’s email address is valid.
Order history message: When it sends an order confirmation email or Outbound Email XML Message (CWEmailOut), CWDirect creates an order history message such as 1/17/02 L Ord Conf to kbottger@commercialware.com. You can review order history messages at the Display Order History Screen.
Email setup: See When Does the System Generate an Email Notification? for more information on the criteria required to generate an email.
Shipment Confirmation Program (G51)
Purpose: Use this screen to define the program to generate shipment confirmations for order shipments.
MSR0053 CHANGE Change System Control Value 6/29/99 15:40:52
Description . : Shipment Confirmation Program
System name . . ECR0135 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
System name field: Enter the program name to generate shipment confirmation emails for order shipments.
Base program: The base program is ECR0135. Your confirmation email will vary if you use a different program. ECR0135 generates an email using the template defined for the entity-level shipment confirmation (SC) template, if any, set up through the Working with Entities (WENT) menu option; if there is no template set up at the entity level, the program uses the company-level template set up through the Working with E-Mail Notification Templates (WEMT) menu option. If a template has not been defined at either level, CWDirect includes only the standard shipment information in the email.
Outbound email API: Any entry in this field indicates to generate a generic outbound XML message, rather than an actual email, for shipment notifications if the Use email API flag for the order shipment confirmation 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.
Shipment confirmation email with tracking number link: In order to enable customers to track their shipments, you can generate a shipment confirmation email that includes the shipment tracking number embedded in a link to the shipper’s web site. See Shipment Confirmation Email with Tracking Number Link for more information and configuration instructions.
To generate: CWDirect generates an email or Outbound Email XML Message (CWEmailOut) when you:
• generate e-commerce shipment confirmations using the Send Internet Order Ship Confirmations menu option; see System Operations Sending Internet Order Ship Confirmation (ESCF)
• execute the ECSHCNF periodic function; see System Operations Working with Periodic Functions (WPER)
Determining when to generate a shipment confirmation: The system generates an email shipment confirmation or Outbound Email XML Message (CWEmailOut) only if:
• the E-mail notification field for the order type is set to Y, and,
• the customer’s Opt-in/out setting is O1 or O2 (see Determining the Opt-in/out Setting), and,
• the customer has an Email address, and,
• the E-Mail Shipment Confirmations for All Orders (H52) is set to Y, or,
• the order type matches the E-Commerce Order Type (G42)
The system does not validate that the customer’s email address is valid.
E-Commerce orders: The system generates the acknowledgment even if the order is in error (E) status, and must be corrected through batch order entry. See Default Batch for E-Commerce Orders in Error (G41).
Order history message: When it generates a shipment confirmation email or Outbound Email XML Message (CWEmailOut), CWDirect creates an order history message such as 1/17/02 L Ship Conf to kbottger@commercialware.com.
Email setup: See When Does the System Generate an Email Notification? for more information on the criteria required to generate an email.
Sample shipment confirmation email: See Sample Shipment Confirmation Email for an example of a shipment confirmation email.
Sample outbound email XML message: See Sample Outbound Email XML Messages.
Return shipments: CWDirect uses the program name defined in the Return Confirmation E-Mail Program (H53) system control value for return shipments.
Gift acknowledgement? If the customer is eligible to receive a shipment confirmation email as described above, the system does not generate a printed gift acknowledgement for gift orders. See the Automatic Generation of Gift Acknowledgement (B92) for more information on when the system generates a gift acknowledgement.
Leave this field blank to email the standard shipment confirmation to the sold to customer when an order is shipped.
Shipment Confirmation Email with Tracking Number Link
You can enable customers to track shipments through the shipment confirmation email by embedding the tracking number in a link to the shipper’s web site. The system derives the tracking number from the Manifest Upload Audit (FLMUAU) file. You can also view the tracking number in order inquiry at the Display Order History Screen.
To configure:
Program name: Set the Shipment Confirmation Program (G51) system control value to ECR0497.
Note: This email program also uses the SKU description rather than the item description for each shipped order detail line.
User defined field definition: Use Setting Up User-Defined Fields (WUDF):
• Create a user-defined field link to the Ship Via file (the File code = VIA)
• Create several user-defined field detail records with:
• Field label = URL
• Type = T (text)
• Usage = I (input)
Note: The number of detail records required depends on the amount of information required by the shipper’s web site in order to link directly to its shipment tracking page. See below for examples.
Ship via: Use the User field option in Working with Ship Via Codes (WVIA) to enter the additional information required to link to the shipper’s web site, embedding the variable CWNUMBER in the place of the tracking number. Because each user-defined field is limited to 30 positions, enter the maximum of 30 characters in each line. The URL will be concatenated in the generated email with no spaces between the 30-character entries. For example, you might enter the following for a Federal Express ship via:
http://www.fedex.com/cgi-bin/t
racking?action=track&language=
english&cntry_code=us&initial=
x&tracknumbers=CWNUMBER
A shipment confirmation email for tracking number 1234567890 would then include the following link:
http://www.fedex.com/cgi-bin/tracking?action=track&language=english&cntry_code=us&initial=x&tracknumbers=1234567890
Similarly, you might enter the following for a UPS ship via:
http://wwwapps.ups.com/WebTrac
king/processInputRequest?HTMLV
ersion=5.0&sort_by=status&term
_warn=yes&tracknums_displayed=
5&TypeOfInquiryNumber=T&loc=en
_US&InquiryNumber1=CWNUMBER&Ag
reeToTermsAndConditions=yes
A shipment confirmation email for tracking number 987654321 would then include the following link:
http://wwwapps.ups.com/WebTracking/processInputRequest?HTMLVersion=5.0&sort_by=status&term_warn=yes&tracknums_displayed=5&TypeOfInquiryNumber=T&loc=en_US&InquiryNumber1=987654321&AgreeToTermsAndConditions=yes
Note:
• If Federal Express or UPS change the configuration or requirements of linking to their tracking information, it might be necessary to change the information included in the user defined fields for the ship via.
• It might be necessary to edit the information in the user-defined fields. For example, for ship vias outside of the United States, substitute the correct country code for us.
• If there are multiple shipments for an order on the same date and the Consolidated Invoice (B49) system control value is set to N, the system generates a separate shipment confirmation email for each shipment, each with its own tracking number link if you have configured the ship via to do so. Otherwise, if the Consolidated Invoice (B49) system control value is set to Y, the email includes a separate link for each shipment that takes place on the same date.
• The tracking number link is not automatically generated as part of the Outbound Email API; however, the outbound email message does include the tracking number, so you can include this information when producing the formatted email to the customer.
Status Message for E-Commerce Partial Reserved Lines (G52)
Purpose: Use this screen to define the status message to pass through the e-commerce interface for order lines that are partially reserved.
MSR0051 CHANGE Change System Control Value 6/29/99 15:40:12
Description . : Status Message for E-Commerce Partial Reserved lines
Code . . . . . BACKORDER RESERVED BACKORDER PARTIAL
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Code field: Enter the code representing the message to pass through the e-commerce interface when a customer orders an item that is partially reserved and partially backordered. Valid values are:
• BACKORDER
• RESERVED
• PARTIAL
Depending on the setup of your web storefront, you can generate a different message and order line status for partially reserved items based on the setting of this system control value.
Job Queue for E-Commerce Order Processing (G53)
Purpose: Use this screen to define the job queue to use for the e-commerce interface.
MSR0053 CHANGE Change System Control Value 6/29/99 15:39:17
Description . : Job queue for E-Commerce order processing
System name . . Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
System name field: Enter the name of the job queue to use for the e-commerce interface. You might want to use a separate job queue for e-commerce, so you can reduce the amount of time a customer shopping on the web storefront needs to wait for edits or a credit check.
If you leave this field blank, the system uses QSYSNOMAX, an iSeries job queue that permits an unlimited number of jobs.
E-Commerce Staging Library (G56)
Purpose: Use this screen to define the staging library to use for e-commerce data downloads.
MSR0053 CHANGE Change System Control Value 6/29/99 15:38:22
Description . : E-Commerce Staging Library
System name . . Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
System name field: Enter the name of the library to use for the download to the web storefront.
You use these menu options to download information to the staging library:
• Downloading E-Commerce Static Files (ESTF)
• Downloading E-Commerce Offer Files (EOFR)
• Downloading B2B E-Commerce Static Files (BBED)
Additionally, you use these periodic functions:
• ECAVAIL (Download Availability)
• ECGFTC (Download Gift Certificates)
• ECITMCH (Download Item Changes)
For more information: See Downloading E-Commerce Static Files (ESTF) for an overview.
Price Override Reason for E-Commerce (G73)
Purpose: Use this screen to specify the price override reason code to use when overriding the regular price of an item for e-commerce orders.
MSR0051 CHANGE Change System Control Value 10/16/00 8:57:47
Description . : Price Override Reason for E-Commerce
Code . . . . . Z A B D G M Q X Z 1 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Code field: Enter the price override reason code to use when overriding the regular price of an item added through the e-commerce interface or the generic order interface.
Price overrides through the e-commerce interface: When you send the CWCreateOrder message, you can include a price override amount in the list_price attribute. To have this price override amount apply to the order, you can specify a valid price override reason code in the prc_ovr_rsn attribute; or you can use either this system control value or the Default Price Override Reason (B35) system control value to provide the price override reason code to assign to the order. The system uses the following logic if there is a list_price in the CWCreateOrder message:
• First check the prc_ovr_rsn specified in the message. If it is valid, use this reason.
• If a prc_ovr_rsn is specified in the message, but is invalid, or if no prc_ovr_rsn is specified in the message, but the price_override attribute is set to 1:
• If this system control value (Price Override Reason for E-Commerce) specifies a price override reason, use this reason; otherwise,
• If the Default Price Override Reason (B35) system control value specifies a price override reason, use this reason; otherwise,
• Do not use the list_price from the message. Use regular pricing logic.
• Otherwise, create the order in error because of a missing price override reason.
Price overrides through the generic order interface: When you send the CWORDERIN message, you can include a price override amount in the actual_price attribute. To have this price override amount apply to the order, you can specify a valid price override reason code in the prc_ovr_rsn attribute; or you can use either this system control value or the Default Price Override Reason (B35) system control value to provide the price override reason code to assign to the order. The system uses the following logic if there is an actual_price in the CWORDERIN message:
• First check the prc_ovr_rsn specified in the message. If it is valid, use this reason.
• If a prc_ovr_rsn is specified in the message, but is invalid:
• If this system control value (Price Override Reason for E-Commerce) specifies a price override reason, use this reason; otherwise,
• If the Default Price Override Reason (B35) system control value specifies a price override reason, use this reason; otherwise,
• Do not use the actual_price from the message. Use regular pricing logic
• If no prc_ovr_rsn is specified in the message, do not use the actual_price from the message. Use regular pricing logic.
Price override reason and order response: The order response message the system generates includes details depending on if a price override is defined for the item (a price is defined in the list_price field or 1 is defined in the no_charge field) and, if defined, the price override reason defined for the order detail line.
The order response message includes details (ship_to_number, sku, item_id, list_price, status, reserved_warehouse, and reserved_quantity) if:
• a price override is not defined for the item.
• a price override is defined for the item and the price override reason for the order line equals the value in the Price Override Reason for E-Commerce (G73) system control value.
• a price override is defined for the item and the price override reason for the order line does not equal the value in the Default Price Override Reason (B35) or Price Override Code for Promotional Priced Lines (B61) system control values.
The order response message does not include details if:
• a price override is defined for the item and the price override reason for the order line equals the value in the Default Price Override Reason (B35) system control value.
• a price override is defined for the item and the price override reason for the order line equals the value in the Price Override Code for Promotional Priced Lines (B61) system control value.
• additionally, if the item is priced at no charge, the system includes a gift response (free_gift field) in the order response message: Item added as a free gift.
Price override reason codes are defined in and validated against the Price Override Reason file. See Customer Service Establishing Price Override Reason Codes (WPOR).
Leave this field blank if you do not allow price overrides from the web storefront.
For more information:
• processing new orders from the web storefront: E-Commerce Order Creation
• processing cancellation or maintenance requests from the web storefront: Working with Batch Order Maintenance Transactions (WBOM)
• processing orders through the generic order API: Generic Order Interface (Order API)
Hold Reason for Failed E-Commerce Maintenance Transactions (H11)
Purpose: Use this screen to define the order hold reason code to use when a customer’s attempt to maintain an order on the web storefront fails.
MSR0051 CHANGE Change System Control Value 10/16/00 9:14:01
Description . : Hold Reason for Failed E-Commerce Maintenance Transactions
Code . . . . . AT AV A0 BD BU CL CW DH FR HD HF ... Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 999
F3=Exit F12=Cancel |
Code field: Enter the hold reason code to assign to an order if a customer attempts to maintain an order or process a cancellation from the web storefront, and the request fails. For example, a maintenance request might fail if the any items on the order have pick slips printed.
Hold reason codes are defined in and validated against the Order Hold Reason file; see Customer Service Establishing Order Hold Reason Codes (WOHR).
Note: If a maintenance or cancel request fails because the order is in use, the order will not go on hold.
Leave this field blank if you do not want orders to go on hold due to a failed maintenance or cancellation attempt from the web storefront.
For more information: See Working with Batch Order Maintenance Transactions (WBOM) for more information on processing cancellation or maintenance requests from the web storefront.
Order Maintenance Confirmation E-Mail Program (H12)
Purpose: Use this screen to define the program to use for generating an email confirmation when a customer attempts to maintain an order on the web storefront.
MSR0053 CHANGE Change System Control Value 10/16/00 9:15:36
Description . : Order Maintenance Confirmation E-Mail Program
System name . . ECR0273 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 30
F3=Exit F12=Cancel |
System name field: Enter the program name to use for generating confirmation emails for maintenance or cancellation requests you receive through the web storefront. The base program is ECR0273.
The system generates a notice to the customer indicating whether the attempt succeeded or failed. You use the Working with E-Mail Notification Templates (WEMT) menu option to create the templates for the success or failure notices. See When Does the System Generate an Email Notification? for a discussion of how the system determines whether to generate a notice.
For more information: See Working with Batch Order Maintenance Transactions (WBOM) for more information on processing cancellation or maintenance requests from the web storefront.
Default Add Reason for Batch OM Line Additions (H14)
Purpose: Use this screen to define the add reason code to use for order lines added through maintenance on the web storefront.
MSR0051 CHANGE Change System Control Value 10/16/00 9:18:00
Description . : Default Add Reason for Batch OM Line Additions
Code . . . . . 1 1 2
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 110
F3=Exit F12=Cancel |
Code field: Enter the add reason code to use when adding new items to orders as a result of a Maintenance Request from the web storefront.
When a customer requests to add an item at the web storefront, the system checks this system control value for an add reason code only if the:
• Require Reason for Lines Added in Order Maintenance (D75) system control value is set to Y, or
• Required reason code field for the item offer or SKU offer is set to Y.
Add reason codes are defined in and validated against the Add Reason file; see Customer Service Establishing Add Reason Codes (WADR).
Leave this field blank if you do not require add reason codes for items a customer adds to an order through order maintenance on the web storefront, regardless of the settings of the Require Reason for Lines Added in Order Maintenance (D75) or the Required reason code field for the item offer or SKU offer.
For more information: See Working with Batch Order Maintenance Transactions (WBOM) for more information on processing maintenance requests from the web storefront.
Default Salesrep for E-Commerce Interface (H24)
Purpose: Use this screen to define the default salesrep number to use on e-commerce orders if the Require Salesrep Number in Order Entry/Order Maintenance (E87) system control value is set to Y.
MSR0054 CHANGE Change System Control Value 11/15/00 15:31:56
Description . : Default Salesrep for E-Commerce Interface.
Number . . . . 34 0000034 0000067 0000299 0003434 0006767 0018812 5555555
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Number field: Enter the salesrep number to default on e-commerce orders if the Require Salesrep Number in Order Entry/Order Maintenance (E87) system control value is set to Y. If you specify a salesrep number to default, but the Require Salesrep Number in Order Entry/Order Maintenance (E87) system control value is set to N, a salesrep number does not default.
If you do not enter a salesrep number on this screen and the Require Salesrep Number in Order Entry/Order Maintenance (E87) system control value is set to Y, the order is placed in an error status regardless of whether you have defined a value for the Default Salesrep Number (E86) system control value.
Salesrep numbers are defined in and validated against the Salesrep file; see Accounts Payable Working with Sales Representatives (WSLS).
Pass Reserved Warehouse Code to E-Commerce (H25)
Purpose: Use this screen to define whether to pass item warehouse reservation information from CWDirect to your web storefront.
MSR0052 CHANGE Change System Control Value 11/16/00 14:38:01
Description . : Pass Reserved Warehouse Code to E-Commerce.
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 999
F3=Exit F12=Cancel |
Yes/No field: If you set this field to Y, the system passes the warehouse where an item is reserved and the reserved quantity of that item to the web storefront. This works for single or multi-recipient orders, for a single item or numerous items reserving in the same or different warehouses.
Example: If one customer orders three different items and they are in stock but in three different warehouses, the system passes a reserved warehouse and the reserved quantity in that warehouse for each item. If there are multiple recipients on the order, this information is passed for each ship-to customer.
The reserved quantity number that the system passes to the web storefront reflects only the number of items that are actually reserved in the associated warehouse(s). If an item is backordered or soldout, the status message changes and no reserved warehouse or quantity information is passed. If a warehouse has enough stock to fulfill only part of an order, the status shows how many items are reserved, backordered, and sold out, and the reserved warehouse and reserved quantity display only for the items actually reserved.
Set Items: For set items, the system passes the reserve warehouse of the master set item, regardless of whether the component items of the set are in the same warehouses as the master set item.
Note: If you pass an order from CWDirect with the pay_incl (pay include) field set to Y and credit card information included for the order, the system will not pass the reserved warehouse and the reserved quantity information to the web storefront.
If you set this field to N, you do not pass reserved warehouse and reserved quantity information to your web storefront.
For more information: See E-Commerce Interface.
Default Recipient Type for E-Commerce Orders (H33)
Purpose: Use this screen to define the default recipient (ship-to) type for e-commerce orders when a web storefront customer selects an alternate shipping address for an order.
MSR0051 CHANGE Change System Control Value 11/29/00 8:48:15
Description . : Default Recipient Type for E-Commerce Orders
Code . . . . . ORDER ORDER CUSTOMER PERMANENT
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 100
F3=Exit F12=Cancel |
Code field: Enter the code which will define the default type of recipient order the system will create for an e-commerce order when a web storefront customer selects an alternate shipping address and the retailer has not set up his storefront to specify which type of alternate shipping address to create. Valid codes are:
• ORDER or blank - Create an order ship-to address. This address type corresponds to the function F14 in order entry or order maintenance. In the New Order message sent from the web storefront to CWDirect, the Ship_to_type = 1. See Order Entry Assigning an Order Shipping Address.
• CUSTOMER - Create a sold-to recipient address. This address type corresponds to the function F2 (Sold To Recipient) in order entry or order maintenance. This is the function you would use to create a gift recipient. In the New Order message sent from the web storefront to CWDirect, the Ship_to_type = 2. See Order Entry Adding a Recipient Order.
• PERMANENT - Create a permanent ship-to address for the customer. This address type corresponds to the function F7 (Customer Ship To) in order entry or order maintenance. This is the function you would use to create an alternate address for a customer. In the New Order message sent from the web storefront to CWDirect, the ship_to_type = 3. See Order Entry Using a Permanent Shipping Address.
E-Commerce order maintenance transactions: When you receive an E-Commerce Maintenance message containing a new ship-to address, the system looks at the value in this system control value to determine the type of ship-to address to create. However, if a ship-to customer or permanent ship-to already exists on the order, the system creates an order ship-to address, regardless of the value in this system control value. See Working with Batch Order Maintenance Transactions (WBOM).
If you leave this field blank, the default ship to type for an e-commerce order will correspond to the function F14 in order entry.
Duplicate customer check: When the system creates a sold-to recipient address (CUSTOMER type) or permanent ship to address (PERMANENT type) for an e-commerce order, the system checks existing customers for a match with:
• the same match code, and
• the same name and address fields whose related system control values for duplicate customer checking are set to Y. See Duplicate Checking for Customers (F71-F77, H88 and I11).
Pass Order Ship To # in New Order Response Message (H47)
Purpose: Use this screen to specify whether the ship to number will be passed in the New Order Response message sent from CWDirect to the web storefront for a single ship to order. Multi-ship to order response messages will always include ship to numbers, regardless of how you set this system control value.
MSR0052 CHANGE Change System Control Value 7/13/01 12:36:59
Description . : Pass Order Ship To # in New Order Response Message
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99999
F3=Exit F12=Cancel |
Yes/No field: If you set this field to Y, the system always includes the order ship to number in the New Order Response message sent from CWDirect to a web storefront.
If you set this field to N, the system does not include the order ship to number in the New Order Response message for single ship-to orders. However, for multi-ship-to orders, the ship to number is always included in the message, regardless of the setting of this field.
For more information: See System Operations Working with E-Commerce Job Control (EJCT) for information on how messages are passed to and from a web storefront. See the E-Commerce Interface for examples of messages and the files and fields they update in CWDirect.
Maximum Order Amount for E-Commerce Orders (H54)
Purpose: Use this screen to define the order amount that will cause an e-commerce order to be placed on hold automatically.
MSR0056 CHANGE Change System Control Value 1/14/02 9:46:31
Description . : Maximum Order Amount for E-Commerce Orders
Dollar amount . Narrative . . .
Application . : O/E Applic group . FRD Sequence# . . . 99
F3=Exit F12=Cancel |
Dollar amount field: Enter the dollar amount that will cause an e-commerce order to be placed on hold automatically. This field is 12 positions with a 2-place decimal.
This dollar amount hold applies to all methods of payment.
Important: The system evaluates the Maximum Order Amount for Ecommerce Orders only if a dollar amount has also been defined for the Maximum Order Amount (A92) system control value.
If the total amount of the order is greater than the amount defined here, the order will be placed on e-commerce hold (EH type hold) when Credit Checking is performed. These orders display on the Release Held Orders screen and must be released from hold manually using Release Held Orders. See Customer Service Selecting Held Orders (ERHO).
Order history message: If the order is placed on e-commerce dollar hold, CWDirect creates an order history message: 1/28/02 H SYS HLD---E-COMMERCE DOLLAR HOLD. You can review order history message at the Display Order History Screen.
Determining an e-commerce order: CWDirect identifies an e-commerce order by an I in the Internet order field in the Order Header file or the order type for the order matches the order type defined in the E-Commerce Order Type (G42) system control value.
Leave this field blank (.00) if you do not want to establish a separate maximum dollar amount for e-commerce orders. Instead, the dollar amount defined in the Maximum Order Amount (A92) system control value is used to determine if an order should be placed on hold automatically.
For more information: See Customer Service Establishing Order Hold Reason Codes (WOHR) for more information on creating the e-commerce dollar hold reason code.
Division for Source Code Download (H66)
Purpose: Use this screen to indicate the division to include when selecting source codes for B2B e-commerce downloads.
MSR0051 CHANGE Change System Control Value 11/02/01 16:24:33
Description . : Division for Source Code Download
Code . . . . . CA 01 1A 1B 11 2 2A 2B 3 4 Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Code field: Enter a division code to restrict the extract to source codes assigned to that division; or, leave the field blank to select all source codes regardless of division. Only unrestricted source codes (based on the Restricted field) are included. This value controls extracts you make using the Downloading B2B E-Commerce Static Files (BBED) menu option; it does not affect the processing of the Downloading E-Commerce Offer Files (EOFR) option.
For more information:
• Division codes are defined in and validated against the Division file. See Accounts Payable Working with Divisions (WDIV).
• See Marketing Working with Source Codes (WSRC) for an overview on source codes.
Default Price Table Code for E-Commerce Extraction (H67)
Purpose: Use this screen to indicate the price table to select for B2B e-commerce downloads.
MSR0051 CHANGE Change System Control Value 11/02/01 16:27:38
Description . : Default Price Table Code for E-Commerce Extraction
Code . . . . . 789 $ITEM 123 456
Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Code field: Enter a price table code to restrict price table information you download through Downloading B2B E-Commerce Static Files (BBED) to this price table only; or, leave this field blank to include all price tables in the download. Valid price table codes display beside the Code field.
About price tables: You can use price tables to define a pricing structure based on unit quantity or total dollars ordered, including price breaks for individual items on an order, or for the total order of a group of items. Price tables can also identify items offered as free or reduced-price premiums on qualifying orders. See Marketing Working with Price Tables (WPTB).
Pass E-Commerce Order Status Response Type (H68)
Purpose: Use this screen to define whether an Order Status Response Message is generated, regardless of whether an order is found that matches the order status inquiry request.
MSR0052 CHANGE Change System Control Value 1/18/02 14:17:59
Description . : Pass E-Comm Order Status Response Type - Y/N
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you wish to generate an E-Commerce Order Status Response Message (CWStatusResponse), regardless of whether an order is found that matches the order_id in the E-Commerce Order Status Message (CWOrderStatus).
The Order Status Response message includes the response_type field, which indicates whether an order was found that matches the order status inquiry request.
• 1 (order found and last name matches) indicates an order was found that matches the order status inquiry and the bill to last name, company name, and/or individual last name defined for the inquiry matches the name on the order. The Order Status Response message contains the order information with a response type of 1.
• 2 (order found/last name mismatch) indicates an order was found that matches the order status inquiry, but the last name defined for the inquiry (bill_to_lname, ind_lname, or company_name) does not match the last name on the order. The Order Status Response Message contains the order information with a response type of 2; you can decide to display an error on your web storefront indicating the mismatch or display the order information on the web storefront, regardless of the mismatch.
• 3 (order not found) indicates an order was not found that matches the order status inquiry. The Order Status Response Message includes company, order number, and a response type of 3, but does not include order information.
Note: You will not receive an Order Status Response Message if the connection between the web storefront and the E-Commerce server is not made, regardless of the setting of this system control value.
Leave this field blank or enter N if you with the system to only send an Order Status Response message to the web storefront when an order number is found that matches the order_id in the Order Status message and a match is found on at least one of the name fields in the request (bill_to_lname, ind_lname, or company_name).
Additionally, when this system control value is blank or N, the Order Status Response Message does not include the response_type field.
For more information: See E-Commerce Order Status Processing for additional processing information.
Generate E-Commerce Customer Merge Staging Files (H86)
Purpose: Use this screen to define whether CWDirect populates the e-commerce customer merge staging files when you run the customer sold to merge/purge program or customer bill to merge/purge program.
MSR0052 CHANGE Change System Control Value 1/31/02 11:52:58
Description . : Generate E-Commerce Customer Merge Staging Files
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want CWDirect to populate the e-commerce customer merge staging files when you run the customer sold to merge/purge program or customer bill to merge/purge program.
When you run the customer sold to merge/purge program using the Working with Merge/Purge Sold-to Names (MMCS) menu option, CWDirect populates the EC Customer Sold To Merge Staging file if this system control value is set to Y. CWDirect also populates the EC Customer Individual Merge Staging file if the sold to customer is associated with individuals.
When you run the customer bill to merge/purge program using the Merging and Purging Customer Bill To Names (MMCB) menu option, CWDirect populates the EC Customer Bill To Merge Staging file if this system control value is set to Y.
The EC Customer Sold To Merge Staging file, EC Customer Individual Merge Staging file, and EC Customer Bill To Merge Staging file are located in the library defined in the E-Commerce Staging Library (G56) system control value.
E-Commerce File Download Trigger Process (TRIGGER_DL)
The e-commerce File Download Trigger process sends a Customer Merge XML Message (CWFileTransfer) through CWIntegrate to the web storefront when you process a customer sold to merge or customer bill to merge in CWDirect. The Customer Merge XML message indicates that customers have been merged in CWDirect and the customer information on the web may now be inaccurate. It is the web storefronts responsibility to retrieve the records in the e-commerce customer merge staging files (EC Customer Sold To Merge Staging file, EC Customer Individual Merge Staging file, and EC Customer Bill To Merge Staging file). You can work with the e-commerce file download trigger process using the Working with Integration Layer Processes (IJCT) menu option.
Customer Merge XML Message (CWFileTransfer)
The Customer Merge message indicates that customers have been merged in CWDirect and the e-commerce customer merge staging files contain new records to update the web storefront.
For more information: See XML Messages for a table that provides links to the DTD, schema, and a sample XML layout for each XML message.
Customer merge message:
Attribute Name |
Type |
Length |
Comments |
source |
alpha |
25 |
Identifies the source of the XML message. RDC indicates the XML message is from CWDirect. |
target |
alpha |
25 |
Identifies the target of the XML message. IL indicates the XML message is sent to the web storefront. |
type |
alpha |
25 |
Identifies the type of information in the XML message. CWFileTransfer indicates the message contains customer merge information. |
fileType |
alpha |
25 |
CWCustMerge indicates that customers have been merged in CWDirect and the customer information on the web may now be inaccurate. It is the web storefronts responsibility to retrieve the records in the e-commerce customer merge staging files: • EC Customer Sold To Merge Staging file • EC Customer Individual Merge Staging file • EC Customer Bill To Merge Staging file Note: CWCustMerge displays, regardless of the type of customer (sold to, individual, or bill to) that has been merged. |
Customer Merge Message: Sample XML
A sample of the Customer Merge XML Message (CWFileTransfer) is presented below.
<Message source="RDC" target="IL" type="CWFileTransfer">
<CWFileTransfer fileType="CWCustMerge" />
</Message>
Leave this field blank or enter N if you do not want CWDirect to populate the e-commerce customer merge staging files when you run the customer sold to merge/purge program or customer bill to merge/purge program.
For more information:
• customer sold to merge/purge: Marketing Working with Merge/Purge Sold-to Names (MMCS)
• customer bill to merge/purge: Marketing Merging and Purging Customer Bill To Names (MMCB)
• e-commerce file download trigger process: System Operations Working with Integration Layer Processes (IJCT)
• e-commerce overview and XML messages: E-Commerce Interface
E-Commerce Item Availability Download Method (I10)
Purpose: Use this screen to define the method the system uses to download e-commerce item availability data.
MSR0051 CHANGE Change System Control Value 2/13/03 12:02:52
Description . : E-Commerce Item Availability Download Method
Code . . . . . FILE XML BOTH
Narrative . . .
Application . : EDC Applic group . CST Sequence# . . . 99
F3=Exit F12=Cancel |
Code field: Enter the method you wish the system to use to download e-commerce item availability data.
The methods you can select are:
• FILE: the system downloads e-commerce item availability data to the EC Item Availability file in the E-Commerce Staging Library (G56) for retrieval by the web storefront.
• XML: the system downloads e-commerce item availability data to a E-Commerce Item Availability Response Message (CWAvailResponse) and sends the XML message to the E-Commerce Item Availability job for processing.
• BOTH: the system downloads e-commerce item availability data to the EC Item Availability file and a CWAvailResponse XML message.
When is item availability data downloaded? The system extracts item availability information 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 web threshold, triggering an interactive download.
• you enter or maintain a purchase order for an item whose available quantity is zero or less.
• you change the soldout control code assigned to an item.
For more information:
• See E-Commerce Item Availability Processing for more information on downloading item availability data.
• See E-Commerce Item Availability Processing for more information on receiving a E-Commerce Item Availability Request Message (CWItemAvail) from the web storefront.
• See E-Commerce Item Availability Response Message (CWAvailResponse) for a message layout.
Leave this field blank if you want the system to download e-commerce item availability data to the EC Item Availability file in the E-Commerce Staging Library (G56) for retrieval by the web storefront.
Perform Order Edit Interactively (I56)
Purpose: Use this screen to indicate whether to perform the order edit interactively for orders you receive through the e-commerce interface or the generic order API.
MSR0052 CHANGE Change System Control Value 2/11/04 16:34:18
Description . : Perform Order Edit Interactively
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the order edit to occur interactively when you create an order through the e-commerce interface or the generic order API.
Why use interactive edit? If you use the interactive edit, the order totals and other information included in the response message the system sends when you create an order are more accurate. For example, if you use the e-commerce interface to create an order that includes a freight discount promotion or accompanying item, the response message includes the discount or accompanying item.
Many types of discounts are applied before the order edit, and are still reflected in the order totals even if the edit has not yet taken place. For example, dollar discounts by source code (that is, discounts that are not applied with a negative additional charge) are reflected in the merchandise totals before the order edit takes place.
When you use the interactive edit, the Order Error Listing generated for e-commerce or order API orders in error is available for review under the job that processes the orders, rather than under the ORDER_EDIT job.
Restrictions of the interactive edit:
• For e-commerce orders, you must also have the Send Order Response After E-Commerce Payment Message (I57) system control value set to Y in order to have the system generate a CWOrderResponse message which includes final totals and other details determined at order edit. See that system control value for more information.
• For orders received through the generic order API, pricing and order total information is included only when you send the Detailed Order XML Response (CWORDEROUT). The response_type specified in the Inbound Order XML Message (CWORDERIN) controls whether an order response is generated when the order goes through the edit. If the response_type is:
• D (detailed): the system sends the Detailed Order XML Response (CWORDEROUT)
• E (errors): the system sends the Detailed Order XML Response (CWORDEROUT), including descriptions of any errors currently on the order
• A (acknowledgement): the system sends the Order Acknowledgement XML Message (CWORDEROUT)
• N (no response): the system does not send a response when the order goes through the edit.
Note: If the payment information is sent separately from the rest of the order in the generic order API, the CWORDEROUT message might be generated twice: once when you receive the initial order message, and once when you receive the payment information.
• If an order is in error and fails the edit, the response will not reflect the final totals and other information determined through the order edit. In this situation, even discounts that are normally applied before the order edit (such as dollar discounts by source) might not be reflected in the order response message.
• Selecting this system control value could potentially lengthen the response time at the web storefront.
Leave this field blank or enter N if you want to submit the order edit to the batch job queue. The order response does not include information such as discounts, free gifts, or ship via overrides made in final order processing, and if the response_type is set to E, the response message does not include all errors that would be found through the order edit. Also, the Order Error Listing generated for e-commerce or order API orders in error is available for review under the ORDER_EDIT job.
Discounting and Added Items in the Response Message
The following table summarizes when the response message reflects repricing and free or accompanying items, based on the settings of the Perform Order Edit Interactively (I56) and Apply End of Order Discounts during Repricing (J37) system control values.
Discount |
Applies to Web Orders? |
SCV I56 setting |
SCV J37 setting |
Reflected in First Response? |
free gifts by offer or source code See Work with Offer Free Gifts Screen (WOFR) and Work with Source Free Gifts Screen (WSRC) |
yes |
Y |
Y |
yes |
Y |
N |
no |
||
N |
Y |
yes |
||
N |
N |
no |
||
promotions: order (O), freight (F), tiered (T), and additional freight (A) types |
yes |
Y |
Y |
yes |
Y |
N |
no |
||
N |
Y |
yes |
||
N |
N |
no |
||
telemarketing specials See Work with Telemarketing Specials Screen (WOFR) |
no |
N/A |
N/A |
N/A |
promotional pricing See Work with Promotional Pricing (WPRP) The Promotional Pricing job, started through the Working with Integration Layer Processes (IJCT) menu option, allows you to offer promotional pricing on the web storefront; see E-Commerce Promotional Pricing for an overview. |
yes |
N/A |
N/A |
yes, based on promotional pricing added to the order during checkout on the web storefront |
price codes |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
price tables |
yes |
Y |
Y |
discounting: yes free gift: yes |
Y |
N |
discounting: yes free gift: no |
||
N |
Y |
discounting: no free gift: yes |
||
N |
N |
no |
||
quantity break by item |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
package inserts |
yes |
Y |
Y |
yes |
Y |
N |
no |
||
N |
Y |
yes |
||
N |
N |
no |
||
accompanying items |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
source percentage discount |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
source dollar discount |
yes |
Y |
Y |
yes |
Y |
N |
no |
||
N |
Y |
yes |
||
N |
N |
no |
||
customer percentage discount |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
membership discount |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
associate pricing |
yes |
Y |
Y |
yes |
Y |
N |
|||
N |
Y |
no |
||
N |
N |
|||
upsell promotions |
no |
N/A |
N/A |
N/A |
coupon promotions |
yes |
Y |
Y |
yes |
|
Y |
N |
||
|
N |
Y |
||
|
N |
N |
Order Processing Overview: E-Commerce Orders
The following chart illustrates how this system control value and the Send Order Response After E-Commerce Payment Message (I57) affect the sequence of steps taken and messages generated when you receive orders through the e-commerce interface
Summary: The steps for e-commerce order processing are:
• The EC_ORDERS job receives the CWCreateOrder message. If the order does not include payment information, the job generates the CWOrderResponse message and the EC_PAY_ACC job waits for payment information on the order.
• If the order does include payment information, or if the EC_PAY_ACC job receives the CWPayment message providing payment information for an in-process order, the system checks the setting of the Perform Order Edit Interactively system control value.
• If this system control value is selected, the EC_PAY_ACC job performs the order edit before proceeding to the next step. If the order is in error, the spool file listing the error information is available under the EC_PAY_ACC job.
• If this system control value is not selected, the EC_PAY_ACC job submits the order to the batch order edit and proceeds to the next step without waiting for the edit to complete. If the order is in error, the spool file listing the error information is available under the ORDER_EDIT job.
• The EC_PAY_ACC job checks the setting of the Send Order Response After E-Commerce Payment Message (I57) system control value.
• If this system control value is selected, the job generates the CWOrderResponse message, including the payment information for the order. Otherwise, the EC_PAY_ACC job does not generate a response message.
For more information: See:
• Working with E-Commerce Job Control (EJCT)
Order Processing Overview: Generic Order API
The following chart illustrates how this system control value affects the sequence of steps taken when you receive orders through the generic order API:
Summary: The steps for generic order API processing are:
• The ORDER_IN process receives the Inbound Order XML Message (CWORDERIN) message.
• If the order does not include payment information (the pay_incl attribute is set to N) and the response_type is set to D (detailed) or E (errors), the job generates the Detailed Order XML Response (CWORDEROUT), and waits for payment information on the order. Otherwise, if the response_type is set to A or N, the job generates the Order Acknowledgement XML Message (CWORDEROUT) and waits for payment information on the order.
• If the order does include payment information, or if the ORDER_IN job receives the CWORDERIN message providing payment information for an in-process order, the system checks the setting of the Perform Order Edit Interactively system control value.
• If this system control value is selected, the ORDER_IN job performs the order edit before proceeding to the next step. If the order is in error, the spool file listing the error information is available under the inbound job name for the ORDER_IN process queue.
• If this system control value is not selected, the job submits the order to the batch order edit and proceeds to the next step without waiting for the edit to complete. If the order is in error, the spool file listing the error information is available under the ORDER_EDIT job.
• The job checks the setting of the response_type attribute in the CWORDERIN message.
• If the response_type is D or E, the job generates the Detailed Order XML Response (CWORDEROUT).
• If the response_type is A, the job generates the Order Acknowledgement XML Message (CWORDEROUT).
• Otherwise, the job does not generate the CWORDEROUT message.
For more information: See:
• Generic Order Interface (Order API)
• Working with Integration Layer Processes (IJCT)
Send Order Response After E-Commerce Payment Message (I57)
Purpose: Use this screen to specify whether the e-commerce ORDER PAYMENT/ACCEPT process should send an order response message after processing payment information for an order.
MSR0052 CHANGE Change System Control Value 2/11/04 16:36:07
Description . : Send Order Response After E-commerce Payment Message
Yes/No . . . . N (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the e-commerce ORDER PAYMENT/ACCEPT function to send the CWOrderResponse message to the web storefront after updating a new e-commerce order with payment information.
When is the response message sent? You can choose to send the response message to the web storefront at one or two different points:
• The e-commerce ORDER PROCESSING function always sends the CWOrderResponse message when it receives a new order message that does not include payment information (that is, the payment information will be sent separately).
• In addition, if this system control value is selected, the e-commerce ORDER PAYMENT/ACCEPT function also sends the CWOrderResponse message after adding payment information to the order.
Why send response message after payment? You might choose to send the response message after the payment if you currently send the order and payment information for e-commerce orders in a single message, rather than sending the payment separately.
Includes final order totals? The Perform Order Edit Interactively (I56) system control value controls whether the CWOrderResponse message includes final order totals determined during the order edit process after payment information is received. See that system control value for more information.
Leave this field blank or enter N if you do not want to send the CWOrderResponse message after receiving payment information for new e-commerce orders.
Download Prepaid Payment Types to E-Commerce (I69)
Purpose: Use this screen to define whether the system includes prepaid (cash/check payment category 1) payment types in the e-commerce pay type extraction.
MSR0052 CHANGE Change System Control Value 2/25/04 11:18:53
Description . : Download Prepaid Payment Types to E-Commerce
Yes/No . . . . N (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you wish the system to include prepaid (cash/check payment category 1) payment types in the e-commerce pay type extraction.
The system downloads credit card payment types (payment category 2), A/R payment types (payment category 3), and coupon/credit payment types (payment category 5) to the EC Payment Type file when you select the Payment type field at the Process E-Commerce Downloads Screen. If the Download Prepaid Payment Types to E-Commerce system control value is set to Y, the system also downloads cash/check payment types (payment category 1) to the EC Payment Type file.
Enter N or leave this field blank if you do not wish the system to include cash/check payment types in the e-commerce pay type extraction. The system downloads only credit card, A/R, and coupon/credit payment types to the EC Payment Type file.
Note: Regardless of the setting of the Download Prepaid Payment Types to E-Commerce system control value, the system downloads open, unredeemed coupons and gift certificates from the Coupon Redemption file to the EC Gift Certificate file when you run the ECGFTC (program name ECR0142) periodic function.
Use SCF Ship Via in E-Commerce (J30)
Purpose: Use this screen to define whether the system overrides the ship via on a remote ship to order with the preferred ship via defined for the ship to customer’s SCF.
MSR0052 CHANGE Change System Control Value 1/16/06 8:14:26
Description . : Use SCF Ship Via in E-Commerce
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the system to override the ship via code on a remote ship to order with the ship via code defined in the Preferred ship via field for the ship to customer’s SCF (the first 3 digits of the destination postal code).
The system looks at the setting of this system control value when processing any remote order (e-commerce order (both XML and name/value pair), order API, and phone order interface). The system does not look at the setting of this system control value during interactive order entry (OEOM).
Ship via defaults for remote orders: The system uses the following logic to determine the ship via code to default to a remote ship to order when the Use SCF Ship Via in E-Commerce (J30) system control value is set to Y.
If a ship via code is defined for the remote ship to order:
1. Use the ship via code defined in the Preferred ship via field for the ship to customer’s SCF. However, the system only defaults the preferred ship via to the remote ship to order if the Allow auto assignment field for the current ship via code on the order is set to Y.
2. If the Preferred ship via field for the ship to customer’s SCF is blank or the Allow auto assignment field for the current ship via code is set to N, use the ship via code defined on the remote ship to order.
If a ship via code has not been defined for the remote ship to order:
1. Use the ship via code defined in the Preferred ship via field for the ship to customer’s SCF. However, the system only defaults the preferred ship via to the remote ship to order if the Allow auto assignment field for the ship via code defined in the Default Ship Via (A77) system control value is set to Y.
2. If the Preferred ship via field for the ship to customer’s SCF is blank or the Allow auto assignment field for the Default Ship Via (A77) is set to N, use the ship via code defined in the Default Ship Via (A77) system control value.
Example: A remote order is received into CWDirect. The ship via code defined on the remote order is 1.
Allow auto assignment for ship via 1 |
Preferred ship via for SCF |
Results |
Y |
2 |
Preferred ship via code 2 defaults to the order. |
Y |
blank |
Ship via code 1 remains on the order. |
N |
2 |
Ship via code 1 remains on the order. |
N |
blank |
Ship via code 1 remains on the order. |
Example: A remote order is received into CWDirect. A ship via code has not been defined for the remote order. The Default Ship Via (A77) is 3.
Allow auto assignment for ship via 3 |
Preferred ship via for SCF |
Results |
Y |
2 |
Preferred ship via code 2 defaults to the order. |
Y |
blank |
Default ship via code 3 defaults to the order. |
N |
2 |
Default ship via code 3 defaults to the order. |
N |
blank |
Default ship via code 3 defaults to the order. |
Enter N or leave this field blank if you do not want the system to override the ship via code on a remote ship to order with the ship via code defined in the Preferred ship via field for the ship to customer’s SCF.
The system uses the ship via code defined for the remote ship to order. If a ship via code has not been defined for the remote ship to order, the system uses the ship via code defined in the Default Ship Via (A77) system control value.
Pass Ship To Address in E-Commerce Status Inquiry (J33)
Purpose: Use this screen to define whether the complete ship to name and address information is included in the E-Commerce Order Status Response Message (CWStatusResponse).
MSR0052 CHANGE Change System Control Value 1/17/06 15:45:41
Description . : Pass Ship To Address in E-comm Sts Inq
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you wish to include the complete ship to name and address information in the E-Commerce Order Status Response Message (CWStatusResponse).
If the Pass Ship To Address in E-Commerce Status Inquiry (J33) system control value is set to Y, the system includes the following tags in the ShipTo element of the message:
Enter N in or leave this field blank if you wish to only include the ship to name in the E-Commerce Order Status Response Message (CWStatusResponse).
If the Pass Ship To Address in E-Commerce Status Inquiry (J33) system control value is set to N, the system includes the following tags in the ShipTo element of the message:
For more information: See E-Commerce Order Status Processing for more information on requesting order summary information from the web storefront.
Write Promotional Information to the Order Response Message (J38)
Purpose: Use this screen to define whether the system includes the Promotion element in the E-Commerce New Order Response Message (CWOrderResponse) when the Apply End of Order Discounts during Repricing (J37) system control value is set to Y.
MSR0052 CHANGE Change System Control Value 3/07/06 16:19:13
Description . : Write Promotional Info to the Order Response Message
Yes/No . . . . (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the system to include the Promotion element in the E-Commerce New Order Response Message (CWOrderResponse) when the Apply End of Order Discounts during Repricing (J37) system control value is set to Y.
Note: The Promotion element is included in the E-Commerce New Order Response Message (CWOrderResponse) only if the Apply End of Order Discounts during Repricing (J37) system control value and Write Promotional Information to the Order Response Message (J38) system control value are set to Y. In addition, the Promotion element and all of its attributes is available in version 10.0 or later of CWDirect for XML only.
What does the Promotion element contain? The Promotion element contains the end of order discounts that have been applied to the order. See End of Order Discounts Applied during Repricing for a list of the end of order discounts that can be included in the Promotion element.
Enter N or leave this field blank if you do not want the system to include the Promotion element in the E-Commerce New Order Response Message (CWOrderResponse) when the Apply End of Order Discounts during Repricing (J37) system control value is set to Y.
Hold Reason for Duplicate Items Found in Processing Remote Orders (J51)
Purpose: Use this screen to specify the order hold reason code to use for an order received from an external system if it includes a duplicate item recently ordered by the customer.
MSR0051 CHANGE Change System Control Value 12/07/06 13:46:03
Description . : Hold Reason for Dup Items Found in Processing Remote Orders
Code . . . . . DP AT AV A0 BD BF BU CB CL CW DH DP ... Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Code field: Enter a valid order hold reason code to have the system put an order you receive from a remote system on hold if it includes a duplicate item. This check takes place for orders you receive through the Generic Order Interface (Order API), E-Commerce Order Creation, and Loading Remote Orders.
Why use this system control value? Using this order hold reason enables you to easily identify such orders when you use Selecting Held Orders (ERHO) and release them from hold as appropriate. There might be situation when you would like to release most orders that are held due to the presence of a duplicate item, such as when the same item is added to multiple orders through Package Insert Processing (WPIP).
Identifying duplicate items: The system considers an item a duplicate if the Duplicate Item Check (C09) system control value is set to Y, and the same item has appeared on orders for the customer within the number of days specified in the Duplicate Item Days (C58) system control value.
Exceptions:
• Express bill orders: Duplicate item checking does not apply to orders you receive from a remote system that have an express bill ship via, indicating that the orders have already been shipped.
• Additional hold reasons: If an additional hold reason applies to the order, the system does not apply the hold reason code specified with this system control value.
About order hold reason codes: Use Establishing Order Hold Reason Codes (WOHR) to set up the hold reason code for this system control value.
Leave this field blank if you do not want to place orders containing duplicate items on hold. If you have duplicate item checking set up through the use of the Duplicate Item Check (C09) and the Duplicate Item Days (C58) system control values, evaluation of remote orders that include duplicate items varies based on the setting of the Apply End of Order Discounts during Repricing (J37) system control value:
• If the Apply End of Order Discounts during Repricing (J37) system control value is set to Y: Duplicate item checking does not apply to remote orders (received through the order API, e-commerce interface, or the phone order load).
• If the Apply End of Order Discounts during Repricing (J37) system control value is set to N: The system initially puts the order in error status with an error of Duplicate item for cust. If you receive the order Inbound Order XML Message (CWORDERIN) and the response_type is set to E (errors), then the Detailed Order XML Response (CWORDEROUT) indicates this error occurred. However, once you submit the order batch for edit, the edit process puts the order in open status provided there are no additional errors.
Include Set Components in Order Status Response Message (J83)
Purpose: Use this screen to indicate whether to include set components, or just the set master item, in the CWOrderStatusResponse e-commerce message.
MSR0052 CHANGE Change System Control Value 11/01/07 17:12:50
Description . : Include Set Components in Order Status Response Message
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the system to include both the set master item and set component items in the E-Commerce Order Status Response Message (CWStatusResponse) when it receives the E-Commerce Order Status Message (CWOrderStatus) for an order that includes a set item. You would typically use this setting if you apply pricing to sets at the component level rather than at the set master item level, so that the status response message indicates the pricing for set items on an order.
Types of pricing for sets: There are two ways to apply pricing for set items:
• Price at the set master item: The full price of the set applies to the set master items, and each of the components are added to the order with a price of zero
• Price at the component level: The price of the set is prorated across the component items, and the set master item is added to the order with a price of zero
If you always price sets at the component level, then a status response message that includes the components is the only way to provide an accurate indication of the pricing for a set. However, if you always price sets at the master level, then including the components in the response message does not provide any additional pricing information, and might be less efficient.
Example: You have a set of spices for a total price of $20.00. If you apply pricing at the set master level, the items are added to the order as:
• SPICES (set master): $20.00
• OREGANO (component): $0.00
• BASIL (component): $0.00
• PARSLEY (component): $0.00
• MARJORAM (component): $0.00
However, if you apply pricing at the component level, depending on the percentage of the total set price assigned to each component, the items might be added to the order as:
• SPICES (set master): $0.00
• OREGANO (component): $5.00
• BASIL (component): $5.00
• PARSLEY (component): $5.00
• MARJORAM (component): $5.00
If you set this system control value to Y and pricing is at the component level, the set master items and its components would appear similar to the following in the order status response message, with the price of the set master at zero and the total price of the set applied to the individual components:
<Items>
<Item sku="2221" item_id="SPICES" line_nbr="1" description="ASSORTMENT OF SPICES" quantity="1" list_price="0000000" status=" In stock and reserved"/>
<Item sku="2131" item_id="OREGANO" line_nbr="2" description="ALLSPICE 2 OZ." quantity="3" list_price="0000500" status=" In stock and reserved"/>
<Item sku="2132" item_id="BASIL" line_nbr="3" description="CLOVE 2 OZ." quantity="3" list_price="0000500" status=" In stock and reserved"/>
<Item sku="2129" item_id="PARSLEY" line_nbr="4" description="CUMIN 2 OZ." quantity="1" list_price="0000500" status=" In stock and reserved"/>
<Item sku="2129" item_id="MARJORAM" line_nbr="5" description="CUMIN 2 OZ." quantity="1" list_price="0000500" status=" In stock and reserved"/>
</Items>
However, if this system control value is set to Y and pricing for a set is at the master level, the set item and its components in the order status response message would be similar to the following:
<Items>
<Item sku="2221" item_id="SPICES" line_nbr="1" description="ASSORTMENT OF SPICES" quantity="1" list_price="0002000" status=" In stock and reserved"/>
<Item sku="2131" item_id="OREGANO" line_nbr="2" description="ALLSPICE 2 OZ." quantity="3" list_price="0000000" status=" In stock and reserved"/>
<Item sku="2132" item_id="BASIL" line_nbr="3" description="CLOVE 2 OZ." quantity="3" list_price="0000000" status=" In stock and reserved"/>
<Item sku="2129" item_id="PARSLEY" line_nbr="4" description="CUMIN 2 OZ." quantity="1" list_price="0000000" status=" In stock and reserved"/>
<Item sku="2129" item_id="MARJORAM" line_nbr="5" description="CUMIN 2 OZ." quantity="1" list_price="0000000" status=" In stock and reserved"/>
</Items>
Set this system control value to N or leave it blank if you do not want to include set components in the order status response message, typically because you apply pricing to set items at the set master level.
In this situation, if pricing is at the set master level, only the set master would be included in the order response message:
<Items>
<Item sku="2221" item_id="SPICES" line_nbr="1" description="ASSORTMENT OF SPICES" quantity="1" list_price="0002000" status=" In stock and reserved"/>
</Items>
However, if this system control value is set to N or blank and a set item is priced at the component level, the pricing of the set is not indicated in the order response message:
<Items>
<Item sku="2221" item_id="SPICES" line_nbr="1" description="ASSORTMENT OF SPICES" quantity="1" list_price="0000000" status=" In stock and reserved"/>
</Items>
For more information: See:
• Entering Set Information (WSET) for general information on set items, including selecting a pricing method
• E-Commerce Order Status Processing for background on the order status request and response messages
E-mail Shipment/Return Confirmation Notification Immediately (K07)
Purpose: Use this screen to indicate whether to generate the shipment or return confirmation email immediately when billing the transactions, or to use a separate menu option to generate the emails on demand.
MSR0052 CHANGE Change System Control Value 12/12/08 15:43:59
Description . : E-mail Shipment/Return Confirmation Notification Immediately
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the billing async job (BILL_ASYNC) to generate shipment and return confirmation emails or the Outbound Email XML Message (CWEmailOut) for eligible orders when it bills shipments and returns.
Set this system control value to N or leave it blank if you want to use the Sending Internet Order Ship Confirmation (ESCF) option to generate emails or the Outbound Email XML Message (CWEmailOut), rather than generating them immediately as the orders are billed.
Determining whether to generate an email: The same rules apply to generating shipment and return confirmation emails immediately as when you use the Sending Internet Order Ship Confirmation (ESCF) option. See Sending Internet Order Ship Confirmation (ESCF) for an overview on how the system determines whether to generate the shipment or return confirmation email or the Outbound Email XML Message (CWEmailOut) for an order.
Generating Multiple Confirmations for the Same Shipment or Return Invoice
Avoiding duplicate emails: If this system control value is set to Y and you use Sending Internet Order Ship Confirmation (ESCF), the option generates an additional email notification or Outbound Email XML Message (CWEmailOut) for each eligible order that was shipped or returned in the selected date range. Similarly, if you select the same date twice when using the Sending Internet Order Ship Confirmation (ESCF) option, the option generates an additional email notification or Outbound Email XML Message (CWEmailOut), regardless of the setting of this system control value. The Sending Internet Order Ship Confirmation (ESCF) does not check whether a shipment or return confirmation email was previously generated.
If you consolidate invoices: If you consolidate shipment invoices (based on the setting of the Consolidated Invoice (B49) system control value) or if you consolidate credit invoices (based on the setting of the Consolidated Credit Invoice (K06) system control value), then it is possible for the customer to receive more than one notification email in the same day. In this situation, each subsequent email generated the same day includes a cumulative list of the items shipped or returned against the same invoice number.
Example: |
You ship the first item of an order. The shipment confirmation email includes this item: 1. COMFORT GRIP GEL WRITER (PEN23/BLUE) Qty : 1
Later the same day, you ship an additional item on the same order. The second shipment confirmation email generated that day includes: 1. COMFORT GRIP GEL WRITER (PEN23/BLUE) Qty : 1
2. COMFORT GRIP GEL WRITER (PEN23/BLK) Qty : 1 |
If the Consolidated Invoice (B49) or the Consolidated Credit Invoice (K06) system control values are set to Y, the Invoice Consolidation Method (E29) system control value determines whether to consolidate shipments or returns for the order, or only for the same order ship-to. See the Invoice Consolidation Method (E29) system control value for a discussion and examples.
Holding invoices for multi-recipient orders: If both the E-Mail Shipment Return Confirmation Notification Immediately and the Hold Invoices for Multi-Recipient Orders (G07) system control value are set to Y, the billing async generates a separate return or shipment notification for each return or shipment, even though the invoices are consolidated.
Populate E-Commerce Effective Date Files (K23)
Purpose: Use this screen to indicate whether to create records in the EC Item Effective Date and EC SKU Effective Date files when you extract item and offer information for download to the web storefront.
MSR0052 CHANGE Change System Control Value 3/03/09 16:55:08
Description . : Populate Ecommerce Effective Date Files
Yes/No . . . . Y (Y,N) Narrative . . .
Application . : EDC Applic group . ALL Sequence# . . . 99
F3=Exit F12=Cancel |
Yes/No field: Enter Y in this field if you want the Downloading E-Commerce Offer Files (EOFR) and ECITMCH periodic function to create records in the EC Item Effective Date and EC SKU Effective Date files in your E-Commerce Staging Library (G56). These functions create records in these files for the most current Item Price and SKU Price records, plus any future Item and SKU Price records. Using this option enables you to download current and future prices to the web storefront in a single step, and to capture more complete pricing information in these files.
Set this system control value to N or leave it blank if you do not want to create records in the EC Item Effective Date and EC SKU Effective Date files.
This system control value does not control whether the Downloading E-Commerce Offer Files (EOFR) option and the ECITMCH periodic function create records in the other item and SKU price and offer-related files in the staging library. These other files include the EC Item Breakpoint, EC SKU Breakpoint, EC Offer SKU Link, and EC Offer Item Link.
For more information: See Downloading E-Commerce Offer Files (EOFR), especially the discussion and examples under Rules for Selecting SKU-Level and Future Pricing Information.
| Setting Up Warehouse Interface System Values | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Setting Up Interface Values |
IN03_16 CWDirect 18.0.x 2018 OTN