Implementing Oracle Procurement Command Center Plus

The chapter discusses the prerequisite products and the setup steps required to install and use Oracle Procurement Command Center Plus.

This chapter covers the following topics:

Licenses for Oracle Procurement Command Center Plus

Prerequisite Licenses

To use Oracle Procurement Command Center Plus, you must have the following:

Additional Licenses

Oracle Procurement Command Center Plus integrates and interacts with the other Oracle E-Business Suite products. Licensing and implementing other products is optional; however, other products enable more functionality and provide optimal business information.

Feature License Required Comments
Reviews, Ratings, and Feedback analysis and actions
Catalog review ratings
Oracle iProcurement Information Discovery Plus Requesters enter reviews or ratings and submit feedback using Oracle iProcurement Information Discovery Plus, which is a separately licensed product.
iExpense spend analysis and actions Oracle iExpenses  
iProcurement catalog: manage and refine Oracle iProcurement  
Negotiations: monitor, analyze, and manage
Initiatives, objectives, and tasks
Oracle Sourcing  
Deliverables: track and manage Oracle Procurement Contracts  
Search suppliers using user-defined attributes (UDAs).
Supplier performance evaluation
Oracle Supplier Lifecycle Management and Oracle Supplier Hub  
View invoice and payment information Oracle Payables  

Oracle Procurement Command Center Plus Predefined Components

Oracle Procurement Command Center Plus provides the following predefined components:

Submenu

The 'Purchasing: SCC: Dashboard Tab' (PO_DASHBOARD_TAB ) submenu is delivered as part of the 'Purchasing Home Page for Buyers' (PO_BUYER_HOME_PAGE) main menu.

Description of the 'Purchasing: SCC: Dashboard Tab' submenu:

Prompt Submenu /Code Submenu Type Function/Code Function Type Description
Procurement Operations Purchasing: SCC Operational Dashboard (PO_SCC_OPERATIONAL_SUBTAB) SUBTAB     Purchasing: Operational Dashboard
  Purchasing: Project Procurement : Plan Tab (PO_PSC_PROC_PLAN_TAB) TAB     Purchasing: Project Procurement tab
Item Analysis Purchasing: Dash Board: Item Analysis Subtab ( PO_DB_ITEM_ANAL_SUBTAB ) SUBTAB     Purchasing: Dash Board: Item Analysis Subtab
Supplier Analysis Purchasing: Dashboard: Supplier Analysis Subtab (PO_DB_SUPP_ANAL_SUBTAB) SUBTAB     Purchasing: Dashboard: Supplier Analysis Subtab
      Purchasing: Dash Board: Bookmark Page (PO_DASHBOARD_BOOK_MARK_FN) JSP  
      Purchasing: Indirect Procurement: Bookmark Page (PO_IND_PROC_BOOK_MARK_FN) JSP  
      Purchasing: Procurement: Bookmark page (PO_PSC_BOOK_MARK_FN) JSP  
Indirect Procurement Purchasing: SCC Indirect Procurement SubTab (PO_IND_PROC_SUB_TAB) SUBTAB     Purchasing: Indirect Procurement SubTab
      Purchasing: Procurement: Supplier Analysis Page (PO_PSC_SUPPLIER_ANALYSIS_FN) JSP Purchasing: Procurement: Supplier Analysis Page
      Strategic Sourcing Dashboard: Endeca page (PON_PCC_STR_SOURCING_ENDECA_FN) JSP Strategic Sourcing Dashboard: Endeca page
Strategic Sourcing Sourcing: Dash Board: Strategic Sourcing Subtab SUBTAB     Sourcing: Dash Board: Strategic Sourcing Subtab
      PON: Sourcing Bookmark page (PON_SCC_BOOK_MARK_FN) JSP  

Function

The 'Purchasing: SCC Operational Page' (PO_SCC_OPERATIONAL_FN) function is delivered as part of the Purchasing Buyer Work Center (PO_BUYER_WORK_CENTER) main menu.

Note: Oracle does not deliver any responsibility to log in to Oracle Procurement Command Center Plus.

Enabling the Oracle Procurement Command Center Plus Menu

To use Oracle Procurement Command Center Plus, the system administrator must provide a prompt to the predefined menu and function. Once the prompt is entered for the predefined menu and function, then the tab for Procurement Command Center is visible on the Purchasing responsibility, Buyer Work Center page. This tab in Buyer Work Center is the starting point for Oracle Procurement Command Center Plus. From this tab, procurement teams and buyers can click any of the following subtabs:

For more information, see: Setting Up Oracle Procurement Command Center Plus.

Setting Up Oracle Procurement Command Center Plus

Prior to performing Oracle Procurement Command Center Plus setup steps, you must ensure that the following are completed:

  1. Install Oracle Purchasing R 12.2.5 or above

  2. Install Oracle E-Business Suite Information Discovery Release 12.2 V6 or above.

    See the Installing Oracle E-Business Suite Information Discovery note for the relevant release on My Oracle Support.

Post-Installation Steps

Complete the following post-installation steps.

Required Steps

  1. Add a prompt to the following menu and function to enable the user interface for Oracle Procurement Command Center Plus.

    1. Navigate to the System Administrator responsibility.

    2. Open the Menus window.

    3. Query the Purchasing Home Page for Buyers (PO_BUYER_HOME_PAGE) main menu.

    4. Locate the Purchasing: SCC: Dashboard Tab submenu.

    5. Enter a prompt for the submenu, for example, Dashboard.

    6. Save your work.

    7. Query the Purchasing Buyer Work Center (PO_BUYER_WORK_CENTER) main menu.

    8. Locate the Purchasing: SCC Operational Page (PO_SCC_OPERATIONAL_FN) function.

    9. Enter a prompt for the function, for example, Dashboard.

    10. Save your work.

    11. Now, when users log in to the Purchasing responsibility and click Buyer Work Center, they view a function called Dashboard.

      When clicking the Dashboard function, the Buyer Work Center page appears, where they can view the Dashboard tab.

      The Dashboard tab in Buyer Work Center is the starting point for Oracle Procurement Command Center Plus. From this tab, procurement teams and buyers can click any of the following subtabs:

      • Procurement Operations

      • Strategic Sourcing

      • Indirect Procurement

      • Item Analysis

      • Supplier Analysis

  2. Set up access for users as follows:

    For procurement managers and buyers, setup the following role to the Purchasing responsibility:

    Role Name: UMX|PO_SCC_ENDECA_ACCESS_ROLE

    Grant Name: PO_SCC_ENDECA_ACCESS_GRANT

    Permission Set Name: Purchasing SCC Buyer Permission Set

    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. Set up the following profile option for Oracle Procurement Command Center Plus. If you have set this profile option for Oracle Project Procurement Command Center Plus, then review the date to ensure that the date is also applicable to Oracle Procurement Command Center Plus.

    PO: Item and Supplier Analysis Data-load Cut-off – Set an applicable date based on how much data you want to use when evaluating items and suppliers. This profile value determines the historical procurement documents, such as requisitions, purchase orders, agreements, and negotiations that are loaded into the data set that supports the Supplier and Item Analysis pages. The application does not load any data beyond this cut-off and compares this date with the creation date of the document header to determine the document information to load. You must set the value in the canonical date format (example: 2010/01/01).

    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.

  4. Run the Full Load Graph to load applicable data from the Oracle Endeca Server to the Oracle Endeca Integrator ETL. See: Running the Full Load Graph.

  5. Set up the scheduler for incremental refresh. See: Setting up the Scheduler for Incremental Refresh.

Optional Steps

  1. Add lookup values to the following lookup types for Note Types in the Notes page.

    • PO_BUYER_ACTION_STATUS: Lookup type for the Action Status

    • PO_BUYER_PA_HEADER_ACTIONS: Lookup type for the Agreement Header

    • PO_BUYER_PA_LINE_ACTIONS: Lookup type for the Agreement Line

    • PO_BUYER_PO_HEADER_ACTIONS: Lookup type for the PO Header

    • PO_BUYER_PO_LINE_ACTIONS: Lookup type for the PO Line

    • PO_BUYER_REQ_LINE_ACTIONS: Lookup type for the Requisition Line

    • PO_BUYER_REVIEW_ACTIONS: Lookup type for the Review

    • PO_BUYER_SUGGESTION_ACTIONS: Lookup type for the Suggestions

    Each lookup value relates to an independent task that a buyer performs or delegates to another buyer. Each document, such as a requisition Line or a purchase order can have its own set of lookup values, as defined by these lookups. To review the delivered lookup values, see: Using Notes in Oracle Procurement Command Center Plus. After review, add the lookup values based on your business requirements.

    Use the Oracle Purchasing Lookups window to define lookup codes. See: Defining Lookup Codes, Oracle Purchasing User's Guide.

  2. Review the Oracle Web Applications Desktop Integrator (ADI) layouts available for Oracle Procurement Command Center Plus.

    If required, you can customize these layouts to suit your business requirements. If you customize these layouts, then you must ensure that you do not remove or hide key columns. Key columns include: Batch Id, Result Format Usage Id, Line Number, Schedule/Pay Item Number, and Distribution Number. For information about the Web ADI integrator and layouts supplied by Oracle Procurement Command Center Plus, see: Oracle Procurement Command Center Plus Predefined Components.

  3. Enable descriptive flexfields (DFFs) on Oracle Procurement Command Center Plus dashboards.

    The application allows buyers to filter purchasing documents by descriptive flexfield attributes. You can enable DFFs for the dashboards and for the Web ADI functionality.

    Important: You can use only one DFF at a time for each dashboard.

    The DFFs for the Procurement Command Center dashboards are:

    • Purchasing Documents Order Header Layout: Header DFF for orders

    • Purchasing Documents Lines Layout: Line DFF for orders. This is the default DFF

    • Purchasing Documents Agreement Header Layout: Header DFF for agreements

    DFFs are supported in the following tables in Procurement Command Center:

    • PO Header

    • PO Line

    • PO Shipment

    • PO Distribution

    • Requisition Header

    • Requisition Line

    DFFs can be enabled in the Procurement Operations Dashboard (PoOperationalDashboardPG).

    For information about how to enable DFFs, refer to the Oracle Application Framework Personalization Guide.

  4. If required, implement the document-level security for Oracle Procurement Command Center Plus. See: Document Security in Oracle Procurement Command Center Plus.

    If document-level security is setup, then run the Fill Employee Hierarchy concurrent program for any hierarchy-related changes to take effect.

    Refer to the Oracle Purchasing User's Guide for information about the Fill Employee Hierarchy concurrent program.

  5. Configure partial search attributes, if required.

    Partial search is enabled for a predefined set of attributes on all the dashboards. For the list of attributes for which partial search is enabled, see:

    As an optional step, you can customize the list of attributes identified for partial search. To add additional attributes or remove already configured attributes for partial search, modify the attribute profile value using the Information Discovery Developer responsibility. Follow the configuration steps in the Oracle E-Business Suite Information Discovery Plus Integration and System Administration Guide. After the configuration is changed, run the Full Load Graph (FullLoadConfig.grf) for this configuration to take effect.

Running the Full Load Graph

Once you have run the full load graph in accordance with the Installing Oracle E-Business Suite Information Discovery note for the relevant release on My Oracle Support, attribute configuration is loaded for all seeded attributes. Additionally, you need to run the following full data loads as follows:

To run a full Endeca Refresh on the Integrator Server:

  1. Log in to Integrator server using your Clover login.

  2. Click the Scheduling tab.

  3. Select the New Schedule link.

  4. Enter a Description for the scheduler, for example, Projects Full Load Scheduler.

  5. Select Periodic as the Type.

  6. Select by interval as the Periodicity.

  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.

  9. Enter a value in the Interval (minutes) field.

  10. Ensure you select the Fire misfired event as soon as possible check box.

  11. Select Execute graph from the Task Type list.

  12. Select "po-scc" for Procurement Operations dashboard, "po-ind-proc" for Indirect Procurement dashboard, "po-proc-sup" for supplier analysis, and "po-proc-item" for Item Analysis from the Sandbox list one after another. Ensure to run the full load graph for each of these sandboxes.

  13. Select as follows from the graph list:

    • po-scc (FullLoadConfig.grf) when you select po-scc sandbox

    • po-ind-proc (FullLoadConfig.grf) when you select po-ind-proc sandbox

    • po-proc-item(Full.grf) when you select po-proc-item sandbox

    • po-proc-sup(Full.grf) when you select po-proc-supp sandbox

    • scc-sourcing(FullLoadConfig.grf) in pon-scc-sourcing sandbox

  14. Click Create to set the scheduler.

Setting Up the Scheduler for Incremental Refresh

Once the Full graph is run in accordance with the Installing Oracle E-Business Suite Information Discovery, Release 12.2 V6, My Oracle Support Document ID 1970071.1, initial data load for Oracle Procurement Command Center Plus is complete. For incremental refresh, you must determine how often the Endeca data should be refreshed from EBS depending upon your organizational requirements. Oracle recommends that you keep this near real time. As the data is updated in the EBS, you need to ensure it is updated in the Endeca MDEX server. You set up the Scheduler to load incremental graphs depending on the volume of information requiring update.

To set up the scheduler:

  1. Log in to Integrator server using your Clover login.

  2. Click the Scheduling tab.

  3. Select the New Schedule link.

  4. Enter a Description for the scheduler, for example, Projects Full Load Scheduler.

  5. Select Periodic as the Type.

  6. Select by interval as the Periodicity.

  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.

  9. Enter a value in the Interval (minutes) field.

  10. Ensure you select the Fire misfired event as soon as possible check box.

  11. Select Start a graph from the Task Type list.

  12. Select "po-scc" for Procurement Operations dashboard, "po-ind-proc" for Indirect Procurement dashboard, "po-proc-sup" for supplier analysis, and "po-proc-item" for Item Analysis from the Sandbox list one after another. Ensure to run the full load graph for each of these sandboxes.

  13. Select as follows from the graph list:

    • po-scc (IncrementalLoadConfig.grf) when you select po-scc sandbox

    • po-ind-proc (IncrementalLoadConfig.grf) when you select po-ind-proc sandbox

    • po-proc-item(Incremental.grf) when you select po-proc-item sandbox

    • po-proc-sup(Incremental.grf) when you select po-proc-sup sandbox

    • pon-scc-sourcing(IncrementalLoadConfig.grf) in pon-scc-sourcing sandbox

  14. Click Create to set the scheduler.

Views and Joins to Load Procurement Command Center Data

The following views are used by the Oracle Endeca Integrator ETL to load and display Procurement Command Center Plus, Item Analysis, Supplier Analysis, and Strategic Sourcing dashboards data to the Endeca data store:

Oracle Procurement Command Center Plus Menu Navigation

Oracle Procurement Command Center Plus enables procurement teams and buyers to access the product using the Purchasing responsibility, Buyer Work Center page, tab for Oracle Procurement Command Center Plus.

The system administrator must provide a prompt for the Purchasing: SCC: Dashboard Tab' (PO_DASHBOARD_TAB ) submenu and Purchasing: SCC Operational Page' (PO_SCC_OPERATIONAL_FN) function. Once the prompt is entered for the predefined menu and function, then the tab for Procurement Command Center is visible on the Purchasing responsibility, Buyer Work Center page. This tab in Buyer Work Center is the starting point for Oracle Procurement Command Center Plus. From this tab, procurement teams and buyers can click any of the following subtabs:

For more information, see: Setting Up Oracle Procurement Command Center Plus.

Document Security in Oracle Procurement Command Center Plus

Oracle Procurement Command Center Plus provides the following security features for purchasing documents:

Multi-Org Access Control (MOAC)

Oracle Procurement Command Center Plus uses MOAC to control what data is displayed. Each dashboard displays only data for organizations to which the logged-in user has access. The MOAC feature applies to the following dashboards in Procurement Command Center:

Document Security

Oracle Procurement Command Center Plus provides the same document security available within Oracle Advanced Procurement for purchasing documents such as requisitions, negotiations, agreements, and purchase orders. Oracle Purchasing lets you control which groups of users have access to each document type, and what modification or control actions these users can take. The security rules also affect the calculation of metrics and plotting of charts, which use only the data to which the user has access. For more information about document security, refer to Document Security and Access in Oracle Purchasing User's Guide.

Important: Document Security Implementation Considerations

Document security affects metrics and charts. The calculation of metrics and the plotting of charts use only the data that is visible to the user. When implementing Oracle Procurement Command Center Plus, buyer administrators must consider the security structure and ensure that if a buyer has access to purchase orders, then the buyer also has access to associated documents such as agreements and negotiations. If there are inconsistencies in the security setup, such as having different document security settings on the agreement than on the associated negotiation and on the purchase orders that reference the agreement, then the buyers will not get the correct insights to make better and more informed decisions. These inconsistencies will impact the ability of the procurement team to maximize savings and improve responsiveness. Excessive and complicated document-level security will lead to incorrect analysis and insights and can lead to incorrect decision making. Therefore, it is important to keep document security simple and to use it only when it is essential for the business. Inconsistent document security rules will severely undermine the value of the insights available through Oracle Procurement Command Center Plus.

The document security applies to the Procurement Operations dashboard and the Indirect Procurement dashboard only. The document security does not apply to the Item Analysis dashboard and the Supplier Analysis dashboard. Buyer administrators can restrict document access based on security level options for each document type. Buyer administrators can specify a security access level that controls which modifications and control actions buyers can take on a particular document type.

The following sections explain how the document security works for purchasing documents in Oracle Procurement Command Center Plus.

Purchase Orders

  1. If MOAC is enabled, then buyers can view only documents that belong to the operating units that they have access to. Therefore, users who need access to the Procurement Operations dashboard and the Indirect Procurement dashboard must be set up as buyers.

  2. If MOAC is enabled, then buyers can view only documents that belong to the operating units that they have access to. Therefore, users who need access to the Procurement Operations dashboard and the Indirect Procurement dashboard must be set up as buyers.

    • Purchasing: Only the document owner, subsequent approvers, and buyers can access the document.

    • Public: All system users can access the document.

    • Private: Only the document owner and subsequent approvers can access the document.

    • Hierarchy: Only the document owner, subsequent approvers, and users included in the security hierarchy can access the document. Security Hierarchy is a position hierarchy, which is specified in the Purchasing Options.

  3. If the profile option PO: Enforce Project Security is set to Yes, then the buyer can access a purchase order only if the purchase order is associated with a project to which the buyer has access. Access to projects is based on the projects setup.

  4. Purchase order security overrides all other document security. For example, when a purchase order refers to an agreement or a negotiation, and the document-level security for purchase orders is different from that of the referenced document, then the application ignores the document security of the referenced document.

Requisitions

  1. If a requisition is placed on a purchase order or negotiation, then the security from the final document in the business flow applies to the requisition.

  2. If a requisition is in a pool, then MOAC security and project security is applied. The document-level security on the requisitions is not applied, which is the behavior of Demand Workbench in Oracle Purchasing.

  3. For requisitions in a pool, the profile option PO: Allow Buyer Override in Autocreate Find is applied. If this profile is set to yes, then the user can view unassigned requisitions and requisitions assigned to other buyers as well. If this is set to No, then only requisitions assigned to that user as a buyer are visible.

Negotiations

  1. If a negotiation is referenced on a purchase order, then only the purchase order security applies.

  2. If a negotiation is placed on an agreement and not referenced on a purchase order, then only the agreement security applies.

  3. For negotiations that are not placed on a purchase order or on a global blanket purchase agreement, the security level set at the Negotiation Document type and for the collaboration team will take effect.

    • For Purchasing and Public: All buyers have access.

    • For Private: The buyer who owns the negotiation and all members of the collaboration team have access to the negotiation. Note that the dashboards are accessible only to buyers.

Agreements

  1. If an agreement is referenced on a purchase order and a buyer has access to that purchase order as per the rules described in the Purchase Orders section, then the agreement data is accessible to the buyer. See: Purchase Orders

  2. For agreements not used on a purchase order, MOAC security and Document Type security will apply as described in points 1 and 2 of the Purchase Orders section. See: Purchase Orders