SAP 1240_TRANSL_INT_EXT_LTXT Function Module for

Search SAP Function Modules

1240_TRANSL_INT_EXT_LTXT is a standard 1240 transl int ext ltxt 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 1240 transl int ext ltxt FM, simply by entering the name 1240_TRANSL_INT_EXT_LTXT into the relevant SAP transaction such as SE37 or SE38.

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

Function 1240_TRANSL_INT_EXT_LTXT 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 '1240_TRANSL_INT_EXT_LTXT'"
  EXPORTING
   CCIHS_LONGTEXTAPI =  "

CHANGING
   BAPI1240_LTXT =  "

.

IMPORTING Parameters details for 1240_TRANSL_INT_EXT_LTXT

CCIHS_LONGTEXTAPI -

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

CHANGING Parameters details for 1240_TRANSL_INT_EXT_LTXT

BAPI1240_LTXT -

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

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

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