Show TOC

Background documentationControlling Partner/Product Ranges

 

The partner/product range type (PPR type) controls the characteristics and attributes for a partner/product range at header and item level.

This includes, for example:

  • The application (sales contract, marketing project, and so on) in which it is valid

  • For which organizational data (transaction type, partner function, sales organization, service organization, and so on) it can be valid

  • Which references to products, accounts, and so on, are possible

    Note Note

    You make the settings for the partner/product range type in the Implementation Guide (IMG) in the Customizing for Partner/Product Ranges under Start of the navigation path Basic Settings Next navigation step Define Partner/Product Range Types End of the navigation path.

    End of the note.
Process Flow: Control at Header Level

PPR type

When creating a partner/product range you choose a PPR type. The available PPR types are defined in Customizing.

Item type

When you create a new partner/product range type or a new item, you choose a new item type. This can either be a reference to other PPRs or a reference to a combination of accounts, products, and validity periods.

You define the possible item types for a PPR type in Customizing for Partner/Product Ranges under Start of the navigation path Basic Settings Next navigation step Define Partner/Product Range Types End of the navigation path.

Organizational data

In Customizing for the Partner/Product Range Type, you define for which organizational data a partner/product range can be valid. The following are available for selection:

  • Transaction type

  • Partner function

  • Sales organization

  • Service organization

    The PPR check is used for each of these objects:

    • If entries are maintained, the system checks whether they match the values entered in the business transaction. If they match, the system continues to consider the products contained in the PPR. Otherwise, the products are not considered.

    • If no entries are maintained, the corresponding PPR is used for all possible instances of each organizational data object. If, for example, no data is maintained for the sales organization, the relevant PPR is valid for all sales organizations.

Process Flow: Control at Item Level

You define the possible reference types for accounts, products, and validity periods in Customizing for the Partner/Product Range Type.