SAP CBRC_PUR_PLANNED_DATA_SAVE Function Module for NOTRANSL: Customizing: Sichern der geplanten eingekauften Mengen

Search SAP Function Modules

CBRC_PUR_PLANNED_DATA_SAVE is a standard cbrc pur planned data save 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: Sichern der geplanten eingekauften Mengen 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 planned data save FM, simply by entering the name CBRC_PUR_PLANNED_DATA_SAVE 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_PLANNED_DATA_SAVE 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_PLANNED_DATA_SAVE'"NOTRANSL: Customizing: Sichern der geplanten eingekauften Mengen
  EXPORTING
   I_REG =  "Regulatory List
*  I_SCEN =  "Scenario
*  I_VALFR =  "Start Date of Current Tracking Period
*  I_VALTO =  "End Date of Current Tracking Period
   I_PUPL_UPD_TAB =  "Update Table
   I_PUPL_INS_TAB =  "Table Type for CCRCT_PUPL
   I_PUPL_DEL_TAB =  "Table Type for CCRCT_PUPL
   I_PUPL_OLD_UPD_TAB =  "Table Type for CCRCT_PUPL

 IMPORTING
   E_ERROR_TAB =  "Message Table for Application Log
   E_FLG_ERROR =  "Error Indicator

.

IMPORTING Parameters details for CBRC_PUR_PLANNED_DATA_SAVE

I_REG - Regulatory List

Data type: ESESLSTID
Optional: No
Call by Reference: Yes

I_SCEN - Scenario

Data type: CCRCE_SCEN
Optional: Yes
Call by Reference: Yes

I_VALFR - Start Date of Current Tracking Period

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_VALTO - End Date of Current Tracking Period

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_PUPL_UPD_TAB - Update Table

Data type: CCRCTT_PUPL
Optional: No
Call by Reference: Yes

I_PUPL_INS_TAB - Table Type for CCRCT_PUPL

Data type: CCRCTT_PUPL
Optional: No
Call by Reference: Yes

I_PUPL_DEL_TAB - Table Type for CCRCT_PUPL

Data type: CCRCTT_PUPL
Optional: No
Call by Reference: Yes

I_PUPL_OLD_UPD_TAB - Table Type for CCRCT_PUPL

Data type: CCRCTT_PUPL
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CBRC_PUR_PLANNED_DATA_SAVE

E_ERROR_TAB - Message Table for Application Log

Data type: CCRCTT_MSG
Optional: No
Call by Reference: Yes

E_FLG_ERROR - Error Indicator

Data type: ESEBOOLE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CBRC_PUR_PLANNED_DATA_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM CBRC_PUR_PLANNED_DATA_SAVE

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