Using PeopleSoft eProcurement with a Marketplace

This chapter provides an overview of the integration between a Marketplace and PeopleSoft eProcurement, lists prerequisites and common elements, and discusses how to:

• Set Up Marketplace suppliers and buyers.

• Set up integration with a Marketplace.

• Load Marketplace catalog items into PeopleSoft eProcurement.

• Use price and availability check.

• Set up Integration Broker for Marketplace transactions.

• Integrate PeopleSoft eProcurement transactions with a Marketplace.

Understanding the Integration Between a Marketplace and PeopleSoft eProcurement

This overview discusses:

• Integration between a Marketplace and PeopleSoft eProcurement.

• Marketplace integration set up.

• Marketplace EIPs.

Integration Between a Marketplace and PeopleSoft eProcurement

A Marketplace is an electronic trading community in which buyers and sellers use a common internet portal. Integrating the PeopleSoft eProcurement system with Marketplace suppliers enables you to review the latest supplier catalogs and prices in a Marketplace, and then download these catalogs into eProcurement. When you connect a Marketplace with eProcurement, you can:

• Load or update items from a Marketplace into eProcurement catalogs and use these items on eProcurement requisitions and purchase orders.

• Pass purchase orders/change order created in PeopleSoft eProcurement to a Marketplace where suppliers receive the orders and review them.

• Pass the supplier’s response to the purchase order from a Marketplace to eProcurement.

  In a Marketplace, the supplier responds by accepting or rejecting the purchase order. This response is passed to PeopleSoft eProcurement where it is inserted in the PO Dispatch Message Log page. The status of the PO in eProcurement changes to Dispatched.

• Load or create a receipt using advanced shipment receipt (ASR).

• Load or create an voucher/invoice for the purchase order.

• Use the price check feature in PeopleSoft eProcurement to update an item’s price to match the current price in a Marketplace.

  Users receive the latest price for an item. This is especially important when prices fluctuate frequently.

• Use the availability check feature in PeopleSoft eProcurement to update an item’s available quantity to match the supplier’s available quantity in a Marketplace.

  Users know before submitting an order whether stock is currently available.

• Use the order status feature in PeopleSoft eProcurement to request the current status of the purchase orders submitted to a Marketplace.

Note. Not all suppliers may support all features of this integration. For example, availability check is not going to work unless the supplier has integrated their inventory system with a Marketplace.

Marketplace Integration Set Up

To set up the connection between PeopleSoft eProcurement and a Marketplace:

1. Set up the Application Message Gateway nodes and note the address.

   When a supplier accepts or rejects a purchase order through a Marketplace, the system posts an XML document to PeopleSoft eProcurement. The system then changes the purchase order’s status to Dispatched; and inserts the supplier’s response in the PO Dispatch Message Log page. If the supplier rejects the order, you must cancel the original PO and create a new one.

2. Add Marketplace suppliers as PeopleSoft vendors, using the Vendor Information component.

3. Set up Marketplace suppliers as eProcurement vendors, using a Marketplace Supplier Setup page.

4. Use the Marketplace Buyers - Buyer Setup page to link the SetID used in the PeopleSoft eProcurement record group as a buyer in a Marketplace.

   Note. All transactions for PeopleSoft eProcurement are stored within business units. These business units are linked to the record group eProcurement (PV_01) using a SetID on the Table Control - Record Group page. In order to pass transactions to a Marketplace, the SetIDs used must be defined as a Marketplace buyer using the Marketplace Buyers - Buyer Setup page.

   Note. If you are using xCBL 2.0 or Business Interlinks, then you need to enter the internet address of the Application Message Gateway node of the Buyer Setup page. If you use Integration Broker, the internet address is not required.

5. Synchronize shared data that is transferred between PeopleSoft eProcurement and a Marketplace.

   To prevent validation errors during the transfer of data between PeopleSoft eProcurement and a Marketplace, ensure that common control data is identified by the same codes. This common data includes units of measure, currency codes, country codes, language codes, and so on.

Marketplace EIPs

To support integrated implementations in which you use a third-party system to acquire goods and services, PeopleSoft eProcurement provides these EIPs:

• PV_AVAIL_CHECK_REQ:

  Checks for the availability of items with a supplier.

• PV_AVAIL_CHECK_RESP:

  The supplier responds with the availability of the items.

• PV_MS_RESP_MSG:

  PeopleSoft eProcurement PO response from a Marketplace.

• PV_ORD_STS_REQ:

  Checks the order status with the external system.

• PV_ORD_STS_RESP:

  PeopleSoft eProcurement gets a response to the order status request.

• PV_PRICE_CHECK_REQ:

  Checks prices available from the Marketplace supplier.

• PV_PRICE_CHECK_RESP:

  Gets the response to the price check request.

Prerequisites

Before integrating a Marketplace with eProcurement, all Marketplace suppliers to be used in eProcurement must be set up as PeopleSoft eProcurement vendors.

See Maintaining Vendor Information.

Common Elements Used in This Chapter

Setting Up Marketplace Suppliers and Buyers

To set up linked suppliers for a Marketplace, use the Linked Supplier component.

To set up Marketplace buyers and buyer options, use the Marketplace Buyers component.

This section discusses how to:

• Set up Marketplace suppliers.

• Identify SetIDs to be defined as Marketplace buyers.

• Set up Marketplace buyers.

• Define Marketplace buyer options.

Pages Used to Set Up Marketplace Suppliers and Buyers

See Also

Maintaining Vendor Information

Setting Up Marketplace Suppliers

Setting up Marketplace Buyers

Setting Up the Gateway for a Marketplace

Setting Up Marketplace Suppliers

Access the Linked Suppliers page.

Linked Supplier ID	Enter a 64-bit universally identifier for a Marketplace trading partner. A trading partner is a buyer or seller in a Marketplace. Supplier participant ID’s are defined within a Marketplace and cannot be changed. The system uses ID’s to identify the supplier of an item when transferring information between a Marketplace and eProcurement. This is a required field.
Linked Supplier Name	Enter the name of the supplier.
Buyer Account Code	The code used by a Marketplace supplier to identify the PeopleSoft eProcurement buyer.
EDX PO Dispatch Type (electronic data transfer purchase order dispatch type)	Defines the format of the purchase order document to be dispatched to the Marketplace. Note. PeopleSoft currently supports cXML1.2 and xCBL3.0 formats.
PO Dispatch Node (purchase order dispatch node)	Select the node to be used for the dispatch type.
Direct Connect Method	Select the method you wish to connect to the supplier with. PunchOut uses the cXML 1.2.008 standard, and RoundTrip uses the RoundTrip standard based off of the OCI 2.0b spec.
Direct Connect Node	Select the node that you want to use to link to the vendor. Use the Integration Broker Node Definition link to create a node and its characteristics.

Note. You associate each Linked Supplier with its specific Direct Connect Node. It is a one-to-one relationship. You may not associate several Linked Suppliers to a single Direct Connect Node.

Identifying SetIDs to be Defined as Marketplace Buyers

The Marketplace Buyers component enables you to define and test the connection to a Marketplace. The PeopleSoft eProcurement application is defined as a buyer within a Marketplace, so that information can be exchanged.

The SetID defines a Marketplace buyer. If you have multiple business units for PeopleSoft eProcurement, you might have multiple Marketplace buyers.

To determine the SetIDs that must be defined as Marketplace buyers:

1. Identify the Purchasing business units that are used to record PeopleSoft eProcurement purchase orders that are passed to a Marketplace.

2. Access the Tableset Control - Record Group page.

   In the Set Control Value field, enter in the business unit. On the Tableset Control - Record Group page, look up the SetID used for the eProcurement record group. The record group ID is PV_01.

3. Use the Marketplace Buyers - Buyer Setup page to define a buyer for this SetID.

See Also

Creating Business Unit Options

Setting up Marketplace Buyers

Access the Marketplace Buyer Setup page.

Define a Marketplace buyer for each SetID used to link a business unit to the PeopleSoft eProcurement record group PV_01.

Defining Marketplace Buyer Options

Access the Marketplace Buyer Options page.

Note. In order for you to have read or write access to the log files, the log file location must be accessible by the application server, process scheduler server, and the client. Write access should be granted to the application server and the process scheduler server. The client servers should have read access.

Log Files

Test Marketplace Connectivity

See Also

Dispatching Purchase Orders in PeopleSoft eProcurement

Creating Requisitions in PeopleSoft eProcurement

Setting Up Integration with a Marketplace

This section discusses how to:

• Establish a Marketplace connection using PeopleSoft Integration Broker.

• Set up the gateway for a Marketplace.

• Set up nodes.

• Set up the relationships.

Pages Used to Set Up Integration with a Marketplace

Establishing a Marketplace Connection using PeopleSoft Integration Broker

To establish a Marketplace connection using PeopleSoft Integration Broker:

1. Install the Marketplace connection files by running the self-extracting zip MPC-IB.exe file.

2. Select the Overwrite files without prompting check box.

3. Extract the file to the C:\PT8.44\webserv\peoplesoft\applications\ peoplesoft\PSIGW\WEB-INF directory.

4. Replace PT8.44 with a user-defined PeopleTools installation directory.

5. Configure the WebLogic environment by:

   1. Verifying that the web server has been stopped.

   2. Adding the Marketplace connection files to the class path in the C:\PT8.44\webserv\peoplesoft\setEnv.cmd directory.

      In the :setEnv section of the setEnv.cmd file, add these lines:

      SET MPC_LIB=C:\PT8.44\webserv\peoplesoft\applications\ peoplesoft\PSIGW\WEB-INF\lib\mpc

      Make sure this one line with no returns in the line. SET MPC_CP=%MPC_LIB%\bussdocs.jar;%MPC_LIB%\ccs_dir.jar;%MPC_LIB%\ccs_event.jar;%MPC_LIB%\ccs_util.jar;%MPC_LIB%\ccs_xdk.jar;%MPC_LIB%\ent_misc.jar;%MPC_LIB%\xcbl30.jar;C:\PT8.44\webserv\peoplesoft\applications\peoplesoft\PSIGW\WEB-INF\classes\com\peoplesoft\pt\integrationgateway\targetconnector\mpc.

      Then add the value %MPC_CP% into the CLASSPATH. The last SET line should look similar to: SET CLASSPATH=%MPC_CP%;% PSCLASSPATH%;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;%CLASSPATH%

6. Configure the integration gateway properties by:

   1. Searching for the ig.log.level property and setting the level to 4.

      Note. Level 4 is for testing. Once everything is done and listed, set the level back to 2 or the original log setting.

   2. Editing the file: C:\PT8.44\webserv\peoplesoft\applications\ peoplesoft\PSIGW\WEB-INF\integrationGateway.properties.

      Configure the ig.isc properties. You can control the logging level with the ig.log.level property.

   3. Entering these Marketplace connection attributes if you require their functionality:

      ig.mpc.validateSchema: This true/false option enables users to ensure that values in the XML document are valid in the xCBL schema. As a default value, the schema is validated. If special character functionality is enabled, schema validation is disabled automatically.

      ig.attachmentDir: This directory holds attachments for the Marketplace connection. Use this directory: \bea\wlserver6.1\config\ peoplesoft\applications\PSIGW\WEB-INF\classes\com\peoplesoft\pt\integrationgateway\targetconnector\mpc\attachments.

      ig.mpc.asciiTypesFile:This file holds information on whether a file should be transferred as binary or ASCII file for attachments. Use the file: \bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-INF\ classes\com\peoplesoft\pt\integrationgateway\targetconnector\mpc\ascii_types.txt.

      ig.mpc.checkSpecialChars:If Spanish, French, or other non-7bit characters are to be checked, set this value to true.

      ig.mpc.specialCharFile: This file contains number codes for the special characters. Use the file: \bea\wlserver6.1\config\peoplesoft\ applications\PSIGW\WEB-INF\classes\com\peoplesoft\pt\integrationgateway\targetconnector\mpc\special_characters.txt.

      This example is for web logic 6.1 and illustrates the previous steps. The details will be different if you are using web logic 8.1. You must use forward slashes (/) instead of backslashes (\).

      ig. ig.mpc.validateSchema=false
      mpc.attachmentDir=c:/bea/wlserver6.1/config/peoplesoft/applications/PSIGW/WEB-INF/classes/com/peoplesoft/pt/integrationgateway/targetconnector/mpc/attachments
      ig.mpc.asciiTypesFile=c:/bea/wlserver6.1/config/peoplesoft/applications/PSIGW/WEB-INF/classes/com/peoplesoft/pt/integrationgateway/targetconnector/mpc/ascii_types.txt
      ig.mpc.checkSpecialChars=true
      ig.mpc.specialCharFile=c:/bea/wlserver6.1/config/peoplesoft/applications/PSIGW/WEB-INF/classes/com/peoplesoft/pt/integrationgateway/targetconnector/mpc/special_characters.txt
      

7. Add the Marketplace certificate.

   In order for the PeopleSoft Integration Broker gateway to make HTTP calls, the certificate of the server to which you are connecting must be in a list of trusted certificate authorities. In addition, the host name in the URL must match the host name on the certificate. Obtain the Marketplace CA certificate (with a .cer extension) and run these lines from the command prompt:

   C:\PT8.44\webserv\peoplesoft\pskeymanager.cmd —import Alias: eScout_CA.cer Name: eScout_CA.cer

   C:\PT8.44\webserv\peoplesoft\pskeymanager.cmd —import Alias: wbmQA_cert.cer Name: wbmQA_cert.cer

   Note. Certificate names may vary.

8. Configure the purchase order response listening connector servlet.

   In order to receive purchase order responses from the Marketplace, you use a servlet for the listening connector. To set this up, edit the \bea\wlserver6.1\config\peoplesoft\ applications\PSIGW\WEB-INF\web.xml file. Under the <web-app> tag, next to the rest of the <servlet> tags, add these lines:

       <servlet>
           <servlet-name>MarketSiteListeningConnector</servlet-name>
           <servlet-class>com.peoplesoft.pt.integrationgateway.listeningconnector.MarketSiteListeningConnector</servlet-class>
       </servlet>
   

   Then with the rest of the <servlet-mapping> tags, you need to add:

   <servlet-mapping>
           <servlet-name>MarketSiteListeningConnector</servlet-name>
           <url-pattern>/MarketSiteListeningConnector/*</url-pattern>
       </servlet-mapping>
   

9. Start the web server, app server, and PeopleSoft Process Scheduler.

   If WebLogic is being started as a service, then you must uninstall the service, then reinstalled it for the setEnv.cmd changes to take affect.

See Also

PeopleTools PeopleBook: PeopleSoft Integration Broker

Setting Up the Gateway for a Marketplace

Access the Gateways page.

To set up the gateway:

1. Click the Search button for a list of gateway IDs and select LOCAL.

   Or you can also use the Gateway Integration ID field, to enter: http://<host>:<port>/PSIGW/PeopleSoftListeningConnector.

2. Click the Load button and verify that the MarketSiteTargetConnector is available.

Setting Up Nodes

Access the Node Definitions page.

Setting Up a Marketplace Connection Node

To set up a Marketplace connection node with order and PO response transactions:

1. Select the Add a New Value tab.

2. Enter PV_MPC_NODE, and click Add.

3. Enter a Description of MarketSite Node.

4. Select External in the Node Type field.

5. Select Explicit in the Routing Type field.

6. Select None in the Authentication field.

Access the Connectors page.

1. Select MARKETSITECONNECTOR in the Connector ID field.

   Three properties appear in the Properties section.

2. Enter the Marketplace URL in the Value field for the primary URL property.

3. Click Save.

Access the Transactions page.

1. Click the Add Transaction button to create the order transaction.

   The Node Transactions page appears. The node name uses a default value to the current node (PV_MPC_NODE).

2. Select Outbound Asynchronous in the Transaction Type field.

3. Select PV_ORDER in the Request Message field.

4. Select VERSION_1 in the Request Message Version field.

5. Click Add, and set the Status field to Active.

6. Click the Return to Transaction List link on the right side of the page.

   Now, you create the Order Response transaction using the same steps:

   1. Click the Add Transaction button to create the Order Response transaction.

      The Node Name field default value is to the current node (PV_MPC_NODE).

   2. Select Inbound Asynchronous in the Transaction Type field.

   3. Select PV_MS_RESP_MSG in the Request Message field.

   4. Select VERSION_1 in the Request Message Version field.

   5. Click Add, and set the Status field to Active.

7. Click the Return to Transaction List link on the right side of the page.

   Again, you create another Order Response transaction using the same steps:

   1. Click the Add Transaction button to create the Order Response transaction.

      The Node Name field default value is to the current node (PV_MPC_NODE).

   2. Select Inbound Asynchronous in the Transaction Type field.

   3. Select PV_MS_XCBL_POR in the Request Message field.

   4. Select VERSION_1 in the Request Message Version field.

   5. Click Add, and set the Status field to Active.

Setting Up the Local Node with Order and Purchase Order Response Transactions

Access the Node Definitions page.

To set up the local node with order and PO response transactions:

1. Select a local node, such as PSFT_EP.

2. Select the Transaction tab, and click the Add Transactions button to create an outbound order.

3. Select Outbound Asynchronous in the Transaction Type field, PV_ORDER in the Request Message field, and VERSION_1 in the Request Message Version field.

4. Click Add to access the Transaction Details page.

5. Set the Status to Active and the Routing Type to Explicit.

6. Click Save, and then click the Return to Transaction List link.

Note. For one supplier, only one node can be used for outbound documents. You can use either PSFT_SUPPLIER_NETWORK or PV_MPC_NODE You can also opt to define the own instead.

See Also

PeopleTools PeopleBook: PeopleSoft Integration Broker

Overview of Definitions and Relationships

Setting Up Relationships

Access the Relationships page.

Setting Up the Order Relationship

Relationships are delivered as part of the PeopleSoft system. This is an example of how to set up a relationship:

1. Select the Add a New Value tab.

2. Enter Purchase Order Relationship in the Description field.

3. Select Active in the Relationship Status field, PSFT_EP in the upper Node Name field and PV_MPC_NODE in the lower Node Name field.

4. Click Save and the Transaction Modifiers (list) page appears.

5. Click the Add Transaction Modifier button and select these values for the new transaction modifier:

   1. Relationship ID: PV_ORDER_REL.

   2. Initial Node: PV_MPC_NODE.

   3. Request Message Name: PV_ORDER.

   4. Source Request Message Version: VERSION_1.

   5. Transaction Type: OA.

   6. Result Node: PV_MPC_NODE.

   7. Request Message Name: PV_ORDER.

   8. Target Request Message Version: VERSION_1.

6. Click Add, and the Transaction Modifiers page appears.

7. Select Active in the Status field, OA in the Transaction Type field, and PV_ORD_TXFR in the Request field.

8. Click Save.

Setting Up the Purchase Order Response Relationship

To set up the relationship for the PV_POR_REL order:

1. Select the Add a New Value tab.

2. Enter POR Relationship / Transform in the Description field.

3. Select Active in the Relationship Status field, PV_MPC_NODE in the upper Node Name field and PSFT_EP in the lower Node Name field.

4. Click Save, and the Transaction Modifiers page appears.

5. Click the Add Transaction Modifier button and select these values for the new transaction modifier.

   1. Relationship ID: PV_POR_REL.

   2. Initial Node: PV_MPC_NODE.

   3. Request Message Name: PV_MS_XCBL_POR.

   4. Source Request Message Version: VERSION_1.

   5. Transaction Type: IA.

   6. Result Node: PV_MPC_NODE.

   7. Request Message Name: PV_MS_RESP_MSG.

   8. Target Request Message Version: VERSION_1.

6. Click Add, and the Transaction Modifiers (details) page appears.

7. Select Active in the Status field and IA in the Transaction Type field.

8. Select PV_FIX_PORX3 in the Transformations Request field for xCBL 3.0, or if you are using xCBL 2.x, select PV_FIX_PORX2.

9. Click Save.

See Also

Overview of Definitions and Relationships

Setting up Marketplace Buyers

Setting Up Common Components for Direct Connect

Loading Marketplace Catalog Items into PeopleSoft eProcurement

This section provides an overview of loading Marketplace items into PeopleSoft eProcurement and discusses how to:

• Download supplier flat files.

• Extract data from a CUP file.

• Export CUP data.

• Load CUP files.

• Define item import defaults.

• Validate and process imported items.

• Edit imported item categories.

• Maintain imported item statuses.

• Load Marketplace items.

• Correct inventory item load errors.

• Download item attachments.

Understanding Loading Marketplace Items into PeopleSoft eProcurement

After you set up connections to a Marketplace, you can load items from Marketplace catalogs into PeopleSoft eProcurement. These Marketplace items can be entered on eProcurement requisitions and purchase orders. You can also update prices and check available quantities for Marketplace items in PeopleSoft eProcurement. After you load the items, you should schedule regular updates to capture changes such as price changes, discontinuation of items, or the addition of new items.

To load a CUP file into the system, you complete these steps:

1. Import the product and price files to PeopleSoft eProcurement, using the Import CUP File process (PV_CUP_LOAD).

   This application engine process loads the product and price flat files into the PV_CP_LOAD and PV_CP_CAT_TMP staging tables. The attachment file is loaded into the PV_CP_ITM_XREF table.

2. Use the Validate and Process Imported Items page to validate the CUP file data in the staging tables, adding or changing information as necessary.

3. Use the Edit CUP Item Categories page Edit CUP Item Categories page to review any new item categories added for the items loaded from a Marketplace.

   Each new item category requires a default account (the top level of the PeopleSoft ChartFields). This account is used to record the accounting entries created by ordering items in this item category.

4. Review the CUP status of the item on the CUP Items Status page.

5. Run the Load Marketplace Items process (PV_CP_ITM_LOAD).

   This process loads items with a status of Ready to Build Items (new items) or Items to be Updated from the staging tables into the PeopleSoft Item Master tables.

6. Use the Data Definition Maintenance page to review any errors for items that were not loaded properly.

   Select the ITEM transaction type and enter the SetID for the items. Select the stage table option with an Error status, then click the Query button. Any errors appear at the bottom of the page.

7. Go to the eProcurement Installation Options page after you have successfully loaded the items.

   If the Catalog Search Type field is populated with FSE, run the Item Search Update process. If the Catalog Search Type field is populated with VSE, run the Build Verify Search Collection process (PV_SRCH_RUN_INDEX).

   Note. When you select the search catalog method of FSE, the system uses a different index table during requisition entry to search for all available items. By running the Item Search Update process, you are updating this index table with the new items. It is important to run this process whenever you add or change any items in PeopleSoft eProcurement.
   
   If you select the Index Items check box on the Procurement Catalog Load page, this process is run automatically.

This diagram illustrates the process of loading Marketplace items into PeopleSoft eProcurement:

Load Marketplace items into PeopleSoft eProcurement process flow

To set up the system to utilize the CUP Load process, you need to complete these tasks:

1. Provide locations for the product, price, and attachment files from the supplier.

2. Load the CUP file to extract the data from the input files and place them in the Inventory tables.

3. Provide item defaults such as account number and currency information.

4. Validate items being imported into the PeopleSoft systems.

5. Correct errors that may occur in the extraction process.

Pages Used to Load Marketplace Catalog Items into PeopleSoft eProcurement

Downloading Supplier Flat Files

PeopleSoft will search for three files to be on the system to successfully move the supplier data into the PeopleSoft Inventory tables. These three files are:

• A product file containing item information.

• A price file containing pricing information.

• An attachment file containing information on each item’s attachments.

The CUP file that you download from a Marketplace may reside in a Microsoft Access database. The Export CUP Data process (PS_CUP_EXPORT.EXE) uses SQL (structured query language) statements to retrieve the necessary data from the Microsoft Access database.

To load Marketplace catalog items into PeopleSoft eProcurement from a Microsoft Access database:

1. Download the supplier’s latest CUP (Catalog Update process) file using the instructions on the Marketplace's website.

   The machine on which you run the Export CUP Data process must have Microsoft Data Access Components installed.

2. Navigate to the ps_home\setup folder, and run the program mdac_typ.exe.

3. Install the Microsoft Data Access Components.

4. Extract and export information from the Microsoft Access database to flat files, using the PeopleSoft eProcurement Export CUP Data process (PS_CUP_EXPORT.EXE)

   Note. This process builds one to three flat files: a product file containing item information; a price file containing pricing information, and an attachment file containing a cross-reference to the item images and attachments.

See Also

Importing and Searching Supplier Catalogs

Implementing the Verity Search Engine

Extracting Data From a CUP File

Not all data in the CUP file is retrieved, only the information needed by PeopleSoft. This Visual Basic (VB) program is delivered with PeopleSoft eProcurement.

PeopleSoft retrieves this information from a CUP file:

Item Information (Product File)

Pricing Information (Price File)

Note. The item’s long description is loaded from the CUP file into a cross-reference table called PV_CP_ITM_XREF, and the item’s image is loaded into a web server directory. The description and image both appear when you view the item in PeopleSoft eProcurement.

Exporting CUP Data

Use the Export CUP Data process to create the three flat files for the PeopleSoft system to utilize when importing the supplier data into the Inventory tables.

Input Access Database (CUP File)

Output Text Files

Loading CUP Files

Access the Procurement Catalog Load page.

Note. The product and price files are loaded into the staging tables PV_CP_LOAD and PV_CP_CAT_TMP. This process adds certain defaults that were not in Marketplace catalog tables to required fields in PeopleSoft’s Item tables. The attachment file is loaded into the table PV_CP_ITM_XREF.

Import Catalog Items

Note. Before running this process, verify the settings for requiring item approval. If you select the Item Approval Required check box on the Installation Options - Overall/GL page, all items that you load require approval. If you are loading thousands of items, you might not want to approve each item individually.

Options

The Run Load process loads the data from the PV_CP_LOAD and PV_CP_CAT_TMP staging tables to the production tables for PeopleSoft items.

The process of loading data includes four steps:

1. The Build PeopleSoft Items process (PV_CP_ITM_LOAD) adds new item categories and then loads Marketplace CUP items into the PO item staging tables (ITM_LOAD_MST_EC, ITM_LOAD_INV_EC, ITM_LOAD_PUR_EC, and ITM_LOAD_VND_EC).

2. The Load Item Stage process (PO_ITMLOAD) transfers the data to the item loader staging tables.

3. The Item Loader process (IN_ITMLOAD) transfers the data into the PeopleSoft production tables.

4. The item status is updated on the CUP Item Status page.

The Load Marketplace Items process also adds certain defaults that were not in Marketplace catalog tables to the required fields of the PeopleSoft Item Master tables. This information is hard coded into the Item Catalog PS_ITM_CAT_TBL table:

This information is hard coded into the Item PS_ITM_LOAD_PUR_EC table:

See Also

Setting Up Installation Options

Setting Up Attachments for Transactions

Validating and Processing Imported Items

Defining Item Import Defaults

Access the Item Defaults page.

Image Folder	Enter the file location that contains images for use with the catalog items that you import.
Inventory Item	Select to indicate this item is also a PeopleSoft Inventory item. This means you can source the item from Inventory.
Account	Select an account to which you want the categories to belong.
Currency	Select the currency to use with this category.

Validating and Processing Imported Items

You use the Validate and Process Imported Items page to review categories and items, determine the state the items are in, and to load the staged items into the Inventory tables.

Access the Validate and Process Imported Items page.

Categories	This link takes you to the Edit Imported Items Categories page.
View Items	This link takes you to the Imported Item Status page.
Load Staged Items	When you have determined that the results are satisfactory, you can load the staged items from the eProcurement staging tables into the Inventory tables.
Delete All	Deletes all pending data from the eProcurement staging table.

See Also

Validating and Processing Imported Items

Editing Imported Item Categories

Access the Edit Imported Item Categories page.

Note. These categories are created from the UN/SPSC codes downloaded from a Marketplace. Add an account to each new category. The account is the top level of the ChartFields (chart of accounts) used to create accounting entries in PeopleSoft. If the CUP file does not create any new item categories, this page does not appear.

See Also

Defining Procurement Options

Maintaining Imported Item Statuses

Use the Imported Item Status page to update information for items that are in staging tables. After making the updates, you can load them into PeopleSoft production tables. You can load an item again if its status is Processing Complete.

Access the Imported Item Status page.

Item Status

The current load status of the items in the staging tables. The drop-down list only displays a status if there are currently items in that status. Values include: Invalid Unit of Measure: Select to display all items with units of measure that are invalid in PeopleSoft eProcurement. Invalid or Missing Category: Select to display all items that do not have a valid item category. Invalid or Missing Supplier: Select to display all items that do not include a valid supplier and vendor. Item to be Updated: Select to display all items that have been previously loaded into PeopleSoft eProcurement and currently need to be updated with new item information. Price to be Updated: Select to display all items that have been previously loaded into PeopleSoft eProcurement and currently need to be updated with new pricing information. Ready to Build Items: Select to display all items that are ready to be loaded into the PeopleSoft Item Master tables. Items to be Inactivated: Select to delete items from the catalog. Processing Complete: Appears when the item has been entered successfully into the PeopleSoft production tables.

The actions on this page will display either A for add, or D for delete.

Loading Marketplace Items

Access the Load Item Catalog page.

Run Item Load Process	Select to run the Load Item Stage process (PO_ITMLOAD). If this option is not selected, only the first step in this process is completed. You can run this process separately using the Items Price List page. You can run this process separately to verify or change data in the PO Item staging tables.
Run Inbound Items Process	Select to run the Item Loader process (IN_ITMLOAD). This option is only available, if you select the Run Item Load Process check box. You can also run this process separately using the Item Loader page. You can run this process separately to verify or change data in the Item Loader staging tables.
Inventory Item	Select to indicate this item is also a PeopleSoft Inventory item. This means that you can source the item from Inventory.
Update Business Unit Price	Select to update business unit standard prices when an Item/Vendor UOM price record is loaded. This field is available only if Item Pricelist is selected in the Item Load Type field. If this is selected, all business units that match the SetID/item combination and that have the Business Unit Update Price check box selected on the BU Specific Attributes page will have the new price applied. Future effective-dated prices do not go into effect until you run the Price Update process on or after the effective date.
Update Standard Price	Select to update standard prices when an Item/Vendor UOM price record is loaded. This field is available only if Item Pricelist is selected in the Item Load Type field. Future effective-dated prices won't go into effect until you run the Price Update process on or after the effective date.
Index Items	Select to indicate that you want the system to include the item as part of the Verity indexing process.
Item Image Sub Folder	Enter a location where images for use with item catalogs should be stored.

Note. If errors occur during the Item Loader process, use the Data Definition Maintenance page to review them.

Correcting Inventory Item Load Errors

Access the Data Def Maint page.

Use this page to review and resolve problems with items.

See Also

Using the Error Handling Utility

Downloading Item Attachments

Any item downloaded could have an item image stored as an attachment. You can download these attachments from a Marketplace. The image of the item appears on the Search Catalog - Item Description page and the Requisition Summary - Item Description page.

To download item attachments from a Marketplace into PeopleSoft eProcurement:

1. Run the Export CUP Data process to create the attachment file from a CUP file.

   This file does not contain the actual attachments (item images), just the file names and extensions of each attachment. The actual attachments are downloaded in a separate step. This attachment file cross-references the names and extensions of each attachment to the corresponding item ID.

   Note. In order to create an attachment file from the Export CUP Data process, a product file must be created at the same time from the same CUP file.

2. Run the Import CUP File process to move the data in the attachment file into the eProcurement cross-reference table, PV_CP_ITM_XREF.

   Note. Other attachments—aside from images—can be downloaded from a Marketplace. Only attachments with a P (picture) type are loaded into the eProcurement cross-reference table, PV_CP_ITM_XREF, when the Import CUP File process runs. All other attachments are loaded into the PV_CP_ATTACH file for future use.

3. Define the location where the item attachments should be stored using:

   1. The File Location page, which defines the first part of the directory and extension of the attachments.

   2. The Load Marketplace Items process, which defines the subdirectory.

      For example, if the item attachments that you are downloading are GIF images, the File Locations page defines the file extension (GIF) and the file directory F:\User\Images\. If you enter MktPlc items in the Item Image Sub Directory field of the Load Marketplace Items page, the attachments with the extension GIF are stored in the directory: F:\User\Imagesl\MktPlc items.

4. Download the zipped file containing the item attachments from a Marketplace.

   Place these item attachments in the directory location defined in step 3.

See Also

Setting Up Attachments for Transactions

Using Price and Availability Check

During requisition entry, you can update the price of an item with the most current price in a Marketplace. Click the Check Price and Availability button on the Requisition Summary - Item Description page. If the supplier’s price in a Marketplace is the same as the price in the item tables, there is no change to the page. If the supplier’s price is different, a message appears which informs you that the price is changing to the supplier’s price. The Item Description page then displays the Marketplace price.

Use the Check Price and Availability function to also compare the supplier’s available quantity in a Marketplace to the requisition quantity. If the quantity requested exceeds the available quantity, a message appears which provides the opportunity for you to change the requisition quantity.

Note. The Check Price and Availability button only appears if this is a Marketplace item and the user has been assigned the eProcurement role action of PRICEANDAVAILCHECK.

See Creating Requisitions in PeopleSoft eProcurement.

Setting Up Integration Broker for Marketplace Transactions

This section provides an overview of the Integration Broker function for Marketplace transaction and discusses how to:

• Define the Marketplace node within Integration Broker.

• Identify connectors.

• Identify transactions used with the Marketplace Document Integration.

• Define relationships

• Define transaction modifiers.

• Use relationship transaction modifiers.

Transactional Integration between PeopleSoft eProcurement and a Marketplace

PeopleSoft integrates to a Marketplace to facilitate:

• Enabling companies to easily register with Marketplaces.

• Creating requisitions within eProcurement, while viewing catalogs in the Marketplace.

• Enabling suppliers to send Purchase Order Acknowledgements (POA).

• Enabling suppliers to send Advanced Shipment Notifications (ASN).

• Generating receipts when Advanced Shipment Receipts (ASR) are received.

• Enabling suppliers to send invoices to the company, if you are using PeopleSoft Payables.

• Creating vouchers for inbound invoices.

This diagram illustrates the flow of information from PeopleSoft, through the Integration Broker, and to the Marketplace:

PeopleSoft Transaction Integration in a Marketplace

Integration Broker Set Up for Document Integration

To utilize the purchase order acknowledgement, advanced shipment notification, and invoice transaction capabilities, the administrator need to configure the Integration Broker. These elements need to be set up:

• Node

• Transactions

• Relationships

Integration Broker works within the PeopleSoft system to send and receive information from external systems, such as the Marketplace. In this case, the job of the Integration Broker is to send and receive documents that come to/from the Marketplace. The purpose of the Integration Broker is to aid in the translation of the xCBL 3.0 documents used by the Marketplace into the PSXML format that the PeopleSoft system recognizes. Integration Broker accomplishes this translation by using a combination of nodes, relationships, and messages.

Pages Used to Set Up Integration Broker for Marketplace Transactions

Defining the Marketplace Node Within Integration Broker

Access the Node Definition page.

To create the Marketplace nodes, complete these tasks:

1. Select Add a New Value and enter the new node name.

2. Click the Add button.

3. Create a description to identify the purpose of the new node.

4. Select the Active Node check box, and enter:

   Field Name	Value
   Node Type	External
   Routing Type	Explicit
   Authentication Option	None

Identifying Connectors

Access the Connectors page.

If the outbound documents contain attachments, you need to use the MPC target connector.

To receive inbound documents from the Marketplace you must use the MPC listening connector.

A key part of the Connectors page is to create a Property ID for the PRIMARYURL, in which you enter the URL supplied by the Marketplace. This URL is used for the gateway to post transaction to the Marketplace gateway from PeopleSoft.

Note. Please contact the PeopleSoft Global Support Center (GSC) for detailed MPC installation instructions.

1. To set up connectors, enter:

   Field Name	Value
   Gateway ID	LOCAL
   Connector ID	HTTPTARGET
   Property ID	HEADER
   Property Name	Content-Type
   Value	Text/xml

2. Add a new property:

   Field Name	Value
   Property ID	HEADER
   Property Name	sendUncompressed
   Required	selected
   Value	Y

3. Add a new property:

   Field Name	Value
   Property ID	HTTPPROPERTY
   Property Name	Method
   Required	selected
   Value	POST

4. Add a new property:

   Field Name	Value
   Property ID	PRIMARYURL
   Property Name	URL
   Required	selected
   Value	(Enter in the URL used to do business with a Marketplace.)

Identifying Transactions used with the Marketplace Document Integration

Access the Transactions page.

Within the node, you need to identify all of the inbound and outbound transactions you will use with the PeopleSoft eProcurement integration with the Marketplace. You need to identify the message you wish to have associated with the transaction, and the version of that particular message.

You need to identify:

• For outbound registration transactions, identify transactions for the MP_REG_EMPTY,MP_PO_EMPTY, and MO_REG_REQ messages.

• For the outbound purchase order, identify the PV_ORDER message.

• For the outbound order status request (OSR), identify the PV_ORD_STS_REQ message.

• For the inbound advanced shipment notification (ASN), identify the ADVANCED_SHIPPING_RECEIPT message.

• For the inbound invoice, identify the EM_VOUCHER_IN message.

• For the purchase order acknowledgement (POA), identify the PURCHASE_ORDER_ACKNOWLEDGEMENT message

There are two additional messages you need to identify inbound transactions for: PV_MS_RESP_MSG and PV_MS_XCBL_POR.

Defining Relationships

Access the Relationships page.

Once you create the node for the Marketplace transactions, you need to create the relationships between that node, the transactions within the node, and the Marketplace. To complete this picture you define the node for the Marketplace transactions and the relationships that tell the PeopleSoft system how to translate (transformation AE program) the message to xCBL 3.0 format.

From the Relationship page, the first node you identify is the one used for the Marketplace. The second node name is the one used for the local database.

Defining Transaction Modifiers

Access the Relationship Transaction page.

You need to create relationships for each of these transactions:

Relationship Transaction Modifiers

Access the Relationship Transaction Modifiers page.

Use the Request field to inform the system what message to use to transform the Marketplace files.

Integrating PeopleSoft eProcurement Transactions with a Marketplace

This section provides an overview of transaction integration and discusses how to:

• Use the Marketplace Registration Wizard.

• Test the transactional Marketplace integration.

• Move from a test environment to the production environment.

• Prepare to use Marketplace catalog search.

• Receive a purchase order acknowledgement.

Understanding Transaction Integration

This overview discusses:

• Marketplace catalog search integration.

• Receipt of Purchase Order Acknowledgements from a Marketplace.

• Receipt of an Advanced Shipment Notification (ASN).

• Receipt of an Invoice.

Marketplace Catalog Search Integration

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

This diagram depicts an overview of Marketplace catalog search:

Marketplace Catalog Search Overview

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 fairly seamlessly.

2. Complete the set up in eProcurement by creating vendor profiles and vendor locations, and linking the properties of that vendor to the information that create a link to a Marketplace.

   Note. Upon completion of this set up, a link will be provided on the eProcurement requisition. Selecting this link directs the requester to the Marketplace site.

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

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

Receipt of Purchase Order Acknowledgements from a Marketplace

The purchase order acknowledgement (POA) is a collaboration between 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. From the Marketplace the suppliers can initiate a POA document.

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:

Purchase Order Acknowledgement with a Marketplace

Note. The POA is mapped to a line, not to a schedule within the Marketplace. Only one schedule is allowed within Marketplace POA integration.

Note. The Notes to Buyer from the Marketplace are not mapped into the PeopleSoft system.

There are two options for receiving a purchase order acknowledgement from the 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) 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 shipment notification (ASN) 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 ASNs from the Marketplace site.

2. Once submitted, Integration Broker transforms the message to the PeopleSoft outbound ASN message called the Advanced Shipment Receipt (ASR) in PeopleSoft.

3. The message populates the Receipt Load tables.

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

This diagram represents the flow of the ASN from the Marketplace:

Advanced Shipment Notification with a Marketplace

Receipt of an Invoice

When an integrated supplier creates and invoice and sends it to the Marketplace, or 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 vendor ID field using the Linked Supplier table. The vendor SetID and vendor ID are retrieved based upon this information.

Once the vendor 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 executed.

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:

Invoice Transactions with a Marketplace

Note. The Marketplace invoice integration is not supported if PeopleSoft eSettlements is active.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker, “Administering Basic Integrations”

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker, “Defining Message Channels and Messages”

Pages Used to Integrate PeopleSoft eProcurement Transactions with a Marketplace

Using the Marketplace Registration Wizard

Access Marketplace Registration Wizard page.

The wizard will guide you to enter this information prior to submitting the registration:

• Company information.

• Company Contacts.

• Gateway Information.

Enter the company information including the User ID and Password to use when logging onto the Marketplace.

Enter the Gateway production and test URL.

See Testing the Transactional Marketplace Integration, Moving From a Test Environment to the Production Environment.

Testing the Transactional Marketplace Integration

Access the Marketplace Test page.

Prior to using the production environment, you should elect to submit a test. This test verifies that PeopleSoft eProcurement is communicating with the Marketplace test environment by sending a predefined purchase order with a predefined test supplier. the purchase order will be a generic, non-configurable, purchase order. It will only be used to test the connectivity, it will not be fulfilled.

Moving From a Test Environment to the Production Environment

Once you have successfully tested the PeopleSoft test environment, the administrator performs these tasks to move the buyer setup data into the production database:

1. Login to data mover for source/test database.

2. Marketplace script upd304852_01.dmsto import relevant Marketplace definitions:

   • Marketplace buyer.

   • Marketplace registration information.

3. Login to data mover for target/production database.

4. Marketplace script upd304852_02.dmsto import relevant Marketplace definitions:

   • Marketplace buyer.

   • Marketplace registration information.

5. When you are ready for production, navigate to the Marketplace buyer page and change the URL to the Marketplace production URL.

   See Setting up Marketplace Buyers.

Preparing to Use Marketplace Catalog Search

Before you begin using Marketplace catalog search, you must create a link to the Marketplace. This link will appear on the requisition for users to access the supplier catalogs:

1. Create a generic vendor profile for the Marketplace that is then tied to a link supplier configuration. This combination is used to link to the Marketplace web site to the requisition.

2. Set up logins for each location and register each within the Marketplace.

3. Create a vendor profile for each supplier the company does business with.

4. Associate each vendor location with its individual linked supplier; this includes all vendor locations for the Marketplace vendor profile.

5. Create a node for each login ID that is passed from eProcurement to the Marketplace.

Setting up Vendor Profiles

Access the Vendor Profile page.

To enable the Marketplace integration you must complete these tasks:

1. Create a vendor profile for the Marketplace.

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

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

4. Create link supplier identifiers for each vendor location.

   See Setting Up Marketplace Suppliers.

See Maintaining Vendor Information.

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 aid in determining which catalogs requesters are capable of viewing upon login to the Marketplace.

See Understanding Catalog Security.

Receiving a Purchase Order Acknowledgement

Access the Define Static Maps page.

PeopleSoft is delivered with POA statuses mapped from the Marketplace header and line formats. If you add a new status in the Marketplace, you can add the mapping to the PeopleSoft status codes.

These are the POA header status mappings:

The POA line status mappings options are:

See Also

Mapping PeopleSoft Field Values to Supplier Field Values