Zeitbeschränkungsverknüpfungen: Unterschied zwischen den Versionen
GK (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „{{DISPLAYTITLE:Zeitbeschränkungsverknüpfungen}} <div align="right">Hilfe Nummer: 742160</div> <hr> Durch Verknüpfungen mit dem [Typ] "Zeitbeschränkung" is…“) |
(kein Unterschied)
|
Version vom 4. März 2019, 20:33 Uhr
Durch Verknüpfungen mit dem [Typ] "Zeitbeschränkung" ist es Ihnen möglich, frei Beziehungen zwischen Aufträgen oder Vorgängen anzulegen, ohne die Integrierten Stammdaten anzupassen.
Verknüpfungen mit Typ Zeitbeschränkung
Verknüpfungen mit diesem Typ haben die folgenden Eigenschaften:
- Verknüpfte Vorgänge werden zugewiesen, als ob die [Zeitbeschränkungsart] "ES" und die [Zeitbeschränkung MIN] "0s" wären.
- Artikel und Menge werden nicht beachtet. Unter dem Vorgang oder der Aufgabe werden automatisch Output- und Input-Anweisungen erstellt, für die [Artikel] und [Menge] nicht gesetzt sind, und verknüpft.
Sie können diese Verknüpfungen können auf zwei Wegen erstellen:
- Durch Setzen der Auftragseigenschaft [Nächste Aufträge].
- Durch Ziehen von Verknüpfungen in Gantt-Diagrammen
When you create a pegged object by specifying it in the [Next orders] property, a pegged object is created for the specified object each time the order is exploded. When you create a pegged object with the peg editing feature of the Gantt chart, the [Fixed flag] property of the pegged object is automatically set to [TRUE], and the pegged object is maintained as long as it is [TRUE]. If the [Fixed flag] property of the pegged object is set to [FALSE], that object will be deleted the next time the order is exploded.
If you set the [Fixed flag] property of a pegged object to [TRUE], even if the [Next orders] property is then deleted, the pegged object created with the [Next orders]" property will be maintained the next time the order is exploded. Pegged objects are the same as those created with the peg editing feature of the Gantt chart.
Verknüpfbare Objekte
| Zu verknüpfendes Objekt |
Beschreibung | Definition in Nächste Aufträge |
|---|---|---|
| Vorgang | A pegged object is created for the operation. When assigned, it moves to the task.1 | ✔ |
| Produktionsaufgabe | A pegged object is created for the Production task. When unassigned, it moves to the operation. | ❌ |
| Rüstaufgabe | A pegged object is created for the setup task. When unassigned, it moves to the operation. When assigned again, it moves to the setup task, but if there is no setup task, it moves to the production task. When a setup task occurs again, it moves to the setup task. | ❌ |
| Abrüstaufgabe | A pegged object is created for the teardown task. The basic specification is the same as the setup task. | ❌ |
| Ressourcensperraufgabe | Pegging is not possible. | ❌ |
| Auftrag | If you specify an order on the previous process side of pegging, the pegged object will be created for all the last process operations, and if you specify an order on the next process side, a pegged object will be created for all the first process operations. A pegged object will also be created for last process operations and first process operations created at the time of order explosion.
In other words, you will be able to get the same result as when you set up an order with the [Next orders] property. |
✔ |
| Ursprung geteilter Vorgänge | A pegged object is created for all split child operations. When unassigned, it moves to the split root operation. Pegged objects are created even for newly created split child operations, regardless of whether static splitting or dynamic splitting was used. In other words, you will be able to get the same result as when you set up an order with the [Next orders] property. | ✔ |
| Teillos | A pegged object is created for the split child operation itself. It will not move to other split child operations or split root operations. | ✔ |
| Vorgangsgruppe | A pegged object is created for all operation group members. Also, a pegged object is created for the operation group itself.
A pegged object is also created for operation group members newly added with the Group operations command. |
❌ |
| 1 If the above objects have a task in a child object, the output instruction and input instruction will move to the production task at the time of assignment and move to the operation at the time of unassignment. However, if the pegged object is a setup task or a teardown task, the task index is automatically recorded in the "destination task index" of the output instruction or input instruction , and it moves to that task at the time of assignment. If the task does not exist at the time of assignment, it moves to the production task. | ||
Orders too can be selected as the addition destination for pegged objects by the peg editing feature. However, whether pegging can be done in front or in back with the pegging edit feature depends on the type of order.
| Auftragstyp | Bedingung | Verknüpfungsposition | |
|---|---|---|---|
| Vorher | Nachher | ||
| Fertigungsauftrag | ✔ | ✔ | |
| Bestand (Fluktuation) | [Menge] >= 0 | ❌ | ✔ |
| [Menge] < 0 | ✔ | ❌ | |
| Bestand (absolut) | ❌ | ✔ | |
| Bestand (geplant) | ❌ | ❌ | |
| Verkaufsauftrag | ❌ | ✔ | |
| Einkaufsauftrag | APS | ✔ | ❌ |
| SCP | ✔ | ✔ | |
| Ereignisauftrag | ❌ | ❌ | |
| Auftragsgruppe | ❌ | ❌ | |
