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

Function UMK_DOCUMENT_INFO_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 'UMK_DOCUMENT_INFO_GET'".
EXPORTING
I_OBJNAME = "
I_OBJVERS = "
* I_DOCID = "
IMPORTING
ET_COMPONENTS = "
ET_SIGNATURE = "
EXCEPTIONS
NO_DOCUMENT_FOUND = 1 FAILED = 2
IMPORTING Parameters details for UMK_DOCUMENT_INFO_GET
I_OBJNAME -
Data type: UMK_Y_MEASOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJVERS -
Data type: UMK_Y_OBJVERSOptional: No
Call by Reference: No ( called with pass by value option)
I_DOCID -
Data type: BDS_DOCIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UMK_DOCUMENT_INFO_GET
ET_COMPONENTS -
Data type: SBDST_COMPONENTSOptional: No
Call by Reference: Yes
ET_SIGNATURE -
Data type: SBDST_SIGNATUREOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_DOCUMENT_FOUND -
Data type:Optional: No
Call by Reference: Yes
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UMK_DOCUMENT_INFO_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_i_objname | TYPE UMK_Y_MEAS, " | |||
| lv_et_components | TYPE SBDST_COMPONENTS, " | |||
| lv_no_document_found | TYPE SBDST_COMPONENTS, " | |||
| lv_failed | TYPE SBDST_COMPONENTS, " | |||
| lv_i_objvers | TYPE UMK_Y_OBJVERS, " | |||
| lv_et_signature | TYPE SBDST_SIGNATURE, " | |||
| lv_i_docid | TYPE BDS_DOCID. " |
|   CALL FUNCTION 'UMK_DOCUMENT_INFO_GET' " |
| EXPORTING | ||
| I_OBJNAME | = lv_i_objname | |
| I_OBJVERS | = lv_i_objvers | |
| I_DOCID | = lv_i_docid | |
| IMPORTING | ||
| ET_COMPONENTS | = lv_et_components | |
| ET_SIGNATURE | = lv_et_signature | |
| EXCEPTIONS | ||
| NO_DOCUMENT_FOUND = 1 | ||
| FAILED = 2 | ||
| . " UMK_DOCUMENT_INFO_GET | ||
ABAP code using 7.40 inline data declarations to call FM UMK_DOCUMENT_INFO_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.Search for further information about these or an SAP related objects