Professional Documents
Culture Documents
Revenue Recognition For Service Contracts in Sap CRM: Configuration Guide
Revenue Recognition For Service Contracts in Sap CRM: Configuration Guide
Service Contracts in
SAP CRM
Configuration Guide
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
© 2012 SAP AG
Dietmar-Hopp-Allee 16
D-69190 Walldorf
Configuration Guide
Table of Contents
1 Introduction .................................................................................................. 3
1 Introduction
This guide describes the configuration steps that need to be taken to achieve a period-based accrual of
revenue for service contracts with periodic billing plans. This means that revenue is realized in the
posting period in which the service was rendered rather than in the posting period in which a billing
document is created.
Service contracts are created in SAP CRM and revenue recognition takes place in SAP ERP. Purpose
and mode of operation are explained in the application documentation.
There is no technical dependency between revenue recognition and billing. Billing can take place in SAP
CRM or in SAP ERP.
Prerequisites
• Service contracts, service orders, and service confirmations in SAP CRM can be opened,
processed, and closed.
• Integration with the SAP ERP controlling components is set up for service transactions.
• Period-end closing works in financials/controlling.
• Settlement of internal orders is set up in controlling.
• Reports in the info system for internal orders in controlling are used to displays costs, revenues
and accrual accounts (SAP Easy Access menu: Accounting Controlling Internal Orders
Information System).
• Revenue account determination is set up in SAP CRM.
This also has to take place for the transfer of planned revenue to the internal order in controlling.
• If service contracts are billed in SAP ERP, revenue account determination also has to be set up in
SAP ERP.
• Condition types are set up for pricing in SAP CRM.
Implement user exits according to SAP Note 1019177 (“Results analysis for CRM service contracts”). The
following ABAP coding has to be created and activated:
• Enhancement KKAG0001 („Period costing in make-to-order production”) function module
EXIT_SAPLKKAG_002 (“Customer-Specific Determination of Planned Values/Valuation”)
include ZXKAGU02:
In the overview list of item categories, select the item category and navigate to the view Assignment of
Business Transaction Categories. Select the transaction category Sales and make the following settings.
Settings
Bill. Relevance = Not Relevant for Billing
Rev. recog. = Time based revenue recognition (A)
In the overview list of item categories, select the item category and navigate to the view Assignment of
Business Transaction Categories. Select the transaction category Sales and make the following settings.
Settings
Bill. Relevance = Not Relevant for Billing
Rev. recog. = Standard revenue recognition or, alternatively, Service based revenue recognition (B)
In the overview list of item categories, select the item category and navigate to the view Assignment of
Business Transaction Categories. Select the transaction category Sales and make the following settings.
Settings
Bill. Relevance = External Billing (A) for billing in SAP ERP SD, or alternatively Billing after Contract
Release (B) for billing in SAP CRM
Customizing (if you use enhanced account determination): Billing Integration Transfer of Billing
Documents to Accounting [Transfer to Accounts Receivable (FI-AR) and Accounts Payable (FI-AP)] or
[Transfer to Contract Accounts Receivable and Payable (FI-CA)] Enhanced Account Determination
Assign Symbolic Account Key.
Select the entry, navigate to Controlling Scenario, and assign a controlling scenario, for example
SERV000001.
4.4 Set Up Mapping for the Document Type for Debit Memo Requests
Customizing: Integration with other SAP components Customer Relationship Management Settings
for Service Processing Billing Integration Map Transaction Types and Item Categories
Example
Map CRM transaction type ZDP2 to ERP document type for debit memo request ZDP2.
Select the entry, navigate to Item category mapping, and map the billing-relevant item category (for
example ZDPB) to the sales item category for the debit memo request (for example) ZDPB.
Choose Expert Mode to navigate to the expert mode for either of the statuses, and make the following
settings for the statuses.
6 Controlling Transactions
This section describes the controlling transactions for which the settings describe above are relevant.
6.2 Settlement
SAP Easy Access menu: Accounting Controlling Product Cost Controlling Cost Object Controlling
CRM Service Processes Period-End Closing Single Functions Settlement Individual
Processing (or alternatively: Collective Processing).
Example: Enter number of internal order for service contract item, period and fiscal year and execute.