SAP SRET_DOCCLASS_GET Function Module for
SRET_DOCCLASS_GET is a standard sret docclass get 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 sret docclass get FM, simply by entering the name SRET_DOCCLASS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRCL
Program Name: SAPLSRCL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SRET_DOCCLASS_GET 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 'SRET_DOCCLASS_GET'".
EXPORTING
USER = "Index category identification
HIERARCHY = "Application Key
LANGU = "Language key (1 character)
LAISO = "Language According to ISO 639
* APPLKEY = 'MINING' "Application Key
TABLES
DOCTAB = "Document info for indexing (R/3 service API)
DOCCONTAB = "Document content - data stream ASCII TEXT / URL / file
CLASSTABLE = "Result Classes
EXCEPTIONS
CATID_UNKNOWN = 1 LANGUAGE_ERROR = 2 RFC_SYS_FAILURE = 3 RFC_COM_FAILURE = 4 NO_RFC_DEST = 5 CADID_UNKNOWN = 6
IMPORTING Parameters details for SRET_DOCCLASS_GET
USER - Index category identification
Data type: SY-UNAMEOptional: No
Call by Reference: Yes
HIERARCHY - Application Key
Data type: SRET_ATRVLOptional: No
Call by Reference: Yes
LANGU - Language key (1 character)
Data type: SRETIDLACI-LANGUOptional: No
Call by Reference: Yes
LAISO - Language According to ISO 639
Data type: SRETIDLACI-LAISOOptional: No
Call by Reference: Yes
APPLKEY - Application Key
Data type: SRETIDCTAT-APPLKEYDefault: 'MINING'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for SRET_DOCCLASS_GET
DOCTAB - Document info for indexing (R/3 service API)
Data type: SRETDOCINFOptional: No
Call by Reference: Yes
DOCCONTAB - Document content - data stream ASCII TEXT / URL / file
Data type: SRETDOCCONOptional: No
Call by Reference: Yes
CLASSTABLE - Result Classes
Data type: SRETRESCLSOptional: No
Call by Reference: Yes
EXCEPTIONS details
CATID_UNKNOWN -
Data type:Optional: No
Call by Reference: Yes
LANGUAGE_ERROR -
Data type:Optional: No
Call by Reference: Yes
RFC_SYS_FAILURE -
Data type:Optional: No
Call by Reference: Yes
RFC_COM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
NO_RFC_DEST -
Data type:Optional: No
Call by Reference: Yes
CADID_UNKNOWN -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SRET_DOCCLASS_GET 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_user | TYPE SY-UNAME, " | |||
| lt_doctab | TYPE STANDARD TABLE OF SRETDOCINF, " | |||
| lv_catid_unknown | TYPE SRETDOCINF, " | |||
| lt_doccontab | TYPE STANDARD TABLE OF SRETDOCCON, " | |||
| lv_hierarchy | TYPE SRET_ATRVL, " | |||
| lv_language_error | TYPE SRET_ATRVL, " | |||
| lv_langu | TYPE SRETIDLACI-LANGU, " | |||
| lt_classtable | TYPE STANDARD TABLE OF SRETRESCLS, " | |||
| lv_rfc_sys_failure | TYPE SRETRESCLS, " | |||
| lv_laiso | TYPE SRETIDLACI-LAISO, " | |||
| lv_rfc_com_failure | TYPE SRETIDLACI, " | |||
| lv_applkey | TYPE SRETIDCTAT-APPLKEY, " 'MINING' | |||
| lv_no_rfc_dest | TYPE SRETIDCTAT, " | |||
| lv_cadid_unknown | TYPE SRETIDCTAT. " |
|   CALL FUNCTION 'SRET_DOCCLASS_GET' " |
| EXPORTING | ||
| USER | = lv_user | |
| HIERARCHY | = lv_hierarchy | |
| LANGU | = lv_langu | |
| LAISO | = lv_laiso | |
| APPLKEY | = lv_applkey | |
| TABLES | ||
| DOCTAB | = lt_doctab | |
| DOCCONTAB | = lt_doccontab | |
| CLASSTABLE | = lt_classtable | |
| EXCEPTIONS | ||
| CATID_UNKNOWN = 1 | ||
| LANGUAGE_ERROR = 2 | ||
| RFC_SYS_FAILURE = 3 | ||
| RFC_COM_FAILURE = 4 | ||
| NO_RFC_DEST = 5 | ||
| CADID_UNKNOWN = 6 | ||
| . " SRET_DOCCLASS_GET | ||
ABAP code using 7.40 inline data declarations to call FM SRET_DOCCLASS_GET
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 UNAME FROM SY INTO @DATA(ld_user). | ||||
| "SELECT single LANGU FROM SRETIDLACI INTO @DATA(ld_langu). | ||||
| "SELECT single LAISO FROM SRETIDLACI INTO @DATA(ld_laiso). | ||||
| "SELECT single APPLKEY FROM SRETIDCTAT INTO @DATA(ld_applkey). | ||||
| DATA(ld_applkey) | = 'MINING'. | |||
Search for further information about these or an SAP related objects