release info (english)

Release Notes for SAP for InsuranceRelease 4.72

Release Notes

© Copyright 2004 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, 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.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

1.1 FS-CD Collections/Disbursements 11.1.1 Account Balance Display 11.1.2 Additional Account Assignments (Changed) 11.1.3 Archiving for Tax Reporting Argentina (Changed) 11.1.4 Archiving 21.1.5 Authorization Objects 31.1.6 Balance Interest Calculation 41.1.7 BAPIs in Contract Accounts Receivable and Payable 41.1.8 Broker Collections 51.1.9 Business Information Warehouse 71.1.10 Cash Desk 81.1.11 Cash Journal 91.1.12 Closing Operations 101.1.13 Coinsurance 101.1.14 Submission of Receivables to Collection Agency 111.1.15 Company Codes 121.1.16 Creation of Correspondence 141.1.17 Creation of Tax Items 141.1.18 Document Display for a Business Case (New) 141.1.19 Insurance-Specific Dunning 151.1.20 Dunning 171.1.21 Changes to Collections/Disbursements Area Menu 181.1.22 Extended Message Management 191.1.23 New and Changed Events 201.1.24 Conversion of Finnish Bank Statement to MultiCash (Enhanced) 231.1.25 Foreign Currency Valuation (Extended) 231.1.26 Transfer Post Items to Other Responsible Company Code 241.1.27 Funds Management 241.1.28 IDoc Interfaces for Communication with Ext Systems 271.1.29 Changes in IMG for Contract Accounts Receivable and Payable 281.1.30 Information System 291.1.31 Deferral and Installment Plan 301.1.32 Integration 321.1.33 Interest Calculation 331.1.34 Insurance Invoices 341.1.35 Post Documents (Extended) 341.1.36 Business Locks 341.1.37 Mass Activities 351.1.38 Master Data 351.1.39 Evaluation of Open Items 361.1.40 Payment Plans 36

______________________________________________________________SAP AG iii

SAP-System Inhaltsverzeichnis SAP AG______________________________________________________________

1.1.41 Processing Incoming and Outgoing Payments 391.1.42 Creating Payment Plan Items 401.1.43 Payment Transactions 401.1.44 Postings and Documents 421.1.45 Prenotifications 481.1.46 Collections in the Print Workbench 481.1.47 New Reports 491.1.48 Processing Returns 491.1.49 Inclusion of Schedule Managers in Contract Receivable and 501.1.50 Stop Future Payment (Denmark) 511.1.51 Tax Reporting in Contract Accounting (New) 511.1.52 Credit Splitting 521.1.53 Write-Offs 521.1.54 Generic Withholding Tax Reporting (Enhanced) 53

______________________________________________________________SAP AG iv

SAP-System Inhaltsverzeichnis SAP AG______________________________________________________________

1.1 FS-CD Collections/Disbursements

1.1.1 Account Balance Display

Use

Restriction of Item Selection

If you select the button Period for Item Selection (F7) on the initial screen of the account balancedisplay, you can restrict the period that the system uses for selecting the items in the account balance.

Context Menu in the Account Balance

You can call up a context menu by clicking on the right mouse button when the cursor is on an item in theaccount balance. In events 1247 and 1248, you can adjust the functions of the context menu to meet yourrequirements or add to them.

Effects on Customizing

Define the required function modules for events 1247 and 1248 in the Implementation Guide for ContractAccounts Receivable and Payable under Program Enhancements -> Define Customer-SpecificFunction Modules.

1.1.2 Additional Account Assignments (Changed)

Use

From SAP for Insurance 4.72, the insurance type is no longer a required entry field in the additionalaccount assignments for insurance. You can now process the additional account assignments using DirectInput, and do not have to include them as customer includes in the appropriate structures in the paymentplan interface.

1.1.3 Archiving for Tax Reporting Argentina (Changed)

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following new archiveinfo structures for archiving objects FKK_GENREP, FKK_GENREV, and FI_MKKGENS are deliveredand must be used for Argentina:

o SAP_FICA_ARREP1

o SAP_FICA_ARREV1

o SAP_FICA_ARRES1

You must use these info structures in conjunction with the following function modules:

o FKK_AR_EVENT_0515

______________________________________________________________SAP AG 1

SAP-System______________________________________________________________

o FKK_AR_EVENT_0520

o FKK_AR_EVENT_0525

The system calls these function modules to include Argentina-specific fields from the tax reporting tablesin the archive info structures above. Only by using these info structures with these function modules doyou ensure that the system correctly connects the Argentine tax reports to the archive.


You need to assign the above function modules to each of the relevant tax events: 0515, 0520, and 0525.You do so in Customizing for Financial Accounting, under Contract Accounts Receivable andPayable -> Basic Functions - > Tax Reports -> Tax Reporting - Argentina -> Basic Settings ->Activate Recording of Tax Data.

1.1.4 Archiving

Use

Document Archiving

In future, the program for archiving documents (RFKKAR10)

checks whether the balance of the document is zero (check DOCUMENT-01).

Two new events are available:

o In event 0501 you can check document headers in blocks.

o In event 0505, you can carry out installation-specific checks at document level.

If you need data from other tables for the document check in event 0505, you should read this data inadvance in event 0501 in order to avoid adverse effects on performance. In event 0501, you can select allof the data required for the documents transferred and save it to the local memory. This means that youcan carry out all additional checks for event 0505 with no individual database access.

The archiving log of the document archiving device has been change over to the Archive DevelopmentKit (ADK) standard log. You can now no longer display the details of documents that cannot be archivedin the detailed error log. Instead, click on the document number in the detail log to go to the documentdisplay.

The number of archived entries in the individual tables is no longer displayed for the individualdocuments. These totals are now only displayed for all archived documents. However, you can displaythe archive entered before deletion using the Archive File Browser (transaction AS_AFB) and thuscheck the archived structures/content.

Archiving Information about the Foreign Currency Valuation

You can use the new archiving object FI_MKKVAL to archive the data that arises from the foreigncurrency valuation. The prerequisites for the archiving are described in the documentation for reportRFKKAR36.

Archiving Clearing Histories

You can archive clearing histories with the new archiving object FI_MKKPCR. The prerequisites for the

______________________________________________________________SAP AG 2

SAP-System______________________________________________________________

archiving are described in the documentation for report RFKKAR41.

Archiving of Doubtful Entries

You can archive data for doubtful receivables with the new archiving object FI_MKKDRVA. Theprerequisites for the archiving are described in the documentation for report RFKKAR44.

Archiving of Transfer Records for Invoicing by Third Parties

You can use the new archiving object FI_MKKTHI to archive data fo invoicing by third parties (see alsodocumentation for report RFKKTHPAR01).

1.1.5 Authorization Objects

Use

Maintaining Interval Variants

With authorization object F_KKVARI, you can restrict the authorizations for maintaining intervalvariants:

o In the field OBJECT_KK, define the authorization for individual objects, such as GPART andVKONT.

o In the field ACTVT, you can control the authorizations for the following activities:

Activity Description

01 Create variants

02 Change variants

03 Display intervals

06 Delete variants

07 Generate variants

New Authorization Object F_FKKCJ for the Cash Journal

The authorization object F_FBCJ, which controls the authorizations for the cash journal, has beenreplaced by the authorization object F_FKKCJ.

In the field ACTVT, you can control the authorizations for the following activities:

Activity Description

01 Add or create

02 Change

03 Display

10 Post

33 Read

B5 Display history

If you cannot change over to the authorization object F_FKKCJ in the cash journal quickly, see SAP note667984. This note contains a description of how you can continue to use the old authorization objectF_FBCJ in the FI-CA Cash Desk. Note that you should deactivate this temporary solution as soon as

______________________________________________________________SAP AG 3

SAP-System______________________________________________________________

possible. After Release 4.72, SAP will only support the authorization object F_FKKCJ.

1.1.6 Balance Interest Calculation

Use

With Release 4.72 of SAP for Insurance, you can find the new V091 event (Balance Interest CalculationMass Activity: Check Ins. Object) in balance interest calculation. The system uses this to check whetherinterest is to be calculated on an insurance object/business partner relationship in the balance interestcalculation mass activity.

1.1.7 BAPIs in Contract Accounts Receivable and Payable

Use

Requests

You can now use new BAPIs for the business object CA_REQUEST to process requests. The followingmethods are supported:

CreateBAPI_REQUEST_CREATE Create request

GetdetailBAPI_REQUEST_GETDETAIL Read request

ChangeBAPI_REQUEST_CHANGE Change request

DeleteBAPI_REQUEST_DELETE Delete request

EasyCreateBAPI_REQUEST_EASYCREATE Create request with template

AddPeriodsBAPI_REQUEST_ADDPERIODS Add execution periods for request

DeletePeriodsBAPI_REQUEST_DELETEPERIODS Delete execution periods for a request

______________________________________________________________SAP AG 4

SAP-System______________________________________________________________

AddSpecialDatesBAPI_REQUEST_ADDSPECIALDATES Add special dates for request

DelSpecialDatesBAPI_REQUEST_DELSPECIALDATES Delete special dates for a request

AddLineItemsBAPI_REQUEST_ADDLINEITEMS Add request items

DelLineItemsBAPI_REQUEST_DELLINEITEMS Delete request items

Changes to the BAPIs for FI-CA Documents

The parameters ItemRelation and CardData have been added to the BAPI CtrAcDocument.Create,

The parameters DocumentHeader and DocumentHeaderX have been added to the BAPICtrAcDocument.Change

New BAPI for Contract Accounts

From Release 4.72, you can use the new BAPI CtrAcContractAccount.GetOpenItems.

Changes to the BAPI for Contract Accounts

The selection field in the parameter ValueSelektions has been extended.

See also

You can find more information about the new BAPIs in the release note for payment plans.

1.1.8 Broker Collections

Use

You can find the following new developments in Broker Collections for Release 4.72 of SAP forInsurance.

Integration

Broker collections and the functions for transferring coinsurance shares are now integrated: The brokercan transfer coinsurance shares independently, as well as transferring the shares for the respectiveinsurers. The broker does not transfer the total collected amount to the leading company, but just theshare for the leading company.

Master Data

The new Broker Transfers Coinsurance Shares flag has been introduced for the broker contract.

Customizing Settings

______________________________________________________________SAP AG 5

SAP-System______________________________________________________________

The Basic Settings IMG activity for broker collections now contains both new flags, Broker DunningStatus Active and Brokers Transfer Coinsurance Shares.

Broker Report

Selection Fields

As the classification key has been introduced as a new criterion for the document, the length of theselection fields in the broker report (IBROSTMP-SELV1, ..., IBROSTMP-SELV5) has been extendedto 35 characters. If you use the file interface for creating broker reports, as well as the BAPIs for brokerreports, you have to adjust the interfaces accordingly.

Broker Report Proposal

The Proposal for Broker Report function in Broker Report Processing now contains the new PostprocessProposal Online flag. If the flag is set you can manually postprocess the proposal determined by thesystem, meaning that items can be deactivated, clearing amounts can be changed and new items can beadditionally selected. The system then uses the changed proposal to construct the broker report items.

Checking Open Items

The new release of broker report processing now contains the new Check Open Items function. Thisallows you to check all broker report items to see whether the information about open items, stored forthe broker report item, still corresponds to the current status in the system. If this is not the case, theinformation about the open item is adjusted to match the current system status and the clarification codeis set accordingly. You can use event V525 (Archiving Generic Tax Report Shadow Table: Sort Fields) tomake further adjustments to the change determined by the system.

Late Payments

In broker report processing, you can now levy surcharges for late payments. To do this, you have todefine an appropriate function module, using event 104 (Clearing: Surcharges for Late Payment). Youcan set the surcharges manually in processing for open items for a broker report item. If you also use theProposal for Item function, the system automatically suggests proposals. The surcharges are added to thesuggested amount for a broker report. The Value Date field in the broker report item is used to calculatethe surcharges, and if it is not filled, the system does not calculate any surcharges.

ExampleIf an open item for 100 EUR is selected in an broker report item, and a surcharge of 2 EUR is leviedmanually, the system expects a reported amount of 102 EUR from the broker.If the broker actually pays 102 EUR and a clarification code with the Post according to proposalposting rule is used, the customer item is fully cleared; the system posts 102 EUR to the brokeraccount, as well as 2 EUR to a revenue account for payment surcharges defined in Customizing.

Authorization View

You can now adjust the authorization view for a user in broker collections, which is determined asstandard with the references to the user master record for business object BUSISI0002, using eventV575 (Broker Report: User Authorization).

New Events

V525: Check open items

V527: Decide whether the broker transfers the coinsurance shares for an item

V575: Adjust authorization view in broker collections

______________________________________________________________SAP AG 6

SAP-System______________________________________________________________

BAPIs

The BAPIs in broker collections have been adjusted as follows for the new release:

o Transfer of coinsurance shares is integrated:

- Broker Transfers Coinsurance Shares flag for Collect BAPI

- Broker Transfers Coinsurance Shares flag for the Creation and Change BAPIs

- Extension of Detail BAPIs

o Interest for late payments:

- AMOUNT_LATE_PYMT field in the BAPIBROKREPSELITEMC structure. In this field, youcan define a surcharge for late payment (for the open items for the item), when creating brokerreport items.

- AMOUNT_LATE_PYMT field in the BAPIBROKREPSELITEM structure. The field is usedfor the detailed view of open items for a broker report item.

o Check authorization view for user:

- NO_AUTH_CHECK flag. If this is set, no authorization checks are executed on theauthorization view for the user currently logged on. If it is not set, the authorization checks areexecuted.

File Interface

The file interface for creating broker reports has been extended with the Broker Transfers CoinsuranceShares field.

See also

You can find further information about the new flags in broker collections in the release note onInsurance-Specific Dunning for Release 4.72.

1.1.9 Business Information Warehouse

Use

Extracting Open Items

During the evaluation of receivables balances in the Business Information Warehouse (BW), you cannow simulate the clearing of credits with the oldest open receivables for a business partner.

The credits are only cleared if the transaction currency of the receivables and the credits to be cleared isthe same.

In event 2506, you can determine which of the following data has to agree for the credits to be cleared:

o Company code

o Business area

o General ledger account

If you do not define the event individually, clearing only takes place if the company code and the general

______________________________________________________________SAP AG 7

SAP-System______________________________________________________________

ledger account are the same for the receivable and the credit.

In the simulation, the due date of the credits is fixed to the due date of the receivables cleared. Thismeans that when the items are totaled and sorted, the status is the status that would be reached if thecredits were cleared with the oldest receivables due. If a credit memo is to be distributed over severalreceivables, the extractor simulates several fictitious items.

The restriction by business partner has been added to the extraction of open items. This means that youcan now restrict the extraction of open items to a subset of business partners before the open itemanalysis. You can use event 2504 to restrict the quantity of business partners selected. The functions ofevent 2505 have also been enhanced to enable you to exclude combinations of business partner, contractaccount, and contract (GPART/VKONT/VTREF) that are not required from the extraction quantity. Thesystem recognizes the runs to be restricted from the naming convention used in the event modules. Thefields LAUFD and LAUFI have been added to the interface of event 2505 for this purpose.

Extracting Installment Plan Data

You can use a new mass activity to extract installment plan data for the evaluation in the BusinessInformation Warehouse (BW). The data can be extracted either with or without consideration ofprevious extractions (delta queue).

As standard, only the most important data for the installment plan headers, installment plan items, andoriginal items is extracted. However, you can extend the extract structures. You can use events 2525 and2530 to read additional data and fill additional fields in the extract structures.

1.1.10 Cash Desk

Use

General Ledger Account Postings In the cash desk (Short Account Assignment)

The function for transferring incoming and outgoing payments in the Cash Desk has been enhanced andyou can now carry out the transfer postings with a tax on sales and purchases part. The field Tax Codehas been added to the area G/L Account Posting on the tab page Specifications for Payment on theinitial screen of the Cash Desk. The following fields have been added to the Customizing activity DefineShort Account Assignments for Transfer Postings in the Cash Desk:

o Tax on Sales and Purchases CodeHere you can define a tax code for each short account assignment key, that is, each G/L accountposting.

o Authorization GroupWith the authorization group you can assign specific authorizations to allow a clerk, for example, touse only certain short account assignment keys. Maintain the authorization via authorization objectF_KK_KUKON.

Barcode Scanner

With Release 4.72, the connection of barcode scanners has been implemented in the cash journal and theCash Desk.

In the Customizing activity Maintain Specifications for Cash Desk/Cash Journal, you can define whetherthe barcode entry field is to be displayed or hidden. If the barcode entry field is available, you display or

______________________________________________________________SAP AG 8

SAP-System______________________________________________________________

hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry ->Display/Hide. In the menu under Extras -> Hold Settings, you can save the settings user-specific.

The barcode scanned must be interpreted in event FKK_SAMPLE_6050 and the data required for theentry must be entered on the input screen for the cash desk/cash journal.


You make the system settings in the Implementation Guide for Contract Accounts Receivable andPayable under Business Transactions -> Payments -> Processing Incoming/Outgoing Payments-> Cash Desk/Cash Journal.

1.1.11 Cash Journal

Use

Reversing Withdrawals

In the cash journal menu under Edit, you can use the function Reverse Withdrawal to reversewithdrawal documents. This function does not just reverse the document; it also corrects the cash deskbalance.

Barcode Reader

From Release 4.72, you can connect a barcode reader in the cash journal and the cash desk. InCustomizing, you can define whether the barcode entry field is to be hidden or displayed. If the barcodeentry field is available, you display or hide the field dependent on the workplace via the Cash Desk menuExtras -> Barcode Entry -> Display/Hide, provided the workplace has a barcode reader. In the menuunder Extras -> Hold Settings, you can save the settings user-specific.

The barcode read is interpreted in event 6060. Enter the data required on the input screen for the cashdesk or the cash journal. For more information, see the sample function module FKK_SAMPLE_6060.


Posting Areas 0150 and 0160

The field Payment Type has been added to the posting areas 0150 - Cash Journal: Specifications forPosting Cash Desk Differences - and 0160 - Cash Journal: Bank Clearing, Deposit, andWithdrawal Accounts. You can define a separate cash desk clearing account per payment type:

CS Incoming and outgoing cash payment

CP Credit card payment

CH Incoming check payment

PO Postal order payment

CO Outgoing check payment

The introduction of the new payment type CO for outgoing check payments means that you can nowdefine separate cash desk clearing accounts for incoming and outgoing check payments. Make sure thatyou also enter the cash desk clearing accounts that you enter here in the activity Define Bank Clearing

______________________________________________________________SAP AG 9

SAP-System______________________________________________________________

Accounts for Payment Lots and that they are as follows:

Validity for the Corresponding Lot Types

PymtType PymtLot CheckLot CardLot Online Check

CS X

CP X

CH X

PO X

CO X

Maintain Specifications for Cash Desk/Cash Journal

From Release 4.72, you can make the specifications for the cash desk and the cash journal together in theactivity Maintain Specifications for Cash Desk/Cash Journal.

1.1.12 Closing Operations

Use

Summarization Accounts and Summarization Company Codes for Reclassifications

You can now display reclassifications for a group of accounts or company codes - previously, you couldonly display the reclassifications in the balance of one receivables or payables account of a businesspartner within a company code.

Summarization accounts are required for key date-related open items whose receivables and payablesaccounts are displayed in one item in the financial statements (for example, same type of legal transactionfor several utility provider divisions in the case of different receivables accounts per division).

Summarization company codes are required where company codes are in the legal entity that has to createthe financial statements (for example, consolidated financial statements).

See the release information for Foreign Currency Valuation and Evaluation of Open Items.


Summarization Accounts and Summarization Company Codes for Reclassifications

You make the specifications for reclassification by summarization company codes and accounts in theImplementation Guide for Contract Accounts Receivable and Payable under Closing Operations ->Reclassifications.

1.1.13 Coinsurance

Use

You can find the following new developments in Coinsurance for Release 4.72 of SAP for Insurance.

Direct Identification of the Coinsurer

______________________________________________________________SAP AG 10

SAP-System______________________________________________________________

You can define the coinsurance key directly for a G/L item. In this case, direct specification of acoinsurance key takes precedence, and the determination is not executed using the structure and thecharacteristic value. You must specify the category for the coinsurance-relevant document (premium orclaim), as well as the coinsurance key.

The coinsurance key can be entered in the payment plan item, and is passed on to the created G/L itemwhen executing the Execute Payment Plans function.

You can also enter the coinsurance key directly in the Post Document application, and display it in theDisplay Document application. The coinsurance key cannot be entered later, using the Change Documentapplication, for example.

Transferring Coinsurance Shares

In event V110 (Clearing: Amount Distribution), you can now change the document header of thecoinsurance document created by the system. The new ES_FKKKO parameter has been introduced forthis.

If you have defined your own event module for event V110 in the system, you have to extend theinterface for your module with the new parameter, and add the following line:

ES_FKKKO = IS_FKKKO.

Integration

The Transfer Coinsurance Shares function has been integrated into the functions for broker collections,so that brokers can now independently transfer coinsurance shares. In this case, the coinsurance sharesare not posted to the coinsurance contract by the coinsurance function (Transfer Coinsurance Sharesmass activity).

See also

You can find further information in the release note for broker collections.

1.1.14 Submission of Receivables to Collection Agency

Use

The following functions have been added to the submission of receivables to collection agencies:

o Derivation of collection agency responsible

o Deletion of submission logs

Derivation of Collection Agency Responsible

If you want to release receivables to different collection agencies using rules in your organization, fromRelease 4.72, you can define these derivation rules in Customizing for Contract Accounts Receivable andPayable.

The derivation rules defined in Customizing are evaluated by the derivation tool. The derivation tool isalways called in the function module FKK_COLL_AG_SAMPLE_5060 if items are released forcollection individually in transaction FP03E or in the mass release via transaction FP03M. The derivationtool determines the relevant collection agency in one or more derivation steps from a sequence of sourcefields of the enhanceable structure FKKCOLLAG. The number of derivation steps corresponds to the

______________________________________________________________SAP AG 11

SAP-System______________________________________________________________

number of derivation rules that you define in Customizing.

Deletion of Submission Logs

You can now delete logs recorded in table DFKKOPCOLL by the mass run for submitting receivables tocollection agencies (FP03M). You can do this with transaction Delete Submission Logs (FP03DML)(see SAP menu: Periodic Processing -> Delete Data).


You define the derivation rules for the responsible collection agency in the Implementation Guide forContract Accounts Receivable and Payable under Business Transactions -> Submission ofReceivables to Collection Agencies -> Define Derivation Rules for Responsible Collection Agency.

1.1.15 Company Codes

Use

Replacement of the Responsible Company Code in Contract Accounts Receivable and Payable

Previously, the responsible company code had the following control characteristics in FI-CA:

o It determined the company codes in which you could post to a contract account

o It was the company code in which payment transactions were processed

o It was (regardless of Customizing) the company code in which payments on account were posted

The coupling of these functions heavily restricts the options in some areas and leads, for example, to youhaving to introduce auxiliary company codes to portray the organizational model.

From Release 4.72, the responsible company code is replaced by the following three new entities:

o Company code groupThe company code group includes all company codes that are permitted for posting to a companyaccount. One company code group is assigned to each contract account. Company code groups canoverlap. This means, for example, you can have a group G1 that consists of company codes 0001,0002, and 0003, and group G2 that consists of 0001 and 0003.

o Paying company codeExactly one paying company code is always assigned to each company code group. A payingcompany code is responsible for payment transactions. You have to define house banks andpayment methods for paying company codes. Several company code groups can have the samepaying company code. The paying company code does not have to be in the company code groupitself.

o Standard company codeOne standard company code is assigned to every contract account. You use the standard companycode for all postings for which no company code can be determined by other means (for example,for payments on account).

Transition from Responsible Company Code to the New Entities

The conversion of the responsible company codes to company code groups and paying company codestakes place automatically during the first check (contract account or document) where you check the

______________________________________________________________SAP AG 12

SAP-System______________________________________________________________

validity of a company code group or where the company code group is a prerequisite.

For each responsible company code, the system creates a company code group with the same key. Thecompany codes that were previously assigned to the responsible company code are assigned to thiscompany code group. The responsible company code is assigned as the paying company code for thegroup. This ensures continuity for the existing organizational model.

The name of the responsible company code is taken as the name for the company code group. Since thenew name is language-dependent, it is automatically created in all languages used in the installation. Thelanguages are determined empirically by analyzing the document type texts.

Changes to the Contract Accounts

For new contract accounts, the company code group and standard company code are mandatoryrequirements. For existing contract accounts, you can use conversion report RFKKSTDBK to add thestandard company code. The standard company code receives the value of the former responsiblecompany code. You can convert the contract accounts in stages you do not have to convert them all atonce. The system handles accounts that you have not yet converted as if you had converted them.

Changes to Checks in Contract Accounts

The validity of certain fields was previously coupled to the combination with the country of theresponsible company code. The following changes have occurred in these checks:

o The country from the paying company code of the company code group is used for:

- Payment methods

- Own bank details

o The country of the standard company code is used for:

- Withholding tax codes

- Region

- County code

- Tax exemptions

Restrictions for Company Code Groups

Using the new event 1010, you can check whether a company code group is permitted in a contractaccount. This enables you to prevent, for example, that cross-country groups (in certain contractaccounts) are used.

Authorization Check

In the authorization object F_KKVK_BUK, the responsible company code was used for the check in themaster data maintenance. The standard company code is now used instead.

Payment Program

You can also specify the paying company code in a business partner item. In this case, this specificationoverrides the paying company code determined via the company code group of the contract account. If apaying company code specified in the line item is in a different country to the paying company codedetermined via the contract account, you also have to specify a payment method in the line item. In thiscase you cannot use the payment methods from the contract accounts since they refer to a differentcountry.

______________________________________________________________SAP AG 13

SAP-System______________________________________________________________

In the parameters for the payment run/debit memo run, you restrict the company codes to be processed.All relevant company code groups and their paying company codes are determined for the companycodes internally. If these are in different countries, the country of the payment run must be assigned via adifferent parameter. In a payment run, you can still only create payments for one country.


You define the company code groups in the Implementation Guide for Contract Accounts Receivable andPayable under Organizational Units -> Define Company Code Groups.

You assign the company codes to the groups under Organizational Units -> Assign Company Codesto Company Code Groups.

1.1.16 Creation of Correspondence

Use

Balance Notification

You can use event 9552 to create balance notifications. In this event you decide whether a balancenotification is to be created.

Requests and Standing Requests

To print requests and standing requests, you can use events 0766: Print Request and 0767: Create RequestPrintout, and correspondence type 0039 Request (see also the release information for Requests).

Note for SAP Insurance

In Collections/Disbursements, events 9552 and V768 are used alongside one another, to createcorrespondence types:

o You use event 9552 to create correspondence type 0026.

o You use event V768 to create the insurance-specific correspondence type V033.


You define customer-specific function modules in the Implementation Guide for Contract AccountsReceivable and Payable under Program Enhancements -> Define Customer-Specific FunctionModules.

1.1.17 Creation of Tax Items

Use

Release SAP for Insurance 4.72 moves the creation of additional tax lines from the debit entry to theposting interface. Exit V063 (Debit Entry Payment Plans: Create Tax Lines), which previously createdtax lines, has been shut down.

______________________________________________________________SAP AG 14

SAP-System______________________________________________________________

1.1.18 Document Display for a Business Case (New)

Use

From SAP for Insurance 4.72, you can use the V_SHOW_ALL_DOCS_FOR_GSFNR report in theDisplay Documents for a Business Case application (transaction GSFNR) to display all documents for abusiness transaction with their business partner items and G/L items, even if the documents have beenposted in differing currencies. This is a logical extension of the Display Document application, in whichit is not possible to display documents for various currencies together, as the totals function implementedthere is not capable of handling this.

1.1.19 Insurance-Specific Dunning

Use

1. Dunning Charge Calculation

From Release 4.72 of SAP for Insurance, you have the option of using the Do Not Take Transaction intoAccount for Dunning Charge Calculation flag, to exclude certain line items from the calculation ofdunning charges.

If the flag is set, the system does not take this item into account, with corresponding main andsubtransactions, when calculating dunning charges.

2. Collective Dunning: Including More Items

Previously, items were only included in a running dunning procedure for collective dunning if the days inarrears for the first dunning level had been reached. From Release 4.72 of SAP for Insurance, you canenter a value for alternative days in arrears for the first dunning level. If more items are included for anexisting dunning procedure, the system does not check them against the days in arrears for the firstdunning level, but against the alternative days in arrears for the first dunning level. If no value is enteredfor alternative days in arrears, the days in arrears for the first dunning level are checked, as waspreviously the case.

3. Dynamic Dunning Grouping

Previously, you used the different dunning procedure types (individual dunning, collective dunning andcontract dunning) with the appropriate dunning grouping categories. From Release 4.72 of SAP forInsurance, these dunning procedure types are extended with multi-collective dunning.

Grouping category One item? One dunning procedure?

Individual dunning 01 Yes No

Collective dunning 02 No Yes

Contract dunning03 Yes Yes

Multi coll. dunning XX No No

The following grouping categories are delivered as standard for SAP for Insurance:

01 Grouping for individual dunning

02 Grouping for collective dunning

______________________________________________________________SAP AG 15

SAP-System______________________________________________________________

03 Grouping for collective dunning

Multi collective dunning gives you the advantage of allowing the existence of multiple collective dunningnotices for a business partner/insurance object relationship. To control this, define your own dunninggrouping category, which can have up to three additional (different) dunning grouping fields (in additionto standard dunning grouping 02).

You can choose from the following dunning grouping fields: MAHNV, STDBK, GSBER, SPART, SUBAP,VKNT1, XINFO, FRDAT, STDBK, GDUNN, COLLECT, BROKER, BRO_CONTRACT, PRGRP, FAEDN,VSARL_VX.

You can define additional fields in the CI_FKKMAKO customer include.

4. Dunning for Corporate Customers

From Release 4.72 of SAP for Insurance, you can use the Broker Dunning Status Active central flag inthe Customizing settings to control whether the broker dunning status is to be used. In connection withthis, you can now use the Broker Executes Coll./Disb. flag in the insurance object master data, to definecertain dunning activities as not to be executed, if the Broker Dunning Status Active flag is set(meaning, if the customer is in broker collections).

This is realized with the new dunning activity categories M1 and M2:

o M1 = Broker collections: Key for the dunning activity category tjhat must be executed for opendunning procedures.

o M2 = Broker collections: Key for the dunning activity category that must be executed for ending adunning procedure.

The existing activity categories retain their validity.

The following rules are in effect for the conversion of the new functionality:

1. Customer is in broker collections:All activities with activity category 01 (dunning activity) are executed.All activities with dunning activity category M1 (Broker collections: Activity when opening thedunning procedure) are not executed.

2. Customer is not in broker collections:All activities with activity category 01 (dunning activity) are executed.All activities with dunning activity category M1 (Broker collections: Activity when openingdunning procedure) are executed.

The same is true when ending with activity categories 02 and M2.

You can also use the Set Dunning Level flag to determine whether no broker dunning status is created forcertain dunning levels, by setting the flag to value 3 (do not take dunning level into account for brokerdunning status).

You can now restrict the Create Broker Dunning Status application to certain dunning activity runs, usingthe new Date ID and Identification selection fields.

From Release 4.72 of SAP for Insurance, you can also use the Broker Dunning Status History application(transaction IBR75), which you can restrict by using the Date ID and Identification fields.

5. Insurance Dunning History

In the Insurance Dunning History application (transaction VYM10), you can still display the dunning

______________________________________________________________SAP AG 16

SAP-System______________________________________________________________

history for an insurance object/partner relationship, or a contract account/partner relationship. FromRelease 4.72 of SAP for Insurance, there are two new buttons in the application menu bar, which allowyou to reach the following functions directly.

Display Document button

From the insurance dunning history overview, you can display the documents related to the dunnedgroups, such as interest or charges documents. The possible document numbers are listed in a pop-upmenu, from which you can then select the appropriate document for display.

You can display the original document for the item due for dunning from the dunning line display.

To display the documents, place the cursor on the document number and choose the Display Documentbutton, double-click on the document number, or choose the menu path Goto -> Document.

The system displays the selected document. The following functions are available in document display:

Display Dunning Lines button

Place the cursor on the required dunning grouping (dunning header). Follow the path Goto -> DunningLines, or choose the Display Line button.

Double-clicking on a dunning grouping takes you to the item-related dunning history, as was previouslythe case.


In order to use extended dunning charge calculation, set the Do Not Take Transaction into Account forDunning Charge Calculation flag under Parameterize External Transaction in the IMG(Collections/Disbursements -> Basic Functions -> Postings and Documents -> Document -> MaintainDocument Assignments -> Maintain Transactions for SAP for Insurance (FS-CD) -> Define andParameterize External Transactions).

To be able to include more items with values for alternative days in arrears in collective dunning, edityour settings in the IMG under ... -> Business Transactions -> Dunning Notices -> Configure DunningProcedures.

In the same IMG activity, you define the Setting the Dunning Level flag.

In order to be able to use dynamic dunning grouping, edit your settings under ... -> Business Transactions-> Dunning Notices -> Define Dunning Grouping Categories.

You set the Broker Dunning Status Active flag in the IMG, under ... -> Broker Collections -> BasicFunctions -> Activation of Basic Functions.

1.1.20 Dunning

Use

In the dunning history, you can display a text for the business partner. As standard, the text appears withthe name and address of the business partner; with a customer-specific function module defined in event4700, you can adjust this text to meet your requirements.


______________________________________________________________SAP AG 17

SAP-System______________________________________________________________

Register your function module in the Implementation Guide for Contract Accounts Receivable andPayable under Program Enhancements -> Define Customer-Specific Function Modules for event4700.

1.1.21 Changes to Collections/Disbursements Area Menu

Use

From SAP for Insurance Release 4.72, the following changes have been made in theCollections/Disbursements area menu:

New Applications

o Under ... Account -> Further Information: The Clarification Case for Account Balance application(transaction FPDM00)

o Under ... Document: The Display Documents for a Business Case application (GSFNR transaction)

o Under ... Master Data -> Business Partner: The Maintain Bank Details application (FPP4transaction)

o Under ... Periodic Processing -> For Contract Accounts: The Reversing Check Payments (FPCHStransaction), Distribute Credit to Multiple Recipients (VAZE transaction), Set Business Locks(FKLOCK2 transaction) and Delete Business Locks (FPLKDEL transaction) applications.

o Under ... Periodic Processing -> Open Item Evaluation: The Execute Evaluation (ParallelProcessing) application (FPO4P transaction).

o Under ... Periodic Processing -> For Contract Accounts -> Dunning: The Transfer Telephone Listapplication (FPVT transaction)

o Under ... Periodic Processing -> Mass Processing Administration: The Schedule Mass Activityapplication (FPSCHEDULER transaction)

o Under ... Periodic Processing -> Mass Processing Administration -> Extended MessageManagement: The Clarification List with Shortcut (EMMACLS transaction), Clarification withAutomatic Processes (EMMACAP transaction) and creation of Clarification Cases in Mass Runtransactions (FPEMMACGEN transaction)

o Under ... Periodic Processing -> Closing Preparationsy: The Foreign Currency Evaluation Log(FPW2 transaction) application

o Under ... Periodic Processing -> Extraction for Business Information Warehouse: The ExtractInstallment Plans application (FPIPBW transaction)

o Under ... Periodic Processing -> Archive Data: The Foreign Currency Evaluation, (FPAR09transaction), Clearing History (FPAR10 transaction), Doubtful Entries (FPAR11 transaction) andThird-Party Invoicing (FPAR12 transaction) applications

o Under ... Periodic Processing -> Delete Data: The Submission to Collection Logs (transactionFP03DML) and Dunning Telephone List Entries (FPVT1 transaction) applications

o Under ... Periodic Processing -> Forward Postings -> Execution: The Forwarding CashManagement (transaction FPCF) application

______________________________________________________________SAP AG 18

SAP-System______________________________________________________________

o Under ... Periodic Processing -> Delete Data: The Totals Records (After Document Archiving)application (FPARS1 transaction), as well as the new Forward Data to SAP Credit Managementsubfolder, with the new Transfer Credit Cards (FPCM1 transaction) and Replicate Creditworthiness(FPCM2 transaction) applications.

o Under ... Payments -> Cash Journal: The Cash Journal Master Data (transaction FPCJM), CashDesk Closing Overview (transaction FPSC) and Cash Journal Evaluation (FPCJR transaction)applications

o Under ... Payments -> Cash Journal -> Responsibilities: The Branch Leader (transactionFQ_FPCJ_SU), Cashier with Special Authority (transaction FQ_FPCJ_SC) and Cashier (transactionFQ_FPCJ_NC) applications

o Under ... Administration: The Activate Search Index for Archived Payment Lots (transactionFP05ARC) application

Discontinued Applications

o The Transfer Post Items to Other Responsible Company Code application (transaction FPU2)

o The Mass Reversal of Dunning Notices application (transaction FPVC)

Changes

o The Create Clarification Worklist application (EMMACL transaction) is now called DisplayClarification List.

o The Cash Desk application (transaction FPB0) is no directly under ... Payments.

o The ... -> Payments -> Cash Desk folder is now called ... -> Cash Journal.

o The Print Installment Plan Payment Forms application (FPRD transaction) has been renamedInstallment Plan Printing, as you can now use this application to process all installment plancorrespondence.

o The Totals Records application (FTP6 transaction), which you found under ... Periodic Processing-> Delete Data up to Release 4.71, has been renamed Totals Records Restructuring and is nowunder ... Periodic Processing -> Forward Postings -> Preparation.

o Reasons of process logic determined that subfolders were swapped around under ... PeriodicProcessing: The Closing Operations subfolder is now before the Correction Postings subfolder.

1.1.22 Extended Message Management

Use

The Enhanced Message Management Analysis (EMMA) has been enhanced so that you can now analyzethe application logs of any jobs in the R/3 system. The transaction code is no longer required to identifythe job logs. Instead, business process areas and business process codes have been introduced.The Customizing has been changed so that you now have to activate EMMA for complete businessprocess areas instead of for individual transaction codes; you can also define the suppression of messagesduring log preparation per business process area.

Business process areas consist of similar business processes, such as billing and invoicing. Business

______________________________________________________________SAP AG 19

SAP-System______________________________________________________________

process codes rewrite a specific activity of a business process area regardless of whether this activitywas carried out by a transaction, a report to be started online or in the background, or by a mass activity(for example, reversal of a document in transaction FP08, or mass reversal of documents with transactionFP08M).

Installation-specific transactions are evaluated via the interface IF_EMMA_LOGMSG_PROCESS.

The Customizing for the case category has been revised with regard to user-friendly aspects. For existingcase categories, you have to maintain the assigned business process code, since this has taken over therole of the clarification case type as decisive selection criterion for case generation.

You can now use clarification types for several business area codes; they are no longer coupled to an SAPentity and are used as optional specification for the categorization of case categories.

The role resolution has been integrated in Customizing for clarification case processing.

You can now insert business object attributes into the Customizing for clarification case categorieswithout programming. To do this, connect the objects of the message pool with the new case containervia a data flow definition.

In the Customizing for the clarification case categories, the administrative data of the author and the lastperson to make changes is recorded.

With transaction FPEMMACGEN (see SAP menu: Periodic Processing -> Mass ProcessingAdministration -> Enhanced Message Management Analysis -> Create Clarification Cases), youcan now create clarification cases in a mass run. You can also create clarification cases for individualintervals of a mass activity or for several.


Make the system settings required for Enhanced Message Management Analysis in the ImplementationGuide for Contract Accounts Receivable and Payable under Basic Functions.

1.1.23 New and Changed Events

Use

New Events

0063: Include Document in Collective Bill

0086: Industry Grouping Key for Rounding

0104: Clearing: Arrears Surcharges

0113: Clearing: Transaction for Payment on Account

0175: Account Assignment Derivation for Tax Items in PS-CD

0211: Payment Lots: Propose Key for New Lot

0222: Payment Lot: Include Screen for Customer Fields

0232: Payment Lot: Additional Data for Item

0254: Payment Reversal of Locked Checks

______________________________________________________________SAP AG 20

SAP-System______________________________________________________________

0367: Dunning: Leading Contract Account and Company Code

0501: Document Archiving: Check Header

0505: Document Archiving: Check Complete Document

0580: G/L Account Check for Accounting Rules

0652: Payments: Partner Bank Selection

0671: Payments: Round Payment Amount

0766: Correspondence: Print Request

0767: Correspondence: Create Request

0798: Printing: Output Mode of Attached Payment Media

1010: Contract Account: Check Company Code Group

1054: Business Partner: Determine CCARD_ID for Automatic Creation

1091: Change Payment Card Data: Print Correspondence

1092: Change Payment Card Data: Create Correspondence

1247: Account Balance: Determination of Document Category

1248: Account Balance: Supplement Context Menu

1250: Dispute: Default Values for Creation of Dispute Case

1251: Dispute: Distribute Follow-On Postings to Disputes

1252: Dispute: Define Communication Channel

1253: Dispute: Include Screen for Customer Fields

1254: Dispute: Additional Activities for Manual Changes

1311: Checks for Posting Area 1010

1742: Mass Activity: Set Locks

1743: Mass Activity: Set Locks, Move Parameters

1766: Mass Activity: Evaluation of Open items OP04

1767: Mass Activity: Integration FI/COPA

1840: Mass Activity: Credit Liability Update

1841: Mass Activity: Credit Liability Update, Move Parameters

1842: Mass Activity: SAP Credit Management Score Replication

1843: Mass Activity: SAP Credit Management Parameters, Score Replication

1970: 1099 Reporting: Determine Reporting Flag

1971: 1099 Reporting: Items Relevant for 1099 Reporting

2065: Interest: Set Value Date

2404: Posting via IDoc: Processing of Customer Header Segment

______________________________________________________________SAP AG 21

SAP-System______________________________________________________________

2504: BW: Open Items, Restrict Selection

2506: Open Item BW Extraction: Parameters for Credit Clearing

2805: ICWC Account Balance: Create Info Items

2806: ICWC Account Balance: Create Item Groupings

2807: ICWC Account Balance: Prepare Items

2821: ICWC Documents: Correspondence Category Independent Data

2822: ICWC Documents: Correspondence Category Dependent Data

3031: Installment Plan: Determine Print Type for Payment Forms

3910: Migration: Document Transfer - Convert Document Data

3920: Migration: Document Transfer - Check Document Data

4030: SD/FICA Integration: Enhanced Transaction Determination

4256: Credits: Create Additional Correspondence

4257: Credits: After Creation of Correspondence

4258: Credits: Check Payment Method (Transfer/Check)

4500: SAP Credit Management: Supplement FI Summary

4501: SAP Credit Management: Filter Open Items

4502: SAP Credit Management: Determine Liability Category

4600: XI: Add FI Summary for SAP Credit Management

4601: XI: Asynchronous Outbound Interface for FI Summary

5125: Transfer of Open Items: Payment on Account

6060: Cash Desk: Barcode Interpretation

6302: Boleto: Determination of Default Instruction Key

6303: Boleto: Assignment of Instruction Key

6306: Boleto: Selection of Statistical Documents

6351: Boleto: Adjust Data Parameters for Account Statements

FKK_EMMA_MASS_CREATE_CASES: Creation of Clarification Cases in Enhanced MessageManagement Analysis (EMMA)

6507: Requests: Supplement Customer Fields for Approval

9050: Print Collection Letter

9051: Create Collection Letter

9052: Analyze Items from Collection Case

9053: Attributes for Collection Case

9510: BAPI: Create Request (ExtensionIn)

______________________________________________________________SAP AG 22

SAP-System______________________________________________________________

9511: BAPI: Create Request (ExtensionOut)

9512: BAPI: Change Request (ExtensionIn)

9513: BAPI: Change Request (ExtensionOut)

9514: BAPI: Create Execution Period for Request (ExtensionIn)

9516: BAPI: Read Request (ExtensionOut)

9552: Balance Confirmation: Check Balance

9557: Document Extracts: Additional Data Records for Import

9558: Document Extracts: Additional Data Records for Deletion

9570: Set Mass Locks


You define installation-specific function modules in the Implementation Guide for Contract AccountsReceivable and Payable under Program Enhancements -> Define Customer-Specific FunctionModules.

1.1.24 Conversion of Finnish Bank Statement to MultiCash (Enhanced)

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the Bank Statement: FinlandReference Payments - Convert to MultiCash report (RFEBFI00) has been enhanced to convert thefollowing types of bank statement files in FI-CA:

o Reference payments

o Direct debits

o Direct invoices

You can also specify further processing of the converted file with the FI-CA MultiCash report,RFKKKA00.

1.1.25 Foreign Currency Valuation (Extended)

Use

In the foreign currency valuation (transaction FPW1) (see SAP menu: Periodic Processing ->Closing Preparations), you can now save the valuation difference for each open item. This enables youto further process the revaluation of an open item in closing preparations, for example, in the keydate-related open item list and during reclassification of customers with credit balances.

By saving the valuation difference, you can make a more flexible assignment of valuation methods tocompany codes. This means that the foreign currency valuation is compatible with different GAAPs. Thismeans that you can valuate open items differently according to the reporting view (valuation area).

______________________________________________________________SAP AG 23

SAP-System______________________________________________________________

Each foreign currency valuation that requires correction postings is logged. You can use the newtransaction Log for Foreign Currency Valuation (FPW2), you can get an overview of all foreigncurrency valuations. You can also reverse individual valuation runs in the display if you have theauthorization to run them again later with more current data.


In the Implementation Guide for Contract Accounts Receivable and Payable under Closing -> ForeignCurrency Valuation, define:

o Valuation methods

o Valuation areas for each reporting view (for example, HGB, IAS, US GAAP)

o Valuation variantsFor each company code and for each local currency, you can configure the valuation method to beused for a foreign currency valuation, and for which valuation area the valuation is to be carried out.

o The general ledger accounts that the unrealized gains and losses are to be posted toYou can define different accounts dependent on the valuation area.

1.1.26 Transfer Post Items to Other Responsible Company Code

Use

If the Reinsurance component (FS-RI) has been implemented alongside Collections/Disbursements, itemtransfer posting to another company code previously took place using the FPU2 transaction (TransferPost Items to Other Responsible Company Code). From Release 4.72 of SAP for Insurance, FPU2 is nolonger available, due to new developments in company code organization and in the document concept.

Company code organization now covers the functions of the application: Various company codes can beassigned to a company code group (company code groups can overlap with one another). Every companycode group always has just one paying company code, which is used to process the posting data. Younow specify the alternative paying company code when posting. This means that it is no longer necessaryto specify a separate date for currency conversion.

Transfer posting of payment data to another contract account now takes places using the Transfer Itemsapplication.

Effects on Existing Data

As before, one company code must be specified for each item in the document. This company code mustbe assigned to the company code group defined for the contract account, which the system uses todetermine the paying company code.

If the desired paying company code lies outside the company code group defined for the contract account,you can then specify an alternative paying company code in the document, and an alternative associatedpayment method, to process the payment with a separate company code, and therefore a separate housebank. This alternative company code can be chosen, independent of the company code group defined forthe account.

______________________________________________________________SAP AG 24

SAP-System______________________________________________________________

1.1.27 Funds Management

Use

As of Release 4.72 you can use Contract Accounts Receivable and Payable integrated with componentFunds Management (PSM-FM). Funds Management was only released for industry-specificcomponent Public Sector Contract Account Receivable and Payable until now. As of Release 4.72,Funds Management is released for Utilities Industry, all other industry-specific components can useFunds Management with a pilot project.

Prerequisites for the Integration

In order to be able to maintain data for Contract Accounts Receivable and Payable in Funds Management,you must:

o Activate Funds Management in Customizing (see Activate/Deactivate Funds Management)

o Define function module FKK_EVENT_FM_1102 (FM Integration: Account AssignmentDerivation) with event 1102SAP provides this function module as a standard function module. If Funds Management is notactive, the function module will not run.

If you want to use the component Fund Accounting, you must define function moduleFKK_FM_SAMPLE_0032 (Fund Accounting: Supplementing Document Items) with event 0032 .SAP provides this function module as standard function module. If Fund Accounting is not active, thefunction module is not run.

Restrictions

Note that Funds Management does not support the update of all postings for Contract AccountsReceivable and Payable. See SAP note 686383 for a list of restrictions.

Activating FM Account Assignments in Contract Accounts Receivable and Payable

All relevant tables and structures of Contract Accounts Receivable and Payable must be enhanced withthe organizational unit of Funds Management, the FM area FM Area and the following FundsManagement account assignment elements:

o Commitment item

o Funds center

o Fund

o Functional area

o Funded program

Note that you cannot use the account assignment element Grant of component Public SectorManagement at the moment.

The exception to this is the document tables of the business partner and G/L items and their counterpartsfor sample documents. In the interest of performance in systems in which Contract Accounts Receivableand Payable is not used in connection with Funds Management, the FM account assignment fields are notincluded in tables DFKKOP and DFKKOPK. If you want to connect Contract Accounts Receivable andPayable to Funds Management, you must activate Funds Management in the IMG of Contract AccountsReceivable and Payable. On activation, the FM account assignment fields are included in the tables

______________________________________________________________SAP AG 25

SAP-System______________________________________________________________

mentioned automatically. SAP provides corresponding Customer includes for the integration of FMaccount assignment fields. For more information, see the documentation on activity Activate FM TableFields for Contract Accounts Receivable and Payable in Customizing.

Fields for FM expenditure and revenue account assignment were also included in the business partneritems in order to improve performance. As such, the document for the FM account assignment mustdisplay zero balance for an invoice. The FM information is available immediately for clearing.

FM Account Assignment Logic for Automatically Generated Docs

To derive FM account assignments in automatically generated documents (for example, charge postings),you must define derivation rules in Customizing. The system can derive the FM account assignmentsassigned automatically from the contract account, main and subtransaction. You can also use thederivation rules to determine default values for entering documents manually and entering requests.

Enhancing Cash Security Deposits

You can also enter an FM account assignment when creating Cash Security Deposits. CommitmentItem, Fund, Funds Center and Functional Area are ready for input on the processing screen. If you donot enter any FM account assignment, the system derives these automatically from the rules defined. Thederivation also takes place automatically with the migration of Cash Security Deposits.

Enhancements for Doubtful Areas and Individual Placings

The posting data is supplied automatically with the FM account assignment for the two businesstransactions. All other FM account assignment data, apart from the commitment item is passed onthrough the original document. The system determines the commitment item based on event 1750MakeDefined Installation-Specific Function Module with Tax Adjustment. This ensures that the FM accountassignment is adjusted accordingly.

Enhancement with Posting of Delayed Revenue

The system copies the FM account assignment automatically from the original document into the delayedrevenue posting. In order to use this function, you must include structure IFKKFMOBJ in tableFKKDEFREV.

Updates in Funds Management

The update of FM document data takes place at the same time as the transfer of total records to ContractAccounts Receivable and Payable into the general ledger (DFI-GL) with program RFKKGL00 (see SAPmenu: Periodic Processing -> Forward Postings -> Execute -> Transfer to General Ledger).

The update of payments and other clearing transactions take place automatically in Contract AccountsReceivable and Payable. The system updates all clearings and clearing reversals as well as invoices andpayments on account online in the totals tables of Contract Accounts Receivable and Payable.


You define the settings for Funds Management in the IMG of Contract Accounts Receivable and Payableunder Integration -> Funds Management (PSM-FM).

Define FM account Assignment Derivation

You define the FM account assignment derivations in the activity Define FM Account AssignmentDerivation. Contract Accounts Receivable and Payable uses the derivation strategy from FundsManagement by default (see the IMG of Funds Management) Government Master Data -> Allocationsto Account Assignments from Other Components -> Define Account Assignment Derivation).

______________________________________________________________SAP AG 26

SAP-System______________________________________________________________

If you want to use your own derivation strategy in Contract Accounts Receivable and Payable, you mustset the indicator Use Derivation Strategy of Contract Accounts Receivable and Payable inmaintenance view TFK_FMDERIVSTRAT . To do this, call the view on this using transaction SM30.However, note that the derivation strategy of Contract Accounts Receivable and Payable is no longersupported.

Fund Accounting

If you want to use Fund Accounting, you must activate the Fund in the IMG of Public SectorManagement under Basic Settings -> Activate Account Assignment Elements. You can also readthe activation status in the IMG of Contract Accounts Receivable and Payable in activity ActivationStatus of Fund Accounting.

When the fund is active the system generates additional clearing lines that ensure that the balance iscleared for each document and company code. Define G/L account for the fund clearing in activityDefine Accounts for Fund Clearing .

1.1.28 IDoc Interfaces for Communication with External Billing Systems

Use

Evaluation of Mass Runs by Enhanced Message Management Analysis

The evaluation of Enhanced Message Management Analysis has been activated for the followingprograms:

o Document Data Transfer (transactions FKK_EBS_TOI_COPA and FKK_EBS_TOI_COPA_E)

o Linking with Archive Data (transactions FKK_EBS_ARC and FKK_EBS_ARC_E)

o Reversal of Documents (transactions FKK_EBS_MRD and FKK_EBS_MRD_E)

Functional Enhancements in the IDOC FKK_EBS_TOI_COPA (Document Data Transfer fromExternal Billing Systems)

To define and process customer- or project-specific document header data, you can now define areplacement segment for the segment E1FKK_EBS_TOI_HEADER in Customizing.

You can use event 2404 to process header

segment data. You can also change the standard processing by defining the standard segmentE1FKK_EBS_TOI_HEADER in Customizing. For example, you can change the field BLART orAWTYP.

In event 2404, you can also create the object relations between documents via the interfaceT_FKKOPREL.

By defining a customer- or project-specific segment you can transfer the additional data containedtherein, for example, the classification key, to the document header.

The optional field DOC_TYPE (document type) has been added to the segmentE1FKK_EBS_TOI_HEADER. With this segment you can override the document type defined in theinterface Customizing at document level.

Maintaining Object Relations at Item Level

______________________________________________________________SAP AG 27

SAP-System______________________________________________________________

The maintenance of object relations (interface T_FKKOPREL) has been added to event 2413. Thismeans that you can now fill the object relations at document item level from a customer- orproject-specific ITEM additional segment.


In the Implementation Guide for Contract Accounts Receivable and Payable under Data Transfer ->Communication with External Billing Systems -> Transfer of Accounting Documents, thefollowing activities have been enhanced:

o Basic Settings for Document TransferYou can now define a customer- or project-specific header data segment.

o Define Translation of External Tax IDYou can now define (optional) a tax on sales and purchases code as well as the condition key foreach external tax code. If you define a tax on sales and purchases code, this is available in events2405 and 2406 for comparison.

1.1.29 Changes in IMG for Contract Accounts Receivable and Payable

Use

The following IMG activities have been changed for SAP for Insurance Release 4.72:

There have been changes to the following system settings with Release 4.72:

Organizational Units

As part of the changeover of the company code concept in Contract Accounts Receivable and Payable,you now have to make the settings for the company code in the following activities:

- Set Up Company Codes for Contract Accounts Receivable and Payable

- Define Company Code Groups

- Assign Company Codes to Company Code Groups

Basic Functions

o Contract AccountsThe activity Activate Additional Checks for Changes to the Business Partner Master Recordhas been moved from the section Technical Settings to the section Contract Accounts.

o Postings and DocumentsIn the section Define Account Assignments for Automatic Postings, the activity Define COAccount Assignments has been renamed to Define CO Account Assignment Keys.

Here you can also define the required specifications for the Nota Fiscal in Brazil. To do this,Contract Accounts Receivable and Payable uses the Customizing of the standard FI.

Business Transactions

o Payments

______________________________________________________________SAP AG 28

SAP-System______________________________________________________________

The activity Specifications for the Clarification of Incoming Checks under Basic Functions ->Check Management has been renamed to Define Specifications for the Clarification ofCashed Checks.The activities in the sections Cash Desk and Cash Journal under Business Transactions ->Payments -> Processing of Incoming/Outgoing Payments have been grouped under the sectionCash Desk/Cash Journal.The activity Maintain Responsibilities for Cash Journal Users has been moved from the IMG tothe menu (see SAP menu Payments -> Cash Journal -> Responsibilities).

In the section Creation of Incoming/Outgoing Payments, the activity Define Specifications forResponsible Company Code has been replaced by the activity Define Specifications forPaying Company Code.In the same section, the activity Specifications for Transferring Open Items to the ResponsibleCompany Code is no longer available.

o Submitting Receivables to Collection AgenciesThe activity Define Strategy for Derivation of Collection Agency Responsible has beenrenamed to Define Derivation Rules for Collection Agency Responsible and has beenenhanced.

Technical Settings

The activity Activate Dependency Check for Business Partner Master Data Changes is no longeravailable.

Note for SAP Insurance

With SAP for Insurance 4.72, you can use the following insurance-specific new developments:

o Under ... Basic Functions -> Particular Aspects of Taxation Procedure -> Insurance Tax (Italy),you can now find the new Define Tariff Groups IMG activity. The existing activities that wererequired for Italian tax law, Define Other Tax Codes and Assign Main and Subtransactions to TaxCodes are also included in the IMG branch for Insurance Tax (Italy).

o Under ... -> Program Extensions -> Prepared Extensions, you can now find the ActivateClassification Key for Direct Input (Payment Plan Items) IMG activity.

o Under ... Payment Plans -> Settings for Debit Entry, you can now find the new Edit Settings forCash Management (Payment Plans) IMG activity.

The Define Lock Reasons for Payment Plans IMG activity has been removed from Release 4.72.

1.1.30 Information System

Use

Preselections of Master Data (Transaction FPSELP)

When you select by dunning data, you can now consider only open items if required previously allcleared items were selected automatically.

Data Extracts (GDPdU)

From Release 4.72, all developments for the realization of the German Principles of Data Access and

______________________________________________________________SAP AG 29

SAP-System______________________________________________________________

Verifiability of Digital Documentation (GDPdU) area available in all releases maintained by SAP. InReleases 4.64, 4.63, and 4.61 however, only the export programs FPDE_EXP, FPDE_AEXP, andFPDE_EXTR are available. All export programs support the SAP format AIS, which can be importedinto IDEA. For the Contract Accounts Receivable and Payable objects, the following export, import, anddeletion transactions are available:

o Document Extracts

- FPDE_EXP

- FPDE_AEXP

- FPDE_IMP

- FPDE_DELYou can also select SD documents for the FI-CA documents and export them.

o Partner Extracts

- FPDEP_EXP

- FPDEP_IMP

- FPDEP_DEL

o Customizing Extracts

- FPDEC_EXP

- FPDEC_IMP

- FPDEC_DELYou can use the transactions FPDE_EXTR (evaluation system) and FPDE (extract overview) for allextract objects.

Evaluating Open Items

Transaction FPO4P provides you with a parallel variant for transaction FPO4. For each interval, thistransaction creates a list and a list with the totals records (similar to transaction FPO1P (Open Items forKey Date Parallel). However, in contrast to transaction FPO4, transaction FPO1P has certain restrictions.Parallelization is therefore only possible if the layout sorting corresponds to the parallelization object.The output is not in ALV format and no additional output in the dataset is possible.

For transaction FPO4, the memory has been optimized. If you do not want to display line items, thereport no longer collects all items in the memory if you have selected an object and a variant (technicalsettings) (see also the documentation for the report).

You can now group the spool requests for individual intervals for the evaluation with transaction FPO1Pand transaction FPO4P.

Transactions FPO1 and FPO1P can now also calculate the evaluation for different currency types andtherefore consider a currency valuation. Transaction FPRECL has therefore also been changed. You cannow also post adjustments to reclassifications for different currency types.

______________________________________________________________SAP AG 30

SAP-System______________________________________________________________

1.1.31 Deferral and Installment Plan

Use

Clearing Locks on Installment Plan Items

When you display installment plans, you can now also display the clearing locks as well as the payment,dunning, and interest locks. When you create and change installment plans, you can create and setclearing locks.

Improved Display of Processing Locks

Previously, you could only display the different processing locks (payment, dunning, interest, andclearing locks) in installment plan items via a joint icon (lock), which, when you placed the cursor on it,displayed the type of locks that existed in a quick info. You could only see details, such as the lockreason, by double-clicking on the icon. The display of the installment plan items now also has, in additionto the joint lock icon, a column for each processing lock with the respective lock reason. If there areseveral locks of the same type with different lock reasons, a tilde appears (~). Double-click on one ofthese fields to display the details for the locks.

Easier Maintenance of Processing Locks

Previously, you could only maintain processing locks (payment, dunning, interest, and clearing locks) forinstallment plan items by double-clicking on the field for displaying the lock icon. Then you had to selectthe type of lock. Now you can maintain the lock you have selected directly by double-clicking on one ofthe new table fields. You can also set an unlimited (time) lock by entering a lock reason directly. If thereis only an unlimited (time) lock for a lock type, you remove this from the table field by deleting the lockreason.

Selection by Classification Key

You can also select items for which a new installment plan is to be created by classification key.

Standard Company Code instead of Responsible Company Code

If the system cannot derive a unique company code from the original receivables when you are creatingan installment plan, the system posts the installment plan to the standard company code.

New Display Fields in the Installment Plan History

When you display the installment plan history (SAP menu: Account -> More Information ->Installment Plan History), the contract account, business partner, and address of the business partner aredisplayed for each installment plan.

New Fields in the Header Data of the Installment Plan History

The fields Number of Installments and Distributed Interest and Charges are stored in the header datafor the installment plan history.

Determination of Company Code, Contract, Business Area, and Business Place No Longer inEvent 3000

When you create an installment plan, the company code, contract, business area, and business place aretaken from the original item as standard, as long as these fields have the same value in all original itemsselected. Previously, this check took place in a standard module processed in event 3000. This check nowtakes place in the standard coding before event 3000. The source code of the standard module

______________________________________________________________SAP AG 31

SAP-System______________________________________________________________

FKK_SAMPLE_3000 has been deleted.

If you do not want to fill these fields in the installment plan, or want to enter other values, you can do thisby defining event 3000 accordingly.

Printing of Payment Forms for Installment Plans - List of Correspondence Created

When you are printing payment forms for installment plans (SAP menu: Periodic Processing -> ForContract Accounts -> Correspondence -> Print Installment Plan Payment Forms), you can use theentry Correspondence in the environment menu to display a list of the correspondence created(installment plan letters and payment forms).

1.1.32 Integration

Use

Event 4030: Determination of SD/FI-CA Transaction

Before the upgrade from Release 4.6* to Release 4.7*, you have to close all of the reconciliation keys inthe old system and transfer the postings to the General Ledger and Profitability Analysis (CO-PA).

Event 4030 has been introduced to determine the main and subtransaction of an FI-CA document duringthe transfer of an SD billing document. In this event you have access to all of the information in an SDbilling document, which means that a more detailed transaction determination is possible here in contrastto Customizing.

With the new event 4040 you can restrict the selection of contract accounts when you create/change anSD order.

In the SD document flow, FI-CA documents that have already been archived are also displayed now.

Transfer of Totals Records to the General Ledger (Report RFKKGL00)

Errors in the transfer of FI-CA totals records to the general ledger no longer lead to a programtermination. From Release 4.72, report RFKKGL00 continues the transfer with the next company codeand logs the errors in the spool list. There you can check the completeness of the transfer.

Integration of FI-CA with SAP Credit Management

With SAP Credit Management you can manage liabilities and scores for a business partner. The centralCredit Management server manages information from different systems, such as CRM, ContractAccounts Receivable and Payable (FI-CA), and Accounts Receivable Accounting (FI-AR), and carriesout operational credit queries. The use of the interface technology of the Exchange Infrastructure meansthat you can also connect external systems to SAP Credit Management.

FI-CA now has an interface for transferring credit information from SAP Credit Management.

The FI-CA document interfaces (report RFKKBIB0, BAPI, IDoc interface) support the transfer of thepartner message ID for SAP Credit Management. This transfer guarantees the synchronization of theliability update over several systems.

In FI-CA there are mass activities for the following activities:

o Sending the liability for a business partner to SAP Credit Management

o Sending an FI summary to SAP Credit Management

______________________________________________________________SAP AG 32

SAP-System______________________________________________________________

o Replication of the score in SAP Credit Management

FI-CA also supports the liability query for the online credit check in SAP Credit Management.

You can influence the program flow in the following events:

o 4500: Add FI Summary

o 4501: Filter Open Items for Liability Determination

o 4502: Determination of Liability Category

For a description of the integration of industry-specific processes, see the release information for thecorresponding industry components.


You configure SAP Credit Management in the Implementation Guide for Contract AccountsReceivable and Payable under Integration -> Financial Supply Chain Management -> CreditManagement.

o In order for the internal processes of Contract Accounts Receivable and Payable (for example,creditworthiness) to derive the data from SAP Credit Management, you have to activate CreditManagement here.

o In the activity Define Specifications for Credit Management, you define the default values, such asthe interest rate for the liability subject to interest and the liability category.

o The credit segments that you enter in the activity Maintain Credit Segments must agree with thoseof SAP Credit Management. There the credit segments are used to split the liability into differentareas (for example, country A and B).

o In the activity Assign Open Items to Credit Segments, you use the parameters Posting Area,Division, Account Determination ID, and Business Area to decide which credit segment an openitem is to be assigned to.

1.1.33 Interest Calculation

Use

Interest Calculation Rule

There are two new calculation methods for defining interest calculation rules:

o 30/30EYou should only use the method 30/30E for exponential interest calculation. The system calculatesexponential interest on a monthly basis.

o act/actY In the method act/actY, the suffix Y stands for Year. It indicates that the calculation is based on thenumber of days in a calendar year.

Setting #Interest Calculation To Date

With a function module processed in event 2065 you can change the date for the Interest CalculationTo for clearing items.

______________________________________________________________SAP AG 33

SAP-System______________________________________________________________

For amounts cleared in the account maintenance, as standard the due date of the invoice and clearing dateof both items are used to calculate the interest.

In event 2065 you can use the due date of the invoice amount and the value date of the payment amountto calculate the interest for amounts cleared in the account maintenance.


You define interest calculation rules in the Implementation Guide for Contract Accounts Receivable andPayable under Business Transactions -> Interest Calculation -> Item Interest Calculation ->Define Interest Calculation Rule.

1.1.34 Insurance Invoices

Use

From Release 4.72 of SAP for Insurance, you can improve the performance of the Create InsuranceInvoices mass activity (transaction VYCOV004), by setting the following flags for access optimization onthe Detailed Selections tab page:

o Suppress Collective Invoices

o Ignore Collective Invoice Parameters for Account

Only set the Suppress Collective Invoices flag if no collective invoices are created in your company.

Only set the Ignore Collective Invoice Parameters for Account flag if the paramters for collectiveinvoices are never set for the contract account/partner relationship in your company.

1.1.35 Post Documents (Extended)

Use

From SAP for Insurance 4.72, you can also use the Post Document application to post documents usingItalin tax law.

1.1.36 Business Locks

Use

Setting Processing Locks

With the new transaction FKLOCK2 (Set Processing Locks) in the SAP menu under PeriodicProcessing -> For Contract Accounts, you can create processing locks. From the selection criteriaBusiness Partner, Contract Account, Contract, Company Code, you can set mass locks for acombination of Lock Category, Process, Lock Reason. Locks created in this way contain the data ofthe creating run in the fields DFKKLOCKS-LAUFI and DFKKLOCKS-LAUFD in table DFKKLOCKS.

______________________________________________________________SAP AG 34

SAP-System______________________________________________________________

You have to define event 9570 for the following application-specific locks:

Lock Category Object

21 Insurance policy

22 Partner locks for insurance policy

41 Utility contract

51 Contract object partner account

To delete mass locks, you can use transaction FPLKDEL (Delete Mass Locks Set) in the SAP menuunder Periodic Processing -> For Contract Accounts.

1.1.37 Mass Activities

Use

Repeated Processing of a Job Interval

If an interval cannot be processed in a payment run, interest run, or interest calculation run for cashsecurity deposits because the data is locked by another processing function, the system can restart theprocessing of this interval automatically and as frequently as required.


You have to enter the maximum number of repetitions in the field Maximum Int. Repetitions in thespecifications for General Control on the tab page Job Control under Technical Settings -> PrepareMass Activities in the Implementation Guide for Contract Accounts Receivable and Payable.

1.1.38 Master Data

Use

Changing the Bank Data of a Business Partner

With the new transaction Maintain Payment Data (FPP4) (see SAP menu: Master Data -> BusinessPartner), you can:

o Create new bank details

o Change existing bank details

o Delete existing bank details

o Create new payment cards

o Change existing payment card details

o Create customer contacts

o Print confirmation letters

______________________________________________________________SAP AG 35

SAP-System______________________________________________________________

This makes changing business partner-related bank data much easier. In the transaction MaintainPayment Data, you can, for example, change the bank details of a customer who changes from being acash payer to a direct debit payer simultaneously in the business partner master record and in dependentobjects, such as the contract account.

You can also control follow-up actions, such as reversing dunning notices, by means of flexible rules.

If you set the indicator Create Bank ID in the client-specific settings in Customizing, in event 1053 youcan determine new bank details ID for the business partner concerned.

If you set the indicator Create Credit Card ID in the client-specific settings in Customizing, in event1054 you can determine a new payment card ID for the business partner concerned.

With a function module processed in event 1083 you can make further changes to the contract accountwhen you save the data. In this event, you can, for example, change the field Posting Control Group inthe contract account if a customer changes from being a cash payer to a direct debit payer.


You make specifications for changing bank data in the Implementation Guide for Contract AccountsReceivable and Payable under Basic Functions -> Contract Partner -> Changes to PaymentTransactions in the following activities:

o Client-Specific Settings

o Company Code-Specific Settings

o Define Processing Variants

o Define Rules for Follow-Up Actions

o Specifications for Posting Credits in Follow-Up Actions

If you want to send confirmation letters, define the required form for correspondence type 0036 underBasic Functions -> Correspondence -> Define Application Forms for Correspondence.

You define event modules under Program Enhancements -> Define Customer-Specific FunctionModules.

1.1.39 Evaluation of Open Items

Use

Currency Type and Currency Valuation

When you enter a currency type on the selection screen for the Key Date-Related Open Item List(transaction FPO1), the report replaces the first local currency with a currency with this currency type. Ifyou also enter a valuation variant and a valuation key date, the report does not display the originalamounts of the items; instead, it displays the amounts calculated by the currency valuation for thevaluation key date.

______________________________________________________________SAP AG 36

SAP-System______________________________________________________________

1.1.40 Payment Plans

Use

The following changes have been made to the Payment Plans area for Release 4.72 of SAP for Insurance:

Discontinued Functions

The Debt Recognition and Payment Plan Locks functions are no longer supported.

Events

Events V062 (Debt Recognition) and V063 (Taxes from INSTAXS insurance tax schedule) no longer run.

The following new events have been added:

o V054 (Payment Plans Debit Entry: Summarization of Customer Fields): Summarization of customerfields

o V604 (Payment Plan Items: Set ARCHI in Debit Entry): Set VVSCPOS-ARCHI in debit entry (newpayment plan items only)

o V605 (Payment Plans: Check Payment Plan Item): Consistency checks on VVSCPOS andVVSCITEM (Payment Plan Item + Payment Plan Subitem) in simulation and debit entry (newpayment plan items only)

o V606 (Payment Plans: Change to a Renewed Payment Plan Item): Changes to a renewed paymentplan item

The following events have been changed:

o V051 (Payment Plans Debit Entry: Create Charges): Charges from charges schedule for paymentplan keyTo improve performance (and as no charges are posted, in most cases), the creditworthiness is nolonger transferred for the event module, but must be determined within it. You can find an examplefor adjusting customer-specific modules in the VKKSA2_CHARGES_CREATE_V051 functionmodule.

o V050 (Payment Plans Debit Entry: Enhance Lines) is now also called up for tax lines that have beencreated due to MWSKZ. You have the new OPKTAX category for this, and a new parameter.

o Function modules for activities from the debit entry now contain the new I_UPDATE_TASKparameter (see above). If the parameter is set, database changes are made in the function module,using the updater.

New Parameter

In the new ISCD_SCPOS_MAINTAIN function module, you can find the new I_UPDATE_TASKparameter (database changes take place using the updater).

New Functions

o In date specification for payment plan changes, amoung changes and early endings, the date hasbeen extended with a field for specifying a time. Mutiple changes of the same type, in the samesecond, are not permitted. The time has no effect on the actual change. It is simply used todetermine a unique processing sequence.

o Multiple early endings can be entered for each payment plan item, if no ending has yet been

______________________________________________________________SAP AG 37

SAP-System______________________________________________________________

executed. The last ending entered is executed in the next debit entry.

o When creating payment plan items, you will be able to transfer the amount for individualinstallments, instead of the total amount VVSCPOS-AMOUNT_INST field).

o When ending payment plan items early, you will be able to transfer the difference to be posted onthe end date, instead of the required amount (VVSCPOS-AMOUNT_END field).

New BAPIs

New BAPIs for payment plans are available in the new release, under the Payplan business object(BUSISI013 object category), which fill the interface for the function moduleISCD_SCPOS_MAINTAIN and return prepared system messages (error messages)

The Payplan business object, with its methods, presents no new update function, but simplifies thehandling of the payment plan interface (ISCD_SCPOS_MAINTAIN function module). You can use themethods for the object to create, change, reverse or display payment plan items.

In detail, the following methods are delivered:

o AmountChange (BAPI_PPLAN_CHANGE_AMOUNT): Amount change for payment plan items(instance method)

o CreateGeneralLedgerTransfer (BAPI_PPLAN_GL_TRANSFER): G/L transfer posting (classmethod)

o CreateItem (BAPI_PPLAN_ITEM_CREATE): Create payment plan items (class method)

o CreateSubLedgerTransfer (BAPI_PPLAN_SUBL_TRANSFER): Subledger transfer posting (classmethod)

o EarlyEnding (BAPI_PPLAN_END): Early ending of payment plan items (instance method)

o GetAdditional fields (BAPI_PPLAN_CUST_FIELDS_VZK): Read customer-specific fields andadditional account assignment for insurance (class method)

o GetDetails (BAPI_PPLAN_GETDETAILS): Details for payment plan items (instance method)

o GetList (BAPI_PPLAN_GETLIST): Read payment plan items (class method)

o Reverse (BAPI_PPLAN_REVERSE): Payment plan reversal (instance method)

o ReverseBuscase (BAPI_PPLAN_REVERSE_BUSCASE): Business case reversal (instance method)

o ReverseItem (BAPI_PPLAN_REVERSE_ITEM): Payment plan item reversal (instance method)


Due to internal changes in the payment plans area, we recommend that you attempt to process as manypayment plan items and payment plan changes as possible, before upgrading with debit entry.

See also

You can find further information about event V063 (taxes from insurance tax schedule INSTAXS) in therelease note entitled Creation of Tax Items.

You can find information about changes to payment plan Customizing in the release note entitledChanges to Contract Accounts Receivable & Payable IMG.

You can find detailed information about the new BAPIs from the document for methods, and the businessobject, in the BAPI Explorer.

______________________________________________________________SAP AG 38

SAP-System______________________________________________________________

1.1.41 Processing Incoming and Outgoing Payments

Use

Payment Lot: Archive Connection

From Release 4.72, you can display archived lots and non-archived lots.

When you display documents posted by a payment lot, you can also display the related payment lot itemsif the lot has been archived. This display option requires an additional index table that is created duringarchiving with effect from Release 4.72. For payment lots archived before 4.72, you can recreate theseindex entries using report RFKKPLAR.

Payment Lot: Default Value for New Key

If you want to create a new lot, you can have the system default a suitable key. The prerequisite for thisfunction is that you have registered a suitable module for event 0211.

Payment Lot: Installation-Specific Fields in Items

If additional fields are included in the payment lot item via the customer include CI_FKKZP, you candisplay these on the detail screen and the list screen. To do this you have to provide an include screen.The program name and the number of the include screen are determined in event 0222. For moreinformation see the documentation and the coding examples in the related sample function moduleFKK_SAMPLE_0222.

Payment Lot: Installation-Specific Additional Function

The detail screen for the payment lot item contains an installation-specific addition function that you candefine to meet your requirements. This function is available under Extras -> XXX, and you can also callit up via a separate pushbutton (optional). In event 0232, the texts for the processing menu and thefunction key (xxx) are determined, along with which function module is to be called when the userexecutes this function. For more information, see the documentation for the function moduleFKK_SAMPLE_0232.

Payment Lot: Clarification

o From Release 4.72, you can have the clarification account determined dependent on the documenttype. Posting area 1040 has been extended accordingly.

o From Release 4.72, clerks can also create notes during clarification.

o If clearing is to be posted online during clarification, the note to payee entered in the payment lotalso appears on the processing screen for the open items (first 80 characters).

o In the search with errors function, you can now also search for business partner with just the name(and optionally the city) in the field Sold-to-Party/Account Holder.

Payment Lot: Changes to Protected Fields

o In check lots, you can use the special function Correct Check Number to correct the check numberfor individual payments in lots that have already been closed or posted. You may need to make acorrection, for example, if, when creating the check deposit list, you discover that check numbers

______________________________________________________________SAP AG 39

SAP-System______________________________________________________________

have been entered incorrectly. To carry out this function you need authorization 014 forauthorization object F_KK_SOND. You make the change in the check lot display. On the firstscreen, choose Edit -> Correct Check Numbers. Then call up the detailed display for the checkpayment to be corrected and select Edit -> Correct Check Numbers. The check number field isthen ready for input you can overwrite the number and save.

o In payment lots created automatically, you can change the bank data of the payer and the note topayee during clarification. A correction is necessary, for example, if a data reader has incorrectlyinterpreted a hand-written note to payee. To carry out this function you need authorization 017 forauthorization object F_KK_SOND. To make the fields on the tab pages Payment Data or Note toPayee ready for input, select Edit -> Change Bank Data.

Payment Lot: Transfer with Report RFKKZE00

In the transfer structures BFKKZP and BFKKZS (ZFKKZP/ZFKKZS), the field lengths of the fieldsSELW1, SELW2, and SELW3 have been extended from 30 characters to 35.

If you do not create the files with these record structures with ABAP programs, you may have toadjust the data declarations and the coding in the programs.


Payment Lot: Clarification

You define the clarification account in the Implementation Guide for Contract Accounts Receivable andPayable under Business Transactions -> Payments -> Processing of Incoming/OutgoingPayments -> Define Clarification Account. If you want to use the document type as selection criterion,you first have to select the field Document Type as additional key field via Goto -> Key Selection.

1.1.42 Creating Payment Plan Items

Use

From SAP for Insurance 4.72, you can no longer use the NO DATA flag when creating payment planitems to display that the field is empty.

Empty fields are to be left as they are.

1.1.43 Payment Transactions

Use

Payment Program: Restriction to One Payment Card Type

From Release 4.72, you can restrict the payment run to one payment card type. You can then run separatepayment runs for each payment card type, event though the payment method is always the same cardpayment.

For contract accounts with other payment card types, a corresponding message is created in theapplication log and a payment exception is created.

______________________________________________________________SAP AG 40

SAP-System______________________________________________________________

Payment Program: Selection of Partner Bank via New Event

In the new event 0652, you can override the automatic selection of partner banks created by the paymentprogram.

In the standard system, the partner bank is selected as a result of the bank details defined either in thecontract account or the contract (differentiated by incoming payment and outgoing payment). You canoverride this by explicitly specifying bank details in the line item. However, it is not possible, forexample, to select a partner bank dependent on the currency of the items paid if these bank details are notentered in the items to be paid.

Using event 0652, you can now set a different bank details ID dependent on the items to be paid, orprevent payment.

See the documentation for function module FKK_SAMPLE_0652.

Payment Media Creation: Settings for the Note to Payee

The standard options for defining the note to payee have been enhanced for the creation of paymentmedia. In the user-defined specifications, you can now specify the number of items to be prepared onlyonce per payment. This avoids the contents of PAYH and PAYHX being output per item, even thoughthese are the same for all items.

In the definition of the item content (FQP5 -> Note to Payee: Content), the sequence (item number)decides whether the content is prepared per payment or per item. If, for example, you have specified 2information items per payment and 1 information item per item, you have to provide a total of 3 itemswith content. The first two apply per payment, which means that here only the fields from the structuresPAYH and PAYHX are useful. The third item is then repeated for each item. The fields from thestructure PAYP are useful here.

Payment Media Creation: Correspondence Banks

If you use the payment media formats EDIFACT, S.W.I.F.T. (MT 100, 101, 103, 104, 200, and 202),(customer development), from Release 4.72 you can define correspondence banks. This means that youcan specify a bank chain with up to three intermediary banks (correspondence banks) in Customizing forthe transfer from one bank to another. You can define general and recipient-specific bank chains. Youthen specify recipient-specific bank chains in the transactions for creating and changing business partnerdata (FPP1, FPP2) on the tab page Payment Transactions, in the area Bank Chains.

The function module FI_PAYMENT_BANK_CHAIN_SET determines the bank chains during thepayment media creation and places them in the corresponding structures.

If you want to use the function for the payment media formats stated, you have to add the call of thefunction module FI_PAYMENT_BANK_CHAIN_SET to the function modules defined for the events 20and 30, or, for customer-defined developments, the events 21 and 31. The function moduleFI_PAYMENT_BANK_CHAIN_SET contains the data in the corresponding event module as importparameter.

Check Management: New Status for Processing Check Locks

A new check status (Locked) has been introduced with Release 4.72. This means that you can lock acheck and report the lock to the bank, without having to reverse the related payment or issue areplacement check. The check is locked in check management and reported to the bank using transactionFPCHX. After a specific deadline (usually 24 hours) the bank guarantees that this check can no longer becashed. You reverse the related payment document after this deadline by regularly scheduling transactionFPCHS so that the cleared items are open again. By running the payment run again you can create a new

______________________________________________________________SAP AG 41

SAP-System______________________________________________________________

check if required. If checks are cashed within the deadline, you can define, in the settings for the voidingreason, whether the checks are to be deemed 'cashed' automatically or whether clarification cases are tobe created.

This procedure is interesting for US customers and is known by the name 'Stop Payment'. It is analternative to the previous way of issuing a replacement check. Invalid checks that have not yet left thecompany premises should be voided and reissued as previously. A check lock is not necessary in thesecases.

Check Management: Enhanced Maintenance in Change Mode

If you want to correct the data of a check that was created via a payment run, only a few fields aremodifiable. You cannot even change a status set by accident. From Release 4.72, the button'Administrator has been added in change mode (F6). When you press this button, additional fields areready for input. To carry out this function you need authorization 018 for authorization objectF_KK_SOND.


You make the settings for bank chains in the Implementation Guide for Contract Accounts Receivableand Payable under Basic Functions -> Bank Chains:

o Define Scenario

o Activate Bank Chains

o Set Up General Bank Chains

In the activity Define Scenario, you define for each scenario, whether the bank chain is determined viathe general bank chain search and/or via the partner-specific bank chain search. If both fields are set, thepartner-specific bank chain search has priority over the general bank chain search. Using the fieldsSender Bank, Recipient Bank Country, Recipient Bank, and Currency, you can define a ranking forthe bank chain search for each scenario. SAP delivers four standard scenarios; you can also generate yourown scenarios.

The bank chains that you create in the activity Set Up General Bank Chains are independent of thebank details of a business partner or of the house banks. For a bank chain ID, you can create up to threeintermediary banks. The intermediary banks are linked independently of the recipient and sender banks.

Check Management: Settings for Voiding Reasons

If you want to use the new check status 'Locked, you need a voiding reason or a lock reason, as forvoiding. Whether a reason is permitted as a lock reason depends on the indicator Lock.

You can also define whether the cashing of a locked or voided check is to be posted automatically orwhether a clarification case (for check encashment) is to be created.

In the field Activity, you can enter a 6 digit code to control additional activities (for example, settinglimited clearing locks) in customer modules. You can evaluate this field directly or use it as a key foryour own customer table.

______________________________________________________________SAP AG 42

SAP-System______________________________________________________________

1.1.44 Postings and Documents

Use

Postings and Documents: Classification Key as New Characteristic in Document

The new attribute Classification Key has been added to the Contract Accounts Receivable and Payabledocument and the request. The classification key provides a similar function to the reference number, butallows keys with a length of up to 35 characters. The classification key is an enhancement supported inthe system. This means that the attribute is not initially active in the system delivered; you have toactivate it explicitly in your installation.

Functions of the Classification Key

The classification key

o Can be entered in the document header

o Is available as input field in the document display, document change, document reversal, and massreversal, and you can use this field to identify the required document(s)

o Is inherited in the business partner items and can be displayed in the account balance or in theprocessing of open items

o Can be used as selection criterion in the account balance, in the selection of open items (forexample, in the payment lot or in online posting), and for the write-off or creation of an installmentplan

o Is a possible selection criterion in payment advice notes for incoming payments

Activating the Classification Key

You activate the field Classification Key in Customizing using a report that creates the required fieldsand database indexes. In test mode, the report shows which enhancements would be made.

If the classification key is active and you have posted documents with classification keys, the systemadministrator must update the database statistics for table DFKKKO. This is the only way to make surethat the new indexes are also used.

If you use requests, the same applies for table DFKKORDERPOS.

Deactivating the Classification Key

You can deactivate the classification key but only manually. To do this, you have to remove the fieldOPORD from the CI includes to which it was added. You then have to convert the database tables; thiscan involve a long runtime if there are a lot of data records affected.

SAP therefore recommends that you weigh-up the use of the classification key and then adhere to thisdecision.

Postings and Documents: Negative Postings

From Release 4.72 you can create negative postings in Contract Accounts Receivable and Payable. A

______________________________________________________________SAP AG 43

SAP-System______________________________________________________________

negative posting reduces the transaction figures for the account posted to in the general ledger. A debitposting as negative posting therefore does not lead to an increase of the debit transaction figures; it leadsto a reduction of the credit transaction figures. This enables you to show transaction figures for accountsafter an incorrect posting and subsequent correction (for example, invoice posting and reversal) as ifneither the incorrect posting nor the correction had taken place.

Negative postings have been supported in the general ledger (FI-GL) for a long time. You decide whetherto permit negative postings at company code level. The corresponding setting in the company code tableis also effective for Contract Accounts Payable and Receivable.

In addition, in Contract Accounts Receivable and Payable, the document type decides whether a postingis to be posted negatively. You can designate a document type such that negative postings are alwayscreated, or such that negative postings are only created for corrections in the same fiscal year. For moreinformation about the setting for the document type, see the Customizing for the document types and thefield documentation for the field Negative Posting.

A description of negative postings for the most important business transaction follows:

Reversal

For a reversal, the document type used decides:

o Whether a negative posting is never permitted

o Whether a negative posting is always permitted

o That a negative posting is created if the posting and reversal are in the same fiscal year

A special feature is that the items in the reversal document for which the account to be posted to has beenswapped in comparison to the original document are not posted negatively This can be the case foraperiodic reversals (swap of P&L accounts) or for posting incoming payments where the reversal is usedto post back to the clarification account.

Resetting Clearing

After resetting clearing, all accounts should appear as if the clearing had not taken place. This means thatthe inverse posting of cash discount, small differences, exchange rate differences, and taxes that wereposted due to the clearing are to be posted negatively. The display in the receivables accounts is retained.

Example

You reset clearing for a payment received. After the clearing reset, the payment with clearing of openitems becomes a type of payment on account again, which means that the credit from the payment is anopen item in the receivables account. From the view of the account balance in the receivables account, itis irrelevant whether there was a payment on account or whether items were cleared.

Returns

Returns should be treated like reversals. The first item in a returns clearing account is, however, neverposted negatively; the same applies to returns charges.

Individual Identification of Individual Posting Items

If you want to post a document for which negative postings are required for all items manually, all you

______________________________________________________________SAP AG 44

SAP-System______________________________________________________________

have to do is select an appropriate document type. However, if you only want to post individual itemsnegatively, you have to enter the entire transaction in two documents.

Example

Transfer posting from an incorrect G/L account to the correct G/L account. The reset in the incorrect G/Laccount should be posted negatively, the posting to the correct account not. First enter a negative posting:Clearing account to incorrect G/L account. Then a 'normal posting: Correct G/L account to clearingaccount.

Payments on Account

If, on receipt of payment, you first post on account instead of clearing immediately and then carry outclearing later, (for example, via account maintenance or during processing of a subsequent payment), thedebit and credit side of the receivables account increases by the amount of the payment on account. If youwant to avoid this effect, make sure that every clearing of a posting on account is posted negatively. Todo this, you have to indicate in Customizing for the main and subtransaction used for payments onaccount that each clearing of this item is to be posted negatively.

Postings and Documents: Parallel Open Item Processing for Partners

If a business partner has several contract accounts, before Release 4.72, it was not possible for two clerksto process open items in different contract accounts for this business partner simultaneously (for example,during account maintenance). Parallel processing in different accounts of a business partner is possiblefrom Release 4.72.

Postings and Documents: Hold Status of Open Item Processing

During manual processing of clearing transactions, you can save the status of open item processing andreload it later. For this purpose, the new functions Hold Processing Status and Retrieve ProcessingStatus are available on the processing screen for open items. When you hold the status, you have tospecify an identification. You can hold several processing statuses in parallel for the same object (forexample, same business partner, same collective bill).

A processing status is held in the system for 30 days. This period starts from the last time the status issaved.

For each processing status, the system also saves the object being processed in addition to theidentification. This is either the business partner to whom the open items belong, or for assignment atdetail level, the collective bill, the installment plan or the bundle for which assignment of clearingamounts is to take place at the level of the related original item.

If the business partner is not unique, the partner with the most active items is set.

When you retrieve a held status, in the detail assignment for collective bills, installment plans, andbundles, only identifications that belong to the object named are permitted. The possible entries help (F4)offers a correspondingly restricted selection.

When you retrieve a held status during the processing of open items for one or more business partners,the identifications permitted are those where the business partner held is correct for at least one of thecurrently selected items. The possible entries help (F4) also offers a correspondingly restricted selectionhere.

In general, the held status is mixed with the current selected items. These can be different to the itemsthat were selected when the processing status was held. Possible causes are:

______________________________________________________________SAP AG 45

SAP-System______________________________________________________________

o Other selection criteria

o Clearing or partial clearing that has taken place in the meantime

o Different amounts for clearing in a different currencyHere the amounts are translated for open item processing and the translation result may havechanged due to changes in the exchange rate.

If a clearing amount was recorded in a held status, and this clearing amount is higher than the totalamount of the open items when the status is retrieved, the maximum possible clearing amount is set. If acash discount amount was specified, this is reduced accordingly so that the cash discount percentage rateis retained.

Whenever the held status cannot be used again completely, the user sees a message with details of thevariance in the long text.

Postings and Documents: Transfer Postings in Account Maintenance

In the account maintenance, you can transfer difference amounts to a G/L account defined inCustomizing. You have to specify the amount to be posted and similar to the payment lot a shortaccount assignment that the system can use to determine the company code, account, business area, andCO account assignments.

The fields for the transfer posting are only active if the user has been assigned to a tolerance group forwhich a maximum amount and maximum percentage rate for the transfer posting have been specified inCustomizing.

You cannot transfer to tax-relevant accounts.

Postings and Documents: Arrears Surcharges

If open items are cleared by payments or clearing of payments, you can define arrears surcharges. Thesesurcharges have the opposite effect to cash discount. For example, if you set a surcharge of 2.00 for aninvoice for 100.00, a payment of 100.00 leads to postings for partial clearing in the amount of 98.04 andrevenue from payment surcharges of 1.96.

Since the calculation of surcharges is dependent on the value date of the payment, clearing transactionswith surcharges can only consider additional credit items (for example, from payments on account) ifthey have the same due date. All other credit items are locked for the current clearing transaction.

If clearing processing takes place online, you can deactivate or reduce the surcharges calculatedmanually.

The following transactions enable the calculation and posting or surcharges:

o Payment Lot

o Cash Desk and Cash Journal

o General posting online

o Account Maintenance

o Automatic Clearing

In order to enable the calculation of surcharges you have to define an installation-specific functionmodule for event 0104.

Postings and Documents: Mass Postings and Cash Management

______________________________________________________________SAP AG 46

SAP-System______________________________________________________________

For mass postings that run in parallel processes, waiting time may occur due to competing accessesduring the update of data for Cash Management. Contract Accounts Receivable and Payable thereforeoffers a parallel update mode that you can activate for specific categories of mass runs. CashManagement is then updated at the end of each process. If the process is terminated before the CashManagement update, the update takes place when you close the relevant reconciliation key. If theupdate also fails here, you can transfer the data recorded separately individually. To do this, in the menufor Contract Accounts Receivable and Payable choose Periodic Processing -> Execution -> CashManagement Transfer.

Document Transfer

During the document transfer, you can also transfer the identification of the partner message from SAPCredit Management (field PRTID) with the header structure.

You can also transfer the identification of the subapplication in Contract Accounts Receivable andPayable (field SUBAP) with the item structure (BFKKOP).

During the document transfer, you can transfer the company code for the automatic payment transactions(field PYBUK) with the item

structure (BFKKOP).

You can also transfer the following new structures:

o BFKKOPREL: Relation between objects

o BFKKOPC: Card supplement for open items


Classification Keys

To activate the classification key, in the Implementation Guide for Contract Accounts Receivable andPayable choose Program Enhancements -> Prepared Enhancements -> Classification Key.

Postings and Documents: Negative Postings

You make the setting for the company code (negative postings possible) in the Implementation Guide forFinancial Accounting under Financial Accounting Global Settings -> Company Code -> Checkand Supplement Global Parameters.

You make the setting for the document type in the Implementation Guide for Contract AccountsReceivable and Payable under Basic Functions -> Postings and Documents -> Document ->Maintain Document Account Assignments -> Document Types -> Maintain Document Typesand Assign Number Ranges.

The main and subtransactions that you want to define for a negative clearing (example: Payments onAccount) are in the Implementation Guide for Contract Accounts Receivable and Payable under BasicFunctions -> Postings and Documents -> Document -> Maintain Document AccountAssignments -> Maintain Subtransactions.

Transfer Postings in Account Maintenance

You define the short account assignments in the Implementation Guide for Contract Accounts Receivableand Payable under Basic Functions -> Open Item Management -> Short Account Assignments forTransfer Postings in Account Maintenance.

You maintain the tolerance groups under Basic Functions -> Postings and Documents -> Document

______________________________________________________________SAP AG 47

SAP-System______________________________________________________________

-> Tolerance Groups for Amount Limits and then the entries Define Tolerance Groups andAssignment of Tolerance Groups to Users.

Arrears Surcharges

To create the installation-specific function module for event 0104 and to register, in the ImplementationGuide for Contract Accounts Receivable and Payable choose Program Enhancements -> DefineCustomer-Specific Function Modules.

To define the accounts to be posted to in the case of arrears surcharges, choose Basic Functions ->Postings and Documents -> Document -> Define Account Assignments for Automatic Postings-> Automatic G/L Account Determination -> Define Accounts for Arrears Surcharges.

Mass Postings and Cash Management

You activate the parallel update of Cash Management for selected processes via: Technical Settings-> Activate Parallel Update of Cash Management.

1.1.45 Prenotifications

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following prenotificationfunctions have been added:

o The Create Prenotification File program has been enhanced to cover requirements for Denmark.SAP delivers a new payment medium format, PBS_PRENOTE, required for sending prenotificationfiles to the Danish clearing house PBS.

o The Process Return File program has been enhanced to handle incoming files in formats DK603 forDenmark, AUTH for Finland, and ACH for the United States. It additionally creates a PBS605 fileto send back to the Danish clearing house, PBS, if required; and it processes bank statement datacontained in the return file sent by the US clearing house, ACH.


In Denmark, to establish an agreement with PBS, you must include your customers' CPR or CVR numberin the prenotification file. To maintain these numbers, from the SAP Easy Access menu, chooseAccounting -> Financial Accounting -> Contract Accounts Receivable and Payable -> MasterData -> Enter Registration ID (DK).


A Business Add-In is available for Denmark that enables you to delete business partner CPR and CVRnumbers after you have processed the return file from PBS. You can create an implementation inCustomizing for Financial Accounting, under Contract Accounts Receivable and Payable ->Business Transations -> Payments -> Incoming/Outgoing Payment Processing -> Add-In:Deletion of CPR/CVR Numbers (Denmark).

______________________________________________________________SAP AG 48

SAP-System______________________________________________________________

1.1.46 Collections in the Print Workbench

Use

Using Collections, you can now group application forms to process them together.

A Collection is an application form of the form type Collection.

In a Collection, you can group both application forms from the same form class, and also applicationforms from different form classes. You can define your own parameters for the technical components of aCollection, for example, a specific printer. You can classify the individual application forms so that theyare issued sequentially or bundled. You can process Collections using transaction EFRM (SAP menu:Print Workbench -> Application Form -> Process), as for application forms.

1.1.47 New Reports

Use

Report RFKK_MA_SCHEDULER

The program RFKK_MA_SCHEDULER creates and starts new mass activity runs. Once the run hasstarted, the program monitors all parallel jobs started.

This program is particularly helpful if you want to schedule and monitor mass activities using theSchedule Manager or your own report.

1.1.48 Processing Returns

Use

Read Returns Data from Archive

Via transaction FPO9, (SAP menu: Payments -> Returns -> Returns Lot), you can display returns thathave already been archived. Note that when you are archiving, archived returns are no longer availablefor the determination of the number of returns an important value for determining the returns activities.

Zero Total Tax Items

If charges are posted for a return, and the charges have a tax code with a tax rate of 0.0%, the systemcreates zero total tax items and displays these in the returns document.

Automatic Creation of Returns Lots

At the time of creation, you can create the manual posting items Type of Posting = 3 directly.

Check for Changed Bank Details

You can check for a return whether the bank details of the partner have changed since the last paymentrun. If this is the case, you can either use an alternative returns reason, or you can define your ownactivities to be carried out by the return via event 0293.

______________________________________________________________SAP AG 49

SAP-System______________________________________________________________

Version Numbering and New Fields in the Returns History

The new activity fields and the version numbering have been included in the returns history; you candisplay both using the display variant.

Selection via Payment Form Number

When you are assigning payments, you can also use the payment form number as selection criterion.

New Returns Category "External Payment Collector"

If a confirmation of a payment receipt forwarded by a payment collector is incorrect, a return occurs. Youhave to process such returns in a separate account not the bank clearing account for bank returns. Youcan determine the G/L account required in the automatic account determination using the new returnscategory 05 (External Payment Collector).

Reversal of Returns with a Clarification Document

From Release 4.72, you can also reverse returns with a clarification document. During the reversal of thedocument (SAP menu: Document -> Reverse), a returns lot that has already been closed is reopenedand, if necessary, a new reconciliation key created, and you can then process the clarification case againin the returns lot. The creditworthiness of the business partner concerned is reset accordingly.

Save Display Variant for Returns Display

In the header of the returns lot you can save a user-dependent line layout variant for data entry.


You make the settings for the new returns category External Payment Collector in the ImplementationGuide for Contract Accounts Receivable and Payable under Business Transactions -> Returns ->Define Charges Accounts for Returns.

1.1.49 Inclusion of Schedule Managers in Contract Accounts Receivable andPayable

Use

From Release 4.72, you can schedule mass activities in Contract Accounts Receivable and Payable withthe program RFKK_MA_SCHEDULER - Schedule Mass Activities using the Schedule Manager (seeSAP menu: Periodic Processing -> Mass Processing Administration).

In addition, the following periodic programs have been changed over so that you can also schedule thesewith the Schedule Manager:

Technical Names Name

RFKKFIKEYCLOSE Automatic Closure of

Reconciliation Keys

RFKKABS1 Check Totals Tables

______________________________________________________________SAP AG 50

SAP-System______________________________________________________________

RFKKGL00 Transfer of FI-CA Totals Records to

General Ledger

RFKKCOPA00 Transfer of Account Assignment Data to

Profitability Analysis

RFKKPCDS Bill Payment Cards

RFKKBIB0 Document Transfer

RFKKZE00 Payment Lot Transfer

RFKKRL00 Returns Lot Transfer

RFKKCM00 Data Transfer for Manually Issued

Checks

RFKKCR00 Transfer of Cashed Checks

RFKKKA00 Transfer of Data from Account Statement to

Payment/Returns Lot

RFKKAV00 Transfer of Payment Advice Notes from

Sequential File

RFKKCOPM Read Collection Agency File

RFKKRD00 Post Revenue Distribution

1.1.50 Stop Future Payment (Denmark)

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can generate a file tosend to PBS to cancel a future (within two business days) direct debit payment for a business partner. Todo so, from the SAP Easy Access menu, choose Accounting > Financial Accounting > ContractAccounts Receivable and Payable > Payments > Payment Run -> Stop Future Payment (DK).

______________________________________________________________SAP AG 51

SAP-System______________________________________________________________

1.1.51 Tax Reporting in Contract Accounting (New)

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can prepare value-addedtax (VAT) reporting with the new program, Tax Reporting in Contract Accounting (RFKKTX00).


A new Business Add-In, FKK_TAX_REP_00, is available that enables you to modify the list layout tocover country-specific requirements. An implementation is delivered for Mexico,IMP_MX_TAX_REP_00.

Note, also, that a new function module is delivered for Mexico, FKK_MX_EVENT_0934, which youmust assign to event 934 in Customizing for Financial Accounting, under Contract AccountsReceivable and Payable -> Program Enhancements -> Define Customer-Specific Function Modules(assign under Installation-Specific Function Modules). Refer to the function module documentation formore information.

1.1.52 Credit Splitting

Use

From Release 4.72 of SAP for Insurance, you can create a clearing document for every open credit itemthat is to be disbursed to multiple alternative payment recipients, in the new VAZE mass activity(Distribution of Open Credit Items for Disbursement to Multiple Alternative Payment Recipients). Theclearing document contains a business partner item for every alternative payment recipient, with theappropriate partial amount that is to be paid out to the alternative payment recipient, and the alternativepayment recipient as an alternative partner.

Mass activity VAZE has to have been executed before the payment run.


As was previously the case, you can enter an alternative payment recipient for a contract account or acontract, or you can enter a list of alternative payment recipients, specifying the distribution rules andpartial amounts to be distributed, as a new function for the insurance object (contract).

Entering a credit document still takes place without taking the alternative payment recipient into account:If alternative partners are specified in this credit document, these values take priority over the alternativepayment recipients for the contract account or the contract.


In der IMG-Aktivität Aufteilungsart für Guthabensplitting definieren steuern Sie die Aufteilung des imGuthabenbeleg ausgewiesenen Betrags auf die verschiedenen Beträge, die an die abweichendenZahlungsempfänger ausgezahlt werden.

______________________________________________________________SAP AG 52

SAP-System______________________________________________________________

1.1.53 Write-Offs

Use

In the transaction Write-Off (FPO4), you can enter notes for a write-off document created. To do this, inthe menu choose Extras -> Notes -> Enter Notes.

1.1.54 Generic Withholding Tax Reporting (Enhanced)

Use

As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), Generic Withholding TaxReporting has been enhanced to enable you to select withholding tax data from FI-CA.

Under the group box Further Selections, you can select which application the system is to retrieve datafrom when you run the program, and specify other parameters relevant to FI-CA.


A new Business Add-In, FKK_WTAX_REP00, is available that enables you to enhance the report tocover country-specific requirements in the output. You can add parameters to the selection screen andmodify business partner and withholding tax data. An implementation is delivered for the United States,IMPUS_IDWT_1099MISC.

______________________________________________________________SAP AG 53

SAP-System______________________________________________________________