Understanding the Integration Between the Oracle Business Network, PeopleSoft eProcurement, and PeopleSoft eSettlements

The Oracle Business Network (OBN) is an hosted service offering in which buyers and sellers use a common hub for exchanging and monitoring transactions. The integration between OBN and PeopleSoft enables you to pass the following transactions:

  • Purchase orders and change orders from PeopleSoft to the OBN supplier (outbound transactions). The purchase order is passed to suppliers through OBN. Suppliers can decide their delivery method, and monitor transactions on OBN.

  • Purchase order acknowledgement (POA) or a POA with changes from the OBN supplier to PeopleSoft (inbound transactions). The supplier's POA is sent through OBN to PeopleSoft.

  • Advanced Shipping Notification (ASN) from the OBN supplier to PeopleSoft (inbound transaction). The supplier's ASN is sent through OBN and loaded into PeopleSoft as an advanced shipment receipt (ASR) where you can create a receipt in PeopleSoft.

  • Invoices from the OBN supplier to PeopleSoft (inbound transaction). The supplier's invoice is sent through OBN and loaded into PeopleSoft where you can create a voucher in PeopleSoft eSettlements.

  • Punchout to OBN Supplier from PeopleSoft Fluid Create requisition (outbound transaction). Through eProcurement, requesters are redirected to the supplier site via OBN, where they can browse available products and add selected items directly to their requisition cart.

  • Import OBN supplier catalog items to PeopleSoft eProcurement (inbound transaction). OBN facilitates the suppliers to share their catalog to Peoplesoft, enabling requesters to search, view, and select items from integrated supplier content in the Fluid Create Requisition – Browse Catalogs page.

The following diagram illustrates the communication protocols between PeopleSoft, the Oracle Business Network, and the OBN suppliers. PeopleSoft should use OAG (Open Applications Group) XML for the outbound transaction since OBN supports incoming OAG messages over HTTP. The OBN suppliers can send and receive messages using cXML or OAG.

This image illustrates the communication protocols between PeopleSoft, the Oracle Business Network, and the OBN suppliers.

 Overview of PeopleSoft to Oracle Supplier Network Integration

For outbound transactions from the PeopleSoft eProcurement or Purchasing applications, the PeopleSoft Integration Broker (Integration Gateway) uses application engine transformation programs and the fscm_epo_OSNListeningConnector IB connector to convert XML messages that use the PeopleSoft format (PSXML) into OAG XML files. For inbound transactions from the Oracle Business Network to PeopleSoft eSettlements, OAG XML messages are sent to the PeopleSoft Integration Gateway where transformation programs and the fscm_epo_OSNListeningConnector IB connector convert the incoming files into the PSXML format.