Versions Compared

Version Old Version 1 New Version 2
Changes made by

Rahul Singh

Alaf Azam Khan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Item Code Key is case sensitive.

  • Configured Item Code Key will be stored in current system only.

  • If the scanned item does not match the configured item key then the whole input will be considered as the item code value.

image-20240702-022332.png

image-20240702-023218.png

FAQs

  • What specific validation rules are being applied to the External Serial Codes and ItemCodes?

    • The validation rules involve checking the format of ItemCodes and External Serial Codes. These include patterns like ensuring the first X characters are digits or not, matching the first X characters to a part of the barcode or other SKU master data fields (style, size, color), and combinations such as a specific length or a predefined string followed by digits.

  • How do these validation rules improve or change the existing functionality?

    • These rules reduce errors in capturing and mapping ItemCodes and Serial Numbers by ensuring they follow a consistent and correct pattern, thus improving data accuracy and reducing the likelihood of mismatches or errors.

  • Are there any specific scenarios or use cases that these validation rules address?

    • The rules are applied at various entry points like item creation (GRN), returns, and wherever items are being created. They ensure that the scanned values adhere to specific patterns required by different brands.

  • Who are the primary users affected by this feature?

    • The primary users are warehouse and store operations teams who handle item entries, returns, and inventory management within the WMS (Warehouse Management System) and SFS (Store Fulfillment System).

  • Are there any new error messages or alerts introduced with this feature?

  • How does this feature impact the overall system performance or workflow?

    • The feature ensures higher accuracy in data capture, reducing the need for manual corrections and improving overall workflow efficiency. It does not significantly impact system performance but enhances data integrity.

  • Are there any dependencies or prerequisites for this feature to work correctly?

    • The validation rules are set at the client level and may use SKU master data. The system should have access to accurate and up-to-date SKU data for these rules to function correctly.