Getting FF891 Error in MIRO

[Former Member]

Hi all,

We are getting the error message "Gl/L account item without tax code in document $1 with deferred taxes"

but just in PRD, in QAS all is working fine. We tried to implement the SAP NOTE 1058620,

but it cannot be implemented throught SNOTE transaction. Do you think is a good idea to implement the

code of the corrections directly? or do you know how can we solve the issue?

Thanks in advance.

[Former Member]

Hi all,

We are getting the error message "Gl/L account item without tax code in document $1 with deferred taxes"

but just in PRD, in QAS all is working fine. We tried to implement the SAP NOTE 1058620,

but it cannot be implemented throught SNOTE transaction. Do you think is a good idea to implement the

code of the corrections directly? or do you know how can we solve the issue?

Thanks in advance.

[Former Member]

Why can you not implement the note using SNOTE. What message do you get.

And what version of R/3 are you on?

Rob

[Former Member]

I don't know what was the message showed,

the BASIS team just said it couldn't be implemented.

The version is SAP ECC 6.0.

[Former Member]

Well, you have to find out what the problem was. It could be that it is already implemented, in which case, you don't want to implement it. Or it may be that because there are manual steps SNOTE cannot implement it. In that case, it has to be done manually.

Rob

[Former Member]

Having said that, if you are above support pack 10, then it should already be implemented.

Rob

[Former Member]

Hi,

I think that the NOTE doesnt have to be implemented, because in QAS is working fine...I guess that you wont have different updates in QAS and PRD...

It must be sth about the tax account...check with a FI consultant.

Regards

[Former Member]

Yes - check the support pack level in both systems. QA may be at a higher level.

Rob

[Former Member]

I checked both systems and have the same level in all components.

Here it is the list:

Software Component	Release	Level	Highest support package	Short description of software component
SAP_ABA	700	15	SAPKA70015	Cross-Application Component
SAP_BASIS	700	15	SAPKB70015	SAP Basis Component
ST-PI	2005_1_700	5	SAPKITLQI5	SAP Solution Tools Plug-In
PI_BASIS	2005_1_700	15	SAPKIPYJ7F	PI_BASIS 2005_1_700
SAP_BW	700	17	SAPKW70017	SAP NetWeaver BI 7.0
SAP_AP	700	12	SAPKNA7012	SAP Application Platform
SAP_HR	600	28	SAPKE60028	Human Resources
SAP_APPL	603	2	SAPKH60302	Logistics and Accounting
EA-IPPE	400	13	SAPKGPID13	SAP iPPE
EA-APPL	603	2	SAPK-60302INEAAPPL	SAP Enterprise Extension PLM, SCM, Finan
EA-DFPS	603	2	SAPK-60302INEADFPS	SAP Enterprise Extension Defense Forces
EA-FINSERV	603	2	SAPK-60302INEAFINSRV	SAP Enterprise Extension Financial Servi
EA-GLTRADE	603	2	SAPK-60302INEAGLTRAD	SAP Enterprise Extension Global Trade
EA-HR	603	2	SAPK-60302INEAHR	SAP Enterprise Extension HR
EA-PS	603	2	SAPK-60302INEAPS	SAP Enterprise Extension Public Services
EA-RETAIL	603	2	SAPK-60302INEARETAIL	SAP Enterprise Extension Retail
FINBASIS	603	2	SAPK-60302INFINBASIS	FINBASIS 603
ECC-DIMP	603	2	SAPK-60302INECCDIMP	DIMP
ERECRUIT	603	2	SAPK-60302INERECRUIT	ERECRUIT 603
FI-CA	603	2	SAPK-60302INFICA	FI-CA
FI-CAX	603	2	SAPK-60302INFICAX	FI-CA Extended
INSURANCE	603	2	SAPK-60302ININSURANC	SAP Insurance
IS-CWM	603	2	SAPK-60302INISCWM	Industry Solution Catch Weight Managemen
IS-H	603	2	SAPK-60302INISH	SAP Healthcare
IS-M	603	2	SAPK-60302INISM	SAP MEDIA
IS-OIL	603	2	SAPK-60302INISOIL	IS-OIL
IS-PS-CA	603	2	SAPK-60302INISPSCA	IS-PUBLIC SECTOR CONTRACT ACCOUNTING
IS-UT	603	2	SAPK-60302INISUT	SAP Utilities/Telecommunication
LSOFE	603	2	SAPK-60302INLSOFE	LSOFE
SEM-BW	603	2	SAPK-60302INSEMBW	SEM-BW 603
BP-INSTASS	600V4	0	-	Best Practices Installation Assistant ba
BP-ERP05	603V2	0	-	Best Practices for All-in-One based on E
BP-ERP05	603V2	0	-	Best Practices for All-in-One based on E

So the level is 15, right? I look at the code and the modifications have not been applied.

[Former Member]

Well, you appear to above that support level, so you cannot implement anything that has already been implemented. It may be time to raise an OSS message.

Rob