SAP ISHCM_ADMISSION_INTERFACE Function Module for IS-HCM: Interface function module to external program









ISHCM_ADMISSION_INTERFACE is a standard ishcm admission interface 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-HCM: Interface function module to external program 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 ishcm admission interface FM, simply by entering the name ISHCM_ADMISSION_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHCM_ADMISSION_INTERFACE 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 'ISHCM_ADMISSION_INTERFACE'"IS-HCM: Interface function module to external program
EXPORTING
RFCDEST = "RFC destination
RFCFUNAM = "Function to be called externally

IMPORTING
STATUS = "Status display / return code

TABLES
I_ORDERS = "Order data (events + movements)
I_NBEW = "Movement data
I_NDIA = "Diagnoses
I_NFAL = "Case data
I_NFKL = "Case classification
I_NPAT = "Patient data
I_NVVF = "Insurance relationships by case

EXCEPTIONS
SYSTEM_FAILURE = 1 COMMUNICATION_FAILURE = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for ISHCM_ADMISSION_INTERFACE

RFCDEST - RFC destination

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

RFCFUNAM - Function to be called externally

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

EXPORTING Parameters details for ISHCM_ADMISSION_INTERFACE

STATUS - Status display / return code

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

TABLES Parameters details for ISHCM_ADMISSION_INTERFACE

I_ORDERS - Order data (events + movements)

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

I_NBEW - Movement data

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

I_NDIA - Diagnoses

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

I_NFAL - Case data

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

I_NFKL - Case classification

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

I_NPAT - Patient data

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

I_NVVF - Insurance relationships by case

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

EXCEPTIONS details

SYSTEM_FAILURE - System error during RFC

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

COMMUNICATION_FAILURE - Communication error during RFC

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

INTERNAL_ERROR - Other error

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

Copy and paste ABAP code example for ISHCM_ADMISSION_INTERFACE 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_status  TYPE SY-SUBRC, "   
lv_rfcdest  TYPE TN02S-RFCDEST, "   
lt_i_orders  TYPE STANDARD TABLE OF RNCORDER, "   
lv_system_failure  TYPE RNCORDER, "   
lt_i_nbew  TYPE STANDARD TABLE OF VNBEW, "   
lv_rfcfunam  TYPE TNCD1-FUNAM, "   
lv_communication_failure  TYPE TNCD1, "   
lt_i_ndia  TYPE STANDARD TABLE OF NDIA, "   
lv_internal_error  TYPE NDIA, "   
lt_i_nfal  TYPE STANDARD TABLE OF NFAL, "   
lt_i_nfkl  TYPE STANDARD TABLE OF NFKL, "   
lt_i_npat  TYPE STANDARD TABLE OF NPAT, "   
lt_i_nvvf  TYPE STANDARD TABLE OF RNVVF. "   

  CALL FUNCTION 'ISHCM_ADMISSION_INTERFACE'  "IS-HCM: Interface function module to external program
    EXPORTING
         RFCDEST = lv_rfcdest
         RFCFUNAM = lv_rfcfunam
    IMPORTING
         STATUS = lv_status
    TABLES
         I_ORDERS = lt_i_orders
         I_NBEW = lt_i_nbew
         I_NDIA = lt_i_ndia
         I_NFAL = lt_i_nfal
         I_NFKL = lt_i_nfkl
         I_NPAT = lt_i_npat
         I_NVVF = lt_i_nvvf
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        COMMUNICATION_FAILURE = 2
        INTERNAL_ERROR = 3
. " ISHCM_ADMISSION_INTERFACE




ABAP code using 7.40 inline data declarations to call FM ISHCM_ADMISSION_INTERFACE

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 SUBRC FROM SY INTO @DATA(ld_status).
 
"SELECT single RFCDEST FROM TN02S INTO @DATA(ld_rfcdest).
 
 
 
 
"SELECT single FUNAM FROM TNCD1 INTO @DATA(ld_rfcfunam).
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!