Chapter 57: CWCollaborate Interface
Purpose: The CWCollaborate interface provides a means of passing information between CWDirect and CWCollaborate, an application that provides automatic processing of drop ship orders.
CWCollaborate is an MICROS application that provides a collaborative, browser-based environment for retailers and vendors to share order, customer, and shipping information related to Drop Ship Processing, and to automatically process drop ship orders.
You can set up CWCollaborate for as many of your vendors as you wish, and at the same time use CWDirect drop ship purchase order or drop ship pick functionality for other vendors. You define the functionality used to process drop ship orders for each vendor on the Create Vendor (2 of 2) screen. See Working with Vendors (WVEN).
CWCollaborate is sold as a separate product. For more information about purchasing CWCollaborate, contact your MICROS representative.
Locate’s Supplier Direct Fulfillment module: See the Locate Supplier Direct Fulfillment Interface for information on fulfilling drop ship purchase orders through integration with Locate.
In this chapter:
• Overview
• CWCollaborate Interface Files
• CFS Transaction File (FLCSFT)
• PO Detail Drop Ship Order File (PODTDS)
• New Purchase Order File (FLCSPO)
• CSF Cancel Request File (FLCSCN)
• Purchase Order Update File (FLCSFS)
• CSF Vendor Download File (FLCSVD)
• Return Authorization File (FLCSRA)
• CSF Return Upload File (FLRART)
• CSF Cost Change File (FLCSCC)
• PO Address Change File (FLCSPO)
• A/P Invoice Upload File (APINUP)
• CDC Async and CDC Batch Jobs for CWCollaborate Integration
• Retail Brands/Retail Divisions
• CWCollaborate Drop Ship Purchase Order Cycle
• Creating Drop Ship Orders for CWCollaborate
• Sending Drop Ship Order Information to CWCollaborate
• Cancelling CWCollaborate Drop Ship Orders
• Changing Address and Cost Information
• Shipping CWCollaborate Drop Ship Orders
• Returning CWCollaborate Drop Ship Orders
• Creating and Sending CWCollaborate Return Authorizations
• Cancelling CWCollaborate Return Authorizations
• Accepting returns without an Authorization
• Uploading Invoices from CWCollaborate
• Tracking the Status of CWCollaborate Drop Ship Orders
• Special Handling on CWCollaborate Drop Ship Orders
• Reports
• Emails
• Setting up the CWCollaborate Interface
Although CWDirect allows you to process drop ship orders in several ways, manual intervention is required to complete the business processes. The CWCollaborate interface creates a bridge between CWDirect and the CWCollaborate application which allows you to exchange information with drop ship vendors via the internet, to track transactions throughout the process, and to automate the business process. When you use CWCollaborate, you do not need to intervene manually to complete transactions. The CWCollaborate interface automatically sends drop ship purchase order information to CWCollaborate, which makes the information available to your vendors, automatically creates packing slips when the vendors pull orders, and sends tracking and transaction information back to CWDirect. Optionally, you can use the CWCollaborate interface to process returns of drop ship orders and to process vendor’s invoices. The interface bridge contains files that CWDirect and CWCollaborate populate with information that needs to be passed between the two products.
The CWCollaborate interface:
• identifies vendors for whom you use CWCollaborate to process drop ship orders
• downloads initial vendor information for these vendors to CWCollaborate
• identifies retail brands you want CWCollaborate to display on screens and use for sorting information
• when you process drop ship orders (MDSP):
• automatically creates and sends drop ship purchase orders to CWCollaborate, where they can be accessed by your collaborative vendors
• CWCollaborate automatically sends email notifications to your vendors to inform them that there are purchase orders to be selected and fulfilled
• from order inquiry or PO inquiry (OIOM or MPOI):
• allows you to initiate a request to cancel the order
• CWCollaborate automatically sends email notification to your vendors informing them of the cancel request
• receives the vendor’s cancel response; automatically cancels the PO when the vendor accepts a cancel request
• when you create a return authorization:
• automatically sends RA information to CWCollaborate
• CWCollaborate automatically sends email notification to your vendors to inform them that there are return authorizations to be processed
• allows you to cancel an RA
• CWCollaborate automatically sends email notification to your vendor to inform them that an RA has been cancelled
• automatically credits the RA and updates the order when a vendor posts a return
• offers the option of allowing vendors to receive returns without return authorizations and:
• automatically creates and processes a return authorization
• receives return information; automatically creates and credits the RA and updates the order for the returned item
• tracks the status of CWCollaborate drop ship orders to identify when they have been:
• created in CWDirect and sent to CWCollaborate
• created in CWCollaborate but not yet selected (pulled) by the vendor for fulfillment
• updated with information entered by the vendor
• updated with information entered in CWDirect
• pulled by the vendor for fulfillment
• cancelled or had a cancel request denied
• held by the vendor
• shipped by the vendor
• updated with a return authorization in CWDirect
• updated by cancelling an RA
• updated with a return received and posted in CWCollaborate
• updated with PO cost changes
• updated with ship-to address changes on the PO
• when you process back order cards:
• allows you to generate backorder notices with a meaningful expected ship date based on Vendor lead days and Drop Ship Lead Days (H36)
• allows you, optionally, to send immediate backorder notices
• when the vendor submits invoices for drop ship orders, allows you to upload the invoices from CWCollaborate into CWDirect, matching the invoices to the purchase order detail lines
Locate’s Supplier Direct Fulfillment module: See the Locate Supplier Direct Fulfillment Interface for information on fulfilling drop ship purchase orders through integration with Locate.
The CWCollaborate interface files used to pass information from CWDirect to CWCollaborate are:
• CFS Transaction File (FLCSFT)
• PO Detail Drop Ship Order File (PODTDS)
• New Purchase Order File (FLCSPO)
• CSF Cancel Request File (FLCSCN)
• Purchase Order Update File (FLCSFS)
• CSF Vendor Download File (FLCSVD)
• Return Authorization File (FLCSRA)
• CSF Return Upload File (FLRART)
• CSF Cost Change File (FLCSCC)
• PO Address Change File (FLCSPO)
• A/P Invoice Upload File (APINUP)
This file records information passed to and from CWDirect and CWCollaborate. The CFS Transaction file is populated when:
• A CWDirect user requests a cancellation of a drop ship purchase order processed through the CWCollaborate interface.
• CWCollaborate receives the purchase order.
• A collaborative vendor selects a purchase order line for fulfillment, updates information on the purchase order, confirms or rejects a cancel request, puts the order line on hold, or ships a purchase order line.
• A CWDirect user creates an RA for a CWCollaborate order.
• A collaborative vendor selects the RA for processing.
• A CWDirect user cancels the RA.
• A collaborative vendor posts a return against an RA.
• A collaborative vendor posts a return without an RA (against a PO).
Field |
Description |
Company |
The company where the transaction took place. Alphanumeric, 3 positions. |
PO # |
The purchase order number associated with the transaction. Numeric, 7 positions. |
Seq # |
The purchase order sequence number. Numeric, 5 positions. |
Transaction date |
The date the transaction occurred. Numeric, 7 positions (CYYMMDD format). |
Transaction time |
The time the transaction occurred. Numeric, 6 positions (HHMMSS format). |
Transaction status |
The status of the transaction. E = Error B = Pending batch transfer C = Pending change transfer R = Pending RA transfer P = Processed U = Unprocessed Alphanumeric, 1 position. |
Transaction type |
The type of transaction. AP = A/P invoice received CC = Cancel request confirmed CJ = Cancel request rejected CR = Cancel request sent CG = Cost change PS = Drop ship PO confirmed PC = Drop ship PO created PM = Drop ship PO modified PU = Drop ship PO updated RC = Return auth cancelled RA = Return auth created RR = Return update received Alphanumeric, 2 positions. |
Transaction quantity |
The quantity associated with the transaction. Numeric, 7 positions. |
PO update type |
The type of update that occurred. A = Acknowledged D = Date change H = Held M = Maintenance acknowledged P = Pulled R = Released U = Unpulled Alphanumeric, 1 position. |
PO update message |
Purchase order update message associated with the transaction. Alphanumeric, 80 positions. |
PO update date |
The date when the purchase order was updated. Numeric, 7 positions (YCCMMDD format). |
Error message |
The error message associated with the transaction. You can review drop ship transaction errors in the Working with Drop Ship Errors (WDSE) menu option. Errors messages include: • Order detail not shipped • PODTDS record not found • Invalid transaction type • Invalid RA header • Invalid RA detail • RA header completed • Invalid return quantity • Invalid return reason • RA cancel transfer failed • Invalid loc for return • Receive/confirm error • Invalid email See Invoice Upload Errors for a list of possible errors related to the A/P invoice upload. Alphanumeric, 25 positions. |
PDS status |
The purchase order drop ship status. C = Cancelled D = Delivered H = Held I = In process P = Invoiced O = Open N = RA cancelled A = RA sent R = Returned E = Sent S = Shipped Alphanumeric, 1 position. |
Future date |
This field is currently not implemented. Numeric, 7 positions (CYYMMDD format). |
Future quantity |
This field is currently not implemented. Numeric, 7 positions. |
Future code |
This field is currently not implemented. Alphanumeric, 10 positions. |
Vendor # |
The vendor number associated with the transaction. Numeric, 7 positions. |
Tracking # |
The shipment tracking number associated with the transaction. Alphanumeric, 30 positions. |
Meter charge |
The shipment meter charge associated with the transaction. Numeric, 7 positions with a 2-place decimal. |
Package weight |
The shipment package weight associated with the transaction. Numeric, 7 positions with a 2-place decimal. |
Ship via |
The ship via code associated with the transaction. Numeric, 2 positions. |
Return date |
The date a PO line was returned. Numeric, 7 positions (CYYMMDD format). |
Return postage amount |
The postage amount associated with the return transaction. Numeric, 9 positions with a 2-place decimal. |
Return comment line 1 |
Return message. Alphanumeric, 80 positions. |
Return comment line 2 |
Return message. Alphanumeric, 80 positions. |
Return reason |
The reason for the return. Alphanumeric, 10 positions. |
Return reason description |
A description of the return reason. Alphanumeric, 40 positions. |
Vendor return # |
The vendor return number. Alphanumeric, 30 positions. |
RA # |
The return authorization number. Numeric, 3 positions. |
RA line # |
The return authorization line number. Numeric, 3 positions. |
AP invoice # |
The A/P invoice number. Alphanumeric, 11 positions. |
AP invoice line # |
The A/P invoice line number. Alphanumeric, 18 positions. |
AP invoice date |
The A/P invoice date. Numeric, 7 positions (CYYMMDD format). |
RDC AP invoice # |
The CWDirect A/P invoice number. Alphanumeric, 11 positions. |
RDC AP invoice line # |
The CWDirect A/P invoice line number. Numeric, 5 positions. |
PO Detail Drop Ship Order File (PODTDS)
This file records order number and purchase order information, sold-to and item information, original and revised due dates, drop ship status and additional information entered by the vendor for drop ship orders processed through CWCollaborate. This information is displayed on the Display P/O Drop Ship Screen.
Field |
Description |
Company |
The company associated with the purchase order detail line. Numeric, 3 positions. |
PO # |
The purchase order number assigned by the system when you process drop ship purchase orders. Numeric, 7 positions. |
Seq # |
The purchase order sequence number. Numeric, 5 positions. |
CSF sts |
The status of the purchase order detail line. blank = The drop ship purchase order is not flagged to be processed by CWCollaborate. C = Cancelled; The drop ship purchase order line has been cancelled. D = Delivered H = Held; The drop ship purchase order line is held by the vendor. I = In process; The drop ship purchase order line has been selected (pulled) by the vendor for fulfillment. P = Invoiced; The vendor has submitted an invoice for the shipment. O = Open; The drop ship purchase order line has been created in CWCollaborate but not yet selected by the vendor for fulfillment. N = RA cancelled; A return authorization has been cancelled for the purchase order line and sent to CWCollaborate. A = RA sent; A return authorization has been created for the purchase order line and sent to CWCollaborate. R = Returned; The drop ship purchase order returned merchandise has been received and posted by the vendor. When the vendor posts a return, the return is received and credited (if not already credited) in CWDirect. E = Sent; The drop ship purchase order has been created in CWDirect and sent to CWCollaborate. S = Shipped; The drop ship purchase order line has been shipped by the vendor. When the vendor ships the purchase order line, the line is closed in CWDirect, and the corresponding order line is also closed. |
|
Note: This field is not changed when you send PO cost change or address change information to CWCollaborate. Alphanumeric, 1 position. |
CSF exp del date |
The most recent date sent by the vendor indicating when the merchandise will ship. If the vendor has not revised the Original expected ship date, this field is blank. If a vendor revises the expected ship date, the system adds a message to the Additional info and Message fields; if the vendor has not entered a reason message when revising the ship date, the message Expected Ship Date Changed to MM/DD/YYYY displays in the CSF message field. If the vendor subsequently removes the revised expected ship date from the PO line, the revised expected ship date is removed from this field, and a message is added to the CSF message field; if the vendor has not entered a reason message, the message Revised ship date removed by vendor displays in the CSF message field. Note: The revised expected ship date on a drop ship purchase order does not update the expected ship date on the order line. Numeric, 7 positions (CYYMMDD format). |
CSF message |
The most recent text message sent from the vendor regarding the drop ship purchase order line. The vendor types this message on the status screen. Alphanumeric, 40 positions. |
Original del date |
The original due date on the purchase order. The original expected ship date is calculated by adding the lead days for the vendor item and the Drop ship lead days (H36) to the order date; however, if the Arrival date on the order is later than this date, the Arrival date is used as the Original expected ship date. Numeric, 7 positions (CYYMMDD format). |
Future date 2 |
This field is currently not implemented. Numeric, 7 positions (CYYMMDD format). |
Future y/n 1 |
This field is currently not implemented. Alphanumeric, 1 position. |
Future y/n 2 |
This field is currently not implemented. Alphanumeric, 1 position. |
Future text 1 |
This field is currently not implemented. Alphanumeric, 10 positions. |
Future text 2 |
This field is currently not implemented. Alphanumeric, 20 positions. |
Order # |
The order number associated with the purchase order. Numeric, 8 positions. |
Ship to # |
The order ship to number associated with the purchase order. Numeric, 3 positions. |
Seq # |
The purchase order detail sequence number associated with the purchase order line. Numeric, 5 positions. |
Vendor # |
The vendor number associated with the purchase order. Numeric, 7 positions. |
Cancel reason |
The cancellation reason code associated with the purchase order line. Numeric, 2 positions. |
New Purchase Order File (FLCSPO)
When you process CWCollaborate drop ship orders, CWDirect creates this file and sends it to CWCollaborate. Once the record is sent to CWCollaborate, the system automatically deletes the record from the file.
Field |
Description |
PO record type |
Indicates the type of information included in the transaction. When a new purchase order is sent to CWCollaborate, the system generates 4 messages: HEADER = Transaction header information. POHEAD = Purchase order header information. PODETL = Purchase order detail information. TRAILER = Transaction trailer information. Alphanumeric, 10 positions. |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
The CWDirect company code where the drop ship purchase order was processed. Alphanumeric, 15 positions. |
Sequence # |
System generated number. Numeric, 9 positions. |
PO data 1 - PO data 25 The contents of the transaction. The fields included in this message string are listed below. |
|
HEADER record type: |
|
Retailer ID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
Organization ID |
From the Company field in the Company file. 15 positions. |
Sequence # |
System generated number. 9 positions. |
Date stamp |
The date the new PO was created in CWDirect. YYYYMMDD format. 8 positions. |
Time stamp |
The time the new PO was created in CWDirect. HHMMSS format. 6 positions. |
POHEAD record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNum |
System generated number. 9 positions. |
PONum |
From the PO# field in the PO Header file. 15 positions. |
VendorNum |
From the Vendor # field in the PO Header file. 10 positions. |
DivisionID |
15 positions. |
SalesOrderNum |
From the Order # field in the PO Header file. 30 positions. |
SoldToID |
From the Cust # field in the Order Header file. 15 positions. |
SoldToPrefix |
From the Prefix field in the Customer Sold To file. 3 positions. |
SoldToName |
From the First name + Initial + Last name fields in the Customer Sold To file. 60 positions. |
SoldToSuffix |
From the Suffix field in the Customer Sold To file. 3 positions. |
SoldToApt |
From the Apartment field in the Customer Sold To file. 10 positions. |
SoldToAddr1 |
From the Street address field in the Customer Sold To file. 50 positions. |
SoldToAddr2 |
From the Address line 2 field in the Customer Sold To file. 50 positions. |
SoldToAddr3 |
From the Address line 3 field in the Customer Sold To file. 50 positions. |
SoldToAddr4 |
From the Address line 4 field in the Customer Sold To file. 50 positions. |
SoldToCity |
From the City field in the Customer Sold To file. 30 positions. |
SoldToStateCode |
From the State field in the Customer Sold To file. 2 positions. |
SoldToStateName |
From the Description field in the State file. 30 positions. |
SoldToZip |
From the Zip field in the Customer Sold To file. 10 positions. |
SoldToCountryCode |
From the Country field in the Customer Sold To file. 3 positions. |
SoldToCountryName |
From the Description field in the Country file. 30 positions. |
SoldToEmail |
From the Email field in the Customer Sold To file. 80 positions. |
SoldToCompany |
From the Company name field in the Customer Sold To file. 30 positions. |
SoldToTelephone |
From the Phone field in the Customer Sold To Phone # file. 20 positions. |
SoldToTelephoneExt |
From the CS# Extension field in the Customer Sold To Phone # file. 5 positions. |
ShipToPrefix |
From the: • Prefix field in the Order Ship To Address file, or • Prefix field in the Customer Ship To file, or • Prefix field in the Customer Sold To file. 3 positions. |
ShipToName |
From the: • First name + Initial + Last name fields in the Order Ship To Address file, or • First name + Initial + Last name fields in the Customer Ship To file, or • First name + Initial + Last name fields in the Customer Sold To file. 60 positions. |
ShipToSuffix |
From the: • Suffix field in the Order Ship To Address file, or • Suffix field in the Customer Ship To file, or • Suffix field in the Customer Sold To file. 3 positions. |
ShipToAppt |
From the: • Apartment field in the Order Ship To Address file, or • Apartment field in the Customer Ship To file, or • Apartment field in the Customer Sold To file. 10 positions. |
ShipToAddr1 |
From the: • Street address field in the Order Ship To Address file, or • Street address field in the Customer Ship To file, or • Street address field in the Customer Sold To file. 50 positions. |
ShipToAddr2 |
From the: • Address line 2 field in the Order Ship To Address file, or • Address line 2 field in the Customer Ship To file, or • Address line 2 field in the Customer Sold To file. 50 positions. |
ShipToAddr3 |
From the: • Address line 3 field in the Order Ship To Address file, or • Address line 3 field in the Customer Ship To file, or • Address line 3 field in the Customer Sold To file. 50 positions. |
ShipToAddr4 |
From the: • Address line 4 field in the Order Ship To Address file, or • Address line 4 field in the Customer Ship To file, or • Address line 4 field in the Customer Sold To file. 50 positions. |
ShipToCity |
From the: • City field in the Order Ship To Address file, or • City field in the Customer Ship To file, or • City field in the Customer Sold To file. 30 positions. |
ShipToStateCode |
From the: • State field in the Order Ship To Address file, or • State field in the Customer Ship To file, or • State field in the Customer Sold To file. 2 positions. |
ShipToStateName |
From the Description field in the State file. 30 positions. |
ShipToZip |
From the: • Zip field in the Order Ship To Address file, or • Zip field in the Customer Ship To file, or • Zip field in the Customer Sold To file. 10 positions. |
ShipToCountryCode |
From the: • Country field in the Order Ship To Address file, or • Country field in the Customer Ship To file, or • Country field in the Customer Sold To file. 3 positions. |
ShipToCountryName |
From the Description field in the Country file. 30 positions. |
ShipToEmail |
From the: • Email address field in the Order Ship To Address file, or • Email address field in the Customer Ship To file, or • Email field in the Customer Sold To file. 80 positions. |
ShipToCompany |
From the: • Company name field in the Order Ship To Address file, or • Company name field in the Customer Ship To file, or • Company name field in the Customer Sold To file. 30 positions. |
ShipToTele |
From the: • Phone field in the Customer Ship To Phone # file, or • Phone field in the Customer Sold To Phone # file. 20 positions. |
ShipToTeleExt |
From the: • CS# Extension field in the Customer Ship To Phone # file, or • CS# Extension field in the Customer Sold To Phone # file. 5 positions. |
Attention |
From the Contact name field in the Order Ship To file. 60 positions. |
SOPayMethod |
From the Description field in the Pay Type file. 30 positions. |
SOPaidAmt |
From the Amount collected field in the Order Payment Method file. 12 positions. |
SORefundBalDue |
From the Amount credited field in the Order Payment Method file. 12 positions. |
SOFreightChrg |
From the Freight field in the Order Ship To file. 12 positions. |
SOAdditionalFreight |
From the Add’l freight field in the Order Ship To file. 12 positions. |
SOAdditionalCharges |
From the Add’l charges field in the Order Ship To file. 12 positions. |
GiftOrderFlag |
From the Gift order field in the Order Ship To file. 1 position. |
SalesOrderNote1 |
The first OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote2 |
The second OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote3 |
The third OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote4 |
The fourth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote5 |
The fifth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote6 |
The sixth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote7 |
The seventh OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote8 |
The eighth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote9 |
The ninth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote10 |
The tenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote11 |
The eleventh OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote12 |
The twelfth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote13 |
The thirteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote14 |
The fourteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote15 |
The fifteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote16 |
The sixteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote17 |
The seventeenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote18 |
The eighteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote19 |
The nineteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote20 |
The twentieth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
GiftMsgNote1 |
The first OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote2 |
The second OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote3 |
The third OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote4 |
The fourth OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote5 |
The fifth OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
VendorNote1 |
The Note field in the Vendor Notes file whose Seq # is 1. 60 positions. |
VendorNote2 |
The Note field in the Vendor Notes file whose Seq # is 2. 60 positions. |
VendorNote3 |
The Note field in the Vendor Notes file whose Seq # is 3. 60 positions. |
VendorNote4 |
The Note field in the Vendor Notes file whose Seq # is 4. 60 positions. |
VendorNote5 |
The Note field in the Vendor Notes file whose Seq # is 5. 60 positions. |
POHeaderNote1 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote2 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote3 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote4 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote5 |
This field is currently not passed from CWDirect. 60 positions. |
BuyerCode |
From the Buyer field in the PO Header file. 10 positions. |
BuyerName |
From the Name field in the Buyer file. 30 positions. |
POEntryDate |
From the Entry date field in the PO Header file. 8 positions. |
POFreightCharge |
12 positions. |
NumberOfLines |
6 positions. |
DiscountAmt |
12 positions. |
DiscountPercentage |
From the Discount % field in the PO Header file. 5 positions. |
ShippingInstructions |
From the Shipping instructions field in the PO Header file. 40 positions. |
RetailerCurrencyCode |
From the Currency code field in the PO Header file. 3 positions. |
RetailerCurrencyDesc |
From the Currency description field in the Currency file. 30 positions. |
VendorCurrencyCode |
From the Currency code field in the Vendor file. 3 positions. |
VendorCurrencyDesc |
From the Currency description field in the Currency file. 30 positions. |
CurrencyRate |
From the Conversion rate field in the Currency file. 11 positions. |
TaxExemptNum |
From the Resale/Exempt # field in the Order Ship To file. 15 positions. |
PORetailOrderValue |
From the Price field in the Vendor Item file. 12 positions. |
POVendorOrderValue |
From the Price field in the Vendor Item file. 12 positions. |
ShipCompleteFlag |
From the Ship complete field in the Order Ship To file. 1 position. |
VendorName |
From the Name field in the Vendor file. 40 positions. |
VendorAddr1 |
From the Address line 1 field in the Vendor file. 50 positions. |
VendorAddr2 |
From the Address line 2 field in the Vendor file. 50 positions. |
VendorAddr3 |
From the Address line 3 field in the Vendor file. 50 positions. |
VendorAddr4 |
From the Address line 4 field in the Vendor file. 50 positions. |
VendorCity |
From the City field in the Vendor file. 30 positions. |
VendorStateCode |
From the State field in the Vendor file. 2 positions. |
VendorStateName |
From the Description field in the State file. 30 positions. |
VendorZip |
From the Zip field in the Vendor file. 10 positions. |
VendorCountryCode |
From the Description field in the Country file. 3 positions. |
VendorCountryName |
From the Country field in the Vendor file. 30 positions. |
VendorEmail |
From the Email address field in the Vendor file. 80 positions. |
VendorContact |
From the Contact name field in the Vendor file. 60 positions. |
VendorFax |
From the Fax number field in the Vendor file. 20 positions. |
VendorTelephone |
From the Telephone number field in the Vendor file. 20 positions. |
OrganizationDesc |
From the Description field in the Company file. 30 positions. |
DivisionDesc |
From the Description field in the Retail Brand file. 30 positions. |
OrderLevelTaxOnFreight |
12 positions. |
PODETL record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNum |
System generated number. 9 positions. |
PONumber |
From the PO# field in the PO Detail file. 15 positions. |
POLineNum |
From the Ln# field in the PO Detail file. 5 positions. |
InternalReference |
Combination of Company + PO# + Ln#. 20 positions. |
RetailerItemCode |
From the ITM number field in the PO Detail file. 48 positions. |
RetailerItemDesc |
From the Description field in the Item file. 50 positions. |
RetailerItemStyle |
From the ITM number in the SKU file. 20 positions. |
RetailerItemColor |
From the Element 1 field in the SKU file. 10 positions. |
RetailerItemSize |
From the Element 2 field in the SKU file. 10 positions. |
RetailerItemSize2 |
From the Element 3 field in the SKU file. 10 positions. |
VendorItemCode |
From the Item field in the PO Detail file. 48 positions. |
VendorItemDesc |
From the Description field in the Vendor Item file. 50 positions. |
ItemCodeUPC |
From the UPC type field in the Item UPC file. 48 positions. |
ItemDescUPC |
From the UPC field in the Item UPC file. 50 positions. |
ItemCodeEAN |
From the UPC type field in the Item UPC file whose value is E13 or E8. 48 positions. |
ItemDescEAN |
From the UPC field in the Item UPC file for UPC type E13 or E8. 50 positions. |
RetailerPOUOMCode |
From the UOM field in the PO Detail file. 3 positions. |
RetailerPOUOMRate |
12 positions. |
RetailerPOLineQuantity |
From the Order qty field in the PO Detail file. 7 positions. |
RetailerPOUnitPrice |
From the Price field in the PO Detail file. 12 positions. |
RetailerPOExtendedPrice |
Order qty x Price = RetailerPOExtendedPrice. 12 positions. |
RetailerPOExtendedTax |
12 positions. |
VendorPOUOMCode |
From the Vendor’s unit of measure field in the PO Detail file. 3 positions. |
VendorPOUOMRate |
12 positions. |
VendorPOLineQuantity |
From the Vendor order qty field in the PO Detail file. 7 positions. |
VendorPOUnitPrice |
From the Vendor price field in the PO Detail file. 12 positions. |
VendorPOExtendedPrice |
Vendor order qty x Vendor price = VendorPOExtendedPrice. 12 positions. |
VendorPOExtendedTax |
12 positions. |
POLineNote1 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote2 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote3 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote4 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote5 |
This field is currently not passed from CWDirect. 60 positions. |
POLineEntryDate |
From the Entry date field in the PO Detail file. 8 positions. |
CarrierCode |
From the Ship via field in the PO Detail file. 10 positions. |
ItemDueDate |
From the Due date field in the PO Detail file. 8 positions. |
CancelAfterDate |
From the Cancel date field in the PO Detail file. 8 positions. |
SalesOrderUnitPrice |
From the Price field in the Order Detail file. 12 positions. |
SalesOrderExtLineTax |
From the Tax field in the Order Detail file. 12 positions. |
SalesOrderExtLineGST |
From the GST field in the Order Detail file. 12 positions. |
SalesOrderExtLinePST |
From the PST field in the Order Detail file. 12 positions. |
SalesOrderExtLineFreight |
From the Freight charge field in the Order Detail file. 12 positions. |
SalesOrderExtLineHand |
From the Special handling $ field in the Order Detail file. 12 positions. |
SalesOrderLineNote1 |
The first OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote2 |
The second OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote3 |
The third OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote4 |
The fourth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote5 |
The fifth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote6 |
The sixth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote7 |
The seventh OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote8 |
The eighth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote9 |
The ninth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 10 |
The tenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 11 |
The eleventh OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 12 |
The twelfth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 13 |
The thirteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 14 |
The fourteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 15 |
The fifteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 16 |
The sixteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 17 |
The seventeenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 18 |
The eighteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 19 |
The nineteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 20 |
The twentieth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
CustomizationNote1 |
From the Label field and Input field in the Order Special Format file whose Seq # is 1. 60 positions. |
CustomizationNote2 |
From the Label field and Input field in the Order Special Format file whose Seq # is 2. 60 positions. |
CustomizationNote3 |
From the Label field and Input field in the Order Special Format file whose Seq # is 3. 60 positions. |
CustomizationNote4 |
From the Label field and Input field in the Order Special Format file whose Seq # is 4. 60 positions. |
CustomizationNote5 |
From the Label field and Input field in the Order Special Format file whose Seq # is 5. 60 positions. |
CustomizationNote6 |
From the Label field and Input field in the Order Special Format file whose Seq # is 6. 60 positions. |
CustomizationNote7 |
From the Label field and Input field in the Order Special Format file whose Seq # is 7. 60 positions. |
CustomizationNote8 |
From the Label field and Input field in the Order Special Format file whose Seq # is 8. 60 positions. |
CustomizationNote9 |
From the Label field and Input field in the Order Special Format file whose Seq # is 9. 60 positions. |
CustomizationNote10 |
From the Label field and Input field in the Order Special Format file whose Seq # is 10. 60 positions. |
GiftWrapFlag |
From the Gift wrap field in the Order Detail file. 1 position. |
ShipAloneFlag |
From the Ship alone field in the Item file. 1 position. |
CarrierName |
From the Shipper name field in the Ship Via file. 30 positions. |
VendorItemLeadDays |
From the Lead days field in the Vendor Item file. 5 positions. |
SalesOrderExtPrice |
Price x Qty ordered = SalesOrderExtPrice. 12 positions. |
POUOMConverFactor |
12 positions. |
The del_whse and its associated fields (del_whse_name, del_whse_addr1, del_whse_addr2, del_whse_addr3, del_whse_city, del_whse_state, del_whse_state_name, del_whse_postal_code, del_whse_country, del_whse_country_name, del_whse_phone, and del_whse_manager) represent the HDL assigned to the order line. An HDL warehouse represents a delivery service provider that provides “white glove” home delivery service. Instead of shipping products directly to the customer, the system sends the products to the HDL, who in turn, delivers the products to the customer. For example, you may wish to use a home delivery service for large items, such as furniture or appliances, that require someone to carry and set up the item in the customer’s home or business. The system only assigns an HDL to an order line if the Include HDL Warehouse Value on Order Detail (J54) system control value is set to Y. See HDL (Home Delivery Service) Processing for more information. |
|
del_whse |
A code for the HDL assigned to the order line. This is the HDL warehouse in the warehouse list associated with the order line that has the highest warehouse list priority. From the ODT Future use qty 1 field in the Order Detail file. 3 positions. |
del_whse_name |
The name of the HDL. From the Name field in the Warehouse file. 30 positions. |
del_whse_addr1 |
The street address of the HDL. From the Address field in the Warehouse file. 32 positions. |
del_whse_addr2 |
The second address line of the HDL. From the Address line 2 field in the Warehouse file. 32 positions. |
del_whse_addr3 |
The third address line of the HDL. From the Address line 3 field in the Warehouse file. 32 positions. |
del_whse_city |
The city for the HDL address. From the City field in the Warehouse file. 25 positions. |
del_whse_state |
The state for the HDL address. From the State field in the Warehouse file. 2 positions. |
del_whse_state_name |
The name of the state. From the Description field in the State file. 25 positions. |
del_whse_postal_code |
The postal code for the HDL address. From the Zip code field in the Warehouse file. 10 positions. |
del_whse_country |
The country code for the HDL address. From the RPR Country field in the Warehouse file. 3 positions. |
del_whse_country_name |
The name of the country. From the Description field in the Country file. 30 positions. |
del_whse_phone |
The phone number for the HDL. From the Phone field in the Warehouse file. 20 positions. |
del_whse_manager |
The name of the manager at the HDL. From the Manager field in the Warehouse file. 30 positions. |
TRAILER record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
System generated number. 9 positions. |
DateStamp |
The date the message was generated in YYYYMMDD format. 8 positions. |
TimeStamp |
The time the message was generated in HHMMSS format. 6 positions. |
POHeaderTotal |
The number of POHEAD strings included in the message. 7 positions. |
PODetailTotal |
The number of PODETL strings included in the message. 9 positions. |
RecordTotal |
The total number of records included in the message. 9 positions. |
CSF Cancel Request File (FLCSCN)
When you initiate a cancel request, CWDirect creates this file and sends it to CWCollaborate.
Field |
Description |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
From the Company field in the Company file. Alphanumeric, 15 positions. |
PO number |
From the PO# field in the PO Detail file. Alphanumeric, 15 positions. |
PO line number |
From the Ln# field in the PO Detail file. Numeric, 5 positions. |
Cancel request date |
From the Cancel date field in the PO Detail file. Numeric, 8 positions. |
Purchase Order Update File (FLCSFS)
When your vendor updates the status of a purchase order line, CWCollaborate creates the Purchase Order Update file. Each time a vendor updates another PO line, the information is appended to the file. CWDirect periodically looks for a new transaction file (which may contain multiple record types), and transfers the file to the iSeries.
Field |
Description |
Retailer ID |
Matches the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
Matches the Company field in the Company file. Alphanumeric, 15 positions. |
PO number |
Matches the PO # field in the PO Detail file. Alphanumeric, 15 positions. |
PO line number |
Matches the Ln# field in the PO Detail file. Numeric, 5 positions. |
Update status |
• POREL: PO released from hold • PODATE: PO revision date entered or changed • POHOLD: PO placed on hold • POMSG: PO reason description entered or changed • POPULL: PO pulled • CANREJ: Cancellation request rejected • POACK: PO acknowledgment sent • CANACP: Cancellation request accepted • POSHIP: PO shipped Alphanumeric, 10 positions. |
Internal reference |
OrganizationID + PONumber + POLineNumber Alphanumeric, 20 positions. |
Message |
Not passed from CWCollaborate. Alphanumeric, 80 positions. |
Revised due date |
Updates the Due date field in the PO Detail file. Numeric, 8 positions. |
Ship carrier code |
Not passed from CWCollaborate. Alphanumeric, 10 positions. |
Ship carrier name |
Not passed from CWCollaborate. Alphanumeric, 30 positions. |
Class of shipment |
Not passed from CWCollaborate. Alphanumeric, 10 positions. |
Freight charges |
Not passed from CWCollaborate. Numeric, 12 positions with a 4-place decimal. |
Shipment date |
Not passed from CWCollaborate. Numeric, 8 positions. |
Actual weight |
Not passed from CWCollaborate. Numeric, 12 positions with a 4-place decimal. |
Tracking # |
Not passed from CWCollaborate. Alphanumeric, 30 positions. |
Shipment quantity |
Not passed from CWCollaborate. Numeric, 7 positions. |
Unit of measure |
Not passed from CWCollaborate. Alphanumeric, 3 positions. |
CSF Vendor Download File (FLCSVD)
When you send vendor information to CWCollaborate using the Downloading CWCollaborate or Locate Vendor Information (ECSV) menu option, CWDirect creates the CSF Vendor Download file and sends it to CWCollaborate. The information in this file does not overwrite information for any vendor which already exists in CWCollaborate.
Field |
Description |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
From the Company field in the Company file. Alphanumeric, 15 positions. |
Vendor ID |
From the Vendor # field in the Vendor file. Alphanumeric, 10 positions. |
Vendor name |
From the Name field in the Vendor file. Alphanumeric, 40 positions. |
Vendor address 1 |
From the Address line 1 field in the Vendor file. Alphanumeric, 50 positions. |
Vendor address 2 |
From the Address line 2 field in the Vendor file. Alphanumeric, 50 positions. |
Vendor address 3 |
From the Address line 3 field in the Vendor file. Alphanumeric, 50 positions. |
Vendor address 4 |
From the Address line 4 field in the Vendor file. Alphanumeric, 50 positions. |
Vendor city |
From the City field in the Vendor file. Alphanumeric, 30 positions. |
Vendor state code |
From the State field in the Vendor file. Alphanumeric, 2 positions. |
Vendor state name |
From the Description field in the State file. Alphanumeric, 30 positions. |
Vendor postal code |
From the Zip field in the Vendor file. Alphanumeric, 10 positions. |
Vendor country code |
From the Country field in the Vendor file. Alphanumeric, 3 positions. |
Vendor country name |
From the Description field in the Country file. Alphanumeric, 30 positions. |
Vendor email |
From the Email address field in the Vendor file. Alphanumeric, 80 positions. |
Vendor contact |
From the Contact name field in the Vendor file. Alphanumeric, 60 positions. |
Vendor fax |
From the Fax number field in the Vendor file. Alphanumeric, 20 positions. |
Vendor telephone |
From the Telephone number field in the Vendor file. Alphanumeric, 20 positions. |
Return Authorization File (FLCSRA)
When you create a return authorization for a CWCollaborate drop ship order, CWDirect creates the Return Authorization file and sends it to CWCollaborate if you have flagged the vendor to send return information to CWCollaborate, and if you have flagged the return authorization to be sent to CWCollaborate.
Field |
Width |
Comments |
RA record type |
|
Indicates the type of information included in the transaction. When a new RA is sent to CWCollaborate, the system generates 4 messages: HEADER = Transaction header information. RAHEAD = Purchase order header information. RADETL = Purchase order detail information. TRAILER = Transaction trailer information. Alphanumeric, 10 positions. |
Retailer ID |
|
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
|
From the Company field in the Company file. Alphanumeric, 15 positions. |
Sequence # |
|
System generated number. Numeric, 9 positions. |
RA data 1 The contents of the transaction. The fields included in the message string are listed below. |
||
HEADER record type: |
||
RetailerID |
15 |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
15 |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
9 |
System generated number. 9 positions. |
DateStamp |
8 |
The date the message was generated. 8 positions. |
TimeStamp |
6 |
The time the message was generated. 6 positions. |
RAHEAD record type: |
||
RetailerID |
15 |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
15 |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
9 |
System generated number. 9 positions. |
RANumber |
30 |
From the RA Header file: Order # + Ship to # + RA#. 30 positions. |
SalesOrderNumber |
30 |
From the Order # field in the RA Header file. 30 positions. |
RACreateDate |
8 |
From the Date entered field in the RA Header file. 8 positions. |
RADETL record type: |
||
RetailerID |
15 |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
15 |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
9 |
System generated number. 9 positions. |
RANumber |
30 |
From the RA Header file: Order # + Ship to # + RA#. 30 positions. |
RALineNumber |
5 |
From the Line # field in the RA Detail file. 5 positions. |
PONumber |
15 |
From the PO # field in the PO Detail file. 15 positions. |
POLineNumber |
5 |
From the Ln# field in the PO Detail file. 5 positions. |
RALineQuantity |
7 |
From the Qty returned field in the RA Detail file. 7 positions. |
InternalReference |
20 |
Company + PONumber + POLineNumber + RALineQuantity + ReturnReason. 20 positions. |
ReturnReasonDescription |
30 |
From the Description field in the Return Reason file. 30 positions. |
ReturnReason |
3 |
From the Return reason code field in the RA Detail file. Right-aligned and zero-filled. 3 positions. |
TRAILER record type: |
||
RetailerID |
15 |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
15 |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
9 |
System generated number. 9 positions. |
DateStamp |
8 |
The date the message was generated. 8 positions. |
TimeStamp |
6 |
The time the message was generated. 6 positions. |
When you delete a return authorization which has been sent to CWCollaborate, CWDirect creates the Cancel RA file and sends it to CWCollaborate.
If multiple return lines are cancelled for an RA, CWDirect sends one CSF RA Cancel file to CWCollaborate containing all of the cancelled return lines. However, if multiple RAs are cancelled, CWDirect sends a separate CSF RA Cancel file for each cancelled RA.
Field |
Description |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
From the Company field in the Company file. Alphanumeric, 15 positions. |
PO number |
From the PO# field in the PO Detail file. Alphanumeric, 15 positions. |
PO line number |
From the Ln# field in the PO Detail file. Numeric, 5 positions. |
RA number |
From the RA Detail file: Order # + Ship to # + Line #, separated by hyphens; for example 00008071-001-002. Alphanumeric, 30 positions. |
RA line number |
From the Line # field in the RA Detail file. Numeric, 5 positions. |
RA cancel quantity |
From the Qty returned field in the RA Detail file. Numeric, 7 positions. |
RA cancel date |
From the Return date field in the RA Detail file. Numeric, 8 positions. |
CSF Return Upload File (FLRART)
When your vendor receives and posts a return against an RA, or receives and posts a return without an RA, CWCollaborate creates the CSF Return Upload file. Each time a vendor posts another return, the information is appended to the file. CWDirect periodically looks for a new transaction file (which may contain multiple record types), and transfers the file to the iSeries.
Field |
Description |
Retailer ID |
Matches the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
Matches the Company field in the Company file. Alphanumeric, 15 positions. |
PO number |
Matches the PO# field in the PO Detail file. Alphanumeric, 15 positions. |
PO line number |
Matches the Ln# field in the PO Detail file. Numeric, 5 positions. |
Vendor return number |
Alphanumeric, 30 positions. |
RA number |
Matches the RA # field in the RA Detail file. Alphanumeric, 30 positions. |
RA line number |
Matches the Line # field in the RA Detail file. Numeric, 5 positions. |
Return quantity |
Updates the Qty returned field in the RA Detail file. Numeric, 7 positions. |
Return reason |
Updates the Return reason code field in the RA Detail file. Alphanumeric, 10 positions. |
Return reason description |
Matches the Description field in the Return Reason file. Alphanumeric, 40 positions. |
Return postage |
Numeric, 9 positions with a 2-place decimal. |
Return comment line 1 |
Alphanumeric, 80 positions. |
Return comment line 2 |
Alphanumeric, 80 positions. |
Return date |
Updates the Return date field in the RA Detail file. Numeric, 8 positions. |
Internal reference |
Alphanumeric, 20 positions. |
When you update the Cost field on the PO Maintenance - Change PO Detail Screen, CWDirect creates the PO Cost Change file and sends it to CWCollaborate.
Field |
Description |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
From the Company field in the Company file. Alphanumeric, 15 positions. |
PO number |
From the PO# field in the PO Detail file. Alphanumeric, 15 positions. |
PO line number |
From the Ln# field in the PO Detail file. Numeric, 5 positions. |
Retailer unit price |
From the Price field in the PO Detail file. Numeric, 12 positions with a 4-place decimal. |
Retailer extend price |
From the PO Detail file: Price x Order qty = Retailer_Extended_Price. Numeric, 12 positions with a 4-place decimal. |
Vendor unit price |
From the Vendor price field in the PO Detail file. Numeric, 12 positions with a 4-place decimal. |
Vendor extend price |
From the PO Detail file: Vendor price x Vendor order qty = Vendor_Extended_Price. Numeric, 12 positions with a 4-place decimal. |
PO Address Change File (FLCSPO)
When you update the ship to address on an order which includes a CWCollaborate drop ship item, CWDirect creates the PO Address Change file and sends it to CWCollaborate.
Field |
Description |
PO record type |
Indicates the type of information included in the transaction. When a PO address change is sent to CWCollaborate, the system generates 4 messages: HEADER = Transaction header information. POHEAD = Purchase order header information. PODETL = Purchase order detail information. TRAILER = Transaction trailer information. Alphanumeric, 10 positions. |
Retailer ID |
From the CDC Retailer ID (H15) system control value. Alphanumeric, 15 positions. |
Organization ID |
The CWDirect company code where the drop ship purchase order was processed. Alphanumeric, 15 positions. |
Sequence # |
System generated number. Numeric, 9 positions. |
PO data 1 - PO data 25 The contents of the transaction. The fields included in this text string are listed below. |
|
HEADER record type: |
|
Retailer ID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
Organization ID |
From the Company field in the Company file. 15 positions. |
Sequence # |
System generated number. 9 positions. |
Date stamp |
The date the PO address change was created in CWDirect. YYYYMMDD format. 8 positions. |
Time stamp |
The time the PO address change was created in CWDirect. HHMMSS format. 6 positions. |
POHEAD record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNum |
System generated number. 9 positions. |
PONum |
From the PO# field in the PO Header file. 15 positions. |
VendorNum |
From the Vendor # field in the PO Header file. 10 positions. |
DivisionID |
15 positions. |
SalesOrderNum |
From the Order # field in the PO Header file. 30 positions. |
SoldToID |
From the Cust # field in the Order Header file. 15 positions. |
SoldToPrefix |
From the Prefix field in the Customer Sold To file. 3 positions. |
SoldToName |
From the First name + Initial + Last name fields in the Customer Sold To file. 60 positions. |
SoldToSuffix |
From the Suffix field in the Customer Sold To file. 3 positions. |
SoldToApt |
From the Apartment field in the Customer Sold To file. 10 positions. |
SoldToAddr1 |
From the Street address field in the Customer Sold To file. 50 positions. |
SoldToAddr2 |
From the Address line 2 field in the Customer Sold To file. 50 positions. |
SoldToAddr3 |
From the Address line 3 field in the Customer Sold To file. 50 positions. |
SoldToAddr4 |
From the Address line 4 field in the Customer Sold To file. 50 positions. |
SoldToCity |
From the City field in the Customer Sold To file. 30 positions. |
SoldToStateCode |
From the State field in the Customer Sold To file. 2 positions. |
SoldToStateName |
From the Description field in the State file. 30 positions. |
SoldToZip |
From the Zip field in the Customer Sold To file. 10 positions. |
SoldToCountryCode |
From the Country field in the Customer Sold To file. 3 positions. |
SoldToCountryName |
From the Description field in the Country file. 30 positions. |
SoldToEmail |
From the Email field in the Customer Sold To file. 80 positions. |
SoldToCompany |
From the Company name field in the Customer Sold To file. 30 positions. |
SoldToTelephone |
From the Phone field in the Customer Sold To Phone # file. 20 positions. |
SoldToTelephoneExt |
From the CS# Extension field in the Customer Sold To Phone # file. 5 positions. |
ShipToPrefix |
From the: • Prefix field in the Order Ship To Address file, or • Prefix field in the Customer Ship To file, or • Prefix field in the Customer Sold To file. 3 positions. |
ShipToName |
From the: • First name + Initial + Last name fields in the Order Ship To Address file, or • First name + Initial + Last name fields in the Customer Ship To file, or • First name + Initial + Last name fields in the Customer Sold To file. 60 positions. |
ShipToSuffix |
From the: • Suffix field in the Order Ship To Address file, or • Suffix field in the Customer Ship To file, or • Suffix field in the Customer Sold To file. 3 positions. |
ShipToAppt |
From the: • Apartment field in the Order Ship To Address file, or • Apartment field in the Customer Ship To file, or • Apartment field in the Customer Sold To file. 10 positions. |
ShipToAddr1 |
From the: • Street address field in the Order Ship To Address file, or • Street address field in the Customer Ship To file, or • Street address field in the Customer Sold To file. 50 positions. |
ShipToAddr2 |
From the: • Address line 2 field in the Order Ship To Address file, or • Address line 2 field in the Customer Ship To file, or • Address line 2 field in the Customer Sold To file. 50 positions. |
ShipToAddr3 |
From the: • Address line 3 field in the Order Ship To Address file, or • Address line 3 field in the Customer Ship To file, or • Address line 3 field in the Customer Sold To file. 50 positions. |
ShipToAddr4 |
From the: • Address line 4 field in the Order Ship To Address file, or • Address line 4 field in the Customer Ship To file, or • Address line 4 field in the Customer Sold To file. 50 positions. |
ShipToCity |
From the: • City field in the Order Ship To Address file, or • City field in the Customer Ship To file, or • City field in the Customer Sold To file. 30 positions. |
ShipToStateCode |
From the: • State field in the Order Ship To Address file, or • State field in the Customer Ship To file, or • State field in the Customer Sold To file. 2 positions. |
ShipToStateName |
From the Description field in the State file. 30 positions. |
ShipToZip |
From the: • Zip field in the Order Ship To Address file, or • Zip field in the Customer Ship To file, or • Zip field in the Customer Sold To file. 10 positions. |
ShipToCountryCode |
From the: • Country field in the Order Ship To Address file, or • Country field in the Customer Ship To file, or • Country field in the Customer Sold To file. 3 positions. |
ShipToCountryName |
From the Description field in the Country file. 30 positions. |
ShipToEmail |
From the: • Email address field in the Order Ship To Address file, or • Email address field in the Customer Ship To file, or • Email field in the Customer Sold To file. 80 positions. |
ShipToCompany |
From the: • Company name field in the Order Ship To Address file, or • Company name field in the Customer Ship To file, or • Company name field in the Customer Sold To file. 30 positions. |
ShipToTele |
From the: • Phone field in the Customer Ship To Phone # file, or • Phone field in the Customer Sold To Phone # file. 20 positions. |
ShipToTeleExt |
From the: • CS# Extension field in the Customer Ship To Phone # file, or • CS# Extension field in the Customer Sold To Phone # file. 5 positions. |
Attention |
From the Contact name field in the Order Ship To file. 60 positions. |
SOPayMethod |
From the Description field in the Pay Type file. 30 positions. |
SOPaidAmt |
From the Amount collected field in the Order Payment Method file. 12 positions. |
SORefundBalDue |
From the Amount credited field in the Order Payment Method file. 12 positions. |
SOFreightChrg |
From the Freight field in the Order Ship To file. 12 positions. |
SOAdditionalFreight |
From the Add’l freight field in the Order Ship To file. 12 positions. |
SOAdditionalCharges |
From the Add’l charges field in the Order Ship To file. 12 positions. |
GiftOrderFlag |
From the Gift order field in the Order Ship To file. 1 position. |
SalesOrderNote1 |
The first OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote2 |
The second OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote3 |
The third OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote4 |
The fourth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote5 |
The fifth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote6 |
The sixth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote7 |
The seventh OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote8 |
The eighth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote9 |
The ninth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote10 |
The tenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote11 |
The eleventh OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote12 |
The twelfth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote13 |
The thirteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote14 |
The fourteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote15 |
The fifteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote16 |
The sixteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote17 |
The seventeenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote18 |
The eighteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote19 |
The nineteenth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderNote20 |
The twentieth OMS message field in the Order Messages file, whose Print? field is P or B. 60 positions. |
GiftMsgNote1 |
The first OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote2 |
The second OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote3 |
The third OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote4 |
The fourth OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
GiftMsgNote5 |
The fifth OMS message field in the Order Messages file, whose Print? field is G. 60 positions. |
VendorNote1 |
The Note field in the Vendor Notes file whose Seq # is 1. 60 positions. |
VendorNote2 |
The Note field in the Vendor Notes file whose Seq # is 2. 60 positions. |
VendorNote3 |
The Note field in the Vendor Notes file whose Seq # is 3. 60 positions. |
VendorNote4 |
The Note field in the Vendor Notes file whose Seq # is 4. 60 positions. |
VendorNote5 |
The Note field in the Vendor Notes file whose Seq # is 5. 60 positions. |
POHeaderNote1 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote2 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote3 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote4 |
This field is currently not passed from CWDirect. 60 positions. |
POHeaderNote5 |
This field is currently not passed from CWDirect. 60 positions. |
BuyerCode |
From the Buyer field in the PO Header file. 10 positions. |
BuyerName |
From the Name field in the Buyer file. 30 positions. |
POEntryDate |
From the Entry date field in the PO Header file. 8 positions. |
POFreightCharge |
12 positions. |
NumberOfLines |
6 positions. |
DiscountAmt |
12 positions. |
DiscountPercentage |
From the Discount % field in the PO Header file. 5 positions. |
ShippingInstructions |
From the Shipping instructions field in the PO Header file. 40 positions. |
RetailerCurrencyCode |
From the Currency code field in the PO Header file. 3 positions. |
RetailerCurrencyDesc |
From the Currency description field in the Currency file. 30 positions. |
VendorCurrencyCode |
From the Currency code field in the Vendor file. 3 positions. |
VendorCurrencyDesc |
From the Currency description field in the Currency file. 30 positions. |
CurrencyRate |
From the Conversion rate field in the Currency file. 11 positions. |
TaxExemptNum |
From the Resale/Exempt # field in the Order Ship To file. 15 positions. |
PORetailOrderValue |
From the Price field in the Vendor Item file. 12 positions. |
POVendorOrderValue |
From the Price field in the Vendor Item file. 12 positions. |
ShipCompleteFlag |
From the Ship complete field in the Order Ship To file. 1 position. |
VendorName |
From the Name field in the Vendor file. 40 positions. |
VendorAddr1 |
From the Address line 1 field in the Vendor file. 50 positions. |
VendorAddr2 |
From the Address line 2 field in the Vendor file. 50 positions. |
VendorAddr3 |
From the Address line 3 field in the Vendor file. 50 positions. |
VendorAddr4 |
From the Address line 4 field in the Vendor file. 50 positions. |
VendorCity |
From the City field in the Vendor file. 30 positions. |
VendorStateCode |
From the State field in the Vendor file. 2 positions. |
VendorStateName |
From the Description field in the State file. 30 positions. |
VendorZip |
From the Zip field in the Vendor file. 10 positions. |
VendorCountryCode |
From the Description field in the Country file. 3 positions. |
VendorCountryName |
From the Country field in the Vendor file. 30 positions. |
VendorEmail |
From the Email address field in the Vendor file. 80 positions. |
VendorContact |
From the Contact name field in the Vendor file. 60 positions. |
VendorFax |
From the Fax number field in the Vendor file. 20 positions. |
VendorTelephone |
From the Telephone number field in the Vendor file. 20 positions. |
OrganizationDesc |
From the Description field in the Company file. 30 positions. |
DivisionDesc |
From the Description field in the Retail Brand file. 30 positions. |
OrderLevelTaxOnFreight |
12 positions. |
PODETL record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNum |
System generated number. 9 positions. |
PONumber |
From the PO# field in the PO Detail file. 15 positions. |
POLineNum |
From the Ln# field in the PO Detail file. 5 positions. |
InternalReference |
Combination of Company + PO# + Ln#. 20 positions. |
RetailerItemCode |
From the ITM number field in the PO Detail file. 48 positions. |
RetailerItemDesc |
From the Description field in the Item file. 50 positions. |
RetailerItemStyle |
From the ITM number in the SKU file. 20 positions. |
RetailerItemColor |
From the Element 1 field in the SKU file. 10 positions. |
RetailerItemSize |
From the Element 2 field in the SKU file. 10 positions. |
RetailerItemSize2 |
From the Element 3 field in the SKU file. 10 positions. |
VendorItemCode |
From the Item field in the PO Detail file. 48 positions. |
VendorItemDesc |
From the Description field in the Vendor Item file. 50 positions. |
ItemCodeUPC |
From the UPC type field in the Item UPC file. 48 positions. |
ItemDescUPC |
From the UPC field in the Item UPC file. 50 positions. |
ItemCodeEAN |
From the UPC type field in the Item UPC file whose value is E13 or E8. 48 positions. |
ItemDescEAN |
From the UPC field in the Item UPC file for UPC type E13 or E8. 50 positions. |
RetailerPOUOMCode |
From the UOM field in the PO Detail file. 3 positions. |
RetailerPOUOMRate |
12 positions. |
RetailerPOLineQuantity |
From the Order qty field in the PO Detail file. 7 positions. |
RetailerPOUnitPrice |
From the Price field in the PO Detail file. 12 positions. |
RetailerPOExtendedPrice |
Order qty x Price = RetailerPOExtendedPrice. 12 positions. |
RetailerPOExtendedTax |
12 positions. |
VendorPOUOMCode |
From the Vendor’s unit of measure field in the PO Detail file. 3 positions. |
VendorPOUOMRate |
12 positions. |
VendorPOLineQuantity |
From the Vendor order qty field in the PO Detail file. 7 positions. |
VendorPOUnitPrice |
From the Vendor price field in the PO Detail file. 12 positions. |
VendorPOExtendedPrice |
Vendor order qty x Vendor price = VendorPOExtendedPrice. 12 positions. |
VendorPOExtendedTax |
12 positions. |
POLineNote1 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote2 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote3 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote4 |
This field is currently not passed from CWDirect. 60 positions. |
POLineNote5 |
This field is currently not passed from CWDirect. 60 positions. |
POLineEntryDate |
From the Entry date field in the PO Detail file. 8 positions. |
CarrierCode |
From the Ship via field in the PO Detail file. 10 positions. |
ItemDueDate |
From the Due date field in the PO Detail file. 8 positions. |
CancelAfterDate |
From the Cancel date field in the PO Detail file. 8 positions. |
SalesOrderUnitPrice |
From the Price field in the Order Detail file. 12 positions. |
SalesOrderExtLineTax |
From the Tax field in the Order Detail file. 12 positions. |
SalesOrderExtLineGST |
From the GST field in the Order Detail file. 12 positions. |
SalesOrderExtLinePST |
From the PST field in the Order Detail file. 12 positions. |
SalesOrderExtLineFreight |
From the Freight charge field in the Order Detail file. 12 positions. |
SalesOrderExtLineHand |
From the Special handling $ field in the Order Detail file. 12 positions. |
SalesOrderLineNote1 |
The first OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote2 |
The second OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote3 |
The third OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote4 |
The fourth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote5 |
The fifth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote6 |
The sixth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote7 |
The seventh OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote8 |
The eighth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote9 |
The ninth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 10 |
The tenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 11 |
The eleventh OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 12 |
The twelfth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 13 |
The thirteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 14 |
The fourteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 15 |
The fifteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 16 |
The sixteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 17 |
The seventeenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 18 |
The eighteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 19 |
The nineteenth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
SalesOrderLineNote 20 |
The twentieth OLM message field in the Order Line Messages file, whose Print? field is P or B. 60 positions. |
CustomizationNote1 |
From the Label field and Input field in the Order Special Format file whose Seq # is 1. 60 positions. |
CustomizationNote2 |
From the Label field and Input field in the Order Special Format file whose Seq # is 2. 60 positions. |
CustomizationNote3 |
From the Label field and Input field in the Order Special Format file whose Seq # is 3. 60 positions. |
CustomizationNote4 |
From the Label field and Input field in the Order Special Format file whose Seq # is 4. 60 positions. |
CustomizationNote5 |
From the Label field and Input field in the Order Special Format file whose Seq # is 5. 60 positions. |
CustomizationNote6 |
From the Label field and Input field in the Order Special Format file whose Seq # is 6. 60 positions. |
CustomizationNote7 |
From the Label field and Input field in the Order Special Format file whose Seq # is 7. 60 positions. |
CustomizationNote8 |
From the Label field and Input field in the Order Special Format file whose Seq # is 8. 60 positions. |
CustomizationNote9 |
From the Label field and Input field in the Order Special Format file whose Seq # is 9. 60 positions. |
CustomizationNote10 |
From the Label field and Input field in the Order Special Format file whose Seq # is 10. 60 positions. |
GiftWrapFlag |
From the Gift wrap field in the Order Detail file. 1 position. |
ShipAloneFlag |
From the Ship alone field in the Item file. 1 position. |
CarrierName |
From the Shipper name field in the Ship Via file. 30 positions. |
VendorItemLeadDays |
From the Lead days field in the Vendor Item file. 5 positions. |
SalesOrderExtPrice |
Price x Qty ordered = SalesOrderExtPrice. 12 positions. |
POUOMConverFactor |
12 positions. |
SUBTOTAL record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNum |
System generated number. 9 positions. |
VendorNumber |
From the Vendor # field in the PO Header file. 10 positions. |
VendorPOCount |
The number of POs included in this message. 7 positions. |
VendorPOLineCount |
The number of PO lines included in this message. 9 positions. |
TRAILER record type: |
|
RetailerID |
From the CDC Retailer ID (H15) system control value. 15 positions. |
OrganizationID |
From the Company field in the Company file. 15 positions. |
SequenceNumber |
System generated number. 9 positions. |
DateStamp |
The date the message was generated in YYYYMMDD format. 8 positions. |
TimeStamp |
The time the message was generated in HHMMSS format. 6 positions. |
POHeaderTotal |
The number of POHEAD strings included in the message. 7 positions. |
PODetailTotal |
The number of PODETL strings included in the message. 9 positions. |
RecordTotal |
The total number of records included in the message. 9 positions. |
A/P Invoice Upload File (APINUP)
When the vendor submits an A/P invoice, CWDirect creates records in this file before creating the actual A/P invoices. See Working with A/P Invoice Upload Errors (WAPU) for information.
Field Name |
Comments |
Record type |
Indicates the type of information included in the transaction. When an invoice is received from CWCollaborate, the system receives 2 messages: RECORD01 = Invoice header information. RECORD02 = Invoice detail information. Alphanumeric, 10 positions. |
Interface type |
CDC defaults. Alphanumeric, 5 positions. |
Seq # |
System generated number. Numeric, 7 positions. |
Co# |
Updates the Company field in the PO Receipt file. Numeric, 3 positions. |
Vendor # |
Numeric, 7 positions. |
Invoice # |
Updates the PO # field in the PO Receipt file. Alphanumeric, 11 positions. |
Sts |
Remains blank. Alphanumeric, 1 position. |
APU upload record 1 - 2 The contents of the transaction. The fields included in this text string are listed below. |
|
Invoice_Header record type: |
|
InterfaceType |
CDC defaults. 5 positions. |
SequenceNumber |
System generated number. Right-aligned and 0 filled. 7 positions. |
CompanyNumber |
Updates the Company field in the PO Receipt file. 3 positions. |
VendorNumber |
7 positions. |
InvoiceNumber |
Updates the PO # field in the PO Receipt file. 11 positions. |
Status |
Blank filled. 1 position. |
PONumber |
0000000 displays. Right-aligned and 0 filled. 7 positions. |
DebitCreditIndicator |
DB = Debit CR = Credit 2 positions. |
RemitToName |
30 positions. |
RemitToAddress1 |
32 positions. |
RemitToAddress2 |
32 positions. |
RemitToAddress3 |
32 positions. |
RemitToAddress4 |
32 positions. |
RemitToCity |
25 positions. |
RemitToStateCode |
2 positions. |
RemitToPostalCode |
10 positions. |
RemitToCountryCode |
3 positions. |
RemitToEmail |
50 positions. |
FreightAmount |
Right-aligned and 0 filled. 11 positions. |
HandlingAmount |
Right-aligned and 0 filled. 11 positions. |
OtherAmount |
Right-aligned and 0 filled. 11 positions. |
InvoiceDate |
Updates the Receipt date field in the PO Receipt file. 8 positions. |
GrossDays |
Right-aligned and 0 filled. 3 positions. |
NetDueDays |
Right-aligned and 0 filled. 3 positions. |
DiscountPercent |
Right-aligned and 0 filled. 5 positions. |
HoldFlag |
1 position. |
TermsCode |
Right-aligned and 0 filled. 2 positions. |
User |
10 positions. |
Invoice_Detail record type: |
|
InterfaceType |
CDC defaults. 5 positions. |
SequenceNumber |
System generated number. Right-aligned and 0 filled. 7 positions. |
CompanyNumber |
Updates the Company field in the PO Receipt file. 3 positions. |
VendorNumber |
7 positions. |
InvoiceNumber |
Updates the PO # field in the PO Receipt file. 11 positions. |
Status |
Blank filled. 1 position. |
PONumber |
Updates the PO # field in the PO Receipt file. 7 positions. |
POLineNumber |
Updates the Seq # field in the PO Receipt file. Right-aligned and 0 filled. 5 positions. |
InvoiceLineNumber |
Right-aligned and 0 filled. 18 positions. |
FreightAmount |
Right-aligned and 0 filled. 11 positions. |
HandlingAmount |
Right-aligned and 0 filled. 11 positions. |
OtherAmount |
Right-aligned and 0 filled. 11 positions. |
DiscountAmount |
Right-aligned and 0 filled. 11 positions. |
Cost |
Right-aligned and 0 filled. 11 positions. |
Units |
Right-aligned and 0 filled. 7 positions. |
ItemNumber |
12 positions. |
SKUCode |
14 positions. |
VendorItemNumber |
20 positions. |
MiscDebitCreditFlag |
1 position. |
UnitDiscountAmount1 |
Updates the Unit discount amt 1 field in the PO Receipt file. Right-aligned and 0 filled. 9 positions. |
UnitDiscountAmount2 |
Updates the Unit discount amt 2 field in the PO Receipt file. Right-aligned and 0 filled. 9 positions. |
UnitDiscountAmount3 |
Updates the Unit discount amt 3 field in the PO Receipt file. Right-aligned and 0 filled. 9 positions. |
UnitDiscountPercent1 |
Updates the Unit discount pct 1 field in the PO Receipt file. Right-aligned and 0 filled. 5 positions. |
UnitDiscountPercent2 |
Updates the Unit discount pct 2 field in the PO Receipt file. Right-aligned and 0 filled. 5 positions. |
UnitDiscountPercent3 |
Updates the Unit discount pct 3 field in the PO Receipt file. Right-aligned and 0 filled. 5 positions. |
ShortNote |
25 positions. |
CDC Async and CDC Batch Jobs for CWCollaborate Integration
CWDirect creates and sends new drop ship purchase order information and new vendor information to CWCollaborate through batch jobs. The transfer takes place in two steps:
• CWDirect processes the information using the DROP_SHIP job.
• CWDirect sends the information to CWCollaborate using the XMT_TO_CDC job. When the XMT_TO_CDC job is completed, the record is deleted from your screen.
Cancel requests, purchase order update transactions, return authorizations, return authorization cancels, completed return updates, purchase order changes, and invoices are processed in CWDirect as background (asynchronous) jobs. These include:
Files sent to CWCollaborate:
• Cancel requests
• Return authorizations
• RA cancellations
• PO cost changes
• Order address changes
Files received from CWCollaborate:
• Purchase order updates:
• Cancel responses
• Updates to PO status (pulled, held, released from hold, expected ship date revised)
• Shipment confirmations
• Return updates
• A/P invoices
The async job dedicated to collaborate transactions is the CDC background job, which can be started or stopped using the WMS Background Jobs (WPBJ) menu option. The CDC job should be stopped and started each day. The periodic function (program name MSR0949) that starts the system background jobs and the periodic function (program name MSR0954) that ends the system background jobs also start and end the CDC background job.
The CDC job functions in the same manner whether you are transferring files via File Transport Mechanisms: FTP Codes or via File Transport Mechanisms: MQSeries queues.
Cancel requests, return authorizations, RA cancellations, PO cost changes and address changes are processed in two steps:
• The CDC job processes the information in CWDirect
• The job sends the information to CWCollaborate via file transport mechanism FTP or IBM MQSeries® 1, depending on the setting of your system control value setting in the Communications protocol field of the Drop Ship Integration Values Screen (H20).
When sending a file to CWCollaborate, the job passes the iSeries system date, not the date the job was started.
Purchase order updates, return updates, and A/P invoice updates are processed when the CDC job retrieves information which has been transferred from CWCollaborate to CWDirect. If you are using MQSeries message queues, the CDC job reads purchase order update information directly from the queue. If you are using FTP as a transfer mechanism, the job read purchase order update information via the WakeupLoader, which polls the CWCollaborate Outbox.
For troubleshooting problems with the CDC async, see Troubleshooting the CDC Async job.
Note: These jobs also support the Locate Supplier Direct Fulfillment Interface.
Retail Brands/Retail Divisions
Retail brands and descriptions associated with the source code of an order header are passed to CWCollaborate each time purchase orders are sent. Retail brands appear on CWCollaborate screens as Retail divisions. In CWCollaborate, you can use retail divisions to:
• restrict the display of information to the selected division.
• specify a logo, packing slip messages, and a stationery type for a retail division’s packing slips and a logo for RA forms
• specify separate email addresses for each retail division, which CWCollaborate uses when sending status update, Return notification (error) and contact email
• set parameters for the display of Overview screens for each retail division in CWCollaborate.
You create Retail brands through the Working with Retail Brands (WRBD) menu option.
CWCollaborate Drop Ship Purchase Order Cycle
Creating Drop Ship Orders for CWCollaborate
You create a drop ship order when you enter an order for an item identified as a drop ship item in the Item file. For each drop ship item in the item file, you must identify the vendor who ships the item. The drop ship vendor can be flagged for using CWCollaborate, by entering C in the Drop ship output field using the Working with Vendors (WVEN) menu option; the CWCollaborate interface recognizes and processes drop ship orders for your collaborative vendors only.
You can view all unprocessed drop ship orders, including orders for your non-collaborative as well as your collaborative vendors, using the Displaying Unprocessed Drop Ship Items (DUDS) menu option; this menu option identifies drop ship orders flagged for automatic processing through the CWCollaborate interface.
Note: CWCollaborate does not support negative prices, regardless of the setting of the Allow Negative Prices in Order Entry (E97) system control value. A drop ship order with a negative price is not passed through the CWCollaborate interface, and you receive an email listing the record in error. See Error Acknowledgement email to the retailer.
Which messages are included? CWDirect includes the following types of messages on a drop ship order sent to CWCollaborate:
• Order header messages flagged as P (print on pick) or B (print on both pick and invoice). You can send up to 20 order header messages.
• Order header messages flagged as G (gift order message). You can send up to 5 gift order messages.
• Order line messages. You can send up to 20 order line messages.
• Custom special handling lines. You can send up to 10 custom special handling lines.
• Vendor notes. You can send up to 5 vendor notes.
Sending Drop Ship Order Information to CWCollaborate
You process CWCollaborate drop ship orders using the Selecting Vendors for Drop Ship Processing (MDSP) menu option. For drop ship orders whose vendors are flagged as collaborative, the system:
• creates drop ship purchase orders
• sends the information to CWCollaborate
• CWCollaborate sends an email notification to the vendor informing him that there are drop ship purchase orders to be fulfilled (See New PO Notification email to the vendor)
The vendor can access the purchase order information in CWCollaborate. At this point, the drop ship purchase order has been created and sent, but not yet selected by the vendor for fulfillment.
Note: You can print or reprint a drop ship purchase order using the Print PO and Receiving Worksheets (PPWS) or Printing and Faxing Purchase Orders (MPRP) menu options. Printing or reprinting a drop ship purchase order does not transmit any information to CWCollaborate.
Sending Drop Ship Sets to CWCollaborate
If a drop ship component is associated with a vendor that uses CWCollaborate, the system sends the drop ship component to CWCollaborate. In addition, if the set master item is flagged as drop ship and is associated with a vendor that uses CWCollaborate, the system sends the set master item to CWCollaborate as well.
CWCollaborate does not identify the set master item or its component items; each item in the set is sent to CWCollaborate as an individual item; in order to identify the set in CWCollaborate, you must use the item number and item description to determine which items are part of a set. In order to process the set correctly in CWCollaborate, you should keep the items that make up the set together by pulling and shipping the items in the set at the same time.
In addition, if a PO contains more than one set, there is no way to determine which items belong to which set. In order to process the sets correctly, you should keep the items that make up both sets together by pulling and shipping the items in the sets at the same time.
Pull by PO feature: In order to ship the drop ship set using CWCollaborate correctly, you should pull the drop ship set using the pull by PO feature in CWCollaborate. This ensures that the set master item and its components are pulled at the same time.
Ship by PO feature: If you do not ship by PO, and instead ship selected components of the set, the set remains open until the set master item and all of its components have been selected to ship from CWCollaborate. In addition, if you price at the set master level and ship the components but do not ship the set master item, the system does not bill the set until the set master item is shipped.
Vendor lead days: If you use CWCollaborate and price sets at the set master level, the lead days defined for the set master item and its components impacts how the system creates invoices for the order. When you ship from CWCollaborate, the system sorts the PO lines on the CWCollaborate shipping screen by expected ship date and then by PO line number. If the set master item has a later expected ship date than the component items, the set master item displays last on the shipping screen. When the vendor ships the PO, the PO line ship message for the set master item comes into CWDirect last. When CWCollaborate PO lines are shipped, CWDirect creates a separate invoice for each PO line and puts the freight on the first PO line it encounters. If the set master item is not the first PO line shipped, the system adds freight to the invoice created for a component PO line instead of the set master item’s PO line.
In order to ensure that the first invoice for the drop ship set is for the set master item, the vendor lead days defined for the set master item and all of the component items must match so that the expected ship date is the same for the set master item and all of the component items. If the lead days defined for the set master item is greater than the lead days defined for one or more of the components, the set master item displays after those components.
For more information: See Defining Sets as Drop Ship.
Cancelling CWCollaborate Drop Ship Orders
You can request to cancel a CWCollaborate drop ship order line through Order Inquiry or Purchase Order Inquiry at the Display P/O Drop Ship Screen. A cancel request produces two possible actions:
• If the vendor has not yet selected the order line for fulfillment, the order line is automatically cancelled, and is deleted from the vendor’s screens. You receive an email notification that the cancel request has been accepted, and the drop ship purchase order line is updated with a cancelled status in CWDirect.
• If the vendor has already selected the order line for fulfillment (the order line’s status is In Process), CWDirect sends a cancel request to CWCollaborate.
• CWCollaborate sends a Drop Ship PO Cancel Request email to the vendor informing your vendor that he has cancel requests that require his response. Your vendor either confirms the cancel request, or rejects it (if it is too late to stop the shipment) in CWCollaborate.
You can generate a report of pending cancellation requests using the Printing Drop Ship Integration Reports (PDSR) menu option. See Reports.
If your vendor confirms the request, the drop ship purchase order line is updated in CWDirect with a cancelled status. If your vendor rejects the request, the purchase order line is not cancelled. For either response, you receive a PO Status Update emails to the retailer notification from CWCollaborate informing you of the vendor’s action.
Changing Address and Cost Information
Changing Address Information: When you change the ship-to or sold-to address for an order which includes a CWCollaborate drop ship PO line item which has been sent to CWCollaborate and has not yet been shipped, CWDirect sends the PO Address Change file to CWCollaborate. CWCollaborate creates a record of the original and changed sold-to address and a record of the changed ship-to address, and:
• automatically updates the sold-to address on the sales order.
• if all lines on the PO are in unpulled status, automatically updates the ship-to address information, and does not generate an email to the vendor.
• if any line on the PO is in pulled or held status, generates a New Ship To Address Change Requests email to the vendor email informing your vendor that there are address changes he needs to review. If your vendor accepts the address change, the new ship-to address prints on the packing slip when your vendor ships the order. CWCollaborate keeps a record of the original and the changed ship-to address. If your vendor rejects the address change, CWCollaborate generates a Ship Address Changes were Denied by Vendor email to the retailer email to indicate that the shipping address change cannot be implemented for the purchase order in CWCollaborate.
• if all lines on the PO are in shipped or cancelled status, CWDirect should not generate a PO Address Change file. If, however, the order was not yet updated to Shipped status in CWDirect, but had been shipped in CWCollaborate, no changes are made to address information in CWCollaborate, and CWCollaborate generates an Shipping Address Changes were Auto-Declined email to the retailer email to inform you that address changes have been auto-rejected.
When you change the address on a CWCollaborate drop ship order, the message: Address change sent to vendor displays on the lower half of the Display P/O Drop Ship Screen.
Changing cost information: When you update the Cost field on the PO Maintenance - Change PO Detail Screen, CWDirect sends the PO Cost Change file to CWCollaborate, which then generates a New Purchase Order Cost Change Requests email to the vendor email informing your vendor that there are cost changes for him to review and acknowledge. Whether or not your vendor acknowledges the cost changes, CWCollaborate creates a record of original and updated PO cost, and updates the PO with the new cost.
When you change the cost of a PO, the message: Cost change sent to vendor displays on the lower half of the Display P/O Drop Ship Screen if you access the screen through Purchase Order Maintenance (MPOI).
Shipping CWCollaborate Drop Ship Orders
When your vendor ships a drop ship purchase order line, the CWDirect purchase order line is closed, and the corresponding CWDirect order line is also closed. CWDirect automatically performs shipment confirmation updates for the order and the purchase order.
Vendors can enter shipping-related information (including carrier, tracking number, rate, weight, and ship date) into CWCollaborate; that information is transmitted to CWDirect and can be used to respond to a customer’s questions.
Returning CWCollaborate Drop Ship Orders
You can use CWCollaborate to process returns for a collaborative vendor by entering Y in the Send returns to Collaborate field on the Second Create Vendor Screen. Typically, you would send return information to CWCollaborate if you expect customers to return drop ship merchandise to the vendor’s warehouse, and you want to process returns automatically through CWCollaborate. For each vendor you select to processing returns through CWCollaborate, you can require that the vendor must have a return authorization for the order before accepting returned merchandise, or allow the vendor to accept returned merchandise without a return authorization. You can require some of your collaborative vendors to have return authorizations but allow others to return merchandise without an authorization. See Accepting returns without an Authorization.
• When you send return authorizations to CWCollaborate, your vendors can post returns against the RAs, using the View Returns Authorizations to Receive screen.
• Vendors with CWCollaborate authority to create returns without return authorizations can create returns using the Receive Return screen.
Creating and Sending CWCollaborate Return Authorizations
Notify vendor? Whenever you create a CWCollaborate return, you have the option of not sending the return information to CWCollaborate, by entering N for the Notify vendor field when you create the return. You might choose not to send return information to the vendor, for example, if a customer has received damaged merchandise that you do not want returned, or if the merchandise is being returned to your own warehouse instead of the vendor’s.
Sending return authorizations: Regardless of whether you create, receive and credit a return in one step, or only create (but do not receive or credit) a return authorization, the CWCollaborate interface sends a return authorization to CWCollaborate which is identical to the one sent when you create, but do not receive and credit, a return. When you create the return, regardless of how far it has been processed, the Drop ship status on the Display P/O Drop Ship Screen is updated to RA Sent. When the vendor receives the merchandise and posts the return, CWDirect receives the information, automatically completes processing of the return if it is not yet complete, and the Drop ship status on the Display P/O Drop Ship Screen is updated to Returned.
Emails: CWCollaborate automatically creates and sends a Return Authorization emails to the vendor to each vendor who has RAs to be reviewed, and sends an RA Upload Error emails to the retailer if any RAs did not successfully transfer to CWCollaborate due to errors.
CWCollaborate also sends a Return Authorization Cancellations email to the vendor email to each vendor for whom you delete an RA.
Returning through order maintenance or Work with Return Authorizations: You can create a CWCollaborate return using three options:
• Work with Return Authorizations (WRTA): standard process, using the Create RA Detail Screen
• Work with Return Authorizations (WRTA): streamlined process, using the Return/Exchange Item Screen (Creating a Return)
• Order Maintenance (OIOM or OEOM), using the Return/Exchange Item Screen (Single Item)
You cannot create a CWCollaborate return by entering a negative quantity in order entry.
Regardless of whether you use Work with Return Authorizations or Order Maintenance to create a CWCollaborate return, you must create the return using detail screens; you cannot use the F17 option in order maintenance or the F8 option in Work with Return Authorizations to return all items on an order at once.
Work with Return Authorizations (WRTA) standard process
When you create a return authorization using WRTA with the standard process (the Use Streamlined Return Authorizations (F44) system control value is set to N or is blank) you create, receive, and credit return authorizations in separate steps. Typically, you would create, but not receive and credit, a CWCollaborate return authorization. The process would follow these steps:
1. When you create the return authorization and accept your entry, the CWCollaborate interface automatically sends the return authorization to your vendor.
2. On the Display P/O Drop Ship Screen the Drop ship status is updated to RA Sent.
3. When the vendor receives the merchandise and posts the return, CWCollaborate sends the return information to CWDirect, which automatically receives and credits the return.
4. The order line is updated to Returned status.
5. On the Display P/O Drop Ship Screen the Drop ship status is updated to Returned.
Work with Return Authorizations (WRTA) streamlined process
When you create a CWCollaborate return using the streamlined process in Work with Return Authorizations (the Use Streamlined Return Authorizations (F44) system control value is set to Y), depending on your authority to create, receive, and credit return authorizations, the return is processed automatically as far as your authority extends. However, the CWCollaborate interface sends the vendor a return authorization which is the same as that sent when you create, but do not receive or credit, a return. The process follows these steps:
1. Regardless of how far the return authorization has been processed in CWDirect, the system sends a return authorization to CWCollaborate which is the same as the RA sent when you create, but do not receive or credit a return.
2. Regardless of how far the return authorization has been processed, the Drop ship status on the Display P/O Drop Ship Screen is updated to RA Sent.
3. When the vendor receives the merchandise and posts the return, CWDirect receives the information and automatically completes processing of the return, if it is not yet complete.
4. The order line is updated to Returned status (if it is not already in Returned status).
5. The Drop ship status on the Display P/O Drop Ship Screen is updated to Returned.
Order Maintenance returns (OIOM)
When you create a return in order maintenance, CWDirect creates, receives, and credits the return in one “behind the scenes” step. However, the CWCollaborate interface sends the vendor a return authorization which is the same as the return authorization sent when you create, but do not receive or credit, a return. The process follows these steps:
1. When you create, receive and credit the return, the system sends a return authorization to CWCollaborate which is the same as the RA sent when you create, but do not receive or credit a return.
2. The return is completely processed in CWDirect, and the order line is in Returned status. However, the Drop ship status on the Display P/O Drop Ship Screen is updated to RA Sent.
3. When the vendor receives the merchandise and posts the return, CWDirect receives the information. The return is already credited in CWDirect; however, if the vendor has entered Vendor’s return postage CWDirect creates another credit invoice for the return postage amount.
4. The Drop ship status on the Display P/O Drop Ship Screen is updated to Returned.
Multiple POs or multiple vendors on an order: You can create a CWCollaborate return authorization which includes more than one purchase order, as long as all purchase orders are for the same collaborative vendor. This situation might arise if a customer places an order for a CWCollaborate drop ship item. The PO for that item is sent to CWCollaborate, The customer then modifies the order and orders an additional drop ship item associated with the same vendor. The PO for the second item is sent to CWCollaborate. If the customer returns both items, you can create a return authorization which includes both purchase orders.
You cannot, however, create a return authorization for more than one CWCollaborate vendor. You must create a separate return for each different vendor.
Multiple Returns against a single RA line: A CWCollaborate vendor can create multiple returns against a single RA line. For example, if you create a return authorization with a single RA line for 6 units of an item, the vendor may enter a return against the RA line for 2 units on 12/5 and enter another return against the RA line for the remaining 4 units on 12/10. Each time the vendor enters a return against the RA line, the CWDirect order line is updated to receive and credit the partial return (if the return authorization is not already completely processed), and the Display P/O Drop Ship Screen is updated with the information that the item has been returned for the quantity the vendor received. The Drop ship status field is updated to Returned when the first partial return is posted against the RA.
If the Vendor Modifies a Return Reason or Enters Return Comments: In CWCollaborate, you can specify which vendors have authority to enter or change the return reason, enter comments, or add return postage when they post returns. If a vendor enters comments or changes the return reason when posting a return against an RA, the comments and the changed return reason is stored in the CFS Transaction File (FLCSFT) for the transaction, but these values do not update the return authorization.
If the vendor enters a return postage amount when posting a return against an RA, CWDirect stores this value in the Drop Ship Transaction file, and also credits the amount of the return postage as an additional charge on the order. When CWDirect receives and credits the return authorization, this value increments the amount in the Additional Charge field on the credit invoice. For a return which has already been fully credited in CWDirect before the RA is sent to the vendor, the system creates an additional credit invoice for the return postage amount (as an additional charge credit to the order) when the vendor posts the return.
Cancelling CWCollaborate Return Authorizations
You can send an RA cancellation to CWCollaborate for an RA that has been created, but not received or credited, using the Work with Return Authorizations menu option. Returns created through order maintenance cannot be cancelled, since they are received and credited at the time they are created. An RA cancellation file is automatically sent to CWCollaborate when you delete an RA line on the Work with Return Authorization Detail Screen (standard process) or the Work with RA Detail for Item Screen (streamlined process).
CWDirect creates a separate record in the CSF RA Cancel File (FLCSRC) for each cancelled RA; however, one Cancel RA file can contain multiple cancelled RA lines.
If the vendor has already selected the RA for processing, CWCollaborate generates a Return Authorization Cancellations email to the vendor email to the vendor indicating the RA line has been cancelled and the customer is not returning the item to the vendor.
If the vendor has not yet selected the RA for processing, no email is sent; the RA is deleted from the vendor’s CWCollaborate screens.
Accepting returns without an Authorization
You can allow a CWCollaborate vendor to receive returned merchandise without an RA from CWDirect. When the vendor processes a return without an RA, CWCollaborate sends the return information to CWDirect in the CSF Return Upload File (FLRART); CWDirect creates an RA for the returned merchandise and receives and credits the RA at the same time. This process is similar to the process that occurs when you create Order Maintenance returns (OIOM). The information that you would enter on the Return/Exchange Item Screen (Single Item) when entering the return is provided either in the CSF Return Upload File (FLRART) sent from CWCollaborate, or from default values you specify in system control values as follows:
Value |
Source |
RA # |
This number is comprised of the order number, ship-to number, and return authorization number sequentially assigned by the system for each return authorization against the order. The RA number is assigned in the same way whether you create the return authorization and send it to CWCollaborate, or the return is initiated by a CWCollaborate vendor without an RA. The order number and ship-to number must be passed in the CSF Return Upload File (FLRART) from CWCollaborate. When a CWCollaborate vendor posts a return, CWCollaborate requires that the vendor enter a return number; however, CWDirect does not use the vendor’s return number when creating an RA for a return initiated by a CWCollaborate vendor without an RA. The vendor’s return number is stored in the CFS Transaction File (FLCSFT). When the vendor is returning against an RA, the vendor’s return number is normally the RA number sent from CWDirect, which defaults on the vendor’s CWCollaborate screens. |
Quantity to return |
The number of units of the item that are being returned. This value must be less than or equal to the quantity shipped. The quantity to return must be passed in the CSF Return Upload File (FLRART) from CWCollaborate. |
Return Reason |
The reason for the return, validated against the Return Reason file. The return reason can be passed in the CSF Return Upload File (FLRART) from CWCollaborate. If no valid return reason is passed for a return initiated by a CWCollaborate vendor without an RA the system uses the return reason specified in the Default Return Reason Code for Inbound Returns (H63) system control value. If no reason is specified in the system control value, the system uses the alphanumeric first return reason in the Return Reason file (OERTRS). In CWCollaborate, you can select which vendors have authority to enter return reasons. |
Exchange reason code |
Exchanges cannot be initiated by a CWCollaborate vendor. |
A code that identifies how a returned item is handled by the system, in terms of whether the return updates inventory and the warehouse and location to which the item is returned. The return disposition code for a return initiated by a CWCollaborate vendor without an RA is specified in the Default Return Disposition Code for Inbound Returns (H65) system control value. If no return disposition is specified in the system control value, the system uses the first return disposition in the Return Disposition file (RTNDIS). |
|
Warehouse/Location |
If the Return Disposition code affects inventory (meaning that the item is returned into active inventory and update the on-hand quantity in the specified location), then the warehouse and location to return items is specified in the disposition code. If the disposition code is set up to affect inventory and return to the primary location, the system checks for the primary location for the item. If one is available, the system returns the item automatically to this warehouse location. |
Refund freight |
This value indicates whether to refund the freight charge for the returned item. Valid values are Y andN. The Refund Freight Default for Inbound Returns (H59) system control value specifies the setting of this field for a return initiated by a CWCollaborate vendor without an RA. If no value is specified in the system control value, the system does not refund the shipping charges. See Refund Freight Default for Inbound Returns (H59) for a discussion of when the system prorates freight refunds. Note: This value also controls whether the system refunds any service charges by ship via on the order. See Fulfillment Chapter 30: Working with Ship Via Codes (WVIA). |
Refund additional charges |
This value indicates whether the system should refund the additional charges on the order. Valid values are Y andN. The Refund Additional Charge Default for Inbound Returns (H60) system control value specifies the setting of this field for a return initiated by a CWCollaborate vendor without an RA. If no value is specified in the system control value, the system does not refund the additional charges. An order's additional charges are billed with the first shipment on the order, and a return is always performed against an invoice. For this reason, when you specify to refund additional charges against a subsequent invoice, the customer may not receive the intended refund. |
Refund handling |
This value indicates whether the system should refund handling charges on the order. Valid values are Y andN. The Refund Handling Default for Inbound Returns (H61) system control value specifies the setting of this field for a return initiated by a CWCollaborate vendor without an RA. If no value is specified in the system control value, the system does not refund handling charges. |
Refund duty |
This value indicates whether the system should refund duty on the order. Valid values are Y andN. The Refund Duty Default for Inbound Returns (H62) system control value specifies the setting of this field for a return initiated by a CWCollaborate vendor without an RA. If no value is specified in the system control value, the system does not refund handling charges. |
Vendor’s return postage |
You can specify whether return postage is refunded for a return initiated by a CWCollaborate vendor without an RA by entering a value in system control value Default Additional Charge Code for Inbound Returns (H64). If a valid additional charge code is entered in this system control value, the vendor’s return postage is refunded for the order as an additional charge credit. In CWCollaborate, you can select which vendors have authority to enter return postage amounts. |
Vendor’s comments |
The comments a vendor enters on a return initiated in CWCollaborate without an RA is passed to CWDirect and stored in the Drop Ship Transaction file (FLCSFT). Vendor’s comments entered on a return in CWCollaborate are not displayed on the order. In CWCollaborate, you can select which vendors have authority to enter comments. |
Exchanges can be performed on return authorizations for CWCollaborate returns as on any other return authorization, by entering an exchange reason code when creating the RA in order maintenance or Work with Return Authorizations. The exchanged item is added to the order when the return is received and credited. The exchanged item is treated as a new PO that must then be sent to CWCollaborate using the Selecting Vendors for Drop Ship Processing (MDSP) menu option.
Exchanges cannot be performed on a return initiated by a CWCollaborate vendor without an RA.
Uploading Invoices from CWCollaborate
You can enable your vendors to submit A/P invoices through CWCollaborate, which you can then upload into CWDirect. Various controls and thresholds are available for you to control the way that the A/P invoices are created; for example, you can set quantity or cost variances that the invoices cannot exceed without being suspended in batch, or you can choose to have all uploaded invoices suspended in batch for review.
See Working with A/P Invoice Upload Errors (WAPU) for an overview on uploading A/P invoices from CWCollaborate, including setup options and how to correct errors.
Tracking the Status of CWCollaborate Drop Ship Orders
The Display P/O Drop Ship Screen displays the status of a CWCollaborate drop ship order so that you can track the order line through the CWCollaborate process. When you process the drop ship order, request a cancellation for an order line, send or cancel a return authorization, update the shipping address for an order, a message is written to the Display P/O Drop Ship screen. When you update the PO Cost for a PO, a message displays if you access the screen through PO Maintenance (MPOI). In addition, whenever a CWCollaborate vendor pulls an order for fulfillment, ships the order, confirms or denies a cancel request, updates the expected delivery date for an order, completes a return or responds to a return cancellation, a message is written to the Display P/O Drop Ship screen.
Special Handling on CWCollaborate Drop Ship Orders
The CWCollaborate interface supports only custom special handling of drop ship orders. Up to ten lines of special handling instructions can be displayed on CWCollaborate’s Customization screen. See Work with Special Handling Screen for information on custom special handling.
To set up custom special handling for a drop ship item, see Customer Service Chapter 9: Establishing Custom Special Handling Formats (WSHF).
The CWCollaborate interface sends up to five lines of each of the following types of messages:
• Order messages: you may enter up to 20 Sales Order messages on an order header for a CWCollaborate drop ship order. Order messages identified in CWDirect with a status of P or B print on CWCollaborate packing slips.
• Gift messages: you may enter up to 5 Gift messages on an order header for a CWCollaborate drop ship order. Order messages identified in CWDirect with a status of G print as gift messages on CWCollaborate packing slips.
• Order Line messages: you may enter up to 20 order line messages at a drop ship order line for a CWCollaborate drop ship order. Order line messages identified in CWDirect with a status of P or B print on CWCollaborate packing slips below the order line.
See Order Entry Chapter 14: Adding Order Messages.
You can generate the following reports for CWCollaborate drop ship orders, using the Printing Drop Ship Integration Reports (PDSR) menu option:
• Drop Ship Integration Items on Hold from Vendor Report
• Drop Ship Integration Items Revised Due Date Report
• Drop Ship Items Pending Cancellation
• Drop Ship Items Confirmed Cancellation
• Drop Ship Items Pending Shipment
Viewing Errors and Re-entering Orders in Error
CWCollaborate transfer errors can be viewed using the Working with Drop Ship Errors (WDSE) menu option.
An order which is not transferred successfully through the Selecting Vendors for Drop Ship Processing (MDSP) menu option cannot be re-transferred. You must recreate the order as a new order to process it.
When using CWCollaborate in conjunction with CWDirect, backorder notices for drop ship items are based on accurate expected ship date information which your collaborate vendors communicate to CWDirect. Because expected shipment information is readily available for CWCollaborate drop ship items, the CWCollaborate interface evaluates drop ship items for back order notices in a manner similar to the way it evaluates non-drop-ship backordered items. CWCollaborate offers the following advantages over regular drop ship processing:
• When you enter an order for a CWCollaborate drop ship item, the system calculates an expected ship date based on vendor item Lead days and the value you enter in the Drop Ship Lead Days (H36) system control value.
• When your CWCollaborate vendor enters a revised expected ship date for a drop ship order line, the expected ship date is updated in the CWDirect order, and this updated expected ship date prints on backorder notices when you generate backorder cards, and is used as the Next backorder notice date in generating subsequent backorder cards.
• For order types configured to print immediate backorder card notices, these initial notices print for CWCollaborate drip ship items as well as non-drop-ship items.
Setup for backorder notifications: If you want to generate backorder notices for a CWCollaborate drop ship item, set the following fields:
• the Sup B/O card (Suppress backorder card) field in the SKU file must be set to N for the item
• the Unconditional Suppression of Backorder Card (F19) system control value must be set to N
• set accurate Lead days for the vendor item, using the Working with Vendor Items (WVNI) menu option
• set the Drop Ship Lead Days (H36) system control value to the number of days you want to add to the date passed to CWCollaborate to calculate Expected ship date in CWDirect.
Calculating an Expected Ship Date for CWCollaborate Items
When you enter an order line for a drop ship item that will be fulfilled by a CWCollaborate vendor, the CWCollaborate interface passes a due date to CWCollaborate which your vendor uses to fulfill the order. In addition, CWCollaborate calculates an expected ship date and populates the Expected ship date field in the CWDirect Order Detail file with this date. This date is the Exp ship date (Expected ship date) in Order Inquiry, and as the Orig exp ship date on the Display P/O Drop Ship Screen, and is printed on Backorder notices sent to the customer.
To calculate the due date sent to CWCollaborate, the system uses:
Current date + Vendor item Lead days
(An order line with a future Arrival date is not eligible for processing through MDSP until its Arrival date is within the vendor item lead days for the item)
To calculate the Expected ship date, the system uses the greater of:
Arrival date
Current date + Vendor item Lead days + Drop Ship Lead Days (H36).
For example, for an order entered 3/10:
For an order entered on: 3/10 |
|||
If the Arrival Date is: |
3/10 (current order) |
3/15 |
4/1 |
Vendor Item Lead Days: |
14 |
14 |
14 |
Drop Ship Lead Days (SCV H36): |
3 |
3 |
3 |
Expected Ship Date in CWDirect: |
3/27 (3/10 + 14 + 3) |
3/27 (3/10 + 14 + 3) (This calculation is greater than the arrival date.) |
4/1 (This arrival date is greater than the calculated date.) |
Due Date sent to the vendor via CWCollaborate: |
3/24 (3/10 + 14) |
3/24 (3/10 + 14) (This calculation is greater than the arrival date.) |
4/1 (This arrival date is greater than the calculated date.) |
When the Expected Ship Date Expires with No Shipment
Additionally, if the Expected ship date passes before the order has been shipped, the system generates a backorder notification when you process backorder cards. In this case, the new Expected ship date reported to the customer is calculated by adding the number of days specified in the FTC -- # of Days for Items without Expected Ship Date (C71) system control value to the date you run the Generate Backorder Cards function.
Example: When the expected ship date passes but the order has not shipped:
• Order date: 3/10
• Arrival date: 3/10
• Vendor item lead days: 14
• Drop ship lead days (H36): 3
• Expected delivery date [Current date + Vendor item lead days + Drop ship lead days]: 3/27
• FTC -- # of Days for Items without Expected Ship Date (C71): 30
Date |
Action |
Backorder Card Result when you process backorder cards (GBOC) |
3/10 |
You enter the order. |
No card is produced (Immediate Backorder Notification is set to N). Expected ship date on the order is 3/27. |
3/27 |
Expected ship date expires but the order has not shipped. |
Backorder card is generated with new expected ship date: 4/26 (3/27 + days specified in SCV C71). |
See Setting up the CWCollaborate Interface for additional information on system control value settings.
When Your Vendor Revises the Expected Ship Date
When your vendor revises an expected ship date, the CWDirect-CWCollaborate interface updates the Expected ship date to reflect your vendor’s entry. If the Expected ship date has been increased from the date calculated when you entered the order, the system generates a backorder notification for the order line, informing the customer of the revised date, the next time you process backorder cards using the Generate Backorder Cards (GBOC) menu option.
See Setting up the CWCollaborate Interface for information on system control value settings.
Example: When your vendor revises the expected ship date:
• Order date: 3/10
• Arrival date: 3/10
• Vendor item lead days: 14
• Drop ship lead days (H36): 3
• Expected delivery date [Current date + Vendor item lead days + Drop ship lead days]: 3/27
Date |
Action |
Backorder Card Result when you process backorder cards (GBOC) |
3/10 |
You enter the order. |
No card is produced (Immediate Backorder Notification is set to N). Expected ship date on the order is 3/27. |
3/20 |
Your vendor revises the expected ship date to 4/15 |
Backorder card is generated to inform the customer of the new expected ship date: 4/15 |
4/15 |
Expected ship date expires but the order has not shipped. |
Backorder card is generated with new expected ship date: 5/15 (4/15 + days specified in SCV C71). |
Generating Immediate Backorder Notifications for CWCollaborate Items
For drop ship items processed through the CWCollaborate interface, you can, if you wish, generate immediate backorder notifications to inform your customers of an accurate expected delivery date. Immediate backorder notifications are controlled by order type, and set up in the Establishing Order menu option. For order types with the Immediate B/O (Immediate backorder notice) field set to Y, CWDirect generates backorder notices for CWCollaborate drop ship items the next time you generate backorder cards.
Note: The Number of Days to Delay Initial Backorder Notice (D89) system control value does not apply to CWCollaborate drop ship items.
When you generate an immediate backorder notice for a CWCollaborate item, the notice informs the customer of the expected delivery date calculated by CWDirect. (See Calculating an Expected Ship Date for CWCollaborate Items.) Subsequent backorder notices are generated When Your Vendor Revises the Expected Ship Date, or When the Expected Ship Date Expires with No Shipment.
Setup for immediate backorder notifications: If you want to generate immediate backorder notices for a CWCollaborate drop ship item, in addition to settings for backorder notifications, set the following fields as:
• the Immediate B/O (Immediate backorder notice) field for the order type must be set to Y, through the Establishing Order Types (WOTY) menu option.
For additional setup, see Setting up the CWCollaborate Interface.
Example: When you generate immediate backorder notices:
• Order date: 3/10
• Arrival date: 3/10
• Vendor item lead days: 14
• Drop ship lead days (H36): 3
• Immediate backorder field for the order type: Y
• Expected delivery date [Current date + Vendor item lead days + Drop ship lead days]: 3/27
Date |
Action |
Backorder Card Result when you process backorder cards (GBOC) |
3/10 |
You enter the order. |
Backorder card is generated to inform the customer of the expected ship date: 3/27. |
3/20 |
Your vendor revises the expected ship date to 4/15 |
Backorder card is generated to inform the customer of the new expected ship date: 4/15. |
4/15 |
Expected ship date passes but the order has not shipped. |
Backorder card is generated with new backorder date: 4/15 + days specified in SCV C71. |
Working with Pending Cancellations for CWCollaborate Items
You can flag orders to be cancelled after the second backorder notice by using the FTC -- Action after Second Notification (C70) system control value. You can work with orders and order lines that have been flagged for cancellation due to backorders through the Working with Backorders Pending Cancellation (WBPC) menu option.
Purpose: CWCollaborate generates emails to notify the vendor or retailer when a certain action is performed.
The system generates and sends the following emails to vendors:
• New PO Notification email to the vendor
• Drop Ship PO Cancel Request email to the vendor
• New Purchase Order File Waiting to be Downloaded email to the vendor
• PDF Packing Slips Available email to the vendor
• Vendor Shipment Upload email to the vendor
• Vendor Shipment Batch Processing Error email to the vendor
• Invoice File Uploaded email to the vendor
• Approve/Reject Invoice Email Alert email to the vendor
• New Purchase Order Cost Change Requests email to the vendor
• New Ship To Address Change Requests email to the vendor
• Return Authorization emails to the vendor
• Vendor Return Upload Errors email to the vendor
Emails are sent to the vendor in text format without an attachment.
New PO Notification email to the vendor
CWCollaborate sends the following email when it has received POs from CWDirect to be fulfilled by the vendor.
Defining when the vendor receives new PO notification emails: A retailer defines whether the vendor receives a new PO notification email each time CWDirect sends a new PO to CWCollaborate to be fulfilled by the vendor or whether the vendor receives the new PO notification email at defined intervals.
• the Newpo_Mail_Enable tag in the Properties file defines whether the vendor receives a new PO notification each time CWCollaborate receives POs from CWDirect to be fulfilled by the vendor. If this tag is set to TRUE, the vendor receives new PO notification emails. If this tag is set to FALSE, the vendor does not receive new PO notification emails unless you enable the new po alert for vendor SQL Server Agent job.
• the new po alert for vendor SQL Server Agent job allows you to define the time interval when the vendor receives the new PO notification email for the new POs sent to CWCollaborate to be fulfilled by the vendor. You can define when (monthly, weekly, or daily) and the time interval (hours or minutes) the system uses before sending new PO notification emails to the vendor.
Note: If the Newpo_Mail_Enable tag in the Properties file is set to FALSE and the new po alert for vendor job is not enabled, the vendor never receives a new PO notification email for the new POs sent from CWDirect to be fulfilled by the vendor.
Subject: New PO Notification
EGOLF has transmitted drop ship purchase orders for you to fulfill.
Click on this url to launch the website in your browser: http://www.Company.com
Date-Time
Fri Feb 15 16:28:56 EST 2002
Division Name |
No. of POs |
No. of Items |
No. of Units |
Total Value |
55 RETAIL BRAND |
1 |
2 |
10 |
10.00 |
Total |
1 |
2 |
10 |
10.00 |
The total value represents the vendor’s price for merchandise.
New Automatically Pulled PO Notification email to the vendor
CWCollaborate sends the following email when the automatic PO pull process pulls all unpulled PO lines and sends the POPULL file to the vendor’s outbox.
If you enable the automatic PO pull process, CWCollaborate uses the address defined in the New PO notification emails field (renamed to New PO file emails when automatic PO pull is enabled) to send this email. In this case, the vendor does not receive an email when CWCollaborate receives POs from CWDirect to be fulfilled. Instead, the vendor receives an email when the system automatically pulls unpulled PO lines and sends the POPULL file to the vendor’s outbox. If you enable automatic PO pull processing, the vendor always receives an email notification; you cannot define when the vendor receives new automatically pulled PO notification emails.
Note: If you enable the automatic PO pull process and the vendor manually pulls a PO, an email is not generated.
The vendor or retailer can define an email address in the New PO file emails field on the vendor preferences screen.
Subject: New Automatically Pulled PO Notification
EGOLF has transmitted drop ship purchase orders for you to fulfill.
The purchase orders have been pulled and are waiting in your outbox to be retrieved.
Click on this url to launch the website in your browser: http://www.Company.com
Drop Ship PO Cancel Request email to the vendor
CWCollaborate sends the following email when it has received a request from CWDirect to cancel an order which has already been pulled by the vendor.
The vendor or retailer can define an email address in the PO update emails field on the vendor preferences screen.
Note: When CWDirect requests to cancel a drop ship order line which has not yet been selected for fulfillment (pulled) by the vendor, no email is generated. The order line is deleted from the vendor’s screens and the order line is automatically cancelled.
Subject: Drop Ship PO Cancel Request
A customer has requested that the drop ship item indicated below be cancelled.
Please access our website and verify whether this item can be cancelled.
Click on this url to launch the website in your browser: http://www.Company.com
RETAIL BRAND 001 division of EGOLF sent this request on Fri Feb 15 16:34:25 EST 2002
PO Number: |
0007890 |
PO Line: |
|
00001 |
Customer Name: |
KATE MCCARTHY |
SO Number: |
00003395-001 |
|
Item Code/Desc: |
V001/VENDOR'S TEST ITEM DESC - 001 |
|
|
|
Units: |
1 |
Cost: |
|
33.33 |
The email displays vendor’s item number and description; if these are not available, the retailer’s item number and description display. The cost displayed is the retailer’s cost (vendor’s price); if this cost is not available, 0.00 displays.
New Purchase Order File Waiting to be Downloaded email to the vendor
CWCollaborate sends the following email when a POPULL file in a ready status remains in the vendor’s outbox for longer than the number of hours defined by the retailer in the Outbox file delinquency trigger(hours) field on the retailer preferences screen.
The vendor or retailer can define an email address in the Delinquent file notification emails field on the vendor preferences screen.
Note: The system only sends this email if you have automatic PO pull enabled.
Subject: New Purchase Order File Waiting to be Downloaded
There is a New PO file waiting to be retrieved from the EGOLF retailers system.
File Name Created Date
222_POPULL 11/21/2001 12:01 PM
511_POPULL 12/07/2001 11:16 AM
515_POPULL 12/07/2001 12:32 PM
521_POPULL 12/07/2001 03:05 PM
Please retrieve as soon as possible.
PDF Packing Slips Available email to the vendor
CWCollaborate sends the following email when PDF packing slips on the download packing slips screen that have not yet been printed are ready to print.
Note: To print PDF packing slips, you must set the Packing slip format field on the vendor preferences screen to PDF.
This email is sent only if the PDF packing slips do not print interactively during PO pull. Packing slips do not print during PO pull if:
• The Enable print packing slip preference is not selected.
• The number of POs pulled is greater than the maximum threshold. The retailer can use the confirmPull field in the Properties file to define the maximum number of records to process at the pull recap confirmation screen before switching from interactive to batch processing.
• The number of packing slips to be printed is greater than the maximum threshold. If the packing slip format is PDF, the retailer or vendor can use the Packing slip threshold field on the vendor preferences screen to define the maximum number of PDF packing slips that can print interactively during PO pull. If you exceed this threshold, a browser window opens and displays a message instead of the packing slips. In addition, the system sends the PDF packing slips available email to the vendor when the packing slips are ready to download.
The vendor or retailer can define an email address in the PO update emails field on the vendor preferences screen.
Subject: PDF Packing Slips Available
A PDF file containing packing slip batch number 121 is available for you to download and print.
Click on this URL to launch the website in your browser: http://www.Company.com.
Date-Time
Tue Mar 29 10:48:59 EST 2005
Vendor Shipment Upload email to the vendor
CWCollaborate sends the following email when the vendor uploads shipment confirmations from his system either using the upload shipment confirmation screen or a custom program.
This email is sent to the vendor based on the Shipment error emails only preference setting.
• If the Shipment error emails only preference is selected, the system sends the email only if the shipment file did not load successfully due to errors.
• If the Shipment error emails only preference is unselected, the system sends the emails regardless if the shipment confirmations upload successfully or if errors occur during the upload.
The vendor or retailer can define an email address in the Upload shipment notification emails field on the vendor preferences screen.
Successful shipment upload email:
Subject: Vendor shipment upload for BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has uploaded a shipment file with the following results:
Date Time
12/10/2001 9:54 AM
Total number of records processed 2
Total number of records successfully loaded 2
Failed shipment upload email:
Subject: Vendor shipment upload for BOTTGER COLLABORATE INDUSTRIES
Shipments from vendor BOTTGER COLLABORATE INDUSTRIES could not be loaded into system for the following reasons:
Retailer Id Org Id PO # Line # Qty Error
EGOLF 555 0001327 00001 1 Line already shipped
Shipment upload errors: The table below lists the shipment errors that may display in the email and the reason for the error. CWCollaborate validates the shipment confirmation upload only if the Bypass shipment edit vendor preference is not selected.
Error |
Reason |
Invalid retailer ID |
The retailer ID in the shipment upload is missing, invalid, or not associated with the vendor. |
Invalid organization ID |
The organization ID in the shipment upload is missing, invalid, or not associated with the vendor. |
Missing PO number |
The PO number in the shipment upload is missing. |
Missing PO line number |
The PO line number in the shipment upload is missing. |
PO number invalid for vendor |
The PO number in the shipment upload is not associated with the vendor. |
PO number/line number invalid |
The PO line number is invalid for the PO number. |
PO line could not be determined based on item |
The PO line number could not be found, based on the item information in the shipment upload (retailer item number, vendor item number, UPC number). |
Invalid PO line number/item number combination |
The item (retailer item number, vendor item number, or UPC number) in the shipment upload is not associated with the PO line number defined in the shipment upload. |
Line already shipped |
The PO line is already in a shipped status. |
Line cancelled |
The PO line is in a cancelled status and cannot be shipped. |
Line unpulled |
The PO line is in an unpulled status and cannot be shipped. |
Line heldunpulled |
The PO line is in a heldunpulled status and cannot be shipped. |
Invalid internal reference number for PO line |
The internal reference number is not associated with the PO line number. |
Missing shipment date |
A shipment date is not defined for the PO line. |
Invalid shipment date |
The shipment date defined for the PO line is invalid or a future date. |
Shipped quantity greater than ordered quantity |
The shipped quantity defined for the PO line is greater than the ordered quantity. |
Shipped quantity less than ordered quantity |
The shipped quantity defined for the PO line is less than the ordered quantity. |
Invalid uom for PO line |
The unit of measure does not match the unit of measure on the PO line. |
PO line number could not be determined based on item due to invalid line status |
The status of the PO line number found, based on the item information in the shipment upload (retailer item number, vendor item number, UPC number), was not eligible for shipment (based on the Bypass shipment edit vendor preference). |
Vendor Shipment Batch Processing Error email to the vendor
CWCollaborate sends the following email when the vendor selects to ship more than the number of purchase order lines the retailer specifies in the updateShipment threshold in the Properties file and an error occurs during the shipment batch process. The failed PO line does not ship and instead, remains unshipped on the shipping screen.
The vendor or retailer can define an email address in the Upload shipment notification emails field on the vendor preferences screen.
Subject: Vendor shipment batch processing error
Interactive Shipping for vendor BOTTGER COLLABORATE INDUSTRIES failed during batch processing for the following reason:
Date Time
06/17/2005 9:55 AM
Tracking #:75661352
Error: Unable to insert shipment header.
Invoice File Uploaded email to the vendor
CWCollaborate sends the following email when the vendor uploads a new invoice file if it cannot reconcile one or more of the included invoices, either because of missing or inconsistent information, or because the invoice is out of balance.
Possible errors include:
• the invoice is out of balance
• the invoice number already exists
• the item on the invoice line did not match a shipped PO line
• the item on the invoice line was already fully invoiced
• the item code is not valid
• shipped quantity is greater than the ordered quantity
• invalid shipment date
• invalid uom (unit of measure) for PO line
The vendor can define an email address in the Vendor invoice email field on the vendor preferences screen. The retailer can define an email address for the vendor in the Vendor invoicing email address field on the vendor information screen.
An email is also sent to the retailer at this time; see Invoice File Uploaded for Vendor email to the retailer.
Subject: Invoice File Uploaded
Date: Thu, 6 Dec 2001 12:12:03 -0500 (EST)
The following invoices encountered problems during load:
Invoice #CR1234 Reason: Invoice is Out of Balance.
Thank you,
EGOLF
Approve/Reject Invoice Email Alert email to the vendor
CWCollaborate sends the following email when CWDirect approves or rejects an out of balance invoice that the vendor had submitted.
The vendor or retailer can define an email address in the Invoice emails field on the vendor preferences screen.
Subject: Approve/Reject Invoice Email Alert
The following invoices have been approved:
Inv. Date |
Invoice Number |
Invoice Description |
12/06/2001 |
IN1094a |
regular shipments from 11/01 through 12/01 |
12/06/2001 |
IN1107s |
special handling shipments for 11/01 |
Click on this URL to launch the website in your browser:http://www.Company.com.
Thank you,
EGOLF
New Purchase Order Cost Change Requests email to the vendor
CWCollaborate sends the following email when CWDirect submits a PO cost change for a PO. A separate email is generated for each changed line on a PO.
The vendor or retailer can define an email address in the Vendor invoice email field on the vendor preferences screen.
Subject: New Purchase Order Cost Change Requests
Prices have been changed on the following Purchase Orders:
PO# 0001120 00001
Please log in to our website to review and acknowledge the changes.
Click on this url to launch the website in your browser: http://www.Company.com.
Thank you,
EGOLF
New Ship To Address Change Requests email to the vendor
CWCollaborate sends the following email when CWDirect submits an address change for a pulled, held/pulled, or held/unpulled PO.
Note: An address change generates a notification for a change to a sold-to address even if the sold-to address is different from the ship-to address. The vendor can just use the Select checkbox at the View Address Changes screen to accept the change, even though it does not affect the shipping address for the order.
The vendor or retailer can define an email address in the PO update emails field on the vendor preferences screen.
Subject: New Ship To Address Change Requests
The shipping address has changed on the following pulled/held orders:
Retail Div |
Sales Order |
Purchase Order |
Customer Name |
002 |
00005912-001 |
0001075 |
Margaret Mahoney |
The changes must be accepted before they can take effect. Please log in to our website and accept or reject these changes.
Click on this url to launch the website in your browser: http://www.Company.com.
Thank you,
EGOLF
Return Authorization emails to the vendor
CWCollaborate sends the following email when new RAs and cancelled RAs are loaded from CWDirect.
Note: The cancelled RA must be in a pulled status in order to generate an email.
The vendor or retailer can define an email address in the Return notification emails field on the vendor preferences screen.
New Return Authorization email to the vendor
Subject: New Return Authorization
EGOLF has transmitted return authorizations for customer returns that will be sent directly to your facility. Print the return authorizations or download them to your system.
Click on this url to launch the website in your browser:
http://www.Company.com
Date |
Time |
02/15/2002 |
4:43 PM |
Total Number of RAs |
Total Items |
Total Units |
Total Dollar Value |
1 |
1 |
1 |
25.00 |
Return Authorization Cancellations email to the vendor
Subject: Return Authorization Cancellations
EGOLF has cancelled the attached return authorizations. The customer will not be returning these items to you.
Date=02/15/2002 Time=4:47 PM Order #=00003238-001 PO #=0007731
RA #=00003238-001-001 Item #=V001 Description=VENDOR'S TEST ITEM DESC - 001
Vendor Return Upload Errors email to the vendor
CWCollaborate sends the following email when NEWRETURN files uploaded from the vendor’s OMS are not loaded into CWCollaborate due to errors. An email is not sent to the vendor if the NEWRETURN file load is successful.
Note: If the NEWRETURN file contains a return with multiple return lines and 1 return line contains errors but the other return lines do not contain errors, the system loads the return lines that do not contain errors into the database successfully. You can correct the errors for the 1 return line in the same NEWRETURN file and reload the file; when you do this, all of the return lines that were previously loaded will error (because they are now considered duplicates) and the 1 return line that has been corrected will load into the database successfully.
The vendor or retailer can define an email address in the Return notification emails field on the vendor preferences screen.
Possible errors:
• Invalid retailer ID
• Invalid organization ID
• Either the return authorization or the vendor return number is required
• Invalid Sales Order, RA Number, PO # combination
• Invalid Sales Order, RA Number, RA Line, PO #, PO line combination
• Return Reason missing
• Return reason is invalid
• Return Reason description missing
• Invalid purchase order number / line number
• Invalid sales order number for purchase order / line number
• PO number / PO line number invalid for the vendor and the sales order
• Quantity to be returned greater than shipped
• Line already fully returned
• PO line has not been shipped (the line is in a cancelled, unpulled, or pulled status)
• Quantity to return must be greater than zero
• Duplicate return received line
• The item details of the returned item do not match the details of the same item sent through the PO. One or more of the following fields is invalid: itemCodeUPC, itemDescUPC, itemCodeEAN, itemDescEAN, retailerItemCode, vendorItemCode, poInternalReferenceNumber.
• There is no existing return authorization for the item
• A return authorization already exists for the same return number and item
• A return exists without return authorization
• The returned date should be in YYYYMMDD format and should not be empty
Subject: Vendor return upload errors
The following returns could not be loaded into the system for the following reasons:
Retailer ID=EGOLF Org ID=032 RA #=00003238-001-001 Order #=00003238-001
PO #=0007731 Item #=VENDOR001 Qty=1
Error=A return authorization with the same number already exists.
A retailer can send general contact emails to a vendor by clicking the vendor contact email link on the vendor workload summary screen. The system launches an email message in the retailer’s browser, addressed to the vendor.
The system allows a retailer to store retailer’s contact email addresses at all hierarchy levels, but these addresses are for informational purposes only.
The system generates and sends the following emails to retailers:
• Error Acknowledgement email to the retailer
• PO Status Update emails to the retailer
• Vendor Delinquent Picking Up New PO File for Vendor email to the retailer
• Vendor Shipment Upload email to the retailer
• Invoice File Uploaded for Vendor email to the retailer
• Shipping Address Changes were Auto-Declined email to the retailer
• Address Change Errors email to the retailer
• Ship Address Changes were Denied by Vendor email to the retailer
• RA Upload Error emails to the retailer
• Vendor Return Upload Errors email to the retailer
Emails sent to the retailer are in text format without an attachment.
Note: Generating email and updating CWDirect are separate functions in the system. Receiving an email notification does not necessarily mean your OMS has been updated if, for example your file transfer protocol is incorrectly set up.
Error Acknowledgement email to the retailer
CWCollaborate sends the following email when it has received new information from CWDirect and one or more of the records contains errors and could not be loaded into the database. If none of the records from CWDirect contain errors, the retailer does not receive an error acknowledgment email. An email is sent to the retailer when records contain errors for:
• vendors; see Vendor Load Upload Error email to the retailer
• new POs; see Drop Ship PO Load Error email to the retailer
• cancel requests; see Cancel Request Upload Error email to the retailer
• new RAs; see New Return Authorization Errors email to the retailer
• cancel RAs; see Cancel Return Authorization Errors email to the retailer
Other types of upload errors generate different emails, such as the Invoice File Uploaded for Vendor email to the retailer or the Address Change Errors email to the retailer.
The retailer can define an email address in the Error acknowledgment field on the retailer preferences screen at the retailer level only. If an email address is not defined in this field, the system uses the address defined in the Properties file.
Vendor Load Upload Error email to the retailer
Subject: Vendor Load Upload error
Errors encountered when loading vendors. See error log for details.
Drop Ship PO Load Error email to the retailer
Subject: Drop Ship PO Load Error
Below is a summary of records received, processed, and errored by the system
Total Number of Records Processed : 1
Total Number of Correct Records : 0
Total Number of Errored Records : 1
Bad File Name : e:/cdc/logs/NewPOError.log
-- Error Log
Error while trying to Insert record in PO_HEADER Table
FOR RETAILER_ID = 'EGOLF'
AND ORGANIZATION_ID = '032'
AND PO_NUMBER = '0007890'
ERROR MESSAGE : [CDCAPPNT40]Violation of PRIMARY KEY constraint 'PK__po_header__30F848ED'. Cannot insert duplicate key in object 'po_header'.-0000001-
Error while trying to Insert record in PO_HEADER Table
FOR RETAILER_ID = 'EGOLF'
AND ORGANIZATION_ID = '032'
AND PO_NUMBER = '0007890'
ERROR MESSAGE : [CDCAPPNT40]Violation of PRIMARY KEY constraint 'PK__po_header__30F848ED'. Cannot insert duplicate key in object 'po_header'.-0000001-
Error while trying to validate or insert records in RETAIL_CARRIER Table
ERROR MESSAGE : Carrier for PO already exists as inactive. The new PO could not be loaded.
Invalid Carrier Code is 02
Cancel Request Upload Error email to the retailer
Subject: Cancel Request upload error
Error encountered when loading cancel request. See error log for details.
New Return Authorization Errors email to the retailer
Subject: New Return Authorization errors
The following return authorizations could not be loaded into CWCollaborate for the following reasons:
RetailerID=EGOLF Org ID=555 RA#=00008071-001-003 Order #=00008071-001
PO#=0020063 Item #= Qty=1
Error=Invalid purchase order number / line number.
Cancel Return Authorization Errors email to the retailer
Subject: Cancel Return Authorization errors
The following cancel return authorizations could not be loaded into CWCollaborate for the following reasons:
RetailerID=EGOLG Org ID=555 RA#=00008071-001-003 Order #=00008071-001
PO#=0020063 Item #= Qty=1
Error = Invalid retailer ID.
PO Status Update emails to the retailer
Drop Ship PO Status Change from Vendor email to the retailer
CWCollaborate sends the following email every time a vendor user clicks update on the status screen. On the status screen, a vendor can perform a variety of tasks that affect the status of an item on order. Specifically, these tasks include:
• Putting an ordered item on a PO on hold when you cannot fulfill the order or have a problem with the order that needs to be communicated back to CWDirect
• Releasing an ordered item from hold
• Revising the due date
The retailer can define an email address in the PO status update field on the retailer preferences screen at the vendor, retail division, organization, or retailer level; a separate email is generated for each retail division.
Subject: Drop Ship PO Status Change from BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has changed the status of the following drop ship items.
PO Number: |
0007730 |
|
|
SO Number: |
00003237-001 |
|
|
Item Code/Desc: |
VENDOR001/NON-SKU'D TEST ITEM FOR VENDOR 001 |
||
Current Status: |
Pulled |
|
|
Orig. Due Date: |
02/18/2002 |
New Due Date: |
|
Reason: |
EMAIL CHECK FOR STATUS CHANGE |
||
Note: The New due date is always the revised due date whether or not it was updated. If the due date was never revised, the New due date is blank.
The email displays the retailer’s item number and description; if these are not available, the vendor’s item number and description display.
Drop Ship PO Cancel Request Response from Vendor email to the retailer
CWCollaborate sends the following email when a vendor user has confirmed or rejected a cancel request.
The retailer can define an email address in the PO status update field on the retailer preferences screen at the vendor, retail division, organization, or retailer level.
Subject: Drop Ship PO Cancel Request Response from BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has ACCEPTED the following cancellation requests on Mon Dec 10 15:03:40 EST 2001:
PO Number: |
0001003 |
PO Line: |
0003 |
Customer Name: |
BERNADETTE T MIRANDA |
SO Number: |
00004839-001 |
Item Code/Desc: |
DOGA1/PLUSH STUFFED ANIMAL DOG |
||
Units:
|
5 |
Cost: |
400.00 |
Total Units: |
5 |
Total Cost: |
400.00 |
The email displays the retailer’s item number and description; if these are not available, the vendor’s item number and description display. The cost displayed is the retailer’s cost (vendor’s price); if this is not available, 0.00 displays.
Vendor Delinquent Picking Up New PO File for Vendor email to the retailer
CWCollaborate sends the following email when a POPULL file remains in the vendor’s outbox for longer than the number of hours defined by the retailer in the Outbox file delinquency trigger(hours) field on the retailer preferences screen.
The retailer can define an email address in the Delinquent file notification emails field on the retailer preferences screen at the vendor, organization, or retailer level.
Subject: Vendor Delinquent Picking up New PO File for BOTTGER COLLABORATE INDUSTRIES
The following vendor is late in retrieving their New PO file(s) from the outbox.
Vendor# |
Vendor Name |
File Name |
File Create Date |
9782723 |
BOTTGER INDUSTRIES |
222_POPULL |
11/21/2001 12:01 PM |
9782723 |
BOTTGER INDUSTRIES |
531_POPULL |
12/10/2001 09:23 AM |
9782723 |
BOTTGER INDUSTRIES |
532_POPULL |
12/10/2001 09:34 AM |
9782723 |
BOTTGER INDUSTRIES |
533_POPULL |
12/10/2001 09:39 AM |
Vendor Shipment Upload email to the retailer
CWCollaborate sends the following email when it receives shipment confirmations from the vendor’s system, based on the Shipment error emails only preference setting.
• If the Shipment error emails only preference is selected, CWCollaborate sends the email only if the shipment file did not load successfully due to errors.
• If the Shipment error emails only preference is unselected, CWCollaborate sends the email regardless if the file loaded successfully or did not load due to errors.
The vendor can upload the file using the upload shipment confirmation screen or a custom program. The retailer can define an email address in the Upload shipment notification emails field on the retailer preferences screen at the vendor, organization, or retailer level.
Successful shipment upload email:
Subject: Vendor shipment upload for BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has uploaded a shipment file with the following results.
Date Time
12/10/2001 12:03 PM
Total number of records processed 1
Total number of records successfully loaded 1
Failed shipment upload email:
Subject: Vendor shipment upload for BOTTGER COLLABORATE INDUSTRIES
Shipments from vendor BOTTGER COLLABORATE INDUSTRIES could not be loaded into system for the following reasons:
Retailer Id Org Id PO # Line # Qty Error
EGOLF 555 0001327 00001 1 Line already shipped
Shipment upload errors: The table below lists the shipment errors that may display in the email and the reason for the error. CWCollaborate validates the shipment confirmation upload only if the Bypass shipment edit vendor preference is not selected.
Error |
Reason |
Invalid retailer ID |
The retailer ID in the shipment upload is missing, invalid, or not associated with the vendor. |
Invalid organization ID |
The organization ID in the shipment upload is missing, invalid, or not associated with the vendor. |
Missing PO number |
The PO number in the shipment upload is missing. |
Missing PO line number |
The PO line number in the shipment upload is missing. |
PO number is invalid for vendor |
The PO number in the shipment upload is not associated with the vendor. |
PO number/line number invalid |
The PO line number is invalid for the PO number. |
PO line could not be determined based on item |
The PO line number could not be found, based on the item information in the shipment upload (retailer item number, vendor item number, UPC number). |
Invalid PO line number/item number combination |
The item (retailer item number, vendor item number, or UPC number) in the shipment upload is not associated with the PO line number defined in the shipment upload. |
Line already shipped |
The PO line is already in a shipped status. |
Line cancelled |
The PO line is in a cancelled status and cannot be shipped. |
Line unpulled |
The PO line is in an unpulled status and cannot be shipped. |
Line heldunpulled |
The PO line is in a heldunpulled status and cannot be shipped. |
Invalid internal reference number for PO line |
The internal reference number is not associated with the PO line number. |
Missing shipment date |
A shipment date is not defined for the PO line. |
Invalid shipment date |
The shipment date defined for the PO line is invalid or a future date. |
Shipped quantity greater than ordered quantity |
The shipped quantity defined for the PO line is greater than the ordered quantity. |
Shipped quantity less than ordered quantity |
The shipped quantity defined for the PO line is less than the ordered quantity. |
Invalid uom for PO line |
The unit of measure does not match the unit of measure on the PO line. |
PO line number could not be determined based on item due to invalid line status |
The status of the PO line number found, based on the item information in the shipment upload (retailer item number, vendor item number, UPC number), was not eligible for shipment (based on the Bypass shipment edit vendor preference). |
Invoice File Uploaded for Vendor email to the retailer
CWCollaborate sends the following email when the vendor uploads a new invoice file if it cannot reconcile one or more of the included invoices, either because of missing or inconsistent information, or because the invoice is out of balance.
The retailer can define an email address at the Invoice approval/rejection email field on the retailer preferences screen at the vendor, organization, or retailer level. The division-level email address is not used.
An email is also sent to the vendor at this time; see Invoice File Uploaded email to the vendor.
Subject: Invoice File Uploaded for BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has uploaded invoices which encountered problems during load:
Invoice #IN1130456 Reason: The invoice number already exists.
Out of Balance Invoice(s) Alert for Vendor email to the retailer (confirming an out of balance invoice)
CWCollaborate sends the following email when a vendor confirms an out of balance invoice at the create invoice recap screen.
The retailer can define an email address in the Invoice approval/rejection email field at the retailer preferences screen. CWCollaborate determines the correct email address to use by checking the vendor level first, then the organization and finally the retailer level. The division-level email address is not used.
Subject: Out of Balance Invoice(s) Alert for BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has confirmed an out of balance invoice:
Invoice IN1075 dated 12/04/2001.
Please access the View Invoice option to review and accept or reject the of Out of Balance invoices.
Out of Balance Invoice(s) Alert for Vendor email to the retailer (uploading an out of balance invoice)
CWCollaborate sends the following email when a vendor selects to notify the retailer of an out of balance invoice at the view invoices screen. Only invoices that the vendor uploads are eligible for such notification; when the vendor enters an invoice interactively in the system, the Out of Balance Invoice(s) Alert for Vendor email to the retailer (confirming an out of balance invoice) is generated instead.
The retailer can define an email address in the Invoice approval/reject email field at the retailer preferences screen. CWCollaborate determines the correct email address to use by checking the vendor level first, then the organization and finally the retailer level. The division-level email address is not used.
Subject: Out of Balance Invoice(s) Alert for BOTTGER COLLABORATE INDUSTRIES
Vendor BOTTGER COLLABORATE INDUSTRIES has submitted the following out of balance invoices:
Inv. Date |
Invoice Number |
Invoice Description |
12/11/2001 |
IN1101 |
shipments for 11/15 -- 11/30 |
Please access the View Invoice option to review and accept or reject the Out of Balance invoices.
Shipping Address Changes were Auto-Declined email to the retailer
CWCollaborate sends the following email when it automatically rejects a shipping address change uploaded by CWDirect because the purchase order has already shipped or canceled.
The retailer can define an email address in the PO status update email field at the retailer preferences screen. Only the retailer-level email address is used.
Subject: Shipping Address Changes were Auto-Declined
Shipping address changes have been declined on the following shipped/cancelled orders.
Retail Div |
Vendor |
Sales Order |
Purchase Order |
Customer Name |
002 |
BIRDS OF A FEATHER |
00005984-001 |
0001153 |
PETER VAN VOORHIS |
Address Change Errors email to the retailer
CWCollaborate sends the following email when a shipping address change uploaded by the retailer fails because the file was missing required data or included incorrect data.
The retailer can define an email address in the Error acknowledgement emails field at the retailer preferences screen. This email address is available at the retailer level only.
Subject: Address Change Errors
The following errors occurred while attempting to load address changes:
Sales Order Number: 00009984-001 Unable to retrieve Sales Order Header
Sales Order Number: 00009987-001 Unable to retrieve Sales Order Header
Ship Address Changes were Denied by Vendor email to the retailer
CWCollaborate sends the following email when a vendor declines a shipping address change uploaded by the retailer if, for example, the vendor cannot ship to the new address, or the purchase order is too far along in the fulfillment process to be changed.
The retailer can define an email address in the PO status update email field at the retailer preferences screen, at the vendor, organization, or retailer levels. The division-level email is not used.
Ship Address Changes were denied by BOTTGER COLLABORATE INDUSTRIES
Shipping address changes have been rejected by BOTTGER COLLABORATE INDUSTRIES on the following orders:
Retail Div |
Sales Order |
Purchase Order |
Customer Name |
002 |
00005912-001 |
0001075 |
MARGARET MAHONEY |
Comment: Package is already shipped
RA Upload Error emails to the retailer
CWCollaborate sends the following emails when new RAs and cancelled RAs are not loaded from CWDirect due to errors.
The retailer can define an email address in the Return notifications emails field on the retailer preferences screen at the retailer level. If the retailer ID or organization ID is invalid or blank for the record, the system uses the email address defined in the Properties file.
Possible errors:
• Invalid retailer ID
• Invalid organization ID
• Invalid purchase order number / line number
• Invalid sales order number for purchase order / line number
• Duplicate sales order / RA number combination
• Quantity to be returned greater than shipped
• Line already fully returned
• PO line has not been shipped
• Quantity to return must be greater than zero
• RA created date missing
• Return reason missing
• Return description missing
• Unable to insert Return Authorization line
• RA number is missing
• Unable to add the new return authorization
• RA line number must be an integer
• Quantity to return must be an integer
• A Return Authorization with the same number already exists
• Return already cancelled
New Return Authorization Errors email to the retailer
Subject: New Return Authorization errors
The following return authorizations could not be loaded into the system for the following reasons:
Retailer ID=EGOLF Org ID=032 RA #=00003238-001-001 Order #=00003238-001
PO #=0007731 Item #=VENDOR001 Qty=1
Error=A return authorization with the same number already exists.
Return Authorization Cancellation Errors email to the retailer
Subject: Return Authorization Cancellation errors
The following return authorization cancellations could not be loaded into the system for the following reasons:
Retailer ID=EGOLF Org ID=032 RA #=00003238-001-001 Order #=00003238-001
PO #=0007731 Item #=VENDOR001
Error=Invalid status - return already cancelled.
Vendor Return Upload Errors email to the retailer
CWCollaborate sends the following email when NEWRETURN files uploaded from the vendor’s OMS are not loaded into CWCollaborate due to errors. An email is not sent if the NEWRETURN file load is successful.
The retailer can define an email address in the Return notification emails field on the retailer preferences screen at the vendor, retail division, organization, or retailer level.
Subject: Vendor return upload errors
The following returns could not be loaded into the system for the following reasons
RetailerId :EGOLF Org Id :025 Return No :v6635 RA No : PO No :0003999 Item No : Qty :1 Error :PO number / PO line number invalid for the vendor and the sales order.
Thank you
Setting up the CWCollaborate Interface
If you are running version 5.0 of CWDirect, you should apply the CWCollaborate-CWDirect integration patch, (# 0001171) from your Integration Patch V.5.0 CD. Run this patch before completing the following setup instructions.
File Transport Mechanisms: FTP Codes
If you use FTP as a file transfer mechanism to send information to CWCollaborate, you must create FTP applications which define the internet address and FTP commands used to send the following information to CWCollaborate:
• Vendor download information sent when you use the Downloading CWCollaborate or Locate Vendor Information (ECSV) menu option
• Purchase order download information sent when you process drop ship purchase orders
• Cancellation requests
• Purchase order updates
You must then enter the FTP application codes in their associated system control value fields on the Drop Ship Integration Values screen (system control value H20). See System Control Values.
Important: FTP application codes must be identical in the corresponding system control values for all companies in a single environment. For example, the FTP ID - Cancellation Requests field must be populated with the same code, and the code must identify the same FTP script, for all companies in the environment.
See Chapter 63: Working with FTP Application (WFTP) for information about creating FTP scripts.
For sample FTP scripts for the CWCollaborate application, see the following system control value documentation:
• FTP ID - Vendor Download (H16)
• FTP ID - PO Download - New (H17)
• FTP ID - PO Download Changes (H35)
• FTP ID - PO Cost Changes (H78)
• FTP ID - Cancellation Requests (H18)
• FTP ID - Returns Download - New (H56)
• FTP ID - Return Updates (H58)
• FTP ID - AP Invoice Upload (H77)
File Transport Mechanisms: MQSeries
If you use IBM MQSeries as a file transfer mechanism to send information to CWCollaborate, you must install MQSeries on your CWDirect and CWCollaborate systems, and define, for each system:
• MQM Queue manager
• MQM Message queues
• MQM Channels
Important: MQ Series queues must be defined for each environment you use. The same queues are used for all companies in a single environment.
See Chapter 64: Working with CWCollaborate Message Queues (WCDC) for information about MQSeries.
Required system control values:
• Drop Ship Integration Values Screen (H20): this umbrella system control value defines whether your system uses the CWCollaborate interface to transmit information to CWCollaborate for processing drop ship orders, and allows you to define the retailer ID, drop ship lead days, communication mechanism and FTP values (if you use FTP as a transfer mechanism) for passing information to the CWCollaborate application. Enter Y if you use CWCollaborate. The following fields are included in the umbrella SCV:
• Use CWCollaborate/Locate (H13): controls whether the CDC Async and CDC Batch Jobs for CWCollaborate Integration becomes active, and whether a value of C (Collaborative Shipping Framework) can be associated with a vendor in the Vendor file.
• Retailer ID (H15): identifies the retailer within the CWCollaborate data base. This value is first defined in CWCollaborate, and then entered here.
• Drop Ship Lead Days (H36): the number of days you want to add to the date passed to CWCollaborate to calculate Expected ship date in CWDirect. See Calculating an Expected Ship Date for CWCollaborate Items.
• Communication Protocol (H37): the protocol you use to transmit information between CWCollaborate and CWDirect. Valid options are File Transport Mechanisms: FTP Codes or File Transport Mechanisms: MQSeries.
Note: This setting must be identical in the corresponding system control values for all companies in a single environment; all companies in a single environment should be set to MQ or all companies in a single environment should be set to FTP.
• If you use FTP as a file transfer mechanism, you must create FTP codes and enter them in the following fields (See Chapter 63: Working with FTP Application (WFTP)):
• FTP ID - Vendor Download: identifies the FTP script used to send vendor information to CWCollaborate
• FTP ID - PO Download - New: identifies the FTP script used to send new purchase order information to CWCollaborate
• FTP ID - PO Download Changes: identifies the FTP script used to send outbound PO address changes to CWCollaborate
• FTP ID - PO Cost Changes: identifies the FTP script used to send PO cost changes to CWCollaborate
• FTP ID - Cancellation Requests: identifies the FTP script used to send cancellation requests to CWCollaborate
• FTP ID - PO Updates: identifies the FTP script used to receive purchase order updates from CWCollaborate
• FTP ID - Returns Download - New: identifies the FTP script used to send new return or return authorization information to CWCollaborate
• FTP ID - Deleted RAs: identifies the FTP script used to send information about deleted return authorizations to CWCollaborate
• FTP ID - Return Updates: identifies the FTP script used to receive return information updates from CWCollaborate
• FTP ID - AP Invoice Upload: identifies the FTP script used to receive information about updated A/P invoice records from CWCollaborate
See the Drop Ship Integration Values Screen (H20).
System Control Values Related to CWCollaborate Backorder Card Processing:
• Unconditional Suppression of Backorder Card (F19): this system control value must be set to Nif you want to generate backorder notices for any items, including CWCollaborate drop ship items.
• Backorder Card Print Program (D04): must be set to a valid program (the standard program is BOR0008)
• Drop Ship Lead Days (H36): the number of days you want to add to the date passed to CWCollaborate to calculate Expected ship date in CWDirect.
• FTC -- # of Days for Items without Expected Ship Date (C71): the number of days the system adds to the backorder card processing date to create a new expected ship date When the Expected Ship Date Expires with No Shipment.
Note: The FTC - Number of Days to Add for Special Handling (C67) and FTC - Number of Days to Add for Drop Ships (C68), and Number of Days to Delay Initial Backorder Notice (D89) system control values, which define values used for non-collaborative drop ship items, do not apply to CWCollaborate items.
For more information: For additional system control values related to backorder card processing for all items, see Customer Service Chapter 116: Purchase Order Layering and Backorder Notifications.
System Control Values Related to Returns
• Refund Freight Default for Inbound Returns (H59): determines whether to refund freight on a vendor-initiated return without an RA (return against a PO)
• Refund Additional Charge Default for Inbound Returns (H60): determines whether to refund additional charges on a vendor-initiated return without an RA (return against a PO)
• Refund Handling Default for Inbound Returns (H61): determines whether to refund freight on a vendor-initiated return without an RA (return against a PO)
• Refund Duty Default for Inbound Returns (H62): determines whether to refund freight on a vendor-initiated return without an RA (return against a PO)
• Default Return Reason Code for Inbound Returns (H63): determines which return reason to use for a vendor-initiated return without an RA (return against a PO) when the return does not have a valid return reason.
• Default Additional Charge Code for Inbound Returns (H64): determines whether to refund vendor’s return postage on a vendor-initiated return without an RA (return against a PO); enter a valid additional charge code to have vendor’s return postage amount refunded to the customer as an additional charge credit.
• Default Return Disposition Code for Inbound Returns (H65): determines which return disposition code to use for a vendor-initiated return without an RA (return against a PO).
System control values related to the A/P invoice upload: See A/P Invoice Upload Setup for a complete list.
Optional system control values:
• SKU Element Defining Color (H21): Determines which SKU element defines color when interfacing from CWDirect to other systems. CWCollaborate does not separate split SKU information from base item information. You may wish to use this system control value for informational and data retrieval purposes.
• SKU Element Defining Size (H22): defines which SKU element defines size when interfacing from CWDirect to other systems.
• SKU Element Defining Size 2 (H23): defines which SKU element defines size 2 when interfacing from CWDirect to other systems.
• Authorize Only Merchandise for Drop Ship Picks (C92): defines whether the system authorizes only the merchandise amount on a CWCollaborate drop ship purchase order (if the drop ship item is the only item left to be shipped on the order). If there are other items left to be shipped on the order, only the merchandise amount is authorized on a drop ship purchase order, regardless of the setting of this system control value.
• Print Drop Ship Invoice with PO (C85): regardless of the setting of this system control value, the system does not print drop ship invoices for CWCollaborate drop ship orders. See Chapter 6: Selecting Vendors for Drop Ship Processing (MDSP).
• PO Default Status (A49): regardless of the setting of this system control value, CWCollaborate drop ship purchase orders are created in an OPEN status.
• Print Drop Ship Invoice at time of Purchase Order Receiving (F10): if this system control value is set to Y, the system prints a drop ship invoice when you receive a drop ship purchase order using the Select PO for Receipt (PORC) menu option.
• Default Item Unit of Measure (B33): CWCollaborate requires that you define a unit of measure for each drop ship item processed. If the item does not have a Unit/measure (Unit of measure) defined in the Item file, CWDirect uses the unit specified in system control value B33. If there is no Unit of measure defined for the item, and no Unit of measure defined in this system control value, CWCollaborate defines the unit of measure on the drop ship purchase order as EA.
• Include HDL Warehouse Value on Order Detail (J54): Enter Y in this system control value if you want the system to automatically assign an HDL (Home Delivery Service) to an order line during reservation, based on the warehouse list associated with the SCF of the order ship to. If the item on the order line is a drop ship item, the system sends the HDL code and address information to CWCollaborate in the new PO message. This way, the vendor that supplies the item knows which home delivery service to use to deliver the item to the customer. See HDL (Home Delivery Service) Processing.
Important: If you have specified a unit of measure for the vendor item, it must match the unit of measure specified for the item in the Item file. See Chapter 22: Working with Vendor Items (WVNI).
Order Maintenance Access (A22): You must have authority to this secured feature to initiate a cancel request.
Item Setup
For each drop ship item you process through CWCollaborate, you should specify a unit of measure for the item. This unit of measure must match the unit of measure you specify for the item in the Vendor Item file. Additionally, in order to create accurate Expected ship dates for your items, it is important that you enter accurate Lead days for each item in the Vendor Item file. See Calculating an Expected Ship Date for CWCollaborate Items.
For each vendor who uses CWCollaborate to process your drop ship orders, enter C in the Drop ship output field on the Second Create Vendor Screen.
For each vendor who uses CWCollaborate to process drop ship returns, enter Y in the Send returns to Collaborate field on the Second Create Vendor Screen.
To use the CWCollaborate interface with CWDirect versions 4.2 or earlier, you must run the CWDirect Version 5.0 Patch associated with the CWCollaborate interface to replace the Drop ship picks field in the Vendor file with the Drop ship output field, and you must enter C in this field for each vendor for whom you use CWCollaborate to process drop ship orders. See Merchandising Chapter 19: Working with Vendors (WVEN).
Additionally, you should enter an email address for each collaborative vendor in the Vendor Contact file.
Note: If your vendor enters an email address on the CWCollaborate Administration/Vendor Preferences screen or you as a retailer enter an email address on the CWCollaborate Vendor Profile screen, the system uses the CWCollaborate-entered email addresses instead of the email address you enter here for sending new PO notifications or cancellation requests to your vendor. Entering a different address on the CWCollaborate screens, however, does not update the address you enter here.
Optionally, you can use menu option Downloading CWCollaborate or Locate Vendor Information (ECSV) to initially transmit vendor information to CWCollaborate for all vendors defined as Collaborative (Drop ship output = C). If CWCollaborate already has information for a vendor, this menu option does not overwrite the information.
Vendor information is also passed to CWCollaborate when you process a drop ship purchase order. If the vendor has not been previously created, CWCollaborate creates the vendor. If the vendor already exists in CWCollaborate, the vendor’s data is updated.
• Downloading CWCollaborate or Locate Vendor Information (ECSV): allows you to initially transmit vendor information to CWCollaborate for all vendors defined in the Vendor file as Collaborative (Drop ship output = C). After you have set up the CWCollaborate interface, information for a new, collaborative vendor is passed to CWCollaborate when you process the first drop ship purchase order for the new vendor.
• Working with Retail Brands (WRBD): allows you to create and maintain retail brands, and associate them with one or more entities in your company. You must set up retail brands in order to use CWCollaborate. Each retail brand must be associated with at least one entity. Entities are associated with divisions; the source code on an order must point to the division associated with the entity for which you have set up retail brands. See Chapter 60: Working with Retail Brands (WRBD) for more information.
• Displaying Unprocessed Drop Ship Items (DUDS): allows you to review all drop ship order detail lines that have been entered but not yet processed through the MDSP menu option.
• Printing Drop Ship Integration Reports (PDSR): allows you to print the following reports:
• Drop Ship Integration Items on Hold from Vendor Report
• Drop Ship Integration Items Revised Due Date Report
• Drop Ship Items Pending Cancellation
• Drop Ship Items Confirmed Cancellation
• Drop Ship Items Pending Shipment
• Working with FTP Application (WFTP): allows you to create an FTP application, and to define the internet address and define or change the FTP commands associated with the application.
• Working with CWCollaborate Message Queues (WCDC): allows you to create MQ Message queues and channels if you use MQSeries as a file transfer mechanism.
• Working with Entities (WENT): a new field, Retail brand, on the Create/Change/Display Entities screens allows you to associate a retail brand with an entity. This field does not display if the Use CWCollaborate/Locate on the Drop Ship Integration Values Screen (H20) is set to N. See Chapter 60: Working with Retail Brands (WRBD).
• WMS Background Jobs (WPBJ): you must start the CDC job in order to process CWCollaborate transactions subsequent to creating and sending purchase order information. You can start the job using the WMS Background Jobs menu option.
• Working with Drop Ship Errors (WDSE): allows you to review CWCollaborate file transfer errors and delete the records in error from the Drop Ship Transaction file (FLCSFT).
• Working with A/P Invoice Upload Errors (WAPU): allows you to review and correct any errors related to invoices from your vendors uploaded from CWCollaborate.
| Part G: CWCollaborate and Locate Drop Ship Integration | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 58: Locate Supplier Direct Fulfillment Interface |
FU07_01 CWDirect 18.0 August 2015 OTN