SAP Table EDSC (Disc.Header Data)
SAP table EDSC has 2 primary key fields being MANDT,RABZUS.
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 | |||||||||
RABZUS | Discount key | CHAR | 10 | 0 | RABZUS | ||||||||||
SPARTE | Division | CHAR | 2 | 0 | TSPA | SPARTE | |||||||||
RABTYP | Discount category | CHAR | 1 | 0 | RABTYP |
|
|||||||||
BZGBASIS | Discount Reference Base | CHAR | 1 | 0 | BZGBASIS |
|
|||||||||
USE_REGIST | Permissibility for registers | CHAR | 1 | 0 | USE_REGIST |
|
|||||||||
RABART | Discount type | CHAR | 1 | 0 | RABART |
|
|||||||||
MASS | Unit of Measurement | UNIT | 3 | 0 | T006 | E_MASS | |||||||||
TIMBASIS | Time Basis | CHAR | 3 | 0 | TIMBASIS | ||||||||||
TIMTYP | Time category (days or months) | CHAR | 1 | 0 | TIMTYP |
|
|||||||||
AKLASSE | Billing Class | CHAR | 4 | 0 | AKLASSE | ||||||||||
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 | ||||||||||
BEGRU | Authorization Group | CHAR | 4 | 0 | BEGRU | ||||||||||
LOEVM | Deletion Indicator | CHAR | 1 | 0 | LOEVM |
EDSC foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 EDSC | MANDT | T000 | Clients | MANDT |
1 EDSC | MASS | T006 | Units of Measurement | MSEHI |
0 EDSC | SPARTE | TSPA | Organizational Unit: Sales Divisions | MANDT |
0 EDSC | SPARTE | TSPA | Organizational Unit: Sales Divisions | SPART |