Payment

Update Online

©SAP AG 2005

© SAP AG 1
 Overview

Necessary Customizing Steps

©SAP AG 2005

© SAP AG 2
 Payment Update

EA-
EA-
FI PS

Invoice
Invoice Online update

only for
Payment RFFMS200 new Payment
customers

Online update

Payment RFFMS201 Payment

© SAP AG 2005

With Release mySAP ERP2005 payments are updated online in Funds Management. The use of programs
RFFMS200 (Payment selection) and RFFMS201 (Create FM Documents for Payments without Invoice
Reference) is not necessary any longer, thus it is not possible to activate or run these programs when
activating online updates of payments (exception: existing customers already working with RFFMS200).
The online update of payments is only available for new customers.
Existing customers already working with RFFMS200 can’t activate the payment update online. There is
no migration path to migrate from RFFMS200 to online payment update. Although the activation of
RFFMS200 in Customizing (“Settings for the Payment Transfer”) is not visible any longer, RFFMS200
once activated in previous releases, will remain active. Like that there’s no change for existing customers
regarding payment updating.
Migration for existing customers is planned for mySAP ERP2007.

© SAP AG 3
 How does it work?

EA-
EA-
FI PS

Invoice
Invoice Online update

Entry
View
Payment
Document
Document
Splitting
Splitting

Internal
Split Payment
View
Online update Payment

© SAP AG 2005

The payment document is enhanced with Invoice information (KNBELNR) and split according to this
characteristic.
The enhanced and split payment document is the basis to change the status of the paid invoice in Funds
Management from “invoice” to “paid”.
Activation of the new general ledger and of document splitting is a prerequisite to use online update of
payments. For more information see “mySAP ERP 2004: Learning Map for Financial Accounting
Consultants“, especially topics „Introduction to New General Ledger in mySAP ERP 2004“ and
„Document Processing“.

© SAP AG 4
 How it works – Example – Step I

Post 2 Invoices:

Online Update in Funds Management:

© SAP AG 2005

Invoice is updated online in Funds Management.

© SAP AG 5
 How it works – Example – Step II

Post 1 Payment and clear both invoices:

Document Splitting of Payment:

Online Update in Funds Management:

© SAP AG 2005

Document Splitting splits Payment document according to split characteristic KNBLENR and creates
additional lines (see table FAGL_SPLINFO).
Payment is updated online in Funds Management based on splitted document.

© SAP AG 6
 Differences to Payment Selection (RFFMS200)

Handling of partial payments for invoices:

Online payment update uses splitting procedure (update without

splitting procedure is not possible)

Payflag:

The payflag is set to „X“ as soon as the corresponding invoice is

reduced in FM completely, independet whether the whole document
bundle is closed or not.

Profit and Loss Adjustment

with the activation of New General Ledger the program SAPF181 is not
needed any longer, the adjustments are done online

© SAP AG 2005

Using online payment update, there is no choice between „splitting procedure“ and „without splitting
procedure“. Partial payment of an invoice that is divided between several account assignments in Funds
Management is always updated in proportion to the given amounts for each invoice in Funds Management.
Whereas the payment selection sets the payflag to „X“ when the whole document bundle is closed in FI,
the online payment update sets the payflag as soon as the corresponding invoice is reduced completely in
FM. Basically it is not necessary to set the payflag when working with online payment update. It is done to
improve the performance of the commitment carry forward. If new documents are posted referencing a
completely reduced invoice, the payflag is deleted.
User Exit EXIT_SAPLFMPA_002 Deactivate Conversion of Credit Memos doesn’t work for online
payment update.
Readjustment of Profit and Loss for cash discounts and exchange rate differences is not needed any
longer, but distributed online via Document Splitting.

© SAP AG 7
 Common features of RFFMS200 and online update

Conversion of bank clearing has to be activated in Customizing

Critical business cases

existing critical business cases will remain valid for online payment
update

© SAP AG 2005

The updating of the bank account clearing is carried out in the same way as via the payment selection
(RFFMS200). This means that payments, which are posted on the bank clearing account with financial
transaction 80 will be updated in FM statistically using the amount types 210/260. After offsetting the
payment on the bank clearing account against the bank account the statistical items in FM are reversed and
replaced by the items with amount types 200/250 as usual. This functionality has to be activated in
customizing.
All existing critical business cases (already defined for RFFMS200) will remain valid for the time (see
OSS note 400924). Additionally the following business cases will be determined as critical:
In the case of the active updating the bank account clearings the reset clearing has to be always carried
out with a reversal. It will be made sure on this way that the payment in the FM will be reversed as well.
The invoice reference of the payment must not be changed in the transaction FB02.

© SAP AG 8
 Prerequisites for online payment update - overview

New customer

Activation of online payment update

Use of New General Ledger

Activation of Document Splitting with characteristics KNBELNR

and VOBELNR

© SAP AG 2005

The online payment update requires the use of the new general ledger and suitable Customizing for
document splitting. Here you can use the standard splitting method 0000000012 as a basis. You must also
define the fields KNBELNR and VOBELNR as document splitting characteristics of the general ledger.
For further details see the following slides.
For more information about New General Ledger and Document Splitting, please refer to Verweis auf
RKT.

© SAP AG 9
 Overview

Necessary Customizing Steps

©SAP AG 2005

© SAP AG 10
 Acitvate Payment Update Online

© SAP AG 2005

IMG: Public Sector Accounting->Funds Management Government->Actual and Commitment

Update/Integration->Integration->Define Settings for Payment Transfer
There is no possibility anymore for new customers to activate RFFMS200

© SAP AG 11
 Define Ledgers for General Ledger Accounting

© SAP AG 2005

IMG: Financial Accounting Global Settings (New)->Ledgers->Ledger->Define Ledgers for General

Ledger Accounting

© SAP AG 12
 Define Document Splitting Characteristics for General
Ledger Accounting

© SAP AG 2005

IMG: General Ledger Accounting (New)->Business Transactions->Document Splitting->Define

Document Splitting Characteristics for General Ledger Accounting
For the online payment update the system needs to split based on the fields KNBELNR and VOBELNR.
In addition to KNBELNR and VOBELNR we recommend to add FIPOS as well. FIPOS is needed If you
want to create online adjustments for cash discounts (similar to the functionality, SAPF181 provided in
previous releases) or if you want to update payments without invoice reference.
The Split Characteristic “FIPOS” includes the Funds Center, meaning the document is split by
combination Commitment Item/Funds Center.
Don’t set the Zero Balance Indicator for Split Characteristics FIPOS, KNBELNR or VOBELNR! When
you set the indicator, the system checks during posting whether the balance for the characteristic is equal
to zero. If this is not the case, the system generates in the document additional clearing lines on clearing
accounts that achieve the zero balance.

© SAP AG 13
 Activate Document Splitting

splitting method
0000000012
recommended

© SAP AG 2005

Splitting method 0000000012 is the default method for document splitting.

In case delivered functions of splitting method 0000000012 are not sufficient for your needs and you want
to make changes or enhancements, you can define your own splitting method (it is not allowed to change
standard splitting methods!). To do this you have to follow the steps „Define Document Splitting Method“,
“Define Document Splitting Rule“ and „Assign Document Splitting Method“ in the IMG path Financial
Accounting (New)->General Ledger Accounting (New)->Business Transactions->Document Splitting-
>Extended Document Splitting
If you want to update payments without invoice reference in Funds Management you have to define your
own splitting method (see following slides).

© SAP AG 14
 Settings for payments without invoice reference - I
Define Constant for nonassigned processes:

Assign values:

© SAP AG 2005

Similar to RFFMS201 you can update payments without invoice reference statistically on a special FM
account assignment.
After creating the constant, you have to assign the FM account assign where the payments are updated
statistically. Please note that only those fields are available as constants, that have been defined as split
characteristics earlier!
IMG: Financial Accounting (New)->General Ledger Accounting (New)->Business Transactions-
>Document Splitting->Edit Constants for Nonassigned Processes

© SAP AG 15
 Settings for payments without invoice reference - II

Create Business transaction variant for Transaction 1000 Payments:

© SAP AG 2005

IMG: Financial Accounting (New)->General Ledger Accounting (New)->Business Transactions-

>Document Splitting->Extended Document Splitting->Define Business Transaction Variants
You can copy your Variant from the Standard Variant 0001

© SAP AG 16
 Settings for payments without invoice reference - III

Create Document Splitting Rule for Business Transaction Variant:

Create
Create rule
rule for
for your
your own
own
splitting
splitting method,
method, Business
Business
Transaction
Transaction 1000
1000 (Payments)
(Payments)
and
and Transaction Variant you
Transaction Variant you
created
created inin previous
previous step
step

© SAP AG 2005

Standard Splitting Methods can‘t be changed, thus you have to define your own splitting method (use
customer-namespace): IMG: Financial Accounting (New)->General Ledger Accounting (New)->Business
Transactions->Document Splitting->Extended Document Splitting->Define Document Splitting Method
After defining your own Splitting Method, you have to assign the document splitting rules. SAP
recommends to copy the rules from a Standard Splitting Method and use them as templates for your own
set of rules. IMG: Financial Accounting (New)->General Ledger Accounting (New)->Business
Transactions->Document Splitting->Extended Document Splitting->Define Document Splitting Rule
In addition to the copied rules coming from a standard Splitting Method, you have to create a rule for the
Business Transaction Variant you created in the previous step.
Don’t forget to assign the Splitting Method you created for Document Splitting! IMG: Financial
Accounting (New)->General Ledger Accounting (New)->Business Transactions->Document Splitting-
>Extended Document Splitting->Assign Document Splitting Method

© SAP AG 17
 Settings for payments without invoice reference - IV

Maintain item categories to be edited:

© SAP AG 2005

Assign the defined constant to item categories Customer, Vendor and Cash Account.

© SAP AG 18
 Settings for payments without invoice reference - V

Assign Business Transaction Variant to Document type:

© SAP AG 2005

IMG: Financial Accounting (New)->General Ledger Accounting (New)->Business Transactions-

>Document Splitting->Classify Document Types for Document Splitting

© SAP AG 19
 Copyright 2005 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

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

© SAP AG 2005

© SAP AG 20