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 Differentiators PPR Listings

Exchange listing information between

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

Use product proposal in

  • Activity Journal
X X
  • Order (only MSA)
X X

Use listing check in

  • Order
X X
  • Marketing
X X
  • Account Planning
X X

Listing maintenance

  • Generic
X X
  • CP specific enhancements
X
Customizing
  • Process driven customizing for better fine tuning
X
Define listings for
  • Single account
X X
  • Account hierarchy node
X X
  • Target group
X X
  • 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
X X
  • 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)
X X
  • 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.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. prasadh thunga

    Hi Shanthala,

    Can you please share the process of listings replication from CRM 7 to ECC.

    We have scenario where in R/3 material listings is mandatory per config. In CRM7 we have maintained listings but not flowing to ECC..could you please explain the config that is to be setup and replication process..thanks a lot.

    Regards

    Prasad

    (0) 
    1. Shanthala Kudva

      Hello Prasad,

      As far I know, it is not possible to replicate listings maintained in CRM to ECC.

      Generally, listings will be maintained in ECC and then replicated to CRM via MW and then maintenance shift will be done to CRM.

      But again there is no auto upload from CRM to ECC.

      You can refer  SAP Note: 1591754 – Listings download from ECC to CRM here.

      Hope this helps.

      Best Regards,

      Shanthala.

      (0) 

Leave a Reply