What's new in SCM: Migrate Italian Subcontracting
Timeline
What's new in SCM: Migrate Italian Subcontracting
This session is for Italian customers and partners. It explains how to move from the old Italian subcontracting functionality to the new global Subcontracting app, which replaces it. The presenter walks through a Contoso Italy company: the legacy toggle in Manufacturing Setup, the pre-check, cleaning up open transfer and purchase documents with work in progress items, installing the apps, and running the migration. He then shows what changes afterwards (fields, pages, views, prices) and lists the requirements and what data gets migrated. Migration can now run in production, based on customer and partner feedback.
Watch: https://www.youtube.com/watch?v=nb_a42dmSqE (11:25). Area: Supply chain. Audience: consultant, partner, admin. Presenters as heard: not introduced by name.
Chapters
- 0:00 Why the Italian subcontracting is being replaced (1 min)
- 1:19 Legacy toggle and pre-check in Manufacturing Setup (2 min)
- 2:50 Cleaning up open documents and reviewing existing data (2 min)
- 4:53 Installing the Subcontracting and migration apps (2 min)
- 7:08 Running the migration and application areas (2 min)
- 9:08 Migrated vendors and prices (1 min)
- 9:43 Feedback, requirements and what gets migrated (2 min)
Features in this video
- Subcontracting app replaces Italian subcontracting - GA - 0:06 to 1:19 - Italian subcontracting is discontinued and replaced by the global Subcontracting app.
- Legacy subcontracting toggle - GA - 1:19 to 2:19, demo 1:19 to 2:19 - An Italy-only Manufacturing Setup field indicates legacy subcontracting.
- Legacy subcontracting pre-check - GA - 2:19 to 4:53, demo 2:19 to 4:53 - An action checks for open transfer and purchase orders with WIP items before disabling legacy subcontracting.
- Install Subcontracting app from Manufacturing Setup - GA - 4:53 to 7:08, demo 4:53 to 7:08 - The app can be installed from Manufacturing Setup when disabling legacy subcontracting.
- Italian Subcontracting Migration app - GA - 5:52 to 11:25, demo 6:20 to 6:34 - A separate app, not on AppSource, migrates legacy Italian data and is proposed only when needed.
- Run migration by disabling legacy subcontracting - GA - 6:54 to 8:17, demo 7:08 to 8:17 - Disable legacy subcontracting runs the migration, restarts the session and switches application areas.
- Subcontracting views on purchase and transfer orders - GA - 8:04 to 9:08, demo 8:04 to 9:08 - Legacy subcontracting pages are gone and migrated documents appear in normal lists with a subcontracting view.
- Migrated vendor fields and subcontracting prices - GA - 9:08 to 9:43, demo 9:08 to 9:43 - Vendor subcontracting fields are migrated and the work center link stays.
Quotes
- 0:32 "we are discontinuing the existing Italian functionality and replacing it with a subcontracting app." - States the core decision: the legacy Italian subcontracting is being retired, so migration is required.
- 2:34 "make sure that there is no open transfer orders with the VIP items and purchase orders with the VIP items" - The main precondition for migration: open documents with work in progress items must be dealt with first.
- 6:07 "system even do not ask you to install migration because there is nothing to migrate." - Environments that never used legacy subcontracting skip the migration app entirely.
- 6:54 "You are in control when exactly you want to migrate." - Installing the apps does not migrate anything, so timing of the cutover is left to the user.
- 7:52 "If you have data in your legacy subcontracting system, system will not allow you to activate the toggle without migration." - A guard prevents switching to the new app with unmigrated legacy data.
- 9:43 "We did a lot of improvements on the migration process." - Signals the migration was reworked after feedback and is now usable in production.
- 10:11 "Italian subcontracting migration up is not listed on AppSource. It's only available to install from the tenant itself." - Partners must know the migration app cannot be found on AppSource and is installed from Manufacturing Setup.
- 10:39 "Vendor, purchase headers, lines, transfers, components, routing, and subcontracting prices." - Lists the scope of data that is migrated.
- 10:49 "You can create a clone of your uh environment, install apps, and run the migration in each company individually" - Recommends testing in a cloned environment and shows migration runs per company.
Disclaimers and status moments
- 5:18 other: "I will skip it for now because it's reviewed in a different session."
- 9:30 other: "Previously, when we just released it, we make sure that migration is not possible"
Documented features matched
- none of the features in this video matched an item in the documented features baseline
Cleaned transcript (auto-captions, 11:25)
What's new in SCM: Migrate Italian Subcontracting
0:06 Buongiorno. Let me continue in English, but this session is for Italian customers and partners because we will we will be talking about very Italy specific process. Because Italian localization for a long time had advanced subcontracting capabilities already handling transfer of uh raw materials between company and subcontractor, work in progress items, and managing prices. With new subcontracting app available globally and in Italy, we are discontinuing the existing Italian functionality and replacing it with a subcontracting app.
0:44 And here we will be talking about migration path or how to transfer from the legacy subcontracting to new app. Conceptually, new subcontracting app includes a lot of features which available in Italy and more. There is one significant difference in implementation. That's why we need a little bit more migration. But let's take a look in practice. How to switch from let's call it legacy subcontracting to the just subcontracting subcontracting app.
1:19 All right. Contoso Italy. Where do I start? I will navigate to manufacturing setup. And you will see something which is only visible in Italy. So, this is a old field coming from the legacy subcontracting and indicator that legacy subcontracting is on. Interesting part, if you activate the new environment, if you provision the new environment, this toggle will be off by default and the new subcontracting app is installed. But you are until you started to use a new app or maybe even after you started the new app, you can disable it.
1:57 You need just to uninstall the subcontracting and go here and choose legacy subcontracting. And you'll see the action. We will look at it a little bit later. But if you migrated, upgraded, uh legacy subcontracting will be on, new app is not installed, and you are thinking about starting on how to migrate. So, there is a new actions. Legacy subcontracting. We can disable it. But before, we can do pre-check. You can ignore it, but the same checks will be run it anyway.
2:34 As I mentioned before, 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 no open transfer orders with the VIP items and purchase orders with the VIP items. Let's go and fix this specific problem. Subcontracting transfer. Here it is. So, I have it here. What does it mean? I can just go and post it. I post ship.
3:09 I post receipt. And that should be enough. All right. The second one, it has no work in progress lines, so that's why I can just leave it as is, even if it is subcontracting order. All right. Let's continue. Actions, subcontracting, pre-check. Now it will be telling me about purchase orders. Fair enough. Subcontracting orders. And this is my first subcontracting order. I'll scroll. Uh here I don't plan to uh post it. I will I will delete it.
3:47 I'm not saying that you need to follow this path, but you decide how to manage your data. Maybe you complete the documents, maybe you just restart them, maybe cancel the subcontracting order completely and recreate it later once you migrated. But I will be just deleting line four for this demo. All right. Now I have two subcontracting orders. Only one had work in progress line. Good. So the data is fixed. Before we jumping there, let's uh check one more thing. Vendors. I navigate to vendors
4:28 and explore subcontracting specific field. Yeah, subcontractor true, subcontracting location code. So these are local Italian fields and we plan to migrate them. Also we need to take a look at the subcontracting prices. And we can see that some prices are defined here for this vendor. All right. Let's close. So now by now we already explored all the data which is already present. So it is a vendor, prices, purchase and transfer orders, and apparently production orders, but it's a it's a given. So now the next step precheck.
5:07 You need to install subcontracting app. Yeah, without it you have nothing to migrate to. You can install it right from here. I will choose yes. Continue and install. And it suggest me to run the assisted setup. I will skip it for now because it's reviewed in a different session. All right. Once app is installed, we get back to a role center. Uh that's how installation process works. So to continue we need to navigate back to manufacturing setup. Manufacturing
5:40 setup. Yeah, of course you can do the preparation work up front and install subcontracting app early. And now let's try to disable legacy subcontracting. Still not still not. Here we run the check and analyze if migration is needed. 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 the data, uh system even do not ask you to install migration because there is nothing to migrate. Yes, you just getting the the new app. So this is not a problem. But uh otherwise,
6:20 you need to install the app and the path is the same. So the system allows you to install it right from here from this manufacturing setup. I will choose yes and get my app installed. Perfect. App is installed and ready to use. All right. Basically we again back on the role of center because installation of the app is a serious process. We go to the manufacturing setup for the like whatever third first time. And again, yeah, you could install them up front and have them available. So installing app does nothing.
6:54 You are in control when exactly you want to migrate. So you can pre-install these apps and wait and work on your work in progress documents like production orders, purchase documents, transfer documents to make sure that they are uh cleaned up and ready. And as soon as they're ready, then you navigate to actions, legacy subcontracting, and finally disable legacy subcontracting. Yes. Data was migrated and again everything restarted. The reason is we are reactivating activating some application areas. All Italian subcontracting the legacy subcontracting is tagged with application area.
7:35 Let's find it. Legacy subcontracting and you can it is off. New app is marked with subcontracting tag, and now it's on. So, activating this toggle is actually changing this setting as well. But, it is also uh guarded, and it controls if you have data or not. If you have data in your legacy subcontracting system, system will not allow you to activate the toggle without migration. And as soon you as soon as you run migration, system does this change, and now you do not see legacy subcontracting fields. You can see the only new subcontracting fields coming from the app, but not the previous ones.
8:17 You also do not see subcontracting orders. Yeah? Or subcontracting transfer orders, which is basically the same. So, these dedicated pages are not available anymore. But, where are my purchase and transfer orders? Purchase purchase orders. They are in the same list. You can see as normal purchase orders. But, can I look only on subcontracting ones? Yes, we have a view for this one. I got only subcontracting orders. So, the same story goes for transfer orders.
8:55 View to subcontractor I have something from subcontractor I have nothing, but that's uh it's expected. So, you can still get your documents filtered as needed. All right. Next one, what do we want to look at? We want to look at our vendors. The subcontracting location was moved. The link to work center is still still here. What about prices?
9:30 Prices look absolutely the same, but they are actually in the new table in the in the migrated table. What we learned? 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. And thank you very much for customers and partners in Italy who provided us feedback. We did a lot of improvements on the migration process. Appreciate it very much. Couple of requirements, just to remind you. Both subcontracting up and Italian subcontracting migration up are new. Subcontracting up you can install different ways from AppSource or from a inside product.
10:11 Italian subcontracting migration up is not listed on AppSource. It's only available to install from the tenant itself. So, you need to open manufacturing setup and you trigger installation. Again, if needed, system will identify if it's needed or not and uh propose you to install it. WIP work in progress items, purchase and transfers are something you need to handle up front. Otherwise, uh migration just works. What gets migrated? Vendor, purchase headers, lines, transfers, components, routing, and subcontracting prices.
10:49 Uh minor fields are here and there. So, that's uh basically it. Uh Feel free to try it at any point of time. You can create a clone of your uh environment, install apps, and run the migration in each company individually at uh point of time when it is most convenient for you. Thank you and ciao.