> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Active Suppliers, Oracle ERP Cloud > Active Suppliers from Oracle ERP Cloud. Count of suppliers in an active status in Oracle Procurement / Payables, a spend-base and supplier-master-hygiene metric. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Count of suppliers in an active status in Oracle Procurement / Payables. A spend-base and supplier-master-hygiene metric. ## At a glance > The number of suppliers held in an active status in the Oracle Procurement and Payables supplier master. It is two metrics in one: a measure of how broad your spend base is, and a measure of how clean your supplier master is. A supplier count that drifts far above the number you actually transact with usually means dormant, duplicate, or never-deactivated records, which is a procurement-governance and fraud-surface concern. A count that is too tight can mean over-aggressive deactivation that blocks legitimate purchasing. | | | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The count of suppliers whose status is active in the Oracle Procurement / Payables supplier master, within the Business Unit scope. Counts the supplier (the top-level party), not the number of supplier sites, addresses, or assignments beneath it. Excludes suppliers in inactive, on-hold, or end-dated status. | | **Currency** | n/a. This is a count metric. | | **Business Unit scope** | Respects the dashboard's Business Unit filter via supplier-site and procurement BU assignments. By default counts every active supplier the connected role can see. | | **Time window** | Real-time snapshot (RT). The active-status test is evaluated against the live supplier master at each sync. | | **Alert trigger** | None by default. A sudden jump usually signals a bulk onboarding or migration; a sudden fall signals a deactivation sweep. | | **Roles** | owner, operations, finance | ## Calculation Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A US Fortune 500 distributor on Oracle ERP Cloud with Procurement and Payables. Snapshot 12 Apr 26. | Supplier population | Count | | --------------------------------------------------- | ----- | | Active suppliers (this card) | 3,180 | | Suppliers with spend in the last 12 months | 1,940 | | Active suppliers with no PO or invoice in 24 months | 640 | | Suppliers on hold (excluded from the card) | 95 | | Inactive / end-dated suppliers (excluded) | 2,210 | Five things to notice: 1. **3,180 active, but only 1,940 transacted in a year.** The 1,240-supplier gap is the supplier-master-hygiene signal. Some of those are seasonal or contingency vendors you keep active on purpose; many are simply never-deactivated records that inflate the count and widen your fraud surface. 2. **640 active suppliers with no activity in 24 months is the cleanup candidate.** Two years of silence on an active record is the classic dormant-vendor pattern. Procurement governance teams routinely review these for deactivation, because an active-but-dormant supplier with banking details on file is a known payment-fraud vector. 3. **Suppliers on hold are excluded from the count.** The 95 on-hold suppliers are not active, so they do not count here. Hold is a deliberate intermediate state (a compliance review, a quality dispute) that suspends transacting without deactivating the master. 4. **The card counts the supplier, not the site.** A single active supplier may have many supplier sites (one per pay-from location or procurement BU). This card counts the top-level supplier once. If your procurement reporting counts sites, expect a higher number. 5. **Watch the trend, not just the level.** A jump from 3,180 to 3,900 in one period almost always means a bulk onboarding or a migration, not genuine spend-base expansion. A drop signals a deactivation sweep. Pair the level with [Vendor Payment On-Time Rate](/nerve-centre/kpi-cards/oracle-erp/vendor-payment-on-time-rate) to see whether the active base is being paid well. ## Sibling cards merchants should reference together Active Suppliers is the spend-base and supplier-hygiene anchor. Pair it with these to understand whether the base is healthy and well-managed. | Card | Why pair it with Active Suppliers | | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | [Vendor Payment On-Time Rate](/nerve-centre/kpi-cards/oracle-erp/vendor-payment-on-time-rate) | A large active base is only healthy if you pay it on time; together they describe supplier relationship health. | | [AP Aging 60 Days](/nerve-centre/kpi-cards/oracle-erp/ap-aging-60-days) | What you owe the active base, and how overdue it is. | | [Top Customers by Revenue](/nerve-centre/kpi-cards/oracle-erp/oerp-top-customers-revenue) | The customer-side mirror; together they frame both ends of the trading relationship. | | [Oracle Fusion Health Score](/nerve-centre/kpi-cards/oracle-erp/oracle-fusion-health-score) | Supplier-master hygiene feeds the overall data-health composite. | | [Top Findings Across Business Units](/nerve-centre/kpi-cards/oracle-erp/top-findings-across-business-units) | Dormant-supplier and duplicate-vendor findings surface here for action. | ## Reconciling against Oracle ERP Cloud **Where to look in Oracle ERP Cloud:** > **Navigator → Procurement → Suppliers → Manage Suppliers** (filter on status = Active) > **Navigator → Payables → Suppliers** (supplier list with status) > **Reports and Analytics → OTBI → Procurement / Supplier Real Time Subject Area** (count distinct active suppliers) Manage Suppliers in Procurement filtered to Active status is the canonical view and the closest one-to-one with this card. OTBI on the Supplier subject area lets you reproduce the exact count distinct of active suppliers, and to slice it by spend, last-activity date, and procurement BU to see the dormant tail this card includes. Common mistakes when comparing against Oracle's own reports: * **Counting supplier sites instead of suppliers.** A supplier with five sites appears as five rows in a site-level report. This card counts the supplier once. Match the level before reconciling. * **Including on-hold suppliers as active.** On-hold is a distinct status, not active. A report that filters on "not inactive" rather than "active" will pick up held suppliers and overstate. * **Mixing Procurement and Payables status.** A supplier can be active for purchasing but restricted for payment, or vice versa, depending on assignments. Decide which status governs your definition; the card uses the active supplier-header status by default. **Why our number may legitimately differ from Oracle's reports:** | Reason | Direction | Why | | -------------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Supplier vs site level** | Oracle report often higher | The card counts suppliers; a site-level report counts more rows per supplier. | | **Status definition** | Either | Active vs not-inactive vs not-on-hold are different filters. Align the exact status set. | | **Business Unit scope** | Either | A supplier active in one procurement BU may be unassigned in another. The card respects the dashboard BU filter. | | **Sync timing** | Small | A newly activated or deactivated supplier appears at the next sync. | | **Deactivation sweeps** | Card lower | A governance cleanup run in-period drops the count, correctly, before a scheduled report catches up. | ## Known limitations / merchant FAQs **What does active mean here?** A supplier whose status in the Oracle Procurement / Payables supplier master is active and is not end-dated, inactive, or on hold. Active means the supplier is eligible to be transacted with; it does not mean the supplier has actually been transacted with recently. **Why is the active count higher than the number of suppliers I actually buy from?** Because active is an eligibility state, not an activity state. Most supplier masters carry a long tail of active-but-dormant records: seasonal vendors, contingency suppliers, and records that were simply never deactivated. The gap between active suppliers and suppliers-with-spend is the supplier-master-hygiene signal worth reviewing. **Are on-hold suppliers counted?** No. On hold is a deliberate intermediate status that suspends transacting (for a compliance review or a dispute, say) without deactivating the master. The card counts only active suppliers, so held suppliers are excluded. **Does the card count supplier sites?** No, it counts the supplier (the top-level party). A single supplier can have many sites, one per pay-from location or procurement BU. If your procurement team reports at site level, their number will be higher than this card. **Why does the count matter for fraud and governance?** Every active supplier with banking details on file is a potential payment destination. A bloated active master with dormant records widens the attack surface for invoice fraud and bank-detail tampering. Keeping the active count tight to the suppliers you genuinely use is a core procurement control. **A migration just doubled the count. Is that real?** No. A sudden large jump is almost always a bulk onboarding or a data migration, not genuine spend-base growth. Read it as an onboarding event and confirm against your load schedule. **Does an active supplier with no spend appear in spend reports?** No. Spend reports key on PO and invoice activity, so a dormant active supplier shows in this card but not in spend analysis. That divergence is exactly the dormant-vendor population you want to review. **Differences vs SAP or NetSuite supplier counts?** SAP holds vendors as business partners with a vendor role and a block/deletion flag; NetSuite holds a Vendor record with an inactive checkbox. Oracle uses the Procurement supplier with status and assignments per BU. The active-supplier concept is the same across all three; the status model and the site hierarchy differ. Vortex IQ supports all three. *** ### Tracked live in Vortex IQ Nerve Centre *Active Suppliers* is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.