SAP FKK_DOCUMENT_CHANGE_COMPLETE Function Module for









FKK_DOCUMENT_CHANGE_COMPLETE is a standard fkk document change complete 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 fkk document change complete FM, simply by entering the name FKK_DOCUMENT_CHANGE_COMPLETE into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_DOCUMENT_CHANGE_COMPLETE 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 'FKK_DOCUMENT_CHANGE_COMPLETE'"
EXPORTING
I_OPBEL = "Number of a Contract Accounts Receivable and Payable Document
* I_UPDATE_TASK = "
* I_USERNAME = "
* I_WORKFLOW_CHECK = 'X' "
* I_CHANGE_CLEARED_ITEMS = ' ' "

TABLES
* T_KOCHANGES = "Change Document: Changes to Document Header
* T_OPCHANGES = "Change Document: Business Partner Items
* T_OPWCHANGES = "Change Document: Repetition Entries?
* T_CHANGEDOPS = "Business Partner Items in Contract Account Document
* T_CHANGEDOPWS = "Items in contract account document
* T_FKKOPCHL = "Locks for Open Items (Posting Interface) Change

EXCEPTIONS
ERR_LOCK_CHANGE = 1 ERR_DOC_CHANGE = 2
.



IMPORTING Parameters details for FKK_DOCUMENT_CHANGE_COMPLETE

I_OPBEL - Number of a Contract Accounts Receivable and Payable Document

Data type: FKKKO-OPBEL
Optional: No
Call by Reference: Yes

I_UPDATE_TASK -

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

I_USERNAME -

Data type: SYST-UNAME
Optional: Yes
Call by Reference: Yes

I_WORKFLOW_CHECK -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_CHANGE_CLEARED_ITEMS -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for FKK_DOCUMENT_CHANGE_COMPLETE

T_KOCHANGES - Change Document: Changes to Document Header

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

T_OPCHANGES - Change Document: Business Partner Items

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

T_OPWCHANGES - Change Document: Repetition Entries?

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

T_CHANGEDOPS - Business Partner Items in Contract Account Document

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

T_CHANGEDOPWS - Items in contract account document

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

T_FKKOPCHL - Locks for Open Items (Posting Interface) Change

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

EXCEPTIONS details

ERR_LOCK_CHANGE -

Data type:
Optional: No
Call by Reference: Yes

ERR_DOC_CHANGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_DOCUMENT_CHANGE_COMPLETE 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_opbel  TYPE FKKKO-OPBEL, "   
lt_t_kochanges  TYPE STANDARD TABLE OF FKKCHDOC_KO, "   
lv_err_lock_change  TYPE FKKCHDOC_KO, "   
lt_t_opchanges  TYPE STANDARD TABLE OF FKKCHDOC_OP, "   
lv_i_update_task  TYPE XFELD, "   
lv_err_doc_change  TYPE XFELD, "   
lv_i_username  TYPE SYST-UNAME, "   
lt_t_opwchanges  TYPE STANDARD TABLE OF FKKCHDOC_OPW, "   
lt_t_changedops  TYPE STANDARD TABLE OF FKKOP, "   
lv_i_workflow_check  TYPE BOOLE-BOOLE, "   'X'
lt_t_changedopws  TYPE STANDARD TABLE OF FKKOPW, "   
lv_i_change_cleared_items  TYPE BOOLE-BOOLE, "   SPACE
lt_t_fkkopchl  TYPE STANDARD TABLE OF FKKOPCHL. "   

  CALL FUNCTION 'FKK_DOCUMENT_CHANGE_COMPLETE'  "
    EXPORTING
         I_OPBEL = lv_i_opbel
         I_UPDATE_TASK = lv_i_update_task
         I_USERNAME = lv_i_username
         I_WORKFLOW_CHECK = lv_i_workflow_check
         I_CHANGE_CLEARED_ITEMS = lv_i_change_cleared_items
    TABLES
         T_KOCHANGES = lt_t_kochanges
         T_OPCHANGES = lt_t_opchanges
         T_OPWCHANGES = lt_t_opwchanges
         T_CHANGEDOPS = lt_t_changedops
         T_CHANGEDOPWS = lt_t_changedopws
         T_FKKOPCHL = lt_t_fkkopchl
    EXCEPTIONS
        ERR_LOCK_CHANGE = 1
        ERR_DOC_CHANGE = 2
. " FKK_DOCUMENT_CHANGE_COMPLETE




ABAP code using 7.40 inline data declarations to call FM FKK_DOCUMENT_CHANGE_COMPLETE

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 OPBEL FROM FKKKO INTO @DATA(ld_i_opbel).
 
 
 
 
 
 
"SELECT single UNAME FROM SYST INTO @DATA(ld_i_username).
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_workflow_check).
DATA(ld_i_workflow_check) = 'X'.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_change_cleared_items).
DATA(ld_i_change_cleared_items) = ' '.
 
 


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!