Limit Management - Workflow

Download as pdf or txt
Download as pdf or txt
You are on page 1of 8

Start of Workflow

when Limit is
Breached

SAP AG

©SAP AG 2005

© SAP AG 1
Business Background

Usage

Customizing

©SAP AG 2005

© SAP AG 2
Reason for Workflow for Limit Management

When a dealer breaches a limit not only the dealer but


also another person should be informed about this
within a short time
„ For example the dealer‘s manager should be informed
immediately of the breach

This is to avoid that the dealer builds up too big a


position that will only be discovered at the end-of-day
run when all limits are recalculated

© SAP AG 2005

© SAP AG 3
Business Background

Usage

Customizing

©SAP AG 2005

© SAP AG 4
Example of Workflow when limit is breached

© SAP AG 2005

© SAP AG 5
Business Background

Usage

Customizing

©SAP AG 2005

© SAP AG 6
Customizing
To activate the workflow you must set the flag
„Workflow is active“ in the global settings.
The start of workflow is only supported with
the on-line limit check.

In the basic settings under assignments you


have to maintain the sender and recipients.
Alternatively the assignment can be taken
from the organigram.

© SAP AG 2005

„ In Global Settings in Credit Risk Analyzer you can activate the workflow for CRA or not. It is not possible
to activate per company code.
„ Under Assignments you have to maintain a list of senders and receipts of workflow.
„ The workflow is only started when the on-line limit check is activated. It is not started as part of the end-
of-day process.

© SAP AG 7
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 are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

„ The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
„ This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
„ SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
„ The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

© SAP AG 2005

© SAP AG 8

You might also like