SAP ABAP Data Element TEM_PLAN_YEAR_VARIANT (Planning Year Variant)
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷ FTEM_EXPOSURE_MGT_PER (Package) Treasury: Exposure Management - Persistency Layer
⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷ FTEM_EXPOSURE_MGT_PER (Package) Treasury: Exposure Management - Persistency Layer
Basic Data
Data Element | TEM_PLAN_YEAR_VARIANT |
Short Description | Planning Year Variant |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PERIV | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | T009 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | PlnVariant |
Medium | 15 | Planning Year |
Long | 20 | Plng Year Variant |
Heading | 2 | PV |
Documentation
Definition
The planning year variant splits the year into periods. You can split exposures for planning and analysis into periods other than the fiscal year variant of your company code.
Use
Exposure analysis is based on periods. Exposures that have corresponding relevant attributes and periods are dealt with together, regardless of the exposure date.
Dependencies
The planning year variant is technically a fiscal year variant. Therefore, when you define periods for exposure analysis, you can use all the options that you are familiar with from the fiscal year variants. It is not necessary to use the variants that you use in exposure management as fiscal year variants in a company code.
Example
History
Last changed by/on | SAP | 20060208 |
SAP Release Created in | 600 |