SAP CBRC_CON_DATA_TRACK Function Module for NOTRANSL: Customizing: Rahmen für Überwachung konsumierter Mengen









CBRC_CON_DATA_TRACK is a standard cbrc con data track 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: Rahmen für Überwachung konsumierter 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 con data track FM, simply by entering the name CBRC_CON_DATA_TRACK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CBRC_CON
Program Name: SAPLCBRC_CON
Main Program: SAPLCBRC_CON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CBRC_CON_DATA_TRACK 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_CON_DATA_TRACK'"NOTRANSL: Customizing: Rahmen für Überwachung konsumierter Mengen
EXPORTING
I_VALFR = "Start Date of Current Tracking Period
I_FLG_CORR_REPORT = "
I_VALFR_TIME = "
I_VALTO = "End Date of Current Tracking Period
I_VALTO_TIME = "
I_FLG_HIST = "
* I_FLG_DELTA = "
I_DET_FCT = "
I_DETTYPE_FCT_TAB = "
* I_FLG_REG_COMPLETE = "

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



IMPORTING Parameters details for CBRC_CON_DATA_TRACK

I_VALFR - Start Date of Current Tracking Period

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

I_FLG_CORR_REPORT -

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

I_VALFR_TIME -

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

I_VALTO - End Date of Current Tracking Period

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

I_VALTO_TIME -

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

I_FLG_HIST -

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

I_FLG_DELTA -

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

I_DET_FCT -

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

I_DETTYPE_FCT_TAB -

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

I_FLG_REG_COMPLETE -

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

EXPORTING Parameters details for CBRC_CON_DATA_TRACK

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

E_MATNR_UNCONSIDERED_TAB -

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

Copy and paste ABAP code example for CBRC_CON_DATA_TRACK 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_valfr  TYPE SY-DATUM, "   
lv_e_error_tab  TYPE CCRCTT_MSG, "   
lv_i_flg_corr_report  TYPE ESP1_BOOLEAN, "   
lv_e_flg_error  TYPE ESEBOOLE, "   
lv_i_valfr_time  TYPE CPUTM, "   
lv_i_valto  TYPE SY-DATUM, "   
lv_e_matnr_unconsidered_tab  TYPE CCRCTT_LKEY, "   
lv_i_valto_time  TYPE CPUTM, "   
lv_i_flg_hist  TYPE ESEBOOLE, "   
lv_i_flg_delta  TYPE ESEBOOLE, "   
lv_i_det_fct  TYPE CCRCC_DET, "   
lv_i_dettype_fct_tab  TYPE CCRCTT_DETDOCTYPE, "   
lv_i_flg_reg_complete  TYPE ESEBOOLE. "   

  CALL FUNCTION 'CBRC_CON_DATA_TRACK'  "NOTRANSL: Customizing: Rahmen für Überwachung konsumierter Mengen
    EXPORTING
         I_VALFR = lv_i_valfr
         I_FLG_CORR_REPORT = lv_i_flg_corr_report
         I_VALFR_TIME = lv_i_valfr_time
         I_VALTO = lv_i_valto
         I_VALTO_TIME = lv_i_valto_time
         I_FLG_HIST = lv_i_flg_hist
         I_FLG_DELTA = lv_i_flg_delta
         I_DET_FCT = lv_i_det_fct
         I_DETTYPE_FCT_TAB = lv_i_dettype_fct_tab
         I_FLG_REG_COMPLETE = lv_i_flg_reg_complete
    IMPORTING
         E_ERROR_TAB = lv_e_error_tab
         E_FLG_ERROR = lv_e_flg_error
         E_MATNR_UNCONSIDERED_TAB = lv_e_matnr_unconsidered_tab
. " CBRC_CON_DATA_TRACK




ABAP code using 7.40 inline data declarations to call FM CBRC_CON_DATA_TRACK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!