SAP ISP_CONTRACT_VSG_MA_READ Function Module for
ISP_CONTRACT_VSG_MA_READ is a standard isp contract vsg ma 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 contract vsg ma read FM, simply by entering the name ISP_CONTRACT_VSG_MA_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: JL02
Program Name: SAPLJL02
Main Program: SAPLJL02
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_CONTRACT_VSG_MA_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_CONTRACT_VSG_MA_READ'".
EXPORTING
BEZIRK = "
BEZRUNDE = "
* DATE = SY-DATUM "
LIEFERART = "
ROLLE = "
VSG = "
VSG_MA = "
IMPORTING
JGSBV_ABR_OUT = "
TJLZM_OUT = "
TJLZT_OUT = "
EXCEPTIONS
DATE_ERROR = 1 INPUT_ERROR = 2 NO_EMPLOYEMENT = 3 NO_MODALITIES = 4 ROLLE_ERROR = 5
IMPORTING Parameters details for ISP_CONTRACT_VSG_MA_READ
BEZIRK -
Data type: JLTVM01-BEZIRKOptional: No
Call by Reference: No ( called with pass by value option)
BEZRUNDE -
Data type: JLTVM01-BEZRUNDEOptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: JLTVM01-WDAT1Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
LIEFERART -
Data type: JLTVM01-LIEFERARTOptional: No
Call by Reference: No ( called with pass by value option)
ROLLE -
Data type: JGTBV-JPARVWOptional: No
Call by Reference: No ( called with pass by value option)
VSG -
Data type: JLTVM01-VSGOptional: No
Call by Reference: No ( called with pass by value option)
VSG_MA -
Data type: JLTVM01-VSG_MAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_CONTRACT_VSG_MA_READ
JGSBV_ABR_OUT -
Data type: JGSBV_ABROptional: No
Call by Reference: No ( called with pass by value option)
TJLZM_OUT -
Data type: TJLZMOptional: No
Call by Reference: No ( called with pass by value option)
TJLZT_OUT -
Data type: TJLZTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DATE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INPUT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_EMPLOYEMENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_MODALITIES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ROLLE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_CONTRACT_VSG_MA_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_bezirk | TYPE JLTVM01-BEZIRK, " | |||
| lv_date_error | TYPE JLTVM01, " | |||
| lv_jgsbv_abr_out | TYPE JGSBV_ABR, " | |||
| lv_bezrunde | TYPE JLTVM01-BEZRUNDE, " | |||
| lv_tjlzm_out | TYPE TJLZM, " | |||
| lv_input_error | TYPE TJLZM, " | |||
| lv_date | TYPE JLTVM01-WDAT1, " SY-DATUM | |||
| lv_tjlzt_out | TYPE TJLZT, " | |||
| lv_no_employement | TYPE TJLZT, " | |||
| lv_lieferart | TYPE JLTVM01-LIEFERART, " | |||
| lv_no_modalities | TYPE JLTVM01, " | |||
| lv_rolle | TYPE JGTBV-JPARVW, " | |||
| lv_rolle_error | TYPE JGTBV, " | |||
| lv_vsg | TYPE JLTVM01-VSG, " | |||
| lv_vsg_ma | TYPE JLTVM01-VSG_MA. " |
|   CALL FUNCTION 'ISP_CONTRACT_VSG_MA_READ' " |
| EXPORTING | ||
| BEZIRK | = lv_bezirk | |
| BEZRUNDE | = lv_bezrunde | |
| DATE | = lv_date | |
| LIEFERART | = lv_lieferart | |
| ROLLE | = lv_rolle | |
| VSG | = lv_vsg | |
| VSG_MA | = lv_vsg_ma | |
| IMPORTING | ||
| JGSBV_ABR_OUT | = lv_jgsbv_abr_out | |
| TJLZM_OUT | = lv_tjlzm_out | |
| TJLZT_OUT | = lv_tjlzt_out | |
| EXCEPTIONS | ||
| DATE_ERROR = 1 | ||
| INPUT_ERROR = 2 | ||
| NO_EMPLOYEMENT = 3 | ||
| NO_MODALITIES = 4 | ||
| ROLLE_ERROR = 5 | ||
| . " ISP_CONTRACT_VSG_MA_READ | ||
ABAP code using 7.40 inline data declarations to call FM ISP_CONTRACT_VSG_MA_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.| "SELECT single BEZIRK FROM JLTVM01 INTO @DATA(ld_bezirk). | ||||
| "SELECT single BEZRUNDE FROM JLTVM01 INTO @DATA(ld_bezrunde). | ||||
| "SELECT single WDAT1 FROM JLTVM01 INTO @DATA(ld_date). | ||||
| DATA(ld_date) | = SY-DATUM. | |||
| "SELECT single LIEFERART FROM JLTVM01 INTO @DATA(ld_lieferart). | ||||
| "SELECT single JPARVW FROM JGTBV INTO @DATA(ld_rolle). | ||||
| "SELECT single VSG FROM JLTVM01 INTO @DATA(ld_vsg). | ||||
| "SELECT single VSG_MA FROM JLTVM01 INTO @DATA(ld_vsg_ma). | ||||
Search for further information about these or an SAP related objects