SAP table T459C (Default values for independent requirements)
SAP table T459C has 2 primary key fields being MANDT,BEDAR.
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 | |||||||||||
BEDAR | Requirements class | CHAR | 3 | 0 | T459K | BEDAR | |||||||||||
VERVP | Consumption indicator for planning requirements | CHAR | 1 | 0 | VERVP |
|
|||||||||||
HISKZ | Indicator: Process plan with or without history | CHAR | 1 | 0 | HISKZ | ||||||||||||
VERSB | Version Number for Independent Requirements | CHAR | 2 | 0 | T459V | VERSB | |||||||||||
VERVS | Indicator: Version Active | CHAR | 1 | 0 | VERVS |
|
|||||||||||
VERBI | Version number for indep. requirements in batch run | CHAR | 2 | 0 | T459V | VERBI | |||||||||||
APROG | Reference type | CHAR | 1 | 0 | T459R | APROG | |||||||||||
INNUM | Internal number assignment for requirements plan number | CHAR | 1 | 0 | INNUM |
|
|||||||||||
HIABB | Indicator: History for Plnd Ind. Rqmt, also During Reduction | CHAR | 1 | 0 | HISKZ_ABBAU |
T459C foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 T459C | APROG | T459R | Reference requirements table | MANDT |
0 T459C | APROG | T459R | Reference requirements table | APROG |
1 T459C | BEDAR | T459K | Control table for customer requirements | MANDT |
0 T459C | VERBI | T459V | Version table | MANDT |
0 T459C | VERBI | T459V | Version table | SPRAS |
0 T459C | VERBI | T459V | Version table | VERSB |
1 T459C | VERSB | T459V | Version table | MANDT |
1 T459C | VERSB | T459V | Version table | SPRAS |
1 T459C | VERSB | T459V | Version table | VERSB |