Understanding the PeopleSoft Enterprise eProcurement to JD Edwards EnterpriseOne Procurement Integration

This chapter discusses:

Release levels for the eProcurement integration.
Business process for the eProcurement integration.
Integration architecture for the eProcurement integration.
Integration points for the eProcurement integration.
Assumptions for implementation of the eProcurement integration.

Release Levels for the eProcurement Integration

This document supports the integration between JD Edwards EnterpriseOne 8.12 Procurement and PeopleSoft Enterprise 8.9 eProcurement.

Business Process for the eProcurement Integration

With the PeopleSoft Enterprise eProcurement to JD Edwards EnterpriseOne Procurement integration, you can use PeopleSoft Enterprise eProcurement Direct Connect and Requisitioning processes and pass critical purchase order information to JD Edwards EnterpriseOne Procurement.

The major tasks involved in the integration of PeopleSoft Enterprise eProcurement with JD Edwards EnterpriseOne Procurement are:

Setting up integration options and code cross-referencing in the JD Edwards EnterpriseOne WSG soft-coding/cross-reference database.
Set up the integration in the PeopleSoft Enterprise database.
Loading JD Edwards EnterpriseOne master data into PeopleSoft Enterprise tables.
Synchronizing incremental changes in JD Edwards EnterpriseOne master data with the PeopleSoft Enterprise system.
Creating a purchase order:
1. You create a requisition in PeopleSoft Enterprise eProcurement.
2. You create a corresponding purchase order in the PeopleSoft Enterprise system.
3. The PeopleSoft Enterprise system sends the purchase order to the JD Edwards EnterpriseOne system.
4. The system creates a matching purchase order in the JD Edwards EnterpriseOne system.
5. Budget checking occurs in the JD Edwards EnterpriseOne system, if appropriate.
  
  If the purchase order does not pass budget-checking, the system places the JD Edwards EnterpriseOne purchase order on hold and sends a hold code status update to the JD Edwards EnterpriseOne system.
Releasing the purchase order hold in the JD Edwards EnterpriseOne system.

The purchase order hold is also released in the PeopleSoft Enterprise system.
Dispatching the purchase order from either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system.
Receiving the purchase order in either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system.

The receipt is sent from the system in which it is created to the other system, where a corresponding receipt is created.
Closing the purchase order:
1. In the JD Edwards EnterpriseOne system, you create a voucher for the receipt or cancel the receipt.
2. A close status is transmitted to the PeopleSoft Enterprise system from the JD Edwards EnterpriseOne system.

When you perform any of these integrated actions in the PeopleSoft Enterprise system or in the JD Edwards EnterpriseOne system, the integration updates the purchase order in the other system.

Integration Architecture for the eProcurement Integration

This section discusses the integration architecture for the:

Purchase order creation process.
Purchase order hold release process.
PeopleSoft Enterprise purchase order dispatch process.
JD Edwards EnterpriseOne purchase order dispatch process.
PeopleSoft Enterprise receipt process.
JD Edwards EnterpriseOne receipt process.
Purchase order close process.

Integration Architecture for Purchase Order Creation Process

This diagram illustrates the process of creating a purchase order in the PeopleSoft Enterprise system and creating a corresponding purchase order in the JD Edwards EnterpriseOne system:

PeopleSoft Enterprise purchase order to JD Edwards EnterpriseOne purchase order process

Sending purchase orders from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system consists of these steps:

A PeopleSoft Enterprise user creates a purchase order with the PO_HDR.HOLD_STATUS set to Y.
A PeopleSoft Enterprise user runs the batch process for purchase order EIPs to publish the SAC_PS_PO_EIP message using the Integration Broker and route the EIP message to the Integration Server.
The SAC_PS_PO_EIP message is published by calling the SAC_POEIPPUB Application Engine process.

This process selects only approved purchase orders.
The Integration Server is listening for the EIP message, and triggers the E_PO_To_E1_PO flow, which converts the SAC_PS_PO_EIP message and invokes the processPurchaseOrder interface flow service.
The interface flow creates a purchase order in the JD Edwards EnterpriseOne system.
The JD Edwards EnterpriseOne system performs a budget check on the purchase order. If the purchase order fails the budget check, the JD Edwards EnterpriseOne system places a budget hold on the purchase order.
The interface flow's response is converted to the SAC_EXT_PO_STS_UPD message and sent to the Integration Broker using the dispatcher.

If the purchase order failed the budget check in the JD Edwards EnterpriseOne system, this message contains the hold status.
Once the message is received in the PeopleSoft Enterprise system, the user navigates to eProcurement, Buyer Center, Manage Purchase Orders component to verify that the status has updated accordingly.

When the budget hold is released in the JD Edwards EnterpriseOne system, the PO_HDR.HOLD_STATUS is changed to N, and the purchase order is ready for dispatch.

Integration Architecture for the Purchase Order Hold Release Process

This diagram illustrates the process of releasing a purchase order hold in the JD Edwards EnterpriseOne system and sending a status update to the PeopleSoft Enterprise system:

JD Edwards EnterpriseOne purchase order hold to PeopleSoft Enterprise purchase order status update process

Sending purchase order hold release messages from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system consists of these steps:

In the JD Edwards EnterpriseOne system, the user releases a purchase order from hold using the Release Held Orders program (P43070), which triggers a realtime event RTPOHLDOUT.
The adapter service receives the realtime event and converts it to the notifyHoldStatusEventPublishDocument.
The Integration Server receives the notifyHoldStatusEventPublishDocument and triggers the E1_POHoldStatus_To_E_POStatusUpdate flow, which generates the SAC_EXT_PO_STS_UPD message and sends it to the Integration Broker using the dispatcher.
The Integration Broker uses the message to update the hold status of the purchase order to N (not held from further process).

Integration Architecture for the PeopleSoft Enterprise Purchase Order Dispatch Process

This diagram illustrates the process of dispatching a purchase order in the PeopleSoft Enterprise system and sending a status update to the JD Edwards EnterpriseOne system:

PeopleSoft Enterprise purchase order dispatch to JD Edwards EnterpriseOne purchase order status update process

Note. You can dispatch purchase orders from either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system. We recommend that you dispatch all purchase orders for a specific vendor in one system, though you may dispatch purchase orders for another vendor in the other system.

Notifying the JD Edwards EnterpriseOne system of purchase order dispatches from the PeopleSoft Enterprise system consists of these steps:

In the PeopleSoft Enterprise system, the user dispatches a purchase order.
With the publishing of new or changed purchase orders, the PeopleSoft Enterprise system also publishes any purchase order that has been dispatched.

The SAC_PO_STS_OUT message represents the dispatched purchase order sent to the JD Edwards EnterpriseOne system.
The Integration Server is listening for the EIP message, and triggers the E_PODispatch_To_E1_POStatus flow, which calls an adapter service business function.
The business function updates the status of the purchase order in the JD Edwards EnterpriseOne system.
The E_PODispatch_To_E1_POStatus integration responds with the SAC_EXT_PO_STS_UPD message to indicate whether the transaction was successful, and sends it to the Integration Broker using the dispatcher.
In the PeopleSoft Enterprise system, use the Integration Broker Monitor to verify that the message is complete.

Integration Architecture for the JD Edwards EnterpriseOne Purchase Order Dispatch Process

This diagram illustrates the process of dispatching a purchase order in the JD Edwards EnterpriseOne system and sending a status update to the PeopleSoft Enterprise system:

JD Edwards EnterpriseOne purchase order dispatch to PeopleSoft Enterprise purchase order status update process

Note. You can dispatch purchase orders from either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system. It is recommended that you dispatch all purchase orders for a specific vendor in one system, though you may dispatch purchase orders for another vendor in the other system.

Notifying the PeopleSoft Enterprise system of purchase order dispatches from the JD Edwards EnterpriseOne system consists of these steps:

The user runs the Print Purchase Orders program (R43500) to dispatch the purchase order, which creates an outbound realtime event RTPOOUT.

The event triggers the JD Edwards EnterpriseOne Adapter, which then publishes a notifyPurchaseOrderEventPublishDocument.
The Integration Server is listening for the notifyPurchaseOrderEventPublishDocument, and triggers the E1_PODispatch_To_E_POStatus flow, which generates the SAC_EXT_PO_STS_UPD message and sends it to the Integration Broker using the dispatcher.
The Integration Broker is listening for messages to automatically update statuses.

When a message is received, the dispatch status of the PeopleSoft Enterprise purchase order is set to D.

Integration Architecture for the PeopleSoft Enterprise Receipt Process

This diagram illustrates the process of creating a purchase order receipt in the PeopleSoft Enterprise system and sending receipt information to the JD Edwards EnterpriseOne system:

PeopleSoft Enterprise receipt to JD Edwards EnterpriseOne receipt process

Note. You can create receipts in either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system. A purchase order should be received entirely in either the PeopleSoft Enterprise system or the JD Edwards EnterpriseOne system. Do not partially receive a purchase order in one system and then receive the remaining portion in the other system.

Sending receipts from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system consists of these steps:

Add a new receipt to complete desktop receiving in the PeopleSoft Enterprise system.
Run the Receipt EIP.
The receipt process triggers the SAC_RECPT_OUT message using the Integration Broker and routes the EIP message to the Integration Server.
The Integration Server is listening for the EIP message, and triggers the E_POReceipt_To_E1_POReceipt integration, which converts the SAC_RECPT_OUT message and invokes the processPurchaseOrderReceipt interface flow.
The processPurchaseOrderReceipt interface flow creates the purchase order receipt in the JD Edwards EnterpriseOne system.
The processPurchaseOrderReceipt interface flow's response is converted to the SAC_EXT_RECV _STS_UPD message, and is sent to the Integration Broker using the dispatcher.

Integration Architecture for the JD Edwards EnterpriseOne Receipt Process

This diagram illustrates the process of creating a purchase order receipt in the JD Edwards EnterpriseOne system and sending receipt information to the PeopleSoft Enterprise system:

JD Edwards EnterpriseOne receipt to PeopleSoft Enterprise receipt process

Sending receipts from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system consists of these steps:

Create a receipt in the JD Edwards EnterpriseOne system, which triggers a realtime event RTRECOUT.
The adapter service receives the realtime event and notifies the Integration Server.
The Integration Server triggers the E1_POReceipt_To_E_POReceipt integration, which generates the SAC_EXT_RCPT message and sends it to the Integration Broker using the dispatcher.
The Integration Broker uses the message to create a corresponding receipt record in the PeopleSoft Enterprise system.

Integration Architecture for the Purchase Order Close Process

This diagram illustrates the process of closing a purchase order in the JD Edwards EnterpriseOne system and sending a status update to the PeopleSoft Enterprise system:

JD Edwards EnterpriseOne purchase order close to PeopleSoft Enterprise purchase order status update process

Sending purchase order closes from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system consists of these steps:

A JD Edwards EnterpriseOne user uses the PO Receipts program (P4312) for a three way match or the Voucher Match program (P4314) for a two way match to close a purchase order, which triggers the RTPOOUT realtime event.
The adapter service receives the realtime event and converts it to the notifyPurchaseOrderEventPublishDocument.
The Integration Server receives the notifyPurchaseOrderEventPublishDocument and triggers the E1_POClose_To_E_POStatus integration, which generates the SAC_EXT_PO_STS_UPD message and sends it to the Integration Broker using the dispatcher.
The Integration Broker uses the message to update the status of the purchase order line.

Note. The JD Edwards EnterpriseOne system sends the close status on a line-by-line basis. When all lines on a purchase order are closed, the SAC_EXT_PO_STS_UPD process also sets the PO_HDR.PO_STATUS to C (complete).

Integration Points for the eProcurement Integration

This section lists integration points for:

Initial batch loads
Incremental synchronizations
Transactions

Integration Points for Initial Batch Loads

This table lists the integration points used by the eProcurement integration for the initial batch loads of data from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system:

PeopleSoft Enterprise Message Name	Integration Service Flow	JD Edwards EnterpriseOne Object/Event	Description
SAC_ACCT_LOAD_EIP	E1_Account_To_E_SRM_Account: convertAccountToAccountLoad	Account Master Batch Load program (R8909F0901)	Loads account information from the JD Edwards EnterpriseOne system to accounts in the PeopleSoft Enterprise system.
ITEM_SYNC	E1_ItemMaster_To_E_Item: convert_E1_ItemMaster_To_E_Item	Item Master Batch Load program (R8941F4101)	Loads items from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system. Note. The E1_ItemMaster_To_E_Item flow used for the batch load of items is a different flow from the E1_ItemMaster_To_E_Item flow used for the incremental sync of items.
ITEM_SYNC	E1_ItemCost_To_E_Item: convert_E1_ItemCost_To_E_Item	Item Cost Batch Load program (R8941F4105)	Loads item cost information from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
VENDOR_SYNC	E1_Supplier_To_E_Vendor: convert_E1_Supplier_To_E_Vendor_ And_Dispatch	Supplier Master Batch Load program (R8901F0401)	Loads suppliers from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
ITEM_PRICELIST_LOAD	E1_SupplierItemCost_To_E_SRM_ ItemPriceList: convertSupplierItemCostToItemPriceList	Supplier Price Batch Load - F41061 program (R8945F4161)	Loads supplier item cost information from the JD Edwards EnterpriseOne system to the item price list in the PeopleSoft Enterprise system.
ITEM_SYNC	E1_ItemUOM_To_E_ItemUOM: convert_E1_ItemUOM_To_E_ItemUOM	Unit Of Measure Batch Load (R89F41002)	Batch load of unit of measure conversion from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system. This batch load is optional.
SHIPTO_LOCATION	E1_ShipTo_To_E_ShipToLocation: convert_ShipTo_To_ShipToLocation	Address Book Master Batch Load program (R8901F0101)	Loads address book records for facilities from the JD Edwards EnterpriseOne system to ship to locations in the PeopleSoft Enterprise system.
REQUESTER_LOAD	E1_UserProfile_To_E_SRM_Requester: convertUserProfileToRequester	User Profile/Address Book Batch Load (R89F0092)	Loads JD Edwards EnterpriseOne users as requesters in the PeopleSoft Enterprise system.

Integration Points for Incremental Synchronizations

This table lists the integration points used by the eProcurement integration for the incremental synchronization of data from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system:

PeopleSoft Enterprise Message Name	Integration	JD Edwards EnterpriseOne Object/Event	Description
SAC_ACCT_LOAD_EIP	E1_Account_To_E_Account	notifyGLAccountEvent PublishDocument	Incremental sync of accounts from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
ITEM_SYNC	E1_ItemMaster_To_E_Item	notifyItemMasterEvent PublishDocument	Incremental sync of items from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system. Note. The E1_ItemMaster_To_E_Item flow used for the incremental sync of items is a different flow from the E1_ItemMaster_To_E_Item flow used for the batch load of items.
ITEM_SYNC	E1_ItemCost_To_E_Item	notifyItemCostEvent PublishDocument	Incremental sync of item cost information from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
ITEM_SYNC	E1_ItemUOM_To_E_ItemUOM	notifyItemUOMEvent PublishDocument	Incremental sync of unit of measure conversion from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
VENDOR_SYNC	E1_Supplier_To_E_Vendor	notifySupplierEvent PublishDocument	Incremental sync of suppliers from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system.
LOCATION_SYNC SHIPTO_LOCATION	E1_AddressBookRTE_To_E_ShipToLocation	notifyAddressBook PublishDocument	Incremental sync of ship to locations from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system. This integration point integrates ship to locations when you change a ship to location record in the JD Edwards EnterpriseOne system.
SHIPTO_LOCATION	E1_ShipToRTE_To_E_ShipTo Location	notifyShipToEvent PublishDocument	Incremental sync of ship to locations from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system. This integration point integrates ship to locations when you add a ship to location record in the JD Edwards EnterpriseOne system.

Integration Points for Transactions

This table lists the integration points used by the eProcurement integration for the transfer of transactional data between the PeopleSoft Enterprise system and the JD Edwards EnterpriseOne system:

PeopleSoft Enterprise Message Name	Integration	JD Edwards EnterpriseOne Object/Event	Description
SAC_PS_PO_EIP SAC_EXT_PO_STS_UPD	E_PO_To_E1_PO	processPurchaseOrder	Sends an existing purchase order from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system and creates a corresponding purchase order in the JD Edwards EnterpriseOne system. Notifies the PeopleSoft Enterprise system whether the transaction was successful.
SAC_PO_STS_OUT SAC_EXT_PO_STS_UPD	E_PODispatch_To_E1_POStatus	F4311UpdateAllOrder DetailStatus business function (B4303400)	Updates the purchase order status in the JD Edwards EnterpriseOne system when a purchase order is dispatched in the PeopleSoft Enterprise system and notifies the PeopleSoft Enterprise system whether the transaction was successful.
SAC_EXT_PO_STS_UPD	E1_POHoldStatus_E_POStatusUpdate	notifyHoldStatusEvent PublishDocument	Updates the purchase order status in the PeopleSoft Enterprise system when a purchase order is released from hold in the JD Edwards EnterpriseOne system.
SAC_EXT_PO_STS_UPD	E1_PODispatch_To_E_POStatus	notifyPurchaseOrderEvent PublishDocument	Updates the purchase order status in the PeopleSoft Enterprise system when a purchase order is dispatched in the JD Edwards EnterpriseOne system.
SAC_RECPT_OUT SAC_EXT_RECV_STS_UPD	E_POReceipt_To_E1_POReceipt	processPurchaseOrder Receipt	Sends a purchase order receipt from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system and creates a corresponding purchase order receipt in the JD Edwards EnterpriseOne system. Notifies the PeopleSoft Enterprise system whether the transaction was successful.
SAC_EXT_RCPT	E1_POReceipt_To_E_POReceipt	notifyPurchaseOrderReceipt PublishDocument	Sends a purchase order receipt for the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system and creates a corresponding purchase order receipt in the PeopleSoft Enterprise system.
SAC_EXT_PO_STS_UPD	E1_POClose_To_E_POStatus	notifyPurchaseOrderEvent PublishDocument	Updates the purchase order status in the PeopleSoft Enterprise system when a purchase order is closed in the JD Edwards EnterpriseOne system.

Assumptions for Implementation of the eProcurement Integration

The PeopleSoft Enterprise eProcurement to JD Edwards EnterpriseOne Procurement integration functions based on these assumptions:

Accounts Payable should not be installed in the PeopleSoft Enterprise system; Accounts Payable should reside in the JD Edwards EnterpriseOne system only.
General Ledger should not be installed in the PeopleSoft Enterprise system; General Ledger and Financial Reporting reside in the JD Edwards EnterpriseOne system only.
Inventory should not be installed in the PeopleSoft Enterprise system; Inventory resides in the JD Edwards EnterpriseOne system only.