Be-terna Product Documentation on Product Documentation

Version 27.1.0

Mon, 01 Jan 0001 00:00:00 +0000

Summary

Version 27.1.0 extends Professional Services with new control options in billing types, improvements around sales contracts and work orders, and adjustments for complaint and connector scenarios. It also delivers a broad set of fixes across service, contact, and billing processes.

27.1.0 — 2026-02-10

New features

30741 - Introduced the Consider quantity flag in billing types and billing assignments
47525 - Implemented the contract field Print option recurring billing as an enum
47500 - Added a new enum for Sales Type in work orders
47168 - Reworked the contract assistant in Project Connector for Professional Services
43193 - Added the missing from-to contract structure to project tasks
43271 - Made related lists editable in the sales contract
39067 - Improved validation and lookup for SLA no. and contract no. on the work order card
Introduced multi-select in the sales contract list
43216 - Harmonized initial and demo data for BE-terna Project, Professional Services, and Project Connector
39065 - Enabled opening the work task card directly from the list
46938 - Extended recurring invoices with Shortcut Dimension 1 and 2
43244 - Activated the Show as rental field on sales invoices
43216 - Revised initial and demo data
42513 - Connected the complaint process to Project and Connector
39809 - Introduced a sales complaint process based on complaint-related documents
39925 - Added c/o addresses with contacts without customer records
38691 - Deletes orphaned project task lines
39891 - Made the project task number prefix configurable
39586 - Revised translations
39925 - Added installation lookup from the contract line
19810 - Added a TransferFields test
39353 - Plan lines can now be completed and canceled

Bug fixes

47784 - Owner was missing on the work-task subpage
47776 - Corrected the contact list lookup filter for c/o addresses
47605 - Location remained empty when a complaint was created from a work order
37956 - The Sales documents function in AAZ did not show the sales order
47007 - Create recurring invoice(s) ignored the contract status in the sales contract list
39069 - Print on service report had no effect in service lines
27965 - Improved translations
40009 - Corrected an incorrect search entry for service billing
27965 - Corrected Payment Method Code handling
40043 - Service billing run stopped while creating invoices
39962 - Fixed the print error on sales credit memos
23560 - Increased field length
39475 - Disabled phone-number validation in work orders

Assisted Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the assisted setup flow for webshop channels in BE-Commerce.

Prerequisites

A new or extended webshop channel is defined.
Number series, languages, and baseline settings are aligned.

Recommended Sequence

Start the wizard and enter channel code and basic data.
Configure import/export behavior and implementations.
Maintain countries, payment methods, and shipping parameters.
Complete check options, contact settings, and company information.

Setup Steps

Click to enlarge

Channel Basics

Click to enlarge

Base Setup

Mon, 01 Jan 0001 00:00:00 +0000

Within the base setup, general standard templates and settings can be defined.

Click to enlarge

General

Field	Description
Initialize Cash Register Menu	Creates and assigns the BE-POS role center for the signed-in user
Initialize Standard Template	Creates the general standard template for interface and functionality
Initialize Job Queues	Creates the cash register job queues if they do not yet exist. This automatically imports movement data into the journals, for example.
Initialize Overview Setup	Creates or extends the overviews that the standard uses for various search functions in the cash register interface
Initialize Captions	Creates receipt text captions, including multilingual captions

Demo

Field	Description
Initialize Setup	Creates DEMO cash register setups (cash register setup, tenders, etc.)
Initialize Data	Creates DEMO cash register data (receipts)
Location	The location code for the DEMO cash register setup
Cash Register	The cash register code for the DEMO cash register setup

Note: When a new DEMO cash register setup is created, all cash register setups and any data already generated are deleted.

Version BC 22

Mon, 01 Jan 0001 00:00:00 +0000

Summary

Upgrade to Business Central 22, replacement of DotNet variables with the File Management codeunit, rework of the import/export control into a transfer-type-independent field, and final move from Company Information to IC Setup.

22.0.3 — 2023-08-30

Bug fixes

The Import/Export field on the IC partner card is now visible regardless of the transfer type.

22.0.2 — 2023-07-27

New features

For incoming sales orders you can decide which line description is used on the sales order line (new field Deviating description on sales order line on the intercompany partner).

22.0.1 — 2023-07-17

New features

File import detects automatically which IC partner the file comes from. The new BET PIC Import/Export field on the IC partner selects the XMLport. The previous BET PIC XMLPort ID for Import field becomes obsolete.
Final move from Company Information to IC Setup.

Other changes

DotNet variables are no longer used; file import and export run through the File Management codeunit.
Field 5399207 BET PIC XMLport ID (Integer) is replaced by field 5399223 BET PIC Import/Export (Enum BET PIC Import/Export). A data upgrade is required.

22.0.0 — 2023-07-10

Other changes

Upgrade from 20.0.71 to 22.0.0.

BE POS Listener Setup

Mon, 01 Jan 0001 00:00:00 +0000

Download

The BE POS Listener can be downloaded here.

Installation

Start the bepos_listener_setup.exe application.
Select the target folder and continue with Next.

Click to enlarge

Run the installation with Install.

Click to enlarge

Finish the installation with Finish. This lets you start the BE-POS Listener directly.

Click to enlarge

Communication

There are two ways to communicate with the BE-POS Listener, directly through the browser or through Microsoft Azure.

BE-terna Project License

Mon, 01 Jan 0001 00:00:00 +0000

In the setup of the BE-terna Project license, the client’s license can be managed and viewed. In addition, the module administration per user can be called up from here.

Click to enlarge

Field	Explanation
Kundennummer	Eindeutige Kundennummer die von BE-terna dem Kunden bereitgestellt wird.
Identifikationsnummer	Wird von BE-terna generiert und dem Kunden zugespielt. Diese Nummer ist im Feld einzutragen und über den Button über “Vom Webserver aktualisieren” wird dann die Lizenz geladen. Sollte keine Internetverbindung aus Business Central heraus möglich sein, lässt sich eine Lizenzdatei über “Aus Datei importieren” einspielen.
Anzahl Module	Über das Klicken auf die Zahl im Feld Anzahl Module öffnet sich eine Übersicht zu den gebuchten Modullizenzen.
Benutzereinträge	Über das Klicken auf die Zahl im Feld Benutzereinträge gelangt man in die Liste zur Pflege der Benutzer pro Modul.
Historie	Hier sind Änderungen an Modulen ersichtlich.
Webseite	Homepage von BE-terna. Von hier aus lässt sich über das Kontaktformular ein Supportticket erstellen.
Telefonnr.	Das ist die Telefonnummer des Empfangs von BE-terna. Von hier aus kann an Ansprechpartner weitergeleitet werden.

In the overview of the booked module licenses, you can see which products are licensed and thus accessible. From here, you can assign the corresponding users to the modules by clicking on the number in the User Entries column. The number in the Number activated column shows the number of activated users.

Cash Register Closing Report

Mon, 01 Jan 0001 00:00:00 +0000

The cash register closing report is used to obtain an A4 printout of the filtered cash register closings. Revenues are totalled by POS process and date.

The filter that opens when you run the report can be used to filter the report to a specific cash register setup.

Click to enlarge

Cash Register Start

Mon, 01 Jan 0001 00:00:00 +0000

The POS start is initiated using the Start button.

Click to enlarge

First, the cashier must identify themselves by entering the relevant cashier code.

Click to enlarge

If the cashier code is not known, it can be searched for and selected using the magnifying glass button.

Click to enlarge

If a password has been stored for the cashier, it is then requested in the input field.

Drop shipment

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Drop shipments link a sales order and a purchase order so that the supplier ships directly to the end customer and the selling company only handles the commercial side. BE-terna Intercompany automates this flow between IC partners so that it runs through without manual intermediate steps.

Business value

Shorter process: purchase order and sales order are shipped and invoiced together.
Automatic posting reduces manual work at the receiving company.
Additional lines (for example freight) can optionally be shipped along.
The Sales before purchase invoicing constraint can be lifted when needed (see Vendor and purchase).

Focus areas

Auto-post orders

For automatic posting on drop shipments, posting must run against the existing purchase order. Incoming invoices are then applied automatically to that order.

Import local detail view control

Mon, 01 Jan 0001 00:00:00 +0000

The “Import Local Detail View Control” action can be used to import a text file that defines a detail view in project documents.

Click to enlarge

Installation

Mon, 01 Jan 0001 00:00:00 +0000

Goal of the setup

This page describes how to get started with installing BE-terna products from Microsoft AppSource. It covers the path from the prerequisites for a SaaS tenant to the app installation and the first steps after the download has completed.

Prerequisites

A Microsoft Dynamics 365 Business Central SaaS tenant is available for the installation.
A Microsoft account is available for signing in to the tenant and to AppSource.
The target test or production environment has already been created.
The required licenses or an available trial version have been clarified in advance.

Recommended sequence

Prepare the SaaS tenant and the sign-in details.
Search for the BE-terna product in Microsoft AppSource and add it to the environment.
Install the app in Business Central and confirm the language if prompted.
Review the basic environment settings and open the assisted setup.

Setup steps

Prepare the SaaS tenant

To download the app from AppSource, you need a Software as a Service tenant for Microsoft Dynamics 365 Business Central. If no environment is available yet, create the tenant first and verify that you can sign in with the intended Microsoft account.

Intercompany setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The intercompany setup controls how BE-terna Intercompany processes documents company-wide. The page groups every non-partner-specific switch and defines the frame for exchange with all IC partners.

Click to enlarge

Prerequisites

BE-terna Intercompany is installed in the company.
A user with permission for the Intercompany Setup page is available.
The Intercompany role center can be activated in user settings (see Role center).

Recommended order

Open the intercompany setup and review the base values.
Align transfer of line comments and item tracking with your own processes.
Configure the job queue for file import and automatic acceptance.
Create one partner card per IC partner and refine the switches there.

Setup building blocks

Document line comments

When line-comment transfer is active, comments on purchase and sales document lines travel with the IC document and become visible at the partner. See Line comments.

Interface

Mon, 01 Jan 0001 00:00:00 +0000

Under Designer → Interface, the cashiering interface can be configured.

The STANDARD template is always used as the base template and is created automatically during the initial BE-POS setup. It can be copied, for example as a template for a custom layout.

Click to enlarge

Actions

Copy Template

Creates a copy of the selected template under the name assigned afterwards. Both the interface setup and the button setup are copied.

Item tracking

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany extends the Business Central standard so that item tracking (lot and serial numbers) is transferred consistently across companies. This keeps traceability intact beyond the company boundary – from the outgoing document to the warehouse receipt at the partner.

Supported are purchase orders, sales orders, sales and purchase invoices, and sales and purchase shipments.

Business value

End-to-end traceability of lots and serial numbers across companies.
Automatic assignment of tracking data at the receiver when items and tracking codes match.
Deviations land in the error log and can be corrected there.
Foundation for compliance evidence in regulated industries.

Focus areas

Inspect tracking on IC documents

The line menu of each IC document exposes the transferred item tracking.

JSON-REST Interfaces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is the entry point for JSON-REST interfaces in the BE-Commerce module.

Scope

Export endpoints for master data, prices, inventory, and status information
Import endpoints for sales orders, contacts, returns, and reservations
Consistent conventions for filters, request payloads, and responses

Guardrails

Slugs and endpoint names remain ASCII and consistent.
Required filters (for example webshop channel code) are mandatory per endpoint.
Payload changes must be aligned with webshop integration and downstream processes.

Order confirmation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

As soon as the receiving company creates a sales order from an incoming purchase order, BE-terna Intercompany reports back to the partner automatically. The purchasing company sees that the document has been picked up without asking.

Business value

Buyers get reliable feedback on the status of their order without contacting the partner company.
Differences between purchase order and confirmation surface early, because they are visible in the same IC flow.
Foundation for later Order changes on the same order.

Focus areas

Flow

After the receiver creates the sales order, the order confirmation is sent back to the sender as an IC document. The purchasing company sees it in the incoming transactions.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Click to enlarge

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-Code exposes an API that generates QR and barcode images on request. The response carries the image directly as a base64-encoded PNG, so you can embed it in documents, forms, and portals without extra steps.

Business value

Supports more than 90 barcode types for industry, logistics, healthcare, and postal services.
Returns images directly as base64-encoded PNG; a good fit for Word layouts, reports, and portals.
Offers fine-grained styling: scaling, rotation, padding, colors, human-readable text on 1D codes, and error-correction level on QR codes.
Wraps different encodings behind a single GET interface.

Functional focus

Unified HTTP GET interface

Every call returns a JSON object with two fields: data holds the image as a base64-encoded PNG, and message holds the status. You can embed barcodes server-side as easily as client-side.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Barcode Service is a container-based middleware service that Business Central and other applications call to generate QR and barcodes and to send messages to external channels. The service can run locally on your own server or as an Azure Container Instance.

Business value

Generates more than 90 barcode types on demand, from EAN-13 and Code 128 to QR Code and GS1 variants.
Embeds barcodes seamlessly into Word layouts and reports in Business Central.
Returns barcodes as base64-encoded PNG images, so they fit into any document or portal.
Provides a single middleware for messaging channels such as Microsoft Teams, Telegram, and WhatsApp.
Runs both on-premises and in Azure as Software-as-a-Service.

Functional focus

QR and barcode generation

The BE-terna Barcode Service creates one- and two-dimensional codes for all relevant industrial and postal standards. Calls use a simple HTTP GET interface; the response carries the image directly as a base64-encoded PNG.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is the business entry point to the BE-Commerce module. It is written for users who are new to the module and want to understand what it is used for, which master data must be prepared, and which daily tasks follow from that setup.

Who should read this page

E-commerce coordinators who support webshop-related business processes.
Customer service or sales users who review imported documents and contacts.
Key users who are responsible for setup, data quality, and stable daily operations.

What you do with BE-Commerce

BE-Commerce connects Business Central with a webshop. The module helps you to

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is the business entry point to Connector Commerce Interface to Fashion. It is written for users who need to place the connector for the first time and understand which fashion-specific master data is required in addition to the general BE-Commerce scope.

Who should read this page

Key users in a fashion context who maintain channels, colors, and attribute-based data.
Business users who need to understand which additional maintenance tasks exist beyond the BE-Commerce standard.
Teams that must distinguish between general BE-Commerce functionality and fashion-specific extensions.

What the connector adds

The connector extends the general BE-Commerce usage with fashion-specific requirements. This especially includes

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Controlled Sales Core supports day-to-day automotive supply workflows in Business Central, from delivery call-offs to dispatch control and transport handling. This page helps you understand where the solution is used and which pages you should start with.

Business Value

Less manual coordination between sales, shipping, and warehouse teams.
Clear handling of customer call-offs against blanket sales orders.
Faster creation of shipping and pick documents using reusable filters.
Traceable transport handling with carrier handoff and delivery details.
Better visibility of cumulative quantities and in-transit quantities.

Functional Focus

Delivery call-offs from blanket orders

You use document call-offs and delivery call-offs when customers continuously update required quantities and dates. The system keeps references, unloading points, and item-related data aligned for downstream processing.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Material Surcharges Management extends Business Central with structured maintenance of charges and charge prices. It helps you assign charges to items clearly, maintain prices by period, and use that information reliably in sales and purchasing.

Audience

This documentation is aimed at users in sales, purchasing, item master data maintenance, and key users who manage charges, pricing rules, and their presentation on documents.

Business value

Charges are maintained per item, quantity type, and unit in a traceable way.
Charge price rules can be managed by effective date and different relation types.
Changes to charge prices can flow into open sales and purchase documents.
The solution extends existing item, sales, and purchase processes instead of introducing a separate process area.

How you work with Material Surcharges Management

Charge assignment on the item

At item level, you define which charges are relevant for an item. You maintain the item number, item and charge unit, quantity type, and the desired document display. This keeps it clear which charge applies in which business context.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Handling Unit Management helps you define reusable packaging structures in Business Central, assign them to documents, and keep them consistent through posting. The solution combines packaging materials, contents, rules, and logistics processes into one end-to-end handling model for handling units.

Who is this documentation for?

This documentation is written for end users in operational roles who work with packaging processes every day:

Shipping and picking
Goods receipt and warehouse operations
Sales and purchasing document processing
Key users responsible for packaging master data

The content is structured so teams with limited Business Central experience can follow and apply the processes reliably.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany enables automated exchange of documents and master data between Business Central companies. The solution extends the standard with an end-to-end document flow from purchasing through invoicing, reduces manual reconciliation effort, and keeps data consistent across company boundaries.

The target audience is end users in purchasing, sales, logistics, and finance, as well as key users and administrators who are responsible for cross-company exchange.

Business value

Seamless integration into Microsoft Dynamics 365 Business Central with no additional interface.
End-to-end process coverage from sales order through shipment and goods receipt to invoicing.
Improved data quality through price and text validation between IC partners.
Lower manual effort thanks to automated document dispatch and automatic processing on the receiving side.
Reduced need for cross-company permissions through background processing without direct access to partner companies.

Functional focus

Extended logistics and document flow

Item tracking with serial and lot numbers is passed through across companies. Goods receipts and shipments can be created automatically from incoming IC documents. Drop shipments can be delivered and invoiced directly from the purchase order without manual intermediate steps.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Manufacturing extends Microsoft Dynamics 365 Business Central with additional capabilities for production planning, production order handling, purchasing, logistics, tool management, and costing and reporting. This documentation brings the main use cases together so that users and key users understand the business flow, the required master data, and the downstream processes in context.

Business Value

Brings daily tasks, KPIs, and navigation targets for manufacturing together in a dedicated role center.
Reduces manual maintenance through automatic defaults for routings, production BOMs, locations, and production orders.
Supports planning through enhanced planning worksheets, automatic planning runs, and production families.
Makes release, posting, correction, and reopening of production orders easier to trace and more reliable.
Connects production with purchasing, logistics, tool management, and costing in one connected process landscape.

Areas and Topics

Role center and daily orientation

The BE-terna Manufacturing role center combines the main entry points for items, production orders, routings, BOMs, capacities, and tasks. Users also see KPIs for their own and general production orders, delayed operations, and follow-up tasks for day-to-day control.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Master Data Management helps you move data from one leading company into other companies in a structured way, define clear rules for that transfer, and review differences in a targeted manner. The module is especially useful when several companies work with the same master data and changes should not be maintained separately in every company.

Typical use case

One company maintains certain master data centrally first. This data should then also be available in other companies. At the same time, not everything should be transferred without review. MDM helps you decide which data is transferred, which exceptions apply, and how you can review deviations later.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Printconnect connects Microsoft Dynamics 365 Business Central with PrintNode so that print jobs can be prepared centrally and forwarded to available printers. The solution extends standard printing in Business Central with cloud-based printer management, print-job tracking, and configurable print options.

Business Value

Connects Business Central with the printers that are available to the user through PrintNode.
Reduces manual effort for printer assignments and recurring print scenarios.
Supports print options such as color, duplex, collation, copies, and paper size.
Makes print history traceable for support and troubleshooting.
Checks whether the PrintNode service is reachable before a print job is sent.

Functional Scope

Feature	Benefit
Printer Management	Available printers become visible and manageable for Business Central.
Printer Setup	Print options such as collation, color, duplex, copies, and paper size can be maintained per printer.
Default Printer Assignment	Recurring print jobs can be assigned to a preferred printer.
Print Job Statistics	The number of print jobs supports transparency and cost analysis.
Print Job History	Individual print jobs remain traceable for support and troubleshooting.
Customized Paper Size	Printer-specific custom formats can be mapped in addition to standard sizes.

Documented Scope

Supported Editions

Microsoft Dynamics 365 Business Central Essentials Edition 19
Microsoft Dynamics 365 Business Central Essentials Edition 20

Supported Countries

Denmark
United States
France
Germany
Norway
Serbia
Spain
Sweden

Supported Languages

Danish (Denmark)
English (United States)
French (France)
German (Germany)
Norwegian (Norway)
Serbian (Serbia)
Spanish (Spain)
Swedish (Sweden)

Important Note for Initial Setup

During installation, Business Central should not already contain active local printers in printer management. This constellation can interfere with the setup and lead to unexpected installation errors.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Shipping Labels connects Microsoft Dynamics 365 Business Central directly with supported shipping providers so that users can create shipping labels, retrieve tracking information, and review shipping requests without switching to a separate carrier portal. The solution combines the shared setup in Business Central with carrier-specific onboarding so that operational users and key users can work with one consistent shipping model.

Business Value

Create shipping labels directly from operational documents such as sales orders, warehouse shipments, and shipment orders.
Control productive carrier, product, and service combinations through one shipping agent service setup matrix.
Reduce manual coordination by keeping carrier onboarding, request URLs, and request history in the same Business Central solution area.
Download generated labels, review tracking IDs, and generate same-day shipping reports from the app.
Troubleshoot failed requests with request and response data instead of relying only on generic carrier error messages.

Areas and Topics

Supported carrier landscape

Shipping Labels covers 12 main carriers. Their exact product and service combinations depend on the configured carrier account, but the supported landscape includes CargoLine, DACHSER, DHL Express, DHL Freight, DHL Shipping, DPD, DSV, FedEx, GLS, Hermes, PCH, and UPS.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Vendor Rating helps you evaluate vendors in Microsoft Dynamics 365 Business Central in a structured, objective, and traceable way. The solution combines automatically calculated operational indicators with manual assessments from audits and self-disclosures.

Business value

Uses existing Business Central data for quantity reliability, delivery time, complaints, and PPM values.
Complements automatic indicators with qualitative input from audits and self-disclosures.
Evaluates vendors with a consistent scoring model and clearly defined criteria.
Makes results transparent for operational analysis and management decisions.
Supports continuous improvement of purchasing and quality processes.

Functional focus

Configurable rating model

You define main criteria, subcriteria, thresholds, grading logic, and classifications to match your requirements. This allows vendor evaluation to reflect different quality and purchasing strategies.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

NOS Dispo is the replenishment planning module for NOS (Never-Out-of-Stock) items in BE-terna Fashion. It allows buyers to determine planned order quantities for colour-based staple items by period, detect shortfalls early, and keep the replenishment plan up to date automatically after release.

Business Value

Combines reference sales, depot quantities, corrections, and a planning factor in a single planning matrix.
Automatically identifies colours and periods where the projected closing inventory becomes negative (shortfall).
Preserves manually set corrections and planned order quantities when a released document is automatically rebuilt.
Supports two planning granularities: by variant (colour and size) or aggregated by colour.
Distributes planned colour quantities to variants using NOS size keys.

Planning Document and Structure

Each Dispo NOS document describes a planning period for one or more NOS items and optionally a vendor. The document header holds the planning type, period type (week, decade, or month), the number of periods before and after the work date, and item and colour filters.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

This documentation is currently under construction. Content will be available shortly.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

This guide walks you through the key processes and functions of the BE-terna Reactor Mobile Inventory app. The app is designed to simplify warehouse operations, manage stock efficiently, and improve accuracy through mobile scanning.

Setting up the module

To use the module, you need our Reactor Client and the BE-terna Reactor Platform Core app (AppSource). Please refer to the help page in the BE-terna Reactor Platform Core app AppSource listing to obtain and install the client, or contact us if you need assistance.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

This guide walks you through the key processes and functions of the BE-terna Reactor Mobile Logistics app. The app enables efficient warehouse activities on mobile devices.

Supported logistics documents

The module supports the following warehouse activities:

Warehouse put-away
Warehouse pick
Warehouse movement
Put-away
Pick
Transfer

Setting up the module

Overview

Mon, 01 Jan 0001 00:00:00 +0000

This guide walks you through the key processes and functions of the BE-terna Reactor Mobile Manufacturing module. The app enables production staff to post production order data efficiently via mobile devices. This reduces paper consumption, improves accuracy, and accelerates output posting directly in Microsoft Dynamics 365 Business Central.

Supported production activities

The module supports the following manufacturing processes:

Output posting
Component consumption
Time recording (setup time and run time)
Scrap posting

Setting up the module

Overview

Mon, 01 Jan 0001 00:00:00 +0000

The Reactor Physical Inventory module enables you to perform physical inventory efficiently and easily on mobile devices. This includes working with physical inventory journals and physical inventory orders. With the scanning functions, users can select locations and items, enter quantities, and make real-time adjustments directly in Microsoft Dynamics 365 Business Central, which significantly simplifies the inventory process.

Setting up the module

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Various mobile solutions can be installed on top of BE-terna Reactor Platform Core.

The available modules are listed in the subordinate documentation areas on this page.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

The documentation for the Reactor Platform Core solution for Business Central is published on the following website:

Reactor Platform Core documentation

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Professional Services extends Microsoft Dynamics 365 Business Central with capabilities for service organizations that rely on recurring revenue, contract-based services, and service-oriented processes. The solution connects sales, contract management, service, and billing in one continuous workflow.

Typical use cases

Recurring billing for SaaS, rental, financing, maintenance, and support
Sales quotes and sales orders with related sales contracts
Periodic single, batch, and monthly billing
Billing for tickets and work orders
Management of objects, installations, and components
Integration of external ticketing systems through API

Functional focus areas

Sales and contract management

Professional Services supports the creation of sales quotes, sales orders, and sales contracts. Recurring services can be embedded directly in quote and order processes and prepared for later billing.

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Project provides the functional foundation for project-based work in Microsoft Dynamics 365 Business Central. The solution helps you manage project processes in one consistent system flow, from initial costing and execution to final invoicing.

Business value

Creates transparency for project status, costs, delivered services, and open tasks.
Connects pre-sales preparation, operational project execution, and financial evaluation.
Reduces process breaks between project management, purchasing, invoicing, and controlling.
Supports traceable decisions with one consistent data basis and clear process guidance.
Can be adapted flexibly through industry-specific extensions and integrations.

Functional focus

End-to-end project management

From project setup and structuring to document handling, progress tracking, and final settlement, all relevant information stays in one project context. This improves collaboration across teams and reduces coordination overhead.

Prerequisites

Mon, 01 Jan 0001 00:00:00 +0000

Before we can play through the key usage scenario we need some setup and master data as prerequisites.

Switch your settings to the BE-POS user role.

Click to enlarge

Search for Basic Setup Card.

Click to enlarge

With the Basic Setup Card, you set up templates for your cash register setup.

Click to enlarge

Base Setup

Field	Description
Insert role center	Inserts the cash register role center
Initialize Standard Template	Initializes the standard template for the cash register design
Initialize Demo Data	Initializes CRONUS demo data
Demo Location	Demo location for CRONUS demo

By default, it is always recommended to call this function once and then adjust the data regarding cash register setup, discounts, and so on. Via the demo location you can use any location for test purposes.

Replication

Mon, 01 Jan 0001 00:00:00 +0000

Under Data Transfer → Replication, the publications and their subscribers are configured, thereby controlling the transfer of master data to the cash registers.

Click to enlarge

Publication

A publication is the combination of multiple tables whose data or data changes are to be synchronized to the cash registers.

General

Click to enlarge

Field	Description
Name	The name of the publication
Description	The description of the publication
Items	Number of monitored tables
Subscriptions	Number of assigned cash registers

Items

Click to enlarge

Resource

Mon, 01 Jan 0001 00:00:00 +0000

Under Assignment → Resources, resources can be allowed and/or excluded per cash register, per location, or for all cash registers.

Click to enlarge

Role center

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The Intercompany role center is the central entry point for everyone who works with IC documents regularly. It bundles navigation, key figures, and actions in one place so that typical tasks can be done without detours.

Access in Business Central

Pick the role center through the user/role assignment in user management or through My settings.

Click to enlarge

Prerequisites

User has the right permissions (see Permissions).
Intercompany is configured at the company level.

Activities

Entry point for partner maintenance, transaction overviews, and the error log.
Direct navigation to the job queue for retries and error analysis.
Start common actions for sending, accepting, and remediating IC documents.

Click to enlarge

Sales Data

Mon, 01 Jan 0001 00:00:00 +0000

The Sales Data provides an overview of the sold items, services, and posted accounts per sales line.

Click to enlarge

Using the Receipt function, you can open and reprint the related receipt or receipt card.

Click to enlarge

Glossary and roles

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This glossary consolidates the most important terms and roles of MDM for the first entry into the solution. It helps users read and apply relations, rules, and review steps with one shared business understanding.

Business value

Standardizes the core MDM terminology across business teams, master-data maintenance, and review work.
Makes communication easier between users, business owners, and administrators.
Reduces misunderstandings around relations, DSR, substitutions, and consistency checks.

Content focus

Core terms

Term	Meaning	Typical context
Source company	Company from which business-relevant data is read or compared with the target context.	Data origin, review start, reference context
Target company	Company in which data arrives, is checked, or is evaluated from a business perspective.	Data receipt, comparison, correction
MDM relation	Central business mapping between tables, companies, and processing rules.	Relation list, relation card
DSR	Abbreviation used for Selected Record Distribution and the business term for controlled record distribution in MDM.	Distribution matrix, DSR page, relation maintenance
DSR filter	Rule that excludes records from distribution for all or selected target companies.	Distribution filters, distribution matrix
Relation structure	Structured representation of which fields, levels, or relationships belong to one relation.	Relation Structure, field logic
Dependency	Rule that describes when a value or record depends on other information.	Dependency Lines, control rules
Exclusion	Rule that deliberately excludes specific fields or situations from processing.	Relation Exclusions, exceptions
Substitution	Replacement or derivation of a target value based on defined rules.	Substitutions, field-value control
Consistency check	Review that verifies whether records or field values between source and target contexts match the expected state.	Consistency Check, review results
Review entry	Documented result of a relation review or consistency check.	Check Entries, follow-up
MDM start area	Central entry point for working with relations, activities, and follow-up actions.	Profile, daily entry

Roles and permissions

Role	Typical task
MDM - Read	Read MDM content, understand results, and get oriented
MDM - User	Use relations, rules, and operational MDM functions in day-to-day work
MDM - Administrator	Own the setup, maintenance, release, and business control of MDM
MDM responsible user	Profile that uses the central MDM start area as the entry point for activities and insights

Core logic between relation, rule, and review

The MDM relation is the business core object. Based on that, relation structure, dependencies, exclusions, and substitutions define the expected data behavior. Consistency checks then show whether the result in the target context matches the defined frame or whether follow-up work is required.

Glossary

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This glossary consolidates the key terms and roles used in Handling Unit Management. It helps teams apply the same business language across master data, packaging structures, and operational packaging assignments.

Business value

Standardizes terminology for packaging means, packaging materials, contents, and hierarchy levels.
Makes collaboration easier across master data maintenance, order processing, and warehouse operations.
Reduces misunderstandings around alternatives, weights, and document assignments.

Content focus

Core terms

Term	Meaning	Typical context
Packaged goods	Generic business term for the goods that are packed, moved, or contained in a structure.	Item, content of a packaging unit
Content	Concrete item to be packed or already packed within a packaging structure or packaging assignment.	Content line, item in the structure
Package	Movable real-world combination of packaging means and packaged goods.	Shipping unit, finished package
Packaging means (Packmittel)	Structural packaging component that contains, groups, or organizes contents or other packaging components.	Pallet, box, KLT, insert
Packaging material (Verpackungsmaterial)	Physical empty unit of a packaging means with its own quantity, availability, and often its own weight.	Packaging-material line, warehouse-managed material
Packaging aid	Supporting packaging component used together with packaging means.	Accessory, separator, auxiliary material
Outer packaging	Higher packaging level that contains multiple units.	Carton, layer, secondary packaging
Packaging unit	Smallest defined pack unit with a fixed quantity.	Single, packaging unit
Handling unit	Highest movable unit within the structure.	Master, load carrier
Packaging structure	Hierarchical model of packaging means, aids, and contents as a reusable template or real structure.	Structure definition, real packaging
Assignment	Concrete link between a structure, hierarchy level, or line and a master-data or document context.	Assignment field, hierarchy, document context
Document packaging structure	Document-specific variant of a packaging structure that is proposed, selected, or maintained as an alternative for a specific context.	Sales, purchase, transfer
Packaging assignment	Operational use, adjustment, and registration of the real structure on the concrete document.	Shipping, warehouse shipment, posting
Alternative	Variant of a packaging structure for the same business context.	Customer-specific or regional packaging
Net/gross weight	Weight of the content without and with packaging; these values drive shipping and validation checks.	Calculation, shipping, registration
Overload	Situation in which the gross weight or another defined limit is exceeded.	Validation rule, weight limit

Example structure levels

The following illustration shows the basic relationship between packaging aids, packaging materials, packaging units, and the handling unit.

Version 27.0.0 / 26.2.0

Mon, 01 Jan 0001 00:00:00 +0000

Summary

This release state groups the changes for versions 27.0.0 and 26.2.0. Key topics are quote printing, report selection, updates to the calculation matrix, and improvements in work orders and demo data.

27.0.0 / 26.2.0 — 2025-10-29

New features

39364 - Reworked GetPrintOptions
38754 - Extended quote printing
30478 - Extended project report selection
38754 - Adjusted the quote print layout
38866 - Stored report print control as fields on the project
37853 - Added a report for posted sales credit memos
38258 - Added Job No. in the Core App
38258 - Moved Job No. handling in purchasing out of the app
20556 - Revised web demo data
38512 - Extended the calculation matrix for financing
38514 - Enabled work orders without a project

Bug fixes

39265 - Unit code and unit on attributes were validated incorrectly
39267 - Werartnr. on attributes could not be created or edited
39190 - Manual price could not be changed on the work order
38852 - Fixed the error when creating a new contingent template on the SLA template card
38480 - Fixed the creation of work operations from work tasks

Analysis

Mon, 01 Jan 0001 00:00:00 +0000

Discount Reason

Item Category

An item category evaluation analyses the sales performance of different item categories. The evaluation is based on sales figures reported per day and month. A day filter allows sales to be filtered to a specific day.

Turnover

The turnover list analyses the turnover of different locations and cash registers. The evaluation is based on sales figures, and the data is grouped into different categories. A day filter allows sales to be filtered to a specific day. In addition, the view can be switched between location and cash register.

API reference

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page documents the HTTP GET interface of BE-Code in full: the base request, all optional parameters, and the complete list of supported barcode types.

Context

Every call returns a JSON object with two fields:

{
  "data": "...",
  "message": "..."
}

data contains the barcode image as a base64-encoded PNG (with the data:image/png;base64, MIME prefix).
message carries a status message for the request.

Prerequisites

A BE-Code instance reachable over HTTPS.
Basic authentication credentials. Credentials for a test instance are available from BE-terna support on request.

Base request

Every call includes at least the parameters type and content:

Basic Setup Wizard

Mon, 01 Jan 0001 00:00:00 +0000

As long as no cash register setups have been set up yet, this notification appears on all standard Business Central role centers and BE-POS setup pages:

Click to enlarge

If you click Set up BE-POS extension, the basic setup wizard opens. You can use it to define the initial setup for a cash register.

If you click Do not show again, this notification is no longer shown for the current user. If the current user has sufficient permissions to set up the cash register, the notification can also be deactivated for the entire tenant.

Version BC 20

Mon, 01 Jan 0001 00:00:00 +0000

Summary

On BC 20 Intercompany was extended by automatic warehouse receipts, the role center, order confirmation, IC resource validation, a more robust error log, and numerous fixes around partial shipments and invoicing.

20.0.73 — 2023-07-28

New features

New field Transfer line comments in the intercompany setup enables transfer of purchase and sales line comments.

20.0.72 — 2023-07-27

New features

For incoming sales orders you can decide which description is used on the sales order line when it deviates (new field Deviating description on sales order line on the intercompany partner).

20.0.71 — 2023-07-10

Other changes

New event OnBeforeValidateReturnReasonCodeInSalesLine() controls the use of the return reason code.

20.0.70 — 2023-07-05

Bug fixes

Fixes in the role center and the file-import status display.

20.0.69 — 2023-07-04

New features

With automatic file import active, the incoming transactions provide the Error log (file import) action and the role center shows file-import status information.

Bug fixes

The file error log could not be opened once entries existed – fixed.

20.0.68 — 2023-07-03

Bug fixes

Automatic posting of incoming purchase invoices now also works with Create purchase invoice (standard).

20.0.67 — 2023-06-29

New features

Processing an incoming shipment through the warehouse receipt no longer requires the current user to be configured as a warehouse employee.

20.0.66 — 2023-06-23

Bug fixes

Error Status must be open on incoming purchase invoices (invoicing through the order) removed.

20.0.65 — 2023-06-20

New features

The Send IC document action is available on posted sales invoices and posted sales shipments.

20.0.64 — 2023-06-19

Bug fixes

Error IC partner … does not exist with the current company code removed.
When using the warehouse receipt, partially shipped item charges were fully shipped – fixed.

Other changes

Internal function to detect that a document was created by IC processing.

20.0.63 — 2023-06-15

Bug fixes

An incoming shipment with over-delivery through the warehouse receipt caused a status error – fixed.
Completion message for Run line actions … on the IC incoming transactions was clarified.

20.0.62 — 2023-06-13

New features

The calculation method for automatic assignment of item charges can be configured on the IC partner. Empty means no automatic assignment.
When creating sales orders from incoming purchase orders, item charges can now also be calculated automatically.

20.0.61 — 2023-06-13

Bug fixes

Incoming purchase invoice with over-delivery caused a status error – fixed.

20.0.60 — 2023-05-04

Bug fixes

Order changes with a changed Requested delivery date caused an error when Promised delivery date was already set. The promised date is now cleared.

20.0.59 — 2023-04-12

Bug fixes

Transfer to the sales document failed with an unknown salesperson on the IC document – fixed.

20.0.58 — 2023-03-10

New features

Posting an incoming shipment through the warehouse receipt now also accepts non-item lines (G/L accounts, item charges); same for the related purchase invoice and credit memo. Non-item lines are shipped directly through the purchase order.

Bug fixes

Posting error with negative quantity on a purchase line removed.

20.0.57 — 2023-02-15

New features

In sales, item charges (items) are recorded as IC partner references and fully transferred to the partner.

Bug fixes

Incoming purchase credit memos applied to an existing purchase return order and posted immediately did not invoice lines added by the IC partner – fixed.
Missing translation added.

20.0.56 — 2023-02-10

New features

On incoming purchase credit memos, lines added by the IC partner are taken into the purchase return order when Use existing purchase return order is active.
The default IC partner G/L account number is also taken into sales document lines.

Bug fixes

Wrong prices in automatically generated IC purchase documents when the return reason code was used – fixed.

20.0.55 — 2023-01-26

Bug fixes

Shipping and invoicing a sales document simultaneously used to send the IC shipment after the IC invoice, which caused the partner to skip automatic invoice processing. The IC shipment is now sent before the IC invoice.

20.0.54 — 2023-01-24

New features

Partial shipments through the warehouse receipt.
Partial invoices for orders via warehouse receipt (new option Accept purchase partial invoices on the IC partner card avoids user prompts).

Other changes

Known limitation: non-item invoice lines are ignored when shipping through the warehouse receipt.

20.0.53 — 2023-01-18

Bug fixes

Upgrade fix.

20.0.52 — 2023-01-18

Other changes

New upgrade tags for the data upgrade from 20.0.51.

20.0.51 — 2023-01-17

Other changes

Preparation for moving feature management Intercompany to the new IC setup (fields moved to table 443 Intercompany Setup).
Preparation for relocating long fields on the IC Partner table (fields 5399245 and 5399214).

20.0.50 — 2023-01-13

Bug fixes

Incoming purchase documents other than invoice and credit memo were not processed – fixed.

Other changes

Role center translations completed.

20.0.49 — 2023-01-13

New features

Processing of incoming transactions no longer aborts on an error. Failing transactions are marked and highlighted in red. Show last error exposes details.

20.0.48 — 2023-01-12

New features

Role center extended with sales order processing activities.
Configure batch available in the role center.

20.0.47 — 2023-01-11

New features

InterCompany role center available and selectable through My settings.

20.0.46 — 2023-01-11

New features

With IC resources active, validating a resource number on a purchase line checks whether the default IC partner resource number is maintained on the resource card.
Sending a purchase order with IC resources enabled checks that purchase lines of type Resource carry an IC partner reference.
Adjusting a purchase order by an incoming purchase invoice automatically converts new IC-resource lines to a resource as soon as a configured intercompany resource is found.
Receiving IC shipments throws an error and rejects acceptance when On incoming shipment is empty on the IC partner.

Bug fixes

Auto-detecting the unique location for warehouse receipts failed on resource lines – fixed. Only item lines are considered.
Incoming IC order changes failed when a unit of measure was missing on the IC line – fixed. For items and resources the line is now checked against the base unit of measure.

20.0.45 — 2023-01-11

Other changes

Internal preparations; no functional changes.

20.0.44 — 2023-01-10

Bug fixes

An incoming IC G/L account in an IC sales document was not mapped to a resource even when configured in the intercompany chart of accounts – fixed.

20.0.43 — 2023-01-05

New features

Error log for automatic file import of IC transactions, reachable from the Intercompany setup page.

20.0.42 — 2023-01-03

Bug fixes

Partial shipments through the warehouse receipt failed from the second partial shipment onwards – fixed.

20.0.41

Other changes

Adjustments to allow using an alternative XMLport.

20.0.40

Bug fixes

Restoring an IC transaction lost item tracking – fixed.

20.0.39 — 2022-10-10

New features

New IC document Shipment for the outgoing shipment.
On an incoming shipment the warehouse receipt is created and posted.

Buttons

Mon, 01 Jan 0001 00:00:00 +0000

Under Designer → Buttons, the function buttons for cashiering can be configured.

The button designer makes it possible to change the position, caption, background color, and font color. Buttons that are not required can also be deactivated.

Note: The STANDARD template serves as the copy template and cannot be changed. If changes to the buttons are required, a copy of the STANDARD template must first be created.

Click to enlarge

Cash Register Start

Mon, 01 Jan 0001 00:00:00 +0000

Cash register start is initiated via the Start button.

Click to enlarge

First, the cashier must identify themselves by entering the relevant cashier code.

Click to enlarge

If the cashier code is not known, it can be searched for and selected via the magnifying glass button.

Click to enlarge

If a password is stored for the cashier, it is then requested in the input field.

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

Global Facility

Within the Be-terna Project facility, the Open Masterdata facility can be accessed as follows:

Click to enlarge

General

A window opens which first allows the configuration of the data package to be transmitted by Open Masterdata by default. \

Furthermore, the behavior in dealing with articles related to the requested article can also be determined. If these are also imported, the data package can also be used for these articles.

Import of DATANORM

Mon, 01 Jan 0001 00:00:00 +0000

In the event that a unit is stored in DATANORM that cannot be managed in the master data, the “Ignore missing units of measure” field in the DATANORM setup can be used to specify that when DATANORM is imported, it should be asked whether a new unit of measure should be maintained. Otherwise, no message will be displayed and the items will be transferred without a unit of measure.

Click to enlarge

Importing a Project Document

Mon, 01 Jan 0001 00:00:00 +0000

BE-Project offers various options for importing a bill of quantities directly. The basic procedure is always the same: First, you create a new document with an empty bill of quantities (see [Creation of a new document](/BE%2Dterna-Project-Documentation/Project Documents/Creation-of-a-new-document)). If items have already been entered in the bill of quantities, they will be overwritten during an import.
For the import, click Actions on Import and then on Documents. There you select a file format for the import. The explorer opens, where the GAEB file can be selected.

Intercompany partner

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The partner card describes a concrete business partner in the intercompany exchange. Settings on the partner level override the global switches from the intercompany setup and define the transport channel, file format, and process-specific behaviour.

Prerequisites

Intercompany setup is completed.
The partner company is known (company name or external IC code).
The exchange method (server directory, Azure File Share, or direct company access) is agreed with the partner.

Recommended order

Create the partner, record the code and company/path information.
Pick the import/export implementation (XMLport) – keep the default for the standard format.
Set process options for purchase, sales, drop shipment, and warehouse receipt.
Send a test document to the partner and verify the outcome in the role center.

Setup building blocks

General

Define the partner code, base information, and whether the partner actively participates in the exchange.

Item Category

Mon, 01 Jan 0001 00:00:00 +0000

Under Assignment → Item Category, item categories can be allowed and/or excluded per cash register, per location, or for all cash registers.

Click to enlarge

Manage licenses

Mon, 01 Jan 0001 00:00:00 +0000

The “Manage Licenses” action takes you to the BE-terna Project License.

Click to enlarge

Master Data and Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes master data and basic setup in BE-terna Manufacturing. First prepare the central production setup, then make sure that items, routings, production BOMs, locations, and additional validation logic are maintained so that later production orders work with consistent defaults.

Prerequisites

Core manufacturing functionality in Business Central is set up and users can access items, routings, production BOMs, production orders, and Manufacturing Setup.
Number series, locations, work center groups, and vendors for subcontracting are aligned from a business perspective where required.
Item templates or similar master data defaults are available if consumption and output locations should be prefilled systematically.

Recommended Sequence

Complete all Manufacturing-specific switches and standard values in Manufacturing Setup.
Maintain item templates and item master data including location defaults, item tracking, and optional item versions.
Create or open routings and production BOMs directly from the item card.
Configure additional rules for routing link codes, location transfers, and work center groups.
Test the effect with a sample item and an initial production order.

Area: Master Data and Setup

Use Manufacturing Setup as the central control point

Several BE-terna Manufacturing extensions are activated centrally through Manufacturing Setup. This includes automatic defaults for Assigned User ID in the production order, a Default Gen. Bus. Posting Group, a Default Output Location Code, transfer of production details, validation logic for routing link codes, and calculation methods for output and consumption.

Order changes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

If the partner changes a purchase order after sending it, BE-terna Intercompany can propagate the change to the sales order that was created from it. This page describes the conditions for that and how deviating item numbers are handled.

Business value

Later quantity and price changes stay in sync between the purchase and sales sides.
No manual cancel-and-recreate of the sales order.
A clear rule for item-number changes (only before shipment).

Focus areas

Activation on the IC partner card

On the IC partner card you allow order changes on already received sales orders. Changes coming in from a re-sent purchase order then take effect on the existing sales order.

Permissions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany ships its own permission sets that are granted in addition to the Business Central standard IC permissions. This page describes the sets and their typical assignment.

Access in Business Central

Permissions are managed through permission sets and user management.

Prerequisites

Administrator rights to assign permission sets.
Knowledge of which roles in the company work with Intercompany.

Activities

Assign the matching permission set to every IC user.
Review and adjust assignments when roles change.
Use a test company to validate new roles before rollout.

Fields and actions

Permission set	Purpose
`BET ICY BASIC`	Basic rights for every IC user; covers reading and working with IC documents.
`BET ICY SETUP`	Additional rights to maintain the intercompany setup and IC partners.
Related BC standard sets	Must be granted alongside so that sales and purchase keep working.

Monitoring and troubleshooting

Missing permissions often only surface when accepting an IC document. Check the user’s permission sets first in such cases.
Job queue and error log require additional standard rights.

Best practices

Apply least privilege: grant BET ICY SETUP to administrators only.
Audit permissions periodically, especially after rollouts or upgrades.

Purchase invoice

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

An incoming IC purchase invoice can either be created as a new purchase invoice or invoiced through an existing purchase order. This page describes both variants and their implications for partial invoices and vendor references.

Business value

Flexibility: a new invoice for simple cases, invoicing through the purchase order for automated end-to-end flows.
Partial invoices stay stable as long as the purchase order ships automatically.
The vendor invoice number can optionally be embedded into a custom number via a placeholder.

Focus areas

Create a new purchase invoice

By default BE-terna Intercompany creates a new purchase invoice for an incoming IC invoice. This variant is simple to run and suits cases where no related purchase order exists or no link is wanted.

Quick Start

Mon, 01 Jan 0001 00:00:00 +0000

The following steps explain how to create a new BE-terna Project client in the BC Client and import initial or demo data.

Note: After each step, Seite aktualisieren (F5).

Schritt 1

Open the Function Management list in the current client
→ Enable Feature Update: New Sales Price Calculation for all users
Click to enlarge
Background:
Some time ago, a change was introduced in the standard version of Business Central regarding sales price calculation. This feature is not currently automatically updated by default, so it must be manually enabled for each tenant.

Schritt 2

Receipt

Mon, 01 Jan 0001 00:00:00 +0000

In the Receipt Archive, you can search for receipts and reprint them.

Click to enlarge

From the respective receipt, you can open the Receipt Card, which shows the sales, payment, and discount lines.

Click to enlarge

Resources

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Resources such as services or internal capacity can be used in IC exchange when the resource card carries an IC partner reference. This page describes how BE-terna Intercompany validates, transfers, and resolves resources at the receiver.

Business value

Services and internal capacity can be carried on IC documents just like items.
Automatic validation makes sure only resources with a stored IC partner reference are sent.
On the receiver side, incoming IC resources are automatically mapped to the local resource.

Focus areas

Activation in the intercompany setup

Enable IC resources globally in the intercompany setup. The following mechanisms then apply.

Sales

Mon, 01 Jan 0001 00:00:00 +0000

The sales mode of the cash register opens with the Sales button after cashier login.

Click to enlarge

If the cash register is set up accordingly, a salesperson must be entered before every receipt.

Click to enlarge

Input Item

After entering the salesperson number, the POS program is in sales mode.

Click to enlarge

For the sales transaction, the barcode can either be scanned or entered manually if the scanner is not working.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page walks you through the basic setup of the BE-terna Barcode Service and helps you pick the right deployment model. The service ships as a container image and runs either locally on a Windows server or as an Azure Container Instance.

Prerequisites

Access to the BE-terna Azure Container Registry becode.azurecr.io. Authentication uses tokens created in ACR. One token or password per customer.
A valid SSL certificate as a .pfx file for HTTPS delivery.
Depending on the deployment model:
- On-premises: Windows Server build 22H2 or later, at least 1 CPU core, 1 GB RAM, and 10 GB of free disk space; installed Docker Engine and Docker Compose.
- Azure: active Azure subscription, Azure CLI or Azure portal access, optionally Azure Key Vault with an Azure AD service principal for certificate management.

Recommended order

Choose the deployment model: on-premises or Azure Container Instance.
Pull the container image from the registry and start the service.
Configure the certificate and passwords.
Maintain the BE-terna Barcode Service setup in Business Central and verify the connection.

Setup building blocks

Pick a deployment model

On-premises: A good fit when you already run Windows Server infrastructure and want to host the container yourself. See Set up an on-premise container.
Azure Container Instance: A good fit when the service should run in the cloud without your own server infrastructure. See Set up an Azure Container Instance.

Authentication and passwords

Use one ACR token per customer instead of the registry admin account.
Set a strong user password for the BE-terna Barcode Service and configure the same value in the BE-terna Barcode Service setup in Business Central.
Protect the certificate path and certificate password; the certificate must be reachable inside the container at C:\certs\cert.pfx.

Verify the connection in Business Central

In the BE-terna Barcode Service setup, enter the service URL (for example https://<fqdn>:1880/becode) and the basic authentication credentials.
Use the Check connection action to send a test request to the container.

Process Notes on secure operation Key guardrails for certificates, passwords, and registry access. +

Name the certificate file exactly cert.pfx and store it in the volume mapped from the host.
Use the default demo password only for testing; always set an individual password in production.
Do not store ACR tokens in repositories or unencrypted scripts; use Key Vault or a secure variable store.
In Azure Container Instance, never expose the container publicly without HTTPS or a reverse proxy.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the basic setup of BE-Commerce from an end-user perspective. It shows which decisions are needed before go-live, which data should be maintained first, and in which order you make the module ready for operations.

Who this page is for

Key users who set up a new webshop channel or extend an existing one.
Business owners for master data, country logic, and release rules.
Users who need a complete picture of the setup scope before starting detailed maintenance.

Prerequisites

Access to the relevant setup pages in the BE-Commerce module.
Aligned ownership for channels, data maintenance, and release checks.
Baseline decisions for languages, countries, pricing logic, and import/export behavior.

Recommended Order

Define webshop channels and global setup values.
Maintain master data and mappings per channel.
Align validation and release rules for daily operations.
Test the relevant follow-up processes with sample data.

Relevant Setup Areas

Area	Why you need it	Typical decision
Webshop Channel	Controls the overall behavior of one shop	Which languages, countries, and customer defaults apply?
Master Data	Enables categorization and multilingual output	Which categories, attributes, and mappings are mandatory?
Validation and Release Logic	Stabilizes data quality and processing	Which mandatory fields and checks must be fulfilled?
Follow-Up Process Testing	Verifies operational readiness	Do import, release, and export run successfully with sample data?

Channels and Core Parameters

Define channel code, description, languages, and countries.
Maintain required mappings and posting-related information per channel.
Align import and export behavior for each interface context.

Master Data and Mappings

Maintain categories, attributes, and channel-specific mappings.
Align translations for multilingual output.
Use the detailed master-data pages as the operational drill-down.

Quality and Release Logic

Define mandatory fields and validation rules for releases.
Align responsibilities for data quality and corrections.
Re-test major changes with representative test cases.

Initial Master Data

Before users start working with the module in daily operations, at least these basics should be complete:

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Setup Goal

This page describes the core setup for Connector Commerce Interface to Fashion from an end-user perspective. It shows which additional settings must be checked compared to BE-Commerce and how to prepare the fashion-specific master data for daily operations.

Who this page is for

Key users who set up or extend a fashion webshop.
Users who align colors, attributes, and country logic for the webshop.
Teams that need to make sure the business setup is ready before the first live run.

Prerequisites

Access to the relevant setup pages in the Commerce Interface and BE-Commerce context.
Defined webshop channels, languages, and countries for the connected shops.
A dedicated integration user for data exchange via web services.

Setup Steps

First confirm that the general BE-Commerce setup is complete.
Create the required webshop channel with languages, countries, and core parameters.
Add the fashion-specific master data such as colors, attributes, and categorization.
Align validation options and release logic for later data publication.
Finally clarify the technical connection and test one full process with sample data.

Relevant Setup Areas

Area	Why you need it	Typical decision
Webshop Channel	Business basis per shop	Which languages, countries, and sales locations apply?
Country and Pricing Logic	Correct posting and assignment	Which price groups, shipping charges, and voucher types apply per country?
Validation Options	Data quality before release	Which mandatory checks must be active per channel?
Fashion Master Data	Variant and attribute logic	Which colors, attributes, and categories are needed in the shop?
Technical Connection	Coordination with data exchange	Which endpoints and handover rules are relevant for operations?

Define the Webshop Channel

Create one channel per shop and maintain the control data relevant to the connector. This includes the location group, the sales location for webshop documents, allowed contact changes, and the active languages.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page guides you through the base setup of Controlled Sales Core. The goal is a stable operational start so delivery call-offs, dispatch control, and transport processing work together smoothly.

Prerequisites

Permissions for setup and administration in Business Central.
Core master data for customers, items, locations, and shipping agents is available.
Number series for transport documents is defined with the business team.

Recommended Sequence

Open Controlled Sales Core Setup and define core parameters.
Maintain transport number series and create base data.
Create dispatch control records for recurring daily routines.
Run an end-to-end test with sample documents.

Setup Building Blocks

Controlled Sales Core Setup

Use the setup page to control key switches for call-off and shipping behavior. For the first rollout, focus on these fields:

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to establish the baseline for MDM. The sequence is intentional: first define companies and defaults, then build relations, and only after that use rules and reviews in a reliable way.

Prerequisites

MDM is installed in the environment and the responsible users work with an appropriate MDM profile.
It is clear from a business perspective which companies should act as source and target companies in MDM.
Ownership for relation maintenance, release, and follow-up work is aligned between business teams and administration.

Recommended sequence

Select the managed companies and define the default source context.
Review central MDM settings such as routing template defaults, background processing, and the active MDM version.
Create the first MDM relations for the relevant tables and assign source and target companies.
Decide per relation whether Selected Record Distribution with DSR should be used and prepare the related distribution behavior.
Add dependencies, exclusions, DSR filters, and substitutions where business-specific control is required.
Review the relation, move it in a controlled way to Released, and run the first consistency checks.

Setup components

Define companies and the default context

The MDM Setup Wizard starts with the selection of companies that should be configured for MDM. In this step, decide which companies are managed in the module and from which default source company new relations are typically created.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the initial technical and functional setup of BE-terna Printconnect. First, you prepare PrintNode in the user context. Then, you connect Business Central with the printers that should be available for print jobs.

Prerequisites

BE-terna Printconnect is installed and enabled in the target system.
The user has access to the PrintNode website and can generate an API key there.
The PrintNode Client is installed on the workstation.
For the initial setup, Business Central should not already contain conflicting local printer entries in printer management.

Recommended Sequence

Create the PrintNode account, confirm the email address, and install the PrintNode Client.
Retrieve the API key and API URL from PrintNode.
Open the BE-terna Printconnect Setup page in Business Central and enter the connection details.
Select the required printers and verify the first synchronization in printer management.

Click to enlarge

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains the shared setup logic of Shipping Labels in Microsoft Dynamics 365 Business Central. Before you configure a specific carrier, prepare the common master data, create the required shipping agents and services, and complete the global Shipping Labels setup so that later label requests are based on consistent data.

Prerequisites

Shipping Labels is installed and available in the Business Central environment.
The required carrier accounts, API credentials, customer numbers, or onboarding data are available from the shipping provider.
Sender and recipient master data such as addresses, contact data, phone numbers, and email addresses are maintained with the quality required by the target carrier.
Users can access the pages for shipping agents, shipping agent services, shipping agent service setups, and the central Shipping Labels setup.

Recommended sequence

Clarify which carriers, products, and service options are required in the business process.
Prepare the master data for addresses, package handling, weights, dimensions, and Incoterms.
Create the shipping agents and shipping agent services in Business Central.
Maintain the shared Shipping Labels setup, including assigned source types and Incoterms.
Build the shipping agent service setup matrix for the valid carrier and service combinations.
Complete the carrier-specific properties, credentials, and tests on the corresponding carrier setup pages.

Setup components

Prepare master data before the first label request

Successful label requests depend on consistent business data. In practice, the most important preparation is not the carrier page itself, but the quality of the sender and recipient data that later flows into the request.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Before you rate vendors, configure the core parameters for BE-terna Vendor Rating. This setup defines the time frame, scoring logic, and classification model that all later evaluations and reports are based on.

Prerequisites

BE-terna Vendor Rating is installed and available in Business Central.
You have access to the setup area as well as the relevant master and transaction data.
The rating period, scoring logic, and desired vendor classification have been aligned from a business perspective.

Recommended order

Maintain the rating setup with periods, total score, and business criteria.
Define grade percentages so manual ratings can be converted into points.
Define classifications with percentage thresholds.
Optionally create an example setup as a starting point.
Complete the rating criteria schema, thresholds, and vendor-specific settings.

Setup components

Rating setup

The rating setup defines the basis for later evaluations. This includes the relevant posting period, the maximum score, and the business criteria that are taken over from Business Central.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the required configuration for NOS Disposition Planning. You first set the global planning parameters in the Fashion Planning Setup, ensure that the relevant items have NOS colours assigned, and create NOS size keys for variant distribution when needed.

Prerequisites

BE-terna Fashion is installed and accessible.
Items and their colours exist in the system.
Locations, number series, and vendor master data are set up.
Users have access to the Fashion Planning Setup and the item master.

Recommended Order

Open the Fashion Planning Setup and maintain all NOS-specific parameters.
Assign NOS colours to the relevant items (activate the NOS flag).
Create NOS size keys when using the Item Colour planning type.

Setup Areas

Fashion Planning Setup

The Fashion Planning Setup contains the global control parameters for NOS Dispo. It is the central starting point and must be fully maintained before a first planning document can be created.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This app generates a complete set of fashion-industry-specific demo data for the BE-terna Fashion solution in Business Central.

It builds directly on Microsoft’s Contoso Coffee Demo Framework and extends it with realistic content tailored to the fashion industry like colors, sizes, brands, seasons, and everything else that makes fashion tick.

Note: The setup wizard is currently only available in German. The screenshots and option labels below refer to the German UI.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The Professional Services setup defines the foundation for contract management, recurring billing, service processes, and ticketing in Business Central. This page consolidates the key setup areas so the solution can be rolled out in a clear and business-oriented sequence.

Prerequisites

Professional Services is installed and licensed in Business Central.
Core Business Central settings for customers, vendors, projects, posting logic, and number series are prepared.
The target model for sales contracts, billing types, service execution, and ticketing has been aligned from a business perspective.

Recommended order

Define general Professional Services settings, contract behavior, and default values.
Configure number series and templates for sales contracts, billing types, SLAs, contingents, work orders, and tickets.
Define billing logic for service billing, project journals, and default billing types.
Complete ticketing, API, and property-related settings for operational use.
Use initial data, demo options, and standard pre-/post-texts only in a controlled test or rollout context.

Setup components

Core parameters and contract control

In the Professional Services setup, you first define the core control parameters of the solution. These include the default task for consumption, the use of project prices in sales lines, whether c/o addresses are mandatory, and the date formula for expiring contracts.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Device Management Setup

The Device Management Setup sets the basic parameters needed to work with devices, handovers, checks, and calendar functions. It forms the basis for the consistent use of the module.

Click to enlarge

Bereich	Feld	Erklärung / Zweck
Nummernserien	Gerät Nr.-Serie	Legt fest, aus welcher Nummernserie Gerätenummern automatisch vergeben werden.
	Übergabeprotokoll Nr.-Serie	Definiert die Nummernserie für Übergabeprotokolle (Reservierung, Ausgabe, Rückgabe).
	Standort Nr.-Serie	Nummernserie für Standorte.
Fakturierung	Projekt-/Ressourcenbuchung aktiviert	Verknüpft die Geräteverwaltung mit Projekt- oder Ressourcenbuchungen.
	Verwende Basiskalender	Aktiviert die Nutzung eines Basiskalenders für die Geräteplanung. Verwendet einen definierten Basiskalender um Feiertage etc. aus der Mengenberechnung von Proj.-/Ress.-Buchung auszuschließen
	Basiskalender Code	Definiert den Basiskalender, der für alle Geräte gilt (z. B. GERÄTE).
	Vorgabe Arbeitstypencode	Standard-Arbeitstyp für Buchungen (z. B. GSTD).
	Einheit	Maßeinheit für Buchungen (z. B. STD = Stunden).
	Vorgabemenge je Einheit	Standardbuchungsmenge (z. B. 8 Stunden pro Tag).
	Ausgabedatum als Buch.-Datum verwenden (Geräteausgabe)	Wenn aktiv, wird das Ausgabedatum als Buchungsdatum übernommen. Falls nicht aktiviert, wird das Buchungsdatum (Belegkopf) zur Buchung der Geräteausgabe verwendet.
	Rückgabedatum als Buch.-Datum verwenden (Geräterückgabe)	Wenn aktiv, wird das Rückgabedatum als Buchungsdatum übernommen. Falls nicht aktiviert, wird das Buchungsdatum (Belegkopf) zur Buchung der Geräterückgabe verwendet.
Geräteprüfung	Mehrere Hauptprüfungen pro Gerät/Typ	Erlaubt die Pflege mehrerer Prüfungen pro Gerätetyp (z. B. UVV + Sicherheitscheck).
Gerätekalender	Gerätekalender-Startansicht	Bestimmt die Standardansicht (Tag, Woche, Monat) beim Öffnen des Kalenders.
	Anzahl Ressourcen	Definiert die Anzahl der Ressourcen, die im Kalender angezeigt werden.
	Von Jahr	Beginn des Zeitraums, für den der Gerätekalender gültig ist.
	Bis Jahr	Ende des Zeitraums, für den der Gerätekalender gültig ist.

User Setup

The User Setup in Dynamics 365 Business Central defines which people have access to device management and how they are stored in the system. This controls which users can book, reserve or check devices.

Setup and master data

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Before you use charges productively, set up Material Surcharges Management and maintain the required master data. This includes the rules for price determination in sales and purchasing as well as the assignment of charges to items and units.

Prerequisites

Material Surcharges Management is installed in Business Central.
You have access to the DEL-Notation Setup page.
The required items, units, and item charges already exist in the standard system.
It is clear from a business perspective which charges are used in sales, purchasing, or both.

Recommended sequence

Define the basic rules in DEL-Notation Setup.
Maintain charges per item.
Create price lines for the charges you use.
Review translations and document display.
Test the business behavior on sales and purchase documents.

Setup building blocks

DEL-Notation Setup

The setup defines the basic pricing logic for Material Surcharges Management. At the moment, two central fields are available:

Setup and master data

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the foundational setup for Handling Unit Management. It covers packaging materials, packaging structure definitions, master-data-based assignments, and the rules and alternatives that are later used in document processes.

Prerequisites

Handling Unit Management is installed in Business Central and enabled for the relevant processes.
Item or resource master data for packaging materials and the required content items are available.
Responsibilities for master data maintenance, release, and operational use are defined.

Quick start for end users

If you are new to HUM, complete this checklist in order:

SOAP Interfaces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is the entry point for SOAP-based interfaces in the BE-Commerce module.

Scope

XML-based export and import operations
Channel-specific transfer using a unique webshop identifier
Processing through container and downstream module processes

Guardrails

Requests and responses follow operation-specific XML schemas.
Required parameters must be provided for each method.
Semantic validation is often executed in downstream processing steps.

SOAP Endpoints

Reference Processes

Synchronization

Mon, 01 Jan 0001 00:00:00 +0000

Under Data Transfer → Synchronization, the transfer of sales data from the cash registers to the main system is configured.

Click to enlarge

Setup

General

Click to enlarge

Field	Description
Location	The location code
Cash Register	The cash register code

Settings

Click to enlarge

Field	Description
Type	Push: The cash register independently transfers the sales data via the locally stored job queue. Pull: The main system independently transfers the data from all pull cash registers via the designated job queue.
Tables	Defines which tables are relevant for the sales-data transfer (deactivating tables that are not required reduces the amount of data to be transferred)
Records per Run	Defines how many records can be transferred at most per run of the respective job queue (affects the amount of data to be transferred and the execution speed of the responsible web service)

Actions

Entries

Click to enlarge

User and Permission Management

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains the core principles of user and permission management in Microsoft Dynamics 365 Business Central. It helps you set up new users so that sign-in, data access, interface, and business responsibilities work together cleanly from the beginning. It also shows where permissions can be adopted from the standard setup, extended in a controlled way, or adapted to groups of users.

Prerequisites

The user exists in Microsoft 365 or Microsoft Entra ID.
The user is available in Business Central or can be imported from Microsoft 365.
The setup is performed by a user with sufficient rights, for example IT or a key user.

Recommended Sequence

Check the user or import the user from Microsoft 365.
Assign the required permission sets.
Use security groups for recurring roles.
Add business-specific settings in User Setup.
If required, maintain warehouse assignment and profile.
Review the effective permissions before productive use.

Setup Components

Users

Open the Users page and check whether the required user already exists. In the cloud version, sign-in is handled through Microsoft 365, so separate password maintenance in Business Central is usually not required.

Webshop Channel Card

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the webshop channel card and the related advanced setup areas for ongoing operations.

Prerequisites

A webshop channel is available.
Core channel master data and baseline settings are defined.

Recommended Sequence

Validate channel basics and import/export controls.
Complete advanced setup areas.
Finalize checks and company information.

Channel Basics

Click to enlarge

Maintain a unique channel code and description.
Configure import/export behavior.
Set contact modification, location groups, and customer templates.
Configure document import and release checks.

Advanced Setup

Click to enlarge

Example setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The example setup helps you get BE-terna Vendor Rating up and running quickly. It creates a predefined baseline structure that you can refine afterwards to match your business requirements.

Prerequisites

The basic Vendor Rating setup is already in place.
You want to start with a predefined rating schema.
No productive, individually designed criteria structure is in use yet.

Recommended order

Open the Vendor Rating setup.
Switch to the example setup area.
Create the example configuration once.
Review and refine the schema, weightings, and criteria afterwards.

Setup components

Open the example setup

You can reach the function through Setup and then Example setup. Use it when you do not want to start from an empty criteria structure.

Rating criteria schema

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The rating criteria schema is the core element of BE-terna Vendor Rating. It defines which main criteria and subcriteria are used to evaluate vendors and how strongly each area contributes to the final result.

Prerequisites

The basic Vendor Rating setup is complete.
You have decided which quality, audit, and business criteria should be rated.
Responsibilities for weighting and evaluation have been aligned from a business perspective.

Recommended order

Create main criteria as the top-level evaluation areas.
Add subcriteria for each main criterion.
Define weightings in percent.
Enable rating types and calculation options.
Review audit, factbox, and business-criteria options for each subcriterion.

Setup components

Create main criteria

Main criteria provide the business structure of your vendor evaluation. Typical examples are quality management or logistics. For each main criterion, maintain the number, description, criterion level, rating type, percentage weighting, and the Confirmed calculation option.

Grade definitions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Grade definitions let you define what each grade means for a given subcriterion. This makes manual grading more consistent and easier to understand.

Prerequisites

The rating criteria schema with the relevant subcriteria is available.
The relevant subcriterion is not evaluated only through a business criterion.
The intended business meaning of the grades has been aligned.

Recommended order

Open the relevant subcriterion in the rating criteria schema.
Switch to the grade definitions.
Maintain a short and unambiguous description for each grade.
Verify the display of the grade description in the rating audit.

Setup components

Prepare the subcriterion

Grade definitions are maintained for subcriteria that are evaluated manually. These descriptions help auditors and reviewers assign ratings consistently in audits and self-disclosures.

Master-Data Templates

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Master-Data Templates help Professional Services predefine billing types, SLAs, and contingents directly on resources, customers, or items. This means recurring contract models are not built from scratch in each document, but transferred consistently from the underlying master data.

Prerequisites

templates for billing types, SLAs, and contingents are defined from a business perspective
the relevant master data such as resources, customers, or items is maintained
it is clear which templates should be transferred automatically during document creation

Functional focus

Templates on resources

Resources can store templates for billing types, SLAs, and contingents. When a contract-related document is later created for that resource, the required contract elements are already prepared.

Thresholds

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Thresholds define how operational deviations for business-rated subcriteria are translated into grades. This turns process data into a reproducible evaluation result.

Prerequisites

The rating criteria schema contains subcriteria with Business rating enabled.
The corresponding Business criterion is selected for each subcriterion.
The desired business tolerances have been aligned.

Recommended order

Open the relevant subcriterion in the rating criteria schema.
Enable business rating and choose the correct business criterion.
Maintain thresholds that match the criterion.
Verify the outcome with real process data.

Setup components

Evaluate delivery time

For the Delivery time criterion, maintain thresholds as a deviation in days from the agreed delivery date. When the goods receipt is posted, the system compares due date and actual posting date and derives the appropriate grade automatically.

Initial Data, Demo Data, and Licensing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Initial Data, Demo Data, and licensing functions support the first-time provisioning of Professional Services in a new company. They help provide a usable base setup, import demo master data for testing, and review the licensing state of the installed modules at the same time.

Prerequisites

a new or otherwise suitable target company exists
it is clear whether only the base setup or additional demo master data is needed
the existing Business Central configuration is understood so productive tables are not overwritten unintentionally

Functional focus

Initial data for the base setup

The Initial Data function can import setup tables, sales setup, customer setup, posting matrix data, and other core configuration elements for Professional Services. This option is suitable when a company should become operationally ready without creating additional demo master data.

Vendor card

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

On the vendor card, you define whether a vendor is included in vendor evaluation. The page also shows key figures from the last rating as well as PPM-related target values.

Prerequisites

The vendor exists as master data in Business Central.
The basic Vendor Rating setup and classification logic are maintained.
You know whether the vendor should also be evaluated through PPM.

Recommended order

Open the relevant vendor.
Go to the Rating section.
Enable vendor evaluation for the vendors that should be rated.
Decide whether PPM should be calculated and maintain target values.
Review the result of the last rating.

Setup components

Relevant fields in the Rating section

In the Rating section, you maintain or review the following fields in particular:

Standard Pre- and Post-Texts

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Standard Pre- and Post-Texts standardize the text flow in quotes, orders, and other document types in Professional Services. They reduce manual maintenance during document creation and control which texts are automatically reused, replaced, or reset when one document type creates another.

Prerequisites

the affected document types and their business text blocks are defined
it is clear for which document transitions existing texts should be reused or overwritten
standard texts are aligned with business and legal requirements

Functional focus

Standard texts per target document type

For each target document type, you can define which pre- and post-texts apply when a new document is created. This is especially relevant when, for example, a quote becomes an order or another source document creates a follow-up document.

Invoice Import for Consumption-Based Billing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The invoice import setup supports consumption-based billing scenarios in which price-list or invoice data is taken over from external sources. It provides the technical basis for transferring imported data into items, price lists, and downstream billing processes in a controlled way.

Prerequisites

the underlying import interface and the target billing model are defined from a business perspective
number series for imported documents and price lists are prepared
item templates, price lists, and required billing-type templates already exist or are defined

Functional focus

Number series for imported documents

Dedicated number series are maintained for imported invoices and imported price lists. This keeps imported records separate from manually created documents and makes them easier to trace during daily operations.

COP Catalog Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

COP Catalog Setup is used to take over item data from supplier catalogs into Professional Services. This makes it easier to feed external product information into purchasing-related processes and prepare it for later contract, pricing, or service contexts.

Prerequisites

a suitable supplier or catalog interface is available
it is defined which item data should be taken over from external catalogs
downstream purchasing and pricing processes in Business Central are prepared

Functional focus

Import external item data

The catalog setup allows item data to be imported from supplier catalogs. This provides information from external sources in a form that can be maintained and reused in later purchasing processes.

Calculation Matrix

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The Calculation Matrix is used to determine an appropriate percentage for billing-type templates automatically. It is based on the combination of calculation type code and periodic calculation code, so business pricing logic does not have to be duplicated across many nearly identical templates.

Prerequisites

the calculation types and periodic calculation codes in use are defined from a business perspective
billing-type templates for the relevant delivery models exist
it is clear in which documents the automatic percentage logic should apply

Functional focus

Combination of calculation type and periodic calculation

The Calculation Matrix evaluates the combination of calculation type code and periodic calculation code. For each relevant combination, a predefined percentage can be stored and later applied automatically when a document is created.

(Costing)Article

Mon, 01 Jan 0001 00:00:00 +0000

Costing articles

By importing catalogs from external suppliers, such as wholesalers, costing articles can be created via the DATA standard interface. A distinction is made between items and catalog items to keep inventory low, as wholesalers carry an extensive quantity of items. The search function with the input Costing Item takes you to the costing item card.

Click to enlarge

Costed item card

The DATA-NORM import already pre-fills the costing item card. You can access it by clicking on the number of a corresponding item in the list of costing items.

Version 26.1.0

Mon, 01 Jan 0001 00:00:00 +0000

Summary

Version 26.1.0 strengthens calculation, pricing logic, templates, project integration, and sales-contract status handling. It also includes many fixes in posting, SLA lines, translations, and contingent logic.

26.1.0 — 2025-08-20

New features

38437 - Revised standard pre- and post-texts
30478 - Report selection
38319 - Lookup templates
23560 - Credit memo field numbers / report
37189 - Reworked calculation logic
30783 - Prices from project documents
38048 - Work order: transfer multiple lines
36995 - Delivery address in the work order
37853 - Implemented sales credit memo report with Professional Services features
37811 - Reworked contract status
37858 - Implemented c/o address
37565 - Billing type assignment - price adjustment
37480 - Integrated templates in the resource list
37695 - Reworked sales document assignment view
19810 - Test code
37253 - Number series for CSP items
35199 - Open CSP topics
31256 - Enhancements for contingents and periods
32310 - Sales contract - required date indicator

Bug fixes

38419 - Error message during posting
38343 - Error in work package
38010 - RC tickets - missing translation
37858 - c/o address - fix for field entry
37946 - Billing type assignment
37797 - Synchronize subject fields from sales document to contract
37277 - Error message for SLA line from template
37141 - Professional Services setup - missing fields
27896 - Improvements and fixes for contingents

Barcode

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Barcode, barcodes can be configured.

Click to enlarge

Setup

Field	Description
Prefix	Specifies which character string appears at the beginning of the barcode and therefore has to be removed
Type	Defines the barcode type and therefore how it should be interpreted Campaign: The barcode is interpreted as a campaign code Coupon: The barcode is interpreted as a coupon Reservation: The barcode is interpreted as a reservation receipt
Suffix	Specifies which character string appears at the end of the barcode and therefore has to be removed

Usage

If a campaign called TEST exists and it should be applied manually rather than automatically on the receipt, the barcode could look like this: CAMPTEST. To interpret this barcode successfully, a barcode setup for Campaign must first be created with CAMP stored as the prefix. When CAMPTEST is captured, the cash register program then recognizes that it is a campaign, removes the CAMP prefix, and registers the TEST campaign.

Basic Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides a compact overview of the most important basic setup topics in Microsoft Dynamics 365 Business Central. It summarizes the themes from the Microsoft Learn onboarding pages without explaining each assisted setup or business area in detail.

The focus is on the recommended starting sequence, the main setup areas, and the Microsoft documentation paths to use for deeper follow-up.

Prerequisites

A Business Central environment is available and you can sign in.
The initial app installation and the first user settings are already prepared.
It is aligned which business areas should be used productively first.

Recommended Sequence

Review and complete company and finance basics.
Align assisted setup, role center, and user context.
Prioritize the relevant business capabilities and introduce them step by step.

Setup Components

Company and finance basics

The Microsoft quick-start page bundles the first topics for company information, financial information, and report and document layout adjustments. For the initial setup, the key point is that company master data, bank details, tax information, and the financial baseline are maintained consistently.

Business Functions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page summarizes the main business capability areas of Professional Services. It helps teams understand which tasks the solution supports across sales, service, billing, purchasing, and customer-related master data.

Functional areas

Sales and contract management

Professional Services supports quotes, orders, and sales contracts for recurring services. Typical use cases include hardware rental, SaaS subscriptions, support and maintenance contracts, and project-related services.

Key capabilities include:

recurring billing embedded in quote and order processes
sales contracts as the basis for long-running service relationships
billing types and assignments for different business models
service level agreements and contingents for contract-based services

Details for this area are available on the Sales page.

Calculation in the bill of quantities

Mon, 01 Jan 0001 00:00:00 +0000

In the bill of quantities, the calculation is made by adding the subitems to the items, which in turn are added up to the title level. The total result of all title levels is then shown in the total line. BE-terna Project allows flat calculations, as well as complex calculations on several levels.

Click to enlarge

Subheadings

Since the reference value of the subitems refers only to a unit of measure of the parent item, quantities are maintained accordingly only for a unit of measure of the parent item. These quantities are then factored with the required quantity of the main item and summed up to the title level.

CargoLine

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the CargoLine-specific setup in Shipping Labels. Use it after the shared setup is complete to maintain the CargoLine product catalog, package types, credentials, URL assignments, and the properties that control pickup windows, label output, and fallback package data.

Prerequisites

The shared Shipping Labels setup is complete.
CargoLine test or productive endpoints and the required authorization token are available.
The relevant shipping agent and shipping agent service are already maintained in Business Central.
Item attributes for dimensions and weight are maintained where possible, or a fallback package definition is available on the setup.

Recommended sequence

Create or verify the CargoLine shipping agent service combination in the shared setup.
Maintain the CargoLine product list and package-type list.
Assign the CargoLine test or productive URL and the authorization token.
Maintain pickup window, label size, and fallback package properties.
Test one realistic label request with complete package data.

Setup components

Maintain products and package types first

CargoLine depends on two reference catalogs before the final setup line is usable: the available CargoLine products and the allowed package types. These lists define which business combinations can be selected later in the actual setup.

Copying a Project Document

Mon, 01 Jan 0001 00:00:00 +0000

A document that has already been entered can be copied within a project or moved to another project. To copy, select Process in the navigation menu under Actions and click Copy document…. First, a dialog opens with settings similar to [Creation of a new document](/BE%2Dterna-Project-Documentation/Project Documents/Creation-of-a-New-Document).

Click to enlarge

Additional options for copying the document are available under Copy Options.

Click to enlarge

Field	Explanation
Marked only	Copies only positions marked in the bill of quantities.
Consolidation type	Two options are available: Flatten subpositions converts subpositions to positions. Flatten and consolidate by no. also converts subpositions to positions, removes title levels, and consolidates quantities of identical items.
Skip zero-quantity lines	Lines without quantity are not copied.
Keep dimensions	Keeps dimensions from the source document or applies dimensions from the target project.
Quantity from delivery orders	Uses quantities from delivery orders instead of the quantities stored in the bill of quantities.
Quantity from measurements	Uses measured quantities instead of quantities stored in the bill of quantities. Can be combined with Skip zero-quantity lines to create an invoice with measured positions and quantities only.
Copy measurements	Copies measurements.
Measurement no. filter	Copies only measurements with selected measurement numbers. If empty, all measurements are considered. Applies to both Quantity from measurements and Copy measurements.
Sheet no. filter	Copies only measurements from selected sheet numbers.
Location no. filter	Copies measurements from the selected location into the new document.
Pre-/post-texts	New documents are always created with standard texts if configured. During copy, existing texts can either be replaced or supplemented. If no texts are maintained, empty text positions are created.
Pre-text	Copies maintained pre-texts.
Keep pre-text	Uses the pre-text from the source document.
Standard pre-text	Replaces the source pre-text with the configured standard pre-text.
Post-text	Copies maintained post-texts.
Keep post-text	Uses the post-text from the source document.
Standard post-text	Replaces the source post-text with the configured standard post-text.
Company copy
Copy from other companies	Copies the document from another company and enables the following fields.
Company	Select a permitted company.
Project no.	Select a project by its project number.
Project document no.	Select a project document by its project document number.
Base document type	Defines the base document type, for example Draft.
Document type	Defines the document type.

Costing Groups

Mon, 01 Jan 0001 00:00:00 +0000

Costing groups offer the possibility to use the master data to determine the mark-ups with which items are to be included in the costing. To create a new costing group, enter the term Costing Groups in the search function. Clicking on the New button will create a new line, which can now be filled. A code and a description are stored at the calculation group, as well as the percentage markups for materials, wages, equipment, external services and others.

Create costing items

Mon, 01 Jan 0001 00:00:00 +0000

For the creation of new costing articles via Open Masterdata, there are three different actions on the supplier card

Create costing articles via GTIN
An input window opens, where a costing article can be created by entering the Global Trade Item Number (GTIN / EAN) of an article available at the supplier.
Costing items per supplier article no. create
An input window opens, where a costing article can be created by entering the supplier article number.
Create costing articles via IDS
The user is directed to the webshop and can fill a shopping cart similar to IDS and send it back to Business Central. The decisive difference is that all items in the IDS shopping cart are created in the BC as costing items.

Create XRechnung

Mon, 01 Jan 0001 00:00:00 +0000

Export as XRechnung

A project invoice document can be output as an XRechnung. The XRechnung created is automatically added to the attachments of the document.

To do this, go to Actions in the open project document via Export to Other and then Export as XRechnung.

Click to enlarge

Attention! If you have transmitted the exported XRech file to the client, it is considered the original of the invoice document for tax purposes and is therefore subject to retention.

Creation of a new document

Mon, 01 Jan 0001 00:00:00 +0000

Creation of a new document

To create a new document in a project, go to Manage in the Project Documents tab and then to New.

Click to enlarge

Field	Explanation
Project no.	The project number specifies in which project the document is created. The system automatically uses the current project’s number. You can also create the document for another project here.
Document type	The lookup opens the list of document types that can be created, for example draft, quote, order, partial invoice, invoice, partial credit memo, and credit memo.
Document heading	Defines the document heading line.
Subject	Defines the document subject line. This field is prefilled with the project name.
Sell-to customer no.	The lookup lets you assign a customer from the customer list to the project. Address and contact details are then filled automatically from customer data.
Sell-to contact no.	If no customer is selected, a contact can be selected here. If the contact is already linked to a customer, the Sell-to customer no. field is filled automatically.
Sell-to customer template code	Specifies whether the document is domestic, EU foreign, or non-EU foreign.
Sell-to name	Is filled automatically with the customer name if a customer exists.
Sell-to contact	The full contact name defined via Sell-to contact no.
Posting date	The date on which the document (for example an invoice) is posted.
Document date	The date printed on the document (for example an invoice).
Business posting group	Selection includes: customers and vendors in EU, foreign countries, domestic customers and vendors, purchase/sales according to German VAT §13b construction services, domestic down payment invoices, and down payment invoices under §13b.
Currency code	Currency code in which the document is posted.
Start date	Start date of the related project.
End date	End date of the related project.
Quote valid-until date	Date until which a quote document remains valid.

The optional information in the other masks is derived from the preset data of the project, which can be changed if necessary by switching between the masks via Next or Back. The document is created directly via Done. The optional information when creating a document is usually not necessary.

Customer and sales

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page groups the customer and sales setup steps that are specifically needed for intercompany exchange. They complement the standard Business Central setup with behavioural rules that kick in when IC sales documents are sent or accepted.

Prerequisites

Sales & receivables setup in Business Central is completed.
Permissions for the Sales & Receivables Setup page are granted.

Setup building blocks

Allow quantity 0 on posting

This switch suppresses the standard check Warn before posting sales lines with quantity 0. It is helpful when IC order changes leave lines at quantity 0 that would otherwise block posting.

DATANORM Download with the help of Open Connect

Mon, 01 Jan 0001 00:00:00 +0000

ITEK-GmbH provides the directory services Arge Neue Medien, SHK Connect and Open Connect. These directory services try to reduce the variety of variants of data exchange procedures on the provider side to a few different ones. The participating manufacturers and wholesalers will provide information on an optionally supported IDS interface as well as links to the article catalogue in DATANORM format.

In the supplier master data, the Open Connect Lieferantenliste with all participants can be found in the navigation menu under Data Exchange.

Device management

Mon, 01 Jan 0001 00:00:00 +0000

The Device List in Dynamics 365 Business Central serves as a central overview of all tracked devices in the company. It enables the rapid management, tracking and control of devices, their location and inspection dates.

Click to enlarge

The following standard actions are available in the header area:

New: Create a new device
Erase: Remove marked device
Device / Inspection / Handover: Special actions for device editing and management

Document Resource Prices

Mon, 01 Jan 0001 00:00:00 +0000

In the project document, it is possible to add a resource group from the master resource groups at each item, if some have not already been maintained in the master data of the article. To do this, the advanced view must be enabled to access the Resource Group column. After the addition, the cost price of this resource group, if any, is inherited.

In addition, there is a “Resource Group Price” table in the project document. These can be used to edit the resource groups contained in the project document retrospectively. If a resource group is entered in this table, the cost price is transferred from the master data to the table. These can be individually adjusted at a later date. The adjusted prices must be updated in the document in order to enter them in the bill of quantities. The table is located in the navigation menu under Related in Settings.

EDS Klein References

Mon, 01 Jan 0001 00:00:00 +0000

The company EDS Klein provides a catalogue that assigns the same articles from different suppliers to each other.

In order to create these reference articles and their assignment, the calculation articles of the dealers must first be imported (sample example EDS-Muster.zip).

Next, the reference articles are imported. The supplier of the reference items must be given the “Reference Articles Only” flag.

Click to enlarge

After importing the reference items, the assignments to the supplier items can be imported. In the import dialog, you must specify for each file to which supplier this file is assigned.

Click to enlarge

EK VK Price Fixed

Mon, 01 Jan 0001 00:00:00 +0000

These options apply to the entire position and not to a single price component. They can be found under Edit in the FastTab and then back on Edit. In the window for item editing, the two sliders are located in the “Prices” tab.

Click to enlarge

Sales price fixed

If activated, it protects the calculated retail price from change due to the final sum calculation of the sales price. Changes to the items can change the price (e.g. a change in the purchase or sale price).

Export Item

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns item data for a webshop channel including optional expansions such as descriptions, categories, attributes, cross-selling, and variants.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/items?$filter=webshopChannelCode eq '<webshop-channel-code>' and no eq '<item-no>'&$expand=itemDescriptions($expand=descriptions),categories,itemDynamicAttributes,itemFreeTextAttributes($expand=freeTextLanguages),crossSellingItems,itemSelectionVariants($expand=crossSellingVariants)

Required Parameters

webshopChannelCode in the filter
no (item number) in the filter

Optional Expansions

itemDescriptions
categories
itemDynamicAttributes
itemFreeTextAttributes
crossSellingItems
itemSelectionVariants

Key Response Fields

Item header: systemId, webshopChannelCode, no, released, firstReleasedDate, vendorNo, itemDescription
Descriptions: language, meta title, description types
Category assignment: code and main flag
Attributes: dynamic and free-text attributes with language values
Variants and cross-selling relations

Result

The webshop receives a consolidated item JSON payload for the requested channel and item filter.

Export Item

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This SOAP method exports item data for a webshop channel, optionally filtered to a single item.

Method

Operation: ItemExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameters

itemNo_P
incremental_P

Response

XML in itemExport_PX with item header, descriptions, categories, attributes, and variants.

Result

The webshop receives current item master data for synchronization and product display.

Extensions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes two sales-specific extensions: configurable handling of deviating prices and descriptions on incoming sales orders and manual resending of posted sales documents to the IC partner.

Business value

A clear rule when incoming IC data deviates from local master data (replace, ignore, or fail).
A targeted way to resend posted documents without disturbing the running chain.

Focus areas

Incoming sales orders

For each deviation (sales price or description) on an incoming IC order line you define the behaviour on the partner card:

Forming group totals

Mon, 01 Jan 0001 00:00:00 +0000

Group totals can be used to group items in the document according to various criteria and to perform a Final Total Calculation based on the groupings. The function can be called in the document via Edit and Group Totals. It can be grouped according to various characteristics. It is possible to switch between different grouping characteristics via the dropdown. It should be noted that the sum is only calculated from the level at which the document was navigated (title level – total level). The available grouping criteria are customizable by BE-TERNA. It is therefore possible to sum according to your own criteria.

Functions

Mon, 01 Jan 0001 00:00:00 +0000

The Functions menu is available during checkout in every state and provides several generally applicable options.

Click to enlarge

Back to Sales

This function takes you back to sales mode at any time, provided that no actions have already been performed that make this impossible, such as payments that have already been posted or cashbook actions.

Click to enlarge

If the function is not possible for the reasons already mentioned, a corresponding information message appears.

Functions in the navigation menu

Mon, 01 Jan 0001 00:00:00 +0000

In the navigation menu, there are several options for editing at row or document level. In addition, various tabs can be shown and hidden.

View

Click to enlarge

Field	Explanation
Entry	Changes the table header to entry view.
Advanced	Changes the table header to advanced view.
Costing	Changes the table header to costing view.
Invoicing	Changes the table header to invoicing view.
Purchasing	Changes the table header to purchasing view.
Measurement	Opens a FastTab for measurements and switches the bill of quantities to measurement view.
GAEB	Changes the table header to GAEB view.
Print	Changes the table header for document print settings.
Manufacturing	Changes the table header to manufacturing view.
Select…	Opens a window to choose the project document view.
Design…	Configures a user-specific view.

Details

Click to enlarge

IDS Connect Orders

Mon, 01 Jan 0001 00:00:00 +0000

To place an order for the shopping cart in the IDS webshop, you have to use the [Purchasing Exchange](/BE%2Dterna-Project-Documentation/Purchasing/Purchasing Exchange) and process it into an order.

IDS Shop Use

Mon, 01 Jan 0001 00:00:00 +0000

There are several ways to use the IDS webshop.

In the list of costing items, you have to navigate to the desired article. In the article card, the navigation menu under IDS contains the IDS Deeplink to open the webshop.

Click to enlarge

The IDS Deeplink opens the display of the item with price information, availability, descriptions, packaging information, etc.

Another option is in the supplier card with the function IDS shopping cart. This will direct you to the stored webshop. When the cart is returned, a new purchase exchange process will be opened.

Inbox and outbox

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The IC inbox and IC outbox show every IC transaction and its current state. They are the primary workspace for daily operations: sending, accepting, re-queueing, error analysis.

Access in Business Central

Inbox and outbox are reached through the role center or through search.

Prerequisites

Intercompany is configured and at least one IC partner is active.
Permissions for IC transactions are granted.

Activities

Send or accept pending transactions on demand.
Analyse failing transactions and restart them.
Review processed transactions as history.

Fields and actions

Action	Effect
Send (outbox)	Transfers the transaction to the partner.
Accept (inbox)	Picks the transaction up at the receiving company.
Reject	Marks the transaction as not to be processed.
Retry	Restarts a previously failing processing.

Monitoring and troubleshooting

When transactions stay in Open for long, check the job queue.
Transactions in Error reference entries in the Error log.

Best practices

Walk through the inbox daily, even with automatic acceptance enabled.
Sweep the outbox regularly for old Open entries – they often point to disabled queue jobs.

Individual workspace

Mon, 01 Jan 0001 00:00:00 +0000

Activities

In the Activities section, there are tiles in which thresholds can be set up to ensure a faster overview of certain metrics. To do this, you can click on the arrow next to Activities. Then a selection opens with Update Data and Set Up Batch. If you click on Set up stack, the page for stacking setup opens. This refers to the arrangement of the tiles.

Click to enlarge

Infobox in the project map

Mon, 01 Jan 0001 00:00:00 +0000

Details

There is also an info box on the right side of the project map. In the Details tab, you will find business information about the selected project. These include, for example, budget costs and actual costs. The project number is also indicated.

Click to enlarge

Attachments

In the attachments, you can attach documents such as receipts, provide links or pin notes.

Click to enlarge

Infobox in the project overview

Mon, 01 Jan 0001 00:00:00 +0000

Details

In the Details tab in the project list, you will find information about cumulative project data. These are generated from the WIP/revenue recognition area in the projects. At the bottom, the project statistics are displayed in a diagram.

Click to enlarge

Attachments

In the Attachments tab of the infobox you will find additional functions.

Click to enlarge

On the one hand, important documents for the project (construction drawings, etc.) can be stored in table structure under “Attachments”. Under Notes, you can document additional annotations about projects.

Infoboxes

Mon, 01 Jan 0001 00:00:00 +0000

The document editor consists of five info boxes, which can be found on the right-hand side: Document totals, Item details, Measurement details, Item attachment and Reference article.

Click to enlarge

Document totals

The Infobox Document Totals refers to the entire document in its data and values. It contains the cost amount and the total price, as well as the total time and discounts, if available. These values then result in the contribution margin for this document.

Invoicing

Mon, 01 Jan 0001 00:00:00 +0000

Invoices are created identically to the other project documents. Different types of invoices can be created directly from the project card in the Project Documents and Project Invoices tabs via Manage and New.

Click to enlarge

Partial invoices as down payment invoice
Partial invoices
Invoices
Final invoices
Credits and
Partial credits (preferably always non-cumulative)

Final invoices always refer to previous partial invoices. They are cumulative and complete a billing process. Invoices, on the other hand, have no previous partial invoices. So they cannot be cumulative and form their own billing process. An overview of all invoices can be found in the Project Cockpit under the Project Invoices tab. Whether a partial invoice is called partial invoice, partial invoice or invoice invoice, can be set in the document types.

Item Packages

Mon, 01 Jan 0001 00:00:00 +0000

An article package is made up of various (costing) articles and resources. It is possible to create these in advance. To do this, use the search function to call up the article package overview.

The list for viewing and editing catalog items can be found in BE-Project in the master data, which can also be accessed via the search function under Catalog Items.

To use the article packages, first create a new item in the service specification and select the desired article package under Type and No. The item package then appears as an item and the associated components as subitems.

Item sales

Mon, 01 Jan 0001 00:00:00 +0000

After the cashier sign-in, the sales mode opens with the Sales button.

Click to enlarge

If the cash register is configured accordingly, a salesperson must be captured before each receipt.

Click to enlarge

Input Item

After entering the salesperson number, the cash register is in sales mode.

Click to enlarge

For the sales process, the barcode can either be scanned or entered manually if the scanner does not work.

Line comments

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Comments on purchase and sales document lines can be transferred with the IC document so that the partner sees the same business context. This page describes activation and visibility in the document context.

Business value

Business-side hints (for example delivery notes, internal agreements) reach the partner without a side-channel email.
The comment appears on the correct document and the correct line, not as a bulk attachment.

Focus areas

Activation in the intercompany setup

The option Transfer line comments activates the transfer. Without this switch, line comments are not sent and are not visible at the receiver.

Lookup

Mon, 01 Jan 0001 00:00:00 +0000

Under Designer → Lookup, the lookups for cashiering are configured.

Type	Description
Salesperson	Configuration of the salesperson lookup
Customer	Configuration of the customer lookup
Item	Configuration of the item lookup
Item Variant	Configuration of the variant lookup
Return Reason	Configuration of the return-reason lookup
Unit of Measure	Configuration of the unit-of-measure lookup
Cash Account Book	Configuration of the cash account book lookup
Tender	Configuration of the tender lookup
Discount Reason	Configuration of the discount-reason lookup
Voucher Sale	Configuration of the lookup for open vouchers
Voucher Redemption	Configuration of the lookup for redeemable vouchers
Customer Ledger Entries	Configuration of the customer ledger entry lookup (open entry balance)
Contact	Configuration of the contact lookup
Item Reference	Configuration of the item reference lookup
Resource	Configuration of the resource lookup
Item Category	Configuration of the category lookup
Contact Editing	Configuration of contact creation/editing
Customer Editing	Configuration of customer creation/editing
Customer History	Configuration of the lookup for previous customer purchases
Price Information	Configuration of item price determination
Lot Information	Configuration of the lot lookup
Fattura PA	Configuration of invoice data for Italian fiscalization
Receipt Return	Configuration of return capture
Location	Configuration of the location lookup
Campaign	Configuration of the manual campaign lookup
Coupon	Configuration of the manual coupon lookup
Reservation	Configuration of the reservation lookup
Serial No.	Configuration of the serial-number lookup
Tax Free	Configuration of subsequent tax-free capture
Demoscopic Query	Configuration of the demoscopic-query lookup
Campaign Entries	Configuration of the lookup for campaigns currently registered/applied on the receipt
Receipt	Configuration of the receipt lookup
Employee	Configuration of the employee lookup

Actions

Action	Description
Reset	Resets the currently selected lookup to the default settings
Reset All	Resets all lookups to the default settings

Setup

General

Click to enlarge

Manual pricing

Mon, 01 Jan 0001 00:00:00 +0000

These options apply to the entire position and not to a single price component. The ticks can be selected in the “Details” tab.

Click to enlarge

Manual purchase price

If activated, the purchase price of the selected price share is determined via the Purchase price (total) field. Changes to fields used to calculate this purchase price no longer have any effect on the purchase price. The final total calculation can change this manual price.

Master data and relation maintenance

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the recurring maintenance of MDM master data and relations. The focus is on relations, company assignments, dependencies, exclusions, DSR filters, substitutions, and the preparation needed for later consistency checks.

Business value

Makes the business maintenance of relations and rule sets understandable as reusable master data.
Supports a consistent mapping between source and target companies.
Helps teams prepare controlled deviation handling through rules, DSR, and review logic.

Content focus

Relations as the central maintenance object

The MDM relation is the leading object for maintaining the business data relationship. It combines table context, routing rule, distribution behavior, status, and the related company assignments in one shared maintenance context.

Master data at the supplier

Mon, 01 Jan 0001 00:00:00 +0000

In the supplier card there is the IDS tab.

Click to enlarge

The IDS Version field is used to specify the IDS version to be used if this cannot be determined automatically by the supplier. \

The corresponding URL of the supplier can be stored in the IDS-Uri field, if it has not been automatically transmitted by Open Connect.

If you click on the number in the field Number of IDS users, the list of explicitly logged in users in the webshop who can use the IDS Shop opens. There it is possible to create additional users.

Master Data for Fashion

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page consolidates the fashion-specific master data you maintain in addition to the general BE-Commerce standard. It helps new users understand the main data objects and the order in which they should be prepared.

Who this page is for

Users who prepare categories, attributes, and colors for a fashion webshop.
Key users responsible for master-data quality and channel-related maintenance.
Teams that need to decide which data is maintained in the connector and which belongs to the shared BE-Commerce area.

Recommended Sequence

First review the basics in BE-Commerce Master Data.
Then define the channel-related foundation for the fashion webshop.
Continue with categories as well as dynamic and free-text attributes.
Finish with colors, supplier colors, and item-related webshop data.

Webshop Channels

Each shop is managed through its own channel. Per channel you maintain, among other things, the location group for available inventory calculation, the sales location for webshop documents, allowed contact changes, and the active languages.

Measurement Entry Matrix

Mon, 01 Jan 0001 00:00:00 +0000

For cases where you are working with several locations and associated sublocations, it makes sense to use the measurement entry matrix.

This function makes it possible to record a measurement in matrix form. It can be found in document processing under Actions under Functions and Aufma ß erfassungsmatrix….

Click to enlarge

In the General tab, the specifications for filter criteria are set to row and column view and you select the location and sublocation or measurement number depending on the selected view. In this way, the matrix enables measurements to be recorded in two dimensions. In addition, you can specify whether sublocations should be displayed and whether the number or name should be displayed as a column heading. In the case of an extensive list of services, the items can be filtered for clarity.

Measurement recording directly in the order

Mon, 01 Jan 0001 00:00:00 +0000

In the document, the FastTab Aufma ß can be opened under View. The table header is adjusted accordingly.
The measurement number, location and partial location, as well as sheet number are stored there. If there are no default values for the location or sublocation, these can be entered manually. The system saves these after a query.

After the default values have been entered in your head, it is possible to enter the measurement chain directly at the position in the column “Measurement Input”.
After the measurement has been entered, the respective amount of measurements is summed up for each item. If the default values have been changed, the corresponding measurements are displayed.

Measurement recording via Excel

Mon, 01 Jan 0001 00:00:00 +0000

The third way to measure is via Excel. In the navigation menu under Actions, go to Export and Aufma ß and select Handaufma ß.

Click to enlarge

A list opens where a hand measurement can be selected from the Excel templates. By default, two templates are available:

Hand Measurement - BE-terna-Project_Handaufmass_V1.0.xlsx
Hand Measurement Cross - BE-terna-Project_Handaufmas_Makro_V1.0.xlsm

Click to enlarge

Note: For the hand measurement horizontally, macros must be activated on the corresponding client. If no macros are available on the client system, the manual measurement BE-terna-Project_Handaufmass_V1.0.xlsx can be used.

Order Requests

Mon, 01 Jan 0001 00:00:00 +0000

A purchase order request can be created directly from the document. It is possible to create a request for the entire document or for individual items. To do this, the items that are to be ordered must be marked (a click on the title level or the item is sufficient). Then go to Actions via the navigation menu and select Einkauf… under Process. A new dialog box will open.

Click to enlarge

Orders

Mon, 01 Jan 0001 00:00:00 +0000

Creating a purchase order

All purchase orders for a project can be viewed in the project card under the Project Purchasing Documents tab.

Click to enlarge

In the project, a purchase order document can be created from the bill of quantities in the same way as the procedure described in the item [Order Requests](/BE%2Dterna-Project-Documentation/Purchasing/Purchase Requests). For this purpose, Destination is selected as a type of purchase order in the tab.

Overhead Costs in the Document

Mon, 01 Jan 0001 00:00:00 +0000

Site-specific overhead costs can be stored in a bill of quantities in the navigation menu under Related in Settings.

Click to enlarge

The overhead costs increase the cost amount and are not visible to the customer. The values are entered in the overhead lines and the price share to which they are to be allocated is determined. Alternatively, you can work with formulas under Details. By clicking on Assign overhead costs, the costs are allocated 3% to the items in the document as a purchase mark-up and this distribution is reversed by clicking on Uncover overheads.
Attention: This will change the retail amount, unless it has been fixed everywhere by means of batch processing!

Packaging materials and structures

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page expands on the master-data foundation of Handling Unit Management. It explains how packaging materials are created, how packaging structures are built, and how alternatives and rules are prepared for later automatic packaging assignment.

Business value

Makes packaging materials and structure templates available as reusable master data.
Creates a reliable foundation for automatic standard packaging on documents.
Helps teams maintain alternatives, weights, and validation rules consistently.

Content focus

Define packaging materials

Packaging materials can be created from items or resources. In practice, items are often used. Marking an object as a packaging material mainly controls filtered selection and input validation in the downstream tables.

Payment plan

Mon, 01 Jan 0001 00:00:00 +0000

The payment plan is a variant to control payment flows. Payment plans are stored directly with the project, customers or vendors. In the BE-terna Project setup, a [Standard Payment Plan](/BE%2Dterna-Project-Documentation/Setup-and-Extension/BE%2Dterna-Project-Setup/Master Data) can also be defined. The function of the same name can be found in the navigation menu at Start in the project map. A list of the payment plans stored in each case opens, where existing payment plans can be selected, edited or new payment plans can be stored.

Position Batch Processing

Mon, 01 Jan 0001 00:00:00 +0000

You can find the batch processing in document processing under Edit in the FastTab.

Click to enlarge

Using item batch processing, a selection of items in the project document can be changed using various setting options.

Click to enlarge

General

Field	Explanation
Positionsnr.	Specifies the number of the position selected beforehand.
Beschreibung	Shows the description of the currently selected position.
Positionsauswahl
Auswahl	This lookup defines how many positions are processed. All processes all positions in the document. Current only processes the previously selected position. Subordinate additionally includes subordinate positions.
Positionstypenfilter	This lookup selects whether batch processing should handle main positions and/or subpositions.
nur markierte	Applies the selection only to marked positions.
Aktion
VK-Preis	In this lookup, choosing Current as manual transfers the calculated result to sales. If purchase values change later, sales prices stay unchanged. The Calculation result option recalculates the sales price from costing. The Manual sales price flag on positions (per price share) determines the sales price of the selected price share via Current Sales Price. Changes to costing fields used for that price no longer affect it. Final total calculation can still change this manual price.
GAEB-Preis	Specifies whether imported GAEB prices should be taken over into purchasing. The sales price is then derived from costing.
GAEB EP-Anteile	Defines whether unit prices from imported GAEB should be adopted and directly assigned to position price shares.
Aufmaß	Transfers measured quantities per position into the position quantity column.
Preise aus Stamm aktualisieren	After prices were changed in item or catalog item master data, this field controls whether only cost price or both cost and sales prices are updated.
Lohn-Zeitanteil aus Stamm übernehmen	Updates the labor time value (usually in minutes) on the labor price share from master data.
Texte aus Stamm aktualisieren	Updates short and long texts of positions based on the current version in master data (items, catalog items).
Zeilenumbruch vor Position	Selects whether a line break should be printed before the position.
Einzelpreisaufgliederung de-/aktivieren	For GAEB export with unit-price breakdown, activation on the main position is required.
Erstelle Datensatz aus Position	Creates a new costing item, item, or package in master data from a manually entered position, depending on selection.
Kreditorenartikelnr. aus Stamm übernehmen	Specifies whether the vendor item number should be copied from master data.
Variable Textsteuerung	This lookup also sets optional positions (visible in Print view). It then controls whether long and/or short texts are printed for positions in the project document.
Referenzkreditor	Specifies a reference vendor via lookup.

Purchasing Exchange

The Purchase Exchange function allows selected items to be exchanged for other items from an existing purchase exchange.

Position Editing

Mon, 01 Jan 0001 00:00:00 +0000

The Project Document Line editor is available as an additional means of editing items. This can be opened by navigating to the desired position and then clicking on Edit in the FastTab and then on Edit. The editor offers various setting options.

Click to enlarge

General

The General tab initially displays fields that can be found as columns in the bill of quantities. From the field As needed, new content is added.

Price calculation

Mon, 01 Jan 0001 00:00:00 +0000

With the update to version 22.11 and 23.11 of BE-terna Project, the price calculation has been completely switched to the new data model of Business Central. This means that the price lists for prices and discounts (purchasing/sales) in the Business Central Standard can also be used to their full extent in BE-terna Project.

The prerequisite for this is that the corresponding feature is activated in the function management:

Click to enlarge

Price History

Mon, 01 Jan 0001 00:00:00 +0000

Compared to the catalog item history, the price history is displayed in the document. This shows all manually made changes to the prices at item level. It can therefore be traced how prices have been changed in the past. The price history can be found in Document Processing under Details.

Click to enlarge

The use of the price history is activated by default.

Price shares

Mon, 01 Jan 0001 00:00:00 +0000

Price shares are partial costs and break down the unit price according to the cost types that cause it. As standard, these are wages, fabrics, equipment and other costs. Also included are any surcharges. Price shares can be defined and adjusted at document and item level.

Any number of price shares can be created. Due to the dynamic property of the price components, they must always be assigned a base category for master data transfer and project statistics.

Printing Options and Receipt Printing

Mon, 01 Jan 0001 00:00:00 +0000

The print settings for the current document can be accessed via Reports and, under General, via Select print variant.

Click to enlarge

Standard templates can be stored or existing ones can be edited.

Click to enlarge

Regardless of the selected form template, extra settings can be made. Some attitudes have already been explained elsewhere.

Click to enlarge

Field	Explanation
General
Settings template	Selects a stored print settings template.
Description	Stores a description for the settings template.
Form template	Selects a form template from the lookup.
Report ID	Specifies the report ID used to run the report.
Custom report layout code	Selects a report layout by code from the lookup.
Preferred variant	Marks the settings template as the preferred variant.
Text mode	Selects which text module is printed for individual lines. With Variable, the text stored for the item in the document is used (Print view). Only lines marked in the bill of quantities are copied.
Printer matrix	Settings for print flow and printer selection.
Minimum output level	Prints only fields on this level or higher. Useful for suppressing background elements.
Subject	Defines whether the document subject is printed.
Introductory remarks	Defines whether the introductory text is printed.
Title totals	Prints totals for each title on the document.
Title per page	Prints each title on a new page.
Carry forward	Prints a carry-forward total on each page.
Suppress zero quantities	Lines without quantity are not printed.
Suppress lines without price	Lines without price are not printed.
Suppress text lines	Text lines in the document are not printed. No effect on preface and closing texts.
Print item no.	Defines whether the item number is printed.
Sub-lines	Sub-lines are printed always, never, or based on the setting of the parent line.
Sub-lines of sub-lines	Sub-lines of sub-lines are printed always, never, or based on the setting of the sub-line.
Print sub-line prices	Defines whether prices of sub-lines are printed.
Do not print line prices	Defines whether line prices should be omitted from print.
Measurement rows	Prints measurement rows.
Show price shares	Shows individual price shares for each line.
Title heading	Defines whether titles are printed and which text variant is used.
Print image attachments	Defines whether image attachments are printed.
Finalize
Title summary	Defines whether an additional short or long title summary is printed at the end of the invoice.
Summary only	Defines whether only the title summary is printed. Individual lines are omitted and only the line total is shown.
Print net amount line text	Defines whether the text of the total net amount line is printed.
Print net amount	Defines whether the net amount is printed. Outputs the net amount as total services.
Material totals	Shows material totals on a document.
VAT lines	Shows or hides VAT on the document.
Surcharges/discounts net	Prints the net amount of any surcharges/discounts.
Surcharges/discounts gross	Prints the gross amount of any surcharges/discounts.
Partial invoices	Displays partial invoices in the document.
Partial payments	Prints any partial payments in the document.
Separate partial invoices and payments	Displays partial invoices and partial payments separately.
Print gross amount	Defines whether the gross amount is printed. In the invoice, it is shown as the amount due in EUR.
Closing remarks	Defines whether closing remarks are printed.
Print posting group text	Prints the posting group text stored in the document.
Do not append standard phrases	Defines whether standard phrases are printed.
Print phrase introduction	Prints an individual print section/line after the line table and before the partial-invoice phrase.
Print standard phrases	Defines whether standard phrases are printed and to what extent.
Print payment terms	Defines whether payment terms stored in the document/project are printed.
Print cash discount terms	Prints cash discount terms.
Print phrase ending	Prints an individual print section/line after the payment terms and the partial-invoice phrase.
Closing remarks after phrases	Places the closing text after the phrase block.
Print shipping address	Defines whether the shipping address is printed.

Processing delivery and fine call-offs

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes daily call-off processing in Controlled Sales Core: from blanket order and document call-off through delivery and fine call-offs to updated sales lines and downstream logistics processing. It is intended for teams that verify customer call-offs, align quantities and dates, and process released demand in dispatch control, consignment, or transport.

Business context

Blanket order or blanket agreement: Long-running customer agreement against which recurring call-offs are processed.
Document call-off: The business master record on the sales document. It connects customer, item, reference, plant, unloading point, contract data, and cumulative quantities.
Delivery call-off: A new call-off state with its own call-off number, call-off date, and call-off lines. It is released before operational processing.
Fine call-off: Detailed date and quantity demand. In daily work, these values appear as call-off lines; additionally, a separate Detailed Call Off can be created and released.
Cumulative quantities: Quantity progression from customer and internal shipment perspective. These values control which call-off quantity is actually transferred to sales lines.

Typical roles

Sales operations: verifies call-off data, references, and release readiness.
Order processing: checks sales lines, dates, open quantities, and downstream documents.
Warehouse and shipping: process released lines in dispatch control, picking, and transport.
Key user: handles exceptions for cumulative quantities, corrections, zero settings, and rerelease.

Prerequisites

Setup and number series are maintained.
The blanket order or sales document is available in a processable status.
Item, customer, reference number, plant, and unloading point are maintained correctly.
If mandatory logic is active, cumulative received quantity is available in the call-off.
Warehouse and shipping responsibilities are aligned across teams.

Process map

flowchart LR
  A[Review document call-off] --> B[Review fine call-off data]
  B --> C[Create delivery call-off]
  C --> D[Validate quantities and dates]
  D --> E[Release delivery call-off]
  E --> F[Update sales lines]
  F --> G[Run dispatch control]
  G --> H[Hand over downstream processes if required]
  H --> I[Continue logistics processing]

Operational flow

Process 1) Review document call-off on the blanket order The document call-off is the central link for call-off number, customer, item, and delivery context. +

Open document call-off data from the blanket order or sales document.
Verify reference number, item, customer order number, plant, and unloading point.
Check contract start, contract end, and the latest released call-off state.
Review cumulative delivered quantity, cumulative received quantity, and quantity in transit.
Clarify deviations before creating a new call-off state.

Process 2) Review and assign fine call-off data Fine call-off data provides detailed demand input for dates and quantities. +

Review or enter incoming fine call-off data if your process provides it separately.
Assign the fine call-off data to the correct customer, item, plant, unloading point, and blanket order.
Validate date relation, quantities, start/end date, and references per call-off line.
Use cumulative values and differences to quickly compare against the previous call-off state.
Transfer only business-valid fine call-off data into release processing.

Process 3) Create delivery call-off or Detailed Call Off A new releasable call-off state is created from the document call-off. +

Use Create Delivery Call Off when a new delivery call-off should be created for the existing document call-off.
Use Create Detailed Call Off when detailed fine call-off data should be processed as its own call-off type.
The system copies reference, item, customer, customer order number, plant, unloading point, and cumulative received quantity from the document call-off.
The new call-off number is continued from the latest released call-off state.
Until release, the new call-off remains business-editable.
Review proposed call-off lines by date and correct only business-relevant deviations.

Process 4) Validate quantities and dates before release Release should happen only when call-off data and quantity status are aligned. +

Check call-off date, call-off number, call-off lines, quantities, and dates.
Verify that the new call-off number is higher than the latest accepted call-off state.
Check whether requested dates are operationally feasible, and align deviations with sales operations, warehouse, or shipping.
Align unclear cumulative received quantities, delivery progress, or in-transit quantities with the customer process.
Check whether items are blocked or contract dates restrict the call-off period.
Confirm whether Ignore Qty. In Transit is intentionally set and matches the current business agreement.
Use the review and documentation rules further below on this page for corrections and zero settings.

Process 5) Release delivery call-off Release updates the call-off state and prepares operational sales quantities. +

Release only after completing the business checks.
On release, cumulative received quantity is written back to the document call-off.
The system updates the latest delivery call-off state and stores release date and released-by user.
Errors are recorded on the call-off so that they can be corrected directly.
If needed, the latest delivery call-off can be rereleased after quantity corrections.

Process 6) Verify sales lines Released call-off lines update matching lines or create new ones. +

If a matching sales line exists for item and date, the line is updated.
If no matching line exists, the system creates a new sales line.
Call Off Quantity remains visible as dedicated business information on the sales line.
Already shipped quantities, open order quantities, and existing warehouse documents are respected.
After release, verify quantity, Requested Delivery Date, location, and downstream readiness.

Process 7) Run dispatch control Due sales lines are transferred into shipment or picking processes. +

Start the relevant dispatch control entry with your filter setup.
Dispatch control works on released sales order lines and follows the relevant location setup.
Review the resulting lines for due date and required quantity.
Select lines and create required documents.
Optionally create picks in the same run if your process requires it.
Confirm that all selected lines were transferred into the target process.
This keeps demand planning in the call-off and logistics execution in dispatch control clearly separated.

Process 8) Hand over downstream processes After call-off release, logistics runs the appropriate downstream process. +

Hand over released sales lines only to the downstream processes required for the specific location and customer scenario.
Run transfer control where location-based replenishment is required.
Consider consignment when the target location is managed as a consignment location.
Continue shipment, transfer, consignment, or transport in the dedicated process pages.
Create transports only from posted shipment information.

Field catalog for end users

Document call-off

Field	Mandatory	Example	Meaning
Item No.	Yes	70000	Item controlled by call-off data
Reference No.	Yes	VDA-REL-2026-0815	Customer-specific item reference
Order No.	Process-dependent	RA-4711	Customer order or blanket-agreement reference
Plant	Yes	1000	Customer plant
Unloading Point	Yes	GATE-03	Customer unloading point
Last Del. Call Off No. (new)	No	2026-0141	Latest released call-off state
Cumulative Delivered Quantity	No	13,800	Internally cumulative shipped quantity
Cumulative Received Quantity	Setup-dependent	15,000	Customer-side cumulative received quantity
Quantity in Transit	No	400	Shipped but not yet confirmed as received by customer
Ignore Qty. In Transit	Process-dependent	Off	Controls whether in-transit quantity is considered in call-off calculation

Delivery and fine call-off

Field	Mandatory	Example	Meaning
Delivery Call Off Type	Yes	Delivery Call Off	Differentiates delivery call-off and Detailed Call Off
Del. Call Off No. (old)	No	2026-0141	Previous call-off number
Del. Call Off No. (new)	Yes	2026-0142	New call-off number
Del. Call Off Date (new)	Yes	2026-06-01	Business call-off date
Customer No.	Yes	10000	Customer of the call-off
Utilisation Key	Process-dependent	S	Utilisation key for reporting and downstream documents
Released	No	Yes	Indicates whether the call-off has been released
Last Error	No	Item blocked	Last release-check error

Call-off lines

Field	Mandatory	Example	Meaning
Call Off Date	Yes	2026-06-03	Demand date of the call-off line
Quantity	Yes	800	Call-off quantity for the date
Cumm. Quantity	No	15,800	Cumulative call-off quantity up to the date
Quantity Last Call Off	No	600	Quantity from the previous call-off on the same date
Difference	No	200	Difference to the previous call-off state
Start Date / End Date	Process-dependent	2026-06-01 to 2026-06-07	Period for multi-day or periodic demand

Handover to downstream process

Field	Mandatory	Example	Meaning
Requested Delivery Date	Yes	2026-06-03	Planned date on the sales line
Call Off Quantity	No	800	Business quantity transferred from the call-off
Outstanding Qty. in Orders	No	300	Open quantity from linked orders against the blanket order
Qty. to Ship	Process-dependent	0	Checked after call-off release and set later in shipment processing
Location Code	Yes	MAIN	Warehouse context for shipment or picking

Cumulative quantities and calculation logic

Cumulative quantities prevent customer call-offs from being processed twice or too low. The decisive comparison is between customer-side quantity status, internal delivery progress, and quantities already considered.

Project List

Mon, 01 Jan 0001 00:00:00 +0000

Project List

The project list provides an overview of all projects in a client.

Directly above the list is the ribbon with various functions.

Clicking on the project number opens the project card in edit mode.

Click to enlarge

Infoboxes

To the right of the project list are the infoboxes, which show different data depending on the type of infobox. The info box shows more details about the marked project. They can be hidden again via the “i” button above the infobox.

Project Map

Mon, 01 Jan 0001 00:00:00 +0000

Project Map

The project card represents the central administration interface of all receipts, documents, processes and tasks for a specific construction project.

By clicking on a project number within the project list, the corresponding project card can be opened.

Click to enlarge

Functions/Actions

The following actions are available on this map:

Start

Field	Explanation
Payment plan	Opens the project’s payment schedules.
Copy project tasks from…	Opens an editor for copying project tasks from another project into the current one.
Copy project tasks to…	Opens an editor for copying project tasks and moving them to a selected target project.
Create warehouse pick	Creates a warehouse pick for the project items based on project planning lines.
Create pick	Creates warehouse pick documents for the related project planning lines.
Statistics	Opens project-specific statistics.

Prices and Discounts

Project production

Mon, 01 Jan 0001 00:00:00 +0000

The project document editor can also deal with the topic of contract manufacturing for the production of small and medium quantities. Routings and production BOMs are mapped at subitem levels. These can be edited and supplemented so that calculations can be made down to the lowest level of BOMs in the project document.

It also provides its own (configurable) view for manufacturing.

Click to enlarge

In addition, there is a tab in the BE-terna Project facility specifically for the topic of production. There you can set up the price shares on which the processing or set-up time is to be displayed. Furthermore, a resource specification for the routing (in the bill of quantities) must be created and specified accordingly. If production articles are also to be created from the bill of quantities, a separate template for production articles is required.

Purchasing Exchange

Mon, 01 Jan 0001 00:00:00 +0000

The purchase exchange offers the possibility to start price inquiries from the service specification and to retrieve the updated prices in a document.

The purchase exchange is called up via Actions in the navigation menu under Process. A card opens in which the supplier can be selected. It should be noted that a vendor must be defined for the supplier. The receipt for the purchase exchange is then opened.

Click to enlarge

Raw material surcharges

Mon, 01 Jan 0001 00:00:00 +0000

In the position

To enter or display a raw material, open the “Raw material surcharges” tab in the navigation menu under Details. In this window, there are various setup options for maintaining multiple raw materials in the current position. However, raw material surcharges can also be entered manually at the item. You can choose from a list of non-ferrous materials from the master data or use individual abbreviations. However, the prices then have to be maintained manually.

Raw materials

Mon, 01 Jan 0001 00:00:00 +0000

Non-ferrous

To enter a raw material, enter “non-ferrous” in the search function. In the list that opens, a new entry can be inserted via New. The daily price is set manually in the Daily Price (MW) column. The daily price always refers to the price base weight. If the value is 800 in the Daily Price field and 100 in the Price Base Weight field, 100 units of weight would correspond to a price of 800.

Reason Codes

Mon, 01 Jan 0001 00:00:00 +0000

General reason codes

Reason codes are freely definable identifiers that companies can use to document the motives or causes for certain business transactions. They are used to better classify, evaluate and analyze bookings.

Typical uses for reason codes

Reason codes can be used in many places in Business Central, including:

Inventory postings (e.g., inventory corrections, manual repostings)
Item Booking Sheets
Sales and purchase documents
Production Bookings
Service receipts
Financial postings

Setup and function

Reason codes are maintained centrally under “Setup - Reason codes”.
They can then be specified per document line, journal line, or posting.
In the posting history (for example, item entries, inventory entries, general ledger entries), the respective reason code can be traced.
They are often used for internal analysis, tracking or to prepare evaluations (e.g. why a warehouse was withdrawn: shrinkage, theft, samples, returns, etc.).

Click to enlarge

REB Export

Mon, 01 Jan 0001 00:00:00 +0000

Recorded measurements can be exported in REB format and in GAEB DA 31 format. The function is available from Actions > Export > Measurement.

Click to enlarge

An export dialog appears with various options:

Click to enlarge

REB version

Selection	Explanation
1979	In this version, the OZ pattern is mandatory: only documents containing OZ pattern 1122PPPPI (in BE-Project #2241) can be exchanged. Output sorting follows sheet number and column index.
2009	In this version, the OZ pattern is limited to a maximum of 9 characters. Within that limit, the OZ pattern can vary. Output sorting follows sheet number and column index.
GAEB DA31 (1979/2009)	In these versions, OZ patterns with more than 9 characters can be output. Sorting follows line numbers. OZ pattern 1234PP is recommended.

It is advantageous to agree with the business partner which version he can read successfully so that it can be decided which version should be used for export.

Receipt Line Search

Mon, 01 Jan 0001 00:00:00 +0000

Under the Archive menu, you can find the Receipt Line Search, which can be used to filter the sales, payment, and discount lines of all receipts.

Click to enlarge

The Clear Filters action removes all applied filters.

Field	Description
Location Code	Specifies the location to filter by.
Cash Register	Specifies the cash register to filter by.
POS Process	Sets the filter to a POS process number.
Receipt No.	Sets the filter to a receipt number.
Start Date	Defines the start date of the search period.
End Date	Defines the end date of the search period.
Item No.	Specifies the item number to filter by.
Receipt Type	Filters the receipt lines by a specific receipt type.
Tender Type	Filters the payment lines by the selected tender type.
Customer No.	Sets the filter to a customer number.
Customer Name	Sets the filter to a specific customer name.
Salesperson Code	Specifies the salesperson code to filter by.
Cancelled	Defines whether only cancelled receipts should be displayed.
Employee Sale	Filters the lines to receipts with an employee sale.
Discount Type	Filters the receipt lines by a specific discount type.

If receipt lines exist for the applied filters, they are displayed in the corresponding overviews below the filters.

Receipt Report

Mon, 01 Jan 0001 00:00:00 +0000

The receipt report is used to obtain an A4 printout of the filtered receipts of the cash register. The receipts, together with their lines, are displayed as a list.

Click to enlarge

Resources

Mon, 01 Jan 0001 00:00:00 +0000

Resources

A resource is either a person or a machine associated with a project. To create or edit resources, you can access the list of all resources via the search function by entering the keyword resources. If you click on a resource number, the corresponding resource map opens.

Click to enlarge

In the resource, you can specify a resource group in addition to a costing group and overheads. As a price share category, it makes sense to use wages, materials or external services for resources. Alternatively, a fixed sales price can also be set here.

Return Reason

Mon, 01 Jan 0001 00:00:00 +0000

Under Assignment → Return Reason, return reasons can be allowed and/or excluded per cash register, per location, or for all cash registers.

Click to enlarge

Reverse project invoice

Mon, 01 Jan 0001 00:00:00 +0000

A posted project invoice can be cancelled on the project card in the Project Invoices area by calling the Cancel Final Invoice action in the All Tasks area.

View of project invoices on the project map:

Click to enlarge

Procedure:

When the action is called, a credit note is created and matched with the invoice, after which the invoice is canceled. In addition, the project voucher wizard is opened to create a corrected invoice document.

Role Center

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The role center provides the central entry point to the operational workspaces of BE-Commerce. It consolidates the most frequently used lists and views for user and admin tasks.

Business Value

Fast access to relevant work lists.
Separation between user and admin views.
Focus on the most important operational documents and checks.

Content Focus

User View

The user view shows documents that are ready for processing, archived documents, and incorrect entries. It also includes contacts and other daily work lists.

Search the system

Mon, 01 Jan 0001 00:00:00 +0000

General Search

In the Role Center, the search button is located at the top right of the window.

Clicking on the button opens an input window. Search terms can be entered in this window. The system suggests actions, pages, reports, etc. to match the search term.

Click to enlarge

Search for records

If you want to search for specific records in the areas of addresses, projects, articles or maintenance, the Search action can be used.

Set up an on-premise container

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the recommended approach for running BE-Code as an on-premise installation on a Windows server with Docker Compose.

Prerequisites

Windows Server build 22H2 or later with at least 1 CPU core, 1 GB RAM, and 10 GB of free disk space.
Installed and configured Docker Engine and Docker Compose.
Access to the BE-terna Azure Container Registry becode.azurecr.io; authentication uses ACR tokens, one token per customer.
A valid SSL certificate as cert.pfx in a host directory (for example C:\certs).

Recommended order

Create an application folder, for example C:\be.code.
Create the files docker-compose.yml and .env in that folder.
Fill in docker-compose.yml.
Fill in .env and set passwords.
Start the container and verify availability.

Setup building blocks

Maintain the Docker Compose file

In the application folder, create docker-compose.yml with the following content:

Specifications

Mon, 01 Jan 0001 00:00:00 +0000

The tabs under Details will be discussed in more detail later in the [Calculation](/BE%2Dterna Project Documentation/Calculation).

General

In the General tab, master data of the project is stored and basic settings can be made. The majority of the fields have already been covered in the project map, which is why we will not take a closer look at them at this point. If the Budget-effective field is selected, the amounts from the document are included in the statistics in the Debit area. This is pre-assigned for orders. However, it can be manually disabled or enabled for other receipts.

Standard Import and Export

Mon, 01 Jan 0001 00:00:00 +0000

The Import/Export action can be used to import and export large amounts of data (e.g. demo data) as a text file.

Click to enlarge

After clicking on Interactive Import, a wizard for importing data opens.

Click to enlarge

Statistics and Project Controlling

Mon, 01 Jan 0001 00:00:00 +0000

Project Statistics

To view an evaluation for a project, go to Start on Statistics in the project map.

Click to enlarge

The project statistics display purchase and sales values as well as contribution margins with the respective price shares in the Target, Measurement, and Actual columns.
In order for the receipts to be recorded in the target, the tick must be ticked Budget-effective. Orders are automatically budget-effective.

Storing an article from the webshop in the bill of quantities

Mon, 01 Jan 0001 00:00:00 +0000

Articles from the webshop can be stored via the specifications in a project document. To do this, the corresponding costing items in the desired number must first be created in the bill of quantities.

The marked calculation article can then be ordered directly via the webshop via Edit and IDS Deeplink.

Click to enlarge

However, multiple selection is not possible. To do this, an ordinary order must be triggered via Actions and Process with Purchase….

Storing Master Data at the Supplier

Mon, 01 Jan 0001 00:00:00 +0000

In the “DATANORM” tab, which is located in the supplier card, various master data can be stored.

Click to enlarge

Field	Explanation
Open Connect Lieferant	DATANORM-Download mit Hilfe von Open Connect.
Import Codepage	Codepage der DATANORM (i.d.R. nicht nötig).
Neuanlage erlaubt	Drei Auswahlmöglichkeiten: Nicht erlaubt, Erlaubt und Erlaubt bei KZ „N“. Erlaubt bei KZ „N“ legt neue Katalogartikel nur bei DATANORM-N-Sätzen an (Neuanlagesätze), Erlaubt/Nicht erlaubt unterscheidet ob Neuanlagen von Katalogartikeln generell eingelesen oder ignoriert werden sollen.
Änderung erlaubt	Bietet drei Auswahlmöglichkeiten: Nicht erlaubt, Erlaubt und Erlaubt bei KZ „A“. Über Erlaubt/Nicht erlaubt kann festgelegt werden, ob vorhandene Positionen im Artikelstamm mit Änderungen überschrieben, bzw. nicht überschrieben werden sollen. Bei Erlaubt bei KZ „A“ kann ausgewählt werden, ob die Änderungen nur bei DATANORM-A-Sätzen eingepflegt und sonstige Regeln beachtet werden sollen (z.B. die Art der gewünschten Rabattpflege).
Matchcode-Änderung erlaubt	Teilt dem System mit, ob vom DATANORMSATZ der Matchcode übernommen werden soll.
Preisänderung erlaubt	Gibt an, ob die Artikelpreise im Artikelstamm ersetzt werden dürfen. Ist dieses Feld nicht ausgewählt, werden nur die Texte beim Import geändert.
Umbenennung erlaubt	Artikel darf umbenannt werden.
Löschen erlaubt	Artikel darf gelöscht werden.
SET-Artikel als Zubehör importieren	Legt fest, ob SET-Artikel als Zubehörartikel importiert oder als Artikelpakete angelegt werden sollen.
Paketkomponentenlieferant	Hier kann ein Lieferant ausgewählt werden, von dem man andere (Artikel-)Paketkomponenten bezieht. In diesem Feld wird das Kürzel des Lieferanten angegeben.
Paketkomponentenlieferantenname	Hier kann ein Lieferant ausgewählt werden, von dem man andere (Artikel-)Paketkomponenten bezieht. In diesem Feld steht der vollständige Name des Lieferanten.
Keine SET-Komponenten-Validierung	Spielt Pakete ein, ohne zu prüfen, ob die angegebenen Komponenten bereits vorhanden sind oder nicht.
Nach Import Preise aktualisieren	Bei Aktualisierung der DATANORM werden durch einen Stapellauf die Preise der zugehörigen Lagerartikel gepflegt.
Verkaufspreis 2 aus Listenpreis	Bewirkt, dass diverse Aufschläge oder Kalkulationen nicht wirken, sondern der Listenpreis aus DATANORM geführt wird.
Nur Referenzartikel	Verschiedene Anbieter (z.B. EDS-Klein) stellen Datenkataloge/Leistungsbücher in Form von DATANORM zur Verfügung, welche nur sog. Referenzartikel bzw. die zugehörigen Artikelreferenzen enthalten. Solche Lieferanten können nun mit dem Kennzeichen nur Referenzartikel versehen werden.
Bevorzugter Referenzlieferant	Zusätzlich kann ein bevorzugter Referenzlieferant ausgewählt werden. Dieses Kennzeichen muss vor dem Import gesetzt werden, da dieses beim Import an die Katalogartikel vererbt wird.
Bevorzugter Referenzlieferantenname	Verweis auf den Lieferanten, welcher im Stamm hinterlegt ist.
Anschließende Preispflege	Bewirkt eine Validierung der Rabattgruppen nach Import des Kalkulationsartikels, sodass die hinterlegten Rabatte auch auf den Kalkulationsartikeln angewandt werden.

Structure of the Role Center

Mon, 01 Jan 0001 00:00:00 +0000

The Role Center represents the home screen in Microsoft Dynamics Business Central. The look and feel design of the Microsoft Office product range ensures simple and intuitive operation.

Click to enlarge

Structure of the Role Center

The Role Center is divided into different areas:

Current client
Explore business features
Bookmark
Business Insights
Direct Call Actions
Activities/Key Figures
“tell-me” search function and settings

The client name is located at the top left of the window and shows the user which client he is currently in.

Suppliers & Creditors

Mon, 01 Jan 0001 00:00:00 +0000

Vendors and vendors are held and set up for use in two separate tables. To set up the suppliers, the list of suppliers must be called up via the search function.

Click to enlarge

On the map of a respective supplier, the respective tabs General, DATANORM, UGL and IDS are available.

Click to enlarge

If a new supplier is to be created, this must be done via the New action in the list of suppliers. Then the Kennzeichen field must be filled in as an identifying feature. Furthermore, a name and a search term can be assigned to the supplier. The link to an existing vendor is done using the Vendor ID field.

The bill of quantities with FastIndex and table header

Mon, 01 Jan 0001 00:00:00 +0000

In this area, the bill of quantities is processed. Most of the functions for this are located in the FastRegister.

Click to enlarge

Manage

Click to enlarge

Field	Explanation
Expand/Collapse	Expands or collapses the currently selected position. If the total amount line is selected, the entire bill of quantities is expanded or collapsed.
Expand all	Expands all positions.
New title	Inserts a new title.
New position	Creates a new position in the bill of quantities.
New subposition	Inserts a subposition under the selected position.
Long text search	Opens a dialog to search positions by long text.
Previous position	Switches to the previous position in the bill of quantities.
Next position	Switches to the next position in the bill of quantities.

View

Click to enlarge

Update costing items

Mon, 01 Jan 0001 00:00:00 +0000

Various actions for updating costing items can be found on the costing item card under “Actions” –> “Open Masterdata”.

Click to enlarge

There are the following update options:

Update master data
The costing item is updated depending on the global or supplier-specific setup
Update master data manually
The data package can be individually defined for updating via a dialog box.
Update links
Only attachments (e.g. images, documents) are updated.
Update prices
Only the item’s pricing data is updated.

Update of existing articles

Mon, 01 Jan 0001 00:00:00 +0000

BE-terna Project offers the possibility to update existing calculation articles.

To update the articles only for a specific supplier, select the function Costing Items in the corresponding supplier card under Supplier. A list of all costing items from the supplier opens. If you select the desired article that is to be changed, the new values must finally be entered and confirmed.

Click to enlarge

To change the properties for all costing items, navigate to the list of catalog items using the search function. Here you will find the function Costing Item Maintenance under Related to Costing Articles. The list can now be filtered in the map and the desired changes can be made under (other) options.

Versioning of project documents

Mon, 01 Jan 0001 00:00:00 +0000

BE-Project offers the possibility to save document versions and thus call up and activate older versions of a document at a later time.

Document version table

To access the different versions, click on Manage in the project documents area of the project card and then on Versions. A new window opens with all versions of the selected project document.

Click to enlarge

To make it easier to track the changes, the Editiert am and Editiert Zeit columns contain the date and time when an edit was made. The Editiert von column shows the user who was the last to make a change to the document. Erstellt of Benutzer indicates the author of the receipt. It is possible to store a description for each version. When the version of the project document was created can be seen in columns Datum Erstellt and Erstellt Zeit.

Warehouse receipt

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When IC shipments arrive from the partner, BE-terna Intercompany can create warehouse receipt documents from them automatically. This keeps inventory posted without forcing users to enter receipts manually.

Business value

Automatic inventory posting on incoming IC shipments – no manual entry required.
Partial shipments are supported when the purchase order is set up accordingly.
Consistency between purchasing and inventory, because the receipt carries the same lines as the IC shipment.

Focus areas

Prerequisites

The relevant location uses warehouse receipt documents.
Automatic posting of the warehouse receipt is enabled for incoming IC shipments.

Interaction with invoicing

When shipping runs through the warehouse receipt, you cannot invoice through the purchase order. In that case the incoming invoice must use Create purchase invoice (standard).

Web Service

Mon, 01 Jan 0001 00:00:00 +0000

Under Data Transfer → Web Service, the web service connections to the cash registers and to the main system are stored.

Click to enlarge

Note: For web service calls, a separate BC instance with NavUserPassword authentication must be installed on the target system in each case.

Setup

General

Click to enlarge

Field	Description
Location	The location code
Cash Register	The cash register code
Type	POS: Connection to the cash register (per cash-register master). ERP: Connection to the main system (once for all cash-register masters).

Settings

Click to enlarge

Work Expense Types in the Document

Mon, 01 Jan 0001 00:00:00 +0000

Exactly one expense type can be defined for each item. Depending on the type of workload, the “wages time costs per minute” are adjusted. To display the corresponding column in the table, select the “Working Effort Type” field in the user-specific view.

Click to enlarge

DACHSER

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DACHSER-specific setup in Shipping Labels. It covers the reference lists for products, branches, and package types as well as the API keys, endpoints, divisions, depot selection, and fallback package properties required for productive label requests.

Prerequisites

The shared Shipping Labels setup is complete.
DACHSER test and productive endpoints are available.
The required API keys for the relevant environment are available.
Products, branches, and package types are known from the DACHSER onboarding material.

Recommended sequence

Maintain the DACHSER product list.
Maintain the DACHSER branch list and package types.
Assign test or productive endpoint and API key.
Select division, depot, product, label count, and fallback package properties.
Validate the setup first in test mode and switch to productive mode only for go-live.

Setup components

Build the DACHSER reference lists first

DACHSER is not only a credential setup. Before the main line becomes usable, you should maintain the supporting lists for products, branches, and package types.

Sales Quotes and Orders

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Sales Quotes and Orders are the operational entry point into contract-related sales processes in Professional Services. When a quote is created, a new sales contract can already be created in parallel or an existing contract can be extended, so sales activities and recurring services are prepared together from the beginning.

Prerequisites

customer, project, and the intended sales type are defined
standard pre- and post-texts plus the relevant contract and billing parameters are configured
it is clear whether a new sales contract should be created or an existing one should be extended

Functional focus

New sales quote with sales contract

When you create a sales quote with the Professional Services sales type, a new sales contract can be generated at the same time. Customer, project, duration, and further document data are therefore prepared not only for the quote, but also for later contract and billing logic.

Version 26.0.0

Mon, 01 Jan 0001 00:00:00 +0000

Summary

Version 26.0.0 delivers the foundation for posting preview, the calculation matrix, c/o enhancements, service-report-related processes, and extended report selection. At the same time it includes several fixes in status handling, print output, translations, and ticket behavior.

26.0.0 — 2025-05-23

New features

35580 - Posting preview and find entries
19811 - Test codeunits
35138 - Assignment texts from-to
26169 - Cue: My open orders
35143 - Revised pre- and post-texts
29118 - Implemented the calculation matrix
31949 - Work order: prefill customer no.
32488 - Reworked the CSP module
34242 - Added service-report integration in the menu
27965 - Invoice CO
32248 - Billing: c/o fields
29898 - Transfer c/o fields into documents and sales contracts
27965 - ID like Purchase Line
24434 - ITK order signature for technician and customer
29427 - c/o fields in reminders
27965 - General translations
26163 - Reworked service report
34273 - Extend sales report selection: credit memo draft
19810 - Test codeunits: posting groups

Bug fixes

32488 - Status New error
31951 - Correct label for the field “Type” in order lines
33970 - Fixes for recurring billing and service billing
33975 - Fixes and additions for tickets
34948 - Duplicate “Long Text” tab on the SLA card
34952 - Missing translation in SLA service lines
34950 - Superfluous ticket notification
34243 - RDLC print error in the service report
34273 - Report selection: Format Address
33980 - Fixes for work orders

Cash Register Closing

Mon, 01 Jan 0001 00:00:00 +0000

To perform a cash register closing, you must first be in an empty receipt and then initiate the process via Receipt Type -> Cash Register Closing.

Click to enlarge

If the following prompt is confirmed with Yes, the process for carrying out a closing is started.

Click to enlarge

Cash Revenue Registration

Depending on the setting in the cash register setup, there are two ways to capture cash revenue first: by denomination or as a total amount.

Color Management

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the maintenance of colors and supplier colors for Connector Commerce Interface to Fashion.

Webshop Colors

For colors stored in the system, you can maintain webshop descriptions in multiple languages. These descriptions support a consistent presentation of colors in the shop across all relevant channels.

Click to enlarge

Supplier Colors

Dedicated webshop descriptions can also be stored for supplier colors. This makes it possible to translate supplier-specific color naming into a shop-ready presentation.

Data Log

Mon, 01 Jan 0001 00:00:00 +0000

In the Data Log, all logs relevant to the cash register are stored.

Click to enlarge

The entries support faster analysis in the event of support requests.

Note: All records older than 100 days are deleted automatically when the cash register starts.

Demoscopic Query

Mon, 01 Jan 0001 00:00:00 +0000

If Demoscopic Queries are set up and Assigned, the query appears as soon as the sales receipt has been completed.

Click to enlarge

DHL Express

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Express-specific setup in Shipping Labels. It focuses on product selection, allowed service options, customer credentials, pickup-window properties, and return-service behavior for national and international express scenarios.

Prerequisites

The shared Shipping Labels setup is complete.
DHL Express test or productive credentials and URLs are available.
The required DHL Express products and account information are known.
The relevant shipping agent service is already maintained in Business Central.

Recommended sequence

Maintain the DHL Express product list.
Define the allowed service options per product.
Assign credentials and the correct environment URL.
Maintain pickup times, closing time, sender email fallback, and return-service behavior.
Test one realistic shipment with the selected service option combination.

Setup components

Start with products and allowed service options

DHL Express combines products with selectable service options. The public-facing setup should therefore explain two layers:

DSR and Distribution Matrix

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is written for responsible business users who steer and review distribution decisions in MDM. Within MDM, DSR is used as the term for Selected Record Distribution. It explains how DSR filters and the distribution matrix work together so that you can define and review, in a traceable way, which records are distributed to which target companies for released relations.

Business value

Makes distribution decisions transparent and reviewable per relation and target company.
Reduces manual follow-up work because you can maintain business exclusion rules centrally through DSR filters.
Supports target-company-specific rule maintenance without rebuilding the entire relation.
Helps teams re-evaluate existing data in a controlled way after a filter change and align the result with business stakeholders.

Focus

DSR as a control layer for record distribution

DSR adds an extra decision layer for individual records on top of the MDM relation. When record distribution is selected for a relation and the relation is released, MDM evaluates incoming records against the maintained DSR filters and derives the initial distribution decision from that result. For responsible business users, this is the central control point for deciding which records should reach target companies productively and which should remain excluded by design.

Example: integration with Business Central

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This example shows how BE-Code plugs into Business Central and how you can follow the execution through the BE-Code register. The example follows the shipped demo scenario for item identifiers.

Context

BE-Code runs as a middleware service. Setup is described in BE-Code setup.
When an item identifier is created or modified, the shipped event subscriber automatically inserts an entry in the BE-Code register and calls the service.

Prerequisites

The BE-Code service is available (on-premises or Azure Container Instance).
Basic authentication credentials for the service are at hand.
The BE-Code app is installed in Business Central.

Process catalog

Process Step 1 – Maintain the BE-Code setup Enter the server URL and authentication, then test the connection. +

In Business Central, open the BE-Code Setup page.
Enter the server API URL, for example https://<fqdn>:1880/becode.
Enter the basic authentication credentials.
If needed, enable the item identifier integration and maintain the API path and the default identifier parameter.
Choose the Check connection action. A success message confirms that BE-Code is reachable.

Process Step 2 – Verify execution in the BE-Code register Trace the generated entries and stored images. +

Create an item identifier or modify an existing entry.
Open the BE-Code Register page. One record is created per operation.
Review the status and the generated images.

The base64-encoded image is stored as a media set. You can reuse the matching GUID identifier in other tables without asking for the image again.

Export Item List

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns a list of item numbers changed since a given timestamp.

Method

Operation: ItemListExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

changedSince_P

Response

XML in itemListExport_PX with affected item numbers.

Result

The webshop can run delta synchronization and fetch only changed items.

Export Price

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint provides price data per webshop channel, optionally filtered to a single item.

Endpoint

Method: GET
URL pattern (channel-wide): http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/itemPrices?$filter=webshopChannelCode eq '<webshop-channel-code>'&$expand=itemVariantPrices($expand=prices)
URL pattern (single item): http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/itemPrices?$filter=webshopChannelCode eq '<webshop-channel-code>' and itemNo eq '<item-no>'&$expand=itemVariantPrices($expand=prices)

Required Parameters

webshopChannelCode in the filter

Key Response Fields

Header: systemId, webshopChannelCode, itemNo, salesPricesSentToWebshop, lastSalesPriceChangeAt
Variants: code
Price lines: currency, unitPrice, customerPriceGroup, priceIncludesVAT

Result

The webshop receives current pricing structures per channel and optionally per item.

Initial data

Mon, 01 Jan 0001 00:00:00 +0000

The “Initial Data” action starts the wizard for the BE-terna Project Quick Start. This wizard also starts when you set up a new client. The import of the initial data ensures that BE-terna Project is operational. Demo data can also be imported at this point.

Click to enlarge

Item Releasing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to release items to webshop channels in BE-Commerce. The goal is a repeatable approach to publish items only with complete and consistent data.

Prerequisites

Setup and channel assignments are configured.
Categories, attributes, and required descriptions are maintained.
Validation and release responsibilities are clearly assigned.

Recommended Sequence

Complete item and variant data per channel.
Run release validation and review the error protocol.
Fix issues, re-validate, and then release per channel.

Configuration Building Blocks

Release-Relevant Mandatory Data

Verify minimum requirements for category assignment and description fields.
Complete language- and channel-specific content before release.

Error Handling

Work through error protocols by root cause.
Standardize recurring corrections for repeatable quality.

Process Release Guardrails Rules for stable and traceable item publishing. +

Execute releases channel by channel with explicit validation steps.
Never skip error protocols; re-validate after each correction cycle.
For bulk updates, validate with a small item subset first.

Location Report

Mon, 01 Jan 0001 00:00:00 +0000

The location report displays the turnover for a filtered location. The filter page that opens when you run the report can be used to filter for a specific location.

Click to enlarge

Logistics scenarios

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains which standard Business Central logistics variants are available and how Controlled Sales Core fits into the operational flow. The key question is simple: Which action belongs to which location setup and document type?

Core Principle

In Business Central, the location setup determines whether a document can be posted directly or whether shipment and/or pick documents must be created first. Controlled Sales Core sits exactly at that decision point: it filters the relevant lines, creates the necessary follow-up documents, and keeps the operational selection transparent.

Production Planning

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the extended planning workflows in BE-terna Manufacturing. It helps users process demand from sales orders or planning suggestions, set up automatic planning runs, and include special scenarios such as production families or additional personnel and tool requirements in a structured way.

Business Value

Transfers the sales unit of measure and sales quantity directly into the production order during order planning.
Speeds up planning worksheet handling through bulk actions for action messages.
Enables automatic planning runs with reusable filters, planning horizons, and target worksheets.
Supports production families for co-products or multiple outputs per operation.
Makes additional personnel and tool requirements visible already in the routing and later in the production order.

Area: Production Planning

Order planning with sales units of measure

When you derive a production order from a sales order through Actions > Plan > Planning, BE-terna Manufacturing transfers not only the demand but also Unit of Measure and Quantity from the sales line. This keeps planning in packages or pallets intact instead of automatically converting to the base unit.

Receipt

Mon, 01 Jan 0001 00:00:00 +0000

Receipt setup can be used to define how specific receipt types should be printed. You can define whether a receipt type is output via the receipt printer or as a report. The report to be used can be defined, and the number of printouts can be selected.

Click to enlarge

Setup

Field	Description
Print Type	Receipt print or report print
Usage	Selection of the receipt type for which the setup should be used
Location	Location of the cash register (if the location is left blank, the setup applies to all locations)
Cash Register	ID of the cash register (if the cash register is left blank, the setup applies to all locations)
Number of Printouts	Number of printouts (for a standard receipt, the minimum is 1, otherwise 0)
Report ID	ID of the report (available only if report is selected as the print type)
Report Name	Name of the report (filled automatically)

Reservation

Mon, 01 Jan 0001 00:00:00 +0000

Under Assignment → Reservation, the settings for reservations and parked receipts can be defined per cash register, per location, or for all cash registers.

Click to enlarge

Field	Description
Type	defines the type of setup; Reservation and Parked Receipt are available
Location	defines the location
Cash Register	defines the cash register number
Post Transfer	indicates whether a transfer should be posted during the transaction
Receipt Type Description	allows a separate label for printing the reservation/parked receipt
Transfer Location	defines the location to which stock should be transferred
Duration	defines the reservation duration (date formula), if no date is specified, the cashier must enter the expiration date during reservation

Sales

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The sales functions of Professional Services connect quotes, orders, sales contracts, and recurring billing in one continuous flow. This allows recurring services to be sold, structured, calculated, activated, and billed on an ongoing basis.

Business value

recurring services can be embedded directly in quotes and orders
sales contracts provide the binding framework for support, maintenance, subscriptions, and similar service models
recurring billing enables batch invoicing across multiple contracts

Functional focus

Quotes and orders

When you create sales quotes, you can generate a new sales contract in parallel or extend an existing contract. This means sales activities and later billing are prepared together from the beginning.

Search Setup

Mon, 01 Jan 0001 00:00:00 +0000

In the setup of the search function in BE-terna Project, various parameters for the search behavior can be defined. What these are in detail and what effects they have is explained in more detail in the following for the setup wizard.

Click to enlarge

Setup Wizard

The setup wizard guides you step by step through the search setup of BE-terna Project.

Set up an Azure Container Instance

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the recommended approach for running BE-Code as an Azure Container Instance (ACI) without your own server infrastructure. You can optionally bind the service to Azure Key Vault to manage certificates centrally.

Prerequisites

Active Azure subscription with sufficient permissions to create resource groups and Container Instances.
Azure CLI installed on your workstation, or access to the Azure portal.
Access to the BE-terna Azure Container Registry becode.azurecr.io; authentication uses one ACR token per customer.
Optional: an Azure AD service principal with access to the Key Vault and a valid SSL certificate stored in the Key Vault.

Recommended order

Sign in to Azure and to the Container Registry.
Create a resource group.
Create the Azure Container Instance.
Verify the container and set up DNS forwarding.
Test availability and configure the service URL in the BE-Code setup in Business Central.

Setup building blocks

Shipment

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

For sales shipments an IC shipment document can be sent to the partner. It is the basis for the automatic warehouse receipt on the purchase side.

Business value

The purchasing partner sees the shipment in the system immediately, not only via the invoice.
The warehouse receipt at the receiver can be created automatically – no manual entry required.
Shipping and invoicing stay cleanly separated and traceable.

Focus areas

Setup on the IC partner card

On the IC partner card you enable sending the IC shipment. Without this setting only the invoice is transferred.

Transaction status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Every IC transaction moves through several statuses. This page describes what each status means and the typical transitions so users can see where a transaction stands and what to do next.

Access in Business Central

The status is visible in the IC inbox, IC outbox, and the transaction overviews.

Prerequisites

Access to IC transaction lists.
Basic knowledge of the IC flow (send, accept, post).

Activities

Check status regularly and handle outliers early.
On Error look up the cause in the error log.

Fields and actions

Status	Meaning
New	Transaction has been created but not sent/accepted yet.
Open	Transaction is being processed (for example by the job queue).
Error	Processing has aborted; details are in the error log.
Accepted	Receiver has picked the document up.
Rejected	Transaction was intentionally not processed.
Completed	Transaction has run through and is archived.

Monitoring and troubleshooting

Several transactions in Open over a longer time → check the job queue.
Do not mass-retry transactions in Error without understanding the cause.

Best practices

Include the status field in the daily tiles of the role center.
Document Rejected deliberately so that later questions stay traceable.

Unit of measure mapping

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When sender and receiver use different units of measure for the same item, the mapping makes sure quantities are transferred consistently and converted correctly. This page describes how to create and use UoM mappings.

Business value

Quantities and prices stay consistent despite differing units of measure.
Manual conversions at the receiver are no longer needed.
The classic “forgotten conversion” error is removed by stored factors.

Focus areas

Creating a mapping row

On the U. of Measure Mappings page, create one row per combination: source UoM in the sending company, target UoM in the receiving company, and the conversion factor.

Vendor and purchase

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page groups the vendor and purchase setup steps that are specifically needed for intercompany exchange. They adapt the standard Business Central behaviour to the IC flow, especially around drop shipments and subsequent quantity changes.

Prerequisites

Purchases & payables setup in Business Central is completed.
Permissions for the Purchases & Payables Setup page are granted.

Setup building blocks

Allow invoicing drop shipment before sales

By default, Business Central blocks invoicing a purchase order for a drop shipment until the linked sales order has been invoiced. This switch lifts that lock.

Billing Types

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Billing Types define how recurring services are represented commercially and operationally within a sales contract in Professional Services. They provide the frame for calculation, duration, billing rhythm, and the detailed billing-type assignments from which recurring services are later invoiced.

Prerequisites

a suitable sales contract exists or is prepared from a business perspective
number series and, if needed, billing-type templates are configured
the type, calculation logic, billing rhythm, and project reference are aligned

Functional focus

Billing types and templates

Billing types can be created manually or derived from templates. Templates help prepare recurring contract models such as financing, service, rental, or maintenance consistently and assign them to multiple contracts under the same rules.

Sales Contract

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The sales contract is the central object for recurring services in Professional Services. It combines project, customer, contract duration, billing logic, and concrete contract lines in one document and forms the basis for recurring billing, contingents, and service-related add-ons.

Prerequisites

The core Professional Services setup is maintained.
Number series, contract types, billing types, SLA templates, and contingent templates exist.
The related project and customer are already available.

Functional focus

Contract structure

A sales contract is structured in three layers:

Service Level Agreements

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Service Level Agreements define the service-related framework of a contract in Professional Services. They describe the committed response, arrival, and restoration times, the time window in which service is delivered, and how these commitments relate to the sales contract, project, and connected contingents.

Prerequisites

number series and, if needed, SLA templates are configured
a suitable sales contract and project reference are available
business commitments for priority, response time, and on-site service are aligned

Functional focus

SLA templates and contract linkage

SLAs can be created directly or derived from SLA templates. In practice they are closely linked to sales contracts and billing types so that recurring services are governed not only commercially, but also by explicit service commitments.

Recurring Billing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Recurring Billing consolidates due contract invoices from multiple sales contracts into one shared processing run. It is the central mechanism for invoicing recurring services efficiently and with control.

Prerequisites

activated sales contracts with a correctly maintained next billing date exist
year, month, and posting date for the planned billing run are defined
if required, filter criteria are prepared to limit the run to a specific contract population

Functional focus

Billing period and contract selection

The recurring invoice list works on a calendar basis using year and month. In addition, the contract view can be used to restrict which sales contracts are included in a specific run. This supports both broad batch runs and targeted subsets.

Contingents

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Contingents control which quantities or amounts are available to a customer within a contract period in Professional Services. They therefore connect the promised service scope with recurring provisioning and actual consumption in ticket, work-order, and billing processes.

Prerequisites

a suitable sales contract exists and is prepared for recurring services
the contingent type, method, and reference period are defined
if the contingent is linked through SLA or billing types, the related templates and assignments exist

Functional focus

Contingent type and billing logic

Contingents can be quantity-based or amount-based. They can also be capped or uncapped. This determines whether excess consumption is billed separately once the limit is reached or whether the service scope remains fully covered by the agreed service price.

DHL Freight

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Freight-specific setup in Shipping Labels. It focuses on product constraints, package types, API access, stackability, and the package dimensions and weights that must stay within the limits of the selected DHL Freight product.

Prerequisites

The shared Shipping Labels setup is complete.
DHL Freight account number, API key, and the correct test or productive endpoint are available.
DHL Freight product settings and package types are known from the carrier onboarding.
Item attributes or fallback package data are available for the relevant shipment scenario.

Recommended sequence

Maintain or import the DHL Freight product settings.
Maintain the DHL Freight package types.
Assign account number, API key, and URL.
Choose the product, package type, stackability, and fallback dimensions and weight.
Validate the request against the selected product constraints before productive use.

Setup components

Start with the product settings, not with the final setup line

DHL Freight is strongly driven by carrier product constraints. The product settings define the allowed ranges for package dimensions, package weight, total shipment weight, volume, pieces, and loading meters.

Print Options

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Print Options control how recurring invoices and service invoices are presented in the project and contract context in Professional Services. This makes it possible to align batch invoices and related document output with the business structure of a project or customer scenario.

Prerequisites

projects and contract-related billing processes are set up
the desired grouping or presentation of invoice documents is defined from a business perspective
if needed, project-specific defaults are already maintained

Functional focus

Print options on the project

For recurring invoices and service invoices, print options can be maintained directly on the project. These settings provide the default logic for later invoice documents and create a consistent output across multiple transactions.

Assigned Location

Mon, 01 Jan 0001 00:00:00 +0000

In general, returns are posted back to the store location of the cash register. It is possible to post the inventory change to a different location. This is available for the posting of sales and returns.

Click to enlarge

Setup

Filter

Click to enlarge

This defines for which cash register process the settings should be made.

Return Reason

Click to enlarge

If return reasons are captured at the cash register during returns, this setup is checked when determining the location for the item journal line. If a result is determined from the assigned locations, posting is made to the stored target location. The most specific setup (with location and cash register specified) is always used first. If a target location applies to the entire store, the cash register entry can be omitted. It is also possible to specify a target location for the return reason without specifying location and cash register, as well as a general complaint location without specifying the return reason and without cash register details. If this setup is not used, the default location from the return reason is used.

Automation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Intercompany exchange ideally runs without manual intervention: the receiving company accepts incoming documents automatically and processes them further. This page describes how BE-terna Intercompany keeps automatic acceptance stable even when individual tasks fail.

Business value

More stable automatic operation, because transient errors do not require manual rework.
A clear upper bound on retries prevents endless loops.
Activation and deactivation fully manage the job queue by themselves.

Focus areas

Standard behaviour

When an IC document is sent from company to company, the receiving company – with automatic acceptance enabled – creates a task in the job queue. If acceptance fails, the task stays in state Error and is not processed further without intervention.

Cash Account Book

Mon, 01 Jan 0001 00:00:00 +0000

If you are in sales mode, the Cash Account Book functionality is available under Receipt Type.

Click to enlarge

Deposit

Use the Deposit button to post cash amounts into the POS.

Click to enlarge

First, enter the reason for the deposit. This can be done using the code, the configured shortcut buttons, or the magnifying glass button.

Click to enlarge

Contact Creation and Update

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to validate imported webshop contacts, create contacts in Business Central, and apply controlled updates to existing contacts.

Prerequisites

Number series for webshop contacts is configured.
Contact changes are approved per channel.
Customer templates and mandatory transfer fields are defined.

Recommended Sequence

Validate imported contact records for completeness and consistency.
Correct issues in setup, mappings, and mandatory fields.
Execute contact creation or update and document the result.

Configuration Building Blocks

Contact Validation Before Processing

Validate salutations, contact numbers, and mapping keys against valid BC values.
Distinguish new and existing customers unambiguously based on contact-number logic.

Transfer into Business Central

Run contact creation and updates only after successful validation.
Document outcomes, errors, and rework actions in a traceable way.

Process Contact Processing Guardrails Rules for consistent and safe contact transfer. +

Do not force automated transfer when salutations or number series are invalid.
For existing contacts, ensure an unambiguous mapping to the existing contact number.
Validate template and channel rule changes in test runs before production use.

Demoscopic Results

Mon, 01 Jan 0001 00:00:00 +0000

The demoscopic results can be viewed here.

Click to enlarge

Field	Description
Location	Location of the cash register
Cash Register	Cash register
POS Process	Number of the POS process
Receipt Number	Number of the receipt
Question Code	Code of the demoscopic query
Answer Code	Code of the answer
Answer Description	Description of the answer
Date	Date of the answer
Time	Time of the answer

DHL Shipping

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Shipping setup in Shipping Labels. It covers domestic parcel scenarios, return labels, SOAP and REST credentials, participation numbers, print format, detailed request properties, and optional international return handling.

Prerequisites

The shared Shipping Labels setup is complete.
The required DHL Shipping credentials and URLs are available for the target environment.
Country data contains the required ISO Alpha-3 values for REST-based scenarios.
Default sender contact data and package data are available.

Recommended sequence

Decide whether the rollout should start directly with REST credentials.
Maintain the required URL entries for test or productive use.
Maintain credentials, participation number, default sender email, and print format.
Configure request properties such as return labels, validation, insurance, and notification behavior.
Add international return settings only for locations and products that actually support them.

Setup components

Prefer REST credentials and keep SOAP only for compatibility

DHL Shipping currently spans older SOAP-based values and newer REST-based access. For public guidance, the safest rule is to prefer REST credentials from the beginning whenever the carrier account supports them.

Dispatch control

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Dispatch control helps you bundle due document lines and move them into shipping, picking, or posting flows in a controlled way.

Standard BC setup context

Dispatch control always runs against a standard location setup. The relevant question is whether the location requires shipment, picking, or both:

No warehouse requirement: standard posting without warehouse documents.
Shipment required: dispatch control creates or fills the warehouse shipment step.
Picking required: dispatch control creates pick documents.
Shipment and pick required: both steps are processed in sequence.

For sales control, the relevant actions are Create Document, Create Document And Pick, Create Pick, Post Document, and Add to Whse. Shipment. For transfer control, the equivalent transfer actions are Create Whse. Shipment, Create Whse. Shipment and Pick, Create Whse. Pick, Add to Whse. Shipment, and Post Document.

Error log

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The error log is the central place for failing IC processing. Every aborted transaction leaves an entry with timestamp, transaction reference, and error text.

Access in Business Central

Open the error log from the role center or via search.

Prerequisites

Permission to read IC error log entries.
Access to the source and target documents to remediate.

Activities

Read error messages and identify category and root cause.
Clean up the affected transaction and restart it.
Mark entries as handled or document why they remain deliberately.

Fields and actions

Field	Content
Date/Time	Time of the abort.
Source	Affected IC transaction or job queue entry.
Error text	Business Central error message.
User	Running user or job queue system user.

Monitoring and troubleshooting

Recurring error texts hint at a setup or data problem, not at single events.
Always clarify the cause before a mass retry; otherwise retries create new entries.

Best practices

Walk through the error log at least daily.
Fix recurring error types in partner or master-data maintenance.

Export internal SKR03

Mon, 01 Jan 0001 00:00:00 +0000

The “Export internal SKR03” action can be used to export and download the initial data of BE-terna Project in a zip file.

Click to enlarge

Export Sales Order History

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns history entries for webshop orders including line references.

Method

Operation: OrderHistoryExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameters

changedSince_P
orderNo_P

Response

XML in orderHistoryExport_PX with history headers and line details.

Result

The webshop can track processing history per order and per line.

Image Reference

Mon, 01 Jan 0001 00:00:00 +0000

Images for receipt printing can be stored under Setup → Image Reference.

Click to enlarge

Actions

Upload

This action can be used to assign a local image resource to the current record.

Click to enlarge

After a successful selection, the image is uploaded to the database and can then be referenced via the assigned code (for example in the receipt texts).

Click to enlarge

Setup

Field	Description
Code	The unique reference code (cannot be changed later because it is stored as a reference in the metadata of the receipt documents)
Description	Image description, for example Logo or Advertising
Uploaded	Indicates whether an image has been uploaded

Import

Mon, 01 Jan 0001 00:00:00 +0000

Import is available for posting financial accounting, items, and resources, provided that the POS store setup is configured to import the data.

Click to enlarge

Sales Data

All sales data is available in the following table if it has not yet been imported and has therefore already been archived.

Click to enlarge

Importieren creates the corresponding journals.

Via Bon, you can navigate to the respective receipt.

Via the Zeilennummer, you can navigate to the import and correct the data in case of error messages.

Import Sales Order

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint imports webshop order data into the Business Central import container.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Import/v2.0/companies(<company-system-id>)/orders?$filter=webshopChannelCode eq '<webshop-channel-code>'

Required Parameters

webshopChannelCode filter
JSON payload with order header and at least one orderLines entry

Payload Core Areas

Order header: channel, order ID, date, totals, currency, customer and contact references
Addresses: sell-to, bill-to, and ship-to
Payment and shipping information
Line data (orderLines) including type, item, price, quantity, and optional metadata

Processing Note

The API call primarily performs syntactic import into the container.
Semantic validation and document creation run in downstream processing.

Result

The order is available as an imported record for further BC processing.

Job queue

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The job queue is the engine for automated file exchange. This page describes the one-time setup for automatic file import and background dispatch. Ongoing operation (monitoring, retry, error analysis) is covered on the Job queue page in the administration module.

Click to enlarge

Prerequisites

Job queues are enabled in Business Central.
The job queue service account has access to the exchange directory (server share or Azure File Share).
Automatic file import is enabled in the intercompany setup.
For automatic acceptance the corresponding option is set in the intercompany setup.

Recommended order

Enable automatic file import in the intercompany setup.
Verify that the job queue entry for file import has been created automatically.
If desired: enable automatic retry of acceptance, set the maximum number of attempts.
Store credentials and path to the exchange directory in the setup.

Setup building blocks

Job queue entry for file import

Enabling automatic file import creates a recurring job queue entry automatically. It reads files from the configured directory and creates incoming transactions in the inbox.

Maintenance Setup

Mon, 01 Jan 0001 00:00:00 +0000

General

Click to enlarge

Field	Explanation
Auftragsnummernserie	Number series code for new maintenance orders.
Reparaturnummernserie	Number series code for repair orders.
Objektnummernserie	Number series code for new objects (for example, a customer company or building).
Anlagennummernserie	Number series code for a specific installation within an object.
Standortnummernserie	Number series code for an installation location. A location is treated as a subunit of an object.
Verwende BE-terna Project Beleg	Defines that BE-terna Project documents are used for invoicing when maintenance or repair orders are created.
gesperrte Debitoren Kategorie	Color used to mark blocked debtors for objects, installations, and orders.
Komponenten und Aufträge für Gruppierungsanlagen zulassen	If enabled, installation hierarchies can be created and one combined order can be created for grouped, hierarchically related installations.
Wartungsart Nur Rechnung	Enables the maintenance type “Invoice only”. In this mode, recurring invoicing runs without creating a separate order document.

Project Assignment

Field	Explanation
Projektnr. Wartung	Defines the default project for new maintenance orders.
Projektnr. Reparatur	Defines the default project for new repair projects.
Manuelle Projektwahl Wartung	If enabled, users must manually select a project when creating a maintenance order.
Manuelle Projektwahl Reparatur	If enabled, users must manually select a project when creating a repair order.

Document type

Field	Explanation
Grundbelegart Auftrag	Defines the base document type for a new maintenance order (selectable from a dropdown).
Dokument Typ Auftrag	Defines the document type associated with the order base document type.
Grundbelegart Abschluss	Defines the base document type used when closing a maintenance order.
Dokument Typ Abschluss	Defines the document type associated with the closing base document type.
Grundbelegart - Vertrag	Defines the base document type for a new contract.
Dokument Typ - Vertrag	Defines the document type associated with the contract base document type.
Standard Vertrags Wart. Artencode	Defines the default contract maintenance code used when a contract is created from an installation. For “GROSS”, the default interval is 12 months; for “KLEIN”, 6 months. Additional contract types can be added and existing ones can be edited.

Rotation management

Click to enlarge

Production Order Management

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes production order management in BE-terna Manufacturing. It explains how orders are created with meaningful defaults, reviewed before release and finish, reported through workers and journals, enriched with item tracking, and corrected or reopened in a controlled way when necessary.

Business Value

Transfers key defaults such as assigned user, posting group, and location automatically into new production orders.
Provides dedicated overview pages for release status and readiness to finish.
Supports workers with a dedicated time registration role center, authentication, and filtered order visibility.
Controls item tracking and automatic quantity calculation directly in the production order and output journal context.
Automatically proposes the matching application entry for negative correction postings.
Allows finished production orders to be reopened for required follow-up postings.

Area: Production Order Management

Create production orders with standard defaults

New production orders can be created manually, from sales orders, from planning suggestions, or from order planning. When the related switches are enabled in Manufacturing Setup, the system automatically transfers Assigned User ID, Gen. Bus. Posting Group, and Location Code into the order.

Reference Processes

Mon, 01 Jan 0001 00:00:00 +0000

This page consolidates the main reference processes for Connector Commerce Interface to Fashion. The focus is on setup, import, processing, and export together with fashion-specific master data.

Process WSE – Webshop Setup Channel, languages, countries, colors, and HTTP connection are set up for the connected shop. +

A dedicated channel with the required control data is created per webshop.
Countries, languages, and validation options are maintained per channel.
Colors and supplier colors are prepared so they can later be transferred to items and variants.

Process JQE – Job Queue Setup Recurring validation and processing runs are scheduled for import, release, and export. +

Background processing ensures that import and release steps run regularly.
Faulty records remain traceable and can be processed again after correction.

Process IBC – Import BE-Commerce Contacts, sales orders, and reservations are transferred from the shop into Business Central container and target structures. +

The shop provides documents and master data changes through web services.
Processing validates the data and creates target documents only after successful validation.

Process PBC – Process BE-Commerce Imported data is validated, corrected, released, and moved into the operational flow. +

Release logic evaluates mandatory fields, categorization, language-dependent descriptions, and price availability.
Error lists support follow-up actions before documents or item releases are checked again.

Process EBC – Export BE-Commerce Changes to items, prices, inventory, and other shop-relevant data are made available to the shop. +

Change logs control which data is exported or signaled through HTTP calls.
The shop retrieves the provided data through the defined export interfaces.

Salesperson Report

Mon, 01 Jan 0001 00:00:00 +0000

The salesperson report is used to obtain an A4 printout of the filtered sales data grouped by salesperson. The totals for the number of receipts, sales, and revenues are displayed.

Click to enlarge

Service

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The service functions of Professional Services connect ticketing, work orders, recurring tasks, and service billing. This makes it possible not only to organize operational work, but also to turn it into structured, billable processes.

Business value

tickets, work orders, and recurring tasks are managed in one shared service model
external ticketing systems can be connected through the API
completed work can be transferred into project planning lines and billable service transactions

Functional focus

Ticketing

Tickets can be created manually in Professional Services or transferred from external systems through an interface. The ticket stores effort, responsibility, status, and billing-relevant information.

Work Tasks and Work Packages

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Work tasks and work packages provide the planning foundation for recurring service delivery. They help define recurring activities, bundle them into reusable structures, and trigger tickets or work orders at the right time.

Prerequisites

recurring activities, intervals, and responsible roles are defined from a business perspective
required references to properties, customers, projects, or contracts are available
it is clear whether tasks should create tickets, work orders, or grouped operational transactions

Functional focus

Define work tasks

Work tasks describe individual recurring activities with a validity period, property context, and business assignments. They also define whether execution should generate a ticket or a work order.

Ticketing System

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The ticketing system is used to capture customer requests, issues, and service cases in a structured way, process them, and turn them into billable services. Tickets can originate manually, from work packages, or through an API from external systems.

Business value

tickets can be assigned to customer, project, sales contract, SLA, and property-related objects
ticket lines capture the actual services delivered
completed tickets can be transferred into project planning lines and service billing

Functional focus

Create and assign tickets

A ticket is assigned to a customer and usually to a project. In addition, responsibility, priority, status, sales contract, contingent, SLA, and property-related data such as object, installation, or component can be maintained.

DHL API Assistant – MCP Integration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to integrate the DHL API Assistant MCP Server into an AI-enabled development environment. The integration allows supported AI tools and IDEs to access DHL API-specific capabilities through the Model Context Protocol (MCP).

The DHL API Assistant helps developers create request examples, analyze API errors, understand required fields, and test DHL API workflows in the sandbox environment. The integration is limited to the sandbox environment. For production use, the official DHL API documentation is authoritative.

Work Orders

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Work Orders are the operational bridge between tickets, planning, service capture, and billing in Professional Services. They support manual field service scenarios as well as processes created from tickets, properties, or recurring tasks.

Prerequisites

required order types, number series, and base parameters are configured
customer, project, and if needed sales contract, SLA, or contingent are available
if resources are planned, responsibilities, qualifications, and target dates are defined

Functional focus

Creation and dispatch planning

Work orders can be created manually, from a ticket, or directly from property-related master data. The document header stores order type, status, planning details, responsibility, and contract references. This makes the document both the planning object and the operational control point for the service case.

Service Billing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Service Billing groups tickets and work orders into one shared billing run. This allows multiple service cases to be collected, turned into invoices, and then reviewed, printed, or posted in a controlled way.

Prerequisites

Tickets or work orders with billable service lines exist.
Project, contract, and billing references are maintained in the underlying documents.
If contingents are used, they are assigned correctly to the relevant ticket or contract.

Functional focus

Billing period and selection

Service Billing does not rely on fixed periods. Instead, you define a flexible start date and end date for the billing interval. Based on this range, the system identifies billable cases and transfers them into the billing lines.

DPD

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DPD-specific setup in Shipping Labels. The DPD setup is comparatively compact and focuses on service type, credentials, URL assignment, and the package limits that the request must respect.

Prerequisites

The shared Shipping Labels setup is complete.
DPD credentials and the correct test or productive URL are available.
The intended DPD service is known.
Item or fallback package weight is available for the request scenario.

Recommended sequence

Assign the DPD shipping agent service in the shared setup.
Maintain username, password, and URL.
Select the DPD service and maintain package limits.
Validate one realistic request with complete package data.

Setup components

Maintain credentials and environment URL

DPD requires a straightforward credential setup with the correct environment URL. Keep test and productive values separate and validate each environment independently.

Property-Based Service Operations

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Property-based service operations connect operational service cases with objects, installations, and components. This makes it possible to assign tickets, work orders, contracts, and recurring tasks not only to a customer, but also to the concrete installed base.

Prerequisites

objects, installations, and components exist as master data or are defined as part of the target model
required number series, attributes, and hierarchy assignments are configured
customer, project, and if needed contract references are available for later service processing

Functional focus

Master-data model for objects, installations, and components

Professional Services can model customer environments flexibly through objects, installations, and components. These elements can be linked hierarchically and further classified through attributes, serial numbers, activation dates, or manufacturer information.

Objects

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Objects are the top property-related structure level in Professional Services. They provide the business container in which installations, components, attributes, and related service processes are grouped so services can be connected to a concrete customer context.

Prerequisites

the basic object structure and its business hierarchy are defined
customer reference, address reference, and required attributes are available
if installations or components should be assigned, those master-data elements are prepared

Functional focus

Object card and customer reference

The object card stores the object number, description, and customer assignment. This allows an object to be described from a business perspective and linked directly to a customer or delivery address.

Installations

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Installations are the technical middle layer between objects and components in Professional Services. They show which installed units are active at a customer site, which components belong to them, and from which concrete installed-base element service processes are handled.

Prerequisites

the related object exists or is defined as part of the target model
installation types, required number series, and relevant serial or lot information are prepared
if service processes should be started directly from the installation, work-order and service processes are configured

Functional focus

Installation card and business assignment

The installation stores information such as installation type, object number, description, and activation or deactivation dates. Serial number and lot number can also be maintained so the installed unit can be identified clearly and tracked across its lifecycle.

Components

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Components describe the individual technical elements inside an object or installation in Professional Services. They help structure the installed base in detail and connect service, contract, and billing processes precisely to concrete installed elements.

Prerequisites

related objects and, where needed, installations exist
component types, calculation types, and relevant item or resource assignments are aligned from a business perspective
if service or contract references should be used, the related master data and processes are configured

Functional focus

Master data and technical classification

The component stores object and installation references, description, component type, calculation type, and sales-related references. In addition, installation and activation dates, quantities, units, serial or lot numbers, version numbers, and manufacturer information can be maintained.

Cash Register Closing

Mon, 01 Jan 0001 00:00:00 +0000

To perform a POS closing, you must first be on an empty receipt and then initiate it via Receipt Type -> POS Closing.

Click to enlarge

If the following prompt is confirmed with Yes, the process for carrying out a closing is started.

Click to enlarge

Cash Revenue Registration

After that, based on the corresponding setting in the POS setup, there are initially two ways to enter the cash revenue: either as a denomination or as a total amount.

Change Log

Mon, 01 Jan 0001 00:00:00 +0000

Zweck

The change log records relevant changes to master and transactional data for the commerce area. It serves as the basis for synchronization between Business Central and the webshop.

Was erfasst wird

Item master data
Price changes
Inventory changes
Webshop categories
Free-text attributes
Dynamic attributes
Locations and document data

Struktur

Entry number
Processed
Skip
Latest request successful
Created at
Name and code
Webshop channel code
Number of HTTP requests
Last send date and time
Latest response
Parameters 1 to 3

Fachlicher Nutzen

Traceability of changes for webshop synchronization.
Control over which data is sent to the shop.
Prevention of duplicate transmissions through existing entries.

Ergebnis

A controlled data stream for changes in the commerce context.
A traceable list for technical and business follow-up.

Consignment process

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the implemented consignment process in Controlled Sales Core from an end-user perspective. The focus is shipment handling, transport creation, and process-type behavior.

Business context

At consignment locations, documents are still processed operationally like sales flows, but transport logic classifies them as transfer-oriented where required. This preserves the logistics view of replenishment and transfer-like movement.

Clear split of process roles

Process role	Sales control	Transfer control
Trigger	Customer demand and delivery call-off	Replenishment need at consignment location
Primary function	Start operational shipment and pick process	Execute transfer order for location replenishment
Target documents	Sales-related shipment/pick documents	Transfer-related shipment/pick documents
Business focus	Deliver customer demand on time	Keep location stock availability stable

Required setup for consignment

For a stable process, these setup elements should be maintained consistently:

Custom file formats

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

When data exchange with an IC partner uses files – transfer types File location, E-mail, or File location (server) – custom formats can be used. File import and export go through an interface; custom implementations can be picked per partner card.

Business value

Connect partners that do not use the standard format without changing the core process.
The exchange format can be defined per partner.
Extensions can provide external XML or EDI variants without product modifications.

Focus areas

Selection on the partner card

The Import/Export field on the IC partner card picks the implementation. If a custom variant is configured for the partner, it is used automatically on sending and receiving.

DSV

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DSV-specific setup in Shipping Labels. It covers residential delivery handling, pickup windows, fallback package data, notification options, and the multiple credential sets needed for shipping and tracking-related services.

Prerequisites

The shared Shipping Labels setup is complete.
DSV shipping credentials, tracking-related credentials, and the correct environment URLs are available.
Sender and recipient contact data are maintained in the required format.
The required notification scenario is known.

Recommended sequence

Maintain shipping credentials and URL assignment.
Maintain pickup window and residential-delivery behavior.
Maintain notification settings and the related tracking credentials.
Verify phone and email data in a realistic test request.

Setup components

Start with the DSV credential model

DSV setup can include several technical values, for example account number, x-pat, Subscription-Key, Service-Auth, and additional tracking-oriented values for notification scenarios. Keep these values grouped by service purpose so that shipping requests and notification flows are not mixed accidentally.

Export Inventory

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns inventory values for items and variants.

Method

Operation: InventoryExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameters

changedSince_P
itemNo_P
incremental_P

Response

XML in inventoryExport_PX with items, variants, and stock values.

Result

The webshop receives inventory for availability and synchronization.

General

Mon, 01 Jan 0001 00:00:00 +0000

Most of the facilities in the General tab are part of the Business Central Standard module. The following describes the facilities that belong to BE-terna Project.

Click to enlarge

In the list of share type origin codes, price shares are provided with the corresponding origin codes. This can be used in accounting for account determination and related evaluation.

Click to enlarge

Project Journal Templates

A journal in Business Central causes data to be permanently stored in an entry. It is therefore a manual template for posting data. When you post the journal, the information is transferred to accounts in ledger entries and cannot be changed.

Import Contact

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint imports contact data from the webshop into the Business Central contact import container.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Import/v2.0/companies(<company-system-id>)/webshopContacts

Required Parameters

webshopChannel in the payload
JSON body with contact header data

Payload Core Areas

Contact header: channel, contact number, name, address, language, country, communication data
Optional additional fields such as salutation, first/last name, and company name
Contact lines (webshopcontactLines) for ship-to specific information

Response Behavior

The API returns the imported record as JSON.
With $expand=webshopcontactLines, the response can include contact line data.

Result

The webshop contact is available for downstream processing in BC.

Job queue

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The job queue carries automatic IC document processing. This page describes daily operations: monitoring, start/stop, error analysis, and retry strategy. Initial configuration is documented on the Job queue setup page.

Access in Business Central

Reach job queue entries from the role center or via the Job Queue Entries search.

Prerequisites

Job queue is configured (see setup page).
User has rights to start/stop entries.

Activities

Check the state of IC entries (Ready, In Process, Error).
Restart failing entries in a targeted way.
Adjust schedules when load changes.

Fields and actions

Action	Effect
Set to Ready	Restarts an entry, for example after an error.
Put on Hold	Temporarily stops cyclic execution.
Show error	Opens the last error message.
Max. no. of attempts	Limits automatic retry.

Monitoring and troubleshooting

Fix Error entries with a speaking message first before retrying.
Long-running In Process states hint at stuck sessions – put the entry on hold and restart it.
Automatic retry through the intercompany setup (see Automation) reduces manual work.

Best practices

Always set a max. number of attempts – unlimited is rarely useful.
Choose cycle frequency as high as necessary, not higher.

Purchasing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

In the purchasing area, Professional Services supports the management of purchase contracts and their business assignment to customer and sales-contract scenarios. This keeps vendor, customer, and recurring-service relationships visible in one shared view.

Business value

purchase contracts can be maintained with vendor, validity period, and optional customer assignment
sales contracts can be linked to purchase contracts for transparency
purchasing-related scenarios can be connected to contract-based and service-based processes

Functional focus

Purchase contracts

Purchase contracts define the contractual framework with vendors. The header typically contains the vendor, the validity period, and, where needed, the related customer.

Receipt Layout

Mon, 01 Jan 0001 00:00:00 +0000

The layout of each individual receipt type can be adjusted under Setup → Receipt Layout.

Click to enlarge

Actions

The following actions are available in the header of the receipt layout setup:

Action	Description
Reset	Resets the currently selected receipt layout.
Reset All	Resets all receipt layouts.

Setup

In the Type field, select the receipt type whose layout is to be adjusted. Afterwards, the lines of the selected receipt layout can be changed by direct input or via AssistEdit.

Sales Order Creation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how imported order data is processed into a sales order in the system. It covers both the successful path and the rework path for faulty imports.

Prerequisites

The webshop provides order data to Business Central.
The import process has loaded the data into the container.
The business-critical order fields are known and maintained.

Recommended Sequence

Review the imported order data.
If the content is correct, create the sales order.
Correct faulty data in the container and process it again.

Configuration Building Blocks

Successful Sales Order Creation

The order is created from the webshop data as a sales order.
The document contains traceable header information such as number and creation timestamp.

Faulty Sales Order Creation

Invalid imports are marked with an error and an error text.
Rework happens in the container under the converted data tab.
After correction, the order can be created manually.

Process Sales Order Creation Guardrails Rules for stable processing of imported sales orders. +

Always validate imported data before creating the document.
Fix issues in the container instead of on the downstream document.
Use manual rework only for approved business exceptions.

Store Manager Entry

Mon, 01 Jan 0001 00:00:00 +0000

The Store Manager Entry page provides an overview of the changes made to the setup for cash register setups and distributed to the cash register setup through store administration.

Click to enlarge

All changes can be reversed via Reset.

Click to enlarge

Technical Connection

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the technical connection between Business Central and the connected shop in the context of Connector Commerce Interface to Fashion.

Technical Structure

Web Services for Master Data and Transaction Data

Data exchange is based on provided web services. The shop supplies sales orders, returns, reservations, and contact changes in container structures. After successful validation, the target documents are created in Business Central.

HTTP Calls for Change Control

Changes to items, contacts, prices, inventory, categories, and attributes are stored in a change log. Configurable HTTP calls notify the shop that updated data is available for retrieval.

Time Tracking Users

Mon, 01 Jan 0001 00:00:00 +0000

The time tracking user setup can be accessed via the search function of Business Central. Here, users can be linked to resources and structured in Teams via Time Tracking User Assignment. There, the team lead is entered in the Resource No. column and the team members belonging to the team are entered in the Assigned Resource No. column.

Click to enlarge

VAT

Mon, 01 Jan 0001 00:00:00 +0000

Under Assignment → VAT, posting group mappings can be defined after, or for temporary, VAT changes.

Click to enlarge

This assignment is required for item returns that were sold before the relevant VAT change.

For manual returns, the system first uses the current posting groups to determine whether a mapping exists for them. If so, a selection must be made to specify whether the return takes place inside or outside the stated period. Inside the period, the currently valid VAT and the current posting groups are used; outside the period, the stored Ret. VAT % together with the stored Ret. posting groups are used.

Purchase Contract

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Purchase Contracts provide the contractual framework toward vendors in Professional Services. They combine the vendor, duration, project and customer reference, and the concrete contract lines, creating a reliable basis for recurring or planned purchasing scenarios.

Prerequisites

a vendor with the relevant contact and payment information exists
project reference and, if needed, customer reference are clarified
duration, cancellation logic, and the services or items to be procured are defined

Functional focus

Contract header and master-data linkage

The purchase contract stores the contract type, vendor, contact, start and end date, and project or customer reference. This makes the contract not just a purchasing document, but a structured frame for later procurement and assignment processes.

FedEx

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the FedEx-specific setup in Shipping Labels. It focuses on product selection, label format, customs-relevant fields, direct API credentials, and the fallback package data needed for national and international scenarios.

Prerequisites

The shared Shipping Labels setup is complete.
FedEx account number, API key, secret key, and the correct environment URL are available.
The FedEx product list is known.
Customs-relevant values such as currency and country of manufacture are available where needed.

Recommended sequence

Maintain the FedEx product list.
Assign account number, API key, secret key, and URL.
Choose product and label format.
Maintain customs-relevant properties and fallback weight.
Validate one national and, if relevant, one international scenario.

Setup components

Start with the product list

FedEx setup uses a product catalog that distinguishes between national and international shipping scenarios. Maintain the product code and name exactly as agreed with the carrier.

Azure File Share

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

BE-terna Intercompany supports file exchange between IC partners via an Azure File Share. This page describes daily administration of that exchange – the underlying permissions are maintained in the Azure portal.

Access in Business Central

Azure File Share settings are visible on the IC partner card in the transfer-type section.

Click to enlarge

Prerequisites

Azure storage account with a file share; access is granted through a SAS token (never through persistent account keys inside BC).
Partners use the same file-share path for the bilateral exchange.
Transfer type File location is active on the IC partner card.

Activities

Monitor SAS token validity and renew it in time.
Keep the share permissions in Azure as narrow as possible.
On issues: check network access and target folder before touching the IC setup.

Fields and actions

Field	Purpose
File share path	Source or target folder of the exchange.
Access token	Time-limited SAS token.
Checksum	Optional: validates exchanged files.

Monitoring and troubleshooting

File not found almost always points to an expired token or a changed path.
Connection issues create entries in the Error log.
The job queue for automatic import only works if the IC partner folder exists.

Best practices

Issue SAS tokens with the shortest reasonable validity and minimal rights.
Separate folders per partner to prevent data mixing.

Demoscopic Query

Mon, 01 Jan 0001 00:00:00 +0000

This page controls on which cash register demoscopic queries may be used. Queries can be blocked for individual cash registers or locations.

Click to enlarge

Field	Description
Location	Selection of the location (optional) - blank = all
Cash Register	Selection of the cash register (optional) - blank = all
Code	Selection of the query
Excluded	Blocks the query for all cash registers found under Location + Cash Register. (optional)

Export Document Status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns document creation status including error text.

Method

Operation: DocumentStatusExport
Service: Codeunit BEConnect as SOAP web service

Required Parameters

webshopChannel_P
OrderType_P
OrderNo_P

Response

return_value with success or failure status
errortext_P in error cases

Result

Integrations can verify whether posting succeeded.

Export Item List

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns the item list for a webshop channel, including send-state and change timestamp.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/itemsList?$filter=webshopChannelCode eq '<webshop-channel-code>' and sentToWebshop eq <true|false> and changedForWebshopAt eq <datetime>

Required Parameter

webshopChannelCode in filter

Optional Filters

sentToWebshop
changedForWebshopAt

Key Response Fields

systemId, itemNo, webshopChannelCode, changedForWebshopAt, sentToWebshop

Result

The webshop receives item list records for delta or full synchronization.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ When do you need the connector in addition to BE-Commerce? The connector is needed when a fashion webshop uses additional colors, attributes, variant logic, or channel-specific fashion master data. +

Use the connector when the general BE-Commerce standard must be extended with fashion-specific requirements. Typical examples are webshop colors, supplier colors, attribute-based variant presentation, or fashion-specific categorization.

If you want to understand the base module first, start with BE-Commerce Overview. Then continue with the connector-specific pages such as Setup and Master Data for Fashion.

Fiscal Transaction

Mon, 01 Jan 0001 00:00:00 +0000

In the Archive for Fiscal Transactions, metadata is stored for each transaction so that communication with the respective interface can be traced.

Click to enlarge

Field	Description
Location	Location code
Cash Register	Cash register code
Serial No.	Consecutive serial number
Provider	Fiscal provider
Module	Fiscal module
Receipt Location	Receipt location code
Receipt Cash Register	Receipt cash register code
POS Process	POS process
Receipt No.	Receipt number
Document Type	Type of receipt
Slip Type	Type of slip
Transferred	Indicates that the transaction was transferred
Processed	Indicates that the transaction was processed
Operations Log	Number of operations log entries
Result Code	Shows the number of error messages and events
Error Message	Shows the error message
Contains Warnings	Indicates that the transaction contains warnings
Request Date	Date of the request
Request Time	Time of the request
Response Date	Date of the response
Response Time	Time of the response
Cash Register Setup Initialized	Indicates whether the cash register setup has already been initialized for fiscalization
Request URI	Request address
HTTP Status Code	HTTP status code
HTTP Status Description	HTTP status code name

Operations Log

For an entry with a result code, it must be documented what triggered this entry and when and how the error was resolved.

GLS

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the GLS-specific setup in Shipping Labels. The main topics are service type selection, delivery-time promise, credentials, URL assignment, and the parcel-size limits that belong to the chosen GLS scenario.

Prerequisites

The shared Shipping Labels setup is complete.
GLS credentials and the correct test or productive endpoint are available.
The business scenario is clear about whether a standard parcel or an express scenario is required.
Item or fallback package weight is available.

Recommended sequence

Assign GLS credentials and URL.
Choose the service type.
Maintain express delivery time if the express service is used.
Maintain parcel limits and fallback package weight.
Validate one realistic request with the chosen service type.

Setup components

Start with the GLS service decision

The key business decision in GLS is whether the setup represents a regular parcel flow or an express flow. If Express is chosen, the delivery-time commitment becomes part of the setup. If Parcel is chosen, that additional time promise is not required in the same way.

Import BE-terna Project

Mon, 01 Jan 0001 00:00:00 +0000

The following areas are available in the BE-terna Project import function setup: Import Wizard, Migration Addresses, Migration Project Documents, Migration Maintenance, and Transfer of AZ Open Projects.

Click to enlarge

Import Wizard

The Import Assistant is intended for the import of migration data from old ERP systems from BE-terna’s craft sector.

Click to enlarge

Migration Addresses

Extended functions of the Import Assistant for the manual import of migration data from old ERP systems from BE-terna’s trade sector can be found here. This area is for customers, vendors, and contacts.

Print

Mon, 01 Jan 0001 00:00:00 +0000

In the “Print” area of the BE-terna Project setup, parameters for document forms, print preferences and Excel templates can be set.

Click to enlarge

Document forms

In the Document Forms Overview, individual forms are defined and the corresponding data is transferred to the print layout of a document.

Click to enlarge

Print Presets

In the print preferences, parameters can be defined that determine the behavior of a document during printing. These settings can be changed later when printing. At this point, only the default settings are defined.

Purchasing and Subcontracting

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how BE-terna Manufacturing extends the purchasing area in Business Central with subcontracting processes. It covers the modeling of subcontracting through work center groups and routings, the creation of linked purchase orders, pricing for subcontracted operations, and the connection to transfer and receipt processes.

Business Value

Makes the relationship between production order, subcontracting suggestion, purchase order, and purchase receipt transparent.
Transfers item description fields into subcontracting purchase lines when needed.
Supports subcontracting prices with quantity tiers, currencies, and validity periods.
Connects purchase orders and transfer orders for component supply to the subcontractor.
Enables the use of standard warehouse receipt and put-away processes for suitable return scenarios.

Area: Purchasing

Content Focus

The functions described here belong to the purchasing area in Business Central because they extend purchase orders, vendors, pricing, and transfer references for collaboration with subcontractors.

Receipt Text

Mon, 01 Jan 0001 00:00:00 +0000

Receipt texts can be configured under Setup → Receipt Text.

Click to enlarge

Actions

The following actions are available on the respective receipt text card:

Action	Description
Receipt Test	Sends the currently selected receipt text as a test receipt to the stored receipt printer.
Device Setup	Opens the device setup overview.

Setup

Field	Description
Location	Location code
Cash Register	Cash register code
Type	Defines the receipt text type
Start Date	Specifies the date from which the text line should be printed
End Date	Specifies the date until which the text line should be printed

Types

In the header lines, for example, the address and contact data of the respective branch can be specified.

Sales Return Order Creation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how sales return orders are created in Business Central from imported webshop return data. The processing follows the same basic pattern as sales orders.

Prerequisites

The webshop sends return data to Business Central.
The import has loaded the data into the container.
The channel-specific return rules are known.

Recommended Sequence

Review the imported return data.
Correct errors in the container.
Create the sales return order manually or automatically.

Configuration Building Blocks

Processing Imported Returns

Returns are first loaded into a container.
Business Central performs the content check after import.
Error handling follows the same pattern as sales order processing.

Rework and Creation

Faulty data can be adjusted.
The sales return order is then created from the corrected data.

Process Return Guardrails Rules for safe processing of imported returns. +

Apply the same validation discipline to returns and orders.
Correct container data before manual document creation.
Document root causes for recurring return errors.

Transport processing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to combine posted shipment data into transport documents, validate them, and complete transport posting safely.

Standard BC setup context

A transport does not replace the shipping process. It consolidates already posted delivery documents into one operational handoff to a carrier or internal transport chain.

Transport sources in Controlled Sales Core are:

posted sales shipments
posted transfer shipments
posted warehouse shipments or shipment-derived lines
in exceptional cases, posted warehouse picks with a sales reference

Depending on the source, the transport process type is handled as Sales or Transfer. At consignment locations, a sales shipment can still be treated as transfer from a business perspective.

Hermes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the Hermes-specific setup in Shipping Labels. It focuses on parcel class, output format, ZPL handling, and the separate authentication and shipping URLs that Hermes requires for test and productive operation.

Prerequisites

The shared Shipping Labels setup is complete.
The Hermes authentication and shipping URLs are created in the shared URL setup.
The required Hermes credentials are available for the productive environment.
The business scenario is clear about parcel class and output format.

Recommended sequence

Maintain the shared URL entries for Hermes authentication and shipping access.
Maintain the Hermes credentials for the relevant environment.
Choose parcel class and output format.
If ZPL is used, maintain the required resolution.
Validate the setup with the target output format and printer scenario.

Setup components

Treat authentication URL and shipping URL separately

Hermes uses separate URL concepts for authentication and the actual shipping service. These entries should be maintained explicitly in the shared URL setup before the Hermes line itself is completed.

Demoscopic Query

Mon, 01 Jan 0001 00:00:00 +0000

Demoscopic queries are shown at the end of the receipt. It can be used to ask statistical answer options. The setup is done under Setup → Demoscopic Query.

Click New to create a new query. Enter the question code and the question text. If several queries exist, the priority can be used to control the order in which they appear. The query must be activated. This is possible only if at least one answer has been entered.

Export Dynamic Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns dynamic attributes with translations and possible values.

Method

Operation: DynamicAttributeExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

attributeCode_P

Response

XML in dynamicAttributeExport_PX with attributes, value sets, and labels.

Result

The webshop receives attribute metadata for filtering and product representation.

Export Inventory

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns inventory data for one item, including optional variant information.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/inventories?$filter=webshopChannelCode eq '<webshop-channel-code>' and itemNo eq '<item-no>'&$expand=itemVariants

Required Parameters

webshopChannelCode in filter
itemNo in filter

Key Response Fields

Header: systemId, webshopChannelCode, itemNo
Variants: code, inventory

Result

The webshop receives current inventory levels per item and variant.

Logistics

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the logistics enhancements in BE-terna Manufacturing around pending consumption postings and returned goods from subcontracting. It helps users handle posting failures caused by insufficient inventory in a controlled way and connect returned subcontracted work to the standard warehouse receipt flow.

Business Value

Handles backward-flushed components with insufficient stock as pending consumption instead of simply losing the posting intent.
Makes open residual consumption visible in the production order and therefore prevents incomplete order finishing.
Allows pending consumption to be reposted even from another location.
Supports cancellation of pending residual consumption when the root cause was resolved outside the production order itself.
Reuses standard warehouse receipt, put-away, and inventory put-away processes for suitable subcontracting return scenarios.

Area: Logistics

Content Focus

Activate pending consumption by location

Whether pending consumption is allowed is decided per Location. This is especially useful for subcontractor locations where backward-flushed component consumption is not fully controlled by your own warehouse team.

PCH

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the PCH-specific setup in Shipping Labels. It focuses on the product catalog, response language, label size, customer and client credentials, and the strict geographic scope for Switzerland and Liechtenstein.

Prerequisites

The shared Shipping Labels setup is complete.
PCH test or productive client credentials and URLs are available.
The relevant PCH products are known.
Company Information contains the sender address used for PCH requests.

Recommended sequence

Maintain or import the PCH product list.
Validate the products with the available product-check functionality.
Maintain customer number, client credentials, response language, and label size.
Test one valid scenario inside the supported country scope.

Setup components

Start with the product list and product check

PCH uses a product list that should be maintained from the carrier-provided data. Use the product-check step when it is available to validate whether the maintained products are still usable.

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This catalog summarizes the key end-to-end workflows in Controlled Sales Core. It helps users execute recurring daily tasks in a clear, reliable sequence.

Context

Delivery call-offs are typically processed against blanket sales orders.
Fine call-offs provide detailed demand and date input as an upstream process component.
Dispatch control turns operational data into actionable processing lists.
Transfer control adds location-oriented replenishment execution.
Consignment connects sales-side processing with transfer-oriented logistics interpretation.
Transport documents capture carrier handoff and final shipping information.

Prerequisites

Setup is complete and transport number series is maintained.
Blanket and/or sales documents are available in a processable status.
Warehouse and shipping responsibilities are aligned across teams.

Process map

flowchart LR
  A[Import fine call-off] --> B[Create delivery call-off]
  B --> C[Release delivery call-off]
  C --> D[Run dispatch control]
  D --> E[Run transfer control if required]
  E --> F[Apply consignment logic]
  F --> G[Post shipment or transfer]
  G --> H[Create transport]
  H --> I[Post transport]
  I --> J[Process completed]

Required depth per process page

The linked detail pages should always include at least:

References

Mon, 01 Jan 0001 00:00:00 +0000

In the BE-terna Project setup, the following areas can be set up under Related in the Documents tab: Document Types, Details, View, Configuration, Column Selection, HTML Editor Setup and Standard Long Texts.

Click to enlarge

Document Types

In the BE-terna Project setup, the document types can be called up and edited via Related and Documents. This maps the basic document types of the system in order to be able to create specific documents from a bill of quantities.

Reservation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes reservation processing in the BE-Commerce import context.

Prerequisites

The reservation import process is enabled.
Required locations and mappings are configured.
Business rules for reservation scenarios are defined.

Recommended Sequence

Validate reservation data in the container.
Correct functional and technical issues.
Execute reservation processing and verify the result.

Configuration Building Blocks

Difference from Sales Order Import

Processing is similar to sales order creation.
No sales order is created for the customer.
Reserved items are transferred from the branch to a reservation or selection warehouse.

Voucher

Mon, 01 Jan 0001 00:00:00 +0000

The Archive for Vouchers contains all vouchers generated from setup.

Click to enlarge

Field	Description
No.	Voucher code
Status	Open: voucher can be issued Issued: voucher can be redeemed Invalidated*: voucher has been invalidated
Location	Location where the voucher was sold
Cash Register	Cash register where the voucher was sold
Default Amount	Amount stored when the voucher was created
Amount	Calculated voucher amount based on the loads posted so far
Remaining Amount	Calculated remaining amount based on the redemptions posted so far
Activated in Company	Company in which the voucher was activated
Activation Time	Time of voucher activation
Expiry Date	Indicates until when the voucher can be redeemed

Actions

Load/Invalidate

Vouchers can be loaded or invalidated after issue. Entering a reason is always mandatory.

UPS

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the UPS-specific setup in Shipping Labels. It focuses on service type, return-service behavior, international shipment handling, units of measure, and the transition from older authentication fields to preferred OAuth-based access.

Prerequisites

The shared Shipping Labels setup is complete.
UPS shipping account data and the required environment URL are available.
The chosen UPS service type is known for the origin and destination corridor.
Fallback package weight is available where item weight is not maintained.

Recommended sequence

Maintain the UPS URL and the preferred authentication method.
Maintain shipper number and the required credential fields.
Select the UPS service type and return-service behavior.
If international shipping is required, maintain the international-shipment settings and description.
Validate one domestic and, if relevant, one international scenario.

Setup components

Prefer OAuth-based access when available

UPS can still contain older access-license-style fields, but the preferred direction is OAuth-based access with client ID and client secret. Keep older values only where a supported compatibility scenario still requires them.

E-Receipt

Mon, 01 Jan 0001 00:00:00 +0000

The interface is configured under Setup → E-Receipt. The Initialize All Cash Register Setups action creates all cash register setups available under Setup → Cash Register Setup.

Click to enlarge

Setup

General

Click to enlarge

Field	Description
Location	The location code of the cash register setup to be used
Cash Register	The cash register code of the cash register setup to be used
Provider	Defines the e-receipt provider Email: With email, a PDF is generated natively by the cash register software and sent to the customer by email. Anybill: Anybill is an external provider for the digital storage of receipt documents. In cooperation with this provider, the cash register or the customer receives the option to archive the documents created by the cash register digitally and access them at any time. The customer receives the link to the respective receipt via a QR code, so printing the receipt is not necessarily required
Active	Activates the interface
Digital Receipt Confirmation	Defines whether and when a prompt for creating the digital receipt is executed Always Confirm: At the end of every receipt, a prompt appears asking whether it should be digitized. Confirm for Customer: The prompt appears at the end of the receipt only if a customer is signed in on the receipt. No Confirmation: The digital receipt is created and displayed automatically at the end of the receipt. Upstream QR Code: The digital receipt is already created and displayed at the beginning of the receipt.
QR Code on Receipt Copy	If the original receipt was already generated with Anybill, this QR code can be shown again on the receipt copy

Display

Click to enlarge

Export Branch Inventory

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns available stock per branch, item, and variant.

Method

Operation: BranchInventoryExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

itemNo_P

Response

XML in branchInventoryExport_PX with variants and mapped branch quantities.

Result

The webshop can display branch-level availability.

Export Inventory Item List

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns channel-wide inventory list records including delta indicators.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/inventoriesItemsList?$filter=webshopChannelCode eq '<webshop-channel-code>'

Required Parameter

webshopChannelCode in filter

Key Response Fields

systemId, webshopChannelCode, itemNo, inventorySentToWebshop, lastStockChangeAt

Result

The webshop receives inventory synchronization records for all channel items.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ When should I use delivery call-offs instead of the standard sales process? Use delivery call-offs when customers continuously adjust required quantities and dates against blanket orders. +

Delivery call-offs are the right choice when customer schedules are dynamic and reference data must stay consistent. They support structured quantity/date updates before downstream shipment processing.

FAQ Why do expected lines not appear in dispatch control? In most cases, filter settings or due-date logic do not match current document status. +

Check dispatch control type, filter fields, filter values, and due-date calculation first. Depending on setup, already processed or non-eligible lines are intentionally excluded.

FAQ Why is cumulative received quantity important? It helps keep call-off quantities aligned in sensitive customer supply scenarios. +

If cumulative received quantity is required in setup, users can better align internal and customer-side quantity progression. This reduces mismatches and improves follow-up call-off quality.

FAQ What must be checked before posting a transport? Transport header data, handoff details, and lines must be complete and plausible. +

Verify shipping agent, carrier handoff date/time, delivery date, and included transport lines before posting. Post only when all required transport information is complete.

Import Interfaces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the available import interfaces for receiving webshop data in Business Central.

Imported Data Areas

Sales orders
Returns
Contacts
Reservations

Usage Notes

Each import interface has a field-level description with required and control fields.
In case of import errors, validate and correct container data before processing downstream documents.

Master data

Mon, 01 Jan 0001 00:00:00 +0000

The following areas are available in the BE-terna Project master data setup: Units of Measure, Non-Ferrous, Translation Heading, GAEB Price Share Assignment, BE-terna Project Images, Basic Payment Plans, and Costing Item Setup.

Click to enlarge

Units of measure

In the unit of measure setup, different versions of the units are combined with unit codes. Since different units of measure are sometimes imported into the system via the DATANORM import, this setup ensures clarity.

Shipping Label Print Connect Connector

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the setup of the Shipping Label Print Connect Connector. The connector links Shipping Labels with BE-terna Printconnect and enables direct ZPL label printing without routing through the browser’s local printer.

Prerequisites

BE-terna Printconnect is installed and configured. For details, see Printconnect – Setup.
A user account is available and registered in PrintNode.
The Shipping Label Print Connect Connector app is installed in the target environment.

Recommended Sequence

Make sure BE-terna Printconnect is fully configured.
Open the Shipping Label Setup page.
Configure the printer assignment per user and label type.

Setup Components

Open the Shipping Label Setup Page

In Business Central, open the Shipping Label Setup page.

Tool Management

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes tool management in BE-terna Manufacturing. It explains how tools and complete tools are structured in master data, assigned to operations, logged automatically during output reporting, maintained through repair orders, and posted directly through tool journals where required.

Business Value

Manages tools and complete tools with their own history and optional tool BOM structures.
Transfers tool assignments from the routing into the production order.
Logs tool usage automatically through tool ledger entries when output is reported.
Supports repair orders with fault coding, new service life values, and status updates.
Integrates tool posting and tool usage with Business Central dimension logic.

Area: Tool Management

Content Focus

Provide tools, complete tools, and the right role center

Tool management comes with a dedicated role center. From there, users can open master data and setup data for tools, complete tools, tool groups, fault codes, and supporting tables. Tools represent self-contained units, while Complete Tools combine several components into one productive configuration through a tool BOM and its versions.

Voucher Card

Mon, 01 Jan 0001 00:00:00 +0000

The Archive for the Voucher Card contains all voucher cards activated so far.

Click to enlarge

Field	Description
Card No.	Card number
Customer No.	Customer number assigned to the card
Customer Name	Name of the assigned customer
Remaining Amount	Remaining amount of the card
Invalidated	Indicates whether the card has been invalidated

Actions

Invalidate

To invalidate a voucher card, select a voucher card that has not yet been invalidated and still has a remaining amount greater than 0, then enter an invalidation reason.

Calculation

Mon, 01 Jan 0001 00:00:00 +0000

Via “Related” and “Costing”, the facilities can be called up from the calculation templates and calculation groups.

Click to enlarge

Calculation templates

In the settings for the calculation templates, existing calculation templates can be viewed, edited and added. In addition, new calculation templates can be created. Based on these templates, project documents are created and formatted. For example, fixed items can be preset for each document or standard texts can be attached for each document.

Costing and Reporting

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the most important costing and reporting functions in BE-terna Manufacturing. It helps users print production orders in a structured way, trace costs across multiple production levels, evaluate WIP, and follow the value chain through related item ledger entries in both directions.

Business Value

Structures production order output into readable reports with header, line, routing, and component information.
Analyzes expected versus actual costs across all relevant production levels.
Reduces WIP reports to the materially relevant production orders through a configurable threshold.
Supports forward and backward navigation through related item ledger entries across the value chain.
Simplifies operational and financial analysis without manually combining many separate views.

Area: Costing and Reporting

Production order printouts and job cards

With Prod. Order Printout BE and the extended Production Order Job Card, BE-terna Manufacturing provides reports with much more structure than the standard output. They include production order header data, production order lines, routing lines, and components. The job card also adds descriptions, quantities, unit codes, required times, QR information, and further line-level details.

Export Contact

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns contact master data and related ship-to addresses for webshop synchronization.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/contacts?$expand=contactsShipTo

Filters and Expands

Contact filtering is done by contact number
Ship-to addresses are provided via $expand=contactsShipTo

Key Response Fields

Contact: no, name, address, postCode, city, country, email
Ship-to: shipToCode, shipToName, shipToAddress, shipToPostCode, shipToCity

Result

The webshop receives contact data including ship-to structures.

Export Free Text Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns free text attributes including language-specific labels.

Method

Operation: FreeTextAttributeExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

freeTextAttributeCode_P

Response

XML in freeTextAttributeExport_PX with attribute code and description nodes.

Result

The webshop receives free text metadata for product content and UI labels.

Export Interfaces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the main export objects that are transferred from Business Central to the webshop.

Exported Data Areas

Item master data including variants
Webshop categories
Free-text and dynamic attributes
Cross-selling items
Inventory and prices
Contacts
Vouchers
Document history and document status
Locations and branch inventory

Usage Notes

Each export interface has a dedicated field-level interface description.
Functional changes should always be aligned with the related interface documentation.

Packaging assignment process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog shows how packaging structures are transferred from master data into operational document processes, adjusted when needed, and then registered. The focus is on standard packaging assignments, alternatives, manual changes, and the handling of lots and weights.

Context

The packaging assignment is maintained in the document that controls the relevant shipping, purchasing, or transfer process.
Standard packaging comes from the packaging structures assigned in master data or the respective document context.
Weights, tracking information, and additional document lines are carried forward during registration and posting.

Prerequisites

Setup and master data for packaging materials, packaging structures, and alternatives are maintained.
The relevant documents contain the required quantities and, where applicable, lot or expiration date information.
Users have access to the required sales, purchase, shipping, or transfer processes.

Process map

flowchart LR
  A[Open source document] --> B[Propose standard structure]
  B --> C{Standard suitable?}
  C -->|Yes| D[Review assignment]
  C -->|No| E[Apply alternative or manual adjustment]
  D --> F[Check tracking and weights]
  E --> F
  F --> G[Register package assignment]
  G --> H[Post document process]
  H --> I[Verify result and packing list]

Required depth per process page

The linked detail pages should always include at least:

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This process catalog describes the key work procedures in MDM from the perspective of responsible business users. The focus is on creating and releasing relations, handling controlled changes, steering DSR filters from a business perspective, working with substitutions, and running consistency checks.

Context

The functional baseline for these processes is described on the Setup and Master data and relation maintenance pages.
The processes target users who maintain relations, release changes, control DSR filters and substitutions, or evaluate review results.

Prerequisites

Source and target companies, routing defaults, and initial relations are configured in MDM.
The involved users have the permissions required to work with relations, DSR filters, substitutions, and consistency checks.
The business-relevant tables and rules are aligned before the process starts.

Process catalog

Process REL-01 - Create and release a relation A new relation is prepared, reviewed, and released for productive use. +

Start by selecting the business-relevant table and defining between which source and target companies the relation should apply.
Use this workflow whenever an additional business-relevant table should become a permanent part of the existing distribution and review logic.
You are working in the relation setup or relation maintenance page. There you see the table, involved companies, and the main control fields.
Add the routing rule, distribution logic, and required rule components such as dependencies, exclusions, and substitutions.
Decide whether the relation is already complete enough for productive use or whether business rules are still missing.
Review the relation with the available review function before changing the status.
Release the relation only after the structure and rules are complete.
Use release without update only if no retroactive update should be triggered for changes made while the relation was in maintenance status.
The visible result is a released relation that can be used for data transfer and review.

Process REL-02 - Change a released relation in a controlled way Released relations are reopened only when needed, adjusted, and released again. +

Reset a released relation to an editable state only when business-relevant changes are actually required.
This workflow is typical when field logic, target-company assignments, or the handling of exclusions and substitutions has changed from a business perspective.
You are in the existing relation and can see its current processing state.
Maintain the adjustments while the relation is in maintenance status so that source and target contexts remain controlled during editing.
Be aware that changes to source or target data can be restricted while the relation is not released.
Review the relation again after the update and release it once the changes are complete.
The visible result is a released relation with traceable changes.

Process REL-03 - Identify missing or related relations Support functions help complete the relation landscape in a consistent way. +

Use the missing-relations suggestion function to identify relations that are missing for business-related tables.
Use this workflow also when business teams suspect new table relationships and you first need to clarify whether a relation is actually missing.
You see a proposal list with additional possible relations.
Use related-relation suggestions when dependencies must be analyzed across several table levels.
Do not adopt suggested relations blindly; review the business value and ownership first.
Refresh field-level relation information when the technical basis for additional rules needs to be sharpened.
The visible result is a clearer decision about which additional relations are really needed.

Process DSR-01 - Maintain DSR filters and re-evaluate existing data Responsible users define exclusion rules per relation and decide how filter changes are applied to records that already exist. +

Open the distribution matrix from a released relation or directly from the central MDM start area when you need to review or adjust distribution decisions from a business perspective.
You see the records of the selected relation and the decision per target company.
From there, open the distribution filters and maintain new filters only in the context of the affected relation table.
Decide explicitly whether a filter should apply to all target companies or only to one specific target company.
After each change, review the distribution matrix to confirm that the expected records are excluded or distributed and that the decision source matches the intended business rule.
Use the function that applies DSR filters to existing data when the new filter logic should also be applied to records that already exist.
Decide consciously whether only default and automatically set decisions should be updated or whether manual decisions may also be overwritten.
Align business-critical changes with the affected teams before running a mass update so that exceptions and special cases are not removed unintentionally.
The visible result is an updated distribution matrix that shows the new decisions.

Process SUB-01 - Maintain substitutions and distribute changes Substitutions control derived target values and can be propagated to additional companies. +

Open substitutions either in the context of a relation or directly from the central substitutions page.
You see the affected fields, target values, and open changes.
Define which target values should be replaced or derived when source and target contexts differ from a business perspective.
Review open substitution changes regularly so that pending delta updates remain visible.
Use Copy Substitutions when existing substitution logic should be transferred to additional companies in a controlled way.
Treat this workflow not only as rule maintenance, but also as the required follow-up processing for already affected target contexts.
The visible result is a clear view of adjusted target values and remaining follow-up work.

Process CHK-01 - Check consistency for records and field values Consistency checks show whether target data matches the expected state. +

Open the relevant consistency check with the source company, target company, and table context you want to review.
You see the table, company context, and later the resulting findings.
Start either a record-based check or a field-based check depending on what you need to analyze.
Evaluate the review entries together with the underlying relations and rules.
If deviations appear, also assess whether the cause lies in missing relations, incomplete rules, open substitution changes, or in the source data itself.
Use the results as the basis for follow-up work, renewed release, or the completion of missing rule components.
The visible result is a traceable list of deviations and follow-up work.

Result

The key MDM processes for relations, DSR, substitutions, and consistency checks are described in a traceable sequence.
Relations, controlled changes, substitutions, and consistency checks are classified as connected workflows.
The page now covers the most important application scenarios directly inside the relevant process context.

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog shows the main day-to-day workflows in Shipping Labels. It explains how label creation starts from different Business Central documents and how users can continue with downloaded labels, tracking information, and shipping reports.

Context

Shipping Labels supports several operational entry points because companies do not always ship in the same way. Some teams create labels directly from sales orders, others rely on warehouse shipments, and some use shipment orders for scenarios outside the classic warehouse flow.

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog shows where operational data and manual assessments enter BE-terna Vendor Rating. It helps you understand how purchasing processes, complaints, and audits together shape the final vendor result.

Context

Vendor Rating combines indicators from purchasing processes with manually maintained assessments. The quality of the result therefore depends directly on how consistently purchase orders, goods receipts, complaints, and audits are maintained.

Prerequisites

The basic setup and the rating criteria schema are maintained.
Relevant vendors are enabled for vendor evaluation.
Thresholds, grade percentages, and classifications are defined.

Process catalog

Process Purchase orders Maintain appearance grades directly on the purchase order when no separate goods receipt is used. +

In purchase orders, the Appearance grade field is available on both the header and the lines.
The grade can be copied from the header to the lines and adjusted individually per line.
Grades 1 to 6 are supported; grade 1 is the default value.
After posting, the appearance grade is reset so follow-up and partial deliveries can be rated independently.

Click to enlarge

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog summarizes the main end-to-end flows of Professional Services. It shows how sales contracts, recurring billing, ticketing, work orders, and purchase contracts work together from a business perspective.

Context

Professional Services connects sales, service, and purchasing processes through shared contract, project, and billing objects. This creates linked process paths from the initial quote to recurring invoicing or from a service case to a billable service transaction.

Prerequisites

The core setup for contracts, billing types, tickets, and work orders is maintained.
Projects, customers, vendors, and relevant number series exist.
Teams have defined which processes are triggered manually, from contracts, or from external systems.

Process catalog

Process Sales quote to recurring billing Quotes, sales contracts, and recurring invoicing are directly connected in Professional Services. +

A sales quote can be created with the Professional Services sales type and linked directly to a new or existing sales contract.
The sales contract stores billing assignments, contract duration, service level agreements, and other recurring service components.
Once the contract is activated, due services are collected in the recurring invoice list.
From recurring billing, multiple invoices can be created, reviewed, printed, and posted.

Process Purchase contracts and purchasing-side contract visibility Purchasing is connected with customer-side contract scenarios through purchase contracts. +

Purchase contracts define the contractual framework with a vendor, including validity and optional customer reference.
Contract lines maintain services, quantities, prices, and validity periods.
Purchase contracts can be linked to sales contracts for transparency across vendor and customer scenarios.
Activated purchase contracts can be considered in batch purchase-order generation or trigger purchase orders directly.

Process Ticketing and service billing Service cases are captured in tickets, released, and transferred into billable service output. +

Tickets can be created manually in Professional Services or transferred from external ticketing systems through the API.
The ticket stores responsibilities, ticket lines, project reference, and optional contract or contingent reference.
Once completed and released, the ticket can be transferred and posted, which creates project planning lines.
These services are then collected and invoiced through service billing.

Process Work orders and operational service execution Work orders structure planned field or service activities and convert execution into billable services. +

Work orders can be created manually, from tickets, or from property-related master data.
The process maintains header data, order lines, and later the actual service lines delivered.
Status changes such as completed and released control when the order is ready for print, handover, or billing.
When transferred or posted, the system creates project planning lines that can be invoiced through service billing.

Process Recurring tasks and work packages Plannable activities are prepared in a structured way and turned into operational tickets or work orders. +

Recurring activities can be defined as work tasks and grouped into work packages.
Depending on the configuration, these structures generate tickets or work orders for execution.
This standardizes repeatable service activities and makes them easier to schedule and process.
Final billing still follows the service and contract logic of Professional Services.

Outcome

Sales, service, and purchasing flows are combined into one shared process picture.
Contract and billing objects form the common backbone across the individual steps.
Recurring services can be managed in a traceable way from the first commercial step to the final billed service.

Process Catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This process catalog consolidates the most important workflows around BE-terna Printconnect after the initial setup has been completed. It shows where users trigger print jobs, manage printers, and review print history.

Context

The actual print trigger happens on business pages, posted documents, or report dialogs in Business Central.
Printers, default assignments, and print-related follow-up information are maintained centrally in the Printconnect administration pages.

Prerequisites

The PrintNode and BE-terna Printconnect setup is complete.
At least one suitable printer is selected for the user.
The PrintNode Client is signed in on the workstation.
Default printers and special paper formats are maintained when print jobs should run without manual selection.

Process Catalog

Click to enlarge

Process Catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This process catalog describes the key workflows in NOS Disposition Planning. Use it as a starting point when creating a new planning document, reviewing planning values, analysing shortfalls, or releasing a document for automatic updates.

Context

The basic configuration (Fashion Planning Setup, NOS colours, size keys) is described on the Setup page.
The business context is explained in the Overview.

Prerequisites

The Fashion Planning Setup is fully maintained (number series, NOS default factor).
Items have the relevant NOS colours assigned with the NOS flag active.
Users have the FN Dispo NOS Planning permission set assigned.

Process Catalog

Process Create a new Dispo NOS document Create a new planning document and configure the item filters and planning parameters. +

Open the Dispo NOS Headers list and create a new document. The number is assigned automatically from the configured number series.
Enter the item or item filter in the Item No. Filter field. This field is required before planning lines can be created.
Select the Planning Type: ItemVariant for planning at variant level, ItemColour for planning aggregated by colour.
Select the Period Type (Week, Decade, or Month) and define the planning horizon using Periods Before and Periods After. The total number of columns must not exceed 36 periods.
Set a Vendor No. filter if only colours belonging to a specific vendor should be included.
Set a Colour Filter or Colour Season if the planning should be limited to specific colours or seasons.

Process Create planning lines Generate all planning lines and periods based on the document filters. +

Run the create planning lines action in the Dispo NOS document. The system creates planning lines for each qualifying NOS colour across all configured periods.
The system checks whether a document for the same item filter, colour filter, and start date already exists. If so, an error message is shown and no lines are created.
If an older document with the same filters but an earlier start date exists and is still Open, it is automatically set to Released before the new lines are built. Existing lines of the current document are then deleted and rebuilt.
After creation, review the planning matrix: each colour (or variant) should have rows for historical data, depot, base, plan, and closing inventory.

Process Review and manually adjust planning values Adjust corrections and planned order quantities in the planning matrix. +

Open the planning matrix in the document. Review the Hist row for plausibility of historical reference values per period.
Enter manual corrections in the Correction row to adjust the reference sales for a period. The base value (Base) and planned sales quantity (Plan) are recalculated immediately.
Enter the desired order quantity in the Plan Order row to specify a manual order quantity for a period.
Corrections and planned order quantities are preserved during automatic rebuilds of released documents, as long as the combination of item, colour (and variant), and period start date remains unchanged.

Process Analyse and resolve shortfalls Identify colours with a projected negative inventory and respond with targeted order quantities. +

Enter the number of periods to check for shortfall in the Coverage (Periods) field in the document header. A value of 0 checks all periods.
Review the Has Shortfall field in the document header. If active, at least one colour in the planning matrix has a negative closing inventory within the coverage horizon.
Activate Hide Covered Colours to show only colours with a shortfall in the planning matrix, making targeted review easier.
Enter a Plan Order quantity for periods with a negative closing inventory until the projected closing balance becomes positive.
Deactivate Hide Covered Colours and check Has Shortfall once all colours are sufficiently covered.

Process Release a document and enable automatic updates Release a completed document so it is picked up by the scheduled refresh job. +

Once planning values have been reviewed and shortfalls resolved, set the document to Released using the Release action.
Released documents are periodically updated by a background job (job queue entry). Each run rebuilds all lines, restores manually set corrections and planned order quantities, and recalculates the inventory projection.
When a document is complete and should no longer be updated, set it to Closed.

Process Show customer lines Display optional customer lines to review planning needs at the level of individual customers or head establishments. +

Activate the Show Customer Lines field in the document header to show additional customer lines below the SKU lines in the planning matrix.
Customer lines show reference sales and corrections per customer (head establishment) and period.
Customer lines can be given separate corrections, which feed into the overall correction total of the parent SKU line.

Process Assign an NOS size key and review variant distribution Assign an NOS size key to a document when colour-level planning requires distribution to variants. +

Select the desired NOS size key in the Size Key field in the document header. This is relevant when the Item Colour planning type is used.
The size key determines how a planned colour quantity is distributed across the individual size variants.
Review the distribution shares in the size key using NOS Size Key Card before assigning it to a document.
If no size key is assigned, no automatic variant distribution is performed.

Results

You can create a Dispo NOS document, configure it, and generate planning lines.
You know how to enter corrections and planned order quantities in the matrix.
You can identify shortfalls and resolve them with targeted order quantities.
You understand how the automatic refresh of released documents works.

Store Type

Mon, 01 Jan 0001 00:00:00 +0000

Store categories can be created and stored on the cash register setup, for example store or outlet. This can support the setup of cash register setups and tenders.

Click to enlarge

Voucher Card Entries

Mon, 01 Jan 0001 00:00:00 +0000

The Voucher Card Entries contain all voucher card transactions.

Click to enlarge

There are different actions.

Activation The card was activated.
Cancellation The transaction was cancelled.
Credit The card was loaded.
Balance The balance was queried.
Debit The card was used for a payment.

Note: Several transaction stages can arise for each receipt and/or voucher card.

DATANORM

Mon, 01 Jan 0001 00:00:00 +0000

In the DATANORM area in the BE-terna Project facility, the following items are listed: Facility, discount groups, and product groups.

Click to enlarge

Setup

After clicking on “Setup”, you will be taken to the DATANORM facility.

Click to enlarge

Field	Explanation
Commit pro	Import-Datei: DATANORM-Datei wird bei einem Fehler nicht ins System geschrieben sondern der Import wird komplett rückgängig gemacht. Importierter Datensatz: Die Datei wird bis zum Fehler eingelesen und der Rest nicht.
Fehlende Mengeneinheiten importieren	Wenn nicht angehakt, können noch nicht in den Stammdaten hinterlegte Mengeneinheiten vor dem DATANORM-Import als Variante einer Mengeneinheit eingetragen werden. Wenn angehakt, ist dieses Vorgehen nicht verfügbar und die neue Mengeneinheit wird einem Artikel nur hinzugefügt.
Nutze Filter für Hauptwarengruppen	Wenn angehakt, ist es möglich nur einzelne Warengruppen einer DATANORM-Datei zu importieren.
Nutze Filter für Rabattgruppen	Wenn angehakt, ist es möglich nur einzelne Rabattgruppen einer DATANORM-Datei zu importieren.

Regarding the filters, it must be mentioned that if they are activated, certain discount or product groups or all of them must be selected. Otherwise, no costing items are imported.

Export Contact Status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns contact processing status including error text.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/ODataV4/<serviceName>_ContactStatusExportOData?company=<companyName|companyId>

Required Payload Fields

webshopChannel_P
contactNo_P or eMail_P

Response

The response contains a JSON object in value with contactNo and errorText.

Result

The webshop can check asynchronous contact processing status.

Export Voucher

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns voucher status and balance information for a webshop channel.

Method

Operation: VoucherExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

VoucherNo_P

Response

XML in voucherExport_PX with voucher ID, state, amount, and currency.

Result

The webshop can synchronize voucher validation and voucher status display.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Where should you start before the first productive go-live? Start with setup, master data, and one complete test run for the most important business transactions. +

Start with Setup and verify that webshop channels, language and country assignments, and the main control values are maintained completely.

Then continue with Master Data so that categories, attributes, translations, and channel-related mappings are available. After that, test at least one complete process such as item release, sales order creation, or return processing.

Finance Validation

Mon, 01 Jan 0001 00:00:00 +0000

The cash register validations make it possible to configure custom validation criteria. If such a validation fails, the related import cannot be posted automatically via a job queue. In that case, posting is only possible manually or via manual batch posting.

The validations are managed via the Finance Validation menu item. This opens a list of the available cash register validations. In the card, you can create a new validation or edit an existing one.

Packaging assignment in documents

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the operational packaging assignment on documents. It expands on the default logic, manual changes, weight calculation, and the use of lots and expiration dates in daily operations.

Business value

Shows how standard and alternative packaging structures are actually used on documents.
Describes which manual interventions are allowed and how structural consistency is maintained.
Explains weight and tracking logic through registration and posting.

Process map

flowchart LR
  A[Propose standard structure] --> B[Select standard or alternative]
  B --> C[Apply manual changes if required]
  C --> D[Use wizard/detail assignment for tracking]
  D --> E[Validate weights]
  E --> F[Register package assignment]
  F --> G[Post document]
  G --> H[Review posted assignment]

Content focus

General packaging-assignment process

The packaging assignment is maintained in the document through which the relevant shipping, purchasing, or transfer process is posted. The decisive value is the quantity that must be shipped, received, or moved on the respective document line.

Reports and evaluations

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The reports and evaluations in BE-terna Vendor Rating make results, trends, and root causes transparent. They support both operational analysis of individual ratings and the overall assessment of a vendor.

Business value

Shows individual ratings together with their origin and timestamp.
Makes historical developments in vendor evaluation visible.
Consolidates main criteria and subcriteria into one clear overall report.
Supports internal analysis and vendor discussions with reliable data.

Functional focus

Rating entries

Rating entries document every individual assessment of a criterion. They show which grade was assigned, when the rating was captured, and from which process or audit it originated.

Voucher Entries

Mon, 01 Jan 0001 00:00:00 +0000

The Voucher Entries contain all voucher transactions.

Click to enlarge

Field	Description
Entry No.	Primary key
Location	The location code of the cash register
Cash Register	The cash register code of the cash register
POS Process	The POS process of the respective receipt
Receipt No.	The number of the respective receipt
Time	Date and time of the transaction
No.	The voucher number
Transaction	Authorization: The voucher was registered in the receipt Issue: The voucher was sold Redemption: The voucher was redeemed, in full or in part Invalidation: The voucher was invalidated after issue Cancelled: The voucher was cancelled after authorization
Amount	The amount of the transaction
User	The user who triggered the transaction
Remarks	Notes on this transaction

Administration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the ongoing administration of BE-terna Printconnect. It serves key users and administrators as the central reference for extension web access, default printers, and recurring printer-management tasks.

Access in Business Central

Open BE-terna Printconnect Administration when printers, default mappings, or print history must be maintained.
Open Extension Management when Allow HttpClient Requests for the extension must be checked.

Prerequisites

You have key-user or administrative permissions in Business Central.
PrintNode and BE-terna Printconnect are already set up on a basic level.

Activities

Verify HttpClient access for the extension

In Extension Management, Allow HttpClient Requests must be enabled so that the extension can access external web services. Check this setting especially after reinstallations or updates.

Administration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the operational administration of Shipping Labels after the shared and carrier-specific setup is in place. It focuses on URLs, reusable setup packages, request analysis, retention settings, and the support information that helps key users and administrators keep the solution stable.

Access in Business Central

Open Shipping Label Setup for global settings, request logs, deletion settings, and access to related setup pages.
Open Shipping Label URL when productive or test endpoints must be created or updated.
Open Configuration Packages when setup data should be exported, imported, or rolled out across companies or environments.
Open BE-terna Support Info and the BE-terna license update page when support or license maintenance is required.

Prerequisites

Shared setup and at least one carrier setup are already maintained.
The user has permission to change setup data, URLs, and configuration packages.
Productive and test credentials or URLs are available from the relevant carrier.
Customer number, ident, and other support metadata are available where license or support actions are required.

Activities

Maintain shipping label URLs for productive and test use

Shipping label URLs define which carrier endpoint is called by the respective setup. In practice, this usually means that you maintain separate entries for test and productive access and assign them to the relevant carrier setups.

Campaign Entries

Mon, 01 Jan 0001 00:00:00 +0000

The Campaign Entries menu item contains all campaigns applied so far.

Click to enlarge

Field	Description
Entry No.	Unique and sequential entry number
Source Type	Trigger of the campaign, currently always receipt
Source Code	Primary key, currently always receipt ID
Time	Date and time of campaign registration
Campaign Code	Code of the applied campaign
Campaign Type	Type of the campaign at the time of application
Registration Type	Type of campaign registration Automatic: The campaign was registered automatically Manual: The campaign was registered manually Coupon: The campaign was registered by a coupon
Registration Code	Contains the code used for manual registration
Discount Type	Type of discount at the time of application Discount: Percentage reduction Reduce: Absolute reduction
Discount Value	The percentage or absolute reduction value
Reduce Amount	The sum of all reductions made by this campaign
Transaction	The type of campaign application Issue: The reduction was printed as a coupon when the receipt was finished Application: The campaign was applied

Export Contact

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method exports contact master data per channel, optionally filtered to one contact.

Method

Operation: ContactExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameters

contactNo_P
incremental_P

Response

XML in contactExport_PX with contact fields such as name, address, country, and communication data.

Result

The webshop receives current contact master data.

Export Location

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns all locations assigned to a webshop channel.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/channels('<webshop-channel-code>')?$expand=locations

Required Parameter

webshop-channel-code in the channel URL

Key Response Fields

Channel: code
Location: code, name, address, postCode, city, countryRegion, phoneNo, eMail

Result

The webshop receives linked warehouse locations for shipping and availability logic.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Why is no packaging structure found for the sales line? Usually either no matching released structure exists or the assignment context does not match. +

If this message appears in the packaging assignment, the current document line either has no matching packaging structure or no released variant is available. First check the business assignment context, for example item, item variant, customer, document header, or a document-specific exception.

Only a released packaging structure can be used operationally as the default structure. Open structures can still be edited, but they are not proposed automatically as the standard choice.

Fiscalization

Mon, 01 Jan 0001 00:00:00 +0000

The actual signing of receipt data does not take place directly in BE-POS, but is performed by the external providers Fiskaly, Fiskaltrust, and EFSTA. You therefore need an account with one of these three providers. We recommend the provider Fiskaly because no additional dependencies are required and the necessary account is provided by BE-terna.

Provider	Modules	Contact	Portal
Fiskaly	Germany	sales@fiskaly.com	https://dashboard.fiskaly.com/
EFSTA	Germany, Austria, Italy	office@efsta.eu	https://portal.efsta.net/
Fiskaltrust	France	contact@fiskaltrust.fr	https://portal.fiskaltrust.fr/

EFSTA Requirements

To link a cash register with EFSTA, it is first necessary to download an electronic fiscal register, EFR, from the following link: http://public.efsta.net/EFR/

Reference Processes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page consolidates the webshop reference processes as a condensed process catalog in the BE-Commerce module of the Commerce Interface solution.

It provides the core building blocks for:

Webshop channel setup
Importing webshop changes into Business Central
Processing imported e-commerce documents
Exporting webshop-relevant data from Business Central

Process Catalog

Process WSE – Webshop setup Basic setup of the webshop channel in Business Central. No data is transferred to the webshop during this setup. +

Create or change a webshop channel (assign attachment types, languages, countries, and line types).
Define carriers and transport codes per channel.
Define payment methods per channel.
Define countries (optionally including an EU country/region code).
Define the languages used by the webshop.
Define webshop colors.
Maintain HTTP setup per webshop channel (including the URL binding).

Process IBC – Import BE-Commerce New and changed webshop data is imported into Business Central via the interface and made available as an e-commerce document. +

Import via the e-commerce interface: webshop data is loaded into intermediate tables (for example webshop and reservation tables).
A corresponding e-commerce document is created from the imported data so it can be processed further.
Typical import variants:
- Contacts
- Orders
- Sales return registration (sales complaint)
- Reservations
Next step: processing via PBC.

Process PBC – Process BE-Commerce Check, control by status, correct if needed, and release: this creates the corresponding system documents. +

Check the e-commerce document: the system lists errors in a structured (tabular) way.
Set the message status (for example checked/erroneous/processable).
Rework data: manual correction when validation fails.
Check and release: the system processes the document and creates follow-up documents.
Typical outcomes:
- Sales order and downstream sales documents
- Sales complaint/return
- For reservations: creation of a transfer order for the reserved items (store → reservation/selection location)

Process EBC – Export BE-Commerce Webshop-relevant data is provided when created/changed in Business Central; the webshop is notified and retrieves the data via web services. +

Create/change data: relevant data is maintained in Business Central.
Notify the shop: a ping is sent to the webshop based on the HTTP setup.
The shop retrieves the data: the webshop pulls the updated data via web services.
Typical export objects (examples):
- Webshop categories (tree structure, translations)
- Dynamic attributes (including values and translations)
- Free-text attributes (including translations)
- Webshop items (categories, attributes, cross selling, colors, multilingual descriptions, publishing per channel)
- Sales prices (including start/end date, potentially on variant level)
- Availability (single item or batch transfer)
- Contacts
- Order statuses
- Vouchers

Support for public tenders

Mon, 01 Jan 0001 00:00:00 +0000

BE-terna Project offers the possibility to export the forms 221, 222 and 223 (formerly EFB) to Excel for third parties, which are often required in public tenders. As a rule, no manual post-processing is necessary. If it does, the processing takes place on the first Excel sheet. The function EFB 221 – 223 is located in the document in the navigation menu under Reports and again Reports.

Click to enlarge

Devices

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Devices you can find the device setup, where the control of various hardware components can be configured.

Click to enlarge

Actions

Several actions are available on the device setup card and are briefly explained below:

Field	Description
Receipt Test	Tests control of the receipt printer
Cash Drawer Test	Tests control of the cash drawer
Display Test	Tests the display. The display pop-up must be allowed in the browser so that the display is visible.
Store Management	Enables management of multiple stores

Store Management

Store management makes it possible to transfer settings from one device setup to all or selected device setups.

Export Contact Status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method returns processing status for contact creation or update.

Method

Operation: ContactStatusExport
Service: Codeunit BEConnect as SOAP web service

Required Parameters

webshopChannel_P
contactNo_P or eMail_P

Response

return_value and optional errortext_P.

Result

External systems can verify contact processing completion.

Export Vendor

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns vendor master data for integration scenarios.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/vendors

Key Response Fields

systemId, no, name, address, postCode, city, countryRegionCode
eMail, currencyCode, languageCode, paymentTermsCode, shipmentMethodCode, blocked

Result

External systems receive current vendor master data from BC.

Guarantees

Mon, 01 Jan 0001 00:00:00 +0000

Create and process guarantees

A list of all guarantees can be found in the Guarantee Overview, which can be accessed via the search function. The New function can be used to create a new guarantee.

Click to enlarge

Field	Explanation
Nr.	Wird automatisch vergeben.
Beschreibung	In diesem Feld kann eine Beschreibung als Freitext für Bürgschaften gepflegt werden. Dafür gibt es keine Vorgaben.
Bankkonto Nr. (Pflichtfeld)	Das Bankkonto des Users.
Ext. Belegnummer	In diesem Feld wird die Belegnummer des Partners hinterlegt.
Ext. Kontonummer	An dieser Stelle kann die zugehörige, externe Kontonummer erfasst werden.
Projektnummer	Die Projektnummer zu welcher die Bürgschaft hinterlegt wird.
Typ	Hier kann ausgewählt werden ob der User ein Debitor oder Kreditor ist.
Debitoren-/Kreditorennummer	Je nach Einstellung unter Typ, wird hier der jeweilige Debitor bzw. Kreditor ausgewählt.
Kosten	Kosten die für diese Bürgschaft entstehen.
Bürgschaftsart	Hier wird ausgewählt, ob die Bürgschaft gegeben oder empfangen wurde.
Bürgschaftstyp	In diesem Feld wird festgelegt, um welche Art Bürgschaft es sich handelt.
Unbefristet	Legt fest, ob es sich um eine unbefristete Bürgschaft handelt.
Status	Zeigt den aktuellen Status der Bürgschaft an.
Bürgschaftsbetrag	Höhe der Bürgschaft.
Kumulierter Betrag	Gesamtbetrag aller Bürgschaftszeilen.
Änderungsdatum	Letzte Änderung an der Bürgschaft (wird automatisch gesetzt).

Different types of guarantees can be created in the BE-Project:

POS Process

Mon, 01 Jan 0001 00:00:00 +0000

Under Archive → POS Process you can see when a POS process was started and ended and which turnover was generated with it.

Click to enlarge

Using the POS Process Card, you can view the turnover and income of the POS process and also trace them in detail.

General

Click to enlarge

Field	Description
Location	The location code of the respective cash register setup
Cash Register	The cash register code of the respective cash register setup
No.	The number of the selected POS process
Finished	Marks the POS process as completed
Start Time	The time at which the POS process was started
End Time	The time at which the POS process was ended
Cashier Code	Indicates the cashier code that originally started the POS process
Cashier Name	Indicates the cashier name that originally started the POS process

Cash Movement

Click to enlarge

Process Catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This process catalog bundles the main business workflows in BE-terna Manufacturing. It serves as an entry point when you want to understand end-to-end processes from master data preparation through production, purchasing, and costing, or jump quickly to the relevant detail page.

Context

Initial configuration of Manufacturing Setup, items, routings, and locations is described on the Master Data and Setup page.
The thematic pages provide the detailed instructions for production planning, production orders, purchasing, logistics, tool management, and costing and reporting.

Prerequisites

Master data, routings, production BOMs, and locations are maintained for the relevant items.
Users can access planning worksheets, production orders, output journals, and the required lists or role center pages.

Process Catalog

Process Prepare manufacturing items and master data Set up items, routings, BOMs, item versions, and core switches so later production orders work with the correct defaults. +

Activate the required automation in Manufacturing Setup for default fields, locations, routing link codes, and journals.
Create or open routings and production BOMs directly from the item card and review active versions where needed.
Maintain item versions, location defaults, and routing link codes so that traceability remains intact in the production order.
See Master Data and Setup for the detailed configuration.

Process Plan demand and create production orders Transfer demand from sales, planning worksheets, and recurring planning runs into concrete production orders. +

Use order planning with sales units where quantity and unit should flow from the sales order into the production order.
Review action messages in the planning worksheet together when several suggestion lines should be accepted or reset in one step.
Set up recurring planning runs through the job queue when planning worksheets should be generated automatically.
Use production families when one production order should combine several items or quantities with the same routing.
The related instructions are collected on Production Planning.

Process Review, release, and process production orders After creation, the production order moves through defaults, overview pages, release checks, posting, and controlled rework. +

Create production orders manually, from sales orders, from planning suggestions, or from order planning.
Review material availability and processing status through the overview pages for firm planned and released production orders.
Use defaults, reopening, rework, and worksheet views to manage production orders in a controlled way.
Use reopening and correction suggestions only for necessary follow-up postings, not for renewed operational planning.
See Production Order Management for the detailed lifecycle.

Process Manage reporting and item tracking in the production order Journals, quantity automation, correction suggestions, and item tracking work together closely in production order management. +

Use related output and consumption posting when quantities should be calculated automatically from each other.
Use correction suggestions when negative output or consumption postings should propose the matching application entry automatically.
Review inventory information in the production or consumption journal before backward flushing or correction postings are carried out.
Use item tracking when serial, lot, or package information should be generated automatically or transferred from a main component.
Details follow on Production Order Management.

Process Execute subcontracting through purchasing Subcontracting operations are handled in the purchasing area with purchase orders, pricing, and transfer links for subcontractors. +

Calculate the subcontracting suggestion from the released production order and create the purchase order from it.
Open related documents directly from the production order or purchase order to review the current subcontracting status.
Maintain subcontracting prices by vendor, work center group, and item where costs should not come only from the routing.
Use purchase-transfer link lines when components have to be shipped together with the subcontracting purchase order.
See Purchasing and Subcontracting for the detailed process.

Process Handle returns and pending consumption through logistics Subcontracting returns and pending consumption postings form a dedicated logistics follow-up process. +

Use warehouse receipt, put-away, or inventory put-away for subcontracting returns in the standard flow only when the subcontracting operation is the last routing operation.
Activate pending consumption by location only where backward flushing with routing link codes should be handled in a controlled way.
Clear open residual consumption through reposting or cancellation before a production order is finished.
See Logistics for the detailed flow.

Process Use and maintain tools in the production process Tools are created as master data, assigned to routing operations, logged through posting, and maintained through repairs. +

Assign tools and complete tools directly to routing operations so they flow into the production order.
Use output posting when tool usage should create tool ledger entries automatically.
Control repair orders, service life, cavities, and status so tools can be returned to service in a controlled way.
See Tool Management for the detailed processes.

Process Evaluate production orders through costing and reporting Dedicated reports support final costing, WIP valuation, and traceability of related item ledger entries. +

Use production printouts and production order job cards when production orders should be reviewed with header, line, routing, and component details.
Review final costing across multiple production levels when expected and actual material or capacity costs should be compared.
Check WIP values and related item ledger entries when you need to understand amounts, origins, or downstream documents of a production order.
The Costing and Reporting page groups the relevant perspectives.

Result

You can place the most important manufacturing processes in BE-terna Manufacturing into one coherent business context.
You can navigate faster to the right detail page for setup, operational handling, and reporting.
Transitions between production planning, production orders, purchasing, logistics, and costing remain understandable.

Work aids for daily work

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page bundles practical guardrails for recurring decisions in daily MDM work. It is aimed at users who release relations, evaluate review results, follow up substitution changes, or want to structure daily maintenance tasks more efficiently.

Business value

Shortens the daily classification of common MDM decisions.
Supports a consistent assessment of releases, review errors, and follow-up work.
Makes recurring control points for relations, DSR, substitutions, and field views more transparent.
Complements process and FAQ pages with concrete orientation for everyday work.

Focus

Decision aid for status actions

Not every status action serves the same purpose. Releasing a relation is the standard path after a complete review, reopening brings a relation back into a controlled editable state, and release without update remains a deliberate exception for cases without retroactive redistribution.

Employee Discount Entries

Mon, 01 Jan 0001 00:00:00 +0000

Employee Discount Entries

The employee discount entries show the individual discount lines. For each employee, the accumulated reduction amount for the current date filter is displayed. The current calendar year is used as the initial date filter. If the granted reduction amount exceeds the quota, this is shown in the warning color Red.

Click to enlarge

Export Location

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method exports location master data for a sales channel.

Method

Operation: LocationExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Response

XML in locationBranchExport_PX with location code, name, and address data.

Result

The webshop receives channel-relevant location data.

Export Webshop Category

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint provides channel category records including hierarchy data and optional translated texts.

Endpoint

Method: GET
URL pattern categories: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/webshopCategories?$filter=webshopChannelCode eq '<webshop-channel-code>'
URL pattern category descriptions: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/webshopCategoryDescriptions?$filter=webshopChannelCode eq '<webshop-channel-code>' and webshopCategorySystemId eq <category-system-id>

Required Parameters

webshopChannelCode
For descriptions additionally webshopCategorySystemId

Key Response Fields

Category: systemId, webshopCategoryCode, parentCategoryCode, active, hidden
Texts: language, text, webshopCategorySystemId

Result

The webshop receives category tree data and multilingual category labels.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Where should I start if I do not know Material Surcharges Management yet? Start with the overview and then move to setup before you use charges productively. +

If you are using Material Surcharges Management for the first time, start with the Overview. It explains the purpose of the solution and the work areas involved. Then continue with Setup and master data to define price determination and prepare charges correctly.

FAQ Why is no charge shown for an item? In most cases, the charge assignment is missing or the maintained unit or quantity type does not fit the transaction. +

First review the Item Charge Assignment page. A charge can only apply correctly when item, charge, quantity type, unit, and display logic fit together in the business context. The setup basis for this is described on the Setup and master data page.

FAQ Why are charge prices on open documents not updated as expected? The most common cause is the pricing logic, the relevant date fields, or the business context of the document. +

Material Surcharges Management reacts to changes on sales and purchase documents as well as to relevant date fields. If the expected price does not appear, first check the Sales Price Calculation and Purchase Price Calculation settings together with the business-relevant date fields on the affected document. Also make sure that a matching price line exists at all for the combination of charge, relation, and period.

FAQ What controls how charges are shown on documents? Document display is maintained in the charge assignment and must fit the intended business output. +

The Display on Documents setting controls how a charge is handled in the document context. If charges appear differently on documents than expected, first review this setting and then the document output that is used. In particular, summarized charges require the output to be aligned with that business logic.

FAQ What is Item Charge Costs used for? The page helps review charge costs for item, date, and quantity before you use prices productively. +

Item Charge Costs is mainly useful for business review. It shows how charges affect costs depending on item, date, and quantity. Use this view especially when you want to validate pricing rules or understand which additional costs are considered before applying a change productively.

FAQ Why are translations or understandable charge texts missing? Language-dependent labels are not generated automatically from the charge logic and must be maintained deliberately. +

If charges are unclear in multilingual documents or views, review the maintenance on the Item Charges page and the available translation entry there. Material Surcharges Management extends the business charge logic, but it does not replace the deliberate maintenance of language-dependent texts. For a consistent end-user output, translations and document display should always be reviewed together.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Why is my item version not shown in the production order? Usually no version is certified, the number series is missing, or the production order was not refreshed after the change. +

First check on the item card whether a number series for item versions is maintained and whether exactly one version has the status Certified. Then review the FactBox on the item card or item list and run Process > Refresh Production Order on the production order. Only then is the certified item version transferred into the production order line. Details are available on Master Data and Setup.

FAQ Why are planning results missing from my automatic planning run or expected worksheet? Overlapping item filters or several planning runs for the same item are the most common cause. +

If one item is covered by several planning run setups, the result is written into the worksheet of the last calculation. Review Planning Group, Filter Expression, the Parameter String of the job queue entry, and the target worksheets of the different planning runs. This helps prevent planning suggestion lines from being deleted or overwritten elsewhere. See Production Planning.

FAQ Why can't I finish a production order? Open pending consumption, remaining component postings, or missing operation confirmations are the most common causes. +

Start with the released production order overview and check whether components, capacity entries, or warehouse picks are still open. If the production order shows Pending Consumption, that quantity must first be reposted or cancelled before the order can be finished. Details are available on Production Order Management and Logistics.

FAQ Why does the worker time registration not show the operations I expect? Usually worker filters on work center group, work center, or department apply, or the operations are not released. +

First review the worker master record and the maintained filters. In time registration, only released operations are shown that match those criteria. In addition, the signed-in worker can manually change filters on the time registration page; these deviations are highlighted visually. Also check the Worker Authentication Type and the dedicated worker role center setup. See Production Order Management.

FAQ Why does automatic backward flushing fail during output posting or warehouse receipt? Usually inventory is missing for a component linked by routing link code, or the location is not configured for pending consumption. +

If an operation uses components with Flushing Method = Backward and a routing link code, enough inventory must exist for automatic consumption. If stock is missing, posting either fails or creates pending consumption entries, depending on the location setup. Review inventory, location settings, and the Logistics page.

FAQ Why were serial or lot numbers not transferred automatically? Automatic item tracking depends on the tracking code setup, the main component, and the exact process step that triggers the transfer. +

Check whether the tracking code logic is configured consistently on the tracking code, the main component, and the output item. Depending on the scenario, numbers are created only when the production order is refreshed, the assembly quantity is validated, or the main component consumption is posted. Also note that not every combination of serial, lot, and package transfer is supported. See Production Order Management for the details.

FAQ Why are default values such as user or location missing in the production order? The order origin and item-based overrides influence which defaults are finally transferred. +

The transfer of Assigned User ID, Gen. Bus. Posting Group, and Default Output Location Code depends on the switches in Manufacturing Setup and on how the order was created. In addition, an output location maintained on the item overrides the default from setup. Review both Manufacturing Setup and the item card. See Master Data and Setup and Production Order Management.

FAQ When should I reopen a finished production order? Reopening is intended for corrections and follow-up postings, not for renewed operational planning. +

Finished production orders should only be reopened when additional consumption, output, or reversal postings are required. A reopened order is not rescheduled for capacity planning, and backward-flushed positions do not create a second automatic backward posting when the order is finished again. Do not use reopening as a normal workaround to bring a completed order back into operational planning. See Production Order Management.

FAQ Why does warehouse receipt in subcontracting not work as expected? Often the subcontracting operation is not the last routing operation, or backward-flushed components with routing link codes cause follow-up issues. +

For the supported standard flow, the subcontracting operation should be the last operation in the routing. If it is not, the return can still be posted, but the internal follow-up move to the next work center is not supported. Also review whether components with Flushing Method = Backward and a routing link code are involved. In such cases, Purchasing and Subcontracting and Logistics explain the limitations.

FAQ Why do tool dimensions or tool ledger entries not appear as expected? Usually the activation in Manufacturing Setup is missing, the tool is not assigned correctly on the operation, or the number of dimensions is too high. +

First review the tool assignment on the operation and, for complete tools, also the switch that controls posting during output reporting. If dimensions from tools should flow into output reporting lines, the related activation in Manufacturing Setup must be enabled. Also note that a maximum of 10 dimension values per output reporting line is supported. Details are available on Tool Management.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Why can’t I edit a released relation directly? Released relations are intentionally protected so that productive rules are not changed without control. +

Released relations form the productive rule base in MDM and should therefore not be changed unnoticed. When a business rule has to be adjusted, the relation is brought back into an editable status and released again only after another review. For the broader context, see the process catalog.

FAQ When is release without update the right business choice? This action is intended only for deliberately limited changes and should not be the default release path. +

Release without update is appropriate when a relation should be released again without retroactively redistributing already changed records to the target companies. This can be acceptable for clearly scoped rule adjustments, but it should be a deliberate decision because otherwise open business changes will not be carried forward in the target context.

FAQ Why are there still open tasks after substitution changes? Substitutions first change the rule set; the actual follow-up processing can still require an update. +

Changed substitutions do not automatically update all already affected records. Open entries in the change log and a possible update indicate that the business rule has been adjusted, but the operational follow-up processing is still pending. The practical classification is also covered on the work aids for daily work page.

FAQ When should I apply DSR filters to existing data? This action is useful when changed DSR rules should apply not only to new records, but also to records that already exist. +

Use this action when changed DSR logic should also be rolled out to records that already exist. The critical decision is whether only default and automatic decisions should be updated or whether manual decisions may also be overwritten. The business classification of this action is explained on the DSR and Distribution Matrix page.

FAQ What do errors in consistency checks actually mean? Check errors show a deviation between the expected and actual target state, not automatically a technical defect. +

At first, a consistency error only means that MDM found a different state in the target context than the one expected from the relation and rule set. The cause can be a missing relation, incomplete rules, an intentional business deviation, or actually incorrect data. Because of that, review entries should always be assessed together with the relation, the source and target company, and the concrete field context.

FAQ Why doesn’t the missing-relations suggestion always provide usable proposals? Suggestions depend on the existing relation landscape and the business relationship between tables. +

The suggestion functions can only derive relationships that are meaningfully visible from the current table and relation context. If the base relations are too narrow, incomplete, or not yet clearly scoped from a business perspective, the proposal space stays limited as well. Review the existing setup first on the master data and relation maintenance page.

FAQ How do I narrow the field view down to the really relevant information? Field views help distinguish between the full table structure and the fields that are actively used for synchronization. +

In daily review work, not every available field is relevant. Views such as active fields and all fields help users focus either on the actually synchronized fields or on the full table structure. This is especially useful when review results or rule changes have to be classified from a business perspective.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ The installation fails because local printers already exist in Business Central Local printer entries in Business Central printer management can block the initial Printconnect setup. +

If Business Central already contains local printers in printer management, the initial setup can fail with an installation error. In this situation, Printconnect typically cannot create the printer as a cloud printer.

Click to enlarge

First, verify whether local printers are already active in the target system’s printer management.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Why does Shipping Labels say that an assigned source type is missing? The table ID required for the current source document is not maintained in Assigned Source Types. +

Open Shipping Label Setup > Assigned Source Types and verify that the table ID required for the affected process is maintained together with the correct source type. Shipping Labels can only generate labels for the source types that are assigned there. If a new document context needs additional information, extend the Assigned Source Types setup accordingly. See Setup.

FAQ Why can the request not be sent successfully? Usually a mandatory setup value, credential, URL, or master-data field is missing, or there is a connectivity issue. +

Start in the request log and compare Error Text, Response, and HTTP Status. If the request never reached the carrier, first verify internet connectivity, the maintained URL, and the credentials. If the carrier rejected the request, review the source data that was sent: shipping agent service setup, assigned Incoterms, country data, addresses, package data, and required contact information. The Administration page explains which technical details are available in the request log.

FAQ How do I know whether a carrier setup is complete enough for the first test? Before the first request, verify the shared setup, the carrier-specific setup, and the source-document data together instead of testing one field at a time. +

Use a short readiness check before the first end-to-end test:

Voucher

Mon, 01 Jan 0001 00:00:00 +0000

Under Voucher Setup, vouchers can be generated depending on the respective cash register setup settings.

Click to enlarge

Actions

Generate

This functionality generates new vouchers while taking into account the settings of the respective cash register setups.

Click to enlarge

If Voucher Issue is configured as Self-Printed, the specified number of vouchers is created for this cash register setup and marked accordingly with Location and Cash Register. When issuing a new voucher, the respective cash register setup filters by Location and Cash Register and takes the first available free voucher. In this case, the default amount is ignored because the voucher amount is always assigned manually during checkout.

Export Price

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method provides channel-based price information including customer groups and VAT flag.

Method

Operation: PriceExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameters

changedSince_P
itemNo_P
incremental_P

Response

XML with variant prices, currency, list price fields, and priceIncludesVAT.

Result

The webshop receives price structures for catalog and checkout calculations.

Import Return

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint imports return orders from the webshop into the BC import container.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Import/v2.0/companies(<company-system-id>)/returnOrders

Required Payload Fields

Header: webshopChannelCode, orderId, orderType, orderDate, currency, customerNo, contactNo
Lines (returnOrderLines): at least one line with id, type, amount and source order references (orderNo, orderLineNo)

Response Behavior

Returns imported header as JSON.
Optional $expand=returnOrderLines includes imported lines.

Result

The return order is available for downstream BC processing.

Log Entries

Mon, 01 Jan 0001 00:00:00 +0000

The Log Entries document the button presses of the cash register.

Click to enlarge

Voucher Card

Mon, 01 Jan 0001 00:00:00 +0000

The configuration of voucher cards can be found under Setup → Voucher Card.

Click to enlarge

Setup

General

Click to enlarge

Field	Description
Location	The location code of the cash register setup to be used
Cash Register	The cash register code of the cash register setup to be used
Provider	The provider of the voucher card system Standard: No special external provider, but an in-house solution Point4More: Interface for Point-4-More voucher cards
Active	Activates the voucher card function
Type	Defines how the voucher card should be titled on or in related buttons and messages

Settings

Click to enlarge

Campaign

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Campaign, you can configure time-limited and/or product-dependent automatic discount campaigns. This avoids the need to adjust item price lines manually for short-term promotions.

Click to enlarge

Actions

The card contains several actions, which are briefly described below:

Field	Description
Activate	Activates the campaign for all cash registers whose cash register setup allows campaigns
Deactivate	Deactivates the campaign so it can no longer be used at any cash register
Filter	Opens the filter overview for this campaign
Assignment	Opens the assignment overview for this campaign
Entries	Opens the related campaign entries
Coupons	Opens coupon management
Barcode	Opens barcode setup

Activate

This releases the campaign for use. After that, no further changes can be made to the campaign until it is deactivated.

Export Webshop Category

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method exports webshop categories including parent relationship and multilingual descriptions.

Method

Operation: CategoryExport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Optional Parameter

categoryCode_P

Response

XML with category code, parent, active/hidden flags, and description nodes.

Result

The webshop receives category tree data and translated labels.

Import Reservation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint imports reservation orders from the webshop.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Import/v2.0/companies(<company-system-id>)/webshopReservations?$expand=webshopReservationLines

Required Payload Fields

Header: webshopChannelCode, reservationOrderId, orderType, orderDate, currency
Lines (webshopReservationLines): at least one line with id, type, itemNumber, amount

Key Notes

Empty fields may be omitted in the payload.
Address and contact data can be included when required.

Result

The reservation order is available for further BC processing.

Reservations

Mon, 01 Jan 0001 00:00:00 +0000

The Reservations menu item contains all reservations that have not yet been completed.

Click to enlarge

When a reservation is selected, the related card is opened:

Click to enlarge

Cash Account Book

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Cash Account Book, you can configure predefined cash account book reasons for deposit and payout processes in the cash register system.

Click to enlarge

Actions

Only one action is available in the cash account book overview: the language-dependent translation option.

Translation

In the translation overview, language-dependent descriptions can be stored for the respective cash account book.

Click to enlarge

Setup

Field	Description
Code	The unique cash account book code
Description	Language-dependent description of the selected cash account book
G/L Account	The G/L account to be used for posting; for each cash account book, either its own G/L account or a collective/transfer account can be stored
Blocked	Deactivates the selected cash account book so it can no longer be used
Capture Text	When the cash account book reason is selected, text capture becomes mandatory and overrides the cash account book reason

Export Item Description

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes exporting item descriptions (meta title, short description, long description) per language.

Endpoints

Via item export with expand: http://<server>:<port>/<service-tier>/api/beTerna/export/v2.0/companies(<company-system-id>)/items?$filter=webshopChannelCode eq '<webshop-channel-code>' and no eq '<item-no>'&$expand=wsItemDescriptions
Direct description query: http://<server>:<port>/<service-tier>/api/beTerna/export/v2.0/companies(<company-system-id>)/wsItemDescriptions?$filter=webshopChannel eq '<webshop-channel-code>'

Required Parameters

webshopChannelCode or webshopChannel
For item export additionally no

Key Response Fields

itemNo, language, descriptionType, descriptionText

Result

The webshop receives language-specific item content for product and SEO presentation.

Import Sales Order

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method imports sales order payload from the webshop into BC import tables.

Method

Operation: OrderImport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Payload Core

webshopOrderImport_PX with header, addresses, payment data, and orderlines

Processing Logic

SOAP import performs primarily syntactic validation.
Semantic validation and document creation run in a background process.

Tax-Free Entries

Mon, 01 Jan 0001 00:00:00 +0000

Under Archive -> Tax-Free Entries, the transactions executed so far can be viewed, with faulty ones highlighted in red.

List

Click to enlarge

Field	Description
Entry No.	Unique entry number of the respective transaction
Location	The location code of the triggering cash register
Cash Register	The cash register code of the triggering cash register
Time	Date and time of the transaction
Provider	The provider used for the transaction
Transaction ID	This ID identifies related transactions
Transaction	The transaction operation
Successful	Flag indicating the success of the transaction

Card

General

Click to enlarge

Export Order Status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint provides order status history on both header and line level.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/orderStatusCodes?$filter=webshopChannelCode eq '<webshop-channel-code>' and externalDocumentNo eq '<external-document-no>'

Required Parameters

webshopChannelCode
externalDocumentNo

Key Response Fields

statusCode, documentType, documentNo, externalDocumentNo, lineNo, itemNo, systemCreatedAt

Result

The webshop can track processing status per order and line.

Import Contact

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method imports contact payload and prepares it for downstream processing.

Method

Operation: CreateOrUpdateSingleContact
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Payload Core

webshopContactImport_PX with webshopContact structure

Processing Logic

Syntactic validation at import time.
Semantic validation and create/update in follow-up processing.

POS Setup

Mon, 01 Jan 0001 00:00:00 +0000

POS Setup contains all settings that apply to the entire BE-POS module and cannot be configured individually per cash register. Setup is done under Setup → POS Setup.

Actions

Action	Description
Email Setup	Opens the standard Business Central setup for sending emails

General

Click to enlarge

Field	Description
Receipt Data Filter	You can restrict the visibility of analyses and archive tables. For example, the cash register can be configured so that only its own receipts are shown in the tables. The relevant cash register is determined via the signed-in user and the assigned cash register setup.
Location Filter for Inventory Inquiry	You can define whether the inventory inquiry should consider all locations or only locations with assigned cash registers.
Customer Type	Defines whether debtors or contacts are used at the cash register
Customer Email Check	During customer creation or editing within checkout, this setting can activate duplicate checking. If the check is active, you can define whether the cashier sees an error or only an informational message.
Contingent Visibility	You can choose whether the contingent is shown never, via a button, or directly in the list.
Suppress Item Receipt/Shipment Posting	When POS sales are posted through sales orders, no item receipt or shipment is created.
Waiting Time Between Posting POS Orders (in ms)	Specifies the waiting time between postings of POS orders, in milliseconds
Visibility of Parked Receipts	Defines which parked receipts and reservations are shown at the cash register. Available options are: Own: Only receipts of the current cash register are shown Location: Receipts of the current location are shown All: All receipts are shown
Number Series for Parked Receipts/Reservations	Stores the number series for parked receipts and reservations
Package No.	Defines whether the Package No. field in the relevant order or journal should automatically be filled with the predefined value when posting item sales/returns, for POS compatibility when package tracking is active

Email Notifications

Click to enlarge

Processed Imports

Mon, 01 Jan 0001 00:00:00 +0000

In the processed imports, you can view the finance imports that have already been posted. The journal lines before posting can be viewed in decompressed and compressed form. The links to the receipt data are also available.

Click to enlarge

Cash Register Setup

Mon, 01 Jan 0001 00:00:00 +0000

A cash register setup contains the individual configuration for its assigned cash register. This results in a 1:1 assignment between cash register and cash register setup. Setup is done under Setup → Cash Register Setup.

Click to enlarge

Actions

Several action buttons are available on the cash register setup card. They are briefly described below.

Click to enlarge

Field	Description
Initialize	Initializes the cash register setup for the current Windows user
Device Setup	Opens device setup
Receipt Text Setup	Opens receipt text setup
Copy	Copies the selected cash register setup
Store Management	Lets you manage multiple stores
Dimensions	Opens dimension management

Initialize

Defines this cash register setup for the user.

Counting

Mon, 01 Jan 0001 00:00:00 +0000

The Counting Archive can be used to view all counts performed at the cash register.

Click to enlarge

Here you can find the cash register start, the cash register closing, and interim cash counts during the day.

The Card of the respective count contains the information on target and actual amounts as well as differences.

Click to enlarge

Import Return

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method imports returns from the webshop into BC import containers.

Method

Operation: ReturnImport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Payload Core

webshopReturnImport_PX with returnOrder and returnOrderLines

Processing Logic

Syntactic validation during SOAP call.
Semantic processing and document creation in downstream steps.

Order Import API - Voucher Processing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to submit voucher lines correctly in the JSON-REST sales order import.

Relevant Endpoint

POST /api/BEterna/Import/v2.0/companies(<company-system-id>)/orders

Voucher Line Types

type = 2: voucher purchase
type = 5: voucher redemption

Core Rules

voucherCode is mandatory for both voucher line types.
For type = 5, singlePrice must be negative or 0.
subtotal is calculated without type = 5 lines.
totalAmount includes all lines, including type = 5.
Redemption total must not exceed subtotal.

Result

Voucher scenarios are imported consistently and processed correctly in BC.

Employees

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Employees, employees and employee groups are configured.

Click to enlarge

Actions

Groups

This is where employee groups are managed. This makes it possible to group discounts among employees, for example according to length of service or classification.

Click to enlarge

Actions

Apply

Applies the selected group to all existing employees. If the prompt is confirmed with Yes, the group is always applied; otherwise only employees without an existing employee group assignment are updated.

Export Sales Order History

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint provides sales order history data including line-level details.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/orderHistoryHeaders?$filter=webshopChannelCode eq '<webshop-channel-code>'&$expand=orderHistoryLines

Required Parameter

webshopChannelCode in filter

Key Response Fields

Header: webshopOrderNo, salesOrderNo, createdAt, type, postedDocumentNo, trackingNo
Lines: orderLineNo, itemNo, variantCode, quantity, lineAmount, postedDocumentLineNo

Result

The webshop receives order history for tracking and customer visibility.

Import Reservation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This method imports reservation payload including lines and address data.

Method

Operation: ReservationImport
Service: Codeunit BEConnect as SOAP web service

Required Parameter

webshopChannel_P

Payload Core

webshopReservationImport_PX with header, reservationOrder, and reservationOrderLines

Processing Logic

Syntactic validation during import.
Semantic processing in the background process.

Cross-Selling

Mon, 01 Jan 0001 00:00:00 +0000

If you want additional related products to be suggested to the customer for specific products, this can be configured under Setup → Cross-Selling.

Click to enlarge

Setup

Field	Description
Origin Type	Type of the triggering product, Item or Resource
Origin Code	Item or resource number
Type	Type of the suggested product, Item or Resource
Code	Item or resource number
Description	Description to be displayed

Export Document Status

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns processing status for a document, including error text.

Endpoint

Method: POST
URL pattern: http://<server>:<odata-port>/<service-tier>/ODataV4/<serviceName>_DocumentStatusExportOData?company=<companyName|companyId>

Required Payload Fields

webshopChannelCode
orderType
orderNo

Response

The response contains JSON in value with documentCreated and errorText.

Result

Integrations can validate whether posting was successful or failed.

Discount Reason

Mon, 01 Jan 0001 00:00:00 +0000

If the cash register is to work with discount reasons, they can be configured under Setup → Discount Reason.

Click to enlarge

Actions

Only one action is available within the discount reasons: the language-dependent translation option.

Translation

In the translation overview, language-dependent descriptions can be stored for the respective discount reason.

Click to enlarge

Setup

Field	Description
Code	Unique discount reason code
Description	Contains the language-dependent description
Type	Defines the type of discount reason Discount: Percentage reduction at line or receipt level Reduce: Absolute reduction at line or receipt level New Price: Assignment of a new sales price at line level No Price: Item without price at line level Free: Sets the sales amount to 0 and can be applied as a discount, reduce, or new price at both line and receipt level
Usage	Defines where it can be used Line: At line level Receipt: At receipt level Line & Receipt: At line and/or receipt level
Value	Defines a value (percentage or absolute; if no value is specified, it is requested manually during the cash register process)
Print	Controls the print mode Never: The discount reason is not printed Code: The discount reason code is printed Description: The discount reason description is printed
Employee Discount	Allows assigning the discount to an employee purchase

Export Dynamic Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes exporting dynamic attributes including value and language datasets.

Endpoints

Attributes: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/dynamicAttributes
Attribute descriptions: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/dynamicAttributeDescriptions?$filter=webshopChannelCode eq '<webshop-channel-code>' and dynamicAttributeSystemId eq <dynamic-attribute-system-id>
Attribute values: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/dynamicAttributeValues?$filter=dynamicAttributeCode eq '<dynamic-attribute-code>'
Value descriptions: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/dynamicAttributeValueDescriptions?$filter=webshopChannelCode eq '<webshop-channel-code>' and dynamicAttributeValueSystemId eq <dynamic-attribute-value-system-id>

Key Response Fields

Attributes: dynamicAttributeCode, filter, show
Values: dynamicAttributeValueCode
Descriptions: language, text

Result

The webshop receives structured attribute and translation data for product presentation.

Export Branch Inventory Item Variant List

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint returns item variants with branch inventory changes since the last synchronization.

Endpoint

Method: GET
URL pattern: http://<server>:<port>/<service-tier>/api/beTerna/export/v2.0/companies(<company-system-id>)/branchinventoriesItemVariantsList?$filter=webshopChannelCode eq '<webshop-channel-code>' and branchinvSentToWebshop eq false

Required Parameter

webshopChannelCode in filter

Key Response Fields

itemNo, variantCode, branchInvSentToWebshop, lastBranchStockChangeAt

Result

This list is used as a high-performance trigger for detailed branch inventory requests.

Regional

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Regional, country-specific configurations can be made.

Note: No check is performed regarding the necessity or legal feasibility of the respective settings; responsibility lies solely with the user.

General

Click to enlarge

Field	Description
Location	The location code of the cash register (if left blank, the settings apply to all cash registers)
Cash Register	The cash register code of the cash register (if left blank, the settings apply to all cash registers of the location)
Country/Region Code	The country code of the cash register(s) for legally compliant cashiering

Total Rounding

Click to enlarge

Export Branch Inventory

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This endpoint provides per-branch inventory for one item including variant structure.

Endpoint

Method: GET
URL pattern: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/branchInventories?$filter=webshopChannelCode eq '<webshop-channel-code>' and no eq '<item-no>'&$expand=branchItemVariants($expand=branchLocations)

Required Parameters

webshopChannelCode in filter
no (item number) in filter

Key Response Fields

Header: webshopChannelCode, no
Variants: code
Branch data: code, inventory, calculationTimeStamp

Result

The webshop receives branch-level availability data.

Resource

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Resource, different services can be created for the cash register. They are based on the standard resources and extend them with POS-specific properties.

Click to enlarge

Actions

Translation

In the translation overview, language-dependent descriptions can be stored for the respective resource.

Click to enlarge

Setup

Field	Description
No.	Number of the service
Description	Description of the service
Product Posting Group	The product posting group to be used
VAT Product Posting Group	The VAT product posting group to be used
Invoice Discount Allowed	Allows the application of receipt discounts/reduces
Line Discount Allowed	Allows the application of line discounts/reduces
Assignment Exists	Indicates that a cash-register-master-specific assignment exists
Capture Text	Allows the description of the resource to be overwritten

Export Free Text Attributes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes exporting free text attributes and their translations.

Endpoints

Free text attributes: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/freeTextAttributes
Free text attribute descriptions: http://<server>:<odata-port>/<service-tier>/api/BEterna/Export/v2.0/companies(<company-system-id>)/freeTextAttributeDescriptions?$filter=webshopChannelCode eq '<webshop-channel-code>' and freeTextAttributeSystemId eq '<free-text-attribute-system-id>'

Required Parameters

For descriptions: webshopChannelCode and freeTextAttributeSystemId

Key Response Fields

Attributes: code
Descriptions: language, text

Result

The webshop receives free text content fields with language-specific labels.

Quick Selection

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Quick Selection, quick-selection options can be stored for various cash register states.

Note: Up to 12 quick buttons can be stored per category.

Tender

Allows storing tenders; these can be selected during the payment process of cashiering.

Click to enlarge

Customer

Allows storing customers/contacts; these can be selected during customer login within cashiering.

Click to enlarge

Reduce

Allows storing reduce reasons; these can be selected within cashiering for both line-level and receipt-level reduces. It is also possible to define a start and end date from or until which the respective reason is valid.

Backup

Mon, 01 Jan 0001 00:00:00 +0000

The backup feature makes it possible to export and import specific data.

Click to enlarge

Actions

Initialize

Initializes all tables available for the current configuration, depending on the selected mode.

Execute

Executes the current configuration by exporting data as a ZIP folder to Downloads or importing it via manual file selection.

Admin Mode

Provides access to the password-protected administrator mode, which grants access to protected functionalities.

Setup

General

Click to enlarge

Tax Free

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Tax Free, you can configure the country-specific VAT refund process for tourists.

Setup

General

Click to enlarge

Field	Description
Location	The location code of the cash register to be used
Cash Register	The cash register code of the cash register to be used
Provider	The tax-free provider Global Blue: The Global Blue interface is used
Active	Activates the tax-free setup for use during cashiering

Settings

Click to enlarge

Terminal

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Terminal, you can configure card terminal settings per cash register.

Click to enlarge

Actions

The following actions are available both in the overview and on the card:

Field	Description
Card Assignment	Starts a test transaction with the currently stored settings
Copy Direct Debit Text	Distributes the direct debit text of this setup to all other terminal setups.
Test Transaction	Starts a test transaction with the currently stored settings

Card Assignment

In this overview, you can assign a corresponding card to each return value of a terminal protocol. Under Setup → Tender, you can assign the stored card types to individual card tenders.

Sound

Mon, 01 Jan 0001 00:00:00 +0000

Audio feedback is set up under Setup → Sound. The setup can be controlled individually per cash register setup, per location, or across all cash registers.

Click to enlarge

Events

Several events are available on the sound setup card and are briefly explained below:

Field	Description
Item Captured	When an item has been captured correctly
Receipt End	When the receipt has been completed in full
Error Message	When an error message appears
Item Not Found	When an item has been captured but could not be evaluated correctly

Sounds

Several sound types are available on the sound setup card and are briefly explained below:

Salesperson

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Salesperson, the salespeople and salesperson rights are maintained.

Click to enlarge

Actions

Several action buttons are available in the salesperson overview and are briefly introduced below.

Field	Description
Change Password	Changes or sets the password for the selected salesperson
Delete Password	Removes the password stored for the selected salesperson
Groups	Opens group management

Change Password

This action opens a new window in which the old and new password, including confirmation, must be entered. Selecting OK applies the new password and stores it in encrypted form for the relevant salesperson. Password entries are only required for cashier and supervisor sign-ins, but not for changing the salesperson.

Tender

Mon, 01 Jan 0001 00:00:00 +0000

Under Setup → Tender, the tenders available for the relevant cash register setup are configured.

Click to enlarge

Actions

Several action buttons are available in the tender overview and are briefly introduced below.

Field	Description
Store Management	Enables the management of multiple stores
Denomination	Stores the denominations for cash tenders
Translation	Stores the language-dependent description for the selected tender
Card Assignment	Opens an informative overview of the terminal-dependent card types
Tender Check	Allows selected tender types to be assigned specific check criteria

Translation

In the translation overview, language-dependent descriptions can be stored for the respective tenders.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the recommended initial setup of a new BE-terna Project client in the Business Central Client.

Prerequisites

Access to an existing tenant with permission for function management
Permission to create new companies
Decide whether to import initial data or demo data

Order

Activate the function update “New Sales Price Calculation” in the function management.
Create a new company in the client list with “Create new - No data”.
Switch to the new tenant and start the setup.
Import initial data or demo data.
Then schedule the data update for the sales price calculation in the new client and check the closing status.

Decision support: initial data or demo data

Initial data: Technical and functional basic structure without additional demo documents
Demo data: Initial data plus additional sample master data and sample operations

Note: After importing initial or demo data, a reset in the same client is not provided. A new client is created for a different data status.

Process Catalog

Mon, 01 Jan 0001 00:00:00 +0000

Process Setting up a new client for BE-terna Project Create a company, start the setup and define the database. +

Use the guided process in the new company to import initial or demo data in a controlled manner. Then check the necessary data update so that price calculation and follow-up processes work stably.

Process Control projects via the Role Center Use project lists and project cards as central workspaces. +

Open projects via search, tiles or bookmarks and control further editing via project list and project card. In this way, planning, purchasing and evaluation functions remain in a consistent process.

Process Reconcile project documents and costing Document entry, pricing and controlling in a coordinated process. +

Connect document processing, price shares, and award logic with project-specific evaluations. This reduces media disruptions and improves the traceability of changes in results.

Process Prepare and close project accounting Carry out invoicing in a controlled manner with printing and checking options. +

Use standardized verification and approval steps before final invoicing, including surcharge and instalment checks. Document deviations directly in the process.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ When do I use initial data instead of demo data? Initial data is suitable for a neutral start without sample data. +

Use initial data if you want to build setup, roles, and processes without sample business data. Demo data is usually better suited for training, demos and early process runs.

FAQ Can I undo the data import in the same client? A reset of the already filled client is not planned. +

If initial or demo data has already been imported, create a new company for a clean rebuild.

FAQ Where do I start my daily work in BE-terna Project? Central access is via Role Center, Project List and Project Card. +

Open the project overview via the Role Center and switch from there to the project card for detailed work, actions and evaluations.

Be-terna Product Documentation on Product Documentation

Archive

Version 27.1.0

Summary

27.1.0 — 2026-02-10

New features

Bug fixes

Assisted Setup

Purpose

Prerequisites

Recommended Sequence

Setup Steps

Channel Basics

Base Setup

General

Demo

Version BC 22

Summary

22.0.3 — 2023-08-30

Bug fixes

22.0.2 — 2023-07-27

New features

22.0.1 — 2023-07-17

New features

Other changes

22.0.0 — 2023-07-10

Other changes

BE POS Listener Setup

Download

Installation

Communication

BE-terna Project License

Cash Register Closing Report

Cash Register Start

Cashier Sign-In

Drop shipment

Purpose

Business value

Focus areas

Auto-post orders

Import local detail view control

Installation

Goal of the setup

Prerequisites

Recommended sequence

Setup steps

Prepare the SaaS tenant

Intercompany setup

Purpose

Prerequisites

Recommended order

Setup building blocks

Document line comments

Interface

Actions

Copy Template

Item tracking

Purpose

Business value

Focus areas

Inspect tracking on IC documents

JSON-REST Interfaces

Purpose

Scope

Guardrails

Order confirmation

Purpose

Business value

Focus areas

Flow

Overview

Overview

Purpose

Business value

Functional focus

Unified HTTP GET interface

Overview

Purpose

Business value

Functional focus