SAP MDG · DATA MODEL & UI

What are few practical examples of issues faced in Upgrade for HANA 2025 for MDG

SAP HANA 2025 Upgrade Issue for SAP MDG

SMT Mapping for BP for Custom Fields with standard data element is not supported anymore.

This needs to be handled in Handler Class.

SAP Note 3785535

Field Descriptions have changed sligtly (Name to Name 1 and PO Box to P.O.Box ) for CEPC and CSKS table.

So if any coding is based on the fields description, it might need a review

For Consolidation Custom Table, the Field MANDT to CLIENT or Vice Versa might be needed for Backend Custom Tables.

Even though older code, some may face it with HANA 2025 version Data Replication for MDG Finance data, Merges the editions(Validity Periods) if there is no change in time Dependent data in multiple editions in MDG.

Also the replication of data to S4, on failure, doesn't send back the Error confirmation message if FEH (Forward Error Handling) is enabled.

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • HANA 2025 Upgrade
  • MDG Custom Field Replication from Staging to KNA1 Fails After 2025 Upgrade

Possible questions

  • HANA 2025 Upgrade
  • MDG Custom Field Replication from Staging to KNA1 Fails After 2025 Upgrade
  • What configuration is required for SAP HANA 2025 Upgrade Issue for SAP MDG?
  • How can this SAP MDG scenario be tested?

Keywords

Upgrade issues2025HANA 2025S4 2025 MDG issues