March 2004

Release Notes

SAP AG

SAP Telecommunications - Receivables Management -

Contract Accounting(SAP IS-T/RM-CA)

as at 4.72

______________________________________________________________

CopyrightCopyright(c) 2004 SAP AG. All rights reserved.Neither this document nor any part of it may be copied or reproduced in any form or by anymeans or translated into another language, without the prior consent of SAP AG. Theinformation contained in this document is subject to change without notice.SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registeredtrademarks of their respective companies.

1 New Entries in the SAP Menu for Telecommunications Release 4.72 12 IS-T-CA Contract Accounts Receivable and Payable 22.1 Account Balance Display 22.2 Archiving for Tax Reporting Argentina (Changed) 32.3 Archiving 32.4 Authorization Objects 42.5 BAPIs in Contract Accounts Receivable and Payable 52.6 Boletos 62.7 Business Information Warehouse 72.8 Cash Desk 82.9 Cash Journal 92.10 Closing Operations 102.11 Submission of Receivables to Collection Agencies 102.12 Collective Bills 112.13 Company Codes 122.14 Creating Correspondence 142.15 Connection of SAP Dispute Management to Contract Accounts Receivable and Payable 142.16 Dunning 182.17 Enhanced Message Management 192.18 New and Changed Events 202.19 Conversion of Finnish Bank Statement to MultiCash (Enhanced) 232.20 Foreign Currency Valuation 232.21 IDoc Interfaces for Communication with External Billing Systems 242.22 Changed IMG Activities in Contract Account Payable 252.23 New IMG Activities in Contract Accounts Receivable Payable 262.24 Information System 282.25 Deferral and Installment Plan 292.26 Integration 302.27 Interest Calculation 322.28 Processing Locks 332.29 Mass Runs 332.30 Master Data 332.31 Evaluating Open Items 352.32 Processing of Incoming and Outgoing Payments 35

______________________________________________________________

SAP AG iii

SAP IS-T 4.72 Content SAP AG______________________________________________________________

2.33 Payment Transactions 362.34 Collections in the Print Workbench 382.35 Postings and Documents 392.36 Prenotifications 442.37 New Reports 442.38 Requests 452.39 Processing of Returns 462.40 Integration of Schedule Manager in Contract Accounts Receivable and Payable 472.41 Stop Future Payment (Denmark) 482.42 Tax Reporting in Contract Accounting (New) 482.43 Write-Offs 492.44 Generic Withholding Tax Reporting (Enhanced) 49

______________________________________________________________

SAP AG iv

SAP IS-T 4.72 Contents SAP AG______________________________________________________________

1 New Entries in the SAP Menu for Telecommunications withRelease 4.72

UseThe following transactions have been added to the SAP menu in the areas listed:

o Business master data:

- Business partner:-> Maintain Bank Data (FPP4)-> Enter Registration ID (DK) (FPDKCPR)

o Contract A/R + A/P:

- Account:-> Other Information -> Dispute Cases for Account Balance (FPDM00)

- Payments:-> Cash Account -> Cash Journal Evaluation (FPCJR)- Payment Run -> Stop Future Payment (DK)

-> External payment collectors -> Clarification of Transferred Payments (FPCVS)- Standing request:

-> Approve Request (FKKORDA)- Periodic processing:

-> For Contract Accounts -> Boleto -> Mass Run (FP01)-> For Contract Accounts -> Boleto -> Single Generation (FBO1S)-> For Contract Accounts -> Boleto -> Mass Reversal (FBO1C)-> For Contract Accounts -> Reversal of Check Payments (FPCHS)-> For Contract Accounts -> Dunning notice -> Forward Telephone List (FPVT)-> For Contract Accounts -> Set Processing Locks (FKLOCK2)-> For Contract Accounts -> Delete Processing Locks (FPLKDEL)-> Forward Postings -> Preparation -> Recreate Totals Records (FPT6) (moved andrenamed from Delete Data -> Totals Records (FPT6))-> Forward Postings -> Execution -> Cash Management Transfer (FPCF)-> Closing Preparation -> Reverse Foreign Currency Valuation (FPW2)-> Correction postings:The sequence of the Correction Posting and Closing Preparation nodes has been changed inthe menu so that the Closing Postings node is displayed first followed by the CorrectionPostings node in the menu.-> Evaluation of Open Items -> Perform Evaluation (Parallel Processing) (FPO4P)-> Extraction for Business Information Warehouse -> Extract Installment Plans (FPIPBW)-> Archive Data -> Foreign Currency Valuation (FPAR09)-> Archive Data -> Clearing History (FPAR10)-> Archive Data -> Doubtful Entries (FPAR11)

______________________________________________________________

SAP AG 1

SAP IS-T 4.72______________________________________________________________

SAP Telecommunications

Receivables Management - Contract Accounting (SAP IS-T/RM-CA)

-> Delete Data -> Invoice Creation by Third Party (FPAR12) -> Delete Data -> TotalRecords (Following Document Archiving) (FPARS1)-> Delete Data -> Logs of Submissions for Collection (FP03DML)

-> Delete Data -> Entries in Dunning Telephone List (FPVT1)- Administration:

-> Create Search Index for Archived Payment Lot (FP05ARC)o Tools:

- Administration of mass processing:-> Schedule Mass Activity (FPSCHEDULER)-> Enhanced Message Management -> Display Clarification List (EMMACL)-> Enhanced Message Management -> Clarification List with Short Cut (EMMACLS)-> Enhanced Message Management -> Clarification with Automatic Processes(EMMACAP)-> Enhanced Message Management -> Creation of Clarification Cases in Mass Run(FPEMMACGEN)

- Administration of customer portal:-> Customer Messages Worklist (IQS8)-> Create Customer Notifications (FPACTEN)

- Forward data to SAP Credit Management:-> Transfer Credit Data (FPCM1)-> Replicate Creditworthiness (FPCM2)

2 Contract Accounts Receivable and Payable

2.1 Account Balance Display

UseRestriction of Item SelectionIf 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 BalanceYou 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 CustomizingDefine 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.

______________________________________________________________

SAP AG 2

SAP IS-T 4.72______________________________________________________________

2.2 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

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.

Effects on CustomizingYou 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.

2.3 Archiving

UseDocument ArchivingIn 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.

______________________________________________________________

SAP AG 3

SAP IS-T 4.72______________________________________________________________

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 ValuationYou 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 HistoriesYou can archive clearing histories with the new archiving object FI_MKKPCR. The prerequisites for thearchiving are described in the documentation for report RFKKAR41.

Archiving of Doubtful EntriesYou 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 PartiesYou can use the new archiving object FI_MKKTHI to archive data fo invoicing by third parties (see alsodocumentation for report RFKKTHPAR01).

2.4 Authorization ObjectsUse

Maintaining Interval VariantsWith 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 Description01 Create variants02 Change variants03 Display intervals06 Delete variants07 Generate variants

New Authorization Object F_FKKCJ for the Cash Journal

______________________________________________________________

SAP AG 4

SAP IS-T 4.72______________________________________________________________

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 Description01 Add or create02 Change03 Display10 Post33 ReadB5 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 aspossible. After Release 4.72, SAP will only support the authorization object F_FKKCJ.

2.5 BAPIs in Contract Accounts Receivable and Payable

UseRequestsYou 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

______________________________________________________________

SAP AG 5

SAP IS-T 4.72______________________________________________________________

BAPI_REQUEST_ADDPERIODS Add execution periods for request

DeletePeriodsBAPI_REQUEST_DELETEPERIODS Delete execution periods for a request

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 DocumentsThe 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 AccountsFrom Release 4.72, you can use the new BAPI CtrAcContractAccount.GetOpenItems.

Changes to the BAPI for Contract AccountsThe selection field in the parameter ValueSelektions has been extended.

2.6 Boletos

UseCreating BoletosTo improve the performance of the program for creating Boletos, you can use the payment method torestrict the selection of open items.

If you also consider statistical documents in Boletos, you can delete or integrate the required statisticaldocuments in event 6303 (see FKK_SAMPLE_6303).Mass Reversal of BoletosYou can now use a mass reversal transaction (FPO1C) for Boletos created by a mass run (see SAP menu:Periodic Processing -> For Contract Accounts -> Boleto).

______________________________________________________________

SAP AG 6

SAP IS-T 4.72______________________________________________________________

AddPeriods

You select the run to be reversed using the run date and the run ID for the creation run. After the reversal,you can create new Boletos for the open items in the reversed Boletos. The system automatically recordsthe new run date and run ID for the payments assigned to the banks during the creation of the Boletos.

Creating Boletos OnlineIn the transaction Create Boleto from Open Items (FBO1S), you can create Boletos online. To do this,select the required open items manually by business partner, contract account, and document number andspecify the bank and account to which the payment is to be made.

This transaction is particularly useful for installment plans. You can select the individual installment planitems by business partner, contract account, payment method, and due date and create one Boleto forthese items.

The system assigns the run date and run ID automatically and saves this data in the header of the Boleto.The payment assigned to the bank is updated in table DFKKBOL_BANKID.

Effects on CustomizingYou make the settings for creating Boletos in the Implementation Guide for Contract AccountsReceivable and Payable under Business Transactions -> Payments -> Creation of Incoming andOutgoing Payments -> Boleto.

2.7 Business Information Warehouse

UseExtracting Open ItemsDuring 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 generalledger 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, contract

______________________________________________________________

SAP AG 7

SAP IS-T 4.72______________________________________________________________

account, 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.

2.8 Cash Desk

UseGeneral 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 ScannerWith 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 orhide 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.

Effects on CustomizingYou 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.

______________________________________________________________

SAP AG 8

SAP IS-T 4.72______________________________________________________________

2.9 Cash Journal

UseReversing WithdrawalsIn 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 ReaderFrom 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.

Effects on Customizing

Posting Areas 0150 and 0160The 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 paymentCP Credit card paymentCH Incoming check paymentPO Postal order paymentCO 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 ClearingAccounts for Payment Lots and that they are as follows:

Validity for the Corresponding Lot Types

PymtType PymtLot CheckLot CardLot Online CheckCS XCP XCH XPO XCO X

______________________________________________________________

SAP AG 9

SAP IS-T 4.72______________________________________________________________

Maintain Specifications for Cash Desk/Cash JournalFrom 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.

2.10 Closing Operations

UseSummarization Accounts and Summarization Company Codes for ReclassificationsYou 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.

Effects on CustomizingSummarization Accounts and Summarization Company Codes for ReclassificationsYou make the specifications for reclassification by summarization company codes and accounts in theImplementation Guide for Contract Accounts Receivable and Payable under Closing Operations ->Reclassifications.

2.11 Submission of Receivables to Collection Agencies

UseThe 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 ResponsibleIf 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 source

______________________________________________________________

SAP AG 10

SAP IS-T 4.72______________________________________________________________

fields of the enhanceable structure FKKCOLLAG. The number of derivation steps corresponds to thenumber of derivation rules that you define in Customizing.

Deletion of Submission LogsYou 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).

Effects on CustomizingYou 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.

2.12 Collective Bills

UseFrom Release 4.72, you can group documents from different contract accounts in a collective billdocument in order to process them together. You can manage and process all of the individual documentsin a collective bill together via a third account the collective bill account. You can create a joint invoiceand make the payment or in the case of payment arrears, dun all of the items in the collective billtogether.

Collective bills are particularly useful, for example, for billing property and house building companiesthat process receivables from utilities companies for their tenants, and for companies with branch-headoffice relationships.

Effects on Existing DataAt master data level, you have to assign the individual contract accounts to a collective bill account. Acollective bill account is a contract account of the contract account category collective bill account. Youhave to define this account in the master record of every contract account whose postings you want togroup in a collective bill. There is no change to the assignment of contract accounts that you link via thecollective bill account to your business partners. To link an account with the collective bill account:

1. In the SAP menu choose Contract Account -> Create or Change.2. In the field Collective Bill Account in the area Invoice Creation on the tab page General Data,

enter the required collective bill account.

Once you have assigned the account to a collective bill account, when you enter posting documents inthis account, each business partner item is automatically linked to a statistical posting document(collective bill document) in the collective bill account.

Effects on CustomizingTo use collective bills, you have to carry out the following in the Implementation Guide for ContractAccounts Receivable and Payable:

o Under Program Enhancements -> Define Customer-Specific Function Modules, enterFKK_COLL_BILL_CREATE_0063 for event 0063, provided this module is not already integratedin the industry-specific module for event 0063.

______________________________________________________________

SAP AG 11

SAP IS-T 4.72______________________________________________________________

In the industry components Utilities and Telecommunications, this module is already integrated inthe industry-specific module for event 0063.

o Under Basic Functions -> Contract Accounts -> Number Ranges and Contract AccountCategories -> Configure Contract Account Categories and Assign Number Ranges, enter acontract account category for collective bill accounts.Set the indicator in the column CB (contract account is collective bill account) and assign anumber range to the contract account category.

o Under Basic Functions -> Postings and Documents -> Document -> Maintain DocumentAccount Assignments -> Document Types -> Maintain Document Types and AssignNumber Ranges, create a document type for collective bill documents and assign anumber range to this document type.

o Under Basic Functions -> Postings and Documents -> Document -> Maintain Document AccountAssignments -> Maintain Default for Document Type for Collective Bill, define the document typethat you defined in the previous step as the default for creating collective bill documents.

The main and subtransaction for the collective bill item are determined in event 2222. You can overwriteindustry definitions implemented for this event. This event has already been defined for the industrycomponent Utilities.

2.13 Company Codes

UseReplacement of the Responsible Company Code in Contract Accounts Receivable and PayablePreviously, 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 postedThe 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.

______________________________________________________________

SAP AG 12

SAP IS-T 4.72______________________________________________________________

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 thevalidity 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.

______________________________________________________________

SAP AG 13

SAP IS-T 4.72______________________________________________________________

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.

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.

Effects on CustomizingYou 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.

2.14 Creating Correspondence

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

Requests and Standing RequestsTo 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).

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

2.15 Connection of SAP Dispute Management to Contract Accounts Receivable and Payable

UseFrom Release 4.72, you can create and manage complaints (disputes) from your business partners withregard to incorrect invoices and credits or missing invoices and credits as dispute cases in a disputesystem as part of SAP Dispute Management. These dispute cases contain attributes, such as the reason

______________________________________________________________

SAP AG 14

SAP IS-T 4.72______________________________________________________________

for the complaint, the priority, the disputed amount, the clerk responsible for resolution, and contact dataof the business partner. During the processing of the dispute case, you can trigger functions such as thereversal of an invoice, write-offs, and postings of invoice-related credits. From the dispute case you candisplay the follow-on postings for the case. To get an overview, you can display a list with all disputecases for a business partner or document.

Definition of terms used

Dispute System The system in which the dispute casesare created and managed.

FI-CA System The system in whichContract Accounts Receivable and Payable runs.

Dispute Case The complaint of the business partner asobject to be managed inSAP Dispute Management. The dispute casecontains attributes such as the amount, dataabout the status of processing and forcategorizing the dispute as well as,in the record, a listof related objects to which thecase references (for example, document, invoicebusiness partner, contract, contract account).

Case Type The following case types aredifferentiated:

- FICA: Incorrect invoice, incorrect credit- FCA2: Missing payment

The case types are differentiated bytheir attributes. A dispute caseof the case type Missing Payment describes, for

example,the case when a customer complains about a dunning

noticethat was executed despite payment having been made.The clerk's job is tofind this payment, which may have been incorrectly

assigned,and potentially reassign itand then close the case. With

______________________________________________________________

SAP AG 15

SAP IS-T 4.72______________________________________________________________

a dispute case of the case typeIncorrect Invoice, the customer has complainedabout an incorrectinvoice amount. Here the clerk hasto check the amountand trigger any adjustment postings,such as reversals, write-offs, orcredits.

Internal Dispute Type Internal categorizationof a dispute case that eachdispute case must have.Since the system behaves differently indifferent case types,and each customer can createinstallation-specific case types,an internal categorization(assignment) is necessary. Thus, thedispute type A001, for example, is an incorrectinvoice, and dispute type B001 is amissing payment.

Creating Dispute CasesDispute cases are created from the dispute system. However, you can also create dispute cases in theFI-CA system.

In the document display, you can use the function Create Dispute Case to create a dispute case. Adialog box appears, where you can set the default values defined for event 1250. For a sample form ofevent 1250, see sample function module FKK_SAMPLE_1250.

The specification of a business partner is mandatory in each dispute case; the specification of a contractaccount and contract is option and determines the level of detail of the dispute case. The system includesthe document displayed as a disputed document in the case. The data and amounts of the document areused to determine the default values.

Dispute cases are only created at document level, not at line item level. You can create several disputecases for one document.

You can create a dispute case from the account balance. This enables you to create dispute cases withoutan invoice reference, for example, for cases of the type Missing Payment after Dunning Notice. The samedialog box appears for creating the case. Enter the amount specified by the customer as paid as thedisputed amount; then assign the case to a business partner.

When you create a dispute case, the system proposes contact data of the contact person, such as name ande-mail address from the address data of the business partner; you can overwrite this data.

Displaying Dispute Cases

______________________________________________________________

SAP AG 16

SAP IS-T 4.72______________________________________________________________

In the document display, you can use the function Display Dispute Case to display invoice-relateddispute cases. However, this function is only active if such a dispute case exists. If, for example, you haveentered various disputed partial amounts for various reasons, you can simultaneously create severaldispute cases for one document. If there are several dispute cases for one document, the system firstdisplays an overview of all cases, and there you can select the case you want to display. If you create anew dispute case for a document for which a dispute case already exists, the system notifies you of thisbefore sending the dialog for creating a case.

In the account balance you can display an icon on which you can double-click to display a dispute case.To do this, include the field IDISP (placeholder for icon Dispute Case) in a line layout variant for itemswhose document number is included in a dispute case. You also have to set the indicator Field-SensitiveDouble-Click in the settings.With the function Environment -> Account -> Dispute Case -> Display in the menu of the accountbalance display, you can display a list of all of the dispute cases for the business partner/contract account.

With report RFKKDM00 you can select dispute cases across all business partners and contract accounts.This report provides additional selection options to the master data.

Changing Dispute CasesWhen you display a dispute case you can use the function Change to switch the mode and thereforechange a dispute case. However, from the FI-CA system you can only change the disputed amount. Withcase type Incorrect Invoice, you can include additional documents in the dispute case.

With the case type Missing Payment, the payments received since the creation of the dispute case arelisted on the lower part of the screen. The system only adds the payment amounts posted in the disputecase via the payment lot as potential candidates for the missing payment, since you can assume thatpayments posted by the payment program cannot be #missing#. From this list of payments you can createone or more payments, identify them as missed, and assign them to the dispute case. The case can then beclosed in the dispute system.

In the dispute system, an amount field with the total of all potentially suitable payments received sincethe creation of the case is managed before the assignment of the payment found. With the assignment ofthe payment found, the document number of this payment and the identification of the related paymentlot are included in the case. By double-clicking on these objects in the case you can display the paymentdocument or the payment lot item.

With the case type Missing Credit, you can list the credits posted since the creation of the dispute case,identify them and assign them to the case. Only the amounts of the credits that fulfill the followingcriteria are added in the dispute case:

o They are not statistical

o They are not down payments

o They were not posted by the payment run

o They were not posted with the main/subtransaction defined in posting area 0113 for postingpayments on account

Follow-On Postings for Dispute CaseFollow-on postings for dispute cases are reversals, write-offs, credits (invoice adjustments), and theposting of replacement receivables. In these postings, the corresponding amount fields are updated in therelevant dispute cases automatically. With the exception of the case type Missing Payment, incoming

______________________________________________________________

SAP AG 17

SAP IS-T 4.72______________________________________________________________

payments are not automatically logged follow-on postings. For example, in the case of an underpaymentof an invoice, a dispute case is not created automatically for the residual open amount. Dispute cases aregenerally independent of the existence of open items and are not tied to the clearing or partial clearing ofopen items.

You can also post invoice-related credits (invoice adjustments) or replacement receivables withtransaction FPE1 - if, for example, you reverse an incorrect invoice and then post the corrected invoice.To do this, enter the document number to which the adjustment/replacement receivable refers on theinitial screen of the transaction. You can also enter such postings with reference to a dispute case. In thiscase you have to enter the case ID (external identification of the case). The input help shows you thecases for the business partner, and you can select a case.

You can also call up the transactions for reversals and write-offs in the case display of the dispute system.The dispute system calls up the corresponding transaction in the FI-CA system. You can then completethe data and post the document. However, the transactions should only be called up in the display ofdispute cases in the dispute system, since the amounts (for example, amount written off) of the case couldbe changed during the update. Locked dispute cases cannot therefore be updated and you have tosubsequently post the corresponding IDoc in this situation.

Integration in the Payment RunIf an open dispute case exists, you can reduce the amount to be collected from a business partner by thedisputed amount. You can make the logic of the reduction dependent on the status, the priority, thecomplaint reasons, and whether the dispute case is an invoice-related dispute case or a dispute casewithout invoice reference. The reduction therefore makes more sense for the collection of an invoice forwhich there is exactly one invoice-related dispute case than for the collection of the first random item tobe collected where the dispute case has no invoice reference. In order to be able to make these decisionsflexibly, you can define your process logic for event 0610. For a commented example, see the samplemodule FKK_SAMPLE_0610_DISPUTE.

Effects on CustomizingActivating Dispute ManagementYou have to activate the integration of SAP Dispute-Management with Contract Accounts Receivableand Payable (FI-CA) at company code level in the FI-CA system. To do this, set the activity Dispute inthe activity Set Up Company Codes for Contract Accounts Receivable and Payable in the ImplementationGuide for Contract Accounts Receivable and Payable under Organizational Units.

2.16 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.The dunning activity with the Dunning activity: Dunning notice printout (synchronous)(ISU_DUNNING_PRINT_REMIND_0350) function module is no longer part of the exampleCustomizing settings . Use the dunning notice printout from the correspondence container instead. If

______________________________________________________________

SAP AG 18

SAP IS-T 4.72______________________________________________________________

however, you still want to use the ISU_DUNNING_PRINT_REMIND_0350 event, you must alsoincorporate the Print parameter in the FPVB dunning activities run:

1. Execute the RAVC0ALS report using transaction SE38.

2. Enter FI-CA_MASS in the P_APPL field and choose Execute.3. Choose layout 0004.

4. Choose Tab page titles.5. Make the new entry 2| print parameter and select this entry.6. Choose Position of groups on the tab pages.7. Make the new entry 1| S2306.8. Save the entry.

9. Transport the Customizing request with the view.

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

2.17 Enhanced Message Management

UseThe 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. Businessprocess 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 categories

______________________________________________________________

SAP AG 19

SAP IS-T 4.72______________________________________________________________

without 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.

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

2.18 New and Changed Events

UseNew Events

0063: Include Document in Collective Bill0086: Industry Grouping Key for Rounding0104: Clearing: Arrears Surcharges0113: Clearing: Transaction for Payment on Account0175: Account Assignment Derivation for Tax Items in PS-CD0211: Payment Lots: Propose Key for New Lot0222: Payment Lot: Include Screen for Customer Fields0232: Payment Lot: Additional Data for Item0254: Payment Reversal of Locked Checks0367: Dunning: Leading Contract Account and Company Code0501: Document Archiving: Check Header0505: Document Archiving: Check Complete Document0580: G/L Account Check for Accounting Rules0652: Payments: Partner Bank Selection0671: Payments: Round Payment Amount0766: Correspondence: Print Request0767: Correspondence: Create Request0798: Printing: Output Mode of Attached Payment Media1010: Contract Account: Check Company Code Group

______________________________________________________________

SAP AG 20

SAP IS-T 4.72______________________________________________________________

1054: Business Partner: Determine CCARD_ID for Automatic Creation1091: Change Payment Card Data: Print Correspondence1092: Change Payment Card Data: Create Correspondence1247: Account Balance: Determination of Document Category1248: Account Balance: Supplement Context Menu1250: Dispute: Default Values for Creation of Dispute Case1251: Dispute: Distribute Follow-On Postings to Disputes1252: Dispute: Define Communication Channel1253: Dispute: Include Screen for Customer Fields1254: Dispute: Additional Activities for Manual Changes1311: Checks for Posting Area 10101742: Mass Activity: Set Locks1743: Mass Activity: Set Locks, Move Parameters1766: Mass Activity: Evaluation of Open items OP041767: Mass Activity: Integration FI/COPA1840: Mass Activity: Credit Liability Update1841: Mass Activity: Credit Liability Update, Move Parameters1842: Mass Activity: SAP Credit Management Score Replication1843: Mass Activity: SAP Credit Management Parameters, Score Replication1970: 1099 Reporting: Determine Reporting Flag1971: 1099 Reporting: Items Relevant for 1099 Reporting2065: Interest: Set Value Date2404: Posting via IDoc: Processing of Customer Header Segment2504: BW: Open Items, Restrict Selection2506: Open Item BW Extraction: Parameters for Credit Clearing2805: ICWC Account Balance: Create Info Items2806: ICWC Account Balance: Create Item Groupings2807: ICWC Account Balance: Prepare Items2821: ICWC Documents: Correspondence Category Independent Data2822: ICWC Documents: Correspondence Category Dependent Data3031: Installment Plan: Determine Print Type for Payment Forms3910: Migration: Document Transfer - Convert Document Data3920: Migration: Document Transfer - Check Document Data

______________________________________________________________

SAP AG 21

SAP IS-T 4.72______________________________________________________________

4030: SD/FICA Integration: Enhanced Transaction Determination4256: Credits: Create Additional Correspondence4257: Credits: After Creation of Correspondence4258: Credits: Check Payment Method (Transfer/Check)4500: SAP Credit Management: Supplement FI Summary4501: SAP Credit Management: Filter Open Items4502: SAP Credit Management: Determine Liability Category4600: XI: Add FI Summary for SAP Credit Management4601: XI: Asynchronous Outbound Interface for FI Summary5125: Transfer of Open Items: Payment on Account6060: Cash Desk: Barcode Interpretation6302: Boleto: Determination of Default Instruction Key6303: Boleto: Assignment of Instruction Key6306: Boleto: Selection of Statistical Documents6351: Boleto: Adjust Data Parameters for Account StatementsFKK_EMMA_MASS_CREATE_CASES: Creation of Clarification Cases in Enhanced MessageManagement Analysis (EMMA)6507: Requests: Supplement Customer Fields for Approval9050: Print Collection Letter9051: Create Collection Letter9052: Analyze Items from Collection Case9053: Attributes for Collection Case9510: BAPI: Create Request (ExtensionIn)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 Balance9557: Document Extracts: Additional Data Records for Import9558: Document Extracts: Additional Data Records for Deletion9570: Set Mass Locks

______________________________________________________________

SAP AG 22

SAP IS-T 4.72______________________________________________________________

Deleted EventsEvents 0161, 1706, and 1707 are no longer available.

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

2.19 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.

2.20 Foreign Currency Valuation

UseIn 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).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.

Effects on CustomizingIn the Implementation Guide for Contract Accounts Receivable and Payable under Closing -> ForeignCurrency Valuation, define:o Valuation methods

______________________________________________________________

SAP AG 23

SAP IS-T 4.72______________________________________________________________

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

For 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.

2.21 IDoc Interfaces for Communication with External Billing Systems

UseEvaluation of Mass Runs by Enhanced Message Management AnalysisThe 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 LevelThe 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.

Effects on CustomizingIn the Implementation Guide for Contract Accounts Receivable and Payable under Data Transfer ->Communication with External Billing Systems -> Transfer of Accounting Documents, the

______________________________________________________________

SAP AG 24

SAP IS-T 4.72______________________________________________________________

following 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.

2.22 Changed IMG Activities in Contract Accounts Receivable and Payable

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

Organizational UnitsAs 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 GroupsBasic 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 PaymentsThe 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).

______________________________________________________________

SAP AG 25

SAP IS-T 4.72______________________________________________________________

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 SettingsThe activity Activate Dependency Check for Business Partner Master Data Changes is no longeravailable.

2.23 New IMG Activities in Contract Accounts Receivable and Payable

UseIn the Implementation Guide for Contract Accounts Receivable and Payable, the following new settingsare available:

Basic Functions

o Contract PartnerThis section and the subsection Changes to Payment Transactions, with the activitiesClient-Specific Settings, Company Code-Specific Settings, Define Processing Variants, andDefine Rules for Follow-Up Actions are new.

o Bank ChainsIn this section you can now Define Scenarios, Define Bank Chains, and Configure BankChains as in the component Financial Accounting (FI).

o Postings and DocumentsIn the section Automatic G/L Account Determination, you can Define Accounts for Surchargeson Late Payment.

o RequestsFor requests you can Make Settings for Approving Requests.

o Open Item ManagementYou can define Short Account Assignments for Transfer Postings in Account Maintenance.

o Enhanced Message ManagementThe settings for maintaining clarification case categories have been changed over as follows:

______________________________________________________________

SAP AG 26

SAP IS-T 4.72______________________________________________________________

Specifications for Processing Clarification Cases- Generate Selection Screen for Clarification List- Define Reasons for Reversing Clarification Cases- Specifications for Customer-Defined Business Processes and Messages- Define Customer Business Process Areas for Message Management- Define Customer Business Processes for Message Management- Define Customer Business Processes for Processes from CIC

Business Transactions

o Processing Incoming and Outgoing PaymentsThe Customizing for the cash desk/cash journal has been changed over (see release information).

o BoletoIn this section you can make all of the settings required for processing Boletos in Brazil.

o Write-OffsFor write-offs you can Maintain Alternative Expense and Contract Account.

o TransfersYou can now Define Default Values for Transfer Reasons.

o Doubtful Entries and Individual Value AdjustmentsYou can Define an Age Grid for Value Adjustment Variants.

Integrationo Financial Supply Chain Management

- Biller DirectYou can make the following settings for the integration of SAP Bille Direct:- Define Clearing Account for Overpayments- BAdI: Determination of Bill Details- BAdI: Assignment of Business Partners to User IDs- Specifications for the Integration of SAP Dispute Management

- Credit ManagementYou can make the following new system settings as part of the integration of SAP CreditManagement:- Activate Credit Management- Maintain Credit Segments- Assign Open Items to Credit Segments- Define Specifications for Credit Management

- Dispute ManagementFor the integration of SAP Dispute Management you can Make Basic Settings forDispute Management.

______________________________________________________________

SAP AG 27

SAP IS-T 4.72______________________________________________________________

o Funds ManagementThe following settings have been provided for the integration of Funds Management in theFI-CA standard:- Activate FM Table Fields for Contract Accounts Receivable and Payable- Define FM Account Assignment Derivation- Display Activation Status of Fund Accounting- Define Accounts for Funds Clearing

Closing Operationso In the Foreign Currency Valuation you can:

- Define Valuation Areas- Define Valuation Variants- Define Valuation Area-Specific Accounts for Exchange Rate Differences

o In Reclassifications you can:- Define Summarization Accounts- Define Company Codes for Summarization

Technical SettingsYou can Activate Parallel Update in Cash Management.

Program EnhancementsAs part of the introduction of the classification key you can activate the prepared enhancements.

2.24 Information System

UsePreselections 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 andVerifiability 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

______________________________________________________________

SAP AG 28

SAP IS-T 4.72______________________________________________________________

- 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 ItemsTransaction 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.

2.25 Deferral and Installment Plan

UseClearing Locks on Installment Plan ItemsWhen 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

______________________________________________________________

SAP AG 29

SAP IS-T 4.72______________________________________________________________

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 LocksPreviously, 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 KeyYou can also select items for which a new installment plan is to be created by classification key.

Standard Company Code instead of Responsible Company CodeIf 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 HistoryWhen 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 HistoryThe 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 3000When 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 moduleFKK_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 CreatedWhen 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).

______________________________________________________________

SAP AG 30

SAP IS-T 4.72______________________________________________________________

2.26 Integration

UseEvent 4030: Determination of SD/FI-CA TransactionBefore 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 ManagementWith 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 Managemento Sending an FI summary to SAP Credit Managemento Replication of the score in SAP Credit ManagementFI-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.

______________________________________________________________

SAP AG 31

SAP IS-T 4.72______________________________________________________________

Effects on CustomizingYou 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.

2.27 Interest Calculation

UseInterest Calculation RuleThere 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 DateWith a function module processed in event 2065 you can change the date for the Interest CalculationTo for clearing items.

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.

Effects on CustomizingYou 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.

______________________________________________________________

SAP AG 32

SAP IS-T 4.72______________________________________________________________

2.28 Processing Locks

UseSetting Processing LocksWith 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.You have to define event 9570 for the following application-specific locks:

Lock Category Object

21 Insurance policy22 Partner locks for insurance policy41 Utility contract51 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.

2.29 Mass Runs

UseRepeated Processing of a Job IntervalIf 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.

Effects on CustomizingYou 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.

2.30 Master Data

UseChanging the Bank Data of a Business PartnerWith the new transaction Maintain Payment Data (FPP4) (see SAP menu: Master Data -> Business

______________________________________________________________

SAP AG 33

SAP IS-T 4.72______________________________________________________________

Partner), 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

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.

Effects on CustomizingYou 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.

______________________________________________________________

SAP AG 34

SAP IS-T 4.72______________________________________________________________

Currency Type and Currency ValuationWhen 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.

2.32 Processing of Incoming and Outgoing Payments

UsePayment Lot: Archive ConnectionFrom 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 KeyIf 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 ItemsIf 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 FunctionThe 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: Clarificationo From Release 4.72, you can have the clarification account determined dependent on the document

type. 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

______________________________________________________________

SAP AG 35

SAP IS-T 4.72______________________________________________________________

2.31 Evaluating Open ItemsUse

(and optionally the city) in the field Sold-to-Party/Account Holder.Payment Lot: Changes to Protected Fieldso In check lots, you can use the special function Correct Check Number to correct the check number

for 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 numbershave 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 RFKKZE00In 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.

Effects on CustomizingPayment Lot: ClarificationYou 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 selec