D50792GC10 sg1

Oracle Internal & Oracle Academy Use Only
R12 Oracle iProcurement

Fundamentals
Student Guide – Volume 1
D50792GC10
Edition 1.0
September 2007
D53020
Copyright © 2002, 2007, Oracle. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted

by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Author
Richard Sears, Vic Mitchell
Technical Contributors and Reviewers
Barbara.Snyder, Sharon Tennier
This book was published using: oracletutor

Table of Contents
Procure to Pay Lifecycle Overview ................................................................................................................1-1

Procure to Pay Lifecycle Overview ...............................................................................................................1-3
Objectives ......................................................................................................................................................1-4
Procure to Pay Lifecycle................................................................................................................................1-5
Oracle Procure to Pay Process.......................................................................................................................1-7
Demand: Requisitions....................................................................................................................................1-9
Source: RFQs and Quotations .......................................................................................................................1-11
Suppliers ........................................................................................................................................................1-13
Purchase Orders.............................................................................................................................................1-15
Receiving.......................................................................................................................................................1-17
Invoicing........................................................................................................................................................1-19
Payment .........................................................................................................................................................1-20

Overview of Oracle Application Integration .................................................................................................1-21
Summary........................................................................................................................................................1-23
Understanding Oracle iProcurement.............................................................................................................2-1
Understanding Oracle iProcurement..............................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Procure to Pay: Oracle iProcurement.............................................................................................................2-5
Agenda...........................................................................................................................................................2-6
Oracle Advanced Procurement ......................................................................................................................2-7
Oracle iProcurement In E-Business...............................................................................................................2-9
Key Oracle iProcurement Capabilities ..........................................................................................................2-10
E-Business Suite Integration..........................................................................................................................2-11
Procurement Suite Integration .......................................................................................................................2-13
Agenda...........................................................................................................................................................2-15
Key Functionality of Oracle iProcurement ....................................................................................................2-16
Oracle iProcurement Content Management...................................................................................................2-18
Content Zones................................................................................................................................................2-19
Stores .............................................................................................................................................................2-20
Shopping........................................................................................................................................................2-21
Overview of Checkout...................................................................................................................................2-23
Approval and Document Creation .................................................................................................................2-24
Overview of Receiving..................................................................................................................................2-25
Center-Led Procurement................................................................................................................................2-26
Agenda...........................................................................................................................................................2-27
Oracle iProcurement Shopping Data Flow ....................................................................................................2-28
Oracle iProcurement Submit Request Data Flow .........................................................................................2-30
Agenda...........................................................................................................................................................2-32
Oracle iProcurement Setup Overview ...........................................................................................................2-33
Oracle iProcurement Setup Steps ..................................................................................................................2-34
Practice - Create a New Employee and User .............................................................................................2-35
Solution - Create A New Employee and User ...........................................................................................2-36
Practice - Set Yourself Up As a Buyer ......................................................................................................2-40
Guided Demonstration - Run the Fill Employee Hierarchy Process .........................................................2-42
Summary........................................................................................................................................................2-43
Oracle iProcurement Content Management .................................................................................................3-1
Objectives ......................................................................................................................................................3-4
Procurement Process: Oracle iProcurement...................................................................................................3-5
Agenda...........................................................................................................................................................3-6
What Are iProcurement Catalogs? ................................................................................................................3-7
Copyright © Oracle, 2007. All rights reserved.
R12 Oracle iProcurement Fundamentals Table of Contents

i
Why Use Catalogs? .......................................................................................................................................3-8
What is an iProcurement Store? ....................................................................................................................3-9
Where Does the Catalog Content Come From?............................................................................................3-10
Local or Buyer-Hosted Content.....................................................................................................................3-13
External or Supplier-Hosted Content.............................................................................................................3-14
External Marketplace-Hosted Content...........................................................................................................3-16
Choosing Content ..........................................................................................................................................3-17
Requirements of Local Catalogs....................................................................................................................3-18
Requirements of Supplier-Hosted Content ....................................................................................................3-19
Requirements of Marketplace-Hosted Content............................................................................................3-20
Utilization of Catalog Content.......................................................................................................................3-21
Control Content Using Content Zones...........................................................................................................3-22
Stores: Pulling It All Together…...................................................................................................................3-23
iProcurement Catalog Administration ...........................................................................................................3-24
Agenda...........................................................................................................................................................3-25
Creating Local Content..................................................................................................................................3-26

Oracle iProcurement Content Management Review.....................................................................................3-27
Oracle Content Utilization Types ..................................................................................................................3-28
Local Content ................................................................................................................................................3-29
E-Business Suite Local Content ....................................................................................................................3-30
Practice - Create a Purchasing Category....................................................................................................3-31
Solution - Create a Purchasing Category ...................................................................................................3-32
Practice - Create Items...............................................................................................................................3-38
Solution – Create Items .............................................................................................................................3-39
Uploading Local Content...............................................................................................................................3-44
Before Uploading Content.............................................................................................................................3-45
Upload Content: Resource Files ....................................................................................................................3-46
Item Content That You Upload .....................................................................................................................3-47
Uploading Local Content...............................................................................................................................3-48
Content Upload And Document Types..........................................................................................................3-49
Automatically Uploading Shopping Categories ............................................................................................3-50
Price Lists That You Upload .........................................................................................................................3-51
Online Content Authoring Flow ....................................................................................................................3-52
Upload Content Authoring Flow ...................................................................................................................3-53
Sample Item Spreadsheet Upload ..................................................................................................................3-54
Practice - Create a Global Blanket Purchase Agreement and Edit Content...............................................3-55
Solution - Create a Global Purchase Agreement and Edit Content............................................................3-56
XML: More Catalog Control .........................................................................................................................3-62
XML Upload Items File Structure .................................................................................................................3-63
Uploading Items: Spreadsheet Compared to XML.......................................................................................3-65
Sample XML Administrative Section............................................................................................................3-66
Sample XML Data File Structure ..................................................................................................................3-67
Sample XML Document Header Section ......................................................................................................3-68
Sample XML Document Lines Section .........................................................................................................3-69
Sample XML Data Item Section....................................................................................................................3-70
Sample XML Data Price Section...................................................................................................................3-71
Practice - Understand the XML Data File Structure..................................................................................3-72
Practice - Load Items Using XML.............................................................................................................3-73
Solution – Load Items Using XML ...........................................................................................................3-74
Loading Local Catalog Images ......................................................................................................................3-81
Sample Uploads for Image Files....................................................................................................................3-82
Maintaining Items and Prices ........................................................................................................................3-83
View Loader Job Status.................................................................................................................................3-84
View Document Upload History ...................................................................................................................3-86
Agenda...........................................................................................................................................................3-87
Catalogs, Content Zones, And Stores ............................................................................................................3-88

ii
iProcurement Catalog Administration: Manage Stores ................................................................................3-89
Content Zones................................................................................................................................................3-90
Why Content Zones? .....................................................................................................................................3-91
Creating A Local Content Zone.....................................................................................................................3-92
Applying Content Security Rules ..................................................................................................................3-93
Applying Content Security Rules In Stores ...................................................................................................3-94
Practice - Create a Local Content Zone .....................................................................................................3-95
Solution – Create a Local Content Zone....................................................................................................3-96
Creating A Punchout Zone ............................................................................................................................3-99
Creating An Informational Zone ...................................................................................................................3-100
Practice - Create an Informational Content Zone ......................................................................................3-102
Solution......................................................................................................................................................3-103
Creating Smart Forms....................................................................................................................................3-104
What Are iProcurement Stores? ....................................................................................................................3-105
Managing Stores ............................................................................................................................................3-107
Practice - Create a Store ............................................................................................................................3-109
Solution – Create a Store ...........................................................................................................................3-110

Agenda...........................................................................................................................................................3-112
Remote Catalog Content................................................................................................................................3-113
Oracle iProcurement Catalog Management Review.....................................................................................3-114
Oracle Content Zone Types Review..............................................................................................................3-116
What is Punchout? .........................................................................................................................................3-117
What is Transparent Punchout? .....................................................................................................................3-118
Oracle iProcurement Punchout Models .........................................................................................................3-120
XML: The Language of a Punchout ..............................................................................................................3-121
Comparing a Supplier Punchout to a Marketplace Punchout ........................................................................3-122
Model 1 & 2 Technical Overview .................................................................................................................3-123
Models 3 & 4 Technical Overview................................................................................................................3-124
Deciding on a Punchout Model .....................................................................................................................3-126
Punchout Management ..................................................................................................................................3-127
Basic Punchout Setup Steps...........................................................................................................................3-128
Oracle Exchange Punchout Setup..................................................................................................................3-130
Supplier Punchout Setup ...............................................................................................................................3-131
Agenda...........................................................................................................................................................3-132
Administer Oracle iProcurement Catalog Structure .....................................................................................3-133
Catalog Structure Components ......................................................................................................................3-134
Local Catalog Structure: Categories ..............................................................................................................3-135
Local Catalog Structure: Items ......................................................................................................................3-136
Creating and Modifying the Catalog Structure..............................................................................................3-137
Online Schema Maintenance .........................................................................................................................3-138
XML Upload Schema File Structure .............................................................................................................3-139
Sample XML Schema File.............................................................................................................................3-140
Sample XML Schema Section.......................................................................................................................3-141
Practice - Review XML Schema Structure................................................................................................3-142
Practice - Load Categories using XML .....................................................................................................3-143
Solution – Load Categories Using XML ...................................................................................................3-144
Manage Base Descriptors ..............................................................................................................................3-148
Manage Item Categories................................................................................................................................3-149
Managing Descriptors....................................................................................................................................3-150
Manage Category Hierarchy..........................................................................................................................3-152
Sample iProcurement Table of Contents .......................................................................................................3-153
Map iProcurement Categories .......................................................................................................................3-154
Map Purchasing Categories ...........................................................................................................................3-155
Shopping Category Mapping.........................................................................................................................3-156
Practice - Map iProcurement Categories to Purchasing Categories...........................................................3-157
Solution – Map iProcurement Categories to Purchasing Categories .........................................................3-158
Practice - Build a Schema Hierarchy.........................................................................................................3-159

iii
Solution - Build a Schema Hierarchy ........................................................................................................3-160
Uploading Categories and Descriptors ..........................................................................................................3-162
Agenda...........................................................................................................................................................3-163
Catalog Search Components..........................................................................................................................3-164
Types of Catalog Searches.............................................................................................................................3-165
Search Results Display: Paragraph ................................................................................................................3-167
Search Results Display: Grid.........................................................................................................................3-168
Special Characters in Catalog Searches.........................................................................................................3-169
Filtering and Sorting......................................................................................................................................3-170
Search Descriptor Characteristics..................................................................................................................3-171
Searchable Base Descriptors..........................................................................................................................3-172
Search Results Visible Base Descriptors .......................................................................................................3-173
Rebuild Catalog Indexes................................................................................................................................3-174
Search Engine Setup Impact..........................................................................................................................3-175
Agenda...........................................................................................................................................................3-176
iProcurement Catalog Administration ...........................................................................................................3-177
Setup Considerations .....................................................................................................................................3-178

Local Catalog Setup.......................................................................................................................................3-179
Profile Options for Uploading Local Content................................................................................................3-180
Supplier-Hosted Setup...................................................................................................................................3-181
Marketplace-Hosted Setup.............................................................................................................................3-182
Profile Options for Punchout .........................................................................................................................3-183
Practice - Recognize Catalog Specific Profile Options..............................................................................3-184
Agenda...........................................................................................................................................................3-186
Decide on a Catalog Source...........................................................................................................................3-187
Considerations for Local Catalogs.................................................................................................................3-189
Considerations for Supplier-Hosted Content .................................................................................................3-191
Considerations for Marketplace-Hosted Content...........................................................................................3-192
Considerations for Security ...........................................................................................................................3-193
Summary........................................................................................................................................................3-194
Oracle iProcurement Requisitions .................................................................................................................4-1
Oracle iProcurement Requisitions .................................................................................................................4-3
Objectives ......................................................................................................................................................4-4
Agenda...........................................................................................................................................................4-5
iProcurement Flow ........................................................................................................................................4-7
iProcurement Home Page ..............................................................................................................................4-8
iProcurement Preferences ..............................................................................................................................4-9
Practice - Set User Preferences..................................................................................................................4-10
Solution – Set User Preferences.................................................................................................................4-11
Shop For Goods and Services........................................................................................................................4-14
Practice - Creating a Favorites List............................................................................................................4-16
Solution – Creating a Favorites List ..........................................................................................................4-17
Basic Shopping Flow.....................................................................................................................................4-20
Basic Checkout Flow.....................................................................................................................................4-21
Checkout Step-by-Step ..................................................................................................................................4-22
Review & Submit ..........................................................................................................................................4-24
Practice - Split Cost Across Charge Accounts...........................................................................................4-25
Solution – Split Cost Across Charge Accounts .........................................................................................4-26
Practice - Specify Different Delivery Information for a Single Item.........................................................4-29
Solution – Specify Different Delivery Information for a Single Item .......................................................4-30
Agenda...........................................................................................................................................................4-32
Enter iProcurement Users ..............................................................................................................................4-33
Document Routing Option #1: Employee/Supervisor Relationship ..............................................................4-35
Document Routing Option #2: Position Approval Hierarchy........................................................................4-36
Run Fill Employee Hierarchy Process...........................................................................................................4-38

iv
Document Routing Option #3: Oracle Approvals Management....................................................................4-39
Give Access to the Users ...............................................................................................................................4-41
Guided Demonstration - Scheduling Send Notification Workflows..........................................................4-42
My Notifications Region ...............................................................................................................................4-43
Center-Led Procurement................................................................................................................................4-44
Agenda...........................................................................................................................................................4-46
Set up iProcurement Shopping Defaults........................................................................................................4-47
Oracle Applications Framework....................................................................................................................4-48
OAF / iProcurement Personalization .............................................................................................................4-49
Guided Demonstration - Add Filter Option to Search Results Page..........................................................4-50
Setting Up iProcurement Information Templates ..........................................................................................4-52
Practice - Create an Information Template ................................................................................................4-53
Solution – Create an Information Template...............................................................................................4-54
Practice - Submit a Requisition Using an Information Template ..............................................................4-57
Solution – Submit a Requisition Using an Information Template .............................................................4-58
Smart Forms ..................................................................................................................................................4-61
Internally Sourced Requisitions Overview ....................................................................................................4-63

Internally Sourced Requisitions Details ........................................................................................................4-65
Internally Sourced Requisitions Prerequisites ...............................................................................................4-67
Guided Demonstration - Enter and Submit an Internally Sourced Requisition .........................................4-69
Services Procurement Contractor/Service Request ......................................................................................4-70
Oracle Services Procurement.........................................................................................................................4-72
Services Procurement: Contingent Labor Flow............................................................................................4-74
Oracle Procurement Feature Comparison......................................................................................................4-75
Agenda...........................................................................................................................................................4-76
Requisition Management Actions..................................................................................................................4-77
Copying Requisitions ....................................................................................................................................4-78
Canceling Requisitions ..................................................................................................................................4-79
Change / Resubmit Requisitions....................................................................................................................4-80
Requisition Statuses.......................................................................................................................................4-82
Requester Change Order................................................................................................................................4-83
Requester Change Order Approval................................................................................................................4-85
Procure to Pay Lifecycle Tracking ................................................................................................................4-87
Agenda...........................................................................................................................................................4-88
Setting Up Oracle iProcurement Responsibility and Function Security ........................................................4-89
Approval and Document Creation .................................................................................................................4-90
Automatic Purchase Order Creation ..............................................................................................................4-91
Automatic Release Creation ..........................................................................................................................4-92
Oracle iProcurement Requisition Approval...................................................................................................4-93
Integration with Oracle Approvals Management...........................................................................................4-95
Workflows Used by Oracle iProcurement .....................................................................................................4-96
PO Create Documents Workflow ..................................................................................................................4-98
Guided Demonstration - Set Values of Key Workflow .............................................................................4-100
Accounting Considerations for Oracle iProcurement ...................................................................................4-101
PO Account Generator Workflow .................................................................................................................4-102
Account Creation Overview ..........................................................................................................................4-103
Expense Account Rules .................................................................................................................................4-105
Practice - Create Expense Account Rules..................................................................................................4-106
Solution – Create Expense Account Rules ................................................................................................4-107
Tax Calculation .............................................................................................................................................4-110
Grants Accounting and Hazard Information..................................................................................................4-111
Attachments and Special Requisitions...........................................................................................................4-112
Guided Demonstration - Create iProcurement Buyer Attachment.............................................................4-114
Agenda...........................................................................................................................................................4-115
Procurement Card Support ............................................................................................................................4-116
Procurement Card Flow - Order ...................................................................................................................4-117
Procurement Card Flow - Invoice..................................................................................................................4-118

v
Procurement Card Flow - Reconciliation ......................................................................................................4-120
Setting Up Credit Card Programs in Oracle Payables ...................................................................................4-122
Code Sets Window ........................................................................................................................................4-123
Card Programs Window ................................................................................................................................4-124
GL Account Sets Window .............................................................................................................................4-125
Credit Card Profiles Window ........................................................................................................................4-126
Credit Cards Window ....................................................................................................................................4-127
Credit Card Workflows .................................................................................................................................4-128
P-Card Setup for iProcurement......................................................................................................................4-129
Practice - Set Up and Use P-Cards ............................................................................................................4-130
Solution – Set Up and Use P-Cards ...........................................................................................................4-133
Agenda...........................................................................................................................................................4-145
iProcurement Profile Options ........................................................................................................................4-146
Practice - Recognize Requisition Specific Profile Options........................................................................4-147
Solution......................................................................................................................................................4-148
Notification Routing Rules ............................................................................................................................4-151
Personalizing the Home Page ........................................................................................................................4-152

Home Page Logo ...........................................................................................................................................4-153
Purchasing News ...........................................................................................................................................4-154
Purchasing Policies........................................................................................................................................4-155
Descriptive Flex Fields In iProcurement .......................................................................................................4-156
Agenda...........................................................................................................................................................4-158
Requisition Implementation Considerations Checklist..................................................................................4-159
Important Points to Remember......................................................................................................................4-161
Summary........................................................................................................................................................4-162
Oracle iProcurement Receiving......................................................................................................................5-1
Oracle iProcurement Receiving.....................................................................................................................5-3
Objectives ......................................................................................................................................................5-4
Agenda...........................................................................................................................................................5-5
Key Functionality of Oracle iProcurement ....................................................................................................5-7
Overview of Procurement Receiving.............................................................................................................5-9
Oracle iProcurement Receipt Routing ...........................................................................................................5-10
Agenda...........................................................................................................................................................5-11
Receiving in Oracle iProcurement.................................................................................................................5-12
Receiving Orders in Oracle iProcurement .....................................................................................................5-13
Oracle iProcurement Receiving Page ............................................................................................................5-14
Receiving Home Page Functions...................................................................................................................5-15
iProcurement Receiving Process ...................................................................................................................5-16
Finding Your Receipts...................................................................................................................................5-17
Practice - Receive in iProcurement............................................................................................................5-19
Solution – Receive in iProcurement ..........................................................................................................5-20
Entering Returns in Oracle iProcurement......................................................................................................5-24
Entering Corrections......................................................................................................................................5-27
Difference Between Returns and Corrections................................................................................................5-28
Practice - Process a Correction ..................................................................................................................5-29
Solution – Process a Correction.................................................................................................................5-30
Practice - Process a Return ........................................................................................................................5-31
Solution – Process a Return.......................................................................................................................5-32
Guided Demonstration - Run the Confirm Receipts Workflow (Required) ..............................................5-34
Receipt Header in Oracle iProcurement ........................................................................................................5-37
Receipt Line in Oracle iProcurement.............................................................................................................5-38

vi
The PO Confirm Receipts Workflow ............................................................................................................5-39
Agenda...........................................................................................................................................................5-40
Purchasing Receiving Setup ..........................................................................................................................5-41
iProcurement Profile Options ........................................................................................................................5-43
Practice - Recognize Receiving Specific Profile Options..........................................................................5-44
Solution – Recognize Receiving Specific Profile Options ........................................................................5-45
iProcurement Receipt Function Security .......................................................................................................5-46
Agenda...........................................................................................................................................................5-47
Additional Receiving Considerations ............................................................................................................5-48
Receiving Comparison ..................................................................................................................................5-49
Data Mapping Considerations .......................................................................................................................5-50
Data and Reporting Considerations ...............................................................................................................5-51
Optional Components ....................................................................................................................................5-52
Receiving Open Interface ..............................................................................................................................5-53
Overview of Payment on Receipt ..................................................................................................................5-54
Summary........................................................................................................................................................5-55

Objectives ......................................................................................................................................................6-4
Agenda...........................................................................................................................................................6-5
Oracle iProcurement Integration with Oracle Applications Impact on Setup................................................6-7
Agenda...........................................................................................................................................................6-9
Oracle Applications Setup Overview ............................................................................................................6-10
Oracle Applications Setup Overview - 2 .......................................................................................................6-11
Agenda...........................................................................................................................................................6-14
Perform Oracle iProcurement Specific System Administration Setup ..........................................................6-16
Verify Profile Options That Impact Oracle iProcurement: Oracle Applications ...........................................6-17
Verify Profile Options That Impact Oracle iProcurement: Oracle Purchasing..............................................6-19
Verify Profile Options That Impact Oracle iProcurement .............................................................................6-21
Verify Profile Options That Impact Oracle iProcurement: Continued ..........................................................6-23
Practice - Recognize Catalog Specific Profile Options..............................................................................6-25
Practice - Recognize Requisition Specific Profile Options........................................................................6-27
Solution......................................................................................................................................................6-28
Practice - Recognize Receiving Specific Profile Options..........................................................................6-31
Solution – Recognize Receiving Specific Profile Options ........................................................................6-32
Requisition Templates ...................................................................................................................................6-33
Define Information Templates.......................................................................................................................6-34
Set Up Catalog...............................................................................................................................................6-35
Agenda...........................................................................................................................................................6-36
Additional Implementation Considerations ...................................................................................................6-37
Training Considerations ................................................................................................................................6-38
Oracle iProcurement Features to Consider ....................................................................................................6-39
Custom Package Implementation ..................................................................................................................6-40
Page-Specific Customization.........................................................................................................................6-41
Summary........................................................................................................................................................6-42

vii
Preface
Profile
Before You Begin This Course
• Thorough knowledge of the Oracle E-Business Procure to Pay process.
• Working experience with e Oracle E-Business Procure to Pay products.
Prerequisites
• R12 Oracle Purchasing Fundamentals

How This Course Is Organized
This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.

ix
Related Publications
Oracle Publications
Title Part Number
Oracle Purchasing User's Guide B28669-01
Oracle iProcurement Implementation and Administration Guide B31402-01
Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout B13856-01
Oracle Payables User Guide B25454-01
Additional Publications

• System release bulletins
• Installation and user’s guides
• Read-me files
• International Oracle User’s Group (IOUG) articles
• Oracle Magazine

x
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.
lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.
windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);
case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)

(default is filenames, Filename: Locate the init.ora file.
lowercase) passwords, Password: User tiger as your password.
pathnames, Pathname: Open c:\my_docs\projects
URLs, URL: Go to http://www.oracle.com
user input,
User input: Enter 300
usernames
Username: Log on as scott
Initial cap Graphics labels Customer address (but Oracle Payables)
(unless the term is a
proper noun)
Italic Emphasized words Do not save changes to the database.
and phrases, For further information, see Oracle7 Server SQL Language
titles of books and Reference Manual.
courses, Enter user_id@us.oracle.com, where user_id is the
variables name of the user.
Quotation Interface elements Select “Include a reusable module component” and click Finish.
marks with long names
that have only This subject is covered in Unit II, Lesson 3, “Working with
initial caps; Objects.”
lesson and chapter
titles in cross-
references
Uppercase SQL column Use the SELECT command to view information stored in the
names, commands, LAST_NAME
functions, schemas, column of the EMP table.
table names
Arrow Menu paths Select File > Save.
Brackets Key names Press [Enter].
Commas Key sequences Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xi
Typographic Conventions in Code
Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER (‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

italic
Uppercase SQL commands and SELECT userid
functions FROM emp;
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2. (M) From the menu, select Query then Find.
3. (B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xii
Typographical Conventions in Oracle Application Help System Paths
This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—
(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:
1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.

xiii

xiv
Procure to Pay Lifecycle
Overview
Chapter 1
Procure to Pay Lifecycle Overview

Chapter 1 - Page 1

Chapter 1 - Page 2

Chapter 1 - Page 3
Objectives

Chapter 1 - Page 4

Sourcing
• Request for quote
• Supplier selection
• Contract negotiations and awards
• Catalog content management
Ordering
• Requisition and purchase order generation
• Purchase order management and fulfillment
• Payment
Reporting and Analysis
• Supplier performance
• Commodity analysis
• Internal compliance
• Robust intelligence gathering

Chapter 1 - Page 5
• Decision support
• Process functionality

Chapter 1 - Page 6
Oracle Procure to Pay Process

Oracle Procure to Pay Process
Demand
The procurement process generates and manages requests for the purchase of goods. The
demand for purchase items may be a one-time event or may recur in either predictable or
random time intervals.
Source
The procurement sourcing process covers the business activities related to the search,
qualification, and selection of suitable suppliers for requested goods and services.
Order
The procurement ordering process includes purchase order placement by the buying
organization and purchase order execution by the supplying organization.
Receive
The receipt process acknowledges that a purchase order has been duly executed. For orders of
physical goods, it will typically include the receipt, inspection and delivery of the goods to
inventory or to another designated location. For orders of services, it will typically consist of a

Chapter 1 - Page 7
notification from the requester or the approving person that the service has been performed as
agreed.
Pay
The payment process consists of those activities involved in the payment for ordered goods and
services.

Chapter 1 - Page 8
Demand: Requisitions

Demand: Requisitions
Requisitions represent demand for goods or services. Whether you want to provide online
requisitions to everyone in the organization or limit the number of users who have access to the
system, Oracle Purchasing is flexible enough to meet the needs of your organization. With
online requisitions, you can centralize your purchasing department, source your requisition
with the best suppliers, and ensure that you obtain the appropriate management approval before
creating purchase orders from requisitions.
Requisitions for goods and services:
• Are generated by applications like Inventory, Work in Process (WIP), Advanced Supply
Chain Planning (ASCP) and Order Management
• May be entered manually through Oracle Purchasing windows
• May be entered using Oracle iProcurement
• May be imported from external systems
With Oracle Purchasing, you can:

Chapter 1 - Page 9
• Create, edit, and review requisition information on-line. You can enter suggested supplier
information, delivery instructions, multiple accounting distributions, and notes to buyers,
approvers, and receivers.
• Review the current status and action history of your requisitions. You always know who
approves requisitions and whether they are in the approval, purchasing, receiving, or
delivery stage.
• Route requisitions according to your approval structure. You can set authorization limits
by amount, charge account, item category, and location.
• Review and approve requisitions that need your approval. You can see the full requisition
detail and review the action history before you approve a requisition.
• Print requisitions (with status Approved, Cancelled, Rejected, In Process, Pre-Approved,
and Returned) for off-line review and approval. You can always be able to track the status
of requisitions through the approval process.

• Automatically source requisitions from outstanding blanket purchase agreements or
quotations you have received from suppliers.
• Create requisitions quickly and easily for commonly purchased items.
• Provide attachments as notes on requisition headers and lines.
• Assign requisition lines to buyers and review buyer assignments for requisition lines.
• Forward all requisitions awaiting approval from one approver to an alternate approver.
Within your security and approval constraints, you can reroute requisitions from one
approver to another whenever you want.
• Source goods from your own inventory with internal requisitions.

Chapter 1 - Page 10
Source: RFQs and Quotations

Source: RFQs and Quotations
Oracle Purchasing provides you with request for quotation (RFQ), and quotation features to
handle your sourcing needs. You can create an RFQ from requisitions, match supplier
quotations to your RFQ, and automatically copy quotation information to purchase orders.
Oracle Purchasing provides complete reporting to control your requests for quotations and
evaluate supplier responses.
Quotations can be:
• Entered manually
• Copied from an RFQ
• Imported using the Purchasing Documents Open Interface
• Imported using the e-Commerce Gateway
• Identify requisitions that require supplier quotations and automatically create an RFQ.
• Create an RFQ with or without approved requisitions so that you can plan ahead for your
future procurement requirements.

Chapter 1 - Page 11
• Record supplier quotations from a catalog, telephone conversation, or response from your
request for quotation. You can also receive quotations electronically.
• Review, analyze, and approve supplier quotations that you want available to reference on
purchase orders and requisitions. You can evaluate your suppliers based on quotation
information.
• Receive automatic notification when a quotation or request for quotation approaches
expiration.
• Review quotation information online when creating purchase orders or requisitions and
copy specific quotation information to a purchase order or requisition.
• Source the items for which you negotiated purchase agreements automatically. If you
created sourcing rules and approved supplier list entries for the items, supplier information
can be entered automatically in the Requisitions window when you create requisitions.
You can also place supplier information for items onto blanket purchase order releases.

With Oracle Purchasing and Oracle Sourcing, you can:
• Initiate a buyers auction in Oracle Sourcing based on requisitions in Oracle Purchasing.
• Create RFQs and negotiations in Oracle Sourcing that result in purchase orders and
purchase agreements in Oracle Purchasing.
• Collaborate on-line directly with suppliers to get the best terms and prices.
With Oracle Purchasing and Oracle iSupplier Portal, you can:
• Enable suppliers to query RFQs and manufacturing planning statuses.
• Enable suppliers to maintain their production capabilities in Oracle Purchasing.

Chapter 1 - Page 12
Suppliers

Suppliers
You must define a supplier before performing most activities within Oracle Purchasing and
Payables. Once defined you can:
• Optionally enter a recommended supplier on a requisition
• Use a supplier to issue a request for quotation
• Use that same supplier when you enter a quotation
• Use supplier information for purchase orders
• Receive goods or services from suppliers
• Return goods to suppliers
• Pay the supplier for the goods or services purchased
Set up suppliers to record information about individuals and companies you purchase goods
and services from. You can also enter employees you reimburse for expense reports. You can
designate supplier sites as pay sites, purchasing sites, RFQ only sites, or procurement card
sites. For example, for a single supplier, you can buy from several different sites and send
payments to several different sites. Most supplier information automatically defaults to all

Chapter 1 - Page 13
supplier sites to facilitate supplier site entry. However, you can override these defaults and
have unique information for each site.

Chapter 1 - Page 14
Purchase Orders

Purchase Orders
Oracle Purchasing supports four types of purchase orders: standard, blanket, contract and
planned. There are several methods that can be used to create purchase orders. You can
manually create purchase orders or search approved requisitions and add them to purchase
orders. Standard purchase orders can be imported through the Purchasing Documents Open
Interface in a status of Incomplete or Approved. You can automate purchase document
creation using the PO Create Documents workflow to automatically create a blanket purchase
agreement release or a standard purchase order upon approval of a requisition.
Once purchase orders are created, they may be submitted for approval. The approval process
checks to see if the submitter has sufficient authority to approve the purchase order. Once the
document is approved, it may be sent to your supplier using a variety of methods including:
printed document, EDI, fax, e-mail, Oracle iSupplier Portal and XML. Once the purchase
order or release is sent to your supplier, they are authorized to ship goods at the times and to
the locations that have been agreed upon.
Purchase documents may be created:
• By buyers using the AutoCreate window
• By importing them using the Purchasing Documents Open Interface

Chapter 1 - Page 15
• Automatically, by the Create Releases program (blanket releases)
• Automatically, by Workflow (blanket releases or standard purchase orders)
• Review all of your purchases with your suppliers to negotiate better discounts.
• Create purchase orders simply by entering a supplier and item details.
• Create standard purchase orders and blanket releases from both on-line and paper
requisitions.
• Create accurate and detailed accounting information so that you charge purchases to the
appropriate departments.
• Review the status and history of your purchase orders at any time for all the information
you need.
• Record supplier acceptances of your purchase orders. You always know whether your

suppliers have received and accepted your purchase order terms and conditions.
• Copy existing purchase orders.
• Manage global supplier agreements (blankets and contracts) from a centralized business
unit.
• Manage approved contractual terminology from a library of terms using Oracle
Procurement Contracts.

Chapter 1 - Page 16
Receiving

Receiving
Using Oracle Purchasing, you can process receipts from suppliers, receipts from other
warehouses or inventory organizations, in-transit shipments and receipts due to customer
returns. You can search for expected receipts based on a purchase order or a customer return
recorded in Oracle Order Management and then process them to their final destination whether
it is inventory, expense or shop floor. Oracle Purchasing lets you control the items you order
through receiving, inspection, transfer, and internal delivery. You can use these features to
indicate the quantity, quality, and internal delivery of the items you receive.
• Use routing controls at the organization, supplier, item, or order level to enforce material
movement through receiving. For example, you can require inspection for some items and
dock-to-stock receipt for others.
• Define receiving tolerances at the organization, supplier, item, and order level, with the
lowest level overriding previous levels. You can define tolerances for receipt quantity,
on-time delivery, and receiving location. You can assign looser tolerances to low-value
items. You can set enforcement options to ignore, warn the user, or reject transactions
that violate the tolerances.

Chapter 1 - Page 17
• Use blind receiving to improve accuracy in the receiving process. With this option, the
quantity due for each shipment does not show and quantity control tolerances are ignored.
• Use Express and Cascade receiving to process certain types of receipts more quickly.
• Use Advance Shipping Notices (ASNs) to save time in processing receipts.
• Record receipt of unordered items based on your item, supplier, or organization defaults.
For example, if your organization does not allow receipt of unordered items, you should
not be able to enter a receipt unless it can be matched to a purchase order shipment.
• Record the receipt of predefined substitute items.
• Record the receipt of services and labor.
With Oracle iProcurement, you can:
• Receive orders from your desktop, bypassing the need for receiving department
interaction.

Chapter 1 - Page 18
Invoicing

Invoicing
Once you’ve received goods or service from your supplier, you’ll also receive an invoice.
Using Oracle Payables you can record invoices in a number of different ways.
With Oracle Payables you can:
• Enter invoices manually, either individually or in batches.
• Use the Invoice Gateway for rapid, high-volume entry of standard invoices and credit
memos that are not complex and do not require extensive online validation.
• Automate invoice creation for periodic invoices using the Recurring Invoice functionality.
• Use Oracle iExpenses to enter employee expense reports using a web browser.
• Record credit card/procurement card invoices from transactions the credit card issuer
sends to you in a flat file.
• Record Oracle Project related expense reports.
• Import EDI invoices processed with the Oracle e-Commerce Gateway.
• Import lease invoices transferred from Oracle Property Manager.
• Match invoices to purchase orders to ensure you only pay what you’re supposed to be
paying for.

Chapter 1 - Page 19
Payment

Payment
Once invoices have been validated, they can be selected for payment. Oracle Payables provides
the information that you need to make effective payment decisions, stay in control of payments
to suppliers and employees, and keep your accounting records up-to-date so that you always
know your cash position. Oracle Payables handles every form of payment, including checks,
manual payments, wire transfers, EDI payments, bank drafts, and electronic funds transfers.
Oracle Payables is integrated with Oracle Cash Management to support automatic or manual
reconciliation of your payments with bank statements sent by the bank.
With Oracle Payables, you can:
• Ensure duplicate invoice payments never occur
• Pay only invoices that are due, and automatically take the maximum discount available
• Select invoices for payment using a wide variety of criteria
• Record stop payments
• Record void payments
• Review information on line on the status of every payment
• Process positive pay

Chapter 1 - Page 20
Overview of Oracle Application Integration

Overview of Application Integration
This slide attempts to capture the complex interaction of Oracle Applications resulting from the
Procure to Pay process. The key Oracle Applications that are integrated to perform this process
are described below.
Inventory
Order Management and Purchasing, as well as other Oracle applications can use items defined
in Oracle Inventory. If the item is designated as a planned item, demand can be generated in
the form of requisitions and sent to Oracle Purchasing where purchase orders or blanket
releases can be created to replenish inventory levels.
Order Management
Customer purchase orders can be recorded in Oracle Order Management. Goods are shipped to
customers as defined by the sales order. After goods are shipped, customer invoices are sent to
Oracle Receivables and inventory levels are updated. Any customers that are set up in Order
Management are shared with Receivables and vice versa.
Receivables
Oracle Receivables maintains information about invoices received from Oracle Order
Management and other sources. Invoices are sent to customers who respond by sending

Chapter 1 - Page 21
payments. You can use Receivables to record receipts against customer accounts.
Receivables, revenue and cash receipts are interfaced to Oracle General Ledger.
Purchasing
Oracle Purchasing captures accounting information on requisitions and purchase orders.
Purchase orders are sent to suppliers who respond by delivering goods or services and sending
invoices that are processed in Oracle Payables. During the accounting period, accruals for
goods set to accrue a liability on receipt are sent to Oracle General Ledger. At the end of the
accounting period, accruals for goods and services set to accrue a liability at period end can be
sent to General Ledger. Any suppliers set up in Purchasing are shared with Payables and vice
versa.
Payables
Supplier invoices are entered into Oracle Payables and if appropriate, matched to purchase
orders in Oracle Purchasing. During the matching process, the invoice distribution is copied

from the purchase order (in the case of an expense) or the appropriate liability account (in the
case of an inventory item). Payables, expenses and payments are interfaced to Oracle General
Ledger. Invoices for asset purchases can be interfaced to Oracle Assets.
Assets
Assets from Payables and other sources are maintained in Oracle Assets. Assets are added,
processed, depreciated and eventually retired. At the end of each asset period, accounting
information is interfaced directly to Oracle General Ledger.
General Ledger
Oracle General Ledger receives accounting information from many Oracle applications. Once
accounting information is imported, journals can be posted and account balances updated.
When implementing Oracle Applications, creating a set of books consisting of an accounting
calendar, currency and chart of accounts is one of the first steps that must be completed before
setting up other applications.

Chapter 1 - Page 22
Summary

Chapter 1 - Page 23

Chapter 1 - Page 24
Understanding Oracle
iProcurement
Chapter 2
Understanding Oracle iProcurement

Chapter 2 - Page 1

Chapter 2 - Page 2

Chapter 2 - Page 3
Objectives

Chapter 2 - Page 4
Procure to Pay: Oracle iProcurement

Procure to Pay: Oracle iProcurement
The Oracle iProcurement functionality provides the essentials for the ordering portion of the
procurement process. This includes catalog content management, requisitioning, purchase
order creation, and receiving orders.

Chapter 2 - Page 5
Agenda

Chapter 2 - Page 6
Oracle Advanced Procurement

Oracle Advanced Procurement
Oracle Advanced Procurement automates purchasing to make buyers more productive,
improves management of your supply base and adapts to any procurement process. As the
heart of the Oracle Advanced Procurement suite, Oracle Purchasing provides a rich store of
policy and supplier information, a robust workbench for buying professionals, and consolidated
visibility into all spending. Oracle Purchasing turns demand into orders with the least possible
manual work. Configurable automation executes routine transactions without intervention,
making buyers more productive while enforcing compliance at every step. So procurement
professionals spend less time processing paper, and more time discovering and exploiting new
savings opportunities.
Web-Shopping Interface Ensures Rapid Deployment and Adoption
Oracle iProcurement lets you control spending by all employees because it is easy for you to
implement and for them to use. Oracle iProcurement gives employees an intuitive web-
shopping interface that is instantly familiar to anyone who has shopped online. Powerful search
features and logically grouped online “stores” lead users to the products and services they
need. Requesters can place and track orders from any web browser. This web architecture also
allows rapid deployment to every employee because there is no desktop software to install.

Chapter 2 - Page 7
Your employees have immediate access to the 'iProcurement' system and an interface they can
use right away.
Content Control Guides User Choice
With Oracle iProcurement, Purchasing departments completely control the products, services
and views that employees see; based on organization, responsibilities, and more. The content
can be easily loaded into iProcurement and you can use your existing supplier agreements.
Requesters find the items using a configurable category structure or employ the powerful
advanced search capabilities. You can provide rich information on the items so employees
make informed decisions. Suppliers can also manage content on your behalf. Oracle
iProcurement allows users to punch-out to supplier-hosted sites, returning for checkout and
approval. Additionally, iProcurement’s unique Transparent Punch-Out even allows users to
access content from external sites without ever leaving the familiar iProcurement interface. By
providing flexible options for user content, Oracle iProcurement gives you unparalleled ability
to guide employees to make compliant purchasing choices.

Chapter 2 - Page 8
Oracle iProcurement In E-Business

Oracle iProcurement In E-Business
This diagram attempts to summarize the positioning of Oracle iProcurement relative to
supplier content and some of the closely integrated Oracle Applications.

Chapter 2 - Page 9
Key Oracle iProcurement Capabilities

Key Oracle iProcurement Capabilities
The key function of the Oracle iProcurement solution is to provide robust catalog content and a
simplified approach to creating requisitions to order from that catalog.

Chapter 2 - Page 10
E-Business Suite Integration

E-Business Suite Integration
Oracle Payables
• Accounting for matched purchase orders
• Suppliers
• Procurement cards
• Purchase orders
Oracle Purchasing
• Blanket purchase agreements
• Contract purchase agreements
• Quotations
• Approved supplier lists
• Document controls and defaults
Oracle General Ledger
• Ledgers
• Exchange rates

Chapter 2 - Page 11
• Accounting flexfield
• Currency
• Charge account combinations
Oracle Workflow
• Account Generator
• Approval process
• Automatic document creation
• Notifications
Oracle Human Resources
• Employees (requestors and buyers)
• Organizations (receiving)
• Locations

• Hierarchies (approval)
Oracle eCommerce and XML Gateway
• Electronic document transmission
• Code conversions
Oracle Projects
• Project and task tracking
• Expenditure type and expenditure organization
• Award id tracking

Chapter 2 - Page 12
Procurement Suite Integration

Procurement Suite Integration
Oracle Purchasing
• Professional procurement management tool
• Complete control over document routing and approval
• Complete control over purchase order creation
• Complete control over receiving
Oracle Services Procurement
• Contingent labor procurement
• Integrates Oracle Time & Labor (OTL) for payment through Oracle Payables
Oracle DBI for Procurement
• Daily Business Intelligence reports for Oracle Procurement
• Role-based performance overviews
• Interactive summarization of buyer and supplier performance
Oracle iSupplier Portal (iSP)
• Record purchase order acknowledgments

Chapter 2 - Page 13
• Reschedule Promised-By dates
• View purchase order and revision history
• View RFQs
• View expected deliveries
• Create and view ASNs and ASBNs
• View receipts, returns and overdue receipts
• Set processing lead time, minimum order quantities and fixed lot multiples
• View invoice and payment information
Oracle Sourcing
• Collaborative RFQs
• Collaborative RFIs
• Negotiate all aspects of the transaction

• Auctions
Oracle Supplier Network
• Services to electronically enable suppliers
• Electronic message transformation and routing services through an Internet-based hub
• Self-service trading partner registration

Chapter 2 - Page 14
Agenda

Chapter 2 - Page 15
Key Functionality of Oracle iProcurement

Key Functionality of Oracle iProcurement
Catalog Management
Purchasable content is made available for shopping from internal or external sources based on
the organization’s needs.
Shopping
Process where users search for, compare, and select items that they need to purchase. Users
can search the internal catalog, lists, table of contents, and categories. They can also punch out
to either supplier-hosted or marketplace-hosted catalogs to shop. Once found, the items can be
quickly added to a shopping cart.
Checkout and submit
Requestors enter quantities, billing information, and delivery information in the shopping cart
for their order. Their cart contents are converted to a requisition and submitted for approval.
Approval and order creation
Workflow routes requisitions to the correct approvers based on predefined business rules.
Approved requisitions are used to create purchase orders and blanket purchase agreement
releases. Additionally, approved requisitions can be placed on Sourcing RFQs and auctions.

Chapter 2 - Page 16
Receive order
Process where users specify information about the delivery of their order.

Chapter 2 - Page 17
Oracle iProcurement Content Management

These are the sources of loading and maintaining content in the Oracle iProcurement internal
catalog (buyer-hosted). This catalog is different from the supplier item catalog in Oracle
Purchasing.
Purchasing
Identify and load data from Oracle Purchasing.
Supplier
Bulk load data from other sources using the iProcurement Catalog Administrator responsibility
and update online using iSupplier Portal.
Schema
Manage catalog structure using XML or the iProcurement Catalog Administrator
responsibility.
Oracle iProcurement
Author content online spreadsheet upload.

Chapter 2 - Page 18
Content Zones

Content Zones
Content zones are the basic containers that hold your shopping content. You place different
types of items in different content zones. Content zones can be locally hosted in Oracle
Purchasing, supplier-hosted, or hosted in iProcurement.

Chapter 2 - Page 19
Stores

Stores
Stores allow you to organize your catalogs. Stores consist of one or more content zones.
Stores are what your users search when looking for items. Stores can be configured by
administrators to organize by:
•Usage
•Source
•Relevance

Chapter 2 - Page 20
Shopping

Shopping
Shopping describes the process of finding the correct items for your order and adding them to
your shopping cart. Depending on the procurement needs of your requestors and the buying
policies of your organization, the setup can be simple or complex.
My Favorites
If requestors order the same items regularly they can develop a Favorites List by selecting an
item from the search results and clicking the Add to Favorites button. They can then use their
My Favorites list as the basis for additional Favorites lists they create. Item information in the
Favorites List is not updated when the original item is updated in the Oracle iProcurement
internal catalog.
Shopping Lists
Shopping lists are requisition templates that are created in Oracle Purchasing and then
extracted into iProcurement. An example of a shopping list is an office supplies list. The list
could contain the standard set of office supplies a new hire would need. See “Requisitions -
Public Lists” in the Oracle iProcurement Implementation Guide.

Chapter 2 - Page 21
Search
Searching in Oracle iProcurement makes use of the Context or interMedia features of the
Oracle database. Requesters can search for item names, item numbers, supplier names, and
other criteria available in your internal catalog. Review the Managing iProcurement Catalog
Content course for more details on what items are available in the internal catalog. Also see
“Creating and Maintaining Local Content” in the Oracle iProcurement Implementation Guide.
Browse Categories
Oracle iProcurement catalog management enables the catalog administrator to create a table of
contents by item category. For example, you may want to order a pencil. By using the Browse
Category feature you would first select Office Supplies and then Pencils to see the selections
available. Review the Managing iProcurement Catalog Content course for more details on
creating a table of contents.
Non-Catalog

There may be occasions when an item is not listed in either the internal catalog or in a supplier-
hosted or marketplace-hosted catalog. You can order an item that is not listed in your catalog
by using the Create Non-Catalog Request page. Non-Catalog items can include services or
specialty items. You can also create non-catalog templates by creating Smart Forms in
iProcurement Catalog Administration.
External Marketplace
Users may punchout to a supplier-hosted or marketplace-hosted Web site to search for items
and bring them back into Oracle iProcurement to be used on a requisition. Review the
Managing iProcurement Catalog Content course for more details on punchout.

Chapter 2 - Page 22
Overview of Checkout

Overview of Checkout
Use the checkout process to complete necessary requisition information, copy items from your
shopping cart to a requisition, and submit the requisition for approval.
Requisition information
Requester is prompted to enter all the relevant delivery and billing information required to
process a requisition. Delivery and billing information initially defaults from the user’s profile.
Select approvers
Requester then selects the approvers, adds notes, and adds attachments as required.
Note: After a requisition is saved in Oracle iProcurement, it is inserted directly into the same
tables Oracle Purchasing uses to process requisitions.

Chapter 2 - Page 23
Approval and Document Creation

Approval and Document Creation
After the requisition is submitted, it passes through the Requisition Approval workflow to pass
the business rules set up by the company. These rules are set up in Oracle Purchasing.
AutoCreate
Manual Oracle Purchasing process where approved requisitions are picked out of the
requisition pool by buyers, and then placed onto either RFQ’s, purchase orders or releases.
Requisition lines can also be placed on Sourcing RFQs or auctions.
Create Documents Workflow
Using a source document, this workflow automatically creates a purchase document from an
approved requisition. If the source is a blanket purchase agreement, then a purchase order
release is created. If the source is a contract purchase agreement, then a standard purchase
order is created. An approved supplier list is necessary if you want to use blanket purchase
agreements as source documents and you are using system items. If you are not using a system
item, but you have a supplier item number, then no ASL is required

Chapter 2 - Page 24
Overview of Receiving

Overview of Receiving
The approved order is then transmitted to the supplier, the supplier ships the items, and the
requestor then acknowledges receipt of the items.
Order Transmission
The approved order is transmitted to the supplier by mail or facsimile, e-mail, electronic data
interchange (EDI), or extensible markup language (XML) as set up for the supplier in Oracle
Purchasing. The approved order is also available to the supplier through iSupplier Portal.
Shipment Notification
Order is shipped and supplier provides notification of shipment by mail or facsimile, EDI, or
Oracle iSupplier Portal.
Receipt Confirmation
Requestor confirms receipt of order, corrections of receipts, or returns at desktop using Oracle
iProcurement. Receipt can be done at time of receipt or by response to a confirm receipt
notification.

Chapter 2 - Page 25
Center-Led Procurement

Center-Led Procurement
In many enterprises the requisitioning, sourcing, ordering, and payment activities are all
performed in the context of a single business unit and transactions do not cross business unit
boundaries. The Oracle Procurement Suite supports that but can also free enterprises to
perform their procurement activities irrespective of business unit boundaries. Requisitions that
are raised in one business unit can reference source documents and be placed on purchase
orders in another business unit taking advantage of supplier negotiations.
The purpose of using a shared service center is for the enterprise to not only source globally
but also be able to identify business unit specific procurement practices. Within Oracle
Purchasing this is done by enabling the global agreements only for the business units that need
to use them.

Chapter 2 - Page 26
Agenda

Chapter 2 - Page 27
Oracle iProcurement Shopping Data Flow

Oracle iProcurement Shopping Data Flow
iProcurement
Users search for items using the internal catalog and/or punchouts to external suppliers or
marketplaces. All items selected are placed in the user’s shopping cart.
Internal Catalog
Content can be uploaded from:
• Tab-delimited text (spreadsheet) file
• XML file
Content can come from item and category extraction from Oracle Purchasing.
Punchout to Marketplace (external catalogs)
Shopping in catalogs hosted by third-party sources or by the supplier.
Oracle Purchasing
Contributes defaults to the requisition:
• Buyer information
• Document defaults

Chapter 2 - Page 28
Oracle Payables
Contributes defaults to the requisition either directly or through Oracle Purchasing:
• Supplier information
E-Business Tax
Contributes defaults to the requisition
• Tax information

Chapter 2 - Page 29
Oracle iProcurement Submit Request Data Flow

Oracle iProcurement Submit Request Data Flow
Once the shopping cart is complete, it is processed:
iProcurement
The shopping cart contents become requisition lines during checkout and are submitted for
approval.
Purchasing
The iProcurement requisition becomes part of the requisition pool awaiting action by workflow
or AutoCreate.
Workflow
• PO Requisition Approval workflow routes the requisition for approval.
• PO Create Documents workflow creates a purchase order or release from the approved
requisition.
• PO Approval workflow routes the purchase order for approval.
e-Commerce Gateway
• Outbound 850
• Outbound 860

Chapter 2 - Page 30
XML Gateway
• New Purchase Order (standard or release)

Chapter 2 - Page 31
Agenda

Chapter 2 - Page 32
Oracle iProcurement Setup Overview

Oracle iProcurement Setup Overview
Although some of the setup steps overlap, there are three distinct business process concerns
involved in Oracle iProcurement setup:
• Oracle Applications Setup (refer to the Oracle Purchasing User’s Guide)
• Oracle Purchasing Setup (refer to the Oracle Purchasing User’s Guide)
• Oracle iProcurement Setup (refer to the Oracle iProcurement Implementation Guide)

Chapter 2 - Page 33
Oracle iProcurement Setup Steps

Oracle iProcurement Setup Steps
This is a high level overview. Details will be discussed in each section of this course and a
summary is provided in the setup section. Always check Metalink for the latest information
before beginning your implementation.

Chapter 2 - Page 34
Practice - Create a New Employee and User
Overview
Part of initial set up for Oracle Purchasing employees. In this practice, you will create a new
employee and a new user for yourself to be used during the remaining practice sessions of this
course. Do not be too concerned at this point about what the fields mean, as we will be
discussing most of them in depth during the remainder of the course.
Assumptions
• Replace XX with your terminal number or initials.

• You have prior experience using Oracle Applications or have completed an introductory
Oracle Applications course.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Sign on to the Personal Home Page
− User = operations
− Password = welcome
Define an Employee
Responsibility = Human Resources, Vision Enterprises
Define yourself as an employee with account details as shown in steps 4-6 below.
Add a New User
Responsibility = System Administrator, Vision Enterprises
Define yourself as an user with account details as shown in steps 9 & 10 below.

Chapter 2 - Page 35
Solution - Create A New Employee and User
Sign on to the Personal Home Page
− User = operations
− Password = welcome
Define an Employee
Responsibility = Human Resources, Vision Enterprises
1. Navigate to the People window
• (N) People > Enter and Maintain

2. (B) New
− Last = Your last name
− First = Your first name
− Gender = Choose a gender
− Action = Create Employment
− Person Type = Employee
− Social Security = Enter any 9 digit number (xxx-xx-xxxx)
Note: If you get a message indicating that the social security number is a duplicate accept it.
For the purposes of the exercise it doesn’t matter if it is a duplicate it or not.
− Birthday = Enter a birthday (dd-mmm-yyyy)
3. (I) Save.

Chapter 2 - Page 36
4. (B) Assignment. Create an assignment using the following information:
Note: If necessary, click Correction, then Cancel in the People Group window that opens
while you are making your entries. Also, during position entry, enter Yes to the Decision
window if it appears.
Field Value
Organization Vision Operations
Job MGR500.Manager
Position MM400.MATERIALS MANAGER
Location M1- Seattle Mfg
5. (T) Supervisor
− Name = Brown, Ms. Casey
6. (T) Purchase Order Information

− Set of Books = Vision Operations (USA)
− Default Expense Account = 01-110-7740-0000-000
Note: Click Cancel if the Alias window appears and enter the account number manually.

Chapter 2 - Page 37
7. (I) Save.
Note: Click Cancel in the window that opens regarding location.
8. Close windows until you are back at the Navigator.
Add a New User
Responsibility = System Administrator, Vision Enterprises
9. Navigate to the Define Users window
• (N) Security > User > Define

− User Name = XXUSER (where XX is your unique ID)
− Password = welcome1 (tab, re-enter password to verify). When you initially

signon, you will be prompted to change your password. At that time, change it
to welcome.
− Person = The employee you created
10. Add the following responsibilities to your new username
Responsibility Security Group

Purchasing, Vision Operations (USA) Standard
Payables, Vision Operations (USA) Standard
Human Resources, Vision Enterprises Standard
Inventory, Vision Operations (USA) Standard
iProcurement Standard
iProcurement Catalog Administration Standard
Workflow Standard
System Administrator Standard

Chapter 2 - Page 38
11. (I) Save
12. Exit Oracle applications and sign back in with your newly created User name.

Chapter 2 - Page 39
Practice - Set Yourself Up As a Buyer
Overview
Part of initial set up for Purchasing employees. In this exercise, you will set yourself up as a
buyer in order to complete later practices.
Assumptions

• Logon to the system using the XXUSER you created earlier.
Tasks
Responsibility = Purchasing, Vision Operations
Set yourself up as a buyer in the define Buyers window.

Chapter 2 - Page 40
Practice - Set Yourself Up As a Buyer
1. Navigate to the Buyers definition window
• (N) Setup > Personnel > Buyers
2. Open a new buyer entry by clicking Add Buyer.
3. Set yourself up as a buyer with a default Ship-To of M1 – Seattle Mfg

.
4. Save your entry.
5. (H) Home.

Chapter 2 - Page 41
Guided Demonstration - Run the Fill Employee Hierarchy Process
Overview
The instructor will run the Fill Employee Hierarchy process to add the person you just created to
the purchasing hierarchy. This is necessary for approvals to work correctly.
Assumptions

Tasks
Run the Fill Employee Hierarchy process
1. Navigate to the request submission window
• (N) Reports > Run

− Name = Fill Employee Hierarchy
− Operating Unit = Vision Operations
2. Monitor the request and ensure it completes successfully
Note: The Fill Employee Hierarchy adds our position and people assigned the position to
the position hierarchy. This process is not necessary for an Employee/Supervisor hierarchy.
Both types will be discussed during this course.

Chapter 2 - Page 42
Summary

Chapter 2 - Page 43

Chapter 2 - Page 44
Oracle iProcurement Content
Management
Chapter 3

Chapter 3 - Page 1

Chapter 3 - Page 2

Chapter 3 - Page 3
Objectives

Chapter 3 - Page 4
Procurement Process: Oracle iProcurement

Procurement Process: Oracle iProcurement Catalogs
The Oracle iProcurement functionality provides the essentials for the ordering portion of the
procurement process. In this section we will discuss the catalog content management portion
of the process.

Chapter 3 - Page 5
Agenda

Chapter 3 - Page 6
What Are iProcurement Catalogs?

Catalog
A catalog is a collection or grouping of items from which you might search and select a
particular item for purchasing.

Chapter 3 - Page 7
Why Use Catalogs?

Chapter 3 - Page 8
What is an iProcurement Store?

What is an iProcurement Store?
As organizations have expanded their use of Oracle iProcurement to additional and distinct key
spend areas, it has become increasingly important to organize content in a way that provides
easy access to a more specific range of goods and services. Using stores, organizations can
define an intuitive collection of content areas. For instance, Oracle iProcurement could be
configured to have a Promotional Items store, an IT store, a Temporary Labor store, a
Chemicals store, a Power Equipment store, and an Office Supplies store. Within a store, items
are grouped into content zones to allow access control.

Chapter 3 - Page 9
Where Does the Catalog Content Come From?

Where Does the Catalog Content Come From?
Catalog content for Oracle iProcurement shopping can come from both internal and external
sources.
Note: It is important to keep in mind that the Oracle iProcurement shopper is intended to only
see the online stores that you create as a homogenous catalog. Behind the scenes the content is
actually loaded into Oracle Purchasing blanket purchase agreements and then made available
to shoppers in an easy to navigate environment. Content can also come from marketplace
and/or supplier punchouts as well.

Chapter 3 - Page 10

You don't define or setup catalogs in Oracle iProcurement. Instead you define content zones.
Catalog Administrators partition local catalog content into local content zones, define punchout
or transparent punchout content zones, and then assign these content zones to stores. The
combination of content zones that you assign to a Store determines what catalog content your
users see. This slide indicates sources and uses of content.
Content Type
• Local: Locally hosted catalogs maintained by the buying organization. Provides maximum
control over content and a requester’s access to that content.
• Supplier-hosted: A supplier organization provides access to their externally hosted
catalogs.
• Marketplace-hosted: A third party organization hosts multiple supplier’s catalogs.
Commodities
• Direct material: mass-produced mechanical parts; products with pre-negotiated or stable
prices; strategic maintenance, repair, and operation (MRO) items (such as packing
material).

Chapter 3 - Page 11
• Configured products: products requiring high degree of configuration, such as computer
hardware or office furniture; specialized services, such as printing or media services;
products with fluctuating prices; extremely large or specialized catalogs, such as chemical
supplies.
• Indirect material: office supplies; standard MRO items; products with unstable pricing.

Chapter 3 - Page 12
Local or Buyer-Hosted Content

Local or Buyer-Hosted Content
This approach is best suited for direct material (example: packing material) and is also referred
to as a local content or internal catalog. This type of catalog provides the most local control of
content and access to that content.
Buyer-hosted content comes from following sources:
• Upload: Supplier creates an XML, cXML, CIFF or spreadsheet (tab delimited text) file,
and the buyer uploads the file using the eContent Manager.

Chapter 3 - Page 13
External or Supplier-Hosted Content

External or Supplier-Hosted Content
This approach is best suited for products requiring a high degree of configuration (example:
office furniture).
Oracle iProcurement refers to this as a punchout catalog. A requester can:
• Click a link on Shopping or Search pages that takes requester directly to the supplier’s
Web store.
• Shop for and select items in the Web store.
• Return with chosen items to iProcurement.
• Complete checkout process in iProcurement for the items
Setup is required by both the catalog administrator in iProcurement and the supplier to
implement a punchout. More information will be provided in the Set Up Remote Content topic.
Examples of suppliers Oracle iProcurement Customers Link To:
• Barnes & Noble
• Dun & Bradstreet
• Compaq
• Corporate Express

Chapter 3 - Page 14
• Grainger
• Office Depot

Chapter 3 - Page 15
External Marketplace-Hosted Content

External Marketplace-Hosted Content
Best suited for indirect material (example: office supplies).
Marketplaces (also known as hubs or third-party hosting services) offer:
• A central repository to which suppliers load catalog items and files.
• One-stop shopping for buyers who register or shop directly on the hub.
Marketplace product examples:
• Oracle Exchange
• Ariba Marketplace
• Commerce One MarketSite
• i2 TradeMatrix Procurement

Chapter 3 - Page 16
Choosing Content

Choosing Content
The first and foremost question has to be what kinds of items will your requestors typically be
expected to order. See the earlier slide titled Oracle iProcurement Catalog Content
Management for more details. Some types of items can only be ordered from a supplier-hosted
catalog because of configuration constraints.
Local catalogs offer maximum control, which of course also means your company does most
of the work.

Chapter 3 - Page 17
Requirements of Local Catalogs

Requirements of Local Catalogs (Local Content)
References:
• Oracle iProcurement Implementation Guide
• Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout

Chapter 3 - Page 18
Requirements of Supplier-Hosted Content

Requirements of Supplier-Hosted Content
References:

Chapter 3 - Page 19
Requirements of Marketplace-Hosted Content

Requirements of Marketplace-Hosted Content
If you are using Oracle Exchange as your marketplace also see Oracle Exchange and Oracle
Sourcing System Operator Implementation Guide and Oracle Exchange XML Transaction
Delivery Guide for Marketplace Exchange.
References:

Chapter 3 - Page 20
Utilization of Catalog Content

Utilization of Content
Another way of describing catalogs is in terms of how Oracle iProcurement requesters access
the content.
Oracle iProcurement supports the following types of catalogs:
• Local content
• Punchout content hosted by a supplier or marketplace
- Standard punchout where you shop on remote store
- Transparent punchout where your search returns items to iProcurement
• Informational content (special variation of local catalog)

Chapter 3 - Page 21
Control Content Using Content Zones

Control Content Using Content Zones
So far we have only discussed the actual content to be included in the shopping “catalog.” This
content must be organized and access controlled by an administrator.
Catalog Administrators can partition local catalog content into local content zones. Local
content zones act as containers for subsets of local catalog content and can be assigned to
Stores.

Chapter 3 - Page 22
Stores: Pulling It All Together…

Stores: Pulling It All Together…
Stores can be configured to include a combination of local catalogs (content zones) , regular
punchout catalogs, transparent punchout catalogs and even informational catalogs. To ensure
stores are easily configurable by administrators, Oracle iProcurement supports segmentation of
local content into unique supplier catalogs.
Punchout catalogs: Requesters can punch out or link directly to a supplier’s Web store
(supplier-hosted catalog) or a marketplace Web store (marketplace-hosted catalog). After
selecting items for purchase, they return to Oracle iProcurement and proceed through the
checkout process.
Transparent Punchout catalogs: Requesters can search for items on an external site
(supplier-hosted or marketplace-hosted catalog) without leaving Oracle iProcurement. From
the Search Results page, requesters add the items to their cart and proceed through the
checkout process.
Non-Catalog Requests
Non-catalog requests can be made using non-catalog request templates and/or Smart Forms.

Chapter 3 - Page 23
iProcurement Catalog Administration

At the highest level, there are two areas that define the catalog, the catalog content and the
catalog schema. The content is what the requester sees. The schema controls the structure and
ultimately the usability of the content.
The iProcurement Catalog Administration home page provides all the tools you need to
manage both the content and schema in one easy to use work center.

Chapter 3 - Page 24
Agenda

Chapter 3 - Page 25
Creating Local Content

Creating Local Content
This section covers the two ways of creating local buyer-hosted content:
• Uploads (bulk loads) to iProcurement from external sources
• Manual entry in Oracle Applications
You can use either or both of these methods to maintain local content.

Chapter 3 - Page 26
Oracle iProcurement Content Management Review

Oracle iProcurement Content Management Review
Content Type
A local catalog is an internally hosted catalog maintained by the buying organization and
suppliers. Using a local catalog generally provides maximum control over content and a
requester’s access to that content. Supplier-hosted is content maintained and stored at the
supplier. Marketplace-hosted is stored by third-party providers.
Suggested Commodities
material).

Chapter 3 - Page 27
Oracle Content Utilization Types

Oracle Content Utilization Types Review
These are the official catalog (or content) “types” as identified in the Oracle iProcurement
Implementation and Administration Guide and the Oracle iProcurement Help. It is important to
understand the distinction between how catalog content is stored and how it is delivered to the
Oracle iProcurement requester.

Chapter 3 - Page 28
Local Content

Local Content
Local or buyer-hosted content is hosted, as the name suggests, by the purchasing organization.
A single catalog is built with product and services information from multiple suppliers. It is
used by all purchasing staff and has a common user interface, no matter which supplier the
product or service is ultimately obtained from. Content can be:
•Loaded or directly entered online from Oracle Applications (Purchasing, iProcurement,
Sourcing, Inventory)
•Uploaded from any third party content provider.
•Updated directly by suppliers using iSupplier Portal (requires Buyer approval).

Chapter 3 - Page 29
E-Business Suite Local Content

E-Business Suite Local Content
Oracle E-Business suite categories and items can be easily included in the iProcurement
catalog.
Web-enabled Purchasing categories
In Oracle Purchasing or Inventory, enable the purchasing category code for iProcurement.
Tip: If you are going to use many categories from Oracle Applications, there is an open
interface for categories in Oracle Inventory. Detailed information on this Oracle Inventory
interface is available from the Oracle Manufacturing APIs and Open Interfaces Manual.
References:
See the Oracle iProcurement Implementation Guide for additional discussion.

Chapter 3 - Page 30
Practice - Create a Purchasing Category
Overview
In this practice you will create a purchasing category to be used later when creating purchasing
documents.
Assumptions

Tasks
Add Key Values for Purchasing Category Combinations
Add XX to the PO Item Category value set.
Create Purchasing Categories
Create categories for XX.COMPUTER. XX.SUPPLIES, and XX.MISC
Assign the Categories to a Category Set
Assign the categories you created to the Purchasing category set.

Chapter 3 - Page 31
Solution - Create a Purchasing Category
Add Key Values for Purchasing Category Combinations
Note: In most cases creating a Purchasing category would only require the steps below for
creating category codes and then assigning them to the Purchasing category set. Since the
Flexfields in the Oracle Vision database have dependent value sets due to other product
requirements, we have to do a little extra work.
1. Navigate to the Key Segment Values window

• (N) Setup > Flexfields > Key > Values
2. Add XX to the PO Item Category value set
• Select Value Set, enter PO Item Category as Name, and click Find.
• Place your cursor in the first row of the Values, Effective tabbed region. If no open rows
are visible, click (I) New.
• Enter XX in the Value field, and XX in the Description field.

Chapter 3 - Page 32
• (I) Save. Close the form and click OK in the Compile note when it appears.
3. Add COMPUTER, SUPPLIES, and MISC to the Commodity value set as dependent values
to XX.
• Select Value Set.
• Name = Commodity.
• Independent Value = XX
• (B) Find

Chapter 3 - Page 33
• Place your cursor in the first row of the Values, Effective tabbed region. If no open rows
are visible, click New to open a new row.
• Enter COMPUTER in the Value field, and XX Computer in the Description field.
• If no open rows are visible, click New.
• Enter SUPPLIES in the Value field, and XX Supplies in the Description field.
• Enter MISC in the Value field, and XX Miscellaneous in the Description field.

Chapter 3 - Page 34
• (I) Save. Close the form and click OK in the Compile note when it appears.
Create Purchasing Categories
4. Navigate to the Categories window
• (N) Setup > Items > Categories > Category Codes
5. (B) New
6. Create categories according to the following table:
Structure Name Category Description Supplier?

PO Item Category XX.COMPUTER XXComputer Purchases Y
PO Item Category XX.SUPPLIES XXOffice Supplies Y
PO Item Category XX.MISC XXMiscellaneous Purchases Y

Chapter 3 - Page 35
7. Save
Assign the Categories to a Category Set
8. Navigate to the Category Sets window
• (N) Setup > Items > Categories > Category Sets
• Select the M1 Seattle Manufacturing organization if asked.
9. Query the Purchasing category set.
• PF11
• Flex structure = PO Item Category)
• Ctrl + PF11
• Verify the Name is Purchasing. (If it is not, use the up and down arrows to cycle through
the options until you find Purchasing).
10. Add your categories to the Categories region.
• Insert the cursor in the line region.
• (I) Add line.
• Add new rows as needed to add XX.COMPUTER and XX.SUPPLIES, and XX.MISC

Chapter 3 - Page 36
11. Save.
12. Close windows until you are back at the Navigator

Chapter 3 - Page 37
Practice - Create Items
Overview
In this practice you will create an Oracle Inventory item that is iProcurement enabled, and assign
your Purchasing category to the item.
Assumptions

Tasks
Create an Item
Assign your Category to your Item
Create Inventory Organization Assignments

Chapter 3 - Page 38
Solution – Create Items
Create an Item
1. Navigate to the Master Items window
• Select Vision Operations as the organization.
• (N) Items > Master Items (V1)
2. Enter your item

− Item = XXBUSINESS CARDS
− Description = XXBusiness Cards
− Primary = Box
3. (T) Purchasing
− Purchased = Checked
− Purchasable = Checked
− List Price = 25.00

Chapter 3 - Page 39
5. Save your item
Assign your Category to your Item
6. (M) Tools > Categories

− Category = XX.SUPPLIES (Replace MISC.MISC)

Chapter 3 - Page 40
7. Save your work
Create Inventory Organization Assignments
8. (M) Tools > Organization Assignment
9. Enable your item in inventory organizations according to the following table:
Org Name Primary UOM Enabled

M1 Seattle Manufacturing Box Checked
M2 Boston Manufacturing Box Checked

Chapter 3 - Page 41
10. Save your selections and return to the Navigator.

Chapter 3 - Page 42

Chapter 3 - Page 43
Uploading Local Content

The Upload process uses CIF, cXML, XML, or spreadsheet (tab-delimited text) file that
supplier creates and buyer uploads to add large amounts of data to the internal catalog. If only
small amounts of data need to be added or maintained, you can use the online authoring
feature.
You can use uploading to add and maintain buyer-hosted content. For example, uploaded items
can augment items already entered into the iProcurement catalog.
• You can upload items in addition to items you’ve entered.
• You can modify items using your upload file. Basically, uploading lets you specify more
information about items than the item master or other sources may allow.

Chapter 3 - Page 44
Before Uploading Content

Before Uploading Content
If you are using categories from Oracle Purchasing, keep in mind that the existing category
structure will be reproduced in the Oracle iProcurement catalog. If you are going to create a
category structure in Oracle iProcurement, you’ll need to create or load these categories using
schema editing or uploading, and then map these categories to Oracle Purchasing categories.

Chapter 3 - Page 45
Upload Content: Resource Files

Upload Content: Resource Files
iProcurement Catalog Administration Responsibility
(N) iProcurement Catalog Administration Home Page > (T) Agreements > (L) Summary > (B)
Upload > (B) Download Resources

Chapter 3 - Page 46
Item Content That You Upload

Item Content That You Upload
This slide details the minimum information you would be expected to include in your upload
file for a new item. For more complete details see the Readme files available from the
Download Resources page in the iProcurement Catalog Administration Manager.

Chapter 3 - Page 47

(N) iProcurement Catalog Administration > (T) Agreements > Upload
The supplier (or buyer) creates a content file, and the buyer uploads the file using the
iProcurement Catalog Administration.
References:
See the Oracle iProcurement Implementation Guide for more catalog upload discussion.

Chapter 3 - Page 48
Content Upload And Document Types

Content Upload And Document Types
When using the content upload feature you must specify the document to which your content is going to be added.
The three document types are specified in the above slide. The actual upload is performed in different places
within iProcurement depending on which document type you are updating.
Global Blanket Purchase Agreement
1. (N) iProcurement Catalog Administration home page
2. (T) Agreement
3. Search for the global agreement you wish to upload items to, select it, and open it for update.
4. Select Via Upload from the Add Lines list and click Go.
5. Identify your upload file and related information.
6. (B) Submit
Blanket Purchase Agreement or Quotation
1. (N) iProcurement Catalog Administration home page
2. (T) Agreement
3. (L) Upload
4. On the View Document Upload History page click Upload.
5. Select your document type, number, upload file, and related information.
6. (B) Submit

Chapter 3 - Page 49
Automatically Uploading Shopping Categories

Automatically Uploading Shopping Categories
The category you specify for the item doesn’t have to already exist in the catalog if this profile
option is set to Yes; the loader process will add both the item and the new shopping category.
Otherwise, you must use existing categories. See the readme accompanying the upload
spreadsheet for detailed information on how category and shopping categories are used and
derived.

Chapter 3 - Page 50
Price Lists That You Upload

Chapter 3 - Page 51
Online Content Authoring Flow

Online Content Authoring Flow
Online catalog authoring complements the batch upload process. While batch upload is
optimized for large data uploads, online authoring is designed for the catalog administrator to
make small and quick updates to catalog content. These updates are made directly to the
catalog using the Oracle iProcurement Catalog Administration Web interface.

Chapter 3 - Page 52
Upload Content Authoring Flow

Upload Content Authoring Flow
You can download the example spreadsheet template and readme files. Using these resources,
you can upload multiple items to your catalog.
1. Create and save a global purchase agreement.
2. Access the agreement.
3. Download the zip file containing the upload resources (template, lists, and readme file).
4. Complete the spreadsheet. Remember that for each item you upload, at a minimum you
must include the
- Action (ADD, SYNC, etc)
- Description
- Purchasing Category (if unspecified, the Purchasing default category is used)
- Price
- UOM
- Currency
5. Upload your completed spreadsheet to the system and monitor any errors.

Chapter 3 - Page 53
Sample Item Spreadsheet Upload

Sample Item Spreadsheet Upload
This is a portion of an example spreadsheet (text) upload file. The row and column titles
provided in the template must not be altered!
Process to Load a Spreadsheet
The process for uploading data using text files or spreadsheets is straightforward. The
templates can be obtained from the resource file described earlier in this topic. The zip file
contains the Readme instructions for entering data into the file. After filling in the template you
can upload it following the instructions provided earlier or in the online help.
Tip: The templates should already have been loaded into a specific directory during the install
for them to be available for you to download. If you encounter any errors there are notes on
OracleMetaLink that will tell you how to get the templates loaded again.

Chapter 3 - Page 54
Practice - Create a Global Blanket Purchase Agreement and Edit
Content
Overview
This practice provides an opportunity for you to create a purchase agreement in Oracle
Purchasing’s Professional Buyer’s Work Center. You will authorize this agreement for update by
both suppliers and iProcurement Catalog Authors. As a supplier, you will upload a spreadsheet
file to add items to the agreement. You will add items as a catalog author as well. For both
updates, as a Buyer, you will accept the updates.
Assumptions

Tasks
Buyer Creates Global Blanket Purchase Agreement
Supplier Loads New Items
Buyer Reviews and Approves New Supplier Items
Catalog Administrator Adds New Items
Buyer Reviews and Approves New Author Items

Chapter 3 - Page 55
Solution - Create a Global Purchase Agreement and Edit Content
Buyer Creates Global Blanket Purchase Agreement
Responsibility = Purchasing, Vision Operations (USA)
1. Navigate to the Agreements page in the Professional Buyer’s Work Center.
• (N) Buyer Work Center > Agreements
2. Create Global BPA header

Verify Create field LOV is “Blanket Purchase Agreement”, then click (B) Go
Note: The Agreement tab in the Buyer’s Work Center will ONLY create a global
blanket purchase agreement (BPA). So you will NOT see any Global checkbox in the
header section as it is global by default.
3. On the Blanket Purchase Agreement page, enter the following information for the Header:
Field Vision Operations

Operating Unit Vision Operations
Supplier Office Supplies, Inc.
Supplier Site OFFICESUPPLIES
Buyer Your last name, first name
Description XX GBPA
Bill to Location V1- New York City
Default Ship to Location M1- Seattle

Chapter 3 - Page 56
4. (B) Save
5. Note the BPA number #___________________________
6. ACTIONS field LOV, choose "Enable Supplier Authoring" and click Go button.
Note the confirmation that the supplier Office Supplies, Inc. can now edit this Blanket
Purchase Agreement
VERY IMPORTANT NOTE: This action is to allow the supplier user to modify the
BPA and add items. Supplier users cannot create their own BPAs. The supplier’s access
for this is Oracle iSupplier Portal.
7. ACTIONS field LOV, choose “Enable Catalog Administrator Authoring” and click Go. This
allows the iProcurement Catalog Administrator to upload items to the agreement in a
subsequent step.
At this point the agreement is created (but not approved or processed) and is accessible to
the supplier for uploading of items.
Supplier Loads New Items
8. Logout and log into Oracle iSupplier Portal

− Username / password = supplier / welcome
− Responsibility = iSupplier Portal Full Access
iSupplier Portal homepage opens. The Orders at a Glance table will only show
Approved POs.

Chapter 3 - Page 57
9. Find your agreement and navigate to the Update Blanket Agreements page:
• (T) Orders > (ST)Agreements > (B) Search
• Enter your agreement number in PO Number
• (B) Go
• Open your agreement by clicking the PO Number link
• Select Edit Agreement in Actions list and click (B) Go
10. Upload file with new items.
• (M) Add Lines: Via Upload

• (B) Go
• Accept the default (Tab-delimited)
• (B) Download Resources.
• (B) Download.
• Save the zip locally.
• Open the zip file. Open the TextTemplate.txt file in Excel. Use the readme file and the
instructions below to complete the spreadsheet file.
Type Description Shopping Category Category Unit Price
Goods XXSticky Pads XXOffice Supplies XX.SUPPLIES Pack 8
Goods XXLegal Pads XXOffice Supplies XX.SUPPLIES Dozen 7
Goods XX600MB CD- XXComputer Supplies XX.COMPUTER Each 100

ROM
Goods XX250GB XXComputer Supplies XX.COMPUTER Each 100

External Drive
11. Return to the Upload Lines Page
• (B) Back
• Browse to your completed spreadsheet file.

Chapter 3 - Page 58
• (B) Submit.
Buyer Reviews and Approves New Supplier Items
Responsibility = Purchasing, Vision Operations (USA)
12. Logon to the system using the XXUSER you created earlier.
13. Navigate to the Agreements page.
• (N) Buyer Work Center > Agreements
14. Accept the supplier entered items:
• Select the “My Agreements With Pending Change Requests” View and click (B) Go

OR
• (M) Select Agreement: Respond to Change Requests and click (B) Go
The Respond to Change Requests page allows the buyer to decide item by item to either
accept or reject. You can also click on the Details icon to see all the attributes for each
item (Image filenames, price breaks, and so forth).
15. (B) Accept All or (B) Submit (if Action = Accept for all lines).
16. (H) Return to Agreements.
17. Query your agreement, it is now or will be shortly displayed with a status Approved.

Chapter 3 - Page 59
Catalog Administrator Uploads Additional Items
Responsibility = iProcurement Catalog Authoring
18. (H) agreement number
19. (T) Lines
20. (B) Update. You should see the items you just added as a supplier.
21. (B) Add 5 Rows.
22. Add two new lines:

Line 1 Line2
Type Goods Goods
Description XXHP Brochure Paper - Glossy XXHP Presentation Paper - Glossy
8.5x11" 150 Sheets 8.5x11" 300 Sheets
Category XX.SUPPLIES XX.SUPPLIES
Unit Ream Ream
Price 9.00 16.00
23. (B) Submit.

Chapter 3 - Page 60

Chapter 3 - Page 61
XML: More Catalog Control

XML: More Catalog Control
The Oracle iProcurement catalog was initially designed to be maintained using XML
(Extensible Markup Language) files. The spreadsheet (tab-delimited) and other format options
are provided to make interfacing with external supplier’s catalogs simpler.
XML is just another markup language like HTML (HyperText Markup Language). They are
both subsets of SGML (Standard Generalized Markup Language), the international standard
for defining descriptions of the structure of different types of electronic documents.
Markup languages are generally similar in structure since they tend to group like things within
a begin tag followed by an end tag. The begin tag and end tag have the same name and are
surrounded with separator characters <>. So we could create our own XML to describe a
sentence and it would look like: <SENTENCE>This is my special sentence.</SENTENCE>.
In this example <SENTENCE> is the begin tag and </SENTENCE> is the end tag.
References:
XML: http://w3.org/XML/

Chapter 3 - Page 62
XML Upload Items File Structure

XML Upload Items File Structure
The XML file that is used to load content into Oracle iProcurement can be generated in a text
editor, commercial XML generator program, or an XML generator program that you write
yourself. Since XML is a simplified dialect of SGML you should expect the file to follow a
predefined structure.
Process to Upload an XML File
(N) iProcurement Catalog Administration > (T) Agreement > Upload
Loading an XML file works the same as the spreadsheet (tab-delimited) file, except:
• You use the DTD instead of a template to help you create a valid XML file. (Also use the
Readme included in the download; it contains XML examples.)
• Save the file as a .xml file.
• Optionally make use of the POR:Load Auto Root profile option. Setting this to Yes lets
you add new base descriptors, in addition to system-provided base descriptors, such as
supplier item number. For example, you can add a Country of Origin descriptor for all
items.

Chapter 3 - Page 63
• Use XML tags instead of column headings.

Chapter 3 - Page 64
Uploading Items: Spreadsheet Compared to XML

Uploading Items: Spreadsheet Compared to XML
As you can see illustrated in the slide above, the basic difference between the spreadsheet file
that you loaded in an earlier practice and an XML file is just format. The spreadsheet file is
spread out with a column and row relationship. The XML file presents the entire item and its
attributes all in a sequential sequence.
Note the use in XML of the begin tag and end tag markers that are part of all generalized
markup languages. The widespread acceptance of XML is due to its being an International
Standards Organization (ISO) data transmission standard and its ease of extensibility.
Attributes can be added to an XML file without having to modify a process that uses the file.
With an old style row and column relationship, any new attributes force modification to the
processing program for it to work.
References:
W3C recommendation for Extensible Markup Language (XML) 1.0 at
http://www.w3.org/TR/2000/REC-xml-20001006.

Chapter 3 - Page 65
Sample XML Administrative Section

As described in detail in the Readme file available from the Download Bulk Load Resources
page in the eContent Manager, the XML bulk load file is composed of several sections:
• ADMIN (Catalog Title and other fields in spreadsheet)
• NAME (Name used to identify your file)
• DATE (Date of creation or modification)
• SOURCE (Author of the XML document)
This slide shows a sample ADMIN section.

Chapter 3 - Page 66
Sample XML Data File Structure

Sample XML Data File Structure
This is a generalized version of the XML file that might be used to add an item. The following
slide detail each specialized section.

Chapter 3 - Page 67
Sample XML Document Header Section

Sample XML Document Header Section
This section is required, but its fields are used for your own identification purposes only. The
XML loader does not validate or store any of the information contained in the document header
section.
When you specify a Purchasing Document in the user interface during the upload process, the
loader obtains the proper context from the document you have selected.

Chapter 3 - Page 68
Sample XML Document Lines Section

Sample XML Document Lines Section
This slide shows a sample LINES section. The LINES section is used to maintain your catalog
items and their respective prices.

Chapter 3 - Page 69
Sample XML Data Item Section

Sample XML Item Section
This slide shows a sample ITEM section. The CATEGORY element identifies the Oracle
Purchasing category while SHOPPING_CATEGORY indicates the iProcurement category this
item belongs to (Shirts).
Note that the SUPPLIER_PART_NUM in this section refers to the supplier’s item number.
Other commonly used descriptors for an XML item section are:
• PRICE (Note that UNIT_PRICE is the list price for all users. The next slide illustrate the
PRICE section which is used to specify different prices for this item for different
operating units.)
• DESCRIPTION (Description of the item or service. Required on an ADD.)
• UOM (Unit of measure as defined in Oracle Applications.)
• PICTURE (File name of image associated with this item.)

Chapter 3 - Page 70
Sample XML Data Price Section

Sample XML Price Section
This is an example of another data defining element that can be included in the ITEM section
of your XML document. This particular sample sets a price discount of 10% when purchased
in a quantity greater than 5. This example applies to everyone but could be limited to a ship to
organization.

Chapter 3 - Page 71
Practice - Understand the XML Data File Structure
Overview
In this practice, you will review the XML file structure for loading data into the iProcurement
catalog. There are 3 main XML sections in an XML file pertaining to Data
− Admin (Required) – Identifies the catalog, optionally specify a contract purchase
agreement number
− Root Descriptors (Optional)
− Data (Required)
Tasks

Review XML Data Structure
1. Review XML file structure for loading data.
<?xml version="1.0" ?> 

<CATALOG xml:lang="EN-US">
<ADMIN>
Admin section is
 required
</ADMIN>
<DATA>
<ITEM ACTION="SYNC"
<NAMEVALUE>
<NAME>Column name</NAME> This name/value Catalog open and
<VALUE>Data</VALUE> section may repeat close tags surround
many times. Name admin and data
</NAMEVALUE> is column name
and value is the
data value. The
<NAMEVALUE> must be one name/
<NAME>Column name</NAME> value section for
EACH required data
<VALUE>Data</VALUE> value.
</NAMEVALUE
</ITEM>
</DATA>
</CATALOG>

Chapter 3 - Page 72
Practice - Load Items Using XML
Overview
Suppliers may provide you with electronic catalog content to add to your local catalog. In this
practice, you will load items for the catalog using XML and the agreement you created earlier.
Assumptions

• Profile option POR: Auto Load Shopping Categories is set to Yes.
• Profile option POR: Autocreate Shopping Category and Mapping is set to Yes.
Tasks
Download the XML Resource Files
Create an XML Catalog Data File From the Example
Check Syntax with Internet Explorer
Upload the XML File
Troubleshooting Upload Errors

Chapter 3 - Page 73
Solution – Load Items Using XML
Download the XML Resource Files
Responsibility = iProcurement Catalog Administration
1. (T) Agreements
2. Select your agreement.
• (B) Search
• (M) Agreement = is. Enter agreement number as search value.

• (B) Go
3. (M) Select Agreement
4. (B) Update
5. (B) Go.
6. (T) Lines
7. Select Add Lines: Via Upload and click Go.
8. Select XML File Type.
9. (B) Download Resources

Chapter 3 - Page 74
10. (B) Download
11. Save the Download Resources zip file locally.
Note: The Upload Lines page is a multi-purpose window. You can both download the
resource files for various upload file formats as well as upload the completed files to update
the catalog. This particular window is for uploading activities related to the global blanket
agreement that you created in an earlier practice. There is a similar window for uploading
content to existing blanket agreements and quotations.
Create an XML Catalog Data File From the Example
12. Open the .zip file and then open the file Readme_XML.htm.
• You may have to respond positively (Allow, Yes) to some Security Warning messages,

depending on the browser configuration.
13. Open a window with Notepad.
14. Create your own XML file, XXAddItems.xml. You can copy and update the Example 4 in
the readme or copy the example below into your Notepad window.
• To use Example 4 in the readme:
• In Internet Explorer window displaying the readme, click (H) Data Section: Lines and
scroll down to Example 4
• Select and copy the XML for the example starting <?xml version="1.0" and ending
with </CATALOG>
• Paste the selection into your Notepad window. Note that you can delete the empty
lines to improve readability.
• Insure that there is an underscore between AUX and ID in all usages of the
SUPPLIER_PART_AUX_ID element
• To use the example below:
• Copy and paste the following text into your Notepad window:
<?xml version="1.0" encoding="ISO-8859-1" ?>

<ADMIN>
<NAME />
<INFORMATION>
<SOURCE />
<DATE />
</INFORMATION>
</ADMIN>

Chapter 3 - Page 75
<DATA>
<DOCUMENT type="">
<HEADER>
<DOCUMENT_NUMBER />
<OPERATING_UNIT>
<OWNING_ORG />
<ORG_ASSIGNMENTS enabled="">
<REQUESTING_ORG />
<PURCHASING_ORG />
<PURCHASING_SITE />
</ORG_ASSIGNMENTS>
</OPERATING_UNIT>
<SUPPLIER_NAME />
<SUPPLIER_SITE />

<CURRENCY />
<EFFECTIVE_FROM/>
<EFFECTIVE_TO />
<NAMEVALUE name="" />
</HEADER>
<LINES>
<ITEM lineNum="" lineType="" action="ADD">
<CATEGORY>CLOTHING.SHIRTS</CATEGORY>
<SHOPPING_CATEGORY>Shirts</SHOPPING_CATEGORY>
<JOB_CODE />
<INTERNAL_ITEM_NUM revision="" />
<SUPPLIER_PART_NUM>TS-01</SUPPLIER_PART_NUM>
<DESCRIPTION>Green T-Shirt</DESCRIPTION>
<SUPPLIER_PART_AUXID>Green</SUPPLIER_PART_AUXID>
<EXPIRATION_DATE />
<NAMEVALUE name="LONG_DESCRIPTION">100% cotton, heavy
weight</NAMEVALUE>
<PRICE negotiated="">
<UNIT_PRICE>10</UNIT_PRICE>
<UNIT_OF_MEASURE>Each</UNIT_OF_MEASURE>
<AMOUNT />
</PRICE>
</ITEM>
<ITEM lineNum="" lineType="" action="ADD">
<CATEGORY>CLOTHING.SHIRTS</CATEGORY>
<SHOPPING_CATEGORY>Shirts</SHOPPING_CATEGORY>
<JOB_CODE />
<INTERNAL_ITEM_NUM revision="" />
<SUPPLIER_PART_NUM>TS-01</SUPPLIER_PART_NUM>
<DESCRIPTION>Red T-Shirt</DESCRIPTION>
<SUPPLIER_PART_AUXID>Red</SUPPLIER_PART_AUXID>
<EXPIRATION_DATE />
<NAMEVALUE name="LONG_DESCRIPTION">100% cotton, heavy

Chapter 3 - Page 76
weight</NAMEVALUE>
<PRICE negotiated="">
<UNIT_PRICE>10</UNIT_PRICE>
<UNIT_OF_MEASURE>Each</UNIT_OF_MEASURE>
<AMOUNT />
</PRICE>
</ITEM>
</LINES>
</DOCUMENT>
</DATA>
</CATALOG>
• Update the text in your Notepad window according to the instructions below:

First line:
XML Tag Value
<CATEGORY> XX.MISC
<SHOPPING_CATEGORY> XXMiscellaneous
<SUPPLIER_PART_NUM> XXPP-101
<DESCRIPTION> XX Premier Paper Punch
<SUPPLIER_PART_AUX_ID> Three Hole
<NAMEVALUE Heavy weight three hole punch
name="LONG_DESCRIPTION">
<UNIT_PRICE> 12
<UNIT_OF_MEASURE> Each
Second line:
XML Tag Value
<CATEGORY> XX.MISC
<SHOPPING_CATEGORY> XXMiscellaneous
<SUPPLIER_PART_NUM> XXPC-901
<DESCRIPTION> XX Jumbo Paper Clips
<SUPPLIER_PART_AUX_ID> JumboPC
<NAMEVALUE 100 jumbo sized metal paper clips
name="LONG_DESCRIPTION">
<UNIT_PRICE> 3
<UNIT_OF_MEASURE> BOX
• Save your Notepad file as XXAddItems.xml.

Chapter 3 - Page 77
15. You can check the XML syntax with Internet Explorer by simply opening the file. Internet
Explorer detects that the file is .xml and opens it with its own XML Editor.
Internet Explorer is being used here to check the syntax of your XML file. If you somehow
changed the structure of the sample file while performing your edits (for example, deleted a
closing bracket), that would be indicated in this window. In your work environment you can
use an XML editor that will provide this same syntax checking while you edit. Most likely is
that you will receive larger XML files from your supplier that have been generated by
software that insures that the file complies with the structure required.
16. Verify that the syntax of your XML is correct. Errors will be indicated. Note this just
validates the XML language syntax. It does not validate the XML file against the DTD. If

there are any errors indicated, open the XXAddItems.xml file in Notepad and correct them.
Upload the XML File
17. Return to the Upload page. (B) Back.
18. Upload your XML file using the following options:
Field Value
File Type XML
File Name XXAddItems.xml
Submit for Approval Yes
Apply Oracle e-Commerce Gateway Mapping No
Set Error Tolerance No

Chapter 3 - Page 78
19. (B) Submit
If the submit is successful, you will be returned to the Agreements page with a confirmation
that your upload job has been submitted for processing.
Verify Upload and/or Troubleshooting Upload Errors
20. Verify that the load completed successfully or correct any upload errors.
• Give the upload process some time to complete and then check the job status.
• Click the link for your Agreement number and check the Lines tab to see if your new
lines have been added. If so, you are done with this practice.
• Alternatively, you can click the Upload button. You will receive a message that either

the job is still in progress or that the job completed with errors.
• If there are errors, select View Upload Errors from the Actions menu and click Go.
• View the errors and correct the file in Notepad. Select Discard Errors from the
Actions menu and upload again.

Chapter 3 - Page 79

Chapter 3 - Page 80
Loading Local Catalog Images

Loading Local Catalog Images
Images associated with catalog items can be uploaded using either just the file name as loaded
on a local server or as a URL that links the item to a Web page. Both are accomplished by
providing the file name or the URL in the appropriate section of your upload file.
For a complete overview of image management, including recommendations on thumbnail
image sizes, see the Image Management section of the Oracle iProcurement Implementation
and Administration Guide.

Chapter 3 - Page 81
Sample Uploads for Image Files

Sample Uploads for Image Files
Image files are hosted on the local server:
1. For the POR: Hosted Images Directory profile option, enter the directory path you use to
store image files. This path usually corresponds to the MEDIA_DIRECTORY defined in the
ssp_init.txt file.
2. Ask your database administrator to transfer the pictures to the directory you specified
above. The recommended image file format type is gif or jpeg for maximum browser
compatibility.
3. Create your catalog file image link:
• For a spreadsheet file Insert a column named Image in your file and populate the Image
field with the file name of the images, such as bluepen.gif.
• For an XML file insert a NAMEVALUE element in the ITEM section with NAME
populated with PICTURE and VALUE populated with the file name of the image.
• Note that the image file name is case sensitive. For example, if the image file name is
bluepen.gif, but you specify BluePen.gif in the Image field, the image will not display.
4. Load your catalog file.

Chapter 3 - Page 82
Maintaining Items and Prices

Maintaining Items and Prices
You can maintain items and their attributes using both upload files and/or online authoring.
Online authoring is especially useful for small updates, for example price changes.

Chapter 3 - Page 83
View Loader Job Status

View Loader Job Status
(N) iProcurement Catalog Administration > (L) Upload
From this page you can search for a specific load or for all jobs that you submitted using the
Upload button on the Agreements tab. with a certain status:
• Pending: The job is waiting to be processed.
• Running: The job is in progress. For example, for file uploads, the eContent Manager is
loading the data.
• Completed: The job completed successfully. For file uploads, all of your catalog lines
loaded successfully.
• Error: For file uploads, the file failed to load because of a format or encoding error (none
of the catalog lines was loaded), or the file loaded, but some of its lines were rejected
(successful lines were loaded).
Note: When updating a GBPA by editing an existing agreement and adding/modifying items
on the Update Blanket Purchase Agreement page, you can add lines by using the Via Upload

Chapter 3 - Page 84
option from the Add Lines menu. Any uploads you submit using this option are not viewable
by loader job status.

Chapter 3 - Page 85
View Document Upload History

View Document Upload History
(N) iProcurement Catalog Administration > (L) Upload
If the load completed with errors, you can view reasons why individual lines were rejected.
(The entire item or price is rejected.) Make these fixes in your file and upload again.
Tip: If you have trouble diagnosing an error in a job, or if you want to monitor the job in
Oracle Applications, use the Requests window in Oracle Applications or Oracle Purchasing.
The number assigned to your job on the Loader Jobs page is the same as the Request ID in the
Requests window. Use the View Log button in the Requests window to get more details on the
errors, if needed.

Chapter 3 - Page 86
Agenda

Chapter 3 - Page 87
Catalogs, Content Zones, And Stores

Catalogs, Content Zones, and Stores
Catalog
A generic term describing your online shopping content.
Content Zone
This is an iProcurement term that indicates the type of content and its associated security.
Store
A store enables you to group content zones and smart forms into a single, searchable store.

Chapter 3 - Page 88
iProcurement Catalog Administration: Manage Stores

(N) iProcurement Catalog Administration > (T) Stores
This is the home page for working with content zones, stores, and smart forms in Oracle
iProcurement.

Chapter 3 - Page 89
Content Zones

Content Zones
Catalog is general term that refers to your online shopping content. However, you don't define
or setup catalogs in iProcurement. Instead you define content zones. Catalog Administrators
partition local catalog content into local content zones, define punchout or transparent
punchout content zones, and then assign these content zones to stores. The combination of
content zones that you assign to a Store determines what catalog content your users see.

Chapter 3 - Page 90
Why Content Zones?

Why Content Zones?
Partitioning
• Partitioning based on item’s supplier, supplier site, item category and browsing category
information
• Inclusion and exclusion rules
• Inventory items, items without iProcurement categories may be included or excluded
Punchout, Transparent Punchout, Informational Punchout Content Zones, and Smart
Forms:
• Simplified definition pages
• Searchable keywords
All content zones support operating unit or responsibility level security.

Chapter 3 - Page 91
Creating A Local Content Zone

Creating A Local Content Zone
(N) iProcurement Catalog Administration > (T) Stores > Content Zones
The Manage Content Zones page is the home page for working with content zones in Oracle
iProcurement.
Select Create Local Content Zone from the list of actions and click Go.
Select the appropriate include/exclude statements to define this zone’s content (that is, which
items will be included). Note that you can restrict by both suppliers and shopping categories.
Select the appropriate security statement to define the access controls for this zone.

Chapter 3 - Page 92
Applying Content Security Rules

Applying Content Security Rules
Since rules about supplier content can exist in a content zone along with rules about category
content, when both are defined the restrictions they create are both in effect. The rules are
ANDed together

Chapter 3 - Page 93
Applying Content Security Rules In Stores

Applying Content Security Rules in Stores
Since stores are defined in terms of content zones, there could be a case where a store
contained multiple local content zones. Also, each content zone could have its own supplier
and category rules. In this case the content available from the store are the items which meet
either of the content zones’ rules. The content available from one content zone appears along
with the content from the other store. The rule sets are ORed together.

Chapter 3 - Page 94
Practice - Create a Local Content Zone
Overview
In this practice, you will create a local content zone for later inclusion in an iProcurement store.
Assumptions

Tasks
Set up a new local content zone

Chapter 3 - Page 95
Solution – Create a Local Content Zone
Set up a new local content zone
1. Navigate to the Manage Content Zones page.
• (N) iProcurement Catalog Administration > (T) Stores > (H) Content Zones
• (M) Create Local Content Zone. (B) Go.
2. Create a new local content zone using the information in the table below to complete the

page.
Field Value
Name XX Office Supplies, Inc. Content Zone
Description Items supplied by Office Supplies, Inc.
Suppliers Include items from specific suppliers (Office Supplies, Inc. )
Categories Leave blank
Assign Content Zone Security Secure by operating units (Vision Operations)

Chapter 3 - Page 96
3. (B) Apply.

Chapter 3 - Page 97

Chapter 3 - Page 98
Creating A Punchout Zone

Select Create Punchout Content Zone or Create Transparent Punchout Content Zone from the
list of actions and click Go.
More details regarding setting up punchouts will be covered in the “Set up remote content”
topic.

Chapter 3 - Page 99
Creating An Informational Zone

Creating An Informational Zone
Select Create Informational Content Zone from the list of actions and click Go.
Informational zones are used for general procurement policies and guidance specific to a
commodity type. They can provide a link to an internal or external web site for additional
information.
Buying organizations may not choose to handle some types of items and services through the
Oracle iProcurement requisition system. For example a company may not have any approved
supplier for flowers. An informational catalog is set up to advise employees to purchase
flowers directly from local florists. The informational catalog would outline company policy,
describe the process to get a company credit card, some links or phone numbers to the florists,
and even steps to file the expense report.

Chapter 3 - Page 100
The information is contained on either a web page, in which case you can reference it using a
URL:
http://my.web.page, or in an html page.

Practice - Create an Informational Content Zone
Overview
In this practice, you will create an informational content zone for later inclusion in a store.
Assumptions

Tasks
Create an Informational Content Zone

Solution
Create an Informational Content Zone
1. Navigate to the Manage Content Zones page:
• (N) iProcurement Catalog Administration > (T) Stores > (H) Content Zones
2. (M) Create Informational Content Zone. (Go)
5. Create your content zone:

− Name = XX Oracle Web Page
− URL = http://www.oracle.com
− Accessible by all users
6. Apply.

Creating Smart Forms

Creating Smart Forms
(N) iProcurement Catalog Administration > (T) Stores > Smart Forms
The Manage Smart Forms page is the home page for working with smart forms in Oracle
iProcurement. Smart forms are used by buyers to request items that are not in the catalog (non-
catalog requests). A standard default form for these type of requests can be used by clicking the
Non-Catalog Request link in the toolbar. Smart forms allow you to create customized request
forms. This can include default item and supplier information. You can allow overrides to the
defaults or define them as uneditable. Also, you can attach previously defined information
templates to request additional request details.
Refer to Practice – Creating a Smart Form [CreSmartForm]

What Are iProcurement Stores?

What Are iProcurement Stores?
For most organizations, restricting access to content by role is very important. After
configuring catalogs and stores, administrators can easily control which are available to
different classes of users within the employee population.
A store enables you to group catalogs into a single, searchable store. The store should be easy
for requesters to understand - for example, a store containing all computer supplies or all office
supplies. You can create one or more stores. These stores appear on the Shop page. Requesters
select a store before searching. When requesters search, Oracle iProcurement searches across
all content zones in the store and displays the results. Requesters can also click a store to see
the content zones within it. (You cannot search more than one store at a time.) Using their
preferences, requesters can also select a favorite store to search by default.
• Every punchout, transparent punchout, or informational content zone must be assigned to
a store to be searchable. (The local catalog is already in the Main Store by default,
although you can assign it to any store.)
• A content zone can be in multiple stores.

• A store can contain more than one content zone of the same type, such as two punchout
catalogs, with one exception: to maximize searching performance, a store can have only
one local content zone.
• The more transparent punchout content zones in a store, the slower the performance may
be (depending on factors such as network and Internet traffic and the external site's
performance).
• If a store contains only punchout content zones, set at least one of them to always display
in the search results, to prevent the Search Results Summary page from being blank when
the search returns no matching items. See creating or editing a store.
• The default Main Store has no image associated with it. If you want to associate images
with stores, see creating or editing a store.
• A store that contains a transparent punchout content zone does not allow Advanced
Search. Advanced Search is performed on the local content zone only.

Managing Stores

Managing Stores
(N) iProcurement Catalog Administration > (T) Stores
Oracle iProcurement provides the default Main Store when installed.

• Uploaded content will be in that store unless you specify otherwise.
• Additional stores must be created for punchout (external) and informational content.
To create a store:
1. On the Manage Stores page, click Create Store
2. On the Create Store page, enter a Store Name. Maximum character limit for Name: 2,000
bytes.
3. Image: Enter or edit the name or URL of an image that you want to display next to this store.
The image displays to requesters on the Shop page. If you enter an image name (such as
abc.gif) rather than a full URL (such as http://www.abc.cm/abc.gif), make sure the image
exists in the directory specified in POR: Hosted Images Directory. If you specify
no image, the store displays its name and description only. (Behind the scenes, the store

displays a blank image file if you specify no image. If desired, you can change this default
blank image file to always display a standard "no store image" file or message. See the
image management section of the Oracle iProcurement Implementation Guide).
4. Enter a Short Description. These appear next to the store when it displays to requesters on
the Shop page. Maximum character limit for Short Description: 240 bytes.
5. Enter a Long Description. The Long Description displays after the requester clicks the store
on the Shop page. The Shop Store page displays the long description near the top of the
page; it displays the list of catalogs and their descriptions below. Maximum character limit:
2,000 bytes.
6. Add one or more Content Zone.
7. Add a Smart Form, if appropriate.
8. Click Continue and Add Catalogs to select the catalogs that you want to include in the store.

To edit a store, click the Update icon next to the store.

Practice - Create a Store
Overview
In this practice, you will create a store.
Assumptions

Tasks
Create a New Store
Field Value
Store Name XX Office Supplies, Inc
Description Office Supplies, Inc. item store
• Include your XX Office Supplies, Inc. local content zone.
• Include your XX Oracle Wed Page informational content zone
• Include your XX Office Supplies, Inc. smart form.
1.
Test your new store’s content restrictions

Solution – Create a Store
Create a New Store
1. Navigate to the Manage Stores page
• (N) iProcurement > (T) Stores > (H) Stores > (B) Create Store
2. Create your store:
• (B) Create Store

Field Value
Store Name XX Office Supplies, Inc. Store
• (B) Add Content Zone - include your XX Office Supplies, Inc. local content zone.
• (B) Add Content Zone - Include your XX Oracle Web Page informational content zone.
• (B) Add Smart Forms - Include your XX Office Supplies, Inc. smart form.
3. (B) Continue

4. Resequence the content zones to have your informational content zone show before your
smart form. Accept all other defaults.

5. (B) Apply
Verify your new store in the table on the Manage Stores page
Responsibility = iProcurement
6. On the Shopping page, enter pen in the keyword field.
7. (B) Go. Briefly scroll through the search results. Note that there are many entries from
various suppliers.
8. Return to the main shopping page. (T) Shop
9. Select your XX Office Supplies, Inc store.
10. Perform your search again. Note that only entries from Office Supplies, Inc. appear in the
results.
11. Test your informational content zone.
• (ST) Stores, (H) xxOffice Supplies, Inc store, (H) xxOracle Web Page. Note that you go
to the public Oracle web page. Close page to return.
12. Test your smart form. Note that the supplier information cannot be modified.
• (H) xxOffice Supplies, Inc.(smart form)
13. Sign off and sign on as Bruno/welcome (this user is assigned to Vision France). Select
iProcurement Vision France.
14. Select your store. Note that only the informational content zone is accessible as it is
unsecured by operating unit.

Agenda

Remote Catalog Content

Remote Catalog Content
Remote or external catalog content simply means that no catalog content is stored on our
servers.
Requester can:
• Click a link on Shopping or Search pages that takes requester directly to the supplier’s
Web store.
• Shop for and select items in the Web store.
• Return with chosen items to iProcurement.
• Complete checkout process in iProcurement for the items.
Setup is required by both the catalog administrator in iProcurement and the supplier.

Oracle iProcurement Catalog Management Review

Oracle iProcurement Catalog Management Review
This slide provides a generic breakdown of catalogs and some suggestions as to how they
might be used. For our discussion of punchout to to remote catalogs we are only concerned
with two of the four possible catalogs:
Catalog
For our discussion of punchout to to remote catalogs we are only concerned with two of the
four possible catalogs:
• Supplier-hosted: A supplier organization provides access to their externally hosted
catalogs.
• Marketplace-hosted: A third party organization hosts multiple supplier’s catalogs.
Commodities
material).
• Configured products: products requiring high degree of configuration, such as computer

supplies.

Oracle Content Zone Types Review

Oracle Content Zone Types Review
These are the official catalog “types” as identified in the Oracle iProcurement Implementation
Guide and the Oracle iProcurement Help. It is important to understand the distinction between
how catalog content is stored and how it is delivered to the Oracle iProcurement requester.

What is Punchout?

What is Punchout?
Punchout is protocol for interactive sessions managed across the Internet. It supports user
interaction with a remote site through communication from one application to another. This
interaction is performed using real-time XML transactions over the Internet.

What is Transparent Punchout?

What is Transparent Punchout?
Punchout and transparent punchout offer the same basic benefits—mainly, the benefit of the
supplier maintaining its own item information, reducing maintenance costs for the buyer and
supplier, and a single point of access to catalog content regardless of where it resides.
The main distinctions between punchout and transparent punchout are as follows:
• With transparent punchout, the requester does not visibly access the supplier site.
Transparent punchout accesses the site in the background and returns the items directly to
Oracle iProcurement, with no changes to the requester’s user interface. Requesters
perform no additional navigation to return to Oracle iProcurement.
• Whereas transparent punchout is ideally suited for products with fluctuating prices,
punchout is ideally suited for configurable products. In addition, the supplier’s site may
have special features unique to the industry or to the buyer-supplier relationship that a
punchout can take advantage of.
In a transparent punchout, the supplier sets up integration with its search engine to properly
return search results to Oracle iProcurement. In a punchout, the supplier sets up integration to
access its catalog and provide a mechanism for returning the requester to Oracle iProcurement.

(If the supplier has already implemented a punchout, the supplier can leverage some of that
setup when implementing a transparent punchout.)

Oracle iProcurement Punchout Models

Oracle iProcurement Punchout Models
The models described here mention Oracle Exchange since that punchout model simplifies
some of the technical issues. You could punchout to some other marketplace as well using
model 2.
Since the Oracle Exchange catalog contains many suppliers’ items in one place, with the ability
to shop and compare common item information, buyers can easily search and compare among
many supplier items using Model 1. Suppliers load their items to the Exchange catalog using
XML or spreadsheet text files.
Model 4 can be used for suppliers who use cXML (commerce eXtensible Markup Language).
Models 3 and 4 enable the catalog administrator to simply download the supplier’s punchout
setup (also known as a punchout definition) from Oracle Exchange into iProcurement.

XML: The Language of a Punchout

XML: The Language of a Punchout
In order to standardize the exchange of catalog content and to define request/response
processes for transactions over the Internet several “standards” have been created. The
processes covered by these standards include purchase orders, change orders,
acknowledgments, status updates, ship notifications and payment transactions.
Be aware that there are other XML DTD “standards” in use as well including initiatives led by
CommerceNet, RosettaNet, and Information & Content Exchange (ICE). For more
information about OBI visit www.openbuy.org and for cXML visit www.cxml.org.

Comparing a Supplier Punchout to a Marketplace Punchout

Comparing a Supplier Punchout to an Oracle Exchange Punchout
Here we are comparing the benefits of shopping at a supplier-hosted site to a marketplace-
hosted site.

Model 1 & 2 Technical Overview

Model 1 & 2 Technical Overview
1. The buyer connects to the Oracle iProcurement server using a browser.
2. When the buyer clicks a punchout to Oracle Exchange site the iProcurement server will send
an XML punchout request document to the Exchange providing details of the user and
authentication information.
3 & 4. The Exchange will send an XML Punchout response to the iProcurement server. The
response includes a URL though which the user connects to Oracle Exchange.
5. The user's browser is redirected to the Oracle Exchange catalog, where the user browses the
catalog and adds items to the shopping cart.
6a. When the user finishes shopping, the contents of the shopping cart is posted to the user’s
browser.
6b. The contents of the shopping cart are added to the user’s shopping cart in Oracle
iProcurement. The normal check out will follow in the usual manner.
Model 2 Technical Overview
Same as above, but substitute supplier for Exchange. Details can vary somewhat depending on
supplier’s configuration.

Models 3 & 4 Technical Overview

Models 3 & 4 Technical Overview
1. The buyer connects to the Oracle iProcurement server using a browser.
2. When the buyer clicks a punchout to a Supplier site via an Oracle Exchange, the
iProcurement server will send an XML punchout request document to the Exchange providing
details of the punchout supplier, the user performing the punchout, and the proxy user through
which to connect to the Exchange.
3. The Exchange will send a punchout request to the supplier site, providing details of the
password with which to connect (provided by the supplier when they defined the punchout on
the Exchange) and the iProcurement user requesting the connection.
4. The supplier will respond with an XML Punchout response document. The response
includes a URL through which the user will connect to the supplier site.
5. The Exchange will send an XML Punchout response to the iProcurement server. The
response includes a URL through which the user will connect to the supplier site.
6 & 7. The user’s browser session will be redirected to the supplier’s catalog, where the user
will browse the catalog and add items to their shopping cart.

8a and 8b. When they have finished shopping, the contents of the shopping cart will be posted
to the user’s browser and then added to the user’s shopping cart in Oracle iProcurement, the
check process will continue in the usual manner
cXML is a specialized version of XML developed by several commercial partners in an
attempt to streamline the commercial use of XML documents. You can think of it as a uniquely
defined subset of XML designed specifically for procurement transactions.
9 & 10. If this is a cXML supplier, since iProcurement cannot process cXML document, the
cXML document is sent to the Oracle Exchange to be translated into Oracle native XML,
format which is then passed back to Oracle iProcurement.

Deciding on a Punchout Model

Deciding on a Punchout Model
Assuming you have chosen to use punchout this slide shows the decision flow you should
consider. The following are the models referred to above:
• 1 - Oracle iProcurement to Oracle Exchange
• 2 - Oracle iProcurement Directly to Supplier-Hosted Catalog
• 3 - Oracle iProcurement to Supplier-Hosted Catalog using Exchange (XML)
• 4 - Oracle iProcurement to Supplier-Hosted Catalog using Exchange (cXML)

Punchout Management

Punchout Management
Select Create Punchout Content Zone or Create Transparent Punchout Content Zone from the
list of actions and click Go.
Content Zones
Used by the Oracle iProcurement administrator to create and manage content zone
characteristics. The Manage Content Zones page is used to define the punchout source and
access method, as well as details about the actual location of the catalog.
Stores
Used by the Oracle iProcurement administrator to create and manage store attributes. The
Manage Stores page is used to define the store name, type, operating unit, and identification.
Smart Forms
You can define smart forms and associate them for specialized requests.

Basic Punchout Setup Steps

Basic Punchout Setup Steps
These are the common setup steps for all punchout models.
You should always check the Oracle iProcurement documentation on MetaLink for the latest
information. At the time this slide was prepared the following profile options impacted
punchout:
• POR: Proxy Server Name
• POR: Proxy Server Port
• POR: CA Certificate File Name
• POR: Transparent Punchout Timeout Limit
• POR: Default Currency Conversion Rate Type
Other considerations:
• If the supplier’s site is secure (uses an https:// URL):
- Make sure the supplier’s site is on the certificate authorities (CA) list, which is a file
in iProcurement. By default this file is called ca-bundle.crt in iProcurement.
- Make sure POR: CA Certificate File Name is set to this CA directory and file. For
example: $APACHE_TOP/Apache/conf/ssl.crt/ca-bundle.crt.

• Category mapping is required, so at minimum, the catalog administrator must map
Purchasing categories to category names that the supplier uses.
• You can also do supplier, supplier site, and UOM mapping, if the supplier uses different
values for these than you do.
• Set up mapping in e-Commerce Gateway.
References:
See the Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout for more
information.

Oracle Exchange Punchout Setup

Supplier Punchout Setup

Supplier Punchout Setup
Once all of these steps are done, the catalog administrator at the buying company enters the
supplier URL and password in the eContent Manager setup pages in iProcurement.
For Model 1 (punchout from iProcurement to Exchange) the supplier must:
• Register on Oracle Exchange.
• Upload XML or spreadsheet text files to the Oracle Exchange catalog. (Performed on
Oracle Exchange.)
For punchouts involving Oracle Exchange (Models 3 and 4) the supplier must:
• Register on Oracle Exchange.
• Define the punchout (for example, specify URL, password, and keywords) on Oracle
Exchange.
• Publish the punchout on Exchange. (At any time, the supplier can “hide” access to the
punchout by unpublishing it if necessary.)
References:
See the Oracle Procurement Supplier’s Guide to Punchout and Transparent Punchout for
more details.

Agenda

Administer Oracle iProcurement Catalog Structure

Administer Oracle iProcurement Catalog Structure
Manage Descriptors and Item Categories: A critical portion of the Online Schema
Maintenance features. Schema refers to the structure and organization of the catalog. Schema
consists of categories and descriptors.
Manage Category Hierarchy: The table of contents presents a hierarchical view of the
catalog, similar to a book's table of contents. Use the table of contents to view and create
hierarchies of categories and to create browsing categories.
Map Shoping Categories: Enables you to display different category names to the requestor for
an existing category.
Map Purchasing Categories: Mapping categories enables you to link category names
imported to the catalog to an existing Oracle Purchasing category.
You can perform your administration either by using Schema Maintenance online or by XML
upload.

Catalog Structure Components

Catalog Structure Components
Item categories
Creating a new category in Oracle iProcurement is easy and gives you the flexibility to change
as your needs change. You could change a category name to reflect a change in your business
or in the market. Deleting a category might be required if you no longer purchase items in that
category.
The iProcurement catalog supports a maximum of 50 local descriptors per category, 250 total
base descriptors, and any number of item and browsing categories. (The more browsing
categories you have, the longer the Build Table of Contents page may take to display.)
Descriptors
Remember that changing local descriptors allows you to change the information for a particular
category. Editing base descriptors changes descriptors for the entire catalog, not just for a
particular category.

Local Catalog Structure: Categories

Local Catalog Structure: Categories
When we talk about a catalog, we are usually thinking about paper catalogs. These paper
catalogs are broken down into sections - clothing, home and garden, lighting, and so on. Think
of the category structure you are building as if it were a table of contents to a reference book.
Within each section there are items, and each item has a description with some relevant
information for that item. The Oracle iProcurement catalog is designed to enable you to model
your electronic catalog in a way similar to a paper catalog.

Local Catalog Structure: Items

Local Catalog Structure: Items
Within each category (catalog section) there are items, and each item has a description with
some relevant information for that item. The information specific to a category of an item is
termed a ‘local descriptor’. An example might be that a sofa comes with dimensions, to make
sure it will fit in your lounge, whereas speakers come with output ratings.
Any information that could appear on every item in every category (like price or description) is
a ‘base descriptor’.
Note: This discussion of local descriptors is presented here only to assist your understanding of
the overall catalog structure. Local descriptors cannot be extracted, but must be bulk loaded
which will discussed later.

Creating and Modifying the Catalog Structure

Creating and Modifying the Catalog Structure
Tip: Use XML files to build your catalog structure. Once you have refined them in the test
environment it is a simple matter to copy them and load them to the production system.

Online Schema Maintenance

Online Schema Maintenance
(N) iProcurement Catalog Administration > (T) Schema
From this page you can
•Manage base descriptors
•Create item categories and descriptors
•Maintain your category hierarchy (Table of Contents)
•Perform category mapping
Note: Most catalog administration functions are also available using uploads.

XML Upload Schema File Structure

XML Upload Schema File Structure
Similarly to the item upload discussed in an earlier topic, you an use a completed XML file to
upload catalog (schema) information.

Sample XML Schema File

As described in detail in the Readme file available from the Download Bulk Load Resources
page in the eContent Manager, the XML bulk load file is composed of several sections:
• ADMIN (Catalog Title and other fields in spreadsheet)
• CONTRACTS (Contract Reference section in spreadsheet)
• ITEM (item information such as Supplier Item Number in spreadsheet)
• PRICE (price information such as UOM in spreadsheet)
• ROOT_DESCRIPTORS (if you want to include additional base descriptors, and
POR:Load Auto Root is set to Yes)
This slide shows a sample ADMIN section.

Sample XML Schema Section

Practice - Review XML Schema Structure
Overview
In this practice, you will review XML Schema Structure. There are 3 main XML sections in an
XML file pertaining to Schema
− Admin (Required)
− Schema (Optional)
− Hierarchy (Optional)
Tasks
Review XML Schema Structure

1. Review XML Schema Structure
<?xml version="1.0" ?> 

<ADMIN>
Admin section is
 required
</ADMIN> Catalog open and
close tags surround
admin and schema
<SCHEMA>
Schema section

</SCHEMA>
</CATALOG>

Practice - Load Categories using XML
Overview
In this practice, you will load categories using XML.
Assumptions

Tasks
Create an XML Catalog Data File
XML
<?xml version="1.0" ?>
<ADMIN>
<NAME>2005 Office Supplies Catalog Categories</NAME>
<INFORMATION>
<SOURCE>Internal</SOURCE>
<DATE>01-JAN-2005</DATE>
</INFORMATION>
</ADMIN>
<SCHEMA>
<CATEGORY ACTION="SYNC">
<KEY>XXOffice Furniture</KEY>
<NAME>XXOffice Furniture</NAME>
<TYPE>GENUS</TYPE>
<DESCRIPTION>XXOffice Furniture</DESCRIPTION>
</CATEGORY>
</SCHEMA>
</CATALOG>
Upload the File

Solution – Load Categories Using XML
Create an XML Catalog Data File
Signon = XXUSER
1. (B) Start > Programs > Accessories > Notepad
2. Type the following XML (Replace XX with your terminal number!)
Tip: You can cut and paste the XML example below and modify it.

XML
<?xml version="1.0" ?>
<ADMIN>
<NAME>2005 Office Supplies Catalog Categories</NAME>
<INFORMATION>
<SOURCE>Internal</SOURCE>
<DATE>01-JAN-2005</DATE>
</INFORMATION>
</ADMIN>
<SCHEMA>
<CATEGORY ACTION="SYNC">
<KEY>XXOffice Furniture</KEY>
<NAME>XXOffice Furniture</NAME>
<TYPE>GENUS</TYPE>
<DESCRIPTION>XXOffice Furniture</DESCRIPTION>
</CATEGORY>
</SCHEMA>
</CATALOG>
3. (M) File > Save As

− File Name = XXcategory.xml
− Save as type = Text Document
4. (B) Save
5. Locate the file
6. Right click and choose Open With > Internet Explorer

7. Verify that the syntax is correct. If the syntax is invalid, you receive messages when trying
to open the file.
Upload the File
Responsibility = iProcurement Catalog Administrator
8. Navigate to the upload page and upload your xml file
• (T) Schema > (B) Upload > (B) Browse
• Locate your .xml file
• (B) Submit
9. Monitor your job until it completes.
10. Check your category.

11. (ST) Item Categories
12. (M) Category Name = starts with and enter XX as the search value.
13. (B) Go.


Manage Base Descriptors

Manage Base Descriptors
(N) iProcurement Catalog Administration > (T) Schema > Base Descriptors
Where descriptors appear in the Oracle iProcurement Catalog:
• See the column headings on the Search Results page as a result of a direct search. These
are all base descriptors.
• Local descriptors display on the Search Results page only if the requester got there by
browsing levels of categories.
• The exception to the above statements is when the descriptor has been bulk loaded with
the Search Visible attribute off.

Manage Item Categories

Manage Item Categories
(N) iProcurement Catalog Administration > (T) Schema > Item Categories
From the Item Categories page you can perform any of the tasks listed in the slide above. For
the most part, it is simply a mater of finding the category you wish to modify and then
performing the modification. See the online help from the Manage Item Categories page for
step by step details.
Note: For review:
• Categories are used for browsing and categorizing items.
• Descriptors provide information about an item in the catalog.

Managing Descriptors

Managing Descriptors
Type: Text or number. You can additionally choose Translatable Text if uploading, meaning
you allow the value for this descriptor to vary by language. (If you just choose Text, it cannot
vary by language. You may want Ink Color to vary by language, but Country of Origin not.)
Description: For your own purposes.
Sequence: You can influence the order in which base or local descriptors display on the Search
Results page.
Searchable: You can tell the search engine not to search on this descriptor, or to include it in
searches. For example, your attribute is Ink Color for the category Pens. Someone on the
system enters Red Pen in the search field. If Ink Color is searchable, any item in the Pens
category with a Red ink color will appear on the search results list. If it isn’t searchable, Red
Pen will not return an item with a Red ink color specified in the descriptor.
Note: It is recommended not to make too many descriptors searchable. The more descriptors
you make searchable, the longer it takes for the system to conduct searches. Also, if you make
long values like description searchable, the accuracy of the search is diluted, and if you make
searchable descriptors that are not item detail visible, buyers and catalog authors will not
understand why a particular item was included in their search results.

Search Results Visible: Indicator of whether the descriptor displays as a column header in the
search results. Valid values are 0 (for No) or 1 (for Yes). Note: local descriptors are displayed
to requesters only when accessed by browsing categories online.
Note: making too many descriptors visible will force the requester to scroll too far across on
the Search Results page.
Item Detail Visible: Indicate whether you want this descriptor to display in the item details.
Note: It’s recommended that you make all descriptors visible in the item details to help
requesters make an informed decision about what to buy.
The Schema Readme file provides more detail on these.

Manage Category Hierarchy

Manage Category Hierarchy
(N) iProcurement Catalog Administration > (T) Schema > Category Hierarchy
The category hierarchy is a hierarchical view of the catalog, similar to a book's table of
contents. Use the Category Hierarchy page to view and create hierarchies of categories and to
create browsing categories.
The Category Hierarchy page allows you to create and edit this category structure. This
hierarchical structure can be used to supplement the catalog search capabilities. The table of
contents is structured using a parent/child model.
The root category and all associated categories are displayed on the Category Hierarchy page.
Clicking the expand/collapse icon displays all items associated with that category.
Note: Using the HIERARCHY section of the schema bulk load also enables you to create a
table of contents.

Sample iProcurement Table of Contents

Sample iProcurement Table of Contents
In this sample; Office Supplies is a parent category and Ball Point Pens is an child category. If
you were to select Ball Point Pens there are individual items below it in the hierarchy.

Map iProcurement Categories

Map iProcurement Categories
(N) iProcurement Catalog Administration > (T) Schema > Category Mapping
Since categories can be created in Oracle iProcurement independently from Oracle Purchasing,
mapping catalog categories to Oracle Purchasing categories is a required step in order to
transfer items from the shopping cart (in iProcurement) back into Oracle Purchasing to
complete the shopping cycle.
When an end user shops for an item in iProcurement they see the catalog category, however,
when creating the requisition, the iProcurement mapping is considered and the requisition line
uses the corresponding Oracle Purchasing category.

Map Purchasing Categories

Map Purchasing Categories
(N) iProcurement Catalog Administration > (T) Schema > Category Mapping > Purchasing
Category
The purpose of mapping Oracle Purchasing categories to catalog categories is for display. If
this mapping is performed, the user will see the iProcurement catalog category description
instead of the Purchasing category when shopping for items in Oracle iProcurement. You
would want to do this if the category descriptions defined in Oracle Purchasing are not intuitive
to the Oracle iProcurement catalog users.
Note: Using the Map Categories page, you cannot map Oracle Applications categories to a
category that contains subcategories (browsing category); you can map only to the lowest-level
(item) categories.

Shopping Category Mapping

Shopping Category Mapping
(N) iProcurement Catalog Administration > (T) Schema > Category Mapping > Shopping
Category
This is a very simple sample of how you might use the iProcurement Mapping feature. In
Oracle iProcurement terminology the catalog categories such as My Computer Stuff and My
Networking are referred to as navigation (browsing) categories. The catalog categories like My
Hub contain orderable items. These categories can be linked to Oracle Purchasing categories
and are referred to as genus categories.
Mapping Considerations:
• You can map multiple iProcurement catalog categories to a single Oracle Applications
category.
• You cannot map a single iProcurement catalog category to more than one Oracle
Applications category.
Tip: You can build a hierarchy of categories and as a last step simply link the top of your
hierarchy (a navigation category) to an Oracle Purchasing category and all categories below
will be mapped as well.

Practice - Map iProcurement Categories to Purchasing
Categories
Overview
In this practice, you will map iProcurement categories to Purchasing categories.
Assumptions

Tasks
Map iProcurement Category to Purchasing Category
In the previous two labs, you created two new shopping categories, XXOffice Furniture and
XXPens. You now need to map these categories to Oracle Purchasing categories.
Catalog Categories Oracle Categories

XXOffice Furniture XX.SUPPLIES
XXPens XX.MISC

Solution – Map iProcurement Categories to Purchasing
Categories
Map iProcurement Categories to Purchasing Categories
1. (T) Schema > Category Mapping
2. Map iProcurement shopping category to Purchasing category:
Shopping Categories Oracle Categories

XXOffice Furniture XX.SUPPLIES
XXPens XX.MISC
3. Query up all XX categories: (T) Shopping Category > (M) Shopping Category Name =
starts with > XX
4. (B) Go
5. Select XXOffice Furniture
6. (B) Map
7. Purchasing Category = XX.SUPPLIES
8. (B) Apply
9. Repeat the previous instructions to map XX.Pens to the XX.MISC Purchasing category.

Practice - Build a Schema Hierarchy
Overview
In this practice, you will build a schema hierarchy. A schema hierarchy functions the same as a
table of contents. There are two types of categories in the catalog. Together, these categories
define the hierarchy:
• Item categories, also known as genus categories, are used to group similar items. Item
categories are found at the lowest level of the category hierarchy; therefore an item
category can never be a parent category to a child category. Every item in the catalog
must belong to an item category.

• Browsing categories, also known as navigation categories (or master or intermediate
level categories), are used to define the levels of the category hierarchy. These types of
categories can be either a parent or child to another category, but cannot contain any
items.
Assumptions
Tasks
Build a Table of Contents
Test your Table of Contents

Solution - Build a Schema Hierarchy
Build a Table of Contents
1. Responsibility = iProcurement Catalog Administration
2. (T) Schema > Category Hierarchy > (B) Create Top Level Category
− Category Key = XX Items
− Category Name = XX Items

3. (B) Apply
4. Select the new top-level category, XXItems.
5. (B) Insert Existing Child.
6. Query up all your XX categories.
• (M) Category Name = starts with.
• Enter XX as the search value (in this example, 51).

7. Add your XXComputer Supplies, XXMiscellaneous, XXOffice Supplies, XXOffice
Furniture, and XXPens categories.
• (B) Apply.
Test Your Table of Contents
8. Responsibility = iProcurement
9. Select your XX store.
10. (H) XX Items.
11. Check to see the items in each category (note that there will be on items in the Office
Furniture and Pens categories).

Uploading Categories and Descriptors

Uploading Categories and Descriptors
(N) iProcurement Catalog Administration > (T) Schema > Upload > (B) Upload
If the auto-load profile options are set to Yes you can load categories and local descriptors with
a upload text file, but XML schema files enable you to perform all online maintenance
functions and other functions as well. For complete details see the readme files available from
the Upload Schema page in iProcurement Catalog Administration.

Agenda

Catalog Search Components

Search Components
Search engine (interMedia): Method and technology the search process uses to find items in
the catalog. interMedia database platform services manage rich content (image, audio, and
video) and associated metadata in an integrated fashion with other enterprise information.
Search descriptors: Influence whether the item appears in the search results. A Search Results
Visible descriptor influences whether a particular item descriptor (such as Ink Color for pens)
displays on the Search Results page for the item.

Types of Catalog Searches

Types of Catalog Searches
The quick search:
• Match all search terms: Each keyword must be found to determine a match.
The advanced search:
• Match all search terms with stemming: Each keyword without an operator must be found
to determine a match. Using a technique called stemming the search engine also looks for
words that are derived from the search keywords.
• Begins with (or wildcard): The search engine appends a wildcard to the end of each
keyword without an operator and looks for matches.
• Fuzzy match: The search engine looks for keywords without operators that closely
resemble your item, but are spelled differently.
• Relevance ranking: Relevance is determined by the number of keyword occurrences.
– Items containing more of the search words are scored higher.
– Within documents containing equal number of search words, the score is based on
individual scores of the search words.

– Frequently occurring words contribute less to the relevance ranking than rare
words.
In addition to returning matching items, iProcurement also returns the following:
• Matching categories
• Matching shopping lists
• Matching punchout links. (If the keywords defined while defining the punchout match
the keywords entered, that punchout link displays on the Search Results page.)
Note: The search engine is discussed in detail in the Search Engine Logic appendix of the
Oracle iProcurement Implementation Guide.

Search Results Display: Paragraph

Search Results Display: Paragraph
You can select one of two methods for your search results to be displayed, paragraph or grid.
You set the display method in your Preferences.
The paragraph display includes the images (unless you choose to hide them).

Search Results Display: Grid

Search Results Display: Grid
The grid display shows the search results in a tabular view, allowing easy comparison of many
items.

Special Characters in Catalog Searches

Special Characters in Catalog Searches
Search operators
If you enter % or * in your search word, the system performs a wildcard search. When you use
% or * explicitly in your search word, stemming and fuzzy matching are not performed.
Searchable characters
You can enter a hyphen (-) or underscore (_), and these will be included in the search. For
example, if you enter item-123 test, the search engine looks for items that contain both item-
123 and test.
All other special characters are ignored
For example, if you entered red, white & blue, the search engine ignores the comma and the
ampersand and looks for any items containing the terms red or white or blue.
Additional considerations:
Entry of partial item or part numbers won’t match without a wildcard. For example, enter
AZ2%, not AZ2, to find item numbers starting with AZ2.
Characters that the search ignores are deleted from the string. For example, if you enter
black&white, the search engine ignores the ampersand and looks for a match on blackwhite.

Filtering and Sorting

Filtering and Sorting
Filtering:
• You can filter any of the default base descriptors that the catalog provides except for item
Description, Category, and any of the pricing descriptors (Currency, Price, UOM,
Operating Unit).
• Note that filtering is intended for descriptors that normally contain natural groupings. For
example, the descriptor Manufacturer is likely to contain some values that are the same (a
finite group of airplane manufacturers, for example). But descriptors like Supplier Item
number are typically unique. Although you can technically filter by Supplier Item, it’s not
really intended for filtering.
Sorting:
• You can sort only on item Description, Supplier, Relevance, Category, Unit Price, and
Functional Currency Price.
• You can select ascending or descending.

Search Descriptor Characteristics

Search Descriptor Characteristics
When you are planning your catalog structure you must consider the impact that the descriptor
characteristics have on the search results that your users will see. Are they helping the user
find their results quickly or hindering?

Searchable Base Descriptors

Searchable Base Descriptors
These are the catalog base descriptors that are initially set (by default) to be searchable.

Search Results Visible Base Descriptors

Search Results Visible Base Descriptors
These are the catalog base descriptors that are initially set (by default) to be search results
visible.

Rebuild Catalog Indexes

Rebuild Catalog Indexes
Rebuilding the catalog indexes is an important step after any major catalog software upgrade.
However, it is not a required step to be able to use any newly added data.
When a rebuild is required you must consider the consequences of not being able to use the
catalog during rebuild.

Search Engine Setup Impact

Agenda


(N) iProcurement Catalog Administration
Implementation steps performed in iProcurement Catalog Administration that are related to
catalog content.
Note that this section is merely a review, these topics were covered earlier in the sequence that
they would normally be performed

Setup Considerations

Local Catalog Setup

Profile Options for Uploading Local Content

Profile Options for Uploading Local Content
Important profile options for local catalog setup. Note that there are many profile options that
impact catalog behavior in Oracle iProcurement. See the Oracle iProcurement Setup section
later in this topic for more details.

Supplier-Hosted Setup

Marketplace-Hosted Setup

Profile Options for Punchout

Profile Options for Punchout
Important profile options for Punchout setup. Note that there are many profile options that
impact catalog behavior in Oracle iProcurement.

Practice - Recognize Catalog Specific Profile Options
Overview
In this practice, you will review catalog specific profile options.
Tasks
Recognize Catalog Specific Profile Options
Section Profile Option Description
Catalog Setup MRP:Default Sourcing Assignment Set Sourcing rules for internally sourced items that are
added to the assignment set are used.

Catalog Setup POR: Approved Pricing Only contents extracted from core Purchasing is
displayed in search results.
Catalog Setup POR:Allow Manual Selection of If set to Yes and internally orderable items are
Source displayed, then this column wil display "Select
Source" for internally orderable items. If set to
No, then no distinction will be made between
strictly purchasable items and items that are
internally orderable.
Catalog Setup PO:Legal Requisition Type As of family pack H, this profile option affects
iProcurement. In iProcurement, this profile option
Determines if users may see internally sourced
items or not in iProcurement (if they can't see
internally sourced items, they can't submit
requisitions for them). In Purchasing, this profile
option determines whether users can submit
Internal Requisitions.
Catalog Setup POR:Purge Commit Size Default commit size for Catalog purge
Catalog Setup POR:Purge Jobs Older than (days) Determines how often Bulk Loader History is
purged
Catalog Setup POR: Load Auto Category If set to Yes, can automatically create
iProcurement categories when bulk loading
catalog content (tab-del or XML).
Catalog Setup POR: Load Auto Attrib If set to Yes, can automatically create local
descriptors when bulk loading catalog content.
(tab-del or XML).
Catalog Setup POR: Load Auto Root If set to Yes, can automatically create base
descriptors (XML only).
Catalog Setup POR: Hosted Images Directory Location of images that can be displayed in search
results.
Catalog Setup POR: Catalog Bulk Load Directory Temporary directory where bulk files are loaded
prior to processing.
Catalog Setup POR: Bulk Load for All Business Enable Global Loader. This feature allows users
Groups to load catalog content for all operating units even
those outside of the catalog administrator's
business group.
Catalog Setup POR: Bulk Load Extractor Commit Default commit size for Catalog extract
Size
Catalog Setup POR: Enable Advanced Search and Set this profile option if you are not using the local
Category Browse catalog, but are implementing only punchout or
transparent punchout catalogs.

Catalog Setup POR:Display Search Box and Browse If set to No, searching and browsing for items in
Categories the internal catalog is not allowed (the boxes and
relevant links are removed from the user
interface). Also, the Shopping tab is replaced with
the Supplier Site tab to display external. With the
addition of this profile option, internal realms are
no longer supported.
Catalog Setup POR: Show Thumbnail Images Show or Hide thumbnail images on search results
page
Catalog Setup POR:Search Governer Value Controls the number of search results requesters
can sort and filter. If the number of search results
is greater than the value specified in this profile
option, requesters will not be able to sort or filter
the results and they will have to narrow their
search prior to filtering and sorting.
Catalog Setup POR:Sort by Relevance Determines whether or not Quick Search results
can be sorted by relevance (rank...basically the

more keywords that match, the higher the rank).
This option is always available during an
expanded search.
Catalogs POR : Dtd Files Directory Dtd files absolute directory. For example.
oracle_stuff/XML/orc115.
Catalogs POR: Set Debug Catalog Loader ON Set this profile option to Yes or Yes with Detail
when you want to record debug messages in the
log file while bulk loading a catalog file—for
example, if you are experiencing problems with
the bulk loader or trying the bulk loader for the
first time. These messages can be viewed in the
Log screen in the Requests window. As soon as
you are finished debugging the problem, set this
profile option back to No, to minimize
performance issues. Default Value: No
The options are as follows:
■ No: The bulk loader records informational
messages, including parameters selected on the
Specify Options page before loading, and
information that the job has started, it is beginning
the index rebuild, and so on.
■ Yes: In addition to informational messages, the
bulk loader records debug messages that can help
identify problems.
■ Yes with Detail: In addition to informational
and debug messages, the bulk loader records line-
level debug messages. If you need to generate
SQL trace information to track loader performance
issues, choose Yes with Detail.

Agenda

Decide on a Catalog Source

Decide on a Catalog Source
We cannot overemphasize the importance of carefully analyzing your organization’s
procurement needs and then choosing the catalog that best fits those needs!
Commodities
• Direct material: Mass-produced mechanical parts; products with pre-negotiated or stable
material).
• Configured products: Products requiring high degree of configuration, such as computer
supplies.
• Indirect material: Office supplies; standard MRO items; products with non-stable
pricing.

Considerations when choosing a catalog model:
• Kinds of items requestors will order.
Buyer-hosted catalog provides a common user interface, and includes multiple suppliers’
items all in one place.
• Buyer-hosted catalog is inside the firewall.
• Do suppliers already send electronic agreements and quotations (EDI or XML)?
• Supplier-hosted and marketplace-hosted catalogs put the maintenance in the supplier’s
hands.
• Supplier-hosted and marketplace-hosted catalogs require more complex security.

Considerations for Local Catalogs

Considerations for Local Catalogs
• Think about where your items and categories are coming from: Oracle Purchasing,
suppliers (via upload files), or both?
• Will you use the descriptors provided by uploading to augment item information for items
extracted from Oracle Purchasing? If so, which descriptors will you use?
• Depending on your sources of local content, think about how you want to structure
categories in the catalog. Will you use UNSPSC codes? Will you use categories extracted
from Oracle Purchasing? Will you create your own categories and map these to categories
in Oracle Purchasing?
• Will requesters understand the category structure you’ve set up in Oracle Purchasing? If
not, you’ll need to create categories that a requester will more likely understand and map
these to Oracle Purchasing categories. Or, you can avoid mapping by setting up categories
in Oracle Purchasing that work for both buyers and requesters.
• Are the base descriptors that iProcurement provides enough, or do you need more? If so,
you can use XML schema uploading (or online schema editing) to add or change these.
• Do you need to create additional descriptors specific to certain categories? If so, use XML
schema uploading (or online schema editing) to add these.

• Do you need to create different pricing for different operating units? Use uploading to do
this.
• Decide whether or how to control users’ access to categories using realms.

Considerations for Supplier-Hosted Content

Considerations for Supplier-Hosted Content
• Decide on the punchout model you and your supplier can implement based on the
capabilities of the supplier and your own preferences.
• At a minimum you must map the supplier’s categories to your own categories (categories
in Oracle Purchasing). Figure out the mapping that needs to occur.
• You can also do supplier, supplier site, and UOM mapping, if the supplier uses different
values for these than you do. This is described in more detail in the Oracle Procurement
Buyer's Guide to Punchout and Transparent Punchout.
• Set up mapping in e-Commerce Gateway. (For via Exchange models, you can also use
Exchange to assist with the mapping.)

Considerations for Marketplace-Hosted Content

Considerations for Marketplace-Hosted Content
• If you use Oracle Exchange as your marketplace you can punch out directly to the
Exchange, to the myriad items that suppliers have loaded there. Or you can punch out
through the Exchange, enabling the supplier to define its punchout once on the Exchange
and enabling you (the catalog administrator at the buying company) to easily download it.
• If you will be using other third parties to manage your content determine how much you
want those third parties to manage: will they deliver files to you, which you then bulk
load? Or do they offer their own service that requestors in your system can access?
• Will you use punchout to access the third party’s Web site? Or does the third party offer
other mechanisms for ordering items from their system?

Considerations for Security

Summary

D50792GC10 sg1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D50792GC10 sg1

Uploaded by

Copyright:

Available Formats

Oracle Internal & Oracle Academy Use Only

R12 Oracle iProcurement

Restricted Rights Notice

U.S. GOVERNMENT RIGHTS

Oracle Internal & Oracle Academy Use Only

Richard Sears, Vic Mitchell

Technical Contributors and Reviewers

Barbara.Snyder, Sharon Tennier

This book was published using: oracletutor

Procure to Pay Lifecycle Overview ................................................................................................................1-1

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

• Thorough knowledge of the Oracle E-Business Procure to Pay process.

• Working experience with e Oracle E-Business Procure to Pay products.

• R12 Oracle Purchasing Fundamentals

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle iProcurement Implementation and Administration Guide B31402-01

Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout B13856-01

Oracle Payables User Guide B25454-01

Oracle Internal & Oracle Academy Use Only

• Installation and user’s guides

• International Oracle User’s Group (IOUG) articles

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Oracle Internal & Oracle Academy Use Only

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

Passwords DROP USER scott

Lowercase Syntax variables CREATE ROLE role

Oracle Internal & Oracle Academy Use Only

Typographic Conventions in Oracle Application Navigation Paths

This simplified path translates to the following:

2. (M) From the menu, select Query then Find.

3. (B) Click the Approve button.

(ST) = Sub Tab

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle iProcurement Fundamentals Table of Contents

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

2. Under the General Ledger entry, expand Journals.

Oracle Internal & Oracle Academy Use Only