Social Services RCRM20

SAP Social Services Management for
Public Sector
Workshop RCRM20: "SAP Social Services Management for Public Sector,

Detailed Overview"
Agenda
1. Introduction
2. Application Management
3. Benefit Decision
4. Net Calculation
5. Payment Execution
6. Follow up Benefit Decision
7. Deduction Decision
8. Case Assignment
9. Additional CRM Capabilities
10. Customizing
11. Appendix
SAP 2010 / Page 2
Agenda
1. Introduction
1.
2.
3.
SAP 2010 / Page 3
Social Services Strategy

SAP Solution Social Care Management
SAP Solution Social Security
Key trends driving change in Social Services

Balancing service responsiveness and optimizing resources to maximize social value
Increasing
Constituent
Expectations
Increased need for

services due to
economic
environment
Holistic service
needs of the client
across programs
Demand for high
service level with
multi-channel
access - One stop
government
SAP 2010 / Page 4
Greater Budgetary
Pressures
Demographic / Cultural
Changes
Increased benefits
payments e.g.
unemployment
Increasing life
expectancy
Retiring workforce
Rising pension
costs
Increasing complex
family groupings
Reduced revenues
Less discretionary
spending
Increasing number
of child abuse cases
Lower or nonexistent pensions

due to no job for
life
Better control on
benefit
expenditures
Pressing Need to
Optimize Resources
Collaborate across
organizations to
share resources
and avoid
duplication of
efforts
Improve
operational
efficiency while
minimizing impact
on social service
delivery
Demands for
Accountability and
Transparency
Need to reduce
fraud, waste and
abuse
Provide
measurable
outcomes
Greater
accountability for
expenditures
Improve
performance of
social agency
There are two Social Services segments

Social Care
Social Security
Homecare
Benefit Payments
Residential Care
Veteran Payments
Foster Care
Medical Assistance
Adoption
Unemployment
Child Protection
Pensions
Youth Justice
Workers Comp
Adult Protection
Child Benefits
Drug Action
Disability Benefits
Mental Health
Income Support
Learning Disability
Housing Benefits
Physical Disability
Meals On Wheels
Reablement

Services and cash assistance provided by a government, which provide for the general
welfare and basic living requirements of individuals or families." Gartner 2007
SAP 2010 / Page 5
SAP solution for Social Service Agencies
SAP offers a comprehensive

software suite for Social
Service Agencies
Front Office / Back

Office
Transaction / Analytics
Customer Interaction /
Case Processing
Extensible / Rule
Management
SAP Front Office
SAP for Social Services & Social Security
Multi-Channel
Access
(Monetary Benefits Income Assistance)
Service
Centers
Social Security
Application
Processing
Eligibility
Determination
Benefit
Decision
Social Services / Care

(non-monetary Services)
Referral /
Intake
Assessment
Care
Planning
Service
Delivery
Collection / Contribution Management
Citizens &
Businesses
Registration
Online /
Web
Returns
Filling
Collection &
Disbursement
Financial
Customer
Care
Mass Payment Services
Case Management
Analytics for Social Services
Call
Center
SAP 2009 / Page 6
Benefit
Payment
SAP solution for Social Service Agencies

Customer Interaction
SAP Business
Communication Management
provides integrated channel
management
IP Telephony, Fax, Mail,

Chat, IVR
SAP for Social Services & Social

Security
Social Security
Multi-Channel
Access
Service
Centers
Application
Processing
Call
Center
Referral /
Intake
Online
/ Web
SAP 2009 / Page 7
Benefit
Payment
Assessment
Care
Planning
Service
Delivery
Registration
SAP Customer Interaction

Management provides
integration between Channel
and Process Management
using CRM Interaction
Center
Benefit
Decision

Citizens &
Businesses
Eligibility
Determination
Returns
Filling
Collection &
Disbursement
Financial
Customer
Care
Case Management
SAP Enterprise Portal

provides web content
management and
collaboration capabilities
SAP Front Office
Not all positioned customers are

formal Reference Customers
Social Services & Social Security

Social Security
Eligibility
Determination
Application
Processing
Benefit
Decision
Benefit
Payment
Caisse Nationale dAssurance Vieillesse
Referral /
Intake
Assessment
Care
Planning
Service
Delivery

Registration
Returns
Filling
Collection &
Disbursement
Financial
Customer
Care
SAP 2009 / Page 8
Istituto Nazionale Previdenza Sociale

Social Security
Eligibility
Determination
Application
Processing
Benefit
Decision
Benefit
Payment
Florida Department of Revenue, US
Referral /
Intake
Assessment
Care
Planning
Service
Delivery

Registration
Returns
Filling
Collection &
Disbursement
SAP 2009 / Page 9
Financial
Customer
Care
Ministry of Finance, Costa Rica

Social Security
Eligibility
Determination
Application
Processing
Benefit
Decision
Benefit
Payment
Referral /
Intake
Assessment
Care
Planning
Service
Delivery

Registration
Returns
Filling
Collection &
Disbursement
Financial
Customer
Care
This presentation and SAPs strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. 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 2009 / Page 10

Social Security
Eligibility
Determination
Application
Processing
Benefit
Decision
Benefit
Payment
Referral /
Intake
Assessment
Care
Planning
Service
Delivery

Registration
Returns
Filling
Collection &
Disbursement
SAP 2009 / Page 11
Financial
Customer
Care
Michigan DHS/DCH

Social Security
Q4 2010
Social Security
Eligibility
Determination
Application
Processing
Benefit
Decision
Benefit
Payment
Referral /
Intake
Assessment
Care
Planning
Service
Delivery

Registration
Returns
Filling
Collection &
Disbursement
SAP 2009 / Page 12
Financial
Customer
Care
98 Cities
More than 70 programs
including
Pension & Unemployment
15 programs
including
Pension & Unemployment
Agenda
1.
Introduction
1.
2.
3.

SAP Solution Social Care Management
SAP Solution Social Security
SAP AG 2009. All rights reserved. / Page 13
Customer
What is Social Care?
Looked After Children

Fostering
Adoption
Children in public care, who are
placed with foster carers, in
residential homes or with parents or
other relatives.
Child Protection
Protecting children from violence,
exploitation and abuse is an integral
component of protecting their rights to
survival, growth and development.
SAP 2010 / Page 14
Social care may be defined as a wide

range of services provided by local
authorities and the independent
sector to Child, Youth , Adults,
Elderly people either in their own
homes or in a care home.
Mental, Physical, Learning Disability

People have experienced a loss of function or
part of the body leading to impairment, but they
are disabled as a result of the limitation of
opportunities to take part in the everyday life on
an equal basis with others, due to economic,
environmental and social barriers"...
Community Based / Home Care

Services offer practical help and support
to people at home with essential daily
tasks they are unable to manage safely
for themselves.
Residential Care
For people who can not continue living in
their own home, even with support from
home care services. You can stay in
residential care for a short time, over a longer
period or permanently.
High Level Process Overview

Social Care Management
2
1
Identification of
client need
Contact Social
Services department
3
Assessment
Social Care
Management
4
Formulate Care
Plan
6
Time based Review
5 Implementation of
Care Plan
SAP 2010 / Page 15
Agenda
1. Introduction
2. SAP Solution Social Care Management
3. SAP Solution Social Security
1. SAP Social Services Management Overview
2. Demo
3. Process & Software View
1.
SAP 2010 / Page 16
What is Social Security?
Old age, and Survivors

Systems providing financial security
for the elderly are under increasing
strain throughout the world. In many
countries, populations are ageing
rapidly due to rising life expectancy
and declining fertility rates.
Unemployment
New forms of work and work patterns have
emerged over the past decades that challenge
the relationship between labour markets and
social security. These developments are
having a significant impact at various levels.
Family Allowance
Children account for nearly one-half of
the world's population; and over half of
them are in poor countries. One person
in five worldwide is a child in poverty.
Social security may be defined as any

program of social protection
established by legislation, or any
other mandatory arrangement, that
provides individuals with a degree
of income security when faced with
the contingencies of old age,
survivorship, incapacity, disability,
unemployment or rearing children.
Work Injury
During the last two decades, disability benefit
payments increased significantly in most of
the industrialized countries, although the rate
of this growth has declined over time. This
has occurred despite increased efforts to
prevent disabilities and a clear long-term
improvement in physical work conditions
SAP 2010 / Page 17
Maternity Leave and Sickness

Sickness benefit programs are generally of two types:
cash sickness benefits, which are paid when short term
illnesses prevent work,
and health care benefits, which are provided in the form
of medical, hospital, and pharmaceutical benefits
Solution Overview
SAP Social Services Management
End to end solution allowing monetary benefit allocations with BS i2010e
2
Collection
Management
Person
Management
3
Eligibility
Determination
Application
Management
4
Entitlement /
Gross Payment
Determination
SAP Social Security
- Social Case 5
Benefit Program
Rule Based
7
Financial / Payment
Management
SAP 2010 / Page 18
Change of
Circumstances
6
Overpayment / Deduction
Management
OVERVIEW TAX PROCESSING

SAP Tax & Revenue Management - Solution overview
Taxpayer
Online Services
SAP CRM
SAP ERP
Enterprise Portal
Registration
e-Filing
Returns Processing
e-Payment
Receivables & Payables Management
Activities
Overview
Revenue Accounting
Account
Information
Collections Management
Public Sector Collection & Disbursement
Enterprise Extension Public Sector
Financials
Controlling
Case/Records
Management
Documents
SAP IPS520 Overview Tax Processing / Page 19
Financial
Customer Care
Audit Case
Bankruptcy
Case
Budget
Rules Engine
Workflow
SAP NetWeaver
Business
Intelligence
Tax Estimation
Tax Analysis
Solution Overview
End to end solution allowing monetary benefit allocations with BS i2010e
2
Person
Management
Current
1
Delivered BS i2010e
Delivered BS i2011
3
Eligibility
Determination
Application
Management
4
Entitlement /
Gross Payment
Determination
SAP Social Security
- Social Case 5
Benefit Program
Rule Based
Change of
Circumstances
7
Financial / Payment
Management
6
Management
confidential
Solution Overview
Data Management
Call Center
Case
Management
Online
Services
2
Person
Management
3
Eligibility
Determination
Social Application
Management
Rules
Management
Third
Parties
Case
Worker
Benefit Program
Rule Based
Entitlement /
Gross Payment
Determination
Document / Records
Management
Family
SAP Social Security

7
5
Change of
Circumstances
6
Financial / Payment
Management
Management
Business Intelligence
Performance
Management
Authorization
Management
Accounting / Budget
Management
SAP 2010 / Page 21
Organization / Workload
Management
SAP Solution Architecture: Technical Positioning

of Monetary Benefits Scenario
The Monetary Benefits scenario combines a front office social decision making
processes with an automated back-office solution to execute financial. The solution
leverages key functionalities of the Social Case Management component in SAP
CRM and the Public Sector Collection and Disbursement (PSCD) component in SAP
ERP.
Client
request
Determine
entitlements
for benefits
Calculate
payments
Execute
payment and
manage
account
CRM
Social Case
Management
SAP 2010 / Page 22
Financial
Management
Agenda
1. Introduction
2. Demo
1.
SAP 2010 / Page 23
Agenda
1. Introduction
2. Demo
1.
SAP 2010 / Page 24
SAP Social Services Solution / Monetary Benefits

Process & Software View
Customer & Partner Interaction Management
Social Benefit Management
Payment Management
Social Claims Management

Social Deduction Management
Industry Specific Functions
Social Service Management
Net Calculation
Cross-Industry Functions
Interaction Management
Case Management
Payments
Activity Management
Document Management
Business Partner Management
SAP CRM
SAP ERP
User Interaction
Business Intelligence
Business Rules Framework
Service Bus
Application Lifecycle Management
SOA Management
Application Platform Services

SAP NetWeaver
SAP 2010 / Page 25


Route Request
Identify
Customer
Understand
Request
Manage
Request
Finalize
Request

Submit
Application
Manage
Application
Payment Management
Establish
Decision
Determine
Entitlement
Calculate
Entitlement
Determine
Gross Payment
Approve
Claims Management
Receive
Claim
Determine
Liability
Approve
Deduction Management
Receive
Liability
SAP 2010 / Page 26
Determine
Deduction
Approve
Calculate
Net Payment
Execute
Payment

Route Request
Identify
Customer
Understand
Request
Manage
Request
Finalize
Request

Submit
Application
Manage
Application
Establish
Decision
Determine
Entitlement
Payment Management
Calculate
Entitlement
Determine
Gross Payment
Approve
Claims Management
Receive
Claim
Determine
Liability
Calculate
Net Payment
Approve
Receive
Liability
Social Service Management

Interaction Management
Determine
Deduction
Approve
Calculation (Entitlement,Gross, Net)

Payments
Case, Activity & Document Management
SAP 2010 / Page 27
Business Rules Management
Business Rules Management
SAP CRM
SAP ERP
Execute
Payment
SAP Social Services Solution / Benefit Decision

Submit
Application
Manage
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Receive
Liability
Caseworker
Application
Form
XML
SAP 2010 / Page 28
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Application Management
Progr
am
Receive
Liability
Payment Management
Determine
Gross Payment
Determine
Deduction
BRF
plus
Social
Application
Caseworker
Application
Form
XML
Progr
am
BRF
plus
Interactions
Case
SAP 2010 / Page 29
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application

Determine
Calculate
Entitlement
Entitlement
Manage
Application
Progr
am
Payment Management
Establish
Decision
Receive
Liability
Determine
Gross Payment
Determine
Deduction
BRF
plus
Social
Application
Caseworker
Application
Form
XML
Progr
am
Interactions
Social Service Plan
BRF
plus
Progr
am
BRF
plus
Case
SAP 2010 / Page 30
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application
Manage
Application
Determine
Entitlement
Establish
Decision
Progr
am
BRF
plus
Application
Form
XML
Progr
am
Interactions
Calculate
Entitlement
Determine
Gross Payment
Receive
Liability
Determine
Deduction
Progr
am
Social
Application
Caseworker
Payment Management
BRF
plus
Social Service Plan
BRF
plus
Progr
am
BRF
plus
Case
SAP 2010 / Page 31
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application

Calculate
Establish
Determine
Entitlement
Decision
Entitlement
Manage
Application
Progr
am
Receive
Liability
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
XML
Progr
am
Payment Management
Determine
Gross Payment
Determine
Deduction
BRF
plus
Social Service Plan
BRF
plus
Progr
am
Interactions
BRF
plus
Case
Progr
am
SAP 2010 / Page 32
BRF
plus
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Progr
am
Receive
Liability
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
XML
Progr
am
Determine
Gross
Payment
Determine
Deduction
BRF
plus
Social Service Plan
BRF
plus
Progr
am
Interactions
BRF
plus
Case
Progr
am
SAP 2010 / Page 33
BRF
plus
Payment Management
Approve
Calculate
Net Payment
Approve
Execute
Payment

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Progr
am
Receive
Liability
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Calculate
Net
Payment
Execute
Payment
Approve
BRF
plus
Approval
XML
Progr
am
Social Service Plan
BRF
plus
Progr
am
Interactions
BRF
plus
Case
Progr
am
SAP 2010 / Page 34
BRF
plus
Net Calculation

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Receive
Liability
Progr
am
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Execute
Payment
Calculate
Net Payment
Approve
BRF
plus
Approval
XML
Progr
am
Social Service Plan
BRF
plus
Progr
am
Interactions
BRF
plus
Case
Progr
am
Payment
SAP 2010 / Page 35
Payment Execution in PSCD
BRF
plus
Net Calculation
SAP Social Services Solution / Monetary Benefit

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Progr
am
Approve
Calculate
Net Payment
Determine
Deduction
Execute
Payment
Approve
Benefit / Deduction Decision
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
BRF
plus
Approval
XML
Progr
am
Social Service Plan
BRF
plus
Progr
am
Interactions
Progr
am
Payment
SAP 2010 / Page 36
Determine
Gross Payment
Receive
Liability
Payment Management
BRF
plus
Social Deduction Plan

BRF
plus
Net Calculation
SAP Solution Architecture

Monetary Benefits Scenario Component Diagram
UI
Case
R
Case
Activities
Cases
Activities
Business
Partner
R
Application
Processing
BuPa
SOA
Decision Making Process
Customer Defined
Trigger Processes
SSP
CRM
Simulation
Mass
(re)calculation
R
Gross Entitlement
Calculation
Gross Payment Calculation

(incl. Over / Underpayment calc.)
Activities
Decision
Making
Process
Gross
Entitlement
Amounts
Net Calculation
Color Legend
Objects not affected
by this project
Net
Calculation
Result
Objects partialy affected

by this project
R
Billing
Gross
Entitlement
Calculation
Fi- CA
Invoicing
Billing run
4S Billing & Deduction Engine

-
Objects new developed

within this project
Objects within development in
other projects optionaly
under consideration of this
project
ERP
Billing
Documents
Fi- CA Invoicing
FI-CA
postings
SAP 2010 / Page 37
Gross
Payment
Items
Invoices
Invoicing run
ERP
Worker
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 38
Social Application Making Process

Submit
Application
Manage
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Receive
Liability
Social Application
Making Process
SAP 2010 / Page 39
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Calculate
Net Payment
Approve
Execute
Payment

Social Application
SAP 2010 / Page 40
Social Application
Making Process
Incoming
Application
SAP 2010 / Page 41
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Approval
Service
Plan
Assignment

Incoming Application
Incoming
Application
Validation
Case Worker
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment
At the beginning, the

application data
comes in
based on SAP CRM
Web request
technology either
via a Web form or
via XML
Paper Application
XML Application
SAP 2010 / Page 42

Validation
Incoming
Application
Validation
Case
Assignment
During the validation step,

the application form is
checked for correctness
You are able to check:
Mandatory fields
Field formats
Dependencies between
fields (e.g. via rules
framework)

SAP 2010 / Page 43
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment

Case Assignment
Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
With the case assignment step, the new application is assigned to a

new or existing case
You are able to:
Decide if case assignment
should be mandatory
Search for cases in
various ways
(e.g. via rules framework)
Set up a case creation
procedure
Assign a case
manually/automatically
Define relevant partners
for the case
SAP 2010 / Page 44
Maternity Leave
Service Plan
Approval
Assignment

Benefit Selection
Incoming
Application
Validation
Case
Assignment
Benefit
Selection
Eligibility
Check
Assessment
Approval
With the benefit selection step, benefits are determined and assigned.
This could be done
either automatically via the rules engine
(e.g. based on the data in the application form)
and/ or manually by the case worker
SAP 2010 / Page 45
Service Plan
Approval
Assignment

Eligibility Check
Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
With the eligibility check, the system checks if the citizen is eligible for the benefits in a specific period.
This check could be performed according to rules specified in the rules engine.
The eligibility check can be
automatic
(e.g. after a data change)
manually triggered by the
case worker
overruled by the
case worker
The result is displayed as a
status (eligible/ not eligible)
SAP 2010 / Page 46
Service Plan
Approval
Assignment

Assessment
Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
With assessment, an overall judgment on each benefit of a social

application is made.
Typically, it documents the
caseworkers decision
based on current
case information
System can propose a
decision to support the
case worker
System proposal should
support, but not replace
caseworkers decision
The result is displayed
as a status
SAP 2010 / Page 47
Service Plan
Approval
Assignment

Approval
Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
The approval step states the confirmation of / agreement to an

application.
Typically, it documents the
case workers confirmation
that all application data
is valid.
Rules-based approval
checks can be implemented
to support the case worker
Can also be automated
Authorization checks
SAP 2010 / Page 48
Service Plan
Approval
Assignment

Social Service Plan Assignment
Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment
With social service plan assignment, the application is assigned on a rule basis to
an existing social service plan (SSP). The SSP represents the contractual agreement
between citizen and authority (e.g. municipality).
The assignment could also de done manually by the case worker
If no suitable service plan is found, a new one is created
SAP 2010 / Page 49

Incoming
Application
SAP 2010 / Page 50
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment

SocialService Plan Assignment
Incoming
Application
Action
to start successor
processing
Case
Assignment
Validation
Action
Profile
Change Mode
Benefit
Selection.
Eligibility
Check
Assessment
Transaction type
for social application
Web Request Category
Approval
Service Plan
Approval
Assignment
SSP Assignment Profile

How is social service plan searched?
Service Plan Determination Types:
via BADI
via Rules Engine (BRF)
SSP of current case
Assignment mandatory: Yes / No
Creation Mode
Change Processing Profile
How is service plan changed?
Versioning:
New service plan version?
Partners be copied from old version?
Items status be copied from old
version?
New eligibility check / assessment?
Common settings:
How are..
a) item and
b) item status
copied from application?
New eligibility check?
New item assessment?
Successor Processing Profile

How is service plan created?
Transaction type of new service plan
Approval: Should checks and activation
start automatically?
Change Process Chain

Global Change Process
I.e. the last changes on the
service plan (e.g. at the end
approval shall start)
SAP 2010 / Page 51
i.e. sequence of changes on the service plan
= Assignment path
Change Processes
(e.g. termination of benefits)

Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment
1. Social application is approved (which starts successor processing via action)

2. System searches for an appropriate social service plan
3. System assigns the found service plan, otherwise creates a new service plan
4. System updates an existing service plan according to application data (optionally in a
new version)
5. Optionally: System starts automatically the approval process of the social service plan
6. System closes the social application (status: completed)
SAP 2010 / Page 52

Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment
Scenario: A mother expects her new child in September

1st SOA
1nd Application
Form
(expected
date of birth
1.9.)
(1st version)
Pregnancy leave
Maternity leave
Parental leavev
Preg. leave: 1.8.-1.9.

Mat. leave: 2.9.-8.12.
Par. leave: 9.12.-20.7.
SOA: Social Application

SSP: Social Service Plan
SUPR: Successor Processing
SAP 2010 / Page 53
SSP
Pregnancy leave
Maternity leave
Parental leave
SUPR

Mat. leave: 2.9.-8.12.
Par. leave: 9.12.-20.7.
Transfer:
Header data (dates etc.)
Items (with dates & eligibility and assessment status values)

Incoming
Application
Validation
Case
Assignment
Benefit
Selection.
Eligibility
Check
Assessment
Approval
Service Plan
Approval
Assignment
The baby was born. The date of birth varies from the expected date of birth.
1nd
Application
Form
(expected
date of birth
1.9.)
2nd Application
Form
(expected
date of birth
3.9.)
SAP 2010 / Page 54
1st SOA
SSP
(1st version)
Preg. leave
Mat. leave
Par. leave
new version
(copy all header &
item data)
SUPR
(2nd version)
Preg. leave
Mat. leave
Par. leave
Preg. leave
Mat. leave
Par. leave

Mat. leave: 4.9.-10.12.
Par. leave: 11.12.-22.7.
2nd SOA
(Preg. leave)
(Mat. leave)
(Par. leave)
SSP
Executes change
process Child is
born on new SSP
version to change
dates
SUPR
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 55
Agenda
3. Benefit Decision
Overview
2. SSP Creation
3. Eligibility Creation
4. Entitlement Determination
5. Entitlement Calculation
6. Manual Adjustment
7. Decision Assessment
8. Gross Payment Item Determination
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 56
What is Benefit Decision?

Benefit decision for social services is, the determination, the calculation and the approval of potential benefits that can be
received by a beneficiary and paid to a payment recipient.
???
1000
Authorities
Beneficiary
Citizen
200 / Month
Approved on
Payment Recipient
SAP 2010 / Page 57
Benefit Decision Making Process

Submit
Application
Manage
Application
Benefit Decision
Making Process
SAP 2010 / Page 58
Establish
Decision
Determine
Entitlement
Payment Management
Calculate
Entitlement
Determine
Gross Payment
Receive
Liability
Determine
Deduction
Approve
Calculate
Net Payment
Approve
Execute
Payment

Social Service Plan
SAP 2010 / Page 59
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Optional
Out of Scope
SOA
SSP
Previous Release
Can be only executed before
decision assessment
Can be only executed after
decision assessment
SAP 2010 / Page 60
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 61

SSP Creation / Establish Decision
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Already
Existing
SSP
Eligibility
Check
No
Entitlement
Determin.
New
SSP
Creation
Entitlement
Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Optional
Out of Scope
Yes
SSP
Version
Creation
Previous Release
decision assessment
decision assessment
SAP 2010 / Page 62

New SSP Creation / / Establish Decision
New SSP
Creation
Application
Decision
SSP
Creation
Already
Existing
SSP
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
New
SSP
Creation
No
Benefit
Program
Determination
Main
Partner
Determination
Case
Assignment
Decision
Period
Determination
SSP Header
Data
Determination
Eligibility
Determination
Yes
SSP
Version
Creation
Out of Scope
SAP 2010 / Page 63
Previous Release

decision assessment

decision assessment
New SSP Creation / Establish Decision

Caseworker Home Page
SAP 2009 / Page 64

Benefit Program Determination
SAP 2010 / Page 65

Decision Period, Date Management
SAP 2010 / Page 66

Date Management and Delivery Customizing
SAP 2010 / Page 67

Date Management and Delivery Customizing
SAP
SAP
20092010
/ Page
/ Page
68 68

Case Assignment Business Partner Data
SAP 2010 / Page 69

Case Assignment Customizing
SAP 2009
2010 / Page 70
New SSP Creation / Establish Decision Social

Assigned Case
SAP 2010 / Page 71

Other SSP Header Data
SAP
SAP
20092010
/ Page
/ Page
72 72
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 73
Eligibility Determination
SAP 2010 / Page 74
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 75

Entitlement Determination
Benefit Decision
Making Process
SSP
Creation
Application
Decision
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Benefit
Determin.
Manual
Adjustment
Entitlement
Period
Determin.
Decision
Assessment
Manual
Entitlement
Items
Retrieving
from
Previous
SSP (s)
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Entitlement
Item
Creation
Optional
Out of Scope
Decision Period
Previous Release
Benefit Program
Main Partner
SAP 2010 / Page 76
Previous
SSP (s)
Can be only executed

before decision assessment
decision assessment

SAP 2010 / Page 77

SAP 2010 / Page 78
Entitlement item in Detail
SAP 2010 / Page 79
SAP 2010 / Page 80
We do have three different kind of items within SSP

E
Items created out of entitlement determination
Read only Can be only accepted / rejected by the case worker (but no other
manual change is allowed)
SAP 2010 / Page 81
Manually created items
Adjustments items generated out of entitlement adjustment
Read only it is not possible to influence the items manually at all
Items are not considered by change processes at all
Item Proposal Profile Assignment
SAP 2010 / Page 82
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 83

Entitlement Calculation
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Manual
Adjustment
Data Collection
Entitlement
Items
Decision
Assessment
Period
Determination
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Calculation
Optional
Benefit
Entitlement Period
Beneficiary
Out of Scope
Previous Release
decision assessment
SAP 2010 / Page 84

SAP 2010 / Page 85
Architecture Overview
SAP 2010 / Page 86
Architecture Overview
ERP
Replicated
Data
Result
SXP
(SSP, SDP)
including
header, item,
partner,
appointment,
status,
customer
defined fields
Entitlement
Controller
Gross
Entitlement
Document
Item
(GED Item)
Business Partner
Business Partner
Relations
Product
SAP 2010 / Page 87
Gross
Entitlement
Document
(GED)
Calculation
Exit
(BRF+ / BAdI)
BRF+ Trace
Customizing
CRM / ERP Integration
CRM / ERP Integration
CRM and ERP: Configure the middleware replication

CRM: Configure the communication settings
ERP: Maintain basic Customizing for calculation and payment
Frequency types
Due date rule types
Mapping between due date rule types and frequencies
Payment families
Payment methods for outgoing payments
CRM: Synchronize the basic Customizing for calculation and payment
The ERP Customizing entries must be maintained manually or by means of synchronization
objects in the corresponding Customizing activities of CRM
CRM: Maintain transaction types and item categories (SSP types....)
Payment family
Due date rule for regular payment
Due date rule for underpayment
Entitlement frequency
ERP: Maintain the corresponding settings for transaction types and item categories
SAP 2010 / Page 88
Entitlement Frequency Customizing
On SAP ERP side you have to do the customizing for the

entitlement frequency which is the
smallest granularity in which calculation results are stored and
on which follow-up processes like recalculations can be
supported e.g. calculations are always done on a daily
basis
Just maintain a frequency type you need and

mark it as an possible entitlement frequency
SAP 2010 / Page 89
Entitlement calculation
Transaction type Customizing
On SAP CRM side you have then to assign your

entitlement frequency within the header customizing
of your transaction type
SAP 2010 / Page 90
Calculation Exit Strategy customizing
On SAP ERP you have a customizing activity to

maintai your Calculation Exit Strategies e.g.
to assign on SXP level

how/where you want to implement
your calculation rules. It is
possible to use a BAdI
implementation or to maintain
your rules within BRFplus.
For BRFplus you have to maintain

the BRFplus Application Name
and the corresponding BRFplus
Function Name. In addition you
could decide if the BRFplus Lean
Trace should be switched on i.e.
to log how/which rules have been
processed.
SAP 2010 / Page 91
Use the scroll bar to display:

- Application Name
- Function Name
Handling of manual items Customizing
SAP 2010 / Page 92
These gross entitlement amounts always are kept even if the implemented rules have
calculated a result for this item
These gross entitlement amounts are overwritten but a warning message is shown to the
caseworker
These gross entitlement amounts are just overwritten without any checks
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 93

Manual Adjustment
Benefit Decision
Making Process
SSP
Creation
Application
Decision
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Change on
SSP header
Data
Manual
Adjustment
Generated
Entitlement
Items
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Generated
Entitlement
Items
Update
Manual
Entitlement
Item
Creation
Approval
Manual
Assessment
Optional process step
Not possible
Optional
SAP 2010 / Page 94
Manual Adjustment
Header
SAP 2010 / Page 95
Manual Adjustment
Entitlement item
SAP 2010 / Page 96
Manual Adjustment
Generated Items
SAP 2010 / Page 97
Manual Adjustment
Manual Items
SAP 2010 / Page 98
Manual Adjustment
Manual Items in Detail
SAP 2010 / Page 99
Benefit Product
SAP 2010 / Page 100
Item Category Group
SAP 2010 / Page 101
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 102

Decision Assessment
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Optional
Out of Scope
Previous Release
decision assessment
decision assessment
SAP 2010 / Page 103

Decision Assessment
SAP 2010 / Page 104

Decision Assessment
Display mode
SAP 2010 / Page 105

Decision Assessment Customizing
SAP 2010 / Page 106
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 107

Gross Payment Item Determination
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Optional
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Entitlement
Items
Manual
Adjustment
Entitlement
amount
Decision
Assessment
Data Collection
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Split
Approval
Calculation
Out of Scope
Previous Release
decision assessment
SAP 2010 / Page 108
Beneficiary
Payment
recipient
Optional

GEDocument
GEHeader
Entitlement
Frequency
Payment
Frequency
Weekly
GEItem
Monthly
Due Dates
End of
Period
SSP
Benefit
Benefit Beneficiary
Payment Recipient
Entitlement Frequency Period
Reference Date
Due Date Rules
GPDocument
Gross
Payment Item
Determination
GPHeader
GPItem
GPDocument
GPHeader
GPItem
Reference Date
SAP 2010 / Page 109
Today
+3
days

First Decision not Retroactive
GEDocument
Entitlement
Frequency
GEHeader
GEItem
01/01 to 31/12 1000
Payment
Frequency
Weekly
Due Date
Monthly
GPDocument
Gross
Payment Item
Determination
GPHeader
GPItem
REG 01/01 to 28/02 4000
REG 01/03 31/03 5000

REG 01/04 to 30/04 4000
REG 01/01 to 31/01 1000
Reference Date
SAP 2010 / Page 110

First Decision partially Retroactive
GEDocument
Entitlement
Frequency
GEHeader
GEItem
01/01 to 31/12 1000
Payment
Frequency
Weekly
Due Date
Monthly
GPDocument
Gross
Payment Item
Determination
GPHeader
GPItem
UP
31/03
9000
REG 01/03 31/03 5000

REG 01/04 to 30/04 4000
REG 01/05 to 31/05 5000
Reference Date
SAP 2010 / Page 111

Second Decision partially Retroactive
GEDocument
Entitlement
Frequency
GEHeader
GEItem
01/01 to 31/12 1000
Payment
Frequency
Weekly
Due Date
01/01 to 31/12 1500
Monthly
GPDocument
Gross
Payment Item
Determination
GPHeader
GPItem
UP
GPDocument
31/03
4500
REG 01/03 31/03 7500
GPHeader
REG 01/04 to 30/04 6000

REG 01/05 to 31/05 7500
GPItem
01/01 to 28/01 9000
SAP 2010 / Page 112
Reference Date

First Decision partially Retroactive
GEDocument
Entitlement
Frequency
GEHeader
GEItem
01/01 to 31/12 1000
Payment
Frequency
Weekly
Due Date
01/01 to 31/12 800
Monthly
GPDocument
Gross
Payment Item
Determination
GPHeader
GPItem
OV
GPDocument
31/03
1800
REG 01/03 31/03 4000
GPHeader
REG 01/04 to 3200

REG 01/05 to 31/05 4000
GPItem
01/01 to 28/01 9000
SAP 2010 / Page 113
Reference Date
Basic Example:
Step 1: SSP and GED
GPCP
GED:
w9
GED Item3: 12.1. 17.1. 800 / w
w8
w1
GED Item1: 21.11. 23.11. 300 / w
w2
w3
GED Item2: 24.11. 11.1. 1000 / w
SSP:
SXP
21.11.08 17.1.09
Legend:
: 1 calender week
SXP Item1: 21.11. 17.1., Benefit: Maternity

Fr
21.11.
SAP 2010 / Page 114
1.12.2008
1.1.2009
Sa
17.1.
entitl.freq. : weekly
paym.freq. : monthly
Basic Example:
Step 2: Creation of GPIs
GED:
w5 1000 tdue = 11.12. ...
w6 1000 tdue = 11.12. ...
w7 1000 tdue = 11.12. ...
w9 800 tdue = 8.1.. ...
w4 1000 tdue = 11.12. ...

?
W3 1000 tdue = 11.12. ...

?
w8 1000 tdue = 8.1. ...
W2 1000 tdue = 13.11. ...

?
W1 300 tdue = 13.11. ...
GPI:
GPCP
w9
GED Item3: 12.1. 17.1. 800 / w
w8
w1
GED Item1: 21.11. 23.11. 300 / w
w2
w3
GED Item2: 24.11. 11.1. 1000 / w
SSP:
SXP
21.11.08 17.1.09
Legend:
efp
Fr
21.11.
SAP 2010 / Page 115
1.12.2008
1.1.2009
: 1 calender week
Sa
17.1.
Basic Example:
w9 800 tdue = 8.1.. ...

REG
w7 1000 tdue = 11.12. ...

REG
w8 1000 tdue = 8.1. ...
w6 1000 tdue = 11.12. ...

REG
REG
w5 1000 tdue = 11.12. ...

REG
REG w4 1000 tdue = 11.12. ...
W2 1000 tdue
= 13.11. ...
15.12.
UP
REG W3 1000 tdue = 11.12. ...
tdue = 13.11. ...

W1 300 15.12.
Because these 2 payments

are already due (with
respect to the reference
date) they get the process
category underpayment.
Please mention also that
the due date for those
items has been changed
(according to customizing
regarding due date rule for
underpayments)
UP
Step 3: Considering the Reference Date
w9
GED Item3: 12.1. 17.1. 800 / w
w8
w1
GED Item1: 21.11. 23.11. 300 / w
w2
w3
GED Item2: 24.11. 11.1. 1000 / w
SXP
21.11.08 17.1.09
Legend:
Fr
21.11.
SAP 2010 / Page 116
1.12.2008
tref = 6.12.
1.1.2009
: 1 calender week
Sa
17.1.
Example with Follow-Up-Decisions :

Retrocalculation & Delimitation
REG
ID A
1000
REG
ID B
1000
REG
ID C
1000
REG
ID D
1000
REG
ID E
1000
REG
ID F
1000
REG
ID G
1000
D1t
D2t+1
UP
ID I
200
REG
ID J
1200
UP
ID K
900
D3t+2
UP
ID L
9000
UP
ID M
700
UP
ID N
700
stopped_by
tref
stops
GED Item: Type A 1200 / w
General Rule for Stopping: previous

GPIs are stopped when they are not
already payed out/due !
stopped_by
UP
ID H
200
General Rule for Retrocalculation:

previous GPIs are "taken into account"
when they are already payed out/ due !
stops
GPCP
Overall Rule: previous GPIs belonging to

same EFP with the same benefit, payment
recipient, benefit beneficiary
stopped_by
stops
REG
ID O
1900
REG
ID P
1900
Legend:
: 1 calender week
tref
t
SAP 2010 / Page 117
Periods & Due Date Rules
Frequency Type Customizing
Dynamic Generation of Periods
Simple
Multiple
SAP 2010 / Page 118
Frequency Mappings
No Mapping
Category required
Mapping
Category required
(BAdI)
GPD 02.02.2009 - 08.03.2009

GPI 1
GPI 2
GPI 3
GPI 4
GPI 5
Payment Frequency Period 01.02.2009 28.02.2009

01.03.2009 31.03.2009
SAP 2010 / Page 119
Due Date Rules
DD05
DD04
15th Day of Month

respecting Factory
Calendar
CW 06
CW 07
Last Day of
Month respecting
Factory Calendar
DD06
CW 08
CW 09
CW 10
Last Day of Month -4

Days for Bank Transfer
ZD09
SAP 2010 / Page 120
Wednesday in
2nd Week of Next
Month
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 121

Net Display
Benefit Decision
Making Process
SSP
Creation
Application
Decision
Eligibility
Check
Entitlement Entitlement
Determin. Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Net
Calculation
Display
Approval
Net
Calculation
Display
On demand and optional

Optional
Out of Scope
Deduction
Making Process
Previous Release
decision assessment
SAP 2010 / Page 122

Net Display
SAP 2010 / Page 123
Agenda
3. Benefit Decision
Overview
2. SSP Creation
9. Net Simulation
10. Approval
1.
SAP 2010 / Page 124

Approval
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Deduction
Making
Process
Approval
Net
Calculation
Display
Optional
Out of Scope
Previous Release
decision assessment
SAP 2010 / Page 125

Approval
SAP 2010 / Page 126
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 127
Agenda
4. Net Calculation
1.Process
Overview
2.Architecture and Technical Details
3.Configuration
4.Example
SAP 2010 / Page 128

Net Calculation
Submit
Application
Manage
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Receive
Liability
Net Calculation
SAP 2010 / Page 129
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Calculate
Net Payment
Approve
Execute
Payment
Monetary Social Benefits Scenario

Major Components
CRM
Application
Processing
ERP
Benefit
Decision
Process
Social
Application
SAP 2010 / Page 130
Net
Calculation
Decision
Processing
ERP
Periodical
Billing
FI-CA
Invoicing
Payment
Run
Account
Maintenance
Deduction
Decision
Process
Social
Benefit /Deduction
Decision
Net
Calculation
Result
Billing
Document
Accounting
Document
(Open Item)
Payments
Clearings
Net Calculation
Purpose
Benefit Decision:
Each month
2000 Benefit
1700
Deduction Plan:
Each month
50 for water & electricity
Payment
Recipient
Net
Calculation
50
Utilities
Company
Tax Law
250
Tax Agency
SAP 2010 / Page 131
Net Calculation
Execute Net Calculation Run
SAP Menu (ERP) Accounting Public Sector Management Social Services Mass Processing Create Net
Calculation Documents
Application Log with

different level of
message details, can
be analyzed after run
SAP 2010 / Page 132
Net Calculation Process Logic
Basically the process of net calculation is split up into three major parts:
1. Grouping of gross payment document items to net calculation units by
Payment recipient
Payment family
Payment frequency type
Due date rule
2. Determination of rule based and decision based deductions

3. Limitation of prior created net calculation documents in case of a change of a
gross payment document or deduction document.
SAP 2010 / Page 133
Net Calculation Unit
Pension
SSP
Type 1
old age
pension
Maternity - Monthly Payments
SDP
Type 1
electricity
Payment Family 1
Frequency 1
monthly
Due Date 15th of
month
PSCD Contract Account Category

Pension
SAP 2010 / Page 134
SSP
Type 2
monthly
maternity
SDP Type
2
electricity
Payment Family 2
Frequency 1
monthly
Due Date end of
month
Maternity - Weekly Payments
SSP
Type 3
weekly
maternity
Payment Family 3
Frequency 2
weekly
Due Date beginning
of next week
PSCD Contract Account Category Maternity Benefits
Types of Deductions
We have to distinguish
Decision Based Deductions
Created manually by caseworker in CRM, not related to a single benefit

= applied to all gross payment document items
Examples: outstanding debts, rent
Rule Based Deductions
determined by a BAdI, based on certain benefits = subset of gross

payment document items
Examples: income tax, insurance
For all deduction types:

Deductions are either a fixed amount or a percentage.
Partial deductions are supported
Deductions are applied until deductible amount is 0
SAP 2010 / Page 135
Agenda
4. Net Calculation
1.Process
Overview
3.Configuration
4.Example
SAP 2010 / Page 136
Net Calculation in the Overall Architecture
SAP 2010 / Page 137
Process Overview Relationships within

document chain
SSP/SDP
n:m
SAP 2010 / Page 138
Involved Parts in Net Calculation
Prequisite
Data
Result
GPD
(including
Decision
Based
Deductions)
Deduction
Types
including
Deduction
Type Priority
Customizing
SAP 2010 / Page 139
Net Calculation
Controller
BAdI for
Determination
of Rule Based
Deductions
Net Calculation
Documents
(NCDs)
per
Payment Period /
Due Date
Net Calculation
Document
Item
(NCDITEM)
Net Calculation: NCD Header and Item Group
Benefit Decision:
Each month
2000 Benefit
./. 500 Deduction
./. 250 Taxation
-----------------------1250 Net Benefit
NCD Header GUID x

January
Net Calculation Run for

January to March
NCD Header GUID y

February
NCD Item Group 1
1.
2.
3.
SAP 2010 / Page 140
NCD Header GUID z

March
Benefit 2000
Deduction -500
Taxation -250
Net Calculation: Correction for a period
INVALID
NCD Header GUID
x
January
SAP 2010 / Page 141
NCD Header GUID y

February
NCD Header GUID z

March
NCD Header GUID

yy
February
NCD Item Group 1
NCD Item Group 2
1.
2.
3.
1.
2.
3.
Benefit 2000
Deduction -500
Taxation -250
Benefit 2100
Deduction -500
Taxation -250
How does a NCD Header look like?
NCD Header consists of:
Begin date of the payment period
End date of the payment period
Due Date
Payment Family
Payment Recipient
Due Date Rule
Status (Open, Billed, Revised, Cancelled, Reversed)
Billing Document Number
Reversal Billing Document Number
Additional customer defined fields
Working with NCD Headers:
SAP 2010 / Page 142
For each Due Date a separate NCD document header is created serving as input for
the Billing Process
How does a NCD Item look like?
NCD Item consists of:

Gross Payment or Deduction Plan Item
Amount
Currency
Benefit ID
Item Process Class (Regular or Underpayment)
Item Type (CRM)
Deduction Type
Deduction Plan Item Process Category (Third Party, Allocated Deduction, )
Deduct To Party
Customer defined fields
...
SAP 2010 / Page 143
Agenda
4. Net Calculation
1.Process
Overview
3.Configuration
4.Example
SAP 2010 / Page 144
Net Calculation
Customizing
Maintain Payment Family

IMG Public Sector Management Social Services Basic Settings Maintain Payment Families
Payment Family Description
Payment Frequency Type
Contact Account Category
Maintain Payment Parameters on SSP Type in CRM

IMG Customer Relationship Management Transactions Basic Settings Define Transaction
Types: Definition of transaction types Assignment of Business Transaction Categories
Customizing header
Technical Parameters for Net Calculation Run
IMG (ERP) Public Sector Management Social Services Net Calculation
Maintain Deduction Types
Maintain Ranking of Deduction Types
SAP 2010 / Page 145

SAP 2010 / Page 146
Maintain Payment Parameters on SSP in CRM

IMG Customer Relationship Management Transactions Basic Settings Define Transaction Types:
Definition of transaction types Assignment of Business Transaction Categories Customizing header
SAP 2010 / Page 147
SAP Menu (ERP) Accounting Public Sector Management Social

Services Mass Processing Analyze Initial Net Calculation
SAP 2010 / Page 148
SAP 2010 / Page 149
SAP 2010 / Page 150
Agenda
4. Net Calculation
1.Process
Overview
3.Configuration
4.Example
SAP 2010 / Page 151
Business Example for Net Calculation (1): Starting

Situation
Jan
09
Feb
09
Mar
09
Apr
09
May
09
500
500
500
500
500
GPD 1
Jun
09
Jul
09
Aug
09
Sep
09
Oct
09
Nov
09
Dec
09
500
500
500
500
500
500
500
GPD 1
Amount: 500 EUR for 01.01.2009 31.12.2009 = 1 to 12
GPD 2
900
900
900
900
SAP 2010 / Page 152
900
900
900
GPD 2
Amount: 900 EUR for 01.05.2009
31.12.2009 = 5 to 12
Net Calculation Unit Period

Relevant for Net
Calculation
900
Business Example for Net Calculation (2):

Additional GPIs are determined and added
GPD 1
Jan
09
Feb
09
Mar
09
Apr
09
May
09
500
500
500
500
500
Jun
09
Jul
09
Aug
09
Sep
09
Oct
09
Nov
09
Dec
09
500
500
500
500
500
500
500
GPD 1
Amount: 500 EUR for 01.01.2009 31.12.2009 = 1 to 12
600
GPD 1a
600
600
600
600
600
600
600
GPD 1a
Amount: Changed to 600 EUR
for 01.05.2009 31.12.2009
GPD 2
GPD 2a
900
900
900
900
900
900
900
900
GPD 2
Amount: 900 EUR for 01.05.2009
31.12.2009 = 5 to 12
GPD 2a, Item 1

1000
1000
1000
Amount changed to 1 000 EUR

for period 01.04.2009 30.06.2009
Amount changed to 0 EUR
for period 01.07.2009 30.09.2009
2000
2000
2000
GPD 2a, Item 2
Amount: 2 000 EUR for 01.07.2009
30.09.2009
Relevant for
Net Calculation
Not relevant, outside NCU Period
Not relevant, successor GPI

SAP 2010 / Page 153
Net Calculation Unit Period
Business Example for Net Calculation (3): Net

Calculation Document Item Groups and Headers
NCD Header 1
30.04.2009
NCD Item Group A
500 Euro Housing
900 Euro Cash Allowance
NCD Header 4
31.07.2009
NCD Item Group C
600 Euro Housing

2000 Euro Emergency
SAP 2010 / Page 154
NCD Header 2
31.05.2009
NCD Item Group B
600 Euro Housing
NCD Header 5
30.08.2009
NCD Item Group C
600 Euro Housing

2000 Euro Emergency
NCD Header 3
30.06.2009
NCD Item Group B

600 Euro Housing
NCD Header 6
30.09.2009
NCD Item Group C
600 Euro Housing

2000 Euro Emergency
Business Example for Net Calculation (4): Net

Calculation Documents with Deduction Items
NCD Header 1
30.04.2009
NCD Item Group A
500 Euro Housing
1400 Euro Gross
- 450 Eur Tax
NCD Header 4
31.07.2009
NCD Item Group C
600 Euro Housing
2000 Euro Emergency
2600 Euro Gross
- 450 Eur Tax
1820 remaining for
other deductions
- 200 Euro deduction
SAP 2010 / Page 155
NCD Header 2
31.05.2009
NCD Item Group B
600 Euro Housing
1500 Euro Gross
- 480 Eur Tax
NCD Header 5
30.08.2009
NCD Item Group C
600 Euro Housing
2000 Euro Emergency
2600 Euro Gross
- 450 Eur Tax
1820 remaining for
other deductions
NCD Header 3
30.06.2009
NCD Item Group B

600 Euro Housing
1500 Euro Gross
- 480 Eur Tax
NCD Header 6
30.09.2009
NCD Item Group C
600 Euro Housing
2000 Euro Emergency
2600 Euro Gross
- 450 Eur Tax
1820 remaining for
other deductions
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 156

Submit
Application

Establish
Determine
Calculate
Decision
Entitlement
Entitlement
Manage
Application
Receive
Liability
Progr
am
BRF
plus
Progr
am
Social
Application
Caseworker
Application
Form
Payment Management
Determine
Gross Payment
Determine
Deduction
Approve
Execute
Payment
Calculate
Net Payment
Approve
BRF
plus
Approval
XML
Progr
am
Social Service Plan
BRF
plus
Progr
am
Interactions
BRF
plus
Case
Progr
am
Payment
SAP 2010 / Page 157
BRF
plus
Net Calculation
Agenda
1.Accounting
for Financial Benefits in PSCD

2.Billing Process and Configuration
3.Invoicing Process Options
SAP 2010 / Page 158
Billing/Accounting
What happens in Accounting?
Posting & Paying
Benefit Decision
after Net Calculation:
Each month
2000 Benefit
./. 50 Deduction
./. 250 Taxation
-----------------------1700 Net Benefit
1700
Payment
Recipient
50
Utilities
Company
Billing & Invoicing

250
Tax Agency
SAP 2010 / Page 159
Accounting for Financial Benefits: From Benefit

Calculation to Payment (and Backwards)
Net Calculation
Document
Social Billing
Run
Billing
Document
Invoicing
Run
Invoicing
Document
Posting
Document
Payment
Run
2
Payment
Document
1
(recommended)
Account
Maintenance
PSCD
Cross-Reference between documents
Process Chain in Accounting
SAP 2010 / Page 160
Clearing against
Debit
Recipients Account
Social Services Business Information on PSCD

documents
Account Holder (Business Partner in Role MKK
= Recipient of Benefit, usually the beneficiary or main business partner on SSP
Contract Account
= Beneficiarys account for one or several benefits
Contract Object
= optional sub-classification for contract account
Main- and Sub-Transaction
= classification for benefits and business transaction
Final Recipients Contract Account
= contract account of deduct-to party; deduct-to party is account holder of this
account (revenue distribution will forward the deduction to the deduct-to party)
Alternative Payer/Payee
= other business partner that receives payment instead of account holder
Period Key
= period to which the benefit or deduction relates
SAP 2010 / Page 161
Master Data: Example for Account Display

CO = Benefits Program; Main = Benefit; Sub = generic
BP
CA
CO
Main/Sub
Main/Sub Text
Amount
Final Recipient
Due Date
30.04.2009
Monthly
Parental Benefits
4100/0100 Pregnancy: Regular Benefits
2500 Euro
Monthly
Parental Benefits
4100/0200
Pregnancy: Tax Deduction
-1000 Euro
Monthly
Parental Benefits
4100/0110
Pregnancy: Underpayment
5000 Euro
Monthly
Parental Benefits
4100/0210
Pregnancy: Und-pyt Tax Ddct. -2000 Euro
Monthly
Parental Benefits
4200/0060 Maternity: Down Payment
500 Euro
26.05.2009
Monthly
Parental Benefits
4200/0100 Maternity: Regular Benefits
2200 Euro
31.05.2009
Monthly
Parental Benefits
4200/0200
-900 Euro
Maternity: Tax Deduction
Tax Agencys CA
30.04.2009
13.05.2009
Tax Agencys CA
Tax Agencys CA
13.05.2009
To be cleared
payment = 1500
To be cleared
payment = 3000
To be cleared
payment = 1300
31.05.2009
AND: 1300 be
cleared with down
payment of 500;
payment = 800
CO would be blank if not used at all
SAP 2010 / Page 162
Master Data: Example for Account Display

CO = Benefit; Main/Sub = general
BP
CA
CO
Main/Sub
Main/Sub Text
Amount
Final Recipient
Due Date
30.04.2009
Monthly
Pregnancy Leave
4000/0100
Regular Benefits
2500 Euro
Monthly
Pregnancy Leave
4000/0200
Tax Deduction
-1000 Euro
Monthly
Pregnancy Leave
4000/0300
Underpayment
5000 Euro
Monthly
Pregnancy Leave
4000/0210
Und-paymt Tax Deduction -2000 Euro
Monthly
Maternity Leave
0060/0100
Down Payment
500 Euro
26.05.2009
Monthly
Maternity Leave
4000/0100
Regular Benefits
2200 Euro
31.05.2009
Monthly
Maternity Leave
4000/0200
Tax Deduction
-900 Euro
Tax Agencys CA
30.04.2009
13.05.2009
Tax Agencys CA
Tax Agencys CA
13.05.2009
31.05.2009
To be cleared
payment =
1500
To be cleared
payment =
3000
To be cleared
payment =
1300
1300 be cleared
with down
payment;
payment =
800
SAP 2010 / Page 163
Agenda
1.Accounting

SAP 2010 / Page 164
Billing/Accounting
From NCD to Billing Document
2000 /
monthly
500 /
monthly
250 /
monthly
Net Calculation Document:
Same Payment Recipient

Same Payment Family
Same Payment Frequency
Same Due Date Rule
Mass Activity
scheduled as
Batch job
Billing Documents
SAP 2010 / Page 165
Net Calculation: NCD Header and Item Group
Benefit Decision:
Each month
2000 Benefit
./. 500 Deduction
./. 250 Taxation
-----------------------1250 Net Benefit
NCD Header GUID x

January
Net Calculation Run for

January to March
NCD Header GUID y

February
NCD Item Group 1
1.
2.
3.
SAP 2010 / Page 166
NCD Header GUID z

March
Benefit 2000
Deduction -500
Taxation -250
Net Calculation: Correction for a period
INVALID
NCD Header GUID
x
January
SAP 2010 / Page 167
NCD Header GUID y

February
NCD Header GUID z

March
NCD Header GUID

yy
February
NCD Item Group 1
NCD Item Group 2
1.
2.
3.
1.
2.
3.
Benefit 2000
Deduction -500
Taxation -250
Benefit 2100
Deduction -500
Taxation -250
Technical Relation between Net Calculation

Document and Billing Document
NCD Header GUID

yy
February
Billing Document Header

1- 28 February
NCD Item Group 2
1.
2.
3.
SAP 2010 / Page 168
Benefit 2100
Deduction -500
Taxation -250
Billing Document Items
1.
2.
3.
Benefit 2100 , due on 28 Feb

Deduction -500, due on 28 Feb
Taxation -250, due on 28 Feb
Example NCD header item group link to

billing document
NCD
Header:
Unique Identifier of NCD

Header
Link to NCD Item group

This is the Net Calculation for the
week of 27 July to 02 August 2009
NCD Header Status: billed
Weekly payment
Cross Reference to Billing

Document
SAP 2010 / Page 169
Link Item Group ID Social Services Business

Object ID
1. Item in item group:

Housing Allowance of 140
2. Item in item group:

Social Income Tax -28
SAP 2010 / Page 170
Billing Document link to NCD
Unique Identifier of NCD

Header
Combination of Main and

Sub Transaction
Link to corresponding NCD
Items
SAP 2010 / Page 171
Grouping and Selection for Billing runs
Net Calculation Document
Payment Recipient
Payment Family
Payment Frequency
Due Date Rule
Social Billing
Run
Selection Parameters
Payment Recipient
Payment Family
Due Date Rule
Frequency Unit
Frequency Factor
PSCD
SAP 2010 / Page 172
Billing
Billing
Document
Document
Invoicing
Run
nvoicing
Invoicing
Document
Document
Billing/Accounting
Process overview Billing details
Mass
Mass
Activity
Activity
Social
Social
Billing
Billing
Business logic per
work package
Select NCDs to be processed
Reverse Billing Documents of revised NCDs
BAdI for Customer Enhancements
Bill all new NCDs
Update NCD database tables
SAP 2010 / Page 173
Billing Status of Net Calculation Document
SSP/SDP
approved
Transfer to
Accounting
Follow-up
SSP/SDP
approved
New Transfer to
Accounting
Net Calculation Run
Billing Run
Net Calculation Run
Billing Run
Open
Billed
Revised
Reversed
Cancelled
Status on Net Calculation Document
Open
Billed
Status on new Net Calculation

Document
SAP 2010 / Page 174
Billing/Accounting
Derivation of PSCD accounting information
Billing
Document
Invoicing
Document
NCD Header
BillDoc Header
InvDoc Header
NCD Items
BillDoc Items
InvDoc Items
Net Calculation
Document
BAdI:
PSSCB_BILL_CREATE
SAP 2010 / Page 175
Invoicing:
Event 2611
BAdI PSSCB_BILL_CREATE
Import and Export Parameters for Accounting
PSCD Billing Document
NCD Header PSSCD_NCD
Header DFKKINVBILL_H
Payment Recipient (GUID + ERP)

Payment Family
Payment Frequency Begin and
End Date
Payment Frequency Type
Status of NCD Doc
NCD Items PSSCD_NCDITEM
Kind of SXP
Tax Category
Benefit ID
Item Category
Gross Payment Item Process Cat.
Deduction Type
Priority of Items
Deduct-To-Party
Deduction Plan Item Process Cat
Entitlement Begin Date/End Date
Entitlement Frequency Type
Alternate Payee (GUID + ERP)
Alternate Payee Payment Method,
Address ID, Bank ID
SAP 2010 / Page 176
Origin Process of Billing Doc

Source Document Type of Bill Doc
Doc Type
BP Number
CA Number
Period Key
Revenue Type
Ref Doc GUID
Contract Object Type
Social Service Unique UUID
Items DFKKINVBILL_I
Main- /Sub-Transaction
CA Category (Account Det ID)
BP/CA/CO
Alternative BP for payments
CA of final recipient
Payment Items DFKKINVBILL_PY

Alternate
Payee Information
BAdI PSSCB_BILL_CREATE
Typical derivation logic to be implemented
PSCD Billing Document
Payment Recipient
Move
BP Number
Payment Family
Customizing Table
PayFam CA Category
CA Number
Due Dates; pay freq; SDP/SSP; reference

period (SSP)
Function module
Period Key (optional)
Payment Freq Begin/End Date
Move
Document Begin/End Date
Underpayment vs. reversal vs.

regular NCD?
Function module
Billing Doc Type (optional)
Kind of SXP, Tax Cat,

(Deduction Type, GPI item cat)
Derivation n:1
Main Tx (AcctingClassification)
(Sub-) Benefit ID
Derivation n:1
Sub Tx ((Sub)Benefit)
Constant or Derivation
from User/Benefit
Company Code
(Sub-)Benefit ID
Derivation n:1
Contract Object = (Sub)Benefit
From CA or CO master
data
Acct Determination ID
Due Date
Move
Net Amount Due Date
Deduct-To Party
Function Module BP
CAC for deduction CA
CA of Final Recipient
Alternate Payee
Move
Alternate Payee
SAP 2010 / Page 177
Billing Documents Configuration
When
billing documents are transferred from external systems or from

Public Sector Billing, new billing documents with sequential
numbers are created in the SAP system.
External number assignment must not be specified.
Billing documents can be created with different document types.
Billing documents can be created in several processes in parallel.
For each document type, define as many number ranges as you want
to use parallel processes.
You can use number range object FKKINVBILL to manage the
number range intervals for invoicing documents.
SAP 2010 / Page 178
Transaction Social Billing Mass Run

SAP Menu Public Sector Management Social Services Mass Processing Create Billing Documents
SAP 2010 / Page 179
PSCD Document Chain: Billing Document

SAP Menu Accounting Contracts Accounts Receivable and Payable Invoicing Display
Document Display Billing Document
SAP 2010 / Page 180
PSCD Document Chain: Invoicing Document

SAP Menu Accounting Contracts Accounts Receivable and Payable Invoicing Display
Document Display InvoicingDocument
SAP 2010 / Page 181
PSCD Document Chain: Posting Document

SAP Menu Accounting Contracts Accounts Receivable and Payable Posting Document
Display
SAP 2010 / Page 182
PSCD Document Chain: Account Display

SAP Menu Accounting Contracts Accounts Receivable and Payable Account Account Balance
SAP 2010 / Page 183
Agenda
1.Accounting

SAP 2010 / Page 184
Billing and Invoicing in PSCD
Invoicing in PSCD
Social Billing
Inbound Interface
Additional Functions
Other
Billing Systems
(external or internal)
Account Maintenance and Clearing

Interest Calculation
Charges Calculation
Dunning Proposal
Display of Additional Items
Notification
SAP 2010 / Page 185
Invoicing Process Architecture

SAP ERP
Invoicing in PSCD
SAP BW
Invoicing
Process
BW
Extraction
RM-CA
PSCD
PSCD
Posting
Document
Billing
System A
Structured bill document 1
Billing
System B
Inbound
Processing
Service Billing
Invoicing
Document
Structured bill document 2
EDR
Billing
Document
Printing
Process
SAP 2010 / Page 186
Print
Workbench
Invoice
Printout
Inbound Interface for Billing Documents
ERP
Inbound
Interface
Invoicing
Order
Billing
Document
Z Table
SAP 2010 / Page 187
Invoicing
Mapping
External Document Data
ALE
External
System
BAPI
External
System
Invoicing Functions
Invoicing Function
The invoicing function describes a task that is supported in invoicing.

The following are some of the invoicing functions possible:
Automatic Account Maintenance
Manual Account Maintenance (Dialog Call)
Activation of Open Items
Integration in BW Sales Statistics
Charges and Discounts
Debit Entry of Statistical Documents
Dunning Proposal
Sub item
Calculation of Interest on Open Items
Invoicing of Billing Documents
Creation of Collective Invoicing Printout
Invoicing of SD Documents

SAP 2010 / Page 188
Invoicing Orders Selection Control
Form Preparation
Public Sector
Billing
External Billing
Systems
Billing Documents
Invoicing Orders
Master Data
To Be Billed
Selection of Invoicing
Orders
Data Selection
Creation of Invoicing
Units
SAP 2010 / Page 189
Invoicing Transactions
In billing and invoicing, main and sub transactions are used for invoice
display and to control the posting of billing documents
In billing, transactions can be determined as follows:
External Billing Systems: Determination of transactions from external document data
Public Sector Billing: Determination of transactions in the action definition in the

Business Rule Framework
In invoicing, the transactions are used for the following purposes:
To explain the billing document items in invoice printing
To determine the account assignment (revenue accounts) for the general ledger items
To determine the account assignment for the business partner items
To determine the CO account assignments
For the BW update
Transactions in invoicing can:
Be transferred from billing document items
Be summarized on the basis of the transactions in the billing document items
SAP 2010 / Page 190
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 191

Submit
Application
Manage
Application
Benefit Decision
Making Process
Decision Update
SAP 2010 / Page 192
Establish
Decision
Determine
Entitlement
Payment Management
Calculate
Entitlement
Determine
Gross Payment
Receive
Liability
Determine
Deduction
Approve
Calculate
Net Payment
Approve
Execute
Payment
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Optional
Out of Scope
SOA
SSP
Previous Release
decision assessment
decision assessment
SAP 2010 / Page 193

Approval
Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Manual
Adjustment
Decision
Assessment
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Deduction
Making
Process
Approval
Net
Calculation
Display
Optional
Out of Scope
Previous Release
decision assessment
SAP 2010 / Page 194
Agenda
Benefit Decision Update: Change Process

2. Standard Change Processes
3. Delta Logic / Entitlement Adjustment
1.
SAP 2010 / Page 195
Benefit Decision
Update Process
Benefit Decision
Making Process
Previous Benefit Decision
SSP
Creation
Eligibility
Check
Entitlement
Determin.
Entitlement
Calculation
Updated Benefit Decision
Manual
Adjustment
Decision
Assessment
Entitlement
Adjustment
Gross
Payment
Item
Determin.
Approval
Previous SSP
Change
Process
SSP
Creation
Approval
Follow up SSP
Auto
One SSP can have several non approved follow up SSP.

One SSP can have only one approved follow up SSP
One SSP can have only one previous SSP
Out of Scope
Previous Release
decision assessment
SAP 2010 / Page 196
Benefit Decision Update

Change Process
SAP 2010 / Page 197
Agenda

1.
1.
2.
3.
4.
3.
SAP 2010 / Page 198
Create Follow-Up Social Service Plan (G006)

Copy Header (G002)
Termination at Header Level (G001)
Customizing
Delta Logic / Entitlement Adjustment
Change Processes Types
Three generic change processes on header level are available out of the
box:
Copy Header (G002)
Nota: Item Change Processes
Termination (G001)
Copy (G002)
Are not available anymore for caseworker.
SAP 2010 / Page 199
(G00X) = Business
transaction of the
change process
Previous SSP
SAP 2010 / Page 200
Agenda

1.
1.
2.
3.
4.
3.
SAP 2010 / Page 201

Copy Header (G002)
Customizing
SAP 2010 / Page 202
SAP 2010 / Page 203
SAP 2010 / Page 204
Agenda

1.
1.
2.
3.
4.
3.
SAP 2010 / Page 205

Copy Header (G002)
Customizing
Copy Header (G002)
SAP 2010 / Page 206
Copy Header (G002)
SAP 2010 / Page 207
Agenda

1.
1.
2.
3.
4.
3.
SAP 2010 / Page 208

Copy Header (G002)
Customizing
SAP 2010 / Page 209
SAP 2010 / Page 210
Termination at Header Level (G001) Example

Previous SSP
Benefit A
Benefit B
Benefit C
01.01.2012
31.12.2012
Incoming Change > Termination of whole SSP on 31.07.2012
SSP
Non Entitled
Entitled
Benefit B
Benefit C
01.01.2012
SAP 2010 / Page 211
01.08.2012
31.12.2012
Agenda

1.
1.
2.
3.
4.
3.
SAP 2010 / Page 212

Copy Header (G002)
Customizing
Change Process
Customizing
Make Settings for Change Processes

SAP Customizing Implementation Guide -> Customer Relationship Management ->
Industry-Specific Solutions -> Public Sector -> Social Services -> Basic Settings ->
Change Processes -> Make Settings for Change Processes
Define BRF Rules for Change Processes

Change Processes -> Define BRF Rules for Change Processes
Determine Target Transaction Type in Change Processes

Define BRF Rules for Change Processes
Change Processes -> Determine Target Transaction Type in Change Processes

Change Processes -> Business Add-Ins (BAdIs)
SAP 2010 / Page 213
Create Follow-Up Social Service Plan (G006):

Customizing
SAP 2010 / Page 214

Customizing
SAP 2010 / Page 215

Customizing
SAP 2010 / Page 216

Customizing
SAP 2010 / Page 217
Agenda

1.
1.
2.
3.
4.
3.

1.
2.
SAP 2010 / Page 218

Copy Header (G002)
Customizing
Entitlement Adjustment
1.
Determination of Previous SSP Relevant Version
2.
Determination of Relevant Entitlement Items
Delta logic scenarios and examples

Benefit Decision
Making Process
Application
Decision
SSP
Creation
Eligibility
Check
Optional
Entitlement
Determin.
Entitlement
Calculation
Generated
Entitlement
Items
Out of Scope
Previous Release
Manual
Adjustment
Relevant
Previous
Entitlement
Items
Determin.
Decision
Assessment
Benefit
Filtering
Item
Category
Determin.
Gross
Payment
Entitlement
Item
Adjustment
Determin.
Approval
Entitlement
Item
Creation

decision assessment
SAP 2010 / Page 219
Previous
SSP (s)
Optional
Decision Update, Delimitation of Predecessor

SSP, Delta Logic Scenario
Context
A decision, from a set of circumstances, is an outcome of a legal case.

From a business point of view it can happen that this outcome needs to be modified and new decision
(s) have to be made.
As a basic principle, an approved decision cannot be changed and so modification of an outcome can
be only done via the creation of a new decision.
This decision can update the outcome using two approaches:
Replace logic The new decision nullifies and replaces the previous one for the entire decision
period,
Delta Logic The new decision nullifies and replaces the previous one only for the time slice
where outcome needs to be changed.
End Date
Beginning Date
Decision Period SSP version n
31/12
01/01
Benefit Program 1
EI1 1000 /Month
SAP 2010 / Page 220
SSP
Version n

Example
Outcome: Decision n Beneficiary received a benefit X from January to December. Benefit amount from January to
December 1000 per month
Decision n
Decision period 01/01 to 31/12
From 01/01 to 31/12 Beneficiary will receive 1000 per month
Change of outcome: Benefit amount becomes 1200 from June

Replace Logic: Decision n+1
Decision n is not seen anymore by the system as input of processes.
Delta Logic: Decision n+1
Decision n is still active and seen by the system as input of processes from 01/01 to 31/05
Decision n+1 replaces decision 1 only for decision n+1 Decision Period.
Decision 1 is not seen anymore by the system as input of processes for decision n+1 Decision Period.
Beginning Date
01/01
End Date
31/12

Benefit Program 1
SSP Version n
EI1 1000 /Month

Beginning Date
01/01
Decision Period SSP version n+1 Replace Logic

Benefit Program 1
SSP Version
n+1
EI1 1000 /Month

31/05
End Date
31/12
EI1 1200 /Month
Decision Period SSP version n+1 Delta Logic

Beginning Date
01/06
Benefit Program 1
EI1 1200 /Month
SAP 2010 / Page 221
SSP Version
n+1

Conclusion
From a business process point of view Delta Logic better maps process reality.
From a performance point (e.g. several years recalculation scenario) Delta Logic offers
better guaranties
For business processes or situation where Replace Logic is required, Delta Logic if the
new decision period is the same than the previous decision period, is equivalent to
Replace Logic
System is Delta Logic

Beginning Date
01/01
End Date
31/12

Benefit Program 1
SSP Version n
EI1 1000 /Month
Decision Period SSP version n+1 Delta Logic

Beginning Date
01/06
Benefit Program 1
EI1 1200 /Month
SAP 2010 / Page 222
SSP Version
n+1
Agenda

1.
1.
2.
3.
4.
3.

1.
2.
SAP 2010 / Page 223

Copy Header (G002)
Customizing
1.
2.
Sub processes
Entitlement
Adjustment
Entitlement
Determination
Generated
Entitlement
Items
Previous
SSP (s)
SAP 2010 / Page 224
Relevant
Previous
Entitlement
Items
Determin.
Previous
Relevant
SSP
Determin.
Benefit
Filtering
Item
Category
Determin.
Relevant
Entitlement
Items
Determin.
Entitlement
Item
Creation
Entitlement
Period
Determin.
Agenda

1.
1.
2.
3.
4.
3.

1.
2.
SAP 2010 / Page 225

Copy Header (G002)
Customizing
1.
2.
Relevant SSP Determination
Entitlement
Adjustment
Generated
Entitlement
Items
Previous
SSP (s)
Relevant Previous
Entitlement Items
Determin.
Previous
Relevant SSP
Determin.
Benefit Filtering
Item
Category
Determin.
Relevant
Entitlement
Items Determin.
Entitlement
Item Creation
Entitlement
Period Determin.
Principles
The initial decision (first SSP) can be updated several time which will create a decision chain based
on follow up of follow up SSP.
A SSP can have only one follow up approved SSP.
A follow up SSP replaces his previous SSP for the follow up SSP decision period
If follow up SSP decision period is not included in the previous SSP decision period it may happen the
new decision replaces one or several previous SSP.
Conclusion
The first step of the process is to identify which previous SSP (s) are impacted by the new follow up
SSP.
This identification is done via the decision period and SSP chain.
Next slides provide various example allowing a better understanding of the logic
SAP 2010 / Page 226
Relevant SSP Determination Scenario 1
TIME
End Date
Beginning
Decision Period Version n
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
Decision Period Version n+1
E.D n+1
SSP
Version n + 1
B.D n+1
Business Scenario 1
Relevant
Vn
Time slice to be considered from previous versions
Version n
decision
Vn+1
Beginning Date Version n: B.D.n

End Date Version n: E.D.n
SAP 2010 / Page 227
See
note
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
E.D n+1
B.D n+1
SSP
Version n + 1
Business Scenario 1
B.D n+2
E.D n+2
SSP
Version n + 2
Business Scenario 1
Relevant
Vn
decision
Vn+1

Vn+2

SAP 2010 / Page 228
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
E.D n+1
B.D n+1
Business Scenario 1
B.D n+2
E.D n+2
SSP
Version n + 2
Business Scenario 1
Relevant
Vn
SSP
Version n + 1
Time slice to be considered from previous version n
decision
Time slice to be considered from previous versions Vn+1
Version n + 1
Vn+2

SAP 2010 / Page 229
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
E.D n+1
SSP
Version n + 1
B.D n+1
Business Scenario 1
Relevant
Vn
Vn
Version n
decision
Vn+1

SAP 2010 / Page 230
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
E.D n+1
SSP
Version n + 1
B.D n+1
Business Scenario 1
B.D n+2

Business Scenario 1
Relevant
Vn
E.D n+2
SSP
Version n + 2
Time slice to be considered from previous version n
decision
Version n + 1
Version n
Vn+2

SAP 2010 / Page 231
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
E.D n+1
B.D n+1
SSP
Version n + 1
Business Scenario 1
B.D n+2
E.D n+2
Business Scenario 1
B.D n+3
E.D n+3
SSP
Version n + 3
Business Scenario 1
Relevant
decision
SSP
Version n + 2
Vn
Vn+2
Version n + 2
Vn+3

SAP 2010 / Page 232
Agenda

1.
1.
2.
3.
4.
3.

1.
2.
SAP 2010 / Page 233

Copy Header (G002)
Customizing
1.
2.
Relevant Entitlement Items Determination
Entitlement
Adjustment
Generated
Entitlement
Items
Previous
SSP (s)
Relevant Previous
Entitlement Items
Determin.
Previous
Relevant SSP
Determin.
Benefit Filtering
Item
Category
Determin.
Relevant
Entitlement
Items Determin.
Entitlement
Item Creation
Entitlement
Period Determin.
Principles
After relevant SSP (s) determination, Entitlement items to be considered have to be

defined.
To be considered entitlement period must be:
Completely or
Partially
Includes in the new decision period.
Next slides provide various example allowing a better understanding of the

logic
SAP 2010 / Page 234
Entitlement item from previous SSP version

relevance Scenario 1
TIME
End Date
Beginning
Date
Version n
E.D.n
Version n
B.D.n
SSP
Version n
Business Scenario 1
EI1
EI2
EI3

B.D n+1
Business Scenario 1
E.D n+1
SSP
Version n + 1
EI1
EI2

SAP 2010 / Page 235
SSP version relevance

Scenario 2
TIME
End Date
Beginning
Date
Version n
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
EI1
EI2
EI3
E.D n+1
B.D n+1
Business Scenario 1
SSP
Version n + 1
EI1
EI2
B.D n+2

Business Scenario 1
E.D n+2
SSP
Version n + 2
EI1
EI2
SAP 2010 / Page 236

Scenario 3
TIME
End Date
Beginning
Date
Version n
E.D.n
Version n
SSP
Version n
Business Scenario 1
B.D.n
EI1
EI2
EI3
E.D n+1
B.D n+1
SSP
Version n + 1
Business Scenario 1
EI1
EI2
B.D n+2

Business Scenario 1
E.D n+2
SSP
Version n + 2
EI1
EI2
EI1
EI3
SAP 2010 / Page 237

Scenario 4
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
Business Scenario 1
B.D.n
SSP
Version n
EI1
EI2
EI3

B.D n+1
Business Scenario 1
E.D n+1
SSP
Version n + 1
EI1
EI2

SAP 2010 / Page 238

Scenario 5
TIME
End Date
Beginning
Date
Version n
E.D.n
Version n
Business Scenario 1
B.D.n
SSP
Version n
EI1
EI2
EI3
E.D n+1
B.D n+1
SSP
Version n + 1
Business Scenario 1
EI1
EI2
B.D n+2
E.D n+2
SSP
Version n + 2
Business Scenario 1
EI1
EI2
EI3
EI1
EI2
SAP 2010 / Page 239

Scenario 6
TIME
End Date
Beginning
Version n
Date
E.D.n
Version n
Business Scenario 1
B.D.n
SSP
Version n
EI1
EI2
EI3
B.D n+1
E.D n+1
SSP
Version n + 1
Business Scenario 1
EI1
EI2
B.D n+2
E.D n+2
SSP
Version n + 2
Business Scenario 1
EI1
EI3
EI2
E.D n+3
EI1
B.D n+3
EI2
SSP
Version n + 3
Business Scenario 1
EI1
EI2
EI2

SAP 2010 / Page 240
Agenda

1.
1.
2.
3.
4.
3.

1.
2.
SAP 2010 / Page 241

Copy Header (G002)
Customizing
1.
2.
Example 1: First Decision

Application
Decision
29.05.200n
SSP
Creation
Eligibility
Check
03.06.200n
Manual
Adjustment
GPI 1
SAP 2010 / Page 242
Entitlement
Adjustment
Gross
Payment
Item
Approval
01.09.200n
19.04.200n+1
Business Scenario 1
EI 1
Global
Assessment
3500 / w
15000 / M
Example 1: Follow-up Second Decision

(Scenario 1)
Application
Decision
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
01.09.200n
29.05.200n
Entitlement
Adjustment
Gross
Payment
Item
Approval
19.04.200n+1
04.07.200n
Business Scenario 1
SSP 1
3500 / w
EI 1
3500 / w
GPI 1
21.04.200n+1
23.06.2003
Due date
30.07.2003
Due date
Business Scenario 1
01.07.200n
SSP 2
EI 1
14.07.200n
EI 2
GPI 2
3500 / w
21.12.200n
7000
EI 3
GPI3
3500 / w
15000 / M
EIn
EIn
SAP 2010 / Page 243
Entitlement Item with category not entitled

Entitlement Item with category entitled

(Scenario 2)
Application
Decision
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
Entitlement
Adjustment
Gross
Payment
Item
Approval
01.09.200n
29.05.200n
19.04.200n+1
04.08.200n
Business Scenario 1
SSP 1
3500 / w
EI 1
3500 / w
GPI 1
21.04.200n+1
23.06.2003
Due date
30.07.2003
Due date
Business Scenario 1
01.07.200n
SSP 2
EI 1
GPI 1
0/ w
-15000
14.07.200n
EI 2
GPI 2
3500 / w
21.12.200n
7000
EI 3
GPI3
3500 / w
15000 / M
EIn
EIn
SAP 2010 / Page 244

Application
Decision
01.01
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
03.01
Entitlement
Adjustment
Gross
Payment
Item
Approval
31.12
Business Scenario 1
EI 1
GPI 1
SAP 2010 / Page 245
1000 per Month

1000 per Month
SSP 1

(Scenario 1 no overpayment)
Application
Decision
01.01
SSP
Creation
Eligibility
Check
12.06
Manual
Adjustment
Global
Assessment
Entitlement
Adjustment
30.06.
Gross
Payment
Item
Approval
31.12
Business Scenario 1
EI 1
GPI 1
SSP 1
1000 per Month
1000 per Month
Business Scenario 1
SSP 2
EI 1
EIn
EIn
SAP 2010 / Page 246


(Scenario 2 Overpayment)
Application
Decision
01.01
SSP
Creation
Eligibility
Check
30.06
Manual
Adjustment
Global
Assessment
31.07
12.08
Entitlement
Adjustment
Gross
Payment
Item
Approval
31.12
Business Scenario 1
EI 1
GPI 1
SSP 1
1000 per Month
1000 per Month
Business Scenario 1
SSP 2
EI 1
GPI 1
-1000
EIn
EIn
SAP 2010 / Page 247

Application
Decision
01.01
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
03.01
Entitlement
Adjustment
Gross
Payment
Item
Approval
31.12
Business Scenario 1
EI 1
GPI 1
SAP 2010 / Page 248
1000 per Month

1000 per Month
SSP 1

(Scenario 1 no underpayment)
Application
Decision
01.01
SSP
Creation
Eligibility
Check
01.03
12.03
Manual
Adjustment
Global
Assessment
Entitlement
Adjustment
30.06
Gross
Payment
Item
Approval
31.12
Business Scenario 1
SSP 1
1000 per Month
EI 1
GPI 1
1000 per Month
Business Scenario 1
EI 1 1200 per Month
EI 1
SSP 2
0 per Month
GPI 1 1200 per Month
EIn
EIn
SAP 2010 / Page 249


(Scenario 2 Underpayment)
Application
Decision
01.01
SSP
Creation
Eligibility
Check
01.03
31.03
12.04
Manual
Adjustment
Global
Assessment
Entitlement
Adjustment
Gross
Payment
Item
30.06
Approval
31.12
Business Scenario 1
SSP 1
1000 per Month
EI 1
GPI 1
1000 per Month
Business Scenario 1
EI 1
GPI 1
1200 per Month
EI 1
SSP 2
0 per Month
200 O.t.P for March

GPI 1 1200 per Month
EIn
EIn
O.t.P
SAP 2010 / Page 250

One time payment
Application
Decision
01.01
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
03.01
Entitlement
Adjustment
Gross
Payment
Item
Approval
31.12
Business Scenario 1
EI 1
GPI 1
SAP 2010 / Page 251
1000 per Month

1000 per Month
SSP 1

Application
Decision
01.01
SSP
Creation
Eligibility
Check
Manual
Adjustment
Global
Assessment
01.10
01.03
Entitlement
Adjustment
12.10
Gross
Payment
Item
31.10
Approval
31.12
Business Scenario 1
SSP 1
1000 per Month
EI 1
GPI 1
1000 per Month
Business Scenario 1
SSP 2
EI 1
GPI 1
- 7000 O.t.P for from March to September
EIn
EIn
O.t.P
SAP 2010 / Page 252

One time payment
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 253
Agenda
1.
2.
Deduction Decision Process Overview

Deduction Decision Process Detail view
SAP 2010 / Page 254
What is Deduction in Social Services?
1000
Authority
Gross Benefit
Payment
800
Net Payment
Deduct-From
Party
200
200
Deducted
Amount
SAP 2010 / Page 255
Deduct-To
Party
Examples of Typical Deduction Scenarios
Decision-based
Deductions
Utility Fee Deduction

Periodical deductions made to cover rent, water, electricity, TV-license etc.
Claim Deduction
Deductions to cover existing liabilities to the agency (e.g. overpayment of Benefit
occurred in the past).
Saving Account
The deducted amount is placed to a dedicated account of the beneficiary and paid
out as a total sum only when the target saving amount is reached.
Rule-based
Income Tax
Deduction Types
Deduction on Social Benefit Payments considered as additional income.
Pension contribution
SAP 2010 / Page 256
Deduction on Social Benefit Payments as contribution to the pension scheme.
Withholding Deduction
1000
Benefit Payment
Account
200
SAP 2010 / Page 257
Third-Party Payment Deduction
1000
Benefit Payment
Account
200
Deduct-To Party
SAP 2010 / Page 258
Alternative Payment
Account
Allocated Deduction
1000
- 200
Benefit Payment
Account
200
- 200
Third-Party
Liability Account
SAP 2010 / Page 259
Liability
Account
Deduction Decision Process
Decision Making
Processes
PSCD
Benefit Decision
Process
Standard Functionality
Net
Calculation
Periodic
Billing
Invoicing
Deduction
Decision Process
CRM
SAP 2010 / Page 260
ERP
Contract
Accounting
Process Step: Request Deduction
Deduction
Decision Process
Request
Deduction
Create
Deduction
Plan
Maintain
Deduction
Plan
Approve
Deduction
Plan
Trigger
Changes
Process Step Description:

This step constitutes the actual reason why a deduction shall be made. Usually the decision to initiate a deduction is
triggered as a follow-up activity of a preceding decision process.
SAP 2010 / Page 261
Process Step: Create Deduction Plan
Deduction
Decision Process
Request
Deduction

Create a Social Deduction Plan (SDP) in the CRM
system as a outcome of the deduction request
process
Input
Deduction Request
Trigger
There is no deduction plan yet or no

appropriate deduction plan could be found
(e.g. no deduction plan in status open)
Procedure
1.
Create new Deduction Plan
2.
Assign Case
3.
Maintain Header Data:
Output
A new Deduction Plan with maintained

header.
SAP 2010 / Page 262
Create
Deduction
Plan
Maintain
Deduction
Plan
Approve
Deduction
Plan
Trigger
Changes
Process Step: Maintain Deduction Plan

Sub Step: Create Deduction Item
Deduction
Decision Process
Request
Deduction
Create
Deduction
Plan
Create
Deduction
Item

Create a deduction plan item as a line item of
the deduction plan. Define the business
purpose for the deduction.
Input
An not yet approved Deduction Plan with

maintained header.
Trigger
Create deduction Items

Procedure
Create new Deduction Item

2.
Maintain Item header Details
Output
1.
A new Deduction Item
SAP 2010 / Page 263
Maintain
Deduction
Plan
Maintain
Deduction
Data
Approve
Deduction
Plan
Simulate
Deduction
Trigger
Changes

Sub Step: Maintain Deduction Data
Deduction
Decision Process
Create
Deduction
Plan
Request
Deduction
Create
Deduction
Item
Maintain the grouping criteria for payments to be

deducted and other deduction details (amount,
priority, Deduct-To-Part).
Input
A new Deduction Item with header data.

Trigger
System triggered.
Procedure
1.
Maintain grouping criteria or select payment to
deduct from via net payment search.
2.
Copy the selection criteria to the item.
3.
Maintain deduction amount/percentage.
4.
Maintain Deduct-To Party.
Output
A Deduction Item with deduction details
SAP 2010 / Page 264
Maintain
Deduction
Plan
Maintain
Deduction
Data
Approve
Deduction
Plan
Simulate
Deduction
Trigger
Changes

Sub Step: Simulate Deduction
Deduction
Decision Process
Request
Deduction
Create
Deduction
Plan
Create
Deduction
Item

Run planned deduction items before activate them in
a simulated environment to check their
correctness.
Input
1.
Trigger
1.
Decision Assessment
1.
Access Net Display

Adjust simulation criteria
Execute Simulation Request to back-end.
Procedure
2.
3.
A decision assessed deduction plan with welldefined deduction items.
Output
1.
Simulated Net Calculation Result including not

yet activated deduction items in the deduction
plan.
SAP 2010 / Page 265
Maintain
Deduction
Plan
Maintain
Deduction
Data
Approve
Deduction
Plan
Simulate
Deduction
Trigger
Changes
Process Step: Approve Deduction Plan
Deduction
Decision Process
Request
Deduction

Approve the decision assessed deduction plan
and activate it for replication and follow-up
processing in backend.
Input
Trigger
Trigger For Approval
Procedure
Decision Assessed Social Deduction Plan
System performs the approval process.

Optional: User manually approve or reject
the social deduction plan.
User saves the deduction plan.
Output
An approved and activated Social

Deduction Plan.
SAP 2010 / Page 266
Create
Deduction
Plan
Maintain
Deduction
Plan
Approve
Deduction
Plan
Trigger
Changes
Process Step: Trigger Changes
Deduction
Decision Process
Request
Deduction

Perform well-defined change processes on an
activated Social Deduction Plan.
Input
An activated deduction plan with deduction

items.
Trigger
1.
Launch change options on Plan or Item Level
Procedure
1.
Trigger one of the following change processes
Create a new version of the deduction plan

(plan level change process)
Put deduction plan on hold and resume later

(plan level change process)
Cancel a deduction item (item level change

process)
2.
Save the original deduction plan and navigate to
the follow-up Deduction Plan.
3.
Edit the follow-up deduction plan.
4.
Decision-assess the plan (creation of invalidation
items)
5.
Active the follow-up Deduction Plan
Output
A new Deduction plan and updated Deduction

Items
SAP 2010 / Page 267
Create
Deduction
Plan
Maintain
Deduction
Plan
Approve
Deduction
Plan
Trigger
Changes
Agenda
2. Deduction Decision Process Detail view
1.Social Deduction Plan in CRM Web Client UI
1.
2.Customizing
SAP 2010 / Page 268
Options in CRM for Deduction Decision Process
Social Deduction Plan - Overview Page
The deduction plan

represents a legal
decision and therefore
has the same decision
assessment as
processing step like
SSPs.
After entering the main

partner for the deduction
plan, the system
automatically derives the
corresponding case
according to the profile
assigned in customizing.
For Deduction Plan a case
assignment is optional.
Technically speaking, the

Deduction Plan is a
bracket entity for the
grouping of different
deduction plan items. The
deduction plan has no real
processing impact on the
deduction execution in the
follow-up processes in
ERP.
An external reference
can be entered as
additional identifier for
the deduction plan.
Follow Assignment Blocks are visible by default:
General Data for maintaining header data
Items for Deduction plan Items

Transaction History for display of document flow
The items have the real process meaning as they
contain the explicit deduction instructions, how to
make the deduction from actual payments and where to
transfer the deduction amount.
The customer has the flexibility to either define one
unique deduction plan per individual and collect all
deductions as items in the same plan or create multiple
deduction plans per business partner, each dealing
with specific types of deductions
SAP 2010 / Page 269
Change History for tracking of changes on the plan

Notes and Attachments for documentation.
Following Assignment Blocks are hidden:
Parties Involved
Dates
Cases
Social Deduction Plan Item - Overview Page -1
The start and end date of the

deduction are displayed here.
Start date shall not be in the
past, as it is not possible to
deduct from payments, which
have already been paid. The
definition of past is dependent
on the payment family of the
payment and the related
reference date.
The item category defines the

business reason for deduction
(e.g. utility fee deduction, claim
deduction etc.).
The Deduct-to-Party is optional for some deduction

scenarios.
The Deduct-To-Party does not always have to be a
different person but could also be the deduct-from
party itself.
The actual account for posting the deducted
amount to is derived by the system based on
account category and deduction category
assignment as customized in IMG. Result of the
derivation are the payment details like bank
account and payment method, which are specified
for the target account.
SAP 2010 / Page 270
Follow Assignment Blocks are visible by default:

General Data for maintaining header data
Transaction History for display of document flow
Change History for tracking of change on the plan
Notes and Attachments for documentation.
Dates

Triggers navigation to the
payment search page, where it is
possible to search and select the
payment and copy the relevant
payment grouping criteria data to
the concerned fields on this
screen.
At item creation the system

derives the main partner from the
plan level as the default deductfrom party. But the user is free to
assign a different business
partner as deduct-from party.
The relevant grouping criteria, Payment
Recipient, Payment Family, Payment
Frequency and Due Date Rule are the
minimum criteria, which unambiguously
determine an exact due date.
The criteria values are used by net
calculation engine in the back-end to bring
payments and deductions together.
Instead of manual entry, the data can also
be copied from the Payment Search screen
accessible through the Search for
Payment button above.
The priority influences the sequence of the item

execution later net calculation. If there are two
deduction items of the same ERP deduction type
targeting the same payment, the one with the
lower priority number comes first.
It is possible to enter the same priority number
for two different items. But then the first come
first serve principle will apply.
SAP 2010 / Page 271

Triggers navigation to the
payment search page, where it is
possible to search and select the
payment and copy the relevant
payment grouping criteria data to
the concerned fields on this
screen.
At item creation the system

derives the main partner from the
plan level as the default deductfrom party. But the user is free to
assign a different business
partner as deduct-from party.
The relevant grouping criteria, Payment
Recipient, Payment Family, Payment
Frequency and Due Date Rule are the
minimum criteria, which unambiguously
determine an exact due date.
The criteria values are used by net
calculation engine in the back-end to bring
payments and deductions together.
Instead of manual entry, the data can also
be copied from the Payment Search screen
accessible through the Search for
Payment button above.
The Partial Deduction flag instructs the

net calculation to deduct a fraction of the
absolute deduction amount specified, if the
full amount cannot be executed. If not
checked, the system will simply skip
deduction items, which cannot be fully
applied to a payment.
SAP 2010 / Page 272
The priority influences the sequence

of the item execution later net
calculation. If there are two
deduction items of the same ERP
deduction type targeting the same
payment, the one with the lower
priority number comes first.
Alternatively to the absolute

deduction amount, it is possible to
enter a percentage value instead.
This is particularly useful for
Deduct as much as possible
deduction scenario.
Social Deduction Plan Item Payment Search

After the suitable payment is
View
found, you can press this
button to copy the selection
criteria values back to the
corresponding fields on the
item overview screen.
The Search for Payments view is

basically a modified Net Display
view. By entering the search values,
the user is able to narrow down to
the suitable payments for deduction.
The user can filter the result by populating

additional search fields. All search criteria
(except the end date) are mandatory for the
determination of the suitable payment.
Search criteria not populated here must be
completed on the item overview screen.
SAP 2010 / Page 273
Social Deduction Plan Item Payment Search

Detailed View
The detailed view shows the

positions of a single payment
(unique due date).
The Net item category shows the

type of the payment (regular
payment, underpayment). For
deduction item it shows the
deduction types defined in ERP. For
each deduction item category
defined in CRM there is a
corresponding mapping to a ERP
deduction type. The mapping logic
has to be maintained in a BAdI
implementation in ERP.
SAP 2010 / Page 274
You can check the deduction priority

of each deduction item and plan
your own deduction item
accordingly.
Social Deduction Plan - Search Page

As a caseworker, it is possible to search for deduction plans using almost all attributes available on the
Social Deduction Plan. In addition, it is also possible to search for deduction plans using attributes of the
included items like Deduct-From Party, Deduct-To Party and Item Category.
Search Criteria:
Plan attributes:
Deduction Plan ID
Business Partner ID
Created By
Deduction Plan Description
Deduction Plan Type
Start Date
End Date
External Reference
Main Partner
Partner Function
Status
Item level attributes:
Deduct-From Party
Deduct-To Party
Item Category.
SAP 2010 / Page 275
Social Deduction Plan Search using Business

Partners in specific Partner Functions
It is possible to use Deduction plans specific partner functions directly as input for business partner IDs, like
Main Partner, Deduct-From Party and Deduct-To Party. It returns the same result like using two search fields
Business Partner ID and Partner Function combined.
One-Stop Search
SAP 2010 / Page 276
Combined Search
Agenda
1.
2.Customizing

1.Plan Level Customizing
2.Item Level Customizing
3.Change Processes
4.Integration with ERP
SAP 2010 / Page 277
Process Step: Trigger Changes
Deduction
Decision Process
Request
Deduction
Create
Deduction
Plan
Maintain
Deduction
Plan

Perform well-defined change processes on an activated Social Deduction Plan.
Input
An activated deduction plan with deduction items.

Trigger
1.
Launch change options on Plan or Item Level
Procedure
1.
Trigger one of the following change processes
Create a new version of the deduction plan (plan level change process)
Put deduction plan on hold and resume later (plan level change process)
Cancel a deduction item (item level change process)

2.
Save the original deduction plan and navigate to the follow-up Deduction Plan.
3.
Edit the follow-up deduction plan.
4.
Decision-assess the plan (creation of invalidation items)
5.
Active the follow-up Deduction Plan
Output
A new Deduction plan and updated Deduction Items
SAP 2010 / Page 278
Approve
Deduction
Plan
Trigger
Changes
Available Change Processes

Change processes can be triggered on both deduction plan and item level. The
Assignment Block for Change Options is only visible when the deduction has been
approved and activated.
Three generic change processes are available out of the box:
Create a follow-up deduction plan (Plan level)

Stop/resume an deduction plan (Plan level)
Cancel deduction item (Item level)
SAP 2010 / Page 279
Change Process Create follow-up Deduction

Plan
The change process Create Follow-up Deduction Plan creates a copy of the original SDP
starting with the date, when the change process is triggered. The follow-up SDP is open for
editing. The user can change the existing items or add new ones.
Change Process
Triggering Date
TIME
Jan
Deduction
Plan A
Feb
Mar
Apr
Deduction Plan Period

Item 1
Item 2
Deduction Plan Item 1
Follow-Up
Deduction
Plan A*
Item 1*
Item 2*
SAP 2010 / Page 280
Deduction Plan Item 1*
May
Jun
Jul
Aug
Change Process Create Follow-up Deduction

Plan
In the following example only item 10 is affected by the change process
because the change process is triggered between the validity period of the
item.
Items of the activated SDP
Change Process
Triggering Date:
14.07.2009
Items of the follow-up SDP:

Item 10 has been truncated
with start date equals the new
decision start date 14.07.2009
SAP 2010 / Page 281
Change Process Stop and Resume Deduction

Plan - 1
The Stop/Resume Change process on the deduction plan header is meant to stop all deduction activities of a
plan at a defined (future) stop date. With the resume date, the user define the date, on which the deduction
activities shall re-start again. The deductions originally planned between the stop and resume date are not lost
but will be caught up by prolonging the end date of the deduction to cover the missed deductions.
In that respect stop/resume supports the business understanding of deduction as an activity to fulfill the
collection target amount. It is less important WHEN the money will be collected but that it WILL be collected
completely at one time.
The resume date is optional. If left empty the system will only generate the items with end date equals the
stop date and no resumed item parts.
TIME
SDP
Deduction Plan Item
Stop
date
Resume
date
Follow-up SDP
Deduction Plan Item
Part 1
Deduction Plan Item

Part 2
shifted
Stopped Period
SAP 2010 / Page 282
Prolonged Period

Plan - 2
Technically, all deduction plan items with a period intersecting the stop date will have the end date truncated
to the stop date. The remaining part will be shifted by the time span between stop and resume date.
Since the deductions already planned for the stopped time span need to be deleted, corresponding
invalidation item (red colored item in the diagram below) will be automatically created at decision assessment
by the system.
Items are copied to follow-up SDP with the start date equals or later than the system date (= change process
triggering date)
Change Process
Triggering Date
TIME
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Item 1
Deduction
Plan A
Item 1*

Item 1**
SAP 2010 / Page 283
Deduction Plan Item Period 1*
15.04. Resume Date
Follow-up
Deduction
Plan A*
13.02. Stop Date
Item 1*
Invalidation
item
Deduction Plan Item 1**

Plan - 3
Items with start date between the stop and resume date (Item 2) are shifted to start after resume date as
well.
Processdate (Item 3) are not effected by Stop and Resume.
Items with start date afterChange
the resume
Triggering Date
TIME
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug

Item 1
Deduction
Plan A
Item 2
Item 3
Item 1*
Follow-up
Deduction
Plan A*
Item 1**
Item 2**
Item 3*
SAP 2010 / Page 284
15.04. Resume Date
Item 2*
13.02. Stop Date
Item 1*
Invalidation
items


Plan - 4
Item of the activated SDP
The copy of the original item has

new end date (16.10.2009) one
day before the stop date
(17.10.2009).
The second part is the resumed
deduction item starting with the
resume date 10.11.2009 and
ends with 16.12.2009 (= the
original end date 22.11.2099 plus
the missing 4 weeks due to the
stop).
The invalidation item has start
date equals the stop date and
end date one day before the
resume day.
SAP 2010 / Page 285
Stop Date:
17.10.2009
Resume date:
10.11.2009
Change Process Cancel Item

The system will cancel a deduction plan item by creating a follow-up deduction plan covering the complete
predecessor deduction plan period. Second, the system will copy all existing items from the old deduction
plan except the to be canceled item. For this item, the system will restore the first part of the original item
until the cancellation date. The Decision Assessment is then responsible to create the invalidation items
covering the remaining part.
The invalidation item will be used to cancel the existing deduction already planned in net calculation.
TIME
Jan
Feb
Mar
Apr
Deduction
Plan A
Item 2*
Item 2**
SAP 2010 / Page 286
13.02. Date of Cancellation
Follow-Up
Deduction
Plan A*
Item 2
Invalidation item
Change Process - Cancel Item
Items of the activated SDP:

Item 10 is to be cancelled.
Day of Cancellation:
01.10.2011
Items of the Follow-up SDP:

The cancelled item has end date
one day before the cancellation
day.
The system generated
invalidation Item has start date
equals cancellation day.
SAP 2010 / Page 287
Change Processes Customizing

You can directly use the
standard change processes
defined for deduction plans or
copy and modify them to
adapt to your own
requirements.
If the standard change processes sufficiently

meet your requirement, you just need to
assign them to your deduction plan types.
Change Process
It is possible to assign a change process to
multiple transaction types.
SAP 2010 / Page 288
Copying Control for Business Transactions

As result of a change process triggered for a
deduction plan or deduction plan item, the
system always technically creates a followup transaction representing a new decision.
To determine the list of change options
suitable for a transaction type and item
category, the copying logics for each new
transaction type and item category need to
be defined via the copying control
customizing.
By re-assigning the transaction type SDP
again as target transaction type for the
Source Transaction Type SDP, the system
allows the change processes defined for the
transaction type SDP being executed out of
a deduction plan of type SDP.
The same logics works for the
items.
SAP 2010 / Page 289
Agenda
1.
2.Customizing

1.Plan Level Customizing
2.Item Level Customizing
3.Change Processes
4.Integration with ERP
SAP 2010 / Page 290
Replication of Customizing Entries

For the deduction plan item being processed correctly with the target payment in the backend net
calculation, the deduction plan item must have the same values regarding a set of payment
specific grouping criteria, which are:
Payment Recipient (Master Data)

Payment Family (Customizing Definition)
Payment Frequency (Customizing Definition)
Due Date Rule (Customizing Definition)
All four criteria combined determine a specific payment to a specific person on a specific
day.
Of the four criteria, only the payment recipient is initially created and known to the CRM system.
The payment family, the payment frequency and the due date rule are values, which are initially
defined as part of customizing in ERP backend.
In CRM it has to be ensured that the same IDs of the entries are maintained identical to ERP.
Otherwise ERP will not be able to correctly derive the definition of the grouping criteria and match
the deductions with the intended payments in net calculation.
The customizing in CRM has to be done manually. Customizing table entries from ERP are NOT
automatically replicated to CRM IMG!!!
SAP 2010 / Page 291
Payment Family and Payment Frequency

replication
SAP CRM Customizing
SAP ERP Customizing
The same Frequency

to Payment Family
assignment like in
ERP need to be
maintained in CRM
Frequencies used for entitlement or

payment purpose are defined in
Customizing table in ERP IMG as
well as Payment Families.
SAP 2010 / Page 292
The IDs of the

payment frequencies
and payment families
defined in the
corresponding ERP
customizing need to
be maintained
manually in CRM.
Due Date Rule and Payment Frequency

Replication
SAP ERP Customizing
Manually
maintain IDs
of Due Date
Rule defined
in ERP to
CRM
SAP CRM Customizing
Manually maintain
the same Due Date
Rule to Frequency
assignment as
customized in ERP
SAP 2010 / Page 293
Frequency and Due Date Rule Derivation on

CRM UI
The customizing of the grouping criteria controls the valid values, which can be entered by the user during the planning of
the deduction plan items on CRM UI.
System automatically
derives the corresponding
payment frequency based
on the selected payment
family.
System automatically
derives the list of possible
Due Date Rules based on
the selected payment
frequency.
SAP 2010 / Page 294
Priority and Ranking

In CRM , on the Item overview of a Social
Deduction Plan (SDP), it is possible to specify
a deduction priority ranging from 000-999 for
each item.
But how does the priority work?
When a SDP is activated in CRM and then transfered to ERP, it is treated the same way like a SSP. That
means it will processed by the Gross Entitlement Calculation in ERP. What happens is that the item
categories on each SDP items will be mapped to a corresponding deduction type on ERP side.
SDP (CRM)
SDP (ERP)
Item of Cat 1
Item of Type A
Item of Cat 2
Item of Type A
Item of Cat 3
Item of Type B
The mapping logic is maintained in

a BAdI implmentation, which is
called during the Gross Entitlement
Calculation,. An example could be
like on the right:
SAP 2010 / Page 295
CRM Item Category
ERP Deduction Type
Item Category 1
Deduction Type A
Item Category 2
Deduction Type A
Item Category 3
Deduction Type B

Each customer can define own deduction
types in the corresponding customizing
table in ERP
The customer can assign unique ranking to

deduction types, which determines the order of
processing. If there are two deduction items
with different deduction types. The item with
the lower ranking number comes first. The
ranking is unique. It is not possible to have
two deduction types with the same ranking.
The example from the previous slide could therefore be extended like the following:
SAP 2010 / Page 296
CRM Item Category
ERP Deduction Type
Item Category 1
Deduction Type A
Item Category 2
Deduction Type A
Item Category 3
Deduction Type B
Deduction Type
Ranking
Now if we have a SDP with

three items and each of them
has a priority maintained. When
transfering to ERP, the priority
are transfered as well.
First the item categories are
mapped to deduction types
during Gross Entitlement
Calculation.
During net Calculation the item

are first rearranged according to
the ranking of the deduction type
in Customizing. Therefore Item 3
comes first.
Gross Entitlement Calculation

SDP (ERP)
SDP (CRM)
Item 1 of Cat 1
Prio 100
Item 1 of Type A
Prio 100
Item 2 of Cat 2
Prio 50
Item 2 of Type A
Prio 50
Item 3 of Cat 3
Prio 200
Item 3 of Type B
Prio 200
Net Calculation
SDP (ERP)
SDP (ERP)
Then, within the same deduction
type, the items are arranged
according to the priority. The
lower the number, the higher the
priority. Therefore Item 2 comes
before item 1.
SAP 2010 / Page 297
Item 3 of Type B
Prio 200
Item 3 of Type B
Prio 200
Item 1 of Type A
Prio 100
Item 2 of Type A
Prio 50
Item 2 of Type A
Prio 50
Item 1 of Type A
Prio 100
Priority and Ranking Nice to know
The processing order of the deduction items is first determined by the ranking of the deduction type and in the second
step by the priority of the items within the same deduction type.
If the mapping between the CRM item category and deduction type is 1:1, then the item priority has only influence on the
order of deduction items from the same deduction type.
If you would like to influence the order of the CRM deduction items only through item priority in CRM, then you could
map all CRM item categories to the same deduction type and thus giving them the same ranking. However, by doing this,
you will have problem to differentiate between the items in ERP if they have the same amount.
It is possible to enter the same priority number for two different deduction items in CRM (regardless whether they are on
the same item category or not). This could end up with two deduction items in ERP having the same deduction type and
same priority number. Then the logic of first come first serve applies.
SAP 2010 / Page 298
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 299
Agenda
8. Case Assignment
1.
2.
Overview
Case assignment in Detail
SAP 2010 / Page 300
Case Assignment
SAP 2010 / Page 301
Case Assignment
Overview
Majority of the social service customers work with cases.
This functionality makes it possible to search automatically for cases a social

application/social service plan should be assigned to.
Under certain conditions also a new case could be automatically created.
SAP 2010 / Page 302
Case Assignment
Overview
With the case assignment step, the social application / social service plan is
assigned to a new or existing case
You are able to:
Decide if case assignment
should be mandatory
Search for cases in
various ways
(e.g. via rules framework)
Set up a case creation
procedure
Assign a case
manually/automatically
Define relevant partners
for the case
SAP 2010 / Page 303
Maternity Leave
Case Assignment
Process Flow
CAP = Case Assignment profile
CDS = Case Determination Strategy
CCS = Case Creation Strategy
CTDS = Case Type Determination Strategy
BPFM = Business Partner Function Mapping
SAP 2010 / Page 304
Agenda
8. Case Assignment
Overview
2. Case assignment in Detail
1. Case type determination strategy
2. Business partner function mapping
3. Case determination algorithms
4. Case determination strategy
5. Case creation strategy
6. Case assignment profile
1.
SAP 2010 / Page 305
Case Type Determination Strategy

What is this setting for ?
It is used to determine a case type and an optional case category
Where used?
Usage within the Case creation strategy: A case of what case type / case category should
be created
Usage within a Case determination algorithm: The case type / case category could be
used as a (search) parameter for a case determination algorithm
SAP 2010 / Page 306
There are 4 possibilities (case type determination categories) to determine

automatically the case type (and optionally the case category):
Within the BRFPlus (Business Rule Framework)
Within a BAdI implementation
Via assignment of the case type/case category to a transaction type
Via assignment of the case type/case category to a request category
SAP 2010 / Page 307

Case Type Determination Category: BRFPlus
You are able to execute the case type determination within the SAP Business
Rule Framework
Therefore enter the BRFPlus application class and the BRFPlus Function in the
details view. Within this event (maintenance within the BRF) you could maintain
the rules to determine the case type (and optionally the case category)
SAP 2010 / Page 308

Case Type Determination Category: BAdI
You are able to execute the case type determination within a BAdI
SAP 2010 / Page 309

Case type determination category: Business transaction
You are able to assign a case type and optional a case category to a business
transaction
Therefore maintain the case type and the case category in the details view
How is the case type/case category then assigned to a transaction type?

1)
The CTDS is assigned to a case determination algorithm
2)
This case determination algorithm is within a case determination strategy
3)
The case determination strategy is within a case assignment profile
4)
This case assignment profile can be maintained at the header customizing for the
social application/social service plan
SAP 2010 / Page 310

Case type determination category: Web Request
You are able to assign a case type and optionally a case category to a Request
Category
Therefore maintain the request category, the case type and the case category in
the details view
SAP 2010 / Page 311
Agenda
8. Case Assignment
Overview
1.
SAP 2010 / Page 312
Business Partner Function Mapping
In the business partner function mapping, you define how the partner functions of a CRM
business transaction (e.g. APPLICANT) are mapped to the partner functions in the
respective case in Case Management (e.g. BENEFICIARY).
Where used?
Usage within the Case assignment profile: Defines which business partners should be
transferred from the business transaction to the case, e.g. the APPLICANT of the
business transaction will become the BENEFICIARY of the new case
Usage within the Case determination strategy: Search for cases where e.g. APPLICANT
of the business transaction = BENEFICIARY of the case
SAP 2010 / Page 313
Agenda
8. Case Assignment
Overview
1.
SAP 2010 / Page 314
Case Determination Algorithms

A case determination algorithm is used to find a case where a social application /
social service plan should be assigned to
SAP 2010 / Page 315
There are 4 possibilities (case determination algorithm types) to determine

automatically the case the social application/social service plan should be
assigned to:
Within the BRFPlus (Business Rule Framework)
Within a BAdI implementation
Take the same case of a predecessor document (e.g. of a former version of a
social service plan)
Use a simple predefined case search with parameter case type, case category,
business partners and status
SAP 2010 / Page 316

Type BRFPlus
You are able to execute the case determination within the SAP Business
Rule Framework
Therefore enter the BRF application class and the BRF event in the details
view. Within this event (maintenance within the BRF) you could maintain
the rules to determine the case type (and optionally the case category)
SAP 2010 / Page 317

Type BAdI
You are able to execute the case determination within a BAdI
The here entered CTDS, BPFM and

case processing status are
available within the BAdI as
parameter
(could be used as parameter)
SAP 2010 / Page 318

Type Predecessor
Take the same case of a predecessor document (e.g. of a former version of
a social service plan)
the result is a case that is assigned to the predecessor

document (if there is one) with the corresponding status
SAP 2010 / Page 319

Type Case Search
Use a simple predefined case search with parameter case type, case
category, business partners and status
the result is a case where

The case type (case category) match to the settings of the CTDS
The business partner(s) match to the settings BPFM
The status matches to the setting of this case determination algorithm
SAP 2010 / Page 320
Agenda
8. Case Assignment
Overview
1.
SAP 2010 / Page 321
Case Determination Strategy

A case determination strategy is used to find a case a social application/social
service plan should be assigned to. Here you can build a sequence of case
determination algorithms that should be executed till a case is found (if a case is
found the sequence is not further processed)
Example:
First try to determine the case via the predecessor document. If this algorithm
fails (=no result) execute the next algorithm in the batch sequence e.g. a BAdI
implementation to determine the case
SAP 2010 / Page 322
Agenda
8. Case Assignment
Overview
1.
SAP 2010 / Page 323
Case Creation Strategy

A case creation strategy is used to create a case a social
application/social service plan should be assigned to. The case type (case
category) of this newly created case is determined by the CTDS entered in
the marked field.
SAP 2010 / Page 324
Agenda
8. Case Assignment
Overview
1.
SAP 2010 / Page 325
Case Assignment Profile

A case assignment profile is a grouping of a case determination strategy and a
case creation strategy. In addition you could decide if case assignment is
mandatory and how the business partners should be mapped to the case.
the case assignment profile will be assigned to the header customizing of

a social application/social service plan and defines thereby the system
behavior for searching/creation of cases
SAP 2010 / Page 326
There are 4 possibilities to maintain a case assignment profile:

Resulting system behavior
CDS
CCS
Case will be searched via case determination

strategy and if no case could be found a case will be
created via case creation strategy
Assigned
Assigned
Every time a new case will be created corresponding

to the settings of the case creation strategy
Assigned
Case will be searched via case determination

strategy but if no case could be found there will be
no automatic case creation (just manual)
Assigned
No automatic search / creation of cases is

maintained, but case assignment is still possible on
the UI of the application / social service plan
SAP 2010 / Page 327
Manual case assignment could be necessary if:

Automatic case assignment leads to an error, i.e.. case assignment is mandatory but
the system was not able to assign a case
There is no CCS and no CDS maintained in the CAP case assignment is manual
1
In the upper region all cases
found by the CDS were
displayed
In the lower region you could

search for cases with the
standard case search (via F4 help)
SAP 2010 / Page 328
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 329
SAP CRM
Managing Social Services
Challenges
Drive to Transform & Reform

Resource optimization requires major change or transformation
Shared service is also seen as major enabler of transformation and
efficiency
Eligibility criteria being tightened to support best use and allocation of limited
budgets
Benefit Fraud
High and not easily managed and detected using old systems and silos of
data
Lack of single rules and calculation engine allows people to take advantage
Diverse complex family groupings means that rules and calculations are
complex
Capabilities
Social Application
Application creation using web form or web service
Validation Check
Benefit Determination (possibility to manage multiple Social Benefits within
one application)
Social Service Plan creation
Social Service Plan
Rule based Eligibility Check
Future & Retroactive Entitlement Calculation *
Gross Payment Determination *
Change Procedures (Delta Logic) *
Net Calculation Integration *
SAP 2010 / Page 330
Social Service
Management
Activity
Management
Interaction
Management
Document
Management
Case
Management
Business Partner
Management
SAP CRM
SAP CRM
Managing Activities
Challenges
What dates and tasks do I have next week?

Which activities took place with my customers? Which are planned?
Which activities are currently taking place within my team?

What was the result of my telephone call?
Social Service
Management
Which follow-up activities resulted from the meeting?
Capabilities
Context relationship (which Case?)

Task relationship (which Business Partner, which Business Object?)
Activity
Management
Status management and results
Journals & Attachments
Interaction
Management
Groupware Integration
Follow-up documents
Document
Management
Case
Management
Workflow management
Action management
Successfailure analysis
Customer care intensity analysis
Business Partner
Management
Activity history analysis

Planned activities analysis
SAP 2010 / Page 331
SAP CRM
Activity Management
Various Types of Activities
Appoint-ment
E-Mail
Activity
Task
SAP 2010 / Page 332
Interaction
Log
SAP CRM
Managing Interactions across channels
Challenges
Service Delivery improvement is high on agenda and focus is on front

office interaction
How do you execute a business process in distributed teams (across
geographies, partners, and functions)?
How do you seamlessly leverage the best expertise, especially if they
are not part of the call center operation or one organizational unit?
How do you manage business processes when customers contact
your company through many communication channels (phone,
email, web, fax, SMS)?
Capabilities (selection)
Multi-channel Management (voice, mail, fax, IVR, chat, sms) using

SAP Business Communication Management
Automatic Customer Identification
Interaction History
Customer Fact Sheet
Agent Inbox
E-mail editor / E-mail response management
Interactive Scripting
Social Case Management
Knowledge Search
Interaction Center Management & Analytics
SAP 2010 / Page 333
Social Service
Management
Activity
Management
Interaction
Management
Document
Management
Case
Management
Business Partner
Management
SAP CRM
SAP CRM Business Communication Mgmnt

Overview
Runs on MS SQL Server 2000/2005 och MS Windows Server 2000/2003. Next release will run on MS SQL Server 2005/2008 och MS
Windows Server 2003/2008
SAP 2010 / Page 334
SAP CRM
Managing Documents
Challenges
Paper-based document management prevents efficient

cross-organization processes
Capabilities
Linking of content and business objects
Technical Content Management functions such as folder

management and saving content to content servers
Social Service
Management
Activity
Management
Content versioning
Metadata management
Interaction
Management
Integration of Internet documents by entering the appropriate

URLs
Document
Management
Import and export of documents
Where-Used list
Content search
MS Word and Adobe PDF Document Template Management
Case
Management
Business Partner
Management
SAP CRM
SAP 2010 / Page 335
SAP CRM
Managing Cases
Challenges
Drive to Transform & Reform

Resource optimization requires major change or transformation
Governments across the globe are putting in major transformation agendas
Shared service is also seen as major enabler of transformation and efficiency
Ageing population derives higher demand for services with not appropriate budgets
Workforce Management Optimization
Distribute granular tasks to specialized individuals across the organization to be
executed in parallel
Managing sensitive information
Social Service
Management
Capabilities
Linking existing business objects to a case

Problems and solutions from the knowledge base
Assigning and displaying the involved parties
Linking electronic documents, such as forms and policies, to a case
Linking activities to a case
Case notes
Change history
Authorizations
Status management
Using reference categories
Reassignment of business partners in linked objects
Configuring repetitive tasks
Sending e-mails directly from a case
Linking related cases
Defining case closing profiles
Case archiving
SAP 2010 / Page 336
Activity
Management
Interaction
Management
Document
Management
Case
Management
Business Partner
Management
SAP CRM
Case Management
Case Search
Case Search
Criterias: Case ID, Type,

Description, External
Reference, Status, Prio,
Changed/Created On,
Reference Category,
IBase Component,
Product, Partner and more
Saved Search support
Search result list can be
sorted
filtered
exported to MS Excel
Search Scenarios
SAP 2010 / Page 337
Standard or
SAF/TREX search is a
very quick full text
indexed search.
Case Management
Functions 1/3
SAP 2010 / Page 338
Case Record can link

Partners
Activities and other
transactions
Reference objects
other Cases
any other object
(Customizing)
The record can be visualized
in a tree structure
A multitude of Classification
and categorization attributes
are available
Case Copy function can be
used to duplicate a case
according to customizable
settings.
New Transaction controls
which case data is transferred
to the new business
transaction
Partner determination can be
done via BAdI Interface
Case Management
Functions 2/3
SAP 2010 / Page 339
Case Hierarchies can be

used to group cases.
In addition Related Cases

offer non-hierarchical links.
Notes Log captures the

history of all entered text
notes
CRM Case uses the

Content Management to
link Attachments
Actions can be triggered

automatically or manually
to execute follow-up
functions / processes
Change History tracks all

changes of case attributes
Case Management
Functions 3/3
SAP 2010 / Page 340
Web Service
Enablement You
can generate Web
Services for case
search, case create,
case read and , case
change
Static and dynamic

(ACE)
Authorizations
restricting view and
editing capabilities.
SAP CRM
Managing Business Partners
Challenges
Benefit Fraud
Complex family groupings that change over time
Multiple, non-integrated sources of person data
Social Service
Management
Capabilities
One central source for person data (common for SAP

applications as well as other systems)
Activity
Management
Also used for legal entities (third party actors in the Social
Benefit process)
Interaction
Management
Flexible model to manage time-dependent person-to-person

relationships
Document
Management
Role concept (same individual can be customer as well as

employee)
Case
Management
Easy data model extension
User Master integration enabling secure self-services
Business Partner
Management
SAP CRM
SAP 2010 / Page 341
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 342
Agenda
10. Customizing
1.
2.
3.
4.
5.
6.
7.
8.
Application
Benefit Decision
Net Calculation
Change Processes for Social Service Plan
Deduction Plan
Deduction Plan Item
SAP 2010 / Page 343
Customizing Options in CRM / Application

Management
1. Transaction Type / SOA Type
SAP 2010 / Page 344
Social Application / SOA Type ( CRM

Transaction Type) Customizing
SAP 2010 / Page 345
Social Application / SOA Type ( CRM

Transaction Type) Customizing
SAP 2010 / Page 346
Customizing Options in CRM

Benefit Decision
1. Benefit Program / SSP Type

2. Item Proposal Strategy
3. Standard Delivery for SSP and Entitlement Determination
SAP 2010 / Page 347
Benefit Program / SSP Type

Customizing
SAP 2010 / Page 348
(CRM Transaction Type)
SSP Type Customizing
SAP 2010 / Page 349
SSP Type Customizing
SAP 2010 / Page 350
New SSP Creation, Date Profile
SAP 2010 / Page 351
New SSP Creation, Date Profile, Date Type
SAP 2010 / Page 352
New SSP Creation, Date Profile, Date Type
SAP 2010 / Page 353
New SSP Creation, Date Profile, Date Type,

Date Rule
SAP 2010 / Page 354

Date Rule -> Definition
SAP 2010 / Page 355

Date Rule -> Function
SAP 2010 / Page 356

Benefit Decision

SAP 2010 / Page 357
Item Proposal Profile Assignment
SAP 2010 / Page 358
Item Proposal Profile
SAP 2010 / Page 359
IPP BAdi implementation
SAP 2010 / Page 360

Benefit Decision

SAP 2010 / Page 361
IPP Standard Customizing Delivery
SAP 2010 / Page 362
Standard Customizing Delivery Partner

Function
SAP 2010 / Page 363
Standard Customizing Delivery: Due Date Rule

Type
SAP 2010 / Page 364
Standard Customizing Delivery: Frequency

Type
SAP 2010 / Page 365
Standard Customizing Delivery: Payment

Family
SAP 2010 / Page 366
Customizing Options in CRM / ERP for

1.CRM / ERP: Integration CRM / ERP

2.Entitlement Frequency
3.Calculation Exit Strategy
4.Handling of manual items
5.BRFPlus samples
SAP 2010 / Page 367
CRM / ERP: Integration CRM / ERP
As a first step you have to set up the system

integration between SAP CRM and SAP ERP like
described in the shown customizing activity on SAP
ERP side
SAP 2010 / Page 368


5.BRFPlus samples
SAP 2010 / Page 369
Entitlement frequency customizing
On SAP ERP side you have to do the customizing for the

entitlement frequency which is the
smallest granularity in which calculation results are stored and
on which follow-up processes like recalculations can be
supported e.g. calculations are always done on a daily
basis
Just maintain a frequency type you need and

mark it as an possible entitlement frequency
SAP 2010 / Page 370
Entitlement frequency customizing
On SAP CRM side you have then to assign your

entitlement frequency within the header customizing
of your transaction type
SAP 2010 / Page 371


5.BRFPlus samples
SAP 2010 / Page 372
Calculation Exit Strategy customizing
On SAP ERP you have a customizing activity to

maintai your Calculation Exit Strategies e.g.
to assign on SXP level

how/where you want to implement
your calculation rules. It is
possible to use a BAdI
implementation or to maintain
your rules within BRFplus.
For BRFplus you have to maintain

the BRFplus Application Name
and the corresponding BRFplus
Function Name. In addition you
could decide if the BRFplus Lean
Trace should be switched on i.e.
to log how/which rules have been
processed.
SAP 2010 / Page 373


5.BRFPlus samples
SAP 2010 / Page 374
Handling of manual items
You are able to create entitlement items with an gross entitlement amount manually within the
CRM WebClient UI. On SAP ERP side there is a customizing activity where you could
decide how these manual entered gross entitlement amounts should be handled within the
Calculation Exit Strategy:
SAP 2010 / Page 375
These gross entitlement amounts always are kept even if the implemented rules have
calculated a result for this item
These gross entitlement amounts are overwritten but a warning message is shown to the
caseworker
These gross entitlement amounts are just overwritten without any checks


5.BRFPlus samples
SAP 2010 / Page 376
Prerequisite
You have to know basics regarding Business Rule Engine Plus (BRF+)
You can find further information regarding BRF+ in SAP software development network (SDN):
www.sdn.sap.com
SAP 2010 / Page 377
BRFplus samples
Use TX BRP+ to start the BRFplus workbench on ERP side. SAP delivers 2 sample
Applications to ease the implementation of rules for the customer. The first Application is
PSSCS_TOOLS. Within this Application there are several Expressions of type static
method call. There are sample expressions showing you how to access replicated SAP
CRM data within the BRFplus workbench. You will find a step by step description how to
create your own expressions using this sample in the Appendix.
SAP 2010 / Page 378
BRFplus samples
The second Application is

PSSC00_SIMPLE_SAMPLE Within this
Application you find an easy example how to
calculate gross entitlement amounts.
Business logic of this sample:

The entitlement calculation period of the GED will be equal to the decision period of the calling SXP
The entitlement calculation results (items of the GED) will take over the entitlement periods of the
corresponding entitlement items and get each a constant amount of 2000
SAP 2010 / Page 379
BRFplus samples
Within the BRFplus application

PSSC00_SIMPLE_SAMPLE
SAP delivers the BRFplus
function Simple Sample which
runs in Event Mode i.e. the rules
are implemented via rule sets
and rules
Here you could see the

signature of this function. More
details about the context / result
of this function on the following
slides
Here you find the ruleset to be

executed by the function. More
details on this ruleset on the
following slides
SAP 2010 / Page 380
Simple Sample Signature (1)

Context
These 2 data objects are always filled when
gross entitlement calculation is triggered i.e.
BRFplus functions that contain rules for gross
entitlement calculation MUST also have this 2
data objects assigned for the context.
Besides the element

FREQ_TYPE (i.e. the
entitlement frequency) the
structure
PSSCS_SXP_DATA_BRFP is
part of the context i.e. you
can directly access all SXP
data contained in this
structure in BRFplus during
your rule processing
SAP 2010 / Page 381
Simple Sample Signature (1)

Result
The signature of the SIMPLE SAMPLE function contains a

Result of DDIC Type PSSCS_GE_RESULT_BRFP which is a
structure of 2 components GED (Gross Entitlement Document)
and ECR (Entitlement Calculation Result)
defining the entitlement calculation period on GED level
and a table of entitlement calculation results for the

entitlement calculation period.
SAP 2010 / Page 382
Ruleset
The ruleset RS_SIMPLE_RULESET

contains one rule to fill the GED
(Simple_Header_Rule) and one to determine
the ECRs
On a ruleset level you could

declare local variables.
Here it is a structure which
represents a single line in
the ECR result table (e.g.
like a working area in
ABAP)
SAP 2010 / Page 383
Header Rule
The GED part (entitlement calculation

period) of the result is filled with the decision
period of the SXP transferred to BRF+ by
the context
SAP 2010 / Page 384
Loop expression
Execute the Rule Item_Rule for each SXP

item
SAP 2010 / Page 385
Item Rule
Fill the local variable (one line of the ECR) with simple data
and insert this into the ECR table of the result. Done!
SAP 2010 / Page 386
Appendix
Step by step description how to create your own expression using SAP delivered
sample expressions:
1. Create your own application in BRF+
2. Create an BRFplus Data Object for the Context of your function (Name and Type to be used is
mentioned on the following slides) e.g. Name = PARTNER and Type = BU_PARTNER
3. Create an BRFplus Data Object for the Result of your expression (Type to be used is mentioned on the
following slides) e.g. boole_d
4. Create your own expression of type static method call and enter the name of the class you want to use
(all delivered classes are shown on the following slides) e.g. CL_PSSC00_BRFP_CHECK_REL
5. Maintain the Result-Data-Object for this expression (use the one you have created in step 3)
6. Create your function
7. Add on the Tab Signature in the section context your Context-Data-Object created in step 4 (this
context value will be used as input parameter for the static method called by BRFplus)
8. Maintain your rules using your new expression
SAP 2010 / Page 387
Context / Result / Behavior
Context needs this Data Object:

Name=PARTNER;
Type = BU_PARTNER;
Value = BP Number
Result:
Type = boole_d ;
Behavior: Checks if BP has relationship of type has_child
SAP 2010 / Page 388
Context: Label =versionid; Type = psscobjectversionid ; Value = SXP GUID

Result: Type = PSSCT_GE_GED_BRFP ;
Behavior: Returns table of GEDs assigned to SXP mentioned in the context
SAP 2010 / Page 389

Name= DATE;
Type = timepoint (elementar BRFplus type);
Value = Date
Result:
Type = PSSCS_PERIOD ;
Behavior: Maps the date defined in the context according to FREQ_TYPE ( =entitlement
frequency) e.g. if date = 15.01.2009; FREQ_TYPE = 003 ( =Monthly)
begin-date = 01.01.2009 and end-date = 31.01.2009
SAP 2010 / Page 390

Name= PERIOD;
Type = psscs_period
Value = Interval
Result:
Type = pssct_period (= Tablke of PSSCS_PERIOD) ;
Behavior: Maps / cuts the interval defined in the context according to FREQ_TYPE ( =entitlement frequency) e.g. if
interval = 15.01.2009 07.06.2009; FREQ_TYPE = 003 ( =Monthly)

SAP 2010 / Page 391

Name=PARTNER;
Type = BU_PARTNER;
Value = BP Number
Result:
Type = ad_pstcd1;
Behavior: Gets postal-code of the BP mentioned in the context
SAP 2010 / Page 392

Name=PRODUCT;
Type = char32;
Value = GUID of the product
Result:
Type = comt_product_id;
Behavior: Gets the product ID of the product
SAP 2010 / Page 393

Name=VERSIONID;
Type = psscobjectversionid ;
Value = SXP GUID
Result:
Type = psscs_sxp_data_brfp;
Behavior: Returns SXP data for a SXP GUID
SAP 2010 / Page 394
Customizing Options for Gross Payment

Item Determination
SAP 2010 / Page 395
Customizing: Step 1
Select Application Area (Social Services)
SAP 2010 / Page 396
Customizing: Step 2
Maintain Payment Frequencies and Frequency Mappings
SAP 2010 / Page 397
Customizing: Step 3
Maintain Due Date Rules and Payment Frequency Assignment
Details are already explained in

the former chapters
SAP 2010 / Page 398
Customizing: Step 4
Enter your payment

frequency type
SAP 2010 / Page 399
Enter your Due Date Rule

type to determine the
reference date
Customizing: Step 5
Define SXP Settings for Gross Payment Item Determination
Maintain per SXP type:

The
frequency mapping type

paymnet family
Due Date Rule for regular payments
Due Date Rule for underpayments
The Due Date Rule for the last date of approval i.e. if an SXP shall get approved later then this date this is
not possible anymore. You have to retrigger the entitlement calculation and gross payment item
determination
The
The
The
SAP 2010 / Page 400
Customizing: Step 6 (on CRM side)

Transaction Type Customizing
Also maintain your payment family and

your due date rules for regular and
underpayments on CRM transaction
type customizing
SAP 2010 / Page 401
Customizing: Step 7 (optional)
If an entitlement is open ended the GPID

will determine many GPIs. Via this
parameter you could inluence how many
items will be displayed as maximum in the
CRM WebClient UI
Possible use cases:

-fill customer fields
-set the Hold Flag on GPI-level to stop a GPI from
further processing.
- detect/collect Overpayment-GPIs for further nonstandard processing
SAP 2010 / Page 402
Customizing Options for Net Calculation
confidential

SAP 2010 / Page 404
Maintain Payment Parameters on SSP in CRM

IMG Customer Relationship Management Transactions Basic Settings Define Transaction Types:
Definition of transaction types Assignment of Business Transaction Categories Customizing header
SAP 2010 / Page 405
SAP Menu (ERP) Accounting Public Sector Management Social

Services Mass Processing Analyze Initial Net Calculation
SAP 2010 / Page 406
SAP 2010 / Page 407
SAP 2010 / Page 408
Customizing Options for Change Process

for Social Services Plan
SAP 2010 / Page 409

Customizing
SAP 2010 / Page 410

Customizing
SAP 2010 / Page 411

Customizing
SAP 2010 / Page 412

Customizing
SAP 2010 / Page 413
Customizing Options for Deduction Plan

Deduction Plan
SAP 2010 / Page 414
Deduction Plan Type - Customizing

The deduction plan type (1Order transaction type) specifies the parameters for the behavior of the deduction plan as
grouping entity in CRM only. It has no impact on the deduction execution in the ERP backend.
The transaction type SDP is

available in the customizing for
delivery.
All deduction plan types have to

be assigned to the Business
Transaction Category
BUS2000290, which is explicitly
defined for Deduction Plans
The default deduction plan

type SDP has the approval
strategy SOA and the case
assignment profile SOCIAL
assigned. And the activation
process is triggered
automatically. The settings
are identical with those for
SSP.
SAP 2010 / Page 415
Social Deduction Plan Transaction Type

Detailed Customizing
The default transaction type SDP

for Social Deduction Plan uses
the standard Status Object Type
(COH) of CRM Order.
SDP is delivered with its own set

of profiles. The Text Det.
Procedure is identical with the
profile for SSP as well as the
Action profile SDP_H and the
Partner Function category for
Organization Data determination.
The transaction type can be used

as a template and copied to
create your own transaction types.
SAP 2010 / Page 416
Social Deduction Plan - Partner Determination

Procedure
The existing partner function Main
Partner, Approved By and Employee
Responsible for SSP will be reused for
SDP Header Level as well as the access
sequences for their determination.
The Main Partner serves as the
contract partner for the public
organization. Therefore only one Main
Partner is allowed per SDP, while for
Employee Responsible up to 5 entries
are allowed. The Approver is optional
and unique as well.
Function
Text
Abbrev.
Function category
Usage
00000141
Main Partner
(CRM)
MAPA
Sold-To-Party
Customer
Relationship
Management
00001102
Approved By
APPB
Approved by
Customer
Relationship
Management
00000014
Employee
Responsible
ER
Person
Responsible
Customer
Relationship
Management
SAP 2010 / Page 417
Relationship
Cat.
Is responsible
BP for
Social Deduction Plan Date Profile
The start date and end date on the deduction plan

header define the maximum deduction time span
covered by the deduction plan. The start and end
date are not editable but automatically computed by
the system each time when the plan overview page is
called. The deduction plan start date is the earliest
deduction start date of all included deduction plan
items and the deduction plan end date equals the
latest end date of all included deduction plan items.
The End date is optional. If left empty, the deduction
plan is considered as running for infinity.
In addition to the start and end date the standard
date profile SDP also defines an approval date and
the decision date. Per default the decision date
equals the approval date.
SAP 2010 / Page 418
Customizing Options for Deduction Plan

Deduction Item
SAP 2010 / Page 419
Social Deduction Plan Item - Customizing Item

Category
The item category for deduction plan items can be defined by the customer in the IMG.
IMG Customer Relationship Management Transactions Basic Settings -> Define Item Categories
The item category usually reflects the

business scenario or purpose of the
deduction plan item. Three deduction plan
item categories (SDP1, SDP2, SDP3) are
included in the standard delivery.
Each deduction plan item category is

assigned to the Business Transaction
Category BUS2000290, which is
explicitly defined for Deduction Plans
Each of the three item categories references

to one of the three deduction process
categories: Third-Party Deduction, Allocated
Deduction and Withholding Deduction.
SAP 2010 / Page 420
Social Deduction Plan Item - Item Category

Determination
The item category determination is maintained

for the default transaction type SDP, so that the
three item categories SDP1, 2 and 3 are
available for selection within the transaction
type SDP.
Once selected, the item category cannot be
changed anymore. If you change your mind,
you have to delete and re-create the item
again.
SAP 2010 / Page 421
Deduction Plan Item - Item Category Detailed

Customizing
The item category uses
the standard Status
Object Type (COI) for
CRM Order.
The default item
Categories for Social
Deduction Plan SDP1,
SDP2 and SDP3 are
delivered with the same
set of profiles.
The Date Profile for
items (SDP_I) only
contain the start and
end date.
The default item
categories can be used
as a template and
copied to create your
own item category of a
certain processcategory.
SAP 2010 / Page 422
Social Deduction Plan Item - Partner

Determination Procedure
Social Deduction Plan has its own
Partner Determination procedure
(SDP_I) on the item level.
The deduct-from party will be derived
from the main partner by default each
time when a new deduction plan item is
created.
Each deduction plan item must have
exactly one Deduct-From party
assigned. The same is true for the
partner function Deduct-To Party, except
for items of item categories, which are
associated with item process category
withholding deduction. For those items,
Deduct-To-Party is not required.
Partner
Function
Text
Abbrev
Function cat.
Usage
Relationship
Cat.
00001104
Deduct-From
Party
DFRP
Sold-To Party
CRM
Is Payee for
00001115
Deduct-ToParty
DTOP
Payment
Recipient
CRM
Is Payee For
SAP 2010 / Page 423
From business point of view the

deduction will be posted to the
account of the sold-to party.
And the deduct-to party is the
recipient of the deducted
amount as payment.
Social Deduction Plan Item Date Profile

The Social Deduction plan items delivered in
standard shipment have all the same date
profile assigned. The start and end date
determine when a deduction shall start at the
earliest and when it as to terminate.
The start date entered here on the item level do
not have to match exactly the date when the
first deduction will be made. The deduction
execution is dependent on the due date of the
actual payment.
In the example on the left, the deduction item
start date is 30.06.2009, which could be
between two actual monthly payments, one for
29.06.2009 and one for 29.07.2009. In this
case, the first deduction will be made on
29.07.2009, as this is the next future payment
data.
The exact time is not relevant, as deductions
are planned on a daily basis. Therefore the time
column is defaulted.
SAP 2010 / Page 424
Agenda
1. Introduction
3. Benefit Decision
4. Net Calculation
8. Case Assignment
10. Customizing
11. Appendix
SAP 2010 / Page 425
Agenda
11. Appendix
1.
2.
3.
SAP 2010 / Page 426
Social Services BRFPlus

Periods and Dates in SAP Social Services
Social Services Payment Walkthrough
Index
1.Integration into social application

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment
2.Integration into social service plan

1.Case assignment
2.Entitlement determination
3.Integration into deduction plan

1.Case assignment
4.New action types

5.New expression types
SAP 2010 / Page 427
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 428
Validation of a social application
On the Social Application BRF+ is integrated to execute

form validation checks e.g. to check for constraints within
application dates
SAP 2010 / Page 429
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 430
Case assignment
Case assignment itself is not a new functionality. It is already

available since CRM 5.2. Also detailed RKT documentation is
available for this release.
You are now able to use BRFplus for the determination of the case
type and for the determination of a case
SAP 2010 / Page 431
BRFplus for case type determination
You have to use the names

CONTEXT_CTD for the context
and CTD_RESULT for the result.
The corresponding DDIC types are
shown in the red box on the right
The Case category

is optional
SAP 2010 / Page 432
BRFplus for case assignment

CONTEXT_CDS for the context
and CDS_RESULT for the result.
Business Partner
Function Mapping Table
as defined in
customizing for case
assignment
SAP 2010 / Page 433
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 434
Item proposal
Item proposal itself is not a new functionality. It is already available

since CRM 5.2. Also detailed RKT documentation is available for
this release.
You are now able to use BRFplus for the item proposal
This flag is useful if IPS is used

within the Social Service Plan
and you want to read data
from an social application.
If the flag is set the GUID of
the latest created SOA is
available within the BRF+
context for IPS. Via an Web
Request Read expression
(also mentioned in this
document) you are then able to
read the data.
SAP 2010 / Page 435
BRFplus for item proposal

CONTEXT_IPS for the context
and IPS_RESULT for the result.
Start and End date

of a SSP i.e.
decision period
Latest SOA GUID

mentioned on the
former slide
BP number of the applicant of the social

application
or
the main partner of the social service plan
This depends on which is the IPS calling
object
SAP 2010 / Page 436
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 437
SSP assignment
SSP assignment itself is not a new functionality. It is already

available since CRM 5.2. Also detailed RKT documentation is
available for this release.
You are now able to use BRFplus for the item proposal
SAP 2010 / Page 438
BRFplus for SSP assignment

CONTEXT_SSPDS for the
context and SSPDS_RESULT for
the result.
BP number of the
applicant of the social
application
SAP 2010 / Page 439
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 440
Case assignment & Entitlement Determination

Case assignment itself is not a new functionality. It is already available since CRM 5.2. Also detailed RKT
documentation is available for this release.
You are now able to use BRFplus for the determination of the case type, case category and for the determination of a
case
Customizing and BRFplus settings are the same like on the social application (mentioned before in this document)
because case assignment is a generic functionality
Entitlement determination is a new functionality on the Social service plan. You can find more details for this
functionality in the RKT material for CRM 7.0 EHP1
Technically the entitlement determination is realized by plugging the item proposal functionality into the social service
plan. Therefore the customizing and the BRF+ settings are the same like for the item proposal which was already
mentioned in this document
SAP 2010 / Page 441
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 442
Case assignment
Case assignment itself is not a new functionality. It is already available since CRM 5.2. Also detailed RKT
documentation is available for this release.
The new object deduction plan is also enabled for the case assignment functionality
You are able to use BRFplus for the determination of the case type, case category and for the determination of a case
Customizing and BRFplus settings are the same like on the social application (mentioned before in this document)
because case assignment is a generic functionality
SAP 2010 / Page 443
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 444
Action type CRM Activity

i.e. create a CRM activity
Common data
Because this action can be used at

several process steps in CRM it is
technically necessary to distinguish
between calling this functionality
within the processing of an one order
object or outside the one order
processing. For social services the
(BRFplus enabled) process steps
that are within the one order
processing are:
Validation
Item
Case
SSP
proposal
assignment
assignment
Entitlement
determination
Here you have to flag the checkbox

and to assign the leading one order
object
SAP 2010 / Page 445
Assignment of business partners and business partner functions
SAP 2010 / Page 446

Assignment of Texts
You have the possibility to assign

text as free text or as T100
messages. You can select via
this toggle button
SAP 2010 / Page 447

Filling customer extension fields
SAP 2010 / Page 448
Action type CRM case note

Create a CRM case note
Common data
Define a criteria that the result of this

expression should fulfill
SAP 2010 / Page 449
Create CRM case note

Note

this toggle button
SAP 2010 / Page 450
Create CRM case note

Filling note attributes
SAP 2010 / Page 451
Action type CRM WR Message

i.e. create a message for a Web Request

this toggle button
SAP 2010 / Page 452
Action type CRM Message
i.e. create a message for the application log
SAP 2010 / Page 453
Index

1.Validation
2.Case assignment
3.Item proposal
4.SSP assignment

1.Case assignment

1.Case assignment
4.New action types

SAP 2010 / Page 454
Expression type CRM BP Read

Read BP attributes of a selected BP
(also multiple attributes possible)
Determine
here the BP ID
of the BP you
want to read
data from
You can use this

button to
automatically bind
the result object to
selected attributes.
Just create a new
data object (choose
type element if you
just select one
attribute or
structure/table for
multiple attributes),
press this button
and save afterwards
Select here via

checkbox the
attribut(es) you
want to read
SAP 2010 / Page 455
Expression type CRM Order Read

Read order attributes of a selected order
(also multiple attributes possible)
Determine
here the order
GUID of the
oreder you
want to read
data from
SAP 2010 / Page 456
Expression type CRM Search
i.e. search for cases, order object, one order items

Here you can select the
object you want to search
for:
Case
One Order
One order item
The result of the search

expression is a list of
GUIDs. Hence, the result
object has to be a table
with one column of type
text with at least 32
characters.
Here you can state
your predecessor
object to search for
example for: 1.) one
order objects within one
special case
2.) an one order item
within one special one
order object
SAP 2010 / Page 457
Search parameters single value and multi value
Some parameters
allow a multi value
selection. Here you
are able to add or
delete additional
parameters if multi
value is allowed for
the selected attribute.
Just one
single value
is allowed
SAP 2010 / Page 458

Source type: Web Request Field
You can select the source

here i.e. the envelope or
the Web Request
If you have selected the
source type Web
Request Field you can
select here a Request
category. Below the
corresponding tree
structure allows you to
select a single attribute
Just in the validation step of the social
application you can leave this
parameter empty (it will be derived
automatically).
Otherwise you have to derive the Web
Request One Order GUID here (e.g.
the context for item proposal process
step provides the latest social
application GUID. Otherwise you could
also use a one order search expression
to determine this GUID)
SAP 2010 / Page 459

Source type: Envelope Field
If you have selected the

source type Envelope
Field you can select here
which field you want to
read. Below the
corresponding type and
description is displayed
SAP 2010 / Page 460
Agenda
11. Appendix
1.
2.
3.
SAP 2010 / Page 461

Index
1.Periods and Dates in SAP Social Services

a) Business Rules
b) Date Fields and Periods in Social Services
2.Configuration of ERP and CRM; Period & Date Tool
SAP 2010 / Page 462
Business Rules for the Due Date of Financial

Benefits
When scheduling benefit payments you need to be decide the following questions. The standard options from SAP
are listed below:
Per which period is the benefit calculated?

System Options:
month
week
day
and multipliers
Per which period is the benefit paid out?

System Options:
month
week
day
SAP 2010 / Page 463
Frequency Mapping
First day of entitlement period is relevant earlier payment period

Last day of entitlement period is relevant later payment period
After determining the payment period how do you find the due date?
Standard Options:
Gross Payment Frequency
and multipliers
An entitlement period belongs to which payment period?

Standard Options:
Gross Entitlement Frequency
End of Period
Beginning of Period
Today
plus offset days to be added or subtracted

and use of factory calendar
Due Date Rule

for regular payment
for underpayment
Periods and Dates for Financial Benefits

In SAP for Social Services, periods and dates are used to determine:
1.
2.
3.
4.
For which time the applicant wants financial support

Which time the decision covers
For which time a single benefit is granted
Until when a benefit decision may be approved before it is too late for the next
payment cycle
5. The payment schedule for benefits
6. The exact payment date for a benefit and its deductions; different benefits may be
grouped and paid out together
7. The reference date as of when a benefit payment is elapsed and hence to be
considered as overdue
8. When overdue payments have to be paid out
9. How far into the future unlimited benefits are calculated and scheduled
10. By when forecasts of unlimited benefits (such as old age pensions) have to be
renewed or updated
SAP 2010 / Page 464
Periods in Social Services
Application Period
Start and End Date of the Period the application is made for. If the
application refers to several benefits, the application period begins at
the earliest benefit start date and end at the latest benefit end date.
Decision Period
Time frame a social services decision covers. Determined automatically

from SOA with date profile on SSP Type. Defines whether a decision
is a new decision for this period or a follow-up SSP.
Benefit item start and end date
Period within the decision period for which a certain benefit is granted;
can be entered manually or determined automatically.
Entitlement period
Period within in validity of the benefit with a stable benefit amount. The
entitlement period embraces all entitlement frequency periods in a row
for which the amount remains the same.
For varying benefit amounts, a new entitlement period is created for
each amount. sub-periods
Payment Frequency Period
The time slice following the frequency type a benefit is paid out for.
The decision is a sequence of payment frequency periods. Only when
the amount changes a new period starts.
Used in Gross Payment Documents and Net Calculation Documents.
Concatenated on the CRM UI, there are NCDs for every payment
frequency period; meaning: even if the amount is identical, these are 2
different payment frequency periods.
SAP 2010 / Page 465
Periods for the Financial Processing of

Benefits and Deductions
Gross Entitlement Frequency
Period
Single period for which the gross entitlement has been determined, i.e.
without considering deductions or previous payments.
Gross Payment Frequency

Period
Single period for which the gross payment amount has been
determined, i.e. considering previous payments but not deductions
NCD Payment Frequency

Period
Single period for which the net calculation amount has been determined,
after deductions.
SAP 2010 / Page 466
Dates for Application Processing and

Decision Making
Reference Date
Determines in SSP underpayment; in an SDP, the deduction item may

not start before the reference date
Approval Date
Date when SSP or SDP is approved; latest date of approval is

defined through Due Date Rule; after this date, an approval is not
possible; Gross Entitlement Calculation has to be executed again and
usually issues an underpayment
SAP 2010 / Page 467
Use of Due Date Rules

Due Date Rules are used for several purposes:
Determine the due date for a regular payment

Determine the due date for an underpayment
Determine the date for the latest approval of an SXP. After that date, the entitlement needs to be calculated again,
and this will result in an underpayment.
Delimit the net calculation into the future.
Determine the latest date to execute net calculation in order to guarantee that the net calculation data is present
according to the limitation time interval.
SAP 2010 / Page 468
SSP Date Management: New SSP
SAP 2010 / Page 469
Dates and Periods before Entitlement

Determination
Benefit start and end date

must be within decision
period; decision period is
defaulted into benefit
maintenance
SAP 2010 / Page 470
Date and Periods after Entitlement

Determination
Detailed list in sync with

generated entitlement
periods
SAP 2010 / Page 471
Date and Periods after Entitlement

Calculation
SAP 2010 / Page 472
Net Calculation Display: Date and Periods in

Shortened Periods
SAP 2010 / Page 473
GPD Items for shortened start week in SSP

and regular weeks
For first (shortened) week of benefit payments
SAP 2010 / Page 474
For regular benefit payments from 06.07. until 27.12.2009
GPD Items for shortened final week in SSP

For last (shortened) week of benefit payments
SAP 2010 / Page 475
GPD Header
GPD Header for Decision Period 01.01.2009 to 01.01.2010
Decision Date on SSP is translated into

Reference Date = derived from due date rule for this SXP Type
Break Date = end date of latest entitlement frequency period to
be processed as underpayment; entitlement frequency periods
after break date will be paid out as regular payment
SAP 2010 / Page 476
Social Deduction Plan Date Profile
The start date and end date on the deduction plan

header define the maximum deduction time span
covered by the deduction plan. The start and end
date are not editable but automatically computed by
the system each time when the plan overview page is
called. The deduction plan start date is the earliest
deduction start date of all included deduction plan
items and the deduction plan end date equals the
latest end date of all included deduction plan items.
The End date is optional. If left empty, the deduction
plan is considered as running for infinity.
In addition to the start and end date the standard
date profile SDP also defines an approval date and
the decision date. Per default the decision date
equals the approval date.
SAP 2010 / Page 477
Social Deduction Plan Item Date Profile

The Social Deduction plan items delivered in
standard shipment have all the same date
profile assigned. The start and end date
determine when a deduction shall start at the
earliest and when it as to terminate.
The start date entered here on the item level do
not have to match exactly the date when the
first deduction will be made. The deduction
execution is dependent on the due date of the
actual payment.
In the example on the left, the deduction item
start date is 30.06.2009, which could be
between two actual monthly payments, one for
29.06.2009 and one for 29.07.2009. In this
case, the first deduction will be made on
29.07.2009, as this is the next future payment
data.
The exact time is not relevant, as deductions
are planned on a daily basis. Therefore the time
column is defaulted.
SAP 2010 / Page 478
Change Process Create Follow-up Deduction

Plan
In the following example only item 10 is affected by the change process
because the change process is triggered between the validity period of the
item.
Items of the activated SDP
Change Process
Triggering Date:
14.07.2009
Items of the follow-up SDP:

Item 10 has been truncated
with start date equals the new
decision start date 14.07.2009
SAP 2010 / Page 479

Plan - 4
Item of the activated SDP
The copy of the original item has

new end date (16.10.2009) one
day before the stop date
(17.10.2009).
The second part is the resumed
deduction item starting with the
resume date 10.11.2009 and
ends with 16.12.2009 (= the
original end date 22.11.2099 plus
the missing 4 weeks due to the
stop).
The invalidation item has start
date equals the stop date and
end date one day before the
resume day.
SAP 2010 / Page 480
Stop Date:
17.10.2009
Resume date:
10.11.2009
Index
1.Periods and Dates in SAP Social Services

a) Business Rules
b) Date Fields and Periods in Social Services
2.Configuration of ERP and CRM; Period & Date Tool
SAP 2010 / Page 481
Periods & Due Date Rules: Entitlement and

Payment Frequencies
Frequency Type Customizing
Dynamic Generation of
Periods
Simple
Multiple
GED 02.02.2009 - 08.03.2009

GED Item 1
GED Item 2
CW 07
CW 06
GPD
02.02.2009 - 08.03.2009
GPI 1
GPI 2
CW 08
CW 09
CW 10
GPI 3
GPI 4
GPI 5
SAP 2010 / Page 482
CW 11
Periods & Due Date Rules: Mapping of

Entitlement and Payment Frequency
Frequency Mappings
No Mapping
Category required
Mapping
Category required
(BAdI)
GPD 02.02.2009 - 08.03.2009

GPI 1
GPI 2
GPI 3
GPI 4
GPI 5
Payment Frequency Period 01.02.2009 28.02.2009

01.03.2009 31.03.2009
SAP 2010 / Page 483
Periods & Due Date Rules: Deriving the Due

Date of a Payment
Due Date Rules
DD05
DD04
15th Day of Month

respecting Factory
Calendar
CW 06
CW 07
Last Day of
Month respecting
Factory Calendar
DD06
CW 08
CW 09
CW 10
Last Day of Month -4

Days for Bank Transfer
ZD09
SAP 2010 / Page 484
Wednesday in
2nd Week of Next
Month
Customizing: Step 1
Maintain payment frequencies and frequency mappings
Details are already explained in the former

chapters
SAP 2010 / Page 485
Customizing: Step 2
Maintain Due date rules and payment frequency assignment
Details are already explained in the former

chapters
SAP 2010 / Page 486
Customizing: Step 3
Maintain payment family
Enter your payment

frequency type
SAP 2010 / Page 487
Enter your Due Date Rule

type to determine the
reference date
Customizing: Step 4
Define SXP settings for gross payment titem determination
Maintain per SXP type:

The frequency mapping type
The paymnet family
The Due Date Rule for regular payments (RP)
The Due Date Rule for underpayments (UP)
The Due Date Rule for the last date of approval (LA) i.e. if an SXP shall get approved later than this
date this is not possible anymore. You have to retrigger the entitlement calculation and gross payment item
determination
SAP 2010 / Page 488
Customizing: Step 5 (on CRM side)

Transaction type customizing
IMG in the CRM System CRM Transactions Basic Settings Define Transaction
Types
Also maintain your payment family and your due date

rules for regular and underpayments on CRM
transaction type customizing
SAP 2010 / Page 489
Customizing: Step 6 (optional)
If an entitlement is open ended the GPID

will determine many GPIs. Via this
parameter you could inluence how many
items will be displayed as maximum in the
CRM WebClient UI
Possible use cases:

-fill customer fields
-set the Hold Flag on GPI-level to stop a GPI from
further processing.
- detect/collect Overpayment-GPIs for further nonstandard processing
SAP 2010 / Page 490
Agenda
11. Appendix
1.
2.
3.
SAP 2010 / Page 491

Scenario Overview
In our example, Samantha Wilson is entitled to a housing

allowance, which is calculated and paid weekly. This benefit is
subject to 20% tax. The system deducts this tax automatically
from the housing allowance.
Later, Samantha asks to also deduct her TV license fee from her
benefit and to pay this fee directly to the collection agency. This
will be processed through a manually created social deduction
plan.
SAP 2010 / Page 492
Housing Allowance SSP
SAP 2010 / Page 493
Housing Allowance GPI details

Totals
SAP 2010 / Page 494
Net Display on SSP
Click on date to see the details
SAP 2010 / Page 495
SAP 2010 / Page 496
Social Billing Run Parameters
SAP 2010 / Page 497
Social Billing Run Execution
SAP 2010 / Page 498
Billing Documents generated for SSP
SAP 2010 / Page 499
Billing Document Display in PSCD

Samanthas benefits
account in PSCD
Business Transaction
Payment Frequency Period
SAP 2010 / Page 500
Reference to Net Calculation Item
Voluntary Deduction SDP
SAP 2010 / Page 501
TV-Licence Fee Deduction Item
SAP 2010 / Page 502
Net Display on SDP
Click on date to see the details
SAP 2010 / Page 503
New Net Calculation Document with

Deduction Created (older ones revised)
SAP 2010 / Page 504
Re-run Billing
SAP 2010 / Page 505
New Billing Document Created (older Billing

Document Cancelled)
SAP 2010 / Page 506
Reversal Billing Document
SAP 2010 / Page 507
New Billing Document
SAP 2010 / Page 508
Net calculation Document Status updated

(Revised Reversed and Open Billed)
SAP 2010 / Page 509
Invoicing Run
SAP 2010 / Page 510
Invoicing Document
SAP 2010 / Page 511
Posting Document I Summarized Level
SAP 2010 / Page 512
Posting Document II Details of BP Items
SAP 2010 / Page 513
Posting Document with Manual Deduction Summarized
SAP 2010 / Page 514
Posting Document with Manual Deduction Details
SAP 2010 / Page 515
Billing Documents updated with invoicing

document reference
SAP 2010 / Page 516
Account Balance with open credit positions
SAP 2010 / Page 517
Payment Run
SAP 2010 / Page 518
Payment cleared. No open items.
SAP 2010 / Page 519
Payments made to Samantha
SAP 2010 / Page 520
Deduction posting item ready for distribution
SAP 2010 / Page 521
Revenue Distribution
SAP 2010 / Page 522
Deduction distributed to Final Recipient

Account
SAP 2010 / Page 523
Deduction Item distributed
SAP 2010 / Page 524
Create Posting document on the final recipient

account
SAP 2010 / Page 525
Total Deduction Posted to Final Recipient`s

Account and Ready to be Paid
Reference to Revenue Distribution Run
Business Transaction = Revenue Distribution
SAP 2010 / Page 526
Result of Scenario
Out of the original housing allowance of 140 Euro, Samantha

Wilson now obtains a regular payment of 82 Euro as housing
allowance per week. 28 Euro of tax are withheld at the Social
Services department. The Social Services agency also
arranges regular transfers to the TV Lisence Fee Collection
Agency on Samanthas behalf so that Samanthas does not fall
behind anymore.
In the future, the Social Services department will have to
schedule regularly the entitlement calculations and net
calculations as well as the follow-up processes in accounting.
SAP 2010 / Page 527

Social Services RCRM20

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Social Services RCRM20

Uploaded by

Copyright:

Available Formats

SAP Social Services Management for

Workshop RCRM20: "SAP Social Services Management for Public Sector,

SAP 2010 / Page 2

SAP 2010 / Page 3

Social Services Strategy

Key trends driving change in Social Services

Increased need for

SAP 2010 / Page 4

Lower or nonexistent pensions

There are two Social Services segments

SAP solution for Social Service Agencies

SAP offers a comprehensive

Front Office / Back

SAP Front Office

SAP for Social Services & Social Security

(Monetary Benefits Income Assistance)

Social Services / Care

Collection / Contribution Management

Mass Payment Services

Analytics for Social Services

SAP 2009 / Page 6

SAP solution for Social Service Agencies

IP Telephony, Fax, Mail,

SAP for Social Services & Social

(Monetary Benefits Income Assistance)

SAP 2009 / Page 7

Collection / Contribution Management

SAP Customer Interaction

Social Services / Care

Mass Payment Services

Analytics for Social Services

SAP Enterprise Portal

SAP Front Office

Not all positioned customers are

Social Services & Social Security

Caisse Nationale dAssurance Vieillesse

Collection / Contribution Management

Mass Payment Services

SAP 2009 / Page 8

Analytics for Social Services

Social Services / Care

Istituto Nazionale Previdenza Sociale

Social Services & Social Security

Florida Department of Revenue, US

Collection / Contribution Management

Mass Payment Services

SAP 2009 / Page 9

Analytics for Social Services

Social Services / Care

Ministry of Finance, Costa Rica

Social Services & Social Security

Collection / Contribution Management

Mass Payment Services

Analytics for Social Services

Social Services / Care

Social Services & Social Security

Collection / Contribution Management

Mass Payment Services

SAP 2009 / Page 11

Analytics for Social Services

Social Services / Care

Social Services & Social Security

Collection / Contribution Management

Mass Payment Services