The following table represents BEX keyword equivalents to Java expressions:
BEX keywords |
|
---|---|
Java expression |
BEX equivalents |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Because of these keywords, name clashes with business vocabulary can occur. The easiest way to avoid clashes is to use upper case notation when referring to model attributes because BEX grammar is case sensitive and all keywords are in lower case.
For example, assume there is an attribute called isLessThanCoverageLimit
. If it is referred as 'is less than coverage limit', a name
clash with keywords 'is less than' occurs. The workaround is to
refer to the attribute as 'Is Less Than Coverage
Limit'.