LXE_TS_API_CREATE_PROPOSAL SAP Function module - Creates a proposal

LXE_TS_API_CREATE_PROPOSAL 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_CREATE_PROPOSAL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LXE_TS_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM LXE_TS_API_CREATE_PROPOSAL - LXE TS API CREATE PROPOSAL

CALL FUNCTION 'LXE_TS_API_CREATE_PROPOSAL' "Creates a proposal
  EXPORTING
    source_lang =               " lxeisolang    Translation Language
    target_lang =               " lxeisolang    Translation Language
    source_text =               " lxeunitlin    Translation Unit for Short Text (Line)
    target_text =               " lxeunitlin    Translation Unit for Short Text (Line)
    system_standard =           " lxebool       Boolean
    domain =                    " lxedomanam    Domain Name
    status =                    " lxepp_stat    Default Status
*   creator =                   " uname         User Name
  EXCEPTIONS
    UNAUTHORIZED = 1            "               Unauthorized
    UNKNOWN_LANGUAGE = 2        "               Unknown language
    UNKNOWN_DOMAIN = 3          "               Unknown domain
    INVALID_STATUS = 4          "               Invalid proposal status
    HASH_CREATION_FAILED = 5    "               Hash creation for proposal text failed
    PROP_CREATION_FAILED = 6    "               Proposal creation failed
    .  "  LXE_TS_API_CREATE_PROPOSAL

ABAP code example for Function Module LXE_TS_API_CREATE_PROPOSAL

The ABAP code below is a full code listing to execute function module LXE_TS_API_CREATE_PROPOSAL 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_source_lang) = 'Check type of data required'.

DATA(ld_target_lang) = 'Check type of data required'.

DATA(ld_source_text) = 'Check type of data required'.

DATA(ld_target_text) = 'Check type of data required'.

DATA(ld_system_standard) = 'Check type of data required'.

DATA(ld_domain) = 'Check type of data required'.

DATA(ld_status) = 'Check type of data required'.

DATA(ld_creator) = 'Check type of data required'.
.

CALL FUNCTION 'LXE_TS_API_CREATE_PROPOSAL'
  EXPORTING
    source_lang =                ld_source_lang
    target_lang =                ld_target_lang
    source_text =                ld_source_text
    target_text =                ld_target_text
    system_standard =            ld_system_standard
    domain =                     ld_domain
    status =                     ld_status
*   creator =                    ld_creator
  EXCEPTIONS
    UNAUTHORIZED =               1
    UNKNOWN_LANGUAGE =           2
    UNKNOWN_DOMAIN =             3
    INVALID_STATUS =             4
    HASH_CREATION_FAILED =       5
    PROP_CREATION_FAILED =       6
    .  "  LXE_TS_API_CREATE_PROPOSAL

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
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_source_lang
 
 TYPE LXEISOLANG ,
ld_target_lang
 
 TYPE LXEISOLANG ,
ld_source_text
 
 TYPE LXEUNITLIN ,
ld_target_text
 
 TYPE LXEUNITLIN ,
ld_system_standard
 
 TYPE LXEBOOL ,
ld_domain
 
 TYPE LXEDOMANAM ,
ld_status
 
 TYPE LXEPP_STAT ,
ld_creator
 
 TYPE UNAME .


ld_source_lang = 'Check type of data required'.
ld_target_lang = 'Check type of data required'.
ld_source_text = 'Check type of data required'.
ld_target_text = 'Check type of data required'.
ld_system_standard = 'Check type of data required'.
ld_domain = 'Check type of data required'.
ld_status = 'Check type of data required'.
ld_creator = 'Check type of data required'.