Picking Using Fulfillment Engine Integration Points
Third-party systems can use the INVENTORY_PICK_CONFIRM or the INVENTORY_SHIPPING inbound EIPs to send PeopleSoft fulfillment transaction requests that provide picking information to orders in the released state using the fulfillment engine.
These EIPs are especially useful when dealing with a large number of orders. Data from external systems can be processed through the PeopleSoft Integration Broker. These service operations can request to move material stock orders and sales orders from one fulfillment status to another. PeopleSoft delivers these asynchronous EIPs that enable you to post data to the Integration Broker and receive a response indicating the data has been received. For each active inbound asynchronous transaction defined in the system for the source node and message version, the Integration Broker places the data in staging tables and then processed by the fulfillment engine using the Fulfillment Requests process.
The fulfillment engine default values for the INVENTORY_PICK_CONFIRM EIP and the INVENTORY_SHIPPING EIP come from the Transactions / Request Picking Feedback row and the Transactions / Request to Ship row on the Setup Fulfillment-Fulfillment Task Options page (business unit level). If no value is entered in the Setup Fulfillment component, then the default values come from the same rows on the Fulfillment Engine Options page (SetID level). These default values include the auto-processing option, that enables the orders to be sent to the confirmed, shipped, or depleted state, and the complete flag to determine what picking information should be recorded on the orders.
Note: The Complete Flag can be applied at the header, group, or detail level. The level where the Complete Flag is located determines what level to apply the complete flag logic.
In integrated implementations, in which an internally-controlled warehouse management system (WMS) or a third-party WMS is used to pick, pack, and ship orders, the PeopleSoft Inventory system must send the orders to the WMS and then receive the picking, packing, or shipping results back from the WMS. When orders are ready to be released to the warehouse, the Order Release Request process is run to generate the Shipping Order Release EIP containing all releasable orders. The warehouse system accepts the order, then picks, packs, and ships the goods and sends either the Inventory Pick Confirm EIP or the Inventory Shipping EIP back to the PeopleSoft system.
The Inventory Pick Confirm EIP and the Inventory Shipping EIP are an inbound asynchronous service operations containing the details for picking and shipping managed by the WMS system for the orders released to it by the PeopleSoft system. Use the Inventory Pick Confirm EIP to send back the details of the picking activities or use the Inventory Shipping EIP to send back the details of the picking and shipping activities. With these EIPs, you can configure the PeopleSoft system to subscribe to an XML-based service operation. The Inventory Shipping EIP meets X.12 EDI requirements of the 945 - Warehouse Shipping Advice transaction set.
A third alternative for providing shipping information is the Shipping Notification EIP. In prior releases the Shipping Notification EIP was used to send back picking and shipping details from the WMS. The Shipping Notification EIP is available for backwards compatibility to earlier releases. However, if you are currently implementing the integration point between PeopleSoft Inventory and a WMS, use the Inventory Pick Confirm EIP or the Inventory Shipping EIP instead of the Shipping Notification EIP.
Inventory Shipping EIP
When the WMS ships an order, shipping information is sent to the PeopleSoft system using the Inventory Shipping EIP. This transaction contains all the information necessary to pick, pack, and ship individual orders in PeopleSoft Inventory. In addition, the service operation can create single-level shipping containers and ship serial IDs.
The message of the service operation contains header, group, detail, and LLS segments.
The header level is used to enter shipping information that is changed during the shipping process.
Overrides can be made to the carrier ID, shipping method (Ship Type ID) and freight terms. In addition, new shipping information can be entered identifying a pro number, bill of lading, ship date, ship time, shipping container assignment, freight dollars, or a container tracking number. Note that overrides entered at this level are applied to all demand lines selected within the transaction that do not have overrides at lower transaction segment levels.
A ship ID may also be provided at the header level. This ship ID is applied to all demand lines in the shipment. If a ship ID is not provided then the system automatically generates it.
The group and detail level segments are used to identify demand lines within the shipment.
Most of the key fields that exist on a demand line are available to be used when selecting which orders are to be shipped. Overrides also exist at these levels. Note that the lowest level override is applied to the demand line. For example, if different pro-numbers are provided at both the detail and group levels, then the pro-number entered on the detail segment is applied to all demand lines selected by the selection criteria on that detail segment. Any demand lines that are selected at the group level but not included in the selection criteria at the detail level are given the pro-number provided at the group level.
The LLS segment is used to identify specific quantities picked against a demand line.
All key information required to pick the item in the PeopleSoft system must be provided. This key information includes the item ID, material storage location, and (if necessary) the lot ID, serial ID, staged date, storage container, and stocking unit of measure. Shipping containers and tracking numbers associated with the shipping containers and shipping serial IDs can also be entered at this level.
Inventory Shipping transactions sent from a WMS are staged as a transaction in PeopleSoft Inventory's staging tables BCT_CTL and BCT_DTL. An Inventory Fulfillment Request run control is used to start up the fulfillment engine and have it process the Inventory Shipping transactions. The fulfillment engine may also automatically deplete the orders shipped if the auto-processing option on the header segment is set to Advance to Depleted.
Note: A single release order line cannot be split across two different shipping IDs.
Note: Freight can only be applied at one segment level on the transaction. If freight is applied at more than one level of the transaction, then this is an error condition and the transaction is rejected. For example, you can apply freight at the header level, then all orders on the transaction are given a prorated portion of the freight dollars. If you do not apply freight at the header level, then you can apply it at the group or detail level. However, you cannot provide freight at both the header and group/detail level. You also cannot provide freight at both the group and detail level. It must be provided at a single segment level.
Note: If a bill of lading number is sent to PeopleSoft Inventory on the Inventory Shipping service operation, then the system updates the demand table for tracking purposes but does not create a bill of lading in the PeopleSoft system.
Note: The Inventory Shipping EIP can work with demand lines coming from an unfulfilled, releasable, released, or confirmed state. While this feature opens up many procedural alternatives when interfacing to third-party systems, it also means that the appropriate From State options must be entered on the message segments of the service operation. When entering selection criteria the SELECT_UNFULFILLED, SELECT_RELEASABLE, SELECT_RELEASED, and SELECT_CONFIRMED fields must be set to a Y or N. If all four of these fields are set to N when processed by the fulfillment engine, then the fulfillment engine default values are applied. The fulfillment engine default values for the Inventory Shipping EIP come from the Transactions / Request to Ship row on the Setup Fulfillment-Fulfillment Task Options page (business unit level). If no value is entered in the Setup Fulfillment component, then the default values come from the same row on the Fulfillment Engine Options page (SetID level).
Inventory Pick Confirm EIP
The Inventory Pick Confirm EIP may be used in place of the Inventory Shipping EIP if the actual shipping action will occur in the PeopleSoft system. This EIP provides all information necessary to pick and relieve material storage location inventory balances but does not ship orders. All shipping override information provided in the Inventory Shipping transaction may be provided on the Inventory Pick Confirm transaction with the exception of freight dollars, ship date, and ship time.
Inventory Pick Confirm transactions sent from a WMS are staged as a transaction in PeopleSoft Inventory's staging tables BCT_CTL and BCT_DTL. An Inventory Fulfillment Request run control is used to start up the fulfillment engine and process the Inventory Pick Confirm transactions. The fulfillment engine may also automatically confirm, ship or deplete the orders if the auto-processing option on the header segment is set to Advance to Confirmed, Advance to Shipped, or Advance to Depleted.
If a ship ID is provided on the Inventory Pick Confirm EIP, then the ship ID is applied to the full shipment whether or not the order is being shipped. If the auto-processing option on the header segment is set to Advance to Confirmed and a ship ID is provided, then the behavior is similar to the functionality provided when using the Shipping/Issues page with an action of Do not Ship/Include.
Note: The Inventory Pick Confirm EIP only selects demand lines coming from a released state where the Confirm Flag is set to N. If the Confirm Flag has already been set to Y by the autopick feature in the Order Release process or manually from the Material Picking Feedback component, then these demand lines are ignored by the Inventory Pick Confirm process.
Shipping Notification EIP
The Shipping Notification EIP is converted to either an Inventory Pick Confirm or Inventory Shipping transaction by the PeopleSoft system as the data is processed by the subscription process assigned to the Shipping Notification EIP. The original Shipping Notification service operation is written to the transaction log (BCT_CTL and BCT_DTL) in a complete status for audit purposes only. The Inventory Pick Confirm or Inventory Shipping transactions are also be written to the transaction log. If the Ship Flag on the shipment header of the Shipping Notification EIP is set to Y, then an Inventory Shipping transaction is created. If the Ship Flag is set to N, then an Inventory Pick Confirm transaction is created.
The Shipping Notification service operation includes the shipment header and shipment lines. A shipment designated by a shipment header is defined as a shipment event for a single carrier ID, ship type ID, freight terms value, ship date, ship time, and bill of lading. These field values must be identical for all lines defined for the given instance of a shipment header. If these values are left blank on the detail segment then those at the header level are applied.
A third segment level defining ship serial IDs is also available when reporting shipping information with the Shipping Notification EIP. This segment is only used for items that are ship serial controlled. Ship serial IDs must be provided when the Ship Flag is set to Y for shipments that include ship serial controlled items.
PeopleSoft delivers the service operations in PeopleSoft Integration Broker with a default status of Inactive. You must activate each service operation before attempting to send or receive data from a third-party source or another PeopleSoft system, such as CRM.
To set up the Shipping Notification EIP within PeopleSoft Integration Broker and Enterprise Components, use the information in the table below and refer to the setup instruction in the PeopleSoft Supply Chain Management Integrations, "Implementing Integrations" topic, Setting Up Service Operations section.
|
Service Operation |
Direction and Type |
Handlers |
Chunking Available? |
Integrates With |
|---|---|---|---|---|
|
SHIPPING_NOTIFICATION |
Local and Inbound Asynchronous |
Shipping Notification |
No |
Third-party system |