Generating Assembly Orders

Assembly orders are only created if the following criteria are met:

  • The Assembly Status, which appears in the Product Variants (Assembly) (tiapl3500m000)) session, is Open.
  • The To Be Deleted check box in the details of the Product Variants (Assembly) (tiapl3500m000) session, is cleared.
  • The Planned Offline Date in the Product Variants (Assembly) (tiapl3500m000)) session, falls in the assembly order time fence of the roll-off line. The assembly order time fence is defined per assembly line, in the details of the Assembly Lines (tiasl1530m000) session.
  • The Assembly Line Structure Status of the roll-off assembly line, which is displayed in the Assembly Lines (tiasl1530m000) session, is Actualized.

    The item has the following characteristics:

    • The item type is Generic.
    • The item is Serialized
    • The item's item ordering data exists
    • The item ordering system is FAS

If you select the data in the current session by zooming to the related sessions, only those assembly lines, product variants, and generic items, that meet these criteria can be selected. However, the assembly order time fence and planned offline date do not influence the selections you can make.

The creation of assembly orders is a complex process, because many data must be combined. The flow of this process can be outlined as follows:

  1. Based on the selection of the product variants in the current session, the product variant structure are generated. Refer to the online help of the Generate Product Variant Structures (tiapl3210m000) session for a detailed explanation of this process. Note that the product variant structure is only generated if the External Product Variant Structure check box is cleared in the details of the Assembly Planning Parameters (tiapl0500m000) session. If this check box is selected, ERP Enterprise uses the currently present product variant structure.
  2. The assembly line structure is initialized in Assembly Control. The line structure must be determined, because, for each supplying assembly order, the parent assembly order must be known.
  3. The line structure is browsed, starting from the end of the roll-off line to the start of the supplying assembly line. While browsing the line structure, the following data is registered. First, whether generic sub-items are assembled in another company, and second, the assembly parts and operations that are related to an engineering module. The first action is used to determine which assembly orders must be generated. Each company requires his own assembly order. The second action is used to gather information for the creation of line-station variant (LSVs). This information is taken from the flattened assembly parts and operations, and is evaluated based on effective dates and units. The required materials and operations are stored by line station.
  4. The LSVs are determined and/or created in Assembly Control. LSVs store the assembly parts and operations that are required for a specific assembly order by line station. LSVs can be reused, which means that the LSV can also be used for other assembly orders, if these orders require the same assembly parts and operations on the line station concerned. This way, the LSVs reduce unnecessary data and enhance performance.
  5. The assembly orders are created, starting with the roll-off line. For each line station an LSO is created, based on the appropriate LSV.
  6. The Assembly Status, which appears in the Product Variants (Assembly) (tiapl3500m000) session, is set to Planned. If the creation of the assembly orders did not succeed completely, the Assembly Status remains Open, and assembly lines for which no assembly orders were created, are considered the next time the current session runs.

After the assembly orders are created, a completion report is created.

If errors occurred, the Messages button is enabled, click it to display the error messages.

Click Make Job to add the current session to a job to run the session in batch mode.