Supplier Direct Fulfillment Processing

Purpose: Locate’s Supplier Direct Fulfillment module is a 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.

Locate and its Supplier Direct Fulfillment module are sold as separate products. For more information about purchasing Locate’s Supplier Direct Fulfillment, contact your MICROS representative.

In this topic:

Supplier Direct Fulfillment Information Flow

What Does CWSerenade send to Locate’s Supplier Direct Fulfillment Module?

What Does Locate’s Supplier Direct Fulfillment Module send to CWSerenade?

Creating or Updating Vendors in Locate

Creating Drop Ship Orders for Locate’s Supplier Direct Fulfillment Module

Sending Drop Ship Purchase Order Information to the Supplier Direct Fulfillment Module

Viewing Errors and Re-entering Orders in Error

Shipping Orders through the Supplier Direct Fulfillment Module

Posting Invoices from Locate

Updates to Locate Drop Ship Purchase Orders

Cancelling Locate Drop Ship Order Lines

Changing Address and Cost Information

Drop Ship Reports

Supplier Direct Fulfillment Backorder Notice Processing

Sample Drop Ship Messages between CWSerenade and Locate

CreateDSVendor Message Samples

CreateDSOrder Message Samples

GetDSChanges Message Samples

GetDSInvoices Message Samples

SetDSCancel Message Samples

SetDSAddressChange Message Samples

SetDSCostChange Message Samples

Supplier Direct Fulfillment Information Flow

In this topic:

What Does CWSerenade send to Locate’s Supplier Direct Fulfillment Module?

What Does Locate’s Supplier Direct Fulfillment Module send to CWSerenade?

Creating Drop Ship Orders for Locate’s Supplier Direct Fulfillment Module

Sending Drop Ship Purchase Order Information to the Supplier Direct Fulfillment Module

Viewing Errors and Re-entering Orders in Error

Shipping Orders through the Supplier Direct Fulfillment Module

Posting Invoices from Locate

What Does CWSerenade send to Locate’s Supplier Direct Fulfillment Module?

CWSerenade sends the following information to Locate for Supplier Direct Fulfillment:

• Vendor: current name and address

• New purchase orders

• Purchase order address changes

• Purchase order cost changes

• Purchase order cancel requests

What Does Locate’s Supplier Direct Fulfillment Module send to CWSerenade?

Locate’s Supplier Direct Fulfillment module sends the following information to CWSerenade:

• Purchase order acknowledgements

• Purchase order updates, including address change and cancellation acceptances or rejections, status changes, and changes to accepted ship dates

• Purchase order shipment confirmations

• Posted invoices

Creating or Updating Vendors in Locate

CWSerenade sends the CreateDSVendor message for each vendor whose Drop ship output field on the Second Create Vendor Screen to Locate drop shipping when you use the Downloading Drop Ship Vendors (ECSV) option. If the vendor already exists in Locate, the existing information is overwritten. See the CreateDSVendor Message Samples for the vendor information that CWSerenade sends to Locate.

You can also use the Locate screens to create or update a vendor, and need to use these screens to specify additional vendor configuration options, such as assignment of carriers (ship vias), pack slip output, and the creation of vendor user IDs who can log into the Vendor Portal.

Note: You can also create a vendor through the CreateDSOrder message sent through Selecting Vendors for Drop Ship Processing (MDSP) if the vendor does not already exist in Locate; however, this creates the vendor with minimal information, and you will need to complete vendor setup, typically through the Locate screens.

Creating Drop Ship Orders for Locate’s Supplier Direct Fulfillment Module

You must identify the vendor for each item flagged for drop ship, and typically use the vendor item record to specify additional information about the item to include on the purchase order. You flag a drop ship vendor to use Locate’s Supplier Direct Fulfillment module by setting the vendor’s Drop ship output field to Locate drop shipping. The Selecting Vendors for Drop Ship Processing (MDSP) option determines whether to send purchase orders to Locate based on this setting.

You can view all unprocessed drop ship orders, regardless of whether the vendor is flagged for Locate drop shipping, collaborative shipping through CWCollaborate, or any other setting, using the Displaying Unprocessed Drop Ship Items (DUDS) menu option.

D/S PO history: When you create the purchase order through Selecting Vendors for Drop Ship Processing (MDSP), the Display P/O Drop Ship Screen displays the message: Drop Ship PO Created.

Sending Drop Ship Purchase Order Information to the Supplier Direct Fulfillment Module

You create and send drop ship purchase orders through the Selecting Vendors for Drop Ship Processing (MDSP) menu option. For drop ship purchase orders whose vendors are flagged for Locate drop shipping, the system:

• Creates drop ship purchase order records.

• Sends the CreateDSOrder message to Locate to create the purchase order for any drop ship items on the order for each vendor. Multiple items are included on the same purchase for a vendor, regardless of whether the items are flagged to ship alone. See the CreateDSOrder Message Samples for details on the information included in the message.

When Locate receives a purchase order, it sends an email notification to the vendor indicating that there are drop ship purchase orders to be fulfilled.

The vendor can access the purchase order information in the Locate Vendor Portal. 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 also print or reprint a drop ship purchase order using the Print PO and Receiving Worksheets (PPWS) or Printing Purchase Orders (MPRP) menu options. Printing or reprinting a drop ship purchase order does not resend the purchase order to Locate.

D/S PO history: When CWSerenade sends the purchase order to Locate, the Display P/O Drop Ship Screen displays the message: PO available to vendor.

Required Information in Locate

When you use Selecting Vendors for Drop Ship Processing (MDSP) to send a new drop ship purchase order to Locate through the CreateDSOrder message, the information in the message includes:

vendor: If the vendor does not already exist in Locate, Locate creates the record using the vendor code, name, and email address specified; however, this is the only vendor information included in the CreateDSOrder message, and you will need to complete vendor configuration in Locate. See Creating or Updating Vendors in Locate for information on sending current vendor name and address information to Locate.

Locate does not update an existing vendor based on the code, name, or email address passed in the CreateDSOrder message.

carrier: If the ship via does not already exist in Locate as a valid carrier, Locate creates a new carrier based on the ship via code; however, this is the only carrier information included in the CreateDSOrder message, and you will need to complete carrier configuration in Locate. If the ship via code is a single position, it is passed with a padding zero; for example, a code of 7 is passed as 07.

item: If the item does not already exist in Locate as a valid item, and CWSerenade is the system of record in your Locate organization, Locate creates the item and vendor item, using the information passed in the CreateDSOrder message.

The drop ship item and vendor item in Locate do not need to match an existing product imported into Locate as part of Order Broker processing, and the item does not need to be flagged as Locate eligible in CWSerenade.

brand: The brand you set up through Working with Retail Brands (WRBD) must match a brand you have created in Locate.

For more information: See the CreateDSOrder Message Samples for details on the data passed to Locate from CWSerenade.

Special Handling on Orders Sent to the Supplier Direct Fulfillment Module

The Supplier Direct Fulfillment interface supports only custom special handling for drop ship items. See the Work with Special Handling Screen for information on entering custom special handling instructions.

To set up custom special handling for a drop ship item, see Establishing Custom Special Handling Formats (WSHF).

Order and Gift Messages

The Supplier Direct Fulfillment interface sends the following messages for a drop ship purchase order:

Order messages or gift messages: Up to 8 total order header (sales order) messages with a Print flag setting of Picks, Both, or Gift msg can print below the ship-to address at the top of the pack slip.

Order line messages: You can send up to 99 order line messages for a drop ship order line. Order line messages identified in CWSerenade with a Print flag setting of Picks or Both print below the order line on the pack slip.

See Adding Order Messages.

Viewing Errors and Re-entering Orders in Error

You can use the Working with Drop Ship Errors (WDSE) menu option to review different types of drop ship errors, including errors related to sending a purchase order to Locate.

You cannot resend a drop ship purchase order if Locate does not receive it; instead, you can recreate the order as a new order to process it, or retrieve the CreateDSOrder message from Locate’s xml_ds.log and resend it to Locate if the message was logged.

Requesting Updates from Locate

To obtain updates on vendor activity related to drop ship purchase orders, the CDC async job periodically sends the GetDSChanges request message to Locate for each company whose Use CWCollaborate/Locate (H13) system control value is selected. Possible activities include:

• generating the pack slip

• acknowledgement of the purchase order from an integrated vendor

• shipment: see Shipping Orders through the Supplier Direct Fulfillment Module

• acceptances or rejections of cancel requests: see Cancelling Locate Drop Ship Order Lines

• vendor changes to due dates or a purchase order line’s hold status: see GetDSChanges Message Samples

Examples: See the event listing under the GetDSChanges Response Message from Locate for examples of updates, and see the Display P/O Drop Ship Screen for examples of the related history messages.

How many changes sent? The CW_LOCATE_PURCHASING_SERVICES_MAX_UPDATES in the Locate Properties File determines the maximum number of changes to request for each company at a time. If the number of changes since the last request exceeds this maximum, Locate sends any additional changes in response to the next GetDSChanges request.

Shipping Orders through the Supplier Direct Fulfillment Module

When your vendor completes shipment of a drop ship purchase order line, the CWSerenade purchase order line is closed, and the corresponding CWSerenade order line is also closed. CWSerenade automatically performs shipment confirmation updates for the order and the purchase order.

Depending on the carrier settings you have specified in Locate, vendors may be required to enter or upload shipping-related information (including carrier (ship via), tracking number, rate, weight, and ship date) for shipments. This shipment information is transmitted to CWSerenade and can be available to the customer through, for example, the shipment confirmation email.

If the carrier does not match a valid ship via: If the carrier passed for a shipment in the GetDSChanges response message does not match a valid ship via, CWSerenade uses the existing ship via on the order. In this case, the tracking number link in the shipment confirmation email might not be a valid link for the ship via indicated.

CWSerenade does not require that there be a valid SCF/ship via record for the carrier passed for the shipment and the shipping address on the order.

Locate sends shipment information to CWSerenade in the GetDSChanges response message. See the GetDSChanges Message Samples for more information.

D/S PO history: When CWSerenade receives a shipment confirmation update from Locate, the Display P/O Drop Ship Screen displays a message such as: Item Shipped 11/02/13.

Posting Invoices from Locate

You can enable your vendors to submit A/P invoices through Locate, and include one or more purchase orders on each invoice. Locate sends invoices to CWSerenade in the GetDSInvoices response message. In Locate, you can specify for each vendor:

• whether the vendor can submit invoices

• whether the vendor must specify an invoice number when confirming shipment

• the percentage unit cost variance allowed for the vendor without requiring you to approve the invoice

To obtain invoices for drop shipments, the CDC async job periodically sends the GetDSInvoices request message to Locate for each company whose Use CWCollaborate/Locate (H13) system control value is selected. The GetDSInvoices response message includes any newly posted invoices from vendors.

How many invoices sent? The CW_LOCATE_PURCHASING_SERVICES_MAX_INVOICES in the Locate Properties File determines the maximum number of invoices to request for each company at a time. If the number of invoices since the last request exceeds this maximum, Locate sends any additional invoices in response to the next GetDSInvoices request.

Splitting invoices by purchase order: CWSerenade creates a separate invoice for each purchase order included in the invoice submitted from Locate, assigning the CWSerenade invoice number by appending a hyphen and numeric suffix to the invoice number passed from Locate. For example, if the vendor passes invoice number ABC123 for three purchase orders, CWSerenade creates invoice ABC123-1, ABC123-2, and ABC123-3.

Limiting the number of purchase orders per invoice: Use the Max POs / Invoice setting at the Drop Ship Preferences screen in Locate to control the number of purchase orders that a vendor can assign to a single invoice. This setting automatically controls the setting of the Invoice Number Length, preventing the total invoice number to assign in Locate plus the hyphen and suffix from exceeding the length of the CWSerenade invoice number field (11 positions).

Example: You set the Max POs / Invoice field in Locate to 50. To allow for the hyphen (1 position) and up to 50 purchase orders (2 positions), Locate automatically sets the Invoice Number Length to 8 positions, preventing the vendor from entering an invoice number that exceeds this length.

Out-of-balance? If the vendor has changed the unit price on a purchase order line so that it exceeds or falls below the original cost by the Unit Cost Threshold you have specified for the vendor in Locate, the invoice does not post to CWSerenade unless you approve the invoice in Locate.

An invoice does not require your approval in Locate if the vendor adds freight, handling, or other charges to the invoice header or detail. You use the Vendor Extended record in CWSerenade to control the maximum freight, handling, and other charges for an invoice.

D/S PO history: When CWSerenade receives an invoice posted from Locate, the Display P/O Drop Ship Screen displays a message for the shipment, such as: AP Invoice IN0913b/Line 00003 Received. The line number indicated is the invoice detail line for the merchandise, rather than any freight, handling, or other charge.

For more information: See Working with A/P Invoice Upload Errors (WAPU) for an overview on uploading A/P invoices from Locate including setup options, the edits applied by CWSerenade, and how to correct errors. Also, see the GetDSInvoices Message Samples for details on the invoice information sent from Locate.

Updates to Locate Drop Ship Purchase Orders

Overview: The changes that you can apply to purchase orders once they are sent to Locate are described below.

Note: Changes can be applied to purchase orders only if the vendor uses the Vendor Portal screens. If the vendor uses the vendor integration rather than Vendor Portal screens to work with purchase orders, the changes are not sent to the integrated vendor’s system.

Cancelling Locate Drop Ship Order Lines

Changing Address and Cost Information

Cancelling Locate Drop Ship Order Lines

You can request to cancel a Locate drop ship order line at the Display P/O Drop Ship Screen, available through standard Order Inquiry or Purchase Order Inquiry. CWSerenade sends the SetDSCancel message to Locate. It is not possible to cancel a partial quantity. If the vendor has:

• not yet generated a pack slip for the purchase order line, Locate cancels the line automatically. The cancellation is noted in the next GetDSChanges response message from Locate, and CWSerenade cancels the line.

• already generated a pack slip for the purchase order line or put the line on hold, Locate notifies the vendor that there is a cancellation request pending and displays related messages on various screens in the Vendor Portal. If the vendor:

• accepts the cancel request, Locate cancels the line automatically. The cancellation is noted in the next GetDSChanges response message from Locate, and CWSerenade cancels the line. Similarly, if the line goes back to New Order status in Locate if the vendor voids the pack slip, Locate cancels the line automatically.

• declines the cancel request Locate does not cancel the line. Locate sends an email notification to your PO Status Notification email address specified through its Drop Ship Preferences screen. The rejection is noted in the next GetDSChanges response message from Locate, and CWSerenade does not cancel the line.

• confirms shipment without responding to a cancel request, Locate closes the purchase order line. The shipment is noted in the next GetDSChanges response message from Locate, and CWSerenade bills the line.

If line is already shipped? If the cancel request arrives in CWSerenade after the vendor has confirmed shipment of the line, Locate automatically rejects the cancel request and does not perform any additional updates, but does send an email notification to your PO Status Notification email address specified through its Drop Ship Preferences screen.

You can generate a report of pending cancellation requests using the Printing Drop Ship Reports (PDSR) menu option. See Drop Ship Reports.

D/S PO history: When you send a cancellation request to Locate, the Display P/O Drop Ship Screen displays the message: Cancel Request Sent. If:

• the vendor declines the cancel request, the message is Cancel Request Rejected.

• the vendor accepts the cancel request, or the cancellation applies automatically because the vendor has not yet begun processing the purchase order, the message is Cancel Request Confirmed

• the cancellation is rejected automatically because the vendor has shipped the line, there is no message noting the automatic rejection.

Secured feature: If you have authority to the Cancel Collaborate/Locate Drop Ship PO (J04) secured feature, you can cancel a Locate drop ship purchase order line using the Cancel option on the PO Maintenance - Maintain Detail Screen. In this situation, the system does not send a cancel request to Locate and instead immediately performs a full cancellation, cancelling the purchase order line and order line, removing the printed quantity on the order line, writing an order transaction history message: DS PO line canceled, and updating the drop ship status of the line to cancelled.

Note:

• The only situation in which you should use the Cancel option on the PO Maintenance - Maintain Detail Screen to cancel a Locate drop ship purchase order line is if you have previously sent a cancel request to Locate and did not receive a response indicating whether the vendor confirmed or rejected the cancellation.

• Because the cancellation updates the drop ship status of the line to cancelled, you cannot use the cancel request option on the Display P/O Drop Ship Screen to send a cancellation request to Locate. However, if Locate returns an update in the GetDSChanges response message for the order line that updates its status to an open status, such as Held, after the cancellation has been performed, you can use the cancel request option to send a cancellation request to Locate.

• If the GetDSChanges response message includes a shipment confirmation from Locate after the line has been cancelled, CWSerenade does not update the line as shipped, but does update order transaction history with the shipment confirmation.

For more information: See the SetDSCancel Message Samples for details on the information sent to Locate for a cancellation request.

Changing Address and Cost Information

Changing Address Information

Changing Cost Information

Changing Address Information

When you maintain an order that includes at least one Locate drop ship PO line item which has been sent to Locate and has not yet been shipped, and the changes to the order include an update to the ship-to address, CWSerenade sends the updated address information to Locate in the SetDSAddressChange message.

Sold-to same as ship-to? If the sold-to and the ship-to address are the same, then the SetDSAddressChange message includes a flag indicating to apply the same update to both.

Updates in Locate: Locate creates a record of the original and changed ship-to address and:

• If all lines on the PO are in a new (not in process) status, automatically updates the address information and does not generate an email to the vendor.

• If any line on the PO is already in process, generates an email notification to the vendor about the requested address change; also, various screens in the Vendor Portal display a warning message about the requested change. If the vendor:

• declines the address change, Locate sends an email notification of the rejection to your PO Status Notification email address specified through its Drop Ship Preferences screen.

• accepts the address change, Locate updates the address for all open (unshipped, uncanceled) lines.The vendor then needs to void and reprint the pack slip in order to generate a pack slip with the correct address.

• If all lines on the PO are in shipped or cancelled status, Locate automatically rejects the address change and sends an email notification of the rejection to your PO Status Notification email address specified through its Drop Ship Preferences screen.

Conditions:

• If you update a customer’s address in any way besides using order maintenance to maintain the order that includes the drop ship purchase order, the address change is not sent to Locate.

• If there are additional open purchase orders for the same customer being fulfilled through the Supplier Direct Fulfillment module, CWSerenade does not send address updates to Locate for these purchase orders.

• If you change the sold-to customer’s address but the order is shipping to a different address, CWSerenade does not send an address update to Locate.

• If you change information that is not part of the shipping address, CWSerenade does not send an address update to Locate.

D/S PO history: When you send an address change request to Locate, the Display P/O Drop Ship Screen displays the message: Address change sent to vendor. No additional drop ship purchase order history is written for address changes, regardless of vendor action or automatic acceptance or rejection.

For more information: See the SetDSAddressChange Message Samples for details on the information sent to Locate for an address change request.

Changing Cost Information

When you update the Cost field on the PO Maintenance - Change PO Detail Screen, CWSerenade sends the SetDSCostChange message to Locate. Locate creates a record of the original and updated PO cost, and updates the PO with the new cost. No action by the vendor is required.

D/S PO history: When you change the cost of a purchase order line, the Display P/O Drop Ship Screen displays the message Cost change sent to vendor if you advance to the screen through Purchase Order Maintenance (MPOI). This message is not displayed in order inquiry.

For more information: See the SetDSCostChange Message Samples for details on the information sent to Locate for a cost change request.

Drop Ship Reports

You can use the Printing Drop Ship Reports (PDSR) menu option to generate reports for drop ship purchase orders fulfilled through the Supplier Direct Fulfillment module:

Drop Ship Items on Hold from Vendor Report

Drop Ship Items with Revised Due Date Report

Drop Ship Items Pending Cancellation Report

Drop Ship Items Confirmed Cancellation Report

Drop Ship Items Sent to Integrated System Report

Drop Ship Items Pending Shipment Report

Drop Ship Items Shipped Report

Supplier Direct Fulfillment Backorder Notice Processing

Backorder notices for drop ship items fulfilled through the Supplier Direct Fulfillment module are based on accurate expected ship date information that your vendors communicate to CWSerenade. Because expected shipment information is readily available for these drop ship items, the interface evaluates drop ship items for backorder notices in a manner similar to the way it evaluates non-drop-ship backordered items. The integration offers the following advantages over regular drop ship processing:

• When you enter an order for a drop ship item fulfilled through the Supplier Direct Fulfillment module, the system calculates an expected ship date based on vendor item Lead days plus the CDC Drop Ship Lead Days (H36).

• When your vendor revises the expected ship date for a drop ship order line, the expected ship date is updated on the CWSerenade order. This updated expected ship date is included on the backorder notice to the customer.

• Drop ship items fulfilled through the Supplier Direct Fulfillment module are eligible for immediate backorder card notices, if immediate notices are selected for the order type.

Setup for backorder notifications: If you want to generate backorder notices for an item fulfilled through the Supplier Direct Fulfillment module:

• leave the Suppress backorder card field in the SKU table unselected.

• make sure the Unconditional Suppression of Backorder Card (F19) system control value is unselected.

• set accurate Lead days for the vendor item, using the Working with Vendor Items (WVNI) menu option.

• set the CDC Drop Ship Lead Days (H36) system control value to the number of days you want to add to the date passed to Locate to calculate the Expected ship date in CWSerenade.

Due date calculation: For a purchase order line fulfilled through the Supplier Direct Fulfillment interface, the due date sent to the vendor and the Expected ship date to present to the customer are calculated as: Current date + Vendor item Lead days + CDC Drop Ship Lead Days (H36).

Future arrival date? An order line with a future Arrival date will not be eligible for processing through Selecting Vendors for Drop Ship Processing (MDSP) until the line’s Arrival date is within the vendor item lead days for the item plus the CDC Drop Ship Lead Days (H36).

When the expected ship date passes with no shipment: If the Expected ship date passes, the Next BO card date has been reached, and the item has not been shipped, the backorder notification program generates a notification to the customer. In this case, the new Expected ship date reported to the customer is calculated by adding the FTC -- # of to the date you generate the backorder notices.

Example: When the expected ship date passes but the order has not shipped:

• Order date: 9/10

• Arrival date: 9/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]: 9/27

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

Date

Action

Backorder Notice Result (GBOC)

9/10

You enter the order.

No notice is produced (Immediate Backorder Notification is set to N). Expected ship date on the order is 9/27.

9/27

Expected ship date expires but the order has not shipped.

Backorder notice is generated with new expected ship date: 10/25.

(9/27 + FTC -- # of Days for Items without Expected Ship Date (C71)).

When the vendor revises the expected ship date: When the vendor revises an expected ship date, the system updates the Expected ship date to reflect your vendor’s entry. If the Expected ship date is later than the date calculated when you entered the order, and the Next BO card date for the line has been reached, the backorder notification program generates a notification with the revised date the next time you generate notifications.

See System Control Values Related to Locate’s Supplier Direct Fulfillment Module for information on system control value settings.

Example:

• Order date: 9/10

• Arrival date: 9/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]: 9/27

Date

Action

Backorder Notice Result (GBOC)

9/10

You enter the order.

No notice is produced (Immediate Backorder Notification for the order type is unselected). Expected ship date on the line is 9/27.

9/20

Your vendor revises the expected ship date to 10/14.

If the Next BO card date has been reached, a backorder notice is generated with the new expected ship date of 10/14.

10/14

Expected ship date expires but the order has not shipped.

If the Next BO card date has been reached, a backorder notice is generated with the new expected ship date of 11/13 (10/14 + FTC -- # of Days for Items without Expected Ship Date (C71)).

Immediate backorder notice? For drop ship items processed through the Supplier Direct Fulfillment interface, you have the option to generate immediate backorder notifications to inform your customers of an accurate expected delivery date. Immediate backorder notifications are controlled by Immediate B/O notice setting for the order type, set up in the Establishing Order Types (WOTY) menu option.

Note: The Number of Days to Delay Initial Backorder Notice (D89) system control value does not apply to items fulfilled through the Supplier Direct Fulfillment module.

Sample Drop Ship Messages between CWSerenade and Locate

Purpose: Below are samples of the messages passed between CWSerenade and Locate to support the Supplier Direct Fulfillment integration.

For more information: See the Locate Operations Guide for complete descriptions of these messages.

CreateDSVendor Message Samples

CreateDSVendor Request Message to Locate

CreateDSVendor Response Message from Locate

CreateDSOrder Message Samples

CreateDSOrder Message to Locate

CreateDSOrder Response Message from Locate

GetDSChanges Message Samples

GetDSChanges Message to Locate

GetDSChanges Response Message from Locate

GetDSInvoices Message Samples

GetDSInvoices Message to Locate

GetDSInvoices Response Message from Locate

SetDSCancel Message Samples

SetDSCancel Message to Locate

SetDSCancel Response Message from Locate

SetDSAddressChange Message Samples

SetDSAddressChange Message to Locate

SetDSAddressChange Response Message from Locate

SetDSCostChange Message Samples

SetDSCostChange Message to Locate

SetDSCostChange Response Message from Locate

CreateDSVendor Message Samples

Purpose: CWSerenade sends the CreateDSVendor message for each vendor whose Drop ship output field on the Second Create Vendor Screen to Locate drop shipping when you use the Downloading Drop Ship Vendors (ECSV) option.

For more information: See the Downloading Drop Ship Vendors (ECSV) option and the Locate Operations Guide.

CreateDSVendor Request Message to Locate

Information in this message includes:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

• destination = from the Locate Account (K49) system control value

requesting_system_cd = from tthe Locate System (K50) system control value

vendor_cd = the CWSerenade vendor number

• vendor name, contact name, and address information = from the vendor name and address (not the remit-to address or the contact address), however:

• the email address is from the first vendor contact record that you created (not based on the vendor contact sequence number)

• the address includes a maximum of 3 address lines

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:CreateDSVendor xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:create_ds_vendor_request_message>

<message_header>

<datetime>2013-09-09</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<vendor>

<requesting_system_cd>6</requesting_system_cd>

<vendor_cd>257</vendor_cd>

<vendor_name>FAIR TRADE CLOTHING </vendor_name>

<address1>12345 EXAMPLE STREET</address1>

<address2></address2>

<address3></address3>

<address4></address4>

<suite></suite>

<city>WESTBOROUGH</city>

<province>MA</province>

<postal>01581</postal>

<country>USA</country>

<email>example@example.com</email>

<telephone></telephone>

<ext></ext

<fax></fax>

<contact_name></contact_name>

</vendor>

</message_body>

</ns2:create_ds_vendor_request_message>

</ns2:CreateDSVendor>

</soap:Body>

</soap:Envelope>

CreateDSVendor Response Message from Locate

Locate returns a response such as the following when it receives the CreateDSVendor request message.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:CreateDSVendorResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<create_ds_vendor_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-09T16:40:43.668</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<response response_code="0" vendor_cd="257">

<response_description>Vendor Updated</response_description>

</response>

</message_body>

</create_ds_vendor_response_message>

</ns2:CreateDSVendorResponse>

</soap:Body>

</soap:Envelope>

CreateDSOrder Message Samples

Purpose: When you use the Selecting Vendors for Drop Ship Processing (MDSP) menu option to generate drop ship purchase orders, CWSerenade uses a message such as the following to send drop ship purchase orders to Locate for vendors whose Drop ship output field is set to Locate drop shipping.

For more information: See Sending Drop Ship Purchase Order Information to the Supplier Direct Fulfillment Module and the Locate Operations Guide.

CreateDSOrder Message to Locate

Information in this message includes:

po_header:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

destination = from the Locate Account (K49) system control value

po_no = the CWSerenade purchase order number

brand_cd = The code identifying the retail brand associated with the source code on an order header. Must be a valid brand in Locate. A retail brand links to a source code through the entity associated with the division specified for the source code. See Working with Retail Brands (WRBD) for more information.

vendor_cd = The code identifying the vendor. If this code does not match an existing vendor in Locate, Locate creates a new vendor, using this code, the vendor_name, and the vendor_email; however, additional configuration is required for the vendor’s preferences, assigned carriers, and user profiles with authority the Vendor Portal. If the vendor already exists in Locate, the CreateDSOrder message does not update the name or email address.

requesting_system_cd = from tthe Locate System (K50) system control value

requesting_location_cd = from the Locate Default Location (K51) system control value

buyer_cd and buyer_name = from the buyer on the first purchase order line.

po_entered_date = the date when you generated the purchase order and sent it to Locate. May not be the same as the order date or the created date for the order.

discount_percentage = from the purchase order header. Defaults from the Discount % defined for the vendor. No discount amount is passed.

shipping_instructions = set to DRP SHP ORD#12345678, where 12345678 is the originating order number. Updates the Shipping instructions for the purchase order in Locate. Displayed in the Vendor Portal, but not printed on the pack slip.

retailer_currency_cd, vendor_currency_cd, and currency_conversion_rate = The currency on the order, the vendor’s currency, and the conversion rate between them. The retailer and vendor currencies should be the same, and the conversion rate should be 1.000. Locate’s Supplier Direct Fulfillment module does not currently support currency conversion.

sales_order:

order_id = the CWSerenade order number and ship-to number, separated by a hyphen (for example, 12345-001). Displayed on Vendor Portal screens, where the Vendor can use it for searching.

freight_amount, order_additional_freight_charges, and order_additional_charges = Included in the shipping and handling total on the pack slip.

gift = from the Gift flag on the order. If set to Y, no prices or charges print on the pack slip.

ship_complete = from the Ship complete flag on the order. Does not enforce shipping complete in Locate.

balance_due = does not print on the pack slip.

freight_tax = the tax on freight, if any. The Tax on Freight (B14) system control value controls whether you tax freight for any shipping addresses. Included in the first pack slip for the purchase order.

sold_to: the customer_no and customer sold-to name and address print on the pack slip, with the exception of the prefix and suffix, middle initial, third and fourth address lines, email, phone numbers, and country.

ship_to: the shipping name and address print on the pack slip, with the exception of the prefix and suffix, third and fourth address lines, email, phone numbers, and country. Includes an attention line if specified.

order_message and gift_message = Up to 8 order header (sales order) messages with a Print flag setting of Picks, Both, or Gift msg print below the ship-to address at the top of the pack slip.

payment = updates the Locate database, but not displayed to the vendor and not printed on the pack slip. Includes the description of each pay type used, and the amount charged for prepaid payment methods.

po_detail:

external_ref_number = set to 006-0000412-001, where 006 is the company number, 412 is the purchase order number, and 001 is the ship-to number. Locate passes this number in the GetDSChanges response and the GetDSInvoices response messages, and CWSerenade uses this information to identify the purchase order and ship-to.

retailer_item_id and retailer_item_description = the item and SKU, and the item description. Creates a new product in Locate if it does not already exist, provided the requesting system is the default system for the organization in Locate; however, the new product is not used as parto of the Order Broker.

vendor_item_id and vendor_item_description = the vendor item and vendor item description. Creates a new vendor item if it does not already exist. If there is no vendor item record in CWSerenade, the item/SKU and item description are passed instead.

item_upc_cd or item_ean_cd = from the UPC or EAN codes, if any, set up for the item or SKU. If there are multiple UPC or EAN codes, the first code of each time is included.

po_unit_price and vendor_unit_price= from the vendor item unit price. If there is no vendor item record, from the item or SKU cost.

po_uom_code and vendor_uom_code = from the vendor item unit of measure code. Informational only; Locate does not support unit of measure conversion for drop ship purchase orders.

po_qty_ordered and vendor_ordered_qty = all unit quantities should be the same; Locate does not support unit of measure conversion for drop ship purchase orders.

carrier_code = from the ship via, if any, associated with the vendor item; otherwise, from the ship via on the order header. The pack slip prints the ship via for the first vendor item, if any; otherwise, the pack slip prints the ship via from the order header. The ship via codes and purchase order ship via codes in CWSerenade should match the carrier codes in Locate.

po_line_due_date = calculated using the vendor item lead days plus the CDC Drop Ship Lead Days (H36). See Supplier Direct Fulfillment Backorder Notice Processing for a discussion.

order_detail:

sales_order_qty_ordered = should be the same as the po_qty_ordered and vendor_ordered_qty. Locate does not support unit of measure conversion for drop ship purchase orders.

sales_order_unit_price = the customer’s unit price. Prints on the pack slip.

order_extended_freight = the total freight for the order line. Included only if the source code uses a line-level freight method.

order_line_customization_charge = the customer’s special handling charge for the item.

order_line_gift_wrap = set to Y if the item requires gift wrap; otherwise, set to N.

order_line_ship_alone = set to Y if the item is flagged to ship alone. Does not enforce shipping alone in Locate.

order_line_message = Includes order line messages identified with a Print flag setting of Picks or Both. Separate message lines are separated by a new line character. The messages print below the order line on the pack slip.

tax = the total tax for each line is included with a description of Tax. If there are additional tax buckets, such as GST or PST, the Tax total includes the amounts in these buckets.

unit_ship_weight = Used as part of the integrated shipping option in Locate. From the:

Ship weight from the SKU, if any; otherwise, the

Ship weight from the item, if any; otherwise, the

Sell weight from the SKU, if any; otherwise, the

Sell weight from the item, if any; otherwise, no weight is passed.

customizations:

customization_code = from the Field label for the special handling format. Prints on the pack slip.

customization_message = from the special handling input. Prints on the pack slip.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

ns2:CreateDSOrder xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:create_ds_order_request_message>

<message_header>

<datetime>2013-07-23</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<po_header>

<request_id>6-412</request_id>

<po_no>412</po_no>

<brand_cd>456</brand_cd>

<vendor_cd>203</vendor_cd>

<vendor_name>MATCHES VENDOR IN LOCATE</vendor_name>

<vendor_email>example@example.com</vendor_email>

<requesting_system_cd>6</requesting_system_cd>

<requesting_location_cd>1</requesting_location_cd>

<buyer_cd>HEB</buyer_cd>

<buyer_name>HANNAH BROWN</buyer_name>

<po_entered_date>2013-07-23</po_entered_date>

<discount_percentage>0.0000</discount_percentage>

<discount_amount>0.00</discount_amount>

<shipping_instructions>DRP SHP ORD#00012179</shipping_instructions>

<retailer_currency_cd>USA</retailer_currency_cd>

<vendor_currency_cd>USA</vendor_currency_cd>

<currency_conversion_rate>1.0000</currency_conversion_rate>

<sales_order>

<order_id>12179-001/order_id>

<freight_amount>10.00</freight_amount>

<order_additional_freight_charges>0.00</order_additional_freight_charges>

<order_additional_charges>0.00</order_additional_charges>

<gift>N</gift>

<ship_complete>N</ship_complete>

<balance_due>0.00</balance_due>

<sold_to customer_no="144">

<name>

<company_name>WENDELL ENTERPRISES </company_name>

<prefix>MR.</prefix>

<first>MICKEY</first>

<middle>Q</middle>

<last>WENDELL</last>

<suffix>JR.</suffix>

</name>

<address>

<attention></attention>

<address1>257 APPLE STREET</address1>

<address2>FIRST FLOOR </address2>

<address3>THIRD ADDRESS LINE</address3>

<address4>FOURTH ADDRESS LINE</address4>

<apt>APT 1234</apt>

<city>WORCESTER</city>

<province>MA</province>

<postal>01602</postal>

<email>example@example.com</email>

<phone1>(508) 555-0100</phone1>

<phone2>(508) 555-0102</phone2>

<country>USA</country>

</address>

</sold_to>

<ship_to>

<name>

<company_name>WENDELL ENTERPRISES </company_name>

<prefix>MR.</prefix>

<first>MICKEY</first>

<middle>Q</middle>

<last>WENDELL</last>

<suffix>JR.</suffix>

</name>

<address>

<attention></attention>

<address1>10 APPLE STREET</address1>

<address2>FIRST FLOOR</address2>

<address3>THIRD ADDRESS LINE</address3>

<address4>FOURTH ADDRESS LINE</address4>

<apt>APT 3B</apt>

<city>WORCESTER</city>

<province>MA</province>

<postal>01602</postal>

<email>example@example.com</email>

<phone1>(508) 555-0100</phone1>

<phone2>(508) 555-0101</phone2>

<country>USA</country>

</address>

</ship_to>

<order_message></order_message>

<gift_message></gift_message>

<payments>

<payment line_item_no="1">

<tender_description>MASTERCARD</tender_description>

<tender_amount>0.00</tender_amount>

<tender_account></tender_account>

</payment>

</payments>

<freight_tax>0.82</freight_tax>

</sales_order>

</po_header>

<po_details>

<po_detail po_line_no="1">

<external_ref_number>006-0000412-001</external_ref_number>

<retailer_item_id>SWADDLER </retailer_item_id>

<retailer_item_description>EMBROIDERED FLANNEL BABY BLANKET</retailer_item_description>

<vendor_item_id>V203SWADDLER</vendor_item_id>

<vendor_item_description>EMBROIDERED BABY BLANKET</vendor_item_description>

<po_unit_price>20.00</po_unit_price>

<po_uom_code>EA</po_uom_code>

<vendor_uom_code>EA</vendor_uom_code>

<po_qty_ordered>1</po_qty_ordered>

<vendor_ordered_qty>1</vendor_ordered_qty>

<vendor_unit_price>20.00</vendor_unit_price>

<carrier_cd>7</carrier_cd>

<po_line_due_date>2013-08-04</po_line_due_date>

<home_delivery_carrier></home_delivery_carrier>

<order_detail>

<sales_order_qty_ordered>1</sales_order_qty_ordered>

<sales_order_unit_price>50.00</sales_order_unit_price>

<order_extended_freight>0.00</order_extended_freight>

<order_line_customization_charge>12.95</order_line_customization_charge>

<order_line_gift_wrap>N</order_line_gift_wrap>

<order_line_ship_alone></order_line_ship_alone>

<order_line_message></order_line_message>

<customizations>

<customization>

<customization_code>FIRST NAME LABL</customization_code>

<customization_message>Mickey</customization_message>

</customization>

<customization>

<customization_code>COLOR FLD LBL</customization_code>

<customization_message>black</customization_message>

</customization>

<customization>

<customization_code>LAST NAME LABEL</customization_code>

<customization_message>Wendell</customization_message>

</customization>

</customizations>

<taxes>

<tax description="Tax" line_item_no="1">

<amount>3.93000</amount>

</tax>

<tax description="GST" line_item_no="2">

<amount>0.00000</amount>

</tax>

<tax description="PST" line_item_no="3">

<amount>0.00000</amount>

</tax>

</taxes>

<unit_ship_weight>2.010</unit_ship_weight>

</order_detail>

</po_detail>

<po_detail po_line_no="5">

<external_ref_number>006-0000412-005</external_ref_number>

<retailer_item_id>SWADDLER </retailer_item_id>

<retailer_item_description>EMBROIDERED FLANNEL BABY BLANKET</retailer_item_description>

<vendor_item_id>V203SWADDLER</vendor_item_id>

<vendor_item_description>EMBROIDERED BABY BLANKET</vendor_item_description>

<po_unit_price>20.00</po_unit_price>

<po_uom_code>EA</po_uom_code>

<vendor_uom_code>EA</vendor_uom_code>

<po_qty_ordered>1</po_qty_ordered>

<vendor_ordered_qty>1</vendor_ordered_qty>

<vendor_unit_price>20.00</vendor_unit_price>

<carrier_cd>7</carrier_cd>

<po_line_due_date>2013-08-04</po_line_due_date>

<home_delivery_carrier></home_delivery_carrier>

<order_detail>

<sales_order_qty_ordered>1</sales_order_qty_ordered>

<sales_order_unit_price>50.00</sales_order_unit_price>

<order_extended_freight>0.00</order_extended_freight>

<order_line_customization_charge>12.95</order_line_customization_charge>

<order_line_gift_wrap>N</order_line_gift_wrap>

<order_line_ship_alone></order_line_ship_alone>

<order_line_message></order_line_message>

<customizations>

<customization>

<customization_code>FIRST NAME LABL</customization_code>

<customization_message>Baby</customization_message>

</customization>

<customization>

<customization_code>COLOR FLD LBL</customization_code>

<customization_message>yellow</customization_message>

</customization>

<customization>

<customization_code>LAST NAME LABEL</customization_code>

<customization_message>Blue</customization_message>

</customization>

</customizations>

<taxes>

<tax description="Tax" line_item_no="1">

<amount>3.93000</amount>

</tax>

<tax description="GST" line_item_no="2">

<amount>0.00000</amount>

</tax>

<tax description="PST" line_item_no="3">

<amount>0.00000</amount>

</tax>

</taxes>

</order_detail>

</po_detail>

</po_details>

</message_body>

</ns2:create_ds_order_request_message>

</ns2:CreateDSOrder>

</soap:Body>

</soap:Envelope>

CreateDSOrder Response Message from Locate

Locate returns a response such as the following when it receives the CreateDSOrder request message.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:CreateDSOrderResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<create_ds_order_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-11T09:55:33.249</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<response response_code="0" order_id="12373-001" po_no="506">

<response_description>Order Acknowledged</response_description>

</response>

</message_body>

</create_ds_order_response_message>

</ns2:CreateDSOrderResponse><

/soap:Body>

</soap:Envelope>

GetDSChanges Message Samples

Purpose: The CDC async job sends this message to Locate periodically for each company that has the Use CWCollaborate/Locate (H13) system control value selected in order to receive updates for drop ship purchase order lines. Possible updates include:

• shipment

• acceptance or rejection of an address change or cancellation request

• change to due date

• holding or releasing the line

You can review this activity at the Display P/O Drop Ship Screen.

For more information: See Updates to Locate Drop Ship Purchase Orders, Shipping Orders through the Supplier Direct Fulfillment Module, Cancelling Locate Drop Ship Order Lines, Changing Address and Cost Information, and the Locate Operations Guide.

GetDSChanges Message to Locate

Information in this message includes:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

requesting_system_cd = from tthe Locate System (K50) system control value

no_transactions = from the CW_LOCATE_PURCHASING_SERVICES_MAX_UPDATES setting in the Locate Properties File. The response does not include more than this number of transactions.

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">

<S:Body>

<ns2:GetDSChanges xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:get_ds_changes_request_message>

<message_header>

<datetime>2013-09-05</datetime>

<version>4.5</version>

<source>Direct</source>

<destination>Locate</destination>

</message_header>

<message_body>

<changes>

<requesting_system_cd>6</requesting_system_cd>

<no_transactions>100</no_transactions>

</changes>

</message_body>

</ns2:get_ds_changes_request_message>

</ns2:GetDSChanges>

</S:Body>

</S:Envelope>

GetDSChanges Response Message from Locate

Information in this message includes:

more_changes = indicates whether there are additional changes to send to CWSerenade beyond the number specified in the request message

event = possible events are:

PO_Cancel_Accepted = the vendor accepts a cancellation request for a purchase order line

PO_Cancel_Rejected = the vendor declines a cancellation request for a purchase order line

PO_Due_Date_Changed = the vendor changes the due date for a purchase order line

PO_Held = the vendor holds a purchase order line

PO_In_Process = the vendor generates a pack slip

PO_Message = the vendor enters a reason description for a purchase order line without also changing the due date or the held status

PO_Released = the vendor releases a purchase order line

PO_Ship = the vendor confirms shipment of a purchase order line

change_date = the date when the activity occurred. Always included.

external_ref_number = set to 006-0000412-001, where 006 is the company number, 412 is the purchase order number, and 001 is the ship-to number. Always included.

po_line_no = the purchase order line number affected by the activity. Always included.

po_no = the purchase order affected by the activity. Always included.

request_system_cd = from the requesting_system_cd in the request message.

cancel_qty = the quantity specified for a cancel request. Included when a cancel request is accepted or rejected.

ship_qty = the quantity shipped. Included for a purchase order shipment.

actual_weight = the weight specified by the vendor at shipment. Included for a shipment only if a weight was specified.

ship_date = the date and time when the shipment occurred. Even if the shipment date indicated is not the same as the current date, CWSerenade uses the current date as the shipment date. Always included for a shipment.

freight_charges = the total freight charges specified by the vendor at shipment. Included for a shipment only if a freight amount was specified.

tracking_number = the shipment tracking number. Included for a shipment only if a tracking number was specified.

carrier_cd = the code identifying the carrier (ship via) for the shipment. Always included for a shipment.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:GetDSChangesResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<get_ds_changes_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-11T16:26:16.829</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<PO_changes more_changes="No" response_description="Success" response_code="0">

<PO_change cancel_qty="1" event="PO_Cancel_Accepted" change_date="2013-09-11T16:25:51.157" external_ref_number="006-0000511-001" po_line_no="1" po_no="511" request_system_cd="6"></PO_change>

<PO_change cancel_qty="1" event="PO_Cancel_Rejected" change_date="2013-09-11T16:25:51.250" external_ref_number="006-0000510-002" po_line_no="2" po_no="510" request_system_cd="6"></PO_change>

<PO_change revised_date="2013-09-18T12:00:00.000" message="delayed shipment" event="PO_Due_Date_Changed" change_date="2013-09-11T16:24:49.703" external_ref_number="006-0000494-001" po_line_no="1" po_no="494" request_system_cd="6" />

<PO_change message="" event="PO_Released" change_date="2013-09-11T16:24:49.267" external_ref_number="006-0000479-001" po_line_no="1" po_no="479" request_system_cd="6" />

<PO_change message="hold pending cancel" event="PO_Held" change_date="2013-09-11T16:24:49.627" external_ref_number="006-0000490-001" po_line_no="1" po_no="490" request_system_cd="6" />

<PO_change ship_qty="1" actual_weight="2.0" ship_date="2013-09-11T16:23:58.633" freight_charges="3.0" tracking_number="XYZ12345" carrier_cd="2" event="PO_Ship" change_date="2013-09-11T16:24:13.233" external_ref_number="006-0000455-001" po_line_no="1" po_no="455" request_system_cd="6" />

<PO_change message="message from vendor" event="PO_Message" change_date="2013-09-11T16:44:14.323" external_ref_number="006-0000497-001" po_line_no="1" po_no="497" request_system_cd="6"/>

</PO_changes>

</message_body>

</get_ds_changes_response_message>

</ns2:GetDSChangesResponse>

</soap:Body>

</soap:Envelope>

GetDSInvoices Message Samples

Purpose: The CDC async job sends this message to Locate periodically for each company that has the Use CWCollaborate/Locate (H13) system control value selected in order to receive invoices from vendors using Locate’s Supplier Direct Fulfillment module.

For more information: See Posting Invoices from Locate and the Locate Operations Guide.

GetDSInvoices Message to Locate

Purpose: CWSerenade sends this message to Locate periodically to request any new invoices posted by vendors.

Information in this message includes:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

requesting_system_cd = from tthe Locate System (K50) system control value

no_invoices = from the CW_LOCATE_PURCHASING_SERVICES_MAX_INVOICES setting in the Locate Properties File. The response does not include more than this number of invoices.

For more information: See Posting Invoices from Locate and the Locate Operations Guide.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:GetDSInvoices xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:get_ds_invoices_request_message>

<message_header>

<datetime>2013-07-21</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<invoices>

<requesting_system_cd>6</requesting_system_cd>

<no_invoices>5</no_invoices>

</invoices>

</message_body>

</ns2:get_ds_invoices_request_message>

</ns2:GetDSInvoices>

</soap:Body>

</soap:Envelope>

GetDSInvoices Response Message from Locate

Information in this message includes:

more_invoices = indicates whether there are additional invoices to send to CWSerenade beyond the number specified in the request message

PO_invoices:

invoice_created_by_user = the vendor user ID of the person who created the invoice when logged into the Vendor Portal.

discount_pct, net_due_days, and gross_due_days = Used to identify the A/P terms code to assign to the invoice if the A/P Invoice Upload Terms Code Usage system control value is selected. See Selecting the Terms Code for a discussion.

total_other_amount, total_handling_amount, and total_freight_amount = from the header-level charges specified by the vendor. Each of these charges applies to the invoice created in CWSerenade, with a Type of OTHER. If the invoice from Locate includes multiple purchase orders, resulting in the invoice splitting in CWSerenade, the charges apply to the first invoice created in CWSerenade (for example, INV123-1).

debit_credit = always set to DB.

requesting_system_cd = from the requesting_system_cd in the request message (from tthe Locate System (K50) system control value).

invoice_date = the date and time when the vendor created the invoice, or the date the vendor specified for the invoice, if different. If the vendor specified a different date, the time is set to all zeroes (for example, 2013-09-14T00:00:00.0000).

invoice_no = the invoice number specified by the vendor. CWSerenade appends a numeric suffix for each purchase order if the invoice includes multiple purchase orders.

vendor_no = the number identifying the vendor submitting the invoice. Updates the Created by field.

invoice_detail =

other_amount, handling_amount, and freight_amount = total_other_amount, total_handling_amount, and total_freight_amount = from the detail-level charges specified by the vendor. Each of these charges applies to the invoice created in CWSerenade, with a Type of OTHER.

invoice_qty = the detail shipment quantity being invoiced. Set to 1 for a handling, freight, or other amount.

invoice_unit_cost = the unit cost for the item shipped. From the unit cost sent from CWSerenade, unless the vendor overrode the unit cost. See Posting Invoices from Locate for a discussion.

vendor_item_no = the code identifying the item and SKU to the vendor. From the vendor item code sent in the CreateDSOrder message.

retailer_item_no = your item and SKU code.

order_no = the number identifying the order in CWSerenade that originated the drop ship purchase order.

po_line_no = the line number on the purchase order.

invoice_line_no = the line number on the invoice.

external_ref_number = set to 006-0000412-001, where 006 is the company number, 412 is the purchase order number, and 001 is the ship-to number. Always included.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:GetDSInvoicesResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<get_ds_invoices_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-07-21T14:00:31.935</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<PO_invoices more_invoices="No" response_description="Success" response_code="0">

<PO_invoice invoice_created_by_user="vendor257" discount_pct="2.0" net_due_days="20" gross_due_days="30" total_other_amount="3.45" total_handling_amount="2.34" total_freight_amount="1.23" debit_credit="DB" requesting_system_cd="6" invoice_date="2013-07-21T13:27:22.473" invoice_no="IN376b" vendor_no="257">

<invoice_detail other_amount="3.77" handling_amount="2.66" freight_amount="1.55" invoice_qty="1" invoice_unit_cost="1.09" vendor_item_no="V257BUGHAT" retailer_item_no="BUGHAT " order_no="12143" po_line_no="1" po_number="376" invoice_line_no="1" external_ref_number="006-0000376-001" />

<invoice_detail other_amount="0.0" handling_amount="0.0" freight_amount="0.0" invoice_qty="1" invoice_unit_cost="1.0" vendor_item_no="V257SCARFBLUE" retailer_item_no="SCARF BLUE " order_no="12143" po_line_no="2" po_number="376" invoice_line_no="2" external_ref_number="006-0000376-002" />

<invoice_detail other_amount="0.0" handling_amount="0.0" freight_amount="0.0" invoice_qty="1" invoice_unit_cost="1.0" vendor_item_no="V257SCARFRED" retailer_item_no="SCARF RED " order_no="12143" po_line_no="3" po_number="376" invoice_line_no="3" external_ref_number="006-0000376-003" />

</PO_invoice>

</PO_invoices>

</message_body>

</get_ds_invoices_response_message>

</ns2:GetDSInvoicesResponse>

</soap:Body>

</soap:Envelope>

SetDSCancel Message Samples

Purpose: CWSerenade sends the SetDSCancel request message to Locate when you use the Cancel Request option at the Display P/O Drop Ship Screen.

For more information: See Cancelling Locate Drop Ship Order Lines and the Locate Operations Guide.

SetDSCancel Message to Locate

Information in this message includes:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

• destination = from the Locate Account (K49) system control value

requesting_system_cd = from tthe Locate System (K50) system control value

po_no = the CWSerenade purchase order number

po_line_no = the purchase order line number to cancel

po_line_qty = the quantity of the purchase order line to cancel. It is not possible to cancel a partial quantity.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSCancel xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:set_ds_cancel_request_message>

<message_header>

<datetime>2013-09-05</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<cancellations>

<cancellation>

<requesting_system_cd>6</requesting_system_cd>

<po_no>488</po_no>

<po_line_no>1</po_line_no>

<po_line_qty>1</po_line_qty>

</cancellation>

</cancellations>

</message_body>

</ns2:set_ds_cancel_request_message>

</ns2:SetDSCancel>

</soap:Body>

</soap:Envelope>

SetDSCancel Response Message from Locate

Locate returns a response such as the following when it receives the SetDSCancel request message.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSCancelResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<set_ds_cancel_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-06T11:49:58.240</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<responses>

<response external_ref_number="006-0000461-002" po_line_no="2" po_no="461" response_code="0">

<response_description>Successfully updated</response_description>

</response>

</responses>

</message_body>

</set_ds_cancel_response_message>

</ns2:SetDSCancelResponse>

</soap:Body>

</soap:Envelope>

SetDSAddressChange Message Samples

Purpose: CWSerenade sends the SetDSAddressChange request message to Locate when you update the shipping address on an order that includes a drop ship purchase order being fulfilled through the Supplier Direct Fulfillment module.

For more information: See Changing Address Information and the Locate Operations Guide.

SetDSAddressChange Message to Locate

Information in this message includes:

requesting_system_cd = the Locate System (K50)

po_no = the CWSerenade purchase order number

sold_to_same_as_ship_to = Set to Y if there is not a separate shipping address for the order; otherwise, set to N.

name and address elements = The name and address from the shipping address on the order.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSAddressChange xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:set_ds_address_change_request_message>

<message_header>

<datetime>2013-09-05</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<address_changes>

<address_change>

<requesting_system_cd>6</requesting_system_cd>

<po_no>493</po_no>

<sold_to_same_as_ship_to>N</sold_to_same_as_ship_to>

<ship_to>

<name>

<company_name>SPRINGER INDUSTRIES </company_name>

<prefix>MS.</prefix>

<first>BUNNY</first>

<middle>Q</middle>

<last>SPRINGER</last>

<suffix></suffix>

</name>

<address>

<attention></attention>

<address1>1234 SPRINGER ROAD</address1>

<address2>SPRINGER ROAD EXTENSION</address2>

<address3></address3>

<address4></address4>

<apt></apt><

city>WORCESTER</city>

<province>MA</province>

<postal>01602</postal>

<email></email>

<phone1>508 555 0100</phone1>

<phone2></phone2>

<country>USA</country>

</address>

</ship_to>

</address_change>

</address_changes>

</message_body>

</ns2:set_ds_address_change_request_message>

</ns2:SetDSAddressChange>

</soap:Body>

</soap:Envelope>

 

SetDSAddressChange Response Message from Locate

Locate returns a response such as the following when it receives the SetDSAddressChange request message.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSAddressChangeResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<set_ds_address_change_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-05T16:45:21.032</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<responses>

<response po_no="493" response_code="0">

<response_description>Successfully updated</response_description>

</response>

</responses>

</message_body>

</set_ds_address_change_response_message>

</ns2:SetDSAddressChangeResponse>

</soap:Body>

</soap:Envelope>

SetDSCostChange Message Samples

Purpose: CWSerenade sends the SetDSCostChange request message to Locate when you update the Cost field on the PO Maintenance - Change PO Detail Screen for a drop ship purchase order fulfilled through the Supplier Direct Fulfillment module.

For more information: See Changing Cost Information and the Locate Operations Guide.

SetDSCostChange Message to Locate

Information in this message includes:

version = the CW_LOCATE_PURCHASING_SERVICES_MESSAGE_VERSION from the Locate Properties File. See Properties File Settings for the Supplier Direct Fulfillment Integration for background.

• destination = from the Locate Account (K49) system control value

requesting_system_cd = from tthe Locate System (K50) system control value

po_no = the CWSerenade purchase order number

po_line_no = the purchase order line number to receive the cost change

po_unit_price and vendor_unit_price = the new unit price to apply. Both the purchase order unit price and the vendor unit price should be the same, since Locate does not support currency conversion or unit of measure conversion for purchase orders.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSCostChange xmlns:ns2="http://microsretail.com/LocatePurchasing">

<ns2:set_ds_cost_change_request_message>

<message_header>

<datetime>2013-09-06</datetime>

<version>4.5</version>

<source>Serenade</source>

<destination>Locate</destination>

</message_header>

<message_body>

<cost_changes>

<cost_change>

<requesting_system_cd>6</requesting_system_cd>

<po_no>465</po_no>

<po_line_no>1</po_line_no>

<po_unit_price>1.02</po_unit_price>

<vendor_unit_price>1.02</vendor_unit_price>

</cost_change>

</cost_changes>

</message_body>

</ns2:set_ds_cost_change_request_message>

</ns2:SetDSCostChange>

</soap:Body>

</soap:Envelope>

SetDSCostChange Response Message from Locate

Locate returns a response such as the following when it receives the SetDSCostChange request message.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<ns2:SetDSCostChangeResponse xmlns:ns2="http://microsretail.com/LocatePurchasing">

<set_ds_cost_change_response_message>

<message_header xaction_response="OK" xaction_type="INFO">

<datetime>2013-09-06T12:04:15.717</datetime>

<version>4.5</version>

<source>Locate</source>

<destination>Serenade</destination>

</message_header>

<message_body>

<responses>

<response external_ref_number="006-0000465-001" po_line_no="1" po_no="465" response_code="0">

<response_description>Successfully updated</response_description>

</response>

</responses>

</message_body>

</set_ds_cost_change_response_message>

</ns2:SetDSCostChangeResponse>

</soap:Body>

</soap:Envelope>

FU07_02b Serenade 5.0 March 2015