SAP Function Modules

FIEH_EVENT_EXCEPTION_TRIGGER SAP Function module







FIEH_EVENT_EXCEPTION_TRIGGER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FIEH_EVENT_EXCEPTION_TRIGGER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FIEH
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM FIEH_EVENT_EXCEPTION_TRIGGER - FIEH EVENT EXCEPTION TRIGGER





CALL FUNCTION 'FIEH_EVENT_EXCEPTION_TRIGGER' "
  EXPORTING
    id_component =              " fieh_component
    id_bukrs =                  " bukrs
*   id_objectid =               " fieh_refobj
    id_objid =                  " fieh_objid
*   id_subid =                  " fieh_subid
*   id_accrule =                " fieh_accrule
*   id_valid =                  " fieh_valid
    id_msgid =                  " bapiret2-id
*   id_type =                   " bapiret2-type
*   id_number =                 " bapiret2-number
    id_loghandle =              " balloghndl
    .  "  FIEH_EVENT_EXCEPTION_TRIGGER

ABAP code example for Function Module FIEH_EVENT_EXCEPTION_TRIGGER





The ABAP code below is a full code listing to execute function module FIEH_EVENT_EXCEPTION_TRIGGER including all data declarations. The code uses 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 original method of declaring data variables up front. 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).


DATA(ld_id_component) = 'Check type of data required'.
DATA(ld_id_bukrs) = 'Check type of data required'.
DATA(ld_id_objectid) = 'Check type of data required'.
DATA(ld_id_objid) = 'Check type of data required'.
DATA(ld_id_subid) = 'Check type of data required'.
DATA(ld_id_accrule) = 'Check type of data required'.
DATA(ld_id_valid) = 'Check type of data required'.

DATA(ld_id_msgid) = some text here

DATA(ld_id_type) = some text here

DATA(ld_id_number) = Check type of data required
DATA(ld_id_loghandle) = 'Check type of data required'. . CALL FUNCTION 'FIEH_EVENT_EXCEPTION_TRIGGER' EXPORTING id_component = ld_id_component id_bukrs = ld_id_bukrs * id_objectid = ld_id_objectid id_objid = ld_id_objid * id_subid = ld_id_subid * id_accrule = ld_id_accrule * id_valid = ld_id_valid id_msgid = ld_id_msgid * id_type = ld_id_type * id_number = ld_id_number id_loghandle = ld_id_loghandle . " FIEH_EVENT_EXCEPTION_TRIGGER
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_id_component  TYPE FIEH_COMPONENT ,
ld_id_bukrs  TYPE BUKRS ,
ld_id_objectid  TYPE FIEH_REFOBJ ,
ld_id_objid  TYPE FIEH_OBJID ,
ld_id_subid  TYPE FIEH_SUBID ,
ld_id_accrule  TYPE FIEH_ACCRULE ,
ld_id_valid  TYPE FIEH_VALID ,
ld_id_msgid  TYPE BAPIRET2-ID ,
ld_id_type  TYPE BAPIRET2-TYPE ,
ld_id_number  TYPE BAPIRET2-NUMBER ,
ld_id_loghandle  TYPE BALLOGHNDL .

ld_id_component = 'Check type of data required'.
ld_id_bukrs = 'Check type of data required'.
ld_id_objectid = 'Check type of data required'.
ld_id_objid = 'Check type of data required'.
ld_id_subid = 'Check type of data required'.
ld_id_accrule = 'Check type of data required'.
ld_id_valid = 'Check type of data required'.

ld_id_msgid = some text here

ld_id_type = some text here

ld_id_number = Check type of data required
ld_id_loghandle = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FIEH_EVENT_EXCEPTION_TRIGGER or its description.