What is the "LFA1 direct access" issue in S/4HANA migration?

LFA1 (Vendor master) direct access. S/4HANA uses Business Partner model for vendors. Use released CDS view I_Supplier. Direct LFA1 writes are blocked.

How much effort does it take to fix "LFA1 direct access"?

Remediation effort is rated M — Medium (days). Severity: HIGH.

Which tool checks for LFA1 direct access automatically?

The s4ready.ai A1 Readiness Scanner checks for LFA1 direct access (and 29 other rules) automatically across your custom ABAP codebase. Results include object-level findings with severity and effort estimates.

HIGH Effort: M — Medium (days) Deprecated Tables

How to remediate: LFA1 direct access

LFA1 (Vendor master) direct access. S/4HANA uses Business Partner model for vendors.

Is this issue in your codebase?

A1 scans all 30 rules across your custom ABAP — results in minutes.

Scan your codebase free →

What changes in S/4HANA

Use released CDS view I_Supplier. Direct LFA1 writes are blocked.

Before and after: ABAP code example

Before (ECC)

* ECC: LFA1 direct write — blocked in S/4HANA
MODIFY lfa1 FROM ls_vendor.

After (S/4HANA)

* S/4HANA: Supplier via Business Partner API
CALL FUNCTION 'BAPI_BUPA_CENTRAL_CHANGE'
  EXPORTING
    businesspartner = lv_bpnr
    centraldata     = ls_central
  IMPORTING
    return          = lt_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
  EXPORTING wait = abap_true.

Effort estimate and common pitfalls

Effort estimate

M — Medium (days)

Estimate is per affected object. Total effort scales with the number of occurrences in your codebase. Use the A1 scan to get an object-level count before estimating the full project.

Common pitfalls

! Missing related objects that contain the same pattern
! Not testing edge cases after replacing the API
! Skipping regression tests for dependent programs

Related rules to check

HIGH M

KNA1 direct access

KNA1 (Customer master) direct access. S/4HANA uses Business Partner model — KNA1 is still present but populated via BP.

CRITICAL XL

BSEG direct access

BSEG is a cluster table in ECC. In S/4HANA, financial data moved to ACDOCA (Universal Journal).

HIGH L

Deprecated vendor BAPIs

BAPI_VENDOR_* function modules are deprecated. Use Business Partner APIs.

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including LFA1 direct access — across your custom ABAP objects and produces a prioritised remediation backlog.

Scan your codebase for this issue free →

← All remediation rules Resources →

SAP, S/4HANA and ABAP are trademarks of SAP SE. s4ready.ai is an independent solution and is not affiliated with, endorsed by, or sponsored by SAP SE.