SAP ABAP Message Class AJ Message Number 652 (The to-date for &1 has been adjusted)
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U-BI (Application Component) Contract Billing
     ⤷ EE20 (Package) IS-U: Billing
Attribute
Message class AJ  
Short Description Billing program    
Message Number 652  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20050224   
Message Text
The to-date for &1 has been adjusted
Help Document

Diagnosis

You have directly or indirectly adjusted the to-date of an operand value that was updated in the installation facts by automatic billing.

In the following cases, an adjustment can lead to cancellation of the next billing that updates the values for this operand in the installation facts:

  • Updating an operand in the future:
    • A new manual value is entered for a date that is after the end of the billing period of the next (future) updating billing.
      • Example: You bill at the end of the month. The operand is updated on the first day of each month, starting from next month. Billing took place on March 31st. The current operand was updated from April 1st to December 31st 9999.
      The entry of a manual value after May 1st leads to cancellation of the next billing until April 30th.
    • The operand value is not required in the next billing, therefore no value is provided.
      • Example: You bill at the end of the month. The accumulated consumption is updated for the price determination for the next month.
      If this operand is restricted so that no new value is entered, it can lead to cancellation due to the periods without value provision.
  • Updating an operand from the start of the billing in the future:
    • A new manual value is entered for a date that is after the start of the billing period of the next updating billing.
      • Example: You bill monthly. The accumulated consumption is updated from the start of the billing period in the future. The period of the last billing is March 1st to March 31st. The current operand was updated from March 1st to December 31st 9999.
      The entry of a manual value after April 1st leads to cancellation of the next billing from April 1st.
    • The operand value is required in the next billing, but no values are provided.
      • Example: See above.
  • Updating an operand in the billing period:

    You are in principle not permitted to make any changes to operands that are reimported and/or retrospectively updated in the installation facts during floating backbilling or period-end billing. This can cause a number or errors leading to cancellation of the billing and incorrect bills.

  • Reversal:

    The reversal reactivates the operand values. If time overlaps occur in the installation facts with entries that have been entered manually, it is not possible to reverse the billing document. In this case you must first delete the manual values from the installation facts, and then re-attempt the reversal.

System Response

Procedure

Procedure for System Administration

History
Last changed on/by 20110810  SAP 
SAP Release Created in