SAP CBRC_SO_DATA_FILL Function Module for NOTRANSL: Customizing: Datenüberführung in ÜberwTabellen (Lieferung)
CBRC_SO_DATA_FILL is a standard cbrc so data fill 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: Customizing: Datenüberführung in ÜberwTabellen (Lieferung) 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 cbrc so data fill FM, simply by entering the name CBRC_SO_DATA_FILL into the relevant SAP transaction such as SE37 or SE38.
Function Group: CBRC_SO
Program Name: SAPLCBRC_SO
Main Program: SAPLCBRC_SO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CBRC_SO_DATA_FILL 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 'CBRC_SO_DATA_FILL'"NOTRANSL: Customizing: Datenüberführung in ÜberwTabellen (Lieferung).
EXPORTING
I_REG = "Regulatory list
* I_VBEP_TAB = "Sales Document: Schedule Line Data
I_LIKP_TAB = "SD Document: Delivery Header Data
I_LIPS_TAB = "SD Document: Delivery: Item Data
I_VBPA_TAB = "Sales Document: Partner
I_MKPF_TAB = "Header: Material Document
I_MSEG_TAB = "Document Segment: Material
I_MATNR_SUB_TAB = "Material Substance Table
* I_SCEN = "Scenario
I_DETTYPE_FCT = "EHS: Modules for Regulation/Scenario/Scenario Category
I_VALFR = "Start Date of Current Tracking Period
I_VALTO = "End Date of Current Tracking Period
* I_VBUK_TAB = "Sales Document: Header Status and Administrative Data
I_VBUP_TAB = "Sales Document: Item Status
* I_VBAK_TAB = "Sales Document: Header Data
* I_VBAP_TAB = "Sales Document: Item Data
IMPORTING
E_SO_TAB = "Confirmed Quantities
E_SO_DEL_TAB = "Table Type for CCRCT_PU
E_SOPL_TAB = "Planned Quantities
E_SOPL_DEL_TAB = "Delta Table for CCRCT_PUPL
E_ERROR_TAB = "Message Table for Application Log
E_FLG_ERROR = "Error Indicator
IMPORTING Parameters details for CBRC_SO_DATA_FILL
I_REG - Regulatory list
Data type: ESESLSTIDOptional: No
Call by Reference: Yes
I_VBEP_TAB - Sales Document: Schedule Line Data
Data type: CCRCTT_VBEPOptional: Yes
Call by Reference: Yes
I_LIKP_TAB - SD Document: Delivery Header Data
Data type: CCRCTT_LIKPOptional: No
Call by Reference: Yes
I_LIPS_TAB - SD Document: Delivery: Item Data
Data type: CCRCTT_LIPSOptional: No
Call by Reference: Yes
I_VBPA_TAB - Sales Document: Partner
Data type: CCRCTT_VBPAOptional: No
Call by Reference: Yes
I_MKPF_TAB - Header: Material Document
Data type: CCRCTT_MKPFOptional: No
Call by Reference: Yes
I_MSEG_TAB - Document Segment: Material
Data type: CCRCTT_MSEGOptional: No
Call by Reference: Yes
I_MATNR_SUB_TAB - Material Substance Table
Data type: CCRCTT_FIELDSOptional: No
Call by Reference: Yes
I_SCEN - Scenario
Data type: CCRCE_SCENOptional: Yes
Call by Reference: Yes
I_DETTYPE_FCT - EHS: Modules for Regulation/Scenario/Scenario Category
Data type: CCRCC_DETDOCTYPEOptional: No
Call by Reference: Yes
I_VALFR - Start Date of Current Tracking Period
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_VALTO - End Date of Current Tracking Period
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_VBUK_TAB - Sales Document: Header Status and Administrative Data
Data type: CCRCTT_VBUKOptional: Yes
Call by Reference: Yes
I_VBUP_TAB - Sales Document: Item Status
Data type: CCRCTT_VBUPOptional: No
Call by Reference: Yes
I_VBAK_TAB - Sales Document: Header Data
Data type: CCRCTT_VBAKOptional: Yes
Call by Reference: Yes
I_VBAP_TAB - Sales Document: Item Data
Data type: CCRCTT_VBAPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CBRC_SO_DATA_FILL
E_SO_TAB - Confirmed Quantities
Data type: CCRCTT_SOOptional: No
Call by Reference: Yes
E_SO_DEL_TAB - Table Type for CCRCT_PU
Data type: CCRCTT_SOOptional: No
Call by Reference: Yes
E_SOPL_TAB - Planned Quantities
Data type: CCRCTT_SOPLOptional: No
Call by Reference: Yes
E_SOPL_DEL_TAB - Delta Table for CCRCT_PUPL
Data type: CCRCTT_SOPLOptional: No
Call by Reference: Yes
E_ERROR_TAB - Message Table for Application Log
Data type: CCRCTT_MSGOptional: No
Call by Reference: Yes
E_FLG_ERROR - Error Indicator
Data type: ESEBOOLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CBRC_SO_DATA_FILL 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_reg | TYPE ESESLSTID, " | |||
| lv_e_so_tab | TYPE CCRCTT_SO, " | |||
| lv_i_vbep_tab | TYPE CCRCTT_VBEP, " | |||
| lv_i_likp_tab | TYPE CCRCTT_LIKP, " | |||
| lv_i_lips_tab | TYPE CCRCTT_LIPS, " | |||
| lv_i_vbpa_tab | TYPE CCRCTT_VBPA, " | |||
| lv_i_mkpf_tab | TYPE CCRCTT_MKPF, " | |||
| lv_i_mseg_tab | TYPE CCRCTT_MSEG, " | |||
| lv_i_matnr_sub_tab | TYPE CCRCTT_FIELDS, " | |||
| lv_i_scen | TYPE CCRCE_SCEN, " | |||
| lv_e_so_del_tab | TYPE CCRCTT_SO, " | |||
| lv_e_sopl_tab | TYPE CCRCTT_SOPL, " | |||
| lv_i_dettype_fct | TYPE CCRCC_DETDOCTYPE, " | |||
| lv_i_valfr | TYPE SY-DATUM, " | |||
| lv_e_sopl_del_tab | TYPE CCRCTT_SOPL, " | |||
| lv_i_valto | TYPE SY-DATUM, " | |||
| lv_e_error_tab | TYPE CCRCTT_MSG, " | |||
| lv_i_vbuk_tab | TYPE CCRCTT_VBUK, " | |||
| lv_e_flg_error | TYPE ESEBOOLE, " | |||
| lv_i_vbup_tab | TYPE CCRCTT_VBUP, " | |||
| lv_i_vbak_tab | TYPE CCRCTT_VBAK, " | |||
| lv_i_vbap_tab | TYPE CCRCTT_VBAP. " |
|   CALL FUNCTION 'CBRC_SO_DATA_FILL' "NOTRANSL: Customizing: Datenüberführung in ÜberwTabellen (Lieferung) |
| EXPORTING | ||
| I_REG | = lv_i_reg | |
| I_VBEP_TAB | = lv_i_vbep_tab | |
| I_LIKP_TAB | = lv_i_likp_tab | |
| I_LIPS_TAB | = lv_i_lips_tab | |
| I_VBPA_TAB | = lv_i_vbpa_tab | |
| I_MKPF_TAB | = lv_i_mkpf_tab | |
| I_MSEG_TAB | = lv_i_mseg_tab | |
| I_MATNR_SUB_TAB | = lv_i_matnr_sub_tab | |
| I_SCEN | = lv_i_scen | |
| I_DETTYPE_FCT | = lv_i_dettype_fct | |
| I_VALFR | = lv_i_valfr | |
| I_VALTO | = lv_i_valto | |
| I_VBUK_TAB | = lv_i_vbuk_tab | |
| I_VBUP_TAB | = lv_i_vbup_tab | |
| I_VBAK_TAB | = lv_i_vbak_tab | |
| I_VBAP_TAB | = lv_i_vbap_tab | |
| IMPORTING | ||
| E_SO_TAB | = lv_e_so_tab | |
| E_SO_DEL_TAB | = lv_e_so_del_tab | |
| E_SOPL_TAB | = lv_e_sopl_tab | |
| E_SOPL_DEL_TAB | = lv_e_sopl_del_tab | |
| E_ERROR_TAB | = lv_e_error_tab | |
| E_FLG_ERROR | = lv_e_flg_error | |
| . " CBRC_SO_DATA_FILL | ||
ABAP code using 7.40 inline data declarations to call FM CBRC_SO_DATA_FILL
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 DATUM FROM SY INTO @DATA(ld_i_valfr). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_valto). | ||||
Search for further information about these or an SAP related objects