Contract classifications
Contract classifications are required when you add a contract. With contract classifications, you have a way of categorizing and organizing contracts.
Examples of contract classifications might include: Corporate, Company/Facility Specific, Local, Departmental, Maintenance or IT. When you add a classification, you make decisions that affect the contracts, addendums, change orders, and amendments that are assigned to that classification.
The two main primary purposes of the classification are security and the flow of the contract. Classification determine which process automation flow to use and the flow of the contract. Security is driven from classification to determine who can see which contracts. If a contract subclassification is attached to the classification, then the rules that are defined in the contract classification take precedence.
This explains the type of decisions you make:
- Decide whether a contract, addendum, or amendment requires approval before or after starting negotiations with your supplier, and whether to require negotiations with your supplier.
- Decide whether to receive notification when the text of a term and condition changes.
- Decide whether commodity code, manufacturer code and manufacturer number are required for service and non-service items, item master or special items, on a contract line. For information about manufacturing codes, see the Inventory Control User Guide .
- Decide on a default document template to use with contracts assigned to this classification.
- Decide whether contracts assigned to this classification are eligible to create events in Strategic Sourcing.
After setting up a classification, you can optionally assign a subclassification to it. You make the same decisions as for the classification. In cases where a contract has both a classification and a subclassification, the settings for the subclassification are used.
Important: Before you add a contract classification, a contract group must already exist in Contract Management.