Skip to content
ERP Preflight

CLASclass· BC-ABA-LA

CX_ABAP_HTTP_TIMESTAMP_INVALID: Clean Core status and successor

CX_ABAP_HTTP_TIMESTAMP_INVALID is an SAP class (object type CLAS) in application component BC-ABA-LA. In SAP BTP ABAP environment SAP BTP ABAP environment — current release its official release state is “Released”.

Last verified:
Data source
Knowledge snapshot #3 · 33e0865dc811
Cite:r/SAPINXHN

Answer

Released — no successor required

The object is part of the released ABAP Cloud API contract for this release.

Release: SAP BTP ABAP environment — current release

What this page answers: Whether CX_ABAP_HTTP_TIMESTAMP_INVALID may be used in ABAP Cloud / clean core development, in which releases, and what to use instead.

What to do

Use CX_ABAP_HTTP_TIMESTAMP_INVALID directly in ABAP Cloud code; it is part of the released API contract in the releases marked “Released”.

What ERP Preflight reports when custom code uses CX_ABAP_HTTP_TIMESTAMP_INVALID

Released objects are reported for information only.

Release state per release

Release state per release
EditionReleaseStateSuccessor
SAP BTP ABAP environmentSAP BTP ABAP environment — current releaseReleased· A
none

    Lifecycle per edition

    • SAP BTP ABAP environment

      Current state: Released (SAP BTP ABAP environment — current release)

      First released in: SAP BTP ABAP environment — current release

      Deprecated since: not deprecated

    Evidence and provenance

    Only global, reviewed knowledge is shown. Customer data from workspaces is never used by the free tools.

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