The following updates have been added to RamBase Cloud ERP:
Production
Automatic locking of Production work order (PWO) created for Sales order item (COAITEM)
Classification: USEFUL
When manufacturing to order, a Production work order (PWO) will in most cases, be created for one single Sales order item (COAITEM).
Today, there is no automatic locking of the link between the Sales order item (COAITEM) and the created Production work order (PWO), and it’s potential sub Production work order (PWO).
This is not optimal as there is a risk of relinking the Production work orders (PWO) to other needs etc.
To mitigate this, we are now adding an automatic Stock assignment (SAR) locking of the link between the Sales order item (COAITEM) and the Production work order (PWO), and it’s potential sub Production work order(s) (PWO).
The new locking is activated in the following scenarios:
Creating a Production work order (PWO) in the Production planning (PRODPLAN) application via the:
Pending by Order tab
Pending Single Orders tab
Pending Orders by Part tab and then selecting the Pending by Order tab
Admin
Significant improvements to the Load Article archive (ARTUPLOAD)
Classification: IMPORTANT
On 17 March we made significant improvements to the ARTUPLOAD functionality. The updated solution is now more user-friendly and comprehensible, particularly regarding error handling and field naming. Errors are no longer showstoppers—if one line fails validation, it is logged, and the import continues seamlessly with subsequent lines.
Additionally, older, less intuitive field names have been replaced with clear, standardized API names, making it easier to work with and understand the data.
With these changes, data imports are more reliable, errors are easier to diagnose, and the overall ARTUPLOAD process is significantly more user-friendly.
Summary of Changes
Enhanced pre-validation
Additional checks are performed before data is passed to the standard update methods.
Improved error handling
All errors (from both pre-validation and update methods) are captured and logged in the In/out log view (IOL) application.
If an error is found, the job continues with the next line in the file, rather than stopping altogether.
Field Formatting
The system automatically handles decimal separators (comma vs. period) and certain date formats to reduce errors.
Updated Field Names
All field names have been updated to more understandable API names, with clearer descriptions.
New Fields:
AutoCreateProductUnitAtGoodsReception
This new field has been added to extend functionality.
When activated, product units are automatically generated when goods are registered to stock.
AutomaticallyCreateWorkOrdersForSubstructures
This new field has been added to extend functionality.
When activated, production work orders should be created for sub structures automatically.
Field Blanking
Fields can be blanked out by sending in the value <BLANK>.
This applies to:
CustomField1, CustomField2, CustomField3, InternalNote, CountryOfOriginCode, DomesticCustomsTariffCode, EUCustomsTariffCode and PurchaseGroupName
Please note that this update has replaced the former Load Article archive (ARTUPLOAD). We also recommend using the standard rules for field formatting for all other load jobs.
Knut Sætre Waka
The following updates have been added to RamBase Cloud ERP:
Production
Automatic locking of Production work order (PWO) created for Sales order item (COAITEM)
Classification: USEFUL
When manufacturing to order, a Production work order (PWO) will in most cases, be created for one single Sales order item (COAITEM).
Today, there is no automatic locking of the link between the Sales order item (COAITEM) and the created Production work order (PWO), and it’s potential sub Production work order (PWO).
This is not optimal as there is a risk of relinking the Production work orders (PWO) to other needs etc.
To mitigate this, we are now adding an automatic Stock assignment (SAR) locking of the link between the Sales order item (COAITEM) and the Production work order (PWO), and it’s potential sub Production work order(s) (PWO).
The new locking is activated in the following scenarios:
Creating a Production work order (PWO) in the Production planning (PRODPLAN) application via the:
Pending by Order tab
Pending Single Orders tab
Pending Orders by Part tab and then selecting the Pending by Order tab
Admin
Significant improvements to the Load Article archive (ARTUPLOAD)
Classification: IMPORTANT
On 17 March we made significant improvements to the ARTUPLOAD functionality. The updated solution is now more user-friendly and comprehensible, particularly regarding error handling and field naming. Errors are no longer showstoppers—if one line fails validation, it is logged, and the import continues seamlessly with subsequent lines.
Additionally, older, less intuitive field names have been replaced with clear, standardized API names, making it easier to work with and understand the data.
With these changes, data imports are more reliable, errors are easier to diagnose, and the overall ARTUPLOAD process is significantly more user-friendly.
Summary of Changes
Enhanced pre-validation
Additional checks are performed before data is passed to the standard update methods.
Improved error handling
All errors (from both pre-validation and update methods) are captured and logged in the In/out log view (IOL) application.
If an error is found, the job continues with the next line in the file, rather than stopping altogether.
Field Formatting
The system automatically handles decimal separators (comma vs. period) and certain date formats to reduce errors.
Updated Field Names
All field names have been updated to more understandable API names, with clearer descriptions.
New Fields:
AutoCreateProductUnitAtGoodsReception
This new field has been added to extend functionality.
When activated, product units are automatically generated when goods are registered to stock.
AutomaticallyCreateWorkOrdersForSubstructures
This new field has been added to extend functionality.
When activated, production work orders should be created for sub structures automatically.
Field Blanking
Fields can be blanked out by sending in the value <BLANK>.
This applies to:
CustomField1, CustomField2, CustomField3, InternalNote, CountryOfOriginCode, DomesticCustomsTariffCode, EUCustomsTariffCode and PurchaseGroupName
Please note that this update has replaced the former Load Article archive (ARTUPLOAD). We also recommend using the standard rules for field formatting for all other load jobs.
Click the links to read more about the Load Article archive (ARTUPLOAD) - INP/14542, as well as the Load procedure - Input menu (INP) and Import/export Wizard (IOQWIZ).
Released: 17 March 2025