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
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
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.
PO Award Buyer Bulkload / Online author PBWC iP Admin External Supplier Sites iP Catalog Admin Buyer Approve iSP Requester Sourcing Supplier Sourcing Professional Enhanced Catalog Agreement Management Overview Catalog Definitions: Buyer - Purchasing user Supplier - Supplies goods or services to the buying organization Catalog Administrator - Performs catalog related activities within the buying organization
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
Content Security EnhancementsDescription • 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.
Content Security EnhancementsPartition Content 11.5.10 Release 12 • Release 12 Content Zones Replace 11.5.10 Catalogs. • All Content Zones Support Operating Unit or Responsibility Security.
iProcurement – Content SecurityWhat’s New? Example: Local Content Inclusion Rule Supplier • The rules: • Include items from supplier X • Include items from category C Correspond to the red block of available content. Supplier X Supplier Y .... … Category Category A Category B Category C
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). iProcurement – Content SecurityWhat’s New? Example: Local Content Exclusion and Inclusion Rules Supplier Supplier X Supplier Y .... … Category Category A Category B Category C
iProcurement – Content SecurityWhat’s New? Let’s Look at how category rules are defined: Include specific categories Include specific suppliers Make content accessible to specific user groups
iProcurement – Content SecurityWhat’s New? 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).
iProcurement – Content SecurityWhat’s New? Let’s Look at how supplier rules are defined: Include specific categories Include specific suppliers Make content accessible to specific user groups
iProcurement – Content SecurityWhat’s New? 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.
iProcurement – Content SecurityWhat’s New? • 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
iProcurement – Content SecurityWhat’s New? Assign Content Zone to specific Responsibilities, Operating Units, or all Users.
Content Security EnhancementsBenefits • 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.
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
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
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
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 Usability EnhancementsParagraph Search Skin
3 columns format allows more information to be displayed Usability EnhancementsParagraph Search Skin
Usability EnhancementsSearch Skins – Grid Format The grid format allows users to differentiate between similar items more effectively.
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
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.
Advanced Approvals Enhancements Example – Add Viewers Option to add Viewers to the Approval List
Usability EnhancementsBenefits • 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
Usability EnhancementsBenefits • 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
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
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
Professional Buyer’s Work Center Customization and Extensibility Options • Customers can create custom views using personalization feature in all inquiry pages.
Professional Buyer’s Work CenterBenefits • 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.
Enhanced Catalog AccessFeature 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
Document StylesFeature Description Assign Display Names to Document Types Enable/Disable Features
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.
Multi-Org Access Control Feature Description OLD PROCESS Application Responsibility B Application Responsibility A Application Responsibility C Operating unit Y Operating unit X Operating unit Z NEW PROCESS Application Responsibility A Operating unit Y Operating unit Z Operating unit X
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)
Document Printing EnhancementsFeature Description Purchasing Layout PO Output New in Release 12.0 Purchasing XML 11.5.10 New in Release 12.0 Purchasing Layout PO Output in Multiple Formats Purchasing XML Release 12
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
Support for Contractor Purchasing UsersFeature 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
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 4. PO complies to Supplier packaging constraints PURCHASE ORDER SUPPLIERS
E-Business Tax Integration Feature Description Prior toE-Business Tax • Basic tax setup – tax codes and tax groups WithE-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 Note: Please refer to the e Business Tax TOI for more information on this feature
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 Model Complex Pricing for Blanket Line Items Blanket 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 Orders Oracle Advanced Pricing
Mass Re-pricing of Purchasing DocumentsFeature Description Orders Blanket Purchase Agreement Advanced Pricing Price Lists, Modifiers Revise Pricing Data New in Release 12.0 Custom Pricing API
Auto-Approval Tolerances for Change Orders Eliminates need for Workflow Customizations Set tolerances by document type New tolerance attributes introduced
Advanced Approvals Support for RequisitionsDescription • Parallel Approvals • Notifications are sent out to multiple people simultaneously to speed up the approval process • Position Hierarchy Support