SAP table EMDUSDRQHEAD (Table of MDUS Request Data)
SAP table EMDUSDRQHEAD has 2 primary key fields being MANDT,MDUSREQUESTID.
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 | MANDT | ||||||||||||||||||
MDUSREQUESTID | MDUS Request ID | CHAR | 22 | 0 | E_MDUSREQUESTID | ||||||||||||||||||
PROCESS | Creation Process for MDUS Request | NUMC | 2 | 0 | E_MDUSRQPROCESS |
|
|||||||||||||||||
STATUS | Status of MDUS Request | NUMC | 2 | 0 | E_MDUSRQSTATUS |
|
|||||||||||||||||
PRIORITY | Priority of MDUS Request | NUMC | 1 | 0 | E_MDUSREQUESTPRIO | ||||||||||||||||||
TIMEZONE | Time Zone | CHAR | 6 | 0 | * | TIMEZONE | |||||||||||||||||
ANLAGE | Installation | CHAR | 10 | 0 | ANLAGE | ||||||||||||||||||
ABRDATS | Scheduled Billing Date | DATS | 8 | 0 | ABRDATS | ||||||||||||||||||
ABRVORG | Billing Transaction | CHAR | 2 | 0 | ABRVORG |
|
|||||||||||||||||
MDUS | Meter Data Unification & Synchronization | CHAR | 10 | 0 | TEAMI_MDUS | E_AMI_MDUS | |||||||||||||||||
ERDAT | Date on which the record was created | DATS | 8 | 0 | ERDAT | ||||||||||||||||||
ERNAM | Name of Person Responsible for Creating the Object | CHAR | 12 | 0 | ERNAM | ||||||||||||||||||
AEDAT | Last Changed On | DATS | 8 | 0 | AEDAT | ||||||||||||||||||
AENAM | Name of Person Who Changed Object | CHAR | 12 | 0 | AENAM |
EMDUSDRQHEAD foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 EMDUSDRQHEAD | MDUS | TEAMI_MDUS | Meter Data Unification & Synchronization | MANDT |
0 EMDUSDRQHEAD | MDUS | TEAMI_MDUS | Meter Data Unification & Synchronization | MDUS |