Powered by Cloud Customer Care

This guide compiles curated content of SAP S/4HANA Cloud Public Edition for Retail, Fashion and Vertical Business, and lessons learned obtained after supporting multiple retail implementations as Product & Engineering Solution Architect in collaboration with SAP Retail Product Management. Whether you are an SAP partner, or a customer, the goal is the same: reduce your TCO, shorten the project timeline, minimize risk during the implementation, and leverage the retail features for the company.

 

1. Lay the Foundation Before the Project Starts

Foundational Principles 

Regardless of the SAP Cloud ERP industry solution implementation and scope, the most successful retail implementations share common traits: They follow SAP Activate Methodology, embrace the cloud mindset, perform rigorous fit-to-standard workshops, leverage the new features delivered in upgrades and feature updates, and elevate their business scenarios with SAP AI.

The cloud mindset shift is real. If your team is used to SAP ECC or SAP S/4HANA on-premise, this blog would be helpful for your project activities: Accelerated Business Transformation – Moving from SAP ERP 6.0 to SAP S/4HANA Cloud Public Edition. In our experience, projects that cut corners on these topics consistently face timeline impacts, rework activities, and could face more challenges down the road. The SAP Activate Methodology guides you through all the project phases, tasks and deliverables.

Digital Discovery Assessment

The Digital Discovery Assessment (DDA) is not a formality. It enables you to document the initial project scope which will be used as a reference during implementation.

While Executing a Digital Discovery Assessment, the Retail Relevant Solution Processes and Scope Items accelerator available in SAP Activate guides you through the scope items available for the project scope. You can use this as additional guidance to include the scope items in the DDA.

In addition, please make sure to cover all the detailed questions of the DDA and validate the solutioning guides available. For example:

 

Retail Sizing

It is mandatory to perform the retail sizing before starting the project through the Capacity Planner. This will ensure that your system continues to support increasing data volumes and transaction loads over the coming years.

The following video explains how to use the tool: Leveraging the Capacity Planner for SAP Cloud ERP Retail Sizing – PET 2026

Pro tip: Based on recent sizing discussions with multiple customers, there is one decision that can help you before the Explore Phase. You can use the data retention input as part of the archiving strategy. Even though this is not an activity that you will execute in the short term, you need to archive data once the business is live through the Information Lifecycle Management (1KA) scope item, so we recommend aligning it early in the project.

 

Validate Country Availability

The retail content has expanded significantly in the last two releases. As of Release 2608, the solution supports 59 SAP Local Versions. For the rest of the world (with some exceptions, please check SAP Note 3107866), you can leverage Customer Local Versions through Configuration Localization Tool (CLT), but customers and partners own the localization content.

General Guidance:

Local Version	Content
SAP Local Version	SAP provides the content. Scope items available per release and country: SAP Signavio Process Navigator
Customer Local Version	Customer owns the localization content. Please check the SAP Note 3107866
Partner Local Version	Partner implementation package with localization content included using CLT

Pro tip: If you’re implementing retail through Configuration Localization Tool, please make sure to involve localization experts early in the project to gather all the localization requirements to comply with local regulations, and use Parallel Line to implement Customer Local Versions. Once you finalize your configurations and testing, you can merge the content to the Main line.

 

2. Planning Activities for the Fit-to-Standard Workshops

Initial Business Process Assessment

Before executing the Fit-to-Standard workshops, it is critical to Perform Initial Business Process Assessment for SAP S/4HANA Cloud through the Business-Driven Configuration Questionnaire accelerator for retail. It contains relevant questions that are key to the workshop’s success. This activity also applies to other lines of business (LOB) workshops: Verify Configuration for Fit-to-Standard Workshop for SAP S/4HANA Cloud

Initial Settings

As part of the preparations, you must perform the corresponding settings in the Starter System before the Fit-to-Standard workshops are executed. The following SAP Note contains an accelerator about the settings for both Starter and Development Systems: SAP Note 3313681 – SAP Accelerator: SAP S/4HANA Cloud Retail, Fashion and Vertical Business Set Up Instructions

Multiple projects have asked: “Can we implement retail scope items in a second wave?”  Please make sure to follow the retail set up Instructions accelerator to avoid a reprovisioning of the landscape.  You must include the retail bundle (license-dependent) in the scoping phase of SAP Central Business Configuration.

Note: If you’re implementing Brazil, please use the accelerator included in the SAP Note 3701808 – Accelerator for Retail Solution Processes for Brazil

During the scope item selection process, please keep in mind that some scope items can’t be activated once the retail bundle is selected. For example, Accounting Enhancements for Banking (5NU). For more detailed information: SAP Note 3435102.

For other initial crucial activities like the primary finance settings, please check the following blogs:

• Getting started with your SAP S/4HANA Cloud Project – Dodging the System Re-Provisioning Bullets
• The Importance of Primary Finance Settings in SAP Cloud ERP

 

3. Future Retail Operations

Core Retail Backbone

A common question from consultants that have previous experience implementing SAP S/4HANA Cloud for other industries: “Should we use plants and materials, or retail sites and articles?”. There is only one correct approach: If you’re implementing retail and fashion scope items, you need to use the retail sites and articles for your business, even if you require make-to-stock scenarios (raw, semifinished and finished products).

The plant is only required for the CBC org structure configuration, and the materials are not required. Currently the plant and material conversion to retail site and article is not supported.

Furthermore, the term merchandise category is used in retail for taxonomy management to group articles. We don’t use material groups.

 Fit-to-standard Solution

During the fit-to-standard, please ensure to run specific workshops for all the retail/fashion streams based on the scope items: master data, pricing and promotions, demand & supply, procurement, manufacturing, supply chain, store connectivity and sales.

The goal is to avoid combining retail workshops with generic topics. This consistently underestimates the depth of retail-specific discussions, so please dedicate separate sessions.

General Guidance:

Topic	Guidance
Retail Master Data	Best practice: Always include reference articles as part of your master data design. This will avoid complexities once you’re live. Once the initial SAP CBC settings are finalized, and you face issues while assigning the Business Partner master data to the retail site, please ensure that the retail site is assigned to the corresponding sales area. Only one sales area can be assigned to the retail site in the Set Up Organizational Structure app:  SAP KBA 3653104 – Error “Sales Org, Distr Chl not maintained in BP” while assigning a Business Partner to a Retail Site
Data Migration	Make sure to plan the migration activities earlier in the project. Data Migration is key for the project success. This is not optional activity required only for User Acceptance Testing or during the Deploy Phase plan. It requires ownership early in the project: Available Migration Objects Data cleansing: Master Data is the heart of the system, so if you’re transitioning from a legacy ERP system, please make sure to plan your data cleansing activities properly. You don’t want your Production System polluted with inaccurate data that could make you take wrong business decisions. Explore using Parallel Line to get familiarized with the Migration Cockpit.
Promotion Management	SAP Omnichannel Promotion Pricing is a solution hosted on SAP Business Technology Platform (SAP BTP) that allows you to integrate promotions across sales channels. Please find more details in the integration section. Please check SAP Note 3747242 – SAP S/4HANA Public Cloud Sales Order and SAP Omnichannel Promotion Pricing Solution integration release restriction note
Supply Chain	Many customers are interested to enable Warehouse Management for their Distribution Center which is ideal for their logistic operations. For the retail store, we recommend using the in-store apps as these are a better fit for the store associate and decrease operational complexity. If Transportation Management is part of the project scope, please review in detail the following considerations: SAP Note 3332309 3332309 – SAP S/4HANA Cloud, Public Edition – Restrictions for the Transportation Management processes
Store Operations	Before using the store operations app, please make sure the store associate has a valid store assignment: SAP Note 3624540 – Sales Order Error – “Enter a Valid Retail Site” (Message no. RFM_STORE_SO_MANAGE052) in SAP S/4HANA Cloud Public Edition For in-store scenarios, you can use the Manage In-Store Sales Orders app. The Manage Sales Orders app/Create Sales Orders (VA01) are available, however, for the store operations this app meets the store associate requirements. For point-of-sale (POS) integration, I would recommend leveraging the parallel processing feature for replication. Likewise, we recommend having only one job replication active for a single communication scenario. Consider the advanced down payments scope item (7ZJ) to post your in-store sales orders. Usually retailers prefer delivery-based down payments functionality instead of the milestone-based approach (scope item BKJ). The store associate can print different label types for different products and product variants in the store using the Print Labels app.
Point of Sale Connectivity	If you’re using the Message Monitoring apps, the processing date time zone is reflected as UTC following the official system time zone: SAP KBA 3520009 – AIF – Timestamp Gap for AIF Fiori Apps in Cloud Public Edition. However, the payload contains the accurate transaction time.

 

Fashion and Vertical Business

Coexistence of retail features with manufacturing can be leveraged in SAP S/4HANA Cloud Public Edition, so fashion companies can use the following functionality on top of the retail foundation:

Scope Item	Name	Purpose
83B	Manufacturing for Retail	Enables manufacturing processes within a retail context
82X	Segmentation for Retail	Demand and inventory segmentation
6DI	Seasons for Retail	Seasonal collection management
6NM	Value-added Services	VAS management in operational documents (PO, STO, SO)
7DL	Characteristic Value Conversion	Characteristic value mapping for fashion variants

 

4. Build and Switch Operations

Integrations

A common integration question from SAP partners and customers: “Which API should I use to create retail articles?” Please make sure to always use the Product SOAP API with the communication arrangement SAP_COM_0009 for both inbound and outbound integrations: SAP KBA 3761515 – Which API enables full integration for creating retail articles.

Similar question applies for integrations in general. We always recommend leveraging out of the box integrations (if available) following the SAP Best Practices. For example, SAP Customer Checkout to perform all the POS activities in the store, SAP Omnichannel Sales Transfer and Audit to capture and process POS transactions, SAP Omnichannel Promotion Pricing Service to extend the promotion capabilities, and SAP Order Management Foundation to handle order-related data from multiple channels.

For more detailed information: SAP Note 3438787 – Interface overview: SAP S/4HANA Cloud Retail, Fashion and Vertical Business

Extensibility

In case you find additional requirements during the fit-to-standard workshops, please check the Developer Extensibility BAdIs available in the SAP Business Accelerator Hub that can be used during the Realize Phase to extend standard behavior. For example, you can adapt the POS integration data and messages for inbound and outbound scenarios.

To create reports and other extensibility use cases, please check the CDS Views for Retail, Fashion and Vertical Business.

Cutover

Planning activities before the go-live is critical for your success, so please don’t leave them at the end of the Realize Phase or early in the Deploy Phase to work on it. You must start planning the cutover earlier to ensure the best plan for the business. Please remember that a cutover not only applies to the IT Team, but to the whole business.

Pro tip: Please make sure to avoid planning cutover activities during a weekend with up-time restrictions.

As part of the standard maintenance windows of SAP S/4HANA Cloud Public Edition, we have uptime restrictions and downtime during the Hotfix Collections Deployments and feature updates. Transport Management is locked, configurations and Migration Cockpit are in read-only mode, so you need to wait for the system to finalize to re-start your activities.

Each release I update the hotfix collection restrictions accelerator in SAP Activate Methodology, so I would recommend reviewing it to plan your project activities: Review and Process Hotfix Collection.

 

5. Stay Current and Elevate your Autonomous Enterprise

Go-live is not the finish line. The Run phase is where you realize the ongoing value of cloud deployments, and where the new capabilities change the operations. The Release Assessment and Scope Dependency (RASD) provides a tailored list of changes that your system will have after a feature update or a major upgrade based on your system scope.

It is critical to stay current with the latest and greatest by monitoring, testing and using new retail/fashion content delivered in our release cycles.

If you didn’t implement any AI feature as part of the first wave of the project, make sure to elevate your business scenarios with SAP Business AI capabilities.  Use the SAP Discovery Center to explore the full catalog of SAP AI offerings available to your team: SAP Discovery Center.

Joule is generally available for Assortment Management since 2602. Retail planners can create assortments, assign products or store locations, adjust validity periods, and terminate assortment modules using natural language by reducing the time and expertise required for routine assortment tasks.

 

Looking further ahead, we have multiple AI initiatives in the pipeline, so please explore the product roadmap for upcoming retail features in the SAP Road Map Explorer.

 

Product Feedback

If you would like to request a product improvement for SAP S/4HANA Cloud Public Edition, you can use the Customer Influence Portal to submit your ideas, so other customers can vote for them.

Best Practice: Please first validate if a request already exists and vote on it before posting a new entry.

Product Documentation

Before starting the project, you should familiarize yourself with the official product documentation.

• SAP Help: Retail and Fashion and Vertical Business
• SAP Learning: Exploring SAP S/4HANA Cloud Public Edition – Retail
• Restrictions: SAP Note 3435102 – SAP S/4HANA Cloud: Retail Release Restriction Note
• Performance and Scalability: SAP Note 3723491 – Performance and Scalability Best Practices and Recommendations for SAP S/4HANA Public Cloud Edition for Retail, Fashion and Vertical Business

Source link