Used to create product returns from material issues to work orders.
Automated Test Platform
Sage X3 Automated Test Platform 3.1.0:
Ensures compatibility with latest version of node.js 18 delivered to date. Refer to the prerequisites_atp online documentation for more information about node.js compatibility with Sage X3 Automated Test Platform 3.1.0
Updates the third-party components to benefit from the latest capabilities and fixes. Consult Sage X3 Automated Test Platform – Third-party components for more information.
Bug fixes for the following components: header dropdown, data table row action toolbox.
Improvements to ensure that the Sage X3 Automated Test session management is activated before entering a Sage X3 function or entity.
Security vulnerability fix.
Improved support for One Stop Shop
You can define the rules needed to comply with One Stop Shop (OSS) requirements. This includes managing tax classifications, VAT declarations, SAF-T, and QR codes.
TicketBAI: Autoinvoice management
When you create a purchase invoice for a supplier, you have the option to generate a sales invoice that cannot be posted and cannot be sent to the TBAI tax authority. Instead, it is submitted by the customer.
This is managed by the ISSBYREC–Autoinvoicing parameter (LOC chapter, SPA group).
Validate SIREN/SIRET IDs
In the SIREN/SIRET validation function (FUNSIRVAL), you can quickly validate SIREN/SIRET IDs against the French government’s SIRENE database. You can validate one or a range of business partners at once, saving time.
The validation process compares information in business partner, company, and site records, such as address, name, and so on, to ensure that they are correct. It also identifies duplicates.
A log file details the results so that you can update records as needed.
This is managed by the EINSI–SIREN/SIRET validation and KFR–French localization activity codes.
Stock lines in the Miscellaneous issue, Subcontract transfer, and Intersite transfer transactions
- You can select the stock line to issue or to transfer. All the required information from the stock line is automatically retrieved and populated at once.
Scan composite codes to enter product data in the Stock change transaction
- When you scan a GS1 composite barcode, a QR code, or a Data Matrix code, the following product data is automatically read and entered: 01-Global Trade Item Number, 10-Batch or Lot number, 21-Serial number.
New Stock change transaction in the By identifier menu
- This transaction is designed to select stock identifiers used to quickly filter the stock lines for the stock change movement.
Shipment number and packing slip in the Purchase receipt transaction
- You can specify the shipment number when the purchase order line is shipped with several purchase shipments. You can also enter or scan the supplier packing slip. It is automatically populated on the purchase receipt document, which helps you perform any research or tracking.
Intersite receipt transaction from the Receipt menu
- You can use this transaction to receive intersite purchase orders quickly and easily.
View stock by product-site, View stock by location, and View stock by LPN transactions
- You can display these transactions with improved response times. The product image displays correctly.
Filter the product in the Putaway transaction
- You can filter the product from the selected storage list.
Dropdown lists for entry transactions
- In all transactions, all authorized values are displayed in the dropdown lists.
In invoice reports, the PTMENTIONS06 field allows another selection option
SAF-T extraction when the SAFTPRDKIT parameter is No
– For flexible kits:
In SAF-T, all lines for a kit are included in the SAF-T communication regardless of the parameter setting.
– For fixed kits:
Yes: All lines for a kit are included in the SAFT communication.
No: Only lines different from LINTYP 3 to 9 are included.
For the credit memos for this type of kit, you cannot select only one component.
The following is an overview of features being developed to manage electronic invoices through the e-invoicing framework. The framework includes new functions and updates to current functions as needed but does not change existing processes.
These features are in development should not be used in a production environment.
All features are managed by the EINV – E-invoicing activity code, which is not active by default.
Manage inbound e-invoices
When development is complete, you will be able to:
- Receive and manage inbound e-invoices with dedicated tools.
- Map Sage X3 data to inbound supplier e-invoices.
- Define mapping rules and criteria.
- Review results in a log file that details success, errors, and warnings.
- Set up as a recurring task.
Manage outbound e-invoices
When development is complete, you will be able to:
- Create, submit, and manage e-invoices with dedicated tools.
- Process transactions for sales or AR invoices, posted invoices, credit memos, and debit notes, (excluding direct GL entries and proforma invoices).
- Define criteria such as date, module, customer, and so on.
- Set up as a recurring task.
- Customers need to be able to accept e-invoices.
- Not all legislations support the cancellation of e-invoices.
New properties for finite scheduler integration
Additional properties are available for reading data through GraphQL APIs for Finite scheduler integration.
Increased Employee ID field length
The Employee ID is increased to 6 digits from 4 digits. All transactions, screens, and tables that use the Employee ID are updated.
Use the new datatype EPN to set the length of the Employee ID code to fit with your human resources software.
Work order production tracking default location
To assist the shop floor operator, Work order production tracking displays the default location for the product-site, based on the rules for the product category.
Mobile Automation: Filter for the components to be tracked
To filter the list of components to be tracked for a work order, set the Stock withdrawal mode in the Material tracking plan entry transaction.
The change manager for a change request can only be modified by an admin user
Use the CCMUPDCHGM-Allow change manager update parameter (TC chapter, CCM group) to control modification of an assigned change manager by any user approved as a change manger.
Mobile Automation: View product image in Production tracking and Material consumption
The Mobile Automation Manufacturing transactions Work order production tracking and Material consumption display the product image.
Error when replacing a component
Assigning an unplanned material to a released product line for a work order for multiple released products
Unplanned components added to a work order for multiple released products in the Work order (GESMFG), Production tracking (GESMTK), or Material tracking plan (FUNBENCHM) functions have the default link type “Released product.” This ensures easy selection of the work order line number for the updated released product. Alternatively, you can set the link type as “Complete order,” enter the component details and select the order line.
In the Material tracking plan entry transaction (GESMML), to display the Link type and Order line no. fields you need to add a number to the Input column. Sage recommends the fields are adjacent each other.
Manufacturing enhancements for user experience
- You can view work center data in a graphical format from the Where-used work centers function (GESMWW).
- You can open a sales order from a transfer request line (TPF) in the Enterprise planning function (FUNGBENCH / FUNGBENCHA).
- The Loc. field (Location) in the Production tracking function (FUNBENCHM) defaults to the default location defined in the issue rule or to a location where there is stock available.
Sage Provisioning Portal: AWS enhancements
Improved documentation: The portal’s documentation provides more comprehensive help related to AWS. You can find answers to questions quickly and efficiently.
Enhanced error handling: During unexpected situations, you receive more informative responses and messages to better understand what happened.
Microsoft SQL Server secure connection with the console
You can create a Microsoft SQL Server secure connection and benefit from the latest Microsoft SQL Server security settings.
Microsoft SQL Server secure connections require the PowerShell SQL Server module release 22 or later.
See the prerequisites and installation documentation for all components concerning PowerShell and the Microsoft SQL Server module for PowerShell.
Reset password link
The login screen includes a link to reset your password when basic authentication (user/password) is used to allow users to reset their passwords easily without having to ask the Administrator when passwords are forgotten or compromised.
Basic authentication is not recommended on production systems.
You receive an email with temporary links to reset your password, which you can do autonomously and securely.
The Notification Server needs to be active for the Sage X3 solution.
Runtime: Native JSON parser
Native Sage X3 language instructions were developed for JSON parsing and constructing JSON streams. You can use these instructions in your scripts when handling JSON payloads for faster and more robust processing.
For more details, refer to the JSON instructions documentation (openJson, closeJson, getJsonStr, getJson, setjsonInt, setjsonStr, and so on).
Register your organization and companies
As an administrator, you can register your organizations and companies with Sage in the Organizations menu to access Sage online services such as e-invoicing, tax number validation, artificial intelligence, and other services that elevate and streamline your business workflow through your Sage account.
Registering your organization and companies provides secure authentication when using Sage services outside of Sage X3 with no additional effort.
Enhanced Runtime cache management for scripts and table definitions
The Sage X3 Runtime contains an enhanced cache for scripts and tables that introduces faster and more streamlined processing when reading and parsing scripts and table definitions.
Memory requirements are refined.
Check the updated Runtime server requirements in the Prerequisites help pages.
System variables maxmem (Memory management) and adxmpr (Cache management) default values are updated:
- Adxmpr = 500
Using runtime tags on batch jobs
You can use runtime tags to direct individual batch jobs to a specific runtime service or a specific group of runtime services. This can be done with tags assigned to the batch jobs.
Runtime tags provide unlimited flexibility in batch jobs workload distribution.
Add-on packages for Sage X3 API dictionary
You can create new add-on packages in the dictionary for customizing and extending the Sage X3 GraphQL API.
Packages help you manage your extensions securely and can be associated with activity codes. Packages can be extensions of other packages.
Sage Provisioning Portal: Azure enhancements
Improved documentation: The portal’s documentation provides more comprehensive help related to Azure. You can find answers to questions quickly and efficiently.
Simplified Bastion instance management: You can use SPP to stop and start Bastion instances on your Azure cloud network. This enhancement helps to streamline operations and improve efficiency.
Effortless site deletion: To ensure a clean subscription, you can easily delete a site and all elements including site the site resource group. You need to confirm the action to avoid accidental deletions. If delete protection is enabled, you receive a message on why you can’t delete.
The existing infrastructure was updated to remove the link between Frontdoor and Private Link to ensure smooth site deletions.
Declare scripts through the Sage X3 API dictionary
To run a wide range of operations, you can declare Sage X3 scripts, or subprograms, as GraphQL operations attached to a GraphQL entity through the Sage X3 API dictionary.
See the online help and training resources for more details on the Sage X3 GraphQL API.
Automatic generation of GraphQL node definitions
GraphQL API schemas are described in the Sage X3 metadata dictionary. You can easily extend standard APIs, including customizations, and create new queries and operations.
The API menu contains all the links needed to view or extend the Sage X3 GraphQL APIs: packages, data models, node bindings, binding dictionary, and operations.
The tables and data models contain property names in friendly GraphQL notation and package information.
Custom GraphQL query schemas are generated when node bindings are validated after data models or operations are saved.
See developer.sage.com for more information to extend and use the Sage X3 GraphQL APIs.
Runtime: Managing prerequisite packages
The runtime prerequisite packages are described in a package.json file and centralized in the Dependencies repository.
Successful print jobs saved for traceability
Successful print jobs can be viewed in the Print supervision function (PSIMP). This allows monitoring mechanisms to retrieve all jobs, successful or not, through the Print Server APIs for better and more robust traceability.
The default retention period for failed print jobs is 20 minutes.
The default retention period for successful print jobs is 0 minutes (No retention). This can be changed in the Sage X3 Management Console, in the Print Server expert parameters.
See the Print server online help for details.
Simplified Excel add-in layout
The improved ribbon for the Microsoft Excel add-in is more consistent and provides easier authentication and setup flows.
Remove license restriction message
A message no longer displays when you access a function that is not authorized based on your badge. This provides quicker access to functions you need.
The Read-only indicator in the Action panel details why access is restricted.
Syracuse technical compliance and security
The SOAP Web Service pool will not start if the maximum size or the initialization size is 0. Default values are set as follows:
- Maximum size: 4
- Initialization size: 2
Runtime: Updated Microsoft Visual C++ Redistributables
The runtime supports and uses the latest Microsoft Visual C++ Redistributables.
Runtime: Updated PowerShell prerequisites
The runtime and console support PowerShell 7.3.
The minimum requirement for PowerShell in the latest release is version 7.2.
Runtime and print servers: Updated database clients
The server support and use the latest ODBC clients for Oracle and Microsoft Server and Azure elastic pools.
User interface enhancements for readability and accessibility
The following features have been improved:
- Readability of left lists with:
- Alternating lines
- Colors for hover and selected lines
- Header enhancements
- Readability of grid sections with:
- Alternating lines
- Colors for hover and selected lines
- Field highlights for editable fields
- Uniform background (textured backgrounds have been removed)
- Performance of complex screen rendering. Refer to the dedicated note in this document.
PowerShell scripts: Oracle database
The Oracle database is now configured through PowerShell when installing or updating. This provides for more security and simplifies deployment.
See the installation online help for more detail.
Improved performance of classic screen rendering
The Auto-collapse feature available from your user profile settings makes loading complex large windows with many tabs faster.
The option displays the header and first tab of a function and then shows the rest of the tabs as collapsed sections.
The settings are automatically saved when you expand or collapse sections and exit the function. The tabs will be as you left them when you reopen the function.
The Reset auto-collapse settings option resets all tabs to the default settings with two sections expanded and the others collapsed by default.
Support and security for Elasticsearch 8
Sage X3 supports Elasticsearch 8 and Elastic Cloud. This includes the Search server settings function to set up database and connection security. This makes it faster and easier to deploy Elasticsearch more securely.