VC nomenclature
Hello Friends,
I am trying to gather information on what sort of rules can be made for various VC component nomenclature.
We have so many objects setup for VC,
Classes
Characteristic
Characteristic Value
Configuration Profile’s
Dependencies
So what do you suggest, do all this objects needs some rules to maintain nomenclature or not?
Let’s take example of product as CAR.
Broadly there are 3 types based upon pricing range.
Economy, Middle segment & Luxury
3 KMAT’s, ECO_CAR, MID_CAR, LUX_CAR
Consider CAR’s have just 4 assemblies, COLOUR, ENGINE, TRANSMISSION, TYRES
So should I go ahead and create this 4 Characteristic presenting these assemblies or each assembly of specific model needs a new Characteristic.
ENGINE
ENGINE_ECO
ENGINE_MID
ENGINE_LUX
How many classes do I need?
Just one per model to hold all characteristic for that Model or more?
Classes
CL_ECO
CL_MID
CL_LUX
I am starting this discussion and I am sure as each organizatipn has its own nomenclature for various objects, but there could be best practices in naming these objects.
Implementing a naming convention greatly helps. looking forward more additions in product attributes and introduction of new products.
So please reply with your thoughts.
Thanks
Ritesh
Ya, we have decided name for material , class where I work.
thanks
PV
We always have one class for each material. In a few cases we have had some characteristics that were common for a group of materials and then we created a class for them so that those materials had two classes attached - one with the characteristics specific for that material and then the class with the common characteristics. But in general I would say one class per material.
If I should make your model I would have four characteristics: COLOUR, ENGINE, TRANSMISSION, TYRES which then each hold the values for the three groups: Economy, Middle segment & Luxury.
Depending on how you use the model - if you use it with a customer or only for production I would strongly consider making a fifth characteristic CAR CLASS with the values: Economy, Middle segment & Luxury. You can then make dependencies which assure that if the customer wants an economy car then only the economy colours are available and economy engine etc.
Hope that helps you
Christina
Christina,
Thanks for comments.
Ritesh
good job
We generally use according to the models we configure, suppose if we say it a CAR and if it is KIA then Class will be VCL_KIA , characteristics will be VKIA_CHAR1,VKIA_CHAR2 etc...Dependencies would be VKIAPRE_HIDE_CHARACT , VKIAPRO_COMPONENT_SEL etc...PRE for Precondition and PRO for Procedure etc..
good work.
Our approach is to classify each material, and the name of the classification uses Z_CL_material number;
Then all the characteristics of this material are grouped into this classification.
E.g
Material number: MYCAR
Class：Z_CL_MYCAR
------
Characteristic
Z_CT_ENGINE
Characteristic Value
01-ECO
02-MID
03-LUX
-----
Characteristic
Z_CT_COLOUR
Characteristic Value
01
02
03
04
Dependencies
Dep. Net
PLANT_material number; 1000_MYCAR
Procedure
1000_MYCAR_PRICE
etc...