MTO Types - Intergraph Smart Materials - Version 2020 (10.0) - Help - Hexagon PPM

Intergraph Smart Materials Classic Help (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
2020 (10.0)

The MTO type describes all characteristics of an MTO:

  • Criteria for the material selection

  • Structure of the resulting engineering requisitions

Requisitions are generated by an MTO job based on an MTO type and preconfigured rules to meet the project requirements. An MTO type is ideally defined for all material within a project discipline, but depending on the project requirements, other MTO type definitions might be more advantageous.

The MTO types are defined on the R.10.51 MTO Types screen.

To define a new MTO type, enter the name in the Type field and the descriptions in the Short Desc and Description fields.

You can specify different MTO logic using the MTO Option drop-down box.

The available MTO options are listed below.

MTO Option

Meaning

Standard

Used for bulk material

Template Structure

Used for equipment

Balance

Balance requisitions

Standard

If the MTO Option field is set to 'Standard', the MTO type is defined using the standard logic.

With this option, the Type, Bom Set, Req Node, and Req Split fields are mandatory and must be filled.

The Req Rule, Req Desc Rule, Doc Type Set, and Email Templ Set fields are disabled such that you cannot enter data.

The Ident (check box), Tag Option, Mto Crit (check box), Serial Execution Group, Dispo Rule Set, Non Ident Group-by, Line item order, Parent Type, Exclude Idents, and MTO Job Type fields are optional.

Template Structure

If the MTO Option field is set to ‘Template Structure', the MTO type is defined using the Requisition Template logic (pre-processor of the MTO job).

With this option, the Type, Bom Set, Req Rule, and Req Desc Rule fields are mandatory and must be filled.

The Ident (check box), Tag Option, Req Split, Non Ident Group-by, and Parent Type fields are disabled such that you cannot enter data. A req split cannot be entered, because the MTO job creates the req split set automatically with all details. The req split set name is created from the MTO type name.

The MTO Crit (check box), Serial Execution Group, Req Node, Dispo Rule Set, Doc Type Set, Email Templ Set, Line item order, Exclude Idents, and MTO Job Type fields are optional.

The Requisition Template Structure block is displayed beneath the MTO Types block.

In this block, you must define at least one requisition template structure and one split criterion. This information is used to build the requisition split set details (R.10.42) and the requisition templates (R.10.41).

For example:

The name of the MTO type is 'EQT-TEST'. The BOM Setup has only one List Node attached, having five positions with two list position attribute (MAT_GRP, UNIT) values.

Pos

MAT_GRP

UNIT

1

4800

X870

2

4801

X870

3

4801

X870

4

4801

X530

5

Null

Null

You want to create the requisitions separated by the MAT_GRP and split by the UNIT. You must define two rows in the Requisition Template Structure block as shown below.

Seq

Attribute

Type

1

MAT_GRP

Requisition Template

1

UNIT

Split Criteria

Before the MTO job is started, the requisition template logic is applied.

  1. The job creates as many where conditions as different values for the attributes exist.

    Where Condition

    MAT_GRP

    UNIT

    EQT-TEST_1

    4800

    X870

    EQT-TEST_2

    4801

    X870

    EQT-TEST_3

    4801

    X530

    EQT-TEST_4

    Null

    Null

  2. The job creates the requisition node EQT-TEST, which is the name of the MTO type.

  3. The job creates the necessary requisition templates:

    Name (Code)

    Description

    Exe Seq

    Where Condition

    4800 Create by MTO Job

    EQT-TEST 02-OCT-02

    1

    EQT-TEST_T_1

    4801 Create by MTO Job

    EQT-TEST 02-OCT-02

    2

    EQT-TEST_T_2

    NULLVALUE Create by MTO Job

    EQT-TEST 02-OCT-02

    3

    EQT-TEST_T_3

  4. The requisition split set 'EQT-TEST' is built, with the requisition set details displayed below.

    Detail Code

    Exe Seq

    Where Condition

    X530

    1

    EQT-TEST_S_1

    X870

    2

    EQT-TEST_S_2

    NULLVALUE

    3

    EQT-TEST_S_3

  5. Based on this information, the regular MTO job is performed. The requisition rule is defined as #MTO_TYPE#/#REQ_TEMPLATE#/#REQ_SPLIT_DETAIL#. These requisitions are created by the job:

    EQT-TEST/4800/X870 - includes position 1

    EQT-TEST/4801/X530 - includes position 4

    EQT-TEST/4801/X870 - includes position 2 and 3

    EQT-TEST/NULLVALUE/NULLVALUE - includes position 5

Balance

If the MTO Option field is set to 'Balance', the MTO type is defined using the Balance Requisition logic.

With this option, the Type, Req Rule, and Req Desc Rule fields are mandatory and must be filled.

The Ident (check box), Tag Option, MTO Crit (check box), Serial Execution Group, BOM Set, Req Node, Req Split, Dispo Rule Set, Parent Type, Exclude Idents, and MTO Job Type fields are disabled such that you cannot enter data. The req split cannot be entered, because the MTO job creates the req split set automatically with all details. The req split set name is created from the MTO type name.

The Doc Type Set, Email Templ Set, Line item order, and Non Ident Group by fields are optional.

The Child MTO for Balance Requisitions block is displayed beneath the MTO Types block.

Use the LOV in the Child Type field to assign child MTOs to the balance MTO type.

A child MTO type can only be assigned once to a balance MTO type.

With the Ident indicator, you define whether the MTO is an IDENT-MTO (indicator selected) or a NON-IDENT-MTO (indicator not selected). IDENT-MTO means the MTO calculates the material requirements, whereas NON-IDENT-MTO calculates only attributes of the BOM positions like insulation material or erection service work.

The Tag Option indicator shows whether the resulting MTO job must include the tag numbers from the BOM positions.

If the Tag Option indicator is set to Yes, the MTO job includes the tag number in the GROUP-BY condition. This results in engineering requisitions with separate sub-positions for each different tag number.

If the Tag Option indicator is set to Aggregate SWT, the MTO job includes the tag number in the GROUP-BY condition, but SWT is grouped by ident with tag number '---'. The Aggregate SWT tag option allows you to handle in one MTO both regular tags (TWM, TOM...) and standard with tag (SWT). The tag numbers from SWT are ignored (tag number on requisition line item is '---'), and the quantities are summarized by ident and unit. For TWM, TOM..., the tag number appears in the requisition.

If the Tag Option indicator is set to No, the tag number on the BOM position is ignored, and different BOM positions with different tag numbers result in ONE line item on the engineering requisition with the summarized quantity.

  • If the Tag Option indicator is set to No, the tag number of the related BOM positions is not available on the line items of the engineering requisition because it is not possible to store more than one tag number on one line item.

  • The Tag Option indicator is ignored for NON-IDENT-MTOs because it does not make sense to separate different tag numbers on different requisition line items for NON-IDENT-MTOs.

With the MTO Crit indicator, you can control from which level the sum attributes and the group-by criteria are taken. If this indicator is selected, the sum attributes and the group-by criteria defined at the MTO type level are taken in the MTO job. If sum attributes and/or group-by criteria are not defined at this level, no attributes and no group-by criteria are taken into account by the MTO job. If the MTO Crit indicator is not selected, the sum attributes and the group-by criteria at the requisition template level are used in the MTO job. If the MTO job cannot find a definition of sum attributes or group-by criteria at the requisition template level, no sum attributes and/ or no group-by criteria used in the MTO job.

If you select the Only Leaf Pos check box, the corresponding MTO job only considers the BOM leaf positions. If you clear this check box, the MTO job considers all BOM positions and their sub positions. The MTO job creates RLIs (requisition line items) for all BOM positions and not just the leaf BOM positions.

The Serial Execution Group field defines to which serial execution group MTO job incarnations of this type belong. Jobs of the same group are not executed in parallel but instead are serialized by the system.

Select a predefined BOM set from the LOV in the BOM Set field. For more information, see BOM Sets. With the BOM set, you define which BOM nodes and thus associated positions are included in the MTO job.

Open the LOV in the Req Node field to open the R.10.41 LOV, displaying the predefined requisition nodes. For more information, see Requisition Nodes. With the requisition node, you define which requisitions should be created and populated with material by the MTO job.

Double-click a node to expand it to view the sub-nodes. Select a node and click the OK button to close the LOV and to assign this node to the MTO type. Click the Cancel button to close the LOV without inserting a node.

Select a predefined req split set from the LOV in the Req Split field. For more information, see Requisition Split Sets. With the req split set, you define how the MTO job should automatically split requisitions based on position attribute values.

Select a predefined disposition rule set from the LOV in the Dispo Rule Set field. For more information, see Disposition Rule Sets. With disposition rules, you define the contingencies to be included in the requisition.

For equipment templates, select a predefined requisition rule from the LOV in the REQ Rule field. For more information, see Requisition Number Rules. With req rules, you define the way in which a requisition name is automatically generated by the MTO job.

For equipment templates, select a predefined requisition description rule from the LOV in the REQ Desc Rule field. For more information, see Requisition Description Rules. With req desc rules, you define the way in which a requisition description is automatically generated by the MTO job.

For equipment templates, select a predefined document type set rule from the LOV in the Doc Type Set field. For more information, see Document Type Sets.

For equipment templates, select a predefined email template set from the LOV in the Email Templ Set field. In the Email Templ Set field, you can assign an email template set, defined on the A.10.53 Email Template Sets screen. For more information about email templates, refer to Email Templates and Email Template Sets.

For standard MTO types, you can select a Non Ident Group By option from the dropdown list to define if the material is grouped by commodity group, part, commodity code, or ident code.

When the Line item order field is filled, the CIP m_pck_req_custom.order_req is executed to order the requisition line items. The list of ordering options is definable with project default ZR_RLI_ORD.

The Parent Type allows different BOM structures to indicate BOM revision rather than Issue Status. You can assign a parent MTO type here to the selected MTO type (only if the equipment template indicator is set to 'NO').

This parent type provides a new mechanism for organizing MTO/requisitioning work into several distinct stages: If you do not want to use the BOM functionality of having separated BOM position data sets at the same node respectively with differing issue status for different stages of progress, but instead you use different BOM structures for various stages of work progress (meaning, you do NOT want to use the 'Best Quantity' logic throughout the COMPLETE workflow), you can have the system recognize requisitions that have been created in an earlier stage by MTO type A when it creates new requisitions for MTO type B: just assign A as parent type to B.

This has the following effect on the MTO program execution: for new requisitions with supplement number 0, the system will populate the last quantity fields on the requisition line items with values of the quantity fields of matching line items of the highest released supplement of the matching requisition of the parent MTO type.

So basically this feature provides a useful extension to the NORMAL comparison logic, which takes into account the highest released matching requisition supplement of the SAME MTO type. This functionality is still present and will be applied if you do not specify a parent type.

Of course, this new functionality is also subject to the same uniqueness logic that applies if the comparison is done within the same MTO type only: there must not be any unreleased supplements of those requisitions (identified by project reference, origin, requisition set detail, requisition template and Purchase indicator) that the current MTO job is going to create. Otherwise, the error message 'MAR-25080: Open requisitions of the same or parent MTO type exist' will be raised and processing stopped. This has the same reason for the parent type as for the normal type: it ensures that for each requisition, only one supplement is open at the same time.

An important prerequisite for working with this new functionality is that, except for the BOM Set and Dispo Set, all other MTO type data, that is, Req Node (the templates to be used), Req Split (the split details to be used), the Ident and MTO Crit check boxes, the Tag Option, as well as the attached Group By attributes have to be exactly the same as for the parent MTO type. Otherwise, the quantities generated by the new type are not comparable to the requisition quantities generated by the last job of the parent type. Only the BOM Set may be exchanged by another one, pointing to the new BOM structures for the new stage of work.

You can assign a Where condition in the Exclude Idents field, which allows you to exclude idents from the MTO. With the assigned Where condition, you define how the MTO job finds the idents that are not included in the MTO. With the Where condition, a SQL statement is created, which is used by the MTO job to filter the idents to be excluded. For more information^see Where Conditions.

To assign a Where condition, either use the LOV in the Exclude Idents field to select one, or double-click in the field to open the A.60.06 screen, which displays all existing Where conditions for R.10.51. You can either select one of the existing Where conditions or create a new one.

With the MTO Job Type option, you can define for which kind of requisitions the Exclude Idents where condition is considered. The available options are listed below.

  • All - The Exclude Idents condition is considered for all MTO jobs.

  • PO - The Exclude Idents condition is considered only for MTO jobs creating requisitions for purchase orders.

  • Inquiry - The Exclude Idents condition is considered only for MTO jobs creating requisitions for inquiries.

  • None - The Exclude Idents condition is not considered for any type of MTO job.

Use the button to enter additional summary fields. Window 3 opens where you can enter the attributes.

Use the button to enter additional group-by criteria. Window 2 opens where you can enter the attributes.