SAP GRPCRTA_VIEW_CONVERSION_OUTPUT Function Module for Data conversion

Search SAP Function Modules

GRPCRTA_VIEW_CONVERSION_OUTPUT is a standard grpcrta view conversion 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 Data conversion 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 grpcrta view conversion output FM, simply by entering the name GRPCRTA_VIEW_CONVERSION_OUTPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function GRPCRTA_VIEW_CONVERSION_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 'GRPCRTA_VIEW_CONVERSION_OUTPUT'"Data conversion
  EXPORTING
   VALUE_INTERN =  "
*  INTLEN = 0 "Internal length in bytes
*  TABNAME = ' ' "Table name
*  FIELDNAME = ' ' "Field name
*  INTTYPE = ' ' "ABAP data type (C,D,N,...)
*  DATATYPE = ' ' "Data type in ABAP Dictionary
*  DECIMALS = 0 "Number of decimal places
*  CONVEXIT = ' ' "Conversion routine
*  SIGN = ' ' "Flag for sign in numerical fields
*  OUTPUTLEN = 0 "Output length

 IMPORTING
   VALUE_EXTERN =  "

EXCEPTIONS
   PARAMETER_ERROR = 1 

.

IMPORTING Parameters details for GRPCRTA_VIEW_CONVERSION_OUTPUT

VALUE_INTERN -

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

INTLEN - Internal length in bytes

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

TABNAME - Table name

Data type: TABNAME
Default: SPACE
Optional: Yes
Call by Reference: Yes

FIELDNAME - Field name

Data type: FIELDNAME
Default: SPACE
Optional: Yes
Call by Reference: Yes

INTTYPE - ABAP data type (C,D,N,...)

Data type: VIMNAMTAB-INTTYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATATYPE - Data type in ABAP Dictionary

Data type: VIMNAMTAB-DATATYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DECIMALS - Number of decimal places

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

CONVEXIT - Conversion routine

Data type: VIMNAMTAB-CONVEXIT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

SIGN - Flag for sign in numerical fields

Data type: VIMNAMTAB-SIGN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

OUTPUTLEN - Output length

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

EXPORTING Parameters details for GRPCRTA_VIEW_CONVERSION_OUTPUT

VALUE_EXTERN -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PARAMETER_ERROR - Wrong parameter

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

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