EIPs for Fulfillment Transactions

In an integrated environment, the order fulfillment engine EIPs enable a third-party system to send requests to PeopleSoft Inventory that efficiently move orders to the desired fulfillment state in one step or create new materials stock requests. 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 using service operations. For example, this data can request to move material stock orders and sales orders from one fulfillment state to another. PeopleSoft delivers these asynchronous service operations that enable you to post data to the Integration Broker and receive a response indicating that the data has been received. For each active inbound asynchronous service operation defined in the system for the source node and message version, the Integration Broker places the data in staging tables. The data is then processed by the fulfillment engine using the Fulfillment Requests process. The delivered service operations for inventory demand fulfillment are:

• Inventory Create Stock Request, which enables you to create new materials stock requests or add a new demand line to an existing stock request. These orders are created in the Unfulfilled state.

• Inventory Reservation, which enables you to move orders from an Unfulfilled state to a Releasable state.

• Inventory Pick Confirm, which enables you to move orders from a Released state to the Confirmed state.

• Inventory Front End Shipping, which enables you to move orders from an Unfulfilled or Releasable state to a Shipped state. In addition, this service operation can be used to create new MSRs or new demand lines for existing stock requests in the Shipped state.

• Inventory Shipping, which enables you to move orders from an Unfulfilled, Releasable, or Confirmed state to a Shipped state. In addition, this service operation can be used to create new MSRs or new demand lines for existing stock requests in the Shipped state.

The external third-party freight system EIPs enable PeopleSoft Inventory and PeopleSoft Order Management to integrate with third-party freight providers that supply the sales orders with freight charges and shipping manifesting data.

See Enabling the PeopleSoft EIPs for Third-Party Freight.

The transportation management system (TMS) EIPs enable PeopleSoft Inventory to integrate with a third-party TMS in order to maximize space utilization of loads and thereby minimize the costs of shipping goods. The outbound TMS EIP (TMS Order Release EIP) is a service operation that sends demand information from MSRs and sales orders to the TMS where optimal loads are determined. The inbound TMS EIP receives load optimization data from a TMS and loads the data into PeopleSoft Inventory. This data includes the carriers, loads, and dates based on optimization rules that take place within the TMS. There are two inbound TMS Load Notification EIPs, an asynchronous inbound service operation (TMS_LOAD_NOTIFICATION) and a synchronous inbound service operation (TMS_LOAD_NOTIFICATION_REQ). The synchronous service operation provides a real-time update to PeopleSoft Inventory's production tables.

The Inventory Picking EIP is an asynchronous inbound service operation that receives picking feedback data into PeopleSoft from an electronic data collection system. The data is stored in the transaction log using any one of three transaction codes: Pick Location (0301), Complete Pick Batch Line (0302), and Complete Pick Batch (0303).

The Shipping Order Release EIP is an outbound asynchronous service operation that provides third-party systems with details of orders that have been released for picking and shipment. This EIP supports integrated implementations in which a third-party system is used to pick, pack, and ship orders. With this EIP, you can send both XML-based data and flat files. The Shipping Order Release EIP meets X.12 EDI requirements of the 940 − Authority to Ship Customer Order transaction set.

The Advanced Shipping Notice (ASN) EIP is an asynchronous outbound service operation used to notify your customers that a sales order has been shipped. This data is passed to an external system or to the PeopleSoft CRM Field Service and PeopleSoft CRM Order Capture applications. The Advanced Shipping Notice EIP meets X.12 EDI requirements of the 856-Shipping Notice/Manifest transaction set and is also used with warehouse management systems. An ASN service operation is generated when a sales order entered from PeopleSoft Order Management has been depleted in PeopleSoft Inventory. You can specify whether to generate the ASN for all sales order shipments in the business unit, sales orders belonging to a specific shipping ID, sales orders for a specific sold to customer, or sales orders for a specific ship to customer.

The Internal Location Expected Receipt EIP is a asynchronous outbound service operation that sends notification of an expected receipt transaction when an internal MSR is depleted. Internal MSRs are created to fulfill demand from a material storage location within the PeopleSoft Inventory business unit. Typically, you use the Internal Location Expected Receipts EIP when integrating with third-party point-of-use (POU) supplier systems or surgical resource management systems that manage supplies stored in internal par locations. The third-party system can use the data contained in the service operation to manage receiving and restocking activities at the destination location. The Internal Location Expected Receipts EIP can be used with surgical resource software and POU applications.

The InterUnit Expected Receipt EIP is an asynchronous outbound service operation used to notify a third-party system that a PeopleSoft Inventory business unit has shipped an interunit transfer order. The Interunit Expected Receipt EIP meets X.12 EDI requirements of the 943 - Warehouse Stock Transfer Shipment Advice transaction set and is also used with warehouse management systems. Interunit transfer orders are created in PeopleSoft to move stock between PeopleSoft Inventory business units. Typically, you use the Interunit Expected Receipt EIP in integrated implementations in which a third-party system is controlling a PeopleSoft Inventory business unit. Transactional data is generated when an interunit transfer order with a destination business unit that is under external warehouse control is depleted. The third-party system can use the information from the interunit expected receipt service operation to validate the receipt of goods when the shipment arrives at the destination warehouse.

The Purchase Order and InterUnit Transfer Information request/response business interlink (GETPOIUT and RF_GETPOIUT) provides a third-party or another PeopleSoft database information regarding purchase orders and interunit transfer orders based on the business unit and requisition ID sent in on the request. This business interlink (RF_GETPOIUT ) can be integrated with the PeopleSoft CRM Field Service database.

To set up a business interlink, use PeopleTools to:

• Enter the correct merchant URL on the Business Interlink definition.

• Enter the correct userID/password on the Business Interlink definition.

  This userID/password should be the same as the userID/password defined for the web profile.