SAP EXT_BELNR_TRAFO Function Module for
EXT_BELNR_TRAFO is a standard ext belnr trafo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ext belnr trafo FM, simply by entering the name EXT_BELNR_TRAFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVI4
Program Name: SAPLFVI4
Main Program: SAPLFVI4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXT_BELNR_TRAFO pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'EXT_BELNR_TRAFO'".
EXPORTING
* FLG_USER_CHG = 'X' "
* IMP_DATE = SY-DATUM "
* IMP_EXTBELEGNR = ' ' "
* IMP_OBJECT = 'FVVI_SOID' "
* IMP_VISLID = ' ' "
* NR_RANGE_NR = '01' "
IMPORTING
EXP_EXTBELNR = "
EXP_VISLID = "
FLG_DB_ENTRY = "
EXCEPTIONS
INTERVAL_NOT_FOUND = 1 NO_ENTRY = 2 NUMBER_RANGE_NOT_INTERN = 3 OBJECT_NOT_FOUND = 4 QUANTTITY_IS_0 = 5
IMPORTING Parameters details for EXT_BELNR_TRAFO
FLG_USER_CHG -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IMP_DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IMP_EXTBELEGNR -
Data type: BKPF-XBLNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IMP_OBJECT -
Data type: INRI-OBJECTDefault: 'FVVI_SOID'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IMP_VISLID -
Data type: VISLIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NR_RANGE_NR -
Data type: INRI-NRRANGENRDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXT_BELNR_TRAFO
EXP_EXTBELNR -
Data type: BKPF-XBLNROptional: No
Call by Reference: No ( called with pass by value option)
EXP_VISLID -
Data type: VISLIDOptional: No
Call by Reference: No ( called with pass by value option)
FLG_DB_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERVAL_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NUMBER_RANGE_NOT_INTERN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
QUANTTITY_IS_0 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXT_BELNR_TRAFO Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_exp_extbelnr | TYPE BKPF-XBLNR, " | |||
| lv_flg_user_chg | TYPE BKPF, " 'X' | |||
| lv_interval_not_found | TYPE BKPF, " | |||
| lv_imp_date | TYPE SY-DATUM, " SY-DATUM | |||
| lv_no_entry | TYPE SY, " | |||
| lv_exp_vislid | TYPE VISLID, " | |||
| lv_flg_db_entry | TYPE VISLID, " | |||
| lv_imp_extbelegnr | TYPE BKPF-XBLNR, " SPACE | |||
| lv_number_range_not_intern | TYPE BKPF, " | |||
| lv_imp_object | TYPE INRI-OBJECT, " 'FVVI_SOID' | |||
| lv_object_not_found | TYPE INRI, " | |||
| lv_imp_vislid | TYPE VISLID, " SPACE | |||
| lv_quanttity_is_0 | TYPE VISLID, " | |||
| lv_nr_range_nr | TYPE INRI-NRRANGENR. " '01' |
|   CALL FUNCTION 'EXT_BELNR_TRAFO' " |
| EXPORTING | ||
| FLG_USER_CHG | = lv_flg_user_chg | |
| IMP_DATE | = lv_imp_date | |
| IMP_EXTBELEGNR | = lv_imp_extbelegnr | |
| IMP_OBJECT | = lv_imp_object | |
| IMP_VISLID | = lv_imp_vislid | |
| NR_RANGE_NR | = lv_nr_range_nr | |
| IMPORTING | ||
| EXP_EXTBELNR | = lv_exp_extbelnr | |
| EXP_VISLID | = lv_exp_vislid | |
| FLG_DB_ENTRY | = lv_flg_db_entry | |
| EXCEPTIONS | ||
| INTERVAL_NOT_FOUND = 1 | ||
| NO_ENTRY = 2 | ||
| NUMBER_RANGE_NOT_INTERN = 3 | ||
| OBJECT_NOT_FOUND = 4 | ||
| QUANTTITY_IS_0 = 5 | ||
| . " EXT_BELNR_TRAFO | ||
ABAP code using 7.40 inline data declarations to call FM EXT_BELNR_TRAFO
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single XBLNR FROM BKPF INTO @DATA(ld_exp_extbelnr). | ||||
| DATA(ld_flg_user_chg) | = 'X'. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_imp_date). | ||||
| DATA(ld_imp_date) | = SY-DATUM. | |||
| "SELECT single XBLNR FROM BKPF INTO @DATA(ld_imp_extbelegnr). | ||||
| DATA(ld_imp_extbelegnr) | = ' '. | |||
| "SELECT single OBJECT FROM INRI INTO @DATA(ld_imp_object). | ||||
| DATA(ld_imp_object) | = 'FVVI_SOID'. | |||
| DATA(ld_imp_vislid) | = ' '. | |||
| "SELECT single NRRANGENR FROM INRI INTO @DATA(ld_nr_range_nr). | ||||
| DATA(ld_nr_range_nr) | = '01'. | |||
Search for further information about these or an SAP related objects