Enterprise Financials Enhancements

You can now build a complete report tree in Report Tree Maintenance. You can create new analysis codes on the fly and modify existing analysis codes in a tree. These new capabilities are secured by the existing menu access security for Report Analysis Code Create and Report Analysis Code Modify.

You can prepare a complete report structure in Excel and load it directly from the Excel file on your client PC into Report Tree Maintenance. This feature allows you to create a complete new tree and its underlying analysis codes in a few seconds. You can also use Excel integration to update an existing tree and the underlying analysis codes. The Excel template can have a variable number of Excel columns, depending on the number of levels needed in the hierarchy. The number of levels in Excel integration has been increased from 12 to 99.

The Report Cube Generate program has been replaced by a program with a new user interface. During the cube generation process, detailed feedback on the progress of the cube generation process is displayed. The complete generation process happens on the server, so the process is also faster.

A composed column type is available in the definition of columns for a report. You can now create a composed column that contains variable data, depending on the row or section in the report. This column type is useful when you need a report with ratios or percentage calculations that vary throughout the report sections.

The new Fixed period type allows you to define a report column with a fixed period linked to it and enter a fixed period range for the column. The report prints the amount for that period, regardless of the period entered on the report selection. For example, if you want to create a report showing the 12 periods of the year in 12 columns, you can use fixed period type for each of the 12 months. In the same report, you can still have a Year To Date (YTD) column. Only the YTD column corresponds with the period selection that you enter when you run the report. The other 12 columns always show the 12 months. Fixed periods that fall beyond the period selected on the report selection page are automatically hidden.

Columns of type Activity contain the activity for the period range entered as the selection when running a report. To have a column on the same report that only shows the activity in a certain period or current quarter, define a column as YTD activity and the column automatically contains the activity since the start of the year, up to and including the To period that you select when you run the report.

You can now create an analysis code containing one special GL account—the System Type GL account Result Of Current Year. This account was already used in other report programs but can now also be used in Financial Report Writer balance sheets. The analysis code must only contain this single GL account linked as a distinct element.

You can also configure how zeros are suppressed on row and on column level. You can control how amounts are presented; with a currency sign, percentage sign, or currency code. You can use a color to emphasize negative amounts.

In Report Master, there are also several new report output features.

The Zero Suppress option has four settings.

• Show all COA codes: All COA codes of the COA Type (1) selection criteria you select in Financial Report Run are displayed in the report, even those with zero amounts.

The Levels to Print option allows you to create reports with variable detail from the same report tree. For example, you create an income statement report with 12 levels and much detail. You want to present an income statement to the management with only the totals and subtotals on the higher levels of the hierarchy. In this case, create a Report Master code that uses the same detailed report tree, but specify, for example, 4 in Levels to Print. The result is a summarized report only showing the first 4 levels of the tree. You can enter any number in the Levels to Print field. When you enter 0, the complete tree is printed. The same thing happens when you enter a number that is higher than the number of levels in the report tree.

Report Amount Scale enables you to specify how you want to display the amounts in the report. You can display the amounts in full, in thousands, or in millions. For columns you do not want to divide by 1,000 or 1,000,000, such as percentage amounts, simply mark the column as Always Full Amount in the Column Group details.

The Number of Decimals field enables you to select the number of decimals you want in the report. You can have between zero and three decimals. When the number of decimals is less than the precision of the amounts in the report cube, the amounts are rounded with the standard rounding method.

In previous versions of Financial Report Writer, you could explode the report output with the details of one given COA dimension. It is now possible to explode the report for three different COA Types; for example, first by GL account, then by sub-account, and then by cost center. You immediately have a much more detailed report without having to set up a lot of detailed analysis codes.

The three dimensions can be any combination of Domain, Entity, Layer, Intercompany code, GL, Sub-Account, Cost Center, Project, SAF1 - SAF10, Daybook, and Currency. However, the dimensions must be available in the cube data. Domain, Entity, Layer, Intercompany, and GL are always available in a cube but the availability of other dimensions depends on the cube definition.


Menu	Label	Program
25.16.14	Report Tree Maintenance	BReportTree.Create
25.16.12.1	Report Column Group Create	BFRWColumnGroup.Create
25.16.12.2	Report Column Group Modify	BFRWColumnGroup.Modify
25.16.11.1	Report Master Create	BFRWReportMaster.Create
25.16.11.2	Report Master Modify	BFRWReportMaster.Modify
25.16.20	Financial Report Run	c1:QAD_ReportTree

As a result of the conversion to BLF, the following program is obsolete.

Previously, you could only use Journal Entry Cross Co Excel Integration (25.13.1.10) to post cross-company journal entries defined in an Excel spreadsheet where there was a posting in the current entity that included posting lines for other entities. The enhanced functionality enables you to post journal entries that only involve a single entity in the posting, but which are for entities other than the current logged-in entity. Therefore, from the same function and spreadsheet, you can now post journal entries for only the current entity, journal entries for several different single entities, and journal entries across different entities.

To use the function, you must have access to all entities for which you want to create postings, and you must also be assigned role permissions that grant you access to Journal Entry Create in those entities.

Note: It is recommended that you use Journal Entry Cross Co Excel Integration for all journal entry postings from Excel. This function offers transaction posting line by line, detailed error messages, and the ability to automatically create correction reversal and auto reversal journal entries.

To facilitate the creation of journal entries, you can download a template in the Journal Entry Cross Co Excel Integration function. The Excel templates contains column headings that correspond to the grid in Journal Entry Cross Co Excel Integration.

When you are finished editing your spreadsheet in Excel, open Journal Entry Cross Co Excel Integration, right-click in the grid, and select Import from Excel. The entries defined in your spreadsheet are loaded into the grid. When you click Save, the system creates journal entries for the source entity and for each of the corresponding postings for the target entities. It also performs all validation and defaults values if some key fields are blank. If you specify all required values, no defaulting occurs.

Two areas of the Journal Entry Cross Co Excel Integration screen indicate whether postings are processed successfully. The Posted field at Level 1 of the grid is automatically selected by the system as each transaction is processed and saved successfully. In addition, the processing status indicator at the bottom left of the screen indicates the status of records. The screen is locked during the saving process.

For each transaction posting that fails, an error message is displayed at the bottom of the screen. Each message contains a summary of the reason the posting failed. To view more information on the posting, select the message and click the Detail button. In the Detail Message window, select the Detail tab to display the details of the posting. This information helps you to identify the relevant line in the Excel spreadsheet.

When a transaction fails to post, the Posted field is not selected. You can export the unposted transaction back to Excel for maintenance. Right-click in the grid and select Export Unposted to Excel for Maintenance. Correct any errors to the spreadsheet and open Journal Entry Cross Co Excel Integration again to load the corrected transactions.

The Fixed Assets module now supports the scenario where an organization wants to set up the system with statutory currency for the local country currency and base currency for the functional currency. In this setup, it is recommended that you have fixed asset values and depreciation in statutory currency as the leading currency. In some cases, group reporting requires depreciation of the assets in a different GAAP than the local one, using different depreciation methods and a different currency; for example, the currency of the corporate group.

To support such cases, it is possible to link a currency to each of the asset books. During the life cycle of the asset, that currency becomes the leading currency in the transactions. The values in other currencies required for posting in the general ledger are derived from the book currency by applying the historical rate applicable at the time the asset was acquired. That historical rate is stored at asset book level. In fixed assets reporting, you can choose to display values in the book currency or convert them to base or statutory currency. For GAAP purposes, you can now also set different salvage values and depreciation deviation settings.

Each asset book is associated with a book currency. The book currency is the leading currency for all amounts in transactions involving an asset. It is the transaction currency of the postings in this asset book. The GL transaction currency—book currency—values are translated to base currency and statutory currency. The exchange rates in each book are the historical rates specified by the user at asset acquisition.

By default, the book currency is the base currency of the domain. A fixed asset can have multiple books with different currencies. The amounts in the header section are in the book currency of the primary book.

You can set and adjust a salvage value for each book independently. You can also set the depreciation deviation control at book level.

If you have previously used the QAD Fixed Assets module and you want to upgrade to QAD 2014EE, a conversion is needed. There are three steps:

The first step is included in the standard QAD 2014 EE upgrade. Steps 2 and 3 are only required when statutory currency is used and assets already exist or statutory currency is introduced later in a system that already has the QAD 2014 EE Fixed Assets module.


Menu	Label	Program
32.1.9	Book Maintenance	fabkmt.p
32.1.17	Class Maintenance	faclmt.p
32.3	Fixed Asset Maintenance	fafamt.p
32.5.11	Asset Owned Report	faaorp.p
32.5.1	Periodic Activity Report	fapaderp.p
32.5.3	Depreciation Adjustment Report	faajrp.p
32.5.5	Acquisition Report	faaqrp.p
32.5.7	Depreciation Expense Report	faderp.p
32.5.9	Asset Depreciation Array Report	fadarp.p
32.5.13	Primary Book Activity Report	fapaderp.p
32.5.15	Primary Book Acquisition Report	faacqrp.p
32.5.17	Primary Book Retirement Report	faretrp.p
32.5.24	Fixed Asset Browse Extended	fabr002.p


Menu	Label	Program
32.5.21	Fixed Asset Book View	fabr003.p
32.5.25	Fixed Asset Class Browse	fabr009.p
36.25.94	Fixed Asset SC Rates Import	fascutii.p
36.25.93	Fixed Asset SC Rates Export	fascutix.p

Note: Two further new programs, Fixed Assets Extended Browse (32.5.26) and Fixed Assets Account Balance (32.5.27), are added to the menu when the Financials dashboard is installed.

For Equity GL accounts in consolidation, it is best practice to use historical rates. Often, these rates are not in the system and the rates may also be different for each entity in the system. To solve this problem, you must be able to specify a user-defined exchange rate table for each entity for those GL accounts.

Therefore, in GL Account Create (25.3.13.1), on the Currency tab, an Entities button has been added. This button enables you to specify a different user-defined exchange rate for each source entity in a consolidation. You can apply the exchange rate to any account type for consolidation purposes. The rate that you specify at entity level here must also be created as an exchange rate for the rate to be accepted in a consolidation. Create the exchange rate in Exchange Rate Create (26.4.1). This additional function is optional. If you do not specify rate type for one or more source entities, the rate type specified on account level is used for those entities.

In Journal Entry Verify (25.13.1.7), the Add button has been replaced by a Search button and the program has improved performance. Journal Entry Approve (25.13.1.8) also has improved performance and usability.

In Supplier Payment Selection Confirm (28.9.4.5), the time taken to load a selection has been significantly reduced. When a payment selection returns more than 300 record lines, the details are no longer displayed in the grid. Instead, a Browse Details button has been added, which enables you to display a separate browse with the detail lines. You can refine your selection using this browse. The browse contains the same columns as Supplier Payment Selection View.

In Supplier Payment Selection Create (28.9.4.1), the new Discounts up to field enables you to return open items with discounts up to a specific date in the future, rather than all discounts on invoices due at a future date. This feature enables you to control the due and discounted invoice selection.

You can now configure a shorter customer invoice number that is easier to type in downstream transactions. When the Daybook Control type is Operational, you can configure Number Range Maintenance for four daybook types. This change gives you added flexibility in defining invoice number segments. The daybook types are:

You can now shorten the Year and sequential Voucher parts of the invoice number and replace the daybook code with a short code or number. You can add or remove the separators between the three key parts. However, the three key parts are still required in some format.

You can also set up numbering that continues from one year to another. However, you cannot change a number range that has already been used because this action would lead to complicated validations. Therefore, to use the new functionality, new operational daybooks must be created and configured for the four daybook types and those daybooks must be linked to the daybook sets and sites as before.

In Journal Entry Create (25.13.1.1), the Template Code field has been renamed to Use Template. You now use this field to select an existing template code to apply to the entry. Select the Save as Template field to save the entry as a new posting template. When you select this field, you must specify a new posting template code in the text box.

In Journal Entry Modify (25.13.1.2), the Use Template field can be edited for journal entries with transient layers. When you specify an existing template code in the Use Template field, the related template is applied. In Journal Entry Modify, you can edit this field for journal entries at all layers. You can remove the existing template code, replace the existing code, or add a code when the field was blank. However, if you enter a code that is already used in another journal entry, an error is displayed, stating that a template with this code already exists.

Journal Entry Template View (25.13.1.19) enables you to browse journal entry templates. This browse lets you search using various criteria, such as GL period, daybook code, posting date, and template code. When you select and right-click a template in the browse, you can view and modify the template, depending on your permissions in Role Permissions Maintain (36.3.6.5).

When you are responsible for cash collection over many domains, use Customer Aging History Across Domains (27.17.21) to create a report that shows the open balances over multiple selected entities from multiple domains with the same customer shared set. You can add another Entity search field for each entity you want to include.

In Customer Payment Create (27.6.4.1) and Customer Payment Selection Create (27.6.4.6), you can now select invoice correction and credit note corrections for payment.

Two new drill downs are included in this release. Their behavior is consistent with other financial drill downs.

In Journal Entry Excel Integration (25.13.1.6), when you link attachments to the different postings, the link between the postings and the attachments is now correct.

The requests of the Cross-Company daemon now display more readable information. An issue where scrollbars were not appearing when expected has also been fixed.