Processing Inbound EIPs for the Fulfillment Engine
Third-party systems can send PeopleSoft fulfillment transaction requests to be processed by the fulfillment engine using these service operations:
Inventory_Create_Stock_Request: Using transaction code 0360 (Create Stock Request), this message creates material stock requests or new demand lines for existing stock requests in the Unfulfilled state.
Inventory_Reservation: Using transaction code 0361 (Reserve), this message creates a request to move existing material stock requests and sales orders from an Unfulfilled state to a Releasable state.
Inventory_Pick_Confirm: Using transaction code 0364 (Pick Confirm), this message creates a request to move existing material stock requests and sales orders from an Unfulfilled or Released state to a Confirmed state.
Inventory_Front_End_Shipping: Using transaction code 0365 (Front-end Ship), this message creates a request to move existing material stock requests and sales orders from an Unfulfilled or Releasable state to a Shipped state. In addition, this service operation can be used to create new material stock requests or new demand lines for existing stock requests in the Shipped state.
Inventory_Shipping: Using transaction code 0366 (Ship), this message creates a request to move material stock orders and sales orders from an Unfulfilled, Releasable, or Confirmed state to a Shipped state. In addition, this service operation can be used to create new material stock requests or new demand lines for existing stock requests in the Shipped state.
PeopleSoft functionality provides a method for communication between external systems and PeopleSoft Inventory using industry standard XML-formatted messages. These XML messages for fulfillment are automatically loaded into the PeopleSoft system by using the PeopleSoft Integration Broker. All five inbound EIPs are contained in the same queue (Inventory_Fulfillment).
The third-party system posts data to the PeopleSoft Integration Broker and receives a response indicating that the data has been received with guaranteed delivery to the requested node. For each active inbound asynchronous service operation defined in the system for the source node and message version, PeopleSoft Integration Broker passes the information to the Fulfillment Request Handler (an application class), which formats the inbound data within the staging tables.
The messages within the service operations have the same format as the fulfillment engine staging table:
Field or Control |
Description |
|---|---|
Header |
Contains fulfillment request transaction header information. |
Group |
Contains fulfillment request group level information. |
Detail |
Contains fulfillment request detail level information. This record could contain demand line level information or data to be excluded from the request (for example, at the group level you could have defined a carrier and then at the detail level you could enter a specific order number to exclude). |
Loc/Lot/Ser (LLS) |
Contains picking location, lot ID, and serial ID information. This level applies only to the front-end shipping and shipping EIPs. |
You can view transactional data from valid EIPs on the Transaction Maintenance page and access the detail pages that enable you to correct application-level errors. Invalid data with system-level errors are rejected before entry on the staging tables. This data can be viewed using the Integration Broker Monitor. System-level errors include these situations:
Invalid XML or message structure.
Transactional data with an invalid PeopleSoft Inventory business unit.
Invalid data in date or numeric fields.
There are five inbound service operations used by the fulfillment engine. 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. The following setup is required to use the Fulfillment Engine EIPs:
Setup within the PeopleSoft Inventory application:
Set up the fulfillment engine processing options using the Setup Fulfillment - Fulfillment Engine Options component.
Setup 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 |
|---|---|---|---|---|
|
INVENTORY_CREATE_STOCK_REQUEST |
Inbound Asynchronous |
InventoryCreateStockRequest |
No |
Third-party system |
|
INVENTORY_RESERVATION |
Inbound Asynchronous |
InventoryReservation |
No |
Third-party system |
|
INVENTORY_PICK_CONFIRM |
Inbound Asynchronous |
InventoryPickConfirm |
No |
Third-party system |
|
INVENTORY_FRONT_END_SHIPPING |
Inbound Asynchronous |
InventoryFrontEndShipping |
No |
Third-party system |
|
INVENTORY_SHIPPING |
Inbound Asynchronous |
InventoryShipping |
No |
Third-party system |