How to use CX1XN - Edit Cons Group Hierarchies

SAP Transaction Code - Details

• Transaction Code: CX1XN

  Description: Edit Cons Group Hierarchies

  Release: S/4HANA and ECC 6

• • Program: SAPMF21B

    Screen: 100

    Authorization Object: E_CS_DIMEN

  • Development Package: FC00

    Package Description: Cons: General consolidation (cannot be assign.to FC01-FC09)

    Parent Package: APPL

  • Module/Component: EC-CS

    Description: Consolidation

Smart SAP Assistant

• SAP Tcode: CX1XN - Edit Cons Group Hierarchies

  
  Overview:
  The SAP transaction code CX1XN is used to edit the hierarchies of a consumption group. This transaction code allows users to create, change, and delete the hierarchies of a consumption group. It also allows users to assign a consumption group to a cost center or cost object. 
  
  Functionality: 
  The CX1XN transaction code is used to maintain the hierarchies of a consumption group. It allows users to create, change, and delete the hierarchies of a consumption group. It also allows users to assign a consumption group to a cost center or cost object. The hierarchies are used to determine the cost allocation for the consumption group. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code CX1XN in the command field. 
  2. Select the “Create” option from the menu bar. 
  3. Enter the name of the consumption group you want to create or edit in the “Consumption Group” field. 
  4. Enter the name of the hierarchy you want to create or edit in the “Hierarchy” field. 
  5. Enter the name of the cost center or cost object you want to assign to this hierarchy in the “Cost Center/Object” field. 
  6. Select “Save” from the menu bar to save your changes. 
  7. Select “Back” from the menu bar to return to the main screen. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the options available in this transaction code before making any changes or creating any new hierarchies. Additionally, it is important that users ensure that all changes are properly saved before exiting out of this transaction code as any unsaved changes will be lost when exiting out of this transaction code.