To identify the segment of your database that the strategy uses.
| Term | Definition |
|---|---|
| Key | Unique identifier in the database view that links the view to the collections object, such as transaction or customer. It is the data level at which you run strategies. |
| View Name | Name of the database view used to limit the scope of a strategy. |
Your database administrator creates and registers a database view to access a group of records. Views appear in the View Name drop down list on the Segments page when creating or updating strategies. The collections administrator adds a segment to a strategy in the Create Strategy flow.
Are there any restrictions for the database view?The segment name be in the format, IEX_F_[name]_V. The view must be created in the APPS schema (the Database owner of the object must be = 'APPS').
The view must contain an object ID column that is the same as the data level at which you run strategies. For example, if you run strategies at the customer level, PARTY_ID must be a column in the view.
Are there any seeded views for strategies?Yes, We can use scoring filter views IEX_F_PARTIES for Party Level, IEX_F_ACCOUNTS_V for Account Level, IEX_F_BILLTO_V for Bill-To level, and IEX_F_DELINQUENCIES_V or IEX_F_STRATEGY_V for Delinquency level.
Why do some segments have more than one key?A developer can designate multiple primary keys when creating a view. This occurs when the view is used for multiple purposes.