What replaces BAPI_PRDSRVAPSIF_RECEIVELIST2 in SAP S/4HANA Clean Core?

No released successor is named in SAP's data for BAPI_PRDSRVAPSIF_RECEIVELIST2; assess alternatives (released APIs, standard, retirement) for your target release.

Is BAPI_PRDSRVAPSIF_RECEIVELIST2 released for ABAP Cloud?

BAPI_PRDSRVAPSIF_RECEIVELIST2 is not released and has no released successor path.

BAPI_PRDSRVAPSIF_RECEIVELIST2

DClean core level D — ReplaceSAP state: noAPIATC expected: noAPI · priority 1 (error)

Two questions, two answers. The level D above answers the clean core target question — what this object is worth in an ABAP Cloud target. Whether classic ABAP may still call it is a separate property, and it is the right-hand column.

ABAP Cloud view

Not listed

The release file does not mention it, so it says nothing either way.

objectReleaseInfo

Classic view

noAPI

SAP classifies it as not intended for customer use.

objectClassifications_SAP

BAPI_PRDSRVAPSIF_RECEIVELIST2 has no released API successor in the SAP Cloudification Repository.

No clean path

SAP classifies this object as noAPI — not intended for customer use — and names no replacement. Custom code calling it cannot simply be re-pointed; assess alternatives for your target release: a released API, the standard, or retiring the code. This is an honest limitation, not an omission.

See how your code uses BAPI_PRDSRVAPSIF_RECEIVELIST2

This is the object-level answer. To see, per object, whether your actual ABAP can move to the successor or needs an architect — with evidence — run a free ABAP static code analysis.

Analyze free at clean-core.io

→ ABAP static code analysis → Clean Core object classification (A–D)→ What is the Clean Core Score?→ SAP cloudification explained → Clean Core guide (RAP vs CAP)→ Browse the full catalog