Show TOC

Using Temporal JoinsLocate this document in the navigation structure

You can use temporal joins in a CompositeProvider to depict time flows.


The following restrictions apply:
  • Only InfoObjects, DataStore objects (advanced and classic) and InfoCubes are supported.
  • No union nodes are allowed in temporal joins.
  • The CompositeProvider cannot contain any fields that are not assigned.


In BW, only master data can be defined as a time-dependent data source. Two additional fields/attributes 0DATEFROM and 0DATETO are added to the characteristic.

DataStore objects and InfoCubes themselves cannot be defined as time-dependent however. However, they often contain time characteristics (from which a time interval can be derived), or a minimum of two InfoObjects that refer to 0DATE (which you can use to define a time interval for). This allows the corresponding InfoProvider in the CompositeProvider to be considered as time-dependent.

As soon as an InfoProvider that is contained in the CompositeProvider is made pseudo time-dependent, it is handled as a time-dependent data source. An important difference between pseudo time-dependent InfoProviders and time-dependent InfoProviders like InfoObjects, the system cannot prevent gaps or overlaps from occurring in the time stream. This always depends on the dataset of the pseudo time-dependent InfoProvider.


Time-Dependent Characteristics

  1. As soon as you use a time-dependent characteristic in the join, the join becomes time-dependent. You can also deactivate time dependency via Hide Time-Dependent Fields, provided that the characteristic does not exclusively consist of time dependent attributes. The time-dependent fields and the Valid From and Valid To fields are then hidden.

Time-Dependent InfoProviders

  1. In the context menu of your InfoProvider, choose Define Time Dependency.
    You have the following options:
    • Select a time characteristic, which is contained in the InfoProvider to be processed as time-dependent and which can be used for time derivation (0CALMONTH, 0CALQUARTER, 0CALWEEK, 0CALYEAR, 0FISCPER, 0FISCYEAR). Time-dependency is indicated by the addition of the two date attributes 0DATEFROM and 0DATETO to the InfoProvider in the CompositeProvider (below the selected time characteristic).
      Example If 0CALYEAR is derived with the value 2014, the start date has the value 01.01.2004 and the end date has the value 31.12.2004
    • Select a characteristic of type Date as the start date (Valid From) and another characteristic of type Date as the end date (Valid To). Make sure here that the dataset is suitable. The value of the attribute that is interpreted as the start date must be smaller than, or equal to, the value of the attribute that is interpreted as the end date. If this is not the case, the data record is interpreted as invalid, and the request will not be taken into account. Characteristics of type Date must have 0DATE as a reference.
  2. You can also define a key date. To do this, choose Set Key Date in the context menu of your InfoProvider.
    Depending on the type of characteristic, there are various ways of defining a key date: Characteristics of type Date with a reference to 0DATE and the time characteristic 0CALDAY can be flagged as key dates. A key date derivation can be defined for time characteristics that describe an interval (0CALWEEK, 0CALMONTH, 0CALQUARTER, 0CALYEAR, 0FISCPER, 0FISCYEAR). You have multiple options:
    • Use the first day as the key date
    • Use the last day as the key date
    • Use a fixed day as key date (i.e. a particular day from the specified time period)
    • Key Date Derivation Type: You can specify a key date derivation type.
    An artificial characteristic CALDAY, which symbolizes the derived key date, is added to the InfoProvider, which a key date derivation is defined for.