46880563 Time Zones in Sap Presentation

© SAP AG 2007 / 0

What Time Is It Where You Are? Best Practices for Managing Global SAP Systems Running on Different Time ZonesAlexander DavidenkoffSAP AG

Object-related time zone approach

Customized time zone developments

Motivation and overview of time zones

User-related time zone approach

Wrap-up

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 3

Date and Time – Depends Where You Are on the Globe

It is 07h 37m 54sIt is Oct 31 (UK)

So, it is 00h 37m 54s

What time and date is it?

Which day is today?


It is Oct 31DST applies

It is 05h 07m 54s

UTC

31 Oct 2007, 23:37:54


It is Oct 31

2007

DST applies!

Which year?

Which day is today?

It is 09 h 37m 54s

It is Nov 1

DST applies

Which day is today?

It is Nov 1 (DE)

UTC = Universal Time CoordinatedDST = Daylight Saving Time

© SAP AG 2007 / 4

Requirements for an IT Solution Serving a Global Company

The solution must support global business practicesGlobal reporting, consolidationGlobal process definition

The solution must allow for local requirementsTax calculation, accounting rules, financial reporting standardsPayroll (taking into account local tax and social insurance)

The solution must be usable across regionsLocal calendars and time zones must be handledUse of multiple currencies

The data must be usable around the worldText descriptions of data must be language dependentTranslation process must be supportedAll types of character sets/languages must be supportedDate and time should be correct for end users

© SAP AG 2007 / 5

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 zonesSystem availability/maintenanceApplication-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 / 6

Example SAP ESS/MSS Team Calendar: Is the Date Correct?

Test CompanyESS/MSS Application

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 / 7

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 / 8

Time Zone Definitions

Operating System TimeTime 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 ZoneNeed to be identical with operating system time– The system time zone is set within the IMG

User Time ZoneDefines the time zone, where the user is located– The user time zone is set within the user defaults (address)

Business Object Time ZoneBusiness objects do have time zone as attribute

Default Time ZoneIs used for business objects if no time zone is defined

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 9

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





Wrap-up

© SAP AG 2007 / 11

Time Zone Functionality: User-Related Approach

Date and time in wall-clock formatProblem: (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/timeShould no longer refer to the system date/time (location of database server) Have to refer to the local date/time at location of the userUser can change the date/time information in user profile

Constraints for date/timeHave 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 / 12

Time zone settings defined within the IMGSystem time zone will be set – This time must match

operating system Default time zone is used for users/objects without time zone settingsTime zone for user is defined in the user address– Will be maintained by end

userFunctionality used for proposalsRecommended to run a unique approach (i.e., if user time zone is applied, maintain it for all users)

Configuration in SAP NetWeaver ABAP

© SAP AG 2007 / 13

User Settings in SAP NetWeaver ABAP

Activates time zone settings

Shows user and system time

zone in transaction SU3

© SAP AG 2007 / 14

Time Zone in SYSTEM STATUS

Shows user time zone in

any application

or transaction

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 15

Time Zone Functionality: User Settings in Java/Portal

Local time zone in SAP NetWeaver Portal User

Profile

© SAP AG 2007 / 16

Time Zone Functionality: User-Related Approach in FI

User time zone changed to New Zealand timeProposal for posting date is given in New Zealand time

FI posting without time zone setting for the end userProposal for posting date is equal to system date

© SAP AG 2007 / 17

Example: FI Documents with Time Zones Enabled

PurposeThis 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 = 4100Date 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 dateThe Entry date and Time of entry fields in the accounting document header receive the system date and time (table BKPF)

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 18

Example: FI Scenario Period End Procedures

PurposeThis 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 zones2. 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 variantassociated 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 / 19

Customizing of Company Code via SAP IMG

Customizing node for company

code

© SAP AG 2007 / 20

Company Code Address with Time Zone

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

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 21

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)

Time Zones in SAP NetWeaver BI

© SAP AG 2007 / 22

Time Stamps for User Time Zone in SAP NetWeaver BI

All SAP NetWeaver BI monitors display timestamps regarding the user time zone:

RSD1

MonitorMonitor details

Cube admin-istrator

© SAP AG 2007 / 23

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

SM21 system log

Time Stamps for System Time in SAP NetWeaver BI

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________





Wrap-up

© SAP AG 2007 / 25

Time Zone Functionality: Object-Related Approach

Time zone in logistics should reflect business object locationTime 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 / 26

Object view

Database view

StoreCentral Europe(UTC + 1)

Store-in time:7:30 PM

Production time:8:00 PM

PlantEastern Europe (UTC + 2)

Delivery time:8:00 PM

Arrival time:7:00 PM Arrives before produced!

CustomerAmericas(UTC - 8)

Example Scenario Without Time Zone Handling ...

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 27

Database view

Store-in time:6:30 PM


Delivery time:7:00 PM

Arrival time:3:00 AM

(UTC)

Object view

StoreCentral Europe (UTC + 1)

PlantEastern Europe (UTC + 2)

CustomerAmericas (UTC - 8)

... With Time Zone Functionality: Object-Related Approach


Store-in time:7:30 PM Delivery time:

8:00 PM

Arrival time:7:00 PM

© SAP AG 2007 / 28

IMG – Customizing of Business Object Address

Customizing of plant data

© SAP AG 2007 / 29

Example: Plant Maintenance

Customizing of plant address

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 30

Time Zone of Address

Maintenance screen for the address of a plant with field for the time zone

© SAP AG 2007 / 31

Same Concept for All Objects with Addresses

Financial AccountingCompany code

Logistics – General LocationsPlants

Sales and distributionSales organizationsSales office

Materials ManagementStorage locations (can have several addresses)

Logistics eExecutionTransportation planning point

Customer

...

© SAP AG 2007 / 32

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

© SAP AG 2001

Location Type Production Plant

Plant

Name

Customizing: Plant

Street Alsterstr. 13

Town 22222 Hamburg

Country DE

Region 02

Time zone CET

Language German

Plant Hamburg

1000

Master data: Location

Plant Hamburg1000

Loc.type Production plant1001

Alsterstr. 13

Town 22222 Hamburg

DE

02

Germany

Hamburg

Time zone CET

Language German

General Address

Data transfer from the R/3 production plant

Location

Street

Country

Region

Germany

Hamburg

APO

Time zone to be maintained in SAP R/3 for use in Supply Chain Management (SCM)/Advanced Planning and Optimization (APO)

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 33

Time Zones in CRM: Object-Related Approach

Duration

ReferenceObject

Mandatory

MandatoryMandatory:Number valueTime unit (e.g., 4 days)

Master data of possiblereference objects (business partner, user) must contain time zone

Only by having a reference objectat certain time can become local

Date Profile

Assigned to

CRM transactiontypes

CRM itemcategories

Dateformat

Overview overdate profile in the CRM*“One-Order Framework”functionality

Date rules

*CRM = Customer Relationship Management

© SAP AG 2007 / 34

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

Dateprofile

Assign to

HEADER

ITEM

Assign to





Wrap-up

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 36

Time Zone Definition

Set of rules that dictates the offset of the user’s local time from UTC

Time zone includesOffset to Greenwich Mean Time (GMT) orUniversal Time Coordinate (UTC)Daylight saving time definition

Internal and external representationString 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)

Time Zone rule

DST variable rules Fixed DST rule

DST rule

Time Zone

© SAP AG 2007 / 37

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 / 38

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 tablesTTZCU: Customizing Time ZonesTTZD: DST rulesTTZDF: DST (fixed annual rules) TTZDV: DST (variable rules) TTZR: Time Zone rulesTTZZ: Time Zones

System fieldsSYST-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 / 39

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

Time Zones Customizing Transactions

© SAP AG 2007 / 40

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 …

Time Zones ABAP Library for Own Development (Selection)

© SAP AG 2007 / 41

Example: TZ_LOCAL_TO_SYSTEM (System in CET)

Example for ABAPfunction that converts local time to system time

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 42

ABAP Commands

CONVERTCONVERT TIMESTAMP f1 TIMEZONE f2 INTO DATE f3TIME f4

– See help in ABAP

WRITEOutput of time StampWRITE 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 / 43

How to Test Time Zone Developments

Run tests with client and server within different time zonesRun 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 illegaltimepoints 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 / 44

Useful Test Time Points (Switch from/to DST)

25 October 1981, 2:01 local time 31 October 1993, 2:03 local time29 October 2006, 2:05 local time 28 October 2007, 2:07 local time26 October 2008, 2:09 local time

1 March 1981, 2:11 local time 7 March 1993, 2:13 local time2 April 2006, 2:15 local time25 March 2007, 2:17 local time 30 March 2008, 2:19 local time

in Australia

NSW – Sydney(New South Wales)

29 March 1981, 2:01 local time28 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

27 September 1981, 2:11 local time26 September 1993, 2:13 local time29 October 2006, 2:15 local time28 October 2007, 2:17 local time26 October 2008, 2:19 local time

in Germany

Within missing hourWithin duplicate hour

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 45

Switch to/from DST

In a global system use time zone of the majority of usersSwitch 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!





Wrap-up

© SAP AG 2007 / 47

Date and Time in SAP Systems

For each date and time value, it should be clearwhether it is represented in

Local time, Global time (UTC),Independent of time zone (e.g., server time)

The system needs to knowCorrect UTC time orTime 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

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 48

Time Zone Functionality (Mostly) Implemented

User-related time zone approachMostly being used for financial applicationsBeing 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 approachBeing used for logistics applicationsSome functionality still missing in SAP ERP componentsImplemented 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 / 49

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 / 50

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 / 51

New Book Global SAP-Systems – Design and Architecture

Available end of October 2007in German first, English follows in April 2008

www.sappress.com/product.cfm?account=&product=H2917

SAP PRESS270 Pages

© SAP AG 2007 / 52

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 everybusiness 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 / 53

ThankYour Turn

YOU!

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

© SAP AG 2007 / 54

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.

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

46880563 Time Zones in Sap Presentation

Documents

Transcript of 46880563 Time Zones in Sap Presentation