LV61A081 LV61A082 - pricing date vs billing date

[ViviStagno]

Dear Collegue 

We have had a argentine customer claim for a customer invoice because it has wrong calculation of J1X1 Perception and J1A1 Perception. 
We have checked the cause: the requirements 81 and 82 where not fullfilled because the customer master tax grouping records ( table knat) was checked against the pricing date ( komk-prsdt) instead of the billing date ( komk-fkdat) 

In fact , we have found note 1747589 - 1256361 that applies a correction to formula 333 for using billing date instead of pricing date, but 
we have not found any note to be applied related to requirements 81 and 82 for correcting the way it access to table knat using billing date .
We attached the abap code for routines  81 and 82 were it is used the pricing date ( komk-prsdt) for table knat.  

Aditionally, J1X1 and J1A1 conditions are set as pricing date = billing date  in the sap standard ( T685A-KPRDT = C = billing date ) 

Someone had had the same problem? Did you find a solution with a SAP oss note?
We are willing to avoid to  copy the requeriments 81 and 82 to a custom solution to use billing date instead of pricing date , if there is a note to be applied. 

Also we find that in these routines it is not check standard localization table j_1at001tc where it is defined if the perception is active por the company code. 

It seems argentine localization requirements 81 and 82 are not as far as complete ...

Thanks in advance for your imputs
Viviana 

routine 81 - program LV61A081
* check if date is in the subjected interval and therefore valid
      if knat-sbjdf le komk-prsdt and
         knat-sbjdt ge komk-prsdt.
         lv_subrc = 0.
      endif.

routine 82 - program LV61A082
 check if date is in the subjected interval and therefore valid
    if knat-sbjdf le komk-prsdt and
       knat-sbjdt ge komk-prsdt.
      lv_subrc = 0.

[Lakshmipathi]

SAP note 1256361 should address this issue for sure.  In case, you still have an issue, ensure, the routines 82 & 333 are set as per SAP note 2555008. 

With all these settings, still, it is not working, then, before going for any custom validation, raise a ticket with SAP by referring note 1256361 has not solved your issue.  They will guide you