EOS Docs – EX096 EOS FOOD Deliveries (EFW)

Docs: Setup

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

Setup

The Deliveries Setup page is the central configuration point for the EOS FOOD Deliveries module. It is a single setup page that holds all the module’s options.

Configuration Sections

1. Number Series (Numerations)

Configure the number series used for automatic document numbering:

Field	Description
Land Mapping Nos.	Specifies the number series used to assign unique identifiers to land mapping records.
Disciplinary Nos.	Specifies the number series used to assign unique identifiers to disciplinary records.
Deliveries Receipt Nos.	Specifies the number series used to assign unique identifiers to deliveries receipt documents.
Posted Deliveries Receipt Nos.	Specifies the number series used to assign unique identifiers to posted deliveries receipt documents.

2. Reason Codes

Configure default reason codes used when creating delivery orders:

Field	Description
Deliveries Reason Code	Specifies the default reason code applied to delivery orders.
Own Prod. Deliv. Reason Code	Specifies the default reason code applied to own production delivery orders.

3. Processing

Configure document creation behavior:

Field	Description
Deliveries Document Type	Specifies the default purchase document type (Order or Blanket Order) created when generating delivery orders from land mappings.
Deliv. Document Lines Grouping	Specifies how purchase document lines are grouped when creating delivery orders from land mappings.
Company Vendor No.	Specifies the vendor number representing the company itself, used for own production deliveries.

4. Deliveries Receipts

Field	Description
Enable Deliv. Rcpt. Status Mgt	Specifies whether the status management workflow is enabled for deliveries receipts, allowing status transitions before posting.

Setup Checklist

Before using the module, ensure the following are configured:

All four number series are assigned
Deliveries Reason Code is set
Own Prod. Deliv. Reason Code is set (if using own production)
Company Vendor No. is set (if using own production deliveries)
Deliveries Document Type is selected (Order or Blanket Order)
Lines Grouping method is selected
Status Management is enabled/disabled per business requirements

Disciplinaries

Disciplinaries define agricultural production specifications that can be associated with land mappings.

Field	Description
Code	Specifies the unique identifier for the disciplinary record.
Disciplinary Name	Specifies the descriptive name of the production disciplinary, such as organic or conventional farming methods.
Yield Limit	Specifies the maximum allowed yield limit for this disciplinary. Used to control production thresholds per land mapping.
Notes	Specifies any additional notes or remarks about the disciplinary record.

Disciplinaries support document attachments via the standard BC attachment factbox.

Land Mapping Areas

Simple code/description lookup for geographic area classification.

Field	Description
Code	Specifies the unique code that identifies the land mapping area.
Description	Specifies a description of the land mapping area, such as a geographic region or zone name.

Weighing Machines

Registry of weighing machines.

Field	Description
No.	Specifies the unique identifier for the weighing machine.
Name	Specifies the descriptive name or label of the weighing machine.

Weighing Operators

Registry of operators who perform weighing operations.

Field	Description
No.	Specifies the unique identifier for the weighing operator.
Name	Specifies the full name of the weighing operator responsible for performing weight measurements.

Docs: Land Mappings

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

Land Mappings

Overview

Land Mappings represent the cadastral and agricultural data for vendor-owned lands. Each land mapping record associates a vendor with a specific parcel of land, its cultivable area, the crop (item) grown, and the expected yield percentage. This data is the foundation for calculating delivery order quantities.

Fields

General Section

Field	Type	Description
Land ID	Code	Specifies the unique identifier for the land mapping record. Assigned automatically from the number series.
Vendor No.	Code[20]	Specifies the vendor (grower or supplier) who owns or operates this land parcel.
Ref. Year	Integer	Specifies the reference year for this land mapping. Land mappings are tracked annually and can be copied from year to year.
County	Text	Specifies the county or province where the land parcel is located.
City	Text	Specifies the city or municipality where the land parcel is located.

Land Registry Data

Field	Type	Description
Sheet	Text	Specifies the cadastral sheet number from the land registry where this parcel is registered.
Parcel	Text	Specifies the cadastral parcel number that identifies this specific plot within the sheet.
Spacing	Text	Specifies the planting spacing or subdivision identifier within the parcel.
Planting Year	Integer	Specifies the year when the crops or plants were originally planted on this land parcel.
Cultivable Area (mq)	Decimal	Specifies the total cultivable surface area of the land parcel, measured in square meters.

Item Section

Field	Type	Description
Item No.	Code[20]	Specifies the item (product) that is cultivated or harvested from this land parcel.
Description	Text	Specifies the description of the item cultivated on this land parcel.
Description 2	Text	Specifies an additional description for the item cultivated on this land parcel.
Yield %	Decimal	Specifies the expected yield percentage for this land parcel, representing the ratio of usable product to total harvest.

Miscellaneous

Field	Type	Description
Area Code	Code	Specifies the geographic area code that groups this land mapping for reporting and delivery order creation.
Notes	Text	Specifies any additional notes or remarks about this land mapping record.
Disciplinary Code	Code	Specifies the production disciplinary assigned to this land parcel, defining the farming rules and yield limits that apply.

Functions

The Land Mappings list page provides three key report actions:

Print Land Mappings

Generates a printable report of land mappings grouped by vendor. Requires a Reference Year parameter. Displays cadastral data, cultivable areas, yield percentages, and item descriptions.

Copy Land Mappings

Copies land mapping records from one reference year to another. Use this at the beginning of each harvest season to carry forward land configurations.

Parameters:

From Year: Source reference year
To Year: Target reference year

Behavior:

If mappings already exist for the target year, the system asks whether to delete them first
New records are created with new Land IDs (auto-generated)
Vendor filter from the list page is applied

Create Delivery Orders

Creates purchase orders (or blanket orders) from land mappings. This is the primary workflow action. See 03-DeliveryOrders.md for details.

Auto-Fill Behavior

When creating a new land mapping from a vendor-filtered view (e.g., opened from the Vendor Card), the Vendor No. is automatically populated from the filter.

Document Attachments

Land Mapping records support standard Business Central document attachments via the factbox panel. Attachments are linked to the specific land mapping record.

Yield Calculation

The Yield % field, combined with Cultivable Area (mq), determines the quantity of product expected from this land:

Deliverable Quantity = (Cultivable Area × Yield %) / 100

This formula is used by the Create Delivery Orders function to calculate purchase line quantities.

Docs: Delivery Orders

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

Delivery Orders

Overview

The Create Delivery Orders function is the bridge between land mapping data and the standard Business Central purchasing flow. It reads land mapping records and automatically generates purchase orders (or blanket purchase orders) with calculated quantities based on cultivable area and yield percentages.

Create Delivery Orders

The function runs interactively from the Land Mappings list and produces no printed output — it creates the purchase documents directly.

Request Page Parameters

Parameter	Description
Document Type	Order or Blanket Order. Defaults from Deliveries Setup.
Ref. Year	Reference/harvest year to process. Required.
Group By	Item/Area or Item/Area/Land. Defaults from Deliveries Setup.

Vendor Filter

The report inherits the vendor filter from the Land Mappings list page. You can filter to create orders for specific vendors only.

Processing Logic

1. Pre-Processing Validation

Before execution, the function:

Validates that a Reference Year is specified
Checks if delivery orders already exist for the selected year/vendors
If orders exist, asks for confirmation before proceeding

2. Document Creation Flow

The function processes land mappings sorted by Ref. Year → Vendor No. → Item No.:

For each Vendor (new Purchase Header):
│
├── Set Deliveries Order Type:
│ ├── "Own Production Delivery" if Vendor = Company Vendor No.
│ └── "Delivery" for all other vendors
│
├── Set Reason Code (from Setup)
├── Set Ref. Year
│
└── For each Land Mapping:
│
├── Calculate quantity:
│ Qty = (Cultivable Area × Yield %) / 100
│ (rounded per the item's quantity settings)
│
└── Create/Update Purchase Line:
├── Item/Area grouping: accumulate qty on same line
└── Item/Area/Land grouping: new line per land

3. Line Grouping Modes

Item/Area Grouping

Multiple land mappings with the same Item No. and Area Code are combined into a single purchase line. The quantity is the sum of all individual calculated quantities.

Example: 3 land mappings for the same vendor, same item “Grapes”, same area “NORTH”:

Land A: 1000 mq × 80% = 800 kg
Land B: 500 mq × 75% = 375 kg
Land C: 750 mq × 85% = 637.5 kg
→ One purchase line: 1,812.5 kg

Item/Area/Land Grouping

Each land mapping generates its own purchase line. The Land ID is stored on the purchase line for traceability.

Example: Same 3 land mappings → Three purchase lines with individual quantities and Land IDs.

4. Purchase Line Fields

Each created purchase line includes:

Field	Value
Type	Item
No.	Item No. from land mapping
Quantity	Calculated deliverable quantity
Area Code	Area Code from land mapping
Land ID	Land ID (only in Item/Area/Land mode)

5. Post-Processing

After all documents are created:

A summary message shows the number of documents created
The user is asked whether to open the created documents
If confirmed, the system opens either the Purchase Order List or Blanket Purchase Orders list, filtered to the created documents

Delivery Order Type Assignment

Docs: Deliveries Receipts

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

Deliveries Receipts

Overview

Deliveries Receipts are the core operational documents in the EOS FOOD Deliveries module. They represent the physical arrival of goods at the weighing station, capturing weight data, lot tracking, shipment details, and linking the receipt to a specific purchase order line for posting.

Receipt Lifecycle

Status Management (Optional)

When Enable Deliv. Rcpt. Status Mgt is turned on in Setup:

┌──────┐ ┌──────────┐ ┌──────────┐
│ New │───▶│ Accepted │───▶│ Weighed │
└──────┘ └──────────┘ └──────────┘
│ │
└──────────────────────────────┘
(direct skip allowed)

New: Initial status after creation
Accepted: Delivery accepted at the gate (inspection passed)
Weighed: Weighing completed — ready for posting

When status management is disabled, receipts can be posted regardless of status.

Receipt Actions

Get Gross Weight / Get Tare

Reads the gross weight and tare directly from the connected weighing machine and fills in the corresponding fields on the receipt.

Link To Order

Manually links the receipt to an eligible purchase order line. The system searches for purchase lines matching:

Document Type = Order
Same vendor
Deliveries Order Type ≠ blank
Ref. Year ≠ 0
Type = Item
Same item and variant
Outstanding Quantity > 0

If the receipt is already linked, the system asks for confirmation before relinking.

Unlink From Order

Removes the link between the receipt and its purchase order line, clearing Order No. and Order Line No.

Change Status

Transitions the receipt status. Available transitions depend on current status:

From New: Can change to Accepted or Weighed
From Accepted: Can change to Weighed

Requires confirmation before changing.

Post (F9)

Posts the deliveries receipt, creating a purchase receipt and closing the delivery receipt. See Posting Process below.

Creating Deliveries Receipts

Receipts can be created in three ways:

1. From Purchase Order Subform

On the Purchase Order Subform, line-level actions:

Create Deliveries Receipt: Opens a request page allowing you to specify:
- Number of Deliveries Receipts to Create: How many receipts to create for the line (default 1, useful for multiple deliveries against the same order line)
- Posting Date: The posting date to set on the created receipt(s)
The system validates that the purchase order is a delivery order and that the line is of type Item. After creation, it offers to open the receipt card (single) or the receipt list (multiple).
Link to Deliveries Receipt: Shows existing unlinked receipts matching the line’s criteria for selection

2. From Deliveries Receipts List

Create a new record directly in the list or card page. The receipt must then be linked to a purchase order manually using the “Link To Order” action.

Posting Process

When a deliveries receipt is posted (either from the receipt card or from the purchase order):

Pre-Posting Validation

The system validates:

Check	Error if
Posting Date	Not set
Vendor No.	Not set
Item No.	Not set
Lot No.	Not set and item requires lot tracking
Gross Weight	Zero or negative
Tare	Zero or negative
Net Weight	Zero or negative
Qty. to Receive	Zero or negative
Status	Not “Weighed” (if status management enabled)
Consistency	Vendor/Item/Variant/Location doesn’t match purchase line

Posting Steps

When a receipt is posted, the system:

Sets the quantity to receive on the linked purchase order line from the receipt
Applies the lot number for tracking
Updates the purchase order with the posting date and shipment reference
Receives the goods through the standard Business Central purchase posting
Archives the receipt as a Posted Deliveries Receipt with a reference to the purchase receipt
Removes the original open receipt

Posting from Purchase Order

When posting a purchase order that has the Deliveries Order Type set:

The standard posting confirmation is intercepted
Only receipts with Qty. to Receive > 0 are considered
If status management is enabled, only “Weighed” receipts are eligible
The user can select which receipts to post (if multiple)
The Qty. to Receive on purchase lines is controlled by the receipts, not editable directly

Purchase Order Line Protection

When a purchase order line is linked to deliveries receipts:

Qty. to Receive field becomes read-only (managed by receipts)
Item No. cannot be changed (error raised)
Variant Code cannot be changed (error raised)
Buy-from Vendor No. on the header cannot be changed
Deliveries Order Type on the header cannot be changed

Lot Number Generation

The Lot No. field supports AssistEdit:

Click the assist-edit button
System asks: “Do you want to generate a lot number?”
If confirmed, generates the next number from the item’s Lot Nos. number series

Docs: Posted Deliveries Receipts

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

Posted Deliveries Receipts

Overview

Posted Deliveries Receipts are the permanent archive of completed delivery transactions. Each posted receipt represents a successful goods receipt that has been processed through the standard Business Central purchase posting routine.

Visual Indicators

In the Posted Deliveries Receipts list:

Records that have been undone (have an undo entry) are displayed with Unfavorable style (typically red/bold) to visually distinguish reversed entries
The Correction flag identifies the reversal record itself

Undo Process

When a standard BC Undo Purchase Receipt is executed on a receipt line that was created by a deliveries receipt:

What Happens

Undo Posted Deliveries Receipt Created
A new posted deliveries receipt is created with:
- Negative Qty. Received (reversal)
- Correction = true
- Applies-to Posted Del. Rcpt. = original receipt No.
New Deliveries Receipt Reopened
A new open deliveries receipt is created from the posted receipt data:
- Same vendor, item, lot, weights, shipment details
- Linked back to the original purchase order line
- Ready for re-editing and re-posting

Undo Flow

Posted Deliveries Receipt (original, positive qty)
│
├── Undo Purchase Receipt triggered
│
├──▶ New Posted Deliveries Receipt (negative qty, Correction=true)
│ └── Applies-to: original receipt
│
└──▶ New Deliveries Receipt (open, linked to order line)
└── Ready for editing and re-posting

Visual Result

After an undo, the Posted Deliveries Receipts list shows:

Original receipt — positive quantity, marked with unfavorable style (has undo)
Reversal receipt — negative quantity, Correction=true
The new open receipt appears in the Deliveries Receipts list

Relationship to Standard BC Documents

Each posted deliveries receipt is linked to a standard BC purchase receipt:

Posted Deliveries Receipt
│
├── Purch. Receipt No. ──▶ Purchase Receipt Header
├── Purch. Receipt Line No. ──▶ Purchase Receipt Line
│
└── Via Purchase Receipt ──▶ Item Ledger Entry
└── Deliveries Order Type

The Deliveries Order Type is carried through to the Item Ledger Entry, allowing filtered analysis of deliveries vs. standard receipts.

Docs: Deliveries Orders Posting

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

Deliveries Orders Posting

Posting Interception

When a user attempts to post a delivery purchase order (via F9 or the standard Post action):

The standard posting confirmation is suppressed
The system checks for deliveries receipts with Qty. to Receive > 0
If status management is enabled, only “Weighed” receipts are considered
User is shown a custom confirmation
If multiple receipts exist, user selects which ones to post
Each selected receipt is posted individually (one purchase receipt per deliveries receipt)
After all receipts are posted, remaining line quantities are reset

Posting Flow Diagram

User clicks Post on Purchase Order
│
├── Is Delivery Order? (Type set + Ref. Year set)
│ ├── No → Standard BC posting
│ └── Yes ↓
│
├── Find receipts with Qty. to Receive > 0
│ └── (Optional: filter by Status = Weighed)
│
├── Confirm with user
│
├── For each receipt:
│ ├── Validate pre-posting checks
│ ├── Set this line's Qty. to Receive from receipt
│ ├── Apply lot number (if applicable)
│ ├── Receive the goods
│ ├── Create Posted Deliveries Receipt
│ └── Remove original receipt
│
└── Reset remaining unprocessed lines

Data Propagation

The Deliveries Order Type flows through the posting chain:

Purchase Header
└── Deliveries Order Type
│
├──▶ Item Journal Line
│ └── Deliveries Order Type
│
└──▶ Item Ledger Entry
└── Deliveries Order Type

This enables reporting and analysis on item ledger entries by delivery type.