Detailed Commitment Ledger Entries (06521)
Added functionality that allows users to view and report on historical information related to commitment entries created from Purchase Orders in NAV. The table below demonstrates the various workflows for impacting commitment entries and their effect on the historical transactions.
|Purchase Order||Release||Creates Commitment|
|Purchase Order||Reopen||Creates an entry that brings the balance for the commitment line to 0.|
|Purchase Order||Release||On second or subsequent releases the commitments are updated with a new amount based on quantity not received, unit cost, currency and taxes.|
|Purchase Invoice||Post||Posting a Purchase Invoice creates negative commitment detail line(s).|
|Purchase Order||Post||Receiving does not affect commitments. Invoicing creates negative commitment detail line(s).|
|Purchase Order||Close||Creates negative commitment detail line(s). The balance of all entries for the document becomes zero.|
|Purchase Order||Delete||Creates negative commitment detail line(s). The balance of all entries for the document becomes zero.|
|Purchase Order||Commitment Roll Forward||Excludes entries for which no entries exist in the Budget Commitment table and lines with Purchase Document Type = Purchase Invoice. Creates negative and positive entry(s) to reflect the change in dates.|
|Purchase Order||PO Roll Forward||No impact.|
Reports on commitment balances can have different purpose and understanding the dates in Detailed Commitment Ledger Entries is an important part in getting the numbers right.
- Commitment Date is the date of the commitment.
- Effective Date is the date in which this entry comes into effect.
- Entry Date is the transaction date.
The table below illustrates how the dates are being populated depending on the type of document that triggers the transaction:
|Date||Purchase Order||Purchase Invoice|
|Commitment Date||Commitment Date from the Purchase Order line||Posting Date from the Purchase Invoice|
|Effective Date||The date of the action that triggered the entry.||Posting Date from the Purchase Invoice|
|Entry Date||The date of the action that triggered the entry.||The date of the action that triggered the entry.|
The following areas in the system have not been impacted from the introduction of Detailed Commitment Ledger Entries:
- Financial Analysis and Budget Checking on Employee Web Apps.
- Altus Analytics.
- Other pages in NAV with reference to commitments.
- Posting Purchase Credit Memos using the Restore to PO functionality in NAV.
Enable Detailed Commitment Ledger Entries
To enable Detailed Commitment Ledger Entries:
- Search for Purchase & Payable Setup.
- Click on Create Det. Commitm. Ledger Entries to enable the functionality for tracking detailed commitment ledger entries.
The new commitment functionality will work in the same fashion as the current one in terms of the ability to exclude G/L accounts from commitments. The entries in the Detailed Commitment Ledger Entries table will be triggered and registered based on the workflow described in the begging section of these instructions.
Detailed Commitment Ledger Entries
New Page Detailed Commitment Ledger Entries has been created. It is available from:
- Purchase Order List and Page, and
- Budget Commitment Page.
Editing Commitments Effective Date
Users are able to change the Effective Date on a commitment entry.
To enable a user to update Effective Date on commitment entries:
- Search for User Setup.
- Select a line with a user you want to configure, Edit.
- Click on Edit Commitm. Eff. Date in the Security fast tab to enable the user to modify the effective date.
Change the Date on a Single Entry
To change the Effective Date on a single entry:
- Open Detailed Commitment Ledger Entries.
- Highlight the line for which you want to apply the change.
- Select Edit Single Effective Date from the ribbon.
- Enter the new Effective Date in the dialog that appears. Click OK.
- The Effective Date on the line will be updated. Original Effective Date will display the Original Effective Date before any changes have been made to the Effective Date column.
Change the Date on Multiple Entries
To change the Effective Date on multiple entries:
- Open Detailed Commitment Ledger Entries.
- Select Edit Effective Dates from the ribbon.
- Enter a New Effective Date and values for at least one of the filters that will limit the number of lines to be modified.
- Click OK.
- The Effective Date on the filtered lines will be updated. Original Effective Date will display the Original Effective Date before any changes have been made to the Effective Date column.
Deleting Detailed Commitments Ledger Entries
To reduce the number of records and improve performance users can also delete Detailed Commitment Ledger Entries for which the Purchase Order has been deleted or archived.
- Search for Delete Det. Commitmn. Ledger Entries.
- Specify values in the filter(s).
- Click OK.
Users can use various methods to report based on Detailed Commitment Ledger Entries:
- Filter Detailed Commitment Ledger Entry page.
- Export Detailed Commitment Ledger Entry page to Excel.
- Publish Detailed Commitment Ledger Entry page as web service and retrieve this web service as OData connection from Excel if performance is a concern.
- Publish Detailed Commitment Ledger Entry page as web service and retrieve this web service as OData connection from PowerPivot Add-in in Excel. Enhance the data model by publishing other related pages as web services and linking them to Detailed Commitment Ledger Entry. Create Excel Pivot tables based on the data model.
Configurable Standard Cheque Format (06697)
Altus Product now supports a standard Cheque Stub Cheque format when cheques are ordered from a “New Print” as a vendor. Users can configure if the cheque is preprinted or printed on a blank cheque paper. The supported MICR font for the printed cheques is MICR13B.
The following functionality is not part of the new feature:
- Bilingual text,
- Single , or no signature lines,
- Special characters (in MICR line or elsewhere, e.g. for USD cheques),
- Multi-page cheques that use a single Cheque No.
Users can now import a separate logo to Check Logo on Company Information that can be used on the printed cheques to display the logo and the company information. If the cheque is preprinted the company address, bank address and cheque no. should be part of the cheque stock.
The majority of the configuration needs to be completed on the respective Bank Account Card. The table below provides information for the fields related to the cheque format and their description.
|General||Country/Region Code||This field must be populated. For Canadian banks, please select "CA".|
|Posting||Last Cheque No.||Specify the cheque no.|
|Cheque Date Format||Specify the date format to be used on the cheques. This information is no longer retrieved from the Vendor Card.|
|Cheque Style||Choose Regular or Preprinted. Regular will require the MICR configuration on the Transfer tab to be completed as well.|
|Print Company Logo||Check the field if you are using Cheque Style = Regular|
|Signature 1||Import the signature of the first signing authority.|
|Signature 1 Max Amount||Enter maximum amount for the first signing authority if applicable.|
|Signature 2||Import the signature of the second signing authority.|
|Signature 2 Max Amount||Enter maximum amount for the second signing authority if applicable.|
|Transfer||Print MICR Encoding||Check this field if you are using Cheque Style = Regular.|
|MICR Printing Control Fields||Fill in the fields in this group as per the requirements of your bank.|
|Transit No.||For Cheque Style = Regular this field needs to be populated.|
|Bank Institution No.||For Cheque Style = Regular this field needs to be populated.|
|Bank Account No.||For Cheque Style = Regular this field needs to be populated.|
The currency symbol should be specified on the currencies to be used for printing cheques.
For Cheque Style = Regular, the user who is printing cheques needs to have font MICR13B installed on his/her workstation.
Report Selection – Bank Account
You need to choose the standard cheque report in Report Selection – Bank Account.
Integration to Parklane (06548)
This functionality applies only to Ontario and for clients using Advanced Position Management. It is designed to generate information that can then be uploaded to Parklane based on changes in employees’ information or position during a specified period of time.
For this integration to work the application consultants should ensure that the following are configured:
- Change Log Setup,
- Integration Setup,
- HR Department,
- HR Position,
- HR Employee – the fields as listed in the change log table field list,
- Payroll Controls,
- Payroll Control Group.
Change Log Configuration
The changes in employees’ information and position are tracked through the Change Log.
The following tables need to be added to the Change Log.
|23020262||HR Position Ledger Entry|
The report is checking for changes in specific fields per table, when Some Fields is selected and if a field value is not configured the system considers that no change has been done for that field. If All Fields is selected the report checks for changes in all of the fields specified below.
|Field No.||Field Name|
|21||Social Security No.|
|23020107||Emergency 1 Contact Name|
|23020109||Emergency 1 Home Phone No.|
|23020110||Emergency 1 Work Phone No.|
|23020111||Emergency 1 Mobile Phone No.|
|23020112||Emergency 2 Contact Name|
|37032318||Social Insurance No.|
Table: HR Position Ledger Entries
|Field No.||Field Name|
|3||HR Position Code|
|4||HR Position Name|
|8||Calculation Start Date|
|9||Calculation End Date|
|166||HR Position Rank|
|306||Cause of Inactivity Code|
|310||Assignment Start Date|
|311||Assignment End Date|
The report for Parklane needs additional clarification how to identify certain cause of inactivity codes and payroll controls. This is done by configuring this information in Integration Setup.
- Search for Integration Setup.
- Go to ON-Parklane fast tab and select values for:
- PKL Long Term Disability - choose the cause of inactivity code used to specify long term disability.
- PKL Maternity Leave - choose the cause of inactivity code used to specify maternity leave.
- PKL Earnings Payroll Ctrl. Grp - choose a payroll control group that contains the payroll controls used for calculating earnings on weekly basis for the purpose of reporting to Parklane
- Click OK.
The HR Position is configured as part of the normal configuration. Two fields have been added to support the integration to Parklane.
- Default Start Time,
- Default End Time.
The consultant(s) working on the integration need to configure payroll control(s) that calculate weekly salary amounts per type of pay to be used for the report. They should have G/L Post Type: Do not post to G/L.
The screenshots below show a sample Pay Control for bi-weekly Pay Period.
Payroll Control Group
The payroll controls as described in the section above should then be added to the Payroll Control Group to be used for Parklane and attached to Integration Setup.
Export Parklane File
- Search for Parklane Integration.
- The window Parklane Integration opens.
- Under the Options tab, enter the start date in the field From Date and the end date in the field To date. Apply other filters if applicable.
- Click OK to generate the Parklane file.