Managing Master Data

Managing Master Data

Master Data Overview

By creating Master Data files, Users can ensure that the same models of firearms will be recorded with the same information every single time and that customer and vendor data will flow from a single data source.
Part, Customer, and Vendor Master files are not limited to specific FFLs and/ or A&D Books. If a User is operating in A&D Book A when the User creates their Part, Customer, or Vendor Master file, when they switch to operate in A&D Book B the same Part, Customer, or Vendor Master files may still be accessed and used in transactions. 

Master Data Types

Part Master: This transaction should be used by an FFL to create Master Data files for firearms. This allows for information consistency for receiving, serialization, and transfer transactions while saving keystrokes for these operations.
Customer Master: This transaction should be used by an FFL to create Master Data files for regular Customers. By creating these Master Data files, Users can be sure that the same Customer information will be consistently recorded in the eBound Book every single time.
Vendor Master: This transaction should be used by an FFL to create Master Data files for Vendors. By creating these Master Data files, Users can be sure that the same Vendor information will be recorded in the eBound Book every single time.

While the use of Master Data is not required, it is recommended to ensure consistent data is used in your eBound Book, as well as reduce keystrokes necessary to perform daily tasks.  Master Data can be added individually, or via bulk upload.  Click the name of each data type for specific instructions.


    • Related Articles

    • Part Master Data

      This transaction should be used by an FFL to create Master Data files for firearms. By creating these Master Data files, Users can be sure that the same models of firearms will be recorded with the same information every single time. **NOTE: Part ...

    • Vendor Master Data

      This transaction should be used by an FFL to create “Master Data” files for Vendors. By creating these Master Data files, Users can be sure that the same Vendor information will be recorded in the eBound Book every single time. **NOTE: Vendor Master ...

    • Customer Master Data

      This transaction should be used by an FFL to create “Master Data” files for Customers. By creating these Master Data files, Users can be sure that the same Customer information will be recorded in the eBound Book every single time.  **NOTE: Customer ...

    • Q4S21.22 Release Notes - Orchid eBound™

      Q4S21.22 Release Notes Orchid eBoundTM   This program, printed documentation and documents should not be used as a substitute for professional advice in specific situations. The procedures, images and examples in this document are for illustrative ...

    • Q4S20.22 Release Notes - Orchid eBound™

      Q4S20.22 Release Notes Orchid eBoundTM   This program, printed documentation and documents should not be used as a substitute for professional advice in specific situations. The procedures, images and examples in this document are for illustrative ...