Siebel Consumer Goods Handheld Guide > Siebel Handheld Application Administration > Administering Barcode Settings for Siebel Handheld Applications >
Creating New Barcode Definitions for Siebel Handheld Applications
You can define new one-dimensional barcodes in the Barcode Administration views. To define a new barcode, you need to create a new barcode definition in the Barcodes list, then create corresponding records in the Barcode Item list to define data elements within the barcode. To create a new barcode definition
- Navigate to the Administration - Mobile screen > Barcode Administration view.
- Click New, then fill in the fields.
The fields in the Barcodes list are described in the following table:
|
|
Name |
Required. Any descriptive name for the barcode. Must be unique for all records defined in the Barcode screen. |
Sequence |
Required. This is the sequence for barcode parsing. The lower of two sequence numbers takes precedence when deciding which barcode in the list to match. For example, if a scanned barcode matches two entries in the barcode list, the one with a lower sequence number will be picked for the match. The lowest sequence number is 1. |
Barcode Type |
Required. Type of barcode standard. Can either be Location or Code. For a Location type barcode, the barcode data element parsing is done solely by the Sequence field in Barcode Item list. For a Code type barcode, the barcode data is first parsed into multiple sections by the Code field in the Barcode Item list, then is further parsed by the Sequence field for each section. For more information about barcode type, see Example of Location Type Barcode and Example of Code Type Barcode. |
Buscomp |
Optional. Used to designate into which business component the target data is placed. |
Min Length |
Optional. The minimum length for the barcode data in digits. If it is not set, the default minimum length is 1. |
Max Length |
Optional. The maximum length for the barcode data in digits. If it is not set, the default maximum length is 10000. |
Prefix |
Optional. Defines the value that the parsing algorithm uses to identify barcode definition to use. The allowed format for Prefix is any ASCII character for exact match, '#' for any single digit number match (that is, 0 - 9), '&' for any alphabet character in lower and upper case, or '*' for a wild card match. For example, you can enter ##9&* as the prefix, which means the first two characters can be any number, the third character has to be '9', the fourth character can be any alphabet character, and the fifth character can be any ASCII character. |
Suffix |
Optional. Allows you to associate suffixes with individual fields. The allowed format for Suffix is the same as the one specified for Prefix. In addition, the rules for matching Suffix are the same as the ones for Prefix. |
Description |
Optional. Detailed description for this barcode. |
- In the Barcode Item list, add new records to identify how data will be parsed from barcode.
Depending on the type of barcode standard you just defined (either Location or Code), you then need to create new records in the Barcode Item list to identify how data is parsed.
- In the Barcode Item list, Click New, then update the required fields.
Some of the fields are described in the following table:
|
|
Name |
Required. Name of the barcode item (for example, Product Name corresponds to the Product Name field). This name does not determine which field in BusComp the parsed data is written to. That field is determined by the Data Desc field. |
Code |
Applicable for Code barcodes only. Used to break a barcode into multiple barcode sections. |
Sequence |
Required. The sequence for barcode data elements parsing. For Location barcodes, this corresponds to the sequence used to parse data elements from the barcodes. For Code barcodes, this corresponds to the sequence used to parse data elements within barcode sections. |
Min Length |
Required. Minimum Length of the character string for this data element. If this is a variable length string, then Minimum Length is not equal to Maximum Length. |
Max Length |
Required. Maximum Length of the character string for this data element. If this is a variable length string, then Minimum Length is not equal to Maximum Length. |
Data Desc |
Optional. Used by algorithm to identify what field to parse this data into. The value in this field must correspond to the exact field name. For example, Product Name corresponds to the Product Name field. |
Data Format |
Optional. Defines format for data element (for example, MMDDYY is for date). |
Action |
Optional. Defines the action for the data element. Both Data Format and Action are written in the following format to the Data Desc field: <parsed data element>,<Data Format>,<Action>
See the example in Table 14. |
Example of Location Type Barcode
The two entries for the Barcode list, HIBC Secondary and IBM, are shown in Table 11.
Table 11. Location Type Barcode List Entries
|
|
|
|
|
|
|
|
|
HIBC Secondary |
1 |
Location |
Medical Product |
|
31 |
+$$9#####3 |
|
|
IBM |
2 |
Location |
Tech Product |
|
30 |
+$$9#####39 |
|
|
Entries for Barcode - HIBC Secondary in the Barcode Item list are shown in Table 12.
Table 12. Location Type Barcode Item List Entries
|
|
|
|
|
|
|
|
Prefix |
|
1 |
4 |
4 |
Prefix |
|
|
Quantity |
|
2 |
5 |
5 |
Quantity |
|
|
Exp date flag |
|
3 |
1 |
1 |
Exp flag |
|
|
Date |
|
4 |
6 |
6 |
Expiration Date |
YYMMDD |
|
Lot |
|
5 |
0 |
13 |
Lot # |
|
|
Link |
|
6 |
1 |
1 |
Link |
|
|
Check |
|
7 |
1 |
1 |
Check |
|
|
If the barcode being scanned is +$$90010039509283C001LZ, both barcode entries HIBS Secondary and IBM are good matches. Since HIBC Secondary has a lower sequence as 1, it is picked as the final match for parsing the barcode. The data is parsed as follows: {(Prefix, "+$$9") (Quantity, "00100") (Exp flag, "3") (Expiration Date, "950928,YYMMDD") (Lot #, "3C001") (Link, "L") (Check, "Z")} NOTE: In this example, the use of "Prefix" in the two tables is different. The Prefix column in the Barcode list table is required for matching the record in the Barcode list. The Prefix row in the Barcode Item list table is a user-defined data element to be parsed for a particular barcode.
Example of Code Type Barcode
Entries for Code type barcode in the Barcode list are shown in Table 13.
Table 13. Code Type Barcode List Entries
|
|
|
|
|
|
|
|
|
UCC/EAN |
1 |
Code |
Medical Product |
|
37 |
01 |
|
|
Entries for Code type barcode in the Barcode Item list are shown in Table 14.
Table 14. Code Type Barcode Item List Entries
|
|
|
|
|
|
|
|
AI 01 |
01 |
1 |
2 |
2 |
AI 01 |
|
|
Packaging Indicator |
01 |
2 |
1 |
1 |
Indicator |
|
|
UCC/EAN # |
01 |
3 |
12 |
12 |
UCC/EAN |
|
|
Link |
01 |
4 |
1 |
1 |
Link |
|
|
Quantity Section |
30 |
1 |
3 |
5 |
Quantity Section |
1000 |
Validate |
AI 240 |
240 |
1 |
3 |
3 |
|
|
|
Product # |
240 |
2 |
1 |
13 |
Product # |
|
|
The barcode UCC/EAN is parsed to three sections, 01, 30, and 240. If the barcode being scanned is 01103123456789033050240ABCDEFG, the data is parsed as follows: Parsed Data = {(AI 01, "01") (Indicator, "1") (UCC/EAN, "031234567890") (Link, "3") (Quantity section, "3050,1000,Validate") (Product #, "ABCDEFG")}
NOTE: The Code portions in the barcode appear in bold text.
|