SAP /ACCGO/CCAK_CHANGE_API Function Module for Changes Trading Contracts









/ACCGO/CCAK_CHANGE_API is a standard /accgo/ccak 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 Changes Trading Contracts 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 change api FM, simply by entering the name /ACCGO/CCAK_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: 04-Sep-2020
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function /ACCGO/CCAK_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_CHANGE_API'"Changes Trading Contracts
EXPORTING
IV_CONTRACT_NUM = "Trading Contract
IS_CNG_DATA = "API: Change Contract : Input Data
IS_CNG_DATAX = "API: Change Contract : Input Data X Value
* IT_REF_CONTRACT_DETAILS = "Trading Contract
* IV_COMMIT = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IS_SET_BUFFER = "API : Change Contract : Set Buffer

IMPORTING
ET_MESSAGES = "Messages
.



IMPORTING Parameters details for /ACCGO/CCAK_CHANGE_API

IV_CONTRACT_NUM - Trading Contract

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

IS_CNG_DATA - API: Change Contract : Input Data

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

IS_CNG_DATAX - API: Change Contract : Input Data X Value

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

IT_REF_CONTRACT_DETAILS - Trading Contract

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

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

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

IS_SET_BUFFER - API : Change Contract : Set Buffer

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

EXPORTING Parameters details for /ACCGO/CCAK_CHANGE_API

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_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.

DATA:
lv_et_messages  TYPE /ACCGO/TT_CCAK_MESSAGE_API, "   
lv_iv_contract_num  TYPE BAPITCKEY-DOCUMENT_NUMBER, "   
lv_is_cng_data  TYPE /ACCGO/CCAK_S_CNG_INPD_API, "   
lv_is_cng_datax  TYPE /ACCGO/CCAK_S_CNG_INPX_API, "   
lv_it_ref_contract_details  TYPE /ACCGO/TT_CCAK_CNG_REF_API, "   
lv_iv_commit  TYPE BOOLE_D, "   
lv_is_set_buffer  TYPE /ACCGO/S_CAK_PRC_CDOTE_UI. "   

  CALL FUNCTION '/ACCGO/CCAK_CHANGE_API'  "Changes Trading Contracts
    EXPORTING
         IV_CONTRACT_NUM = lv_iv_contract_num
         IS_CNG_DATA = lv_is_cng_data
         IS_CNG_DATAX = lv_is_cng_datax
         IT_REF_CONTRACT_DETAILS = lv_it_ref_contract_details
         IV_COMMIT = lv_iv_commit
         IS_SET_BUFFER = lv_is_set_buffer
    IMPORTING
         ET_MESSAGES = lv_et_messages
. " /ACCGO/CCAK_CHANGE_API




ABAP code using 7.40 inline data declarations to call FM /ACCGO/CCAK_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.

 
"SELECT single DOCUMENT_NUMBER FROM BAPITCKEY INTO @DATA(ld_iv_contract_num).
 
 
 
 
 
 


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!