For all object entries, e.g. UNSAccountB, you can set a connection variable, e.g. "Fullsync", and then check for the variable in the generation condition of any processes on the given table. This does however not work for *total tables: E.g. when you create an entry in UNSAccountBInUNSGroupB, DBScheduler will create the related UNSAccountBInUNSGroupBTotal entry, and any INSERT/UPDATE events would then happen in a different connection, which is why the variable cannot be checked.
This is no different for the components that ship with D1IM, when they have to create any M:N relations, they first handle the related *Total entry through the object layer, then the M:N entry. In that case, DBScheduler doesn't need to adjust the *Total entry and does not fire a new event on the *Total table on its own. Using the object layer has the advantage of adding a related PersonHasObject entry and the XObjectKey per tempate.
As a solution to a custom sync on UNS*B, you can adopt this behaviour. Please note, any scripts implementing this could be difficult to test because "viadmin" does not have insert/edit/delete permissions on *Total tables. The jobservice uses the default system user though and can perform the operations.
Please note this only affects the product up to the 6.1 line.