User-defined fields of various field formats that can be added to various sessions, in which users can edit these fields. No functional logic is linked to the contents of these fields.

Additional information fields can be linked to database tables. When linked to a table, the fields are displayed in the sessions corresponding to the database tables. For example, a field defined for the whinh200 table is displayed as an extra field in the Warehousing Orders (whinh2100m000) session.

The contents of additional fields can be transferred between database tables. For example, the information specified by a user in additional information field A of the Warehousing Orders (whinh2100m000) session is transferred to additional information field A in the Shipments (whinh4130m000) session. For this purpose, additional information fields with identical field formats and field name A must be present for the whinh200 and the whinh430 tables (whinh430 corresponds to the Shipments (whinh4130m000) session).

Commands are distributed across the Views, References, and Actions menus, or displayed as buttons. In previous LN and Web UI releases, these commands are located in the Specific menu.

A warehousing order that is generated during the creation of a push schedule or a production schedule and that contains:

• A position number and sequence number of zero.
• An item as defined on the purchase schedule or production schedule.
• An order quantity equal to the quantity as defined on the purchase contract line. If based on a production schedule, the order quantity of the blanket order is based on the quantity specified in the Transfer Quantity field of the Work List (tirpt4602m000) session.
• An empty planned delivery date and planned receipt date.
• A lot selection defined as Any.

An XML message used to exchange data between enterprises or enterprise applications. The BOD is composed of a noun, which identifies the message content, and a verb, which identifies the action to be taken with the document. The unique combination of the Noun and the Verb forms the name of the BOD. For example, noun ReceiveDelivery combined with verb Sync results in BOD SyncReceiveDelivery.

An event-driven and XML-based messaging engine. This is the standard message bus. The message bus and its message standards provide the infrastructure for transporting messages to other application modules in a secure way.

A combination of project/budget, element and/or activity, which is used to identify costs, demand, and supply for a project.

A planning group is used for segregation in planning for project specific demand and supply. Commingling rules and cost transfer rules can be defined at planning group level to control supply planning behavior of project pegged items within the planning group as well as with other planning groups.

The lines that include the item details in a request for quotation (RFQ), such as required quantity, time to be delivered, delivery warehouse and so on.

The item lines are sent to the bidder. The bidder can respond to each item individually and also offer alternatives for the required item.

A response to a request for quotation, which includes one or more response lines with bids. A bid offers goods or services for a certain price and terms of sale and can be considered as an offer to sell.

The business partner who orders goods or services from your organization, who owns the configurations you maintain, or for whom you perform a project. Usually a customer's purchase department.

The agreement with the sold-to business partner can include:

• Default price and discount agreements
• Sales order defaults
• Delivery terms
• The related ship-to and invoice-to business partner