SAP ISU_SINGLE_CUSTOM_EXIST_CHECK Function Module for IS-U: Existency Check for Individual Customizing

Search SAP Function Modules

ISU_SINGLE_CUSTOM_EXIST_CHECK is a standard isu single custom exist check 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-U: Existency Check for Individual Customizing 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 isu single custom exist check FM, simply by entering the name ISU_SINGLE_CUSTOM_EXIST_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_SINGLE_CUSTOM_EXIST_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 'ISU_SINGLE_CUSTOM_EXIST_CHECK'"IS-U: Existency Check for Individual Customizing
 IMPORTING
   Y_EXIST_ALL =  "
   Y_EXIST_NO =  "ISU Indicator - General
   Y_EXIST_PART =  "ISU Indicator - General

CHANGING
   X_CUST =  "ISU-Internal: Check Existence of Individual CustomizingField

EXCEPTIONS
   GENERAL_FAULT = 1    NO_CHECKING = 2 

.

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_SAPLE20A_001 IS-U: User-Defined Checks in Screen Fields
EXIT_SAPLE20A_002 IS-U: User-Defined Preassignment of Screen Fields
EXIT_SAPLE20A_003 IS-U: User Exit PBO: PBO for Customer Subscreen
EXIT_SAPLE20A_004 IS-U: User Exit PAI_BEFORE: Prepares the CALL SUBSCREEN PAI
EXIT_SAPLE20A_005 IS-U: User Exit PAI_AFTER: Closes the CALL SUBSCREEN PAI
EXIT_SAPLE20A_006 IS-U: User Exit OPEN: Opens Customer Object Processing
EXIT_SAPLE20A_007 IS-U: User Exit INPUT: Checks and Copies Entries on Customer Subscreen
EXIT_SAPLE20A_008 IS-U: User Exit PREPARE_CLOSE: Prepares Closing of Customer Data
EXIT_SAPLE20A_009 IS-U: User Exit ACTION: Actions of Customer Subscreen
EXIT_SAPLE20A_010 IS-U: User Exit CLOSE: Ends Customer Data Processing

EXPORTING Parameters details for ISU_SINGLE_CUSTOM_EXIST_CHECK

Y_EXIST_ALL -

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

Y_EXIST_NO - ISU Indicator - General

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

Y_EXIST_PART - ISU Indicator - General

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

CHANGING Parameters details for ISU_SINGLE_CUSTOM_EXIST_CHECK

X_CUST - ISU-Internal: Check Existence of Individual CustomizingField

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

EXCEPTIONS details

GENERAL_FAULT -

Data type:
Optional: No
Call by Reference: Yes

NO_CHECKING -

Data type:
Optional: No
Call by Reference: Yes

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

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