Show TOC

 Integration with Revenue Accounting

 

You can integrate SAP Convergent Invoicing with Revenue Accounting if you:

If you have integrated SAP Customer Relationship Management (SAP CRM), SAP Convergent Invoicing (in SAP ERP) and SAP Convergent Charging (SAP CC) in the Offer-to-Cash end-to-end process, the integration with Revenue Accounting takes place solely by means of the ERP system. The ERP system transfers all necessary data to Revenue Accounting.

Technical Details

Technical Name of Product Feature

FICA_REVENUE_ACCOUNTING_INTEGR

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

FI-CA 617

Application Component

FI-CA-IN (Integration)

Available As Of

SAP enhancement package 7 (SP09) for SAP ERP 6.0

Required Business Functions

None

Additional Details

In Revenue Accounting, data is updated using revenue accounting items. The following types of revenue accounting items exist in Revenue Accounting:

  • Order items

  • Fulfilment items

  • Invoice items

SAP Convergent Invoicing generates:

  • Order items from provider contract maintenance, and from one-off charges that are transferred to the system as billable items

  • Fulfillment items during the transfer of billable items to rated consumption

    The interface component Integration with Revenue Accounting (REVENUE_ACC) provides the fields in the interface for transferring billable items that you use for transferring data that is needed for Revenue Accounting to billing and invoicing.

  • Invoice items from invoicing

You control the type of revenue accounting items the system creates using the service types assigned to provider contract items and billable items.

Creation of Order Items from the Provider Contract

If the system is configured for it, the ERP system generates order items (for Revenue Accounting) for contract items, when you create and change provider contracts.

For each contract item affected by a change, the system generates at least one order item for Revenue Accounting. Each order item consists of a main item and dependent conditions. The conditions consist of a condition for the total transaction price, and, if a standalone selling price is entered in the item, a condition for the total standalone selling price. The system determines the values for the service type for recurring charges, as well as the condition types, from Customizing.

For each service type of a contract item, the ERP system generates a separate revenue accounting item, consisting of a main item and a condition (if the system is configured for this). The system determines the condition type from Customizing.

There could be additional service types entered on the contract item. These service types reflect the consumption affecting the contract item, without an amount or quantity being entered. The system, therefore, identifies the main item as an estimated quantity, and does not show an amount in the condition. In SAP Revenue Accounting and Reporting, you can use a BRFplus function to add the quantity and amount.

If you create or change contracts, the system processes event 8205 before saving the revenue accounting items. You can use this event to enrich the items with additional information.

Example Example

You can use event 8205 to change customer fields or other allowed fields in main items. Or you can use it to adjust existing conditions or to add new conditions.

End of the example.

Note Note

When you change amount fields or add conditions, the system marks the revenue accounting items to reflect this.

End of the note.

If you change a provider contract in SAP CRM, you can enter a change reason. The system updates this change reason in the provider contract item in the ERP system and it is copied to the revenue accounting item. You can use this entry in reporting in Revenue Accounting.

Example Example

In the case of a contract renewal, you create a new revenue accounting contract in Revenue Accounting for the new performance obligations to be created. You do this based on the change reason.

End of the example.

Creating Order Items from Billable Items for One-Off Charges

When billable items for one-off charges are transferred, the system generates order items for Revenue Accounting.

The system uses the service type you assign to billable items to determine if a billable item is a one-off charge that is relevant for Revenue Accounting.

In posting area 8172, you define the derivation of the service type for one-off charges reported from SAP CRM.

Creating Fulfillment Items

When billable items for rated consumption are transferred, the system generates fulfillment items for Revenue Accounting.

The system determines if a billable item leads to the creation of a fulfillment item based on the service type that you assign to the billable item using posting area 8122.

The treatment of fulfillment items is different from all of the other types of revenue accounting items mentioned here. The system does not create fulfillment items individually for each billable item. Instead it creates a fulfillment item for an aggregate of billable items, in order to reduce the volume of data transferred to Revenue Accounting.

Creation of Invoice Items

If your system is configured for it, invoicing generates revenue accounting items for line items that are relevant for Revenue Accounting. These revenue accounting items are used for reporting invoicing results to Revenue Accounting.

You specify by how you configure the service type assigned to the invoicing document item, if the invoicing document item is relevant for creating invoice items for Revenue Accounting.

Transferring Data to Revenue Accounting

You use a mass activity to forward the revenue accounting items created by SAP Convergent Invoicing to Revenue Accounting. On the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step Forward Postings Next navigation step Execution Next navigation step Revenue Accounting Transfer End of the navigation path (transaction FP_RAI_TRANSF).

You can use the following as selection criteria:

  • Source Document Item Type

    You can enter one or more source document item types: order item (contract item), order item (one-off charges), fulfillment item, invoice item.

  • Company Code

    You can select data from several company codes.

  • Business Partner

    You can select several business partners.

  • Selection To

    You can restrict the data selected to a specific time period.

The mass activity creates revenue accounting items in the following order:

  • Order items from provider contracts

    During the generation, the system uses the time stamp to check if an older version of the revenue accounting item exists that was not yet transferred. If there is an older version, the system takes only the newest version into account.

  • Order items from one-off charges

  • Fulfilment items

    To reduce the volume of data transferred to Revenue Accounting, the system aggregates billable items into fulfillment items during a preliminary step.

    In the standard system, the mass activity aggregates the billable items into fulfillment items and forwards the fulfillment items in one step. However, you can change this by choosing a different processing level. Then the mass activity aggregates billable items into fulfillment items in one run, and transfers the data to Revenue Accounting in a later run.

  • Invoice items

The revenue accounting items forwarded to Revenue Accounting receive the date and time they were sent.

Reconciliation of Data

You can display and analyze revenue accounting items in Contract Accounts Receivable and Payable. On the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step Forward Postings Next navigation step Reconciliation Next navigation step Display Revenue Accounting Items End of the navigation path (transaction FP_RAI_MON).

In Revenue Accounting, you can find discrepancies between the data sent and the the data stored in Revenue Accounting in transaction FARR_CHECK_CONS, which checks data consistency.

Archiving

The system makes use of the new table of service types for the provider contract (DFKK_VT_ST) when archiving provider contracts (archiving object FI_MKKCAVT). See Archiving of Provider Contracts (FI_MKKCAVT)).

Affects on Customizing Settings

You activate the integration with Revenue Accounting and configure the RFC destination to the revenue accounting system, meaning the system, in which SAP Revenue Accounting and Reporting is running, in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Integration Next navigation step Revenue Acccounting End of the navigation path.

In the activities that follow, you then configure your system for the data transfer to Revenue Accounting.

Additional Information

Integration with Revenue Accounting