How CSDM concepts map to CMDB tables
The objects in the conceptual CSDM framework must map to the physical model objects (CIs and CI class tables) in the CMDB. You can navigate in the platform to see dictionary attributes.
Business Application data belongs in the cmdb_ci_business_app table, and not in the cmdb_ci_app table.
Life Cycle Stage inheritance for Business Application records
Business Application records define a restricted set of Life Cycle Stage values that are intended to reflect application planning and usage, such as Ideation, Design, Operational, and End of Life. These life cycle definitions are configured using the life_cycle_control table specifically for the cmdb_ci_business_application class. When you view or edit a Business Application record, however, additional Life Cycle Stage values such as Deploy and Inventory might also appear. These stages are not defined directly for Business Application, but are inherited from parent CI classes (for example, cmdb_ci) through the aggregation-based inheritance model that is used by life_cycle_control. In this model, life cycle definitions from the current CI class are combined with life cycle definitions from all parent classes in the CMDB class hierarchy. Child classes therefore extend parent life cycle definitions rather than overriding them. As a result, Business Application records can display Life Cycle Stage values that are applicable to infrastructure or hardware CIs but might not be semantically meaningful for applications. This behavior is expected and working as designed.
In contrast, in sys_choice inheritance definitions in child tables override the values in parent tables.