BAPI_BILLINGDOC_GETDETAIL in SAP Cloud ERP: what replaces it?

Use instead of BAPI_BILLINGDOC_GETDETAIL

• I_BILLINGDOCUMENTCDS_STOBReleased

SAP successor classification: oneObject

Migration steps

1. List every place your custom code reads or writes BAPI_BILLINGDOC_GETDETAIL; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with I_BILLINGDOCUMENT (CDS_STOB).
3. The successor is marked “Released” in the official release data, so the new code can use it in ABAP Cloud.
4. Re-run the cloud-readiness check on the changed code against your target release.

Release state of BAPI_BILLINGDOC_GETDETAIL per edition

• SAP Cloud ERP Private:Not releasedas of SAP Cloud ERP Private — latest release
• SAP Cloud ERP:Not releasedas of SAP Cloud ERP — current release

Objects with the same successor

These objects have the same official successor, so their usages can be migrated in the same change.

• BAPI_BILLINGDOC_DISPLAYFUNC
• BAPI_BILLINGDOC_EXISTENCECHECKFUNC
• BAPI_BILLINGDOC_GETLISTFUNC
• RV_INVOICE_DOCUMENT_READFUNC

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository