C_CHANGERECORDPARTNERDEX in SAP Cloud ERP: what replaces it?

Use instead of C_CHANGERECORDPARTNERDEX

• C_CHANGERECORDPARTNERDEX_2CDS_STOBReleased

SAP successor classification: oneObject

Migration steps

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

• SAP Cloud ERP:Deprecatedas of SAP Cloud ERP — current release · deprecated since 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.

• C_CHGRECRESPONSIBLEDEXCDS_STOB

Terms used on this page

• Released API
• Successor
• Deprecated object
• CDS view
• ABAP Cloud
• Cloudification Repository