allocation

The reservation of inventory against a demand prior to the outbound process.

You can allocate a quantity of inventory to a business partner or a particular demand order.

Note: The documentation sometimes states that a particular demand object, such as a sales order, is allocated to a business partner, order, or reference. That phrase actually means that LN must fill the demand object with supply that was allocated to that particular business partner, order or reference.

business-function model

A part of a business model that is built from a selection of business functions that are initially created in the repository.

enterprise unit relationship

Identifies the relation between two enterprise units in a multicompany organization.

internal business partner

A business partner that represents an enterprise unit of the same logistic company. The use of internal business partners allows you to model the goods flow between enterprise units and the corresponding financial relations, such as invoicing and pricing agreements. You must define all business partner roles for an internal business partner.

number group

A group of first free number series that you can assign to a specific use.

For example, you can assign a number group to:

  • Business partner codes
  • Purchase contracts
  • Sales orders
  • Production orders
  • Service orders
  • Warehousing orders
  • Freight orders

Within a number group you can define multiple series. Each series is identified by the series code. The series numbers that LN generates consist of the series code followed by the first free number in the series. Series codes of the same number group have the same length.

purchase contract

Purchase contracts are used to register specific agreements with a buy-from business partner that concern the delivery of specific goods.

A contract is comprised of:

  • A purchase contract header with general business partner data, and optionally, a linked terms and conditions agreement.
  • One or more purchase contract lines with (central) price agreements, logistic agreements, and quantity information that apply to an item or price group.
  • Purchase contract line details with logistic agreements and quantity information that apply to an item or price group for a specific location (warehouse) of a multicompany corporation. Contract line details can exist only for corporate purchase contracts.

sales contract

Sales contracts are used to register agreements about the delivery of goods with a sold-to business partner .

A contract is comprised of the following:

  • A sales contract header with general business partner data, and optionally, a linked terms and conditions agreement.
  • One or more sales contract lines with price/discount agreements and quantity information that apply to an item or price group.

series

A group of order numbers or document numbers starting with the same series code.

Series identify orders with certain characteristics. For example, all sales orders handled by the large accounts department start with LA (LA0000001, LA0000002, LA0000003, and so on).

subcontracting

Allowing another company (the subcontractor) to carry out work on an item. This work can concern the entire production process, or only one or more operations in the production process.

terms and conditions agreement

An agreement between business partners about the sale, purchase, or transfer of goods, in which you can define detailed terms and conditions about orders, schedules, planning, logistics, invoicing, and demand pegging, and define the search mechanism to retrieve the correct terms and conditions.

The agreement includes the following:

  • A header with the type of agreement and the business partner(s).
  • Search levels with a search priority and a selection of search attributes (fields) and linked terms and conditions groups.
  • One or more lines with the values for the search levels’ search attributes.
  • Terms and conditions groups with detailed terms and conditions about orders, schedules, planning, logistics, invoicing, and demand pegging for the lines.

terms and conditions attribute set

A set that groups search attributes of the same terms and conditions type for use on the terms and conditions search levels.

Search attributes not linked to the attribute set cannot be entered on the terms and conditions agreement for the terms and conditions type.

terms and conditions group

Groups the detailed terms and conditions about orders, schedules, planning, logistics, invoicing, or demand pegging for the terms and conditions line.

terms and conditions line

Holds the values for the search attributes of a terms and conditions search level. Therefore, it specifies the fields to which the detailed terms and conditions, as stored in the terms and conditions groups, apply.

terms and conditions search attribute

An element (field) selected on the terms and conditions search level and specified and searched for on the terms and conditions line.

terms and conditions search level

A priority level for searching and selecting a terms and conditions line. Search levels include a selection of search attributes (fields) and linked terms and conditions groups.

terms and conditions template

A default terms and conditions agreement, representing a business process, with no business partner linked to it. The level of detail of the template data is user-definable.

Based on a template, you can do the following:

  • Generate new terms and conditions agreements for business partners.
  • Update existing terms and conditions agreements.
  • Validate terms and conditions agreements.

terms and conditions type

Defines the type of terms and conditions agreement or template and is linked to a set of search attributes. Each terms and conditions type has its own search attributes.

The following terms and conditions types are available:

  • Purchase

    Purchase terms and conditions agreements can be linked to purchase contracts.
  • Sales

    Sales terms and conditions agreements can be linked to sales contracts.
  • Internal

    Internal terms and conditions agreements can be linked to enterprise unit relationships.

vendor managed inventory (VMI)

An inventory management method according to which the supplier usually manages the inventory of his customer or subcontractor. Sometimes, the supplier manages the supply planning as well. Alternatively, the customer manages the inventory but the supplier is responsible for supply planning. Inventory management or inventory planning can also be subcontracted to a logistics service provider (LSP).

The supplier or the customer may own the inventory delivered by the supplier. Often, the ownership of the inventory changes from the supplier to the customer when the customer consumes the inventory, but other ownership transfer moments occur, which are laid down by contract.

Vendor-managed inventory reduces internal costs associated with planning and procuring materials and enables the vendor to better manage his inventory through higher visibility to the supply chain.

warehouse

A place for storing goods. For each warehouse, you can enter address data and data relating to its type.

warehouse set

A group of warehouses with similar characteristics. A warehouse can belong to one particular warehouse set.

wizard

A special form of user assistance that automates a task by setting the parameter values within a business model and which directs the software to meet the specific requirements of an organization.