Oracle Fusion - Supplier Portal Detailed View

Supplier Portal Cloud

1. Cloud Functional Workshop Supplier Portal

2. Purpose of Design Workshops Align People, Process and Technology: Build Requirements Blueprint/Future Vision Define Customer’s Oracle implementation Roadmap This will be achieved by… Following Modern best practices Business Flows supported in Oracle Cloud Applications Capturing Customer-specific Configurations /Master data through guided sessions Separate workshop sessions for each functional area will be conducted

3. Design Session Caveats Capturing Notes / Discussion Points A designated individual (or scribe) will be tasked with taking notes during each session He/she will take notes in the notes template The notes will be posted to Confluence/ Project collaboration site within 24 hours of the session

4. Design Session Caveats Parking Lot A “Parking Lot” will capture issues, which will later be transferred to the issue log if not resolved. The meeting facilitator will make sure that agreement is reached for each Parking Lot issue. These decision points will be documented by the scribe.

5. Design Session Caveats Please Limit Side Conversations Everyone’s time is valuable and we need to get the most out of the investment made in these Design sessions, so we ask the following: Please keep side conversations to a minimum. If you have a question or a point, please bring it up to the group so that it can be captured as part of the session as others may have the same concern.

6. Agenda Introductions Deliverables Understanding of Current Processes Oracle Business process overview Key Functionality Master Data Integrations Reporting Design Decisions Wrap Up / Q&A

7. Supplier Portal

8. Workshop Deliverables Updated Process Flows Gather Configurations information /Master Data Configuration Documents Configured Instance for conference room pilot testing Key Design Decisions

9. As-Is & To-be business process flows Get an understanding of high level existing processes How does the setup and communication with suppliers currently work in your environment? Review Supplier Portal functionality and processes Which of the functions will be used? Registration approval requirements? Special considerations for integration of various modules?

10. Key Functionality Procurement Offering Procurement Process Procure to Pay Process Supplier Portal Overview View Information Manage Profile Self-service Transactions

11. Cloud Procurement Offering Oracle Procurement Cloud solution helps cost saving through streamlined procure to pay process, sourcing, and contract management

12. Procurement Process Procure to Pay Analysis Sourcing

13. Procure to Pay Process

14. Supplier Portal Overview Web based supplier self-service Supplier profile self-management Supplier agreement collaboration Supplier change order management Electronic invoice presentment Supply Chain Collaboration

15. Web Based Supplier Self Service

16. Supplier Profile Self-Management

17. Supplier Change Order Management

18. Electronic Invoice Presentation

19. Supply Chain Collaboration

20. Design Decisions - Roles Which supplier user roles to default for new supplier side users? Supplier Accounts Receivable Specialist : Manages invoices and payments for the supplier company Supplier Customer Service Representative : Manages inbound purchase orders and communicates shipment activities for the supplier company Supplier Demand Planner : Manages supplier scheduling, supplier managed inventory and consigned inventory for the supplier company. Supplier Sales Representative : Manages agreements and deliverables for the supplier company. Supplier Self Service Administrator : Manages the profile information for the supplier company. Supplier Bidder : Sales representative from a potential supplier responsible for responding to requests for quote, requests for proposal, requests for information and reverse auctions.

21. Design Decisions – Supplier Profile Change Request

22. Other Touchpoints Initial Supplier Registration Process Was it discussed in initial procurement implementation? If initial discussion: Registration required fields Prospective vs. spend authorized Various Approval Workflows FBDI Contact load Manage Supplier News Content

23. Homework Decide which default roles will be used for new contacts (see earlier slide) Indicate which fields will require approval for supplier profile changes (see earlier slide) Define roll out plan

24. THANK YOU!