QSS7_GET_STEPS_WITH_DOC SAP Function module

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

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

Pattern for FM QSS7_GET_STEPS_WITH_DOC - QSS7 GET STEPS WITH DOC

CALL FUNCTION 'QSS7_GET_STEPS_WITH_DOC' "
  EXPORTING
    iv_sign_id =                " qamr-sign_id  Digital Signature: Signature Number as GUID with 22 Chars.
  IMPORTING
    et_sign_verify_step_tab =   " sign_verify_step_tab  Digital Signature: Data on Signature Process
    ev_doc_txt =                " string
    ev_doc_bin =                " xstring
    ev_doc_type =               " ssftype       SSF Type Indicator
* TABLES
*   et_qss7_ts_sign_verify_step =   " qss7_ts_sign_verify_step  Digital Signature: Verification of Data
  EXCEPTIONS
    FAILED = 1                  "
    .  "  QSS7_GET_STEPS_WITH_DOC

ABAP code example for Function Module QSS7_GET_STEPS_WITH_DOC

The ABAP code below is a full code listing to execute function module QSS7_GET_STEPS_WITH_DOC 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_et_sign_verify_step_tab  
 
 TYPE SIGN_VERIFY_STEP_TAB
,
ld_ev_doc_txt  
 
 TYPE STRING
,
ld_ev_doc_bin  
 
 TYPE XSTRING
,
ld_ev_doc_type  
 
 TYPE SSFTYPE
,
it_et_qss7_ts_sign_verify_step  
 
 TYPE STANDARD TABLE OF QSS7_TS_SIGN_VERIFY_STEP,"TABLES PARAM
wa_et_qss7_ts_sign_verify_step
 
 LIKE LINE OF it_et_qss7_ts_sign_verify_step
.

 

SELECT single SIGN_ID 
  FROM QAMR 
  INTO @DATA(ld_iv_sign_id).

 

"populate fields of struture and append to itab
append wa_et_qss7_ts_sign_verify_step to it_et_qss7_ts_sign_verify_step.
.

CALL FUNCTION 'QSS7_GET_STEPS_WITH_DOC'
  EXPORTING
    iv_sign_id =                 ld_iv_sign_id
  IMPORTING
    et_sign_verify_step_tab =    ld_et_sign_verify_step_tab
    ev_doc_txt =                 ld_ev_doc_txt
    ev_doc_bin =                 ld_ev_doc_bin
    ev_doc_type =                ld_ev_doc_type
* TABLES
*   et_qss7_ts_sign_verify_step =    it_et_qss7_ts_sign_verify_step
  EXCEPTIONS
    FAILED =                     1
    .  "  QSS7_GET_STEPS_WITH_DOC

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_et_sign_verify_step_tab
 
 TYPE SIGN_VERIFY_STEP_TAB ,
ld_iv_sign_id
 
 TYPE QAMR-SIGN_ID ,
it_et_qss7_ts_sign_verify_step
 
 TYPE STANDARD TABLE OF QSS7_TS_SIGN_VERIFY_STEP ,
wa_et_qss7_ts_sign_verify_step
 
 LIKE LINE OF it_et_qss7_ts_sign_verify_step,
ld_ev_doc_txt
 
 TYPE STRING ,
ld_ev_doc_bin
 
 TYPE XSTRING ,
ld_ev_doc_type
 
 TYPE SSFTYPE .



SELECT single SIGN_ID 
  FROM QAMR 
  INTO ld_iv_sign_id.
 

"populate fields of struture and append to itab
append wa_et_qss7_ts_sign_verify_step to it_et_qss7_ts_sign_verify_step.