___________________________ ______ _________________________________ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ _________________________________ ___________________________ ______ ©
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 You Are on the Globe Globe UTC
What time and date is it?
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!
It is Nov 1
Which day is today?
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 re gions
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 dependent
Translation process must be supported
All types of character sets/languages 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
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 s ystem (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
©
SAP AG 2007 / 13
Shows user and system time zone in 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 setting for the end user
User time zone changed to New Zealand time
Proposal for posting date is equal to system date
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
User Company Code = 4100
Date and Time of Document Posting: – User date/time =
13.11.05/09:47:06
– System date/time =
12.11.05/18:47:06
(e.g., Australia)
(system time+15 h)
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 administrator
Monitor details
Monitor
©
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
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 Eastern Europe (UTC + 2)
Production time: 8:00 PM
Object view Store Central Europe (UTC + 1)
Store-in time: 7:30 PM Delivery time: 8:00 PM
Database view ©
SAP AG 2007 / 26
Customer Americas (UTC - 8)
Arrival time: 7:00 PM Arrives before produced!
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
... With Time Zone Functionality: Object-Related Approach
Plant Eastern Europe (UTC + 2) Production time: 8:00 PM
Production time: 6:00 PM
Object view
Customer Americas (UTC - 8)
Store
Arrival time: 7:00 PM
Central Europe (UTC + 1) Store-in time: Delivery time: 7:30 PM 8:00 PM
Store-in time: 6:30 PM Delivery time: 7:00 PM
Arrival time: 3:00 AM
(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 Customizing: Plant
1000
Location
1000
Plant Hamburg
Name
Plant Hamburg
Loc.type
1001
Production plant
Street
Alsterstr. 13
Town
22222 Hamburg
Country DE Region 02 Time zone Language
© SAP AG 2001
©
Master data: Location
Plant
SAP AG 2007 / 32
Germany Hamburg CET German
G en er al
A dd ress
Street
Alsterstr. 13
Town
22222 Hamburg
Country DE
Germany
Region 02
Hamburg
Time zone
CET
Language
German
AP O Time zone to be maintained in SAP R/3 for use in Supply Chain Management (SCM)/Advanced Planning and Optimization (APO)
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
Time Zones in CRM: Object-Related Approach Overview over date profile in the CRM* “One-Order Framework” functionality
Date Profile Duration
Mandatory
CRM transaction types
Mandatory: Number value Time unit (e.g., 4 days)
Date rules
Assigned to
Date format Mandatory
Only by having a reference object at certain time can become local
Reference Object
CRM item categories
Master data of possible reference objects (business partner, user) 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 Customer Relationship Management Basic Functions – IMG 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
Time Zone rule Offset to Greenwich Mean Time (GMT) or Universal Time Coordinate (UTC)
Daylight saving time definition
Internal
©
DST rule
D ST va ria bl e r ul es
F ix ed DS T ru le
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 TIME
TIMEZONE f2
INTO
DATE
f3
f4
– See help in ABAP
WRITE
Output of time Stamp
WRITE
f1
TIMEZONE f2
AS DATE
Output of time Stamp (only time)
WRITE
©
TIMEZONE f2
Output of time Stamp (only date)
WRITE
f1
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
Within missing 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
29 March 1981, 2:01 local 28 March 1993, 2:03 local 26 March 2006, 2:05 local 25 March 2007, 2:07 local 30 March 2008, 2:09 local
in Australia
1 March 1981, 2:11 local time 7 March 1993, 2:13 local time 2 April 2006, 2:15 local time 25 March 2007, 2:17 local time 30 March 2008, 2:19 local time
25 October 1981, 2:01 local t ime 31 October 1993, 2:03 local t ime 29 October 2006, 2:05 local t ime 28 October 2007, 2:07 local t ime 26 October 2008, 2:09 local t ime
NSW – Sydney (New South Wales)
©
SAP AG 2007 / 44
time time time time time
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
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 sw itch 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 s ystem 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 ER P 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 [email protected]
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
* 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)
©
SAP AG 2007 / 50
Access to time zone specific online documentation
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
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
Thank
YOU! ©
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
SAP AG 2007 / 53
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
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 trademarksof 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 an y 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 theinforma tion, 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.
