Generic Pick Out API

Generic Pick Out API

Purpose: Use the generic pick out API to generate an outbound pick slip message.

About the message: The CWPickOut message produced for a new or reprinted pick slip includes the entire contents of each of the tables related to the pick slip. For example, for each item included on the order, the CWPickOut message includes the contents of the Item and SKU tables. Your integration might not require all of the information in the message, and can omit any unneeded information when mapping the message to another system.

Which items included? Other items on the order are included in the CWPickOut message even if they are not ready to ship because they are backordered, held, or drop shipments; however, the message does not include any pick location details for items that are not included on the pick slip.

The pick slip does not include any information on canceled or soldout items.

Warehouse management settings for pick slip generation: If you are using a warehouse management system and do not need to generate printable pick slips, you can select the Bypass Creation of Pick Forms during WSPS Pick Generation (K55) system control value to prevent generating printable pick slips when you use Streamlined Pick Slip Generation (WSPS). To improve performance for the other pick slip generation options:

• Leave the Pick Printing Program (C37) system control value blank.

• If you do not print drop ship pick slips, leave the Drop Ship Pick Print Program (E92) system control value blank.

• Unselect the Use Cart/Bin Picking? (B38) system control value.

See Pick Out Processing for a listing of the options that generate printable pick slips or pick out triggers.

In this chapter:

• Pick Out Processing

- Message Flow

- Sample CWPickOut Message (New or Reprinted Pick Slip)

- Sample CWPickOut message (Void Pick Slip)

• Pick Message from Order Management System (CWPickOut)

Pick Out Processing

The system generates a trigger record of type PCH when you generate pick slips if the Create Generic Pick Download Triggers (I31) system control value is selected. The PICK_OUT process in Working with Integration Layer Processes (IJCT) generates the Pick Message from Order Management System (CWPickOut) for each of these trigger records.

You can generate pick slips and PCH trigger records through:

Function	Condition
Streamlined Pick Slip Generation (WSPS)
Selecting Vendors for Drop Ship Processing (MDSP)	if you print drop ship invoices; see Possible Drop Ship Output
Processing Drop Ship Orders by Batch (MDSB)	if you print drop ship invoices; see Possible Drop Ship Output
Receiving a drop ship purchase order (fast path = PORC)	if you print drop ship invoices and the Print Drop Ship Invoice at time of Purchase Order Receiving (F10) system control value is selected
Reprinting and Voiding Pick Slips (WVRP or WSVP)

Note: If you print drop ship invoices during drop ship processing and when you receive a drop ship purchase order, the system will generate a PCH trigger for both functions.

When generating the outbound message, the PICK_OUT process uses trigger rules and XML inclusion settings as described below.

Pick Out Trigger Rules

You can set a trigger rule for the pick out API based on the company number specified in the Pick Control Header table. See Defining Outbound Interface Trigger Rules for more information.

Pick Out XML Inclusion

As with other outbound messages generated through Working with Integration Layer Processes (IJCT), you can use the Outbound Interface XML Inclusion Screen to exclude elements and their contents from the Pick Message from Order Management System (CWPickOut). The XML inclusion options for the pick out API are:

PickHeader

CustomerSoldToAddress

CustomerBillToAddress

OrderShipTo

PickHeaderMsgs

OrderHeader

OrderPayments

PickDetail

PickLocation

Item

SKU

UPC

OrderDetail

PickDetailMsgs

OtherDetail

OtherItem

OtherSKU

OtherUPC

OtherOrderDetailMessages

If you choose to exclude an element, all of the subordinate elements and attributes of that element will also be excluded.

If you exclude the PickHeader element, the message will not include any information.

Note: XML inclusion settings are not specific to a company. Any XML inclusion settings you create apply to all companies for which you generate trigger records.

Message Flow

Pick slip information is transmitted as follows:

• You generate pick slips using the options listed under Pick Out Processing.

• The PICK_OUT process in Working with Integration Layer Processes (IJCT) creates a trigger record for each pick slip, assigning it a record type of PCH (pick control header). You can review the trigger records at the Work with Outbound Interface Transactions Screen.

Note: Optionally, you can use trigger rules for the PICK_OUT process to restrict trigger creation to one or more specific companies.

• The PICK_OUT process creates the Pick Message from Order Management System (CWPickOut), and then resets the trigger record to processed (X) status.

Void transactions: When you void a pick slip, the PICK_OUT process determines whether to send a CWPickOut message to the external system.

• If a CWPickOut message has already been processed for the generation of the pick slip that was voided (the PCH trigger record for the Add transaction is in a processed (X) status or a PCH trigger record no longer exists for the generation of the pick), the system creates a delete trigger record for the pick slip and sends a CWPickOut message to the external system indicating to delete the pick slip.

• If a CWPickOut message has not yet been processed for the generation of the pick slip that was voided (the PCH trigger record for the Add transaction is in a ready (R) or pending (P) status), the system creates a delete trigger record for the pick slip. However, instead of sending a CWPickOut message to the external system for the generation and delete of the pick slip, the system updates the PCH trigger records for the Add and Delete transaction to processed (X) and does not generate a CWPickOut message.

Re-sending transactions: You can re-send a CWPickOut message by resetting the status of its trigger record at the Work with Outbound Interface Transactions Screen. Note: If a PCH trigger is associated with a drop ship invoice/pick, you will not be able to re-send a CWPickOut message for the trigger because the system deletes the pick records immediately after the drop ship forms are generated.

Active Procedure: The system creates an Active Procedure record when the PICK_OUT job starts to prevent another PICK_OUT job from running at the same time. See Purge Active Procedures Across Users (MACX) for more information on reviewing current Active Procedures.

Sample Pick Slip Messages

A sample CWPickOut message is presented below. The system generates a full CWPickOut message for a new or reprinted pick slip, and generates an abbreviated CWPickOut message for a void pick slip. The transaction_type indicates whether this is a new or reprinted pick slip (transaction type A) or a request to void a pick slip (transaction type D).

Sample CWPickOut Message (New or Reprinted Pick Slip)

</CustomerSoldToAddress>

</OrderPayments>

</PickHeaderMsgs>

</PickLocations>

</Item>

</PickDetailMsgs>

</PickDetail>

</PickDetails>

</PickHeader>

</Message>

Sample CWPickOut message (Void Pick Slip)