This chapter describes how to customize bar codes in Oracle WebCenter Content: Records. You can add a custom bar code range and process nonstandard bar code data.
This chapter includes the following sections:
The Physical Content Management (PCM) software is shipped with a default set of bar codes ranges and bar code transaction types (check in, check out, and set locations). You can add a set of bar code numbers to coincide with the system in place at your site and use them to provide additional custom functionality. After adding the numbers, a customized service must be created to use the new functionality. Consulting Services should be used to design this service.
The system can also be customized to process bar code files that are in a format other than the standard format used by PCM. This is done by altering a processing file to accommodate the format in use at your site. A detailed knowledge of Idoc Script is required to customize the processing file used to upload bar code data.
PCM bar codes are prefixed with a value when printing that should be stripped before processing. User bar codes are prefixed with U, storage bar codes with S, and object bar codes with O.
Permissions:
The Rma.Admin.Customization right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means you must assign it to a role before this functionality is exposed.
To add custom bar code ranges:
Choose Physical then Configure then Function Barcodes from the top menu.
On the Configuring Custom Barcode page, click Add.
In the Create Custom Barcode dialog, enter the bar code and the activity or event associated with the bar code (for example, Inventory or Storage Disposal). A custom code must be a number between 7000 and 9999. Click OK when done.
The Configuring Custom Barcode page opens showing the new bar code in the listing.
After defining the bar code range, contact Consulting Services to define a service called by the custom bar codes. The type of service used will vary depending on the type of functionality defined.
Bar code processing in PCM uses code written with Idoc script in a processing file to evaluate each line in a data file. You can modify the processing file to customize how the system parses and processes the bar code data files.
Important:
A detailed knowledge of Idoc Script is required to customize the file that processes bar code data. If you need assistance, contact Consulting Services.
The processing file is stored in the barcode\resources\ directory and is named barcode_process_resource.htm.
The following is an example of a standard bar code data file:
H YYYYMMYYHHMMSS 00 0000000000 - Header 20050721125151 00 1000 - Transaction code 20050721125201 00 URMUSER - Location 20050721125204 00 OB1 - Object to be processed 20050721125204 00 OB2 - Object to be processed T 000 - Footer
The header line in the standard data file begins with the value H and is ignored by the processing file. This can be customized if a header line is different or if one is absent. To modify this, change the barcodeHeaderStartsWith variable in the bar code environment file.
The standard footer line in the data file begins with T 000. When the processing file encounters this notation, processing stops and the processed data is uploaded. The barcodeFooterStartsWith variable can be changed to indicate a different footer type.
Each line in the file that is not a Header or a Footer is parsed as data. Each valid transaction must have a Transaction Code, a Location, and Items to assign to the location.
Three default transaction codes are available:
1000: Check in
2000: Check out
3000: Set permanent and actual locations; this can also be used as a check-in transaction.
As noted in Adding a Custom Bar Code Range you can also create custom Transaction Codes. If custom codes are used, the location must be set to a user, storage item or object (for example, a box, folder, or tape).
The Transaction Date (dTransDate) and the Transaction Type (dTransType, which is the code designation of 1000, 2000, 3000, or custom number) must be set in the processing file. The following values should be cleared in the processing file:
Location Type (dLocationType)
Location (dLocation)
Object Type (dExtObjectType)
Bar Code (dBarcode)
Bar Code Date (dBarcodeDate). Dates must be in the format MM/dd/yyyy HH:MM:SS.
The following variables should be set to FALSE:
Bar Code Transaction Location (barcodeTransLocation)
Bar Code Item (barcodeItemSet)
The dLocationType and dLocation values must be set to set the location. In addition, the barcodeTransLocation variable must be set to TRUE. This indicates that a location has been set for the current transaction.
If the location is a user, dLocationType must be set to wwUser. If the location is a storage location, dLocationType must be set to wwStorage. If the location is an object, dLocationType can be left blank and the processing code will determine the object type of the object during processing.
Multiple items can be assigned to the same location with one transaction. If the value for barcodeTransLocation is set to TRUE, it is assumed that the item being processed is an object being assigned to the current location set earlier. Make sure the barcodeItemSet value is set to TRUE after each item is parsed so it is processed.