SPC_PERF_GET_PROTOCOL SAP Function module - Retrieve Protocol (using Tables Parameter)

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

Associated Function Group: SPC_DEPRECATED_PERF
Released Date: Not Released
Processing type: Remote-Enabled JAVA Module

Pattern for FM SPC_PERF_GET_PROTOCOL - SPC PERF GET PROTOCOL

CALL FUNCTION 'SPC_PERF_GET_PROTOCOL' "Retrieve Protocol (using Tables Parameter)
  EXPORTING
    iv_document_id =            " prct_pridoc_guid  Pricing Document GUID
    it_item_id =                " prct_item_no_t  List of Item Numbers
    iv_for_document =           " xfeld         Checkbox
    iv_all_items =              " xfeld         Checkbox
  IMPORTING
    es_profile =                " prit_profile  Profile of the IPC call
  TABLES
    et_protocol =               " prit_message_t  Message
    .  "  SPC_PERF_GET_PROTOCOL

ABAP code example for Function Module SPC_PERF_GET_PROTOCOL

The ABAP code below is a full code listing to execute function module SPC_PERF_GET_PROTOCOL 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_es_profile  
 
 TYPE PRIT_PROFILE
,
it_et_protocol  
 
 TYPE STANDARD TABLE OF PRIT_MESSAGE_T,"TABLES PARAM
wa_et_protocol
 
 LIKE LINE OF it_et_protocol
.


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

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

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

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

"populate fields of struture and append to itab
append wa_et_protocol to it_et_protocol.
.

CALL FUNCTION 'SPC_PERF_GET_PROTOCOL'
  EXPORTING
    iv_document_id =             ld_iv_document_id
    it_item_id =                 ld_it_item_id
    iv_for_document =            ld_iv_for_document
    iv_all_items =               ld_iv_all_items
  IMPORTING
    es_profile =                 ld_es_profile
  TABLES
    et_protocol =                it_et_protocol
    .  "  SPC_PERF_GET_PROTOCOL

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_es_profile
 
 TYPE PRIT_PROFILE ,
ld_iv_document_id
 
 TYPE PRCT_PRIDOC_GUID ,
it_et_protocol
 
 TYPE STANDARD TABLE OF PRIT_MESSAGE_T ,
wa_et_protocol
 
 LIKE LINE OF it_et_protocol,
ld_it_item_id
 
 TYPE PRCT_ITEM_NO_T ,
ld_iv_for_document
 
 TYPE XFELD ,
ld_iv_all_items
 
 TYPE XFELD .


ld_iv_document_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_protocol to it_et_protocol.
ld_it_item_id = 'Check type of data required'.
ld_iv_for_document = 'Check type of data required'.
ld_iv_all_items = 'Check type of data required'.