Introducing Localization as a Self-Service

Objective

After completing this lesson, you will be able to understand the Basics of Localization as a Self-Service

Introducing Localization as a Self-Service

As businesses expand globally, they face unique challenges related to local regulations, tax requirements, and business practices that vary across different countries and regions.

The following video explains SAP's approach to localization. It demonstrates how organizations can extend existing localizations or create custom solutions for countries or regions without SAP-delivered local versions.

Note

The Configuration Localization Tool is currently under the early adopter program. To participate in the early adopter program, you must fulfill the following criteria:

You must be on SAP S/4HANA Cloud Public Edition with a 3-system landscape.
Your target country/region and scope items must be supported by the Configuration Localization Tool, as described in the SAP Note 3107866.
Either your implementation partner must be subscribed to a partner TDD system or you need to be subscribed to an SAP S/4HANA Cloud Public Edition sandbox tenant depending on rollout plans.

If you meet the above criteria, please get in touch with your implementation partner or SAP Sales point of contact to participate in the early adopter program.

Refer to the documentation for the Configuration Localization Tool to know more details (accessible to SAP Partners only).

Exploring the Basic Process Flow for Localization as a Self-Service

Let's examine the basic process flow for the two approaches to localization as a self-service.

SAP delivered localization

The process of extending SAP delivered localizations begins in SAP Central Business Configuration by selecting the target country or region and defining the project scope and bundles.

Next, we set up the organizational structure and perform required configuration activities.

We then proceed with last mile localization, using localization as a self-service to implement customer-specific requirements. It's important to note that the customer is responsible for maintaining all last mile localizations. All the extensions are maintained in the customer namespace, ensuring no conflicts during regular software updates and upgrades. This includes responses to legal changes: regulatory updates that affect SAP’s solutions are developed and delivered to SAP customers who have a valid subscription or maintenance contract. By keeping extensions in the customer namespace, these updates integrate seamlessly without causing conflicts.

Customer Local Version

Now, let's continue with Customer Local Versions. When the target country or region isn't covered by an SAP-delivered local version, we use the Configuration Localization Tool in SAP Central Business Configuration to create a customer local version by copying an existing SAP-delivered local version. The configuration content gets copied from the SAP-delivered local version for Germany.

This copy is deployed as the customer local version for the target country or region. We then define the project scope and choose bundles. As with any country, we set up the organizational structure. Following this, we adjust the configuration using self-service configuration UIs (SSCUIs) for our target country. The same applies to adapting business processes, where we use the various localization extensibilities to adjust processes and comply with local legal and business requirments.

Same as for SAP-delivered local versions, extensions for customer local versions are maintained in the customer namespace without affecting SAP-delivered code, which means updates and upgrades can be easily deployed. It's crucial to remember that the customer or corresponding partner is responsible for the development and maintenance of complete customer local version.

Exploring SAP S/4HANA Cloud Public Edition Extensibility Options

SAP S/4HANA Cloud Public Edition offers multiple extensibility approaches that enable customers and partners to adapt the standard software to specific business requirements. These extensibility options are designed to be lifecycle-stable, ensuring that SAP software updates don't interfere with customer or partner extensions.

Integrated Extensibility Options

1. Key User Extensibility

A set of low-code/no-code tools with user-friendly interfaces that don't require coding or extensive ABAP knowledge. Key users can:

Add custom fields
Create custom forms and templates
Extract and customize CDS views for analytics
Make layout changes to existing applications

2. Developer Extensibility

Available only in a 3-system landscape, this option enables custom ABAP code development for:

Creating ABAP applications
Implementing complex extension logic
Extending SAP S/4HANA Cloud solutions
Developing partner extensions

Both integrated extensibility types operate in the customer namespace and remain upgrade-proof, preserving your customizations during future updates. These extensions are possible only using the released APIs provided by SAP, ensuring proper interface approaches that maintain compatibility with the core system.

Side-by-Side Extensibility

This approach leverages the SAP Business Technology Platform (BTP) to create extensions outside the core system. With BTP, you can:

Develop custom applications using ABAP or other languages (Java, Node.js, Python)
Implement loosely coupled extensions that operate independently
Integrate AI business services, process automation, and data science capabilities
Connect to SAP S/4HANA Cloud via remote APIs (OData, SOAP, BAPIs)

All extensibility options are built on the virtual data model (VDM) consisting of core data services (CDS) views, which expose business data in a semantically rich way for easier consumption.

For more detailed information on Extensibility options, please refer to the SAP Help Portal.

Continue to quiz