SAP ISH_WP_VIEW_SPLITT Function Module for
ISH_WP_VIEW_SPLITT is a standard ish wp view splitt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish wp view splitt FM, simply by entering the name ISH_WP_VIEW_SPLITT into the relevant SAP transaction such as SE37 or SE38.
Function Group: N_WP
Program Name: SAPLN_WP
Main Program: SAPLN_WP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_WP_VIEW_SPLITT 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 'ISH_WP_VIEW_SPLITT'".
EXPORTING
* I_WPLACETYPE1 = '001' "Type of the Work Environment
I_WPLACEID1 = "
I_VIEWTYPE1 = "
I_VIEWID1 = "
I_USER = "User Name
* I_MODE = 'R' "
* IR_SPLITTER_CONT = "
CHANGING
* C_WPLACETYPE2 = '001' "
* C_WPLACEID2 = "
* C_VIEWTYPE2 = "
* C_VIEWID2 = "
* C_SASH_POS = "
EXCEPTIONS
VIEW_NOT_SPLITTED = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLN1WP_001 IS-H*MED: User Exit Medical Unit List - Display Fields
EXIT_SAPLN1WP_002 IS-H*MED: User Exit Medical Unit List Fields - Functions
EXIT_SAPLN2WP006_001 IS-H*MED: User Exit Functions f. Clin.Work Station - View Type - Documents
EXIT_SAPLN2WP006_002 IS-H*MED: User-Exit Display fór Clin. Work Station - View Type Documents
IMPORTING Parameters details for ISH_WP_VIEW_SPLITT
I_WPLACETYPE1 - Type of the Work Environment
Data type: NWPLACETYPEDefault: '001'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_WPLACEID1 -
Data type: NWPLACEIDOptional: No
Call by Reference: No ( called with pass by value option)
I_VIEWTYPE1 -
Data type: NVIEWTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_VIEWID1 -
Data type: NVIEWIDOptional: No
Call by Reference: No ( called with pass by value option)
I_USER - User Name
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_MODE -
Data type: CHAR01Default: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IR_SPLITTER_CONT -
Data type: CL_GUI_EASY_SPLITTER_CONTAINEROptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISH_WP_VIEW_SPLITT
C_WPLACETYPE2 -
Data type: NWPLACETYPEDefault: '001'
Optional: Yes
Call by Reference: No ( called with pass by value option)
C_WPLACEID2 -
Data type: NWPLACEIDOptional: Yes
Call by Reference: No ( called with pass by value option)
C_VIEWTYPE2 -
Data type: NVIEWTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
C_VIEWID2 -
Data type: NVIEWIDOptional: Yes
Call by Reference: No ( called with pass by value option)
C_SASH_POS -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
VIEW_NOT_SPLITTED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_WP_VIEW_SPLITT 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_c_wplacetype2 | TYPE NWPLACETYPE, " '001' | |||
| lv_i_wplacetype1 | TYPE NWPLACETYPE, " '001' | |||
| lv_view_not_splitted | TYPE NWPLACETYPE, " | |||
| lv_c_wplaceid2 | TYPE NWPLACEID, " | |||
| lv_i_wplaceid1 | TYPE NWPLACEID, " | |||
| lv_c_viewtype2 | TYPE NVIEWTYPE, " | |||
| lv_i_viewtype1 | TYPE NVIEWTYPE, " | |||
| lv_c_viewid2 | TYPE NVIEWID, " | |||
| lv_i_viewid1 | TYPE NVIEWID, " | |||
| lv_i_user | TYPE SY-UNAME, " | |||
| lv_c_sash_pos | TYPE I, " | |||
| lv_i_mode | TYPE CHAR01, " 'R' | |||
| lv_ir_splitter_cont | TYPE CL_GUI_EASY_SPLITTER_CONTAINER. " |
|   CALL FUNCTION 'ISH_WP_VIEW_SPLITT' " |
| EXPORTING | ||
| I_WPLACETYPE1 | = lv_i_wplacetype1 | |
| I_WPLACEID1 | = lv_i_wplaceid1 | |
| I_VIEWTYPE1 | = lv_i_viewtype1 | |
| I_VIEWID1 | = lv_i_viewid1 | |
| I_USER | = lv_i_user | |
| I_MODE | = lv_i_mode | |
| IR_SPLITTER_CONT | = lv_ir_splitter_cont | |
| CHANGING | ||
| C_WPLACETYPE2 | = lv_c_wplacetype2 | |
| C_WPLACEID2 | = lv_c_wplaceid2 | |
| C_VIEWTYPE2 | = lv_c_viewtype2 | |
| C_VIEWID2 | = lv_c_viewid2 | |
| C_SASH_POS | = lv_c_sash_pos | |
| EXCEPTIONS | ||
| VIEW_NOT_SPLITTED = 1 | ||
| . " ISH_WP_VIEW_SPLITT | ||
ABAP code using 7.40 inline data declarations to call FM ISH_WP_VIEW_SPLITT
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.| DATA(ld_c_wplacetype2) | = '001'. | |||
| DATA(ld_i_wplacetype1) | = '001'. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_i_user). | ||||
| DATA(ld_i_mode) | = 'R'. | |||
Search for further information about these or an SAP related objects