SAP IMP_STORE_TRIGGER Function Module for Saves a Trigger - BDT

Search SAP Function Modules

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

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

Function IMP_STORE_TRIGGER 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 'IMP_STORE_TRIGGER'"Saves a Trigger - BDT
  EXPORTING
   IV_APPLCLASS =  "IMP: Application Class
*  IV_PARAMETERS_XML =  "
*  IV_RUN_ID = ' ' "IMP: ID of a Mass Run
   IV_TRIGGER =  "IMP: Trigger
   IV_HASH_VALUE_REL =  "
*  IV_HASH_VALUE_ALL =  "
*  IV_RUNDATE =  "IMP: Desired Execution Date
*  IT_PARAMETERS_1 =  "Obsolete
*  IT_PARAMETERS_C =  "IMP: Parameters as Cluster Table - Table Type
   IV_HANDLE =  "IMP Handle of IMP Object

EXCEPTIONS
   CX_EXCEPTIONS_IMP = 1 

.

IMPORTING Parameters details for IMP_STORE_TRIGGER

IV_APPLCLASS - IMP: Application Class

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

IV_PARAMETERS_XML -

Data type: STRING
Optional: Yes
Call by Reference: Yes

IV_RUN_ID - IMP: ID of a Mass Run

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

IV_TRIGGER - IMP: Trigger

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

IV_HASH_VALUE_REL -

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

IV_HASH_VALUE_ALL -

Data type: IMP_HASH32
Optional: Yes
Call by Reference: Yes

IV_RUNDATE - IMP: Desired Execution Date

Data type: IMP_RUNDATE
Optional: Yes
Call by Reference: Yes

IT_PARAMETERS_1 - Obsolete

Data type: TIMP_PARAMETERS_1
Optional: Yes
Call by Reference: Yes

IT_PARAMETERS_C - IMP: Parameters as Cluster Table - Table Type

Data type: TIMP_PARAMETERS_C
Optional: Yes
Call by Reference: Yes

IV_HANDLE - IMP Handle of IMP Object

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

EXCEPTIONS details

CX_EXCEPTIONS_IMP - IMP: Mass Processing - Exception Class

Data type:
Optional: No
Call by Reference: Yes

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

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