Skip to content
ERP Preflight

BADI_DEFbadi· FI-LOC-LO-IN

BADI_J_1IG_SUBCON in SAP Cloud ERP: what replaces it?

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

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

Use instead of BADI_J_1IG_SUBCON

SAP successor classification: oneObject

Migration steps

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

  • SAP Cloud ERP Private:Releasedas of SAP S/4HANA 2023 FPS03 · released since SAP S/4HANA 2022 FPS01
  • SAP Cloud ERP:Deprecatedas of SAP Cloud ERP — current release · deprecated since SAP Cloud ERP — current release

Release history and evidence

7 release states from 7 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.