Define Product Hierarchy - Maintence Product Hier

I am trying to creating 3 Levels in the Data Relevant to Sales Distribution sec
I've created level 1's and 2
using     12345 Medical Devices level 1
             12346 Pharma             level 1
             123450001 Medical Devices Level 2
              123460001 Pharma     Level 2
now how do I create level 3 as I know I can on standard settings and please explain why the above numbers create level 1 and 2
I don't know why these above sequences created level 2 etc what basically is the pattern to create level 1 to 3 using my numbers above
help!
thanks

You can define it as Material Group. There are Material Groups 3,4 and 5 avaialble in Sales view of the material master which can be custom defined.
Another way is to define the product hierarchy as characteristics in COPA and define Characteristic Derivation Rules.
Assign Points if Helpful

Similar Messages

Product hierarchy and Product allocation

Dear SD Gurus,
Can I have some good docs on Product hierarchy and Product allocation related to SAP SD.
my mail id is [email protected]
Regards,
Rakesh

Hi
Product allocation helps in allocating prodects based on customer requirement.
Please go through this link for product allocation
http://www.sap-img.com/sap-sd/implement-the-product-allocation-functionality.htm
For product hierarchy go through this link
http://help.sap.com/saphelp_46c/helpdata/en/77/1a39516e36d1118b3f0060b03ca329/frameset.htm
give points if this useful
Thanks
Anil

Creation of new product hierarchy and products in SAP CRM.

Dear all,
please help with resolving of following issue:
In CRM system base hierarchies were replicated from R/3 system with materials. Current requirement is to create new materials in CRM directly (as standalone scenario). As far as I understand, I have to create new hierarchy with required list of set types in order to allow creation of products in CRM directly (product type = material). Can anybody describe changes in the system step by step, what should be changed and where?
As a result I need to have a possibility to create products in CRM directly for sales scenario processing.
Thank you in advance!

Hi Jorge,
thank you so much for your reply!
Here what I tried to do:
1. I created new category in hierarchy R3PRODSTYP, added 3 set types: COMM_PR_MAT, COMM_PR_SHTEXT, COMM_PR_UNIT as basic set types.
2. In the SPRO - Cross-Application Components - SAP Product - Settings for Product Type - Number Assignment - Define Number Ranges for the Product Type "Material" I found my new product category is unassigned, so I assigned it to the "CRM Products" group.
3. Farther I tried to create a new product for created category in CRM Web UI, but was not able to find it in the Base category search field. All categories correctly displayed from R3PRODSTYP, but my new category is absent. What can be the reason of category absence? Btw, it cannot be found even when I try to display whole hierarchy in Web UI, however, in SAP GUI, it can be seen via tcode comm_hierarchy.
Here is the setup of hierarchies in the system:
I have no idea how to check #3 "Ensure the hierarchy is assigned to CRM application".
Can you please suggest, what should be changed in addition? Thank you!

Product Hierarchy: Add product hierarchy whenever G/L for payment diff

Hello SAP Gurus-
We are on ECC 6.0. I have a requirement where the business wants a product hierarchy assigned to all postings to payment differences account during cash application.
How is this done?
Thanks!

To further clarify- under profitability segment, we want the the product group to automatically populate for a specific G/L.
how do we do this??

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 and Assortment Module?

Hi,
Can anyone throw some light on Product Hierarchy and Assortment Module?
Regrds,
Binayak

Hi,
Product Hierarchy:
Product Hierarchy is used to group the materails by combining features. It is used for analyses and pricicng. A produch hierarchy can consist of upto 18 characters. Its features can be combined in various ways, the following figure gives an example of how materials can be grouped using product hierarchy.
Product Hierarchy: Electrical Appliances(00001): 1. Dry Appliances(00001), 1.1 Electri Stoves(00000001), 1.2 Food Processors(00000002); 2. Wet Appliances(00002), 2.1 Washing Machine(00000001), 2.2 Dish washer(00000002).
In this case, a dish washer can be describered by product hierarchy 000010000200000002.
This is called as Product Hierarchy.
Assortment Module:
This is one type of Value contract using assortment module (Contract Type: WK1). Firstly we have to create Assortment Module using T.code: WSO1, and enter the group of material in the assortment module and save. and then create contract and assign the Assortment module number in the contract and enter the value and save the document. after that is same like other contract.
Hope i have answer your question
Reward if it helps
Regards
Prasanna R

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.

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

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

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

Product Hierarchy field in WBS

Hi Everyone
I have checked every where and still unable to find solution that whether can we add product hierarchy field in WBS or not? If yes then how can i?
I have already checked at spro>img reference>project systems>structures>operative structures>user interface settings> define layyout of WBS element deyail screens
But cannot get any answer or clue over there. I was wondering If the field Product heirarchy could add up (PRODH). please help

Hi Master mind,
What exactly do you mean by saying Product Hierarchy? As Ken said, its not a standard PS field. If you wish to add this field at the WBS element level you will need to go for an enhancement CNEX0007 Customer-specific fields in WBS elements
Regards
Varun

Product Hierarchy to COPA

Hi All,
We have defined and maintained product hierarchy as 4 levels with each level as 2 CHAR. This was done by appending the structure. Now in COPA,, how do we get this? Bcoz in COPA the characteristics are different. What changes needs to be done by COPA to pull this?
rgds..Ameet

hi
you can define the characterstics which is similar to the appended structure.
in SPRO - while defining the OPERATING CONCERN.
hope this clears your issue.
balajia

Product Hierarchy Derivation in COPA

Hi Gurus,
We have 6 levels of Product hierarchy defined in the system and I am able to include it in the data structure. The related Characteristics are PAPH1,PAPH2,PAPH3,PAPH4,PAPH5,PAPH6 included in my operating concern. Level 1 has 1 character in number and rest of the levels has 3 characters each in number as follows.
Level 1--1 Number of Character
Level 2--3 Number of Characters
Level 3--3 Number of Characters
Level 4--3 Number of Characters
Level 5--3 Number of Characters
Level 6--3 Number of Characters
Hence all together the total number/length is 16.
Now, when I generated the operating concern,the derivation rules for product hierarchy are created automatically as follows.
Following is the screen shot for source field if I open step number 22
The corresponding screen shot for Target field is as follows
For step 23 , the source field details are same as step 22 but target field details are as follows
We have assigned Product hierarchy in Material master in tab Sales:Sales Org 2 which is 16 digits.
Now when I try to test the derivation rule for step 22, system gives me following error
=================================================================================
Characteristic value 010 does not exist for characteristic PAPH2 (ProdHier01-2)
Message no. KE0C133
Diagnosis
The characteristic "PAPH2" ("ProdHier01-2") should be posted to Profitability Analysis (CO-PA). When the system checked the entries, it was established that the transferred characteristic value (" 010") is not valid in CO-PA.
System Response
The data is not consistent and therefore cannot be transferred to CO-PA.
Procedure
With the function Maintain Characteristic Values, you can add characteristic values to those that are valid.
==================================================================================
I am getting the same error for all steps in test mode. How to fix this error? Do I need delete the PAPH1--PAPH6 characteristics and use the user defined characteristics and write derivation rule again? Also I want to know the use of steps 28 to 31 (clear) in this regard.
I have not included characteristic PRODH in my data structure. Do I require to include it in my Operating concern?
Regards,
makrand

Dear Ajay,
Hearty Thanks for the solution. As suggested by you, I removed "move" steps and defined the Table Lookup" steps.
There are two target entries i.e MVKE (Origin) table and the field name is PRODH (Product Hierarchy) which is equivalent to second target entry COPA (Origin) field (PAPH1 -----to PAPH6) in the same line.
In field PRODH,I used offset position. I selected "Entire Field Contents" and kept character position as 0 and kept total characters as 16 in each table lookup entry.
Again I have to make offset settings in PAPH1---PAPH6 fields. I selected "Entire Field Contents" tab and system automatically changed the field length for PAPH1 to PAPH6. Now the results are correct.
I arrived at solution after making some combinations in offset. Thought, this may be useful for somebody facing the similar issue.
What's the use of "Clear" steps which are generated by system?
Thanks and regards,
makrand

PRODH & CO-PA Product Hierarchy

In our project , we had a three level product hierarchy structure with length of the each level being 5,5 and 8 respectively . Based on this, the characteristics fields in COPA were defined using the standard characteristics PAPH1 ,PAPH2 and PAPH3 . When doing this in CO-PA , SAP created domains RKEG_PAPH1 ,2 and 3 with similar length as the levels in structure PRODHS.
After this was completed , the product hierarchy structure has been changed in PRODHS to four levels with length as 4,4,4,4 respectively. As a result of that the domains RKEG_PAPH1 , 2 and 3 are not matching with the new structure and the PAPH1 to 3 characteristics in COPA have been made unusable.
To fix this SAP help is suggesting two things:
1) First change the number of characters in domains/data element RKEG_PAPH1 to 3 to match the new structure in PRODHS
2) Find out the list of tables/structure where RKEG_PAPH1 to 3 is used and perform a data conversion.
From the where used list , we are able to see that this are used in 21 structures which are in turn used in numerous programs, structures, BAPIs etc.
We would like to know :
1) What is impact of doing this on numerous programs, structures, BAPIs etc ?
2) How these data conversion is done and what utilities are used for the same? Is it required to do this as our project is still not live? Only Dev and Quality systems now running.
3) Potential issues that we may face?
4) Any other alternative solution.
Thanks,
Best regards,
Prashant

Hiya,
First impressions: Since you are not live yet, the impact is much lesser than if you were live. So thats saving grace.
I gather from your post that you either don't wish to leave these Chars as they are (ignore them and create new ones instead). Have you explored the possibility of using these for some other 5-char or 8-Char Characteristics?
The impact is massive, but restricted to BAPIs and custom programs you may have built based on these Chars. Whatever method you follow (new Chars or change these existing ones), you will still need to modify your reports to reflect the new data structures. But then, do you have an option?
You could use custom programs for data conversion, mapping your lagacy data to the new fields, or simply use Excel spreadsheets - that also depends a lot on the source of your legacy data.
Is it required? You don't data convert until your first cutover and that is mostly into a Regression Test server and then into the P server. So do you really need to bother about data conversion to the Dev or the Quality servers?
You may need to explore the possibility of deleting these Chars from the Op Co and including new ones. While this is not a recommended option, that way you can still transport only the required Chars to the P server and ignore the rest. Your Test or Quality servers will go for a toss (data mismatches etc.), but you could try and not let it affect your golden client.
Alternatives: explore the possibility of ignoring these 3 Chars and creating 4 new ones instead. That, by far, could be your best option.
All the best.

Basic type for product hierarchy v/76

Hi all,
I have another task that need to configure once a product hierarchy is created in Tcode v/76, it will trigger an outbound IDOC and send out.
Can anyone explain to me what basic type or message type should be used in this case?
Thanks for help.
Best Regards,
JL

Hi,
I am having the same issue, to send prod-Hier via Idoc.
Please let me know if you get the solution for the same,
BR,
Udit

Define Product Hierarchy - Maintence Product Hier

Similar Messages

Maybe you are looking for