SAP /ACCGO/CCAK_CRT_CHANGE_API Function Module for API: Change Trade Contract Number

Search SAP Function Modules

/ACCGO/CCAK_CRT_CHANGE_API is a standard /accgo/ccak crt change api SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API: Change Trade Contract Number 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 /accgo/ccak crt change api FM, simply by entering the name /ACCGO/CCAK_CRT_CHANGE_API into the relevant SAP transaction such as SE37 or SE38.

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

Function /ACCGO/CCAK_CRT_CHANGE_API 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 '/ACCGO/CCAK_CRT_CHANGE_API'"API: Change Trade Contract Number
  EXPORTING
   IV_CONTRACT_NUM =  "Trading Contract
   IS_CRT_DATA =  "API: Change Contract : Input Data
   IS_CRT_DATAX =  "API: Change Contract : Input Data X Value
*  IV_COMMIT =  "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

 IMPORTING
   EV_CONTRACT_NUM =  "Trading Contract
   ES_CONTRACT_DATA =  "API: Contract Data
   ET_MESSAGES =  "Messages

.

IMPORTING Parameters details for /ACCGO/CCAK_CRT_CHANGE_API

IV_CONTRACT_NUM - Trading Contract

Data type: BAPITCKEY-DOCUMENT_NUMBER
Optional: No
Call by Reference: Yes

IS_CRT_DATA - API: Change Contract : Input Data

Data type: /ACCGO/CCAK_S_CRT_CNG_INPD_API
Optional: No
Call by Reference: Yes

IS_CRT_DATAX - API: Change Contract : Input Data X Value

Data type: /ACCGO/CCAK_S_CRT_CNG_INPX_API
Optional: No
Call by Reference: Yes

IV_COMMIT - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

EXPORTING Parameters details for /ACCGO/CCAK_CRT_CHANGE_API

EV_CONTRACT_NUM - Trading Contract

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

ES_CONTRACT_DATA - API: Contract Data

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

ET_MESSAGES - Messages

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

Copy and paste ABAP code example for /ACCGO/CCAK_CRT_CHANGE_API 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 /ACCGO/CCAK_CRT_CHANGE_API

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