HRIQ_EVOBJINST_INSERT_SINGLE SAP Function module - Evaluation: DB Insert

HRIQ_EVOBJINST_INSERT_SINGLE 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 HRIQ_EVOBJINST_INSERT_SINGLE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: HRPIQ00EVALOBJINST_DB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM HRIQ_EVOBJINST_INSERT_SINGLE - HRIQ EVOBJINST INSERT SINGLE

CALL FUNCTION 'HRIQ_EVOBJINST_INSERT_SINGLE' "Evaluation: DB Insert
  EXPORTING
    is_evoboffer_key =          " piqevoboffer_key  Scheduled Assessments
*   is_evoboffer_attr =         " piqevoboffer_attr  Scheduled Assessment: Attributes
*   it_evoboffer2_attr =        " piqevoboffer2_attr_t  Table Type for PIQEVOBOFFER2_ATTR
*   is_evoboffer3_attr =        " piqevoboffer3_attr
*   iv_create_event = ' '       " piqflag       Indicator
  IMPORTING
    ev_eventid =                " piqexamevent  Exam Event Identification (ID)
  EXCEPTIONS
    KEY_EXISTING = 1            "
    EVENT_NOT_CREATED = 2       "
    .  "  HRIQ_EVOBJINST_INSERT_SINGLE

ABAP code example for Function Module HRIQ_EVOBJINST_INSERT_SINGLE

The ABAP code below is a full code listing to execute function module HRIQ_EVOBJINST_INSERT_SINGLE 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_ev_eventid  
 
 TYPE PIQEXAMEVENT
.


DATA(ld_is_evoboffer_key) = 'Check type of data required'.

DATA(ld_is_evoboffer_attr) = 'Check type of data required'.

DATA(ld_it_evoboffer2_attr) = 'Check type of data required'.

DATA(ld_is_evoboffer3_attr) = 'Check type of data required'.

DATA(ld_iv_create_event) = 'Check type of data required'.
.

CALL FUNCTION 'HRIQ_EVOBJINST_INSERT_SINGLE'
  EXPORTING
    is_evoboffer_key =           ld_is_evoboffer_key
*   is_evoboffer_attr =          ld_is_evoboffer_attr
*   it_evoboffer2_attr =         ld_it_evoboffer2_attr
*   is_evoboffer3_attr =         ld_is_evoboffer3_attr
*   iv_create_event =            ld_iv_create_event
  IMPORTING
    ev_eventid =                 ld_ev_eventid
  EXCEPTIONS
    KEY_EXISTING =               1
    EVENT_NOT_CREATED =          2
    .  "  HRIQ_EVOBJINST_INSERT_SINGLE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_ev_eventid
 
 TYPE PIQEXAMEVENT ,
ld_is_evoboffer_key
 
 TYPE PIQEVOBOFFER_KEY ,
ld_is_evoboffer_attr
 
 TYPE PIQEVOBOFFER_ATTR ,
ld_it_evoboffer2_attr
 
 TYPE PIQEVOBOFFER2_ATTR_T ,
ld_is_evoboffer3_attr
 
 TYPE PIQEVOBOFFER3_ATTR ,
ld_iv_create_event
 
 TYPE PIQFLAG .


ld_is_evoboffer_key = 'Check type of data required'.
ld_is_evoboffer_attr = 'Check type of data required'.
ld_it_evoboffer2_attr = 'Check type of data required'.
ld_is_evoboffer3_attr = 'Check type of data required'.
ld_iv_create_event = 'Check type of data required'.