SAP /ACCGO/CCAK_UPDATE_BAPI_INT Function Module for Update Contract through BAPI (Internal)









/ACCGO/CCAK_UPDATE_BAPI_INT is a standard /accgo/ccak update bapi int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Contract through BAPI (Internal) 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 update bapi int FM, simply by entering the name /ACCGO/CCAK_UPDATE_BAPI_INT 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_UPDATE_BAPI_INT 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_UPDATE_BAPI_INT'"Update Contract through BAPI (Internal)
EXPORTING
IV_TKONN = "Trading Contract
IS_HEADDATAIN = "Communication Structure: Trading Contract Header Data:
IS_HEADDATAINX = "Communication Structure: Trading Contract Header Data:
* IV_BATCH = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

IMPORTING
ET_MESSAGES = "Return parameter table

EXCEPTIONS
ERROR_MESSAGE = 1
.



IMPORTING Parameters details for /ACCGO/CCAK_UPDATE_BAPI_INT

IV_TKONN - Trading Contract

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

IS_HEADDATAIN - Communication Structure: Trading Contract Header Data:

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

IS_HEADDATAINX - Communication Structure: Trading Contract Header Data:

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

IV_BATCH - 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_UPDATE_BAPI_INT

ET_MESSAGES - Return parameter table

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

EXCEPTIONS details

ERROR_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /ACCGO/CCAK_UPDATE_BAPI_INT 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_iv_tkonn  TYPE BAPITCKEY-DOCUMENT_NUMBER, "   
lv_et_messages  TYPE BAPIRET2_T, "   
lv_error_message  TYPE BAPIRET2_T, "   
lv_is_headdatain  TYPE BAPITCHEADC, "   
lv_is_headdatainx  TYPE BAPITCHEADCX, "   
lv_iv_batch  TYPE BOOLE_D. "   

  CALL FUNCTION '/ACCGO/CCAK_UPDATE_BAPI_INT'  "Update Contract through BAPI (Internal)
    EXPORTING
         IV_TKONN = lv_iv_tkonn
         IS_HEADDATAIN = lv_is_headdatain
         IS_HEADDATAINX = lv_is_headdatainx
         IV_BATCH = lv_iv_batch
    IMPORTING
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        ERROR_MESSAGE = 1
. " /ACCGO/CCAK_UPDATE_BAPI_INT




ABAP code using 7.40 inline data declarations to call FM /ACCGO/CCAK_UPDATE_BAPI_INT

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_tkonn).
 
 
 
 
 
 


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!