SAP Function Modules

FINB_TR_CC_EXIT_AFTER_COPY SAP Function module







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

Associated Function Group: FINB_TR_CC
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FINB_TR_CC_EXIT_AFTER_COPY - FINB TR CC EXIT AFTER COPY





CALL FUNCTION 'FINB_TR_CC_EXIT_AFTER_COPY' "
  EXPORTING
    test =                      " flag          General Indicator
    clii =                      " cccliindep    Cross-Client Tables
    appl =                      " ccappldata    Select application data also ('X')
    modus =                     " ccmodus       Mode for client transport
    gt_e071 =                   " tr_objects    Objects
    gt_e071k =                  " tr_keys       Table Keys
*   offline =                   " flag
*   precheck =                  " flag
*   no_local_attributes = SPACE  " flag
*   io_msg =                    " cl_finb_tr_msg_collector  Message Collector - Tools and Enhancements
  IMPORTING
    rcod =                      " sysubrc       Return Value, Return Value after ABAP Statements
    et_msg =                    " finb_tr_messages  Table of Messages
    .  "  FINB_TR_CC_EXIT_AFTER_COPY

ABAP code example for Function Module FINB_TR_CC_EXIT_AFTER_COPY





The ABAP code below is a full code listing to execute function module FINB_TR_CC_EXIT_AFTER_COPY 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_rcod  TYPE SYSUBRC ,
ld_et_msg  TYPE FINB_TR_MESSAGES .

DATA(ld_test) = 'Check type of data required'.
DATA(ld_clii) = 'Check type of data required'.
DATA(ld_appl) = 'Check type of data required'.
DATA(ld_modus) = 'Check type of data required'.
DATA(ld_gt_e071) = 'Check type of data required'.
DATA(ld_gt_e071k) = 'Check type of data required'.
DATA(ld_offline) = 'Check type of data required'.
DATA(ld_precheck) = 'Check type of data required'.
DATA(ld_no_local_attributes) = 'Check type of data required'.
DATA(ld_io_msg) = 'Check type of data required'. . CALL FUNCTION 'FINB_TR_CC_EXIT_AFTER_COPY' EXPORTING test = ld_test clii = ld_clii appl = ld_appl modus = ld_modus gt_e071 = ld_gt_e071 gt_e071k = ld_gt_e071k * offline = ld_offline * precheck = ld_precheck * no_local_attributes = ld_no_local_attributes * io_msg = ld_io_msg IMPORTING rcod = ld_rcod et_msg = ld_et_msg . " FINB_TR_CC_EXIT_AFTER_COPY
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_rcod  TYPE SYSUBRC ,
ld_test  TYPE FLAG ,
ld_et_msg  TYPE FINB_TR_MESSAGES ,
ld_clii  TYPE CCCLIINDEP ,
ld_appl  TYPE CCAPPLDATA ,
ld_modus  TYPE CCMODUS ,
ld_gt_e071  TYPE TR_OBJECTS ,
ld_gt_e071k  TYPE TR_KEYS ,
ld_offline  TYPE FLAG ,
ld_precheck  TYPE FLAG ,
ld_no_local_attributes  TYPE FLAG ,
ld_io_msg  TYPE CL_FINB_TR_MSG_COLLECTOR .

ld_test = 'Check type of data required'.
ld_clii = 'Check type of data required'.
ld_appl = 'Check type of data required'.
ld_modus = 'Check type of data required'.
ld_gt_e071 = 'Check type of data required'.
ld_gt_e071k = 'Check type of data required'.
ld_offline = 'Check type of data required'.
ld_precheck = 'Check type of data required'.
ld_no_local_attributes = 'Check type of data required'.
ld_io_msg = 'Check type of data required'.

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 FINB_TR_CC_EXIT_AFTER_COPY or its description.