Oracle® Fusion Middleware Setup Guide for Universal Records Management 11g Release 1 (11.1.1) E10640-02 |
|
![]() Previous |
![]() Next |
Home > Setup Guide for Universal R... > Setting Up PCM Storage Space
This chapter explains how to set up and manage a storage environment in Physical Content Management.
This chapter covers the following topics:
Concepts
Tasks
Examples
See the Oracle Fusion Middleware Administrator's Guide for Universal Records Management for details about setting up offsite storage.
Storage space is discussed in more detail in the Oracle Fusion Middleware User's Guide for Universal Records Management. See that document for background and conceptual information.
The following considerations should be evaluated when considering storage space management:
At the root (top) level of the storage space hierarchy ("Storage"), only the two highest level location types can be added ("Warehouse" and "Room") by default. If more location types are needed, modify the following configuration variable in the physicalcontentmanager_environment.cfg:
NumberOfStorageTypeRootsToShow=x
where x is the number of location type levels needed at the highest storage level. For example, if users should be able to add storage locations of location types Warehouse, Room, or Row, change the value from 2 (default) to 3. Restart the Content Server for the change to take effect.
There is no limit to the number of top-level storage locations that can be created (for example, one for each warehouse).
At each level in the storage space hierarchy other than top level, only storage locations of a lower location type level can be added. For example, at the Row location type level, storage locations of the types Bay, Shelf, and Position can be added.
Physical items not assigned to any other storage location are automatically assigned to the "Other" storage location, which is always the last of the top-level storage locations of the storage hierarchy.
Storage locations can be deleted from the hierarchy only if no items are stored in them. The "Other" storage location cannot be deleted, even if it is empty.
All storage locations include a percentage which shows how much of the available storage space in the location (and all its children) is currently occupied. For example, 25% means one quarter of the maximum allowed number of stored items is currently assigned to the storage location (and all its children). The percentage of a storage location is updated daily (see next note).
By default, the available storage space for the entire hierarchy is recalculated daily at midnight. Therefore the displayed storage availability information may not be up to date as the day progresses because it still reflects the situation from the night before. If you are an administrator with the PCM.Admin.Manager right, you can force a recalculation of all available storage space by running the "Process Storage Space Counts" batch service.
A storage location can be blocked, which prevents any content from being stored in the storage location or any of its child storage locations, even if it was marked to allow storage of content. Only empty storage locations can be blocked. For example, this can be used to create a "dummy" storage location in a situation where a bay cannot be used because there is a support pillar in front of it but matching bay numbering is necessary to retain across multiple rows.
The ShowContentForStorageBrowse
configuration variable can be used to hide or reveal content when browsing a storage location. Hiding content can speed response time during browsing. If set to TRUE, content is displayed. If set to FALSE, it is hidden.
To speed response time during retrieval and browsing, set up storage so no one level has more than 100 items stored there. For example, set up a series of bays and each bay would contain 100 shelves with a maximum of 100 items on the shelf. This will speed up the browsing of objects in storage. It is also recommended that items be stored only at the shelf and position levels, not at the warehouse, room, row, or bay level. This will also speed retrieval and browsing times.
PCM uses defined space environment to keep track of the storage and retention of physical items. When working with a physical item, assign the item to a storage location, so PCM knows where it is stored and track it.
This section describes browsing the defined storage environment in PCM. It covers the following topics:
Storage space in PCM is set up hierarchically. Storage locations contain other, smaller storage locations which contain still smaller storage locations, and so on. The out-of-the-box PCM feature comes with the following storage space hierarchy (from large to small):
Figure 9-1 Default Storage Space Hierarchy
As shown in this figure, a warehouse consists of one or more rooms, a room consists of one or more rows, and so on. The further down in the hierarchy, the more specific (and smaller) the storage locations become.
The storage space environment you are working with may have different hierarchical levels, depending on how the physical content management feature has been set up for your organization.
Storage space can be depicted as in the following figure, which is similar to a genealogy chart. The Warehouse at the top level contains rooms, which in turn contain rows. A row can contain a bay and a bay can contain shelves. Within each shelf distinct positions are noted for items.
Figure 9-2 Example Storage Space Environment
PCM keeps track of the use of space in the defined storage environment, and provides information about the available storage space on the Storage Information Page of a storage location. Items cannot be stored in a location without sufficient space.
Storage locations can be added regardless of the parent location. For example, you can define a row or bay position in a warehouse.
Note: By default, the available storage space is recalculated daily at midnight. Therefore the displayed storage availability information may not be entirely up to date as the day progresses because it still reflects the situation from the night before. |
Each storage location in the storage space environment has several properties, including:
Important: The type of content storage allowed applies to a particular level only. For example, in the default hierarchy, shelves have several positions, each of which can hold content items, but no content items can be directly assigned to the shelf level (only to the positions on a shelf). Therefore the location type 'Shelf' cannot store content, whereas the type 'Position' can. |
For details about creating and using location, media, and object types, see "Configuring Location Types", "Configuring Object Types" and "Configuring Media Types".
Each storage location is assigned a location type, which helps specify where it is located in the storage space hierarchy. The available location types are defined by your administrator.
The out-of-the-box PCM feature comes with the following six predefined location types (in hierarchical order), with their standard icons for the default Trays layout:
The object type of a storage location in the storage space environment specifies what type of items the storage location can hold.
The out-of-the-box feature comes with the following predefined object types:
All. Note that an "All" object type cannot be assigned to a physical item.
Box
Document
Folder
Micro
Optical
Tape
Your administrator may also have set up a different list of object types to meet the needs of your organization. When creating a new physical item, select its object type on the Create Physical Item page.
The media type of a storage location in the storage space environment provides a further specification of the type of items the storage location can hold.
The out-of-the-box feature comes with several predefined media types, but your administrator may also have set up a different list of media types to meet the needs of your organization.
The available media types depend on the selected object type of the current storage location (see "Object Type"). The table below explains which predefined media types can be selected for each predefined object type:
Object type | Supports these media types |
---|---|
Box | Box |
Document | Mixed Fax Paper Photo |
Folder | Folder |
Micro | Mixed Microfiche Microfilm |
Optical | Mixed CD Disc DVD |
Tape | Mixed Audio Data Visual |
All | Mixed Audio Box CD Data Disc Dvd Fax Folder Microfiche Microfilm Paper Photo Visual |
If a storage location in the storage space can hold content items, its status determines whether content can be stored in the unit, and if not, why not. The status of a storage location is shown in the status column on the location page and can be any of the following:
Available: Content can be stored in the storage location, and space is available. This is the default. If no status is provided, this one is assumed.
Reserved: No content can be stored in the storage location or any of its child storage locations because it has been reserved. There may be space available in the storage location, but it has been set aside for future storage of physical items (for example, to ensure grouped storage of batches of items as they come in to be stored). If the logged-in user is the one who reserved the space, it will show as available to that person.
Occupied: The storage location has reached its maximum storage capacity, and no further content can be added to it.
A user may have blocked a storage location. This prevents storage of content in a storage location even if space is available. If that is the case, the status column on the location page is empty.
The following tasks are involved in managing storage spaces:
Permissions: The PCM.Storage.Create right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to create a new storage location in the storage space hierarchy.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
To create a location at the topmost level of the hierarchy, click Create then Define Storage Location from the page Action menu. You can also choose Create Storage Location from the Action menu for a storage location in the list to add a new child storage location at that level.
The Create or Edit Storage Page is displayed.
Specify the storage location properties and click Create when done.
The newly created storage location is now included in the storage space hierarchy at its assigned level.
Permissions: The PCM.Admin.Manager right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to add several storage locations to the storage space hierarchy in a single batch. This is useful in situations where the storage hierarchy (or part of it) consists of a well-defined tree structure with consistent naming and numbering of its constituent objects. This procedure can be used to define this storage location structure in one operation, without having to define each object separately.
You do not add the defined objects to the storage hierarchy directly from this page. Rather, specify the naming and numbering rules to be used to create the storage locations. After clicking OK, a file called StorageImport.hda is generated, which can be imported into the existing storage hierarchy.
See "Example: Creating a Batch of Storage Locations" for an example of this process.
Click Physical then Configure then Batch Storage Creation from the Top menu.
The Create Batch Storage Import File Page is displayed.
Click the Browse button.
The Select Storage Location Dialog is displayed.
Navigate to the level in the storage hierarchy where the new storage location structure should be added and click OK.
Specify the rules and parameters to be used to create the batch of storage locations.
Click Create when finished to create the storage locations in accordance with the defined specifications, or click Reset to return the screen to its initial values.
A file called StorageImport.hda is generated, and a dialog opens which enables you to save this file to your hard drive.
The newly created storage locations are now included in the storage space hierarchy at their assigned level.
The following information should be considered when considering batch creation of storage locations:
When defining a storage space, you must obey the existing location type hierarchy. Start with the highest-level storage location and work your way down the hierarchy. You cannot add a parent location below a child location (for example, a shelf above a row). If you attempt to do this, error messages will be displayed when you import the StorageImport.hda storage definition file.
The name and description of each generated storage location is built from the name prefix (if specified) and a sequential number such as "Warehouse_001," "R003," or "WH_NY-012."
The default number of digits used in the numeric sequences is 3. To change the number of digits, modify the AutoStorageNumberWidth
parameter in the storagecreationutility_environment.cfg file. Restart the Content Server after changing the parameter value.
Click OK.
The Exploring Page is displayed again.
Permissions: The PCM.Storage.Edit right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to edit the properties of an existing storage location. Depending on the storage location, you may not be able to edit all location properties.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Click Edit then Edit Storage Location from the Action menu of the item to edit.
The Create or Edit Storage Page is displayed.
Modify the storage location properties as required and click Submit Update when finished.
A message is displayed stating the storage location was updated successfully, along with a list of the current storage location properties.
Permissions: The PCM.Storage.Read right is needed to perform this action. This right is assigned by default to the PCM Administrator and the PCM Requestor role. |
Use this procedure to view information about a storage location.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Click the Info icon for the storage location or click Information then Storage Information from the location's Action menu.
The Storage Information Page is displayed listing the current storage location properties.
Click OK when done.
The Exploring Page is displayed again.
This page shows the current properties of the selected storage location, including the total available spaces (calculated from all child storage locations) and the spaces currently used. There are also locator links at the top of the page, which show where the storage location is located in the storage space hierarchy.
By default, the available storage space is recalculated daily at midnight. Therefore, the displayed storage availability information may not be up to date as the day progresses because it reflects the situation from the night before. If you are an administrator with the PCM.Admin.Manager right, you can force a recalculation of the available storage space by running the "Process Storage Space Counts" batch service.
Permissions: The PCM.Storage.Delete right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to delete a storage location from the storage space hierarchy. A storage location must be empty before it can be deleted. A location is considered empty if it does not contain any items. If a storage location has all empty child storage locations, the entire branch can be deleted. If you attempt to delete a non-empty storage location, an error message is displayed.
Note: You cannot delete the predefined "Other" storage location, even if it is empty. |
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Navigate to the storage location to delete, and click Delete then Delete Storage Location from the item's Action menu.
To delete multiple storage locations from the exploring pages select their boxes and click Delete in the Table menu.
If the storage location is empty, it is immediately deleted from the storage space hierarchy (without any further warnings), and the Exploring Page is refreshed. If the storage location is not empty, an error message is displayed and it will not be deleted.
Permissions: The PCM.Storage.Block right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to block a storage location. After blocking, no items can be stored in the location and all its child locations, even if space is available.
Only empty storage locations can be blocked. When a location is blocked, its "Allow storage of content" setting is set to "No."
An example of use is to create a "dummy" storage location a storage bay cannot be used (because of physical limitations) but it is necessary to retain sequential numbering across multiple rows.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Navigate to the storage space level to block and click Edit then Block Storage from the level's Action menu.
The initial Exploring Page is displayed again and content can no longer be assigned to the storage location. If the status column previously showed "Available," it is now empty. Also, the Storage Information Page of the storage location has the "Allow storage of content" field set to "No."
To cancel the blocked status of a storage location and allow storage of content again, edit the storage location and set its Allow storage of content setting to Yes. See "Editing a Storage Location" for details. After unblocking a storage location, its status column on the Exploring pages shows "Available" again. It was empty while the storage location was blocked.
Permissions: The PCM.Storage.Reserve right is needed to perform this action. This right is assigned by default to the PCM Administrator and PCM Requestor role. |
Use this procedure to reserve a storage location for future use.
If you reserve a storage location, all its child locations are also reserved. Only an administrator or the person who reserved a storage location can add items to it.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Navigate to the storage space level that includes the storage location to reserve.
Click Edit then click Reserve Storage on the location's Action menu.
Select the requestor reserving the space from the list of users displayed.
The initial Exploring Page is displayed again and the storage location now shows "Reserved" in its status column, with the name of the user who made the reservation in parentheses next to the status.
To cancel the reserved status of a storage location, navigate to a reserved location and choose Edit then Cancel Request on the Action menu.
Permissions: The PCM.Storage.View right is needed to perform this action. This right is assigned by default to the PCM Administrator and PCM Requestor role. |
Use this procedure to view all items currently contained in a storage location.
Click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Navigate to the storage space level that includes the storage location with items to view. Click Change View from the Table menu to view a graphical depiction of the storage hierarchy.
Click the storage name of a location to view items at that location. Click Information on the Action menu for the location to display the following options:
List items that belong here: This lists all items with the specified storage location as their permanent location.
List items that are actually here: This lists all items with the specified storage location as their current location. This list does not include any items normally in the storage location, but currently checked out.
Permissions: The PCM.Admin.PrintLabel right is needed to perform this action. This right is assigned by default to the PCM Administrator role. |
Use this procedure to create a label for a storage location.
The label file contains the barcodes and other information for the current storage location and all its child storage locations if any exist. Only storage locations that can hold content items are included. Any "intermediate" storage levels are skipped if they cannot hold content.
By default, the label for a storage location contains a barcode uniquely representing the location, the location's name, its description, and its location type.
The format of the label file depends on the Report Label Format setting on the Configure Physical Settings Page.
If the generated label file is in PDF format, Adobe Acrobat Version 6.0 or later is needed to view it.
To create a label for a storage location, complete the following steps:
Click Browse Content then Storage or click Physical then Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
Navigate to the storage space level.
Depending on the current storage location, click Create Reports from the Action menu for the location. Select one of the report types listed there.
You can also create a label for a storage location from the Page menu on the Storage Information Page. Click Create Report then the report type. This menu contains an option to print a label only if the storage location can hold content.
This example demonstrates how to create a storage location called "Warehouse_003," of location type Warehouse at the top level of the storage hierarchy.
Click Browse Content then Browse Storage.
The Exploring Page for the top level of the storage hierarchy is displayed.
You can also access the top-level storage Exploring Page from the Configure Physical Settings Page.
Click Create Storage Item on the menu bar at the top of the page.
The Create or Edit Storage Page is displayed.
Enter Warehouse_003 as the storage name and description.
Click Warehouse as the location type.
Click Create.
The newly created storage location is now included in the storage space hierarchy at the top level:
This example demonstrates how to create the definition file for a storage space structure then import this file to create the defined storage space within Physical Content Management's storage environment. The storage space structure consists of one warehouse at the top level of the storage environment, with several subordinate storage locations. Each of the lowest-level locations (Position) may hold five items, which can be of any object type.
Creating the Batch Storage Definition File
To create the batch storage definition file, complete the following steps:
Click Physical then Configure then Batch Storage Creation from the Top menu.
The Create Batch Storage Import File Page is displayed.
Click Browse to select the highest point of the hierarchy. If not selected, the 'Storage' level is defaulted.
The Select Storage Location Dialog is displayed. Select a location and click OK.
Provide these creation rules for Location Type, Name Prefix, Start Number, Number of items, Allow Content, Number Allowed, and Object Type:
Room, Room_, 1, 2, unchecked, empty, all
Warehouse, Warehouse_, 1, 1, unchecked, empty, all
Row, Row_, 1, 2, unchecked, empty, all
Bay, Bay_1, 1, 2, unchecked, empty, all
Shelf, Shelf_, 1, 2, unchecked, empty, all
Position, Position_, 1, 3, checked, 5, all
If the values provided exceed the limit set for storage (default is 1000) an error message is displayed.
Click Create.
A file download dialog is displayed.
Click Save to store the generated StorageImport.hda file on the local hard drive.
Importing the Batch Storage Definition File
To import the batch storage definition file into Physical Content Management, complete the following steps:
Click Records then Import/Export then Archives from the Top menu.
The Import/Export Content and Record Archive Page is displayed.
Unselect all items (including those under Show External Sources) except for Include Storage.
Click Browse next to the Archive File box to select the StorageImport.hda file saved earlier.
After selecting the file, click Import. The import adds the defined storage space to the existing storage hierarchy at the selected location.
For more details about import and export operations, see the Oracle Fusion Middleware Administrator's Guide for Universal Records Management.