Product Hierarchy discount

Hi,
We have come acorss for a typical discount condition type required.
Discount is required for product hierarchy. say for ex: there are 3 material X, Y and Z are having same product hierarchy key.
Now the requirement is for
Customer buys 15 packs of material X, therefore he should get a 15% discount.
Customer buys 10 packs of material X and 5 packs of material Y, therefore he should get a 15% discount too.
That means, mixing of materials within one product hierarchy should be possible.
How can achieve this?? will header condition work for this? Pls let me know your suggestions ASAP.
Regards,
Srikky

Thank you Navneetha...
really its a problem solving solution..
At last i wiould like to know where we can create this routine? i guess in VOFM - Formulas - Structure og Grp Key, pls correct if i am wrong. what should be logic to write code for this Product Hierarchy routine?
If i am already having a discount condition type and if i activate the 'Group condition', will this going to effect on anything? otherwise the functionality will remain same except Group Cond functionality? Can i use the same condition type for PH discount also?
Pls help me..
Thanks & Regards,
Srikky
Edited by: Srikky on Sep 7, 2010 11:12 AM
Edited by: Srikky on Sep 7, 2010 11:16 AM

Similar Messages

  • Customer Hierarchy and product Hierarchy

    Hi friends what is customer Hierarchy and what is product hierarchy?
    please explain step by step with examples.
    mail id: [email protected]
    Thanx.

    Hi Sirivas,
    CUSTOMER HIERARCHY:
    Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
     A customer hierarchy consists of nodes.
     To create a customer hierarchy:
    1. Create master records for each node.
    2. Assign the nodes to each other.
    3. Assign the customer master records to the relevant nodes.
     Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
    With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customer’s at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
    'How to check'
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
    1) Define hierarchy type: just put and ID and a name to the new hierarchy.
    2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
    3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
    4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
    5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
    It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
    Customer hierarchy setup, firstly decide the hierarchy type to be used.
    The standard is type A.
    You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
    Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
    You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
    You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
    All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
    You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
    Product Hierarchy:
    The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
    Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
    Requirement type determination is based on the "Origin of requirement type in requirement type determination"
    In this field you can select an alternative search strategy (source):
    Source 0 = Material master strategy, then item category and MRP type
    Source 1 = Item type and MRP type strategy
    Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
    e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
    Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
    For make to order std strategy group 20 is used to which req type KE is assigned.
    Check
    Check in Tcode OVZH, what requirement class is assigned to your requirement type
    Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
    The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
    Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
    One can maintain the product hierarchy via transaction "OVSV" and "V/76.
    Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
    The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
    The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
    The transaction which will be useful to change product hierarchies for material master will be V/76.
    Yes, You can print the levels of the product hierarchy through a report.
    Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
    Field Name is PRODH
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Addign product hierarchy to purchasing conditon

    Hi,
    I have a problem,
    I'm trying to create a vendor discount condition based on the material's product hierarchy.
    I added field PRODH to the field catalog and then created a new table, then I added the new table to the access sequence.
    I created a condition record to for a product hierarchy.
    BUT in the purchase order the condition is not recognized.
    In the analysis there is a message for the access seq :" Access not made (initialized field) "
    Can you please help me solve this issue.
    Thanks,
    Dave

    Hi ,
    i think something wrong with VARKEY itself , anyhow y dont you process BDC session with "Display Error Screen" then u wil come to know hot its passing the values to PRODH.....
    regards
    Prabhu

  • CUSTOMER & PRODUCT HIERARCHY

    Dear SAP Gurus,
         Can any one provide me step by step of Customer and Product Hierarchies?
    my mail id is [email protected]
    Highly rewarded.
    Regards.

    hi
    Customer Hierarchy
    All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy 
    1) Define hierarchy type: just put and ID and a name to the new hierarchy. 
    2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function. 
    3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy. 
    4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas). 
    5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination.
    It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount. 
    Customer hierarchy setup, firstly decide the hierarchy type to be used. 
    The standard is type A. 
    You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
    Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy. 
    You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level. 
    You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area. 
    All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy 
    You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers.   If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
    Can also refer to http://help.sap.com/bestpractices/BBLibrary/documentation/J04_BB_ConfigGuide_EN_UK.doc
    Product Hierarchy Configuration:
    http://help.sap.com/bestpractices/BBLibrary/documentation/Q10_BB_ConfigGuide_EN_US.doc
    Reward if USeful
    Thanx & regards..
    Naren..

  • Mass Update of Product hierarchy in all CRM Open Sales Orders

    Hi Folks,
    I have a requirement in my project wherein I have to update product hierarchy details with new values in all Items of CRM Open sales orders.
    If suppose I have a text file which has the details of Open Orders & new product hierarchy which i have to update, then would it be recommended if I use BDC for this task. Can I Call Transaction CRMD_ORDER?
    If someone has already gone through such requirement, Can you please suggest me how to proceed with this requirement. Using BDC or any other way which I can proceed with?
    Thanks in advance !!!
    Regards,
    Nitish.

    You are correct in indicating that Exchange rate type field  is not seen in Header data of sales order. I checked screen layouts for various screens for sales order data and this field is not suppressed. The only reason could be that this field is not used in sales order screens
    If you are interested, you could also check in the following way
    1.  Go to SE11, enter database table as VBAK
    2. Once inside data dictionary table, click where used list button, select programs and screens and execute
    3. click continue (don't select background)
    4. now you would have list of programs and screens, this table is used
    5.  now start another session and go to transaction SE51
    6. indicate program name as SAPMV45A and screen numbers as listed in step 4. you can check all screen numbers to see whether Exchange rate type field is listed in sales order layout.
    7. Of particular interest would be screen number 4311 as this contains  Financial accounting data & 4303 Billing data
    8. you can check screen layout for screen 4311 & 4303. you would see Exchange rate type field is not indicated.
    9. in case you could find this field in any screen, you could ask your ABAP consultant to add this field in the layout screen.
    Hope this answers your question

  • Pricing issue with Product hierarchy - Urgent

    Hello,
    I have an issue on pricing determination with product hierarchy.
    I created product hierarchy as following,
    level1 - A0001
    level2 - A0001B0001
    level3 - A0001B0001C0001
    Then, assigned A0001B0001C0001 to material D in material master.
    I created condition record with A0001B0001C0001(level 3),  the system found the condition sucessfully when I created a sales order with material D.
    However, I created condition record with A0001(level1) but the system didn't get the price when I created the sales order with material D.  Since A0001B0001C0001 belongs to A0001, the system is supposed to get the price from the condition record with A0001... 
    Could you please let me know how to fix it?

    Hi,
    Thanks a lot for your kind explanation.
    Here is the access sequence I defined.  I wonder if there is anyway I can define PRODH1, PRODH2, PRODH3 in access sequnce the same way with customer hierarchy so that the system can check higher level data.  If it's not allowed, I think I should define routine in requirement as you advised.  Thanks!
    *Accesses
    AcNo       Description
      1           Customer Hierarchy/Product Hiearchy
      2           Customer Hierarchy/Product Hiearchy
      3           Customer Hierarchy/Product Hiearchy
      4           Customer Hierarchy/Product Hiearchy
    Fields
      AcNo   Condition    Doc. field      field lable
         1      HIENR      HIEBO01     CustomerHierarchy 01
                 PRODH     PRODH       Product hierarchy
         2.     HIENR      HIEBO02     CustomerHierarchy 02
                 PRODH     PRODH       Product hierarchy
         3      HIENR      HIEBO03     CustomerHierarchy 03
                 PRODH     PRODH       Product hierarchy
         4       HIENR      HIEBO04     CustomerHierarchy 04
                 PRODH     PRODH       Product hierarchy
    I wonder if I can assign product hierachy fields, PRODH1, PRODH2, PRODH3 to access sequence like customer hierarchy so that the system can check higher level data to get the price...

  • Different product hierarchy in sales order and in service order

    Dear experts,
    In VA03, I notice that
    - under Line Item > Sales B, there is a field Product Hierarchy
    - under Line Item > Account assignment, there is a field Order. From here, it links to a service order. In the service order, I can see a field Product Hierarchy too.
    I would like to know if there is an implication when the field Product Hierarchy in sales order and in service order are different. Is it possible that this will cause an inconsistency?
    Usually these two fields have the same value, since the value in sales order is copied from service order. However, in my case, the product hierarchy is changed/updated in service order, but not in sales order.

    Hi,
    We have document pricing procedure maintained at two levels for Sales order or Billing type.
    The pricing procedure is determined based on SAles Area Customer pricing procedureDocument Pricing procedure+pricing procedure.
    Example :For Sales Document type the document pricing rpocedure will be A and for billing type 'B"
    Sales Area1A+Pricing procedure A
    Sales Area1B+Pricing procedure B
    Now A will be maintained in VOV8 and B will be maintained in VOFA.So two pricing procedures.
    Regards,

  • SQVI Report for SAP CRM Product Hierarchy and its Product

    Hi
    How to create a SQVI report for generating a list for SAP CRM Product Hierarchy which should show the outputs->Level 1, level 2, level 3 and level 4 categories and its products?
    I tried COMM_Hierarchy table and Comm_product but not able to achieve this requirement.
    or Is there any chance of getting related tables so that I could try more for this requirement.
    In which table both product id and its category Id can be found?
    Pravin

    Thanks DJ
    Is there any possibility to get a report for product hierarchy in SQVI ?
    say in SAP CRM system, the product category is maintained in COMM_HIERARCHY as
    Parent category Id->
                                    Level2 Category Id->
                                                                     Level 3 Category Id->                                                                               
    Level 4 category Id ->                                                                               
    Product Id's
    (I understood the link between Level 4 category id and product id with your info.) but not able to achieve the requirement fully.
    Is there any possiblity to achive for generateing a report?

  • "Creation" of location product hierarchy

    Hi Experts
    I know that a location product hierarchy can be "generated" by combining a location hierarchy and a product hierarchy. But for our business requirement we cannot use a generated location product hierarchy. This is because we have 1000'ds of products and for each product the parent location -child locations can be different. That is for product A if parent is location L1 and children are L2 and L3 then for product B the parent can be L1 but the children can be different say L5 and L4. There can be 1000ds of location parent - children combinations like this  and it is impossible to model this using a location hierarchy.
    So i want to know if there is a way to directly create a location product hierarchy and manually add members to it. Please advise
    Thanks
    Saradha

    I have found another way to make it work. Iam going to try using the concept of planning product and check how it goes.

  • Issue in Hierarchy data upload from R/3 for info object Product Hierarchy.

    Hi,
    I am trying to upload the hierarchy data from R/3 system for Info Object Product Hierarchy.
    Insted of business content info objects (0PRODH, 0PRODH1, 0PRODH2, 0PRODH3, 0PRODH4, 0PRODH5, 0PRODH6), we are using customized objects (ZPRODH, ZPRODH1, ZPRODH2, ZPRODH3, ZPRODH4, ZPRODH5, ZPRODH6).
    In transfer rules the mapped is as specified below
    Fields        =>  Info Objects.
    0ZPRODH1 => ZPRODH1
    0ZPRODH2 => ZPRODH2
    0ZPRODH3 => ZPRODH3
    0ZPRODH4 => ZPRODH4
    0ZPRODH5 => ZPRODH5
    0ZPRODH6 => ZPRODH6
    Now, when I schedule the Info Package, it is ending with an errors
    "Node characteristic 0PRODH1 is not entered as hierarchy charactersitic for ZPRODH"
    "Node characteristic 0PRODH2 is not entered as hierarchy charactersitic for ZPRODH"
    "Node characteristic 0PRODH3 is not entered as hierarchy charactersitic for ZPRODH"
    "Node characteristic 0PRODH4 is not entered as hierarchy charactersitic for ZPRODH"
    "Node characteristic 0PRODH5 is not entered as hierarchy charactersitic for ZPRODH"
    "Node characteristic 0PRODH6 is not entered as hierarchy charactersitic for ZPRODH".
    when i tried to load by flat file, there is no issues. But, flat file loading is not allowed for us.
    Please let me know any possible solution to handle this issue.
    Thanks.
    Regards,
    Patil.

    Hi voodi,
    Insted of using the info object 0PRODH1, we should use customized info object ZPRODH1 which I added already in the external characteristic in Hierarchy.
    Regards,
    Patil.

  • CO-PA: product hierarchy predefined from best practice

    Hi guys,
    unfortunately I have as basis a best practice system, where product hierarchy with 3 levels is already defined in CO-PA:
    PAPH1     ProdHier01-1     ProdH01-1     CHAR     5     MVKE     PAPH1
    PAPH2     ProdHier01-2     ProdH01-2     CHAR     10     MVKE     PAPH2
    PAPH3     ProdHier01-3     ProdH01-3     CHAR     18     MVKE     PAPH3                 
    PRODH     Prod.hierarchy     Prod.hier.     CHAR     18     MVKE     PRODH
    Those ones are already assigned to a best practice operating concern:
    10UK     Best Practices
    1. we have 7 levels in our product hierarchy
    2. I need to read it from mara and not mvke
    When trying to ad product hierarchy as characteristic in KEA5 in our new operating concern, I gut the message below.
    This data element is used in tons of tables and the whole precdure looks risky + after transport I might have issues again?
    Creating ww* characteristics for product hierarchy is not an option, since then I would need to maintain the whole product hiearchy as characteristc values again (like before release 4.5) and this is far more than 1000 entries and is double maintenance after go live.
    Deleting the best practice operating concern is also difficult, since there are several clients where customizing still sits for 10UK.
    Anybody experience? What did you do?
    regards
    Bjoern
    Here is the text from KEA5 when trying to ad mara fields (since date elment lenghts is different due to more levels):
    Product hierarchy field PAPH1 cannot be adapted to the new structure
    Message no. KE691
    Diagnosis
    The definition of the product hierarchy has changed (structure PRODHS). The hierarchy field generated in CO-PA, PAPH1 cannot be adapted to the new definition, because it is already being used in structures or tables.
    System Response
    The field PAPH1 does not appear in the list of fields that can be selected.
    It can no longer be used as a characteristic.
    Procedure
    If you still want to define hierarchy field PAPH1 as a characteristic, proceed as follows:
    1. Display the where-used list for data element RKEG_PAPH1 in database fields using transaction SE12. For hierarchy field PAPH1 to be adapted, a data conversion must be carried out for all the tables listed!
    2. First change the number of characters in the domain RKEG_PAPH1 to match the new definition of the product hierarchy, following the example below. You can do this using transaction SE11.
    Structure PRODHS     Domain
    Field    Length      name       Number of characters
    PRODH1     3         RKEG_PAPH1      3
    PRODH2     2         RKEG_PAPH2      5
    PRODH3     5         RKEG_PAPH3     10
    PRODH4     8         RKEG_PAPH4     18

    Just as Info,
    I needed to go for deletion of those characteristics - quite some work, like:
    1. delete all where-used entries for the characteristics in ALL CLIENTS of this system (important: e.g. planning layout - recommended to change and not simply delete, because the change can be transported)
    2. when then trying to delete characteristics (with "unlock" in KEA0 > value fields) - tons of tables and strucutres popped up, where this data element is still needed - follow note 353257
    3. generate best practice operating concern new (10UK in our case)
    4. create PAPH1 etc. new from table MARA (not mvke in our case - depends)
    all good - hopefully no issues after transport - we will see.

  • CO-PA Realignment: Changes in Product Hierarchy

    Hello all,
    We have changed the product hierarchy on some of our materials and we want to realign the PA data to reflect the same.
    Our product hierarchy which we have three levels is maintained in KES1. There are no derivation rules. KES1 is updated manually everytime any changes occur.
    For example:
    OLD
    Product: 1-189-01
    Hierarchy 1: 100
    Hierarchy 2:A7300
    Hierarchy3: B56220
    So on the material master the prod hierarchy is 100A7300B56220
    NEW
    Product: 1-189-01
    Hierarchy 1: 125
    Hierarchy 2:A7500
    Hierarchy3: B56120
    I tried using KEND for realignment and this does not change anything. Any help, how to proceed with the realignment is appreciated.

    Hi Anusha,
    Did u also update PH level in KES3 - in specific hierarchy variant ? Also would like to know how did u reset the operating concern
    Thanks,
    Samik (SAP MM)

  • R/3 Product Hierarchy in BW data model.

    Hi all,
    We have been told by our implementation partner that the scenario described below is not feasible to design in our BW 3.5 system and if we were to implement this scenario there would be a significant amount of user maintenance to maintain the hierarchy structure in BW.
    I was a query user in previous BW versions and my datawarehouse modeling experience is mostly in Cognos and Business Objects. The scenario described below is very easily implemented in these other datawarehouse software packages and I would be suprised if SAP does not have a standard solution to address the problem.
    I would like to understand if:
    (1) Yes this solution can be easily implemented in BW 3.5
    (2) A brief explanation on the design approach, implementation, and considerations
    I am already familiar with the link on http://sap.help.com that explains BW hierarchy design and considerations, but I would like to get a "real world" understanding of an approach and design and if you experienced this requirement.
    Thank You in advance for your input.
    Regards,
    -Anthony
    <b><u>Scenario:</u></b>
    In R/3 we have modified the standard delivered product hierarchy structure for material master from 5,5,8 to be 5,5,4,4.
    The 4 levels represent: BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
    Our intent is to use this structure to satisfy current BW reporting requirements for COPA and R/3 Billing infocubes.
    In BEx Explorer we would like to perform product analysis using the following dimension paths:
    BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
    PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
    PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
    We are told that since we have multiple values at the BRAND node we will not be able to perform grouped reporting the starts at PRODUCT LINE node(which would be independent of the BRAND node). For example:
    BRAND,          PRODUCT LINE,          PRODUCT CATEGORY
    HONDA,          AUTOMOBILE,          CIVIC
    HONDA,          AUTOMOBILE,          ACCURA          
    HONDA,          BLOWER,                  CIVIC
    HONDA,          MOTORCYCLE,          ODESSY
    FORD,          AUTOMOBILE,          EXPLORER          
    FORD,          BLOWER,                  EXPLORER          
    FORD,          MOTORCYCLE,          CHAMPION
    So for example we would like to start our dimensional anaylsis to show all AUTOMOBILE or BLOWER sales independent of the fact they were for HONDA or FORD.
    In other datawarehouse systems I have either: (1) created 3 dimensions called: BRAND, PRODUCT LINE, and PRODUCT CATEGORY or (2) created one dimension called BRAND with alternate dimension paths for PRODUCT LINE and PRODUCT CATEGORY. I am not sure if this is feasible in BW.
    We were also told in order to achieve this design a structure would have to be maintained in BW every time we introduce a new material master and the material master would need to be manually entered into the structure so that reporting can be achieved for both the standard structure and the alternate structure(s).<b></b>

    Antony ,
    there will be maintenance involved every time you add a material to the material master. However you could maintain the hierarchy through a GUI also depending on the number of values.
    Ideally if this can be maintained in a table in the source system , it can be imported into BW. Otherwise if you were to maintain it in BW , you will have a lot of problems when :
    1. Change in the hierarchy - A new Product Line coming in and many product category onwards change over to the new product line.
    2. Viewing the changed hierarchy over time - If you have GM and a separate category called Daewoo , earlier they were separate and now they are one - what are my product sales due to the merged entity vis-a-vis separate entities earlier...
    Things that you will need to consider from a design stand popint are :
    1. Should the hierarchy be time dependent ?
    2. Should it be maintained in the source system or in BW?
    3. Change process for the same - Flat file / Manual
    4. Estimate of how frequent the hierarchy would change?
    5. Will you have display hierarchies - Ad-Hoc hierarchies to view certain combinations?
    Depending on the above your hierarchy creation can go from easy to complex and hard to maintain.
    One way to amintain it is to have a SAP ABAP program to populate a hierarchy table to have the relations in R/3 and transfer them into BW. You could automate it in such a way that the hierarchy is changed every time there is a new material
    Otherwise , there can be a flat file to create the relationships
    Or someone could log a request and if the change is minimal it couldbe done thru a GUI Interface provided by BW.
    Arun
    Assiging  points is a way of saying thank you in SDN

  • Product hierarchy in COPA

    Hi all,
    I am new to COPA. What I need to do is creating a report that is using a product hierarchy that we can define.
    So I started and created a hierarchy in V/76 like we need it. Those values can now be entered into the "Prod. hierarchy" field for each material in material master - basic data 1.
    Then I have created a characteristic for the field MARA-PRDHA (Product Hierarchy) in COPA and assigned it to our operating concern in COPA. Now I created a form (KE34), double clicked on a column to add a characteristic and selected my PROD HIERARCHY characteristic. Now in the window for "selected characteristics" there is a checkbox "Flag for entering hierarchies" so I checked that, but it says "No hierarchies exist for this characteristic".
    So is this the right way to do it? How can I add product hierarchies to my COPA report, we would like to be able to "click" through the hierarchy, like starting on the highest level and clicking down.
    Thanks
    Anne

    Anne,
    Do not a check on checkbox "Flag for entering hierarchies" . Select value( Hierarchies from Definition drop down window) .
    Thanks,
    Mahesh

  • Stock overview on basis of product hierarchy (PRDHA)

    Hello to All,
    Is there any SAP standard report of displaying stock overview on basis of the 'product hierarchy' (Field: PRDHA) or do i have to make a copy of the transaction (MMBE) and add the respective field ..
    Looking forward to your feedback. Thanks
    Regards,
    Shehryar Dahar

    check this and do modifications as per ur requirement.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=15856
    get the PRDHA of MARA then report.
    Regards
    Prabhu

Maybe you are looking for