> ## 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. # Blocked Customers (BusinessPartnerIsBlocked=true), SAP > Blocked Customers (BusinessPartnerIsBlocked=true) counts customer Business Partners flagged blocked in S/4HANA Cloud. How to read it, why it matters, and how to ... **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Customer Master](/nerve-centre/connectors#connectors-by-type) > Count of customer Business Partners flagged blocked. Blocked customers cannot transact until released, so this number is a direct read on stuck revenue and a busy credit-control team. ## At a glance > The count of customer Business Partners that carry a block flag in the S/4HANA Cloud master data across the selected Company Codes. A blocked customer cannot place orders, be billed, or post against until someone releases the block. Blocks exist for good reasons (credit risk, disputes, compliance holds, sanctions screening) but every blocked customer is also a customer you cannot sell to right now. This card turns a scattered master-data condition into a single number, so credit control sees the size of the held population and Finance can tell whether revenue is stuck behind a release queue. | | | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of customer Business Partners with a block flag set across the selected Company Codes. In the SAP Business Partner model this is the central block or a posting/order block on the customer role. A blocked BP cannot transact until the block is removed. | | **Types of block** | A customer can carry a central block (whole BP), a sales/order block (cannot order), a billing block, a posting block (cannot post to its account), or a deletion flag. The card focuses on blocks that prevent the customer transacting. Different block reasons can be set independently, so one customer can hold more than one. | | **Credit-management linkage** | Many blocks are automatic, set by SAP credit management (FSCM-CR) when a customer breaches its credit limit or has overdue items. These flow on and off as exposure changes. Other blocks are manual: a dispute, a compliance hold, or a sanctions-screening hit. | | **Business Partner model** | A customer is a Business Partner with the customer role and its company-code finance view. The block can sit on the central BP or on the company-code customer view, so a customer can be blocked in one Company Code and tradeable in another. The card respects the selected Company Code scope. | | **Why it matters** | A blocked customer is held revenue. A rising count means more orders are being stopped at the credit gate, which is either healthy risk control or a release queue that is not keeping up. The alert exists to make sure the queue is being worked. | | **Company Code scope** | Respects the selected Company Code filter. By default counts blocked customer Business Partners across every Company Code visible to the connected SAP API role. | | **Time window** | `RT` (real time, the current count of blocked customer Business Partners) | | **Alert trigger** | `>5` blocked customers flags for review | | **Roles** | owner, finance, operations | ## 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 B2B wholesaler running SAP S/4HANA Cloud Public Edition with two Company Codes: 1000 UK Wholesale Ltd (GBP) and 2000 EU Wholesale BV (EUR). The card reads the live customer master on 22 Jun 26. | Block reason | Company Code | Count | Counted? | | ------------------------------------ | ------------ | ----- | ---------------------------- | | Credit limit breach (auto, FSCM-CR) | 1000 | 4 | Yes | | Overdue items hold (auto) | 1000 | 2 | Yes | | Active dispute (manual) | 2000 | 1 | Yes | | Compliance / sanctions hold (manual) | 2000 | 1 | Yes | | Deletion flag only, no posting block | 1000 | 3 | No (not a transaction block) | | **Blocked Customers (this card)** | | **8** | | Five things to notice: 1. **The count is 8, above the `>5` alert threshold.** The Nerve Centre flags it. Eight customers cannot trade right now. The flag is a prompt for credit control to work the release queue, not a sign of a system fault. 2. **Six of the eight are automatic credit blocks.** Four hit their credit limit and two have overdue items, all set automatically by SAP credit management. These come and go as exposure and aging change: collect the overdue invoices or raise the limit and the block lifts on its own. This is the system working as designed. 3. **Two are manual blocks that need a human decision.** One is an active dispute and one is a compliance/sanctions hold. These will not clear automatically; someone has to resolve the dispute or complete the screening before the customer can trade. Manual blocks are the ones that tend to sit longest. 4. **Deletion-flagged customers are excluded.** Three customers carry a deletion flag but no posting block. A deletion flag is master-data lifecycle, not a transaction block, so it does not count here. The card only surfaces customers that are genuinely prevented from transacting. 5. **A customer blocked in one Company Code may trade in another.** Because the block can sit on the company-code customer view, a customer blocked in CC 1000 could still order in CC 2000. The count respects the Company Code scope in view, so the group total and a single-Company-Code drill-in can differ. ## Sibling cards merchants should reference together A blocked customer is held revenue and a credit-control signal. Read it with the AR and master-data cards that explain why the blocks are there. | Card | Why pair it with Blocked Customers (BusinessPartnerIsBlocked=true) | | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Customer Credit Utilisation](/nerve-centre/kpi-cards/sap/customer-credit-utilisation) | Most automatic blocks are credit-limit breaches. This card shows who is near or over their limit before the block fires. | | [AR Aging (60 days)](/nerve-centre/kpi-cards/sap/ar-aging-60-days) | Overdue items drive automatic holds. Pair to see whether blocks are an aging problem or a limit problem. | | [Overdue Invoice Value](/nerve-centre/kpi-cards/sap/overdue-invoice-value) | The money behind the overdue-item blocks. Collecting these is often the fastest way to clear blocks. | | [Customer Churn Signals](/nerve-centre/kpi-cards/sap/customer-churn-signals) | A customer blocked for a long time is a customer at risk of walking. Pair to spot blocks that are quietly becoming churn. | | [SAP Active Customers](/nerve-centre/kpi-cards/sap/sap-active-customers) | The transactable customer base. Blocked customers are the slice of the master that cannot currently sell, so the two together size the live customer population. | | [New Business Partners (30d)](/nerve-centre/kpi-cards/sap/new-business-partners-30d) | New customers can be blocked on creation pending credit setup or screening. Pair to see whether onboarding is creating a block backlog. | ## 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 customer role with block status set > **Maintain Business Partner** (transaction BP) to inspect a single customer's central, sales, billing, and posting blocks > **Manage Credit Cases / Credit Management** apps for the automatic credit blocks set by FSCM-CR > **Embedded Analytics**: customer master CDS views that expose block flags and reasons To match this card, run the Manage Business Partner Master Data app filtered to the customer role with a transaction-blocking flag set (central, sales, billing, or posting block), excluding records that carry only a deletion flag. Scope to the same Company Codes as the dashboard filter, since a block can sit on the company-code customer view. Common mistakes when comparing against SAP's own reports: * **Counting deletion flags as blocks.** A deletion flag is a lifecycle marker, not a transaction block. The card excludes deletion-only records; a raw export that filters on "any flag" will over-count. * **Missing company-code-level blocks.** A central block is visible everywhere, but a posting block on the company-code customer view only shows when you look at that Company Code. Scope your report to match the card. * **Confusing block reason with block type.** Credit-management blocks, manual sales blocks, and compliance holds are different reasons but all prevent transacting. Filtering to a single block reason will under-count. **Why our number may legitimately differ from SAP's reports:** | Reason | Direction | Why | | ---------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Deletion-flag exclusion** | Card lower | The card excludes records with only a deletion flag; a "any flag" export includes them. | | **Block type coverage** | Either | The card counts customers with any transaction-preventing block. A report filtered to one block type will count fewer. | | **Company-code vs central blocks** | Either | A block on the company-code view only appears at that Company Code. Scope mismatch changes the count. | | **Real-time auto blocks** | Either | Credit-management blocks flow on and off as exposure and aging change. The card is real time, so a snapshot report taken at a different moment will differ. | | **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. | ## Known limitations / merchant FAQs **Is a high blocked-customer count a bad thing?** Not necessarily. Blocks are a control working as intended: a customer over its credit limit or with overdue invoices should be stopped. The count becomes a problem when it climbs because the release queue is not being worked, so customers who could be released are sitting blocked and orders are piling up behind them. The alert exists to keep the queue moving, not to suggest blocks are wrong. **Why are deletion-flagged customers excluded?** Because a deletion flag is a master-data lifecycle marker, not a transaction block. A customer marked for deletion is being retired from the master, which is different from an active customer that is temporarily held. Counting deletion flags would mix two unrelated conditions. **Which blocks clear automatically and which need a human?** Credit-management blocks (limit breach, overdue items) clear automatically when the underlying condition changes: collect the overdue invoice or raise the limit and the block lifts. Manual blocks (disputes, compliance or sanctions holds) need a person to resolve the issue before the customer can trade. Manual blocks tend to sit longest, so they are worth watching. **Can a customer be blocked in one Company Code but not another?** Yes. A block can sit on the central Business Partner (everywhere) or on a company-code customer view (just that entity). So a customer blocked in CC 1000 may still order in CC 2000. The card respects the Company Code scope in view, which is why a group total and a single-Company-Code drill-in can differ. **Does this card show why a customer is blocked?** The headline is a count. The block reason lives on the Business Partner record, which you reach by pivoting into transaction BP or the Manage Business Partner Master Data app. Pairing this card with the credit-utilisation and AR-aging cards usually explains the automatic blocks without leaving the dashboard. **A blocked customer that is also a vendor, how is it counted?** This card keys on the customer role. If the same Business Partner is also a vendor, its vendor status is reflected in the vendor cards, not here. The customer block and the vendor status are independent. **How fresh is the count?** It is real time. S/4HANA Cloud exposes Business Partner block flags through live APIs, and Vortex IQ's connector refreshes frequently, so the count reflects the current block state. Automatic credit blocks in particular move quickly as exposure and aging change. For record-level detail, pivot into transaction BP. *** ### Tracked live in Vortex IQ Nerve Centre *Blocked Customers (BusinessPartnerIsBlocked=true)* 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.