When you write a trigger or procedure, PowerDesigner automatically creates dependencies to any table, view, procedure, or database package referenced in the code. These dependencies are taken into account when performing an impact analysis prior to deleting the trigger or procedure or objects on which they depend. For procedures, if the procedure has a symbol in your diagram, then any dependencies will be shown graphically by way of arrows linking the procedure to these objects.
The diagram below shows a procedure, ProcChangeLocation, which is dependent on a number of other objects:
Its Traceability Links tab lists the objects upon which it depends, and the link type of DBCreateAfter (computed) shows that PowerDesigner has determined that it can only be created after these objects:
The Employee table Dependencies tab shows that ProcChangeLocation is dependent upon it, and if you were to perform an impact analysis prior to deleting the Employee table, you would be warned of the procedure's dependency on it.
