Show TOC

Object documentationContract User Interface Scenario

 

Customizing object in which you define the attributes that control how a contract displays and the combination of objects allowed.

 

You associate a contract user interface scenario with a transaction type. If necessary, you can assign a scenario to more than one transaction type.

When you create a new contract, the system asks you to select the transaction type you want to use. The scenario assigned to the transaction type then determines which information you are able to enter, and certain default settings.

Structure

A user interface scenario consists of the following:

  • Description of the scenario

  • Control attributes, which can include:

    • Default distribution attributes

    • Tree profile that determines the relationships between the objects in the tree hierarchy

      Note Note

      You can create your own tree profile in Customizing for Customer Relationship Management under Start of the navigation path Industry-Specific Solutions Next navigation step Media Next navigation step Intellectual Property Management Next navigation step Master Data Next navigation step Define Object Hierarchy and Object Attributes End of the navigation path.

      End of the note.

  • Item group details, which can include:

    • Default item category usage

    • Allowed item categories for the related item group type

    • Default scale retroactivity type for variable royalties and variable rights and royalties

    • Final invoice item category usage for advances

Integration

You can define user interface scenarios for license acquisition and license sales contracts. To do so, make the settings in Customizing for Customer Relationship Management under Start of the navigation path Industry-Specific Solutions Next navigation step Media Next navigation step Intellectual Property Management Next navigation step Transactions Next navigation step Settings for IPM Transactions Next navigation step Define User Interface Scenarios End of the navigation path.

Example

You want to create a scenario for publishing acquisition contracts that displays only the distribution attributes and item groups you need to create this type of contract.

You specify the following default distribution attributes in Customizing:

  • IP

  • Market

  • Territory

  • Language

You specify the following item groups to be displayed:

  • Advance

  • Rights and Royalties — Variable

You specify the default scale retroactivity type for your Rights and Royalties — Variable item group.

In the scenario outlined, the unnecessary elements, such as pure rights or pure royalties scopes, do not display. The user sees only the elements required for publishing contracts.