SAP FMCA_SAMPLE_P239 Function Module for EVENT for TaxSubmissionERPCreateRequestConfirmation_In(Outbound)
FMCA_SAMPLE_P239 is a standard fmca sample p239 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EVENT for TaxSubmissionERPCreateRequestConfirmation_In(Outbound) 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 p239 FM, simply by entering the name FMCA_SAMPLE_P239 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_P239 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_P239'"EVENT for TaxSubmissionERPCreateRequestConfirmation_In(Outbound).
EXPORTING
IV_RETURN_ID = "Technical Key of Carrying Object
IV_KSV_ID = "GUID in 'CHAR' format with upper-/lowercase (!)
IV_FBNUM = "Number of a Form Bundle
IT_DOC = "DMS: Documents
IT_DOC_CON = "FKKDMS: Link Table
IT_TAXSUBMSNFORM = "Table Type for Uploading Tax Forms
IT_TAXSUBMSN = "Table Type for Uploading Tax Returns
CHANGING
E_OUTPUT = "Confirmation for TaxSubmissionERPCreateConfirmation_Sync
CT_ELMTVALUE = "Table type for form field data
IMPORTING Parameters details for FMCA_SAMPLE_P239
IV_RETURN_ID - Technical Key of Carrying Object
Data type: FMCA_RETURN_GUIDOptional: No
Call by Reference: Yes
IV_KSV_ID - GUID in 'CHAR' format with upper-/lowercase (!)
Data type: GUID_22Optional: No
Call by Reference: Yes
IV_FBNUM - Number of a Form Bundle
Data type: FBNUM_PSOptional: No
Call by Reference: Yes
IT_DOC - DMS: Documents
Data type: FKKDOC_TABOptional: No
Call by Reference: Yes
IT_DOC_CON - FKKDMS: Link Table
Data type: FKKDOC_CON_TABOptional: No
Call by Reference: Yes
IT_TAXSUBMSNFORM - Table Type for Uploading Tax Forms
Data type: FMCA_FORMS_TOptional: No
Call by Reference: Yes
IT_TAXSUBMSN - Table Type for Uploading Tax Returns
Data type: FMCA_RETURN_TOptional: No
Call by Reference: Yes
CHANGING Parameters details for FMCA_SAMPLE_P239
E_OUTPUT - Confirmation for TaxSubmissionERPCreateConfirmation_Sync
Data type: FMCA_TAX_SUBMISSION_ERPCREATE1Optional: No
Call by Reference: Yes
CT_ELMTVALUE - Table type for form field data
Data type: FMCA_FORM_FIELD_DATA_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_SAMPLE_P239 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_e_output | TYPE FMCA_TAX_SUBMISSION_ERPCREATE1, " | |||
| lv_iv_return_id | TYPE FMCA_RETURN_GUID, " | |||
| lv_iv_ksv_id | TYPE GUID_22, " | |||
| lv_ct_elmtvalue | TYPE FMCA_FORM_FIELD_DATA_T, " | |||
| lv_iv_fbnum | TYPE FBNUM_PS, " | |||
| lv_it_doc | TYPE FKKDOC_TAB, " | |||
| lv_it_doc_con | TYPE FKKDOC_CON_TAB, " | |||
| lv_it_taxsubmsnform | TYPE FMCA_FORMS_T, " | |||
| lv_it_taxsubmsn | TYPE FMCA_RETURN_T. " |
|   CALL FUNCTION 'FMCA_SAMPLE_P239' "EVENT for TaxSubmissionERPCreateRequestConfirmation_In(Outbound) |
| EXPORTING | ||
| IV_RETURN_ID | = lv_iv_return_id | |
| IV_KSV_ID | = lv_iv_ksv_id | |
| IV_FBNUM | = lv_iv_fbnum | |
| IT_DOC | = lv_it_doc | |
| IT_DOC_CON | = lv_it_doc_con | |
| IT_TAXSUBMSNFORM | = lv_it_taxsubmsnform | |
| IT_TAXSUBMSN | = lv_it_taxsubmsn | |
| CHANGING | ||
| E_OUTPUT | = lv_e_output | |
| CT_ELMTVALUE | = lv_ct_elmtvalue | |
| . " FMCA_SAMPLE_P239 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_SAMPLE_P239
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