SAP TRIGGER_INFCFGCHECK Function Module for Informix: Trigger Checktool INFCFGCHECK

Search SAP Function Modules

TRIGGER_INFCFGCHECK is a standard trigger infcfgcheck SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Informix: Trigger Checktool INFCFGCHECK 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 trigger infcfgcheck FM, simply by entering the name TRIGGER_INFCFGCHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SICT
Program Name: SAPLSICT
Main Program: SAPLSICT
Appliation area: S
Release date: 16-Apr-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRIGGER_INFCFGCHECK 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 'TRIGGER_INFCFGCHECK'"Informix: Trigger Checktool INFCFGCHECK
  EXPORTING
   PARAMS =  "
   TERMINATIONWAIT =  "

EXCEPTIONS
   SXPG_COMMAND_NOT_FOUND = 1    SXPG_X_ERROR = 10    SXPG_OTHERS = 11    ALLAZY_PROBLEM = 12    SXPG_NO_PERMISSION = 2    SXPG_PARAMETERS_TOO_LONG = 3    SXPG_PARAMETER_EXPECTED = 4    SXPG_PROGRAM_START_ERROR = 5    SXPG_PROGRAM_TERMINATION_ERROR = 6    SXPG_SECURITY_RISK = 7    SXPG_TOO_MANY_PARAMETERS = 8    SXPG_WRONG_CHECK_CALL_INTERFAC = 9 

.

IMPORTING Parameters details for TRIGGER_INFCFGCHECK

PARAMS -

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

TERMINATIONWAIT -

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

EXCEPTIONS details

SXPG_COMMAND_NOT_FOUND -

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

SXPG_X_ERROR -

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

SXPG_OTHERS -

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

ALLAZY_PROBLEM -

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

SXPG_NO_PERMISSION -

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

SXPG_PARAMETERS_TOO_LONG -

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

SXPG_PARAMETER_EXPECTED -

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

SXPG_PROGRAM_START_ERROR -

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

SXPG_PROGRAM_TERMINATION_ERROR -

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

SXPG_SECURITY_RISK -

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

SXPG_TOO_MANY_PARAMETERS -

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

SXPG_WRONG_CHECK_CALL_INTERFAC -

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

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

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