SAP ABAP IMG Activity HR_F4_GET_SUBTYPE (BAdI: Set Up Entry Help for Subtypes)
Hierarchy
☛ SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   ⤷ PA-PA (Application Component) Personnel Administration
     ⤷ PBAC (Package) Customizing HR Master Data
IMG Activity
ID HR_F4_GET_SUBTYPE BAdI: Set Up Entry Help for Subtypes  
Transaction Code S_PH0_48000290   (empty) 
Created on 20000120    
Customizing Attributes HR_F4_GET_SUBTYPE   HR: Entry Help for Subtypes 
Customizing Activity HR_F4_GET_SUBTYPE   HR: Entry Help for Subtypes 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HR_F4_GET_SUBTYPE    

Business Add-In (BAdI) Entry help for subtypes (HR_F4_GET_SUBTYPE) is used to implement the following functions in new or changed infotypes:

  • Possibility of an entry help for subtypes
  • Determining the name of a subtype

The BAdI has two methods:

  • Determine Tables for Entry Helps (GET_TAB_F4_HELP)
  • Determine Text for Subtype (GET_SUBTYPE_TEXT)

These methods are called in the following subtypes, to either create a list of subtypes of an infotype, or to determine the name of a specified subtype:
Determine Subtypes of Infotype (HR_F4_GET_SUBTYPE)
Define Subtype Tables of Infotype (HR_F4_GET_TABLES)
Determine Subtype Texts of Infotype (HR_GET_SUBTYPE_TEXT).

Infotype (parameter FLT_VAL) is used as a filter value, which is used to differentiate between the various implementations of BADIs. All other import parameters in the GET_SUBTYPE_TEXT method interface (excluding SUBTY) are only optional, and are used to determine or restrict the list of possible subtypes, or to determine the subtype exactly.

Example

You can find examples in the implementations HR_GET_SUBTYPE_T591A and HR_GET_SUBTYPE_T512Z.

Standard settings

If no BAdI implementation is available for an infotype, when one of the three function modules is called (Determining Subtypes of Infotype (HR_F4_GET_SUBTYPE), Define Subtype Tables of Infotype (HR_F4_GET_TABLES) and Determining Subtype Texts of Infotype (HR_GET_SUBTYPE_TEXT)), standard coding is run, as long as it is available for the corresponding subtype table. If it is not available, the infotype is classed as "not supported".

If standard coding and a BAdI implementation exists for one infotype, the standard coding is ignored, and the BAdI is processed.

Recommendation

We recommend that you use naming convention HR_GET_SUBTYPE_<xxxx> for your BAdI implementations of this type, where <xxxx> stands for the name of the corresponding subtype table (such as HR_GET_SUBTYPE_T591A).

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Further notes

Interface

Method: Determine Tables for Entry Helps

Method: Determine Subtype Texts

You can use the above examples as a basis for your implementations.

For more information on using Business Add-Ins, refer to the SAP Library under Basis Components ->ABAP Workbench (BC-DWB) ->Changing the SAP Standard (BC)->Business Add-Ins.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HR_F4_GET_SUBTYPE 0 HLA0100326 Tools 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20000128 
SAP Release Created in 46C