0% Tax Code Users: Beware of a Surprise Consequence to Long-Term Database Cost!
- by Kurt Goldsmith, Senior Business Consultant, Enowa Consulting
- March 15, 2004
Disk space availability is a concern for every business. It is possible that your company's tax calculation functionality, even if you use a zero percent tax code, is slowing down your system. The author explains how a little-known table may be to blame for your company's lack of disk space.
Once your site has been live on R/3 for a few years, disk space availability might start to be a concern. Reports take longer to run. Navigational pauses from screen to screen become visible. Even the act of saving your data entry documents seems noticeably slower. Of course, the accounting department gets the blame. (Everything is somehow deemed our fault!)
This time, though, it's really true. Of the thousands and thousands of individual database tables in the system, most of the "top 10" in terms of disk space consumption belong to FI or CO, such as table BSEG (FI line items), table COEP (CO line items), and … what is this … table BSET (tax line items)?
When readers of the FI/CO Expert newsletter think of their R/3 system-generated purchase orders and vendor invoices, it is not likely that they are also wondering if the tax calculation functionality in those transactions has a relationship to overall system performance and database size growth. This is because purchase orders from one business to a vendor might not require any tax to be calculated or collected (especially in the United States).
As most of us know, the R/3 processing side of vendor A/Ps recorded via the Purchasing module's invoice verification must include a tax code — not necessarily a tax, just a tax code. The workaround for non-taxable purchases is to go with a zero percent tax code. Typical examples in the standard system are E0 and I0. Okay, get ready for a surprise!
Would you like to see this full item?