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.