FTI_LDB_PB_SEL_PL_CF_AND_ATTR SAP Function module - Core Selection Module for Strict Revenues of Parallel Ledgers

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

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

Pattern for FM FTI_LDB_PB_SEL_PL_CF_AND_ATTR - FTI LDB PB SEL PL CF AND ATTR

CALL FUNCTION 'FTI_LDB_PB_SEL_PL_CF_AND_ATTR' "Core Selection Module for Strict Revenues of Parallel Ledgers
  EXPORTING
    im_datin_list =             " ftis_ys_datin_inv  Zeitselektionen
    im_selection =              " rsds_frange_t  Selection Parameters
    im_tab_ccsf =               " ftis_yt_selected_fields  selektierte Ausgabefelder
    im_tabnm =                  " tabname       Table Name
  IMPORTING
    ex_tab_pl_cf =              " vtvdeta_cfm_pl_t  Table Type: Revenue and Cash Flow Information (-> LDB)
    ex_tab_pl_cf_2 =            " vtvdeta_cfm_pl_2_t  Results Table: CFM Revenue List
  CHANGING
    ct_messages =               " bapierr_t     Table Type for Error Handling
    .  "  FTI_LDB_PB_SEL_PL_CF_AND_ATTR

ABAP code example for Function Module FTI_LDB_PB_SEL_PL_CF_AND_ATTR

The ABAP code below is a full code listing to execute function module FTI_LDB_PB_SEL_PL_CF_AND_ATTR 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_ex_tab_pl_cf  
 
 TYPE VTVDETA_CFM_PL_T
,
ld_ex_tab_pl_cf_2  
 
 TYPE VTVDETA_CFM_PL_2_T
.


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

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

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

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

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

CALL FUNCTION 'FTI_LDB_PB_SEL_PL_CF_AND_ATTR'
  EXPORTING
    im_datin_list =              ld_im_datin_list
    im_selection =               ld_im_selection
    im_tab_ccsf =                ld_im_tab_ccsf
    im_tabnm =                   ld_im_tabnm
  IMPORTING
    ex_tab_pl_cf =               ld_ex_tab_pl_cf
    ex_tab_pl_cf_2 =             ld_ex_tab_pl_cf_2
  CHANGING
    ct_messages =                ld_ct_messages
    .  "  FTI_LDB_PB_SEL_PL_CF_AND_ATTR

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_ct_messages
 
 TYPE BAPIERR_T ,
ld_ex_tab_pl_cf
 
 TYPE VTVDETA_CFM_PL_T ,
ld_im_datin_list
 
 TYPE FTIS_YS_DATIN_INV ,
ld_ex_tab_pl_cf_2
 
 TYPE VTVDETA_CFM_PL_2_T ,
ld_im_selection
 
 TYPE RSDS_FRANGE_T ,
ld_im_tab_ccsf
 
 TYPE FTIS_YT_SELECTED_FIELDS ,
ld_im_tabnm
 
 TYPE TABNAME .


ld_ct_messages = 'Check type of data required'.
ld_im_datin_list = 'Check type of data required'.
ld_im_selection = 'Check type of data required'.
ld_im_tab_ccsf = 'Check type of data required'.
ld_im_tabnm = 'Check type of data required'.