SAP ISM_BADCUSTOMER_CHECK Function Module for









ISM_BADCUSTOMER_CHECK is a standard ism badcustomer check 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 ism badcustomer check FM, simply by entering the name ISM_BADCUSTOMER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_BADCUSTOMER_CHECK 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 'ISM_BADCUSTOMER_CHECK'"
  EXPORTING
   IV_VKORG =  "
   IV_VTWEG =  "
   IV_SPART =  "
   IV_PARTNER =  "
   IV_AUART =  "
   IV_POART =  "
   IS_PARAMETER =  "
   IS_JGTSADR =  "

 IMPORTING
   ET_BADCUST =  "
   ES_RATING =  "

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for ISM_BADCUSTOMER_CHECK

IV_VKORG -

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

IV_VTWEG -

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

IV_SPART -

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

IV_PARTNER -

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

IV_AUART -

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

IV_POART -

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

IS_PARAMETER -

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

IS_JGTSADR -

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

EXPORTING Parameters details for ISM_BADCUSTOMER_CHECK

ET_BADCUST -

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

ES_RATING -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_BADCUSTOMER_CHECK 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_iv_vkorg  TYPE VKORG, "   
lv_not_found  TYPE VKORG, "   
lv_et_badcust  TYPE RJG_BADCUSTOMER_TAB, "   
lv_iv_vtweg  TYPE VTWEG, "   
lv_es_rating  TYPE RJG_BADCUSTOMER_RATING, "   
lv_iv_spart  TYPE SPART, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_iv_auart  TYPE AUART_ISP, "   
lv_iv_poart  TYPE POART_ISP, "   
lv_is_parameter  TYPE RJG_BADCUSTOMER_PAR, "   
lv_is_jgtsadr  TYPE JGTSADR. "   

  CALL FUNCTION 'ISM_BADCUSTOMER_CHECK'  "
    EXPORTING
         IV_VKORG = lv_iv_vkorg
         IV_VTWEG = lv_iv_vtweg
         IV_SPART = lv_iv_spart
         IV_PARTNER = lv_iv_partner
         IV_AUART = lv_iv_auart
         IV_POART = lv_iv_poart
         IS_PARAMETER = lv_is_parameter
         IS_JGTSADR = lv_is_jgtsadr
    IMPORTING
         ET_BADCUST = lv_et_badcust
         ES_RATING = lv_es_rating
    EXCEPTIONS
        NOT_FOUND = 1
. " ISM_BADCUSTOMER_CHECK




ABAP code using 7.40 inline data declarations to call FM ISM_BADCUSTOMER_CHECK

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



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!