CBGL_PRAPI_PRTREQBODY_UNLOCK SAP Function module

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

Associated Function Group: CBGL_PRINT_REQUEST_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CBGL_PRAPI_PRTREQBODY_UNLOCK - CBGL PRAPI PRTREQBODY UNLOCK

CALL FUNCTION 'CBGL_PRAPI_PRTREQBODY_UNLOCK' "
  EXPORTING
    it_prtreq_id =              " ccgld_prtreq_id
*   iv_flg_appl_log = 'X'       " as4flag
  CHANGING
    cv_flg_warning =            " as4flag
    cv_flg_error =              " as4flag
    ct_messages =               " bal_t_msg
  EXCEPTIONS
    OBJECT_CREATION_FAILED = 1  "
    .  "  CBGL_PRAPI_PRTREQBODY_UNLOCK

ABAP code example for Function Module CBGL_PRAPI_PRTREQBODY_UNLOCK

The ABAP code below is a full code listing to execute function module CBGL_PRAPI_PRTREQBODY_UNLOCK 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_cv_flg_warning) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'CBGL_PRAPI_PRTREQBODY_UNLOCK'
  EXPORTING
    it_prtreq_id =               ld_it_prtreq_id
*   iv_flg_appl_log =            ld_iv_flg_appl_log
  CHANGING
    cv_flg_warning =             ld_cv_flg_warning
    cv_flg_error =               ld_cv_flg_error
    ct_messages =                ld_ct_messages
  EXCEPTIONS
    OBJECT_CREATION_FAILED =     1
    .  "  CBGL_PRAPI_PRTREQBODY_UNLOCK

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_cv_flg_warning
 
 TYPE AS4FLAG ,
ld_it_prtreq_id
 
 TYPE CCGLD_PRTREQ_ID ,
ld_cv_flg_error
 
 TYPE AS4FLAG ,
ld_iv_flg_appl_log
 
 TYPE AS4FLAG ,
ld_ct_messages
 
 TYPE BAL_T_MSG .


ld_cv_flg_warning = 'Check type of data required'.
ld_it_prtreq_id = 'Check type of data required'.
ld_cv_flg_error = 'Check type of data required'.
ld_iv_flg_appl_log = 'Check type of data required'.
ld_ct_messages = 'Check type of data required'.