Inventory Records › Inventory File Description

Inventory File Description

The CA‑PanAPT Inventory File is a collection of records with information about members of Production Libraries.

Inventory Records serve two purposes:

• They hold information about the member that can be used to control model processing for the member.
• They prevent a member from being used in different Move Requests by assigning responsibility for the member.

There are two sets of activities that can be performed against CA‑PanAPT Inventory File Records: Assigning Responsibility and Maintenance.

Assigning Responsibility

Assigning responsibility for CA‑PanAPT members to Move Request users includes:

• Assigning responsibility for the member to a user and a Move Request
• Releasing responsibility from a user and a Move Request
• Transferring responsibility to a different user and/or Move Request.

These are done through the CA‑PanAPT Inventory Maintenance functions ASN, RET, REL, and TRN, respectively. In addition, a Permanent Owner can be specified to maintain the Inventory member when it is not assigned to a Move Request user.

Retrieve copies members from a destination, such as a production, a backup, or a backout library, to a starting test library. You can only Retrieve members assigned to you. However, if the member is unassigned, it is assigned to you when you request Retrieve. Retrieve is done using the CA‑PanAPT Inventory and Move Request maintenance activity RET.

Maintenance

Setup and maintenance of the Inventory Records include adding, updating, deleting, displaying, and approving records. These are done through the CA‑PanAPT Inventory Maintenance functions ADD, CHG, DEL, INQ, and APP. Information entered in the Inventory Records is available for use by the modeling language.

If Auto Create is enabled in the Library Code, every time you do an assign (ASN) for an entity that has no Inventory Record, you implicitly do an ADD.

If Auto Retrieve is enabled in the Library Code, every time you do an assign (ASN) for an unassigned entity, you do an implicit RET.