SAP ISP_ZU_READ Function Module for
ISP_ZU_READ is a standard isp zu read 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 isp zu read FM, simply by entering the name ISP_ZU_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: JG03
Program Name: SAPLJG03
Main Program: SAPLJG03
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISP_ZU_READ 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 'ISP_ZU_READ'".
EXPORTING
GPNR_IN = "Carrier's business partner number
IMPORTING
X_GESPERRT = "Lock indicator (summarized)
X_LOESCHVM = "Deletion flag (summarized)
ZUSTELLER_OUT = "Carrier structure
EXCEPTIONS
DELETED = 1 NOT_EXISTS = 2
IMPORTING Parameters details for ISP_ZU_READ
GPNR_IN - Carrier's business partner number
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_ZU_READ
X_GESPERRT - Lock indicator (summarized)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_LOESCHVM - Deletion flag (summarized)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ZUSTELLER_OUT - Carrier structure
Data type: JGVDB_ZUOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DELETED - Record has deletion indicator
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_EXISTS - Record does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_ZU_READ 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_deleted | TYPE STRING, " | |||
lv_gpnr_in | TYPE STRING, " | |||
lv_x_gesperrt | TYPE STRING, " | |||
lv_not_exists | TYPE STRING, " | |||
lv_x_loeschvm | TYPE STRING, " | |||
lv_zusteller_out | TYPE JGVDB_ZU. " |
  CALL FUNCTION 'ISP_ZU_READ' " |
EXPORTING | ||
GPNR_IN | = lv_gpnr_in | |
IMPORTING | ||
X_GESPERRT | = lv_x_gesperrt | |
X_LOESCHVM | = lv_x_loeschvm | |
ZUSTELLER_OUT | = lv_zusteller_out | |
EXCEPTIONS | ||
DELETED = 1 | ||
NOT_EXISTS = 2 | ||
. " ISP_ZU_READ |
ABAP code using 7.40 inline data declarations to call FM ISP_ZU_READ
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