SAP ABAP Data Element DB2CCEXCL (Defined in exceptiontable: YES, NO, QUERY or NULL(no exctab))

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
     ⤷ STU2 (Package) CCMS for DB2 for OS/390

Basic Data

Data Element	DB2CCEXCL
Short Description	Defined in exceptiontable: YES, NO, QUERY or NULL(no exctab)

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	CHAR40
Data Type	CHAR	Character String
Length	40
Decimal Places	0
Output Length	40
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Exc. tab.
Medium	15	Exception table
Long	26	Defined in exception table
Heading	40	Defined in exception table

Documentation

Definition

You may use an exception table which is an optional, user-created DB2 table. You can use it to place information in this column of the recommendations result set. The most common use of this column is to filter the recommendations result set for tables you don't want to be subject to utility treatment. Each row in the exception table represents an object for which you want to provide information for the recommendations result set.

Now, the entry in this column contains one of the following values:

• YES, if you put a row in the exception table for the object that this result set row represents, but you specify NULL in the QUERYTYPE column. In that case, SAP ignores the recommendation for this object and neither raises an alert nor runs an utility on it.
• NO, if the exception table exists but does not have a row for the object that this result set row represents. That's the normal case, where SAP will raise an alert based on the recommendations and treat the object with the corresponding utilities when asked by you e.g. in Planning Calendar (Transaction DB13).
• NULL, if the exception table does not exist. SAP assumes in this case, that you don't have any tables that shouldn't be subject to utility treatment and treats this value in the same way as value NO.
• There's also a fourth option, returning a text that you specify in the QUERYTYPE column of the exception table. SAP doesn't make use of this option and treats this value in the same way as value YES. If you plan to implement your own filtering criteria, you will utilize this option.

History

Last changed by/on	SAP	20070813
SAP Release Created in	620