SAP table ESCH (Billing Schema (Header Data))
SAP table ESCH has 2 primary key fields being MANDT,SCHEMANR.
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 | |
| SCHEMANR | Number of the billing schema | CHAR | 10 | 0 | SCHEMANR | ||
| SPARTE | Division | CHAR | 2 | 0 | TSPA | SPARTE | |
| AKLASSE | Billing Class | CHAR | 4 | 0 | AKLASSE | ||
| ABRSPERRDT | Date on which schema was blocked for billing | DATS | 8 | 0 | ABRSPERRDT | ||
| PEBRATE | Period-end billing rate | CHAR | 10 | 0 | PEBRATE | ||
| BB_SCHEMA | Indicator: schema with backbilling steps | CHAR | 1 | 0 | BB_SCHEMA | ||
| DYNPERSCHEMA | Billing schema with dynamic period control | CHAR | 1 | 0 | DYNPERSCHEMA | ||
| CONDBILLPROG | Execute Conditional Billing Program | CHAR | 1 | 0 | E_CONDBILLPROG | ||
| 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 |
ESCH foreign key relationships
| Table | Field | Check Table | Check Field | |
|---|---|---|---|---|
| 0 ESCH | MANDT | T000 | Clients | MANDT |
| 1 ESCH | SPARTE | TSPA | Organizational Unit: Sales Divisions | MANDT |
| 1 ESCH | SPARTE | TSPA | Organizational Unit: Sales Divisions | SPART |