SAP SOTR_API_WB_TRANSLATE Function Module for

Search SAP Function Modules

SOTR_API_WB_TRANSLATE is a standard sotr api wb translate 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 sotr api wb translate FM, simply by entering the name SOTR_API_WB_TRANSLATE into the relevant SAP transaction such as SE37 or SE38.

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

Function SOTR_API_WB_TRANSLATE 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 'SOTR_API_WB_TRANSLATE'"
  EXPORTING
*  SOURCE_LANGU = SY-LANGU "SAP R/3 System, Current Language
   TARGET_LANGU =  "SAP R/3 System, Current Language
   PGMID =  "Program ID in requests and tasks
   OBJECT =  "Object Type
   OBJ_NAME =  "Object Name in Object List
*  FLAG_STRING =  "
*  EDIT_MODE = 'T' "Character Field Length 1

EXCEPTIONS
   NO_ENTRY_FOUND = 1    INTERNAL_ERROR = 2    NO_AUTHORIZATION = 3    ERROR_IN_CONTEXT = 4    USER_CANCELLED = 5    ERROR_IN_TRANSPORT_REQUEST = 6 

.

IMPORTING Parameters details for SOTR_API_WB_TRANSLATE

SOURCE_LANGU - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: No
Call by Reference: No ( called with pass by value option)

TARGET_LANGU - SAP R/3 System, Current Language

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

PGMID - Program ID in requests and tasks

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

OBJECT - Object Type

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

OBJ_NAME - Object Name in Object List

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

FLAG_STRING -

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

EDIT_MODE - Character Field Length 1

Data type: CHAR01
Default: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_CONTEXT -

Data type:
Optional: No
Call by Reference: Yes

USER_CANCELLED -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_TRANSPORT_REQUEST -

Data type:
Optional: No
Call by Reference: Yes

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

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