You can assign or release member ownership automatically or explicitly using commands. You specify how CA‑PanAPT performs the assignment or release when you set up the Library Code. Assignment can be enabled (required) or not.
When Assignment is automatic, an unassigned member is assigned to the user who adds it to a Move Request.
When Assignment is required, but not automatic, you must manually assign the member. This is done from Move Request Maintenance or Inventory File Maintenance.
The assigned user of a member can release control of a member or can transfer control to another CA‑PanAPT user. When a member is released, it is available for assignment to any other CA‑PanAPT user and Move Request. When the assignment of a member is transferred, you can transfer it to another user, another Move Request, or both.
You can implement CA‑PanAPT to release assigned members for Library Codes automatically. When release is automatic, the member is released or reassigned when its Move Request is moved to its final destination. The final destination is either the highest move level used by all of the Library Codes of the Move Request, or the early stop level if specified. The Move Request that a member is assigned to can change when the member is deleted from a Move Request, or when the Move Request is moved to its final destination, regardless of whether or not Automatic Release is enabled. However, Assignment to the user is changed or released only if Automatic Release is enabled.
During the automatic reassign that takes place when a Move Request is moved to its final destination, you can optionally have CA‑PanAPT set a concurrent development flag for all other instances of the reassigned members on other Move Requests. This serves to document that a concurrent change to a member has been moved, and that its changes should be accounted for in the new version of the member before the Move Request is closed. Move Requests cannot be moved or closed until all of their concurrent development flags have been manually reset.
You can also use a separate CA‑PanAPT function to release ownership. When release is not automatic, you must explicitly release a member before it can be assigned to someone else.
When you close a Move Request or verify a Move Request for closing, CA‑PanAPT checks each member for Proper Assignment. A site defines Proper Assignment by selecting a Close Assignment option (CLO) on the Control File Maintenance/System Information panels and by selecting a relationship to be tested for the MOVEREQ/CLOASSGN activity under the Control File Maintenance/Activity panels.
You can also require that inventory is assigned to a Move Request in order to close and move the Move Request. This is defined by selecting an appropriate Move Req Assignment Option on the Control File Maintenance/System Information panels.
|
Copyright © 2004 CA.
All rights reserved.
|
|