As discussed in Time and Technical Characteristics, a master data read class is assigned to such a special InfoObject which handles the master data retrieval. The values for display attributes are derived(by this class) from the period of the data record, navigation attributes are read with the help of the master data tables P and X.
The time characteristic 0FISCPER uses the class is CL_RSMD_RS_0FISCPER(see note 1387166). The definition depends on the content release. E.G. on BW/4Hana systems, 0FISCPER is shipped with some navigation attributes in contrast to BW75 systems where all attributes are display attributes(and hence the P and X tables are empty/do not exist). The characteristics 0FISCPER depends on the fiscal variant(0FISCVARNT) and is maintained with transaction OB29. See example below.
As explained in notes 2194279 and 2074801, it is important to use the current content version of this characteristic. It is not recommended to change the delivered version of the object, however, it is possible to create your own hierarchies and change display attributes to navigations attributes. See examples below.
The display of the text for periods of the characteristic 0FISCPER depends on the following customizing settings for the fiscal year variant:
- Transaction OB29
- Setting "Calendar Year" set: the text always contains the calendar year which is added automatically. The short and medium text can be maintained under 'Period Texts'
- Setting "Year Dependent" set: the system always displays the text exactly as maintained in transaction OB29 in the section "Period Texts"
- Transaction RSRHIERARCHYVIRT: in case neither of the settings from above are used, this transaction offers the possibility to specify "Calendar Year" or "Year Dependent"
For time characteristics like 0FISCPER so called Virtual Time Hierarchies can be used in order to get a hierarchical display of the periods in query results. See Virtual Time Hierarchies for further details. It is also possible to create manually hierarchies with transaction RSD1/RSH1 and BW Modeling Tools.
Transaction RSRHIERARCHYVIRT can be used to define a time interval which is the basis for the F4 help of time characteristics. In case of inconsistencies, this transaction also offers an option to refill the corresponding master data tables(more precisely, the SID, P, and X tables) for the characteristics 0DATE, 0CALMONTH, 0QUARTER and 0FISCPER(since the new content versions of these objects contain navigation attributes). So, when this function is used, all attribute values of the P and X table are refilled for all periods of the SID table.
2608688 New Rebuild Option for Time Characteristics Master Data
In case the (content) version of 0FISCPER does not contain any navigation attributes(P and X tables do not exist), this rebuild option does not have any effect.
There is a check called "Consistency of SID and X table for relevant Time Characteristics" in RSRV you can use to check whether the records in the SID, P and X tables are consistent. In case of inconsistencies the button 'Correct Error' can be used to refill these tables(similar to the corresponding function of RSRHIERARCHYVIRT). See also example below.
- 1136142 Key figure attributes 0NUMDAY and 0NUMWDAY
- 635571 "No SID found for value '&' of characteristic 0FISCPER"
- 2241237 - Texts of characteristic 0FISCPER are not displayed correctly (see also note 2349598)
- The note describes customizing settings in OB29, RSRHIERARCHYVIRT etc.
- 2608688 New Rebuild Option for Time Characteristics Master Data
BW75 Systems: Content Version
Since there are only display attributes, the P and X tables are not needed. Hence the P table only contains the initial value(and the X table does not exist at all):
BW/4Hana Systems: Content Version
BW/4Hana Example: New Periods and New SIDs/Masterdata Records
The fiscal variants and periods are defined with transaction OB29. Baically, there are two types of variants, 'Year-Dependent' and 'Calender Year' variants. One often used Calender Year variant is K4(Cal. Year, 4 Special Periods) which we also used in our checks. In Addition we created a Year-Depenent variant which we called Z9.
When the system is new, all the master data tables(/BI0/SFISCPER, /BI0/PFISCPER, /BI0/XFISCPER) of 0FISCPER are empty.
Variant K4(Calender Year)
When data is loaded into a Provider, SIDs are genrerated for 0FISCPER. Although only one period(011.2016) was loaded, SIDs were generated for all periods of 2016:
After saving this definition of the periods of the year 2016 the following data records are stored in table T009B
When now want to load data into an ADSO for the year 2016, we get error Messages like:
SID error for record: InfoObject 0FISCPER and value Z92016008
As discussed in note 635571, if the fiscal year variant is year-specific, the variant must also be defined for the previous calendar year. Hence we add the period Definition for the year 2015:
The data load is now successful. When we check the generated SIDs, we notice that, although only one period was loaded, SIDs were generated for all periods of 2016:
In Addition the following records are generated:
BW75 Eaxmple: Activating navigation Attributes
As explained above, the content version of 0fiscper does not contain any navigation attributes. If required, it is possible to set the corresponding flag and activate the characteristic again. Then the X table is created and both, the X and P table is filled with data.
0FISCPER contains SIDs for the year 2018 and the variant K4.
The X table does not exists and the P table is empty(since 0fiscper does not contain any navigation attributes in the content version)
We take a closer look at the following display attributes:
Now we activate two naviagtion attributes
After activation the P and X tables are filled as follows:
The navigation attributes can then be used in queries:
BW/4Hana Example: Fiscal PeriodTexts
We check the display of texts to periods where the variant is K4, so, a variant with the Setting "Calendar Year". As discussed above, in this case it is possible to maintain(change the default) of the Texts. However, text always contains the calendar year which is added automatically.
In our example we changed the short text of period 2 from FEB to FB and the medium text from "February" to "February Test"
In a corresponding query, the short text is displayed as follows:
When change the display to medium text we get:
BW75 Example: RSRV Check
In our case one record(period 000.2018) is missing in the X table of 0fiscper:
When we run the check, the following error is displayed:
After using the repair function 'Correct Error', the X table is correct again: