Requisition details - Intergraph Smart Materials - 10.2 - Help - Hexagon

Intergraph Smart Materials Web Help (10.2)

Language
English
Product
Intergraph Smart Materials
Subproduct
Web
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.2

Maintain Requisitions_NewRequisition2

To understand this page you need to know the following:

Column

Description

Action/Notes

Engineering Requisition

Name (code, number) of the requisition. When you click on any engineering requisitions, the Maintain Requisition page will be displayed.

Mandatory

Basic Details

Supplement

Describes the supplement of this requisition.

Mandatory

Requisition Type

Indicates the type of requisition:

  • Order

  • Subcontract

Mandatory

Short Description

Language dependent short description for engineering requisitions.

Purchase

This indicates whether the line items of this engineering requisition can be used for both purchasing and inquiries or only for inquiries.

TE Required

Indicates whether the requisition must be evaluated technically or not.

MTO Type

Name (code) for the material take off type.

Requisition Node Path

Path of the requisition in the requisition nodes tree.

  • Mandatory column

  • In case of manually created requisitions you may change this path if you are logged in in the discipline of the requisition. When moving a requisition this does not only affect the current requisition but also all of its supplements.

  • Please note that you cannot select balance requisition node for manually created requisition. Balance requisition nodes are reserved for balance MTO jobs only.

MTO Job

Unique job-name within this project.

Created On

Indicates the date on which the inquiry was created.

Ready for Approval

Indicates whether this engineering requisition is ready for approval or not.

  • Only if this checkbox is checked a requisition can be approved in case that project default ZR_ADV_APP is set to 'Y'.

  • If ZR_ADV_APP is set to 'N' there is no function behind this checkbox.

  • If ZR_ADV_APP is set to 'R', then you can define the approval sequence and with the last approver approving the requisition is automatically released.

  • You can control whether the requisition can be marked as ready for approval using your own check procedures in the CIP function "check_rfa" in the package "M_PCK_REQ_CUSTOM".

  • Once this checkbox is checked, the requisition search conditions which are assigned to the approval templates in the Approval Templates page will be checked if the requisition can be searched in them or not. If found, then the approval template will be used to copy the same in the approval sequence for the requisition. The requisition search condition will be selected based on their order sequence number defined in the Requisition Search Criteria page.

  • Only after setting this checkbox and saving the changes you will be asked to send an email to the approver.

Approved Date

Indicates the date on which the engineering requisition has been approved.

Unique job-name within this project.

Status

Indicated the name of the requisition status defined in Requisition Status page.

Mandatory

Released to Procurement

Indicates the number of line items which have been released to procurement.

Other Details

MR Revision

Refers to the document revision (if one document has changed/updated or is missing, or a SR revision was done). This revision starts with 0 (zero) in case of being a requisition for purchase and starts with 'A' in case of being a requisition for inquiry only.

The MR Revision value is controlled by the following project defaults:

  • ZR_PO_MR - This parameter holds the MR Revision scheme for Purchase Requisitions.

  • ZR_INQ_MR - This parameter holds the MR Revision scheme for Inquiry Requisitions.

SR Revision

Refers to the material revision (if one Line Item exists (in an unapproved supplement), which has an increased quantity <> 0 or an attached VDR has changed/updated or is missing). This revision starts with 0 (zero) in case of being a requisition for purchase and starts with 'A' in case of being a requisition for inquiry only.

The SR Revision value is controlled by the following project defaults:

  • ZR_PO_SR - This parameter holds the SR Revision scheme for Purchase Requisitions.

  • ZR_INQ_SR - This parameter holds the SR Revision scheme for Inquiry Requisitions.

Origin

Indicates the name (code) for the origin (branch).

Mandatory

Balance

Balance requisition created by balance MTO Job.

Pricing Type

Name (code) of the pricing type.

Agreement Type

Type of the agreement.

  • The available agreement types depend on the purchase indicator of the requisition, the requisition type and the setting of project default ZP_CONSPCI.

  • If the requisition can only be used for inquiries and ZP_CONSPCI has been set to 'Y' (default) only agreement type 'Blanket Order' is available for requisition type 'Order' and only agreement type 'Master Agreement' for requisition type 'Subcontract'.

  • If the requisition can be used for purchasing or if project default ZP_CONSPCI has been set to 'N' you have more options.

  • If the requisition type is 'Order' one of the following types can be selected:

    • Blanket Order

    • Purchase Order

    • Notice of Commitment

    • Notice to Proceed

    • Blanket Order Release

    • Field Order

    • Rental Order

  • If the requisition type is 'Subcontract' the following types are available:

    • Master Agreement

    • Subcontract

    • Notice of Commitment

    • Notice to Proceed

    • Service Agreement

    • Work Order

  • A blanket order corresponds to a master agreement. When a blanket order is assigned to a requisition a purchase order (= blanket order release) based on this blanket order can be created; when a master agreement is assigned to a requisition a work order based on this master agreement can be created.

  • A notice of commitment can be converted into a purchase order.

Release Context

Indicates the number of line items displayed on the Line Items page.

Mandatory

Released By

The user who released the requisition to procurement.

  • Once released, an engineering requisition cannot be unreleased by the user.

Buy Cycle

Indicates the name (ascending sequence) of the requisition buy cycle defined in the Requisition Buy Cycle page.

Notes

Indicates whether notes have been assigned to the engineering requisition.

Originator

Indicates the originator of this requisition.

Mandatory

Template Set

Name (code) of the email template set.

Material or Service

Indicates the material or service which is assigned to this requisition.

Revision

Indicates the revision of the material/service.

Section

Name (code) of the section.

Category

Indicates the name (code) of the requisition category defined in the Requisition Categories page.

Account Code

Indicates the name (code) of the account code defined in the Accounts Code page.

Original Budget

Indicates the original budget (this must not reflect the sum of the line item budgets).

Mandatory

Total Budget

Indicates the sum of the line item budget values below this engineering requisition.

Currency

Indicates the currency of the budget.

Mandatory

Blanket Order

Indicates the number of the blanket order which is assigned to this requisition.

Master Agreement

Name (code, number) of the master agreement assigned to the requisition.

  • Only master agreements that have been approved can be entered here.

  • Master agreements can only be assigned to engineering requisitions that can be used for purchasing (checkbox 'Purchase' checked).

  • This field is only available for requisitions of type 'Subcontract'.

  • When assigning a master agreement to a requisition you are asked if you want to transfer data of the master agreement to the requisition.

  • If you opt for 'Yes' the agreement line items are taken over if the requisition has no line items.

  • Regardless of whether the requisition has line items or not the data of the price breakdown (= schedule of values), the scope of work and the SOW milestones are taken over.

Inquiry Requisition

Name (code, number) of the linked inquiry requisition.

  • This field can only be modified for requisitions that fulfill all of the following criteria:

    • The requisition must be for purchase.

    • The supplement of the requisition must be 0.

    • The requisition has not been approved.

    • Login discipline and requisition discipline match.

  • The list of values provided contains the inquiry requisition that has the same origin and the same MTO type as the purchase requisition you are currently positioned on. This inquiry requisition must already be approved and released to procurement. If an inquiry requisition exists that has not been approved or not been released to procurement the list of values will contain no entries.

  • When linking a purchase requisition with an inquiry requisition all attachments of the inquiry requisition are taken over to the purchase requisition both on header and on line item level. In other words attached properties, documents, text and terms, VDRs and notes are transferred to the purchase requisition.

  • Once an inquiry requisition has been linked to a purchase requisition this inquiry requisition cannot be revised any longer. I.e., button 'New Supplement' is no longer available for the inquiry requisition. You will also not be able to create additional inquiry requisition supplements via MTO.

  • When approving a purchase requisition, supplement 0 and this requisition has not been linked to an inquiry requisition a corresponding warning appears allowing you to abort the approval procedure and create this link. But you can also approve a requisition without this link.

  • Linking a purchase requisition to an inquiry requisition allows procurement to create agreements based on the quotes that have previously been created for the inquiry requisition. Thus it is possible to take over the results of the inquiry cycle such as costs, attachments or commercial conditions to the agreements.

  • For requisitions that have been linked to an inquiry requisition option 'Create from Inquiry' in page P.30.01 Requisition Workload is available. Please read the description of this option for more details on how the agreements are created based on the quotes.

Milestone Set

Indicates the name (code) of the milestone set.

Milestone Link

Indicates whether a milestone requisition link exists or not.

MS Supp

Indicates whether a milestone supplement exists or not.

Expediting Level

Name (code) of the level of expediting.

Inspection Level

Name (code) of the level of inspection

Criticality Level

Name (code) of the level of criticality.

Approved By

Indicates the user who approved this engineering requisition

Description

Language dependent description for engineering requisitions.

General CIP

If checked, CIP function 'general_cip' has already been executed.

Get Accounting

If checked, CIP function 'calc_account' has already been executed.

Get Budget

If checked, CIP function 'get_budget' has already been executed.

Get Designation

If checked, CIP function 'get_desig' has already been executed.

Handle BOM Documents

Indicator whether CIP m_pck_req_custom.handle_bom_doc has been executed.

Get Procure Channel

If checked, CIP function 'fast_progress' has already been executed.

Get ROS Date

If checked, CIP function 'calc_ros_date' has already been executed

Get Weight

If checked, CIP function 'calc_weight' has already been executed.