Understanding Inbound Processing and Revenue Accounting Contract Management

Customizing for BRFplus:

1. In the IMG for Revenue Accounting under Revenue Accounting → Inbound Processing → Revenue Accounting Item Management → Assign BRFplus Applications to Revenue Accounting Item Classes, assign a BRFplus application to the Revenue Accounting Item class of the order item class type. For each order item class, enter the context structure to be used in the Revenue Accounting Item generation process and assigned in the BRFplus application.
2. Under classic inbound processing for each order item class, enter the context structure to be used in the Revenue Accounting Item generation process and assigned in the BRFplus application. In the IMG for Revenue Accounting, choose Revenue Accounting → Inbound Processing → Revenue Accounting Item Management → Maintain BRFplus structure. Then you can derive the G/L accounts from any characteristics of order items.

The following points must be considered:

• DT_PROCESS_HEADER: Should be kept in sync with the decision table for SD RAI processing application in case of a hybrid BRIM/SD scenario.
• DT_PROCESS_POB: Driven from SAP Billing and Revenue Integration Management service type.
• DT_PROCESS_SSP: Billable Items do not carry conditions. BITs don't have an SSP condition.
• DT_RAI_REC_ACCT_DET: The receivables account is available in SAP Billing and Revenue Integration Management, but is not determined at contract inception. Event 8204 can be used to fill the receivables account field on the main item level.
• DT_RAI_REV_ACCT_DET: The revenue account is available in SAP Billing and Revenue Integration Management but is not determined at contract inception. Event 8204 can be used to fill the revenue account field on the main item level.

In SAP Revenue Accounting and Reporting, data is updated using the Revenue Accounting Item objects.

The following types of Revenue Accounting Items exist:

• Order items, representing, for example, a provider contract item or a one-off BIT and used to create a performance obligation in SAP RAR.
• Fulfillment items, representing, for example, usage data and used to realize revenues.
• Invoice items, representing, for example, CI invoice items and used to post an invoice correction.

The integration diagram shows how Convergent Invoicing creates transfer records in the different CI processes by using the mass run for Revenue Accounting items generation. The following information is sent to SAP Revenue Accounting and Reporting:

1. Order items
   1. Triggered from provider contract maintenance.
   2. One-off charges that are transferred to the system as billable items.
2. Fulfillment items during the transfer of billable items.
3. Invoice Items from Invoicing.

Based on the customizing settings in the system, SAP S/4HANA generates order items for SAP RAR, when you create or change provider contracts. The item type for order items is CAOI - Order Item (Contract Item).

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. From Customizing, the system determines the service type for recurring charges, as well as the condition types.

Event 8204 can be used for the calculation of total amounts on transfer records based on prices per recurrence period and runtime of provider contract items.

It's called once for price determination per transfer record representing a recurring fee.

Event 8205 is called once per provider contract update. You can use it for adaptation of the order item transfer records that are proposed by standard.

When billable items for one-off charges are transferred, the system generates transfer records for SAP RAR. The item type for order items for one-off charges is CAOO - Order Item (One-Off Charge).

The system derives whether a billable item is a one-off charge that is relevant for Revenue Accounting from the service type you assign to the billable item.

Performance obligations in SAP RAR can be fulfilled either on a time basis or on an event basis.

Consumption-based services are fulfilled on an event basis and refer to the Consumption fulfillment event. The SAP S/4HANA system generates transfer records for fulfillment items by aggregating the billable items for rated consumption. The item type for fulfillment items is CAFI - Fulfillment item.

When loading billable items, the system generates fulfillment transfer records on the billable item level and stores these records in table DFKKBIXBIT_RAI.

The fulfillment items are transferred using the mass activity for transferring to Revenue Accounting (transaction FP_RAI_TRANSF). This does not generate fulfillment items for each billable item, but aggregates the fulfillment transfer records on billable item level before transfer. This creates a transfer record for each aggregate. This is enriched with the Revenue Accounting item ID and is stored in table DFKKRA_RAI_MI. This reduces the volume of data for the fulfillment items to be transferred. Afterward, the mass activity forwards the fulfillment items to Revenue Accounting. Aggregation and transfer can be executed in the same run, or you can also execute aggregation and transfer in separate runs.

Event 8208 is called once per BIT during billable item upload. It can be used for adjustment of fulfillment transfer records on level of billable items (table DFKKBIXBIT_RAI).

Based on the customizing settings of the system, invoicing generates transfer records for invoice items corresponding to invoicing document items that are relevant for revenue accounting. The item type for invoice items is CAII - Invoice item.

Whether the invoicing document item is relevant is determined based on the provider contract item, in combination with the configuration of the service type that is assigned to the invoicing document item.

Event 8207 is used to adjust invoice item transfer records that are proposed by standard; for example, you can adapt exchange rates for amounts in local currencies. It's called per invoicing document and provider contract item.

Event 8209 can be used to split one main item into multiple main items, or you can prevent an item to be transferred to RAR.