SAP FMCA_GET_ARC_FORM_BUNDLE Function Module for Read single form bundle from archive
FMCA_GET_ARC_FORM_BUNDLE is a standard fmca get arc form bundle SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read single form bundle from archive 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 get arc form bundle FM, simply by entering the name FMCA_GET_ARC_FORM_BUNDLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_ARCHIVE_FB
Program Name: SAPLFMCA_ARCHIVE_FB
Main Program: SAPLFMCA_ARCHIVE_FB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_GET_ARC_FORM_BUNDLE 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_GET_ARC_FORM_BUNDLE'"Read single form bundle from archive.
EXPORTING
* IV_CASE_GUID = "Technical Key of Carrying Object
* IV_JOINT_REG_ID = "Joint Reference Specifications from Contract
* IV_JOINT_REG_TYPE = "Joint Subapplication in Contract Accounts Receivable and Payable
* IV_JOINT_ID_TYPE = "Joint Identification Type
* IV_JOINT_FILER_ID = "Joint Identification Number
* IV_REVENUE_TYPE = "Revenue Type
* IV_FBTYP = "Form Bundle Type
* IV_FBNUM = "Number of a Form Bundle
* IV_PERIOD_KEY = "Key for Period Assignment
* I_MAXREC = 0 "Maximum Number of Entries
* IV_TAXPAYER = "Business Partner Number
* IV_ACCOUNT = "Contract Account Number
* IV_REG_ID = "Reference Specifications from Contract
* IV_REG_TYPE = "Subapplication in Contract Accounts Receivable and Payable
* IV_BU_ID_TYPE = "Identification Type
* IV_TAXPAYER_ID = "Identification Number
* IV_JOINT_FILER = "Joint Business Partner Number
* IV_JOINT_ACCOUNT = "Joint Contract Account Number
CHANGING
* T_DFMCA_NOTE_ATT = "Table Type for Data Table DFMCA_NOTE_ATT
TABLES
* T_DFMCA_RETURN = "Data Table for Tax Returns
* T_DFMCA_TRACE_0100 = "TRM BRF+: Indx-typed table for Lean Trace
* T_DFMCA_FORMS = "Data Table for Tax Forms
* T_DFMCA_FORM_VERS = "Versions of Form Data
* T_DFMCA_BRF_MSG = "Tax Calculation and Validation: Error Messages
* T_DFMCA_FPF_HIS = "FPF: Form Processing History
* T_DFMCA_OP_REFDOC = "##Items in contract account document of a Form Bundle
* T_DFMCA_WIHEAD = "Additional Data for Workflow Item
* T_DFMCA_WIHEADH = "Additional Data for Workflow Item (History)
* T_DFKKDOC_CON = "FKKDMS: Links Between Application Objects and Documents
EXCEPTIONS
NO_ENTRY_FOUND = 1 NO_INFOSTRUCTURE_FOUND = 2 NO_SELECTION_CRITERIA = 3 FIELD_MISSING_IN_FIELDCAT = 4 AS_ERROR = 5 WRONG_SELECTION_CRITERIA = 6 E_TOO_MANY_SELTYPES = 7
IMPORTING Parameters details for FMCA_GET_ARC_FORM_BUNDLE
IV_CASE_GUID - Technical Key of Carrying Object
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_REG_ID - Joint Reference Specifications from Contract
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_REG_TYPE - Joint Subapplication in Contract Accounts Receivable and Payable
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_ID_TYPE - Joint Identification Type
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_FILER_ID - Joint Identification Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_REVENUE_TYPE - Revenue Type
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_FBTYP - Form Bundle Type
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_FBNUM - Number of a Form Bundle
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_PERIOD_KEY - Key for Period Assignment
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
I_MAXREC - Maximum Number of Entries
Data type: IOptional: Yes
Call by Reference: Yes
IV_TAXPAYER - Business Partner Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_ACCOUNT - Contract Account Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_REG_ID - Reference Specifications from Contract
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_REG_TYPE - Subapplication in Contract Accounts Receivable and Payable
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_BU_ID_TYPE - Identification Type
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_TAXPAYER_ID - Identification Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_FILER - Joint Business Partner Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
IV_JOINT_ACCOUNT - Joint Contract Account Number
Data type: RSELOPTIONOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for FMCA_GET_ARC_FORM_BUNDLE
T_DFMCA_NOTE_ATT - Table Type for Data Table DFMCA_NOTE_ATT
Data type: FMCA_T_DFMCA_NOTE_ATTOptional: Yes
Call by Reference: Yes
TABLES Parameters details for FMCA_GET_ARC_FORM_BUNDLE
T_DFMCA_RETURN - Data Table for Tax Returns
Data type: DFMCA_RETURNOptional: Yes
Call by Reference: Yes
T_DFMCA_TRACE_0100 - TRM BRF+: Indx-typed table for Lean Trace
Data type: DFMCA_TRACE_0100Optional: Yes
Call by Reference: Yes
T_DFMCA_FORMS - Data Table for Tax Forms
Data type: DFMCA_FORMSOptional: Yes
Call by Reference: Yes
T_DFMCA_FORM_VERS - Versions of Form Data
Data type: DFMCA_FORM_VERSOptional: Yes
Call by Reference: Yes
T_DFMCA_BRF_MSG - Tax Calculation and Validation: Error Messages
Data type: DFMCA_BRF_MSGOptional: Yes
Call by Reference: Yes
T_DFMCA_FPF_HIS - FPF: Form Processing History
Data type: DFMCA_FPF_HISOptional: Yes
Call by Reference: Yes
T_DFMCA_OP_REFDOC - ##Items in contract account document of a Form Bundle
Data type: DFMCA_OP_REFDOCOptional: Yes
Call by Reference: Yes
T_DFMCA_WIHEAD - Additional Data for Workflow Item
Data type: DFMCA_WIHEADOptional: Yes
Call by Reference: Yes
T_DFMCA_WIHEADH - Additional Data for Workflow Item (History)
Data type: DFMCA_WIHEADHOptional: Yes
Call by Reference: Yes
T_DFKKDOC_CON - FKKDMS: Links Between Application Objects and Documents
Data type: DFKKDOC_CONOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND - Keinen Eintrag gefunden
Data type:Optional: No
Call by Reference: Yes
NO_INFOSTRUCTURE_FOUND - Keine Infostruktur gefunden
Data type:Optional: No
Call by Reference: Yes
NO_SELECTION_CRITERIA - Keine Selektionen eingegeben
Data type:Optional: No
Call by Reference: Yes
FIELD_MISSING_IN_FIELDCAT - Ein Feld der Selektionkriterien fehlt im Feldkatalog
Data type:Optional: No
Call by Reference: Yes
AS_ERROR - AS Fehler
Data type:Optional: No
Call by Reference: Yes
WRONG_SELECTION_CRITERIA - Selektionskriterien falsch definiert
Data type:Optional: No
Call by Reference: Yes
E_TOO_MANY_SELTYPES - Es wurde sowohl ein Bereich als auch ein Einzelwert als Selektion angegeben
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_GET_ARC_FORM_BUNDLE 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_case_guid | TYPE RSELOPTION, " | |||
| lv_no_entry_found | TYPE RSELOPTION, " | |||
| lt_t_dfmca_return | TYPE STANDARD TABLE OF DFMCA_RETURN, " | |||
| lv_t_dfmca_note_att | TYPE FMCA_T_DFMCA_NOTE_ATT, " | |||
| lv_iv_joint_reg_id | TYPE RSELOPTION, " | |||
| lt_t_dfmca_trace_0100 | TYPE STANDARD TABLE OF DFMCA_TRACE_0100, " | |||
| lv_iv_joint_reg_type | TYPE RSELOPTION, " | |||
| lv_iv_joint_id_type | TYPE RSELOPTION, " | |||
| lv_iv_joint_filer_id | TYPE RSELOPTION, " | |||
| lv_iv_revenue_type | TYPE RSELOPTION, " | |||
| lv_iv_fbtyp | TYPE RSELOPTION, " | |||
| lv_iv_fbnum | TYPE RSELOPTION, " | |||
| lv_iv_period_key | TYPE RSELOPTION, " | |||
| lv_i_maxrec | TYPE I, " 0 | |||
| lv_iv_taxpayer | TYPE RSELOPTION, " | |||
| lt_t_dfmca_forms | TYPE STANDARD TABLE OF DFMCA_FORMS, " | |||
| lv_no_infostructure_found | TYPE DFMCA_FORMS, " | |||
| lv_iv_account | TYPE RSELOPTION, " | |||
| lt_t_dfmca_form_vers | TYPE STANDARD TABLE OF DFMCA_FORM_VERS, " | |||
| lv_no_selection_criteria | TYPE DFMCA_FORM_VERS, " | |||
| lv_iv_reg_id | TYPE RSELOPTION, " | |||
| lt_t_dfmca_brf_msg | TYPE STANDARD TABLE OF DFMCA_BRF_MSG, " | |||
| lv_field_missing_in_fieldcat | TYPE DFMCA_BRF_MSG, " | |||
| lv_as_error | TYPE DFMCA_BRF_MSG, " | |||
| lv_iv_reg_type | TYPE RSELOPTION, " | |||
| lt_t_dfmca_fpf_his | TYPE STANDARD TABLE OF DFMCA_FPF_HIS, " | |||
| lv_iv_bu_id_type | TYPE RSELOPTION, " | |||
| lt_t_dfmca_op_refdoc | TYPE STANDARD TABLE OF DFMCA_OP_REFDOC, " | |||
| lv_wrong_selection_criteria | TYPE DFMCA_OP_REFDOC, " | |||
| lv_iv_taxpayer_id | TYPE RSELOPTION, " | |||
| lt_t_dfmca_wihead | TYPE STANDARD TABLE OF DFMCA_WIHEAD, " | |||
| lv_e_too_many_seltypes | TYPE DFMCA_WIHEAD, " | |||
| lv_iv_joint_filer | TYPE RSELOPTION, " | |||
| lt_t_dfmca_wiheadh | TYPE STANDARD TABLE OF DFMCA_WIHEADH, " | |||
| lt_t_dfkkdoc_con | TYPE STANDARD TABLE OF DFKKDOC_CON, " | |||
| lv_iv_joint_account | TYPE RSELOPTION. " |
|   CALL FUNCTION 'FMCA_GET_ARC_FORM_BUNDLE' "Read single form bundle from archive |
| EXPORTING | ||
| IV_CASE_GUID | = lv_iv_case_guid | |
| IV_JOINT_REG_ID | = lv_iv_joint_reg_id | |
| IV_JOINT_REG_TYPE | = lv_iv_joint_reg_type | |
| IV_JOINT_ID_TYPE | = lv_iv_joint_id_type | |
| IV_JOINT_FILER_ID | = lv_iv_joint_filer_id | |
| IV_REVENUE_TYPE | = lv_iv_revenue_type | |
| IV_FBTYP | = lv_iv_fbtyp | |
| IV_FBNUM | = lv_iv_fbnum | |
| IV_PERIOD_KEY | = lv_iv_period_key | |
| I_MAXREC | = lv_i_maxrec | |
| IV_TAXPAYER | = lv_iv_taxpayer | |
| IV_ACCOUNT | = lv_iv_account | |
| IV_REG_ID | = lv_iv_reg_id | |
| IV_REG_TYPE | = lv_iv_reg_type | |
| IV_BU_ID_TYPE | = lv_iv_bu_id_type | |
| IV_TAXPAYER_ID | = lv_iv_taxpayer_id | |
| IV_JOINT_FILER | = lv_iv_joint_filer | |
| IV_JOINT_ACCOUNT | = lv_iv_joint_account | |
| CHANGING | ||
| T_DFMCA_NOTE_ATT | = lv_t_dfmca_note_att | |
| TABLES | ||
| T_DFMCA_RETURN | = lt_t_dfmca_return | |
| T_DFMCA_TRACE_0100 | = lt_t_dfmca_trace_0100 | |
| T_DFMCA_FORMS | = lt_t_dfmca_forms | |
| T_DFMCA_FORM_VERS | = lt_t_dfmca_form_vers | |
| T_DFMCA_BRF_MSG | = lt_t_dfmca_brf_msg | |
| T_DFMCA_FPF_HIS | = lt_t_dfmca_fpf_his | |
| T_DFMCA_OP_REFDOC | = lt_t_dfmca_op_refdoc | |
| T_DFMCA_WIHEAD | = lt_t_dfmca_wihead | |
| T_DFMCA_WIHEADH | = lt_t_dfmca_wiheadh | |
| T_DFKKDOC_CON | = lt_t_dfkkdoc_con | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND = 1 | ||
| NO_INFOSTRUCTURE_FOUND = 2 | ||
| NO_SELECTION_CRITERIA = 3 | ||
| FIELD_MISSING_IN_FIELDCAT = 4 | ||
| AS_ERROR = 5 | ||
| WRONG_SELECTION_CRITERIA = 6 | ||
| E_TOO_MANY_SELTYPES = 7 | ||
| . " FMCA_GET_ARC_FORM_BUNDLE | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_GET_ARC_FORM_BUNDLE
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