| Assembly Order (tiasc2100s000) |  |
| Use this session to view assembly orders and define the orders' priority. Related topics Assembly orders
Fields | Description
Assembly Order | An order to assemble a product on one or more assembly lines.
Assembly Line | The final assembly line on which the order will be manufactured. This line is also called the roll-off line for the order.
Status
Assembly Order Status | THe status can be Planned, Sequenced, In Progress, Completed, or Closed. Related topics Assembly orders
Offsetting Required | If this check box is selected, the line station orders (LSOs) of this assembly order must be offset. Offsetting is the calculation of (new) start times and end times. Offsetting is required as soon as a change in the dates or times of an order occurs, or, in other words, as soon as the actual dates and times no longer match the planned dates and times. You can offset LSOs in the Offset Line Station Orders (tiasl4230m000) session. Note This check box visible only for assembly orders with the Planned status. The Offsetting Required check box for planned orders is selected in the following instances: When LAC generates the assembly order in ASC. When an order is generated, all LSOs of the order receive the same initial value, which is the start time and end time of the assembly order itself. If you mix or manually move planned orders and as a result, these orders receive another offline date/time. If you offset the LSOs of a parent order and as a result, the parent order receives another offline date/time, the check box is selected for the child orders; because the child orders must be synchronized with the parent order. Note that offsetting the LSOs of a parent order does not result in new start times and end times for the LSOs of the child orders. The LSOs of the child orders must be offset themselves too.
Priority | If you are using Priority line rules, orders with a low number in this field are processed first. The priority sequence is as follows: Earliest off-line date. Manually entered priority. Sale status of the order (sold orders have higher priority). Priority orders are used during remixing. When you remix orders, you do not have to explicitly define your priorities, because the priority rules are automatically used. You can also use priority rules in sequencing. If you use priority rules in sequencing, you must explicitly define your priority rules.
Item
Item | The end item of the assembly order.
Item Description | The end item of the assembly order.
Serial Number | The serial number of the end item. The serial number will be attached to the order when the order has been sequenced. Related topics Overview of serialized items
Product Variant
Product Variant | A unique configuration or specification of a generic or standard item. The specification results from the configuration process and includes information such as feature options, company, and assembly line. Example If your item is a bike, you can have three product variants: A red bike produced on assembly line one. A blue bike produced on assembly line two. A red bike produced on assembly line two. In this example, color and line are product variant options.
Sell Multiples of Same Configuration | If this check box is selected, a sales order line with this product variant can have an order quantity greater than one. An assembly order always has order quantity one. More than one assembly order can be needed to fulfill one sales order line. Related topics To sell multiples of product variants for assembly
Reference Date | Configuration and BOM explosion in both LAC and ASC are performed on the basis of the reference date, which is determined by the configuration date. In LAC, which is built on Configurator tools, the configuration date is based on the sales parameter's configuration date. The value for this field can be based on the following dates: Order date. System date. Delivery date. The product variant content, which are the options that make up the product variant, is based on the order date, system date, or delivery date. The product variant that is generated contains a reference date, which is equal to the configuration date, in other words, the order date, system date, or delivery date. The BOM explosion that creates the product structure is based on this reference date. The reference date is also used to check which line stations are valid in ASC.
End Item in Inventory
Standard Item | The standard item that is associated with the generic end item. If a generic item is stored in inventory, you must define two items to represent the same physical item: a generic item that you use in Assembly Control and a standard item that you use in Warehouse Management. Related topics To store finished generic items
Standard Item Warehouse | The warehouse where the end item is stored. Related topics To store finished generic items
Offline Dates
Requested Offline Date | The date when work on the assembly order must be completed.
Planned Offline Date | The date when work on the order must be completed.
Delivery Dates
Requested Delivery Date | The date the customer requested delivery of the product.
Confirmed Delivery Date | The date that the manufacturer has told the customer that the product will be delivered.
Planned Delivery Date | The delivery date according to the latest planning, which is determined by ASC.
Actual Delivery Date | The date the end-item was delivered.
Assembly Start Date
Assembly Start Date | The date when work on the assembly order is planned to start on the assembly line.
Environment |
Order
Parent Order
Number | If you use a multisite production environment, the order in another site for which this assembly order is producing a sub-assembly. The parent order is for the main line, and the child order (in the current session) for the supplying line. A supplying line can also have a supplying line, which makes the previous picture more complex, although the principle is the same.
Site | If you use multisite production environment, the parent order site is the site from which this assembly order is derived.
Demand Order
Type | The type of order from which the assembly order is derived. The assembly order can be derived from a sales order, in which case this field reads Sales Order. The order can also be derived from a pseudo order, in which case this field reads Pseudo Order. Note If the Sell Multiples of Same Configuration check box is selected, this field is left empty.
Demand Order | The sales order that gave rise to the current assembly order. Note If the Sell Multiples of Same Configuration check box is selected, this field is left empty.
Position | The position of the demand order (sales order). A sales order can have multiple order lines, which are identified by their position. A product variant, and, therefore, an assembly order, can be generated for each position. Note If the Sell Multiples of Same Configuration check box is selected, this field is left empty.
Costing Data
Calculation Office | An administrative work center that is defined for costing purposes. After assembly lines are closed, the WIP is transferred to the calculation office, where it is posted against the estimated cost price. After the assembly order is closed, the value of the WIP is equal to the option-based cost price. The calculation office appears on the sales order, because the sales department delivers from the calculation office instead of from a warehouse.
Commands | Description
Warehouse Orders | Starts the Warehousing Order (whinh2100m100) session.
Warehouse Order - Status Overview | Start the Inbound Line Status Overview (whinh2119m000) session.