SAP BBP_CREATE_FRAGMENTS Function Module for
BBP_CREATE_FRAGMENTS is a standard bbp create fragments 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 bbp create fragments FM, simply by entering the name BBP_CREATE_FRAGMENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BUPA_VR
Program Name: SAPLBBP_BUPA_VR
Main Program: SAPLBBP_BUPA_VR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CREATE_FRAGMENTS 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_CREATE_FRAGMENTS'".
EXPORTING
* IV_PARTNER_GUID = "
* IS_FRG0030 = "
* IS_FRG0010 = "
TABLES
* IT_FRG0061 = "
* IT_FRG0040 = "
* IT_FRG0030 = "
* IT_FRG0020 = "
* IT_BIDCC = "
* IT_SENDMEDIUM = "
* ET_RETURN = "
EXCEPTIONS
PARTNER_GUID_MISSING = 1 ERROR_MESSAGE_PASSED = 2
IMPORTING Parameters details for BBP_CREATE_FRAGMENTS
IV_PARTNER_GUID -
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_FRG0030 -
Data type: BBPT_BUS_FRG0030Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_FRG0010 -
Data type: BBPT_BUS_FRG0010Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CREATE_FRAGMENTS
IT_FRG0061 -
Data type: BBPM_BUT_FRG0061Optional: Yes
Call by Reference: Yes
IT_FRG0040 -
Data type: BBPT_BUS_FRG0040Optional: Yes
Call by Reference: Yes
IT_FRG0030 -
Data type: BBPT_BUS_FRG0030Optional: Yes
Call by Reference: Yes
IT_FRG0020 -
Data type: BBPT_BUS_FRG0020Optional: Yes
Call by Reference: Yes
IT_BIDCC -
Data type: BIDCCOptional: Yes
Call by Reference: Yes
IT_SENDMEDIUM -
Data type: BBPT_SENDMEDIUMOptional: Yes
Call by Reference: Yes
ET_RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
PARTNER_GUID_MISSING -
Data type:Optional: No
Call by Reference: Yes
ERROR_MESSAGE_PASSED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CREATE_FRAGMENTS 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_it_frg0061 | TYPE STANDARD TABLE OF BBPM_BUT_FRG0061, " | |||
| lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_partner_guid_missing | TYPE BU_PARTNER_GUID, " | |||
| lv_is_frg0030 | TYPE BBPT_BUS_FRG0030, " | |||
| lt_it_frg0040 | TYPE STANDARD TABLE OF BBPT_BUS_FRG0040, " | |||
| lv_error_message_passed | TYPE BBPT_BUS_FRG0040, " | |||
| lv_is_frg0010 | TYPE BBPT_BUS_FRG0010, " | |||
| lt_it_frg0030 | TYPE STANDARD TABLE OF BBPT_BUS_FRG0030, " | |||
| lt_it_frg0020 | TYPE STANDARD TABLE OF BBPT_BUS_FRG0020, " | |||
| lt_it_bidcc | TYPE STANDARD TABLE OF BIDCC, " | |||
| lt_it_sendmedium | TYPE STANDARD TABLE OF BBPT_SENDMEDIUM, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BBP_CREATE_FRAGMENTS' " |
| EXPORTING | ||
| IV_PARTNER_GUID | = lv_iv_partner_guid | |
| IS_FRG0030 | = lv_is_frg0030 | |
| IS_FRG0010 | = lv_is_frg0010 | |
| TABLES | ||
| IT_FRG0061 | = lt_it_frg0061 | |
| IT_FRG0040 | = lt_it_frg0040 | |
| IT_FRG0030 | = lt_it_frg0030 | |
| IT_FRG0020 | = lt_it_frg0020 | |
| IT_BIDCC | = lt_it_bidcc | |
| IT_SENDMEDIUM | = lt_it_sendmedium | |
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| PARTNER_GUID_MISSING = 1 | ||
| ERROR_MESSAGE_PASSED = 2 | ||
| . " BBP_CREATE_FRAGMENTS | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CREATE_FRAGMENTS
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