> ## 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 Vendor Business Partners, SAP > Active Vendor Business Partners counts the active vendor Business Partners in the S/4HANA Cloud master data. How to read it, why it matters, and how to ... **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Vendor Master](/nerve-centre/connectors#connectors-by-type) > Count of active vendor Business Partners in the master data. The size of your supplier base, the number that frames procurement spend, payment-run scope, and master-data hygiene. ## At a glance > The count of Business Partners that carry an active vendor (supplier) role in the S/4HANA Cloud master data across the selected Company Codes. In the SAP Business Partner model, a single Business Partner can hold multiple roles; a vendor is a Business Partner with the supplier role and its associated company-code-level finance view (the modern equivalent of the classic LFA1 general data and LFB1 company-code data). This card counts how many of those vendors are active, not blocked or flagged for deletion. It is the denominator behind procurement spend analysis, the scope of every automatic payment run, and the first thing to check when master-data bloat creeps in. | | | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of Business Partners with an active vendor role across the selected Company Codes. Active means the supplier role exists, the Business Partner is not blocked for posting or purchasing, and it is not flagged for deletion or archiving. | | **Business Partner model** | S/4HANA Cloud uses the Business Partner (BP) as the single master-data object. A vendor is a BP with the supplier role; the same BP can also be a customer if it both buys and sells. The classic vendor master tables (general data conceptually like LFA1, company-code data like LFB1) are now views on the BP. The card keys on the active supplier role. | | **Active vs blocked vs flagged** | A vendor can be blocked for posting, blocked for purchasing, or marked for deletion without being removed. The card counts only genuinely active vendors. Blocked and deletion-flagged vendors are excluded so the count reflects suppliers you can actually transact with. | | **Company-code dimension** | A vendor's finance view is maintained per Company Code. A BP can be an active vendor in one Company Code and not extended to another. The card respects the selected Company Code scope, so the count reflects vendors active in the Company Codes in view. | | **Why informational** | This is a master-data scale metric, not an exception alert. There is no "right" number of vendors; the value is in tracking the trend and spotting unexpected jumps from a data load or a migration. | | **Company Code scope** | Respects the selected Company Code filter. By default counts active vendor Business Partners across every Company Code visible to the connected SAP API role. | | **Time window** | `RT` (real time, the current count of active vendor Business Partners) | | **Alert trigger** | Informational, no threshold | | **Roles** | owner, operations, finance | ## Calculation Calculated automatically from your SAP 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 distributor running SAP S/4HANA Cloud Public Edition with two Company Codes: 1000 UK Distribution Ltd (GBP) and 2000 EU Distribution BV (EUR). The card reads the live vendor master on 22 Jun 26. | Vendor population | Count | Counted as active? | | -------------------------------------------------- | ----------------- | ------------------ | | BPs with active supplier role, extended to CC 1000 | 612 | Yes | | BPs with active supplier role, extended to CC 2000 | 488 | Yes | | BPs active in both Company Codes (overlap) | -180 deduplicated | Counted once | | Vendors blocked for posting | 34 | No | | Vendors flagged for deletion | 21 | No | | One-time vendors (CPD account group) | 9 | Excluded by policy | | **Active Vendor Business Partners (this card)** | **920** | | Five things to notice: 1. **The headline is 920 active vendors, deduplicated across Company Codes.** A Business Partner extended to both CC 1000 and CC 2000 is one supplier relationship to the group, so it is counted once at the group level even though it has two company-code finance views. Drilling into a single Company Code shows that entity's own extended-vendor count. 2. **Blocked and deletion-flagged vendors are excluded.** 34 blocked and 21 deletion-flagged BPs are real records in the system but you cannot transact with them, so they do not belong in an "active vendors" count. A sudden drop in the headline often means a batch of vendors was just blocked or flagged, which is usually a deliberate clean-up. 3. **One-time vendors are excluded by policy.** The CPD (one-time-account) group exists so you do not create a permanent master record for a vendor you will pay once. Counting them would inflate the supplier base with throwaway records, so they are left out. 4. **The number is a denominator, not an alarm.** It is informational because there is no correct vendor count. It earns its place by framing other metrics: spend per vendor, payment-run scope, and on-time payment rates all read differently against a base of 920 vendors than against 9,200. 5. **Watch the trend, not the point.** A steady creep upward without procurement growth is master-data bloat, often duplicate vendors created because someone could not find the existing record. A sudden jump usually means a data load or an acquisition. Either is worth a glance even though there is no hard threshold. ## Sibling cards merchants should reference together The active vendor count is master-data context. It is most useful read alongside the AP and master-data cards that depend on it. | Card | Why pair it with Active Vendor Business Partners | | ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | [Vendor Payment On-Time Rate](/nerve-centre/kpi-cards/sap/vendor-payment-on-time-rate) | The on-time rate is computed across this vendor base. The count is the denominator behind the payment-performance picture. | | [AP Aging (60 days)](/nerve-centre/kpi-cards/sap/ap-aging-60-days) | What you owe these vendors, aged. Pair to see whether a growing vendor base is also a growing payables tail. | | [New Business Partners (30d)](/nerve-centre/kpi-cards/sap/new-business-partners-30d) | The inflow side. New BPs feed the active count; pair to see how fast the master data is growing. | | [Blocked Customers (BusinessPartnerIsBlocked=true)](/nerve-centre/kpi-cards/sap/blocked-customers-businesspartnerisblockedtrue) | The customer-side blocking view. Together they show how much of the BP master is blocked vs transactable. | | [SAP Active Customers](/nerve-centre/kpi-cards/sap/sap-active-customers) | The customer-role mirror of this card. The two together size the full Business Partner base. | ## Reconciling against SAP **Where to look in S/4HANA Cloud:** The closest native equivalents inside the SAP Fiori launchpad are: > **Manage Business Partner Master Data** Fiori app filtered to the supplier role > **Maintain Business Partner** (transaction BP) to inspect any single vendor's roles, blocks, and company-code views > **Supplier list** apps (Manage Suppliers / Display Supplier) for the procurement view of the vendor base > **Embedded Analytics**: supplier master CDS views that expose role, block status, and deletion flag To match this card, run the Manage Business Partner Master Data app filtered to the supplier role with block and deletion-flag filters set to exclude blocked and flagged records, and deduplicate Business Partners extended to multiple Company Codes. Scope the company-code finance view to the same Company Codes as the dashboard filter. Common mistakes when comparing against SAP's own reports: * **Counting company-code views instead of Business Partners.** A vendor extended to three Company Codes appears three times in a company-code-level list. The card counts the Business Partner once at group level. Deduplicate by BP before comparing. * **Including blocked or deletion-flagged vendors.** A raw vendor-list export includes everything. The card excludes blocked and flagged records. Apply the same filters to your export. * **Including one-time (CPD) accounts.** One-time vendor accounts are not part of the permanent supplier base. If your report includes them, the count will be higher than the card. **Why our number may legitimately differ from SAP's reports:** | Reason | Direction | Why | | -------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Deduplication across Company Codes** | Card lower | The card counts a multi-Company-Code vendor once; a company-code-level list counts it per Company Code. | | **Block and deletion filters** | Card lower | The card excludes blocked and deletion-flagged vendors; a raw export includes them. | | **One-time accounts** | Card lower | CPD one-time vendors are excluded by policy; some reports include them. | | **Company Code scope** | Either | The card respects the dashboard's Company Code filter. A report across a different set of entities will count a different population. | | **Role definition** | Either | The card keys on the active supplier role. A report keyed on a different role combination (for example BPs that are both customer and vendor) will differ. | ## Known limitations / merchant FAQs **Why is there no alert threshold?** Because there is no correct number of vendors. A business with 200 suppliers and a business with 20,000 can both be perfectly healthy. The card is informational by design: its value is in the trend and in framing other metrics, not in firing an alarm at an arbitrary count. **Why does a vendor extended to several Company Codes count only once?** Because at the group level it is one supplier relationship. A Business Partner with the supplier role extended to three Company Codes has three company-code finance views, but it is still one vendor to the group. The card deduplicates by Business Partner so the headline reflects distinct suppliers. Drill into a single Company Code to see that entity's extended count. **Are blocked vendors counted?** No. A vendor blocked for posting or purchasing cannot be transacted with, so it is excluded from the active count. A sudden drop in the headline often just means a batch of vendors was blocked during a clean-up, which is healthy master-data management. **What about one-time vendors?** One-time (CPD) accounts are excluded. They exist precisely so you do not create a permanent master record for a vendor you will pay once, so counting them would inflate the supplier base with throwaway records. **My count crept up over the year without more suppliers. What does that mean?** That is the classic signature of master-data bloat, usually duplicate vendor records created because someone could not find the existing Business Partner and made a new one. A steady creep with no procurement growth is worth a clean-up exercise, even though the card will not alert on it. **A customer that is also a supplier, how is it counted?** In the SAP Business Partner model, one BP can hold both the customer and supplier roles. This card counts it once, on the strength of its active supplier role. The same BP also appears in the customer-side cards on the strength of its customer role. **How fresh is the count?** It is real time. S/4HANA Cloud exposes Business Partner master data through live APIs, and Vortex IQ's connector refreshes frequently, so the count reflects the current vendor master. For record-level detail, pivot into the Manage Business Partner Master Data app or transaction BP. *** ### Tracked live in Vortex IQ Nerve Centre *Active Vendor Business Partners* is one of hundreds of KPI pulses Vortex IQ tracks across SAP 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.