SAP Function Modules
SUGQ_GET_PATCH_SEQUENCE SAP Function module
SUGQ_GET_PATCH_SEQUENCE 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 SUGQ_GET_PATCH_SEQUENCE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
SUGQ
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM SUGQ_GET_PATCH_SEQUENCE - SUGQ GET PATCH SEQUENCE
CALL FUNCTION 'SUGQ_GET_PATCH_SEQUENCE' "
* EXPORTING
* iv_func = " gsugi_pa-w_istatus Single-Character Flag
IMPORTING
ev_retcode = " gsugi_pa-nr_conv Return Code
ev_msgtext = " gsugi_pa-rcmessage Message Text
TABLES
it_ncvers_req = " ncvers_i Table of Software Components in the Shadow Repository
it_patchlist = " patchlist Request List for Queue Calculator/Missing Support Packages
ot_ncvers = " ncvers_i Table of Software Components in the Shadow Repository
ot_patch_sequence = " patchqseq
ot_patch_missing = " patchlist Request List for Queue Calculator/Missing Support Packages
. " SUGQ_GET_PATCH_SEQUENCE
ABAP code example for Function Module SUGQ_GET_PATCH_SEQUENCE
The ABAP code below is a full code listing to execute function module SUGQ_GET_PATCH_SEQUENCE 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).
| ld_ev_retcode | TYPE GSUGI_PA-NR_CONV , |
| ld_ev_msgtext | TYPE GSUGI_PA-RCMESSAGE , |
| it_it_ncvers_req | TYPE STANDARD TABLE OF NCVERS_I,"TABLES PARAM |
| wa_it_ncvers_req | LIKE LINE OF it_it_ncvers_req , |
| it_it_patchlist | TYPE STANDARD TABLE OF PATCHLIST,"TABLES PARAM |
| wa_it_patchlist | LIKE LINE OF it_it_patchlist , |
| it_ot_ncvers | TYPE STANDARD TABLE OF NCVERS_I,"TABLES PARAM |
| wa_ot_ncvers | LIKE LINE OF it_ot_ncvers , |
| it_ot_patch_sequence | TYPE STANDARD TABLE OF PATCHQSEQ,"TABLES PARAM |
| wa_ot_patch_sequence | LIKE LINE OF it_ot_patch_sequence , |
| it_ot_patch_missing | TYPE STANDARD TABLE OF PATCHLIST,"TABLES PARAM |
| wa_ot_patch_missing | LIKE LINE OF it_ot_patch_missing . |
DATA(ld_iv_func) = some text here
"populate fields of struture and append to itab
append wa_it_ncvers_req to it_it_ncvers_req.
"populate fields of struture and append to itab
append wa_it_patchlist to it_it_patchlist.
"populate fields of struture and append to itab
append wa_ot_ncvers to it_ot_ncvers.
"populate fields of struture and append to itab
append wa_ot_patch_sequence to it_ot_patch_sequence.
"populate fields of struture and append to itab
append wa_ot_patch_missing to it_ot_patch_missing. . CALL FUNCTION 'SUGQ_GET_PATCH_SEQUENCE' * EXPORTING * iv_func = ld_iv_func IMPORTING ev_retcode = ld_ev_retcode ev_msgtext = ld_ev_msgtext TABLES it_ncvers_req = it_it_ncvers_req it_patchlist = it_it_patchlist ot_ncvers = it_ot_ncvers ot_patch_sequence = it_ot_patch_sequence ot_patch_missing = it_ot_patch_missing . " SUGQ_GET_PATCH_SEQUENCE
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_ev_retcode | TYPE GSUGI_PA-NR_CONV , |
| ld_iv_func | TYPE GSUGI_PA-W_ISTATUS , |
| it_it_ncvers_req | TYPE STANDARD TABLE OF NCVERS_I , |
| wa_it_ncvers_req | LIKE LINE OF it_it_ncvers_req, |
| ld_ev_msgtext | TYPE GSUGI_PA-RCMESSAGE , |
| it_it_patchlist | TYPE STANDARD TABLE OF PATCHLIST , |
| wa_it_patchlist | LIKE LINE OF it_it_patchlist, |
| it_ot_ncvers | TYPE STANDARD TABLE OF NCVERS_I , |
| wa_ot_ncvers | LIKE LINE OF it_ot_ncvers, |
| it_ot_patch_sequence | TYPE STANDARD TABLE OF PATCHQSEQ , |
| wa_ot_patch_sequence | LIKE LINE OF it_ot_patch_sequence, |
| it_ot_patch_missing | TYPE STANDARD TABLE OF PATCHLIST , |
| wa_ot_patch_missing | LIKE LINE OF it_ot_patch_missing. |
ld_iv_func = some text here
"populate fields of struture and append to itab
append wa_it_ncvers_req to it_it_ncvers_req.
"populate fields of struture and append to itab
append wa_it_patchlist to it_it_patchlist.
"populate fields of struture and append to itab
append wa_ot_ncvers to it_ot_ncvers.
"populate fields of struture and append to itab
append wa_ot_patch_sequence to it_ot_patch_sequence.
"populate fields of struture and append to itab
append wa_ot_patch_missing to it_ot_patch_missing.
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 SUGQ_GET_PATCH_SEQUENCE or its description.