How to use EQ10 - Selección de campos superficie (IMG)

SAP Transaction Code - Details

• Transaction Code: EQ10

  Description: Selección de campos superficie (IMG)

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: EE80

    Package Description: IS-U: Customizing

    Parent Package: IS-U/CCS

  • Module/Component: IS-U

    Description: SAP Utilities

Smart SAP Assistant

• SAP Tcode: EQ10 - Selección de campos superficie (IMG)

  
  Overview: 
  The SAP transaction code EQ10 is used to define the field selection for property in the IMG (Implementation Guide). This transaction code is used to define the fields that are available for selection when creating a property in the system. 
  
  Functionality: 
  The EQ10 transaction code allows users to define which fields are available for selection when creating a property in the system. This includes defining which fields are mandatory, optional, or hidden. It also allows users to define which fields are visible in the search help and which fields are used for sorting and filtering. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code EQ10 into the command field. 
  2. Select the “Field Selection” tab. 
  3. Select the “Property” option from the drop-down menu. 
  4. Select the “Fields” tab and select the fields that you want to be available for selection when creating a property in the system. 
  5. Select the “Attributes” tab and define which fields are mandatory, optional, or hidden. 
  6. Select the “Search Help” tab and define which fields are visible in the search help. 
  7. Select the “Sorting/Filtering” tab and define which fields are used for sorting and filtering. 
  8. Save your changes by selecting “Save” from the menu bar at the top of the screen. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the options available in this transaction code before making any changes to ensure that they understand how each option works and how it will affect their system. Additionally, it is recommended that users test any changes they make before implementing them in their production system to ensure that they do not cause any unexpected issues or errors.