Download SAP Credit Management

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Transcript
S/4HANA Finance
New Deployment and Integration Options
Katharina Reichert, February, 2016
Customer
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
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 assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
6
Series on Receivables – Every other Thursday
 Jan 14 - Introduction to Receivables – high level overview
 Jan 28 – “The SD Credit Check is gone!” What is new in
Credit Management in S/4HANA
 Feb 11 – Tools to Lower DSO
 Feb 25 – Deployment and Integration Options: Deeper
Dive on HANA Cloud Platform apps and Central Finance
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
7
LAB PREVIEW
SAP Receivables Management is a portfolio of automation solutions
Accounts Receivable – standard process automation
HCP Fin Fact
Sheet
Manage all financial accounting–related aspects of customer accounts receivable.
HCP Credit
Central Finance
Credit Evaluation and Management
Integrationprocesses and portfolio deployment
Embed proactive credit management in transactional
analysis.
HCP Customer
Billing and E-Invoicing
Deploy a customer bill payment portal or an e-billing process. Payment Mgmt
Dispute Resolution
Clarify and resolve customer payment disputes quickly and efficiently.
Central Finance
deployment
Collections Management
Proactively manage customer collections and customer service.
Central Finance
deployment
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
8
Customer Financial Fact Sheet
Purpose
SAP Customer Financial Fact Sheet (HANA Cloud Platform App)
The app that helps the sales executive
view all his customers’ data
and
collaborate with his back office
“Retired” iOS version of Customer Financial Fact Sheet
SAPcompany.
AG. All rights
© 2016 SAP SE or an SAP©2011
affiliate
Allreserved.
rights reserved.
Internal
1
10
Benefits
SAP Customer Financial Fact Sheet (SAP HANA Cloud Platform)
With this app:
LAB PREVIEW
A sales representative can access financial data, sales volumes, and invoices real time with selfservice access. She can collaborate and exchange information about the customer with her
accounting back office directly.
Without this app:
She needs to call her back office, or send emails, faxes,… in order to obtain the required information.
In turn, the back office then needs to contact her. This is slow and resource-intensive.
With the SAP Customer Financial Fact Sheet (SAP HANA Cloud Platform version), you combine the
state-of-the-art SAP Fiori user experience with your existing SAP ERP 6.0 backend landscape. And
since it runs in the cloud, there is minimal IT effort required.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
11
Enable easy-to-use mobile access to key customer data
SAP Customer Financial Fact Sheet (HANA Cloud Platform App)
LAB PREVIEW
SAP Hana Cloud Platform
SAP Customer Financial
Fact Sheet
https
SAP
Customer Landscape
 The HCP app offers web-based access to data from the
SAP ERP system (6.0 release or higher)
-
Accounts receivable data (like overdues)
Credit Management data
Collections and Dispute Management
 The user can access data via smartphone, tablet, or PC
 A secure online connection (example: VPN) is required if
the access is made possible outside the corporate network
SAP Cloud Connector (OP)
LWMFI001 add-on*
ERP
FI – AR
*Technical add-on for FinFactSheet
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
12
Functionality
SAP Customer Financial Fact Sheet (SAP HANA Cloud Platform)
LAB PREVIEW
 Search for customers
 List of customers assigned to a user (example: customer of a
sales executive)
 Customer detail view






Outstanding & overdue amounts
Invoice list & invoice details (PDF)
List of disputed invoices
Sales volume
Credit data
Display & creation of notes
 The user’s authorizations in the ERP backend are considered
Screenshot: Customer overview
screen in phone size
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
13
Customer Feedback Needed!
Are you mainly interested in viewing data (like we have it on the Phone version)?
Or do you really want your Sales to create disputes & promises to pay (like we have it on the
native iPad version)? For example, one Top 5 Life Sciences company told us last week, that in
Europe and in the US they do not want this, but for India & South America it would be essential.
Do you sees use cases / a target audience other than “classic” mobile? Given that the app is
rendering in a browser and could run on desktops as well.
For your IT specialists: Is HCP as such a topic for you? Are you planning other HCP projects?
(which would imply that the entry barrier for our solutions in the respective organization would
be lower)
Email [email protected] with feedback or to set up a call/feedback session!
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
14
Credit Information
The HCP App SAP Credit Management Integration helps you…
LAB PREVIEW
…to use external credit risk information in order to
make better credit decisions
and to automate the monitoring of
yours customers’ credit risk
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
16
SAP Credit Management: Risk Monitoring
LAB PREVIEW
Credit Decisions
 Automated (standard)
 Manual (exception)
Customer Portfolio
Customer Credit Scoring
(automated)
Internal data (like payment behavior)
ERP
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Alerts (exception)
SAP Credit Management
External data (credit reports from credit agencies)
HCP Credit Management Integration
17
SAP Credit Management: Integration of Credit Risk Agencies Today
Credit Risk Agency 1
SAP Credit
Management
SAP
NetWeaver
Credit Risk Agency 2
PI
Credit Risk Agency 3
Credit Risk Agency 4
On Premise




Integration of external credit agencies done by the customer / during the implementation project
Significant implementation effort per interfaces (= per agency)
Interfaces are XML based
XI / PI is required
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
18
SAP Credit Management: Integration of Credit Risk Agencies Future
LAB PREVIEW
XML
SAP Credit Management
HCP App
Credit Risk
Information
Credit Risk Agency 1
Credit Risk Agency 2
Credit Risk Agency 3
Credit Risk Agency 4
On Premise
HANA Cloud Platform (HCP)




Integration of external credit agencies done by an HCP app
Maintenance of interfaces to credit agencies done by HCP service provider (= SAP)
Bulk of the data of external credit reports remains in HCP app
Few data (like external rating, foundation date of a company,…) is transferred to SAP Credit Management in
order to enable the scoring of customers based on external and internal data
 Credit controller can access detail data on HCP app with one click from SAP Credit Management screen
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
19
HCP App Credit Management Integration: General Assumptions
LAB PREVIEW
 You as an SAP customer still sign contracts with the various credit agencies in order to gain access their credit
reports
 From a legal point of view the external credit agencies will not accept SAP in a role as a consolidator / distributor
of credit reports
 SAP roles remains purely technical, SAP does not become the owner of the data, SAP will not use this data for
own purposes.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
20
HCP App Credit Management Integration: Benefits
LAB PREVIEW
 Significant reduction of TCO for SAP customers:
 No initial setup costs to integrate external credit agencies
 No maintenance costs to keep the interfaces “running”
 No XI / PI required
 Faster implementation of Credit Management on premise projects, as the sub-project to integrate
credit agencies is replaced by setting up the connection to the HCP app.
 You as an SAP customer have a broader choice of external credit agencies.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
21
Integration of External Credit Agencies: Use Cases (I)
 Search / lookup of business partners
 Business partner name, address attributes,… are sent to the credit agency
 The credit agency returns a hit list with business partners that fit the search criteria, including the business
partners’ unique identifiers
 The user selects ”the right” business partner, the respective unique identifier is updated in SAP Credit
Management
 Get credit report of a business partner
 The business partner’s unique identifier, product code and reason code are sent to the credit agency
 The credit agency returns the requested credit report for the business partner, including rating, proposed credit
limit,….
 The credit report is stored in the app and data like rating, legal form, foundation date and industry code is
updated in SAP Credit Management
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
22
Integration of External Credit Agencies: Use Cases (II)
 Manage business partner monitoring
 Register a business partner for monitoring updates
 Stop monitoring updates for a business partner
 Process monitoring updates
 The credit agency sends update for business partner who are registered for monitoring, usually with a reason
code (what has changed?), changed values (old & new) or a full new credit report
 Data need to be updated in SAP Credit Management if necessary
 Trigger investigation / research request
 A business partner requested during the search is not found in the database of the credit agency
 An investigation / research request can be filed in order to trigger further investigations (offline) by the credit
agency
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
23
Process Flow: Step 1
 Initial situation: business partner exists in SAP Credit
Management, but no external credit information is
available
 Internal score is 60
 Risk class derived from internal score is “Very high
default risk”
Action: User presses the button “Manage Credit
Reports”
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
24
Process Flow: Step 2
 A browser window opens, the HCP app Credit
Management Integration starts automatically on the
screen “Manage Customer Credit Reports”
 The address & identification data of the customer is
automatically transferred to the HCP app
 No credit report has been imported, yet
 The user presses the button ”Import Credit Report”
which will allow him to choose a credit agency, a
product and finally import the credit report
Action: User presses the button “Import Credit Reports”
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
25
Process Flow: Step 3
 The credit report is imported
 The external rating is
automatically transferred to SAP
Credit Management
 Thanks to the credit event
functionality…
 the internal score got
recalculated automatically
 the internal risk class got
recalculated automatically (to:
“very low default risk”)
 Further follow on processes could
have been triggered due to the
credit event (ex.: calculate credit
limit)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
26
Process Flow: Step 4
 By a mouse click the user can
view the full credit report
 The full credit report and the
history of credit reports is stored
in the app
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
27
Process Flow: Step 5
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
28
Customer Payment Mgmt
Your AR team is tied up
Processing repetitive customer inquiries
 Requests for invoice copies
 Explanations of why they are underpaying
 Requests for updates on dispute status
Matching incoming payments with open items
 Long telephone calls with AP clerks
discussing which invoices should be
cleared with which payments
 Resolving underpayments
 Changing master data (bank accounts,
credit cards, notification preferences)
 Period-end balance confirmations
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
30
The world of Digital Business
Today’s consumers expect to help themselves
Access account data directly
Global 24 x 7 access
View dispute status and updates
Simplified online collaboration
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
31
Give direct access with SAP Customer Payment Portal
Let customers access their account details with self-service scenarios
Your Customers
SAP Customer
Payment Portal
1
FI-AR Account:
Customer 1
2
FI-AR Account:
Customer 2
3
View and pay bills
FI-AR self-services
SAP ERP
FI-AR
FI-AR Account:
Customer 3
SAP Customer Payment Portal enables your customers to
 View their master data and inform you of any changes
 View bills
 Make payments
 Start the dispute resolution process
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
 Perform annual balance confirmations
Internal
32
Adopt hybrid customer self-service scenarios in less than a month!
SAP Hana Cloud Platform
 Easy access via web browser
 Designed for non-SAP users
Customer access
via any web
browser
Customer Payment Portal
 Fast deployment with hybrid model
 Quick go-live with instant results
 Reduced upfront investment
 No hardware required
 Global availability
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Cloud delivery with outof-the box integration
SAP Cloud Connector
No changes to
existing A/R
processes
(OP)
Your SAP ERP
Internal
33
It’s a “quick win” for your AR team…
Improved billing processes:
 Lower cost of billing by eliminating printing and postal charges
 Customer participation in electronic business without EDI
Faster payment processing:
 Efficient processing of payments and deductions
 More precise cash management and improved liquidity planning
Native data integration:
 Data integration with accounts receivable and cash management
 Improved dispute and collections processes
SAAS SOLUTION WITH STANDARD PROCESSES THAT CAN BE RUNNING IN WEEKS
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
34
…and a win for your customers, too!
Secure payments:
 Simplified and secure processing of electronic payments with better control over the time of payment and
management of the outgoing cash flow
Invoices:
 Fewer accounting and settlement errors with immediate access to invoice copies
 No need to wait for opening times of AR departments
Integration:
 Upload of invoices into AP system without reformatting of data
 Easy notification of master data changes
AVAILABLE IN ANY WEB BROWSER
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
35
Lab Preview
Architecture Details
SAP Hana Cloud Platform
SAP Customer
Payment Portal
Benefits of SAP HANA Cloud Platform
JCo
 Customer does not need to operate a Java
platform
https
SAP
Customer Landscape
SAP Cloud Connector
(OP)
RFC
ERP
FI – AR
 Small IT footprint especially for medium and small
customers
 Changes and updates are instantly available
 Faster innovation with less IT effort
 Easy to start, low entry barrier to setup test / demo
systems
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
36
Initial release supports 3 customer-facing processes
 Match payments with invoices

Customer selects payments and the open items that
should be cleared

This creates a payment advice that gets sent to AR
clerk for processing

Avoids long telephone conversations
 Pay my bills

Customer selects open item and creates payment

Create inquiry for underpay
 Manage my accounts

Customer can view master data to confirm accuracy
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
37
Match payments with invoices
 Customers can assign payments
to invoices and send payment
advice notes to the biller
 Assigned items can be changed
up until the point when the biller’s
accounting clerk has processed
them
 The responsible accounting clerk
can access the payment advice
notes out of his SAP inbox
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
38
Pay my bills
 Customers can see all of their
bills and credit notes on the
internet
 If billing document contains SD
line items, then these can be
displayed; Financial
documents do not have this
line item detail available
 They can download bill data in
PDF or XML format
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
39
Pay my bills
 Customers can pay their
invoices using credit cards
or bank collection (FI-AR)
 Online credit card
authorization and
settlement supported
(planned)
 Partial payments, offset with
credits and cash discounts
are supported
 When a customer has paid
an invoice, a payment
method, bank details, or
credit card details are
entered in the open items
that belong to the selected
invoice
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
*credit cards in Release 2
40
Maintain my accounts - customers can view their master data
 Customers can display their
data to check for accuracy
 In a future release, they will be
able to notify you of changes:

Change their address,
bank or credit card data

Grant or withdraw
automatic debit
authorizations

Modify their notification
preferences
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
41
Payment history and invoice history
Payment history
Filter payments by time, status, bank
Payments can have a different status
(in progress, processed)
depending on the backend
ERP processes
Invoice History
Open invoices from the last 60 days are shown by
default in the portal
Scheduled payments can be
cancelled provided that no
payment run took place
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
42
Create Inquiry for a partial payment
 Customers that indicate a
partial payment may need to
document an inquiry
 Configuration on whether this
functionality is mandatory is
part of customizing
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
43
Lab Preview
Roadmap
Future direction: delivery subject to customer prioritization
Payment advice creation
Support for dispute resolution
View master data
Pay invoices with credit card
Pay invoices with Bank transfer
Support for FI-CA
Jumpstart configuration
Multi backend-System Scenario*
XML invoice download
Q3 2016
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Future Releases
44
Central Finance
Central Finance as a non-disruptive step towards system
consolidation
Central Finance
Accounting Interface
Central Finance
Accounting Interface
Business Mapping
/ MDG
ECS Error Correction
Suspense Accounting
Business Mapping /
MDG
Error correction
handling

Transaction-level data
replicated into instance
with latest SAP
innovations, HANA
optimizations and cutting
edge UI

Existing systems remain
untouched

Benefit from harmonized
master data for
processing, planning,
consolidating, and
reporting
Universal Journal Entry
SAP ERP
SAP ERP
Central Finance instance
SAP HANA
Universal
Journal Entry
Central Finance instance
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
46
Open Item Management in Central Finance
Open items are replicated into Central Finance. To avoid duplication of effort to pay/clear, there are the following options:
Local
Open item
Central Finance
SLT
Open item
Clearing
Tech
Cleared
Local
Central Finance
SLT
Open item
Other*
Open item
SLT
Clearing
Other*
Replicate open item and automatically/technically clear in
Central Finance
•
Available as of 1503
•
Continued open item management in source system
Not suitable for central reporting or central processing (since
clearing status not correct)
Replicate open item and clearing status in Central
Finance
Centralization of finance operations reporting and central
process orchestration
•
Pilot version available with OP 1511 Shipment**
•
•
Continued open item management in source system
A/R and A/P reporting (cross-system view of customer
or vendor account)
•
Central dispute management, collections worklist and
credit evaluation scenarios
•
Shared services and invoice management scenarios
Clearing
Pilot now
Local
Open item
Tech
Cleared
Central Finance
SLT
Open item
Replicate open item and automatically/technically
cleared in local system
•
**Not yet available
•
Centralized open item management in Central
Finance system
Clearing
•
No posting back to the source systems
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Similar to existing ALE scenarios, these are customerspecific scenarios where consistency in certain local
logistics processes must be determined in a case-bycase analysis
Pilot Q3
*ALE, RFC, other
**must apply with Development for access to pilot functionality
47
Centralization of finance operations reporting and central process
orchestration
Pilot Availability
1511*
Central Finance
Cross-system view of customer or
vendor account / real-time operational
reporting with Fiori user experience
A/R reporting:
Customer
Analysis
Open Item
Key processes managed centrally,
executed centrally whenever possible
Postings are seamlessly triggered in
local FI systems
Centralize process know-how in
shared service center
Harmonized, mapped master data
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
ERP
Dispute Lists
Collections
Worklists
SLT
Open Item
ALE / Web
Scenarios
Local logistics
processes access local
FIN data for
consistency
Some processes
require manual steps
for postings in local
systems (example:
credit memo posting
upon dispute
resolution)
Credit
Management
Real-time operational reporting
SAP HANA
Replication of payments, clearing status, cost
differences, discounts, etc into central system
Reporting-related processes could then be
orchestrated or run on centralized data set: cash
application, credit exposure calculations, dunning,
collections prioritization
Mapping of customers/vendors via Central Finance
mapping functionality – optional integration with
SAP
*mustMDG
apply with Development for access to pilot functionality
48
Centralization of A/R reporting and central A/R process
orchestration
Planned Availability
Real-time operational reporting with Fiori
user experience with cross-system view of
customer account
1511*
Central Finance
SLT: Open Items & Clearing Status
Central dispute management
Cross-system root cause analysis
•
Drill-down takes you back to local system logistics
object
Central collections prioritization and team
management
View linked logistics document
Post credit memo
Local
•
ALE / Web scenarios
A/R reporting:
Customer
Analysis
Credit
Management
Dispute Lists
Collections
Worklists
Process receivables (local open items)
Real-time operational reporting
•
Promises-to-pay documented locally
Check central credit limit
•
Correspondence pulled from local system
Update credit exposures
SAP HANA
Central credit evaluation and management
•
Local systems report customer credit exposures
via existing ALE scenarios
•
Central system calculates/manages credit limits
•
Central credit reporting
*must apply with Development for access to pilot functionality
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
49
Example: Central dispute resolution orchestration
Local System
Local Acct team posts
incoming payments
Central Finance
Dispute created into
CF system
UNDERPAYMENT
Manage and update disputes
Dispute
Central Dispute Lists
Cross-system root cause
analysis
View linked logistics document
Customer owes $100
Post credit memo
Customer pays $60
SAP HANA
Notes:
Disputes can be created from the standard SAP ERP
transactions
When viewing a dispute in the local Process Receivables,
the CF system dispute is displayed
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
50
Central process execution for AP / AR processes
Central Finance
Reducing the number of external bank
accounts / fees
Central Payments
Central Internal Payment
ERP
Central External Payment
Open Item
Open Item
BANKS
Limit credit charges in case of overdraft
Central Incoming Payment
Bundle external payments and save charges
on cross border payments
SAP HANA
Real status of open item tracked in Central Finance system
Bank connections maintained in CF system (optional SAP
MDG)
HANA optimization of payment proposal generation
Bank statements
processed in Central
System
Q3 2016
Business Values
Credit, Collections, Disputes
Open items
technically cleared in
source system via
report
Pilot Availability
All open item related processes must be executed in Central
Finance instance as well (example: dunning, collections,
disputes)
When logistics processes need data, they must be changed to
pint to Central Finance to avoid inconsistencies
Centralize payment knowledge and optimize
process in shared service center
Use SAP Standard interface for uploading
bank statements to a central platform
Monitoring of bank communications and
transactions
*Needed for direct bank connectivity
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
51
Central process orchestration in Central Finance for A/R processes:
Source system is SAP ERP
Central Collections
Central Dispute Management
Central Credit Management
Operational reporting / analysis views (Collections
Progress, Promises to Pay) in Fiori with no latency
Operational reporting / analysis views (Open
Disputes) in Fiori with no latency
Fiori analytics for credit limit utilization
Worklist view is in LEGACY GUI with duplicated
customer per backend system
Latest Fiori user experience for end-to-end process of
dispute resolution (role-based access for updating
disputes)
Centralized team management based on customer
contact results
Process Receivables in source systems is in legacy
UI
Case details will include linked business objects, but
SOME JUMP BACKS WILL NOT WORK – e.g.
connect via ALE scenario to billing documents,
orders, customer data, etc; these will be in legacy
user interface
No local installation of Collections necessary if your
SAP ERP >4.7; small amount of customizing effort in
source system required (FI-AR integration settings)
Resulting credit memos would have to be created
manually in source system (it is a manual process
oftentimes today); this will ensure balanced books in
source system
No local installation of Dispute necessary if your
system >4.6C; small amount of customizing effort in
source system required (FI-AR integration settings)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
(Credit Management has not yet been renovated in
Fiori)
Credit checks performed in local systems would refer
to limits in Central Finance system; exposure updates
occur via existing Web Services
No local installation of Credit necessary if your
system >4.6C; small amount of customizing effort in
source system required (FI-AR and SD customizing)
*must apply with Development for access to pilot functionality
52
Central process orchestration in Central Finance for A/R processes:
Source system is not SAP ERP (Dispute, Credit)
Central Dispute Management
Central Credit Management
The Dispute Management ES bundle enables external application to
search for, display, create, and change a dispute case.
Local system would use the existing XML interfaces (Credit
Management Enterprise Services bundle) to feed central credit
management system
Centralized monitoring of dispute resolution process (root causes,
length of resolution time, etc)
No support for automated FI-AR integration (posting write-offs, credit
memos at the conclusion of the resolution process; dunning
integration).
Centralized monitoring of credit risk possible in Central Finance
system, along with central calculation of credit rating and central limit
management
Customer-specific project required to perform system-specific data
mapping and processes
In the implementation project, code must be written to invoke the
services from the source application
*must apply with Development for access to pilot functionality
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
53
Central process orchestration in Central Finance for A/R processes:
Source system is not SAP ERP (Collections)
Central Collections
Central Collections
(from CF documents)
(Substitute System)
Operational reporting / analysis views (Collections Progress, Promises to
Pay) in Fiori with no latency. Centralized team management based on
customer contact results.
Operational reporting / analysis views (Collections Progress, Promises to
Pay) in Fiori with no latency. Centralized team management based on
customer contact results.
Worklist view is in Fiori with duplicated customer per backend system. For
non-SAP open items, Process Receivables allows agents to:
• View invoices, payments, outstanding amounts,…
• View & create promises-to-pay (for invoice level, but not on customer
level)
• View & create standard (tied to invoices) or customer-initiated dispute
cases
• View & create resubmissions and notes
• View & create customer contacts
• Create and send correspondence
Worklist view is in LEGACY GUI with duplicated customer per backend
system. For non-SAP open items, SAP GUI Process Receivables allows
agents to:
• View invoices, payments, outstanding amounts,…
• View & create promises-to-pay at customer level (not on invoice level)
• View & create customer-initiated dispute cases
Case-by-case analysis of whether functionality provided by the substitute
system approach is sufficient for collections teams.
•
•
•
View & create resubmissions and notes
View & create customer contacts
Create and send correspondence
Case-by-case analysis of whether functionality provided by the substitute
system approach is sufficient for collections teams.
*must apply with Development for access to pilot functionality
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
54
Non-SAP-sourced data in Central Finance scenario
Process
Orchestration
Central Finance
Central Finance
Collections
Worklists
Dispute Lists
*
Dispute Lists
Process
Orchestration
Open Item
SLT
Non-SAP
ALE / Web
ERP
Scenarios
Open Item
Real-time operational reporting
SAP HANA
Open Item
SLT
Non-SAP
ALE / Web
ERP
Scenarios
Collections
Worklists
“Substitute system”
Open Item
Real-time operational reporting
*extra copy of data into
substitute system
SAP HANA
All transactions reposted into ACDOCA.
All transactions reposted into ACDOCA.
One central Fiori Collections worklist generation include non-SAP
sourced data as well as SAP-sourced data (multiple lines per customer)
Transfer data into Substitute client from non-SAP system directly using Collectionsspecific BAdI
Process Receivables in Fiori includes promises at invoice level,
standard and customer-initiated disputes (with some limits for process
integration), FI correspondence, and resubmissions.
One central SAP-GUI based Collections worklist generation include non-SAP
sourced data as well as SAP-sourced data (multiple lines per customer)
If SD detail required, use ALE scenario (not recommended)
Process Receivables for substitute system includes promises at customer level,
customer-initiated disputes (without process integration), FI correspondence, and
resubmissions.
If SD detail required, use ALE scenario (not recommended)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
55
Non-SAP-sourced data in Central Finance scenario
All transactions reposted into ACDOCA.
Process
Execution
Central Finance
Dispute Lists
SLT
Open Item
Non-SAP
ALE / Web
ERP
Scenarios*
*if necessary
Collections
Worklists
1 central collections worklist generated in
Fiori that includes non-SAP sourced data as
well as SAP-sourced data
Customer appears on worklist 1 time
Open Item
Real-time operational reporting
SAP HANA
If SD information required, ALE scenario
could be built (not recommended)
Full FI integration for disputes, promises, etc
available for non-SAP sourced data
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
56
Connecting non-SAP systems and R/3 < 4.7 to SAP Collections
Management: Setup
• In your Central Finance system, you have set up
and additional client as a substitute system
using a configuration wizard
• Then, create “mirror” company codes in the
substitute system. These represent the company
codes in the original system.
• See the IMG documentation for details
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
© SAP AG 2009. All rights reserved. / Page 57
57
Connecting non-SAP systems and R/3 < 4.7 to SAP Collections
Management: Data

Transfer the customer master data from the original system
into your substitute system.
 Implement method CMD_GET_EXT_DATA in BAdI
FDM_MIRR_CUSTOMER_MASTERDATA to fetch the
relevant data
 Initially do a full upload
 Then delta upload on a regular basis

Transfer the document data
 Implement method GET_DATA in BAdI
FDM_COLL_GET_DATA to fetch the relevant data
 Initially do a full upload
 Then delta upload on a regular basis (example: each night)

SAP delivers already BAdI implementations which facilitate
the data (master data, document data) for R/3 4.6c  no
additional effort needed in this area for R/3 4.6c backends
 Refer to the BAdI documentation in the IMG
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
58
Central process execution in Central Finance for A/R processes:
Source system is not SAP ERP
Central Collections
Central Dispute Management
Central Credit Management
Operational reporting / analysis views (Collections
Progress, Promises to Pay) in Fiori with no latency
Operational reporting / management views in Fiori
with no latency
Worklist and processing views are in Fiori
Centralized monitoring of dispute resolution process
(root causes, length of resolution time, etc)
Local system would use the existing XML interfaces
(Credit Management Enterprise Services bundle) to
feed exposure data related to logistics (sales orders,
deliveries); financial side of exposure would be fed by
Central Finance postings
Centralized team management based on customer
contact results
Full FI-integration for promises to pay, disputes,
correspondence
Limitations possible in terms of drill-back to non-SAP
source systems for sales orders or other logistics
document
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Full FI-AR integration (automation or opening/closing;
posting write-offs, dunning integration)
Centralized monitoring of credit risk possible in
Central Finance system, along with central
calculation of credit rating and central limit
management
Customer-specific project required to perform
system-specific data mapping and processes,
especially when logistics systems need to call to the
CF system for credit checks
59
Thank you
Contact information:
[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.