SmartPlant Materials A-Z Training – Create …spmat.hec.co.kr/marian_webentry/PDFs/SPMAT A-Z Training...In SmartPlant Materials, a requisition refers to an engineering material (or

SmartPlant Materials A-Z Training – Create Requisition MTO

Version 2011 R1 SP2 (7.1.2)

November 2014

DMAR1-TE-100006B

Copyright Copyright © 2010-2014 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished - rights reserved under the copyright laws of the United States.

Intergraph Corporation 300 Intergraph Way Huntsville, AL 35813

Documentation Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides, Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a particular software product.

Other Documentation Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support, SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph as guidance for using a software product.

Terms of Use a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the

software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product and Documentation. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal, non-commercial use. The Documentation may not be printed for resale or redistribution.

b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid licenseagreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial. The Other Documentation may not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any reason by Intergraph Corporation by giving written notice to Licensee.

Disclaimer of Warranties Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

2 SmartPlant Materials A-Z Training – Create Requisition MTO

Limitation of Damages IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.

IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.

Export Controls Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access) under the following circumstances:

a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries. b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce

Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S. Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S. Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.

c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design, development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive nuclear uses.

d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place. e. Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export

Compliance Department, Huntsville, Alabama 35894, USA.

Trademarks Intergraph, the Intergraph logo, Intergraph Smart, PDS, SmartPlant, SmartMarine, FrameWorks, I-Sketch, IntelliShip, ISOGEN, SmartSketch, SPOOLGEN, SupportManager, SupportModeler, Sapphire, and FreeView are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

SmartPlant Materials A-Z Training – Create Requisition MTO 3


Contents Objectives .................................................................................................................................................... 7

Prerequisites ........................................................................................................................................... 7 Overview ................................................................................................................................................. 8

Explanation .................................................................................................................................................. 9

Workflow Diagrams ............................................................................................................................... 11 Requisition Setup ........................................................................................................................... 11 MTO Job ......................................................................................................................................... 12

Basic Configuration ............................................................................................................................... 13 Project Defaults .............................................................................................................................. 13 Requisition Status ........................................................................................................................... 13 Requisition Buy Cycles ................................................................................................................... 14 Requisition Categories ................................................................................................................... 14 Sections .......................................................................................................................................... 14 Requisition Number Rules .............................................................................................................. 15 Requisition Description Rules ........................................................................................................ 16 Disposition Rules ............................................................................................................................ 17 Disposition Rule Sets ..................................................................................................................... 18 Document Types ............................................................................................................................ 19 Document Type Sets ...................................................................................................................... 20

BOM Sets .............................................................................................................................................. 20 Requisition Structure ............................................................................................................................. 22

Node Types .................................................................................................................................... 22 Requisition Nodes .......................................................................................................................... 23 Requisition Templates .................................................................................................................... 24

Requisition Split Sets ............................................................................................................................ 27 MTO Types ........................................................................................................................................... 28 MTO Jobs .............................................................................................................................................. 36

BOM Data Selection Options ......................................................................................................... 37 Requisition Options ........................................................................................................................ 37 Supplement Creation Options ........................................................................................................ 38 Quantity Calculation Options .......................................................................................................... 38 CIP Execution Options ................................................................................................................... 40 Job Control ..................................................................................................................................... 41 Job Execution ................................................................................................................................. 43

Tutorial........................................................................................................................................................ 47

Project Defaults ..................................................................................................................................... 47 Basic Requisition Setup ........................................................................................................................ 49 BOM Sets .............................................................................................................................................. 51 Where Conditions.................................................................................................................................. 53 Requisition Structure ............................................................................................................................. 55 Requisition Split Sets ............................................................................................................................ 59 MTO Types ........................................................................................................................................... 60 MTO Jobs .............................................................................................................................................. 61


Contents Quiz ............................................................................................................................................................. 67

Summary .................................................................................................................................................... 69

Quiz Answers ........................................................................................................................................ 69 Helpful References ............................................................................................................................... 69 Comments and Questions .................................................................................................................... 70

Index ........................................................................................................................................................... 71


S E C T I O N 1

In this lesson you will learn how to create requisitions based on BOM data using the material take off (MTO) functionality in SmartPlant Materials.

In detail, you will learn how to:

Administer the requisition setup

Define the requisition structure with nodes and templates

Define MTO types

Create MTO jobs

Run MTO jobs

Prerequisites For this session, you must know how to log in to the software with the appropriate access rights from your administrator. You also need to have a consolidated knowledge about SmartPlant Materials and SmartPlant Reference Data basic functionality, which means you should be familiar with general screen handling in the software.

Additionally, you need a basic knowledge of Bill of Materials (BOM) handling in SmartPlant Materials.

Sessions BASICS – General Screen Handling

SPMAT – How to Manage BOM

Objectives


Objectives

Overview This session explains how to handle requisitions for bulk material in SmartPlant Materials. During the tutorial, you define an MTO type with the needed requisition templates. In addition, you run an MTO job to determine the material needed based on a BOM and to create the requisitions.


S E C T I O N 2

In SmartPlant Materials, a requisition refers to an engineering material (or services) requisition. It contains the required material quantity plus contingency, specification, and requirement definitions from the engineering department. The requisition is released to the Procurement module of SmartPlant Materials (MSCM) for further action; for example, to create an inquiry, make an addition to a blanket order, and so forth.

The power behind this module centers on a process called the ‘MTO Job’. This process reviews all the material in the Work Breakdown Structure (WBS) and transmits it into the requisition structure. The requisition structure is how the procurement department prefers to view the material groups.

The graphic below illustrates the Bill of Materials (BOM) in the WBS.

The BOM contains all material organized according to the WBS. This is a structure the Engineering department is familiar with and is suited for the collection of bills of materials from design sources.

Explanation


Explanation The next step is to run an MTO job with various runtime parameters in compliance with the requirements.

This process/job can be run every time a new MTO is loaded or at specific milestones in a project. The result of this process is the generation of requisitions.

The requisitions contain all material quantity information. Any other information that is required to be passed from Engineering to Procurement, such as specifications, VDRs, and delivery destinations, is added after the requisition has been generated. SmartPlant Materials provides requisition tools to manipulate the requisitions that have been created.

The main aspects to consider for this process are as follows:

Basic Administration

Requisition Structure

MTO Types

Running an MTO job

Requisition Tools (reversing an MTO job)

You can find a workflow diagram showing the requisition setup overview in the chapter below.


Explanation

Workflow Diagrams Requisition Setup

This workflow diagram illustrates the needed steps and screens to set up the requisition module before you can run MTO jobs in a new project


Explanation

MTO Job This workflow diagram illustrates the MTO job process, starting with the selection of BOM nodes and positions based on BOM sets, where conditions, issue status and list status. The result is the requisitions created based on rules, project default settings, configurations, and so forth.


Explanation

Basic Configuration When starting a new project in SmartPlant Materials, you must define the E&PI(Req) related project defaults and perform the setup of the E&PI(Req) module. This setup can be done manually as described in this training guide. Or, you can copy the setup from an existing (template) project and then adjust it to the requirements of the new project. For more information about the setup copy functions, see the SmartPlant Materials Administrator's Guide, available from the Printable Guides page in the software.

Project Defaults You can find a detailed description of how to set project defaults and the purpose and usage of each project default in E&PI (Req) Project Defaults (ZR) in the SmartPlant Materials Project Defaults guide, available from the Printable Guides page in the software.

Some of the project defaults must be set before any requisition can be created or any MTO job can be launched in the project. Others are optional depending on the detailed workflow established by the project. The project defaults listed below must be set before creating requisitions via MTO job in a project.

Project Default Comment

ZX_CURCY Default currency for the project

ZX_ORIGIN Default origin; is set on the requisitions by the MTO job

ZR_DESC_RL Requisition description rule used by the MTO job for requisition description derivation

ZR_RLINC Default increment between two requisition line items

ZR_RULE Requisition rule used by the MTO job for requisition name derivation

Requisition Status A requisition must have a status assigned; by default, it is open. If the status is closed, the requisition has been released to Procurement (MSCM), and changes cannot be made except under special circumstances. For example, a change can be made to an inquiry requisition if the inquiry is supplement 0 and has not been issued. This allows last minute changes to be incorporated in a bid inquiry instead of creating a new supplement.

Requisition statuses are defined on the R.10.11 Requisition Status screen.


Explanation To define a status, enter the name in the Status field and the descriptions in the Short Desc and Description fields.

The Default indicator is set on all new requisitions, either created manually or during an MTO job.

The Production indicator is set on all requisitions that are released to procurement.

Requisition Buy Cycles The use of buy cycles is specified by the project requirement; it is not mandatory in SmartPlant Materials. A buy cycle is intended to group requisitions according to a phase (buy cycle) of a project. This allows management of requisitions and purchase orders (PO) according to the buy cycle associated with the PO. A buy cycle is defined by a date range and can be defined differently for each discipline.

Requisition buy cycles are defined on the R.10.12 Req Buy Cycles screen.

Requisition Categories Engineering requisitions can be categorized for reporting purposes. Examples of categories are Bulk Materials, Shop Fabrication - Labor and Materials, Subcontract, Equipment, and Tagged Bulks. Requisition categories are optional and do not need to be set.

Requisition categories are defined on the R.10.14 Req Categories screen.

To define a category, enter the name in the Category field and the descriptions in the Short Desc and Description fields.

Sections With sections you can define the departments or offices in charge of requisitions. If a section is assigned to a user or his role, the section can be used to limit the number of requisitions, inquiries, and agreements available for this user in the procurement (MSCM) screens. Sections are optional and do not need to be set.

Sections are defined on the P.10.36 Sections screen.


Explanation To define a section, enter the name in the Section field and the descriptions in the Short Desc and Description fields.

Requisition Number Rules A requisition number rule defines the way in which a requisition number (name) is automatically generated by the MTO job. When defining a requisition number rule, you must ensure that it always generates unique and consistent requisition names. Otherwise, the subsequent MTO job fails and you are forced to modify your rule.

Req(uisition) number rules can be defined on the R.10.13 Req Number Rules screen. The requisition number rule must be assigned to a requisition template on R.10.41; see Requisition Templates (on page 24).

To define a requisition rule, enter the rule name in the REQ Rule field and the descriptions in the Short Desc and Description fields. Select the Manual check box if this rule is used for numbering manual requisitions.

Use the project default ZR_MAN_RR to specify that the rule is used as the default for numbering manually created requisitions on R.30.01 Maintain Requisitions.

The rule is defined in the REQ Rule Definition field. For the rule definition you can use any fixed text in combination with several predefined parameters. To add parameters to the rule definition, use the LOV to select parameters from the list of available values as shown in the picture below.

The parameters must be delimited by the special character #. This is done automatically when selecting the parameters from the LOV. Free text must be entered without this special character.

As a sequence number, you can either use REQ_SEQ, which creates unique numbers for the entire project, or use RULE_SEQ, which uses separate number cycles for each rule.


Explanation If REQ_TYPE is used in a rule definition, an 'I' is added to the requisition number for requisitions that can only be used for inquiries (Purchase indicator not selected on R.30.01). A 'P' is added to the requisition number if the requisition can be used for both inquiries and agreements (Purchase indicator selected on R.30.01).

The parameters DISC and DISC_ABBREV are replaced by the discipline code and the discipline abbreviation, respectively.

The picture of R.10.13 above displays the example: #MTO_TYPE#-#REQ_TEMPLATE#. This rule would create a requisition name like: PIPING-PIPE CS.

The variables BOM_SETUP, MTO_TYPE, REQ_SPLIT_DETAIL, REQ_TEMPLATE, and REQ_TYPE cannot be used in rule definitions with Manual selected.

Requisition Description Rules A requisition description rule defines the way in which the requisition description is automatically generated by the MTO job.

Requisition description rules can be defined on the R.10.15 Req Desc Rules screen. The req desc rule must be assigned to the requisition template on R.10.41; see Requisition Templates (on page 24).

To define a requisition desc rule, enter the rule name in the REQ Desc Rule field and the descriptions in the Short Desc and Description fields. The rule is defined in the REQ Description Rule Definition field. For the rule definition, you can use any fixed text in combination with several predefined parameters. Further, you can use all the attributes defined on A.50.01. These are replaced by the attribute values when creating the requisition description. To add parameters to the rule definition, use the LOV to select the parameters from the list of available values. In addition to the attributes, the parameters listed below can be used.

#TEMPL-NLS-DESC#

#TEMPL-NLS-SHORT-DESC#

#MATGR-NLS-DESC#

#MATGR-NLS-SHORT-DESC#

#SET-DETAIL-NLS-DESC#

#SET-DETAIL-NLS-SHORT-DESC#


Explanation The parameters must be delimited by the special character #. This is done automatically when selecting the parameters from the LOV. Free text must be entered without this special character.

Disposition Rules The MTO job calculates the total recommended quantity (to be purchased) as the sum of all affected BOM position quantities; this corresponds to the total list quantity. The disposition rule can be used to round up the calculated quantity to get commercially available order quantities, or to add a safety margin for contingency or spare material.

The Total Recommended Quantity value is calculated by a function considering the Total List Quantity value and the disposition rule details.

The disposition rules can be defined on the R.10.22 Disposition Rules screen. You can assign disposition rules to the requisition templates on R.10.41; see Requisition Templates (on page 24).

To define a disposition rule, enter the rule name in the Dispo Rule field and the descriptions in the Short Desc and Description fields.

The details of the disposition rules must be defined on the R.10.23 Disposition Rule Details screen.


Explanation Dispo rules can be used individually or grouped into dispo rule sets. A set is applied during an MTO job and must be relevant to the project phase. For example, you could use dispo rule sets for the project phases ‘Estimate’, ‘Intermediate’, and ‘Final Design’. Each set refers to different rule details. The ‘Estimate’ phase requires more additional material than the ‘Intermediate’ phase, and in the ‘Final’ phase the calculated quantities are almost exact so additions are not needed.

To define dispo rule details, first select a dispo rule set in the Dispo Rule Sets block on the left. Then select a dispo rule in the Dispo Rules block on the right. Now you can enter the details for the selected dispo rule and relevant for the selected dispo rule set.

Enter a sequence number in the Order Seq field.

With the assigned Where condition, you define how the MTO job finds the idents for which the dispo rule must be applied. With the Where condition, a SQL statement is created, which is used by the MTO job to filter the material corresponding to the dispo rule requirements. For more information about Where conditions, refer to Where Conditions in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software. To assign a Where condition, either use the LOV in the Where Condition 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.23. You can either select one of the existing Where conditions or create a new one.

With the next fields you specify how the additional quantity is calculated. The % field defines the percentage addition, the Min Addend field defines the minimum quantity to be added, and the Max Addend field shows the maximum quantity to be added. An entry in the Absolute field is used to add this exact value (not used in combination with the other fields). With the value in the Rounding field, you define to which exact values the calculated quantity should be rounded up.

For example, to add 10% to the calculated pipe length, but not more than 50m and not less than 5m, with exact pipe lengths of 12m, the dispo rule would be defined with these details:

% = 10

Min Addend = 5

Max Addend = 50

Rounding = 12

The Param Char 1 - 5 and Param Num 1 - 5 fields can be used within the CIP m_pck_req_custom.std_dispo_qty. The standard version of the CIP does not use these fields.

The disposition rule specified here and assigned to the requisition template on R.10.41 is applied only when processing an MTO job if the Dispo Rule option of the MTO job is set to ‘Common Rule’.

Disposition Rule Sets Disposition rules are grouped by disposition rule sets. Individual dispo rules can be applied to requisition templates, whereas a dispo rule set is applied to an MTO type and thus to an MTO job. The idea is to have a company or project standard for contingency material that is generated by default, such as one rule set for preliminary material take-offs and others for the intermediate or final take-offs.


Explanation Disposition rule sets can be defined on the R.10.21 Disposition Rule Sets screen. A disposition rule set must be assigned to an MTO type on R.10.51; see MTO Types (on page 28).

To define a disposition rule set, enter the rule set name in the Dispo Rule Set field and the descriptions in the Short Desc and Description fields.

Dispo rule details valid for a dispo rule set are defined on R.10.23; see Disposition Rules (on page 17).

Document Types Documents are generated and attached to requisitions during MTO jobs, according to the rules defined by the assigned document types.

Document types are defined on the R.10.24 Document Types screen. Document types can be combined into sets on the R.10.25 screen.

Enter the document type name in the Document Type field and the descriptions in the Short Desc and Description fields.

With a name rule, you define how document names are created during a MTO job. For the rule definition, you can use any fixed text in combination with several predefined parameters. To add parameters to the rule definition, use the LOV in the Name Rule field to select the parameters from the list of available values as shown in the picture below.

The parameters must be delimited by the special character #. This is done automatically when selecting the parameters from the LOV. Free text must be entered without this special character.

If the LL (line level) indicator is checked, the document type applies to the requisition line items; otherwise, it applies to the requisition header

The Where condition can only be assigned if the LL indicator is selected. The CIP functions in M_PCK_DOC_TYPE_CUSTOM can use the assigned Where condition as a filter. With the Where condition, a SQL statement is created, which is used by the MTO job to filter the req


Explanation lines. For more information about Where conditions, refer to Where Conditions in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software. To assign a Where condition, either use the LOV in the Where Condition 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.24. You can either select one of the existing Where conditions or create a new one.

Document Type Sets Document types can be grouped into document type sets. These sets can be attached to requisition line items or requisition headers.

Document type sets are defined on the R.10.25 Document Type Sets screen. A document type set can be assigned to a requisition template on R.10.41; see Requisition Templates (on page 24).

In the first (Document Type Sets) block, enter the document type set name in the Document Type Set field and the descriptions in the Short Desc and Description fields and save the new type set.

Use the LOV in the Document Type field in the second (Document Type Set Details) block to assign predefined document types to the selected document type set.

BOM Sets The material to be processed by the MTO job must be specified by selecting BOM setup points, which are nodes on the WBS (Work Breakdown Structure). These nodes are called BOM setup nodes because the MTO job identifies in a first step all the nodes of the BOM structure, which are placed below one of these BOM setup nodes. After that, all BOM positions associated to these identified BOM nodes are included in the MTO. To allow the user to assign more than one BOM setup node to an MTO type, the setup points are grouped in sets of BOM setup nodes. After defining these sets, the user can assign one set to each MTO type.

With the BOM sets, you define the scope of the BOM that are included in an MTO type and thus in the created requisitions. Ideally, it is wise to include all BOM nodes in one BOM set to ensure no material is excluded material from the requisitions. By selecting the top node of the WBS (Work Breakdown Structure), all sub-nodes of this node and thus all associated positions are also included.

BOM sets can also be defined on lower (sub-node) levels; however, this requires a careful definition of additional BOM sets to include the remaining BOM nodes, and thus to ensure all material is captured.


Explanation The BOM sets are defined on the R.10.31 BOM Setup Nodes screen. The BOM sets must be assigned to the MTO types on R.10.51; see MTO Types (on page 28).

To create a new BOM set, enter the set name in the BOM Set field and the descriptions in the Short Desc and Description fields. Save this new BOM set.

Next click in the List Node field in the second (BOM Setup Nodes) block and open the LOV. The B.20.01 Edit BOM (LOV for multi select) window opens as displayed in the picture below.

Expand the nodes in the List Node field on the left by clicking the corresponding + sign. To select one or multiple nodes, select the corresponding Sel check boxes on the right. After that, click the button to insert the selected nodes on B.10.31 and to close the LOV. You


Explanation can use the button to select all displayed records or the button to clear the current selection.

Do not modify the BOM sets after requisitions have been generated. The calculation of quantity changes are based on consistent scopes. The quantities calculated based on the new/modified BOM sets are not comparable to the requisition quantities calculated based on the original BOM set.

Requisition Structure Node Types

Requisition nodes build a hierarchy to group the underlying templates and the associated requisitions. The requisition nodes are assigned to the MTO type to include all underlying requisition templates in the MTO job. If inquiries are issued on known material groupings based on previous experience and standard company practice, the requisitions must be broken down in a way that assists the procurement discipline. For example, large-bore gate valves may be sent for inquiry to a different supplier from small-bore gate valves or check valves. If this is the case, it is necessary to specify a different node and template for both items.

For example, the master node of a requisition node structure would be the Piping discipline, with these sub-nodes:

Pipe

Fittings

Valves

Gaskets

Other items

Each of the nodes would have templates assigned for different material types like:

Carbon Steel

Stainless Steel

Alloy

Non Metallic

Do not modify the template definition after requisitions have been generated. The calculation of quantity changes are based on consistent node structure and template definitions. The quantities calculated based on the new/modified template are not comparable to the requisition quantities calculated based on the original template.


Explanation

Requisition Nodes The requisition nodes are defined on the R.10.41 Nodes and Templates screen. To define a new node structure, first you must create a master node. Select R.10.48 Create Req Master Node from the fastcall.

The R.10.48 Create Req Master Nodes screen opens. Enter the node name in the Node field, the sequence in the Order Seq field, and the node descriptions in the Short Desc and Description fields.

The order sequence controls the display order of the nodes in the structure and the order in which the MTO job generates the associated requisitions. The node name and description can be used for the automatic requisition name creation, so it is advisable to consider these carefully.

Click the Save button to save the new master node. Proceed in the same way for the other master nodes.

To define the sub-nodes for the next level(s) of the requisition hierarchy, click the master node and select R.10.49 Create Req Nodes from the fastcall.

The R.10.49 Create Req Nodes screen opens. Enter the node name in the Node field, the sequence in the Order Seq field, and the node descriptions in the Short Desc and Description fields.


Explanation Click the Save button to save the new req node. Proceed in the same way for the other requisition nodes.

To create multiple sub-nodes under the same master node (or sub-node) without closing the screen, use the New Record button after saving the previous node.

The picture below shows an example of a requisition node structure for the piping discipline.

The last node in the sequence should be defined to catch all material that is not categorized

or grouped by the preceding requisition definitions. As such, the uncategorized data is highlighted. For more information, refer to the templates.

Although there can be many levels of sub-nodes, you should not define too many levels so that the requisitions are organized and easier to find.

Requisition Templates With requisition templates, you specify the scope of material that is allocated to the engineering requisition by the MTO job. Besides the material selection, which is the most important function of the template, requisition templates are used to define basic information that is valid for all engineering requisitions derived from these templates. Attributes can be assigned to the template and are copied to all derived engineering requisitions by the MTO job.

Requisition templates are always assigned to a requisition node. You can define requisition templates on the R.10.41 Nodes and Templates screen. Double-click the node in the tree view on the Requisition Nodes field on the left to open Window 2.


Explanation Enter the template name in the Name (Code) field and the descriptions in the Short Desc and Description fields.

By clearing the Enabled indicator, you can disable a rule so that it is not included in the MTO job process. This might be necessary for testing purposes or when the use of the template is not needed anymore due to project changes.

Select a predefined requisition number rule from the LOV in the REQ Rule field, and a predefined requisition description rule from the LOV in the REQ Desc Rule field. For more information, see Requisition Number Rules (on page 15) and Requisition Description Rules (on page 16).

With the value entered in the Exe Seq field you define the processing order of the templates within a node. When running an MTO job, the template with the lowest number is processed first, and so on. This is important if material can be allocated to more than one of the assigned templates, for whatever reason. This feature works in the same way as the node execution sequence to ensure that material is not duplicated on different requisitions.

With the assigned Where condition, you define how the MTO job finds the material for each requisition. With a Where condition, a SQL statement is created, which is used by the MTO job to filter the material corresponding to the requisition template requirements. For more information about Where conditions, refer to Where Conditions in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software. To assign a Where condition, either use the LOV on the Where Condition 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.41. You can either select one of the existing Where conditions or create a new one.

Select a predefined disposition rule from the LOV in the Dispo Rule field. For more information, see Disposition Rules (on page 17).

Select a predefined document type set from the LOV in the Doc Type Set field. For more information, see Document Type Sets (on page 20).

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 in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software.

You can set up SmartPlant Materials to generate an email when a requisition is released. This feature is described in detail in the SmartPlant Materials Mailing Features/Early Warning Alerts guide, available from the Printable Guides page in the software.

If the POS Man indicator is selected, the calculated quantities on the generated requisition can be changed manually. If you clear this check box, the only way to change the requisition quantities is to run another MTO job.

If the Manual to MTO line indicator is selected, the MTO job attempts to integrate manual line items into MTO line items. As a prerequisite, the manual line item data must already exist on the BOM and the BOM setup must cover these BOM positions. If the check box is not selected, the manual line item is available on the next requisition. If the project default ZR_MAN_MTO is set to ‘Y’, the check box is automatically checked when defining a new requisition template.

Select a predefined section from the LOV in the Section field. For more information, see Sections (on page 14). With sections you can define the departments or offices in charge of the requisitions.


Explanation Select a predefined category from the LOV in the Category field. For more information, see Requisition Categories (on page 14). Requisitions can be categorized for reporting purposes; for example, categories could be bulk material or equipment.

Account codes are usually applied to materials. The account code can be entered manually into the field, using the LOV in the Account Code field. Or, the code can be automatically included by the use of a CIP function. A CIP is generally used when another system stores both the account code and the requisition code. During the MTO job, the CIP references this other system and retrieve the appropriate value.

Select a predefined milestone set from the LOV in the Milestone Set field. Milestone sets are defined on the P.10.62 Milestone Sets screen. The Procurement (MSCM) module of SmartPlant Materials can monitor progress through the use of milestone sets applied to requisitions. Typically, this updates the predicted and actual dates of key events affecting a requisition as defined by the project. By entering the name of the milestone set, a link is formed between the requisition and milestone set.

After a blanket order (BO) has been created on the P.50.01 Agreements screen, the BO number can be selected from the LOV in the Blanket Order field to be assigned to the requisition. When this is done, the requisition is linked to the BO and automatically assigned to the BO when the requisition is released to Procurement.

You can assign an attribute set to the requisition using the LOV in the Attribute Set field. All attribute sets defined on the A.50.04 Attribute Sets screen are available. The assignment of the attribute set facilitates the entry of information on the requisition header level.

The next fields represent the MR/SR revision schemes for purchase order requisitions (PO MR Scheme, PO SR Scheme) and for inquiry requisitions (INQ MR Scheme, INQ SR Scheme). Per default, these fields are populated by the values assigned to the project defaults ZR_PO_MR and ZR_INQ_MR, respectively. These fields are not updatable if any requisition exists based on this requisition template.

The Balance Requisition indicator shows whether the selected node is used to create balance requisitions.


Explanation You can use the Order Criteria button to define order criteria. The available columns are displayed in the picture below.

If you define an order criterion that includes the tag number, the requisition line item

(position) is incremented for each different tag number if the ident is the same (standard with tags).

Click the Sum Attrs button to enter additional summary fields, and click the Group By button to enter group-by criteria. Both buttons are not available when the Balance Requisition indicator is checked.

The Doc Type Set, Email Templ Set, Section, Category, Account Code, Milestone Set, Blanket Order, Attribute Set, and PO/Inq MR/SR Scheme fields are optional and do not need to be used.

Requisition Split Sets Splits allow one requisition to be automatically split into multiple requisitions by the MTO job, depending on attribute values assigned to the BOM positions. A good example is to split the material based on the delivery destination, such as shop and field. This allows material from the same isometric to have different delivery dates and destinations applied. Typically, this can be facilitated by the use of the PDS fabrication category attribute that is first defined in the pipe class and then finalized in the design model.

A requisition split set consists of (one or more) requisition split details, which are defined by where conditions.


Explanation Requisition split sets are defined on the R.10.42 Req Split Criteria screen. The Req split sets can be assigned to the MTO types on R.10.51; see MTO Types (on page 28).

To create a new requisition split set, enter the set name in the Set Name field and the descriptions in the Short Desc and Description fields. Save the new Req split set.

Next, enter a name for the detail in the Detail Code field of the second (Req Set Details) block. With the sequence entered in the Exe Seq field, you define the order of execution by the MTO job.

With the assigned Where condition, you define how the MTO job finds the BOM positions for which the dispo rule must be applied, based on the attribute value. With the Where condition, a SQL statement is created, which is used by the MTO job to filter the material corresponding to the split criteria. For more information about Where conditions, refer to Where Conditions in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software. To assign a Where condition, either use the LOV in the Where Condition 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.42. You can either select one of the existing Where conditions or create a new one.

The picture below shows an example of the Where Condition field, defined for R.10.42 and used to filter material with the position attribute value FABCAT = ‘F’.

MTO Types The MTO type describes all characteristics of an MTO:


Explanation 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

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

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.


Explanation 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


Explanation 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_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


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


Explanation 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 (on page 20). With the BOM set, you define which BOM nodes and thus associated positions are included in the MTO job.


Explanation 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 (on page 23). 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 (on page 27). 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 (on page 18). 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 (on page 15). 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 (on page 16). With req desc rules, you define the way in which a requisition description is automatically generated by the MTO job.


Explanation 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 (on page 20).

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 in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software.

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. For more information, refer to the online help of the R.10.51 Parent Type field.

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 about Where conditions, refer to Where Conditions in the SmartPlant Materials Administrator‘s Guide, available from the Printable Guides page in the software.

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.


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

MTO Jobs MTO jobs are used to automatically generate engineering requisitions based on predefined rules and templates, and to determine the exact material requirement on the basis of predefined where conditions and BOM sets.

As a prerequisite for running an MTO job, the configuration of the underlying MTO type must be completed as described in the previous chapters.

MTO jobs are defined and can be launched on the R.20.01 MTO Jobs screen.

First, you select an MTO type in the MTO Type field in the first (MTO Types) block.

Next, you click into the Job field of the second (MTO Jobs) block to create a new MTO job. Click the New Record button, and enter the MTO job name in the Job field and the descriptions in the Short Desc and Description fields. Select a list status from the LOV in the Min. List Status field; this is a mandatory field. Save the new MTO job.

Besides the above mentioned fields, all other job parameters are derived from the corresponding project defaults that are set on A.20.11, A.20.12 or A.20.13. If any of the project defaults are not set or have an invalid value assigned, the default value for this project default is


Explanation used. You can find a detailed description of how to set the project defaults and the purpose and usage of each project default relevant for MTO jobs in the MTO Parameters section of the E&PI (Req) Project Defaults (ZR) chapter of SmartPlant Materials Project Defaults, available from the Printable Guides page in the software.

The options specified on this screen have a major impact on the materials that appear on the requisitions. It is essential that you understand the impact of your settings on this screen on the MTO job results.

The available MTO job parameters are listed below.

BOM Data Selection Options

You can either select the Best Quantity indicator with a Min. List Status, or, you must select a specific Issue Status. Best Quantity indicates the latest information available. However, it may make sense that you need to generate requisitions for the final BOM material only, in which case you would need to specify an exact Issue Status.

With the Only End Nodes indicator, you define whether all BOM nodes (indicator not selected) or only terminal BOM nodes (indicator selected) is processed. It is possible to store material at any node level of a BOM structure, although typically you would only store material at the end node. For example, during the first material take off from PDS, there are positions created on the node level pipe. Later in the design, when isometrics are created for each line, the positions appear under the lower node ISO. Using the Only Endnodes function ensures that only the lowest node is used for the requisition calculation.

If you select the 100% BOM Pos indicator, the MTO job fetches all BOM positions that do not satisfy any of the assigned (material) where conditions and copies them into a separate table. The contents of this table can be displayed after the MTO job is completed by clicking the Bad BOM Pos button at the bottom of the Job Control section.

Requisition Options

The For Purchase indicator controls whether the Purchase indicator of the generated engineering requisitions is set or not and therefore if the line items of these requisitions can be used for both purchase orders (PO) and inquiries or only for inquiries. If the indicator is not selected, SmartPlant Materials does not allow creating an agreement based on the requisition. This option is intended for inquiry use only and provides a way for engineering to get price information from preliminary MTO quantities.

Select the Technical Evaluation check box if the inquiry (created from the requisition) must include a technical evaluation. In that case, the inquiry evaluations cannot be finally approved until the Tech Eval box in the inquiry screen has been checked.


Explanation

Supplement Creation Options

Requisition supplements undergo an approval and release to procurement process. If you select the Delete Unreleased Suppl’s check box, the MTO job deletes any existing requisition (in the scope of this MTO job) that has not been released to procurement, create a new requisition, and consolidate the required material on the new requisition.

Select the Delete Unchanged Reqs check box to delete requisitions with no quantity changes (in comparison to the previous supplement of the same requisition).

When unreleased supplements are deleted by the MTO job and new requisitions are created, all manual changes on those deleted requisitions are lost. When the Keep Attachments check box is checked, the attachments of the deleted requisitions are temporarily saved and reattached when matching requisitions are re-created.

By default, the MTO job creates a requisition for each template defined for the assigned MTO type. Select the Delete Empty Reqs indicator to delete the requisitions with no line item, which means the MTO job hasn’t found any material that matches the template.

Set the Update Inquiry Reqs indicator when inquiry requisitions in supplement 0 shall be revised instead of creating a supplement. If a requisition has been used on an inquiry, it is still possible to update the quantities on the initial requisition. In this way, the bidders can get the very latest information. The prerequisites are that the initial requisition is at supplement 0 and that it has been released for inquiry only (not purchase).

When unreleased supplements are deleted by the MTO job and new requisitions are created, all manual changes on those deleted requisitions are lost. When you select the Keep Manual RLI’s indicator, the manual requisition line items are saved temporarily and reattached when matching requisitions are recreated.

Quantity Calculation Options

The Scope Of Interest field is used to define which quantities are to be generated in a requisition. The available options are:

All Quantities (+, -, and unchanged)

Shortage Quantities (only + quantities)

Surplus Quantities (only - quantities)

On the R.30.01 screen, you can set the Release Context display option. This field also allows displaying only shortage, only surplus, or all quantities. To be able to use this feature on R.30.01, the Scope Of Interest option must be set to ‘All quantities’.


Explanation The disposition procedure uses the calculated quantity for a line item (New List Quantity) to calculate an optimized quantity value, based on rules assigned to the material.

The logic (dispo rule), the disposition is processed, must be selected from the dropdown list in the Dispo Rule field. It can vary between two MTO jobs of the same MTO type and must be entered before the MTO job is started.

The four dispo options that are available in the Dispo Rule field are as follows:

Dispo Option Purpose

Common Rule The MTO job uses the Dispo Rule specified in the template.

Fix Dispo Addend This option calculates the recommended quantity (and hence the Dispo quantity) as equal to the greater of either the current Recommended Quantity or the previous supplement Released Quantity. This option avoids unnecessary qty changes on POs if the dispo quantity is not considered overly important.

Fix Dispo Quantity Dispo quantity remains the same as the previous supplement.

None No disposition (contingency) material. This option also disables the dispo rule specified in the template.

It is important to understand the different quantity fields on a requisition line before selecting the correct dispo rule option. The fields are listed below.

Field Purpose

New List Quantity Total quantity on the current (new) BOM.

Released Quantity Quantity that is released to procurement; by default, it initially equals the Recommended Quantity. This field can be edited manually by the user to change the contingency material.

Recommended Quantity The New List Quantity plus the dispo (contingency) material.

Select the Set Increased Quantity Factor to let the MTO job calculate the increased quantities based on the previous requisition supplement. When the indicator is not checked, the increased quantity field in the requisition is not calculated. It must then be manually verified by an engineer and set before the requisition can be released to procurement. This is a way to force the engineers to check the increased quantity rather than simply accepting the calculation done by the MTO job.


Explanation A BOM node may have a quantity factor set in its definition on B.20.01; see example in the picture below.

If the List Node Factor indicator is selected, the calculated quantity is multiplied by this qty factor. If it’s not checked, the factor is ignored.

Select the Handle Assemblies indicator to explode assemblies (on the BOM) into their component parts and include the individual components in the total quantity instead of the assembly quantity.

CIP Execution Options

Customer Implemented Procedures (CIPs) are SQL packaged procedures that can be executed when the MTO job is processed. A standard CIP to process ROS (Required On Site) dates is delivered with the software. This CIP searches for the BOM position attribute ROS_DATE and copy its value to the requisition ROS date to prevent any further data from being entered by the user. The attribute ROS_DATE must be defined as a position attribute and filled with a date value.

Other CIPs are optional for the user to implement according to different situations. Intergraph can assist with the development of these CIPs, as it requires detailed knowledge of SmartPlant Materials and the Oracle programming language.

The Execute General CIP Procedure radio group on top controls the execution of the general CIP procedures from the package m_pck_req_custom during the MTO job. The options are:

Do Not Execute The general CIP is not executed.

After Deleting Empty/Unchanged Reqs

The empty and/or unchanged requisitions are deleted before the general CIP is applied.

Before Deleting Empty/Unchanged Reqs

The empty and/or unchanged requisitions are deleted after the general CIP is applied.

The selectable CIP execution options are listed below.


Explanation Name Meaning

Get Accounting Generate the Accounting information. CIP std_job_id(r_id).

Get Budget Calculate budget values for requisitions and requisition line items. CIP calc_budget(r_id). The budget is set to 0 (zero) if it cannot be calculated.

Get Designation Fill delivery designation of a requisition line item. CIP procedure designation(r_id) is left empty (NULL) if a delivery designation cannot be found.

Handle BOM Doc Documents attached at BOM nodes to be attached to the requisition, documents attached at BOM position to be attached to the requisition line.

Get Milestone Reference

Update milestone reference. CIP procedure ms_reference(r_id) is left empty (NULL) if a milestone reference cannot be found.

Get Procure Channel Calculate the procure channel.

Get ROS Date Calculate the required on site (ROS) date for all line items of the requisitions. If the ROS date on a line item is changed manually after the MTO has run, the system recognizes this changed value during the following MTO job and tries to assign this value to the related line item on the new engineering requisition. CIP function ros_date(r_id). It calculates the ROS date by requisition, and all line items of this requisition get the same ROS date.

Get Weight Calculate the material weight for each requisition line item using this rule: (unit weight of the Ident) * (line item quantity). CIP function weight(ident). The weight is set to 0 (zero) if it cannot be calculated.

Select the price type defined on AS.10.01 from the LOV in the Price Type field. Select the option ‘With Catalog’ or ‘Without Catalog’ from the Price Display Type dropdown list.

Job Control

Click the Delete Jobs w/o Reqs button to delete jobs that have been completed but have not created any requisitions.

Click the Start Batch button to run the MTO job in batch mode.


Explanation Click the Start button to immediately launch the selected MTO job. Only one MTO job may be processed at a time; if another job is in progress, the MTO job fails and returns an error message.

Each completed job creates a log file.

Click the View Online Log button to open the A.60.72 Show Log File screen displaying the log file details.


Explanation Click the Bad Bom Pos button to open Window 2, which displays BOM positions (material) that were not handled by the MTO job.

Job Execution When all MTO job parameters are set and defined as described above, you can save the MTO job and click the Start button to launch the MTO job. If no errors occur and the MTO job completes successfully, a message appears as shown below.

The result of a successful MTO job is the creation of requisitions and requisition line items according to the rules, templates, BOM sets, and where conditions assigned to the underlying MTO type. You can verify the result on the R.30.01 Maintain Requisitions screen.

The MTO Type, MTO Job, and Created On fields on the right show the MTO job information.


Explanation Double-click the requisition in the Engineering Requisition field to open Window 2, which displays the requisition line items.

The time it takes to process an MTO job depends on the scope (material, BOM positions)

and the complexity of the options. When a job has been processed once, it cannot be run again. The easiest way to re-run an MTO job is to copy the job. To do this, select the job to be copied, click F4 (new record), click F6 (duplicate record above), rename the new job, and save the new job.


Explanation


S E C T I O N 3

The purpose of this tutorial is to configure the requisition setup and to create and run MTO jobs in the E&PI(Req) module of SmartPlant Materials.

Be sure to read the Explanation (on page 9) section of this training document before starting the tutorial.

Before starting the tutorial, please log in to the TRAINPROJ project and the PIPING discipline. You can check the project and discipline by looking at the bottom of the screen.

Project Defaults Purpose This section explains how to set the relevant project defaults when starting a new project in the SmartPlant Materials E&PI(Req) module.

Exercise 1. Open the A.20.12 Projects Defaults screen from the Administration > A.20

Project/Product Group menu branch.

2. The login project should be displayed in the first block. If not, click the Enter Query

button to change to query mode, open the LOV using the List of Values button, and

select the project from the list. Then click OK to close the LOV. Click the Run Query button to display the selected specification with its details.

Tutorial


Tutorial 3. Click the E+PI(Req) tab to display the project defaults relevant for the Requisition module.

4. Double-click in the Value field of project default ZR_DESC_RL to open the LOV, select

PIPING, and click OK to close the LOV and copy the selected value to the Value field. In the same way, set the following project defaults:

Project Default Value

ZR_DESC_RL PIPING (-> 5021)

ZR_RLINC 1

ZR_RULE PIPING (-> 5061)

5. Click the General tab to display the global project defaults.

Set the following project defaults:

ZX_CURCY Select any currency from LOV (predefined on A.10.12)

ZX_ORIGIN Select any origin from LOV (predefined on A.10.33)

Save the changes using the Save button.

6. Close the screen by selecting File > Close All or Close from the main menu.


Tutorial

Basic Requisition Setup Purpose This section explains how to do a basic requisition setup when starting a new project in the SmartPlant Materials E&PI(Req) module.

Exercise 1. Open the R.10.11 Req Status screen from the SmartPlant Materials > E&PI (Req) > R.10

Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

2. To create the req status ‘OPEN’, enter ‘OPEN’ in the Status field and ‘Open’ in the Short

Desc and Description fields. Select the Default indicator, and then click the Save button. Create a second status ‘CLOSED’ in the same way, but select the Production

indicator. Click the Save button.



Tutorial 4. Open the R.10.13 Req Number Rules screen from the SmartPlant Materials > E&PI (Req)

> R.10 Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

5. To create the req rule ‘PIPING’, enter ‘PIPING’ in the REQ Rule field, ‘Piping’ in the Short

Desc field, and ‘Number Rule for discipline Piping’ in the Description field. In the REQ Rule

Definition field, click the List of Values button to open the LOV. Select MTO_TYPE from the list and click OK. Then enter the minus sign (-), open the LOV again, select

REQ_TEMPLATE from the list, and click OK. To save the new rule, click the Save button.


7. Open the R.10.15 Req Desc Rules screen from the SmartPlant Materials > E&PI (Req) >

R.10 Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

8. To create the req description rule ‘PIPING’, enter ‘PIPING’ in the REQ Desc Rule field,

‘Piping’ in the Short Desc field, and ‘Description rule for discipline Piping’ in the Description field. In the REQ Description Rule Definition field, click the List of Values


Tutorial

button to open the LOV. Select TEMPL-NLS-DESC from the list, and click OK. To save

the new rule, click the Save button.


BOM Sets Purpose This section explains how to define BOM sets when starting a new project in the SmartPlant Materials E&PI(Req) module.


Tutorial Exercise 1. Open the R.10.31 BOM Setup Nodes screen from the SmartPlant Materials > E&PI (Req)

> R.10 Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

2. To create the new BOM set ‘PIPING’, enter ‘PIPING’ in the BOM Set field and ‘Piping’ in the

Short Desc and Description fields. To save the new set, click the Save button.

3. Click in the List Node field of the second (BOM Setup Nodes) block.

4. Click the List of Values button to open the BOM multi-selection LOV.

If you want to select a lower level node, click the + sign in front of the node name to

expand the node.

5. Select the Sel check box of the top node PIPING


Tutorial 6. Click the button to copy the selected node to R.10.31. This action

automatically closes the multi-selection window, copies the selected nodes to R.10.31, and saves the changes.

The BOM set definition should now look like the picture below.


Where Conditions Purpose This section explains how to define the where conditions needed for the requisition template definition. By means of the where condition, the MTO job selects the material for each requisition.

Exercise 1. Open the A.60.06 Where Conditions screen from the Administration > A.60 Utilities

menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.


Tutorial 2. Enter ‘PIPES’ in the Name field and ‘Pipes’ in the Short Desc and Description fields.

‘Attribute based’ is automatically set as the default in the Kind of field; do not change it.

Click in the Module field and open the LOV using the List of Values button, select R1041 from the list, and click OK to complete the selection.

3. To save the new where condition, click the Save button.

4. In the second (Attributes for Where Conditions) block, the condition ‘Ident mapped to

Ident’ was automatically inserted. This condition is an internal condition and must not be changed.

5. Click into the Attribute field of the next empty record. Click the List of Values button to open the LOV. Select GROUP_CODE from the list and click OK to complete the selection.

6. Select = as the operator from the dropdown list in the Operator field.

The operator = means that the value found for this attribute must exactly match the value entered in the Value field.

7. Enter ‘P’ in the Value field.

In our example, P is the group code of the Pipes commodity group.

8. Click the Save button to save the changes.

9. Click the button to create the associated MV_WHERE view. The View Status field should beset to Valid as displayed in the picture below.

10. Create additional where conditions in the same way as described above. Here are the

details:


Tutorial

Name Short Desc Description GROUP_CODE

FLANGES Flanges Flanges ‘F’

BW FITTINGS BW Fittings Buttweld Fittings ‘B’

FO FITTINGS Forged Fittings Forged Fittings ‘O’

11. Click the Save button to save the changes. All where conditions should have the View Status field set to ‘Valid’.

12. Create another where condition called ‘ALL’ without any restriction. Enter ‘ALL’ in the Name field and ‘All material’ in the Short Desc and Description fields. Click in the Module field

and open the LOV using the List of Values button, select R1041 from the list, and click OK to complete the selection.

13. To save the new where condition, click the Save button.


Requisition Structure Purpose This section explains how to define requisition nodes and templates when starting a new project in the SmartPlant Materials E&PI(Req) module.


Tutorial Exercise 1. Open the R.10.41 Nodes and Templates screen from the SmartPlant Materials > E&PI

(Req) > R.10 Setup menu branch.

2. Select R.10.48 Create Req Master Nodes from the Fastcall dropdown list.

3. Enter ‘PIPING’ in the Node field, 10 in the Order Seq field, ‘Piping’ in the Short Desc field,

and ‘Piping Discipline’ in the Description field. Click the Save button to save the new master node.

Click the at the upper right corner of R.10.48 to close this screen.

4. Close the R.10.41 screen and reopen it to refresh the node tree on the left. Select the new master node PIPING.

5. Select R.10.49 Create Req Nodes from the Fastcall dropdown list.


Tutorial 6. Enter ‘PIPES’ in the Node field, 10 in the Order Seq field, ‘Pipes’ in the Short Desc field,

and ‘Pipe Material’ in the Description field. Click the Save button to save the new node.

7. In the same way, create further requisition nodes underneath the master node PIPING as

listed below.

Node Order Seq Short Desc Description

FLANGES 20 Flanges Flanges

FITTINGS 30 Fittings Fittings

LEFTOVERS 999 Leftovers unconsidered Material

Click the at the upper right corner of R.10.49 to close this screen.

8. Close the R.10.41 screen and reopen it to refresh the node tree on the left. It should now look like the picture below.

9. Double-click the ‘PIPE’ node in the requisition nodes tree to open Window 2. Enter

‘PIPE-CS’ as the name of the new template in the Name (Code) field and select the Enabled indicator. Enter ‘Pipe CS’ in the Short Desc field and ‘Pipe Carbon Steel’ in the Description field. Click in the REQ Rule field and open the LOV using the List of Values

button, select PIPING from the list, and click OK to complete the selection. Next, click in

the REQ Desc Rule field and open the LOV using the List of Values button, select PIPING from the list, and click OK to complete the selection. Enter 1 in the Exe Seq field.

Click in the Where Condition field and open the LOV using the List of Values button, select PIPES from the list, and click OK to complete the selection.

Click the Save button to save the new template. Click the in the upper right corner of Window 2 to close this window.


Tutorial 10. Double-click the ‘FLANGES’ node in the requisition nodes tree to open Window 2. Create a

new template in the same way as described above and as displayed in the picture below.


11. Double-click the ‘FITTINGS’ node in the requisition nodes tree to open Window 2. Create new templates in the same way as described above and as displayed in the picture below. For this node, we need two templates to cover the buttweld fittings and the forged fittings.

Click the Save button to save the new templates. Click the in the upper right corner of Window 2 to close this window.

12. Double-click the ‘LEFTOVERS’ node in the requisition nodes tree to open Window 2. Create a new template in the same way as described above and as displayed in the picture below.

This template is used to collect all remaining material, that was not selected by any of the other templates. For this reason, we assign the where condition ALL, which does not have any restriction with regard to the material.




Tutorial

Requisition Split Sets Purpose This section explains how to define requisition split sets needed for the MTO type definition. For this exercise, we define a NO_SPLIT set for material that should not be split.

Exercise 1. Open the R.10.42 Req Split Criteria screen from the SmartPlant Materials > E&PI (Req) >

R.10 Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

2. Enter ‘NO_SPLIT’ as the name of the requisition split set in the Set Name field and ‘No Split’

in the Short Desc and Description fields.

3. Click the Save button to save the new split set.

4. Click in the Detail Code field of the second (Req Set Details) block, and enter ‘NO’ in the Detail Code field and ‘1’ in the Exe Seq field.

5. Click in the Where Condition field, and open the LOV using the List of Values button, select NO_SPLIT from the list, and click OK to complete the selection.



Tutorial 7. Close the screen by selecting File > Close All or Close from the main menu.

MTO Types Purpose This section explains how to define MTO types.

Exercise 1. Open the R.10.51 MTO Types screen from the SmartPlant Materials > E&PI (Req) > R.10

Setup menu branch. The screen opens in input mode; all fields are empty and the mandatory fields are displayed with a green background.

2. Enter the new MTO type name ‘PIPING’ in the Type field, ‘Piping’ in the Short Desc field,

and ‘Piping discipline MTO’ in the Description field.

The next fields are preset with defaults; do not change the values.

3. Click in the BOM Set field and open the LOV using the List of Values button, select PIPING from the list, and click OK to complete the selection.


Tutorial 4. Click in the Req Node field, and open the LOV using the List of Values button. Select

the top node PIPING from the tree, and click OK to complete the selection.

5. Click in the Req Split field, and open the LOV using the List of Values button, select NO_SPLIT from the list, and click OK to complete the selection.



MTO Jobs Purpose This section explains how to define and run MTO jobs.

Exercise 1. Open the R.20.01 MTO Jobs screen from the SmartPlant Materials > E&PI (Req) > R.20

Material Take Off menu branch.


Tutorial 2. The first (MTO Types) block displays the predefined MTO types. You must select the

appropriate type to be used for the MTO job. In our example, just the PIPING MTO type is available.

3. Enter ‘PIP-001’ as the name of the new job in the Job field of the second (MTO Jobs) block

and ‘1st MTO’ in the Short Desc and Description fields.

4. Click in the Min. List Status field, and open the LOV using the List of Values button, select 00-DEF from the list, and click OK to complete the selection.

All other fields are either optional or are preset according to the setting of the related project defaults.


6. Click the button in the Job Control Section in the lower right corner to launch the MTO job.

If the job was successful, a message appears informing you about the job result, as displayed in the picture below.

7. Click OK to complete the job.


Tutorial 8. In case of an error, you can use the button to open the A.60.72 Show

Log file of MTO Job screen. Here you can check the log file to find the reason for the problem.

Click the in the upper right corner of this screen to close A.60.72 and go back to R.20.01.

9. Click the button to open Window 2 where BOM positions that were NOT handled by the MTO job are displayed.

If all settings were made correctly as described in the previous chapters, the screen should not show any positions as displayed in the picture below.



Tutorial 11. Open the R.30.01 Maintain Requisitions screen from the SmartPlant Materials > E&PI

(Req) > R.30 Requisitions menu branch. The screen opens in enter query mode; all fields are displayed with a yellow background.

12. Click the Run Query button to display the requisitions created by the MTO job.

13. Scroll to the right to display the MTO job related information.

14. Double-click the requisition name in the Engineering Requisition field to open Window 2,

which displays the requisition line items.

In the New List Quantity field, you find the summarized quantity for the selected ident found by the MTO job on all BOM positions considered by the job.


Tutorial 15. Close the screen by selecting File > Close All or Close from the main menu.


Tutorial


S E C T I O N 4

1. The CLOSED requisition status is set when:

a. The requisition is created.

b. The requisition is approved.

c. The requisition is released to Procurement.

2. How can you specify that MTO jobs automatically round up the calculated quantity to cover contingencies?

3. What do you specify with BOM sets?

a. The scope of the BOM to be included in the MTO job

b. The kind of material to be placed on a requisition

c. The time interval when the MTO job is executed

4. The requisitions to be created by an MTO job are predefined by

a. Requisition nodes

b. Requisition templates

c. Requisition number rules

5. How can you ensure that an MTO job ‘finds’ all material within the defined scope of BOM?

Quiz


Quiz


S E C T I O N 5

In this tutorial, you learned how to:

Administer the requisition setup

Define the requisition structure with nodes and templates

Define MTO types

Create MTO jobs

Run MTO jobs

Quiz Answers 1. The CLOSED requisition status is set when:

c. The requisition is released to Procurement

2. How can you specify that MTO jobs automatically round up the calculated quantity to cover contingencies?

By means of disposition rules

3. What do you specify with BOM sets?

a. The scope of the BOM to be included in the MTO job

4. The requisitions to be created by an MTO job are predefined by

b. Requisition templates

5. How can you ensure that an MTO job ‘finds’ all material within the defined scope of BOM?

Assign a template with no material restriction to the last requisition node to collect the leftovers.

Helpful References SmartPlant Materials and Reference Data - User Interface Basics

Summary


Summary

Comments and Questions Please send comments or questions to [email protected] (mailto:[email protected]).


mailto:[email protected]

B Basic Configuration • 13 Basic Requisition Setup • 49 BOM Data Selection Options • 37 BOM Sets • 20, 51

C CIP Execution Options • 40 Comments and Questions • 70

D Disposition Rule Sets • 18 Disposition Rules • 17 Document Type Sets • 20 Document Types • 19

E Explanation • 9

H Helpful References • 69

J Job Control • 41 Job Execution • 43

M MTO Job • 12 MTO Jobs • 36, 61 MTO Types • 28, 60

N Node Types • 22

O Objectives • 7 Overview • 8

P Prerequisites • 7 Project Defaults • 13, 47

Q Quantity Calculation Options • 38 Quiz • 67 Quiz Answers • 69

R Requisition Buy Cycles • 14 Requisition Categories • 14 Requisition Description Rules • 16 Requisition Nodes • 23 Requisition Number Rules • 15 Requisition Options • 37 Requisition Setup • 11 Requisition Split Sets • 27, 59 Requisition Status • 13 Requisition Structure • 22, 55 Requisition Templates • 24

S Sections • 14 Summary • 69 Supplement Creation Options • 38

T Tutorial • 47

W Where Conditions • 53 Workflow Diagrams • 11

Index
