SAP UPS_FRAMEWORK_FILL_BID Function Module for fill business-ID
UPS_FRAMEWORK_FILL_BID is a standard ups framework fill bid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for fill business-ID 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 ups framework fill bid FM, simply by entering the name UPS_FRAMEWORK_FILL_BID into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPS_FRAMEWORK
Program Name: SAPLUPS_FRAMEWORK
Main Program: SAPLUPS_FRAMEWORK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPS_FRAMEWORK_FILL_BID 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 'UPS_FRAMEWORK_FILL_BID'"fill business-ID.
EXPORTING
I_MODE = "'X' for external, space for characteristics hierarchy
I_TEILPLAN = "Subplan in STS
CHANGING
XR_DOCUMENT = "IF_IXML_DOCUMENT
IMPORTING Parameters details for UPS_FRAMEWORK_FILL_BID
I_MODE - 'X' for external, space for characteristics hierarchy
Data type: CHAR1Optional: No
Call by Reference: Yes
I_TEILPLAN - Subplan in STS
Data type: UPS_Y_TEILPLANOptional: No
Call by Reference: Yes
CHANGING Parameters details for UPS_FRAMEWORK_FILL_BID
XR_DOCUMENT - IF_IXML_DOCUMENT
Data type: IF_IXML_DOCUMENTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPS_FRAMEWORK_FILL_BID 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_i_mode | TYPE CHAR1, " | |||
| lv_xr_document | TYPE IF_IXML_DOCUMENT, " | |||
| lv_i_teilplan | TYPE UPS_Y_TEILPLAN. " |
|   CALL FUNCTION 'UPS_FRAMEWORK_FILL_BID' "fill business-ID |
| EXPORTING | ||
| I_MODE | = lv_i_mode | |
| I_TEILPLAN | = lv_i_teilplan | |
| CHANGING | ||
| XR_DOCUMENT | = lv_xr_document | |
| . " UPS_FRAMEWORK_FILL_BID | ||
ABAP code using 7.40 inline data declarations to call FM UPS_FRAMEWORK_FILL_BID
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.Search for further information about these or an SAP related objects