SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

difference for tax clearing too large

Former Member
0 Kudos

Dear All,

I am getting following error while doing the invoice simulation in EA00:

"Difference for tax clearing too large (contract account: 30008308, diff.: 20.46)"

Message no. EB 008

I have done follwing tax settings till now.

1. Defined Tax procedure (other than jurisdiction tax procedure).

2. Defined tax codes ZH as 6 % sales tax with key MW5, I0 as 0% Input Tax with key VST, O0 as 0 % output tax with key MWS.

3. Assigned tax accounts for above tax codes with proper tax settings in GL master.

4. In FICA, Assigned FICA tax codes ZH, I0 and O0 to corresponding tax codes in FI (as given above).

5. Assigned the Tax accounts to tax code and key combination in FICA.

6. Sub-transactions assigned in Billing Schema are 0022 and 0011for Billing, and 0010 and 0020 for Budget boilling. So i have assigned the tax codes to

0100/0011, 0100/0022, 0200/0011, 0200/0022.

7. Also i have tried to do posting through FPE1 with these Main and Sub-transactions and posted successfully.

Please help me to solve this problem which has stopped the posting of invoices.

Regards,

1 ACCEPTED SOLUTION

hnmuralidhara
Active Contributor
0 Kudos

Dear Priyank,

This is caused by a program error which can occur if there is a cross-company code block formation of the line items for the tax determination. If so, Pls check and implement SAP Note 792194.

If you are using backbilling or period-end billing. The document to be billed contains reversal lines that are relevant for posting but are not relevant for printing. The corresponding grouping lines with CSNO = '999998' (consecutive schema step number) are missing. This situation may occur if the TE301-NOCOMP indicator ('No Line Compression in Backbilling') within a backbilling period was changed, or if different backbilling groups are involved for which the 'No Line Compression in Backbilling' indicator is set differently in the TE301 table. If so, Pls check and implement SAP Note 1046211.

Bye,

Muralidhara

View solution in original post

4 REPLIES 4

hnmuralidhara
Active Contributor
0 Kudos

Dear Priyank,

This is caused by a program error which can occur if there is a cross-company code block formation of the line items for the tax determination. If so, Pls check and implement SAP Note 792194.

If you are using backbilling or period-end billing. The document to be billed contains reversal lines that are relevant for posting but are not relevant for printing. The corresponding grouping lines with CSNO = '999998' (consecutive schema step number) are missing. This situation may occur if the TE301-NOCOMP indicator ('No Line Compression in Backbilling') within a backbilling period was changed, or if different backbilling groups are involved for which the 'No Line Compression in Backbilling' indicator is set differently in the TE301 table. If so, Pls check and implement SAP Note 1046211.

Bye,

Muralidhara

0 Kudos

Thanks Muralidhara,

The SAP note 792194 was already implemented and the sap note 1046211 is from version 600 onwards. Our IS-U version is 464. So the problem seems to be something else. Please suggest.

Regards,

0 Kudos

Dear Priyank,

Post this message to SAP Service Market place with High priority.

Bye,

Muralidhara

0 Kudos

Dear Muralidhara,

when I try to invoice a customer with EA19 I get the following error message:

Difference for tax clearing too large (contract account: 2000000104, diff.: 84,59)

Message no. EB008

This error has been discussed before: http://scn.sap.com/thread/475003 (you said it's a program error that could be corrected by implementing the relevant SAP Notes), but going through that post didn't help solving my issue (Neither of the SAP Notes could be implemented in our system). Our IS-U component version is SAP ECC 6.0 EHP 5 (IS-UT 605). I found SAP Note 1603632 which is supposed to correct this issue in IS-UT 605. However, after implementing the error still persists.

Do you know of any other setting that has to be configured in order to get rid of the error message?

Thank you,

Balazs