<Product Name> <TOI Functional> - 1

<Product Name> <TOI Functional> - 1
R12 Procurement <Product Name> <TOI Functional> - 1

Agenda What is new in R12 Purchasing and iProcurement
Intro to Sourcing, Procurement Contracts, iSupplier Portal Q&A

iProcurement R12 enhancements
Enhanced catalog authoring Difference summary for catalog changes Unified catalog Approval, revision control and archive for catalog data Content security – content zones Advanced approval support - OAM Position hierarchy based approvals Parallel approvals Support for FYI notifications Graphical display of approval chain Enhanced requester driven change order management Requester directed sourcing Multiple search result layouts – updated paragraph or grid display Next, let’s move on to financial operations. In General Ledger, a couple of key points to highlight: the first is XBRL support. XBRL, the extensible business reporting language, allows for XML publication of financial statements and reports. So you are able to communicate in an industry standard open format (XML), your financial results through the Financial Statement Generator. In addition, we’ve integrated that with XML Publisher, which provides the capability to publish the the Financial Statement Generator (FSG) reports, in PDF output or Microsoft Word output. Next, General Ledger also added the Interface Data Transformer, giving added flexibility to transform data, which is coming from disparate systems and feeding into your General Ledger to do things like chart of account mapping from disparate systems or from subsidiaries into your base GL. In addition, across core Financials applications a much-improved UI. In the case of General Ledger, improved transaction entry around journals and management around drilldowns. <Product Name> <TOI Functional> - 3

Procurement R12 enhancements
Professional Buyers Work Center Procurement for Complex Services Multi Org Access Control (MOAC) E Business Tax Document Publishing Enhancements Communicate document attachments to suppliers OSN – rapid supplier enablement Maintain sourcing rules / ASL form agreement items Support for contractor purchasing users Compliance to packaging conditions Auto approval tolerances for change orders Model complex pricing for blanket line items Advanced approval support for requisitions New user interface for purchasing setups Next, let’s move on to financial operations. In General Ledger, a couple of key points to highlight: the first is XBRL support. XBRL, the extensible business reporting language, allows for XML publication of financial statements and reports. So you are able to communicate in an industry standard open format (XML), your financial results through the Financial Statement Generator. In addition, we’ve integrated that with XML Publisher, which provides the capability to publish the the Financial Statement Generator (FSG) reports, in PDF output or Microsoft Word output. Next, General Ledger also added the Interface Data Transformer, giving added flexibility to transform data, which is coming from disparate systems and feeding into your General Ledger to do things like chart of account mapping from disparate systems or from subsidiaries into your base GL. In addition, across core Financials applications a much-improved UI. In the case of General Ledger, improved transaction entry around journals and management around drilldowns. <Product Name> <TOI Functional> - 4

Enhanced Catalog Agreement Management Description
Catalog Authoring Capability for Buyers, Suppliers and Catalog Administrators Online Authoring and File Upload from Buyer Work Center, iSupplier and iProcurement Catalog Administration Responsibilities Industry standard formats for upload mode including OAG XML, cXML, CIF and text files, with improved error review process Difference Summary for Catalog Changes Display changes between the revised vision and the last approved version. Visual indication for added, changed and delete lines Approval, Revision Control and Archive Buyer can review difference summary during approval Buyer’s acceptance with line level disposition for all changes or only for those that exceed price tolerance. Purchasing Approval Hierarchy, Revision Control and Archival capabilities are added to catalog content Real-time catalog update Extractor will be obsoleted. <Product Name> <TOI Functional> - 5

Enhanced Catalog Agreement Management Overview
Sourcing Professional Award PBWC Buyer Bulkload / Online author PO Buyer External Supplier Sites iP Admin Catalog Admin Approve Catalog iSP Supplier iP Requester Definitions: Buyer - Purchasing user Supplier - Supplies goods or services to the buying organization Catalog Administrator - Performs catalog related activities within the buying organization <Product Name> <TOI Functional> - 6

Enhanced Catalog Agreement Management Benefits
Improve Catalog Management Reduce the buying organization overhead in catalog management Buyers can delegate catalog management to suppliers and catalog administrators Online catalog authoring for quicker catalog update Difference Summary to highlight the changes Version control of catalog data Streamline catalog creation and management Catalog perpetually up-to-date and based on real-time data <Product Name> <TOI Functional> - 7

Content Security Enhancements Description
Control What Catalog Content To Show Catalog Administrators can partition local catalog content into Local Content Zones based on items’ Supplier, Supplier Site, Item Category and Browsing Category information. Support for inclusion and exclusion rules. Ability to include Inventory items. Once defined, Content Zones may be made accessible to users of specific Responsibilities or Operating Units. Content Zones may be assigned to multiple Stores. Stores may contain multiple Content Zones. <Product Name> <TOI Functional> - 8

Content Security Enhancements Partition Content
Release 12 Release 12 Content Zones Replace Catalogs. All Content Zones Support Operating Unit or Responsibility Security. <Product Name> <TOI Functional> - 9

iProcurement – Content Security What’s New?
Example: Local Content Inclusion Rule The rules: Include items from supplier X Include items from category C Correspond to the red block of available content. Supplier Supplier X Supplier Y .... … Category Category A Category B Category C <Product Name> <TOI Functional> - 10

Example: Local Content Exclusion and Inclusion Rules The rules: Exclude Supplier X Include Category A Include Category C Results in red blocks of available content. Exclusion is useful when we need to exclude a single Supplier (e.g., X) from many others (e.g., A-Z). Supplier Supplier X Supplier Y .... … Category Category A Category B Category C <Product Name> <TOI Functional> - 11

Let’s Look at how category rules are defined: Include specific categories Include specific suppliers Make content accessible to specific user groups <Product Name> <TOI Functional> - 12

Example: Include Specific Categories (local content): Create Category Specific Stores (e.g., Legal Forms and Services) by creating one or more category specific Content Zones Include content for some users (e.g., Buyers) that should not be available to the general public (e.g., Novice Requesters). <Product Name> <TOI Functional> - 13

Let’s Look at how supplier rules are defined: Include specific categories Include specific suppliers Make content accessible to specific user groups <Product Name> <TOI Functional> - 14

Example: Include Specific Suppliers (local content): Include items on GBPA, BPA, Quotation, Requisition Templates from specific suppliers. Segregate Inventory and Externally Sourced content into separate Stores by creating multiple Content Zones with different inclusion settings. <Product Name> <TOI Functional> - 15

Once content rules have been completed, the Content Zone may be assigned to all, or some, users: Include specific categories Include specific suppliers Make content accessible to specific user groups <Product Name> <TOI Functional> - 16

Assign Content Zone to specific Responsibilities, Operating Units, or all Users.

Content Security Enhancements Benefits
Increase Security Inclusion and Exclusion rules provide more control over content. Responsibility and Operating Unit assignments enable specific user sets to access specific catalog content. Improve Usability Single feature-set replaces and enhances functionalities previously provided by Realms, System Profiles, Catalogs, and Extractor. <Product Name> <TOI Functional> - 18

Requester Driven Change Order Mgmt
Change Order Approval and Routing Based on Tolerances Requester’s and Supplier’s changes are routed to the requester’s approval hierarchy PO changes are routed to to buyer for approval Bypass approval for changes within tolerances <Product Name> <TOI Functional> - 19

Requester Driven Change Order Mgmt Benefits
Enhanced Requester Driven Change Order Management Streamlines the Change Order Process Tolerances to indicate when a requester initiated change should be routed to the requester hierarchy for approval Tolerances and options to determine the need for buyer’s approval Auto-approval for minor changes Flexible Tolerances Simple user interface for managing tolerances instead of using workflow attributes Minimum/Maximum increment by amount or percentage Multiple attributes: document amount, unit price, line amount, need by date, promise date <Product Name> <TOI Functional> - 20

Usability Enhancements
Search & Browse within Stores Paragraph and Grid Layouts Grid Format – allows requesters to differentiate between similar items effectively. Item Details and Comparison Page Layout Enhanced Create and maintain multiple Favorites Lists. List of Values (LOVs) capability are enhanced. Provides users with tools to find the values they are looking for easily and effectively Enhancements include: Sorting Capability Expanded Search Criteria <Product Name> <TOI Functional> - 21

Usability Enhancements Paragraph Search Skin
2 column layout ensures sufficient spacing with item image Images may be hidden. When they are hidden, three columns of descriptors appear Price, UOM and action buttons appear on last rows of each item description This is the paragraph search skin and should be familiar to users of iProcurement and In Release 12, we have enhanced the paragraph search skin in the following ways: Long descriptions are truncated after 180 bytes Descriptor names and values are vertically aligned to provide better readability. They continue to be compliant with ADA standards Price, UOM, and action buttons appear on last two rows of each item’s section. <Product Name> <TOI Functional> - 22

Usability Enhancements Paragraph Search Skin
3 columns format allows more information to be displayed When images are not displayed, the three column layout is used. The 3-column paragraph layout allows more information to be displayed on each row of item descriptors. <Product Name> <TOI Functional> - 23

Usability Enhancements Search Skins – Grid Format
In Release and prior, search results in iProcurement were displayed in a grid format. There is a desire from some users in the customer community to bring this style of presenting search results back, and in Release 12, we have done so. In the chemical industry, for instance, chemicals of identical make up but different concentrations may be distinguished from one another more quickly in a grid format. Since item images are not displayed in the grid search skin, this format also allows a higher density of information to be presented. Each requester can save his search skin preference. The grid format allows users to differentiate between similar items more effectively. <Product Name> <TOI Functional> - 24

Usability Enhancements
Advanced Approvals Enhancements Parallel Approvals Notifications are sent out to multiple people simultaneously to speed up the approval process Support for Viewers FYI notification, approval is not needed Position Hierarchy Support Graphical Approval Path UI Display <Product Name> <TOI Functional> - 25

Advanced Approvals Enhancements Example – Approval List
Takes you to add approver/viewer, delete approvers Parallel Approval A requisition for furniture totaling $4,500 is created. The req will need to be approved by the position hierarchy chain and the Facilities Management Group. <Product Name> <TOI Functional> - 26

Advanced Approvals Enhancements Example – Add Viewers
Option to add Viewers to the Approval List <Product Name> <TOI Functional> - 27

Advanced Approvals Enhancements Example – Add Viewers
<Product Name> <TOI Functional> - 28

Usability Enhancements Benefits
Increase Flexibility Users can specify their search results layout preference: Paragraph or Grid Users can maintain and manage multiple favorites lists Users have more options when searching using List of Values (LOVs) Improve Ease of Use Updated user interface provides requesters with more intuitive and user-friendly layout Allows users to identify desired information quickly <Product Name> <TOI Functional> - 29

Usability Enhancements Benefits
Speed up Approvals Process While Still Maintaining Oversight Requisition can be routed to multiple approvers simultaneously Increase Flexibility for Setting up Approval Routes Voting Regime allows enterprises the flexibility in defining approval rules Reduce Setup Efforts Approval rules can be defined once and be leveraged across multiple products, requiring less maintenance work Provide Intuitive Graphical View of Approval List Graphical View for Approval List provides users with quick view of the approval list and status <Product Name> <TOI Functional> - 30

Oracle Purchasing – Delta Summary
Professional Buyer’s Work Center Enhanced Catalog Access Document Styles Multi-Org Access Control Document Publishing Enhancements Communicate Document Attachments to Suppliers Maintain Sourcing Rules/ASLs for Agreement Items Complex Services Procurement Support for Contract Purchasing Users Supplier Packaging Constraints E-Business Tax Model Complex Pricing for Blanket Line Items Mass Re-pricing of Purchasing Documents Auto-Approval Tolerances for Change Orders <Product Name> <TOI Functional> - 31

Professional Buyer’s Work Center Feature Description
Requisitions View and Process Requisitions into Orders or Sourcing Events Orders Create and Manage Purchase Orders Agreements Create and Manage Blanket and Contract Purchase Agreements Deliverables Manage Procurement Contract Deliverables Negotiations Access Oracle Sourcing Suppliers Create and Manage Supply Base <Product Name> <TOI Functional> - 32

Professional Buyer’s Work Center Implementation Considerations
Requisition Management – Profile Options PO: Document Builder Default Document Type The document type that is defaulted into the document builder region. Profile Value Description Add to PO Add to an existing Purchase Order New Auction Create a new Sourcing Auction New PO Create a new Purchase Order New RFQ Create a new Sourcing RFQ PO: Default Requisition Grouping The default for grouping requisition lines onto a Sourcing RFQ/Auction or PO. Profile Value Description Default Group requisition lines using the default grouping. One or more requisition lines can associated with one purchase order line. Requisition Group requisition lines using requisition grouping. One requisition line can be associated with one purchase order line. <Product Name> <TOI Functional> - 34

Professional Buyer’s Work Center Customization and Extensibility Options Customers can create custom views using personalization feature in all inquiry pages. <Product Name> <TOI Functional> - 35

Professional Buyer’s Work Center Benefits
Increases Productivity Central Place for Buyers to Perform Day-to-Day Tasks Optimized for Shared Service Centers Streamlined Interface Increases Efficiency Pre-Seeded or Custom Views for quicker access to information and prioritize tasks Designed for Procurement Professionals, the PBWC Combines Ease-of-Use with Power Capabilities to Track, Manage and Control all Strategic and Tactical Activities. There are several advantages to using the buyer’s work center. First, purchasing departments that operate as shared service centers can take advantage of accessing documents across the multiple operating units that they service without having to switch responsibilities. In addition, the web-based interface of the work center is designed to enable buyers to perform their tasks easily and quickly. One of the ways that this is achieved is by reducing the number of drilldowns buyers need to access to create purchasing documents. Another benefit of the new interface is that the work center helps buyers prioritize their tasks through the use of views. Oracle Purchasing provides several pre-seeded views, such as the ability to view all documents that are incomplete or all schedules that are past due. However, buyers can also create their own views based on their particular responsibilities. <Product Name> <TOI Functional> - 36

Enhanced Catalog Access Feature Description
iProcurement like Search Capabilities for Purchasing Users Add Catalog Items to Purchase Orders and Agreements Replace non-catalog requests with lines from the catalog Release 12.0 of Oracle Purchasing builds on the popularity of Oracle iProcurement’s search capabilities by offering professional buyers a similar search interface to easily find the items they need to procure. From the Demand Workbench, buyers can access the catalog and favorites to find negotiated alternatives to non-catalog requests. While authoring orders and agreements, buyers can use the catalog or favorites to quickly add items, thereby accelerating the document creation process. <Product Name> <TOI Functional> - 37

Document Styles Feature Description
Assign Display Names to Document Types Enable/Disable Features Access the document style page from the Navigator: Setup > Purchasing > Document Styles. Display names should be specified for each of the document types for whish the style is enabled. The same purchasing document type (e.g. Standard Purchase Order) can assume different names based on the style applied. In the example here, for a style intended for authoring agreements and orders to acquire facilities related services, the name assigned to Standard Purchase Orders using this style is ‘Facilities Maintenance Order’ and the name assigned to Blanket Purchase Agreements using this style is ‘Facilities Maintenance Contract’. These names are exposed throughout the WorkCenter and also to the supplier. Next, features supported by style should be enabled. In this example, ‘Facilities Maintenance Purchase’ style only supports Services and Temp Labor purchases. The attributes and regions associated with goods purchases will not be displayed on the purchase order creation pages for this style. The supported line types on the purchase document are based on the type of purchases enabled for the style. You can either restrict the available line types or support all line types associated with the purchase bases. For the pricing features, you can specify whether Price Breaks should be enabled for Blanket Purchase Agreements and also Price Differentials for Temp Labor purchases. <Product Name> <TOI Functional> - 38

Document Styles Implementation Considerations
Document Styles is a new concept in Release 12. It is a configuration tool that reduces the complexity of the application by allowing procurement managers to control the available functionality and the display of PO documents. A document style is mandatory on a PO document. The style setting controls the document display on the HTML UI for document creation, update, and viewing of individual document, as well as the allowable values during the document creation and update. A style can only be applied at the start of document creation. It cannot be replaced with another style or removed from a document. Standard Style: This will be the only seeded style and will be used for upgrade of the documents created prior to R12. Non-standard style: Any new styles created in R12 are considered non-standard. Purchasing documents with these styles can only be created and processed through the Work Center. <Product Name> <TOI Functional> - 39

Multi-Org Access Control Feature Description
OLD PROCESS Application Responsibility A Application Responsibility B Application Responsibility C Operating unit X Operating unit Y Operating unit Z NEW PROCESS Application Responsibility A In the old process, each application responsibility could access only one operating unit. In the new process, each application responsibility can access multiple operating units. The Multi-Org Access Control feature, also known as "Security by Operating Unit", will enable users to access to secured data in one or more Operating Units within one responsibility. The feature uses Security Profile concept introduced in Release 11i Oracle Human Resources Management System, which allows system administrator to predefine the scope of access privilege as a profile option. A security profile may be defined in hierarchical or listing mode, which may consist one or more Operating Units. Operating unit X Operating unit Y Operating unit Z <Product Name> <TOI Functional> - 40

Multi-Org Access Control Implementation Considerations
New Profile Options Entire Purchasing functionality requires the Multi Org Access Control (MOAC) setups to be configured correctly. The following new profile options need to be set for MOAC MO: Security Profile - the group of operating units that can be accessed in HTML Orders MO: Default Operating Unit - the default OU that should be used when creating new POs. If customer is not leveraging MOAC, they can continue to use R11i profile option ‘MO: Operating Unit’. Select Human resources responsibility to create the security profile (Security -> Global Security Profile (Function PERWSSCP-GLOBAL) <Product Name> <TOI Functional> - 41

Document Printing Enhancements Feature Description
Purchasing Layout PO Output New in Release 12.0 Purchasing XML New in Release 12.0 Purchasing Layout Oracle Procurement Contracts supported XSL-FO stylesheet based layout templates in release 11i.10. Enhancing the printing solution further, the application now enables customers to use layout templates created in Microsoft RTF and Adobe PDF formats. Designing and configuring layouts in these formats is extremely simple and straightforward. PO Output in Multiple Formats Purchasing XML Release 12 <Product Name> <TOI Functional> - 42

Communicate Document Attachments to Suppliers
Attachment Type 11i10 and Before r12 Notes to Supplier Long/Short Text Files (e.g. MS Word, Drawings) URLs As you can see, prior to release 12, only a small subset of the available attachment types were communicated to the supplier. In release 12, there are no limitations to the types of attachments that can be sent to the supplier. <Product Name> <TOI Functional> - 43

Maintain Sourcing Rules/ASLs for Agreement Items
New Concurrent Program Introduced Designate agreement usage in Specific Regions or Plants Extend rule effectivity after renewing Blanket Agreements Maintain rules for all Operating Units enabled to buy off an Agreement Then, we need to launch the concurrent request for each of the blanket agreements. The name of the concurrent request is ‘Generate Sourcing Rules and ASLs from Blanket Agreements’ and can be launched from the Requests link in the main menu. The slide on the left shows the parameters for the San Diego plant, while the slide on the right shows the parameters for the Boston plant. Notice that when the concurrent program is launched for Advanced Network Devices (the west coast supplier), the sourcing level is set to Item-Organization and the inventory organization is set to San Diego Manufacturing. If the sourcing level were set to ‘Item’, global rules would have been created. When the concurrent program is run for Prouty Industrial Supply (the east coast supplier), the sourcing level is again set to Item-Organization, but the inventory organization is set to Boston Manufacturing. The sourcing rules for both plants should be assigned to the same Assignment Set, Supplier Scheduling. <Product Name> <TOI Functional> - 44

Support for Contractor Purchasing Users Feature Description
Allow Contingent Workers to Participate in Purchasing Activities Raise and Approve Requisitions Create, Maintain, and Approve Purchase Orders Receive Goods and Services New Profile Option HR: Expand Role of Contingent Worker In this release, contingent workers will be able to perform the same actions as requesters and buyers who are employees. These actions include creating requisitions, purchase orders, and receipts. In addition, contingent workers will be able to approve both requisitions and purchase orders. Profile Value Description Yes Allow Contingent Workers to Create and Approve Purchasing Documents No Do Not Allow Contingent Workers to Create and Approve Purchasing Documents <Product Name> <TOI Functional> - 45

Compliance to Packaging Constraints
1. Min-max creates Replenishment Request for 116 Eaches New Process Inventory 2. Apply Constraints Order Modifier UOM Conversion Rounding New Quantity = 10 New UOM=Cases of 12 Min-Max 3. PO placed for 10 cases of 12 REQIMPORT Purchasing Oracle Purchasing can now automatically apply supplier-specific order modifiers (fixed lot multiple and minimum order quantity) and UOM to replenishment requests that originate in Inventory planning processes. As per the new process, supplier packaging constraints are setup and stored. This is then used to modify replenishment requests originating from Inventory planning processes. Taking the example from the previous slide, the request from Inventory for 116 eaches is modified during ReqImport as follows: The quantity is below the minimum order quantity which is 10 Cases of 12, I.e., 120. Therefore the quantity is increased to 120. Supplier UOM is cases of 12. Therefore the quantity and UOM are changed to 10 Cases of 12. This leads to the creation of a purchase order for 10 Cases of 12 which is now fully compliant with supplier packaging constraints. 4. PO complies to Supplier packaging constraints PURCHASE ORDER SUPPLIERS <Product Name> <TOI Functional> - 46

E-Business Tax Integration Feature Description
Prior to E-Business Tax Basic tax setup – tax codes and tax groups With E-Business Tax Comprehensive solution addressing complex tax requirements Fragmented tax solution across E-Business Suite modules Multiple tax engines Duplicate tax setup Fragmented data storage Duplicate 3rd party integration Single point tax solution across E-Business Suite Single interface: tax setup and 3rd party integration Uniform services Single repository Oracle E-Business Tax will significantly enhance the tax solution within the Procure to Pay business flow. Previously, only basic tax code and tax group based tax computation capabilities were supported. By integrating with Oracle E-Business Tax, the Procure to Pay business flow will be able to address complex tax requirements. Another benefit of the integration is the ability to utilize a single point tax solution across the E-Business Suite, which greatly simplifies maintenance and tax management. Note: Please refer to the e Business Tax TOI for more information on this feature <Product Name> <TOI Functional> - 47

Model Complex Pricing for Blanket Line Items
Agreement Pricing Transactions Line Price Pricing Engine Price Break Custom API Requisitions Price List Leverage Oracle Advanced Pricing to model Complex Pricing Scenarios Formula Modifiers Leverage Oracle Advanced Pricings’ powerful Pricing Engine price lists, modifiers, and formulas to price transactions referencing BlanketAgreements. Orders Oracle Advanced Pricing Benefits Bring Agreements with Complex Pricing Requirements Online Accurate Pricing of Transactions without the need for Manual Overrides Decrease Supplier over billing Save Cost by ensuring all available discounts are applied <Product Name> <TOI Functional> - 48

Mass Re-pricing of Purchasing Documents Feature Description
Orders Blanket Purchase Agreement Extends Mass Re-Pricing Support beyond transactions priced from Agreements Concurrent Program now capable of re-pricing transactions priced from: Oracle Advanced Pricing Price Lists/Modifiers Custom Pricing APIs Advanced Pricing Price Lists, Modifiers Revise Pricing Data New in Release 12.0 Custom Pricing API <Product Name> <TOI Functional> - 49

Auto-Approval Tolerances for Change Orders
Eliminates need for Workflow Customizations Set tolerances by document type 1st Click: In Release 12, Oracle Purchasing introduces a new HTML User Interface for business users to setup tolerances for auto-approval of Change Orders. Previously setup of these tolerances would have required customization of the PO Approval Workflow in the form of setting new values or changing old values of workflow attributes, a task that typically requires assistance from IT. The new UI effectively eliminates the need for IT’s involvement in rollout of new policy or change to existing policy as it pertains to change order approvals. 2nd Click: The UI will also allow setting up tolerances independently by document types. For businesses to maintain separate tolerances by document types would have meant maintaining separate approval workflows by document type. Therefore customers would no longer need to maintain separate approval workflows per document type just for the sake of following separate tolerance controls by document types. 3rd Click: The new UI also exposes quite a few new attributes compared to the tolerance control attributes available within the approval workflow definition. Customers would now be able to implement more granular tolerance control by leveraging these new attributes. Please note that tolerance values setup for attributes in this page will take precedence over those corresponding attributes within the workflow definition. Please also noteUptake of this feature is optional. In the absence of any values setup in this page, application will still honor tolerance configuration as defined in the workflow. Navigation: Purchasing Responsibility : Setup: Tolerances and Routing: Change Order New tolerance attributes introduced <Product Name> <TOI Functional> - 50

Advanced Approvals Support for Requisitions Description
Parallel Approvals Notifications are sent out to multiple people simultaneously to speed up the approval process Position Hierarchy Support Here are the list of enhancements for the Approvals Management in R12. Parallel Approvals Support for Viewers Position Hierarchy Support <Product Name> <TOI Functional> - 51

Advanced Approvals Support for Requisitions Parallel Approvals
In , approvers for a given requisition are notified sequentially To satisfy regulatory requirements (e.g. Sarbanes-Oxley Act), organizations may need to involve more approvers With parallel approvals, several approvers can be simultaneously notified for a given requisition, thus speeding up the requisition approval process Parallel approvals can be setup within an approval group or for individuals Speaker Notes: Why introduce Parallel Approvals? To comply with the Sarbanes Oxley Regulation requirements, organizations may need more approvers in requisition approvals. This will help to speed up the approval process since the approval list may now be larger. <Product Name> <TOI Functional> - 52

Advanced Approvals Support for Requisitions Voting Method
A Voting Method is a way of sequencing the approvers within an approval group/chain of authority Types of voting methods Consensus All approvers must respond. Approvers will receive notifications in parallel First Responder Wins Approvers will receive notifications in parallel, but only the action of the first approver to respond will be recorded Speaker Notes: As sometimes it is necessary both to seek approvals in parallel and also to choose how that group asserts an approval, AME makes it possible to define approval rules so that: Any single person can approve on behalf of an approval group (First responder wins) All approvers within an approval group must approve the requisition even when the group is being notified in parallel (Consensus) Multiple approval groups should also be able to be notified in parallel, each with their own order number with each contributing to the final approval process The voting method can also be setup for chain of authorities. A chain of authority is a set of approvers returned based on position hierarchy/employee-supervisory rules. <Product Name> <TOI Functional> - 53

Advanced Approvals Support for Requisitions Position Hierarchy Support
In addition to the Employee/Supervisor Hierarchy support, the integration with Oracle Approval Management (AME) also supports Position Hierarchy Approval routing structures using positions and position hierarchies remain stable, even if individual employees leave their organization, or transfer within it Speaker Notes: Human Resources typically use positions and position hierarchies to define management line reporting. Positions and position hierarchies allow customers to define approval routing structures that remain stable regardless of how frequently individual employees leave their organization or relocate within it. Also, position hierarchies offer increased flexibility and allow customers to define separate hierarchies for procuring various commodities. The rules can be based on individual positions or specified hierarchy within an organization Position Hierarchies represent how many levels AME should climb in the given position hierarchy from a given starting point position to complete the approver list. The positions are always relative to a HR Position in question and are calculated at run-time. <Product Name> <TOI Functional> - 54

Advanced Approvals Support Example
Business Rules: If requisition < $5,000, then requires approvals up to first two positions up based on position hierarchy If the item’s category is [IT.EQUIPMENT] then require approval from IT Approval Group IT Approval Group is in parallel to position hierarchy approval chain Speaker Notes: As an example, an organization, has the following Business Rules in place for Requisition Approvals. If requisition < $5,000, then requires approvals up to first two positions up based on position hierarchy If the item’s category is [IT.EQUIPMENT] then require approval from IT Approval Group IT Approval Group is in parallel to position hierarchy approval chain <Product Name> <TOI Functional> - 55

Advanced Approvals Support Example – Approval List
Approval Group returned in Approval List since Item Category is [IT.EQUIPMENT] Since req total is between 0 and 5000, the first 2 positions up (based on the Position Hierarchy Rule) is generated Speaker Notes: Since the req total < 5000, it requires approvals up to first 2 position up, the 2 following 2 positions are returned. Tom Gallant & Maria Menudo are returned based on the position hierarchy defined in Oracle HRMS. In this case, Tom Gallant is 1 position up from the requester, and Maria Menudo 2. The item category for the req line is [IT.EQUIPMENT]. This triggered the rule where approvals from the IT Approval Group is required. An Approval Group is indicated with a group icon A requisition for computers totaling $4,500 is created. The req will need to be approved by the position hierarchy chain and the IT Approval Group. <Product Name> <TOI Functional> - 56

Advanced Approvals Support Example – Approval List
Takes you to add approver/viewer, delete approvers Parallel Approval Speaker Notes: Because the order number is the same for both HR Position Levels and Approver-Group Chain of Authority, they are returned as parallel approvers in the Approval List. By drilling down on the Manage Approvals button, requesters can modify/reset the approval list. A requisition for computers totaling $4,500 is created. The req will need to be approved by the position hierarchy chain and the IT Approval Group. <Product Name> <TOI Functional> - 57

Advanced Approvals Support Example – Add Viewers
Option to add Viewers to the Approval List Speaker Notes: On the Manage Approvals page, the requester can: Insert an ad-hoc Approver Insert a Viewer Change Managerial Approval (Known as Change First Approver in ) Delete an Approver/Viewer Reset the Approval List The option to Insert a Viewer is new in R12. Viewers do not need to approve the requisitions, but will be informed of business purchases and decisions through a FYI notification. <Product Name> <TOI Functional> - 58

Advanced Approvals Support Example – Add Viewers
Viewer Icon Speaker Notes: On the graphical list, a viewer is indicated with a Viewer icon. <Product Name> <TOI Functional> - 59

Advanced Approvals Support Example – View Req Status
The Approval Graphical View shows the following: Tom Gallant has approved the requisition The requisition is currently pending approvals from the IT Approval Group and Maria Menudo Speaker Notes: Based on the approvals graph, Tom Gallant has already approved the Requisitions. Notifications had been sent to IT Approval Group & Maria Menudo, and the requisition is currently pending their approvals. Jim Bellevue has not been notified to take any actions. <Product Name> <TOI Functional> - 60

Sourcing At-a-Glance Buying Professional Identify Suppliers & Opportunities Define Strategies & Negotiations Conduct On- Line Negotiations Analyze & Award Approve & Issue LOB Stakeholder Supply Base “Strategic sourcing is emerging as the leading strategy to control costs, capture innovation, and maximize performance.” <Product Name> <TOI Functional> - 61

Oracle Sourcing & Sourcing Optimization
Source More of Your Spend Source for Lowest Total Cost Create Immediate & Long-Term Savings Identify Suppliers & Opportunities Conduct On- Line Negotiations Analyze & Award Approve & Issue Define Strategies & Negotiations Operations Contract Mgmt Purchasing Finance Increase the Effectiveness & Efficiency of Strategic Sourcing <Product Name> <TOI Functional> - 62

Efficient Online Negotiations Slash Cycle Time by Eliminating Manual Processes
View responses and monitor bidding activity in real-time Drill into individual sourcing events View new incoming supplier messages and incomplete tasks <Product Name> <TOI Functional> - 63

Facilitated Online Bid Comparison Make Faster Award Decisions
Use Bid Data to Reduce Manual Effort Knock-out criteria enforcement Automatic bid scoring Side-by-side comparison Analyze Online for Faster, Better Awards Enable selection of suppliers, lots, or specific lines through flexible awards Enforce policy compliance (e.g., multi-source rqmts, MBWE suppliers) Use Award Summary & Recommendation View award details Award approval by workflow

Automatic Scoring of Requirements Quickly Identify the Best Qualified Suppliers Requirements Weight Value (Score) Quote 990 Response Score Are you ISO certified? 25% Yes (100) No (0) No Number of years in business 35% > 14 (100) 10-14 (75) 5-10 (50) < 5 (0) 15 35 Number of shipping locations 40% > 19 (100) 11-19 (50) 1-10 (25) 40 Total Score Calculated by Oracle Sourcing 75 As you can see in this example, Quote 990 received a score of 75 based on its responses to the requirements. All scores were automatically calculated by Oracle Sourcing following the scoring model specified by the buyer during the negotiation creation. Response scores are calculated by multiplying the score for the response by the weight. The sum of all requirements then is added together in order to determine the supplier score of 75. Automatically eliminate suppliers that score below minimum requirements Automatically exclude non-compliant suppliers from shortlists <Product Name> <TOI Functional> - 65

Centralized Terms Library Ensure Consistent Contract Standards
Capture standard contract clauses, variables, templates and deliverables Clearly define enforceable and automated standard policy and procedure Specify document format with flexibility to accommodate regional variations Provide comprehensive revision control via notification-based workflow with approval rules Central Terms Library Support Compliance and Oversight Requirements <Product Name> <TOI Functional> - 66

Expert-Based Authoring Produce Compliant Contracts
Configurable rules drive terms selection for complex contracts Clauses default based on product, supplier, contract value, etc. Author high quality contracts with minimal legal supervision Industry Segment? Template Government Commercial . . . Over $50k? No Yes Draft Responses Drive Clause Selection Add Clauses High Value Insurance Contract <Product Name> <TOI Functional> - 67

Automated MS Word Synchronization Quickly and Accurately Integrate Offline Redline Edits into Contracts Streamline internal collaboration and supplier negotiation by allowing key stakeholders to be involved in the contract review process Improve contracting efficiency while reducing effort Minimize errors and risk from manual updates Contract Administrator Synchronize Download Legal Supplier To summarize what we’ve just seen over the past few slides, Oracle Procurement Contracts reduces the contracting cycle time and streamlines the collaboration and negotiation process by enabling the automatic synchronization of offline Word redline edits to a contract into the system. This automatic update process cuts down contract management times and prevents errors resulting from manual updates to the contract minimizing potential risk and exposure on these contracts. Microsoft Word synchronization streamlines internal collaboration and supplier negotiation by allowing key stakeholders to be involved in the contract review process. It automates the update of system terms with off-line edits thus improving contracting efficiency. Legal Review Supplier Acceptance <Product Name> <TOI Functional> - 68

Automatic Document Generation Eliminate Manual Re-Keying
Automatically substitute negotiated terms in printed document Easily tailor to each business unit’s standard format – logos, headers, layout, etc. Generate standard .pdf business document Variable Substitution <Product Name> <TOI Functional> - 69

Clause Usage Analysis Search Contracts To Analyze Clause Usage & Modification
Quickly determine number of incidents Identify and view contracts with non-standard clauses All policy deviations are reported to approvers alongside clause deviations in the Contract Deviations Report, guiding approvers to exceptions in the contract along with the standard values. Improved legal discovery on contracts across multiple organizations Better insight into effectiveness of current standard language usage Enhanced visibility into contract standards requiring revision <Product Name> <TOI Functional> - 70

Contract Deliverable Tracking Monitor Supplier Performance
Generate monthly milestone progress reports Provide a prototype within 3 months of contract signing Perform site visit and inspection Provide proof of compliance to industry standards Example Deliverables Define Deliverable Send Notification Manage Deliverable Escalate When Necessary Based on contract T’s & C’s One-time and recurring Internal or external Notify individuals or groups Notify trading partners Track progress Indicate failure or completion Attach supporting documents View status change history Define escalation criteria Escalate to supervisor Having the best corporate policies and business practices are useless if they are not followed. Through the use of workflow and event notifications, Oracle Contracts proactively helps adherence to policies and practices by ensuring deliverables compliance. A few example deliverables are listed on the slide. When you set up a deliverable, you can clearly define who is responsible for completing the deliverables and who is responsible for sign-off. Clearly defined ownership is a critical enabler to contract compliance and is demanded by important regulations such as Sarbanes-Oxley. When a deliverable passes due, an escalation can be optionally sent to the owner’s manager. You can define when the will be sent. <Product Name> <TOI Functional> - 71

Manage Contract Deliverables Track Contractual Responsibilities and Key Administrative Tasks
Track internal commitments & contractual obligations Clearly defined ownership Deliverable status at a glance Alert Any Compliance Risk and Highlight Non-Compliance Review Compliance Status Before Authorizing Payments Track Approval History <Product Name> <TOI Functional> - 72

Supplier Registration
Prospective Supplier Registration Reduce Overhead with Self-Service Registration Supplier Requests Supplier Registration Review & Approval Use corporate website to allow interested prospective suppliers to register Configure qualification details captured during registration Define req. elements of supplier profile Include customized questionnaires* as part of registration Use request details to customize approval flow Enable approvers to update details Notify suppliers via once registration request has been approved / rejected * Requires iSurvey <Product Name> <TOI Functional> - 73

Supplier Management User-Interface Streamlined Supplier Profile Management
To Do List for requests Create supplier Search or drill down to supplier details This screenshot shows the Supplier page where supplier can create and maintain supplier information. Internal users can access this page by logging in as a purchasing user with the ability to create and update suppliers. On the Suppliers page, the container box on the left gives an up-to-date to do list. Users can drill down to respond to requests requiring attention and approve from there. The right panel consists of create, search, and update supplier functionality. Click the Create Supplier button to create a supplier. The left panel is a search section, where existing supplier definitions can be found and user can drill down to update supplier details. <Product Name> <TOI Functional> - 74

Q & A <Product Name> <TOI Functional> - 75

Thank You <Product Name> <TOI Functional> - 76

<Product Name> <TOI Functional> - 1

Similar presentations

Presentation on theme: "<Product Name> <TOI Functional> - 1"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

<Product Name> <TOI Functional> - 1

Similar presentations

Presentation on theme: "<Product Name> <TOI Functional> - 1"— Presentation transcript:

Similar presentations

About project

Feedback