release notes financials

Release Notes

Financials SAP enhancement package 4 for SAP ERP 6.0

Copyright © Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Financial Accounting........................................................................................... 6

Business Function Integration FI-CA/CRM Dispute Management ................ 6

FICA_FSCM_CRM_DISPUTE: Integration FICA/CRM Dispute Management .................. 6

Integration ...................................................................................................................... 7

Business Function Billing and Invoicing .......................................................... 8

FICAX_BILL_INVOICING: Billing and Invoicing .............................................................. 8

Invoicing in Contract Accounts Receivable and Payable ................................................. 9

Billing in Contract Accounts Receivable and Payable .................................................... 11

Enhancements in Billing and Invoicing .......................................................................... 13

EDR Transfer and Demand-Driven Billing Orders (New) ............................................... 15

Business Function Contract Accounts A/R and A/P: 02............................... 16

FICAX_CI_2: Contract Accounts Receivable and Payable, 02 (New) ............................ 16

Posting and Clearing .................................................................................................... 20

Payment Cards ............................................................................................................ 23

Processing of Incoming and Outgoing Payments .......................................................... 24

Payment Transactions .................................................................................................. 25

Country-Specific Development: Italy ............................................................................. 26

Installment Plan............................................................................................................ 27

Information Container ................................................................................................... 28

Enterprise Services ...................................................................................................... 29

External Cash Desk Services ....................................................................................... 31

Collections Management .............................................................................................. 35

Closing Operations ....................................................................................................... 37

Archiving ...................................................................................................................... 38

Account Balance Display .............................................................................................. 40

Dunning ....................................................................................................................... 41

Dunning Inbound Correspondence ............................................................................... 42

Distribution of Revenues .............................................................................................. 43

Master Data ................................................................................................................. 46

Processing Locks ......................................................................................................... 47

Deferred Revenue Postings .......................................................................................... 48

Doubtful Entries and Individual Value Adjustments ....................................................... 51

Write-Off ...................................................................................................................... 54

Enhanced Use of Profit Centers in Contract Accounts Receivable and Payable ............ 56

Automatic Clearing ....................................................................................................... 62

Integration .................................................................................................................... 63

Enhancements to Account Determination ..................................................................... 64

Enhanced Account Assignment of Tax Items ................................................................ 65

Cash Desk ................................................................................................................... 67

Check Escheatment ..................................................................................................... 68

Submit to Collection Agency ......................................................................................... 71

Document Management Service ................................................................................... 76

New Events in Contract Accounts Receivable and Payable .......................................... 77

Extraction of Payments................................................................................................. 81

Extraction of Returns .................................................................................................... 82

Distribution of Revenues .............................................................................................. 83

Extraction of Work Items............................................................................................... 86

Standing Requests ....................................................................................................... 87

New Web Dynpro Applications ..................................................................................... 88

Business Function Contract Accounts Receivable and Payable, Leasing .. 90

FICAX_LEASING: Transfer of Worklists to SAP CRM (Changed) ................................. 90

Business Function Information Life-Cycle Management: Tax Auditing ....... 92

FIN_ACC_ILM: Information Lifecycle Management: Tax Auditing (new) ........................ 92

Business Function Partly Exempt Organizations ......................................... 93

FIN_ACC_PEO: Partly Exempt Organizations (new) ..................................................... 93

Business Function General Ledger Accounting 2 ........................................ 94

FIN_GL_CI_2: New General Ledger Accounting 2 (New) .............................................. 94

FIN_GL_CI_2: Profit Center Assignment Monitor (Enhanced) ....................................... 95

FIN_GL_CI_2: Wizard for Configuring Document Splitting (New) .................................. 96

FIN_GL_CI_2: Wizard for Creating a Document Splitting Rule (New) ............................ 97

FIN_GL_CI_2: Navigation from FI Reports to CO Reports (New) .................................. 98

FIN_GL_CI_2: Validation of Account Assignment Combinations (New) ......................... 99

FI_GL_CI_2: Invoice Reduction (Changed)................................................................. 100

FIN_GL_CI_2: Standard Configuration of Document Splitting (Enhanced) .................. 101

FIN_GL_CI_2: Logical Database BRF (Enhanced) ..................................................... 102

FIN_GL_CI_2: Reports for Displaying Documents (Enhanced) ................................... 103

FIN_GL_CI_2: Closing/Opening Entries for the Leading Ledger (New) ....................... 104

FIN_GL_CI_2: Posting Period Check for CO-FI Postings (New) .................................. 105

FIN_GL_CI_2: Posting Period Check for Non-Representative Ledgers (New) ............. 106

Business Function FI Localization Topics for Japan and Portugal ............ 107

FIN_LOC_CI_2: FI Localization Topics for Japan and Portugal (New)......................... 107

FIN_LOC_CI_2: Migration of Last Year’s Property Tax Data (New) ............................. 108

FIN_LOC_CI_2: Declaration and Output for Property Tax (New) ................................. 110

FIN_LOC_CI_2: Output for Mapas Fiscais (Portugal) (New) ....................................... 111

Business Function FI Localization Topics for Japan and South Korea ..... 112

FIN_LOC_CI_4: FI Localization Topics for Japan and South Korea (New) .................. 112

FIN_LOC_CI_4: Invoice Summary Enhancements (New) ........................................... 113

FIN_LOC_CI_4: Enhancements in Tax Reporting & Payments (New) ......................... 115

Business Function Credit Card Encryption: Periodic Key Exchange......... 116

Periodic Key Replacement for Payment Card Encryption ............................................ 116

Financial Supply Chain Management ............................................................ 119

Business Function Bank Communication ................................................... 119

FIN_FSCM_BNK: Business Function Bank Communication Management (new) ......... 119

Business Function Billing Consolidation Connector ................................... 121

FIN_FSCM_BCONS_CON: Billing Consolidation Connector Business Function.......... 121

Business Function SAP Biller Direct: P2P and Customer Field Extenstion ...................................................................................................................... 122

FIN_FSCM_604_BD_2: Biller Direct, Promise to Pay (New) ....................................... 122

Business Function FSCM Functions 2 ........................................................ 123

FIN_FSCM_CCD_2: Business Function FSCM Functions 2 (New) ............................. 123

FIN_FSCM_CCD_2: Master Data Synchronization for Several FI Systems (New) ....... 125

FIN_FSCM_CCD_2: Head Office/Branch Office Relationships (New) ......................... 126

FIN_FSCM_CCD_2: Master Data Synchronization for Several FI Systems (New) ....... 127

FIN_FSCM_CCD_2: Enterprise Services for Credit Limit Request (New) .................... 128

FIN_FSCM_CCD_2: Web Dynpro Application for Credit Limit Request (New) ............. 129

FIN_FSCM_CCD_2: Enterprise Services for Dispute Case Processing (New) ............ 130

FIN_FSCM_CCD_2: Web Dynpro Application for Dispute Case Processing (New) ..... 131

Business Function FSCM Integration 2 ...................................................... 132

FIN_FSCM_CCD_INTEGRATION: Business Function FSCM Integration 2 ................ 132

Business Function Cash Management: Additional Account Assignments 135

FIN_TRM_CM_DIMENSIONS: CLM-CM, Additional Account Assignments ................. 135

Management Accounting ................................................................................ 137

Business Function CO, Allocations ............................................................. 137

Business Function CO, Allocations (New) ................................................................... 137

Valuation Date for Activity Allocation and Overhead.................................................... 138

Transaction-Based Calculation of Overhead (New) ..................................................... 139

Business Function Financials Master Data Management: Chart of Accounts ...................................................................................................................... 140

FIN_MDM_ACC: Business Function Financial Master Data Management (New) ......... 140

FIN_MDM_ACC: Financial Master Data Management: Charts of Accounts (New) ....... 142

FIN_MDM_ACC: Importing Group Chart of Accounts Master Data (New).................... 143

FIN_MDM_ACC: Import Chart of Accounts Master Data (New) ................................... 144

Treasury and Risk Management .................................................................... 145

Business Function TRM: Correspondence Framework ............................. 145

FIN_TRM_CORR_FW: TRM, Correspondence Framework (New) .............................. 145

Business Function TRM, Hedge Management for FAM............................. 150

FIN_TRM_INS_HM: TRM, Hedge Management for FAM (new) .................................. 150

Business Function TRM, Hedge and Exposure Management, SWIFT ..... 152

FIN_TRM_LR_FI_AN_2: TRM, Hedge and Exposure Management, New Financial

Product (new) ............................................................................................................. 152

FIN_TRM_LR_FI_AN_2: Exposure Management 2.0 (New) ....................................... 156

Financial Accounting

Business Function Integration FI-CA/CRM Dispute

Management

FICA_FSCM_CRM_DISPUTE: Integration FICA/CRM Dispute

Management

Use

As of SAP ECC 6.0, Enhancement Package 4, the business function Integration FI-

CA/CRM Dispute Management is available. This business function makes it possible

to use new functions in the SAP Dispute Management (FIN-FSCM-DM) component.

You can:

o Transfer dispute cases from Contract Accounts Receivable and Payable (FI-CA)

to external applications for further processing

o Transfer dispute cases, which were created in an external application, to

Contract Accounts Receivable and Payable, thereby providing process

integration with the functions of Contract Accounts Receivable and Payable

(payments, dunning)

The integration of disputes of SAP Customer Relationship Management 7.0 with the

dispute cases of SAP Dispute Management (FIN-FSCM-DM) for Contract Accounts

Payable and Receivable is provided by SAP. If you are using Contract Accounts

Receivable and Payable, you can also integrate a different external application with the

dispute cases of SAP Dispute Management (FIN-FSCM-DM) as part of a customer

project.

For more information, see the release note Integration with Dispute

Management (FI-CA).

Integration

Use

Disputes with External Processing

As of SAP ECC 6.0, Enhancement Package 4, when you create dispute cases in

Contract Accounts Receivable and Payable, you can specify that the dispute cases are

not processed in SAP Dispute Management, but are processed instead in an external

component.

The dispute cases can be created in the external component and sent to Contract

Accounts Receivable and Payable.

You can also create these dispute cases in Contract Accounts Receivable and Payable

or in SAP Biller Direct and then send them to the external component using a report

you schedule to run on a periodic basis.

The dispute cases are processed in the external component. (This processing includes

changes to amounts, addition of further documents, changes of attributes or status).

With ECC 6.0, Enhancement Package 4, SAP provides integration with CRM Dispute

of SAP Customer Relationship Management 7.0 as an external component.

Funds Management

As of SAP ECC 6.0, Enhancement Package 4, if you subsequently want to integrate

the Funds Management (PSM-FM) component of Public Sector Management with

Contract Accounts Receivable and Payable (FI-CA), or if you want to post to further

company codes that were previously not assigned to an FM area with active FM

integration, you can write the required FM account assignments to all documents

created before the integration with FM.

For detailed information about the conversion of existing documents, see the IMG

activity Define FM Account Assignment for Subsequent FM Activation.

Effects on Customizing

Dispute Management

Processing by an external component requires new case types in FSCM Dispute

Management, since the ID of the external object (the CRM dispute case) must be

recorded in the case record.

You define new case types in Customizing for Contract Accounts Receivable and

Payable under Integration -> Financial Supply Chain Management -> Dispute

Management -> Basic Settings for Dispute Management in the Definition of Own

Case Types with External Processing group box.

Funds Management

You enter FM account assignment for a subsequent FM activation in

Customizing for Contract Accounts Receivable and Payable under Integration ->

Funds Management (PSM-FM).

Business Function Billing and Invoicing

FICAX_BILL_INVOICING: Billing and Invoicing

Use

As of SAP ERP 6.0, Industry Extension Contract Accounts Receivable and

Payable, Enhancement Package 4, you can use the business function Billing and

Invoicing (FICAX_BILL_INVOICING). You can use this business function to

o Create clarification cases manually or automatically in various invoicing

processes in Contract Accounts Receivable and Payable

o Use the full functions of Billing in Contract Accounts Receivable and Payable

o Convert specific billing and invoicing procedures, for example:

- Topping up a customer account with an amount that will be cleared

against later receivables (from consumption)

- Periodic down payment requests that are cleared against the receivables

from later billing

For more information, see the following release notes:

o Invoicing in Contract Accounts Receivable and Payable (6.02)

o Billing in Contract Accounts Receivable and Payable (6.02)

o Enhancements to Billing and Invoicing (6.04)

o EDR Transfer and Demand-Driven Billing Orders (6.04)

See also

For more information, see SAP Library under SAP ERP -> SAP Contract Accounts

Receivable and Payable (FI-CA).

Invoicing in Contract Accounts Receivable and Payable

Use

As of SAP ERP 6.0 Enhancement Package 2 (Release 6.02), you can use the following

new functions in Invoicing in Contract Accounts Receivable and Payable:

o Release/Adjustment of Cash Security Deposits

In the invoicing process, you can do the following with the new invoicing

function Release/Adjustment of Cash Security Deposits:

- Release cash security deposit credits for clearing and for outgoing

payment

- Adjust cash security deposit amounts (for example, dependent on the

consumption behavior of the customer)

You can view the documentation for this invoicing function under

Release/Adjust Cash Security Deposit.

o Transfer Open Items

In the invoicing process, you can use the new invoicing function Transfer

Open Items to transfer open items from any contract account to the contract

account to be invoiced.

During the invoicing, you can further process the posting items resulting from this

transfer. For example, the items could be cleared as part of the account

maintenance of invoicing.

You can view the documentation for this invoicing function under Transfer

Open Items.

o Activating Line Items Posted before Invoicing

The selection option Selection via Invoicing Order (table DFKKINV_TRIG) has

been added to the existing invoicing function Activation of Line Items Posted

before Invoicing.

If you want certain open items that are to be activated to be able to trigger

invoicing themselves, there must be an invoicing order of the source document

category ACTIT for these items.

The invoicing order can then be created automatically when the open item to be

activated is posted. This is controlled by means of posting area 2627.

As a result, the items are activated by the invoicing processes that can process

the source document category ACTIT.

You can view the documentation for this invoicing function under Activate

Open Items.

o Stamp Tax

In the invoicing process, you can calculate, post, and forward stamp tax using

the new invoicing function Stamp Tax.

If the stamp tax is passed on to the business partner, then the resulting posting

document has the posting date, document date, and due date of the invoice. For

this document, reference document type 0BOL is used in the invoicing

document. The business partner items posted are shown in the invoicing

document as items with type of invoicing item 0BOLLO. These items can be

considered in the final invoice amount.

In the invoicing reversal, you can use the corresponding function to process

stamp tax; at event 2669, you can calculate, post, and forward stamp tax.

At event 2668, you can prevent the receivable being reversed in the invoice

reversal by a stamp charges created during invoicing and forwarded to the

customer.

o Clarification

You can create clarification cases manually or automatically in various processes

of Invoicing in Contract Accounts Receivable and Payable. There is a

clarification process for the asynchronous manual postprocessing of clarification

cases. You can also clarify clarification cases automatically.

In the invoicing process you can use the new invoicing functions Plausibility

Checks for Source Document and Plausibility Checks for Invoicing

Document to determine and run checks for source or invoicing documents.

Dependent on the result of the check, this can lead to the creation of a

clarification case. Contract account checks and error messages in the invoicing process can trigger the creation of a clarification case. In the mass creation, the

clarification case is created automatically; in the individual creation, you can

decide in dialog whether to create a clarification case. Clarification cases can be

clarified automatically in the invoicing process.

In the transfer of billing documents from external billing systems using a BAPI

or IDoc interface, billing documents can be checked, recognized as implausible,

and clarification cases can be created. Use the interface parameter

CFCVALIDATION to check billing documents when they are transferred. When

you import a billing document reversal or adjust a billing document, you can

complete unclarified clarification cases of the billing document automatically.

In the analysis of invoicing orders you can check the source documents and

create clarification cases for the source document or contract account manually.

With the clarification processing in dialog, you can process and complete

clarification cases. It provides the clarification worklist, supports your individual

selection of clarification cases, and displays the data of the clarification case on

a detail screen.


You make the system settings required to activate the invoicing functions in the

Implementation Guide of Contract Accounts Receivable and Payable under Integration

-> Invoicing in Contract Accounts Receivable and Payable -> Invoicing ->

Invoicing Processes -> Define Invoicing Processes.

You define the system settings for posting stamp tax (Bollo) in the Implementation

Guide for Contract Accounts Receivable and Payable under Basic Functions ->

Special Features of Tax Processing -> Stamp Tax (Bollo) (Italy).

You make all system settings required for clarification in Invoicing in Contract Accounts

Receivable and Payable in the Implementation Guide for Contract Accounts Receivable

and Payable under Integration -> Invoicing in Contract Accounts Receivable and

Payable -> Clarification Processing and under Integration -> Invoicing in Contract

Accounts Receivable and Payable -> Program Enhancements -> Define

Clarification Case Categories.

Billing in Contract Accounts Receivable and Payable

Use

As of SAP ERP 6.0 Enhancement Package 2 (Release 6.02), billing is accommodated

in Contract Accounts Receivable and Payable.

Billing in Contract Accounts Receivable and Payable allows you to import and bill Event Detail Records (EDR) from different external rating systems. The billing function

creates billing documents that are invoiced using Invoicing in Contract Accounts

Receivable and Payable. Contract Accounts Receivable and Payable thus supports the

invoice creation process as follows:

o Billing in Contract Accounts Receivable and Payable

- Transfer for EDRs that were valuated in the rating system

- Aggregation of EDRs with regard to the service products defined in the

service contract, based on a stipulated billing cycle

o Invoicing in Contract Accounts Receivable and Payable

- Cross-service invoicing of different billing flows

You can invoice billing documents from Billing in Contract Accounts

Receivable and Payable as well as billing documents from external billing

systems.

- Create an invoice that can be transmitted to the customer on paper or

electronically

o Contract Accounts Receivable and Payable

- Monitoring of the payment of the open items associated with the invoice

The billing process in Contract Accounts Receivable and Payable comprises the

following steps:

o Import billing accounts from an external CRM system by means of a BAPI

interface

EDRs are imported and billed in Billing in Contract Accounts Receivable and

Payable with reference to billing accounts. These billing accounts must first be

imported. The billing accounts exist in an external CRM system (for example,

SAP CRM) and can be transferred to Billing in Contract Accounts Receivable

and Payable by means of a BAPI. The BAPI

BAPI_FKKBI_BILLACCOUNT_UPDATE is provided for this purpose. You also

use the BAPI to make changes to the billing accounts. You cannot make

changes to billing accounts in Billing in Contract Accounts Receivable and

Payable itself.

The components of an invoice to be billed for a billing account are defined using

billing account items.

o Import the EDRs from external rating systems by means of a BAPI interface

You can process EDRs of different EDR categories in Billing in Contract

Accounts Receivable and Payable. Each EDR category has a defined data

structure. The standard SAP contains the EDR category TOLLCOLL for billing

tolls. You can transfer EDRs for the EDR category TOLLCOLL from external

rating systems by means of the BAPI BAPI_EDR_TCOLL_CREATEMULTIPLE.

A comprehensive enhancement concept allows you to define project-specific

EDR categories.

o Create billing orders

Billing cycles enable you to bill billing accounts at regular intervals with Billing in

Contract Accounts Receivable and Payable. To this end, you create billing

orders that are executed by the billing process. The billing order relates to a

contract account.

o Billing of billing orders

When you execute a billing order, the system bills the billing accounts that have

the same billing cycle, which are assigned to a contract account. When billing is

performed for a billing account, a billing period, which determines which EDRs of

the billing account are billed, is created. Thus, for example, all of the EDRs,

which have been transferred to Billing in Contract Accounts Receivable and

Payable since the last billing run and until the 15th of the current month, are

billed for the billing account.

Besides EDR billing, Billing in Contract Accounts Receivable and Payable also

supports the billing of non-EDR-based invoice components, such as the basic

charge of a service contract based on the contract term, or the charge for

providing a technical device. To this end, you define billing account items for

non-EDR-based billing for the relevant billing accounts in Billing in Contract


Executing a billing order creates a billing document that is invoiced using

Invoicing in Contract Accounts Receivable and Payable.


You make the system settings required for Billing in Contract Accounts Receivable and

Payable in the Implementation Guide for Contract Accounts Receivable and Payable

under Integration -> Billing in Contract Accounts Receivable and Payable.

Enhancements in Billing and Invoicing

Use

SAP ECC 6.0, Enhancement Package 4 provides you with additional functions for

billing and invoicing in Contract Accounts Receivable and Payable. These functions

allow you to realize special billing and invoicing procedures. Examples of special billing

procedures are:

o Topping up a customer account with an amount that will be cleared against later

receivables (from consumption)

o Periodic down payment requests that are cleared against the receivables from

later billing

Features

o EDRs for Payment Amounts, Receivables Amounts, and Credit Memo

Amounts

You can use the EDR type AMOUNT for any amounts from payments,

receivables or credit memos that you want to process during billing in Contract

Accounts Receivable and Payable. In the case of amounts from payments, you

can also specify information about the payment method in EDR with the amount.

This means that you can for example process the amount from a credit card

payment using an EDR of the type AMOUNT. Billing and invoicing this amount

produces a receivable that can be cleared using the credit card specified with the

corresponding credit card company.

This means that you can implement a top-up scenario in which your customer

can top-up their account with an amount by specifying their credit card details.

o Billing Account Facts

You can use the operand types AMOUNT, AMOUNTT and AMOUNTP during

billing in Contract Accounts Receivable and Payable to define amounts for billing

a billing account independently of EDRs.

This means that you can define an amount for the billing account that is to be

observed periodically during billing (AMOUNTP). You can realize a basic charge

scenario in which you bill the customer a fixed amount in each bill.

o Billing Procedure

You can perform billing in Contract Accounts Receivable and Payable in

conjunction with a billing procedure. The billing procedure is produced from the

billing cycle assigned to the billing account and is part of the main billing

procedure.

You can define different frequencies for billing for each billing procedure in a

main billing procedure. This means that for a main billing procedure with annual

billing, you can for example define an additional billing procedure with monthly

billing. The system allows you to use monthly billing to generate down payment

requests for a billing account and create annual billing of the actual receivables

for the same billing account.

o Offsetting in Invoicing

You can use the new invoicing function OFFSET_REQ to flag amounts from

down payments for a contract account for subsequent offsetting during invoicing.

You can use the invoicing function OFFSET to offset amounts from receivables

for a contract account during invoicing against amounts you have flagged.

Both amounts that you flag for offsetting and those that you instruct the system

to offset can reference specific items in the billing documents to be invoiced. In a

billing document to be invoiced you can process both standard receivable items

and items that are to be flagged or that are to be offset.

You can use various offsetting reference keys for a contract account to control

this offsetting in great detail. You can for example flag the amounts for a down

payment request generated during billing as a billing account for offsetting. You

can also offset the actual subsequent receivables for the billing account.

If you are using several billing accounts for a contract account, the system

performs offsetting for each billing account.

o Billing and Invoicing for Event-Based Deferred Revenues

You can use the new invoicing function DEF_REV_BY_E to perform event-

based posting for deferred revenues. You can post invoiced services that are

only to affect the revenue when an event occurs to a separate revenue account.

These services are posted to the actual revenue account once the revenue-

relevant event occurs.

You can also trigger the event that triggers this posting by billing a corresponding

EDR.

o Billing and Invoicing for Amounts With Different Original Currencies

You can process EDRs with different amount currencies in a billing document

and convert and post these to an invoicing currency during invoicing.

o Billing and Invoicing of Gross Amounts

You can receive amounts to be billed as gross amounts in EDRs. When the

system invoices the gross amounts, it calculates the tax amount they contain and

posts this to a corresponding tax account as tax.

o Extraction of EDRs

This business function provides you with an extraction process that you can use

to extract EDRs to SAP Netweaver BI.

o Contract Account-Specific Invoicing

You can use contract account-specific invoicing to perform periodic processing of

contract accounts by invoicing (invoicing process) independently of source

documents (such as billing documents). You can for example convert periodic

interest calculation for open items in a contract account.

See also

For more information, also regarding changes to the user interface, see the following

release note: EDR Transfer and Demand-Driven Billing Orders

EDR Transfer and Demand-Driven Billing Orders (New)

Use

As of SAP ECC 6.0, Enhancement Package 4, you can create demand driven

billing orders during the transfer of EDRs.

Effects on Existing Data

There are no changes for existing EDRs.

Effects on Data Transfer

For the EDR categories provided by SAP, the BAPIs for transfer have been enhanced

so that they can generate demand-driven billing orders. If you have defined customer-

specific EDR categories, you also have to adjust the corresponding function module.

To do this, you can use the samples provided by SAP - for example, BAPI

BAPI_EDR_TCOLL_CREATEMULTIPLE and the class used there

CL_FKKBI_EDR_TC_BAPI. In this class, the following methods have been enhanced

for demand-driven billing:

o New instance attribute T_BILLTASK of category FKKBIBILLTASK_TAB.

o New component T_DFKKBIBILLTASK of category DFKKBIBILLTASK_TAB in

local category TY_UPDATE_DATA.

o In method MAP_EDRS, when method GET_BILLACCOUNT_LOADTIME is

called from class CL_FKKBI_EDR_HELP_LOAD, the import parameter

IM_EDRTYPE is filled. Any generated billing orders (export parameter

EX_BILLTASK_TAB) are copied to instance attribute T_BILLTASK.

o In method UPDATE_PREPARE, duplicates are avoided by calling method

CL_FKKBI_BILLTASK=>REDUCE_BY_EXISTING and exported using

parameter EX_UPDATE_DATA. The key of the new billing orders are exported

using the new parameter EX_BILLTASKKEY_TAB.

o The method SAVE calls the function module FKK_BI_BILLTASK_CREATE to

update billing orders. The method exports the key of the new billing orders using

the new export parameter EX_BILLTASKKEY_TAB.

o The function module BAPI_EDR_TCOLL_CREATEMULTIPLE receives the key

of the billing orders from method SAVE and exports it.


You activate the generation of demand-driven billing order during the transfer of EDRs

in Customizing for Contract Accounts Receivable and Payable under Integration –>

Billing in Contract Accounts Receivable and Payable –> Billing –> Settings for

Demand-Driven Billing –> Define Demand-Driven Billing for EDRs.

If you do not use this table, demand-driven billing orders are not generated during the

transfer of EDRs. You do not have to change the functions for transferring customer-

specific EDR categories.

If you do edit this table, demand-driven billing orders can be generated during the

transfer of EDRs. In this case, you have to change all functions for transferring

customer-specific EDR categories.

Business Function Contract Accounts A/R and A/P: 02

FICAX_CI_2: Contract Accounts Receivable and Payable, 02 (New)

Use

As of SAP ERP 6.0, Industry Extension Contract Accounts Receivable and

Payable, Enhancement Package 4, you can use the business function FICAX_CI_2.

You can use this business function to:

o Reflect reductions of withholding tax that is to be withheld, and to directly enter

the percentage, base amount, and tax amount in line items for withholding tax

that you withhold

o Bill for payment card payments using parallel processing

o Use the BIC and IBAN in payment lots instead of the bank number and bank

account number

o Use preselection of master data in the payment run

o Levy Bollo for customers with tax exception (country-specific for Italy)

o Calculate inflation surcharges and/or installment plan surcharges when creating

an installment plan; specify the percentage amount of the total amount that is

used for the first installment; and calculate interest on original items up to the

start date of the installment plan (or any other date of your choice)

o Return receivers of information container entries with up to 60 characters

o Use new enterprise services in the areas of external cash desk services and

submission to collections

o Process deposits, withdrawals and cash desk differences of external cash desks;

enter G/L postings and down payments to external cash desks or branches in

expanded form; determine the cash balance of external cash desks using the

SAP Exchange Infrastructure (XI); use enhancements in the monitor for external

cash desk services

o Simulate responsibilities in Collections Management; replace champion

strategies in master data with challenger strategies; create additional users for

Collections Management; use standing worklists, for which the system

automatically adds new work items

o Run reports for installment plans for a certain key date and save this information

o Archive inbound data from external cash desks, installment plan data for a key

date, event-based deferred revenues, and submissions to external collection

agencies

o Enter value ranges for selection in the account balance display for business

partners, contract accounts, contracts, and company codes

o Also use the dunning activity for creating collection work items for dunning using

a dunning procedure

o Use a dunning activity to create collection work items for inbound

correspondence dunning

o Post distribution documents for revenue distribution in a mass run, and use

enhanced revenue distribution in parallel with classic revenue distribution

o In the case of changes to the bank data of a business partner, use changes to

the determination and display of follow-up actions

o Configure the problem class of messages in the application log of mass activities

in Customizing

o Set up an authorization check for processing locks and enter default values for

the duration of the lock

o Post event-based deferred revenues

o Define an explicit value adjustment amount instead of a percentage rate for

doubtful entries and individual value adjustments; and individually designate an

item as doubtful or adjust its value differently in different ledger groups

o In a mass write-off, write off or prevent the write off of individual items by age

and amount grid

o Make account assignment to profit centers not only for expense and revenues,

but also for other line items, such as:

- Postings to bank account, bank clearing accounts, cash accounts

- Postings to receivables accounts, liabilities accounts, and down payment

accounts

- Postings to tax accounts

o During automatic clearing, summarize the items selected for a business partner

or contract account in groups

The system then calls the clearing control per group and can then, when there

are suitable postings, post several clearing documents.

o When creating dispute cases in Contract Accounts Receivable and Payable,

specify that the dispute cases are not processed in SAP Dispute Management,

but are processed instead in an external component

o Integrate the Funds Management (PSM-FM) component of Public Sector

Management with Contract Accounts Receivable and Payable (FI-CA) after FI-

CA is already active

o Make enhanced account assignment of postings to accounts for tax on

sales/purchases

o Process payment slips at cash desks

o Use a new process of check escheatment for checks that were not cashed by

the recipient within a specified time period

o Replace the existing file interface for submitting to collection with enterprise

services, and use the debt recovery score of a business partner to determine the

chances of successfully collecting outstanding payments using external

collection or a legal dunning proceedings

o Use Document Management Service functions for centrally storing and

accessing links between documents and application objects

o Extract payments, returns, revenue distributions, and collection work items for

Business Intelligence (BI)

o Generate earmarked funds documents for standing requests for the current year

o Use Web Dynpro applications for creating correspondence, the Document

Management Service, customer contacts and the contact history


o Clearing and Posting

o Payment Cards

o Processing Incoming and Outgoing Payments

o Payment Transactions

o Country-Specific Development: Italy

o Installment Plan

o Information Container

o Enterprise Services

o External Cash Desk Services

o Collections Management

o Closing Operations

o Archiving

o Account Balance Display

o Dunning

o Inbound Correspondence Dunning

o Distribution of Revenues

o Master Data

o Mass Activities

o Processing Locks

o Deferred Revenues

o Doubtful Entries and Individual Value Adjustments

o Write-Off

o Enhanced Use of Profit Centers in Contract Accounts

Receivable and Payable

o Automatic Clearing

o Integration

o Enhancements to Account Determination

o Enhanced Account Assignment of Tax Items

o Cash Desk

o Check Escheatment

o Submit for Collection

o Document Management Service

o New Events in Contract Accounts Receivable and Payable

o Extraction of Payments

o Extraction of Returns

o Extraction of Revenue Distribution

o Extraction of Work Items

o Standing Orders

o New Web Dynpro Applications

See also

For more information, see SAP Library under SAP ERP -> SAP Contract Accounts

Receivable and Payable (FI-CA).

Posting and Clearing

Use

Postings and Documents: Withholding Tax Supplements with Negative Percentage

Rate

As of SAP ECC 6.0, Enhancement Package 4, you can also define negative

percentage rates for withholding tax supplements. This enables you to reflect

reductions in the actual withholding tax to be withheld. However, you cannot use

negative percentage rates if you enter the values directly in the document. (For

information on direct entry, see the next section.)

Postings and Documents: Variable Specifications for Withholding Tax/1099

As of SAP ECC 6.0, Enhancement Package 4, you can specify the percentage rate,

base amount, and tax amount directly in the line item for withholding taxes. These

specifications are always at the level of a withholding tax supplement.

The enhancement enables you to effect withholdings at the level of the business

partner item.

Functions of the Previous Versions

Currently you can already reflect several withholding tax deductions in parallel. To do

this you use the withholding tax supplements. On payment, you can post one

withholding for the withholding tax code, and a further withholding for each combination

of withholding tax code/withholding tax supplement. The amounts are determined

exclusively using the gross or net amount of the open item and the calculation rules

defined in Customizing.

Detailed Functions As of EhP4

As of SAP ECC 6.0, Enhancement Package 4, for each combination of withholding tax

code/withholding tax supplement, you can define in Customizing whether:

o The percentage rate is specified individually for each line item

o The base amount is specified individually for each line item

o The tax amount is specified individually for each line item

You can also select whether the withholding tax supplement must be specified for a line

item, or whether this specification is optional.

For all details that are not marked for individual specification, the system calculates, as

before, using the existing rules.

The remaining details are stored as a supplement to the line item and used when the

withholding tax is calculated at the time of payment.

Withholdings Only with Directly Defined Values

You can only define the withholdings for a withholding tax supplement directly; the

system calculates the withholding for the withholding tax code using the rules in

Customizing. If you want to work exclusively with variable withholdings, you have to

make sure that nothing is withheld for the withholding tax code itself. You can do this by

defining a tax rate of 0% or by defining the portion subject to tax as 0%.

If you only define a tax rate of 0%, no line item is created, but an entry is made in the

table with the reporting data for the withholding tax (DFKKQSR). If you define a portion

subject to tax of 0%, the system does not create an entry.

Manual Entry of Documents

When you enter a line item for a contract account and the following prerequisites are

met, after you enter the line item, the withholding tax code from the contract account is

set automatically and, following the withholding tax code, a pushbutton appears that

you can use to enter the details of the withholding tax supplements:

o A withholding tax code is defined in the contract account for own withholdings.

o The main/subtransaction used permits withholding tax withholdings.

o The withholding tax code defined in the contract account permits variable

specifications per item.

Supplements for 1099 Reporting (USA)

For withholdings for outgoing payments that have to be declared in a form 1099, you

have access to relevant data in table DFKK1099. The recording of the data is

controlled by function modules that you have to register for events 1970 and 1971.

Event 1970 has been enhanced such that the new return parameter

E_SPLIT_SUPPLEMENTS specifies whether separate records are to be recorded for

each withholding tax supplement. You should select this option if you create

withholding tax codes and withholding tax supplements such that

o Each 1099 form corresponds to a withholding tax code

o Each amount field on the form corresponds to a withholding tax supplement

o In this case, in Customizing you can specify an explanation for the combination

of withholding tax code/withholding tax supplement that identifies the form and

the field on the form. As of SAP ECC 6.0, Enhancement Package 4, the following

information is added to the data recorded in table DFKK1099 (the system stores

this information for each withholding tax supplement separately):

o QSSEW - Key of the withholding tax supplement

o STPRZ - Withholding tax percentage rate

o SBASH - Withholding tax base amount

Irrespective of the type of recording, the new field AUGBD Posting Date of Clearing

or Clearing Reset is always set.

Open Item Processing – Subtotals when Filtering

In the user-specific settings, you can define that a subtotal is displayed after the items

determined when you filter items.

Example: If you filter using the reference number, and search for all items with

reference number 4711, the total is displayed beneath the items found.

By double clicking the gross amount in the totals line, you can activate or deactivate all

filtered items. By double clicking on the cash discount amount, you can activate or

deactivate the cash discount for all filtered items.


Postings and Documents: Variable Specifications for Withholding Tax

You can specify withholding tax supplements so that you can make variable

specifications for each line item. In Customizing for Contract Accounts Receivable and

Payable, choose Basic Functions -> Withholding Tax -> Define Withholding Tax Supplement.

Payment Cards

Use

Payment Card Billing: Parallel Online Billing

Until now, the billing of payment card payments always took place using report

RFKKPCDS (on the SAP Easy Access screen under Periodic Processing -> Data for

Externals -> Payment Card Organizations -> Settle). This report does not use

parallel processing. It creates a file with the selected payments.

As of SAP ECC 6.0, Enhancement Package 4, you also have the option of using

parallel processing for billing payment card payments (as a mass activity). On the SAP

Easy Access screen, choose Periodic Processing -> Data for Externals -> Payment

Card Organizations -> Parallel Billing by Direct Call. The system does not create a

file when you use this variant. Instead a new event (1421) is made available for the

payments being settled. The payments are grouped by card institute, company code,

agent ID, currency and value date. The new event allows online billing with immediate

return of the result (that is, billing was successful or unsuccessful, with the appropriate

error message). The system stores any errors that occur. The errors are displayed in

the document display for the payment document. The mass activity can select

payments with errors, in addition to the payments for billing. These payments with

errors are payments for which billing was unsuccessful during the last attempt.

The system stores the results of the billing run in the existing log tables under the ID of

the mass activity.

The parallel processing object for this mass activity is the Subarea (KEYPP) field. You

have to add this field to the table of payment card data (DFKKOPKC) beforehand using

a prepared enhancement using report RFKK_ENH_CCARD.


Include the Subarea (KEYPP) field in the table of payment card data (DFKKOPKC) in

Customizing for Accounts Receivable and Payable by choosing Program

Enhancements -> Prepared Enhancements -> Prepare Parallel Processing

for Payment Card Data.

Processing of Incoming and Outgoing Payments

Use

As of SAP ERP 6.0, Enhancement Package 4 (Release 6.04), you can now use BIC

and IBAN both in payment lots and in transfer programs for creating payment lots. You

can use BIC and IBAN, which are commonly used in international payment

transactions, rather than the bank number and bank account number.

When you search for payments in the payment lot, you can use the IBAN as a search

criterion in addition to the bank account number.

Payment Transactions

Use

Payment Run: Use of Preselections for Business Partners or Contract Accounts

As of SAP ECC 6.0, Enhancement Package 4, you can now also use preselections for

master data in the payment run to select business partners or contract accounts.

Up to now you could use these selections in the items list, for example (see Periodic

Processing -> Open Item Evaluations -> Execute Evaluation).

To create preselections, on the SAP Easy Access screen, choose Technical

Preparation -> Define Preselection and create a set of master data using any master

record attributes, for example, all business partners with an address in Chicago.

The system then checks the master records specified in the preselection against the

interval limits of the mass activity as if they had been entered as individual values for

business partner/contract account so that in each interval, only those master records

are processed that are in the interval limits and the preselection.

Payment Run: Set Paying Contract Account

At event 0663, you can override the paying contract account from the master record of

the contract account. For detailed information, see the documentation of the sample function module .


Define event 0633 to meet your needs in Customizing for Contract Accounts

Receivable and Payable under Program Enhancements -> Define Customer-

Specific Function Modules.

Country-Specific Development: Italy

Use

As of SAP ECC 6.0, Enhancement Package 4, you can levy Bollo for customers with a

tax exception.

The system always posts Bollo if the total of the items excluded from tax and the Bollo-

relevant items exceeds the amount of EUR 77.47. It is irrelevant whether it is a debit or

credit item. Only the absolute amount is decisive. The bollo amount is EUR 1.29.

Bollo is can be levied for the following items that are excluded from tax.

o Cash security deposits

o Interest

o Items that would otherwise be taxed but that are excluded from tax for a specific

customer group (tax exception)

Bollo cannot be reversed. This also means that the reversal of a Bollo-relevant posting

does not reverse the Bollo posting.

Bollo is only posted from the FI-CA programs if function module

FKK_CHECK_CALC_BOLLO_INTERN is registered for event 0100 (see Customizing

for Contract Accounts Receivable and Payable: Program Enhancements -> Define

Customer-Specific Function Modules).


You define the system settings for posting stamp tax (Bollo) in the Implementation

Guide for Contract Accounts Receivable and Payable under Basic Functions ->

Special Features of Tax Processing -> Stamp Tax (Bollo) (Italy).

Installment Plan

Use

Installment Plan Enhancement for Surcharges/Interest

As of SAP ECC 6.0, Enhancement Package 4, you can use the following installment

plan enhancements for surcharges and interest:

o When creating an installment plan, you have the option of calculating inflation

surcharges and/or installment plan surcharges (either manually or automatically). (See the IMG activities Define Categories for Installment Plan and Define

Charge Categories for Installment Plan Surcharges.)

At event 3033, you can influence the main transaction and subtransaction, as

well as the charge amount, dependent on the surcharge category.

o When creating an installment plan, you have the option of having the system

calculate interest on original items up to the start date of the installment plan

(default value) or up to any point in time you choose.

o When creating an installment plan, you can specify the percentage amount of the

total amount that is used for the first installment, thereby specifying the amount

of first installment. The remaining amount is then distributed accordingly over the remaining installments. (See the IMG activity Define Categories for Installment

Plan.)

The following functions are also available for processing installment plans:

o When creating an installment plan, you can include partial amounts.

o In addition to the installment plan interest calculation (from the start date to the

due dates of the installment plan), you can trigger an interest calculation on

original items up to the start date of the installment plan. (See the IMG activity

Define Categories for Installment Plan.)

o You can specify a clearing type for clearing original installment plan items (see

the IMG activity Define Categories for Installment Plan). The system uses this

clearing type for distributing a clearing amount to the original items of this

installment plan.


You can make the following settings in Customizing for Contract Accounts Receivable

and Payable under Business Transactions -> Deferral and Installment Plan:

o Define Categories for Installment Plan

In this activity, for each installment plan category you define whether:

- There should be an additional item interest calculation up to the start date

- A special clearing type is to be used for clearing installment plan original

items

- The first installment is to be determined on a percentage basis

- The charges categories defined are to be used for installment plan

surcharges and whether these are to be triggered manually or

automatically

o Define Charge Categories for Installment Plan Surcharges

In this activity you define the charge categories for the installment plan

surcharges.

Information Container

Use

As of SAP ECC 6.0, Enhancement Package 4, you can use the following

enhancements for information containers:

o If the receivers of information container entries are already known when the

entries are created, then you can enter these using event 3701. Until now, the a

maximum length of receiver values was three characters. Now you can return

receivers with a length of up to 60 characters. Implementations that have the old

structure remain valid; however, there are the following changes:

- In event 3701, for the reference type for the export parameter

ET_RECEIVERS, you can also use INFCOREC_KK_T instead of R

CVER_KK_T.

- In events 3702, 3703 and 3704, for the reference type for the import

parameter IV_RECEIVER, you can now use INFCOREC_KK_T instead of

RCVER_KK_T.

- In interface IF_FKK_INFCO_TYPE, which you use when creating your

own information container categories, the methods GET_DATA_SEND

and SEND_VIA_XI each now also contain the new, optional import

parameter IV_RECEIVER_LONG.

- The existing import parameter IV_RECEIVER remains unchanged, for

reasons of compatibility.

o The method GET_DATA_STORE of interface IF_FKK_INFCO_TYPE, which you

use when creating your own information container categories, was enhanced by

adding export parameter ET_DATA_RECEIVER. Using this parameter, you can

enter the receiver of information container entries. You can now thereby enter

the receivers for your own information container categories directly in the method

GET_DATA_STORE instead of in event 3701.

Enterprise Services

Use

As of SAP ERP 6.0, Enhancement Package 4, in Contract Accounts Receivables and

Payable, you have access to new Enterprise Services as XI interfaces.

The Enterprise Service Repository contains the following XI interfaces for software

component FI-CA under FI-CA 604 -> http://sap.com/xi/FICA/Global2 -> Service

Interfaces:

o Dunning:

- ContractAccountReceivablesPayablesDunningNoticeERPByBusinessPart

nerQueryResponseIn

- ContractAccountReceivablesPayablesDunningNoticeERPByIDQueryResp

onse_In

o Subscription/Clearing Notification:

- ContractAccountReceivablesPayablesRegisterERPReferenceSubscription

Request_In

- ContractAccountReceivablesPayablesRegisterERPSubscribedItemBulkNo

tification_Out

o ReceivablesPayablesRegister:

ContrAcctRblsPyblsRegERPItemBusTransacDocRefByBaseBusinessTransactio

nDocumentReferenceQueryResponse_In

At the moment you can only use this service if you use the Insurance industry-

specific component.

o Account balance :

ContractAccountERPSplitItemGroupByElementsQueryResponse_In

o PaymentReturn : PaymentReturnERPOccuredBulkNotification_Out

o Contract Account:

- ContractAccountERPSplitItemGroupbyElementsQueryResponse_In

- Contract Account Down Payment Request

- ContractAccountDownPaymentRequestERPCreateRequestConfirmati

on_In

You also have access to Enterprise Services as part of the External Cash Desk

Services (see Release Note for External Cash Desk Services) and

Submissions for External Collection (see Release Note for Submissions for

Collection).

Changed Interfaces

In the Enterprise Service Repository for software component FI-CA under FI-CA 604

-> http://sap.com/xi/FICA/Global2 -> Service Interfaces the following XI interfaces

have been changed:

ContractAccount

The XI interfaces

ContractAccountERPReceivablesPayablesRegisterItemByIDQueryResponse_In

and ContractAccountERPSplitItemGroupByBusinessPartnerIDQueryResponse_In

have been changed as follows: Addition of a selection option by posting date and the

possibility to restrict the results set.

External Cash Desk Services

Use

As of SAP ERP 6.0, Enhancement Package 4 (Release 6.04), you can use the

following functions as part of external cash desk services:

o Process deposits, withdrawals and cash desk differences of external cash desks

o Enter G/L postings and down payments to external cash desks or in branches in

expanded form

o Check the cash balances of external cash desks and payment collectors

(branches)

The functions of the cash journal are not changed by these enhancements. In the cash

journal, you can continue to make cash journal entries directly in the SAP system as

before. This means that you can enter payments directly in the system and run reports

on them, as well as create follow-on postings in the cash balance, such as, deposits,

withdrawals, differences and reversals.

The external cash desk services make the following enterprise services available,

whereby the transfer of data between the SAP system and the external cash desk

system can be synchronous or asynchronous using the SAP Exchange Infrastructure

(XI).

o CashPointDepositERPNotification

The CashPointDepositERPNotification service is an asynchronous process

that sends deposits to external cash desks to FI-CA.

o CashPointDepositERPCancellationNotification

The CashPointDepositERPCancellationNotification service is an

asynchronous process that sends reversals of deposits to external cash desks to

FI-CA.

o CashPointDifferenceERPNotification

The CashPointDifferenceERPNotification service is an asynchronous process

that sends difference postings made to an external cash desk to FI-CA.

o CashPointDifferenceERPCancellationNotification

The CashPointDifferenceERPCancellationNotification service is an

asynchronous process that sends reversals of difference postings made to

external cash desks to FI-CA.

o CashPointWithdrawalERPNotification

The CashPointWithdrawalERPNotification service is an asynchronous

process that sends withdrawals from external cash desks to FI-CA.

o CashPointWithdrawalERPCancellationNotification

The CashPointWithdrawalERPCancellationNotification service is an

asynchronous process that sends reversals of withdrawals from external cash

desks to FI-CA.

o CashPointPaymentCreateNotification

The CashPointPaymentCreateNotification service is an asynchronous process

that sends G/L account postings made to an external cash desk to FI-CA.

o CashPointPaymentReverseNotification

The CashPointPaymentReverseNotification service is an asynchronous

process that sends reversals of G/L account postings made to external cash

desks to FI-CA.

o CashPointERPBalanceByIDQuery

The CashPointERPBalanceByIDQuery service is a synchronous process that

requests the cash balance of an external cash desk or an external payment

collector (branch).

o CashPointERPBalanceByCashPointOfficeIDQuery

The CashPointERPBalanceByCashPointOfficeIDQuery service is a

synchronous process that requests the cash balance for individual external

payment collectors (branches).

For offline branches and agents, SAP makes the following XI messages available for

postings to G/L accounts and in the cash journal, as well as for reports on the cash

balance.

o G/L account postings: CashPointPaymentCreateNotificationService

o Posting of deposits: CashPointDepositERPNotificationService

o Posting of withdrawals: CashPointWithdrawalERPNotificationService

o Posting of differences: CashPointDifferenceERPNotificationService

For the inbound XI messages, the FI-CA system attempts to generate the postings

directly. The FI-CA system assigns status R to postings that it is not able to generate

directly.

For these failed G/L account postings, the system creates a payment lot, which you can

then close and post in the monitor. If a lot receives Postprocessing status after

posting has taken place, you later have to clarify the payment lot items involved.

External cash desk services now also support the reversal of postings that were sent

using XI. The SAP system receives the XI messages and posts the reversal directly in

FI-CA.

Reversals that the system cannot make directly receive status D. The following

enterprise services are available:

o Reversal of G/L account postings:

CashPointPaymentReverseNotificationService

o Reversal of deposits: CashPointDepositERPCancellationNotificationService

o Reversal of withdrawals:

CashPointWithdrawalERPCancellationNotificationService

o Reversal of difference postings:

CashPointDifferenceERPCancellationNotification Service

Cash Balance

You can now determine the cash balance of external cash desks using the SAP

Exchange Infrastructure (XI).

Enhancement of Monitor for External Cash Desk Services

Using the monitor for external cash desk services, you can now also manage and track

postings and cash balances that you receive by means of the SAP Exchange

Infrastructure. On the SAP Easy Access screen, choose Payments -> External Cash

Desk Services -> Monitor External Cash Desk Services. The monitor provides you,

for instance, with access to deposits, withdrawals and difference postings, G/L account

postings, and cash balances for external payments. You can select data at the level of

the external cash desk or agent, using the extended selection criteria.

You can process postings in the cash journal and cash balances on the following new

tab pages:

o Cash Journal Operations

Here you can display information on all postings in the cash journal, along with

their status. In addition, you can repeat the posting for postings that were not

successful, or set their status to Manual Postprocessing Required. After

manual posting has taken place, you can set the status Manual Clarification

here. You can also update all postings received using enterprise services.

o Cash Balance

The tab page shows the cash balance for all postings. You can check the cash

balance at two different levels - for the branch or for the cash desk of a branch.

The Overview, XI Monitor and Payments tab pages contain the following

enhancements:

o Overview

Here you can select the grouping key and master data by date or by date

intervals.

Selecting by master data returns all payments and G/L account postings with

their status when you specify the agent or the cash desk.

Selecting by grouping key returns the status of all grouping keys.

If the status is not correct, you can repeat the posting here to correct the error.

Then you can display the new status by updating.

o XI Monitor

Here you can now navigate directly to the XI message for new message

categories.

o Payments

You can now obtain more information on G/L account postings.

Integration with Incentive and Commission Management (ICM)

As of SAP ERP 6.0, Enhancement Package 4 (Release 6.04), you can implement

Incentive and Commission Management (ICM) for agent postings as part of external

cash desk services.

If you have agents who process incoming payments, you can benefit from the

integration of Incentive and Commission Management (ICM) with Contract Accounts

Receivable and Payable for calculating agent commissions. Commissions can be

calculated, for example, on the total value of collected payments or on the number of

processed payments.

The prerequisite for using this integration is that you are already using the Incentive

and Commission Management (ICM) component. If you then activate the integration

in Customizing of Contract Accounts Receivable and Payable, the system transfers the

appropriate payment data to the ICM system automatically. As a result, you can

calculate the agent commissions (using the timing that suits you), and transfer the

billing data back to the FI-CA system. The FI-CA system then automatically posts a

credit to the agent's account.

These are the steps:

1. You post all incoming payments in FI-CA under a grouping key.

2. As part of closing the cash desk in FI-CA, for instance at the end of the business

day, you close the grouping key.

3. After closing the cash desk successfully, you use the Post Agent Receivable

transaction (on the SAP Easy Access screen, choose Payments -> External

Cash Desk Services) to post the receivables to the agent accounts.

If integration with Incentive and Commission Management is active, the

system automatically transfers the data entered under the grouping key to the

ICM system.

1. In the ICM system, you calculate the commission due to the agents for each

grouping key. You can choose how often you want to make this calculation

(daily, weekly, monthly).


These options are now available in Customizing for Contract Accounts Receivable and

Payable under Business Transactions -> Payments -> Processing of

Incoming/Outgoing Payments -> External Cash Desk Services:

Make Specifications for Posting Cash Desk Deposits and

Withdrawals

Define Accounts for Expense/Revenue from Cash Desk Differences

Define Specifications for Agent Commissions

You can activate the integration with Incentive and Commission Management (ICM)

in the activity Define Master Data for External Cash Desk Services by

setting the Comm.Act. indicator for the affected branches.

Collections Management

Use

As of SAP ECC 6.0, Enhancement Package 4, the following new functions are

available in Collections Management.

Simulation of Responsibilities

In the context of dunning by collection strategy, you can use the dunning program to

generate work items. These work items are automatically assigned to the responsible

department, and you also have the option of assigning them to a responsible unit

(team) or responsible collections specialist.

When configuring the derivation of responsibilities in Customizing, you could previously

only test your settings for each of the three levels. Using the new transaction Simulate

Responsibilities, you can simulate the derivation of the three levels in one step using

data from dunning. This means that the test directly follows the flow of the dunning

program (see SAP Easy Access screen: Periodic Processing -> For Contract

Accounts -> Dunning -> Areas of Responsibility).

No additional Customizing settings are necessary.

Champion and Challenger Strategies

For dunning by collection strategy, you can define challenger strategies that can

replace the collection strategies (champion strategies) defined on the master data.

To do so, you have to create a test series. On the SAP Easy Access screen, choose

Periodic Processing -> For Contract Accounts -> Dunning -> By Collection

Strategy -> Process Test Series for Strategy Replacement. There you can specify

the percentage of master data that you want to be affected by the replacement. You

can evaluate the valid test series and thereby specify the master data that is actually

affected. On the SAP Easy Access screen, choose Periodic Processing -> For

Contract Accounts -> Dunning -> By Collection Strategy -> Determine Master

Data for Test Series.

At event 1038 you can exclude certain master data from challenger strategies. You can

also choose to implement your own logic for determining the affected master data. In

that case, enter your test series without entering percentages. Instead of the of the

transaction for determining the master data, use your own report to fill database table

DFKKCCMD.

The dunning proposal run considers the entries in table DFKKCCMD and makes the

strategy replacement. The system stores one replacement in the dunning history.

Create Additional Users for Collections Management

You can create (external) employees, who are not assigned to any collections

department in organizational management, as additional managers of a collections

department or collections unit. To do so, on the SAP Easy Access screen, choose

Periodic Processing -> For Contract Accounts -> Dunning -> Areas of

Responsibility -> Define Additional Department or Group Head.

You can create (external) employees, who are not assigned to any collections

department in organizational management, as additional collection specialists. To do

so, on the SAP Easy Access screen, choose Periodic Processing -> For Contract

Accounts -> Dunning -> Areas of Responsibility -> Define Additional Collection

Specialist.

The transactions for managing worklists in Collections Management and in Financial

Customer Care (FCC) are processed in events 2857 and 2858. In the standard system

these events determine the data that was entered in the transactions mentioned.

Standing Worklists

Standing worklists are available as a new type of worklist. With this type of worklist, the

system can automatically add new work items, as long as certain criteria, such as the

collections unit or work item category are filled. Standing worklists always remain open

and do not have an end date.

You can implement customer-specific classification criteria for worklists in event 1037.

In addition, you can implement default settings for certain worklist attributes in event

1036.

The transaction for managing worklists in Collections Management (SAP Easy Access

screen: Periodic Processing -> For Contract Accounts -> Dunning) was modified

for managing standing worklists and a new organizational view was added.


To enable the dunning run to create standing worklists, you have do define the creation

of worklists with the attribute Automatically As Standing Worklist. In Customizing for

Contract Accounts Receivable and Payable, choose Business Transactions ->

Dunning -> Worklists and Work Items -> Define Work Item Categories.

Closing Operations

Use

As of SAP ECC 6.0, Enhancement Package 4, you can run reports for installment plans

in Contract Accounts Receivable and Payable for a certain key date, creating a

snapshot of the installment plan due dates on this key date, as well as ensuring the

assignment of these due dates to the original items. On the SAP Easy Access screen,

choose Periodic Processing -> Closing Preparations -> Record Status of

Installment Plans for Key Date.

The open item list takes this report into account if the appropriate setting is made (see

SAP Easy Access screen: Periodic Processing -> Closing Preparation -> Open

Items at Key Date).

You can run the report either as a simulation or an update run. In an update run, the

report always runs using at least one company code. For simulation runs, you can limit

the selection to individual business partners.

The system stores the installment plan due dates starting from the date entered in the

selection criteria. The system does not store installments that are older than that.

If you want to make your own assignment of due dates to the original items, you can

use event 1882.

Archiving

Use

As of SAP ECC 6.0, Enhancement Package 4, the enhancements listed below related

to archiving are available in Contract Accounts Receivable and Payable.

New Archiving Object: Recording of Installment Plan Data for Key Date

Using the new archiving object FI_MKKIPL, you can archive installment plan data that

you stored for a key date. The prerequisites for archiving are described in the

documentation of report RFKKIPLAR01 (see SAP Easy Access screen: Periodic

Processing -> Archive Data).

New Archiving Object: Event-Based Deferred Revenues

With the new archiving object FI_MKKDRE you can archive data for event-based

deferred revenues. The prerequisites for archiving are described in the documentation

of report RFKKDREAR01 (see SAP Easy Access screen: Periodic Processing ->

Archive Data ).

New Archiving Object: Submission to External Collection Agencies

Using the archiving object FI_MKKCOLD, you can archive data that you stored in

conjunction with submissions of receivables to external collection agencies. The data

meant here is the data that arises due to exchanges with an external collection agency

or due to legal dunning procedures. The prerequisites for archiving are described in the

documentation of report RFKKCOLDAR01 (see SAP Easy Access screen:

Periodic Processing -> Archive Data ).

New Archiving Object: Inbound Data from External Cash Desks (Inbound Services)

You can archive inbound data from external cash desks with the new archiving object

FI_MKKEXCJ. The prerequisites for archiving are described in the documentation

of report RFKKEXCJAR01 (see SAP Easy Access screen: Periodic Processing

-> Archive Data).

Enhancement to Document Archiving (Archiving Object FI_MKKDOC)

When archiving documents, the system now automatically archives table DFKKOPAA

(distribution items with account assignment).

Enhancement to Check Archiving (Archiving Object FI_MKKCREG)

When archiving checks, the system now also automatically archives escheatment data

for check management in database tables

DFKKCRESCH and DFKKCRESCHA.

Enhancement to Archiving of Revenue Distribution (Archiving Object FI_MKKREVD)

When archiving data for revenue distribution, the system now also automatically

archives database tables DFKKRDI_RATE and DFKKRDI_AGGRF.

Enhancement to Archiving of Convergent Invoicing (Archiving Object FI_MKKTHI)

When archiving data for convergent invoicing, the system now also automatically

archives database table DFKKTHI_HIST2. For table DFKKTHI_HIST2, also create a

database index during archiving, as described in the documentation for

RFKKTHPAR01.

Enhancement to Archiving of Collection Items (Archiving Object FI_MKKCOLL)

When archiving collection items, the system now also automatically archives database

table DFKKCOLLEXTH.


You enter the archiving lives and activate the respective archive information structure

for the following archiving objects in Customizing for Contract Accounts Receivable and

Payable by choosing the paths below:

o Storing installment plan data for a key date (FI_MKKIPL)

Choose Closing Operations -> Archiving

o Event-based deferred revenues (FI_MKKDRE)

Choose Business Transactions -> Deferred Revenue Postings -> Archiving

o Submission to external collection agencies (FI_MKKCOLD)

Choose Business Transactions -> Submit to Collection Agency -> Archiving

o Inbound data from external cash desks (Inbound Services) (FI_MKKEXCJ)

Choose Business Transactions -> Payments -> Processing of

Incoming/Outgoing Payments -> External Cash Desk Services -> Archiving

Account Balance Display

Use

Enhanced Selection

As of SAP ECC 6.0, Enhancement Package 4, you can enter value ranges for the

selection of business partners, contract accounts, and company codes. You can select

relationships between master data, such as business partner relationships, in dialog

mode. For business partner relationships, you can limit the number of relationship

types that are offered by making settings in Customizing.

Saving the Selection

You can save selection parameters for master data and company code with a name.

This can be user-independent or user-specific.

New Balances

In Customizing, you can configure balances categories that contain all items with

certain main and subtransactions.


You specify the business partner relationship types, which you do not want offered for

selection, in Customizing for Contract Accounts Receivable and Payable under Basic

Functions -> Account Balance Display -> Exclude Business Partner Relationship Types.

You can enter main and subtransactions that you want to assign to a balances

category that you define. In Customizing choose Basic Functions -> Account

Balance Display -> Balances Variants -> Define Balances Categories.

Dunning

Use

As of SAP ECC 6.0, Enhancement Package 4, you can also use the dunning activity for

creating collection work items for dunning by dunning procedure. The master data

group contains the contract account (the contract) if the contract account (the contract)

is a criterion for the dunning grouping.

Dunning Inbound Correspondence

Use

As of SAP ECC 6.0, Enhancement Package 4, there is a new dunning activity for

creating collection work items that you can use for inbound correspondence dunning.

The master data group contains the contract account or the contract. You cannot

create enforcement work items using this dunning activity.

SAP provides the dunning activities FKK_0746_WLI_CREATE_AND_CLOSE and

FKK_0746_WLI_CLOSE.

Distribution of Revenues

Use

Mass Activity for Distribution Posting

As of SAP ECC 6.0, Enhancement Package 4, you can use the Post Distribution

Documents transaction in the SAP menu under Periodic Processing -> For Contract

Accounts -> Revenue Distribution as a mass activity. If you are using Contract

Accounts Receivable and Payable with Enhancement Package 4, as standard the

system automatically calls up transaction FP60PM when you run the Post Distribution

Documents transaction.

Report RFKKRD00 Revenue Distribution: Create and Post Documents, which was

used up to now, continues to be available in transaction FP60P_OLD. Note however,

that you can no longer use report RFKKRD00 for enhanced revenue distribution. The

only report that now supports this function is the mass activity Post Distribution

Documents.

Enhanced Revenue Distribution

You can use the enhanced revenue distribution in parallel with classic

revenue distribution.

In the standard system, with enhanced revenue distribution, you distribute assigned

payments (receivables items cleared by payment). However, you can also distribute

unassigned payments (payments on account with a subtransaction designated as

payment-relevant) and expected revenues (still open line items but not including

assigned payments). For expected revenues and unassigned payments, the system

runs an estimated distribution. The user estimates the distribution ratios of the final

recipients in advance. In contrast, the system always distributes assigned payments as

final, since the user can determine the distribution ratios uniquely in advance.

The system supports distribution of each receivables item to several final recipients.

Using report RFKKRDI_AGGR, you can create aggregated distribution information

(see SAP menu: Periodic Processing -> For Contract Accounts -> Revenue

Distribution -> Create Aggregated Distribution Information). For more information,

see the report documentation.

You can also extract distribution information for Business Intelligence (BI) (see SAP

menu: Periodic Processing -> Extraction for Business Intelligence -> Extract

Revenue Distribution Items). Report RFKKRDI_BW executes the delta extraction

to BI.

Technical Basics

Enhanced revenue distribution is based on a different technical concept than classic

revenue distribution. For example, in enhanced revenue distribution, the final recipients

and their respective distribution portions for receivables items must already be created

and exist in the table of distribution information (DFKKRDI_RATE) before you can start

the revenue distribution process in Contract Accounts Receivable and Payable. The

distribution information is linked to the line items (DFKKOP) using the distribution key - a GUID that is contained in the table of distribution information and in the line

items. For event 5440, you define which line items are distributed using enhanced


The following applies to the information for the final recipient and the corresponding

distribution ratios:

For assigned payments and expected revenues, you have to define the final recipient

and distribution ratios before the revenue distribution process and write them to the

table of distribution information (DFKKRDI_RATE) together with the distribution keys

created. The distribution key must be inherited by the receivables items (field DISKEY

in table DFKKOP). You have to create an implementation for this in a customer project.

To add the distribution information, you can use function module

FKK_RDI_RATE_INSERT.

Note for the industry component Public Sector Contract Accounts Receivable

and Payable

To add the distribution information, you can use the Business Rules Framework

(BRF). SAP provides the BRF object TRM_TEMPLATE_OBJECT with the

implementing class 0TRMRD001. With an appropriate implementation of this class,

you can determine the distribution information required.

For unassigned payments, the final recipient and distribution ratios are defined at event

5420, which is called by the revenue distribution mass activity (FP60M). The corresponding distribution key is not inherited by the payables items (in table

DFKKOP), it is only noted in the distribution table (DFKKRDI).

Note that an original line item can only be distributed in one way - either with classic

revenue distribution or enhanced revenue distribution. If, for one original line item, data

is defined for both classic and enhanced revenue distribution, the classic revenue

distribution overrides the enhanced revenue distribution. Therefore, make sure that in

the classic revenue distribution, you do not automatically derive the final recipient for

the line items that you want to distribute with enhanced revenue distribution.

Enhanced revenue distribution is based on distribution groups and distribution

periods. A current distribution period must be assigned to each distribution group.

Prerequisites

If you want to use enhanced revenue distribution, the following prerequisites must

be fulfilled.

Events

Using event 5440 you can define whether an item is distributed. The system calls the

event when you post a document.

Using event 5420, you can estimate the distribution ratios for unassigned payments.

The event is called in the mass activity Revenue Distribution.

Evaluation of Revenue Distribution

You can analyze revenue distributions using the following evaluation reports with their

different output options:

o Report RFKKRDI_REPORT (transaction FP60R_NEW) for the analysis of

revenue distribution based on original documents (see SAP menu: Account ->

Further Information -> Evaluation of Revenue Distribution (Original

Document)). Note that if you use Contract Accounts Receivable and Payable

with Enhancement Package 4, transaction FP60R calls up transaction

FP60R_NEW as standard automatically. Report RFKKRD01 List of Distributed

Revenues is still available using transaction FP60R_OLD.

o Report RFKKRDI_REPORT_DIS for the analysis of revenue distribution

based on distribution documents (transaction FP60R1) (see SAP menu:

Account -> Further Information -> Evaluation of Revenue Distribution

(Distribution Document)).

Simulated Assigned Payments for Classic Revenue Distribution

Using the Revenue Distribution (FP60M) transaction, you can use the Simulate

Assigned Payments option. This means that open receivables items are

simulated as assigned payments (cleared by payment) and corresponding simulation

entries are written to table DFKKRDI (see SAP menu: Periodic Processing -> For

Contract Accounts -> Revenue Distribution -> Distribute Revenues). You can then

use the analysis report RFKKRDI_REPORT to select and evaluate simulated

assigned payments.

Activation of Distribution Documents for Invoicing

The system now supports an activation of distribution documents for Invoicing in

Contract Accounts Receivable and Payable. This means that distribution documents

can be cleared with other documents during invoicing and corresponding invoices can

be created for the recipient.


You make the system settings in Customizing for Contract Accounts Receivable and

Payable under Business Transactions -> Distribution of Revenues -> Enhanced

Revenue Distribution in the following activities:

o Make Settings for Enhanced Revenue Distribution

o Define Distribution Groups

o Define Transaction Determination for Distribution Groups

o Define Distribution Periods

o Define Distribution Periods for Distribution Groups

o Define Specifications for Invoicing

Activate enhanced revenue distribution in Customizing for Contract Accounts

Receivable and Payable under Program Enhancements -> Prepared Enhancements -> Enhanced Revenue Distribution.

Master Data

Use

Changing the Bank Data of a Business Partner

Determining Follow-Up Actions

The system determines the set of rules to be used based on your settings in

Customizing for Contract Accounts Receivable and Payable under Basic Functions ->

Contract Partner -> Changes to Payment Transactions -> Settings for Follow-Up

Actions -> Define Set of Rules for Follow-Up Actions. For determining the set of

rules, the system uses the standard company code of the contract accounts and

contracts that are affected by the change to the payment data.

Once the set of rules is determined, then the system determines the rules dependent

on the current operating mode (display, change, delete).

Displaying Follow-Up Actions

As of SAP ECC 6.0, Enhancement Package 4, the system no longer displays the

follow-up actions in the hierarchy under Company Code Group and Set of Rules, but

instead lists them directly under Company Code. If a follow-up action is assigned to

several sets of rules, and these sets of rules are active in the same company code,

then the system displays the follow-up action only once in each company code.

The system now lists the objects affected by a follow-up action (such as, locks, dunning

notices, or returns) directly under the follow-up action, and independently of the set of

rules.

If you execute a follow-up action, then the system performs the activities for all affected

objects (that are displayed in the dialog).

The system lists a follow-up action only if it can determine at least one affected object

for it.

Processing Locks

Use

As of SAP ECC 6.0, enhancement package 4, for processing locks, you can:

o Define default values for the duration of a lock in Customizing

The system uses the values you enter as the default date if you create a

processing lock without specifying the length of its validity period.

o Use the new authorization object F_KKLCK_BG to check authorization at the

lock reason level

In Customizing, you define an authorization group for the desired lock reasons.

o Perform a customer-specific plausibility check at event 1804 when creating and

changing processing locks


Define the appropriate settings in the Implementation Guide for Contract Accounts

Receivable and Payable as follows:

o Basic Functions -> Postings and Documents -> Basic Settings -> Define

Lock Reasons for Posting Locks

o Business Transactions -> Payments -> Incoming/Outgoing Payment

Creation -> Define Payment Lock Reasons

o Business Transactions -> Interest Calculation -> Item Interest Calculation -

> Define Interest Lock Reasons

o Business Transactions -> Dunning -> Define Dunning Lock Reasons

o Business Transactions -> Inbound Correspondence Dunning -> Define

Correspondence Dunning Lock Reasons

o Integration -> Invoicing in Contract Accounts Receivable and Payable ->

Invoicing -> Invoicing Processes -> Define Lock Reasons for Invoicing

Deferred Revenue Postings


Use

Revenues are posted when a receivables document is posted. These revenues

become effective in the posting period in which they are actually posted. This means

that these revenues are assigned to the posting period in which they are posted. The

regulations in some countries are that revenue accruals/deferrals have to be entered in

the general ledger for revenues that do not become effective until some time in the

future. Revenues become effective in the future, if the service upon which the revenue

is based is actually performed in the future. Recognition of revenues is therefore

independent of invoicing. Revenues and accrued/deferred revenues must be posted to

separate general ledger accounts.

SAP provides functions for time-based deferred revenues as of release 4.51.

For time-based deferred revenues, the time of revenue recognition, including the

amounts to be transferred, are already known at the time of invoicing. Therefore, this

information can be noted already at the time of invoicing. The G/L transfer postings are

created by a mass activity.

As of SAP ECC 6.0, Enhancement Package 4, Contract Accounts Receivable and

Payable provides functions for posting event-based deferred revenues. For event-

based deferred revenues, neither the time nor amount for revenue recognition is known

at the time of invoicing. This means that each event that triggers revenue recognition

must be reported to the SAP system, along with the date and amount.

Use

The functions for event-based deferred revenue use the following four, new database

tables, belonging to three different categories:

o The header table DFKKDEFREV_HEAD contains an entry for each G/L posting

for which the functions for event-based deferred revenue should be used.

o The item table DFKKDEFREV_POS contains the information for the initial

transfer from the revenue account to the G/L account for deferred revenue.

o The trigger tables DFKKDEFREV_TRIG and DFKKDEFREV_TRIGE contain the

information about the reported events (DFKKDEFREV_TRIG: revenue

recognition/DFKKDEFREV_TRIGE: check date) that is processed by the transfer

run for deferred revenues.

Interface

SAP provides the following function modules that you can use to implement the

functions for event-based deferred revenues:

o FKK_DEFREV_BY_EVENT_CREATE

The module registers the desired G/L items when an FI-CA document is posted,

and thereby activates further processing of these G/L items in the context of

event-based deferred revenues.

o FKK_DEFREV_BY_EVENT_RAISE

The module reports the events (with date and amount).

In the standard system, these function modules are called from invoicing. Invoicing

documents arise from billing documents, which in turn can be created using event

detail records (EDRs).

Reporting Events

When an event is reported to the SAP system, the system generates a trigger table

entry (DFKKDEFREV_TRIG/DFKKDEFREV_TRIGE).

The transfer run for deferred revenues processes these entries.

Note

It is possible that an event could be reported for an assignment key, although no

related assignment key exists in the SAP system. In that case, the event is not

processed by the transfer run until the related header entry is available.

Transfer Posting Run

There is a mass activity in Contract Accounts Receivable and Payable that makes the

transfer postings for deferred revenue in the general ledger (on the SAP Easy Access

screen, choose Periodic Processing -> Closing Preparation ->

Receivable/Revenue Adjustment -> Event-Based Deferred Revenues -> Transfer

Posting Run).

The mass activity executes the following steps:

1. The system converts the reported events (entries in tables DFKKDEFREV_TRIG

and DFKKDEFREV_TRIGE) into item entries (DFKKDEFREV_POS). At the

same time, the system adjusts the relevant fields in the table containing the

header entries (BETRA, BETRO, ENDIN, CHCKD in table

DFKKDEFREV_HEAD).

2. Then the system processes the entries in the item table (DFKKDEFREV_POS)

and generates transfer documents. The following transfers are possible:

o Posting from the revenue account to the account for deferred revenues (for

example, initial transfer, which transfers the entire revenue from the revenue

account to the account for deferred revenues)

o Posting from the account for deferred revenues to the revenue account (for

example, at revenue recognition)

Adjustment Run

You report already recognized revenues using the adjustment run - assuming the

feeder system did not already do so. On the SAP Easy Access screen, choose

Periodic Processing -> Closing Preparation -> Receivable/Revenue Adjustment ->

Event-Based Deferred Revenues -> Adjustment Run.

Example

o The end of a header entry for an assignment key (DFKKDEFREV_HEAD-ENDIN

= 'X') is reached or the check date (DFKKDEFREV_HEAD-CHCKD) is past.

o The remaining amount that is still to be transferred (DFKKDEFREV_HEAD-

BETRA) is not zero.

The adjustment run offers the following options at event 1146 for each selected

header entry:

- Report the amount still to be transferred

The system creates an entry in table DFKKDEFREV_TRIG.

- Adjust the check date

The system creates an entry in table DFKKDEFREV_TRIGE.

- Process manually

The user decides, for each header entry, if a new check date is set or if

the amount still to be transferred is reported.

You should use this function only for test purposes, since it is not suitable

for processing mass data.

The adjustment run generates the events that are processed by the next transfer

posting run. We recommend that you execute the adjustment run immediately after

processing the transfer posting run.

Additional Functions

In the document display transaction, you can display the most important attributes of

deferred revenue postings by choosing Extras -> Deferred Revenues.

Write-Off

If you want to write off documents (SAP Easy Access screen: Account -> Write-Off

Items) for which event-based deferred revenues were posted, you first have to take the

following steps:

o Register function module FKK_DEFREV_BY_EVENT_WOFF_0020 at event

0020.

o Register function module FKK_DEFREV_BY_EVENT_WOFF_0030 at event

0030.

If you register these function modules, then, when you write off amounts, events

(DFKKDEFREV_TRIG) are automatically reported to the SAP system. These events

contain, as information, the write-off document that was created at the time of the write-

off. Using these events, the system reports the write-off amount proportionally to the

relevant assignment keys.

If you do not want the write-off process to influence the processing of event-based deferred revenues, then do not register these two function modules at events 0020 and

0030. These function modules are not registered in the standard system.

Test of the Function

You can use the report TEST_DEFREV_TABLE_ENTRIES to test the processing of

event-based deferred revenues. Using this report, you can create a list of all

DFKKDEFREV* table entries for an assignment key. To test the reporting of an event

(revenue recognition), you can use report TEST_DEFREV_RAISE_EVENT.


Make the following settings in Customizing for Contract Accounts Receivable and

Payable:

o Define account determination for deferred revenue under Business

Transactions -> Deferred Revenue Postings -> Maintain Account Determination for Deferred Revenue Postings.

o Specify the document type for the documents created by the transfer posting run

by choosing Business Transactions -> Deferred Revenue Postings -> Maintain Default Values for Transfer Posting Run.

o Enter an alternate cost center under Business Transactions -> Deferred

Revenue Postings -> Exchange of No Longer Valid Account Assignments -

> Assign New Cost Center.

o Enter an alternate profit center under Business Transactions -> Deferred

Revenue Postings -> Exchange of No Longer Valid Account Assignments -

> Assign New Profit Center.

Doubtful Entries and Individual Value Adjustments

Use

Predefined Value Adjustment Amount

Until now, you could use the transaction Adjust Receivables (in the SAP menu under

Account) only to specify a percentage rate for the system to use in individually

adjusting a receivable. As of SAP ECC 6.0, Enhancement Package 4, you can also

predefine an explicit value adjustment amount instead of the percentage rate.

In the Adjust Receivables According to Age transaction in the SAP menu under

Closing Preparation -> Receivable/Revenue Adjustment, you can also predefine a

value adjustment amount in event 2950. If there is both a percentage rate and a

predefined value adjustment amount for an item after this event, for further processing,

the system takes the value that leads to a higher individual value adjustment amount.

Note

The predefined value adjustment amount is currently not supported for calculation

types where value adjustments are reset to separate accounts.

Adjust Promises to Pay

In the Adjust Receivables According to Age transaction (SAP menu: Closing

Preparation -> Receivable/Revenue Adjustment), when adjusting items that are in

promises to pay, you can use the due date of the payment dates as the comparison

date for determining the age of the receivable (but not the due date in the original

items). To do this define event 2950.

Dynamic Value Adjustment Variant

Using the new event 2957, in the Adjust Receivables According to Age transaction

(FPRW) (SAP menu: Periodic Processing -> Closing Preparation ->

Receivable/Revenue Adjustment), you can determine the value adjustment variant

dynamically. In this event you define a value adjustment variant whose age structure is

used to perform the value adjustment of the current receivable.

Valuation Areas

You can now designate an item as doubtful or individually adjust its value differently in

different ledger groups. To do this, you use valuation areas that each map to a

ledger group. In the transactions Adjust Receivables (FPZW), Adjust Receivables

According to Age (FPRW), and Transfer Adjusted Receivables (FPRV), you can

now perform actions dependent on valuation areas.

Prepare Valuation Areas

Once you have activated and defined valuation areas, you have to prepare the doubtful

entry data in the database tables for the valuation areas and company codes. This also

applies for company codes for which there are no doubtful receivables or individual

value adjustments.

For this preparation, SAP provides sample report

RFKK_ZWFEWB_BWBER_INIT. Note that you should not deactivate valuation

areas for doubtful entries/individual value adjustments once you have successfully

prepared at least one company code for valuation areas.

Reconciliation with General Ledger

In all ledger groups affected by the valuation areas used for a given company code, the

doubtful entry accounts and individual value adjustment accounts must each have the

same account balance as the company code during the preparation of the valuation

areas.

If you want to use a further valuation area for a company code after the preparation,

then the doubtful entry and individual value adjustment accounts must have no entries

for the company code in the corresponding ledger group.

Once you have prepared valuation areas for doubtful entries/individual value

adjustments, input fields with the following meanings appear in the following

transactions for valuation areas:

o Adjust Receivables (FPZW), Adjust Receivables According to Age (FPRW),

Display Receivables Adjustments Transferred (FPRA), and Open Item Lists

(FPO1, FPO4)

The Valuation Area field is optional. If the field remains empty, only company

codes are selected for which valuation areas are not (yet) defined. If the field

contains a specific valuation area, only company codes are selected that have

been adjusted to valuation areas and to which this specific valuation area has

been assigned in Customizing.

o Transfer Adjusted Receivables (FPRV)

The Valuation Area field appears as selection criterion. There is also a

dropdown box where you can choose one of the following: all company codes;

only company codes with valuation areas; only company codes without valuation

areas.

Example

Before the introduction of valuation areas, an item had been classified as a doubtful

entry and had an individual value adjustment of 50%. Now you defined the valuation

areas HGB and US GAAP in Customizing and you activated (and prepared) valuation

areas for doubtful entry/individual value adjustment. Then you use the Adjust

Receivables transaction (FPZW), to make an individual value adjustment of 100% for

valuation area HGB for this item. In the valuation area US GAAP, the valuation

adjustment of the item does not change. This means that the item still has an individual

value adjustment of 50% there.

A different item previously had the same adjustment for both valuation areas HGB and

US GAAP. Now you enter valuation area HGB in the Transfer Adjusted Receivables

transaction (FPRV) and execute a transfer run. In this case, the transfers of the general

ledger items only refer to the ledger group assigned to valuation area HGB. The system

makes no transfers for the valuation area US GAAP or its ledger group.


Adjust Promises to Pay

Under Business Transactions -> Doubtful Entries and Individual Value

Adjustments, in the Maintain Value Adjustment Variants for Automatic Adjustments activity, you can specify whether, for the adjustment of items in

promises to pay, the due date in the payment dates is to be used as the comparison

date for determining the age of the receivable instead of the due date in the original

items. You define this for each value adjustment variant.

Valuation Areas

Under Business Transactions -> Doubtful Entries and Individual Value

Adjustments -> Valuation Areas, first define your valuation areas. Assign a ledger

group to each valuation area.

Assign these valuation areas to the desired company codes by choosing Business

Transactions -> Doubtful Entries and Individual Value Adjustments -> Valuation

Areas -> Define Valuation Areas for Receivables Adjustments.

In the Activate Valuation Areas for Receivables Adjustments activity,

you activate the use of valuation areas for doubtful entries and individual value

adjustments. This enables you to adjust an item differently in different ledger groups.

Note

All transactions for doubtful entry/individual value adjustment are locked after the

activation and remain locked until all data has been prepared for the valuation areas.

In the Prepare Valuation Areas for Receivables Adjustments activity,

you adjust the desired company codes to the assigned valuation areas.

Write-Off

Use

As of SAP ECC 6.0, Enhancement Package 4, with the mass write-off, you can write off

or prevent the write off of individual items by age and amount grid. When doing so, you

can also influence whether this is to be visible in the application log.

The system determines the write-off variant in event 2957, which you can define in

accordance with your requirements.

For each age and amount structure, the write-off variant defines whether the current

receivable can be written off. You can display the procedure in the application log for

information purposes (optional).

Example:

Document 4711 was posted 200 days ago with the amount EUR 1000.

There is a write-off variant VARI with the following settings:

o Days after Due Date Sequential Number Amount

Automatic W/O . Log

50 1 500 X

100 1 500 X

100 2 1000 X X

100 3 5000 X

From these settings, the system derives the following procedure:

1. The document is older than 50 and 100 days. The system therefore checks all

four entries, but it first checks the rule for which the number of days after the due

date is the highest number of days, and then the rule for which it is the smallest.

2. The system checks line 2 first. The amount of 1000 is more than 500 and,

therefore, does not qualify.

3. The system then checks line 3. The amount of 1000 is within the range up to

1000 and therefore qualifies for the write-off.

4. The system writes off the item automatically and makes a note in the log.


In the Implementation Guide for Contract Accounts Receivable and Payable under

Business Transactions -> Write-Offs:

o Maintain Write-Off Variants, you define the write-off variants that the write-off

run (transaction FP04M) uses to check whether line items may be written off.

Note: Always create at least one age and amount grid for a write-off variant.

o Maintain Age and Amount Grid for Write-Off Variants, define an age and

amount grid for the write-off variants defined in the previous activity. The write-off

run uses these to check whether the line items can be written off.

For each currency, from a specific age, and up to a maximum amount, you can

define whether

- The write-off is permitted

- There should be a note in the log

Prerequisite for the settings mentioned is:

o You have defined write-off variants.

o You have defined event 2957. This event uses different criteria of the item, such

as business partner, contract account, company code, account determination ID,

business area, and segment to determine the write-off variants defined.

o In the write-off run (transaction FP04M), on the tab page Posting Parameters,

you have set the indicator Write-Off by Age and Amount. By setting this

indicator you activate this function.

Enhanced Use of Profit Centers in Contract Accounts Receivable and Payable

Use

As of SAP ERP 6.0, Enhancement Package 4 (Release 6.04), you can make account

assignment to profit centers not only for expense and revenues, but also for other line

items. The enhancements affect:

o Postings to bank account, bank clearing accounts, cash accounts

o Postings to receivables accounts, liabilities accounts, and down payment

accounts

o Postings to tax accounts

Detailed information for each of these three groups is provided below. In all cases it is

important to note that account assignment to a profit center is only possible if the field

status group of the G/L account allows account assignment of this type. The field status

group is entered in the G/L account master record.

Profit Centers in Postings to Bank Accounts and Bank Clearing Accounts

If the enhancements for Enhancement Package 4 for Contract Accounts Receivable

and Payable are activated, then it is possible to post account assignments to profit

centers in bank posting or cash journal posting in the following processes:

o Payments and debit memos resulting from the payment program

o Payments using payment lot, check lot, credit card lot

o Payments using the cash desk or cash journal

o Payments using external cash desks

o Returns

This text describes below how you can enter a profit center in the processes

mentioned. In all cases, you must assign the profit center directly to the item on the

bank account or cash account, regardless of which profit centers are posted in the paid

items or in the payments on account.

From the viewpoint of the general ledger, this results in related receivables and

payables on the affected profit centers. If you made the appropriate settings for the new

general ledger, then the system automatically creates clearing items for these

receivables and payables on the affected profit centers during the general ledger

transfer.

Payment Program

The bank clearing account is determined using posting area 1061. There you can now

enter a profit center in Customizing, in addition to the account number and the business

area.

Payment Lot, Check Lot, Credit Card Lot

The Profit Center field is now available in the lot header, as well as in each lot item.

During posting, an entry in an item takes precedence over an entry in the header.

If you enter or change a lot manually, you can enter the profit center directly.

If you are using sequential files to generate the lots, you can enter the profit center in

the corresponding structures - BFKKZK for the header of the lot and BFKKZP for the lot

item.

If you generate payment lots from the electronic bank statement, then the system

copies the profit center from the items of the bank statement (table FEBEP). The

events 0953 and 0954 allow you to set the profit center for the payment lot header or

payment lot item to a different value.

The profit center that was entered on the payment lot is also used for a posting to a

clarification account.

Cash Desk, Cash Journal

When payments are entered, the system can propose a default profit center in the

same way that it proposes a company code or business area.

What is new is that you can now enter default values for the business area and for the

profit center in Customizing. You make these entries in table TFK100K. You can enter

default values there at the level of the cash desk, the office, or the company code.

External Cash Desks

For payments using external cash desks, you can set the profit center using events

6200 or 6210. The new sample module FKK_SAMPLE_6210_TFK100K is

provided for event 6210. If you register this module, then the values stored in

Customizing in table TFK100K are copied. (See also the section for Cash Desk.)

Returns

If you enter the returns lot manually, you can enter profit centers both at the header

level and at the item level. Just as in the payment lot, the entry in the item takes

precedence.

If you are using sequential files to generate the lots, you can enter the profit center in

the corresponding structures - BFKKRK for the header of the lot and BFKKRP for the

lot item.

If you generate returns lots from the electronic bank statement, then the system copies

the profit center from the items of the bank statement (table FEBEP). The events 0963

and 0964 allow you to set the profit center for the returns lot header or returns lot item

to a different value.

The profit center entered in the returns lot is used for posting to a clarification account,

and is also used as a standard value for receivables for charges, along with expense

and revenue from charges.

Profit Center for Payables, Receivables, and Down Payments

The profit center can now be used for account assignment in line items that post to a

business partner. The same applies here as stated above - namely that this account

assignment is not possible unless the field status group of the assigned G/L account

does not suppress the Profit Center field.

Since the Profit Center field did not exist in the business partner items before

Enhancement Package 4, the setting for it in the field status group (profit center

allowed or not) was not relevant. Accordingly, it is not safe to assume, based on the

current setting in your system, whether or not you want account assignment to profit

centers in the future.

Therefore, a new Customizing setting was introduced at the level of the company code,

where you can specify if you want to allow account assignments to profit centers for

business partner items. You make this setting in table TFK001B. Only if you allow the

account assignment using this setting is there a resulting check of the field status

group. This also makes it possible to have potentially different treatment of different

receivables accounts, liabilities accounts, and down payments accounts.

We would also like to point out that there are differences between FI-CA and classic

Acounts Receivable (FI-AR) and Accounts Payable (FI-AP). In classic Acounts

Receivable and Accounts Payable, it is not possible to post account assignment to a

profit center on customers or vendors. Instead, if you made the appropriate settings for

the new general ledger, the system assigns profit centers and distributes amounts to

profit centers automatically in related subsequent items that are used for updatin the

general ledger.

The following section describes some typical business transactions where business

partner items are posted, with an explanation of how the system determines the profit

center that is posted.

Invoices and Credit Memos

Normally profit centers are derived or defaulted for revenue and expense items. What

is new here is that the profit center that was determined in this way is inherited by the

receivable or payable. If revenue or expense items occur for different profit centers, the

result can be that more business partner items arise in total, because there is no

merging of multiple business partner items with different profit centers.

Inheritance of the profit center from the offsetting items applies for posting using

requests and for all current invoicing programs (invoicing in Contract Accounts

Receivable and Payable, invoicing using SD interface, IS-U invoicing, payment plan

interface of the Industry Solution Insurance).

Down Payment Requests and Budget Billing Requests

When you enter requests manually, you can enter the profit center directly. You can

enter default values and values for automatic creation (such as budget billing requests

in the industry component Utilities) in the new posting area 0310.

Payments on Account and Down Payments (Without Down Payment Request)

The profit center is set using a module for event event 0114. If you do not register

your own function module, the system processes the standard function module

FKK_SAMPLE_0114. This module adopts the profit center from the first G/L item of the

document. This is the line item on the bank account, bank clearing account, or cash

account.

Down Payments, Budget Billing Payments, Cash Security Deposits (with Request)

Down payments, budget billing payments, and cash security deposits that arise due to

clearing of requests adopt their profit center from those requests.

Charges Receivable (Returns)

The system determines the profit center for a charges receivable from the paid items

and the items on account of the payment document. For each profit center concerned,

the system calculates the total amount that arises for it (absolute amount without

positive/negative sign). The profit center with the highest total amount is then adopted

by the charges receivable.

If the system is not able to determine a profit center in this way, then the profit center

from the bank posting/bank clearing posting of the payment document is used.

If that line item also does not contain a profit center, then the system adopts the profit

center entered in the item of the returns lot.

Charges Receivable (Dunning)

For dunning charges, the system determines the profit center using event Zeitpunkt

0363. If you use standard function module FKK_SAMPLE_0363, then the dunned

items are grouped by profit center, and the profit center is determined from the group

with the highest amount.

Transfer Open Items

In the case of the transfer of open items, the profit center is inherited from the item

being transferred.

Open Items from Clearing Reset

For clearing reset, there are different options:

o If only one new open item is generated due to a reset, then the system adopts its

account assignments, including the profit center, from one of the items that was

previously cleared.

o If the distribution to accounts is kept, and there are different profit centers in the

previously cleared items, this results in various new items, each of which

contains the profit center of the item cleared previously.

o If (in the case of a payment document) the amount is returned to the clarification

account, then this posting receives the profit center from the related payment lot

item.

Derived Posting Items

When open items are cleared, additional postings are generated. These additional

postings can include cash discounts, payment surcharges, exchange rate differences,

interest on arrears. For these postings, it was already possible for you to enter account

assignments in Customizing.

If items that were involved in the clearing already have account assignment to a profit

center, then that profit center also takes precedence in the future over a profit center

that the system determines from Customizing. However, the derivation from

Customizing remains in effect for those cases where the open items themselves do not

have account assignment to a profit center.

The system normally derives the account assignments from table TFKCOD using an

account assignment key. Up to now, you could enter cost centers, orders, profit

centers, and project numbers in that table, dependent on the company code, business

area, and segment.

You can enter those elements as also being dependent on a profit center that were

already determined elsewhere. This ensures, for example, that when a cost center is

determined, it agrees with the profit center that was already adopted from an open

item.

Profit Centers in Postings to Tax Accounts

In this context, tax accounts are considered to be accounts to which tax on

sales/purchases or withholding tax is posted. The functions described here are not

available for other types of taxes (such as, insurance taxes).

Profit Centers with Sales/Purchases Tax

The system supports distributing tax items based on various account assignments

(business area, segment, profit center, account assignments from Funds

Management). For more information, see the release note Enhanced Account

Assignment of Tax Items.

Profit Centers with Withholding Tax

When you post withholding tax, the system adopts the profit center from the related

business partner item. The data you are required to report is recorded in table

DFKKQSR. The profit center is also contained in the table, and sample report

RFKKQST00 for evaluating the withholding tax data also displays the profit center.


Settings for Enhanced Use of Profit Center

The relevant Customizing settings for the enhanced use of profit centers in Contract

Accounts Receivable and Payable are:

o Activation of profit center for business partner items

This activation is made per company code. In Customizing for Contract Accounts

Receivable and Payable, choose Organizational Units -> Set Up

Company Codes for Contract Accounts Receivable and Payable

o Field status groups check

The field status group is in the G/L account master records of the receivables

accounts, payables accounts, down payment accounts, bank accounts, cash

accounts, and tax accounts (on the Entry/Bank/Interest tab page). You can

double-click to display the group attributes. The Profit Center field should be

available as an optional entry.

If you need to change the attribute of a field status group, choose Financial

Accounting (New) -> Financial Accounting Global Settings (New) ->

Ledgers -> Fields -> Define Field Status Variants. On the next screen,

select the field status variants relevant for the company code in question and

then navigate to maintenance of the field status groups.

o Define default values for the cash desk

You define default values for the profit center and the business area in

Customizing for Contract Accounts Receivable and Payable under Business

Transactions -> Payments -> Processing Incoming/Outgoing Payments ->

Cash Desk/Cash Journal -> Define Default Account Assignments

o Adjust the account assignment keys for CO objects

If you have defined account assignment keys for which you derive CO objects

dependent on company code, business area, or segment, check whether you

now need to make the settings for each profit center. For example, this is

necessary if you derive a cost center and a profit center is defined in the cost

center. In this case, the profit center in the derived cost center should agree with

the profit center previously transferred from a business partner item.

To make the settings in Customizing for Contract Accounts Receivable and

Payable, choose Basic Functions -> Postings and Documents -> Document -

> Define Account Assignments for Automatic Postings -> Define CO

Account Assignment Keys.

Automatic Clearing

Use

Automatic Clearing: Grouping and Iterative Clearing

As of SAP ECC 6.0, Enhancement Package 4, you can summarize the items selected

for a business partner or contract account in groups in the new event 0591. The

system then calls the clearing control per group and can then, when there are suitable

postings, post several clearing documents.

Items that can only be partially cleared or not cleared after grouping and assignment,

you can group again in an iterative process so that, in a subsequent call, clearing

control has the opportunity to assign the items again. This means that you can define a

series of groupings with a decreasing level of detail and clear an item in a single run in

several steps with several partial clearings.

You can return messages for the grouping logic and these are written in the application

log.

The new event also enables you to define a clearing document type for the current

clearing; this overrides the clearing document type entered in the parameters.


Register your function module for event 0591 in Customizing for Contract Accounts

Receivable and Payable under Program Enhancements -> Define Customer-

Specific Function Modules.

Integration

Use

Disputes with External Processing

As of SAP ECC 6.0, Enhancement Package 4, when you create dispute cases in

Contract Accounts Receivable and Payable, you can specify that the dispute cases are

not processed in SAP Dispute Management, but are processed instead in an external

component.

The dispute cases can be created in the external component and sent to Contract


You can also create these dispute cases in Contract Accounts Receivable and Payable

or in SAP Biller Direct and then send them to the external component using a report

you schedule to run on a periodic basis.

The dispute cases are processed in the external component. (This processing includes

changes to amounts, addition of further documents, changes of attributes or status).

With ECC 6.0, Enhancement Package 4, SAP provides integration with CRM Dispute

of SAP Customer Relationship Management 7.0 as an external component.

Funds Management

As of SAP ECC 6.0, Enhancement Package 4, if you subsequently want to integrate

the Funds Management (PSM-FM) component of Public Sector Management with

Contract Accounts Receivable and Payable (FI-CA), or if you want to post to further

company codes that were previously not assigned to an FM area with active FM

integration, you can write the required FM account assignments to all documents

created before the integration with FM.

For detailed information about the conversion of existing documents, see the IMG

activity Define FM Account Assignment for Subsequent FM Activation.


Dispute Management

Processing by an external component requires new case types in FSCM Dispute

Management, since the ID of the external object (the CRM dispute case) must be

recorded in the case record.

You define new case types in Customizing for Contract Accounts Receivable and

Payable under Integration -> Financial Supply Chain Management -> Dispute

Management -> Basic Settings for Dispute Management in the Definition of Own

Case Types with External Processing group box.

Funds Management

You enter FM account assignment for a subsequent FM activation in

Customizing for Contract Accounts Receivable and Payable under Integration ->

Funds Management (PSM-FM).

Enhancements to Account Determination

Use

As of SAP ERP 6.0, Enhancement Package 4 (Release 6.04), you can select by

specific entries in the list of displayed entries in Customizing transactions for account

determination by choosing Selection -> By Contents.

In addition, you can now execute a transport for subareas of the posting area by

choosing Account Determination -> Transport -> Partial Transport. There you can

select, in dialog mode, which data should be transported from the existing key

combinations (for example, only all entries for a given company code).

For an example of putting this function into practice, see Customizing for Contract

Accounts Receivable and Payable under Basic Functions -> Postings and

Documents -> Define Account Assignments for Automatic Postings -> Automatic

G/L Account Determination -> Define Accounts for Sales/Purchase Tax.

Enhanced Account Assignment of Tax Items

Use

As of SAP ERP 6.0 Enhancement Package 4 (Release 6.04), an enhanced account

assignment of postings to accounts for tax on sales/purchases is available. This also

includes the option of splitting the tax amounts and tax base amounts to different

account assignments.

The Account Assignment Principle and the Splitting of Tax Items

The enhanced account assignment option applies to the following fields:

o Business area

o Segment

o Profit center

o Commitment item

o Funds center

o Fund

o Functional area

o Funded program

o Grant

If you want to use enhanced account assignment for tax items, you have to activate this

option in Customizing for each company code. If the new function is active, the system

determines for each tax item all other related G/L items that have the same tax code.

These items can contain various combinations of the account assignments mentioned

above. The system determines the total amount for each combination.

The tax item is then mathematically split into subitems and the appropriate account

assignment combination is assigned to each subitem.

The subitems are relevant for updating totals records for the reconciliation keys and

therefore also for updating the general ledger.

Example

You post an invoice with two revenue items and a tax item:

Account Profit Center Tax Code Amount Base

Amount

Revenue P001 A1 400

Revenue P002 A1 200

Tax A1 114 600

For the tax item, the system generates two distribution items, as follows:

Account Profit Center Tax Code Amount Base

Amount

Tax P001 A1 76 400

Tax P002 A1 38 200

When updating the general ledger, these two distribution items appear in the place of

the one tax item.

Restrictions

For cross-company code postings, it is possible that the tax-relevant items (expense,

revenue) and the tax items are posted in different company codes. In this case,

account assignments are only inherited if the company codes involved are not assigned

to different controlling areas or to different FM areas.

Special features and technical details

If the account assignment is not unique, then the system saves the account assignment

information for a tax item in the new table DFKKOPAA.

If the account assignment is unique, then the system transfers the account assignment

information for a tax item directly to table DFKKOPK.

There is a special feature for tax-relevant down payments. The account for tax on

sales/purchases and a related clearing account are updated, even though there are no

separate tax items in the document. The tax information (tax code, tax amount, tax

account, clearing account) is only included as additional attributes in the down payment

item posted to the contract account. In that case, the system adopts the account

assignment of the down payment item directly for updating the tax.

Displaying account assignment data for a tax item

In the document display, the tax items are initially displayed as usual. In the case of a

unique account assignment, the tax item is displayed in the same way as other general

ledger items.

If there are differing account assignments, you can display the split using the new

Account Assignment pushbutton.


For enhanced account assignment of tax items in Contract Accounts Receivable and

Payable, make the following settings in Customizing:

o Activating the Functionality

This activation is made per company code. In Customizing for Contract Accounts

Receivable and Payable, choose Organizational Units -> Set Up

Company Codes for Contract Accounts Receivable and Payable

o Field Status Groups Check

The field status group is in the G/L account master records of the tax accounts

(on the tab page Entry/Bank/Interest). You can double-click here to display the

group attributes. Set the account assignment fields mentioned at the start to

optional (at least those account assignments that are used in your installation).

If you need to change the setting of a field status group, in Customizing choose

Financial Accounting (New) -> Financial Accounting Global Settings (New)

-> Ledgers -> Fields -> Define Field Status Variants. On the next

screen, select the field status variants relevant for the company code and then

navigate to maintenance of the field status groups.

Cash Desk

Use

Payments by Payment Slip in the Cash Desk

As of SAP ECC 6.0, Enhancement Package 4, in the cash desk you can use a two-

level procedure for incoming and outgoing payments.

In the first step, you can identify the items to be paid by the customer or to be paid out

by your company and summarize them in a payment slip. In the second step the

payment is processed in the cash desk.


You can define codes for the clerks who issue payment slips. In Customizing for


Payments -> Processing Incoming and Outgoing Payments -> Cash Desk/Cash

Journal -> Define Codes of Issuer.

Check Escheatment

Use

As of SAP ECC 6.0, Enhancement Package 4, Contract Accounts Receivable and

Payable supports the process of check escheatment for checks that were not cashed

by the recipient within a specified time period.

Example

In the United States, uncashed checks and money orders must be escheated to the

state government after a specified amount of time has expired, when, according to

federal law, they then become property of the given state. Insurance companies are

required to undertake reasonable measures to find the check recipient and to

determine if a check has been lost or needs to be re-issued. The last known address of

the lawful check recipient determines which U.S. state laws are applicable.

Escheatment can either be processed automatically, or manually in clarification

processing. In the standard system, escheatment is handled automatically. However,

you can also select checks for manual processing by defining event 0431 (for instance,

based on the amount of the check and/or the address of the recipient).

Check escheatment has the following steps:

o Check creation

o Selection of checks for escheatment

o Escheatment

o Payment

Check creation

At the time the check is created, the system determines the receiver code and the

earliest possible start date for the escheatment process, based on the current standard

address (region) of the recipient. This information is stored in the check. At event 0430,

you can change the receiver code and specify one of the following for the check:

o No escheatment should take place.

o No escheatment should take place if the check recipient lives outside of the

country.

Selection of checks for escheatment

On the SAP Easy Access screen, select all checks that are eligible for escheatment by

choosing Periodic Processing -> Data for Externals -> Tax Authorities -> Check

Escheatment -> Start Escheatment Process. The checks that are eligible are all

checks:

o That have open status and were not yet cashed

o That are older than the number of days you specified in Customizing

o That are above the amount you specified in Customizing

The program generates a persistent worklist containing the checks that can be

escheated and sets the escheatment date and receiver code for these checks based

on the last known address of the payee.

You can also change the receiver code in event 0431.

After that you create the notification letters. On the SAP Easy Access screen, choose

Periodic Processing -> For Contract Accounts -> Correspondence -> Print

(correspondence type 0046 - check escheatment letter).

The program generates notification letters that inform payees that they are in

possession of an uncashed check, which will be escheated after a certain time period

expires. The letter is addressed to the last known address of the business partner. If

the check is included in automatic processing, then the system sends the letter

automatically. Otherwise, you decide if the letter should be sent.

In event 0431, you can prevent correspondence from being created.

If you are using manual processing, you can decide if correspondence is sent or not.

SAP provides the PDF form Check Escheatment Letter

(FI_CA_CHECK_ESCHEATMENT_PDF).

If the recipient does not respond, then the check is escheated automatically on the

escheatment date. If the recipient does respond, then you can transfer the check over

to manual processing. Manual processing takes place in the clarification worklist for

check escheatment, on the SAP Easy Access screen choose Periodic Processing ->

Data for Externals -> Tax Authorities -> Check Escheatment -> Clarification. There

you can respond to the following reactions of the recipient:

o Cashing the check in 'n' days

o Postponement of the escheatment date, for example, because the check needs

further clarification

o Notification that the check was lost

You can:

o Issue a replacement check

o Search for the current address of the payee in the business partner data

o Create a notification letter

o Set the check for resubmission

o Specify an escheatment date that overwrites the escheatment date set by the

program

o Change the receiver code in accordance with the last known address of the

payee

o Specify the address to which the notification letter is sent

o Transfer a check to automatic processing

The check is escheated only in the case of automatic processing (when the

escheatment date is reached).

For example, if a user enters a new address, you can transfer the check to

automatic processing. The check escheatment is then automatic when the

escheatment date is reached. If a notification letter was not yet created, then the

system informs you of that. Note

If a check has been specified for manual processing, then the check cannot be

escheated, even if the escheatment date has been reached.

Escheatment

On the SAP Easy Access screen, choose Periodic Processing -> Data for Externals

-> Tax Authorities -> Check Escheatment -> Execute Escheatment to select all

checks from automatic processing that were not yet cashed and where the

escheatment date has been reached. The program voids these checks and sets the

voiding reason and escheatment date. The system derives the specifications for

creating the document from posting area 1042. You can post the G/L items for the

voided checks either as individual or collective documents.

o Payment

The payment program creates a payment advice for the recipient (the U.S.

state).

Display

You can display all escheated checks. On the SAP Easy Access screen, choose

Periodic Processing -> Data for Externals -> Tax Authorities -> Check

Escheatment -> Display Escheatment Data. You can select the checks by the

payment document.


You activate check escheatment per company code in Customizing for Contract

Accounts Receivable and Payable under Organizational Units -> Set Up Company Codes for Contract Accounts Receivable and Payable.

You make system settings for check escheatment in Customizing for Contract Accounts

Receivable and Payable under Basic Functions -> Check Management in the

following activities:

o Enter Receiver Codes for Check Escheatment

o Enter Specifications for Check Escheatment

Submit to Collection Agency

Use

Enterprise Services for Submit for Collection

As of SAP ECC 6.0, Enhancement Package 4, SAP provides enterprise services for

the business process Submit for Collection. When activated, this service-oriented

interface replaces the previous file interface and offers the following additional functions

as part of the business process:

o Groupings of collection items for submission, along with external grouping

information (external collection cases or court cases), are supported by the

application in the form of collection units.

o External status information on the progress of processing is integrated in the

submitting company's own status information.

o Payments reported by the collection agency result in the posting of receivables

which are credited to the collection agency.

Service Interfaces

The following service interfaces are implemented in SAP Contract Accounts Receivable

and Payable:

o CommissionedOutstandingCollectionsERPBulkRequest_Out

The service interface is used for sending information from the submitting

company to collection agencies, and it determines the following data:

- Information for submitting collection items, including business partner data

and correspondence (such as original invoices), as well as grouping

information (such as, assignment of interest and charges to the main

receivable at the time of submission)

- Clearing information due to (partial) payments or (partial) write-offs of

submitted collection items

- Information for callback of submitted collection items

o CommissionedOutstandingCollectionsERPBulkConfirmation_In

The service interface is used by the submitting company to receive information

from collection agencies, and it accepts the following data:

- Information for assigning collection items to external collection cases/court

cases

- Status information on the progress of processing the collection items

- Payment information

Note

Currently, Contract Accounts Receivable and Payable does not support

processing of called back or reversed payment information that was reported by

collection agencies.

- Information on uncollectible amounts

- Information on interest and charges that were successfully collected by the

collection agency on behalf of the submitting company

Once the enterprise services are activated for the business process Submit for

Collection, the file interface (creation of submission and information files, import of

collection agency files) is no longer supported. For more information on dependencies

related to activating the services, see the documentation for the indicator you use

to activate them.

Monitor for Collection Services

There is a Collection Services Monitor for the outbound and inbound information that

is sent or received using services (see SAP Easy Access screen: Account -> Submit

for Collection -> Collection Services Monitor). You can use this transaction to

monitor the processing status of individual messages.

Preparing Collection Agency Information

There are two transactions for processing the inbound collection agency information:

o Process Collection Agency Information (see SAP Easy Access screen: Account

-> Submit for Collection -> Process Collection Agency Information)

Here you can clear (or partially clear) collection items by payments, or you can

write-off (or partially write off) amounts that are uncollectible. The system posts

interest and charges statistically and immediately clears them. The system uses

the clearing account of the collection agency as the offsetting account for the

clearing payments.

o Post Collection Agency Receivables (see SAP Easy Access screen: Account ->

Submit for Collection -> Post Collection Agency Receivables)

You post collection payments reported by the collection agency as receivables

on the contract account of the collection agency. The system uses the clearing

account of the collection agency as the offsetting account. The collection agency

must assign a grouping key to each collection payment to enable

reconciliation with the SAP system.

Collection History

You can display status information for collection items (both those reported internally

and externally) in the collection history. (See SAP Easy Access screen: Account ->

Other Information -> Collection History). This transaction provides an overview of

how processing of the collection item is progressing.

External Number of Collection Case/Court Case

In the Management of Submitted Items transaction (see SAP Easy Access screen:

Account -> Submit for Collection -> Process Collection Items), the system displays

the external number of the collection case or court case (if there is one) that belongs to

the collection item. In addition, the external case number is available as a selection

criterion.

Events

At event 6260, you can group collection items before submitting them to the collection

agency. For instance, you could assign interest and charge items to the appropriate

main receivable item, thereby grouping them together in a submission group.

At event 6261, you can change or add to outbound information for collection

payments. Also you can change the distribution of outbound payment amount

information (assignment between collection payments and collection units).

At event 6262, you can determine the business partner data for the outbound service

when submitting to a collection agency. In the standard system, the standard address

is determined, along with telephone and fax numbers, e-mail address, and URI

address.

At event 6263, you can determine documents to be used as attachments to collection

units when they are submitted. These documents can be transferred in the outbound

service. For instance, you can determine the original invoices in the form of PDF

documents for the submitted collection items.

At event 6264, you can display industry-specific and customer-specific fields of a

collection case in the Management of Submitted Items transaction (see SAP Easy

Access screen: Account -> Submit for Collection -> Process Collection Items).

At event 6265, you can add certain contents to the message for the outbound service

interface.

At event 6267, you can transfer data from customer-specific fields from the enhanced

message of the inbound service to the application.

At event 6268, you can distribute inbound amount information from external collection

cases or court cases (or other groupings) to the individual collection items.

At event 6269, you can distribute outbound amount information from individual

collection items to already existing groupings.

Debt Recovery Score

As of SAP ECC 6.0, Enhancement Package 4, you can use the debt recovery

score of a business partner to determine the chances of successfully collecting

outstanding payments using external collection or a legal dunning proceedings.

Determining the Debt Recovery Score

The debt recovery score is determined using the following Enterprise Services from

SAP Credit Management (FIN-FSCM-CR) and is available to you for checks before

submission to collections.

o CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_Out

o CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_In

o CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_Out

o CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_In

You can request the debt recovery score of a business partner using these options:

o Manually, using the transactions for releasing and processing collection items

(on the SAP Easy Access screen, choose Account -> Submit for Collection ->

Release Items for Collection and Process Collection Items).

For a manual request, the system calls the enterprise service

CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_Out

directly.

o Using the release run for collections (on the SAP Easy Access screen, choose

Periodic Processing -> For Contract Accounts -> Submit for Collection ->

Release Run)

o Using function module FKK_SAMPLE_0350_GET_DRS for dunning

activities in the dunning run

o In the last two cases, the system does not call the enterprise service

CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_Out

directly. Instead, it determines the value in a two-step procedure as follows:

a) The system stores the corresponding trigger entries in table

DFKKMDC_BP with the source CR (Credit Management) and type 006

(request debt recovery score) using the release run for collections or the

dunning run.

b) You execute the mass run to prepare for master data changes from

external systems (on the SAP Easy Access screen: Forward Data to SAP

Credit Management -> Prepare Master Data Changes from External

System) with source CR (Credit Management) and type 006 (request debt

recovery score).

When the mass run is executed, the system processes the entries of the

trigger table and calls the Enterprise Service

CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_O

ut.

o Using function module FKK_DEBT_RECOVERY_SCORE_QUERY

Using this function module, you can request the debt recovery score from other

processes, such as final billing.

Events

At event 6250, you can determine if the debt recovery score for a business partner

with open items should be requested.

At event 5058, you can use the debt recovery score for additional checks, before you

submit items to collections manually or in a mass run. (On the SAP Easy Access

screen: Account -> Submit for Collection -> Submit Items for Collection or

Periodic Processing -> For Contract Accounts -> Submit for Collection ->

Submission Run.)

At event 6251, you can define postprocessing for items that were not submitted to

collections.

At event 6252, you can fill customer-specific fields in the outbound message of the

enterprise service for requesting the debt recovery score. These are fields which were

included in the message type using a data type enhancement.

At event 6253, you can transfer data to your application from customer-specific fields

(that were included in the message type using a data type enhancement) from the

inbound message of the enterprise service for the debt recovery score response.

Displaying the Debt Recovery Score

You can display the debt recovery score in the following transactions:

o Release Items for Collection (SAP Easy Access screen: Account -> Submit

for Collection -> Process Collection Items)

o Management of Submitted Items (SAP Easy Access screen: Account ->

Submit for Collection -> Release Items for Collection)

o Write Off Items (SAP Easy Access screen: Account -> Write Off Items)


Enterprise Services for Submit for Collection

First activate the service-oriented interface for the business process Submit for

Collection in Customizing for Contract Accounts Receivable and Payable under

Integration -> Enterprise Services -> Make Central Settings for Enterprise Services.

Then you make the necessary settings for collection agency postings in Customizing

for Contract Accounts Receivable and Payable in the activities

Define Specifications for Processing Collection Agency Information and Define

Specifications for Collection Agency Postings under Business

Transactions -> Submit to Collection Agency.

You enter the allowed status information for processing at external collection agencies

under Business Transactions -> Submit to Collection Agency -> Maintain

Status of Collection Units.

You can classify collection units when you submit to collections; you enter the allowed

categories under Business Transactions -> Submit to Collection Agency -> Define Categories of Collection Units.

To display status information in the collection history, select the Coll.Hist. checkbox

under Business Transactions -> Submit to Collection Agency -> Define Submission Status

and under Maintain Status of Collection Units. In addition, define a variant for the

collection history with the event 0007 Submit for Collection under Business

Transactions -> Dunning -> Collection History -> Define Variants.

Debt Recovery Score

First activate the evaluation of the debt recovery score. In Customizing for


Submit to Collection Agency -> Define Specifications for Debt Recovery

Score.

In the next activity, you can define variants for checking the debt recovery

score.

Document Management Service

Use

Document Management Service: Link with Application Objects

As of ECC 6.0, Enhancement Package 4, storing and accessing links between

documents and application objects takes place centrally.

For individual application objects, you can decide if you want to use the application-

specific link or the new central function.

You can integrate this central management of links in your individual applications using

Application Programming Interfaces (APIs). The following functions are supported:

o Create

Using function module FKKDMS_CONNECTION_INSERT, you can link

documents or unprinted correspondence with an application object. After the

correspondence is printed using the print workbench or correspondence history,

the system automatically adds the correspondence to the Document

Management Service. You can use the function module

FKKDMS_CONNECTION_INSERT to link correspondence with an application

object even before it is printed. After the correspondence is printed, and thereby

added to the Document Management Service, the system automatically updates

the links with the information about the documents.

o Delete

You can use the function module FKKDMS_CONNECTION_DELETE to delete

links between application objects and documents.

o Selection

Using the function module FKKDMS_CONNECTION_SELECT, you can select

documents that are linked to an application object.


If you do not want to use the central function for linking documents, then in

Customizing for Contract Accounts Receivable and Payable under Program

Enhancements -> Define Customer-Specific Function Modules, enter:

o A function module that checks if a document can be deleted

For example, if a document is used by an application object, then it cannot be

deleted.

o A function module that returns which application objects use a document

No other activities are required in order to use the function.

New Events in Contract Accounts Receivable and Payable

Use

As of SAP ECC 6.0, Enhancement Package 4, you can use the following new events:

o 0114:Profit Center for Payment on Account or Down Payment

o 0394:Dunning History: Check whether FKKMAKO Is a Dunning Notice

o 0430:Escheatment: Escheatment Data for Check Creation

o 0431:Escheatment: Data at Start of Escheatment Process

o 0591:Automatic Clearing: Group Items

o 0663:Payments: Set Paying Contract Account

o 0761:Inbound Correspondence: Reminder Days before Due Date

o 0781:Correspondence: Create Dynamic PDF Form

o 0782:Correspondence: Print Dynamic PDF Form

o 0787:Correspondence: Create/Print General Correspondence

o 0807:Creation Event: Escheatment Letter

o 0808:Print Event: Escheatment Letter

o 1036:Collections: Determine Attributes of a Worklist

o 1037:Collections: Determine Separartion Criteria for Worklists

o 1038:Check of Master Data Group for Challenger Strategies

o 1056:Business Partner: Determine Business Partner

o 1133:Document: Business Partner Item Split in Posting in Dialog

o 1221:Account Balance Display: Master Data Relationships

o 1258: Biller Direct: Create/Change Card Data/Bank Data

o 1263:CRM: Determine FI-CA Documents for Invoice

o 1421:Parallel Billing of Payment Cards

o 1723:Mass Activity: Update of Delta Queue

o 1725:Mass Activity: Coinsurance Reporting (for Insurances)

o 1727:Mass Activity: Coinsurance Reporting, Move Parameters

o 1786:Subsequent FM Activation in FI-CA: Conversion of Documents

o 1804:Processing Locks: Plausibility Checks

o 1872:Mass Activity: Revenue Distribution - Post Distribution Documents

o 1880:Mass Activity: Snapshot of Installment Plan for Key Date

o 1881:Adjuster Module for Installment Plan Analysis for Key Date

o 1882:Distribution Algorithm of Installments to Original Receivables

o 2720:INV: Mapping for External Billing Documents

o 2721:INV: Check for External Billing Documents

o 2722:INV: Before Update for External Billing Documents

o 2723:INV:Update for External Billing Documents

o 2724:INV: Check of Reversal of External Billing Documents

o 2725:INV: Customer-Specific Fields of Reversal Billing Documents

o 2726:INV: Before Update of Reversal of External Billing Documents

o 2727:INV: Update for External Reversal Billing Documents

o 2728:INV: Enrich Invoicing Orders for Billing Documents

o 2729:INV: Determine Business Partner of Collective Bill Account

o 2780:XI_INTF: Inbound XI Mapping for CAStmntByElmts

o 2781:XI_INTF: Outbound XI Mapping for CAStmntByElmts

o 2782:XI_INTF: Inbound XI Mapping for CAStmntByID

o 2783:XI_INTF: Outbound XI Mapping for CAStmntByID

o 2784:XI_INTF: Inbound XI Mapping for CAStmnt Crt

o 2785:XI_INTF: Outbound XI Mapping for CAStmnt Crt

o 2786:XI_INTF: Inbound XI Mapping for CAInvReq

o 2787:XI_INTF: Outbound XI Mapping for CAInvReq

o 2813:FCC: Filtering of Items and Groups

o 2823:ICWC Documents: Change SearchProfile

o 2824:ICWC Documents: Add Additional Correspondence Entries

o 2826:ICWC Promise to Pay: Change Search Profile

o 2957:Value Adjustments: Dynamic Assignment of Value Adjustment

Group

o 3033:Installment Plan: Change to Penalty Charge Amount (Brazil)

o 3600:Clearing Information Service: Further Registered Objects

o 3601:Clearing Information Service: Conversion of External Object Key to

Internal Object Key

o 3602:Clearing Information Service: Check Industry-Specific Objects

o 3603:Clearing Information Service: Supplement XI interface

o 3604:Clearing Information Service: Supplement Industry-Specific Fields

o 3860:XI Interface: Notification about Returns

o 4604:FICA Services: Inbound XI Mapping ContractAccountByBPId

o 4605:FICA Services: Outbound XI Mapping ContractAccountByBPId

o 4606:FICA Services: Inbound XI Mapping CASIGRPBYELEMQR

o 4607:FICA Services: Outbound XI CASIGRPBYELEMQR

o 4608:XI: Check Business Partner Relationships

o 4610:FICA Services: Inbound XI Mapping ContrAcctDownPaytCreate

o 4620:XI: References to Receivables Payables Items

o 4625:XI: Read Dunning Notices

o 4626:XI: Read Dunning Notices for Business Partner

o 4630:XI: Read Inbound Payment Conditions from Contract Account

o 4631:XI: Read Outbound Payment Conditions from Contract Account

o 4632:XI: Read Inbound Balances Based on Business Partner

o 4633:XI: Read Outbound Balances Based on Business Partner

o 4634:XI: Create Inbound Cash Security Deposit Request

o 4635:XI: Create Outbound Cash Security Deposit Request

o 5420:Revenue Distribution: Estimation of Distribution Installments

o 5430:Revenue Distribution: File Creation by Analysis Report

o 5440:Revenue Distribution: Select Items for Distribution

o 5460:Revenue Distribution: Analysis Report

o 6201:External Payments: Supplement XI CashPointOpenitem

o 6216:External Cash Desks: Convert PAYRF to KUKON and HZUON

o 6217:Transmit Payment Data to ICM

o 6218:External Cash Desks: Check Document Number

o 6220:External Cash Desk Services: Add XI Interface Deposit

o 6221:External Cash Desk Services: Add XI Interface Diffference

o 6222:External Cash Desk Services: Add XI Interface Withdrawal

o 6250:Collection Agency: Request Debt Recovery Score

o 6251:Collection Agency: Follow-On Activities for Unsubmitted Items

o 6252:Collection Agency: Enhance Outbound Message for Debt Recovery

Score

o 6253:Collection Agency: Enhance Inbound Message for Debt Recovery

Score

o 6260:Collection Agency: Grouping of Collection Items

o 6261:Collection Agency: Outbound Information for Collection Payments

o 6262:Collection Agency: Business Partner Data for Outbound Service

o 6263:Collection Agency: Document Attachments for Outbound Service

o 6264:Collection Agency: Display of External Information for Collection

Case

o 6265:Collection Agency: Additional Information for Outbound Service

o 6267:Collection Agency: Additional Information for Inbound Service

o 6268:Collection Agency: Assignment of Inbound Amount Information

o 6269:Collection Agency: Outbound Information for Collection Units

o 8026:BILL: BI Mass Activity Interval: Extraction of EDRs

o 8027:BILL: BI: Customer-Specific Checks for BI-Relevance of EDRs

o 8028:BILL: BI: Customer-Specific Fields in Extract Structure for EDR_00

o 8037:BILL: Monitoring of Billing Account Facts: Fill Customer Fields

o 8038:BILL: Monitoring of Billing Account: Change Layout

o 8039:BILL: Monitoring of Billing Account: Customer-Specific Actions

o 8040:XI_INTF: Inbound XI Mapping: CAINVTSK Create Request

Synchronously

o 8041:INTF: Outbound XI Mapping: CAINVTSK Create Request

Synchronously

o 8042:XI_INTF: Inbound XI Mapping BSRecord Create Request (EDR)

o 8043:XI_INTF: Outbound Mapping BSRecord Create Confirm (EDR)

o 8050:XI_INTF: Inbound XI Mapping: BSA Create Request Asynchronously

o 8051:XI_INTF: Inbound XI Mapping: BSA Change Request Asynchronously

o 8052:XI_INTF: Inbound XI Mapping: BSA Cancel Request Asynchronously

o 8053:XI_INTF:Outbound XI Mapping: BSA Create Confirmation

Asynchronously

o 8054:XI_INTF: Outbound XI Mapping: BSA Change Confirmation

Asynchronously

o 8055:XI_INTF: Outbound XI Mapping: BSA Cancel Confirmation

Asynchronously

o 8062:XI_INTF: Inbound XI Mapping BSRecordFindByElements

o 8063:XI_INTF: Outbound XI Mapping BSRecordFindByElements

o 9600:RE: Document Split for Billing Document

o 9601:RE: Fill Industry-Specific Fields in Billing Document

o 9602:RE: Determination of Billing Document to Be Adjusted


You define installation-specific function modules in the Implementation Guide for

Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.

Extraction of Payments

Use

As of Release 6.04, you can extract all payments data to Business Intelligence (BI).

You can run the extraction as a full upload, as a delta initialization with or without data,

or as a delta update.

Extract Structure

The extract structure FKKPAYBW_DELTA contains all fields that could be relevant for

evaluation in BI. The DataSource delivered with BI Content extracts all relevant fields.

Full upload/Delta init with or without data

The extractor FKK_BW_PAY supports selection of entered data in full upload or delta-

init modes, which transfer payments data from the ERP system to the BW system.

Delta update

Transactions that create or change payments data (that is, FPY1, FP05, FP25, FP35,

FP45, FP08, FPCD, external payment and external reverse services and so on) will set

the trigger in trigger-table DFKKPAYBW. Run mass activity (transaction

FPBW_EXTRACT) to extract data to the delta queue.

You must execute Delta Initialization once for the delta update function to work. The

delta procedure After Image via Delta Queue (AIM) is used.


Before using Extraction of Payments, you first need to activate extraction in

Customizing for Financial Accounting (New) under Contracts Accounts Receivable and

Payable -> Integration -> Business Intelligence -> Make Central Settings.

Extraction of Returns

Use

As of Release 6.04, you can extract all returns data to Business Intelligence (BI). You

can run the extraction as a full upload, as a delta initialization with or without data, and

as a delta update.

Extraction structure

The extraction structure FKKRETBW_DELTA contains all fields that could be relevant

for evaluation in BI. The DataSource delivered with BI content extracts only the most

important of these fields. If you require additional fields for your evaluation, you must

adjust the DataSource accordingly and then replicate it in your BI system.

Full upload and Delta initialization with or without data

The extractor FKK_BW_RET supports the selection of entered data in full upload and

delta-init modes, which transfer returns data from the ERP system to the BW system.

Delta update

Transactions that create or change returns data (FP09 and FPCRL) set the trigger in

the trigger-table DFKKRETBW. Run report RFKKBI_RET (transaction FPRETBW) to

extract data to the delta queue. You must execute Delta initialization for the delta

update function to work. The delta procedure After Image via Delta Queue (AIM) is

used.

Note:

During extraction, if more than one business partner is assigned to a return, the return

charge and the tax amount on the return charge are assigned to the business partner

with the highest partial return amount.

If a business partner has more than one contract account for a single return, the return

amounts for this business partner are aggregated.


You must activate the returns extraction before using it. Do this in Customizing for

Financial Accounting (New) under Contract Accounts Receivable and Payable ->

Integration -> Business Intelligence -> Make Central Settings.

Distribution of Revenues

Use

Mass Activity for Distribution Posting

As of SAP ECC 6.0, Enhancement Package 4, you can use the Post Distribution

Documents transaction in the SAP menu under Periodic Processing -> For Contract

Accounts -> Revenue Distribution as a mass activity. If you are using Contract

Accounts Receivable and Payable with Enhancement Package 4, as standard the

system automatically calls up transaction FP60PM when you run the Post Distribution

Documents transaction.

Report RFKKRD00 Revenue Distribution: Create and Post Documents, which was

used up to now, continues to be available in transaction FP60P_OLD. Note however,

that you can no longer use report RFKKRD00 for enhanced revenue distribution. The

only report that now supports this function is the mass activity Post Distribution

Documents.

Enhanced Revenue Distribution

You can use the enhanced revenue distribution in parallel with classic


In the standard system, with enhanced revenue distribution, you distribute assigned

payments (receivables items cleared by payment). However, you can also distribute

unassigned payments (payments on account with a subtransaction designated as

payment-relevant) and expected revenues (still open line items but not including

assigned payments). For expected revenues and unassigned payments, the system

runs an estimated distribution. The user estimates the distribution ratios of the final

recipients in advance. In contrast, the system always distributes assigned payments as

final, since the user can determine the distribution ratios uniquely in advance.

The system supports distribution of each receivables item to several final recipients.

Using report RFKKRDI_AGGR, you can create aggregated distribution information

(see SAP menu: Periodic Processing -> For Contract Accounts -> Revenue

Distribution -> Create Aggregated Distribution Information). For more information,

see the report documentation.

You can also extract distribution information for Business Intelligence (BI) (see SAP

menu: Periodic Processing -> Extraction for Business Intelligence -> Extract

Revenue Distribution Items). Report RFKKRDI_BW executes the delta extraction

to BI.

Technical Basics

Enhanced revenue distribution is based on a different technical concept than classic

revenue distribution. For example, in enhanced revenue distribution, the final recipients

and their respective distribution portions for receivables items must already be created

and exist in the table of distribution information (DFKKRDI_RATE) before you can start

the revenue distribution process in Contract Accounts Receivable and Payable. The

distribution information is linked to the line items (DFKKOP) using the distribution key - a GUID that is contained in the table of distribution information and in the line

items. For event 5440, you define which line items are distributed using enhanced


The following applies to the information for the final recipient and the corresponding

distribution ratios:

For assigned payments and expected revenues, you have to define the final recipient

and distribution ratios before the revenue distribution process and write them to the

table of distribution information (DFKKRDI_RATE) together with the distribution keys

created. The distribution key must be inherited by the receivables items (field DISKEY

in table DFKKOP). You have to create an implementation for this in a customer project.

To add the distribution information, you can use function module

FKK_RDI_RATE_INSERT.

Note for the industry component Public Sector Contract Accounts Receivable

and Payable

To add the distribution information, you can use the Business Rules Framework

(BRF). SAP provides the BRF object TRM_TEMPLATE_OBJECT with the

implementing class 0TRMRD001. With an appropriate implementation of this class,

you can determine the distribution information required.

For unassigned payments, the final recipient and distribution ratios are defined at event

5420, which is called by the revenue distribution mass activity (FP60M). The corresponding distribution key is not inherited by the payables items (in table

DFKKOP), it is only noted in the distribution table (DFKKRDI).

Note that an original line item can only be distributed in one way - either with classic

revenue distribution or enhanced revenue distribution. If, for one original line item, data

is defined for both classic and enhanced revenue distribution, the classic revenue

distribution overrides the enhanced revenue distribution. Therefore, make sure that in

the classic revenue distribution, you do not automatically derive the final recipient for

the line items that you want to distribute with enhanced revenue distribution.

Enhanced revenue distribution is based on distribution groups and distribution

periods. A current distribution period must be assigned to each distribution group.

Prerequisites

If you want to use enhanced revenue distribution, the following prerequisites must

be fulfilled.

Events

Using event 5440 you can define whether an item is distributed. The system calls the

event when you post a document.

Using event 5420, you can estimate the distribution ratios for unassigned payments.

The event is called in the mass activity Revenue Distribution.

Evaluation of Revenue Distribution

You can analyze revenue distributions using the following evaluation reports with their

different output options:

o Report RFKKRDI_REPORT (transaction FP60R_NEW) for the analysis of

revenue distribution based on original documents (see SAP menu: Account ->

Further Information -> Evaluation of Revenue Distribution (Original

Document)). Note that if you use Contract Accounts Receivable and Payable

with Enhancement Package 4, transaction FP60R calls up transaction

FP60R_NEW as standard automatically. Report RFKKRD01 List of Distributed

Revenues is still available using transaction FP60R_OLD.

o Report RFKKRDI_REPORT_DIS for the analysis of revenue distribution

based on distribution documents (transaction FP60R1) (see SAP menu:

Account -> Further Information -> Evaluation of Revenue Distribution

(Distribution Document)).

Simulated Assigned Payments for Classic Revenue Distribution

Using the Revenue Distribution (FP60M) transaction, you can use the Simulate

Assigned Payments option. This means that open receivables items are

simulated as assigned payments (cleared by payment) and corresponding simulation

entries are written to table DFKKRDI (see SAP menu: Periodic Processing -> For

Contract Accounts -> Revenue Distribution -> Distribute Revenues). You can then

use the analysis report RFKKRDI_REPORT to select and evaluate simulated

assigned payments.

Activation of Distribution Documents for Invoicing

The system now supports an activation of distribution documents for Invoicing in

Contract Accounts Receivable and Payable. This means that distribution documents

can be cleared with other documents during invoicing and corresponding invoices can

be created for the recipient.


You make the system settings in Customizing for Contract Accounts Receivable and

Payable under Business Transactions -> Distribution of Revenues -> Enhanced

Revenue Distribution in the following activities:

o Make Settings for Enhanced Revenue Distribution

o Define Distribution Groups

o Define Transaction Determination for Distribution Groups

o Define Distribution Periods

o Define Distribution Periods for Distribution Groups

o Define Specifications for Invoicing

Activate enhanced revenue distribution in Customizing for Contract Accounts

Receivable and Payable under Program Enhancements -> Prepared Enhancements -> Enhanced Revenue Distribution.

Extraction of Work Items

Use

As of Release 6.04, you can now extract all work items data to Business Intelligence

(BI). You can run the extraction as a full upload, a delta initialization with or without

data, and as a delta update.

Extraction structure

The extraction structure FKKWLIBW_DELTA contains all fields that could be relevant

for evaluation in BI. The DataSource delivered with BI content only extracts the most

important of these fields. If you require additional fields for your evaluation, you must

update the DataSource accordingly and then replicate it in your BI system.

Full upload and delta initialization with or without data

The extractor FKK_BW_WLI supports selection of entered data in full upload or delta-

init modes, which transfer work items data from the ERP system to the BW system.

Delta update

Transactions that create, change or delete work items (that is, FPVA, FPVB, and

FPWLM) set the trigger in trigger-table DFKKWLIBW. Run mass activity (transaction

FPBW_EXTRACT) to extract the data to the delta queue. You must execute delta

initialization once for the delta update function to work.

The delta procedure After Image with Deletion Flag Via Delta Queue (AIMD) is used.


Before using work items data, you must first activate the extraction in Customizing for

Financial Accounting (New) under Contract Accounts Receivable and Payable ->

Integration -> Business Intelligence -> Make Central Settings.

Link to HyperLink: SIMG._FICABW_TFK000BI Customizing.

Standing Requests

Use

As of SAP ECC 6.00, Enhancement Package 4 earmarked fund documents are

statistically consumed as soon as you create a request. When the FI-CA document is

created from the request, the system replaces the statistic consumption by the

consumption through the FI-CA document. In case a request is deleted or rejected, the

system automatically releases the earmarked funds document that was created for this

request.

Note

You can create earmarked fund documents either via a request or via a separate

transaction. The automatic release only happens for earmarked funds documents that

were created via requests.

When you change the amount or account assignment for a request line item, the

system automatically adjusts the earmarked funds document that was created for this

request. Technically, the system releases the old earmarked funds document and

creates a new one based on the new amount and account assignment. This, too, is

only done for earmarked funds documents that were created via requests.

With the improved request features you now can:

o edit requests that are on the approval worklist

o close earmarked fund document directly from within the request

Furthermore, you can use a new year end report that allows creation of earmarked

funds documents for standing requests. (see SAP menu: Periodic Processing ->

Closing Preparation -> Create Earmarked Funds Documents for Standing

Requests)

New Web Dynpro Applications

Use

As of SAP ECC 6.0, Enhancement Package 4, you can use Web Dynpro applications

for creating customer contacts and manual correspondence and for Document

Management Service in Contract Accounts Receivable and Payable.

Clerks are guided through the following new Web Dynpro applications using a user-

friendly default/confirmation principle:

o Business Partner Contact (FKK_WDY_BP_CONTACT)

You can use this Web Dynpro application to log customer contacts. This includes

contact initiated by the customer, such as telephone calls, as well as contact

initiated by you, for example, letters or dunning notices.

You can use the note function to enter notes for a customer contact, such as the

reason for a budget billing amount adjustment.

o Correspondence Creation (FKK_WDY_CORR_MANUAL)

This Web Dynpro application provides a framework that you can use to:

- Create correspondence manually and send it to recipients

- Request inbound correspondence

You enter the tasks necessary for creating and requesting correspondence as

part of a guided procedure. You can have the correspondence checked and

approved based on workflow procedures by configuring the appropriate ISR

scenario. In the correspondence history. You print using the Print Workbench.

SAP provides correspondence type 0400 for creating and for printing

correspondence.

You can load both outbound and inbound correspondence to the Document

Management Service.

o Document Management Service (FKK_WDY_DMS)

You can add documents to the Document Management Service:

- From local PCs

- From correspondence containers

- From storage systems, such as the optical archive

The Document Management Service (DMS) archives documents and links the

archived documents with application objects of Contract Accounts Receivable

and Payable (FI-CA).

You can link application objects with documents. From an application object,

where required you can display and process these documents.

o Interaction History (FKK_WDY_INT_HIST)

The interaction history provides a complete overview of the correspondence

history, customer interactions and notes from various sources. You can extend

this overview as needed. For the following objects, SAP provides Customizing

for displaying information in the interaction history:

- Outbound correspondence

- Customer contact

- Notes on execution work items

- Notes on master data groups

In Financial Customer Care (FCC), you can manually generate correspondence in the

document view. You access this view from the navigation bar or from processing of

collection work items.


You can create correspondence templates for creating correspondence

manually in Customizing for Contract Accounts Receivable and Payable under Basic

Functions -> Correspondence.

You make settings for the contact history in Customizing for Contract Accounts

Receivable and Payable under Basic Functions -> Interaction History.

Business Function Contract Accounts Receivable and

Payable, Leasing

FICAX_LEASING: Transfer of Worklists to SAP CRM (Changed)

Use

As of SAP ECC 6.0, Industry Extension Contract Accounts Receivable and Payable, Enhancement Package 4 (FI-CAX 604), business function Contract Accounts

Receivable and Payable, Leasing (FICAX_LEASING), the transfer of worklists to

SAP CRM has been changed.

Using SAP CRM 2007, you can communicate with your customers during dunning activities thanks to the user role Financial IC Agent Leasing (FCC_LEAS). As a result

of this user role, you no longer need to manually transfer dunning-relevant data

(worklists) to SAP CRM. This data is transferred by Remote Function Call. Before you

can transfer this data, you need to make settings in Customizing for SAP ERP.


The following transactions for Collections Management in the FICAX_LEASING

business function are no longer available on the SAP Easy Access screen under SAP

menu -> Accounting -> Financial Accounting -> Contract Accounts Receivable

and Payable -> Enhancements for Leasing:

Collections Management

o Transfer Worklist to CRM (/LSIERP/WL_SEND)

o Worklist: Display Transfer Log (/LSIERP/WL_SEND_LOG)

The transaction /LSIERP/WLM (Manage Worklists) has also been replaced by the

transaction FPWLM (Manage Worklists).


Before you can automatically transfer worklists from SAP ERP to SAP CRM, in

Customizing for SAP ERP you have to assign the following installation-specific function

modules to the following events:

Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Program

Enhancements -> Define Customer-Specific Function Modules:

Event Function Module

20

/LSIERP/STOP_NON_ACCRUAL_00

20

2807

/LSIERP/SEND_DELINQ_STAT_28

07

1799

/LSIERP/TRIGGER_NON_ACC_179

9

See also

For more information about telephone collections, see SAP Library on SAP Help Portal at http://help.sap.com -> SAP for Industries -> SAP for Banking -> SAP for

Leasing.

Business Function Information Life-Cycle Management: Tax

Auditing

FIN_ACC_ILM: Information Lifecycle Management: Tax Auditing (new)

Use

As of SAP ERP 6.0, Enhancement Package 4 the business function Information

Lifecycle Management: Tax Auditing (FIN_ACC_ILM) is available. With this business

function, you can use the extraction services (also called "Context Data Extractor") of

the Retention Warehouse to archive the following information:

o Master data

o Customizing data

o Meta data of the ABAP dictionary

This information provides the context required for reporting on transactional data after

decommissioning the original system.

After system decommissioning, you can use the Retention Warehouse to select and

upload the archived data in SAP NetWeaver BI. There you can run queries on the data

or use it in an audit.


If you have already archived your transactional data, you can register existing archiving

objects as part of the ILM content. If you register an archiving object, the Retention

Warehouse recognizes the data of the archiving object as part of the solution and

provides additional functions for loading the data to the Retention Warehouse for

further analysis on demand. For more details, see Register Archiving Objects.

The following new entries have been added to the area menu under Tools ->

Administration -> Administration -> ILM: Context Data Extractor:

o Archive Data for ILM

o Data Extract Browser

o Display Archive Files

o Segment Catalog

o Field Catalog

Effects on System Administration

You can use extraction services starting with Release 4.6 C. The required software is

available in SAP Notes. For more information, see SAP Note 1089434.


You have to carry out the Customizing activities under SAP NetWeaver -> Application

Server -> Basis Services -> Information Lifecycle Management -> Retention

Warehouse -> Context Data Extractor.

See also

For more information, see SAP Library under Business Function Sets und Business

Functions -> Enterprise Business Functions -> Cross-Application Enterprise

Business Functions -> Information Lifecycle Management: Tax Auditing.

Business Function Partly Exempt Organizations

FIN_ACC_PEO: Partly Exempt Organizations (new)

Use

As of SAP ECC Enterprise Extension Public Sector Management 6.0,

Enhancement Package 4 (EA-PS 604), Business Function Partly Exempt

Organizations (FIN_ACC_PEO), you can map company areas that are completely or

partly exempt from paying tax in the system. You can define special tax codes for these

areas and create tax reports as proof for the tax office. In addition to this, you can use a

program for supplementary tax adjustments for variable tax deduction rates.


If you are a public sector customer and have used public-owned commercial

operations until now, the following applies:

o If you now want to use the new local financial management (NLFM) and tax

reporting from General Ledger Accounting (new), the function for partly exempt

organizations replaces the function for public-owned commercial operations.

o If you do not want to use the new local financial management and tax reporting,

you can continue using the function for public-owned commercial operations.


Note that the functions for public-owned commercial operations and partly exempt

organizations cannot be used simultaneously.

Business Function General Ledger Accounting 2

FIN_GL_CI_2: New General Ledger Accounting 2 (New)

Use

From SAP ECC 6.0, Enhancement Package 4, the New General Ledger Accounting

2 business function is available. This business function enables you to improve your

processes for parallel accounting as well as integrate your actual postings with

Controlling.

The following functions are available:

o New General Ledger Accounting and Profit Center Accounting

o Profit Center Assignment Monitor (Enhanced)

o Wizards for making the Customizing settings for document splitting

- Configuring Document Splitting (New)

- Creating a Document Splitting Rule (New)

o Navigation from FI Reports to CO Reports (New)

o Validation of Account Assignment Combinations (New)

o Invoice Reduction (Changed)

o Standard Configuration for Document Splitting (Enhanced)

o Parallel ledgers

o Logical Database BRF: Inclusion of Selection Criterion

"Ledger Group" (Enhanced)

o Reports for Displaying Documents: Inclusion of Selection

Criterion "Ledger Group" (Enhanced)

o Closing/Opening Entries for the Leading Ledger (New,

Country-Specific)

o Individual account closing

o Separate Posting Period Check for CO-FI Postings (New)

o Posting Period Check for Non-Representative Ledgers (New)

See also

o For more information, see the SAP Library under Business Function Sets und

Business Functions -> Enterprise Business Functions -> Accounting -

>New General Ledger Accounting 2.

o From SAP ECC 6.0, Enhancement Package 4, you can also migrate existing

data from Special Purpose Ledger (FI-SL) to new General Ledger Accounting.

This migration function is only available as part of the SAP General Ledger

Migration Service in the Migration Cockpit. This does not require the business

function New General Ledger Accounting 2 to be activated. For more

information, see SAP Note 1163997.

FIN_GL_CI_2: Profit Center Assignment Monitor (Enhanced)

Use

From SAP ECC 6.0, Enhancement Package 4, Business Function General Ledger

Accounting 2, you can use the Assignment Monitor for profit centers (transaction

1KE4) to check the assignment of the following objects to profit centers:

o Sales order items and

o Real estate objects from Flexible Real Estate Management (RE-FX)

You have the following selection options:

o You can display all objects that have not been assigned to a profit center;

o You can display all objects assigned to a specific profit center or to a specific

profit center group; or

o You can display an overview of all objects and their assignments to profit

centers.


The user interface of the transaction Profit Center Accounting: Assignment Monitor

(1KE4) has been extended. Previously, you had to use the menu to access the

functions. Now, you have the alternative option of using the selection buttons on the

initial screen for the objects or for the relevant report variants.

This also applies to the objects sales order items and real estate objects (RE-FX).

However, you can only select real estate objects if Flexible Real Estate Management

(RE-FX) is active.

The controlling area specified in the settings is displayed constantly and can still be

changed from the menu under Extras.


In new General Ledger Accounting, you can call the transaction Profit Center

Accounting: Assignment Monitor (1KE4) from the menu (as before) or alternatively

from Customizing under Financial Accounting (New) -> General Ledger Accounting

(New) -> Master Data -> Profit Center -> Assignments of Account Assignment

Objects to Profit Centers -> Check Assignments.

FIN_GL_CI_2: Wizard for Configuring Document Splitting (New)

Use

From SAP ECC 6.0, Enhancement Package 4, Business Function New General

Ledger Accounting 2, you can use a wizard to configure Document Splitting.

The wizard contains step-by-step instructions that enable you to make the Customizing

settings for document splitting and to check those settings. However, unlike in the IMG

activities for making Customizing settings, you do not simply make Customizing

settings; the system runs checks at the same time. There is documentation on the

individual steps in the wizard.


You call the wizard in Customizing for General Ledger Accounting (New) under

Wizard: Configure Document Splitting.

The wizard combines all the IMG activities relating to document splitting. By using the wizard, you do not need to perform the individual IMG activities for document splitting

in addition to the wizard.

See also

For more information, see the central Release Note for the New General Ledger

Accounting 2 business function.

FIN_GL_CI_2: Wizard for Creating a Document Splitting Rule (New)

Use


Ledger Accounting 2, you can use a wizard to create a new splitting rule for

Document Splitting.

The wizard contains step-by-step instructions that enable you to make the Customizing

settings for the splitting rule and to check those settings. However, unlike in the IMG

activities for making Customizing settings, you do not simply make Customizing

settings; the system runs checks at the same time and you can simulate documents on

the basis of existing documents. There is documentation on the individual steps in the

wizard.


You call the wizard in Customizing for General Ledger Accounting (New) under

Wizard: Create Document Splitting Rule.

The wizard combines all the IMG activities for creating a document splitting rule. By

using the wizard, you do not need to perform the individual IMG activities for the

document splitting rule.

See also



FIN_GL_CI_2: Navigation from FI Reports to CO Reports (New)

Use


Ledger Accounting 2, you can use the Report/Report Interface to call up various

reports in Controlling from within profit center reports or segment reports in new

General Ledger Accounting. The receiver reports are derived from the selected origin

object type (such as cost center or internal order) of the sender report.

For certain origin object types (cost center, overhead cost order, production order,

WBS element), possible origin objects are determined from the profit centers of the

sender reports and transferred to the receiver report. The new function is an

enhancement of the general Report/Report Interface in which receiver reports are

derived from the sender report (and not from the origin object type).

This new function is available for the following sender reports that need to have been

extended by the origin object type:

o 0SAPBSPL-03: Profit Center Group: Plan/Actual/Variance

o 0SAPBSPL-04: Profit Center Group: Plan/Plan/Actual

o 0SAPBSPL-13: Segment: Plan/Actual/Variance

o 0SAPBSPL-14: Segment: Plan/Plan/Actual


1. Include the Origin Object Type (ZZHOART) field in the totals table and in the

desired sender reports.

For more information, see the SAP Library under General Ledger Accounting

(FI-GL) (New) -> Reporting -> Drilldown Reports -> Defining Drilldown

Reports -> Including Fields HOART and EPRCTR in Reports.

2. Assign the utility program Select CO Reports for Origin Object

(FAGL_RRI_RECON_CO) to the above-mentioned sender reports using

the normal Report/Report Interface.

When you navigate from the sender report to the utility program, you can select the

receiver report for the origin object type in a second dialog box.

1. SAP delivers standard entries for receiver reports with different origin object

types. In Customizing for General Ledger Accounting (New), you can change

these standard entries under Change Report-Report Interface for Reconciliation with Controlling. First you must load the standard entries

once.

2. To change or add to selections that are transferred from the sender report to the

receiver report (parameters and selection options), you can implement the

Business Add-In (BAdI) Adjust Selections for Report-Report

Interfacein Customizing for General Ledger Accounting (New). This may be

necessary if you have defined your own receiver reports in Customizing, for

example.

See also



FIN_GL_CI_2: Validation of Account Assignment Combinations (New)

Use


Ledger Accounting 2, you can check different account assignment combinations and,

if required, prevent corresponding postings from being made. You can also extend the

check to include an account assignment combination of G/L accounts and cost centers

and prevent postings with this account assignment combination.

Note: The system only checks the entry view and not the general ledger view.

The following functions are available:

o Definition of valid and invalid account assignment combinations to reduce

the amount of validation rules:

If you define an account assignment combination as invalid, the system

considers all other combinations as valid.

o Validation Trace:

You can use the validation trace during postings to display the account

assignments to be checked and to determine the result.

o Validation Log:

You can use the validation log to analyze the validation rule after validation to

help you identify any errors quicker.

o Assignment of the validation strategy to a company code or to a ledger

group:

You can assign a validation strategy to a company code as a default strategy.

You can also assign validation strategies to specific ledger-groups.

o Validation only with documents to be posted:

The check is only performed on documents that need to be posted. It remains

possible to park documents.

o Use of groups:

You can also use groups, such as cost center groups, in your validation rules.


In Customizing for Financial Accounting Global Settings (New), under Define

Validation Rule for Account Assignment Combinations, you define the

validation strategies and assign them to the company codes or ledger groups to be

checked.

See also



FI_GL_CI_2: Invoice Reduction (Changed)

Use


Ledger Accounting 2, you can split invoice reduction items from Materials

Management (MM) across the relevant profit centers.

An assigned purchase order with two invoice reduction items on different profit centers

is written correctly to new General Ledger Accounting when the corresponding

incoming invoice is posted. In other words, the invoice reduction item is split across the

relevant profit centers.


In order that the system applies the invoice reduction amount (and not the total invoice

amount) to split the invoice reduction items, you need to make the following setting in

Customizing for General Ledger Accounting (New): Choose Business Transactions

-> Document Splitting -> Extended Document Splitting -> Define Document Splitting Rule, and set the For Each Logical Transaction indicator in the detail

screen for the header data of the splitting method in the Further Subdivide Document

group box.

See also



FIN_GL_CI_2: Standard Configuration of Document Splitting (Enhanced)

Use


Ledger Accounting 2, there are additional standard settings in the configuration of

document splitting (splitting method 0000000012):

Using these standard settings considerably simplifies configuring business processes, such as in the cash ledger for nonassigned payments or in Funds Management for

the Online Payment Update. Configuration of these processes in document splitting is

restricted principally to assigning the default account assignment values of the

predefined constant and to assigning the new document splitting rule to the relevant

document type.

The additional standard settings are as follows:

o Constant 0PACC for Nonassigned Processes: This constant is used to update

nonassigned payments;

o New business transaction variant 0002 for the business transaction Bank

Account Statement;

o The following item categories are added to the document splitting rule for the

business transaction Payment (business transaction variant 0001):

- Two item categories for editing, Vendor and Customer with the

processing category Transfer Fixed Value (No Splitting) and the constant 0PACC

- Base item categories Customer: Special General Ledger and Vendor:

Special General Ledger for the item category to be edited Cash Account

- Base item category Cash Discount Clearing for the item category to be

edited Taxes on Sales/Purchases

o New document splitting rule for the business transaction Bank Account

Statement, containing only one item category to be edited Cash Account with processing category Transfer Fixed Value (No Splitting) and constant 0PACC

See also



FIN_GL_CI_2: Logical Database BRF (Enhanced)

Use


Ledger Accounting 2, you can make selections by Ledger Group or by Ledger

in all reports that use the logical database BRF (document database) to select data.

For this, Ledger Group has been added as a selection criterion in the logical

database BRF.

The Ledger Group selection criterion is already considered In the following reports:

o Compact document journal (RFBELJ00)

o Compact document journal [not accessible] (RFBELJ00_NACC)

o Document List (RFBUEB00)

For more information on these enhanced reports, see the Release Note HyperLink: RELN.FIGLFIN_GL_CI_2: Reports for Displaying Documents.


To be able to use the Ledger Group selection criterion in your own reports, you need

to proceed as follows:

o You display the selection criterion on the screen by using the MODIF ID GRP.

o To inform the database about selection using this criterion, set the B0SG-

XLDGRP='X' indicator.

o Effects on Customizing

See also



FIN_GL_CI_2: Reports for Displaying Documents (Enhanced)

Use


Ledger Accounting 2, the Ledger Group selection criterion has been added to the

following reports:

o Compact document journal (RFBELJ00)

o Compact document journal [not accessible] (RFBELJ00_NACC)

o Document List (RFBUEB00)

These reports use the logical database BRF (document database). Accordingly, the

Ledger Group selection criterion has been added to this logical database. For more information, see the Release Note FIN_GL_CI_2: Logical Database BRF.

With the reports listed above, you can select reports that have been posted in the

ledger group you have specified.

o You can select either a ledger or a ledger group. If conflicting entries for ledger

and ledger groups are entered, the system issues an error message.

o To display the documents of all ledgers and all ledger groups, do not specify

either a ledger or a ledger group.

o If you specify a ledger, the document list is displayed unchanged. In the ALV

document list, you can display the ledger group in which the documents were

posted by changing the layout to include the Ledger Group column.

o If you specify a ledger group, the Ledger Group column is displayed

automatically in the document list. In the ALV document list, you can sort

documents by ledger group.

The remaining reports that also use the logical database BRF are not changed.

See also



FIN_GL_CI_2: Closing/Opening Entries for the Leading Ledger (New)

Use


Ledger Accounting 2, you can make year-end closing entries and opening entries to

specific ledgers for the leading ledger as well. For this, you use the program

Closing/Opening Postings at Year End (FAGL_YEC_POSTINGS_EHP4). This

program is intended mainly for the following countries: Italy, Slovakia, Turkey, Portugal,

Romania, and Columbia.

It saves the annual net profit or loss in table FAGL_TRVOR as the comparison value

for closing the balance sheet accounts.

Note

In Turkey, you have to close account group 7 separately. To do this, use the program

Turkey : Closing Account Class 7 (RFIDTRCLACCL7).

Since the postings are made using the reference transaction GLYEC, you can make

postings directly to G/L accounts for which the Post Automatically Only indicator is

selected. You cannot enter any other characteristics or account assignments.

Posting with the separate record type 5 (year-end closing) ensures that closing

entries are distinguished from the operational postings (record type 0).

The postings created are not updated in the subledgers. This means that no account

assignments needs to be made for cost centers, materials, fixed assets, and so on.


For new General Ledger Accounting, you use the program Closing/Opening Postings

at Year End (FAGL_YEC_POSTINGS_EHP4). For classic General Ledger Accounting,

you use the program Year-End Postings (RFSUMB00).

Whereas program RFSUMB00 from classic General Ledger Accounting uses a batch

input folder for postings, the new program (FAGL_YEC_POSTINGS_EHP4) creates

postings in real time using the accounting interface (with the reference transaction

GLYEC).


You can summarize the balances using specific account assignment characteristics. To

do this, you can use the Business Add-In (BAdI) Summarize Balances Using

Account Assignment Characteristics (FAGL_COND_ACC_ASSIGNMENT). For

more information, see the documentation on the BAdI.

See also

For more information, see:

o The documentation on the program Closing/Opening Postings

at Year End (FAGL_YEC_POSTINGS_EHP4) and

o The central Release Note for the business function New General Ledger

Accounting 2.

FIN_GL_CI_2: Posting Period Check for CO-FI Postings (New)

Use


Ledger Accounting 2, you can still post CO transactions in the preceding period even

when this period has been closed for FI postings. For this, you can use the additional

period interval 3 in the Customizing settings for the posting periods; this period interval

is only relevant for postings from Controlling (CO) to Financial Accounting (FI) (New). It

is valid for postings created with the real-time integration as well as for postings created

using the CO-FI reconciliation ledger during closing operations.

When you create an entry for period interval 3, only postings that were transferred from

CO to FI are checked against this interval. All other posting transactions are controlled

with period intervals 1 and 2.

If you do not create an entry for period interval 3, the settings for period intervals 1 and

2 are also valid for postings from CO to FI.

Note

You can only define the period interval for account type +.


You make the settings for this function in Customizing for Financial Accounting (New)

under Financial Accounting Global Settings (New) -> Ledgers -> Fiscal Year and

Posting Periods -> Posting Periods -> Open and Close Posting Periods.

See also



FIN_GL_CI_2: Posting Period Check for Non-Representative Ledgers (New)

Use

Previously, period checks were only possible for the representative ledger. This meant

that differing posting periods in non-representative ledgers were not considered.


Ledger Accounting 2, you can specify that the posting period check is also performed

for non-representative ledgers. In this way, postings can still be made in non-

representative ledgers even after the posting period in the representative ledger has

been closed. Furthermore, you can specify a different fiscal year variant for non-

representative ledgers.


You activate this function in Customizing for Financial Accounting (New) by choosing

Financial Accounting Global Settings (New) -> Global Parameters for Company

Code -> Enter Global Parameters and by setting the Manage Posting Period

indicator. Then define a different fiscal year variant and different postings periods for

the nonleading ledgers under Financial Accounting (New) -> Financial Accounting

Global Settings (New) -> Ledgers -> Ledger -> Define and Activate Non-Leading Ledgers.

See also



Business Function FI Localization Topics for Japan and

Portugal

FIN_LOC_CI_2: FI Localization Topics for Japan and Portugal (New)

Use

As of SAP ECC 6.0, Enterprise Extension Financials, Enhancement Package 4

(EA-FIN 604), the business function FI Localization Topics for Japan and Portugal is

available. You can use this business function to meet business requirements in the

Asset Accounting (FI-AA) component for Portugal and Japan.


o Migration Tools for Property Tax Report (Japan)

o Declaration and Output for Property Tax (Japan)

o PDF-Based Output for Mapas Fiscais (Portugal)

See also

For more information, see SAP Library under Business Function Sets and Business

Functions -> Enterprise Business Functions -> Accounting -> Country-Specific

Business Functions.

FIN_LOC_CI_2: Migration of Last Year’s Property Tax Data (New)

Use


(EA-FIN 604), Business Function FI Localization Topics for Japan and Portugal

(FIN_LOC_CI_2), you can use new reports to migrate property tax data from legacy

systems and from the old Statement of Net Assets report, RAJPVERM, to the current

SAP ERP system.

You can use new reports to perform the following functions related to property tax

results data:

o Migrate and process last year’s property tax data that is stored in a legacy

system You can use a new report to migrate data, and if the result is incorrect

due to the depreciation method changing, you can also use the report to change

the data that you migrate.

o Migrate property tax data from the results table of the old report for property tax

returns, the Statement of Net Assets report (RAJPVERM).

This function allows you to transfer the property tax results data to the results table for

the Property Tax Report without first saving the data in a speadsheet.

You can use both of the above reports to correct the results data in the SAP ERP

system, since in cases where the depreciation method changes, the Statement of Net

Assets (RAJPVERM) report can calculate the incorrect amount of depreciation for

property tax.

In addition to migrating last year’s property tax results data, you can also migrate property tax transaction data from your legacy system, and if required, delete that

data:

o Report /KJRTAX01/TRANSACTION_MIGR to import asset transaction data

o Report /KJRTAX01/TRANSACTION_DEL to delete asset transaction data that

you import using the above report

o Report /KJRTAX01/SIMPLY/TRANSAC_DEL to delete asset transaction data

without displaying it in SAP List Viewer (ALV)


The area menu for Property Tax now contains the following

transactions under the new node, Migration Tools:

o Migration of Additional Depreciation Code

o Migration of Last Year's Data

o Migration of Last Year's Data - XML

o Deletion of Data Migrated from Last Year

o Migration of RAJPVERM Data to Results Table

o Insertion of Asset Transaction Data

o Deletion of Asset Transaction Data

o Display Asset Transaction Data for Deletion

You can find the new Migration Tools section on the SAP Easy Access screen under

Accounting -> Fixed Assets -> Information System -> Reports on Asset

Accounting -> Specific Valuations -> Country Specifics -> Japan -> Property Tax.


To migrate property tax data, your company code must be in test mode. You enter the

migration status of your company code using a new Customizing activity in Customizing

for Financial Accounting (FI) under Asset Accounting -> Information System ->

Country-Specific Functions -> Japan -> Property Tax Report -> Enter Migration Status.

See also

For more information, see SAP Library under SAP ERP Central Component ->

Financials -> Country Versions -> Asia-Pacific -> Japan -> Financial Accounting

(FI) -> Asset Accounting (FI-AA) -> Property Tax -> Property Tax Report ->

Migration Tools.

FIN_LOC_CI_2: Declaration and Output for Property Tax (New)

Use


(EA-FIN 604), Business Function FI Localization Topics for Japan and Portugal

(FIN_LOC_CI_2), you can use the following new functions for the Property Tax report:

o Use a new central control function to determine whether your head office

prepares the property tax declaration forms centrally, or whether the individual

offices or subsidiaries prepare their declaration forms separately. To enable this

central control function, you set an indicator at company code level.

o In cases where the law grants tax breaks for some assets in the form of special

rules, you can use two new Customizing activities to cause the report to reduce

an asset’s value by a certain amount automatically.

o Improve the performance of the report when you output the report based on

Adobe document services by compiling the report in multiple files. You specify

the number of pages per file on the selection screen for the Property Tax report.


To restrict the number of pages that the system outputs when you use Adobe

document services, the report selection screen contains a new checkbox, Number of

Pages.


You make settings related to the central control function for submitting declaration

forms in Customizing for Financial Accounting (FI) under Asset Accounting ->

Information System -> Country-Specific Functions -> Japan -> Property Tax

Report ->

o Define Declaration Key

o Assign Tax Office Code to Declaration Key

o Assign Declaration Key to Company Code

o Assign Declaration Key to Company Code and City Code

To allow the report to take into consideration additional and special depreciation rates,

without the need for customer-specific implementations of the Business Add-In

Depreciation Rates, in Customizing for Financial Accounting (FI), choose Asset

Accounting -> Information System -> Country-Specific Functions -> Japan ->

Property Tax Report ->

o Enter Additional Depreciation Rates

o Enter Special Depreciation Rates

See also



(FI) -> Asset Accounting (FI-AA) -> Property Tax ->

o Asset Master Record -> Central Control

o Property Tax Report -> Special Rules

FIN_LOC_CI_2: Output for Mapas Fiscais (Portugal) (New)

Use

As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function

FI Localization Topics for Japan and Portugal (FIN_LOC_CI_2), you can output the

asset reports (mapas fiscais) that you prepare using the Asset Report Print Program for Portugal (RAIDPT02_PDF) as follows:

o Output the asset reports as PDF-based forms in the required legal format

o Improve the performance of the PDF-based forms by outputting them in multiple

files. You specify the number of pages per file on the selection screen


The selection screen of the Asset Report Print Program (RAIDPT02_PDF) contains a

new group box, Output Parameters, in which you specify the number of pages per

output file.

See also


Financials -> Country Versions -> Europe and Africa -> Portugal -> Financial

Accounting (FI) -> Asset Accounting (FI-AA) -> Running the Asset Reports ->

Asset Report Print Program.

Business Function FI Localization Topics for Japan and South Korea

FIN_LOC_CI_4: FI Localization Topics for Japan and South Korea (New)

Use


(EA-FIN 604), the business function FI Localization Topics for Japan and South Korea

is available. You can use this business function to meet business requirements in the

Financial Accounting (FI) component for Japan and South Korea.


o Invoice Summary Enhancements (Japan)

o Enhancements in Tax Reporting & Payments (South Korea)

See also

For more information, see SAP Library under Business Function Sets and Business

Functions -> Enterprise Business Functions -> Accounting -> Country-Specific

Business Functions.

FIN_LOC_CI_4: Invoice Summary Enhancements (New)

Use


(EA-FIN 604), Business Function FI Localization Topics for Japan and South

Korea (FIN_LOC_CI_4), you can use the following new functions for the Invoice

Summary solution:

o Use the batch input manager to upload new or changed master data related to

payment term data and Nayose data from the legacy system to the SAP system

o Extend the invoice summary header with additional fields

o Download the invoice summary data in SAP standard file format using the Print

Program

o Add additional fields to the output of the Print Program

o Define the sorting criteria and sorting sequence to be used in the output of the

Print Program

o Use improvements in manual clearing, including:

- A simplified screen for the invoice summary clearing process, where you

have the option to clear items with reference to monthly invoice data only

- Clearing from the oldest invoice summary payers invoice and its monthly

invoices

o Define special cases when:

- Dynamic virtual account numbers are assigned from a specific

number range to given payer invoices during invoice creation

- Separate clearing logic is used


The following changes are available:

o New fields on the selection screen of the Print Program, which allow you to

choose between downloading or printing the file as well as to define the main

downloading parameters

o A new screen for the manual invoice summary clearing process. You can choose

to display a list of the open monthly invoices only or to display a more detailed

view with the line items. To switch between the views, you can use the new

pushbuttons Detail View or Summary View as required.

o New radio buttons on the selection screen of the Maintenance of Virtual

Accounts program, which allow you to indicate whether you want to maintain

dynamic virtual account numbers, static virtual account

numbers, or both.

o A new checkbox on the Data for Invoice Summary (Japan) screen of the

customer master data, which allows you to specify whether the payer is relevant

for special case consideration and thus dynamic virtual account number

assignment is required.


New screens are provided, which allow you to upload new or changed payment term

daya or Nayose data from the legacy system to the SAP system using the batch input

manager.


Extension of Invoice Summary Header

To extend the invoice summary invoice header with additional fields, in Customizing for

Financial Accounting (New), choose Accounts Receivable and Accounts Payable

-> Business Transactions -> Country-Specific Settings -> Japan -> Invoice

Summary: Customizing Includes -> Customizing Include: Extend Invoice

Summary Header.

To fill in the new header fields you created, implement the Business Add-In (BAdI) in

Customizing for Financial Accounting (New), by choosing Accounts Receivable and

Accounts Payable -> Business Transactions -> Country-Specific Settings ->

Japan -> Invoice Summary: BAdI Enhancements -> Invoice Summary -> BAdI: Invoice Summary Invoice Processing.

This BAdI also contains a method, which allows the identification of special cases when

the Invoice Summary Processing program has to assign dynamic virtual account

numbers to given payer invoices.

Print Program Output File

To add new fields in the output of the Print Program, in Customizing for Financial

Accounting (New), choose Accounts Receivable and Accounts Payable ->

Business Transactions -> Country-Specific Settings -> Japan -> Invoice

Summary: Customizing Includes -> Customizing Include: Add Fields to Output File.

To fill in the new fields you created and to define the sorting criteria in the output file,

implement the BAdI in Customizing for Financial Accounting (New), by choosing

Accounts Receivable and Accounts Payable -> Business Transactions ->

Country-Specific Settings -> Japan -> Invoice Summary: BAdI Enhancements ->

Invoice Summary -> BAdI: Invoice Summary Payer and Monthly Invoices.

See also



(FI) -> Accounts Receivable and Accounts Payable (FI-AR/AP) -> Invoice

Summary.

FIN_LOC_CI_4: Enhancements in Tax Reporting & Payments (New)

Use

As of SAP ECC 6.0, Enterprise Extension Financials, Enhancement Package 4 (EA-

FIN 604), the business function Enhancements in Tax Reporting & Payments is

available.

With this business function you can process:

o The BoE Due Date

For each industry, you can maintain the number of days for BoE due date and

indicate whether the vendor is an SME or an LE on the basis of the company

code and industry key. In the case of SME, the due date is 60 days from the

earliest invoice date. In the case of LE, the due date is 90 days from the payment

run date. This is processed in the Automatic Payment program SAPF110S.

o Time dependent VAT Registration numbers

For every customer/vendor, you can maintain multiple VAT registration numbers

based on the entry date. This is processed in the following Korean reports:

- Tax Invoice Printing program RFIDKRTCR

- Tax Invoice Reprint / Cancel program RFIDKRTPR

- VAT Summary report RFUMSV45R


The following changes are available:

o A new screen for the vendor and customer master. You can choose to display

only the customer/vendor address or to display an enhanced customer/vendor

general data. To switch between the views, you can choose the Standard

pushbutton and Korean Supplement pushbutton.


Define BoE Due Date Determination by Industry

You can Customize the Define BoE Due Date Determination by Industry under

Financial Accounting (New) > Accounts Receivable and Accounts Payable >

Business Transactions > Outgoing Payments > Automatic Outgoing Payments >

Automatic Posting > Country Specific Settings for Automatic Posting > South

Korea > Define BoE Due Date Determination by Industry

Business Function Credit Card Encryption: Periodic Key

Exchange

Periodic Key Replacement for Payment Card Encryption

Use

Starting from SAP NetWeaver 7.0 Enhancement Package 1, you can use the business

function PCA_KEYV. Business function PCA_KEYV provides enhanced functions for

secure handling of payment cards in your system. In addition to the existing options

described in SAP Note 1032588, activating this business function makes it possible to:

oPeriodically replace the keys used for the encryption of payment card data

oDelete keys that are no longer used

To support the key replacement, the SAP system manages several key versions in

parallel in the new Secure Store and Forward (SSF) application PAYCRV.

New SSF Application

Versioned encryption uses the new SSF application PAYCRV. Programs that support

encrypted storage of payment cards now all use this new SSF application if they use

versioned encryption.

The only transaction for maintaining key versions is the transaction Administration of

Key Versions for PAYCRV (CCSECA). The Trust Manager (transaction STRUST)

merely displays the keys for the SSF application PAYCRV.

New Transaction for Managing Keys

In the Administration of Key Versions for PAYCRV (CCSECA) transaction, you

maintain the key versions that are needed for encryption and start the key

replacement. The transaction provides the following functions:

oCreate new key versions and distribute to the application servers

oDisplay information about the use of key versions

oDelete key versions that are no longer needed

You can create as many key versions as you require. The system always uses the

most current key version for encryption. For decryption, the system continues to use

the old key versions only as long as there are data records in the system for encrypted

payment cards that were encrypted using the old version. For this reason, you cannot

delete old key versions immediately. Instead you have to migrate the data records that

still exist for the old version to the current key version. You can ultimately delete the old

key once you have migrated the data successfully, since then the old key version is no

longer needed for decryption. To ensure the utmost security, however, the earliest date

deletion can take place is 90 days after the migration.

The functions for generating and deleting key versions are protected by authorization

object SSFVADM (activities 01 and 02).

Migration to the Current Key Version

After you create a new key version, you can migrate your data records from old key

versions to the current key version. For the migration, you use the Execute

Conversion (CCSECM1) transaction. For large data volumes, you can schedule

parallel processing for the migration. In addition, you can enter a maximum runtime.

You can migrate the data in increments; the system is able to decode existing data at

all times. In other words, the migration does not require system downtime.

In the Administration of Key Versions for PAYCRV (CCSECA) transaction, you can

see how much data the system contains for a given version.

The migration is protected by authorization object SSFVADM (activity 42).

Migration of Old Data to Versioned Encryption

You can even migrate old data, which was encrypted using your own SSF applications

(such as CCARD or PAYCRD), to the new SSF application. For this migration, you use

the Migration to SSF Application PAYCRV (CCSECM0) transaction. You can use

parallel processing for the migration of the database tables and you can enter a

maximum runtime. Here too, you can migrate the data in increments, therefore the migration does not require system downtime.

Deletion of Data Records No Longer Needed

You can delete no longer needed data records for encrypted payment cards using the

Deletion of Credit Card Data (CCSECV_DATA_DEL) transaction. The system

deletes only encrypted payment card data that was not used for a long period of time.

To this end, the report uses the date of last use as a selection criterion. To be safest,

the date of last use that you choose should be far enough in the past so that any

further use is ruled out. In the SAP standard system, this date must be at least 500

days in the past.

Note that after the data is deleted, you can only display the payment card numbers in

masked form.

You can find all of the transactions mentioned in the area menu Encryption of

Payment Cards (CCSEC).


Activating the key replacement does not affect the existing data. The system is able at

all times to decrypt credit card data that was stored in encrypted form.


You migrate old data to the new SSF application PAYCRV using the Migration to SSF Application PAYCRV (CCSECM0) transaction. The migration is not necessary from

the point of view of the processing processes. The migration can be performed in

increments.


Recommended Process Flow

If you want to convert to versioned encryption, proceed as follows:

1.Generate a key version using the Admin. of Key Versions for PAYCRV (CCSECA)

transaction.

2.Set the Key Replacement Active indicator in Customizing under Cross-Application

Components -> Payment Cards -> Basic Settings -> Make Security Settings for

Payment Cards.

3.Migrate your old data to the new SSF application PAYCRV using the Migration to

SSF Application PAYCRV (CCSECM0) transaction.

To replace keys, proceed as follows:

1.Generate a new key version using the Admin. of Key Versions for PAYCRV

(CCSECA) transaction.

2.Migrate the data records for no-longer-current key versions to the current key

version, using the Execute Conversion (CCSECM1) transaction. After the conversion

was performed successfully, confirm this again in a second step using the Check If

Can Be Deleted function in the same transaction.

3.After the migration, using the Admin. of Key Versions for PAYCRV (CCSECA)

transaction, check whether the migrated key versions are designated as being able to

be deleted.

4.In the Admin. of Key Versions for PAYCRV (CCSECA) transaction, delete any non-

current key versions after the grace period of 90 days has expired.


Activate versioned encryption of payment cards in Customizing under Cross-

Application Components ->Payment Cards -> Basic Settings -> Make Security

Settings for Payment Cards. Set the security level Masked Display, and Encrypted

When Saved. Also set the Key Replacement Active indicator.

Specify the payment card types that you want to save in encrypted form by choosing

Cross-Application Components -> Payment Cards -> Basic Settings -> Maintain

Payment Card Type.

Further Information

For information on general release of versioned encryption, see SAP Note 1151936.

Financial Supply Chain Management

Business Function Bank Communication

FIN_FSCM_BNK: Business Function Bank Communication Management

(new)

Use

As of SAP ECC 6.0, Enterprise Extension Financial Services, Enhancement

Package 4, (EA-FS604), you can use the SAP Bank Communication Management

business function. This business function replaces the business function FIN_FSCM_

INTEGRATION for the enablement of SAP Bank Communication Management.

The new business function includes the functionality of Bank Communication

Management shipped with Enhancement Package 2. This new component in SAP

Financial Supply Chain Management supports you when you monitor and release

payment media in payment transactions with the banks. The main functionalities

delivered with SAP ERP 6.0, Enhancement Package 2, are as follows:

o Logical structuring of payments into batches

o Multiple approval levels for outgoing payments

o Audit trail for payment approval decisions along with digital signatures for internal

audit

o Analysis of payment status information and full payment-flow transparency as

well as status monitoring for bank statements

o SWIFTNet integration using SAP Integration Package for Swift

With this business function, you can make use of the new capabilities of Bank

Communication Management.

New features with Enhancement Package 4 include:

o Cash management update

o Automatic triggering of follow-up activities via BAdI

o Additional reporting features

o Capability of assigning additional approval users for dual control (security)


One new user interface is available:

o Batch and Approver List

Improved user interface:

o Batch and Payment Monitor


Certain tasks must be performed by systems administrators in order to prepare the

component for use. For more information, see the corresponding documentation.


You can access the settings for SAP Bank Communication Management in the IMG

under Financial Supply Chain Management -> Bank Communication Management.

Business Function Billing Consolidation Connector

FIN_FSCM_BCONS_CON: Billing Consolidation Connector Business

Function

Use

SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604) introduces the Billing

Consolidation Connector business function. You can use this function to send IDoc

messages from the file system and associated messages from the archive (PDF, ISF)

to SAP Billing Consolidation 2.0, process received messages, list messages, and link

documents to documents.


The business function consists of the following four functions, which you can choose

from the user interface:

o Send Outbound Messages packs documents into document set files and sends

them to SAP Billing Consolidation 2.0.

o Process Inbound Messages processes incoming messages from the

middleware or the transfer client.

o Link Documents to Document links documents (messages) to documents.

o List Messages lists all messages.


You configure the settings for these functions in Customizing for Billing

Consolidation:

o Define Basic Settings

o Define Business Partners

o Define Inbound Object Types

o Define Outbound Object Types

o Define Partner Profiles

o Define Ports in IDoc Processing

o Define Conditions for Message Control

Business Function SAP Biller Direct: P2P and Customer Field

Extenstion

FIN_FSCM_604_BD_2: Biller Direct, Promise to Pay (New)

Use

As of SAP ECC 6.0, Financial Supply Chain Management, Enhancement Pack 4 (SAP-

APPL 604), the business function BD, Promise to Pay is available.

The release notes for the new functionality in the areas of Promise to Pay and

Customer Field Extension can be found in SAP Library under SAP ERP Central

Component.

Business Function FSCM Functions 2

FIN_FSCM_CCD_2: Business Function FSCM Functions 2 (New)

Use

As of SAP ECC 6.0, Enhancement Package 4 (FINBASIS 604), you can use the

FSCM Functions 2 business function. If you want to use this business function, you

must also activate the following business functions:

o FSCM Functions

o FSCM Integration 2 in the Accounts Receivable Accounting (FI-AR) system Exception: If the following conditions both apply, you do not have to activate the

FSCM Integration 2 business function:

- You do not use SAP Collections Management or SAP Dispute

Management; you only use SAP Credit Management.

- You use SAP Credit Management without the connection to an Accounts

Receivable Accounting (FI-AR) system.


SAP Collections Management (FIN-FSCM-COL)

o FIN_FSCM_CCD_2: Master Data Synchronization for Several FI

Systems (New)

o FIN_FSCM_CCD_2: Head Office/Branch Office Relationship

(New)

SAP Credit Management (FIN-FSCM-CR)

o FIN_FSCM_CCD_2: Master Data Synchronization for Several FI

Systems (New)

o FIN_FSCM_CCD_2: Enterprise Services for Credit Limit

Request (New)

o FIN_FSCM_CCD_2: Web Dynpro Application for Credit Limit

Request (New)

SAP Dispute Management (FIN-FSCM-DM)

o FIN_FSCM_CCD_2: Enterprise Services for Dispute

Management Processing (New)

o FIN_FSCM_CCD_2: Web Dynpro Application for Dispute Case

Processing (New)

See also

For more information, see the following documents:

o Central release note for the FSCM Integration 2

(FIN_FSCM_CCD_INTEGRATION) business function in your Accounts

Receivable Accounting (FI-AR) system

o Central release note for the FSCM Functions (FIN_FSCM_CCD) business

function

o SAP Library under Business Function Sets and Business Functions ->

Enterprise Business Functions -> Financials -> Financial Supply Chain

Management:

- FSCM Functions 2

- FSCM Integration 2

- FSCM Functions

FIN_FSCM_CCD_2: Master Data Synchronization for Several FI Systems (New)

Use

As of SAP ECC 6.0, Enhancement Package 4 (FINBASIS 604), Business Function

FSCM Integration 2, you can use central SAP Collections Management system to

collect receivables from several systems. If you replicate the customer master data

from the FI systems in a central system for SAP Collections Management, then you can

use the connection of Unified Key Mapping Service to the SAP NetWeaver Process

Integration (UKMS connection to SAP NetWeaver PI).

This is also possible even if the number ranges of the customers from the relevant FI systems overlap, so that the customer numbers from a cross-system view are not

unique. In SAP Collections Management, the system ensures the assignment of a

unique number when you create the business partner. When processing receivables, it

determines the correct assignment between the business partner and the customer in

the corresponding FI system.


You make the settings for this function in Customizing as follows:

Collections Management system

o Map Company Codes for SAP Collections Management

o Process Distribution Model (Filter for BAPI AccessProcessReceivables for object CollectionData)

o Mapping of FI Company Codes

o Set Master Data Distribution for Several FI Systems (New)

o Configuration in SAP NetWeaver PI

o Configuration for the Connection of UKMS to SAP NetWeaver

PI

Accounts Receivable Accounting system

Financial Supply Chain Management -> Collections Management -> Integration

with Accounts Receivable Accounting -> Master Data Distribution -> Mapping the

Master Data -> Activate/Deactivate Standard Implementation for Mapping in FI

Systems:

o Mapping in FI-AR (New)

o Mapping im SAP Collections Management (New)

See also

Central release note for the FSCM Functions 2 (FIN_FSCM_CCD_2) business

function

FIN_FSCM_CCD_2: Head Office/Branch Office Relationships (New)

Use


FSCM Functions 2, you can decide whether you would like to consider the head

office/branch office relationships that exist for your customers, and that you have

mapped in your Accounts Receivable Accounting, in the SAP Collections Management

component. In addition to the existing options of creating worklist items for your

collection specialists for each head office, you can also create worklist items per

branch. You can distribute the processing of the branches to several collection

specialists. You can also consider and manage outstanding receivables per branch.

If you use the integration with the application component SAP Dispute Management,

you can create dispute cases for branches.

For more information about considering the head office/branch relationships in SAP

NetWeaver Business Intelligence (SAP NetWeaver BI), see the release note

Consideration of Head Office/Branch Relationships (New) in the SAP NetWeaver

Library under SAP NetWeaver by Key Capability -> Information Integration: Key

Areas -> BI Content -> Release Notes SAPNetWeaver 7.0 BI Content Add-On 4.


If you activate the new function in Customizing for particular company codes, then, for

these company codes, you have to recreate all of the transaction data from FI-AR in

Collections Management that is relevant for creating the worklists, using the existing

program FDM_COLL_SEND_ITEMS.

The following interfaces have been slightly changed:

o The detail output list of program FDM_COLL_SEND_ITEMS for sending FI-AR

relevant data to Collections Management.

o Worklist of the collections specialist (transaction UDM_SPECIALIST), and

worklist of the collection manager (transaction UDM_SUPERVISOR)

o Interface of the Process Receivables function, which you access from the

worklist (transactions UDM_SPECIALIST and UDM_SUPERVISOR).


You make the Customizing settings for this function in the FI-AR system under

Financial Supply Chain Management -> Collections Management -> Integration

with Accounts Receivable Accounting -> Distribution of Data in Collections

Management:

o Activate Distribution per Company Code

This activity has been enhanced with a few fields, and is mandatory.

o BAdI: Define Customer for Collections Management

This new Business Add-In BAdI is optional.

See also


function


Use


FSCM Integration 2, you can use the connection of the Unified Key Mapping Service

to SAP NetWeaver Process Integration (UKMS connection to SAP NetWeaver PI) if

you want to use a central Sap Credit Management system for several FI or SD

systems. Using the UKMS connection to SAP NetWeaver PI you can replicate and

synchronize the customer master data from several source systems in a central SAP

Credit Management system.


You make the settings for this new function using the following new Customizing

activities:

o Carry Out ALE Master Data Distribution

o Set ALE Master Data Distribution for Several FI Systems

o Configuration in SAP NetWeaver PI

o Configuration for the Connection of UKMS to SAP NetWeaver

PI

o Configure Messages of SAP Credit Management for UKMS

See also

Central release note for the FSCM Functions 2(FIN_FSCM_CCD_2) business

function

FIN_FSCM_CCD_2: Enterprise Services for Credit Limit Request (New)

Use


FSCM Functions 2 you can use new operations in the process component Credit

Management for creating, changing and finding credit limit requests.

Operations

Create Credit Limit Change Request

o Update Credit Limit Change Request

o Read Credit Limit Change Request

o Find Credit Limit Change Request Basic Data By Elements

o Confirm Credit Limit Change Request (asynchronous)

o Create Credit Limit Change Request (asynchronous)

o Change Credit Limit Change Request (asynchronous)

o Cancel Credit Limit Change Request (asynchronous)

o Check Credit Limit Change Request

The four operations Create Credit Limit Change Request, Update Credit Limit

Change Request, Read Credit Limit Change Request and Check Credit Limit

Change Request are used for the new Web interface for creating and changing credit

limit requests . For more information about the new Web interfaces, see the release

note Web Dynpro Application for Credit Limit Request (New)


You configure the use of the Web services used by the Web interface in SOA

Management.


You make the settings for this function and also the implementation of the

corresponding mapping BAdIs if required in Customizing under the following nodes:

Financial Supply Chain Management -> Credit Management -> Credit Risk

Monitoring -> Credit Limit Request:


o Web Interface for Credit Limit Request

See also

The central release note for the FSCM Functions 2 (FIN_FSCM_CCD_2)

business function

FIN_FSCM_CCD_2: Web Dynpro Application for Credit Limit Request (New)

Use


FSCM Functions 2 you can use the new Web Dynpro ABAP-based application for

creating and changing credit limit requests. The new application features a streamlined

user interface your employees can access using SAP NetWeaver Portal or SAP

NetWeaver Business Client. A guided procedure takes you through the various steps

for creating a credit limit request, and facilitates access even for occasional processors.

This new Web Dynpro application provides you with a new Web interface that you can

use as an alternative to the existing SAP GUI interface.


o Enterprise Services for Credit Limit Request (New)

o BP for Credit Manager (SAP ERP) 1.4 (Changed)

In the SAP Library choose Roles -> Business Packages -> Business Package

for Credit Manager (SAP ERP) 1.4


You configure the use of the Web services in SOA Management.


You make the settings for this function and also the implementation of the

corresponding mapping BAdIs if required in Customizing under the following nodes:

Financial Supply Chain Management -> Credit Management -> Credit Risk

Monitoring -> Credit Limit Request:


o Web Interface for Credit Limit Request

You use the Business Package for Credit Manager (SAP ERP) 1.4 to do your

configurations in SAP NetWeaver Portal or SAP NetWeaver Business Client.

See also

The central release note for the FSCM Functions 2 (FIN_FSCM_CCD_2)

business function

FIN_FSCM_CCD_2: Enterprise Services for Dispute Case Processing

(New)

Use


FSCM-Functions 2 you can use new operations in the process component Dispute

Managementto create, change, read, and find dispute cases.

Operations

o Create Trade Receivables Payables Dispute Case (asynchronous)

o Confirm Trade Receivables Payables Dispute Case (asynchronous)

o Change Trade Receivables Payables Dispute Case (asynchronous)

o Cancel Trade Receivables Payables Dispute Case (asynchronous)

o Check Trade Receivables Payables Dispute Case Update

o Update Trade Receivables Payables Dispute Case

o Read Trade Receivables Payables Dispute Case

o Find Trade Receivables Payables Dispute Case Basic Data By Elements

o Check Trade Receivables Payables Dispute Case Creation

The three operations Check Trade Receivables Payables Dispute Case Update,

Update Trade Receivables Payables Dispute Case and Read Trade Receivables

Payables Dispute Case are used for the new Web interface for changing dispute

cases. For more information about the new Web interfaces, see the release note Web Dynpro Application for Dispute Case Processing (New).


You configure the use of the Web services used by the Web interface in SOA

Management.


You make the settings for this function and also, if necessary, the implementation of the

corresponding mapping BAdIs in Customizing under the following nodes: Financial

Supply Chain Management -> Dispute Management -> Dispute Case Processing:


o Web Interface for Dispute Case Processing

See also

Central release note for the FSCM Functions 2 (FIN_FSCM_CCD_2)

business function

FIN_FSCM_CCD_2: Web Dynpro Application for Dispute Case Processing (New)

Use


FSCM-Functions 2 you can use the new Web Dynpro ABAP-based application for

changing dispute cases. The new application features a streamlined user interface your

employees can access using SAP NetWeaver Portal or SAP NetWeaver Business

Client.

Whereas a regular processor processes the dispute case using the existing complete

interface, the Web interface is particularly suitable for an occasional processor. Since it

provides a reduced, clearly arranged interface with restricted functions, it simplifies

dispute case processing for an occasional processor.

This new Web Dynpro application provides you with a new Web interface that you can

use as an alternative to the existing Sap GUI interface, particularly for occasional

processors.


o Enterprise Services for Dispute Case Processing (New)

o BP for Dispute Manager (SAP ERP) 1.4 (changed)

See the SAP Library under Roles -> Business Packages (Portal Content) ->

Business Package for Dispute Manager (SAP ERP) 1.4.


You configure the use of the Web services in SOA Management.


You make the settings for this function and also, if necessary, the implementation of the

corresponding mapping BAdIs in Customizing under the following nodes: Financial

Supply Chain Management -> Dispute Management -> Dispute Case Processing:


o Web Interface for Dispute Case Processing

You use the Business Package for Dispute Manager (SAP ERP) 1.4 to do your

configurations in SAP NetWeaver Portal or SAP NetWeaver Business Client.

See also


function

Business Function FSCM Integration 2

FIN_FSCM_CCD_INTEGRATION: Business Function FSCM Integration 2

Use

As of SAP ECC 6.0, enhancement package 4 (SAP_APPL 604), you can use the

FSCM-Integration 2 business function. If you want to use this business function, you

must also have activated the FSCM Functions 2 business function in the SAP

Financial Supply Chain Management system in which SAP Collections Management,

SAP Credit Management, or SAP Dispute Management runs. Both business functions

contain new capabilities for the following components:

SAP Collections Management (FIN-FSCM-COL)

If you are using several FI systems and want to use a central system for SAP

Collections Management, there are functions available for replicating customer master

data from these FI systems in the business partner master data of central SAP

Collections Management. Additional release note in the SAP Collections Management

system: FIN_FSCM_CCD_2: Master Data Synchronization for Several FI Systems

(New)

In receivables processing, you can use the SAP Dispute Management function to add

customer-disputed objects to dispute cases. This function was already available with

business function FSCM Integration as of SAP ECC 6.0, Enhancement Package 2

(SAP_APPL 602). Additional release note: FIN_FSCM_CCD: Customer-Disputed

Objects in Receivables Processing (New) in the SAP Collections Management

system

To focus on processing your outstanding receivables, you can include the head office -

branch office relationships of your customers, providing you have mapped them in

Accounts Receivable. Additional release note: FIN_FSCM_CCD: Head Office -

Branch Office Relationships (New) in the SAP Collections Management system

SAP Credit Management (FIN-FSCM-CR)

If you are using several FI or SD systems and want to use a central system for SAP

Credit Management, there are functions available for replicating customer master data

from several source systems in the business partner master data of central SAP Credit

Management. Additional release note in the SAP Credit Management system:


There are Enterprise Services (ES) and Web interfaces available for processing credit

limit requests. Additional release notes in the SAP Credit Management system:

o FIN_FSCM_CCD_2: Enterprise Services for Credit Limit Request (New)

o FIN_FSCM_CCD_2: Web Dynpro Application for Credit Limit Request (New)

SAP Dispute Management (FIN-FSCM-DM)

You can use brand new functions, such as the creation and processing of dispute

cases for customer-disputed objects. In addition, you can use the Document Changes

from Dispute Cases function. Both functions were already available with business

function FSCM Integration as of SAP ECC 6.0, Enhancement Package 2

(SAP_APPL 602). Additional release notes in the dispute case processing system:

o FIN_FSCM_CCD: Customer-Disputed Objects in Dispute Cases (New)

o FIN_FSCM_CCD: Document Changes from Dispute Cases (New)

There are Enterprise Services (ES) and Web interfaces available for processing

dispute cases. Additional release notes in the dispute case processing system:

o FIN_FSCM_CCD_2: Enterprise Services for Dispute Case Processing (New)

o FIN_FSCM_CCD_2: Web Dynpro Application for Dispute Case Processing

(New)


SAP Collections Management

o For master data mapping, you make the following settings in the FI systems as

an enhancement to the settings in the SAP Collections Management system:

- Mapping in FI-AR

- Mapping in SAP Collections Management

o You make the settings for including disputed objects in dispute cases

(particularly the activation of this function) in Customizing of component SAP

Dispute Management under the following nodes: Financial Supply Chain

Management -> Dispute Management -> Process Integration with Accounts

Receivable Accounting -> Customer-Disputed Objects in Dispute Cases

- Process Settings for Customer-Disputed Objects in

Dispute Case (mandatory)

- Implement Customer Enhancement Assignment of Open

Items to Dispute Cases (optional)

- Implement Customer Enhancement Calculation of

Customer-Disputed Amount (optional)

o To take the head office - branch office relationships into account, make the

following settings:

- Activate Distribution for each Company Code (mandatory)

- BAdI: Define Customer for Collections Management

(optional)

SAP Dispute Management

o You make the settings for including disputed objects in dispute cases

(particularly the activation of this function) in the FI settings under the following

nodes as an enhancement to the settings in the SAP Dispute Management

system: Financial Supply Chain Management -> Dispute Management ->

Process Integration with Accounts Receivable Accounting -> Customer-

Disputed Objects in Dispute Cases:

- Process Settings for Customer-Disputed Objects in

Dispute Case (mandatory)

- Implement Customer Enhancement Assignment of Open

Items to Dispute Cases (optional)

- Implement Customer Enhancement Calculation of

Customer-Disputed Amount (optional)

o If you are using the integration of application component SAP Dispute

Management with the application component SAP Biller Direct, you can

implement the new BAdI for changing the case type when creating dispute cases

from SAP Biller Direct: Define the Case Type for SAP Biller Direct (FDM_AR_BD_DEF_CASE_TYPE) (optional)

See also

For more information, see the following documents:

o Central release notes for the business function FSCM Functions 2

(FIN_FSCM_CCD_2) in the SAP Financial Supply Chain Management system in

which SAP Collections Management, SAP Credit Management, or SAP Dispute

Management runs.

o SAP Library under Business Function Sets and Business Functions ->

Enterprise Business Functions -> Financials -> Financial Supply Chain

Management:

- FSCM Functions 2

- FSCM Integration 2

Business Function Cash Management: Additional Account

Assignments

FIN_TRM_CM_DIMENSIONS: CLM-CM, Additional Account Assignments

Use

As of SAP ECC 6.0, Enterprise Extension Financial Services, Enhancement Package 4

(SAP_APPL 604), you can use the Business Function CLM-CM, Additional Account

Assignments.

This business function enables you to update the account assignments Segment and

Profit Center and Fund and Grant to SAP Cash Management (FIN-FSCM-CLM-CM), in

addition to the business area. This provides you with supplementary options for

differentiation in the cash position and liquidity forecast. If you are using SAP Public

Sector Management (PSM), the cash position and liquidity forecast also provide you

with the option of displaying a funds overview for the fund and grant account

assignments.

If you have activated the new general ledger in Financial Accounting, you can also take

into account document splitting for the account assignments relevant to cash

management.

Effects on Customizing and Existing Data

1. You need to define the account assignments in SAP Cash Management that are

to be updated. You do this in Customizing for Financial Supply Chain

Management by choosing Cash and Liquidity Management -> Cash

Management -> Basic Settings -> Define Account Assignments and Document

Splitting.

If you are using the new general ledger and have activated document splitting,

you can define for the relevant account assignments that document splitting is

also taken into account in SAP Cash Management.

Note:

If this IMG activity does not contain any entries for a particular company code,

the business area for this company code is updated to SAP Cash Management.

1. Regeneration of Cash Management Data

To use the new account assignments and document splitting, you need to trigger

the data setup in SAP Cash Management for all company codes. To do this,

choose Cash Management -> Tools -> Prepare Production Startup and Data

Setup and use the Cash Management Implementation Tool (transaction FDFD).

Since the activation of the business function provides the system with access to

new totals records tables (table FDSB2 for bank accounts and bank clearing

accounts and table FDSR2 for planning groups), the new totals records tables

are filled as part of the data regeneration.

Refer also to the notes in the implementation tool documentation. Choose Help -

> Application Help.

Note:

You can also use program RFFDFT604. However, this is only recommended for

company codes relevant to Cash Management for which no settings have been

made under Define Account Assignments and Document Splitting, since the

program only transfers the data from the old totals records to the new tables.

(Fields for the new account assignments are not filled).

1. Distributed SAP Cash Management

If you are using distributed Cash Management (TR-CM link), then all the systems

need to be transferred to the central Treasury system.

The following functions in the area menu have been changed:

o Changes in the Cash Position (FF7A) and Liquidity Forecast (FF7B):

- You can use the account assignments for differentiation purposes in the

cash position and liquidity forecast display screens.

- If you are using SAP Public Sector Management, a funds overview is

displayed for the account assignments Fund or Fund and Grant.

- If you are using the new general ledger, you can also use document

splitting based on these account assignments. The cash position and

liquidity forecast also contain the new Entry View parameter.

o You can assign the new account assignments when you create payment advice

notes and noted items under Cash Management -> Incomings-> Memo Record -

> Create (transaction FF63) -> Extras -> Additional Account Assignments.

o The following functions now also take into account the additional account

assignment elements:

- Enhanced Reconciliation of Cash Management (Report RFFDEA00)

The transaction is called using the implementation tool (transaction

FDFD).

- Payment Advice Journal (entered and changed planned items) (FF-9)

- Reconciliation of Payment Advice and Account (transaction FF.7)

- Change Memo Record Using List (transactions FF6A and FF6B)

See also

For more information, see the documentation for the business function. You can call

this using transaction SFW5 or you can refer to the SAP Library under Business

Functions (SAP Enhancement Package 4 for SAP ERP 6.0) -> Enterprise Business

Functions -> Accounting -> Financial Supply Chain Management -> CLM-CM,

Additional Account Assignments.

Management Accounting

Business Function CO, Allocations

Business Function CO, Allocations (New)

Use

As of SAP ECC 6.0, Enterprise Extension Controlling, Enhancement Package 4 (CO-

OM-CCA), the CO, Allocations (CO_ALLOCATIONS) business function is available.

With this business function you can use the new features of the SAP Allocation Tool for

activity allocation and for the calculation of overhead:

In classic Overhead Cost Controlling, overhead is posted periodically in background

processing. Real-Time Overhead Calculation enables you to post overhead

simultaneously with an activity allocation document. This might be necessary when

processing Special Valuation Dates.

For more information about the new features, see the following release notes:

o Release Information Valuation Date for Activity Allocation and

Overhead

o Release Information Transaction-Based Calculation of Overhead


Note that there are required Customizing settings described in each release note.

See also

For more information about Cost Center Accounting, see the SAP Library under http://help.sap.com -> SAP ERP -> SAP ERP Enhancement Packages -> SAP

Enhancement Package 4 for SAP ERP 6.0 -> SAP Library -> SAP ERP Central

Component -> Accounting -> Controlling (CO) -> Cost Center Accounting (CO-OM-

CCA).

For more information about business functions, see the SAP Library under Business

Function Sets and Business Functions -> Enterprise Extensions: Business Functions ->

Financials Extension (EA-FIN).

Valuation Date for Activity Allocation and Overhead

Use


OM-CCA), the CO, Allocations (CO_ALLOCATIONS) business function provides you

with a new function for using the valuation date for activity allocation and overhead.

You can use this function for the following business transactions:

o Manual Cost Allocation (KAMV) - transaction KB21n

o Actual Activity Allocation (RKL) - transaction KB15n

o Repost Costs (RKUI) - transaction KB11n

o Repost Revenues (RKU2) - transaction KB41n

In Overhead Cost Controlling, you can also use the valuation date to determine prices

and overhead costs based on the document date or on the date determined by a Business Add-In (BAdI). The new BAdI: Maintain Valuation Date is available for this.

The valuation date is stored in the cost document header and you can create it for

direct activity allocation (transaction KB21n) or manual cost allocation. In addition, you

can use the date from the time sheet (such as CAT2) during transfer to Controlling (for

example CAT5, CAT7, CAT 9) as the special valuation date (see Customizing activity Special Valuation Date Settings).


Make the settings for these new functions in Customizing for Cost Center Accounting

under Actual Postings -> Period-End Closing -> Overhead -> Maintain Realtime

Overhead Calculation:

o Activate Date From Time Sheet as Document Date for

Confirmation (transaction RTOHC03)

o Special Valuation Date Settings (transaction RTOHC04)

o BAdI: Maintain Valuation Date (transaction RTOHC05)

Transaction-Based Calculation of Overhead (New)

Use


OM-CCA), the CO, Allocations (CO_ALLOCATIONS) business function provides you

with a new function for transaction-based calculation of overhead. You can use this

function for the following business transactions:

o Manual Cost Allocation (KAMV) - transaction KB21n

o Actual Activity Allocation (RKL) - transaction KB15n

o Repost Costs (RKUI) - transaction KB11n

o Repost Revenues (RKU2) - transaction KB41n

You can use transaction-based overhead for specific business transactions to post a

special overhead document at the same time as you post the document that causes the

overhead costs. When the original document is reversed, the overhead documents are

also reversed. If you also use periodic overhead, the system does not take the selected

transactions into account during periodic posting, so as to avoid duplicate overhead

calculation. You can display transaction-based overhead documents for a specific

document by using the Document Relationship Browser.

Reposting Transaction-Based Overhead:

You can use this function to repost transaction-based overhead if changes or

corrections have been made to the costing sheets or to the costing sheet assignment in

the master data. You can use transaction RTOHC_REPOST to do so.

Note: If you have already posted business transactions for which you have activated

transaction-based calculation, you must use transaction RTOHC_UPGRADE to

calculate the overhead costs for these transactions in the time period in which you have

activated transaction-based calculation.


Make the settings for these new functions in Customizing for Cost Center Accounting

under Actual Postings -> Period-End Closing -> Overhead -> Maintain Realtime

Overhead Calculation:

o Activate Realtime Overhead Calculation (Transaction RTOHC01)

o Activate Overheads for Controlling Area and Business

Transaction (Transaction RTOHC02)

Caution: If you change the time period and remove Customizing entries, it can lead to

inconsistent data in productive systems.

Note: If you have activated a controlling area using the Customizing activity Activate

Realtime Overhead Calculation, you can no longer deactivate this controlling area. The

controlling area is active if you have selected and saved the Realtime Overhead

Calculation flag. This feature is intended to prevent inconsistencies during a period or a

year.

In addition, once you have activated the controlling area and the business transaction,

you can no longer execute the standard overhead transaction. When you execute a

business transaction for the first time, a message appears.

Business Function Financials Master Data Management: Chart

of Accounts

FIN_MDM_ACC: Business Function Financial Master Data Management

(New)

Use

As of SAP Business Suite Foundation 7.01 (SAP_BS_FND 701) , you can use the

business function Financial Master Data Management: Charts of Accounts. You can

use this business function to request changes to financial master data of the enterprise,

centrally consider and approve the request, and to execute the master data changes.

Afterwards you can check the changes and approve the final check. The entire

approval process is controlled via workflow.

The system stores the master data records in editions, which you can display and

analyze at any time. This enables you to track all legacy master data records and

individually document each change.

You use enterprise services to distribute new and modified chart of accounts master

data. You also have the option of uploading a file with the master data into your

transactional systems.

Note:

The functions of this business function are available only if you have installed the

following software components:

o SAP Business Suite Foundation (SAP_BS_FND)

The business function is not usable with this software component alone. Do not

activate the business function if you have installed only this software component

and none of the other following software components.

o FINBASIS

If you have installed this software component, you can activate the business

function. In this case, the functions mentioned earlier are available. If you want to

import new or changed master data into transaction systems, one of the

following software components must be installed.

o SEM-BW

If you have installed this software component and activated the business

function, you can import the master data of the group chart of accounts that you

created or changed with this business function into the Business Consolidation

(FIN-SEM-BCS) application component.

o Logistics and Accounting (SAP_APPL)

If you have installed this software component and activated the business

function, you can import the master data of the chart of accounts that you

created or changed with this business function into the General Ledger

Accounting (FIN-SEM-BCS) application component.


o FIN_MDM_ACC: Financial Master Data Management: Charts of

Accounts (New)

This link works only if you have installed the FINBASIS software component.

o FIN_MDM_ACC: Importing Group Chart of Accounts Master

Data (New)

This link works only if you have installed the SEM-BW software component.

o FIN_MDM_ACC: Importing Chart of Accounts Master Data

(New)

This link works only if you have installed the Logistics and Accounting

(SAP_APPL) software component.

FIN_MDM_ACC: Financial Master Data Management: Charts of Accounts (New)

Use

As of SAP enhancement package 4 for SAP ERP 6.0 (FINBASIS 604), SP03, you

can use the business function Financial Master Data Management: Charts of

Accounts. You can use this business function to manage the financial master data of

your enterprise and track the changes made to it. The approval process is controlled

via workflow. With the help of Enterprise Services, you can distribute master data

changes or download a file that can be uploaded to the operational systems.


Perform the Customizing activities under Cross-Application Components ->

Processes and Tools for Enterprise Applications -> Financial Master Data

Management.

FIN_MDM_ACC: Importing Group Chart of Accounts Master Data (New)

Use

As of SAP enhancement package 4 for SAP ECC 6.0 (SAP_APPL 604) you can use

enterprise services to import group chart of accounts master data that has been

created or changed with the functions in the new business function Financial Master

Data Management: Charts of Accounts.


You customize the activities under Cross-Application Components -> Processes

and Tools for Enterprise Applications -> Financial Master Data Management ->

Enterprise Services for Business Consolidation.

FIN_MDM_ACC: Import Chart of Accounts Master Data (New)

Use

From SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), you can use

Enterprise Services to import chart of accounts master data that has been created or

changed using the functions of the new business function Financial Master Data

Management: Charts of Accounts.


Perform the IMG activities under Cross-Application Components -> Processes and

Tools for Enterprise Applications -> Financial Master Data Management ->

Enterprise Services for General Ledger Accounting.

Treasury and Risk Management

Business Function TRM: Correspondence Framework

FIN_TRM_CORR_FW: TRM, Correspondence Framework (New)

Use


(EA-FS 604), you can use the business function TRM, Correspondence Framework.

This business function provides you with the new correspondence framework. The

existing correspondence functions have been replaced. The new correspondence

function enables you to generate correspondence objects both automatically and

manually for financial transactions and securities accounts. To do this, you can use the

new correspondence monitor (transaction FTR_COMONI) to manage correspondence

objects. The correspondence function provides you with a status management function

and an automatic matching and assignment process. You can also define whether the

automatic matching process sets the status of the financial transaction automatically to

settled, based on the product type.

The system is preconfigured for the following SWIFT messages. However, you can also

make changes or create new formats using the existing settings.

o MT300 Foreign Exchange Confirmation

o MT320 Fixed Loan/Deposit Confirmation

o MT395 Queries

o MT399 Free Format Message

o MT502 Order to Buy/Sell

o MT509 Trade Status Message

o MT515 Confirmation of Purchase/Sale

o MT535 Statement of Holdings

o MT536 Statement of Transactions

o MT540 Receive Free

o MT541 Receive against Payment

o MT542 Deliver Free

o MT543 Deliver against Payment

o MT544 Receive Free Confirmation

o MT545 Receive against Payment Confirmation

o MT546 Deliver Free Confirmation

o MT547 Deliver against Payment Confirmation

o MT548 Settlement Status and Processing Advice

o MT566 Corporate Action Confirmation


Before the activation of the business function your existing system settings and application data for correspondence have to be transferred from the old tables to new

tables. For more information, see in the SAP Library Conversions of Existing

Correspondence Data to Correspondence Framework.

In addition, the activation of the business functions displays the following changes in

the area menu and on the user interfaces.

New Functions in the Transaction Manager Area Menu

In the areas Money Market, Foreign Exchange, Derivatives, Commodities, Securities

and Debt Management, you can find the new Correspondence functions under Back

Office:

o Correspondence Monitor (FTR_COMONI)

o Individual Functions

- Create Correspondence Object (FTR_COCREATE)

- Send Correspondence (FTR_COSEND)

- Match Correspondence (FTR_COMATCH)

- Import Incoming Messages (FTR_IMPORT)

o Alerts

- ALE Status Monitor (BD87)

- Send Correspondence Alerts (FTR_ALERT_BATCH)

o Master Data

- Assign Business Partner Group and Profile to Business Partner

(FTR_BP_ASSIGN)

- Assign BIC and External Securities Account ID to Business Partner

(FTR_BP_BIC)

- Derivation of Settlement Instructions (only available in the Securities area)

- Define Correspondence Activities for Securities Account Transfers (only

available in the Securities area)

Changed Functions in the Tranaction Manager Area Menu

As part of the developments for this business function, changes have been made to the

UIs for the following functions:

o Alert Monitor (FTR_ALERT)

o Securities Account Transfer (FWDU)

Replaced Functions

The following transactions are now obsolete; the transactions that were previously used

for the correspondence in the application menu of the Transaction Manager and

the functions for the standing instructions for the correspondence in the business

partner menu. They have been replaced by the new correspondence functions:

o Outgoing Correspondence (TBZ1)

o Incoming Confirmations (TBZ2)

o Incoming Confirmations (TBZ3)

o Incoming Confirmations (TBZ3A)

o Incoming Confirmations, Currency Options(TBZ4)

o Overdue List of Counterconfirmations (TBZ5)

o Match Incoming SWIFT Confirmation (TBZ6)

o Delete Correspondence Planned Records (TBZ7)

o Correspondence Overview (TBZ8)

o Correspondence Monitor (TBZ11)

o Overview of Reset Counterconfirmations (TBZ12)

o Printer Override (TBZ13)

o ALE Monitor (TBZ14)

o Status Monitor IDoc Confirmations (TBZ15)

o Incoming Confirmations: Agent Assignment (TBZ16)(IMG)

o Incoming Confirmation: Partner Assignment (TBZ17)

o SWIFT Generation MT300 (TSW1)

o SWIFT Generation MT320 (TSW2)

o SI: Correspondence (TBI5)


The new correspondence functions need to be removed from the role menus and

replaced by the new functions. You also need to assign the new transactions to the

corresponding profiles.


When you activate the business function, you will be able to see some Customizing

changes in Transaction Manager:

New IMG Activities

The following IMG activities are available under Transaction Manager -> General

Settings -> Correspondence:

o General Settings

- Define Business Partner Group

- Assign Attributes for Business Partner Groups

- BAdI: Influence Correspondence Monitor Selection Criteria

- BAdI: Fill Fields in Correspondence Objects (Customer-Includes)

- BAdI: Influence Events After Saving Correspondence Objects

o Correspondence Messaging Interface

- Define Communication Channels

- Define Format Metatypes

- Define Formats

- Define Correspondence Recipient Types

- Define Correspondence Classes

- Assign Formats

- Define Format-Dependent Mapping Rules

- Define Communication Profiles

- Dynamic Table Assignment for Configuration

- BAdIs

- BAdI: Determine Check Value for Dynamic Table Selection

- BAdI: Channel-Dependent Mandatory Steps (Publish and Subscribe

Events)

- BAdI: Channel-Dependent Optional Steps (Process Events)

- BAdI: Format-Dependent Optional Steps (Publish and Subscribe Events)

- BAdI: Format-Dependent Mandatory Steps (Process Events)

- BAdI: Format-Dependent Optional Steps (Process Events)

- BAdI: Metatype-Dependent Mandatory Steps (Process Events)

- BAdI: Metatype-Dependent Optional Steps (Process Events)

o Correspondence Activities

- Define Correspondence Activities – Money Market

- Define Correspondence Activities – Foreign Exchange

- Define Correspondence Activities - Derivatives

- Define Correspondence Activities - Securities

o Release

- Assign Release Procedure to Release Object

- Assign Rules to Release Steps

- Assign Workflow and Sub-Workflow to Release Procedure

- BAdI: Enter Customized Attributes to Determine Release Procedure

o Match Correspondence Objects

- Define Rules for Matching Correspondence Objects

- BAdI: Influence Matching of Correspondence Objects

o Alert

- Define Alert Categories

- Money Market: Assign Alert Categories

- Foreign Exchange: Assign Alert Categories

- Derivatives: Assign Alert Categories

- Securities: Assign Alert Categories

- BAdI: Alert Attributes

Replaced IMG Activities

The Correspondence structure node has been removed under Transaction Manager ->

Money Market/Foreign Exchange/Securities/Listed Derivatives/OTC Derivatives ->

Transaction Management. The following activities have now become obsolete:

o Define Correspondence Types

o Define Correspondence Activities

o Define Printer Options

o Define Fax Options (Spool)

o Incoming Confirmations: Agent Assignment (Money Market/Foreign Exchange)

o Customer enhancements

o Tools

- Copy Standard Texts

- Transport Standard Texts

- Check

See also

See also the documentation for the new functions in the SAP Library under SAP ERP

Central Component -> Accounting -> SAP Financial Supply Chain Management (FIN-

FSCM) -> SAP Treasury and Risk Management (TRM) -> Transaction Manager ->

Back Office -> Correspondence Framework..

Business Function TRM, Hedge Management for FAM

FIN_TRM_INS_HM: TRM, Hedge Management for FAM (new)

Use

As of SAP ECC 6.0, Enterprise Extension Financial Services, Enhancement Package

4, (EA-FS604), the business function TRM, Hedge Management for FAM is available.

With this business function, you can use hedging relationships to assign and designate

securities and forward security transactions. The new development is summarised in

this release note:

o Hedging Relationships

You can use hedging relationships to assign hedged items (securities) to

hedging instruments (forward security transactions). If prerequisites (for example,

documentation and effectiveness test) are satisfied, the hedging relationship can

be designated, and hedge accounting regulations can be used. As long as the

hedging relationship is fulfilling the requirements for hedge accounting, the

respective posting rules are used.

o Position Management and Accounting

You can split up a security position according to different subpositions. This

enables you to differentiate between hedged portions of a security and

freestanding portions.

o Effectiveness Test of Hedging Relationship

You can use the dollar-offset-method to calculate the effectiveness of a hedging

relationship. The effectiveness test can also be executed from the master data of

the hedging relationship.

o Documentation of Hedging Relationship

Within hedging relationships, you can create documentation automatically or

manually (upload or enter). The documentation is one of the prerequisites for the

use of hedge accounting. The documents are stored with the document

management service. You have a single point of entry for information gathering

during audits. Documentation can be easily created by using the automatic

functionality based on PDF forms.

o Legacy Data Conversion

You can make a legacy data conversion in order to continue hedging in the new

enhancement. To do this, you dedesignate all hedging relationships in the old

system and transfer all hedge components to the new positions and

subpositions. The key date of legacy data transfer will have to be equal for all

positions and subpositions.


You can transfer already existing and designated hedging relationships into the system

per key date. You can transfer values for the hedged item and hedging instruments

similarly to the general legacy data transfer in TRM-TM. For further information please

refer to the customizing guide.


The system supports the initialization of designated hedging relationships in a new

valuation area.


Carry out the following Customizing activities as requires:

Define and Activate Groups

Define Number Ranges for Hedging Relationships

Define Number Ranges for Hedged Items

Define Number Ranges for Hedging Instruments

Assign Number Ranges

Effectiveness Test Method

Different Setting to Delivery Scenarios: Hedged Item

Different Setting to Delivery Scenarios: Hedging Instrument

Define Hedging Profiles

Define Update Types and Assign Usages

Assign Update Types for Hedge Man. Business Transactions to

Product

Assign Release Procedure to Release Object

Data for Securities with Subpositions

Data for OTC Transactions with Subpositions

Data for Futures with Subpositions

Execute Data Transfer for Hedge Management (FAM)

Cancel Data Transfer for Hedge Management (FAM)

Initialize Hedging Relationships in the Parallel Valuation Areas

Reverse the Initialization of Hedging Relationships in the Parallel Valuation Areas

See also

SAP library under SAP Financial Supply Chain Management (FIN-FSCM) -> SAP

Treasury and Risk Managementt (TRM) -> Transaction Manager -> Hedge

Management for FAM

Business Function TRM, Hedge and Exposure Management,

SWIFT

FIN_TRM_LR_FI_AN_2: TRM, Hedge and Exposure Management, New

Financial Product (new)

Use


(EA-FS 604), you can use the business function TRM, Hedge and Exposure

Management, New Financial Product.

This business function provides you with various enhanced functions in SAP Treasury

and Risk Management. The new Exposure Management 2.0 enables you to manage

exposure items for open commodity items and open currency items. In the Hedge

Management area, you can map the hedging of commodity price risks using the

corresponding hedging transactions in the Transaction Manager.

The complete integration with the analyzers also enables you to run NPV and VaR

analyses for the exposure items. To meet the accounting requirements of IAS39 and

FAS133 with regard to measuring the effectiveness of hedging relationships, the Hedge

Management area now provides you with the option of running retrospective and

prospective effectiveness tests based on linear regression analyses for exposures,

hedged items, and hedging instruments. You can calculate the following parameters to

check the effectiveness:

o Gradient of the regression lines

o Intercept of the regression lines

o Coefficient of determination R²

o t-test

o F-test

There is now also a new product category available; the forward securities

transaction. You can map the life cycle of forward securities transactions from

rollover, advance maturity, delivery at maturity, and dividend adjustment through cash

settlement and physical delivery. You can create forward securities transactions for the

following product categories:

o Stocks (010)

o Investment certificates (020)

o Bonds (040)

o Shareholding (160)

To fulfill the P-GAAP requirements for group accounting when making an investment

exceeding 50% in a company, the following position components have been integrated

in position management: 1025 Value Adjustment of Gains, 1026 Value Adjustment of Losses, and 1027 Original Value Adjustment.

To meet the disclosure requirements of IFRS 7 (as of 01/01/2007), you can receive a

risk statement that includes all the financial transactions and objects in SAP Treasury and Risk Management and exposure items which are then evaluated

with regard to market risk.


By activating the business function, the following changes become visible in the area

menu and application interfaces.

New Functions in the TRM Area Menu

o Exposure Management 2.0

- The following functions in Exposure Management 2.0 are available in the

area menu of the Transaction Manager under Hedge Management:

See also:FIN_TRM_LR_FI_AN_2: Exposure Management

2.0 (new)

- Under Treasury and Risk Management -> Market Risk Analyzer -> Master

Data -> Derive Rule Values -> Operative Exposures, you can use the

function Derive Analysis Parameters from Operative Exposures

(transaction AFO_FOI_RULE_EXP).

o Forward Securities Transactions

The function Forward Securities Transactions: Collective Processing (TFCP) is

available under Securities -> Back Office -> Collective Processing -> Forward

Securities Transactions.

The transactions Create Financial Transaction (FTR_CREATE) and Edit

Financial Transaction (FTR_EDIT) have been revised and now also provide the

new transactions for creating and editing forward securities transactions.

- Create Forward Securities Transaction (TF01)

- Change Forward Securities Transaction (TF02)

- Display Forward Securities Transaction (TF03)

- Settle Forward Securities Transaction (TF04)

- Deliver Forward Securities Transaction (TF05)

- Reverse Forward Securities Transaction (TF06)

- Roll Over Forward Securities Transaction (TF07)

- History for Forward Securities Transaction (TF08)

- Forward Securities Transaction: Advance Maturity (TF09)

- Forward Securities Transaction: Dividend Adjustment (TF11)

o To meet the disclosure requirements for financial instruments in accordance with

IFRS 7, the following reports are provided under Transaction Manager ->

Information System -> Reports -> Reporting -> ISFRS 7:

- Currency Risk (TIS_IFRS7_1)

- Interest Rate Risk (TIS_IFRS7_2)

- Interest Sensitivities(TIS_IFRS7_3)

- Market Values (TIS_IFRS7_4)

- Market Values (with Sensitivities) (TIS_IFRS7_5)

- Market Value Changes (TIS_IFRS7_6)

- Yield Risk Analysis (TIS_IFRS7_7)

- Detailed reports

- Currency Risk (Detail) (TIS_IFRS7_D1)

- Interest Rate Risk (Detail) (TIS_IFRS7_D2)

- Interest Sensitivities (Detail) (TIS_IFRS7_D3)

- Market Values (Detail) (TIS_IFRS7_D4)

- Market Values (with Sensitivities) (Detail) (TIS_IFRS7_D5)

- Market Value Changes (Detail) (TIS_IFRS7_D6)

- Yield Risk Analysis (Detail) (TIS_IFRS7_D7)

Changed Functions in the TRM Area Menu

As part of the developments for this business function, changes have been made to the

UIs for the following functions:

o Edit Financial Object (JBDO)

o Define and Set Up Evaluation Type (JBREVAL)

o Scenario Management (TV21)

o Edit Financial Transactions (FTR_CREATE, FTR_EDIT)

o Effectiveness Test (THM80)

o Subledger Positions (TPM12)

o Alert Monitor (FTR_ALERT)

o Hedge Plan List (THMEX)

Renaming

The previous Exposure Management area has been renamed Exposure

Management 1.0, since as of this enhancement package, the additional Exposure Management 2.0 exists.


When you activate the business function, you will be able to see some Customizing

changes in Treasury and Risk Management:

New IMG Activities

o The Settings for Exposure Management 2.0 are under Transaction Manager ->

General Settings -> Hedge Management.

See also: FIN_TRM_LR_FI_AN_2: Exposure Management 2.0 (new)

o You can find the following new IMG activities under Treasury and Risk

Management -> Basic Analyzer Settings -> Automatic Integration of Financial

Objects in Transaction Master Data -> Operative Exposures:

- Activate/Deactivate Financial Object Integration

- Define Derivation Strategy for Exposures

- BAdI: Exposure

o There is a new BAdI available; Class, Convert ID Number

(TPM_SEC_CONV_SEC_ID) which can be found under Listed

Derivatives/Securities -> Master Data -> Conversions: Internal IDs <-> External

IDs

Other Changes

o The Exposure Management IMG structure under Transaction Manager ->

General Settings -> Hedge Management has been renamed Exposure

Management 1.0.

o The IMG activity Assign Update Types for Derived Business Transactions now

includes the new Value Adjustment tab page to assign the update types required

for mapping Purchase-GAAP Accounting.

o New settings are available for the regression analysis under:

- Treasury and Risk Management -> Transaction Manager -> General

Settings -> Hedge Management -> Effectiveness Test -> Define

Calculation Types. You can now use the fields Effectiveness Method

(offset method or regression analysis) and Significance Level.


Settings -> Hedge Management -> Effectiveness Test -> Define

Assessment Types. The Regression Analysis area is now provided in

which you can define intervals and parameters that can be used to

determine the effectiveness of a hedging relationship. You can also define

the values to be calculated.


Settings -> Hedge Management -> Effectiveness Test -> Define Hedge

Strategies. Various new fields are now provided to define a hedge strategy

that uses the regression analysis. Among other things, the number of data

points to be determined is entered and the data points are specified.

See also

o FIN_TRM_LR_FI_AN_2: Exposure Management 2.0 (New)

o See also the documentation for the new functions in the SAP Library under SAP

ERP Central Component -> Accounting -> SAP Financial Supply Chain

Management (FIN-FSCM) -> SAP Treasury and Risk Management (TRM).

FIN_TRM_LR_FI_AN_2: Exposure Management 2.0 (New)

Use


(EA-FS 604), a new Exposure Management feature is available, called Exposure

Management 2.0.

The purpose of this new feature is to manage and monitor the extent to which your

business is exposed to the following risk types:

o Foreign exchange

If you do business in more than one currency, you might be running the risk of

losses arising from exchange rate fluctuations.

o Commodities

Raw material prices can vary substantially, exposing you to the possibility of

losses on advance sales or purchases.


Implementing Exposure Managment 2.0 has no effect on existing data.


The configuration steps needed for Exposure Management can be found in

Customizing under Financial Supply Chain Management -> Exposure Management

2.0. The steps are as follows:

o Define Global Setting

o Define Periods

o Define Exposure Activity Types

o Define Product Types for Exposures

o Define Exposure Position Types

o Define Exposure Fields Derivation Strategy

o Settings for Free Attributes

- Define Headings, Values, and Texts for Short Attributes

- Define Headings, Values, and Texts for Medium Attributes

- Define Headings, Values, and Texts for Long Attributes

o Release

- Assign Users/Roles to Release Steps

- Assign Release Procedure to Release Object

- Assign Workflow and Sub-Workflow to Release

Procedure

o Business Add-Ins (BAdIs) for Exposure Management

- BAdI: Enhancement for Exposure Fields Derivation

- BAdI: Enhancement for Commodity Splits

- BAdI: Enhancement for Export Position Data to Other

Applications