TB_DATAFEED_CHECK_LENGTH SAP Function module - Datafeed: Check Input Length as per DDIC Rule

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

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

Pattern for FM TB_DATAFEED_CHECK_LENGTH - TB DATAFEED CHECK LENGTH

CALL FUNCTION 'TB_DATAFEED_CHECK_LENGTH' "Datafeed: Check Input Length as per DDIC Rule
  EXPORTING
    value =                     " c
    tabname =                   " dcobjdef-name
    fieldname =                 " dfies-lfieldname
  CHANGING
    sstats =                    " vtb_market-sstats
    error_flag =                " vtb_market-rupdhist
    error_msg =                 " vtb_market-error
    .  "  TB_DATAFEED_CHECK_LENGTH

ABAP code example for Function Module TB_DATAFEED_CHECK_LENGTH

The ABAP code below is a full code listing to execute function module TB_DATAFEED_CHECK_LENGTH 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).

 

SELECT single SSTATS 
  FROM VTB_MARKET 
  INTO @DATA(ld_sstats).

 

SELECT single RUPDHIST 
  FROM VTB_MARKET 
  INTO @DATA(ld_error_flag).

 

SELECT single ERROR 
  FROM VTB_MARKET 
  INTO @DATA(ld_error_msg).


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


DATA(ld_tabname) = some text here


DATA(ld_fieldname) = some text here
.

CALL FUNCTION 'TB_DATAFEED_CHECK_LENGTH'
  EXPORTING
    value =                      ld_value
    tabname =                    ld_tabname
    fieldname =                  ld_fieldname
  CHANGING
    sstats =                     ld_sstats
    error_flag =                 ld_error_flag
    error_msg =                  ld_error_msg
    .  "  TB_DATAFEED_CHECK_LENGTH

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_sstats
 
 TYPE VTB_MARKET-SSTATS ,
ld_value
 
 TYPE C ,
ld_error_flag
 
 TYPE VTB_MARKET-RUPDHIST ,
ld_tabname
 
 TYPE DCOBJDEF-NAME ,
ld_error_msg
 
 TYPE VTB_MARKET-ERROR ,
ld_fieldname
 
 TYPE DFIES-LFIELDNAME .



SELECT single SSTATS 
  FROM VTB_MARKET 
  INTO ld_sstats.

ld_value = 'Check type of data required'.

SELECT single RUPDHIST 
  FROM VTB_MARKET 
  INTO ld_error_flag.


ld_tabname = some text here

SELECT single ERROR 
  FROM VTB_MARKET 
  INTO ld_error_msg.


ld_fieldname = some text here