SAP ALV_BDS_GET_TEMPLATE Function Module for

Search SAP Function Modules

ALV_BDS_GET_TEMPLATE is a standard alv bds get template 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 alv bds get template FM, simply by entering the name ALV_BDS_GET_TEMPLATE into the relevant SAP transaction such as SE37 or SE38.

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

Function ALV_BDS_GET_TEMPLATE 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 'ALV_BDS_GET_TEMPLATE'"
  EXPORTING
   I_CLASSNAME =  "Business Document Service: Class Name
   I_CLASSTYPE =  "Business Document Service: Class Type
*  I_CLIENT =  "Client
   I_OBJECT_KEY =  "Business Document Service: Object Key
   I_MIMETYPE =  "Business Document Service: MIME type
   I_REF_TO_CL_BDS_DOCUMENT =  "

CHANGING
   CT_ALV_BDS =  "BDS Table
   CT_COMPONENTS =  "
   CT_SIGNATURE =  "

EXCEPTIONS
   ERROR_KPRO = 1    INTERNAL_ERROR = 2    NOTHING_FOUND = 3    NOT_ALLOWED = 4    NOT_AUTHORIZED = 5    PARAMETER_ERROR = 6 

.

IMPORTING Parameters details for ALV_BDS_GET_TEMPLATE

I_CLASSNAME - Business Document Service: Class Name

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

I_CLASSTYPE - Business Document Service: Class Type

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

I_CLIENT - Client

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

I_OBJECT_KEY - Business Document Service: Object Key

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

I_MIMETYPE - Business Document Service: MIME type

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

I_REF_TO_CL_BDS_DOCUMENT -

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

CHANGING Parameters details for ALV_BDS_GET_TEMPLATE

CT_ALV_BDS - BDS Table

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

CT_COMPONENTS -

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

CT_SIGNATURE -

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

EXCEPTIONS details

ERROR_KPRO -

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

INTERNAL_ERROR -

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

NOTHING_FOUND -

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

NOT_ALLOWED -

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

NOT_AUTHORIZED -

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

PARAMETER_ERROR -

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

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

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