SAP ALV_AQ_XINT_CONVERSION Function Module for









ALV_AQ_XINT_CONVERSION is a standard alv aq xint conversion SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 alv aq xint conversion FM, simply by entering the name ALV_AQ_XINT_CONVERSION into the relevant SAP transaction such as SE37 or SE38.

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



Function ALV_AQ_XINT_CONVERSION 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 'ALV_AQ_XINT_CONVERSION'"
EXPORTING
* I_LISTFIELDS_ONLY = "Single-Character Flag
* I_TABNAME_MASTER = "
* I_TABNAME_SLAVE = "
IT_FIELDCAT = "
* IT_FILTER_INDEX = "ALV Control: Filter Index
* I_CURRENCY_SHIFT = ' ' "

IMPORTING
EP_NEW_TABLE = "

TABLES
CT_OUTTAB = "
ET_AQFIELDCAT = "SAP Query (L): Field Description for Lists
ET_AQFPAIRS = "SAP Query (L): Amount/Unit Pairs
ET_AQFIELDLIST = "SAP Query (L): Functional area field list
ET_AQRQLIST = "SAP Query (L): Field list of a query (technical)
ET_CONVEXITS = "Subset of DFIES (Conversion Exits)

EXCEPTIONS
CONVERSION_NOT_POSSIBLE = 1
.



IMPORTING Parameters details for ALV_AQ_XINT_CONVERSION

I_LISTFIELDS_ONLY - Single-Character Flag

Data type: CHAR1
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TABNAME_MASTER -

Data type: KKBLO_TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TABNAME_SLAVE -

Data type: KKBLO_TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_FIELDCAT -

Data type: KKBLO_T_FIELDCAT
Optional: No
Call by Reference: No ( called with pass by value option)

IT_FILTER_INDEX - ALV Control: Filter Index

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

I_CURRENCY_SHIFT -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ALV_AQ_XINT_CONVERSION

EP_NEW_TABLE -

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

TABLES Parameters details for ALV_AQ_XINT_CONVERSION

CT_OUTTAB -

Data type:
Optional: No
Call by Reference: Yes

ET_AQFIELDCAT - SAP Query (L): Field Description for Lists

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

ET_AQFPAIRS - SAP Query (L): Amount/Unit Pairs

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

ET_AQFIELDLIST - SAP Query (L): Functional area field list

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

ET_AQRQLIST - SAP Query (L): Field list of a query (technical)

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

ET_CONVEXITS - Subset of DFIES (Conversion Exits)

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

EXCEPTIONS details

CONVERSION_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ALV_AQ_XINT_CONVERSION 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:
lt_ct_outtab  TYPE STANDARD TABLE OF STRING, "   
lv_ep_new_table  TYPE DATA, "   
lv_i_listfields_only  TYPE CHAR1, "   
lv_conversion_not_possible  TYPE CHAR1, "   
lt_et_aqfieldcat  TYPE STANDARD TABLE OF RSAQLDESC, "   
lv_i_tabname_master  TYPE KKBLO_TABNAME, "   
lt_et_aqfpairs  TYPE STANDARD TABLE OF RSAQFPAIRS, "   
lv_i_tabname_slave  TYPE KKBLO_TABNAME, "   
lv_it_fieldcat  TYPE KKBLO_T_FIELDCAT, "   
lt_et_aqfieldlist  TYPE STANDARD TABLE OF RSAQRFLIST, "   
lt_et_aqrqlist  TYPE STANDARD TABLE OF RSAQRQLIST, "   
lv_it_filter_index  TYPE LVC_T_FIDX, "   
lt_et_convexits  TYPE STANDARD TABLE OF LVCDINCL, "   
lv_i_currency_shift  TYPE FLAG. "   SPACE

  CALL FUNCTION 'ALV_AQ_XINT_CONVERSION'  "
    EXPORTING
         I_LISTFIELDS_ONLY = lv_i_listfields_only
         I_TABNAME_MASTER = lv_i_tabname_master
         I_TABNAME_SLAVE = lv_i_tabname_slave
         IT_FIELDCAT = lv_it_fieldcat
         IT_FILTER_INDEX = lv_it_filter_index
         I_CURRENCY_SHIFT = lv_i_currency_shift
    IMPORTING
         EP_NEW_TABLE = lv_ep_new_table
    TABLES
         CT_OUTTAB = lt_ct_outtab
         ET_AQFIELDCAT = lt_et_aqfieldcat
         ET_AQFPAIRS = lt_et_aqfpairs
         ET_AQFIELDLIST = lt_et_aqfieldlist
         ET_AQRQLIST = lt_et_aqrqlist
         ET_CONVEXITS = lt_et_convexits
    EXCEPTIONS
        CONVERSION_NOT_POSSIBLE = 1
. " ALV_AQ_XINT_CONVERSION




ABAP code using 7.40 inline data declarations to call FM ALV_AQ_XINT_CONVERSION

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_currency_shift) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!