SAP G_CONVERT_OUTPUT Function Module for Conversion of output values

Search SAP Function Modules

G_CONVERT_OUTPUT is a standard g convert 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 output values 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 g convert output FM, simply by entering the name G_CONVERT_OUTPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function G_CONVERT_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 'G_CONVERT_OUTPUT'"Conversion of output values
  EXPORTING
*  CONVEXIT = ' ' "Conversion exit
*  DATATYPE = 'CHAR' "Data base field type (for example
*  LENGTH = 0 "Field length in characters
*  LENGTH_TO_CONVERT = 0 "Length of the value to be converted (in characters)
*  OUTPUT_LENGTH = 0 "Field length after the conversion (screen field)
   VALUE_TO_CONVERT =  "Value to be converted (internal di

 IMPORTING
   OUTPUT_VALUE =  "Value after conversion (for screen

EXCEPTIONS
   ILLEGAL_LENGTH = 1 

.

IMPORTING Parameters details for G_CONVERT_OUTPUT

CONVEXIT - Conversion exit

Data type: DFIES-CONVEXIT
Default: SPACE
Optional: Yes
Call by Reference: Yes

DATATYPE - Data base field type (for example

Data type: DFIES-DATATYPE
Default: 'CHAR'
Optional: Yes
Call by Reference: Yes

LENGTH - Field length in characters

Data type: ANY
Optional: Yes
Call by Reference: Yes

LENGTH_TO_CONVERT - Length of the value to be converted (in characters)

Data type: ANY
Optional: Yes
Call by Reference: Yes

OUTPUT_LENGTH - Field length after the conversion (screen field)

Data type: ANY
Optional: Yes
Call by Reference: Yes

VALUE_TO_CONVERT - Value to be converted (internal di

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

EXPORTING Parameters details for G_CONVERT_OUTPUT

OUTPUT_VALUE - Value after conversion (for screen

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

EXCEPTIONS details

ILLEGAL_LENGTH - Inadmissible field length specific

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

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