SAP DOCU_NAME_CHECK Function Module for









DOCU_NAME_CHECK is a standard docu name check 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 docu name check FM, simply by entering the name DOCU_NAME_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDOC
Program Name: SAPLSDOC
Main Program: SAPLSDOC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DOCU_NAME_CHECK 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 'DOCU_NAME_CHECK'"
EXPORTING
IV_ID = "
IV_OBJECT_NAME = "
* IV_CHECK_FROM_SE61 = ' ' "

IMPORTING
EV_MESSAGE_NUMBER = "
EV_ALLOWED_SYMBOLS = "
.



IMPORTING Parameters details for DOCU_NAME_CHECK

IV_ID -

Data type: DOKU_ID
Optional: No
Call by Reference: Yes

IV_OBJECT_NAME -

Data type: DOKU_OBJ
Optional: No
Call by Reference: Yes

IV_CHECK_FROM_SE61 -

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

EXPORTING Parameters details for DOCU_NAME_CHECK

EV_MESSAGE_NUMBER -

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

EV_ALLOWED_SYMBOLS -

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

Copy and paste ABAP code example for DOCU_NAME_CHECK 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_iv_id  TYPE DOKU_ID, "   
lv_ev_message_number  TYPE SYMSGNO, "   
lv_iv_object_name  TYPE DOKU_OBJ, "   
lv_ev_allowed_symbols  TYPE SYMSGV, "   
lv_iv_check_from_se61  TYPE CHAR1. "   SPACE

  CALL FUNCTION 'DOCU_NAME_CHECK'  "
    EXPORTING
         IV_ID = lv_iv_id
         IV_OBJECT_NAME = lv_iv_object_name
         IV_CHECK_FROM_SE61 = lv_iv_check_from_se61
    IMPORTING
         EV_MESSAGE_NUMBER = lv_ev_message_number
         EV_ALLOWED_SYMBOLS = lv_ev_allowed_symbols
. " DOCU_NAME_CHECK




ABAP code using 7.40 inline data declarations to call FM DOCU_NAME_CHECK

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_iv_check_from_se61) = ' '.
 


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!