Skip to main content

Supplier orders, goods receipt and supplier returns (Warenlogistik: Bestellungen, Wareneingang, Retouren)

1. Purpose and scope​

This chapter covers the back half of the purchasing cycle in the IXOS goods-logistics module (Warenlogistik):

  • Orders (Bestellungen): what happens after a basket has been sent to a supplier. This includes the open-orders overview, manual orders (phone, fax, rep), editing order lines, handling the supplier's electronic response (Rückmeldung) line by line, re-routing shortfalls to other suppliers, delivery dates, and orders imported from purchasing cooperatives.
  • Goods receipt (Wareneingang): capturing a delivery against one order or independently of orders. Covers scanning, importing from a picking robot, a mobile scanner or an electronic delivery advice (Lieferavis); expiry and batch capture; securPharm verification; the mandatory and optional difference checks; and booking as stock-only or stock-plus-value. Also covers price calculation at booking and distribution to tours, care homes and wholesale customers.
  • Supplier returns (Retouren): return orders and buy-back orders (Rückkaufaufträge), return reasons, quick capture, electronic return request and announcement (Retourenavis), return slips and packing lists, destruction instead of shipment, credit-note booking (single, collective and automatic reconciliation), return compensation in goods, and write-off of uncredited returns.

Other researchers cover the earlier stages: reminder list (Merkzettel), basket (Warenkorb), automatic order proposal, online availability inquiry, back-order management (Nachliefermanagement), the Deliveries tab and Archive in depth, supplier master data, and the securPharm and documentation-management modules. Where these pages depend on them, a one-line pointer is given.

Every page in the manifest describes the user's view of the help. Where something a designer needs is missing, it is listed in section 13.

2. Key concepts and terms​

German termEnglishMeaning
WarenlogistikGoods logisticsModule for purchasing, receiving and returning goods. Its stages (tabs) are reminder list, basket, orders, deliveries, returns and archive.
MerkzettelReminder listPre-basket list of items to order. Includes a defect note (Defektnotiz) for unavailable items. An order can be pushed back to this status.
WarenkorbBasketDraft order per supplier, waiting to be sent.
BestellungOrderLines sent to (or manually recorded for) one supplier. Stays open until fully closed by goods receipts.
UnterauftragSub-orderPart of one order sent with its own order number, so the supplier packs and invoices it separately (for example vending/robot items, pickups, blood products, open-selection items, behind-counter items, other items).
Auftragsart (A.-Art)Order typeNormal (blank), SO special order, ST batch order, VR forward/stock purchase, ZT timed order. Returns use Normal or RK (buy-back).
RückmeldungSupplier responseElectronic reply to an order, per line: delivered, short, via network, back-ordered, substitute, error.
FehlmengeShortfallQuantity the supplier reports it cannot deliver, or that is missing at goods receipt.
Defekt / DefektgrundDefect / defect reasonSupplier's reason why an item is unavailable.
Verbund (VB)Network deliveryWholesaler delivers from another of its branches. The response shows "000xVB möglich", where x is the quantity possible via the network.
Dispo / NachlieferungDispo / back-orderSupplier schedules the quantity for later delivery.
Ersatz- / NachfolgeartikelSubstitute / successor articleA different article delivered instead of the one ordered.
Naturalrabatt (Nara)Free goodsExtra packs delivered free of charge.
EK, Brutto-EK, Netto-EKPurchase price, gross, netLine purchase price before supplier discounts; net is after manual discounts.
ABDA-EK / Apo-EKList pharmacy purchase priceOfficial list purchase price from the national drug database.
prog. eff. EKForecast effective purchase priceExpected net price after condition agreements and offer lists.
MSV3 (1.0 / 2.0)German wholesaler ordering protocolElectronic ordering, availability and response protocol. Version 2.0 adds delivery advice, return advice and special days.
LieferavisDelivery adviceElectronic delivery note (advance shipping notice) sent before the goods arrive.
GegenscannenCounter-scanScanning the received packs against a delivery advice.
SondertageSpecial daysDates on which the supplier's order windows deviate from the regular ones (for example regional holidays).
VertragsdatenContract dataSupplier-published order windows, regular delivery times and capabilities (for example whether buy-back is accepted).
Wareneingang (WE)Goods receiptCapture and booking of delivered goods.
Lieferung / LieferscheinDelivery / delivery noteDelivery document. Order-independent receipts start from it.
Muss-DifferenzMandatory differenceDeviation that must be resolved before booking: not ordered, too many, too few, none delivered, or no purchase price.
Kann-DifferenzOptional differenceDeviation that is informational: expiry too short, negative article without back-order, substitute/successor, narcotics documentation.
WertbuchungValue bookingBooking that posts stock and updates purchase and retail prices, using invoice data.
BestandsbuchungStock bookingStock-only booking (invoice missing). Value booking follows later.
Kommissioniersystem (KS) / KommissioniererPicking robot / automated dispensaryAutomated storage. It can report what it stored and eject packs.
Abholung / AbholscheinPickup / pickup slipCustomer-reserved goods awaiting collection.
TerminbestellungAppointment orderOrder for a customer, due by an agreed date.
Lagerstatus POS / POR / NegativartikelStock statusStock-keeping modes. POS and POR are both stocked modes (presumably two replenishment methods: POR pharmacies can use physical reorder cards; the exact difference is not defined in these pages). A negative article is not kept in stock.
RetourenauftragReturn orderDocument grouping the lines returned to one supplier.
Rückkaufauftrag (RK)Buy-back orderOffer to the supplier to buy goods back. Stock stays with the pharmacy until accepted and returned.
RetourengrundReturn reasonCause plus originator code: Apo (pharmacy) or Li (supplier).
RetourenscheinReturn slipPrinted document that travels with the returned goods.
PacklistePacking listPrintout of an open return order's lines, used for picking.
Gutschrift / SammelgutschriftCredit note / collective credit noteSupplier credit for returned goods. A collective credit settles several return orders.
ARA (Automatischer Retourenabgleich)Automatic return reconciliationMonthly electronic credit statement from wholesaler GEHE, auto-matched to open returns.
Retourenavis / Retourenanfrage / -ankündigungReturn advice / return request / return announcementMSV3 2.0 electronic return authorisation. The request is non-binding; the announcement is binding.
RetourenausgleichReturn compensationSupplier compensates returned goods with other goods instead of money.
Abschreiben / AbschreibebuchWrite-off / write-off bookWriting off returned goods that were not credited, and the log of write-offs.
VernichtungsprotokollDestruction protocolProof that the pharmacy destroyed goods instead of shipping them back.
BtM / BtM-AbgabebelegNarcotic / narcotics delivery documentControlled drug and its official transfer-form number.
securPharmGerman node of the EU falsified-medicines verification systemVerifies 2D DataMatrix pack identifiers (PZN, serial number, batch, expiry).
PZNPharmazentralnummerGerman national article number.
SortimentssteuerungAssortment controlRule engine that lists and delists articles. Items it affects are shown in blue.
Gemeinsame BestellungJoint orderOne order placed for several pharmacies in a branch/partner network.
Einkaufskooperation (DIREKTplus, apokontor)Purchasing cooperativeBuying group whose web-shop orders are imported into IXOS.
Überweiser(-Großhandel)Remitting wholesalerWholesaler through which a direct-vendor delivery is invoiced and settled.

3. Data model​

The help describes screens, not tables. The entities below are inferred from the fields shown.

3.1 Supplier (relevant attributes only; full master data in another chapter)​

  • Type: wholesaler (Großhändler), vendor/direct supplier (Anbieter), or branch/partner pharmacy. A contact can hold the "supplier" role and the "vendor" flag.
  • Send parameters: protocol (MSV3 1.0 or 2.0, fax, none), MSV3 service provider, and credentials.
  • Delivery parameters (Lieferparameter): regular delivery times, delivery duration for direct suppliers, and the remitting wholesaler (Überweiser-Großhandel) used to settle direct-vendor turnover.
  • Settings: preferred delivery-advice capture mode (counter-scan or read-in), return-slip sort order (grouped by document number, or alphabetical), and "create destruction protocol for returns".
  • Condition agreements: minimum order value, minimum pack count, fees (for example a cool box), cash discount, offer lists with priority and a preferred flag.
  • Addresses: a standard address and an optional deviating delivery/warehouse address (printed on return slips).
  • Contract data fetched from the supplier: order windows, special days, and whether buy-back is accepted.

3.2 Purchase order (Bestellung)​

  • Fields: supplier; order date-time (from send parameters; manual orders have none); delivery date-time (from the MSV3 response, else computed from delivery parameters, or entered manually); MSV3 order number; order type (Normal/SO/ST/VR/ZT); source flags (online order, joint order, cooperative DIREKTplus/apokontor, manual); info text; manual discount flag.
  • Derived fields: Pos (number of lines still to deliver) and Value (purchase value of lines still to deliver).
  • Indicators: goods receipt already captured; at least one line back-ordered or on another delivery note; unprocessed responses exist; transmission error.
  • Has 1..n sub-orders. Each sub-order has its own supplier-side order number and is booked separately at goods receipt.
  • Lifecycle: reminder list → basket → order (sent or manually created) → partially received → fully received (leaves the overview; receipts go to Deliveries or Archive). An order can be set back to "reminder list" or "basket". Orders can be merged (supplier change at order level) or deleted.

3.3 Order line​

  • Fields: article (PZN, or free text for items not in the article master); ordered qty; free-goods qty (Nara); EK (gross); net EK after manual discounts; manual discounts; article note (Artikelhinweis); order type.
  • Links: customer link (customer order, pickup slip, appointment, courier or post back-order) and an assortment-control flag.
  • Response state: none, unprocessed, or processed.
  • Substitute link: a substitute line points to its original. Deleting the original deletes the substitute.
  • Derived: Open qty = quantity still expected given ordered qty, the response and postings.
  • Display attributes taken from the article master:
    • Dispensing restrictions: Rx, narcotic, blood/haemophilia product, T-prescription, substitution exclusion, clinic-only, pharmacy-only, monitoring required.
    • Import status: original, EU parallel import, or Hilfstaxe (pharmacy compounding price list).
    • Article-info flags: current (under 6 months old), own, other.
    • Distribution flags: offer exists, only via vendor, supply-critical active ingredient.
    • Storage requirements; back-order origin icons (back-order/appointment, courier, post, prioritised in that order).

3.4 Supplier response (Rückmeldung)​

  • Header-level outcomes: transmission error (must be acknowledged); MSV3 order-level error with error code and text; minimum order value not reached.
  • Line-level fields:
    • Ordered qty, shortfall qty, and delivered qty of the original article.
    • Immediately deliverable qty with its tour, network qty with its tour and delivery time, and dispo/back-order qty.
    • Substitute PZN, defect reason, error or additional info, and a tour-deviation flag.
    • Delivery-instruction flags set by the user: allow network, allow back-order, allow dispo.
    • Availability icon from automatic inquiries at other suppliers.
  • Status: unprocessed → processed. A line becomes processed by moving the shortfall, accepting it, taking an offer, ordering a comparison article, or by automatic rebooking.

3.5 Delivery advice (Lieferavis, MSV3 2.0)​

  • One per physical delivery, available at the latest when the goods leave the supplier.
  • Fields: delivery-note number (barcode on the note and on tote labels), order ID (may be "picker"), lines with announced packs, optionally batch and expiry per line (more than one batch per article splits into separate lines), and an optional PDF copy.
  • Linked to exactly one delivery/receipt.

3.6 Delivery / goods receipt (Lieferung / Wareneingang)​

  • Header: supplier; delivery-note number and date; capture mode (manual, counter-scan advice, read-in advice, picker, mobile scanner, order data); linked order(s); joint-order flag; info text.
  • Booking data: invoice number and date; or delivery-note number and date for a stock-only booking. Also booking value split by VAT class (19%, 7%, 0%) and total; fees; cash discount %; value date; "remitted from" (direct vendor) and "booked to" (wholesaler); linked DMS documents.
  • Receipt line fields:
    • Article; delivered qty; free goods; return qty (returned straight from the receipt) and its reason.
    • EK (gross or net), expiry, batch, counter-scan status (full, partial, none).
    • Substitute link, distribution to tours, care homes or wholesale customers, and an assortment-control flag.
  • States: captured (open) → stock-booked (moves to Deliveries) → value-booked (moves to Archive). Booking happens per sub-order.

3.7 Difference (Differenz)​

  • Generated by comparing receipt lines with the ordered lines (or with the delivery advice).
  • Fields: kind (mandatory or optional); type (shortfall, over-quantity/not ordered, article without EK, expiry too short, negative article without back-order, substitute/successor, narcotics documentation); expected qty; delivered qty; chosen resolution and its parameters (target basket, credit request, charge flag, defect-note flag, substitute article, statistics transfer, delivery-document number, stock status).
  • Can be reset and recomputed.

3.8 Return order (Retourenauftrag)​

  • Fields: supplier; order type (Normal or RK buy-back); status; return date; creation date; info text; "return to current supplier" flag; "all packs will be destroyed" flag; default return reason; MSV3 reference number and tour (as info text for MSV3 2.0 returns).
  • Derived: Pos (count of unbooked lines) and Value (purchase value of unbooked lines).
  • Statuses: open → (buy-back only: sent) → returned → booked. "Booked" is reached only when every line is booked.
  • Manual status change allows only open and returned. A destruction-flagged order is locked after it is returned.

3.9 Return line (Retourenposition)​

  • Fields:
    • Article (or free text), qty, expiry, batch, target supplier, delivery date.
    • Document number (looked up in this order: delivery advice, then delivery note, then invoice) and a goods-receipt link flag (WE).
    • Booking EK of the linked receipt; Ret-EK (expected refund per pack) and Ret-value (qty × Ret-EK).
    • Return reason; free-text "return info" (only for reason "Other").
    • Captured/changed timestamps and user; MSV3 reason sent; return-request status.
  • Booking fields: credit qty and credit value per pack; booked qty. A partially booked line splits into a booked part and an unbooked remainder.

3.10 Return reason​

  • Structured as cause plus originator: Apo (pharmacy) or Li (supplier). Recall, buy-back and off-market have no originator.
  • Causes:
    • Order error, not collected, approval order, no longer needed, prescription changed, discount changed.
    • Expiry, industry return, expiry too short, expired, pack damaged, customer complaint.
    • Over-delivered, not ordered, consignment goods, warehouse error, shortfall, credit request, other.
    • Recall, buy-back, off market.
    • "Data migration" covers unknown legacy combinations after switching systems.
  • A separate MSV3-conform set is used for electronic return requests (mapping in section 6).

3.11 Credit note (Gutschrift)​

  • Fields: credit number; credit date (default today; fixed to the last day of the month for ARA); credit value split by VAT class (19%, 7%, 0%) and total.
  • Booked lines: return line, credited qty, credit value per pack.
  • A collective credit links several returned orders of one supplier. Booked credits are archived under the supplier.

3.12 Return compensation (Retourenausgleich)​

  • Fields: compensation document number and date (mandatory); the settled return lines with compensated qty; the compensation items (article, qty, EK, expiry, batch, possibly split).
  • Stock-only booking with no money value. Archived with its own icon; correction bookings are possible.
  • Also logged in stock control with the RA number and RA date.

3.13 Write-off record (Abschreibung)​

  • Fields: return line; written-off qty; value per pack; reason (expiry, loss, loss from discount contract, theft, damage, recall, buy-back, loss from return, or user-defined reasons).
  • Written to the write-off book.

3.14 ARA statement and task​

  • Monthly credit file from GEHE. On receipt, the system creates a task in the Notes module (status done or undone).
  • Credit lines carry qty and value per pack and are matched to returned, unbooked lines from the last 12 months.
  • Per-line match status: full match, qty mismatch, value mismatch, both mismatched, credit without return, return without credit.

3.15 Status summary​

ObjectStatesTransitions
Orderreminder list → basket → order → (partially received) → closedSend basket; create manually (New); set back to reminder list or basket (Order status); merge; delete; fully received
Responseunprocessed → processedMove shortfall, accept shortfall, take offer, order comparison article, automatic rebooking, acknowledge error
Receipt / deliverycaptured → stock-booked (Deliveries) → value-booked (Archive)Book stock only; book with invoice; book value later
Differencedetected → resolvedPer-type dialog; reset recomputes
Return order (normal)open → returned → bookedReturn (F12) or announce via MSV3; manual status open/returned; book credit or compensation
Return order (buy-back)open → sent → returned → bookedSend buy-back; delete rejected lines; return; book credit
ARA taskopen → doneAuto-done when everything is booked; manual done/undone

4. Features​

4.1 Orders overview (Bestellungen-Übersicht) [GENERIC]​

  • Purpose: monitor every order not yet fully received and act on it.
  • Shows: supplier, source icons (online, joint, cooperative), order time, expected delivery time, MSV3 order number, order type, open line count, open value, and indicator icons (receipt started, back-order or other delivery note, unprocessed responses, transmission error, manual discount).
  • Filters:
    • By supplier class: wholesalers, direct vendors, branch/partner pharmacies, or all.
    • Back-order and dispo orders are hidden by default; a filter indicator shows this, and "All order types" re-shows them.
    • Rows from joint orders triggered by another network pharmacy (not yet received there) appear greyed.
  • Delivery-time display rule:
    • Use the time sent in the MSV3 response.
    • Otherwise compute the next regular delivery slot from now. Show "not today" if all of today's slots have passed (example: now 16:00, slots 13:00 and 15:00 gives "not today").
    • Also show "not today" when the response allows only network or dispo delivery, or when no regular delivery time is configured.
    • If the order cut-off has not passed, show the next possible delivery time even if the order time has passed.
  • Overview actions:
    • Search, new order, delete order, edit, info text, capture items.
    • Print order log, fax order or labels.
    • Supplier change, which here means merging the order into another order.
    • Order status (set back to reminder list or basket); new joint order (only in a branch network).
    • Delivery date (direct suppliers); change order type.
    • Jump to invoicing (Faktura) orders; view responses; open supplier contact.
    • Reopen a saved order-proposal hit list; open back-order management (other chapter).
  • List configuration: columns are configurable, for example stock status and storage-type icon.

4.2 Manual order (Neue Bestellung) [GENERIC]​

  • Trigger: New (F3) in the overview. The user picks a supplier, then captures lines.
  • Use: recording goods already ordered by phone, from a rep, by fax and so on. Nothing is transmitted.
  • Rules:
    • Capturing order lines never changes stock.
    • An order is the prerequisite for an order-related goods receipt.
    • Lines added or changed in an existing order are not re-transmitted.
    • After a goods receipt has been captured, lines should no longer be added or changed.
  • Branch caveat: an order whose supplier is one of the pharmacy's own branches is not an inter-branch transfer. No invoicing order or delivery note is created in the delivering branch. Transfers use a basket addressed to the branch, or an invoicing order in the delivering branch (other chapter).

4.3 Order lines: capture and edit [GENERIC]​

  • Capture: enter a PZN or the start of a name (a hit list appears for names). A quantity prefix such as "15/ASS" pre-fills qty 15. Then qty, free goods, EK and article note. The minimum to save is article and qty.
  • Free-text items: items not in the article master can be captured as free text.
  • POR pharmacies with a card reader: inserting a reorder card, or typing a full PZN, saves the line immediately with no confirmation.
  • Edit: qty, free goods, EK and order type.
  • Hard rule: qty plus free goods may never fall below the shortfall reported by the supplier for that line.
  • Implicit save: pressing another function key saves the line implicitly.
  • Delete: deleting a line also deletes its substitute line.
  • Move line: supplier change (F10) moves a line to another basket or supplier. Not allowed for substitute-delivery lines.
  • Discounts: per-line manual discounts can be added (not for partner/branch transfers). The column label then becomes gross EK and a net EK column appears.
  • Detail pane while capturing:
    • Sales and lost-sales statistics for the current and two previous years. POS items count sales minus returns; POR items count purchases minus returns, or history-based when demand-statistics optimisation is on.
    • Stock, open back-order qty, prices, last delivery.
    • Assortment-control status (in changeover, delisted or listed on a date, stocked as an alternative to a back-order, temporarily listed by the defect automation for an unavailable article).
  • Price table: shows offers and condition-based prices per supplier and branch, with offer qty, free goods, negotiable-offer flag, preferred-list flag, forecast effective EK, and saving in EUR and % against the list price.
    • Sort by offer EK: negotiable offers first, then offer EK ascending, then qty ascending, then offer-list priority.
    • Sort by forecast effective EK: EK ascending, then qty ascending, then main supplier, then supplier name.
  • Use an offer: double-clicking an offer aligns the qty to the offer, applies the offer EK and moves the line into a basket/order of the offering supplier or branch. The "Offers" order query pops up only if a cheaper offer than the selected one exists.

4.4 Sub-orders (Unteraufträge) [GENERIC]​

  • A basket can be split into sub-orders. Each goes to the wholesaler with its own order number, is processed as an independent order, and is packed and invoiced separately.
  • Examples: vending/robot items, pickups, blood products, open-selection items, behind-counter items, other items.
  • Tabs filter the order and receipt per sub-order.
  • An item received but not ordered triggers a prompt to choose its sub-order.
  • Receipt booking runs sub-order by sub-order.

4.5 Supplier responses: processing (Rückmeldungen bearbeiten) [GENERIC concept; MSV3 transport DE-SPECIFIC]​

  • Trigger: responses arrive after the order is sent, or as an error when transmission failed. The order shows an unprocessed-response icon.
  • Gate: goods receipt for an order is blocked until all its unprocessed responses are processed. For order-independent receipt, the user is warned if any open order of that supplier has unprocessed responses.
  • Display:
    • By default only problem lines are shown; "also show deliverable items" adds the rest, for example to see tour info.
    • Per line: ordered, shortfall, delivered, reason.
    • Breakdown: immediate qty and tour, network qty with tour and time, dispo qty, substitute PZN, regular delivery time.
    • Availability icon from automatic inquiries at other suppliers (green means another supplier can deliver; the tooltip names it).
  • Actions per marked line (multi-select allowed; processed lines stay visible but locked):
    • Move shortfall (F10): to another basket or order, a specific supplier, or the defect note.
    • Accept shortfall (F11): confirm prompt. The response becomes processed and no difference will arise at goods receipt.
    • Offers: list "only my suppliers' offers" or "all offers". Choosing one moves the line into the chronologically next basket of the offering supplier.
    • Send via network (F7): re-sends marked lines with order type "network". Only when the reason reads "VB möglich".
    • Delivery instructions: for online/MSV3 responses, tick allow network / back-order / dispo, then "Send again" (F7) to confirm to the supplier.
    • Online inquiry / online order: lines answered "deliverable" are moved to a basket of the deliverable supplier (the preferred supplier if several).
    • Order comparison article: see 4.7.
    • Stock at branches/partners, article info and own info text, print responses, jump to the customer's contact.
  • Automatic effects of a response on the order:
    • Shortfalls reduce the Open qty.
    • Pos counts only deliverable lines.
    • An announced substitute or successor automatically gets its own order line, cross-referenced to the original.
    • A response naming a delivering wholesaler branch ("VB <branch>") automatically moves the network qty into another order or basket.
    • Depending on settings (section 7), fully undeliverable items stay visible or are removed; if nothing is deliverable the whole order is removed.
  • Order-level messages:
    • An MSV3 error is shown with its code and business text.
    • Minimum order value or pack count not reached: warned at send time if stored in the condition agreement; otherwise the supplier may say so in the response.
  • Tour deviation (MSV3 2.0): a line-level flag when, for example, cold-chain or narcotic items will come on a later tour able to carry them. The reason is shown as "tour deviation".
  • View processed responses: available later (Ctrl+F9).

4.6 Missing response for an online order [GENERIC]​

  • If no response arrives, the system polls automatically for 30 minutes.
    • Passively sent order: info-centre message. Actively sent order: on-screen notice. Either way the order gets a transmission-error icon.
    • Manual "fetch response" is available during and after the 30 minutes.
  • Outcomes:
    • Response arrives: info-centre success message (a manual fetch opens the response window).
    • No connection: info-centre "status could not be verified" (a notice when fetched manually). The user must call the supplier and must not simply re-order, to avoid duplicate deliveries and returns.
    • Supplier reports the order ID unknown (it checks the last 7 days): automatic mode re-sends the order in the next order window; manual mode asks whether to re-send or mark the response processed.

4.7 Comparison article from a response (Vergleichsartikel) [GENERIC]​

  • Purpose: replace an item no supplier can deliver.
  • Availability: only for unprocessed responses, so it requires "move shortfalls automatically" = No.
  • Behaviour:
    • Runs the same comparison search as at the point of sale, including the discount-contract search for customer-linked orders.
    • The chosen article is proposed with the same shortfall qty, in the basket chosen by the basket-determination model (the user can override).
    • Option "create defect line for the original": the original goes to the defect note, which is checked for availability 3 times a day and re-ordered automatically when available.
  • On OK:
    • Customer demands (customer link or pickup slip) are re-pointed to the comparison line.
    • The response becomes processed.
    • The comparison line is created in the target basket, plus the defect line if chosen.

4.8 Delivery date for late deliveries (Lieferzeit) [GENERIC]​

  • For direct-supplier orders (also branch transfers and wholesaler orders): enter a new expected delivery date.
  • Pre-filled from the supplier's configured delivery duration.
  • Order-quantity optimisation uses it, so other orders are sized to last until this one arrives.

4.9 Purchasing-cooperative order import [DE-SPECIFIC]​

  • Orders the pharmacy places in a cooperative web shop (DIREKTplus, apokontor) with industry partners are imported automatically every 30 minutes. Credentials are set in company master data, external services.
  • The imported order is flagged by icon and announced in the info centre. Joint orders are included if the cooperative supports them.
  • Supplier resolution: by the transmitted vendor number.
    • Known vendor: the order goes to that vendor, which is given the supplier role if it lacks it.
    • Unknown vendor: the order goes to a generic supplier named after the cooperative, typed as vendor.
  • The delivery date is taken only if unambiguous. Goods receipt can follow immediately.
  • Underlying idea: import orders placed in external buying portals so receipt and stock stay in one system.

4.10 Extended order search and print [GENERIC]​

  • Filters: supplier, supplier class, article, order type, article note, order date, delivery date.
  • Results: sortable; a checkbox per row selects rows for printing.
  • Print type: a document for the supplier (with an optional note, as for fax orders) or an internal hit list. Each is a separate configurable form.
  • Archiving: optional to the document-management system, configured in company master data.

4.11 Goods receipt capture (Wareneingang) [GENERIC]​

  • Two modes:
    • Order-related: pick an order, then capture. If nothing has been captured yet the capture window opens directly.
    • Order-independent: create a delivery from the delivery-note data on the Deliveries tab. The system matches lines to all open orders of that supplier. This is recommended with delivery advice, because it covers every order of one order window.
  • Capture methods:
    • Scan a barcode or DataMatrix, or type a PZN or name.
    • Lookup searches the supplier's open order lines first; most receipt items are already in the order. A name or "*" opens the "order-line hit list"; a PZN or EAN never does.
    • A quantity preset applies a fixed qty to every following scan until changed (for example 6 per scan for a carton).
    • "15/ASS" style qty prefix.
    • Import from a picking robot, a mobile scanner, a delivery advice, or the order data itself (copies all order lines including expiries; the user then corrects qtys and adds or deletes lines).
  • Per line: delivered qty, free goods, optional EK, expiry (with plausibility warning for past, too near or too far dates; an expired date can be accepted deliberately), batch.
  • DataMatrix: scanning fills expiry and batch and triggers background securPharm verification (licence required).
  • Running comparison: packs, lines and value (including manual discounts) of receipt versus order, or versus delivery-note data, shown continuously.
  • Detail pane:
    • Storage requirements (min/max temperature, cold chain, position, humidity, light) and storage locations.
    • Stock, reserved qty, list retail price or recommended retail price (shown with "#"), own retail price, assortment-control origin.
    • Customer-orders tab: open pickups and appointment orders for this article in this or other orders, with pickup numbers, customers and care homes. If a customer already collected part and got a new slip for the rest, the new slip number is shown.
  • Split line (Ctrl+F5): when packs differ in expiry, batch or EK. The new line takes qty, free goods (only if the original has free goods), returns (only if the original has a return qty), expiry, batch and EK. The original line is reduced automatically.
  • Return from receipt (F6 on a line):
    • Enter qty and reason: expiry too short (optional re-order to a chosen basket), breakage (optional re-order), no need, or approval order.
    • A "Return" column appears in the receipt.
  • Columns: configurable, for example stock status, retail price and line value net of all discounts.

4.12 Differences at goods receipt (Differenzen) [GENERIC]​

  • Detection: compares the receipt with the ordered lines (or with the delivery advice) of that supplier.
    • With MSV3 the comparison set is the lines that, per the response, ship on the same tour with the same order ID.
    • It also includes lines with no tour (back-order or dispo lines) when the receipt is not based on a delivery advice.
  • When: detection runs at booking. Mandatory differences open automatically. Optional differences open only if the "goods receipt" notice parameter is set, or via "Process differences" (F11).
  • Processing: differences can be processed any time before booking. "Reset differences" recomputes and discards earlier decisions, for example after bulk-marking shortfalls as "other delivery note" and then finding the missing box.
  • Grouping: mandatory differences are grouped as in order / not in order / in advice / not in advice.
  • Navigation: Edit opens the first line in a type-specific dialog; Next and Back walk the list; Finish ends.

Mandatory difference types and resolutions

TypeResolutions
Shortfall (too few or none). Single edit defaults to "take into delivered qty"; bulk "process shortfalls" (F6) defaults to "will be back-delivered / other delivery note" (recommended for MSV3).Take into delivered qty: raise to the ordered qty, with expiry/batch entry. Request credit note: a credit-request line is created in Returns, storing the invoice number and date entered at booking; optional re-order to a basket. Other delivery note: expected in another box or delivery; not charged. Will be back-delivered: optional "charge" when the note already invoiced it; the line stays at qty 0 so EK can be fixed on arrival. Accept non-delivery: book only what came; optional defect-note entry at booking. Order: add the shortfall to any basket, including another supplier's. Warehouse error: wrong product sent, right one invoiced; pair with an over-quantity line; optional re-order. Substitute article: pick the unordered delivered article as substitute, which leads to the statistics-transfer question.
Over-quantity / not orderedCaptured too many: delete the surplus. Free goods: not charged. Accept: charged. Return: with a "charge" flag; the return line auto-gets reason "not ordered".
Article without EK (no EK in receipt or on the article)Enter an EK manually, or treat the line as free goods.

With a delivery advice linked, resolutions that make no business sense are greyed out.

Optional difference types

TypeResolutions
Expiry too short (threshold = "expiry length" parameter)Return: removed from the receipt into a return order; the qty is still invoiced; optional re-order to a basket. Order: flag the qty for re-order, for example from another supplier, and decide later which to return. Accept expiry. Shows 3-year monthly sales.
Negative article without back-order (status negative or none, not part of a back-order)Set stock status POS, POR or negative (POS not selectable in POR pharmacies); leave blank to record a lost sale; set storage locations.
Substitute / successor"Transfer statistics" (only if both articles are POS or negative items; also re-points defect-note and appointment-note entries to the new article, with a notice) or "No transfer". Not possible at once while the old article still has stock or an open pickup. Confirmed after booking, where the new article's stock status can be changed.
Narcotics documentation [DE-SPECIFIC]Enter the narcotics delivery-document number (pre-filled for the following narcotic lines of the same order; no check of the per-document item limit) or "no number". The narcotics movement record is created either way. Only if the documentation-management feature is licensed and "document narcotics automatically" plus "ask document number on narcotics receipt" are on. Underlying idea: capture the controlled-substance transfer document reference on every receipt of a controlled drug.

4.13 Booking a goods receipt (Wareneingang buchen) [GENERIC; VAT rates DE-SPECIFIC]​

  • Order of steps: booking runs per sub-order, after differences are resolved.
  • Value booking (default):
    • Enter the invoice number and date (optionally pick the document from the DMS, which fills the number).
    • Booking values before tax split into 19%, 7% and 0% VAT; the total must match the supplier's document. "Booking value" (F5) lets the user edit the split.
    • Fees chosen from supplier conditions; cash discount % (disabled if special conditions exist); value date (defaults to invoice date).
    • "Remitted from" (direct vendor) and "booked to" (default: the supplier's remitting wholesaler).
    • Comparison of lines and value for delivery versus order.
    • Warning when the booking value exceeds the list purchase price, to catch typos.
    • Effects: updates booking EK, average EK and effective EK, and the calculated retail prices; the receipt moves to the Archive.
    • With the ELO DMS, extra data can be sent: gross invoice value (computed) and payment type (default "invoice", "direct debit" if the supplier has a debit account).
  • Stock-only booking ("invoice missing" checkbox):
    • Enter the delivery-note number and date.
    • Stock is posted, prices are not touched, and the receipt moves to the Deliveries tab for later value booking.
    • With a DMS, the scan dialog opens to archive the delivery note. MSV3 delivery notes are passed to the DMS scan dialog automatically.
  • After booking: the statistics-transfer confirmation appears for substitute lines.
  • Robots and joint orders: for a joint order received through a picking robot, only packs stored per the storage list (exact expiry) are ejected for the branch.

4.14 Price calculation at value booking (Preiskalkulation) [GENERIC]​

  • Check: at value booking, the system checks that every item has a retail price and that the price meets the target markup (parameter "EK markup %").
  • Window: lists the failing items with reason "no retail price" or "markup too low", plus pack-size code, stock status, stock, EK and retail price.
  • Action: for OTC and free-sale items the user jumps to the article's pricing page, enters an own price or applies a calculation rule, then pages through the flagged items. Fixed items are value-booked and leave the list.
  • Labels: can be printed from the same window.
  • Archive: the same window is reachable from an archive entry ("calculate own retail price").

4.15 Delivery advice: electronic delivery note (Lieferavis) [DE-SPECIFIC protocol; generic idea = ASN / despatch advice]​

  • Fetching: automatic every 30 minutes during opening hours. If an advice is not yet present when the goods arrive, scanning the delivery-note barcode or typing its number fetches it immediately.
  • Linking: linking the advice to the receipt imports all announced lines with their packs, plus batch and expiry where sent. An article with several batches is split into several lines.
  • Capture variants:
    • Order-independent with counter-scan (default, preferred):
      • Scanning the note or tote barcode in any tab opens the existing delivery in counter-scan mode, or creates a new one from the advice.
      • Advices flagged "picker" pre-select picker mode and the matching robot storage number.
      • Open = announced packs; Qty = packs scanned so far.
      • Scan-status filters: complete / partial or over / not scanned. Completed lines are hidden by default (parameter).
      • Focus jumps to the expiry field after the first pack of an article.
      • Over-delivered or unscannable items are captured in a separate field.
    • Order-independent "read-in" without scanning: the advice lines are taken over directly; the user checks prices and expiries.
    • Order-related: no counter-scan. If several orders of the same MSV3 order window arrive as one delivery, they must first be merged into one order.
  • Late shortfalls: a shortfall found while the supplier was packing (not in the earlier response) creates a high-priority task "shortfall reported by supplier" in the Notes module. There is no automatic re-order.
  • PDF copy:
    • Downloaded automatically when the advice arrives, or when it is linked at the start of a receipt.
    • If linked only later via the delivery-note number in the booking window, a background job polls every 30 minutes.
    • Stored permanently with the delivery and openable from the Deliveries and Archive tabs or the receipt header.
    • If several deliveries share one invoice (joint value booking), all their PDFs open together.
  • Prerequisite: the supplier is switched to the MSV3 2.0 service-provider entry (1.0 credentials are reused). After a successful connection test, contract data is re-fetched.

4.16 Special days / order windows (Sondertage) [GENERIC idea; MSV3 transport DE-SPECIFIC]​

  • The supplier's contract data (order windows) is checked daily and synchronised when it changes. Each change is announced in the info centre and in Notes.
  • Special days override the regular order windows for a specific date.
    • Notice period: up to 12 months ahead, at the latest 3 calendar days before.
    • "No order times" on a special day means no automatic baskets are created that day.
    • Special days can be changed or withdrawn by the supplier with the same 3-day notice; when withdrawn, the regular windows apply again.
  • Short-notice exceptions, agreed by phone, are pulled manually via contract data and can apply from the next day.

4.17 Picking robot integration at receipt [GENERIC]​

  • Import: "Import delivery → picker" reads the packs the robot stored under a storage-list or delivery-note number.
  • WWKS2-protocol robots: stream storage from the first pack and the operator cannot "end" storage, so import and book only after every pack is stored. Delivery-note numbers in barcodes are matched to link the advice to the delivery.
  • Storing pickups in the robot (parameter "store negative articles", default off):
    • Pickups of non-stock items are stored in the robot and the robot is recorded as storage location. POR items are never stored.
    • When the pickup is resolved, or cleaned up for return, the item is ejected.
    • The robot location is removed automatically when a non-stock item's robot stock reaches 0 (not for POS items).
    • If the customer refuses a delivered substitute, the substitute is not auto-ejected; it must be captured as a return and ejected manually.

4.18 Mobile receipt scanner (Artikelscan.mobil) [GENERIC]​

  • Device: a handheld app connected to IXOS over WLAN.
  • Steps: create or open a delivery note (scan or enter its number), assign the supplier (preferred suppliers listed), scan articles (expiry prompt with default highlighted when expiry maintenance is on; pickups shown with qty), close the note.
  • In IXOS: import the closed note into an order-related or order-independent receipt, then check and book.
  • Enlarged display: a workstation parameter shows an enlarged tour or home view per scan for users standing away from the monitor (short name, next tours or homes first, total and needed qty).

4.19 Distribution at receipt: tours, care homes, wholesale customers [GENERIC]​

  • Tour / care-home view (licence for courier/delivery management; parameter "show additional tab"):
    • Per tour or home unit: needed qty from customer demands, total captured so far, qty in this receipt (editable), complete/incomplete icon (tour can be packed), and a pencil icon when the qty was set manually (no more auto-distribution to that tour or home).
    • An icon marks quantities sitting in other orders and opens an order-information view.
    • A yellow warning appears when the captured qty does not cover the demands.
    • A table shows other demands: pickup, pickup terminal, courier, post, appointment order.
  • Wholesale customers (wholesale licence; parameter "batch distribution to wholesale customers"):
    • Columns: ordered per customer, proposed delivery (recomputed on every new batch line or qty change), distributed total and distributed per line.
    • Auto-distribution happens only when unambiguous: exactly the ordered qty in one batch, or a single ordering customer.
    • Excess over the ordered qty goes to stock. Packs already returned from the receipt reduce what can be distributed.
    • A yellow warning marks incomplete distribution.

4.20 securPharm at goods receipt [DE-SPECIFIC; generic idea = serialisation/anti-counterfeit verification]​

  • Status window before stock posting (parameter: default shows only problem packs; "never" hides it):
    • Header counts per status and total scanned. Only scanned packs count, so every pack must be scanned.
    • Per pack: batch, expiry, serial number, status.
    • Statuses: ready to dispense, expired, dispensed elsewhere, sold in own pharmacy, recalled, destroyed, exported, unknown identity, query failed, query pending. They are grouped as not dispensable / pending / OK.
    • Checkboxes filter by status.
  • Logging: all packs are logged in securPharm management for follow-up.
  • Outage: the status window shows a notice and a step guide, including a link to the system status page. The user captures and books as normal; verifications are retried later automatically.
  • Returns: packs whose securPharm status is sold, dispensed or destroyed are decommissioned and cannot be returned to a wholesaler (warning). Scanned packs in a return are logged as "return".
  • Underlying idea: verify serialised packs on receipt and before return, queue verification while the national hub is offline.

4.21 Returns overview and return orders (Retouren) [GENERIC]​

  • Overview:
    • Lists return and buy-back orders: supplier, info icon, status (open, sent [buy-back only], returned, booked), return date, creation date, type (Normal or RK), Pos and Value of unbooked lines.
    • The return date is the date set to "sent" for buy-back orders and to "returned" otherwise.
    • Collective credits show no return or creation date.
    • Return-compensation capture works only on orders in status "returned".
    • Supplier-class filter as for orders.
  • Five-step process: create order → capture lines → "Return" (status returned, return slip print offered) → ship goods with slip (do not change afterwards) → on credit, book lines (single order or collective credit) → booked lines and order move to the Archive.
  • Create:
    • New → pick supplier or vendor (standard or phonetic search; tabs for suppliers and vendors; can create a contact or open contact details/info) → Normal order or Buy-back order.
    • Header controls: "return to current supplier" (default on), "all packs will be destroyed" (vendors only, open orders only), default return reason.
  • "Return to current supplier" off: each line goes to the supplier of the article's last delivery. The line is moved into that supplier's return order, which is created if missing; the user chooses if there are several.
  • Line capture:
    • Scan a DataMatrix or barcode, or type the article (free text allowed).
    • Enter qty and reason (minimum); Ret-EK is optional.
    • Document number, delivery date and the receipt link are filled automatically.
  • Edit: two list views. View 1 covers dosage form, unit, expiry, batch, booking EK, delivery date, document number and reason. View 2 covers PZN, capture/change dates and user, receipt link, delivered versus already captured (red when exceeded), Ret-EK and Ret-value.
  • Detail pane: storage icons, delivered/captured, PZN, stock, open back-order qty, booking/list/effective EK, last supplier and qty, storage location, audit info, and current plus previous-year sales and lost-sales statistics (purchase-based for POR).

4.22 Return line rules and quick capture [GENERIC]​

  • Stock effect: capturing a line in a normal return order immediately deducts stock. Deleting the line or the order restores it.
  • Quantity checks:
    • Warning when the return qty exceeds stock plus reserved qty.
    • Reserved stock (back-order qty) can be returned only if the reserved qty covers the return qty.
    • Red "delivered/already captured" display when more is returned than was delivered.
  • Return info: reason "Other" (pharmacy or supplier) opens a free-text "return info" (pick from the last 10 entries). It prints on the return slip instead of the reason and is cleared if the reason changes.
  • Quick capture (Ctrl+F3):
    • Capture lines without first choosing an order. Each line defaults to the article's last supplier, which can be changed.
    • Nothing is deducted until "Transfer" (F12); then stock is deducted, re-orders are triggered and lines go into the right return orders (created as needed).
    • Leaving without Transfer deletes the buffered lines, with a warning.
  • Returning the whole stock of a stock item opens a choice (default first):
    • Re-order per the basket model; re-order in a specific basket (for example to avoid the same supplier after short expiry); take off stock (status becomes negative item); no action.
    • Not offered for negative items, or when enough is already in a basket or order.
    • For buy-back orders: only "take off stock" (the article is first flagged phase-out, and becomes negative when actually returned) or "no action".

4.23 Moving and merging return lines and orders [GENERIC]​

  • Supplier change of a line:
    • Lists all booked goods receipts that contained the article: supplier, place, document number and date, expiry, batch, booking EK, delivered qty, qty already captured for return.
    • This lets the user return to the supplier with the highest booking EK, which gives the best refund.
    • Picking a receipt routes the line to that supplier's return order: created if none exists, used directly if exactly one, chosen by the user if several. Contacts lookup covers any other supplier.
  • Rebook to a new order of the same supplier (Ctrl+F10): one or many lines; the new order keeps the order type; lines and receipt links are unchanged. If an open order of the supplier exists, the user chooses new / existing / cancel.
  • Merge whole order (F10 in overview): all lines move to the chosen order and the source order is deleted. "New" creates a target for another supplier. Used to switch supplier, or to move between normal and buy-back.
  • Status guard for all moves:
    • Targets are offered only up to the source's status: an open source offers open targets only; a returned source offers open, sent or returned targets.
    • The order type is never mixed when selecting a target order.
    • Moving lines out of returned or sent orders warns and is meant only for corrections.

4.24 Returning (shipping) and return slip [GENERIC]​

  • Return (F12):
    • If the order contains narcotics and "ask narcotics delivery-document number on return" is set, the number is captured into the narcotics documentation.
    • Return slip printing is offered; status becomes "returned"; lines should not change afterwards.
    • Manual status change allows only open ↔ returned.
  • Return slip content:
    • All lines and order info, optional order info text as a remark (prompted), and return info instead of the reason for "Other".
    • When an item goes back to the supplier that delivered it, the invoice/document number is printed as number and barcode.
    • The supplier's deviating delivery or warehouse address is printed if stored.
    • On a reprint both today's date and the original return date are printed.
    • Sort order per supplier setting: grouped by document number (default) or alphabetical.
  • Packing list: for open orders, to pick the goods.
  • Picking robot: eject all unreturned lines of an order (from the overview) or a single line (in edit mode).

4.25 Buy-back orders (Rückkaufaufträge) [GENERIC]​

  • Purpose: offer stock to a supplier who has agreed to buy-back. For MSV3 suppliers, contract data shows whether they accept it.
  • Flow: create (type RK; reason "pharmacy buy-back" preset; document number and delivery date auto-filled) → send → supplier answers which lines it accepts → delete the rejected lines → Return → book credit.
  • Sending:
    • Always electronic. With MSV3, an info text shows the order number for later queries.
    • Otherwise choose "send actively" or "mark as sent" (default follows the supplier's send data; warning if "active" is chosen without send data).
    • Status becomes "sent" and the return date is the send date.
  • Stock rule:
    • While open or sent: no stock deduction, no robot ejection, no re-order trigger, and the items are excluded from the "returned items" order query.
    • Stock is deducted only on Return.
    • Changing the order type, or moving lines between buy-back and normal orders, posts or reverses the deduction automatically. Changing RK to Normal on a sent order also resets its status to open.
  • Return-rate attribution: buy-back counts towards the wholesaler's return rate, so it is attributed to originator "pharmacy" for the return-rate reports.

4.26 Electronic return request and announcement (Retourenavis, MSV3 2.0) [DE-SPECIFIC protocol; generic idea = electronic RMA]​

  • Request (non-binding):
    • Sent automatically when an open return order is opened for editing, and manually any time.
    • Per-line answer: returnable; possibly not (unknown delivery note, or PZN not on that note); not returnable (no take-back, deadline passed, qty exceeds purchased qty); accepted without shipment (credit given, for example "invoiced not delivered"); accepted but call first (special transport such as cold chain or narcotics); error (missing delivery-note number or a reason not supported by MSV3).
    • Lines are tied to a delivery-note or advice number, which can be changed per line.
  • Announcement (binding):
    • Re-checks the lines; returnable lines are pre-selected; lines with red, red-yellow or error status cannot be sent.
    • The user may assign an MSV3 reason to error lines, refresh, then announce.
    • The supplier confirms acceptance, possibly split across pickup tours.
    • The result is shown as a tree: each tour or time; "call first"; "accepted, no goods to send"; "not accepted".
  • After announcement:
    • One return order is created per tour with status "returned", holding the accepted lines. Unsent lines stay in the original order.
    • A return slip is printed per order: the supplier's own slip if provided, else a standard MSV3 slip.
    • The order gets an info text with the reference number and tour. The reason tooltip shows the MSV3 reason used.
    • Lines with non-MSV3 reasons (recall, buy-back, off market, industry return, consignment, supplier-other, customer complaint) are returned the classic way (Alt+F11), ideally after being moved to their own order.
  • After sending: no lines can be added (create a new order); changes should be noted by hand on the slip; do not merge MSV3 return orders.

4.27 Return without shipment: destruction (Ohne Rücksendung retournieren) [GENERIC]​

  • Prerequisites: the supplier is flagged as a vendor and has "create destruction protocol for returns" enabled.
  • Flow:
    • Normal return order to the vendor with "all packs will be destroyed" ticked.
    • Return or send return (if the vendor supports return advice).
    • Print the destruction protocol: only packs reported returnable when return advice is used; the vendor's own document if one was supplied; the form is editable.
  • Narcotics:
    • Narcotics are left off the protocol and no narcotics delivery-document number is asked, because the transfer-form procedure does not apply to in-pharmacy destruction.
    • With automatic documentation a narcotics movement of type "destruction" is created.
    • Narcotics destruction is documented separately with the statutory destruction record [DE-SPECIFIC].
  • After returning: the order is marked "to be destroyed" and locked; the protocol can be reprinted.
  • Wholesale pharmacies: may rebook into blocked stock (special-stock module) and print a securPharm protocol.

4.28 Booking credits (Gutschrift, Sammelgutschrift) [GENERIC]​

  • Single order (Credit F12):
    • Lists unbooked lines with document number, return date, return qty, Ret-EK, credit qty and credit value per pack.
    • From the overview all lines are pre-marked; from an opened order only the selected line is.
    • Credit qty defaults to the return qty and credit value to Ret-EK; the user corrects them to what was actually granted (value per single pack).
    • Book → credit window: credit number, credit date (default today), credit value split 19% / 7% / 0% plus total (must equal the credit note; editable via F5).
    • Warning on an excessive credit value.
  • Single line: "Book" on a selected line in edit mode.
  • Collective credit (F11): shows all orders in status "returned" (the highlighted one pre-selected; "select all" for the supplier; deselecting everything shows all suppliers' returned orders). Then the same booking steps.
  • Partial booking: allowed. A partially booked line is split; the unbooked rest stays open.
  • Result: booked credits go to the Archive under the supplier. A fully booked order leaves the returns overview.

4.29 Automatic return reconciliation, ARA (GEHE) [Wholesaler-specific; generic idea = monthly electronic credit statement auto-matched to open returns]​

  • Prerequisites:
    • Supplier on MSV3 2.0.
    • Book all already-credited older returns before first use.
    • Return document numbers must equal the wholesaler's delivery-note numbers. This is automatic with MSV3 2.0 returns; edited numbers break matching or fall back to PZN matching.
  • Monthly cycle:
    • The wholesaler publishes last month's credits; the system fetches them and creates a Notes task.
    • Executing the task matches credits to returned, unbooked lines with a return date within one year.
    • Result window header: credit date (last day of the month), credited lines, credited value total = Σ(credit qty × credit value), maximum creditable value, open returned lines in the last 12 months, and their value = Σ(return qty × Ret-EK).
    • Per-line status:
      • Full match: book.
      • Qty mismatch: partial booking; the remainder stays visible.
      • Value mismatch: the credit value is used.
      • Both mismatched: partial at the credit value.
      • Credit without return line: cannot be booked; close by setting the task done.
      • Return without credit: cannot be booked here.
    • The user marks lines (partial booking and pausing are allowed) and books. The credit number is pre-filled with a unique ID (editable); the date is fixed.
    • The Archive opens after booking.
  • Task status:
    • Done automatically when everything is booked.
    • "Set done" manually marks all credit lines done without booking (for example for an empty file); "set undone" resumes.
    • Done tasks disappear from the task list after 2 months but stay findable in the calendar or task control.
  • Corrections: each line can be booked via ARA only once. A correction booking must use the manual credit process.
  • Print: all lines, or only marked lines, optionally including "special" lines (credits without returns, returns without credits).
  • Report: a predefined Reports query lists returned, unbooked lines of a wholesaler.

4.30 Return compensation in goods (Retourenausgleich) [GENERIC]​

  • Purpose: a rep or vendor compensates returned expired or slow-moving goods with other articles instead of money.
  • Prerequisite: the order must be in status "returned".
  • Flow:
    • Mark the settled return lines and set the compensated qty (partial is allowed).
    • Enter the compensation items: qty, EK, expiry. Lines can be split for different expiries or batches when qty is 2 or more. Stock status can be changed.
    • Book with the compensation document number and date (mandatory).
  • Effect:
    • Stock-only posting of the compensation items. This is not a regular goods receipt and no credit is booked.
    • Archived with its own icons (normal, corrected, correction booking); the value column stays empty.
    • Also documented in stock control (RA number and date) and flagged in the article's purchase/return history.

4.31 Write-off of uncredited returns (Retourenposition abschreiben) [GENERIC]​

  • Trigger: a returned item that the supplier will not credit (Alt+F8 in a return order with uncredited lines).
  • Permission: the "write off" right, or role "assortment manager" or "manager".
  • Defaults:
    • All unbooked lines are pre-marked.
    • The reason defaults to "expiry" if the article's expiry date has passed, else "loss from return".
    • Qty and value per pack are editable.
  • Reasons: expiry, loss, loss from discount contract, theft, damage, recall, buy-back, loss from return, and user-defined reasons.
  • Effect: written-off qty is removed from the line (the rest stays) and logged in the write-off book report.

4.32 Function-key summaries (meaningful actions only)​

  • Order edit: save, delete line, edit, article info, capture/free text, article details, print, supplier change (line), responses or goods receipt (context), stock at branches, responses view, discounts, customer contacts.
  • Response window: select all, info, send via network, article details, print, move shortfall, accept shortfall, offers, comparison article, contacts.
  • Return edit: save, delete, edit, info text, capture/free text, details, print slip or packing list, supplier change, return / credit / send buy-back, split compensation line, return info, packing list, eject from robot, return compensation, change stock status, write-off, return request.
  • Returns overview: search, new, delete, edit, info text, capture, status, print, merge, send buy-back, return / credit / send, quick capture, order type, packing list, eject all, contacts, collective credit.

5. Workflows​

5.1 Electronic order → response → receipt (standard wholesaler, MSV3)​

  1. The basket is sent in an order window (other chapter). It becomes an order in the overview with order time, MSV3 order number and expected delivery time.
  2. The supplier response arrives within seconds; otherwise the system polls for up to 30 minutes, see 4.6.
    • Fully deliverable lines need no action.
    • Shortfalls reduce the Open qty and raise the "unprocessed responses" flag.
    • Announced substitutes get their own lines; named network branches move the qty into another order.
    • If "move shortfalls automatically" is on, shortfalls are moved straight to the supplier with the next delivery or call, or to the defect note, without an open response.
  3. The user processes the open responses per line: move, accept, take an offer, send via network, set back-order/dispo permission and re-send, order a comparison article, or online inquiry/order at other suppliers.
  4. Goods arrive. A delivery advice (if MSV3 2.0) is already fetched or is fetched when the delivery note is scanned.
  5. The user starts the receipt: order-independent by scanning the delivery-note barcode (preferred with advice), or order-related from the order.
  6. Lines are captured by counter-scan, read-in, robot import, mobile scanner, order-data copy or manual scan. Expiry and batch come from the advice or DataMatrix, otherwise they are typed. Lines are split for differing batches, expiries or EKs.
  7. Optional: return packs straight from the receipt (breakage, short expiry, no need, approval order).
  8. Book: mandatory differences are resolved, optional ones if desired, and securPharm status is reviewed.
  9. The booking window opens per sub-order:
    • With the invoice: value booking (VAT split, fees, cash discount, value date, remittance), then price calculation for missing or low-margin retail prices, labels, and the statistics-transfer confirmation.
    • Without the invoice: stock booking with delivery-note data. The receipt waits in Deliveries for value booking.
  10. The order leaves the overview when fully received. Remaining back-order lines stay open (shown only under "all order types").

5.2 Manual / phone order​

  1. Orders overview → New → supplier → capture lines (qty, free goods, EK).
  2. Optionally enter the expected delivery date (direct suppliers).
  3. On arrival: goods receipt as in 5.1 steps 5–9. There is no response step.

5.3 Shortfall at receipt with credit request​

  1. Booking shows a mandatory shortfall difference. The user chooses "request credit note" and optionally re-orders into a basket.
  2. At booking, the invoice number and date are stored on a new credit-request return line in the Returns overview.
  3. This line is processed like any return (with the MSV3 reason "invoiced not delivered", typically "accepted without shipment") and credited.

5.4 Standard supplier return (no electronic advice)​

  1. Returns → New → supplier → Normal order, or quick capture for many items to their last suppliers.
  2. Capture lines with qty and reason. Stock is deducted. The system pre-fills the document number and receipt link. The user can redirect a line to the supplier with the best booking EK.
  3. If a line takes the whole stock of a stock item, decide: re-order, re-order elsewhere, take off stock, or no action.
  4. Print the packing list; eject the items from the robot if needed.
  5. Return (F12): narcotics document number if required; print the return slip; status becomes "returned".
  6. Ship the goods with the slip.
  7. When the credit note arrives: Credit → mark lines → adjust credit qty and value → credit number, date and VAT split → book → Archive. Or use a collective credit over several orders, or an ARA match for GEHE.
  8. Lines not credited: write off (with permission) to the write-off book, or record a compensation in goods.

5.5 Electronic return with return advice (MSV3 2.0)​

  1. Create the return order with the delivery-advice or delivery-note numbers. Opening it fires a non-binding request.
  2. Remove or redirect the rejected lines (deadline passed, qty exceeded, unknown note); fix document numbers; re-request.
  3. Send return → review the pre-selected returnable lines → announce (binding).
  4. The system splits accepted lines into one "returned" order per pickup tour, with reference and tour in the info text. "No shipment" lines are credited without goods; "call first" lines need a phone call.
  5. Print the return slip per order (supplier's own or standard MSV3), pack, hand over on the tour.
  6. Lines with non-MSV3 reasons are returned the classic way in a separate order.
  7. Credit as in 5.4 step 7.

5.6 Buy-back​

  1. New → supplier → Buy-back order. Capture lines (stock is not deducted).
  2. Send buy-back: actively, via MSV3 (an order number is returned), or mark as sent after a fax or phone offer. Status becomes "sent".
  3. The supplier replies with the accepted lines. Delete the others.
  4. Return: stock is deducted and the slip is printed. Then book the credit.

5.7 Destruction instead of return​

  1. Vendor with the destruction-protocol setting → Normal return order → tick "all packs will be destroyed" → capture.
  2. Return or send return → print the destruction protocol (excludes narcotics; narcotics destruction is documented separately) → the order is locked.
  3. The pharmacy destroys the goods and submits the protocol. The credit is booked as usual when received.

5.8 Return compensation​

  1. Returned order → Return compensation → mark the settled lines and quantities → enter the received articles (qty, EK, expiry, split if needed) → book with document number and date.
  2. The compensation goods enter stock (no value posting). Archived and logged in stock control.

6. Business rules and calculations​

Orders and responses

  • Order line edit: qty + free goods ≥ reported shortfall.
  • Open qty (order view) = qty still expected after response, ordered qty and postings. In order-independent receipt it is the undelivered qty of all open order lines of that article at the current supplier. With MSV3 2.0 advice, "ordered" means the packs announced in the advice.
  • Pos = number of lines still to be delivered (only deliverable lines count after a response). Value = Σ purchase value of the lines still to be delivered.
  • Delivery time display: MSV3-reported time > supplier delivery parameters (next slot after now) > "not today". "Not today" is also forced for network-only or dispo-only responses and when no regular time exists.
  • Missing-response polling: 30 minutes. The supplier's order-ID memory is 7 days; "unknown ID" leads to an automatic re-send in the next window (automatic mode only).
  • Comparison article: the defect note re-checks availability 3 times a day.
  • Cooperative import interval: 30 minutes. Delivery-advice fetch: every 30 minutes during opening hours. PDF background poll: every 30 minutes.
  • Special days: announced at most 12 months and at least 3 calendar days ahead (shorter only by manual agreement).
  • Minimum order value and minimum pack count are checked at send time if stored in the condition agreement.

Goods receipt

  • Lookup at receipt: order lines first, then the article master. PZN or EAN never opens a hit list.
  • Default expiry pre-fill = today + 24 months (parameter). If the parameter is 0, use the last booked expiry of the article (the longest if several were booked together; blank if none).
  • An expiry outside the plausible range (past, too near, too far) gives a warning; an expired date can still be accepted.
  • Expiry-too-short difference threshold = parameter "expiry length" (value not stated in the pages).
  • Price check at value booking: flag an item if it has no retail price, or if its markup is below "EK markup %".
  • Booking-value warning when the booking value exceeds the list purchase price.
  • Value booking updates booking EK, average EK, effective EK and calculated retail prices. Stock booking updates stock only.
  • The booking total before tax must equal the supplier document. It is split 19% / 7% / 0% VAT (German rates).
  • Value date defaults to the invoice date. Turnover defaults to the remitting wholesaler for direct-vendor goods.
  • Wholesale distribution: auto-distribute only if exactly the ordered qty arrives in one batch, or only one customer ordered. Surplus goes to stock.
  • Tour / home distribution: manual edits (pencil) stop further auto-distribution to that tour or home.
  • Robot pickup storage: never for POR items. The robot location is auto-removed only for non-stock items when robot stock reaches 0.

Returns

  • Stock: normal return line → immediate deduction. Quick capture → deduction at transfer. Buy-back → deduction at "returned". Deleting a line or order restores stock. Changing the order type between normal and buy-back posts or reverses the deduction.
  • Returnable qty: return qty ≤ available stock + reserved qty. Reserved (back-order) stock can be returned only if the reserved qty covers the return.
  • Delivered vs captured: shown red if captured return qty > delivered qty of the linked receipt.
  • Document number lookup order: delivery advice → delivery note → invoice.
  • Invoice number on the return slip only when returning to the supplier that delivered the item.
  • Ret-value = qty × Ret-EK.
  • Credit booking: credit value is entered per single pack. Defaults: credit qty = return qty, credit value = Ret-EK. Partial booking splits the line.
  • ARA:
    • Gut-Wert (total) = Σ(credit qty × credit value).
    • Ret-Wert = Σ(return qty × Ret-EK) over the last 12 months.
    • Credit date = last day of the statement month.
    • Lines considered: returned, unbooked, return date ≤ 1 year old.
    • Qty mismatch → book min(return, credit) and keep the remainder open. Value mismatch → book at the credit value.
    • One ARA booking per line.
  • Status guard when moving return lines: target status ≤ source status. Order type is never mixed when choosing a target order. "Booked" cannot be set by hand.
  • Buy-back is attributed to originator "pharmacy" for return-rate statistics.
  • Write-off default reason: "expiry" if the article's expiry date has passed, else "loss from return".
  • Destruction: narcotics are excluded from the protocol and no narcotics transfer-document number is asked.
  • MSV3 return-reason mapping (internal → MSV3):
Internal reasonMSV3 reason
Apo order error, Apo not collected, Apo approval order, Apo no longer needed, Apo prescription changed, Apo discount changed, Apo expiry, Apo otherOrder error
Li expiry too short, Li expiredExpiry too short
Li pack damagedDamaged
Li over-deliveredOver-delivered
Li not ordered, Li shortfall, Li credit requestInvoiced not delivered
Buy-back, Apo industry return, Li customer complaint, Li consignment, Li other, Recall, Off marketnone (cannot be sent via return advice)
  • MSV3 rejection reasons: unknown delivery-note number; PZN not on the delivery note; return deadline exceeded; qty exceeds the purchased qty; no take-back.

7. Configuration and settings​

ParameterScopeEffectDefault
Move shortfalls automatically (Fehlmengen automatisch umbuchen)Goods logistics, system parameter, page "order items"Auto-moves undeliverable or partial quantities to the supplier with the next delivery time, the next call, or the defect note. Then no open response remains. Blocks the comparison-article function.Not stated
Order items (Artikel bestellen) – keep fully undeliverable itemsGoods logistics, system parameter, page "order items"On: undeliverable items remain visible in the order (and their auto-processed response may be shown). Off: they are removed; an order with nothing deliverable is removed.On
Goods receipt notice for optional differences (Wareneingang)Goods logistics, system parameter, page "goods receipt"Notice offers optional differences automatically at booking.Off (optional differences not offered by default)
Expiry maintenance (Verfallpflege)Goods logistics, system parameter, page "goods receipt"Expiry entry required at capture.Not stated
Relative expiry datesamePre-filled expiry; 0 = last booked expiry.Today + 24 months
Expiry length (Verfalllänge)sameThreshold for the "expiry too short" difference.Not stated
EK markup in %sameTarget markup used by price calculation at value booking.Not stated
Show fully captured lines (counter-scan)Goods logistics, system parameter, page "goods receipt 2"Show or hide fully scanned lines in counter-scan mode.Off (hidden)
Show additional tab (Zusätzliche Karteikarte)sameAdds a delivery-management tab: tour overview or home-unit overview.Not stated
Enlarged detail area (article scan)WorkstationEnlarged tour/home view per scan with a mobile scanner.Not stated
Batch distribution to wholesale customersGoods logistics (wholesale licence)Enables the customer-distribution pane at receipt.Not stated
securPharm status window before bookingGoods logistics (page "goods receipt 2" referenced)Which verification statuses are shown before posting; "never" hides the window.Show when not dispensable or pending
Store negative articles (Einlagerung von Negativartikeln)System maintenance, system parameter, page "KS system"Store pickups and non-stock items in the robot at receipt; eject on pickup resolution or cleanup.Off
Ask delivery-document number on narcotics receiptDocumentation management, workstation, page "BtM"Enables the narcotics-documentation optional difference (also needs "document narcotics automatically" and the licensed feature).Not stated
Ask delivery-document number on narcotics returnDocumentation managementPrompts for the number when returning narcotics.Not stated
Demand statistics and optimisation with sales dataGoods logistics > optimisation > POR stock status / stock keepingStatistics in order detail are based on history and lost sales.Not stated
Supplier: preferred delivery-advice capture modeSupplier contact > settingsCounter-scan or read-in.Counter-scan
Supplier: return slip sortSupplier contact > settingsGrouped by document number, or alphabetical.Grouped
Supplier: create destruction protocol for returnsVendor contact > settingsEnables destruction returns.Not stated
Supplier: send parameters / MSV3 service provider (1.0 or 2.0)Supplier contact > send parametersProtocol. 2.0 is needed for delivery advice, return advice, special days and ARA.—
Supplier: delivery parametersSupplier contactRegular delivery times, delivery duration, remitting wholesaler.—
Supplier: condition agreementsSupplier contactMinimum order value and pack count, fees, cash discount.—
Purchasing-cooperative credentialsCompany master > external servicesEnables the 30-minute order import.—
DMS auto-archive of printoutsCompany masterArchive search printouts and delivery notes in the DMS.—
Print forms (supplier document vs internal list; destruction protocol)Print-forms moduleLayout of the printouts.—
List column configurationPer list (Alt+F12)Columns in the order and receipt lists.—

8. Roles and permissions​

  • Write-off of return lines needs the "write off" (Abschreiben) right, or role "assortment manager" (Sortimentsverantwortlicher) or "manager" (Leiter). This applies when the pharmacy uses the permission concept (workstation protection).
  • No other permissions are stated for ordering, receiving, booking or credit booking in these pages (see section 13).
  • Licences and feature gates mentioned:
    • securPharm licence (DataMatrix capture and verification).
    • Paid documentation-management feature (narcotics documentation).
    • IXOS wholesale licence (customer batch distribution, blocked stock, securPharm protocol for destruction).
    • Courier / delivery-management licence (tour and home view).
    • Participation in the GEHE ARA project.
    • Picking robot and mobile scanner hardware.

9. Integrations, hardware and external services​

  • MSV3 1.0 / 2.0 wholesaler protocol [DE]: order transmission, responses (shortfalls, network, dispo, substitutes, tours, tour deviation, error codes), online availability inquiry and order, contract data (order windows, special days, buy-back acceptance), delivery advice with PDF, return request and announcement with return slips, buy-back offers, and the ARA monthly credit file (GEHE).
  • Fax: fax order form, printed or sent electronically.
  • Purchasing cooperatives DIREKTplus and apokontor [DE]: web-shop order import every 30 minutes.
  • Picking robot (Kommissioniersystem): storage lists imported as receipts; WWKS2 protocol streaming; storing and ejecting pickups; ejecting return items.
  • Mobile receipt scanner (Artikelscan.mobil): WLAN handheld; delivery notes closed on the device and imported.
  • Barcode and DataMatrix scanners: PZN/EAN, delivery-note barcodes, tote labels and packing slips, securPharm DataMatrix.
  • securPharm [DE / EU FMD]: verification on receipt, status window, decommissioned-pack check on return, logging in securPharm management, outage handling with deferred retries, securPharm protocol for destruction (wholesale).
  • Document management: ELO (archive printouts; send gross value and payment type with value bookings) and the ORBIZ DMS (link the invoice or delivery-note document to a booking; scan dialog after stock booking; MSV3 delivery notes auto-passed).
  • Notes module and info centre: tasks for late shortfalls from the delivery advice and for ARA statements; messages for imports, responses and contract-data changes.
  • Card reader for reorder cards in POR pharmacies.
  • Branch/partner network: joint orders, stock info at branches, greyed rows for joint orders triggered elsewhere.

10. Printouts, reports and exports​

  • Order log (Bestellprotokoll), fax order form (optionally with a note to the supplier), and labels from the orders overview or an order.
  • Extended order search printout: supplier document or internal hit list (two forms); optional DMS archive.
  • Response printout.
  • Price/shelf labels from price calculation at value booking (and from goods receipt).
  • Return slip (Retourenschein): lines, info remark, return info, document numbers as barcodes, deviating delivery address, first return date on reprints, grouped or alphabetical. A standard MSV3 slip or the supplier's own slip for return-advice orders. One per tour order.
  • Packing list for open return orders.
  • Destruction protocol (editable form, or the vendor's own document); securPharm protocol for wholesale destruction returns.
  • ARA credit/return listing: all or marked lines, optionally including special lines.
  • Write-off book (Abschreibebuch report).
  • Reports query "goods logistics – articles in certain …" (filter by return order).
  • Stock control entries for return compensation (RA number and date).
  • Delivery-advice PDF stored with each delivery.

11. Dependencies on other modules​

  • Basket, reminder list, defect note, automatic order proposal, basket-determination model, online inquiry and order, back-order management: the purchasing chapters before this one.
  • Supplier contacts: send parameters, delivery parameters, condition agreements and fees, offer lists, contract data, settings (Contacts chapter).
  • Article master: stock status (POS, POR, negative), storage locations, pricing page and calculation rules, article info, statistics transfer, write-off reasons, purchase/return history (Article chapters).
  • Assortment control (RX 4.0): listing and delisting shown in blue; defect automation.
  • POS and pickups: pickup slips, appointment orders, courier and post back-orders, resolving and cleaning up pickups.
  • Invoicing (Faktura): branch transfers and invoicing orders.
  • Delivery management: tours and care homes.
  • Wholesale module: customer orders, special stock (Sonderlager) and blocked stock.
  • securPharm management; documentation management (narcotics movements, destruction record); Notes / info centre; Reports; DMS; print forms; Archive tab (correction bookings, archived compensation details); Deliveries tab (later value booking).

12. Portability notes​

Generic ideas worth copying

  • Order lifecycle: reminder list → basket → order → receipt, with stock changing only at receipt.
  • Per-line supplier response model: immediate, network, back-order and dispo quantities, substitute, reason. Response processing gates the receipt.
  • Shortfall routing: to the next-delivery supplier, a specific supplier, the cheapest offer, a comparison article, or a defect watch-list re-checked several times a day. Optional automatic rebooking.
  • Duplicate-order protection: for unconfirmed electronic orders, poll, warn, and re-send only when the supplier confirms it never saw the order.
  • Two-tier receipt reconciliation: mandatory differences (qty, unordered, no price) and optional ones (short expiry, non-stock item, substitute, controlled-drug paperwork), each with explicit resolution choices. Shortfalls can lead to a credit request, an expected back-delivery, or a re-order.
  • Two-step booking: stock-only now, value later when the invoice arrives. VAT-split invoice totals, fees, cash discount, value date. A sanity check of the booking value against the list price. A margin check that triggers retail-price recalculation.
  • Receipt capture tools: search inside the order first; quantity preset; expiry plausibility; batch/expiry split; return straight from receipt.
  • Advance shipping notice with counter-scan, robot and handheld imports.
  • Distribution of received goods to delivery tours, care homes or B2B customers.
  • Return management: cause plus originator reasons (feeds supplier return-rate analysis); stock deducted on capture; route lines to the supplier with the highest booking price; status-guarded moving and merging; quick capture; whole-stock decision (re-order, delist, nothing); buy-back as a stock-neutral offer; destruction with protocol instead of shipment; credit booking with partial and collective credits; compensation in goods; write-off of uncredited returns with permission and a write-off book.
  • Electronic return authorisation (RMA): non-binding request, then binding announcement split by pickup tour, then credit; "accepted, no shipment" for billing errors.
  • Automatic matching of supplier credit statements to open returns, with mismatch categories and partial booking.

Germany-specific, with the idea underneath

  • MSV3 protocol, delivery advice, return advice, special days → a standard wholesaler EDI layer (order/response, ASN, RMA, order-window calendar). In Syria a simple REST or file exchange with drug warehouses could carry the same messages.
  • securPharm verification → serialised-pack verification and decommissioning against a national or regional registry, with offline queueing.
  • Narcotics delivery-document number and destruction record → controlled-substance chain-of-custody documents on every receipt, return and destruction.
  • 19% / 7% / 0% VAT split → configurable tax classes on supplier invoices and credits.
  • ABDA list purchase price, PZN, standard pack sizes (N1–N3), Hilfstaxe, EU re-imports → a national drug database with reference prices and identifiers.
  • Purchasing cooperatives, remitting wholesaler for direct-vendor goods → importing orders from external buying portals; settling vendor deliveries through a distributor account.
  • GEHE ARA → any distributor's periodic credit statement.

13. Open questions​

  • Order statuses: exact status values of an order beyond reminder list / basket / order are not defined, and neither is how "fully received" closes it (only "not yet fully completed by receipts").
  • Back-order monitoring: no explicit "overdue" status or alert exists in these pages. Overdue monitoring relies on delivery time and "not today", the 30-minute polling, and back-order management (another chapter). How partially received orders with outstanding lines are aged or escalated is not described.
  • Default values not stated: "move shortfalls automatically", expiry length, EK markup %, expiry maintenance, and what "next call" (Anruf) means as a rebooking target (presumably the supplier's next scheduled order transmission).
  • Return reasons without originator: the help says the "last three" reasons lack an originator code, but the list ends with "data migration". Presumably recall, buy-back and off-market; to be verified. Buy-back is shown as "Apo buy-back" in one place.
  • Recalls: no recall-specific workflow (receiving a recall notice, locating affected batches, quarantine) appears in these pages. Recall exists only as a return reason, a write-off reason and a securPharm pack status. Expiry monitoring outside goods receipt (expiry lists) is likewise not covered here.
  • Credit-note check against the supplier invoice: for non-ARA suppliers there is no automatic matching. The check is manual: credit qty and value per line, plus an "excessive credit value" warning whose threshold is not stated.
  • Permissions: none are given for deleting orders, booking receipts, changing EK or booking credits.
  • Key binding conflict: the offers function in the response window appears as Ctrl+F8 in one page and Ctrl+F9 in another.
  • Ret-EK default: where the expected refund per pack comes from by default (booking EK of the linked receipt?) is implied but not stated.
  • Return deadline: the supplier's agreed return deadline (Rückgabefrist) is enforced only by the supplier via MSV3; no local deadline setting is described.
  • Joint orders: behaviour of joint orders at receipt is only referenced (another topic).
  • Deliveries and Archive tabs: correction bookings and later value booking are referenced but not described in these pages.

14. Source pages​