Release Notes October 2025

Release Note for ERP Software – Version  ERP7 1.1534.19

Release Date: Oct 01, 2025

We’re thrilled to introduce version 1.1534.19, delivering new features, enhancements, and bug fixes for a streamlined user experience in ERP Software!

Manufacturing Enhancements

1. BOM Deletion Controls

Before:
Users were able to delete the BOM record even if a Manufacturing Order (MO) existed in Draft or In progress status for the same version.

After:
Now, deletion of a BOM is restricted if there’s an associated MO in Draft or In progress status — both from the MO Product Config screen and at the record level.

2. WIP Link Deletion Controls

Before:
WIP links could be deleted even if related MOs were still open (Draft/In Progress).

After:
A validation now prevents WIP Link deletion whenever there’s an MO in Draft or In Progress for that version. Deletion is restricted both from the MO Product Config screen and at the record level.

3. Build Screen Validation

Before:
It was possible to modify or commit inventory for MRP fields even if the consumption quantities were incorrect.

After:
MRP fields are now read-only on the Build screen, and a validation ensures that inventory cannot be committed unless the consumption quantity matches the required MRP quantities.

4. WIP & WIP Flow Deletion Restriction

Before:
Users could delete WIP or WIP Flow records even when active MOs existed.

After:
System now prevents deletion of both WIP and WIP Flow records if any MO is linked or active.

5.New Functionality – MRP Creation After MO Scheduling

Before:
Previously, once an MO was scheduled, users were unable to add new MRPs for that version. Any new product requirement discovered later required manual adjustments or re-creation of the MO.

After:
With this release, users can now create new MRPs even after the MO is scheduled.

• The newly added MRP will automatically include its corresponding Bill of Materials (BOM).
• On re-scheduling the same MO, the system will recognize and include these newly added MRPs seamlessly in the process.
• This provides greater flexibility in handling late-stage product requirements or engineering updates without disrupting existing MOs

Kit Product Logic Enhancements

1. Manual Logistics Restriction on Exploded Products

Before:
Users could proceed with manual logistics creation even after the Order Product and MRP were exploded, leading to duplicate reservations.

After:
System now blocks manual logistic creation if the Order Product and MRP are already exploded.

2. Prevent Explode After Manual Logistics Creation

Before:
Users could still explode Order Products even after manual logistics were already created, leading to inconsistencies.

After:
Once a manual logistic is created, the Explode option for the same Order Product is disabled.

1. PO + Logistic (Manage PO and Record Level)

1. PO Line Item Modification

Before:
Users could not modify PO line items from the record page, and changes to Quantity, Unit Price, or Tax Rate were not reflected automatically in PO, Line Items, or related Stock Inward Line Items. Dimension records were also not updated.

After:
Users are now allowed to modify PO line items (Quantity, Unit Price, Tax Rate) at the record level, and the system automatically updates calculations at both PO and Line-Item levels.

• If a POLI (Purchase Order Line Item) has already been received, unit price changes will reflect in Stock Inward Line Items.
  
• Allocation amounts and Dimension records are now updated accordingly.

2. POLI Quantity Reduction Restriction

Before:
Users could reduce the POLI Quantity manually or from Manage PO even if the complete line item quantity had already been received, potentially causing inconsistencies in inventory and related records.

After:
If the complete line item quantity has been received, users are no longer allowed to reduce the POLI Quantity, either manually or from Manage PO.

3. POLI Quantity Modification Before Logistic Received

Before:
If a Logistic was created but not yet received, users were unable to decrease the POLI Quantity from the record level or Manage PO, causing inconsistencies in the linked Logistic Line Items.

After:
When a Logistic is created but not received, users are allowed to modify (increase or decrease) the POLI Quantity at both record level and Manage PO. Changes are automatically reflected in the associated Logistic Line Items.

4. POLI Deletion After Logistic Received

Before:
Users could delete POLI from the record level even after the associated Logistic was created and received, which could cause inconsistencies.

After:
Once the Logistic is created and received, users are not allowed to delete the POLI from the record level. This validation is also enforced in Manage PO.

5. Logistic and Logistic Line Item Deletion Restriction

Before:
Users could delete Logistic and its Line Items from the record page even after the items were received, leading to data inconsistencies.

After:
Once items are received, Logistic and its Line Items cannot be deleted from the record page. Validation has been implemented to enforce this restriction.

2. PO + Bill (Manage PO and Record Level)#

PO and POLI Deletion Restriction (PO Only, No Logistic)

Before:
Users were able to delete POLI and PO records from both the record page and Manage PO even when a Bill existed, which could lead to inconsistencies in billing.

After:
Users cannot delete POLI or PO records when a Bill is created. Validation is enforced at the record level and in Manage PO.

2. Restrict Bill Deletion When Posted

Before:
Posted Bills and their Line Items could be deleted.

After:
Deletion of Bill and Bill Line Items is now restricted once the Bill is posted.

3. PO Updates Reflecting on Bill When Not Matched

Before:
If a PO existed and a Bill was created against it, changes made to the PO’s quantity or unit price did not reflect on the Bill or Bill Line Items. This caused inconsistencies, even when the Bill was not matched.

After:
If a Bill exists against a PO and the Bill is not matched, any changes to the PO’s quantity, unit price, or tax are now automatically reflected on the Bill and Bill Line Items. This ensures that the PO and Bill remain consistent until the Bill is matched.

4. Bill and Bill Line Item Deletion Restriction When Debit Note Exists

Before:
Users could delete Bills and Bill Line Items even if a Debit Note had already been created for the same PO. This caused inconsistencies in accounting and records.

After:
Once a Debit Note is created, deletion of the Bill and Bill Line Items is restricted both at the record level and from Manage PO. This ensures data integrity and prevents accidental removal of critical financial records.

5. Bill Quantity Update Restriction After Posting

Before:
Users could modify the POLI (Purchase Order Line Item) quantity even after the Bill was posted, causing inconsistencies between PO, Bill, and Stock records.

After:
Once a Bill is posted, any changes to the POLI quantity are restricted at both the record level and from Manage PO, ensuring data consistency and preventing accidental modifications.

6. Bill Creation Quantity Validation

Before:
Users could create a Bill with a quantity greater than the corresponding PO line-item quantity, leading to mismatched records and potential accounting errors.

After:
The system now restricts Bill creation if the Bill quantity exceeds the PO line-item quantity. This validation is enforced at both the record level and during Bill creation, ensuring data accuracy.

7. Restrict Bill Changes When Posted

Before:
Users could update POLI quantities even after Bill was posted.

After:
System now restricts updates to POLI when the Bill is posted.

8. Restrict Bill Creation When Quantity Exceeds PO Quantity

Before:
Bills could be created with quantities exceeding PO quantities.

After:
Validation added to restrict Bill creation if total billed quantity exceeds PO line-item quantity.

Multiple Bills on Same PO

9. Multiple Bills on Same PO – Quantity Restriction

Before:
Users could create multiple Bills for the same PO, and modify Bill line-item quantities either from the record page or the Create Bill page, potentially exceeding the PO line-item quantity.

After:
The system now restricts any modification to Bill line-item quantities so that the total does not exceed the corresponding PO line-item quantity. This applies both from the record page and during Bill creation. 

10. Multiple Bills on Same PO – PO Update Restriction

Before:
Users could update a PO even if multiple Bills were already created against it, which could cause inconsistencies in quantities and amounts.

After:
The system now prevents any updates to a PO when multiple Bills exist for that PO. This validation ensures data integrity across PO and associated Bills.

Invoice and Payment Restrictions

11. Invoice Posted – No Changes Allowed

Before:
Users could modify posted invoices or their line items, leading to inconsistencies in accounting and reporting.
After:
Once an invoice is posted, no changes are allowed on the invoice or its line items fields like quantity, unit price.

12. Invoice Deletion Restriction When Payment is Made

Before:
Users could delete an invoice even after payment was made, causing ledger and reporting discrepancies.

After:
Invoices cannot be deleted if payment has been made. A standard alert notifies users when deletion is attempted. 

13. Payments Not Depletable When Posted

Before:
Posted payments could be deleted, affecting accounting integrity.

After:
System prevents deletion of posted payments. 

14. Approved Voucher – No Changes Allowed

Before:
Approved vouchers could be edited, leading to discrepancies in accounting and audit trails.

After:
Changes on approved vouchers are restricted.

For support, contact us at support@axolt.com.