There are several activities that involve Move Requests. These are:
An authorized CA‑PanAPT user adds the initial Move Request, filling in the CA‑PanAPT panels with appropriate data. The initial status of a new Move Request is Being Created.
A Move Request can also be added by running the CA‑PanAPT Batch Add-Move-Request job. This procedure reads a file containing Move Request descriptions and member data records, creates a Move Request, and adds the Move Request to the Pending File. See the "Batch Interface" chapter in the Adminstrator Guide for proc APJP5960.
The authorized user modifies a current Move Request, reviewing and modifying current data.
Normally, Move Requests are Updated while they are in the Being Created (CRE) status. Only authorized users (through the CHGAWAPP activity record) or the CA‑PanAPT System Administrator are able to do an update against a Move Request that is awaiting approval.
If the Move Request is ready to be moved (no approvals or verifications are outstanding), then no one can change the Move Request. Before you change the Move Request data, change the status of the Move Request to Being Created.
Doing a CA‑PanAPT Update (CHG function) against a Move Request results in CA‑PanAPT revoking all Approvals that have already been granted. In addition, all Verifications are reset.
An authorized user closes the Move Request by using the CA‑PanAPT CLOSE function. The Move Request data and contents are now considered to be complete, and the Move Request is now ready to be Approved.
At close time, CA‑PanAPT verifies that the requirements, specified (during Library Code Maintenance processing) in the Library Code definitions, are met. If the Library Code requires it, CA‑PanAPT verifies that members are properly assigned, that approved Inventory Records exist, and that the members are acceptable to the Member Existence Exit.
Any Verifications required by the Library Code at the starting level must have already been run successfully for the Move Request. If any starting level Verification requirements remain outstanding, the Move Request is not closed. Instead, the Move Request Verification Selection panel displays, allowing you to choose Verifications to be submitted.
Users authorized to perform the necessary approvals use the APP function to log the approvals for each Move Request. If the need should arise, the authorized users can use the APP function to revoke approvals or disapprove a Move Request
When the Move Request has Verification Procedure requirements, you must run the appropriate procedures to successful completion. The actual verification procedure posts the necessary Verification Category indicating success or failure.
You can initiate Verification Procedure processing for a Move Request from the following panels:
CA‑PanAPT provides a separate function for changing the Move Request Next Move Date, Final Move Date, and First Run Date. The DAT function allows the authorized user to update these dates without changing the current status of the Move Request.
The authorized user can request a printout of a single Move Request by using the CA‑PanAPT PRT function.
The authorized user can use the CA‑PanAPT DEL function to flag a Move Request as DELETED. The Move Request remains on the Pending File, but is no longer included in pending reports or in other current processes.
Move Requests are physically removed from the Pending File by the batch purge job, APJJ5950. See File Maintenance Jobs in the "Batch Component"chapter for more information on purging Move Requests from the Pending file.
The Move Request Browse function (BRO) lets you build an online list of Move Requests according to criteria that you specify.
You can browse this list and select a particular Move Request for additional processing by typing the desired CA‑PanAPT function on the line showing the desired Move Request.
Using the Move Request Browse function (BRO) and selecting the status codes for Moves in progress, you can monitor the progress of the current move cycle.
You can browse this list and select a particular Move Request to determine the status of any member that is part of this request.
The Move Request Copy function (COP) creates a new Move Request based on an existing Move Request. You can change the attributes, dates, and member list, as part of the copy process.
As part of final processing, CA‑PanAPT attempts to Assign, Retrieve, and Verify the existence of the members as specified in the Library Code definitions.
This action lets you copy members for rework from a Move Request that is somewhere in the migration path. You need to select the Move Request or Change Name that has a problem. You are presented with an MSL of members. You can then select the member(s) that need to be changed.
A new Move Request is automatically assigned and the Change Name defaults to REWORK FOR NNNNNN. NNNNNN is the Move Request that you copied from.
The Rework Move Request number has a STOP LEVEL equal to the Level you copied from. When the Rework Move Request reaches the Stop Level it is marked as done.
Reassign/Release processing works different for a rework Move Request than others. It always attempts to reassign members back to the original Move Request before considering any other Move Requests.
The Move Request function Back Out (BAK) prepares an existing Move Request that is in the status MOVE COMPLETE, AWAITING APPROVALS, or APPROVED to Back Out by replacing members from the libraries they were last moved to with the corresponding members from the Backup libraries. Different Backup libraries are used for each Move phase or level (such as quality assurance or production).
|
Copyright © 2004 CA.
All rights reserved.
|
|