Skip to main content

Procurement Performance Management Dashboard


Procurement Performance Management Dashboard

Use the Procurement Performance Management reports to help you manage your buyers
and procurement activities:
• How are my buyers performing based on the number and purchase order amount of
processed and fulfilled requisition lines?
• How long on average did it take for buyers to process an order, from requisition approval date to purchase order approval date?
• How long on average did it take for buyers to fulfill an order, from requisition approval date to receipt or invoice date?
• What volume of purchase orders was created manually?
Procurement Performance Management KPIs
Key performance indicators (KPIs) for procurement performance management are described below.

These KPIs enable procurement managers to view how much work their organization is doing in volume and amount of processed requisitions, including how long on average it took to process the requisitions.

• Processed Requisition Lines: Number of approved requisition lines that are not canceled, returned, or rejected, that are on an approved purchase order or release.

• Processed Requisitions Amount: Price * Quantity.
Sum of the purchase order or release shipment amounts corresponding to each processed requisition line.

• Processed Average Age (Days): Number of Days to Process / Processed Requisition Lines. Number of Days to Process is the sum of the number of days between the processed requisition line’s last approval date and the last approval date of the corresponding purchase order or release shipment; this number is divided by the number of processed requisition lines. Both date and time (hours, minutes, seconds) are taken
into account.

These KPIs enable procurement managers to measure the productivity of their organization by seeing the volume of fulfilled requisitions, including how long it took on average to fulfill the requisitions, from requisition approval to rendering of the goods or services.
• Fulfilled Requisition Lines: Number of approved requisition lines that are not canceled, returned, or rejected, whose corresponding purchase order or release shipments have been received within the receipt close tolerance percentage (if 3-Way or 4-Way matching is used), invoiced within the invoice close tolerance percentage (if 2-Way matching is used), or closed. The status of a fulfilled shipment is Closed for
Receiving, Closed for Invoicing, or Closed.

• Fulfilled Requisitions Amount: Price * Quantity.
Sum of the amounts on each purchase order or release shipment referenced by each fulfilled requisition line.

• Fulfilled Average Age (Days): Number of Days Pending / Fulfilled Requisition Lines. Number of Days Pending is the sum of the number of days between the fulfilled requisition line’s last approval date, and the receipt or invoice date; this number is divided by the number of fulfilled requisition lines. Both date and time (hours, minutes, seconds) are taken into account.

• Percent Past Expected Date: (Fulfilled Requisition Lines Past Expected Date / Fulfilled Requisition Lines) * 100. Percentage of fulfilled (received or invoiced) requisition lines that were fulfilled past the Promised Date or Need-By Date on the purchase order or release shipment, or
past the Need-By Date on the requisition line, whichever is available.
Executive Dashboard
Executive Dashboard
Executive Dashboard

Comments

Popular posts from this blog

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Oracle Fusion Cloud: Supplier Import Process using File Based Data Import (FBDI)

 Supplier Data Migration or Upload to Oracle Fusion environment File-Based Data Import for Oracle Procurement Cloud Supplier import in oracle fusion   In this post , We will discuss about Supplier import in oracle fusion. Oracle has provided the FBDI tool to import suppliers from External  Source  to the Oracle fusion. Supplier Import in Oracle fusion we first need to  Download  the Supplier Import FDBI  templates  given by the Oracle fusion to import suppliers. Oracle has given 5 Different FBDI templates to Import supplier in Fusion. Here in this post , I will share the Complete steps for Supplier import in oracle fusion. You can refer this post for Supplier Import.   Steps for Supplier import in oracle fusion     Step1- First we need to download Supplier Data  Template  from Oracle Repository. Go to this path for Oracle Repository. ( select Based on your Cloud version) https://docs.oracle.com/en/...

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects Introduction When it comes to contractual billing, invoice and revenue generation are two separate processes, which during the lifespan of a project may or may not always coincide with each other and so do the balances in revenue and receivables accounts.  This interim difference between revenue and invoice account balances is bridged using Unbilled Receivables (UBR) and Unearned Revenue (UER) Accounts. Unearned Revenue (UER) Unearned Revenue (also termed as deferred revenue or UER) signifies money received for the goods or services, which are yet to be delivered.  As per the principles of Revenue Recognition, UER is recorded as on the balance sheet unless it is converted to Revenue upon delivery of goods or services For Example XYZ Consulting Ltd. receives an annual maintenance contract of $ 12,000 on Dec 31, 2014 for the period of Jan 01, 2015 to Dec 31, 2015. At the start of the contract as of Dec 31, 2...