SAP SLVC_EXPORT_XML_CALL_SCREEN Function Module for









SLVC_EXPORT_XML_CALL_SCREEN is a standard slvc export xml call screen 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 slvc export xml call screen FM, simply by entering the name SLVC_EXPORT_XML_CALL_SCREEN into the relevant SAP transaction such as SE37 or SE38.

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



Function SLVC_EXPORT_XML_CALL_SCREEN 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 'SLVC_EXPORT_XML_CALL_SCREEN'"
EXPORTING
T_XML_CHOICE = "
T_FIELDCAT = "
* DISPLAY_MODE = "

IMPORTING
RESULT = "
.



IMPORTING Parameters details for SLVC_EXPORT_XML_CALL_SCREEN

T_XML_CHOICE -

Data type: IF_SALV_BS_XML=>T_TYPE_XML_CHOICE
Optional: No
Call by Reference: Yes

T_FIELDCAT -

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

DISPLAY_MODE -

Data type: I
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SLVC_EXPORT_XML_CALL_SCREEN

RESULT -

Data type: IF_SALV_BS_XML=>S_TYPE_XML_CHOICE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SLVC_EXPORT_XML_CALL_SCREEN 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_result  TYPE IF_SALV_BS_XML=>S_TYPE_XML_CHOICE, "   
lv_t_xml_choice  TYPE IF_SALV_BS_XML=>T_TYPE_XML_CHOICE, "   
lv_t_fieldcat  TYPE LVC_T_FCAT, "   
lv_display_mode  TYPE I. "   

  CALL FUNCTION 'SLVC_EXPORT_XML_CALL_SCREEN'  "
    EXPORTING
         T_XML_CHOICE = lv_t_xml_choice
         T_FIELDCAT = lv_t_fieldcat
         DISPLAY_MODE = lv_display_mode
    IMPORTING
         RESULT = lv_result
. " SLVC_EXPORT_XML_CALL_SCREEN




ABAP code using 7.40 inline data declarations to call FM SLVC_EXPORT_XML_CALL_SCREEN

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!