Display only. This field displays the action that you entered on the previous panel.
Optional. Length: 1‑4. Type: alphanumeric.
This field identifies the system. For example, you can have multiple separate CA‑PanAPT systems in use at your site. A System Identifier of SYSA could identify one system and SYSB could identify the other. The System Identifier appears on all CA‑PanAPT reports.
Optional. Length: 1‑40. Type: alphanumeric.
Type information or leave blank. Type up to 40 characters for your company name as you expect it to appear on all reports. Whatever you enter here, appears on the second line of the CA‑PanAPT reports.
Required. Length: 1. Type: numeric. Valid values: 1, 2, or 3.
Select one of the following date format options:
Present all dates in MM/DD/YY format.
Present all dates in DD/MM/YY format.
Present all dates in YY/MM/DD format.
Required. Length: 1. Type: character.
Type the date separator option. For example, if you specify a period . to separate the month, day, and year in Date Format 1, the dates appear as MM.DD.YY.
Required. Length: 1. Type: character.
Type the time separator option. For example, if you specify a period (.) to separate the hours, minutes, and seconds, the time appears as HH.MM.SS.
Optional. Lib Code Length: 1‑4. Sub Code Length: 1‑3. Type: alphanumeric.
These ten fields represent the defaults that you establish. The values you enter here appear later, when you add a member to the Member Moves panel.
You can enter values in any part of the Library Code/Sub Code fields. For example, you can specify values in both the Library Code and the Sub Code, just in the Library Code fields, or just in the Sub Code fields. You can place a value in any field (such as in Library Codes 1, 4, and 9).
If you enter Power Input while adding, changing, or copying a Move Request, these codes are displayed as defaults on the first panel after entering Y for Power Input. Use of these Library Codes is discussed in the "Move Requests" chapter.
The values shown are the default values distributed with the CA‑PanAPT system. These default Library Codes appear on the Member Moves panel. A site should specify these defaults to minimize typing by users entering Move Request data. The Library Code values for several (or all) of the default codes can be the same or they can all be different. You can blank out Library Code entries if you choose not to use them.
The default values for the CA‑PanAPT system are shown on the batch job APJJ5103, which reports on the information contained on the CA‑PanAPT Control File. The APCS5103‑01 report provides a listing of the default values. A sample of that report is in Appendix A, "Forms."
Required. Length: 1. Type: alphabetic. Valid values: Y (Yes) or N (No):
All CA‑PanAPT users must enter an expanded description during Move Request creation.
All CA‑PanAPT users do not need to enter an expanded description during Move Request creation, but an expanded description is accepted.
Required. Length: 1. Type: alphabetic. Valid values: Y (Yes) or N (No):
All CA‑PanAPT users must enter a comment when approving an approval category.
All CA‑PanAPT users do not need to enter a comment when approving an approval category, but a comment is accepted.
Required. Length: 1. Type: alphabetic. Valid values: Y (Yes) or N (No):
All CA‑PanAPT users must enter a comment when disapproving an approval category.
All CA‑PanAPT users do not need to enter a comment when disapproving an approval category, but a comment is accepted.
Required. Length: 1. Type: alphabetic. Valid values: Y (Yes) or N (No):
The Service Request field in Move Requests can contain the characters ? and *. The Service Request selection criteria in the Move Request Browse facility is used as an exact match instead of a wildcard expression.
The Service Request field in Move Requests cannot contain the characters ? and *. This allows wildcard expressions to be used in the Service Request selection criteria in the Move Request Browse facility. That is, the * and ? characters in the selection criteria are treated as wildcard characters.
Required. Length: 1. Type: numeric. Valid values: 1, 2, or 3:
When a Move Request is closed, each member is properly assigned if it is assigned to any user. The test fails only if the member is not assigned to anyone. (This is the value set when CA‑PanAPT is installed.)
The test in the MOVEREQ/CLOASSGN activity uses the user IDs of the Owner of the Move Request and the user to whom the member is assigned.
For example, if the MOVEREQ/CLOASSGN activity authorization specifies Users sharing group? as Y and all other fields are N, the Owner of the Move Request and the user to whom the member is assigned must have a group in common between their CA‑PanAPT user ID specifications. (This is true if they are both using the *DEFAULT User ID, that is, if their user IDs are not defined explicitly to CA‑PanAPT, and *DEFAULT specifies a group.)
As a second example, assume that the MOVEREQ/CLOASSGN activity authorization specifies only Owner as Y and all other options are specified as N. The user who has the member assigned must be the Owner of the Move Request. This means that the proper assignment test fails if any member is unassigned or is assigned to any user other than the Owner of the Move Request.
The test in the MOVEREQ/CLOASSGN activity uses the user IDs of the user who is closing the Move Request and the user to whom the member is assigned.
For example, if the MOVEREQ/CLOASSGN activity authorization specifies Users sharing group? as Y and all other fields are N, the user closing the Move Request and the user to whom the member is assigned must have a group in common between their CA‑PanAPT user ID specifications. (This is true if they are both using the *DEFAULT User ID, that is, if their user IDs are not defined explicitly to CA‑PanAPT, and *DEFAULT specifies a group.)
As a second example, assume that the MOVEREQ/CLOASSGN activity authorization specifies only Owner as Y and all other options are specified as N. The user who closes the Move Request must be the user who has the member assigned. This means that the proper assignment test fails if any member is unassigned or is assigned to any user other than the closing user.
When a Move Request is closed, for Library Codes that have assignment enabled, CA‑PanAPT ensures that each member is properly assigned. The Close Assignment Option and the authorization specified for the MOVEREQ/CLOASSGN activity (see the Control File Maintenance, section above) together define properly assigned.
The MOVEREQ/CLOASSGN activity defines a relation to be tested between user IDs. The Close Assignment Option determines which user IDs are used for the test. CA‑PanAPT makes the test only after it ensures that the user ID is authorized for the MOVEREQ/CLO activity (closing the Move Request).
The Close Assignment Option applies to all assignment tests. Whatever value you select is used for all Library Codes and all Move Requests.
|
Copyright © 2004 CA.
All rights reserved.
|
|