Our experience in global FMS implementations suggests SAP’s Data transport and Migration Tool (DTMT) fits in nicely for AFS to FMS migration1. Once a fully configured FMS system is ready, DTMT can be used for migrating all the master and transactional data, including custom data, from AFS to the new FMS system. But organizations that want to accelerate the migrations will need a number of sophisticated tools such as:
- FMS RDS that establishes running FMS systems from Day 1
- Fashion industry process repository
- Analytical tools to identify standard versus custom processes on AFS
- Tools for custom object analysis
- Templates for master data, test scenarios and configuration
During the Greenfield implementation, a complete cutover plan must be established, deciding the processes that FMS will support and the data that needs migration.
However, there are some key influencing factors that determine the adoption path. Organizations may want to:
- Quickly realize their investment on FMS and differentiate in the marketplace
- Start by trying FMS for a new season or for certain geographies
- Start by taking only retail operations on FMS
- Move As-Is business to FMS and then gradually try out the new features
To rapidly realize investments, organizations would be advised to take the Big Bang Approach: Setup the FMS system and then migrate the entire manufacturing and wholesale data as well as retail data from AFS and non-SAP applications. The approach is risky as there are concurrent tasks such as harmonizing processes and organizational structures that need to be completed. But the target state is reached sooner.
For the rest, a phased approach is recommended. There are two ways to manage a phased approach:
- AFS and FMS coexist. AFS and other data moves gradually to FMS. Retail processes move once the system stabilizes. AFS is then retired. This phased approach is ideal for a new season. Data for the new season is moved to FMS. Activities corresponding to the previous seasons are carried out in AFS. Gradually all old season data is migrated to FMS before AFS is retired. The same phased process can be carried out across geos with, say, North America migrating first, followed by Europe or Asia Pacific. However, if there are documents (such as purchase orders) that might contain categories across regions then this approach can become complex.
- FMS acts as a system to support retail processes to begin with and then AFS processes move gradually into FMS. This is recommended for organizations that want to try FMS for a new season or for select geos. It can also be used to first take retail ops onto FMS.
In the phased approach, licenses for AFS and FMS will be required until both systems are active. It is, therefore, imperative to work with SAP on the finer aspects. The phased approach also means dual maintenance. All the relevant interfaces will need to point to both AFS and FMS such as vendor data, customer data, financial transactions including bank data and reporting etc. In addition, the code base may have to be maintained in both the systems.
Organizations that have custom processes will want to continue with them on FMS. In such instances the code will need to be pasted from AFS to FMS.
FMS is guaranteed to set apparel brand owners on the digital path. With proper planning and immaculate execution, the path can be made smooth and easy.
- DTMT will ensure that a material master which is associated to a grid in AFS will automatically convert to an article on FMS. DTMT can also be utilized for migrating custom tables along with data stored in them. It comes with content to carry out this migration and can also be used to migrate from AFS to FMS to S/4HANA Fashion. However, the content to move to S/4HANA Fashion is currently missing.