SAP FKK_SAMPLE_3601 Function Module for Check Industry-Specific Registered Objects
FKK_SAMPLE_3601 is a standard fkk sample 3601 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Industry-Specific Registered Objects 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 fkk sample 3601 FM, simply by entering the name FKK_SAMPLE_3601 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKB_CS1
Program Name: SAPLFKB_CS1
Main Program: SAPLFKB_CS1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_SAMPLE_3601 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_SAMPLE_3601'"Check Industry-Specific Registered Objects.
EXPORTING
I_BTD_REFERENCE = "Business Transaction Document Reference
IMPORTING
E_OBJTYP = "Object Type
E_OBJKEY = "Object Key
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FKK_SAMPLE_3601
I_BTD_REFERENCE - Business Transaction Document Reference
Data type: FKK_BUS_TRANS_DOC_REF_INTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FKK_SAMPLE_3601
E_OBJTYP - Object Type
Data type: OBJTYP_KKOptional: No
Call by Reference: Yes
E_OBJKEY - Object Key
Data type: OBJKY_KKOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED - Unable to convert external key
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_SAMPLE_3601 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_failed | TYPE STRING, " | |||
| lv_e_objtyp | TYPE OBJTYP_KK, " | |||
| lv_i_btd_reference | TYPE FKK_BUS_TRANS_DOC_REF_INT, " | |||
| lv_e_objkey | TYPE OBJKY_KK. " |
|   CALL FUNCTION 'FKK_SAMPLE_3601' "Check Industry-Specific Registered Objects |
| EXPORTING | ||
| I_BTD_REFERENCE | = lv_i_btd_reference | |
| IMPORTING | ||
| E_OBJTYP | = lv_e_objtyp | |
| E_OBJKEY | = lv_e_objkey | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FKK_SAMPLE_3601 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_3601
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