Skip to Content

Dear Community,

It is widely known that one of the major and more complex localization deployments is Brazil.

To quick start the deployment for Brazil, currently 3 accelerators are available or under development focused on the S/4HANA On-Premise:

1) SAP Best Practices package for S/4HANA
 (under development for Brazil)

– an evolution from the former “baseline”, this package delivers a model company using the Solution Builder framework, through a set of building blocks structured for selected business processes.

With this package, a template enterprise structure and selectable related configuration sets can be activated through scripts, offering accelerated jump start for implementation projects, as well as extensive business process documentation as well as test scripts.

For more information, refer to -> SAP Best Practices for SAP S/4HANA, on premise edition.

2) SAP Fast Track Appliance for S/4HANA (localized for Brazil)

– the FT appliance is similar to the Best Practice package, with the difference that it is automatically activated as part of the S/4HANA technical installation. Although the solution coverage is less comprehensive than the Best Practice package, this option allows an even faster project start, delivering at the end of the installation phase a solution with a robust set of business processes. The installation of the FT appliance is comprised of two steps:

a) obtain FT media
b) install S/4HANA with FT appliance.

For more information on the solution coverage, refer to

For information on how to obtain the FT software appliance, refer to SAP Notes 2202234  and 2317122.

Consider that the FT for Brazil is currently only available for S/4HANA On-Premise 1511 FPS01.

3) SAP Best Practices baseline package for SAP ECC (Brazil version), followed by a migration to S/4HANA

– this approach is equivalent to the option 1, with the difference that the package contents are designed for SAP ECC. Therefore, the baseline script must first be run on top of an ECC 6.0x system and then, afterwards, the entire solution should be migrated to S/4HANA. Different from option 2, specific scope items can be selected for the package deployment in the ECC step, however, once the solution is migrated to S/4HANA, the package can no longer be reused (e.g., for provisioning a new client).

For more information, refer to


Summary of options:

Deployment approach
Deployment speed
Scope selection
Best Practices for S/4HANA
Planned S/4HANA 1709 OP
Solution Builder
Fast Track for S/4HANA
Released S/4HANA 1511 OP FPS01
Packed appliance
New installation required
Best Practices for ECC, upgrade to S/4HANA
Released SAP ECC 6.0x
Solution Builder & Upgrade
New installation required


The above accelerators deliver a fully usable and pre-assembled Brazilian Model Company, which can be adjusted, extended and customized freely after the deployment. In general, they will allow jump start deployment of new solutions.

However, it may also happen that a pre-existing country structure exists, which may either require adjustments or ad-hoc complements

Therefore, in addition to the accelerator, a KBA – Knowledge Base Article – is also made available, which describes in detail the sequence of key activities to be performed for enabling the basics of the Brazilian Localization setup.

Refer to 2409683 – KBA: S/4HANABrazilian Localization Quickguide

For those already familiar with Brazil, you will notice that in comparison with SAP ECC, there aren’t any critical deltas in S/4HANA when it comes to Localization, and the underlying customizing activities are pretty much the same. Nevertheless, knowing what to do and how to use the available assets is key to reduce risk and accelerate the implementation.

This is a living guide, and feedback is more than welcome.

Good luck!

Eduardo Rubia

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Jorge Jardim

    Eduardo, bom dia.

    Temos um cliente que já está rodando em S/4 HANA na Europa, ainda sem localização Brasil.

    Vamos trazer o ERP dele para o Brasil e estamos avaliando o grau de dificuldades que teremos em implementar a localização Brasil nessa situação.

    Você teria uma ideia para nos iluminar ?


    1. Eduardo Rubia Post author

      Oi, Jorge.

      O grau de dificuldade para implementar a localização do S/4HANA é praticamente o mesmo de se implementar a localização de um ERP. Isso porque as funcionalidades específicas de Brasil a rigor são as mesmas, com exceção dos relatórios fiscais que agora são disponibilizados somente no TDF.

      Assim, para dimensionar a complexidade é necessário mapear quais processos de negócio são tocados pela localização, o que pode ser atendido através do core, o que precisa ser desenvolvido.

      Se os processos de negócio já produtivos na Europa forem ser aproveitados por exemplo, então estaríamos falando de um delta apenas, o que reduz complexidade. Por outro lado, se os processos aqui forem substancialmente diferentes dos de lá, aumenta a complexidade porque os processos precisam ser discutidos conforme os requisitos locais.

      O que eu sugeriria é que fosse feito um pre-assessment de 1-2 semanas, com os principais módulos envolvidos (Compras, Vendas, Finanças, HCM, Fiscal), onde se levantasse uma visão desses requisitos para dimensionamento de complexidade.





Leave a Reply