In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary
  •   |  
    Next Page

    Additional System Changes and Limitations
    At this point in the Enterprise Edition development cycle, differences with earlier releases as well as limitations exist in various areas:
    Not all optional modules and complementary products can be used with QAD 2012.1 EE. Some of these modules are planned to be available; others may be replaced by a different type of offering.
    Some limitations exist related to technical components such as databases and operating systems.
    Some specific application features that were available in previous releases of the core application are no longer available. In some cases this is intentional; in other cases, plans exist to reimplement the features for the Enterprise Edition.
    Enterprise Financials introduces many new capabilities as well as new Financial concepts. Due to differences in concepts with Standard Financials, a clear function-by-function comparison is not always possible. Certain specific functions of Standard Financials might work differently or not be supported in Enterprise Financials.
    Updated Policy Regarding Source Code
    Source code licenses for QAD Enterprise Applications are available on a module-by-module basis and priced separately. However, even for customers who do not purchase source code licenses, QAD has historically made a subset of source available. This includes source for frequently modified reports and inquiries, and excluded transactional programs.
    The list of files supplied as part of this free subset of source has changed in the EE release. QAD is maintaining the policy of allowing modification of reports and inquiries, but is now applying a stricter criteria to qualify what programs can be modified without purchasing source. As a result of this change, customers may notice that some programs they received in previous releases are no longer available. For example, QAD previously provided all include (.i) files—including those not used by reports and inquiries. Delivery is now limited to .i files that are needed by reports and inquiries; for example, frame definitions.
    Another change in source code involves Financial source code. The new Enterprise Financials follows a different development model, and customization of source is facilitated through a customization layer that does not require direct update to the generated source code. Therefore, source for Enterprise Financial programs is not available for purchase by customers. A small subset of traditional Financial programs that still remain in the Accounts Payable (AP), Multiple Currency (MC), and General Ledger (GL) modules have been moved to the base (OS) module and are available to customers who purchase source for that module.
    Windows GUI User Interface No Longer Supported
    In the Enterprise Edition of QAD Enterprise Applications, the .NET UI is the primary product user interface. GUI is no longer supported at all. Some programs can only be run in .NET UI; many operational programs can still be run in character, but the full use of the suite requires .NET UI.
    Progress Results Files
    In QAD Enterprise Edition, a full set of Progress Results files (.qc and .qc7 files) is not provided because customer requirements for reporting vary extensively. Instead, a sample set is provided on the media containing five valid relationships. Users can add more relationships using the Progress Results application to fit their business needs. Refer to the Progress Results documentation or contact QAD Global Services for assistance with adding relationships to the existing QC files.
    Support for Optional Modules and Complementary Products
    Optional Modules Not Supported in QAD 2012 EE
    Project Realization Management (PRM)
    PRM was removed from the Enterprise Edition. It may be restored at a later time pending product management decision regarding enhancing PRM or using another project management solution.
    Centralized Order Processing (not planned)
    Centralized Order Processing (COP) is not supported in Enterprise Edition, either for sales or purchase orders. Other order management features can be used with QAD EE.
    This means that you cannot enter an SO or PO in one domain and process the SO shipment or PO receipt in another domain. However, you can open an SO or PO with the header site belonging to one entity and the line sites belonging to different entities in the same domain. In this scenario, the appropriate cross-company postings are registered.
    You can also use Enterprise Material Transfer for cross-domain sourcing of items. Enterprise Edition features enhancements to the EMT functionality that make this method easier to use.
    Complementary Products Not Supported in QAD 2012.1 EE
    QAD Manufacturing Execution Workbench (MEW) (unplanned)
    QAD Distributed Order Management (DOM) (unplanned)
    Trade Management (TrM) and APM Medical (unplanned)
    The Planner (unplanned)
    Multi-Level Pegging (unplanned)
    Q/LinQ and DataSync. The features of both these products are now included in QXtend.
    Installation and Conversion Limitations
    Installation
    Multiple-tier installation through QAD Deployment Toolkit (QDT) is not supported.
    Service pack only media are not provided. Each release is a full install, although database upgrade utilities are provided.
    Conversions
    To ensure the highest level of quality and success for customers converting to the QAD 2012.1 EE release, the participation of QAD or certified QAD partner services is strongly recommended. As a result, the conversions are disabled on the release media to ensure conversion requirements are properly reviewed and planned by QAD prior to any conversion activities.
    Operating Systems and Platforms
    Support for an Oracle database is not generally available; only Progress database can be used.
    Note: An Oracle version is available for Early Adopters only.
    Performance Tuning
    Please consult with QAD prior to implementing a Wide Area Network configuration for QAD 2012.1 EE.
    General Limitations
    Multiple Databases Not Fully Supported
    QDT does not currently support the installation of multiple databases. In addition, the application is limited in the support for multiple databases.
    Because of the use of proxies through an App Server to update financial tables, you cannot switch databases if any activity may update financial tables. Currently, this means that a user cannot connect to another database from the UI. The only switching that is allowed is from the low-level DRP and EMT routines where it is known that the resulting updates do not affect financial data.
    EMT itself works correctly in both single (cross-domain) and multiple database implementations. When using multiple databases, users must separately log in to the databases; it is not possible to switch between databases from the menu.
    GL consolidation between multiple databases is not fully supported.
    Some Financial Utilities Not Available
    Delete/archive utilities are planned. Other utilities will be created as needed.
    Handling of Euro Conversion Deferred
    The programs for converting a currency to the Euro have not been updated to work with the Enterprise Financials. This will be addressed when a need for such conversion exists.
    Financial Source Not Available
    Since the Enterprise Financials use a new component-based methodology, they cannot be modified in the way traditional MFG/PRO programs were customized. Source code for the financial modules is no longer provided. Customization templates can be used to add business logic to existing Financial programs without making invasive code changes. Documentation of the source code required for creating APIs is supplied in HTML format. Customization features will be expanded in future releases to support additional features such as including new tables or new components.
    System Cross-Reference Not Available
    Earlier versions of QAD Applications provided a system cross-reference that let you see where tables, fields, and programs were referenced. This is no longer available, since it did not apply to the new component architecture.
    Internationalization Features
    Support for country-specific requirements is being addressed in each release of Enterprise Applications. Many of these features that were previously provided as localization or partner offerings are now being provided as generic features of the product.
    For a complete list of internationalization features and planned country support, see the QAD Support Web site.
     



      |  
    Next Page