Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Purpose
SAP Utilities is a process-oriented sales and information system that supports all
services provided by utility and waste disposal companies. You can use SAP
Utilities to manage and bill residential, commercial and industrial, and
prospective customers.
In times of deregulated markets and increasing competition, it is vital that you
provide the bet possible response to your customers requirements, use
operational information tailored to their specific requirements, and maximize
revenue potential. As an integrated component in SAP ERP, SAP
Utilities provides you with all the benefits of a comprehensive and effective
Enterprise Resource Planning (ERP) System.
SAP Utilities helps you to keep you business processes as streamlined and as
efficient as possible. As a single software solution, SAP Utilities eliminates
incompatible and isolated information in the back office. With SAP Utilities, you
can access data at any time from diverse business areas, providing you with the
information you need to make the right decisions.
Integration
Solution Portfolio SAP for Utilities
SAP Utilities is part of the solution portfolio SAP for Utilities and includes the SAP
Utilities (IS-U) industry-specific component.
SAP for Utilities can be integrated with the following applications:
Application
Documentation
You can use the Plant Maintenance (PM), Customer Service (CS) and Sales
and Distribution (SD) SAP ECC application components to bill service orders,
service contracts, services, and the sale of goods. Due to the large number of
postings from billing and budget billing requests, these are posted in a subledger
in Contract Accounts Receivable and Payable (FI-CA).
SAP Utilities uses SAP Business Workflow to automate the processing of its
many business processes. Common workflows include initial creation of a
service connection and the disconnection of devices.
Features
SAP Utilities
You can use Master Data to manage data that remains fixed for long
periods of time. In IS-U, this data includes the business partners, contracts
and contract accounts, connection objects (buildings and real estate) and
the premises, installations, and device locations contained therein.
You can use Invoicing to group services and invoice them on one bill.
You can also use Invoicing to calculate and charge duty, fees, and taxes.
Unbundling
here are 2 different types of master data: technical and business. These are
shown in the graphic below:
Contract Accounts
Purpose
This component enables you to create and manage contract account master
data. In Contract Accounts Receivable and Payable, each business partner
posting is assigned to one business partner and to one contract account. In the
contract account master record, you can define, for each business partner, the
procedures that apply when posting and processing the line items of a given
contract account. These include, for example, payment and dunning.
Integration
Master data can be changed automatically by certain business transactions. In
this way, for example, a return can result in a processing lock being set.
Features
You can assign more than one contract account to a given business partner.
Similarly, a single contract account can be assigned to more than one business
partner. Note however, that in the industry components listed below, different
rules apply. You can transfer data manually or automatically. Contract accounts
tend to be managed on an open item basis. See Open Item Management. The
system logs changes to master data. See Logging Changes.
Telecommunications (IS-T) component
In this component, a contract account can be assigned to one business partner
only.
Utilities Industry (IS-U) Component
In Utilities,one contract account contains all those contracts belonging to one
business partner for which the same payment and dunning terms apply. You
assign your business partner contracts to the contract accounts. Although one
contract account can contain more than one contract, each individual contract is
assigned to one contract account only. This does not apply to one-time
accounts.
For more information on contracts, see the Utility/Disposal Contracts section in
the Utilities Industry component.
Insurance (FS-CD) Industry Component
You assign contracts to the contract accounts for which there is a business
partner. Each contract is only assigned to one contract account, however one
contract account may have several contracts assigned to it.
Contract account master data is usually created and changed from the
operational system using an interface.
Industry Component Public Sector Contract Accounts Receivable and
Payable (PSCD)
You set up the contract accounts of a business partner for the relevant taxes
(property tax, income tax, and so on). You assign contract objects to a contract
account for which relevant taxes are levied. If different taxes are levied for a
contract object, you can make assignments to several contract accounts.
For more information about the contract objects, see the documentation for the
industry-specific component Public Sector Contract Accounts Receivable and
Payable under Contract Object.
Utility Contract
Definition
Utility contracts are utility service agreements between the utility company and its
business partners. The following contract categories exist:
With the exception of move-in and move-out data, you can change, display and
check all data of multiple contracts of a contract account simultaneously, if none
of these contracts have been terminated.
You can change the screen layout by configuring the tabstrips. For more
information, see the move-in screen layout.
Basic Functions
Business Transactions
Integration
Closing Operations
Information System
Job Controls
European Monetary Union and Contract Accounts Receivable and
Payable
Archiving
Interfaces
The EVENT Concept
Data Processing in Mass Runs
Enhanced Message Management
Organizational Units
Definition
Elements of the logical structure of the SAP System that you can use to portray
your company-specific organizational structure in the SAP System. You use
organizational units to structure business functions.
Use
The organizational units of Financial Accounting, such as the company code,
chart of accounts, and fiscal year are used for external reporting purposes, for
example, for financial statements legally required of your company. For detailed
information about the organizational units in Accounting, see the documentation
for Accounting under Financial Accounting Financial Accounting - General
Topics Organizational Units and Basic Settings.
basic Functions
Purpose
You use this component to enter your basic settings for master data and to post and
process documents. It is also used to create and process master data, and to post and
process documents manually.
Implementation Considerations
You must implement all the components listed below.
Features
This component consists of the following detailed components:
Remark
Business Partner
Category
Business Partner
Relationship
Business Partner
Group Hierarchy
Integration
For more information on the functions for a business partner, see
Business Partner Data.
Processing
616098
432178
624341
503243
Integration
Part of the central business partner concept is that every natural or legal person
as well as every group is only created once in a system. There are different
reasons why a business partner is created several times in one system. Business
partners that have been created more than once are referred to as duplicates.
Duplicate can occur due to the following reasons:
Customer Change
Contract Accounts
Purpose
This component enables you to create and manage contract account master
data. In Contract Accounts Receivable and Payable, each business partner
posting is assigned to one business partner and to one contract account. In the
contract account master record, you can define, for each business partner, the
procedures that apply when posting and processing the line items of a given
contract account. These include, for example, payment and dunning.
Integration
Master data can be changed automatically by certain business transactions. In
this way, for example, a return can result in a processing lock being set.
Features
You can assign more than one contract account to a given business partner.
Similarly, a single contract account can be assigned to more than one business
partner. Note however, that in the industry components listed below, different
rules apply. You can transfer data manually or automatically. Contract accounts
tend to be managed on an open item basis. See Open Item Management. The
system logs changes to master data. See Logging Changes.
Telecommunications (IS-T) component
In this component, a contract account can be assigned to one business partner
only.
Utilities Industry (IS-U) Component
In Utilities,one contract account contains all those contracts belonging to one
business partner for which the same payment and dunning terms apply. You
assign your business partner contracts to the contract accounts. Although one
contract account can contain more than one contract, each individual contract is
assigned to one contract account only. This does not apply to one-time
accounts.
For more information on contracts, see the Utility/Disposal Contracts section in
the Utilities Industry component.
Insurance (FS-CD) Industry Component
You assign contracts to the contract accounts for which there is a business
partner. Each contract is only assigned to one contract account, however one
contract account may have several contracts assigned to it.
Contract account master data is usually created and changed from the
operational system using an interface.
Industry Component Public Sector Contract Accounts Receivable and
Payable (PSCD)
You set up the contract accounts of a business partner for the relevant taxes
(property tax, income tax, and so on). You assign contract objects to a contract
account for which relevant taxes are levied. If different taxes are levied for a
contract object, you can make assignments to several contract accounts.
For more information about the contract objects, see the documentation for the
industry-specific component Public Sector Contract Accounts Receivable and
Payable under Contract Object.
Whether you are allowed to assign only one business partner or more
than one to a contract account
Whether you are allowed to assign only one contract or more than one
The editing screens or data fields that you can use to edit the contract
account
Contract Account
Definition
Structure used to bill the posting data for contracts or contract items for which the
same collection/disbursement agreements apply.
Contract accounts are managed on an open item basis within Contract Accounts
Receivable and Payable.
In the industry component Insurance, you can decide whether
accounting is to be managed on an account or open item basis.
Use
Alternative correspondence recipient
You can define an alternative correspondence recipient in the contract account
(see Recipient and Sender Determination).
Planned changes to the contract account
You do not have to activate contract account changes to have immediate effect,
but rather you can enter a date as from which the changes should become
effective. This data is not written to the database but recorded in change
documents. The planned changes function only applies to changes to the
contract account. You cannot schedule the creation of a contract account.
To activate this data, you should run program BUSPCDACTon a daily basis. This
writes the scheduling to the database. You can use the application object FICAto
activate planned changes to the contract account.
When you are in display mode for change documents, you can delete
inconsistent data, for example, data that arises when planned changes are
cancelled.
Check digits in the contract account
When you create a contract account, you can add a check digit to the contract
account number. The prerequisites are as follows:
You add the check digit procedure using event 1051. (Sample function
module FKK_SAMPLE_1051_2_CHECKDIGITS for two check digits is
supplied by SAP)
Only procedures with one or two check digits are supported. The
number range is configured such that it begins with a leading zero (check
digit procedure with one check digit) or with two leading zeros (procedure
with two check digits).
Contract account enhancements
You can make enhancements using the Business Data Toolset (BDT) in the
menu for transaction CAWM.
Structure
Every contract account master record consists of general data that is the same
for all business partners assigned to the contract account and business partnerspecific data that can be set differently for each business partner in the contract
account.
In the industry component Insurance, you can also define this
data for the insurance relationship.
The master data is structured according to the processes that depend on the
contract account data, such as incoming and outgoing payments,
correspondence, dunning.
Integration
All transactions relating to contract accounts access data from the contract
account master record (such as payments and dunning). Several transactions
change data in the contract account master record (such as payment locks for
returns).
General data
Cross-partner data
Account management
data
Invoice creation
Payments/taxes
Incoming and
outgoing payments
Taxes
Dunning/
correspondence
Dunning control
In addition, you also have the option of using additional industry-specific fields.
Account determination ID
Application form
Language
Dunning Control:
Logging Changes
Use
The system logs changes to fields in the contract account. You can display the
changes when you maintain the account online. In addition, the system records
who created a contract account and when, and who made the last change and
when.
Features
Select (in the menu of the You see:
transaction):
Extras Creation Data
Extras Account
Changes
The system does not create change documents for process locks. There is,
however, a history function that you can call up from the dialog box for locks.
6.
...
1.
In the menu, choose Display Business Partner or Change Business
Partner.
2.
Enter a business partner, specify the screen selection, and
choose Continue.
3.
In the menu on the detail screen, choose Extras Partner
Changes and select the required fields in the selection dialog box. If you
choose Technical Field Names On/Off, the system displays the table and
field names.
4.
Choose Continue.
A list of the change documents previously created appears.
The same procedure applies for the transactions Display Contract Account and Change
Contract Account. In the menu of the detail screen, chooseExtras Account Changes.
Features
You have to trigger the creation of the correspondence manually. The program selects all
change documents created for the business partner on the same day and then creates an
individual correspondence. Only the change documents for the fields defined in
Customizing are considered in the correspondence. This means that the user can decide
which master data changes he wants to follow and inform the customer about.
Only actual changes to existing data and changes made on the current date are
considered. This means that new master data, such as business partners and addresses, are
not taken into account in the correspondence.
You cannot list or individually select the selected changes for the correspondence before
the correspondence is created.
For correspondence type 0030 you can use events 1914 (print event) and 1915 (creation
event). Read the documentation for function modules FKK_SAMPLE_1914 and
FKK_SAMPLE_1915. You can determine industry-specific additional data for the
contract reference with a module for event 1916 (FKK_SAMPLE_1916). The module
FMCA_SAMPLE_1916 is defined for determining data for the contract object for the
industry solutionContract Accounts Receivable and Payable for Public Sector.
FI_CA_MASTERDATA is defined as the standard form class in Customizing. At the top
level (document level), the form class contains a 1:1 level to the business partner. The
hierarchy below contains the level for the change documents, whereby the process logic
determines that first the change documents and then the planned change documents are
listed (see application form example FI_CA_MASTERDATA_SAMPLE). In the
application form, you can display the old and the new value for a changed field. Note that
certain fields only contain IDs (table keys), that is, links to the actual data (for example,
bank details ID for incoming payments). The determination of details for these IDs and
other ID fields is not supported in the standard. However, you can implement this in the
customer-specific application form.
Activities
3.
...
7.
1.
In the menu of the transactions Change Business Partner, Display
Business Partner, Change Contract Account, and Display Contract Account,
chooseExtras Additional Extras Correspondence.
8.
2.
On the processing screen that appears, make selections for the
business partner, contract account, and contract reference and make
specifications for printing.
You must specify a business partner. If you do not make any restrictions for
the contract account and/or contract reference, changes to all contract
accounts and contracts (contract references) of this business partner are
considered, instead of only changes to the selected objects.
9.
3.
Confirm your entries.
The correspondence is created.
Example
Example 1
A customer informs you that she has recently married and informs you of her new last
name. She requests written confirmation that her data has been changed.
Once the clerk has entered the new name in the field Last Name (BUT000NAME_LAST) in the transaction Change Business Partner, he creates a correspondence
that documents the change made and sends it to the customer.
Example 2
A tenant informs you that the bank details for the collection authorization that you have
will change in two months. The clerk enters the new bank details in the field Bank
Details ID for incoming payments (field FKKVKP-EBVTY) in the transaction Contract
Account and schedules the change for the date specified. Using the correspondence for
master data changes he informs the tenant about the change planned in the system.
determines the tax code according to the account to which the document is
posted.
You can settle documents on behalf of third parties through the use of crosscompany code billing documents. For more information, see the Invoicing section
of the Telecommunications component.
Industry-Specific Component Insurance (FS-CD)
In this component, all accounts receivable and payable, and all revenue and
expense accounts are determined automatically by the system using the criteria
entered in the line item. You have to enter revenue and expense accounts if they
are not to be determined automatically. In addition to G/L accounts, the dunning
procedure and item category are also determined automatically.
Tax calculation takes place in the operational system and is transferred
to Contract Accounts Receivable and Payable when making the debit entry. You
have to enter the tax manually when you are posting manually.
Industry Component Public Sector Contract Accounts Receivable and
Payable (PSCD)
The system determines all accounts receivable, and accounts payable, and all
revenue and expense accounts automatically in accordance with the account
assignments entered in the line item, such as main and subtransactions.
Documents
Definition
Representation of business transactions in Contract Accounts Receivable and
Payable which is changed as a result of the account balance in contract accounts
and/or G/L accounts.
Use
Documents serve as proof of the account balances in Contract Accounts
Receivable and Payable and indirectly also as proof of summary data in General
Ledger Accounting, Controlling, and Cash Management.
The open items contained in documents form the basis for subsequent
processing, such as payments, dunning notices and interest calculations.
Structure
Documents consist of header data, items for contract accounts and items for G/L
accounts.
In addition to the unique document number, the header data also contains the
document type as the classifying attribute, the currency key and various date
specifications.
All items contain the posting amount and the necessary information for General
Ledger Accounting, Cash Management and Controlling.
The items in contract accounts also contain specifications regarding the due
date, cash discount, dunning, automatic payments/debit memos, interest
calculation and additional industry-specific processes. Items in contract accounts
Document type
Document types classify the documents in Contract Accounts Receivable and
Payable and determine:
account level. Do not specify any account numbers for the contract accounts
entry, or for the entry * (all account types).
In order to be able to post in contract accounts receivable and payable after
a release change from Release 4.51 (or earlier) to Release 4.61, enter account
typeV for all variants in the posting periods.
Company code
Business partner
Contract account
Contract
G/L account
Division
Compressed list of G/L account items per company code and G/L
account.
Compressed display of the items cleared with this document (for clearing
documents).
Tax screens
Tax screens are display screens for the tax items to be created or that have
already been created. The tax screens used depend on whether you have
selected the field for the jurisdiction code (USA or Canada) in the document
header.
Screen for processing open items
If you want to clear open items straight away with the line items you enter, you
can process the open items on a separate screen for clearing. For more
information, see Processing Open Items.
Prerequisites
In Customizing, you define the fields that you do not require and screen variants
for the list screens (see the IMG structure for Contract Accounts Receivable and
Payable Basic Functions Postings and Documents Document Screen
Preparations).
Activities
You can navigate between the processing screens. The following functions are
available:
You want to:
Taxes
Header
Overview
Automatic Postings
Use
Certain G/L items are created automatically. This reduces the manual entries required.
Features
During clearing, items for cash discount, payment differences, revenues from charges,
exchange rates differences, and any necessary tax adjustments are amended automatically
(see Automatic Postings During Clearing).
With all business transactions containing cross-company code documents, offsetting
entries representing receivables and payables between the company codes involved are
amended automatically.
When posting down payments, you may have to post the tax from a general ledger
viewpoint. No special line items for tax and tax clearing are generated for this in Contract
Accounts Receivable and Payable. Only the tax code, tax amount, and account numbers
for the tax account and tax clearing account are noted in the open item for the down
payment. This information is sufficient for updating the general ledger.
Prerequisites
The accounts to be posted to must be defined in Customizing for the line items to be
created automatically (see the IMG structure for Contract Accounts Receivable and
Payable Basic Functions Postings and Documents Document Define Account
Assignments for Automatic Postings).
Entering Taxes
Prerequisites
The system determines the tax accounts automatically. Define the corresponding account
numbers in Customizing (see the IMG structure for Contract Accounts Receivable and
Payable Basic Functions Postings and Documents Document Define Account
Assignments for AutomaticPostings).
Features
If taxes are to be taken into consideration during document entry, you have the following
options:
Manual entry
Automatic calculation of taxes from the business partner items
Automatic calculation of taxes from the G/L account items.
You can set the preferred entry type in the options. You can change this setting on the
initial screen and during document entry.
You can post documents with or without tax jurisdiction code. You define this on the
initial screen by selecting the Jurisdiction code indicator.
The tax base amounts for line items that are the same with regard to their tax code,
company code, tax jurisdiction and tax date are added for tax calculation purposes. The
tax is first calculated on the totals.
When you display the document, the tax items appear on the overview screen in the G/L
account item area. They form part of the document balance.
Here you distinguish between line items that result in tax and tax items:
Tax items
You cannot actually enter tax items: You can, however, display them with
the Taxes function.
If you delete a line item that results in tax, all tax items generated from this item are
deleted.
Entering Documents
Purpose
You enter documents using the Post Document function. The way you proceed depends
on the document type.
Posting without clearing open items
For example, if you post a payment on account or carry out a transfer posting or debit
entry, you post the document without clearing any items. In this case you carry out the
following steps:
10.
11.
12.
1.
Enter the document header.
2.
Enter the business partner items.
3.
The G/L account items are normally created automatically by the
applications (see Automatic Postings). You can also enter them manually if
necessary.
13.
4.
Post the document
Posting and clearing open items
You usually clear items with one of several specialized functions, which include payment
lot, payment program, account maintenance, or write-offs. You can also clear open items
during document entry. In this case you carry out the following steps:
4.
14.
15.
...
1.
Enter the document header.
2.
Enter the G/L account items where necessary (example: Incoming
payment in a bank clearing account).
16.
3.
Enter business partner items where necessary (payments on
account or transfer postings).
17.
4.
Select and process the open items.
18.
5.
Post the document.
Prerequisites
You have made the settings in the Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions Postings and Documents.
If you frequently enter single postings of a specific category online, for example, in the
cash desk or in the cash journal, and usually always use the same document type, the
response times may be slow because all users use the same number range for document
number assignment. To avoid slow response times, you can assign several number ranges
to a document type for single postings (see Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions Postings and
Documents Document Maintain Document Account Assignments Document
Types Maintain Document Types and Assign Number Ranges (Additional Number
Ranges for Individual Processing)).
Result
Posting without clearing open items
The system posts a document.
Posting and clearing open items
The clearing document created may contain business partner and G/L items as well as a
list of the cleared items in the lower portion of the overview screen.
Roles
Manual Postings (SAP_FI_CA_MANUAL_POSTINGS) Post
Document
SAP Menu
Document Post
Document Changes
Use
You can change the field contents for a document.
Features
The changes are logged. You can display the document changes from the
transactions for displaying and changing documents by using
the Environment Document Changes function.
You can lock field groups against document changes by means of the
authorization object F_KKKO_AEN. The modifiable fields are grouped into field
groups in the business partner items for a document, and you assign only certain
users change authorization for these field groups. This means that you can
ensure that certain fields can only be changed by selected users.
A field that is contained in at least one field group for which there is no change
authorization cannot be changed by means of the change document transaction.
If you have defined some modifiable additional fields in the business partner
item, the list of these non-modifiable fields is provided in the function module
FKK_DOCT_AKTYP_GET.
Activities
You define the field groups in the Implementation Guide for Contract Accounts
Receivable and Payable: Basic Functions Postings and Documents Basic
Settings Define Authorizations for Field Changes.
Roles
Manual Postings (SAP_FI_CA_MANUAL_POSTINGS) Display/Change
Document
SAP Menu
Document Display/Change
On the initial screen, you can specify either the document number or the reference
document number. If you set the Compressed indicator, you can hide empty or empty,
non-modifiable fields.
You can also use the following functions on the initial screen:
Function
Goto Document Header
Goto First Item
Display
Document header data
First document item
Goto Overview
Goto Business Partner Item List
Goto G/L Item List
Settings Taxes
Read from Archive (Pushbutton)
If you have selected the document for the Document Display or Document Change, you
have the option of using additional views as well as the list of individual items:
Function
Display
Goto Payments/Returns
Extras Corrections
By double-clicking on the business partner item, you can go to the detail display. You
can now use the following functions to display clearing documents:
Function
Environment Cleared Items
Environment Previously Cleared Items
Environment Payment Usage
Environment Bank Data from Returns
Document/Payment Lot/Payment Run
Environment Clearing Analysis
Display
Displays the items cleared with this
clearing document within the account
balance display
For a clearing document for which clearing
postings have been reset, this displays the
items that were cleared with this document.
Displays the items cleared with this
clearing document in a dialog box.
Displays the bank data from the sources
mentioned
For the clearing document, displays the
items that were cleared.
For items that are still open, this function
displays the status of the item (open,
cleared, partially cleared).
Displays clearing postings and
resetting of clearing postings in a
chronological view
Displays the clearing document for the
open business partner item
You can use the following functions for dunning/installment plan/collective bills:
Function
Environment Source Receivables
Display
For an installment plan document, this
function displays all the items that went
into this installment plan and were replaced
by it.
When you display a business transaction that consists of several documents, you can
use the following functions:
Function
Document Business
Transaction Individual Document
Display
Document Business
Transaction Total Display
Display
Displays the individual document of a
business transaction
Allows you to switch from the individual
document to the overall business
transaction
You can use the following functions in connection with the changeover to the Euro:
Function
Goto Document Prior to Conversion
Euro Simulation On (Pushbutton)
Display
Displays the document data before the Euro
conversion
Displays the amounts in Euro
In the detail display for the business partner and G/L item, the data is organized on tab
pages. By pressing the First Offsetting Posting button in the navigation area for the detail
screens, you can switch between the detail screen for the business partner item and the
detail screen for the general ledger item.
Navigation in Documents
Use
When you are displaying or changing documents, in addition to switching
between the different document views and displaying additional information for
the document as described in the section Functions Available When Displaying
and Changing Documents, you also have the following options: You can navigate
between the items, the repetition items, the partial payment items, and the
business partner items of a document.
Features
On the detail screen for displaying business partner items, in
the Navigation area, you can use an item counter, repetition counter, or a
subitem counter.
You can use the buttons next to the item counters to navigate between the
individual items. The data appears in the Business Partner Items area .
Integration
By double-clicking on the output fields, you can display the detailed information
about the objects displayed in the business partner item (for example, business
partner, contract, installment plan).
...
Choose one of the following paths:
Role
Manual Postings(SAP_FI_CA_MANUAL_POSTINGS) Mass
Changes to Documents
SAP menu
Document Mass Change
20.
2.
You select the line items to be changed in the same way as you
select open items, by entering the business partner, contract account,
contract, or document number.
21.
3.
Choose Continue.
The selected open business partner items appear in a list. You an change
the following data:
Payment data
Dunning data
Locks
Select individual items and enter the required changes individually or select
all items to be changed and enter the changes that apply to all items in the
upper part of the screen.
By choosing the pushbutton
(Select Additional Items), you can add
additional items to the selection. The additional items are added at the
bottom of the list; already selected items remain selected.
If you choose the
For Deletion pushbutton, on the upper part of the
screen, you can select the fields you want to delete in all selected items.
You can also delete all locks with a specific lock reason, or all locks
regardless of the lock reason, add new locks, and change existing locks.
You can display simultaneous locks by including the fields SPZAH_LST,
MANSP_LST, SPERZ_LST, and CLRLO_LST in Customizing for the line
layout variant with the texts Payment Locks, Dunning Locks, Interest Locks,
Clearing Locks. Double click on these fields or the lock fields to display all
locks. You can then make changes to locks in the dialog box that appears.
22.
4.
Using the
Transfer New Values pushbutton, you can transfer the
changes to all items selected.
23.
5.
Choose Save to save the changes on the database. Change
documents are updated in the same way as for changes to individual
documents.
As well as making changes to individual fields, you can split document items
when carrying out mass changes. You can change the subitems that arise in the
same way as the original item. This means that as in the original item, you can
enter different alternative payees, payment methods, or locks. To split a line item,
choose the Copy pushbutton in the list . The original item is copied and the
amounts are ready for input. You can either enter the amounts manually or you
can change the original item automatically by double clicking on the amount field
such that the total of the subitems corresponds once again to the original
amount. You can also enter percentages according to which the amounts are
distributed. If you choose the Delete pushbutton in the list, the subitems created
as a result of the split are deleted. You can also define a distribution rule for
several selected items. To do this, select the relevant items and choose
the Distributepushbutton.
Example
Document
Number
Amount
Business
Partner
Payment
Lock
4711
100
1002
4733
200
1002
Alternative Payee
If you select both documents, there is a total amount to be split of EUR 300. This
should be split as follows:
20%, alternative payee G1, no payment lock
30%, alternative payee G2, no payment lock
50%, payment lock A
This results in:
Document
Number
Subitem
Amount
Business
Partner
Alternative Payee
4711
20
1002
G1
4711
30
1002
G2
4711
50
1002
4733
40
1002
G1
4733
60
1002
G2
4733
100
1002
Payment
Lock
This means that EUR 20 + EUR 40 = EUR 60 can be paid to alternative payee
G1, and EUR 30 + EUR 60 = EUR 90 to G2.
You can only use one distribution rule for each mass change.
You can enter a tax company code that applies to all line items in the
document header. This company code is used for posting tax. This tax
company code is the company code that issues the business partner a bill
(which displays the tax) or that contains a business partners bill (on which
tax is displayed).
If no tax company code can be used, the company code of the line item
entered for the tax posting is used. In this case tax postings can therefore
occur in different company codes.
Points to note when making payments
You can enter cross-company code payments as well as cross-company code
bills. If items from different company codes are selected and cleared when
making a payment, then any offsetting items needed are automatically added so
as to create a zero balance in the document for each company code.
The system also supports cross-company code incoming payments (debit
memos) and outgoing payments for automatic payment transactions. Since the
documents and therefore also the posting to the bank clearing account are
generated automatically, you must previously have used Customizing to define
the company code in which the bank offsetting item is to be generated. This
company code is known as the paying company code. It processes payment
transactions for other company codes. To be able to do this, you use
Customizing to assign a paying company code to each company code group.
At business partner level, each contract account is assigned to a company code
group and thus to a paying company code. Payment transaction specifications in
the account master record always refer to this paying company code. You can
only post to the contract account in company codes that you have assigned to
the specified responsible company code group.
Reversing Documents
Use
You may sometimes have to reverse a document posting or the clearing of open
items, as well as all the postings that were created automatically. Depending on
the situation, you choose one of the following functions:
Return
Reset Clearing
Reverse documents
Prerequisites
You can reverse a document if it contains items that were cleared by another
document. Otherwise you first have to reset the clearing. Reversal documents
themselves can be reversed, but you receive a corresponding warning. A
In the reversal document, for every general ledger item, the system
creates a corresponding item with the opposite +/- sign.
Reversing payment documents
Reversing a payment document has the following effect:
Depending on the reversal method selected, the system either resets the
clearing data of the original items paid, or creates offsetting items for the
clearing items within the reversal document.
The system logs the transaction in the clearing history, provided clearing
is to be reset.
Before reversing a document, you can use the Cleared Items function to check
whether you have entered the correct document number.
If you reverse a payment document that was posted directly without clarification,
in a dialog box when posting the reversal, you can decide whether you want to
reverse the payment document or transfer to the clarification account. If the
clarification case is created for a payment lot that has already been closed, the
status changes again to Postprocessing Necessary.
Reversing a clarification or partial clarification document
When you reverse a clarification or partial clarification document for an incoming
payment, either a new clarification case for incoming payments is created
automatically or the amount to be clarified in an existing case is adjusted.
Special features for documents with cleared items
If you manually reverse a document that contains cleared items, an overview
screen with all clearings appears. You cannot execute the reversal unless you
reset these clearings. The overview screen displays the date and origin of the
clearing documents and whether additional documents were cleared by this
clearing. You can display the clearing documents or initiate the clearing reset via
function keys. You can carry out the clearing individually online or carry out all
clearing in the background. If you carry out clearing online, you can also partially
reset clearing and thereby retain the distribution of the clearing amounts to the
accounts.
Special features for documents with repetition specifications
If a document contains repetition items, you can reverse a specific repetition
specification by specifying the posting date of the repetition specification to be
reversed in the Repetition Date field. Alternatively, you can reverse all repetitions
that are still open.
Special features when reversing more than one document
You can reverse all documents with the same reference document number or
classification key (if this enhancement is active) together as a group. Using a
simulation function, you can check whether the documents that were selected
using the reference number or classification key can be reversed. A list with the
selected documents is displayed. In this list, error messages point to any
individual documents that cannot be reversed.
Special features for reversing archived documents
Archived documents usually have business partner items that are cleared (for
example, paid invoices), or have cleared business partner items themselves (for
example, payments). An exception is documents that contain exclusively general
ledger items. Since no data may be changed for an archived document, it is not
possible to reset clearing as part of a reversal. Therefore, for archived
documents, you have to select another form of reversal. When you reverse
archived documents, the system therefore creates new business partner items in
the reversal document.
Reversal of archived invoice
In the reversal document, the system creates a business partner item
with a reversed +/- sign for each business partner item of the invoice
document. In this case, the reversal document is a credit memo
posting for the full invoice amount.
Reversal of archived payment
In the reversal document, for the paid receivable items, the system
creates business partners in the same amount. This is identical to the
procedure for returns if new receivables are created derived from
the payment.
If a document that still contains open business partner items is reversed such
that the system creates offsetting postings, account maintenance takes place
automatically after the reversal; the open items of the document to be reversed
are cleared against the open items of the reversal document.
When you reverse an archived document, you cannot
trigger a workflow to confirm the reversal. In this case, event
5502 that is used to trigger a workflow is not processed.
For further restrictions, see the documentation to the Reversal
Method field on the initial screen of the reversal transaction.
Activities
6.
24.
1.
...
Choose one of the following paths:
Role
Manual Postings (SAP_FI_CA_MANUAL_POSTINGS) Reverse
Document
SAP menu
Document Reverse
25.
2.
To select the document to be reversed, enter its document number.
If you want to reverse documents with the same reference number, enter
the reference number instead.
In the case of a document with repetition specifications, you must also enter
the desired date of the repetition, or indicate that all open repetitions should
be reversed.
To reverse documents that have already been reversed, set the
indicator Check Archive.
26.
3.
If you reverse a document that has been archived, enter one of the
following reversal methods:
Document Archiving
Use
When you archive documents, data is deleted from the database and archived in
the file system. You can then store the data from the file system in external
archives. This way you can take some of the load off the database at regular
intervals. The archiving is carried out in two steps: First, data is written to an
archive file in the file system. Based on the archive, data is then deleted from the
database. Once you have archived data to the archive file in the file system, you
can still access it. If you need the data in the database again (for example,
because you have to make changes to it or because you archived it by mistake),
you can also reload the archives.
Prerequisite
To be able to archive a document, all business partner items must have been
cleared and a predefined retention period in the system must have expired. In
Customizing you define the retention period per document type (see the IMG
structure for Contract Accounts Receivable and
Payable Basic Functions Postings and Documents Archiving Define Li
fe of Document Types or choose Goto Customizing in transaction SARA). The
archive information structure must also be activated for documents. You can find
a detailed list of all the checks that are carried out before archiving in the
documentation on the archiving program. To execute an archiving function in the
background, you need a variant in which you define the parameters for the
program run.
Features
When you archive documents in Contract Accounts Receivable and Payable, you
can only archive documents and their related clearing documents in a predefined
order. You can only display the complete clearing document in the system if the
items cleared by it still exist in the database. A reverse dependency does not
apply. Therefore all the clearing documents that have exceeded their retention
period are first archived in an archiving run. You can then archive the documents
with their related cleared items in a second archiving run. You use the SAP
standard tool for archiving, the Archive Development Kit, to archive documents
from Contract Accounts Receivable and Payable. The archiving object for
document archiving is FI_MKKDOC. The associated programs are:
RFKKAR10 FI-CA: Document archiving, archiving documents
RFKKAR11 FI-CA: Document archiving, delete documents
RFKKAR12 FI-CA: Document archiving, reload documents
The starting point for all activities within archiving is transaction SARA for the
archive administration.
Activities
You should first be familiar with the basics of archiving (see Introduction to
archiving). To archive, choose one of the following paths:
Roles
Archiving (SAP_FI_CA_ARCHIVING) Document Archiving
SAP Menu
Periodic Processing Archive Data Documents.
The programs for archiving Contract Accounts Receivable and
Payable documents appear under Actions. For more information about the
individual programs, see the program documentation.
Roles
Transfer Posting
Data (SAP_FI_CA_POSTING_DATA_TRANSFR) Transfer
Documents
SAP Menu
Periodic Processing Transfer Data Documents Transfer
During the document transfer, you can process errors under one of the following
paths:
Roles
Transfer Posting
Data (SAP_FI_CA_POSTING_DATA_TRANSFR) Transfer
Documents - Process Errors
SAP Menu
Periodic Processing Transfer Data Documents Process
Errors
You can delete the incorrect data here by choosing Cluster Delete.
You can ensure that the transfer file structure is releaseindependent by using Z structures. You can generate and
check Z structures in Customizing. (See Implementation
Guide for Contract Accounts Receivable and Payable, Data
Transfer Generate Structures for Document Transfer).
You have entered check reasons in the Implementation Guide for Contract
Accounts Receivable and Payable (Basic Functions Postings and
Documents Workflows for Checks and Approvals Define Check
Reasons). You can specify whether a check is necessary dependent on
any number of criteria. For example, you can make the reversal of
receivables that exceed a predefined amount limit, or the posting of credit
memos from a predefined amount, subject to a check. In addition, you can
also make random checks. For each check reason, you can define whether
payments, other clearing transactions, dunning, calculation of arrears
interest, or document changes are to be permitted up until the time the
workflow is completed.
Features
Checks and approvals are supported for the following transactions:
Posting documents
Reversing documents
Changing documents
Write-offs
Payments
Clearing
Dunning
Document Changes
5500 or 5502, then for posting, the event ApprovalRequired is triggered, and for
reversals, the event ReverseApprovalRequired from object category CA_DOC.
SAP provides the workflow samples WS21000088 for postings,
and WS21000089for reversals. Role 21000056 is used for the role resolution. If
you are posting or reversing in the online transactions Post
Document or Reverse Document, the system prompts you to enter a reason for
the required posting or reversal. If a reversal has to be confirmed, the reversal
document is not created. The check reason is entered in the document to be
reversed. Depending on the check reason, this document is also locked for the
editing processes stated above.
Changing documents
The function module defined for event 5504 runs for document changes. Using
the document data, it checks whether the change has to be confirmed and
released by other clerks in a workflow. If a check is required, the module returns
a check reason that is stored in the document to be changed.
EventChangeApprovalRequired from object category CA_DOC is triggered. In
the document display, clerks that are assigned to the corresponding role in the
workflow can:
Display the original document and the planned changes using the
function Planned Changes
Accept or reject the document change via function keys
System Reaction/Activity to be
Executed
Approve posting
Reject posting
Approve reversal
Reject reversal
You can display the check reasons in the document display once
the document has been posted. You can determine whether the
workflow was started in the SAP Business
Workplace under Outbox Workflows Started.
In the transaction Reset Check Reason in Document
(menu:Administration), you can remove the check reasons from the
documents by specifying the document number. To do this however,
you require the special authorization for activity 060 for the
authorization object F_KK_SOND.
In the transaction Reset Check Reason in Repayment Request
(menu:Administration), you can remove the check reasons from the
repayment requests by specifying the number of the repayment
request.
Prepared Enhancements
Use
In FI-CA documents and requests, you can use the attribute Classification Key to
identify documents. The classification key provides a similar function to the
reference number, but allows keys with a length of up to 35 characters.
In the business partner item, you can use the Broker field. The broker represents
a business partner that takes over the processing of certain processes, such as
payment or dunning for the end customer.
Classification Key and Broker are enhancements supported in the sytem. This
means that in the system delivered, these attributes are not initially active. You
have to activate them explicitly in your installation.
Features
Classification key
You can enter the classification key in the document header and it is available as
an input field for the document display, document change, document reversal,
and mass reversal.
The classification key is inherited in the business partner items and can be
displayed in the account balance or in the processing of open items.
It can be used as selection criterion in the account balance, in the selection of
open items (for example, in the payment lot or in online posting), for write-offs, in
payment advice notes for incoming payments, or for the creation of an
installment plan.
Broker
The field is:
You can use a function module called up for this event to:
0010
0020
0030
0090
Reset the data noted for events 0010, 0020, and 0030 to ensure
consistent data for a ROLLBACK WORK.
See the documentation for the sample function module
FKK_SAMPLE_0090.
Tax Postings
Features
The following sections contain information:
AAAA
Chart of Accounts
According to German
Law
Transaction/account key
MWS
Output tax
Tax Code
G/L account
V1
175100
V2
175200
Profit center
Segment
Business area
Commitment item
Funds center
Fund
Functional area
Funded program
Grant
The system can also distribute the tax items to different account assignments.
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 as follows:
Account
Profit center
Tax code
Amount
Revenue
P001
A1
400
Revenue
P002
A1
200
A1
114
Tax
Base amount
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 one of the tax items.
NOTE
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 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 value added tax
account 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 clearing 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
Account Assignment (Account Assignment
Distribution) pushbutton.
Activities
To have the system automatically split the tax amounts and tax base amounts to
different account assignments, make the following system settings:
Check the field status groups. 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 above to optional (at least those account
assignments that are used in your installation). 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 in question and then navigate to the
maintenance of the field status groups.
Withholding Tax
Withholding tax can arise in the following two forms:
Interest
Items that would otherwise be taxed but that are excluded from tax for a
specific customer group (tax exception)
You cannot reverse Bollo. This also means that the reversal of a Bollo-relevant
posting does not reverse the Bollo posting. Programs in FI-CA post Bollo only if
you registered function module FKK_CHECK_CALC_BOLLO_INTERN for event
0100.
Central Settings for Posting . Set the Parallel Tax Update for U.S.A. indicator.
Also see the documentation (F1 help) for this field, which contains additional
technical information.
Features
In Contract Accounts Receivable and Payable, you can use a mass activity to
update external tax systems using parallel processing. Parallel processing
assists in speeding up the update.
Activities
1. On the SAP Easy Access screen, choose Periodic Processing
Transfer Tax Data Update External Tax Systems .
2. Enter a date and an ID that you can use to identify the run later.
3. Choose Continue.
4. If you want to limit the update, you can enter a document number range
on the General Selections tab page. Or you can make restrictions using the
processing status of the tax data. You can select one of the following
processing statuses:
You can fill the tax reporting date in the document header of the FI-CA
document. However, you cannot set the tax reporting date manually.
Instead you have to add it using a customer-specific module at event 0062.
Contract Accounts Receivable and Payable stores the tax reporting date in
the document header and in the totals records. You can use the tax
reporting date for the EC sales list.
You can also change this date afterward in the transactions for changing
accounting documents. However, this does not have an effect on the documents
in Contract Accounts Payable and Receivable. You cannot change the tax
reporting date subsequently in FI-CA documents.
EC Sales List
The EC sales list assists tax authorities in capturing information for monitoring
the movement of goods within the European Union.
To this end, companies are required to submit an EC sales list to the tax
authorities if they deliver goods within the EU or provide other services in the rest
of the EU, for which the recipient, who resides in another EU country, is subject
to tax.
Contract Accounts Receivable and Payable supports you in creating the EC
sales list for services you have provided.
Prerequisites
You have activated the creation of entries for the EC sales list for each
company code in Customizing for Contract Accounts Receivable and
Payable under Basic Functions EC Sales List Make Specifications
for EC Sales Lists . With the type of reporting date, you specify here the
date that the system uses for recording the data for the EC sales list the
posting date, document date, or net due date.
Reversal There is an entry in the recording table for the original document (that
is, the document being reversed).
Features
The data for the EC sales list is recorded in Contract Accounts Receivable and
Payable at the time the document is posted or reversed. The system stores the
data in table DFKKREPZM.
Note the following with regard to the fields of table DFKKREPZM that are listed in
the table below.
Field
Note
Reporting
Date Type
(DATTY)
Date (DATUM) The field contains the date that the system uses during the
selection of data for the EC sales list (posting date, document
date, or net due date).
However, if a tax reporting date is entered in the document, the
system uses that date as the reporting date.
Sequence
Number
(LFDNR)
If multiple FKKOP lines were posted with the same key data
(BUKRS, DATTY, DATUM, GPART, OPBEL), then the system
generates an additional entry. The sequence number then
receives the next highest number.
Country
Currency
(LWAER)
Country for
Tax Returns
(LSTML)
The system always fills this field with the country of the company
code.
Number of
Reversed
Document
(STBEL)
VAT
Registration
Number
(STCEG)
Country of
Business
Partner
(LAND1)
Name of
Business
Partner
(NAME1)
The system groups entries in table DFKKREPZM with the same company
code (BUKRS), same VAT registration number (STCEG) and same tax on
sales/purchases code (MWSKZ). If the +/- Sign for Availability
Control (BP_SIGN) indicator is set, then the positive/negative sign of the
amount is also treated as a separating criterion.
The indicator for whether it is a triangular deal within the EU (field XEGDR)
is never filled in Contract Accounts Receivable and Payable, since it is not
possible to specify this.
RFKK_REPZM_DISPLAY_DB
The program displays the data that the system recorded for the EC sales list
in database table DFKKREPZM.
RFKK_REPZM_DISPLAY_FI
The system displays the data in the form in which Contract Accounts
Receivable and Payable transfers the data to the general ledger for the
purpose of creating the EC sales list.
SAP does not provide any maintenance for these programs.
Activities
You create EC sales lists on the SAP Easy Access screen for Accounting
under Financial Accounting General Ledger Reporting EC Sales List
General EC Sales List or Belgium EC Sales List (Belgium) .
To delete data, on the SAP Easy Access screen, choose Periodic
Processing Delete Data Data for EC Sales List .
To initialize recorded data, on the SAP Easy Access screen, choose Periodic
Processing Data for Externals Tax Authorities EC Sales List Add
Missing Entries to Recording Table .
To update VAT registration numbers, on the SAP Easy Access screen, choose
Periodic Processing Data for Externals Tax Authorities EC Sales List
Add Missing EU Tax Numbers .
For more information, see the documentation of the programs.
to a separate system that is used exclusively for the government tax audit. Using
the data retained in this system, you can perform analyses and create extracts
that you can then forward to the tax auditor for evaluation using a data medium
that can be evaluated automatically.
Due to the mass data processed in Contract Accounts Receivable and Payable,
you cannot use the SAP Data Retention Tool (DART) to create the data extracts.
Therefore, for all releases that are still being maintained, Contract Accounts
Receivable and Payable provides separate extractors that you can use to extract
industry and customer fields and to carry out field transformations in FI-CA
events. In SAP industry solutions that use Contract Accounts Receivable and
Payable, you can use further extractors in addition to these basic functions.
The required document data is stored in the tables DFKKKO_SHORT,
DFKKOP_SHORT, and DFKKOPK_SHORT. To manage these tables you can
use the following transactions in the menu under Periodic Processing Data for
Tax Audit Documents.
General
Object-specific
SAP Convergent Charging (SAP CC) and SAP Convergent Invoicing (SAP CI)
process services in the telecommunications area (such as telephone calls and
SMS) through to invoicing the customer. As part of this integration, you can
calculate telecommunications tax using an external tax system and report this tax
to the tax authorities.
Features
Billing for a service that was used takes place in the following steps. In this
process, the two components run in separate systems.
1. SAP Convergent Charging prices individual services and determines the
invoice recipient.
The external tax system is integrated with SAP Convergent Charging. The
first tax calculation for a transaction (such as a telephone call or SMS) takes
place there to determine the gross price for the transaction.
2. SAP Convergent Invoicing groups the priced services into invoices, sends
these to customers, and posts the invoices in Contract Accounts Receivable
and Payable.
SAP Convergent Invoicing calculates the tax again.
3. Contract Accounts Receivable and Payable posts a document (invoice)
that contains the telecommunication tax. At the same time, the tax data is
updated in the external system.
To do so, SAP Convergent Invoicing uses Remote Function Call (RFC) to
call functions in SAP Convergent Charging that calculate and manage the
tax data.
In the standard system, there is no direct interface between SAP
Convergent Invoicing and the external system for telecommunications tax.
The standard system implicitly uses the control software that SAP
Convergent Charging also uses. SAP Convergent Charging transfers the
basic data required for the tax calculation to SAP Convergent Invoicing as
attributes of the billable item. This basic data includes the base amount for
the tax calculation, the type of telecommunications service, and various
location codes (such as, the originating address of the phone call, the target
address, and the address of the invoice recipient). To make this possible,
you have to make sure during the configuration of the billable items that the
required fields are available (see System Configuration for
Telecommunications Tax).
4. If problems arise during the update of the tax data in the external tax
system for instance because the Convergent Charging system is
temporarily unavailable Contract Accounts Receivable and Payable flags
the affected documents for updating later.
You transfer the flagged documents on the SAP Easy Access screen by
choosing Periodic Processing Transfer Tax Data Update Ext. Tax
Systems for Telecommunications Tax .
NOTE
Change open items using the document change function (see Postings
and Documents)
Resetting clearing
If open items were cleared accidentally with a payment, you can reset
clearing.
Reversing a document
When you reverse a clearing document, all items that were cleared by the
clearing document become open items again.
Posting a return
When you post a return for a payment document, all items that were cleared
by the payment document become open items again.
Cleared Items
Definition
Posting to a contract account when the posting represents a no longer existing
receivable or payable. A cleared item is produced when an open item is cleared
by an accounting transaction such as a payment or reversal.
Use
A cleared item documents when and how a open item was cleared.
Structure
The following data is included in the cleared item in addition to the information
that was already contained in the open item:
Clearing date
Clearing reason
Clearing currency
Clearing amount
Document number of the clearing document
Posting date of the clearing document
Clearing Documents
Definition
Any document that clears previously open items when it is posted is known as a
clearing document. Examples of clearing documents are payment documents
and reversal documents.
Use
Each accounting transaction that leads to the clearing of open items is stored as
a document. In the document header you can see who conducted the clearing,
when and how.
Additionally, the clearing document is responsible, as are other documents, for
the updating of the account balance.
Structure
Each document consists of a document header and line items. A clearing
document also contains the items that it cleared. These items are recognizable
by their containing the document number of the clearing document in a special
field.
If statistical items are not considered, the balance of a clearing document is zero
for all of its items and all items it cleared.
...
To start the report, choose one of the following paths:
Roles
Receivables
Administration(SAP_FI_CA_RECEIVABLES_ADMINIST) Automati
c Clearing
40.
2.
Assign a date ID and an identification that you can use to identify the
run later, and enter the required selection parameters on the tab
page General Selections.
41.
3.
Schedule the program run. For more information, see Functions
for Scheduling Program Runs.
Resetting Clearing
Use
It may be necessary to reverse a clearing of open items as well as all postings that were
created automatically during the clearing. Depending on the situation, you reverse the
clearing with various functions as shown in the following table. Note that there are other
functions besides Reset Clearing with which you can reverse clearings.
Situation
Choose the
following
function:
Reset
Clearing. For
more
information,
see the text
that follows.
Reversal (see
also Entering
Documents)
Posting
Returns
Lots (see
Returns)
The document for one of the cleared items must be reversed (for
example, invoice issued for the wrong amount).
On the initial screen of the transaction Reset Clearing (menu: Document Reset
Clearing), choose Parts of Clearing in the Settings area. You define the posting of the
clearing amount in the area Posting the Clearing Amount using the relevant buttons
(Retain Distribution to Accounts, Create One Open Item, Clearing Amount in
Clarification Account). For more information, see the documentation for the selection
buttons.
If you partially reset clearing, you can only specify for a group of items (and not for each
cleared item), whether clearing is to be reset. The system groups the cleared items
according to the following criteria:
Business partners
Contract account
Contract
Company code
Business place (Korea)
Business area
Collective bill number
Industry
Document number
Reference document number
Posting the clearing amount
You can reset clearing as follows, depending on the initial situation:
You can create a new open item in the amount of the clearing document.
This item is posted to one of the contract accounts involved in clearing.
When you reset, wholly or in part, the clearing for an incoming payment document that
was posted through a payment or check lot, a new clarification case for incoming
payments is created automatically or the amount in an existing clarification case is
adjusted. If the clarification case is created for a payment lot that has already been closed,
the status will change again to Postprocessing Necessary.
Resetting Clearing in Other Transactions
You cannot post reversals and returns if the document to be reversed or the payment
document contain items that have already been cleared. Typical examples are payments
on account, budget billing payments, and other down payments that have already been
cleared.
You can reset obstructive clearing during processing of returns and reversals. To do this
in a returns lot, set the indicator Enhanced Returns Processing. For a reversal online, the
obstructive clearings are listed and you can reset them in the background or online. When
you reset obstructive clearing, you can also only partially reset clearing; this enables you
to only reset the clearing information in the document/payment document to be reversed.
The clearing is only completely reset if the clearing document was posted in a release
before 4.71 and budget billing requests, down payment requests, or statistical charges
receivables were cleared or if interest on arrears was calculated and posted during
clearing.
Purpose
You use this component to display the debit and credit items posted to one or
more contract accounts.
Features
You can use selection criteria to limit the selection of items to be displayed. For
example, you can only select cleared items or items which were posted in a
particular period.
You determine what information is to be displayed from the document by means
of line layout variants. Line layout variants of the "totals variant" type define the
fields by which items are to be displayed in accumulated form. You can switch
between the variants as required within the account balance display. You define
the required variants in Customizing.
There is also a search, sort and summation function in the account balance
display.
Account Balance
You can display the account balance as a list or an ALV Grid Control; it is divided
into sublists that are displayed on tab pages:
Down Payments
Payment list: Display of the incoming and outgoing payments with the
following information:
You can configure the layout of the header area to meet your requirements in
event 1217; specify the number of a subscreen on which you want to display any
additional data.
You can call up a context menu by clicking on the right mouse button when the
cursor is on an item in the account balance. In events 1247, you can adjust and
supplement the functions of the context menu to meet your requirements.
Selecting Items
Use
Before you access the account balance, you can determine which items are to be
selected.
Prerequisites
Posted items that match the selection criteria must be available in the system.
You have defined the selection fields in the Implementation Guide for Contract
Accounts Receivable and Payable under Basic Functions Account Balance
Display Select Fields for Selection Function.
Features
The items are selected. The list is structured according to the list layout variant
used.
You can integrate the selection screen directly in the account balance
display.
You can place a variant of the account balance next to the standard
account balance and integrate the selection screen in this variant.
Activities
To create a variant of the account balance with an additional selection screen,
proceed as follows:
1. Define a structure with the fields that you want to display on the additional
selection screen.
2. Create a PAI module, and in the top include of the corresponding function
group, make the structure available that you defined in the first step. You
If you enter a business partner, the list contains all contract accounts of
the business partner.
If you enter a business partner and a contract account, the list contains
all contract accounts of the business partner.
If you enter a contract account, the list only contains this contract
account.
The name of the contract account also appears. You can see the name and
number of the business partner in the first line in the list.
If you double-click on a specific contract account line, the item list then contains
only those items that belong to this contract account. If you want to display all of
the items for the business partner again, double-click on the line for the business
partner.
In the following cases the navigation area does not appear:
When selecting the items you selected the postings from other partners.
This means that in the detail view of the list category, you have set the
indicatorWith Postings from Other Partners.
Line Layout
Use
The line layout is the definition of the list format for the items to be displayed. Line
layout variants consist of a number of fields. These constitute the columns of the list and
therefore determine the line layout of a list line. All lines in the list have the same line
layout. The line layout also determines the output of the cleared items for a payment
document in the payment list.
The category of the line layout variant is an important attribute: Single item variant or
totals variant.
With totals variants, the selected items are cumulated before the output for all nonamount fields of the variant, so that a variant that only consists of a business
partner/contract account/amount only gives one list line for 100 items with the same
business partner/contract account.
Prerequisites
You have defined line layout variants in Customizing (see IMG structure: Contract
Accounts Receivable and Payable Basic Functions Account Balance
Display Define Line Layout Variants).
Features
The system outputs each output line in accordance with your specifications of the line
layout. If the totals variant is the category of the list layout variant, the single items are
cumulated before output.
You can also define a hierarchy of line layout variants. In the system, this is defined as a
totals variant with subsequent variants. This hierarchy has a maximum of four levels.
S10 Partner/account
S11 Partner/account/due date
S12 Partner/account/due date/document
In the line layout, you can define a Pointer field (field name, POINT) - normally the first
field of the variant. Click on this field to display the items of the selected lines in the next
lowest variant.
Balances Variants
Definition
A balances variant covers balances whose type of calculation you define in
Customizing.
Use
In addition to the totals in the account balance display, in Customizing you can
create balances variants that you then select on the initial screen of the account
balance display.
You configure balances groups in the Implementation Guide for Contract
Accounts Receivable and Payable under Basic Functions Account Balance
Display Define Balances Groups. Here you define which balances categories
are to be used in the rows for the table display and which balances grid is to be
used in the columns.
You summarize the balances groups into balances variants in the activity Define
Balances Variants. (You can also hide individual balances for a balances
variant.)
Structure
The system groups the individual balances of a balances variants in balances
groups (for example, payments) and displays them in a table.
Example for a balances variant
Payments
Open
Due
Due since 30
Days
Payment on
account
140
140
140
Down payment
160
160
160
Down payment
clearable
390
390
390
balances group. These line items can be read per line of the table (for
example, payment on account or down payment).
For each column of the display, the balances categories are
subdivided by balances intervals (for example, open, due since 30
days).
A balance is therefore the combination of a balances category and a
balances interval. In the example, the "Payments" balances group
shows a balance of 160 for the "Down Payment" balances category
and the "Due" balances interval.
SAP supplies a standard variant. The system only calculates balances
automatically for the combinations of balances categories and balances intervals
delivered in this standard variant.
If you define your own balances variants with balances different to the
combinations contained in the standard variant, you have to implement the
calculation of these balances in event 1299.
SAP provides a time-based balances variant for the industry
component Public Sector Contract Accounts Receivable and Payable.
Activities
Specify the additional fields you want in Customizing for Contract Accounts
Receivable and Payable under Basic Functions Account Balance
Display Select Additional Fields to Be Displayed.
To display an additional field in the account balance, place the cursor on the field
in the list and choose Settings Additional Field.
To hide an additional field, choose Settings Additional Field Off.
Result
In the list
For example, on the
fieldDoc.Date 06/01/02
Features
If you position your cursor on a field in the basic list:
Meaning
Green
Paid
If you want to use balances variants, you made the necessary settings in
Customizing for Contract Accounts Receivable and Payable under Basic
Functions Account Balance Display Balances Variants.
See also the documentation for these activities.
Procedure
42.
1.
Choose one of the following paths:
Roles
Information about Business Partner
Account (SAP_FI_CA_PARTNER_ACCOUNT_INFO) Account
Balance
44.
45.
46.
47.
1.
1.
2.
You define the account balance role parent company and enter it as a
selection criteria in addition to the business partner.
The account balance display therefore displays not only the items of the
business partner, but also all items of the subsidiary companies.
3.
If necessary, restrict your selection to an installment plan, a
collective bill, or a reference document number.
4.
Using the list type, select the items.
5.
Specify whether you also want to display items from the archive,
along with due and (partially) paid budget billing/payment requests.
6.
Set the User-Specific Selection indicator, if you want to use your
own selection criteria that you have already defined. To create your own
criteria, read the documentation for the indicator. To specify selection
criteria:
...
a.
Choose
Selection conditions
b.
Select a maximum of three fields, then
choose Continue.
3.
c.
In the dialog box that appears, include or exclude
values for the selected parameters from the selection. Specify the
type of link between these values.
4.
d.
Confirm your entries.
48.
7.
Choose the type of display.
Using the balances variant, you can control which balances are calculated
and which balances groups are displayed.
49.
8.
The following functions are also available in the toolbar:
Pushbutton
(Period for Item Selection)
50.
9.
Choose Continue.
In addition to the standard initial screen, there is also a reduced initial screen that
only contains the Business Partner, Contract Account, Contract, andCompany
Code fields. Choose the Further details pushbutton to switch between the two
variants.
User-Specific Settings
You can make all user-specific settings (SPA/GPA parameters) for the account
balance display from the menu by choosing Settings Display/Change (or by
choosing the pushbutton
(Display/change settings) in the initial screen or in
the list. When you save your entries, the system updates the user master record.
If you set the Propose tab last active indicator, a new list always begins with the
last screen that was active in the previous list.
Result
The system displays the basic list.
See which
items are still
open
See which
items are
cleared
See the
remaining
amount of a
receivable
See partial
payments
See which
invoices were
cleared by
which
payments
Display
Choose a list type with
payment data the With Cleared
Items indicator
Important information:
Hide
reversals
Display debit
and credit
amounts in
different
columns
Define a
hierarchy of
line layout
variants.
Show the
clearing
history of an
item which
could not be
collected
despite
multiple
attempts
See which
items were
originally paid
by a payment
that was
reversed
Show bank
data for a
payment
Show
payment
transactions
Display a
chronological
list of
transactions
for the
account
Display the
Place the cursor on the SD
archived
document in account balance
document/SD display. ChooseInvoice.
billing
document for
an SD
document
Display the
original
document
from the
Accounting
interface for
any FI-CA
document
Display installment
plan items for a
specific installment
plan
Important information:
Important information:
Access further processing (such as, changing and reversing) for the
displayed items
Features
To navigate from the account balance display to the processing functions for the
document, select the document. Then in the menu, choose Environment
Document and one of the following menu functions:
Menu Entry
Function
Change
Reverse
Display :
Item
Logical View
Physical View
Payments/Returns
Invoice
For Installment Plan Item: The system displays the installment plan for the
installment plan item.
Installment Plan
Source Receivables
Collective Bill Line Items
Histories:
Dunning History
Clearing History
Interest History
Interest Supplement
Dispute Case
To navigate from the account balance display to the processing functions for
payment data, select the payment amount or the document. Then in the menu,
choose Environment Payment Data and one of the following menu
functions:
Menu Entry
Function
From Payment
Run
From Payment
Lot
From Returns
Doc
Payment Usage
To navigate from the account balance display to a processing function for the
selected contract account, choose Environment Account from the menu
and then choose one of the following menu functions:
Menu Entry
Function
Note
Mass Change
Account Maintenance
Installment Plans
Dunning Notices
Returns
Collection Agency(Submit
to Collection
Agency,Release for
Collection)
Write-Offs
Dispute
Cases(Create, Display)
Additional
Corrections: The system
Data(Corrections,Security displays items with individual
Deposits)
value adjustments.
Security Deposits: The system
navigates to the initial screen of
the transaction for displaying an
overview of security deposits
(transactionFPD2).
Creditworthiness
To navigate from the account balance display to a processing function for the
selected master data, choose Environment Master Data from the menu
and then choose one of the following menu functions:
Menu Entry
Function
Business Partner
Change Business
Partner
Contract Account
Change Contract
Account
Contract
Change Contract
in the list category, you make the setting that the original items for
installment plans are to be displayed, the system ignores the
snapshot for the display.
Activities
For a snapshot to reflect the current data status, you have to update it at regular
intervals.
If you are in a snapshot display, you can deactivate the snapshot from the menu
via Account Balance Current Status. The system then reads the current data.
If you select by contract account or contract, you can use the new event 1219
here to determine a business partner.
4. If required, enter a contract on the Master Data tab page and, if you want
to charge the customer, enter a charges schedule on the Charge
Posting tab page. On the tab page Print Parameters, define the required
form and select an output device.
rint Workbench
Purpose
The Print Workbench is a central development environment for creating
standardized outgoing correspondence. To configure the forms, the Print
Workbench uses the SAP standard components for configuring forms
SAPscript forms, Smart Forms, and SAP Interactive Forms by Adobe.
The Print Workbench is subdivided into the following subobjects:
Form classes
Form classes are defined by SAP applications and contain modeling, as
well as access instructions for all of the data that belongs to an application
or an application process. You can use form classes to create application
forms where you access the data defined in the form classes. Invoices,
dunning notices, and account statements are examples of form classes.
The form classes are delivered with each application component that uses
the Print Workbench. Changes to form classes delivered have modification
status.
Application forms
You create application forms based on the form classes delivered. You can
define several application forms for each form class, for example, different
invoices for different business partner groups. SAP delivers example forms
that you can use as a reference for your own application forms. You can
use user exits to adjust the application forms to your requirements.
Numerous help functions simplify form creation.
You can call up the Print Workbench using the area menu PWB.
Integration
The Print Workbench (CA-GTF-PWB) is a component of SAP Web Application
Server and it can be used with no further prerequisites by every other SAP
application. In the Print Workbench you can use Smart Forms (BC-SRV-SSF),
SAPscript (BC-SRV-SCR), or SAP Interactive Forms by Adobe (BC-SRV-FP).
Architecture of the Print Workbench
Form Classes
Definition
The form class is an application-specific object that contains both the underlying
data hierarchy for the application and the database access required for data
procurement in the form of ABAP/4 coding. When creating the data hierarchy,
particular emphasis was given to a logical view of the data model. Therefore, the
form classes are comparable to logical databases. In contrast to logical
databases however, they have the advantage that they can swap two equal
levels and duplicate a level in application forms.
Use
Form classes are used by application forms to create forms, that is,
correspondence.
Structure
A form class consists of a hierarchy representing a logical view of the data model
for each application or an application process. The related Form Class
Librarycontains access instructions in the form of ABAP subroutines. Further
controlling properties are defined in the Attributes of a form class.
Integration
Form classes are a fixed component of an application and cannot be changed or
replaced. Form classes are usually independent of the use of the data and
particularly of the category of the application form.
Application Forms
Definition
Application forms are configuration objects and integrate the data structure
defined in the relevant form class, data procurement, the form logic you have
determined, and the form layout. You can determine the form and scope of the
data procurement as required and add your own data using user exits. You can
also choose between the basic tools for creating the form layout Smart Form,
SAPscript form, or SAP Interactive Forms.
The form class assigned to an application form determines the structure of the
data delivered by SAP. When you create an application form, you have to specify
the form class. Afterwards, you can no longer change the form class.
Use
If standardized correspondence is to be created from an application process, you
have to configure application forms. If the application uses the Print Workbench
as configuration tool, it provides a form class that you have to set as an attribute
in the application form.
Structure
The application form consists of:
Properties/attributes
Hierarchy
The core of an application form is the hierarchy. This has a similar function to the
form class, but is extended. In the context of application forms, the form levels
represent events in the flow logic of the form. In the events you can define further
activities, such as the call of a user exit or, in the case of SAPscript, the call of
texts.
The status of the application form provides information about whether the
application form has no errors and can be run and whether the generated print
program is up-to-date with regard to the application form and its subcomponents.
Integration
An application form is closely linked with the related form class and integrates the
data model and the related data procurement of the application with the
requirements of the SAP customer. The generated print program integrates:
Collection
Definition
A collection is an application form of the form type collection.
Use
You use collections to group application forms so that you can process them together. In
a collection, you can group both application forms from the same form class, and also
application forms from different form classes. You can define your own parameters for
the technical components of a collection, for example, a specific printer. You can classify
the individual application forms so that they are issued sequentially or bundled. You can
process collections using transaction EFRM (SAP menu: Print
Workbench Application Form Process), as for application forms.
Structure
Each collection is assigned to exactly one form class. As for each application form, a
collections assignment to a form class defines how it belongs to an application. Using
the indicator Cross-Form Class, you can control how application forms from other form
classes can be included in a collection.
In the user exit include and the user top include, you can define the form routines of the
user exit or your own data definitions, just as for an application form. These includes are
automatically included in the generated module. They are processed at runtime.
For each collection the system generates a local module that contains the complete
process flow for the collection. This module also contains the calls of the module
EFG_PRINT for printing the application forms to be processed. During printing, the
collection transfers the selection data to the included application form via the interface
EFG_PRINT. This means that wherever you can specify an application form in
Customizing, you can also define a collection. If you make changes to the collection, the
form class, or the user includes, the module is regenerated.
A collection is not suitable for combining different components of
the same document if there are direct dependencies or references
between the individual parts, for example, a sequential page
numbering or a connection at the end of the last page. Collections
must not contain collections or links.
Example
Grouping of technically separated documents, such as an invoice and the attached
payment form, or an e-mail with an electronic document attached.
printing. The difference is in the use of send control, which is triggered in the module
EFG_PRINT_EXPANDED.
The SAP system has no control for external print logistics, such as postage
optimization or control of printing processes. Outside of the SAP system, form
data and other data is increased, or the correspondence categories are sorted
and mixed. For large volumes of data, SAP therefore recommends external
processing by means of an output management system.
BOR object key (key field)
Form classes
From date
To date
Frequency
Priority
The search for related print action records must be integrated in the form class.
This is usually displayed by an appropriate form level in the form class. The form
level must also be integrated and active in the application form in which it is
used. To create individual print action records, choose Print Workbench Print
Action Records Create in the menu. If you want to create several print action
records simultaneously (mass processing), you have to create a report using the
report SAPRISU_PRINTACTION_GENERATE delivered by SAP as a reference.
The print action records are integrated in an application form either by means of
a form level that corresponds to the BOR object of the print action record, or,
alternatively, you can integrate the search for print action records in the user
exits of an application form by means of the programming interface.
If a print action record is determined during the printing transaction, if you use
SAPscript, you can display the content immediately in the MAIN window or store
it temporarily as a variable and then output it as a symbol. In the case of Smart
Forms, the print action record must be saved as a variable and then output as
symbol.
Features
Correspondence is created and issued by means of the integrated use of the
following components:
Correspondence Tool
Print Workbench
SAPscript
Smart Forms
PDF-based forms
The exact form of the correspondence creation and issue is dependent on the
using application.
Correspondence
Purpose
Correspondence is essential for the business processes of companies.
Correspondence, which is created daily in great numbers and sent to customers
in the form of letters, faxes, and e-mails, fulfills various communication purposes:
Transfer of information
(for example, notification about changes to conditions)
Correspondence is created:
Correspondence tool
The correspondence tool manages the process of correspondence creation
using correspondence requests.
Print Workbench
The Print Workbench creates print programs and obtains and configures
data. The Print Workbench enables you to configure the layout of
correspondence to meet your requirements. You can send correspondence
in different ways: as a letter, e-mail, fax, or SMS. If you output
correspondence as a flat file, you can process the data externally with an
output management system (OMS).
Constraints
The following functions are not part of correspondence creation and need to be
performed in an output management system:
Prerequisites
The desired correspondence variant must be defined in the master record of
the contract account to be processed.
Process Flow
13.
...
54.
1.
Enter the parameters for the correspondence creation run (see
Functions for Scheduling Program Runs).
55.
2.
Schedule a correspondence creation run or start it immediately
(see Functions for Scheduling Program Runs).
56.
3.
Using the correspondence variants defined in the contract account
master record, the correspondence run determines the relevant
correspondence data and stores it in the correspondence container (one
data record per print output).
Result
The correspondence data determined is in the correspondence container.
To print the correspondence you can now perform the correspondence print run
(see Printing Correspondence).
Correspondence Types
Use
A correspondence type groups correspondence of the same
category. Correspondence types define which data can be stored in the
correspondence container for creating correspondence. For detailed information
about correspondence types, see the Correspondence Types section of the
documentation of the correspondence tool. For information about the
correspondence types you can use in Contract Accounts Receivable and
Payable, see the sections Creating Individual Correspondence and Periodic
Correspondence.
For instructions on how to define your own installation-specific correspondence
types, see SAP Note 194899.
Integration
If you implement your own correspondence types, you can set the following
indicators when you save the correspondence using the function module
FKK_WRITE_CORR:
Payment Forms
Use
If you send correspondence to a business partner requesting that he make a
payment, you can enclose a payment form. The system automatically assigns
the payment form number. In the system, all open items that make up the
payment amount stated on the payment form are recorded under this number.
Open items can be considered for several payment forms (for example, on a
payment form for dunning or on a payment form for an invoice).
Prerequisites
You have made the settings required for payment forms in Customizing for
dunning and correspondence.
To print payment forms, Contract Accounts Receivable and Payable uses the
country-specific data for attached payment media from the component Financial
Accounting (FI). There you have to define the payment form ID for the attached
payment forms created when you print installment plan notifications and cash
security deposit requests for each company code. To do this, in the
Implementation Guide for Financial Accounting choose Financial Accounting
Global SettingsCorrespondence Attached Payment Media CountrySpecific Data for Attached Payment Media and for each country and payment
method, define a function module that determines the data to be printed on the
attached payment media.
In Customizing, define the payment form ID for each company code. To do this,
in the Implementation Guide for Contract Accounts Receivable and
Payablechoose Basic Functions Correspondence Define Payment Media
ID for Forms.
SAP delivers the number ranges for creating payment forms. You can check the
number ranges in the Implementation Guide for Contract Accounts Receivable
and Payable under Basic Functions Correspondence Check Number
Ranges for Payment Forms.
Features
You create payment forms during dunning in the application
component Correspondence and in the Account Balance. For detailed
information about how to create payment forms in the account balance
see Creating Payment Forms from the Account Balance. For information about
creating payment forms during dunning, see Creating Correspondence.
The system assigns the payment form number automatically. In the system, all
open items that make up the payment amount stated on the payment form are
recorded under this payment form number. Open items can be considered for
several payment forms (for example, on a payment form for dunning or on a
payment form for an invoice). When you print the form the system determines the
payment form number and provides the payment form data. The related line
items are noted in a payment form file under the payment form number.
When you are processing incoming payments, you can select the open items
using the payment form number.
To display all open and cleared items in a payment form, choose one of the
following menu paths:
Role
Incoming Payment
Processing (SAP_FI_CA_INCOMMING_PAYMENTS) Payment Form
Items Overview
SAP Menu
Payments Clarification Activities Payment Form Items
You can select several payment forms with the same reference number.
During clearing (with a payment lot, for example), you can select the open
items in a payment form using the payment form number, provided that the
business partner used the payment form to make the payment.
You can delete payment forms. To do this, choose one of the following paths:
Role
Archiving (SAP_FI_CA_ARCHIVING) Delete Payment Forms
SAP Menu
Periodic Processing Delete Data Payment Forms.
Printing Correspondence
Purpose
The correspondence printing run determines the correspondence data that has
been stored in the Correspondence Container as part of correspondence
creation, and transfers it to the print workbench (see also Printing
Correspondence with the Print Workbench), possibly with additional data
(controlled by the correspondence type and industry-specific events). You can
select the correspondence to be included in a correspondence print run
according to business partner, contract account, contract, company code,
application form, or parameters that you are free to define. For example, in a
program run you can consider all invoices for business partners 1000 to 3000
that are due in calendar week 31, or all dunning notices of dunning level 1.
The data for the print output is prepared in the print workbench. The following
types of output are possible:
To control the sending of correspondence via application forms, you can define
an installation-specific function module for event 0778. See the documentation
for the sample function module FKK_SAMPLE_0788.
You can provide the correspondence requests with individual sort criteria. For
example, you can print correspondence sorted by postal code and therefore
reduce postage expenses.
Prerequisites
The correspondence data to be printed has been stored in the correspondence
container during correspondence creation.
Process Flow
14.
...
57.
1.
Enter the parameters for the correspondence print run (see Entering
Parameters for the Correspondence Print Run ).
58.
2.
Schedule a correspondence print run or start it immediately
(see Scheduling a Correspondence Print Run ).
59.
3.
In a correspondence print run, the system determines the
correspondence data from the correspondence container and outputs the
data to the printer spooler.
Result
The correspondence data is available in the printer spooler either as raw data or
in SAPscript format. You can now view the job log for the correspondence print
run (see Displaying Job Logs for Correspondence Print Run).
Information on the history of all correspondence is stored in the correspondence
history (see Displaying Correspondence History).
742 - Checks the master data for any dunning locks, and determines the
dunning procedure
Correspondence History
Use
The correspondence history displays the correspondence that is in the
correspondence container. You can tell by the print date whether the
correspondence has already been printed.
Prerequisites
The selected data has already been created and is in the correspondence
container. You have maintained the required correspondence status in the
Implementation Guide for Contract Accounts Receivable and
Payable under Basic Functions Correspondence Define Status for
Correspondence.
Features
You have two options for using the correspondence history as part of the
correspondence tool (see Correspondence History) or as an applicationspecific form of Contract Accounts Receivable and Payable.
In Contract Accounts Receivable and Payable, in the correspondence history you
can use the following functions in addition to the functions of SAP List
Viewer(ALV):
Pushbutton
Function
You can also use the following functions for inbound correspondence:
Pushbutton
Function
with the quick info text Dunning Lock Set a dunning lock for inbound
for Inbound Correspondence
correspondence
This dunning lock is considered in the
correspondence dunning run and can
prevent correspondence dunning.
Alternatively, you can call up the functions listed above under Goto in the menu.
Under Settings Display Variantin the menu, you can use the
functionCurrent.... to modify the display variant to meet your requirements.
Via Choose...., you can use previously defined display variants.
You can use authorization object P_CORR to protect the following activities in
the correspondence history:
Change status
Integration
In Financial Customer Care (FCC), you can create correspondence manually in
the documentation view. You can access this view from the navigation bar or
from the transaction for processing collection work items.
Prerequisites
You have defined correspondence templates for creating correspondence
manually. (See Customizing for Contract Accounts Receivable and Payable
under Basic Functions Correspondence ).
Features
The Web Dynpro application provides a framework with which you can:
FKK_WDY_CORR_MANUAL
CORR_MANUAL_GAF_CONF
FKK_WDY_CORR_MANUAL
Enhancement option
The BAdI of the ISR scenario provides the following events for
enhancements:
LOAD_DATA_EVENT
This event runs in steps 2 and 3.
REFRESH_DATA_EVENT
This event runs after the event of the Web Dynpro add-on;
you can enhance the correspondence creation step in the
Web Dynpro interface IF_FKK_WDY_CORR_ADDON.
CHECK_DATA_EVENT
This event runs in steps 3 and 4.
In event 0787, you can derive the contents for individual
correspondence recipients (such as, address in PDF-based
form).
Activities
You make settings for the approval workflow as follows:
1. In Customizing, choose Cross-Application Components
Internet/Intranet Services Internal Service Request Scenario
Definition Define Scenarios .
2. Create a scenario for the application MC (Manual Correspondence).
3. At the Version level, enter Entry Using Adobe PDF as the Entry Type
in Web.
Features
For each customer contact, you can create a reference to a data object. For
example, an invoice complaint can contain a reference to the invoice or an object
reference to a service request derived from the complaint.
You can use the note function to enter notes for a customer contact, such as the
reason for a budget billing amount adjustment.
In the customer overview, customer contacts are displayed separately by
contract account. The contact must contain the contract account as an object.
You must therefore ensure that the contact references a contract account when
you create the contacts. In the settings for Customer Contacts in Customizing
for Contract Accounts Receivable and Payable, maintain an appropriate object
reference. The object references are classified by the role they have in relation to
the customer contact. You can set up this role in Customizing for Contract
Accounts Receivable and Payable under Business Transactions Customer
Contacts Define Object Roles. The object references are stored according to
an SAP concept used by the SD document flow and the SAP Business
Partner (CA-BP) where-used list. You can also display links from the linked
objects. To do so, choose System Links.
Procedure
15.
...
60.
1.
Choose Create Customer Contact.
61. 2. Enter the key of the desired business partner
or contact person, make entries in the fields on
the Contact attributes tab page and enter a note if
you wish.
You can enter the business objects linked to the
contact on theBusiness objects tab page. You can
now access the individual objects by double clicking
on them.
If the system creates a contact automatically, the
business objects are derived from Customizing.
You can also use the following additional functions
when you enter a contact:
Change Customer
Contact
Display Customer
Contact
Evaluate Customer
Contact
16.
63.
64.
...
1.
Choose Change Customer Contact.
2.
Enter the key of the contact and
choose Continue.
65. 3. Change the required details and then save
your entries.
17.
...
66.
1.
Choose Display Customer Contact.
67. 2. Enter the key of the contact and
choose Continue. The required customer contact is
displayed.
18.
...
68.
1.
Choose Evaluate Customer Contacts.
69.
2.
Enter the parameters according to which you
want to select the customer contacts in the system
and add further restrictions if required under Time
Restrictions. Alternatively, select the customer
contacts exclusively by the date and time of creation.
70.
3.
Choose
with the quick info text Execute in
the application toolbar.
The program selects the customer contacts, groups them
according to your specifications under List Sorted By
and outputs these groups in the form of a list. Double
click on a group in the list to obtain further details:
interaction History
The interaction history provides a general overview of the correspondence
history, customer interactions, and notes from various sources, and can be
extended as required.
Prerequisites
You made settings for the contact history in Customizing for Contract Accounts
Receivable and Payable by choosing Basic Functions Interaction History .
Features
SAP provides Customizing for displaying information in the interaction history for
the following objects:
Outbound correspondence
Customer contact
By choosing the Find pushbutton, you can locate entries in the list.
By choosing the Find Next pushbutton, you can locate more entries
that meet the same selection criteria.
Filter
Printing
Sort
Features
To lock objects, set a conditional processing lock for them. If the condition occurs, the
system can remove the lock automatically or change it. Using the transaction Check
Conditional Locks (SAP menu: Periodic Processing For Contract Accounts), you must
periodically check whether the conditions for the lock still exist. If this is not the case, the
program removes or changes the lock automatically. The function module that you have
programmed decides whether a lock is removed or changed.
Object
21
Insurance contract
22
41
Utility contract
51
To delete mass locks, you can use the transaction Delete Mass Locks Set on the
SAP Easy Access screen under Periodic Processing For Contract Accounts.
Example
The implementation and processing of a conditional lock is described below
using an example.
An insurance broker is to draw commission for negotiating life insurance. This
commission is only to be paid to him once the policyholder has paid the first
insurance payment.
20.
...
79.
1.
The payment plan interface of the Industry Solution
Insurance creates both documents and enters the business transaction
number. You can then specify this business transaction number as
reference number in the field COND_LOOBJ1.
80.
2.
To prevent the payment of the commission to the broker before the
first payment is received, create the lock in the corresponding program
event when you post the commission document. To do this, use the function
module FKK_S_LOCK_CREATE. You can transfer the business transaction
number to the parameter I_COND_LOOBJ1.
81.
3.
Make the necessary settings in Customizing for Contract Accounts
Receivable and Payable (Basic Functions Dependencies Maintain
Conditional Locks); assign an activity key and choose a lock type and the
application area.
82.
4.
Program a function module based on module
FKK_SAMPLE_CHECK_DOC_PAYED and assign it to the relevant
activities. If you choose the line item as the lock type, program a module
that checks that clearing status of the initial premium document, for
example. If the system determines the clearing status 9 (clearing
successful) in the document, delete the lock by integrating the module
FKK_S_LOCK_DELETE.
Prerequisites
You have defined and generated the required preselections. For information on
how to do this, see the sections under Information System Evaluation of Open
Items Key Date-Based Open Item List (Individual) Definition of
Preselections for Master Data.
Features
You can use preselections that you have created for business partners and
contract accounts with the transaction Define Preselections in the menu
under Periodic Processing Technical Preparations to set and remove
processing locks.
Activities
21.
...
86.
1.
In the SAP menu, choose Periodic Processing For Contract
Accounts Locks According to Preselections.
87.
2.
In the Selection Name field, enter the name of the preselection that
you want the program to use to select business partners and contract
accounts. By clicking the button
Detail next to the input field, you can
display preselected data.
Specify whether you want to set or remove locks.
88.
3.
Define the locks to be set/removed in more detail. Under Lock
Category, specify the business object, and under Process, specify the
business transaction for which the program is to set/remove locks. Specify
a lock reason and the time from which the lock is to be valid or invalid.
Via a specification in the field Problem Class, you determine the importance
that a message must have to be output in the application log.
89.
4.
Run the program.
You can set or remove locks synchronously from the transaction or
synchronously as a background job that is executed immediately. The result of
the processing of the locks is displayed in a log.
Requests
The functions described below are not relevant for the following industry
components:
Insurance
Telecommunications
Media
You can use requests to park and process posting data for incoming and
outgoing payments. In contrast to entering a document, where you have to
specify the G/L accounts to be posted to, when you enter a request you can use
the standard account assignments used in your work area.
Integration
Contract Accounts Payable and Receivable offers a direct link between requests
and earmarked funds documents of Funds Management (PSM-FM). This makes
it possible to have a real-time budget check directly when you post requests,
before the documents are transferred to Funds Management (PSM-FM).
The system generates certain earmarked funds with taxes when a request is
posted. These earmarked funds can receive special items for the taxes, if you
choose. The earmarked funds items for the taxes receive the same account
assignments as the tax items in the FI-CA document that is generated (and the
same as in the general ledger).
In this context, if you reference already existing earmarked funds in a request,
then you have to enter the earmarked funds items for the net amount and the tax
amount.
Features
You post documents with requests in two steps. In the first step, you enter
document data without updating transaction figures. In the second step, the
system uses the posting data entered in the request to create an accounting
document in Contract Accounts Receivable and Payable. There are two different
types of request in Contract Accounts Receivable and Payable:
Requests
You use requests as input help for posting one-time incoming or outgoing
payments. The amount and business partner are known. A request results
in an FI-CA document with a specific due date.
Standing Requests
You use standing requests to park periodically recurring incoming or
outgoing payments. You use standing requests if a business partner is to
pay or receive an amount at periodic intervals. The system creates multiple
FI-CA documents with different due dates for a standing request.
Before you convert (standing) requests to FI-CA documents, you can subject
them to a check and approval process by one or more users within a workflow.
You can post the FI-CA documents to be posted for a request either when you
save the request or you can post them separately later using an appropriate
mass run. You make this specification in Customizing. FI-CA documents for
standing requests are always posted separately by a mass run. The system
derives the accounting information required to post the documents, such as G/L
account or posting key, from the contract account posted to or the main and
subtransaction. By entering appropriate function modules for the events 1203,
1209 and 1211, you can display the requests and standing requests in the
account balance. SAP provides the function modules
FKK_EVENT_1203_REQUEST, FKK_EVENT_1209_REQUEST, and
FKK_EVENT_12011_REQUEST that you can enter for these events or use as
templates for your own function modules. Authorization checks can be made
dependent on the company code, the request class, and the request type. You
can use the authorization objects F_KK_ODBUK, F_KK_ODCLS, and
F_KKODTYP for this.
In the industry component Public Sector Contract Accounts Receivable and
Payable, two additional functions are available: general requests and short-term
waivers/remissions.
Processing Requests
With a request you can park the posting data for an individual document.
Prerequisites
You made system settings in Customizing for Contract Accounts Receivable and
Payable under Basic Functions Requests . You can specify:
Whether the system creates an FI-CA document from the data entered in
a request when you save
Whether you want to post the document later in the transaction Create
Documents from Requests (SAP Easy Access screen: Request). If you
want to create the documents later in a mass run, you have to set the
indicator Generate Documents from Requests in Mass Run in Customizing
for Contract Accounts Receivable and Payable under Basic Functions
Requests Define Basic Settings for Document Creation .
If you create earmarked funds for each request item, or you want to reference
earmarked funds that contain a special item for tax, then set the
indicatorEarmarked Funds with Tax in Customizing for Contract Accounts
Receivable and Payable under Basic Functions Requests Define Request
Categories
Features
Creating, Changing, Displaying Requests
You create requests using the transaction Edit Request on the SAP Easy Access
screen under Request. On the upper part of the screen you enter the header
data, on the lower part the items of the request. When you save a request, the
system automatically checks the data for consistency. If you choose
Request Save without Checking in the menu, you can circumvent these
checks and enter incomplete requests in the system if you want to change and
complete them later. Requests that are saved but not checked have the status
Saved incomplete and cannot be converted into FI-CA documents. In the
transaction Edit Requests, you can also display, change, and reverse requests
as well as display the documents created from a request. To do this enter the
request number and choose one of the following pushbuttons:
Pushbutton
Function
(Create)
Create request
(Display)
Display request
(Change)
Change request
(Delete)
Delete request
In the menu under Extras Documents Created , you can display the FI-CA
documents created from a request. For each change the system writes a change
document. You can only change a request provided it has not been converted
into an FI-CA document.
Each time you confirm an entry and each time you save a request, event 6500 is
processed. In this event, you can add to or overwrite the data for request items.
To do so, define an installation-specific function module for event 6500 in
Customizing for Contract Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules . See also the
documentation for module FKK_SAMPLE_6500. If you choose Save without
Checking, the system does not process event 6500.
You can enter requests with a tax code that contains several tax rates. The tax
amount calculated and displayed in the request item is the total of the amounts
for the individual tax rates.
You can enter notes for requests.
You can set payment, dunning, interest, and clearing locks for request items.
However, for each request item and lock, you can only set one lock reason and
one validity period.
Displaying Requests
You can display requests using the transaction Display Document Created from
Requests in the menu under Request Evaluations . The document created
is also displayed for each request. You can select by request number, document
date, and posting date. You can restrict the selection further if you only want to
display requests with a specific request status.
You can also display requests that have already been archived. The system
displays this information in the ABAP List Viewer. There you can use the
standard functions for processing lists.
Creating Documents from Requests
In the transaction Create Documents from Requests (in the menu under
Request Create Documents From Request ), you can convert the existing
requests in the system to FI-CA documents (see Creating Documents from
Requests).
If you create documents from the requests, the notes are transferred to the notes
for the documents.
Locks are also transferred to the documents when these are created.
Printing Requests
You can print requests using the function Print under Request in the menu. When
you print a request, all header data and all request items are available with
additional information about the business partners and contract accounts.
Creation and printing takes place in events 0766 (Print Request) and 0767
(Create Request Printout).
Creating and Processing Standing Requests
Use
You can use a standing request to enter incoming and outgoing payments for
which several documents are to be posted with regularly recurring due dates in
Contract Accounts Receivable and Payable.
Prerequisites
You have made the settings in Customizing for Contract Accounts Receivable
and Payable under Basic Functions Requests.
Features
Creating, Changing, and Deleting Standing Requests
In the transaction Edit Standing Request, in the menu under Request, you can
create a standing request with execution dates.
22.
...
90.
1.
Enter the header data in the upper part of the screen.
91.
2.
Enter the run dates. The run period defines the due dates with which
the individual FI-CA documents are generated. You can:
If more than one run period exists for a standing request, these periods are
displayed in a dropdown box. There you can navigate between the various
run periods.
92.
3.
Enter the items in the lower part of the screen.
You can set payment, dunning, interest, and clearing locks that are then
transferred to the documents when these are created. However, for each
request item and lock you can only set one lock reason and one validity
period.
You can enter standing requests with a tax code that contains several tax
rates. The tax amount calculated and displayed in the item results from the
total of the amounts for the individual tax rates.
93.
4.
Save your entries.
The system saves each standing request under a request number. When you
save a standing request, the system does not generate a document, meaning
that no transaction figures are updated. You post the FI-CA documents
separately in the transaction Create Documents from Standing Requests in the
menu underRequest Create Documents. The system checks whether the run
periods overlap. When you save the standing request, the system automatically
checks the data for consistency. However, if you choose the option Save without
Checking in the menu under Standing Request, the system does not make any
consistency checks. This means that you also have the option of changing and
completing standing requests at a later date.
If you enter notes for a standing request, these are included in the notes for the
documents when you create the documents.
Additionally, the transaction Edit Standing Request enables you to:
Enter the standing request number and choose the relevant pushbutton. For
each change the system writes a change document. However, you can only
change a standing request provided that no document has yet been created from
it or provided that the change does not affect any documents that have already
been posted.
If you have standing requests checked as part of an approval workflow, you can
still change and delete these requests if the standing requests have already been
released.
Each time you confirm an entry and save a standing request, event 6500 is
processed. In this event, you can add to or overwrite the data for standing
request items. To do so, define an installation-specific function module in
Customizing for Contract Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules for event 6500.
See also the documentation for module FKK_SAMPLE_6500. If you
choose Save without Checks, the system does not process event 6500.
In addition to the functions specified above, you can also print a standing request
in the transaction Edit Standing Request. From the menu, choose Standing
Request Print. The standing request is printed using correspondence type
0039. All execution dates and special dates are available for the printout.
Displaying Standing Requests
You can also display standing requests in the transaction Display Documents
Created from Standing Requests by choosing Request Display Evaluations.
The system also displays the documents created for each standing request. You
can select the standing requests by request number, document date, and posting
date. You can restrict the selection further if you only want to display standing
requests for reversed documents or with a specific request status.
You can also display standing requests that have already been archived. The
system displays this information in the ABAP List Viewer. There you can use the
standard functions for processing lists.
History Comparison
You can use the compare function to ensure that reversed FI-CA documents are
no longer considered for standing requests. You can compare the history for
standing requests in the transaction Compare Documents Created from Standing
Requests, under Request Evaluations. You should run this comparison on a
regular basis. For more information, see the program documentation.
General Request
Use
You use this process if you expect the same type of incoming or outgoing
payments, but their amounts are not yet fixed. The general request simplifies the
administration run because a payment can be made without a concrete payment
request in a particular case.
Administration and usage charges are an example of revenues which are
arranged by general acceptance requests.
For example, payment requests can be used for telephone charges or for
minimal expenditures for which immediate cash payment is normal. A request for
database with its own request number. You can find more information
underProcess General Requests.
2.
If an approval workflow is set up in Customizing of Contract Accounting, the
request is automatically forwarded to the person responsible, who approves
it. The approved request can be changed, but must go through the approval
workflow again.
3.
If an incoming or outgoing payment enters the system by electronic bank
statement, the system recognizes that a payment was made due to a general
request from the contract (or the classification key). The payment is posted
like a payment on account as a payment without debits because usually no
acceptance or payment request exists for it yet. The business partner account
assignments (business partner, contract account, contract object) and G/L
account assignments (revenues/expenses, CO account assignments and FM
account assignments) are transferred from the corresponding line of the
general request. You can find detailed information on this under Assignment of
Incoming Payments to General Requests.
4.
You generate debit entries for the payments entered for general requests at
regular intervals. You select general requests using the function Generate
Documents for General Requests. The system checks whether there is a
payment for this general request. If there is a payment, the system generates
a FI-CA document for it, which can be automatically cleared with the
payment, according to the Customizing setting. You can find more information
under Generate Documents for General Requests.
23.
...
5.
You can check the consumption of funds on the general request by
carrying out an evaluation for the general request. Call up the
evaluation Display Documents Generated from General Requests for this in
the Contract Accounting menu. In this evaluation, you can have subtotals
calculated for each request number, which enables you to see the totals of
the payments, which refer to a general request at a glance.
Short-Term Waiver/Remission
Use
The short-term waiver of an open receivable means that the entitlement due is not
pursued immediately. The difference between a short-term waiver and a remission is the
following: with a short-term waiver, the entitlement itself is not waived, whereas this is
the case with a remission.
The prerequisites for using short-term waivers and remissions are defined by law.
Integration
The open receivable must be saved as an open Contract FI-CA document in the system.
Prerequisites
The prerequisites that you require for the function Writing Off Items also apply here.
SAP recommends that you define a separate write-off reason in the Customizing
of Contract Accounts Receivable and Payable for both short-term waivers and
remissions. You can then define additional specifications such as the document type or
type of account determination in IMG activity Define Additional Specifications for WriteOffs in the Public Sector. You can only evaluate short-term waivers and remissions
separately.
Features
You enter short-term waivers and remissions using the function
As the entitlement itself is not waived for a short-term waiver, a check must sometimes
be carried out. You can enter a resubmission date when writing off an item. The
program Resubmission Write-Off evaluates this date. When the write-off document is
submitted again, you can clarify the short-term waiver or set a new resubmission date.
For more information on this, refer to Resubmission Write-Off.
If you have defined a separate write-off reason for short-term waivers in the Customizing
of Contract Accounts Receivable and Payable, you can use the Public Sector WriteOff History, in order to generate a directory for short-term waivers.
Request Templates
Use
You want to use the same data in several requests or standing requests.
Features
You can use a template to create requests or standing requests.
Activities
24.
...
94.
1.
To create a template, in the menu choose Request Edit Request
Templates. Enter a request number and the required header and item data
and save your entries.
95.
2.
To use a template, when you create a (standing) request, choose
the pushbutton
with the quick info text Create with Template and in the
dialog box that appears, enter the number of the required request template.
Features
The programs select all requests or standing requests that correspond to the
selection criteria. The program creates one FI-CA document per request.
The program creates several FI-CA documents per standing request. The system
also checks whether an FI-CA document already exists for each due date that
is, for all dates from the first due date in the standing request to the date that you
have entered under Take account of due dates to in the Date and SR
numbers tab page. If this is not the case, the program creates an FI-CA
document for the due date(s) in question. If a document exists already, the
system does not create any further ones. If an FI-CA document already exists,
but has been deleted, a new FI-CA document is only generated if the history
match has already been carried out. If the comparison has not been carried out,
the program does not create an FI-CA document.
If you create requests with lots of lines, and, under certain circumstances, also
several business partners and contract account, this can lead to an extensive
number of documents that can no longer be displayed in an overview. Therefore,
you can also create documents requests and standing requests per request item.
In the Implementation Guide for Contract Accounts Receivable and Payable,
choose Basic Functions Requests and set the Document indicator in the
activity Define Request Categories.
Activities
26.
...
100.
1.
In the menu, choose Request Create Documents From
Requests/Standing Requests.
101.
2.
Enter a date and an ID that you can use to identify the run later.
102.
3.
Restrict the selection of (standing) requests to be processed on
the tab page General Selections by business partner, contract account, or
contract.
If you are working with standing requests, you must also call up the Date
and SR Numbers tab page and specify the due date to be selected to.
Entering request numbers for selection is optional here.
If you are working with requests, you can also call up the Request
Selection tab page and select given request intervals for processing.
103.
4.
Schedule the program run. You can also carry out a simulation
run.
See also Functions for Scheduling Program Runs.
Using this program, you can transfer open business partner items and requests
at the same time.
Features
If you transfer only open business partner items, this program offers the same
functions as the already existing program for transferring open items. Both
programs evaluate the same Customizing settings, and the same restrictions
apply. For more information, see Transferring Open Business Partner Items.
When you transfer requests that are not yet closed, the program sets the
status Transferred and Deleted for all selected requests, standing requests,
general requests, and request templates, and generates a new request of the
same type. The program replaces the source master data (business partner,
contract account, and contract) with the target master data. The program copies
all other posting information from the source request. The execution data of the
new standing requests are adjusted so that only those due dates are taken into
account for which no documents were generated yet. If you have transferred
requests, the programs for processing requests also display the number of the
transfer request or the number of the transferred request.
To document the reasons for the transfer, you can enter transfer reasons in
Customizing for Contract Accounts Receivable and Payable. There you can also
define default values to automate the entry of the transfer document. You make
these settings in Customizing for Contract Accounts Receivable and
Payableunder Business Transactions Transfers .
The following can be transferred:
system also posts them in this way in the transfer document. In this case,
specifying a target contract is irrelevant.
Activities
To execute the program, on the SAP Easy Access screen, choose SAP
menu Accounting Financial Accounting Contract Accounts Receivable and
Payable Account Transfer Items and Requests .
Business Transactions
You use this component to post and process your business transactions.
Within Contract Accounts Receivable and Payable, these processes are largely
automatic. They are controlled by the settings you make in Customizing, which
you assign at business partner/contract account level. However, you can also
enter them in the line item if this particular line item is to be processed
separately.
Features
This component consists of the following detailed components:
Security Deposits
Payments
Interest Calculation
Dunning
Collections Management
Returns
Promises to Pay
Write-Offs
Collective Bills
Purpose
A collective bill groups documents from different contract accounts in a collective
bill document in order to process them together.
Features
You can manage and process all of the individual documents in a collective bill
document together via a third account the collective bill account. You can
create a joint invoice and make the payment or in the case of payment arrears,
dun all of the items in the collective bill together.
Example
Collective bills are particularly useful for billing property management, residential
construction companies, and companies with branch-head office relationships.
A residential construction company handles the payment transactions with the
relevant utilities companies for its tenants (payments, dunning notices, returns,
correspondence). The utility companies manage each tenant of the residential
construction company and the related receivables in its SAP System but
summarize these receivables in a collective bill and process the collective bill via
the residential construction company. The residential construction company pays
the receivables that arise with the utility company for its tenants and then bills
these to the tenants.
Relationship of the collective bill account to the individual accounts
Procedure
At master data level, you have to assign the individual contract accounts to a
collective bill account. A collective bill account is a contract account of the
contract account category collective bill account. You have to define this account
in the master record of every contract account whose postings you want to group
in a collective bill. There is no change to the assignment of contract accounts
that you link via the collective bill account to your business partners. To link an
account with the collective bill account:
27.
...
104.
1.
In the SAP menu, choose Contract Account Create or Change.
105.
2.
In the field Collective Bill Account in the area Invoice Creation on
the tab page General Data, enter the required collective bill account.
Once you have assigned the account to a collective bill account, when you enter
posting documents in this account, each business partner item is automatically
linked to a statistical posting document (collective bill document) in the collective
bill account. The posting item for the collective bill document has the statistical
key S (collective bill item). In the items of the individual documents, the
field Number of Representative Document of Contract Accounts Receivable and
Payable(DFKKOP-ABWBL) is filled with the document number of the collective
bill document and the field Category of the Representative Document of Contract
Accounts Receivable and Payable (DFKKOP-ABWTP) is filled with the value S.
You can summarize several posting items for one or more individual accounts of
a collective bill account in one collective bill. The individual posting items are
summarized in one collective bill according to the following criteria as standard:
Origin
Posting date
Due Date
Currency
If you completely clear a collective bill document, the system clears the
related individual line items completely.
If you partially clear a collective bill document, the system splits the
clearing amount over the related document line items in accordance with
the specifications in clearing control.
The clearing involves two steps:
28.
...
106.
1.
Assignment of the clearing amount to the statistical collective bill
item
The assignment can take place, for example, manually or automatically in
accordance with the rules defined for the respective clearing process (for
example, for payment lots, cash desk, automatic account maintenance) in
clearing control. A separate clearing type is reserved for each process in
clearing control.
107.
2.
Split of the clearing amount of the statistical collective bill item
determined in the first step over the related individual documents
The automatic split takes place independently of the underlying clearing
process based on the clearing control rules defined for clearing type 20s.
The clearing type 20s by SAP as standard.
A clearing variant defined for clearing type 20s must ensure that the clearing
amount due for the collective bill is distributed completely to the related
document line items. The clearing variant must not use rules for automatic writeoff of tolerance variances. If the individual documents cannot be split, the
clearing process issues an error message. In this case, check the Customizing
for the clearing variant concerned.
In the individual business processes, clearing takes place as follows:
Business
Process
Automatic
clearing
Account
maintenance
Payment Run
Payment Lot
Cash Desk
Example
For the collective bill document 8711 in the amount of 398, consisting of
individual documents 4712 in the amount of 116, and 4713 in the amount of 232,
there is a payment for 150. Using the clearing control, the system determines
that the clearing amount leads to complete clearing for document 4712 and
partial clearing of document 4713. Once you have posted the payment document
0815, the following items arise for the documents specified:
Document 8711
Item 1, subitem 0: Amount of 198 still open
Item 1, subitem 1: Cleared with payment document 0815
Document 4712
Item 1, subitem 0: Completely cleared with payment document 0815
Document 4713
Item 1, subitem 0: Amount of 198 still open
Item 1, subitem 1: Cleared with payment document 0815
Include open items for a contract account that belongs to a collective bill
in an existing collective bill or create a new collective bill for these items
Remove open items from an existing collective bill and create a new
collective bill for them
Remove open items from a collective bill and leave them in the respective
contract accounts
Removing open items from collective bills makes sense particularly if a customer
has complained about a collective bill item. By removing the item concerned, you
can check the content without delaying the processing of the remaining collective
bill items. You can therefore, for example, set locks for the removed items and
change the deferral date. This means that you can control processing in the
subsequent processes independently of the collective bill.
SAP recommends adding items if a contract account is integrated in a collective
bill account and you want to integrate the open items in this contract account into
the processing steps for the collective bill.
Activities
In the area Collective Bill Account on the initial screen, enter a collective bill or a
collective bill account, or, in the area Contract Account Level, enter a business
partner and/or a contract account. You can then use the following functions:
Include Items
29.
...
108.
1.
If you select this function, all open items of the business
partner/contract account are displayed on the subsequent screen. If you
have set the indicatorNew Collective Bill on the initial screen, the system
creates a new collective bill when you enter an item. Otherwise, the system
includes the selected item in an existing collective bill.
109.
2.
Select the required items and save your entries.
If a new collective bill is created, the system adds the collective bill number to the
document. If the item is included in an existing collective bill, the amount of the
item is added to the total amount of the collective bill.
Remove Items/
Split Items
30.
...
110.
1.
If you select this function, the collective bills for the business
partner/contract account are displayed in the tree structure on the left side
of the following screen. If you have specified the collective bill account as
selection criterion, all of the contract accounts belonging to this account,
and, in turn, all the open items belong to these contract accounts are
displayed in the tree structure. The open items of the collective bill account
selected are displayed in the upper right area of the screen. The lower part
of the screen contains the list of the items to be processed. If you select a
collective bill in the tree structure (double-click), the items belonging to this
collective bill are displayed on the top half of the screen.
111.
2.
To remove items from the collective bill, select them and
choose . You can remove any number of items from the collective bill in
this way.
112.
3.
Select the items removed and save your entries.
113.
4.
If you split a collective bill, the system updates the total amount of
the existing collective bill and subtracts the amount of the items removed.
The number of the existing collective bill is replaced by the number of the
new collective bill in the document removed. When you remove one or more
items from a collective bill, the number of the collective bill is removed from
the document and the total amount of the collective bill is reduced
accordingly.
When you delete a collective bill account in the master data of the contract
account, you can remove the open items from the collective bill. These items are
then only assigned to the individual contract account.
If you want to lock individual items of a collective bill, you can include these items
in a new, separate collective bill and lock this bill.
For installations where collective bills are not used, you can deactivate the
functions of the transaction Process Collective Bill. To do this, in Customizing for
event 6100, define a corresponding installation-specific function module
(see Program Enhancements Define Customer-Specific Function Modules).
When you change a collective bill, you cannot change the master
data, such as the collective bill account, simultaneously.
Locks are not inherited when you remove or include open items.
Adjusting receivables
Features
Processing collective bills in the business transactions specified below:
Business Transaction
Procedure
Resetting clearing
Dunning
Security Deposits
Interest Calculation
Write-Off
Adjustment of
receivables
Installment Plan
Security Deposits
Purpose
You use this component to manage cash and non-cash security deposits, such
as savings accounts and payment guarantees, in your system.
Notes on Implementation
This component is optional. You need to implement it if you require your
business partners to make security deposits.
Integration
If you are using the Item Interest Calculation component, you can calculate
interest on cash security deposits.
Features
You can assign security deposits to contract accounts or to contracts. Once the
Valid for date defined in Customizing has been reached, you can then repay or
clear cash security deposits. You can return or cash in non-cash security
deposits. Once the Valid for date has elapsed, they are automatically returned
by a workflow.
Industry Component Utilities (IS-U)
You can create security deposits when you process a business partner move-in.
Cash security deposits are offset against receivables at the time of final
settlement when a business partner move-out is processed. For more
information, see the Move-In/Out component of the Utilities
Industry component. For IS-U, information on security deposits is provided in the
front office.
Industry Component Telecommunications (IS-T)
With this component, you can only assign security deposits at contract account
level.
For each security deposit, you can specify the type of service, the reference
object ID, and an additional reference object. These fields are optional and you
can use them for cash and non-cash security deposits. If you want to make the
specification of this data obligatory, you can request the content of these fields in
event 0820. You can change or delete the content of the fields later. For cash
security deposits, these details are saved in the relevant request document.
Industry Component Insurance (FS-CD)
The system does not support the Security Deposits component.
statuses (see the Implementation Guide for Contract Accounts Receivable and
Payable Business Transactions Securities).
Integration
If the status of a non-cash security deposit is changed, a BOR event is initiated which can
trigger a workflow.
For non-cash securities you have to define the categories. You can also create additional
statuses (see Implementation Guide for Contract Accounts Receivable and Payable,
Business Transactions Security Deposits).
Process Flow
Cash security deposits
33.
...
121.
1.
The cash security deposit is created either manually or
automatically in the Utilities industry component when a move-in is entered
in the system. The cash security deposit has the status Requested.
Using the function module FKK_EVENT_0820_PAYMFORM_DET, you can
create a payment form number automatically when you create a cash
security deposit request.
122.
2.
As long as the request document has not yet been cleared, you
can reverse the security deposit. A deposit that has been reversed cannot
be used again.
123.
3.
If you receive a (partial) cash security deposit payment and this
clears the request document either completely or partially, the status
changes to (Partially) Paid.
124.
4. When the return date is reached, or when an early manual release
occurs, the system changes the status to Released.
125.
5.
If the cash security deposit payment is cleared by repayment or
settlement against open receivables, the end status Returned is reached.
In the menu under Periodic Processing For Contract Accounts Security
Deposits Release, you can use the report RFKK_SECURITY_RELEASE to release
the securities.
Non-cash security deposits
34.
...
126.
1.
Non-cash security deposits are created manually. When you save
the security deposit, the status Requested is given.
Further processing is triggered by changing the status. For non-cash
deposits, you can define the status in Customizing. For each change of
status, a BOR event is triggered; this can start a workflow, whereby you
have to model your own workflows.
127.
2.
You can display an overview of all security deposits. To do this,
choose one of the following paths:
Roles
Cash Security Deposits/Security
Deposits (SAP_FI_CA_CASH_DEPOSIT) Security Deposit
Statistics Report
SAP Menu
Periodic Processing For Contract Accounts Security
Deposits Statistics
You can select according to the following criteria:
Start date
Return date
Features
This function has the same features as the posting debit and credit interest
function (see Manually Posting Debit and Credit Interest).
Activities
To calculate interest on individual cash security deposit payments, choose one of
the following paths:
Role
Interest Calculation on Cash Security
Deposits (SAP_FI_CA_CSH_DEP_INTEREST_CAL) Calculate and
Post Interest on Cash Security Deposits.
SAP Menu
Account Security Deposit Interest Calculation
The procedure is similar to posting debit and credit interest.
Alternatively you can also make an interest calculation on cash security deposits
in a mass run.
35.
...
128.
1.
To do this, choose one of the following paths:
Role
Calculation of Interest on Cash Security
Deposits (SAP_FI_CA_CSH_DEP_INTEREST_CAL) Cash
Security Deposit Interest Run.
SAP Menu
Periodic Processing Security Deposits Calculation of Interest on
Cash Security Deposits
129.
2.
Enter a date and an ID that you can use to identify the run later.
130.
3.
Restrict the cash security deposits on which interest is to be
calculated using general criteria on the tab page General Selections, or
select them according to required posting parameters.
131.
4.
On the tab page Interest Parameters, enter the period for the
interest calculation. If you set the indicator Create Correspondence, you can
create interest notifications.
132.
5.
Schedule the program run. You can also carry out a simulation
run. For more information about scheduling program runs, see Functions
for Scheduling Program Runs.
You can display cash security deposit interest that has been posted in the
security deposit maintenance.
In the menu under Environment Interest Calculation List, you can display an
overview for the interest run.
Role
Cash Security Deposits/ Security
Deposits/ (SAP_FI_CA_CASH_DEPOSIT) Create Security Deposit
SAP menu
Account Security Deposits Enter
The Create Security Deposit: Initial Screen appears.
134.
2.
Make entries in the fields as follows:
5.
a.
Enter the contract account and a contract as
required.
6.
b.
Select the field for cash or non-cash security
deposits.
7.
c.
Enter the request reason and amount, a currency
and the start date.
8.
d.
Relevant for the telecommunications industry: Enter
the type of service, reference object ID and the additional reference
object here if required.
9.
e.
You must also specify the type and guarantor for
non-cash deposits.
135.
3.
Save your entries.
Result
The system displays the number of the new security deposit created. The request amount
is posted simultaneously for cash security deposits.
You can use the account category in the contract account to determine additional data
when posting cash security deposits. Define account categories in Customizing
for Contract Accounts Receivable and Payable under Basic Functions Contract
Accounts Define Account Categories and then record these under Business
Transactions Security Deposits Create Special Definitions for Security Deposits.
Roles
SAP Menu
Account Security Deposit Display/Change
2. Enter the number of the security deposit required and select Continue.
The following table lists the functions available when changing or
displaying a security deposit.
Functions with
Display and
Change
Menu Path
Explanation
Print
correspondence
Environment Form
Printing
Edit Reverse
Release cash
deposit
Edit Release
Release cash
security deposit in
part
Edit Release
Partially
Change amount of
cash security
deposit request
Edit Clear
Remaining
Receivable
or
Edit New
Receivable
Post new
receivable
Edit New
Receivable
New Status
Action
Requested
Reversed
Paid
Released
Partially paid
Released
A new cash security deposit is created and existing deposits are released immediately
when you save the change to the contract account. As standard, the function module
FKK_EVENT_1025_DEPOSIT_CHANGE creates a cash security deposit in the amount
of 100 units of the national currency using the first cash security deposit reason found in
the list.
Activities
If you want to automatically release and create cash security deposits when the payment
method in the contract account changes, define an installation-specific function module
for event 1025 in the Implementation Guide for Contract Accounts Receivable and
Payable under Program Enhancements Define Customer-Specific Function Modules.
To do this, copy the function module FKK_EVENT_1025_DEPOSIT_CHANGE and
adjust the copy to meet your requirements, for example, the amount of the cash security
deposit requested, the currency, the request reason, and the reversal reason.
Example
If a direct payer changes his payment method to bank collection, all of the cash security
deposits in the contract account of the business partner are released automatically, since
there is no longer any reason to retain the security deposit.
However, if a business partner who has previously paid his receivables by bank collection
becomes a direct payer, you can automatically request a cash security deposit.
Payments
Purpose
You use this component to create and process outgoing and incoming payments.
Features
The following detail components have been implemented:
You can manually enter data contained in incoming checks in a check lot.
Check lots are special payment lots that contain only checks.
You can enter the data from credit card payments manually in the credit
card lots, or by using an interface.
You can enter data from incoming bank transfers in a payment lot
manually or automatically, or you can transfer the data from an electronic
account statement to a payment lot using an interface.
Payment lots contain both general data and line item data. General data includes
the status of the lot, the total of the payment amounts and default values for the
line items. The line item data comprises the following:
Payment data required for further processing (such as, the payment
amount and bank data)
Here you can enter the bank number and bank account number, or the BIC
and IBAN, which are commonly used in international payment transactions.
Selection criteria by which the payment is assigned to open items
If you enter a payment lot manually, you must enter the selection criteria in each
payment lot item. This can be, for example, a document number or a payment
form number. Where payment lots are created automatically, the selection
criteria are determined from the data in the account statement.
When processing the payment lot, the system uses the selection criteria to
determine the open items. Assignment of the payments to the open items is
governed by industry-specific rules. Clearing of the assigned items takes place
automatically.
Overpayments can be posted as payments on account; underpayments posted
as partial payments. The system posts clarification cases to separate clarification
accounts and you have to postprocess them manually. If you are unable to
assign payments received, you can initiate repayment within the payment lot
provided qualified bank data exists. The payment program then repays the
amounts.
Check lots can be used to create check deposit lists that you can send to your
bank as an accompanying document when depositing the checks.
Industry Component Utilities (IS-U)
You can post incoming and outgoing payments individually in the cash desk.
The lock documents created in a dunning run are removed when all items that
led to the lock have been cleared. For more information about locking/restarting a
utilities installation in the dunning run, see Industry Component
Utilities Contract Accounts Receivable and Payable Lock/Restart. For
information about the workflows for locking/restarting, see the Industry
Component Utilities Customer Service Lock/Restart Utilities Installation.
Industry Component Telecommunications (IS-T)
You can post incoming and outgoing payments individually in the cash desk.
If an overdue item that led to a service being deactivated in a dunning run is paid,
the information about clearing is forwarded to the billing system, which then
triggers the release/unlocking of the service (see IS-T Telecommunications
Services in RM-CA Release/Unlock Services (IS-T)).
The payment medium program creates the data media. The formats required for
this are supplied by SAP.
Modern payment procedures like bank direct debit, debit memo collection, bank
transfer, and check are also supported, as is payment using a payment card. You
enter payment procedures and the bank details to be used per business partner
either in the contract account master record or (in exceptional cases) in the open
item itself. If required, open items can be paid by an alternative business partner.
By setting minimum amount limits, you can prevent very small amounts from
being paid. You can also block accounts or open items from being paid and enter
a temporary processing block in contract accounts.
The system logs the processing steps you carry out.
Check Management
Use
You use check management to enter and process outgoing checks.
Features
You can use check management to carry out the following for checks:
Enter a check
Display a check
Find a check
Correct a check
Void a check
Delete a check
Replace a check
Register a check as cashed
Assign a check to a payment document
Activities
To work with Check Management, choose one of the following paths:
Roles
Check Management (SAP_FI_CA_CHECK_MANAGEMENT) Check
Management
SAP Menu
Check Escheatment
Contract Accounts Receivable and Payable supports the check escheatment
process for checks that were not cashed by the recipient within a certain 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.
Prerequisites
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 .
Make additional system settings for check escheatment in Customizing under
Contract Accounts Receivable and Payable Basic Functions Check
Management in the activities Enter Receiver Codes for Check
Escheatment and Enter Specifications for Check Escheatment.
Process
In the standard system, escheatment is handled automatically. However, at event
0431, you can intervene in the process flow and identify checks that you want to
process manually in Clarification Processing. You can, for example, define event
0431 so that the system transfers checks to manual processing based on their
amount and/or the address of the check recipient.
Automatic check escheatment has the following steps:
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. The system stores
this date in the check.
At event 0430, you can change the receiver code and specify one of the
following for the check:
Escheatment
Outgoing payment
The payment program automatically creates a payment advice for the
recipient (the U.S. state).
The escheatment process was not yet started for them. (The check does
not contain an escheatment date.)
4.
In the Options group box, specify if you want to simulate the escheatment
and if you want to create correspondence.
5. Run the program.
Escheating Checks
During check escheatment, the system voids the checks and sets the voiding
reason and the escheatment date.
Features
Escheatment is controlled by the Customizing settings made for the receiver
code.
During escheatment, you select all checks from automatic processing that the
business partner has not cashed and for which the escheatment date for a
receiver code has been reached. The system calculates the escheatment date
based on the date the check was issued.
The system derives the specifications for document creation from the
Customizing activity Enter Specifications for Check Escheatment. You can create
postings for the voided checks either as individual or collective documents.
Using the settings in the Customizing activity Enter Receiver Codes for Check
Escheatment, the system creates either G/L transfer postings or business partner
postings, depending on how you manage the recipients of escheated checks in
your system.
Activities
1. On the SAP Easy Access screen, choose Periodic Processing Data
for Externals Tax Authorities Escheatment Execute Escheatment .
2. Enter the selection criteria that you want to use to select the checks.
Also enter a reconciliation key, a posting date, and a document date for the
posting.
By setting the appropriate indicator, you can simulate the escheatment
before you execute an update run.
3. Run the program.
You defined event 0431 so that certain checks are selected for manual
processing.
In check management (on the SAP Easy Access screen under Payments)
you set process category 2 (Manual) for the display of the check and its
escheatment data.
In this case, the check must also already be in the check escheatment
process.
You are in the check clarification process (on the SAP Easy Access
screen, under Payments Clarification Activities Cashed Checks ).
Features
In clarification processing, you can respond to the following reactions of the
recipient:
Search for the current address of the payee in the business partner data
Change the receiver code in accordance with the last known address of
the payee
Receipt Management
Use
In the transaction Receipt Management, you can display all receipts printed for a
payment document that meet selection criteria that you specify in an overview.
Prerequisites
If you want to use Receipt Management, make the following settings in the
Implementation Guide for Contract Accounts Receivable and Payable:
Each printed receipt receives a separate receipt number. You control the
assignment of these numbers using a separate number range. Maintain
number range 01 under Business Transactions Payments Processing
Incoming/Outgoing Payments Receipt Management Maintain Number
Ranges for Printing Receipts.
(not yet printed). If you subsequently want to print the receipt, the program
accesses these simulated lines. The receipt line is only simulated if you
have not selected the indicator Only Display Receipts as selection criterion. You
can use the following functions in the display:
If you also display the line items in the list, you can print the receipts for
the payment documents displayed by selecting the corresponding line and
choosing
Receipt.
Processing Credits
Use
If you want to clarify the use of credits in your business partners' contract accounts, you
can use the following functions:
Credit clarification
Processing credits
Using the Credit Clarification function, you can process the following credits:
Credits that were placed in the clarification worklist during posting based
on the settings defined in Customizing
SAP only recommends using the Processing Credits function for manual processing of
individual credits that were not entered by the credit list.
Integration
If the credit items are not included in the clarification worklist automatically during
posting as a result of the system settings for credit clarification, you have to run the mass
activity Create Credit List periodically. (See Creating Credit Lists).
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and Payable,
under Business Transactions Credit, you have defined the document types to be used
for posting credits.
Under Business Transactions Credit Define Selection Criteria for Credit
Clarification, you have defined the parameters that determine whether an item is placed
in the clarification worklist directly during posting or via the credit list. You determine
whether or not an item is placed in the clarification worklist directly during posting or via
the credit list by setting the indicator Immediately.
Implementation Considerations
See SAP Note 1032588.
Features
The following provides information on how you can protect your data by making
certain Customizing settings.
The existing options for saving encrypted payment card numbers
for selected applications, such as the encryption of payment card data
in the customer master record, remain in effect and are not affected
by the measures described here. These measures are available in
addition to existing ones.
Masked display means that when you display or change objects that contain a
payment card number, the system makes the number partially unrecognizable.
For example, only the value 1111********4444 is displayed instead of the card
number 1111222233334444. You can configure the number of visible characters
at the beginning and end of the payment card number. The security standards of
the credit card industry require that a maximum of six characters are visible at
the beginning, and four at the end.
For each card type (AMEX, MC, VISA), you can decide whether you require
encryption or not. In Customizing for Cross-Application
Components, choose Payment Cards Basic Settings Maintain Payment
Card Type. However, the column for this is only visible if the encryption of
payment cards is already active in the business partner data or if you configured
encrypted storage for other data records (see above).
You make general settings for using encryption software in Customizing for SAP
NetWeaver by choosing Application Server System Administration Maintain
the Public Key Information of the System.
Access log
You can retain a record of each display of an unmasked payment card
number in an access log. This enables you to follow which users have
displayed which payment card numbers and when.
Features
You can evaluate accesses to payment card data using report
RCCSEC_LOG_SHOW or transaction CCSEC_LOG_SHOW. To evaluate the
access log, a user requires authorization for activity 71 of authorization object
B_CCSEC.
Log records that are at least one year old can be deleted using report
RCCSEC_LOG_DEL or transaction CCSEC_LOG_DEL. To be able to run the
deletion report, the user needs authorization for object B_CCSEC with activity
06.
Migration
For all objects that until SAP NetWeaver 7.10 were unable to save encrypted
payment card numbers, the card numbers of all new objects created are
encrypted as soon as a corresponding security level is set. This means that your
data records then contain both payment card numbers that are not encrypted (old
records) and encrypted payment card numbers (new records). This does not
reflect a restriction of functionality; the application programs can work with this
mixed status. Migration programs are offered for selected applications. These
comply with the naming convention RCCSEC_MIGRATION_*.
You specified the payment card types that you want to save in encrypted
form in Customizing under Cross-Application Components Payment
Cards Basic Settings Maintain Payment Card Type .
Features
To further increase the security of encrypted payment card data in your system,
you can replace the keys on a periodic basis.
If you activate the business function PCA_KEYV (Periodic Key Replacement for
Payment Card Encryption), then the following functions are available to you in
addition to those described above:
Interest Calculation
Purpose
You use this component to determine and post interest receivables and
payables.
Features
The Interest Calculation component covers the subcomponents Item Interest
Calculation and Balance Interest Calculation.
Interest interval
The defined interest rate is a yearly, monthly, weekly, or daily interest rate.
Interest key
Definition
Key for determining the factors that influence interest calculation and posting. Interest
keys are assigned at item level.
Use
The system calculates interest only on those items for which it is able to determine an
interest key. You can assign contract accounts, items, or dunning levels to an interest key.
In the case of additional receivables, in the related subtransaction you can define whether
a special interest key is to be used.
The system normally determines the interest key for each industry, but can also do so on
a customer-by-customer basis. The interest key refers to an interest calculation rule that
the system uses to determine the valid interest rate in terms of date and amount. The
system determines some of the factors that influence interest calculation using the
calculation rule. The system determines the following influencing factors using the
interest key:
Influencing
factor
Description
Tolerance days
Transfer days
Transfer and
tolerance days
receivables if the amount of receivables exceeds the amount of the payables (see the
documentation for the function modules FKK_SAMPLE_2085,
FKK_CONDENSE_2085).
Structure
You define interest keys in Customizing (see the IMG structure Contract Accounts
Receivable and Payable Business Transactions Interest Calculation Item
Interest Calculation Define Interest Keys).
Integration
The interest key refers to a valid interest calculation rule for which other influencing
factors for the interest calculation are stored.
Interest Document
Definition
Document in Contract Accounts Receivable and Payable that arises as part of
interest posting.
Use
An interest document is generated when interest is posted. Posting interest is
integrated into some business transactions.
In addition to the usual document data, an interest document also contains
information about the basis of interest posting. This information is contained in
the interest schedule. The schedule shows the items for which interest was
calculated for which amounts at which interval. The interest key is retained in the
interest schedule. This allows you to find out which factors were valid for interest
calculation and posting.
If the system settings for the interest calculation rule or for the
interest rule are changed at a later time, you will no longer be able
to retrace interest calculation using the interest schedule.
Structure
An interest document includes the structures of a document in Contract Accounts
Receivable and Payable: document header, line items and general ledger (G/L)
You can charge interest on the installment plan over its whole life.
If individual installment payments are late, you can charge interest on the
overdue installments.
If installment payments are not made, you can also deactivate the
installment plan manually. This reopens the original open receivables for
the old due dates. You can reverse interest documents that are integrated
in an installment plan and that have been posted but not cleared when you
deactivate the installment plan (see Reversing Installment Plan Interest
Documents).
During the interest calculation the system updates an interest history for the installment
plan.
Installment Plan Interest versus Overdue Interest
The system indicates the interest documents posted when you create an installment plan
with a separate transaction. These interest documents are based on the period of the
installment plan and therefore valuate the period from the start date of the installment
plan or an alternative earlier start date up to and including the due date for net
payment of the installments (see graphic). Interest on overdue installments is charged
when the customer does not fulfill the payment agreement Installment Plan. You post this
additional interest document (requested subsequently) with the usual interest transaction.
Interest on overdue installments is based exclusively on the period from the due date of
the installments (see graphic).
Integration
Installment plan interest is integrated in the Creating an Installment Plan process flow
(see Deferral and Installment Plans).
Features
This function has the same features as the posting debit and credit interest
function (see Manually Posting Debit and Credit Interest).
Activities
To calculate interest on individual cash security deposit payments, choose one of
the following paths:
Role
Interest Calculation on Cash Security
Deposits (SAP_FI_CA_CSH_DEP_INTEREST_CAL) Calculate and
Post Interest on Cash Security Deposits.
SAP Menu
Account Security Deposit Interest Calculation
The procedure is similar to posting debit and credit interest.
Alternatively you can also make an interest calculation on cash security deposits
in a mass run.
39.
...
141.
1.
To do this, choose one of the following paths:
Role
Calculation of Interest on Cash Security
Deposits (SAP_FI_CA_CSH_DEP_INTEREST_CAL) Cash
Security Deposit Interest Run.
SAP Menu
Periodic Processing Security Deposits Calculation of Interest on
Cash Security Deposits
142.
2.
Enter a date and an ID that you can use to identify the run later.
143.
3.
Restrict the cash security deposits on which interest is to be
calculated using general criteria on the tab page General Selections, or
select them according to required posting parameters.
144.
4.
On the tab page Interest Parameters, enter the period for the
interest calculation. If you set the indicator Create Correspondence, you can
create interest notifications.
145.
5.
Schedule the program run. You can also carry out a simulation
run. For more information about scheduling program runs, see Functions
for Scheduling Program Runs.
You can display cash security deposit interest that has been posted in the
security deposit maintenance.
In the menu under Environment Interest Calculation List, you can display an
overview for the interest run.
Integration
The dunning run only processes open items. Interest is therefore always
calculated using the Open Items Only option. This also applies to interest
calculation as part of invoicing in the IS-U application.
Features
For item interest calculation, you can use the open items only or cleared items
only options. To use these options, set the relevant indicator on the initial screen
when posting interest online. To do this, choose one of the following paths:
Roles
Process Outstanding
Payments (SAP_FI_CA_OUTSTANDING_PAYMENTS) Post
Interest
SAP Menu
Account Interest Post
Set the relevant indicator in the interest parameters when you schedule the
interest run.
By choosing the Open Items Only option, you can avoid overdue interest charges
for debit items that have already been cleared at the time of interest calculation.
This variant is particularly useful if interest is calculated on a regular basis, for
example, in a monthly dunning run.
Items that have been split by a partial payment are treated as follows:
By choosing the Cleared Items Only option, you can define that overdue interest
charges are only calculated once an item has been cleared completely. This
ensures that one source item creates only one interest item posting and one
interest notification.
Items that have been split by a partial payment are treated as follows:
The system also checks whether the clearing date for all subitems is
earlier than the Calculate Interest To date
Subitem
Amount
Due date
Clearing
4711
0001
50 EUR
01/01
-(item open)
4711
0002
50 EUR
01/01
01/10
You have defined and assigned the required application forms (see
Implementation Guide for Contract Accounts Receivable and Payable Basic
Functions Print Workbench Define Application Forms).
Procedure
40.
...
Request the printout of an interest notification as part of manual interest
calculation (see Editing Items Due for Interest).
You post the interest if you have not done so already.
The system determines the data relevant for correspondence (such as business
partner or contract account) and stores it in the correspondence container (see
also Event-Driven Correspondence Creation).
Enter and schedule a correspondence printing run (see Printing
Correspondence).
41.
When you execute a correspondence printing run, the selected
correspondence data is read from the correspondence container,
supplemented with other data where necessary, and output in the printer
spooler.
Result
The correspondence data is available in the printer spooler either in raw data
or SAPscript format. You can display the job log for the correspondence print
run (see Displaying Logs for Correspondence Print Runs).
Cash Desk
Cash Journal
Account Maintenance
Automatic Clearing
You calculate arrears interest, carry out an interest run, and post an interest
document in the amount of UNI 2. On receipt of the payment for UNI 100,
depending on the item selection and the configuration of the clearing control, the
system clears either the open receivable for UNI 100 or the interest document
posted and a partial amount of UNI 98. In the first case, the interest receivable
for UNI 2 remains open in the contract account of the business partner. If you
have not calculated interest before receiving the payment, you can calculate
interest on the item when you clear the receivable and calculate an interest item
of UNI 2. In this case the interest item remains open.
Arrears surcharges add business value because, in contrast to interest on
arrears, you can calculate and withhold arrears surcharges when you clear the
overdue receivable. The system automatically posts the arrears surcharge as a
general ledger item (revenue) in the clearing document. There is no separate
charges document. If the arrears surcharge calculated in event 0104 has the
same amount as the corresponding interest document, in our example, UNI 2,
the system would split the payment for UNI 100 proportionately as follows:
For the receivable of UNI 100, the system posts a partial clearing for UNI 98.04
and revenue from surcharges of UNI 1.96. UNI 1.96 of the receivable remains
open, and you can levy higher interest/charges for the next payment, since this
partial amount of the receivable is cleared later. To clear all receivables
completely (overdue receivable + arrears surcharge), the business partner would
have to pay UNI 102.
If the business partner pays, for example, UNI 51, UNI 50 of the original
receivable remains open.
The grace period that postpones the due date by a certain number of days
The principle that the dunning interest calculation should begin on the first
working day after the due date
Prerequisites
If you want to use this function, you must define function
module FMCA_SAMPLE_2090 as a customer-specific function module with event 2090
in the Customizing of Contract Accounts Receivable and Payable in IMG activity Define
Customer-Specific Function Modules. If FMCA_SAMPLE_2090 does not cover your
requirements, copy the function module and define this copy as a customer-specific
function module with event 2090.
Dunning
Purpose
With the component Dunning, you can create and send payment reminders or
dunning letters to your business partners to remind them of overdue payables
and to request payment.
You can print correspondence using the component Correspondence or using
the application forms of the Print Workbench that you have defined.
In addition to the features of the standard delivery, you can realize industryspecific dunning activities.
Industry Component Utilities (IS-U)
You can dun budget billing requests as well as open items. The
dunning run can create lock documents automatically. For more
information about lock documents, see the documentation of the
industry component Utilities under Contract Accounts Receivable and
Payable Locking/Restarting a Utilities Installation and
under Customer Service Locking/Restarting a Utilities Installation.
You can postprocess the dunning-relevant data manually in the
dunning proposal.
Industry component Telecommunications (IS-T)
Notes on reversal of dunning runs or dunning notices are not in force for
Collections/Disbursements.
The dunning levels and dunning procedures to be applied are not stored
in the item in Collections/Disbursements, but in the dunning history.
In the insurance dunning history, you can set a new dunning level for
each dunning group, not for individual items. Therefore, you cannot use this
new dunning level as a grouping criterion.
For dunning runs, the system only takes the defined amount limit for the
current dunning level into account in the dunning proposal run. All items
relevant for the dunning balance are added to this and compared with the
amount limit for the dunning level in force. If the dunning group does not
reach the amount limit, the entire group is removed from dunning. The
system automatically assigns the reconciliation key used, and this cannot
be changed.
When generating hard copy, special form classes are available for
Collections/Disbursements. The forms contain no payment forms.
42.
146.
147.
148.
149.
150.
...
1.
An open item is due for dunning if the due date for net payment,
added to the days in arrears defined in the Implementation Guide, lies
before the date of issue for the dunning run, and if no dunning lock is
entered in the master data (contract account or insurance object).
2.
To determine the dunning level for an item due for dunning,
the dunning proposal run evaluates the settings in the master data, the
Implementation Guide and the insurance dunning history, and
forms dunning groups from the items read.
3.
The dunning proposal run delivers a dunning proposal for
the dunning activity run. The dunning activity run executes the activities
for an insurance policy that is suitable for dunning, and calculates charges
and interest.
4.
If the policyholder does not react to a dunning notice, the item due
for dunning is taken from the dunning proposal run and moves to the next
dunning level, after the days between two dunning levels have expired (or
after the days in arrears defined in the next dunning level have been
exceeded), as defined in the dunning frequency.
5.
A dunning procedure is ended if one of the following situations
occurs:
Role
Process Contract Account Master Data Create Contract
Account/Change Contract Account or Manual Postings Post
Document/Change Document
SAP Menu
Master Data Contract Account Create/Change or
Document Post/Change
In certain business transactions, the system can also enter dunning
parameters in the contract account and/or document automatically. This
enables you, for example, to default the dunning procedure when you are
creating contract accounts. Using the BAPI
BAPI_CTRACCONTRACTACCOUNT_CREA, you can determine dunning
locks.
For the industry components Public Sector Contract Accounts
Receivable and Payable and Utilities, in the Implementation Guide
for Contract Accounts Receivable and Payable, you can define default
values for dunning procedures and dunning locks that the system then
enters in the document automatically during posting (see Basic
Functions Postings and Documents Document Maintain Document
Dunning Runs
Purpose
Once you have configured the dunning parameters described, the system can identify
overdue receivables in the system and dun your business partners.
Prerequisites
To prevent you from dunning receivables that have already been paid, you should keep
your postings as up-to-date as possible. This means that you should ensure that all
payments received have been posted in the system and cleared with the receivables due
(for example, using the automatic clearing program in the SAP menu under Periodic
Processing For Contract Accounts Automatic Clearing).
Process Flow
In Contract Accounts Receivable and Payable, you dun receivables in a dunning run.
Carrying out a dunning run involves two steps:
44.
155.
...
1.
Dunning proposal run (SAP menu: Periodic Processing For
Contract Accounts Dunning Dunning Proposal Run)
156.
2.
Dunning activity run (SAP menu: Periodic Processing For
Contract Accounts Dunning Dunning Activity Run)
In the first step, the dunning proposal run determines
The contract accounts to be dunned, together with the items due for
dunning
The valid dunning procedure and the related dunning levels for the
individual items
required depending on the dunning level of the items due for dunning and then carries
these activities out. You can specify the frequency in which you want to carry out
dunning runs. Dunning proposal runs and dunning activity runs can be executed more
than once simultaneously and therefore enable you to process large quantities of data.
The dunning proposal run proposes a reconciliation key for the documents posted during
dunning. You can change this proposal manually. The dunning activity run only uses this
reconciliation key if the run ID agrees with that of the dunning proposal run.
The requirements of the different industries may be very varied, and so Contract
Accounts Receivable and Payable offers numerous events with which applicationspecific and customer-specific requirements can be fulfilled.
Dunning Runs
Result
In a dunning run, you have created, for example, printed records, clerk notes, charges
postings, and interest postings. The system has updated the dunning history and the
dunning activity history.
Features
Depending on the dunning activity, you can create documents for a dunning
notice in two ways:
2.
...
You print using the Print Workbench. There, certain form classes, such as form
class IS_U_CA_DUNNING, provide data in the structure PAYMO Attached
Payment Media Output. You can print this data on the attached payment
form. The application form itself can also trigger a special printout via CALL
FUNCTION OPEN_FORM.
Using a Collection, you can print the application form and the payment form
attached together (see also the documentation for the Print Workbench).
For detailed information about creating payment forms, see Payment Forms.
Activities
45.
...
157.
1.
Configure the required application forms in the Implementation
Guide for Contract Accounts Receivable and Payable Basic
Functions Print Workbench Define Application Forms). For detailed
information, see Processing Application Forms in the documentation for
the Print Workbench.
158.
2.
Assign the application form to the required dunning activity in the
IMG activity Configure Dunning Activities (Business
Transactions Dunning Notices).
159.
3.
Define the dunning activities in the individual dunning levels of the
dunning procedure (see Business Transactions Dunning
Notices Configure Dunning Procedures).
If you set the indicator Print All Items in the Customizing for the dunning level
(screen area History and Dunning Printing), you can include items that are due in
the future info items in the printout. The info items are not displayed in the
dunning history. To print the total of all items selected, you have to create the
total in your dunning form in the Exit-During-Loop of level OPEN_ITEM, print it,
and then reset it in the Exit-After-Loop.
correspondence type 0003, the selected dunning activity creates an entry in the
correspondence container, and the print program archives the paper records, you can also
store the dunning letters under the dunning key in the archive. If you specify key fields
from the dunning header in the Business Document Navigator, you can also find dunning
notices, for example, under the class name CA_DUNNINGand class type BO. Note that
you cannot change the archiving object in Customizing in the meantime.
Dunning by Telephone
Use
You want to contact dunned business partners by telephone.
Features
If you define the function module FKK_SAMPLE_0350_TEL_ITEM as dunning
activity in Customizing, the dunning activity run automatically includes business
partners that receive a dunning notice in a telephone list. You can then use this
list to contact the business partners concerned by telephone.
To process the telephone list, you can use the transaction Dunning Notices
Telephone List in the SAP menu under Periodic Processing For Contract
Accounts Dunning. Several clerks can use this transaction simultaneously. If
the call to the dunned business partner has been made, the clerk responsible
can set the entry in the list to Completed. To give a business partner
information during the telephone call, you can use the detailed information for an
entry in the telephone list, for example, to access the account balance, to access
the objects linked to the dunning notice, and to access another function that you
call up installation-specific in event 9011.
To document the communication with the business partner in the system, the
clerk can also create customer contacts manually or automatically depending
on how the system is configured. If a clerk has removed an entry from the list for
processing, this entry is locked for processing for other clerks. Once processing
is complete, the clerk can set an entry to Completed again, or place it back in
the list.
When you reverse a dunning notice or a dunning run, the system can
automatically delete entries in the telephone list. To do this, use function module
FKK_SAMPLE_0395_TEL_ITEM in event 0395. The entry is deleted regardless
of its status at this point.
Using correspondence type 3003, you can use the correspondence recipient
control to enter an alternative business partner in the telephone list.
Authorizations
The activities in the telephone list are protected by the authorization object
F_KKDUTL.
Connection to mySAP CRM
If you do not process the list created by the dunning activity run in Contract
Accounts Receivable and Payable with the transaction Dunning Notices
Telephone List, but want to forward it to an external system, for example, the call
center in mySAP CRM, you have to implement events 9010, 9012, and 9013.
You can forward the list as follows:
For each business partner, the dunning history shows the name and address as
standard. With a customer-specific module defined in event 4700, you can
change this text to meet your requirements.
You can display additional data fields by enhancing the customer includes of
structure FKKMAKO_PLUS for the dunning header and structure
FKKMAZE_STRUC for the dunning items. Then fill your additional fields using a
customer module for event 0391 for the dunning header or 0392 for the dunning
items.
Troubleshooting
The following information will help you analyze problems that occur in dunning
runs:
Notes for Error Analysis and Correction
Problem
Cause/Solution
The amount limit has not been reached for the next
dunning level, which was determined for the
dunning group.
If the dunning balance for the dunning group is less
than the amount limit defined in the Implementation
Guide, the dunning group is excluded from
dunning.
The days in arrears, or the dunning frequency for
the next dunning level, have not been reached.
Comparison takes place based on the date of
issue for the dunning proposal run.
The Print All Items flag is set and the item is only
an info item and therefore is not to be dunned.
You have manually set the old dunning level as
new dunning level.
Creditworthiness
Use
The creditworthiness of a business partner provides information on the business
partners payment history and influences the selection of activities for dunning
and/or returns and also the calculation of charges. Various different business
transactions, such as returns, dunning notices, installment plans, and write-offs
update the creditworthiness in the system automatically. You can also transfer a
creditworthiness record from external systems or manually.
The current status of a business partners creditworthiness is determined as a
weighted total on the basis of the creditworthiness figures recorded over the last
48 months. You define the monthly weightings in Customizing. A
creditworthiness of zero means that the business partner has an excellent
payment history. The maximum value is 9999.
The level of creditworthiness depends on:
Initialization in Customizing
Manual creditworthiness
In the Define Deactivation Reasons for Installment Plan activity, for each
deactivation reason, define whether a creditworthiness entry updated on
creation of the installment plan is to be reversed when the installment plan
is deactivated.
Features
The system automatically determines the creditworthiness of a business partner
in returns processing and in a dunning run. The creditworthiness influences the
activities and the charges levied, provided that you have defined the activities
and charges dependent on creditworthiness in Customizing.
There is a display and change function for creditworthiness. The features are as
follows:
You can release this fixed value manually, so that the creditworthiness
can change for time-dependent reasons.
Function
Business Partner Account
Information(SAP_FI_CA_PARTNER_ACCOUNT_INFO) Display
Business Partner Creditworthiness or Change Business Partner
Creditworthiness.
SAP Menu
Collections Management
Purpose
The Collections Management component supports you in drawing your
customers' attention to overdue payables and requesting payment.
You can print correspondence using the Correspondence component or using
the application forms of the Print Workbench that you have defined.
Integration
Work items created in Contract Accounts Receivable and Payable are processed
exclusively by collection specialists in Customer Relationship
Management(CRM) in Financial Customer Care.
Dunning Runs
Purpose
Once you have configured the dunning parameters described, the system can
identify overdue receivables in the system and dun your business partners.
Prerequisites
To prevent you from dunning receivables that have already been paid, you
should keep your postings as up-to-date as possible. This means that you should
ensure that all payments received have been posted in the system and cleared
with the receivables due (for example, using the automatic clearing program in
the SAP menu under Periodic Processing For Contract Accounts Automatic
Clearing).
Process Flow
In Contract Accounts Receivable and Payable, you dun receivables in a dunning
run. Carrying out a dunning run involves two steps:
47.
...
163.
1.
Dunning proposal run (SAP menu: Periodic Processing For
Contract Accounts Dunning Dunning Proposal Run)
164.
2.
Dunning activity run (SAP menu: Periodic Processing For
Contract Accounts Dunning Dunning Activity Run)
In the first step, the dunning proposal run determines
The contract accounts to be dunned, together with the items due for
dunning
The result of the dunning proposal is processed further in the dunning activity
run. In the second step, the dunning activity run first determines the dunning
activities required depending on the collection step and then carries these
activities out. You can specify the frequency in which you want to carry out
dunning runs. Dunning proposal runs and dunning activity runs can be executed
more than once simultaneously and therefore enable you to process large
quantities of data.
The dunning proposal run proposes a reconciliation key for the documents
posted during dunning. You can change this proposal manually. The dunning
activity run only uses this reconciliation key if the run ID agrees with that of the
dunning proposal run.
The requirements of the different industries may be very varied, and so Contract
Accounts Receivable and Payable offers numerous events with which
application-specific and customer-specific requirements can be fulfilled.
Result
In a dunning run, you have created, for example, printed records, clerk notes,
charges postings, and interest postings. The system has updated the dunning
history.
Features
Depending on the dunning activity, you can create documents for a dunning
notice in two ways:
166.
167.
2.
Enter a date and an ID that you can use to identify the run later.
3.
On the General Selections tab page, specify the ID of the dunning
proposal run that you want to reverse.
168.
4.
Execute the run.
For more information about scheduling the run, see Functions for Scheduling
Program Runs.
Initialization in Customizing
Manual creditworthiness
depending on this creditworthiness, the system selects the returns activity where
the creditworthiness value determined is greater or the same as the value
defined in Customizing.
In Customizing, you can define a creditworthiness weighting in the returns
reasons. Once returns processing has taken place, the creditworthiness figure of
the current month is increased by this figure.
You can define the creditworthiness weighting with the returns reason in
Customizing (see IMG for Contract Accounts Receivable and
Payable Business Transactions Returns Configure Returns Reasons).
Write-Offs
Write-offs can also have a negative effect on a customer's creditworthiness. If
you want to use creditworthiness determination, enter the write-offs in
conjunction with a creditworthiness figure.
You can define the creditworthiness weighting with the write-off reasons in
Customizing (see IMG for Contract Accounts Receivable and
Payable Business Transactions Write-Offs Configure Write-Off Reasons).
Features
The system automatically determines the creditworthiness of a business partner
in returns processing and in a dunning run. The creditworthiness influences the
activities and the charges levied, provided that you have defined the activities
and charges dependent on creditworthiness in Customizing.
There is a display and change function for creditworthiness. The features are as
follows:
You can enter or change the creditworthiness manually. The system adds
the manual creditworthiness to the value of the creditworthiness determined
automatically. The result is the total creditworthiness of a customer.
You can release this fixed value manually, so that the creditworthiness
can change for time-dependent reasons.
If a collections specialist enters a new contact person for a collection work item in
the Interaction Center WebClient, you can adopt the data in the business partner
master data in Contract Accounts Receivable and Payable. When a collection
specialist enters a contact person in the Interaction Center WebClient,
CRM updates a corresponding trigger in Contract Accounts Receivable and
Payable. You must process these triggers regularly in Contract Accounts
Receivable and Payable using the Update Contact Persons transaction from the
SAP Easy Access screen under Master Data Business Partners Data for
Collections Management.
Features
The dunning activity run, in the context of a collection strategy or a dunning
procedure, executes the dunning activities defined in Customizing. The
dunning activity controls which measures are performed when a collection step
or a dunning level is reached. If the measure is creating a collection work item,
then configure the corresponding dunning activities with the function module
FKK_0350_WLI_CREATE_AND_CLOSE. The module:
From the SAP Easy Access screen under Periodic Processing For
Contract Accounts Dunning Manage Worklists
Activities
169.
1.
Configure dunning activities for creating collection work items in
Customizing for Contract Accounts Receivable and Payable under Business
Transactions Dunning.
170.
2.
If you dun using dunning procedures, assign dunning activities to
dunning levels in Customizing for Contract Accounts Receivable and
Payable underBusiness Transactions Dunning Dunning by Dunning
Procedure Configure Dunning Procedure.
If you dun by collection strategy, assign dunning activities to collection steps
in Customizing for Contract Accounts Receivable and Payable
underBusiness Transaction Dunning Dunning by Collection
Strategy Define Collection Step.
171.
3.
Define work item categories in Customizing for Contract Accounts
Receivable and Payable under Business
Transactions Dunning Worklists and Work Items Define Work Item
Categories.
Using the processing type in the configuration of the work item categories,
you can specify if work items are to be processed by a specialist or by an
automatic dialer.
Either the dunning activity run or the manager assigns dialer work items to a
dialer worklist. If a manager releases a dialer worklist, the system sends all
dialer work items that it contains to an external system (power dialer) by
means of a notification message (XI). This external system assigns a
specialist, who contacts the customer, to each dialer work item. The
external system makes the phone call to the business partner. In event
1049, you convert the connection status to the business partner, which was
determined using the XI interface, into the substatus of a work item. In the
ERP system, the substatus then shows the status of work item at the dialer
(such as, business partner not reached, line busy, business partner
currently being called).
Using the creation mode, you specify if the dunning activity run
automatically groups the work items into a worklist, adds the work items
automatically to a standing worklist, or if the work items are grouped
manually in a worklist. Once a dunning activity run has created a standing
worklist, the system automatically adds new work items to the standing
worklist. This type of worklist always remains open, it is never ended by the
system.
If you set the Own Worklist indicator, the dunning activity run groups the
collection items of this category in their own worklist.
Using the processing deadline, you specify if the work items have to be
processed before the next time the dunning activity run is executed. If
theMandatory indicator is set for a work item category, and a work item of
this category is still open the next time the dunning activity run is executed,
the work item is excepted from further dunning. If the indicator is not set, the
dunning activity run closes the work item and creates a new collection work
item.
If you set the Enforcement WI indicator, the dunning run automatically
assigns the generated work items to an item list. The dunning activity run
always assigns collection work items of this category to a separate worklist.
172.
4.
Assign dunning activities to the work item categories in
Customizing for Contract Accounts Receivable and Payable under Business
Transactions Dunning Worklists and Work Items Assign Work Item
Categories to Dunning Activities.
173.
5.
On the SAP Easy Access screen, under Periodic
Processing For Contract Accounts Dunning, maintain the
responsibilities for your collections departments, collections units and
collection specialists.
Activities
178.
1.
To process worklists, from the SAP Easy Access screen
choose Periodic Processing For Contract
Accounts Dunning Manage Worklists.
179.
2.
On the following tab pages you can get an overview of all worklists
and how complete their processing is:
The New Work Items tab page shows the manager all departments
assigned to him, and the number of work items that are assigned to
his departments and units, but are not assigned to a worklist.
The Current Worklists tab page shows all worklists that are
assigned to the departments/units of the manager and which contain
at least one not completed work item.
The Completed Worklists tab page shows all worklists that are
assigned to the departments/units of the manager and which contain
only completed work items.
The Current Distrib. tab page shows the distribution of work items to the
individual organizational units (department, unit, specialist).
The system considers completed work items in the distribution only if they
were finished on the same day the transaction is called.
180.
3.
Below each tab page there are pushbuttons you can use to:
Create Worklist
Find Worklist
NOTE
If you host the application in a central Data Center and end users have access
using WAN, this has a negative effect on performance. In this case, Accelerated
Application Delivery for SAP NetWeaver offers a solution. For more information,
see the SAP Service Marketplace
athttps://service.sap.com/installnwaccad.
Activities
Call transaction WUI and then proceed as follows:
To get an overview of the assignment of collection work items to
specialists and organizational units:
In the navigation bar, choose Collection Work Items Assignment.
In the work area, you can get an overview of all work items and how complete
their processing is, related to the organizational unit. In detail, you receive
information about:
What the total amount is for the work items assigned to an organizational
unit
How many work items were closed in the course of the day, and what the
total amount of these work items is
To create worklists:
1. In the navigation bar, choose Create Worklist.
2. Enter an ID, a processing type for the work items of the worklist, and a
department that is responsible for processing the worklist.
By entering a description and a text, you can also describe the worklist
more precisely to enable you to identify it more easily later.
By entering an execution date, you specify the latest end date for a work
item of the worklist. You can overwrite this date with a later date. As an
attribute of the worklist, the date serves informational purposes only.
If you enter a valuation rule, you can prioritize the work items of the worklist;
the work items then receive a certain ranking depending on how important
they are.
In the field Maximum Number Uncompleted Work Items, you can enter the
maximum number of work items a specialist is allowed to have in
processing.
In the field Number of Work Items per Assignment, you can specify the
number of work items that a specialist receives through automatic
assignment.
3. Choose Add Work Items.
4. In the dialog that appears, select the work items you want by entering
appropriate selection criteria.
To add work items to the work list, choose the Choose pushbutton.
By choosing
Remove Work Items (Remove Work Items), you can
remove the selection again. If you have already saved the assignment, this
function is no longer available. To remove work items in that case, you have
to assign them to another list.
5. Save the worklist and if you choose, release it. To do so, choose
Save (Save) or
Save and Release (Save and Release).
You have to release the worklist in order for specialists to be able to assign
themselves the work items. If you assign work items to your worklist that are
already released, the system releases the worklist immediately when you
save.
6. If you want to change the header data of the worklist afterward, choose
Edit (Edit).
To search for collection work items:
1. In the navigation bar, choose Find Work Items.
2. Enter your selection criteria and choose Find.
In the work area, you can select individual work items and process them.
To search for worklists:
1. In the navigation bar, choose Find Worklist.
2. Enter your selection criteria and choose Find.
In the work area, you can now select a worklist and close and remove work
items.
If you regularly use the same search criteria, you can save these under an ID.
Enter the ID in the Save Search As field, and choose . You can then enter this
ID in the Central Search area in the Saved Searches field, and use it by choosing
the Start pushbutton. Using the
pushbutton, you can delete existing
selections.
More Information
For information about the UI Framework, see the SAP Help Portal under
Business Suite SAP Customer Relationship Management Customer
Relationship Management WebClient UI Framework .
SAP
Collection History
Definition
Analysis tool that brings business transactions in Collections Management into a
total view with reference to the business partners affected.
Use
You call the collection history in the SAP menu under Account More
Information.
To display the collection history, you can choose between a tabular and a
hierarchical view of the events.
Structure
In the collection history, business transactions are viewed as events that are
subdivided using event categories. SAP delivers events of the following category:
Dunning
Correspondence
Work item
Payment
Promise to pay
Installment plan
The system assigns a work item to a specific dunning notice if the work
item has arisen from a dunning activity for this dunning notice.
Explicitly enter the new collection strategy that you want to replace the
collection strategy entered in the master data
Enter a test series that the program run uses to replace the collection
strategy
Activities
From the SAP Easy Access screen, under Periodic Processing For Contract
Accounts Dunning By Collection Strategy Process Update Run for
Collection Strategies , you can:
the date ID and the run ID of the run you want. On the Dunning
Parameters tab page, choose the
Trace (Display Trace) pushbutton.
Here you can display BRF or BRFplus traces using different selections. You
can select by dunning proposal run using the date ID and run ID. Or you
can display for business partners, contract account groups, collection steps,
and collection strategies. Displaying for contract accounts and business
partners is only possible here if the system has actually generated dunning
headers.
NOTE
If the system did not generate any dunning notices, you can access the
report only by means of the BRF or BRFplus trace.
In the dunning history
You access the dunning history from the menu of the dunning proposal run
under Environment Dunning History . Or on the SAP Easy Access
screen, choose Account Further Information . Then in the history
display, choose the
Trace ( Display Trace) pushbutton. Or from the
menu, choose Goto Display BRF Trace .
You can find examples for contract-related proposal of items and the contract account
related proposal of items.
In the criteria for the minimum/maximum amount check of the clearing amount, you can
also specify whether a clearing amount for disconnection-relevant items is enough to
trigger the reconnection of an accompanying installation.
See also:
Reconnection overview
See also:
Reconnection overview
You can find the documentation on the accompanying workflows under SAP
Utilities Customer service Process execution Disconnection/reconnection.
additional activities to be executed after the open item has been cleared. You can access
all payment document information with the exception of the document number.
When the payment document is created, event 0200 checks if the installation can be
reconnected. The system checks whether the paid item has a dunning indicator, and
whether a dunning history exists for the item.
If the item is allocated to a contract, the system determines all other open items for this
contract. If it is not, the system determines all open items for the corresponding contract
account. The system decides whether the open item is relevant for a disconnection i.e.
whether a disconnection document is allocated to the item.
Event ISU_CECK_RECONNETION_R720 (trigger reconnection during clearing) now
determines whether the installation should be reconnected. It does this by calculating the
difference between the total amount and the total clearing amounts from the
disconnection-relevant items.
If the difference is zero the item relevant for disconnection is cleared, and the
reconnection can take place.
You can also define your own rules for determining when a clearing
amount can trigger reconnection. You must define corresponding
criteria in the event R720 (see documentation on the function module
Trigger reconnection via clearing
ISU_CECK_RECONNETION_R720).
The system now reads the disconnection processing variant from the disconnection
document header. Since the disconnection document was generated from the dunning
program, the variant has the abbreviation DUNN.
The Customizing in the processing variant then tells the system whether the reconnection
is contract related or contract account related. If the items are to be proposed contract
related, you must set the indicator Cntrt-rel. prop (see also Propose contract-related
reconnection.).
If the indicator is set, the system triggers the event disconnection reason
obsolete (Disconnection.DisconReasonObsolete). This starts the reconnection workflow
and completes the clearing of open items.
If the indicator is not set, the system determines all other items relevant for disconnection
in the contract account. If the system finds other open items relevant for disconnection,
the event trigger reconnection via clearing (ISU_CECK_RECONNETION_R720) is
called. This checks whether these items have been cleared and whether the clearing
amount is sufficient for reconnection.
If these items have not been cleared, reconnection does not take place, and the
event disconnection reason obsolete(Disconnection.DisconReasonObsolete) is not
triggered.
In both cases, open item clearing is completed.
See also:
If all the disconnection-relevant items included in the installment plan are cleared, the
criteria for reconnection has been fulfilled.
See also:
If you want to specify a lower value, you can maintain this in event
R720.
Table TA_FKKCL contains all items responsible for the disconnection of an installation.
This provides you with the freedom to specify whether the total amount of cleared items
during clearing is enough to trigger the reconnection of an installation.
See also:
Reconnection proposed per contract. The system checks the open items
of one contract (not all contracts) to determine whether the reconnection
criteria are fulfilled.
See also:
Contract
account
Contract
Payment/
Amount Clearing
installment
amount
plan
10001
4711
200.-
0.-
10002
4711
300.-
0.-
10003
4711
500.-
300.--
Dunning history
Document
No.
Contract
account
Contract
Dunning
amount
Disconnection
document no.
10001
4711
200.-
30001
10002
4711
300.-
30001
10003
4711
500.-
30001
The customer partially pays the item (document 10003) assigned to the contract account
with EUR 300. As a result, the clearing amount for contract 1 and 2 is EUR 0. The utility
installations that belong to contracts 1 and 2 can therefore not be reconnected because the
criteria for reconnection have not been fulfilled for both contracts.
Contract
account
Contract
Payment/
Amount Clearing
installment
amount
plan
10001
4711
200.-
0.-
10002
4711
300.-
0.-
10003
4711
500.-
500.--
Dunning history
Document
No.
Contract
account
Contract
Dunning
amount
Disconnection
document no.
10001
4711
200.-
30001
10002
4711
300.-
30001
10003
4711
500.-
30001
The customer pays the item (document 10003) assigned to the contract account with EUR
500. As a result, the items assigned to the contract account have been completely cleared.
Again, the system executes the reconnection check for the items
assigned to the contract account and those assigned to the contract.
In this case, the 100% clearing has fulfilled the criteria for
reconnection. However, an installation has not been allocated to the
items assigned to the contract account. As a result, the system cannot
start the reconnection. If necessary, you can define a workflow that
informs an agent of this situation.
Example 3: Clearing the total dunning amount of a contract and the items
assigned to a contract account
You have set the indicator Contract-related item proposal.
Open item table DFKKOP:
Document
No.
Contract
account
Contract
Payment/
Amount Clearing
installment
amount
plan
10001
4711
200.-
0.-
10002
4711
300.-
300.-
10003
4711
500.-
500.--
Dunning history
Document
No.
Contract
account
Contract
Dunning
amount
Disconnection
document no.
10001
4711
200.-
30001
10002
4711
300.-
30001
10003
4711
500.-
30001
The customer pays the items for contract 2 (document 10002) with EUR 300, and the
items for the contract account (document 10003) with EUR 500. The items from contract
2 that are assigned to the contract and the items assigned to the contract account are,
therefore, completely cleared. The criteria for reconnecting the utility installation
allocated to contract 2 are fulfilled. The installation can be reconnected. The installation
allocated to contract 1 is not reconnected, however, because the items for contract 1 are
not cleared 100%.
See also:
Contract
10001
10002
10003
1
2
-
4711
4711
4711
Payment
plan/installment
plan
X
X
X
Amount Clearing
amount
100. 100. 800. -
0. 0. 500. -
Dunning History
Document Contract
number
Account
Contract
10001
10002
10003
Total
1
2
-
4711
4711
4711
Dunning amount
Disconnection
document
number
30001
30001
30001
The customer pays the item (document 1003) assigned to the contract account with EUR
500.-. The partial payment corresponds to 50% of the total dunning amount of all
disconnection-relevant items in the contract account (EUR 1000). The installation
allocated to the contract account can, therefore, not be reconnected since the total
dunning amount has not been 100% cleared, and, as a result, the reconnection criteria
have not been fulfilled.
Document Contract
No.
account
Contract
10001
10002
10003
1
2
-
4711
4711
4711
Payment/
installment
plan
X
X
X
Amount Clearing
amount
100. 100. 800. -
0. 0. 800. -
Dunning history
Document
No.
10001
10002
10003
Total
Contract
account
4711
4711
4711
Contract
1
2
-
Dunning amount
100. 100. 800.1000.-
Disconnection
document no.
30001
30001
30001
The customer pays the item (document 10003) assigned to the contract account with EUR
800. This corresponds to 80% of the total dunning amount of all disconnection-relevant
items in the contract account (EUR 1,000). As a result, the utility installation allocated to
the contract account cannot be reconnected. The total dunning amount has not been
cleared, which means that the reconnection criteria have not been fulfilled.
Example 3: Clearing the total dunning amount of a contract and the items
assigned to a contract account
You have not set the indicator Contract-related item proposal.
Open item table DFKKOP:
Document Contract
No.
account
Contract
10001
10002
10003
1
2
-
4711
4711
4711
Payment/
installment
plan
X
X
X
Amount Clearing
amount
200.300.500.-
0.300.500.-
Dunning history
Document
No.
10001
10002
10003
Total
Contract
account
4711
4711
4711
Contract
1
2
-
Dunning amount
200.300.500.1000.-
Disconnection
document no.
30001
30001
30001
The customer pays the items for contract 2 (document 10002) with EUR 300, and the
items for the contract account (document 10003) with EUR 500. The payment of EUR
800 corresponds to 80% of the total dunning amount of all disconnection-relevant items
in the contract account (EUR 1,000). The criteria for reconnecting the installations
allocated to the contract account have not been fulfilled. All installations remain
disconnected until the amount has been 100% cleared.
See also:
Disconnection/reconnection of utility installation: Workflows:
Returns
Purpose
This component enables you to process bank returns that may occur as part of a
debit memo or collection procedure, or with check deposits or outgoing
payments.
Features
In the first step, you have to enter the returns data in returns lots manually using
returns notes or automatically using a transfer program and then post these lots.
The system then processes the returns automatically. First, the receivables or
payables that were cleared on the basis of incoming or outgoing payments are
determined. Then the clearing is reset, which means that the original receivables
or payables are open again, and a returns document is created with the offsetting
postings for the payment document items. The system also creates further
postings that are necessary because of taxes or charges, and executes follow-up
activities such as adoption of incoming and outgoing payment methods. Bank
charges, as well as any tax amounts contained therein, are determined from the
returns amount, if this is specified, and posted to the general ledger. You can
pass on any bank charges to your business partners (without tax). By specifying
amount-specific scaled charges in Customizing for the returns reason, you can
levy additional charges to your business partner. These returns charges can be
posted in the general ledger or statistically.
You can define the follow-up activities in the system dependent on the returns
reason, the creditworthiness of the business partner, the tolerance group of the
contract account, and the number of returns that have occurred. Possible followup activities are:
Returns Lots
Definition
The returns lot is a central object in returns processing. It is essentially a
grouping of documents that were sent back by the house bank and are settled
with the same bank clearing account. Data can be entered in the returns lot both
automatically and manually.
Structure
A returns lot consists of a header that describes the lot. It contains administrative
data and general specifications that the system uses to post the individual items
of the return.
You define the general specifications in Customizing. These include the
document type, the clearing reason, the company code, the screen variant, and
the selection type. (In Customizing for Contract Accounts Receivable and
Payable, choose Business Transactions Returns Determine Document
Type and Clearing Reason for Returns). At the item level, you can manually
change specifications such as the posting date and value date, as well as entries
for taxes and charges. However, you are not allowed to change the clearing
reason and the currency.
Returns Category
Definition
Specifies the source of a return. The returns defined here are bank and check
returns.
Use
Together with automatic account determination, the returns category identifies
the G/L accounts for returns charges and the bank clearing account. By
assigning returns categories to Returns reasons, you ensure that different returns
reasons can be used for different G/L accounts.
Returns Reason
Definition
A returns reason specifies the cause (from an internal business view) of a return.
Examples of possible reasons include "insufficient funds" or "unknown account
number."
Use
The returns reason triggers a number of activities. The activities include charge
handling, and setting dunning/payment locks and payment methods.
In Customizing you must assign the returns reasons given by banks to your own
company-specific returns reasons. This allows you to treat different returns
reasons as defined by individual banks in a uniform way.
Structure
Using activity keys in Customizing, you can define multiple activities to be
performed in the event of a return. The activity key is made up of the Company
code, No. of returns, Creditworthiness, and Tolerance group fields.
For each returns reason, you can define lot charges based on currency and
maximum permitted differences for the payment and return amount.
Creditworthiness
Use
The creditworthiness of a business partner provides information on the business
partners payment history and influences the selection of activities for dunning
and/or returns and also the calculation of charges. Various different business
transactions, such as returns, dunning notices, installment plans, and write-offs
update the creditworthiness in the system automatically. You can also transfer a
creditworthiness record from external systems or manually.
The current status of a business partners creditworthiness is determined as a
weighted total on the basis of the creditworthiness figures recorded over the last
48 months. You define the monthly weightings in Customizing. A
creditworthiness of zero means that the business partner has an excellent
payment history. The maximum value is 9999.
The level of creditworthiness depends on:
Initialization in Customizing
Manual creditworthiness
You can define a creditworthiness weighting in the returns reasons. Once returns
processing has taken place, the creditworthiness figure of the current month is
increased by this figure.
You can define the creditworthiness weighting with the returns reason in
Customizing (see IMG for Contract Accounts Receivable and
Payable Business Transactions Returns Configure Returns Reasons).
Write-offs
Write-offs can also have a negative effect on a customer's creditworthiness. If
you want to use creditworthiness determination, enter the write-offs in
conjunction with a creditworthiness figure.
You can define the creditworthiness weighting with the write-off reasons in
Customizing (see IMG for Contract Accounts Receivable and
Payable Business Transactions Write-Offs Configure Write-Off
Reasons).
Installment Plan
In the Implementation Guide for Contract Accounts Receivable and Payable,
under Business Transactions Deferral and Installment Plan, you can:
In the Define Deactivation Reasons for Installment Plan activity, for each
deactivation reason, define whether a creditworthiness entry updated on
creation of the installment plan is to be reversed when the installment plan
is deactivated.
Features
The system automatically determines the creditworthiness of a business partner
in returns processing and in a dunning run. The creditworthiness influences the
activities and the charges levied, provided that you have defined the activities
and charges dependent on creditworthiness in Customizing.
There is a display and change function for creditworthiness. The features are as
follows:
You can release this fixed value manually, so that the creditworthiness
can change for time-dependent reasons.
Function
Business Partner Account
Information(SAP_FI_CA_PARTNER_ACCOUNT_INFO) Display
Business Partner Creditworthiness or Change Business Partner
Creditworthiness.
SAP Menu
Master Data Business Partner Display/Change Creditworthiness
Procedure
51.
...
189.
1.
You enter a new returns lot or change an existing returns lot
(see Entering Returns Lots Manually).
3.
...
10.
a.
Specify data relevant to the returns lot in the header
of the payment lot, and determine the Type of Posting.
The system requires this data to clear charges and taxes as well as to
determine the bank clearing account to be used.
You can also define the number of items as well as the amount of the
credit or debit total in the header of a returns lot. If you have chosen
default values, the returns lot cannot be closed until the corresponding
totals of the returns items entered match the default values.
11.
b.
Depending on the screen variant you have chosen
(see Screen Variants for Processing Returns Lots), enter an item for
every return, in which you enter the amount, value date, returns
reasons and payment document.
190.
2.
Once you have made all your entries, close the returns lot
(see Closing a Returns Lot Manually.)
191.
3.
Post the returns lot (see Posting a Returns Lot Manually).
4.
...
12.
a. When you post a return, a new open item is created.
The use of this new item is dependent on the type of posting.
13.
b.
The activities defined in the system for a returns
reason and other activities are carried out (see Executing Returns
Activities).
192.
4.
Edit any items shown to be incorrect during posting and post again
(see Postprocessing a Returns Lot Manually).
You can display returns lots that you have entered. In this display, the system
also shows returns lots that have already been archived.
Result
Depending on the type of posting, the original receivables are re-opened, or new
receivables are set. Different activities are executed depending on the system
settings.
Any necessary entries were added to the returns history (see Displaying the
Returns History).
Returns are entered automatically if the bank sends a data medium with returns
or if an external system provides a returns file (see also Entering and Posting
Returns Manually).
Automatic posting of returns allows background processing (as batch sessions),
which in turn results in higher data throughput.
Process Flow
1. Enter the program run parameters for automatic transfer of returns
(see Entering Parameters for Automatic Returns Transfer).
2. When the program is run, the data records from the application server file
specified are read and checked. If the data records are correct, the system
generates one or more returns lots.
3. If you have set the appropriate indicators in the program run, the returns
lots generated are closed and posted.
a. When you post a return, a new open item is created. The use of
this new item is dependent on the type of posting.
b. The activities defined in the system for a returns reason and other
activities are carried out (see Executing Returns Activities).
4. Edit any items shown to be incorrect during posting, and post them again
(see Postprocessing Returns Lots Manually).
Result
Depending on the type of posting, the original receivables are re-opened, or new
receivables are set. Different activities are executed depending on the system
settings.
Any necessary entries were added to the returns history (see Displaying the
Returns History).
Activities
Integration
Returns activities are based on the Returns Reason.
Features
In Customizing you can make the following settings for a returns reason based on
company code, number of returns, creditworthiness, tolerance group, house bankand so
on (see the Implementation Guide for Contract Accounts Receivable and
Payable Business Transactions Returns Configure Returns Reasons).
Activities for charge handling, such as making business partners liable for
charges (see Charge Handling)
Set a dunning lock at contract account, item, or contract level
Set a payment lock at contract account, item, or contract level
Postpone a due date by defining deferral days
Scaled charges and amount differences
Delete the outgoing payment method in the contract account or contract
in the event of credit memo returns
Delete the payment method in the item on which the return is based
Change the payment method in the item on which the return is based
In event 0292 you can set a new payment method in the item dependent on
the existing payment method.
You can also define your own function modules for event 0295. These function modules
execute other returns activities, or supplement existing activities. (See also the
documentation for the sample function module FKK_SAMPLE_0295)
In the different application areas (industry components), you can carry out further
returns activities (see Executing further Returns Activities).
If you have defined returns activities dependent on the house
bank in the system settings, you must specify the house bank in the
returns header lot on the tab page Clearing Account and
Management.
Special Features for Check Returns
You can post outgoing checks that cannot be delivered or that have been returned as
returns instead of reversing the check payment in check management if additional
activities, such as changing the payment method in the contract account are to follow
automatically.
Roles
Business Partner Account
Information (SAP_FI_CA_PARTNER_ACCOUNT_INFO) Returns
History
SAP Menu
Account Other Information Returns History
The initial screen for entering selection conditions appears.
With appropriate Customizing settings for the insallment plan categories, when
you create an installment plan, you can update the creditworthiness of the
business partner concerned. With appropriate Customizing settings for the
deactivation reasons, you can reverse the creditworthiness entries.
Industry Component Utilities (IS-U)
An installment plan can be deactivated automatically by the dunning run when a
certain dunning level is reached.
You define the forms for correspondence with business partners who have
arranged to pay in installments with the Print Workbench component.
Installment Plan
Definition
With an installment plan you divide source items to several installment
receivables that have a due date in the future. Once an installment plan has been
posted, the items of the installment plan and not the source items are referred to
when a bank collection is made or when a dunning run is carried out.
Use
You create an installment plan for business partners wishing to make payment
but who are temporarily unable to keep up their payment obligations. One or
more source items can form part of an installment plan. You can include
receivables and items for a currency and a contract account in an installment
plan, and create installment plans on a cross-account basis.
Structure
An installment plan consists of a statistical document with several installment
receivables. The individual installment receivable is cleared upon payment. The
number of the installment plan is saved in the source items. This ensures a
connection between the installment plan and the source receivables and
between the source receivables and the installment plan. If interest is payable on
an installment plan, the installment plan will also have an interest supplement.
Roles
Manual Postings (SAP_FI_CA_MANUAL_POSTINGS) Change
Document
SAP Menu
Document Change
194.
2.
Enter the document number.
195.
3.
Choose Goto List of Business Partner Items.
196.
4.
Doubleclick on the item to be deferred.
197.
5.
Enter a deferral date.
198.
6.
Save the document.
You can also enter a deferral date at the same time as you enter a document (see
Entering Documents).
Result
The deferred item is not dunned in a dunning run or collected from the bank by the
payment program until after the date specified. Once the deferral date has passed, or if
you have deleted the date from the item, the item can be dunned and collected.
you want to make use of this inability to pay to terminate the business
relationship with the business partner.
Features
The procedure described below has been selected to implement this logic in
Collections/Disbursements.
In Customizing for dunning procedures you can assign an alternative dunning
procedure to every dunning procedure (see SAP for
Insurance Collections/Disbursements Business
Transactions Dunning Dunning by Dunning Procedure Configure
Dunning Procedure).
This alternative dunning procedure is transferred to the items that are generated
when an installment plan is created (event 3000 in the installment plan:
Collections/Disbursements: adds additional fields to the document items in the
installment plan). Items that bear a key for a dunning procedure for which no
alternative dunning procedure has been defined (this would be the case with first
premium dunning procedures) must not be included in an installment plan.
With the complete dunning you must ensure that items are suppressed
when converting to an installment plan, if there is an active initial premium
dunning procedure for the contract to which these items are assigned.
If an initial premium dunning procedure has been agreed in relation to an
insurance contract, or if an initial premium dunning procedure is already in
progress, the subsequent receivables from this contract must not be
converted to an installment plan.
The following procedure has been selected for contract dunning: As long
as an initial premium procedure exists, no later items are converted to an
installment plan.
This procedure ensures that only receivables from subsequent premiums though not all receivables from subsequent premiums- can be included in an
installment plan (technical conversion occurs at event 3020).
If open items should not be included in the installment plan on the basis of the
above conditions, a warning message is displayed.
You should make a selection with open items to see whether they can be
converted to an installment plan.
There are one or more open items on the contract account of a business
partner.
Prerequisites
To be able to prioritize the clearing of original items when payments are received,
you set the Clrg Priority (clearing priority) indicator. You do so in Customizing for
Contract Accounts Payable and Receivable under Business
Transactions Deferral and Installment Plan, Activate Additional Installment
Plan Enhancement.
Features
When you calculate interest, the system creates an interest document
automatically. When you enter a charge amount, the system posts a document
for the installment plan charges. During posting, interest and charges documents
are automatically transferred to the installment plan for the original receivables
(seeCharging Interest and Surcharges for Installment Plans).
When you create an installment plan, the system copies the
company code, contract, business area, and business place from the
original item (in the standard system), as long as these fields have the
same value in all original items selected. If you do not want to fill
these fields in the installment plan, or want to enter other values, you
can do this by defining event 3000 accordingly (see the
documentation of the sample function module FKK_SAMPLE_3000).
The system can calculate the first installment as a percentage of the total amount
of the installment plan. Enter the percentage in Customizing for Contract
Accounts Receivable and Payable under Business Transactions Deferral and
Installment Plans Define Categories for Installment Plan. Activate the
enhancement under Business Transactions Deferral and Installment
Plans Activate Installment Plan Enhancement for Charges/Interest.
When you use a suitable installment plan category, the system calculates the first
installment as a percentage.
Activities
53.
199.
1.
...
Choose one of the following paths:
Role
Process Outstanding
204.
6.
Choose Continue.
An Installment Plan Proposal appears, in which you can make the following
changes:
Add installments
Delete installments
Prerequisites
You can only process an installment plan that has not been deactivated and not
been cleared. If you want to change the amounts in an installment plan, you must
ensure that the total of the installment receivables always corresponds to the
total of the source receivables.
Procedure
54.
...
206.
1.
Choose one of the following paths:
Role
Process Outstanding
Payments (SAP_FI_CA_OUTSTANDING_PAYMENTS) Display
Installment Plan/Change Installment Plan.
SAP menu
Account Installment Plan Create/Change
207.
2.
Select Change or Display.
208.
3.
Specify the desired installment plan and choose Continue.
If you use the input help for the Installment Plan Number field, for
selection using the installment plan history, the system displays only
active installment plans as standard. If you also want to display
deactivated installment plans, you have to specify a deactivation
reason on the tab pageInstallment Plan History.
The following table lists the functions you can use when changing or displaying
an installment plan:
Functions with Display
and Change
Call/function
Procedure/Notes
Print
correspondence
Display source
receivables in the
account balance display
Environment Source
Receivable (Account
Display)
Goto Changes
Display interest
supplement
Environment Interest
Supplement
Prerequisite is that
interest is charged on the
installment plan.
Display/change
processing locks
Call/function
Procedure/Notes
Deactivate installment
plan
Installment
Plan Deactivate
Installment Plan
Add installment
Delete installment
Display source
receivables in the
installment plan history
Deactivation reason
Deactivation date (to be entered when deactivating)
You can conduct various evaluations of the installment plan history using
the following paths:
Role
Process Outstanding
Payments (SAP_FI_CA_OUTSTANDING_PAYMENTS) Display
Installment Plan History
SAP Menu
Account More Information Installment Plan History
Features
The interplay between the installment plan and dunning by dunning
procedure for insurance companies is described here.
On the basis of the above prerequisites, you must differentiate between the
following two cases when you create an installment plan:
Calculates interest only for installment payments that are received late
Calculates interest both for installment payments that are received late
and those received early
Choosing SPACE (Interest Not Calculated from Original Items) allows you
to overwrite the proposed interest start date, which is also the installment
plan start date, when processing the installment plan.
Installment Plans. Make your setting in the Interest on Arrears field. See the
documentation for the field.
For the deactivation reason, you can also specify how you want the system to
handle the interest calculated. You can choose to have the interest credited or
refunded, either partially or wholely. Or you can specify that the interest posting
remains despite the deactivation. In Customizing, choose Business
Transactions Deferral and Installment Plans Define Deactivation Reasons
for Installment Plan.
Surcharges and Interest on Installment Plans
In addition to interest on installment plans and originial items, you can also:
Calculate interest for original items up the start date of the installment plan
(default value) or up to any other point in time (before the start date of the
installment plan)
To do so, choose Business Transactions Deferral and Installment
Plans Activate Installment Plan Enhancement for Surcharges Interest and
enter the value X in the InstPlan Enh. (installment plan enhancement) field. If you
make that entry, then the system displays the pushbuttons for using this
enhancement (see below).
The system derives additional specifications, such as the installment plan
category and charge category, from the activity Define Categories for Installment
Planunder Business Transactions Deferral and Installment Plans.
You make settings for posting any charges you make in the Define Charge
Categories for Installment Plan Surcharges activity.
In the Exclude Main or Subtransaction from Surcharges activity, you can exclude
certain main transactions and subtransactions from being assessed with
surcharges.
Features
You can calculate interest for original items and installment plan items, as well as
levy charges and surchages on installment plans.
Activities
55.
...
209.
1.
Choose one of the following paths and create an installment plan
proposal (see Creating Installment Plans):
Role
Process Outstanding
Payments(SAP_FI_CA_OUTSTANDING_PAYMENTS) Display
Installment Plan/Change Installment Plan.
210.
211.
212.
213.
SAP menu
Account Installment Plan Create/Change
2.
On the Create Installment Plan: Specifiy Installments screen,
choose the
Calculate Interestpushbutton. A dialog box appears for you to
enter the interest parameters.
3.
In the toolbar, choose either the pushbutton
Calc. Inst.Plan
Surcharge (Calculate Installment Plan Surcharge) or
Calc. Inflation
Surcharge(Calculate Inflation Surcharge) to calculate inflation or installment
plan surcharges.
4.
Choose the
OrigItmIntCalc. (Original Item Interest Calculation)
pushbutton in the toolbar to calculate interest for original items up the start
date of the installment plan (default value) or up to any point in time you
choose.
Specify the due date for the interest, and whether you want the interest to
be treated as one or more separate interest installments.
To specify the point in time up to which the system should calculate interest
on the original items, enter a date in the Orig. Item Interest Calc. Tofield.
5.
Choose Installment Plan Post. You can use the following
options to calculate interest retroactively:
Only overdue installments are taken into account (in other words,
installments that have been paid too late).
Function
0 No printing
1 Print immediately
When you create the installment plan payment forms, the program analyzes the
installment plans with print types 2, 3, or 4 and fills the correspondence container
with the relevant correspondence. You can then print this correspondence with
the Print Workbench.
Activities
214.
1.
To create correspondence container entries for printing
correspondence with print types 2, 3, and 4, in the SAP menu
choose: Periodic Processing For Contract
Accounts Correspondence Installment Plan Printing.
215.
2.
Select the installment plans to be considered using the business
partner, contract account, and/or the company code.
Restricting the due date for net payment only has an effect on installment
plans with print type 3.
216.
3.
Schedule the program run (see also: Functions for Scheduling
Program Runs).
If correspondence is created for an installment plan, the field Print Date in the
installment plan header is filled. If the field already contains an entry, no further
correspondence is created. The program also makes sure that only one payment
form is created for any one installment. If you do not restrict the due date for net
payment for print type 3, the program creates a payment form for the next
installment due provided no payment form has been created for this yet.
If you enter the date ID and identification of a run and
select Environment Correspondence in the menu of the transaction, you can
display a list of the correspondence created by the run (installment plan
correspondence and payment forms).
In the Implementation Guide for Contract Accounts Receivable and Payable,
under Business Transactions Deferrals and Installment Plans Define
Default Values for Installment Plans, you can define a default value for the print
type. If you set the indicator Display Dialog, a user can select a print type when
he/she saves an installment plan.
In event 3031, you can also make the default value dependent on the installment
plan parameters. See the documentation for the sample function module
FKK_SAMPLE_3031.
Promise to Pay
Purpose
You use a promise to pay to record a business partner's agreement to pay
receivables that are on his or her account.
Integration
For dialog processing, you can use a user interface in the Interaction Center Web
Client.
Features
A promise to pay states which amounts are to be paid by what dates.
A promise to pay can specify that the business partner payment is
in the form of a debit memo or a direct debit.
Since the payment dates defined in the promise to pay are generally after the
due dates of the items covered by it, you can (optionally) add charges and
interest on late payments as part of the promise to pay.
You can create, approve, withdraw, change and valuate promises to pay.
These activities are all performed online, with the exception of the valuation,
which is a mass activity. Using the functions of valuation of promises to pay, you
can:
When you change a promise to pay, the system does not write history records.
Instead, it creates a nw promise to pay with a reference to the original promise to
pay. This gives you a better overiew. The person actually doing the approving
also sees which change needs to be approved.
If a promise to pay is accepted, the check indicator is automatically removed
from the promise to pay.
If a promise to pay is rejected, the check indicator is automatically removed and
the promise to pay receives the status Not approved. The reference to the
promise to pay is removed from the assigned items.
Activities
You decide whether the creation/change must be approved in event 5516; the
relevant business object is CA_P2P, the rule for the clerk determination
21000071, and the workflow sample WS21000104. See the documentation for
the sample function module FKK_SAMPLE_5516.
Adjusting the interest means that the system reverses the original interest and
instead calculates interest on all items again as follows:
If a promise to pay is withdrawn, the same options apply. However, in this case,
the treatment of charges and interest is dependent on the withdrawal reason and
not on the category of the promise.
If a promise to pay is replaced, charges and interest for the old promise to pay
are handled according to the withdrawal reason; the charges and interest of the
new promise to pay are handled according to the category selected.
If the same charges are to be levied for the new promise to pay as for the old
one, there is no new posting. The charges receivable already posted is
automatically added to the new promise.
A similar rule applies if the interest amounts are the same. Since a new interest
calculation is not necessary only if the items subject to interest and the periods
remain the same, the interest receivable can only be added to the new promise if
both the items and the installments remain the same. However, this is an
exception when replacing a promise to pay, since in that case only payment data
would have changed, which would not require entering a replacement.
Correspondence Creation
Use
You can send correspondence to the business partner when a promise to pay is
created and in the case where a promise to pay is not fulfilled.
Features
The correspondence type for printing a promise to pay is 0045 (Promise to Pay).
The correspondence request is created in event 0806. In this event, an entry is
created in the correspondence container. This can be printed immediately or in
mass printing. Event 0805 prints the correspondence type. In this event, the print
parameters are adjusted specific to the correspondence and the Print Workbench
is called. In the Print Workbench, the correspondence-specific form class
FI_CA_P2P_CORR is used. As an example form, SAP delivers the application
form FI_CA_P2P_CORR_SAMPLE, category SAPscript.
The following details are used for printing:
See the documentation for the sample function modules FKK_SAMPLE 0805
and FKK_SAMPLE 0806.
Promise fulfilled
Using the valuation data determined, the system decides whether the valuation is
saved and the promise to pay closed or whether there should be a further check
at a later date.
The system automatically sets the first check date when a promise to pay is
created. The date is defined in event 0184. In the standard version, the system
sets a date that is seven days after the due date of the middle installment.
For five installments, a check is scheduled seven days after the
due date of the third installment. If there are an even number of
installments, the system uses the later of the two middle installments.
During the check, the decision must be taken whether a further check is
necessary at a later date, and the promise is open until then, or whether the
promise is to be closed in its current status. This decision is taken in event 0189.
In the standard version, a new check date is set if the old check date was not
after the due date of the last installment; otherwise the promise is closed. In the
standard version, the new check date is seven days after the due date of the last
installment. If the date determined in this way is not in the future, the promise to
pay is also closed.
Logic for the Valuation
In the valuation, the following is considered: How much of the promised amount
has actually been paid, and how late the payments were. With regard to the
delay in payment, in Customizing, you can define a number of tolerance days
and what reduction in the valuation is made for each day in excess of these
tolerance days. You define this for each company code.
In Customizing, you have agreed 2 tolerance days and 1.0%
reduction for each further day late. The following promise to pay has
been given:
Write-offs are not other clearings, since they are not deemed to be a waiver of
the receivable; instead, they reflect the opinion that the receivable will probably
not be collected.
Valuation and Creditworthiness
For promises to pay that are not fulfilled, an entry can be made to the
creditworthiness of the business partner. In the standard version, the system
checks whether a creditworthiness weighting is specified in Customizing in case
of non-fulfillment. You can specify the creditworthiness rating for each category
of promises to pay. If a creditworthiness weighting is specified, a new
creditworthiness record is created with this value and the total creditworthiness of
the business partner is reduced. Using event 0188, you can change the
creditworthiness weighting determined in the standard system.
Subsequent Changes to Valuation
As soon as a promise to pay is closed, all further payments, withdrawals, or other
clearings no longer influence the valuation. Therefore, a promise to pay should
not be closed too soon after the last due date; on the other hand, it must be
possible to make an adjustment for promises to pay where the valuation is later
determined to be incorrect. In particular, this should prevent a business partner
receiving a bad creditworthiness where this is not justified.
With a special authorization, you can subsequently change the level of fulfillment
and the status of a promise to pay manually. You have to justify the change with
a comment. All subsequent changes are recorded. The creditworthiness is
adjusted automatically.
Activities
56.
...
57.
...
217.
1.
To valuate and close promises to pay, on the SAP Easy Access
screen, choose Periodic Processing For Contract Accounts Valuation
of Promises to Pay.
218.
2.
Enter a date and an ID that you can use to identify the run later.
219.
3.
Enter a check date. Limit the selection by business partner,
company code, and promise to pay, as needed.
Promises to pay whose next check date is before or on this check date are
valuated.
220.
4.
Save your entries and schedule the program run.
For more information about scheduling and executing mass activities, see
Functions for Scheduling Program Runs.
Write-Offs
Using this component, you can write off open receivables and credits of business
partners. Write-offs are required if receivables are uncollectible or payables
cannot be paid, for example when the payment recipient cannot be identified.
Features
You can write off open receivables completely, or, if you want to waive partial
amounts of open receivables for your customers, you can also write off open
items partially. You have to allow partial write-offs explicitly in Customizing. You
are free to specify the partial amount to be written off in the transaction Write Off
Items.
When you write off an amount, the system clears the item written off, generates a
write-off document, and automatically posts to the expense or revenue accounts
defined in Customizing.
In Customizing, you can define rules for adjusting the tax for a write-off. If the
expense account posted to is relevant for tax, the system also corrects the
posted tax when you write off.
When writing off, you can also:
NOTE
Since SAP enhancement package 2 for SAP ERP 6.0, it is already possible
to inherit the G/L account assignment characteristicProfitability Segment
Number (CO-PA) (PAOBJNR) as a modification in event 5030. This
modification is not affected by an upgrade to SAP enhancement package 6
for SAP ERP 6.0. That means, that if you have implemented logic in the
installation-specific event 5030, the system continues to run through this
logic when you write off.
Using a function module, specify check rules in Customizing that the
system uses to decide whether open items of a business partner can be
written off and which these are
For example, you can specify that receivables can only be written off if there
are no credit items on the contract account and the receivables are more
than six months overdue. If a user has the appropriate authorization, the
system offers all open items to be written off. This means that the check
rules are not applied. The system always applies check rules at a check
level (business partner, contract account, contract, document), groups the
open items to be written off at the check level, and applies the check rules
to each group.
Update the creditworthiness of customers
You can reverse write-off documents, meaning that the receivables or payables
become open again.
Define the write-off reasons that are stored in the written-off line items for
information purposes
Define the G/L accounts for writing off receivables and payables and
define these accounts for automatic account determination in Customizing.
If you also want to permit partial write-offs, set the indicator PW/O (permit
partial write-off) for the required write-off reasons under Business
Transactions Write-Offs Define Write-Off Reasons.
Enter default values and check the specifications for write-off in event
5006
people with special authorization for activity 020 of the authorization object FI-CA
Special Function (technical name F_KK_SOND). To define authorizations,
see Basic Functions Authorization Management.
Procedure
221.
1.
Choose one of the following paths:
Roles
Account Maintenance, Transfer Postings,
Reversals (SAP_FI_CA_ACCOUNT_MAIN_REVERS) Write Off Items
SAP Menu
Account Write Off Items
222.
2.
Enter your selection specifications for the open items and the
details for posting the write-off.
223.
3.
Choose Continue or, if you have the authorization to write off
without check rules, choose Edit Select without Rule.
The items that can be written-off are displayed. If applicable, the number of
items not meeting the checking rules is output.
224.
4.
Select the open items that you want to write off.
Select and activate the required items or select the items using the amount
field in the corresponding row. The system transfers the complete amount
of the item (column Gross Clearing) for the write-off.
If you only want to write off a partial amount, enter this partial amount in the
column Gross Clearing.
225.
5.
Choose Post.
Via Extras Display Document, you can display the write-off document.
Via Extras Account Balance, you can display the account balance of the
business partner.
Via Extras Notes Enter Notes, you can enter notes for write-off document.
Result
The open items you selected are (partially) cleared and a write-off document is
created. The document number of the document created is displayed in the
status line. If you only cleared part of the amount, the remaining amount of the
document is open.
If you want to use write-off variants, you processed the following IMG activities:
Features
Using the mass write-off function, you can write off open receivables and open
credits. These can be written off statistically or posted to the general ledger. You
can select the documents to be written off according to various parameters that
you maintain on the tab pages. This allows you to select according to the type of
business transaction (for example, dunning charges). You can also conduct a
simulation run before the update run for monitoring purposes.
In event 5008, which is always processed, you can apply industry-specific check
rules. In this event, you can also apply check rules that are independent of
whether the indicator Do Not Apply Write-Off Rules is set.
Using a write-off variant, you can automatically write off or prevent the write-off of
individual items based on age and amount grids. For each age and amount
structure, the write-off variant defines whether the current receivable can be
written off. You can display the procedure as needed in the application log for
information purposes.
The system determines the write-off variant in event 2957; you can define this
event to best suit your needs.
200 days ago, you posted document 4711 with an amount of 1 000. There is
a write-off variant VARI with the following settings:
Days after
Due Date
Sequential
Number
Amount
Automatic
Write-Off
50
500
100
500
100
1000
100
5000
Log
...
Choose one of the following paths:
Role
Receivables
Administration(SAP_FI_CA_RECEIVABLES_ADMINIST) Start
Write-Off Run
Write-Off History
Use
Write-off data provides information on a business partner's payment history.
The write-off history allows you to access a business partner's or a contract
account's write-off data quickly and easily.
Integration
Activities
You can find the write-off history under the following paths:
Roles
SAP Menu
If you have defined a separate write-off reason for waivers in Customizing of Contract
Accounting, you can use the write-off history to generate a waiver directory.
Features
You can find detailed information on the features in the program documentation
on the Public Sector Write-Off History.
You can find basic information on the write-off history under write-off history .
Activities
You can find the Public Sector Write-Off History in the Contract Accounting menu
under Account Further Information Public Sector Write-Off History.
events 0105 and 1205. For example, you can use function modules
FKK_WF_TEXT_1205 and FKK_WF_TEXT_0105.
To execute active application-specific standard modules, call these directly from the
customer-specific module.
Process Flow
In the system receivables are submitted in two steps. First you have to release
the items for collection. Then you can submit the released items. The collection
items created are recorded in the system. You can carry out the release and
submission of the items manually, automatically as a mass run, or automatically
in other business transactions. The system can determine the collection agency
to which the receivables are to be submitted automatically during release or you
can specify a collection agency when you submit. For the submission, the system
checks whether the items entered manually or selected by the release run have a
status that permits submission. For each collection agency, it creates a list and/or
a submission file with all information relevant for collecting the receivables. Or, if
you use the service-oriented interface, the system calls the enterprise service
needed for the task. You can generally submit all items with the
status Receivable Released for Submission (01) or Receivable Called Back (09).
If the target account for the transfer posting is a contract account that belongs to
a collective bill account, the collective bill is updated automatically.
You can transfer:
Individual items receivables and credits (see also the explanations for
transfer postings in Clarifying Credits)
Procedure
60.
...
232.
1.
Choose Account Transfer Items.
233.
2.
Under Selections enter the business partner and the contract
account or the contract for which you want to make the transfer.
Alternatively you can enter the document number or the reference
document number of the document that you want to transfer post directly.
234.
3.
Under Transfer Target, enter the business partner and the contract
account or contract to which you want to make the transfer.
235.
4.
Under Transfer Specifications check the posting
specifications. Make any corrections, if necessary, and enter the transfer
reason.
236.
5.
Choose Select Items in the application toolbar.
237.
6.
On the processing screen that follows, activate the items you want
to transfer.
238.
7.
Save your entry.
Result
The transfer document is created, and you return to the initial screen.The number
of the transfer document is displayed in the status line.
You must define the social facilities that are to receive donations in the
method GET_FOUNDATION.
Features
The transfer posting function separates donations from tips and processes the
amounts as follows:
Tip amounts are transferred to the carriers contract account. The carrier
who is to receive the amount is determined according to the assignments in
the BAdI ISM_SD_ADDP_RECEIVER, method GET_CARRIER
(see Prerequisites).
Activities
Execute program RJK_ADDPAYMENT_REBOOKING_SAMPL (transaction
RJKREBOOKING).
Features
When you post a document involving time-based deferred revenues, the system
creates a trigger for the future transfer posting dates, in addition to the document
itself. The system also updates a trigger for the total amount. This trigger
transfers the total amount from the revenue account to the deferred revenue
account when the document is posted. The document itself contains the account
assignment of the revenue account.
For the example described in the previous section, in which a business partner
signs a maintenance contract amounting to 2,400 and involving service on the
15th of each month, the system would make the following postings:
Posting Data
Date
Posting
Amount Time
2400.--
Posting of Document
2400.--
200.--
200.-
...
...
...
...
NOTE
Note for the industry component Insurance
At event V800, you can have the system distribute the total amount based on
revenue recognition considerations. The system executes the actual deferred
revenue posting using the mass activity for transfer posting of deferred revenues.
Activities
1. To transfer revenue from the deferred revenues account to the revenue
account in the general ledger, you execute the mass activity Transfer
Posting Run for Deferred Revenue at periodic intervals. On the SAP Easy
Access screen, choose Periodic Processing Closing Preparation
Receivable/Revenue Adjustment Transfer Deferred Revenues .
2. Enter a date and an ID that you can use to identify the run later.
3. On the General Selections tab page, restrict the selection of the
documents to be transferred. To run a simulation transfer first, set the
indicator for it.
4. If you want to reverse the postings made by a transfer posting run, enter
the parameters of the run on the Reversal Parameters tab page.
5. Schedule the program run. For more information, see Functions for
Scheduling Program Runs.
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.
Prerequisites
You have made the following settings in Customizing for Contract Accounts
Receivable and Payable:
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 .
Features
The functions for event-based deferred revenue use the following four, new
database tables, belonging to three different categories:
The item table DFKKDEFREV_POS contains the information for the initial
transfer from the revenue account to the G/L account for deferred revenue.
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.
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). 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. 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.
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.
In the document display transaction, you can display the most important
attributes of deferred revenue postings by choosing Extras Deferred
Revenues .
Prepaid Processing
If you charge customers for services against a prepaid balance, you can map the
related prepaid processes in Contract Accounts Receivable and Payable. You
manage the prepaid credit on prepaid accounts.
The examples in the following sections are from the cellular telephony area, and
are meant to illustrate the prepaid processes.
Integration
The processing of prepaid credit and prepaid usages using prepaid accounts
forms only one facet of the prepaid processing supported by SAP. Prepaid
processing runs primarily in SAP Convergent Charging; subprocesses run in
SAP Customer Relationship Management (SAP CRM) and SAP ERP. The roles
of the individual components are described below:
SAP Convergent Charging (SAP CC)
SAP CC generates billable items for services used, and transfers these items to
the ERP system for further processing. This process is based on sets of rules
defined in SAP CC for pricing and account determination, in combination with
customer data, contract data, and product data that SAP CC adopts from SAP
CRM. The billable items contain the amount due for the usage of a service, along
with information on the account to which the receivable or payable is to be
posted. In addition, SAP CC manages the prepaid credit and refillable units that
change through the usage of services and through refills.
SAP Customer Relationship Management (SAP CRM)
In the CRM system, you:
Integration
Purpose
This component allows you to integrate Contract Accounts Receivable and
Payable with other SAP components, such as General Ledger Accounting, Cash
Management, Controlling, SAP Credit Management (FIN-FSCM-CR) and SAP
Dispute Management (FIN-FSCM-DM), and Funds Management.
Features
Contract Accounts Receivable and Payable enables integration with the following
SAP components:
Cash Management
Controlling
Information containers
Reconciliation Keys
Definition
Technical key with which documents from Contract Accounts Receivable and
Payable are grouped for transfer to General Ledger Accounting and Cost
Accounting.
Use
The posting totals of the corresponding documents are recorded per
reconciliation key. Once a reconciliation key is closed, no more postings can be
completed with it. Accordingly, the posting totals can no longer be changed. A
transfer document is created for General Ledger Accounting from the posting
total of each reconciliation key. An item with an amount equal to that of the totals
record is generated in the transfer document.
Structure
A reconciliation key consists of the following parts:
further postings can be made with this key. It indicates reconciliation keys
that are only allowed for certain postings (such as only for a payment run or
for a payment lot). It also documents the status of the transfer to the general
ledger, such as All Documents Transferred or All Documents Transferred
Up to Posting Date.
Totals Records
Integration
The reconciliation key represents the connection between the totals records
of Contract Accounts Receivable and Payable and the transfer documents that
go to the general ledger. In the document header of transfer documents,
FKKSU is saved as the reference transaction, and the reconciliation key with a
suffix is saved as the reference key. This means that the first twelve characters
of the reference key of a transfer document are the same as the reconciliation
key for which the transfer document was posted.
Negative Postings
Use
In Contract Accounts Receivable and Payable, you can create negative postings.
A negative posting reduces the transaction figures for the account posted to in
the general ledger. A debit posting as negative posting therefore does not lead to
an increase of the debit transaction figures; it leads to a reduction of the credit
transaction figures. This enables you to show transaction figures for accounts
after an incorrect posting and subsequent correction (for example, invoice
posting and reversal) as if neither the incorrect posting nor the correction had
taken place.
Features
The following table gives an overview of the effects of negative postings for the
most important business transactions:
Business Transaction
Result
Reversal
Resetting Clearing
Returns
Manual Posting
Payments on Account
Distributing Revenues
Activities
You decide whether to permit negative postings at company code level. The
corresponding setting in the company code table is also effective for Contract
Accounts Receivable and Payable. You make the setting for the company code
(negative postings possible) in the Implementation Guide for Financial
Accounting under Financial Accounting Global Settings Company
Code Check and Supplement Global Parameters.
In addition, in Contract Accounts Receivable and Payable, the document type
decides whether a posting may be posted negatively. You can designate a
document type such that negative postings are always created, or such that
negative postings are only created for corrections in the same fiscal year. You
make the setting for the document type in the Implementation Guide for Contract
Accounts Receivable and Payable under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Document Types Maintain Document Types and Assign
Number Ranges. For more information about the setting for the document type,
see the field documentation for the field Negative Posting.
The main and subtransactions that you want to define for a negative clearing
(example: Payments on Account) are in the Implementation Guide for Contract
Accounts Receivable and Payable under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Maintain Subtransactions.
Down payment accounts and accounts for tax clearing for down
payments
Profit and loss accounts: The changeover took place before postings in
the current fiscal year.
item list, the correct value would be 480,000 USD with a value of
380,000 EUR.
The receivables adjustment account is managed in the correct
currency. You also need an interim account for which balances are
only managed in local currency. The following adjustment postings
are necessary:
Receivables adjustment to interim account 80,000 USD
(60,000 EUR).
Interim account to receivables adjustment 60,000 USD
(60,000 EUR).
For the first posting, you have to specify the foreign currency amount
and local currency amount explicitly.
In the evaluation of open items for the key date, you can display totals in
transaction currency or in update currency. For clearing in alternative currency,
this leads to different results. In simulation mode, the results are displayed as if
currency-justified update had been active in the receivables account from the
very beginning.
You can also perform an evaluation by update currency and update amount
using the report for reconciling the general ledger.
Tax accounts
NOTE
Account assignment to a profit center is only possible if the field status group of
the G/L account allows this type of account assignment. The field status group is
entered in the G/L account master record.
Profit Centers in Postings to Bank Accounts and Bank Clearing Accounts
You can post account assignment to profit centers in bank posting or cash
journal posting in the following processes:
Returns
Below is a description of 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 new General Ledger
Accounting, 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 system determines the bank clearing account using posting area 1061. (In
Customizing, choose Contract Accounts Receivable and Payable Business
Transactions Incoming/Outgoing Payment Creation Define Bank Accounts
for Payment Program ). There you can enter a profit center 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 create 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 system also uses the profit center that was entered on the payment lot for
postings to a clarification account.
Cash Desk, Cash Journal
If you are entering payments, the system can propose a default profit center in
the same way that it proposes a company code or business area. You can enter
default values for the business area and profit center in Customizing at the level
of the cash desk, the office, or the company code. (In Customizing, choose
Contract Accounts Receivable and Payable Business Transactions
Processing of Incoming/Outgoing Payments Cash Desk/Cash Journal
Define Default Account Assignments ).
External Cash Desks
For payments using external cash desks, you can set the profit center using
events 6200 or 6210. For event 6210, you can use sample function module
FKK_SAMPLE_6210_TFK100K. If you register this function module, the system
adopts the values entered in Customizing (see the Cash Desk section).
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 BFKKRK 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 system uses the profit center entered in the returns lot for posting to a
clarification account, and it also uses it as a standard value for receivables for
charges, along with expense and revenue from charges.
Profit Center for Payables, Receivables, and Down Payments
You can enter account assignment to a profit center in line items that you 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.
NOTE
Since the Profit Center field did not exist in business partner items before SAP
ERP 6.0, Enhancement Package 4, the setting for it in the field status group
(profit center allowed or not) was not relevant. Accordingly, it does not make
sense to assume, based on the current setting in your system, whether or not
your enterprise wants account assignment to profit centers in the future.
Therefore, a new Customizing setting was introduced at the level of the company
code (IMG activity Set Up Company Codes for Contract Accounts Receivable
and Payable), where you can specify if you want to allow account assignments to
profit centers for business partner items. 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 Accounts Receivable (FI-AR) and Accounts Payable (FI-AP). In classic
Accounts 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 new General Ledger Accounting, the system assigns
profit centers and distributes amounts to profit centers automatically in related
subsequent items that are used for updating the general ledger.
Activities
To be able to use the profit center in Contract Accounts Receivable and Payable
with the full scope described here, you have to make the following settings in
Customizing.
The field status group is in the G/L account master records of the accounts receivables, liabilities, down payment, bank, cash and tax - on
theEntry/Bank/Interest tab page). You can double-click on it to display the
group attributes. The Profit Center field should be specified as an optional
entry. 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 in question and then navigate to the maintenance of the field
status groups.
Define default values for the cash desk
You define default values for the profit center and the business area in
Customizing under Contract Accounts Receivable and Payable
Business Transactions Payments Processing Incoming/Outgoing
Payments Cash Desk/Cash Journal Define Default Account
Assignments .
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 need to make the settings per 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. You make the necessary settings in Customizing under Contract
Accounts Receivable and Payable Basic Functions Postings and
Documents Document Define Account Assignments for Automatic
Postings Define CO Account Assignment Keys .
Example
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.
The profit center determined in this way is inherited in 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
If you create requests manually, you can enter the profit center directly. You can
enter default values and values for automatic creation (such as budget billing
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.
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.
You can assign the document type for the general ledger transfer individually for
each document. You do this via a module that you define for event 0061. The
system records separate totals records for FI-CA documents with different
document types for the general ledger transfer. The system creates the
documents for the general ledger transfer separately according to these
document types. If no document type is defined for the general ledger transfer,
the document type defined in Customizing is used for the posting (see
Implementation Guide for Contract Accounts Receivable and Payable,
Integration General Ledger Accounting Define Posting Specifications for
General Ledger Transfer).
Activities
To swap account assignments:
61.
...
239.
1.
Using the sample module FKK_SAMPLE_0945 as a guideline,
write a function module that will exchange the account assignments.
240.
2.
Enter the function module for event 0945 in the Implementation
Guide for Contract Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules.
241.
3.
Choose one of the following paths:
Role
Reconciliation Key
Administration (SAP_FI_CA_RECONCILIATION_KEY Change
Reconciliation Key
SAP Menu
Document Reconciliation Key Close
242.
4.
Enter the reconciliation key and select the field Subsequent
Adjustments.
You can only make entries in this field if you have special
authorization for the object F_KK_SOND with activity 050.
To transfer the posting totals to the General Ledger, choose one of the following
paths:
Role
Transfer General Ledger and Profitability
Analysis (SAP_FI_CA_TRANSFER_GL_PROFIT) Transfer Posting
Totals to General Ledger
SAP Menu
Periodic Processing Forward Postings Execution Transfer to
General Ledger.
Segment
Profit center
Business area
Fund
Budget period
Grant
The system splits the balance sheet items for the purpose of creating financial
statements for each dimension automatically based on their cause. If the
document splitting does not already reach a zero balance for the additional
dimensions, the system generates additional clearing items in the general ledger
view to bring the balance to zero.
NOTE
New General Ledger Accounting also offers document splitting by customerspecific fields or by characteristics of cost accounting for account assignment of
follow-up costs (such as discounts). Contract Accounts Receivable and Payable
does not support these types of document splitting.
Document splitting splits document items according to certain rules to different
posted subitems. These subitems represent the general ledger view of the
document, which update the balances in the general ledger. The split takes place
using the offsetting items for the item to be split, or using the item cleared by the
offsetting.
EXAMPLE
In an invoice with several different posted revenue items, document splitting
splits the receivable item in proportion to the revenue items.
EXAMPLE
In a payment, document splitting splits the posting on the bank clearing account
using the general ledger views of the items that were cleared by the payment.
Document splitting only provides useful results when the posted document
represents a given business transaction, such as in the above examples a
customer invoice or customer payment. When you transfer postings from
Contract Accounts Receivable and Payable, this prerequisite is not met, since FICA aggregates documents and transfers the data in summarized form to the
general ledger. For example, it is no longer possible to see in the transfer
document which receivables postings led to which revenue postings. For this
reason, new General Ledger Accounting does not split documents transferred
from FI-CA. The system merely ensures that the document balance for all split
characteristics is zero by adding additional clearing items. As a result of the split,
document items without account assignment (such as receivable items without
profit center or without segment) would be supplied with account assignments in
the general ledger view. Since this enrichment does not take place during the
transfer from Contract Accounts Receivable and Payable to the general ledger,
you have to ensure that these items already have an account assignment in
Contract Accounts Receivable and Payable. If you make the necessary system
settings in Contract Accounts Receivable and Payable, then Contract Accounts
Receivable and Payable supplies each posting, including receivables, payables,
tax postings or postings to a bank clearing account, directly with the necessary
account assignments. The system settings and the derivation of account
assignments from the master data, from Customizing or from other documents
are different for each characteristic.
Segment
Profit center
Business area
Fund
Budget period
Grant
EXAMPLE
A document contains a tax line with tax code A1, tax basis 300.00 and tax
amount 57.00. There are two revenue items for it an item for 119.00 that has
account assignment to segment S1, and one for 238.00 with account assignment
to segment S2. The supplement to the tax line shows the following:
Tax basis 100.00
Segment S1
Segment S2
The system uses this supplement data instead of the tax line to record the totals
records for the reconciliation key. This data is also used during the transfer to the
general ledger. This procedure therefore offers a similar level of detail as the
document split of the new general ledger.
You make the settings for splitting the tax items for the company code in
Customizing for Contract Accounts Receivable and Payable.
NOTE
Do not activate the split of taxes if you record separate tax data in the additional
tables DFKKREP06 and DFKKREP07. For a tax return that is based on the data
in these tables, the system is not able to derive suitable account assignments for
the posting in the general ledger. If the split of tax postings is not active, the
system makes account assignment of tax items independently of all other
document items with a segment that it determines using posting area 0300 from
Customizing. In posting area 0300, you can specify a segment for each G/L
account (tax account).
Postings to Bank Accounts
We consider postings to bank accounts to be all postings to bank accounts, bank
clearing accounts and cash accounts. The system recognizes these postings by
the fact that the document item contains a value date or that the G/L account is
designated as cash-flow-relevant in its master record.
Contract Accounts Receivable and Payable does not support the account
assignment split for this type of posting. Instead the system assigns a fixed
segment to these postings using posting area 0300.
EXAMPLE
In posting area 0300, the fixed segment BANKSEGMENT is entered. For the
segment balance of segment SEGMENT_1, this means that it is not possible to
determine what share SEGMENT_1 has in the credit on a certain bank account
or in the cash balance. Only the entire monetary amount can be seen, which is
represented as a receivable offset by BANKSEGMENT.
You can find posting area 0300 in Customizing for Contract Accounts Receivable
and Payable under Basic Functions Postings and Documents Document
Maintain Document Assignments Segments Define Segments for General
Ledger Items .
The Segment in Contract Accounts Receivable and Payable
In new General Ledger Accounting, you can use the segment to differing
degrees. You can either use the segment as an account assignment in selected
items (for example, only for P&L items), or you can use the segment in all items
in order to run segment reporting and create a balance sheet at the level of the
segment.
Contract Accounts Receivable and Payable supports only a comprehensive
solution. That means that once the segment is active in Contract Accounts
Receivable and Payable, you have to have account assignment to a segment for
all posting items. If you implement segment reporting in a productive system after
productive start, there are exceptions for migration scenarios.
Contract Accounts Receivable and Payable and Updating the Profit Center
in New General Ledger Accounting
If you are using Contract Accounts Receivable and Payable, you can use Profit
Center Accounting in new General Ledger Accounting. The precondition for this
is that you activated the scenario FIN_PCA (profit center update) in new General
Ledger Accounting.
The profit center, along with the related partner field Partner Profit Center, are
account assignment characteristics delivered as standard with the standard
system. You can set them in FI postings or derive them from other account
assignments. As a result, the ledgers, for which you activated the scenario, are
updated in new General Ledger Accounting.
Unlike classic Profit Center Accounting, which used a ledger separate from G/L
accounting, the ledger is no longer separate for Profit Center Accounting in new
General Ledger Accounting. If you have already gone live with Contract Accounts
Receivable and Payable, but have not activated the profit center update from the
start, there are migration scenarios available (see Migration to New General
Ledger Accounting and New Implementation of Contract Accounts Receivable
and Payable). For more information about Profit Center Accounting in new
General Ledger Accounting, see SAP Note 826357.
If you are using classic Profit Center Accounting (EC-PCA) along with the profit
center update in new General Ledger Accounting, and you also have activated
document splitting in new General Ledger accounting, then note the restrictions
explained in SAP Note 826357.
RECOMMENDATION
We recommend that you use Profit Center Accounting in new General Ledger
Accounting if document splitting is active.
In order for it to be possible to update postings of Contract Accounts Receivable
and Payable with profit centers during the transfer to the general ledger, certain
preconditions have to be fulfilled in Contract Accounts Receivable and Payable.
These preconditions are explained in more detail in the following.
For the transfer to the general ledger, the profit center must already be filled in
the entry view of the FI document.
NOTE
As of ERP enhancement package 4, there can be account assignment of the
profit center to G/L items and business partner items. In releases earlier than
this, account assignment is only possible to G/L items.
Contract Accounts Receivable and Payable can be used with industry
components, such as SAP for Utilities, SAP for Telecommunications, SAP for
Media or Public Sector Contract Accounts Receivable and Payable. Depending
on which industry component you are using, different scenarios can be
applicable. During the derivation of the profit center, the system uses both
industry-specific as well as non-industry-specific function modules. Therefore, the
derivation of the profit center varies in accordance with which industry
component you are using. Contract Accounts Receivable and Payable, with its
non-industry-specific rules, is only taken into account if no profit center was
derived on an industry-specific basis.
NOTE
Note that the appropriate business function of the given industry solution must be
active. For more information, see the release notes for the mentioned industry
solutions.
Cash Management
Purpose
This component enables you to update data in Cash Management (TR-CM).
Features
This update is madedirectly when you post a document in Contract Accounts
Receivable and Payable. This means that the Cash Management liquidity
forecast and cash position are always up-to-date.
In the contract account master record, you can define the following data for
updating the liquidity forecast:
Planning group
This way, contract accounts with collection authorization can be considered
separately from contract accounts to be paid on demand. The system
proposes the planning group when you enter a document.
Additional days
These days are considered when determining the expected cash receipt
date. The due date for net payment or the cash discount date (if cash
discount was agreed) is used as the baseline date for this.
Line items that are locked for payment can be assigned to an alternative planning
group automatically.
In the G/L account master record, you define a planning level for G/L accounts
that require the cash position to be updated. The system determines the planning
level when you post the document and enters it in the G/L item.
For mass postings that run in parallel processes, waiting time may occur due to
competing accesses during the update of data for Cash Management. For these
postings, Contract Accounts Receivable and Payable offers a parallel update
mode that you can activate for specific categories of mass runs in the
Implementation Guide for Contract Accounts Receivable and
Payable under Technical Settings Activate Parallel Update of Cash
Management. Cash Management is then updated at the end of each process. If
the process is terminated before the Cash Management update, the update takes
place when you close the relevant reconciliation key. If the update also fails here,
you can transfer the data recorded separately individually. To do this, in the SAP
menu choose Periodic Processing Cash Management Transfer.
Utilities Industry (IS-U) Component
The system automatically determines the planning group in the contract account
when you transfer billing documents and then saves it in the corresponding line
items.
Insurance (FS-CD) Industry Component
The system automatically determines the planning group in the contract account
for the debit entry and then saves it in the corresponding line items.
Controlling
Purpose
This component enables data to be updated in Overhead Cost Controlling (COOM).
Features
Overhead Cost Controlling is updated automatically during the general ledger
update.
you can write a dummy FM account assignment to all existing documents that
were created before the integration with Funds Management.
FM Account Assignment Logic for Documents Created Automatically
To derive FM account assignments in documents created automatically, you
have to define FM derivation rules in Customizing. The system derives the
automatically assigned FM account assignments from the business transaction
data.
FM Account Assignment Logic for Documents Created Manually
In manual document entry, entry of requests, and posting of cash security
deposits, you can use derivation rules for determining default values. On the
processing screen, the commitment item, fund, funds center, and functional area
are ready for input. If you do not enter an FM account assignment, the system
derives these values automatically from the rules defined.
FM Account Assignment Logic for Doubtful Entries and Individual Value
Adjustments
In both business transactions, the posting data is provided with the FM account
assignment automatically. The system determines the FM account assignment
data using the derivation rules.
You can make individual value adjustments with tax adjustments using an
installation-specific function module defined for event 1750. The FM account
assignment is adjusted accordingly.
FM Account Assignments for Posting Deferred Revenues
The system transfers the FM account assignment from the original document to
the deferred revenue posting automatically. To use this function, you have to
include the structure IFKKFMOBJ in table FKKDEFREV.
Prerequisites
Funds Management
For information on activating the Funds Management (PSM-FM) component, see
Customizing for Public Sector Management under Funds Management
Government Prepare Funds Management Installation.
Contract Accounts Receivable and Payable
If you want to use Funds Management, you have to activate the business
function FI-CA Core, Funds Management (FICA_FM) in the Switch Framework.
When you activate the function, the system automatically writes the structures
SI_FKKFMOP and SI_FKKFMOPK with the FM table fields in the document
tables.
Make sure that you activate the EA-PS business function in the Activate
Business Functions Customizing activity.
Currently, you cannot use the account assignment element Grant of the
component Public Sector Management.
SAP also provides the following function modules as standard modules for the
enhancement:
If Funds Management is not active, the function modules are not processed.
In order to be able to process the FI-CA data in Funds Management, you have to
define rules for defining FM account assignments in Customizing for Contract
Accounts Receivable and Payable under Integration Funds Management
(PSM-FM). Contract Accounts Receivable and Payable uses the derivation
strategy of Funds Management (see Customizing for Funds Management
Government under Master Data Allocations to Account Assignments from
Other Components Define Account Assignment Derivation).
If you want to continue to use the derivation strategy FMCADERIVE in Contract
Accounts Receivable and Payable, you have to set the indicator Use Derivation
Strategy from Contract Accounts Receivable and Payable in the maintenance
view TFK_FMDERIVSTRAT. Call up the view directly using transaction SM30.
Note, however, that SAP no longer supports this derivation strategy.
If you want to use the Fund Accounting component, you have to:
Features
The figure depicts the functional relationships for updating document data
in Contract Accounts Receivable and Payable in Funds
Management, and Accounting.
246.
1.
Assigning an FM account assignment
The integration with Funds Management requires that each document item
in the document must be assigned to one FM account assignment.
For manual document entry, you can fill these FM account assignment
fields. If you do not make any entries here, the system automatically
assigns the FM account assignments you defined in the derivation rules
when you save the document. The derivation rules are especially required
for documents created automatically. In any one document, the amounts for
each FM account assignment must be cleared. For more information,
see Derivation Logic for Funds Management (PSM-FM).
247.
2.
Classification in FM categories and transaction classes
Documents are saved in the header and item tables of Contract Accounts
Receivable and Payable. The system classifies the business transactions
for Funds Management at the same time. The document is assigned to a
transaction class and each line item of the document receives an FM
category assignment. The FM category for the line item determines whether
You enter the FM account assignment directly into the line items when
you create a document manually.
If you have not made any manual FM account assignment entries, the
FM account assignments are assigned from the derivation rules you defined
in Customizing. This applies in particular to documents created
automatically.
If you do not make any specifications for FM account assignments when you
enter a document, the system uses the derivation steps you defined in
Customizing to determine the account assignment. You define the relationship
between source field entry values and automatic assignments to target fields for
each derivation step. Target fields are the FM account assignment
elements commitment item, funds center, fund and functional area. As well as
the FM account assignment elements, the following source fields can also be
used: Company Code, Main Transaction, Subtransaction, Division, Account
Assignment DeterminationCharacteristic and Period Key.
The derivation tool has various derivation step types (derivation rules, table
access, assignment, initialization, enhancement, function module) that you can
use to define a derivation strategy.
Special Features for Statistical Postings
When a statistical document is posted in FI-CA, this document is not relevant for
the general ledger or FM. The FM category is not filled in the business partner
item. However, the FM account assignments are filled according to the derivation
rules and inherited to the debit entry on clearing.
Example
The following example shows how you can outsort the update for revenues
from income tax and vehicle tax to different FM account assignments in the
IMG activity, Define FM Account Assignment Derivation with the derivation step
type Derivation Rule.
63.
...
250.
1.
You create the derivation rule Income Tax and choose the
source fields Main Transaction and Subtransaction, as well as the target
fields Funds Centerand Commitment Item.
251.
2.
Using the button Maintain Rule Entries, create a table in which you
define the values for the source and target fields. Define the following IF
THEN link:
Income tax derivation rule
Main
Transaction
Subtransaction
Invoice
Income tax
Revenue 1
Income tax
Invoice
Vehicle tax
Revenue 2
Vehicle tax
Invoice
Paid invoice
Clearing
Transfer
On account
Down payment
Clarification worklist
No update:
Transaction class
For further classification of a business transaction, each document is
automatically assigned to a transaction class. The system derives the transaction
class from the G/L accounts taking part. The transaction class is used for
clearings or clearing resets so as to determine the affected FM category for the
offsetting posting. The transaction class is saved in the header data of a
document.
In Contract Accounts Receivable and Payable, the following transaction classes
exist:
Invoice
Payment or clearing
Write-offs
Reversal
Integration
Customer enhancement update in Funds Management
If you post clearing payments for invoices with different fiscal years in Contract
Accounts Receivable and Payable, this is indicated in the line item with one of
the following FM categories:
Example: Overpayment/Underpayment
update in Accounting and not for that in Funds Management. This is why FM
categories have not been assigned to G/L items. In the totals table, the line items
for each reconciliation key are summarized according to FI and FM account
assignments and FM categories. In order to simplify the example, additional
summarization criteria have not been considered.
When updating document data (for each reconciliation key), the property tax
amounts are posted to FM account assignment Revenue 1 as revenues from the
invoices. The receivables for property tax of all business partners are posted to
a reconciliation account in Accounting, and revenues to the G/L
accountRevenue 1.
Several business partner items in one document
In a receivables document, you can enter several items for different
business transactions. Note however, that you have to enter a unique
FM account assignment in each business partner item. System
derivation of account assignments from the specifications for the
general ledger items is not supported. SAP delivers the standard
function module FKK_EVENT_FM_1102. If you have further
requirements, you can enhance event 1102 with a customer-specific
function module.
Totals-based invoice updates in Contract Accounts Receivable and
Payable
See also:
Example: Payment with Clearing
Example: Overpayment/Underpayment
Example: Payment On Account/Down Payment
To keep the graphic simple, data entry and update for a single document are
represented. This means that the amounts of the line items and the data records
of the totals table are the same.
See also:
Example: Overpayment/Underpayment
The following example illustrates payment postings and updates that have
different amounts to the items to be cleared. They are overpayments and
underpayments (partial payments).
Posting an overpayment or underpayment creates an amount split:
For simplification, the figure illustrates only one payment document. This means
that the amounts of the line items and the data records of the totals table are the
same.
See also:
Example: Posting Invoices
Example: Payment with Clearing
Example: Overpayment/Underpayment
control here. An availability control is possible only after the document data has
been passed on from Contract Accounts Receivable and Payable to Funds
Management. Also note that, the document data being transferred are totals
records. The availability control does not check line items it checks totals
records. This can lead to the tolerance limit being exceeded when the totals
records in Contract Accounts Receivable and Payable are passed on and as a
result the availability control prevents a posting in Funds Management. If this
should happen, you must change the Customizing settings for your availability
control accordingly and forward the respective reconciliation key again. (See
Customizing for Public Sector Management Funds Management Public
Services Administration Classic Budgeting Availability Control).
We recommend therefore, that you adjust the tolerance limits of
the availability control to the totals records to be transferred. In
particular, you should adjust the cycle (frequency) of document data
passed on for each reconciliation key to suit your organization. You
can forward the payment data frequently in order to keep the volume
amount for each reconciliation key small.
See also:
For more information on the availability control in Funds Management, see the
documentation for Funds Management, under Controlling Availability Control.
Value Type
CO Object Number
Transaction Currency
Funds Center
Commitment Item
Fund
Functional Area
Customer Dimension
Company Code
You can execute the program a number of times. New carryforward documents
are created each time you run the program, that is, if the corresponding
document data for the carryforward is found.
The carryforward document of the old fiscal year is written in period 13, in the
new fiscal year the carryforward document is written in the blank period .
Activities
To carryforward Contract Accounts Receivable and Payable documents, in the
SAP menu choose Accounting Public Sector Management Funds
Management Additional Functions Integration of Contract Accounts
Receivable and Payable (PSCD) Closing Preparations Carryforward
Documents from Contract Accounts Receivable and Payable.
Documents that you have posted in an old fiscal year but not yet
carried them forward to the new fiscal year distort the reporting
for Funds Management. We recommend therefore, that you start the
carryforward program a number of times throughout the year and not
just for a fiscal year change. In doing so you ensure correct results in
the information system of Funds Management.
See also:
For more information on fiscal year change, see the documentation for Funds
Management under Closing Operations.
Implementation Considerations
SAP Credit Management is part of SAP Financial Supply Chain Management.
For information about SAP Credit Management, see the documentation of SAP
Credit Management. For information about system configuration, see
the Configuration Guide of SAP Credit Management.
You can use Contract Accounts Receivable and Payable and SAP Credit
Management in a single or multiple system landscape without an XI server. This
means that you can connect an instance of Contract Accounts Receivable and
Payable directly with SAP Credit Management without using an XI server.
Contract Accounts Receivable and Payable and SAP Credit Management can be
running in the same system or in separate systems.
The prerequisite for this is as follows: You have installed enhancement package
5 for both Contract Accounts Receivable and Payable and SAP Credit
Management, and you activated the business function FSCM Functions
3 (FIN_FSCM_CCD_3). Activating a business function in Contract Accounts
Receivable and Payable is not a requirement.
You set up the connection between SAP Credit Management and Contract
Accounts Receivable and Payable by configuring the appropriate endpoints and
logical ports in SOA Manager.
Message exchange takes place using Web Services Reliable Messaging (WSRM), which guarantees the transfer of messages and monitors the correct
sequence of incoming messages.
Integration
If you use SAP Credit Management, the internal processes of Contract Accounts
Receivable and Payable do not use the score (creditworthiness) determined in
FI-CA; instead, they automatically access the score in SAP Credit Management.
You can display the SAP Credit Management score in the transaction Display
Business Partner's Creditworthiness (on the SAP Easy Access screen, choose
Account More Information Creditworthiness ).
You can influence the program flows in Contract Accounts Receivable and
Payable at certain events. For more information, see the configuration guide
forSAP Credit Management, in particular the sections for Contract Accounts
Receivable and Payable under Business Customizing Process Integration
with SAP Systems .
Features
The open items of business partners are managed in Contract Accounts
Receivable and Payable; the credit decisions take place in SAP Credit
Management. To ensure credit decisions are based on a current dataset, you
therefore have to transfer the credit exposure - the total of the open items to SAP Credit Management at regular intervals.
In the credit exposure update from Contract Accounts Receivable and Payable,
the total of all current open items for the business partner is always transferred
to SAP Credit Management. It is not a delta update.
You assign the open items to a credit segment using specific parameters in the
Implementation Guide for Contract Accounts Receivable and
Payable underIntegration Financial Supply Chain Management Credit
Management Assign Open Items to Credit Segments.
Activate Credit Management, you set the BillActive indicator, to enable the
transfer of the credit exposure for billable and billed items that have not yet
been invoiced from Billing in Contract Accounts Receivable and Payable to
SAP Credit Management.
Define Credit Exposure Category for External Billing Systems, you entered
external credit exposure categories (optional).
In Customizing for Credit Management under Credit Risk Monitoring Credit
Exposure Update Define Liability Categories in the activity Define Credit
Exposure Categories, you entered the required credit exposure categories; and
especially important, you entered the fixed values mentioned below.
Features
The credit exposure in SAP Credit Management is increased by not yet invoiced
items in Billing as well as open receivables of Contract Account Receivable and
Payable. The credit exposure is therefore the sum of all open items, billable
items and billed items of the business partner that are not yet invoiced.
NOTE
Contract Accounts Receivable and Payable transfers only those billable and
billed, but not yet invoiced, items that you have created for billing in postpaid
scenarios.
The exhaustion of the credit limit through credit exposure is one of the check
criteria during a credit check in SAP Credit Management.
In Contract Accounts Receivable and Payable, you can calculate the credit
exposure of a business partner and then transfer it to SAP Credit Management.
NOTE
If you are using the industry component Utilities, when updating the credit
exposure, you can exclude budget billing requests that lie in the future from the
calculation of the credit exposure.
To improve performance, you can calculate the credit exposure and transfer it to
SAP Credit Management in one step or in two separate steps. The procedure
described below is based on using two steps.
You can enter a percentage rate during the calculation of credit data. Using this
percentage rate, you can limit the update of credit data to that percentage of your
business partners that was not updated for the longest period of time.
EXAMPLE
If you enter a percentage of 25% for each run, and you execute four runs, after
four runs all of your business partners are updated.
In SAP Credit Management, you can designate business partners with
conspicuous behavior or critical business partners as business partners for
special attention. You can update these business partners independently of the
percentage rate selected and, if necessary, transfer them if they exist in the
business partner interval specified.
In SAP Credit Management, credit exposure categories allow you to classify the
reported credit exposures. The following fixed values apply for the following
credit exposures:
Credit exposure category 220 indicates billable items with status billable.
Credit Exposure Update for External Billing Systems
For credit exposure that you transfer from an external billing system, the situation
can arise that both the external billing system and Contract Accounts Receivable
and Payable report the credit exposure to SAP Credit Management. If you define
an external credit exposure category for the update of credit exposure from an
external billing system, then you can reset the external credit exposure as soon
as you transfer the credit exposure from Contract Accounts Receivable and
Payable to SAP Credit Management. If an external application already reported a
credit exposure with this external credit exposure category to SAP Credit
Management, the Transfer of Credit Data mass activity resets this external credit
exposure in SAP Credit Management and reports the credit exposure in the form
of billable items, billing documents or FI-CA posting documents using the credit
exposure categories of Contract Accounts Receivable and Payable to SAP Credit
CreditCommitmentNotification
CreditWorthinessCriticalPartiesQuery
Activities
Calculation of Credit Data in Contract Accounts Receivable and Payable
You calculate credit data in Contract Accounts Receivable and Payable using the
transaction Transfer of Credit Data.
1. On the SAP Easy Access screen, choose Periodic Processing
Forward Data to SAP Credit Management Transfer Credit Data .
2. Enter a run date and an ID that you can use to identify the run later.
3. Set the Update Credit Exposure and Payment Behavior
Summary indicator on the General Selections tab page, and enter a
percentage in thePercentage field.
4. Set the Update Business Partners for Special Attention indicator, if
applicable. If you do not set this indicator, then the business partners for
Open items
Payment methods
Payments
Promises to pay
Returns
Write-offs
The amount of the valuated credit exposure is the total of all open items,
including the interest for overdue items. For simulating the interest calculation for
overdue items, the system uses the interest rate you entered in Customizing.
The system updates the valuated credit exposure in the currency of the credit
segment.
The transfer of the key figures takes place using the mass activity Transfer Credit
Data (see the SAP Easy Access screen: Periodic Processing Forward Data to
SAP Credit Management). This mass activity uses the asynchronous service
CreditPaymentBehaviourSummaryNotification_Out of the
interfaceCreditPaymentBehaviourSummaryNotification.
If you make the system settings described above, this service transfers the
individual key figures from Contract Accounts Receivable and Payable to SAP
Credit Management. The system also fills the PropertyValuation of the service, in
which the characteristics of the individual key figures are filled.
The mass activity Transfer Credit Data forwards the payment behavior summary
for those business partners with negative payment behavior (such as dunning,
returns, or broken promises to pay). In event 4511, you can specify when and
how long the key figures for a business partner should be sent again.
You specify the time period over which a key figure is evaluated in Customizing
for Contract Accounts Receivable and Payable under Integration Financial
Supply Chain Management Credit Management Key Figures Specify
Evaluation Period for Key Figures. The value applies for all key figures that you
have stipulated for transfer, and especially for the following standard key figures:
COL (collections)
RET (returns)
WRO (write-offs)
If you do not make any entries, the system uses the default value of 30 days.
You can add your own data to these standard key figures for payment behavior
in event 4509.
In addition, in event 4510, you can also define your own key figures, fill them,
and then send them along with the standard key figures using the
PropertyValuation of the service to SAP Credit Management.
In SAP Credit Management there is a synchronous service
CreditManagementAccountERPPaymentBehaviourSummaryByDebtor
PartyQueryResponse_In. This service also contains the
PropertyValuation. If the service calls Contract Accounts Receivable
and Payable from SAP Credit Management, then the system
calculates the key figures to be transferred.
Note for the industry component Utilities Industry
You can determine an average budget billing amount for each business partner
and credit segment and transfer it to SAP Credit Management. This means that
the average budget billing amount is available in formulas in SAP Credit
Management as a decision criterion for credit decisions. The system calculates
the average budget billing amount as follows:
64.
...
252.
1.
For each budget billing plan, the system calculates the number of
days between the beginning and end of the budget billing period.
253.
2.
The total amount of the budget billing plan is divided by the
number of days. This provides the average budget billing amount per day
and budget billing plan.
254.
3.
You can determine the average budget billing amount per day for
each business partner by creating the total using the amounts determined in
step 2 for each budget billing plan.
65.
In your scenario, you do not use the key figure Sales. Therefore,
you define event 4600 such that the key figure Budget Billing Amount
per Dayis saved in the Sales field in SAP Credit Management for each
business partner.
You add it to the payment behavior summary in the SAP business
partner and save the key figure Budget Billing Amount per Day for
each business partner in this new field. You also have to define event
4600 accordingly here. You also have to enhance the SAP business
partner using theBusiness Data Toolset (BDT).
Activities
To calculate and transfer the payment behavior summary you also use the
transaction Transfer Credit Data from the SAP Easy Access screen
under Periodic Processing Forward Data to SAP Credit Management.
After the transfer, the valuated credit exposure appears in the business partner
master data of SAP Credit Management in the given credit segment on
thePayment Behavior Summary tab page in the Key Figures screen area in
the Amount field. In the business partner master data of SAP Credit
Management, the payment behavior summary is found in the credit segment
views on the KPI Payment History tab page in the Key Figures screen area.
Prerequisites
You have performed the following actions in Customizing for Contract Accounts
Receivable and Payable under Integration Financial Supply Chain
Management Credit Management in the activity:
Activate Credit Management, you set the BillActive indicator, to enable the
transfer of the credit exposure for billable and billed items that have not yet
been invoiced from Billing in Contract Accounts Receivable and Payable to
SAP Credit Management.
Define Credit Exposure Category for External Billing Systems, you entered
external credit exposure categories (optional).
In Customizing for Credit Management under Credit Risk Monitoring Credit
Exposure Update Define Liability Categories in the activity Define Credit
Exposure Categories, you entered the required credit exposure categories; and
especially important, you entered the fixed values mentioned below.
Features
The credit exposure in SAP Credit Management is increased by not yet invoiced
items in Billing as well as open receivables of Contract Account Receivable and
Payable. The credit exposure is therefore the sum of all open items, billable
items and billed items of the business partner that are not yet invoiced.
NOTE
Contract Accounts Receivable and Payable transfers only those billable and
billed, but not yet invoiced, items that you have created for billing in postpaid
scenarios.
The exhaustion of the credit limit through credit exposure is one of the check
criteria during a credit check in SAP Credit Management.
In Contract Accounts Receivable and Payable, you can calculate the credit
exposure of a business partner and then transfer it to SAP Credit Management.
NOTE
If you are using the industry component Utilities, when updating the credit
exposure, you can exclude budget billing requests that lie in the future from the
calculation of the credit exposure.
To improve performance, you can calculate the credit exposure and transfer it to
SAP Credit Management in one step or in two separate steps. The procedure
described below is based on using two steps.
You can enter a percentage rate during the calculation of credit data. Using this
percentage rate, you can limit the update of credit data to that percentage of your
business partners that was not updated for the longest period of time.
EXAMPLE
If you enter a percentage of 25% for each run, and you execute four runs, after
four runs all of your business partners are updated.
In SAP Credit Management, you can designate business partners with
conspicuous behavior or critical business partners as business partners for
special attention. You can update these business partners independently of the
percentage rate selected and, if necessary, transfer them if they exist in the
business partner interval specified.
In SAP Credit Management, credit exposure categories allow you to classify the
reported credit exposures. The following fixed values apply for the following
credit exposures:
Credit exposure category 220 indicates billable items with status billable.
Credit Exposure Update for External Billing Systems
For credit exposure that you transfer from an external billing system, the situation
can arise that both the external billing system and Contract Accounts Receivable
and Payable report the credit exposure to SAP Credit Management. If you define
an external credit exposure category for the update of credit exposure from an
external billing system, then you can reset the external credit exposure as soon
as you transfer the credit exposure from Contract Accounts Receivable and
Payable to SAP Credit Management. If an external application already reported a
credit exposure with this external credit exposure category to SAP Credit
Management, the Transfer of Credit Data mass activity resets this external credit
exposure in SAP Credit Management and reports the credit exposure in the form
of billable items, billing documents or FI-CA posting documents using the credit
exposure categories of Contract Accounts Receivable and Payable to SAP Credit
Management. Using this procedure enables you to avoid managing duplicate
credit exposures.
Credit Exposure Update for Cash Security Deposits
Contract Accounts Receivable and Payable reports cash security deposits as
secured credit exposure to SAP Credit Management.
Options for Intervening in Events
Event In this event, you can:
4501 Filter the open items and thereby exclude certain items from the credit
exposure update
4502 For an open item of FI-CA, override credit exposure category 200
4503 Exclude certain customer groups from the calculation and transfer of
credit data
EXAMPLE
You do not want to transfer the credit data of customers with whom you
have agreed on automatic debit.
4609 Change credit data and transfer customer-defined fields for the credit
exposure update to the XI interface
4512 For billable and billed items, specify a credit exposure category that
differs from the fixed value mentioned above
XI Interfaces
The following interfaces are used for transferring the data:
CreditCommitmentNotification
CreditWorthinessCriticalPartiesQuery
Activities
Calculation of Credit Data in Contract Accounts Receivable and Payable
You calculate credit data in Contract Accounts Receivable and Payable using the
transaction Transfer of Credit Data.
1. On the SAP Easy Access screen, choose Periodic Processing
Forward Data to SAP Credit Management Transfer Credit Data .
2. Enter a run date and an ID that you can use to identify the run later.
3. Set the Update Credit Exposure and Payment Behavior
Summary indicator on the General Selections tab page, and enter a
percentage in thePercentage field.
4. Set the Update Business Partners for Special Attention indicator, if
applicable. If you do not set this indicator, then the business partners for
special attention in Contract Accounts Receivable and Payable
are not updated.
5. Set the Transfer to Credit Management indicator, if applicable. If you do
not set this indicator, then you have to execute the transaction again (see
below).
6. If you use the industry component Utilities, enter an appropriate value in
the Additional Days for Budget Billing Requests field if you want to exclude
budget billing requests that are in the future from the credit exposure.
7. Schedule the program run.
For detailed information about scheduling program runs, see Functions for
Scheduling Program Runs.
Transfer of Credit Data to SAP Credit Management
After you have calculated the credit data in Contract Accounts Receivable and
Payable, you can also transfer the data to SAP Credit Management using the
transaction Transfer of Credit Data. Proceed as described in the section on
calculating the credit data. However, set the Transfer of Credit Data indicator in
the Transfer to Credit Management group box on the General Selections tab
page, and schedule the run.
After the transfer, the credit exposure appears in the business partner master
data of SAP Credit Management. The system adds the credit exposure amount
from Contract Accounts Receivable and Payable to the credit exposure of the
relevant credit segment of the business partner.
Calculating and Transferring Payment Behavior Summaries
Use
Using payment behavior summaries, you can calculate the creditworthiness
score and the credit limit in SAP Credit Management.
The payment behavior summaries of business partners are determined in
Contract Accounts Receivable and Payable. In the same way, you can determine
the credit exposure including an interest calculation.
Prerequisites
You specified the interest rate for the valuated credit exposure in Customizing for
Contract Accounts Receivable and Payable under Integration Financial Supply
Chain Management Credit Management Define Specifications for Credit
Management.
If you want to transfer individual payment behavior summaries to SAP Credit
Management, you made settings in Customizing for Contract Accounts
Receivable and Payable under Integration Financial Supply Chain
Management Credit Management Key Figures.
Features
In the standard system, payment behavior summaries contain the valuated credit
exposure, as well as information on the following:
Open items
Payment methods
Payments
Promises to pay
Returns
Write-offs
The amount of the valuated credit exposure is the total of all open items,
including the interest for overdue items. For simulating the interest calculation for
overdue items, the system uses the interest rate you entered in Customizing.
The system updates the valuated credit exposure in the currency of the credit
segment.
The transfer of the key figures takes place using the mass activity Transfer Credit
Data (see the SAP Easy Access screen: Periodic Processing Forward Data to
SAP Credit Management). This mass activity uses the asynchronous service
CreditPaymentBehaviourSummaryNotification_Out of the
interfaceCreditPaymentBehaviourSummaryNotification.
If you make the system settings described above, this service transfers the
individual key figures from Contract Accounts Receivable and Payable to SAP
Credit Management. The system also fills the PropertyValuation of the service, in
which the characteristics of the individual key figures are filled.
The mass activity Transfer Credit Data forwards the payment behavior summary
for those business partners with negative payment behavior (such as dunning,
returns, or broken promises to pay). In event 4511, you can specify when and
how long the key figures for a business partner should be sent again.
You specify the time period over which a key figure is evaluated in Customizing
for Contract Accounts Receivable and Payable under Integration Financial
Supply Chain Management Credit Management Key Figures Specify
Evaluation Period for Key Figures. The value applies for all key figures that you
have stipulated for transfer, and especially for the following standard key figures:
COL (collections)
RET (returns)
WRO (write-offs)
If you do not make any entries, the system uses the default value of 30 days.
You can add your own data to these standard key figures for payment behavior
in event 4509.
In addition, in event 4510, you can also define your own key figures, fill them,
and then send them along with the standard key figures using the
PropertyValuation of the service to SAP Credit Management.
67.
Activities
To calculate and transfer the payment behavior summary you also use the
transaction Transfer Credit Data from the SAP Easy Access screen
under Periodic Processing Forward Data to SAP Credit Management.
After the transfer, the valuated credit exposure appears in the business partner
master data of SAP Credit Management in the given credit segment on
thePayment Behavior Summary tab page in the Key Figures screen area in
the Amount field. In the business partner master data of SAP Credit
Management, the payment behavior summary is found in the credit segment
views on the KPI Payment History tab page in the Key Figures screen area.
Replication of Creditworthiness
Use
The creditworthiness managed in Contract Accounts Receivable and Payable is
forwarded to SAP Credit Management and can contribute to the score managed
there. For internal processes such as dunning and returns processing in Contract
Accounts Receivable and Payable to be able to react to the score from SAP
Credit Management, you also have to transfer the score to Contract Accounts
Receivable and Payable.
Features
Transfer of FI-CA Creditworthiness to SAP Credit Management
You transfer the FI-CA creditworthiness to SAP Credit Management using the
mass activity Replicate Creditworthiness.
Monthly Comparison of FI-CA Creditworthiness
In Customizing for Contract Accounts Receivable and Payable, you can enter a
monthly weighting for creditworthiness (under Business
Transactions Dunning Define Time-Dependent Creditworthiness
Weightings). If the creditworthiness of a business partner changes due to this
changed weighting factor at the changeover to a new month, Contract Accounts
Receivable and Payable does not record the fact that a change took place. To
preclude the necessity of replicating the creditworthiness of all business partners
to SAP Credit Management, you use the mass activity Compare Replicated
Score to identify those business partners where their creditworthiness has
changed due to the monthly weighting. The mass activity marks the business
partners where there was a change to their creditworthiness. Then in the mass
activity Replication of Creditworthiness, you transfer only the changed values to
SAP Credit Management (Only Changed Scoresindicator).
Transfer of Score to Contract Accounts Receivable and Payable
When you transfer the FI-CA creditworthiness to SAP Credit Management using
the transaction Replication of Creditworthiness, the updated score in SAP Credit
Management is automatically returned to Contract Accounts Receivable and
Payable. This means that you can only replicate the score in Contract Accounts
Receivable and Payable by performing the mass activity Replication of
Creditworthiness.
Settings for Calculating Creditworthiness in SAP Credit Management
SAP Credit Management saves the FI-CA creditworthiness as external credit
information in the rating procedure FICA. For the configuration, see the
description in the Configuration Guide for SAP Credit Management in the
section Making Settings for Contract Accounts Receivable and Payable.
In Contract Accounts Receivable and Payable, the best
creditworthiness has the value 0. You also have to apply this logic for
the calculation of the score in SAP Credit Management.
The formula for calculating the score in SAP Credit Management must only
contain the FI-CA creditworthiness as additive argument in the following form:
Score = FI-CA creditworthiness + further items from SAP Credit
Management
This enables the score in SAP Credit Managementto be simulated at any time in
FI-CA using the current FI-CA creditworthiness, even if the score has not been
replicated from SAP Credit Management yet. This means that when you change
the FI-CA creditworthiness, for example, due to a dunning activity in FI-CA, you
can directly calculate the score in SAP Credit Management.
Note that if you do not follow this procedure, the creditworthiness
in FI-CA and the score in SAP Credit Management will not be
calculated correctly.
XI Interfaces Used
The following interfaces are used:
FICARatingReplicateQuery
FICARatingReplicateResponse
Activities
Monthly Comparison of FI-CA Creditworthiness
68.
...
258.
1.
To identify business partners whose creditworthiness has changed
after the end of the month, on the SAP Easy Access screen,
choose Periodic Processing Forward Data to SAP Credit
Management Compare Credit Score.
259.
2.
Enter a date and an ID that you can use to identify the run later.
260.
3.
Restrict the quantity of business partners to be considered.
261.
4.
Schedule the program run.
For more information about scheduling program runs, see the section
Functions for Scheduling Program Runs.
Transfer of FI-CA Creditworthiness to SAP Credit Management
69.
...
70.
...
71.
...
262.
1.
To transfer the FI-CA creditworthiness to SAP Credit
Management and, at the same time, replicate the SAP Credit
Management score in FI-CA, on the SAP Easy Access screen,
choose Periodic Processing Forward Data to SAP Credit
Management Replicate Creditworthiness.
263.
2.
Enter a date and an ID that you can use to identify the run later.
264.
3.
Restrict the business partners to those for whom you want to
replicate their creditworthiness. By setting the indicator Only Changed
Scores, you can restrict the transfer to SAP Credit Management to those
business partners whose creditworthiness has changed since the last
transfer in FI-CA. In the same way, setting this indicator for the transfer of
the scores from SAP Credit Management to FI-CA has the effect that only
those score values are replicated where the FI-CA creditworthiness has
changed.
265.
4.
Commitment Query
Use
Support for the commitment query of SAP Credit Management in Contract
Accounts Receivable and Payable (FI-CA).
Features
In SAP Credit Management, for each check step in a credit check, you can
specify whether the current commitment is queried in the connected systems.
This means that independently of the periodic credit exposure transfer, in a credit
check you can determine the current credit exposure at any time.
The XI interface CreditCommitmentQuery is used here.
Activities
To support the commitment query, you have to define a system group for the
corresponding check step. See the description in the Configuration Guide
for SAP Credit Management in the section Making Settings for Contract Accounts
Receivable and Payable.
Credit Check
Use
In Contract Accounts Receivable and Payable, you can carry out a credit check
for a business partner in SAP Credit Management.
Prerequisites
Define event 4505. The event determines the order value to be checked for the
credit check.
To perform the credit check, call the function module
FKK_CR_PERFORM_CREDIT_CHECK.
Using the order value determined, SAP Credit Management performs the credit
check and returns the result. This is then available in Contract Accounts
Receivable and Payable.
72.
1.
2.
5.
3.
4.
5.
6.
i.
Implement a workflow that starts after
the move-in processing.
ii.
Connect the workflow with the
method CheckCredit of the BOR object ISUPARNTER.
In detail, the credit check runs as follows:
...
i.
The workflow is processed after the
move-in processing. This workflow calls the
method CheckCredit.
ii.
The method CheckCredit calls the
function module FKK_CR_PERFORM_CREDIT_CHECK.
iii.
The function module
FKK_CR_PERFORM_CREDIT_CHECK calls event 4505. The
event is defined such that a calculation is run to determine the
order value for the credit check.
iv.
SAP Credit Managementthen runs a
credit check and returns the result.
You can define the cases in which SAP Credit Management reports the changes
to Contract Accounts Receivable and Payable in Customizing.
As standard, the system updates the trigger for changes to the following master
data:
Score
Risk class
Block reason
If you want to transfer further triggers for own change types to the XI interface,
you have to define event 4603. For more information, see the configuration guide
forSAP Credit Management, the section Settings in Contract Accounts
Receivable and Payable from 6.00, EHP 2005.1.
If the credit limit of a business partner has changed in SAP Credit
Management, this should trigger a change to the master data
in Contract Accounts Receivable and Payable.
Replication of Master Data
You can process these triggers using the mass activity Prepare Master Data
Changes from External System. The current master data from SAP Credit
Management is replicated in Contract Accounts Receivable and Payable so that
it is then available for the determination of the master data change in Contract
Accounts Receivable and Payable.
As standard, the following data is saved in the replication of the master data:
Score
Risk class
If you need further master data from SAP Credit Management(for example, credit
group) for the determination of the master data change in Contract Accounts
Receivable and Payable, you can add this data in event 4602. You must also
define event 4508. For more information, see the configuration guide for SAP
Credit Management, the section Settings in Contract Accounts Receivable and
Payable from 6.00, EHP 2005.1.
Change to the Master Data in Contract Accounts Receivable and Payable
Using the mass activity Process Master Data Changes from External System,
you can change the master data of the business partner (for example, contract
account) in Contract Accounts Receivable and Payable based on the replicated
master data.
For changes to contract accounts, you can use event 4506.
CreditWorthinessChangeInformation
FICARatingReplicateQuery
FICARatingReplicateResponse
Activities
73.
...
266.
1.
To process the triggers from SAP Credit Managementand run the
replication of the master data, in the SAP menu choose Periodic
Processing Forward Data to SAP Credit Management Prepare Master
Data Changes from External System.
267.
2.
To change the master data in Contract Accounts Receivable and
Payable, in the SAP menu, choose Periodic Processing Forward Data to
SAP Credit Management Process Master Data Changes from External
System.
Implementation Considerations
Dispute Management in Contract Accounts Receivable and Payable uses
technical components of SAP Dispute Management (FIN-FSCM-DM). If you use
Contract Accounts Receivable and Payable in connection with an industry
component with Release 4.72, Contract Accounts Receivable and Payable and
dispute case processing are in different systems.
If you use Contract Accounts Receivable and Payable in connection with an
industry component with Release 6.00, you can run Contract Accounts
Receivable and Payable and dispute case processing in different systems or in
the same system.
For more information about the multiple system scenario, see the configuration
guide for SAP Dispute Management (FIN-FSCM-DM).
Integration
Dispute Management in Contract Accounts Receivable and Payable consists of
the following subareas:
Component Required
Release 3.0
Features
It is always a customer that initiates the creation of a dispute case in Contract
Accounts Receivable and Payable. Based on a customer message, you can
create a dispute case by collecting all of the data and information required for
processing the case. This information can already be available in Contract
Accounts Receivable and Payable, or you may have to enter additional
information for the dispute case.
As coordinator for dispute cases, you can structure your investigations, and
distribute and manage the results for all parties involved in your company.
Clerks can include other colleagues and departments in the resolution of a case
directly in Contract Accounts Receivable and Payable, and see the current status
of the dispute case. Due to the automatic update of dispute cases, the processor
of a dispute case can get information about the current processing status at any
time and react quickly.
For the component SAP Dispute Management, SAP delivers two sample roles:
Technical Name
Description
Holder
SAP_FIN_FSCM_DM_USER
FSCM Dispute
Management
Processor
Processor for
SAP Dispute
Management
Administrator for
SAP Dispute
Management
You can also create dispute cases in SAP Customer Relationship Management
in the Interaction Center for Financial Customer Care. You can replicate these
dispute cases to Contract Accounts Receivable and Payable.
Conversely, you can replicate dispute cases that were created in Contract
Accounts Receivable and Payable in SAP Customer Relationship Management.
In that case, the dispute cases are processed in SAP Customer Relationship
Management and not in Contract Accounts Receivable and Payable.
For more information, see the SAP Library for SAP Customer Relationship
Management on the SAP Help Portal at http://help.sap.com SAP
Business Suite SAP Customer Relationship Management Application
Help SAP Customer Relationship Management SAP CRM for Industries in
the documentation for your industry component under Functions in the
Interaction Center for Financial Customer Care.
Example
In customer service, you frequently receive queries that relate to accounting
transactions, such as invoices and credits. Customers can
Query the amount of an invoice, even if this invoice has already been
cleared in the accounting system
These cases need to be resolved by your having to find payments paid and
missing payments, and locate missing credits.
Dispute Case
Definition
Complaint of a business partner as a central management object in SAP Dispute
Management
Use
The dispute case contains attributes such as the amount, data for the status of
processing and for categorizing the complaint; and in the record, a list of the
related objects to which the case refers (for example, document, invoice,
business partner, contract, contract account).
The dispute case provides access to all information that you need to process
receivables-related and payment-related dispute cases.
Structure
For a general description of the structure of cases, see The Called Case
Screen in the documentation for Case Management. Note the following special
features of SAP Dispute Management:
Attributes
The dispute case has a series of specific attributes, including amount fields.
Process Route
The process route is not used in the component SAP Dispute Management.
Linked Objects
The Customizing settings in your dispute system determine the structure of the
case record that contains the linked objects.
Since the process integration with Contract Accounts Receivable and
Payable automatically adds, changes, or deletes links to SAP business objects in
the case record, part of the case record must have a fixed predefined structure.
This part of the case record has the following structure:
The links to the disputed documents are located under the structure
node Documents. These can be invoices or credits.
In this part of the case record, links to objects are added, changed, or deleted
exclusively by the process integration. You cannot change this part of the case
record manually. However, the case record can contain any number of additional
customer-specific structure nodes, under which you can add links to objects
manually.
Processing in External Components
When you create dispute cases in FI-CA, you can specify that the dispute cases
are not processed in SAP Dispute Management, but are processed instead in an
external component. You can create dispute cases in the external component
and send them to FI-CA. 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.
To access this report, choose Dispute Management Periodic Processing in
Dispute Case Processing Transfer of Dispute Cases.
The dispute cases are processed in the external component. (This processing
includes changes to amounts, addition of further documents, changes of
attributes or status.)
As an example, SAP provides integration with the CRM dispute of SAP Customer
Relationship Management 7.0 as an external component.
Processing by an external component requires separate 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 these 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
Processinggroup box.
Meaning
Total Amount
Disputed Amount
Amount Credited
Amount Paid
Process Flow
74.
...
268.
1.
Create a dispute case and assign the case to a processor
Dispute cases can be document-related or independent of documents; they
can refer to open receivables and paid invoices. In Contract Accounts
Receivable and Payable, dispute cases are usually initiated by customers
and therefore are not created automatically (for example, as a result of
underpayments). They contain attributes, such as the reason for the
complaint, the priority, the disputed amount, the clerk responsible for
resolution, and contact data of the business partner. According to their
attributes, the dispute cases are differentiated by the following case types:
A001
Incorrect Invoice
A002
Incorrect Credit
A003
Missing Credit
B001
Missing Payment
When you create a dispute case, you only have to enter the business
partner, internal dispute type, and amount.
When you create dispute cases in FI-CA, you can specify that the dispute
cases are not processed in SAP Dispute Management, but are processed
instead in an external component.
269.
2.
Process the dispute case
270.
Dispute Case
Here you can search for dispute cases in SAP Dispute Management. The
creation of dispute cases from SAP Dispute Management is not supported.
My Dispute Cases
By double-clicking on this folder, you can display an overview of those
cases where you are entered as the processor, coordinator, or person
responsible.
Depending on the Customizing settings of your system, the overview tree for
dispute case processing may contain other folders that supplement or replace
the above-mentioned folders.
Correspondence
Use
You can create and send any correcspondence necessary in dispute case
processing.
Integration
The technical basis is the Post Processing Framework. With this component, you
can have follow-on activities (actions), such as the creation of correspondence,
triggered and processed automatically based on conditions. You can define and
configure these actions in accordance with your requirements. The actions are
grouped in an action profile that is assigned to a case type.
The correspondence is actually sent via SAPconnect. Via Tools Business
Communication Communication SAPconnect, you can use an
administration function to monitor the send transactions.
Prerequisites
You have made all settings required in Customizing for SAP Dispute
Management under Correspondence.
If you want to store correspondence that you create and send in an optical
archive, you have made all of the settings required in Customizing for SAP
NetWeaver Application Server under Basis Services ArchiveLink. For more
information, see the Implementation Guide for SAP Dispute
Management under Dispute Case Processing Correspondence Basic
Customizing for ArchiveLink.
You have made all of the settings required for the external communication
interface SAPconnect.
Features
You have the following options for your correspondence:
Under Element Types and Case Records Model Create Element Type,
you have created the element types for storing documents via
SCMG_SP_DOCUMENT.
Under Element Types and Case Records Model Create and Process
Case Records Model, you have described the structure of the case records
model.
In order to be able to include documents in the dispute case via a work
item, here you have defined a model node with a number of instances that
permits the element types for documents and has an anchor with the value
#INITIAL#.
Under Attribute Profile Create Attribute Profile, you have set the
indicator Required for the case attribute PROCESSOR. The system checks
this setting when you enter a new processor.
independent of the existence of open items and are not tied to the clearing or
partial clearing of open items.
You can also post invoice-related credits (invoice corrections) or replacement
receivables with the transaction Post Document, for example, if you reverse an
incorrect invoice and then post the corrected invoice.
You can also call up the transactions for reversals and write-offs in the case
display in the dispute system. To do this, the dispute system calls up the
corresponding transaction in the FI-CA system. You can then complete the data
and post the document.
You should only call up the transactions in the display of the
dispute cases in the dispute system, since, during the update of the
amounts (for example, Amount Written Off), the case could be
changed again itself. This means that locked dispute cases could
therefore not be updated initially, and you would have to subsequently
post the corresponding IDoc manually.
If you reset clearing for a payment, and a payment from a payment lot has
increased the Payments Received amount in a dispute case, when you reset
clearing for this payment, the system reduces the amount by this payment
amount.
When you reverse a document, the system checks whether the document is
included in dispute cases. If this is the case, the system reacts as follows:
When you reverse an invoice for which there is an open dispute case, in
Dispute Case Processing, the Reversed Amount of the dispute case is
updated in accordance with the transaction in Contract Accounts
Receivable and Payable.
When you reverse a write-off that has increased the Amount Written Off,
this amount field is reduced by the amount of the write-off.
In each related dispute case, the system enters the total amount in the
field Amount Reversed.
Activities
To post an invoice-related credit:
76.
...
277.
1.
From the SAP menu, choose Document Post.
278.
2.
On the initial screen of the transaction, enter the document
number to which the correction/replacement receivable refers. You can also
enter such postings with reference to a dispute case. In this case, you have
to enter the case ID (the external identification of the case). The possible
entries show the cases for the business partner; you can select a case from
this list.
In a separate system
If you run SAP GTS and Contract Accounts Receivable and Payable in the same
system and client, you do not have to replicate the business partner data to SAP
GTS, that is, the data does not have to be retained in duplicate.
If you run SAP GTS and Contract Accounts Receivable and Payable in different
clients or systems, the business partner data is replicated to SAP GTS by means
of an ALE scenario. You also have to configure the ALE standard scenario for
master data distribution and check it periodically. The first time you use SAP
GTS you have to carry out a legacy data transfer. This means that you have to
transmit all business partners to SAP GTS and check them there. You also
communicate new business partners or changes to business partners via this
scenario. For more information, see SAP Note 831743.
The business partners created in SAP GTS receive the status Not Checked. The
comparison with the sanctioned party lists takes place through a comparison of
the addresses. Depending on the result of the check, a business partner receives
the status Locked or Released.
SAP customers and vendors that you always access, for example, from Financial
Accounting (FI), are always transferred to SAP GTS and created there separately
as an SAP business partner with a GTS role. SAP GTS saves some additional
data for each business partner with this role.
Contract Accounts Receivable and Payable supports the following checks:
FKK_0350_COLL_CASE_NEW
If this function module is assigned to the dunning activity, for each
dunning notice the dunning activity run creates a new collection case
in the component Debt Recovery Management (FIN-FSCM-DR).
The function module does not create the collection cases itself; it runs
through checks and saves the data in a table that the system needs
for creating a collection case. To actually create the collection cases,
you have to call the transaction FPDM01 Create Collection Cases
after Dunning Run (step 2).
FKK_0350_COLL_CASE_ADD_OR_NEW
This function module checks whether collection cases already to
which the dunning items can be added exist for the business partner
and if so, adds them to the cases. If there is no suitable collection
case, the dunning activity run calls the function module
FKK_0350_COLL_CASE_NEW; this collects the data for the creation
of a new collection case. In this case also the collection case is not
actually created until you call transaction FPDM01 Create Collection
Cases after Dunning Run (step 2).
280.
2.
To create new collection cases in the component Debt Recovery
Management (FIN-FSCM-DR) call transaction FPDM01 Create Collection
Cases after Dunning Run in Contract Accounts Receivable and Payable.
At event 9053, when you create a collection case you can add or
change attribute values such as the priority of a collection case
dependent on the dunning level.
To update the relevant data in the collection case when you reverse a
dunning notice, define the function module
FKK_0395_COLL_CASE_REVERSE for event 0395. If the collection
case has not been created yet, the module ensures that the entry is
deleted in the dunning activity table. Otherwise the item is removed
from the collection case provided the collection cases is not locked
against changes in the item list.
Creating Collection Cases without the Dunning Progarm
78.
...
79.
...
281.
1.
Call transaction FP03EC Submit Items for Internal Collection.
282.
2.
Enter the criteria that you want to use to select the items to be
submitted.
283.
3.
Choose Continue.
The program selects all open items that correspond to the selection criteria
and issues them in a list.
284.
4.
To submit an item, select it and then choose the pushbutton
Submit.
285.
5.
You can then decide, per dialog, whether you want to create a
new collection case or if a collection case already exists for the business
partner add the items to an existing collection case.
286.
6.
To recall an item, selet the item and choose
Recall.
Provided the collection case was not locked against changes in the
component Debt Recovery Management, the program recalls the
submission of the item for internal collection. The next time you call
transaction FP03EC Submit Items for Internal Collection, the item appears
in the list as an item to be submitted.
When you recall an item from internal collection, all subitems of a
line item are recalled.
Result
IN both cases the system either creates new collection cases in the
component Debt Recovery Management (FIN-FSCM-DR) or adds the items
submitted to internal collection to existing collection cases.
If an item has been cleared in Contract Accounts Receivable and
Payable, for example, by pazment, reversal, or write-off, the collection
case is updated in the component Debt Recovery Management (FINFSCM-DR) and this item is no longer displayed.
Invoicing documents are created. These save the information for the
invoice and are the basis for the physical invoice printing.
Purpose
Invoicing in Contract Accounts Receivable and Payable makes it possible to
create convergent invoices that you send to your customers, and posts the
invoice amounts in Contract Accounts Receivable and Payable (FI-CA).
Invoicing in Contract Accounts Receivable and Payable is adjusted to meet the
requirements of the application that uses FI-CA (for example, industry
componentTelecommunications).
Together with Billing in Contract Accounts Receivable and Payable, it offers a
comprehensive back end solution for the mass processing of invoice creation
based on billable items.
Integration
In conjunction with Billing in Contract Accounts Receivable and Payable,
Invoicing in Contract Accounts Receivable and Payable forms SAP Convergent
Invoicing.
Invoicing in Contract Accounts Receivable and Payable merges billing
information from SAP billing systems, such as Billing in Accounts Receivable and
Payable, and billing systems from other providers into customer invoices.
You can integrate billing from the Sales and Distribution (SD) component directly
into Invoicing in Contract Accounts Receivable and Payable. You can connect
external billing systems or CRM Billing to FI-CA using a BAPI/IDoc interface.
Using the print workbench, you can create invoices (or invoice raw data).
Performing Invoicing
With the transaction Invoicing in Contract Accounts Receivable and Payable
(Individual Creation), you can create an invoicing document for individual
business partners or for a contract account.
The function is also available as a parallel mass run for large numbers of
business partners or contract accounts to be invoiced.
Procedure
Analysis of Invoicing Orders
You can analyze invoicing orders from the SAP Easy Access screen by
choosing Invoicing Monitoring Invoicing Orders . You can process
invoicing orders directly in the output list of the program. For more information,
see the program documentation.
Individual Invoicing: Update Run
1. To perform individual invoicing, on the SAP Easy Access screen,
choose Invoicing Dialog Processing Create Invoicing Document .
2. Enter an invoicing process and the required contract partner or contract
account. If you specify an invoicing process that also handles collective
bills, the system prompts you in a dialog box to enter a due period (Due By).
3. Run the program.
4. On the following screen, select the source documents to be invoiced. To
display a document, click on the document number.
Individual Invoicing: Simulation
1. On the SAP Easy Access screen, choose Invoicing Dialog
Processing Create Invoicing Document .
2. Enter an invoicing process and the contract partner or contract account.
3. Set the Simulation Run indicator. By setting the corresponding indicator,
you can determine whether the simulation is with or without an invoicing
order, and whether the invoicing document is saved.
4. Run the program.
In the simulation run, individual invoicing only creates simulated invoicing
documents; it does not post documents in FI-CA.
If you select Simulation Run and Without Invoicing Order on the initial screen,
instead of the selection screen for source documents, a dialog box appears
where you can enter source documents and their category.
Expert Mode
If you start individual invoicing in expert mode using the pushbutton
Expert
Mode instead of the pushbutton
(Execute), you can use the following
processing functions:
After you have selected the source documents to be invoiced, you can
also group the documents by invoicing unit.
For each invoicing unit, you can activate or deactivate specific invoicing
functions.
In addition, you can also invoice source documents before they have reached
their target date for invoicing.
Mass Invoicing
To create invoicing documents for a large number of business partners or
contract accounts in a parallel run, from the SAP Easy Access menu, choose
Invoicing Parallel Processing Create Invoicing Document . As for
individual invoicing, you can also start the parallel run in simulation mode.
By choosing the pushbutton Further Selections in the application toolbar, you can
add additional selection criteria. You can also restrict the runtime of the mass
run. This has the effect that the run ends if the date and time specified are
exceeded. Contract accounts considered up to this point are processed
completely. You can process contract accounts that were not processed because
the runtime ended by starting the run again.
This is the basis for creating the correspondence for the customers
concerned.
Invoicing Reversal
header of the billing document, the system sets the Invoicing Order
Deleted indicator.
If the billing document was already invoiced and postings were already made in
FI-CA, the billing reversal reverses the billing document. The original invoicing
order no longer exists, since the billing document was already invoiced. The
system also creates a reversal billing document.
For clearing the postings in FI-CA, the reversal billing document contains
offsetting items for clearing the items to be reversed. At the same time, the
system creates a new invoicing order, so that the reversal billing document and
the related offsetting items can be posted.
NOTE
The reversal billing document and the reversed billing document are linked to
each other.
You cannot reverse simulated billing documents.
For more information on reversal of billing documents, see Special Features for
Reversal of Billing Documents.
Activities
1. To reverse a billing document, on the SAP Easy Access screen, choose
Invoicing Dialog Processing Reverse Billing Document .
2. To select the document to be reversed, either enter the document number
directly, or enter the business partner and contract account.
3. Specify a reversal reason.
4. Run the program. To do so, choose the
(Execute (F8)) pushbutton.
5. In the dialog box that appears, select the documents you want and
choose Continue.
In the dialog box that appears, the system displays the status of the reversal.
Choose the Log pushbutton to see more information about the reversal
transaction.
Invoice Printing
Purpose
Based on correspondence containers, the print workbench creates invoices or
invoice raw data according to the application form defined for the invoicing
process in Customizing.
Prerequisites
You use the correspondence tool and the print workbench and have made the
system settings described under Making System Settings for Invoice Printing.
Process Flow
Invoicing in Contract Accounts Receivable and Payable uses the
correspondence type 0042.
The invoicing documents are printed as for other print processes in Contract
Accounts Receivable and Payable with the Print Workbench using
Correspondence Printing (transaction FPCOPARA).
The correspondence printing is triggered by the correspondence containers.
These contain the information required for printing (such as application form,
recipient, address numbers, print language) and control the printout.
When you create invoicing documents, Invoicing in Contract Accounts
Receivable and Payable creates a correspondence container for event 2685:
For every posted invoicing document, provided that it does not have a
print lock
If an invoicing document is not to be printed, you can put a print lock on it in
event 2645 (field PRINTLOCK in the invoicing document header).
Displaying Invoices
With the invoicing document, you can also display the simulation of the
invoice printing and the invoice preview. However, the print date and
customer-defined fields are not updated. Clarification in Invoicing
Purpose
When creating bills and processing billing documents situations can occur that
demand the termination of automatic processing and that postprocessing be
performed manually in dialog by the agent. The clarification in invoicing in the
contract account receivable and payable helps you to recognize these exception
situations and to process them successfully.
The invoicing clarification covers the following processes and functions:
Source Documents
Invoice Documents
Contract Account
Error Messages
Simulate an invoice
You can also get an overview of the reversal history of the invoicing document.
The tab page shows which invoicing document has reversed the invoicing
document displayed, or which invoicing document was reversed by the invoicing
document displayed. You can navigate to the reversal document or reversed
document.
Activities
1. On the SAP Easy Access screen, choose Invoicing Document
Display Invoicing Document .
2. Enter your selection criteria on the initial screen and choose Execute.
In addition to the fields defined in the database, you can also display additional
data. To display additional data, define a function module for event 2676 in
Customizing for Contract Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules .
In event 2673, you can change the field catalog of the fields that are to be
displayed, and in event 2674, you can program the navigation for the fields
accessed by double-clicking.
If you use billing within the framework of SAP Convergent Invoicing, there are
additional enhancement options available in the billing document and the
invoicing document. For more information, see Enhancement Options in Billing.
Program Enhancements
Using the event concept, you can integrate industry-specific and customerspecific processes and data not specified explicitly in the previous sections in the
existing system architecture for Invoicing in Contract Accounts Receivable and
Payable for new implementations and for implementations already running.
For the documentation and implementations for the individual events for
Invoicing, see the Implementation Guide for Contract Accounts Receivable and
Payableunder Program Enhancements Define Customer-Specific Function
Modules, using the search term Invoicing.
Integration
SAP Convergent Invoicing offers you the possibility of integrating the following
applications:
SAP Convergent Charging offers service industries the following functions for
billing services (such as, telephone calls for telecommunications providers):
Rating
Charging
Based on this integration, you can adopt billable items directly from SAP
Convergent Charging to Billing in Contract Accounts Receivable and Payable.
SAP Convergent Invoicing subsequently groups the priced services into invoices
that you send to customers, and posts the invoice amounts in Contract Accounts
Receivable and Payable.
EXAMPLE
The following illustrates the integration of SAP Convergent Charging and SAP
Convergent Invoicing using an example from the telecommunications industry.
A customer has a cellular network contract with a telephone company; the
telephone company bills the customer monthly for services (phone calls and
SMS).
1. Consumption
The customer sends an SMS with his cellular phone. He thereby consumes
a service of the telephone provider. The telephone network transfers the
SMS usage data, that means that the content of the SMS is sent to the
recipient. The telephone provider records information about the SMS
consumption, such as the date, the time and the telephone number, and
passes on this data.
2. Mediation
The telephone provider converts the payment-relevant information for the
SMS consumption into a uniform format.
3. Rating
SAP Convergent Charging determines a price for the SMS based on the
rate in the cellular network contract; the rating process converts the service
data into a monetary amount.
4. Charging
SAP Convergent Charging, using the technical information for the SMS
consumption (such as the telephone number), determines the invoice
recipient and the customer account to be debited.
5. Billing
Billing in Contract Accounts Receivable and Payable takes over the billingrelevant data for the SMS consumption and processes this data. Billing
groups the data together with other existing SMS consumption of the
customer and summarizes the data in a billing document. This means the
system performs a preliminary aggregation of structured data records
(billable items) according to technical and business criteria.
NOTE
In the case of integrated use of SAP Convergent Invoicing, SAP CC and SAP
CRM, the SAP CRM system is the leading system with regard to master data.
That means that you create and change business partners, account information,
provider contracts and products in SAP CRM and then replicate these to SAP
Convergent Invoicing in the ERP system and to SAP CC. With regard to the
provider contract and product, SAP Convergent Invoicing stores only the
information directly needed for business transactions that take place in SAP
Convergent Invoicing.
In the ERP system, you normally just display the provider contracts and products.
However, for exceptional cases, there are transactions available for changing
products and contracts. These changes are local only, and are not distributed to
the connected systems. When there is a new replication of master data from SAP
CRM, the system overwrites any manual changes.
Information Containers
Purpose
In a business process, information containers save information that you can send
to external systems at a later point in time.
Features
SAP provides connections from the information containers to various business
processes. You can define your own information container categories in addition
to those delivered by SAP.
You can use the following send types for each process:
XI Interface
The prerequisite is that there is an XI interface for the corresponding
information container category.
Save in File
If you select this send type, event 3704 is called. In order to save the data in
a file, the implementation of the event function module must return file
content. This content is created from the send data.
Define the recipients to which the data of the information container entries
are sent
If you specify several recipients, the same data is sent to the different
recipients.
Collections Management
This scenario covers important processes, such as the initiation of
customer calls, processing of payments, and the granting of deferrals and
installment plans.
Closing Operations
This component consists of the following detailed components:
Doubtful Receivables
Reclassifications
Cumulation
Definition
Summarization of FI-CA documents into totals records during posting
For posting of FI-CA documents, totals records summarize line items that have
the same value for the following criteria:
Criterion
Company code
Header data
Posting date
Document date
Currency
G/L account
Debit/credit indicator
Value date
Tax code
Business area
Cost center
Profit center
Order number
Project
Segment
General ledger document type
Application-specific fields for
subsequent applications (for example,
account assignments for Funds
Management)
Structure FKKSUMKEY contains a list of all relevant characteristics.
Use
Totals records are the basis for a cumulated transfer of FI-CA documents to the
general ledger.
Totals records are recorded in FI-CA under reconciliation keys.
The figure below shows how two FI-CA documents are summarized in one
reconciliation key and how this is transferred to the general ledger.
To transfer the totals records posted for a reconciliation key to the general
ledger, you have to close the reconciliation key. You cannot enter any further
postings under a closed reconciliation key. You can then transfer the posting
totals recorded to the general ledger for each closed reconciliation key.
During the transfer to the general ledger, the system creates transfer documents
from the reconciliation keys. Since a reconciliation key is specified for each
posting in FI-CA, you can use the reconciliation keys (also noted in the general
ledger documents created) to compare FI-CA documents with the general ledger
document.
If necessary, you can suppress the cumulation despite the line items having
identical account assignment as follows:
FI-CA items lead to individual line items in the general ledger if you select
the indicator Line Item when posting.
The period is generally open, that is, for the account type + (valid for all
accounts).
The period must not be blocked for the posting from the general ledger
in Controlling (CO).
If you want to transfer totals records for which the relevant posting period is
already closed in the general ledger, you have to maintain the alternative posting
date as described in the section System Settings for the Transfer to the General
ledger. The system then posts the general ledger documents with the alternative
posting date.
The alternative posting date also controls that the system also posts to the
special posting periods still open after the end of the fiscal year. The system
determines the first open special posting period as soon as the alternative
posting date is in the last period of the previous fiscal year. The alternative
posting date or the special posting period is noted in the totals record to
document the special situation and to enable a reconciliation with the general
ledger despite the different posting date.
The alternative posting date is always used only for the totals records for which
the posting date of the totals record cannot be used because the posting period
is closed in the general ledger.
The settings for the posting periods in the general ledger refer only to the general
ledger that you run in the same system as FI-CA. When you transfer postings
from the general ledger that runs in the same system as FI-CA, make sure that
the posting periods are configured the same in the external general ledger.
See also Posting Date and Posting Period.
Closing
Purpose
Contract Accounts Receivable and Payable supports you in day-end closing,
month-end closing, period-end closing, and year-end closing. The following
sections provide an overview of the activities to be completed.
Process Flow
Day-End Closing
82.
...
295.
1.
Create new reconciliation keys for payment and returns lots for
which clarification processing is still to be completed.
296.
2.
Close the cash journal.
297.
3.
Close all reconciliation keys.
298.
4.
Transfer the totals records to the General Ledger.
299.
5.
Transfer the data to Profitability Analysis.
300.
6.
Reconcile the cash clearing accounts.
301.
7.
Reconcile the open items.
Month-End Closing/Period-End Closing
If you run General Ledger Accounting in a separate system, run the month-end
closing in Contract Accounts Receivable and Payable (FI-CA) one day before the
month-end closing in the general ledger. In the FI-CA system, close the posting
periods one day before you close the posting periods in the general ledger.
83.
...
302.
1.
Run the following receivables and revenue adjustments:
14.
a.
Transfer deferred revenues
15.
b.
Adjust receivables according to age
16.
c.
Transfer adjusted receivables (doubtful
entries/individual value adjustments)
17.
d.
Adjustment postings for percentages of ownership
303.
2.
Run all steps that you run for day-end closing (see above).
304.
3.
Reconcile the clarification accounts.
305.
4.
Close the posting periods.
306.
5.
Create a key date-specific open item list.
Year-End Closing
84.
...
307.
1.
Run a foreign currency valuation.
308.
2.
Run all steps required for month-end/period-end closing (see
above).
309.
3.
Post the reclassifications.
310.
4.
Create the tax returns required.
For countries where the balance carryforward must be posted, you have to
complete closing and opening postings in FI-CA. In the SAP menu,
choose Periodic Processing Closing Preparation Opening and Closing
Postings.
Note that the tax category +B Output Tax for Gross Down
Payments must be entered in the G/L account master record for all
down payment accounts.
To create a document journal, in the SAP menu for FI-CA, choose Periodic
Processing Closing Preparation Document Journal. See the report
documentation.
Key-Date-Related Open Items List
In the SAP menu for FI-CA, choose Periodic Processing Closing
Preparation Open Items on Key Date.
Itemization of Clarification Accounts
In the SAP menu for FI-CA, choose Periodic Processing Closing
Preparation Itemization of Clarification Accounts.
Itemization of Clearing Account for Repayment Requests
In the SAP menu for FI-CA, choose Periodic Processing Closing
Preparation Itemization of Clearing Account for Repayment Requests. See the
report documentation.
Determination of Gaps in Document Number Ranges
In the SAP menu for FI-CA, choosePeriodic Processing Forward
Postings Reconciliation Checks/Adjustments Determine Gaps in
Document Number Ranges.
Analyzing Differences
Purpose
If you discover differences during the reconciliation of the open items, you can
analyze these as described below.
Process Flow
85.
...
311.
1.
If you do not reconcile regularly, you first have to restrict the period
of the difference. To do this, run the transaction Open Items for Key
Date (SAP menu for Contract Accounts Receivable and Payable: Periodic
Processing Closing Preparation) for different key dates.
Generally, if you can determine a difference quickly, the analysis
is easier. You should therefore reconcile regularly.
If a difference arises, proceed as follows:
18.
a.
The accounting interface is used for the transfer to
the General Ledger. This is an SAP standard function. Therefore,
check whether this interface has been modified.
19.
b.
You should also check the G/L accounts to see if
additional postings exist which are not part of the FI-CA transfer. You
can recognize these because the document header of such postings
does not contain the reference transaction FKKSU (Contract Accounts
Receivable and Payable).
20.
c.
Check whether the carryforward in the General
Ledger has been run after the fiscal year change.
If there are still differences, the following reasons could apply:
312.
6.
21.
22.
23.
Adjustments
Purpose
You should only make adjustments using the programs named
below after consultation with SAP.
Process Flow
Generally you can use the following transactions for adjustment:
If the reconciliation key has not yet been transferred, the system
adjusts the incorrect amounts in the totals records.
Under certain circumstances, you may have to recreate the totals records
completely before the general ledger transfer. In the SAP menu,
choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Recreate Totals
Records (Report RFKKABS8).
Cash Management
Purpose
This component enables you to update data in Cash Management (TR-CM).
Features
This update is madedirectly when you post a document in Contract Accounts
Receivable and Payable. This means that the Cash Management liquidity
forecast and cash position are always up-to-date.
In the contract account master record, you can define the following data for
updating the liquidity forecast:
Planning group
This way, contract accounts with collection authorization can be considered
separately from contract accounts to be paid on demand. The system
proposes the planning group when you enter a document.
Additional days
These days are considered when determining the expected cash receipt
date. The due date for net payment or the cash discount date (if cash
discount was agreed) is used as the baseline date for this.
Line items that are locked for payment can be assigned to an alternative planning
group automatically.
In the G/L account master record, you define a planning level for G/L accounts
that require the cash position to be updated. The system determines the planning
level when you post the document and enters it in the G/L item.
For mass postings that run in parallel processes, waiting time may occur due to
competing accesses during the update of data for Cash Management. For these
postings, Contract Accounts Receivable and Payable offers a parallel update
mode that you can activate for specific categories of mass runs in the
Implementation Guide for Contract Accounts Receivable and
Payable under Technical Settings Activate Parallel Update of Cash
Management. Cash Management is then updated at the end of each process. If
the process is terminated before the Cash Management update, the update takes
place when you close the relevant reconciliation key. If the update also fails here,
you can transfer the data recorded separately individually. To do this, in the SAP
menu choose Periodic Processing Cash Management Transfer.
Utilities Industry (IS-U) Component
The system automatically determines the planning group in the contract account
when you transfer billing documents and then saves it in the corresponding line
items.
Insurance (FS-CD) Industry Component
The system automatically determines the planning group in the contract account
for the debit entry and then saves it in the corresponding line items.
Integration
Contract Accounts Receivable and Payable considers system settings that you
have made for the segment for Financial Accounting. See the documentation
on segments in Financial Accounting.
Prerequisites
In addition to the general settings for the segment in the SAP Customizing
Implementation Guide under Enterprise Structure Definition Financial
AccountingDefine Segment, you have also made the following settings in the
Implementation Guide for Contract Accounts Receivable and Payable.
Define the segments for money accounts and tax accounts (and optionally,
for additionally selected accounts) under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Segments Define Segments for General Ledger Items.
If you want to derive the segments from the data for the business partner
items, define your settings under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Segments Segment for Business Partner Items.
Features
Segment in Line Items
Contract Accounts Receivable and Payable assigns a segment to all business
partner and general ledger items.
The system assigns a segment to receivables and payables
directly. There is no calculated split over segments using offsetting
items.
Segments for Tax and Money Accounts
For all balance sheet accounts that are not managed on an open item basis, the
problem arises that there are no fixed dependencies between postings on the
debit side and the credit side. Therefore, where different segments are used, a
balance sheet account may no longer show a balance, but, in the ledgers, there
are positive and negative balances for different segments that then provide no
useful information. Money (bank, cash desk) and tax accounts are particularly
affected by this problem. For these account categories, Contract Accounts
Receivable and Payable uses unique neutral segments that you assign in
Customizing.
These neutral segments for tax and money accounts have no
immediate reference to the segment or segments that are affected by
the underlying business transaction.
The system considers a general ledger item a tax item if a tax base amount is
specified in the line item. The systems considers a general ledger item a money
item if either the value date is set or the attribute Financial Transaction Relevant is set in the master record of the general ledger account.
314.
Company code
Business area
Division
Receivables account
Account determination ID
Main transaction
Subtransaction
2.
The system inherits a segment inherited in this way to the
offsetting items (revenue items).
315.
3.
If the system cannot derive a segment from the business partner
items, it derives the segment from the revenue items and inherits it to the
business partner items. In this case, the derivation is performed using the
profit center. Therefore, a profit center to which a segment is assigned in
the master record must be assigned in the revenue item. Derivation via
Customizing without a profit center is only possible if the segment can be
determined from the combination company code/general ledger account.
316.
4.
For line items that arise as follow-on posting to other line items (for
example, clearing, reversal, returns, interest calculation, write-off), if
possible, the segment of the triggering item is inherited to the follow-on
items. This means that the segment of an open item is not only inherited to
the clearing posting on clearing, it is also inherited to cash discount,
payment surcharges, exchange rate differences, and interest on arrears
that arise from the clearing of this item.
If no unique inheritance is possible, as for dunning or returns charges, if
possible, the system uses the segment that has the highest proportion of
relevant items (for example, dunned items, paid items for returns).
Once you have activated segment account assignment, the system checks
whether all line items have a valid segment account assignment, except for
follow-on postings.
If there are follow-on postings (for example, for clearing or clearing reset), all line
items created must also have a valid segment account assignment provided the
items that are cleared or where clearing is being reset all have a valid segment
account assignment. If these items include older postings with no segment, the
system also permits certain follow-on postings, such as clearing, cash discount,
and exchange rate differences with no segment.
Activities
Individual Derivation of Segment
The segment can be derived on an installation-specific basis for event 0081.
Here you can use individual logic to determine a segment for every item for
which the person creating the document has not assigned a segment.
However, the system ignores segments in bank items and tax
items and replaces them subsequently with the value defined in
Customizing.
You can mix the procedure; that is, you can assign some of the segments
explicitly, add some using event 0081, and determine the rest using the
Customizing settings.
Introduction in Productive Operations
If you use segment account assignment in productive operations when
documents already exist in the system, the system does not add the segment to
documents that have already been posted. Therefore, for an interim period, you
will find transaction figures where the field Segment is not filled in many
accounts. This generally applies as long as follow-on postings arise for
documents posted without a segment (all forms of clearing and clearing reset).
The amount proportion of balances with an initial segment value will reduce over
time. You have to decide individually whether, if there are sufficient small
remaining amounts and sufficiently few remaining documents without a segment,
the amounts are to be split for segmental reporting (for example, proportionately
to the remaining split by segment) or whether transfers should be made to
eliminate the effect of these documents with no segment account assignment.
You maintain the posting periods in the Implementation Guide for Financial
Accounting under Document Posting Periods Open and Close Posting
Periods.
You make the settings for the alternative posting date in the menu for FICA under Periodic Processing Forward
Postings Preparation Maintain Alternative Posting Date, or,
alternatively, in the menu for FI-CA under Settings Current
Settings Maintain Alternative Posting Date.
In addition to the general settings for the segment that you make in
the SAP Customizing Implementation Guide under Enterprise
Structure Definition Financal Accounting Define Segment, you also
have to make settings in the Implementation Guide for Contract Accounts
Receivable and Payable:
Define the segments for money accounts and tax accounts (and
optionally, for additionally selected accounts) under Basic
Functions Postings and Documents Document Maintain
Document Account Assignments Segments Define Segments for
General Ledger Items.
If you want to derive the segments from the data for the business
partner items, define your settings under Basic Functions Postings
and Documents Document Maintain Document Account
Assignments Segments Segment for Business Partner Items.
Doubtful Receivables
Purpose
You can use this component to mark receivables as doubtful and make value
adjustments where appropriate in order to adjust existing receivables to their
actual estimated values.
Reclassifications
Purpose
This component is used to reclassify customers with a credit balance, vendors
with a debit balance and receivables according to the remaining term.
Features
The system outputs the amounts to be reclassified in a list for each receivables
and payables account. You transfer the amounts in the general ledger either
manually or automatically in the transaction Post Reclassifications.
You entered the changes to the equity holdings on the SAP Easy Access screen
under Master Data Business Partners Define Equity Holdings. For each
business partner, you entered the date from which each value is valid, and the
date from which the entry is included in revenue consolidation.
Features
The following cases can all occur if the value in the Company ID (VBUND) field
changes in the contract account of the business partner:
The Company ID field contains no value and is now filled (for example,
with 000001), or the Company ID field was filled and is now empty.
A company was purchased or sold. You have to create a new entry (such
as 000001) for a company that was purchased. In Customizing,
chooseEnterprise Structure Definition Financial Accounting Define
Company. If a company was sold, then you have to delete the entry here.
If you use the component SAP FS-RI (industry
component Insurance), you can enter or delete this entry directly in
the business partner.
The system then automatically makes the adjustment in the contract
account. You have to make a new entry (such as 000001 or * in
the Company ID field) in the account assignment, and enter the
necessary account. On the SAP Easy Access screen under Master
Data Business Partners Define Equity Holdings, make the
appropriate entries. If there is no specification for the start of revenue
consolidation there, the system sets the start to the general valid-from
date.
The value in the Company ID field changes (for example, from 000001 to
000002).
The status of a company changes, for example, from participating to
affiliated. In this case you have to create a new company and assign it in
the contract account or business partner. If you assign it in the business
partner, the system adjusts the Contract Account field automatically. In the
account determination, you create a new entry, and enter 000002 in
the Company ID field with the corresponding account. On the SAP Easy
Access screen underMaster Data Business Partners Define Equity
Holdings, enter the valid-from date for 000002 and the period for the
revenue consolidation.
For the selection of receivables and payables, you can use different
reconciliation accounts for the affiliated companies, the non-affiliated companies,
and the participating companies. The company ID (VBUND) is defined in the
contract accounts of a business partner and is transferred to the documents
during posting. The G/L accounts can be determined in a customer-specific
account determination using the Company ID field.
If you want to control the assignment using accounts, then also use the Company
ID (VBUND) field to separate revenues between affiliated and participating
companies in G/L account determination for revenue and expense accounts.
You make the postings required due to the change of equity holdings as part of
closing preparations. You use the programs for foreign currency valuation,
reclassifications, evaluation of open items for a key date, and the new
report Adjustment Postings for Equity Holdings (on the SAP Easy Access screen
underPeriodic Processing Closing Preparation).
We recommend that you run the report for the adjustment of
equity holdings before the foreign currency valuation and the
reclassification.
If an equity holding is changed retroactively, then it can be assumed that
postings, which were made after the date the change takes effect, but before the
change was entered in the system, are not posted with the correct company ID
(VBUND). The Adjustment Postings for Equity Holdings report analyzes the
postings of the affected business partners for this time period, and determines
the amounts and the account assignments for the required adjustment postings.
The report determines the adjustments needed after the change in the equity
holding shares of the partner (for example, the status of a customer changes
from external company to an affiliated company). These adjustments are
determined separately for:
Reserve postings
The report considers the reserves, receivables, and payables on a key date;
revenues and expenses are considered for the period.
The report can also post the adjustments needed; if necessary by business
partner and/or company code. For test purposes, you can select by segment and
business area.
For receivables and payables, the adjustment is made using separate adjustment
accounts that the report determines for each reconciliation account using posting
area 1350. (See Customizing for Contract Accounts Receivable and Payable
under Closing Operations Reclassifications Define Correction Accounts).
The posting takes place for a key date. The inverse posting is for the key date
plus 1.
For revenues, expenses, and reserve postings, the adjustment is made, for the
key date, to the general ledger accounts with no inverse posting.
In the industry component Insurance, you can determine the
accounts at event V040 if you use customer-specific account
determination for the revenue accounts.
For reserve postings you can use the Summarization of Reserve
Postings (FPRES_CON) report to summarize the table of reserve
postings (DFKKRES). Here you can also compare the amounts of the
table with the original line items after a currency changeover, for
example.
You cannot reverse adjustment documents for receivables and payables and
reserve postings. However, you can run the key-date-related adjustments for
different key dates.
You cannot adjust revenues that have already been adjusted. To make an
adjustment, you first have to reverse the adjustment documents of the revenues.
Define the segments for money accounts and tax accounts (and optionally,
for additionally selected accounts) under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Segments Define Segments for General Ledger Items.
If you want to derive the segments from the data for the business partner
items, define your settings under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Segments Segment for Business Partner Items.
Features
Segment in Line Items
Contract Accounts Receivable and Payable assigns a segment to all business
partner and general ledger items.
The system assigns a segment to receivables and payables
directly. There is no calculated split over segments using offsetting
items.
Segments for Tax and Money Accounts
For all balance sheet accounts that are not managed on an open item basis, the
problem arises that there are no fixed dependencies between postings on the
debit side and the credit side. Therefore, where different segments are used, a
balance sheet account may no longer show a balance, but, in the ledgers, there
are positive and negative balances for different segments that then provide no
useful information. Money (bank, cash desk) and tax accounts are particularly
affected by this problem. For these account categories, Contract Accounts
Receivable and Payable uses unique neutral segments that you assign in
Customizing.
These neutral segments for tax and money accounts have no
immediate reference to the segment or segments that are affected by
the underlying business transaction.
The system considers a general ledger item a tax item if a tax base amount is
specified in the line item. The systems considers a general ledger item a money
item if either the value date is set or the attribute Financial Transaction Relevant is set in the master record of the general ledger account.
Segment in Statistical Items
Certain statistical items, such as statistical charges receivables, down payment
receivables, and budget billing receivables also require the specification of a
segment. This segment is inherited to the non-statistical follow-on postings on
later payment. If the segment is not directly specified externally on creation of the
item, it is derived from the Customizing for the business partner item.
Segment in Payments on Account
For payments on account, the segment cannot be derived from offsetting
postings. As far as payments on account take place in combination with the
clearing of other items, you can select the segment that has the highest amount
proportion in the clearing. However, since payments on account also take place
with no clearing of further open items, this rule cannot be applied generally. You
should therefore define a segment account assignment in Customizing for at
least the combination of main transaction/subtransaction used for a payment on
account.
Account Assignment or Derivation of Segment
For line items that are not created automatically, such as cash discount,
exchange rate differences, taxes, and down payments on request, you can
specify the account assignment Segment on manual entry or transfer using one
of the interfaces available. This specification has priority over the derivation
options described below.
Often, only the business partner items are entered or forwarded by means of
posting interfaces. In this case, the system completes the document (for
example, revenue and tax items are added). If a segment is already specified in
the business partner items entered/transferred, this is transferred to the revenue
items assigned.
If no segment is assigned, one is derived as follows:
87.
...
317.
1.
The system tries to derive the segment from the following details
of the business partner item(s):
318.
Company code
Business area
Division
Receivables account
Account determination ID
Main transaction
Subtransaction
2.
The system inherits a segment inherited in this way to the
offsetting items (revenue items).
319.
3.
If the system cannot derive a segment from the business partner
items, it derives the segment from the revenue items and inherits it to the
business partner items. In this case, the derivation is performed using the
profit center. Therefore, a profit center to which a segment is assigned in
the master record must be assigned in the revenue item. Derivation via
Customizing without a profit center is only possible if the segment can be
determined from the combination company code/general ledger account.
320.
4.
For line items that arise as follow-on posting to other line items (for
example, clearing, reversal, returns, interest calculation, write-off), if
possible, the segment of the triggering item is inherited to the follow-on
items. This means that the segment of an open item is not only inherited to
the clearing posting on clearing, it is also inherited to cash discount,
payment surcharges, exchange rate differences, and interest on arrears
that arise from the clearing of this item.
If no unique inheritance is possible, as for dunning or returns charges, if
possible, the system uses the segment that has the highest proportion of
relevant items (for example, dunned items, paid items for returns).
Once you have activated segment account assignment, the system checks
whether all line items have a valid segment account assignment, except for
follow-on postings.
If there are follow-on postings (for example, for clearing or clearing reset), all line
items created must also have a valid segment account assignment provided the
items that are cleared or where clearing is being reset all have a valid segment
account assignment. If these items include older postings with no segment, the
system also permits certain follow-on postings, such as clearing, cash discount,
and exchange rate differences with no segment.
Activities
Individual Derivation of Segment
The segment can be derived on an installation-specific basis for event 0081.
Here you can use individual logic to determine a segment for every item for
which the person creating the document has not assigned a segment.
However, the system ignores segments in bank items and tax
items and replaces them subsequently with the value defined in
Customizing.
You can mix the procedure; that is, you can assign some of the segments
explicitly, add some using event 0081, and determine the rest using the
Customizing settings.
Introduction in Productive Operations
If you use segment account assignment in productive operations when
documents already exist in the system, the system does not add the segment to
documents that have already been posted. Therefore, for an interim period, you
will find transaction figures where the field Segment is not filled in many
accounts. This generally applies as long as follow-on postings arise for
documents posted without a segment (all forms of clearing and clearing reset).
The amount proportion of balances with an initial segment value will reduce over
time. You have to decide individually whether, if there are sufficient small
remaining amounts and sufficiently few remaining documents without a segment,
the amounts are to be split for segmental reporting (for example, proportionately
to the remaining split by segment) or whether transfers should be made to
eliminate the effect of these documents with no segment account assignment.
Key-Date-Related Open Items List (On the SAP Easy Access screen,
choose Periodic Processing Closing Preparation Open Items at Key
Date .)
To consider installment plan analyses for key dates here, set the Consider
Installment Due Dates indicator on the Output Control tab page.
List Items (On the SAP Easy Access screen, choose Periodic
Processing Evaluation of Open Items Evaluate .)
To consider installment plan analyses for key dates in the items list, on
the Selections tab page, in the Item Categories group box, set the Inst.plan
has prio. (installment plan has priority) and Consider Inst.Plan for
KeyDate indicators.
Features
In a mass run, the installment plan analysis for a key date creates a snapshot of
the installment plans for a certain date, assigns the due dates of the individual
installments to the the original items, and stores this snapshot.
NOTE
The system stores the installment due dates starting only from the selection date
you entered. The system does not store installments that are older than that.
The system assigns the original items to installment plan items in one of two
ways. For items that are cleared at the time the analysis is run, the assignment is
based on the cleared items. For installments that are still open, the assignment is
based on the due dates. This means that the program assumes that when an
installment is cleared, it is always the original items with the oldest due dates that
are cleared. If you want to make your own assignment of due dates to the
original items, you can use event 1882.
Displaying the Analysis
In the menu, choose Environment Display Evaluation to display
evaluations, either for an entire run, or limited by key date, company code, and
business partner. If you do not enter any run data, you can also display data from
other evaluations. You can enter a layout for the display. If the installment plan
analysis for a key date was already archived, the system displays the archived
data.
Deleting the Analysis
You can delete simulated evaluations. In the menu, choose Environment
Delete Key Date . The system adopts the data of the current run; but you can
also enter the data of other runs. The deletion of a key date always applies for
the entire company code.
It is not possible to delete data for individual business partners. If you try to
delete data for an update run, the system issues a warning. You are not allowed
to delete data that you already used in the balance sheet. It is not possible to
delete analyses that were already archived.
Activities
1. On the SAP Easy Access screen, choose Periodic Processing
Closing Preparation Record Status of Installment Plans for Key Date .
2. Enter a date and an ID that you can use to identify the run later.
3. Choose Continue.
4. On the General Selections tab page, enter the key date for the analysis
and the installment plan due date starting from which you want the data to
be stored. Entering the installment plan due date does not affect the data
volume that is processed; instead, this date only allows you to limit the
dataset that is stored. You can also restrict the analysis to selected
company codes.
NOTE
The entries you make for the company code relate to the company code of
the installment plan, which can differ from the company code of the original
items. To be able to restrict the selection by company code, you need to
have display authorization for the company codes you enter.
In simulation mode, you can restrict the selection to business partners.
However, in update runs this restriction is not useful. In simulation mode,
the system stores the analysis with a simulation indicator. You can delete
the data later (see above). Before an update run with the same selections,
the system automatically deletes the simulated data.
5. On the Technical Settings tab page, you can set up parallel processing of
the data based on business partners.
6. Schedule the program run. For more information, see the section
entitled Functions for Scheduling Program Runs.
Information System
Purpose
Using the information system you can evaluate document data in the system
under different views.
Features
In addition to the Evaluation of Open Items, Extraction for Business Intelligence,
and the creation of Foreign Trade Reports, you can use the following reports:
Key Date-Based Open Item List as Total List for Closing Preparation
Features
The report file is the basis for the foreign trade report. This is updated
automatically when you post the documents in Contract Accounts Receivable
and Payable. You create the report based on the report file.
Activities
Whether and which report data is to be recorded for a document is determined by
a function module processed at event 1980. You create this function module
installation-specific and enter it in the Implementation Guide for Contract
Accounts Receivable and Payable (see the documentation for the sample
function module FKK_SAMPLE_1980).
If you want to update new entries in the report file when you reset clearing for a
document for which there are one or more entries in the report file, create an
installation-specific function module for event 1981 and define it in Customizing.
You can edit the report file in the transaction Foreign Trade Reporting: Edit
Report File (SAP Menu: Periodic Processing Data for Externals Tax
Authorities Process Transactions for Foreign Trade Reporting). To ensure that
all relevant documents are entered, you can activate and deactivate the entries
or add new entries.
Write a report that creates the report in the format agreed with the responsible
authorities, based on the data recorded in the report file.
BAPIs
IDoc Interfaces
Event Concept
Purpose
The event concept enables the integration of industry-specific and customerspecific processes and data in the existing system architecture of Contract
Accounts Receivable and Payable for a new implementation and in production
operation.
Features
Using installation-specific and industry-specific function modules that you define
in Customizing, you can enhance the standard business processes of Contract
Accounts Receivable and Payable in predefined program events seamlessly and
without modifications. Depending on the event, you can either realize an
alternative program logic or additional functions.
Customer-Specific Enhancements
Purpose
The event concept enables you to integrate your own source text passages
encapsulated and therefore exchangeable in function modules at specific points
in the program logic, the events, using defined interfaces.
Procedure
With Contract Accounts Receivable and Payable, SAP delivers a sample function
module for each event. This module defines the interface of this event, where
there is usually no process logic implemented. In addition to this sample module,
each industry component (application) can define standard function modules in
each event for conversion of industry-specific process logic. To adjust the
processed defined by SAP to internal requirements, each customer can also
implement an additional customer module in each event in his installation.
The figure below makes this three layer architecture in the program logic clearer.
Program Logic on Reaching an Event (no Additional Function)
You manage these events and their function modules in the Implementation
Guide for Contract Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules.
The function module FKK_FUNC_MODULE_DETERMINE is processed for each
event. From the following tables, it sequentially determines the event modules
defined in Customizing that are to be processed:
To Event
Application
9999
Application-independent
R0
R999
Utilities industry
V0
V999
Insurance
T0
T999
Telecommunications
P0
P999
Public Sector
X0
X999
Partner Development
Z0
Z999
Customer development
S0
S999
In the Function Builder (transaction SE37), you can call up the function modules
and their documentation. For a deeper, technical analysis, use the Object
Navigator (transaction SE80).
General Selections
Activity-Specific Selections
Technical Settings
Logs
On the tab page Technical Settings, you can decide whether you want automatic
load distribution by the system, where you only define the number of jobs, or
explicit load distribution where you explicitly specify how many jobs are to run on
which hosts. For more information about the entries on the individual tab pages,
see Functions for Scheduling Program Runs.
Once you have made all of the entries required to execute the business process,
you can schedule the program run. You can choose between immediate
processing in the background or processing on a specific date. If you use the job
container, you can also select the containers available.
During the processing of the data, the system distributes the dataset to be
processed to several parallel jobs automatically. The details for distributing the
keys for the parallel objects are stored in variants that you have to update
periodically. For example, you can create a variant for the business partners that
splits the business partner set to be processed into 1,000 equal intervals.
During parallel processing, the system makes sure that the processes do not
block each other because of changing accesses to the same database
resources, which could be the case, for example, in the assignment of document
numbers or the update of transaction figures.
A payment run for all business partners starts several processes
(for example, 10) that process the intervals created automatically one
after the other. When the processing is completed for an interval, the
system processes the next free interval. If all intervals have been
processed, and therefore all technical jobs completed, the business
task also receives the status Completed.
You can schedule the parallel interval jobs of the mass activities, execute them in
a specific order, and monitor them using the following tools:
Own programs
For instructions on how to proceed, see SAP Note 402886.
With the module FKJO_SCHEDULE, you can also schedule mass activity runs
by RFC (see SAP Note 402886).
If an interval cannot be processed in a payment run, interest run, or interest
calculation run for cash security deposits because the data is locked by another
processing function, the system can restart the processing of this interval
automatically and as frequently as required. You have to enter the maximum
number of repetitions in the field Maximum Int. Repetitions in the specifications
for General Control on the tab page Job Control under Technical
Settings Prepare Mass Activities in the Implementation Guide for Contract
Accounts Receivable and Payable.
In all mass activities, the system checks the authorizations for authorization
object F_KKMA that checks the authorization for the mass activity via the mass
activity type. The processing of the variants is protected by the authorization
object F_KKVARI (see the documentation for the authorization objects).
You can improve the performance of mass activities through settings in
Customizing, such as activating the business partner shadow table. To do this, in
the Implementation Guide for Contract Accounts Receivable and
Payable choose Technical Settings Activate Performance Improvement for
Mass Runs. Read the documentation for the activity and the individual fields.
In the Implementation Guide for Contract Accounts Receivable and
Payable under Technical Settings Create Interval Variants for Parallel
Processes, you can maintain interval variants for parallelization (see activity
documentation).
Enter parameters as
required.
Technical Settings
329.
1.
Select
either Automatic
Load
Distribution or Explici
t Load
Distribution and
specify the number of
jobs and the target
host.
330.
2.
Select a
variant. The system
proposes the block
size.
If the program run is to be
executed by a single run
(that is, not in parallel),
you do not have to make
any technical settings.
Via a specification in
the fieldProblem Class,
you determine the
importance that a
message must have to
be output in the
application log. For
production, SAP
recommends class 2,
for testing, class 4:
Very important
(1)
Important (2)
Average (3)
Additional
information (4)
If you specify class 3,
logs with lower classes
are also output, that is,
also 1 and 2.
Meaning
Display/Change
Copy
Adjust
Variants
To create a variant:
91.
...
331.
1.
Choose the
button Variant
Maintenance.
332.
2.
Choose New.
You can specify either the
interval size or the
number of intervals.
333.
3.
Choose Execute.
To display the intervals created
or to edit the variant, double-
interval distribution.
End Early
Terminates a run
This means that if the
program is running, once the
current interval has been
processed, all jobs are
terminated from this
command.
Restart Run
stopped.
Deletion
Deactivate Old
Runs
Environment
Categorizing Messages
You can influence the level of detail in the application log by categorizing
messages.
Prerequisites
You made settings for the problem classes of messages in Customizing under
Contract Accounts Receivable and Payable Technical Settings
Specifications for the Problem Classes of Messages Assign Messages to
Problem Classes .
Features
You can configure the problem class of messages in the application log of mass
activities in Customizing. This means, for example, that you can classify
messages that the standard system issues for problem class "medium", so that
they are only issued for problem class "additional log". In this way, you can
influence the level of detail of the application log.
NOTE
Messages that the standard system sends as "very important" are always sent as
"very important".
Activities
Enter the problem class you want for each mass activity and message in
the Assign Messages to Problem Classes IMG activity. In the Activate Recording
of Messages IMG activity, you can specify that the system writes a trace of the
messages that appear for a given mass activity up to a certain date. The system
lists the messages that are recorded in this way in the input help of the Assign
Messages to Problem Classes IMG activity. However, if you know the message
number, you can also make entries directly, without having activated the trace
beforehand.
Additional Characteristics
An additional characteristic is used to categorize a run of a mass activity.
You can enter additional characteristics for each mass activity in Customizing for
Contract Accounts Receivable and Payable under Technical Settings Define
Additional Characteristics for Mass Activities .
The additional characteristics you enter then appear in the input help of
the Additional Characteristic field of the mass activity. There you can assign them
to a run.
Additional characteristics can be interpreted in all customer-specific event
modules of the given mass activity. This makes it possible to have your own
specific procedures for runs to which you have assigned certain attributes.
NOTE
The mass activity itself does not interpret the additional characteristic. The
additional characteristic is evaluated exclusively in customer-specific events.
Therefore, the additional characteristic influences all functions that are possible
in the given event, such as, item selection or the control of processing.
EXAMPLE
You want to define more selection options, in addition to those offered for items
and master data in the mass activity for automatic clearing. For instance, you
might want to process only items with certain transaction data, or only business
partners of the Organization category.
To achieve this, you enter the following additional characteristics in the Define
Additional Characteristics for Mass Activities IMG activity:
Country-Specific Functions
The following section describes which country-specific functions are supported
in SAP Utilities (SAP IS-U). The documentation provides an overview of the
business processes, and the associated Customizing activities and transactions
or reports available in the system.
Features
The functions documented here are functions that are not otherwise covered by
the generic SAP Utilities functions. SAP Utilities provides these additional
functions to enable you to meet country-specific requirements.
India
The SAP Utilities (SAP IS-U) component covers the most important laws and
business practices specific to India. The following documentation covers these
aspects of the component. For generic information about SAP Utilities, see SAP
Utilities.
Features
The country-specific functions for India relate to sales and information system,
particularly, support of management and billing of residential, commercial and
industrial customers.
The main functions that are specific to India include the following:
Energy Audit
Utility bills may be reversed for various reasons. Entry of an incorrect meter
reading contributes to annulment of the bill substantially. Incorrect meter reading
can comprise bills pertaining to several months in the past. For such situations,
the current meter reading is registered from the date of the last correct meter
reading. All bills relating to this period are revised and a corrected net bill is given
to the customer.
Prerequisites
Ensure that the print documents to be reversed are available in the system.
Features
Mistakes in the tariff can generate bills with wrong values. These bills are then
reversed and new bills created. Bills are reversed using the adjustment reversal
functionality. At any given point of time, only one bill is selected for reversal. For
invoice reversal, enter the document number with the relevant reversal reason.
For country-version India, the selection of the print documents to be reversed is
based on the following specifications:
Posting Date
Portion
Billing Transaction
Rate Category
Output
Print documents are selected based on the specifications mentioned above and
are submitted to the Print/Billing Document Reversal (lEA14) transaction for
reversal.
Activities
To print the documents for reversal, from the SAP Easy Access screen, access
the report by choosing SAP Utilities Invoicing Execute Invoicing Mass
Processing Country-Specific Settings India Selecting Print Documents .
Meter Reading
Bill Distribution
Payment Collection
Features
Meter Reading
The franchisee executes meter reading in their area(s) and sends meter reading
results to the utility company. Incentives can be paid for meter readings that are
delivered.
Bill Distribution
Bills are generated after uploading the meter reading data collected by the
franchisees. These bills are distributed by franchisees. The proof of delivery is
recorded after the customer signs the delivery. Details concerning the delivery
including the date of delivery and name of the person who took the bill are then
entered in the system. The timely delivery of bill distribution then becomes the
criterion of a part of incentive or disincentive for the franchisee.
The bill delivery schedule is agreed with the franchisee. The incentive is paid
based on the number of bills delivered on time.
Payment Collection
The franchisee collects money on behalf of the utility company. Customers may
decide if they want to pay the franchisee or pay the utility company directly. The
franchisee issues a receipt for the cash payment, which is then given to the utility
company and entered into the system. The collection ratio in the area is a
criterion of a part of incentive for the franchisee, irrespective of whether the
customer paid directly to the utility company for services rendered or via the
franchisee.
AT&C Loss Calculation
The franchisees are responsible for reduction of non-technical losses in their
grid. The franchisee has to inspect installations and networks before informing
the utility company about potential fraud. The percentage of non-technical losses
in the grid is a criterion of a part of incentive for the franchisee.
Franchisees are responsible for geographical areas. The smallest area is a lowvoltage grid connected to one distribution transformer. One franchisee may
govern several areas. Within a given area, there is a possibility that there exist
different franchisees for each of the functions mentioned above.
Each franchisee is remunerated for the services provided to the utility company.
The franchisees performance for each of the assigned function is evaluated and
accordingly awarded an incentive or penalized.
Activities
Procedure
1. Enter the customer type under the New Service Connection tab in
the Create Service Notification (IW51) transaction.
2. Create the document type in the Create Service Notification (IW51)
transaction.
3. Upload the document. The documents submitted by the customer are
uploaded to the system.
4. Create the new document in the Create Service Notification (IW51)
transaction.
5. Assign the document to the document type. Based on the mandatory
document type submitted, the status can change to
(required
documents submitted),
(additional documents required) or
(no
documents submitted).
6. Save your entries.
Energy Audit
The technical and commercial energy losses in India are very high according to
national statistics. Various measures are required to plug in these energy losses
and increase the efficiency of energy generation.
The Accelerated Power Development and Reforms Program (APDRP) enable
utility companies to reduce Aggregated Technical and Commercial (AT&C)
Losses.
Prerequisites
You have made the following settings:
Completed the system setup for Utilities including the Business Master
Data and Technical Master Data
Procedure
1. Maintain the settlement parameters for the grid. To do this, from the SAP
Easy Access screen, choose Utilities Industry Energy Data
Management ToolsSystem Modifications User-Defined Enhancements for
Energy Data Management Settlement Country-Specific
Settings India Parameters for Settlement Units.
2. Create settlement document for the required period using the Create
Settlement Document (eedmsettlcreate) transaction. Use the settlement
procedureEnergy Audit for India.
3. Perform the settlement run using the Create Settlement
Document (eedmsettlcreate) transaction. The results for the selected period
are now available as profiles.
4. Execute the ALV report for energy audit to see the consolidated results for
various settlement units.
5. Save the energy audit report.
Output
The system prints the invoices with amounts (in words) in the local regional
language.