_________________________________
_________________________________
© SAP AG 2007 / 0
What Time Is It Where
You Are? Best Practices
for Managing Global SAP
Systems Running on
Different Time Zones
Alexander Davidenkoff
SAP AG
Motivation and overview of time zones
User-related time zone approach
Object-related time zone approach
Customized time zone developments
Wrap-up
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
 Date and Time – Depends Where You Are on the Globe
UTC _________________________________
What time and date is it?
31 Oct 2007, 23:37:54
_________________________________
Which day is today? _________________________________
It is Oct 31 (UK) It is Nov 1 (DE) It is 07h 37m 54s
It is Oct 31 _________________________________

Which year?
_________________________________
So, it is 00h 37m 54s
It is 05h 07m 54s
2007 _________________________________
Which day is
today? _________________________________
DST applies! Which day is today? It is Nov 1
_________________________________
So, it is 15h 37m 54s It is Oct 31
DST applies
It is 09 h 37m 54s _________________________________
DST applies _________________________________
So, it is 18h 37m 54s
UTC = Universal Time Coordinated
DST = Daylight Saving Time
© SAP AG 2007 / 3

Requirements for an IT Solution Serving a Global Company

_________________________________
The solution must support global business practices
„ Global reporting, consolidation _________________________________
„ Global process definition
_________________________________
The solution must allow for local requirements
„ Tax calculation, accounting rules, financial reporting standards _________________________________
„ Payroll (taking into account local tax and social insurance)
_________________________________
The solution must be usable across regions
„ Local calendars and time zones must be handled _________________________________
„ Use of multiple currencies

The data must be usable around the world

_________________________________
„ Text descriptions of data must be language dependent
_________________________________
„ Translation process must be supported
„ All types of character sets/languages must be supported _________________________________
„ Date and time should be correct for end users
_________________________________

© SAP AG 2007 / 4

Motivation for Time Zones

_________________________________
More and more customers are implementing a global solution
_________________________________
Several topics are always visible
„ Language support: (e.g., “How to handle these fancy scripts for Asia?”) _________________________________
„ Unicode support _________________________________
„ Localization: (e.g., “How to support local requirements like chart of
account?”) _________________________________
„ And:
– How to handle systems running on multiple time zones? _________________________________
Topics to discuss regarding time zones _________________________________
„ System availability/maintenance
_________________________________
„ Application-related topics
– Correct date and time for end user _________________________________
– Posting period
– Detailed scheduling and tracking, ... _________________________________
„ Support organization with 24x7 for end users
© SAP AG 2007 / 5
 Example SAP ESS/MSS Team Calendar: Is the Date Correct?
_________________________________
_________________________________
ESS/MSS
Test CompanyApplication
_________________________________
_________________________________
_________________________________
Today’s date: Local or _________________________________
Global Universal Time
Coordinated (UTC)? _________________________________
_________________________________

What is displayed for user at 9 am in Sydney (UTC+10) _________________________________

if server is in London (UTC)?
_________________________________

© SAP AG 2007 / 6

Time Zones
_________________________________
Time zones are important attributes of
_________________________________
„ Application objects (customers, vendors, plants, companies, … )
„ Events (scheduling, tracking, period determination, ... ) _________________________________
Time zone related functionality of Basis system _________________________________
– Unification and serialization of system events
„ Logistics _________________________________
– Scheduling and tracking of business events
– Shipping and transport, stock movements, service calls
_________________________________
„ Financials _________________________________
– Determination of posting dates (resulting in posting periods)
„ Organizational Issue: _________________________________
– End-user support around the world
_________________________________
_________________________________

© SAP AG 2007 / 7

Time Zone Definitions

_________________________________
Operating System Time
„ Time zone is defined within the user settings _________________________________
– Environment variable TZ under Unix
– This time zone setting also defines daylight saving time
- Time does not need to be adjusted
_________________________________
„ Database and <sid>adm must use the same time zone
_________________________________
System Time Zone
„ Need to be identical with operating system time _________________________________
– The system time zone is set within the IMG
_________________________________
User Time Zone
„ Defines the time zone, where the user is located _________________________________
– The user time zone is set within the user defaults (address)

Business Object Time Zone _________________________________

„ Business objects do have time zone as attribute
_________________________________
Default Time Zone
„ Is used for business objects if no time zone is defined _________________________________

© SAP AG 2007 / 8
 Technical Basis Environment
_________________________________
The SAP Basis/Web Application Server (WAS)/SAP NetWeaver® system is
always using system time _________________________________
„ All Basis services such as
– Batch processing _________________________________
– Update requests
– Syslog message _________________________________
– Change document
„ Example: The end user needs to calculate system time to schedule a batch job _________________________________
Exception: Transaction SP01 (display spool requests) is using user time
instead of system time (and as of SAP R/3 Enterprise some more system _________________________________
transactions are exceptions)
All system processes that are active in the SAP system (all application
_________________________________
servers database [DB], DB listener, etc.), must have the same time zones
_________________________________
Also relevant to the system time are discussions about system availability,
downtime, maintenance _________________________________
Interfaces to systems in other time zones handled individually
_________________________________

© SAP AG 2007 / 9

Motivation and overview of time zones
User-related time zone approach
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Object-related time zone approach _________________________________

_________________________________
Customized time zone developments
_________________________________
Wrap-up

Time Zone Functionality: User-Related Approach

_________________________________
Date and time in wall-clock format
„ Problem: (e.g., The posting day should be in the right period)
_________________________________
– No time zone information by default
_________________________________
Proposed and default date/time calculated in user date/time
_________________________________
„ Should no longer refer to the system date/time
(location of database server) _________________________________
„ Have to refer to the local date/time at location of the user
„ User can change the date/time information in user profile _________________________________
Constraints for date/time _________________________________
„ Have to refer to the local date and time instead of system date
and time
_________________________________
„ Should be handled uniquely (i.e., no “mix” of user-related and _________________________________
system time approach)
_________________________________

© SAP AG 2007 / 11
 Configuration in SAP NetWeaver ABAP
_________________________________
„ Time zone settings defined
within the IMG _________________________________
„ System time zone will be set
– This time must match _________________________________
operating system
„ Default time zone is used for _________________________________
users/objects without time
zone settings _________________________________
„ Time zone for user is
defined in the user address _________________________________
– Will be maintained by end
user _________________________________
„ Functionality used for
proposals _________________________________
„ Recommended to run a
unique approach (i.e., if user _________________________________
time zone is applied,
maintain it for all users) _________________________________

© SAP AG 2007 / 12

User Settings in SAP NetWeaver ABAP

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Activates
_________________________________
time zone
settings _________________________________
_________________________________
Shows user and _________________________________
system time
zone in
© SAP AG 2007 / 13
transaction SU3

Time Zone in SYSTEM Æ STATUS

_________________________________
_________________________________
_________________________________
_________________________________
Shows user
time zone in _________________________________
any
application _________________________________
or
transaction _________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 14
 Time Zone Functionality: User Settings in Java/Portal
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Local time zone in SAP

_________________________________
NetWeaver Portal User
Profile
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 15

Time Zone Functionality: User-Related Approach in FI

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

„ FI posting without time zone „ User time zone changed to New

setting for the end user
„ Proposal for posting date is equal
to system date
Zealand time
„ Proposal for posting date is
given in New Zealand time
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 16

Example: FI Documents with Time Zones Enabled

_________________________________
Purpose
„ This scenario describes the contents of date fields on the FI
_________________________________
document when the time zone function is enabled in the system
(DST = Daylight Saving Time) _________________________________
Scenario _________________________________
„ System Time Zone = EST (New York) (no DST = UTC-5)
„ User Time Zone = UTC+10 (e.g., Australia) _________________________________
„ User Company Code = 4100
„ Date and Time of Document Posting:
_________________________________
– User date/time = 13.11.05/09:47:06 (system time+15 h)
_________________________________
– System date/time = 12.11.05/18:47:06
Result _________________________________
„ When the time zone function is enabled in the system, default dates at
the time of data entry are based on the user’s time zone, not the _________________________________
system date
„ The Entry date and Time of entry fields in the accounting document _________________________________
header receive the system date and time (table BKPF)
© SAP AG 2007 / 17
 Example: FI Scenario Period End Procedures
_________________________________
Purpose
_________________________________
„ This topic discusses the implications of the fiscal period end for a
corporation or companies with plants located in multiple time zones _________________________________
Scenario
_________________________________
„ You may have one or both of the following situations:
1. Companies located in multiple time zones _________________________________
2. Separate entities within a corporation (for example, with plants that are
located in separate time zones) _________________________________
Result _________________________________
„ FI close period
– The FI posting periods are determined by the fiscal year variant _________________________________
associated with the company code. You can open/close posting periods
based on a company code’s local time if you have a unique fiscal year _________________________________
variant defined for each company code. Authorizations can be used to
prevent unwanted postings into open periods other than the current
period.
_________________________________

© SAP AG 2007 / 18

Customizing of Company Code via SAP IMG

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
Customizing _________________________________
node for
company _________________________________
code
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 19

Company Code Address with Time Zone

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
Maintenance screen for
the address of a company _________________________________
code with field for
the time zone _________________________________
_________________________________
_________________________________

© SAP AG 2007 / 20
 Time Zones in SAP NetWeaver BI
_________________________________
The local time is customized by transaction STZAC
_________________________________
_________________________________
_________________________________
_________________________________
If the user time zone differs from the system time zone, you
can see this in the system status (or transaction SU01): _________________________________

User is assigned
_________________________________
to CET (Central
European Time) _________________________________
_________________________________
User is assigned
to EST (Eastern
Standard Time)
_________________________________

© SAP AG 2007 / 21

Time Stamps for User Time Zone in SAP NetWeaver BI

_________________________________
All SAP NetWeaver BI monitors display timestamps regarding the
user time zone:
_________________________________
RSD1
Cube _________________________________
admin-
istrator _________________________________
_________________________________
Monitor
Monitor details
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 22

Time Stamps for System Time in SAP NetWeaver BI

_________________________________
Basis monitors display timestamps regarding the system time:
_________________________________
ST22 Dump Analysis
_________________________________
_________________________________
_________________________________
_________________________________
SM21 system log _________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 23

Motivation and overview of time zones
User-related time zone approach
Object-related time zone approach
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Customized time zone developments _________________________________

_________________________________
Wrap-up

Time Zone Functionality: Object-Related Approach

_________________________________
Time zone in logistics should reflect business object location
_________________________________
„ Time zone as attribute of a “business object” ...
– Plant _________________________________
– Warehouse
– Customer _________________________________
– User
_________________________________
Time critical functions in logistics should consider day, time, and
time zones _________________________________
„ Scheduling of movements
– Sales and distribution
_________________________________
– Warehousing and shipping
– Stock movements
_________________________________
„ Tracking _________________________________
– Transportation
„ Service management _________________________________
– Customer calls/call centers

© SAP AG 2007 / 25

Example Scenario Without Time Zone Handling ...

_________________________________
Plant Object view _________________________________
Eastern Europe Customer
Americas _________________________________
(UTC + 2)
Store (UTC - 8)
Central Europe _________________________________
(UTC + 1) _________________________________
_________________________________
_________________________________
Production time: Arrival time:
8:00 PM 7:00 PM _________________________________
Store-in time: Arrives before
7:30 PM Delivery time: produced! _________________________________
8:00 PM
_________________________________
Database view
© SAP AG 2007 / 26
 ... With Time Zone Functionality: Object-Related Approach
_________________________________
Plant Object view Customer _________________________________
Eastern Europe (UTC + 2) Americas (UTC - 8)
Production time: Store _________________________________
Arrival time:
8:00 PM Central Europe (UTC + 1) 7:00 PM
Store-in time:
Delivery time:
_________________________________
7:30 PM
8:00 PM _________________________________
_________________________________
_________________________________
Production time: Arrival time:
6:00 PM 3:00 AM _________________________________
Store-in time:
6:30 PM _________________________________
Delivery time:
7:00 PM (UTC) _________________________________
Database view
© SAP AG 2007 / 27

IMG – Customizing of Business Object Address

_________________________________
Customizing _________________________________
of plant data
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 28

Example: Plant Maintenance

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
Customizing
of plant _________________________________
address
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 29
 Time Zone of Address
Maintenance screen for
the address of a plant
with field for the time zone
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 30

Same Concept for All Objects with Addresses

_________________________________
Financial Accounting
„ Company code _________________________________
Logistics – General _________________________________
„ Locations
„ Plants _________________________________
Sales and distribution _________________________________
„ Sales organizations
„ Sales office _________________________________
Materials Management
„ Storage locations (can have several addresses)
_________________________________
Logistics eExecution _________________________________
„ Transportation planning point
_________________________________
Customer
... _________________________________

© SAP AG 2007 / 31

Distribution of Time Zones from SAP ERP to SCM (APO)

_________________________________
Location Type Production Plant
_________________________________
Data transfer from the R/3 production plant
_________________________________
Custom izing: Plant M aster data: Location
APO
Plant 1000 Location 1000 Plant Ham burg _________________________________
Nam e Plant Ham burg Loc.type 1001 Production plant Time zone to
be maintained
_________________________________
General Address
Street Alsterstr. 13
in SAP R/3 for _________________________________
Town 22222 Ham burg Street Alsterstr. 13
use in Supply
Town 22222 Ham burg
Country DE Germ any Chain _________________________________
Country DE Germ any
Region 02 Hamburg Management
Region 02 Hamburg (SCM)/Advanced
Tim e zone
Language
CET
Germ an Tim e zone CET Planning and
_________________________________
Language Germ an Optimization
(APO)
_________________________________
© SAP AG 2001 _________________________________

© SAP AG 2007 / 32
 Time Zones in CRM: Object-Related Approach

Overview over _________________________________

Date Profile date profile in the CRM*
_________________________________
“One-Order Framework”
functionality
_________________________________
Mandatory Duration CRM transaction
z Mandatory:
types
_________________________________
Number value
Time unit (e.g., 4 days)
_________________________________
z Date rules
Date Assigned _________________________________
format to
_________________________________
Mandatory Reference _________________________________
Object CRM item
z Only by having a
reference object
z Master data of possible _________________________________
at certain time
reference objects
(business partner, user)
categories
can become local must contain time zone _________________________________
*CRM = Customer Relationship Management
© SAP AG 2007 / 33

Time Zones in CRM: Object-Related Approach (cont.)

_________________________________
„ Date management is possible at header and item levels
_________________________________
– IMG Î Customer Relationship Management Î Basic Functions Î
Date Management Î Assign Date Profile to Transaction Type or _________________________________
Assign Date Profile to Item Category
_________________________________
HEADER
_________________________________
Assign to _________________________________

ITEM
_________________________________
_________________________________
Date
profile _________________________________
Assign to
_________________________________

© SAP AG 2007 / 34

Motivation and overview of time zones
User-related time zone approach
Object-related time zone approach
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Customized time zone developments _________________________________

_________________________________
Wrap-up
 Time Zone Definition
_________________________________
„ Set of rules that dictates the offset of the user’s local time from
UTC _________________________________
Time Zone _________________________________
„ Time zone includes _________________________________
„ Offset to Greenwich Time Zone rule DST rule
Mean Time (GMT) or _________________________________
Universal Time Coordinate (UTC)
DST variable rules Fixed DST rule
„ Daylight saving time definition _________________________________
_________________________________
„ Internal and external representation
_________________________________
„ String of six characters to identify the time zone (e.g., two time zones
for Central Europe: One using daylight saving time, the second not
using it)
_________________________________
_________________________________

© SAP AG 2007 / 36

Time Zone Examples (Customizing)

List of all defined time
zones in SAP Customizing.
New time zones can be added
with own names.
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 37

ABAP DDIC Definitions for Time Zones

_________________________________
Field for Timestamp: TSTMP (DEC 15 – Internal P (8: Short/11 Long))
_________________________________
Field for Time zone: TZONE ((CHAR 6) – Internal C (6))
Customizing tables _________________________________
„ TTZCU: Customizing Time Zones
„ TTZD: DST rules
_________________________________
„ TTZDF: DST (fixed annual rules)
„ TTZDV: DST (variable rules)
_________________________________
„ TTZR: Time Zone rules
_________________________________
„ TTZZ: Time Zones

System fields _________________________________

„ SYST-TSTUT
– Time Stamp _________________________________
„ SYST-DATUM/SYST-UZEIT
– System date and time _________________________________
„ SYST-DATLO/SYST-TIMLO
– System time converted into user’s time zone _________________________________

© SAP AG 2007 / 38
 Time Zones Customizing Transactions
_________________________________
_________________________________
_________________________________
Main Time Zones Customizing Transactions
(T-Codes) _________________________________
T-Code Description _________________________________
STZAC Maintain time zone Customizing
_________________________________
STZAD Display time zone Customizing
STZBC Maintain time zone basis Customizing _________________________________
STZBD Display time zone basis Customizing
_________________________________
STZGC Maintain geographic time zone Customizing
STZGD Display geographic time zone Customizing _________________________________
_________________________________

© SAP AG 2007 / 39

Time Zones ABAP Library for Own Development (Selection)

_________________________________
TZ_UTIL (Function Group) Time Zone Utilities
TZON_CHECK_TIMEZONE
_________________________________
TZON_GET_TIMEZONE_TEXT
TZON_GET_USER_TIMEZONE _________________________________
…
TZN0 (Function Group) Time Zones _________________________________
TZ_CONVERT_FROM_INT4
TZ_CONVERT_TO_INT4 _________________________________
TZ_GLOBAL_TO_LOCAL
TZ_LOCAL_TO_GLOBAL _________________________________
TZ_LOCAL_TO_SYSTEM
TZ_LOCATION_SYSTEMCLOCK _________________________________
TZ_LOCATION_TIMEZONE
TZ_SYSTEM_GET_TZONE _________________________________
TZ_SYSTEM_TO_LOCAL
TZ_USER_SYSTEMCLOCK
TZ_USER_WORKAREA_INIT
_________________________________
TZ_UTC_SYSTEMCLOCK
…
_________________________________

© SAP AG 2007 / 40

Example: TZ_LOCAL_TO_SYSTEM (System in CET)

_________________________________
_________________________________
_________________________________
_________________________________
Example for ABAP
function that _________________________________
converts local time
to system time _________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 41
 ABAP Commands
_________________________________
CONVERT
„ CONVERT TIMESTAMP f1 TIMEZONE f2 INTO DATE f3
_________________________________
TIME f4
_________________________________
– See help in ABAP

WRITE
_________________________________
„ Output of time Stamp _________________________________
WRITE f1 TIMEZONE f2
„ Output of time Stamp (only date) _________________________________
WRITE f1 TIMEZONE f2 AS DATE
„ Output of time Stamp (only time) _________________________________
WRITE f1 TIMEZONE f2 AS TIME
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 42

How to Test Time Zone Developments

_________________________________
„ Run tests with client and server within different time zones
_________________________________
„ Run tests with different parties involved in the scenario (plant,
customer, processor, …) and locate these parties in different _________________________________
time zones
„ Run tests (entering/processing time dependent data) and set the _________________________________
local time of the server within duplicate hour at end of DST
_________________________________
(switching date from/to DST)
„ Run tests entering time dependent data. Choose legal and illegal _________________________________
timepoints as well as time durations that touch.
– The duplicate hour at the end of DST _________________________________
– The missing hour at the beginning of DST
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 43

Useful Test Time Points (Switch from/to DST)

Within duplicate hour
in Germany 27 September 1981, 2:11 local time
26 September 1993, 2:13 local time
29 October 2006, 2:15 local time
28 October 2007, 2:17 local time
26 October 2008, 2:19 local time
in Australia 1 March 1981, 2:11 local time
7 March 1993, 2:13 local time
NSW – Sydney 2 April 2006, 2:15 local time
25 March 2007, 2:17 local time
(New South
Wales) 30 March 2008, 2:19 local time
_________________________________
Within missing hour
_________________________________
29 March 1981, 2:01 local time
28 March 1993, 2:03 local time _________________________________
26 March 2006, 2:05 local time
25 March 2007, 2:07 local time
30 March 2008, 2:09 local time
_________________________________
25 October 1981, 2:01 local time _________________________________
31 October 1993, 2:03 local time
29 October 2006, 2:05 local time
28 October 2007, 2:07 local time
_________________________________
26 October 2008, 2:09 local time
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 44
 Switch to/from DST
_________________________________
„ In a global system use time zone of the majority of users
_________________________________
„ Switch from winter to summer time (DST)
– Generally no problem for duplicate timestamps, etc. _________________________________
– Possibly batch jobs and background jobs must be rescheduled
_________________________________
„ Switch from summer (DST) to winter time: _________________________________
– 2 hours downtime to be planned during switch from summer to
winter time (double hour problem, could lead to duplicate _________________________________
timestamps)
– Up from Basis ≥ 6.40 a “slowdown” of SAP kernel possible so that _________________________________
only “one hour consumed for two real hours”
– Check is needed if application supports this mechanism _________________________________
– More information in SAP Notes 102088 and 7417 and references
_________________________________
„ If no downtime acceptable:
– Operate a global system in UTC without DST! _________________________________

© SAP AG 2007 / 45

Motivation and overview of time zones
User-related time zone approach
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Object-related time zone approach _________________________________

_________________________________
Customized time zone developments
_________________________________
Wrap-up

Date and Time in SAP Systems

_________________________________
The system needs to know
ƒ Correct UTC time or
_________________________________
ƒ Time zone, date, and time
to convert properly between _________________________________
universal time and local time
_________________________________
When using a local point in time,
when changing from summer time to _________________________________
winter time, an indicator is needed during
the duplicate hour _________________________________
_________________________________
For each date and time value, it should be clear
whether it is represented in _________________________________
ƒ Local time,
ƒ Global time (UTC),
ƒ Independent of time zone (e.g., server time)
_________________________________
_________________________________

© SAP AG 2007 / 47
 Time Zone Functionality (Mostly) Implemented
_________________________________
User-related time zone approach
_________________________________
„ Mostly being used for financial applications
„ Being used for Basis system transaction spool display (SP01) _________________________________
and up from SAP R/3 Enterprise in a few more system transactions
_________________________________
Object-related time zone approach
„ Being used for logistics applications _________________________________
„ Some functionality still missing in SAP ERP components
_________________________________
„ Implemented in SAP SCM and in CRM (date formats)

Time zone functionality needs to be implemented by application

_________________________________
development – or by customer development _________________________________
„ It is not just a Basis service, which is active by default
_________________________________
_________________________________

© SAP AG 2007 / 48

Resources
_________________________________
SAP Service Marketplace:
_________________________________
„ General information about global solutions
– http://service.sap.com/globalization * _________________________________
Æ List of FAQ Æ Which time-zone functionality does SAP currently
offer? _________________________________
Æ Media Library Æ Globalization Workshop Æ Country Version and
Time Zones _________________________________
„ More Questions? Write email to globalization@sap.com
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
* Requires login credentials to the SAP Service Marketplace
© SAP AG 2007 / 49

Time Zone Online Documentation on http://help.sap.com

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
http://help.sap.com > SAP ERP >
ERP Central Component Release
6.0 SR1 SP08 > English > SAP
_________________________________
Library > SAP ERP Central
Component > Cross-Application _________________________________
Components > General
Application Functions (CA-GTF) > _________________________________
Time Zones (CA-GTF-TIM)
Access to time
zone specific _________________________________
online
documentation
© SAP AG 2007 / 50
 New Book Global SAP-Systems – Design and Architecture
_________________________________
_________________________________
Available end of _________________________________
October 2007
in German first, _________________________________
English follows in
April 2008 _________________________________
_________________________________
_________________________________
SAP PRESS _________________________________
270 Pages
_________________________________
_________________________________
www.sappress.com/product.cfm?account=&product=H2917
© SAP AG 2007 / 51

7 Key Points to Take Home

_________________________________
„ Time zones are supported in SAP
_________________________________
„ The user-related time zone approach assigns every SAP user
a local time zone. It is mostly used in financial applications. _________________________________
„ The business object-related time zone approach assigns every _________________________________
business object with a configured address a time zone. It is used
for logistics applications mostly. _________________________________
„ SAP CRM and SCM provide extended time zone functionality _________________________________
„ If time zones are actively used, the user and object-related _________________________________
settings should be used for all user and all business objects
_________________________________
„ You can customize and configure time zones
_________________________________
„ An ABAP function library allows you to develop specific
customized programs for your own time zone requirements _________________________________

© SAP AG 2007 / 52

Your Turn
_________________________________

Thank _________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

© SAP AG 2007 / 53
YOU! _________________________________
 Copyright 2007 SAP AG. All Rights Reserved.
_________________________________
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
_________________________________
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,

_________________________________
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
_________________________________
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
_________________________________
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, SAP, SAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks
or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
_________________________________
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this
_________________________________
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
_________________________________
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
_________________________________
_________________________________

© SAP AG 2007 / 54
Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026
Copyright © 2007 Wellesley Information Services. All rights reserved.