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

Function FMCA_INCORR_UPDATE_BETRAG 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_UPDATE_BETRAG'"Update Betrag.
CHANGING
C_FKKCOHI_EXT = "Erweiterte Struktur Korrespondenzhistorie
EXCEPTIONS
E_NOT_AUTHORIZED = 1 E_NOT_EXISTING = 2 E_ERROR = 3
CHANGING Parameters details for FMCA_INCORR_UPDATE_BETRAG
C_FKKCOHI_EXT - Erweiterte Struktur Korrespondenzhistorie
Data type: FKKCOHI_EXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
E_NOT_AUTHORIZED - Nicht autorisiert zur Änderung
Data type:Optional: No
Call by Reference: Yes
E_NOT_EXISTING - Es existiert keine Anforderung
Data type:Optional: No
Call by Reference: Yes
E_ERROR - General Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_INCORR_UPDATE_BETRAG 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_fkkcohi_ext | TYPE FKKCOHI_EXT, " | |||
| lv_e_not_authorized | TYPE FKKCOHI_EXT, " | |||
| lv_e_not_existing | TYPE FKKCOHI_EXT, " | |||
| lv_e_error | TYPE FKKCOHI_EXT. " |
|   CALL FUNCTION 'FMCA_INCORR_UPDATE_BETRAG' "Update Betrag |
| CHANGING | ||
| C_FKKCOHI_EXT | = lv_c_fkkcohi_ext | |
| EXCEPTIONS | ||
| E_NOT_AUTHORIZED = 1 | ||
| E_NOT_EXISTING = 2 | ||
| E_ERROR = 3 | ||
| . " FMCA_INCORR_UPDATE_BETRAG | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_INCORR_UPDATE_BETRAG
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