Skip to Content

SAP Charm Basic Business Transaction Table Storage Diagram

Hi there:

We created a small basic diagram that shows you and your developers which are main tables related to ChaRM where the Business Transaction data gets stored.

Two main component sets are part of the diagram:

  1. Business Partner, where you find the tables with data related to the BP, identification, HR related information, etc.
  2. Transaction, where you find the tables that store most of the Business Transaction related data, including our own customer developments.

It is important to mention that within each box, we placed the main table fields that server as connectors between tables, following the arrows.    Kind of foreign keys.

There is still an extra resource you may already know.  The report CRM_ORDER_READ.  In that report, you provide a Business Transaction and you will obtain the list of tables that contain records that pertain to that BT in particular.    Unfortunately, the report does not give you a connection between an RfC (ZMCR) and its own Change Objects (ZMMJs), or between either of them and their date field values.  At that moment is when the provided diagram gives you the complementary assistance to hook up the pieces together.

We hope the diagram becomes beneficial for you and any feedback to make it better is very appreciated.

Our apologies for the colors.  There was no inspiration for that today.  They were used to highlight the pairs of tables that stored complementary-to-one-another data.


Juan-Carlos Garcia-Garavito

Updates:  2014-Apr-01.  Better resolution and added Project-related linked tables.

You must be Logged on to comment or reply to a post.
  • Hola Juan-Carlos,

    nice diagram. Shows some of the important underlying CRM tables and how they are connected.

    Even though no relationship to ChaRM or Solution Manager tables..  like the relationship between correction and transports and how these fit in would be a nice addition.

    You mention that CRM_ORDER_READ would:

    Unfortunately, the report does not give you a connection between an RfC (ZMCR) and its own Change Objects (ZMMJs), or between either of them and their date field values

    You get the relationship between BT in ET_DOC_FLOW and date field values are  in ET_APPOINTMENT.

    Nevertheless the diagram is good starting point to explain the underlying data model. For a more complete (and maybe for the beginner more confusing) diagram of the CRM datamodel take a look at Nicolas Busson wiki entry: SAP CRM datamodel - CRM - SCN Wiki

    Best Regards


    • Many thanks Hendrik indeed.

      Your point about ET_APPOINTMENT is very interesting, and I will use that idea to change the diagram in the coming weeks to include that, if you do not mind.  That change will be beneficial for the ones working with ChaRM, as well.

      Nicolas' diagram is excellent.  Your contribution confirms the beauty of SCN:  We all get connected to the pieces of data we are missing here and there.

      Have a nice day,