(Doc ID 2645791.1)
Last updated on SEPTEMBER 22, 2020
Oracle Inventory Management - Version 12.1.2 and later
Information in this document applies to any platform.
REF 2557921.1 - Oracle Mobile Supply Chain Applications Release Notes for Release 12.2.9
GS1 barcode functionality
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
| || 1 - Does it support barcodes that utilize different combinations of GS1 application identifiers, as per above examples?|
Yes! It supports, provided Barcoded is correctly setup with Correct Fixed Lengths and Delimiters (Variable Length Fields should be followed by a Delimiter.)
2 - How does the solution cope with GS1 application identifiers that do not map to a prompt in AK Dictionary, for example, GTIN is not a filed that is represented in Oracle.
I.e. can an additional attribute name be added in the AK Dictionary fro GTIN, which then be mapped in ."
In the above example GTIN is attached to a Item and if Item is configured in the AK region and part of the Page ,then it will work.
Concatenated Barcode works only for the AK Regions Prompts which are part of the Page being scanned .
3 - In the document (Doc ID 2557921.1), you mention that profile 'MWA_DATE_FORMAT_MASK' and lookup 'ICX DATE FORMATS' should be set as YYMMDD, however in the example used, INV_EXPIRATION_DATE_PROMPT has been set as a fixed lonegth of 8 and a data value of 12122020 has been used, which contradicts this in both lonength and order of the date fields i.e. it is DDMMYYYY.
The format YYMMDD is not a seeded date format. Hence if user wants to comply to GS1 standard, they need to add this format to the lookup code and set fixed length as 6.
Adding this format to lookup code does not mean that you should always send barcode with length 6.That is individual customer requirement.
If you are sending a date value of length 8 as in the example, and you have defined fixed length as 8, we will check if there is any lookup code matching 8 characters and process the barcode.
5. Can this be done without setting up the delimiter on the scanner?
Delimiter on the scanner not required.
6. The ideal delimiter is the tab character. Can the tab character be used with the back port?
Possible with latest 1.3.1 version of MSCA App along with the some setup . Listing below the setup needed for Zebra device.
Every device will have a device specific setup needed to make use of the inbuilt scanner. Listed below is an example of the setup needed for a Zebra scanner. You will have to get in touch with device vendor and do a similar setup
for your device.
Set up needed for a Zebra Scanner:
1. Zebra uses Data Wedge software to assist the scans.
2. Make a new profile in Data Wedge - MSCA (Can be any name).
3. Disable all other profiles in Data Wedge.
4. For MSCA profile, the following settings needs to be in place
a) Enable the profile MSCA.
b) Enable Barcode Input Checkbox
c) Enable KEYSTROKE OUTPUT checkbox
i) Within KEYSTROKE OUTPUT , navigate to Basic data formatting
ii) Enable Basic Data Formatting
iii) In the Prefix to data section, enter a ‘@‘ without quotes. (Note: This is same as DATA STREAM INDICATOR as defined in mobile_key.ini file @path: $INST_TOP/admin/install/)
iv) Enable the Send Data checkbox
v) Enable Send ENTER key checkbox.
If user is using scan gun and global delimiter in the barcode is a control character (< ASCII 32), user should define another delimiter >ASCII32 in mwa.cfg file and user needs to setup Advanced Data Formatting rule in MSCA data wedge profile created using the steps listed above. Please refer to the attached document for creating Advanced Data Formatting Rule.
7. Please confirm that we do not need to set the profile option or the scanner to substitute with the back-port?
For this feature to work, No profile option settings are needed.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.