SAP SAMPLE_INTERFACE_CC000170 Function Module for

Search SAP Function Modules

SAMPLE_INTERFACE_CC000170 is a standard sample interface cc000170 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 sample interface cc000170 FM, simply by entering the name SAMPLE_INTERFACE_CC000170 into the relevant SAP transaction such as SE37 or SE38.

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

Function SAMPLE_INTERFACE_CC000170 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 'SAMPLE_INTERFACE_CC000170'"
  EXPORTING
   IDOC_CONTROL =  "Control Record (IDoc)

CHANGING
   CH_AENR =  "Change Master Record
   CH_AEPF =  "ECM: effectivity
   CH_MSGFN =  "Message Function
   CH_EFF_TYPE =  "
   CH_LEADER =  "Change Number
   CH_STSMA =  "Status Profile

TABLES
   TAB_AEDT =  "Engineering Change Management: Alternative Dates
   TAB_AEEF =  "ECM: effectivity
   TAB_AENV =  "
   TAB_AEOI =  "ALE: Object Management Records
   TAB_STSMA =  "ALE: Status Profile
   TAB_THEAD =  "Structure of text header in ECM
   TAB_TLINE =  "Structure of the lines of text in ECM

EXCEPTIONS
   IDOC_ERROR = 1 

.

IMPORTING Parameters details for SAMPLE_INTERFACE_CC000170

IDOC_CONTROL - Control Record (IDoc)

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

CHANGING Parameters details for SAMPLE_INTERFACE_CC000170

CH_AENR - Change Master Record

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

CH_AEPF - ECM: effectivity

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

CH_MSGFN - Message Function

Data type: E1AENRM-MSGFN
Optional: No
Call by Reference: Yes

CH_EFF_TYPE -

Data type: E1AENRM-EFF_TYPE
Optional: No
Call by Reference: Yes

CH_LEADER - Change Number

Data type: AENR_API01-CHANGE_LEADER
Optional: No
Call by Reference: Yes

CH_STSMA - Status Profile

Data type: AENR_API01-STATUS_PROFILE
Optional: No
Call by Reference: Yes

TABLES Parameters details for SAMPLE_INTERFACE_CC000170

TAB_AEDT - Engineering Change Management: Alternative Dates

Data type: AEDT
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_AEEF - ECM: effectivity

Data type: AEEF
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_AENV -

Data type: AENV
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_AEOI - ALE: Object Management Records

Data type: CCALE_AEOI
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_STSMA - ALE: Status Profile

Data type: CCALE_STSMA
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_THEAD - Structure of text header in ECM

Data type: CCTHEAD
Optional: No
Call by Reference: No ( called with pass by value option)

TAB_TLINE - Structure of the lines of text in ECM

Data type: CCTLINE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

IDOC_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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