Deacom16.07 Release Notes

Please reference the DEACOM suggested update path prior to installing DEACOM updates.

Accounting

  • Consolidated Financial Statements - Version 16.07.001 offers the option to consolidate Financial Statements from multiple company databases that share the same system database. The feature works by designating one company database as the Financial Master and linking accounts in non Financial Master databases to the appropriate master accounts in the Financial Master company database. The c4_financialmaster field in the dxcomp4 table designates the company database that will be the financial master. Additional information on the feature is available via the Generating Financial Statements page.
  • Position Name Grid - A new grid has been added in Account Structure as per version 16.07.001. This grid allows users to give specific names & values for positions that makes it significantly easier to decipher the data received in various reports. If a position in an account represents the facility or division, then the Position Name Grid allows the name of the facility or division to print on the appropriate financial reports. Note that a position name may not be added when the position value is set to "1".
  • Rate field on Edit Journal Entry form - Allows user to change the currency rate used when posting journal entries. The Rate field is disabled when the Currency field is set to the system's default currency.
  • VAT Tax Calculations - DEACOM now offers the option to calculate Value Added Tax (VAT) during sales and purchase order entry. The VAT tax rule is applied to all parts, or different categories or classes of parts and can be specified for purchases and sales at all Facilities, individual Facility Groups, or a specific Facility. When VAT Tax is applied, a separate line will be added to the sales or purchase order. In addition, a VAT Tax report has been added to Accounting Reporting. Additional information is available via the VAT Tax page.
  • Sales Order Payments - Default Payment Currency - Beginning in version 16.07.014, if the Cash Account selected on the Cash Receipts pre-filter has a currency specified, this currency will provide the default value for this field and not the currency marked as the overall default. Added to support multi-entity and multi-national customers to help prevent errors and speed up transaction time.
  • Currencies - Implemented system enhancement that downloads and saves New Taiwan Dollar (TWD) to USD currency exchange rates from the Central Bank of the Republic of China (Taiwan) website each time a new Closing Rate is posted. The new code only fires when Currency Bank = EUR because the Bank of Canada provides TWD to CAD exchange rates.
  • Increased Length for Check Reference Field - The "Reference" field on the Process Checks form now allows 60 characters to be entered instead of the previous limit of 20.
  • Printing Check Details Number Increase - A new field, "Maximum Check Details", has been added to Accounting > Options. The field indicates the number of check detail records (remittance information) to print when printing checks which pay multiple invoices via a check run or via manual checks and allows companies to print the full check detail/remittance information and not the summarized details available via the Check Detail Report.

CRM

  • Attach Documents to Ticket Projects - The "View Docs" button has been added to the Edit Project form via CRM > Ticket Reporting. This button allows users to attach files or pictures directly to the Project as well as email the attachments.

Direct Store Delivery

  • Sales Order Line On Hand Quantity - A new field, "On Hand Quantity", has been added. This field displays the on hand inventory available for this Part based and is limited to the to inventory in the location the DSD device is synced to. In the case of DSD, this field can be used to support situations where operators need to know only the on hand quantity available on the truck.
  • Sales Order Templates - the DSD application now supports the ability to use sales order templates. The new "Sync Templates To DSD" field in Sales > Options, as well as the new Authorized Ship-To Companies tab on the Ship Via Method record supports this feature. Additional information is available via the Processing Orders through DSD help page.
  • DSD Routes Report - A new report, "DSD Routes", has been added to Sales Order Reporting. The report displays information regarding Direct Store Delivery (DSD) routes in the system including route start date and time, end date and time, total number of order shipped, the Ship Via, Location and User. When drilling down on a route record from this report, the system will display a lots shipped report for all lots shipped from this route. Additional information is available via the link in the first sentence.
  • Start Route Option - The "Start Route" button was added on the Route Options screen in order to save time and inputs for the user when starting a route in the DSD application.
  • Order Template Use - Now, when the user clicks "Apply" after selecting a template on the Orders tab to use on a DSD route, the template will be removed from the templates screen until the user ends the route. This helps ensure users will not select the same order template for that route more than once.
  • Delete Sales Order Lines - Left swiping on an order line will now display the "Delete" button, allowing the user to delete lines items on the order.
  • Default DSD Location and Cash Account Options - Two new fields. "Default DSD Location" and "Default DSD Cash Account" were added to the new DSD tab via Purchasing > Maintenance > Ship Via Methods. If these fields are populated, they will be used as the default when the Ship Via Method is selected in Route Options. Added to speed up processing and reduce potentially unnecessary inputs.
  • Quarantine View added to Inventory Reporting Form - Added a new view option "Quarantine" to the Inventory Reporting Form in DSD. This can now include Quarantine lots in lots that are synced to DSD, along with the ability to filter on them.
  • Prompt User when Canceling Orders - Clicking the "Cancel Order" button in the DSD application now prompts the user: ""Would you like to cancel this order?" Yes/No. If Yes is selected, the order will be cancelled. If No is selected, the system will close the prompt and go back to the order.

eCommerce

  • Syncing Item Master Changes to eCommerce Sites - The system was enhanced to auto-sync any changes made to item masters in the main Deacom application to the corresponding item master record for eCommerce saleable items indicated on the eCommerce Products tab for active eCommerce Sites.
  • New and Modified Record API Calls - Two new API Calls, General/GetNewRecords, and General/GetModifiedRecords, have been added to the eCommerce API Library.
  • Order/GetMultiple API Call - A new call, /Order/GetMultiple, has been added. This API call will retrieve sales order details for a single sales order or multiple sales orders, given the specific filters chosen.
  • New API Calls for User/Item/Customer Modifications - Eight new API Calls (User/GetModifiedRecords, User/GetNewRecords, Item/GetModifiedRecords, Item/GetNewRecords, BillTo/GetModifiedRecords, BillTo/GetNewRecords/ ShipTo/GetModifiedRecords, and ShipTo/GetNewRecords) have been added so as not to rely on the General/GetModifiedRecords and General/GetNewRecords calls for this information since the responses will be different based on Table parameter.
  • Stateless API Endpoints - A new field, "Stateless API Only", has been added to the Edit ECommerce User form. When this field is checked, only the Stateless eCommerce Endpoints can be used when this user is logged into the eCommerce application. Stateless APIs indicate that there is no specific user associated with the login, so API developers can use a generic login to make the calls.
  • Credit Card Authorization Handling - Now, when using the /Cart/CreateOrder call, prior credit card authorizations will now be correctly applied when checking out. Orders that have been created with prior authorizations can now be modified and shipped successfully. Note: When only an authorization token is supplied without full credit card details the authorization on the order can be voided or captured. However, if the order total changes, a new authorization can't be done without entering the credit card information.
  • Query for Customers by External ID user field - A new API, "/General/GetRecordIDByUserFieldIDAndValue" was added. When called, this call will return the dtd2.d2_recid associated with the dtd2 record returned. The call will return 0 if there is nothing found matching the ID and value, e.g.: {RecordID = ##}. The call contains two required parameters, ID and Value.
  • GET to POST Request Enablement - In eCommerce, the BillTo/StatelessCreate, BillTo/StatelessUpdate, ShipTo/Create, and ShipTo/StatelessUpdate API endpoints have been converted from GET requests into POST requests.
  • Paying via credit card in eCommerce - All authorization types available on Terms in the main application can now be utilized at checkout. This includes "With Authorization", "Without Authorization", "Zero Dollar Authorization", and "None".

EDI

  • Automatically Receive Purchase Orders - Purchase orders can now be received automatically via EDI Imports, including Purchase Orders with stocked inventory. The ability to automatically receive purchase orders assists with greater efficiency in communicating to trading partners that inventory is available to ship. See the Automatically receive purchase orders during EDI Imports help section for additional information.
  • Partially Receive Non-Stocked Items - Deacom now supports the ability to receive partial quantities of non-stocked items on Purchase Orders via EDI.

Inventory

  • Expanded Propagate Lot Attribute Options - Version 16.07.000 replaces the single "Propagate Lot Attributes" field on the Edit BOM Line form with three individual fields entitled "Propagate Lot Attribute 1", "Propagate Lot Attribute 2", and "Propagate Lot Attribute 3". This allows for greater flexibility and to support additional scenarios. If upgrading to version 16.07.000 or greater, and the "Propagate Lot Attributes" field is checked, the system will automatically check all three of the Propagate Lot Attribute fields.
  • Facility Level Default Shipping Quantity - Added a Default Shipping Quantity field to the Sales tab of Facilities. This field will allow the user to set the default shipping quantity behavior for each different facility. By default, the quantity will be determined by the pre-existing field in Sales Options. More information can be found in Facilities.
  • Inventory Transactions - Added the ability to use, store, and update tare weight values to a new Tare Weight field, whenever a lot is created. Depending on the form, the user has the ability to modify the tare weight value. When no tare field is present the system will use the tare weight Item Master File to automatically populate this field.
  • New Securities - 'Jobs - optimize issuing' allows user to use optimize button when issuing/staging a job. 'Inventory - optimize inventory in a master lot' includes inventory in master lots when Optimizing sales or jobs. Three securities that allowed users to use the optimize function have been consolidated into a single security 'Sales orders - optimize reserving'.
  • Lot Exclusions - Users have the option to exclude specific User Lots or System Lots from use or shipment to specific Bill-To Customers, Ship-To Customers, or Billing Groups. The feature was added for situations where a company's customers reject a system or user lot for their own subjective reasons (not something measured by the company QC or customer-specific QC) and do not want to have the same items sold/shipped to them again which may impact the customer relationship and future sales opportunities. The rejection of the lot can be triggered by a complaint or product return. Additional information is available via the Excluding lots for production use and shipment for specific customers help section.
  • Print Lot Label - The Print Lot Label option has been added to the main application for Move Inventory, similar to existing functionality that was only in WMS. This allows the user to print out the lot label when moving inventory in a warehouse, moving from production to warehouse, or warehouse to production.
  • Inventory Zone Reports - A new field, "Zones", has been added to the Inventory Reporting pre-filter. The field allows users to report on inventory based on all the inventory locations within a Zone.
  • Receiving and Staging via Container Unit - A new field, "Container Unit" has been added to both the Edit Vendor Info and Edit Quantity (Purchase Order Receipt) forms. In addition, a new option, "Container", has been added to the "Use Entire" field in the Inventory > Pre-Staging transaction. These changes support the ability to transact using an item's Container Unit which is particularly useful in the Nutra and Pharma industries where bags/boxes/containers can not be opened by the warehouse and must be staged in any quantity packed in.
  • Ability to Adjust Out Master Lots - Beginning in 16.07.002, users have the ability to adjust out Master Lots using the "Adjust On hand" button on this report or via the Inventory > Adjust On hand transaction. This features allows companies to adjust master lots at once instead of the need to de-issue individual system lots first before performing adjustments on the de-issued lots. The security setting "Inventory -- adjust out master lots" controls access to this feature. See the Adjusting out Master Lots section for steps and additional information.
  • Printing COAs from the Transactions. History, and Lot Tracking Explosion Reports - The "Print C of A" button is now available for the "Transactions", "History" and "Lot Tracking Explosion" reports via Inventory > Inventory Reporting. This was added to support customers that require COA’s to be printed for all items used in a manufactured item as well as the manufactured item. In addition to lot information fields, if the lot is associated with a sales order (based on the postref field) and running either the "Transactions" or "History" reports, then the customer and sales order header fields from the dmbill, dmship, and dttord tables are available to the COA.
  • Pre-Staging - Improved Error Handling and Processing - Version 16.07 introduces new error handling when pre-staging. In situations where data errors occur, the system will now continue with the pre-staging process and alert users at the end with the folllowing prompt: "One or more records could not be transacted and have been recorded in the system error log. Review the log to address any issues". The error log is available via System > History/Performance (Type: "System", Report Type: "Errors")
  • Updating Item Master User Search Fields - The Item Master User Search Fields (pr_user5 through pr_user9) can now be updated via the spreadsheet option.
  • Matching Serial Numbers with Userlots and Items during Receipt - The system was enhanced to allow the addition of "pr_codenum" and "fi_userlot" as column headers in Excel spreadsheets when using the "Import Excel" button on the Edit Serial Numbers form. If the spreadsheet contains pr_codenum and fi_userlot values, these will be used to match to the corresponding lot numbers in the system and populate the "codenum" and "userlot" columns on the grid of the Edit Serial Numbers form. This supports the ability to ensure that the serial numbers specified on the form are associated with the correct part and userlot.
  • Allowing Multiple Users to Reserve to Sales Orders - A new field, "Allow Multiple Users to Reserve Simultaneously On WMS", has been added to Sales > Options. This field, if checked, allows multiple users can reserve to the same sales order via the Reserve SO transactions in the WMS system and is useful in situations where multiple pickers will be reserving to the same sales order in different Zones or Locations, particularly for companies that use the Zone picking options in Deacom.
  • Facility Setting in Saved SO MRP Pre-Filter - When running order MRP with an SO MRP pre-filter that does not have a Facility selected, the resulting MRP will be run for all active Facilities.
  • Final Staging Last Iteration Change - The "Required for Picking" field on the Edit Work Flow Sequence form has been renamed to "Required to Issue" field and logic was added for Job Final Staging (in the Main Application and WMS via the Final Staging transaction) that applies only during the final iteration of staging. If, during the final staging iteration for jobs, any incomplete Work Flow Sequences on the job have the Required to Issue field checked, a system prompt/incomplete sequences form is displayed which blocks the staging operation from completing.
  • Inventory Reporting > Locations - When filtering on Report Type by Locations "lo_IDid", "lo_capacity", "lo_capunid", "lo_descrip", other location fields, and the location capacity unit name are available to the invloc grid.

Point of Sale

  • Bill-To/Ship-To History Button Changes - Beginning in version 16.07.008, the "Bill-To History" and "Ship-To History" buttons on the Order Entry form for cash registers have been removed, and added into the pre-existing "History" button. This button now opens a new form that allows the user to choose the type of report as well as start/end dates for a convenient all-in-one solution.

Production

  • Facility Specific Default Issue Quantity - A new field, "Default Issue Quantity", was added on the Production tab of the Facility record. This field may be used to determine how the system will populate the default issue quantity for jobs this Facility, on issuing forms in the main application and WMS and in the "Quantity" field on the Inventory Final Staging form.
  • Custom BOM Notes - A new "Notes" field has been added to the Custom BOM line form. This field can be used to help alert users to any specific details related to the issuing of custom BOM requirements. This field is represented by the "bomnotes", field on the Issue grid form and can be used to further aid users when issuing.
  • Work Center Depreciation - Removed Month, Post On and Day fields and added a new Datebox to the Depreciation Date form. The Month, Post On and Day fields limited the possibilities of dates that could be introduced to run the depreciation. Now with the Date field, the user can put whatever date the user wants.

Quality Control

  • Combine Quality Controls Results - A new field, "Combine Results", has been added to Quality Control Tests in the system. The new, optional, field allows the system to compare QC values on lots being relived to production jobs, and transfer those values to the lot produced on the job when the Quality Control Tests and Quality Control Groups on the lots being relived match those of the lot being produced. The feature designed for blended lot scenarios where a lot produced on a job uses/relives multiple lots of the same material that is produced on the job and previously entered QC values can be transferred to the finished lot. See the Automatically inherit and approve QC results for blended lots section for additional information.
  • UDFs can be added to the QC Group lines and added visibility of these fields to necessary grids and reports.
  • QC INFO and QC PARENT INFO for PO Labels - The QC INFO and QC PARENT INFO block types can now be printed on PO Labels. When using the QCINFO and QC PARENT INFO blocks for PO labels, the default values from the Item Master QC group/tests will be printed on the label.

Quality Control-Stability Testing

  • Major Stability Testing Enhancements - Beginning in version 16.07.001, stability testing for production has been significantly modified and enhanced. In addition, version 16.07.001 also introduces the ability to perform stability testing on lots received on purchase orders, inter-company transfers, and sales order returns. A summary of the stability testing logic used in version 16.07.001 is indicated below. Additional information on stability testing is available via the Managing Stability Tests page.
    • Date Logic - Lots requiring Stability Testing will automatically be moved into a QC status of Pending QC once the stability test date is reached. The "time clock" for when to place a lot into stability testing starts from the date the lot was previously tested. The field containing the date the lot was previously tested is stored via dtqc5.q5_date. See the data dictionary for additional information on this field. The stability testing time calculation is therefore: last lot QC test date (dtqc5.q5_date) plus number of days listed in the "Stability Days" field on the Edit QC/Stability Tests form.
    • QC Status Logic - As indicated in the previous bullet point, lots requiring stability testing will automatically be placed into the Pending QC status when the lot hits it's stability testing date, where it will be unavailable for normal issuing, reserving, and shipping.
    • Stability Testing Check Logic -The "Run Automated Processes" checkbox on the DEACOM Web Service form needs to be checked in order for the system to automatically check for lots requiring stability testing. When this box is checked, the system will conduct the check when the application is started and once a day at midnight.
  • QC Pending Estimated Release Date - The estimated release date for QC Pending lots in MRP has been corrected to calculate as: lot creation date + item QC lead days + item safety days (fi_lotdate + pr_qclead + pr_safedays). The lots are then moved to the "+On Hand" bucket.

Sales

  • Sales Invoicing via Scripting - Added ability to invoice a shipped sales order through scripting. Information and an example can be found in the Scripting Library.
  • Canceling Child Orders with Inventory Issued - Users can no longer delete a Child Order line from a Master Order if it will cause that Child Order to be canceled with inventory still issued to the Child Order.
  • Check for Duplicate Ship Vias on Master Order Lines - The system now checks when using Master Orders to ensure that Ship-To records do not have two different Ship-Vias entered on different lines during order entry. In this case, the user will be alerted and and informed of which lines contain different Ship-Vias.
  • Sales Rep/Sales Rep Manager Filter Options - A new pick list, "Sales Rep Filter", has been added to the Order Reporting (Sales) pre-filter and the Customers pre-filter. The field is used to filter Sales Orders based on the Sales Reps assigned, or the Sales Reps assigned to a specific sales rep manager.
  • Master Order Ship-To Modifications - A new button, "Modify", has been added to the Select Ship-To Companies form to allow users to modify Ship-To records.

Scripting

  • Password Method For Encryption - The Event.Form.Inputs().Password method has been added to allow the true/false value to be set in order to turn on/off the password mask for Textbox inputs. The feature supports the ability to encrypt fields in the database for increased security.

Security

  • Pre-Staging Issue Type Security - The security setting, "Production - change issue type" was enhanced so that users without this security will have the "Type" field on the Pre-Staging form disabled, both in the WMS and Main applications.

WMS

  • Adjust On Hand - Allows users to perform Adjust On Hand via WMS. Works nearly identical to performing the same actions in the main application, requires security setting "WMS -- adjust on hand".
  • Allow PO receipt without physical scan - Allows user to to restrict the WMS PO receipt function. The new security setting 'WMS -- allow PO receipt without physical scan' is used it in conjunction with the 'Enforce Barcode' setting.
  • BOM issue unit functionality - Allows users to set a default issue unit for a part on a BOM revision or custom add.
  • Require WMS Settings On Login - New to version 16.07.001, a new flag, "Require WMS Settings On Login" has been added to User Groups in the main application. This new, optional, field when checked will prompt a WMS user to confirm their settings each time they successfully login to a scanner. This is useful for instances where the scanners move around the floor frequently, to ensure proper settings like Printers are correct for their temporary location.
  • Change Host Picker - Beginning in version 16.07.077, the Host form will always pop up first when launching the WMS application or when using this "Change Host" option. The form will also have a find host button which when clicked displays all available hosts. In addition, when a new host is entered or selected, the user will receive the following prompt: "This operation requires logging out. Are you sure you wish to proceed?" If yes is selected the user is logged out and the login form updates to the new host.
  • Container Unit Default - If the Part Number selected has a "Container Unit", the Container Unit will be defaulted in the "Unit" field for the WMS Move, WMS Issue Job, and WMS Pre-Stage transactions.
  • Application Identifier 92 Added for Deacom Shift ID - The Application Identifier of 92 is now set to be used as the Deacom Shift ID in barcodes.