SAP table TCY35 (Period profile for capacity leveling)
SAP table TCY35 has 2 primary key fields being MANDT,PEPRO_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
Client
CLNT
3
0
T000
MANDT
Period profile for capacity leveling/extended evaluation
CHAR
10
0
CY_PEPRO
PEINHEIT
Unit in which the period duration is specified (day, week..)
CHAR
1
0
DAPER
Possible values
A
Day
B
Factory calendar day
C
Week
D
Month
E
Posting period
F
Calendar year
G
Fiscal year
H
Shift
I
Planning Calendar
PDAUER
Duration of a period (units as specified in period type)
DEC
3
0
DAPED
ZEITRASTER
Period pattern key for available capacity
CHAR
10
0
TC35
CR_ZRAST
KUMUL
Indicator, whether cumulated display is desired
CHAR
1
0
KUMULD
DYNP_WIDTH
Indicator, width of the screen
CHAR
1
0
CY_DYNPWID
AVAIL_CAP
Formula to calculate the rem.avail.cap.
NUMC
1
0
CY_AVAICAP
Possible values
1
Remaining available cap. = available cap. - dispatched rqmts
2
Remaining av. cap. = Av. cap. - dispatched rqmts - pool
SCHED_TIM
Dispatch time used in rescheduling
TIMS
6
0
CY_SCHETIM
REQ_VIEW
Reqmts to be displayed on cap.planning table (table form)
NUMC
1
0
CY_REQVIEW
Possible values
1
Dispatched requirements
2
Requirements not yet dispatched
3
All requirements
MRP_CAL
PPC Planning Calendar
CHAR
3
0
T439G
MRPPP
PPSWERK
Plant
CHAR
4
0
T001W
WERKS_D
TCY35 foreign key relationships
Table
Field
Check Table
Check Field
0 TCY35
MRP_CAL
T439G PP Planning periods: header table
MANDT
0 TCY35
MRP_CAL
T439G PP Planning periods: header table
WERKS
1 TCY35
PPSWERK
T001W Plants/Branches
MANDT
1 TCY35
PPSWERK
T001W Plants/Branches
WERKS
0 TCY35
ZEITRASTER
TC35 Period pattern key
MANDT
0 TCY35
ZEITRASTER
TC35 Period pattern key
ZRAST