Customer Relationship Management Blogs by Members
Find insights on SAP CRM and other customer relationship management products and topics in blog posts from community members and share your own perspective.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

From CRM 5.0, we have both PPR and Listing functionality available in SAP CRM. So, its really confusing to decide which one among them can be used to
meet the business requirement, because same can be achieved by using PPR as well as Listings functionality. So which one among them is best suited for your business?

Before proceeding further, let us familiarize ourselves with their definitions first:

Partner/Product Ranges (PPR) is basically a combination of accounts and products that are valid for a specific time period.

 

Listings can be used to determine the products, which can be ordered by and offered to a customer for a particular time period via a certain sales channel.

 

Exclusion can be used to determine products, which cannot be sold to a customer for a particular time period.

During CRM 4.0, listing functionality was present only in R/3 but there was no integration of listing functionality with CRM. In CRM, same listing functionality was covered by Partner/Product Ranges (PPR). But flexibility of listing definition using PPR was not sufficient due to below reasons:

  • no customer specific key fields
  • no combination of account hierarchy with additional attributes

Motivation behind New Listing Functionality in CRM 5.0:

  • To leverage the advantages of R/3 Listings and PPRs
  • To provide seamless integration between R/3 and CRM Enterprise
  • Combine condition technique (listing header) and PPRs (listing items)

Below table clearly points out the difference betwen PPR and Listings functionality:

Key Features and DifferentiatorsPPRListings

Exchange listing information between

  • R/3 and CRM
X
  • CRM Enterprise and MSA
XX

Use product proposal in

  • Activity Journal
XX
  • Order (only MSA)
XX

Use listing check in

  • Order
XX
  • Marketing
XX
  • Account Planning
XX

Listing maintenance

  • Generic
XX
  • CP specific enhancements
X
Customizing
  • Process driven customizing for better fine tuning
X
Define listings for
  • Single account
XX
  • Account hierarchy node
XX
  • Target group
XX
  • Combination of account hierarchy node and additional attributes
X
  • Customer specific fields
X
  • Any customer attribute (e.g: region, customer group field)
X
Listing Items
  • Product, product category, product catalog
XX
  • Customer specific product fields (e.g: zz_prod_nr)
X
  • Any product attribute (e.g: brand)
X

Additional attributes for listing items as

  • Additional information (e.g: listing price)
XX
  • Key fields (e.g: zz_prod_nr, brand)
X

    

With this I would like to conclude that, Listings in CRM is preferred solution for new implementations and for customers who require R/3-CRM
integration. It also provides high flexibility for listing definition and determination and better performance.

4 Comments