Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

SAP Business One — connector

Reads sales orders, business partners, items and outgoing invoices through the Service Layer (OData) of SAP Business One and loads them into the Bronze layer.

On this page (15)

Leia antes: ../conectores.md (mapa de estados) e fichas.md (índice das fichas).


What it is#

Reads sales orders, business partners, items and outgoing invoices through the Service Layer (OData) of SAP Business One and loads them into the Bronze layer.

Supported ingestion modes:

  • Nós buscamos — Nós buscamos os dados na sua fonte.

What it's for#

Bring SAP Business One data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language Q&A wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources in the plan).
  • Access: requires an active workspace — with a past-due, suspended or canceled subscription, the run is blocked.
  • Shutdown: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the screen informs that the feature is currently unavailable.

Prerequisites#

  • A SAP Business One account with access to the data you want to ingest.
  • In SAP Business One, ask the administrator for a user with a Service Layer license and read permission on Sales, Business Partners and Items. Provide the Service Layer URL (https://servidor:50000), the company database name (CompanyDB), the user and the password — the password is encrypted (AES-256-GCM) and is never shown again.

Credentials#

Authentication method: User login that opens a temporary session.

Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the config of the connection, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving the credential for this connection to an external credentials vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Senha (senha)

Secrets are never re-displayed and are redacted in any error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
urlServidorURL do Service LayertextosimEndereço do Service Layer, sem o /b1s/v1 no fim.
empresaBase da empresa (CompanyDB)textosim—
usuarioUsuáriotextosim—
senha 🔒Senhasenha/segredosimsegredo (cifrado; cofre externo opcional)

Step-by-step#

  1. No menu Dados → Conexões, use Nova conexão.
  2. Escolha SAP Business One no catálogo.
  3. Preencha os campos do formulário (veja a tabela acima).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Salvar NÃO inicia ingestão nenhuma.
  6. No cartão da conexão, use Montar extração (ou vá em Orquestração → Pipelines e use Conectar fonte). O pipeline aponta para a connection salva — a credencial não é copiada.
  7. Na revisão, Publicar (agenda desligada) cria a versão 1 sem executar nada. Depois, Ativar agenda e Executar agora são ações separadas.

Example — connection test#

Sample configuration (all values are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
urlServidor = <urlServidor>
empresa = <empresa>
usuario = <usuario>
senha = •••••• (cifrado — nunca exibido)

Expected result#

O Testar conexão retorna a lista de tabelas/recursos descobertos. Após a primeira carga, as linhas aparecem na camada Bronze do seu workspace, prontas para o pipeline.

Limits and costs#

  • Pagination: hard ceiling per run (default 10.000 pages / 5.000.000 rows); anti-loop guard.
  • SaaS load: default batchSize 5.000, maxRows 200.000 per resource.
  • Estimated volume: ~1 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scope per workspace: each customer reads and writes only in their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credentials vault is optional and enabled per connection; without it, the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs pass through secret redaction (raw, URL-encoded and in JSON).
  • Production doesn't fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or lacking necessary permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket indicating the connector and the resource.
  • Empty record path — the response arrived without records in the expected place. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network problems before scheduling.
  • Monitor the runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed/changed type column = attention).

Related#


Last review: 2026-10-04. Fact sheet automatically generated from the product connectors catalog.

Related links