SAP FDM_CCT_GET_LOCAL_DATA Function Module for









FDM_CCT_GET_LOCAL_DATA is a standard fdm cct get local data 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 fdm cct get local data FM, simply by entering the name FDM_CCT_GET_LOCAL_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function FDM_CCT_GET_LOCAL_DATA 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 'FDM_CCT_GET_LOCAL_DATA'"
EXPORTING
I_CCT_GUID = "
* I_TYPE = "

IMPORTING
ES_CCT_ATTR = "
ET_CCT_NOTES = "
ET_GUIDS = "
.



IMPORTING Parameters details for FDM_CCT_GET_LOCAL_DATA

I_CCT_GUID -

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

I_TYPE -

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

EXPORTING Parameters details for FDM_CCT_GET_LOCAL_DATA

ES_CCT_ATTR -

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

ET_CCT_NOTES -

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

ET_GUIDS -

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

Copy and paste ABAP code example for FDM_CCT_GET_LOCAL_DATA 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_cct_guid  TYPE BDM_CCT_GUID, "   
lv_es_cct_attr  TYPE BDM_CCT_ATTR, "   
lv_i_type  TYPE BDM_CCT_OBJ_TYPE, "   
lv_et_cct_notes  TYPE BDM_T_DISPUTE_NOTE, "   
lv_et_guids  TYPE SCMG_TT_CASE_GUID. "   

  CALL FUNCTION 'FDM_CCT_GET_LOCAL_DATA'  "
    EXPORTING
         I_CCT_GUID = lv_i_cct_guid
         I_TYPE = lv_i_type
    IMPORTING
         ES_CCT_ATTR = lv_es_cct_attr
         ET_CCT_NOTES = lv_et_cct_notes
         ET_GUIDS = lv_et_guids
. " FDM_CCT_GET_LOCAL_DATA




ABAP code using 7.40 inline data declarations to call FM FDM_CCT_GET_LOCAL_DATA

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



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!