SAP table TPOST (Portfolio Determination: Control Table)
SAP table TPOST has 3 primary key fields being MANDT,KAPPL,POFOST.
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 | |||||||||||||||||
KAPPL | Application | CHAR | 2 | 0 | T681A | KAPPL | |||||||||||||||||
POFOST | Portfolio: Control Type for Portfolio Determination | CHAR | 4 | 0 | WB2_CONTR_GROUP | ||||||||||||||||||
KALSM | Procedure (Pricing, Output Control, Acct. Det., Costing,...) | CHAR | 6 | 0 | T683 | KALSM_D | |||||||||||||||||
PRDVO | Portfolio Determination: Date for Portfolio Determination | CHAR | 1 | 0 | PRDVO_POFO |
|
|||||||||||||||||
POFOZ | Portfolio: Time of Automatic Portfolio Determination | CHAR | 2 | 0 | POFOZ |
|
|||||||||||||||||
POFST | Portfolio Determination: Determination Strategy | CHAR | 1 | 0 | POFST |
|
|||||||||||||||||
POEXL | Portfolio: Exclusive Access per Portfolio Type | CHAR | 1 | 0 | POEXL | ||||||||||||||||||
POFOB | Portfolio Required for Follow-On Document Generation | CHAR | 1 | 0 | WB2_POFOB |
|
|||||||||||||||||
POCOM | Update Commodity Data | CHAR | 1 | 0 | WB2_POCOM |
|
|||||||||||||||||
POLOG | Application log for Portfolio Management | CHAR | 1 | 0 | WB2_PORTFOLIO_LOG |
|
TPOST foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 TPOST | KALSM | T683 | Pricing procedures | KAPPL |
0 TPOST | KALSM | T683 | Pricing procedures | KALSM |
1 TPOST | KAPPL | T681A | Conditions: Applications | KAPPL |