Setting Up Suppliers for Direct Connect

There are several tasks that need to be completed before a supplier is enabled for direct connect.

  1. Exchange contact information with the supplier.

  2. Execute contractual agreements that are required between the supplier and your organization.

  3. Set up the direct connect supplier as a PeopleSoft supplier.

    See Understanding Supplier Maintenance

Obtaining Authentication From the Supplier

These steps describe the setup for direct connect suppliers:

  1. The supplier creates an account for your organization.

  2. Your organization's administrator and the supplier establish an organization wide password (shared secret) that authenticates XML service operations from eProcurement.

  3. The supplier provides your organization with a URL, which is used when setting up the Supplier Information page.

Creating a Supplier Profile

If the supplier is not already one, you need to create it. These are the fields for use when creating a linked supplier definition:

  • Supplier SetID.

  • Supplier ID.

  • Supplier Location.

Note: Before you save an eProcurement requisition, you must first establish the supplier as a PeopleSoft supplier. After you establish the supplier as a supplier, the supplier ID is saved on the requisition line. When the requisition is converted to a purchase order, the supplier is listed as the supplier on the purchase order.

See Understanding Supplier Maintenance

Note: SameSite prevents the browser from sending the cookie along with cross-site requests. The main goal is mitigating the risk of cross-origin information leakage. It also provides some protection against cross-site request forgery attacks. Possible values for the flag are None, Lax or Strict. This is being implemented by all the browsers, but Google Chrome is the first to make SameSite attribute to Lax by default (if cookie is missing SameSite in its attribute, browser will treat it as being set to Lax). With SameSite-Lax, the cookie is only sent on Same-site requests or top-level navigation with a safe HTTP method. That is, it will not be sent with cross-domain POST requests or when loading the site in a cross-origin frame. This changed behavior by the browsers will be causing some repercussion in eProcurement punchout and punchback features.

PeopleSoft cookies are not included in the ePro vendor's POST back to PeopleSoft. Without cookies PS is unable to determine the user context and other relevant session information so PS throws the user out to the login page. To handle this scenario, changes are done in PeopleTools.

For eProcurement punchout and punchback features, configure Web Profiles by adding following Custom Property:

Property Name: Repost1, Validation Type: String, and Property Value: s/WEBLIB_PV_DC.PV_ISCRIPT_LIB.FieldFormula.IScript_DCCatcher,http://:

If https is being used, then use https. Hostname and port are to be replaced by proper Load Balancer values by customers.

For more information on configuring Web Profiles for SameSite requirements, see:

PeopleTools: Portal Technology

Page Name

Definition Name

Usage

Supplier Information- Summary Page

VNDR_ID1_SUM

Create new supplier profiles.

Note: The size of the image added in the supplier information page should not exceed 75 x 75 pixels.