SAP SRM_DOCUMENT_GET_VERSION_LIST Function Module for SRM: Get Document Content with File Transfer

Search SAP Function Modules

SRM_DOCUMENT_GET_VERSION_LIST is a standard srm document get version list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SRM: Get Document Content with File Transfer 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 srm document get version list FM, simply by entering the name SRM_DOCUMENT_GET_VERSION_LIST into the relevant SAP transaction such as SE37 or SE38.

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

Function SRM_DOCUMENT_GET_VERSION_LIST 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 'SRM_DOCUMENT_GET_VERSION_LIST'"SRM: Get Document Content with File Transfer
  EXPORTING
   OBJECTID =  "Internal Document ID
   DOCUMENTCLASS =  "Location of Document
*  DOC_CONTEXT =  "Access Context: RMS ID and SPS ID

 IMPORTING
   RETURN =  "Return Parameter

TABLES
   VERSION_TAB =  "Table of Document Files

EXCEPTIONS
   INTERNAL_ERROR = 1    PARAMETER_ERROR = 2    NOT_AUTHORIZED = 3    DOC_NOT_FOUND = 4 

.

IMPORTING Parameters details for SRM_DOCUMENT_GET_VERSION_LIST

OBJECTID - Internal Document ID

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

DOCUMENTCLASS - Location of Document

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

DOC_CONTEXT - Access Context: RMS ID and SPS ID

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

EXPORTING Parameters details for SRM_DOCUMENT_GET_VERSION_LIST

RETURN - Return Parameter

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

TABLES Parameters details for SRM_DOCUMENT_GET_VERSION_LIST

VERSION_TAB - Table of Document Files

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

EXCEPTIONS details

INTERNAL_ERROR - Internal Error

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

PARAMETER_ERROR - Parameter error

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

NOT_AUTHORIZED - No Authorization

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

DOC_NOT_FOUND - Document Not Found

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

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

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