Oracle® Project Procurement: Process Guide Release 12.2
Oracle® Project Procurement: Process Guide Release 12.2
Oracle® Project Procurement: Process Guide Release 12.2
Process Guide
Release 12.2
Part No. E53630-04
September 2015
Oracle Project Procurement Process Guide, Release 12.2
Copyright © 2014, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
iii
Releasing Plan Lines for Planning.......................................................................................... 3-28
Creating Purchase Requisitions.............................................................................................. 3-29
Index
iv
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: [email protected]
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
v
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle Project Procurement Process Guide.
Implementers, administrators, users
See Related Information Sources on page viii for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Structure
1 Overview of Oracle Project Procurement
The chapter discusses the functional advantages of Oracle Project Procurement and the
business entities that enable project managers and project buyers to collaborate plan
and process procurement actions.
2 Implementing Oracle Project Procurement
The chapter discusses the prerequisite products and the post-installation setup required
to use Oracle Project Procurement.
vii
3 Planning Procurement: Project Manager Actions
The chapter discusses the actions that a project manager can perform using the project
manager command center along with the Item Analysis and Supplier Analysis pages.
4 Processing Procurement: Project Buyer Actions
The chapter discusses the actions that a project buyer can perform using the project
buyer command center along with the Item Analysis and Supplier Analysis pages.
5 Analyzing Items and Suppliers
The chapter describes the Item and Supplier Analysis pages and highlights the
decisions that project managers and buyers can make using these pages.
6 Monitoring Procurement Execution
The chapter discusses examples that demonstrate how project managers and buyers can
use Oracle Project Procurement to monitor the progress of project procurement and
ensure that the project is insulated from various procurement delays and issues.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As
your instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
viii
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
ix
1
Overview of Oracle Project Procurement
The chapter discusses the functional advantages of Oracle Project Procurement and the
business entities that enable project managers and project buyers to collaborate plan
and process procurement actions.
This chapter covers the following topics:
• Overview
• Typical Users of Oracle Project Procurement
• Business Actions
• Business Entities
Overview
Oracle Project Procurement enables your project teams to establish and measure
strategic project objectives and drive project procurement planning, decision-making,
and execution throughout the lifecycle of the project. This product provides an
integrated platform for project managers and project buyers to create, view, and update
procurement plans so they have the information they need to make planning decisions
without the need to alert, notify, or engage in unproductive communication to execute
the plan. It breaks traditional functional silos and communication gaps between project
management and procurement by ensuring your project teams are on the same page at
all times in the lifecycle of the project.
Oracle Project Procurement provides the ability to share information about the project
needs and requirements with the buyer and information about procurement status with
the project manager. The product brings together project and procurement information
that is critical to aligning strategy with planning and execution. Project teams can
establish strategic objectives, drive down-stream decision making through these
objectives, and measure compliance with these objectives throughout the lifecycle of the
project.
Based on the power of Oracle Information Discovery, Oracle Project Procurement
provides interactive, information-based tools that enable the project and procurement
• Integrate execution based on a plan aligned to key objectives - The project teams can
use the integrated project-based supply chain execution that reduces wastage and
aligns delivery to key project and organizational objectives.
• Increase the quality of project deliverables by ensuring the right items are ordered,
services are procured or subcontracts arranged with the best suppliers that meet
your project or organization objectives.
Business Actions
Oracle Project Procurement can help project managers and project buyers complete the
following business actions:
• Collaborate effectively on project supply chain decisions through the project
lifecycle.
• Create and manage procurement plans that meet their project's acquisition strategy.
• Execute supply chain activities effectively using the project manager or project
buyer command centers to view project, task, or procurement transactions statuses.
• Analyze and negotiate service level agreements and pricing to optimize costs.
• Empower decision-making using the Item and Supplier Analysis pages to select the
best products, services, and suppliers.
• Discover project risks before they happen by leveraging the power of Oracle
Information Discovery.
• View and act on project procurement decisions without having to send notifications
or rely on workflows.
• View metrics that indicate if previous decisions are providing the required results
so that team member decisions are aligned with the procurement strategy for the
project.
Business Entities
Oracle Project Procurement provides the following business entities that enable project
managers and project buyers to collaboratively plan and process procurement actions:
• Compile and act on key project measures affected by the procurement plan status.
The project manager command center provides information to the project manager for
• Workload Balance – Graphs, charts, metrics, and tables help the project manager
know what work or decisions are the most important to address.
• Metrics – Graphs, charts, metrics, and tables help the project manager understand
the overall health of the project's budget, schedule, and quality with regards to the
status of the project and the procurement plan and services. .
For further information, see: Overview of Project Manager Actions, page 3-1.
• Identify sources of supply and associate them to procurement plan lines for
initiating requisitions or orders.
The project buyer command center provides information to the project buyer for
managing the project supply chain and is based on the project procurement plan. The
page is organized around the following key activities:
• Exceptions – Alerts guide the project buyer to critical actions that need to be taken
to address risks to the project procurement plan or schedule.
• Workload Balance – Graphs, charts, metrics, and tables help the project buyer know
what work or decisions are the most important to address.
• Metrics – Graphs, charts, metrics, and tables help the project buyer understand the
overall status of the procurement plan for the projects they are responsible for.
For further information, see: Overview of Project Buyer Actions, page 4-1.
Item Analysis
The Item Analysis page enables project managers and project buyers to select the
products and services that best suit the needs and objectives of the project. Using this
Supplier Analysis
The Supplier Analysis page enables project managers and project buyers to select the
best suppliers. This page provides additional information to the project managers and
project buyers when they need to analyze information about the suppliers who can
fulfill orders for a procurement plan line. Using this page, the project team can review,
compare supplier performance history, and select suppliers easily.
For further information, see: Analyzing Suppliers, page 5-9
The chapter discusses the prerequisite products and the post-installation setup required
to use Oracle Project Procurement.
This chapter covers the following topics:
• Prerequisites
• Setting Up Oracle Project Procurement
• Running the Full Load Graph
• Setting Up the Scheduler for Incremental Refresh
• Views and Joins to Load Command Center, Item Analysis, and Supplier Analysis
Data
• Responsibilities and Menu Navigation
Prerequisites
To use Oracle Project Procurement, you must have the following:
• Release 12.2.3 or above of Oracle E-Business Suite
• Oracle Sourcing – Provides the ability to create and manage supplier negotiations.
• Oracle Supplier Lifecycle Management and Oracle Supplier Hub – Provides the
ability to search suppliers using additional information, such as user-defined
attributes (UDAs).
• Oracle Inventory – Provides the ability to search and track inventory items.
• Oracle Payables – Provides the ability to view invoice and payment information.
Note: If you choose a date that is too far in the past, then the
amount of data to be loaded increases, resulting in longer
full-load and incremental-load times, and more memory
resources demanded by the Endeca server. If you select too
recent a date, then the insights might not be extensive or
accurate.
2. Set up access privileges for project manager and project buyer users as follows:
• For project buyer users, set up the following for the Project Procurement
(Buyer) responsibility:
• Role Name - UMX|PO_PSC_ENDECA_ACCESS_ROLE
See: Oracle E-Business Suite Security Guide and the 'steps to add product-specific
roles to responsibilities to provide user access to Endeca-related pages and
components in Oracle E-Business Suite' section in My Oracle Support note
1497685.1
3. Enable procurement planning on project templates that you intend to use for
creating projects that you will enable for Oracle Project Procurement. Use the
Project Template Setup page. See: Specifying Project and Task Options for a
Template, Oracle Projects Fundamentals Guide. The option value defaults to new
projects created from templates with procurement planning enabled.
4. Select a financial plan type for procurement reporting that the application uses to
compare actual results to planned values. You can select a predefined financial plan
type or a user-defined financial plan type. To create your own financial plan type,
see Financial Plan Types and Defining Financial Plan Type, Oracle Projects
Implementation Guide.
5. Enable a project for procurement planning. If the option value is not defaulted from
a template, then you can update the project setup option to enable procurement
planning for a project after it is created. You can only upload procurement plans or
view projects in the Oracle Project Procurement pages that have been enabled in the
project setup. Project managers can access the Setup page using the following
navigation: Projects: Delivery > Search Projects > Advanced Search > Search results
Note: Only projects that have shared structure are eligible for
procurement planning.
6. Ensure there is at least one record in excel before you run the Full Load Graph to
load applicable data from the data source to the Oracle Endeca ETL layer. See:
Running the Full Load Graph, page 2-4
7. Set up the scheduler for incremental refresh. See: Setting up the Scheduler for
Incremental Refresh, page 2-5
Optional Steps
1. You can use the predefined expenditure types or define applicable expenditure
types to specify in the procurement plan. See: Expenditure Types and Defining
Expenditure Types, Oracle Projects Implementation Guide.
3. Enable touch-less processing for purchase requisitions created from the Oracle
Project Procurement command center by setting up automatic sourcing. See: Setting
up Automatic Sourcing, Oracle Purchasing User's Guide.
5. Update the White List that appears in the Tag Cloud of the Item Analysis page.
Access the TagList.xlsx in Item sandbox (poprocitemetl.zip -> data-in folder) when
you run the full load graph and update the excel sheet as per your requirements.
4. Enter a Description for the scheduler, for example, Projects Full Load Scheduler.
7. Enter a start date and time in the Not active before date/time field.
8. Enter an end date and time in the Not active after date/time field.
10. Ensure you select the Fire misfired event as soon as possible check box.
12. Select po-proc, po-proc-item and po-proc-sup from the Sandbox list one after
another. Ensure to run the full load gragh for each of these sandboxes.
4. Enter a Description for the scheduler, for example, Projects Full Load Scheduler.
7. Enter a start date and time in the Not active before date/time field.
8. Enter an end date and time in the Not active after date/time field.
10. Ensure you select the Fire misfired event as soon as possible check box.
12. Select po-proc, po-proc-item, and po-proc-sup from the Sandbox list one after
another. Ensure to run the full load graph for each of these sandboxes.
Views and Joins to Load Command Center, Item Analysis, and Supplier
Analysis Data
The following views are used by the ETL layer in Endeca to load and display command
center, item analysis, and supplier analysis data to the Endeca data store:
• PO_ENDECA_BWC_PROCPLAN_V – View to extract procurement plan and
related document data for full load graph – po-proc
These views load data from Oracle Projects and Oracle Procurement (purchase orders,
agreements, negotiations, and supplier) into the ETL.
• Project buyers to use the Project Procurement (Buyer) responsibility and Command
Center menu item. The buyer command center serves as the starting point for
project procurement processing. Additionally, the Item Analysis and Supplier
Analysis menu items are available as sub-tabs in the Procurement menu.
For further details, see:
• Overview of Project Buyer Actions, page 4-1
The chapter discusses the actions that a project manager can perform using the project
manager command center along with the Item Analysis and Supplier Analysis pages.
This chapter covers the following topics:
• Overview of Project Manager Actions
• Creating a Project Procurement Plan
• Updating Project Procurement Plan
• Viewing Procurement Planning Information and Metrics
• Analyzing and Replacing Items to Procure
• Analyzing Sources of Supply
• Managing Project Procurement Exceptions
• Releasing Plan Lines for Planning
• Creating Purchase Requisitions
The project manager performs the project procurement planning related activities using
the project manager command center. The starting point of the command center is the
Project Search and Overview page. Project managers can search for projects and access
the command center for the selected project using the following navigation:
Projects: Delivery > Search Projects > Advanced Search > Search results > Click Project
Name link > Procurement tab to open the selected project.
From the command center, the project manager can access the following:
• Item Analysis and Supplier Analysis - All purchasing documents belonging to the
operating units that the project manager has access to.
• Actions: View Agreement, View PO, View Negotiation - Only those documents
belonging to the operating units that the project manager has access to. For
negotiations, security is governed by the operating unit in which the negotiation is
being created. For agreements, the application enables multiple operating units to
be assigned to a single agreement. Hence, project managers having access to any of
the assigned operating units can access the agreement. For purchase orders, if the
PO: Enforce Projects Security profile is set to Yes, project managers can access only
those purchase orders containing at least one project in the distribution to which the
project manager is a key member, and any other PO-level security.
• Update tasks: for the selected tasks in the task list of the command center, the
project manager can update multiple tasks or mass update a set of tasks using
actions from the table level drop down menu.
The project manager cannot directly access the buyer command center.
2. After you populate the interface tables, the script runs the Procurement Plan Import
(POPROCIMP) concurrent program automatically and returns the concurrent
request ID. Navigate to the concurrent program window or the Procurement plan
page to check whether there are any errors in uploading of a proc plan or it was
uploaded successfully. If this program fails, then the application displays
Complete-Error status in the Procurement Plan page. Use the Request Number link
to check the list of errors and take appropriate action. Additionally, you can view if
there are errors using l_interface_txn_id:
SELECT * FROM PO_INTERFACE_ERRORS WHERE
INTERFACE_TRANSACTION_ID=l_interface_txn_id ;
/* Insert data into the Prog payment interface table for the fixed price
lines */
commit;
po_proc_plan_pub.proc_plan_import_submit(
x_req_id => l_request_id,
x_interface_txn_id => l_interface_txn_id,
p_batch_id => l_batch_id,
p_project_id => l_project_id
);
Dbms_Output.PUT_LINE('l_request_id : '||l_request_id);
end;
------------------------------------------------------------------------
-----------------------------------------------------------
PO_PROC_PLAN_HDR_INTERFACE Table
PO_PROC_PLAN_LINE_INTERFACE Table
PROJECT_ID Project ID
PO_PROC_PLAN_PROG_INTERFACE Table
PO_NUMBER PO Number
BATCH_ID Batch Id
PROJECT_ID Project id
CREATED_BY Created By
• plan_end_date
• plan_name
• project_nameorg_id
• batch_id
• project_id
• lock_update_date
• line_number
• category
• item_number
• item_number
• status
• expenditure_type
• planning_currency_code
• planning_rate
• uom
• batch_id
• project_id
• plan_name
• PO_PROC_PLAN_PRD_INTERFACE:
• schedule_number
• line_number
• task_number
• location
• period_name
• quantity
• batch_id
• project_id
• plan_name
• PO_PROC_PLAN_PROG_INTERFACE:
• Payment_type
• Pay_description
• Need_by_date
• Pay_amount
• Pay_price
• Pay_item
• batch_id
• project_id
• plan_name
• line_number
• task_number
Note: The application populates the columns for which you do not
have to mandatorily enter values while inserting data into the interface
tables.
Using Spreadsheet
To create a procurement plan using a spreadsheet:
1. In the Project Search page, click on Advanced Search. From the search results, click
the Project Name link to select a project, and then open the Procurement tab.
2. Select the applicable project and click the Procurement link to open the
Procurement Plan page.
3. For projects that do not contain procurement plans, the Procurement Plan page
displays the Create Procurement Plan button. Click the Create Procurement Plan
button to open the Create Procurement Plan page for the selected project.
• Using spreadsheet
2. Make the changes and follow the steps discussed in Creating a Project Procurement
Plan > Using Interface Tables topic.
When you enter an existing procurement plan number, the application assumes that
you are updating the plan. You can update the following fields when the plan line
is in Draft status:
• Line Type
• Category
• Item Number
• Suggested Supplier
• Additional Information
• Expenditure Type
• Planning Currency
• Planning Rate
• Task Number
• Location
• Monthly Requirements
2. For projects that already have an existing procurement plans, the Procurement Plan
page displays the Update Procurement Plan button. Click the Update Procurement
Plan button to open the Update Procurement Plan page for the selected project.
Ensure you enter a start and end date.
4. Unzip the archive and extract the XML spreadsheet document in a local folder. If
you use Microsoft Windows and Microsoft Office Excel, then double-clicking the
file opens the spreadsheet in Microsoft Office Excel. If you are not able to open the
file with this method, or if the file opens in a different application, then you can
make a file- type association by right-clicking the extracted XML file and selecting
the option Open With > Choose Program > Microsoft Office Excel.
5. Update existing lines and monthly requirements or add new lines. Please read
through the Readme file available in the downloaded zip archive to understand
how each field in the excel sheet is validated and populated.
6. Once all changes are made, use Save or Save As option to save the file in the same
format. If the system prompts you, then choose to save the workbook in the same
format.
7. To upload the excel sheet, click Browse in the Update Procurement Plan page for
the selected project, select the file that was just saved, and click Upload.
Heading Region
The heading region of the page displays the following:
• Project Name
• Project Number
Selected Refinements
The Selected Refinements component displays all values that you have selected to filter
data, and allows you to quickly make adjustments to the current refinement by
removing items or clearing all filters from the list.
Bookmarks
The Bookmarks component allows you to save a given navigation and component state
and return to it at a later time.
Available Refinements
The Available Refinements component allows you to filter data based on the currently
available values or value ranges for selected attributes that are displayed within
attribute groups. Expand the attribute groups to view and select attribute names.
Metrics Region
The page has two metric sections:
Work
Plan Lines Total plan lines for the procurement plan of the
project
Ready For Planning Ready for Planning for procurement planning lines of
the project
Budgeted Cost (PC) Total burdened cost from the plan type associated to the
project for procurement planning
Planned Procurement Cost (PC) Total cost of the planned amounts from the procurement
plan lines
Services
Progress Payments Total amount paid for the Progress of Work against the
Project
Progress Percentage The total amount paid for the progress of work by the total
amount allotted for the work for the Project
Exceptions Region
This region displays the following:
Items with delayed shipments Items with delayed shipments (not yet delivered)
Items past Order by Date but not ordered Items not ordered
Purchase Orders with Promised Date Delivery dates beyond my Need by Date
beyond Need by Date
Unplanned Purchases POs/orders places for items that are not in the
procurement plan
Invoices on Hold Invoices created for the Projects that are put on
hold due to non receipt of the deliverables
Deliverables Overdue Deliverables with the due dates earlier than the
system date for the Project
Quantity requested
Quantity ordered
Quantity received
Quantity invoiced
Quantity rejected
Total quantity
Plan Lines Schedule Planning amount by period for line status: Draft, Ready for
Status Planning, Ready to Order
Task by Start Planning Task not started that have passed the scheduled start date
Date Status
Actual Over Financial Quantity ordered by period for the items on the project
Planned
Product Item Planned items and ordered items for the project
Variety
- Requested Amount
- Ordered Amount
- Invoiced Amount
Average Lead Progress Average lead time by Item Description. Lead Time in the
Time Payments average number of days needed to procure the service. The
lead time includes pre-ordering, Ordering and Post-ordering
lead time. Lead time is obtained from the Sources of Supply.
• Plan lines – the plan lines for the tasks in the tasks sub-tab
• Schedule – the schedule of item quantities in the procurement plan for the lines in
the plan lines sub-tab
• Sources of Supply – the sources of supply authorized by the buyer for the plan lines
• Mass Tasks Update – You can select multiple task rows and select the 'Mass
Tasks Update' action for task in current working version.
• Mass Update Progress – You can select multiple task rows and select the 'Mass
Update Progress' action for task in latest published version.
• In the Plan Lines tab, you can select multiple lines and select Make Lines Ready for
Planning action using the Actions option available on the right side of the Plan
Lines table. You can also use Add to Shopping Cart from the Actions menu to
create requisitions for Service lines. Additionally, in the Plan Lines tab, if Actions is
selected in the column set dropdown menu, you can analyze items and suppliers.
See: Analyzing and Replacing Items, Analyzing Sources of Supply topics.
• In the Schedules tab, you can select multiple lines and select Add to Shopping Cart
action using the Actions option available on the right side of the Schedule Details
table.
• Agreements
• Requisitions
• Orders
• Deliverables
Select Actions in the column set dropdown menu and view these purchasing
documents from the respective sub-tabs.
3. Click the Analyze Item link to open the Item Analysis page.
4. The Item Analysis page provides a summary of the procurement history of the item
or service, including current orders and suppliers. You can use the Search Box on
this page to look for alternatives.
5. If you find an alternative item that works better for this project, then select the item
in the Item Summary > Item Details > Details table and click Compare with
Procurement Line action available on the right side of the Details table.
6. If you find an alternative item or service that works better for this project, then
select the item in the Item Summary > Item Details > Details table and click
Compare with Procurement Line action available on the right side of the Details
table.
3. Click the Analyze Supplier link to open the Supplier Analysis page.
4. Use the information displayed in the Supplier Analysis page to view the
performance history of the supplier and compare the suppliers.
For further information regarding Supplier Analysis page, see: Analyzing Suppliers,
page 5-9.
5. Scroll right to the Actions option available on the right side of the Plan Lines table.
6. Select Mark Lines Ready for Planning action to indicate to the project buyer that
they can start finding suppliers for the item or service that is best suited for the
project.
4. Scroll right to the Actions option available on the right side of the Plan Lines table.
4. Scroll right to the Actions option available on the right side of the Plan Lines table.
As Oracle Project Procurement is integrated with Oracle iProcurement, the selected plan
lines, quantities, budget amounts, task, and expenditure type details are populated
automatically. If you have enabled touch-less processing in Oracle Purchasing, then the
application automatically creates and approves the associated standard purchase orders
for all purchase requisitions that get approved with an agreement link. If you have not
enabled touch-less processing, then the project buyer needs to find these purchase
requisitions in the Alerts section of the project buyer command center and place an
order.
The chapter discusses the actions that a project buyer can perform using the project
buyer command center along with the Item Analysis and Supplier Analysis pages.
This chapter covers the following topics:
• Overview of Project Buyer Actions
• Reviewing Project Procurement Plan
• Analyzing Items for a Plan Line
• Analyzing Suppliers for a Plan Line
• Creating and Publishing a Negotiation
• Comparing Suppliers and Awarding
• Reviewing Sources of Supply
• Updating Plan Lines
• Creating Sources of Supply
• Updating Sources of Supply
• Analyze Items
The project buyer is responsible for ensuring that the project is successfully executed
and all the objectives of the project are met. To achieve this, they need to ensure that the
right material or service is procured at the right price, and made available at the right
location, with the right quality at the right time. The buyer uses the project buyer
command center to take all decisions related to planning and execution of procurement
activities on the project. The command center provides information to the project buyer
for managing all procurement activities on the project, and is based on the procurement
plan for all the projects the buyer is responsible for.
Use the Project Procurement (Buyer) responsibility to access the command center.
From the command center, the project buyer can access the following:
• All plan lines and procurement documents created in operating units that the buyer
has access to. Additionally, if PO: Enforce Projects Security profile is set to Yes, then
the buyer can access plan lines and related information only for those projects
where the buyer is defined as a key member.
• Item Analysis and Supplier Analysis pages- All purchasing documents belonging to
operating units that the buyer has access to.
• Actions: View Agreement, View PO, View Negotiation - Only those documents
belonging to the operating units that the buyer has access to. For negotiations,
security is governed by the operating unit in which the negotiation is being created.
For agreements, the application enables multiple operating units to be assigned to a
single agreement. Hence, buyers having access to any of the assigned operating
units can access the agreement. For purchase orders, if the PO: Enforce Projects
Security profile is set to Yes, buyers can access only those purchase orders
containing at least one project in the distribution to which the buyer is a key
member. Additionally, further security rules apply if you have set up security rules
in the individual products and documents.
The project buyer has no access to the project manager command center.
Heading Region
The heading region of the page displays the date/time stamp of last the ETL update
(your time-zone)
Search Region
The Search component allows you to submit keyword searches and provides
type-ahead suggestions displaying attribute values that match the typed text. When you
perform a search, the search term is added to the Selected Refinements component. As
you type, you may be prompted to select a matching attribute value, or simply search
for the entered text.
Selected Refinements
The Selected Refinements component displays all values that you have selected to filter
data, and allows you to quickly make adjustments to the current refinement by
removing items or clearing all filters from the list.
Bookmarks
The Bookmarks component allows you to save a given navigation and component state
and return to it at a later time.
Available Refinements
The Available Refinements component allows you to filter data based on the currently
available values or value ranges for selected attributes that are displayed within
Metrics Region
The page has three metric sections:
Work
Services
Exceptions Region
The following alerts convey exceptions that a project buyer needs to address
immediately:
• Items past order-by-date (order-by-date on a schedule is in the past, but all planned
quantity is not requested yet)
• Items overdue (need-by-date on a purchase order is in the past, but all ordered
quantity is not received yet)
• Invoices on Hold (Invoices created for the Projects that are put on hold due to non
receipt of the deliverables)
• Deliverables Overdue (Deliverables with the due dates earlier than the system date
for the Project)
This region displays charts and graphs for the following sub-tabs:
• Planned Amount
• Procurement Status
• Planning Status
• Procurement Spending
• Supplier Measures
• Item Measures
Planned Amount Planned Amount Spread When all plan lines have the
same functional currency, the
planned amount can be sliced
by item category (then item
description),
Deliver-to-location or
Expenditure type.
- Requested Amount
- Ordered Amount
- Invoiced Amount
- Retainage Amount
- Paid Amount
Progress Payment Summary Lead Time by Items Average lead time by Item
Description. Lead Time in the
average number of days
needed to procure the service.
The lead time includes
pre-ordering, Ordering and
Post-ordering lead time. Lead
time is obtained from the
Sources of Supply
• Schedule – The schedule of dates/quantities for each line in the plan lines sub-tab
• Sources of Supply – Sources of Supply identified by the buyer for the lines in the
Plan Lines sub-tab
• Projects – the projects associated to the lines displayed in the Plan Lines sub-tab
• In the Sources of Supply tab, you can select multiple lines and select Update
Sources of Supply action using the Actions option available on the right side of the
Schedule Details table. See: Updating Sources of Supply
• Agreements
• Requisitions
• Orders
• Deliverables
Select Actions in the dropdown menu and view these purchasing documents from the
respective sub-tabs. Depending on the access privileges, project buyers can view these
documents and any action the buyer has the authority to take on those documents are
available to them from the applicable pages. Buyers can view the negotiation, proceed
to compare, and award the suppliers. See: Comparing and Awarding Suppliers.
3. Click the Analyze Item link to open the Item Analysis page. The Item Analysis page
provides a summary of the procurement history of the item or service.
3. Click the Analyze Supplier link to open the Supplier Analysis page.
4. Analyze the comparative performance of the suppliers using the Compare action
available on the right side of the Suppliers table in the Supplier Analysis page.
2. Add suppliers and plan lines to the document builder. You can add plan lines and
suppliers to the document builder in the following ways:
• Select Analyze Supplier on a particular plan line to open the Supplier Analysis
page in the context of a plan line. Select one or more suppliers in the suppliers'
results table and use the Add to Document Builder action. The application adds
the selected suppliers and the plan line in context to the document builder. The
application displays a confirmation message informing you about the number
of plan lines and suppliers added to the document builder. You can add more
plan lines and suppliers by using the appropriate action from the buyer
command center and Supplier Analysis page.
• Select one or more plan lines from the command center and use the Add to
document builder action. The application adds the selected plan lines to the
document builder.
• Select one or more suppliers from the Supplier Analysis page (when not in
context) and use the Add to document builder action. The application adds the
selected suppliers to the document builder.
3. In the Document Builder, specify the negotiation type and outcome document. By
Note: The application displays the operating unit that is set in the
MO: Default Operating Unit profile. All negotiation styles enabled
for RFQ are available for you to select. The outcome documents can
be of any style linked to the blanket purchase agreement document
type. The Supplier Site and Contact list of values are similar to the
values in the Sourcing Supplier tab. The application defaults Group
Line Number using the document builder grouping rules. You can
ungroup the grouped lines, or attempt to group lines that the
auto-grouping logic of document builder did not pick up. Manual
grouping of lines is subject to validations existing in the current
document builder.
4. Click Cancel to go back to the page from where you launched the document
builder.
5. Select Apply. This initiates a negotiation in Oracle Sourcing. You are taken to the
draft Negotiation page and the application establishes the linkage to the negotiation
line as a source of supply. From within Oracle Sourcing pages, enter other details
for the negotiation and publish it. See: Oracle Sourcing Implementation and
Administration guide and Oracle Sourcing User guide Note: For a negotiation that
is in Draft status, you can add suppliers to the negotiation from the Sourcing pages
using the Add Suppliers button. This brings you to the Supplier Analysis page.
Analyze the suppliers, select them, and then add them using the Add to
Negotiation action available on the right side of the Suppliers table in the Supplier
Analysis page. If you delete the negotiation line after creating it through the
document builder, then the application removes the linkage of the negotiation line
as a source of supply. During the award completion stage, the application updates
the sources of supply when a particular negotiation line is awarded to a supplier
(multiple suppliers).
2. The buyer identifies the lead time and associates the lead time to plan line using the
Source of Supply page, and updates the Update Procurement Plan action to update
the status to Ready to Order.
3. The Project Manager now creates a requisition for the plan line.
4. The buyer now adds that requisition to the Document builder and creates a
5. The Purchase Order is available from the Deliverables tab, where you can view any
exceptions that might occur such as Deliverables Overdue or Invoices on Hold.
5. Select negotiations with Closed status and click View Negotiation link. This takes
you to the Negotiation page.
6. Select the Award by Quote action to open the Award by Quote page.
7. Select multiple offers and select Compare Suppliers button in the Award by Quote
page. This opens the Supplier Analysis page with the selected offers' suppliers
pre-filtered.
9. After analyzing the suppliers, scroll-down and click Return to Previous page. This
brings you back to the Negotiation page.
10. Select a supplier or multiple suppliers, if you want to split the award, and proceed
to complete the award process. For information regarding the awarding process, see
Awarding in different ways, Oracle Sourcing User guide.
2. In the Plan Lines tab, select plan lines with Ready for Planning or Ready to Order
status. You can select multiple lines.
4. Update the status by selecting Ready to Order from the drop down list in the
Update Procurement Plan Lines page and click Apply to indicate that the planning
exercise for the selected plan lines is completed.
5. Update the buyer to assign a different buyer or reassign the selected plan lines to
yourself and click Apply. Buyer can be any active buyer enabled in the operating
unit accessible to the project buyer updating the procurement plan status. If you
leave either the Status or Buyer field blank, then the application leaves it blank for
the selected plan lines. On selecting a status or a buyer or both, the application
updates all selected plan lines with the specified value. It displays a confirmation
message and returns the control back to you.
6. If you click Add More Lines, then the application takes you back to the command
center where you can select more plan lines and click Update Procurement Plan
action.
7. If you click Cancel, then the application removes the lines and they do not
re-appear unless you select those lines again to be added back to this page.
8. If you remove all records, then the application disables the Apply button.
2. Select plan lines with Ready for Planning and Ready to Order status. You can select
multiple lines.
• Agreement Line Number: Lists all agreement lines for the selected GBPA.
Additionally, the list of values displays item description, price and validity date
for each agreement line. If lead time is specified in the GBPA line, then the
application populates it. The application defaults the effective from-and-to
dates from the GBPA.
• If all selected plan lines have the same inventory item with same description
and category, then the application enables the agreement/agreement line
number.
• Lead time: Any positive integer value. The application uses the lead time that
you specify here later to prompt the project manager to create requisitions. It
calculates the order-by-date by subtracting the lead time from need-by-date,
and alerts the project manager if requisitions are not created by the
order-by-date.
• Effective From / To: Applicable dates (application does not time stamp).
Effective dates signify the validity of the source-of-supply line. If a source of
supply is valid and effective when the project manager creates requisition, then
the application stamps the blanket agreement identified as source of supply on
to the requisition. The negotiated price flows from the blanket agreement to the
requisition line. If multiple sources of supply are effective for a single plan line
at the same time, or if no sources of supply exist, then the application creates
requisitions without blanket agreement reference.
The Current Sources column lists the number of sources of supply existing for
the line. If it is non-zero, then a pop-up window appears on mouse-over to
5. Click Apply. You can review the sources of supply in the Planning Documents tab >
Sources of Supply sub-tab of the buyer command center. See: Reviewing Sources of
Supply.
6. If you remove all records, then the application disables the Apply button.
Note: The application enables the Agreement Number field only if all
plan lines added are for the same inventory item, or for
description-based items for the same category. Otherwise, you can
enter only supplier and lead-time. If plan lines are for an inventory
item, then the Agreement list of values displays only those blanket
agreements that have at least one active agreement line for the same
inventory item. If plan lines are for description based item, then the
Agreement list of values displays only those agreements that have at
least one active agreement for the same purchasing category. In cases
where the lead-time and effective dates default from the
agreement/agreement line, the buyer can change these values.
Note: You can only update the Source of Supply for goods lines.
3. Select Update Sources of Supply action available in the Actions option on the right
side of the Sources of Supply table.
4. Enter applicable details in the Update Sources of Supply page and click Apply.
Note: If plan lines are for an inventory item, then the agreement list
of values displays only those blanket agreements that have at least
one active agreement line for the same inventory item. If plan lines
are for description based item, then the agreement list of values
displays only those agreements that have at least one active
The chapter describes the Item and Supplier Analysis pages and highlights the
decisions that project managers and buyers can make using these pages.
This chapter covers the following topics:
• Analyzing Items
• Analyzing Suppliers
Analyzing Items
Project managers and buyers can analyze items or services to procure for a project using
the Item Analysis page. The Item Analysis page is centered upon items that have been
ordered for a project in the past. It brings in historically segregated, structured, and
unstructured data from purchasing document attachments about the item and makes it
available to you in a way that enables quick decision making.
Item Analysis page provides additional information to the buyer and project manager
when they need to analyze the items or services assigned to a procurement plan line.
When they click on Analyze Item for a plan line, the application carries the context of
the plan to the Item Analysis page and pre-filters the page with the item or service
number and description. If the page is accessed directly from the menu, no automatic
filters are applied. This page provides all the current and historical procurement
information of items in one page.
Project managers or buyers can assess the risk of procuring an item or service by
looking at past history. For example, if an item or service has had quality issues in the
past, they can anticipate that they might probably encounter quality issues in the future.
Additionally, the Item Analysis page displays availability information and provides
insight into other projects that have procured or planning to procure a given item or
service. The Search functionality in this page enables the project team to find an item or
service by entering keywords as textual content from attachments is also available for
search. The consolidated information regarding items enables the project manager or
buyer to determine if they are buying the right item or service, if there are viable
alternatives, determine most appropriate budget for the item or service, and determine
Item Analysis Trend Analysis - Total Spend Total spend refers to the sum
Vs. Off Contract of purchase order line
amounts. Off contract spend
refers to those purchase order
lines which do not have BPA/
CPA reference. The graph
only renders when there is a
single value for currency code
chosen either explicitly or
implicitly.
Spend Analysis Total Spend Spread - Total Split total spend data by item
Spend by Category categories. This is the default
Spend Analysis graph. The
graph only renders when
there is a single value for
currency code chosen either
explicitly or implicitly.
Spend Analysis Total Spend Spread - Total Split total spend by deliver to
Spend by Deliver to Location location on purchase order
shipments. The graph only
renders when there is a single
value for currency code
chosen either explicitly or
implicitly.
Spend Analysis Total Spend Spread - Total Split total spend by item
Spend by Item Description description (comprises both
inventory items and
description based items). The
graph only renders when
there is a single value for
currency code chosen either
explicitly or implicitly.
Spend Analysis Total Spend Spread - Total Split total spend by supplier
Spend by Supplier name. The graph only renders
when there is a single value
for currency code chosen
either explicitly or implicitly.
Spend Analysis Contract Vs Off Contract Total spend refers to the sum
Spend Spread Contract of purchase orders line
Spend, Off Contract Spend by amounts. Off contract spend
Category refers to those purchase order
lines which do not have BPA/
CPA reference. The graph
only renders when there is a
single value for currency code
chosen either explicitly or
implicitly. The x-axis shows
the category code, and Y axis
is the stack comprising
contract and off contract
spends.
• The Price and Spend option displays currency, unit price details, total spend
with and without BPA/CPA reference and the sum of contract and off contract
spend.
• The Lead Time option displays the lead time details for the selected item.
• The Projects tab displays the summary of the projects for which the item or service
has been planned or ordered.
• The Approved Suppliers List tab displays the approved suppliers for the selected
item or service and enables the project manager and buyer to analyze the suppliers
using the Action drop down menu.
• Agreements
• Requisitions
• Orders
Select Actions in the column set drop down menu and view these purchasing
documents from the respective sub-tabs. Project managers can only view these
documents. Project manager's access to these documents is based on the access rules
governed by the prevailing Oracle Purchasing setup and responsibilities assigned to the
project manager. Project buyers can edit or take action on the individual purchasing
documents based on the access restrictions set up within Oracle Purchasing and the
responsibilities assigned to the buyer.
• Project buyers can compare an item with the item specified on the procurement
plan for analysis purposes using the Compare with Procurement Line action
available on the right side of the Item Details table. See: Analyzing Items for a Plan
Line, page 4-11.
Analyzing Suppliers
Project managers and buyers can analyze suppliers who can supply items or service for
a project using the Supplier Analysis page. The Supplier Analysis page is based upon
suppliers, bringing in data sources from multiple modules together in one page to help
gain insight about the performance of the supplier, the relationship your organization
has with the supplier, and how one supplier compares to others.
Historical procurement information provides great insight into the on-time delivery,
quality and price-compliance trends of the supplier, and also provides quick summary
of the relationship your organization has had with the supplier. If you have installed
Oracle Supplier Lifecycle Management or Oracle Supplier Hub and have configured
user defined attributes for suppliers, then the powerful search and filtering features of
Oracle Endeca make it easy to find the right supplier using all the extensive information
you have collected about the supplier, such as insurance, environmental compliance,
financial stability, or quality maturity information. You can be sure you are selecting the
best suppliers when you use the analysis page to investigate each supplier's history.
Buyers and project managers can also see the current status of a supplier, including
which projects have orders, negotiations or any existing agreements with a supplier,
how much has been spent or is committed to be spent with the supplier and how well
the supplier has performed with regards to supplying the ordered items or services.
Project managers can access the page by clicking on Analyze Supplier from
Procurement Plan, Plan Line tab. Project buyers can access the page by clicking on
Analyze Supplier from buyer command center and Add Supplier from RFI/RFQ Invited
Suppliers page. They can directly access the page from the Supplier Analysis menu.
Additionally, project buyers can access this page as follows:
• From Offer Comparison and Evaluation pages, the advanced supplier search pages
are accessible to compare supplier's performance based on selected parameters and
buyers can choose the most suitable supplier. When project managers access the
Supplier Analysis page using this option, the Supplier Analysis page is pre-filtered
for the list of suppliers whose offers are being compared.
Essentially, the Supplier Analysis page offers a dashboard to the Supplier Management
User, providing the following:
• Ability to receive alerts that needs the supplier manager's attention for example,
when a payment hold is placed on a supplier.
• Quantitative aspects are measured from transaction data. The following are
considered in the current release:
• On-time delivery performance
• Ability to select suppliers from the result list, notify them or create RFx directly
from this page.
• On-hold suppliers: Total number of suppliers who have at least one active hold
(hold all payments, hold all purchase orders etc).
• Change requests - total number of supplier initiated change orders (all statuses).
• Ordered items - total number of unique items ordered from the selected list of
suppliers.
Approved Supplier Lists Approved and Local Shows total spend on the
Suppliers project split by approved
versus unapproved suppliers
(ASL) or by local versus
non-local suppliers (supplier
country versus task location)
by period (year / month).
Chart does not display data
when there are multiple
functional currencies.
• The Relationship tab in this region displays the active purchase orders, blanket
purchase agreements, and negotiations. Additionally, it displays holds applied on
active documents, total count of orders, total spend, number of negotiations in
which a selected supplier participated, negotiations in which the selected supplier
was awarded, average spend per year, receipt and use details.
• The Addresses tab in this region displays address details of the selected supplier.
• The Projects tab displays the projects for which the supplier is associated to a
purchasing document. The Approved Supplier List displays the ASL approval
status, item, supplier category, and manufacturer details of approved suppliers.
Documents Region
This region displays details of the following purchasing documents associated with the
suppliers:
• Agreements
Select Actions in the column set drop down menu and view these purchasing
documents from the respective sub-tabs. Project managers can only view these
documents. Project buyers can view the negotiation, proceed to compare, and award the
suppliers. See: Comparing Suppliers and Awarding, page 4-15.
• Compare two or more agreements using the Compare action available on the right
side of the Agreements table.
• Select one or more agreements and compare with the plan line in context using the
Compare with Demand action available on the right side of the Agreements table.
When no plan line exists in context, the application displays an error. The basic
requirement for comparison are as follows:
• If the plan line has an inventory item, comparison is possible only with
agreement lines of the same item.
• If the plan lines has a description-based item, comparison is possible only with
description-based agreement lines of the same category.
• If you do not want to retain the context of the plan line, then you can click
Remove to remove the plan-line context.
• The Create Source of Supply action is available only to the project buyer. Buyers
can click the '+' icon which takes them to the Create Source of Supply page for
the plan line, where all information is defaulted. Click Apply or make
applicable changes and then click Apply.
• Add to Document Builder - Using this action, you can add one or more suppliers to
the document builder. When you perform this action with a plan line in context, the
application adds the plan line to the document builder along with the selected
suppliers. If you add a supplier who is already added to the negotiation, then the
application displays a warning message. You can add suppliers to the document
builder from the Invite Suppliers page using the Add to Invite List action available
on the Supplier Overview page.
• Add to Negotiation - You can add a plan line to a draft negotiation using this
action. The application groups the additional quantity arising out of this plan line
with the selected negotiation line, and establishes a link between the plan line and
negotiation line.
The chapter discusses examples that demonstrate how project managers and buyers can
use Oracle Project Procurement to monitor the progress of project procurement and
ensure that the project is insulated from various procurement delays and issues.
This chapter covers the following topics:
• Reviewing Procurement Status
• Reviewing Exceptions
• Insulating Project Schedule from Material Delivery Delays
• Keeping Project On-Track by Monitoring Material Availability
• Ensuring that Project Strategic Objectives are Met
Reviewing Exceptions
Review alerts to find potential problems and take corrective action. The conditions
causing the alert must be resolved in order for the alert to be disabled. Alerts display:
• Items past need-by-date but not received yet. This alert indicates that the items have
not been received on-time.
• Items past order-by-date but not ordered. This alert indicates that any further delay
in submitting requisitions could potentially cause delivery delays.
• Progress Payments Overdue. This exception indicates Service Lines with delayed
progress reporting (Progress not yet processed).
• Invoices on Hold. This exception indicates invoices created for the Projects that are
put on hold due to non receipt of the deliverables.
• Deliverables Overdue. This exception indicates deliverables with the due dates
earlier than the system date for the Project.
Exceptions help you view and assess the problems and exceptions on the project before
they actually cause schedule delays or wastage. Click on these exceptions to see the plan
lines with an exception, and quickly resolve the problems even before they occur.
See: Viewing Procurement Planning Information and Metrics, page 3-19 and Reviewing
Project Procurement Plan, page 4-3 .
A E
Analyzing and Replacing Items to Procure Ensuring Project Strategic Objectives are Met
Oracle Project Procurement, 3-27 Oracle Project Procurement, 6-3
Analyzing Items
Oracle Project Procurement, 5-1 I
Analyzing Items for a Plan Line
Insulating Project Schedule from Material
Oracle Project Procurement, 4-11
Delivery Delays
Analyzing Sources of Supply
Oracle Project Procurement, 6-2
Oracle Project Procurement, 3-28
Analyzing Suppliers
K
Oracle Project Procurement, 5-9
Analyzing Suppliers for a Plan Line Keeping Project On-Track by Monitoring
Oracle Project Procurement, 4-12 Material Availability
Oracle Project Procurement, 6-2
B
M
Business Actions
Oracle Project Procurement, 1-3 Managing Project Procurement Exceptions, 3-28
Business Entities
Oracle Project Procurement, 1-4 O
Overview
C Oracle Project Procurement, 1-1
Comparing Suppliers and Awarding Overview of Project Buyer Actions
Oracle Project Procurement, 4-15 Oracle Project Procurement, 4-1
Creating and Publishing a Negotiation Overview of Project Manager Actions
Oracle Project Procurement, 4-13 Oracle Project Procurement, 3-1
Creating a Project Procurement Plan
Oracle Project Procurement, 3-2 P
Creating Purchase Requisitions Prerequisites
Oracle Project Procurement, 3-29 Oracle Project Procurement, 2-1
Creating Sources of Supply
Oracle Project Procurement, 4-16
Index-1
R
Releasing Plan Lines for Planning
Oracle Project Procurement, 3-28
Responsibilities and Menu Navigation
Oracle Project Procurement, 2-7
Reviewing Exceptions
Oracle Project Procurement, 6-1
Reviewing Procurement Status
Oracle Project Procurement, 6-1
Reviewing Project Procurement Plans, 4-3
Reviewing Sources of Supply
Oracle Project Procurement, 4-15
Running the Full Load Graph
Oracle Project Procurement, 2-4
S
Setting Up
Oracle Project Procurement, 2-2
Setting up the Scheduler for Incremental Refresh
Oracle Project Procurement, 2-5
T
Typical Users
Oracle Project Procurement, 1-3
U
Updating a Project Procurement Plan, 3-17
Updating Plan Lines
Oracle Project Procurement, 4-16
Updating Sources of Supply
Oracle Project Procurement, 4-18
V
Viewing Procurement Planning Information and
Metrics
Oracle Project Procurement, 3-19
Views and Joins
Oracle Project Procurement, 2-6
Index-2