Type
|
Short name of the production type. It can be changed and this chnage takes effect in all work orders.
|
Description
|
Long description.
|
Overhead order
|
If active, this relates to an overheads order. This flag is transferred to work order. See Overheads.
This can be used to register costs of non-productive work, like machine cleaning, training, etc.
As an assembly, use it to insert a non-storage related item so it is not closed automatically and is independent of all other settings.
See Close work order automatically
|
|
Planned order
|
Planned work orders can not be started, and no material can be posted. They are created for planning purposes only. However, the work order can be scheduled for material and resource capacity planning.
MRP2 (Material requirement planning – Resource requirement):
If the work order has a sales order reference, it is displayed in MRP2 as a sales order. If not, it is displayed as a forecast.
The requirement of the order is taken into account in MRP and APS, login and completion confirmation is blocked. Therefore, both the planned order and blocked switches must be activated!
The Consider planned orders switch in the MRP Wizard also affects the behavior of planned orders.
(BEAS_FTTYP.PLANNINGORDER=1)
|
|
Project order
|
 Project order
The project order can be defined as one work order or one including several work orders. The work order defining the project is displayed as Project order (displayed green in the WO structure).
As an assembly, a non-storage related item should be added. In this case the assembly is never closed automatically, regardless of the settings.
See Close WO items automatically
|
|
Schedule automatically
|
If active (default), the work order is scheduled automatically backwards after it is created without consideration of the capacity (calculates with unlimited resources). Use APS, for capacity planning.
If changes happen in an existing work order (dates, times, quantities, items or sub-structure) the whole work order is rescheduled.
We recommend disabling this option for overhead orders and project orders.
|
Block
|
Work order is blocked after it is created, but can be released. This is the default type for the block flag. If activated is ignored by both APS and the purchase order list.
|
WIP – do not post differences
|
If enabled, accumulated costs on the WIP account are not automatically booked to the difference account. This setting is useful for example for overhead orders.
If continuous inventory maintenance is activated and the option to empty the WIP account is activated in the Setup Wizard, no postings are performed for work orders with this type from the WIP account to the WIP difference account.
For example in overhead work orders transfer of the WIP amount is not desirable, since no assemblies are posted.
Note: For customer-specific adaptation, a command which can be used to transfer the amount independently of this switch. You can use this e.g. to generate a monthly posting.
|
Invisible
|
Work order is treated like a closed work order, but it is active. Only times can be booked on this type of work order.
|
Release not check
|
If you work with item versions, the production of an item version can be blocked in item version – status.
Activate this switch to override the block in item version – status for this production type. When active, it is always possible to create a WO position for an I-Version.
When disabled, it is allowed to create a Work order position only if Release I-Version and Create WO parameters are enabled.
Example of use:
A yet unreleased item version is to be created (Production blocked).
You want to produce a sample, however. For this, a Sample order work order type is be created, in which this flag is activated.
As a result, it is possible to create a work order for a blocked item version.
|
|
This setting is changeable in production order
|
Refers to both the graphical symbol and color switches. If enabled, the graphical symbol and color can be changed in the work order.
|
Graphical symbol
|
This order is displayed in the tree view with the chosen image.
|
Color
|
The order is displayed in the chosen color in the tree view and production list.
|
Always breakdown subassemblies
|
If enabled, the system breaks down all sub-assemblies, whether they are stock- or order-related. This affects only newly created work orders.
See work order item > always breakdown assemblies
|
Valuation of assembly
|
A separate valuation method can be set for a production type.
For example, a repetition part can be valued at standard costs, a repair order at post calculation price etc. It can be set to automatic in Configuration wizard > Production > Valuation and booking of assembly > Valuation. This option affects assembly posting only.
The following selections are available:
Window basis_fttyp_edit.psr
Note: When working with the Merge function, a production type with the "like manual posting" valuation method needs to be created.
|
Pricing at valuation
|
Determines which calculation value from the calculation schema is used for valuation. The option is only visible if Post calculation or Production planned costs was selected from the Valuation Assembly drop-down list.
|
In house production pricing booking
|
Determines which price list is to be used for valuation. Only visible if As Stock Transfer was selected from the Valuation of assembly drop-down list.
|
Automatic material posting
|
Determines how to execute the issue of materials for the production type:
•at first operation
•at last operation
•no automatic
•automatically
By default this is set to automatically. In this case settings in the Configuration Wizard apply. All other options override the settings in the Configuration Wizard.
This option is only available if "work order backflushing" was not selected in the Configuration Wizard.
See Configuration wizard – material posting.
|
Collective receipt –
Manual Price
|
If enabled, the price can be entered manually in Production > collective receipt.
|
Collective post in –
Manual Batches
|
If enabled, in the batch numbers can be manually entered in Production > collective receipt (for example for disassembly processes).
|
