Cloud Readiness / Oracle Self Service Procurement Cloud
What's New
Expand All


  1. Update 22A
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
  5. Procurement Common
    1. Common Procurement
        1. Integrate and Extend Procurement Using REST Services
  6. Self Service Procurement
    1. Dual Units of Measure
        1. Request Items That Are Priced in Their Secondary UOM
        2. Automatically Derive Ordered Quantity for Items Priced in Their Secondary UOM
        3. Import Purchase Orders for Items Priced in Their Secondary UOM
        4. Generate Reports on Purchase Orders for Items Priced in Their Secondary UOM Using OTBI
    2. Self Service Procurement
        1. Recover Approval Exceptions Using Action Details and Transaction Console

Update 22A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Product Feature Notes
20 DEC 2021     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

  • Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
  • Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

  1. Click Navigator > My Enterprise > New Features.
  2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
  3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
  4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

  1. Click Navigator > My Enterprise > Offerings.
  2. On the Offerings page, select your offering, and then click Opt In Features.
  3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
  4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Procurement Common

Common Procurement

Integrate and Extend Procurement Using REST Services

Self Service Procurement

Dual Units of Measure

Request Items That Are Priced in Their Secondary UOM

Automatically Derive Ordered Quantity for Items Priced in Their Secondary UOM

Import Purchase Orders for Items Priced in Their Secondary UOM

Generate Reports on Purchase Orders for Items Priced in Their Secondary UOM Using OTBI

Self Service Procurement

Recover Approval Exceptions Using Action Details and Transaction Console

Procurement Common

Common Procurement

Integrate and Extend Procurement Using REST Services

In this update, Oracle Fusion Cloud Procurement and Oracle Fusion Cloud Self Service Procurement deliver modified REST APIs to enable and simplify integration with external systems.

The following REST APIs are enhanced:

  • Purchase Requisitions
    • GET, POST, and PATCH are supported for budget date so you can explicitly create a requisition distribution by providing a budget date
  • Draft Purchase Orders
    • GET, POST, and PATCH are supported for pricing UOM
    • PATCH is supported for item and source blanket purchase agreement for open and draft purchase orders
  • Purchase Orders
    • GET is supported for pricing UOM, secondary UOM, and secondary quantity
  • Requisition Processing Requests
    • GET and POST are supported for order number and PO header ID so you can add requisition lines to an existing order
  • Supplier Negotiations
    • POST and PATCH are supported for parent supplier contacts of the invited suppliers
  • Suppliers
    • Use the Submit Supplier Spend Authorization Request custom action to submit a supplier spend authorization request for approval

You can use these modified REST services to simplify integrations and support standards-based interoperability with your other applications and external systems.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Role Information

Self Service Procurement

Dual Units of Measure

Set up your Oracle Cloud applications so you can order, price, receive, pick, pack, and ship an item that you enable with primary and secondary UOM tracking. You might need to order, transfer, outsource, or buy an item in a unit of measure that's different from the unit of measure that you use to price, invoice, and cost it.

For example, you might stock and sell meat in cases, but price it in pounds. Each case of meat has a different price because the total weight in pounds varies from one case to the next, but you need to give your buyers an estimated price for each case.

You can use the dual UOM solution to meet this requirement. It's an end-to-end, integrated solution that works across the Oracle Cloud applications and helps you:

  • Simultaneously track an item in the primary UOM and secondary UOM throughout your order-to-cash process and procure-to-pay processes.
  • Capture the actual weight of the item that you sell, transfer, or purchase, so you can accurately price, invoice, and cost the item.
  • Provide a price estimate at the time of sale or purchase and maximize value according to the exact weight that you ship or receive.

After you opt in to the feature named Purchase Items That Are Priced in Their Secondary UOM, you can use the features described in this section.

Request Items That Are Priced in Their Secondary UOM

For items with dual units of measure, create requisitions in a UOM that matches how the item is packed and shipped, and is different from the UOM that you use to price and invoice the item. In update 21D, you could only use the requisition import (FBDI or Purchase Request Web Service) to create externally managed requisitions for items with dual UOMs. In this update, you can use the UI to create requisitions for items with dual UOMs, and use the requisition import to create internally managed requisitions for items with dual UOMs. We refer to this feature as dual units of measure in the procure-to-pay process.

When you create a requisition using the UI, you don't have to enter a quantity in two units of measure for dual UOM controlled items. You can provide either the primary UOM quantity or the secondary UOM quantity, and the transaction will be automatically tracked in both UOMs according to the UOM conversion rules.

Consider an example where Haddock fillets are priced in pounds but shipped in cases. According to the standard conversion, 1000 pounds of fish is equivalent to 10 cases, and per the BPA, the price of the fish is USD 2 per pound..

Item Primary UOM Quantity Secondary UOM Quantity BPA Price

Haddock Fillets

10 Cases 1000 pounds USD 2/pound

Here's how you use the feature to request items that are priced in their secondary UOM:

  1. Search or browse the Procurement catalog and see the item with the BPA price converted to the primary UOM case. According to the standard UOM conversion, USD 2/pound equates to USD 200/case.

  1. Drill down to the item details page to order 1000 pounds of fish.

Tip: Alternatively, you can order 10 cases of fish.

  1. Review your requisition and make any adjustments to the quantity by entering either the primary UOM quantity or the secondary UOM quantity.

Tip: Alternatively, you can use the Enter Requisition Line page to order the fish. Enter either the primary UOM quantity or the secondary UOM quantity, and the UOM conversion rules will be applied for any necessary quantity adjustment.

You can use dual units of measure to:

  • Track the item in a UOM that's different from the UOM that you use to stock the item. For example, use the primary UOM Cases to track the quantity that your customer orders, and use the secondary UOM Pounds to track the secondary quantity that you price and actually ship.

  • Create requisition lines, using the UI or requisition import, in two units of measure: primary and secondary.

  • Charge the right price to your purchase requests based on the actual quantity shipped in the secondary UOM using blanket purchase agreements. 

  • Process invoices for the purchase order line based on the actual units received in the secondary UOM of the item.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: ProcurementNo Longer Optional From: Update 22D

Tips And Considerations

  • Use the Opt In UI to enable the Purchase Items That Are Priced in Their Secondary UOM feature.

  • Opt into the feature, then price requisition line for items that use dual units of measure in the primary UOM or the secondary UOM using blanket purchase agreements.

    • If you have already opted into this feature in update 21D, then you need to manually run the ESS job Transform Data Post Upgrade. This process will update the shopping catalog index with the correct item prices for blanket agreements that are priced in the secondary UOM.

  • Enable an item for dual unit of measure tracking. The Manage Items task is used in the Product Information Management work area to set the Tracking Unit of Measure attribute to Primary and Secondary for the item.

  • Create your units of measure and then create the standard conversion to convert between the primary UOM and the secondary UOM.

  • Use purchase agreements to price dual UOM items. Your choices are different depending on whether you have a blanket agreement for the requisition line.      

    • Do have it, and the agreement line is priced in the item's secondary UOM. The agreement line price is converted to the primary UOM of the item, which is then saved as the requisition line unit price. In this case, you can't override the price of the blanket purchase agreement line, even if the price override is enabled. 

    • Do have it, and the agreement line isn’t priced in the item's secondary UOM. The agreement line price is saved as the requisition line unit price. If the price override is enabled in the agreement, you can override the agreement price in the requisition line.

    • Don't have it. The item's list price will be used as the price with the primary UOM of the item.

  • Use the Enter Requisition Line or the Item Details page,  to create requisition lines and provide either the primary UOM quantity or the secondary UOM quantity. The item's deviation factors don't apply to this feature.

  • Review and adjust the quantity or the secondary UOM quantity of dual UOM items in the Edit Requisition page. Optionally, you can use the mass edit window to update the quantity, which will in turn adjust the secondary quantity. The mass edit window doesn't support updates to the secondary UOM quantity.

  • In this release, you can also use this feature to create internally managed requisitions using either FBDI or Purchase Request Web Service. You can provide either the primary UOM quantity or the secondary UOM quantity. If you provide both, the secondary UOM quantity is calculated according to UOM conversion rules. The quantity you provide at the distribution level is based on the primary UOM, even if you provide only the secondary UOM quantity at the line level. When you provide the secondary UOM quantity and create multiple distributions, you can use the percentage attribute for the distribution allocation optionally.

  • You can’t use this feature with the purchase requisition REST resource for items that use dual units of measure.

Key Resources

For more information on how to price items in the secondary UOM using a blanket purchase agreement, refer to these features:

  • Purchase Items That Are Priced in Their Secondary UOM feature, available in the Oracle Procurement Cloud What's New, update 21D.
  • Automatically Derive Ordered Quantity for Items Priced in Their Secondary UOM feature, available in the Oracle Procurement Cloud What's New, update 22A.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to use this feature:
    • Requisition Self Service User (ORA_POR_REQUISITION_SELF_SERVICE_USER_DUTY)
    • Procurement Integration Specialist (ORA_PO_PROCUREMENT_INTEGRATION_SPECIALIST_JOB)    
    • Buyer (ORA_PO_BUYER_JOB)
    • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • If you're maintaining your own configured job roles: no new privileges were introduced to support this feature.

Automatically Derive Ordered Quantity for Items Priced in Their Secondary UOM

When you enter the secondary quantity in the secondary UOM for a dual UOM item, the application will automatically calculate the quantity in the UOM on the order line. In update 21D, you couldn't edit the secondary quantity. This update lifts that restriction. 

This screen capture illustrates the feature:

Enter the Secondary Quantity and Derive the Quantity Automatically

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: ProcurementNo Longer Optional From: Update 22D

To use this feature, you must opt in to the Purchase Items That Are Priced in Their Secondary UOM feature. If you previously opted in to the Purchase Items That Are Priced in Their Secondary UOM feature, then this feature is automatically enabled.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles can set up this feature:
    • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
    • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
  • Users who are assigned a configured job role that contains this privilege can set up this feature:
    • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)
  • Users who are assigned this predefined job role can access this feature in Purchasing:
    • Buyer (ORA_PO_BUYER_JOB)
  • Users who are assigned a configured job role that contains this privilege can access this feature in Purchasing:
    • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)

Import Purchase Orders for Items Priced in Their Secondary UOM

You can now create purchase orders for dual UOM items priced in their secondary UOM using the File-Based Data Import (FBDI) template.

A new Pricing UOM attribute is included on the FBDI template to price items tracked in the primary and secondary units of measure.

Purchase Order Import Template

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: ProcurementNo Longer Optional From: Update 22D

To use this feature, you must opt in to the Purchase Items That Are Priced in Their Secondary UOM feature. If you previously opted in to the Purchase Items That Are Priced in Their Secondary UOM feature, then this feature is automatically enabled.

Tips And Considerations

  • You can only provide a pricing UOM if the item is a dual UOM item.
  • You can enter the secondary UOM as the pricing UOM or the purchase order line UOM as the pricing UOM for dual UOM items.
  • If you don’t provide the pricing UOM, the purchase order line UOM will be used as the pricing UOM.
  • You can’t upload purchase order lines with the UOM set to the item’s secondary UOM.
  • If you don't provide the secondary quantity and secondary UOM for dual UOM items on purchase order lines, the value for the secondary UOM defaults from the Product Management item definition. The secondary quantity is calculated according to UOM conversion rules.
  • If you provide the secondary quantity but not under the UOM conversion rule, then the secondary quantity is overridden according to UOM conversion rules. Item's UOM deviation factors aren't considered.
  • If you reference a blanket purchase agreement on the order line, the pricing UOM must match the source agreement line UOM. If you don’t provide the pricing UOM, the value for the pricing UOM defaults from the source agreement line. If the source agreement line is priced in the secondary UOM, then the quantity UOM on the order line must be the primary UOM of the item.

Important Considerations

  • If you price the purchase order line in the secondary UOM, you can't use the Invoice Match to Receipt option.
  • If you price the order line in the secondary UOM, you can't use the order line for consignment.

Key Resources

  • Refer to the File-Based Data Import (FBDI) for Oracle Procurement Cloud documentation, available on the Oracle Help Center.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles can set up this feature:
    • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
  • Users who are assigned a configured job role that contains this privilege can set up this feature:
    • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)
  • Users who are assigned this predefined job role can access this feature in Purchasing:
    • Buyer (ORA_PO_BUYER_JOB)
  • Users who are assigned a configured job role that contains this privilege can access this feature in Purchasing:
    • Import Purchase Order (PO_IMPORT_PURCHASE_ORDER_PRIV_OBI)

Generate Reports on Purchase Orders for Items Priced in Their Secondary UOM Using OTBI

Generate reports and inquiries on purchase orders for items priced in their secondary UOM. For items that could be priced in either the primary or secondary UOM, you can now utilize the pricing UOM and quantity attributes directly in your analysis. Depending on how the item is priced, the pricing UOM attributes will hold either the corresponding order line UOM or the secondary UOM attribute values. The following Oracle Transactional Business Intelligence (OTBI) attributes are available under these folders:

  • Procure to Pay Real Time Subject Area: 
    • Purchase Order
      • Pricing UOM, Pricing UOM Name, Pricing UOM Description
    • Purchase Order Measures
      • Pricing Ordered Quantity, Pricing Open Ordered Quantity, Pricing Delivered Quantity
  • Purchasing Real Time Subject Area:
    • Purchase Order Lines > Purchase Order Line
      • Pricing Quantity
    • Purchase Order Lines > Purchase Order Line Details
      • Pricing UOM, Pricing UOM Name, Pricing UOM Description
    • Purchase Order Schedules -> Purchase Order Schedule
      • Pricing Schedule Quantity, Pricing Over Receipt Quantity, Pricing Received Quantity, Pricing Shipped Quantity, Pricing Accepted Quantity
    • Purchase Order Schedules -> Purchase Order Schedule Details
      • Pricing UOM, Pricing UOM Name, Pricing UOM Description
    • Purchase Order Distributions -> Purchase Order Distribution
      • Pricing Distribution Quantity, Pricing Distribution Delivered Quantity, Pricing Distribution Ordered Quantity, Pricing Canceled Quantity

Values for these attributes are taken from the underlying purchase order line, schedule, and distribution.

This screen capture illustrates the feature:

OTBI Report for Pricing in Secondary

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: ProcurementNo Longer Optional From: Update 22D

To use this feature, you must opt in to the Purchase Items That Are Priced in Their Secondary UOM feature. If you previously opted in to the Purchase Items That Are Priced in Their Secondary UOM feature, then this feature is automatically enabled.

After you have opted in to the feature, add Pricing UOM attributes to existing reports or use them in new reports. To learn more about how to create and edit reports, see the Creating and Administering Analytics and Reports guide.

Tips And Considerations

Important Considerations

  • Subject area attributes including pricing UOM and quantities are available without opt in; however, to generate reports for orders priced in the secondary UOM, you must opt in to the Purchase Items That Are Priced in Their Secondary UOM feature.
  • Evaluate whether you need to add pricing UOM attributes to reports if you are pricing purchase orders in the secondary UOM.
  • Evaluate whether you need to add pricing quantity metrics to reports if you need to compute or verify the amount metrics to the corresponding quantity in the pricing UOM.
  • Evaluate whether your own configured validation of amount should be changed when pricing in the secondary UOM.  You may need to use the pricing-related quantity columns for amount based validations. For example, an existing report shows the Purchase Order Distribution Amount and the Distribution Quantity to validate the amount value against the corresponding quantity.  You might consider using Pricing Distribution Quantity if that report expects the matching result for amount metrics to be unit price multiplied by quantity.  
  • Evaluate whether your own derived expressions should be changed when pricing in the secondary UOM.  You may need to use the pricing-related quantity columns for amount-derived expressions.   For example, if you have a derived PO Schedule Amount in any existing report with the expression Unit Price * Schedule Quantity, you might need to switch the Schedule Quantity to be the Pricing Schedule Quantity in the expression.
  • If reporting was done on purchase orders priced in secondary UOM in update 21D, although not supported, you might see a change in the value for quantity columns in update 22A. In update 21D OTBI, the UOM column shows the pricing UOM of the line. In update 22A OTBI, the UOM column shows the UOM of the line. Therefore, any reports created in update 21D for lines priced in the secondary UOM will see a value change in update 22A.  

Role Information

You have a couple of options for giving people access to use this feature, depending on whether you're assigning them predefined job roles or your own configured job role:

  • Users who are assigned any of these predefined job roles are automatically able to access the Procurement - Procure to Pay Real Time subject area:
    • Buyer (ORA_PO_BUYER_JOB)
    • Purchase Analysis (ORA_PO_PURCHASE_ANALYSIS_ABSTRACT)
    • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
    • Accounts Payable Manager (ORA_AP_ACCOUNTS_PAYABLE_MANAGER_JOB)
    • Accounts Payable Supervisor (ORA_AP_ACCOUNTS_PAYABLE_SUPERVISOR_JOB)
    • Accounts Payable Specialist (ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB)
  • Users who are assigned any of these predefined job roles are automatically able to access the Procurement - Purchasing Real Time subject area:
    • Buyer (ORA_PO_BUYER_JOB)
    • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
    • Purchase Analysis (ORA_PO_PURCHASE_ANALYSIS_ABSTRACT)
    • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
    • Procurement Contract Administrator (ORA_PO_PROCUREMENT_CONTRACT_ADMIN_JOB)
  • Users who are assigned configured job roles that contain this duty role are able to access the Procurement - Procure to Pay Real Time subject area:
    • Spend Transaction Analysis Duty (FBI_SPEND_TRANSACTION_ANALYSIS_DUTY)
  • Users who are assigned configured job roles that contain this duty role are able to access the Procurement - Purchasing Real Time subject area:
    • Purchase Order Transaction Analysis Duty (FBI_PURCHASE_ORDER_TRANSACTION_ANALYSIS_DUTY)

Self Service Procurement

Recover Approval Exceptions Using Action Details and Transaction Console

Review requisitions that are in pending approval status for exceptions. A requisition can be stuck in the approval process for reasons like a user isn’t active, a managerial approval hierarchy isn’t available, or inactive rules.

You can now review the approval process issues using the new Approval Process Error Details section on the Action Details page. You can access this page by clicking the Pending approval link on the Manage Requisitions, View Requisition Details, or Home page. You can then share the details with your approvals administrator, who can use the information to review and recover the transaction using Transaction Console.

Using this feature, you can now review and resolve requisitions that are in pending approval status due to some errors. These requisitions now won’t be rejected automatically and you don’t need to resubmit the requisition process.

These screenshots illustrate the feature.

Requisitions that are in Pending Approval Status

Requisitions That Are in Pending Approval Status

Example of Error when Manager is not available in the Supervisory Hierarchy

An Example of Error When Manager Isn't Available in the Supervisory Hierarchy

Empty Approval Group

Empty Approval Group

Ruleset did not return approvers

Ruleset Didn't Return Approvers

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Role Information

You have a couple of options for giving people access to the Transaction Console work area, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Predefined Job Role Name and Code:
    • Procurement Application Administrator (PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
  • Duty Role Name and Code for Configured Job Roles:
    • Review Procurement Approval Transactions as Administrator (ORA_PO_REVIEW_PRC_APPROVAL_TRANSACTIONS)