SAP FMCA_INCORR_REVERSE Function Module for Reset des Eingangsdatums und Folgeoperationen
FMCA_INCORR_REVERSE is a standard fmca incorr reverse SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reset des Eingangsdatums und Folgeoperationen 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 incorr reverse FM, simply by entering the name FMCA_INCORR_REVERSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_INCORR
Program Name: SAPLFMCA_INCORR
Main Program: SAPLFMCA_INCORR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_INCORR_REVERSE 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_INCORR_REVERSE'"Reset des Eingangsdatums und Folgeoperationen.
EXPORTING
I_INCOTYP = "Eingangskorrespondenztyp
I_GPART = "Geschäftspartnernummer
I_VKONT = "Vertragskontonummer
I_VTREF = "Referenzangaben aus dem Vertrag
I_SUBAP = "Subapplikation im Vertragskontokorrent
I_PERSL = "Schlüssel für Periodenzuordnung
I_ABRZU = "Untergrenze des Abrechnungszeitraums
* I_XSIMU = ' ' "Simulationsmodus
IMPORTING
E_INCORR = "Eingangskorresponenzanforderung (typisiert)
EXCEPTIONS
E_NOT_EXISTING = 1 E_NOT_RECEIVED = 2 E_NOT_AUTHORIZED = 3 E_SEVERAL_PERIODS = 4 E_CONSOLIDATED = 5 E_LOCKED = 6
IMPORTING Parameters details for FMCA_INCORR_REVERSE
I_INCOTYP - Eingangskorrespondenztyp
Data type: INCO_TYP_PSOptional: No
Call by Reference: Yes
I_GPART - Geschäftspartnernummer
Data type: GPART_KKOptional: No
Call by Reference: Yes
I_VKONT - Vertragskontonummer
Data type: VKONT_KKOptional: No
Call by Reference: Yes
I_VTREF - Referenzangaben aus dem Vertrag
Data type: VTREF_KKOptional: No
Call by Reference: Yes
I_SUBAP - Subapplikation im Vertragskontokorrent
Data type: SUBAP_KKOptional: No
Call by Reference: Yes
I_PERSL - Schlüssel für Periodenzuordnung
Data type: PERSL_KKOptional: No
Call by Reference: Yes
I_ABRZU - Untergrenze des Abrechnungszeitraums
Data type: ABRZU_KKOptional: No
Call by Reference: Yes
I_XSIMU - Simulationsmodus
Data type: BOOLEANDefault: ' '
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for FMCA_INCORR_REVERSE
E_INCORR - Eingangskorresponenzanforderung (typisiert)
Data type: FMCA_INCORROptional: No
Call by Reference: Yes
EXCEPTIONS details
E_NOT_EXISTING - Anforderung existiert nicht
Data type:Optional: No
Call by Reference: Yes
E_NOT_RECEIVED - Anforderung wurde noch nicht empfangen
Data type:Optional: No
Call by Reference: Yes
E_NOT_AUTHORIZED - Keine Berechtigung
Data type:Optional: No
Call by Reference: Yes
E_SEVERAL_PERIODS - Es existieren mehrere Teilperioden
Data type:Optional: No
Call by Reference: Yes
E_CONSOLIDATED - Anforderung ist konsolidiert
Data type:Optional: No
Call by Reference: Yes
E_LOCKED - gesperrt
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_INCORR_REVERSE 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_incorr | TYPE FMCA_INCORR, " | |||
| lv_i_incotyp | TYPE INCO_TYP_PS, " | |||
| lv_e_not_existing | TYPE INCO_TYP_PS, " | |||
| lv_i_gpart | TYPE GPART_KK, " | |||
| lv_e_not_received | TYPE GPART_KK, " | |||
| lv_i_vkont | TYPE VKONT_KK, " | |||
| lv_e_not_authorized | TYPE VKONT_KK, " | |||
| lv_i_vtref | TYPE VTREF_KK, " | |||
| lv_e_several_periods | TYPE VTREF_KK, " | |||
| lv_i_subap | TYPE SUBAP_KK, " | |||
| lv_e_consolidated | TYPE SUBAP_KK, " | |||
| lv_i_persl | TYPE PERSL_KK, " | |||
| lv_e_locked | TYPE PERSL_KK, " | |||
| lv_i_abrzu | TYPE ABRZU_KK, " | |||
| lv_i_xsimu | TYPE BOOLEAN. " ' ' |
|   CALL FUNCTION 'FMCA_INCORR_REVERSE' "Reset des Eingangsdatums und Folgeoperationen |
| EXPORTING | ||
| I_INCOTYP | = lv_i_incotyp | |
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_VTREF | = lv_i_vtref | |
| I_SUBAP | = lv_i_subap | |
| I_PERSL | = lv_i_persl | |
| I_ABRZU | = lv_i_abrzu | |
| I_XSIMU | = lv_i_xsimu | |
| IMPORTING | ||
| E_INCORR | = lv_e_incorr | |
| EXCEPTIONS | ||
| E_NOT_EXISTING = 1 | ||
| E_NOT_RECEIVED = 2 | ||
| E_NOT_AUTHORIZED = 3 | ||
| E_SEVERAL_PERIODS = 4 | ||
| E_CONSOLIDATED = 5 | ||
| E_LOCKED = 6 | ||
| . " FMCA_INCORR_REVERSE | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_INCORR_REVERSE
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.| DATA(ld_i_xsimu) | = ' '. | |||
Search for further information about these or an SAP related objects