SAP Function Modules

HRIQ_TRANSCRIPT_GET SAP Function module - RFC: Read Student's Transcripts







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

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


Pattern for FM HRIQ_TRANSCRIPT_GET - HRIQ TRANSCRIPT GET





CALL FUNCTION 'HRIQ_TRANSCRIPT_GET' "RFC: Read Student's Transcripts
  EXPORTING
*   planversion =               " plvar         Plan Version
    objectid =                  " objektid      Object ID
*   transtype =                 " piqtrtranstype  Transcript Category
*   only_fa_rel_types = ' '     " piq_farelevant
*   transstatus =               " piqrepstate   Transcript Status
*   read_texts = ' '            " bapistudent_readtexts  Indicator: Also Read Texts
*   language_iso =              " bapi_laiso-langu_iso  Language According to ISO 639
*   language =                  " bapi_laiso-langu  Language Key
  IMPORTING
    return_code =               " sy-subrc      Return Value, Return Value after ABAP Statements
* TABLES
*   transcript_header =         " piqtrheader_ext  External Transcript (Header Data)
*   transcript_headert =        " piqtrheader_ext_txt  External Academic Work (Header Data with Text Fields)
*   return =                    " bapiret2      Return Parameter(s)
    .  "  HRIQ_TRANSCRIPT_GET

ABAP code example for Function Module HRIQ_TRANSCRIPT_GET





The ABAP code below is a full code listing to execute function module HRIQ_TRANSCRIPT_GET 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_return_code  TYPE SY-SUBRC ,
it_transcript_header  TYPE STANDARD TABLE OF PIQTRHEADER_EXT,"TABLES PARAM
wa_transcript_header  LIKE LINE OF it_transcript_header ,
it_transcript_headert  TYPE STANDARD TABLE OF PIQTRHEADER_EXT_TXT,"TABLES PARAM
wa_transcript_headert  LIKE LINE OF it_transcript_headert ,
it_return  TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return  LIKE LINE OF it_return .

DATA(ld_planversion) = 'Check type of data required'.
DATA(ld_objectid) = 'Check type of data required'.
DATA(ld_transtype) = 'Check type of data required'.
DATA(ld_only_fa_rel_types) = 'Check type of data required'.
DATA(ld_transstatus) = 'Check type of data required'.
DATA(ld_read_texts) = 'Check type of data required'.

DATA(ld_language_iso) = some text here

DATA(ld_language) = Check type of data required

"populate fields of struture and append to itab
append wa_transcript_header to it_transcript_header.

"populate fields of struture and append to itab
append wa_transcript_headert to it_transcript_headert.

"populate fields of struture and append to itab
append wa_return to it_return. . CALL FUNCTION 'HRIQ_TRANSCRIPT_GET' EXPORTING * planversion = ld_planversion objectid = ld_objectid * transtype = ld_transtype * only_fa_rel_types = ld_only_fa_rel_types * transstatus = ld_transstatus * read_texts = ld_read_texts * language_iso = ld_language_iso * language = ld_language IMPORTING return_code = ld_return_code * TABLES * transcript_header = it_transcript_header * transcript_headert = it_transcript_headert * return = it_return . " HRIQ_TRANSCRIPT_GET
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_return_code  TYPE SY-SUBRC ,
ld_planversion  TYPE PLVAR ,
it_transcript_header  TYPE STANDARD TABLE OF PIQTRHEADER_EXT ,
wa_transcript_header  LIKE LINE OF it_transcript_header,
ld_objectid  TYPE OBJEKTID ,
it_transcript_headert  TYPE STANDARD TABLE OF PIQTRHEADER_EXT_TXT ,
wa_transcript_headert  LIKE LINE OF it_transcript_headert,
ld_transtype  TYPE PIQTRTRANSTYPE ,
it_return  TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return  LIKE LINE OF it_return,
ld_only_fa_rel_types  TYPE PIQ_FARELEVANT ,
ld_transstatus  TYPE PIQREPSTATE ,
ld_read_texts  TYPE BAPISTUDENT_READTEXTS ,
ld_language_iso  TYPE BAPI_LAISO-LANGU_ISO ,
ld_language  TYPE BAPI_LAISO-LANGU .

ld_planversion = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_transcript_header to it_transcript_header.
ld_objectid = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_transcript_headert to it_transcript_headert.
ld_transtype = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_return to it_return.
ld_only_fa_rel_types = 'Check type of data required'.
ld_transstatus = 'Check type of data required'.
ld_read_texts = 'Check type of data required'.

ld_language_iso = some text here

ld_language = 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 HRIQ_TRANSCRIPT_GET or its description.