(Glue-2408) Q: When importing fields from table MATDOC from SAP S/4HANA into SNP Glue™ table, not all key fields from the SAP table seem to be imported into SNP Glue™ data dictionary. Why not?

Owned by SNP
Aug 20, 2024
1 min read

Table MATDOC replaces some old SAP ERP tables (I.e. table MSEG). SAP replaced table MSEG for the simplified logistics module.

The way SAP designed the table is to include most fields from MSEG (among other R/3 database tables) in a central location. In order to do this, SAP has changed the overall design of the table. As part of this, SAP changed the key of the table. This key now does not include the document number of material documents directly, as the table MSEG used to. Instead, several fields of data type RAW are being used in MATDOC. When importing fields into SNP Glue™ tables from the SAP ABAP DDIC, fields of types that are not supported on most other databases and/or Hadoop are being skipped. This is mostly the case for fields of type "RAW".

When using MATDOC as the basis for replication to an external database, we recommend the following steps:

  1. Create SNP Glue™ table
  2. Import fields from table MATDOC
  3. Flag the fields MBLNR, MJAHR, ZEILE, and LINE_ID as key fields
  4. Activate the table

Note: key fields don't exist on all of the SQL processing engines, but marking them as a key helps data scientists better interpret the data, as well as be ready conceptually for future Hadoop technologies or other relational databases.