What's new in SCM: Migrate Italian Subcontracting (2026 release wave 2)

Overview

The video explains that the legacy Italian subcontracting functionality is being discontinued and replaced by a subcontracting app available globally and in Italy. The new app includes the features available in Italy and more, but handles work in progress items differently, so open documents must be prepared before migrating.

It walks through finding the legacy subcontracting toggle, running the pre-check, fixing open transfer and purchase orders, installing the Italian subcontracting migration app, and running the migration. It then shows what changes afterwards: the application area switches, legacy pages are removed, and subcontracting documents are found through views on standard lists.

Key points

• Work in progress handling is the main difference between legacy and new subcontracting. Open transfer orders and purchase orders containing work in progress items must be posted, deleted or cancelled before migration.
• The pre-check looks for open transfer orders and purchase orders with work in progress items. It can be skipped, but it runs anyway during migration.
• The Italian subcontracting migration app is not on AppSource. It can only be installed from the tenant itself.
• Migration was initially blocked in production so Microsoft could collect feedback.
• Migrated data: vendors, purchase headers and lines, transfers, components, routing, and subcontracting prices. Vendor fields such as the subcontractor indicator and subcontracting location code move to new tables.
• Turning off legacy subcontracting switches the application area to the new subcontracting and hides legacy fields. The toggle is guarded: it cannot be activated without migration if legacy data exists.
• After migration the dedicated legacy pages are removed. Subcontracting purchase and transfer orders are found through views on the standard lists.

Features

Every feature below: status not stated, demoed.

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “Manufacturing Setup” at 1:19
• other “Subcontracting Transfer” at 2:50
• other “Subcontracting Orders” at 3:34
• other “Vendors” at 4:14

Quotes

• 0:32 “With new subcontracting app available globally and in Italy, we are discontinuing the existing Italian functionality and replacing it with a subcontracting app.”
• 0:54 “new subcontracting app includes a lot of features which available in Italy and more. There is one significant difference in implementation.”
• 2:34 “we have a differences on how work in progress items are implemented. That’s why we are asking you to make sure that there is”
• 5:52 “If you do not have open documents, prices, vendors, etc. So basically if you’re not using the legacy subcontracting at all, we based on”
• 7:52 “it is also uh guarded, and it controls if you have data or not. If you have data in your legacy subcontracting system, system”
• 10:11 “Italian subcontracting migration up is not listed on AppSource. It’s only available to install from the tenant itself.”
• 10:39 “What gets migrated? Vendor, purchase headers, lines, transfers, components, routing, and subcontracting prices.”

Disclaimers in the video

• 9:30 other: Previously, when we just released it, we make sure that migration is not possible to run in the production environment. So, we want to get some feedback.