SAP CBRC_PUR_PL_DATA_READ Function Module for NOTRANSL: Customizing: Lesen geplanter Mengen (Bestellung)
CBRC_PUR_PL_DATA_READ is a standard cbrc pur pl data read 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: Lesen geplanter Mengen (Bestellung) 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 pur pl data read FM, simply by entering the name CBRC_PUR_PL_DATA_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CBRC_PUR
Program Name: SAPLCBRC_PUR
Main Program: SAPLCBRC_PUR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CBRC_PUR_PL_DATA_READ 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_PUR_PL_DATA_READ'"NOTRANSL: Customizing: Lesen geplanter Mengen (Bestellung).
EXPORTING
I_REG = "Regulatory list
* I_SCEN = "Scenario
I_VALFR = "Start Date of Current Tracking Period
* I_VALFR_TIME = "
I_VALTO = "End Date of Current Tracking Period
* I_VALTO_TIME = "
IMPORTING
E_EBAN_TAB = "Purchase Requisition
E_EKKO_TAB = "Purchasing Document Header
E_EKPO_TAB = "Purchasing Document Item
E_EKET_TAB = "Sch. Agmt Sched. Lines
E_ERROR_TAB = "Message Table for Application Log
E_FLG_ERROR = "Error Indicator
IMPORTING Parameters details for CBRC_PUR_PL_DATA_READ
I_REG - Regulatory list
Data type: ESESLSTIDOptional: No
Call by Reference: Yes
I_SCEN - Scenario
Data type: CCRCE_SCENOptional: Yes
Call by Reference: Yes
I_VALFR - Start Date of Current Tracking Period
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_VALFR_TIME -
Data type: CPUTMOptional: Yes
Call by Reference: Yes
I_VALTO - End Date of Current Tracking Period
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_VALTO_TIME -
Data type: CPUTMOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CBRC_PUR_PL_DATA_READ
E_EBAN_TAB - Purchase Requisition
Data type: CCRCTT_EBANOptional: No
Call by Reference: Yes
E_EKKO_TAB - Purchasing Document Header
Data type: CCRCTT_EKKOOptional: No
Call by Reference: Yes
E_EKPO_TAB - Purchasing Document Item
Data type: CCRCTT_EKPOOptional: No
Call by Reference: Yes
E_EKET_TAB - Sch. Agmt Sched. Lines
Data type: CCRCTT_EKETOptional: 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_PUR_PL_DATA_READ 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_eban_tab | TYPE CCRCTT_EBAN, " | |||
| lv_i_scen | TYPE CCRCE_SCEN, " | |||
| lv_e_ekko_tab | TYPE CCRCTT_EKKO, " | |||
| lv_i_valfr | TYPE SY-DATUM, " | |||
| lv_e_ekpo_tab | TYPE CCRCTT_EKPO, " | |||
| lv_e_eket_tab | TYPE CCRCTT_EKET, " | |||
| lv_i_valfr_time | TYPE CPUTM, " | |||
| lv_i_valto | TYPE SY-DATUM, " | |||
| lv_e_error_tab | TYPE CCRCTT_MSG, " | |||
| lv_e_flg_error | TYPE ESEBOOLE, " | |||
| lv_i_valto_time | TYPE CPUTM. " |
|   CALL FUNCTION 'CBRC_PUR_PL_DATA_READ' "NOTRANSL: Customizing: Lesen geplanter Mengen (Bestellung) |
| EXPORTING | ||
| I_REG | = lv_i_reg | |
| I_SCEN | = lv_i_scen | |
| I_VALFR | = lv_i_valfr | |
| I_VALFR_TIME | = lv_i_valfr_time | |
| I_VALTO | = lv_i_valto | |
| I_VALTO_TIME | = lv_i_valto_time | |
| IMPORTING | ||
| E_EBAN_TAB | = lv_e_eban_tab | |
| E_EKKO_TAB | = lv_e_ekko_tab | |
| E_EKPO_TAB | = lv_e_ekpo_tab | |
| E_EKET_TAB | = lv_e_eket_tab | |
| E_ERROR_TAB | = lv_e_error_tab | |
| E_FLG_ERROR | = lv_e_flg_error | |
| . " CBRC_PUR_PL_DATA_READ | ||
ABAP code using 7.40 inline data declarations to call FM CBRC_PUR_PL_DATA_READ
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