tm change controller · 2017. 2. 23. · change controller concept 2. customizing 3. chaco close-up...

Change Controller

Transportation Management 8.0/8.1/9.0Daniel Härder, Andreas Esau August 2012

Agenda

1. Change Controller Concept

2. Customizing

3. ChaCo Close-Up

4. Enhancement Concept

5. Additional Strategies

6. Cascading Strategy Execution

7. Related Notes

1. TOR is changed in one of thetriggering nodes (ROOT, STOP,ITEM_TR,EXECUTIONINFORMATION,CC_CHG_TR)

2. Determination DET_CALL_CHACOis called

3. Identification of changes4. Determination of change strategy5. Det. DET_TRIGGER_STRAT is

called: Registering of asynchronousstrategies, processing ofsynchronous strategies

6. Asynchronous change strategiesare processed asynchronously

BEFORE SAVE

BEFORE SAVEBEFORE SAVEBEFORE_SAVE

AFTERCOMMIT

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

In the TOR Type Customizing the following settings can be maintained:

And the change strategy isdetermined during runtime like this:

• Date Tolerance Condition• Condition of type /SCMTMS/CC_DATE_TOL• The maximum date/time change of a TOR can be classified in fieldCHG_DATE of transient node CC_CHG_TR as

• No change• Critical Change• Non-Critical Change

• This maximum date/time change is provided as a value in minutes viaDAD /SCMTMS/DATECHGDELTA• A negative value indicates an earlier date/time, a positive value a laterdate/time

• Quantity Tolerance Condition• Condition of type /SCMTMS/CC_QUAN_TOL• The maximum quantity change of a TOR can be classified in fieldCHG_QUANTITY of transient node CC_CHG_TR as

• No Relevant Quantity Change Determined• Relevant Quantity Change Determined

• This maximum value is provided as a value in the default unit of measureof the TOR (for weight and volume) vias DADs or via two seperate DADs incase of pieces for value and UOM• A negative value indicates quantity decrease, a positive value an increase

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

The ChaCo is able to react on TOR changes in one of the triggeringnodes:• ROOT• STOP• ITEM_TR• EXECUTIONINFORMATION• CC_CHG_TR

If a freight unit is changed the TRQ context is determined. For allfreight unit inside the same TRQ context the field FORCE_CHACOof node CC_CHG_TR is set to ‚X‘=> ChaCo then also runs for these freight units although they havenot been changed „directly“

• Determination DET_CALL_CHACO is called on BEFORE_SAVE• Action FILL_TRANS_CHANGEINFO is called

• Date and Location changes get determined (including evaluation ofdate tolerance condition)• Quantity changes get determined (with quantity tolerance condition)• New execution events get determined• node CC_CHG_TR is filled with the info about the identified changes• custom enhancements can be used

Fields to classify quantity, date and location changes

Fields for changes in TRQ-Context

Fields for event key and event code

Fields for details for quantity changes

Helper fields to trigger ChaCo processing / validation

Include Structure for node enhancements

• ChaCo related customizing is evaluated• If maintained to the TOR type the change strategy determinationstrategy gets evaluated• If no condition is assigned or condition delivers no result, the defaultchange strategy is taken (default change strategy is only executed incase any change has been determined in CC_CHG_TR)• All keys from the changes TORs are grouped by the found strategytogether with the identified changes in CC_CHG_TR

• Data Access Definitions are delivered in the standard for all the fields ofnode CC_CHG_TR

• Decision table to find change strategy can easily be based on these fields

In case of quantity change the change strategy START_TEND isfoundIn case of event DELAY the change strategy Z_ALERT isfound

• in case the found change strategy has service type TOR_CHACOS, it isprocesses synchronously by FM /SCMTMS/TOR_PROC_CHACO_STRAT• Synchronous Processing of change strategies should always be used carefully,since the BOPF DET-VAL-Cycle is not executed anymore then for the changedmade in the strategies

• strategies of service TOR_CHACO are registered for asynchronous processing• strategies of service TOR_CHACO are registered for asynchronous processing• determination DET_TRIGGER_STRATEGIES is called AFTER_COMMIT• here all previously determined change strategies are processed in FM/SCMTMS/TOR_PROC_STRAT_ASYNC by STARTING NEW TASK• Asynchronous Processing is necessary because the BOPF DET-VAL-Cycle hasto run after possible changes done by change strategy to this instance or to otherinstances

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

The BAdI /SCMTMS/TOR_CHACO_CHANGES_DETis provided to enhance the standard logic to identify TOR changes:• DET_DATE_AND_LOC_CHANGES

standard logic to identify and classify date and location changes can either beenhanced or substituted

• DET_QUANTITY_CHANGESstandard logic to identify and classify quantity changes can either be enhancedor substituted

• DET_CUSTOM_CHANGEScustom changes can be determined and stored in custom fields of transient nodeCC_CHG_TR; node can be enhanced by using dummy includeEEW_TOR_CCCHG

• Custom Data Access Definitions to provide the custom fields ofnode CC_CHG_TR to the ChaCo related conditions to

• determine date tolerances• determine quantity tolerance• find a change strategy

• Custom strategy methods of service type TOR_CHACO (orTOR_CHACOS)

• Custom strategies of service type TOR_CHACO (orTOR_CHACOS)

Delivered and custom strategy methods can be combined in newstrategies

• Strategy method CHACOALERT (/SCMTMS/CL_CHACO_METHODS=>CHACO_CREATE_ALERT) can be used to raise alerts out of a changestrategy

• Internal table MT_ALERT_CAT_KEYS_MESS of the ChaCo requestobject has to be filled with the TOR keys per alert category and relatedmessages

• Alert is then raised for each alert category and filled with the relatedTOR Ids and message texts

• Example:strategy method TOR_DELAY

(/SCMTMS/CL_CHACO_METHODS=>HANDLE_DELAY_FROM_EXECUTION)

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

In the TOR Type Customizing also three additional strategies can bemaintained

Creation and Save Strategy are also processed either asynchronously(service tpyes TOR_SAVE & TOR_CREATE) or synchronously(TOR_SAVE_S & TOR_CREA_S):

Synchronous: Processing in det. DET_TRIGGER_STRAT(BEFORE_SAVE)Asynchronous: Registration in det. DET_TRIGGER_STRAT(BEFORE_SAVE)Asynchronous: Processing via STARTING NEW TASK for FM/SCMTMS/TOR_PROC_CHACO_STRAT(DET_TRIGGER_STRAT at AFTER COMMIT)

Deletion Strategy is processed synchronously:Strategy is called inside of action CANCEL via FM/SCMTMS/TOR_PROC_DEL_STRATEGY

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

• The processing of a save strategy cannot trigger the execution ofanother change or save strategy for the same TOR object.

• The processing of a change strategy cannot trigger the execution ofanother change strategy for the same TOR. A new save strategy canbe triggered.

• In case a change or a save strategy do changes on a different TORnew strategies (change and save) can be triggered

Agenda


2. Customizing

3. ChaCo Close-Up




7. Related Notes

Important related notes are the following:

• 1666523: Introduction of synchronous strategy processing

• 1674629: Consulting note regarding asynchronous and synchronousprocessing of strategies

• 1742287: Introduction of cascading strategy execution

• 1742182: Changes done by strategy processing may get lost

• 1749898: Condition Support for Changed Nodes / Fields

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 hereinmay 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.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.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.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 theexpress 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/ordevelopment. 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 otheritems 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 ofmerchantability, 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 thesematerials. 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 linkscontained 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.

© 2012 SAP AG. All Rights Reserved

tm change controller · 2017. 2. 23. · change controller concept 2. customizing 3. chaco close-up...

Documents