SAP ABAP Data Element RSFSCVTSRC (Source from which the fiscal year variant is used)
Hierarchy
☛ SAP_BW (Software Component) SAP Business Warehouse
   ⤷ BW-WHM-DST (Application Component) Data Staging
     ⤷ RSAU_RSAA (Package) Routine
Basic Data
Data Element RSFSCVTSRC
Short Description Source from which the fiscal year variant is used  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type TEXT20    
Data Type CHAR   Character String 
Length 20    
Decimal Places 0    
Output Length 20    
Value Table      
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 Source 
Medium 20 Source of FYV 
Long 40 Source of fiscal year variant 
Heading 35 Source of Fiscal Year Variant 
Documentation

Definition

The connection between the calendar year and the fiscal year is created through the fiscal year variant (FYV). The FYV determines how many periods and special periods a fiscal year is made up of, and how the system calculates the booking periods that belong to it.

The FYV is also needed in the Business Information Warehouse for various system-wide currency translations and for converting a time-InfoObject in update.

The FYV can have the folllowing sources:

  • InfoCube:

    In the InfoCube the FYV is defined as a constant value. This is the variant with the strongest effesct.

    When you define the FYV in the InfoCube, this constant is always used for updates, translations and conversions.

  • InfoObject:

    If a FYV is specified as a constant value in an InfoObject, this value is then valid system-wide.

    In the InfoCube it only serves as a proposed value and can be overwritten.

    This variant has the second strongest effect in the update.

  • Communications Structure:

    The FYV is transferred from the communications structure, that means, it is only made known to the update during the runtime of the data transfer. Should the FYV value not be known to the Business Information Warehouse, the update is canceled with an appropriate error message.

    If the FYV value changes during an update or during subsequent transfers pre-existing data records are preserved.

The confirmed FYV value from the InfoCube or InfoObject is read during the update runtime. If the value has been changed, new data records will be created.

If the value has been deleted, the update rules are canceled with an appropriate error message.

History
Last changed by/on SAP  20130604 
SAP Release Created in