RamBase Cloud ERP release info - week 22

The following updates have been added to RamBase Cloud ERP:



Sales


Improved Shipping advice (CSA) closure process without dummy invoices 

Classification: USEFUL



We are improving the Shipping advice (CSA) closure process in RamBase by removing the need for automatically generated “dummy” Sales invoices (CIN) in specific non-billable scenarios.

 

Previously, when material was consumed or shipped through Shipping advice (CSA) and the customer should not be invoiced directly, RamBase created a dummy Sales invoices (CIN) to close the Shipping advice (CSA) to Status 9 - Processed. Typical examples included Fixed Price orders and internal Project orders (POD).

 

These dummy invoices were not posted to the customer account or the general ledger. Their sole purpose was to complete the Shipping advice (CSA) process and update the status.

 

With this improvement, Shipping advices (CSA) will now be closed directly to Status 9 - Processed without generating a dummy Sales invoices (CIN).

 

This enhancement simplifies the workflow, reduces unnecessary invoice records, and provides a cleaner and more efficient process for handling non-billable material consumption and shipments.



Production


Additional resource and time details in Production work order progress (PWOPROG)

Classification: USEFUL


The Production work order progress (PWOPROG) application has been updated to include new informational columns, giving users better insight into resource allocation and logged time. Previously, users reviewing the progress of a work order lacked direct visibility into the specific resources assigned to operations, as well as the total accrued man-hours within this main view.  

With this enhancement, production planners and managers can more easily track operational efficiency and resource utilization directly in their daily workflow without needing to dig into deeper levels or navigate to other applications.  


What’s new?

The following information has been added to the Production work order progress (PWOPROG) view:

  • Assigned resources: You can now see exactly which resource is assigned to the production operations.

  • Accrued man-hours: Accrued man-hours have been added to the time information, providing a clearer overview of the actual time spent on specific tasks



Improved line highlighting in Production work order tree (PWOTREE) and Production work order progress (PWOPROG)

Classification: USEFUL


The Production work order tree (PWOTREE) and Production work order progress (PWOPROG) applications have been updated to include line highlighting functionality, helping users maintain focus during detailed inspections.

Previously, when users navigated away from the Production work order tree (PWOTREE) or Production work order progress (PWOPROG) applications to inspect details of sub work orders and then returned, the original line was not highlighted. This made it difficult for users to track their exact location within the tree structure, disrupting the workflow when reviewing complex orders. With this update, a line selection and highlighting feature has been implemented. Now, when a user inspects a sub-level and returns to the main list, the selected line remains highlighted.


Improved financial visibility in the Order overview (OOV) application

Classification: USEFUL


The Order overview (OOV) application has been updated to include key financial data, providing better visibility of amounts and deviating profits on sales order lines.

 

Previously, users lacked direct access to specific financial metrics when reviewing items in the Order overview (OOV), requiring extra steps to gather this essential information.

 

With this update, you can now add specific fields from the Sales order item (COAITEM) as optional columns directly in the Order overview (OOV). This improvement allows for a quicker and more comprehensive review of sales order profitability and amounts without leaving the application.

 

The following optional columns are now available:

  • Currency

  • Gross amount

  • Net amount

  • Landed cost

  • Gross margin (pct)


Enhanced visibility and filtering options in Production work order menu (PWOMENU)

Classification: USEFUL


The Production work order menu (PWOMENU) and Production work order tree (PWOTREE) applications have been updated with new optional columns and filtering capabilities to provide better visibility and efficiency for production planners.

Previously, the Production work order menu (PWOMENU) only displayed the remaining quantity for Production work orders (PWO), making it difficult to view historical production amounts. Additionally, checking important user notifications or accessing progress details required navigating away from the main overview.

With this update, planners gain quick access to essential production data directly within their daily follow-up view, streamlining their workflow and reducing the need to switch between applications.

The following features and optional columns have been added:

  • Original Production work orders (PWO) quantity: Added as a new column in both Production work order menu (PWOMENU) and Production work order tree (PWOTREE) placed in front of the remaining quantity) to easily see the originally planned or produced amounts.

  • Revision filtering: A new Revision field is now available in the Production work order menu (PWOMENU) filter builder to search for specific product revisions.

  • Direct inspection links: Optional columns have been added in Production work order menu (PWOMENU) to quickly inspect the Production work order tree (PWOTREE) and Production work order progress (PWOPROG).

  • User notifications: A new optional column in Production work order menu (PWOMENU) indicates if important user notifications exist on a Production work order (PWO), with the ability to view the notification details directly via hover-over or a pop-up.



New Blocked for release option for Production work orders (PWO) 

Classification: USEFUL


We are introducing a new Blocked for release functionality for Production work orders (PWO) to give planners better control over the production preparation process.   

 

Work orders are needed to be confirmed to be included in resource capacity planning and material optimization processes. However, doing so would cause them to appear as ready for release (reaching status 3 or 4), even if they still required further material or parts planning. This created a risk of work orders being released to production ahead of schedule. With this update, production planners can safely include orders in their capacity and material planning workflows while explicitly blocking them from being released until all preparations are  completed. What’s new?

 

The following capabilities have been added to support this workflow:

 

Automated or manual blocking: A new system setting, New Production work order (PWO) is blocked for release by default, can automatically apply the block to new work orders upon creation. Users with appropriate permissions can also manually manage this using the new Block release of production work order and Unblock release of Production work orders (PWO)  options in the Production work order (PWO) context menu (CMI) under Actions and operations.

 

Clear system indicators: When a Production work order (PWO) is blocked, a Blocked for release message is displayed directly on the order, and the Release button is deactivated. Additionally, a specific icon is now visible in the Info column within the Production work order menu (PWOMENU).

 

Visibility in planning: The blocked status is clearly indicated in the Resource planning (RPLAN) application, appearing in both the operation hover-over pop-ups and the detailed operation view. In addition, pop-ups in the Resource planner display information about work orders which are on hold or have high priority.

 

Inheritance rules: The Blocked for release status is strictly inherited when splitting a Production work order (PWO), including subproductions that were automatically split. However, work orders created specifically for rework will not inherit the blocked flag.



Updated information regarding product and product structure version numbers 

Classification: USEFUL


Several applications have been updated with information regarding the product version number and the produced product version number. The product version number reflects the version of the Product (ART) whereas the produced product version reflects the version of the Production structure (KITDOC). This information can be found in the following applications:

 

  • In the Product (ART) application as a new field named Version in the Product area.

  • In the Product (ART) application as a new optional column named Produced column version in the Production work orders tab under Procurement.

  • In the Product (ART) application as a new optional column in REPORT/107535 from the Available stock quantity field in the Product area.

  • In the Production work orders (PWO) application as two new optional columns named Product version and Produced product version.

  • Via the Production work order details (PWOD) application from the Structure link in the Links area.

  • In the Orders overview (OOV) application as two new optional columns named Product version and Produced product version.


This update provides valuable information about both products and product structures to ensure clarity and control over the production process.



Finance


Additional landed cost support for class:X products and non-stock Sales credit notes items (CCNITEMS) 

Classification: USEFUL


A new update expands the handling of purchase prices and landed costs for additional product classes and item scenarios.

 

Previously, the Purchase price field under the Landed cost tab on Sales invoice item (CINITEM) was only available for class:X products. With this update, the functionality is now extended to include all non-stock products, providing greater flexibility for customers who use different item structures for purchasing and sales processes.

 

This enhancement aligns with common customer workflows where:

  • Type = X is used for purchasing
  • Type = V is used for sales

By extending the functionality to include all non-stock products, users can now maintain landed cost and purchase price information consistently across both purchasing and sales item structures.

 

In addition, the Purchase price field can now be edited for Sales credit notes items (CCNITEMS) in Status 1 when the item is marked as non stock.

 

These improvements provide increased flexibility and simplify cost handling for non-stock and value-added product scenarios.



Extended useful life support for Fixed assets (FAR) 

Classification: USEFUL



We are introducing support for extending the useful life of existing fixed assets in the Fixed asset (FAR) register in RamBase.

 

This enhancement makes it possible to register improvements or upgrades to a fixed asset and recalculate future depreciation based on an updated useful life. The functionality is designed to support common accounting practices where a major upgrade extends the service life, capacity, or quality of an asset.

 

Previously, customers who needed to handle fixed asset lifetime extensions had to calculate depreciation adjustments outside RamBase and post them manually using General ledger posting (ATR) entries. RamBase did not provide a native way to revise the depreciation schedule for an existing asset after a capitalized improvement.

 

With this improvement, users can:

  • Register a capitalized improvement on an existing fixed asset
  • Extend the remaining or total useful life of the asset
  • Automatically recalculate future depreciation prospectively
  • Keep previous depreciation postings unchanged
  • Maintain a complete audit trail with supporting documentation

The updated depreciation schedule is calculated based on the remaining book value, the capitalized improvement amount, and the revised useful life. Existing depreciation methods remain unchanged.

 

This functionality supports accounting practices used in countries including Norway, Poland, Sweden, and the UK, while tax depreciation handling remains outside the scope of RamBase.

 

The enhancement is particularly important for customers with reporting requirements connected to Polish JPK and KSeF regulations, where accurate handling of fixed asset improvements and documentation is required.

 

This improvement provides a more efficient and compliant way to manage fixed asset upgrades directly within RamBase, reducing the need for manual calculations and external processes.