MTO Type Details - Intergraph Smart Materials - 10.1 - Training - Hexagon

Smart Materials Web Tutorials

Language
English
Product
Intergraph Smart Materials
Subproduct
Web
Search by Category
Training
Smart Materials/Smart Reference Data Version
10.1

To define a new MTO type, click New MTO Type button. It will lead to the MTO Type Details page. Enter the name in the MTO 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 as follows:

MTO Option

Meaning

Standard

Used for bulk material

Template Structure

Used for equipment

Balance

Balance requisitions

This tutorial mainly describes how to handle requisitions for bulk material, which means the MTO option is set to Standard. Find further details about the MTO options, as following:

Standard

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

With this option, it is mandatory to specify BOM Set, Requisition Node, and Requisition Split Set in the process of the MTO Type creation.

The Req Rule, Req Desc Rule are not being shown and will be specified in the Requisition Node. You cannot enter data in the Document Type Set, and Email Template Set page as they are disabled for the Standard MTO Option.

The Ident MTO (check box), Tag Option, MTO Criteria (check box), Serial Execution Group, Material Grouped By, Line Item Order, Parent MTO Type, Exclude Idents, and MTO Job Type fields are optional.
The definition of a Disposition Rule Set in the process of the MTO Type creation is optional as well.

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, it is mandatory to specify BOM Set in the process of the MTO Type creation.
Also the Requisition Rule and Requisition Description Rule fields appear and are mandatory and must be filled.

The Ident (check box), Tag Option, Material Grouped By, and Parent Type fields are disabled such that you cannot enter data. You cannot enter data in the Requisition Split page as it is disabled for the Template Structure MTO Option.
A requisition split cannot be entered, because the MTO job creates the requisition split set automatically with all details. The requisition split set name is created from the MTO type name.

The MTO Criteria (check box), Serial Execution Group, Line Item Order, Exclude Idents, and MTO Job Type fields are optional.
The definition of a Requisition Node, Disposition Rule Set, Document Type Set, Email Template Set in the process of the MTO Type creation is optional as well.

After saving an MTO Type with MTO Option ā€˜Template Structureā€™ the Template Details section is added to the MTO Type creation process on the left side.

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 and the requisition templates.

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:

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.

    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, it is mandatory to specify BOM Set in the process of the MTO Type creation.
Also the Requisition Rule and Requisition Description Rule fields appear and are mandatory and must be filled.

The MTO Ident (check box), Tag Option, MTO Criteria (check box), Serial Execution Group, Parent MTO Type, Exclude Idents, and MTO Job Type fields are disabled such that you cannot enter data.
You cannot enter data in the BOM Set, Requisition Node, Disposition Rule Set and Requisition Split page as it is disabled for the Balance MTO Option. 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 Line Item Order, and Material Grouped By fields are optional.
The definition of a Document Type Set and an Email Template Set in the process of the MTO Type creation is optional as well.

After saving an MTO Type with MTO Option ā€˜Balanceā€™ the Child MTO section is added to the MTO Type creation process on the left side.

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

With the Ident MTO 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 Criteria 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 Criteria 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.

For standard MTO types, you can select a Material Grouped 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 MTO Type allows different BOM structures to indicate BOM revision rather than Issue Status. When MTO Option is set to Template Structure or Balance, this cell is disabled. When Standard is selected under MTO Option, it is optional to enter the parent MTO type data.

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. The Where Condition shown in this list must be assigned to Module R1051 MTO Types. For more information about Where conditions, refer to Where Conditions.

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 as follows:

  • 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.