How to use OCMAC06 - Define Condition Types

SAP Transaction Code - Details

• Transaction Code: OCMAC06

  Description: Define Condition Types

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: CMAC_E

    Package Description: Campus Management: Student Account

    Parent Package: PMIQ_MAIN_CORE

  • Module/Component: IS-HER-CM-AC

    Description: Student Accounting

Smart SAP Assistant

• SAP Tcode: OCMAC06 - Define Condition Types

  
  Overview:
  The SAP transaction code OCMAC06 is used to define condition types in the SAP system. It is used to create and maintain condition types for pricing, discounts, taxes, and other calculations. This transaction code is part of the SAP Pricing and Conditions module. 
  
  Functionality: 
  The OCMAC06 transaction code allows users to define condition types for pricing, discounts, taxes, and other calculations. It also allows users to assign a condition type to a pricing procedure and assign a calculation type to the condition type. Additionally, it allows users to define the access sequence for the condition type and assign a condition table to the access sequence. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code OCMAC06 in the command field. 
  2. Enter the name of the condition type you want to create or maintain in the Condition Type field. 
  3. Enter a description of the condition type in the Description field. 
  4. Select a calculation type from the drop-down menu in the Calculation Type field. 
  5. Select an access sequence from the drop-down menu in the Access Sequence field. 
  6. Select a condition table from the drop-down menu in the Condition Table field. 
  7. Click on Save to save your changes or click on Back to go back without saving your changes. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with SAP Pricing and Conditions module before using this transaction code as it requires knowledge of pricing procedures, access sequences, and condition tables in order to use it effectively. Additionally, users should always make sure that they have saved their changes before exiting out of this transaction code as any unsaved changes will be lost when they exit out of it.