Hierarchy
FCCO (Software Component) Financial Closing Cockpit 200⤷
CA-GTF-FCC (Application Component) Financial Closing cockpit Add-on⤷
FCC_CLOSING (Package) Financial Closing Cockpit - SAPGUI and backend
Basic Data
| Data Element | FCC_DEF_TIME_ZONE |
| Short Description | Time Zone for Definition |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TZNZONE | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table | TTZZ |
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 | Time Zone |
| Medium | 20 | Def. Time Zone |
| Long | 25 | Time Zone for Definition |
| Heading | 25 | Time Zone for Definition |
Documentation
Definition
Specifies the time zone on which the offset days and the planned start time of the task are based.
Use
In SAP Financial Closing cockpit 1.0, when you define the offset days and the planned start time of a task, you specify the time zone on which the offset days and the planned start time are based using the Select Time Zone pushbutton (Ctrl+Shift+F11) in the home screen of the Financial Closing cockpit application. The Financial Closing cockpit application displays the time zone you have selected in the Time Zone field. If you change the time zone after you have defined the offset days and the planned start time, the offset days and the planned start time are adjusted accordingly when you edit the task again.
However, when the Financial Closing cockpit application saves the offset days and the planned start time, it always uses the system time zone. Unless the time zone you have specified is the system time zone, the application always converts the offset days and the planned start time to their equivalent values in the system time zone and then saves them. This causes inconsistencies in time calculation because of the observation of daylight saving time (DST), also known as summer time. See the Example section for details.
To solve this problem, SAP Financial Closing cockpit 2.0 saves the offset days and the planned start time in the time zone you have specified. This does not disrupt your existing data if you have upgraded from the 1.0 release to the 2.0 release. In the 2.0 application, when you open a task group, template, or task list that already exists in the 1.0 release for the first time, the Financial Closing cockpit application calculates and displays the corresponding offset days and the planned start time in the time zone you have specified using the Select Time Zone pushbutton. If necessary, you can change the offset days, the planned start time, and the time zone. In the 2.0 release, you specify the time zone on which the offset days and the planned start time of the task are based in this new Time Zone for Definition field, which is always editable. The offset days, the planned start time, and the time zone are left as they are when you save them and no conversion to the system time zone is made. When you open the task again, this field displays the time zone that has been saved rather than the time zone you have specified using the Select Time Zone pushbutton.
Dependencies
The non-editable fields beneath this one are for displaying the offset days and the planned start time of the task in the time zone you specify using the Select Time Zone pushbutton. The non-editable field Time Zone is inherited from the 1.0 release and behaves in the same way. These non-editable fields serve as a reference and are helpful when, for example, you define the offset days and the planned start time of a task in a foreign time zone while you want to display the corresponding offset days and planned start time in your local time zone.
Example
SAP Financial Closing cockpit 1.0 saves the offset days and the planned start time of a task in the system time zone. This causes inconsistencies in time calculation because of the observation of DST. In this example, we define a task in the UTC+8 time zone where DST is not observed while the system time zone is CET where DST is observed. The following table shows what happens when the Financial Closing cockpit 1.0 application saves data at a time of the year when DST has not yet started in DST-observing time zones:
Time Entered Time Saved
1 16:00:00 UTC+8 1 09:00:00 CET
The following table shows the time displayed for edit by the Financial Closing cockpit 1.0 application when you open the task again:
DST in DST-Observing Time Zones Time Displayed for Edit
Still not started 1 16:00:00 UTC+8
Started 1 15:00:00 UTC+8
As the above tables show, because the basis for time calculation is the system time zone, the time displayed for edit in the UTC+8 time zone becomes inconsistent even if the UTC+8 time zone does not observe DST.
SAP Financial Closing cockpit 2.0 saves the offset days and the planned start time of a task in the time zone you specify. The following table shows what happens when the Financial Closing cockpit 2.0 application saves data at a time of the year when DST has not yet started in DST-observing time zones:
Time Entered Time Saved
1 16:00:00 UTC+8 1 16:00:00 UTC+8
The following table shows the time displayed for edit by the Financial Closing cockpit 2.0 application when you open the task again:
DST in DST-Observing Time Zones Time Displayed for Edit
Still not started 1 16:00:00 UTC+8
Started 1 16:00:00 UTC+8
As the above tables show, because the basis for time calculation is the time zone that you have specified, the time displayed for edit in the UTC+8 time zone is always consistent regardless of whether DST has started in DST-observing time zones.
History
| Last changed by/on | SAP | 20141107 |
| SAP Release Created in | 200 |
