How to use S_AHR_61010636 - IMG Activity: OHTY048

SAP Transaction Code - Details

• Transaction Code: S_AHR_61010636

  Description: IMG Activity: OHTY048

  Release: S/4HANA and ECC 6

• • Program: SAPLS_CUS_IMG_ACTIVITY

    Screen: 200

    Authorization Object:

  • Development Package: PTIC

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: S_AHR_61010636 - IMG Activity: OHTY048

  
  Overview:
  S_AHR_61010636 - IMG Activity OHTY048 is a SAP transaction code used to maintain the settings for the Personnel Development (PD) infotype (IT048). This transaction code is used to define the settings for the PD infotype, such as the number of fields, field labels, and field lengths. 
  
  Functionality: 
  The S_AHR_61010636 - IMG Activity OHTY048 transaction code is used to maintain the settings for the Personnel Development (PD) infotype (IT048). This transaction code allows users to define the number of fields, field labels, and field lengths for the PD infotype. It also allows users to define which fields are mandatory and which are optional. Additionally, users can define which fields are visible in the PD infotype and which are hidden. 
  
  Step-by-step How to Use: 
  1. Enter transaction code S_AHR_61010636 - IMG Activity OHTY048 in the command field. 
  2. Select “Maintain Settings” from the menu. 
  3. Select “Fields” from the menu. 
  4. Select a field from the list of available fields and click “Edit”. 
  5. Enter a label for the field and select whether it is mandatory or optional. 
  6. Select whether it should be visible or hidden in the PD infotype. 
  7. Click “Save” to save your changes. 
  8. Repeat steps 4-7 for each field you wish to edit or add. 
  9. Click “Save” when you have finished making changes to save them permanently. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the available fields before making any changes to ensure that they are making changes that are appropriate for their organization's needs. Additionally, users should always test their changes in a test environment before implementing them in a production environment to ensure that they do not cause any unexpected issues or errors.