XBLNR_BUILD_AND_SPLIT_TR SAP Function module

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

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

Pattern for FM XBLNR_BUILD_AND_SPLIT_TR - XBLNR BUILD AND SPLIT TR

CALL FUNCTION 'XBLNR_BUILD_AND_SPLIT_TR' "
  EXPORTING
    i_bukrs =                   " t001-bukrs
*   i_build =                   " char1
*   i_rgtno =                   " idcn_loma-rgtno
*   i_invno =                   " idcn_loma-invfr
*   i_xblnr =                   " bkpf-xblnr
*   i_invtp =                   " idcn_loma-invtp
*   i_pages =                   " ssfcrespd
*   itab_idcn_odn_tr =          " tab_idcn_odn_tr
  IMPORTING
    e_rgtno =                   " idcn_loma-rgtno
    e_invno =                   " idcn_loma-invfr
    e_xblnr =                   " bkpf-xblnr
    e_invtp =                   " idcn_loma-invtp
    etab_idcn_odn_tr =          " tab_idcn_odn_tr
  EXCEPTIONS
    PARAMETER_WRONG = 1         "
    NOT_FOUND = 2               "
    XBLNR_FORMAT_WRONG = 3      "
    .  "  XBLNR_BUILD_AND_SPLIT_TR

ABAP code example for Function Module XBLNR_BUILD_AND_SPLIT_TR

The ABAP code below is a full code listing to execute function module XBLNR_BUILD_AND_SPLIT_TR 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_e_rgtno  
 
 TYPE IDCN_LOMA-RGTNO
,
ld_e_invno  
 
 TYPE IDCN_LOMA-INVFR
,
ld_e_xblnr  
 
 TYPE BKPF-XBLNR
,
ld_e_invtp  
 
 TYPE IDCN_LOMA-INVTP
,
ld_etab_idcn_odn_tr  
 
 TYPE TAB_IDCN_ODN_TR
.

 

SELECT single BUKRS 
  FROM T001 
  INTO @DATA(ld_i_bukrs).


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

SELECT single RGTNO 
  FROM IDCN_LOMA 
  INTO @DATA(ld_i_rgtno).

 

SELECT single INVFR 
  FROM IDCN_LOMA 
  INTO @DATA(ld_i_invno).

 

SELECT single XBLNR 
  FROM BKPF 
  INTO @DATA(ld_i_xblnr).

 

SELECT single INVTP 
  FROM IDCN_LOMA 
  INTO @DATA(ld_i_invtp).


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

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

CALL FUNCTION 'XBLNR_BUILD_AND_SPLIT_TR'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
*   i_build =                    ld_i_build
*   i_rgtno =                    ld_i_rgtno
*   i_invno =                    ld_i_invno
*   i_xblnr =                    ld_i_xblnr
*   i_invtp =                    ld_i_invtp
*   i_pages =                    ld_i_pages
*   itab_idcn_odn_tr =           ld_itab_idcn_odn_tr
  IMPORTING
    e_rgtno =                    ld_e_rgtno
    e_invno =                    ld_e_invno
    e_xblnr =                    ld_e_xblnr
    e_invtp =                    ld_e_invtp
    etab_idcn_odn_tr =           ld_etab_idcn_odn_tr
  EXCEPTIONS
    PARAMETER_WRONG =            1
    NOT_FOUND =                  2
    XBLNR_FORMAT_WRONG =         3
    .  "  XBLNR_BUILD_AND_SPLIT_TR

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_e_rgtno
 
 TYPE IDCN_LOMA-RGTNO ,
ld_i_bukrs
 
 TYPE T001-BUKRS ,
ld_e_invno
 
 TYPE IDCN_LOMA-INVFR ,
ld_i_build
 
 TYPE CHAR1 ,
ld_e_xblnr
 
 TYPE BKPF-XBLNR ,
ld_i_rgtno
 
 TYPE IDCN_LOMA-RGTNO ,
ld_e_invtp
 
 TYPE IDCN_LOMA-INVTP ,
ld_i_invno
 
 TYPE IDCN_LOMA-INVFR ,
ld_etab_idcn_odn_tr
 
 TYPE TAB_IDCN_ODN_TR ,
ld_i_xblnr
 
 TYPE BKPF-XBLNR ,
ld_i_invtp
 
 TYPE IDCN_LOMA-INVTP ,
ld_i_pages
 
 TYPE SSFCRESPD ,
ld_itab_idcn_odn_tr
 
 TYPE TAB_IDCN_ODN_TR .



SELECT single BUKRS 
  FROM T001 
  INTO ld_i_bukrs.

ld_i_build = 'Check type of data required'.

SELECT single RGTNO 
  FROM IDCN_LOMA 
  INTO ld_i_rgtno.


SELECT single INVFR 
  FROM IDCN_LOMA 
  INTO ld_i_invno.


SELECT single XBLNR 
  FROM BKPF 
  INTO ld_i_xblnr.


SELECT single INVTP 
  FROM IDCN_LOMA 
  INTO ld_i_invtp.

ld_i_pages = 'Check type of data required'.
ld_itab_idcn_odn_tr = 'Check type of data required'.