SAP IWB_XML_TRANSL_EXPORT Function Module for









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

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



Function IWB_XML_TRANSL_EXPORT 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 'IWB_XML_TRANSL_EXPORT'"
  EXPORTING
   LANGUAGE =  "
   LOIO =  "Document LOIO
   PHIO =  "
   CONTEXT =  "Context
*  RESPONSIBLE =  "
   OBJECT_TYPE =  "Type of Translation Object
   DATA =  "

EXCEPTIONS
   ERROR = 1    RFC_ERROR = 2
.



IMPORTING Parameters details for IWB_XML_TRANSL_EXPORT

LANGUAGE -

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

LOIO - Document LOIO

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

PHIO -

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

CONTEXT - Context

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

RESPONSIBLE -

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

OBJECT_TYPE - Type of Translation Object

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

DATA -

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

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IWB_XML_TRANSL_EXPORT 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_error  TYPE STRING, "   
lv_language  TYPE LXEISOLANG, "   
lv_loio  TYPE SDOKOBJECT, "   
lv_rfc_error  TYPE SDOKOBJECT, "   
lv_phio  TYPE SDOKOBJECT, "   
lv_context  TYPE SDOKPROPTYS, "   
lv_responsible  TYPE SYUNAME, "   
lv_object_type  TYPE LXEOBJTYPE, "   
lv_data  TYPE XSTRING. "   

  CALL FUNCTION 'IWB_XML_TRANSL_EXPORT'  "
    EXPORTING
         LANGUAGE = lv_language
         LOIO = lv_loio
         PHIO = lv_phio
         CONTEXT = lv_context
         RESPONSIBLE = lv_responsible
         OBJECT_TYPE = lv_object_type
         DATA = lv_data
    EXCEPTIONS
        ERROR = 1
        RFC_ERROR = 2
. " IWB_XML_TRANSL_EXPORT




ABAP code using 7.40 inline data declarations to call FM IWB_XML_TRANSL_EXPORT

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!