FICA-RM-TC- SAP

SAP AG Release Notes

SAP Telecommunications Receivables Management Contract Accounting (SAP IS-T/RM-CA) as at 4.72

March 2004

______________________________________________________________

Copyright

Copyright(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 any means or translated into another language, without the prior consent of SAP AG. The information 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 registered trademarks of their respective companies.

SAP IS-T 4.72 Content SAP AG ______________________________________________________________

1 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24 2.25 2.26 2.27 2.28 2.29 2.30 2.31 2.32

New Entries in the SAP Menu for Telecommunications Release 4.72 IS-T-CA Contract Accounts Receivable and Payable Account Balance Display Archiving for Tax Reporting Argentina (Changed) Archiving Authorization Objects BAPIs in Contract Accounts Receivable and Payable Boletos Business Information Warehouse Cash Desk Cash Journal Closing Operations Submission of Receivables to Collection Agencies Collective Bills Company Codes Creating Correspondence Connection of SAP Dispute Management to Contract Accounts Receivable and Payable Dunning Enhanced Message Management New and Changed Events Conversion of Finnish Bank Statement to MultiCash (Enhanced) Foreign Currency Valuation IDoc Interfaces for Communication with External Billing Systems Changed IMG Activities in Contract Account Payable New IMG Activities in Contract Accounts Receivable Payable Information System Deferral and Installment Plan Integration Interest Calculation Processing Locks Mass Runs Master Data Evaluating Open Items Processing of Incoming and Outgoing Payments

1 2 2 3 3 4 5 6 7 8 9 10 10 11 12 14 14 18 19 20 23 23 24 25 26 28 29 30 32 33 33 33 35 35

______________________________________________________________ SAP AG

iii

SAP IS-T 4.72 Contents SAP AG ______________________________________________________________

2.33 2.34 2.35 2.36 2.37 2.38 2.39 2.40 2.41 2.42 2.43 2.44

Payment Transactions Collections in the Print Workbench Postings and Documents Prenotifications New Reports Requests Processing of Returns Integration of Schedule Manager in Contract Accounts Receivable and Payable Stop Future Payment (Denmark) Tax Reporting in Contract Accounting (New) Write-Offs Generic Withholding Tax Reporting (Enhanced)

36 38 39 44 44 45 46 47 48 48 49 49

______________________________________________________________ SAP AG

iv

SAP IS-T 4.72 ______________________________________________________________

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

1 New Entries in the SAP Menu for Telecommunications with Release 4.72 Use The following transactions have been added to the SAP menu in the areas listed: o

Business master data: -

o

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

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 and renamed 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 in the menu so that the Closing Postings node is displayed first followed by the Correction Postings 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 ______________________________________________________________

-> Delete Data -> Invoice Creation by Third Party (FPAR12) -> Delete Data -> Total Records (Following Document Archiving) (FPARS1) -> Delete Data -> Logs of Submissions for Collection (FP03DML) -> Delete Data -> Entries in Dunning Telephone List (FPVT1) o

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

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 Use Restriction of Item Selection If you select the button Period for Item Selection (F7) on the initial screen of the account balance display, you can restrict the period that the system uses for selecting the items in the account balance. Context Menu in the Account Balance You can call up a context menu by clicking on the right mouse button when the cursor is on an item in the account balance. In events 1247 and 1248, you can adjust the functions of the context menu to meet your requirements or add to them. Effects on Customizing Define the required function modules for events 1247 and 1248 in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function 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 archive info structures for archiving objects FKK_GENREP, FKK_GENREV, and FI_MKKGENS are delivered and 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 tables in the archive info structures above. Only by using these info structures with these function modules do you ensure that the system correctly connects the Argentine tax reports to the archive. Effects on Customizing You need to assign the above function modules to each of the relevant tax events: 0515, 0520, and 0525. You do so in Customizing for Financial Accounting, under Contract Accounts Receivable and Payable -> Basic Functions - > Tax Reports -> Tax Reporting - Argentina -> Basic Settings -> Activate Recording of Tax Data.

2.3 Archiving Use Document Archiving In future, the program for archiving documents (RFKKAR10) checks whether the balance of the document is zero (check DOCUMENT-01). Two new events are available: o

In event 0501 you can check document headers in blocks.

o

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

If you need data from other tables for the document check in event 0505, you should read this data in advance in event 0501 in order to avoid adverse effects on performance. In event 0501, you can select all of the data required for the documents transferred and save it to the local memory. This means that you can 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 Development Kit (ADK) standard log. You can now no longer display the details of documents that cannot be archived in the detailed error log. Instead, click on the document number in the detail log to go to the document display. The number of archived entries in the individual tables is no longer displayed for the individual documents. These totals are now only displayed for all archived documents. However, you can display the archive entered before deletion using the Archive File Browser (transaction AS_AFB) and thus check the archived structures/content. Archiving Information about the Foreign Currency Valuation You can use the new archiving object FI_MKKVAL to archive the data that arises from the foreign currency valuation. The prerequisites for the archiving are described in the documentation for report RFKKAR36. Archiving Clearing Histories You can archive clearing histories with the new archiving object FI_MKKPCR. The prerequisites for the archiving are described in the documentation for report RFKKAR41. Archiving of Doubtful Entries You can archive data for doubtful receivables with the new archiving object FI_MKKDRVA. The prerequisites for the archiving are described in the documentation for report RFKKAR44. Archiving of Transfer Records for Invoicing by Third Parties You can use the new archiving object FI_MKKTHI to archive data fo invoicing by third parties (see also documentation for report RFKKTHPAR01).

2.4 Authorization Objects Use Maintaining Interval Variants With authorization object F_KKVARI, you can restrict the authorizations for maintaining interval variants: o

In the field OBJECT_KK, define the authorization for individual objects, such as GPART and VKONT.

o

In the field ACTVT, you can control the authorizations for the following activities: Activity 01 02 03 06 07

Description Create variants Change variants Display intervals Delete variants 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 been replaced by the authorization object F_FKKCJ. In the field ACTVT, you can control the authorizations for the following activities: Activity 01 02 03 10 33 B5

Description Add or create Change Display Post Read Display history

If you cannot change over to the authorization object F_FKKCJ in the cash journal quickly, see SAP note 667984. This note contains a description of how you can continue to use the old authorization object F_FBCJ in the FI-CA Cash Desk. Note that you should deactivate this temporary solution as soon as possible. After Release 4.72, SAP will only support the authorization object F_FKKCJ.

2.5 BAPIs in Contract Accounts Receivable and Payable Use Requests You can now use new BAPIs for the business object CA_REQUEST to process requests. The following methods are supported: Create BAPI_REQUEST_CREATE

Create request

Getdetail BAPI_REQUEST_GETDETAIL

Read request

Change BAPI_REQUEST_CHANGE

Change request

Delete BAPI_REQUEST_DELETE

Delete request

EasyCreate BAPI_REQUEST_EASYCREATE

Create request with template

______________________________________________________________ SAP AG

5

SAP IS-T 4.72 ______________________________________________________________

AddPeriods BAPI_REQUEST_ADDPERIODS

Add execution periods for request

DeletePeriods BAPI_REQUEST_DELETEPERIODS

Delete execution periods for a request

AddSpecialDates BAPI_REQUEST_ADDSPECIALDATES

Add special dates for request

DelSpecialDates BAPI_REQUEST_DELSPECIALDATES

Delete special dates for a request

AddLineItems BAPI_REQUEST_ADDLINEITEMS

Add request items

DelLineItems BAPI_REQUEST_DELLINEITEMS

Delete request items

Changes to the BAPIs for FI-CA Documents The parameters ItemRelation and CardData have been added to the BAPI CtrAcDocument.Create, The parameters DocumentHeader and DocumentHeaderX have been added to the BAPI CtrAcDocument.Change New BAPI for Contract Accounts From Release 4.72, you can use the new BAPI CtrAcContractAccount.GetOpenItems. Changes to the BAPI for Contract Accounts The selection field in the parameter ValueSelektions has been extended.

2.6 Boletos Use Creating Boletos To improve the performance of the program for creating Boletos, you can use the payment method to restrict the selection of open items. If you also consider statistical documents in Boletos, you can delete or integrate the required statistical documents in event 6303 (see FKK_SAMPLE_6303). Mass Reversal of Boletos You 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 ______________________________________________________________

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 records the new run date and run ID for the payments assigned to the banks during the creation of the Boletos. Creating Boletos Online In 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 and specify 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 plan items by business partner, contract account, payment method, and due date and create one Boleto for these 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 Customizing You make the settings for creating Boletos in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Creation of Incoming and Outgoing Payments -> Boleto.

2.7 Business Information Warehouse Use Extracting Open Items During the evaluation of receivables balances in the Business Information Warehouse (BW), you can now 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 is the same. In event 2506, you can determine which of the following data has to agree for the credits to be cleared: o

Company code

o

Business area

o

General ledger account

If you do not define the event individually, clearing only takes place if the company code and the general ledger account are the same for the receivable and the credit. In the simulation, the due date of the credits is fixed to the due date of the receivables cleared. This means that when the items are totaled and sorted, the status is the status that would be reached if the credits were cleared with the oldest receivables due. If a credit memo is to be distributed over several receivables, the extractor simulates several fictitious items. The restriction by business partner has been added to the extraction of open items. This means that you can now restrict the extraction of open items to a subset of business partners before the open item analysis. You can use event 2504 to restrict the quantity of business partners selected. The functions of event 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. The system recognizes the runs to be restricted from the naming convention used in the event modules. The fields 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 Business Information Warehouse (BW). The data can be extracted either with or without consideration of previous extractions (delta queue). As standard, only the most important data for the installment plan headers, installment plan items, and original items is extracted. However, you can extend the extract structures. You can use events 2525 and 2530 to read additional data and fill additional fields in the extract structures.

2.8 Cash Desk Use General Ledger Account Postings In the cash desk (Short Account Assignment) The function for transferring incoming and outgoing payments in the Cash Desk has been enhanced and you can now carry out the transfer postings with a tax on sales and purchases part. The field Tax Code has been added to the area G/L Account Posting on the tab page Specifications for Payment on the initial screen of the Cash Desk. The following fields have been added to the Customizing activity Define Short Account Assignments for Transfer Postings in the Cash Desk: o

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

o

Authorization Group With the authorization group you can assign specific authorizations to allow a clerk, for example, to use only certain short account assignment keys. Maintain the authorization via authorization object F_KK_KUKON.

Barcode Scanner With Release 4.72, the connection of barcode scanners has been implemented in the cash journal and the Cash Desk. In the Customizing activity Maintain Specifications for Cash Desk/Cash Journal, you can define whether the barcode entry field is to be displayed or hidden. If the barcode entry field is available, you display or hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry -> Display/Hide. In the menu under Extras -> Hold Settings, you can save the settings user-specific. The barcode scanned must be interpreted in event FKK_SAMPLE_6050 and the data required for the entry must be entered on the input screen for the cash desk/cash journal. Effects on Customizing You make the system settings in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Processing Incoming/Outgoing Payments -> Cash Desk/Cash Journal.

______________________________________________________________ SAP AG

8

SAP IS-T 4.72 ______________________________________________________________

2.9 Cash Journal Use Reversing Withdrawals In the cash journal menu under Edit, you can use the function Reverse Withdrawal to reverse withdrawal documents. This function does not just reverse the document; it also corrects the cash desk balance. Barcode Reader From Release 4.72, you can connect a barcode reader in the cash journal and the cash desk. In Customizing, you can define whether the barcode entry field is to be hidden or displayed. If the barcode entry field is available, you display or hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry -> Display/Hide, provided the workplace has a barcode reader. In the menu under 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 cash desk or the cash journal. For more information, see the sample function module FKK_SAMPLE_6060. Effects on Customizing Posting Areas 0150 and 0160 The field Payment Type has been added to the posting areas 0150 - Cash Journal: Specifications for Posting Cash Desk Differences - and 0160 - Cash Journal: Bank Clearing, Deposit, and Withdrawal Accounts. You can define a separate cash desk clearing account per payment type: CS CP CH PO CO

Incoming and outgoing cash payment Credit card payment Incoming check payment Postal order payment Outgoing check payment

The introduction of the new payment type CO for outgoing check payments means that you can now define separate cash desk clearing accounts for incoming and outgoing check payments. Make sure that you also enter the cash desk clearing accounts that you enter here in the activity Define Bank Clearing Accounts for Payment Lots and that they are as follows: Validity for the Corresponding Lot Types PymtType PymtLot CS X CP CH PO CO

CheckLot

CardLot

Online Check

X X X X

______________________________________________________________ SAP AG

9

SAP IS-T 4.72 ______________________________________________________________

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

2.10 Closing Operations Use Summarization Accounts and Summarization Company Codes for Reclassifications You can now display reclassifications for a group of accounts or company codes - previously, you could only display the reclassifications in the balance of one receivables or payables account of a business partner within a company code. Summarization accounts are required for key date-related open items whose receivables and payables accounts are displayed in one item in the financial statements (for example, same type of legal transaction for 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 create the financial statements (for example, consolidated financial statements). See the release information for Foreign Currency Valuation and Evaluation of Open Items. Effects on Customizing Summarization Accounts and Summarization Company Codes for Reclassifications You make the specifications for reclassification by summarization company codes and accounts in the Implementation Guide for Contract Accounts Receivable and Payable under Closing Operations -> Reclassifications.

2.11 Submission of Receivables to Collection Agencies Use The following functions have been added to the submission of receivables to collection agencies: o

Derivation of collection agency responsible

o

Deletion of submission logs

Derivation of Collection Agency Responsible If you want to release receivables to different collection agencies using rules in your organization, from Release 4.72, you can define these derivation rules in Customizing for Contract Accounts Receivable and Payable. The derivation rules defined in Customizing are evaluated by the derivation tool. The derivation tool is always called in the function module FKK_COLL_AG_SAMPLE_5060 if items are released for collection individually in transaction FP03E or in the mass release via transaction FP03M. The derivation tool 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 the number of derivation rules that you define in Customizing. Deletion of Submission Logs You can now delete logs recorded in table DFKKOPCOLL by the mass run for submitting receivables to collection agencies (FP03M). You can do this with transaction Delete Submission Logs (FP03DML) (see SAP menu: Periodic Processing -> Delete Data). Effects on Customizing You define the derivation rules for the responsible collection agency in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Submission of Receivables to Collection Agencies -> Define Derivation Rules for Responsible Collection Agency.

2.12 Collective Bills Use From Release 4.72, you can group documents from different contract accounts in a collective bill document in order to process them together. You can manage and process all of the individual documents in a collective bill together via a third account the collective bill account. You can create a joint invoice and make the payment or in the case of payment arrears, dun all of the items in the collective bill together. Collective bills are particularly useful, for example, for billing property and house building companies that process receivables from utilities companies for their tenants, and for companies with branch-head office relationships. Effects on Existing Data At master data level, you have to assign the individual contract accounts to a collective bill account. A collective bill account is a contract account of the contract account category collective bill account. You have to define this account in the master record of every contract account whose postings you want to group in a collective bill. There is no change to the assignment of contract accounts that you link via the collective 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 in this account, each business partner item is automatically linked to a statistical posting document (collective bill document) in the collective bill account. Effects on Customizing To use collective bills, you have to carry out the following in the Implementation Guide for Contract Accounts Receivable and Payable: o

Under Program Enhancements -> Define Customer-Specific Function Modules, enter FKK_COLL_BILL_CREATE_0063 for event 0063, provided this module is not already integrated in 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 in the industry-specific module for event 0063. o

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

o

Under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Document Types -> Maintain Document Types and Assign Number Ranges, create a document type for collective bill documents and assign a number range to this document type.

o

Under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Maintain Default for Document Type for Collective Bill, define the document type that 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 overwrite industry definitions implemented for this event. This event has already been defined for the industry component Utilities.

2.13 Company Codes Use Replacement of the Responsible Company Code in Contract Accounts Receivable and Payable Previously, the responsible company code had the following control characteristics in FI-CA: o

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

o

It was the company code in which payment transactions were processed

o

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

The coupling of these functions heavily restricts the options in some areas and leads, for example, to you having 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 group The company code group includes all company codes that are permitted for posting to a company account. One company code group is assigned to each contract account. Company code groups can overlap. 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 code Exactly one paying company code is always assigned to each company code group. A paying company code is responsible for payment transactions. You have to define house banks and payment methods for paying company codes. Several company code groups can have the same paying company code. The paying company code does not have to be in the company code group itself.

______________________________________________________________ SAP AG

12

SAP IS-T 4.72 ______________________________________________________________

o

Standard company code One standard company code is assigned to every contract account. You use the standard company code 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 codes takes place automatically during the first check (contract account or document) where you check the validity of a company code group or where the company code group is a prerequisite. For each responsible company code, the system creates a company code group with the same key. The company codes that were previously assigned to the responsible company code are assigned to this company code group. The responsible company code is assigned as the paying company code for the group. 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 the new name is language-dependent, it is automatically created in all languages used in the installation. The languages 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 mandatory requirements. For existing contract accounts, you can use conversion report RFKKSTDBK to add the standard company code. The standard company code receives the value of the former responsible company code. You can convert the contract accounts in stages you do not have to convert them all at once. 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 the responsible company code. The following changes have occurred in these checks: o

o

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

Payment methods

-

Own bank details

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 contract account. This enables you to prevent, for example, that cross-country groups (in certain contract accounts) are used. Authorization Check In the authorization object F_KKVK_BUK, the responsible company code was used for the check in the master 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 specification overrides the paying company code determined via the company code group of the contract account. If a paying company code specified in the line item is in a different country to the paying company code determined via the contract account, you also have to specify a payment method in the line item. In this case you cannot use the payment methods from the contract accounts since they refer to a different country. 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 company codes internally. If these are in different countries, the country of the payment run must be assigned via a different parameter. In a payment run, you can still only create payments for one country. Effects on Customizing You define the company code groups in the Implementation Guide for Contract Accounts Receivable and Payable under Organizational Units -> Define Company Code Groups. You assign the company codes to the groups under Organizational Units -> Assign Company Codes to Company Code Groups.

2.14 Creating Correspondence Use Balance Notification You can use event 9552 to create balance notifications. In this event you decide whether a balance notification is to be created. Requests and Standing Requests To print requests and standing requests, you can use events 0766: Print Request and 0767: Create Request Printout, and correspondence type 0039 Request (see also the release information for Requests). Effects on Customizing You define customer-specific function modules in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.

2.15 Connection of SAP Dispute Management to Contract Accounts Receivable and Payable Use From Release 4.72, you can create and manage complaints (disputes) from your business partners with regard to incorrect invoices and credits or missing invoices and credits as dispute cases in a dispute system 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 data of the business partner. During the processing of the dispute case, you can trigger functions such as the reversal of an invoice, write-offs, and postings of invoice-related credits. From the dispute case you can display the follow-on postings for the case. To get an overview, you can display a list with all dispute cases for a business partner or document. Definition of terms used Dispute System

The system in which the dispute cases are created and managed.

FI-CA System

The system in which Contract Accounts Receivable and Payable runs.

Dispute Case

The complaint of the business partner as object to be managed in SAP Dispute Management. The dispute case contains attributes such as the amount, data about the status of processing and for categorizing the dispute as well as, in the record, a list of related objects to which the case references (for example, document, invoice business partner, contract, contract account).

Case Type

The following case types are differentiated: - FICA: Incorrect invoice, incorrect credit - FCA2: Missing payment The case types are differentiated by their attributes. A dispute case of the case type Missing Payment describes, for

example, the case when a customer complains about a dunning notice that was executed despite payment having been made. The clerk's job is to find this payment, which may have been incorrectly assigned, and potentially reassign it and then close the case. With

______________________________________________________________ SAP AG

15

SAP IS-T 4.72 ______________________________________________________________

a dispute case of the case type Incorrect Invoice, the customer has complained about an incorrect invoice amount. Here the clerk has to check the amount and trigger any adjustment postings, such as reversals, write-offs, or credits. Internal Dispute Type

Internal categorization of a dispute case that each dispute case must have. Since the system behaves differently in different case types, and each customer can create installation-specific case types, an internal categorization (assignment) is necessary. Thus, the dispute type A001, for example, is an incorrect invoice, and dispute type B001 is a missing payment.

Creating Dispute Cases Dispute cases are created from the dispute system. However, you can also create dispute cases in the FI-CA system. In the document display, you can use the function Create Dispute Case to create a dispute case. A dialog box appears, where you can set the default values defined for event 1250. For a sample form of event 1250, see sample function module FKK_SAMPLE_1250. The specification of a business partner is mandatory in each dispute case; the specification of a contract account and contract is option and determines the level of detail of the dispute case. The system includes the document displayed as a disputed document in the case. The data and amounts of the document are used to determine the default values. Dispute cases are only created at document level, not at line item level. You can create several dispute cases for one document. You can create a dispute case from the account balance. This enables you to create dispute cases without an invoice reference, for example, for cases of the type Missing Payment after Dunning Notice. The same dialog box appears for creating the case. Enter the amount specified by the customer as paid as the disputed 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 and e-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-related dispute cases. However, this function is only active if such a dispute case exists. If, for example, you have entered various disputed partial amounts for various reasons, you can simultaneously create several dispute cases for one document. If there are several dispute cases for one document, the system first displays an overview of all cases, and there you can select the case you want to display. If you create a new dispute case for a document for which a dispute case already exists, the system notifies you of this before 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 items whose document number is included in a dispute case. You also have to set the indicator Field-Sensitive Double-Click in the settings. With the function Environment -> Account -> Dispute Case -> Display in the menu of the account balance 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 Cases When you display a dispute case you can use the function Change to switch the mode and therefore change a dispute case. However, from the FI-CA system you can only change the disputed amount. With case 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 are listed on the lower part of the screen. The system only adds the payment amounts posted in the dispute case via the payment lot as potential candidates for the missing payment, since you can assume that payments posted by the payment program cannot be #missing#. From this list of payments you can create one or more payments, identify them as missed, and assign them to the dispute case. The case can then be closed in the dispute system. In the dispute system, an amount field with the total of all potentially suitable payments received since the creation of the case is managed before the assignment of the payment found. With the assignment of the payment found, the document number of this payment and the identification of the related payment lot are included in the case. By double-clicking on these objects in the case you can display the payment document 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 following criteria 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 posting payments on account

Follow-On Postings for Dispute Case Follow-on postings for dispute cases are reversals, write-offs, credits (invoice adjustments), and the posting of replacement receivables. In these postings, the corresponding amount fields are updated in the relevant 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 underpayment of an invoice, a dispute case is not created automatically for the residual open amount. Dispute cases are generally independent of the existence of open items and are not tied to the clearing or partial clearing of open items. You can also post invoice-related credits (invoice adjustments) or replacement receivables with transaction 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 the initial screen of the transaction. You can also enter such postings with reference to a dispute case. In this case you have to enter the case ID (external identification of the case). The input help shows you the cases 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 complete the data and post the document. However, the transactions should only be called up in the display of dispute cases in the dispute system, since the amounts (for example, amount written off) of the case could be changed during the update. Locked dispute cases cannot therefore be updated and you have to subsequently post the corresponding IDoc in this situation. Integration in the Payment Run If an open dispute case exists, you can reduce the amount to be collected from a business partner by the disputed amount. You can make the logic of the reduction dependent on the status, the priority, the complaint reasons, and whether the dispute case is an invoice-related dispute case or a dispute case without invoice reference. The reduction therefore makes more sense for the collection of an invoice for which there is exactly one invoice-related dispute case than for the collection of the first random item to be collected where the dispute case has no invoice reference. In order to be able to make these decisions flexibly, you can define your process logic for event 0610. For a commented example, see the sample module FKK_SAMPLE_0610_DISPUTE. Effects on Customizing Activating Dispute Management You have to activate the integration of SAP Dispute-Management with Contract Accounts Receivable and Payable (FI-CA) at company code level in the FI-CA system. To do this, set the activity Dispute in the activity Set Up Company Codes for Contract Accounts Receivable and Payable in the Implementation Guide 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 with the name and address of the business partner; with a customer-specific function module defined in event 4700, 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 example Customizing 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 also incorporate 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 Customizing Register your function module in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules for event 4700.

2.17 Enhanced Message Management Use The Enhanced Message Management Analysis (EMMA) has been enhanced so that you can now analyze the application logs of any jobs in the R/3 system. The transaction code is no longer required to identify the 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 business process areas instead of for individual transaction codes; you can also define the suppression of messages during log preparation per business process area. Business process areas consist of similar business processes, such as billing and invoicing. Business process codes rewrite a specific activity of a business process area regardless of whether this activity was 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 transaction FP08M). 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 existing case categories, you have to maintain the assigned business process code, since this has taken over the role 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 SAP entity 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 container via a data flow definition. In the Customizing for the clarification case categories, the administrative data of the author and the last person to make changes is recorded. With transaction FPEMMACGEN (see SAP menu: Periodic Processing -> Mass Processing Administration -> Enhanced Message Management Analysis -> Create Clarification Cases), you can now create clarification cases in a mass run. You can also create clarification cases for individual intervals of a mass activity or for several. Effects on Customizing Make the system settings required for Enhanced Message Management Analysis in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions.

2.18 New and Changed Events Use New Events 0063: Include Document in Collective Bill 0086: Industry Grouping Key for Rounding 0104: Clearing: Arrears Surcharges 0113: Clearing: Transaction for Payment on Account 0175: Account Assignment Derivation for Tax Items in PS-CD 0211: Payment Lots: Propose Key for New Lot 0222: Payment Lot: Include Screen for Customer Fields 0232: Payment Lot: Additional Data for Item 0254: Payment Reversal of Locked Checks 0367: Dunning: Leading Contract Account and Company Code 0501: Document Archiving: Check Header 0505: Document Archiving: Check Complete Document 0580: G/L Account Check for Accounting Rules 0652: Payments: Partner Bank Selection 0671: Payments: Round Payment Amount 0766: Correspondence: Print Request 0767: Correspondence: Create Request 0798: Printing: Output Mode of Attached Payment Media 1010: Contract Account: Check Company Code Group

______________________________________________________________ SAP AG

20

SAP IS-T 4.72 ______________________________________________________________

1054: Business Partner: Determine CCARD_ID for Automatic Creation 1091: Change Payment Card Data: Print Correspondence 1092: Change Payment Card Data: Create Correspondence 1247: Account Balance: Determination of Document Category 1248: Account Balance: Supplement Context Menu 1250: Dispute: Default Values for Creation of Dispute Case 1251: Dispute: Distribute Follow-On Postings to Disputes 1252: Dispute: Define Communication Channel 1253: Dispute: Include Screen for Customer Fields 1254: Dispute: Additional Activities for Manual Changes 1311: Checks for Posting Area 1010 1742: Mass Activity: Set Locks 1743: Mass Activity: Set Locks, Move Parameters 1766: Mass Activity: Evaluation of Open items OP04 1767: Mass Activity: Integration FI/COPA 1840: Mass Activity: Credit Liability Update 1841: Mass Activity: Credit Liability Update, Move Parameters 1842: Mass Activity: SAP Credit Management Score Replication 1843: Mass Activity: SAP Credit Management Parameters, Score Replication 1970: 1099 Reporting: Determine Reporting Flag 1971: 1099 Reporting: Items Relevant for 1099 Reporting 2065: Interest: Set Value Date 2404: Posting via IDoc: Processing of Customer Header Segment 2504: BW: Open Items, Restrict Selection 2506: Open Item BW Extraction: Parameters for Credit Clearing 2805: ICWC Account Balance: Create Info Items 2806: ICWC Account Balance: Create Item Groupings 2807: ICWC Account Balance: Prepare Items 2821: ICWC Documents: Correspondence Category Independent Data 2822: ICWC Documents: Correspondence Category Dependent Data 3031: Installment Plan: Determine Print Type for Payment Forms 3910: Migration: Document Transfer - Convert Document Data 3920: Migration: Document Transfer - Check Document Data

______________________________________________________________ SAP AG

21

SAP IS-T 4.72 ______________________________________________________________

4030: SD/FICA Integration: Enhanced Transaction Determination 4256: Credits: Create Additional Correspondence 4257: Credits: After Creation of Correspondence 4258: Credits: Check Payment Method (Transfer/Check) 4500: SAP Credit Management: Supplement FI Summary 4501: SAP Credit Management: Filter Open Items 4502: SAP Credit Management: Determine Liability Category 4600: XI: Add FI Summary for SAP Credit Management 4601: XI: Asynchronous Outbound Interface for FI Summary 5125: Transfer of Open Items: Payment on Account 6060: Cash Desk: Barcode Interpretation 6302: Boleto: Determination of Default Instruction Key 6303: Boleto: Assignment of Instruction Key 6306: Boleto: Selection of Statistical Documents 6351: Boleto: Adjust Data Parameters for Account Statements FKK_EMMA_MASS_CREATE_CASES: Creation of Clarification Cases in Enhanced Message Management Analysis (EMMA) 6507: Requests: Supplement Customer Fields for Approval 9050: Print Collection Letter 9051: Create Collection Letter 9052: Analyze Items from Collection Case 9053: Attributes for Collection Case 9510: BAPI: Create Request (ExtensionIn) 9511: BAPI: Create Request (ExtensionOut) 9512: BAPI: Change Request (ExtensionIn) 9513: BAPI: Change Request (ExtensionOut) 9514: BAPI: Create Execution Period for Request (ExtensionIn) 9516: BAPI: Read Request (ExtensionOut) 9552: Balance Confirmation: Check Balance 9557: Document Extracts: Additional Data Records for Import 9558: Document Extracts: Additional Data Records for Deletion 9570: Set Mass Locks

______________________________________________________________ SAP AG

22

SAP IS-T 4.72 ______________________________________________________________

Deleted Events Events 0161, 1706, and 1707 are no longer available. Effects on Customizing You define installation-specific function modules in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.

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: Finland Reference Payments - Convert to MultiCash report (RFEBFI00) has been enhanced to convert the following 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 Use In the foreign currency valuation (transaction FPW1) (see SAP menu: Periodic Processing -> Closing Preparations), you can now save the valuation difference for each open item. This enables you to further process the revaluation of an open item in closing preparations, for example, in the key date-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 to company codes. This means that the foreign currency valuation is compatible with different GAAPs. This means 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 new transaction Log for Foreign Currency Valuation (FPW2), you can get an overview of all foreign currency valuations. You can also reverse individual valuation runs in the display if you have the authorization to run them again later with more current data. Effects on Customizing In the Implementation Guide for Contract Accounts Receivable and Payable under Closing -> Foreign Currency 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 be used 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 to You can define different accounts dependent on the valuation area.

2.21 IDoc Interfaces for Communication with External Billing Systems Use Evaluation of Mass Runs by Enhanced Message Management Analysis The evaluation of Enhanced Message Management Analysis has been activated for the following programs: 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 from External Billing Systems) To define and process customer- or project-specific document header data, you can now define a replacement 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 segment E1FKK_EBS_TOI_HEADER in Customizing. For example, you can change the field BLART or AWTYP. In event 2404, you can also create the object relations between documents via the interface T_FKKOPREL. By defining a customer- or project-specific segment you can transfer the additional data contained therein, for example, the classification key, to the document header. The optional field DOC_TYPE (document type) has been added to the segment E1FKK_EBS_TOI_HEADER. With this segment you can override the document type defined in the interface Customizing at document level. Maintaining Object Relations at Item Level The maintenance of object relations (interface T_FKKOPREL) has been added to event 2413. This means that you can now fill the object relations at document item level from a customer- or project-specific ITEM additional segment. Effects on Customizing In 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 Transfer You can now define a customer- or project-specific header data segment.

o

Define Translation of External Tax ID You can now define (optional) a tax on sales and purchases code as well as the condition key for each external tax code. If you define a tax on sales and purchases code, this is available in events 2405 and 2406 for comparison.

2.22 Changed IMG Activities in Contract Accounts Receivable and Payable Use There have been changes to the following system settings with Release 4.72: Organizational Units As part of the changeover of the company code concept in Contract Accounts Receivable and Payable, you now have to make the settings for the company code in the following activities: - Set Up Company Codes for Contract Accounts Receivable and Payable - Define Company Code Groups - Assign Company Codes to Company Code Groups Basic Functions o

Contract Accounts The activity Activate Additional Checks for Changes to the Business Partner Master Record has been moved from the section Technical Settings to the section Contract Accounts.

o

Postings and Documents In the section Define Account Assignments for Automatic Postings, the activity Define CO Account Assignments has been renamed to Define CO Account Assignment Keys. Here you can also define the required specifications for the Nota Fiscal in Brazil. To do this, Contract Accounts Receivable and Payable uses the Customizing of the standard FI.

Business Transactions o

Payments The activity Specifications for the Clarification of Incoming Checks under Basic Functions -> Check Management has been renamed to Define Specifications for the Clarification of Cashed 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 section Cash Desk/Cash Journal. The activity Maintain Responsibilities for Cash Journal Users has been moved from the IMG to the 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 for Responsible Company Code has been replaced by the activity Define Specifications for Paying Company Code. In the same section, the activity Specifications for Transferring Open Items to the Responsible Company Code is no longer available. o

Submitting Receivables to Collection Agencies The activity Define Strategy for Derivation of Collection Agency Responsible has been renamed to Define Derivation Rules for Collection Agency Responsible and has been enhanced.

Technical Settings The activity Activate Dependency Check for Business Partner Master Data Changes is no longer available.

2.23 New IMG Activities in Contract Accounts Receivable and Payable Use In the Implementation Guide for Contract Accounts Receivable and Payable, the following new settings are available:

Basic Functions o

Contract Partner This section and the subsection Changes to Payment Transactions, with the activities Client-Specific Settings, Company Code-Specific Settings, Define Processing Variants, and Define Rules for Follow-Up Actions are new.

o

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

o

Postings and Documents In the section Automatic G/L Account Determination, you can Define Accounts for Surcharges on Late Payment.

o

Requests For requests you can Make Settings for Approving Requests.

o

Open Item Management You can define Short Account Assignments for Transfer Postings in Account Maintenance.

o

Enhanced Message Management The 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 Payments The Customizing for the cash desk/cash journal has been changed over (see release information).

o

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

o

Write-Offs For write-offs you can Maintain Alternative Expense and Contract Account.

o

Transfers You can now Define Default Values for Transfer Reasons.

o

Doubtful Entries and Individual Value Adjustments You can Define an Age Grid for Value Adjustment Variants.

Integration o

Financial Supply Chain Management -

Biller Direct You 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 Management You can make the following new system settings as part of the integration of SAP Credit Management: - Activate Credit Management - Maintain Credit Segments - Assign Open Items to Credit Segments - Define Specifications for Credit Management

-

Dispute Management For the integration of SAP Dispute Management you can Make Basic Settings for Dispute Management.

______________________________________________________________ SAP AG

27

SAP IS-T 4.72 ______________________________________________________________

o

Funds Management The following settings have been provided for the integration of Funds Management in the FI-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 Operations o

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 Settings You can Activate Parallel Update in Cash Management. Program Enhancements As part of the introduction of the classification key you can activate the prepared enhancements.

2.24 Information System Use Preselections of Master Data (Transaction FPSELP) When you select by dunning data, you can now consider only open items if required previously all cleared items were selected automatically. Data Extracts (GDPdU) From Release 4.72, all developments for the realization of the German Principles of Data Access and Verifiability of Digital Documentation (GDPdU) area available in all releases maintained by SAP. In Releases 4.64, 4.63, and 4.61 however, only the export programs FPDE_EXP, FPDE_AEXP, and FPDE_EXTR are available. All export programs support the SAP format AIS, which can be imported into IDEA. For the Contract Accounts Receivable and Payable objects, the following export, import, and deletion transactions are available: o

Document Extracts -

FPDE_EXP

______________________________________________________________ SAP AG

28

SAP IS-T 4.72 ______________________________________________________________

-

FPDE_AEXP

-

FPDE_IMP

FPDE_DEL You can also select SD documents for the FI-CA documents and export them. o

o

Partner Extracts -

FPDEP_EXP

-

FPDEP_IMP

-

FPDEP_DEL

Customizing Extracts -

FPDEC_EXP

-

FPDEC_IMP

FPDEC_DEL You can use the transactions FPDE_EXTR (evaluation system) and FPDE (extract overview) for all extract objects. Evaluating Open Items Transaction FPO4P provides you with a parallel variant for transaction FPO4. For each interval, this transaction creates a list and a list with the totals records (similar to transaction FPO1P (Open Items for Key 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, the report no longer collects all items in the memory if you have selected an object and a variant (technical settings) (see also the documentation for the report). You can now group the spool requests for individual intervals for the evaluation with transaction FPO1P and transaction FPO4P. Transactions FPO1 and FPO1P can now also calculate the evaluation for different currency types and therefore consider a currency valuation. Transaction FPRECL has therefore also been changed. You can now also post adjustments to reclassifications for different currency types.

2.25 Deferral and Installment Plan Use Clearing Locks on Installment Plan Items When you display installment plans, you can now also display the clearing locks as well as the payment, dunning, and interest locks. When you create and change installment plans, you can create and set clearing 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, and clearing 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 lock reason, by double-clicking on the icon. The display of the installment plan items now also has, in addition to the joint lock icon, a column for each processing lock with the respective lock reason. If there are several locks of the same type with different lock reasons, a tilde appears (~). Double-click on one of these fields to display the details for the locks. Easier Maintenance of Processing Locks Previously, you could only maintain processing locks (payment, dunning, interest, and clearing locks) for installment plan items by double-clicking on the field for displaying the lock icon. Then you had to select the type of lock. Now you can maintain the lock you have selected directly by double-clicking on one of the new table fields. You can also set an unlimited (time) lock by entering a lock reason directly. If there is only an unlimited (time) lock for a lock type, you remove this from the table field by deleting the lock reason. Selection by Classification Key You can also select items for which a new installment plan is to be created by classification key. Standard Company Code instead of Responsible Company Code If the system cannot derive a unique company code from the original receivables when you are creating an installment plan, the system posts the installment plan to the standard company code. New Display Fields in the Installment Plan History When you display the installment plan history (SAP menu: Account -> More Information -> Installment Plan History), the contract account, business partner, and address of the business partner are displayed for each installment plan. New Fields in the Header Data of the Installment Plan History The fields Number of Installments and Distributed Interest and Charges are stored in the header data for the installment plan history. Determination of Company Code, Contract, Business Area, and Business Place No Longer in Event 3000 When you create an installment plan, the company code, contract, business area, and business place are taken from the original item as standard, as long as these fields have the same value in all original items selected. Previously, this check took place in a standard module processed in event 3000. This check now takes place in the standard coding before event 3000. The source code of the standard module FKK_SAMPLE_3000 has been deleted. If you do not want to fill these fields in the installment plan, or want to enter other values, you can do this by defining event 3000 accordingly. Printing of Payment Forms for Installment Plans - List of Correspondence Created When you are printing payment forms for installment plans (SAP menu: Periodic Processing -> For Contract Accounts -> Correspondence -> Print Installment Plan Payment Forms), you can use the entry 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 Use Event 4030: Determination of SD/FI-CA Transaction Before the upgrade from Release 4.6* to Release 4.7*, you have to close all of the reconciliation keys in the 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 during the transfer of an SD billing document. In this event you have access to all of the information in an SD billing document, which means that a more detailed transaction determination is possible here in contrast to Customizing. With the new event 4040 you can restrict the selection of contract accounts when you create/change an SD 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 program termination. From Release 4.72, report RFKKGL00 continues the transfer with the next company code and logs the errors in the spool list. There you can check the completeness of the transfer. Integration of FI-CA with SAP Credit Management With SAP Credit Management you can manage liabilities and scores for a business partner. The central Credit Management server manages information from different systems, such as CRM, Contract Accounts Receivable and Payable (FI-CA), and Accounts Receivable Accounting (FI-AR), and carries out operational credit queries. The use of the interface technology of the Exchange Infrastructure means that 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 the partner message ID for SAP Credit Management. This transfer guarantees the synchronization of the liability update over several systems. In FI-CA there are mass activities for the following activities: o

Sending the liability for a business partner to SAP Credit Management

o

Sending an FI summary to SAP Credit Management

o

Replication of the score in SAP Credit Management

FI-CA also supports the liability query for the online credit check in SAP Credit Management. You can influence the program flow in the following events: o

4500: Add FI Summary

o

4501: Filter Open Items for Liability Determination

o

4502: Determination of Liability Category

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

______________________________________________________________ SAP AG

31

SAP IS-T 4.72 ______________________________________________________________

Effects on Customizing You configure SAP Credit Management in the Implementation Guide for Contract Accounts Receivable and Payable under Integration -> Financial Supply Chain Management -> Credit Management. 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 Credit Management here.

o

In the activity Define Specifications for Credit Management, you define the default values, such as the 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 those of SAP Credit Management. There the credit segments are used to split the liability into different areas (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 open item is to be assigned to.

2.27 Interest Calculation Use Interest Calculation Rule There are two new calculation methods for defining interest calculation rules: o

30/30E You should only use the method 30/30E for exponential interest calculation. The system calculates exponential 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 the number of days in a calendar year.

Setting #Interest Calculation To Date With a function module processed in event 2065 you can change the date for the Interest Calculation To for clearing items. For amounts cleared in the account maintenance, as standard the due date of the invoice and clearing date of 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 amount to calculate the interest for amounts cleared in the account maintenance. Effects on Customizing You define interest calculation rules in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Interest Calculation -> Item Interest Calculation -> Define Interest Calculation Rule.

______________________________________________________________ SAP AG

32

SAP IS-T 4.72 ______________________________________________________________

2.28 Processing Locks Use Setting Processing Locks With the new transaction FKLOCK2 (Set Processing Locks) in the SAP menu under Periodic Processing -> For Contract Accounts, you can create processing locks. From the selection criteria Business Partner, Contract Account, Contract, Company Code, you can set mass locks for a combination of Lock Category, Process, Lock Reason. Locks created in this way contain the data of the 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 22 41 51

Insurance policy Partner locks for insurance policy Utility contract Contract object partner account

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

2.29 Mass Runs Use Repeated Processing of a Job Interval If an interval cannot be processed in a payment run, interest run, or interest calculation run for cash security deposits because the data is locked by another processing function, the system can restart the processing of this interval automatically and as frequently as required. Effects on Customizing You have to enter the maximum number of repetitions in the field Maximum Int. Repetitions in the specifications for General Control on the tab page Job Control under Technical Settings -> Prepare Mass Activities in the Implementation Guide for Contract Accounts Receivable and Payable.

2.30 Master Data Use Changing the Bank Data of a Business Partner With 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 Maintain Payment Data, you can, for example, change the bank details of a customer who changes from being a cash payer to a direct debit payer simultaneously in the business partner master record and in dependent objects, 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 you can 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 event 1054 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 account when you save the data. In this event, you can, for example, change the field Posting Control Group in the contract account if a customer changes from being a cash payer to a direct debit payer. Effects on Customizing You make specifications for changing bank data in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Contract Partner -> Changes to Payment Transactions 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 under Basic Functions -> Correspondence -> Define Application Forms for Correspondence. You define event modules under Program Enhancements -> Define Customer-Specific Function Modules.

______________________________________________________________ SAP AG

34

SAP IS-T 4.72 ______________________________________________________________

2.31 Evaluating Open Items Use

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

2.32 Processing of Incoming and Outgoing Payments Use Payment Lot: Archive Connection From Release 4.72, you can display archived lots and non-archived lots. When you display documents posted by a payment lot, you can also display the related payment lot items if the lot has been archived. This display option requires an additional index table that is created during archiving with effect from Release 4.72. For payment lots archived before 4.72, you can recreate these index entries using report RFKKPLAR. Payment Lot: Default Value for New Key If you want to create a new lot, you can have the system default a suitable key. The prerequisite for this function is that you have registered a suitable module for event 0211. Payment Lot: Installation-Specific Fields in Items If additional fields are included in the payment lot item via the customer include CI_FKKZP, you can display 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 more information see the documentation and the coding examples in the related sample function module FKK_SAMPLE_0222. Payment Lot: Installation-Specific Additional Function The detail screen for the payment lot item contains an installation-specific addition function that you can define to meet your requirements. This function is available under Extras -> XXX, and you can also call it up via a separate pushbutton (optional). In event 0232, the texts for the processing menu and the function key (xxx) are determined, along with which function module is to be called when the user executes this function. For more information, see the documentation for the function module FKK_SAMPLE_0232. Payment Lot: Clarification o

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 lot also 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 ______________________________________________________________

(and optionally the city) in the field Sold-to-Party/Account Holder. Payment Lot: Changes to Protected Fields o

In check lots, you can use the special function Correct Check Number to correct the check number for individual payments in lots that have already been closed or posted. You may need to make a correction, for example, if, when creating the check deposit list, you discover that check numbers have been entered incorrectly. To carry out this function you need authorization 014 for authorization object F_KK_SOND. You make the change in the check lot display. On the first screen, choose Edit -> Correct Check Numbers. Then call up the detailed display for the check payment to be corrected and select Edit -> Correct Check Numbers. The check number field is then 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 to payee during clarification. A correction is necessary, for example, if a data reader has incorrectly interpreted a hand-written note to payee. To carry out this function you need authorization 017 for authorization object F_KK_SOND. To make the fields on the tab pages Payment Data or Note to Payee ready for input, select Edit -> Change Bank Data.

Payment Lot: Transfer with Report RFKKZE00 In the transfer structures BFKKZP and BFKKZS (ZFKKZP/ZFKKZS), the field lengths of the fields SELW1, 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 to adjust the data declarations and the coding in the programs. Effects on Customizing Payment Lot: Clarification You define the clarification account in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Processing of Incoming/Outgoing Payments -> Define Clarification Account. If you want to use the document type as selection criterion, you first have to select the field Document Type as additional key field via Goto -> Key Selection.

2.33 Payment Transactions Use Payment Program: Restriction to One Payment Card Type From Release 4.72, you can restrict the payment run to one payment card type. You can then run separate payment runs for each payment card type, event though the payment method is always the same card payment. For contract accounts with other payment card types, a corresponding message is created in the application log and a payment exception is created. Payment Program: Selection of Partner Bank via New Event In the new event 0652, you can override the automatic selection of partner banks created by the payment program. In the standard system, the partner bank is selected as a result of the bank details defined either in the

______________________________________________________________ SAP AG

36

SAP IS-T 4.72 ______________________________________________________________

contract account or the contract (differentiated by incoming payment and outgoing payment). You can override this by explicitly specifying bank details in the line item. However, it is not possible, for example, to select a partner bank dependent on the currency of the items paid if these bank details are not entered in the items to be paid. Using event 0652, you can now set a different bank details ID dependent on the items to be paid, or prevent payment. See the documentation for function module FKK_SAMPLE_0652. Payment Media Creation: Settings for the Note to Payee The standard options for defining the note to payee have been enhanced for the creation of payment media. In the user-defined specifications, you can now specify the number of items to be prepared only once per payment. This avoids the contents of PAYH and PAYHX being output per item, even though these are the same for all items. In the definition of the item content (FQP5 -> Note to Payee: Content), the sequence (item number) decides whether the content is prepared per payment or per item. If, for example, you have specified 2 information items per payment and 1 information item per item, you have to provide a total of 3 items with content. The first two apply per payment, which means that here only the fields from the structures PAYH and PAYHX are useful. The third item is then repeated for each item. The fields from the structure PAYP are useful here. Payment Media Creation: Correspondence Banks If you use the payment media formats EDIFACT, S.W.I.F.T. (MT 100, 101, 103, 104, 200, and 202), (customer development), from Release 4.72 you can define correspondence banks. This means that you can specify a bank chain with up to three intermediary banks (correspondence banks) in Customizing for the transfer from one bank to another. You can define general and recipient-specific bank chains. You then specify recipient-specific bank chains in the transactions for creating and changing business partner data (FPP1, FPP2) on the tab page Payment Transactions, in the area Bank Chains. The function module FI_PAYMENT_BANK_CHAIN_SET determines the bank chains during the payment media creation and places them in the corresponding structures. If you want to use the function for the payment media formats stated, you have to add the call of the function module FI_PAYMENT_BANK_CHAIN_SET to the function modules defined for the events 20 and 30, or, for customer-defined developments, the events 21 and 31. The function module FI_PAYMENT_BANK_CHAIN_SET contains the data in the corresponding event module as import parameter. Check Management: New Status for Processing Check Locks A new check status (Locked) has been introduced with Release 4.72. This means that you can lock a check and report the lock to the bank, without having to reverse the related payment or issue a replacement check. The check is locked in check management and reported to the bank using transaction FPCHX. After a specific deadline (usually 24 hours) the bank guarantees that this check can no longer be cashed. You reverse the related payment document after this deadline by regularly scheduling transaction FPCHS so that the cleared items are open again. By running the payment run again you can create a new check if required. If checks are cashed within the deadline, you can define, in the settings for the voiding reason, whether the checks are to be deemed 'cashed' automatically or whether clarification cases are to be created. This procedure is interesting for US customers and is known by the name 'Stop Payment'. It is an alternative to the previous way of issuing a replacement check. Invalid checks that have not yet left the

______________________________________________________________ SAP AG

37

SAP IS-T 4.72 ______________________________________________________________

company premises should be voided and reissued as previously. A check lock is not necessary in these cases. Check Management: Enhanced Maintenance in Change Mode If you want to correct the data of a check that was created via a payment run, only a few fields are modifiable. You cannot even change a status set by accident. From Release 4.72, the button 'Administrator has been added in change mode (F6). When you press this button, additional fields are ready for input. To carry out this function you need authorization 018 for authorization object F_KK_SOND. Effects on Customizing You make the settings for bank chains in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Bank Chains: o

Define Scenario

o

Activate Bank Chains

o

Set Up General Bank Chains

In the activity Define Scenario, you define for each scenario, whether the bank chain is determined via the general bank chain search and/or via the partner-specific bank chain search. If both fields are set, the partner-specific bank chain search has priority over the general bank chain search. Using the fields Sender Bank, Recipient Bank Country, Recipient Bank, and Currency, you can define a ranking for the bank chain search for each scenario. SAP delivers four standard scenarios; you can also generate your own scenarios. The bank chains that you create in the activity Set Up General Bank Chains are independent of the bank details of a business partner or of the house banks. For a bank chain ID, you can create up to three intermediary banks. The intermediary banks are linked independently of the recipient and sender banks. Check Management: Settings for Voiding Reasons If you want to use the new check status 'Locked, you need a voiding reason or a lock reason, as for voiding. Whether a reason is permitted as a lock reason depends on the indicator Lock. You can also define whether the cashing of a locked or voided check is to be posted automatically or whether a clarification case (for check encashment) is to be created. In the field Activity, you can enter a 6 digit code to control additional activities (for example, setting limited clearing locks) in customer modules. You can evaluate this field directly or use it as a key for your own customer table.

2.34 Collections in the Print Workbench Use Using Collections, you can now group application forms to process them together. A Collection is an application form of the form type Collection. In a Collection, you can group both application forms from the same form class, and also application

______________________________________________________________ SAP AG

38

SAP IS-T 4.72 ______________________________________________________________

forms from different form classes. You can define your own parameters for the technical components of a Collection, for example, a specific printer. You can classify the individual application forms so that they are issued sequentially or bundled. You can process Collections using transaction EFRM (SAP menu: Print Workbench -> Application Form -> Process), as for application forms.

2.35 Postings and Documents Use Postings and Documents: Classification Key as New Characteristic in Document The new attribute Classification Key has been added to the Contract Accounts Receivable and Payable document and the request. The classification key provides a similar function to the reference number, but allows keys with a length of up to 35 characters. The classification key is an enhancement supported in the system. This means that the attribute is not initially active in the system delivered; you have to activate it explicitly in your installation. Functions of the Classification Key The classification key o

Can be entered in the document header

o

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

o

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

o

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

o

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

Activating the Classification Key You activate the field Classification Key in Customizing using a report that creates the required fields and database indexes. In test mode, the report shows which enhancements would be made. If the classification key is active and you have posted documents with classification keys, the system administrator must update the database statistics for table DFKKKO. This is the only way to make sure that the new indexes are also used. If you use requests, the same applies for table DFKKORDERPOS. Deactivating the Classification Key You can deactivate the classification key but only manually. To do this, you have to remove the field OPORD from the CI includes to which it was added. You then have to convert the database tables; this can involve a long runtime if there are a lot of data records affected.

______________________________________________________________ SAP AG

39

SAP IS-T 4.72 ______________________________________________________________

SAP therefore recommends that you weigh-up the use of the classification key and then adhere to this decision. Postings and Documents: Negative Postings From Release 4.72 you can create negative postings in Contract Accounts Receivable and Payable. A negative posting reduces the transaction figures for the account posted to in the general ledger. A debit posting as negative posting therefore does not lead to an increase of the debit transaction figures; it leads to a reduction of the credit transaction figures. This enables you to show transaction figures for accounts after an incorrect posting and subsequent correction (for example, invoice posting and reversal) as if neither the incorrect posting nor the correction had taken place. Negative postings have been supported in the general ledger (FI-GL) for a long time. You decide whether to permit negative postings at company code level. The corresponding setting in the company code table is also effective for Contract Accounts Payable and Receivable. In addition, in Contract Accounts Receivable and Payable, the document type decides whether a posting is to be posted negatively. You can designate a document type such that negative postings are always created, or such that negative postings are only created for corrections in the same fiscal year. For more information about the setting for the document type, see the Customizing for the document types and the field documentation for the field Negative Posting. A description of negative postings for the most important business transaction follows: Reversal For a reversal, the document type used decides: o

Whether a negative posting is never permitted

o

Whether a negative posting is always permitted

o

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

A special feature is that the items in the reversal document for which the account to be posted to has been swapped in comparison to the original document are not posted negatively This can be the case for aperiodic reversals (swap of P&L accounts) or for posting incoming payments where the reversal is used to post back to the clarification account. Resetting Clearing After resetting clearing, all accounts should appear as if the clearing had not taken place. This means that the inverse posting of cash discount, small differences, exchange rate differences, and taxes that were posted due to the clearing are to be posted negatively. The display in the receivables accounts is retained. Example You reset clearing for a payment received. After the clearing reset, the payment with clearing of open items becomes a type of payment on account again, which means that the credit from the payment is an open item in the receivables account. From the view of the account balance in the receivables account, it is irrelevant whether there was a payment on account or whether items were cleared.

______________________________________________________________ SAP AG

40

SAP IS-T 4.72 ______________________________________________________________

Returns Returns should be treated like reversals. The first item in a returns clearing account is, however, never posted negatively; the same applies to returns charges. Individual Identification of Individual Posting Items If you want to post a document for which negative postings are required for all items manually, all you have to do is select an appropriate document type. However, if you only want to post individual items negatively, you have to enter the entire transaction in two documents. Example Transfer posting from an incorrect G/L account to the correct G/L account. The reset in the incorrect G/L account should be posted negatively, the posting to the correct account not. First enter a negative posting: Clearing account to incorrect G/L account. Then a 'normal posting: Correct G/L account to clearing account. Payments on Account If, on receipt of payment, you first post on account instead of clearing immediately and then carry out clearing later, (for example, via account maintenance or during processing of a subsequent payment), the debit and credit side of the receivables account increases by the amount of the payment on account. If you want to avoid this effect, make sure that every clearing of a posting on account is posted negatively. To do this, you have to indicate in Customizing for the main and subtransaction used for payments on account that each clearing of this item is to be posted negatively. Postings and Documents: Parallel Open Item Processing for Partners If a business partner has several contract accounts, before Release 4.72, it was not possible for two clerks to process open items in different contract accounts for this business partner simultaneously (for example, during account maintenance). Parallel processing in different accounts of a business partner is possible from Release 4.72. Postings and Documents: Hold Status of Open Item Processing During manual processing of clearing transactions, you can save the status of open item processing and reload it later. For this purpose, the new functions Hold Processing Status and Retrieve Processing Status are available on the processing screen for open items. When you hold the status, you have to specify an identification. You can hold several processing statuses in parallel for the same object (for example, same business partner, same collective bill). A processing status is held in the system for 30 days. This period starts from the last time the status is saved. For each processing status, the system also saves the object being processed in addition to the identification. This is either the business partner to whom the open items belong, or for assignment at detail level, the collective bill, the installment plan or the bundle for which assignment of clearing amounts is to take place at the level of the related original item. If the business partner is not unique, the partner with the most active items is set. When you retrieve a held status, in the detail assignment for collective bills, installment plans, and bundles, only identifications that belong to the object named are permitted. The possible entries help (F4)

______________________________________________________________ SAP AG

41

SAP IS-T 4.72 ______________________________________________________________

offers a correspondingly restricted selection. When you retrieve a held status during the processing of open items for one or more business partners, the identifications permitted are those where the business partner held is correct for at least one of the currently selected items. The possible entries help (F4) also offers a correspondingly restricted selection here. In general, the held status is mixed with the current selected items. These can be different to the items that were selected when the processing status was held. Possible causes are: o

Other selection criteria

o

Clearing or partial clearing that has taken place in the meantime

o

Different amounts for clearing in a different currency Here the amounts are translated for open item processing and the translation result may have changed due to changes in the exchange rate.

If a clearing amount was recorded in a held status, and this clearing amount is higher than the total amount of the open items when the status is retrieved, the maximum possible clearing amount is set. If a cash discount amount was specified, this is reduced accordingly so that the cash discount percentage rate is retained. Whenever the held status cannot be used again completely, the user sees a message with details of the variance in the long text. Postings and Documents: Transfer Postings in Account Maintenance In the account maintenance, you can transfer difference amounts to a G/L account defined in Customizing. You have to specify the amount to be posted and similar to the payment lot a short account assignment that the system can use to determine the company code, account, business area, and CO account assignments. The fields for the transfer posting are only active if the user has been assigned to a tolerance group for which a maximum amount and maximum percentage rate for the transfer posting have been specified in Customizing. You cannot transfer to tax-relevant accounts. Postings and Documents: Arrears Surcharges If open items are cleared by payments or clearing of payments, you can define arrears surcharges. These surcharges have the opposite effect to cash discount. For example, if you set a surcharge of 2.00 for an invoice for 100.00, a payment of 100.00 leads to postings for partial clearing in the amount of 98.04 and revenue from payment surcharges of 1.96. Since the calculation of surcharges is dependent on the value date of the payment, clearing transactions with surcharges can only consider additional credit items (for example, from payments on account) if they have the same due date. All other credit items are locked for the current clearing transaction. If clearing processing takes place online, you can deactivate or reduce the surcharges calculated manually. The following transactions enable the calculation and posting or surcharges: o

Payment Lot

o

Cash Desk and Cash Journal

______________________________________________________________ SAP AG

42

SAP IS-T 4.72 ______________________________________________________________

o

General posting online

o

Account Maintenance

o

Automatic Clearing

In order to enable the calculation of surcharges you have to define an installation-specific function module for event 0104. Postings and Documents: Mass Postings and Cash Management For mass postings that run in parallel processes, waiting time may occur due to competing accesses during the update of data for Cash Management. Contract Accounts Receivable and Payable therefore offers a parallel update mode that you can activate for specific categories of mass runs. Cash Management is then updated at the end of each process. If the process is terminated before the Cash Management update, the update takes place when you close the relevant reconciliation key. If the update also fails here, you can transfer the data recorded separately individually. To do this, in the menu for Contract Accounts Receivable and Payable choose Periodic Processing -> Execution -> Cash Management Transfer. Document Transfer During the document transfer, you can also transfer the identification of the partner message from SAP Credit Management (field PRTID) with the header structure. You can also transfer the identification of the subapplication in Contract Accounts Receivable and Payable (field SUBAP) with the item structure (BFKKOP). During the document transfer, you can transfer the company code for the automatic payment transactions (field PYBUK) with the item structure (BFKKOP). You can also transfer the following new structures: o

BFKKOPREL: Relation between objects

o

BFKKOPC: Card supplement for open items

Effects on Customizing Classification Keys To activate the classification key, in the Implementation Guide for Contract Accounts Receivable and Payable choose Program Enhancements -> Prepared Enhancements -> Classification Key. Postings and Documents: Negative Postings You make the setting for the company code (negative postings possible) in the Implementation Guide for Financial Accounting under Financial Accounting Global Settings -> Company Code -> Check and Supplement Global Parameters. You make the setting for the document type in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Document Types -> Maintain Document Types and Assign Number Ranges. The main and subtransactions that you want to define for a negative clearing (example: Payments on Account) are in the Implementation Guide for Contract Accounts Receivable and Payable under Basic

______________________________________________________________ SAP AG

43

SAP IS-T 4.72 ______________________________________________________________

Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Maintain Subtransactions. Transfer Postings in Account Maintenance You define the short account assignments in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Open Item Management -> Short Account Assignments for Transfer Postings in Account Maintenance. You maintain the tolerance groups under Basic Functions -> Postings and Documents -> Document -> Tolerance Groups for Amount Limits and then the entries Define Tolerance Groups and Assignment of Tolerance Groups to Users. Arrears Surcharges To create the installation-specific function module for event 0104 and to register, in the Implementation Guide for Contract Accounts Receivable and Payable choose Program Enhancements -> Define Customer-Specific Function Modules. To define the accounts to be posted to in the case of arrears surcharges, choose Basic Functions -> Postings and Documents -> Document -> Define Account Assignments for Automatic Postings -> Automatic G/L Account Determination -> Define Accounts for Arrears Surcharges. Mass Postings and Cash Management You activate the parallel update of Cash Management for selected processes via: Technical Settings -> Activate Parallel Update of Cash Management.

2.36 Prenotifications Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following prenotification functions have been added: o

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

o

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

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

______________________________________________________________ SAP AG

44

SAP IS-T 4.72 ______________________________________________________________

2.37 New Reports Use Report RFKK_MA_SCHEDULER The program RFKK_MA_SCHEDULER creates and starts new mass activity runs. Once the run has started, the program monitors all parallel jobs started. This program is particularly helpful if you want to schedule and monitor mass activities using the Schedule Manager or your own report.

2.38 Requests Use Printing Requests You can print requests and standing requests as of Release 4.72. All header data on the request and all request items with additional information on the business partners and contract accounts are available for the printout of a request. All execution dates and special dates are also available for the printout of standing requests. Generation and printout occur with events 0766: Print Request and 0767: Generate Request Printout with correspondence 0039 Request; correspondence type 0039 uses form class FI_CA_REQUEST. SAP provides sample form FI_CA_REQUEST_SAMPLE_SF. Entering Notes You can enter notes for requests and standing requests. If you generate documents from requests, the notes are copied over into the notes on the documents. Business Blocks You can set the clearing block for request items payment/dunning/ interest and clearing blocks that are copied into the documents when the documents are generated. You can enter a block reason and validity period for each request item and block. Entering Documents for each Request Item If you create requests with lots of lines and in some circumstances several business partners and contract accounts, this can cause quite a number of documents that can no longer be represented clearly. For this reason, you can only generate documents from requests and standing requests for each request item. You define the corresponding specifications for requests for each request category in Customizing. Multi-Level Control You can also enter requests and standing requests with a tax code that contains several tax rates. The calculated tax amount that is displayed in the request item is determined from the total of amount of the individual tax rates. Classification Key in Request Items You can enter the new field Classification Key in the request items if you have activated the standard enhancement for the classification key. As the classification key is a header field of the document you can

______________________________________________________________ SAP AG

45

SAP IS-T 4.72 ______________________________________________________________

only enter different classification keys in a request if you generate documents for each request item. Displaying Requests in Account Balance By defining corresponding function modules for events 1203, 1209 and 1211 you can display requests and standing requests in account balance. SAP provides function modules FKK_EVENT_1203_REQUEST, FKK_EVENT_1209_REQUEST and FKK_EVENT_12011_REQUEST for this that you can define for the events mentioned or use as templates for your own function modules . BAPIs for Processing Requests In the future you will be able to use BAPIs to process requests and standing requests (see release information BAPIs). Approving Requests Until now you could only approve requests through workflow. As of Release 4.72 you can approve requests using a worklist. You define which classes and categories of requests should be approved through a worklist in Customizing. Event 5510 was enhanced for a customer-specific differentiation between approval by worklist or by workflow. You can also suppress the entry of an approval reason for event 5510 when starting the workflow. Effects on Customizing To generate documents for each request item, set the indicator Document for each item in the IMG of Contract Accounts Receivables and Payable, under Basic Functions -> Requests -> Document Creation -> Define Specifications for Document Creation. You define which requests should be approved per request class, request category, or document type through a worklist in the IMG of Contract Accounts Receivable and Payable, under Basic Functions -> Requests -> Define Settings for Approving Requests .

2.39 Processing of Returns Use Read Returns Data from Archive Via transaction FPO9, (SAP menu: Payments -> Returns -> Returns Lot), you can display returns that have already been archived. Note that when you are archiving, archived returns are no longer available for the determination of the number of returns an important value for determining the returns activities. Zero Total Tax Items If charges are posted for a return, and the charges have a tax code with a tax rate of 0.0%, the system creates zero total tax items and displays these in the returns document. Automatic Creation of Returns Lots At the time of creation, you can create the manual posting items Type of Posting = 3 directly. Check for Changed Bank Details

______________________________________________________________ SAP AG

46

SAP IS-T 4.72 ______________________________________________________________

You can check for a return whether the bank details of the partner have changed since the last payment run. If this is the case, you can either use an alternative returns reason, or you can define your own activities to be carried out by the return via event 0293. Version Numbering and New Fields in the Returns History The new activity fields and the version numbering have been included in the returns history; you can display both using the display variant. Selection via Payment Form Number When you are assigning payments, you can also use the payment form number as selection criterion. New Returns Category "External Payment Collector" If a confirmation of a payment receipt forwarded by a payment collector is incorrect, a return occurs. You have to process such returns in a separate account not the bank clearing account for bank returns. You can determine the G/L account required in the automatic account determination using the new returns category 05 (External Payment Collector). Reversal of Returns with a Clarification Document From Release 4.72, you can also reverse returns with a clarification document. During the reversal of the document (SAP menu: Document -> Reverse), a returns lot that has already been closed is reopened and, if necessary, a new reconciliation key created, and you can then process the clarification case again in the returns lot. The creditworthiness of the business partner concerned is reset accordingly. Save Display Variant for Returns Display In the header of the returns lot you can save a user-dependent line layout variant for data entry. Effects on Customizing You make the settings for the new returns category External Payment Collector in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Returns -> Define Charges Accounts for Returns.

2.40 Integration of Schedule Manager in Contract Accounts Rec. and Pay. Use From Release 4.72, you can schedule mass activities in Contract Accounts Receivable and Payable with the program RFKK_MA_SCHEDULER - Schedule Mass Activities using the Schedule Manager (see SAP menu: Periodic Processing -> Mass Processing Administration). In addition, the following periodic programs have been changed over so that you can also schedule these with the Schedule Manager: Technical Names

Name

RFKKFIKEYCLOSE

Automatic Closure of Reconciliation Keys

______________________________________________________________ SAP AG

47

SAP IS-T 4.72 ______________________________________________________________

Technical Names

Name

RFKKABS1

Check Totals Tables

RFKKGL00

Transfer of FI-CA Totals Records to General Ledger

RFKKCOPA00

Transfer of Account Assignment Data to Profitability Analysis

RFKKPCDS

Bill Payment Cards

RFKKBIB0

Document Transfer

RFKKZE00

Payment Lot Transfer

RFKKRL00

Returns Lot Transfer

RFKKCM00

Data Transfer for Manually Issued Checks

RFKKCR00

Transfer of Cashed Checks

RFKKKA00

Transfer of Data from Account Statement to Payment/Returns Lot

RFKKAV00

Transfer of Payment Advice Notes from Sequential File

RFKKCOPM

Read Collection Agency File

RFKKRD00

Post Revenue Distribution

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

______________________________________________________________ SAP AG

48

SAP IS-T 4.72 ______________________________________________________________

2.42 Tax Reporting in Contract Accounting (New) Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can prepare value-added tax (VAT) reporting with the new program, Tax Reporting in Contract Accounting (RFKKTX00). Effects on Customizing A new Business Add-In, FKK_TAX_REP_00, is available that enables you to modify the list layout to cover country-specific requirements. An implementation is delivered for Mexico, IMP_MX_TAX_REP_00. Note, also, that a new function module is delivered for Mexico, FKK_MX_EVENT_0934, which you must assign to event 934 in Customizing for Financial Accounting, under Contract Accounts Receivable and Payable -> Program Enhancements -> Define Customer-Specific Function Modules (assign under Installation-Specific Function Modules). Refer to the function module documentation for more information.

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

2.44 Generic Withholding Tax Reporting (Enhanced) Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), Generic Withholding Tax Reporting has been enhanced to enable you to select withholding tax data from FI-CA. Under the group box Further Selections, you can select which application the system is to retrieve data from when you run the program, and specify other parameters relevant to FI-CA. Effects on Customizing A new Business Add-In, FKK_WTAX_REP00, is available that enables you to enhance the report to cover country-specific requirements in the output. You can add parameters to the selection screen and modify business partner and withholding tax data. An implementation is delivered for the United States, IMPUS_IDWT_1099MISC.

______________________________________________________________ SAP AG

49