SAP CRM billing
CRM Billing Customizing :-
To be able to completely use CRM Billing, you must maintain all activities that are in the Implementation Guide under the Billing node. For this, in IMG choose (SPRO) -> CRM->Billing.
Under Billing, you should make the following settings in any case:
Define the services used in CRM Billing, including in particular price determination and partner processing
Define the number ranges for unique number assignment
Define the billing unit in the organizational plan of CRM and define the billing types
Define item categories for CRM Billing and define item category determination
Define the interface to financial accounting (if necessary)
Under Number Ranges, you should make the following settings for number ranges in Billing:
Define Number Range for Billing Documents: Here you define new or existing number range intervals for billing documents.
Define Number Range for Collective Runs: Here you reset and transport number range intervals for collective processing runs.
Under Item Categories, you define the item categories for CRM Billing. The item category determines the properties and characteristics of billing due list items and billing items (normal service items, and credit/debit memo items, for example).The item category attributes determine how the system behaves
during input processing and billing.
Service Related Customizing:-
Under Billing Types, you define billing types for CRM Billing. A billing type specifies the characteristics and properties of a billing document (an invoice, credit memo or debit memo, for example). The billing type attributes determine how the system behaves during billing.
Under Item Category Determination, you make settings for item category determination in CRM Billing. Item Category Determination is used to define the item category for CRM Billing from data on CRM business transactions. There are two possible ways of doing this:
In the activity Assign Item Category, you can assign the item category for CRM Billing to a specific combination of transaction type (process type of source application) and an item category of the relevant CRM business transaction.
If the standard setting shown in the figure is not sufficient for your business scenario, you can use Advanced Item Category Determination to determine the item category for CRM Billing more flexibly.
Under Service-related Customizing, you make settings for the services used by CRM Billing: pricing, partner processing, text processing, and action processing. You make Customizing settings for the first three of these services under Customer Relationship Management Basic Functions. You can define the settings for actions in CRM Billing directly in Customer Relationship Management Billing.
Under Integration-related Customizing, you make settings for integrating Billing with accounting applications. Settings regarding document types, accounts and tax codes for accounting documents are
Transaction customizing: -
In CRM Business Transaction Customizing, you must specify the billing relevance of the item categories (for example, Service Contract Item, Credit memo, Debit memo) to the Business Transaction categories (for example, Sales, Sales Contract, Service, Service Contract) assigned to them. Here the following settings are possible:
Not relevant for billing: The transaction is not relevant for billing (example: item for a free-of-charge delivery or quotation).
Relevant for external billing: Billing is controlled in the SAP R/3 system or another external system.
Relevant for transaction-related billing after release of the contract: In the SAP CRM system, CRM
Billing is started for a transaction for billing the order quantity if the transaction (as a rule, a contract) is released.
Relevant for transaction-related billing according to delivery quantity: In the SAP CRM system, CRM Billing is started for a transaction for billing the cumulated delivery quantity (the delivery in the SAP R/3 system returns the delivery quantity to the CRM transaction). Caution: In this case, you should make sure that the corresponding item category in the SAP R/3 system is set to not relevant for billing.
Relevant for transaction-related billing: In the SAP CRM system, CRM Billing is started for a transaction for billing the order quantity.
*************************
IntroductionThe Transaction Tax Engine (TTE) calculates tax in business scenarios that use the CRM Billing for billing processes.
This document describes the required configuration steps for using the TTE for tax calculation in these scenarios.Document OverviewThe first sections of this document:
IPC Configuration Settings: Overview
TTE Configuration Settings: Overview
R/3 Configuration Settings: Overview
CRM Configuration Settings: Overview
describe the basic configuration settings that are obligatory for all CRM Sales Business Scenarios that use CRM Billing. All these settings must be correct before proceeding to the next stage. In each section you will find details on how to validate the configuration settings made. Do not proceed to the next stage until the settings have been successfully validated.
For business scenarios, such as US Sales and Use tax, that use jurisdiction codes for tax determination, the section External Systems Configuration Settings describes in detail the required configuration steps.
Country-Specific Information contains details of any additional steps that need to be taken for the country in question, if this information is not sufficiently covered in the Implementation Guide (IMG). Any countries that are not listed in this section do not require any configuration settings in addition to those listed in the other sections.
**************************************SAP CRM Billing vs. SAP ERP Billing
CRM biliing feature is usually used in pure service industries.Hence for simplicity I am refering to service scenario.SAP CRM service documents can be billed either in SAP CRM or in SAP ERP, this includes:
Service Orders and Confirmations
Service Contracts
Spare Part Orders
Credit and Debit Memos
Exchange Orders
Warranty Claims
Comparison of Main Features
Features | In SAP ERP? | In SAP CRM? |
Billing Due List to see what is in the queue to be billed | YES | YES |
Collective Billing, to combine various due list entries into a single bill | YES | YES |
Integration of Billing with ERP Financials (posting to FI) | YES | YES |
Comprehensive work bench to enhance Billing with new fields, custom search parameters, etc. | NO | YES |
WebClient User Interface | NO | YES |
Capability to integrate credit card payments | YES | NO |
Capability to print out invoices | YES | YES |
Capability of handling high volumes | YES | YES |
Integration to Costing (posting of revenues to an internal order or other cost element) | YES | YES |
Billing in SAP CRM
- Integration between CRM documents and CRM billing is seamless and controlled via status at the line item level (To be invoiced, Invoiced, etc.)Uses the CRM Billing Engine, which is driven by the Billing Engine Framework
- The Billing Engine Framework is easily extensible using transaction BEFN
- This can be used to enhance the billing due list and the billing document, e.g., with new fields.Several BAdIs are available to influence the data that goes into the billing due list or the billing document
- This can be combined with enhancements to the framework as previously mentioned
- The invoice can be printed using SmartForms
- The form will have to be created from scratch in SAP CRM (not possible to re-use form from SAP ERP)
- No out-of-the-box functionality for credit card integration into SAP CRM billing
Billing in SAP ERP
- Billing CRM documents in SAP ERP is achieved by creating SAP ERP Credit/Debit memos
- The SAP CRM document (items) has to be marked as relevant for “external billing”
- Once the document is saved, an SAP ERP Debit memo is created viaCRM middleware
- The Debit memo can then be billed using standard SAP ERP billing
- Pricing (including manual conditions) can be transferred, unchanged, from SAP CRM to SAP ERP
- The billing integration can be influenced using BAdI CRM_EXT_BILLING
- The SAP ERP Debit and Credit memo document types to be used are configured in the SAP CRM plug-in in SAP ERP
Advantages of Using SAP CRM Billing
- All activity is happening in the same system, i.e., the documents and the billing items are contained in the same system
- Easy for administrators to troubleshoot issues
- Nice user interface for administrators to use
- Extensible engine to accommodate various customer requirements
- Flexible integration to SAP ERP Financials
Advantages of Using SAP ERP Billing
Any company that has an SAP ERP backbone has probably already implemented the SAP ERP Billing Engine.With this option, the company has the capability to leverage a proven technology for billing and also re-use the efforts and investments put into this area.
- The SmartForm for printing the invoice can be re-used
- Billing Engine customization can be re-used
- Billing administrators do not have to be retrained as the technology and platform remains the same
- Billing document and FI document is in the same system
- Credit Card integration is available in the SAP ERP Billing Engine
If choosing SAP ERP billing be aware of the following:
- A lot more documents will be generated in your landscape —for every SAP CRM Service document, you will have at least one SAP ERP document (Debit memo)
- A lot more traffic between SAP CRM and SAP ERP (middleware) and consequently higher monitoring needs
- Integration scenarios need to be thoroughly tested, especially around service contract billing as billing plans are complex structures.
Post a Comment