SAP FMAVC_CONVERT_ACO_TO_MSGVX Function Module for Condense control object into message variable(s)

Search SAP Function Modules

FMAVC_CONVERT_ACO_TO_MSGVX is a standard fmavc convert aco to msgvx SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Condense control object into message variable(s) 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 fmavc convert aco to msgvx FM, simply by entering the name FMAVC_CONVERT_ACO_TO_MSGVX into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMAVC_CONTROL_OBJECT_TOOLS
Program Name: SAPLFMAVC_CONTROL_OBJECT_TOOLS
Main Program: SAPLFMAVC_CONTROL_OBJECT_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMAVC_CONVERT_ACO_TO_MSGVX 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 'FMAVC_CONVERT_ACO_TO_MSGVX'"Condense control object into message variable(s)
  EXPORTING
   I_FM_AREA =  "Financial Management Area
   I_ALDNR =  "Availability Control Ledger
   I_S_ACO_ADDRESS =  "AVC dimensions (FM)
*  I_FLG_ADD_ALDNR = ' ' "Flag: Include the AVC ledger number into the output
*  I_ADD_FISCAL_YEAR =  "Fiscal year to be added to the output
*  I_ADD_CEFF_YEAR =  "Year of cash effect. to be added to the output
*  I_FLG_ONLY_ONE_MSG_VAR = ' ' "Flag: Limit the output to only one message variable
*  I_FLG_ADD_FM_AREA = ' ' "Flag: Include the FM area into the output

 IMPORTING
   E_MSGV1 =  "Messages, message variables
   E_MSGV2 =  "Messages, message variables

.

IMPORTING Parameters details for FMAVC_CONVERT_ACO_TO_MSGVX

I_FM_AREA - Financial Management Area

Data type: FIKRS
Optional: No
Call by Reference: Yes

I_ALDNR - Availability Control Ledger

Data type: BUAVC_ALDNR
Optional: No
Call by Reference: Yes

I_S_ACO_ADDRESS - AVC dimensions (FM)

Data type: FMAVC_S_DIMENSIONS
Optional: No
Call by Reference: Yes

I_FLG_ADD_ALDNR - Flag: Include the AVC ledger number into the output

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: Yes

I_ADD_FISCAL_YEAR - Fiscal year to be added to the output

Data type: GJAHR
Optional: Yes
Call by Reference: Yes

I_ADD_CEFF_YEAR - Year of cash effect. to be added to the output

Data type: GNJHR
Optional: Yes
Call by Reference: Yes

I_FLG_ONLY_ONE_MSG_VAR - Flag: Limit the output to only one message variable

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: Yes

I_FLG_ADD_FM_AREA - Flag: Include the FM area into the output

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMAVC_CONVERT_ACO_TO_MSGVX

E_MSGV1 - Messages, message variables

Data type: SYST-MSGV1
Optional: No
Call by Reference: Yes

E_MSGV2 - Messages, message variables

Data type: SYST-MSGV1
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMAVC_CONVERT_ACO_TO_MSGVX 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.

ABAP code using 7.40 inline data declarations to call FM FMAVC_CONVERT_ACO_TO_MSGVX

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