<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=652223065253317&amp;ev=PageView&amp;noscript=1">

Blog

From SAP AFS to S/4HANA Fashion: Impact on Key Processes

Mon, Apr 26, 2021



3-Key processors

The SAP Apparel and Footwear solution (SAP AFS) has been around since the early 2000s, and many of its users over the years have grown accustomed to certain functionality and processes that it offered.

Any changes to these need to be understood clearly, including how the new functionality will work and the potential impact on the business. With SAP S/4HANA Fashion and Vertical Business moving closer to the core business solution and with the harmonization that has gone into the new product, SAP AFS user will notice the following significant changes:

Available to Promise (ATP) is now Advance ATP (aATP). Key differences are:

  • Advance Available to Promise (aATP) consists of 2 main components Product Availability Check (PAC) and Product Allocation (PAL)
  • Introduction of confirmation strategies during instances of re-ATP to better manage the order book
  • Rescheduling Report for orders
  • Ability to use BOP Fiori App for ATP and Supply Assignment together

ARUN (Allocation Run) is now Supply Assignment. Key differences are:

  • Introduction of new statuses to determine which quantities are acceptable for customers
  • Replacement of the ARUN Optimizer Tool with a more detailed reporting tool - ARUN Insight to Action
  • Exception Rules can now be defined by users with more ease
  • Supply Assignment can be executed together with ATP via the BOP Fiori app

Rebates

  • New transaction used in S/4HANA to create Rebates (WCOCO)
  • Users can create Rebate Agreements (Condition Contract in S/4HANA) together with the condition records used for accruing the required values

Business Partner replaces the traditional customer and vendor master record

  • Both Customer and Vendor Master records maintained as Business Partners with transaction BP
  • No separate transactions to maintain Customer master (XD01) and Vendor master (XK01) in S/4HANA
  • The transaction FD32 used in AFS to maintain master data for Credit Management no longer exists in S/4HANA
  • Handling Authorization to control data changes in Customer and Vendor masters is different in S/4HANA

Finance: Credit Management

  • Credit Management is no longer part of Sales and Distribution as it was in AFS earlier. It is now part of Financial Supply Chain Management (FSCM)
  • The transaction FD32 used in AFS to maintain master data for Credit Management no longer exists in S/4HANA
  • The master data maintenance is part of Business Partner (BP) transaction

Data Migration from SAP AFS to S/4HANA For Fashion and Vertical Business Using the S/4HANA Migration Cockpit

Fundamental data structure changes between SAP AFS and S/4HANA for Fashion and Vertical Business makes the new platform more robust and vertically integrated. But it also means challenges when it comes to data migration.

To ease the data migration, SAP developed a migration tool, which attune participated in early testing and provided relevant feedback to SAP for further enhancements. We've been getting a lot of questions regarding the migration process so we got together with SAP to answer the most commonly asked questions of data migration from AFS to S/4HANA Fashion.

Some of the questions we've covered are:

  • Are all AFS data objects covered with the Data Migration cockpit?
  • What is the advantage of using the AFS Data Migration cockpit vs the traditional data conversion?
  • What versions of AFS does this work in?
  • Does the tool have reporting capabilities, after data mapping and before upload?
  • Would the AFS Data Migration cockpit work for customized fields carried out on a customer’s landscape?

Learn more on the migration cockpit; including the approaches and different paths available by accessing the webinar below.

New call-to-action