Professional Documents
Culture Documents
Isu Fica Sap Help
Isu Fica Sap Help
Isu Fica Sap Help
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
SAP Customer Relationship SAP Help Portal (help.sap.com):
Management SAP Business Suite SAP Customer
Relationship Mgmt.
SAP NetWeaver Business Intelligence SAP Help Portal (help.sap.com):
SAP NetWeaver (or other
release) German SAP NetWeaver
by Key Capability { BI
Content Industry Solutions
Utilities
SAP NetWeaver Portal SAP Help Portal (help.sap.com):
SAP NetWeaver Portal Content
SAP Utilities Customer E-Services SAP Solution Manager
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 Basic Functions to manage addresses and regional
structures. You can generate schedules for meter reading, budget billing,
and billing.
● 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 Device Management to manage the installations, meter
reading, and the certification of all devices for a utility company.
● The Billing component is used to bill the standard divisions: Electricity,
gas, water/waste water, district heating, and multimedia services (for
example, cable TV).
● 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.
● In Customer Service you can use the Customer Interaction
Center (CIC) or Front Office to display all data and start specific business
processes. In Internet-Self-Services your customers can send you new
data or changes to their existing data via the Internet. For example, they
can grant you collection authorization or register a move-in.
● Energy Data Management (EDM) is a solution that meets the
requirements of interval reading, schedule management, and the billing of
interval energy consumption. EDM includes the following functions:
○ Central database for energy data (Energy Data Repository)
○ Settlement and schedule management using the settlement
workbench
○ Billing of profiles using real-time-pricing billing (RTP billing)
● Intercompany Data Exchange (IDE) fulfills the requirements of the
deregulated market. IDE includes the following functions:
○ Infrastructure for processing deregulated business processes
○ Unbundling
○ Data exchange processes
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:
Delivery contracts, for example for residential contracts, nonresidential
contracts, cable television, telecommunications
Purchase contracts for small power producers, solar installations and
other forms of energy transmission
Plant consumption contracts for generation and distribution installations
of the utility company
Company consumption contracts, for example for the electricity
consumption of offices at the utility company
Waste disposal contracts for the waste disposal industry.
For more information, see Waste Disposal Contract in the Waste Disposal
Industry (IS-U-WA) component.
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.
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
Features
These data cleansing functions are not released for systems with
industry add-ons.
For further information, see the release information about Changes to Data
Cleansing on the SAP Service
Marketplace under http://service.sap.com/releasenotes mySAP
Solutions R/3 SAP R/3 Enterprise 4.70x110 (English) Chapter 04 Cross
Application Components (page 12).
Features
For further details about business partner merging, read the following information
on business partner objects and further functions and tools:
Objects in Contract Accounts Receivable and Payable
Objects and Enhancements in SAP Utilities
Customer Change
Objects and Enhancements in SAP CRM
Automatic Business Partner Merging
In the following, the business partner to be removed from the system is referred
to as the source business partner. The business partner that replaces the source
business partner is referred to as the target business partner.
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.
Contract Account Category
Definition
A contract account category defines certain attributes for a contract account.
Use
You have to assign a contract account category to each contract account when
you create it. The fields that appear when you create a contract account are
among the things controlled by the contract account category.
Structure
The contract account category determines the following contract account
attributes:
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
Whether you are allowed to maintain a contract account online
The number range that is allowed for external or internal number
assignment
Whether it is a collective bill account (industry component Utilities)
Whether it is a one-time account
Whether it is a deposit account and the account contains deposit
contracts (industry component Insurance)
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)
The contract account is created with internal number assignment.
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 partner-
specific 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).
In addition, you also have the option of using additional industry-specific fields.
There is a series of IS-T-specific attributes in the contract account. These attributes can
be split up into different areas.
Dunning Control:
Use
You must assign at least one business partner to each contract account.
Depending on the industry, you may also be allowed to assign several business
partners to a contract account.
Prerequisites
You can only assign additional business partners to a contract account if the
respective contract account category allows you to do this.
Features
The master data in a contract account can be divided into one part that is the
same for all business partners in the contract account (in other words, cross-
business partner) and into another part that is business partner-specific. You can
set the business partner-specific data differently for different business partners.
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
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.
Automatic Master Data Transfer
Use
You use this function to transfer the contract account master data from legacy or
operational systems.
Features
Data is generally transferred in two steps:
1. ...
1. 1. The relevant data is read from the operational system and placed in
a sequential file (operational system sender structure) by the data selection
program. This transaction takes place outside of the SAP system and is not
supported by SAP programs. Therefore the data selection program can
make changes to data at this point.
2. 2. The SAP transfer program reads the data from the sender structure,
changes the data, and places the data in the receiver structure. Data can be
changed or converted in this last step.
Activities
For more information, and the programs involved, see the Implementation Guide
for Contract Accounts Receivable and
Payable: Basic Functions ContractAccounts Data Transfer.
This function is used for the initial transfer of contract account data from a legacy system
in IS-T, and is a component in the IS-U Migration Workbench.
Integration
The IS-U Migration Workbench is required to prepare for and execute the data transfer.
Choose the Settings for IS-U Migration activity in Customizing forUtilities.
Prerequisites
You must transfer the business partners in the IS-U Migration Workbench before you can
transfer the contract accounts.
Features
The contract accounts are generated from the data in the legacy system using the “direct
input” method.
Automatic Account Maintenance (IS-T)
A report is available to automatically clear contract accounts. The open items are
allocated in accordance with the rules defined in the Implementation Guide (see
Creating Automatic Clearing Proposals).
To start the report, select the following path in the telecommunications menu Periodic
Processing For Contract Accounts Correspondence Automatic Clearing.
Using correspondence type 0030 (master data change), you can follow immediate and
planned changes to the master data of your business partners (business partner, contract
account, contract reference).
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and Payable, under Basic
Functions Correspondence Define Fields for Creating Master Data Changes, you
have entered the tables to be considered for the correspondence (for example, BUT000 –
general business partner data). You can only define tables that contain object classes
defined by SAP, since the key for selecting the change documents is different for each
object class and is created in module FKK_SAMPLE_1915. If you want other tables and
therefore object classes to be considered, a program enhancement is necessary. The
object classes defined by SAP are delivered in system table TFK070QC, which contains
the following entries: ADRESSE, ADRESSE2, BUPA_BUP, FMCA_PSOB,
FMCA_PSOBVKK, MKK_VKONT. When you enter a table in Customizing, the system
automatically checks whether your entry is valid. Use the input help to display the valid
entries.
Once you have entered the tables, in a second step, you define the fields to be monitored
for each table (for example, STREET in table ADRC). If the system writes a change
document for a field that you have defined here in Customizing, this field is displayed in
the correspondence. To determine which tables and fields you have to enter in
Customizing, proceed as follows:
2. ...
3. 1. In the menu, choose Display Business Partner or Change Business
Partner.
4. 2. Enter a business partner, specify the screen selection, and
choose Continue.
5. 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.
6. 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.
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 (BUT000-
NAME_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.
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
can be statistical. Statistical items do not update transaction figures in the
general ledger. The corresponding open items are only needed for creating
follow-on postings. For example, when you clear a statistical charge receivable, it
triggers the creation of a non-statistical charge receivable, its clearing and the
posting of the respective revenue. When you clear a budget billing request, it
triggers the creation of a budget billing posting.
Documents can contain repetition specifications. In this case the document
represents a time-dependent sequence of transactions with the same structure.
For example, you can post a budget billing request for which budget billing
payments are requested every month for twelve months as a document. In an
additional item category, known as repetition items, data that varies with time
(such as the due date for cash discount, due date for net payment, or billing
period) is recorded.
Repetition specifications can only be made if the document just contains
statistical items.
Document type
You can only carry out a posting in Contract Accounts Receivable and Payable if
the period is allowed under account type V for contract accounts and under the
masked entry '*'.
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:
If you delete a line item that results in tax, all tax items generated from this item are
deleted.
In the industry solution
components Utilities and Telecommunications, the tax items are
created automatically from the business partner item.
Entering Documents
Purpose
You enter documents using the Post Document function. The way you proceed depends
on the document type.
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:
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. 1. Enter the document header.
15. 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 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.
You can post a document when it has a zero balance. During posting, the
summary records for the reconciliation key specified in the document header
as well as any balances in Cash Management are updated.
Roles
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.
If you want to display or change a document, choose one of the following paths:
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 Display
Goto Document Header Document header data
Goto First Item First document item
Goto Overview Business partner items, G/L account items,
and clearing of receivables document
Goto Business Partner Item List Business partner items for the document
Goto G/L Item List Only the G/L items for the document
Settings Taxes Tax data for the document
Read from Archive (Pushbutton) Documents from the document archive
(including archived SD documents).
However, you cannot display change
documents for archived documents. You
cannot change documents read from the
archive or rewrite them to the database.
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 Physical View Displays business partner items and
repetition specifications separately
Goto Logical View Displays integrated business partner
items and repetition specifications, with
due date, clearing numbers, and open
residual amounts
Goto Due Date View Displays due dates, deferral date,
payment and dunning blocks in a
logical view
Goto Payments/Returns Displays the payments, payment
returns, and returns with return
reasons, bank data, and return texts for
the selected business partner item
Extras Interest Supplement Displays the interest data for an item
on which interest has been calculated
Extras Payment Card Supplement Displays the payment card data for a
clearing document for which
receivables were cleared by the
payment run or cash desk using the
payment card payment method.
Extras Profitability Analysis Displays the profitability analysis
account assignment for the G/L item
Extras Deferred Revenues Displays the trigger for deferred
revenue postings for receivables for
which a revenue deferral has been
carried out.
Extras Corrections Displays the trigger records for doubtful
items.
Environment Document Changes Displays document changes
Environment Master Data Displays the contract account,
business partner, and contract data for
the document
Environment Posting Totals Displays the posting totals for the
reconciliation key used to post the
displayed document.
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 Display
Environment Cleared Items Displays the items cleared with this
clearing document within the account
balance display
Environment Previously Cleared Items For a clearing document for which clearing
postings have been reset, this displays the
items that were cleared with this document.
Environment Payment Usage Displays the items cleared with this
clearing document in a dialog box.
Environment Bank Data from Returns Displays the bank data from the sources
Document/Payment Lot/Payment Run mentioned
Environment Clearing Analysis 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).
Extras Clearing History Displays clearing postings and
resetting of clearing postings in a
chronological view
Environment Clearing Document Displays the clearing document for the
open business partner item
You can use the following functions for dunning/installment plan/collective bills:
Function Display
Environment Source Receivables For an installment plan document, this
function displays all the items that went
into this installment plan and were replaced
by it.
Environment Line Items: Collective Bill Displays the individual invoices that make
up a collective bill
Environment Installment Plan Displays the installment plan for the
installment plan document
Goto Dunning History Displays the dunning history for the
dunned items
When you display a business transaction that consists of several documents, you can
use the following functions:
Function Display
Document Business Displays the individual document of a
Transaction Individual Document business transaction
Display
Document Business Allows you to switch from the individual
Transaction Total Display document to the overall business
transaction
You can use the following functions in connection with the changeover to the Euro:
Function Display
Goto Document Prior to Conversion Displays the document data before the Euro
conversion
Euro Simulation On (Pushbutton) 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
Features
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).
The Mass Change to Master Data function allows you to perform mass changes
for fields of facts, contract objects and contract accounts.
Features
You can update locks on contract accounts and contract objects, that is you can
set, delete or replace locks for the selected master data objects. To update locks
on contract accounts, select object type contract account and
table FKKVKLOCK (Locks for Contract Account). To update locks on contract
objects, select object type contract object and
table SPSOB_BP_ACC_LOCKS (Locks for Contract Object).
Facts can be used on the contract object. It is possible to update this fact data
through the mass maintenance as well. To do so select object type contract
object and table SPSOB_FACTS (Data Facts for Contract Object). For general
information on facts, see Facts.
More Information
For more information, see Making Mass Changes.
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
reversed document cannot be reversed again unless the related reversal
document itself has been reversed beforehand.
For the creation of the offsetting items for the business partner items of the
document to be reversed, you have specified the main and subtransactions in the
Implementation Guide for Contract Accounts Receivable and
Payable under Basic Functions Postings and
Documents Document Maintain Document Account
Assignments Maintain Subtransactions. For each main and subtransaction,
you have to specify a combination of main and subtransaction that is to be used
for the offsetting item in the reversal document in the case of a reversal.
You have entered default values for the reversal parameters in the
Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions Reversal Define Default Values for
Reversals.
Features
Reversing documents
There are two reversal methods. In the classic method, open business partner
items are cleared by the reversal and clearing is cancelled by the reversal. The
second method is restricted to the creation of offsetting items. In particular, this
method is used when the document to be reversed has already been archived
and therefore, neither clearing nor clearing reset is possible.
Reversing a document has the following effect:
Depending on the reversal method selected, the system clears all
business partner items of the document or creates offsetting items with
opposite +/- signs.
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.
If clearing is reset, in the payment document the system creates one or
more business partner items as replacement for clearing. These
replacement items are cleared by 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:
Clear business partner items/reset clearing
Create offsetting postings if document is in archive
Create offsetting postings for business partner items
27. 4. Choose Document Reverse.
Using event 0073, you can add customer-specific data to the
business partner items created in the reversal document. The event is
processed if business partner items are created with inverse +/- sign
(for example, reversal of invoice). To do this, define an installation-
specific function module in the Implementation Guide for Contract
Accounts Receivable and Payable under Program
Enhancements Define Customer-Specific Function Modules.
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.
You can use a program to transfer documents from an operational system (initial
data transfer). You can also use this program to transfer data regularly from an
operational system if you do not have an industry-specific program available.
Roles
Transfer Posting
Data (SAP_FI_CA_POSTING_DATA_TRANSFR) Transfer
Documents
SAP Menu
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
You can delete the incorrect data here by choosing Cluster Delete.
● Document Changes
Posting and reversing documents
For each posting, event 5500 is processed; for each reversal, event 5502. The
function modules defined for these events transfer all of the data of the document
to be posted or reversed. If a check reason is returned by the modules for event
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
SAP delivers the sample workflow 21000093 FICA_DCHAPPR. The role
21000056 FICA_DOCAPPR is used for the role resolution.
Creating installment plans
If, for example, you do not want to grant installment plans to customers with bad
creditworthiness without subjecting them to a check and approval first, define an
installation-specific function module for event 5506 in Customizing. This module
runs when you create installment plans. If the module returns a check reason,
the event ApprovalRequired from object category INSTMNTPLN is triggered.
SAP delivers the role 21000062 FICA_INSTPL and the sample workflow
21000094 INSTPL.
Repayment requests
In order to check and approve repayment requests in a workflow, you have to
enter an installation-specific function module for event 5508 in Customizing. If the
module returns a check reason, the event ApprovalRequired from object
category CA_RPAYREQ is triggered. SAP delivers the role 21000063
FICA_RPAYREQ and the sample workflow 21000095 FICA_RPAYREQ.
Requests and standing requests
See Workflow for Checking and Approving Requests.
Write-offs
See Checking and Approving Write-Offs.
Payment specification
See Approval and Release of Payment Specifications by Workflow.
Promises to pay
See Approval and Release of Promises to Pay by Workflow.
Activities
To authorize or reject a posting or reversal, proceed as follows:
7. ...
28. 1. In the SAP Business Workplace, choose Inbox Workflow.
The reason for the check procedure appears on the lower part of the
screen.
29. 2. Select the corresponding work item by double-clicking it. The
document posted or to be reversed appears. You can then use various
functions to accept or reject the posting or reversal:
Required Action System Reaction/Activity to be
Executed
Approve posting The check reason is removed from the
document. The workflow is completed
and the document is posted.
Reject posting The screen for processing the reversal
appears automatically. All the data is
copied, but you can change it (except
for the number of the document to be
reversed). The workflow is completed
when the reversal is posted.
Approve reversal The screen for processing the reversal
appears automatically. All the data is
copied, but you can change it (except
for the number of the document to be
reversed). The workflow is completed
when the reversal is posted.
Reject reversal The check reason is removed from the
document to be reversed. The
document is not reversed.
Accept document change The check indicator is removed from
the document automatically; the
change is included in the document.
Reject document change The check indicator is removed from
the document automatically; the status
of the document does not change.
Accept installment plan The check indicator is removed from
the document automatically and the
installment plan is created.
Reject installment plan The check indicator is removed from
the document automatically. The
original receivables are not changed.
Accept repayment request The repayment request is released.
Reject repayment request The repayment request is reversed.
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:
An additional specification for document entry, document change, and
document display
Selection criterion for the account balance
Selection criterion for the account maintenance
Selection criterion for other clearing processing
Selection criterion in payment lot
Activities
You activate the Classification Key and Broker fields in the Implementation Guide
for Contract Accounts Receivable and Payable under Program
Enhancements Prepared Enhancements. When you run the corresponding
reports in Customizing, these create the fields and database indexes required. In
test mode, the report shows which enhancements would be made in an update
run.
If the classification key is active and you have posted documents
with classification keys, the system administrator must update the
database statistics for table DFKKKO.
If the broker is active, you should update the database statistics for
table DFKKOP.
This is the only way to make sure that the new indexes are also used.
If you use requests, the same applies for table DFKKORDERPOS.
You can deactivate the classification key and the broker – but only manually. To
do this, for the classification key, remove the field OPORD from the CI includes
to which it was added, and for the broker, the field BROKR. You then have to
convert the database tables. This conversion can have a long runtime if a lot of
data records are affected. SAP therefore recommends that you weigh-up the
activation of the field and then adhere to this decision.
Customer-Specific Enhancements for Postings and Documents
Use
You can use the function modules that are called up for the events listed below to trigger
industry- or installation-specific additional actions when you are posting or reversing a
document in Contract Accounts Receivable and Payable.
Features
Additional Activities When Posting and Reversing
Event You can use a function module called up for this event to:
0010 Trigger additional actions when you are posting a document
in Contract Accounts Receivable and Payable. To do this, you can
use all the document data (except for the document number) in this
event.
See the documentation for the sample function module
FKK_SAMPLE_0010.
0020 Trigger additional actions when you are posting a document
in Contract Accounts Receivable and Payable and simultaneously
clearing or partially clearing open items. You can use all the
document data (except for the document number) and all the data for
the items to be cleared for this event.
See the documentation for the sample function module
FKK_SAMPLE_0020.
0030 Close additional actions initiated by event 0010 (document posted) or
0020 (document posted and items cleared). You can use the
document header, including the document number assigned
(I_FKKKO_OPBEL).
See the documentation for the sample function module
FKK_SAMPLE_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.
Using a function module called up for event 0032, you can create additional line items in
a document. Event 0032 is processed before the creation of items for cross-company code
clearing.
See the documentation for the sample function module FKK_SAMPLE_0032.
The event is not processed if you post reversals, returns, or
clearing reversals. You cannot create additional items for purely
statistical documents.
Dependent Documents
You can use events 0010, 0020, or 0030 to create an additional document for a document
automatically. To do this, in the events, define a function module that creates the
additional document, checks it, and the calls up the function module
FKK_CREATE_DOC_ADDITIONAL.
For more information, see the documentation for the function module
FKK_CREATE_DOC_ADDITIONAL.
You can use a function module called up for event 0070 to integrate document reversal.
To check whether the reversal is permitted, you can use the document header data,
I_FKKKO, the desired reversal date, I_STODT, and an ID for the reversal trigger,
I_CALLR.
See the documentation for the sample function module FKK_SAMPLE_0070.
You can use a function module called up for event 0071 to integrate clearing reversal.
See the documentation for the sample function module FKK_SAMPLE_0071.
You can use function modules called up for events 5500 and 5502 to subject document
posting and reversal to a check. For more information, see the documentation for the
sample function modules FKK_SAMPLE_5500 and FKK_SAMPLE_5502 and the
section Dual Control Principle for Posting and Reversing.
In event 5504, you can subject changes to documents to a check and subsequent release
in accordance with the dual control principle dependent on document data. See the
documentation for the sample function module FKK_SAMPLE_5504.
In event 5508, you can check and approve repayment requests in a workflow. See the
documentation for the sample function module FKK_SAMPLE_5508.
Dual Control Principle for Write-Offs
In event 5512, you can subject write-offs of documents to a check and subsequent release
in accordance with the dual control principle dependent on document data. See the
documentation for the sample function module FKK_SAMPLE_5512.
Activities
8. ...
30. 1. Write function modules for the events stated above as required.
31. 2. Define these function modules for the relevant events in the
Implementation Guide for Contract Accounts Receivable and
Payable under Program Enhancements Define Customer-Specific
Function Modules.
Tax Postings
Features
The following sections contain information:
About posting taxes in Contract Accounts Receivable and Payable
About creating tax returns for the tax authorities
Withholding Tax
You can levy Bollo for customers with tax exceptions (in Italy).
Prerequisites
You made the necessary system settings for posting stamp tax (bollo) in
Customizing under Contract Accounts Receivable and Payable Basic
Functions Particular Aspects of Taxation Procedure Stamp Tax (Bollo)
(Italy) .
You registered function module FKK_CHECK_CALC_BOLLO_INTERN at event
0100 in Customizing under Contract Accounts Receivable and Payable
Program Enhancements Define Customer-Specific Function Modules .
Features
If you configured the system accordingly, the system always posts Bollo if the
total of the items excluded from tax and the Bollo-relevant items exceeds a set
amount determined by law. It is irrelevant whether the items are debits or credits.
Only the absolute amount is decisive. The bollo amount is always a fixed
amount.
You can levy Bollo for the following items that are excluded from tax:
Cash security deposits
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.
You have the following two options for creating the advance return for tax on
sales/purchases:
You create the advance return for tax on sales/purchases in General
Ledger Accounting.
From the General Ledger menu, choose Reporting Tax Reports
General Advance Return for Tax on Sales/Purchases Advance Return
for Tax on Sales/Purchases .
You create the advance return for tax on sales/purchases in Contract
Accounts Receivable and Payable.
Special Considerations When Creating the Advance Return for Tax on
Sales/Purchases in General Ledger Accounting
As another option, you can fill the tax reporting date (field VATDATE) in the
document header of accounting documents as follows:
You can specify in Customizing for Contract Accounts Receivable and
Payable for each company code that the system fills the field either with the
document date or the posting date of the accounting document created
during the transfer to the general ledger. This ensures that tax reporting
takes into account the accounting documents that were created during the
transfer from Contract Accounts Receivable and Payable to General Ledger
Accounting. In this case, the system stores the tax reporting data neither in
the documents nor in the totals records of Contract Accounts Receivable
and Payable. Instead the system only sets the date in the document header
of the accounting document during the transfer.
If you choose this option, specify for your company codes which date the
system uses to fill the tax reporting date during the transfer to the general
ledger. To do so, in Customizing for Contract Accounts Receivable and
Payable choose Organizational Units Set Up Company Codes for
Contract Accounts Receivable and Payable and specify in the Tax
Reporting Date field which date is used to fill the Tax Reporting Date field
during the transfer.
If you make an entry there, you override any Customizing settings made
under Financial Accounting (New) Financial Accounting Global Settings
(New) Tax on Sales/Purchases Basic Settings Define and Check Tax
Reporting Date . This means that you can specify a different rule for filling
the tax reporting date for documents from Contract Accounts Receivable
and Payable.
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.
Exchanging Tax on Sales/Purchases Code for Credit Memos
In some countries, such as the Czech Republic, Slovakia and Slovenia, you are
required to delay reporting tax on sales/purchases on credit memos until you
receive confirmation that the credit memo was received by the customer. To
enable you to reflect this process in the system, the add-on SAP IS-UT CEE is
available in the industry components Utilities and Telecommunications. Follow
these steps:
1. You post credit memos with a temporary tax code. Until the customer
confirms receipt of the credit memo, you post the tax on a separate G/L
account, which you do not consider in the advance return for tax on
sales/purchases.
2. Once the customer confirms having credited the credit, you change the
status of the credit memo in the system and transfer the tax to the final G/L
account, which you consider in the advance return for tax on
sales/purchases.
The add-on SAP IS-UT CEE contains table /sapce/fk_ndcrn, in which
the system records credit memos with their statuses. It also contains
program /SAPCE/FK_NDCRN_TRANSF that you can use to transfer the tax
items to the final G/L account.
You exchange the tax on sales/purchases codes in event 0067. The system
processes event 0067, if the document to be posted has the following
characteristics:
The document is not statistical and it is not a down payment.
The tax on sales/purchases code is filled.
The document is not cleared.
The balance of credits and receivables is less than zero (credit
memo).
CAUTION
The basis for the calculation of the newly determined tax on
sales/purchases code is not allowed to differ from the basis for the
calculation of the original tax on sales/purchases code. That means that the
percentages must be the same.
NOTE
If there is no tax on a credit memo, the system immediately posts it with the final
tax code to the final G/L account.
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.
A VAT registration number is entered for the affected business partners.
Postings and reversals fulfill the following prerequisites:
Posting The document is not a sample document (FKKKO-
XMBEL = SPACE).
The document item is not statistical (FKKOP-STAKZ =
SPACE).
The document item is not a down payment or a down
payment request (FKKOP-XANZA = SPACE).
The document item contains a tax on sales/purchases
code (FKKOP-MWSKZ <> SPACE).
The tax on sales/purchases code contains an EU tax
code (see the attributes of the tax on sales/purchases code in
Customizing for Financial Accounting (New) under Tax on
Sales/Purchases Calculation Define Tax Codes for Sales and
Purchases ).
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 The reporting date type that applies is the one entered in
Date Type Customizing at the time of the posting.
(DATTY) The system uses the reporting date type entered in Customizing
if no tax reporting date is entered in the document.
If a tax reporting date is entered in the document, the system
ignores the Customizing setting for the reporting date type and
uses the Tax Reporting Date as the reporting date type.
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 If multiple FKKOP lines were posted with the same key data
Number (BUKRS, DATTY, DATUM, GPART, OPBEL), then the system
(LFDNR) generates an additional entry. The sequence number then
receives the next highest number.
Country The system calculates the tax base amount in the country
Currency currency. In doing so, the system first determines the country of
(LWAER) the company code and then the country currency from
table T005 (field WAERS). If a currency translation is necessary,
but this fails, because, for example, there are no exchange rates
entered in Customizing, then the local currency is used as the
country currency.
Country for The system always fills this field with the country of the company
Tax Returns code.
(LSTML)
Number of This field is only filled for a reversal. It contains the document
Reversed number of the reversed document.
Document
(STBEL)
Name of Depending on the business partner category, the system fills the
Business field with the last name (category Person), the Name1 field
Partner (categoryOrganization) or Name1 field (category Group).
(NAME1)
Cleared Items
Definition
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.
Structure
If statistical items are not considered, the balance of a clearing document is zero
for all of its items and all items it cleared.
Manual Account Maintenance
Purpose
If open items exist in an account on the debit (invoices) and on the credit sides (payments
on account, credit memo), you can clear or partially clear these items using account
maintenance.
Prerequisites
You can only post clearing if the amounts to be cleared balance to zero, or if the balance
is smaller than the assigned tolerance for small differences. You can only process open
items for which no clearing restriction is indicated. Items with clearing restrictions cannot
be selected. A clearing restriction only allows the clearing of the item within certain
transactions. A budget billing payment for utilities can thus only be cleared during a final
settlement.
Process Flow
10. ...
34. 1. You select the items to be cleared (see Selecting Open Items).
35. 2. You enter the parameters for posting the clearing document
(see Parameters for Clearing Documents).
36. 3. You can have the system provide you with a proposal for the
clearing (see “Automatic Assignment of Open Items” in the corresponding
application).
37. 4. You process the open items and assign them to clearing amounts
(see Processing Open Items).
38. 5. You post the clearing document once you have assigned all
amounts as desired (see Posting Clearing).
Result
The clearing is always documented by a clearing document that is created during the
clearing process. The selected items are cleared. Automatic postings for cash discounts,
taxes, and exchange rate differences are included in the clearing document. The
subsequent postings (down payments, charges) are also included in the clearing document
when clearing statistical items (down payment request, statistically posted charges)
(see Automatic Postings During Clearing).
Automatic Account Maintenance
Use
If you want to carry out account maintenance for a large number of contract
accounts or business partners, in addition to manual account maintenance, you
can use the mass transaction Automatic Clearing.
Prerequisites
You have made the settings for clearing control for creating an automatic clearing
proposal in Customizing for Contract Accounts Receivable and
Payable underBasic Functions Open Item Management Clearing Control.
With the settings that you make under Business Transactions Automatic
Clearing, you can also influence how the clearing documents are composed by
assigning corresponding grouping variants to define whether a clearing
document is to be posted, for instance, for each contract account, for each
contract reference, or for another item grouping.
See also the documentation for the individual IMG activities.
Features
The report selects the open items that correspond to the selection criteria and
clears them according to the settings you have made in Customizing for clearing
control.
In addition, you can group selected items for a business partner or contract
account into groups at event 0591. If you use grouping variants, then the groups
that are formed with them are further subdivided in this event. The system then
calls the clearing control per group and can then, when there are suitable
postings, post several clearing documents. Items that can only be partially
cleared or not cleared after grouping and assignment, you can continue to group
again in an iterative process. In this way, clearing control has the opportunity to
assign the items again in a subsequent call. This means that you can define a
series of groupings with a decreasing level of detail and clear an item in a single
run in several steps with several partial clearings. You can return messages for
the grouping logic; these are written in the application log.
Activities
11. ...
39. 1. To start the report, choose one of the following paths:
○ Roles
Receivables
Administration(SAP_FI_CA_RECEIVABLES_ADMINIST) Automati
c Clearing
○ SAP Easy Access screen
Periodic Processing For Contract Accounts Automatic 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.
Features
Scope of reset
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
System activities
Using the Reset Clearing function, the system carries out the following actions for the
clearing document number you specify:
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.
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.
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.
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:
Receivables/credit: Items according to the line layout variant selected
Down Payments
Totals: Summation of items in categories such as open receivables,
payment on account postings, down payments, and balance display of the
selected items.
Payment list: Display of the incoming and outgoing payments with the
following information:
Date, amount of payment
Items cleared with the payment
Items posted on account
The display in the ALV Grid Control is similar to the list display. However, the
detailed display of a payment in the ALV Grid Control is not on the tab
page Payment List in the normal list; instead, you double-click on the payment to
display the details. This takes you to the document display. There you can
display the items of the clearing document and the items thus cleared.
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 an additional selection screen in the account balance that
meets your specific requirements.
Features
To display an additional selection screen in the account balance, you have the
following options:
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
can use function module FKK_FPL9_SAMPLE_PAI as a template for the
PAI module.
3. Define a subscreen with your selection fields in Screen Painter.
4. Create a report that calls the
module FKK_LINE_ITEMS_WITH_DIALOG with I_FKKEPOSC-
ANWND = INITC.
5. Create a report transaction for the report you created in step 4.
6. In Customizing for Contract Accounts Receivable and Payable, choose
Basic Functions Postings and Documents Document Screen
Preparations Include Own Fields in Detail Screens . For
program SAPLFKL9, enter the application INITC and enter the objects you
created in the previous steps under screen number, program, and PAI
module.
To integrate the selection screen in the standard account balance, 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
can use function module FKK_FPL9_SAMPLE_PAI as a template for the
PAI module.
3. Define a subscreen with your selection fields in Screen Painter.
4. In Customizing for Contract Accounts Receivable and Payable, choose
Basic Functions Postings and Documents Document Screen
Preparations Include Own Fields in Detail Screens . For
program SAPLFKL9, enter the application INIT and enter the objects you
created in the previous steps under screen number and PAI module.
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 non-
amount 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 140 140 140
account
Down payment 160 160 160
Down payment 390 390 390
clearable
Features
Cursor position Result
In the list The system searches for all items with the
For example, on the value 06/01/2002 in the Doc.Date field
fieldDoc.Date 06/01/02
On the column header A dialog box appears where you can enter
For search values for the field Document Date.
example, Doc.Date column Afterwards, the system displays all items that
match the search criteria.
Outside of the list The system displays, one after the other, a
dialog box for selecting search fields and a
dialog box for entering search conditions. You
must have defined the search fields in
Customizing (see IMG structure Contract
Accounts Receivable and Payable Basic
Functions Account Balance
Display Choose Fields for Search
Function). There you can specify all of the
fields of the business partner item as search
fields.
Use
Prerequisites
You are using Event 1203 (see IMG structure: Contract Accounts Receivable and
Payable Program Enhancements Define Customer-Specific Function Modules).
Features
Color Meaning
Green Paid
Yellow Not paid, not yet due
Red Not paid, overdue
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.
The account balance display integrates numerous functions that you can use to:
Display further information (such as histories) for the displayed items
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
For Installment Plan Item: The system displays the installment plan for the
Installment Plan installment plan item.
Source Receivables
Collective Bill Line Items The system displays the line items that belong to the
collective bill item.
Line Item Bundle The system displays the line items that belong to the
bundle item.
Cash Security Deposits The system displays the cash security deposit for
the cash security deposit request document.
Budget Billing Plan The system displays the budget billing plan for the
budget billing plan document.
Interest Supplement The system displays the interest supplement for the
interest document.
Dispute Case The system displays the dispute cases for the
document in Dispute Management.
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 For a payment document from the payment run, the system
Run displays the payment data (bank data, payment method) in a
dialog box.
From Payment For an incoming payment, the system displays the bank data
Lot from the payment lot.
From Returns For a returns document for an incoming payment, the system
Doc displays the payment data from the returns lot.
From External For a payment that was entered at an external cash desk, the
Cash Desk system displays the payment data.
Payment Usage In a dialog box, the system displays the receivables and
credits for which the payment was used.
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 The system offers the items that To have the system
you currently selected for mass offer only those
change. This applies even if you items for mass
reduced the number of items change that are in
using the search after you the current item
selected items. Also in that selection of the
case, the system transfers only account balance,
the currently displayed items to define event 1256
the mass change. and set the
E_ADD_CUST-
XMCFI indicator in
your
implementation.
Budget Billing Plans The system displays the budget The display is
billing plans for the business implemented using
partner, contract account, and event 1215.
contract – provided they can be
determined uniquely.
Dunning Notices The system displays the The system calls
dunning history for the contract the initial screen of
account or for the business the
partner and contract account – reportRFKKMA02.
provided it can be determined
uniquely.
Dispute Create: The system asks for the The prerequisite for
Cases(Create, Display) necessary data for creating the this is that you are
dispute case in SAP Dispute using SAP Dispute
Management and creates the Management and
dispute case. you have made all
Display: The system navigates necessary system
to the initial screen of settings for the
the Dispute Cases for Account integration.
Balance (RFKKDM00) report in
order to display existing dispute
cases.
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).
Change Business The system navigates to the transaction for changing the
Partner business partner.
Change Contract The system navigates to the transaction for changing the
Account contract account.
Change Contract The system navigates to the transaction for changing the
contract.
Account Balance Display by Snapshot
Use
For individual business partners whose contract accounts have a large number of
items, you can create the account balance display from a preselected set of
items – a snapshot.
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and
Payable under Basic Functions Account Balance Display Define Business
Partner for Creation of Snapshots, you have entered business partners with large
numbers of items. This setting is one of the current system settings and,
therefore, you can access it in the menu under Current Settings (Business
Partner for Snapshots).
Note for the industry component Insurance
You can only use snapshots in the account balance if there is exactly
one insurance object-business partner relationship for the selection
criteria entered.
Features
The system manages the business partner for whom you create an item set in
table TFK021_SNAP. Changes to this table are current settings, which means
that you can also make entries in the productive system. You use report
RFKKSNAP (SAP menu: Account Account Balance Snapshot) to create the
current dataset for all (or selected) business partners in this table and save it as
a data cluster in the database in the form of a snapshot.
When you call up the account balance display, the system checks whether a
unique business partner can be determined from the selection conditions.
If the system has determined a business partner and a snapshot exists for this
business partner:
12. ...
51. 1. The system imports this snapshot.
52. 2. The system checks the current selection conditions.
53. 3. The system displays the result in the list with corresponding
information that the data is not up-to-date and with the date of the snapshot.
If you use account balance roles or event 1210 such that several
selections are derived from one selection condition, the system does
not evaluate the snapshot.
For installment plans, the snapshot contains the installment plan items
and not the original item for these installment plan items. Therefore, if,
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.
Use
The business partner has open items for settlement. You therefore want to send
your business partner a payment form .
Procedure
1. On the initial screen of the account balance, enter the business partner or
the contract account and choose Continue.
2. From the menu, choose Environment Create Payment Form.
A dialog box appears for you to enter the data required for creating the
payment form.
3. On the Payment Form Content tab page, specify the number of payment
forms required and the amount category. You can:
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.
5. If you choose Continue, the payment form is printed on the printer
requested immediately. If you choose Set in Print Dataset of Mass
Printing, the correspondence is created in the next correspondence print
run.
Result
Use
Procedure
1. In the basic list of the account balance display for the business partner
concerned, choose Environment Create Account Information.
A dialog box appears in which all the business partner items are listed.
2. On the Item Selection tab page, deselect the items that you do not want to
appear in the account information.
3. If you want to charge the customer for sending account information, define
the appropriate charges schedule on the Charges Posting tab page.
4. On the tab page Print Parameters, define an application form and select
an output device.
5. Choose Continue or Set in Print Dataset for Mass Printing.
Result
The account information is output on the printer you selected or created with the
next correspondence print run.
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).
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
● Form (SAPscript, Smart Form, or SAP Interactive Form)
● SAPscript texts (SAPscript)
● User exit includes
● User top includes
● Generated print program
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:
● The SAP application
● Customer-defined configurations and implementations of user exits
● Calls of the components SAPscript, Smart Form, and SAP Interactive
Forms.
Application forms are usually defined in Customizing tables or master data in the
application. An application form is printed by calling the module EFT_PRINT that
then calls the generated module for the application form.
Collection
Definition
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
collection’s 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.
An application form is a configuration object from which a runtime object in the form of
a function module is generated. The following is a description of how the runtime object
is called from an ABAP program to print an application form.
Integration
Form printing is called exclusively via central interfaces of the Print Workbench.
Activities
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)
Documentation of business processes
(for example, notification about the creation of a standing order,
confirmation of termination, installment plan agreement)
The Correspondence application component supports you when creating periodic
and event-controlled correspondence. The main focus is on the creation of
standardized mass correspondence by the application.
Creation Types of Correspondence
Correspondence is created:
Event-controlled if correspondence is required for a specific business
transaction (for example, confirmation of a change of address).
The system creates correspondence as a single run when it executes the
respective application program.
Periodically if correspondence is required for business transactions that
occur regularly (for example, bank statement).
The system creates correspondence as a mass run when it periodically
executes the respective application program. Using the selection criteria of
the program, you can define which business objects are to be considered
when you create correspondence (for example, confirmations of execution
for standing orders, invoices).
Integration
The system controls the creation and output of correspondence using the
following application components:
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).
SAPscript, Smart Forms, PDF-Based Forms
You can design the layout of correspondence and transfer data
with SAPscript, Smart Forms, and PDF-based forms.
The following sections explain the processes and functions of the
correspondence tool in more detail. For more information on the Print
Workbench andSAPscript, Smart Forms, and PDF-based forms, see the
documentation on these components. To do this, see the documentation
at help.sap.com and then enter one of the following paths SAP
NetWeaver Release xx SAP NetWeaver Application Platform (SAP Web
Application Server):
Cross-Application Services Print Workbench
Business Services Smart Forms/PDF-Based Forms/SAPscript (BC-
SRV-SCR)
Creation of Standardized Correspondence
Constraints
The following functions are not part of correspondence creation and need to be
performed in an output management system:
Automatic assignment of marketing material for a correspondence
Grouping multiple correspondence to enable them to be sent together (for
example, sending a bank statement, a confirmation of a standing order, and
a change to conditions together)
etermining Correspondence-Specific Data
Use
Determination of Sender in Contract Accounts Receivable and Payable
The standard company code resulting from the contract account noted in the
correspondence entry is used as the sender. You can use event 0760 to create
settings for your own installation.
Determination of Recipient in Contract Accounts Receivable and Payable
Usually, the business partner in a business process receives
correspondence. For most correspondence types, you can define alternative and
additional recipients.
● An alternative correspondence recipient replaces the original one so that
correspondence is only sent to the alternative recipient.
● An additional correspondence recipient is added to the business partner
so that both the original business partner and the additional recipient both
receive correspondence.
You can define an alternative correspondence recipient at the contract
account/business partner level which is then used for all types of
correspondence. This then becomes your standard correspondence recipient.
You can define one alternative and an unlimited number of correspondence
recipients for each correspondence type.
If you enter a correspondence recipient meant only for one type of
correspondence, the standard correspondence recipient will not be used.
As an alternative to entering a partner ID directly, you can define a
correspondence activity. These correspondence activities determine alternative
and/or additional correspondence recipients algorithmically. This can be useful,
for example, for determining a broker or a vehicle registration center.
You can use event 0770 to create settings for your own installation.
Determination of Address in Contract Accounts Receivable and Payable
You can define one address type for each correspondence type.
Correspondence of this type is then sent to this address type.
In event 0773, you can influence the address type used for the address
determination. The event runs when the address number for correspondence is
determined. You can therefore determine a time-specific address if there are
several addresses with different address types in Customizing for a business
partner.
Integration
If you have defined alternative or additional correspondence recipients, you can
perform a recipient simulation at contract account level (in industry
componentInsurance, this is done at insurance object level) to check which
correspondence recipients were defined.
For alternative or additional recipients, you can also define correspondence
roles in the master data. The correspondence role allows you to determine the
recipient address type, and also to define special application forms.
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:
● Suppress company code determination
● Suppress recipient determination
● Suppress sender determination
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 Country-
Specific 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:
● Output in SAPscript format (see SAP NetWeaver Library SAP
NetWeaver by Key Capability Application Platform by Key
Capability Business Services SAPscript (BC-SRV-SCR) BC
SAPscript: Printing with Forms)
● Output in raw data format for further processing in an external text
processing system (see SAPscript Raw Data Interface).
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).
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 application-
specific 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
with the quick info text Change Display change history for individual
Documents correspondence entries
Changes to status, deferral date, and
date of entry are displayed
with quick info text Change Status of Assignment of correspondence status
Correspondence to individual correspondence entries
with the quick info text Display Displays a document from the optical
Correspondence Archive archive
You can also use the following functions for inbound correspondence:
Pushbutton Function
with the quick info text Set Date of Define date of receipt of
Receipt of Inbound Correspondence correspondence
with the quick info text Deferral Date Postpone the date on which
of Inbound Correspondence correspondence is due.
The deferral date is taken into account
when youdun inbound correspondence.
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
Set date of receipt (only for inbound correspondence)
Set date of deferral (only for inbound correspondence)
Manually change the amount
Activities
To call up the correspondence history of the correspondence tool, in the SAP
menu choose Cross-Application Components Correspondence Display
Correspondence History.
To call up the correspondence history from the application, in the SAP menu
choose Account More Information Correspondence History.
The data to be displayed is selected in the same way in both transactions. See
the Displaying Correspondence History section of the correspondence tool.
3 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.
If you want the workflow to start before an entry is created in the
correspondence container, enter CW as the Notification Type.
(If you do not want to use a workflow, enter CD as the Notification Type. )
4. Enter the Adobe form and the interface.
5. At the Characteristics level, enter the characteristics for the interface of
the interactive forms. Enter a function module for loading the
correspondence data. If you want to use the data of the correspondence
header (master data set, application object), define a characteristic of the
typeFKK_CORRM_EXTERNAL_DATA.
6. Define a BAdI for additional functions (such as, generating address data).
7. Generate the interactive form and create the layout for the
correspondence.
8. Choose the Additional Data for Scenario pushbutton. In
the Create Notification field, enter workflow template WS31000009 for the
ISR standard workflow.
9. Choose the Assignment of Processors pushbutton to enter the users who
are allowed to approve the correspondence requests.
10. Activate the linkage for the ISR notification event CLOSED. To do so, on
the SAP Easy Access screen, choose Tools Business Workflow
Development Definition Tools Events Event Linkages Type
Linkages .
Customer Contacts
Purpose
This component logs all customer contacts that were saved from this component
or automatically from other components and displays them. This includes
contacts initiated by the customer such as telephone calls, as well as contacts
initiated by the utility company (such as letters or dunning notices). In the display,
you can list customer contacts by type, period, and medium for example.
Analyzing customer contacts provides information on the efficiency of business
processes and the capacity of customer service representatives.
Implementation Considerations
This component is optional. You need it if you wish to log and manage your
customer contacts.
Integration
The Business Object Repository (BOR) contains the following Business
Application Programming Interface (BAPI) for customer
contacts:PartnerContact.CreateFromData (create contact with data). For general
information on BAPIs, see the BAPI User Guide and the BAPI Programming
Guide (CA-BFA). For more detailed information, see the documentation for the
individual BAPIs in the BOR.
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.
Customer contacts can be created at any time. These may be incoming contacts from the
customer or outgoing contacts that you initiate yourself (telephone calls,
correspondence).
Integration
You can have the system create outgoing contacts automatically when a form is
generated, depending on the form class.
Prerequisites
You should have made all the relevant settings in Customizing under Financial
Accounting Contract Accounts Receivable and Payable Basic
Functions Customer Contacts.
Features
You can attach any object links when generating a contact. An object link is a BOR
object reference. You define the allowed object references for each contact class and
contact activity in the Customizing settings for Contract Accounts Receivable and
Payable under Basic Functions Customer Contacts.
Industry-Specific Component SAP Media
interaction History
Find 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 By choosing Filter ( ) and the Delete Filter pushbutton, you can
switch between different views and, in addition, you can set a filter for
the contents of a view.
Printing By choosing the Print, you can print notes as PDF files.
Sort By clicking on a column header, you can sort the entries in the
column.
For certain business transactions, it may be useful to remove objects, such as line items,
from further processing until a specific condition occurs.
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.
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.
To check whether the condition still applies for the locks, and what consequences this has
(for example, deletion of locks), you have to check all conditional locks at periodic
intervals.
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and Payable, under Basic
Functions Dependencies Maintain Conditional Locks, you have entered a check
module for the lock type.
Procedure
83. 1. In the SAP menu, choose Periodic Processing For Contract
Accounts Check Conditional Locks.
84. 2. Assign a date ID and run ID that you can use later to identify the
program run.
85. 3. Enter the required selection parameters and schedule the program
run. For more information about scheduling program runs, see the
section Functions for Scheduling Program Runs.
As described in the example in the section Set Conditional Locks, to arrange the
payment of commission to the broker once the first premium has been received, run the
mass activity Check Conditional Locks. This selects all conditional locks and processes
the function module entered in Customizing and programmed in accordance with the
sample module FKK_SAMPLE_CHECK_DOC_PAYED.
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
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
the payment within debit memos transactions is a special case in general
payment requests. This can be used to represent standing requests and the
participation in debit memo collection procedure (for example vendor debit
memos for insurance amounts).
General requests can also be used in connection with the cash desk or cash
journal. This payment request process corresponds to the process described
underAssignment of Incoming Payments of General Requests.
Prerequisites
The following IMG activities must be carried out in Customizing of Contract
Accounting:
Define Number Ranges
Assign Number Ranges to Request Categories
Define basic settings for general requests.
Define Specifications for Clearing Documents for General Requests
Define settings for approving requests.
Define Specifications for Document Creation
Define Accounts for Receivables/Payables
Define Accounts for Revenue/Expenses
Define Funds Management (FM) Account Assignment Derivation
Assign External Transactions (for Public Sector Contract Accounting)
Define Interpretation Rules for Note to Payee
Process Selection Values from Note to Payee
Process Flow
1. You enter a general request with the request category acceptance request
or payment request. For a successful automatic payment assignment, it is
essential that you enter a unique contract object (referred to as contract in the
following description) with which the system can create a link to the
payment. Unique means that this contract is exclusively used in a general
request and only in one line.
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 Write-
Offs 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 Writing Off Items.
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 Write-
Off 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.
Workflow for Checking and Approving Requests
Use
You can hold requests and standing requests in a status that has to be
confirmed. A workflow is triggered for the confirmation, the last step in the
workflow being either approval or rejection.
Alternatively, you can approve requests via a worklist.
Prerequisites
You define which requests are to be approved via a worklist for each request
class, request category, or document type in the Implementation Guide
for Contract Accounts Receivable and Payable under Basic
Functions Requests Settings for Approving Requests.
If, instead, you want to approve requests in a workflow, or make the approval via
a worklist dependent on other criteria, you have to register an installation-specific
function module for event 5510 in the Implementation Guide for Contract
Accounts Receivable and Payable under Program Enhancements Define
Customer-Specific Function Modules.
Every time a request is saved, the function modules defined for event 5510 are
processed. All data from the request or standing request is passed on to these
function modules. There you can also suppress the entry of an approval reason
when a workflow is started.
Features
You can always trigger a workflow if approval is required for creating, changing
or deleting a request or standing request.
If approval is necessary for creating, changing of deleting, the function module
processed for call-up point 5510 provides the number of checks required in field
E_C4LEV. This helps to decide whether, for example, dual control (one check
required), triple control (two checks required) or more involved controls still are
required. The maximum permitted value for E_C4LEV is 9. You can make the
number of approval steps required is dependent on a freely definable range of
criteria. For example, you could prescribe triple control for all requests that
exceed a given amount. In addition to the number of approval steps required,
three more freely-definable parameters can be set that are then available for role
resolution in the workflow. This allows you, for example, to define which person is
authorized to approve a request that exceeds a given amount. If a value between
1 and 9 is given for the number of checks required, the system triggers event
APPROVALREQUIRED of object type CA_REQUEST when requests are
created, changed or deleted. A workflow can be registered for this event, which
sets off the approval procedure. For this purpose, SAP provides sample workflow
WS21000098. Role 21000065 is available for role resolution.
When a request or standing request is created, changed, or deleted, the
processor is required to enter a reason.
The recipient of the workflow can call up the (standard) requests in his/her inbox
and either approve or reject them.
Provided that a request or standard request is still in the workflow and has not
yet been finally approved or rejected, it has the status To Be Approved. No
documents can be generated from a request or standing request that still has this
status. If the request or standing request is approved, the status changes
toApproved. When a request is approved, depending on the settings in
Customizing, a document is either created immediately or you can post the
document using the transactions Create Documents from Requests/Create
Documents from Standing Requests. If deletion is approved, the status is set
to Deleted.
If the request or standing request is not approved, the status is changed from To
Be Approved to Saved. You cannot create documents from a request or standing
request with this status. However, the request or standing request is not deleted,
and the changes remain in effect.
Activities
To approve requests via worklist:
25. ...
96. 1. From the SAP menu, choose Request Approve Request.
The approval takes place using the clarification processing of Contract
Accounts Receivable and Payable.
97. 2. Enter the parameters required for selecting the requests and run the
program.
In administrator mode, all requests to be approved are displayed. If you
select the function Resubmission Cases, only those requests marked for
resubmission are displayed.
98. 3. Select the required entry and choose the button Clarify.
In the list you can use all the functions of the ALV Grid Control.
99. 4. On the detail screen, you can set the status required using the
buttons Approve and Reject in the application toolbar.
● Interest Calculation
● Dunning
● Collections Management
● Disconnection/Reconnection of a Utility Installation
● Returns
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
posting Collective Bills
Purpose
Joint processing and management of items for individual contract accounts in
one collective bill account.
Prerequisites
To use the functions described below, in the Implementation Guide for Contract
Accounts Receivable and Payable, under Program Enhancements Define
Customer-Specific Function Modules, enter FKK_COLL_BILL_CREATE_0063
for event 0063, provided this module is not already integrated in the industry-
specific module for event 0063. In the industry
components Utilities and Telecommunications, this module is already integrated
in the industry-specific module for event 0063.
Make the following entries in the Implementation Guide for Contract Accounts
Receivable and Payable:
Basic Functions Contract Accounts Number Ranges and Contract
Account Categories Configure Contract Account Categories and Assign
Number Ranges
Create a contract account category for collective bill accounts. Set the
indicator in the column CB (Contract Account Is Collective Bill Account) and
assign a number range to the contract account category.
Basic Functions Postings and Documents Document Maintain
Document Account Assignments Document Types Maintain
Document Types and Assign Number Ranges
Create a document type for collective bill documents and assign a number
range to this document type.
Basic Functions Postings and Documents Document Maintain
Document Account Assignments Maintain Defaults for Document Type
for Collective Bills
Define the document type that you defined in the previous step as the
default for creating collective bill documents.
The main and subtransaction for the collective bill item are determined in event
2222. You can overwrite industry definitions implemented for this event. This
event has already been defined for the industry component Utilities.
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
Due date for cash discount
Cash discount percentage rate
Currency
+/- sign of amount (credit/receivable)
In event 2225, you receive a selection of the collective bill documents that qualify
for the inclusion of the individual document according to the criteria described.
Here you can decide on a specific collective bill document or trigger the creation
of a new collective bill document.
In event 2220, you can also group the line items according to additional criteria,
such as company code and transaction, or prevent the creation of a collective bill
for specific items.
The collective bill reference is created automatically in event 0063.
When there is a posting to an individual account, for each new business partner
item entered, the system automatically creates a statistical posting document
(collective bill document) in the collective bill account assigned or links the
document with an existing collective bill document. This means that several
individual documents link to one collective bill document. However, further
individual documents are only included in an existing collective bill document if
the collective bill document has not been (partially) cleared or reversed. The
amount of the collective bill document is the total of the amounts of the individual
documents that belong to it. The general ledger-relevant posting, if required,
always takes place at individual account level.
In some special cases, no collective bill document is created when you enter
individual documents. For example, document line items with a clearing
restriction or documents explicitly excluded from the collective bill in event 2220.
When you post line items that do not link directly to a collective bill document
number whose contract account is however linked to a collective bill account, the
system fills the field Alternative Contract Account for Collective Bills (DFKKOP-
ABWKT) automatically.
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.
Use
Cash security deposits
The status is derived from the history of the request document and is
displayed but not saved when you maintain the security deposit.
Integration
If the status of a non-cash security deposit is changed, a BOR event is initiated which can
trigger a workflow.
Use
Tthe reason for request is saved in the security deposit for information purposes, and,
where cash security deposits are concerned, also in the request document.
Structure
Define the request reasons in Customizing (see Implementation Guide for Contract
Accounts Receivable and Payable, Business Transactions Security Deposits).
Integration
In the Utilities Industry component, you can enter the reason for the request when
processing the move-in for the automatic creation of a cash security deposit.
Use
The security deposit category is stored in the security deposit for your information.
Structure
Define the permitted categories in Customizing (see Implementation Guide for Contract
Accounts Receivable and Payable, Business Transactions Security Deposits).
Cash Security Deposit Request Document
Definition
Use
The document number is stored in the security deposit for your information.
Structure
You have defined request reasons for cash security deposits (see Implementation Guide
for Contract Accounts Receivable and Payable under Business Transactions Security
Deposits Define Request Reasons for Security Deposits).
You have created a number range with internal number assignment and the document
type for the request documents for cash security deposits and assigned them to the
application component in the Customizing parameters (see Implementation Guide
for Contract Accounts Receivable and Payable Business Transactions Security
Deposits).
For the industry components Utilities and Telecommunications, you also have to maintain
main and subtransactions and the account determination for cash security deposits in
Customizing. To do this, choose:
Basic Functions Postings and Documents Document Maintain Document
Account Assignments Maintain Main Transactions for IS-U/IS-T and Maintain
Subtransactions for IS-U/IS-T and Define Account Assignments for Automatic
Postings Automatic G/L Account Assignment.
Then make the following entries in the Implementation Guide for Contract Accounts
Receivable and Payable:
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.
For event 0860, you can define follow-on actions for security deposits that meet certain
criteria. For example, that a clerk retrieves a non-cash security deposit from storage if the
return date is reached within the next week.
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.
Autom. Creation of Security Deposits During a Move-In (IS-UT)
Use
A cash security deposit can be created automatically when a customer move-in is entered
in the system.
Prerequisites
In the Customizing settings for the move-in, the indicator Deposit Automatically
Created must be set in the Contract Level Control Parameters. (SelectCustomer
Service Process Execution Move-In/Out Move-In Define Move-In Control
Parameters at Contract Level).
Procedure
37. ...
136. 1. Call the transaction for entering a customer move-in: Customer
Service Process Execution Move-In Create.
The screen Create Move-in: Initial Screen appears.
137. 2. In the Contract subscreen, enter the reason for the request and
the amount of the request.
Result
When you save the move-in document, a cash security deposit and request document, is
posted and entered in the log.
Roles
Cash Security Deposits/Security
Deposits (SAP_FI_CA_CASH_DEPOSIT) Display Security
Deposit or Change Security Deposit
SAP Menu
2. Enter the number of the security deposit required and select Continue.
Release cash Edit Release You can offset the released portion
security deposit in Partially or pay it out if a payment method is
part defined in the partial release.
Change amount of Edit Clear You can reduce the amount of the
cash security Remaining cash security deposit receivable
deposit request Receivable later using the function Clear
Remaining Receivable, or increase
or it using the function New
Receivable.
Edit New
Receivable In the first case, a part of the
original receivable is written off, in
the second case a new cash
security deposit receivable is
posted with reference to an existing
cash security, provided that this has
not been reversed or released.
You want to react to the change of payment method in the contract account of a business
partner.
Features
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
Check Management
Receipt Management
Processing Credits
Purpose
This component enables you use the payment program to process incoming and
outgoing payments.
Features
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.
Check Management
Use
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
Roles
SAP Menu
Payments Check Management
Check Escheatment
To start the escheatment process, you have to select the checks that are to be
escheated.
Features
You start the escheatment process by selecting all escheatable checks.
Escheatable checks are those that meet the following criteria:
Their status is open and they were not yet cashed.
The escheatment process was not yet started for them. (The check does
not contain an escheatment date.)
They are older than the number of days specified in Customizing.
Their amount is greater than the amount specified in Customizing.
The program generates a persistent worklist containing the checks that can be
escheated and sets the escheatment date and receiver code for these checks
based on the last known address of the payee.
You can also change the receiver code in event 0431.
Activities
1. On the SAP Easy Access screen, choose Periodic Processing Data
for Externals Tax Authorities Escheatment Start Escheatment
Process .
2. Limit the selection of checks to be escheated by making entries in
the Selection Criteria group box.
3. If you have not made any specifications for the number of days until
escheatment in Customizing, make an entry in the No. of Days Until Esch.
Proc.(number of days until escheatment process) field.
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.
After you have started the escheatment process, you have to create notification
letters for the business partners affected.
Features
The system prints the notification letters using correspondence
type 0046 (Check Escheatment Letter).
The notification letters inform payees that they are in possession of an uncashed
check, which will be automatically escheated after a certain time period expires.
The system addresses the letter to the last known address of the business
partner. If the check is included in automatic processing, then the system sends
the letter automatically. If you are using manual processing, you can decide if
you want to send correspondence or not.
In event 0431, you can prevent correspondence from being created.
SAP provides the PDF form Check Escheatment Letter
(FI_CA_CHECK_ESCHEATMENT_PDF).
If the recipient does not respond to the notification letter, then the check is
escheated automatically on the escheatment date as part of the further process
flow.
If the recipient does respond, then you can remove the check from the automatic
process flow and transfer it to manual processing.
Activities
To create notification letters, on the SAP Easy Access screen, choose Periodic
Processing For Contract Accounts Correspondence Print . The program
creates notification letters. For more information, see Printing Correspondence.
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.
If a business partner responds to the notification letter, then you can react
accordingly during clarification processing.
Prerequisites
Escheatable checks are included in clarification processing in these cases:
You defined event 0431 so that certain checks are selected for manual
processing.
You set process category 2 (Manual) for checks already in the
escheatment process. On the SAP Easy Access screen, choose Periodic
Processing Data for Externals Tax Authorities Escheatment
Change Escheatment Data .
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.
The system cannot determine a receiver code.
Customizing is not set up or is set up incorrectly.
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:
Cashing the check in n days
Postponement of the escheatment date, for example, because the check
needs further clarification
Notification that the check was lost
You can:
Issue a replacement check
Search for the current address of the payee in the business partner data
Create a notification letter
Set the check for resubmission
Specify an escheatment date that overwrites the escheatment date set by
the program
Change the receiver code in accordance with the last known address of
the payee
Specify the address to which the notification letter is sent
Transfer a check to automatic processing
The check is escheated when the escheatment date is reached only when
automatic processing is used. If you close manual processing (for instance, by
entering a new address), then you must then transfer the check for automatic
processing. The check escheatment is then automatic when the escheatment
date is reached. If you have not yet created a notification letter, the system
informs you of this.
NOTE
If a check is specified for manual processing, then the check cannot be
escheated, even if the escheatment date has been reached.
Activities
1. To manually process the clarification worklist, on the SAP Easy Access
screen, choose Periodic Processing Data for Externals Tax
Authorities Escheatment Clarification .
2. In the tree structure on the left side of the screen, choose the parameters
you want to use for selecting a check. To do so, position the cursor on a
field and choose (Copy Selected). In the same way, you can remove
individual selection criteria by choosing the pushbutton (Delete Selected
Objects).
3. Enter the selection criteria and choose (Execute).
For more information about clarification processing, choose the (Selection
screen help) pushbutton in the application toolbar.
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:
Activate Receipt Management under Basic Functions Postings and
Documents Basic Settings Maintain Central Posting Settings. To do
this, set the indicator Receipt Management Used. If you have set the
indicator, when you post payments, required clearing information is
recorded in the system; this information is then used in Receipt
Management when you (repeat) print receipts.
Define the Specifications for Managing Receipts under Business
Transactions Payments Processing Incoming/Outgoing
Payments Receipt Management.
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.
Under Business Transactions Payments Processing
Incoming/Outgoing Payments Receipt Management Define Reasons
for Repeat Print, you can also define reasons for a repeat print.
Features
The list is output with the ABAP List Viewer. You can define the display by
defining the required layout. You can select layouts in the menu under Output
Parameters.
Activities
38. ...
138. 1. Choose Payments Receipt Management.
139. 2. Specify the parameters that you want to use to select receipts.
Under Specifications for Selection you can restrict your selection further:
Only output receipts for which stamp tax is posted
Only output payment documents for which a receipt was printed
Also output reversed receipts
140. 3. Depending on the display required, choose with the quick info
text Execute or Without Line Item Display.
If you choose with the quick info text Execute the system displays the receipts
that correspond to the selection criteria. For payment documents for which no
receipt exists, the program simulates a line with print information for the 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.
If the corresponding payment document has already been reversed, you
can reverse printed receipts in the list by selecting the corresponding line
and choosing Reverse.
Doubleclick on a line to display the payment document.
Using the button Mass Receipt Print you can navigate to the
transaction for the mass print for receipts.
If you select the button Without Line Item Display, the amounts, net amounts,
and stamp tax amounts are output totaled by company code, origin of the
payment document, clerk, branch, and cash desk. The output is in the ABAP List
Viewer. By selecting the totals line you can display the line items considered in
the totals line.
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:
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
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_*.
NOTE
Activating the key replacement does not have any effect on the data itself. The
system can always decrypt credit card data that was already stored in encrypted
form.
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.
Rule for calculating interest. Key for determining the factors that influence interest
calculation.
Use
Structure
You define interest calculation rules in Customizing (see the IMG structure Contract
Accounts Receivable and Payable Business Transactions Interest
Calculation Item Interest Calculation Define Interest Calculation Rules). Interest
rates based on date and amount are defined for an interest calculation rule. You can also
calculate interest on the basis of whole months. Alternatively, an interest calculation rule
may refer to a reference interest rate. Other influencing factors are:
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 Description
factor
Tolerance days Granted to a customer in the case of overdue items.
Interest is not calculated on debit items before the
tolerance days have been exceeded. If the tolerance days
have expired, the system calculates interest from the
original due date. If clearing takes place within the
tolerance period, overdue interest cannot be calculated.
Transfer days Consider the time needed for a payment method. Interest
is calculated from the date that equals due date +
tolerance days.
Transfer and If both transfer and tolerance days have been entered for
tolerance days an item, they are considered separately.
Example:
If one transfer day and five tolerance days are granted,
and expire five days after the due date, the interval from
the due date + transfer days (exclusively) is considered. If
clearing takes place within five days, no interest can be
posted.
Interest frequency The interest frequency prevents interest from being
calculated on an item after a very short time. Since
demanding interest (for example, sending an interest
notification) is time-consuming and involves costs,
interest is not calculated unless the interest period
determined by the interest frequency has expired. The
interest frequency is made up of a number field and a
time unit.
SAP recommends summarizing items that the system rounds before the interest
calculation (for example, for rounding to complete 100) and subitems before the interest
calculation. To do this, set the indicator Summarize Subitems before Interest
Calculation in the interest key (Implementation Guide for Contract Accounts Receivable
and Payable: Business Transactions Interest Calculation Item Interest
Calculation Define Interest Key). If you also set the indicator Consider All Subitems
for Interest Calculation, the system automatically selects missing subitems when
calculating interest on subitems. This ensures that interest is calculated on the whole
amount, even when receivables are split for technical reasons.
Event 2085 gives you even further options for summarizing items before the interest
calculation. There, for example, you can summarize items and, if you use different
interest rates for calculating interest on receivables and payables, use the interest rate for
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
Use
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
Purpose
You can display the results of interest calculation and create an interest
notification for the business partner in question using
the Correspondence application component (see Printing Interest Notifications).
Prerequisites
Process Flow
1. Select the business partner and/or contract account for which you want to
post interest.
2. The system determines the items due for interest with your selection
criteria.
3. Post the interest document. You may post any or all of the items matching
the selection.
You can calculate interest on debit items as part of the dunning run or in a
separate mass run.
Use
The system calculates interest only on those items for which it is able to
determine an interest key. An interest key can be assigned to contract account,
items or dunning levels. The system normally determines the interest key for
each industry, but can also do so on a customer-by-customer basis.
Generally, an interest key is determined as follows:
If no interest key has been entered in an item, the system checks for an interest
key entry in the contract account. If no interest key exists in either place, interest
cannot be calculated on the item. In other words, the item is interpreted as being
blocked for interest calculation even if an explicit interest block has not been set.
If a debit item has been dunned but no interest key is entered, the system will try
to determine a dunning key by looking at the dunning level of the item. If an
interest key has not been maintained there, the contract account is used.
Since interest, and in particular, debit interest, is only to be posted and requested when
the expense is justified, the system checks the amount limits.
Integration
The amount limit check is integrated into the Determining and Posting Interest process
flow and thereby into all other business transactions in which interest is posted.
Features
The check for amount limits is industry- or customer-specific and can also be integrated
if required (see Implementation Guide for Contract Accounts Receivable and
Payable Business Transactions Interest Calculation Item Interest
Calculation Maintain Amount Limits for Debit/Credit Interest). If you do not make
any settings, the amount that is the total of all interest items for a company code is
compared with the amount limit defined in the system settings. Interest is only posted if
the amount of all the interest items exceeds the amount limit. The check is company
code-specific.
To clear a late incoming installment payment, you can charge installment plan interest
(see Calculating Interest on Installment Plans). The installment plan interest can be based
on the installments or on the items in the installment plan. You can calculate interest on
an installment plan as follows (see graphic):
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.
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).
Use
You can use this option if you want to calculate interest only on open items, or
only on cleared items.
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
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:
Account
The German Fiscal Code stipulates that a grace period of five days must be adhered to for
payments by bank transfer when calculating penalty surcharges for public-law
receivables
In addition to this, it is not possible to start the interest calculation on the first day after
the due date; it can only be calculated starting from the nextworking day after the due
date.
Activities
If a customer-specific function module was defined with event 2090, the system
calculates the dunning interest that accrued between the last dunning run and clearing of
open items based on the entries made.
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 industry-
specific 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)
You can postprocess the dunning-relevant data manually in the
dunning proposal. If receivables have reached a specific dunning
level, you can lock the contract account or the service for a business
partner automatically in the dunning activities run. (See IS-T
Telecommunication Services in RM-CA Locking Services via the
Dunning Run (IS-T)).
Industry component Insurance (FS-CD)
The following dunning procedure types are supported:
Individual dunning notice
In an individual dunning notice, all items in a contract are
considered independently of one another. This means that you
can have several dunning procedures for one contract.
Total dunning notice
In a total dunning notice, all items in a contract are dunned with
one dunning procedure.
Multiple total dunning notice
A multiple total dunning notice can, in contrast to the total
dunning notice, contain several total dunning notices for one
business partner/insurance object relationship in parallel.
Contract dunning notice
In a contract dunning notice, only one current dunning
procedure exists at any one point in time. This refers to the
oldest item.
Account dunning
All items due for dunning for a contract account are dunned on a
cross-contract basis for account dunning.
The dunning procedures to be used are determined in the dunning
proposal run and saved in the item.
● Notes on reversal of dunning runs or dunning notices are not in force for
Collections/Disbursements.
● In Collections/Disbursements, you control the determination of dunning
procedures by defining a dunning variant for the contract account or the
insurance object-partner relationship (or a dunning procedure for the
document), instead of a dunning procedure. Notes on dunning control for
the contract account are also valid for the insurance object.
● 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.
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)
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
The dunning groupings in which the items are to be summarized
To determine the dunning balance, the dunning proposal run adds the amounts of the
items with the highest level in a dunning grouping and compares this total with the
amount limit for the applicable dunning level. If the amount limit is not reached, the
program adds the total of the amounts for the items with the next lowest dunning level to
the total and compares this total with the amount limit for this dunning level. The
procedure continues until the amount limit for a dunning level is reached. Dunning takes
place in the dunning level whose amount limit was reached.
The program uses this information to create a dunning proposal structured by dunning
groups. 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 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 application-
specific 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.
Creating Printed Records
Use
As part of a dunning run, you want to send dunning letters and payment forms.
Integration
You can prepare application forms using the Print Workbench component. You
then print the correspondence using the Correspondence component. The
following form classes are delivered as standard:
● FI_CA_DUNNING_NEW (Contract Accounts Receivable and Payable)
with the sample application form FI_CA_DUNNING_SAMPLE_SF (Smart
Form)
● IS_U_CA_DUNNING (Industry components Utilities, Telecommunications)
● ISM_CA_DUNNING (Industry component Media)
Features
Depending on the dunning activity, you can create documents for a dunning
notice in two ways:
2. ...
● The dunning activity run creates the documents via industry-specific or
customer-specific dunning activities. SAP does not recommend this
method.
● The dunning activity Create Correspondence Request creates
correspondence container entries that you print using correspondence
printing (SAP menu:Periodic Processing Correspondence Print).
In this case, you create the dunning letter itself using the print program from
the Correspondence component. In events 0770 and 0773, you can
determine the recipient and address for a dunning letter dependent on the
dunning level.
To avoid printing dunning notices that have already been reversed,
always print the documents immediately after the dunning activity
run. See SAP Note 526624.
Payment Forms
If you use the function modules *DUNNING_PR_CORR_CONT_0350 as a
dunning activity, you can also send a payment form for the dunned items and the
related interest and charges documents with the dunning letter. If the activity for
creating correspondence has not created a payment form number, you can
assign the payment form number using the function module
FKK_DUNNING_PF_NO_DET_0350. The internal and external payment form
numbers are saved in the dunning header and can be used to assign the open
items on payment receipt.
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.
Activities
In the Implementation Guide for Contract Accounts Receivable and Payable, under Basic
Functions Correspondence Archiving Define Archives for Paper Records, you
can define which object type is to be used for archiving. Object type BUS4401 is used as
standard for dunning notices. If however, you use object type CA_DUNNING for
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:
Automatically in the dunning run
Define the function module FKK_TRANSFER_CALL_LIST_1799 in event
1799.
Independent of the dunning run
Start report RFKKMADUTLTRANF. Make sure you read the report
documentation.
Using an installation-specific function module for event 0395, you keep mySAP
CRM up-to-date after you have transferred the data, for example, if an entry is
removed from the telephone list again as the result of a reversal of a dunning
notice.
You can asign the entries in the telephone list created in mySAP CRM to a clerk
automatically. Depending on the settings for the replication, you can enter the
clerk in CRM and/or FI-CA. The prerequisite for the automatic assignment is that
the clerk in CRM also exists as business partner in the system where FI-CA runs.
CRM middleware replicates the business partner Clerk and makes the
assignment to the contract account.
Maintenance in Contract Accounts Receivable and Payable (FI-CA)
In FI-CA, enter the required clerk in the contract accounts of your business
partners on the tab page General Data in the field Clerk Responsible.
Maintenance in CRM System
mySAP CRM portrays the clerk as a partner function using the business
agreement. In Customizing for CRM you define which partner function is to be
replicated in the corresponding field in the contract account.
Deleting Data Records No Longer Required
You can delete old entries that are no longer required – this decreases the
burden on the system. In the SAP menu, choose Periodic Processing Delete
Data Entries in the Dunning Telephone List. See the report documentation.
Activities
Make the following settings in the Implementation Guide for Contract Accounts
Receivable and Payable:
Configure the dunning activities under Business Transactions Dunning
Notices.
Using the component Customer Contact, your clerks can document
communication with business partners in the system. To enable this, carry
out the contact configurations for the program context SAPLFKKDUTL
under Basic Functions Customer Contacts Define Configurations.
Under Technical Settings Prepare Processing of Clarification
Worklists, you can adjust the functions of the clarification worklist. The
relevant application object has the key DUTL. In particular, here you can
define your own processing status and user commands. SAP delivers the
function module FKKDUTL_EVENT_UCOMEXIT_OTHER as an example
for user commands.
If you use the function module FKK_SAMPLE_0746_TEL_ITEM as a
dunning activity, you can also create a telephone list in Correspondence
Dunning(compare Dunning Incoming Correspondence).
Troubleshooting
The following information will help you analyze problems that occur in dunning
runs:
Notes for Error Analysis and Correction
Problem Cause/Solution
An item is not dunned. The item is not due yet or has been deferred.
The Print All Items flag is set and the item is only
an info item and therefore is not to be dunned.
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 master data groups in which the items are to be summarized
● The strategy for dunning the master data groups
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.
Activities
In the Implementation Guide for Contract Accounts Receivable and Payable, under Basic
Functions Correspondence Archiving Define Archives for Paper Records, you
can define which object type is to be used for archiving. Object type BUS4401 is used as
standard for dunning notices. If however, you use object type CA_DUNNING for
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.
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
In addition, you can integrate further events using a customer enhancement. In
Customizing you can place these events (business transactions) in context and
assign specific transactions to one another. You make the settings in the
Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions Dunning Collection History. For
detailed information, see the documentation for the individual activities.
Example
● The system assigns a correspondence to a specific installment plan if the
correspondence is an installment plan notification for this 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.
● The system assigns a payment to a specific promise to pay if the promise
to pay was closed by this payment.
You can use test series to determine which collection strategies achieve the
highest success rates during dunning.
Features
You define collection strategies in your system and assign these strategies to
contract accounts or contracts that you want to dun using the given strategy. To
optimize your collection process, you can compare newly designed strategies
with existing strategies. To do so, you can juxtapose an existing strategy (called
a champion strategy) and a new strategy (called a challenger strategy) in a test
series. This means, for a certain period of time you can use the challenger
strategy to dun a certain percentage of the master data that is actually subject to
the champion strategy. By subsequently analyzing how successful the dunning
was, you can determine which strategy is more effective. To compare the
strategies, follow these steps:
1. Using test series, you define which champion strategies you want to
replace with which challenger strategies. You also specify what percentage
of the master data the change is applied to. (On the SAP Easy Access
screen, choose Periodic Processing For Contract Accounts
Dunning By Collection Strategy Process Test Series for Strategy
Replacement .)
In doing so, you tailor each challenger strategy to just one champion
strategy.
2. You determine the master data, for which you want the system to replace
the strategy, and you replace the strategy. (On the SAP Easy Access
screen, choose Periodic Processing For Contract Accounts
Dunning By Collection Strategy Determine Master Data for Test
Series .)
3. By analyzing the time periods in which a champion or challenger strategy
was used, you can form conclusions about the efficiency of the given
strategy by means of reporting in Business Intelligence (BI) and by
using Success Valuation of Dunning Notices (on the SAP Easy Access
screen, choose Periodic Processing For Contract Accounts
Dunning ).
The system records which master data is assigned to which challenger strategy.
It automatically prevents the master data from being assigned to more than one
challenger strategy at the same time.
Both strategies are displayed in the dunning header. The dunning history informs
you if the dunning run is currently using the champion strategy or the challenger
strategy. (On the SAP Easy Access screen, choose Account Further
Information Dunning History .)
NOTE
At event 1038, you can exclude certain master data from being assigned to a
challenger strategy.
If you want to replace a collection strategy, for example because you have
determined the optimum collection strategy, you can replace it in a program run
in the master data of all affected business partners.
Features
You update collection strategies at the master data level (contract account,
contract account group, contract, contract group). In doing so, you can:
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:
Display the log for an update run
Execute an update run again for one that had errors
Undo an update run
For more information, see the program documentation.
Using a BRF or BRFplus trace, you can, in individual cases, interpret decisions of
the Business Rules Framework (BRF) or the Business Rules Framework plus
(BRFplus), and based on this you can make targeted adjustments to the check
rules in BRF or BRFplus.
Features
You trigger the recording of a BRF or BRFplus trace in the dunning proposal run
by setting the Trace Active indicator on the Dunning Parameters tab page. (On
the SAP Easy Access screen, choose Periodic Processing For Contract
Accounts Dunning Dunning Proposal Run .)
To reduce the load on your database, enter an amount of time after which the
BRF trace or BRFplus trace is released to be deleted. Enter this in the Days Until
Trace Deleted field. Based on the number of days you enter, the system
determines the date the trace expires and stores this date in the trace data
record. The system automatically proposes 30 days. However, you can change
this value. If you do not enter a value, the system automatically sets the
expiration date to December 31, 9999. Once the expiration date has been
reached, the system deletes the BRF trace or BRFplus trace automatically the
next time the dunning proposal run is executed. In the case of BRF or BRFplus
traces with the expiration date December 31, 9999, the system never deletes
them automatically. You delete these traces manually. On the SAP Easy Access
screen, choose Periodic Processing Delete Data Delete BRF Trace .
You can also use the same transaction to directly delete BRF and BRFplus
traces that do have an expiration date.
You can display recorded BRF or BRFplus traces using these methods:
Using the report Collections Management: Display BRF Trace
You call the report either from the SAP Easy Access screen or in the
dunning proposal run. On the SAP Easy Access screen, choose Periodic
Processing For Contract Accounts Dunning By Collection Strategy
Display BRF Traces . To call the report in the dunning proposal run, enter
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 use this component to disconnect a utility installation during a dunning run when
open items in the accompanying contract account are still unpaid after repeated dunning.
You can also use it to reconnect an installation once the items have been paid, or an
installment plan has been created.
You can find further information on disconnecting a utility installation during a dunning
run under Creating disconnection documents using a dunning run. A disconnection
document can also be created for a collective bill account when a dunning run is executed
for the collective bill account (See Creating disconnection documents for collective bill
accounts).
You can find further information on reconnecting a utility installation in the graphic
overview as well as reconnection through payment and reconnection through installment
plan creation.
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.
If a customer still has not paid, despite receiving repeated dunning notices, you can create
a disconnection document as part of the dunning run.
Integration
Activities
Make the following settings in the Customizing menu for Contract accounts receivable
and payable under Business transactions Dunning notices:
See also:
Reconnection overview
Reconnection via payment
Reconnection via installment plan creation
Minimum/maximum amount check of clearing amount
Propose contract-related reconnection
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
Creating Disconnection Documents for Collective Bill Accounts
When a collective bill account reaches the disconnection dunning level, the system
creates a disconnection document. You can use a workflow to inform an agent that a
disconnection has occurred for the collective bill account. The agent manually creates the
disconnection for the appropriate subaccount. If a payment is made for the collective bill
or the subaccount, or if an installment plan is created for the collective bill account, the
agent can be informed of this via the workflow task TS20500407. He or she can then
check whether the disconnected utility installation for this collective bill account should
be reconnected.
You must specify the notification of the agent via workflow task TS205500407 when you
allocate tasks to agents.
See also:
Reconnection overview
Reconnection via payment
Reconnection via installment plan creation
Propose contract-related reconnection
Minimum/maximum amount check of clearing amount
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
Reconnection Process: Overview
You can find the documentation on the accompanying workflows under SAP
Utilities Customer service Process execution Disconnection/reconnection.
This function allows you to reconnect a utility installation when an open item that
previously contributed to a disconnection has been cleared.
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.
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.
See also:
Reconnection via installment plan creation
Minimum/maximum amount check of clearing amount
Propose contract-related reconnection
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
This function enables you to reconnect an installation when an installment plan is created.
When the installment plan is created, the system calls event 3040 (installment plan is
created). This event allows further processing steps to be carried out after the installment
plan has been created.
When you select due, open items in order to created an installment plan, the system
checks whether the items have already been dunned. The system determines all dunned
items in the corresponding contract account and checks whether the items have triggered
a disconnection. Each of the selected, open items is marked as cleared. The total of the
clearing amounts corresponds to the total amount of the disconnection-relevant items
once all overdue, disconnection-relevant items have been included in the installment
plan. 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 all the disconnection-relevant items included in the installment plan are cleared, the
criteria for reconnection has been fulfilled.
If the items are to be proposed contract related, you must set the indicator Cntrt-rel.
prop (see also Propose contract-related reconnection.).
Once you have specified that the reconnection should be proposed contract-related, the
event disconnection obsolete(Disconnection.DisconReasonObsolete) is triggered for
every contract that fulfils the criteria for a reconnection. The event disconnection
obsolete then triggers the reconnection.
If you have specified that the reconnection should not be proposed based on contracts, the
system checks all contracts in the contract account. If the criteria have not been fulfilled
for at least one contract, the system does not trigger the event. If the installation is to be
reconnected, all contracts in the contract account must fulfill the criteria for reconnection.
If all contracts are under the disconnection dunning level, the event disconnection
obsolete is triggered and the reconnection started.
See also:
Minimum/maximum amount check of clearing amount
Propose contract-related reconnection
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
Minimum/Maximum Amount Check for Clearing Amount
When you check reconnection criteria in event R720, you can also execute a max/min.
amount check. This enables you to check the clearing amount of disconnection items
in one contract and in all contracts in a contract account. If clearing the
disconnection-relevant items fulfills the minimum/maximum amount specified, the
criteria for reconnecting the installation allocated to a contract are also fulfilled. The
standard specification is that the maximum/minimum amount during clearing must
correspond to 100% of the total amount of the dunned items.
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:
Propose contract-related reconnection
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
This function allows you to define which items are considered for the reconnection
proposal when an installment plan is created or an open, disconnection-relevant item is
cleared. You can use the following options:
Reconnection proposed per contract. The system checks the open items
of one contract (not all contracts) to determine whether the reconnection
criteria are fulfilled.
All contracts from the contract account should be considered for
reconnection. The system checks whether all contracts from the contract
account fulfill the reconnection criteria.
Only one of the two variants can be set in Customizing.
Procedure
50. ...
185. 1. In Customizing, select SAP Utilities Customer
Service Process execution Disconnection/reconnection Define
processing variants for disconnection documents.
186. 2. Select the processing variant DUNN (disconnection dunning level
has been reached).
187. 3. Select Details.
188. 4. Set the flag Cntrt-rel. prop (contract-related item proposal).
If you want the system to propose a contract-related reconnection, you must set the
indicator Cntrt.-rel prop must be set. If you want all contracts of the contract to be
considered, do not set this indicator.
See also:
Examples for the contract-related proposal of items
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
You have set the indicator contract-related item proposal. This means that the total
dunning amount for a contract is compared to the clearing amount of the disconnection-
relevant items for this contract. The system then checks whether a reconnection can take
place.
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.
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
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:
Examples for the contract account-related proposal of items
Disconnection/reconnection of utility installation: Workflows:
Examples for Contract-Related Proposal of Items
Example 1: Partial Payment of Contract-Related Items
You have not set the indicator contract-related proposal of items. This means that the
total dunning amount of the contract account it compared with the clearing amount of all
disconnection-relevant items for this contract account. The systems then checks whether
all installations for this contract account can be reconnected.
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.
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
See also:
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 follow-
up activities are:
Changes to the item
Setting a deferral date, a dunning block and/or a payment block for the
reopened receivables
Changes to the contract account
Setting a dunning block, incoming payment block, outgoing payment block
and/or changing the incoming payment method, from direct debiting to
payment on demand, for example.
You can also manually set a processing block with a certain time limit in order to
prevent dunning notices and debit memos being generated for a contract
account.
In an industry solution or a customer project, you can also realize the following
activities:
Connect processing to a workflow
Create and transfer information for the clerk responsible
Create correspondence for the business partner
The system records all data and activities in a returns history. Here, for example,
you can see the number of returns for a business partner. The system uses the
returns history to determine the creditworthiness of a business partner
You use predefined application forms in the Correspondence component to
print paper records such as return notifications. You define application forms
using the Print Workbench.
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
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
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
partner’s 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 partner’s 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
● The creditworthiness factor in percent
● Manual creditworthiness
Purpose
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).
Process Flow
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).
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).
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.
Displaying the Returns History
Prerequisites
At least one returns lot was entered, closed, and posted successfully.
Procedure
Roles
SAP Menu
You can structure the result list with predefined display variants (see
below).
3. Choose Continue.
All those returns that match the criteria you entered are displayed.
Result
Installment Plan
Definition
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
If a business partner is temporarily unable to pay his liabilities, you can enter a deferral
date in the item. You can reverse a deferral by deleting the deferral date in the item. You
can enter a deferral date in the item when you post or change a document. To cancel a
deferral date, use the transaction Change Document. If you want to display the deferral
date of an item, use the transaction Display Document.
Procedure
52. ...
193. 1. Choose one of the following paths:
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.
○ Delete installments
○ Calculate or delete interest
○ Create or delete an installment plan surcharge and/or an inflation
surcharge
The prerequisite in this case is that you activated the enhancement in
Customizing under Business Transactions Deferral and Installment
Plans Activate Installment Plan Enhancement for Charges/Interest.
In the bottom right hand corner of the screen, a table appears with the most
important account balances (such as open amount, due amount, installment
plan, credit). If you select a balance, the account balance display appears
and you can see the corresponding items.
205. 7. Save the installment plan.
Use
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.
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:
● Close promises to pay.
For this you plan mass runs at periodic intervals.
● Determine the extent to which promises to pay were kept.
If the promise was not kept, then the system can update the credit standing
of the business partner.
The system puts currently running dunning procedures for the business partner
on hold until the promise to pay is closed.
When you create a promise to pay for overdue items, the system does not open
a new dunning procedure for these items – assuming you create the promise to
pay before the dunning run.
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:
● Amounts with their due dates
● Charges and interest on arrears
● Receivables cleared by payments
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:
Inherit the G/L account assignment characteristic Profitability Segment
Number (CO-PA) (PAOBJNR) from the document being written off to the
write-off document
The prerequisite for this inheritance is that you entered the value 1 (Inherit
Item to Be Written Off) for the derivation of the CO account assignment in
Customizing for Contract Accounts Receivable and Payable under
Business Transactions Write-Offs in the activities Define Specifications
and Default Values for Write-Off and Define Specs and Default Values for
Mass Write-Offs.
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.
If you want to use this function, you must define the amounts you require in Customizing
of Contract Accounting in the IMG activity Define Petty Amount Limits for Mass Write-
Off.
Features
If you have defined petty amount limits in Customizing of Contract Accounting, you
prevent items that have open amounts above or below the petty amount limits from being
written off by mistake in the mass write-off run.
The program determines the lowest petty amount limit of all items which enter a
check level (for example, contract object) and compares them with the total of the
items of this check level. All items of this check level are only written off in the
mass run if the total (underpayment or overpayment) is lower or the same as the
corresponding petty amount limit. Otherwise, none of the items of this check level
are written off.
A petty amount limit of 4.99 EUR is defined for dunning level 00 and a
limit of 19.99 EUR for dunning level 01.
A contract object has two open items. An amount of 8.00 EUR was
due on March 15, which was dunned once. A further 8.00 EUR was
due on June 15, which has not yet been dunned. The program
determines the petty amount limit of 4.99 EUR during the check in the
mass write-off because one of the items is still at dunning level 00.
Neither of the items are written off, as the total of the two items is
larger than 4.99 EUR. The petty amount 19.99 EUR is only used and
the items written off when the second item is at dunning level 01.
However, if the business partner has paid the total amount of 16.00
EUR because of the dunning of the second item, the petty amount
rule is not applied.
You can find more information in the implementation guide (IMG) of Contract
Accounting in the documentation in the IMG activity Define Petty Amount Limits for
Mass Write-Off.
Writing Off Items in External Systems
Use
You can perform write-offs in external systems.
Prerequisites
You have planned write-offs in external systems and made the relevant setting in
the Implementation Guide for Contract Accounts Receivable and
Payable underBusiness Transactions Write-Offs Activate Write-Offs in
External Systems.
You have made the settings for the derivation of the FM account assignment for
the write-off document in the Implementation Guide for Contract Accounts
Receivable and Payable under Business Transactions Write-Offs Write-Off:
Define Specifications for Enhanced Account Assignment Derivationand Mass
Write-Off: Define Specifications for Enhanced Account Assignment Derivation.
Features
If you perform write-offs in an external system, line items that are posted in
Contract Accounts Receivable and Payable via this external system are
forwarded to the relevant external system via the Outbound Interface for
Business Partner Items. The SAP system (Contract Accounts Receivable and
Payable) holds the items to be written off with clearing restriction T. This means
that these items cannot be cleared using other transactions or business
transactions. The tax calculation takes place in the external system.
Using the Bill Line ItemInterface, the general ledger items determined for the
write-off document by the external system are posted in the SAP system
(Contract Accounts Receivable and Payable) again. The preselected items to be
written off are cleared and the clearing restriction T is deleted. For detailed
information about transferring data from external systems, see the
documentation for the IDoc interfaces of Contract Accounts Receivable and
Payable, section Process Flow of Document Transfer with Revenue Item.
Write-Off History
Use
Integration
The write-off history is updated automatically during write-off. It can also be
updated automatically during mass write-off, depending on authorization.
Any write-off documents that are reversed are also noted in the write-off history.
Features
Activities
You can find the write-off history under the following paths:
Roles
SAP Menu
The Public Sector write-off history lists the individual documents which were written off
and entered in the write-off history with the function Write Off Item. In addition to the
information from the write-off history, the data of the written off documents, the write-
off document and the resubmission is issued. They are sorted according to currency,
write-off date, and document number.
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.
Printing does not work when you have activated the approval
procedure for write-offs.
Prerequisites
You must have entered function module FMCA_EVENT_PRNT_5040 in IMG
activity Define Customer-Specific Function Modules with event in the
Customizing of Contract Accounts Receivable and Payable.
Features
For the following data is available for the printout: data on the write-off document,
cleared items and data entered with the write-off with additional information on
the business partner. This data is generated and printed with events P730 and
P731.
SAP delivers a sample form for printing data which you can use as a template for
your own application form. You copy sample form
FMCA_WRITEOFF_DOC_SAMPLE_SF for this, save it under a new name and
program the changes you want. Then you assign this form to correspondence
type P034 in the Customizing of Contract Accounts Receivable and Payable in
IMG activity Define Application Forms for Correspondence. Form class
FMCA_WRITEOFF_DOC is assigned to this correspondence type by default.
Activities
To print the write-off data you must go to the function Write Off Item. When you
save the write-off, a dialog box appears where you can specify you want to print
the data.
You can hold write-offs in a status that has to be confirmed. A workflow is triggered for
the confirmation; the last step in the workflow is an approval or rejection.
Prerequisites
You have entered the required check reasons in the Implementation Guide for Contract
Accounts Receivable and Payable Basic Functions Postings and
Documents Workflows for Postings and Approvals Define Check Reasons.
You have entered the installation-specific function modules described below in the
Implementation Guide for Contract Accounts Receivable and Payableunder Program
Enhancements Define Customer-Specific Function Modules.
Features
Activities
If you want the information for line items to be output in open item processing or in the
account balance display for approval, you can define installation-specific modules for
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.
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 post time-based deferred revenues when: you are required to differentiate
between revenue and deferred revenue in the general ledger, and the service
from which the revenue arises will not be provided until some time in the future,
and the dates for the revenue recognition are already known.
Integration
You can display the data records that were included in a transfer run for deferred
revenue. You can create totals for these records according to different attributes
and thereby account for the totals posted in the general ledger. On the SAP Easy
Access screen, choose Periodic Processing Closing Preparation
Receivable/Revenue Adjustment Display Transferred Deferred Revenues .
For more information, see the program documentation.
As an alternative, you can reach the function from the menu of the transfer run
for deferred revenue under Environment Line Items .
Prerequisites
You have carried out the following activities in Customizing for Contract Accounts
Receivable and Payable under Business Transactions Deferred Revenue
Postings :
Maintain Account Determination for Time-Based Deferred Revenue
Postings
Maintain Default Values for Transfer Posting Run Here it is especially
important that you entered the document type for the documents to be
generated by the transfer run.
Exchange of No Longer Valid Account Assignments In case the account
assignments are already closed, you entered a replacement profit center or
replacement cost center in the activities Assign New Cost
Center and Assign New Profit Center.
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
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:
Define account determination for deferred revenue under Business
Transactions Deferred Revenue Postings Maintain Account
Determination for Deferred Revenue Postings .
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 .
Enter an alternate cost center under Business Transactions Deferred
Revenue Postings Exchange of No Longer Valid Account Assignments
Assign New Cost Center .
Enter an alternate profit center under Business Transactions Deferred
Revenue Postings Exchange of No Longer Valid Account Assignments
Assign New Profit Center .
Features
The functions for event-based deferred revenue use the following four, new
database tables, belonging to three different categories:
The header table DFKKDEFREV_HEAD contains an entry for each G/L
posting for which the functions for event-based deferred revenue should be
used.
The item table DFKKDEFREV_POS contains the information for the initial
transfer from the revenue account to the G/L account for deferred revenue.
The trigger tables DFKKDEFREV_TRIG and DFKKDEFREV_TRIGE
contain the information about the reported events (DFKKDEFREV_TRIG:
revenue recognition/DFKKDEFREV_TRIGE: check date) that is processed
by the transfer run for deferred revenues.
SAP provides the following function modules that you can use to implement the
functions for event-based deferred revenues:
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:
Configure and manage your products
Enter and manage customer data and contract data
You transfer the relevant parts of this data to the other involved systems.
SAP ERP
Contract Accounts Receivable and Payable in the ERP system:
1. Receives billable items from SAP CC
2. From the billable items, creates invoices and credit memos and posts
corresponding receivables or payables
3. Manages the receivables or payables until they are paid
Contract Accounts Receivable and Payable automatically offsets credit on
prepaid accounts.
Refills also lead to billable items, for which Contract Accounts Receivable and
Payable makes postings to prepaid accounts (refill of credit) or posts revenues
(purchase of refillable units).
In the following documentation, the focus is on the processes in Contract
Accounts Receivable and Payable. As far as SAP CRM and SAP CC are
mentioned, the only purpose is to make the explanations more understandable in
the given context. For more information about the processes in SAP CC and SAP
CRM, see the documentation for these components.
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:
● General Ledger Accounting
● Cash Management
● Controlling
● Sales and Distribution
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:
General management record
The general management record documents the status of the reconciliation
key, such as Open, that is, can still be posted to, or Closed, meaning no
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.
Management record per company code
The management record per company code documents the status of the
transfer to the general ledger per company code. Data from different
company codes within a reconciliation key does not have to be transferred
to the general ledger simultaneously.
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 For a reversal, the document type used
decides:
Whether there is never a
negative posting
Whether a negative posting is
always permitted
That a negative posting is
created if the posting and reversal
are in the same fiscal year
A special feature is that the items in the
reversal document for which the
account to be posted to has been
swapped in comparison to the original
document are not posted negatively.
This can be the case for aperiodic
reversals (swap of P&L accounts) or for
posting incoming payments where the
reversal is used to post back to the
clarification account.
Resetting Clearing After resetting clearing, all accounts
should appear as if the clearing had not
taken place. This means that the
inverse posting of cash discount, small
differences, exchange rate differences,
and taxes that were posted due to the
clearing are to be posted negatively.
The display in the receivables accounts
is retained.
You reset clearing for a payment
received. After the clearing reset, the
payment with clearing of open items
becomes a payment on account again,
which means that the credit from the
payment is an open item in the
receivables account. From the view of
the account balance in the receivables
account, it is irrelevant whether there
was a payment on account or whether
items were cleared.
Returns Returns should be treated like
reversals.
The first item of a returns posting, that
is, the posting to the returns clearing
account, is never posted negatively.
This also applies to returns charges.
Manual Posting If you want to post a document for
which negative postings are required
for all items manually, all you have to
do is select an appropriate document
type. However, if you only want to post
individual items negatively, you have to
enter the entire transaction in two
documents.
Transfer posting from an incorrect
G/L account to the correct G/L account.
The reset in the incorrect G/L account
should be posted negatively, the
posting to the correct account not. First
enter a negative posting: Clearing
account to incorrect G/L account. Then
a “normal” posting: Correct G/L
account to clearing account.
Payments on Account If, on receipt of payment, you first post
on account instead of clearing
immediately and then carry out clearing
later, (for example, via account
maintenance or during processing of a
subsequent payment), the debit and
credit side of the receivables account
increases by the amount of the
payment on account. If you want to
avoid this effect, make sure that every
clearing of a posting on account is
posted negatively. To do this, you have
to indicate in Customizing for the main
and subtransaction used for payments
on account that each clearing of this
item is to be posted negatively.
Distributing Revenues In contrast to the normal distribution
postings, adjustment postings that
arise from, for example, clearing reset
or reversal of payments, are posted
negatively. The prerequisite for this is
that negative postings are permitted at
company code level and that the
document type used for revenue
distribution (posting area 1381) is
supported for negative postings.
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.
Totals Record
Definition
Total of all line items posted under a reconciliation key.
Use
Totals records form the basis for creating the line items of the G/L document.
Structure
Documents that are posted in FI-CA are not transferred on a one-to-one basis to
the general ledger, rather, they are transferred as an accumulated record. Totals
records are updated in FI-CA when you post FI-CA documents and they are the
basis for a cumulative transfer of FI-CA documents to the general ledger. A
reconciliation key must be specified for each posting.
A totals record for a reconciliation key contains the total of the posted amounts
for all line items that are grouped by the totals record. Totals records are
recorded separately by company code, business area, G/L account, currency,
posting date, document date, as well as other account assignments, such as
those from cost accounting.
The totals items created in FI-CA contain information for the document header
and the line items for the general ledger documents to be created during the
transfer. For an identical account assignment, the accumulation can be
suppressed. To achieve this, when you post the line items you have to set
the Line Item indicator – a separate line item is created for this FI-CA line item in
the general ledger document created later.
In the following topics you receive an overview of the special considerations with
integrated use of Contract Accounts Receivable and Payable with new General
Ledger Accounting.
Contract Accounts Receivable and Payable and Document Splitting in New
General Ledger Accounting
Features
With the Document Splitting component of new General Ledger Accounting, you
can create financial statements, including a profit and loss statement, based on
various dimensions. New General Ledger Accounting allows document splitting
for a number of characteristics, of which Contract Accounts Receivable and
Payable (FI-CA) supports the following:
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 customer-
specific 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 FI-
CA 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.
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
Features
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: Posting Invoices
Example: Overpayment/Underpayment
Example: Payment On Account/Down Payment
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:
● If there is an underpayment, the divided amount is in the invoice
document to be cleared. One item maps the partial clearing and the other
the outstanding receivable. In the payment document, the underpayment is
posted as full clearing of the partial amount with the FM
category C (clearing) and is updated in the assigned FM account
assignment.
● If there is an overpayment, the divided amount is in the payment
document. An item maps the full clearing of invoicing and is updated as FM
category C(clearing) in the assigned revenues FM account assignment.
The remaining amount is posted as a payment on account with FM
category G (payment on account).
However, payments on account are only updated in Funds
Management if you have activated the Payment Matching there. In
the SAP standard system, payment on accounts are not updated
in Funds Management. (See the Customizing for Public Sector
Management Funds Management Public Services Actuals and
Commitments Update/Integration Integration Define Settings for
Payment Transfer.
The example below depicts an overpayment. The payment amount (300) is
divided into a clearing amount (-200) and a payment on account (-100). In Funds
Management, the payment matching is activated, therefore the payment on
account is also relevant for the update. The derivation rules are also defined so
that the settlement payment and the payment on account are in different FM
account assignments.
For simplification, the figure illustrates only one payment document.
See also:
Example: Posting Invoices
Example: Payment with Clearing
Example: Payments on Account/Down Payments
● Transaction Currency
● Funds Center
● Commitment Item
● Fund
● Functional Area
● Customer Dimension
● G/L account for General Ledger Accounting
● 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.
Active Availability Control for Requests
Features
To make an active budget availability check possible between Public Sector
Contract Accounts Receivable and Payable and Funds Management, in the
transaction for processing requests you automatically create earmarked funds
documents or reference existing earmarked funds documents.
The system statistically uses up earmarked funds documents as soon as you
create a request. When the FI-CA document is created from the request, the
system replaces the statistical consumption with the FI-CA document. If a
request is deleted or rejected, the system automatically releases the earmarked
funds document generated for the request.
NOTE
You can create earmarked funds documents either by means of a request or in a
separate transaction. The system only automatically releases earmarked funds
documents that were created by means of a request.
If you change the amount or the account assignment for a request item, the
system automatically adjusts the earmarked funds document for the request.
From a technical perspective, the system releases the old earmarked funds
document and creates a new one, taking the new amount and new account
assignment into account. This also applies only to earmarked funds documents
that were created by means of a request.
You can:
Process requests that are on the approval list
Close earmarked funds documents directly from the request
In addition, there is a year-end closing report that makes it possible to create
earmarked funds documents for standing requests. (On the SAP Easy Access
screen, choose Periodic Processing Closing Preparation Create
Earmarked Funds Documents for Standing Requests ).
Credit Segments
Definition
Organizational unit of SAP Credit Management that you can define as required,
for example, by product type or business area.
Subdivision of the relevant business transactions in a
telecommunications company according to the following credit
segments:
Fixed network
Internet
Cellular network
Use
The credit segment groups the business of a company from the view of credit
assignment and control.
Structure
You have to define the credit segments you have defined in the Implementation
Guide for Contract Accounts Receivable and
Payable under Integration Financial Supply Chain Management Credit
Management Maintain Credit Segments.
The credit segments that you define here must agree with those
of SAP Credit Management.
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.
You can transfer credit exposure from Contract Accounts Receivable and
Payable to SAP Credit Management.
Integration
In Contract Accounts Receivable and Payable, you can display the credit
exposure of a business partner in the master record per credit segment and go
from there to the details of the credit exposure.
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.
Maintain Credit Segments, you entered your credit segments.
The credit segments that you enter here must agree with those in SAP
Credit Management. The credit segments are used there to break down
credit exposures into different areas, such as countries A and B.
Assign Open Items to Credit Segments, you assigned receivables to an
appropriate credit segment based on their company code, account
determination ID, business area and division.
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 200 indicates open items.
Credit exposure category 100 indicates open SD orders.
Credit exposure category 210 indicates billable items with
status billed that are not yet invoiced.
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.
● Returns
● Deferrals and installment plans
● 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)
● DUN (dunning notices)
● P2P (promises to pay)
● RET (returns)
● TIP (installment plans)
● 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.
If you want to change the type of calculation, define event 4500
accordingly.
If you want to use the function, you also have to define event 4600 to
forward the key figure Budget Billing Amount per Day determined for
each business partner to SAP Credit Management. In SAP Credit
Management you have two options:
65. ...
You can save the key figure in a field of the payment behavior
summary that you do not use in the SAP business partner.
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.
You can transfer credit exposure from Contract Accounts Receivable and
Payable to SAP Credit Management.
Integration
In Contract Accounts Receivable and Payable, you can display the credit
exposure of a business partner in the master record per credit segment and go
from there to the details of the credit exposure.
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.
Maintain Credit Segments, you entered your credit segments.
The credit segments that you enter here must agree with those in SAP
Credit Management. The credit segments are used there to break down
credit exposures into different areas, such as countries A and B.
Assign Open Items to Credit Segments, you assigned receivables to an
appropriate credit segment based on their company code, account
determination ID, business area and division.
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 200 indicates open items.
Credit exposure category 100 indicates open SD orders.
Credit exposure category 210 indicates billable items with
status billed that are not yet invoiced.
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.
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. Schedule the program run.
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.
Note for the industry component Utilities Industry
For a move-in, you can perform a credit check in SAP Credit
Management and process the result accordingly. To do this you can
use the methodCheckCredit of the BOR object type ISUPARTNER.
To implement the credit check, proceed as follows:
72. ...
1. i. Implement a workflow that starts after
the move-in processing.
2. ii. Connect the workflow with the
method CheckCredit of the BOR object ISUPARNTER.
In detail, the credit check runs as follows:
5. ...
3. i. The workflow is processed after the
move-in processing. This workflow calls the
method CheckCredit.
4. ii. The method CheckCredit calls the
function module FKK_CR_PERFORM_CREDIT_CHECK.
5. 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.
6. iv. SAP Credit Managementthen runs a
credit check and returns the result.
● Block reason
● Indicator Special Attention
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.
The risk class of the business partner has become worse,
therefore the contract accounts should be dunned with a different
dunning procedure.
To change other objects (for example, contract), you can use event 4507.
XI Interfaces Used
The following interfaces are used:
● 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.
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 link to the business partner/contract account to which the dispute
case refers is located under the structure node Business Partner.
● 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.
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:
Correspondence Created Automatically
Correspondence Created Manually
You can send and print correspondence asynchronously as background
processing. For later processing, choose Dispute Management Periodic
Processing in Dispute Case Processing Processing of Actions, or schedule
the program RSPPFPROCESS as job.
Example
You create a dispute case in Contract Accounts Receivable and Payable. You
can enter the data of a contact person (correspondence recipient); this is then
included in the dispute case as an attribute and used for the correspondence. In
Customizing you have defined that an automatic notification to the customer is
created. The communication channel configured for the contact person is used
(e-mail, fax, or letter). The correspondence is sent asynchronously as a
background job at night to ease the load on the system.
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 an incoming payment that has increased the
amount Payments Received, this amount field is reduced by the amount of
the payment.
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.
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).
● For each reversal invoicing document, provided the reversed document
has already been printed
If the document has not been printed yet, in the reversal, the system
deletes the correspondence container of the reversed document.
Generally, there is one container for each invoicing document. If an additional
recipient has been defined for the business partner, the system creates a further
container. The system does not create correspondence containers for simulated
invoicing documents, since these are not supported for mass printing.
For the creation of correspondence containers, SAP delivers the sample function
module FKK_SAMPLE_2685. You can use this as a template for your own
implementations, and there should be no differences.
In addition to the standardized data, the correspondence container contains the
document number of the invoicing document in the second correspondence data
field for the entity identification DOCN, and it contains the invoicing process in
the first correspondence data field for the entity identification IPRC.
For each correspondence container, correspondence printing calls up one
application form and creates one print document with this form. If the actual
printout was successful, correspondence printing sets the print date in the
correspondence container and in the header of the invoicing document.
Invoice Printing
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:
● Recognize defined situations in invoicing processes in contract account
receivable and payable.
● Create clarification cases automatically or manually
● Specify a clarification process that supports the asynchronous, manual
postprocessing of the clarification case using an agent
● Clarify clarification cases automatically
The Clarification Processing in invoicing is an application of the Clarification
Framework Controller (CFC) and can be called with transaction FKKINV_CFC.
The Customizing for the processing of clarification worklist is delivered by SAP
(Customizing Contract Account Receivable and Payable Technical
Settings Prepare Processing of Clarification Worklist).
Process Flow
Validation
Validation covers the system-side analysis and recognition of a clarification
situation when processing source documents or invoice documents and decides
whether a clarification is needed or not in an automated mass process.
The validation can refer to various different objects.
The following elements can be checked:
● Source Documents
● Invoice Documents
● Contract Account
● Error Messages
These checks can be processed in the Invoicing Process
You can also perform Plausibility Checks for Source Documents in Analyze
Invoicing Orders.
Billing documents can already be recognized as implausible in Transfer of Billing
Documents and can be checked again in Display Billing Document.
Creating the Clarification Case
If there is a situation to be clarified then a Clarification Case is created.
Clarification cases can be created either automatically in the Invoicing
Processor Transfer of Billing Documents or manually in the Analyze Invoicing
Orders.
Clarification Processing
In Clarification Processing the clarification cases can be
either automatically or manually clarified by the agent:
● Clarification Processing in Dialog enables the agent to process and
complete the clarification case. It delivers the clarification worklist, supports
the individual choice of clarification cases by the agent and displays the
clarification case data in the detail screen.
● Clarification cases can also be automatically clarified when billing
documents are transferred and in the invoicing process.
Displaying the Invoicing Document
The invoicing document display gives you an overview of all data contained in
the invoicing document.
Features
If the system determines one invoicing document based on the the selection
criteria that you enter, all document information is displayed immediately. The
upper part of the screen shows the header data of the invoicing document. All
document data is displayed in list form below this.
If the system determines more than one invoicing document for the selection
criteria you enter on the initial screen, initially only the header data appears. The
system can display the header data for up to ten invoicing documents in the list
on the upper part of the screen. If more than ten invoicing documents satisfy the
selection criteria, all further document headers are displayed on a separate
screen. By double-clicking on an invoicing document, you can navigate to the
detailed display of the document. The items, posting documents, and source
documents for this document are each displayed on a separate tab page. By
means of icons on the tab pages, you can immediately recognize which data is
available.
Actions and Navigation
In the list of the document headers you can:
Simulate an invoice
Call up the invoice preview
Display an existing invoice from the optical archive
To perform one of these actions, in the list of document headers, select an
invoicing document and choose the appropriate pushbutton in the application
toolbar.
If the selected invoicing document is an individual document of a collective bill,
you can navigate within the collective invoicing document. To do this, select the
header line of the individual document and choose the Collective Bill pushbutton.
If the invoicing document selected is a collective invoicing document, you can
display the list of all the individual documents. To do this, select the header line
of the collective invoicing document and choose the Individual
Documents pushbutton.
On the Posting Documents tab, you can navigate to the posting document
display.
On the Source Documents tab, you can see the source documents of the
invoicing document. Depending on the source document category, you can
navigate to the following views:
Source document category in the billing document display
Source document category of the collective bill
Source document category in SD document
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.
Program Enhancements
Using the event concept, you can integrate industry-specific and customer-
specific 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.
You can integrate invoicing with Sales and Distribution (SD), with SAP Customer
Relationship Management (SAP CRM), and with billing systems.
Together the Billing in Contract Accounts Receivable and Payable and Invoicing
in Contract Accounts Receivable and Payable components form SAP
Convergent Invoicing.
Integration
SAP Convergent Invoicing offers you the possibility of integrating the following
applications:
SAP Convergent Charging
SAP Customer Relationship Management
Contract Accounts Receivable and Payable
This comprehensive integration enables you to implement the business process
from the consumption of a service through pricing and billing right up to dispatch
of the invoice to the customer.
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.
● Remote Function Call (RFC)
The data is sent by the call of event 3703. To use the send type RFC, you
have to call an RFC-capable function module in the external system at
event 3703.
● 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.
● Web Services Reliable Messaging (WSRM)
For data in information container categories that you transfer using XI
messages, you can also send this data using Web Services Reliable
Messaging (WSRM) for asynchronous enterprise services.
The WSRM send type is available for the following information container
categories:
○ 0001 (returns) with service operation
PaymentReturnERPOccuredBulkNotification_Out
○ 0002 (clearing and clearing resets) with service operation
ContractAccountReceivablesPayablesRegisterERPSubscribedItemB
ulkNotification_Out
To make it possible to send using WSRM, you have to configure the send
type in Customizing. In addition, you have to configure the following service
groups in SOAMANAGER:
○ FKK_PAYRETBULKOCCNO for information container category
0001
○ FKK_CARPRSUBSCRITEMBULKNO for information container
category 0002
The logical determination of the recipient in SOAMANAGER uses the
recipient field of the information container. You can determine the values for
the recipients of an information container entry in a function module entered
for event 3701.
If you have defined your own information container category and want to
send data by WSRM, you must implement the method SEND_VIA_WSRM
of the interface IF_FKK_INFCO_TYPE.
With each entry in the information container, the system saves the related
business partner and, depending on the information container category, the
contract account and contract.
You can add your own data to the data of the individual information container
categories. To add data to the data saved for an information container entry, you
can use event 3701.
To add your own data to the send data, you can use event 3702.
Using event 3701, you can also:
● Change the number days up to which data is no longer sent
In the standard system the value is set to 100 days.
● 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.
● For specific situations, define that no new information container entry
should be created
See the documentation for the sample function modules FKK_SAMPLE_3701,
FKK_SAMPLE_3702, FKK_SAMPLE_3703, and FKK_SAMPLE_3704.
Closing Operations
This component consists of the following detailed components:
Foreign Currency Valuations
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:
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.
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:
○ There is a difference between general ledger documents and FI-CA
totals records.
○ There is a difference between FI-CA totals records and FI-CA
documents.
312. 2. First check whether the general ledger documents and the totals
records agree. In the SAP menu, choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Check General Ledger
Documents (Mass Run)/Check General Ledger Documents (report
RFKKGL20).
If the evaluations of these programs show differences, proceed as follows:
6. ...
21. a. Check the status of the transfer of the reconciliation
keys. In the SAP menu, choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Check Transfer
Status of Reconciliation Keys (Report RFKKABS5). All reconciliation
keys with a posting date before or on the key date must have been
completely transferred to the general ledger.
22. b. Then check whether there are differences between
the totals records and the FI-CA documents. In the SAP menu
for Contract Accounts Receivable and Payable, choose Periodic
Processing Forward
Postings Reconciliation Checks/Adjustments Check Totals
Records (Mass Run)/Check Totals Records (Report RFKKABS1). If
the evaluations of the programs show differences, you have to correct
the totals records.
23. c. After you have adjusted the totals records, check
again whether there are differences between general ledger
documetns and totals records. If this is the case, you have to make a
further adjustment.
Determine the cause of the differences and complete
adjustments in cooperation with SAP. To do this, enter a customer
message. For the programs necessary for the adjustments, see the
following section.
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:
● To correct differences between general ledger documents and totals
records, in the SAP menu for FI-CA choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Check General Ledger
Documents. Select the required reconciliation key and then, in the
application toolbar of the evaluation, choose Adjust General Ledger. The
system then creates further general ledger documents.
● To correct differences between totals records and and FI-CA documents,
in the SAP menu for FI-CA choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Check Totals Records.
Select the required reconciliation key and then, in the application toolbar of
the evaluation, choose Adjust Totals. The system differentiates as
follows:
○ If the reconciliation key has not yet been transferred, the system
adjusts the incorrect amounts in the totals records.
○ If the reconciliation key has already been transferred, adjustment
totals records are created for this reconciliation key. You then have to
transfer the adjustment totals records to the general ledger. In the
SAP menu for FI-CA, choose Periodic Processing Forward
Postings Execution General Ledger Transfer.
● 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).
● To reconcile Profitability Analysis, in the SAP menu for FI-CA,
choose Periodic Processing Forward
Postings Reconciliation Checks/Adjustments Check CO-PA
Documents (Mass Run)/Check CO-PA Documents (Report RFKKCO20).
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.
○ Division
○ Receivables account
○ Account determination ID
○ Main transaction
○ Subtransaction
314. 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.
Purpose
You use this component to valuate foreign currencies in contract accounts with
the aim of adjusting the receivable and payable accounts as part of balance
sheet preparations.
Implementation considerations
This component is optional. You need it if you make foreign currency postings.
Features
Valuation is according to the single valuation principle. This means that the
individual items which are open at the balance sheet key date are taken into
account during valuation. Foreign currency valuation can be in local currency as
well as in the currencies managed in parallel (such as group currency or hard
currency).
The G/L accounts to which the exchange rate differences from the valuation are
to be posted are determined and posted to automatically.
Valuation can be based on the usual valuation procedures (such as general
valuation or the lowest value principle).
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.
○ Business area
○ Division
○ Receivables account
○ Account determination ID
○ Main transaction
○ Subtransaction
318. 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.
You can use installment plans to distribute original receivables over a series of
installments that have due dates in the future. Receivables with a due date more
than one year in the future need to be displayed separately in the balance sheet.
Using an installment plan analysis for a key date, you create a snapshot of the
installment plan due dates on this key date, as well as of the assignment of these
due dates to the original items.
Integration
If there are installment plan analyses in the system from an update run, you can
use this data in the following reports:
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:
● RFKKCF_DELETE allows you to delete entries that have been resolved.
The IS-T variant of the Idoc interface is no longer supported in version 4,71 because the
IS-T IDoc interface has been migrated to the FI-CA standard. As a result, the following
changes have occurred in 4.71 for users of the previous RM-CA IDoc interface:
Namespace changes for IDoc types, IDoc segments, data elements,
function module names and so on.
The prefixes of the IDoc types and data have been changed from IST to FKK; for
example, IDoc segment IST_EBS_TOI_COPA toFKK_EBS_TOI_COPA.
Changes to events
The IDoc interface events now start with event 2400 (previously T400), The sequence
remains the same.
Functional Enhancements
The VAT code has been entered in the IDoc segment E1FKK_EBS_TOI_ITEMS via the
field TAX_CODE. If the code is set, the value added tax code is used to determine tax. If
not, the external code is used.
The mass processing transaction has a new, improved application log processing.
The most important Customizing settings are automatically transferred by the report
(XPRA) IST_XPRA_IST20_FKKIDOC during the update.
Event Concept
Purpose
The event concept enables the integration of industry-specific and customer-
specific 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:
TFKFBM (sample function modules of Contract Accounts Receivable and
Payable)
TFKFBS (Standard function modules for applications)
TFKFBC (Installation-specific function modules)
The technical name of the sample function module is made up of the technical ID
FKK_SAMPLE_ and the name of the event. In the case of a sample module
defined for event 0010, the name would be FKK_SAMPLE_0010.
In addition to the events available to all industry components, there are additional
industry-specific events that you can recognize from the encryption of the
application area in the technical name.
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).
● 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:
● Job Commander of Contract Accounts Receivable and Payable
● External job control system
For detailed information about integration, see Integrating External Job
Control Systems in the job control documentation.
● 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).
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
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:
Category A for selecting items with certain transactions
Category B for selecting business partners of the organization category
The system calls event 0590 in the mass activity for automatic clearing for
deselecting items. At this event, you enter values as appropriate for the
additional characteristics category A and category B. You can access the
additional characteristic as follows:
DATA: g_basics TYPE fkk_mad_basics.
IMPORT basics TO g_basics FROM MEMORY ID 'FKKMADBASICS'
The value of the additional characteristic is contained in the MACAT component
of the g_basics structure.
If the event module contains an import parameter of the type fkk_mad_basics,
then you can use it directly.
You use function module FKK_MACAT_CHECK to check for the existence of an
additional characteristic, and to determine the short text for it.
On the SAP Easy Access screen, you now choose Periodic Processing For
Contract Accounts Automatic Clearing . If you enter an appropriate value in
the Additional Characteristic field, then the mass activity processes the data, not
only based on the entries you made on theGeneral Selections tab page, but also
based on the definition of the additional characteristic you entered. If you
entered Category B as the additional characteristic, then the automatic clearing
only processes business partners with the the organization category.
Country-Specific Functions
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:
Print Documents for Reversal
Distribution Franchisee Management
New Service Connection
Energy Audit
Print Local Language
The new service connection solution enables utility customers to support the
varied requirements for different states in India. Different states in India have
different procedures for a new service connection. There are some mandatory
documents that a utility customer will need to provide while applying for a new
service connection. The procedure varies from one region or state to another
based on the regulations governed by the regional authorities.
To obtain a new connection from a utility company, a prospective customer
needs to submit an application form along with required documents. After the
necessary verification, the customer pays a security deposit, following which a
new connection is provided to the customer.
Utility companies cater to diverse customers that include residential customers
and commercial customers. Industries and buildings are also accommodated as
customers.
Prerequisites
You have made the following settings:
Maintained document category for a new service connection. You do so in
Customizing for SAP Utilities, by choosing Customer Service Country-
Specific Functions India New Service Connections Maintain
Document category for New Service Connection .
Maintained document IDs. You do so in Customizing for SAP Utilities, by
choosing Customer Service Country-Specific Functions India New
Service Connections Maintain Document ID .
Maintained documents for the customer type. You do so in Customizing
for SAP Utilities, by choosing Customer Service Country-Specific
Functions India New Service Connections Maintain Documents for
the Customer Type .
Maintained documents assigned to document category. You do so in
Customizing for SAP Utilities, by choosing Customer Service Country-
Specific Functions India New Service Connections Maintain
Documents Assigned to Document Category .
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
Set up the grid hierarchy
Assigned the installations to the respective grids
Completed the system set up for Energy Data management: Maintained
Settlement master data, mapping of grid to settlement units and hierarchy of
settlement units
Created the settlement parameters for the settlement units using
the Check and Create Settlement Parameters (EEDMSETTLPARA_WZ)
transaction
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.
Being a land of diversity in terms of regions and culture, India has multiple
regional languages. However, languages spoken also vary beyond the regional
level. These are the local languages and it has been observed that a particular
region can have multiple local languages.
The consumers of electric energy are spread across the country right up to the
smallest unit of a region. It has been observed that a majority of these
consumers prefer communication in their local language.
The Print Local Language functionality enables customers to avail their choice of
language for generation of electricity bills, thus translating the total amount
payable into the local language.
Prerequisites
You have made the following settings:
Completed the system setup to support the required local language
Programmed the print workbench to support the printing of amounts in
words
Features
Once the print workbench is ready, the invoices can be printed using the
standard print options available in the Individual Bill (EASIBI) and Print out Print
Document (EA60) transactions.
Output
The system prints the invoices with amounts (in words) in the local regional
language.