SAP CONVERSION_EXIT_OBART_OUTPUT Function Module for Conversion of object type from internal to language-specific value

Search SAP Function Modules

CONVERSION_EXIT_OBART_OUTPUT is a standard conversion exit obart output SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion of object type from internal to language-specific value processing and below is the pattern details for this FM, 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 conversion exit obart output FM, simply by entering the name CONVERSION_EXIT_OBART_OUTPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function CONVERSION_EXIT_OBART_OUTPUT 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 'CONVERSION_EXIT_OBART_OUTPUT'"Conversion of object type from internal to language-specific value
  EXPORTING
   INPUT =  "Internal value for object type
*  I_LANGU = SY-LANGU "Language

 IMPORTING
   OUTPUT =  "Language-specific value for object type
   TXT10 =  "
   TXT15 =  "
   TXT20 =  "
   TXT60 =  "

.

IMPORTING Parameters details for CONVERSION_EXIT_OBART_OUTPUT

INPUT - Internal value for object type

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

I_LANGU - Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CONVERSION_EXIT_OBART_OUTPUT

OUTPUT - Language-specific value for object type

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

TXT10 -

Data type: TBO01-TXT10
Optional: No
Call by Reference: No ( called with pass by value option)

TXT15 -

Data type: TBO01-TXT15
Optional: No
Call by Reference: No ( called with pass by value option)

TXT20 -

Data type: TBO01-TXT20
Optional: No
Call by Reference: No ( called with pass by value option)

TXT60 -

Data type: TBO01-TXT60
Optional: No
Call by Reference: No ( called with pass by value option)

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

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