About Naming Scenario Components

Use the following guidelines when naming bound variables, thresholds, table attributes, and external bindings:

• Write table attribute names in UPPER_CASE. For example: ACCT.ACCT_INTRL_ID.
• Write bound variables that other Oracle Financial Services modules (external bindings such as variables that represent focal entities) require and define in the UPPER_CASE. For example: ACCOUNT, SECURITY, ASSOC_SECURITY.
• Write bound variables that the scenario defines in Title_Case and use the $ prefix. For example: $Min_Trans_Am.
• Write thresholds that the scenario defines in Title_Case and use the @ prefix. For example: @Max_Trans_Am

In general, use the upper case when referring to components defined outside of the scenario, and the title case when referring to bound variables or thresholds that the scenario defines.