SAP J_3G_SEARCH_PERSONAL_IH Function Module for Determination of User per Equi./Partner Function
J_3G_SEARCH_PERSONAL_IH is a standard j 3g search personal ih SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determination of User per Equi./Partner Function processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for j 3g search personal ih FM, simply by entering the name J_3G_SEARCH_PERSONAL_IH into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3GB
Program Name: SAPLJ3GB
Main Program: SAPLJ3GB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_3G_SEARCH_PERSONAL_IH pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'J_3G_SEARCH_PERSONAL_IH'"Determination of User per Equi./Partner Function.
EXPORTING
I_EQUNR = "Equipment Number
I_PARVW = "Partner Function
* I_OBTYP = 'IEQ' "Object (Type and Equipment Number)
* I_NO_DIALOG = "X=No Dialog (for Several Partners)
IMPORTING
E_PARNR = "Partner/User/Operator
EXCEPTIONS
NO_PARTNER_EXIST = 1
IMPORTING Parameters details for J_3G_SEARCH_PERSONAL_IH
I_EQUNR - Equipment Number
Data type: J_3GBELP-EQUNROptional: No
Call by Reference: No ( called with pass by value option)
I_PARVW - Partner Function
Data type: IHPA-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
I_OBTYP - Object (Type and Equipment Number)
Data type: IHPA-OBTYPDefault: 'IEQ'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_DIALOG - X=No Dialog (for Several Partners)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_3G_SEARCH_PERSONAL_IH
E_PARNR - Partner/User/Operator
Data type: J_3GPERNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_PARTNER_EXIST - No Partner Exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_3G_SEARCH_PERSONAL_IH Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_e_parnr | TYPE J_3GPERNR, " | |||
| lv_i_equnr | TYPE J_3GBELP-EQUNR, " | |||
| lv_no_partner_exist | TYPE J_3GBELP, " | |||
| lv_i_parvw | TYPE IHPA-PARVW, " | |||
| lv_i_obtyp | TYPE IHPA-OBTYP, " 'IEQ' | |||
| lv_i_no_dialog | TYPE IHPA. " |
|   CALL FUNCTION 'J_3G_SEARCH_PERSONAL_IH' "Determination of User per Equi./Partner Function |
| EXPORTING | ||
| I_EQUNR | = lv_i_equnr | |
| I_PARVW | = lv_i_parvw | |
| I_OBTYP | = lv_i_obtyp | |
| I_NO_DIALOG | = lv_i_no_dialog | |
| IMPORTING | ||
| E_PARNR | = lv_e_parnr | |
| EXCEPTIONS | ||
| NO_PARTNER_EXIST = 1 | ||
| . " J_3G_SEARCH_PERSONAL_IH | ||
ABAP code using 7.40 inline data declarations to call FM J_3G_SEARCH_PERSONAL_IH
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single EQUNR FROM J_3GBELP INTO @DATA(ld_i_equnr). | ||||
| "SELECT single PARVW FROM IHPA INTO @DATA(ld_i_parvw). | ||||
| "SELECT single OBTYP FROM IHPA INTO @DATA(ld_i_obtyp). | ||||
| DATA(ld_i_obtyp) | = 'IEQ'. | |||
Search for further information about these or an SAP related objects