SAP table REBR1 (Batch Record: Layout Profile)
SAP table REBR1 has 2 primary key fields being MANDT,LAYOUT.
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 | |
| LAYOUT | Document profile for batch records | NUMC | 8 | 0 | LYTPROF | ||
| FLG_CONTE | Batch record: generate table of contents | CHAR | 1 | 0 | FLG_CONTE | ||
| FLG_HIST | Batch record: generate "version data" document | CHAR | 1 | 0 | FLG_HIST | ||
| FLG_DEVIA | Batch record: generate "deviations" document | CHAR | 1 | 0 | FLG_DEVIA | ||
| FLG_ORDER | Batch record: generate "process order" document | CHAR | 1 | 0 | FLG_ORDER | ||
| FLG_MATLI | Batch record: generate "material list" document | CHAR | 1 | 0 | FLG_MATLI | ||
| FLG_PRLOS | Batch record: generate "inspection lot" document | CHAR | 1 | 0 | FLG_PRLOS | ||
| FLG_SHEET | Batch record: generate "PI sheet" document | CHAR | 1 | 0 | FLG_SHEET | ||
| FLG_MESSA | Batch record: generate "process messages" document | CHAR | 1 | 0 | FLG_MESSA | ||
| FLG_USER | Batch record: generate "user-defind data" document | CHAR | 1 | 0 | FLG_USER |