Ansicht
Dokumentation

_ISUBIBDRS_000064 - Calculation to the Day for Aperiodic Changes

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Calculation to the day in the case of aperiodic changes controls how schema steps and values are processed if they are added to or omitted from the billing period.

The system supports three procedures. Note that the time portions to the day are calculated in much the same way as processing to the day in the case of move-in/out:

• Procedure 1

• Calculation of month-based time portions if a schema step deviates from the billing period, but still falls within the interval in the portion.

• Calculation of time portions to the day if a schema step falls outside the interval.

Example 1 for procedure 1
Interval = 27 to 35 days

        !------------------Billing period-----------------------!

        !-------------------Schema step 1-----------------------!
      1/10                     32 days                         2/10
            !---------------Schema step 2---------------------!
          1/12                 29 days                       2/9

Time portion for values of schema step 1 = one month
Time portion for values of schema step 2 = one month

Example 2 for procedure 1

With prorations (due to VAT change, for example)

        !------------------Billing period-----------------------!

        !-------------------Schema step 1---!-------------------!
      1/10              22 days            2/1    10 days      2/10
            !---------------Schema step 2---!-----------------!
          1/12          20 days            2/1     9 days    2/9
                  !---------Schema step 3---!-------------------!
                1/16    16 days             2/1    10 days    2/10

Time portion for values of schema step 1 = 1 month (month-based)
===> time portions for partial periods = 22/32 month and 10/32 month

Time portion for values of schema step 2 = 1 month (month-based)
===> time portions for partial periods = 20/29 month 9/29 month

Time portion for values of schema step 3 = 26 days (to the day)
===> time portions for partial periods = 16/30 month 10/30 month with reference to the standard month = 30 days

• Procedure 2

• Calculation of month-based time portions if a schema step corresponds exactly to the billing period and falls within the interval in the portion.

• Calculation of time portions to the day if a schema step deviates from the billing period or the billing period does not fall within the interval.
  

Example for procedure 2

Interval = 27 to 35 days

With prorations (due to VAT change, for example)

        !------------------Billing period-----------------------!

        !-------------------Schema step 1---!-------------------!

      1/10              22 days            2/1    10 days      2/10

            !---------------Schema step 2---!-----------------!

          1/12          20 days            2/1     9 days    2/9

                  !---------Schema step 3---!-------------------!

                1/16     16 days           2/1    10 days     2/10

Time portion for values of schema step 1 = one full month (month-based), since the step corresponds exactly to the billing period and it falls within the interval.

===> time portions for partial periods = 22/32 month and 10/32 month

Time portion for values of schema step 2 = 29 days (to the day), since the step deviates time-wise from the billing period.

===> time portions for partial periods = 20/30 month and 9/30 month with reference to the standard month = 30 days

Time portion for values of schema step 3 = 26 days (to the day), since the step deviates time-wise from the billing period and it does not fall within the interval.

===> time portions for partial periods = 16/30 month and 10/30 month with reference to the standard month = 30 days

• Procedure 3

• Calculation of month-based time portions if a logical value of a schema step falls within the interval.

• Calculation of time portions to the day if a logical value falls outside the interval.
  

A logical value could, for example, be a device in a rental price variant (such as SETTLE01 variant). In contrast to the other two procedures, the decision whether month-based billing is to be executed is based on the billing days of the logical value, not on the length of the schema step. The procedure also affects the billing of reference values. This is because several logical values come into question at the same time only during billing of device rental prices and reference values.

Other values - such as factors, quantities, demand and prices - must cover the complete schema step period in the variants where they are used. Values such as these are processed in schema steps with procedure 3, in the same way as if the schema step had procedure 1.

Interval = 27 to 35 days in the following examples for procedure 3

Example 1 for procedure 3

With device rental price

        !-----------------------Device 1---------------------------!
      1/10                      32 days                          2/10
            !--------------------Device 2-------------------------!
          1/12                   29 days                         2/9

Since both devices (logical values ) fall within the interval, a time protion of one month is calculated for each of them.

Example 2 for procedure 3

With device rental price

        !------------------------Device 1---------------------------!
      1/10                       32 days                           2/10

                            !---------------Device 2----------------!
                          1/20              22 days                2/10

Time portion for device 1 = 1 month
Time portion for device 2 = 22/30 month (standard month = 30 days)

Example 3 for procedure 3

With device rental price and proration (due to change in tax, for example)

        !------------------------Device 1---!-----------------------!
      1/10        22 days                  2/1     10 days         2/10

            !--------------------Device 2---!-----------------------!
          1/12    20 days                  2/1     10 days         2/10

Since both devices (logical values) fall within the interval, a total time portion of one month is calculated for each of them. The time portions for the individual time slices are calculated as follows:

Time portions for device 1 = 22/32 month and 10/32 month
Time portions for device 2 = 20/30 month and 10/30 month

Note

For both of the second time slices, different time portions are calculated for the devices although both time slices cover the same period.

Example 4 for procedure 3

With device replacement

     !------------------------Device 1---------------------------!
   1/10                       32 days                          2/10

         !----------Device 2-------------!------Device 3-------!
       1/12      20 days                2/1     9 days        2/9

In the case of a device replacement, device 2 and device 3 are considered as a single logical value. This means that a time portion of one full month is calculated on the basis of the 29-day period (20 + 9).

Warning

For a device rental price the system can recognize a logical value in the case of aperiodic changes (such as device replacement) in the following ways:

Case A: Rental price is levied at the device level

In this case, consecutive time slices for devices can only be recognized as a single logical value if a device was replaced. Only in the case of a replacement can the system recognize that in example 4 device 2 logically becomes device 3. If, instead, device 2 was removed and afterwards device 3 was installed, the system would consider the two devices as two independent logical values. In this case, the time portions would be calculated to the day as 20/30 and 9/30.

Case B: Rental price is levied at register level

In this case, consecutive time slices for registers can only be recognized as a single logical value if you defined in the other installation structure that the registers replace each other. You can manually maintain logical register allocations in the installation structure, if this has not already taken place automatically during a device replacement.

The following applies to both cases, A and B: If you change the level on which the rental price is levied from the device to the register level or vice versa, the system cannot recognize a logical transition. Such changes are always interpreted as a change of the logical value.

Example 5 for procedure 3

With gaps in the period

        !-----------------------Device 1---------------------------!
      1/10                      32 days                          2/10

            !-----Device 2------!      !----------Device 2---------!
          1/12    13 days     1/24   1/27         15 days         2/10

The time slices for device 2 are handled as a single logical value despite the gap. This means that a time portion of one full month is calculated on the basis of the 28-day period (13 + 15). The time portions are 13/28 month and 15/28 month.

Note

The information for procedure 3 (per logical value) also applies to the calculation of time portions for reference values. Since there is no function similar to device replacement for reference values, the logical value is always the individual reference value itself.

BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 17499 Date: 20240606 Time: 075535     sap01-206 ( 137 ms )