SAP ISH_MOVEMENT_SUBSCREEN_SAVE Function Module for IS-H: Save Movement Data Subscreen

Search SAP Function Modules

ISH_MOVEMENT_SUBSCREEN_SAVE is a standard ish movement subscreen save 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: Save Movement Data Subscreen 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 movement subscreen save FM, simply by entering the name ISH_MOVEMENT_SUBSCREEN_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: NBE2
Program Name: SAPLNBE2
Main Program: SAPLNBE2
Appliation area: N
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_MOVEMENT_SUBSCREEN_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_MOVEMENT_SUBSCREEN_SAVE'"IS-H: Save Movement Data Subscreen
  EXPORTING
   SS_EINRI =  "Institution
   SS_PATNR =  "Patient Number
   SS_FALNR =  "Case Number
*  SS_LFDNR = 0 "Sequence Number of the Visit
*  SS_VCODE_NFAL = 'UPD' "Processing Mode - Case
*  SS_VCODE_NBEW = 'UPD' "Processing Mode Admission/Visit

 IMPORTING
   SS_FALNR_NEW =  "New Case Number (with Internal Number Assignment)
   SS_LFDNR_NEW =  "New Sequence Number of the Movement

EXCEPTIONS
   ERROR = 1 

.

IMPORTING Parameters details for ISH_MOVEMENT_SUBSCREEN_SAVE

SS_EINRI - Institution

Data type: NBEW-EINRI
Optional: No
Call by Reference: No ( called with pass by value option)

SS_PATNR - Patient Number

Data type: NPAT-PATNR
Optional: No
Call by Reference: No ( called with pass by value option)

SS_FALNR - Case Number

Data type: NBEW-FALNR
Optional: No
Call by Reference: No ( called with pass by value option)

SS_LFDNR - Sequence Number of the Visit

Data type: NBEW-LFDNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_VCODE_NFAL - Processing Mode - Case

Data type: TNDYM-VCODE
Default: 'UPD'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_VCODE_NBEW - Processing Mode Admission/Visit

Data type: TNDYM-VCODE
Default: 'UPD'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISH_MOVEMENT_SUBSCREEN_SAVE

SS_FALNR_NEW - New Case Number (with Internal Number Assignment)

Data type: NFAL-FALNR
Optional: No
Call by Reference: No ( called with pass by value option)

SS_LFDNR_NEW - New Sequence Number of the Movement

Data type: NBEW-LFDNR
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR - Other Errors (for example, Not Found)

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISH_MOVEMENT_SUBSCREEN_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.

ABAP code using 7.40 inline data declarations to call FM ISH_MOVEMENT_SUBSCREEN_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.

Search for further information about these or an SAP related objects