Skip to content
ERP Preflight

FUNCbapi· MM-PUR-PO-2CL

BAPI_PO_CREATE1 in SAP Cloud ERP: what replaces it?

Custom code that reads or writes BAPI_PO_CREATE1 (FUNC) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names one successor: I_PURCHASEORDERTP_2.

Last verified:
Data source
Knowledge snapshot #3 · 33e0865dc811
Analyse your code for freeLook up another object
Cite:r/SAPINXHN

Use instead of BAPI_PO_CREATE1

SAP successor classification: oneObject

Migration steps

  1. List every place your custom code reads or writes BAPI_PO_CREATE1; 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_CREATE1 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.

Release history and evidence

8 release states from 9 official sources, last verified October 12, 2026.

Full release history and evidence

Terms used on this page

ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.