DataLotse Portal

•

Sign in

Sign in to your DataLotse account.
New to DataLotse?Register

Set a new password

Choose a password for your DataLotse account.

Your subscription

Your plan is managed by DataLotse. New accounts start on a 7-day trial; once payment is received we activate your plan. To change your plan, contact sales.

Change password

Update the password you use to sign in.

Two-factor authentication

Add a second step at sign-in using the Google Authenticator app (free, on the App Store / Google Play). Strongly recommended for the account owner.

Create system connection

Pick the connection type first — then fill in the details it needs.
Data can be copied only between systems of the same release.
Full route to the SAP host, ending with the gateway / dispatcher port — e.g. /S/3300 (gateway, 33nn) or /S/3200 (dispatcher, 32nn), where nn is the system number. Format: /H/<router>/S/3299/H/<saphost>/S/<port>
Reached via the on-prem agent — host, user and password live in the agent and are not entered here. Set the Display name to a system the agent reports.

Your systems

Run a connection test before using a system in a copy.
No systems yet.

Register an on-prem agent

The agent runs inside your network and connects outbound to DataLotse — no inbound firewall change. Register it here to get a token, then put that token in the agent's agent.yaml. See the setup guide for installation steps.

Your agents

An agent appears as online shortly after it starts polling.
No agents yet.

Object catalog

Objects available to copy on your subscription. Filter by module to shorten the list. Use Data Copy to run one.

Data copy

Prerequisite: the target system must already have had a SAP_CUST client copy performed.

Cleanup

Deletes the selected object's documents from the target system only (source is never touched). Master data and follow-on documents (e.g. material / invoice documents) are left intact. This cannot be undone.

Status tracking

Live progress from the run log. Click a job to expand per-table results.
Adding team members is available on a paid plan. Choose a plan on the Account tab to invite users — your trial includes a single account owner.

Create user

Add a user and grant module-wise access. A user may hold several modules. Only modules included in your licence can be assigned.

Users

How DataLotse works

Set up DataLotse and run your first copy — on your own. Pick a topic on the left.
The agent runs inside your network, connects outbound to DataLotse, and runs every copy locally — so your SAP credentials and business data never leave your landscape. Only the job request and a status summary cross the internet.
  1. SAP setup — your Basis team installs 3 ABAP function modules (ABAP function modules) and a dedicated RFC user.
  2. Agent setup — install + register the agent and point it at your systems.
  3. Use DataLotse — add Source/Target systems, run a copy, optionally clean up the target.

ABAP function modules (RFMs)

DataLotse moves data through three generic, remote-enabled function modules your Basis/ABAP team installs once. There is no per-object ABAP — these handle every table.
Where to install: ZDATALOTSE_TABLE_READ on every source system · ZDATALOTSE_TABLE_WRITE + ZDATALOTSE_TABLE_DELETE on every target system (install DELETE on non-production targets only). After installing, use Systems → Check RFMs to verify.

Install (transaction SE37)

  1. Create a function group (e.g. ZDATALOTSE) in SE80/SE37.
  2. SE37 → create the function module → on Attributes, set the processing type to Remote-Enabled Module.
  3. On the Import/Export tabs, define the parameters exactly as the tables below (each pass by value).
  4. Paste the source into Source code, then activate.
  5. Grant the RFC user authorization to call them (S_RFC) and table access.
Prefer a transport? Your Basis team can request a transport request from DataLotse support instead of keying these in.

1 · ZDATALOTSE_TABLE_READ source

Reads the selected rows of a table and returns them encoded for transport.
ParameterKindTypeDescription
IV_TABNAMEImportTABNAMETable to read
IV_WHEREImportSTRINGTABDynamic WHERE conditions (one per line); empty = all rows
IV_MAXROWSImportIMax rows to return (0 = no limit)
EV_SUBRCExportSYSUBRCReturn code (0 = success)
EV_MESSAGEExportSTRINGError text when subrc ≠ 0
ET_ROWSExportSTRINGTABEncoded result rows
Show ABAP source
Loading…

2 · ZDATALOTSE_TABLE_WRITE target

Upserts (MODIFY) the transported rows into the target table.
ParameterKindTypeDescription
IV_TABNAMEImportTABNAMETarget table
IV_COMMITImportFLAG'X' = commit work
IV_TESTImportFLAG'X' = validate then roll back (writes nothing)
IT_ROWSImportSTRINGTABEncoded rows to upsert
EV_ROWSExportIRows written
EV_SUBRCExportSYSUBRCReturn code (0 = success)
EV_MESSAGEExportSTRINGMessage
Show ABAP source
Loading…

3 · ZDATALOTSE_TABLE_DELETE target · non-prod

Deletes rows by key — used by Cleanup. Install on non-production targets only.
ParameterKindTypeDescription
IV_TABNAMEImportTABNAMETarget table
IV_COMMITImportFLAG'X' = commit work
IV_TESTImportFLAG'X' = validate then roll back
IT_ROWSImportSTRINGTABEncoded key rows to delete
EV_ROWSExportIRows deleted
EV_SUBRCExportSYSUBRCReturn code (0 = success)
EV_MESSAGEExportSTRINGMessage
Show ABAP source
Loading…

RFC user

A dedicated SAP user the agent uses to connect — its credentials stay on your machine.
  1. Create a system/communication RFC user (e.g. DATALOTSE_RFC) on each system the agent connects to.
  2. Grant authorization to call RFC function modules (S_RFC) and to read/write the tables involved in your copies.
  3. Put this user + password in agent.yaml — they stay on your machine, never in the cloud.

Install the on-prem agent

A Linux host with Docker, outbound HTTPS to app.datalotse.com, network access to your SAP, an RFC user, and your SAP NW RFC SDK (under your own SAP licence). The agent is a compiled image — you just pull and run it; no build, no source.
DataLotse gives you a package with the compiled image and simple run scripts — no Docker commands to type, no build, no source.
  1. Unpack the package, then unpack your SAP NW RFC SDK inside it (a wrong SDK path is the most common failure): 
    mkdir datalotse-agent && tar xzf datalotse-agent-package.tar.gz -C datalotse-agent && cd datalotse-agent
unzip nwrfc750P_17-70002752.zip          # your SAP SDK → creates nwrfcsdk/
ls nwrfcsdk/lib/libsapnwrfc.so           # this file MUST exist
  2. Create your config from the example and fill it in (see Configure agent.yaml): 
    cp agent.yaml.example agent.yaml
  3. Install and start the agent: 
    ./install.sh
  4. That's it — the agent appears in the Agents tab. Day-to-day: ./logs.sh (watch the log) · ./restart.sh (after editing agent.yaml) · ./stop.sh
The image is a compiled binary with no SAP SDK and no Python source inside — nothing to build, and you never handle the agent's source code.

Register an agent

  1. Open the Agents tab → enter a name (e.g. landscape-agent-01) → Register agent.
  2. Copy the token shown — it is displayed only once. It goes in agent.yaml as agent_token.
  3. Your plan allows one agent; it can serve multiple systems.

Configure the agent (agent.yaml)

Your SAP credentials live here on your own machine — never in the cloud.
cloud_url: "https://app.datalotse.com"
agent_token: "<token from the Agents tab>"
poll_seconds: 5
dry_run: false
systems:
  PROD:
    ashost: "<sap-host>"
    sysnr: "00"
    client: "100"
    user: "<RFCUSER>"
    passwd: "<password>"
  TEST:
    ashost: "<sap-host>"
    sysnr: "00"
    client: "500"
    user: "<RFCUSER>"
    passwd: "<password>"
          
    
            
  1. The names (PROD, TEST) are what you'll pick in the Systems form.
    2. 
            
  2. After editing, restart the agent: docker restart datalotse-agent
    3. 
            
  3. The agent reports these system names to the portal — they appear as suggestions in the Systems form.
    4.

Add a system

  1. Systems tab → Add system. Pick the connection type first.
  2. On-prem Agent (recommended): set Display name to a system your agent reports — host, user and password live in the agent, not here.
  3. Or Direct / SAProuter / VPN: enter app server, system no., client, user and password.
  4. Set the role (Source / Target) and SAP release (ECC or S/4HANA), then save.
  5. Add a Source and a Target, and run Test connection before using them.
Copies are only allowed between systems of the same release. The number of systems (landscapes) you can add is set by your subscription.

Run a data copy

  1. Data Copy tab → choose an object (e.g. MM_PURCHASE_ORDER).
  2. Select Source → Target, and enter at least one filter (company code, year, or a document range).
  3. Click Run. DataLotse resolves dependencies, referenced master data and follow-on documents automatically; PII is scrambled for non-production.
  4. Track progress and document counts in Monitor; click a job for per-table detail and number-range guidance.
Objects available to copy are limited to the modules in your plan. A selection filter is always required — DataLotse never copies a whole table.

Run a cleanup

  1. Cleanup tab → choose an object and enter a filter (a selection is required — cleanup never targets a whole table).
  2. Click Preview to see exactly what would be deleted.
  3. Review carefully, then Delete. Use this only on non-production targets.
Cleanup is available on Professional and Enterprise plans.