To create a new bar code translation association:
Field | Description |
---|---|
Bar Code Type | The bar code type is populated automatically based on the bar
code type selected. Note: For a bar code
translation to be successful for Barcode Type 'Item' and Barcode Translation
Source 'UPCCaseCode', the packaging indicator for UOM 'Case' should
be defined.
In addition, an alias 'UPCCode' should be defined, and a value for this alias should be provided in 'Other Attributes' tab in 'Item Details' screen. |
Description | Enter a description for the bar code translation being created. |
Translation Sequence | Enter a translation sequence number for the bar code translation. Translation sequence defines the sequence of translations of a bar code for a given bar code type. For example, a bar code data type 'Item ID' has Item, UPC, and UPC Case Code defined as translations, with sequence numbers 2, 3, and 1 respectively. The translation sequence now is to first validate against UPC Case Code, Item, and finally UPC. |
Variable Length Code | Select if the bar code length is not fixed This indicates that the bar code length is fixed or not fixed. For example, while scanning an item bar code, the item ID could be of different lengths. |
Application Identifier | Enter the application identifier. Application identifier is an alphanumeric string used to identify the data source. For example, in EIA compliance scanning for a pallet and carton labels, a prefix of K indicates a purchase order, P indicates an item, and Q indicates the quantity. The remainder of the bar code is used to validation against the source specified. |
Fixed Length Bar Code Attributes | |
Code Length | Enter the length of the bar code. Code length is the length
of the entire stream that is scanned. Consider for example, a barcode "K6789". The length of this barcode is 5. This is because the Start Position is the one where the application identifier, "K", is located, and the End Position is the one where the last digit of the bar code, "9", is located. Code length is used to identify a bar code when validating scanned data. This is, however, not applicable for bar codes having variable lengths. |
Start Position | Enter the Start Position of the bar code. This is not applicable
for bar codes having variable lengths. As mentioned earlier, the length
that is to be configured is inclusive of the application identifier.
For example, for barcode "K6789", the Start Position should be entered
as 1 because "K" is the application identifier here, and the Start
Position is considered to be the position in which "K" is placed. However, the application identifier is not displayed as part of the Case/Pallet ID. When taken in the context of this example, it means that on scanning "K6789", only "6789" is displayed. |
End Position | Enter the End Position of the bar code. This defines the section of the bar code that is to be validated. For example, for barcode "K6789", the End Position should be entered as 5. This is because the last digit's position is considered to be the End Position. |
Bar Code Validation Source | Choose the validation source for the bar code. Bar code validation source represents the data to be validated against. For example, a bar code representing a UPC Case code for an item has a data source of UPC Case Code. A location bar code being scanned has location id as its data source or a distinct location bar code. The list of values although extensive also provides for additional sources to be added through the use of ‘External Source' data source. The externally translated source is implemented using the Service Definition Framework. |
Alias Type | Choose the alias type for the bar code. This applies when the validation source is ‘ItemAlias'. A list of defined item alias displays here from the catalog. An example is UPC Code. |
Validation Service | Choose the validation service for external validation of the
barcode. This applies when a validation source of ‘External Source' is chosen. A list of service flows defined in Service Definition Framework are displayed. Note: This service needs to support the same input and output
XML structure as the translateBarCode API. For more information, see
the Sterling Selling and Fulfillment Foundation:
Javadocs.
|