How to use FSH_DC_CT_COND_TYPE - Gérer types de conditions

SAP Transaction Code - Details

• Transaction Code: FSH_DC_CT_COND_TYPE

  Description: Gérer types de conditions

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: FSH_DPR

    Package Description: Distribution Profile for Fashion

    Parent Package: FSH_CROSS_FUNCTIONS

  • Module/Component: LO-RFM

    Description: Retail & Fashion Management in S/4HANA

Smart SAP Assistant

• SAP Tcode: FSH_DC_CT_COND_TYPE - Gérer types de conditions

  
  Overview:
  The SAP transaction code FSH_DC_CT_COND_TYPE is used to maintain condition types in the SAP system. It is used to define the different types of conditions that can be used in pricing and billing documents. This transaction code is part of the SAP Financial Supply Chain Management (FSCM) module. 
  
  Functionality: 
  The FSH_DC_CT_COND_TYPE transaction code allows users to create, change, and delete condition types in the SAP system. It also allows users to define the characteristics of each condition type, such as the condition category, calculation type, and currency. Additionally, users can assign a condition type to a pricing procedure or billing document type. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code FSH_DC_CT_COND_TYPE into the command field. 
  2. Select “Create” from the menu bar to create a new condition type. 
  3. Enter the required information for the new condition type, such as the condition category, calculation type, and currency. 
  4. Select “Save” to save the new condition type. 
  5. Select “Assign” from the menu bar to assign a condition type to a pricing procedure or billing document type. 
  6. Select “Save” to save your changes. 
  
  Other Recommendations: 
  It is important to note that when creating or changing a condition type, users should ensure that all of the required information is entered correctly and completely. Additionally, users should be aware that changes made to a condition type may affect other areas of the system, such as pricing and billing documents. Therefore, it is important to test any changes before they are implemented in production systems.