Ansicht
Dokumentation

Process: Billing Plan Synchronization ( RELNGG_30D_BPLANSYNC )

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Short text

Process: Billing Plan Synchronization

Description

This process enables you to synchronize billing plans between two sales documents. One of these documents has to supersede another and both have to refer to the same serial number in the IBASE.

A sales order item for a SW license contains the original billing plan. This is the origin of any recurring charge billing associated with the document.

Create license bump

A new bump order is also a recurring charge document that contains its own billing plan for the new/changed license information. In order not to overbill the customer, the old billing plan has to be stopped as soon as the new billing plan starts. See the Create License Bump Release Note for more information.

Note: If an overbilling occurred in the old billing plan because of advance billing (billing in advance of the current period), and the billing plan is stopped before period end, a credit must be posted to the customer with the pro-rated overbilled amount.

Billing plan synchronization

Step 1: The link process

• You create the superseding document.

• You select the serial number for the bump from the IBASE.

• A list of predecessor documents (orders) with billing plan items is displayed that are still active for this IBASE record (in a standard scenario, only one outstanding active document should exist).

• You mark the billing plan and order item to be synchronized with the new billing plan.

• When you save the new order, the old billing plan number is stored in the new billing plan.

• The new billing plan number is stored in the old billing, together with a synchronization status.

Step 2: The synchronization process

This step can be triggered:

• As a follow up of the workflow created by the bump process after the IBASE record has been flagged with a status (see Workflow based on IBASE status),

• From a direct change transaction of the superseded document, or

• By a new billing plan synchronization transaction.
  

You can access the synchronization transaction in the sales area under "order."

The billing plan synchronization transaction

This transaction allows you to save a selection of order documents into a list. Then you can process each document individually, or mark some or all documents and execute an automatic synchronization.

A range of selection criteria allows you to select only those documents where synchronization is still outstanding by using the synchronization status.

Note: This transaction can be run in the background or foreground, and can execute the synchronization automatically for all documents selected.

Synchronization status

The following statements describe the various IS-SW synchronization statuses:

1. The billing plan of document item has not been synchronized yet, and full synchronization is possible.
2. The billing plan of the document item has not been synchronized, and no automatic synchronization is possible because of the following:

• The superseded document (i.e., the initial order) had an item quantity greater than one and several serial numbers are assigned.

• One of these serial numbers has been bumped and the new billing plan only reflects the billing and pricing of this serial number.

• The old billing plan cannot be synchronized automatically, and you must take manual action and choose the corrected values for the superseded document.

1. The superseding document (e.g., a bump order) has been deleted, and now automatic synchronization can take place. You have to synchronize the plans manually, if it is still required.

Change system parameters in customizing

The billing plan synchronization is an automatic process and always runs for recurring charge bump items.

Only the credit memo type and the credit memo block has to be customized. You have to customize a credit memo type if one must be be created for overpayment (if not, you get a warning). The credit memo block is optional. The system does not check if the selected type is not a credit memo.

To look this information up in the IMG, use the path: Sales document -> Billing Plan -> Date Category. The topic is entitled: Define Date Category.

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5620 Date: 20240603 Time: 144426     sap01-206 ( 73 ms )