Page tree
Skip to end of metadata
Go to start of metadata

Purpose

This document provides information on how the tax code is being determined for settlement document items in Condition Contract Settlement (CCS) scenarios and aims to provide help with the configuration to avoid tax code-related errors (e.g. WS533) in the settlement program.

Overview

In CCS scenarios, where the settlement document is created in the background in most of the cases  (by executing WB2R_SC or WB2R_SV transactions), the tax codes are not entered manually but determined automatically by the Pricing program. 

For this automatic determination, the Pricing program tries to search for a tax code for the tax condition type from the calculation schema of the settlement document.

Depending on whether you have a customer/supplier-sided settlement, it has to be ensured that the Pricing program can find a valid condition record for the tax condition type, and is able to determine a tax code from it. For commission settlement, the supplier-sided data is used for the tax code determination. Below you can find an overview of the relevant customizing and configuration prerequisites.


Customizing prerequisites from Pricing side

First of all, the tax condition type has to be customized correctly on the Pricing side:
  1. For example if you have a customer-sided settlement*, you need to ensure that the calculation schema (which is used for the settlement and which can be checked in customizing transaction V/08) contains a condition type, which can be used for tax calculation (condition category has to be "D - Taxes" for the condition type).
  2. In the customizing settings of this tax condition type (in customizing transaction V/06), an access sequence has to be assigned, which can be used by the system to search for condition records. 
  3. Finally, in the access sequence, that (those) access(es) must be maintained, which would be used for the condition record search. 

*the mentioned customizing transactions can be accessed on the Purchasing side as well, by using transaction codes M/08, M/06, and M/07.

Customizing prerequisites from CCS side

In the customizing settings of the tax condition type (which is used inside the calculation schema), for simplification purposes, you have the opportunity to use a reference condition type. As a reference, you can check tax condition type RETX (which was delivered by SAP as part of the standard customizing in S/4HANA) and which has reference condition type MWST maintained in it.

The tax determination logic (and the relevant customizing settings) depends on whether there was a reference condition type assigned to the tax condition type, or not.

If a reference condition type was NOT maintained for the tax condition type

The system will search a condition record for the tax condition type, which is valid on the posting date of the settlement. Therefore it has to be ensured that based on one of the accesses, the system can find a condition record, which contains a tax code for the tax condition type, that can be passed by Pricing to the settlement program.

This means, that during the settlement, the program will only be able to determine a tax code for the settlement document item if the condition record is valid on the posting date of the settlement and the KOMK/KOMP data matches with the data from your settlement document. 

If necessary, please check and/or adjust the condition record data of the relevant tax condition type. Please refer to the "Additional information" section of this document for the relevant transaction codes.

If a reference condition type was maintained for the tax condition type

The system will search a condition record for the tax condition type, which is valid on the posting date of the settlement. But during the condition record search, the system will search for a condition record, which is valid for the reference condition type. Moreover, during the condition record search, only those accesses will be used by the system, which the access sequences of the tax condition type and the reference condition type have in common.

Therefore it has to be ensured that based on one of the accesses, the system can find a condition record for the reference condition type, which contains a tax code for the reference condition type, that can be passed by Pricing to the settlement program. For this, you have to make sure, that the KOMK/KOMP data matches with the data from your settlement document.


An example from the standard delivered customizing in S/4HANA, for tax condition type RETX (for which access sequence RET1 is used) on the sales side:
Tax condition type RETX has reference condition type MWST and has access sequence RET1 assigned to it. In the standard customizing, for condition type MWST, access sequence MWST is assigned. The two access sequences (RET1 and MWST) have one access in common, called Domestic taxes, which contain the following access fields:

 

KOMP/KOMK field nameField description
KOMK-ALANDDeparture Country
KOMK-TAXK1Tax Classification 1-Customer
KOMP-TAXM1Tax Classification Material

Based on the above settings, during a sales-sided settlement, the program will only be able to determine a tax code for the settlement document item, if a condition record was maintained for the reference condition type. The condition record has to be valid on the posting date of the settlement and the Departure country, tax classification data have to match with the settlement document header data, moreover, the tax classification material data also has to be the same as the one on item level of the settlement document.

If necessary, please check and/or adjust the condition record data of the relevant tax condition type. Please refer to the "Additional information" section of this document for the relevant transaction codes.

Additional information

For the creation/change/display of condition records the following transaction codes can be used:

  • on the sales side: VK11/VK12/VK13
  • on the purchase side: MEK1/MEK2/MEK3
  • No labels