Skip to main content

Report generator and smaller office functions (Büro: Reports, Kassenbuch, Zahlungsverkehr, Payback, Wertgutscheinverwaltung, IXOS.campus, MEP24web)

1. Purpose and scope​

This chapter covers the back-office ("Office", Büro) menu of the pharmacy system apart from the analytics cockpit, the fixed evaluations (Auswertungen), DMS, DATEV and the documentation registers, which other chapters cover. It describes:

  • Reports (formerly "combined evaluation", Kombi-Auswertung): an ad-hoc query builder for every part of the merchandise-management system. Users run predefined queries or build their own from a field catalogue, with conditions, operators, time windows, reusable parameters (variables), aggregate filters, calculated columns, grouping and drill-down, column totals and result limits. Result lists can feed mass actions (ordering, returns, price and stock-parameter changes, labels, customer flags, coupons, accounting accounts and so on). They can also be printed, exported (PDF, Excel, CSV, cloud download link, OData feed), scheduled as recurring tasks (open, print, e-mail, export) and reused as dynamic customer selections by other modules. Results can span the branches of a pharmacy group. A licensed layer adds management reporting: the MMR overview of business-management reports, each linked to drill-down work lists.
  • Cash book (Kassenbuch): a tax-compliant cash ledger derived from the daily till closings, with an opening balance, carry-over, current cash balance, cash withdrawals (bank deposit or private withdrawal), correction bookings, filtering and a printed report for the tax advisor.
  • Payment transactions (Zahlungsverkehr): SEPA direct-debit collection of till and invoice receivables. It covers mandate prerequisites, export of bank files, automatic due-date correction, accepting and rejecting debits, return codes, re-collection, mandate revocation side-effects and regeneration of lost files.
  • Value-voucher administration (Wertgutscheinverwaltung): the lifecycle of stored-value gift vouchers (statuses, search, clean-up of unredeemable balances into income, history, cross-pharmacy settlements).
  • Payback: link to an external coalition loyalty programme (point accrual rules, daily transfer to a service centre, transfer statistics).
  • IXOS.campus (training portal), MEP24web (external staff-scheduling link) and the Office menu itself (list of office modules and web portals).

2. Key concepts and terms​

German termEnglishMeaning
Reports / Kombi-AuswertungReport generatorModule for predefined and user-built database queries.
AbfrageQueryA saved report definition: result category + conditions + result columns + variables + layout.
ErgebniskategorieResult categoryThe entity type a query returns (articles, customers, employees, suppliers, vendors, goods receipts, credit notes, sales, pharmacies/branches).
Abfrage-KlassifikationQuery classificationFolder that groups queries (predefined or own).
Vordefinierte / Eigene AbfragenPredefined / own queriesQueries shipped by the vendor versus user-built ones.
Feld / Feldkategorie / FeldklassifikationField / field categoryAn attribute or key figure of the result type, grouped in categories (e.g. "article identification", "sales – revenue", "storage – new creations", "price information").
BedingungConditionA field used as a filter on the result rows.
BedingungsfensterCondition windowField-type-specific dialog in which a condition's values are set.
AbfragekriteriumQuery criterionA condition value shown (and possibly changeable) above the result.
VariableVariable / parameterA named criterion that can be changed in display mode and shared across conditions, columns and filters of one query.
AnpassungAdjustmentA per-usage relative shift of a variable (e.g. the same period two years earlier).
Weitere Filterung / SummenfilterFurther filter / aggregate filterRestriction of what is summed in a quantity or amount field (e.g. revenue only from prescription sales).
AngleichenAlignPropagating an identical definition change to all other conditions and columns that share it.
ErgebnisspalteResult columnA field shown as a column in the result.
Berechnete SpalteCalculated columnA column computed from two values.
Gliederung: Gruppierung / Auffächerung / ZeiteinteilungOutline: grouping / fan-out / time divisionHierarchical consolidation (left of the object), detail breakdown of a cell (right of the object), or a breakdown by time slices.
Anzeigemodus / BearbeitungsmodusDisplay mode / edit modeRunning queries and changing their variables / building and changing queries.
Einfach / KomplexSimple / complex modeImplicit AND list of conditions / explicit "and also" and "but not" blocks.
Ergebnis verarbeiten / ErgebnisverarbeitungResult processingMass actions on selected result rows.
VerarbeitungsgruppeProcessing groupGroup of mass actions in the result-processing dialog.
Vorgangsansicht / PositionsansichtTransaction view / line viewTwo views of sales results (header level / line level).
Vorgangskette / AuftragsketteTransaction chain / order chainLinked receipts created when a completed till sale (chain) or invoice order (chain) is later edited, resolved or cancelled.
Aktuell gültiger BelegCurrently valid receiptFlag selecting only the latest receipt of a chain.
Interaktive Aufgabe / AufgabenserieInteractive task / task seriesScheduled job in the Notes module that opens, prints, mails or exports a query.
Download-Link / OData-DatenfeedCloud download link / OData feedCloud-hosted export of a result, as a one-off file or a refreshable feed.
Kundenselektion / KundenlisteCustomer selection / customer listA dynamic, query-based customer set versus a static hand-picked set.
MMR (Management-Report)Management reportLicensed business-management reporting; reports are coded like M1, M2, P4, B2.
MMR-ArbeitslisteMMR work listActionable drill-down list linked to a management report.
MMR-ProzesskategorieMMR process categoryStocks, processes, employees, selling, assortment, customer.
Umsatzrelevante AbfrageRevenue-relevant queryQuery whose results only revenue officers may see.
KassenbuchCash bookCash ledger derived from till closings.
Z-Bon / S-BonZ-receipt / S-receiptTill closing report that resets totals (daily closing) / summary report without reset. Their exact semantics are described in the till chapter.
AnfangsbestandOpening balanceCounted cash at cash-book start.
ÜbertragCarry-overCash still in the till at the start of the evaluated period.
KassenbestandCash balanceExpected physical cash at the end of the period.
Auszahlung: Bankeinzahlung / PrivatentnahmePayout: bank deposit / private withdrawalCash taken out of the tills.
KorrekturbuchungCorrection bookingManual correcting entry in the cash book.
ZahlungsverkehrPayment transactionsSEPA direct-debit module.
LastschriftDirect debitCollection order against a customer's bank account.
Mandat / MandatsreferenzMandate / mandate referenceThe customer's signed debit authorisation and its identifier.
Sequenztyp FRST / RCUR / FNALSequence typeFirst, recurring or final debit under a mandate.
Gläubiger-IDCreditor identifierThe pharmacy's SEPA creditor ID.
RückgabecodeReturn codeThe bank's reason code for a returned debit.
WertgutscheinValue voucherPrepaid stored-value voucher (gift card).
BereinigenClean upWrite off a voucher's remaining balance to pharmacy income.
WertgutscheinverrechnungVoucher settlementInter-pharmacy settlement when a voucher of pharmacy A is redeemed in pharmacy B.
Kulanzpunkte / AktionspunkteGoodwill points / promotion pointsExtra loyalty points (manual goodwill / from coupons or marketing codes).
ASC (Apotheken Service Center)Pharmacy service centreWholesaler-run intermediary that validates loyalty transactions and forwards them to the programme operator.
Verbund / Filiale / PartnerapothekePharmacy group / branch / partner pharmacyMulti-pharmacy organisation.
UnternehmenssteuerungCorporate controlRole allowed to evaluate across the group.

3. Data model​

3.1 Report generator​

ResultCategory (fixed enumeration): Articles, Customers, Employees, Suppliers, Vendors (manufacturers/providers, Anbieter), Goods receipts, Credit notes, Sales, Pharmacies/Branches. Each category has its own field catalogue, its own processing groups and its own detail module.

QueryClassification: name; kind (predefined or own). Own classifications can be renamed, and own queries can be moved between own classifications.

Query

  • id, name, classification, result category, owner kind (predefined or own).
  • description: free text; the default text lists all evaluated criteria.
  • mode flags: simple or complex condition mode.
  • conditions[] (see Condition), result columns[], variables[], outline definition, column footer aggregates, row limit (first N / user-defined N), column order, widths and labels, sort.
  • visibility flag "visible only to revenue officers" (default off).
  • group exchange flag: shared with the pharmacy group. Sharing is irreversible and checked for duplicates.
  • licence tag: basic, Profi, MMR or Cockpit Profi (controls availability).
  • For MMR queries: a code of the underlying management work list or graphic (e.g. M1, M2, P4, B2), the MMR process category, the report-or-work-list type, and links to related work lists and "similar" queries.
  • Export format: a file with extension .abfrage that carries the category (sub-folder).

Field

  • name; field category; data type (text, number/amount, quantity with unit, yes/no, enumeration, hierarchical enumeration, date, period aggregate "… im Zeitraum", point-in-time value "… zum Zeitpunkt", price/discount).
  • capabilities: usable as condition and/or column (e.g. sales "unit/pack size" is column-only); supports further filters (quantity and amount fields); supports price comparison (price-information fields); calculable (quantities, prices, percentages).
  • level for Sales: transaction, subtotal or line. A line field has the suffix "per line" (zur Position) and may have a corresponding transaction field.

Condition

  • field; operator/values according to type (value set, "any value", "don't care", "is not set", ranges, text match "matches/contains", quantity + unit, period option, point-in-time option, expiry-date option, price comparison).
  • active flag: can be deactivated for testing.
  • block in complex mode: base, "and also", or "but not / and also not".
  • multi-selection: an OR list of several sub-conditions on the same field.
  • further filters (by filter category); linked variables; adjustments.

Variable

  • unique name within the query (default = condition name); description (tooltip); type (value or period/point in time) and current value.
  • usages[]: the conditions, columns and further filters bound to it.
  • It exists only while it has at least one usage and is deleted automatically otherwise. Scope is one query.

VariableAdjustment (per usage): mode (same period shifted back / partial period / arbitrary relative period / value offset) and parameters (unit, shift span, anchor at start or end of the current period).

FurtherFilter (aggregate filter) set on a quantity or amount condition or column: filter categories and their criteria (§4.1.7). Filter groups are compared as a whole when aligning.

ResultColumn: field or calculated definition; properties (period, price basis, price comparison, further filters); user label (up to five lines; optional appended date info); width; position; footer aggregate (sum, average, min, max, count empty, count non-empty, count yes/no, count per value). For Sales: which view the column belongs to.

CalculatedColumn: operand 1 (column or potential field with its settings); operation family and operator; operand 2 (column/field, constant value, or averaging period). It is independent of later changes to its source definitions.

Outline: up to three groupings and three fan-outs. Each element is a column, or a further-filter criterion of a summed column, or a time division (weekday, month, calendar month, calendar quarter, quarter, year). Other settings: sort direction and "hide empty outlines".

ScheduledReportTask (stored in the Notes task system)

  • subject (query name), description, a frozen snapshot of the variable values.
  • action: open / auto-print / auto e-mail / auto-export PDF / Excel / CSV.
  • start, end, all-day flag; recurrence (once, daily, weekly, monthly, quarterly, yearly, plus pattern).
  • assignee (employee or whole pharmacy) and deputy (open action only); priority.
  • print-legend flag; CSV-headers flag; fixed export path or default temporary directory.
  • e-mail address (defaults from company master data) and optional encryption password.
  • state: active or done.

ExportLink: format (PDF, XLSX, CSV, OData); access protection (on by default, generated password, user name "reports" for OData); availability (download link valid one month; OData with daily refresh or no refresh); link URL; usage protocol; the associated task series (auto-closed when availability ends).

CustomerSelection: name, description, type (report query = dynamic, or customer list = static), the query reference or the list of customer ids. A process can combine several selections.

3.2 Cash book​

  • CashBookSetup: opening balance (≥ 0), validity start (date + time; may lie before or after today but not before the installation or migration date). It is entered once, on first start.
  • CashBookEntry (derived from till closings, plus manual entries): date, voucher number (Beleg-Nr.), running number, income amount (positive) or expense amount (negative), booking text (generated, optionally with the remark appended), link to a DMS document.
  • Payout: type (bank deposit / private withdrawal), amount (> 0, no negatives), booking date (default today; may be back-dated no earlier than the cash-book start).
  • Correction booking: exists, but is described on a page outside this slice.
  • Period view state: evaluated period from/to (from 00:00 of the start day to 24:00 of the end day), last printed period from/to, carry-over, cash balance, active filter criteria.

3.3 Payment transactions (SEPA)​

  • Customer prerequisites (contact management, payment page): bank account with direct debit enabled (IBAN, BIC); SEPA mandate (reference, signed, status active or revoked); payment method on the invoicing tab = direct debit.
  • DirectDebit: origin (till or invoicing); customer; mandate reference; receipt or till-receipt number; receipt date-time (for till sales, the time of the total closing with payment type direct debit or immediate invoice); due date (proposed by the originating module); amount; sequence type (FRST/RCUR/FNAL); state (open, locked, exported, accepted, not accepted, re-exported, cancelled in sales management); return code; history of re-exports (same receipt number).
  • SepaFile: export timestamp, file name (export date-time, creditor IBAN, sequence type, execution date), folder (timestamped), free-text remark, total amount, contained debits.
  • Formats: IBAN up to 35 characters (2-letter country, 2 check digits, up to 30 alphanumeric account identifier; for Germany bank code + account number; displayed in blocks of four); BIC with 8 or 11 characters; creditor ID up to 35 characters (2-letter country, 2 check digits, 3-character business code, up to 27-character national identifier).

3.4 Value vouchers​

  • ValueVoucher: internal number and external (alphanumeric) number with barcode; issuing pharmacy (origin); issue date; expiry date (optional); balance; status; linked sales transactions.
  • Status enumeration:
    • Pre-captured (Vorerfasst): the sale of the voucher is not finished.
    • Issued (Ausgestellt): sold; balance available.
    • In processing (In Bearbeitung): the voucher sale was reopened for editing and not yet closed.
    • In redemption (In Einlösung): captured in a sale as a means of payment.
    • Fully redeemed (Vollständig eingelöst).
    • Cancelled (Storniert): cancelled within the voucher sale.
    • Cleaned up (Bereinigt): remaining balance moved to pharmacy income; no longer redeemable.
  • VoucherHistory: every status change with a timestamp.
  • VoucherSettlement (cross-pharmacy): created when another group pharmacy redeems one of this pharmacy's vouchers. Fields: date-time, details, cancelled flag, DMS document.

3.5 Payback (external loyalty)​

  • PaybackModel: name, valid from/to (date + time), points, per euro amount, article range, active flag. The standard model is fixed and cannot be edited.
  • PaybackTransaction: receipt number, eligible revenue, 13-digit card number, base points, goodwill points, coupon number, promotion points, feedback/error type.
  • PaybackTransfer: transfer number, date, time, status (success without errors / success with errors / pending / sent with no feedback yet / failed), feedback text, totals of points and promotion points.
  • Configuration: user ID, password, server address of the service centre.

3.6 Training portal​

Course (active or completed), learning progress per user, pharmacy-wide list of completed courses, printable certificates.

4. Features​

4.1 Report generator (Reports) [GENERIC]​

4.1.1 Module layout and modes​

  • Purpose: answer any question about the merchandise-management data without programming, then act on the answer.
  • Access: desktop and Office menu. Other modules that use report queries (e.g. customer selections) can open edit mode via "edit selection".
  • Layout and navigation:
    • Several queries can be open at once as tabs; a "+" tab opens a new query selection.
    • Result-category selector.
    • Query browser: search box (with two terms, both must match), predefined and own classification trees, licence badges (MMR, Cockpit Profi).
    • Above the result: the query description and the changeable criteria.
    • The result grid and a function bar.
    • The vendor recommends full-screen use. In full screen the result covers the category and query panes.
  • Display mode (default when the module opens): run queries and change only the criteria that the author exposed as variables.
    • Multi-value criteria appear as a link (e.g. a period, or "stock status = POS and POR").
    • Single-value criteria appear as a drop-down (e.g. "MMR article exclusion", "standard pack size = N1").
    • Every criterion has a tool icon that opens its condition window. In display mode the window offers only what the author allowed.
  • Edit mode (licensed) has four areas:
    • Field list: categories and a search.
    • Conditions pane: the query definition. These conditions are invisible and unchangeable in display mode unless they are variables.
    • Variables pane: shows the variables as they will appear in display mode.
    • Result pane.
    • Extra functions: simple/complex toggle, save, end editing (saves changes).
  • Special criterion values:
    • <all with value>: the field is non-empty.
    • <don't care>: no restriction; rows with and without a value.
    • <is not set>: the field is empty.
  • Refresh: results are recomputed whenever a query is opened, created or edited. A manual refresh exists for when the module has been open for a long time.
  • Other functions in the function bar:
    • "Query done" opens the interactive appointment, so that a task run manually from Notes can be marked as done.
    • "<Category> details" opens the record in its owning module.
    • "Process result" (§4.1.14).
    • "Create task in Notes" (§4.1.17).
    • Print and the exports (§4.1.18).
    • Greyed-out functions are unavailable in the current mode or editing state.
  • Workstation usage flag: the configuration parameter "usage of till" (Nutzung der Kasse) marks a till placed in the back office as "back-office till", and a secondary workstation placed at the counter as "secondary workstation in front office". Without this, sales would be attributed to the wrong area and distort front-office metrics such as service level (delivery readiness) and customer frequency in Reports and the cockpit.
  • Data retention in groups: sales data of partner pharmacies is deleted after three years.

4.1.2 Running a query​

  1. Pick the category, then pick a query from search, the predefined tree or own queries.
  2. The description, changeable criteria and results appear.
  3. Change a variable through its link or tool icon (opens "change <field>"), or through its drop-down, and confirm. The result refreshes.

4.1.3 Creating and editing a query (edit mode)​

  1. Choose the category, then "New query" (or "Edit query" on an own query, or start from a predefined query and save as own).
  2. Expand a field category (e.g. "Sales – revenue") or search for a field.
  3. Drag the field into the conditions pane, or use the context menu "Add as condition". The field-specific condition window opens (§4.1.4).
  4. Set the values (e.g. gross revenue 50–100 €, period "last month"). Optionally add further filters (§4.1.7) and turn values into variables (§4.1.8).
  5. Repeat for every condition. Switch to complex mode for AND / AND NOT blocks (§4.1.5).
  6. Add result columns by dragging fields into the grid or with "Add as result column". New columns are appended on the right. Remove columns by dragging them out or with "Delete column".
  7. Deactivate a condition with its checkbox to test its effect; the result updates immediately. The vendor advises saving with all conditions active. Delete a condition with its delete icon.
  8. Save the query with:
    • name, classification and description (overwrite or extend);
    • optional "exchange query in group" (duplicate check; irreversible);
    • optional "visible only to revenue officers". This is off by default, so every operator can run the query. The author decides whether the query is revenue-relevant, including indirectly through arithmetic on non-revenue fields.

Default rule: a new article query starts with the condition stock status = POS and POR, so that only stocked articles are evaluated (§6).

Relative periods in saved queries are recalculated at every run; "last month" always means the month before the execution month. Absolute dates are stored as they are. In general only relative periods make sense in saved queries.

4.1.4 Condition windows and operators​

Each field type has its own condition dialog:

Field typeInputs and semantics
Simple list / yes-noCheckbox per value. The header checkbox selects all (shown as <all with value>). All + "show results without value" gives <don't care>. Header unchecked + "without value" gives <is not set>. Some values + "without value" gives those values or empty.
Fixed values with searchA search term filters the list (substring). Composite values are shown (e.g. vendor number + vendor name). A second search adds hits while earlier selections stay. Hierarchical values (storage locations, product-group keys): expand levels; selecting a child automatically includes its parents.
Free text ("matches" / "contains")"Matches": prefix match. For customer names the match is phonetic-tolerant, so a term like "may" also finds "mei", "mai" and "mey", as in contact search. "Contains" or a leading *: substring anywhere.
Quantity with unitOptional amount in the formats 100, 3x3, 3x1,5, plus a unit from a list; the unit alone is allowed (e.g. pack size).
Period aggregate ("… in period")Key-figure value (lower bound, open upper end) or a range, plus a period option (§4.1.6). Special case: plain date fields such as "co-payment exemption until" select records whose date falls in the period, or that have no value.
Point in time ("… at point in time")Value or range, plus a point option: the period containing the point (current / exactly N units ago / fixed date, default yesterday) and the position within it (start, same position as today, middle, end).
Reference-value listChoice of basis, e.g. price basis = purchase price (EK), selling price (VK) or stock value at a point in time; future points in time for overstock fields; new-creation options for "storage – new creations" fields.
Expiry dateRelative ("expires within N months/years from today"), absolute from/to (either end may stay open), or "articles without expiry date".
Multiple selectionAdds OR-combined sub-conditions on the same field; the result widens.
Price comparisonFor price and discount fields. Operator: greater, less, at least (≥), at most (≤), equal, not equal. A comparison price or discount (e.g. pharmacy purchase price from the drug database, vendor discount), a ± percentage surcharge and a ± euro surcharge. Formula in §6.
Further filtersAvailable on quantity and amount fields (§4.1.7).
"Show results without value"Adds empty rows; display mode shows <is not set>.

A condition becomes changeable in display mode only if it is defined as a variable (icon next to the value).

4.1.5 Simple and complex condition logic​

  • Simple mode: conditions are listed one after another and all must hold (AND).
  • Complex mode:
    • Fields dragged into the "and also" area add a required condition.
    • Fields dragged into the "but not" area exclude matching rows. Several exclusions are allowed; from the second one on, the block is labelled "and also not".
    • A condition in an "and also" block can be a variable, so it stays adjustable.
  • Within one field, "multiple selection" gives OR.
  • In complex mode the outline row is shown by default.

4.1.6 Time windows​

The evaluation horizon is at most ten years back, for periods and for points in time.

Relative period options:

  • More than N days ago: everything up to N days ago (shown as "until N days ago (<date>)").
  • Exactly N units ago: one completed unit. Example: in November, "exactly 1 month ago" = October.
  • In the last N units: the N completed units before the current one. Example: in April, "last 2 months" = March and February.
  • Between the last N and M units: example, in November, "between the last 3 and 6 months" = May to August. A start of 0 includes the current, incomplete unit.
  • In the next N units: future periods. Example: in November, "next 2 months" = December and January. Intended, for instance, for dunning that falls due in future.
  • Absolute period: from/to dates; the default is the next 30 days. Not recalculated.

Rules for relative periods:

  • They always refer to completed units (hour, day, week, month, quarter, year), so "in the last …" starts from the last complete interval.
  • Hour example: at 09:48 the last full hour is 08:00–09:00, and the current hour is excluded.
  • Days, weeks, months and so on behave the same way.
  • They are recalculated every time the query is run.

Point-in-time options:

  • Current (today, current week …), exactly N units ago, or a fixed date (default yesterday; stays fixed when saved).
  • Position for week, month, quarter or year: start, same position as today, middle, end. "Same position as today" is recalculated relative to the run date, e.g. "the same day of the month as today".

4.1.7 Further filters (aggregate filters)​

  • Purpose: restrict what a summed quantity or amount field aggregates, e.g. revenue only from transactions of type "Total", or only for a customer group.
  • Key rule: further filters change the VALUES in the result, not the SET of result rows. The rows are determined by the conditions.
  • Filter categories (only the supported ones are shown per field):
    • General defaults of the condition.
    • ABC analysis of articles (e.g. ABC class by unit sales).
    • Article price and calculation (e.g. how the price was determined: manual, calculated …).
    • Article attributes (e.g. dispensing rule / prescription status).
    • Article classifications (e.g. article flags; only if classifications exist).
    • Suppliers (e.g. is main supplier).
    • Customers (e.g. address, city; "is walk-in customer", "is person").
    • Customer profile group (disease or indication groups such as allergy sufferers or thyroid patients, for articles and customers; MMR Profi licence).
    • Employees (name).
    • Sales or sale lines (line type, sale type, transaction type).
    • Goods receipts (order type).
    • Returns (return reason, return originator).
    • Stock and order control (e.g. manual stock corrections in period).
    • Opening hours in period (Pharmacy/Branches only: weekday, closed yes/no/any).
    • Cross-selling (is a cross-selling recommendation, name of the source group).
    • Pharmacies/Branches (branch selection, §4.1.15).
    • Order lines (e.g. "branch & partner sourcing" to exclude or isolate internal transfers between branches).
    • Time division (for fan-outs).
  • Restriction: a further filter cannot add a second period on top of the condition's own period (applies to all categories).
  • Display: the filtered criterion gets the suffix "(filtered)", with the filters listed in its tooltip. Columns aligned to the same filter get a filter icon. Activated filter categories and categories containing variables are highlighted differently.
  • Reset all special filters removes all further filters, including those bound to variables. The user is asked whether aligned conditions and columns should be reset too.
  • The vendor warns that many conditions with many further filters quickly become hard to interpret.

4.1.8 Variables (query parameters)​

  • Purpose:
    1. expose criteria for change in display mode;
    2. share one reference (typically a period and a comparison period) across many conditions, columns and further filters, so that a single change keeps all comparable columns consistent.
  • Create: in a condition window, choose "new variable" next to a value.
    • The name defaults to the condition name and must be unique; a clash forces a new name.
    • Description (shown as tooltip), value.
    • For period variables, a usage list of all conditions, columns and filters where the variable can apply. A master checkbox shows none, some or all.
    • Variable-bound criteria are visually marked.
    • The usage list shows every technically possible linkage, including text fields such as article name, short name, customer name, city and street across filters. The user must pick only meaningful ones.
  • Use existing variable: when adding a new condition, column or filter, bind it to an existing variable of the same value or period type; its settings are taken over.
  • Edit: name, description, value and usages, from the variables pane or the condition's context menu.
  • Remove usage: the criterion becomes independent again. If it was the last usage, the variable disappears from display mode and is deleted.
  • Lifetime and scope: a variable exists only while it is used, and only within its own query (it is not system-wide).
  • Adjustments (per usage, not changing the variable itself):
    • Same period shifted back: e.g. the current month two years ago.
    • Partial period: e.g. the first two weeks of the current month, or the third week. Parameters: "a whole <unit>" (may be larger than the current period), "shifted by <span>", "from the start or end of the current period". A preview shows the result.
    • Arbitrary relative period (complex mode): any time slice relative to the variable's period, shifted into the past.
    • Value offset relative to the current value.
    • Created via "new adjustment" in the context menu or from the variable's usage list. Also "edit adjustment" and "remove adjustment" (which reverts to the variable's value).

4.1.9 Aligning definitions (Angleichen)​

  • When a definition of a condition or column changes (period, price comparison, price basis, further filter, or activation of a further filter group), the system lists all other conditions, columns and calculated columns with an identical definition and offers to change them all in one step.
  • Equality rules:
    • Price comparisons are equal only if comparison field, operator, € surcharge and % surcharge all match.
    • Filter groups (customer filter, employee filter …) are compared as a whole. Example: one field changed "is walk-in customer" and another changed "is person", so the two customer filters are not equal. If both only set "is walk-in customer = yes", they are equal.
  • It applies only to explicit changes, not to newly created definitions.
  • In the Sales category, a change in the visible view also asks about matching items in the hidden view.

4.1.10 Result columns, totals and limits​

  • Reorder columns by dragging; sort by clicking the header; adjust width (saved with the query and used in Excel and PDF output); delete by dragging out or from the context menu.
  • Rename: user-specific label of up to five lines (four free lines plus an optional line that appends the period or date information). The time information can be suppressed. A calculated column built from unnamed columns shows the source labels as they were at creation, and later renaming or deletion of the sources does not change it.
  • Footer aggregates per column (only the ones meaningful for the type): sum, average, maximum, minimum; count empty; count non-empty; count of yes / count of no (e.g. "is customer = yes"); count per value (e.g. number of POS, POR and negative-stock articles). They are saved with the query and also drive the subtotals shown in outline rows.
  • Result limit: "first 10 …" and similar presets, or a user-defined maximum. It is always displayed (e.g. "the first 10 customers") and saved with the query.
  • Tooltips on fields and cells show the full text of truncated labels (not for numbers or yes/no) and the exact filters of filtered criteria, headers and cells.
  • Column properties: columns with a period, price comparison or further filters, and calculated columns, have editable properties (edit mode: context "Properties"). In display mode they follow the bound variables. Example: the condition "gross revenue in period" can be split into the two variables "gross revenue" and "period", and changing either one updates the column.

4.1.11 Calculated columns [GENERIC] (Reports Profi)​

  • A calculated column relates two numeric values (quantities, prices, percentages).
  • Operation families, depending on the first operand:
    • with another value or column: plus, minus, times, divided by, difference in %;
    • with a constant: plus value, minus value, times value, divided by value, plus %, minus %, share %;
    • with an averaging period: per day, week, month, quarter or year.
  • The second operand can be a field that is not a visible column (a "potential column" with its own settings). It is not added to the grid automatically.
  • The system offers every numeric field for every sensible operation. Whether the result is meaningful (e.g. adding gross to net) is the user's responsibility.
  • Calculable columns carry a marker. Non-calculable columns (e.g. the article number) and already-calculated columns get no preselected partner.
  • The new column is appended last, with a header of the form "<col1> <op> <col2>", e.g. "Gross 2012 ÷ Gross 2011" for year-on-year development.
  • Examples from the help:
    • Relate displayed prices (pharmacy purchase price, own purchase price) to a vendor price that is not shown, in the query "articles by vendor and minimum sales".
    • Clinic statistics: number of dispensed dosage units (e.g. tablets) of an active ingredient or product group in a period, using the fields "piece count" and "packs sold".
  • Calculated columns keep their own copy of the definitions (no live link to their sources).

4.1.12 Outlining: grouping, fan-out, time division​

  • Grouping: consolidates rows into higher groups, shown left of the category object. Fan-out: splits a cell's value into parts, shown right of the object. Fan-outs are always possible for summed or calculated columns.
  • The object being outlined is always the category's entity (e.g. the article, identified by name + article number; or the employee by surname + first name).
  • Limits: up to three grouping levels and three fan-out levels, and only by visible columns or by further-filter criteria of those columns. The Reports Profi licence allows a single grouping level by a simple column; MMR Standard allows up to three levels, including complex fields.
  • Grouping by a non-summed column: "group by <column>", e.g. stock status, then dosage form. Placement depends on how the level is added: from the header it becomes the outer level; with the "+" icons the user chooses the position (super- or sub-group).
  • Grouping or fan-out by a summed column (e.g. "Gross 2009"): context menu → grouping/fan-out → filter category (e.g. customers) → criterion (e.g. gender).
    • Examples: articles by stock status and customer gender; customer revenue fanned out by whether the sold lines were in stock at the time of sale.
  • Time divisions (summed columns only):
    • Weekday: Monday to Sunday, always starting on Monday.
    • Month: 12 month rows starting from the most recent month of the period. Over multi-year periods each month row sums that month across all years, which places prior-year comparison columns side by side. Example: period 2012 gives December 2012 down to January 2012.
    • Calendar month: month + year, exactly the period, no 12-month limit.
    • Calendar quarter: each quarter touched by the period; partial quarters contain only the months inside the period. Example: February 2011 to July 2012 gives Q3 2012 (July only) down to Q1 2011 (February + March).
    • Quarter: fixed Q1–Q4 summed across years.
    • Year: most recent first.
  • Display controls: expand or collapse all levels or a single level; sort groups ascending or descending (e.g. negative-stock > POR > POS); delete an outline element.
  • Hide empty outlines (no value or 0): on by default. It is offered only when at least one outline relates to a value summed via a time division or further filter. It hides rows only; folder values, counts and subtotals do not change.
  • Worked example: an employee query on gross revenue in a period, fanned out by month and then, with the "+" after "month", by article dispensing rule, gives revenue per employee per month per prescription category.

4.1.13 Sales category specifics​

  • Sales queries are always tied to a period.
  • Two views: the line view (initial view) and the transaction view. Conditions apply to both.
    • Transaction view: receipt number, gross amount of the transaction and similar header fields.
    • Line view: article number, name, price, line gross and similar.
    • Unlike the sales-management module, the line view lists ALL lines of the transactions in the transaction view, not only those of marked transactions.
  • Field levels: transaction, subtotal and line. A corresponding line field is suffixed "per line". Some fields exist only at one level, e.g. operator name (transaction).
  • Column-insertion rules:
    • A transaction field added as a condition creates a column in the transaction view and the corresponding field (or the same field) in the line view.
    • A transaction field shown in the line view displays the transaction total, not the line value.
    • A line field added as a condition while the line view is active creates a column only in the line view. With the transaction view active, no column is added there.
    • Line and subtotal fields can never be columns of the transaction view, but as conditions they still filter both views. Example: "transactions to customers with a discount model" filters the transaction view without showing that column there; the line view shows the column.
    • A column added in one view is not added to the other.
    • "Unit" (pack size of a line) is column-only.
    • Filtering a column propagates only to the same column in the other view, not to the corresponding one. Example: the condition "dispensed quantity" creates the transaction column "disp. qty" and the line column "disp. qty [line]". Filtering the transaction column changes only the condition, not the line column.
    • Adding an already-filtered field as a column does not open its dialog; use Properties.
  • Some fields are pre-computed (e.g. net-net revenue). Their properties can be changed and they can feed calculated columns.
  • Gross margin % shows no value when it cannot be computed (e.g. division by zero).
  • Transaction and order chains: a chain arises when a completed till sale or invoice order is edited, a pickup is resolved, or an order is cancelled. Example: one pack sold for 1.18, later changed to two packs.
    • Transaction view: the original transaction (1.18) and a follow-up transaction with the difference (1.18). The follow-up has "count as customer = no".
    • Line view: the original line (1.18), the new line with the full amount (2.36) and an internal reversal of the first line (−1.18).
    • The line-level flag "currently valid receipt" keeps only the latest receipt of each chain. This gives final quantities, unit prices and co-payments, which is useful for co-payment lists and purchase lists. Revenue columns are then misleading: the transaction view shows only the last 1.18, while the line view shows 2.36 with quantity 2. Revenue columns should therefore be avoided with this flag.
  • Worked example:
    1. Three sales are evaluated, with the column "dispensed quantity" per transaction and per line (the line quantities sum to the transaction quantity).
    2. A second transaction column, filtered to prescription sales, is added; the user answers "no" to the align prompt to keep both versions.
    3. Adding the subtotal field "sale type = statutory-insurance prescription sale" as a condition removes normal sales from both views.
  • "Show sales details" opens the sales-management module with all or the marked transactions, including subtotals and lines.
  • No result processing: mass-changing sales makes no sense.

4.1.14 Result processing (mass actions) [GENERIC]​

  • Precondition: a query has been run. Mark some or all rows, choose "Process result", pick a processing group and action, set the parameters, confirm OK and the safety prompt. The action is executed for every marked row.
  • The actions mirror the single-record functions. Customer actions can work across the branch chain (connected branches and partner pharmacies).
  • Alternative: the "<category> details" function opens the marked records one by one in their own module for individual editing. Result processing sets the same predefined value on all of them.

Articles

GroupActionParameters and rules
Goods logistics / order optimisationOrder (Bestellen)Supplier: from the automatic shopping-cart determination, last supplier (of the last delivery), or a specific supplier (searched by name; supplier-number entry not supported). Quantity: (a) optimisation — standard (order-quantity optimisation model) or by a stock-cover period ("dispo time") in days, e.g. 90; optional evaluation period override (dates within the current and the previous two years); reductions by stock on hand, by lines already in shopping carts and by lines in open orders (each on by default, can be unticked); (b) fixed stock order quantity (e.g. 10), bypassing optimisation and ordered for stock without reservation; (c) top up the missing emergency-duty stock (night/weekend duty reserve). The articles are sorted into existing or new shopping carts for further editing or automatic ordering.
Goods logisticsReturn (Retournieren)Return reason (default "pharmacy ordering error"); supplier: specific (by name) or last supplier; quantity: complete stock (for status POR the quantity of the last goods receipt), quantity of the last goods receipt, or N pieces.
Order optimisationOrder parametersEach parameter has a "change" checkbox with "set to N" or "delete" (= 0): fixed minimum stock; maximum stock; discontinued flag (no longer reordered, warning on manual orders, icon in search lists); fixed order quantity (always this quantity or an integer multiple, e.g. a carton of bottles); maximum order quantity (caps optimised quantities); permanent-procurement flag (Dauerbesorger: frequently dispensed but deliberately not stocked, e.g. expensive or short-dated); fixed supplier assign/delete. Rule: fixed order quantity ≤ maximum order quantity.
StorageRetrieve from picking robot (Auslagern)Output point (default from the robot configuration), priority, quantity: complete robot stock, quantity of the last goods receipt, N packs, or the quantity expiring within a period. Use: purge short-dated or overstocked items.
StorageStorage dataEmergency-duty stock set/delete; standby stock set/delete; "in blister machine" yes/no; "preferably dispense" yes/no; "permanent assortment" yes/no.
StorageStorage locationAdd selected locations / replace existing with selected / delete selected / delete all.
StorageStock statusSet to a value from the list (e.g. POS, POR …).
StorageExpiry datesDelete stored expiry dates (stock is kept): all, or those within from/to.
Price calculationOwn purchase priceSet € / delete. Needs the right "Article: edit prices" or role manager or assortment manager.
Price calculationOwn selling priceAssign or delete a calculation rule; allow or restrict discounts; set the price manually or delete it; allow or restrict discounts on fixed own prices. Same permission.
Additional infoOwn info textAppend / overwrite / delete; "show at dispensing (POS)" yes/no.
Additional infoArticle classificationAssign to selected classes; remove selected assignments (with "select all"); assign to a NEW article flag (name, description).
PrintLabelsType: price label, shelf/location label, base-price (unit-price) label. "With own prices" (own purchase price only on location labels; own selling price marked with *). Quantity: number of packs in stock (only for item-level stock keeping) or a fixed count. Price cascade in §6.
EditAssign vendorOnly own-created and pre-captured drug-database articles.
EditDelete articlesOnly own-created and pre-captured articles; at most 5000 per action; needs Reports Profi. Articles that are not deleted are listed afterwards.
EditExtend to groupShare own-created articles with the whole pharmacy group (query field "is visible group-wide"). Irreversible. If the article number is not unique in the group, a new one must be assigned in article details, which also show in which group pharmacies the article is visible.

Customers

GroupActionParameters and rules
AccountingDebtor accountSet a number: 5 digits, recommended 10000–69999 under the standard accounting chart; the input stays marked invalid until valid, and other numbers should be agreed with the tax advisor. Or assign per the accounting-export setting "collective accounts grouped by alphabet" or "consecutive individual accounts" (only if configured). This is how manual numbers get overwritten, because automatic assignment never overwrites existing numbers. Or delete.
Care (Betreuung)Batch and expiry entryFlag "always ask for batch number and expiry" yes. Only for customers who take part in blistering; others are rejected with a message.
CareMedication managementParticipation in medication management yes/no; federal medication plan flag yes/no.
CouponsAssign couponsDiscount-coupon model, number of coupons per customer, validity period.
PropertiesStatusActive / inactive (hidden from the standard contact search, still found by the extended search and can be reactivated) / deceased (natural persons only; excluded e.g. from birthday lists).
PropertiesOrigin, contact exchange, batch documentation, roleUpdate the origin; activate cross-branch contact exchange; batch documentation on/off; set the contact role to customer (person).
InvoicingInvoicing settingsInvoicing permission yes/no ("no" deactivates an existing permission); assign or remove an invoicing model; separate invoice yes/no.
Care homeHome assignmentAssign as residents of a home or structural unit (tree); delete existing home assignments. Use: residents moving to another building.
Contact classificationAdjust assignmentAssign to selected classifications / remove them / assign to a NEW classification (name, description).
Health insuranceInsurer status / co-payment exemption"Delete exemption" clears the exemption dates AND sets the insurer status to "co-payment and extra-cost liable". Or change: exemption from (set/delete), exemption until (set/delete), insurer status from a list. Use: exemptions usually expire at the start of the year, and prescription sales to customers with expired exemptions raise warnings, so the expired ones are mass-deleted.
DiscountInstant discount / discount modelInstant discount % applied at sale. Applies to: no articles, self-selection OTC, or self-selection and behind-the-counter OTC. Replace or remove the discount model. If a discount would cause a loss in a sale, a price-control dialog lets the user decide the final price.

Suppliers

GroupActionParameters and rules
AccountingCreditor account5 digits, recommended 70000–99999; set/delete.
PropertiesSettings"Ignore in shopping-cart determination" option.
PropertiesSub-ordersConfigure the sub-order types. Use: switch sub-orders off for all direct suppliers, which deliver in one shipment, so that one order is not split into separately booked sub-orders. Also works for suppliers maintained by the external price-update service.

Sales: none. Other categories: not described in this slice.

4.1.15 Cross-branch queries​

  • Data of all or selected branches can be included.
  • Rights: "evaluate across group", contained only in the role "corporate control" (Unternehmenssteuerung). The role is active automatically for staff who hold the manager role in all branches; otherwise the group owner asks the vendor to activate it. Holders can grant the right to others. The right "start Reports" is also needed. If data is still missing, the vendor must adjust the branch configuration.
  • Predefined queries in the categories customers, sales, credit notes, goods receipts and pharmacies/branches carry the criterion/variable "Pharmacy", which defaults to the own pharmacy. Other categories and own queries use the filter category "Pharmacies/Branches".
  • Examples:
    • A cross-branch birthday list: change the pharmacy criterion of the predefined "Birthdays" query.
    • Cross-branch "top sellers in period": do not include stock status, because it differs per branch. The filter icon on the column shows that not all pharmacies are included; set the branches in the column properties.
    • Suppliers match across branches only if their names are identical in every branch, and suppliers created locally in one branch are excluded. Recommendation: identical naming, with supplier creation done group-wide.
    • An own vendor query "order lines in period" with a branch filter.
    • The filter "branch & partner sourcing" in the order-lines category (categories articles, vendors, pharmacies/branches) excludes internal transfers or isolates them.

4.1.16 Query management and exchange​

  • Own queries can be renamed, deleted (with confirmation), exported, imported and exchanged within the group. Predefined queries can only be imported. All of this needs Reports Profi.
  • Export writes a .abfrage file.
  • Import:
    • Single import: the save dialog is prefilled with the category from the export and lets the user adjust name and category.
    • Multi-import: no dialog; queries are stored under their saved category and name.
    • Own queries go to the own area, predefined ones to the predefined area.
  • Group exchange marks the query with a symbol, is irreversible, and first checks whether an identical query already exists in the branch, to avoid duplicates.

4.1.17 Scheduled and interactive report tasks​

  • From "Create task in Notes": a one-off task or a series that runs a query.
  • Assignment: open-query tasks can be assigned to an employee (with a deputy) or the whole pharmacy. Automatic print, e-mail and export tasks can be assigned only to the whole pharmacy.
  • Actions:
    • open query at the scheduled time;
    • auto-print on the chosen printer (optionally with a legend);
    • auto-send by e-mail (address prefilled from the company master data; optional encryption password);
    • auto-export to PDF, Excel or CSV (CSV with or without headers) into a fixed export path in the pharmacy directory, or by default into a temporary pharmacy directory.
  • Recurrence: once (default), daily, weekly, monthly, quarterly, yearly. Also start, end, all-day, priority.
  • Variables are frozen: the task stores a snapshot of the variable values when it is created, and later changes to the query's variables are not applied to it. Series must therefore use relative periods (e.g. "last 3 months").
  • Execution: a background process checks every five minutes. Preconditions:
    • the time is reached;
    • the query still exists under its saved name;
    • its variables are unchanged (same number, same names; changes to conditions or columns are not checked);
    • the result has at least one row;
    • the query's licence is present.
  • Failure: a message appears in the info centre and in the Notes messages folder "automatic tasks". Tasks can also be started manually from Notes.
  • Sales queries always print the line view. Printouts of sensitive data land on a shared printer, so access must be considered.
  • Editing a query that has tasks: saved changes to column sort, column moves, additions and deletions, added or deleted conditions and changed non-variable condition values are applied. Ad-hoc changes made when the query is opened from Notes are not saved.
  • An open-query task appears in the calendar, task list and task control of the assignee and the deputy, or of everyone.
  • Export-link tasks: every cloud download link or OData feed automatically creates a task series in Notes task control. It stays active until the link's availability or series duration ends, and is then set to "done" automatically. Functions:
    • Delete: removes the task and deactivates the link.
    • Show link (right needed): shows the URL and password, and allows deactivating or copying the link.
    • Refresh link: regenerates the data immediately, outside the series pattern.
    • A "protocols" tab logs every use of the link.

4.1.18 Exports and printing​

  • Print: selected rows or all; optional legend (query description and column explanations; off by default to save paper); "scale to page width" on by default. Grouping and outlines are printed. A configuration parameter controls the brightness of report prints.
  • PDF export:
    • The header shows the query description and the criteria that are changeable in display mode; the end of the list shows the row count, followed by descriptions of all columns and aggregate filters.
    • Destination: the file system, or a cloud download link (access protection on by default with a generated password, which can be changed within the password policy; disabling protection is discouraged). The link is valid one month.
    • With or without legend; scale to page width.
    • Actions: open, save, send link by mail (opens a prefilled internal message; the user adds recipients), copy link, close.
    • A link sent by e-mail is no longer protected by the link-viewing right: anyone with access to sent mail can see it.
  • Excel/CSV export: xlsx or csv; a one-off snapshot with no refresh (use a scheduled export for repeats). Destination: file system or download link (same rules). CSV headers are optional; Excel always has headers. The files open in any spreadsheet program. A simple viewer may lack features such as filtering.
  • OData data feed:
    • A standard web data interface; the spreadsheet loads it once and refreshes it itself, so no new query is needed in the pharmacy system.
    • Always contains ALL rows (selection ignored).
    • Availability: daily refresh (report regenerated each day) or no refresh (generated once).
    • Actions: send link by mail, copy link, close.
    • Access protection: user name "reports" plus a password set in the pharmacy system.
    • Recommended spreadsheet use: data import, query editor, pivot tables, charts, "refresh when opening the file".
    • Multi-branch: import one feed per branch, name each, append them into one table, then pivot. When sources are combined the spreadsheet asks for privacy levels. The vendor recommends "private" at the top level of the feed host, because feeds may contain personal or confidential business data. Using one password for several feeds is the pharmacy's responsibility.
  • Rights: "create link"; "show, refresh and delete link". Both are in the manager role by default.
  • Overview of the four use cases: simple file download (Excel, CSV, PDF); raw data into a spreadsheet (OData); pivot analysis for a single pharmacy (OData); pivot analysis across branches and partners (OData).

4.1.19 Customer selections built on queries [GENERIC]​

  • Used wherever a process targets or excludes a set of customers (e.g. customer information and tasks, campaigns).
  • Report-query selection: criteria-based, automatic, dynamic, refreshes itself (at intervals or manually, depending on the module); requires shared features; suits recurring selections; built from a predefined or own query.
  • Customer list: hand-picked, static, unchanged unless edited; filled one by one or with a snapshot of a query result; suits ad-hoc groups.
  • Procedure: choose the option "customer selection", then browse. Tick existing selections (several, in any combination), or create one:
    • import a predefined customer query (e.g. "regular-customer top sellers"), adjust it, take it over, and give it a name and description;
    • new selection → report query → configure in Reports → "take over query";
    • new selection → single customer list → add customer / add customers from report.
  • Selections can be edited or deleted; deleting affects the functions linked to them.

4.1.20 Pharmacies/Branches category and MMR overview​

  • Pharmacies/Branches category (licensed except the basic queries): business-management evaluations for running the pharmacy (management report MMR, Cockpit Profi).
    • Many results are outlined by default.
    • The queries are built on the fields of the other categories.
    • MMR queries mirror MMR work lists; their description cites the list or graphic code (M1, M2, P4 …).
    • Predefined MMR queries sit in classifications prefixed "MMR-" (e.g. "MMR-Processes").
    • Queries marked as Cockpit Profi are available with that licence even without MMR.
    • The article classification "MMR exclusion" removes an article from all MMR-relevant queries.
  • MMR overview (separate module, and a link above the categories in Reports):
    • All MMR queries in a two-column list, by process category: All (sorted by category), Stocks, Processes, Employees, Selling, Assortment, Customer. The count of queries is shown per category.
    • Filters: search (including queries marked as "similar"); reports/analyses only; work lists only (default within a category); both (default for "All").
    • Opening a query runs it in full screen.
    • Reports show a link icon that lists the work lists related to them. Example: report "B2 – structure of special procurements" compares the last 12 months with a comparison period → work list "unwanted non-stock procurements" (items procured ≥ 3 times) → result processing, e.g. change the stock status of frequently procured items, to reduce the unwanted procurement rate.
    • Closing the query returns to the overview. To edit a query or see its category, switch to the normal view.
    • Positioned as a profit-optimisation tool used together with the vendor's MMR consultants and the monthly printed MMR report.

4.1.21 Predefined query catalogue (as named in the pages read)​

The help does not contain a full catalogue in this slice. The following predefined queries and query groups are named:

CategoryQuery or classificationPurpose / main criteria
ArticlesEmergency-duty articles with missing emergency stockArticles with a defined emergency-duty stock whose total stock is below it; feeds the "order missing emergency stock" action.
ArticlesTop sellers in period (Verkaufs-Renner im Zeitraum)Ranking by units sold (packs dispensed) in a period, optionally across branches (then without stock status).
ArticlesArticles by vendor and minimum salesArticles of a vendor above a minimum sales threshold, with price columns (pharmacy purchase price, own purchase price) for comparison.
ArticlesArticles of a vendor incl. supplier revenues (Profi)Vendor assortment with purchase revenues per supplier.
ArticlesPurchase data overview (Profi)Purchasing key figures.
ArticlesPermanent-procurement articles (Artikel-Dauerbesorger)Items flagged as procured on demand; the help's auto-print example.
CustomersBirthdays (Geburtstage)Customers with birthdays in a period; branch criterion; excludes deceased customers.
CustomersRegular-customer top sellers (Stammkunden-Renner)Regular customers by sales; offered as an importable customer selection.
SalesWrite-off (Abschreibung)Write-offs for own consumption and compounding needs.
SalesOrders to care homesHome orders without residents, or including residents.
SalesExtended transaction searchTill and/or invoice sales above an amount or within an amount range.
SalesCustomer-related: theoretical co-payment listTheoretical co-payments of a chosen customer for the previous year.
SalesRevenue / gross-margin analyses (e.g. revenue by VAT rate)Gross and net-net revenue by full or reduced VAT rate (VAT rates as filtered columns); total revenue and gross margin.
SalesSales statisticsNumber of sale types per transaction; sales to employees; transactions with add-on sales (filterable per employee); transactions per employee; "transaction counter per operator" sums "count as customer = yes" to show customers served per employee.
Pharmacies/BranchesCockpit – Sales cockpit (Verkaufscockpit)KPI data set used in the OData examples (Cockpit Profi).
Pharmacies/BranchesMMR-… classifications (e.g. MMR-Processes); reports such as B2 "structure of special procurements"; work list "unwanted non-stock procurements"Management reports and drill-down work lists by process category (stocks, processes, employees, selling, assortment, customer).

4.2 Cash book (Kassenbuch) [GENERIC core; tax framing DE-SPECIFIC]​

  • Purpose: produce the legally required cash ledger for a period from the till closings and track the expected physical cash. The report goes to the tax advisor.
  • Source:
    • all relevant bookings within the boundaries of the daily closing reports (Z-receipts) that fall in the period, including pay-ins and payouts made at the till;
    • payouts entered in the cash book (bank deposit, private withdrawal);
    • correction bookings.
    • A system parameter ("summary receipts to evaluate") can switch the source from Z-receipts to S-receipts.
  • First start: enter the opening balance and its validity start. Procedure:
    1. Create all outstanding Z-receipts.
    2. Count all cash in all tills plus the safe.
    3. Enter the total (≥ 0) and the start date and time. Forward- and back-dating are allowed, but not before the installation of or migration to the system.
    4. Confirm the safety prompt.
    • This step is a precondition for all balances.
  • Header values:
    • last printed period;
    • evaluated period (from 00:00 of the start date to the end of the end date);
    • opening balance (relevant only initially);
    • carry-over: cash not withdrawn before the period start, computed as opening balance + all subsequent Z-receipts + pay-ins − payouts, and added into the current period;
    • cash balance at the period end;
    • filter criteria.
  • Entry list: date, voucher number, running number, income, expense, generated booking text (with the remark appended).
  • Functions:
    • correction booking (details on a separate page);
    • payout: bank deposit or private withdrawal, positive amount, booking date that can be back-dated to the actual day but not before the cash-book start;
    • filter and remove filter;
    • print;
    • jump to the DMS document of a pay-in or payout and back to the transaction (also available in till turnover and till closing).
  • Rule: the user must make sure the cash balance never becomes negative; the help does not describe a system block.
  • Print: a print preview, then the cash-book report: every Z-receipt's data in the period, pay-ins and payouts at the till, bank deposits and private withdrawals, carry-over and cash balance. If a filter is active, a warning says that the filter must be removed for a valid report. A filtered print lists the filter criteria on the extract.

4.3 Payment transactions – SEPA direct debit (Zahlungsverkehr) [DE/EU-SPECIFIC]​

General idea: a batch bank-collection file generator with a mandate lifecycle, pre-notification and lead-time rules, and reconciliation of bank returns.

  • Purpose: collect receivables from customers who pay by direct debit, both from till sales and from invoicing.
  • Origin of debits:
    • at the till: closing type "direct debit", or "immediate invoice" for a direct-debit customer;
    • in invoicing: invoices of customers with payment method "direct debit".
  • Prerequisites per customer: a bank account flagged for direct debit; a signed SEPA mandate on file; payment method set to direct debit.
  • Paid module. Rights: "start payment transactions", or role payments officer, or manager.
  • Direct-debit page:
    • Filters: receipt date range, amount range, receipt or till-receipt number, customer, IBAN, mandate reference.
    • Tab Open: not yet exported, or returned by the bank. Rows can be marked, exported or locked.
    • Tab Exported: exported, accepted or not accepted.
    • Columns: payment status icon, lock icon, "cancelled in sales management" warning, origin (till or invoicing), customer, mandate reference, receipt number, receipt date-time, due date, due-date validity icon (too early / insufficient lead time, or too far in the future), amount. A detail pane shows the reference data.
    • On opening, all debits that are due or overdue and valid are preselected.
    • Sort order: no status first, then accepted, then not accepted. A not-accepted row that was later re-exported is greyed out; the new export with the same receipt number is shown normally.
  • Export:
    1. Mark rows (or select all), then choose export.
    2. A prompt offers to correct invalid due dates automatically (§6).
    3. A success message names the folder <documents>/SEPA-Export/<YYYY_MM_DD_HHMMSS> and the files.
    • One XML file is created per combination of creditor account × sequence type × execution date. The file name contains the export date-time, the creditor IBAN (e.g. the default account in the company master data), the sequence type and the execution date.
    • Exported invoice-based debits set the invoice status to Paid.
  • Transfer: the user uploads every file through their own online banking, each to the bank of the IBAN in its file name, promptly. The automatic due dates assume prompt upload.
  • Lock / unlock: exclude a debit from export, e.g. when a customer asks for a deferral.
  • Cancellation in sales management of an exported till debit: a red warning icon appears and the debit is excluded from re-export. Marking it "not accepted" does not open the re-order dialog. The user must check manual steps such as refunds.
  • Accepted: money received; marks the receivable as settled for overview.
  • Not accepted: dialog "re-order debit":
    • return code from the bank (certain codes automatically tick "lock");
    • sequence type for re-collection, as the bank reports it;
    • optional lock until clarified.
    • Result: the debit appears in Open (locked) and in Exported (not accepted), and the invoice status goes back to Created.
    • After clarifying, unlock and export again.
    • A mistaken "not accepted" can be switched to accepted as long as the debit has not been re-exported.
  • Mandate side-effects:
    • Choosing sequence type "final" on re-ordering revokes the mandate with the next export.
    • Later re-ordering a debit of that mandate as "first" or "recurring" reactivates it.
    • A mandate revoked manually in the contact data cannot be reactivated this way.
  • SEPA-file page:
    • Filters: receipt date range, export date range, receipt number, mandate reference.
    • Columns: export date, file name, remark (free text, editable inline), total amount. A detail pane shows the contained records.
    • "Create copy" regenerates a byte-identical file (same content and name) from the stored records if the original was lost.

4.4 Value-voucher administration (Wertgutscheinverwaltung) [GENERIC]​

  • Purpose: oversee prepaid stored-value vouchers issued by this pharmacy and, with cross-pharmacy use, across the group.
  • Default list: current vouchers only (pre-captured, issued, in processing, in redemption). The filter can add redeemed, cancelled and cleaned-up vouchers.
  • Expiry: an expired voucher shows a warning with its expiry date. This does NOT block redemption; honouring expired vouchers is the pharmacy's decision.
  • Search: the full (external) voucher number, or a barcode scan. Search ignores the active filters. External numbers are alphanumeric, so there is no numeric sort.
  • Filter: status (checkbox dialog), issue-date range, origin pharmacy (only visible with cross-pharmacy vouchers).
  • Clean up:
    1. Select the voucher and confirm.
    2. If an expiry date exists and has not been reached yet, a second warning appears.
    3. The voucher becomes unredeemable, and the remaining balance is booked out of the voucher liability account into the pharmacy account (income). Both movements are visible in the cash book and the accounting export.
  • Incoming settlements (only with group-wide vouchers): list and details of redemptions of own vouchers in other group pharmacies. Sorted by date and time; cancelled settlements greyed out with an S marker; search and filter. Documents are filed into the DMS automatically, with a jump button. Creating outgoing settlements is described elsewhere.
  • Evaluations: open vouchers of the own pharmacy; sums of settlements payable and receivable (details elsewhere).
  • Other functions: reprint a voucher; print a voucher overview; jump to the related transactions in sales management; history of all status changes with timestamps.

4.5 Payback – external coalition loyalty programme [DE-SPECIFIC partner; idea GENERIC]​

General idea: a third-party points programme in which the pharmacy captures a card at the till, computes the eligible revenue under exclusion rules, prints the expected points, and batches the transactions daily to a clearing intermediary.

  • Purpose: let customers collect points of an external programme at the pharmacy as a purchase incentive and for retention.
  • Contract and access: the pharmacy contracts with the wholesaler that runs the programme for pharmacies (extra cost). The service centre then sends the credentials. Paid add-on module.
  • At the till: the card's 13-digit barcode is scanned or typed in.
    • Points are earned on all non-prescription items.
    • No points for prescription-only items, compounded preparations, fees, books, cash sales (as worded in the help) or non-material system items.
    • The expected base points are printed on the receipt. The programme operator verifies the card and makes the final award.
    • Promotion coupons (alphanumeric barcodes, so a suitable scanner is recommended, or typed in) can raise or multiply points. Their points are not printed; the receipt only notes that a coupon was applied.
  • Standard model (fixed, not editable): 1 point per €1 of eligible revenue, rounded commercially on the total eligible revenue of the sale (§6).
  • Model list: name, valid from/to, points per euro, article range, active.
  • Transfer:
    • Every day from about 09:00, all transactions not yet transferred are sent automatically over the internet as an encrypted file to the service centre. The centre validates them, forwards them to the operator and returns a confirmation.
    • The customer sees the balance on the operator's website; final crediting can take several days.
  • Send-statistics page:
    • Period filter.
    • Totals of points, goodwill points and promotion points.
    • Transfer list: status (successful; successful with errors such as an invalid card number; pending; sent with no feedback yet; failed, e.g. checksum error), number, date, time, feedback (full text in the tooltip), base points, promotion points from marketing codes.
    • Transaction details: receipt number, eligible revenue, card number, points, goodwill points, coupon number, promotion points, feedback error type.
    • "Send": manually sends all untransferred transactions, including today's.
    • "Test connection": reports success or failure.
    • If the connection fails, a message appears in the info centre and the Notes module.
  • An interface to an external web-based workforce-planning service. The pharmacy system supplies sales data (timestamp, employee, till name, key figures); the service independently computes how many staff are needed at which times.
  • Paid add-on; the contract with the planning vendor is separate.
  • Access: desktop or Office menu.
    • First start: login (customer number, user, password). If the customer number is stored in the company master data, only user and password are needed.
    • Configured: opens the portal directly.
    • Not configured or not licensed: opens the vendor's information website.
  • Configuration (transfer modalities, credentials): company master data, page "staff scheduling" (other chapter).
  • Branches: always branch-capable. Each pharmacy system transmits separately. Systems with the same customer key pool their data, so planning can be done across those branches.

4.7 Training portal – IXOS.campus [GENERIC]​

  • A learning platform for the pharmacy team: course catalogue, taking courses, own progress. It is also usable on mobile devices through the companion staff app.
  • Rights are assigned in role management.
  • "My campus": active and completed courses. Open the full catalogue in a browser, or start an active course directly (its modules open in the browser).
  • Pharmacy overview: all completed courses of the whole pharmacy. Needs a permission, which the manager role includes.
  • Print: the campus overview, the "e-prescription licence" certificate, or self-defined certificates after passing a course.

4.8 Office menu (Büro) – module inventory​

  • Cockpit (daily or monthly KPI dashboards with gauges, tables, charts; other chapter).
  • Reports; MMR overview.
  • Evaluations (Auswertungen; other chapter).
  • DMS (documents generated in the system and scanned external documents such as wholesaler invoices and phone bills, in a preconfigured folder structure; other chapter).
  • Documentation administration (blood products, narcotics; other chapter).
  • Accounting export (DATEV).
  • Tax-audit data export and till-inspection export (other chapter).
  • Cash book; staff scheduling; Payback; payment transactions.
  • Web portals:
    • online support portal: hotline contacts, support forms, FAQ, online help, support documents, release plan, product training, consumables order form; requires a specific browser;
    • vendor webshop for consumables;
    • training portal;
    • user management for the vendor's cloud ("Connect") products;
    • Media.connect: management of in-store and till-screen TV content.
  • Installed office programs and the calculator.

5. Workflows​

W1 – Build and publish a recurring KPI report

  1. Reports → category (e.g. Employees) → New query.
  2. Drag "gross revenue in period" into the conditions; set the period to "last month". Turn both the value and the period into variables.
  3. Add columns; add a second revenue column with an adjustment "same period one year earlier", using the same period variable.
  4. Add a calculated column: current ÷ prior → growth.
  5. Fan out by month and by dispensing rule; set footer sums; limit to the top 20.
  6. Save under a classification. Tick "visible only to revenue officers" if the report is sensitive. Optionally share it with the group.
  7. Create a task in Notes: auto-export to Excel, monthly, fixed export path (variables frozen, which is fine because the period is relative).
  8. Alternatively, export an OData feed with daily refresh and send the link; the recipient builds a pivot table in a spreadsheet.

W2 – Act on a work list (e.g. reduce unwanted special orders)

  1. MMR overview → Stocks → report B2 → linked work list "unwanted non-stock procurements".
  2. Mark the rows → Process result → Storage → Stock status → set to a stocked status → confirm.
  3. Optionally: Order optimisation → set a fixed minimum stock; or Goods logistics → Order with dispo time 30 days.

W3 – Year-start co-payment exemption clean-up

  1. Customers query: exemption-until in the past year.
  2. Mark all → Process result → Health insurance → Delete exemption → status becomes co-payment liable.

W4 – Customer campaign

  1. Customers query (e.g. regular customers with category X purchases).
  2. Process result → Coupons → assign coupon model, count and validity. Or reference the query as a dynamic customer selection in the customer-tasks module.

W5 – Cash book period

  1. First use: create the open Z-receipts, count all cash (tills + safe), enter the opening balance and start date-time.
  2. Daily: till closings produce Z-receipts automatically.
  3. When cash goes to the bank or to the owner: cash book → payout → bank deposit or private withdrawal, amount, date.
  4. Month end: set the period, check the carry-over and cash balance, remove filters, print the report, and hand it to the tax advisor.

W6 – Direct-debit run

  1. Sales with payment type direct debit or immediate invoice at the till, and invoice runs, create open debits.
  2. Payment transactions → Open → preselected due debits → export → accept the due-date corrections.
  3. Upload each file to the bank of its IBAN.
  4. When the bank credits arrive → Exported → accepted.
  5. On a return → not accepted → return code, sequence type, lock → clarify with the customer → unlock → export again.
  6. If the file was lost → SEPA files → create copy.

W7 – Voucher clean-up

  1. Voucher administration → filter: issued, issue date older than X → select an expired voucher → clean up → confirm (twice if the expiry is not reached).
  2. The balance becomes income and appears in the cash book and the accounting export.

W8 – Loyalty transfer check

  1. Payback → send statistics → period.
  2. Look for failed transfers or errors (e.g. invalid card).
  3. Test the connection → send manually.

6. Business rules and calculations​

  • Price comparison condition: base price (or discount) OP comparison × (1 + pct/100) + eur, with OP ∈ {>, <, ≥, ≤, =, ≠}. Positive surcharges add and negative ones subtract. Example: net selling price > purchase price × 1.03 + 8.76 €.
  • Relative periods always use completed units; "between the last 0 and N" includes the current unit; recalculated per run; maximum ten years back. "Same position as today" points are recalculated per run. Absolute dates are frozen.
  • Further filters change the aggregated values, never the row set; no additional period inside a further filter.
  • Variables: unique per query; deleted when unused; scoped to one query. Adjustments apply only to their usage.
  • Align: only identical definitions (field, operator, € and % for price comparisons; complete filter group for further filters).
  • Article query default: stock status = POS and POR.
  • Outlines: up to three groupings + three fan-outs; only visible columns; empty outlines hidden by default; hiding changes row counts only.
  • Month time division aggregates the same month across years; the calendar variants do not.
  • Sales: line-field conditions filter both views; a filter on a transaction column does not propagate to the corresponding line column; gross margin % is blank on division by zero; the follow-up receipt of a chain does not count as a new customer.
  • Result processing:
    • Article deletion: at most 5000 per action; only own-created or pre-captured articles.
    • Fixed order quantity ≤ maximum order quantity.
    • Order evaluation period: current year and the previous two years only.
    • Return quantity "complete stock" means the last goods-receipt quantity for stock status POR.
    • Debtor accounts: 5 digits, recommended 10000–69999. Creditor accounts: 5 digits, recommended 70000–99999. Automatic account assignment never overwrites existing numbers; only the mass action does.
    • Deleting a co-payment exemption also resets the insurer status to "co-payment and extra-cost liable".
    • Batch and expiry prompting is only possible for blistering customers.
  • Label price cascade: with own prices: own selling price → recommended retail price → pharmacy retail price. Without: recommended retail price → pharmacy retail price → own selling price. The next price is used if one is missing; a printed own price is marked *.
  • Scheduled tasks: checked every five minutes. They run only if the query exists under the same name, the variables are unchanged in number and names, there is at least one result row, and the licence is present. Otherwise a message is filed. Sales prints use the line view.
  • Links: a download link is valid one month; access protection is on by default; an OData feed always contains all rows; tasks close automatically when the link expires.
  • Query exchange in the group: irreversible, duplicate-checked. Extending articles to the group is irreversible and needs a unique article number in the group.
  • Group data: sales data of partner pharmacies is deleted after three years. Suppliers are matched across branches only by identical names.
  • Cash book:
    • Period from ≥ 00:00 of the start day to < 24:00 of the end day.
    • Carry-over = opening balance + Z-receipts + pay-ins − payouts before the period start.
    • Cash balance = carry-over + period income − period expenses.
    • The opening balance is ≥ 0 and cannot be dated before the installation.
    • A payout amount must be > 0 and cannot be dated before the cash-book start.
    • A negative balance is the user's responsibility.
  • SEPA due-date correction:
    • Too early: set to the earliest possible date. First debits need 7 business days of lead time; recurring and final debits need 4 business days.
    • Too late: set to the latest possible date. First debits at most 13 calendar days ahead; all others at most 14 calendar days ahead.
    • A recurring debit must execute at least one day after the first debit of the same mandate.
  • SEPA files: one per creditor account × sequence type × execution date.
  • Invoice status coupling: exported → Paid; not accepted → Created.
  • Mandate: re-ordering with the "final" sequence type revokes the mandate at the next export; re-ordering with "first" or "recurring" reactivates it unless it was revoked manually.
  • Vouchers: expiry is informational only; clean-up books the remaining balance to income and makes the voucher unredeemable; default view shows the current statuses only.
  • Payback: points = round(eligible revenue), where eligible revenue is the sale's total of non-prescription items excluding fees, books, compounding, cash sales and non-material items. Cents 0–49 round down and 50–99 round up (24.39 € → 24 points; 24.50 € → 25 points). Only untransferred transactions are sent; the daily automatic send starts at about 09:00; a manual send includes today's transactions.

7. Configuration and settings​

ParameterScopeEffectDefault
Usage of till (Nutzung der Kasse)WorkstationClassifies a till as front-office or back-office for reports and cockpit metrics (service level, customer frequency).Per installation (front-office till)
Brightness of report printSystem / workstationPrint density of report printouts.Not stated
Summary receipts to evaluate (Auszuwertende Summenbons)Cash-book system parameterThe cash book uses Z-receipts or S-receipts.Z-receipts
Cash-book opening balance + validity startCash book (one-time)Base for the carry-over and the balance.Entered at first start
Picking-robot output connectionSystem maintenance, page "robot system"Default output point for the "retrieve from robot" action.Configured connection
Accounting export settings (collective accounts by alphabet / consecutive individual accounts)Accounting exportEnables automatic debtor-number options in result processing.Not stated
Payback user ID, password, server addressPayback system parametersAccess to the service centre; server prefilled with the centre's host.Server address prefilled
Staff-scheduling credentials and transfer modalitiesCompany master data, page staff schedulingEnables the portal and the data transfer.—
Company e-mail addressCompany master dataDefault recipient for scheduled report e-mails.—
Default creditor account (IBAN)Company master dataAccount named in SEPA files.—
Query visibility "revenue officers only"Per queryRestricts viewing to revenue officers + manager + report owner.Off
Exchange query in groupPer queryShares the query with the branches.Off
Row limit, footer aggregates, column widths and labels, outlinePer queryStored layout.None
Scheduled-task export pathPer taskFixed folder or default temporary pharmacy directory.Temporary directory
Download-link passwordPer linkAccess protection; can be changed within the password policy.Generated, protection on
OData refreshPer feedDaily or none.Not stated
SEPA export folderSystem<documents>/SEPA-Export/<timestamp>Fixed

8. Roles and permissions​

  • Reports:
    • "Start module": run predefined queries except revenue-relevant ones. In all predefined roles.
    • "Process result": requires start.
    • "Create query": in the report-owner role.
    • "Export query to Excel": in the report-owner role.
    • "Run revenue-relevant query": in the revenue-officer and report-owner roles.
    • "Evaluate across group": only in the corporate-control role.
    • The manager role contains all of these.
    • The overview page also names the roles "report owner" (creates reports) and "report-result owner" (processes results).
  • Link rights: "create link"; "show, refresh and delete link". Both are in the manager role by default.
  • Price mass changes (own purchase price, own selling price): the right "Article: edit prices" or the role manager or assortment manager.
  • Corporate control: automatic for people who are manager in every branch; otherwise activated by the vendor. Holders can grant "evaluate across group".
  • Query visibility: revenue-relevant own queries are visible only to revenue officers, the manager and the report owner.
  • Payment transactions: "start payment transactions", the payments-officer role, or manager.
  • Training portal: rights per role. The pharmacy-wide course overview needs a permission that the manager role includes.
  • Licences (function gates rather than user rights):
    • Reports Standard (free): display mode only, basic predefined queries, no Excel export, no Notes tasks, no import.
    • Reports Profi: edit mode, one-level grouping by a simple column, visibility flag, Profi queries, Excel export, Notes tasks, calculated columns, article deletion. A temporary trial is possible; queries saved during the trial become unavailable after it.
    • MMR Standard (requires Profi): MMR overview and the Pharmacies/Branches category, all predefined MMR queries, own queries without MMR fields, outlines up to three levels including complex fields, a monthly printed MMR report.
    • MMR Profi (requires MMR Standard): create and edit MMR queries; profile-group filters.
    • Cockpit Profi: cockpit-marked queries.
    • Other paid modules: payment transactions, Payback, staff scheduling, MMR overview.

9. Integrations, hardware and external services​

  • Notes module: task control, calendar, messages ("automatic tasks" folder), internal e-mail with prefilled link messages, info centre.
  • Cloud export service of the vendor: download links and OData feeds on a vendor API host, with password protection, availability periods and usage logs. Consumed by spreadsheet programs (Excel, LibreOffice, Numbers, Power Query, pivot tables).
  • E-mail: scheduled report delivery with optional encryption password.
  • Printers: report prints and label printers (price, shelf, base-price labels).
  • Picking robot (automated dispensing system): retrieval jobs with output point and priority.
  • Blister machine flag; care-home structures.
  • Accounting export (DATEV): debtor and creditor account numbering; voucher clean-up bookings.
  • DMS: cash-book pay-in and payout documents, voucher settlements, till closing.
  • Banking: SEPA XML files uploaded manually through the pharmacy's online-banking software. There is no direct bank interface.
  • Loyalty programme: an encrypted daily file to the wholesaler's pharmacy service centre, which forwards it to the programme operator and returns feedback. The till needs a barcode scanner that can read alphanumeric codes.
  • External staff-scheduling SaaS: periodic sales-data feed per pharmacy keyed by customer key.
  • Training platform and companion mobile staff app; a web browser is required.
  • Pharmacy group (Verbund) infrastructure: cross-branch queries, query and article exchange, contact exchange, voucher settlements.

10. Printouts, reports and exports​

  • Report printout: selected or all rows; optional legend (query description + column explanations); scale to page width; outlines included; brightness parameter.
  • PDF export: header with the description and changeable criteria; row count; column and filter descriptions at the end; legend optional; file or one-month cloud link.
  • Excel (xlsx) and CSV: file or link; CSV headers optional.
  • OData feed: daily or one-off; all rows.
  • Query definition export (.abfrage).
  • Scheduled outputs: printouts (optionally with legend), e-mails, PDF, Excel and CSV files.
  • Article labels: price, shelf/location (optionally own purchase price), base-price.
  • Cash-book report: per tax rules; filtered extracts list their filter criteria.
  • SEPA XML direct-debit files (pain format implied, not named) and regenerated copies.
  • Voucher overview printout; voucher reprint.
  • Training certificates: course overview, e-prescription licence, custom certificates.
  • Printed monthly MMR report (MMR Standard).

11. Dependencies on other modules​

  • Till / POS: Z- and S-receipts, payment types direct debit and immediate invoice, loyalty card capture, voucher sales and redemption, instant discounts, price-control dialog.
  • Invoicing (Faktura): invoices, invoicing models, permission, separate invoice, invoice statuses Created and Paid.
  • Sales management: sales details, cancellations, transaction chains.
  • Goods logistics / purchasing: shopping carts, cart determination, order-quantity optimisation model, dispo time, returns, sub-orders, emergency-duty stock.
  • Article management: stock status, storage data and locations, expiry dates, own prices and calculation rules, article classifications, discontinued and permanent-procurement flags, article number assignment.
  • Contacts: customer status and roles, classifications, care-home structures, health-insurance status and exemption, discount models, coupons, payment-transaction tab (accounts, mandates), contact exchange.
  • Medication management and blistering.
  • Notes: tasks, calendar, messages, mail.
  • Role and permission management (workstation protection); company master data.
  • Cockpit (KPIs, Cockpit Profi queries); fixed evaluations (Auswertungen); DMS; DATEV export; customer information and tasks (customer selections).
  • Picking robot configuration (system maintenance).
  • Branch and group configuration (vendor-managed).

12. Portability notes​

  • Generic and directly reusable:
    • The metadata-driven query builder: categories, typed fields, condition dialogs, AND/NOT blocks, OR multi-select, relative periods on completed units, point-in-time snapshots, aggregate filters that do not change the row set, query-scoped variables with per-usage adjustments, aligning shared definitions, calculated columns, three-level grouping and fan-out, time divisions, footer aggregates, row limits.
    • Query sharing and export files; revenue-sensitive visibility.
    • Scheduled report jobs with frozen parameters and pre-run validation.
    • Cloud links with expiry and passwords; OData feeds for BI tools.
    • Mass actions on result sets that reuse single-record operations behind a safety prompt.
    • Dynamic versus static customer selections.
    • Management reports linked to actionable work lists.
    • Cash book derived from till closings; value-voucher lifecycle and breakage write-off; staff-scheduling export; training portal.
    • For Shefa these map naturally onto a PostgreSQL query-definition schema with server-side SQL generation, and onto an offline-tolerant POS whose closings feed the cash book.
  • Germany-specific, with the general idea underneath:
    • Cash book per German tax rules (Z-receipt based, handed to the tax advisor) → an auditable cash ledger reconciled with fiscal till closings; owner withdrawals and bank deposits as explicit cash movements.
    • SEPA direct debit (mandates, FRST/RCUR/FNAL, lead times of 7/4 business days and a 13/14-calendar-day window, return codes) → bank-collection batch files with an authorisation lifecycle, lead-time validation and return reconciliation. In Syria the equivalent might be bank transfer or mobile-wallet collection, but the batch, reconcile and re-collect flow carries over.
    • DATEV debtor and creditor ranges (10000–69999 / 70000–99999) → sub-ledger account numbering conventions for an accounting export.
    • Co-payment exemption and insurer status mass reset → payer-status fields with validity periods and a year-end bulk reset.
    • Federal medication plan flag → a standard printable medication plan per patient.
    • PAYBACK via the wholesaler's service centre → an external coalition loyalty programme with a clearing intermediary, eligibility exclusions (no points on prescription items and fees) and deferred confirmation.
    • Drug-database purchase price, article numbers (PZN), stock statuses (POS/POR), dosage-form codes → national drug master data and stocking classifications.
    • Tax-audit export and till inspection (listed in the menu only) → a regulator data-access export.

13. Open questions​

  • The licence naming is inconsistent across the pages. Edit mode is said to need "MMR", query creation "MMR Expert", outlining "MMR-Reports", while the licensing page assigns edit mode to "Reports Profi". The exact gating is unclear.
  • The licensing page says that even Reports Profi cannot "import predefined evaluations", while the query-management page says predefined queries can be imported (with Profi). Contradictory.
  • The cash-book pages on correction bookings and filtering are referenced but not in this slice. The kind of corrections allowed and their audit trail are unknown. It is also unclear whether payouts can be edited or cancelled once entered.
  • The cash book's handling of non-cash payment types and of multiple tills (per-till versus pharmacy-wide balance) is not described; the opening balance is pharmacy-wide.
  • The exact semantics of Z- versus S-receipts belong to the till chapter. Why one would switch the cash book to S-receipts is not explained.
  • The full list of fields per result category and the complete predefined-query catalogue are not in these pages; the table in §4.1.21 lists only the names that appear.
  • Result-processing groups for the employees, vendors, goods-receipts and credit-notes categories are not described.
  • The SEPA XML schema version and batch-booking options are not specified, nor how business days (holidays) are computed.
  • How "accepted" or "not accepted" affects receivables or dunning beyond the invoice status is not described.
  • The loyalty exclusion "cash sales" (Barverkäufe) is ambiguous: it may mean anonymous or specific sale types. How goodwill points are awarded (where they are entered) is not described.
  • Voucher evaluations, reprint, outgoing settlement creation, and voucher sale and redemption are referenced pages outside this slice.
  • The help gives a German IBAN as "25 characters" while its example has 22 alphanumeric characters (27 with spaces). This looks like a counting error in the source.
  • The defaults for OData availability and the duration of feed series are not given.
  • The meaning of the stock statuses POS, POR and "negative article" is assumed from the context of other chapters.

14. Source pages​