SAP EXIT_SAPLN1PLANT_USF Function Module for IS-H*MED: Planning Grid: Function Calls in User-Specific GUI Statuses
EXIT_SAPLN1PLANT_USF is a standard exit sapln1plant usf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H*MED: Planning Grid: Function Calls in User-Specific GUI Statuses 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 exit sapln1plant usf FM, simply by entering the name EXIT_SAPLN1PLANT_USF into the relevant SAP transaction such as SE37 or SE38.
Function Group: XN1USERSEXITSGUI
Program Name: SAPLXN1USERSEXITSGUI
Main Program: SAPLXN1USERSEXITSGUI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLN1PLANT_USF 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 'EXIT_SAPLN1PLANT_USF'"IS-H*MED: Planning Grid: Function Calls in User-Specific GUI Statuses.
EXPORTING
I_UCOMM = "Triggered Function Code
I_ORGID = "Planning Organizational Unit
I_MODE = "Display of Multi-Scheduling Control of Planning Grid
I_REGCARD = "Active Tab Page (Either Org. Unit or Date according to Value of i_mode)
CHANGING
* C_ERRORHANDLER = "IS-H*MED: Class for Error Handling
TABLES
* T_NLEI = "Services
* T_NLEM = "Services, Med.
* T_NTMN = "Appointments
* T_NAPP = "Resource Commitments
* T_NPAT = "Patients for the First and Follow-Up Visit
* T_N1USEGUI_PLANT = "Planning Objects
* T_DATA_PRV = "Unsaved Data
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISHMED_CALL_SAPLN1PLANT_USF
ISHMED_POB_TIMESLOTS_READ
IMPORTING Parameters details for EXIT_SAPLN1PLANT_USF
I_UCOMM - Triggered Function Code
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
I_ORGID - Planning Organizational Unit
Data type: NORG-ORGIDOptional: No
Call by Reference: Yes
I_MODE - Display of Multi-Scheduling Control of Planning Grid
Data type: IOptional: No
Call by Reference: Yes
I_REGCARD - Active Tab Page (Either Org. Unit or Date according to Value of i_mode)
Data type: COptional: No
Call by Reference: Yes
CHANGING Parameters details for EXIT_SAPLN1PLANT_USF
C_ERRORHANDLER - IS-H*MED: Class for Error Handling
Data type: CL_ISHMED_ERRORHANDLINGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLN1PLANT_USF
T_NLEI - Services
Data type: ISHMED_NLEIOptional: Yes
Call by Reference: Yes
T_NLEM - Services, Med.
Data type: ISHMED_T_NLEMOptional: Yes
Call by Reference: Yes
T_NTMN - Appointments
Data type: ISHMED_T_NTMNOptional: Yes
Call by Reference: Yes
T_NAPP - Resource Commitments
Data type: ISHMED_T_NAPPOptional: Yes
Call by Reference: Yes
T_NPAT - Patients for the First and Follow-Up Visit
Data type: ISHMED_T_NPATOptional: Yes
Call by Reference: Yes
T_N1USEGUI_PLANT - Planning Objects
Data type: ISHMED_T_N1USEGUI_PLANTOptional: Yes
Call by Reference: Yes
T_DATA_PRV - Unsaved Data
Data type: ISH_OBJECTLISTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLN1PLANT_USF 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: | ||||
| lt_t_nlei | TYPE STANDARD TABLE OF ISHMED_NLEI, " | |||
| lv_i_ucomm | TYPE SY-UCOMM, " | |||
| lv_c_errorhandler | TYPE CL_ISHMED_ERRORHANDLING, " | |||
| lt_t_nlem | TYPE STANDARD TABLE OF ISHMED_T_NLEM, " | |||
| lv_i_orgid | TYPE NORG-ORGID, " | |||
| lv_i_mode | TYPE I, " | |||
| lt_t_ntmn | TYPE STANDARD TABLE OF ISHMED_T_NTMN, " | |||
| lt_t_napp | TYPE STANDARD TABLE OF ISHMED_T_NAPP, " | |||
| lv_i_regcard | TYPE C, " | |||
| lt_t_npat | TYPE STANDARD TABLE OF ISHMED_T_NPAT, " | |||
| lt_t_n1usegui_plant | TYPE STANDARD TABLE OF ISHMED_T_N1USEGUI_PLANT, " | |||
| lt_t_data_prv | TYPE STANDARD TABLE OF ISH_OBJECTLIST. " |
|   CALL FUNCTION 'EXIT_SAPLN1PLANT_USF' "IS-H*MED: Planning Grid: Function Calls in User-Specific GUI Statuses |
| EXPORTING | ||
| I_UCOMM | = lv_i_ucomm | |
| I_ORGID | = lv_i_orgid | |
| I_MODE | = lv_i_mode | |
| I_REGCARD | = lv_i_regcard | |
| CHANGING | ||
| C_ERRORHANDLER | = lv_c_errorhandler | |
| TABLES | ||
| T_NLEI | = lt_t_nlei | |
| T_NLEM | = lt_t_nlem | |
| T_NTMN | = lt_t_ntmn | |
| T_NAPP | = lt_t_napp | |
| T_NPAT | = lt_t_npat | |
| T_N1USEGUI_PLANT | = lt_t_n1usegui_plant | |
| T_DATA_PRV | = lt_t_data_prv | |
| . " EXIT_SAPLN1PLANT_USF | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLN1PLANT_USF
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 UCOMM FROM SY INTO @DATA(ld_i_ucomm). | ||||
| "SELECT single ORGID FROM NORG INTO @DATA(ld_i_orgid). | ||||
Search for further information about these or an SAP related objects