Symptom

After an upgrade to SAP Business One 10.0 FP 2608, assigning an electronic file format or generating a bank file, electronic document or electronic report fails with one of these errors:

Cannot call the electronic file manager; contact technical support. EFM URI not defined. Check SLD.
Cannot call the Electronic Document Service. Contact technical support. CEDFHttpClient Exception: (7) Could not connect to server.

You typically see the error in these places:

  • Banking: when you assign a bank file format (BPP) to a payment method, or when the Payment Wizard generates a payment file with an existing format.
  • Administration → Setup → General → Electronic File Manager: when you assign a GEP or SPP format.
  • Electronic documents and reports: when you run a GEP-based report or create an SPP-based electronic document or report.

Example: on SP 2605, the Payment Wizard creates the SEPA payment file for a run as usual. After the upgrade to FP 2608, the same run with the same format stops with the EFM URI not defined error and no file is created.

The issue often goes unnoticed at first. The upgrade wizard finishes without errors and daily work in the client is not affected. The error appears only when someone runs the next payment run, bank statement import or legal report, often days later and close to a deadline.

All functions that use electronic file mappings are affected, for example:

  • Electronic documents such as FPA (Italy), KSeF (Poland), CFDI (Mexico), NF-e (Brazil), eInvoice (France), Veri*factu (Spain) and PEPPOL
  • Electronic reports based on SPP mappings, such as BAS, Digipoort (Netherlands), MTD (United Kingdom) and the MYF and E-Books reports (Greece)
  • Reports based on GEP mappings, such as the Intrastat Wizard, the withholding tax report, DIOT (Mexico) and the Zusammenfassende Meldung (Germany)
  • The Payment Wizard (BPP) and the Bank Statement Wizard (BFP)

Cause

As of FP 2608, SAP moved the Electronic File Manager out of the SAP Business One client into a separate server component, the EFM Transformation Service. The client and the Electronic Document Service now send every file transformation to this service. If the service is not installed, the client finds no service address in the System Landscape Directory (SLD). If it is installed but not running or not reachable, the connection fails.

Who is affected

All of the following must apply:

  • The system runs SAP Business One 10.0 FP 2608 or higher, on Microsoft SQL Server or SAP HANA.
  • You use at least one function that relies on electronic file mappings (see the list above).
  • The EFM Transformation Service is not installed, not registered in the SLD, or not running.

On SAP Business One Cloud, landscapes on SAP Business One Cloud 1.1 PL22 or lower are always affected, because the service cannot be installed there.

The error text tells you where to look:

  • EFM URI not defined. Check SLD. means the service is not installed or not registered in the SLD.
  • Could not connect to server means the service is installed but not running or not reachable.

To check whether the service is installed and running, use the server where it should run.

On Windows (PowerShell):

PowerShell
Get-Service -DisplayName "*EFM Transformation*"

On Linux:

Shell
systemctl status sapb1efmt

If the command returns nothing or reports that the service is unknown, it is not installed. A status of Running or active (running) means it is running. A running service doesn't prove that the client and the Electronic Document Service can reach it. Different hostname formats in the SLD or a firewall can still block the connection, so also check the SLD control center as described under Confirm the result.

Prevent the issue on FP 2608

Install the EFM Transformation Service as part of the upgrade, before users start working on FP 2608:

  1. Make sure the SLD is installed and at least one database server is registered with a hostname or IP address.
  2. Run the Component Wizard from the FP 2608 installation package and select Electronic File Mapping Transformation Service.
  3. Install it on a machine that can reach the SLD and that the Electronic Document Service can reach. Use the same hostname or address format as in the database server registration in the SLD.
  4. Restart the service. On Windows, use the Services app (SAP Business One EFM Transformation Service). On Linux:
Shell
systemctl restart sapb1efmt

Keep in mind:

  • The service is passive: it waits for requests from the client, the Electronic Document Service and the Job Service. The Electronic Document Service depends on it.
  • Posting documents and payments in the client works without the service. Only steps that create or read an electronic file fail.
  • The configuration files appsettings.json and log4net.conf are in C:\Program Files\SAP\SAP Business One EFM Transformation Service\conf\` on Windows and in `/usr/sap/SAPBusinessOne/EFMTransformationService/conf/ on Linux. There you can set the logging level and limit parallel connections (Kestrel → Limits → MaxConcurrentConnections). Restart the service after every change.
  • There is no setting that brings back the old built-in behavior. SAP describes the service as required from FP 2608 on.

On premise, the service runs on Windows or Linux. For the SAP HANA version on Linux, manage it with systemctl as shown above.

On SAP Business One Cloud, the service needs SAP Business One Cloud 1.1 PL23 or higher. On lower versions, the Component Wizard blocks the installation with this warning:

The Electronic File Mapping Transformation Service is compatible with SAP Business One Cloud PL23 and higher. Lower versions are not supported.

Upgrade the cloud landscape to PL23 or higher first, then install the service.

For the complete upgrade path and the other prerequisites of FP 2608, see SAP Business One 10.0 FP 2608: upgrade paths and requirements.

Confirm the result

  • In the SLD control center, open the Services tab. Check that the EFM Transformation Service is listed and that its dashboard opens from the link in the Link column.
  • Assign a bank file format to a payment method again, then generate a test payment file. Compare it with a file from before the upgrade before you send anything to the bank.
  • Run one GEP-based report and create one electronic document in your test company.
  • Check electronic documents and reports created while the service was missing. They may show an error status and need to be sent again.
  • Check scheduled jobs that generate reports or files, since they may have failed in the background.