SAP VBRP_FILL_FIELDS Function Module for VBRP migration function module for parallel processing
VBRP_FILL_FIELDS is a standard vbrp fill fields SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VBRP migration function module for parallel processing 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 vbrp fill fields FM, simply by entering the name VBRP_FILL_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: VBRP_S4MIG
Program Name: SAPLVBRP_S4MIG
Main Program: SAPLVBRP_S4MIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function VBRP_FILL_FIELDS 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 'VBRP_FILL_FIELDS'"VBRP migration function module for parallel processing.
EXPORTING
IV_VBELN_START = "Sales and Distribution Document Number
IV_VBELN_END = "Sales and Distribution Document Number
IV_INCLUDE_VBELN_FIRST = "Flag to include iv_vbeln_first in selection
* IV_PACKAGE_SIZE = "Package size of db rows to be processed together
* IV_TEST_MODE = "General flag
IMPORTING
ES_BAPIRET2 = "Return Parameter
ET_PK_MSG_043 = "Key Fields of Table VBEP
ET_PK_MSG_030_VBRK = "Key Fields of Table VBEP
EV_MSG_CNT_030_VBUK_FROM_VBRP = "counter: number of message 030
EV_MSG_CNT_030_VBRK_FROM_VBRP = "counter: number of message 030
EV_MSG_CNT_036_VBRP = "counter: number of message 036
EV_MSG_CNT_039 = "counter: number of message 039
EV_MSG_CNT_043 = "counter: number of message 042
EV_CNT_REC_TO_BE_ENRICHED = "Counter: Records found that need to be enriched
EV_CNT_REC_ENRICHED_OK = "Counter: Records enriched without problem(s)
EV_CNT_REC_ENRICHED_PARTLY = "Counter: Records enriched, but problem(s) occurred
EV_CNT_REC_ENRICHMENT_FAILED = "Counter: Records not enriched, as ALL enrichments failed
EV_CNT_REC_IGNORED = "Counter: Records selected but left out, as already migrated
ET_PK_MSG_030_VBUK = "Key Fields of Table VBEP
ET_PK_MSG_036 = "Key Fields of Table VBEP
ET_PK_MSG_039 = "Key Fields of Table VBEP
IMPORTING Parameters details for VBRP_FILL_FIELDS
IV_VBELN_START - Sales and Distribution Document Number
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_VBELN_END - Sales and Distribution Document Number
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_INCLUDE_VBELN_FIRST - Flag to include iv_vbeln_first in selection
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IV_PACKAGE_SIZE - Package size of db rows to be processed together
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TEST_MODE - General flag
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VBRP_FILL_FIELDS
ES_BAPIRET2 - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
ET_PK_MSG_043 - Key Fields of Table VBEP
Data type: TDT_VBEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
ET_PK_MSG_030_VBRK - Key Fields of Table VBEP
Data type: TDT_VBEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
EV_MSG_CNT_030_VBUK_FROM_VBRP - counter: number of message 030
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_MSG_CNT_030_VBRK_FROM_VBRP - counter: number of message 030
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_MSG_CNT_036_VBRP - counter: number of message 036
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_MSG_CNT_039 - counter: number of message 039
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_MSG_CNT_043 - counter: number of message 042
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_CNT_REC_TO_BE_ENRICHED - Counter: Records found that need to be enriched
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_CNT_REC_ENRICHED_OK - Counter: Records enriched without problem(s)
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_CNT_REC_ENRICHED_PARTLY - Counter: Records enriched, but problem(s) occurred
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_CNT_REC_ENRICHMENT_FAILED - Counter: Records not enriched, as ALL enrichments failed
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EV_CNT_REC_IGNORED - Counter: Records selected but left out, as already migrated
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
ET_PK_MSG_030_VBUK - Key Fields of Table VBEP
Data type: TDT_VBEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
ET_PK_MSG_036 - Key Fields of Table VBEP
Data type: TDT_VBEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
ET_PK_MSG_039 - Key Fields of Table VBEP
Data type: TDT_VBEP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VBRP_FILL_FIELDS 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_es_bapiret2 | TYPE BAPIRET2, " | |||
| lv_iv_vbeln_start | TYPE STRING, " | |||
| lv_et_pk_msg_043 | TYPE TDT_VBEP_KEY, " | |||
| lv_et_pk_msg_030_vbrk | TYPE TDT_VBEP_KEY, " | |||
| lv_ev_msg_cnt_030_vbuk_from_vbrp | TYPE I, " | |||
| lv_ev_msg_cnt_030_vbrk_from_vbrp | TYPE I, " | |||
| lv_ev_msg_cnt_036_vbrp | TYPE I, " | |||
| lv_ev_msg_cnt_039 | TYPE I, " | |||
| lv_ev_msg_cnt_043 | TYPE I, " | |||
| lv_iv_vbeln_end | TYPE STRING, " | |||
| lv_ev_cnt_rec_to_be_enriched | TYPE I, " | |||
| lv_ev_cnt_rec_enriched_ok | TYPE I, " | |||
| lv_iv_include_vbeln_first | TYPE BOOLEAN, " | |||
| lv_iv_package_size | TYPE I, " | |||
| lv_ev_cnt_rec_enriched_partly | TYPE I, " | |||
| lv_iv_test_mode | TYPE BOOLEAN, " | |||
| lv_ev_cnt_rec_enrichment_failed | TYPE I, " | |||
| lv_ev_cnt_rec_ignored | TYPE I, " | |||
| lv_et_pk_msg_030_vbuk | TYPE TDT_VBEP_KEY, " | |||
| lv_et_pk_msg_036 | TYPE TDT_VBEP_KEY, " | |||
| lv_et_pk_msg_039 | TYPE TDT_VBEP_KEY. " |
|   CALL FUNCTION 'VBRP_FILL_FIELDS' "VBRP migration function module for parallel processing |
| EXPORTING | ||
| IV_VBELN_START | = lv_iv_vbeln_start | |
| IV_VBELN_END | = lv_iv_vbeln_end | |
| IV_INCLUDE_VBELN_FIRST | = lv_iv_include_vbeln_first | |
| IV_PACKAGE_SIZE | = lv_iv_package_size | |
| IV_TEST_MODE | = lv_iv_test_mode | |
| IMPORTING | ||
| ES_BAPIRET2 | = lv_es_bapiret2 | |
| ET_PK_MSG_043 | = lv_et_pk_msg_043 | |
| ET_PK_MSG_030_VBRK | = lv_et_pk_msg_030_vbrk | |
| EV_MSG_CNT_030_VBUK_FROM_VBRP | = lv_ev_msg_cnt_030_vbuk_from_vbrp | |
| EV_MSG_CNT_030_VBRK_FROM_VBRP | = lv_ev_msg_cnt_030_vbrk_from_vbrp | |
| EV_MSG_CNT_036_VBRP | = lv_ev_msg_cnt_036_vbrp | |
| EV_MSG_CNT_039 | = lv_ev_msg_cnt_039 | |
| EV_MSG_CNT_043 | = lv_ev_msg_cnt_043 | |
| EV_CNT_REC_TO_BE_ENRICHED | = lv_ev_cnt_rec_to_be_enriched | |
| EV_CNT_REC_ENRICHED_OK | = lv_ev_cnt_rec_enriched_ok | |
| EV_CNT_REC_ENRICHED_PARTLY | = lv_ev_cnt_rec_enriched_partly | |
| EV_CNT_REC_ENRICHMENT_FAILED | = lv_ev_cnt_rec_enrichment_failed | |
| EV_CNT_REC_IGNORED | = lv_ev_cnt_rec_ignored | |
| ET_PK_MSG_030_VBUK | = lv_et_pk_msg_030_vbuk | |
| ET_PK_MSG_036 | = lv_et_pk_msg_036 | |
| ET_PK_MSG_039 | = lv_et_pk_msg_039 | |
| . " VBRP_FILL_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM VBRP_FILL_FIELDS
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