Define Time-Based Fields for Cost Centers

In this step you determine on the client level, independently of organizational units such as controlling area or chart of accounts, whether master data table fields are historically relevant or not.

You can maintain master data for cost centers, cost elements, activity types, and business processes as time-based . Changes to any other time interval aree possible at any given time. Data storage is also time-based. In this way, you can store multiple database records for a master data record, each holding different information.

The time-based dependencies are determined by SAP and cannot be changed.The following dependencies are possible:

• Not time-based

• Day-based

• Period-based

• (Fiscal) Year-based

In the "Time Dependency" column, you have an overview of the time-based dependencies for individual master data fields as set by SAP.

For day-based fields, you can set an indicator determining whether fields are historically relevant or not. Period-based and year-based fields are always historically relevant.

If you change fields during master data maintenance which were marked as historically relevant, and redefine a new analysis period, the SAP R/3 System creates new database records, for the new analysis period and for any following periods, and simultaneously restricts the validityperiod of the existing database records.

Example: Day-Based, Historically Relevant Fields

If you change fields during master data maintenance not marked as historically relevant, but without a new analysis period, the entire database record changes for the entire analysis period. These changes appear in the change log.

If you change day-based fields not marked as historically relevant, the existing database record also changes for the entire selected analysis period. Definition of a new period is not possible. These changes appear in the change log.

Example: Day-Based, Not Historically Relevant Fields

Fields without time-based dependencies may be changed at any time, with the change applying to the entire validity period of the master data.

Note

• Remember that time-based storage consumes large amounts of data storage space. Designate only important fields for time-based dependencies.

• If consecutive fields have identical historically relevant definitions, the SAP R/3 System replaces the database records with a single record valid for the existence of the individual records.

Further Notes

Actions

Notes for Transport

If, in your client, you have not selected the automatic recording of changes for client-specific objects (in Customizing under Basis Components -> System Administration -> Change and Transport System -> Configure Clients ), you can transport your settings to the target system in a user-defined activity.
To do this, in Customizing, choose Controlling -> General Controlling -> Production Start-Up Preparation -> Transport System Settings and then process the relevant activity.