For example, the following is a valid Businessobject clause:
The first value is an actual object type name: Customer. The second value uses wildcard characters, multiple values, and character strings. A user might search for a customer named Howard Trevor. But the user is unsure of the name spelling and does not know if the customer is stored as Howard or Trevor. By specifying the object name with this pattern, all object names that begin with the letters “Tre” or “How” are searched for. If any are found that are of type Customer, they are listed. The final asterisk indicates that all revisions are allowed. When listing multiple values as part of a pattern, you cannot have spaces within the pattern unless the spaces are enclosed within quotation marks. If you accidentally include spaces, the search could read the value as the next part of the object specification. For example, the following clause would produce false values:
When this clause is processed, Customer is again used for the object type. However, rather than searching for names that begin with “Tre” or “How,” The search is only for objects whose names begin with “Tre”. How* is interpreted as the revision pattern, not part of the name pattern. For a complete listing of all defined business objects regardless of their exact specification, you can simply insert an asterisk into each pattern of the Businessobject clauses:
Since this clause could produce a large number of objects, it is usually desirable to restrict the query searches in some way. Rather than use an asterisk for each pattern, you can use an asterisk in only one or two of the required patterns. The goal is to provide enough information to filter out unwanted objects. However, you do not want to make your search too narrow or you might miss an important object. | |||||||||||