You can extend the supplier portal integration with Oracle Platform as a Service (PaaS) to create other custom applications.
Learn About a Supplier Portal Solution
A manual procurement process introduces many inefficiencies, such as:
- 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, often requiring manual re-entry of order information.
- Both parties must communicate through phone calls and email, which can slow the process.
By creating a supplier portal by using JD Edwards EnterpriseOne with Oracle Content and Experience and Oracle Integration, these inefficiencies are mitigated. With this integration:
- Friction is removed and the process is simplified.
- The buyer receives orders faster.
- The supplier receives payment faster.
- Real time buyer/supplier collaboration is enabled.
- Buyer Supplier relationship improves.
- Process costs are reduced.
- Transaction accuracy is increased.
This solution provides background information to help design a supplier portal solution.
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 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.
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:
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 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 users mapped to roles in the process.
The table below lists the principal users for the processes in the supplier portal. Each user represents a particular job function in the process. You can extend the example to include multiple users for any job function, as necessary.
This is the user who initiates a purchase in JD Edwards.
|A/P Approver||This is the JD Edwards user who approves supplier invoices.|
This user is the supplier working for the company supplying the product to the buyer and is the principal user of the supplier portal website.