SAP ISH_EDI_CASE_OVERVIEW Function Module for
ISH_EDI_CASE_OVERVIEW is a standard ish edi case overview 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 edi case overview FM, simply by entering the name ISH_EDI_CASE_OVERVIEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: NC12
Program Name: SAPLNC12
Main Program: SAPLNC12
Appliation area: N
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function ISH_EDI_CASE_OVERVIEW 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_EDI_CASE_OVERVIEW'".
EXPORTING
EINRI = "
EDIPROC = "
FALNR = "
* READ_UNBUFFERED = ' ' "
* POPUP = ' ' "
* POPUP_STARTCOL = 1 "
* POPUP_STARTLIN = 1 "
* POPUP_ENDCOL = 85 "
* POPUP_ENDLIN = 17 "
EXCEPTIONS
NO_DATA_FOUND = 1
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_SAPLNC12_001 IS-H: User Exit for Case Exclusions
EXIT_SAPLNC12_002 IS-H: User Exit for Patient Exclusion
EXIT_SAPLNC12_003 IS-H EDI User Exit Order File Name in EDI Procedure
EXIT_SAPLNC12_004 IS-H ยง301 User Exit Write Order File (Outbound)
IMPORTING Parameters details for ISH_EDI_CASE_OVERVIEW
EINRI -
Data type: NFAL-EINRIOptional: No
Call by Reference: No ( called with pass by value option)
EDIPROC -
Data type: NC301S-EDIPROCOptional: No
Call by Reference: No ( called with pass by value option)
FALNR -
Data type: NFAL-FALNROptional: No
Call by Reference: No ( called with pass by value option)
READ_UNBUFFERED -
Data type: RNCOM-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP -
Data type: RNCOM-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP_STARTCOL -
Data type: IDefault: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP_STARTLIN -
Data type: IDefault: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP_ENDCOL -
Data type: IDefault: 85
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP_ENDLIN -
Data type: IDefault: 17
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_EDI_CASE_OVERVIEW 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_einri | TYPE NFAL-EINRI, " | |||
lv_no_data_found | TYPE NFAL, " | |||
lv_ediproc | TYPE NC301S-EDIPROC, " | |||
lv_falnr | TYPE NFAL-FALNR, " | |||
lv_read_unbuffered | TYPE RNCOM-XFELD, " SPACE | |||
lv_popup | TYPE RNCOM-XFELD, " SPACE | |||
lv_popup_startcol | TYPE I, " 1 | |||
lv_popup_startlin | TYPE I, " 1 | |||
lv_popup_endcol | TYPE I, " 85 | |||
lv_popup_endlin | TYPE I. " 17 |
  CALL FUNCTION 'ISH_EDI_CASE_OVERVIEW' " |
EXPORTING | ||
EINRI | = lv_einri | |
EDIPROC | = lv_ediproc | |
FALNR | = lv_falnr | |
READ_UNBUFFERED | = lv_read_unbuffered | |
POPUP | = lv_popup | |
POPUP_STARTCOL | = lv_popup_startcol | |
POPUP_STARTLIN | = lv_popup_startlin | |
POPUP_ENDCOL | = lv_popup_endcol | |
POPUP_ENDLIN | = lv_popup_endlin | |
EXCEPTIONS | ||
NO_DATA_FOUND = 1 | ||
. " ISH_EDI_CASE_OVERVIEW |
ABAP code using 7.40 inline data declarations to call FM ISH_EDI_CASE_OVERVIEW
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 EINRI FROM NFAL INTO @DATA(ld_einri). | ||||
"SELECT single EDIPROC FROM NC301S INTO @DATA(ld_ediproc). | ||||
"SELECT single FALNR FROM NFAL INTO @DATA(ld_falnr). | ||||
"SELECT single XFELD FROM RNCOM INTO @DATA(ld_read_unbuffered). | ||||
DATA(ld_read_unbuffered) | = ' '. | |||
"SELECT single XFELD FROM RNCOM INTO @DATA(ld_popup). | ||||
DATA(ld_popup) | = ' '. | |||
DATA(ld_popup_startcol) | = 1. | |||
DATA(ld_popup_startlin) | = 1. | |||
DATA(ld_popup_endcol) | = 85. | |||
DATA(ld_popup_endlin) | = 17. | |||
Search for further information about these or an SAP related objects