Product Hierarchy/Category

Hi,
How can i download the Hierarchy and its Category to the deepest level, like what i can find in COMM_HIERARCHY transaction.
for example if i have the hierarchy and category like this.
ROOT----> Hierarchy
CD01----->category
      CD01_01--->sub category
          CD001_01_01--->sub category.
can i download this tree view in excel in the same format as above and if not then at least with there level in tree structure
for example CD001_01_01 is at level 3 and is child of CD01_01.
Thanks,
Sanju

Hi ,
You can use FM COM_PRDCAT_SEARCH_CATEGORIES to get category guid and heirarchy_guid using category_id as input . Then use FM COM_PCAT_READPHIERCHILDREN_O to get child categories by passing heirarcy guid as iv_product_hierarchy and category_guid as iv_parent_category.
Regards,
Nithish

Similar Messages

Create product hierarchy & category in CRM

Hello experts,
I need to write a program that create product hierarchy & category in CRM 5 from flat file.
As anyone know how to do it?
I couldn't find any bapi, and when i tried to debug the program that transfer this data between R3 to CRM i got to dead end.
I realy dont know how to attack this...
regards,
Ronen.

USE LSMW. Even i am working on a similar thing though i need to create products in CRM from excel file. Category and hierarchy ar supplied to me. Actually there are a couple of options.
Basically do research in SE37 with search term COMCATEGORYCREATE* and similarly for COMCATEGORYsav* for category and for hierarchy replace category with 'hier' . You can then shortlist which FM is good for you and try to construct structure in your program that u can pass to the FM to get desired output.
Thing to remember is that you first create and then do save.
1. Use following if input is from a *.txt or any tab delimited file.
INCLUDE com_product_const001.
INCLUDE com_product_const003.
*Excel data into Internal table
PARAMETERS: p_infile LIKE rlgrap-filename.
DATA: gd_file type string.
DATA: prod type N.
*Internal tabe to store upload data
TYPES: BEGIN OF t_record,
productid TYPE COMT_PRODUCT_ID,
product_desc TYPE COMT_PRSHTEXTX,
proudct_type TYPE COMT_PRODUCT_TYPE,
prod_categoryid TYPE COMT_CATEGORY_ID,
prod_obj_family TYPE COMT_PRODUCT_OBJECT_FAMILY,
prod_hierarchyid TYPE COMT_HIERARCHY_ID,
maintenance_language TYPE SY-LANGU,
prod_base_uom TYPE COMT_BASE_UNIT,
sales org1
sales org2
item category
END OF t_record.
TYPES : Begin of struc_mat,
 HEADER TYPE COMT_PRODUCT_MAINTAIN_API,
 DATA TYPE COMT_PROD_MAT_MAINTAIN_API,
 INTERLINKAGES TYPE COMT_PRODUCT_IL_API,
 CONDITIONS TYPE COM_PRODUCT_CND_API,
 DOCUMENTS TYPE COMT_PRODUCT_DOCUMENTS_API,
 END of struc_mat.
DATA: it_record TYPE STANDARD TABLE OF t_record INITIAL SIZE 0,
wa_record TYPE t_record,
ls_record TYPE t_record.
**For Unicode check active in program attributes then need to declare constants as follows:
**class cl_abap_char_utilities definition load.
**constants:
 con_tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_INFILE.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_infile.
CALL FUNCTION 'WS_FILENAME_GET'
 EXPORTING
 DEF_FILENAME = 'p_infile'
 DEF_PATH = ' '
 MASK = '*.txt'
 MODE = '0'
 TITLE = 'UPLOAD TAB DELIMITED FILE'(078)
 IMPORTING
 FILENAME = p_infile
 RC =
 EXCEPTIONS
 INV_WINSYS = 1
 NO_BATCH = 2
 SELECTION_CANCEL = 3
 SELECTION_ERROR = 4
 OTHERS = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*START-OF-SELECTION
START-OF-SELECTION.
gd_file = p_infile.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = gd_file
FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
 TABLES
 DATA_TAB = it_record
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 write: 'Error' , sy-subrc .
 skip.
ENDIF.
END-OF-SELECTION.
*!!! Text data is now contained within the internal table IT_RECORD
Display report data for illustration purposes
LOOP AT it_record INTO wa_record.
 WRITE:/ sy-vline,
 (10) wa_record-productid, sy-vline,
 (10) wa_record-product_desc, sy-vline.
 (10) wa_record-age, sy-vline.
ENDLOOP.
*The field data in structure for MAT & FIN are very different . Loop at retreived data and based on product
*type fill in the respective structure and proceed.
*PARAMETERS: g_matnr1 TYPE comt_product_id.
*PARAMETERS: gv_guid AS CHECKBOX DEFAULT on.
DATA : gv_save TYPE BOOLEAN VALUE 'X'.
LOOP AT it_record INTO wa_record.
 IF wa_record-proudct_type EQ '01'.
 PERFORM init.
 PERFORM create USING wa_record.
 PERFORM save USING gv_save.
 ELSE.
 ENDIF.
ENDLOOP.
2. Use excel file and use LSMW

Derive the category/subcategory from the product hierarchy (PRDHA)

Hi,
Is there a function module/table/transaction where I can derive the category/subcategory from the product hierarchy (PRDHA)?
Thks,
William

Hi,
I do see entries in /n/sapapo/relhshow. I don't see how the production hierarchy (Seen in /sapspo/mat1 under the properties tab) relates to it.
There is no F1 on that field in /sapapo/mat1 unfortunatly, so it acts like a free-form text field, as far as I can see. I changed it to a random value and it allowed me to save it, so it looks like there's no validation on the field?
William

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?

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
Scenario:
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).

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 MATERIAL MASTER ?

Hi experts
Can some body explain me about the Product hierarchy in material master under basic data view .??
Explain me about the purpose of Product hierarchy??
Which ind of industries will do with Product hierarchy??
And What the configuration has to done and where ??
What are the tyransaction in front to maintain the Product hierarchy??
In short without any links can some body explain ../
Many Thanks

Implement the Product Allocation Functionality
We are required to implement product allocation functionality in SAP R/3 (Enterprise Version).
We tried to do the elaborate steps as per the implementation guide but are not successful. Can you kindly help by giving the simple steps for implementation.
Please see if the following helps:
Configuration Overview; Allocation Specific Usage
1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation.
2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material
3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed
4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check.
5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials
6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant.
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant
8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified.
9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy
10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors
11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered
12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Invoiced Quantity grouped by Product Hierarchy

Hello,
I am trying to create an Evaluation (tCode MC11) which will report on Invoiced Quantity grouped by Product Hierarchy. I created an evaluation referencing an evaluation structure which references two other eval. structures: one - for data tables VBRP and the second for info. struct.S004. One of the characteristics is Product Hierarchy. The problem is, that when I execute the evaluation - I only get 4th level of product hierarchy, but I need to see all four, starting with the first one.
(I would like it to look like this:
level 1
     level 2
          level 3
                level 4
Thank you in advance for your help,
Olga

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 level in TPM Pricing condition records

Hi all,
we're setting up TPM scenarios in CRM7.0.
A question arosen about the level of the product hierarchy we need to create pricing records.
We have a 5 level product hierarchy structure and we're using the CRM feature to spread the product category at the lates level while creating trade promotion. In example if the user put in the product category tab a level 1 category the system spread down to the 10 level 5 underneath.
My question is: shall i generate pricing records at that level (lev5) or can i create the pricing records at higher level and keep the campaign dtermination one at the lowest?
Appreciate any reply
Regards

Hi Carmine,
It's not mandatory to create conditions at the lowest level, but my recommendation is to keep a match between the level you allow users to plan their promotion and the level of the condition records.
However depending on the scenarios, it may be valid to do otherwise. Some examples:
- A user assign a Level1 Category, and it's exploded into 5 lower categories. Then he creates a trade spend exception for 1 of the categories, the conditions should have (at least) the same level in order to create this exception.
- A user assign a Level1 Category, and it's exploded into 5 lower categories. The user wants to create only 1 condition at a higher level, then yes it can make sense to have condition with the higher level.
An option to allows both would be to have different condition generation type (one for High Level planning and one for lower level).
Some additional thoughts:
The feature that "explode" the high level category into lower categories, was developed for customers that wanted to restrict their users in planning at a lower level. It also helps to ensure a KAM does not create a condition for a whole Brand, but only to the level he's allowed.
The system is build to manage a high number of conditions.
Best regards,
Guillaume

ECC Product Hierarchy to CRM

Hi all,
We have a product hierarchy created in ECC in Tcode V/76. These hierarchies have 3 levels and assigned to different materail in ECC materail master.
We have done a initial load of Materail and all the products in CRM now have the R3PRODSTYP. But none of them got assigned to R3PRODHIER when I check in Product wokbench. This is making my product search in a Sales order really difficult.
Is it a standard behavior that R3PRODHIER does not get assigned automatically even though those materail belong to that hierarchy in ECC?
I cheked the SMW01, no errors in initial load of the objects "Material", "DNL_CUST_PROD01" etc.
Any help much appreciated.
Edited by: Praveen Rangineni on Aug 4, 2008 4:10 PM

Yes..That can be a possible approach. But the product maintenance workbench will not allow you to delete the base category with which the product was created.
Instead the best way is to use this recategorization trx. COMM_PROD_RECATEG to change the category assignment of all your products on the fly.
Please use this in TEST mode first and then go for it!
Thanks,
Sudipta.
Note: Unfortunately, the report cannot be executed to delete the assignment of a category to a product when that category is assigned to the base hierarchy.
In that case, a report program to reassign the base hierarchy would be 1 option. Alternatively, you need to purge your product data in CRM and restart the download from ECC after making the customizing change.
Edited by: Sudipta Sarma on Aug 5, 2008 1:00 AM

Customised Product Hierarchy assignment to application to "Sale" in CRM7.0

hi Gurus,
1.Here my client wants customised hierarchy(say "soldprod") created in sap crm 7.0 to be assigned to application "sale" instead of R3prodhier which is standard, and then he wants ECC products to be migrated as product category under this hierarchy.
is it possible..? or any workaround for this situation..?
2.can we assign application "sale" to two product hierarchy..? as far as i know it is not possible..
Thanks,
gaurav

Hi Tanya
My issue is got sovled with SAP note 1398619 .However, for the second issue there is no finding.
I am assuming ,that is standard SAP CRM behaviour , if we assign any account in crm , that will be shown in the assignment block.
Regards
Satish

Product hierarchy conditions

Hi,
I have a query on product hierarchy.
We are using standard product hierarchy 3 level structure.
My structre is like below:
PHLevel 1 : SBU
PHLevel 2: Category
PHLevel 3 : Brand
I have PH3 as Brand 1 and Brand2 under PH2
so someone pls tell me what happens in sale order is created with PH3 material, when i maintain condition records for PH2 as 10%dis and for Brand1(PH3) as 5%
which condition record system will consider? is it 5% or 10% why?
Thanks in Advance
Srikky
Edited by: Srikky on Dec 10, 2010 3:15 PM

Hi,
It purely depends on the sequence in which you have defined the condition tables. If the PH2 table is before the PH3 table, then obviously PH2 entries will be picked in the record and not PH3.
In case where there is one condition table with all the 3 levels and the data maintenance for these fields is maintained as Optional, then the rule of priority comes into picture.
In such case, when you assign the condition table to acc seq, you have to maintain the priority list for the optional fields of the condition tables in the access sequence. In this case, PH3 will have first priority, PH2 teh second and PH1 the last (more specific will have first priority than the less specific.
Now in this case PH3 if available in condition record, will be taken. If PH3 is not there , PH2 data will be used. If PH2 and PH3 are available, only PH3 data will be taken.
Hope this helps.

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 customers 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

Product hierarchy ID lost after transport

Hi experts,
could you please help me with the following problem: we have made customizing of the mapping of imported catogeries to the categories in the EBP for a schema.
The mapping is as follows: Imported category, Product hierarchy, Product category, The customizing was transported successfully but the product hierarchy ID field is empty in the target system although the hierarchy ID exists in the target system.
Any ideas what can be the problem?
Thanks for your help.
Tomas

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.

Level in product hierarchy ??

Hi
Some body can explain me about the levelin product hierarchy ??
Diefinition of level ?
Purpose of level??
Thanks

Product Hierarchy:
Product hierarchies are the domain of materials management. A product hierarchy is assigned to the material master record. This hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. This hierarchy number may have a maximum of 18 digits with a maximum of 9 levels. The custom Product hierarchies can be maintained in V/76.
Product Hierarchy Number of chars at Various level
In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9.
You can define hierarchy nodes at the individual levels of the product hierarchy.
The product hierarchy can be structured via DDIC structure PRODHS. In the standard system, a product hierarchy can be created with up to three levels. The individual levels can contain the following number of digits:
Level number of allowed digits
1 5
2 5
3 8
This can be changed as of Release 3.0, where it is possible to extend the maximum number of levels to 9.
If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows:
1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length).
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS.
You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3. Proceed as follows:
Create the following domains:
ZPRODH3 with length 5, category CHAR,
ZPRODH4 with length 3, category CHAR,
Change structure PRODHS:
Structure PRODHS in the standard system:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
Changes according to example:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 5
ZZPRODH4 PRODH4 CHAR 3
please take help of ABAPER in extending the levels of Product hierarchy
Configure for Product hierarchy at
SPRO -> IMG -> Logistics - General -> Material Master -> Settings for Key Fields -> Data Relevant to Sales and Distribution -> Define Product Hierarchies

Product Hierarchy download into CRM from ECC6

Hi Guys,
Recently we have added few Product hierarchies into ECC6 (level 2, 3 , 4 and 5 hierarchies)
now they are not replicated into CRM...
how can I replicate them into CRM from ERP6... quick guidance....?
The object - DNL_CUST_PROD1
Thanks
KP

it will be done maually,
- On CRM
For Defining the Product Hierarchy Strucuture :
CRM IMG -> Cross Application Components -> SAP Product -> Product Category -> Define Category Numbering Schemes
   - make new entry
          Number Scheme     R3PRODHIER
   - after that select the new Scheme, and choose a new entry (should be the same as structure PRODHS on ECC)
For Defining Product ID
CRM IMG ->Cross-Application Components->SAP Product->Basic Settings->Define Output Format and Storage Format of Product Ids (tx. COMCPRFORMAT)
note : should be matched with ERP (Tx. OMSL)
refrence B09_BB_ConfigGuide
الحمد لله الذي علمنا

Product Hierarchy/Category

Similar Messages

Maybe you are looking for