Document Styles
Agenda
Introduction
– Description
– Benefits
Setup
– How to set up the feature
Process
– How to use the feature
Summary
Document Styles
Description
Document Styles
– Control the look and feel of the application to match the
needs of different purchasing documents.
– Through reusable document styles, deploying
organizations turn on or off various Oracle Purchasing
features, thereby simplifying the user interface.
Document Styles
Benefits
Name documents
– Name purchasing documents to match deploying
organization’s business and naming conventions
Enable/disable features
– Increase User Productivity by optimizing UI for targeted
Usage
Reduce application complexity
– Simplify user interface by reducing clutter
Setup
Document Styles
Setup – Create Style
Assign Display Names
to Document Types
Enable/Disable
Features
Document Styles
Setup – Create Style
Create Style For
Complex Service
Contracts
Document Styles
Setup – Standard Style
• Standard Style:
Seeded style
Least restrictive
No Complex Payments
support
Documents accessible
from both the Work Center and
PO Forms
Pre-R12 and new
documents
• Non-standard Styles:
Any new styles in R12
Documents accessible
from Work Center only
Process
Document Styles
Process – Create Document
Create purchasing document with the selected style.
Document Styles
Process – Create Document
Display Name from
Style Definition
- Displays attributes for
procuring Services
- Hides attributes for
procuring Goods
Document Styles
Process – Create Document
Available Line Types
Limited by Document
Style
Document Styles
Process – Printed Document
Display Name from
Style Used in External
Facing Documents
Document Styles
Process – Create Demand Request into Order
Create purchasing document for the requisition line with the selected style.
Document Styles
Process – Source Document Reference
Requisitions
– Style of the source document should be compatible with
the requisition line
Purchase Documents
– A purchase document and its source document should
have the same document style (e.g. Standard Purchase
Order referencing a Global Blanket Agreement)
Summary
Document Styles
Summary
Document Styles allow buying organizations to control
the look and feel of the application to match the needs
of different purchasing documents.
• Name documents to match business and naming conventions
Benefits • Enable or disable features on the document
• Reduce application complexity
Procurement for Complex Services
Agenda
Introduction
– Description
– Business Flow
– New Features
– Benefits
Dependencies and Interactions
Summary
Procurement for Complex Services
Description
An integrated solution to automate acquisition of complex services
Complex Services Procurement is characterized by:
– High dollar value projects
– Long lead time delivery schedules
– Complex Payment Terms
– Progress payments based on work completion
– Contract Financing
Commodities of Interest
– Professional Services
– Engineering Services
– Construction Services
Note: Please refer to the Complex Services Procurement TOI for more information on this feature
Procurement for Complex Services
High Level Business Flow
Request for Service Source Author Contract Track Progress Process Payment
Author Contract
Supplier and Contracting Officer sign off on Contract
Supplier reports progress
Progress is certified by Facilities Manager, and/or Project Manager
Procurement for Complex Services
New Purchasing Features
Define Document Styles
Author Complex Service Contracts
– Create Complex Service Contract from Requisition
– Define Progress Payment Schedule
– Define Terms for Retainage
– Define Terms for Contract Financing including Advances
Monitor & Track Contract Status/Progress
Manage Contract Changes
Procurement for Complex Services
Benefits
Streamline and Automate Procurement of the Complex
Services Spend Category
Ensure Compliance with 360º Visibility to all aspects of the
Contract Lifecycle.
Reduce Acquisition Costs through Seamless Collaboration
with Key Stakeholders.
Minimize Acquisition Risks by using Negotiated Payment
Terms
Dependencies and Interactions
Procurement for Complex Services
Dependencies and Interactions
Oracle Purchasing (Required)
– Contract with Complex Payment Terms
– Progress Payment Schedule
– Track Execution of Contract
– Create Work Confirmation
Oracle Services Procurement (Required)
– Use of Fixed Price Services and Temp Labor functionality
Oracle Payables (Optional)
– Create & Submit Invoices for Progress Payments, Advances &
Financing, Retainage Release
Oracle Sourcing (Optional)
– Negotiate with Suppliers on Payment Terms and Payment
Schedule
Oracle Procurement Contracts (Optional)
– Use Clauses & Deliverables on Contract
Procurement for Complex Services
Dependencies and Interactions
Oracle iProcurement (Optional)
– Create Service Requests
Oracle iSupplier Portal (Optional)
– Track Execution of Contract
– Create & Submit Work Confirmation
– Create & Submit Invoices for Progress Payments, Advances &
Financing
Oracle E-Tax (Optional)
– Tax Engine with rules for tax calculation on Payment Schedule,
Advances, and Contract Financing
Oracle Enterprise Asset Management (Optional)
– Carry Work Order Reference on Requisition
Summary
Procurement for Complex Services
Summary
Complex Services Procurement is a new solution
Reduces acquisition costs
– Manage, Control & Track Complex Contracts
– Keep lead times & costs in check by monitoring progress on
Progress Payment Schedule
– Minimize acquisition risks by using negotiated Payment Terms
Offers seamless collaboration between key stakeholders
– Eliminates paper-based processes
– Ensures visibility & smooth execution of the Contract
Multi-Org Access Control
Agenda
Introduction
– Description
– Benefits
Setup and Process
– How to use the feature
Summary
Multi-Org Access Control
Description
Multi-Org Access Control (MOAC)
– Access multiple operating units from a single application
responsibility
– Enable shared services while maintaining operating unit
security
Multi-Org Access Control
Description
OLD PROCESS
Application Application Application
Responsibility A Responsibility B Responsibility C
Operating unit X Operating unit Y Operating unit Z
NEW PROCESS
Application
Responsibility A
Operating unit X Operating unit Y Operating unit Z
Multi-Org Access Control
Benefits
Streamlined Shared Service Center Operations
– Access, process, and report on data for multiple
operating units from within a single applications
responsibility
– Eliminates the need to switch application
responsibilities in order to service multiple
operating units
Setup
Multi-Org Access Control
Setup and Process
SETUP
Define security profile &
assign operating units
Run Security List
Maintenance
Assign
security profile to
responsibility or user
Multi-Org Access Control
Setup - Create Operating Unit
Use Oracle
Financial
Accounting
Setup Manager
Or
Oracle HRMS
Organization
Form
Multi-Org Access Control
Setup – Create Security Profile
A security
profile may be
defined in
hierarchical
(using
hierarchy
above) mode
CA Security Profile based on Hierarchy
Multi-Org Access Control
Setup - Run Concurrent Program
Multi-Org Access Control
Setup – Set Profile Options
Profile Value Description
Identify the list of operating units
MO: Security Profile
that the user can access
Identify the default operating unit
MO: Default Operating Unit
for the user when accessing an application
R11i profile option that will be maintained
MO: Operating Unit for those products and customers not
leveraging Multiple Organizations.
Process
Multi-Org Access Control
Requisition Entry
Enter Requisitions for
Multiple OUs
Multi-Org Access Control
Requisition Management
View Requisition
Demand Across
Multiple OUs
Multi-Org Access Control
Requisition Management
Negotiate and Order for
Requisition Demand in
Multiple OUs
Multi-Org Access Control
Purchase Agreement Management
Author Agreement for
Multiple OUs
Multi-Org Access Control
Purchase Agreement Management
Search for Agreements
across Multiple OUs
Multi-Org Access Control
Purchase Order Management
Place Purchase Orders
for Multiple OUs
Multi-Org Access Control
Purchase Order Management
View Orders Across
Operating Units
Multi-Org Access Control
Approved Supplier List
Maintain Approved
Suppliers for Multiple OUs
Multi-Org Access Control
ASL Summary
View ASLs for Multiple
OUs
Multi-Org Access Control
RFQ Entry
Enter RFQs for Multiple
OUs
Multi-Org Access Control
Purchasing Setups – Requisition Template
Create Requisition
Templates for Multiple
OUs
Multi-Org Access Control
Purchasing Setups – Purchasing Options
Perform Setups for
Multiple OUs
Multi-Org Access Control
Concurrent Programs
Run Concurrent
Programs for Multiple
OUs
Multi-Org Access Control
Public APIs
Public APIs modified to accept Operating Unit as a
parameter
Example Public APIs modified:
– PO Change API – POXCHN1B.pls
– Cancel PO API – POXPDCOB.pls
– Price Control API – POXPCPRB.pls
Summary
Multi-Org Access Control
Summary
Multi Org Access Control is a new process:
Facilitates access to multiple operating units from a
single application responsibility
Enables shared services while maintaining operating
unit security
Benefits Streamlined Shared Service Center Operations
