SAP BAPI_MEDDOC_CREATE_LINK_PART Function Module for

Search SAP Function Modules

BAPI_MEDDOC_CREATE_LINK_PART is a standard bapi meddoc create link part 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 bapi meddoc create link part FM, simply by entering the name BAPI_MEDDOC_CREATE_LINK_PART into the relevant SAP transaction such as SE37 or SE38.

Function Group: 1400
Program Name: SAPL1400
Main Program: SAPL1400
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_MEDDOC_CREATE_LINK_PART 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_PART'"
  EXPORTING
*  ISHMED_LINK = ' ' "
*  TESTRUN = ' ' "
*  ARCHIVE_LINK = ' ' "
*  SAPSTORAGE = ' ' "
   DOCUMENT_KEY_SOURCE =  "
   DOCUMENT_PART_DATA =  "
*  ARCHIVEDATA =  "
*  HOSTNAME =  "
*  SAPSTORAGEDATA =  "
*  DEFAULT_DOC_OU = '0' "

 IMPORTING
   WORST_RETURNED_MSGTY =  "
   DOCUMENTDATA =  "

TABLES
*  RETURN =  "

.

IMPORTING Parameters details for BAPI_MEDDOC_CREATE_LINK_PART

ISHMED_LINK -

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

TESTRUN -

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

ARCHIVE_LINK -

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

SAPSTORAGE -

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

DOCUMENT_KEY_SOURCE -

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

DOCUMENT_PART_DATA -

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

ARCHIVEDATA -

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

HOSTNAME -

Data type: BAPI_DOC_AUX-HOSTNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAPSTORAGEDATA -

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

DEFAULT_DOC_OU -

Data type: BAPIMEDDOC_PAR-DEFAULT_DOC_OU
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_MEDDOC_CREATE_LINK_PART

WORST_RETURNED_MSGTY -

Data type: BAPINALL-WORSTRETMSG
Optional: No
Call by Reference: No ( called with pass by value option)

DOCUMENTDATA -

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

TABLES Parameters details for BAPI_MEDDOC_CREATE_LINK_PART

RETURN -

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

Copy and paste ABAP code example for BAPI_MEDDOC_CREATE_LINK_PART 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.

ABAP code using 7.40 inline data declarations to call FM BAPI_MEDDOC_CREATE_LINK_PART

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