SD partner functions design in BW

[Former Member]

Hi

have you already worked with partner functions in customer master data in SD ? how did you manage to design it in BW ?

here is the situation, currently in SAP ECC each customer have multiples sales representatives, and every sales representative visits the customer only for a specific product category, so for a specific product category and a specific client there is only one sales  representative.

Sales representative is designed as “partner function” in the customer master data (table KNVP)

The relation between a sales representative and product categories is 1:N and  evolves frequently

In the sales document, we have the customer and product, the product category  is a navigational attribute of product

the requirement is to display at SD billing document level, the sales representative linked currently to  the customer (not the one who was linked at billing time)

what's the best approach to design this scenario ?  a  hierarchy on 0cust_sales can solve the problem?

Thanks

[FCI]

No need for a hierarchy. Create a new characteristic Customer compounded with the  product category with the sales rep. as an attribute.

You will have to add this characteristic to your InfoProvider and the attribute (current sales rep for the customer and product category) will be available for reporting.

Regards,

Frederic

[Former Member]

Hi Frédéric,

Currently we the product category needed is a navigational attribute of product, how to instruct the system to use it in the compounding ?

Thanks

[FCI]

You can use any infoObject as a compound characteristic. Did you encounter a problem ?

Where can you find the sales representative in your data model ?

Regards,

Frederic

[Former Member]

Hi Frédéric,

Did you already worked with such scenario ?

if i create a simple compounded infoobject with product category C, at infocube loading time the system will generate the data with wrong SID of C.

in the infocube we have :

material, customer, C,  amount

product category is a navigantional attribute of material

sales representative is a navigantional attribute of C (C is not mapped for the infocube and is loaded as master data)

business rules:

product category of a material can change

sales representative for a (product category,client) can change

Thanks

[former_member199573]

Hi,

Can you check if Transitive attribute will meet your requirement?

http://help.sap.com/saphelp_nw73/helpdata/en/4a/420ee4402c0451e10000000a421937/content.htm

If a characteristic was included in an InfoCube as a navigation attribute, it can be used for navigating in queries. This characteristic can itself have further navigation attributes, called transitive attributes. These attributes are not automatically available for navigation in the query. However, this procedure describes how you can display the transitive attributes in the query via modeling.

...............

Regards,

Raja.