What's New in Version 8.03 March 2025 Release
Theme Update
The new-look theme will replace the original theme in the coming months. More information will be provided in the next release.
Resolved Issues
The following issues have been fixed in this release:
| ID | Description |
|---|---|
| DEV-192663 | When running Planning & Scheduling for a non-standard (NS) part in a Sales Order without operations, the ‘No Operations’ tab in the Plan Audit incorrectly displays Material Availability, Supply Demand by Part, and Interactive Planning by Part, instead of properly redirecting to Interactive Planning by SO, causing confusion in planning. |
| DEV-199946 | The CTP (Capable-to-Promise) screen does not refresh properly when selecting a new part after running a CTP analysis for a different part. The previous CTP results (including dates and quantities) remain visible, causing confusion. |
| DEV-239056 | Parts in inspection locations without a pass disposition are incorrectly appearing as available to ship in the Shipping Queue, potentially allowing unapproved parts to be shipped. |
| DEV-236536 | Users with ‘View and Add’ permissions for Quotes, Sales Orders (SO), Purchase Orders (PO), and Receipts (RECV) are unable to add line items because the system considers this action an edit to the document. As a result, the expected functionality is blocked unless full Edit permissions are granted. |
| DEV-240966 | Users with only View permissions in SFMWC (Shop Floor Work Center) can still issue Job Orders, bypassing the expected permission restrictions that should prevent issuance without Edit permissions. |
| DEV-242827 | The ‘0’ key on the numeric keypad does not function when entering values in number-only fields, requiring users to manually click ‘0’ on the on-screen calculator. However, the ‘0’ key above the keyboard works correctly. |
| DEV-187416 | When changing a Purchase Order (PO) vendor from one with jurisdiction to one without, the system does not automatically uncheck the taxable box for each line item, requiring manual updates. In contrast, previous versions either displayed an error message or handled the change correctly. |
| DEV-253243 | Historical invoices with an apostrophe in the AR invoice number fail to synchronize with CRM due to improper handling of the single quote. |
| DEV-248016 | Adding the Delivery Commitment column to the Sales Order (SO) Item grid causes a server error when the user first accesses the Items tab or attempts to sort the column. Occasionally, this leads to display inconsistencies, such as gaps in the SO Release grid for multi-release items. |
| DEV-254755 | Users with view-only permissions for FIOV, PROV, and SAOV can successfully access PROV and SAOV. However, FIOV displays an insufficient rights error, requiring administrators to grant higher-level permissions, which unintentionally provides access to additional screens. |
| DEV-255981 | When navigating from a Sales Order (SO) screen to Item Details and then returning, some fields in the Accessories tab (e.g., Attachments, Activity, Quality, Customize) disappear from the More Actions panel, requiring a manual screen refresh to restore their visibility. |
| DEV-256650 | The Memo field on the Additional Info tab of the Accounts (CUST) screen no longer automatically populates the Customer Notes field on the Sales Order (SO) Additional Info tab, resulting in lost functionality from previous versions and requiring manual lookup. |
| DEV-258670 | In JODBOM, the column chooser does not include all fields available in the Data Dictionary, preventing users from adding necessary columns, such as Sub-Job. This results in lost functionality and additional steps to retrieve critical information. |
| DEV-259059 | AP payments incorrectly appear as cash receipts in Explorer and Browse views, causing data integrity concerns and confusion. Users see payments that should not be classified as receipts and are unable to search for them accurately. |
| DEV-259056 | Users are unable to create a Purchase Order (PO) from the PLNPOQ screen for a part with demand, as the system throws an error stating, ‘Operation Number is not found in Detail Routing,’ preventing them from fulfilling procurement requirements. |
| DEV-120107 | The Total BOM Cost field is missing from SODBOM and QTDBOM, requiring users to manually calculate component costs or switch to the Price Summary, which causes inefficiencies compared to previous versions where this value was displayed in the BOM grid. |
| DEV-255641 | The Labor Errors widget does not provide a way to filter out inactive employees with unresolved errors, causing outdated records to remain visible even though they will never be corrected. This leads to unnecessary data clutter. |
| DEV-259745 | Events/Actions (E/A) processing fails with an ‘index out of bounds’ error, preventing events from firing correctly. This occurs because the validation logic incorrectly applies queries to SHMAST instead of the appropriate table (e.g., POMAST), impacting automated notifications and actions. |
| DEV-260855 | When generating an EFT batch for a newly created vendor, the system successfully creates the EFT batch file and records it in APDIST. However, RPAPTG and RPGLTL do not pick up the records, leaving the invoice in an Unpaid status and preventing the expected GL postings. |
| DEV-261052 | Attempting to create an ARINV credit memo from an RMA with multiple items fails with the error message: ‘Unable to create Credit Memo for RMA No. xxxxxx,’ preventing users from efficiently processing multi-item RMAs. |
| DEV-261572 | The data stored as popup values did not honor the selection to display either the stored value or the description and always displayed the stored value. |
| DEV-262922 | EFT batch postings do not appear in the RPAPTG report when using a manually defined bank ID sequence. However, they work correctly with automatic sequencing, preventing accurate AP module reconciliation. |
| DEV-264474 | The Quantity Available and Used in Operation fields in SODBOM are not updating correctly. Additionally, expanding child components causes delays, impacting users’ ability to retrieve accurate BOM data efficiently. |