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: 

Error in EA19 "Incorrect leading sign for statistical tax after difference clearing"

Former Member
0 Kudos

Hi,

While raising the Invoice using transaction EA19, I am getting the following error "Incorrect leading sign for statistical tax after difference clearing".

Can anybody help me out of this?

I am trying to generate an invoice in the context of the aggregated billing to generate an entry in the table DFKKTHI.

1 ACCEPTED SOLUTION

AmlanBanerjee
Active Contributor
0 Kudos

Hi Sinda,

There are quite a few notes released by SAP which discuss the error that you have mentioned.

Can you check SAP Note 2111559,2045399 and 2302019 for the same.

Thanks,
Amlan

View solution in original post

3 REPLIES 3

AmlanBanerjee
Active Contributor
0 Kudos

Hi Sinda,

There are quite a few notes released by SAP which discuss the error that you have mentioned.

Can you check SAP Note 2111559,2045399 and 2302019 for the same.

Thanks,
Amlan

0 Kudos

Hi Amlan ,

Thank you for your reply.

I tried to correct the error. I suppose it's an error in the sub and main transactions.

In fact, I have set them in SPRO after I have maintained them in EK72 transaction.

When I try to run again EA19, I am getting the following dump.


two identical records in table DFKKTHI.

have you an idea about this error ?

0 Kudos

Hi Sinda,

The data duplication exception that you are getting is quite common in nature, and can get triggered from multiple reasons.

As far my knowledge goes, for Aggregated invoicing posting scenario, the first step is when you are invoicing through EA19/EASIBI, it creates an entry in DFKKTHI table, where in I think you are getting the error.

I guess you have maintained the Main Tr 4500 and Sub 0010/0020 correctly.

Check SAP note 2086427 to see if it solves your issue.


The last resort would be to debug to see how duplicate records are getting inserted into DFKKTHI

Thanks,

Amlan