SAP ABAP IMG Activity OHARUMDPA_IT0011_002 (Hide or view Infotype Screen Control)
Hierarchy
☛ SAP_HRCRU (Software Component) Sub component SAP_HRCRU of SAP_HR
   ⤷ PY-RU (Application Component) Russia
     ⤷ P33C (Package) HR Customizing: Russia
IMG Activity
ID OHARUMDPA_IT0011_002 Hide or view Infotype Screen Control  
Transaction Code S_AC0_52000278   (empty) 
Created on 20041211    
Customizing Attributes OHARUMD   Check Seniority 
Customizing Activity OHIRUMDPA_IT0004_001   View for Infotype Screen Control 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHIX0636    

Different entry screens are delivered for some infotypes. Depending on the transaction class ("A" for employee, "B" for applicant) or the country grouping, a different screen can be used.
In addition to this, you can also change the characteristics of the individual screen fields: For example, you can define fields as required-entry fields or suppress any fields that are not required.
You may want to suppress field attributes in accordance with certain employee control data.

Example

  • You want to suppress the field Foreman's area in the infotype Organizational assignment (0001) and make the field Administrator HR master data into a required-entry field.

Requirements

In the view "Screen assignment", a single screen and a list layout is assigned to every infotype.

Standard settings

These alternative screens are already preset by SAP depending on
transaction class and country grouping.

Activities

  • Screen modification is identical for all employees or all applicants.
    • Find the entry for the current screen. If necessary, create a new entry for the screen. The variable key must be empty when you do this.
    • On the detail screen, determine which fields are to be modified.
  • Screen modification depends on the organizational assignment of the employee or on the infotype's subtype.
    • Find the entry for the current screen. If necessary, create a new entry for the screen. The variable key must always be empty for the first entry when you do this - this is the basic entry.
    • Assign the name of a feature. The naming convention is "Pnnnn", where "nnnn" is the number of the infotype.
    • Maintain the feature.
      Use the structure "PME04", all fields are allowed.
    • Make a new entry per return value of the feature. By doing this, you include the return value in the variable key.
    • Assign the number of an alternative screen, if applicable.
    • Determine the screen modification on the detail screen.
    • If you do not enter a return value of the feature, the entry for which the variable key is empty, i.e. the basic entry, is valid.
  • An alternative screen should be used.
    • Determine a basic entry as above and predefine the feature Pnnnn.
    • Determine the variable key by using the feature and in accordance with the transaction class, country grouping etc..
    • Make a new entry for the variable key.
    • Assign the number of the alternative screen.
    • The screen modification in the detail screen now applies to the alternative screen.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHIX0636 0 HLA0100326 O HLA0009705  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_T588M V - View SM30  
History
Last changed by/on SAP  20041211 
SAP Release Created in 600