Release 10.0.47.22 (April 2026)

New or changed features in Release 10.0.47.22 (April 2026) of PLM integration for Engineering Change Management.

This release introduces line-level release targeting for product release automation, support for non-engineering-controlled items in BOM integration, multi-route import capability, and AI-powered business impact analysis within the Staging journal.

1. Release Targets on PLM Staging Journal Lines

You can now define which receiving companies and sites a product releases to during automated release at the line level. A new Release targets tab is added on the PLM staging journal lines page, positioned between the Route and Translations tabs. Previously, users relied on the global PLM system setup, which did not support per-product-line targeting.

Key capabilities:

• The new Release targets tab displays a grid with Receiving company and Receiving site columns. You can add one or more company/site pairs per journal line and delete rows as needed. The Receiving site lookup is filtered to sites that belong to the selected receiving company.

• When the staging journal is posted, release automation uses the company/site pairs defined on the Release targets tab. Lines with release targets are released to all specified companies with their respective sites. Lines without release targets fall back to the PLM system setup values.

• When releasing a product with a BOM to a receiving company defined on the Release targets tab, the BOM table site in the receiving company is set to the receiving site from the Release targets tab. If no BOM site is filled on the staging journal line, the BOM table site remains blank in both the engineering entity and the receiving company.

• If no entries exist on the Release targets tab for a journal line, the system falls back to the company and receiving site configured on the PLM system setup. This preserves backward compatibility.

• Duplicate company/site combinations on the same journal line are not permitted. If a receiving company is not present in the Product release policy, does not exist as an active legal entity, or if the receiving site does not exist in the specified company, the system logs an error and skips the release for that target row.

• You can populate Release targets via Connectivity Studio. PLM systems can push receiving company and site information directly into the staging journal lines during import.

2. Receiving Site on PLM System Release Automation Setup

A new Receiving site column is available on the Company accounts grid within the Product release automation tab in the PLM system setup. This provides a default receiving site per company per engineering product category. When a staging journal line has no release targets defined on the Release targets tab, the system uses the company and site from this PLM system setup as the fallback.

Key capabilities:

• The system determines the receiving site through a three-level priority:
  (1) Release targets tab (per line) - highest priority;
  (2) PLM system setup (Receiving site column per company) - fallback;
  (3) Template item default order settings - lowest priority.

• When Release targets exist on the journal line, the system uses only those targets. It does not additionally release to companies from the PLM system setup. The PLM system setup is the fallback only when the Release targets tab is empty for that line.

• When releasing a product with a BOM using the PLM system setup receiving site, the BOM table site in the receiving company is set to the receiving site from the PLM system setup; not the engineering entity's BOM site. If no BOM site is filled on the staging journal line, the BOM table site remains blank.

• If the configured receiving site does not exist in the specified company, the system logs an error for that company's release and skips it.

• If no receiving site can be determined from any of the three levels, the system logs a warning and proceeds with the release without a site on the BOM.

3. BOM Site Field Optional on PLM Staging Journal Line

The BOM site field on the PLM staging journal line Details tab is now optional, even when the item has a BOM. Previously, this field was mandatory when a BOM was present. This deviated from the standard D365 manual release behavior.

Key capabilities:

• The release automation behavior now matches the standard D365 manual release. When a receiving site is determined (from the staging journal line, PLM system setup, or template item default order settings), the system sets the BOM table's site in the receiving company to the receiving site.

• The BOM site mandatory check is now a configurable scenario validation (Warning/Continue by default). Customers who require mandatory BOM site can reconfigure it to Error/Stop.

4. Support for Non-Engineering-Controlled Items in BOM Integration

A new configurable field on the PLM system setup page enables the PLM staging journal to accept BOM lines that reference non-engineering-controlled items. This is a per-PLM-system setting that addresses scenarios where legacy items exist in both ERP and PLM systems but are not managed through the ECM process.

Key capabilities:

• A new Boolean field, Allow non-engineering-controlled items in BOM, is available on the PLM system setup page (Engineering change management > Setup > PLM integration > PLM systems). The default value is No (off).

• When enabled, the PLM staging journal accepts BOM lines referencing non-engineering-controlled (standard) items. These items are added to the BOM as standard component lines without being enrolled in the engineering change lifecycle.

• When disabled (default), the existing validation remains active. BOM lines referencing non-engineering-controlled items are blocked.

• This setting applies to BOM import only. It does not affect item creation, ECO import, migration, or release scenarios.

5. Attach Several Existing Routes to an Item in a Single Import

You can now import several existing routes for an item in a single PLM import. Previously, importing routes required separate imports for each route. This did not support scenarios where the same route number is used across different sites.

Key capabilities:

• Import several routes for different sites or the same route number across several sites in a single import.

• Pass and maintain route effective dates during the import.

• Eliminates the need for repeated imports when assigning several routes to a single item.

6. Business Impact Analysis in Staging Journal

The Business impact analysis feature brings AI-powered downstream impact assessment directly into the Staging journal. You can view and analyze the business impact of BOM changes before posting, enabling informed decision-making.

Key capabilities:

• Select View documents to see a tabbed breakdown of affected sales orders, purchase orders, production orders, inventory, inventory journals, purchase requisitions, and quotations.

• Each tab displays Product, Company, Transaction, Quantity, Blocked, and Notified status. You can take actions such as View transaction, Block order, Notify responsible, View history, or view all transactions.

Bug fixes in Release 10.0.47.22 (April 2026) of PLM integration for Engineering Change Management.

Known issues in Release 10.0.47.22 (April 2026) of PLM integration for Engineering Change Management.

The package consists of a deployable package containing the following models and their respective versions. These models are essential for the functionality and integration of the PLM and Business Integration solutions.

Note

Ensure that all models are deployed and verified in the target environment to maintain compatibility and functionality across the PLM and Business Integration solutions.