SAP EXIT_SAPLN1ON_008 Function Module for IS-H*MED: Planning List & OR Schedule - Menu Exit 3









EXIT_SAPLN1ON_008 is a standard exit sapln1on 008 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 List & OR Schedule - Menu Exit 3 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 sapln1on 008 FM, simply by entering the name EXIT_SAPLN1ON_008 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XN1Q
Program Name: SAPLXN1Q
Main Program: SAPLXN1Q
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPLN1ON_008 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_SAPLN1ON_008'"IS-H*MED: Planning List & OR Schedule - Menu Exit 3
EXPORTING
I_LIST_KZ = "List-IND (P=Planning List, O=OR Schedule)

IMPORTING
E_LIST_UPD = "Should Planning List or OR Schedule be updated?

TABLES
T_PLAN = "Data for the Planning List or OR Schedule
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISHMED_CHECK_OP_BEGONNEN
ISHMED_GET_ANKER_LSSTA
ISHMED_NBEW_CHECK_OP_TYPE
ISHMED_OP_PROGRAMM
ISHMED_OP_STORNO
ISHMED_PLAN_LIST
ISHMED_POPUP_DATUM_GPART
ISHMED_POPUP_TO_DECIDE
ISHMED_SET_OP_BEGONNEN
ISHMED_STORNO_OPZEITEN

IMPORTING Parameters details for EXIT_SAPLN1ON_008

I_LIST_KZ - List-IND (P=Planning List, O=OR Schedule)

Data type: N1FLD-N1LISTE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EXIT_SAPLN1ON_008

E_LIST_UPD - Should Planning List or OR Schedule be updated?

Data type: RN200-MARK
Optional: No
Call by Reference: Yes

TABLES Parameters details for EXIT_SAPLN1ON_008

T_PLAN - Data for the Planning List or OR Schedule

Data type: RN1PLAN
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EXIT_SAPLN1ON_008 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_plan  TYPE STANDARD TABLE OF RN1PLAN, "   
lv_i_list_kz  TYPE N1FLD-N1LISTE, "   
lv_e_list_upd  TYPE RN200-MARK. "   

  CALL FUNCTION 'EXIT_SAPLN1ON_008'  "IS-H*MED: Planning List & OR Schedule - Menu Exit 3
    EXPORTING
         I_LIST_KZ = lv_i_list_kz
    IMPORTING
         E_LIST_UPD = lv_e_list_upd
    TABLES
         T_PLAN = lt_t_plan
. " EXIT_SAPLN1ON_008




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLN1ON_008

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 N1LISTE FROM N1FLD INTO @DATA(ld_i_list_kz).
 
"SELECT single MARK FROM RN200 INTO @DATA(ld_e_list_upd).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!