New features added, version 7.5.2, 7.5.3, 8.1
Program MOTM, Modular Bill Maintenance, is used to enter and maintain modular items. This program allows you to construct an item from a variety of component items.
Four types of models can be constructed in this program, models, kits, prompts, and planning bills.
* Models are configurable and can be sold. Configurable means that they have prompts assigned to them to allow a selection of different items to make up the model. Models can have models, prompts, kits, and inventory items assigned to them.
* Kits are not configurable and can be sold. Kits cannot have prompts assigned to them and are not allowed a selection of different items. Kits have a certain set of items assigned to them, with no other options. Kits can have kits and inventory items assigned to them.
* Prompts are used in the configuration of models. Prompts allow you to choose which item of a selection of items that you want to have in the construction of your modular item. Prompts can have models, kits, and inventory items assigned to them. Prompts cannot be directly assigned to prompts.
* Planning bills are a future feature, and currently have no use.
Changes made to an item in program MOTM, Modular Bill Maintenance, can be applied to items that have already been configured in program MOCF, Modular Bill Configuration. When the [Configure] button is pressed in program OEOE, Sales Order Entry Maintenance, for the item, the program will return the following prompt:
* A newer release for this model ECL is available for this model. Do you wish to migrate configuration to the new ECL release?
* If you wish to update the configuration to the current release number from program MOTM, Modular Bill Maintenance, press the [Upgrade to Current Version] button. Make any necessary changes to the configuration for the new release.
* If you do not wish to update the configuration, press the [Keep existing model] button.
Model String Configuration, Model Codes, and Named Properties
Fixed Quantities for Modular Components
String Configuration using Model Codes
String Configuration using Named Properties
Adding Other Items to a Model Item
Creating and Maintaining Attributes
Assigning Attributes to an Item
Copying Component Items between Model Items
Copying Component Items within a Model Item
Adding Routings to a Model Item
Adding Model Codes for a Specific Item
Adding Named Properties to a Model Item
Adding Named Properties to a Component Model or Item
There are three ways for model items to be priced.
* The model can have a single price for all configurations of the model.
* The model price can be a combination of the model's component items.
* The model price can be defined according to the named properties and values assigned to the item during configuration.
Model pricing can occur at any point in a modular bill. There might be a kit in the model configuration for which there is a set price, while the price for the main model can be a combination of the price for that kit and the prices of two other inventory items.
The price matrix uses the model price, no matter how it is calculated, as the list price when it is determining the price to use when the model item is sold.
To have the model be priced the same for all configurations, set the Price Method pop-list to Model Pricing and enter the list price for the item in the Model Price field in program MOTM, Modular Bill Maintenance, or in the List Price field in program ICSM, Inventory Sales Data Maintenance.
To have the model be priced as a combination of the model component items, set Price Method pop-list to Detail Pricing.
To have the model be priced according to the named properties and values, set the Price Method pop-list to Property Pricing. For more information, see the Property Based Model Pricing section.
Parent model costs are rolled up from the routing costs and component item costs in program ICMM, Inventory Master Maintenance. Model costs are always rolled up regardless of the setting of the Price Method pop-list in this program.
If a parent model has component models assigned to it, the costs entered for those models in program ICCM, Inventory Cost Data Maintenance, will also be added to the cost.
For example, the total cost for model A will be as follows. The cost from program ICMM, Inventory Master Maintenance, for each component item will be added to the cost of the parent model item from program ICCM, Inventory Cost Data Maintenance, to get the total top level cost for the model.
ICCM Cost Total Cost
Model A 20 70
Component Model B 10 20
Component Inventory Item B-1 5
Component Inventory Item B-2 5
Component Kit C 0 10
Component Inventory Item C-1 5
Component Inventory Item C-2 5
Component Inventory Item D 10 10
Routing Operation 10 10 10
Caution: You should be extremely cautious when assigning attributes to fixed quantity components. Fixed quantity components are based on the sales order line quantity while attributes are based on each model by itself. Assigning attributes to fixed quantity components could cause unexpected results.
Models can be assigned attributes. Attributes describe the features of a model item and its components. These features are used in the construction of the model.
There are two kinds of attributes, provided attributes and consumed attributes. A model or its components can have any combination of attributes. To better explain how provided and consumed attributes work, the following is an example of a personal computer.
* Provided attributes are the features that the item provides that can be used by other items in the model. For example, a computer can have interfaces that provide such attributes as slots (ISA slot, SCSI slot, SIMM slot, etc.). A disk drive might provide the attribute of a disk. A memory chip would provide so many megabytes of memory.
* Consumed attributes are the features of the item that use the attributes other items provide. For example, a computer can consume such attributes as a disk, memory, and central processing unit. The disk drive might consume a SCSI slot and a power plug. A memory chip might consume a SIMM slot.
There are three types of enforcement for an attribute. Enforcement is used during configuration to help determine the validity of the configuration.
* Mandatory: if the attribute is in deficit for an item during configuration, the configuration will be invalid.
* Warning: if the attribute is in deficit, a warning will be displayed, but the item will not be affected.
* Disabled: the attribute is disabled, no messages will be displayed, and no items will be affected.
Attributes are assigned a unit of measure for reference.
Attributes are defined with the [Maintain Attr] button. The attributes are defined without connection to a particular modular item, so any attribute that you enter with this button can be used on any modular item in this program.
When an attribute is defined, an explanation can be entered in the text field for the attribute. This text will be displayed when the attribute is lacking during sales order entry, and the [Explain] button is pressed with the lacking attribute selected.
Attributes are assigned to items using the [Attribute Usage] button or using the [Attributes] button on the Navigator screen.
* For instructions on creating attributes, see the Creating and Maintaining Attributes section.
* To add attributes to an item, see the Assigning Attributes to an Item section.
Model components can now be set up with fixed quantities. Modular bill fixed quantities are based on work orders created from sales order lines.
For example, if you entered a sales order line with a quantity ordered of 13, and one of the components was a fixed quantity component with the quantity of 1, when the work order was created only 1 of that component will be used for all 13 of the models. If the item is a serial controlled item and you select one work order per serial item, one of the item will be used in each of the 13 work orders created for the order.
If a fixed quantity is applied to a component with components, such as a model, that fixed quantity will be extended to its components.
Caution: You should be extremely cautious when assigning attributes to fixed quantity components. Fixed quantity components are based on the sales order line quantity while attributes are based on each model by itself. Assigning attributes to fixed quantity components could cause unexpected results.
Model codes are used in sales order entry as a way to configure models without entering program MOCF, Modular Bill Configuration. In order to use model codes to configure a model, a model code separator must be entered in program MOPM, Modular Parameter Maintenance, and model codes must be assigned to the model and model component in program MOTM, Modular Bill Maintenance.
* The model code separator cannot be the same as any characters that are used in the model item number itself. For example, if you have model item numbers with - in them, you should not use the - as the model code separator.
To configure models using the model codes, you enter the model item on the sales order line, followed by the model code separator and the desired model code. If multiple model codes are being entered, the model separator must be entered before each code.
* For example, suppose the model separator is - and the following model codes have been set up for the model item - 64MB and STD. The model item number is PC200. On the sales order line, the user would enter PC200-64MB-STD and then go to the next field.
* As soon as the cursor leaves the item number field, the configuration that was entered in the item number field updates the configuration for the item.
* This configuration information can be viewed in program MOCF, Modular Bill Configuration, and using the Model Details button in the sales order entry program.
For models using model codes, components will be selected if any of the listed model codes match. When a model code selects a component, the parent of that component is also selected.
Standard configuration rules apply, however. This means that if the configuration is not valid with the entered model codes, the program will inform the user and more information will have to be entered in program MOCF, Modular Bill Configuration, before the model item can be manufactured or shipped.
Default model codes are assigned to prompts and are used to automatically configure a prompt if the model codes entered in the string configuration on the sales order line do not configure the prompt.
Model String Configuration, Model Codes, and Named Properties
Named properties are used in sales order entry as a way to configure models without entering program MOCF, Modular Bill Configuration. In order to use named properties to configure a model, a model code separator and a model quantity separator must be entered in program MOPM, Modular Parameter Maintenance, and named properties must be assigned to the model and model component in program MOTM, Modular Bill Maintenance.
* The model code separator and model quantity separator cannot be the same as any characters that are used in the model item number itself. For example, if you have model item numbers with - in them, you should not use the - as the model code separator or model quantity separator.
To configure models using the model codes, you enter the model item on the sales order line, followed by the model code separator, named property, model quantity separator, and property value. If multiple named properties are being entered, the model separator must be entered before each code.
* For example, suppose the model separator is ',' and the model quantity separator is '='. The model item 'CAR' has been set up with the properties AUDIO, TRANS, and COLOR. On the sales order line, the user would enter CAR,AUDIO=STD,TRANS=AUTO,COLOR=GOLD and then go to the next field.
* As soon as the cursor leaves the item number field, the configuration that was entered in the item number field updates the configuration for the item.
* This configuration information can be viewed in program MOCF, Modular Bill Configuration, and using the Model Details button in the sales order entry program.
Any component at any level within a model structure can have a list of named properties and associated values applied to it. At the time of auto-configuration the following rules are applied:
* Only those properties whose names are specified in the configuration string are examined.
* If a given component has a matching value for each property it has in common with the configuration string, it is a candidate for selection, subject to the rules below.
* If a component has a property in common with one in the configuration but does not have a matching value, the component is excluded.
* If the parent is a model and is selected, the component is automatically selected.
* If the parent is a prompt, the component is excluded if not selected by property.
* If the parent is a model, is not selected, and the component has been selected by property, the component is excluded.
These rules combine with the effect that component selection can be based on combinations of property values.
As components are selected, they may receive an initial quantity value from one of the properties involved in the selection, subject to the minimum and maximum qty per limits.
In addition, the named property scheme allows pricing based on the property values.
Standard configuration rules apply, which means that if the configuration is not valid with the entered named properties, the program will inform the user and more information will have to be entered in program MOCF, Modular Bill Configuration, before the model item can be manufactured or shipped.
Model String Configuration, Model Codes, and Named Properties
Adding Named Properties to a Model Item
Adding Named Properties to a Component Model or Item
When assigning a component to a model on the Model Bill Items screen, you can define a query that will return the initial quantity during model string configuration based on the properties and property values assigned to the component and model.
* This feature can only be used in conjunction with the String Configuration using Named Properties feature.
* Some knowledge of SQL is required in order to use this feature.
The query can employ any SQL function provided by Oracle. It can refer to property values and attributes in the configuration, as described below. The query must return a single numeric result and can be overridden if manual configuration is performed in program MOCF, Modular Bill Configuration.
The query results are subject to the minimum and maximum quantity per limits assigned to the component. If the query results in no rows returned or an error, the initial quantity assigned during the component selection is retained.
When referencing properties in the query, enter the property names in uppercase and place a caret '^' before and after the property name.
* For example, if you wish to return a surface area quantity based on the values specified for the HEIGHT and WIDTH properties in the configuration string, you might define the query as:
select ^HEIGHT^ *^WIDTH^ from dual
When referencing attributes in the query, the attributes are entered in uppercase, carets '^' are placed before and after, and the at sign '@' is placed after the first caret to indicate that the reference is an attribute. In addition, there other characters used to select which number associated with the attribute is used.
* Total consumed: dash '-'.
* Total provided: plus '+'
* Net amount: equal '='
For example:
* If you wish to select the total consumption for the SLOTS attribute from the configuration, you would define the query as:
select ^@-SLOTS^ from dual
* If you wish to select the property values for height multiplied by the attribute total for the PANELS attribute, multiplied by 2, you would define the query as:
select 2*^HEIGHT^*^@+PANELS^ from dual
When referencing attributes during auto-configuration, the totals are derived after all component selections have been made and after all quantity queries that do not contain attribute references have been executed. No attempt is made to resolve dependencies or reflexive relationships between components which use attribute reference queries. Such constructs should be avoided.
When entering the program the first screen that appears is the Model Selector screen. The model selector screen is used to query the model items that you wish to maintain.
From the model selector screen you can:
* Maintain modular items.
* Maintain attributes.
* Maintain model codes.
* Maintain named properties.
When a model item is queried, you can:
* View the tree for the item.
* Maintain the attribute usage for the item.
* Maintain the routing for the item.
* Maintain named properties for the item.
* Maintain comments for the item.
* Make the ECL and RRV current for the item.
* Set up property based pricing.
When you press the [Tree] button, the Navigator screen is displayed.
The Navigator screen allows you to view and maintain the items assigned to a modular item. From this screen you can add items, remove items, and copy the items assigned to a modular item.
Selected items are highlighted on this screen. To highlight an item in this screen, click on it with your left mouse button.
When the [Create] button or the [Modify] button is pressed, the Modular Bill Items screen is displayed. It will also be displayed if you double-click on an item without a + or - in front of it.
Items displayed in the tree are different colors to indicate the type of item.
* Green items are model type items.
* Purple items are prompt type items.
* Brown items are kit type items.
* Blue items are inventory items.
* Press the [Expand] button to expand the modular bill by one level for the selected item or prompt.
* Press the [Expand All] button to expand the entire tree.
* Press the [Collapse] button to collapse the tree below the selected item or prompt so that only the selected item or prompt is displayed.
* Press the [Collapse All] button to collapse the entire tree. This will collapse all items and prompts so that only the item or prompt that was selected in the Model Selector screen is displayed.
The Modular Bill Items screen allows you to maintain the parameters of the items assigned to the model item, maintain model codes assigned to the model item, and maintain the named properties assigned to the model item.
This screen can be accessed with the [Modify] button, the [Create] button, or by double-clicking on an item without a + or - in front of it on the Navigator screen.
1. From the Model Selector Screen, press the [Maintain Models] button.
2. The Maintain Models screen opens in query mode. Press [Execute Query} to display the existing models, or press [Exit] to cancel the query.
3. Press [New Record]. In the Model No field, enter the model number.
4. In the Name field, enter the model description.
5. Set the Type pop-list to the desired model type. Four types of models can be constructed in this program, models, kits, prompts, and planning bills:
* Models are configurable and can be sold. Configurable means that they have prompts assigned to them to allow a selection of different items to make up the model. Models can have models, prompts, kits, and inventory item assigned to them.
* Kits are not configurable and can be sold. Kits cannot have prompts assigned to them and are not allowed a selection of different items. Kits have a certain set of items assigned to them, with no other options. Kits can have kits and inventory items assigned to them. Kits cannot be controlled items.
* Prompts are used in the configuration of models. Prompts allow you to choose which items of a selection of items that you want to have in the construction of your modular item. Prompts can have models, kits, and inventory items assigned to them. Prompts cannot be directly assigned to prompts.
* Planning bills are a future feature, and currently have no use.
6. Set the String Method field to the desired setting.
* Set the pop-list to Model Codes if this model will be configured in sales order entry programs using string configuration with model codes.
* Set the pop-list to Named Properties if this model will be configured in sales order entry programs using string configuration with named properties.
* For more information on model codes and named properties, see the Model String Configuration, Model Codes, and Named Propertiessection.
7. Set the Treat Model as Kit flag to the desired setting for Model items. The default value for new models is determined by the Models are Treated as Kits for OE Allocation flag in program SPMM, System Parameters/Default Maintenance.
* When this flag is set to off, the model is treated normally, and sales allocations are created for the model. When the work order for the modular item is completed and received, the item can be shipped with program OESC, Shipping Confirmation. Work orders can be created for a modular item after the order is created and exists in program OEOE, Sales Order Entry Maintenance, or program OQEM, Sales Order Quotation Entry/Maintenance.
* When this flag is set to on, the model is treated as a kit for sales allocations and shipping.
* For more information, see Model Treatment for Allocations and Shipping
* Kit items cannot be configured. Kits are not allocated to sales. Instead, the kit components are allocated to sales, and the components are shipped in program OESC, Shipping Confirmation.
8. In the UM field, enter the stock unit of measure for this model.
9. In the ECL field, enter the active engineering change level for the model.
10. In the RRV field, enter the active routing revision level for the model.
11. Set the Price Method flag to the desired setting.
* Set this pop-list to Model Pricing if the item will be priced the same for all model configurations. The list price is entered in the Model Price field.
* Set this pop-list to Detail Pricing if the item will be priced according to the prices of the model's component items.
* Set this pop-list to Property Pricing if the item will be priced according to the named properties assigned to the item. For more information, see the Property Based Model Pricing section.
* The default setting for this pop-list is dependent on model type and is determined by the pop-lists in program MOPM, Modular Parameter Maintenance.
12. If the Price Method pop-list is set to Model Pricing, enter the list price for the model in the Model Price field.
13. If the item will be serialized, set the Serialized flag to on. Serialized items are assigned a serial control number.
* If the model item will have a production schedule created for the configuration, the item should be a controlled item. This allows the configuration to be dealt with through the production schedule system. Otherwise, the configuration could be confused with the configuration of another of the same model item.
* The default value for this field is set by the Serialized Default in program MOPM, Modular Parameter Maintenance.
14. Set the Sub-Tier Project flag to on, if this model is to be used in project management and converted to a sub-tier project during sales order to project conversions with program PMSM, Convert Order/Quote to Project.
* When a sales order for a model item with this flag set to on is converted to a project with program PMSM, Convert Order/Quote to Project, the model item will be converted to its own sub project, linked to the master project generated for the sales order. All components and routing operations for the model will be converted to project lines on the model sub project.
* If this flag is set to off, it will not be converted to a project line when sales orders are converted to projects with program PMSM, Covert Order/Quote to Project.
15. Press [Commit].
The items that can be added to a model item depend upon the model type. Model type items can have prompts, models, kits, and inventory items added. Kit type items can have inventory items and kits added. Prompts can have models, kits, and inventory items added.
1. From the Model Selector screen, query the model item to which you are adding other items. Press the [Tree] button.
2. The Navigator screen will be displayed. Highlight the desired item. Press the [Create] button.
3. The Modular Bill Items screen will be displayed for the item. In the Sequence field, enter the sequence number for this component item.
* The same component item can be used twice in a modular bill. This indicates the order in which it is used.
* It is also used to indicate the processing sequence for the work order. For each operation sequence for the model item, sequence numbers that are blank will be exploded first and so on in ascending sequence.
* This number also indicates the order in which the components will be displayed during configuration with program MOCF, Modular Bill Configuration.
4. In the Component field, enter the component item number.
* Kits assigned to models are treated as models without choices for processing purposes in sales order entry.
5. In the Effective From field, enter the first date on which this component will be included in the configuration of the model. Effectivity dates are optional.
6. In the Effective Thru field, enter the last date on which this component will be included in the configuration of the model. Effectivity dates are optional.
7. In the Min Qty Per field, enter the minimum quantity allowed per assembly for this component item for this model.
8. In the Max Qty Per field, enter the maximum quantity allowed per assembly for this component item for this model.
9. Set the Fixed Qty flag to on, if the quantity for this item is a fixed quantity.
* The fixed quantities are based on work orders created from sales order lines.
* For example, if you entered a sales order line with a quantity ordered of 13, and one of the components was a fixed quantity component with the quantity of 1, when the work order was created only 1 of that component will be used for all 13 of the models.
* If the item is a serial controlled item and you select one work order per serial item, one of the item will be used in each of the 13 work orders created for the order.
10. If the item is a prompt item, in the Min List Items field, enter the minimum number of component items that can be selected for this prompt during configuration with program MOCF, Modular Bill Configuration.
* For example, if no component items attached to the prompt were required to be selected, you would enter 0 in this field.
* If at least one of the component items attached to the prompt were required to be selected, you would enter 1 in this field.
11. If the item is a prompt item, in the Max List Items field, enter the maximum number of component items that can be selected for this prompt during configuration with program MOCF, Modular Bill Configuration.
* For example, if only one component item attached to the prompt could be selected, you would enter 1 in this field.
* If three component items attached to the prompt could be selected, you would enter 3 in this field.
* If you enter 0 in this field, no components attached to the prompt will be able to be selected during configuration.
12. In the Operation Seq field, enter the operation sequence for this item for the model routing.
13. In the Lead Time Offset field, enter the lead time offset for this item for the model routing.
14. Set the Backflush flag to on if the component will be backflushed when work orders are created for this model item.
15. If you are adding an inventory item to the model, set the Configurator Display flag to the desired setting.
* Set it to on to indicate that the item will be displayed in program MOCF, Modular Bill Configuration, during model configuration.
* Set it to off indicates that the item will not be displayed in program MOCF, Modular Bill Configuration, for configuration, but will be displayed on the bill of material.
16. Set the Print on Acknowledgement flag to on to include the component item on sales order acknowledgements.
17. Set the Print on Pick List flag to on to include the component item on pick lists.
18. Set the Print on Pack List flag to on to include the component item on pack lists.
19. Set the Print on Invoice flag to on to include the component item on invoices.
20. Set the Include in Sales Analysis flag to on to include the component item in the sales analysis detail information displayed in program SAIQ, Sales Analysis Order Line Inquiry.
21. If the item that you are adding is a prompt, you can enter the Default Model Code for the item, which will be used for string configuration of models during sales order entry.
* For more information on how to use default model codes, see Model String Configuration, Model Codes, and Named Properties and Assigning Default Model Codes.
22. In the Initial Qty Query field, you can enter a SQL query that will return the initial quantity for this component based on property values assigned to the item during string configuration with named properties.
* This feature can only be used in conjunction with the String Configuration With Named Properties feature.
* For more information, see the Query Based Initial Quantity section.
23. Press [Commit] or press the [Attach] button to add it to the modular bill.
Attributes are defined without connection to a particular modular item, so any attribute that you enter can be used on any modular item in this program.
1. On the Model Selector screen, press the [Maintain Attr] button.
2. In the Attribute Name field, enter the unique name for this attribute.
3. In the Description field, enter the description for this attribute.
4. In the U/M field, enter the unit of measure for this attribute.
5. In the Enforcement pop-list, select Mandatory, Warning, or Disabled. Enforcement is used during configuration to help determine the validity of the configuration.
* Mandatory: if the attribute is in deficit for an item during configuration, the configuration will be invalid.
* Warning: if the attribute is in deficit, a warning will be displayed, but the item will not be affected.
* Disabled: the attribute is disabled, no messages will be displayed, and no items will be affected.
6. In the text field, you can enter an explanation for the attribute. This text will be displayed when the attribute is lacking during sales order entry, and the [Explain] button is pressed with the lacking attribute selected.
7. Press [Commit].
The [Attribute Usage] button is found on the Model Selector screen, under the [Maintain Models] button, and under the [Attributes] button on the Navigator Screen.
Caution: You should be extremely cautious when assigning attributes to fixed quantity components. Fixed quantity components are based on the sales order line quantity while attributes are based on each model by itself. Assigning attributes to fixed quantity components could cause unexpected results.
1. Press the [Attribute Usage] button or the [Attributes] button. The attributes assigned to selected item will be displayed.
2. The left side of the screen, titled PROVIDED, is for entering attributes that the item provides for other items to consume. The right side of the screen, titled CONSUMED, is for entering attributes that the item consumes, which other items provided.
3. In the Attribute field, enter the attribute.
4. In the Quantity field, enter the quantity provided or consumed of this attribute by this item.
5. In the Eff From field, enter the first date in the range of dates for which this attribute is valid for this item.
6. In the Thru field, enter the last date in the range of dates for which this attribute is valid for this item.
7. Press [Commit]. The attributes are assigned. For more information on attributes, see the Attributes section.
1. On the Model Selector screen, query the model item from which you wish to copy a component item.
2. Press the [Tree] button.
3. Select the item that you want to copy.
4. Press the [Copy] button.
5. Return to the Model Selector screen. Query the item to which you wish to copy the component item.
6. Press the [Tree] button.
7. Select the item to which you wish to assign the copied item.
8. Press the [Paste] button.
9. Press [Commit]. If you copied a prompt, model, or kit that has component items, when the prompt, kit, or model is pasted to the tree structure, it will appear that the component items were not copied with it. However, the component items were copied. After you have committed the tree structure, re-query the item and to which you copied the prompt, kit, or model, and the component items will be displayed.
1. On the Model Selector screen, query the model item.
2. Press the [Tree] button.
3. Select the item that you want to copy.
4. Press the [Copy] button.
7. Select the item to which you wish to assign the copied item.
8. Press the [Paste] button.
9. Press [Commit]. If you copied a prompt, model, or kit that has component items, when the prompt, kit, or model is pasted to the tree structure, it will appear that the component items were not copied with it. However, the component items were copied. After you have committed the tree structure, re-query the item and to which you copied the prompt, kit, or model, and the component items will be displayed.
This screen is used to copy the component tree from one model to another model.
1. On the Maintain Models screen, press the [Copy Model Bill] button.
2. In the From Model field, enter the model number from which the bill of material will be copied.
3. In the To Model field, enter the model number to which the bill of material will be copied.
4. Set the Copy Properties flag to the desired setting. When this flag is set to on, any properties assigned to the 'from model' and its components will be copied to the 'to mode'.
5. Set the Copy Model Code Assignment flag to the desired setting. When this flag is set to on, any model codes assigned to the 'from model' and its components will be copied to the 'to model'.
6. Press the [Copy] button.
1. Query the item on the Model Selector screen to which you wish to add routings, and press the [Routing] button.
2. In the Component No field, enter the component item that will be used in the routing, if appropriate.
3. In the Routing Rev field, enter the routing revision level for the model item.
4. In the Effective From and Effective Thru fields, enter the effective dates for the routing.
* The effective from date is the first date the routing will be used. These dates are for reference only.
* The effective thru date is the last date the routing will be used. These dates are for reference only.
5. In the Operation Seq field, enter the operation sequence for the operation that you are assigning to the routing.
6. In the Oper Code field, enter an operation code. You do not have to enter an existing standard operation code in this field.
* If you do enter a standard operation code, many of the following fields will have already been entered from the standard operation record. However, they can still be maintained.
7. Set the Oper Type pop-list to the desired setting. The choices for operation type are Regular, Batch, Unattended, Outside Service, and Indirect.
* Regular operations are performed by direct labor employees, producing one item per cycle.
* Batch operations have items processed in batches, such as a heat treating oven or a washing operation.
* Unattended operations have a machine run without an operator.
* Outside services are purchased from a vendor.
* Indirect operations a performed by indirect employees, such as material handlers.
8. In the Vendor field, enter the vendor for this routing operation if it is an Outside Service operation.
* If no vendor is entered, the vendor will default from item planning in program ICPM, Inventory Planning Data Maintenance, for the component item.
* When modular work orders are released automatically for model items and a requisition is created for the component item, the requisition will be converted to a purchase order automatically when the work order is created if a vendor has been assigned here. Some set up is required. For more information, see Models and Routings.
9. In the Work Center No field and Machine No field, enter the work center and machine number in which this operation is performed.
10. Set the Pay Point pop-list to the desired setting. The choices are Manual, Automatic, and Pay Point.
* Manual indicates that labor is reported manually when the operation is complete.
* Automatic indicated that labor is reported automatically. This happens when the work order or production schedule is received. For work orders, labor will be reported when labor for the next operation defined as paypoint is reported.
* Paypoint indicates that labor for the operation must be reported manually when the operation is complete. However, when labor for a paypoint operation is reported, all labor will be reported for all automatic operations that occurred between this paypoint operation and the previous paypoint operation. Only work orders use paypoint operations.
11. In the Move Time field, enter the average number of days required to move a manufacturing order from this operation.
12. In the Crew field, enter the crew size. This is the number of employees required to run this operation.
13. In the Units per cycle field, enter the units produced per machine cycle. The number you enter here is used in determining the runtime for the operation.
14. In the Operation Description field, enter the operation description.
15. In the Hours fields, enter the amount of time it takes to complete the operation.
* Setup. This is the number of hours it takes to set up this operation.
* Hours per unit. This is the number of hours that it takes to complete one unit. The program will calculate this as the reciprocal of the units per hour field.
* Units per hour. This is the number of units that are completed in one hour. The program will calculate this as the reciprocal of the hours per unit field.
* Indirect hours. This is the number of indirect labor hours it takes to complete the operation.
* Inspect hours. This is the number of inspection labor hours it takes to complete the operation.
* Machine hours. The number of machine hours required to complete this operation.
* Other hours. The number of user-defined hours required to complete this operation
16. In the Rate Codes fields, enter the rate codes for setup, hours per unit, indirect hours, inspect hours, machine hours, and other hours.
17. Press [Commit].
1. Press the [Network] button.
2. Enter the operation sequence numbers on which the operation in the Current field is directly dependent. In other words, the operations you enter here must be completed before the operation in the Current field.
3. Press [Commit].
1. Press the [Tooling] button. This will display the Routing Tool Requirements screen.
2. In the Tool ID field, enter the tool ID from program TLMM, Tool Master Maintenance, that is used in this operation.
* The tool must be authorized for the work center and machine for the operation in order to be entered here.
3. In the Type field, enter labor type code for which the tool will be used.
4. In the # Hits field, enter the number of hits for this tool and this operation.
5. Press [Commit]. The tool is assigned.
Model codes are used to configure models when the model item is entered in sales order entry programs.
1. Press the [Model Codes] button.
2. In the Model Code field, enter the model code.
3. In the Description field, enter the model code description.
4. If this model code is a self-pruning model code, set the Self-Pruning flag to on. For more information, see the Model Self-Pruning section.
5. In the Model No field, enter the model number to which the component to which this model code will be assigned is attached. This should be the model that occurs at the next level up from the component item.
* For example, if you have a model with four prompts, and each prompt has components, and you want to assign a model code to one of the components, enter the prompt model number in the Model No field.
6. In the Component No field, enter the component number to which the model code is assigned. This is the component that this model code will select for this model item.
7. In the Initial Qty field, enter the initial quantity for the component item.
8. Press [Commit].
9. When this model item is entered in a sales order entry program with this model code, the entered component will be selected with the quantity entered here.
* For example, suppose you have entered a model code for a component of a prompt for a quantity of 1. You enter a model to which the prompt is assigned in program OEOE, Sales Order Entry Maintenance followed by the model separator and model code. (PC200-64MB). The component to which the model code is assigned will be selected with the quantity of 1.
1. From the Tree screen, highlight the item to which you wish to add model codes.
2. Press the [Modify] button.
3. Select the Model Codes tab to display the parent model item and component number to which you are assigning model codes.
4. Any model codes currently assigned to this item will be displayed.
5. Press [New Record].
6. In the Model Code field, enter the model code that you are assigning to this item.
7. In the Description field, enter the description for the model code.
8. In the Initial Qty field, enter the quantity of this item that will be selected when this model code is entered on a string configuration for the top level parent model item.
9. The Self-Pruning flag here is display only. If you wish to designate this model code as self-pruning, you must do so from the [Model Codes] button on the Model Selector screen. For more information, see the Entering Model Codes section and the Model Self-Pruning section.
10. Press [Commit].
Default model codes can only be added to prompt items. For more information on default model codes and how they are used, see Default Model Codes.
1. On the Model Selector screen, query the top-level parent model item to which the desired prompt belongs.
2. Press the [Tree] button.
3. Select the desired prompt item.
4. Press the [Modify] button.
5. In the Default Model Code field, enter the desired model code.
6. Press [Commit].
Named properties are assigned to models and components and are used to configure models when the model item is entered in sales order entry programs. Named properties must be defined before they can be assigned to models and components.
1. Press the [Maint Properties] button.
2. In the Property Name field, enter the property name.
3. In the Description field, enter the property description.
4. Set the Numeric flag to the desired setting. If this property will only be assigned numeric values, set the checkbox to on. Otherwise, set the checkbox to off.
5. If the Numeric flag is set to on, in the Min field, enter the minimum numeric value that can be assigned to the property, if appropriate.
6. If the Numeric flag is set to on, in the Max field, enter the maximum numeric value that can be assigned to the property, if appropriate.
7. In the Validation/LOV Query field, you can enter a SQL query that will be used to provide a list of values and generate default entries when assigning the properties to components or setting up property pricing. In addition, the SQL query will be used to validate the property values assigned during string configuration.
* The SQL query entered here must return only two columns, aliased as col_value and col_desc.
* If a Validation/LOV Query is entered at the model level for the property, it will override the query entered here.
* Examples:
select 'CHERRY' COL_value,'CHERRY TOP' col_desc from dual
union
select 'WALNUT' COL_value,'WALNUT TOP' col_desc from DUAL
union
select 'WHITE OAK' col_value,'WHITE OAK TOP' col_desc from dual
select state_prov_ID col_VALUE, state_PROV_desc col_desc from state_prov
select icode1 col_value, description col_desc from item_code1
where product_group = 'MP'
select 2 col_value, '2 panels' col_desc from dual
union
select 4 col_value, '4 panels' col desc from dual
8. Press [Commit].
For each top level model item, enter every property that can be specified for the model in the sting configuration.
1. On the Model Selector screen, press the [Model Properties] button to assign named properties to the queried model.
2. In the Property Name field, enter the property name associated with this model item.
3. Set the Required flag to on if the property is required for the model configuration to be valid.
4. If the model is property priced, enter the price column (1-4) that will be used to designate this property during property price setup with the [Property Pricing] button. Only one property can be designated per price column.
5. In the Validation/LOV Query field, you can enter a SQL query that will be used to provide a list of values and generate default entries when assigning the properties to components or setting up property pricing. In addition, the SQL query will be used to validate the property values assigned during string configuration.
* The SQL query entered here must return only two columns, aliased as col_value and col_desc.
* The Validation/LOV Query entered here will override the default query defined for the property on the Maintain Properties screen.
* Examples:
select 'CHERRY' COL_value,'CHERRY TOP' col_desc from dual
union
select 'WALNUT' COL_value,'WALNUT TOP' col_desc from DUAL
union
select 'WHITE OAK' col_value,'WHITE OAK TOP' col_desc from dual
select state_prov_ID col_VALUE, state_PROV_desc col_desc from state_prov
select icode1 col_value, description col_desc from item_code1
where product_group = 'MP'
select 2 col_value, '2 panels' col_desc from dual
union
select 4 col_value, '4 panels' col desc from dual
5. In the Default Value field, you can enter the default value for this property, if you are not using the Default Value Query for the property's default value. If a default value is provided and no property is entered in the configuration string, the default value will be used.
* If a validation query is provided, the default value will be validated by the Validation/LOV Query.
6. In the Default Value Query field, you can enter a query that will derive the default value for this property during string configuration, if no property is entered and you are not using the Default Value field for the property's default value.
* The query can reference other property values in the configuration by using the referenced property's name in carats - ^PROPERTY_NAME^.
For example, suppose that you have properties named LENGTH, WIDTH, and AREA. The default value of the AREA property is the value of the LENGTH property * the value of the WIDTH property.
The default value query might be: SELECT round (^LENGTH^ * ^WIDTH^) FROM DUAL.
* Any properties that are referenced by default query of another property should not default from a query as there is no attempt made to determine the order in which the default values from queries are calculated. Referenced properties should either have a default value in the Default Value field, or must have the value entered in the configuration string.
* If a validation query is provided, the default value will be validated by the Validation/LOV Query.
7. Press [Commit].
When entering properties for component items, only assign those properties directly related to the component item or the initial quantity for the component items. Only one property can be used to define the initial quantity for a component item.
1. On the Navigator screen, highlight the item to which you wish to assign named properties.
2. Press the [Modify] button.
3. Click on the Properties tab.
4. Any named properties currently assigned to this item will be displayed.
6. In the Property Name field, enter the named property that you are assigning to this item.
7. In the Value field, enter the value that is associated with this component and property.
8. In the Initial Qty field, enter the quantity of this item that will be selected when this named property and value is entered on a string configuration for the top level parent model item.
9. Press [Commit].
10. You can use the [Populate from LOV Query] button to enter records here for all values for a property name.
* This is useful in cases where the property value is being used to supply initial quantity values rather than selection criteria or when setting up components which must be excluded on an exception basis.
* In the Property Name field, enter the desired property name.
* In the Value field, enter a dummy value.
* Press the [Populate from LOV Query] button.
* Rows will be generated for each property value returned by the LOV query.
On the Model Selector screen, query the model for which you are setting up property based pricing.
There are four value columns in the price matrix. Those columns which have properties assigned to them will show the property description as a heading for the column. Above these headings are fields which allow entry of filter criteria to query a specific group of records. Leaving a filter field blank will cause all values for that column to be queried.
A wildcard token value of '****' is used to designate cases where any value is appropriate and appears in all columns with no property assigned. The wildcards have a lower priority than entries for specific values, so any match on a specific value will take precedence over a wildcard entry.
1. Press the [Property Pricing] button.
2. In each column, enter the property value for which the price is valid. Combinations of values can be defined.
3. When all value combinations and prices have been entered, press [Commit].
4. You can generate the values for the pricing matrix based on the price columns assigned to the properties on the Model Properties screen if an LOV Query was defined.
* Place your cursor in the first column on the screen.
* Press the [Generate Values from LOV Query] button.
* A record will be created for each value defined in the LOV Query.
* Repeat for each additional column for that is assigned to a price column.
* Delete any unwanted generated rows.
* In the Unit Price field, enter the unit price for the combination of property values.
* Press [Commit].
Assume that there are two properties used to price a model. The property assigned to the first column can have possible values of (A,B,C), the second can have values of (X,Y,Z). Place cursor in first column, press button. This results in :
**** **** **** **** 0
A **** **** **** 0
B **** **** **** 0
C **** **** **** 0
Now place the cursor in the second column, press button again, this results in :
**** **** **** **** 0
A **** **** **** 0
A X **** **** 0
A Y **** **** 0
A Z **** **** 0
B **** **** **** 0
B X **** **** 0
B Y **** **** 0
B Z **** **** 0
C **** **** **** 0
C A **** **** 0
...etc
Press this button to attach the component item to the model item in the modular bill tree.
Press this button to view and maintain the provided and consumed attributes for this item.
Press this button to view and maintain the provided and consumed attributes for this item.
Press this button to collapse one level of items and prompts below the selected item or prompt so that only the selected item or prompt is showing.
Press this button to collapse all levels of items and prompts below the selected item or prompt so that only the selected item or prompt is displayed.
Press this button to copy the information for the selected item and move the copied information to a temporary file.
Press this button on the Copy Model Bill screen to copy the component tree from the 'from model' to the 'to model'.
Press this button to add a new item or prompt to the selected location in the modular bill.
Press this button to remove the selected item from its current position and move it to a temporary file.
Press this button to delete an item or prompt from the modular bill. This does not delete the item or prompt from the system; the item or prompt is just removed from the modular bill.
Press this button to display the items and prompts that are one level below the selected item or prompt.
Press this button to display all levels of items and prompts below the selected item or prompt.
Press this button to generate the price matrix according to the values assigned to the property for the selected column.
Press this button to move down one page in the Navigator screen.
Press this button to move up one page in the Navigator screen.
Press this button to define and maintain named properties. You must define the properties before they can be assigned to models and component items.
Press this button to maintain the attributes that can be used by any of the items. No matter what item is displayed, the attributes viewed and entered here can be assigned to any of the items.
Press this button to maintain the information for model items, including the model type, stock unit of measure, routing revision level, price method, and whether the item is a serial controlled item.
Press this button to make the engineering change level and routing revision level for the displayed item the current engineering change level and routing revision level. The engineering change level (ECL) is the revision level for the bill of material. Each level value indicates the number of modifications made to the bill. The routing revision level is a user-defined code denoting the version of the routing. It combines with the item number to form a unique key.
Press this button to enter and assign model codes to model component items.
On the Modular Bill Items screen, press this button to assign a model code to the selected item.
Press this button to assign named properties to the queried model item.
Press this button to change the item or prompt information on the selected item or prompt. The Modular Bill Items screen is displayed when this button is pressed.
Press this button to enter the operation sequences that must be completed before this one can be started.
Press this button to paste the information from the temporary file to the selected location in the modular bill.
Press this button to populate the properties tab for the values in the LOV query assigned to the entered property on either the Maintain Properties screen or the Model Properties screen.
Press this button to define the price matrix for property priced model items.
Press this button to re-query the price matrix after having changed the Query Filters.
Press this button to undo the last change you made to the modular bill. Only the last change will be undone, and you cannot undo a reversion.
Press this button to enter or maintain the routing for the displayed item.
Press this button to commit the modular bill.
Press this button to search backward in the modular bill for the information in the find box.
Press this button to search forward in the modular bill for the information in the find box.
Press this button to enter the tools that are used in the process of completing this operation.
Press this button to display the modular bill tree for the selected item.