SAP table ELPASS (Allocation of Load Profiles to any BOR Objects)
SAP table ELPASS has 5 primary key fields being MANDT,OBJKEY,OBJTYPE,LOGLPRELNO,BIS.
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 | ||
OBJKEY | Object key | CHAR | 70 | 0 | SWO_TYPEID | ||
OBJTYPE | Reference obj. type | CHAR | 10 | 0 | SWO_REFOBJ | ||
LOGLPRELNO | Logical Number of Profile Allocation | NUMC | 18 | 0 | LOGLPRELNO | ||
BIS | Date at Which a Time Slice Expires | DATS | 8 | 0 | BISZEITSCH | ||
AB | Date from which time slice is valid | DATS | 8 | 0 | ABZEITSCH | ||
LOADPROF | Load profile | CHAR | 18 | 0 | ELPROF | LOADPROFILE | |
PROFILE | Number of EDM Profile | NUMC | 18 | 0 | EPROFHEAD | E_PROFILE | |
PROFROLE | Profile allocation role | CHAR | 4 | 0 | EPROFASSROLE | PROFROLE | |
ARCH_AB | From Date of Last Archiving | DATS | 8 | 0 | E_ELPASS_DATEFROM_ARCH | ||
ARCH_BIS | To-Date of Last Archiving | DATS | 8 | 0 | E_ELPASS_DATETO_ARCH | ||
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 |
ELPASS foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 ELPASS | LOADPROF | ELPROF | Load Profile Header Data | MANDT |
1 ELPASS | PROFILE | EPROFHEAD | Profile Header Data | MANDT |
1 ELPASS | PROFILE | EPROFHEAD | Profile Header Data | PROFILE |
0 ELPASS | PROFROLE | EPROFASSROLE | Roles for Profile Allocation | MANDT |