BUT000 table — Business Partner General Data

BUT000 stores central, role-independent identity data for each SAP Business Partner. Each row must be interpreted using the complete technical key and the application process that writes it. A consultant should first establish whether the row represents current state, a dated master-data slice, a document item, a history event, an index entry or a compatibility representation. Organizational levels, validity dates, fiscal years, ledgers, languages, statuses and sequence numbers are part of the grain whenever those dimensions exist. The table should be read as evidence of application behavior, not as an isolated spreadsheet. Confirm the owning business object and configuration before deciding that a value is wrong.

PARTNER and PARTNER_GUID identify the Business Partner at the general-master-data level. BP category, grouping and category-dependent name/identity fields are useful for diagnosis, but they do not establish active supplier or customer roles.

Connect BUT000 to address assignments (BUT020), identification records (BUT0ID) and the appropriate CVI mapping when customer or supplier integration is in scope. A single BP can have several addresses, IDs and organizational extensions.

When a supplier or sold-to party appears missing in a transaction, confirm the BP record first, then its role and purchasing/sales/company-code extensions. A BUT000 row alone is insufficient to prove that an organization can create a PO or sales order.

Take one reproducible example from the relevant SAP screen, report or application log. Record its full displayed key, organizational context, key date, language and status. Locate the matching BUT000 row using those values, then follow the documented parent and child joins without dropping key components. Compare the result using the same key date and ledger. When values differ, test for leading-zero conversion, multiple validity slices, inactive history, parallel ledgers, fiscal-year boundaries, archived data and asynchronous replication. Save the read-only evidence before escalating. If the row is wrong, reproduce the maintenance path in a non-production system and route the fix to the application owner rather than changing the table.

Business Partner is the mandatory leading customer and supplier master object in S/4HANA, making BUT000 a central master-data table. Customer and supplier roles are synchronized through CVI to classic customer/vendor structures where required; do not infer sales-area or company-code data from BUT000 alone.

Central BP master-data governance owns core identity and duplicate prevention. FI, MM and SD own role and organizational extensions; CVI integration teams resolve mapping or synchronization failures.

Review BUT000 with its connected SAP objects rather than in isolation. The main related objects in this draft are A, D, R, C, |, K, N, A, 1, |, L, F, A, 1. Relationship direction and cardinality depend on the full key and application context, so every graph link should be used as a navigation aid and confirmed against the installed release before it becomes production extraction logic.