There's a list of OSS notes for the issue between BSET and BSEG on marketplace.
There's even custom program developed by SAP in order to clear differences for already existing documents. From my understanding, this program is nothing but copying value from BSEG into BSET or the other way around, but not fixing the actual issue.
Differences appear in standard reports, such as EC Sales List RFASLM00, Tax return RFUMSV00 and etc. etc.
Difference can be also checked by comparing tax base amount in FB03 with BSET-LWBAS. There you will see that indeed BSET-LWBAS is having very minor difference with BSEG-DMBTR (or WRBTR, depending on the currency of posted invoice, where BSEG-BUZEI= 'T').
The difference is very insignificant, but it is valid from company code to company code. And it is valid only for RV documents, documents posted from SD.
Apparently, this is not even program issue, this is incorrect handling of VA01/VF01 postings from SD side. If you go on checking VF03, i.e. original invoice from FI document, you would notice that among all, there's condition type, having very small value assigned to it, because of which tax base amount is getting incorrectly updated in FI, when invoice released.
So, whenever you have BSET/BSEG inconsistencies, it is better not to rush fixing it on FI side with custom programs, or changing logics of standard RF* tax reports.
There's even custom program developed by SAP in order to clear differences for already existing documents. From my understanding, this program is nothing but copying value from BSEG into BSET or the other way around, but not fixing the actual issue.
Differences appear in standard reports, such as EC Sales List RFASLM00, Tax return RFUMSV00 and etc. etc.
Difference can be also checked by comparing tax base amount in FB03 with BSET-LWBAS. There you will see that indeed BSET-LWBAS is having very minor difference with BSEG-DMBTR (or WRBTR, depending on the currency of posted invoice, where BSEG-BUZEI= 'T').
The difference is very insignificant, but it is valid from company code to company code. And it is valid only for RV documents, documents posted from SD.
Apparently, this is not even program issue, this is incorrect handling of VA01/VF01 postings from SD side. If you go on checking VF03, i.e. original invoice from FI document, you would notice that among all, there's condition type, having very small value assigned to it, because of which tax base amount is getting incorrectly updated in FI, when invoice released.
So, whenever you have BSET/BSEG inconsistencies, it is better not to rush fixing it on FI side with custom programs, or changing logics of standard RF* tax reports.
Комментариев нет:
Отправить комментарий