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




Feature Changes
.NET UI Dashboards
The latest version of the QAD .NET UI features a new navigation concept: dashboards.
Dashboards bring together browses, Web pages, business intelligence, and metrics within panels. Each panel offers a quick summary; to find out more, you click on the panel. As a user, you can create, edit, and delete dashboards directly in the QAD .NET UI. To create a new dashboard, in the Applications pane, open Dashboards | Create Dashboard and add panels. You can double or triple the width of panel. You can also copy and edit an existing dashboard. As an administrator, you can share the dashboard with others and assign it to one or more roles. For more information on using dashboards, see the Introduction to QAD Enterprise Applications User Guide. System administrators can change the maximum number of panels allowed in a dashboard, copy dashboards between systems, and modify access and display settings. For additional information on configuring dashboards, see the QAD .NET UI Administration Guide.
You can start creating dashboards right away, but you can also get sample dashboards in three functional areas—Financials, Customer Management, and Manufacturing—that can be associated with roles in your system. The sample dashboards are available for download from the QAD Store ( http://store.qad.com ). To install the sample dashboards, use the package installation tool included with the download. After installing the dashboards, edit the role assignments for dashboards.
Daybook Masks
Daybook masks allow you to specify a selection of daybooks and daybook groups that you want to lock at GL period closing. This functionality prevents postings to these daybooks for the current entity and GL period. You can also lock daybooks for groups of entities. See “Multi-Entity Processing” for more information on entity groups.
Daybook masks introduce a greater level of granularity to the closing process by enabling you to build separate daybook masks for each stage of your closing process. You can also use daybook masks to prevent postings to particular accounting layers such as the US GAAP layer and local GAAP layers.
Use Daybook Mask Create (25.21.5.1.1) to create a daybook mask by selecting daybooks or daybook groups that belong to the shared set for the current domain. Daybook masks cannot include periodic costing daybooks.
Entity GL Period Lock by Daybook
Use Entity GL Period Lock by Daybook (25.21.5.6) to apply a daybook mask to a GL period.
When a daybook mask is applied to a GL period, the overall status of the GL period remains Open, even if certain postings are blocked depending on the daybooks defined in the mask. You can only apply active daybook masks to GL periods, and only one mask can be associated with a GL period at any time.
There are some restrictions on applying daybook masks to GL periods. You cannot apply a daybook mask to a GL period if:
The GL period is a year-end closing period.
The daybook mask contains customer invoice daybooks with operational control, and Invoice Post and Print is running.
The daybook mask contains daybooks of type journal entry with operational control, and there are operational transactions outstanding.
Note: To overcome this restriction, run Operational Transaction Post and then apply the mask.
The daybook mask contains revaluation daybooks and there are unposted revaluations for the GL period.
The daybook mask contains daybooks of type AP matching, and AP matching postings for the GL period exist in the transient layer.
To remove a daybook mask from a GL period, clear the contents of the Daybook Mask field in Entity GL Period Lock by Daybook, and click Save.
Note: Locking a GL period that has a daybook mask applied to it removes the daybook mask automatically; removing the lock from the GL period does not reapply the daybook mask.
New Programs for Daybook Masks

New Programs for Daybook Masks
 
Menu
Label
Program
25.21.5.1.1
Daybook Mask Create
BCMask.Create
25.21.5.1.2
Daybook Mask Modify
BCMask.Modify
25.21.5.1.3
Daybook Mask View
BCMask.View
25.21.5.1.4
Daybook Mask Delete
BCMask.Delete
25.21.5.1.5
Daybook Mask Copy
BCMask.Copy
25.21.5.6
Entity GL Period Lock by Daybook
BPeriod.LockJournalPeriod
Multi-Entity Processing
Multi-entity processing enables you to group entities together, so that you can save time by carrying out period end activities for multiple entities at once without the need to switch between entities. Multi-entity activities reduce data maintenance time and provide better control over routine and largely repetitive period end tasks. Entity groups are stored at database level.
To create an entity group, use Entity Group Create (36.1.1.2.5). The current entity must be included in the entity group, and different entity groups can be used for each of the closing activities.
The following activities are possible at entity group level:
Entity GL Period Lock by Daybook
Revaluation Simulate
Revaluation Post
Entity GL Period Lock
Entity GL Period Report
Important: If you add the current entity to an entity group for the first time, you must log out and log in again before you can see the option to run an activity for an entity group.
To run Entity GL Period Lock by Daybook, Entity GL Period Lock, or Entity GL Period Report for an entity group, select the entity group from the Apply To field in the relevant activity. Similarly, use the Simulate For and Post Simulation For fields to select an entity group in Revaluation Simulate and Revaluation Post respectively. You can only select an entity group that contains the current entity; other entity groups are not visible.
The following behavior occurs when running activities on entity groups:
If the activity fails for one entity within the entity group, you are informed of the entities that the activity failed for. The activity completes for all remaining entities. For example, if you do not have role permission for a specific activity for an entity in the group, an error displays for that entity; the activity completes for the other entities.
If the start date or end date for the selected GL period is not the same for all entities in the group, a warning displays.
For activities that involve running a consistency check, by default all entities included in the group are selected for the check; these entities display in the Entity Code field. Clicking within this field removes the selection of all entities apart from the entity that you click on.
Entity GL Period Lock by Daybook
A new activity, Entity GL Period Lock by Daybook, has been added in QAD Enterprise Applications 2013.1. For an explanation of this activity see “Entity GL Period Lock by Daybook”.
The following behavior occurs when running Entity GL Period Lock by Daybook on entity groups:
If the daybook shared set is not the same for all of the entities in the entity group, an error occurs.
Revaluation Simulate
The following behavior occurs when running Revaluation Simulate on entity groups:
The system generates a separate rev number for each entity in the group, and displays the rev number for the current entity in the Rev Number field.
A progress bar appears at the bottom of the screen to show the entity that Revaluation Simulate is currently processing, and how many entities remain to be processed. If you click Stop, Revaluation Simulate stops processing after the entity currently processing completes.
When you select the Include Statutory Currency field and run simulation on an entity group, if some entities in the group do not have statutory currency enabled, an error appears and Revaluation Simulate completes only for entities with statutory currency enabled. If you have selected both Include Base Currency and Include Statutory Currency, then Revaluation Simulate completes for all entities selected, but the statutory currency revaluation only completes for those entities that have statutory currency enabled.
After running Revaluation Simulate, the results appear in a grid on the bottom half of the screen. These results apply to the current entity only; if you want to see the details for each entity in the group, run the simulation entity by entity or run revaluation view for each entity.
Revaluation Post
The following behavior occurs when running Revaluation Post on entity groups:
A progress bar appears at the bottom of the screen to show the entity that Revaluation Post is currently processing, and how many entities remain to be processed. If you click Stop, Revaluation Simulate stops processing after the entity currently processing completes.
If there are posting restrictions on either the current GL period or the next GL period for any of the entities in the entity group, an error displays when you run Revaluation Post. This is because the revaluation posting reverses in the next GL period.
When running Revaluation Post for an entity group, the system posts to the current entity based on the contents of the Posting grid. The system posts to other entities in the group based on the selection criteria specified in the search fields above the grid. If you search for revaluations and then clear the Selected field in one or more of the resulting rows in the grid, a message displays informing you of the difference in behavior when posting to the current entity and when posting to other entities in the group. If you want to continue with the postings, click Yes.
Multi-Entity Closing View
The Multi-Entity Closing View browse collection lets you determine the closing status of periods across all domains and entities in the database.
You can view:
The status of the period: open, closed, frozen, or reported.
Whether or not there is a daybook mask code assigned to a period.
Which of the application areas are open or closed for a period; available ledgers are Inventory, Purchases, Sales, and GL.
Whether or not there are unposted operational transactions in a period.
Whether or not there are posted revaluations in a period.
Supplier invoices with an allocation status of Transient Allocation.
The data displayed in the browse is sorted by year, then period, then domain, and finally by entity.
The Pending Invoices tab contains a browse related to the GL period selected in the main browse; this browse displays any sales orders that were shipped in the selected period and are ready for invoicing.
New Programs for Multi-Entity Processing

New Programs for Multi-Entity Processing
 
Menu
Label
Program
36.1.1.2.5
Entity Group Create
BCompanyGroup.Create
36.1.1.2.6
Entity Group Modify
BCompanyGroup.Modify
36.1.1.2.7
Entity Group View
BCompanyGroup.View
36.1.1.2.8
Entity Group Delete
BCompanyGroup.Delete
25.21.5.6
Entity GL Period Lock by Daybook
BPeriod.LockJournalPeriod
 
Multi-entity Closing View
 
Modified Programs for Multi-Entity Processing

Modified Programs for Multi-Entity Processing
 
Menu
Label
Program
25.4.2.3
Entity GL Period Lock
BPeriod.LockAccountingPeriod
25.4.2.5
Entity GL Period Report
BPeriod.ReportAccountingPeriod
25.21.1.1
Revaluation Simulate
BRevaluation.Simulate
25.21.1.5
Revaluation Post
BRevaluation.Post
SEPA
The Single Euro Payments Area (SEPA) is a payment-integration initiative of the European Union (EU) to simplify electronic bank transfers. Within SEPA, all Euro payments are treated as domestic payments.
A SEPA reference number is an alphanumeric string, up to 25 characters long. The letters RF always appear at the beginning of a SEPA reference. The two characters following RF are check digits and the remaining characters make up the actual reference.
For customer payments, SEPA payment references are generated within the system and saved as a unique identifier for each transaction. For supplier invoices received, the supplier generates the SEPA payment reference and the AR clerk enters the reference in the system. The SEPA reference is then validated by the system.
The Payment Reference fields on customer and supplier screens also enable you to use SEPA to allocate payments. SEPA references are also printed on financial reports such as Customer Invoice Print (27.1.1.4) and Supplier Remittance Print (28.9.9.8). The SEPA payment reference is also used for matching in Process Incoming Bank Files (31.1.6) and is integrated in the XML message of the outgoing supplier payment file.
A payment format can be defined as SEPA by selecting the SEPA field in Payment Format Maintenance (25.11.1). When a customer or supplier bank account is set up to use SEPA, then all transactions are expected to include a valid SEPA reference number. When SEPA messages are switched on at entity level, any deviation from SEPA format returns a warning message. These warning messages do not prevent you from proceeding.
Important: If you are running QAD 2013 Patch 3 and above and you are using SEPA when processing incoming bank files and receiving payment reference information, you must apply a schema change. If you are running QAD 2013.1 EE Patch 3 and above, no change is required.
Modified Programs for SEPA

Updated Programs for SEPA
 
Menu
Label
Program
25.11.1
Payment Format Maintenance
BPaymentFormat.MaintainPayFormat
36.1.1.2.1
Entity Create
BCompany.Create
36.1.1.2.2
Entity Modify
BCompany.Modify
27.1.1.1
Customer Invoice Create
BDInvoice.Create
27.1.1.2
Customer Invoice Modify
BDInvoice.Modify
27.6.4.1
Customer Payment Create
BDDocument.Create
31.1.1
Banking Entry Create
BBankEntry.Create
31.1.2
Banking Entry Modify
BBankEntry.Modify
31.1.5
Banking Entry Allocate
BBankEntry.Allocate
28.1.1.1
Supplier Invoice Create
BCInvoice.Create
28.1.1.2
Supplier Invoice Modify
BCInvoice.Modify
28.9.3.1
Supplier Payment Create
BCDocument.Create
28.9.4.1
Supplier Payment Selection Create
BPaymentSelection.Create
28.9.4.2
Supplier Payment Selection Modify
BPaymentSelection.Modify

Updated Financial Reports for SEPA
 
Menu
Label
Program and Crystal Report Name
QRF Report
27.1.1.4
Customer Invoice Print
BDebtorReport.DebtorInvoicePrint
QAD_BDebtorReport_DebtorInvoicePrint
QAD_BDebtorReport_DebtorInvoicePrint_Excel
28.9.9.8
Supplier Remittance Print
BPaymentSelectionReport.Remittance
QAD_BPaymentSelectionReport_
Remittance
QAD_BPaymentSelectionReport_
Remittance_Excel
27.6.8.4
Customer Direct Debit Print
BDDocumentReport.DDocumentReportAutoIncasso
 
Note: Payment Reference is not printed on Customer Direct Debit Print by default, but you can add it.

Updated Operational Reports for SEPA
 
Menu
Label
Program
7.13.4
Invoice Post and Print
soivpst.p
7.13.12
Invoice Print or Reprint
soivrp10.p
Receiver Matching API
More and more companies create their supplier invoices in third-party applications, and these external invoices must be registered in QAD EE because companies are legally required to store tax details exactly as recorded on the official invoice issued by the supplier. As a result, QAD has extended the Receiver Matching API so that it can now update existing supplier invoices.
Until now, the Receiver Matching API could only create new supplier invoices. The tax details of supplier invoices created by the external application could previously differ from the supplier invoices created by the Receiver Matching API.
The extended Receiver Matching API Integration can create new supplier invoices as before. However, the API can now also update existing supplier invoices received from a third-party application in combination with additional posting lines to complete the Accounts Payable process. You can also use the API to add one or more additional posting lines with extra charges. The supplier invoices are created based on the information in the purchase order and receipt, in addition to the matching information passed (year, daybook, and voucher number or invoice registration number).
The extended Receiver Matching API can:
Create supplier invoices and perform receiver matching using existing functionality.
Process supplier invoices created externally and passed to QAD EE.
Add one or more posting lines to record additional:
Costs
Costs with posting to a GL account of type Open Item
Costs including SAFs
Costs with posting to a GL account of type Tax
Costs in base currency and in statutory currency
Support for Budgets on Oracle
Budgets are now supported if you are running QAD EE with an Oracle database. However, there is a limitation of 12 budget levels when running on Oracle.
Segregation of Duties
The superuser role is specially configured to provide assigned users with access to all resources in the system. This role should only be assigned to a small number of trusted users. Prior to activating segregation of duties, it is now recommended that you select the Excluded from SOD field for the superuser role in SOD Role Exclusion (36.3.27.8). Excluding the superuser role from segregation of duties means that no segregation of duties violations will be raised for this role, which speeds up the activation of segregation of duties.
If you attempt to activate segregation of duties in SOD Configuration (36.3.27.14) and the Excluded from SOD field is not selected for the superuser role, a warning displays to inform you that the activation may not process properly. You are then presented with the option to activate segregation of duties from the command line, which is a new option, or to continue with the activation using the UI. It is recommended that you use the command line to activate segregation of duties if the Excluded from SOD field is not selected for the superuser role.
Modified Program for Segregation of Duties

Modified Program for Segregation of Duties
 
Menu
Label
Program
36.3.27.14
SOD Configuration
BSystem.SODConfigure
Periodic Costing
New reports are available to track inventory and shop floor movements, inventory and WIP balances, WO close variances, and item transactions.
Additionally, changes have been made to Periodic Cost Calculation and Periodic Costing Initialize to support cost calculations for WIP of advanced repetitive orders.
New Reports
New Reports for Periodic Costing lists the new reports for periodic costing.

New Reports for Periodic Costing
 
Menu
Label
30.5.19.1
Inventory and SF Movement Report
30.5.19.2
Inventory and WIP Balance Report
30.5.19.3
WO Close Variance Item Summary Report
30.5.13.17
Item Transaction Report
Modified Programs
Modified Programs for Periodic Costing lists the modified programs for periodic costing.

Modified Programs for Periodic Costing
 
Menu
Label
Program
30.5.7.1
Periodic Cost Calculation
pccscalc.p
30.5.1.23
Periodic Costing Initialize
pcinitmt.p
30.5.15.2
PC WO WIP History Report
pcworp03.p
Receiving Legal Documents Enhancements
Legal Documents functionality has been updated to support scenarios in which PO return shippers must be unconfirmed so that the associated legal documents can be canceled. For example, this feature is needed when:
The incorrect quantity was recorded in a PO return.
The return should not have been recorded at all and must be reversed.
The fiscal data associated with the legal document is incorrect.
To make these functions available, Non-Sales Shipper Unconfirm (3.15.2) has been extended to PO Returns shippers. Additionally, Non-Sales Shipper Confirm (3.15.1) has been extended to allow it to reconfirm RCT-PO shippers and ISS-PRV shippers.
Modified Programs for Receiving Legal Documents contains the modified programs for receiving legal documents.

Modified Programs for Receiving Legal Documents
Menu
Label
Program
3.15.1
Non-Sales Shipper Confirm
icshconf.p
3.15.2
Non-Sales Shipper Unconfirm
icshcl.p
Additional New Fields
Fields have been added to some programs to enhance functionality or improve performance. These include:
A new RMA Iss. Mn/Mx Price Check field in RMA/RTS Control (11.7.24) lets you specify the way in which RMA Maintenance manages RMA issue lines when both of the following are true:
Because of a manually entered discount or a discount type price list, the Net Price of the item on the RMA issue line falls either below the minimum or above the maximum price in the item price list.
There is no warranty or contract set, or the covered amount is zero.
The field controls whether the system displays an error message or only a warning when the net price is below the minimum or above the maximum price.