SAP ISH_CONTRACT_SCHEMES_SAVE Function Module for
ISH_CONTRACT_SCHEMES_SAVE is a standard ish contract schemes save 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 contract schemes save FM, simply by entering the name ISH_CONTRACT_SCHEMES_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: NVVH
Program Name: SAPLNVVH
Main Program: SAPLNVVH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_CONTRACT_SCHEMES_SAVE 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_CONTRACT_SCHEMES_SAVE'".
EXPORTING
SS_PATNR = "Patient Number
* SS_EINRI = "Institution
* SS_FALNR = "Case Number
* SS_LFDNR = "Sequence Number of the Movement
* SS_DIALOG = ' ' "Dialog Allowed (ON/OFF)
* SS_ACTION = 'C' "Time of Check
SS_CALUP = "Event for which Changes Have Occurred
IMPORTING
SS_RETMAXTYPE = "Worst Message Type Returned
SS_CHANGED = "
TABLES
SS_RETURN = "Table with Error Messages
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_SAPLNVVH_001 IS-H: Insurance Relationship Enhancement
EXIT_SAPLNVVH_002 IS-H: Enhancement for Save Insurance Relationships
EXIT_SAPLNVVH_003 IS-H: Function Exit Maint. Insurance Relationships - Call Maint. Screen
EXIT_SAPLNVVH_004 IS-H: Function Exit Maint. Insurance Relationships - Save Maint. Screen
IMPORTING Parameters details for ISH_CONTRACT_SCHEMES_SAVE
SS_PATNR - Patient Number
Data type: PATNROptional: No
Call by Reference: No ( called with pass by value option)
SS_EINRI - Institution
Data type: EINRIOptional: Yes
Call by Reference: No ( called with pass by value option)
SS_FALNR - Case Number
Data type: FALNROptional: Yes
Call by Reference: No ( called with pass by value option)
SS_LFDNR - Sequence Number of the Movement
Data type: LFDBEWOptional: Yes
Call by Reference: No ( called with pass by value option)
SS_DIALOG - Dialog Allowed (ON/OFF)
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_ACTION - Time of Check
Data type: ISH_POL_ACTIONDefault: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_CALUP - Event for which Changes Have Occurred
Data type: ISH_POL_CALUPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISH_CONTRACT_SCHEMES_SAVE
SS_RETMAXTYPE - Worst Message Type Returned
Data type: NPDOK-BAPIRETMAXTYOptional: No
Call by Reference: No ( called with pass by value option)
SS_CHANGED -
Data type: ISH_ON_OFFOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_CONTRACT_SCHEMES_SAVE
SS_RETURN - Table with Error Messages
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_CONTRACT_SCHEMES_SAVE 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_patnr | TYPE PATNR, " | |||
| lt_ss_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_ss_retmaxtype | TYPE NPDOK-BAPIRETMAXTY, " | |||
| lv_ss_einri | TYPE EINRI, " | |||
| lv_ss_changed | TYPE ISH_ON_OFF, " | |||
| lv_ss_falnr | TYPE FALNR, " | |||
| lv_ss_lfdnr | TYPE LFDBEW, " | |||
| lv_ss_dialog | TYPE ISH_ON_OFF, " SPACE | |||
| lv_ss_action | TYPE ISH_POL_ACTION, " 'C' | |||
| lv_ss_calup | TYPE ISH_POL_CALUP. " |
|   CALL FUNCTION 'ISH_CONTRACT_SCHEMES_SAVE' " |
| EXPORTING | ||
| SS_PATNR | = lv_ss_patnr | |
| SS_EINRI | = lv_ss_einri | |
| SS_FALNR | = lv_ss_falnr | |
| SS_LFDNR | = lv_ss_lfdnr | |
| SS_DIALOG | = lv_ss_dialog | |
| SS_ACTION | = lv_ss_action | |
| SS_CALUP | = lv_ss_calup | |
| IMPORTING | ||
| SS_RETMAXTYPE | = lv_ss_retmaxtype | |
| SS_CHANGED | = lv_ss_changed | |
| TABLES | ||
| SS_RETURN | = lt_ss_return | |
| . " ISH_CONTRACT_SCHEMES_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM ISH_CONTRACT_SCHEMES_SAVE
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 BAPIRETMAXTY FROM NPDOK INTO @DATA(ld_ss_retmaxtype). | ||||
| DATA(ld_ss_dialog) | = ' '. | |||
| DATA(ld_ss_action) | = 'C'. | |||
Search for further information about these or an SAP related objects