SAP FMCA_SAMPLE_P217 Function Module for Outbound event for TaxReturnERPValidateRequestConfirmation
FMCA_SAMPLE_P217 is a standard fmca sample p217 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Outbound event for TaxReturnERPValidateRequestConfirmation 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 fmca sample p217 FM, simply by entering the name FMCA_SAMPLE_P217 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_TRM_ESOA_EVENTS
Program Name: SAPLFMCA_TRM_ESOA_EVENTS
Main Program: SAPLFMCA_TRM_ESOA_EVENTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_SAMPLE_P217 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_SAMPLE_P217'"Outbound event for TaxReturnERPValidateRequestConfirmation.
EXPORTING
IS_INPUT = "Tax Return ERP Validate Request Message_Sync
IT_RETURN = "Table Type for Uploading Tax Returns
IT_FORMS = "Table Type for Uploading Tax Forms
IT_FORMDATA = "Table type for form field data
IT_INVBILL_I = "Standard Table for Structure FKKINVBILL_I
CHANGING
C_OUTPUT = "Tax Return ERP Validate Confirmation Message_Sync
IMPORTING Parameters details for FMCA_SAMPLE_P217
IS_INPUT - Tax Return ERP Validate Request Message_Sync
Data type: FMCA_TAX_RETURN_ERPVALIDATE_R1Optional: No
Call by Reference: Yes
IT_RETURN - Table Type for Uploading Tax Returns
Data type: FMCA_RETURN_TOptional: No
Call by Reference: Yes
IT_FORMS - Table Type for Uploading Tax Forms
Data type: FMCA_FORMS_TOptional: No
Call by Reference: Yes
IT_FORMDATA - Table type for form field data
Data type: FMCA_FORM_FIELD_DATA_TOptional: No
Call by Reference: Yes
IT_INVBILL_I - Standard Table for Structure FKKINVBILL_I
Data type: FKKINVBILL_I_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for FMCA_SAMPLE_P217
C_OUTPUT - Tax Return ERP Validate Confirmation Message_Sync
Data type: FMCA_TAX_RETURN_ERPVALIDATE_COOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_SAMPLE_P217 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_c_output | TYPE FMCA_TAX_RETURN_ERPVALIDATE_CO, " | |||
| lv_is_input | TYPE FMCA_TAX_RETURN_ERPVALIDATE_R1, " | |||
| lv_it_return | TYPE FMCA_RETURN_T, " | |||
| lv_it_forms | TYPE FMCA_FORMS_T, " | |||
| lv_it_formdata | TYPE FMCA_FORM_FIELD_DATA_T, " | |||
| lv_it_invbill_i | TYPE FKKINVBILL_I_TAB. " |
|   CALL FUNCTION 'FMCA_SAMPLE_P217' "Outbound event for TaxReturnERPValidateRequestConfirmation |
| EXPORTING | ||
| IS_INPUT | = lv_is_input | |
| IT_RETURN | = lv_it_return | |
| IT_FORMS | = lv_it_forms | |
| IT_FORMDATA | = lv_it_formdata | |
| IT_INVBILL_I | = lv_it_invbill_i | |
| CHANGING | ||
| C_OUTPUT | = lv_c_output | |
| . " FMCA_SAMPLE_P217 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_SAMPLE_P217
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