SAP table COMH (PP-PI: Header Data for Process Messages)
SAP table COMH has 2 primary key fields being MANDT,MSID.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
| Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
|---|---|---|---|---|---|---|---|
| MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |
| MSID | Number of the Process Message | NUMC | 18 | 0 | CO_MSID | ||
| WERK | Plant | CHAR | 4 | 0 | T001W | WERKS_D | |
| MSCLA | Process Message Category | CHAR | 8 | 0 | TC50 | CO_MELDG | |
| TSTKZ | Indicator: Message or Control Recipe for Test Purposes | CHAR | 1 | 0 | TSTKZ | ||
| SEDAT | Date on which the record was created | DATS | 8 | 0 | ERDAT | ||
| SEUZT | Time when the record was created | TIMS | 6 | 0 | ANUZT | ||
| SOURCE | Sender of the process message | CHAR | 32 | 0 | CO_SOURCE | ||
| ERRKZ | Processing Status of the Process Message/the Control Recipe | CHAR | 1 | 0 | CO_ERRKZ | ||
| ARFCIPID | Host ID (IP ID | CHAR | 8 | 0 | ARFCIPID | ||
| ARFCPID | Process ID | CHAR | 4 | 0 | ARFCPID | ||
| ARFCTIME | Time Stamp | CHAR | 8 | 0 | ARFCTIME | ||
| ARFCTIDCNT | Transaction ID (LUW -> COMMIT WORK) | CHAR | 4 | 0 | ARFCTIDCNT | ||
| SNDALL | Indicator: Send message to all destinations or not at all | CHAR | 1 | 0 | CO_SNDALL | ||
| AUFNR | Order Number | CHAR | 12 | 0 | * | AUFNR |
COMH foreign key relationships
| Table | Field | Check Table | Check Field | |
|---|---|---|---|---|
| 0 COMH | MANDT | T000 | Clients | MANDT |
| 1 COMH | MSCLA | TC50 | PP-PI: Proc.Message Categories/ Proc.Instruction Categories | MANDT |
| 1 COMH | MSCLA | TC50 | PP-PI: Proc.Message Categories/ Proc.Instruction Categories | WERKS |
| 0 COMH | WERK | T001W | Plants/Branches | WERKS |