Specify the contract's attributes

Go to the contract's content area > Overview.

Define the contract's basic data.

• Name: (Mandatory) Enter a meaningful name for the contract that is known by the users in your enterprise.
• Contract Number: The contract number provided for the legal contract.
• Authorized User: The user who creates the contract is the authorized user per default. This can be changed.

  authorized user

  An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for.

• Authorized User Groups: Select one or more authorized user groups that shall have write permissions to the contract. All users in the authorized user group can edit the contract.

  authorized user group

  An authorized user group is a set of users that have been granted write permissions to an object. More than one authorized user group may be specified for an object.

Define the organizations and vendors.

• Buyer: Each contract requires a buyer. This is the organization buying the contract deliverable that are addressed by the contract.

  contract deliverable

  A contract deliverable is the obligated deliverable that must be provided to fulfill the terms of a contract or contract item. A contract deliverable has a delivery date and a quantity that must be delivered as well as the application, component, physical server, or virtual server that is targeted by the deliverable.

• Vendor/Provider Organization: Each contract requires a vendor or organization that providing the contract deliverable addressed by the contract.

Define the lifecycle attributes. Go to the LIfecycle Data attribute box and define the following:

• Start Date and End Date: The start and end date captures the contract's period of validity. Click the calendar icon to select the date or enter the date in the date format Month/Day/Year. For example: 4/30/2026
• Review Date: The point in time when the contract should be reviewed to prevent it from unknowingly becoming obsolete.
• Predecessor: The contract that came before this contract.
• Release Status: Describes the governance status of the contract over its lifecycle and thus indicates how well users can trust the information. The release status determines whether a contract can or cannot be deleted. Possible values are:
  • Draft: The status of the contract when initiated.
  • In Negotiation: The contract is currently being negotiated between both parties. A contract with this release status cannot be deleted.
  • Signed: A final agreement between both contract parties has been reached. A contract with this release status cannot be deleted.
  • Retired: The contract is no longer relevant for operational purposes.