Global Work Definitions
Work definitions are defined at the maintenance organization level, as they are based on organization specific work areas, work centers, material items, and resources. If you have definitions that have the same work scope across some or all your maintenance organizations, then you can create and manage them globally.
Global work definitions are supported only in the Redwood enabled Work Definitions page
and are defined in a maintenance-enabled master organization. Once created, they are
replicated to the selected child maintenance-enabled organizations. This provides the
ability to source control them, while maintaining revisions and new versions globally,
instead of at each local organization. This reduces the work of creating and managing
these common definitions across your maintenance organizations.
Note: Existing work definitions at child organizations can’t be
managed globally. You must create new definitions in the maintenance-enabled master
organization, then replicate to the child organizations.
Enable the master organization for maintenance and ensure users have the
WIS_PROPAGATE_GLOBAL_WORK_DEFINITIONS_PRIV privilege to view
and manage the list of child organizations across which the global definition are
replicated.
Important: You must ensure that the
name of the work definition in the global master organization doesn’t exist in any
child organizations, else the replication will fail for that
organization.
Global definitions still require the unique definition of child objects across each child
maintenance organization as a pre-requisite, as these objects are not managed globally.
This includes:
- Work areas
- Work centers
- Resources
- Items
- Standard operations
Remember: It's recommended to have a common naming
strategy of these objects, making setup consistent across organizations. Otherwise, they
won't replicate from the global definition to each child organization and will error
out.
After maintenance organization replicates are created, you can view and verify them in
each child organization. You can locally define and manage these fields in the child
replicas:
- Allow out-of-sequence completion checkbox
- Allow return to inventory checkbox
- Completion sub inventory and locator
- Supply sub inventory and locator
- Supplier and supplier site for supplier operations
After a child organization replicate is created, the organization can’t be removed from
the assigned list of child organizations. You can optionally choose to disconnect the
replicate and manage the local copy, including deactivating or even deleting it, per the
existing validations. Additionally, you can disconnect the replicate if you want to
manage the local copy if the work steps are fundamentally different.
Caution: Care should be taken when disconnecting a
replicated work definition, as this can’t be reversed. Only users with a specific
privilege WIS_UNLINK_REFERENCED_WORK_DEFINITION can disconnect them.