SAP FKK_CRM_ARIDOC_CREATE_PROXY Function Module for
FKK_CRM_ARIDOC_CREATE_PROXY is a standard fkk crm aridoc create proxy 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 crm aridoc create proxy FM, simply by entering the name FKK_CRM_ARIDOC_CREATE_PROXY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKCRM_ARIDOC
Program Name: SAPLFKCRM_ARIDOC
Main Program: SAPLFKCRM_ARIDOC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FKK_CRM_ARIDOC_CREATE_PROXY 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_CRM_ARIDOC_CREATE_PROXY'".
EXPORTING
IT_ARI_ATTR = "Attributes of Adjustment Request Items
* IT_REFERENCE = "Reference Objects for Adjustment Request
IV_HEADER_GUID = "Globally Unique Identifier
* IV_IS_DISPUTE = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* IV_OBJECT_ID = "Process ID
* IV_LOGSYS = "Logical System
* IV_UPLOAD_ID = "Unique Reference Number
* IT_CRM_KEY_INFO = "Table Type for BAPICRMKEY
IMPORTING
ET_RETURN = "Error Messages
IMPORTING Parameters details for FKK_CRM_ARIDOC_CREATE_PROXY
IT_ARI_ATTR - Attributes of Adjustment Request Items
Data type: FKK_CRM_ARI_ATTR_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_REFERENCE - Reference Objects for Adjustment Request
Data type: FKK_CRM_ARI_REF_TOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_HEADER_GUID - Globally Unique Identifier
Data type: GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_IS_DISPUTE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_ID - Process ID
Data type: CRMT_OBJECT_ID_DBOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGSYS - Logical System
Data type: LOGSYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_UPLOAD_ID - Unique Reference Number
Data type: REF_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_CRM_KEY_INFO - Table Type for BAPICRMKEY
Data type: BAPICRMKEY_TOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_CRM_ARIDOC_CREATE_PROXY
ET_RETURN - Error Messages
Data type: BAPIRET2_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_CRM_ARIDOC_CREATE_PROXY 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_return | TYPE BAPIRET2_TAB, " | |||
| lv_it_ari_attr | TYPE FKK_CRM_ARI_ATTR_T, " | |||
| lv_it_reference | TYPE FKK_CRM_ARI_REF_T, " | |||
| lv_iv_header_guid | TYPE GUID, " | |||
| lv_iv_is_dispute | TYPE BOOLE_D, " | |||
| lv_iv_object_id | TYPE CRMT_OBJECT_ID_DB, " | |||
| lv_iv_logsys | TYPE LOGSYSTEM, " | |||
| lv_iv_upload_id | TYPE REF_ID, " | |||
| lv_it_crm_key_info | TYPE BAPICRMKEY_T. " |
|   CALL FUNCTION 'FKK_CRM_ARIDOC_CREATE_PROXY' " |
| EXPORTING | ||
| IT_ARI_ATTR | = lv_it_ari_attr | |
| IT_REFERENCE | = lv_it_reference | |
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IV_IS_DISPUTE | = lv_iv_is_dispute | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_LOGSYS | = lv_iv_logsys | |
| IV_UPLOAD_ID | = lv_iv_upload_id | |
| IT_CRM_KEY_INFO | = lv_it_crm_key_info | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| . " FKK_CRM_ARIDOC_CREATE_PROXY | ||
ABAP code using 7.40 inline data declarations to call FM FKK_CRM_ARIDOC_CREATE_PROXY
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