Learn About the Supplier Portal Integration

For many businesses, the procurement process involves manual coordination, data reentry, and communication over multiple channels that can be costly in both time and labor. A supplier portal built by integrating JD Edwards EnterpriseOne with Oracle Content and Experience and Oracle Integration automates many of the steps in the procurement process to provide an efficient, integrated process flow between you and your suppliers.

Does your procurement process rely on manual coordination and multiple communication channels?
  • Buyers must contact the provider to determine the status of a purchase order, often more than once

  • Buyers must manually update purchase order status with each change in status

  • Suppliers are often unaware of pending orders which creates delays

  • Suppliers submit invoices in different ways that often require manual re-entry of order information

  • Communicating through phone calls and email can slow the process

Use the resources provided with this fully-functional integration example as a starting point to provide your own solution.

Before You Begin

To use the supplier portal solution, you must first:

  1. Make sure that you have access to the required services.

  2. Make sure that you understand the users and roles for the process participants.

  3. Make sure that the integration between JD Edwards and Oracle Content and Experience is set up and that the supplier portal templates, orchestrations, and processes are set up as described in the companion integration solution Create a supplier portal with JD Edwards and Oracle Content and Experience.

    The integration solution helps you install, create, and configure the components of the supplier portal including:

    1. Orchestrations and versions to automate tasks within JD Edwards EnterpriseOne
    2. The application and connections that are used by Oracle Integration Process
    3. The folder hierarchy used in Oracle Content and Experience.
    4. The access permissions and metadata that are associated with the folders, including buyer and supplier email addresses
    5. The supplier portal website template and site

Architecture of a Supplier Portal Created by Integrating JD Edwards with Oracle Content and Experience

This image shows the integration architecture between JD Edwards EnterpriseOne, Oracle Integration, and Oracle Content and Experience for creating a supplier portal that automates many of the steps in the purchase order fulfillment process.

Description of jde-supplier-portal-architecture.png follows
Description of the illustration jde-supplier-portal-architecture.png

The buyer initiates the process by generating a purchase order. Document exchange between the Orchestrator in JD Edwards and Oracle Content and Experience is supported directly in the integration.

Data exchange between JD Edwards and Oracle Content and Experience for dynamic data such as Status, Metadata, and Invoice/Voucher Approval is managed together by Orchestrator in JD Edwards and by processes in Oracle Integration.

Notifications between the buyer and the supplier are handled by processes in Oracle Integration.

About Required Services for the Supplier Portal

The supplier portal solution uses the integration features of the following cloud services to automate many of the steps in the procurement process to provide a coherent process flow for both the buyer and the supplier.

Service Description

JD Edwards EnterpriseOne

By using the processes created with JD Edwards Orchestrator, the supplier portal solution augments the JD Edwards order management system. It allows you to:
  • Route purchase orders and receipts to Oracle Content and Experience
  • Receive process messages from Oracle Integration to update purchase order status and to create supplier invoices
  • Provide notifications to approvers
The supplier portal solution requires JD Edwards Tools release 9.2.2.

Oracle Content and Experience

Oracle Content and Experience allows you to automate content exchange. In a supplier portal, it provides designated folders that serve as the repository for purchase orders, invoices and receipts for each supplier. Suppliers sign in to a website to get real-time access to the documents based on their status and to perform their tasks in the procurement process.

Oracle Integration

Oracle Integration includes Process functionality that coordinate the actions between order management, the document repository, and the web portal.

See Learn how to get Oracle Cloud services for Oracle Solutions to get the cloud services you need.

About Users and Roles for the Supplier Portal

The supplier portal is designed around a standard set of personas that you map to users and roles in the process.

The personas listed below are an example of the minimum set of users for the processes in the supplier portal. You must map these personas to the roles in the services and give them access rights to the resources. Each persona represents a particular job function in the process, for example, the supplier. You can extend the example to include multiple users for any job function as necessary.

Persona Description

JD Edwards Integration User

When you create the integration between JD Edwards and Oracle Content and Experience, you specify a user to act as the principal integration user. The integration user is the overall process and folder owner and can set permissions on resources for other users.

Robin Marlow

Robin is an administrator for Oracle Integration Process and for Oracle Content and Experience. Robin manages the processes and folders and can set permissions on resources for other users. In this example, Robin is also the accounts payable representative.

Larry Miller

Larry creates the purchase order in JD Edwards.

Morgan Zu

Morgan is the procurement manager in JD Edwards.

Joshua Baker

Joshua is the supplier working for Dakota Farms and is the principal user of the supplier portal website.

To coordinate the users and roles between services:
  • Oracle Cloud: You must create an account for each of the named personas in Oracle Cloud. Although you set up cloud users and JD Edwards users separately, the user IDs must match.

  • JD Edwards: You must create users for the JD Edwards integration user and for the buyer (Larry Miller). Although you set up cloud users and JD Edwards users separately, the user IDs must match.

    In addition, you must set up a user connection between JD Edwards and Oracle Content and Experience. The connection consists of a connection template that includes user and password information and a connection record that references the template.

  • Oracle Content and Experience: You must provision all users of the supplier portal with a process role as standard users in Oracle Content and Experience to have access to the folders that contain the purchase orders, invoices, and receipts. Depending on the process role and the associated folder role, the user may be able to add content to the folder or conversation or just access the content.