SAP CONVERSION_EXIT_ISEID_INPUT Function Module for Conversion exit input









CONVERSION_EXIT_ISEID_INPUT is a standard conversion exit iseid input 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 exit input 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 iseid input FM, simply by entering the name CONVERSION_EXIT_ISEID_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function CONVERSION_EXIT_ISEID_INPUT 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_ISEID_INPUT'"Conversion exit input
EXPORTING
INPUT = "

IMPORTING
OUTPUT = "
.



IMPORTING Parameters details for CONVERSION_EXIT_ISEID_INPUT

INPUT -

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CONVERSION_EXIT_ISEID_INPUT

OUTPUT -

Data type:
Optional: No
Call by Reference: Yes

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

DATA:
lv_input  TYPE STRING, "   
lv_output  TYPE STRING. "   

  CALL FUNCTION 'CONVERSION_EXIT_ISEID_INPUT'  "Conversion exit input
    EXPORTING
         INPUT = lv_input
    IMPORTING
         OUTPUT = lv_output
. " CONVERSION_EXIT_ISEID_INPUT




ABAP code using 7.40 inline data declarations to call FM CONVERSION_EXIT_ISEID_INPUT

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!