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:
Oracle Project Procurement Command Center Plus enables project managers to perform the following actions:
Create a Project Procurement Plan
Update a Project Procurement Plan
View Procurement Planning Information and Metrics
Analyze and Replace Items to Procure
Analyze Sources of Supply
Manage Project Procurement Exceptions
Release for Planning
Create 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 Advanced Project Planning and Control interface. Project managers can also 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.
Oracle Project Procurement Command Center Plus enables you to create a procurement plan and specify a monthly delivery schedule for the items and services associated to the plan lines using one of the following two methods:
Use the interface tables to transfer data automatically
Manually enter the data into a spreadsheet
To transfer procurement plan data automatically:
Insert data into the following interface tables using the sample script:
po_proc_plan_hdr_interface: Holds the header information such as Project Name, Description, Start date, End Date and Duration
po_proc_plan_line_interface: Holds the plan line details
po_proc_plan_prd_interface: Holds the monthly requirements details
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 ;
Use the following sample script to insert data into the interface tables and invoke the public API to create the plan. This script assumes that the project is effective for duration of one year. Based on the effective dates of the project, the number of rows to be inserted into po_proc_plan_period_req would change. Ensure you modify the task number and expenditure types needed for the project procurement plan to insert the proper data.
-----------------------------------------------------------------------------------------------------------------------------------
declare
x_return_status VARCHAR2(1);
l_request_id NUMBER;
l_batch_id NUMBER := 1;
l_errbuf varchar2(100);
l_retcode varchar2(1);
l_interface_txn_id NUMBER;
CURSOR C_BATCH IS
SELECT MAX(BATCH_ID) + 1
FROM po_proc_plan_hdr_interface;
l_project_name VARCHAR2(120) := 'Hyd Metro East';
l_project_id NUMBER;
l_org_id NUMBER;
l_start_date date;
l_end_date date;
CURSOR c_project_id IS
SELECT project_id,Nvl(start_date, nvl(scheduled_start_date,sysdate-1)) start_date,
Nvl(completion_date,nvl(scheduled_finish_date,SYSDATE+1)) end_date
FROM pa_projects_all
WHERE name = l_project_name;
l_task1 varchar2(120) :='2.02';
begin
po_proc_plan_pub.Apps_initialize(1,
'SERVICES',
'Projects SU, Vision Services (USA)',
204);
mo_global.set_policy_context('S',204 );
--MO_GLOBAL.SET_ORG_CONTEXT('204','','PA');
OPEN C_BATCH ;
FETCH C_BATCH INTO l_batch_id;
close C_BATCH;
OPEN c_project_id ;
FETCH c_project_id INTO l_project_id,l_start_date,l_end_date;
close c_project_id;
l_org_id := fnd_global.org_id;
/*insert into header interface*/
INSERT INTO po_proc_plan_hdr_interface(plan_start_date,plan_end_date,plan_name,project_name,org_id,batch_id, project_id,lock_update_date)
VALUES('01-JAN-2012','31-DEC-2013',l_project_name,l_project_name,l_org_id,l_batch_id, l_project_id,'02-APR-2014');
/*insert into line interface*/
insert into po_proc_plan_line_interface(line_number,
line_type,
category,
item_number,
description,
status,
buyer,
suggested_supplier,
priority1,
priority2,
priority3,
additional_information,
expenditure_type,
planning_currency_code,
planning_rate,
uom,
batch_id,
project_id,
plan_name)
values(7,'Goods',null,'AS72111',null,'Draft','Stock, Ms. Pat','Advanced Network Devices','Approved Supplier','Location','Price Compliance',null,'Construction','USD',720,'Each',l_batch_id, l_project_id,l_project_name);
/*insert into period table*/
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-01',1000,l_batch_id, l_project_id, l_project_name,1 );
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-02',1500,l_batch_id, l_project_id, l_project_name,2 );
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-03',2100,l_batch_id, l_project_id, l_project_name,3);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-04',5600,l_batch_id, l_project_id, l_project_name,4);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-05',8500,l_batch_id, l_project_id, l_project_name,5);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-06',11000,l_batch_id, l_project_id, l_project_name,6);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-07',9800,l_batch_id, l_project_id, l_project_name,7);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-08',1600,l_batch_id, l_project_id, l_project_name,8);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-09',2000,l_batch_id, l_project_id, l_project_name,9);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-10',1500,l_batch_id, l_project_id, l_project_name,10);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-11',500,l_batch_id, l_project_id, l_project_name,11);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2012-12',500,l_batch_id, l_project_id, l_project_name,12);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-01',1000,l_batch_id, l_project_id, l_project_name,13);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-02',1500,l_batch_id, l_project_id, l_project_name,14);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-03',2100,l_batch_id, l_project_id, l_project_name,15);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-04',5600,l_batch_id, l_project_id, l_project_name,16);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-05',8500,l_batch_id, l_project_id, l_project_name,17);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-06',11000,l_batch_id, l_project_id, l_project_name,18);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-07',9800,l_batch_id, l_project_id, l_project_name,19);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-08',1600,l_batch_id, l_project_id, l_project_name,20);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-09',2000,l_batch_id, l_project_id, l_project_name,21);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-10',1500,l_batch_id, l_project_id, l_project_name,22);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-11',500,l_batch_id, l_project_id, l_project_name,23);
insert into po_proc_plan_prd_interface(schedule_number, line_number , task_number , location , period_name, quantity, batch_id,project_id, plan_name,period_sequence)
values(4,7,l_task1,'HR- San Francisco','2013-12',500,l_batch_id, l_project_id, l_project_name,24);
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;
-----------------------------------------------------------------------------------------------------------------------------------
The following tables list the columns in the three interface tables:
| Column Name | Description/Valid Value |
|---|---|
| PLAN_START_DATE | Project Start Date |
| PLAN_END_DATE | Project End Date |
| STATUS | Not used |
| PROJECT_NAME | Name of the Project |
| PLAN_NAME | Name of the Plan |
| PLAN_DESCRIPTION | Description of the plan |
| ORGANIZATION_NAME | Not used |
| BATCH_ID | This is a unique number and will be auto generated |
| LAST_RUN_REQUEST_ID | Previous run Concurrent Program Request Id |
| PROCESS_FLAG | Not used |
| PROJECT_ID | ID for the project |
| ORG_ID | Project organization ID |
| DELETE_FLAG | Not used |
| LOCK_UPDATE_DATE | Whenever the procurement plan is downloaded for updating, the date will be saved in this column |
| SRC_SYS_NAME | Name of the Source System |
| SRC_SYS_DOC | Name of the Reference Document in Source System |
| SRC_SYS_DOC_VER | Version of the Reference Document in Source System |
| SRC_SYS_LINE_NUMBER | Source System Document Line Number |
| SRC_SYS_LINE_VER | Version of the Reference Document Line in the source system |
| SRC_SYS_DATE | Source System Date |
| Column Name | Description/Valid Value |
|---|---|
| LINE_NUMBER | Line number |
| LINE_TYPE | Line type value |
| CATEGORY | Category of the item |
| ITEM_NUMBER | Item number |
| DESCRIPTION | Item description |
| STATUS | Select one of the following starting values: Draft, Ready to Order, Ready for Planning |
| BUYER | Buyer name |
| SUGGESTED_SUPPLIER | Any valid supplier or a user can enter any name |
| PRIORITY1 | Select applicable value from PA_PSC_SUPP_SELECTION lookup - Approved Supplier, Location, On-time delivery, Price Compliance, Quality |
| PRIORITY2 | Select from PA_PSC_SUPP_SELECTION lookup - Approved Supplier, Location, On-time delivery, Price Compliance, Quality |
| PRIORITY3 | Not used |
| ADDITIONAL_INFORMATION | Additional information or description for a plan line |
| EXPENDITURE_TYPE | Expenditure type to be associated with any purchase order distribution for the item such as Airfare, Hardware, Materials |
| PLANNING_CURRENCY_CODE | Planning currency code, for example, USD, EUR |
| PLANNING_RATE | Planning rate |
| AMOUNT_COMMITTED | Not used |
| AMOUNT_OBLIGATED | Obligated amount |
| UOM | Unit of measure |
| QUANTITY_ORDERED | Ordered quantity |
| QUANTITY_RECEIVED | Received quantity |
| QUANTITY_REJECTED | Rejected quantity |
| QUANTITY_OVERDUE | Overdue quantity |
| NEXT_SHIPMENT_DATE | Next shipment date |
| CREATION_DATE | Date on which it was created |
| CREATED_BY | Name of the person who created it |
| LAST_UPDATE_DATE | Last updated date |
| LAST_UPDATED_BY | The person who updated it last |
| LAST_UPDATE_LOGIN | Login ID of the person who updated it last |
| BATCH_ID | Same ID as on the header |
| PROCESS_FLAG | Not used |
| PLAN_NAME | Name of the project |
| PROJECT_ID | Project ID |
| DELETE_FLAG | Not used |
| ACQ_STRATEGY_OBJECTIVE1 | The application does not use these columns, instead it uses columns PRIORITY1, PRIORITY2 |
| ACQ_STRATEGY_OBJECTIVE2 | Not used |
| PROD_SELECTION_OBJECTIVE1 | Not used |
| PROD_SELECTION_OBJECTIVE2 | Not used |
| INV_STRATEGY_OBJECTIVE1 | Not used |
| INV_STRATEGY_OBJECTIVE2 | Not used |
| COST_CODE | Project Cost code if the Project is CBS enabled Project. |
| Column Name | Description/Valid Value |
|---|---|
| SCHEDULE_NUMBER | Schedule number |
| LINE_NUMBER | Line number same as in Plan Line Work sheet |
| LINE_TYPE | Line type value |
| CATEGORY | Category of the item |
| ITEM_NUMBER | Item number |
| DESCRIPTION | Item description |
| TASK_NUMBER | Task number |
| LOCATION | Location name |
| PERIOD_NAME | NULL value |
| QUANTITY | No need to enter any value |
| CREATION_DATE | Created date |
| CREATED_BY | Name of the person who created it |
| LAST_UPDATE_DATE | Last updated date |
| LAST_UPDATED_BY | Name of the person who updated it last |
| LAST_UPDATE_LOGIN | Login ID of the person who updated it last |
| BATCH_ID | Same ID as on the header |
| PROCESS_FLAG | Not used |
| PLAN_NAME | Project name |
| PROJECT_ID | ID of the project |
| PERIOD_SEQUENCE | Sequence of the period. For example, a schedule has 12 periods and each period must have a sequence number and it must be in sequence order |
| COST_CODE | Project Cost code if the Project is CBS enabled Project. |
While inserting data into the interface tables, you must ensure that the following columns have applicable data:
PO_PROC_PLAN_HDR_INTERFACE:
plan_start_date
plan_end_date
plan_name
project_nameorg_id
batch_id
project_id
lock_update_date
PO_PROC_PLAN_LINE_INTERFACE:
line_number
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
period_sequence
Note: The application populates the columns for which you do not have to mandatorily enter values while inserting data into the interface tables.
To create a procurement plan using a spreadsheet:
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.
Select the applicable project and click the Procurement link to open the Procurement Plan page.
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.
Click Download to download a zip archive containing a Readme and an XML Spreadsheet Template.
Refer to the Readme file available in the downloaded zip archive for instructions to use the spreadsheet for creating a new procurement plan for the project.
Oracle Project Procurement Command Center Plus enables you to update a procurement plan using the following two methods:
Using the interface tables
Using spreadsheet
To update through interface table:
In the interface tables, add the existing procurement plan number.
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
Acquisition Strategy Primary Objective
Acquisition Strategy Secondary Objective
You can update the following fields anytime:
Buyer
Additional Information
Expenditure Type
Planning Currency
Planning Rate
UOM
Task Number
Location
Monthly Requirements
You can modify content and add new lines to an existing procurement plan by downloading the existing procurement plan and uploading it back after making changes to it.
To update a project procurement plan:
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.
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
When there is a change in any of the attributes of a Procurement Plan Line, you can:
Freeze the current version of the line identified by the Procurement Plan, Procurement Plan Line Number and Procurement Plan Line Version Number
Create a new record for the same Procurement Plan, Procurement Plan Line Number and Procurement Plan but with the next higher Line Version Number
In order to keep a Procurement Plan Line Version in sync with the corresponding source of demand in the Engineering system, as a Project Manager, you can modify any of the following attributes of the line:
Category of the Procurement Plan Line
Item Description
Destination
Buyer Name
Suggested Supplier
Acquisition strategy primary objective
Acquisition strategy secondary objective
Source Information reference (All source related details)
Additional Information
Expenditure type
Planning Rate
Purchasing UOM
For one or more of the Schedules for a Material line:
Task Number
UOM
Location
Quantity
For one or more of the Pay Items for a Services line:
Pay item type
Pay item Description
Task Number
Quantity
UOM
Value(%)
Price
Need by date
Add one or more Schedules for a Material line
Add one or more Pay Items for a Services line
Suggested suppliers
Reference to a document detailing on or more components of the Technical Specifications
Reference to a document detailing the Submittal Requirements
As a Project Manager, you can make any kind of change to the Procurement Plan Line irrespective of the status of the plan line. You can download, make changes, and upload the document. You can however, not make manual updates to the status of the plan line. The Version Number column in the Plan Lines sheet is a non-editable field. If you, as a Project Manager provide a value for the Version Number, the application will ignore it during data upload. The Version Number is automatically updated to 0 when a plan line is uploaded in the Draft status. Any changes to the plan lines in draft status will not increment the Version Number. The Version Number is incremented by 1 when any of the plan lines that are not in Draft status are changed or updated. For example, if a plan line is in the Ready for Planning status, and the attributes of the plan line are changed, then the application automatically increments the Version Number by 1. Incrementing the Version Number by 1 puts the plan line in Revised status. The following table displays details of the various scenarios and application behavior based on the status:
| Scenario | Application Behavior |
|---|---|
| Updates to Plan lines that are in Draft status | No change in application behavior. Application will continue to work the way it works today |
| Updates to Plan lines that are in Ready for Planning status | When the plan line is in Ready for Planning status and the changed attribute falls under one of the following attributes:
then,
|
| Updates to Plan lines that are in Ready To Order status | When the plan line is in Ready to Order status and the changed attribute falls under one of the below attributes
then,
|
Click Download to download a zip file containing the procurement plan spreadsheet and a Readme file.
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.
Update existing lines, 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.
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.
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.
The command center page for a project displays work and project procurement financials metrics, analysis charts and graphs, planning and procurement documents. This page enables you to manage the project supply chain effectively. This central page of the project manager command center indicates the current status of the project. You can see how much quantity has been requested, ordered, received, and invoiced for each task or for each monthly bucket. You can see the status of plan lines and negotiations. Additionally, you can see where the project has incurred unplanned spend and the procurement status for each task.
This page displays the following:
The heading region of the page displays the following:
Project Name
Project Number
Date/time stamp of last ETL update
Update Procurement Plan button
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.
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.
The Bookmarks component allows you to save a given navigation and component state and return to it at a later time.
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.
The page has two metric sections:
| Work Metric | Metric Display Title |
|---|---|
| Plan Lines | Total plan lines for the procurement plan of the project |
| Draft | Draft status from the procurement plan lines of the project |
| Ready For Planning | Ready for Planning for procurement planning lines of the project |
| Ready To Order | Ready to Order for procurement plan lines of the project |
| Revised | Number of Plan lines that are modified by the Project Manager that needs buyer review. This metrics lists the number of plan lines updated by the Project Manager that are in the Ready for Planning or Ready to Order statuses. When you click Revised, the application reapplies the Revised filter to the page and displays only those plan lines that are in the Revised status. |
| Supplier Change Requests | Change requests for the supplier |
| Supplier on Hold | Number of Suppliers on Hold |
| Project Procurement Financials Metric | Metric Display Title |
|---|---|
| Project Currency | Currency indicator for the Project Currency |
| 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 |
| Requisitioned | Total requisitioned for the procurement plan |
| Ordered | Total ordered for the procurement plan |
| Received | Total received for the procurement plan |
| Invoiced | Total invoiced for the procurement plan |
| Paid | Total paid for the procurement plan |
This region displays the following:
| Alert Name | Description |
|---|---|
| Items with delayed shipments | Items with delayed shipments (not yet delivered) |
| Items past Need by Date but not requisitioned | Items not requisitioned |
| Items past Order by Date but not ordered | Items not ordered |
| Purchase Orders with Promised Date beyond Need by Date | Delivery dates beyond my Need by Date |
| Unplanned Purchases | POs/orders places for items that are not in the procurement plan |
| New Supplier Holds | Latest supplier holds |
Note: Any chart containing 'amount' on one of the axes, only renders if the data is of a single functional currency. If the chart does not render, then you must apply a currency filter.
This region displays the following charts and graphs:
| Chart Title | Tab | Details |
|---|---|---|
| Schedule | Schedule | Quantity by period for Quantity requested Quantity ordered Quantity received Quantity invoiced Quantity rejected Total quantity |
| Plan Lines Status | Schedule | Planning amount by period for line status: Draft, Ready for Planning, Ready to Order, and Revised. |
| Task by Start Date | Planning Status | Task not started that have passed the scheduled start date The graph displays details of the period for the task. |
| Spend Analysis | Planning Status | Amount by item category |
| Actual Over Planned | Financial | Quantity ordered by period for the items on the project |
| Procured Cost Percentage | Financial | Percentage breakdown of total procured cost by: Total cost ordered Total cost received Total cost requisitioned Total cost rejected/returned Total cost remaining |
| Supplier Measures | Supplier | Average delivery rating by month for each supplier |
| Approved, Local Suppliers | Supplier | Total amount approved by approval year date |
| Average Lead Time | Item | Average lead time by period |
| Product Variety | Item | Planned items and ordered items for the project |
| Unplanned Orders | Orders | Unplanned orders by date |
| Change Orders | Orders | Supplier change request by date |
This region lists the tasks and related procurement plan information that meet the filter criteria applied by the you through searching, guided navigation, or selection of a chart series/section. The table in this section has the following sub-tabs:
Tasks – the tasks for a project that have at least one associated procurement plan line
Plan lines – the plan lines for the tasks in the tasks sub-tab. You can choose to filter information further based on the available result sets – for example Plan Lines, Delivery Tracker, Budget Tracker, Supplier Selection Strategy, Additional Information, Source Information, and Actions. You can view details such as Item Description, Item Category, Item Number, Line Number, Line Type, Version Number (value displayed only if there are revisions to the plan line), Line Status, Previous Status (displays the Previous Status value only if the plan line is in Revised status – for example, if the plan line is Revised when it is in Ready to Order status, then the Line Status column displays Revised as the status and the Previous Status column will display Ready to Order), Buyer Name, UOM, Quantity, Planning Currency, Unit Price, Planning Amount, Functional Currency, Amount (Functional Currency), Project Currency, Amount (Project Currency), Functional Currency, and Amount (Functional Currency).
Schedule – the schedule of item quantities in the procurement plan for the lines in the plan lines sub-tab
Schedule Summary – a summary of the schedule amounts displayed in the schedule sub-tab
Sources of Supply – the sources of supply authorized by the buyer for the plan lines
Project managers can perform the following actions while reviewing the project details:
In the Tasks tab, you can select multiple task rows and request the following actions using the Actions option available on the right side of the Tasks table:
Update Multiple Tasks – You can select multiple task rows and select the 'Update Multiple Tasks' action for task in current working version.
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.
Additionally, in the Tasks tab, if Actions is selected in the column set dropdown menu, you can update financial plans by selecting a task and the Update Financial Plans action to view and update the financial plan lines (budgets or forecasts) for the task selected.
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. You can also select one or more lines and click View Revision History. When you click View Revision History, the Revision History page displays, where you can view the changes to the plan lines across different revisions. You can compare the changes of the selected procurement plan line with the earlier revision, original version and all the versions of the plan line. 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.
This region displays details of the following purchasing documents associated with the plan lines:
Negotiation
Agreements
Requisitions
Orders
Select Actions in the column set dropdown menu and view these purchasing documents from the respective sub-tabs.
Project Managers can use the Revision History page to view and compare the changes made to a procurement plan line with the earlier revision, original version and all the versions of plan line. To do this, you, as a project manager, need to select one or more plan lines and select the View Revision History action in the Plan Lines tab of the Project Manager Command Center.
The Revision History page shows the changes made at the header (Project Details), Plan line, Monthly Requirements and Progress Summary levels.
If you select more than one plan line for viewing the revision changes, then the comparison is sorted by Line and Revision. If you select a single plan line for viewing the revision changes then the comparison is sorted by Revision, where the latest revision is shown first followed by subsequent revisions.
If you delete the plan line selected from the command center from the Selected Plan Line region then the application refreshes and shows the revision changes for the available line in the Show all Procurement Plan Line Changes region.
When you select only one plan line from the command center and the selected line is deleted from the Selected Plan Lines region, then the application refreshes and does not show any values if you choose the Compare to Original Plan Line or the Compare to Previous Revision from the actions menu.
If you select a goods line that has associated monthly requirement details, then the application displays an icon adjacent to the Line Number to identify it as a goods line.
Click Return to Command Center to return to the Command Center.
Click Compare to Previous Revision and then click Go to view the changes between the previous revision and the current revision.
Click Compare to Original Revision and then click Go to view the changes between the original revision and the current revision.
Click the Compare to All Revisions and then click Go to view all the changes across all revisions of the Procurement Plan Line.
Project managers can use the Item Analysis page to view, compare, analyze, and replace items to procure for the project. For items that are specified in the procurement plan, project managers can analyze them using the Procurement Plan for a given project.
To analyze and replace items to procure:
Navigate to the Items Analysis page using the following navigation: Procurement Plan page for a given project > Planning Documents region > Plan Lines tab > Actions from the column set dropdown menu
Select the applicable item.
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, including current orders and suppliers. You can use the Search Box on this page to look for alternatives.
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.
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.
For further information regarding Item Analysis page, see Chapter 5 – Analyzing Items and Suppliers
Project managers can use the Supplier Analysis page to view, compare, and analyze the supplier performance for a given item. For suppliers who are specified in the procurement plan, project managers can analyze them using the Procurement Plan for a given project.
To analyze sources of supply:
Navigate to the Supplier Analysis page using the following navigation: Procurement Plan page for a given project > Planning Documents region > Plan Lines tab > Actions from the column set dropdown menu
Select the applicable item.
Click the Analyze Supplier link to open the Supplier Analysis page.
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 Chapter 5 – Analyzing Items and Suppliers
Oracle Project Procurement Command Center Plus enables project managers to manage project procurement exceptions that pose risks to the project schedule or budgets. Use the Exceptions region in the Procurement Plan page for a given project to view and act upon the risks to the project progress. Exceptions help alert you to approach 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.
The project manager can authorize the project buyer to start sourcing the items required for the project by marking the applicable plan lines as ready for planning. This authorization changes the plan line status from 'Draft' to 'Ready for Planning'. The application displays an error if any of the selected plan lines are not in Draft status.
To release plan lines for planning:
Navigate to the Planning Documents region on the Procurement Plan page for a given project.
Click the Plan Lines tab.
Ensure that Plan Lines is selected in the Action dropdown menu.
Select the applicable items.
Scroll right to the Actions option available on the right side of the Plan Lines table.
Select Mark Lines Ready for Planning action to indicate to the project buyer that they can start finding suppliers for the item that is best suited for the project.
Upon successful completion of action, the application displays a confirmation message.
Project managers can create purchase requisitions for plan lines that are in Ready to Order status. The application can alert the project managers when they need to create purchase requisitions or they can apply filters to identify the plan lines with items or services that need to be ordered. They can select one or more schedule detail lines for the procurement plan lines and create a single requisition. When creating requisition, they can:
Update the item description (if not linked to an agreement)
Specify the quantity / amount and need by date
To create purchase requisitions:
Navigate to the Planning Documents region on the Procurement Plan page for a given project.
Click the Schedules tab.
Select the applicable schedules.
Scroll right to the Actions option available on the right side of the Plan Lines table.
Select Add to Shopping Cart action.
Select Checkout in the Shopping Cart page
Review the requisition summary.
Click Submit to submit the requisition.
The application displays a confirmation message. Click Continue to return to the Procurement Plan page.
As Oracle Project Procurement Command Center Plus is integrated with Oracle iProcurement, the selected plan lines, budget amounts, task, and expenditure type details are populated automatically.