SAP ISH_CH_API_PI_INQUIRY Function Module for









ISH_CH_API_PI_INQUIRY is a standard ish ch api pi inquiry 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 ch api pi inquiry FM, simply by entering the name ISH_CH_API_PI_INQUIRY into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_CH_API_PI_INQUIRY 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_CH_API_PI_INQUIRY'"
EXPORTING
I_EINRI = "
* I_USER = SY-UNAME "
IS_NEGK = "
* I_USECASE = ' ' "
* I_TREATMENT_DATE = SY-DATUM "
* I_RETRY_RC15_16 = ON "

IMPORTING
ES_NEGK = "
E_WORST_MTYPE = "
ET_RETURN = "
E_NEW_INQ_IND = "
ES_NEW_CRD_DAT = "
ES_NEW_INQ_DAT = "

EXCEPTIONS
NOT_FOUND = 1 NOT_UNIQUE = 2 FORMAL_ERROR = 3 AUTH_ERROR = 4 DIFF_LOCAL = 5 ERROR = 6
.



IMPORTING Parameters details for ISH_CH_API_PI_INQUIRY

I_EINRI -

Data type: EINRI
Optional: No
Call by Reference: Yes

I_USER -

Data type: SY-UNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

IS_NEGK -

Data type: NEGK_DATA
Optional: No
Call by Reference: Yes

I_USECASE -

Data type: NEHCT_USECASE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_TREATMENT_DATE -

Data type: NFAL-BEGDT
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_RETRY_RC15_16 -

Data type: ISH_ON_OFF
Default: ON
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISH_CH_API_PI_INQUIRY

ES_NEGK -

Data type: NEGK_DATA
Optional: No
Call by Reference: Yes

E_WORST_MTYPE -

Data type: BAPI_MTYPE
Optional: No
Call by Reference: Yes

ET_RETURN -

Data type: BAPIRETTAB
Optional: No
Call by Reference: Yes

E_NEW_INQ_IND -

Data type: I
Optional: No
Call by Reference: Yes

ES_NEW_CRD_DAT -

Data type: NEGK_DATA
Optional: No
Call by Reference: Yes

ES_NEW_INQ_DAT -

Data type: NEGK_DATA
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NOT_UNIQUE -

Data type:
Optional: No
Call by Reference: Yes

FORMAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

AUTH_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DIFF_LOCAL -

Data type:
Optional: No
Call by Reference: Yes

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_CH_API_PI_INQUIRY 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_es_negk  TYPE NEGK_DATA, "   
lv_i_einri  TYPE EINRI, "   
lv_not_found  TYPE EINRI, "   
lv_i_user  TYPE SY-UNAME, "   SY-UNAME
lv_not_unique  TYPE SY, "   
lv_e_worst_mtype  TYPE BAPI_MTYPE, "   
lv_is_negk  TYPE NEGK_DATA, "   
lv_et_return  TYPE BAPIRETTAB, "   
lv_formal_error  TYPE BAPIRETTAB, "   
lv_i_usecase  TYPE NEHCT_USECASE, "   SPACE
lv_auth_error  TYPE NEHCT_USECASE, "   
lv_e_new_inq_ind  TYPE I, "   
lv_diff_local  TYPE I, "   
lv_es_new_crd_dat  TYPE NEGK_DATA, "   
lv_i_treatment_date  TYPE NFAL-BEGDT, "   SY-DATUM
lv_error  TYPE NFAL, "   
lv_es_new_inq_dat  TYPE NEGK_DATA, "   
lv_i_retry_rc15_16  TYPE ISH_ON_OFF. "   ON

  CALL FUNCTION 'ISH_CH_API_PI_INQUIRY'  "
    EXPORTING
         I_EINRI = lv_i_einri
         I_USER = lv_i_user
         IS_NEGK = lv_is_negk
         I_USECASE = lv_i_usecase
         I_TREATMENT_DATE = lv_i_treatment_date
         I_RETRY_RC15_16 = lv_i_retry_rc15_16
    IMPORTING
         ES_NEGK = lv_es_negk
         E_WORST_MTYPE = lv_e_worst_mtype
         ET_RETURN = lv_et_return
         E_NEW_INQ_IND = lv_e_new_inq_ind
         ES_NEW_CRD_DAT = lv_es_new_crd_dat
         ES_NEW_INQ_DAT = lv_es_new_inq_dat
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_UNIQUE = 2
        FORMAL_ERROR = 3
        AUTH_ERROR = 4
        DIFF_LOCAL = 5
        ERROR = 6
. " ISH_CH_API_PI_INQUIRY




ABAP code using 7.40 inline data declarations to call FM ISH_CH_API_PI_INQUIRY

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 UNAME FROM SY INTO @DATA(ld_i_user).
DATA(ld_i_user) = SY-UNAME.
 
 
 
 
 
 
DATA(ld_i_usecase) = ' '.
 
 
 
 
 
"SELECT single BEGDT FROM NFAL INTO @DATA(ld_i_treatment_date).
DATA(ld_i_treatment_date) = SY-DATUM.
 
 
 
DATA(ld_i_retry_rc15_16) = ON.
 


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!