Delete object

Delete object command can be used to delete the unnecessary old messages in the message box, or delete the old orders in order table easily. (Ver.10 restricted feature.)

There are properties as follows in "delete object" command object.

 Table->Specify a table name.
 Object filter expression->Specify a filter expression to filter the object.

It can be used to delete the filtered objects in specified table.

If the "Object filter expression" of an object returns TRUE, then it will delete the object.

More than one "table" and "Object filter expression" can be specified. In this case, it can delete many objects in different tables once time.

* When there are more than one "table" and "Object filter expression", the index of "table" must match with the index of "Object filter expression". Or else it may delete inaccurate object.

Sample1 - Delete message

Please add an delete object command with followed settings to an scheduling command.

 Object filter expression->TRUE

Sample2 - Delete orders which are completed and the due date are before "Scheduling basis time".

Please add an delete object command with followed settings to an scheduling command.

 Object filter expression->ME.Status=='B'&&ME.LET<PROJECT.BasisTime

In addition, it can be used to delete the operation input instructions on specific resource, then the operation input instructions can be switched to other items. * After this operation was assigned, the "Explode orders" command is necessary to auto replenish related input instructions.

The object which can be deleted

If one object is deleted, the child object of this object will be deleted too.
For example, if one order is deleted, the operations of this order are deleted too.
If one item is deleted, the master operation of this item are deleted too.

For more information on the deleted objects, please look at <13>the list in Command_DeleteObject_TableID here</13>.

OperationIf one parent operation are splitted into many child operations, then one child operation can not be deleted separately, the parent operation is deleted too. Split root operations can be deleted along with child operations.
Operation groups are also included.
In addition, if one operation is deleted, the setup task, production task, teardown task, resource lock task, input instruction, use instruction, output instruction are deleted too.
PegObject whose type is "Within same order" cannot be deleted.
ItemChild objects (in other words, Integrated Master of master operation, master input instruction, master output instruction, master use instruction objects) are deleted too.
If “Unassign operations with deleted master data” in the project settings is set to “Yes”, the operations which use the master data of this item are unassigned automatically.


1. When an order or operation is deleted, it may be generated automatically after rescheduling.
If you do not want to generate the deleted object automatically, please exclude the object from "Explode orders" objects by filter expression in scheduling parameters dialog.

2. When delete the message, the message generated before the time when running delete object command can be the candidate objects. So the message after running delete object command cannot be deleted.

© Since 2019 Asprova Corporation, All rights reserved.