Updated: 23.02.2026

John Deere DBS 365 2603 Release Note

Introduction

Dear Readers,


We are pleased to provide you with this document.

The transfer, publication or duplication of this document is only permitted with the explicit permission of TRASER Software GmbH.


Your contacts from our teams will be happy to help you. Ask us!


Your


TRASER Software GmbH

Bug Fixes

This release includes several bug fixes as well as the following new functions and improvements.

Core

New Functions

[27903] Enhanced VAT posting logic for EU service and delivery invoices

This release improves VAT handling for EU deliveries and services, ensuring that invoices, such as workshop invoices for spare parts and labor, are posted correctly. John Deere DBS 365 now automatically evaluates the proportion of goods and services within an invoice: if services (e.g., workshop labor posted to a G/L account) account for more than 50% of the total amount, the transaction is posted using the reverse charge mechanism based on the defined VAT business and VAT product posting groups. If goods (e.g., spare parts posted as items) exceed 50% of the total invoice amount, the transaction qualifies as a tax-free intra-community supply in accordance with §6a UStG and is posted using the appropriate VAT posting groups. To support this process, two new fields have been added to the General Ledger Setup, allowing users to predefine the VAT business and Product posting groups for intra-community supplies. This ensures accurate VAT entries while other accounting postings remain unchanged and enables compliant, automated VAT processing for EU service documents.

[29043] Commission handling

With this release, canceled trade-ins no longer impact commission amounts or block commission payments. When a trade-in is canceled, related commissions are automatically updated, ensuring accurate payouts and removing any pending status. In addition, users can now link related documents directly for correct commission calculation. This can be done via Link Purchase to a Sales Document in the purchase order lines menu bar or via Link Trade-in to a Sales Document in the trade-in lines menu bar, ensuring all relevant transactions are properly considered in commission processing.

Improvements

[23283] Formatting of document lines

The formatting checkboxes Page Break, Bold, Italic and Underline will no longer be displayed by default in document lines across sales, service and rent documents. These checkboxes can still be added back through personalization if needed.

[28259] Removal of confirmation message when creating documents

The confirmation message shown after creating sales, purchase, rent or service documents was removed. Newly created documents now open immediately, reducing unnecessary clicks and streamlining the workflow.

[29907] Standardized item number in order confirmation

To ensure a consistent layout across all sales documents, the order confirmation report was improved. Previously, when using a service item in a sales document, the Service Item No. was printed on the order confirmation while all other sales documents displayed the Item No.. The report has now been adjusted to also use the Item No., aligning the order confirmation report with all other printed sales documents and ensuring a consistent document layout.

[30054] Renaming of 'Service Order Types' page to 'Order Types'

The Service Order Types page was renamed to Order Types. This change improves usability and allows users to find the page more easily.

[30350] Extended 'Show Document Lines' setting

The Show Document Lines setting in the User Setup has been enhanced to ensure consistent behavior across return orders. If Show Document Lines is activated in the sales area, document lines are now also displayed in the sales return order list. If the setting is activated in the purchase area, document lines are now also displayed in the purchase return order list. This improvement ensures consistent visibility of document lines across all related sales and purchase documents.

[30497] 'Combine Fix Prices' in sales reports

The option to Combine Fix Prices is now available in sales order confirmation reports. This enhancement allows users to combine fix price lines and ensures consistent behavior between sales and service processes.

[31126] Streamlined trade-in posting

When posting a trade-in, John Deere DBS 365 will no longer create entries in the Approved Calculation Review table. This improvement streamlines the workflow, eliminates unnecessary record creation and enhances the overall usability and reliability of the trade-in process.

Machine

New Functions

[26775] 'Extension of calculation review and resource allocation

This release introduces several extensions to calculation entry types, calculation review and resource allocation. When setting up Item Charges, users can now only select Calculation Entry Types that are relevant to the Calculation Review, ensuring cleaner configuration and improved data consistency. The same restriction has been applied to Revaluation Journals, where only relevant entry types are available for selection. Additionally, Item Charges for built-in configurations can now be configured differently for the sales and purchase area, providing greater flexibility in cost allocation. In addition, the resource allocation in the sales ares of the Calculation Review was improved and Expected Additional Cost and Expected Discount are now properly represented in the calculation review. These extensions enhance transparency, accuracy and usability within the calculation process.

[30135] Opening built-in service items

Service items that are assigned to/built into another service item can now be opened directly from the configuration. Using the Open Card function in the menu bar of the Configurations FastTab, users can quickly access the card of assigned or built-in configurations, improving navigation and simplifying configuration management.

Improvements

[28500] Transfer of service item pictures to sales quote

Pictures stored on a service item can now be transferred directly to a sales quote. Users can choose whether to include all pictures or only the favorite picture, providing flexibility based on their needs. This enhancement makes it easier to include and print relevant images directly on the sales quote.

Service

New Functions

[27099] Maintenance contract reporting

With this feature, a new maintance contract report was introduced, allowing contracts to be printed and shared with customers. The layout can be customized using a Word layout, enabling flexible and customer-specific document design. In addition, the Maintenance Contract Statistics page was extended with two new fields:

  • Profit % calculation
  • Profit amount calculation

Furthermore, printed service documents for machine communities were enhanced to include the following information:

  • Customer Names
  • Share Values

Improvements

[28006] Enhanced printed service documents for machine communities

Printed service documents for machine communities have been enhanced to include customer names and share values, in addition to the existing customer number and share percentage. This improvement provides clearer, more transparent and more comprehensive information in printed documents.

[28545] Prefiltered service items in maintenance contracts

The service item number lookup in maintenance contracts is now automatically filtered to show only machines assigned to the customer listed on the contract. This ensures that only relevant service items can be selected, prevents incorrect assignments and improves data accuracy.

[30000] 'Serial No.' in 'Barcode Label Setup'

The Barcode Label Setup has been extended to support printing the Serial No. for service items.

[30205] Suppressed checklist messages when creating multiple service orders

When using the Create Multiple Service Orders action in service intervals, checklist messages are now optimized for better usability. Previously, a separate message was displayed for each created service order that had an automatically generated checklist, causing excessive confirmation clicks when creating multiple orders at once. Now, individual checklist messages are suppressed during multiple order creation. Instead, a single summary message is displayed, indicating how many checklists were created. This significantly improves usability and reduces unnecessary user interaction.

[30797] Caption change from 'Counter' to 'Meter'

All occurrences of Counter within John Deere DBS 365 have been renamed to Meter to ensure consistent and standardized terminology across the system.

Trade

New Functions

/

Improvements

[27613] Enhanced option selection usability in 'Configuration' FastTab

The usability of option selection in the Configuration FastTab has been improved. Users can now apply filters to options and filter by Category Description.

[28064] New setup for configuration sorting in sales documents

A new setup option in the Sales & Receivables Setup allows users to define how configurations are sorted in sales documents created from calculation worksheets. Users can choose to sort the configuration lines either by Category or by Line Number, providing greater flexibility and control over the document layout.

[29023] Vendor currency prompt in calculation worksheet

When importing configurations into the calculation worksheet, John Deere DBS 365 now checks the vendor’s currency. If the vendor has a different Currency Code, the user is prompted to decide whether the vendor currency should be used in the calculation worksheet. If confirmed, John Deere DBS 365 automatically recalculates the prices based on the current exchange rate. This improvement ensures transparent currency handling and accurate price calculations.

[30291] Creating service orders without 'Customer No.'

The Create Service Order action is now available even if a service item has no Customer No.. If a service item is created by releasing a purchase order, John Deere DBS 365 automatically inserts the Internal Customer from the Sales & Receivables Setup into the service item card. This allows users to create service orders more easily and ensures a smooth process.

[30622] New setup regarding configuration sort order

A new setup option Configuration Sort Order was added to the Sales & Receivables Setup. This setup allows users to define the sorting order for sales and purchase documents that are created from a configuration.

[31089] Improved filter in calculation review

The filter logic in the calculation review has been improved. Open trade-ins are no longer displayed as Exp. Sales Price in the calculation review. This ensures clearer and more accurate representation of expected values within the calculation overview.

Parts

New functions

[10804] Rework of REMAN functionality

This release introduces a centralized setup and improved automation for reman parts. A new REMAN Returnable Parts FastTab has been added to the Inventory Setup, allowing users to activate the creation of reman parts, define a default item template for these items and set up a suffix for reman parts that is added to the Vendor Item No.. In the Prices & Sales FastTab on the item card, new fields have been introduced to manage and monitor reman parts. Once the REMAN Value is entered on the item card, users can create or update reman parts directly using the new Create/Update REMAN Returnable Parts action. This process can also be executed for multiple items at once via the Create/Update REMAN Returnable Parts action in the Inventory Setup. Additionally, users now have the option to automate the process by using the Create Job Queue for Returnable Parts action available in the Inventory Setup. This feature enhances the reman functionality and helps customers create reman parts more quickly and efficiently.

[29560] Create catalog items directly from items

With this release, users can now create individual catalog items directly from existing items. Relevant data is automatically transferred from the item card to the new catalog item, eliminating the need for a full catalog import. Catalog items can be created or connected from the item card as well as within service worksheets and purchase orders. In addition, catalog items can be easily connected to existing items from the catalog items page, giving users greater flexibility and efficiency in maintaining catalog item data.

Improvements

[29579] Improved 'Link Catalog Item to Item' performance

The performance of the Link Catalog Item to Item action has been improved. Users can apply additional filters before execution. John Deere DBS 365 processes the filtered catalog items and automatically links items where no link exists yet.

[29981] Enhanced inventory difference recording

The field Difference Recording Qty has been added to the physical inventory lines. The new field supports enhanced inventory difference recording without changing existing processes.

[30235] Using storage bin code as description in physical inventory records

When creating a physical inventory recording from a physical inventory order using Make New Phys. Invt. Recording, users can now activate the Use storage location code as description option. When activated, John Deere DBS 365 automatically copies the storage bin code into the Description field of the physical inventory recording header. This enhancement streamlines data entry, reduces manual effort and shortens the overall inventory workflow.

[30776] Using order-related bins for picks

When using Tasklet Factory Mobile WMS to pick sales orders without creating a pick in John Deere DBS 365, the Bin Code defined in the sales order line will be used. If an order-related bin is specified, it is checked and, if valid, displayed in the Tasklet Factory Mobile WMS pick function. This ensures warehouse users always see the correct bin from which the items should be picked, improving accuracy and efficiency in the picking process.

John Deere DBS 365

Tip

If needed, a PDF file of the John Deere DBS 365 release note with all specific content can be downloaded here.

Bugfixes

[30315] Issue related to opening DPMEXT job queue entries from Interface Card

When activating the DPMEXT Interface and then clicking on Open Job Queue Entries in the smart notification, an error message was displayed saying: The filter "[...]" is not valid for the ID field on the Job Queue Entry table. The left side of '|' operators cannot be empty. This issue was fixed.

[30399] Issue related to PMManage calculation of total cost of sales

In the PMManage Monthly History Values table, the Total Cost of Sales valuation type was not calculated correctly, i.e., the value was always 0.00. This issue was fixed.

[30535] Issue related to missing mapping between 'General' and 'Lines' FastTab in purchase orders

In purchase orders, the Factory Delivery Date and Requested Delivery Date values from the General FastTab were not copied into the corresponding columns of the Lines FastTab when adding them manually. This issue was fixed.

[30588] Issue related to manually filling vendor order number

It was not possible to manually fill the Vendor Order No. value in purchase orders where the JDPoint Order Type value was not defined. This issue was fixed.

[30647] Issue related to connection setting order in TRASER Power BI John Deere-App

The connection settings in the TRASER Power BI John Deere app were presented in the wrong order (Lakehouse Name > SQL Connection String > Company Name). This issue was fixed. The order is now Company Name > SQL Connection String > Lakehouse Name.

[30648] Issue related to responsibility centers with blank location values in TRASER Power BI John Deere app

Ticket: 51310

The TRASER Power BI John Deere app could not correctly handle responsibility centers when no location was assigned. This issue was fixed. Empty locations no longer cause data model issues or missing data in reports.

[30905] Issue related to missing PMManage field number

The PMManage export was failing due to a missing field number in the PMManage Monthly History Values table. This issue was fixed.

[31244] Issue related to Parts ADVISOR picklists containing diacritical characters

Ticket: 52018

When processing Parts ADVISOR files where the picklist name or any content contains a language using special diacritical characters (e.g., Hungarian, Polish, Romanian, Serbian), an error message was displayed saying that the JSON file is invalid. This issue was fixed.

[31255] Issue related to wrong maximum quantities in imported parts invoices

When importing John Deere parts invoice XML files containing multiple package numbers for the same item number, incorrect maximum quantities were available in imported parts invoices in John Deere DBS 365. This issue was fixed.

[31305] Issue related to purchaser code in DC approval workflows

When starting an approval workflow with Continia Document Capture (DC), it was not possible to use the Standard Workflow functionality, i.e., the Purchaser Code value in the purchase header was always overwritten, even if no purchaser code was assigned to that user. This issue was fixed. The Purchaser Code value is not overwritten anymore, no matter whether it is filled or empty.

[31306] Issue related to parts invoice import of CORE values

When importing CORE values from a parts invoice XML file, an error occurred saying that the total amounts of created purchase invoice and parts invoice do not match. This issue was fixed.

[31326] Issue related to Product Information Interface visibility

There was an issue regarding the visibility of the Product Information Interface, i.e., its buttons and actions were not visible as expected. This issue was fixed.

[31386] Issue related to 'Transport Status Update' job queue

When running the Update RPM Tables job queue to process records of the Combined type, the RPM records were not updated, though the job queue finished without errors. This issue was fixed.

[31764] Issue related to RPM table update job queue

When running the Transport Status Update job queue, the HTTP error 400 (bad request) occurred, so that the job queue could not be finished. This issue was fixed.

[31792] Issue related to 'Service Item Serial No.' value not being filled during Parts ADVISOR imports

When importing a Parts ADVISOR picklist into a service document, the Service Item Serial No. field was not filled for automatically created lines. For manually entered item lines, the field is filled without any problems. This issue was fixed.

New Functions

[25010] Responsibility center setup extended to allow multiple dealer numbers per responsibility center

29982 - 30347 - 30348 - 30349

In this feature, the support of having the same Dealer No. value assigned to multiple responsibility centers was implemented what delivers the following benefits:

  • More flexibility for responsibility center assignment by supporting more configurations.
  • Support of JDIN dealer complexity with centralized JDPoint ordering by automatically filling the combination of dealer number and destination code for the right location.
  • Automatic adjustment of service item responsibility center assignment.
  • Dealers can assign multiple responsibility centers to a single John Deere dealer number, supporting department based operations (Parts, Service, Trade) and simplifying JDPoint handling for centralized ordering scenarios.

To set up multiple dealer numbers per responsibility center, open the John Deere Responsibility Center Mapping table and fill the following fields:

  • Dealer No.: specifies the unique John Deere dealer number. The field must be filled with the 6-digit number in accordance with the John Deere dealer account numbers definition.
  • Area: specifies for which DBS 365 area the assigned dealer number will be used for (e.g., Parts for JDPoint and JDPrism).
    Available options: Parts, Service, Trade
  • Responsibility Center Assignment: specifies the responsibility center which will be assigned to the related dealer number. One responsibility center can cover up to 3 departments (Parts, Service, Trade).
  • JDPoint Alternative Account (JDIN): for JDIN Dealers only and for centralized JDPoint accounts using destination codes for dealer outlets. Only displayed if Area = Parts.
    Enter the Main Dealer No. account.
  • JDPoint Default Destination Code (JDIN): for JDIN Dealers only and for centralized JDPoint accounts using destination codes for dealer outlets. Can only be filled if the JDPoint Alternative Account (JDIN) value is filled.
    Enter the JDPoint destination code matching the responsibility center.

After this setup, the responsibility center is automatically assigned for service items based on the originating sales document and the dealer mapping. Manual assignments are not overwritten.

Purchase orders for Parts using JDPoint now automatically substitute the default Dealer No. value (linked to the responsibility center) with the predefined alternative combination of dealer account + destination code, so that purchase orders are placed under the correct John Deere dealer account without manual intervention or impacting DPMORD/DPMXFER.

[25321] Operator complaint text box added to service wizard

25322

In this feature, the Operator Complaint text box was added to the Service Wizard dialog (above the Fault Description text box) to enter customer complaint details directly, so that the complaint information is automatically included in the newly created service order document. This makes sure that dealers can capture the customer's complaint once during service creation and have it automatically carried into the service order, reducing retyping, avoiding information loss, and improving service accuracy.

[26840] Sending vendor order and serial number to CRM COI for multi-company environments implemented

26279

In this feature, the Vendor Order No. value was integrated into CRM Customer Order Interface (COI) processes for multi-company environments to support automatic transfer of vendor order numbers and serial numbers from John Deere DBS 365 to CRM COI in multi‑company dealer environments. This ensures seamless tracking and referencing of vendor-specific order identifiers across John Deere CRM and John Deere DBS 365, improving transparency, traceability, and operational efficiency:

  • Improved order traceability across systems.
  • Enhanced data consistency between John Deere CRM and John Deere DBS 365.
  • Streamlined multi-company operations with clear vendor references.
  • Better auditability for compliance and reporting.

This is achieved by sending the ManufacturerOrderNo and serialNo tags to the CRM COI. The values are then copied to the Vendor Order No. and Serial No. fields of the related calculation worksheet (only if the fields are not empty) and the Lines FastTab of the purchase order created from the calculation worksheet.

[27753] JD Service 365 app published as desktop app

27754

In this feature, the JD Service 365 app was recompiled to also work on systems running Microsoft Windows, not only on mobile devices running iOS or Android. This enables technicians to access and manage service tasks more flexibly depending on their working environment and devices. The core functionality is the same as in the mobile app. The Mobile Service 365 JD desktop app can be downloaded from the Microsoft Store here.

[28140] [BETA] Parts invoice import improved with MD surcharge import at line level

28141 - 28151 - 28590 - 28592

Important

This functionality is available as a beta version. It is still under evaluation and may have limitations or unexpected behavior.

In this feature, the import logic of MD surcharges/discounts was improved to correctly map them to purchase invoice lines and to improve the accuracy and transparency of John Deere parts pricing in John Deere DBS 365 by correctly calculating and mapping MD surcharges and discounts during invoice import, enabling a more automated and reliable purchase invoice process. This leads to less manual intervention by users as well as better purchase price accuracy for John Deere parts. The specific improvements are outlined in the following:

It is now possible to import the Net Price and Fully Discounted Line Price values from parts receipts into John Deere DBS 365, so that visibility of MD surcharges at line level for purchase orders and parts invoices can be implemented later this yearso that visibility of MD surcharges is given at line level for parts invoices. To achieve this, the value names were added to the Imported Parts Receipt Data table which is filled using the JD Document Integration.

Also, the difference between the Net Price and Fully Discounted Line Price values is calculated to copy it to the parts receipt file and to use when importing the parts invoice. To achieve this, the Surcharge/Discount Amount column was added to warehouse and parts receipt lines. It is hidden and read-only by default and calculated as follows:

Fully Discounted Line Price - (Net Price * Quantity)

If a parts receipt contains multiple lines for one item, John Deere DBS 365 summarizes the values to post them into one warehouse receipt line. The calculations for the Net Price and Fully Discounted Line Price values are also summarized.

In addition, the Pull MD Charges from Receipt Lines checkbox was added to the Parts Invoice Item Charges & Other Invoice Text table as well as the Pull MD from Receipt checkbox (can only be selected if the Pull MD Charges from Receipt Lines checkbox is selected is as well). If the checkbox is selected, the surcharge from the parts receipt is automatically transferred to the parts invoice. To reflect this new information, the Automatic MD Surcharge Assignment column was added to the Lines FastTab of purchase invoices. The checkbox indicates whether the MD surcharge was automatically allocated during the parts receipt process (selected) or not (cleared).

Note

The automatic MD surcharge assignment is skipped, if quantities are different or if the total surcharge amount does not match the differences from the parts receipt.

The Qty. to Assign value in the Lines FastTab of purchase invoices is not split equally anymore. It is now calculated based on the individual line surcharge. Exception: if the total surcharge value from the purchase invoice does not equal the sum of all surcharges from the parts receipt, the Qty. to Assign value is still split equally.

[28248] REMAN part identification added to JD Service 365 app

28250

In this feature, the possibility to easily identify parts eligible for re-manufacturing (Reman) during service operations for service technicians was added to the JD Service 365 app which leads to:

  • Improved visibility of Reman-eligible parts,
  • Streamlined return process for re-manufacturing,
  • Enhanced sustainability and cost-efficiency in service operations.

To achieve this, a green leaf symbol is now shown in the app for parts which have the REMAN field filled in John Deere DBS 365.

[28279] OSI change history view implemented

28281

In this feature, the OSI Change History View feature was implemented to provide transparency into OSI machine configuration and price changes by exposing original, penultimate, and latest option code history in CRM. It empowers admin users with real-time visibility into modifications made by the Order Status Interface (OSI) to orders in John Deere DBS 365. By capturing and displaying a chronological comparison of option codes and their associated dealer net prices (DNP), this feature enables users to actively monitor structural and pricing changes over time, e.g.:

  • Instantly identify what has changed in order configuration and pricing
  • Reactively respond to updates by reviewing highlighted differences
  • Take corrective actions, such as updating the sales order with the latest data

This dynamic view not only enhances transparency and traceability but also supports faster, more informed decision-making in response to OSI-driven changes.

To achieve this, the OSI Change Tracking View table was added to John Deere DBS 365 which can be opened via the Related > Service Item > OSI Change Tracking button in the menu bar of service items, and via the Actions > OSI Change Tracking button in the menu bar of purchase orders and sales orders. The table displays a change history for each order updated by OSI:

  1. Area 1: Original values (option codes and DNP) at the time of the first OSI update.
  2. Area 2: Penultimate changes (from the second-to-last OSI update; only used for reference, thus no color coding).
  3. Area 3: Latest changes (from the most recent OSI update).

Each Area has an Option Code, Description, and DNP value. The Areas 2 and 3 also have the Updated At value showing the exact timestamp. The Line Type column indicates whether the line is a base machine, an option, or a sum. This column is also used for sorting, i.e.: base machine >option >sum.

TIP: A sum of the dealer net price (DNP) will be displayed at the bottom of each column.

The view is generated in two scenarios:

  1. When OSI updates an order for the first time in John Deere DBS 365: On the first OSI update, original values are stored. Each subsequent update appends new change data.
  2. When a purchase order is released: if the tracking view does not exist yet (no OSI update has occurred), John Deere DBS 365 creates tracking entries and fills the Original column with values from the calculation forecast and equipment records at the time of release. This ensures visibility even before the first OSI update.

Lastly, a color coding was implemented as follows:

  • No highlight: If an Option Code value already exists in Area 1 with the same DNP, no highlight is needed.
  • Green highlight: If the Option Code value already exists in Area 1 but the DNP has changed, both the Option Code and DNP values are highlighted in green.
  • Yellow highlight: If the Option Code value is new (i.e., not present in Area 1), it is highlighted in yellow.
  • Red highlight: If an Option Code value from Area 1 was removed and is missing in Area 3, it is highlighted in red.

[29435] Parent-child relationship for CRM EI introduced

29436

In this feature, the parent-child relationship of service items was improved, i.e., when a service item in John Deere DBS 365 is now assigned as a child to another service item, John Deere CRM is automatically updated with the corresponding reference to the parent service item. This reference is a composite key combining the UniqueDealerId and ParentServiceItemDBSId values. This ensures that hierarchical relationships between equipment are consistently reflected in John Deere CRM, improving traceability and coordination. The update is automatically triggered by any change of the Assigned To field and flows one-way from John Deere DBS 365 to John Deere CRM.

This will significantly enhance the data integrity and usability of John Deere CRM equipment records by introducing automated parent-child relationships between service items. For sales admins and service coordinators, this means:

  • Improved Traceability: child service items in John Deere CRM will now carry a direct reference to their parent service items, enabling clearer visibility into equipment hierarchies and dependencies.
  • Operational Efficiency: automatic updates triggered by changes in John Deere DBS 365 reduce manual data entry and the risk of errors, saving time and ensuring consistency across systems.
  • CRM Data Quality: the use of a standardized composite key ensures accurate linkage between John Deere DBS 365 and John Deere CRM records, supporting reliable reporting and analytics.
  • Seamless Integration: the one-way sync from John Deere DBS 365 to John Deere CRM ensures that John Deere CRM always reflects the latest structure without requiring manual reconciliation or back-propagation.

[29471] JDPoint order status usability improved

29127 - 30079

In this feature, the JDPoint order status was improved to be more user-friendly and more in line with general purchase order features. This should avoid data discrepancies between John Deere DBS 365 and JDPoint by making JDPoint order changes immediately visible to the dealer:

  • The Current Status button in the menu bar of the Purchase Lines table was renamed to Retrieve JDPoint Order Status. It also states the new group button for JDPoint actions.
  • The following color coding was implemented for the JDPoint Line Status column in the Purchase Line table:
    • Favorable = green standard/bold
    • Unfavorable = red bold/italics
    • Ambiguous = yellow standard
    • Strong = black bold
  • The JDPoint Line Changes field does now reflect the count for the specific purchase lines based on the Document No. value instead of the Part No. value.
  • Users are now warned about any JDPoint line changes >
    0 once the purchase order is transferred to JDPoint. When clicking on the digit in the JDPoint Line Changes column, when manually retrieving the JDPoint order status, or when submitting an order to JDPoint, a message is displayed notifying the user about the change and related consequences.

[29636] OSI process extended to update calculation worksheets

29472

In this feature, the Order Status Interface process was extended, so that not only the related calculation worksheet template is updated but also the service item calculation worksheet, if available.

[29657] Price visibility setup per user for Parts ADVISOR implemented

29387 - 29825

In this feature, setting up the Parts ADVISOR price visibility for different users was implemented, so that unit prices and/or unit costs can be hidden, if needed, and to enable dealers to control parts price visibility per user in Parts ADVISOR, ensuring prices are only visible to authorized roles.

To achieve this, the Parts ADVISOR Prices Visibility field was added to the User Setup Card page. Users can then select one of the following options:

  • Unit Price + Cost: default setting Shows all prices to Parts ADVISOR users.
  • Unit Price Only: Shows only the Unit Price value to Parts ADVISOR users.
  • No Prices: Hides all prices from Parts ADVISOR users.

As a small improvement, the Parts ADVISOR actions Import Parts ADVISOR Picklist and Import Shopping Basket were merged into one action group in the menu bar of sales orders, sales quotes, service orders, service quotes, and purchase orders. The Import Shopping Basket button is now available when clicking on the Import Parts ADVISOR Picklist button.

[29682] JDMINT Interface support for 'Sold to' and 'Ship to' fields implemented

30123

In this feature, the JDMINT Interface was improved by supporting the Sold to and Ship to fields, so that delivery expectations can be passed seamlessly to downstream systems. This is leading to the following benefits:

  • Double work for admins eliminated: admins needed to manually re-enter delivery dates in multiple systems, which was time-consuming and prone to error.
  • Simplified process: the automatic transfer of delivery dates reduces complexity and improves workflow efficiency.
  • More accurate data: passing the date directly from John Deere CRM or John Deere DBS 365 to JDMINT minimizes human error and guarantees consistency across systems.
  • Improved customer experience: Accurate delivery dates help meet customer expectations and reduce delays.

[30041] Catalog update speed increased

30043

In this feature, the update speed for John Deere catalog imports was massively increased to save time. Many catalog update tasks do now take only half the time compared to before.

[30196] PLP calculation for CRM improved

30185

Before, the price list price (PLP) sent to John Deere CRM via the CRM Equipment Interface (EI) was calculated as a sum of the values Price List Price (PLP) + List Price Configuration Options from the calculation worksheet. This worked fine for configurator templates but led to inconsistent pricing data in John Deere CRM and incorrect totals for manual templates as the Price List Price (PLP) value is often 0.

In this feature, the fallback logic to use the List Price value was introduced for cases where Price List Price (PLP) = 0. This ensures accurate PLP totals for both configurator and manual templates.

[30198] Restricting incentive transmission via CRM EI implemented

30199

In this feature, the possibility to send incentives from purchase orders or calculation worksheets was added to the CRM Equipment Interface (EI) setup which allows dealers to control whether incentives are included in the data sent to John Deere CRM. This:

  • helps dealers to decide whether incentives should be visible to sales representatives in John Deere CRM, aligning with their internal pricing policies and confidentiality requirements.
  • helps prevent unintended disclosure of sensitive discount structures, ensuring compliance with dealer-specific agreements.
  • reduces confusion for sales representatives by showing only relevant pricing information, leading to cleaner quotes and better customer communication.
  • eliminates the need for manual data adjustments or workarounds, saving time for admins and reducing risk of errors.

To set this configuration up, proceed as follows:

  1. Open the Interface List table in John Deere DBS 365 and select the JDCRMEQUIPMENT entry.
  2. In the Parameters FastTab, select one of the following values for the IncentivesTransfer parameter:
    1. 1: default value incentives are sent to John Deere CRM.
    2. 0: incentives are removed from CRM data and not sent to John Deere CRM.
  3. Close the pages. Your setting is applied to all upcoming EI integration records.

[30222] Definition of vendors with same VAT ID for wholegood and parts invoices implemented

30223

In this feature, the possibility to import John Deere wholegood and parts invoices for dealers with multiple VAT IDs for John Deere vendors was implemented for dealers. This should avoid manual purchase invoice creation and lead to less error handling when comparing the imported purchase invoice for wholegoods and parts with the vendors in John Deere DBS 365.

To achieve this, the John Deere Vendor Setup table was added to the Mapping Setup FastTab of the JD Document Integration Interface Card. In this table, for each document type (wholegoods or parts invoice), the VAT ID and corresponding vendor number can be defined. Each line in the table must be filled completely, otherwise an error message will be displayed.

Important

The JD Document Integration is deactivated when applying this release. Please make sure to fill the table completely before manually reactivating the integration.

[30365] Search of warranty claim source document in import process optimized

30359 (Ticket: 50703)

In this feature, the source document number search for warranty claims was optimized to ensure warranty claims (especially ZSPA Special Allowance claims) are imported correctly and consistently by using the right logic, reducing errors and rework in the warranty process. Before, when importing warranty notes, John Deere DBS 365 searched for the Source Order No. value in the General FastTab of warranty claims instead of the Work Order value in the warranty claim details (WO tag in the XML file), which would be required for special allowance claims (ZSPA).

[30444] PMManage calculation of total parts sales last 12 and total parts sales prior 12 values improved

30407

In this feature, the PMManage calculation was improved to be more reliable. Before, the Total Parts Sales Last 12 and Total Parts Sales Prior 12 values were calculated building an average, but the total amount of the 12-month period is needed. This was achieved in this feature.

[30445] Automatic filling of 'Base Code' field improved

28798

In this feature, automatic filling of the Base Code field in calculation worksheets and calculation worksheet templates was implemented to improve the data quality during manual creation of the calculation worksheet. When now selecting a model in the General FastTab, the Base Code field is automatically filled with the latest base machine code (BMC) based on the product hierarchy.

If there is no associated BMC for the model, the field is left blank. If the user manually fills or overrides the auto-filled Base Code, John Deere DBS 365 will not change this value.

[30591] Line break support added for CRM Integration notes

30592

In this feature, support for line breaks in CRM Integration notes was added, so that line breaks added in John Deere DBS 365 are also correctly reflected in John Deere CRM. The new line sequence (\n) is now automatically added to notes, if a line break is available, so that John Deere CRM can correctly interpret it and shows the same layout as intended by the John Deere DBS 365 user.

[30654] Estimated time of arrival feature added to Transport Status Interface

30655

In this feature, a dedicated field to show the estimated time of arrival was added to purchase orders, integrated with the Transport Status Interface. It ensures that delivery timelines are visible and actionable for sales and purchasing teams leading to:

  • Improved Customer Communication: sales teams can provide accurate delivery dates, increasing customer trust.
  • Operational Efficiency: reduces uncertainty and enables better planning for logistics and resource allocation.
  • Flexibility: allows manual adjustments while supporting automated updates from transport data.

To achieve this, the ETA field (estimated time of arrival) was added to the General FastTab of the Purchase Order page which is automatically filled with the latest date of service item delivery upon transport status updates.

Tip

It is also possible to manually enter or change the ETA value. John Deere DBS 365 will not automatically overwrite a manually entered value.

[30887] John Deere warranty functionalities improved

30886 - 30888 (Ticket: 50703)

In this feature, the John Deere warranty functionality was improved as follows:

The warranty claim status is now retrieved via the Work Order value from the John Deere Warranty Claim Details FastTab, not via the Source Order No. from the General FastTab of the warranty claim anymore.

The Warranty Claim Segment value in the John Deere Warranty Claim Details FastTab is now automatically set to 1 when users manually create a warranty claim without a related service order, so that the warranty claim is initialized correctly and avoids incorrect default values that lead to processing or reporting issues.

[30922] JD Document Integration import improved

30921 - 30923

In this feature, the JD Document Integration import functionality was extended as follows:

Incoterms from wholegood invoice and parts invoice XML files are now supported and processed in the right John Deere DBS 365 area, so that the Shipment Method Code field can be filled automatically. To accommodate this change, several captions needed to be updated:

  • Imp. Parts Inv. Disc./Sur. table:
    • Discounts/Surcharges/Core Values FastTab > Discounts/Surcharges/Core Values/Incoterms
  • Parts Invoice Item Charge table:
    • Surcharge Usage > Use Indicator Mapping for Surcharges
    • Discount/Surcharge Indicator > Discount/Surcharge Indicator or Incoterm
    • Item Charge > Item Charge Code

In addition, the Shipment Method Code field was added to the Parts Invoice Item Charge table which defines the shipment method code that should be used in the purchase invoice.

Note

Item Charge Code and Shipment Method Code cannot be used at the same time.

Payment terms are now assigned per service order type, so that the Due Date value in imported purchase invoices is calculated correctly to comply with John Deere's payment terms which are based on the Order Type value, not on the Due Date from the Vendor Card page.

To achieve this, the Payment Terms Code field was added to the Order Type table. This field defines the code used to calculate the payment due date. If filled, the selected payment terms code is used in purchase documents instead of the vendor data. The field is only displayed, if Deere Trading Type = COMMERCIAL on the John Deere Setup page.

[31054] Operator complaints added to service order creation process in JD Service 365 app

29591

In this feature, the possibility to add operator complaints when creating a new service order in the JD Service 365 app was implemented. It is an optional field and placed above the fault description. This should ensure that operator complaints are captured early and consistently during service order creation in JD Service 365 App, improving service quality and information flow from intake to execution.

[31078] Manually adding missing maintenance contract numbers to service notifications implemented

31077 - 31195

In this feature, the possibility to retrospectively import missing maintenance contract numbers into SVAP service notifications was implemented to ensure service notifications are correctly linked to maintenance contracts, even when contract numbers were missing at creation time, supporting accurate service processing, billing, and reporting.

To achieve this, the Actions > Get Maintenance Contract No. button was added to the menu bar of the Service Notifications table. After clicking on this button, the Agreement Business Key of the selected service notification is read, and a matching Maintenance Contract No. is searched. If available, the Maintenance Contract No. is filled for the service notification, and the Contract Status field is cleared.

In addition, an issue was fixed where in an Event Business Key error message, the Agreement Business Key was falsely displayed.

[31262] Technical improvements implemented

31264

In this feature, several technical improvements under the hood were implemented to create a better user experience and a more stable system.

Improvements

[26555] Changing the vendor shipment number in posted purchase receipts implemented

In this improvement, the possibility to change the Vendor Shipment No. value in posted purchase receipts was implemented, so that the related parts invoice can be reconciled with this posted purchase receipt. This improvement is needed to accommodate for cases where dealers are unable to follow the standard process that automatically creates purchase receipts with the correct 9-digit packlist number.

Now, a manual change of the posted purchase receipt is possible via the Home > Change Vendor Shipment No. button in the menu bar of the Posted Whse. Receipt page. After changing the value, the posted warehouse receipt line and header, general ledger entry, item ledger entry, and value entry records are updated with the vendor shipment number as well.

[30289] B&P session timeout extended

The session timeout period for Build & Price was extended from 2 minutes to 10 minutes what should lead to less disruptions.

[30376] Packlist number handling for commercial parts invoices improved

This update introduces automatic import and matching of multiple packlist numbers associated with a single order number in warehouse receipts, reducing errors caused by manual processing. Additionally, you can now manually add packlist numbers to purchase order lines using the Add Packlist No. button, ensuring that commercial invoices can be created without any issues.

[30593] CRM COI integration record deletion clarified

The tooltip of the Delete button in CRM COI integration records was updated to: Deletes the current CRM customer order record and all related records. to make the consequences clearer.

[30664] Surcharge indicator import for parts invoices improved

The Surcharge Indicator field was not filled with the value from the XML file, so that commercial parts invoice surcharges could not be correctly assigned to affected lines. This process was improved.

[30868] Maximum character length of Parts ADVISOR picklist comments extended

The maximum character length of model names sent via Parts ADVISOR was extended from 50 to 150 characters, i.e. the Comment 1 and Comment 2 columns in the Parts ADVISOR Picklists table can now show up to 150 characters.

[31000] RPM functionality optimized

The RPM functionality was improved to create more reliable DPMEXT data.

First, the RPMProcessingType parameter was added to the Parameters FastTab of the DPMEXT Interface Card page. This parameter indicates whether the RPM records will be processed as combined record only (Combined RPM Record Processing value) or whether the processing logic allows separated processing and recalculation of the RPM data (Separated RPM Record Processing value).

Second, the Combined Recalc. of RPM Records column was added to the John Deere RPM Primary Data table. When the checkbox is selected, the RPM records should be recalculated because of data changes in John Deere DBS 365. The data of the primary and initialization record combined is recalculated, and the Starting Date for Init Record Data Recalculation date field is ignored.

Lastly, the RPM buffer processing and RPM table recalculation were also streamlined under the hood based on the RPMProcessingType parameter setup.

[31091] PMManage parts return value export improved

PMManage export files are now sent with the correct data formatting when the result for returns is a negative value, i.e., a minus sign is attached at the end of the 9-digit value.

[31288] Over-receipt tolerance % increased

The Over-Receipt Tolerance % value in the Over-Receipt Codes table can now exceed 100% (up to 10,000%). This can be useful if, by mistake, more parts are received from John Deere. Users can thus receive those parts without any problems in John Deere DBS 365.

[31385] CRM CDI synchronization made more flexible

It is now possible to customize the values in the Customer Classifications table to use values different from John Deere's presets and still be able to send them to John Deere CRM without any issues. This is achieved by a special mapping event.

Also, when synchronizing data from John Deere CRM using CRM CDI, users can now opt in or out to apply specific data so that no manually maintained data is lost or overwritten when clicking on the Create/Update Customer button in CDI integration records.

[31487] Delay between API calls in JDPoint order status automation implemented

Ticket: 52275

The MinRequestDelayInSec parameter was added to the Parameters FastTab of the JDPoint Interface to add a delay between JDPoint Order Status Automation job queue calls, so that no issues or timeouts occur. The minimum and default value is 30 seconds, but you can define a longer period, if needed.

[31555] Ignoring line discounts for parts invoice creation implemented

It is now possible to create parts invoices that contain a line discount to avoid manual purchase invoice creation. Before, the invoice amount check took any line discount into account, so that an import error occurred.

[31564] Flexible packlist number entering implemented

It is now possible to enter any digit into the Packlist No. field in the staging table, so that a related receipt with a Vendor Shipment No. with a character count other than 9 or 14 digits can be matched. When entering a value with ≠14 characters, the Packlist Sequence No. field is cleared.