SAP RE_GET_CC_CUSTOMIZING Function Module for
RE_GET_CC_CUSTOMIZING is a standard re get cc customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 re get cc customizing FM, simply by entering the name RE_GET_CC_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVF1
Program Name: SAPLFVF1
Main Program: SAPLFVF1
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RE_GET_CC_CUSTOMIZING 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 'RE_GET_CC_CUSTOMIZING'".
EXPORTING
I_BUKRS = "
IMPORTING
E_TIPZB = "
EXCEPTIONS
NO_CC_CUSTOMIZING = 1
IMPORTING Parameters details for RE_GET_CC_CUSTOMIZING
I_BUKRS -
Data type: TIPZB-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RE_GET_CC_CUSTOMIZING
E_TIPZB -
Data type: TIPZBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CC_CUSTOMIZING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RE_GET_CC_CUSTOMIZING 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_e_tipzb | TYPE TIPZB, " | |||
| lv_i_bukrs | TYPE TIPZB-BUKRS, " | |||
| lv_no_cc_customizing | TYPE TIPZB. " |
|   CALL FUNCTION 'RE_GET_CC_CUSTOMIZING' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| IMPORTING | ||
| E_TIPZB | = lv_e_tipzb | |
| EXCEPTIONS | ||
| NO_CC_CUSTOMIZING = 1 | ||
| . " RE_GET_CC_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM RE_GET_CC_CUSTOMIZING
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 BUKRS FROM TIPZB INTO @DATA(ld_i_bukrs). | ||||
Search for further information about these or an SAP related objects