SAP ISH_CASESERVICE_POOL_GET Function Module for IS-H: Read Service Data from Data Pool
ISH_CASESERVICE_POOL_GET is a standard ish caseservice pool get 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: Read Service Data from Data Pool 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 ish caseservice pool get FM, simply by entering the name ISH_CASESERVICE_POOL_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: NPOL
Program Name: SAPLNPOL
Main Program: SAPLNPOL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_CASESERVICE_POOL_GET 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_CASESERVICE_POOL_GET'"IS-H: Read Service Data from Data Pool.
EXPORTING
SS_EINRI = "IS-H: Institution
SS_FALNR = "IS-H: Case Number
IMPORTING
SS_SRV_TRANSFERRED = "
TABLES
* SS_VNLEI_CURR = "Current Performed Services
* SS_NLEI_DABA = "Performed Services from DB
* SS_NLEI_ORIG = "
* SS_VNNLZ_CURR = "Current Service <-> Business Partner Assignments
* SS_NNLZ_DABA = "Service <-> Business Partner Assignment from DB
* SS_VNLLZ_CURR = "Current Service <-> Service Assignment
* SS_NLLZ_DABA = "Service <-> Service Assignment from DB
* SS_VNLICZ_CURR = "Current Service <-> SP Code Assignments
* SS_NLICZ_DABA = "Service <-> Surgical Procedures Code Assignments from DB
IMPORTING Parameters details for ISH_CASESERVICE_POOL_GET
SS_EINRI - IS-H: Institution
Data type: EINRIOptional: No
Call by Reference: No ( called with pass by value option)
SS_FALNR - IS-H: Case Number
Data type: FALNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISH_CASESERVICE_POOL_GET
SS_SRV_TRANSFERRED -
Data type: ISH_ON_OFFOptional: No
Call by Reference: Yes
TABLES Parameters details for ISH_CASESERVICE_POOL_GET
SS_VNLEI_CURR - Current Performed Services
Data type: VNLEIOptional: Yes
Call by Reference: Yes
SS_NLEI_DABA - Performed Services from DB
Data type: NLEIOptional: Yes
Call by Reference: Yes
SS_NLEI_ORIG -
Data type: NLEIOptional: Yes
Call by Reference: Yes
SS_VNNLZ_CURR - Current Service <-> Business Partner Assignments
Data type: VNNLZOptional: Yes
Call by Reference: Yes
SS_NNLZ_DABA - Service <-> Business Partner Assignment from DB
Data type: NNLZOptional: Yes
Call by Reference: Yes
SS_VNLLZ_CURR - Current Service <-> Service Assignment
Data type: VNLLZOptional: Yes
Call by Reference: Yes
SS_NLLZ_DABA - Service <-> Service Assignment from DB
Data type: NLLZOptional: Yes
Call by Reference: Yes
SS_VNLICZ_CURR - Current Service <-> SP Code Assignments
Data type: VNLICZOptional: Yes
Call by Reference: Yes
SS_NLICZ_DABA - Service <-> Surgical Procedures Code Assignments from DB
Data type: NLICZOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISH_CASESERVICE_POOL_GET 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_ss_einri | TYPE EINRI, " | |||
| lt_ss_vnlei_curr | TYPE STANDARD TABLE OF VNLEI, " | |||
| lv_ss_srv_transferred | TYPE ISH_ON_OFF, " | |||
| lv_ss_falnr | TYPE FALNR, " | |||
| lt_ss_nlei_daba | TYPE STANDARD TABLE OF NLEI, " | |||
| lt_ss_nlei_orig | TYPE STANDARD TABLE OF NLEI, " | |||
| lt_ss_vnnlz_curr | TYPE STANDARD TABLE OF VNNLZ, " | |||
| lt_ss_nnlz_daba | TYPE STANDARD TABLE OF NNLZ, " | |||
| lt_ss_vnllz_curr | TYPE STANDARD TABLE OF VNLLZ, " | |||
| lt_ss_nllz_daba | TYPE STANDARD TABLE OF NLLZ, " | |||
| lt_ss_vnlicz_curr | TYPE STANDARD TABLE OF VNLICZ, " | |||
| lt_ss_nlicz_daba | TYPE STANDARD TABLE OF NLICZ. " |
|   CALL FUNCTION 'ISH_CASESERVICE_POOL_GET' "IS-H: Read Service Data from Data Pool |
| EXPORTING | ||
| SS_EINRI | = lv_ss_einri | |
| SS_FALNR | = lv_ss_falnr | |
| IMPORTING | ||
| SS_SRV_TRANSFERRED | = lv_ss_srv_transferred | |
| TABLES | ||
| SS_VNLEI_CURR | = lt_ss_vnlei_curr | |
| SS_NLEI_DABA | = lt_ss_nlei_daba | |
| SS_NLEI_ORIG | = lt_ss_nlei_orig | |
| SS_VNNLZ_CURR | = lt_ss_vnnlz_curr | |
| SS_NNLZ_DABA | = lt_ss_nnlz_daba | |
| SS_VNLLZ_CURR | = lt_ss_vnllz_curr | |
| SS_NLLZ_DABA | = lt_ss_nllz_daba | |
| SS_VNLICZ_CURR | = lt_ss_vnlicz_curr | |
| SS_NLICZ_DABA | = lt_ss_nlicz_daba | |
| . " ISH_CASESERVICE_POOL_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISH_CASESERVICE_POOL_GET
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.Search for further information about these or an SAP related objects