Show TOC

Background documentationIntegration with SAP Convergent Charging Locate this document in the navigation structure

 

SAP Convergent Charging handles the rating (pricing) and charging (determination of invoice recipient) of services. As a result billable items are created that you transfer to Billing in Contract Accounts Receivable and Payable and that – for example in the case of rerating – you can also reverse.

Features

Billing in Contract Accounts Receivable and Payable offers the following Application Programming Interfaces (APIs) as RFC function modules. SAP Convergent Charging uses these APIs:

  • FKK_BIX_BITCAT_LIST_GET_SAPCC

    This API supplies the list of billable item classes that are released as productive and that you have created for SAP Convergent Charging.

  • FKK_BIX_BITCAT_STRUC_GET_API

    This API supplies the technical definitions for a billable item class, such as the field names in the interface for the class.

  • /1FE/<billable item class>_BIT_CREATE_API

    This API is generated for a billable item class and sends the items to SAP Convergent Invoicing.

    Note Note

    You do not have to configure a destination in order to send billable items. A destination is only required if you process telecommunications tax data.

    End of the note.

  • FKK_BIX_BIT_REVERSE_CHECK_CC

    For a record consisting of source transactions, contract account, and contract reference, this API provides the information about whether reversal is allowed in SAP Convergent Invoicing for the related billable items.

  • FKK_BIX_BIT_REVERSE_CC

    This API reverses all billable items for a record consisting of source transactions, a contract account and a contract reference. For already billed items, the system generates offsetting items, which compensate for the original items. The system first stores the request for reversal as a reversal request on the database. The reversal request is either processed immediately by the system, or you process the reversal request in a separate step.

Billing in Contract Accounts Receivable and Payable also offers the API FKK_BIX_BITCAT_LIST_GET_API. This API supplies the list of billable item classes that are released as productive. SAP Convergent Charging does not use this API.

In Customizing under   Integration   Convergent Charging   Display Interfaces to SAP CC  , you can get an overview of the interfaces between Contract Accounts Receivable and Payable (FI-CA) and SAP Convergent Charging (SAPCC). You receive a list of all interfaces. You can limit the display by choosing a group. To see detailed information on an interface, double click on the interface.

Activities

To adopt billable items from SAP Convergent Charging and process them in Billing in Contract Accounts Receivable and Payable, you perform the following steps in your ERP system:

  1. Configure an appropriate billable item class in Billing in Contract Accounts Receivable and Payable.

    To do so, in Customizing for Contract Accounts Receivable and Payable, choose   Integration   Billing in Contract Accounts Receivable and Payable   Billable Item Classes   Maintain Billable Item Classes  .

  2. Activate the interface component SAP Convergent Charging for the class.

  3. Activate the billable item class. To do so, in Customizing for Contract Accounts Receivable and Payable, choose   Integration   Billing in Contract Accounts Receivable and Payable   Basic Data   Activate Billable Item Classes  .

  4. Enter transfer rules for the billable item class.

    To do so, in Customizing for Contract Accounts Receivable and Payable, choose   Integration   Billing in Contract Accounts Receivable and Payable   Billable Item Management   Define Processing Rules and Program Enhancements   and enter the transfer rule Add Items with Errors as Raw Data.

  5. Generate the objects for the class in your test system or live system.

    To do so, in Customizing for Contract Accounts Receivable and Payable, choose   Integration   Billing in Contract Accounts Receivable and Payable   Billable Item Classes   Generate Interfaces for Billable Item Classes  .

  6. Make the basic settings for the reversal of billable items; define the standard exception reasons for reversal; and specify if reversal requests are processed immediately or in a separate process. To do so, in Customizing for Contract Accounts Receivable and Payable, choose   Integration   Billing in Contract Accounts Receivable and Payable   Reversal of Billable Items   Make Basic Settings   and Define Processing Rules.

  7. Create a user from the SAP Easy Access screen under   Tools   Administration   User Maintenance   Users  . On the Logon Data tab, enter the User Type Communication Data.

  8. Assign this user the authorizations for the authorization objects F_KKBIXBIT and F_KKBIXCON.

    Using the access data of this user, SAP Convergent Charging calls the APIs in SAP Convergent Invoicing in the ERP system.

  9. Assign authorization for authorization object S_TABU_DIS to this user. Using the access data of this user, SAP Convergent Charging calls the SAP NetWeaver API BAPI_CURRENCY_GETLIST in the ERP system.

Now perform the following steps in SAP Convergent Charging to configure the charging master data for the service provider. For more information, see the documentation for SAP Convergent Charging.

  1. Create a catalog in the Core Tool.

  2. Create a mapping for billable items and a charged item class.

    SAP Convergent Charging offers a list of the billable item classes that you have created in Billing in Contract Accounts Receivable and Payable. Choose a billable item class. SAP Convergent Charging automatically creates a mapping for billable items and a charged item class that is based on the billable item class you choose.

  3. Create a chargeable item package and a chargeable item class.

  4. Create the charges.

  5. Create a charge plan and assign charges.

    In each charge of a charge plan, you configure the generation of charged items and billable items. That means you specify which values the system adopts in the individual fields. You can reuse values from rating or charging or the processing of chargeable items.

    Example Example

    SAP Convergent Charging automatically derives the field Amount of the Billable Item (BIT_AMOUNT) from the charged amount.

    End of the example.

    You can assign multiple charge plans to a product.

  6. If it is relevant for your processes, create master data for the refill of prepaid accounts.

  7. Create a subscriber account in SAP ERP or SAP CRM.

    Specify the connection of the master data to Billing in Contract Accounts Receivable and Payable. In the external account key, enter the number of the contract account in Billing in Contract Accounts Receivable and Payable. Under External Billing System, enter the number of the business partner in Billing in Contract Accounts Receivable and Payable.

  8. Create a provider contract in SAP CRM.

  9. Create an incoming entry.

You can change billable item classes in Billing in Contract Accounts Receivable and Payable. The changes that are allowed depend on the configuration status of the class (see Configuration of Billable Item Classes).

Note Note

Note:

  • If a class has the configuration status In Processing or Transportable, you can change the interface in any way you like. In particular, this means that you can delete fields from the interface. Since SAP Convergent Charging does not support the deletion of individual fields in a charged item class, you have to create a new mapping for billable items with a new charged item class. You also have to adjust all dependent objects in SAP Convergent Charging accordingly (such as the charges in the charge plan).

  • If a billable item class has the configuration status Released as Productive, you can only make compatible changes to the interface. This means that you can only add fields to the interface. The system adds the new fields to the end of the structures in the interface. As a result, you can continue to adopt billable items using the corresponding generated RFC function module, without it being necessary for SAP Convergent Charging to fill these new fields (offset problematic with RFC calls). If SAP Convergent Charging is to fill these new fields with values, you must identify all changes to the configuration so that SAP Convergent Charging can generate or convert the corresponding data. You also have to determine the method for converting these changes. For more information, see the configuration guide for SAP Convergent Charging.

End of the note.

SAP Convergent Charging determines amounts with up to six decimal places. You can process these amounts in the ERP system. For more information, see Handling Amounts with Increased Precision.

More Information

For more information about SAP Convergent Charging, see the SAP Help Portal at http://help.sap.com   SAP Business Suite   SAP Convergent Charging   .