SAP Function Modules

CONVERSION_EXIT_FMCIS_INPUT SAP Function module








CONVERSION_EXIT_FMCIS_INPUTis a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name CONVERSION_EXIT_FMCIS_INPUT into the relevant SAP transaction such as SE37 or SE80.

Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CONVERSION_EXIT_FMCIS_INPUT or its description.


Pattern for FM CONVERSION_EXIT_FMCIS_INPUT - CONVERSION EXIT FMCIS INPUT
Associated Function Group: FMCONVCI
Released Date: Not Released
CALL FUNCTION 'CONVERSION_EXIT_FMCIS_INPUT' "
  EXPORTING
    input =                     "
  IMPORTING
    output =                    "
    .  "  CONVERSION_EXIT_FMCIS_INPUT

ABAP code example for CONVERSION_EXIT_FMCIS_INPUT Function Module

The ABAP code below is a full code listing to execute function module CONVERSION_EXIT_FMCIS_INPUT including all data declarations. The code uses the latest IN-LINE DATA DECLARATION SYNTAX but I have included an ABAP code snipet at the end to show how declarations would look using the original method of declaring data variables up front. 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).
DATA:
ld_output TYPE STRING.

DATA(ld_input) = 'some text here'.. CALL FUNCTION 'CONVERSION_EXIT_FMCIS_INPUT' EXPORTING input = ld_input IMPORTING output = ld_output . " CONVERSION_EXIT_FMCIS_INPUT
IF SY-SUBRC EQ 0. "All OK ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
ld_output TYPE STRING ,
ld_input TYPE STRING .

ld_input = 'some text here'..