Customizing Objects in Transition
Many concepts from the SD-CAS world will remain in the CRM Add-on of S/4HANA – albeit with changed technical paths, naming conventions, or mapping logics. This chapter provides an overview of the most important objects and their migration.

1. Class System
  • The class type (e.g. Z99 Contacts (CIS mobile)) is retained
  • The object assignment now occurs to table CRMS4D_ACTV_H
  • Structure ZMCLF contains fields such as OBJTYPE_H and OBJECT_ID
  • Multiple classification and characteristic structures remain intact

2. Partner Schemas
  • Partner functions such as client, contact person, and contact will be adopted
  • Min/Max count and modifiability need to be checked
  • Linkage with Business Object Type BUS2000126 remains

3. Status Schemas
  • Standard statuses such as Open (0) or Closed (5) can be adopted
  • Check if existing status paths are available in S/4HANA CRM
  • Status transitions remain linked to user status

4. Issue Profiles & Code Groups
  • Example: Z0000001 for activity reasons, Z0000002 for results
  • Catalog A1 for reasons, A2 for status reasons
  • Assignment to code group profiles (e.g. 200000001) remains identical

5. Text Schemas
  • Text object: CRM_ORDERH, Text ID: e.g. "Report"
  • Maintenance via text schemas in CRM customizing
  • Texts will now be stored in CRMS4D_ACTV_TXT

These adjustments are the prerequisites for CIS mobile to retain its familiar functionality and utilize new features in the S/4HANA environment.