SAP BUP_PARTNER_FILL_TAB Function Module for
BUP_PARTNER_FILL_TAB is a standard bup partner fill tab 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 bup partner fill tab FM, simply by entering the name BUP_PARTNER_FILL_TAB into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUD1
Program Name: SAPLBUD1
Main Program: SAPLBUD1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUP_PARTNER_FILL_TAB 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 'BUP_PARTNER_FILL_TAB'".
EXPORTING
I_PARTNER_MACO = "
* I_VALDT_SEL = SY-DATLO "
TABLES
T_PARTNER = "Business Partner Number
EXCEPTIONS
NO_PARTNER_FOUND = 1
IMPORTING Parameters details for BUP_PARTNER_FILL_TAB
I_PARTNER_MACO -
Data type: BU_MCNAME1Optional: No
Call by Reference: Yes
I_VALDT_SEL -
Data type: SY-DATLODefault: SY-DATLO
Optional: No
Call by Reference: Yes
TABLES Parameters details for BUP_PARTNER_FILL_TAB
T_PARTNER - Business Partner Number
Data type: BUSPARTNEROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_PARTNER_FOUND - No business partner found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUP_PARTNER_FILL_TAB 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: | ||||
| lt_t_partner | TYPE STANDARD TABLE OF BUSPARTNER, " | |||
| lv_i_partner_maco | TYPE BU_MCNAME1, " | |||
| lv_no_partner_found | TYPE BU_MCNAME1, " | |||
| lv_i_valdt_sel | TYPE SY-DATLO. " SY-DATLO |
|   CALL FUNCTION 'BUP_PARTNER_FILL_TAB' " |
| EXPORTING | ||
| I_PARTNER_MACO | = lv_i_partner_maco | |
| I_VALDT_SEL | = lv_i_valdt_sel | |
| TABLES | ||
| T_PARTNER | = lt_t_partner | |
| EXCEPTIONS | ||
| NO_PARTNER_FOUND = 1 | ||
| . " BUP_PARTNER_FILL_TAB | ||
ABAP code using 7.40 inline data declarations to call FM BUP_PARTNER_FILL_TAB
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 DATLO FROM SY INTO @DATA(ld_i_valdt_sel). | ||||
| DATA(ld_i_valdt_sel) | = SY-DATLO. | |||
Search for further information about these or an SAP related objects