Line 5: | Line 5: | ||
| | ||
+ | |||
== Contract Type == | == Contract Type == | ||
− | + | The structure of an Agreement in ICM is based on the concept of Contract Types. These are user-defined workflows (as opposed to rule-based) and are of following types: | |
+ | |||
+ | *Contract Request: defines the request form to assemble all the inputs and data required to create an Agreement or Contract. It is based on attributes and rules. | ||
+ | *Agreement: defines the structure of an agreement or contract that is to be executed and is based on Attributes, Templates, Clauses and Rules. | ||
+ | *Associated Document: defines the nature and format of the supporting documents that will be required to execute the agreement or contract in its entirety. It is based on Attributes, Templates and Rules. | ||
+ | *Masterdata: defines the structure to store the less frequently changing data and business information, such as vendor and company details, business number and address, and so on. It is based on Attributes and Rules. | ||
== Attribute == | == Attribute == |
Revision as of 09:11, 10 May 2019
Configuration
The Configuration tile is used by an Administrator to setup various entities of ICM.
Contract Type
The structure of an Agreement in ICM is based on the concept of Contract Types. These are user-defined workflows (as opposed to rule-based) and are of following types:
- Contract Request: defines the request form to assemble all the inputs and data required to create an Agreement or Contract. It is based on attributes and rules.
- Agreement: defines the structure of an agreement or contract that is to be executed and is based on Attributes, Templates, Clauses and Rules.
- Associated Document: defines the nature and format of the supporting documents that will be required to execute the agreement or contract in its entirety. It is based on Attributes, Templates and Rules.
- Masterdata: defines the structure to store the less frequently changing data and business information, such as vendor and company details, business number and address, and so on. It is based on Attributes and Rules.
Attribute
Attributes contain certain variable information that can be same or different across Agreements. For example, Expiry date of an Agreement. Attributes are stored in a global repository and created as part of ICM configuration.
Rule
Masterdata
Alias Master
Related Topics: Contract Type | Attribute | Rule | Masterdata | Alias_Master