Hierarchy
⤷ BC-TWB-TST-ECA (Application Component) eCATT Extended Computer Aided Test Tool
⤷ SECATT_DDIC (Package) eCATT ABAP Dictionary Objects
Basic Data
Data Element | ETVO_NAME |
Short Description | Validation Object |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ETOBJ_NAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | Validation |
Medium | 17 | Validation Object |
Long | 20 | Validation Object |
Heading | 30 | Validation Object |
Documentation
Definition
Documentation comes here!
Business Message Reference
Validation is generally performed to verify the Business/Technical functionality of any application under test.
In order to match the technical results to a business sense, these translatable messages could be used.
A Validation Object execution can result in 'Success', 'Failure' or 'Technical Error'.
These technical states can be mapped to appropriate business sense with this Business Message Grid.
The eCATT execution log will contain the appropriate business message depending upon the status of the execution.
Types of Messages that can be used:
T100 and OTR Messages
How to specify Messages?
1. T100 Message:
A T100 Message can be uniquely identified by specifying the Message Class & the corresponding Message Number. A message class is basically used for classifying a group of messages and Message ID uniquely identifies a message under a message class.
Both of these values should be specified under the message key column with 'Message Class followed by Message ID with colon (':') as a delimiter.
For ex: Assume a message class MSGCLS has a message under message ID 001, it should be represented as 'MSGCLS:001'. Please node ':' is used as a delimiter between the message class and the message number.
Creation and navigation of messages are supported from the Validation Object UI with a double click from the Message Key cell.
2. OTR Messages (Partial Support):
You can specify an existing OTR message, by providing the ID of the message in the message key Column. Navigation is possible to view the text message from the message key column.
Creation of OTR messages are not supported from the Validation Object UI
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |