Integrating PeopleSoft eProcurement Transactions with a Marketplace

Marketplace Catalog Search Integration

The Marketplace catalog search is an application that hosts multiple supplier catalogs within the Marketplace.

This diagram illustrates an overview of Marketplace catalog search launched by an PeopleSoft eProcurement user. Users are transferred to the MarketPlace catalog search, where they can search the aggregated supplier catalog and return results to the shopping cart within PeopleSoft eProcurement.

This diagram illustrates an overview of Marketplace catalog search launched by an PeopleSoft eProcurement user.

To set up and use the Marketplace catalog search, you must:

1. Set up security that enables requesters to move from the eProcurement requisition into the Marketplace.

2. Create supplier profiles and supplier locations, and link the properties of that supplier to the information that creates a link to a Marketplace.

   Note: Upon completion of this setup, a link will be provided in the eProcurement requisition. Selecting this link directs the requester to the Marketplace site.

3. Set up background details that determine which supplier catalogs the requester can view.

   The Marketplace validates requester security and displays the catalogs that the requester can view. The requester selects catalog items and returns to the requisition. The system populates the selected items as requisition lines.

Receipt of Purchase Order Acknowledgements from a Marketplace

The purchase order acknowledgement (POA) is a collaboration among the supplier, the Marketplace, and the PeopleSoft application. To create and transmit a POA, these steps must occur:

1. Once the purchase order has been dispatched from PeopleSoft, the supplier logs into the Marketplace and finds that the purchase order is available in a queue for that specific supplier. Suppliers can initiate a POA document from the Marketplace.

2. The Marketplace then transmits xCBL formatted POA to PeopleSoft, where it is transformed to the PeopleSoft internal format PSXML.

3. The inbound message populates the PO Electronic Commerce tables.

4. If the POA results in changes; a change order may be generated.

This diagram represents the flow of the POA from the Marketplace.

Two options are available for receiving a purchase order acknowledgement from a supplier. The first is a POA, which uses the PeopleSoft Purchasing functionality and stores the status within Purchasing tables. The second is the POR (purchase order response), which is where you can view the status from the PO Dispatch Message page. eProcurement > Buyer Center > Dispatch Purchase Order > Dispatch Message Log.

Receipt of an Advanced Shipment Notification (ASN)

The supplier uses the advanced shipping receipt (ASR) enterprise integration point (EIP) to notify the PeopleSoft system that the order has been fulfilled. To complete the integration, these steps must occur:

1. A supplier is able to enter advanced shipping notifications (ASNs) within the Marketplace site.

2. Once submitted, Integration Broker transforms this data to the PeopleSoft inbound ASR message using the Advanced Shipping Receipt (ADVANCED_SHIPPING_RECEIPT) service operation in PeopleSoft.

3. The message populates the Receipt Load tables.

4. The Receipt Loader process is then run to create a receipt, which may then be approved by an administrator.

This diagram represents the flow of the supplier-entered ASN from the Marketplace.

Receipt of an Invoice

When an integrated supplier creates and invoice and sends it to the Marketplace, or when an invoice is created, the Marketplace sends the invoice to the Integration Broker. Integration Broker then transforms the invoice from xCBL 3.0 to the PeopleSoft inbound XML invoice message.

From the Integration Broker, the Marketplace partner ID (MPID) that is passed from the Marketplace is used to look up the supplier ID field using the Linked Supplier table. The supplier SetID and supplier ID are retrieved based on this information.

Once the supplier ID is established, the invoice is loaded to the voucher staging tables.

When the data is in the staging tables, these steps take place:

1. Voucher build is run.

2. Voucher is created.

3. Matching may be run if the voucher has an associated purchase order or receipt.

4. Paycycle process creates a payment.

This diagram represents the flow of an invoice from the Marketplace as defined in the above steps.

This diagram represents the flow of an invoice from the Marketplace.

PeopleTools: Integration Broker

Setting up Supplier Profiles

Access the Supplier Information - Summary page.

Navigation:

eProcurement > Administer Procurement > Maintain Suppliers > Supplier Information

To enable the Marketplace integration, you must complete these tasks:

1. Create a supplier profile for the Marketplace.

2. Create supplier locations for every login ID you have with the Marketplace.

3. Create supplier profiles for each supplier you do business with within the Marketplace.

4. Create link supplier identifiers for each supplier location.

See Understanding Supplier Maintenance.

Using Rule-Based Catalogs with the Marketplace

Rule-based catalogs are a form of security within PeopleSoft eProcurement. As an administrator, you have the option of allowing requesters visibility of catalogs, as well as the links to the direct connect suppliers, based on the criteria you define within the catalog security. The Marketplace is considered a direct connect supplier in this case. You can determine requester access based on role, business unit, or a specific requester ID. Think of each Marketplace catalog search link as a different catalog. Use rule-based catalogs to help in determining which catalogs requesters are capable of viewing upon login to the Marketplace.

See Understanding Catalog Security.