‎2007 May 24 3:23 PM
Hi Friends,
I have a problem with working one of the BDC sessions for Pcard.
Error: Maximum permitted number of internal tax items reached
Message class is <b>FF</b>
Message Number is <b>755</b>
When I checked the documentation of the message it say
<b>
Short Text
Maximum permitted number of internal tax items reached
Diagnosis
The maximum number of internal tax items is limited to 999. More than 999 internal tax items were generated during the current posting.
System Response
The posting is rejected.
Procedure
Enter fewer G/L account items or do without an item by item tax determination.
</b>
Is there any possibility that I can increase this limit.
Please suggest me what to do.
Thanks,
Saya
‎2007 May 24 3:30 PM
Hi Saya,
I have faced the same problem once. There is no way that you can increase the max number of internal tax items to more than 999. Instead you can send the batch input in multiples of 449.
Hope this solves your problem.
Reward if useful.
Thanks
Aneesh.
‎2007 May 24 3:30 PM
No you cannot increase this limit as this ultimately translates to a line number in BSEG-BUZEI which is limited to 3 digits which means 999.
You will have to split your transaction items at 950 or so and create the documents. You will have to keep track of the total amount for the document and use that in the next document to make the net total of the two documents is 0. You have to do this every time you work with accounting documents.
‎2008 Feb 12 7:11 PM
SAP has a limit of 999 BSET lines for an FI document.
With Taxware, each line taxable item on an FI document (BSEG line) can produce up to 6 lines in BSET (one for each level of tax; state, county, city, etc).
If your PO has 344 tax relevant lines, each line produces a number of tax lines (lets say it produces 3 lines each for state, city and county taxes). Thats 344 * 3 = 1032 BSET lines, which is greater than the 999 line maximum that SAP allows. So basically, the more levels of tax you have for a particular jurisdiction, the fewer PO/FI lines you can enter on a PO. In this case, the only thing you can do, is to split the PO, so that you stay below that maximum.