SAP CACS_VIEW_OO_WRAPPER Function Module for .









CACS_VIEW_OO_WRAPPER is a standard cacs view oo wrapper SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for . 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 cacs view oo wrapper FM, simply by entering the name CACS_VIEW_OO_WRAPPER into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS_VIEW_OO_WRAPPER 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 'CACS_VIEW_OO_WRAPPER'".
  EXPORTING
   I_TABNAM =  "Table Name
*  I_X_HEADER_FLG =  "
*  I_VIEW_NAME =  "Name of SAP table view
   IS_DATA =  "

CHANGING
   MAXLINES =  "
*  KEY =  "
*  EXIND =  "
   TABLE1 =  "
   ZEILE =  "
*  ACTION =  "
*  XACT =  "
*  STATUS_VIEW_DELETE =  "
*  VIM_TOTAL_KEY =  "
*  STATUS_VIEW_UPD_FLG =  "
*  STATUS_VIEW_UPD_CHK =  "

TABLES
   T_TABLE =  "
   EXTRACT =  "
   TOTAL =  "
*  T_TABLE1 =  "
*  TABELLE =  "

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for CACS_VIEW_OO_WRAPPER

I_TABNAM - Table Name

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

I_X_HEADER_FLG -

Data type:
Optional: Yes
Call by Reference: Yes

I_VIEW_NAME - Name of SAP table view

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

IS_DATA -

Data type:
Optional: No
Call by Reference: Yes

CHANGING Parameters details for CACS_VIEW_OO_WRAPPER

MAXLINES -

Data type:
Optional: No
Call by Reference: Yes

KEY -

Data type:
Optional: Yes
Call by Reference: Yes

EXIND -

Data type:
Optional: Yes
Call by Reference: Yes

TABLE1 -

Data type:
Optional: No
Call by Reference: Yes

ZEILE -

Data type:
Optional: No
Call by Reference: Yes

ACTION -

Data type:
Optional: Yes
Call by Reference: Yes

XACT -

Data type:
Optional: Yes
Call by Reference: Yes

STATUS_VIEW_DELETE -

Data type:
Optional: Yes
Call by Reference: Yes

VIM_TOTAL_KEY -

Data type:
Optional: Yes
Call by Reference: Yes

STATUS_VIEW_UPD_FLG -

Data type:
Optional: Yes
Call by Reference: Yes

STATUS_VIEW_UPD_CHK -

Data type:
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for CACS_VIEW_OO_WRAPPER

T_TABLE -

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

EXTRACT -

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

TOTAL -

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

T_TABLE1 -

Data type:
Optional: Yes
Call by Reference: Yes

TABELLE -

Data type:
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR -

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

Copy and paste ABAP code example for CACS_VIEW_OO_WRAPPER 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_error  TYPE STRING, "   
lt_t_table  TYPE STANDARD TABLE OF STRING, "   
lv_i_tabnam  TYPE TABNAME, "   
lv_maxlines  TYPE TABNAME, "   
lv_key  TYPE TABNAME, "   
lv_exind  TYPE TABNAME, "   
lv_table1  TYPE TABNAME, "   
lt_extract  TYPE STANDARD TABLE OF TABNAME, "   
lv_i_x_header_flg  TYPE TABNAME, "   
lt_total  TYPE STANDARD TABLE OF TABNAME, "   
lv_zeile  TYPE TABNAME, "   
lv_i_view_name  TYPE VIEWNAME, "   
lv_action  TYPE VIEWNAME, "   
lv_is_data  TYPE VIEWNAME, "   
lt_t_table1  TYPE STANDARD TABLE OF VIEWNAME, "   
lv_xact  TYPE VIEWNAME, "   
lt_tabelle  TYPE STANDARD TABLE OF VIEWNAME, "   
lv_status_view_delete  TYPE VIEWNAME, "   
lv_vim_total_key  TYPE VIEWNAME, "   
lv_status_view_upd_flg  TYPE VIEWNAME, "   
lv_status_view_upd_chk  TYPE VIEWNAME. "   

  CALL FUNCTION 'CACS_VIEW_OO_WRAPPER'  ".
    EXPORTING
         I_TABNAM = lv_i_tabnam
         I_X_HEADER_FLG = lv_i_x_header_flg
         I_VIEW_NAME = lv_i_view_name
         IS_DATA = lv_is_data
    CHANGING
         MAXLINES = lv_maxlines
         KEY = lv_key
         EXIND = lv_exind
         TABLE1 = lv_table1
         ZEILE = lv_zeile
         ACTION = lv_action
         XACT = lv_xact
         STATUS_VIEW_DELETE = lv_status_view_delete
         VIM_TOTAL_KEY = lv_vim_total_key
         STATUS_VIEW_UPD_FLG = lv_status_view_upd_flg
         STATUS_VIEW_UPD_CHK = lv_status_view_upd_chk
    TABLES
         T_TABLE = lt_t_table
         EXTRACT = lt_extract
         TOTAL = lt_total
         T_TABLE1 = lt_t_table1
         TABELLE = lt_tabelle
    EXCEPTIONS
        ERROR = 1
. " CACS_VIEW_OO_WRAPPER




ABAP code using 7.40 inline data declarations to call FM CACS_VIEW_OO_WRAPPER

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



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!