As of Release 4.6B, the Tax Per Document method is available. This method is important to allow Max Tax calculation rules across multiple items to be applied to an SD document. Tax Per Document is also important for performance reasons, because the RFC call to the external tax system occurs once for the entire document instead of numerous times for each line item.

To make full use of the Tax Per Document method, the correct configuration set up is required in SD.

The SAP standard delivered pricing procedure RVAXUD is used instead of RVAXUS.

In RVAXUD, the condition type UTXJ is replaced by 2 other condition types:

• UTXD - differs from UTXJ for being a group condition
• UTXE - differs from UTXJ for being a group condition and for having no access sequence

As condition type UTXD has UTXJ as reference condition type, there is no need to maintain condition records for UTXD. The UTXJ condition records is used for UTXD as well.

Since condition type UTXE does not have an access sequence, it is always active in the pricing procedure during SD document transactions.

Notice that UTXD has condition value formula 500 (instead of 300) and UTXE has condition value formula 510.

During condition value formula 500, all document items are collected and stored. After the tax relevant data is stored for all items, it is passed to the external tax system for tax calculation. External tax system can eventually execute Max Tax calculation rules across multiple items. The tax results from the external system are distributed back to the corresponding item through the condition value formula 510.

The condition value formulas 500 and 510 are able to operate accordingly because UTXD and UTXE are group conditions.