011000358700004462132005 e

7/25/2019 011000358700004462132005 e

http://slidepdf.com/reader/full/011000358700004462132005-e 1/16

© SAP AG 1

©SAP AG2005

Status: (23/08/05)

Change of

EquipmentHistory

7/25/2019 011000358700004462132005 e


© SAP AG 2

© SAP AG2005

Objectives

After completing this presentation, you will be able to:

Understand the purpose of this development

Explain the function and features of “Change Equipment

History”

7/25/2019 011000358700004462132005 e


© SAP AG 3

© SAP AG2005

Business Pain Points

In asset-intensive industries, customers often demand asolution which allows an exception handling process for

incorrect equipment usage data.

In releases up to ECC 5.0, it was impossible to change

incorrectly entered equipment installations (e.g. with wrong

date or location) in a consistant manner. This is not

acceptable for industries that have to comply with

regulatory requirements which require that equipment life

cycles are accurately documented.

7/25/2019 011000358700004462132005 e


© SAP AG 4

© SAP AG2005

Change of Equipment History

As of ECC 6.0 , you can make back-dated changes to the

equipment history. In the process, the following data is

taken into consideration and corrected:

Equipment master data and equipment history

Definition of the measurement reading transfer and

adjustment of the corresponding measurement documents

Notifications that affect installation, removal, and exchange

7/25/2019 011000358700004462132005 e


© SAP AG 5

© SAP AG2005

Business Process

The aim of the solution is to correct errors in the history of

equipment data and to directly change other related objects. The user starts by entering a piece of equipment and the date/time,

on which he wants to start building up the new history.

With different functions the user builds up the new history / list of

events step by step.

Executing follow-up programs, these programs organize the new

equipment data, the measuring point assignments and the

measurement documents.

7/25/2019 011000358700004462132005 e


© SAP AG 6

© SAP AG2005

Change Equipment History

Workbench to

Transform Actual History

into Target History

Taking into account:

Data inheritance

Change Documents

Measurement

Documents

Measurement Reading

Transfer

Structure Gaps

Goods Movements

Synchronization with

Financial Assets

Synchronization with

CRM

Notifications

7/25/2019 011000358700004462132005 e


© SAP AG 7

© SAP AG2005

Example

Explanation of the time stamps of the picture above:

T0: Installation of equipment B into Equipment A.

T1: Installation of equipment A to the functional location X.

T2: Dismantling of equipment A from the functional location X.

T3: Change of a historic relevant field in equipment B (e.g. cost center) witch creates a new time

segment for equipment B. See point 3 on slide ‘Design of time segments at the moment’.

T4: Installation of equipment A to the functional location Y.

What changes happen when changing valid-to-date of time segment 2 of equipment A?

Equipment A:

- Valid-to-date/valid-to-time of time segment 2 are changed.

- Valid-from-date of time segment 3 is changed to the new valid-to-date of time segment 2 in order to

keep consistency.

Equipment B


- Valid-from-date of time segment 4 is changed to the new Valid-to-date of time segment 3 in order to

keep consistency.

7/25/2019 011000358700004462132005 e


© SAP AG 8

© SAP AG 2005

Example





T3: Change of a historic relevant field in equipment B (e.g. cost center) witchcreates a new time segment for equipment B. See point 3 on slide ‘Design oftime segments at the moment’.


What changes happen when changing valid-to-date of time segment 2 ofequipment A?

Equipment A:

Valid-to-date/valid-to-time of time segment 2 are changed.

Valid-from-date of time segment 3 is changed to the new valid-to-date of timesegment 2 in order to keep consistency.

Equipment B

Valid-to-date/valid-to-time of time segment 3 are changed.

Valid-from-date of time segment 4 is changed to the new Valid-to-date of timesegment 3 in order to keep consistency.





T3: Change of a historic relevant field in equipment B (e.g. cost center) witch creates a new time

segment for equipment B. See point 3 on slide ‘Design of time segments at the moment’.


What changes happen when changing valid-to-date of time segment 2 of equipment A?

Equipment A:


- Valid-from-date of time segment 3 is changed to the new valid-to-date of time segment 2 in order to

keep consistency.

Equipment B


- Valid-from-date of time segment 4 is changed to the new Valid-to-date of time segment 3 in order to

keep consistency.

7/25/2019 011000358700004462132005 e


© SAP AG 9

© SAP AG2005

The Various Phases of a ‘History Change’

The complete process can be

divided into 3 phases:

Phase 1: Replace Actual History

with Target History

Master data history, structure

gaps, material movements etc. are

created

Phase 2: After triggering „Replace

Actual History“ a job is triggered

This job is organizing the

measurement transfers.

Phase 3: The notification

processing starts after the

background job is finished

Process notification data

Balancing notifications

7/25/2019 011000358700004462132005 e


© SAP AG 10

© SAP AG2005

Phase 1 –Buildup a Target History

7/25/2019 011000358700004462132005 e


© SAP AG 11

© SAP AG2005

Supported Events

The following 4 events can be changed

created or copied by the Workbench

Dismantling

Installation

Exchange

Field Change

7/25/2019 011000358700004462132005 e


© SAP AG 12

© SAP AG2005

Phase 2 – Measurement Transfer

Phase 2: Background job for

measurement transfer

7/25/2019 011000358700004462132005 e


© SAP AG 14

© SAP AG2005

Conversion Log

The Workbench comes

with various predefined

system checks andmessages which appear in

a conversion log:

Consistency of actual

status

Installation possible

Recursion of

hierarchies

Field checks Inheritance

Structure gaps

…

7/25/2019 011000358700004462132005 e


© SAP AG 15

© SAP AG2005

Explain the main function/features and purpose of the

new development ‘Change Equipment History’

Now you are able to

Summary

7/25/2019 011000358700004462132005 e


© SAP AG 16

© SAP AG2005

Copyright 2005 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, 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, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks 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 intendedstrategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, productstrategy, 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 k ind 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 useof hot links contained in these materials and does not endorse your use o f third-party Web pages nor provide any warranty whatsoever relating to third-party

Web pages.