SAP H99L_F4_EXIT_ORGCODE Function Module for F4 Help for org. grouping
H99L_F4_EXIT_ORGCODE is a standard h99l f4 exit orgcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for F4 Help for org. grouping 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 h99l f4 exit orgcode FM, simply by entering the name H99L_F4_EXIT_ORGCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HR99L00_DISMPROT
Program Name: SAPLHR99L00_DISMPROT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function H99L_F4_EXIT_ORGCODE 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 'H99L_F4_EXIT_ORGCODE'"F4 Help for org. grouping.
EXPORTING
MOLGA = "Country Grouping
DISPLAY = "Single-character flag
CHANGING
ORGCO = "Org. Code
IMPORTING Parameters details for H99L_F4_EXIT_ORGCODE
MOLGA - Country Grouping
Data type: MOLGAOptional: No
Call by Reference: Yes
DISPLAY - Single-character flag
Data type: CHAR1Optional: No
Call by Reference: Yes
CHANGING Parameters details for H99L_F4_EXIT_ORGCODE
ORGCO - Org. Code
Data type: T799L06-ORGCOOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for H99L_F4_EXIT_ORGCODE 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_molga | TYPE MOLGA, " | |||
| lv_orgco | TYPE T799L06-ORGCO, " | |||
| lv_display | TYPE CHAR1. " |
|   CALL FUNCTION 'H99L_F4_EXIT_ORGCODE' "F4 Help for org. grouping |
| EXPORTING | ||
| MOLGA | = lv_molga | |
| DISPLAY | = lv_display | |
| CHANGING | ||
| ORGCO | = lv_orgco | |
| . " H99L_F4_EXIT_ORGCODE | ||
ABAP code using 7.40 inline data declarations to call FM H99L_F4_EXIT_ORGCODE
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 ORGCO FROM T799L06 INTO @DATA(ld_orgco). | ||||
Search for further information about these or an SAP related objects