Count of Business Partners created in the last 30 days vs the prior period. The pulse of master-data growth, customer onboarding speed, and whether new records are flowing in clean.
At a glance
The count of Business Partners created in the trailing 30 days across the selected Company Codes, compared with the prior 30-day period. In the SAP Business Partner model a new BP can be a new customer, a new vendor, or both, and it can arrive from a person creating it in transaction BP, from a commerce-platform sync, or from a bulk data load. This card measures the inflow into the master data. Read as a vs-prior comparison it tells you whether onboarding is accelerating, steady, or has spiked because of a migration or an integration that started creating duplicates.
| What it counts | The number of Business Partners whose creation date falls in the trailing 30 days across the selected Company Codes, shown against the prior 30-day period. A BP is counted once on creation regardless of how many roles it carries. |
| What “new” means here | Newly created Business Partner records, keyed on the BP creation date. This includes new customers (BPs with the customer role), new vendors (supplier role), and BPs that hold both. It is creation, not first transaction, so a BP created today but not yet ordered still counts. |
| Sources of new BPs | Manual creation in transaction BP or the Manage Business Partner Master Data app, commerce-platform syncs that create a Business Partner for a new storefront customer, B2B onboarding workflows, and bulk loads or migrations. The source matters when a number spikes. |
| Why vs prior period | The absolute count means little without context, so the card shows the trailing 30 days against the prior 30 days. A steady inflow is healthy onboarding; a sharp jump usually means a data load, an acquisition, or an integration creating duplicates. |
| Customer vs vendor mix | A new BP can carry the customer role, the supplier role, or both. The headline counts all new BPs; the customer and vendor cards show the role-specific populations. Most commerce-driven creation is customer-role BPs. |
| Company Code scope | Respects the selected Company Code filter. By default counts new Business Partners across every Company Code visible to the connected SAP API role. A BP extended to several Company Codes is counted once on creation. |
| Time window | 30D vsP (trailing 30 days vs the prior 30 days) |
| Alert trigger | Informational, no threshold |
| Roles | owner, finance, marketing |
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 and DTC brand running SAP S/4HANA Cloud Public Edition with two Company Codes: 1000 UK Brand Ltd (GBP) and 2000 EU Brand BV (EUR). New customers flow in from a Shopify Plus DTC store and a B2B portal, plus the occasional vendor onboarding. The window is 23 May 26 to 22 Jun 26, compared with 23 Apr 26 to 22 May 26.| Source of new Business Partner | This 30 days | Prior 30 days |
|---|---|---|
| DTC customers synced from Shopify Plus | 184 | 171 |
| B2B portal customers (onboarding workflow) | 22 | 19 |
| New vendors (supplier role) | 6 | 8 |
| Bulk load (one-off supplier import) | 0 | 0 |
| New Business Partners (this card) | 212 | 198 |
- The headline is 212 new Business Partners, up 7.1% on the prior 198. The card is informational, so nothing alerts, but the gentle rise tracks healthy onboarding momentum. The vs-prior framing is what makes the number readable: 212 alone says little, 212 vs 198 says “growing steadily”.
- Most of the inflow is DTC customer creation. 184 of the 212 are Shopify customers synced into S/4HANA as customer-role Business Partners. This is the normal commerce-to-ERP flow: a storefront sign-up or first order creates the BP so the order can post and bill.
- A spike would be the thing to investigate, not the steady number. If this card had read 1,200 instead of 212, the most likely cause is a migration, an acquisition, or an integration that started creating a new BP for every order instead of matching to the existing customer. Duplicate creation is the silent failure mode the trend exposes.
- A new BP counts on creation, not on first order. The 22 B2B portal customers include several who have signed up but not yet placed an order. They count here because the record exists, even though they will not appear in transaction-based cards until they trade.
- The same BP extended to both Company Codes counts once. A new B2B customer set up to trade with both UK Brand Ltd and EU Brand BV is one new Business Partner, counted once on creation, even though it has two company-code customer views. Drilling into a single Company Code shows that entity’s own new-creation count.
Sibling cards merchants should reference together
New BP creation is the inflow side of the master data. Read it with the population and quality cards to see whether the inflow is clean.| Card | Why pair it with New Business Partners (30d) |
|---|---|
| SAP Active Customers | The total customer population. New BPs feed it; pair to see whether the base is growing in line with creation. |
| Active Vendor Business Partners | The vendor side of the master. New supplier-role BPs feed this count. |
| Blocked Customers (BusinessPartnerIsBlocked=true) | New customers can be blocked on creation pending credit setup or screening. Pair to see whether onboarding is creating a block backlog. |
| Ecom Customers Absent from SAP Business Partner | The flip side: commerce customers who should have become a BP but did not. A low new-BP count alongside a high absent count means the sync is failing. |
| Customer Churn Signals | New BPs are acquisition; churn signals are loss. The two together frame net customer growth. |
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 a creation-date range Maintain Business Partner (transaction BP) to inspect any single new BP’s roles and creation administrative data Customer / Supplier list apps for the role-specific view of recent creations Embedded Analytics: Business Partner master CDS views that expose the creation date and creating userTo match this card, run the Manage Business Partner Master Data app filtered to a creation date in the trailing 30 days, deduplicate Business Partners extended to multiple Company Codes, and scope to the same Company Codes as the dashboard filter. Repeat for the prior 30 days to reproduce the vs-prior comparison. Common mistakes when comparing against SAP’s own reports:
- Filtering on first transaction instead of creation date. The card keys on the BP creation date. A report that counts customers by first order or first invoice will miss BPs created but not yet transacting, and will show a different number.
- Counting company-code extensions as new BPs. Extending an existing BP to a new Company Code is not a new creation. The card counts the original creation once; a company-code-level report can mistake an extension for a new record.
- Double-counting multi-role BPs. A BP created with both customer and supplier roles is one creation. A report that counts by role will count it twice.
| Reason | Direction | Why |
|---|---|---|
| Creation date vs first transaction | Either | The card counts on creation date; a transaction-based report counts on first order or invoice and excludes not-yet-trading BPs. |
| Company-code extension | Card lower | Extending an existing BP to a new Company Code is not a new creation. The card does not count it; a company-code report might. |
| Multi-role deduplication | Card lower | A BP created with both roles counts once; a role-based report counts it per role. |
| Window boundaries | Either | The trailing-30-day and prior-30-day boundaries must match exactly. A calendar-month report will not align with a rolling 30-day window. |
| 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. |