portfolio assignment and transfer

20
©SAP AG 2005 Portfolio Assignment and Transfer Incentive & Commission Management October 2005

Upload: micoelho

Post on 21-Apr-2017

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Portfolio Assignment and Transfer

©SAP AG 2005

Portfolio Assignment and Transfer

Incentive & Commission ManagementOctober 2005

Page 2: Portfolio Assignment and Transfer

©SAP AG 2005

Portfolio Assignment & Transfer: IntroductionPortfolio Assignment & Transfer: SolutionPortfolio Assignment & Transfer: Integration

Page 3: Portfolio Assignment and Transfer

© SAP AG 2005

‘Portfolio’

Motivation

Entities of business objects are usually managed in a single, specific system

Examples:

Manageslifecycle

Policy# 1

Policy# 2

Policy# 3

CommissionsManagement

System

Manageslifecycle Comm.

Contract# 2

Comm.Contract

# 1

PolicyManagement

System

Page 4: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Often, entities of business objects are linked to each other via logical relationships

Examples:

Policy# 1

Policy# 2

Policy# 3

Comm.Contract

# 2

Comm.Contract

# 1

Manager for customer relationshipsRecipient for follow-up commission

Page 5: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Relationships between the entities of business objects are not static; they may be in a constant state of change

Policy# 1

Policy# 2

Policy# 3

Comm.Contract

# 2

Comm.Contract

# 1

Manager for customer relationshipsRecipient for follow-up commission

Page 6: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Relationships may be evaluated by different systems. Consequently, questions arise about ownership or the management of objects and their relationships.

Policy# 1

Policy# 2

Policy# 3

Comm.Contract

# 2

Comm.Contract

# 1

CommissionsManagement

System

Manageslifecycle Comm.

Contract# 2

Comm.Contract

# 1

PolicyManagement

System

Manageslifecycle

Uses formailingaction Uses for

remunerationentitlements

Managed by?

Manager for customer relationships

Page 7: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Example:

Grouping of insurance policies by regional aspects

An agent is then responsible for all insurance policies for a given region

Segmentation

Entities of business objects are often grouped together logically by various attributes The result is referred to as “segmentation”

Page 8: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Segmentation

Policy# 1

Policy# 2

Policy# 3

Comm.Contract

# 2

Comm.Contract

# 1

RegionalSegments

Detroit

L.A.

Regional manager for customer relationshipsbelongs to region

Page 9: Portfolio Assignment and Transfer

© SAP AG 2005

Motivation

Requirements

Integrate into a heterogeneous system landscape

Handle any type of business object

Allow any type of relationship between these objects

Manage relationships between objects

Provide grouping mechanisms

Provide functions for import and export

Page 10: Portfolio Assignment and Transfer

©SAP AG 2005

Portfolio Assignment & Transfer: IntroductionPortfolio Assignment & Transfer: SolutionPortfolio Assignment & Transfer: Integration

Page 11: Portfolio Assignment and Transfer

© SAP AG 2005

Engineering Response

Meet the requirements

Generic RFC functions provide full integration for import and export issues

Provide functions for import and export

Segments provide options for grouping mechanisms

Provide grouping mechanisms

Portfolio assignment provides an expandable set of administrative functions

Manage relationships between objects

Object types and roles for relationships can be designed / constructed by customers

Handle any type of business object or relationship between these objects

Portfolio assignment is designed as a distinct system

Integrate into a heterogeneous system landscape

Page 12: Portfolio Assignment and Transfer

© SAP AG 2005

System Positioning

Portfolio assignment is designed as a distinct system with import and export functions

System(CommissionsManagement)

System(Policy

Management)

System(...)

System(...)

PortfolioAssignment

Page 13: Portfolio Assignment and Transfer

© SAP AG 2005

Architecture / Design

Model

Customizing

SegmentTypes

Roles ObjectTypes

Combinat-ions

AssignmtObject

Segment

BusinessObject

AssObjAssignmt

BusObjAssignmt

Con

trol

ele

men

ts

Portfolio Assignment

Page 14: Portfolio Assignment and Transfer

© SAP AG 2005

Configuration

Page 15: Portfolio Assignment and Transfer

© SAP AG 2005

Basic Principles and Features

Fully integrated with FS-CS and FS-PM, without being part of it

Can be connected to any external system

Manages relationships, not objects

Provides full versioning of relationships

Allows the enhancement of data structures of relationships and objects by customer attributes

Provides an infrastructure using exit technology to complement standard administration methods

Portfolio Assignment

Page 16: Portfolio Assignment and Transfer

© SAP AG 2005

Mass Input

How do you import huge data volumes into portfolio assignment?

Like FS-CS, portfolio assignment offers a mass input interface using SAP’s EDT tool (electronic data transfer) to support activities such as migration or mass updates

PolicyManagement

System

PortfolioAssignment

EDT(PFO)

Flat fileGenericimportmodule

The generic EDT interface allows you to import mass data of different types in a single flat file

Page 17: Portfolio Assignment and Transfer

©SAP AG 2005

Portfolio Assignment & Transfer: IntroductionPortfolio Assignment & Transfer: SolutionPortfolio Assignment & Transfer: Integration

Page 18: Portfolio Assignment and Transfer

© SAP AG 2005

Integration with FS-PM

Portfolio Assignment provides a set of pre-configuration settings to handle FS-PM objects

FS-PM(Policy

ManagementSystem)

PortfolioAssignment

Create, update, deleteobjects and relations,

provide details*

Provide information aboutexisting objects and relations

*Planned for FS-PM release 3.0

Page 19: Portfolio Assignment and Transfer

© SAP AG 2005

Integration with FS-CS

FS-CS is linked to Portfolio Assignment through various functions and pre-configurations

FS-CS(Commissions

Management System)

PortfolioAssignment

(PFO)Commission CaseProcessing

Build participation in commissioncase using PFO data

Target Agreements Get target values using PFO data

Segment Assignment (SZO) Provide segment info to PFO

Commission Contracts Represent contracts as objects in PFO

Page 20: Portfolio Assignment and Transfer

© SAP AG 2005

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.