SAP Knowledge Base Article - Preview

3093382 - Purpose and standard behavior of the Central Block ( BUT000-XBLCK) in the transaction BP


Central Block field (BUT000-XBLCK) blocks Business Partner centrally so that other applications cannot modify Business Partner Data. Central Block flag is not used to avoid the use of the business partner, but to avoid certain activities. This depends on the other applications logic that is using the BP, not the BP itself. The field BUT000-XBLCK only becomes relevant when another application is involved.

E.g.: any business transaction like a sales order. If the controlling application of sales order creation has a check implemented e.g. for the central block field, then they might throw an error that BP cannot be used in the sales order due to the fact it is centrally blocked.

If the Central lock field(XBLCK) is set, the Central Posting Block (LFA1-SPERR) and the Central Purchasing block (LFA1-SPERM) of the corresponding vendor would NOT be set automatically. This was delivered with the SAP Note 1666895.

If you want to block a vendor in PO and/or FI documentation, you need to use directly the field Central Posting Block (LFA1-SPERR) and/or the field Central Purchasing block (LFA1-SPERM).







SAP ERP all versions ; SAP S/4HANA all versions


central block, BUT000-XBLCK, LFA1-SPERM, LFA1-SPERR, BP, customer, vendor, update, updated, automatically, purpose, activities, effect , KBA , LO-MD-BP , Business Partners , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.