14 Reln Ehp7 Insurance En

7/27/2019 14 Reln Ehp7 Insurance En

http://slidepdf.com/reader/full/14-reln-ehp7-insurance-en 1/34

Release Notesfor

Insurance

SAP enhancement package 7 for SAP ERP 6.0



SAP® What's New? – Release Notes

Release Notes for Insurance SAP EhP 7 for SAP ERP 6.0 of 34

Copyright©Copyright 2012 SAP AG. All rights reserved.

Document classification: CUSTOMER

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be

changed without prior notice.No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,

Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and J ava are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany andother countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.





Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

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





INS Insurance .................................................................................................. 5

INS_FSCD_CI_5: Business Function SAP for Insurance:Collections/Disbursements 5 .................................................................................. 5

Creation and Processing of SEPA Direct Debits (New) ................................................... 6

SEPA Direct Debit Pre-Notifications (New) ................................................................... 10

Archiving (New) ............................................................................................................ 14

Extended Message Management (New) ....................................................................... 15

New Events (New) ........................................................................................................ 15

SAP NetWeaver ILM and Archiving in Contract Accounts Receivable and Payable (New).................................................................................................................................... 17

Use of Additional Account Assignments in a Live System (New) ................................... 20

Integration with Sales (New) ......................................................................................... 22

Outbound Interface for Postings to the Business Partner (Changed) ............................. 24

Special Periods ............................................................................................................ 25

Locks (R082 / R019)..................................................................................................... 26Contract in Histories (R057).......................................................................................... 27

Enhancements of Transaction FPE2M (R067) .............................................................. 28

Enhancements of Transaction FPLKA (R047) ............................................................... 28

Clarification Note for Incoming Payments Clarification (R061) ....................................... 28

Foreign Trade Declarations (New) ................................................................................ 29

INS_FSCM_CI_5: Business Function Insurance Claim Handling 5 (New) ............ 30

Long Texts in Claim Processing (Enhanced) ................................................................. 30

Benefit Types: Input Help (New) .................................................................................. 31

Reason for Changing Manual Reserve (New) ............................................................... 32

Authorizations for Coverage Referrals (New) ................................................................ 32

Multiple Insured Objects (Enhanced) ............................................................................ 33





INS Insurance

INS_FSCD_CI_5: Business Function SAP for

Insurance: Collections/Disbursements 5Use

As of SAP Enhancement Package 7 for SAP ERP 6.0, the Business Function SAP for Insurance: Collections/Disbursements 5 (I NS_FSCD_CI _5) is available. The followingnew or enhanced functions are available with this business function:

o Creation and Processing of SEPA Direct Debits

o SEPA Direct Debit Pre-Notifications

o Archiving

o Extended Message Management

o New Events

o SAP NetWeaver ILM and Arch iving in Contract Accounts Receivable and

Payable

o Use of Addit ional Account Assignments in a Live System

o Integration with Sales

o Outbound Interface for Postings to the Business Partner

o Preliminary Postings in Contract Accounts Receivable and Payable

(New)Special Periods

o Locks

o Contract in Histories

o Enhancements of Transaction FPE2M

o Enhancements of Transaction FPLKA

o Clarification Note for Incoming Payments Clarification

o Foreign Trade Declarations





o BAPI_CTRACCONTRACTACCOUNT_SREP

Mandates in Business Partners

As you could up to now, you can still create and display mandates for bank details onthe business partner on the Payment Transactions tab. This function is now alsopossible without selecting a specific set of bank details and then it shows all mandates

for the business partner (independent of the bank details). As result, it is possible, forexample, to display mandates for a business partner, even if there are not yet any bankdetails for this business partner. This can be the case, for example, if you have sentmandates without knowing the bank data, in order to find out what the bank data is.

Synchronization of Mandates with Address and Bank Data in Business Partner

In a mandate for a set of bank details, the IBAN of these bank details is stored. If thebank is changed, then it becomes necessary to adjust the bank data in the mandate,since otherwise the payment run cannot find a mandate for the new IBAN. You canconfigure this synchronization of bank data in Customizing so that the system does oneof the following when a bank is changed:

o Queries in dialog if it should synchronize the mandate

o Adjusts the mandate automatically (without query)

o Creates a new mandate automatically (without query)

o Does not synchronize the mandate

In addition, you can specify in Customizing that the system:

o Sends a query when you enter a new set of bank details with an IBAN to ask if SEPA mandates should also be created for this new bank

o Reverses existing SEPA mandates when bank details are deleted

o After a bank is changed or after a new bank is created for the automaticallychanged or created SEPA mandates, automatically creates a print request,which you can print later using the correspondence printing function (transactionFPCOPARA)

For printing using the correspondence printing function, SAP provides the newcorrespondence type 0047 with the example application formsFI_CA_MANDATE_SAMPLE_SF and FI_CA_MANDATE_SAMPLE_PDF.

If direct debit pre-notifications are active in your system, you can specify in Customizingthat when bank details are changed, the system makes you aware of open direct debitpre-notifications that can no longer be used because of the change.

Mandates in Requests

In a similar way as for business partner items, you can also enter a mandate already in

requests. When the receivable from the request is posted, the system copies themandate reference to the line item of the FI-CA document; the payment run takes themandate into account accordingly.

You can also change the mandate reference in the request.

The SEPA mandate was added to the following BAPIs for requests (object typeCA_REQUEST):

o BAPI_REQUEST_CR

o BAPI_REQUEST_CH

o BAPI_REQUEST_GD

Mandates in Payment Specifications





In payment specifications, in addition to the payer and the bank details to be used, youcan now also enter the SEPA mandate to be used. When you are assigning a SEPAmandate, the system displays a list of all suitable mandates for the bank details of thepayer. From this list, you can now also change mandates or create new mandates.

Mandates in Prepaid Accounts

In prepaid accounts, in addition to the bank details to be used, you can now also enterthe SEPA mandate to be used. When you are assigning a SEPA mandate, the systemdisplays a list of all suitable mandates for the bank details. From this list, you can nowalso change mandates or create new mandates.

The SEPA mandate was added to the following BAPIs for prepaid accounts (objecttype CA_PREPACC):

o BAPI_CTRACPREPAIDACCOUNT_CREA

o BAPI_CTRACPREPAIDACCOUNT_CHNG

o BAPI_CTRACPREPAIDACCOUNT_GETD

Mandates in Promises to Pay

In promises to pay, you can enter payment details for each installment for the collectionof the installment. In addition to the payer and the bank details, you can now also enterthe mandate reference to be used. In correspondence for the promise to pay, you canalso print the entered mandate reference.

Mandates in the Account Balance

By defining a suitable line layout variant (in Customizing for Contract AccountsReceivable and Payable under Basic Functions -> Account Balance Display ->

Define Line Layout Variants for Account Balance), you can show the mandatereference in the account balance at item level.

Mandates in Installment Plans

You can also enter the SEPA mandate to be used when you enter or change aninstallment plan. You can print the entered mandate reference in the installment planletter. In this way, the installment plan letter (with the naming of the mandate referenceto be used) can act as a SEPA direct debit pre-notification.

Mandates in SD Orders

You can also enter the SEPA mandate to be used when you enter or change an SDorder. The prerequisite is that you enter a SEPA payment method.

The payment run in Contract Accounts Receivable and Payable requires the bankdetails of the business partner, but this information is not stored in the SD order. Whenthe document is posted in Contract Accounts Receivable and Payable, the systemdetermines the bank details of the business partner from the IBAN of the mandate andstores the bank details in the FI-CA document.

Visibility of Mandate Fields

In Customizing, you can hide mandate fields at different levels.

Notes for Industry Components

Mandates in Insurance Objects (Insurance industry component)

In the same way as in the contract account, you can enter the SEPA mandate to beused in insurance objects. In this way, you can assign multiple insurance objects to oneSEPA mandate. In the SEPA mandate itself, you can only enter one insurance object.

During payment, the payment run evaluates all payment data (such as payment

method and bank details) in combination with the mandate.





The SEPA mandate was added to the BAPIs for creating, changing, and displayinginsurance objects.

Mandates in Payment Plan items (Insurance industry component)

You can also enter the SEPA mandate to be used in payment plan items. The systemadopts the mandate in the business partner items of the posted FI-CA document.

The SEPA mandate was added to the BAPI for creating a payment plan item.

Mandates in Contract Objects (Public Sector Contract Accounts Receivable and

Payable industry component)

In the same way as in the contract account, you can enter the SEPA mandate to beused in contract objects. In this way, you can assign multiple contract objects to oneSEPA mandate. In the SEPA mandate itself, you can only enter one contract object.

During payment, the payment run evaluates all payment data (such as paymentmethod and bank details) in combination with the mandate.

The SEPA mandate was added to the BAPIs for creating, changing, and displayingcontract objects.

Effects on Customizing

Synchronization of Address and Bank Data Changes

You make settings for the synchronization of address and bank data changes betweenbusiness partners and the SEPA mandate in Customizing for Contract AccountsReceivable and Payable under Business Transactions -> Payments ->

Incoming/Outgoing Payment Creation -> Management of SEPA Mandates ->

General Settings.

Visibility of Mandate Fields

You specify the levels at which mandate fields are visible in Customizing for Contract

Accounts Receivable and Payable underBusiness Transactions -> Payments ->

Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> Hide

Mandate Fields.





SEPA Direct Debit Pre-Notifications (New)

Use

The functions described below are available as of:

o SAP ERP 6.00, SP 24

o SAP enhancement package 2 for SAP ERP 6.0, SP 14




o SAP enhancement package 7 for SAP ERP 6.0

Definition of Direct Debit Pre-Notifications

The changeover of national collection procedures to SEPA Direct Debit requires, alongwith the use and management of SEPA mandates, that preceding information be

supplied to the business partner about the items to be collected while naming themandate to be used.

This SEPA direct debit pre-notification has to contain the date of collection, thecreditor ID of the company collecting the money, and the mandate reference that isused at collection.

You can create and send the direct debit pre-notification as a separate letter (newcorrespondence type). As another alternative, you can create this letter in processesthat cause invoices to be issued, and print the letter on the invoice. In any case, youhave to ensure that you only collect items for which pre-notification has been sent. Thatis, only items that you have mentioned in correspondence with the customer. You alsohave to ensure that you collect the items with the mandate entered in the pre-

notification.Necessity for Direct Debit Pre-Notification

In Contract Accounts Receivable and Payable, you specify at the mandate level if directdebit pre-notifications are generally possible. At the level of the paying company code,you can specify in which paying company codes direct debit pre-notifications can becreated.

You can also specify for each payment method if a direct debit pre-notification isnecessary (or possible) before collection can take place.

During posting, you can specify that pre-notification is necessary for certain items. Youcan also change this setting when you make manual changes to documents.

Pre-Notification Run

If you do not print pre-notifications during the creation of invoices, you can use aseparate pre-notification run to pre-notify customers of receivables. On the SAP EasyAccess screen, choose Periodic Processing -> For Contract Accounts -> Direct

Debit Pre-Notification (SEPA) (transaction FPYP).

The pre-notification run performs the following steps, just like the collection run(payment run) itself:

o Selection and grouping of items to be collected

o Selection of payment method and bank data

o Selection of the mandate to be used





o Creation of payment data (tables DPAYH, DPAYP) for pre-notification

The pre-notification run does not post any documents and does not create anypayment orders. Instead it creates a direct debit pre-notification and enters this pre-notification as the use in a SEPA mandate.

You can display the created direct debit pre-notification using transaction FPPRN3 (on

the SAP Easy Access screen under Payments -> Payment Run -> Display DirectDebit Pre-Notification).

This display shows the data of the direct debit pre-notification (business partner, date of collection, mandate to be used, bank data) as well as a list of the pre-notified items.

The system enters the created direct debit pre-notification on the Use tab in themandate, so that the direct debit pre-notifications that were already created based onthis mandate are also visible in the mandate. (The prerequisite for this is that youdefined the number of uses high enough in Customizing for Contract AccountsReceivable and Payable under Business Transactions -> Payments ->

Incoming/Outgoing Payment Creation -> Management of SEPA Mandates ->

General Settings.)

Correspondence for Direct Debit Pre-Notifications

For each direct debit pre-notification that is created from the pre-notification run, thesystem creates a correspondence entry with the new correspondence type 0048, whichyou can print using the correspondence print program (FPCOPARA). SAP providesexample application forms FI_CA_PRENOT_SAMPLE_SF andFI_CA_PRENOT_SAMPLE_PDF.

The display of this correspondence is integrated in the display of the direct debit pre-notification by means of a pushbutton.

Reversal of Direct Debit Pre-Notifications

It is not possible to reverse a document that contains a pre-notified business partner

item - you first have to reverse the pre-notification.Document changes or clearing of pre-notified items (except clearing by the subsequentcollection run) are not possible. During the processing of open items, pre-notified itemsare displayed with a special icon, and they cannot be activated or cleared.

You can reverse direct debit pre-notifications in transaction FPPRN8 on the SAP EasyAccess screen under Payments -> Payment Run -> Reverse Direct Debit Pre-

Notification or using a report for mass reversal on the SAP Easy Access screen underPayments -> Payment Run -> Mass Reversal of Direct Debit Pre-Notif ications

(transaction FPPRN8M).

When you reverse the pre-notification, the system removes the designation of the itemas pre-notified and the item is available again for document changes, clearing and

pre-notification.

For mass reversal, you can select using the run ID of the pre-notification run, so thatyou can remove all pre-notifications that were created in one run.

When a pre-notification is reversed, the system deletes any correspondence entries notyet printed.

Changing Direct Debit Pre-Notifications

You transmit direct debit pre-notifications to your business partners in writing; you haveto react to queries regarding individual pre-notified items.

If you reverse a direct debit pre-notification, you have to send pre-notification again forall items that were pre-notified. If a customer raises an objection about individual items

shortly before the collection date, you can remove these items from the direct debit pre-





notification (see transaction FPPRN2 on the SAP Easy Access screen underPayments -> Payment Run -> Change Direct Debit Pre-Noti fication). If items wereremoved by mistake from a direct debit pre-notification, you can also add them back tothe pre-notification. The system automatically adjusts the current amount of the pre-notification to reflect your changes.

Note that you can only remove items from a pre-notification if the items were posted inthe currency of the pre-notification.

It is not possible to add just any items to a pre-notification that has already beencreated. You can only add back items that were already contained in the pre-notification but that were removed. You can only add back items that were removed, if one of the following conditions is met:

o The items were not cleared in the meantime (that is, after they were removed).

o A payment request or another pre-notification was already created for the items.

The system indicates that items were removed by displaying the icon @11@ in the pre-notification display on the Items tab.

Immediately before saving a change, the system offers event FKK_SAMPLE_0657 ,which you can use to change certain data of the pre-notification to meet your individualneeds. At this event, you can also add additional checks.

After you save a change, the system offers event 0658, in which you can trigger furtheractions. For example, you can create correspondence for notifying the customer of thechange.

Overview of Direct Debit Pre-Notifications

You can use report RFKKPRNL (on the SAP Easy Access screen under Payments ->

Payment Run -> Overview of Direct Debit Pre-Notifi cations) to obtain an overviewof all direct debit pre-notifications.

Treatment of Direct Debit Pre-Notifications in Payment Run

On the initial screen of the payment run (on the General Selections tab), you specifythat direct debit pre-notifications are selected and processed. To do so, you set thePre-Notif ied Items indicator and enter the execution date for the pre-notification. Fortest purposes, you can also enter the pre-notification number itself as a selectioncriterion.

The payment run then pays the items based on the pre-notification, that is, it groups theselected items by pre-notification number and does not allow any additional sub-grouping. The payment run either pays a group of pre-notified items completely or notat all. If the amount of the pre-notified items is not the same as the collection amount,the system generates payment exception 52 Direct Debit Pre-Notification with

Different Amount and does not pay the item.

Partial payment of items from a pre-notification is not possible.

Particularly through the use of free selections (restriction of dataset of open items to beselected), it could be the case that not all items of a pre-notification are selected.

Therefore, you should not use free selections for pre-notified items in such a way thatyou exclude individual items from a pre-notification.

If at the time of collection, the IBAN of the bank details to be selected is not the sameas the IBAN in the pre-notification, the system generates payment exception 56 Direct

Debit Pre-Notification with Other Bank Account and does not pay the item.

If the execution date named in the pre-notification is exceeded by a greater number of days than is entered in the settings in Customizing for Contract Accounts Receivable

and Payable, the system generates payment exception 55 Debit Memo Notification





Used Too Late and does not pay the item.

Document Reversal and Clearing Reset

It is not possible to reverse a document that contains open and already pre-notifiedbusiness partner items. You first have to reverse the pre-notification. After that, you canreverse the receivables document.

When a pre-notified receivable is cleared (by the payment run), the data of the pre-notification is retained in the cleared receivable. If you then reverse this clearingdocument, the receivable again becomes open, and at the same time, the data of thepre-notification is removed from the receivable. The pre-notification that was used forthe payment keeps the status "Used" and it cannot be used again. You need to pre-notify the receivable again before you can collect it.

The behavior is similar for a clearing reset for the clearing document created by thepayment run. The data from the pre-notification is removed from the receivable when itis open again. You need to pre-notify the receivable again if you want to collect it.

Archiving of Direct Debit Pre-Notifications

You can archive direct debit pre-notifications if the creation date, the change date andthe execution date are at least 90 days in the past and the status of the pre-notificationis Reversed orUsed Completely. The archiving object is FI_MKKPRNH. In dialogmode, you can display already archived pre-notifications from the archive.

Specifications During Posting

Using event 0061, you can specify, dependent on any document data, such as themain and subtransaction of the items to be posted, if pre-notification is necessary forthese items. For more information, see the documentation for function moduleFKK_SAMPLE_0061.

Specification in Pre-Notification Run

At event 0600 you can specify, dependent on any fields of the business partner item,such as the main and subtransaction, if pre-notification is necessary for these items.For more information, see the documentation for function moduleFKK_SAMPLE_0600.

Checking and Changing Data of Pre-Notification Before Saving

You can add additional checks using event 0657. You can also use the event tochange some data of pre-notifications when they are created. Event 0657 is processedbefore the pre-notification is saved. For more information, see the documentation forfunction module FKK_SAMPLE_0657.

Performing Additional Actions After Changing a Pre-Notification

You can perform additional actions after saving a change to a pre-notification using

event 0658. For example, you can create correspondence to inform the customer of the change. For more information, see the documentation for function moduleFKK_SAMPLE_0658.


General Specifications

You specify that SEPA direct debit pre-notifications are created in Customizing forContract Accounts Receivable and Payable under Business Transactions ->

Payments -> Incoming/Outgoing Payment Creation -> Management of SEPA

Mandates -> Enter General Specifi cations.

In addition, you specify the number of days after the pre-notification date that the direct

debit is still allowed to take place. A direct debit is not allowed for a date earlier than the





pre-notified date. The system does not perform a direct debit for a collection date that ismore than the defined number of tolerance days after the pre-notification date. Instead,this results in a payment exception in the payment run. In such cases, you have toreverse the pre-notification and create a new one with a new collection date.

Specifications for Paying Company Code

You specify the paying company codes in which SEPA direct debit pre-notifications canbe created in Customizing for Contract Accounts Receivable and Payable underBusiness Transactions -> Payments -> Incoming/Outgoing Payment Creation -

>Define Specifications for Paying Company Code.

Specifications for Payment Method

You specify the payment methods for which SEPA direct debit pre-notifications can becreated or must be created in Customizing for Contract Accounts Receivable andPayable under Business Transactions -> Payments -> Incoming/Outgoing

Payment Creation -> Define Payment Methods.

If the creation of a direct debit pre-notification is required, the system does not collect areceivable, unless a suitable direct debit pre-notification was previously created.

If a direct debit pre-notification can be created, the system collects the receivable, evenif a suitable direct debit pre-notification was not previously created.

Number Range for Direct Debit Pre-Notifications

You define the number range for direct debit pre-notifications in Customizing forContract Accounts Receivable and Payable under Business Transactions ->

Payments -> Incoming/Outgoing Payment Creation -> Enter Number Ranges for

Direct Debit Pre-Notif ications (SEPA).

Archiving (New)

Use

As of SAP Enhancement Package 7 for SAP ERP 6.0, the following functions forarchiving in Contract Accounts Receivable and Payable are available:

Archiving of Payment Data from Payment Runs

Archiving object FI_MKKPAYH can be used for archiving payment data from paymentruns.

The prerequisites for archiving are described in the documentation of reportRFKPYARC01.

Archiving of Security Deposits

Archiving object FI_MKKSEC can be used for archiving security deposits.


Archiving of Payment Data from Payment Runs

Enter the residence time and activate the archiving information structure for paymentdata from payment runs in Customizing for Contract Accounts Receivable and Payableunder Business Transactions -> Payments -> Archiving.

Archiving of Security Deposits





Enter the residence times and activate the archiving information structure for securitydeposits in Customizing for Contract Accounts Receivable and Payable underBusiness Transactions -> Security Deposits -> Archiving .

Extended Message Management (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, you can enter your own namesfor solution processes in clarification cases.


Assign the name of the call definition of the solution process in Customizing forContract Accounts Receivable and Payable under Basic Functions -> Enhanced

Message Management -> Specifi cations fo r Generating Clarification Cases ->

Enter Texts for Solution Processes.

New Events (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, you can use the following newevents:

o 0174:Tax: Criteria for Tax Determination with Cumulation

o 0178: Taxes: Add to Data During Update to External System

o 0198: Contract: Determine Payment Data

o 0199: Filter Contracts by Contract Category

o 0294: More Field Changes in Mandate Due to Returns

o 0421: Master Agreement/Filter: Check Test Data for Assignment

o 0530: Master Agreement: Enrich Data; Influence Check Status

o 0553: Provider Contract: Normalization of IDs

o 0554: Provider Contract: Reading of IDs (Migration to ERP)

o 0560: Generation of Partner Consumption Items

o 0561: Filling of Additional Fields in Partner Consumption Items

o 0576: SEPA Mandates: Mandate Changes After Change of Bank

o 0578: SEPA Mandate: Checks Before Saving

o 0579: SEPA Mandate: Follow-On Activities After Saving

o 0581: SEPA Mandate: Authorization Checks

o 0582: SEPA Mandate: Forward Navigation





o 0657: SEPA Direct Debit Pre-Notification: Add to Data Before Saving

o 0658:SEPA Direct Debit Pre-Notification: Follow-On Activities After Change

o 0659: SEPA Pre-Notification: Generate from CI/Invoicing

o 0771: Correspondence: Print SEPA Mandate Request

o 0772: Correspondence: Generate SEPA Mandate Request

o 0776: Correspondence: Print SEPA Direct Debit Pre-Notification

o 0777: Correspondence: Generate SEPA Direct Debit Pre-Notification

o 0779: Correspondence: Follow-On Activities After Printing

o 0949: Set Account Assignments for Subsequent Postings

o 1123: Document: Mass Change - Initialization

o 1790: MassAct: Deletion of Table Entries

o 1791: MassAct: Deletion of Table Entries for Shift Parameters

o 1857: MassAct: Delete Outbound Interface Triggero 1858: MassAct: Outbound Interface Delete Triggers, Parameters

o 1892: MassAct: Adjustment Records for Partner Settlements

o 1893: MassAct: Adjustment Records for Partner Settlement (Shift)

o 1894: Determination of Adjustment Amount for Partner

o 1895: Determination of Adjustment Amount for Partner

o 1896: Subsequent Introduction of Account Assignments

o 1897: MassAct: SEPA Prenotification

o 1898: MassAct: SEPA Prenotification, Shift Parameters

o 1982: Foreign Trade Declaration: Data Export to Local File

o 2087: Interest: Distribute Items for Interest Calculation

o 5706: SAP CC: Business Relationship with Bus. Partner (B2B/B2C)

o 5710: Determine Logical Ports

o 6534: Requests: Propose Alternative Currency

o 6750: Mass Act: Interval Function Module for Mass Activities

o 8145: BIX: Parallel Archiving of Rated Consumption Items

o 8175: BIX: Analyze and Enrich Consumption Items

o 8182: BIX: Mass Activity: Rating

o 8183: BIX: Mass Activity: Move Rating Parameters

o 8187: Mass Activity: Partner Activation

o 8188: Mass Activity: Move Partner Activation Parameters

o 8189: BIX: Mass Activity: Perform Rerating

o 8190: BIX: Mass Activity: Move Rerating Parameters


You enter installation-specific function modules in Customizing for Contract Accounts

Receivable and Payable under Program Enhancements -> Define Customer-





Specifi c Function Modules.

SAP NetWeaver ILM and Archiving in Contract AccountsReceivable and Payable (New)

Use

Integration with SAP NetWeaver Information Lifecycle Management

As of SAP enhancement package 7 for SAP ERP 6.0, the integration of ContractAccounts Receivable and Payable (FI-CA) with SAP NetWeaver Information LifecycleManagement (SAP NetWeaver ILM) lets you manage archived data on the basis of

residence rules. By storing the archived data in specified retention periods, destructionof the data in accordance with legal requirements is possible.

The following archiving objects in Contract Accounts Receivable and Payable wereintegrated with SAP NetWeaver ILM:

Archiving object Descript ion Software

Component

FI_MKKCORR FI-CA Correspondence FI-CA

FI_MKKCREG FI-CA Check Management FI-CA

FI_MKKDOC FI-CA Document FI-CA

FI_MKKEXC FI-CA External Payment Information FI-CA

FI_MKKEXCJ FI-CA Cash J ournal (Inbound Services) FI-CA

FI_MKKINF FI-CA Information Container FI-CA

FI_MKKIP FI-CA Payment Specifications FI-CA

FI_MKKPAYL FI-CA Payment Lot FI-CA

FI_MKKPCRD FI-CA Payment Card Supplement FI-CA

FI_MKKPNBK FI-CA Prenotification FI-CA

FI_MKKPP FI-CA Promise to Pay FI-CA

FI_MKKPPAC FI-CA Prepaid Accounts FI-CA

FI_MKKCAMA FI-CA Master Agreement FI-CA

FI_MKKCAVT FI-CA Provider Contract FI-CA

FI_MKKREHI FI-CA Returns History FI-CA

FI_MKKRET FI-CA Returns Lot FI-CA

FI_MKKPAYH FI-CA Payment Data from Payment Runs FI-

CA





FI_MKKSEC FI-CA Security Deposit FI-CA

FKK_GENREP FI-CA Generic Tax Reporting FI-CA

FKK_GENREV FI-CA Generic Tax Reporting - Revenue FI-CA

FI_MKKPRNH FI-CA: Direct Debit Pre-Notifications (SEPA) FI-

CA

FI_MKKMDOC FI-CA: Sample Documents FI-CA

FI_MKKUSTX FI-CA: Telecommunications Tax FI-CA

FI_MKKEXTD FI-CA: Official Document FI-CA

FI_MKKGENS FI-CA: Generic Tax Reporting - Additional Table FI-

CA

In addition, the archiving object CA_BUPA (business partner) is integrated withNetWeaver ILM.

Note for the industry solution component Public Sector Contract Accounts

Receivable and Payable (IS-PS-CA)

Archiving object FMCA_FB (PSCD form bundle) was integrated with SAP NetWeaverILM.

Note for the industry solution component Insurance Contract Accounts

Receivable and Payable (FS-CD)

The following archiving objects were integrated with SAP NetWeaver ILM:

Archiving object Descript ion Software

Component

VVKK_ITAG VVKK: Archiving Agency Collections

INSURANCE

VVKK_SCHED VVKK Bill Scheduling INSURANCE

VVKK_BRCOL Broker Report INSURANCE

VVKK_COINH Coinsurance Reporting INSURANCE

VVKK_FAKTB IS-CD Posting Data INSURANCE

VVKK_INTEG Insurance Integration INSURANCE

VVKK_INVCH Invoicing History INSURANCE

VVKK_REPCL Clarification Worklist for Money Laundering

Regulations INSURANCE

VVKK_SAICH Balance Interest Calculation History

INSURANCE

VVKK_TAX Tax Reporting for Italy INSURANCE

Archiving objects integrated with SAP NetWeaver ILM offer up to three additional

actions:





o Archiving (archiving of data after successful archivability check)

o Snapshot (archiving of data without checks)

o Destruction of data (destruction of archived data in accordance with the rulesfrom the Information Retention Manager )

Caution

BDT archiving objects integrated with SAP NetWeaver ILM only offer the ILM actions Arch iv ing and Destruction of Data.

In transaction ILMARA, you enter the audit areas to which you can assign ILM objectsfor a policy category (for FI-CA: retention rule only); in transaction IRMPOL, you enterthe ILM policies by specifying the policy category, object category, audit area and ILMobject.

In transaction ILMSIM, you can simulate the policies that you entered in transactionIRMPOL.

Deletion of Other Objects

As of SAP enhancement package 7 for SAP ERP 6.0, you can reduce the load on yourdatabase by deleting data from tables that you do not archive and no longer needonline.

Along with the deletion objects of the standard system, you can implement your owndeletion objects as follows. To do so, you define a function module that deletes thedata from the appropriate tables (see example function module FKK_DELOBJ _0000)and enter the deletion object in the customer namespace in Customizing.


Integration with Information Lifecycle Management (ILM)

You make the system settings for retention regulations and retention rules inCustomizing for Contract Accounts Receivable and Payable under Data Deletion in thefollowing activities:

o Define Retention Regulations

o Assign Retention Regulations

Delete Other Objects

You find the deletion objects in Customizing Contract Accounts Receivable andPayable under Data Deletion -> Enter Deletion Objects.

You can enter your own deletion objects also in Customizing Contract AccountsReceivable and Payable under Data Deletion -> Enter Deletion Objects. Assign the

appropriate deletion module to the deletion object here and specify a residence time.





Use of Additional Account Assignments in a Live System(New)

Use

You can enter the following account assignments in business partner items in theposting document in Contract Accounts Receivable and Payable:

o Business area

o Segment

o Profit center

If you have not used one of these account assignments up to now, but want to use it inthe future, you can only do so in new documents. You cannot change any of theseaccount assignments in documents posted already because this leads to errors whenreconciling with the general ledger. As a result, the account assignments are alsomissing in follow-on postings that arise due to clearing or other follow-on processes

(such as cash discounts, payment surcharges, interest, exchange rate differences,down payments on statistical request) for these documents. For key date evaluations of open items, balances without account assignment remain until the last items withoutaccount assignment are cleared.

To eliminate these effects, as of SAP enhancement package 7 for SAP ERP 6.0, youcan use a prepared enhancement to add a second set of account assignment fields inyour business partner items. These include the term subsequent, for example, Profit

Center Assigned Subsequently to an Account. If the original account assignmentsare not set, after implementing the enhancement, fill the additional fields with theappropriate account assignments using a mass activity (on the SAP Easy Accessscreen under Changeovers in Live System -> Set Subsequent Account

Assignments in Business Partner Items). Derivation of the appropriate account

assignment occurs at event 0949, which you must define in accordance with yourrequirements.

You can use these subsequently set account assignments as follows:

o Follow-on postings for items with subsequent account assignment receive theaccount assignments in exactly the same way as if the original fields in thebusiness partner item had had these account assignments. The system takesfollow-on postings into account for:

- Clearing (cash discounts, payment surcharges, exchange rate differences,down payments on request, charges on request)

- Write-off (expense or revenue)

- Interest calculation The goal is for all postings to have account assignment to the income statement,and not to allow any new, open business partner items to be created withoutaccount assignment. Therefore, the system always takes into account allsubsequently set account assignments, without taking a key-date-dependentview, as with reports on open items.

o The clearing posting on the receivables account or payables account is notaffected by the subsequent account assignments, since the clearing of an itemalways has to be posted with the same account assignments as were used whenthe item was created.

o Valuation gains and valuation losses resulting from foreign currency valuationalso receive their account assignments as if the account assignments were





already entered in the original fields in the business partner items.

o You can also take the subsequent account assignments into account for keydate evaluations of open items (reclassification, aging, foreign currencyvaluation). For each company code, enter the key date, starting from which thisshould take place, in Customizing for Contract Accounts Receivable and Payable

under Closing Operations -> Define Settings for Subsequent Account Assignments.

The system then displays the balances and all required adjustment postings forreceivables and payables as if the original account assignment fields were set. Sincethe general ledger still records the balances without account assignment, the systemproposes additional adjustment postings, that you can post from the SAP Easy Accessscreen under Periodic Processing -> Closing Preparation -> Adjustments for

Subsequent Account Assignment. Using these adjustments, the system reduces thebalances without account assignment using the adjustment accounts for receivablesand payables, and builds up balances with account assignment. As a result of theadjustment, the receivables and payables for postings with subsequent accountassignment appear in the balance sheet as if they were originally entered with these

account assignments.Note

The entries in the Customizing activity Define Settings for Subsequent Account

Assignments then also cause the enrichment of account assignments for key dateevaluations, if no subsequent account assignments were set, but an enrichment wasmade at event 0945 during the general ledger transfer. All adjustment postings forreceivables and payables then inherit the account assignments that the system addedduring the general ledger transfer. For more information, see the documentation forevent 0945.

Proceed as follows to add subsequent account assignments:

1. Preparation

- Execute the prepared enhancement.

- Define the events 0944, 0945 and 0949 to meet your requirements.

2. Introduction of the Account Assignment

- Set the subsequent account assignments from the SAP Easy Accessscreen under Changeovers in Live System -> Set Subsequent Account

Assignments in Business Partner Items.

- In Customizing under Closing Operations -> Activate Subsequent

Account Assignments for Closing Operations, enter the date for allaffected company codes starting from which you want an enrichment totake place during the general ledger transfer and at the same time the

subsequent account assignments should be taken into account for keydate reports.

- Migrate the balances of the reconciliation accounts to Contract AccountsReceivable and Payable. In doing so, set a dummy account assignmentfor the desired account assignment field (such as profit center).

3. Closing Operations

- For the evaluation of open items for a key date, enter a name for theexport of the transfer data for subsequent account assignments.

- In addition to other adjustment postings (reclassification, aging), also enterthe adjustment posting for the subsequent account assignments (on the

SAP Easy Access screen under Periodi c Processing -> Closing





Preparation -> Adjustments for Subsequent Account Assignment).


To add the initial account assignments to business partner items of the document, inCustomizing for Contract Accounts Receivable and Payable, choose Program

Enhancements -> Prepared Enhancements -> Add Fields for Subsequent

Account Assignments.

You activate adjustment postings for individual company codes in the activity Define

Settings for Subsequent Account Assignments in Customizing for ContractAccounts Receivable and Payable, or under Integration -> General Ledger

Accounting orClosing Operations.

Integration with Sales (New)Use

Previously, you could only use the interface between Sales and Distribution (SD) andContract Accounts Receivable and Payable (FI-CA) in an integrated scenario in oneclient.

As of SAP Enhancement Package 7 for SAP ERP 6.0, you can also integrate ContractAccounts Receivable and Payable and Sales and Distribution even if you run bothcomponents in distributed systems. To do this, the following prerequisites must befulfilled:

o The customer must be defined with an identical key in both systems - as a

customer in the SD system and as a business partner with a contract account inthe FI-CA system.

o Customizing for company codes, controlling areas, operating concerns, andbilling types must match in the FI-CA and SD systems.

o If you use multiple SD systems, you must use different number ranges for SDinvoicing documents.

In a distributed scenario, create the SD order and SD billing document in the SDsystem. However, post the accounting document in Contract Accounts Receivable andPayable in the FI-CA system.

On the basis of the customer account group, the SD system decides whether to sendan SD billing document to the FI-CA system. The decision is made by means of

message condition records during billing. The information is transferred by IDoc toContract Accounts Receivable and Payable.

Depending on the billing type, Contract Accounts Receivable and Payable posts:

o Directly

o After invoicing in Contract Accounts Receivable and Payable

o Sample documents

If you reverse an SD billing document, the SD system also sends an IDoc to the FI-CAsystem.

If you have integrated Contract Accounts Receivable and Payable with Profitability

Analysis (CO-PA), the SD system also sends the corresponding profitability segments





to the FI-CA system.

Note the following:

o From the SD billing document, a profitability segment is determined from theavailable characteristics combination. This profitability segment is unknown inthe FI-CA system and must be converted there. To do this, you can also use an

alternative characteristics combination with less granularity.

o When you post a document directly in Contract Accounts Receivable andPayable, the SD system sends the corresponding profitability segment by IDoc tothe FI-CA system and converts it to a local profitability segment there.

o When you post by invoice trigger, the FI-CA system does not determines theconverted profitability segment until invoicing in Contract Accounts Receivableand Payable.

o When you post using a sample document, Contract Accounts Receivable andPayable determines the converted profitability segment when the sampledocument is posted. In each case, the CO-PA document not posted until it istransferred to Profitability Analysis (CO-PA).

In the document flow of the SD billing document, you can see the current status. If theIDoc in Contract Accounts Receivable and Payable was not yet processed, the statusof the outbound IDoc is displayed. All documents of Contract Accounts Receivable andPayable can be displayed directly from the document flow.

In document header messages, you can check the status of the outbound IDoc. In theevent of errors, you can display error messages and trigger the distribution to ContractAccounts Receivable and Payable again.

You can monitor the distribution in the SAP Menu under: Periodic Processing ->

Reconci liation of Documents with Source Data -> Reconci liation wi th SD Billing

Documents. The program assigns FI-CA documents to SD billing documents and findsinconsistencies.

To find errors in IDoc inbound processing, you can use transaction WE02.


You make system settings for SD integration for distributed systems in Customizing forSales and Distribution in the system in which Sales and Distribution is running, and inCustomizing for Contract Accounts Receivable and Payable in the system in whichContract Accounts Receivable and Payable is running:

o Sales and DistributionDefine the account groups that are relevant for integration with ContractAccounts Receivable and Payable under: Basic Functions -> Integration with

Contract Accounts Receivable and Payable -> Specify Posting of Debtor

Groups to Contract Accounts Receivable and Payable.

o Contract Accounts Receivable and PayableDefine and activate system connections under: Integration -> Sales and

Distribution -> Define Logical Systems for Distributed SD Systems.





Outbound Interface for Postings to the Business Partner (Changed)

Use

Using the outbound interface, you transfer open and cleared items, as well as well aspayments of a business partner, to an external system using an XI interface (forinstance, for invoice creation).

As of SAP enhancement package 7 for SAP ERP 6.0, the data storage for the triggerentries has changed in the outbound interface for postings to the business partner.

Tables DFKK_TRIGX_OP, DFKK_TRIGX_CL, DFKK_TRIGX_PAY andDFKK_TRIGX_RCL replace tables DFKK_TRIGGER_OP, DFKK_TRIGGER_CL,DFKK_TRIGGER_PAY and DFKK_TRIGGER_RCL.

To prevent problems during parallel updates, the system writes a separate trigger entryfor each triggering document. The mass run for the transfer (transaction FPOITR)considers all business partners, for which there is at least one trigger entry in table

DFKK_TRIGX_OP with status 1 (Preselected for Transfer ). Entries in the old triggertable DFKK_TRIGGER_OP that were not yet transferred are automatically moved tothe new table DFKK_TRIGX_OP. The mass activity works primarily on the new triggertable DFKK_TRIGX_OP, however, it still also considers data in the old trigger tablesDFKK_TRIGGER_CL, DFKK_TRIGGER_PAY and DFKK_TRIGGER_RCL that wasnot yet processed.

Unlike the previous procedure, the system no longer automatically deletes triggerentries 180 days after the transfer. The transfer is now separate from the deletion of triggers. You delete trigger entries using a mass run. On the SAP Easy Access screen,choose Periodic Processing -> Delete Data -> Triggers for Outbound Interface.





Special Periods

Use

As of enhancement package 7 for SAP 6.0, you can enter the special period in

requests and FI-CA documents that should be posted later during the transfer to thegeneral ledger.

If you have the necessary authorization (activity 140 for authorization objectF_KK_SOND), you can enter the special period you want at document header level inrequests and FI-CA documents.

Since FI-CA documents can post across company codes, it can be the case that therequested special period (from the document header) is not open in all posted companycodes for the document. A check for this at item level therefore only results in awarning message. The system issues an error message only if the special period is notopen in any document item.

For postings from other transactions, such as reports or mass activities, you define a

default special period, dependent on the posting date, that the system thenautomatically enters in the document header. In this way, for example, you can preventthe posting period of the clearing document for automatic clearing (FP06 or FPMA)from being earlier than the posting period of the document to be cleared.

This default special period is also proposed as the default special period for manualpostings (FPE1/FKKORD1). If you have the necessary authorization, you can overwritethe default special period manually; or you can delete it, if you want to post without aspecial period. Following a change to the proposed posting date, the systemautomatically proposes the new default special period that results from the change (if you did not manually change the special period at the same the posting date waschanged). In this way, you can check if the entered posting date and special period arecorrect.

During the transfer to the general ledger, it can be the case that the special periodstored in the document header or totals record is not open in all company codes. Forthese cases, dependent on the company code, you can enter an alternative specialperiod in Customizing for the transfer to the general ledger. This setting is onlynecessary for cross-company-code postings in company codes with different fiscal yearvariants.

If none of the defined special periods is still open during the transfer to the generalledger, you can enter an alternative special period for the transfer to the general ledgerthat is dependent on the company code and the requested special period.

However, if none of the possible special periods is open or you do not want to openone, you can still (as before) transfer the totals record by entering a different posting

date.

For automatic postings (transactions for which it is not possible to enter a specialperiod), you can also use event 0062 to change the default special period that wasdetermined from the Current Settings, based on any document data (such as thedocument origin from the document header).

When you display a document (FPE2/FPE3), you can display the special period fromthe document header at the level of the line items also. To do so, define an appropriateline layout variant, taking into account that a new special period might be determinedfor each company code (using table TFK001W). That means that you display thespecial period, in which the transfer to the general ledger is to be posted.

You activate the use of special periods in Customizing.





You enter default special periods for the posting date on the SAP Easy Access screenunder Setti ngs -> Current Settings -> Special Periods -> Specify Default Special

Periods.

You specify alternative special periods for each company code for the transfer to thegeneral ledger on the SAP Easy Access screen under: Settings -> Current Settings -

> Special Periods -> Define New Determination fo r Each Company Code. You specify the alternative special period to be used for the transfer to the generalledger if the special period is closed, on the SAP Easy Access screen under: Settings -

> Current Settings -> Special Periods -> Define Dif ferent Special Period for

Transfer .


Activate the use of special periods by setting the Special Period indicator inCustomizing for Contract Accounts Receivable and Payable under Basic Functions ->

Postings and Documents -> Basic Settings -> Maintain Central Posting Settings.

Locks (R082 / R019)

Use

As of enhancement package 7 for SAP ERP 6.0, you can create information in acomment on processing locks (such as the reason for setting the lock) and therebymake the issue easier to process later.

You create the comment for the lock when you create the lock. If you change a lock,you can change the comment. The system logs changes in the history.

When evaluating locks in the SAP Menu under: Periodic Processing -> for Contract

Accounts -> Evaluation of Processing Locks, you can use the field to make aselection and make comments.


Activate the comment field using a prepared enhancement in Customizing for ContractAccounts Receivable and Payable under Program Enhancements -> Prepared

Enhancements -> Add Comment Field to Lock.





Contract in Histories (R057)

Use

As of SAP enhancement package 7 for SAP ERP 6.00, you can also select by contract

in various evaluations and histories.Write-Off History

Using a prepared enhancement (report RFKK_ENH_VTREF), you can add contractfields to the table of the write-off history. If the written-off item was posted to a contract,the system saves new entries in the write-off history with this contract data.

The initial screen for selecting the returns history now offers selection by contract.In the SAP Menu, under: Changeovers in Live System -> Set Contract in Write-Off

History, you can enter the contract data history in existing entries and so enableselection by contract for older entries too.

Collection Items

When selecting collection items, the contract is offered as a new selection field.

Payment Search

The search for user-initiated payments (transaction FP31) now offers selection bybusiness partner, contrafct account, and contract. You can choose whether theseselections apply to the the payment header data (who is paying) or also to the paymentitem data (whose items are paid).

Returns History

The returns history now offers selection by contract.

Receivables Adjustments and Doubtful Entries

You can use a prepared enhancement (report RFKK_ENH_VTREF) to include contract

fields in the tables for receivables adjustments. If the line item was posted to a contract,the system saves new entries for receivables adjustment with this contract data.

The transaction for transfer postings (FPRV) now offers selection by contract, as doesthe evaluation report for displaying adjusted receivables (FPRA).

In the SAP Menu, under: Changeovers in L ive System -> Set Contract in Adjusted

Receivables, you can enter the contract data in existing entries in the tables foradjusted receivables and so enable selection by contract for older entries too.


You activate selection by contract for the write-off history and receivable adjustmentsby using a prepared enhancement in Customizing for Contract Accounts Receivable

and Payable under: Program Enhancements -> Prepared Enhancements -> AddContract to Write-Off History and Receivable Adjustment.





Enhancements of Transaction FPE2M (R067)

Use

As of SAP Enhancement Package 7 for SAP ERP 6.00, when using the mass change

function for documents, you can enter new values for the document items to bechanged in a new, single-column table. This table is displayed above the table of document items. Both tables have the same layout. The columns that are ready forinput in the table of document items are also ready in the table in which you enter thenew values.

In the new table, you can also select fields whose values you want to delete in selectedrows of the document item table. To do so, you select the corresponding columns in thenew table and initialize the field. During the transfer of new (non-initial) values, thevalues are deleted when you choose the Copy New Values pushbutton.


In the Mass Document Change transaction, to offer the option to enter new values in

a single-row table with the layout of the table of document items, select the EnhancedMass Change checkbox in Customizing for Contract Accounts Receivable andPayable under Basic Functions -> Postings and Documents -> Basic Settings ->

Maintain Central Settings for Posting.

Enhancements of Transaction FPLKA (R047)

Use

As of SAP Enhancement Package 7 for SAP ERP 6.0, you can use the Only Locks for

Open Items checkbox in Evaluate Processing Locks (transaction FPLKA). This

causes the program not to select and issue locks for cleared documents.Note that determination of the clearing status of line items can have a negative effecton program runtime.

Clarif ication Note for Incoming Payments Clarification (R061)

Use

As of SAP Enhancement Package 7 for SAP ERP 6.0, during clarification of incomingpayments from payment lots, a symbol in the new column Clarif. Note Available

indicates whether a clarification note was created for the given clarification case. The

tooltip for the symbol displays the first line of the clarification note.

In the details of a clarification case, the same symbol on the Clarification Note tabalso indicates a clarification note is available.

As an alternative or in addition to the above, you can have the system show a textcolumn Clarification Note (1st Line) in the ALV list. The column then contains the firstline of the clarification note. You can use this column to sort the list, for example.

To have the list of clarification cases indicate when there is a clarification note, in thedetail display of the clarification case in the SAP Menu under: Settings -> User

Settings, set the corresponding indicator in the Settings for Clarification Processing

dialog box.





Foreign Trade Declarations (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, you can, as part of creating

foreign trade declarations, format the reporting data in accordance with the regulationsof your country, and store the data in a local file that you can transfer to the responsibleauthority.

You can format the reporting data in the new event 1982 in the format required by theresponsible authority. In the transaction for displaying the reporting data (on the SAPEasy Access screen under Periodic Processing -> Data for Externals -> Tax

Author it ies -> Display Transacti ons for German Foreign Trade Declarati ons), youcan enter a file path and a prefix that the program uses to create the file name.

For Germany, we provide function module FKK_EVENT_1982_Z4_CSV for exportingthe reporting data for form Z4 in CSV format. You enter this function module at event1982 as an installation-specific module.





INS_FSCM_CI_5: Business Function Insurance ClaimHandling 5 (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance(I NSURANCE 617), the business function Insurance Claim Handling 5

(I NS_FSCM_CI _5) is available. The following new or enhanced functions are available

with this business function:

o Long texts in claim processing

o Benefit types: Input help

o Pictures for damaged vehicle

o Reason for changing manual reserve

o Authorizations for coverage referrals

o Multiple insured objects

o Role-based performer: Assignment for specific period

Long Texts in Claim Processing (Enhanced)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance(I NSURANCE 617, business function Insurance Claim Handling 5 (I NS_FSCM_CI _5),

the following new functions are available with long texts when processing claims.

o Permitted processing typeAs with notes, you can configure the permitted processing type of all long texts inclaim processing.

You can make the following settings in Customizing:

- User can make any changes to an existing long text

- User can only extend an existing long text (and not change the existinglong text)

For processing of claims, make this setting dependent on the line of business.

For processing of claim bundles, make this setting dependent on the claimbundle type.

o Display of the long text in a dialog box You can view every long text in a dialog box, meaning that you are able to seethe full long text.Proceed as follows:

a) Place the cursor on the long text.

b) In the context menu, choose Display Text in Dialog Box.


Perform Customizing activity Set Permitted Processing Type for Notes and Long Texts.





Benefit Types: Input Help (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension

Insurance(I NSURANCE 617), Business Function Insurance Claim Handling 5(I NS_FSCM_CI _5), you can use the new Business Add-In (BAdI)BADI _ I CL_BENTYPE_F4 to restrict the values in the input help for benefit types,

depending on the context (for example, for the coverage or incident type). The inputhelp then contains only those values that are really relevant, making things clearer forthe claim handler.

The input help defined with the new BAdI is much more accurate and far more context-sensitive than the input help defined by means of assignment to the benefit type treeand internal claim type.


You can find the new BAdI in Customizing for SAP Insurance under Claims

Management -> Claim -> Business Settings -> Claim Items -> Benefit Types -> BAdI:Input Help for Benefit Types.

Pictures for Damaged Vehicle (Enhanced)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance

(I NSURANCE 617), Business Function Insurance Claim Handling 5(I NS_FSCM_CI _5), the following enhancements have been made to the display of the

damaged vehicle in picture format:

o To display the damaged vehicle, you can now use up to 20 pictures. Previously,only six pictures per vehicle were available.

This means that you can document the damaged parts of the vehicle in greaterdetail.

o SAP now also provides new pictures that represent the vehicle more accurately(see below under "Effects on Existing Data").

o You can now delete existing pictures.

o You can now copy already uploaded pictures from another client to your own.

Effects on Existing Data

Report ICL_PICTURE_UPLOAD

Report I CL_PI CTURE_UPLOADhas been enhanced to include the functions mentioned

above.

Pictures Delivered

SAP now delivers the following pictures:





o 20 pictures for the undamaged state of the vehicle: They have the following naming convention: I CL_CAR_ <sequential numbers 01-

20>

o 20 pictures for display of the damage: They have the following naming convention: I CL_CAR_ <sequential numbers 01-

20> _DAM

Effects on System Administration

When you upload the pictures delivered with Customizing for the first time (see "Effectson Existing Data"), the system automatically saves the pictures in client 000. Thismeans that you then have to copy the pictures to the client you need.


To call report I CL_PI CTURE_UPLOAD, execute the same Customizing activity Upload

and Save Picture Files under Claims Management -> Claim -> Business Settings ->

Damaged and Insured Objects/Diagnoses -> Damaged and Insured Objects/Injured

Persons.

Reason for Changing Manual Reserve (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance

(I NSURANCE 617, business function Insurance Claim Handling 5 (I NS_FSCM_CI _5),

you can restrict the input help for the reasons for changing reserves manually.

For this purpose, the Customizing activity Enhance Reasons for Changing Reserves

contains the new checkbox Manual Reason. If you change a reserve manually in theapplication, the input help displayed by the system for the Change Reason fieldcontains only those reasons where the Manual Reason checkbox has been selected.


Perform Customizing activity Enhance Reasons for Changing Reserves.

Authorizations for Coverage Referrals (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance(I NSURANCE 617, business function Insurance Claim Handling 5 (I NS_FSCM_CI _5),

you can assign the following authorizations for editing coverage referrals:

o Overruling of coverage referrals You can use the new authorization object I _I CL_REF to control whether a user

can overrule a coverage referral when processing a claim.

o Deletion of coverage referrals created manually





You can use the existing authorization object I _I CL_SUBX to control whether a

user is permitted to delete a manually created coverage referral when processinga claim and thereby change the compensability.

o Change compensability without specifying an overruling reason You can use the authorization object I _I CL_SUBX to control whether a user is

permitted to change the compensability when processing a claim withoutspecifying an overruling reason.

Multiple Insured Objects (Enhanced)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance(I NSURANCE 617), Business Function Insurance Claim Handling 5

(I NS_FSCM_CI _5), the following new functions are available for mapping multiple

insured objects in a claim:

o You can now map different coverages for each insured object. The insuredobject is now assigned to a subclaim.For more information, see SAP Library for SAP Claims Management on SAPHelp Portal at http://help.sap.com/insurance-cm under Claims Management ->

Claim -> Cross-Line of Business Concepts in Claim Processing -> Policy

Snapshot -> Insured Objects/Insured Persons.

o Even if the same coverage is assigned to multiple insured objects, different limits

and deductibles are possible for each coverage.o In the policy snapshot you can now assign a liability coverage for each insured

object.


To be able to use these new functions, you must select the Mult.Insd Obj. (MultipleInsured Objects) checkbox in Customizing activity Configure Policy Products at thelevel of Version of Policy Product (Customizing path: Claims Management -> Claim ->

Product Configuration -> Configure Policy Products).




Role-Based Performer: Assignment for Specific Period (New)

Use

As of SAP enhancement package 7 for SAP ERP 6.0, Industry Extension Insurance(I NSURANCE 617), Business Function Insurance Claim Handling 5

(I NS_FSCM_CI _5), automatic performer assignment via Organizational Managementhas been enhanced: You can now assign a performer for a specific period. You canenter a period on the following levels:

o Assignment strategy You can specify a period depending on the assignment strategy.Example: You assign a performer for the period J anuary 1 through May 31 usingthe Round Robin assignment strategy of the organizational unit, and for theperiod J une 1 through August 31 you use theWorkload Balancing assignmentstrategy, and for the period September 1 through December 31 you use theRound Robin assignment strategy again.

o Availability

You can specify the availability of a performer for a specific period.Example: Performer A is on vacation from August 1 through August 23. For thisperiod you can enter the availability as being 0 %.

At each of the levels specified above, you can navigate between the individual periods.

14 Reln Ehp7 Insurance En

Documents

Transcript of 14 Reln Ehp7 Insurance En