HRNQF_WRITE_OUTC_DATA SAP Function module - Write NQF Outcome data to infotypes

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

Associated Function Group: HRNQFZA_DATA
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM HRNQF_WRITE_OUTC_DATA - HRNQF WRITE OUTC DATA

CALL FUNCTION 'HRNQF_WRITE_OUTC_DATA' "Write NQF Outcome data to infotypes
  EXPORTING
    plvar =                     " hrp1000-plvar
    otype =                     " hrp1000-otype
    objid =                     " hrp1000-objid
*   begda = '19000101'          " hrp1000-begda
*   endda = '99991231'          " hrp1000-endda
    infty1632 =                 " nqfoutc       Fields for Outcome data
  EXCEPTIONS
    NO_AUTHORITY = 1            "
    OBJECT_NOT_FOUND = 2        "
    INVALID_DATE = 3            "
    ERROR_DURING_INSERT = 4     "
    UNDEFINED = 5               "
    .  "  HRNQF_WRITE_OUTC_DATA

ABAP code example for Function Module HRNQF_WRITE_OUTC_DATA

The ABAP code below is a full code listing to execute function module HRNQF_WRITE_OUTC_DATA 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).

 

SELECT single PLVAR 
  FROM HRP1000 
  INTO @DATA(ld_plvar).

 

SELECT single OTYPE 
  FROM HRP1000 
  INTO @DATA(ld_otype).

 

SELECT single OBJID 
  FROM HRP1000 
  INTO @DATA(ld_objid).

 

SELECT single BEGDA 
  FROM HRP1000 
  INTO @DATA(ld_begda).

 

SELECT single ENDDA 
  FROM HRP1000 
  INTO @DATA(ld_endda).


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

CALL FUNCTION 'HRNQF_WRITE_OUTC_DATA'
  EXPORTING
    plvar =                      ld_plvar
    otype =                      ld_otype
    objid =                      ld_objid
*   begda =                      ld_begda
*   endda =                      ld_endda
    infty1632 =                  ld_infty1632
  EXCEPTIONS
    NO_AUTHORITY =               1
    OBJECT_NOT_FOUND =           2
    INVALID_DATE =               3
    ERROR_DURING_INSERT =        4
    UNDEFINED =                  5
    .  "  HRNQF_WRITE_OUTC_DATA

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_plvar
 
 TYPE HRP1000-PLVAR ,
ld_otype
 
 TYPE HRP1000-OTYPE ,
ld_objid
 
 TYPE HRP1000-OBJID ,
ld_begda
 
 TYPE HRP1000-BEGDA ,
ld_endda
 
 TYPE HRP1000-ENDDA ,
ld_infty1632
 
 TYPE NQFOUTC .



SELECT single PLVAR 
  FROM HRP1000 
  INTO ld_plvar.


SELECT single OTYPE 
  FROM HRP1000 
  INTO ld_otype.


SELECT single OBJID 
  FROM HRP1000 
  INTO ld_objid.


SELECT single BEGDA 
  FROM HRP1000 
  INTO ld_begda.


SELECT single ENDDA 
  FROM HRP1000 
  INTO ld_endda.

ld_infty1632 = 'Check type of data required'.