SAP BBP_EXTREQ_TRANSFER Function Module for NOTRANSL: Übertragung von externen Anforderungen









BBP_EXTREQ_TRANSFER is a standard bbp extreq transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Übertragung von externen Anforderungen processing and below is the pattern details for this FM, 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 bbp extreq transfer FM, simply by entering the name BBP_EXTREQ_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_EXTREQ
Program Name: SAPLBBP_EXTREQ
Main Program: SAPLBBP_EXTREQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_EXTREQ_TRANSFER 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 'BBP_EXTREQ_TRANSFER'"NOTRANSL: Übertragung von externen Anforderungen
EXPORTING
* IV_TRANS_DATE = SY-DATUM "Date in CHAR format
* IV_PACKAGESIZE = 100 "
* IV_QUEUENAME = 'BBP_EXTREQ_TRANS' "
* IT_BANFSEL = "Purchase Requisition Number
* IV_MAXROWS = 100000 "
* IV_TRANS_OFFSET = "
* IV_SPLIT = "Checkbox
* IV_CALLHANDLER = "Checkbox
* IV_SPLITNUMBER = "

IMPORTING
EV_RESULT = "Results structure for transfer of external requirements
.



IMPORTING Parameters details for BBP_EXTREQ_TRANSFER

IV_TRANS_DATE - Date in CHAR format

Data type: BBP_ER_TRANSDATE
Default: SY-DATUM
Optional: No
Call by Reference: Yes

IV_PACKAGESIZE -

Data type: I
Default: 100
Optional: Yes
Call by Reference: Yes

IV_QUEUENAME -

Data type: CHAR22
Default: 'BBP_EXTREQ_TRANS'
Optional: Yes
Call by Reference: Yes

IT_BANFSEL - Purchase Requisition Number

Data type: BBPT_TRANS_SECTION
Optional: Yes
Call by Reference: Yes

IV_MAXROWS -

Data type: I
Default: 100000
Optional: Yes
Call by Reference: Yes

IV_TRANS_OFFSET -

Data type:
Optional: Yes
Call by Reference: Yes

IV_SPLIT - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IV_CALLHANDLER - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IV_SPLITNUMBER -

Data type: I
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_EXTREQ_TRANSFER

EV_RESULT - Results structure for transfer of external requirements

Data type: BBS_ER_RESULT_FROM_TRANSFER
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_EXTREQ_TRANSFER 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_ev_result  TYPE BBS_ER_RESULT_FROM_TRANSFER, "   
lv_iv_trans_date  TYPE BBP_ER_TRANSDATE, "   SY-DATUM
lv_iv_packagesize  TYPE I, "   100
lv_iv_queuename  TYPE CHAR22, "   'BBP_EXTREQ_TRANS'
lv_it_banfsel  TYPE BBPT_TRANS_SECTION, "   
lv_iv_maxrows  TYPE I, "   100000
lv_iv_trans_offset  TYPE I, "   
lv_iv_split  TYPE XFELD, "   
lv_iv_callhandler  TYPE XFELD, "   
lv_iv_splitnumber  TYPE I. "   

  CALL FUNCTION 'BBP_EXTREQ_TRANSFER'  "NOTRANSL: Übertragung von externen Anforderungen
    EXPORTING
         IV_TRANS_DATE = lv_iv_trans_date
         IV_PACKAGESIZE = lv_iv_packagesize
         IV_QUEUENAME = lv_iv_queuename
         IT_BANFSEL = lv_it_banfsel
         IV_MAXROWS = lv_iv_maxrows
         IV_TRANS_OFFSET = lv_iv_trans_offset
         IV_SPLIT = lv_iv_split
         IV_CALLHANDLER = lv_iv_callhandler
         IV_SPLITNUMBER = lv_iv_splitnumber
    IMPORTING
         EV_RESULT = lv_ev_result
. " BBP_EXTREQ_TRANSFER




ABAP code using 7.40 inline data declarations to call FM BBP_EXTREQ_TRANSFER

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.

 
DATA(ld_iv_trans_date) = SY-DATUM.
 
DATA(ld_iv_packagesize) = 100.
 
DATA(ld_iv_queuename) = 'BBP_EXTREQ_TRANS'.
 
 
DATA(ld_iv_maxrows) = 100000.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!