BAPI_PO_GETDETAIL1 in SAP Cloud ERP: what replaces it?

Use instead of BAPI_PO_GETDETAIL1

• I_PURCHASEORDERTP_2BDEFReleased

SAP successor classification: oneObject

Migration steps

1. List every place your custom code reads or writes BAPI_PO_GETDETAIL1; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with I_PURCHASEORDERTP_2 (BDEF).
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_PO_GETDETAIL1 per edition

• SAP Cloud ERP Private:Not releasedas of SAP S/4HANA 2023 FPS03
• 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_PO_CHANGEFUNC
• BAPI_PO_CREATE1FUNC
• BAPI_PO_GETITEMSFUNC

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository