Notes for Developers
The migration to the CRM add-on in S/4HANA involves some technical changes that developers should consider. This chapter describes relevant tables, interfaces, extension points, and possible adjustments for integration with CIS mobile.

1. Note the new table structure
  • Activity header: CRMS4D_ACTV_H
  • Text objects: CRMS4D_ACTV_TXT
  • Classification: KSSK, AUSP, INOB (still valid)
  • Partner: CRMD_PARTNER
  • Status management: TJ30, TJ31, TJ32

2. Relevant BAdIs and User Exits
  • BADI_ORDER_SAVE
  • CRM_ORDER_STATUS
  • CRM_ORDER_MAINTAIN
  • BADI_CRM_PARTNER_UPDATE

3. Migration techniques
  • Data transfer via LSMW or customer-specific report
  • Optional: Use of CRM_ORDER_MIGRATE
  • Test data creation via CRMD_ORDER

4. Integration with CIS mobile
  • Use of customized function modules (RFC)
  • Example: Call the table CRMS4D_ACTV_H to display activities
  • BAPI calls may need to be adjusted (BAPI_ACTIVITYCRM_CREATE, etc.)
  • Check custom tabs and extension fields in VB.NET interface

5. Tools and resources
  • Log display: SLG1
  • CRM Debugging: CRM_ORDER_READ, CRM_ORDER_MAINTAIN
  • Structure display: CRMD_ORDER with detailed review

Developers should become familiar with the new structure early on to implement necessary adjustments efficiently – both in the SAP system and in the mobile integration.