Functionality
This function module calls the Viewcluster maintenance.
The Viewcluster maintenance maintains data across several tables. Itcombines the maintenance of several tables or views (objects) into onemaintenance dialog. The objects are maintained by the extended tablemaintenance.
The Viewcluster definition must have been created and activated viaSE54.
Selection conditions for the data to be edited, and function codes ofthe not desired standard functions can be passed.
Exceptions are raised with MESSAGE...RAISING, so they need not behandled by the caller.

Notes
This function module is released.
The function module documentation is being edited to satisfy the formalrequirements for released function modules.
The function module can not be called in the function library testenvironment.

Description
Correction number for Change and Transport (parameterMAINTENANCE_ACTION).
If no correction number is passed, a correction number entry dialog boxappears when Transport is called or a first change is saved.

Description
Processing type. Possible actions are:

• S = Display


• U = Change


• T = Transport

Default
none

Description
When data in client-independent tables or views are to be maintained,there is usually a warning about the possible effects on other clients.
This flag suppresses this information.

Value range
SPACE - information displayed (default)
<> SPACE - information not displayed

Default
SPACE - information is displayed

Description
The parameter READ_KIND influences when the Viewcluster object data isread in.


• ' ' = complete

All Viewcluster object data is read in immediately at the start ofViewcluster maintenence.

• T = subtree

At first, only the data of objects which depend on the initial objectare read in. The data of other root objects (objects with nopredecessor) and their dependent objects are read in as required, bysubtree.
If a Viewcluster has several root objects, READ_KIND = 'T' improvesperformance at the start of Viewcluster maintenance.
For Viewclusters with only one root object this parameter makes nodifference.

Default
' ' = complete

Description
One object is flagged as the initial object in a Viewclusterdefinition. This initial object is presented to the user first when theViewcluster is called.
If you want to use another object as initial object, specify it in theSTART_OBJECT parameter.

Default
The initial object specified in the Viewcluster definition.

Description
Flag: Suppress "Specify Workarea" dialog box
Note: The flag is intended for calling from the IMG.
Some maintenance views contain key fields with the maintenanceattribute *Subset", which requires the user to specify a value for thefield at the start of the view maintenance dialog. If the field has aparameter ID which contains previous values or user parameters, aproposal is offered.
If the flag SUPPRESS_WA_POPUP is set, the input dialog box issuppressed if the field already has a parameter ID value. The user isthen not prompted to specify a value for the field more than once perR/3 logon.

Value range
'X': Suppress dialog box if all input fields already have values fromthe parameter ID.
SPACE: Always display input dialog box.

Default
SPACE

Description
The table DBA_SELLIST contains the selection conditions for theViewcluster initial object database access. They are passed on todependent objects according to the relationships specified in theViewcluster definition field dependencies.
Prerequisites:
The initial object must be a root object (object with no predecessors),and the DBA_SELLIST_CLUSTER parameter must not be specified. Theselection conditions are otherwise ignored.
Notes:


• The following fields must be filled in DBA_SELLIST:

Field name Contents
NEGATION NOT, if the condition is to be negated
SPACE otherwise
VIEWFIELD Name of the field to which the condition applies
OPERATOR logical operator of the condition (e.g. 'EQ', 'NE',...)
VALUE condition comparison value
AND_OR AND, if the next line of the condition is to be linked
to the current one by a logical AND
OR, if the next line of the condition is to be linked
to the current one by a logical OR
SPACE, if no line follows

• Valid operators are: (see also ABAP doc.)

EQ - equals
NE - not equal
GT - greater than
GE - greater than or equal to
LT - less than
LE - less than or equal to
CA - for strings only: contains at least one character of thecomparison string
CN - for strings only: negation of CA
CO - for strings only: contains only characters from the comparisonstring
NA - for strings only: negation of CO
CP - for strings only: contains the pattern in the comparison string
NP - for strings only: negation of CP
CS - for strings only: contains the string in the comparison string
NS - for strings only: negation of CS
LK - like the LIKE operator in a SELECT ... WHERE clause

• The function module does not check whether these selection conditions
are compatible with any conditions specified in the Data Dictionaryview definition. The caller must ensure that this is the case.

Description
The table DBA_SELLIST_CLUSTER contains database access selectionconditions for any Viewcluster objects. They are passed on to dependentobjects according to the relationships specified in the Viewclusterdefinition field dependencies.
Selection conditions for fields of a dependent object which are relatedto the higher-level object according to the Viewcluster definitionfield dependencies are ignored.
Notes:


• The table DBA_SELLIST_CLUSTER must be of type VCLTY_SELLIST_TABLE. The
table entries must be of type VCLTY_SELLIST_FOR_OBJECT and have thefollowing structure:
OBJECT Name of the Viewcluster object
SELLIST Selection conditions for the object OBJECT

• The SELLIST fields must be filled as described for the parameter
DBA_SELLIST.

• The function module does not check whether the selection conditions are
compatible with any conditions specified in the View definition of theobject in the Data Dictionary. The caller must ensure that this is thecase.

Description
The table DPL_SELLIST_FOR_START_OBJECT contains selection conditionsfor entries to be displayed for the initial view cluster object, if itis not a root object (object without predecessor).
Background:
If you go directly into a dependent object when you enter the viewcluster, the entries to be displayed in this object cannot be selectedvia the selected entries in the higher-level object, as in normalnavigation. The view cluster maintenance displays a popup by default toenter the missing conditions.
These conditions can be specified in the parameterDPL_SELLIST_FOR_START_OBJECT. The standard popup is then not called, ifa condition is specified for each field in the initial object whichdepends on a predecessor field.
Notes:


• If the initial object is a root object, the parameter
DPL_SELLIST_FOR_START_OBJECT is ignored.

• The following fields must be filled in DPL_SELLIST_FOR_START_OBJECT:

Field name Contents
NEGATION SPACE
VIEWFIELD Name of the field to which the condition applies
OPERATOR condition logical operator ('EQ')
VALUE condition comparison value

• Only the operator 'EQ' (equals) is allowed; entries with other
operators are ignored.

• The field NEGATION must be SPACE; entries with NEGATION <> SPACE are
ignored.

• The value 'AND' is always implicitly assumed ; das for the field
AND_OR.The field is not processed.

Default
No conditions specified.

Description
The table EXCL_CUA_FUNCT_ALL_OBJECTS must contain all the functionswhich should not be callable while processing Viewcluster objects.These functions are deactivated dynamically in the GUI interface ofeach Viewcluster object at runtime.
This is useful, e.g. for the following Viewcluster maintenancefunctions:
'ANZG' -> switch processing mode from 'change' to
'display' in a maintenance Viewcluster
'AEND' -> switch processing mode from 'display' to
'change' in a display Viewcluster
'xxxx' -> other functions.
The table must have the structure VIMEXCLFUN, as follows:
FUNCTION(4) TYPE C -> function code to be deactivated dynamically
MESSAGE(3) TYPE C -> online help auxiliary field (not yetsupported)
Notes


• This parameter is ignored if the parameter EXCL_CUA_FUNCT_CLUSTER is
specified.

• If the function module VIEWCLUSTER_SET_EXCL_CUA_FUNCT is called during
Viewcluster maintenance for a Viewcluster object, the functions to beexcluded specified for this object in the parameterEXCL_CUA_FUNCT_ALL_OBJECTS are overwritten.

Description
The table EXCL_CUA_FUNCT_CLUSTER contains all the functions for anyViewcluster objects which are not to be callable while processing thisobject. These functions are deactivated dynamically in the GUIinterface of this object at runtime.
Notes


• The table EXCL_CUA_FUNCT_CLUSTER must have the type
VCLTY_EXCLFUNCT_TABLE and the table entries the typeVCLTY_EXCLFUNCT_FOR_OBJECT and structure:
OBJECT Name of the Viewcluster object
EXCLFUNCT CUA functions to be excluded for the object OBJECT

• The table EXCLFUNCT must have the structure VIMEXCLFUN, as follows:

FUNCTION(4) TYPE C -> function code to be dynamically deactivated
MESSAGE(3) TYPE C -> online help auxiliary field (not yet
supported)

• If the function module VIEWCLUSTER_SET_EXCL_CUA_FUNCT is called during
Viewcluster maintenance for a Viewcluster object OBJECT for whichfunctions to be excluded are also specified in the parameterEXCL_CUA_FUNCT_CLUSTER, the functions specified with the call areoverwritten.