Officers
Officers Property Class is used to specify the primary internal officer responsible for an arrangement. Additionally other officers or departments can also be specified who have responsibility for the product in general or a specific arrangement. It is used by all products where there is a need to assign product or arrangement specific officers (that is, different from the customer’s default officers). Each Temenos Transact product defined and processed in AA can have a single OFFICERS Property defined.
Officers and Account Property Class
When the product has both the ACCOUNT and OFFICERS properties while creating the product, the fields enabled in the Account condition are disabled and the Officer condition must be used in the arrangement.
If the product has only the Account product condition, the officer related fields in the Account condition can be used in the arrangement.
Product Lines
The following Product Lines use the Officers Property Class:
- Accounts
- Agent
- Asset Finance
- Deposits
- Facility
- Lending
- Rewards
- Safe Deposit Box
Property Class type
The Officers Property Class (optional) uses the following Property Class Types:
- Dated
- Enable External
- Enable External Financial
- Enabled For Memo
- Tracking
- Variation Supported
Property Type
There is no associated Property Type with this Property Class.
Balance Prefix and Suffix
Officers Property Class does not hold any balances as it is not financial in nature and therefore there is no associated balance prefix.
Attributes
The following section describes the related attributes:
Primary Officer
The Primary Officer (Primary field) responsible for the product or arrangement can be specified. All officers must exist in the DEPT.ACCT.OFFICER file. The primary officer is used as the ACCOUNT.OFFICER in the created ACCOUNT record.
Other Officer
Additional officers (Other field) who can assist with a product or arrangement can be specified. All officers must exist in the DEPT.ACCT.OFFICER table. This field is part of a multi-value set of fields with associated Role and Notes.
Officer Role
Each additional officer must have a specified role. The roles are user defined and specified in EB.LOOKUP. This field is part of a multi value set of Other and Notes fields.
Notes
The user can enter any notes relating to the other officer. This field is part of a multi-value set of fields with Other.1 and Role fields.
Periodic Attribute Classes
There are no periodic Attribute Classes associated with Officers Property Class.
Actions
The Officers Property Class supports the following actions:
| Action Name | Description |
|---|---|
| DATA.CAPTURE | This action is used in capturing the information on Officers when records are migrated from Legacy to AA. |
| UPDATE | The update action is initiated manually and allows the User to change any of the OFFICERS attributes. This action can be initiated as part of the NEW-ARRANGEMENT and UPDATE- OFFICERS Activities. |
Accounting Events
Officers Property Class does not perform actions that generate Accounting events.
Limits Interaction
Actions associated with the Officers Property Class does not have an impact on the Limits.
In this topic