SAP UI_LIST_OF_DOCS_UPD Function Module for
UI_LIST_OF_DOCS_UPD is a standard ui list of docs upd 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 ui list of docs upd FM, simply by entering the name UI_LIST_OF_DOCS_UPD into the relevant SAP transaction such as SE37 or SE38.
Function Group: UI_SERVICES
Program Name: SAPLUI_SERVICES
Main Program: SAPLUI_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UI_LIST_OF_DOCS_UPD 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 'UI_LIST_OF_DOCS_UPD'".
EXPORTING
* I_RFCDEST = "Logical Destination (Specified when Calling Function)
IT_CHAS = "
* IT_DOC_AS_CONTENT = "ASCII Table
* I_DOC_ID = "
* I_BDS_DOC_ID = "Business Document Service: Document ID
I_DOC_TITLE = "Document title (documents in the SEM-BIC databasis)
I_DOC_TYPE = "Business Document Service: MIME type
I_TODO = "
I_SEMAPPL = "SEM application to be called
I_DOC_SIZE = "
* IT_DOC_CONTENT = "
IMPORTING
E_DOC_ID = "
E_BDS_DOC_ID = "Business Document Service: Document ID
EXCEPTIONS
CREATE_ERROR = 1 UPDATE_ERROR = 2 DELETE_ERROR = 3 RFC_ERROR = 4 NO_DOC_ID = 5 NO_BDS_DOC_ID = 6
IMPORTING Parameters details for UI_LIST_OF_DOCS_UPD
I_RFCDEST - Logical Destination (Specified when Calling Function)
Data type: RFCDESTOptional: Yes
Call by Reference: Yes
IT_CHAS -
Data type: UIYT_CHASOptional: No
Call by Reference: Yes
IT_DOC_AS_CONTENT - ASCII Table
Data type: UIYT_AS_CONTENTOptional: Yes
Call by Reference: Yes
I_DOC_ID -
Data type: UI_Y_DOC_IDOptional: Yes
Call by Reference: Yes
I_BDS_DOC_ID - Business Document Service: Document ID
Data type: BDS_DOCIDOptional: Yes
Call by Reference: Yes
I_DOC_TITLE - Document title (documents in the SEM-BIC databasis)
Data type: UI_Y_DOC_TITLEOptional: No
Call by Reference: Yes
I_DOC_TYPE - Business Document Service: MIME type
Data type: BDS_MIMETPOptional: No
Call by Reference: Yes
I_TODO -
Data type: UI_Y_TODOFLOptional: No
Call by Reference: Yes
I_SEMAPPL - SEM application to be called
Data type: UI_Y_SEMAPPLOptional: No
Call by Reference: Yes
I_DOC_SIZE -
Data type: BDS_COMPSIOptional: No
Call by Reference: Yes
IT_DOC_CONTENT -
Data type: UIYT_DOC_CONTENTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for UI_LIST_OF_DOCS_UPD
E_DOC_ID -
Data type: UI_Y_DOC_IDOptional: No
Call by Reference: Yes
E_BDS_DOC_ID - Business Document Service: Document ID
Data type: BDS_DOCIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
CREATE_ERROR - Error creating document
Data type:Optional: No
Call by Reference: Yes
UPDATE_ERROR -
Data type:Optional: No
Call by Reference: Yes
DELETE_ERROR - Error deleting the document
Data type:Optional: No
Call by Reference: Yes
RFC_ERROR - Error During RFC Call
Data type:Optional: No
Call by Reference: Yes
NO_DOC_ID -
Data type:Optional: No
Call by Reference: Yes
NO_BDS_DOC_ID -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UI_LIST_OF_DOCS_UPD 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_e_doc_id | TYPE UI_Y_DOC_ID, " | |||
| lv_i_rfcdest | TYPE RFCDEST, " | |||
| lv_create_error | TYPE RFCDEST, " | |||
| lv_it_chas | TYPE UIYT_CHAS, " | |||
| lv_it_doc_as_content | TYPE UIYT_AS_CONTENT, " | |||
| lv_i_doc_id | TYPE UI_Y_DOC_ID, " | |||
| lv_e_bds_doc_id | TYPE BDS_DOCID, " | |||
| lv_update_error | TYPE BDS_DOCID, " | |||
| lv_delete_error | TYPE BDS_DOCID, " | |||
| lv_i_bds_doc_id | TYPE BDS_DOCID, " | |||
| lv_rfc_error | TYPE BDS_DOCID, " | |||
| lv_i_doc_title | TYPE UI_Y_DOC_TITLE, " | |||
| lv_no_doc_id | TYPE UI_Y_DOC_TITLE, " | |||
| lv_i_doc_type | TYPE BDS_MIMETP, " | |||
| lv_i_todo | TYPE UI_Y_TODOFL, " | |||
| lv_no_bds_doc_id | TYPE UI_Y_TODOFL, " | |||
| lv_i_semappl | TYPE UI_Y_SEMAPPL, " | |||
| lv_i_doc_size | TYPE BDS_COMPSI, " | |||
| lv_it_doc_content | TYPE UIYT_DOC_CONTENT. " |
|   CALL FUNCTION 'UI_LIST_OF_DOCS_UPD' " |
| EXPORTING | ||
| I_RFCDEST | = lv_i_rfcdest | |
| IT_CHAS | = lv_it_chas | |
| IT_DOC_AS_CONTENT | = lv_it_doc_as_content | |
| I_DOC_ID | = lv_i_doc_id | |
| I_BDS_DOC_ID | = lv_i_bds_doc_id | |
| I_DOC_TITLE | = lv_i_doc_title | |
| I_DOC_TYPE | = lv_i_doc_type | |
| I_TODO | = lv_i_todo | |
| I_SEMAPPL | = lv_i_semappl | |
| I_DOC_SIZE | = lv_i_doc_size | |
| IT_DOC_CONTENT | = lv_it_doc_content | |
| IMPORTING | ||
| E_DOC_ID | = lv_e_doc_id | |
| E_BDS_DOC_ID | = lv_e_bds_doc_id | |
| EXCEPTIONS | ||
| CREATE_ERROR = 1 | ||
| UPDATE_ERROR = 2 | ||
| DELETE_ERROR = 3 | ||
| RFC_ERROR = 4 | ||
| NO_DOC_ID = 5 | ||
| NO_BDS_DOC_ID = 6 | ||
| . " UI_LIST_OF_DOCS_UPD | ||
ABAP code using 7.40 inline data declarations to call FM UI_LIST_OF_DOCS_UPD
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