SAP FMCC_CHECK_AVC_ACTIVATION Function Module for Cash Control: Check whether the cash AVC is active
FMCC_CHECK_AVC_ACTIVATION is a standard fmcc check avc activation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Cash Control: Check whether the cash AVC is active 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 fmcc check avc activation FM, simply by entering the name FMCC_CHECK_AVC_ACTIVATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCC_CR
Program Name: SAPLFMCC_CR
Main Program: SAPLFMCC_CR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCC_CHECK_AVC_ACTIVATION 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 'FMCC_CHECK_AVC_ACTIVATION'"Cash Control: Check whether the cash AVC is active.
EXPORTING
IV_BUKRS = "Company Code
IMPORTING
EV_CASH_AVC_ACTIVE = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for FMCC_CHECK_AVC_ACTIVATION
IV_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FMCC_CHECK_AVC_ACTIVATION
EV_CASH_AVC_ACTIVE - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCC_CHECK_AVC_ACTIVATION 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_bukrs | TYPE BUKRS, " | |||
| lv_ev_cash_avc_active | TYPE BOOLE_D. " |
|   CALL FUNCTION 'FMCC_CHECK_AVC_ACTIVATION' "Cash Control: Check whether the cash AVC is active |
| EXPORTING | ||
| IV_BUKRS | = lv_iv_bukrs | |
| IMPORTING | ||
| EV_CASH_AVC_ACTIVE | = lv_ev_cash_avc_active | |
| . " FMCC_CHECK_AVC_ACTIVATION | ||
ABAP code using 7.40 inline data declarations to call FM FMCC_CHECK_AVC_ACTIVATION
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