Glossary

Understand the terms.See the possibilities.

The meaning is just the beginning. Blue Ocean helps you connect SAP, processes and decisions to what happens in your business.

SAP Business One · SAP S/4HANA · Business management

This glossary turns SAP terminology into management decisions.

ERP connects records and processes across finance, purchasing, sales and inventory.

Product, licenses, infrastructure, implementation and support are different cost components.

A technology name does not guarantee a feature is included in your contract.

Use these definitions to request clear scope and responsibilities.

How it works

A product and a journey are different.

Before comparing proposals, identify the software and the path used to put it into operation.

  • SAP Business One: ERP for small and midsize companies.
  • SAP GROW: the current offering associated with public SAP Cloud ERP, previously known as GROW with SAP.
  • RISE with SAP: a modernization journey for existing SAP environments, with architecture to assess.

Project terms should describe deliverables.

Every word should point to a result you can review.

  • Assessment: mapping processes, data, risks and priorities.
  • Fit-to-standard: comparing your operation with standard processes before selecting extensions.
  • Go-live: starting production after testing and acceptance.
  • Support: service and evolution according to the contracted scope.

Details and criteria

Architecture in practical terms.

Ask what stays in the ERP core and what connects to it; this distinction affects updates, costs and maintenance.

  • SAP BTP: a platform for integrations, extensions, data and other services subject to subscription.
  • Clean core: an approach that reduces interventions in the core and supports its evolution.
  • API: an interface used by systems to exchange information under defined rules.

Data, AI and cloud require context.

Availability varies by product, edition, country, language, license and configuration.

  • Joule: SAP AI capabilities whose availability must be checked in the selected scenario.
  • Localization: country-related capabilities and configuration, without replacing tax review.
  • BI: data analysis through indicators, reports and calculation definitions.
  • Public or private cloud: distinct operating, responsibility and extensibility models.

Questions worth answering.

Are Business One and S/4HANA versions of one product?

No. They are different products; moving between them requires assessment of processes, data and architecture.

Is integration always included?

No. Source, destination, frequency, error handling and support must be included in scope.

Does clean core mean no extensions?

No. It means planning extensions and integrations without unnecessarily compromising core evolution.