Beispiel U-2: Unterschied zwischen den Versionen
GK (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „{{DISPLAYTITLE:Beispiel U-2: Nacharbeitsaufträge über benutzerdefinierte Objekteigenschaft anlegen}} <div align="right">Hilfe Nummer: 928000</div> <div align…“) |
GK (Diskussion | Beiträge) (→Übersicht) |
||
| Zeile 5: | Zeile 5: | ||
== Übersicht == | == Übersicht == | ||
| + | This sample is sample data for learning the automatic object generation function applying the additional functions of object type user properties added in Ver.15.2. | ||
| + | For the basics of object type user properties, refer to sample U-1. | ||
| + | == Automatic generation of objects == | ||
| + | If you select the "Auto generate object” check box in the dialog for creating object type user properties, the object will be automatically generated if the object corresponding to the specified code cannot be found. | ||
| + | In this sample, we will apply this function to create a rework order, peg it, and assign it. | ||
| + | |||
| + | == What is a rework? == | ||
| + | |||
| + | Rework is work done to carry out a repair process or redo some process when a defective product is output. | ||
| + | It is possible to prepare rework processes in advance in the integrated master, but this is not easy if you cannot determine when rework will occur. | ||
| + | In this sample data, the work immediately after which a rework process is to be generated is arbitrarily selected on the Gantt chart, etc., and the rework order is generated to send the work to the repair center and returned after 12 hours of repair. | ||
| + | |||
| + | == Let's generate a rework process == | ||
| + | |||
| + | This data covers two orders consisting of three steps. | ||
| + | |||
| + | |||
| + | |||
| + | Select [Execute command]-[SAMPLE_Generate_Rework] from the right-click menu of any use instruction. | ||
| + | |||
| + | |||
| + | |||
| + | Then, the rework process was added immediately after the selected process. | ||
| + | This means that a rework order has been generated, pegged between the 10th and 20th processes, and assigned to the repair center resources. The connecting line in light blue indicates that it is tied by "Next order" (Order_NextLotV9). | ||
| + | |||
| + | Executing the scheduling parameter "SAMPLE_Delete_Rework" deletes the settings for rework orders and the next orders. | ||
| + | |||
| + | == Let’s check the settings == | ||
| + | |||
| + | The order table before and after rework order generation is as follows. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | Rework order properties are object type user properties. The addition method is as follows. | ||
| + | First, in the order table, launch the Add New Property dialog from the Column Settings dialog. | ||
| + | |||
| + | Enter the following: Even if you forget to select the "Auto generate object” check box, you can change this later using the "Auto generate object" (IsAutoGenerate) property of the property definition. | ||
| + | |||
| + | |||
| + | |||
| + | Next, in the Integrated Master, create the integrated master of the rework item. Here, 12 hours are assigned to the repair center. | ||
| + | |||
| + | |||
| + | |||
| + | Next, make the settings in the scheduling parameter table. Here, using the command execution function, we call the scheduling parameter from the right-click menu. | ||
| + | When "Parameter type" (Command_ParameterType) is set to "Sequencing", it will be displayed in the right-click menu. | ||
| + | |||
| + | |||
| + | |||
| + | This scheduling parameter sets three commands. | ||
| + | The Upload selected operations command, per its name, uploads the operations selected with the GUI. | ||
| + | In the Modify properties command, the following five expressions are set in "Operation expression" (Command_ExpressionExecutor_OperationExpr). | ||
| + | |||
| + | # <code>ME.Order.ReworkOrder=ME.Order.Code+'_RW'</code> | ||
| + | # <code>ME.Order.ReworkOrder.Item='rework item’</code> | ||
| + | # <code>ME.Order.NextLotV9=ME.Code+',,'+ME.Order.ReworkOrder+',,'</code> | ||
| + | # <code>IF(Exist(ME.NextOperation),ME.Order.ReworkOrder.NextLotV9=ME.Order+',,'+Format( ME.OperationProcNo+10,'0'),FALSE)</code> | ||
| + | # <code>ME.Order.ReworkOrder.Qty=ME.Order.Qty</code> | ||
| + | |||
| + | In 1, the rework order is generated automatically by specifying as the rework order property an order code that does not exist in the order table. It is not generated if it already exists. | ||
| + | In 2, rework items are set so that rework orders use the previously mentioned Integrated Master. | ||
| + | In 3, the next order property is set to generate pegging from the selected order to the rework order. | ||
| + | In 4, to generate a peg that returns from the rework order to the selected order, the next order property is also set for the rework order. In the case of the final process, nothing is set. | ||
| + | In 5, the same quantity as the order selected for the rework order is set. In the production column of the Integrated Master, this has no particular meaning because the value of 12 hours is set regardless of the production quantity. | ||
| + | |||
| + | Lastly, for the Reference execution command, the order is exploded and scheduling parameter FW scheduling, which simply makes forward assignments, is called. | ||
| + | |||
| + | Note that with this setting, only one rework order can be generated from one order, so multiple rework steps cannot be generated. In the case of multiple processes, this can be achieved by, for example, presenting the Integrated Master of the rework item in multiple processes. | ||
<hr> | <hr> | ||
<div align="right">Hilfe Nummer: 928000</div> | <div align="right">Hilfe Nummer: 928000</div> | ||
Version vom 4. September 2019, 13:12 Uhr
Inhaltsverzeichnis
Übersicht
This sample is sample data for learning the automatic object generation function applying the additional functions of object type user properties added in Ver.15.2. For the basics of object type user properties, refer to sample U-1.
Automatic generation of objects
If you select the "Auto generate object” check box in the dialog for creating object type user properties, the object will be automatically generated if the object corresponding to the specified code cannot be found. In this sample, we will apply this function to create a rework order, peg it, and assign it.
What is a rework?
Rework is work done to carry out a repair process or redo some process when a defective product is output. It is possible to prepare rework processes in advance in the integrated master, but this is not easy if you cannot determine when rework will occur. In this sample data, the work immediately after which a rework process is to be generated is arbitrarily selected on the Gantt chart, etc., and the rework order is generated to send the work to the repair center and returned after 12 hours of repair.
Let's generate a rework process
This data covers two orders consisting of three steps.
Select [Execute command]-[SAMPLE_Generate_Rework] from the right-click menu of any use instruction.
Then, the rework process was added immediately after the selected process. This means that a rework order has been generated, pegged between the 10th and 20th processes, and assigned to the repair center resources. The connecting line in light blue indicates that it is tied by "Next order" (Order_NextLotV9).
Executing the scheduling parameter "SAMPLE_Delete_Rework" deletes the settings for rework orders and the next orders.
Let’s check the settings
The order table before and after rework order generation is as follows.
Rework order properties are object type user properties. The addition method is as follows. First, in the order table, launch the Add New Property dialog from the Column Settings dialog.
Enter the following: Even if you forget to select the "Auto generate object” check box, you can change this later using the "Auto generate object" (IsAutoGenerate) property of the property definition.
Next, in the Integrated Master, create the integrated master of the rework item. Here, 12 hours are assigned to the repair center.
Next, make the settings in the scheduling parameter table. Here, using the command execution function, we call the scheduling parameter from the right-click menu. When "Parameter type" (Command_ParameterType) is set to "Sequencing", it will be displayed in the right-click menu.
This scheduling parameter sets three commands. The Upload selected operations command, per its name, uploads the operations selected with the GUI. In the Modify properties command, the following five expressions are set in "Operation expression" (Command_ExpressionExecutor_OperationExpr).
-
ME.Order.ReworkOrder=ME.Order.Code+'_RW' -
ME.Order.ReworkOrder.Item='rework item’ -
ME.Order.NextLotV9=ME.Code+',,'+ME.Order.ReworkOrder+',,' -
IF(Exist(ME.NextOperation),ME.Order.ReworkOrder.NextLotV9=ME.Order+',,'+Format( ME.OperationProcNo+10,'0'),FALSE) -
ME.Order.ReworkOrder.Qty=ME.Order.Qty
In 1, the rework order is generated automatically by specifying as the rework order property an order code that does not exist in the order table. It is not generated if it already exists. In 2, rework items are set so that rework orders use the previously mentioned Integrated Master. In 3, the next order property is set to generate pegging from the selected order to the rework order. In 4, to generate a peg that returns from the rework order to the selected order, the next order property is also set for the rework order. In the case of the final process, nothing is set. In 5, the same quantity as the order selected for the rework order is set. In the production column of the Integrated Master, this has no particular meaning because the value of 12 hours is set regardless of the production quantity.
Lastly, for the Reference execution command, the order is exploded and scheduling parameter FW scheduling, which simply makes forward assignments, is called.
Note that with this setting, only one rework order can be generated from one order, so multiple rework steps cannot be generated. In the case of multiple processes, this can be achieved by, for example, presenting the Integrated Master of the rework item in multiple processes.