SAP BAPI_MEDDOC_CREATE_LINK Function Module for IS-H*MED: Create Document Link
BAPI_MEDDOC_CREATE_LINK is a standard bapi meddoc create link SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H*MED: Create Document Link 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 bapi meddoc create link FM, simply by entering the name BAPI_MEDDOC_CREATE_LINK into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1400
Program Name: SAPL1400
Main Program: SAPL1400
Appliation area:
Release date: 20-Aug-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_MEDDOC_CREATE_LINK 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 'BAPI_MEDDOC_CREATE_LINK'"IS-H*MED: Create Document Link.
EXPORTING
* ISHMED_LINK = ' ' "Checkbox: Create Document Link
* DEFAULT_DOC_OU = '0' "Presetting of Documenting OU
* ARCHIVE_LINK = ' ' "Checkbox: Create Link to Archived Document
* SAPSTORAGE = ' ' "Checkbox: Store Using SAP Document Management
DOCUMENTDATA_IN = "Changeable Doc. Management Data - WITHOUT Movement, Service, Request
* ARCHIVEDATA = "Code for Archived Documents
* HOSTNAME = "Name of Frontend
* SAPSTORAGEDATA = "Document Management System Document Data
* VERSION_CREATE = ' ' "Checkbox: Create Document Version
* TESTRUN = ' ' "Checkbox: Test Run Without Database Modifications
IMPORTING
WORST_RETURNED_MSGTY = "Most Severe Message Type
DOCUMENTDATA = "All Doc. Management Data - WITHOUT Movement, Service, Request
TABLES
* RETURN = "Return Messages
* MOVEMENT_IN = "Movement Code
* CASESERVICE_IN = "Service Code
* REQUEST_IN = "Request Code
* MOVEMENT = "Movement Data of a Document
* CASESERVICE = "Service Data of a Document
* REQUEST = "Requset Data of a Document
IMPORTING Parameters details for BAPI_MEDDOC_CREATE_LINK
ISHMED_LINK - Checkbox: Create Document Link
Data type: BAPINALL-XINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEFAULT_DOC_OU - Presetting of Documenting OU
Data type: BAPIMEDDOC_PAR-DEFAULT_DOC_OUDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIVE_LINK - Checkbox: Create Link to Archived Document
Data type: BAPINALL-XINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SAPSTORAGE - Checkbox: Store Using SAP Document Management
Data type: BAPINALL-XINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DOCUMENTDATA_IN - Changeable Doc. Management Data - WITHOUT Movement, Service, Request
Data type: BAPIMEDDOC_DATAINOptional: No
Call by Reference: No ( called with pass by value option)
ARCHIVEDATA - Code for Archived Documents
Data type: BAPIMEDDOC_ARCHIVEOptional: Yes
Call by Reference: No ( called with pass by value option)
HOSTNAME - Name of Frontend
Data type: BAPI_DOC_AUX-HOSTNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
SAPSTORAGEDATA - Document Management System Document Data
Data type: BAPI_DOC_FILES2Optional: Yes
Call by Reference: No ( called with pass by value option)
VERSION_CREATE - Checkbox: Create Document Version
Data type: BAPINALL-XINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Checkbox: Test Run Without Database Modifications
Data type: BAPINALL-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_MEDDOC_CREATE_LINK
WORST_RETURNED_MSGTY - Most Severe Message Type
Data type: BAPINALL-WORSTRETMSGOptional: No
Call by Reference: No ( called with pass by value option)
DOCUMENTDATA - All Doc. Management Data - WITHOUT Movement, Service, Request
Data type: BAPIMEDDOC_DATAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_MEDDOC_CREATE_LINK
RETURN - Return Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
MOVEMENT_IN - Movement Code
Data type: BAPIMEDDOC_MOVEINOptional: Yes
Call by Reference: Yes
CASESERVICE_IN - Service Code
Data type: BAPIMEDDOC_SERVINOptional: Yes
Call by Reference: Yes
REQUEST_IN - Request Code
Data type: BAPIMEDDOC_REQINOptional: Yes
Call by Reference: Yes
MOVEMENT - Movement Data of a Document
Data type: BAPIMEDDOC_MOVEOptional: Yes
Call by Reference: Yes
CASESERVICE - Service Data of a Document
Data type: BAPIMEDDOC_SERVOptional: Yes
Call by Reference: Yes
REQUEST - Requset Data of a Document
Data type: BAPIMEDDOC_REQOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_MEDDOC_CREATE_LINK 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: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_ishmed_link | TYPE BAPINALL-XIND, " SPACE | |||
| lv_worst_returned_msgty | TYPE BAPINALL-WORSTRETMSG, " | |||
| lv_default_doc_ou | TYPE BAPIMEDDOC_PAR-DEFAULT_DOC_OU, " '0' | |||
| lt_movement_in | TYPE STANDARD TABLE OF BAPIMEDDOC_MOVEIN, " | |||
| lv_archive_link | TYPE BAPINALL-XIND, " SPACE | |||
| lv_documentdata | TYPE BAPIMEDDOC_DATA, " | |||
| lv_sapstorage | TYPE BAPINALL-XIND, " SPACE | |||
| lt_caseservice_in | TYPE STANDARD TABLE OF BAPIMEDDOC_SERVIN, " | |||
| lt_request_in | TYPE STANDARD TABLE OF BAPIMEDDOC_REQIN, " | |||
| lv_documentdata_in | TYPE BAPIMEDDOC_DATAIN, " | |||
| lt_movement | TYPE STANDARD TABLE OF BAPIMEDDOC_MOVE, " | |||
| lv_archivedata | TYPE BAPIMEDDOC_ARCHIVE, " | |||
| lv_hostname | TYPE BAPI_DOC_AUX-HOSTNAME, " | |||
| lt_caseservice | TYPE STANDARD TABLE OF BAPIMEDDOC_SERV, " | |||
| lt_request | TYPE STANDARD TABLE OF BAPIMEDDOC_REQ, " | |||
| lv_sapstoragedata | TYPE BAPI_DOC_FILES2, " | |||
| lv_version_create | TYPE BAPINALL-XIND, " SPACE | |||
| lv_testrun | TYPE BAPINALL-TESTRUN. " SPACE |
|   CALL FUNCTION 'BAPI_MEDDOC_CREATE_LINK' "IS-H*MED: Create Document Link |
| EXPORTING | ||
| ISHMED_LINK | = lv_ishmed_link | |
| DEFAULT_DOC_OU | = lv_default_doc_ou | |
| ARCHIVE_LINK | = lv_archive_link | |
| SAPSTORAGE | = lv_sapstorage | |
| DOCUMENTDATA_IN | = lv_documentdata_in | |
| ARCHIVEDATA | = lv_archivedata | |
| HOSTNAME | = lv_hostname | |
| SAPSTORAGEDATA | = lv_sapstoragedata | |
| VERSION_CREATE | = lv_version_create | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| WORST_RETURNED_MSGTY | = lv_worst_returned_msgty | |
| DOCUMENTDATA | = lv_documentdata | |
| TABLES | ||
| RETURN | = lt_return | |
| MOVEMENT_IN | = lt_movement_in | |
| CASESERVICE_IN | = lt_caseservice_in | |
| REQUEST_IN | = lt_request_in | |
| MOVEMENT | = lt_movement | |
| CASESERVICE | = lt_caseservice | |
| REQUEST | = lt_request | |
| . " BAPI_MEDDOC_CREATE_LINK | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_MEDDOC_CREATE_LINK
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 XIND FROM BAPINALL INTO @DATA(ld_ishmed_link). | ||||
| DATA(ld_ishmed_link) | = ' '. | |||
| "SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty). | ||||
| "SELECT single DEFAULT_DOC_OU FROM BAPIMEDDOC_PAR INTO @DATA(ld_default_doc_ou). | ||||
| DATA(ld_default_doc_ou) | = '0'. | |||
| "SELECT single XIND FROM BAPINALL INTO @DATA(ld_archive_link). | ||||
| DATA(ld_archive_link) | = ' '. | |||
| "SELECT single XIND FROM BAPINALL INTO @DATA(ld_sapstorage). | ||||
| DATA(ld_sapstorage) | = ' '. | |||
| "SELECT single HOSTNAME FROM BAPI_DOC_AUX INTO @DATA(ld_hostname). | ||||
| "SELECT single XIND FROM BAPINALL INTO @DATA(ld_version_create). | ||||
| DATA(ld_version_create) | = ' '. | |||
| "SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects