SCN Wiki upgrade to version 6.13 on Tuesday 19.11.2019 - beginning 07:30 am CET

During upgrade process new content will not be transported to new Wiki version

Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

 

In CRM you can use either the CRM Billing Engine (CRM-BE) or use the external Billing on ECC side. On ECC side a Debit Memo Request (DMR) is created for the billing relevant CRM Service document item. A Debit Memo Request is a type of Sales order in ECC, you can use the sales order only for billing (and not for logistic movements or other functions). Billing plans of CRM Servicecontracts are not transfered to ECC, but only Billing Request Items (BRI) are created on the basis of Billing plans in CRM (see note 813774).

For the following service transaction types in CRM, billing can be performed externally in SAP ERP Central Component (SAP ECC).

            • Service contract

            • Service order

            • Service confirmation

 

 

      •  

      •  

      • For service transactions containing items that are defined as relevant for external billing, SAP CRM automatically transfers billing-relevant data to SAP ECC. Transfer takes place when a user sets a particular status for the transaction. The data transferred includes the billing date, products to be billed for (services and service parts), business partners, and conditions.

        When data is transferred, a debit memo request is automatically created in SAP ECC for each service transaction, in the form of a sales order. The items in this order represent the billing-relevant items in the original service transaction. Billing can be performed immediately for these debit memo requests, without any additional processing steps.

  •  

 

External Billing of Service Orders and Service Confirmations

 

Data is transferred to SAP ECC when an order or confirmation is set to Completed. Invalid items can still be cancelled by specifying a reason. The cancellation reason is transferred to SAP ECC through item category mapping, and either the relevant debit memo request item is automatically canceled or, if the item has already been billed, a credit memo request is created.

 

After data transfer, transcations can be cancelled or rejected in SAP CRM. If it is no longer possible to cancel individual items later on in the process, for example because an invoice has already been created for a debit memo request, a credit memo request can be created in SAP ECC to reverse a debited amount.

 

 

External Billing of Service Contracts

 

Billing request items generated by a billing plan are transferred automatically to SAP ECC. Service contract items that are relevant for billing are transferred when contract data is updated and a contract item is marked as Released.

 

 Customizing - CRM

 

The main settings for integration components are at item category level (Transaction category BUS2000115 Sales) . Below see some of SAP Standard itemcategory SRVS:

 

You can found these in the IMG under





 

or directly via transaction CRMC_ITEM_MA.

 

Customizing - ECC
Map Transaction Types and item Categories
 
 

When SAP CRM Service transactions are transferred to SAP ECC for billing, debit memo requests are created as sales orders in SAP ECC. The debit memo request (sales order) items represent the billing-relevant items in the original transaction.

 

In this activity, you determine the SAP ECC sales order types and item categories that the system uses to represent business transactions and items from SAP CRM Service that are to be billed in SAP ECC. You map the following:

 
          • SAP CRM transaction types to SAP ECC sales order types (for debit and credit memo requests)
 
          • SAP CRM item categories to SAP ECC sales order item categories (for debit and credit memo requests)

 

 

 

 

 

Meaning of rejection reason in this customizing:

The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:

                    • Inquiries and quotations: no further references by other documents
                    • Sales orders: no further delivery of items
                    • Contracts: no further creation of release orders
                    • Credit and debit memo requests: no further processing of credit or debit memos

If you enter a reason for rejection, the system automatically cancels any MRP  requirements previously generated for the items.

 
Business Add Ins (BADIs)

 

 

 In CRM:   CRM_EXT_BILLING

 

 

 BADI to manipulte the billing data to be sent to ERP. This BADI can also be found in SPRO -> IMG -> Customer Relationship Management -> Transcations -> Settings for Service Transactions -> Business Add-Ins

 

 

The following customer-specific enhancements are possible for the transfer:

 

            • The CHANGE_DATA_SERVCONF_BILLING method is called when Service Confirmations are transferred.

 

            • The CHANGE_DATA_SERVICE_BILLING method is called when Service Contracts and Service Orders are transferred.
           

 

 

When the business transactions are transferred, sales orders are created in SAP R/3. The items in the sales orders are created from the billing-relevant items from the business transactions. You should ensure that the sales document type and the item categories for the sales order in SAP R/3 correspond to business requirements.

They should just be billing-relevant and not delivery-relevant.

 

In ECC: SRV_BILLING_CHANGE

 

To modify data such as the order reason, billing block, partner, and conditions before data import in ERP. This BAdI can also be found in SPRO -> IMG -> Integration with Other SAP Components -> customer relationship management -> Settings for Service Processing -> Billing integration -> BAdI: Influencing Data for External Billing of CRM Service Documents or Transaction SCRM.

 

 

 

This Business Add-In (BAdI) is used in the Billing (SD-BIL) component. It enables you to modify data from business transactions in SAP CRM Service (service contracts, service orders, and service confirmations) before this data is imported into SAP ECC.

 

The following customer-specific enhancements are available in the BAdI:

 

            • The method SERVICE_BILLING_DATA_CHANGE is called when service contracts and service orders are transferred.

 

            • The method SRVCONF_BILLING_DATA_CHANGE is called when service confirmations are transferred.

 

When service business transactions are transferred from SAP CRM, sales orders are created in SAP ECC, with the billing-relevant transaction items created as sales order items.

 

You can use the above-mentioned methods to influence sales order data, such as the order reason, billing block, partner, and conditions.

You have ensured that the sales document type and the item categories for the sales order in SAP ECC are set up correctly (they should be billing-relevant but, for example, not delivery-relevant).

 

 

 

In any Case the relevant Consulting note 1381563 should be strictly adhered.