Creation of a Budget Billing Plan 

Use

You use the portioning component to generate dates for the budget billing amounts periodically.

You define all the possible budget billing cycles for a portion in scheduling. A standard budget billing cycle is specified in the portion that is valid for all customers in this portion.

The budget billing cycle can be overridden in the contract (for next budget billing plan generation) or directly in the budget billing plan (effective immediately).

Prerequisites

The contracts for which a budget billing plan is to be created must be billable.

All mandatory contracts of a contract account must have the same portion and the same budget billing cycle (except budget billing cycle 00).

Make sure when migrating budget billing plans, that the dates for the budget billing periods – start and end date – are the same as the associated schedule master data. The end of the budget billing period may not be after the end of the billing period defined in the portion.

Activities

You can create a budget billing plan manually or automatically.

To be able to create a budget billing plan manually, the following transactions are available:

·        Create Budget Billing Plan (EA61) for statistical and partial bill procedures

·        Create Payment Plan (EK92) for the payment plan procedure

·        Within Move-In (EC50E)

Create budget billing plan manually

       1.      To create a budget billing plan manually, call up the Utilities Industry menu and then choose Invoicing and open transaction Create Budget Billing Plan.

       2.      Enter the number of the business partner or the contract account in the initial screen.

       3.      You branch to a list of contracts that are allocated to the customer or to the contract account, and for which no budget billing plan exists for the Date of BB period field. In the Date of BB period field, you specify the budget billing period for which the budget billing plan is to be created (the budget billing period is the same as the billing period of the portion from scheduling).

       4.      To create the budget billing plan, select a contract or enter a contract directly in the Contract field.

¡        If you choose a mandatory contract (Joint Invoicing field = 1), the budget billing plan is created with all further mandatory contracts belonging to the contract account.

¡        If you do not choose a mandatory contract, the budget billing plan is only created for this one contract. The amounts that are proposed by the system are determined by extrapolating the contracts belonging to the budget billing plan, and are transferred to the budget billing plan.

The following graphic shows how a budget billing plan is created:

Determination of the due dates in the budget billing plan:

The budget billing period defined by the Date of BB Period field is used to determine the schedule records of the portion, and the associated budget billing request dates/partial bill dates for the budget billing plan. The corresponding due date is calculated for each budget billing request date/partial bill date, based on the payment conditions. You can use enhancement Change Due Dates of a Budget Billing Plan (EA610002) to change the calculated dates once more.

In the case of a move-in, the budget billing period is determined by the move-in date.

Late entry of a move-in:

If the budget billing request dates/partial bill dates and the due dates of all due budget billing amounts are before the creation date, you can no longer create a budget billing plan for the budget billing period determined for the move-in date. In this case, there are two different scenarios:

§         If the creation date of the budget billing plan is before the end of the billing period, the system proposes to create a budget billing plan for the subsequent period.

§         If the creation date of the budget billing plan is after the end of the billing period, the system does not propose to create another plan. Process error TU 078 in enhancement Change Due Dates of a Budget Billing Plan (EA610002) if you want the system to automatically propose the budget billing plan for the subsequent period.

Budget billing amount

The budget billing amount is either determined during extrapolation, or was defined in the directly previous plan as a standing budget billing amount.

In the case of a move-in, the budget billing amount is either determined during extrapolation or transferred as a fixed amount.

In all cases, extrapolation is performed in order to be able to distribute the budget billing amount to the individual subtransactions.

For more information, see the documentation for Budget Billing Amount Determination.

Budget billing items whose budget billing request dates/partial bill dates and due dates are between the move-in date/start of the budget billing period and the creation of the budget billing amount, can no longer be requested. The amount of these items is therefore set to 0 and marked as cleared (clearing reason 06, number of clearing document = budget billing plan number).

This does not apply for the migration of budget billing plans.

Mandatory contracts

If there are several mandatory contracts for a contract account, a joint budget billing plan is created for all contracts.

It a mandatory contract is added retrospectively to a contract account, and a budget billing plan is then created for this contract account, this mandatory contract is added to the existing budget billing plan.

If when creating a budget billing plan, the budget billing request date/partial bill date of an item is before the creation date, and the due date is after the creation date, the system attempts to ‘save’ this due date as follows:

§         The budget billing request date/partial bill date is postponed (creation date + 1 day)

§         The due date is redetermined:

§         New due date < Due date of next item ® Due date is saved
New due date ³ Due date of next item ® Due date is not saved

You can use event IS-U ABP: Change FAEDN, delayed move-in (R992) to override this function.

Create budget billing plan manually

To be able to create a budget billing plan automatically, the following functions are available:

·        During annual consumption billing

·        Migration object BBP_MULT for statistical and partial bill procedures

·        Migration object BBP_EXT for payment plan procedure

Budget billing plan within annual consumption billing

A budget billing plan is created within annual consumption billing in principle in the same way as using transaction EA61 (manual creation). However, there are a few differences:

·        The budget billing period is determined internally (subsequent period of billing period that has just been invoiced).

·        If a budget billing plan exists for the invoiced billing period, it is deactivated.

·        You can not manually change the budget billing plan while it is being created.

The following graphic shows how a budget billing plan is created within YAP:

Migration object BBP_MULT

Migration object BBP_MULT groups together the data for the master data object budget billing plan. A prerequisite for importing data to budget billing plans is a completely structured and billable customer construct. This includes the following:

·        Business partner

·        Contract account

·        Contract

·        Installation

Migration object BBP_MULT supports the structuring of budget billing plans with external scheduling. Therefore, different to the IS-U scheduling for the migrated budget billing plan, for example, the number of items, the amounts to be requested and the due date of the amounts can be structured according to the legacy system.

When the first periodic bill is invoiced, it orientates towards IS-U scheduling when structuring the budget billing plan. This means, for example, that the data for the budget billing plan must be the same as the IS-U scheduling.

The following graphic shows migration with migration object BBP_MULT:

For more information, see the documentation for migration object BBP_MULT in the Migration Workbench.