Actual Migration
The entire migration process is logged in the following:
03 Monday Sep 2012
Posted Baan Infor Installation
inActual Migration
The entire migration process is logged in the following:
03 Monday Sep 2012
Posted Baan Infor Installation
inActual Migration
The entire migration process is logged in the following:
03 Monday Sep 2012
Posted Baan Infor Installation
inIntroduction
To support all languages available for Infor ERP LN in a single environment,
you must install ERP LN in Unicode mode. Unicode is the standard for
Multilanguage support and provides a unique code for each character,
regardless of language.
Prerequisites
30 Thursday Aug 2012
Posted Baan Infor Installation
inRecalculate freight costs
If value Automatic is selected for field Recalculation of Freight Costs, and an advanced status is
selected for field Recalculate Load Costs until Status in the Freight Rates and Costs Parameters
(fmfrc0100m000) session, freight costs are automatically recalculated for loads, clusters, and shipments
each time the loads, clusters, and shipments are manually changed until processing the loads, clusters,
and shipments has progressed beyond the specified status. Frequent changes to the loads, clusters,
and shipments result in numerous freight cost recalculations, which can affect system performance.
To save performance, consider recalculating the freight costs only once, after all changes have been
made to the loads and shipments, or only allowing automatic recalculation during the early stages of
the planning and shipping process. For this purpose, for field:
▪ Recalculation of Freight Costs, select one of the following values: ▪ Interactive ▪ No
▪ Recalculate Load Costs until Status, select an early status.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Update actual load data
If value Automatic Replanning is selected for field Update Actual Load Data in the Freight Planning
Parameters (fmlbd0100m000) session, actual load plans are automatically replanned each time particular
changes are made to the freight orders on which the load plan is based. Changes made to the originating
orders of freight orders also affect the freight orders. Frequent changes can result in frequent replanning,
which can affect system performance.
8
Chapter 8
Freight
To save performance, consider replanning the freight orders only once, after all changes have been
made. For this purpose, select one of the following values for field Update Actual Load Data:
▪ Manual Replanning ▪ Not Allowed
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Trace load plan changes
To keep track of the changes made to load plans and related data, use the Trace Load Plan Changes
field in the Freight Planning Parameters (fmlbd0100m000) session.
To save system performance, consider selecting value No for this field, unless you have a valid reason
to track load plan change data.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
History data
To enable the creation of history records for freight orders and freight order clusters, use the Freight
Invoicing Parameters (fmfri0100m000) session.
To enable the creation of history records for freight invoices, use the Freight Order Control Parameters
(fmfoc0100m000) session.
In the Log Planning History field of the Freight Planning Parameters (fmlbd0100m000) session, you
can enable the creation of history records for:
▪ Load plans ▪ Loads ▪ Shipments
History data is only used to keep track of the life cycle of an object. Enabling the creation of history data
should be carefully considered, taking into account the effect of data growth. Note that every change in
the order results in an additional history record. If history data is used, you must regularly delete, archive,
or delete and archive the history data.
Note that If you delete an object while history data creation is enabled, Infor ERP LN creates a history
record for the deleted object. This history record only includes the last transaction of the deleted object.
8-2 | Freight
You can access the archiving sessions from the appropriate menu of the history sessions. For further
information on deleting and archiving, see Delete and archive (p. 8-3) .
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Delete and archive
To save disk space and system performance, regularly delete or archive, or delete and archive actual
warehousing order data, inventory transaction data, and history data (p. 8-2) .
Delete and archive history data
You can delete and/or archive history data for the following objects:
▪ Freight orders ▪ Freight order clusters ▪ Load plan data ▪ Shipment data ▪ Standard route dates and times
You can access the archiving sessions from the appropriate menu of the history sessions.
For more information, refer to the User’s Guide for ERP LN Archiving (U9352* US).
Delete live data
In addition to history data, you can also delete live records for the following objects:
▪ Freight orders ▪ Freight order clusters ▪ Load plans ▪ Load plan tracking data ▪ Planning log data
To access the deletion sessions, use the appropriate menu on the sessions of these objects.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Freight | 8-3
Disable unused concepts in Freight Management
To save system performance, disable the concepts you do not use. If invoice matching and approval is
not applicable for a particular carrier, clear the Carrier/LSP Invoice check box in the Carriers/LSP by
Shipping Office and Planning Group (fmfrc0160m000) session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
30 Thursday Aug 2012
Posted Baan Infor Installation
inWarehousing
Using lots and serials
Generally, the use of lot items and serialized items usually increases the number of records in your
database and affects system performance, the more so if you use low volume serialized items or low
volume lot items. If low volume lots, low volume serials, or both, are implemented, all warehousing and
related financial transactions are performed for individual lots or serial numbers, which results in
considerable data growth.
To save system performance and avoid unnecessary data growth, only use these concepts if they are
vital to your business processes.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Outbound methods
The outbound method specifies which items will be issued first. You can specify the outbound method
in the Outbound Method field of the following sessions:
▪ Item – Warehousing (whwmd4100s000) ▪ Item – Warehousing Defaults (whwmd4101s000)
The outbound method has the following options:
▪ LIFO ▪ FIFO ▪ By Location
Comparing FIFO and LIFO to the By Location method, using FIFO or LIFO can result in a considerably
larger number of records than By Location. This is because for FIFO or LIFO, receipts are stored by
inventory date in the stockpoint inventory. The stock point inventory is displayed in the Stock Point
Inventory (whinr1540m000) session.
For example, five receipts on different dates for a particular item in a particular warehouse are registered
as five separate entries with different inventory dates in the Stock Point Inventory (whinr1540m000)
session. Using By Location, the same receipts would result in a single entry, provided that the items are
stored in the same location.
To avoid unnecessary data increase, which can impact system performance, you are recommended to
use By Location instead of FIFO or LIFO, unless there is a valid reason to use the latter two. Using the
FIFO or LIFO inventory valuation methods has no relation to the outbound methods used. For example,
you can use inventory valuation method LIFO or FIFO with outbound method By Location.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Remove order line activities of closed orders
If you do not want to remove warehousing orders with status Closed, but want to avoid unnecessary
data growth, remove the order line activities defined for the closed warehousing orders. To remove order
line activities for closed warehousing orders, in the Remove Warehousing Orders (whinh2250m000)
session, select the Line Activities of Closed Orders check box.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
SIC and TPOP order horizons
If you use the SIC and TPOP stock replenishment planning methods, do not extend the order horizons
further than required for your immediate planning purposes.
In the Inventory Analysis Parameters (whina0100m000) session, TPOP and SIC order horizon data are
set in the following fields:
▪ Factor ▪ Constant
In the Factor and Constant fields of the Generate Orders (TPOP) (whinh2201m000) session and the
Generate Order Advice (SIC) (whina3200m000) session, you can overwrite the TPOP and SIC order
horizon data set in the Inventory Analysis Parameters (whina0100m000) session.
Performance aspects
▪ Effect on CPU: Yes
7-2 | Warehousing
▪ Effect on database growth: Yes
Assign item surcharges for item transfer
To specify if and how items transferred between warehouses must be surcharged, use the Assign Item
Surcharges for Item Transfer field of the Inventory Handling Parameters (whinh0100m000) session.
Using item surcharges results in additional postings, and therefore data increase, which can affect
system performance.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Calculate surcharges
If the Calculate Surcharges on Purchase Price of Lot Item check box of the Lot Control Parameters
(whltc0100s000) session is selected, cost price surcharges are added to the net purchase price of the
order line to calculate the lot price.
Selecting this check box is only relevant in case of valuation against lot price. To avoid unnecessary
data increase, which can affect system performance, do not select this check box if the cost price
surcharges, which are recorded on item group level, do not apply to lot items.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Engineering revisions in lot control
If the Engineering Revisions in Lot Control check box of the Lot Control Parameters (whltc0100s000)
session is selected, for a lot, you can record the revision of the item for which inbound or outbound
movements are performed. In this way, you can trace revisions from purchase through to sales, and
service through production.
Creating revision tracking data results in data increase. To avoid unnecessary data increase, only select
this check box if tracking revisions is required.
Warehousing | 7-3
Performance aspects
▪ Effect on CPU: No ▪ Effect on database growth: Yes
Number of staging locations
If the daily number of shipment lines is large compared to the number of available staging locations,
locking problems can occur.
By default, one staging location is in use for a warehouse. To avoid locking problems and therefore
performance reduction, you must define more staging locations. To do so:
1. In the Warehouse – Locations (whwmd3500m000) session, add multiple locations of type
Staging to the required warehouses.
2. In the Warehouse – Dock Locations (whwmd2120m000) session, define multiple dock locations
for the warehouses.
3. To define the dock locations, select the staging locations defined in the previous step.
4. Assign the dock locations to items, business partners, or both, preferably the business partners
for whom the largest volumes of outbound shipment lines are created.
As a result, the dock locations assigned to the items or business partners are used during the outbound
process.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
History data
In the Inventory Handling Parameters (whinh0100m000) session, you can enable the creation of history
records for the following objects:
▪ Warehouse orders
▪ ASN
▪ Receipts
▪ Shipments
▪ Inventory Ownership Change Orders
▪ Allocation Change Orders
▪ Adjustment orders
▪ Cycle counting orders
7-4 | Warehousing
In the Inventory Reporting Parameters (whinr0500m000) details session, you can specify that history
records are created for the following objects:
▪ Inventory transactions ▪ Item issue history ▪ Item issue by warehouse history
Note
In the Inventory Reporting Parameters (whinr0100s000) session, select either the Item – Issue by Period
field or the Warehouse – Item – Issue by Period field. If you select both fields, each issue will be logged
twice. This affects system performance and results in data growth.
History data is only used to keep track of the life cycle of an object. Enabling the creation of history data
should be carefully considered taking into account the impact of data growth. Note that every change
in the order results in an additional history record. If history data is used, you must delete, archive, or
delete and archive, the history data on a regular basis.
Note that If you delete an object while history data creation is enabled, Infor ERP LN creates a history
record for the deleted object. This history record includes only the last transaction of the deleted object.
From the appropriate menu of the history sessions, you can access the archiving sessions. For further
information on deleting and archiving, see Delete and archive (p. 7-5) .
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Delete and archive
To save disk space and system performance, regularly delete or archive, or delete and archive actual
warehousing order data, inventory transaction data, and history data (p. 7-4) .
Delete and archive history data
In the following sessions, you can delete or archive, or delete and archive history data:
▪ Delete/Archive Warehousing Orders (whinh2255m000)
▪ Delete/Archive Shipment Notice History (whinh3251m000)
▪ Delete/Archive Receipt History (whinh3260m000)
▪ Delete/Archive Load/Container/Shipment History (whinh4251m000)
▪ Delete/Archive Cycle Counting Order History (whinh5250m000)
▪ Delete/Archive Adjustment Order History (whinh5270m000)
▪ Delete/Archive Inventory Transactions (whinr1200m000)
▪ Delete/Archive Inventory Transactions by Item and Warehouse (whinr1210m000)
Warehousing | 7-5
▪ Delete/Archive Issues by Period (whinr1220m000)
▪ Delete/Archive Issue by Period and Warehouse (whinr1230m000)
▪ Archive/Delete Packaging Item Transactions (whinr1215m000)
▪ Delete/Archive Handling Unit Version History (whwmd5231m000)
In the following sessions, to keep the last transaction of the objects that you delete, select the Keep
Last Transaction check box:
▪ Delete/Archive Warehousing Orders (whinh2255m000)
▪ Delete/Archive Shipment Notice History (whinh3251m000)
▪ Delete/Archive Receipt History (whinh3260m000)
▪ Delete/Archive Load/Container/Shipment History (whinh4251m000)
This way, the most recent transaction stays in the live company while the older data is deleted or archived.
To access the archiving sessions, use the appropriate menu of the history sessions.
Note
For more information, refer to the User’s Guide for ERP LN Archiving (U9352* US).
Delete live data
In addition to history data, you can also delete live records for the following objects:
▪ Warehousing orders
▪ Handling units
▪ Inbound and outbound advice
▪ Confirmed shipments
▪ Adjustment orders and related data
▪ Cycle counting order and related data
You can access the deletion sessions from the appropriate menu on the sessions of these objects.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Disable unused concepts in Warehousing
To save system performance, you must disable the concepts that you do not use. Clear the following
check boxes to disable the concepts that you do not use:
Warehouse Master Data Parameters (whwmd0500m000) details session
▪ Handling Units in Use
7-6 | Warehousing
▪ Engineering Revisions on Orders Active
▪ The check boxes in the Test Storage Conditions group box
▪ Lot Control in Use
▪ Serialized Items in Use
▪ Extended Packaging Item Registration
Inventory Handling Parameters (whinh0100m000)
▪ Dynamic Cross-docking
▪ Direct Material Supply (DMS)
▪ Export Compliance Provider
▪ Calculate Additional Costs for Shipments
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Calculate totals at runtime for Warehouse Manager Dashboard
If the Calculate Totals at Runtime check box is selected in the User Profiles (whwmd1540m000)
session, on the Warehouse Manager Dashboard (whinh2300m000) session, ERP LN calculates the
values for the fields of the Inbound Open, Outbound Open, Cross-docking, and Resource
Requirements group boxes at runtime.
To save system performance, consider clearing this check box.
If the Calculate Totals at Runtime check box is cleared, ERP LN calculates these totals:
▪ If you select an order, provided that the Show Figures per Order check box is selected.
▪ If you click the Refresh Totals button. This button becomes available if the current check box,
and, on the Warehouse Manager Dashboard (whinh2300m000) session, the Show Figures
per Order check box is cleared.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Automatic receipts
To create automatic receipt records, ERP LN first creates combinations of buy-from business partners,
warehouses, and items based on the ranges or specific selection of business partners, warehouses,
Warehousing | 7-7
dates, and items inserted by the user in the Initiate Automatic Receipts (whinh3223m000) session. Next,
ERP LN reads the receipt settings in the terms and conditions for these combinations.
The generated receipt records include data such as the warehouses in which the receipts are to take
place, the item quantities, and the dates on which the automatic receipts are to take place. When the
automatic receipt date is due, ERP LN performs the automatic receipts.
Creating the combined business partner, warehouse, and item combinations and reading the terms and
conditions may draw heavily on your system’s resources. Therefore, if receipt records were already
created during a previous run of the Initiate Automatic Receipts (whinh3223m000) session, select the
Skip reading of Terms and Conditions check box to prevent ERP LN from creating the receipt records
again before performing the automatic receipts.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Update deliveries
In the course of the delivery process, Warehousing updates a sales order several times.
To carry out these updates directly, in the Update Sales Deliveries field of the Inventory Handling
Parameters (whinh0100m000) session, select Direct.
Select Decoupled to split up the process of confirming a shipment line and updating the originating
sales order into two separate processes and thus save performance. This is because the table behind
the Deliveries (whinh4139m000) session is much smaller than its counterpart of the Shipment Lines
(whinh4131m000) session. Consequently, only a small process table with a limited number of records
is queried instead of the much larger shipment lines table.
To enhance system performance even further, select Batch. This option allows you to carry out these
updates in a batch process in the quiet hours, thus reducing the risk of locking problems.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
30 Thursday Aug 2012
Posted Baan Infor Installation
inProject Control
Standard-to-order items in Project Control
If you generate a PCS project from a sales order in the Generate (Project) Structure for Sales Orders
(tdsls4244m000) session, you must select a method to generate the item structure for items with order
policy To Order:
▪ Standard-to-Order ▪ Engineer-to-Order
If you select Standard-to-Order, ERP LN does not create a customized BOM or a customized routing
at any level in the product structure; this means that you can no longer change the BOM or routing for
a specific project. Note that in the Projects (tipcs2101m000) session, the Engineering Allowed check
box is cleared.
If you select Standard-to-Order instead of Engineer-to-Order, the database growth is limited, which
improves system performance.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Interim results by cost component
To calculate interim Cost of Goods Sold (COGS) and interim revenue for a PCS project, use interim
revenue recognition.
The setting of the Post Interim COGS and Revenues by Cost Component check box in the Project
Control Parameters (tipcs0100m000) session determines how the Post Interim COGS and Revenues
by Cost Component check box in the Project Details (tipcs2130m000) details session is set for PCS
projects generated from a sales order line; it does this by using the Generate (Project) Structure for
Sales Orders (tdsls4244m000) session.
If this check box is selected, the interim COGS is specified by detailed cost components. To view and
maintain the detailed interim COGS, use the COGS by Cost Component (tipcs3191m000) session.
If this check box is cleared, the interim COGS is not specified by detailed cost components; instead, the
interim COGS is posted on the cost component specified in the General Cost Component for Interim
Postings field in the Project Control Parameters (tipcs0100m000) session.
If you clear the Post Interim COGS and Revenues by Cost Component check box, database growth
is decreased, which improves system performance.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
6-4 | Manufacturing
PCF without PCS
The Product Configuration (PCF) module is very flexible and can be used to set up very complex
structures. However, when the structure becomes more complex, system performance gets worse.
You can use PCF without using PCS projects in Manufacturing. The number of transactions in PCS
decreases, which improves system performance. To set up PCF without Project Control (PCS), create
items in the Items – General (tcibd0501m000) session with item type Generic. The item policy of the
items defined in the Items – Ordering (tcibd2500m000) session must be Anonymous.
Product configurator version
The Product Configuration (PCF) module is flexible and can be used to set up very complex structures.
However, when the structure becomes more complex, system performance gets worse.
To specify the product configurator version, use the Product Configuration Parameters (tipcf0100m000)
session. If you select Object Version in the Product Configurator Version field, system performance
improves significantly.
The Object Version is available for the operational situation. During runtime, constraints are directly
carried out by the product configurator as objects, without the need to repeatedly read in and interpret
or compile constraints. Compared to the interpreter version, the object version considerably improves
performance, especially in complex constraints. Prior to using the object version, all constraints must
be compiled in the Compile Constraints by Configurable Item (tipcf2201m000) session. For this purpose,
you need the compiler ‘bic6.2’ of Enterprise Server.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Transaction processing in ASC
In the Assembly Control Parameters (tiasc0100m000) session, you can select in the Transaction
Processing field at which level transactions are processed:
▪ Line Station Based ▪ Order Based
From a performance and database growth perspective, the setting Line Station Based is preferred for
high-volume environments. For each line station, the line-station order data is collected in one daily
clustered line-station order (CLSO). Processing is carried out at an aggregated (line station) level. You
will receive production results for each period when you use line-station-based transaction processing.
Therefore, the number of transactions is significantly reduced, which improves system performance.
Manufacturing | 6-5
Note
You can only set this parameter during implementation.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Shop Floor Control
Financial transactions by work center
In the Shop Floor Control Parameters (tisfc0100s000) session, to determine whether you want to store
financial results in Shop Floor Control by work center or by production order, use the Financial
Transactions by Work Center field:
▪ If the Financial Transactions by Work Center check box is selected, financial results are
stored by work center. Efficiency results are analyzed by work center. Additional postings take
place (more end-item unit cost data), which worsens performance.
▪ If the Financial Transactions by Work Center check box is cleared, financial results are
stored by production order. All financial transactions are posted on the production order
calculation office, which means that no financial transactions for WIP transfers are required.
The results are calculated on calculation office level, which is less detailed than on work center
level. Therefore, clearing the Financial Transactions by Work Center check box improves
performance.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Transfer WIP method
If in the Shop Floor Control Parameters (tisfc0100s000) session, the Financial Transactions by Work
Center check box is selected, use the Transfer WIP method field to specify when the WIP is transferred
from one work center to the next. You can choose between the following options:
▪ Always
The transfer is performed when a quantity is reported as complete. The delivering work center
must be different from the receiving work center,
▪ Only upon Completion
The transfer is performed when the whole operation is reported as completed. The delivering
work center is different from the receiving work center.
6-6 | Manufacturing
If the setting is Always, every time a quantity is reported as completed, financial transactions take place.
If the setting is Only upon Completion, financial transactions only take place once, when the whole
operation is completed. Therefore, the setting Only upon Completion results in less transactions, which
means less database growth and a better performance of the production order completion process.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Posting method for price variances
If the setting of the Posting Method Price Variances to Calculation Office fields in the Shop Floor
Control Parameters (tisfc0100s000) session is Not Applicable, production results are aggregated to an
additional calculation variance. Some details are lost, but the number of transactions is limited.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Posting method for efficiency variances
If the setting of the Posting Method Efficiency Variances on Calculation Office fields in the Shop
Floor Control Parameters (tisfc0100s000) session is Not Applicable, production results are aggregated
to an additional calculation variance. Some details are lost, but the number of transactions is limited.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Actual cost price for receipt posting
The setting of the Use Actual Cost Price for Receipt Posting check box in the Shop Floor Control
Parameters (tisfc0100s000) session and the valuation method can affect system performance and
database growth. You can distinguish the following situations:
▪ Use Actual Cost Price for Receipt Posting check box is selected and valuation method
is not FTP
If the Use Actual Cost Price for Receipt Posting check box is selected, and the inventory
valuation method on item/warehouse level is an actual costing valuation method such as FIFO,
LIFO, MAUC, lot price or serial price, only a limited number of variance postings takes place
because the end items are received in inventory at their actual production order costs. This
means no price variance postings and efficiency postings take place, but additional calculation
office variances can occur, especially if the Financial Transactions by Work Center check
Manufacturing | 6-7
box is selected. The posting methods for variances defined in the Shop Floor Control
Parameters (tisfc0100s000) session are not used.
▪ Use Actual Cost Price for Receipt Posting check box is selected and valuation method
is FTP
If the Use Actual Cost Price for Receipt Posting check box is selected, and the inventory
valuation method on item/warehouse level is FTP, variance posting is done by SFC. ERP LN
processes inventory variances, which you can view in the Inventory Variances
(whina1516m000) session.
▪ Use Actual Cost Price for Receipt Posting check box is cleared and the valuation method
is not FTP
If the Use Actual Cost Price for Receipt Posting check box is cleared, and the inventory
valuation method on item/warehouse level is an actual costing valuation method such as FIFO,
LIFO, MAUC, lot price or serial price, variance posting is done by SFC. ERP LN processes
inventory variances, which you can view in the Inventory Variances (whina1516m000) session.
▪ Use Actual Cost Price for Receipt Posting check box is cleared and valuation method
is FTP
If the Use Actual Cost Price for Receipt Posting check box is cleared, and the inventory
valuation method on item/warehouse level is FTP, production variances are likely to occur
and are logged according to the settings of the variance parameters in the Shop Floor Control
Parameters (tisfc0100s000) session. This results in additional postings.
Relative impact on
database growth
Use Actual Cost Price for Re- Inventory valuation method
ceipt Posting
Selected FIFO, LIFO, MAUC, lot price, serial price Low
Selected FTP Medium
Cleared FIFO, LIFO, MAUC, lot price, serial price High
Cleared FTP High
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Actual operation rates
The Process Hours using field in the Shop Floor Control Parameters (tisfc0100s000) session can have
the following settings:
▪ Actual Man and Machine Rates
The labor and machine costs are booked using the actual operation rates. If the employee’s
operation rate differs from the estimated operation rate, price variance postings occur.
6-8 | Manufacturing
▪ Estimated Operation Rates
The labor and machine costs are booked using the estimated values. The used cost
components are specified in the Operation Rates (ticpr1150m000) session.
If you select Estimated Operation Rates, the number of price variance postings is reduced. However,
if in the Operation Rates (ticpr1150m000) session several cost components are specified for the same
operation cost type ( Labor, Machine, Overhead on Machine Hours, or Overhead on Man Hours ),
additional postings occur.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Printing of documents
To support the production process, you can choose to print several types of documents. Specify the
required documents on the Documents tab in the Shop Floor Control Parameters (tisfc0100s000)
session. However, the printing of these documents, slows down system performance; therefore, only
print documents that are required.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Moment of freezing estimates
To specify the moment that estimates are frozen, use the Moment Freezing Estimates field in the
Default Production Order Data (tisfc0102m000) session. When the estimates are frozen, every change
on the order will result in variance postings, which increases database growth and makes system
performance worse. You can select one of the following values, by number group or by production order
series:
▪ Before First WIP Transaction ▪ During Releasing Order ▪ During Creating Order
To improve performance, postpone estimate freezing as long as possible. Note that if you select Before
First WIP Transaction, the estimates are calculated and stored at the first actual posting; this means
that performance of the first step will not improve.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Manufacturing | 6-9
History, archiving, and deleting in Manufacturing
BOM history in Engineering Data Management
To store a history of production BOM lines, select the PBOM History check box in the Engineering Data
Management Parameters (tiedm0100m000) session. Keeping a history of PBOMs results in additional
data.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
Delete item costing data
Item costing data is part of the cost price data, and is stored by price calculation code. If you carry out
many price simulations, the data in the underlying tables grows. To remove redundant cost price data
by price calculation code, and to empty the tables, use the Delete Cost Price Data (ticpr2260m000)
session.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
Remove item standard costing data
The item standard costing data is part of the cost price data, and contains all standard costs (FTP) by
item, cost component, and warehouse. The data is date effective, and every update of the costs results
in new data.
The underlying tables contain the actual cost prices and the cost price history. Therefore, the underlying
tables can grow significantly. Usually, the data is stored for a while, but when the data is no longer
required, use the Remove Cost Price History Data (ticpr2230m000) session to remove the data.
To remove cost price data while actualizing cost prices, select the Delete Cost Price History Data
check box in the Actualize Standard Cost and Valuation Prices (ticpr2220m000) session.
Old cost price data is removed, and takes into account the number of years defined in the Retain
Standard Cost Price History field in the Cost Price Calculation Parameters (ticpr0100m000) session.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
6-10 | Manufacturing
Archive and delete in Shop Floor Control
In Shop Floor Control, you can distinguish between the following data:
▪ Production orders ▪ Financial transaction data ▪ Costing data
If you create production orders, financial transaction data and costing data are automatically created.
You cannot have a history of financial transaction data; instead, use the costing data, which is a subset
of the financial transaction data.
▪ Archive or delete production orders
To archive or delete closed production orders, use the Archive Production Orders
(ticst0250m000) session.
▪ Delete financial transaction data of production orders
To delete the financial data of a reconciled production order, use the Delete Production Order
Transactions (ticst3200m000) session.
▪ Archive costing history
To archive and delete costing history data, use the Archive Costing History (ticst2250m000)
session.
To remove production orders, use the Cancel Range of Production Orders (tisfc0202m000) session.
Note
For more information, refer to the User’s Guide for ERP LN Archiving (U9352* US).
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
Delete in Assembly Control
In Assembly Control no archiving functionality is available; however, you can delete the following data:
▪ Assembly orders
To delete assembly orders and financial data for closed and reconciled orders, use the Purge
State-dependent ASC Data (tiasl1200m000) session.
▪ Product variants
To delete product variants, use the Purge Product Variants (tiapl3200m000) session.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
Manufacturing | 6-11
Delete and archive in Project Control
With respect to Project Control within Manufacturing, the following is of importance.
▪ Delete financial data in Project Control
If a PCS project is closed, you can use the Delete Financial Transactions by Project
(tipcs3200m000) session to remove financial data. After removal of the financial data, you
cannot print WIP and costs anymore. The PCS project is definitively closed and cannot be
reopened. Note that after the data is deleted, you cannot use the Archive Project
(tipcs2260m000) session anymore to archive the data.
▪ Archive projects
Use the Archive Project (tipcs2260m000) session to archive or delete closed PCS projects.
This includes the financial data, so running this session makes using the Delete Financial
Transactions by Project (tipcs3200m000) session superfluous.
Note
For more information, refer to the User’s Guide for ERP LN Archiving (U9352* US).
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
30 Thursday Aug 2012
Posted Baan Infor Installation
inBOM master data
Number of BOM levels
If you set up a BOM, limit the number of BOM levels. More BOM levels means more complexity, which
makes performance worse and increases data growth.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Floor stock
To reduce the number of transactions, you can define BOM material as floor stock; this decreases data
growth and has a positive effect on performance.
To define a specific material as floor stock, select the Floor Stock check box in the Items – Warehousing
(whwmd4500m000) session for that material. Floor stock items are delivered to the shop floor using
Kanban, which reduces the number of transactions. To add the costs of floor stock, use surcharges.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Phantoms
Limit the use of phantoms. If you add phantoms to the BOM, creating and managing production orders
takes additional time.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Routing master data
Material for multiple operations
If the same material is used in several sequential operations, it is recommended to issue the material
at the start of the production order. Therefore, in the Bill of Material (tibom1110m000) session, enter 0
(zero) in the BOM line’s Operation field. To improve performance, do not define a material-routing
relationship in the BOM Line – Material-Routing Relationships (tibom0140m000) session.
To issue the material required for a phantom at the start of the production order, in the Items – Production
(tiipd0101m000) session, set the Issue Unlinked Materials At field to First Operation of Production
Order.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Micro routing
A routing can consist of several operations. From a performance and data growth perspective, every
additional operation requires additional planning effort.
If you do not need operations for planning reasons, but only want to provide information about operations
to the people on the work floor, use a microrouting. Micro routings can provide stepwise information
without the need to create additional operations.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Production order without operations
For production orders, it is not always required to set up operations. Production orders without operations
result in faster planning.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
6-2 | Manufacturing
Backflushing
Backflushing method
If, in the Shop Floor Control Parameters (tisfc0100s000) session, the Backflushing Method field is
Automatic, material is automatically backflushed every time quantities or orders are reported as completed.
Automatic backflushing slows down the performance of the completion process.
To carry out the backflushing process in a batch job during quiet hours, set the Backflushing Method
field to Manual, .
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Backflushing without warehouse orders
If the Backflushing without Warehouse Orders check box in the Shop Floor Control Parameters
(tisfc0100s000) session is selected, no warehouse orders are created during the backflushing process;
this improves the performance of the backflushing process and the production order releasing process,
and database growth in Warehousing is decreased.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Backflushing in jobs
If the Backflushing Method field in the Shop Floor Control Parameters (tisfc0100s000) session is
Automatic, backflushing is performed every time a quantity is reported as complete. If you select
Interactive, you can choose whether to perform backflushing after a quantity is completed.
If the Backflushing Method field is Manual, to backflush material use the Backflush Materials and
Hours (tisfc0220m000) session . If you select the Completed Operations Only check box, backflushing
is only performed after an operation is completed, instead of after every completed quantity. If you create
a job, you can perform backflushing during the off hours.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Manufacturing | 6-
30 Thursday Aug 2012
Posted Baan Infor Installation
inStart of fixed lead-time horizon
To define a plan item’s fixed lead-time horizon, use the Start of Fixed Lead-Time Horizon (SFC) field
in the Items – Planning (cprpd1100m000) session. The Start of Fixed Lead-Time Horizon (SFC) field
is used only for planned production orders.
The fixed lead-time horizon is the time period for which Enterprise Planning uses a fixed lead time to
plan orders.
Before the fixed lead-time horizon, Enterprise Planning plans on the basis of routing data. Beyond the
fixed lead-time horizon, Enterprise Planning plans orders by using a fixed lead time.
The fixed lead-time horizon applies especially to manufactured items. Beyond the fixed lead-time horizon,
the planning run does not calculate or store operations during the planning run. Instead, the planning
run uses the plan item’s fixed lead time to calculate the start and finish date of planned orders. The
orders without operations cannot be transferred to Shop Floor Control module; which means the planned
production orders can be transferred, if the order is within the fixed lead time horizon.
The fixed lead time is taken from the order lead time specified in the Items – Production (tiipd0101m000)
session, which is calculated based on the routing and economic order quantity.
Planning with a fixed lead time is faster than planning on the basis of routing data, but the results are
less precise.
For the planned purchase orders, you must define the plan item’s fixed lead-time horizon, in the Items
– Purchase Business Partner (tdipu0110m000) session. The lead time is defined in the Lead Time
Horizon (Days) field.
To make a rough and faster calculations for the planned purchase orders, you can define the calculated
lead time in the Calculated Lead Time (Days) field.
With in the lead time horizon, you can also define the following for a planned purchase orders.
▪ Internal Processing Time ▪ Safety Time ▪ Supply Time ▪ Transportation Time (Days)
Recommendation:
▪ Do not make the number of days in the Start of Fixed Lead-Time Horizon (SFC) field too
large.
Performance aspects
▪ Effect on CPU: Yes
5-6 | Enterprise Planning
▪ Effect on database growth: Yes
Order horizon
To define a plan item ‘s order horizon, use the Order Horizon field in the Items – Planning
(cprpd1100m000) session.
The order horizon is the time period for which Enterprise Planning uses order-based planning to plan
supply.
The Generate Order Planning (cprrp1210m000) session, that performs the order-based planning, also
performs the capacity planning for the planned orders. To calculate the capacity utilization, ERP LN
matches the routing lead times against the calendar; this takes a lot of processor time and is performance
sensitive. If the order horizon is very long, the planning run’s performance slows down.
A reasonable minimum value for the order horizon is the cumulative order lead time.
When you set or change the Order Horizon field, you can run the Check Horizons (cprpd1200m000)
session to check and optionally adjust the order horizon. For details, refer to the field Help of the Order
Horizon field.
Recommendations:
▪ Do not make the number of days in the Order Horizon field too large.
▪ To check the value of the Order Horizon field, use the Check Horizons (cprpd1200m000)
session field.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Planning horizon
To define a plan item ‘s planning horizon, use the Planning Horizon field in the Items – Planning
(cprpd1100m000) session.
The planning horizon is the time period for which ERP LN maintains planning data for an item.
If you maintain an item master plan for the plan item, the Generate Master Planning (cprmp1202m000)
session calculates, among other things, the critical capacity requirements to generate the resource
master plans; this calculation takes a considerable amount of system performance. The planning horizon
determines over what period ERP LN must calculate the master plans and, therefore the required
calculation time.
Enterprise Planning | 5-7
When you set or change the Planning Horizon field, you can run the Check Horizons (cprpd1200m000)
session to check and optionally adjust the order horizon. For details, refer to the field Help of the Planning
Horizon field.
Recommendations:
▪ Do not make the number of days in the Planning Horizon field too large.
▪ To check the value of the Order Horizon field, use the Check Horizons (cprpd1200m000)
session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
CTP horizon
To define a plan item ‘s CTP horizon, use the CTP Horizon field in the Items – Planning (cprpd1100m000)
session.
The CTP horizon is the date until which ERP LN performs ATP and CTP checks.
After the ATP/CTP horizon, ERP LN assumes that capacity and components are infinite.
If you make the CTP horizon longer, the system performance of the ATP check decreases.
Recommendation:
▪ Do not make the number of days in the CTP Horizon field too large.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Maintain master plan
If you select the Maintain Master Plan field in the Items – Planning (cprpd1100m000) session, ERP LN
maintains an item master plan and possibly also channel master plans for the plan item.
The maintenance of item master plans and channel master plans requires storing a lot of data.
If many plan items have master plans, the online update of master plans takes considerable system
performance. For each transaction, such as the generation of an order or the issue of goods, ERP LN
must immediately update all fields of the master plan over the entire master-planning horizon. Examples
of these fields are the projected inventory, ATP, and cumulative ATP.
5-8 | Enterprise Planning
If many plan items have master plans, the Initialize, Roll, and Update Scenario (cprpd4200m000) session
takes a lot of system performance to roll or initialize a scenario.
The following situations can be reasons to maintain an item master plan:
▪ You need to create a demand forecast for the plan item.
▪ The production of the item is a bottleneck in the factory.
▪ The item is situated on the customer order decoupling point, that is, the item is produced on
the last large stock point in the production process or logistical process.
For other plan items, you do not need a master plan.
Note
ERP LN can calculate a plan item’s available-to-promise (ATP) quantity or the capable-to-promise
quantity without a master plan. You do not require a master plan for that purpose.
Recommendation:
▪ Unless you really require the functionality, clear the Maintain Master Plan field.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Maintain resource master plan
A resource master plan is a time-phased overview of the capacity use at a certain resource. A resource
in Enterprise Planning represents a work center.
If you initialize a scenario, ERP LN generates a resource master plan for each resource for which the
Maintain Resource Master Plan field in the Resource (cprpd2100m000) session has been selected.
Critical in CTP
During a capacity CTP check, ERP LN must check the cumulative capacity CTP of all resources in the
plan item’s routing for which the Critical in CTP check box was selected.
If ERP LN maintains resource master plans for more resources, it takes more system performance to
initialize a scenario.
Recommendation:
▪ Unless you really require the functionality, clear the Maintain Resource Master Plan field.
Performance aspects
▪ Effect on CPU: Yes
Enterprise Planning | 5-9
▪ Effect on database growth: Yes
Operation storage horizon
To define a resource ‘s operation storage horizon, use the Operations Storage Horizon field in the
Maintain Resource Master Plan session.
A resource’s operation storage horizon is the number of future working days for which ERP LN stores
the operations for planned orders.
For planned orders beyond the operation storage horizon, you cannot analyze the capacity use of
planned orders, and you cannot transfer the planned orders to the execution level.
The operations storage horizon must be at least as long as the longest of the time fences of the plan
items produced at the involved resource.
A larger value of the operation storage horizon increases the data growth.
Recommendation:
▪ Do not make the number of days in the Operations Storage Horizon field too large.
Performance aspects
▪ Effect on CPU: Not applicable ▪ Effect on database growth: Yes
Fixed order quantity
If you use a fixed order quantity for a particular item, every order for that item will have the same order
quantity. If you require a larger quantity, ERP LN generates multiple orders for the same item and the
same due date.
5-10 | Enterprise Planning
Example
Demand 2000
Fixed Order Quantity 100
20 planned orders with quantity
of 100
Result
Example 1: Reasonable values
If you have a high volume demand and you choose a small fixed order quantity, ERP LN generates
many planned orders.
Demand 100000
Fixed Order Quantity 10
10000 planned orders with quantity
of 10
Result
Example 2: Extreme values
To define a fixed order quantity for manufactured items, use the Fixed Order Quantity field in the Items
– Ordering (tcibd2500m000) session.
To define a fixed order quantity for purchased items, use the Fixed Order Quantity field in the Item –
Purchase Business Partner (tdipu0110m000) session.
The Plan Items – Optimized Lot Sizes (cprao3110m000) session calculates the optimal lot sizes.
During the planning process, ERP LN stores the requirements and planned orders for each individual
plan item in memory. If requirements are very large, but the lot sizes are very small, the planning run
requires considerable performance.
Recommendations:
▪ If you use a fixed order quantity, make the fixed order quantity sufficiently large. Take the
expected volume for the item into account.
▪ To calculate the optimal lot sizes, use the Plan Items – Optimized Lot Sizes (cprao3110m000)
session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Enterprise Planning | 5-11
Pegging horizon
In the EP Parameters (cprpd0100m000) session, you can enter a pegging horizon in the Pegging
Horizon field.
The pegging horizon is the number of days into the future for which the order-based planning generates
pegging relations. ERP LN records no pegging relations for transactions with a transaction date beyond
this horizon.
A shorter pegging horizon can give better system performance, but offers less pegging information.
Recommendations:
▪ If you only use the pegging information for part of the order horizon, set the Pegging Horizon
field to that part of the order horizon.
▪ If you do not use pegging information, set the Pegging Horizon field to 0.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Top-down item selection
In the Generate Order Planning (cprrp1210m000) session, if you select the Use Top-Down Item
Selection check box, Enterprise Planning extends the item selection and takes into account the multi-level
structure of the bill of material (BOM), supplying relationships, and the relations between generic items
and the possible product variants.
For the range of plan items you specified in the From Plan Item and To Plan Item fields, or for any item
that ERP LN includes in the selected range because of the bottom-up item selection, ERP LN extends
the item selection with the following:
▪ Components in the bill of material.
▪ Supplying items you specified in the Supplying Relationships (cprpd7130m000) session.
▪ Components in the generic bill of material, for the generic items included in the specified item
range.
▪ Derived-from items; the generic or normal items you use to create project items in the Project
Control (PCS) module of Manufacturing, of any project items included in the specified item
range.
If you perform order planning for a single plan item, the Use Top-Down Item Selection check box offers
a useful option. However, if you perform order planning for all plan items (the full range), the setting of
the Use Top-Down Item Selection check box makes no difference for the end result. In that case,
selecting the Use Top-Down Item Selection check box only slows down the planning run.
5-12 | Enterprise Planning
Recommendation:
▪ If you run the Generate Order Planning (cprrp1210m000) session for all items, clear the Use
Top-Down Item Selection check box.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Number of plan items
To plan the supply of an item based on the anticipated demand for that item, set the item’s order system
to Planned to create a plan item and maintain the relevant data in the Items – Planning (cprpd1100m000)
session.
You can create one plan item for each combination of item code and cluster of warehouses.
The Enterprise Planning package plans the supply for these plan items.
Order systems and methods exist that do not use plan items, such as statistical inventory control (SIC),
time-phased order point (TPOP), Kanban, and order controlled/Single.
You can also make the item available on the shop floor as floor stock.
If the number of plan items increases, performance of the planning process decreases. It is not usually
necessary to create a plan item for every item and every cluster.
Recommendations:
▪ For every item, consider which planning method is most suitable, such as statistical inventory
control (SIC), time-phased order point (TPOP), Kanban, or order controlled/Single.
▪ Only use Enterprise Planning if you need the planning algorithms of that package.
▪ If an item is a material in production and the item is cheap, make the item available as floor
stock.
▪ Do not create a plan item for an item in every cluster. Only create the plan item for the clusters
you really require.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Yes
Enterprise Planning | 5-13
Component CTP bucket
To define the component CTP bucket, use the Component CTP bucket field in the EP Parameters
(cprpd0100m000) session. The component CTP bucket is the level of detail on the time scale for the
component CTP check.
Example
If you set the Component CTP bucket field to 1 day and Enterprise Planning finds you have insufficient
ATP to promise an ordered quantity on the requested order date, Enterprise Planning checks component
availability to determine whether the order can be promised for the next day, and so on.
If you set the Component CTP bucket field to 1 hour and Enterprise Planning finds you have insufficient
ATP to promise an ordered quantity on the requested order date, Enterprise Planning checks component
availability to determine whether the order can be promised one hour later, and so on.
To make all component CTP buckets equal to the plan periods, set the unit field to Plan Period Definition.
A shorter value for this field increases order-promising accuracy, but slows down system performance.
Recommendations:
▪ Carefully consider the required accuracy for the component CTP check.
▪ Do not set the component CTP bucket to one hour, unless you actually do order promising
on hour level.
▪ If order promising on week level is sufficient, set the component CTP bucket to 7 days.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Online ATP update
If the ATP is to be used to support order acceptance, it must be kept up-to-date. To update the ATP,
choose one of the following methods:
▪ Online update, carried out when a planned or actual inventory transaction is recorded.
▪ Offline update, carried out when the item master plan is updated.
To switch the online ATP update on or off for all plan items, use the Online ATP Update in EP check
box in the EP Parameters (cprpd0100m000) session.
If the Online ATP Update in EP check box is selected, to switch the online ATP update on or off for a
particular plan item, use the Online ATP Update check box in the Items – Planning (cprpd1100m000)
session.
5-14 | Enterprise Planning
Note
If you use ATP functionality for an item that has no master plan, no online ATP updates are required;
in this case, the ATP is always computed online.
Online updating of ATP requires additional system performance, especially during sales order entry.
Recommendations:
▪ If you do not use the available-to-promise functionality, clear the Online ATP Update in EP
check box in the EP Parameters (cprpd0100m000) session.
▪ If a plan item has no master plan, do not select the Online ATP Update check box in the
Items – Planning (cprpd1100m000) session for that plan item unless you use the
available-to-promise functionality for that plan item.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
CTP check for sales
If you select the CTP Check for Sales check box in the EP Parameters (cprpd0100m000) session, ERP
LN carries out a capable-to-promise (CTP) check when a sales order for an item is closed.
CTP checks require additional system performance during the sales order entry procedure.
Recommendation:
▪ If you do not require the capable-to-promise (CTP) functionality, clear the CTP Check for
Sales check box in the EP Parameters (cprpd0100m000) session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Online phase-number update
If you select the Online Phase Number Update check box in the EP Parameters (cprpd0100m000)
session, ERP LN immediately updates the phase numbers of items and plan units when a change occurs
in a bill of material (BOM) or bill of critical material (BCM).
To separately update the phase numbers, use the Compute Phase Numbers (cprpd6200m000) session.
Enterprise Planning | 5-15
During a master-based planning run or an order-based planning run, ERP LN checks whether the phase
numbers are correct; if an incorrect phase number is encountered, ERP LN updates the phase numbers
and restarts the planning run, if necessary.
If you select the Online Phase Number Update check box, ERP LN must do more work if you modify
a bill of material (BOM) or bill of critical material (BCM). Therefore, ERP LN needs more time to process
these modifications.
If you do not update the phase numbers online and you have not used the session to compute phase
numbers, a planning run can encounter incorrect phase numbers; this situation delays the planning run.
Master-based planning runs and order-based planning runs can suffer from this situation.
Recommendations:
▪ Clear the Online Phase Number Update check box in the EP Parameters (cprpd0100m000)
session and, if you perform a planning run after modifying a BOM or BCM, run the Compute
Phase Numbers (cprpd6200m000) session first.
▪ If you do not want to run the Compute Phase Numbers (cprpd6200m000) session before every
planning run if a BOM might have been modified, select the Online Phase Number Update
check box in the EP Parameters (cprpd0100m000) session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Online update resource master plan
If you select the Online Update Resource Master Plan check box in the EP Parameters
(cprpd0100m000) session, the system performance for master-based planning runs and order-based
planning runs decreases.
Recommendation:
▪ Clear the Online Update Resource Master Plan check box in the EP Parameters
(cprpd0100m000) session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not appl
30 Thursday Aug 2012
Posted Baan Infor Installation
inParallel processing concept
To improve processing speed, some planning runs can run in parallel on multiple processors (CPUs).
To do this, set these sessions to run in multiple bshells. Each bshell can run on its own CPU.
This section describes the general concept. For information on the setup, refer to To set up parallel
processing for planning (p. 5-2) .
Application of the parallel processing concept
The sessions for which parallel processing is available include these planning sessions:
▪ Generate Order Planning (cprrp1210m000)
▪ Initialize, Roll, and Update Scenario (cprpd4200m000) ▪ Generate Pegging Relations (cprrp0240m000)
▪ Generate Planned Supply based on Forecast (cpvmi1211m000)
Note
The process that transfers planned orders to the execution level can only use one bshell.
Distribution of items across bshells
The order planning process takes the plan item’s phase number into account. The planning of plan items
with phase number 1 cannot start until all plan items with phase number 0 have been planned; otherwise,
some dependent demand might be missing for the second level.
If you use multiple bshells, ERP LN completes the following steps:
1. ERP LN dynamically calculates an optimal workload for the bshell, but the Workload per
Server field in the Performance Parameters (cpcom0100m000) session restricts this number
to a maximum, such as 500 different plan items.
2. ERP LN assigns a batch of plan items with phase number 0 to the first bshell. ERP LN assigns
a second batch of plan items with phase number 0 to the second bshell, and so on; in this
way, all plan items with phase number 0 are distributed across the bshells.
5
Chapter 5
Enterprise Planning
3. To plan the assigned plan items, all available bshells work in parallel.
4. When all plan items with phase number 0 have been planned, ERP LN assigns batches of
plan items with phase number 1 to the bshells, followed by the plan items with phase number
2, and so on.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
To set up parallel processing for planning
To improve processing speed, some planning runs can run in parallel on multiple processors (CPUs).
To do this, set these sessions to run in multiple bshells. Each bshell can run on its own CPU.
This section describes the setup. For general information on the concept, refer to Parallel processing
concept (p. 5-1) .
To set up parallel processing, perform the following steps:
1. Start the Performance Parameters (cpcom0100m000) session.
2. Select an appropriate value for the Workload per Server field.
For more information, refer to Workload per server (p. 5-4) .
3. Select or clear the Workload Based on Operations check box, as appropriate.
For more information, refer to Workload based on operations (p. 5-4) .
4. Select or clear the Dynamic Workload Calculation check box, as appropriate.
For more information, refer to Dynamic workload calculation (p. 5-4) .
5. Select the Parallel Processing check box for the sessions you want to run on multiple bshells.
The first time that you select the Parallel Processing check box for a session, that session
appears in the Parallel Processing Configuration (ttaad7520m000) session.
6. Start the Parallel Processing Configuration (ttaad7520m000) session, and double-click the
session that must run on multiple bshells.
7. In the Servers field, specify the number of bshells, that is, the number of parallel processes,
available for that session.
8. In the Mode field, select the appropriate value.
Note
Each time you start a planning run, you can select the Parallel Processing check box in the planning
sessions. However, you must only set the number of servers in the Parallel Processing Configuration
(ttaad7520m000) session once.
5-2 | Enterprise Planning
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Table boosters
To speed up the planning process, you can load particular tables into memory; this method reduces the
number of times a calculation must fetch information from a permanent storage device.
To speed up the planning run in Enterprise Planning, you can instruct the system to load the particular
tables into memory when the planning is run. To see for which tables a table booster is available, start
the Table Boosters (tcmcs0598m000) session.
Some examples of tables for which table boosters exist are the following:
▪ tcmcs001 (Units). ▪ tcmcs016 (Seasonal Patterns). ▪ tcmcs017 (Seasonal Pattern Factors).
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Display time interval
To specify the amount of time, in seconds, ERP LN waits before it displays new information in the
progress bar of the Generate Order Planning (cprrp1210m000) session, use the Display Time Interval
field in the Performance Parameters (cpcom0100m000) session.
Sessions that process large volumes of data usually display some runtime information, which lets you
monitor the session’s progress. However, if the screen is often refreshed, system performance can be
affected.
It is recommended to set this field to a large value.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Enterprise Planning | 5-3
Workload per server
To define the number of items included in each batch that is distributed across multiple bshells, use the
Workload per Server field in the Performance Parameters (cpcom0100m000) session.
The parallel processing solution dynamically calculates the optimal workload per server. The number
you specify in the Workload per Server field is the upper limit.
Recommendations:
▪ Do not specify a number that is too low.
▪ In general, 500 is a reasonable value for this parameter.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Workload based on operations
To prescribe how ERP LN must estimate the workload of planning a plan item, use the Workload Based
on Operations check box in the Performance Parameters (cpcom0100m000) session.
If this check box is selected, the criterion ERP LN uses for workload distribution across the bshells is
the routing composition of each item. The more operations a routing of an item is composed of, the more
weight it has.
Recommendations:
▪ If the number of operations in item routings varies considerably between items, select this
check box to increase the system performance; otherwise, clear this check box.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Dynamic workload calculation
If the Dynamic Workload Calculation check box in the Performance Parameters (cpcom0100m000)
session is selected, the total workload is equally distributed across the available bshells.
Performance aspects
▪ Effect on CPU: Yes
5-4 | Enterprise Planning
▪ Effect on database growth: Not applicable
Round values
If the Round Values check box in the EP Parameters (cprpd0100m000) session is selected, ERP LN
rounds all quantities in a planning run.
The rounding is based on the unit’s rounding factor.
Generally, you must use rounding to ensure that quantities are whole numbers. For example, to avoid
an order for 2.5 light bulbs, which would make no sense, you set the rounding factor for that item’s
inventory unit to 1.0.
The rounding of quantities can reduce the system performance of a planning run by over 10 %.
Recommendation:
▪ If you are confident that you do not require rounded quantities, for example, if the planning
run is only a simulation, clear the Round Values check box.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Scenario start and finish date
To define the scenario ‘s start date and finish date, use the Scenario Start Date and Scenario Finish
Date fields in the Scenarios (cprpd4100m000) session.
The length of time between a scenario’s start date and finish date affects the system performance if you
roll the scenario. The rolling process recalculates all master-plan data from plan periods to separate
days; then, the rolling process recalculates the data from days to plan periods.
The recalculation process also includes open orders with a start date before the start date of the scenario.
The orders between the start date and the current date form the history of the master plan. To check
what has happened in the previous periods, use this historic data. However, a longer history reduces
the system performance of the planning process.
The goods flow before the scenario’s start date is aggregated to one transaction at the scenario start
date. Before the scenario’s start date, no pegging information is available, because all transactions
before the scenario’s start date are anonymous.
Recommendations:
▪ Do not make the period between the scenario’s start date and finish date too long.
▪ Do not set the scenario’s start date too far before the current date.
Enterprise Planning | 5-5
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
30 Thursday Aug 2012
Posted Baan Infor Installation
inParallel processing concept
To improve processing speed, some planning runs can run in parallel on multiple processors (CPUs).
To do this, set these sessions to run in multiple bshells. Each bshell can run on its own CPU.
This section describes the general concept. For information on the setup, refer to To set up parallel
processing for planning (p. 5-2) .
Application of the parallel processing concept
The sessions for which parallel processing is available include these planning sessions:
▪ Generate Order Planning (cprrp1210m000)
▪ Initialize, Roll, and Update Scenario (cprpd4200m000) ▪ Generate Pegging Relations (cprrp0240m000)
▪ Generate Planned Supply based on Forecast (cpvmi1211m000)
Note
The process that transfers planned orders to the execution level can only use one bshell.
Distribution of items across bshells
The order planning process takes the plan item’s phase number into account. The planning of plan items
with phase number 1 cannot start until all plan items with phase number 0 have been planned; otherwise,
some dependent demand might be missing for the second level.
If you use multiple bshells, ERP LN completes the following steps:
1. ERP LN dynamically calculates an optimal workload for the bshell, but the Workload per
Server field in the Performance Parameters (cpcom0100m000) session restricts this number
to a maximum, such as 500 different plan items.
2. ERP LN assigns a batch of plan items with phase number 0 to the first bshell. ERP LN assigns
a second batch of plan items with phase number 0 to the second bshell, and so on; in this
way, all plan items with phase number 0 are distributed across the bshells.
5
Chapter 5
Enterprise Planning
3. To plan the assigned plan items, all available bshells work in parallel.
4. When all plan items with phase number 0 have been planned, ERP LN assigns batches of
plan items with phase number 1 to the bshells, followed by the plan items with phase number
2, and so on.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
To set up parallel processing for planning
To improve processing speed, some planning runs can run in parallel on multiple processors (CPUs).
To do this, set these sessions to run in multiple bshells. Each bshell can run on its own CPU.
This section describes the setup. For general information on the concept, refer to Parallel processing
concept (p. 5-1) .
To set up parallel processing, perform the following steps:
1. Start the Performance Parameters (cpcom0100m000) session.
2. Select an appropriate value for the Workload per Server field.
For more information, refer to Workload per server (p. 5-4) .
3. Select or clear the Workload Based on Operations check box, as appropriate.
For more information, refer to Workload based on operations (p. 5-4) .
4. Select or clear the Dynamic Workload Calculation check box, as appropriate.
For more information, refer to Dynamic workload calculation (p. 5-4) .
5. Select the Parallel Processing check box for the sessions you want to run on multiple bshells.
The first time that you select the Parallel Processing check box for a session, that session
appears in the Parallel Processing Configuration (ttaad7520m000) session.
6. Start the Parallel Processing Configuration (ttaad7520m000) session, and double-click the
session that must run on multiple bshells.
7. In the Servers field, specify the number of bshells, that is, the number of parallel processes,
available for that session.
8. In the Mode field, select the appropriate value.
Note
Each time you start a planning run, you can select the Parallel Processing check box in the planning
sessions. However, you must only set the number of servers in the Parallel Processing Configuration
(ttaad7520m000) session once.
5-2 | Enterprise Planning
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Table boosters
To speed up the planning process, you can load particular tables into memory; this method reduces the
number of times a calculation must fetch information from a permanent storage device.
To speed up the planning run in Enterprise Planning, you can instruct the system to load the particular
tables into memory when the planning is run. To see for which tables a table booster is available, start
the Table Boosters (tcmcs0598m000) session.
Some examples of tables for which table boosters exist are the following:
▪ tcmcs001 (Units). ▪ tcmcs016 (Seasonal Patterns). ▪ tcmcs017 (Seasonal Pattern Factors).
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Display time interval
To specify the amount of time, in seconds, ERP LN waits before it displays new information in the
progress bar of the Generate Order Planning (cprrp1210m000) session, use the Display Time Interval
field in the Performance Parameters (cpcom0100m000) session.
Sessions that process large volumes of data usually display some runtime information, which lets you
monitor the session’s progress. However, if the screen is often refreshed, system performance can be
affected.
It is recommended to set this field to a large value.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Enterprise Planning | 5-3
Workload per server
To define the number of items included in each batch that is distributed across multiple bshells, use the
Workload per Server field in the Performance Parameters (cpcom0100m000) session.
The parallel processing solution dynamically calculates the optimal workload per server. The number
you specify in the Workload per Server field is the upper limit.
Recommendations:
▪ Do not specify a number that is too low.
▪ In general, 500 is a reasonable value for this parameter.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Workload based on operations
To prescribe how ERP LN must estimate the workload of planning a plan item, use the Workload Based
on Operations check box in the Performance Parameters (cpcom0100m000) session.
If this check box is selected, the criterion ERP LN uses for workload distribution across the bshells is
the routing composition of each item. The more operations a routing of an item is composed of, the more
weight it has.
Recommendations:
▪ If the number of operations in item routings varies considerably between items, select this
check box to increase the system performance; otherwise, clear this check box.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Dynamic workload calculation
If the Dynamic Workload Calculation check box in the Performance Parameters (cpcom0100m000)
session is selected, the total workload is equally distributed across the available bshells.
Performance aspects
▪ Effect on CPU: Yes
5-4 | Enterprise Planning
▪ Effect on database growth: Not applicable
Round values
If the Round Values check box in the EP Parameters (cprpd0100m000) session is selected, ERP LN
rounds all quantities in a planning run.
The rounding is based on the unit’s rounding factor.
Generally, you must use rounding to ensure that quantities are whole numbers. For example, to avoid
an order for 2.5 light bulbs, which would make no sense, you set the rounding factor for that item’s
inventory unit to 1.0.
The rounding of quantities can reduce the system performance of a planning run by over 10 %.
Recommendation:
▪ If you are confident that you do not require rounded quantities, for example, if the planning
run is only a simulation, clear the Round Values check box.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Scenario start and finish date
To define the scenario ‘s start date and finish date, use the Scenario Start Date and Scenario Finish
Date fields in the Scenarios (cprpd4100m000) session.
The length of time between a scenario’s start date and finish date affects the system performance if you
roll the scenario. The rolling process recalculates all master-plan data from plan periods to separate
days; then, the rolling process recalculates the data from days to plan periods.
The recalculation process also includes open orders with a start date before the start date of the scenario.
The orders between the start date and the current date form the history of the master plan. To check
what has happened in the previous periods, use this historic data. However, a longer history reduces
the system performance of the planning process.
The goods flow before the scenario’s start date is aggregated to one transaction at the scenario start
date. Before the scenario’s start date, no pegging information is available, because all transactions
before the scenario’s start date are anonymous.
Recommendations:
▪ Do not make the period between the scenario’s start date and finish date too long.
▪ Do not set the scenario’s start date too far before the current date.
Enterprise Planning | 5-5
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Start of fixed lead-time horizon
To define a plan item’s fixed lead-time horizon, use the Start of Fixed Lead-Time Horizon (SFC) field
in the Items – Planning (cprpd1100m000) session. The Start of Fixed Lead-Time Horizon (SFC) field
is used only for planned production orders.
The fixed lead-time horizon is the time period for which Enterprise Planning uses a fixed lead time to
plan orders.
Before the fixed lead-time horizon, Enterprise Planning plans on the basis of routing data. Beyond the
fixed lead-time horizon, Enterprise Planning plans orders by using a fixed lead time.
The fixed lead-time horizon applies especially to manufactured items. Beyond the fixed lead-time horizon,
the planning run does not calculate or store operations during the planning run. Instead, the planning
run uses the plan item’s fixed lead time to calculate the start and finish date of planned orders. The
orders without operations cannot be transferred to Shop Floor Control module; which means the planned
production orders can be transferred, if the order is within the fixed lead time horizon.
The fixed lead time is taken from the order lead time specified in the Items – Production (tiipd0101m000)
session, which is calculated based on the routing and economic order quantity.
Planning with a fixed lead time is faster than planning on the basis of routing data, but the results are
less precise.
For the planned purchase orders, you must define the plan item’s fixed lead-time horizon, in the Items
– Purchase Business Partner (tdipu0110m000) session. The lead time is defined in the Lead Time
Horizon (Days) field.
To make a rough and faster calculations for the planned purchase orders, you can define the calculated
lead time in the Calculated Lead Time (Days) field.
With in the lead time horizon, you can also define the following for a planned purchase orders.
▪ Internal Processing Time ▪ Safety Time ▪ Supply Time ▪ Transportation Time (Days)
Recommendation:
▪ Do not make the number of days in the Start of Fixed Lead-Time Horizon (SFC) field too
large.
Performance aspects
▪ Effect on CPU: Yes
5-6 | Enterprise Planning
▪ Effect on database growth: Yes
Order horizon
To define a plan item ‘s order horizon, use the Order Horizon field in the Items – Planning
(cprpd1100m000) session.
The order horizon is the time period for which Enterprise Planning uses order-based planning to plan
supply.
The Generate Order Planning (cprrp1210m000) session, that performs the order-based planning, also
performs the capacity planning for the planned orders. To calculate the capacity utilization, ERP LN
matches the routing lead times against the calendar; this takes a lot of processor time and is performance
sensitive. If the order horizon is very long, the planning run’s performance slows down.
A reasonable minimum value for the order horizon is the cumulative order lead time.
When you set or change the Order Horizon field, you can run the Check Horizons (cprpd1200m000)
session to check and optionally adjust the order horizon. For details, refer to the field Help of the Order
Horizon field.
Recommendations:
▪ Do not make the number of days in the Order Horizon field too large.
▪ To check the value of the Order Horizon field, use the Check Horizons (cprpd1200m000)
session field.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable
Planning horizon
To define a plan item ‘s planning horizon, use the Planning Horizon field in the Items – Planning
(cprpd1100m000) session.
The planning horizon is the time period for which ERP LN maintains planning data for an item.
If you maintain an item master plan for the plan item, the Generate Master Planning (cprmp1202m000)
session calculates, among other things, the critical capacity requirements to generate the resource
master plans; this calculation takes a considerable amount of system performance. The planning horizon
determines over what period ERP LN must calculate the master plans and, therefore the required
calculation time.
Enterprise Planning | 5-7
When you set or change the Planning Horizon field, you can run the Check Horizons (cprpd1200m000)
session to check and optionally adjust the order horizon. For details, refer to the field Help of the Planning
Horizon field.
Recommendations:
▪ Do not make the number of days in the Planning Horizon field too large.
▪ To check the value of the Order Horizon field, use the Check Horizons (cprpd1200m000)
session.
Performance aspects
▪ Effect on CPU: Yes ▪ Effect on database growth: Not applicable