Abbreviations used in the document:
|DA||DA is the generic term for Attributes (in other term a place holder to hold characteristics of a product) which could be either dynamic data attribute (DDA) or dynamic symbolic attribute (DSA)|
|DDA||Dynamic Data Attribute|
|DSA||Dynamic Symbolic Attribute|
|GUI||Graphical User Interface|
|IMCScript||A graph traversing syntax for In Mind’s MX platform to query Quote and SalesItem data for various purposes to be used in Config Engine, Price Engine|
|KB||Knowledge base which defines the structure of product and product rules that includes BOM explosion, range restriction and conditional rules|
|KBTriggerRelation or Quote Attributes||
A business type that can define the IMCScript to tell MX to fetch the value(s) inside the Quote or SalesItem.
|MX||Manufacturing X Sales Platform|
|Sales Item||SalesItem represents a line item inside the Quote where it can have linkage to the product and knowledge base|
|UI||UI is everything designed graphically into an information device with which a person may interact together with backend system|
|Quote||Quote is a technical representation of the Sales Document for MX. Quote can include more than one SalesItem|
The following terms and phrases are commonly used in the context of Sales Platform product. Each of them is followed by a brief description and it may include a link to more in-depth documentation of that subject.
|Attributes||The attributes of a product. Attribute can either by Dynamic Data Attribute or Dynamic Symbolic Attribute|
|BOM Explosion||Based on product BOM and the product rules, the MX will insert the related products as sub line items of the main configurable product according to the configured data and rules defined|
|Conditional Trigger||Any rule that can be executed in configuration engine if the condition is found to be true|
|Configuration Page||A configuration page is a user interface where the attributes of the product are shown for the user to configure the properties / characteristics of the sales item|
|Default BOM Explosion||Default BOM explosion means that one or more BOM products of the main configurable product will be added when main configurable product was added to the sales document|
|KBClass||A KBClass holds the attributes/characteristics that define the characteristics of classified product. A classified product can attach to KBClass and create the different default value for each KBClass|
|KnowledgeBase||Product model in MX, contains the set of dynamic attributes, its layout and trigger (conditional) information. Is also useful for range restriction and bill of material explosion|
|Global Precision Setting||This is the setting to scale the numeric value data according to the precision property defined in SettingPrecision which can be found under Master Data Management -> Setting Numeric -> SettingPrecision|
|Product modeler||A product modeler understands the business needs of the product and defines the structural information about the product as well as rules to do the BOM explosion, restricting some range value and changing the meta attribute property of the attribute|
|Schema||MX product schema. Lists all standard attributes that are used in In Mind product|
|OnType||It is used to specify the Domain business type of the IMC object. It is mainly used in price engine and config engine to help the user select the available values|
|OnAttribute||It is used to specify the attribute of the business type, example, objectName, objectERPId, objectExternalId. With onType and onAttribute properties, MX can gather all the attribute value belonged to the type specified in onType property|
|searchExpression||It is an expression that contains only the single statement. The search expression is used to fetch the value inside the Quote at run time. The syntax of search expression is same as IMCScript which can contains more than one statement, iteration and conditional expressions|
|KBSnapshot||In order word, Snapshot is the copy of configurable KB or classified KB which user can assign default value|
A product modelling is a task to create one or more products and define the product rules depending on the characteristics of the product. MX has a configuration engine which will apply the product rules defined in the product model to perform the BOM Explosion logic and range restriction as well as visibility of the attributes and its value. The MX internal price engine can also make use of configured data and exploded product to calculate the overall price/cost of sales document differently.
A product can be modeled using product BOM, attributes, knowledge base, rules and scripting.
The product modelling can be further divided into five main tasks, structure definition, calculation and rules definition.