SAP table TCY33 (Time profile for capacity leveling)
SAP table TCY33 has 2 primary key fields being MANDT,TIPRO_ID.
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 | |||
TIPRO_ID | Time profile for capacity leveling/extended evaluation | CHAR | 10 | 0 | CY_TIPRO | ||||
ANATIMT | Type of entry | CHAR | 1 | 0 | CY_ANATIMT | ||||
ANADATF | Start date for an evaluation | CHAR | 10 | 0 | CY_ANADATF | ||||
ANADATT | End date for an evaluation | CHAR | 10 | 0 | CY_ANADATT | ||||
PLATIMT | Type of entry planning period | CHAR | 1 | 0 | CY_PLATIMT | ||||
PLADATF | Start date for planning period | CHAR | 10 | 0 | CY_PLADATF | ||||
PLADATT | Finish date for planning period | CHAR | 10 | 0 | CY_PLADATT | ||||
RDATE_TYPE | Type of date specification | CHAR | 1 | 0 | CY_RDATETY | ||||
RDATE | Date of backlog dispatching | CHAR | 10 | 0 | CY_RDATE | ||||
DBRTIMT | Type of entry database read period | CHAR | 1 | 0 | CY_DBRTIMT | ||||
DBRDATF | Start date of database selection | CHAR | 10 | 0 | CY_DBRDATF | ||||
DBRDATT | End date for database selection | CHAR | 10 | 0 | CY_DBRDATT | ||||
PROFAPP | Identifier for an application | NUMC | 2 | 0 | CY_PROFAPP |
|