| # CF パッケージの用語集 Infor アプリケーションクラス An object-oriented representation of a relational table. A ERP LN application class gives you easy access from Configurator to information that is stored in the ERP LN database. ERP LN application classes serve as intermediary between relational ERP LN tables and object-oriented configuration classes. Infor アプリケーションクラスプロパティ The relational ERP LN table column (or property) to which a feature is mapped in a ERP LN application class. アプリケーションクラス An object oriented representation of a relational table A Session in ERP LN where data is stored assigned to classes and which is used in the Configurator package. アプリケーションクラスオブジェクト A specification of the specific object (instance) of a class. The application class object can be compared with a specific record (occurrence) in a table. アプリケーションクラスプロパティ When a class is related to a ERP LN application class, all ERP LN table fields are called properties. Each property is related to a feature. イベントメソッド A configuration constraint rule or configuration constraint expression that is used to include, exclude and select options. Event method expressions can be used to perform any kind of calculation or update when certain events like create, get, save and so on occur. インスタンス可能クラス Can be instantiated by one or more objects. オブジェクト A group of objects with simular characteristics. For instance a class can be Person. The class Person consists of objects, individual instances of a class. In this case the individual person John Mackingtosch is an example of the object of the class Person. A class has associated data linked to it like: name, birthday. . A persion has data allocated to 's age. be used to calculate Pietje Puk's age, by オブジェクト An individual instance (or occurrence) of a class. オブジェクトフィルタ A configuration constraint rule or configuration constraint expression that is used to select a single object (when applied to an object) or set of objects (when applied to a collection of objects). In case of a configuration constraint rule the configuration constraint only contains a condition part, while in case of a configuration constraint expression the environment variable SelectObject must be set after evaluating a (complex) calculation. オブジェクトブラウザ The user-interface of the Configurator. In the object browser you can view and maintain the Configurator data and the converted ERP LN data in an explorer-like way. In the Configurator framework you can define the way in which the object browser reflects the data. オブジェクトブラウザアイコン A bitmap used to represent in the object browser. For example: an open folder or closed folder an application a bitmap on a Form Tab user interface component or a Button user interface component. An open folder and closed folder icon can be used by a configuration view component of type view category. An application can be used by a configuration view component of type configuration class. オプション 特徴を表す定義済の値 特徴: 基本色 特徴オプション: 赤、緑、または青 オプションパッケージ An option package defines an implication between an option value and more option values of another feature. As an example of an option package consider the feature "edition". This feature has two predefined options standard and luxury. In addition to these two features, the features sunroof and air-conditioning exist. Both features have two predefined values: yes and no. An option package can now be defined to state that a luxury edition implies the inclusion of both sunroof and air-conditioning. On the other hand, another option package can be used to define that a standard edition has no sunroof and no air-conditioning. Formally this can be expressed by two option packages X and Y. X: (edition, luxury) -> {(sunroof, yes), (air-conditioning, yes)} Y: (edition, standard) -> {(sunroof, no), (air-conditioning, no)} Option packages come in two different types: Commercial, Technical. These types only influence the way option packages are used. Commercial packages are visible to the user because they carry commercial semantics. Technical option packages only have technical use, and therefore, these options are not presented on the user interface. オプションパッケージ A means to define a connection between one or more option values of another feature. An option package can now be defined to state that a luxury edition implies the inclusion of both sunroof and air-conditioning. On the other hand, another option package can be used to define that a standard edition has no sunroof and no air-conditioning. Formally, this can be expressed by the two option packages X and Y. X: (edition, luxury) -> {(sunroof, yes), (air-conditioning, yes)} Y: (edition, standard) -> {(sunroof, no), (air-conditioning, no)} Option packages come in two different types: Commercial, and Technical. These types only influence the way option packages are used. Commercial packages are visible to the user because they carry commercial semantics. Technical option packages only have technical use, and, therefore, these options are not presented on the user interface. Example Consider a feature edition with two predefined options: standard and luxury. In addition to these two features, the features sunroof and air-conditioning exist. Both features have two predefined values: yes and no. オプション値 The value you can assign to an option or a feature. Only features that have the domain list can have options. All features that have another type of domain have option values. Note In the Feature Options (cfcmd1110m000) session an option value is a specification of an option. In the Option Value field you can fill in any data to further distinguish an option. Example In order to distinguish between different options of the color red, you give each color red its own number. In order to know the prices of options and combinations of options, you can fill in a price in the option value field and calculate the different prices in the configurator. オプション値ドメイン A specification of the possible values a feature can hold. クラスメソッド A configuration constraint expression containing a piece of application logic that is related to a configuration class. バージョン Used to identify entities that slightly differ from a previous created base entity. モデル A set of configuration classes. A class is a group of objects with similar characteristics. モデルサーバ A set of classes stored on one computer in a network. Several model servers can exist on one computer. The data store for a class in a model server does not have to be on the same computer. One model server can contain classes from more than one conceptual model. ユーザインタフェース構成要素 A component of the user interface dialog. Each component has its own characteristics. There are components that only influence the layout of the user interface dialog (For example form, tabbed dialog, form tab and frame) and components that are able to handle data (text box, drop down list box and option button). In the figure above you see the user interface components and their relations (called user interface component relationships). A component of the user interface dialog. Each component has its own characteristics. There are components that only influence the layout of the user interface dialog (For example form, tabbed dialog, form tab and frame) and components that are able to handle data (text box, drop down list box and option button). ユーザインタフェース構成要素の関係 This is a parent child relationship by which the user interface components are arranged and eventually form an user interface dialog in the object browser. As an example see the figure below. The components Form Tab 1, Form Tab 2, and Form Tab 3 are children of the parent Form. The components Frame 1 and Frame 2 are children of the parent Form Tab 1. And so on. In the example above you see the user interface components and their relations (called user interface component relationships). ユーザの役割 Role played by a user. Examples of user roles are marketing and engineering. Users that play the role of an engineer within an organization choose the engineering role to access the desired information in the desired format. ライン番号 レコードが概要セッションで表示される順序を決定する番号 依存 A model server is dependent on another model server, if it refers to another model server in the same conceptual model. Example The conceptual model is split into two model servers (A and B), on two separate computers. Model server A consists of classes 1, 2 and 3, model server B consists of classes 4, 5 and 6. Model server A refers to class 4 (in model server B). Because each model server is compiled separately, model server B must be compiled before model server A. That is, model server A ｢depends｣ on model server B. 依存クラス The life of an object that originates from a dependent class depends on the existence of another object. An example is the BOM-relation which cannot exist on its own. The life of a BOM-relation depends on the life of an item to which it is related. If the item is deleted all the BOM-relations are deleted as well. 一般価格リスト Generic price lists form the basis for calculating the prices for particular product variants. For each generic item from the bill of material a price is computed separately. For each operation line a constraint rule may apply. 一般決定テーブル A two dimensional representation of data. On the two axes of the table a different feature can be used as input. These input values result in a single output value which is determined by the searching method defined for both axes. The generic decision table is able to represent data of the following types: Alphanumeric Integer Fraction Boolean Price 一般工順 製品バリアントの構成および生成時に作成されるバリアント工順の基準を形成します。作業ラインごとに、制約規則が適用されます。 一般品目データ Generic item data form the basis for the item data per variant which arise during the configuration/generation of a product variant. For each generic item data element a constraint rule may apply. 一般品目別制約 Constraints per generic item are constraint rules regarding the use of product features of product feature options for composing product variants. 一般品目別製品特徴 Product features per generic item are item-dependent characteristics allowing product variants to be composed. 一般部品表 製品バリアントを構成可能な、一般品目ごとの構成要素のセット。一般部品表は、製品バリアントの構成および生成中に作成されるバリアント部品表の基準を形成します。部品表ライン (構成要素) ごとに、制約規則が適用されます。 価格リストマトリックス X 軸と Y 軸の物理量の値にもとづいた価格テーブルです。 価格リストマトリックス ID 2 つの物理的数量にもとづく一連の値を表すコード。これらの値は、価格リストマトリックスの X 軸および Y 軸の値です。物理的数量ごとの値の最大数は 24 です。 関係タイプ Class relation types describe relations between classes and are assigned at class-level to state that objects of the involved classes are related. Relation types facilitate the inheritance of data between classes. For instance, the class Volvo has a relation with three other classes namely the dependent classes Volvo truck, Volvo van and Volvo family car. The relation type between Volvo and the types could be for instance "One of the car types of Volvo". You can inherit classes related to the class Volvo (for instance the class Color) to the classes Volvo truck and Volvo family car. As a result, these both classes have a relationship type called for instance 'Color options'. So the objects within the class family car do have a relation with the objects in the class color for instance Red, Blue. 継承フィルタ Inheritance is controlled by means of inheritance filters. Filters limit the inheritance of available features and options to derived classes. For instance an engineering view uses features which are not used in the marketing view. To limit the number of features and options that can be inherited from the engineering view to the marketing view you must specify an inheritance filter. 継承関係 An inheritance relation exists between two classes. The relation exists to make reuse possible of data-structure and application logic of objects of the involved classes. Application of inheritance relationships between classes result into super-classes and sub-classes. The derived class is the sub-class. The original class is known a super-class. 結合特徴 A feature that consists of a sequence of two or more other features. Example The feature address, which serves as an identification for a house, is identified by the combination of features zip code and house number. `Comb(address,<zip-code, house-number>)` In this example the features zip code and house number are combined feature parts. 結合特徴パート A feature that consists of a sequence of two or more other features. 例 Consider the feature address which serves as an identification for a house. A house is identified by the combination of zip code and house number. 言語 説明が記述された言語のコード 構成イベントの識別番号 Constraints are used as event methods. One occurrence of an event method is the Button press event. To relate an event method with event type Button press to a user interface component, a class event must be defined. Each class event is identified by a Configuration Event Identification. 構成クラス A group of objects with similar characteristics. For example, the class Person can consist of the objects Mr. Smith, Mrs. Smith and Dr Smith. A class can have data linked to it, for example Name and Date of Birth. A class can also have associated application logic linked to it. For example, Age can be calculated from today's date and Date of Birth. 構成クラスイベント An event is a piece of application logic (for instance Calculate age) which take place when for instance clicking a button. A configuration event is identified with an configuration event identification. 構成クラスメソッドタイプ Determines to which objects of a class, constraints are applicable. 構成ビュー A user interface definition that consists of a menu structure and dialogs, displayed in the object browser. The menu is made up out of configuration view components. The hierarchy between these configuration view components is defined by the configuration view component relationships. The dialog consist of user interface components. The hierarchy between these user interface components is defined by the user interface component relationships. Note The configuration view has a reference to the first (root) configuration view component. 構成ビューコンポーネントの関係 This is a parent child relationship by which the configuration view components are arranged and eventually form an user interface menu in the object browser. As an example see the figure below. The components Demonstration, Line Structure, and Parameters are children of the parent Main Menu. The component Demonstration Dialog is a child of the parent Demonstration. Because this is a configuration view component of type configuration class which represents an application this is also the lowest level of the menu structure. 構成ビュー構成要素 This is a component that is used in the hierarchy of a configuration view. There are two types of configuration view components: view category (represents a menu icon) configuration class (represents a dialog icon). A configuration view component of type configuration class has two important references: The configuration class that contains information on the data that can be displayed or modified via user interface components The root (first) component of the user interface. Example 構成モデル A set of configuration classes. A class is a group of objects with similar characteristics. 構成ユーザ Any user of ConfiguratorA user is identified by its name as recorded in the ERP LN environment. Configurator users are always a subset of ERP LN users. 構成ユーザの役割 A role played by a configurator user, such as a marketing or engineering role. Users that play the role of an engineer within an organization choose the engineering role to access the desired information in the desired format. Assigned to the role are the authorizations of the ERP LN user within the configuration model. Each user can have multiple roles, and each role can relate to multiple users. However, a user can be active (logged-on) in only one role at the time. Note A configuration role is linked to a normal ERP LN user in the Authorization Management System Module in ERP LN Tools. Super Users have all configuration user roles. 構成環境 The configuration environment defines the relationships between application servers and database servers. The database is outside the environment, the application (model) servers are inside the environment. The configuration environment defines the following parameters: the mapping (that is, description of associations) between the conceptual model of classes and the execution environment on which computer in a network each class is defined and the location of the objects of each class how a single conceptual model is split up into multiple models on several servers on one network. One model server contains a set of classes that are stored on one machine. 構成検証メッセージ System messages which show the constraint rules during configuration. These rules are part of constraint texts, in the form of either codes or text. Constraint validation messages only refer to constraint sections of the type Validation. 構成資源 A user-definable variable that is linked to a feature that can change in value. Generally, you have to define the configuration resource first before assigning it to a feature. This makes re-use of resources possible. Note The value of the feature linked to the configuration resource can be restricted by a resource constraint. This constraint specifies a minimum and maximum value for the feature. 構成制約 Expresses application logic that controls or performs an operation. One application is the translation of the customer requirements into the product structure of the variant. The configuration constraints indicate which components and operations will be used in a specific product variant. 構成制約グループ An identification that the selected configuration constraint belongs to a group of configuration constraints that share certain characteristics. 構成制約セクション Defines when (if applicable) the configuration constraint) must be evaluated. 構成制約タイプ Defines where and how the configuration constraint is used. 構成制約バージョン The version of the configuration constraint. The configuration constraint rule and configuration constraint expression are linked to the configuration constraint version. In Configurator version control must be enabled to work with configuration constraint versions. Only one version of the constraint may be active at the time. 構成制約確認メッセージ A message defined in one or more languages that can be used in a configuration constraint expression and which is shown to the user during the configuration process. 構成制約規則 A simple if-then statement. By this if-then statement you can include, exclude or select options depending on a condition. Explanation of each part its function: Condition part A condition part is a Boolean expression that expresses under which circumstances options have to be included, excluded or selected. The condition part checks a feature against a certain option value. Inclusion part The inclusion part is that part of a configuration constraint rule that expresses which options should have been selected. If this is not true, the configuration constraint is said to be violated. Exclusion part The exclusion part is that part of a configuration constraint rule that expresses which options should not have been selected. If this is not true, the configuration constraint is said to be violated. Selection part The selection part is that part of a configuration constraint rule that expresses which options will be selected. This configuration constraint can not be violated because option selection will be enforced. In other words, the options will be set as defined. The general format of the if-then statement is: `IF <condition part> THEN INCLUDE <inclusion part> EXCLUDE <exclusion part> SELECT <selection part>` 構成制約式 A block of source code in visual basic to perform 'complex' operations. 梱包オプション値 An option selected from a list, or a user definable option value that has been assigned to a packaged feature. 参照日 変更オーダおよび構成エンティティの有効性のチェックに使用されるユーザ定義可能な日付 次のような、変更オーダおよび構成エンティティの有効性のチェックに使用されるユーザ定義可能な日付 ユーザの役割 特徴 構成資源 有効性管理では、参照日と発効日および失効日が照合されます。参照日が発効日より後の場合、構成エンティティは有効です。 参照日が失効日より後の場合、構成エンティティは有効でなくなります。 資源 Are used to assign additional values to a feature. For instance, when you select air-conditioning as an extra feature, the resources Price of the car and the Weight of the car increase. So, the value of a resource depends on the chosen features. 資源タイプ The resource type specifies if the class feature to which the resource is linked functions as a supplier or a consumer of the resource involved. A supplying feature increases the resource value while a consuming feature decreases a resource value. If the resource value is limited to a certain interval by means of minimum and maximum features, ERP LN checks if a supplying feature does not exceed the maximum resource value and a consuming feature does not exceed the minimum value. 資源制約 A constraint that limits the value of a configuration resource by specifying a maximum and minimum value for the selected feature. 資源値 During configuration of a product, changes can occur in the value (for instance weight or price) of a product due to changes of the features and options you choose. Resource values display the differences. The value of the resource can be expressed in: Amount Percentage Sub total Total Text 失効日 エンティティの有効期間が終了する日付 有効性管理では、参照日と失効日が照合されます。参照日が失効日より後の場合、構成エンティティは有効でなくなります。 所有権 A specification of the configuration model to which the selected item belongs. The item can represent: A configuration constraint A feature And so on. 所有者 The ERP LN user who has created or modified the Configurator entity. 親変更オーダ The condition that is specified on the root of the tree when you create a bill-of-change-orders. This way, the change order can be synchronized, because all change orders become effective if the condition defined at the root note evaluates to true. 製品バリアント ID Product variant codes identify the separate product variants. 製品バリアント構造 一般製品構造および選択された製品バリアントオプションから製品バリアントを作成するために従う構成パス。 製品特徴オプション このトピックに関連するヘルプはありません。 製品特徴オプション Options per product feature that specify the product feature. 製品特徴記述 Language-dependent descriptions of product features. 製品特徴別オプション理由 Descriptions of aspects of product features. 特徴 構成クラスの特徴。特定の値を保持するどの種類のプロパティでも構いません。特徴の 1 例として色があります。 クラス特徴は次のように設定できます。 必須 永続的 (保存可能) 個人用 (構成モデルの外部では使用できない) 有効 (使用中) 明示的 (派生元) 注意 クラスには、特徴をいくつでもリンクできます。特徴にリンクできるのは、1 つのオプションのみです。 特徴カテゴリ A user-definable group that contains features that are classified based on their similar characteristics. A feature category is used to simplify the retrieval of features. 発効日 エンティティの有効期間が開始する日付 有効性管理では、参照日と発効日が照合されます。参照日が発効日より後の場合、構成エンティティは有効です。 複数言語サポート A tool in Configurator to define and handle descriptions of entities in multiple languages. 変更オーダ 有効性を制限または拡張する手段 次のエンティティに適用されます。 クラスの特徴 クラスの特徴のオプション クラスの特徴のオプションパッケージ クラスの制約 構成制約バージョン クラスの資源の値 変更オーダは、オプションベースまたは日付ベースにできます。変更オーダが日付ベースの場合、失効日/発効日と参照日の組み合わせにより、変更オーダが有効かどうかが決まります。 オプションベースの変更オーダは、オプション値の観点で条件を表現するために使用されます。たとえば、特定のシリアル番号に到達したときに変更オーダが有効になったり、特定のシリアル番号で変更オーダを有効にしたりします。 変更オーダ Change orders are used to limit or extend the validity. Change orders are used to limit or extend the validity of Features Options Constraints Etc Etc A change order can be option based or date based. When the change order is date based, the expiry and/or effective date, in combination with a reference date, determine the validity of the change order. 埋め込み特徴 A feature assigned to an option of another feature. Example 有効 このチェックボックスがオフの場合、 you do not want to use the feature, option, resource again. Inactive features, options, resources can be inherited to other classes but remain deactivated when inherited. 有効性管理 A means to check whether entities modeled in Configurator are valid. Almost every entity modeled in the Configurator has an effective date and an expiry date that defines the entity's validity period. If a reference date is specified, you can check whether the entity is valid. If the effective date is B and the reference date is C, the entity in Configurator is not valid. If the expiry date is B and the reference date is C, the entity in Configurator is valid in the interval (C <-> B). Example If the effective date is A and the reference date is C, the entity in Configurator is valid. 連番 順序を決定する番号 次の順序を決定する番号 レコードが概要セッションまたはリストボックスに表示される順序 特徴などの構成要素がユーザメニュー (ユーザダイアログ) に表示される順序 |