FIQA_GET_SIGNATURES_FOR_PDF_1 SAP Function module - Qatar extractor for PDF form signatures

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

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

Pattern for FM FIQA_GET_SIGNATURES_FOR_PDF_1 - FIQA GET SIGNATURES FOR PDF 1

CALL FUNCTION 'FIQA_GET_SIGNATURES_FOR_PDF_1' "Qatar extractor for PDF form signatures
  EXPORTING
    iv_bukrs =                  " bukrs         Company Code
    iv_form_name =              " fpwbformname  PDF-Based Forms: Form Name
    iv_lang = SY-LANGU          " spras         Language Key
*   iv_sign_id =                " char10        Character Field Length = 10
  IMPORTING
    et_sign_tab =               " fiqa_t_roletxt_sign_1  Roles text for Qatar PDF Form Signatures
    .  "  FIQA_GET_SIGNATURES_FOR_PDF_1

ABAP code example for Function Module FIQA_GET_SIGNATURES_FOR_PDF_1

The ABAP code below is a full code listing to execute function module FIQA_GET_SIGNATURES_FOR_PDF_1 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_tab  
 
 TYPE FIQA_T_ROLETXT_SIGN_1
.


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

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

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

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

CALL FUNCTION 'FIQA_GET_SIGNATURES_FOR_PDF_1'
  EXPORTING
    iv_bukrs =                   ld_iv_bukrs
    iv_form_name =               ld_iv_form_name
    iv_lang =                    ld_iv_lang
*   iv_sign_id =                 ld_iv_sign_id
  IMPORTING
    et_sign_tab =                ld_et_sign_tab
    .  "  FIQA_GET_SIGNATURES_FOR_PDF_1

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_et_sign_tab
 
 TYPE FIQA_T_ROLETXT_SIGN_1 ,
ld_iv_bukrs
 
 TYPE BUKRS ,
ld_iv_form_name
 
 TYPE FPWBFORMNAME ,
ld_iv_lang
 
 TYPE SPRAS ,
ld_iv_sign_id
 
 TYPE CHAR10 .


ld_iv_bukrs = 'Check type of data required'.
ld_iv_form_name = 'Check type of data required'.
ld_iv_lang = 'Check type of data required'.
ld_iv_sign_id = 'Check type of data required'.