02-21-2012 11:02 PM
Hi,
Client has issue that wrong variant control is used for certain operand, which result in valid to date and alternative valid to date in ETTIFN are updated with 12/31/9999. This error will result in Billing failed for next billing cycle. So there is a clean up program to correct Valid to date in ETTIFN. However, as billing doc is reversed, the valid to date for previous billing doc will be updated by alternative valid to date automatically. My question is do anyone knows if there is way to prevent valid to date being updated by alternative valid to date during reversal. Or is there any event or FM I can leverage?
Thanks in advance.
02-22-2012 8:47 AM
Hi,
Which variant control are you using?
In variant programs which are writing some information into ETTIFN (INFACT*) you can use following variant controls:
Update to billing period with proration
Update total to the billing period (will insert ENDABRPE into installation facts)
Update total to future period (will insert 31.12.9999 into installation facts)
Initialization of quantity in the installation facts
Update from beg. of current period until future period
or
you can try to use following enhancements in billing reversal:
EBIA0007 - IS-U: customer-defined activities in billing reversal
EBIA0008 - IS-U: customer-defined activities in billing reversal update
or
try to develop own variant program based on some variant program INFACT*, which will change the date to in ETTIFN according to the some conditions.
Vlado
02-22-2012 4:59 PM
the variant: Update total to future period is used before, which is caused the issue of billing. Now the variant is changed to Update to billing period with proration.