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  |   On Demand  |   Home  |   qad.com




QAD 2007.1
This release of QAD Enterprise Applications 2007 includes all ECOs closed between October 6, 2006, and July 27, 2007. A few significant changes introduced with ECOs that modify product features are highlighted in this section.
Note: This update is the equivalent of Service Pack 6.
Quality Management
Specification Functionality Change and Update Utility
Master Specification Maintenance (19.1.1) and Item Specification Maintenance (19.1.13) have been modified to prevent you from defining a specification that includes test steps with the Number field (mpd_type, ipd_test) blank. A blank creates problems when recording test results in some user interfaces, so the Number field is now a required value.
After installing the release, you should run the new utility Update Blank Master Specification (19.25.1, utmpnbr.p) to populate blank mpd_type and ipd_test fields in existing records.
1
First run the program in simulation mode, then review the resulting report.
2
Set Update Master Specification and/or Update Item Specification to Yes. The system sets each instance of a blank field to *****.
3
Use the browses and reports on the Item Specification Menu (19.1) to identify updated records.
4
Manually modify the Number field in the appropriate maintenance program as needed.
Quality Order Report
A new Include Closed field has been added to Quality Order Report (19.9).
Set this field to No and leave Status blank to limit the report output to open orders. Previously, since open orders have a status of blank, there was no way to show only those orders based on the Status field.
Leave the field set to Yes (the default) to continue using the report as it was before Include Closed was added.
Formulas
A new Formula Only field has been added to Formula Cost Report (15.7.4) and Item-Site Formula Report (15.7.8). Set the field to Yes to limit the report to formulas. Otherwise, it includes both formulas and product structures.
Additionally, Formula Inquiry (15.6) and Item-Site Formula Inquiry (15.7.7) have been modified to display only records with Formula set to Yes in Formula Code Maintenance (15.1). Previously, these programs also displayed product structure records.
Routing Cost
A site range has been added to the selection criteria in Item Routing Cost Report (14.13.15).
Additionally, the program has been modified to look first for site-specific records defined in Item-Site Planning Maintenance (1.4.17). Previously, it only selected records defined in Item Master Maintenance (1.4.1).
Lean Manufacturing
Card Management
A new Kanban Activity Recap function (option 6) has been added to Kanban Card Management (17.22.16.16) to let you print cards before exiting from the program. If any cards were created or activated, this function displays the Kanban Activity Recap frame. Individual logical fields let you print created cards, activated cards, or both. You can also print card comments.
Note: The print function applies only to cards created or activated during the current session.
Previously, the system was designed to display a print frame before exiting if cards had been created or activated during the session. However, this function did not work consistently in non-character user interfaces.
Pitch Calculation
The calculation logic that validates pitch quantity has been modified in Kanban Process Maintenance (17.22.3) and Basic Process Calculations (17.22.11) to add a threshold value.
Because current functionality supports only fixed-pitch processes, pitch quantity calculations use a lowest-common-multiple approach. If the user-specified process pitch quantity is not a common multiple of all the kanban quantities of the loops using the process, the system previously recommended the lowest common multiple.
However, when a process supports many loops with various kanban quantities, the quantity recommended using this approach could be unrealistically large. The calculation time involved could also have a significant impact on system performance.
Now, the calculation uses the following threshold value:
100 * Largest kanban quantity
As soon as the calculated lowest common multiple exceeds this value, the system assumes that this is a variable-pitch process. It displays a message recommending that you set the pitch to the largest kanban quantity.
Accumulator Monitor
A new Enter Number of Times to Execute field has been added to Accumulator Monitor (17.22.19.6).
The default is 0 (zero). If you do not change this, the process continues to run until you stop it manually, just as it did before the field was added.
If you enter a number, the process runs the specified number of times, then exits.
You can use this field to eliminate an issue related to batch processing. Previously, when the program was run in batch, the batch processor did not have an exit point for Accumulator Monitor. If other programs were included in the same batch, the processor never got to them. However, you can now enter a value in this field. After running Accumulator Monitor the specified number of times, the batch processor moves on to the next task in the batch.
Invoices
A new Print Tax ID on Invoice field has been added to Sales Order Control (7.1.24).
When this field is Yes, the output of Invoice Print (7.13.3) includes the Tax ID - Federal value specified in the tax frame of Customer Maintenance (2.1.1).
The new field also applies to other programs that let you print invoices, such as shipping functions.
Logistics Accounting
A new Include Logistics field has been added to Purchase Receipt Report (5.13.5). You can set use this field to control how variances between the PO cost and the Standard GL cost are reported.
Yes: The system considers logistics charges when calculating variances. You should set the field to Yes to avoid misleading results in this report when you are using Logistics Accounting.
No (the default): Variances are based strictly on a comparison between PO cost and Standard GL cost, without considering logistics charges. This is the way the system behaved before the new field was added.
Enterprise Material Transfer
A new Export Hold Sales Status field has been added to the Enterprise Material Transfer (EMT) frame of Sales Order Control (7.1.24).
The new field adds flexibility to the way EDI ECommerce PO export functions send EMT purchase orders to the secondary business unit (SBU) supplier based on the value of Send Credit Held SO in Supplier Maintenance (2.3.1).
When selecting EMT orders for export, the system now first looks at the Export Hold Sales Status field. Subsequent actions depend on its value.
Blank (the default): The system exports all orders to SBUs with Supplier Maintenance records that have Send Credit Held SO set to Yes, regardless of action status.
HD: When Send Credit Held SO is Yes, the system exports orders with an action status of HD or blank. Orders with any other action status are excluded.
Other non-blank value: When Send Credit Held SO is Yes, the system exports orders with Action Status set to this value or blank. Orders with any other action status are excluded.
Note: When the sold-to customer’s Customer Maintenance (2.1.1) record has EMT Credit Flow set to Yes, the exported PO includes the Action Status value from the primary sales order.
Previously, EDI ECommerce PO export functions only selected EMT orders when the primary sales order Action Status field was blank (regardless of the setting of Send Credit Held SO) or HD (when Send Credit Held SO was Yes). If Action Status was any other value, the PO was not exported to the SBU.
VAT Registration Codes
A new table-based function has been introduced to support value-added tax (VAT) registration code formats required for European Union (EU) countries.
Previously, additions or modifications required changes to the source code. Now, when new countries are added to the EU, corresponding valid formats can be defined as table entries.
This enhancement adds three new menu programs:
Use VAT Registration Format Maint (2.13.3.20) to enter or update registration code formats. Specify a VAT prefix (country code), country name, and up to 9 valid formats. Processing functions have been updated to validate that the specified VAT code matches a format defined for the associated country in this program.
Use the following standards for creating a format:
Do not enter the country code as a prefix. The system builds valid records by adding the value from the VAT Prefix field.
9 represents any number 0-9.
A represents any letter A-Z.
X represents any number 0-9 or letter A-Z.
Define a record with blank VAT Prefix to allow for a blank ID in any addresses in a country without a VAT registration number.
Note: The Dutch format (VAT prefix NL) requires the letter B as a hard-coded character in position 10: 999999999B99.
Use VAT Registration Format Inquiry (2.13.3.21) to view existing records.
Use VAT Registration Format Init (2.13.3.25, utvatreg.p) after installing the release to load an initial set of format definitions. The initial data load includes valid format definitions for EU member countries as of January 2007.
General Ledger Report Writer
A new Field Separator field has been added to GL Report Writer Control (25.21.24). When you export a report to a file using Run Report (25.21.17), the system uses the specified character as a field delimiter.
Previously, the system used a hard-coded comma to separate fields. This new feature provides the flexibility needed to support international requirements.
Service/Support Management
Material Orders
You can now modify the GL effective date in Material Order Shipments (10.7.6 or 11.11.6) and MO Direct/Pending Returns (10.7.8 or 11.11.8).
Previously, no Effective Date field was available. The transactions were always effective on the current date.
Contract Price Rounding
A new Intermediate Rounding field has been added to Contract Control (11.5.24). This affects the way extended prices are calculated by service contract quote, maintenance, shipping, billing, and invoicing functions.
When this field is Yes (the default), the system first multiplies the net price by the item quantity and rounds the result. It then multiplies this value by the quantity to bill—based on the billing cycle code—and rounds the total to yield the extended price.
This was the only method available before the new field was added. In some cases, rounding twice during the calculation can limit the amount of precision available to the user. For example, a contract priced at $100 per year might have a system-calculated price during contract invoicing of $99.96.
When Intermediate Rounding is No, the system consistently calculates the extended price by multiplying the item quantity by the net price and the quantity to bill, then rounding the result. In this case, the same $100 contract would be invoiced at $100.
Bill-To Address in RTS
A Bill-To field has been added to RTS Maintenance (11.7.3.1). The default is blank; you can enter any valid company address code.
When you print the return-to-supplier document using Purchase Order Print (5.10) with Print Bill-To Address set to Yes, the street address associated with the address code prints on the RTS.
Previously, you could not include a company address on the printed RTS.
EDI ECommerce
New Control Field
A new EMT Inbound Directory field has been added to ECommerce Control (35.17.24). When you use Enterprise Material Transfer (EMT), use this field to specify the directory where ECommerce EMT Manager (35.22.13) looks for source files when Import Files is Yes.
Previously, the import process used the same source directory (Inbound Directory) as Document Import (35.1). The new field lets EDI implementers separate EMT-specific import processes from other EDI imports.
To differentiate between the two directories, the Inbound Directory field in ECommerce Control has been relabeled EDI Inbound Directory.
Note: You can leave EMT Inbound Directory blank. In that case, ECommerce EMT Manager continues to use EDI Inbound Directory as the source of imported files.
Variables Update Utility
A new utility program, Update Transformation Variables (35.17.22, uxedtrv.p), has been provided to support EDI ECommerce performance enhancements that are included in the release.
If you use ECommerce, you must run this utility after installing the release update to avoid errors during document processing. See Update Installation Guide: QAD Enterprise Applications 2007.1 for information.
Support for Advanced Reporting and Dashboards
You can use programs on the new Report Setup Menu (36.4.21) to support advanced reports and dashboards designed using the Cognos reporting tool. Additionally, several QAD-designed dashboards are available with QAD Business Intelligence 2.5.
Dashboards add an interactive element to reports. They let you:
Drill up and down to see higher and lower levels of detail.
Include multiple charts derived from different data sources in a single report.
Important: Although the new setup menu is available in all user interfaces, you can only view the resulting reports and dashboards through the QAD .NET UI.
QAD-Provided Dashboards
If you have purchased QAD Business Intelligence 2.5 and the appropriate supporting elements, you can implement several QAD-provided dashboards. See Technical Reference: QAD Business Intelligence 2.5 for detailed requirements and procedures.
Custom Reports and Dashboards
You can implement custom reports and dashboards in QAD 2007.1 without using QAD Business Intelligence, as long as you have installed the following components:
QAD .NET UI, version 1.0 or higher
QAD ReportNet Bundle 1.0
Cognos 8.2
Use the following workflow to implement custom reports and dashboards.
1
Set up the QAD report server after installing Cognos 8.2.
2
Create reports and dashboards using Cognos Report Studio. See User Guide: Cognos BI 8 Report Studio for details.
3
Configure report settings and perform report synchronization using the new QAD 2007.1 menu programs:
a
Use Report Control (36.4.21.24) to configure report server settings and view or modify URL parameters.
b
Use Report Synchronization (36.4.21.2) to synchronize reports between the system and the report server.
c
Use Report Parameter Synchronization (36.4.21.4) to synchronize report parameters in the system with the report server.
4
Create menu entries for the new reports using Menu System Maintenance (36.4.4).