Sizing Industry SolutionPublic Sector - Collection and Disbursement

IS-PS-CA

SAP AG 2002, IS-T/RM-CA 2

IS-PS-CA Objectives

Provide accounts receivable/payable and collection functionality for Public Sector organizations

Transfer of posting data from non-SAP billing systems Create and track receivables Generate Dunning notices and process other dunning activities Receive and settle incoming payments Process payment program and returns Create correspondence Send out invoices

Handle high volumes of Business Partners Contract Accounts Contract Objects Documents/Open items

SAP AG 2002, IS-T/RM-CA 3

Where do I have to go?

SAPNET: Alias: QUICKSIZER

Enter a customer number and project number

For the quantity-based sizing of IS-PS-CA, please use mySAP Insurance

If you have any questions concerning IS-PS-CA functionality and sizing please contact:

Volkmar.zahn@sap.com

Frank.schmahlfeldt@sap.com

SAP AG 2002, IS-T/RM-CA 4

Why can I use mySAP Insurance for Sizing IS-PS-CA (1)

FI-CA

IS-PS-CA FS-CD

Public Sector Collectionsspecific functionality

InsuranceCollection & Disbursementspecific functionality

SAP AG 2002, IS-T/RM-CA 5

Why can I use mySAP Insurance for Sizing IS-PS-CA (2)

Relationship between IS-PS-CA & FI-CA & FS-CD FI-CA is the generic kernel for all industry specific contract accounts

receivables and payables solutions IS-PS-CA is the Public Sector specific contract accounts collections

and disbursement solution for high-volume processing consisting of FI-CA and Public Sector industry specific enhancements “on top” of FI-CA

FS-CD is the insurance specific collections and disbursement solution consisting of FI-CA and insurance industry specific enhancement “on top” of FI-CA

Due to the fact that both IS-PS-CA and FS-CD are based on the same FI-CA kernel, a good estimate for the IS-PS-CA database and an initial estimate of the CPU sizing can be done by using the mySAP Insurance sizing for FS-CD.

SAP AG 2002, IS-T/RM-CA 6

User and Quantity Based Sizing

User-based sizing (1)

Use standard SAP R/3 Enterprise FI Users

For those users working directly in IS-PS-CA

Quantity structure-based sizing

Use mySAP Insurance – Collections and Disbursement sizing considering the guidelines for the Quicksizer described on the next slide(s)

Considering that due to the high process flexibility of IS-PS-CA and FI-CA the concrete sizing (especially CPU Sizing) needs to be verified based on the concrete customizing and configuration of a customer installation

Remark 1) For IS-PS-CA basically quantity based sizing can be used. However, if FI processes run parallel to the batch processes identified in the quantity based sizing, a user based sizing for FI etc. might be relevant. Then, the results of the user-based sizing have to be added to the quantity based sizing.

SAP AG 2002, IS-T/RM-CA 7

mySAP Insurance Sizing for IS-PS-CA

Chapter “Master Data” relevant / not relevant Total Number of Business Partners Number of contract accounts Number of insurance objects (Remark 1)

Number of brokers Avg. number of customer assigned to a broker

Chapter “Subledger Documents” relevant / not relevant Subledger document – postings Subledger document – payments

Remark 1: Insurance objects = Contract Objects

Quantity Based Sizing (1)

SAP AG 2002, IS-T/RM-CA 8

mySAP Insurance Sizing for IS-PS-CA

Chapter “Batch Processes” relevant / not relevantPayment plan transfer (remark 1,2)Payment plan executionPayment runPayment lotDunningBroker Report (Transfer/Post) Insurance InvoicesAccount Statement (remark 3)

Chapter “Online Processes”Display account balance

Remark 1: “Payment plan transfer” of FS-CD is used as the synonym process to “IS-PS-CA Idoc based Document transfer from External Billing System”

Remark 2: Only the “Max. Number of Objects created by Day” & “Execution Period” is relevant, do not use the other fields.

Remark 3: Creation of account statements is very performance intensive, which can be identified when reviewing the results for the distribution tables. Changes in the time interval might be helpful. E.g. the creation of account statements is a periodic job which can run on a weekend at month end rather than each day for 2 hours

Quantity Based Sizing (2)

SAP AG 2002, IS-T/RM-CA 9

Restrictions

General restrictions The CPU sizing does only cover the main processes of IS-PS-CA.

Additional CPU power is expected to be necessary in case of extensive use of add. IS-PS-CA processes and for all customer specific functionality implemented with IS-PS-CA

The Database and CPU Sizing does not consider the use of CO-PA (Profitability Analysis) in conjunction with IS-PS-CA.