SAP Knowledge Base Article - Public

3598071 - Decommission of PurchaseOrderAPI

Symptom

The exact decommission date for API_PURCHASEORDER_PROCESS_SRV PO ODATA V2 requires confirmation, with a notification alert desired before it is officially implemented.

Environment

SAP S/4HANA Cloud Public Edition 2502

Cause

API States

SAP APIs can be in any of the following states:
  • Beta: A version of an API that is not meant for productive use. Beta APIs may be changed or deleted from the API Hub at SAP’s discretion.
  • Active: A version of an API that is meant for productive use.
  • Deprecated: A version of an API that supports productive use but is destined to be Decommissioned. In cases where an Active version of the API exists, it is advisable to migrate to the Active version, however, an Active version may not exist in all cases.
  • Decommissioned: A version of an API that is no longer meant for productive use and is no longer supported by SAP.
API Lifespan and State Change
  • Minimum Lifespan:

    SAP will provide a minimum lifespan for non-Beta APIs of 24 months in Active or Deprecated states before announcing a Decommissioned state. For example, the minimum API lifespan ‘M’ for an API after it is published in Active version V1 is 24 months, where M is defined as the combined periods in Active and Deprecated states.

  • Deprecated -> Decommissioned:

    Once an API transitions from and Active to a Deprecated state, SAP will maintain the API in the Deprecated state for a minimum of 12 months before transitioning the API to a Decommissioned state.

  • Decommissioned:

    Decommissioned APIs are no longer supported by SAP may be deleted from the API Hub at SAP’s discretion.

  • Beta State Change:

    Beta APIs may be changed to an Active state or deleted from the API Hub at SAP’s discretion.

 

Resolution

SAP deprecate the V2 API 'API_PURCHASEORDER_PROCESS_SRV' with 2308. Deprecation indicates that the decommissioning of API V2 is planned for the future. Currently, the specific deprecation timeline cannot be guaranteed, switching to and familiarizing with the V4 API as soon as possible is strongly recommended.

This KBA will be updated as soon as there will be a final fix date for the decommission of V2.

See Also

KBA 3360429 - Differences Between OData API V2 API_PURCHASEORDER_PROCESS_SRV and V4 API_PURCHASEORDER 

Keywords

V2, V4, ODATA, Deprecated, Decommissioned , KBA , MM-PUR-PO-2CL , Purchase Orders (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition 2502