M3 Business Engine

Data Model Introduction

Version 1.0
February 2014

Authors:
Simon Adriansson, Diran Demirian, Mikael
Enberg, Kristina Sabotic, Henrik Sandberg,
Jacob Walfridsson, Sofie Wibaeus, Erfan
Yousefi, Josefine Öjersson
Table of contents
Introduction ...................................................................................................................................... 3
Data model symbols .................................................................................................................... 3
Limitations .................................................................................................................................... 3
Allocation ......................................................................................................................................... 4
Bonus and commission ................................................................................................................... 5
Budget ............................................................................................................................................. 7
Company structure .......................................................................................................................... 9
Cost accounting ............................................................................................................................. 10
Customer ....................................................................................................................................... 12
Customer blanket agreement ........................................................................................................ 14
Customer order .............................................................................................................................. 15
Customer order invoicing ............................................................................................................... 16
Delivery .......................................................................................................................................... 18
Distribution order / Requisition order ............................................................................................. 20
Distribution order proposal ............................................................................................................ 21
Financial accounting ...................................................................................................................... 22
Fixed asset .................................................................................................................................... 24
Item ................................................................................................................................................ 25
Maintenance customer order ......................................................................................................... 27
Manufacturing order ...................................................................................................................... 30
Manufacturing order proposal........................................................................................................ 32
Pre–allocation ................................................................................................................................ 33
Product costing .............................................................................................................................. 35
Purchase order .............................................................................................................................. 37
Purchase order agreement ............................................................................................................ 39
Report generator............................................................................................................................ 41
Service agreement......................................................................................................................... 43
Service order ................................................................................................................................. 45
Service order - Individual item ....................................................................................................... 47
Stock .............................................................................................................................................. 49
Stock transaction ........................................................................................................................... 50
Supplier .......................................................................................................................................... 51
User ............................................................................................................................................... 53
Warehouse .................................................................................................................................... 54
Work order ..................................................................................................................................... 55

2
Introduction
This document aims to give an overview of database tables used throughout different
business areas in M3 Business Engine version 15.1.2.
For detailed information about each table, please use the M3 Metadata Publisher.

Data model symbols

Below are the symbols and their respective descriptions used to illustrate the data models of
this document.

One-to-one relationships
Describes a one-to-one table relationship.

One-to-many relationships
Describes a one-to-many table relationship.

Many-to-many relationships
Describes a many-to-many table relationship.

Main tables
XXXXXX Central tables for an area are identified with a
bold font weight.

Non-main tables
XXXXXX Tables not central to an area are identified with
a regular font weight.

Limitations
The table connectors describe a relationship from a business point of view and do not
necessarily reflect what may be technically possible to set up. For example, in some cases it
may be theoretically possible to have a zero-to-many relation between two tables. However
as this relation lacks business significance, possible zero-connectors are not specified in this
document.
Further, this document describes what main tables are used in different areas at an overall
level. There may consequently be additional relations than displayed in the models. Although
in the context such relations are to be considered of minor importance.

3
Allocation
Allocation is to assign a given available quantity of resources for a demand. If the quantity
isn't available a pre-allocation can be performed instead, the quantity will then be allocated as
it comes into stock.

MITLOC

MITALO

OOLINE MWOMAT MGLINE

MGLINE Distribution order/Requisition order line

This table contains distribution-, requisition- and move location- order lines.

MITALO Allocation
This table connects allocated quantities for an item with what is in stock of the item.

MITLOC Balance Identities

This table contains records regarding stock quantity for given item/location/lot or container
combination. If multiple locations are used for an item, quantities on every balance ID are
stored here.

MWOMAT MO Material file

This table contains material and operation lines.

OOLINE Customer Order Lines

This table contains all customer order lines. Some basic information is retrieved from this
table during invoicing and is also updated with information such as status, invoiced quantity,
etc.

4
Bonus and commission
A bonus/commission (B/C) agreement determines the conditions for calculating and
processing B/C for one or more recipients and is updated with sales (invoiced customer order
lines) covered by the agreement. The B/C is settled when the agreement expires. If the
agreement extends over several years, it is settled annually. Advances, according to a fixed
or dynamic advance method, can also be credited to the recipients during the agreement
period.

OBONSR OBOACP

OBONSU OBONAG OBOPAY OBOWRK

OBONST

OBOPER

OBOTRA

OBOACP B/C allocation % (and for fixed advances)

This table contains reservation percentage for the recipients of the B/C and is defined
according to selected field in the B/C agreement. If fixed advance method is used for the B/C
agreement, this percentage is also used for calculations of the fixed advances.

OBONAG B/C agreement file

This table contains all B/C agreements, which can be preliminary, active or settled.

OBONSR B/C agreement staggered rates

This table contains the B/C percentage according to a scale which is based on generating
value of B/C agreement.

OBONST B/C status per recipient

This table contains annual status records of the recipients of B/C agreements, e.g., balances
of the generating value and the paying amount.

5
OBONSU B/C substitution hierarchy
This table is used when an agreement should be substituted by another during a defined
period.

OBOPAY B/C payouts

This table contains records created per B/C agreement. These can be advances (10),
settlement (90) and print a preview of settlement (99).

OBOPER B/C status per recipient per period

This table contains the period balances of the generating value, paying amount and
reservations per recipients. The periods are according to the period type in the B/C
agreement.

OBOTRA B/C transaction file

This table contains all transactions made per recipient. The transactions can be invoices,
advances and settlements.

OBOWRK Qualified for B/C payout

This table contains advance proposals created per B/C agreement and recipient. When the
advances are approved and transferred to the batch order entry, the records will be removed
from this table.

6
Budget
A budget is a quantified financial plan for a forthcoming accounting period. M3 budgeting
enables the actual financial operation of the business to be measured against the forecast.

FBRDEF

FBRESP FBTMPH FBTMPD

FBDCTH FBDCTD

FBDIST FBUDEF FBUDIH

FBUSUM FBUDIS

FBUDET

FBUDAY

FBDCTD Budget per budget - responsible - detail

Contains detailed information of the sub-budget.

FBDCTH Budget per budget – head

Contains a sub-budget which is used in a decentralized management environment, allowing
each budgeting officer to control his or her separate budgeting. A decentralized budget can be
used to create a central budget.

7
FBDIST Distribution template head
Contains accounts allocation template information for a budget connected to an accounts
allocation template.

FBRDEF Resource
A resource is something that the department manager needs in order to run the department,
such as number of employees or heating cost per square meter.

FBRESP Budget responsible

Contains data indicating the person or function in the organization responsible for the budget.

FBTMPH Budget template - head

A budget template header that can hold several line with useable information.

FBTMPD Budget template - detail

This detailed table consists of at least one line with a resource or account connected to it.

FBUDAY Budget detail

Contains information about budget changes on a daily basis. This file is used in the module
Cash Flow Management.

FBUDEF Budget
This is the header table and contains common information about a budget.

FBUDET Budget detail

Contains a specification of FBUSUM at period level.

FBUDIH Budget distribution – selections

Contains accounts allocation selection information for a budget connected to an accounts
allocation template.

FBUDIS Budget distribution detail

Contains accounts allocation detail information for a budget connected to an accounts
allocation template.

FBUSUM Budget entry

Contains accumulated budget values at the level of accounting string, currency code and
allocation template.

8
Company structure
A company structure contains different divisions, which are separate legal entities. Each
division can contain different facilities, which in turn contains different warehouses.

CMNCMP

CMNDIV

CFACIL

MITWHL

CFACIL Facility master

Contains basic data for facilities.

CMNCMP Company master

Contains basic data for company structures.

CMNDIV Company/Division
Contains basic data for divisions.

MITWHL Warehouse
Contains basic data for warehouses.

9
Cost accounting
The internal account entry table CINACC contains costs from various accounting events and
types within the company, and may be used to aid in decision making by providing costs
divided into several accounting dimensions. CINACC is updated by different function
programs, which are either called manually or by a scheduled run, or else triggered by
various transaction events.

MWOPTR CPOHED

MITTRA MWOPTS MMOPTR CPOCAW CPOMAT CPOOPE CRACTR

CINACC

FCR040

FGLEDG

CINACC Internal account entry

Contains internal account entries, some of which may also be transferred to ledger accounts
via the work table FCR040.

CPOCAW Post calculation maintenance

Contains costing component amounts per product number and order number.

CPOHED Order Costing Header

Contains order costing totals, as a summation of CPOMAT and CPOOPE.

CPOMAT Order Costing Material lines

Contains material order costing and quantity for work orders, manufacturing orders and
purchase orders. It also holds an accounting number field that is updated when account
entries are created in CINACC.

10
CPOOPE Order Costing Operation lines
Contains operation order costing and labor/machine run time for work orders, manufacturing
orders and purchase orders (such as subcontracted operations). It also holds an accounting
number field that is updated when account entries are created in CINACC.

CRACTR Various accounting transactions

Contains other types of transactions, for example standard cost changes or cost of goods
sold.

FCR040 Acc. transactions for update of GL

Contains all transactions that will update General ledger. A check is done for erroneous posts
before transferring to FGLEDG, and invalid posts will be stuck in FCR040 until taken care of.

FGLEDG General ledger

Contains all General ledger transactions.

MITTRA Stock transactions

Contains stock transaction history, created from all transactions affecting a warehouse, such
as receiving or reclassifying goods.

MMOPTR Operation transaction

Contains reported operations per work order, including data such as time rates and
labor/machine run time used.

MWOPTR Operation transaction

Contains reported operations per manufacturing order, including data such as time rates,
labor/machine run time used and manufactured quantity.

MWOPTS Cumulative operation transactions

Contains a summary of reported operations per manufacturing order. It also holds an
accounting number field that is updated when account entries are created in CINACC.

11
Customer
A customer may be a person, although most commonly it’s defined as an organization. Every
sales transaction requires a customer to exist in the customer master table. Other tables
closely linked to that table contain more detailed information, such as address types or credit
limits.

OCUSCH ODCHRG

CCUCRL OCUSMA

CCUDIV OCUSCO OCUSAD OCUSIT CEMAIL

CCUCON

CCUCON Contact person

This table displays the customer contacts.

CCUCRL Customer credit limit

This table displays’ different types of credit limits e.g. limits based on overdue invoices or
outstanding invoices. If this limit is exceeded, delivery of the customer order is blocked.

CCUDIV Customer Local exceptions

This table makes it possible to create local exceptions based on division, e.g. due to different
currencies.

CEMAIL E-mail address

This table contains different e-mail types tied to the customer, different e-mail types such as
customer, payer and invoice recipient.

OCUSAD Customer address

This table contains information about the customer site address where it is possible to add
different types of addresses such as delivery, invoice or confirmation address.

12
OCUSCH Connect customer charges
This table connects the defined charges in table ODCHRG to the customer. The charges
connected to the customer are used to retrieve charges automatically to the order header
during the order entry.

OCUSCO Customer connect contact

This table connects the defined contact persons in table CCUCON to the customer.

OCUSIT Customer item

This table contains basic data per customer and item.

OCUSMA Customer master

The table is the master data table for customers and is used to validate customer numbers.
The table also contains information about external or internal customers and includes service
order data; this is where the basic data for service orders are stored e.g. price lists, Service
manager and technician.

ODCHRG Customer charges

This table contains customer charges, e.g. for administrations or deliveries.

13
Customer blanket agreement
A customer blanket agreement is where a customer and a supplier enter a time-limited
agreement covering terms, items and prices. During the validity period of the agreement, the
customer can make call-offs against the agreement for a portion of the goods covered. The
customer agreement header is stored in table OAGHRE, while the customer agreement lines
are stored in table OAGRLN.

OAGRHE

OAGRPR OAGRLN OOLIAR

OAGHLN Customer agreement lines

This table contains the customer agreement lines connected to a customer agreement
header.

OAGHRE Customer agreement head

This table contains the customer agreement headers.

OAGRPR Customer agreement price

This table contains the customer agreement prices. One customer agreement line can have
more than one customer agreement price since prices can be scaled.

OOLIAR Customer order line agreement reference

This is a transaction table containing customer order lines connected to a customer
agreement line.

14
Customer order
The customer order header is stored in table OOHEAD, while the customer order lines are
stored in table OOLINE. Documents connected to the customer order header are stored in
table OODOCU. Charges (both internal and external) can be put on both the customer order
header and the customer order lines. Charges connected to the customer order header are
stored in table OOCHRG and charges connected to the customer order lines are stored in
table OOLICH.

OODOCU

OOCHRG OOHEAD OOADRE

OOLICH OOLINE

OSASTD

OOADRE Customer order address

This table contains “order unique” addresses.

OOCHRG Order charges

This table contains charges per order. The charges can be external, i.e. invoiced to the
customer, or internal, i.e. only for statistics and bookkeeping.

OODOCU Customer order documents

This table contains the documents connected to the customer order header.

OOHEAD Customer order header

This table contains the customer order headers.

OOLICH Line charges

This table contains line charges connected to an order line. The charges can be external, i.e.
invoiced to the customer, or internal, i.e. only for statistics and bookkeeping.

OOLINE Customer order lines

This table contains customer order lines.

OSASTD Order sales statistics, detail

This table contains orders received, not orders delivered.

15
Customer order invoicing
The CO invoicing process starts when invoicing is performed and is based on a customer
order that has been delivered or an advance invoice record that has been entered. Invoicing
contains customer order invoicing, advance invoicing and corrective invoicing.

OINVIP OINREF

OOPINV

ODHEAD OINVOH

OOCHRG ODLINE OINVOL OINACC

OOLICH

ODHEAD Delivered Customer Order Headers

This table contains all delivered customer orders’ order headers and is the basis of the orders
to be invoiced.

ODLINE Delivered Customer Order Lines

This table contains all delivered customer orders’ order lines and is the basis of the order lines
to be invoiced

OINACC Invoice Accounting

This table contains all invoice accountings that should be transferred or are transferred to the
General Ledger (transaction code 11) and Accounts Receivable (transaction code 10). A
status code specifies if a transaction is transferred or not.

OINREF Invoice Reference

This table is a transaction table used to store references between original and corrective
invoice(s).

16
OINVIP Invoices in Progress
This table is a work table containing invoices in progress during invoicing. If an abnormal end
of the invoicing program has occurred, the restart of interrupted invoicing program uses this
table for the restart.

OINVOH Invoice Headers

This table contains all invoiced customer orders’ invoice headers and is the basis for creating
invoice accountings (to Accounts Receivable).

OINVOL Invoice Lines

This table contains all invoiced customer orders’ invoice lines and is the basis for creating
invoice accountings (to General Ledger).

OOCHRG Order Charges

This table contains charges per order. The charges can be external, i.e. invoiced to the
customer, or internal, i.e. only for statistics and bookkeeping. Internal charges are not invoiced
to the customer.

OOLICH Line Charges

This table contains line charges connected to an order line. The charges can be external, i.e.
invoiced to the customer, or internal, i.e. only for statistics and bookkeeping. Internal charges
are not invoiced to the customer.

OOPINV Advance invoicing

This table contains information of those customer orders that should be invoiced in advance
on specific dates.
During invoicing this table is used to retrieve information for the advance invoicing such as
amount, advance- invoice date, terms of payment, etc. At advance invoicing, information is
retrieved from table OOPINV (no ODHEAD records) to table OINVIP.
At final invoicing (ODHEAD record exists) a check is performed if advance invoicing has been
done, if so, information about advance invoice amount is retrieved from table OOPINV and is
deducted on the final invoice via table ODHEAD.

17
Delivery
A delivery is a dispatch of orders between a warehouse and usually a customer or another
warehouse.
The table MHDISH contains information about when the delivery occurs, and connects to
records of how the delivery will be performed and to/from what warehouse. MHDISL holds the
quantities to be delivered and connects to the order lines.

MHDIPO MITWHL MITALO

MHDISH MHPICH

DROUTE MHDISL

MGLINE OOLINE MPLINE

DROUTE Route
This table contains information regarding place of load, place of unload and how a delivery or
shipment is transported.

MGLINE Distribution order/Requisition order line

This table contains distribution-, requisition- and move location- order lines.

MHDIPO Dispatch policy

This table contains dispatch policy records. The dispatch policy holds rules regarding
delivery.

MHDISH Delivery
This table contains direction of the delivery and information of the sending and receiving
location.

MHDISL Delivery lines

This table contains the connection between delivery and order lines. It tells how much of an
order line that will be delivered on a delivery.

18
MHPICH Picking list header
This table contains data regarding picking list header per delivery number. A picking list
header holds information regarding among others, picking status.

MITALO Allocation
This table contains a specification of the connection of what item and which quantity in the
warehouse that is allocated to which order line.

MITWHL Warehouse
This table contains basic data for a warehouse.

MPLINE Purchase order line

This table contains information about the different purchase order lines belonging to a record
in table MPHEAD.

OOLINE Customer order line

This table contains customer order lines. Some basic information is retrieved from this table
during invoicing and is also updated with information such as status, invoiced quantity, etc.

19
Distribution order / Requisition order
Table MGHEAD contains basic data for distribution and requisition orders. Order lines
connected to the order head are stored in MGLINE.
Each order header is connected to either two warehouses (stored in MITWHL) for distribution
orders, or only one warehouse for requisition orders. This difference occurs due to that
distribution orders goes two-way, from one warehouse to another, while requisition orders
goes one-way – a warehouse it either demanding or sending away something.

MGTYPE MGHEAD MITWHL

MGLINE

MGHEAD DO/RO Header File

Contains the basic data for distribution and requisition orders.

MGLINE RO/DO Line file

Contains the order lines connected to a Req/Distr Order head.

MGTYPE Transaction types parameters

Contains order types for distribution orders, requisition orders and move orders. It is
unfortunate that the table description on this table is “Transaction types parameters”. The
order type sets the characteristics of the order and controls the order.

MITWHL Warehouse
Contains basic data for a warehouse.

20
Distribution order proposal
DO orders are created from distribution order proposal. When there is a demand a proposal is
created. When the DO is supposed to be issued, and the demand is unfulfilled, the proposal
will be updated to a sharp order.

MITBAL

MGTYPE MDOPLP MITWHL

MITPLO

MDOPLP Distribution order proposal

This table contains distribution order proposals, i.e. distribution orders that are not firm
planned.

MGTYPE RO/DO Types

This table contains configuration parameters for the handling of different requisition and
distribution orders.

MITBAL Item - Warehouse

This table contains item details per warehouse, which means it contains item details that may
vary between warehouses. It also contains aggregated quantities per item and warehouse.

MITPLO Material Plan

This table contains all planned stock transactions. It is updated from all other routines where
planned stock transaction exists. It is then used for detailed planning decisions.

MITWHL Warehouse
This table contains basic data for a warehouse.

21
Financial accounting
FSLEDG and FPLEDG contain information about AR (Accounts Receivable) and AP
(Accounts Payable) payments and invoices, which is not stored in the General Ledger,
FGLEDG. FGLEDG stores all transactions in the General Ledger, and its balance values are
stored in FBAVAL. The balance values for AR and AP are stored in FSLBAL and FPLBAL,
respectively.

FSLEDX FGLEDX FPLEDX

FSLEDG FGLEDG FPLEDG

FSLBAL FBAKEY FPLBAL

FBAVAL

FBAKEY General Ledger keys for balance values

Contains all keys, which are a set of 8 balance dimensions, in the balance table.

FBAVAL General Ledger balance values

Contains all values connected to FBAKEY.

FGLEDG General Ledger

Contains all general ledger transactions. Transactions containing more information in
Accounts Payable or Accounts Receivable are indicated by a transaction code.

FGLEDX General Ledger extra information

Contains extra information per transaction in FGLEDG.

FPLBAL Accounts Payable balance file

Contains the Accounts Payable balance values per supplier and period.

FPLEDG Purchase ledger

The Purchase Ledger contains invoices and payments for Accounts Payable. Transactions
with transaction code 40 and 50 in the General Ledger are found in this table.

22
FPLEDX Purchase ledger extra information
Contains extra information per transaction in FPLEDG.

FSLBAL Accounts Receivable balance file

Contains the Accounts Receivable balance values per customer and period.

FSLEDG Sales ledger

The Sales Ledger contains invoices and payments for Accounts Receivable. Transactions
with transaction code 10 and 20 in the General Ledger are found in this table.

FSLEDX Sales ledger extra information

Contains extra information per transaction in FSLEDG.

23
Fixed asset
The fixed asset master contains important asset and depreciation data. The asset data for
each asset makes it possible to record the specific information that your plant, property and
equipment comprises. You can enter an impressive amount of information for each fixed
asset.

MILOIN FFASDM FFAINS FFASVL

FFASMA

FFATXG

FFAHIS Fixed asset history file

Contains the different values for an asset for each period and value type.

FFAINS Fixed asset insurance

Contains the information regarding insurance for a fixed asset.

FFASDM Fixed asset depreciation rules

Contains the depreciation rules for a fixed asset.

FFASMA Fixed assets file

Contains all common data for a fixed asset.

FFASVL Fixed asset values

Contains different values for an asset. These values are defined by value types and are
defined by the user.

FFATXG Fixed asset tax group

Contains the information about which tax asset group the fix asset belongs.

MILOIN Serial number

Contains the information about the equipment.

24
Item
An item is a central object that must be defined in order to perform actions such as
purchases, sales and manufacturing.

MILOMA MITVEN MITFAC MITBAL MITAUN

MITMAS

MCFMOD MITPOP MITALT MMETER MCFCVA MITTRS MITLAD

MCFCVA Component (Variant)

Contains information about variants on a model

MCFMOD Model/Site
Contains information about Models/As-built structures.

MILOMA Lots/Serial Numbers

Contains the details about lots. The information is stored per item and lot number.

MITALT Related Items

Contains related item numbers. How item numbers are related or interchangeable is
specified here.

MITAUN Alternate Units of Measure

Contains alternate units of measure per item. The alternate unit can be one of two types;
quantity unit or price unit. The details per records contains the relationship between quantity
in the alternate unit and quantity in the basic unit. It also contains details about whether the
unit is standard unit for some type of order.

25
MITBAL Item/Warehouse
Contains item details per warehouse and aggregated quantities per item and warehouse.

MITFAC Item/Facility
Contains item details per facility

MITLAD Language Descriptions

Contains item description per language.

MITMAS Item Master

Contains basic data for items on company level. Example of data is item group, gross weight
and volume.

MITPOP Alias Numbers

Contains aliases per item number. An alias is an alternate item number for an item.

MITTRS Item transport data

Contains item transportation codes per item.

MITVEN Item/Supplier
This table contains supplier information per item.

MMETER Meter per item

Contains information about which meters that should be monitored on an Item.

26
Maintenance customer order
A maintenance customer order (MCO) may be created when a customer wants to have some
kind of maintenance performed on an object, such as a vehicle. During order details entry,
you specify what service is to be performed on a specific object, how the work is to be priced
and the different dates, such as when the object is to be received and when it is to be
returned to the customer. From the order lines in ACUORL a work order proposal is created
in MWOPLP, which may then be released to create a real work order.

ACUAGH ACUAGL

OCUSMA

ACUORA ACUORD ACUORC

ACUOTY ACUORH ACUORP

ACUIVH ACUORL MWOPLP

ACUIVL ACUOLS ACUORM ACUORN

ACUIVR ACUINV

ACUICH

27
ACUAGH Agreement header file - service
Contains agreement information such as discounts, charges and delivery terms.

ACUAGL Agreement lines

Contains pricing information per product.

ACUICH Items charges per trans line

Contains charges connected to a separate material transaction line.

ACUINV Invoice specification

Contains specified invoice information of the costing types material, operation, subcontracting
and miscellaneous.

ACUIVH Invoice header

Contains invoice header.

ACUIVL Invoice lines

Contains invoice lines.

ACUIVR Invoice lines references

Contains references to the order, connecting the invoice with agreement and item number.

ACUOLS Order line summary

Contains cost summaries of the order lines that are used for invoicing.

ACUORA Customer order, address

Contains various address types connected to the customer and order.

ACUORC Order charges

Contains charges connected to the order.

ACUORD Order documents

Contains various order documents, such as quotations, confirmations or payment requests.

ACUORH MCO header

Contains the maintenance customer order header.

ACUORL MCO line

Contains line information, such as product number, serial number and service.

ACUORM Order line – invoice split

Contains financial information of the order line, e.g. if there should be several payers.

ACUORN Order line - discount

Contains discounts connected to an order line.

ACUORP Pre-payment invoice

Contains information of advance payments.

28
ACUOTY Order type
Contains order type settings that determine how the order is processed during order entry
and during the processing flow.

MWOPLP Work requests

Contains work order proposals. One order line can result in a separate work order.

OCUSMA Customer
Contains customer master data.

29
Manufacturing order
Manufacturing orders can be created manually, from proposal or via batch. The
manufacturing order head is created in MWOHED, operations and materials are connected to
the header and saved in tables MWOOPE and MWOMAT. The manufacturing order type,
MWORDT, has a key role when creating an order. The table holds parameters and data
which govern the manufacturing order process.

MWORDT MPDCHF

MWORCO MACHED

MWOMAA MWOMAT MWOHED MACMAT

MITTRA MACOPE

MWOOPE

MWOPTR MWOCPN MWOPOL MWOOPS

MACHED Manufacturing statistics

This table contains manufacturing order head statistics.

MACMAT Manufacturing material statistics

This table contains material statistics.

MACOPE Manufacturing operation statistics

This table contains operations statistics.

MITTRA Material transactions

This table contains material transactions. The table is populated when a material is reported.

MPDCHF Config simulation

This table contains the configuration header. The table is created when configuring products
from a manufacturing order.

MWOCPN Coproduct per operation number

This table contains the manufactured coproducts. The table includes data on how much of a
share that results in a co-product for a given operation.

30
MWOHED Manufacturing order head
This table contains the manufacturing order head holding information for the complete order.

MWOMAA Manufacturing order – alternative material

This table contains the alternative material connected to a material line. The alternative
material can replace the normal component in a shortage situation.

MWOMAT Material file

This table contains the material connected to the manufacturing order. The types of material
that can be connected are normal components and by-products.

MWOOPE Operation file

This table contains the operations connected to a manufacturing order.

MWOOPS Routing operation activity description

This table contains elements that should be done in an operation and which tool to use.

MWOPOL Work order production lots

This table contains which production lots that are connected to an operation.

MWORCO Rate compensators per material

This table contains the material that should compensate an active material.

MWORDT Manufacturing order type

This table contains the manufacturing order types. The order type contains data used to
decide what type of manufacturing order flow can be used.

MWOPTR Operation transactions

This table contains operations transactions. The table is populated when an operation is
reported.

31
Manufacturing order proposal
Manufacturing orders proposals can be created manually or generated, for example via MRP
or order initiated. Regardless of situation, the two important tables in this context are MITPLO
and MMOPPO. These tables hold data about the materials and operations connected to the
proposal. When the manufacturing order proposal is released, the result will be a
manufacturing order with the header created in MWOHED.

MMOPLP

MITPLO MMOPPO

MITPLO Material Plan

This table contains the planned stock transactions including the material demands connected
to the manufacturing order proposal.

MMOPLP Manufacturing order proposal

This table contains the actual manufacturing order proposal. When the planned
manufacturing proposal is released, a header for the order is created in table MWOHED.

MMOPPO Operation list for proposal

This table contains the list of operations included in the manufacturing order proposal.

32
Pre–allocation
Pre-allocation is to set aside an incoming quantity for a demand.
For every record in MPREAL there is one record from two tables, one for demand and one for
supply. The tables above MPREAL in the model, contributes with the supply records and the
ones below with the demand records. However MGLINE can contribute with both demand
and supply records.

MPLINE MWOPLP MDOPLP MMOPLP MWOHED

MPREAL

MGLINE OOLINE MDEOHE SSLINE MWOMAT

MDEOHE Demand order

This table contains demand order records

MDOPLP Distribution planning proposal

This table contains distribution order proposals in form of planned orders.

MGLINE Distribution order/Requisition order line

This table contains distribution-, requisition- and move location- order lines.

MMOPLP Stock issues to WIP

This table contains manufacturing order proposals in form of planned orders.

MPLINE Purchase order line

This table contains information about the different order lines belonging to a record in table
MPHEAD. The table contains data for the order lines such as item number prices, discounts,
delivery times, status and goods receiving method. The table also contains confirmation data,
delivery data, goods receiving results, claim data and invoice data.

MPREAL Pre-allocation
Pre–allocation connects demand and supply tables to each other and the belonging quantity.

MWOMAT MO Material file

This table contains material and operation lines.

33
MWOHED Manufacturing order header
This table contains manufacturing order header record.

MWOPLP Work request

This table contains work request records.

OOLINE Customer order line

This table contains customer order lines. Some basic information is retrieved from this table
during invoicing and is also updated with information such as status, invoiced quantity, etc.

SSLINE Service order line

This table contains information about planned or used spare parts, service expenses for work
time, traveling time, etc.

34
Product costing
Product costing is a way of building a cost structure of a product, derived from different areas
such as raw material costs, labor costs in manufacturing or distribution costs. Its purpose is to
help managerial decisions in an operational context rather than to measure corporate
performance.

MITFAC MCCOPU

MCCOTY MCHEAD MCCOMA

MCCCID MCCOML

MCCCDF

MCCOMP MCCELE

MCMACO MCPRCO MCWCCO MCBOEL

MCBOEL Bill of element

Contains bill of costing elements with different purposes, such as a more summarized
presentation level.

MCCCDF Costing model definition

Contains the costing model that can consist of costing components, costing elements, part
summaries and total.

MCCCID Product costing model

Contains model name and description.

35
MCCELE Product costing element
Contains basic data for the costing element. Costing elements consist of cost drivers and are
used to build costing models for purchased components.

MCCOMA Costing component aggregated

Contains summaries for all costing components on all levels.

MCCOML Costing component this level

Contains summaries for all costing components on this level. All lower levels are added to
material cost.

MCCOMP Costing components

Contains basic data for the costing component. Costing components are used to calculate the
cost for a manufactured product.

MCCOPU Purchase costing file

Contains cost prices for purchased items and subcontracting operations.

MCCOTY Costing types

Contains configuration parameters for the handling of different costing types.

MCHEAD Product costing header

Contains part summaries and total sum for calculated identity

MCMACO Material add on costing data

Contains costing rates for material and subcontracting overheads.

MCPRCO Product overhead

Contains costing rates for product common costs.

MCWCCO Work center costing data

Contains costing rates for operation costs.

MITFAC Item – facility

Contains costing data such as the costing model.

36
Purchase order
Purchase orders can be created manually, from a proposal or via batch. Purchase order
headers are created in MPHEAD and the lines connected are created in MPLINE. The
purchase order type, MPORDT, has a key role when creating an order. The table holds
parameters and data which govern the purchase order flow.

MXHEAD MPORDT MPURST MPPOAD MPAUTD

MPHEAD

MPPEXP MPPOEX

MPOPLP MPLINE MPOPLA

MXLINE MPLIND MPOEXP

MPAUTD Authorization distribution

This table contains authorization data per user for purchase orders.

MPHEAD Purchase order – header

This table contains the purchase order header holding information for the complete order.

MPLIND Purchase order - line transactions

This table contains purchase order line transactions. The transactions are always registered
when a purchase order line is affected by an increase in status.

MPLINE Purchase order – line

This table contains the purchase order lines. Besides storing basic data like item-number,
quantity and purchase price, the table also contains e.g. the goods receiving method.

37
MPOEXP Purchase order connect charges
This table contains the purchase order charges. The charges are based upon the costing
model and the including elements.

MPOPLA Planning proposal archived

This table contains archived purchase order proposals.

MPOPLP Planned purchase order

This table contains purchase order proposals in form of planned orders. When a planned
purchase order is released, a header record is created in MPHEAD.

MPORDT Purchase order types

This table contains the purchase order types. The order type contains data used to decide
what type of purchase order flow can be used

MPPEXP Whole sale calculate proposal

This table contains the charges calculated on the purchase order proposal.

MPPOAD Purchase order address

This table contains the purchase order address. The valid addresses are supplier address,
ship-via address, invoice address and final destination address.

MPURST Purchase statistic

This table contains purchase statistics

MXHEAD Purchase order head – batch

This table contains the purchase order head created from batch. The table holds the same
data as MPHEAD.

MXLINE Purchase order line – batch

This table contains the purchase order lines created from batch. The table holds the same
data as MPLINE.

38
Purchase order agreement
Purchase prices are normally fetched from a purchase agreement header which is connected
to a purchase order line. Various types of agreement headers are stored in MPAGRT and
govern which type of agreement header that is created. This includes for instance a discount,
blanket or a volume-based agreement. The lines are connected to the header and stored in
table MPAGRL. The prices are in turn set up per each unique line and stored in table
MPAGRS.

MPAGRT

MPAGRH CIDMAS

MPAGRX MPAGRL MPAGRI

MPAGRP

CIDMAS Supplier
This table contains master supplier information; supplier type, status, country codes etc.

MPAGRH Purchase agreement header

This table contains purchase agreement headers.

MPAGRI Purchase agreement loan charges

This table contains agreement loan charges. The charges applied are valid from a specified
day and forward.

MPAGRL Purchase agreement lines

This table contains the purchase agreement lines. The agreement lines are based on a
search pattern of user-defined fields (Group ID).

MPAGRP Purchase agreement price

This table contains the purchase agreement prices. Price setup is reached from the
agreement lines.

39
MPAGRT Purchase agreement type
This table contains the agreement types. The types hold settings that determine how a
purchase agreement is processed.

MPAGRX Purchase price index

This table contains the purchase price index which is connected to the agreement header.

40
Report generator
This is used to define a report within the financial system. The report helps you to organize
and present information in the financial system in a clear and manageable way. The report
can also be distributed to different categories of people, within and outside the company.
Reports can be printed on regular paper, saved as a document or sent as a file to another
user. In addition, you can convert reports and transfer them as files to a PC for processing in
spreadsheet or word processing program.

FFRCSL FFRCCL FFRLSL FFRLCL FFRLTX FFRXCL

FFRCDF FFRLDF FFRXDF

FFRDEF

FFRPCI FFRPCL FFRPCH

FFRCCL Column calculations

Contains one record for each calculation in a calculation column.

FFRCDF Column definitions

Contains one record with common data for each column within the report number. Classifies if
the column is a detail, calculation or text column.

FFRCPH Report generator. PC-file headings

Contains column headings for each report.

FFRCSL Column selections

Contains one record for the selection that is made for each column. Holds from and to values
for the selected dimensions in the balance key.

FFRDEF Report definitions

Contains all common data for each report. One record for each report number.

41
FFRLCL Line calculation
Contains one record for each calculation in a calculation line.

FFRLDF Line definitions

Contains one record for each line within the report. It contains common data for one line such
as description and classification of lines in detail lines, calculation lines, text lines and external
lines.

FFRLSL Line selections

Contains one record for the selection that is made for each line. Holds from and to values for
the selected dimensions in the balance key.

FFRLTX Text lines

One record for each defined text line in the report.

FFRPCI Report generator, PC-file lines, details

Contains reports per predefined user to be distributed or viewed

FFRPCL Report generator, PC-file lines

Contains report results per each report line for each period

FFRXCL Cell calculation

One record for each calculation within the cell.

FFRXDF Cell definitions

Contains one record for each defined cell in the report.

42
Service agreement
The service agreement headers are stored in table SAHEAD and documents connected to
the service agreement header are stored in table SADOCU. Charges (both internal and
external) can be put on both the service agreement header and the service agreement
location. Charges connected to the service agreement header are stored in table SAHCHR
and charges connected to the service agreement location are stored in table SALCHR.

SADOCU

SAHCHR SAHEAD SAGCON

SALCHR SALOCA SAADRE

SALINE

SAADRE Customer address

This table contains information about the customer site address if an address number is used
or a temporary address has been entered manually. If only a customer is used, no address
information is stored in this table.

SADOCU Agreement documents

This table contains documents connected to the service agreement header.

SAGCON Contents of an agreement

This table defines what’s included or not included in the agreement.

SAHCHR Agreement header charge

This table contains charges connected to a service agreement header. If the agreement
contains several customer sites, these charges will be invoiced on the first site of the
agreement.

SAHEAD Agreement header

This table contains the agreement header

SALCHR Agreement location charges

This table contains charges connected to an agreement location.

43
SALINE Agreement line
This table contains information about the agreement lines connected to a customer site.

SALOCA Customer site per agreement

This table contains information about the different customer sites on an agreement. Default
values are retrieved from the agreement header but can be changed.

44
Service order
The service order headers are stored in table SSHEAD, the service order assignments are
stored in table SSJOBH and the service order lines are stored in table SSLINE. Documents
connected to the service order assignment are stored in table SJDOCU. Charges (both
internal and external) can be put on the service order header, the service order assignment
and the service order lines. Charges connected to the service order header are stored in table
SSOCHR, charges connected to the service order assignment are stored in table SJOCHR
and charges connected to the service order lines are stored in table SSLICH.

SSOCHR SSHEAD SSADRE

SJOCHR SSJOBH SJDOCU

SSLICH SSLINE

OSBSTD

OSBSTD Sales statistics detail

This table contains the sales statistics for all service orders

SJDOCU Service order assignment documents

This table contains the documents connected to the service order assignment.

SJOCHR Service order assignment charges

This table contains charges connected to a service order assignment.

SSADRE Service order address

This table contains information about the customer site address if an address number is used
or a temporary address has been entered manually at service order entry. If only a customer
is used, no address information is stored in this table.

SSHEAD Service order header

This table contains the service order headers.

45
SSJOBH Service order assignment
This table contains information about service order assignments connected to a service order
header.

SSLICH Line charges

This table contains line charges connected to a service order line.

SSLINE Service order lines

This table contains information about the service order lines connected to a service order
assignment.

SSOCHR Order charges

This table contains charges connected to a service order header.

46
Service order - Individual item
Individual items are stored in table SINDIV. A service agreement or a service order can then
be created for the individual item. Additional information, such as information regarding
meters and version information, is stored in tables SINDMD and SINVER, while documents
connected to the individual items are stored in table SINDDO.

SINDMD SINVER

SINDDO SINDIV SAGITM

SSJOBH

SALINE SSLINE

SAGITM Contract item

This table contains the contract item, which is the item that is invoiced when an agreement
line is invoiced. In the individual item table, a contract item for service agreement can be
entered. If entered, they will be proposed when an agreement line is created for the individual
item.

SALINE Agreement line

This table contains information about the agreement lines connected to a customer site.

SINDDO Individual item document

This table contains the documents connected to the individual item.

SINDIV Individual items

This table defines the service objects that an agreement or service order should be entered
for.

47
SINDMD Individual item meter detail
This table contains information about meters that are used for an individual item.

SINVER Information versions per individual item

This table contains date, status and description of information versions that exist for an
individual item.

SSJOBH Service order assignment

This table contains information about service order assignments connected to a service order
header.

SSLINE Service order lines

This table contains information about the service order lines connected to a service order
assignment.

48
Stock
Stock is defined as quantities per location and stored in MITLOC. MITBAL, which holds
records of quantities per warehouse, is not considered stock.

MITWHL MITPCE

MITBAL MITLOC MCONMA

MITMAS MILOMA

MCONMA Container master

This table contains records of containers.

MILOMA Lot file

This table contains basic data for a lot/serial number. It can be created both manually and
automatically.

MITBAL Item – Warehouse

This table contains records regarding items per warehouse. Examples of records are reorder
point, and on-hand balance.

MITLOC Balance identity

This table contains records regarding stock quantity for given item/location/lot or container
combination. If multiple locations are used for an item, quantities on every balance ID are
stored here.

MITMAS Item Master

This table contains master data for items in a company.

MITPCE Stock location

This table contains basic data for a stock location. Examples are Stock zone and Location
type.

MITWHL Warehouse
This table contains basic data for a warehouse.

49
Stock transaction
Information regarding stock transactions is saved in order to be able to trace movements in
resources.
Each record in MITTRA can, and must, only be connected to at least one record in MITLOC,
the location from where the quantity is taken to fulfill a demand. It is not necessary that there
is a connection to an order line.

MITLOC

MITTRA

MDEOHE MPLINE OOLINE MGLINE MWOHED

MDEOHE Demand order

This table contains demand order records.

MGLINE Distribution order/Requisition order line

This table contains distribution-, requisition- and move location- order lines.

MITLOC Balance identities

This table contains records regarding stock quantity for given item/location/lot or container
combination. If multiple locations are used for an item, quantities on every balance ID are
stored here.

MITTRA Stock transaction

This table contains detailed historical stock transactions on item level.

MPLINE Purchase order line

This table contains information about the different order lines belonging to a record in table
MPHEAD. The table contains data for the order lines such as item number prices, discounts,
delivery times, status and goods receiving method. The table also contains confirmation data,
delivery data, goods receiving results, claim data and invoice data.

MWOHED Manufacturing order header

This table contains manufacturing order header record.

OOLINE Customer order line

This table contains customer order lines. Some basic information is retrieved from this table
during invoicing and is also updated with information such as status, invoiced quantity, etc.

50
Supplier
The master table of supplier is CIDMAS; this is where the basic supplier data is stored.
CIDVEN stores information directly related to purchasing. The table is also highlighted as a
master table because of its important relation to CIDMAS.

CIDREF MVENST CIDADR

CIDMAS MPSURE

MIDQCG CIDVEN

MIDTLE MIDOTY MRPDTH MIDDST MIDSCH MIDDSC CIDVAT MIDDET

CIDADR Vendor address

This table contains address information about the supplier. Valid address types are postal,
street, bank and final delivery address.

CIDMAS Supplier
This table contains master supplier information; supplier type, status, country codes etc.

CIDVAT Supplier TAX number

This table contains VAT codes for suppliers in different divisions.

CIDVEN Supplier – purchase & finance

This table contains supplier information directly connected to purchasing. The information is
supplier type status etc.

CIDREF Supplier reference

This table contains reference data belonging to the supplier. The data is copied to the
purchase order header.

MIDDET Vendor delivery terms text

This table contains supplier terms and text.

51
MIDOTY Vendor order types
This table contains valid order types for a specific supplier. The information is used in the
purchase order flow.

MIDDSC Vendor discount

This table contains supplier discounts from a beginning date. The discount is used in price
calculations for purchase order lines.

MIDOTY Vendor order types

This table contains valid order types for a specific supplier. The information is used in the
purchase order flow.

MIDSCH Vendor charge

This table contains limit values for different charge types and charge values. The data is
compared when ordering a purchase order.

MIDTLE Vendor transport lead time

This table contains information about transportation lead time for a specific delivery term
connected to a supplier.

MIDQCG Quality class

This table contains quality class belonging to a delivery group.

MPSURE Supplier return settings

This table contains settings for surplus return. The settings are based on the surplus return
type.

MRPDTH Point of time

This table contains the supplier’s calendar expressed from Monday to Sunday. Valid day
types to be specified are calendar days, working days, shipment days and goods receiving
days.

MVENST Vendor statistics

This table contains supplier statistics.

52
User
The user table contains data about the user definition. Various tables that contain roles and
positions are directly connected to the user table, handling permissions and responsibilities
for users. To set up a new user, a table with start values is also needed.

FBRESP SSRESP

CMNUSR CEAEMP

CSYUSR CSYSTR

CEAEMP Employment file

Contains data about the user’s employment, such as the employee number etc.

CMNUSR User definition file

Contains basic data about users.

CSYUSR Users per company

Contains defined permissions for which users that have access to which companies and
divisions.

CSYSTR Start values and parameters / program

Contains start values to set up a user.

FBRESP Budget responsible

Contains defined permissions for users (or functions) that are budget officers, i.e. responsible
for the budget.

SSRESP Service responsible

Contains defined permissions for users that are service managers, which can be either a
person or a department head for one or more technicians.

53
Warehouse
Warehouse is a central entity when it comes to item management. Item quantities are defined
on warehouse level; all material transactions are connected to order lines, which in turn are
always connected to a warehouse.

CFACIL

MITWHL

MITARE MITPCE

CFACIL Facility master

This table contains basic data for a facility.

MITARE Stock zone

This table contains basic data for a stock zone.

MITPCE Stock location

This table contains basic data for a stock location. Examples are Stock zone and Location
type.

MITWHL Warehouse
This table contains basic data for a warehouse.

54
Work order
A work order is normally created as a scheduled job, generated as a proposal in the table
MWOPLP. When it has been released, a work order header is created in MMOHED and a
history post made in MWOPLA while it disappears from MWOPLP. A work order can either be
service of your own equipment or be connected to a customer in a maintenance customer
order (MCO).

CFACIL MITFAC MITBAL

MMORDN MMORDT MMOHED MMOMAT

MWOPLA MMOOPE MMOOPS

ACUORL MWOPLP MMPMAT

MMPOPE MMPOPS

MPDSRC MPDMAT

MPDOPE MPDOPS

MPDWCT

ACUORL MCO line

In the case of an MCO, a work order proposal is created from a customer order line.

55
CFACIL Facility
Contains basic data such as main warehouse per facility which is defaulted to the work order
header.

MITFAC Item – facility

Contains dynamic lead times and costing types used with manufacturing work order.

MITBAL Item – warehouse

Contains lead times for material acquisitions.

MMOHED Work order

Contains the work order header.

MMOMAT Work order material

Contains the materials connected to a work order. When a work order is released, the
materials connected to the selected service in MMPMAT are transferred to MMOMAT.

MMOOPE Work order operation

Contains the operation connected to a work order. When a work order is released, the
operations connected to the selected service in MMPOPE are transferred to MMOOPE.

MMOOPS Routing operation activity description

Contains operation elements, that is requirements per operation such as certain tools or
skills.

MMORDN Work order type no series

Contains order type exceptions per facility.

MMORDT Work order type

Contains the work order type definition.

MMPMAT Work order - line

Contains the materials connected to a work order. When a work order proposal is created, the
materials connected to the selected service in MPDMAT are transferred to MMPMAT.

MMPOPE Work request operations

Contains the operation connected to a work order. When a work order proposal is created,
the operations connected to the selected service in MPDOPE are transferred to MMPOPE.

MMPOPS Work request operations elements

Contains operation elements, that is requirements per operation such as certain tools or
skills.

MPDMAT Connect materials-operations

Contains the materials connected to a service.

MPDOPE Operations
Contains the operations connected to a service.

56
MPDOPS Routing operation activity description
Contains operation elements, that is requirements per operation such as certain tools or
skills.

MPDSRC Service definition

Contains the definition of a service to be used in a work order.

MPDWCT Planning groups (work centers)

Contains work center information, that is where to perform the operation. A work center is
always connected to a facility.

MWOPLA Service history

Contains released work order proposals from MWOPLP that may be used to calculate next
scheduled work order.

MWOPLP Work requests

Contains work order proposals that may either be generated by schedule or created from an
MCO. Proposals may be released and are then transferred to MMOHED, and simultaneously
a history post is created in MWOPLA to calculate next scheduled service.

57
Copyright © 2014 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or
registered trademarks of Infor and/or related affiliates and subsidiaries. All other trademarks listed herein are the
property of their respective owners. www.infor.com.

58