SAP FKK_DISPUTE_INSERT_OBJECTS Function Module for









FKK_DISPUTE_INSERT_OBJECTS is a standard fkk dispute insert objects 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 dispute insert objects FM, simply by entering the name FKK_DISPUTE_INSERT_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKK_DM_SRV
Program Name: SAPLFKK_DM_SRV
Main Program: SAPLFKK_DM_SRV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FKK_DISPUTE_INSERT_OBJECTS 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_DISPUTE_INSERT_OBJECTS'"
  EXPORTING
*  I_SAVE = 'X' "
*  I_ACTION = '2' "
*  IT_OBJECTS =  "
*  IT_ATTRIBUTES =  "FSCM-DM Integration: Attribute Value
*  IT_NOTES =  "
*  I_NO_COMMUNICATION = ' ' "
*  I_EXTERNAL_GUID = ' ' "
*  I_COMMIT_ALLOWED = 'X' "

 IMPORTING
   E_RETURNDATA =  "FICA-DM: Dispute - Return Data
   E_COMMIT_REQUESTED =  "COMMIT WORK is Necessary
   ET_ATTR_CHG =  "

TABLES
*  T_RETURN =  "Return Parameter(s)
.



IMPORTING Parameters details for FKK_DISPUTE_INSERT_OBJECTS

I_SAVE -

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

I_ACTION -

Data type: FDM_ACTION
Default: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_OBJECTS -

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

IT_ATTRIBUTES - FSCM-DM Integration: Attribute Value

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

IT_NOTES -

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

I_NO_COMMUNICATION -

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

I_EXTERNAL_GUID -

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

I_COMMIT_ALLOWED -

Data type: BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FKK_DISPUTE_INSERT_OBJECTS

E_RETURNDATA - FICA-DM: Dispute - Return Data

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

E_COMMIT_REQUESTED - COMMIT WORK is Necessary

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

ET_ATTR_CHG -

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

TABLES Parameters details for FKK_DISPUTE_INSERT_OBJECTS

T_RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for FKK_DISPUTE_INSERT_OBJECTS 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_save  TYPE BOOLE_D, "   'X'
lt_t_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_e_returndata  TYPE FKK_DM_RETURN, "   
lv_i_action  TYPE FDM_ACTION, "   '2'
lv_e_commit_requested  TYPE BOOLEAN, "   
lv_it_objects  TYPE FDM_T_AR_OBJECTS, "   
lv_et_attr_chg  TYPE FDM_T_ATTRIBUTE, "   
lv_it_attributes  TYPE FDM_T_ATTRIBUTE, "   
lv_it_notes  TYPE TLINETAB, "   
lv_i_no_communication  TYPE XFELD, "   SPACE
lv_i_external_guid  TYPE SYSUUID_C, "   SPACE
lv_i_commit_allowed  TYPE BOOLEAN. "   'X'

  CALL FUNCTION 'FKK_DISPUTE_INSERT_OBJECTS'  "
    EXPORTING
         I_SAVE = lv_i_save
         I_ACTION = lv_i_action
         IT_OBJECTS = lv_it_objects
         IT_ATTRIBUTES = lv_it_attributes
         IT_NOTES = lv_it_notes
         I_NO_COMMUNICATION = lv_i_no_communication
         I_EXTERNAL_GUID = lv_i_external_guid
         I_COMMIT_ALLOWED = lv_i_commit_allowed
    IMPORTING
         E_RETURNDATA = lv_e_returndata
         E_COMMIT_REQUESTED = lv_e_commit_requested
         ET_ATTR_CHG = lv_et_attr_chg
    TABLES
         T_RETURN = lt_t_return
. " FKK_DISPUTE_INSERT_OBJECTS




ABAP code using 7.40 inline data declarations to call FM FKK_DISPUTE_INSERT_OBJECTS

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.

DATA(ld_i_save) = 'X'.
 
 
 
DATA(ld_i_action) = '2'.
 
 
 
 
 
 
DATA(ld_i_no_communication) = ' '.
 
DATA(ld_i_external_guid) = ' '.
 
DATA(ld_i_commit_allowed) = 'X'.
 


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!