SAP Function Modules

LXE_TS_API_GET_OBJECT SAP Function module - Export an object







LXE_TS_API_GET_OBJECT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LXE_TS_API_GET_OBJECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LXE_TS_API_AREA_GEN1
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM LXE_TS_API_GET_OBJECT - LXE TS API GET OBJECT





CALL FUNCTION 'LXE_TS_API_GET_OBJECT' "Export an object
  EXPORTING
    transarea =                 " lxecustmnr    Translation Area
    objname =                   " lxeobjname    Name of Translation Object
    language =                  " lxeisolang    ISO Language ID
  IMPORTING
    orig_lang =                 " lxeisolang    ISO Language ID
    collnam =                   " lxecollnam    Collection Name
    domanam =                   " lxedomanam    Domain Name
    developer =                 " lxeunitlin    Developer
    description =               " lxeunitlin    Description
    pc_ad =                     " lxe_pc_ad_s   Path Data
  TABLES
    ex_pc_ap_xml =              " lxe_pc_ap_xml  PC* Objects: Texts
    ex_pcx_tx_xml =             " lxe_pcx_tx_xml  PCX Objects: Texts
    ex_pcy_tx_xml =             " lxe_pcy_tx_xml  PCY Objects: Texts
    ex_pcz_tx_xml =             " lxe_pcz_tx_xml  PCZ Objects: Texts
  EXCEPTIONS
    UNKNOWN_TRANS_AREA = 1      "               Unknown translation area
    UNSUPPORTED_TRANS_AREA_TYPE = 2  "          Unsupported translation area type
    OBJECT_NOT_FOUND = 3        "               Object was not found
    UNKNOWN_LANGUAGE = 4        "               Language is unknown
    EXPORT_ERROR = 5            "               The export failed
    UNAUTHORIZED = 6            "               Unauthorized
    LOCKED = 7                  "               Operation is currently locked
    .  "  LXE_TS_API_GET_OBJECT

ABAP code example for Function Module LXE_TS_API_GET_OBJECT





The ABAP code below is a full code listing to execute function module LXE_TS_API_GET_OBJECT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_orig_lang  TYPE LXEISOLANG ,
ld_collnam  TYPE LXECOLLNAM ,
ld_domanam  TYPE LXEDOMANAM ,
ld_developer  TYPE LXEUNITLIN ,
ld_description  TYPE LXEUNITLIN ,
ld_pc_ad  TYPE LXE_PC_AD_S ,
it_ex_pc_ap_xml  TYPE STANDARD TABLE OF LXE_PC_AP_XML,"TABLES PARAM
wa_ex_pc_ap_xml  LIKE LINE OF it_ex_pc_ap_xml ,
it_ex_pcx_tx_xml  TYPE STANDARD TABLE OF LXE_PCX_TX_XML,"TABLES PARAM
wa_ex_pcx_tx_xml  LIKE LINE OF it_ex_pcx_tx_xml ,
it_ex_pcy_tx_xml  TYPE STANDARD TABLE OF LXE_PCY_TX_XML,"TABLES PARAM
wa_ex_pcy_tx_xml  LIKE LINE OF it_ex_pcy_tx_xml ,
it_ex_pcz_tx_xml  TYPE STANDARD TABLE OF LXE_PCZ_TX_XML,"TABLES PARAM
wa_ex_pcz_tx_xml  LIKE LINE OF it_ex_pcz_tx_xml .

DATA(ld_transarea) = 'Check type of data required'.
DATA(ld_objname) = 'Check type of data required'.
DATA(ld_language) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ex_pc_ap_xml to it_ex_pc_ap_xml.

"populate fields of struture and append to itab
append wa_ex_pcx_tx_xml to it_ex_pcx_tx_xml.

"populate fields of struture and append to itab
append wa_ex_pcy_tx_xml to it_ex_pcy_tx_xml.

"populate fields of struture and append to itab
append wa_ex_pcz_tx_xml to it_ex_pcz_tx_xml. . CALL FUNCTION 'LXE_TS_API_GET_OBJECT' EXPORTING transarea = ld_transarea objname = ld_objname language = ld_language IMPORTING orig_lang = ld_orig_lang collnam = ld_collnam domanam = ld_domanam developer = ld_developer description = ld_description pc_ad = ld_pc_ad TABLES ex_pc_ap_xml = it_ex_pc_ap_xml ex_pcx_tx_xml = it_ex_pcx_tx_xml ex_pcy_tx_xml = it_ex_pcy_tx_xml ex_pcz_tx_xml = it_ex_pcz_tx_xml EXCEPTIONS UNKNOWN_TRANS_AREA = 1 UNSUPPORTED_TRANS_AREA_TYPE = 2 OBJECT_NOT_FOUND = 3 UNKNOWN_LANGUAGE = 4 EXPORT_ERROR = 5 UNAUTHORIZED = 6 LOCKED = 7 . " LXE_TS_API_GET_OBJECT
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_orig_lang  TYPE LXEISOLANG ,
ld_transarea  TYPE LXECUSTMNR ,
it_ex_pc_ap_xml  TYPE STANDARD TABLE OF LXE_PC_AP_XML ,
wa_ex_pc_ap_xml  LIKE LINE OF it_ex_pc_ap_xml,
ld_collnam  TYPE LXECOLLNAM ,
ld_objname  TYPE LXEOBJNAME ,
it_ex_pcx_tx_xml  TYPE STANDARD TABLE OF LXE_PCX_TX_XML ,
wa_ex_pcx_tx_xml  LIKE LINE OF it_ex_pcx_tx_xml,
ld_domanam  TYPE LXEDOMANAM ,
ld_language  TYPE LXEISOLANG ,
it_ex_pcy_tx_xml  TYPE STANDARD TABLE OF LXE_PCY_TX_XML ,
wa_ex_pcy_tx_xml  LIKE LINE OF it_ex_pcy_tx_xml,
ld_developer  TYPE LXEUNITLIN ,
it_ex_pcz_tx_xml  TYPE STANDARD TABLE OF LXE_PCZ_TX_XML ,
wa_ex_pcz_tx_xml  LIKE LINE OF it_ex_pcz_tx_xml,
ld_description  TYPE LXEUNITLIN ,
ld_pc_ad  TYPE LXE_PC_AD_S .

ld_transarea = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ex_pc_ap_xml to it_ex_pc_ap_xml.
ld_objname = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ex_pcx_tx_xml to it_ex_pcx_tx_xml.
ld_language = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ex_pcy_tx_xml to it_ex_pcy_tx_xml.

"populate fields of struture and append to itab
append wa_ex_pcz_tx_xml to it_ex_pcz_tx_xml.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LXE_TS_API_GET_OBJECT or its description.