SAP FMCA_CONVERT_ISR_DATA_INPUT Function Module for









FMCA_CONVERT_ISR_DATA_INPUT is a standard fmca convert isr data input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fmca convert isr data input FM, simply by entering the name FMCA_CONVERT_ISR_DATA_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_CONVERT_ISR_DATA_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 'FMCA_CONVERT_ISR_DATA_INPUT'"
EXPORTING
IV_SCENARIO = "Key for a Scenario
IV_VERSION = "Version of Scenario

CHANGING
* CT_SPECIAL_DATA = "Table type for form field data
* CT_SPECIAL_DATA_ORIG = "Internal Service Request: Values of the Special Fields
.



IMPORTING Parameters details for FMCA_CONVERT_ISR_DATA_INPUT

IV_SCENARIO - Key for a Scenario

Data type: QISRSCENARIO-SCENARIO
Optional: No
Call by Reference: Yes

IV_VERSION - Version of Scenario

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

CHANGING Parameters details for FMCA_CONVERT_ISR_DATA_INPUT

CT_SPECIAL_DATA - Table type for form field data

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

CT_SPECIAL_DATA_ORIG - Internal Service Request: Values of the Special Fields

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

Copy and paste ABAP code example for FMCA_CONVERT_ISR_DATA_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_iv_scenario  TYPE QISRSCENARIO-SCENARIO, "   
lv_ct_special_data  TYPE FMCA_FORM_FIELD_DATA_T, "   
lv_iv_version  TYPE QISRDVERSION, "   
lv_ct_special_data_orig  TYPE QISRTSPECIAL_PARAM. "   

  CALL FUNCTION 'FMCA_CONVERT_ISR_DATA_INPUT'  "
    EXPORTING
         IV_SCENARIO = lv_iv_scenario
         IV_VERSION = lv_iv_version
    CHANGING
         CT_SPECIAL_DATA = lv_ct_special_data
         CT_SPECIAL_DATA_ORIG = lv_ct_special_data_orig
. " FMCA_CONVERT_ISR_DATA_INPUT




ABAP code using 7.40 inline data declarations to call FM FMCA_CONVERT_ISR_DATA_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.

"SELECT single SCENARIO FROM QISRSCENARIO INTO @DATA(ld_iv_scenario).
 
 
 
 


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!