HIGH Effort: L — Large (1–2 weeks) Deprecated APIs

How to remediate: Deprecated vendor BAPIs

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

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

Vendor creation/change must go through Business Partner (BUPA) APIs.

Before and after: ABAP code example

Before (ECC)
* ECC: deprecated vendor BAPI
CALL FUNCTION 'BAPI_VENDOR_CREATE'
  EXPORTING
    companycode    = lv_bukrs
    vendordata     = ls_vendor
  IMPORTING
    vendorno       = lv_lifnr
    return         = lt_return.
After (S/4HANA)
* S/4HANA: Business Partner API for supplier
CALL FUNCTION 'BAPI_BUPA_CREATE_FROM_DATA'
  EXPORTING
    partnercategory = '2'
    centraldata     = ls_central
    addressdata     = ls_address
  IMPORTING
    businesspartner = lv_bpnr
    return          = lt_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
  EXPORTING wait = abap_true.

Effort estimate and common pitfalls

Effort estimate

L — Large (1–2 weeks)

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

  • ! Underestimating the number of affected objects
  • ! Missing performance test after switching to released APIs
  • ! Transport dependencies across development, quality, and production

Related rules to check

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including Deprecated vendor BAPIs — across your custom ABAP objects and produces a prioritised remediation backlog.

Scan your codebase for this issue free →

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.