Verifications - Intergraph Smart Materials - 10.2 - Training - Hexagon

Smart Materials Web Tutorials

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

Verification routines are processing procedures to verify and maintain data in BOMs. There are two types of verifications: fixed and variable.

Verifications of the fixed type are part of Smart Materials and cannot be changed (except for the description).

Verifications created by the user are of the ‘Variable’ type. These verifications can either be a customer-installed procedure (CIP), or a variable list check that associates a Where Condition (from Administration > Query Builder) with a check name.

Customer-installed procedures (CIPs) are PL/SQL procedures that must be incorporated into the Smart Materials custom package called M_PCK_VERIFY_CUSTOM. They allow you to embed any kind of complex processing logic that may be developed and implemented by customers, and seamlessly integrate this logic into Smart Materials verification processing. A Where condition must be allocated to each ‘Variable’ type verification routine. Without a Where condition, the verification routine cannot be allocated to a verification job (on Procedures/Macros, called from Maintain BOM), or to a List Status (on List Status). The properties to be edited during verification processing are defined in this Where condition. Property values and logic rules (AND, OR) can also be given in the Where condition. For more information about Where conditions, see Query Builder.

The verifications can be maintained on the Verifications screen.

Select the Exclude check box to exclude the list check from the use in the Verifications screen. List checks with Exclude marked are not available for selection with the corresponding button.

Select the Only Endnodes check box to restrict the usage of a list check on BOM end nodes only. This means, only the end nodes in the BOM tree hierarchy below the selected start node will be processed. In the Verifications screen, the value of this check box will be evaluated when adding list checks to a list job and before execution of the list job.

Fix Verification Routines

The Verification routines of type ‘FIX’ are part of Smart Materials delivery, and they cannot be changed. The available fix verifications are:

BLD_IDENT (Build Idents): This program calls the procedure that builds idents.

BOM_COPY (Copy Assemblies to BOM): This program copies assemblies as defined on S.70.03/S.70.04 to the Bill of Materials. It is driven by the BOM_COPY rule setup in the Project Defaults.

BOM_POS (Find BOM terminal nodes without BOM positions): This program finds BOM terminal nodes beneath the starting node specified for the verification job that do not have any BOM positions. This data quality check detects potential incomplete BOM structures.

EST_SHORT (Calculate Estimation Shortage): This program can be used on the Maintain BOM screen. The purpose of this check routine is to automatically generate an isometric with the missing material. This material will be the difference between the first estimation and the material included in the isometrics loaded into Smart Materials when a line is incomplete.

FND_IDENT (Find Idents): This program attempts to find idents for BOM positions, using this set of rules:

  • If a BOM position has a specification code assigned, the program tries to find an ident using the specification, short code, option code, and sizes.

  • If no specification is assigned, but the BOM position has a commodity code, the program tries to find an ident for a special item, using the commodity code and sizes.

IDENT_INFO (Update Ident Information): This program updates BOM positions that already have an ident with the information from the Smart Reference Data module that is associated with this ident; that is, it sets the commodity group, part, commodity code, and sizes accordingly. So, this is a means of synchronization for the BOM positions data.

ISSUE_DEL (ISSUE_DEL): This procedure deletes positions of a specified issue status. However, ISSUE_DEL does not process or delete positions with site quantities, which ISSUE_REV does.

ISSUE_REV (ISSUE_REV): This program can be used on the BOM Import Job Details screen (Start Job). The purpose of this check routine is to reverse an issue to site and thus to enable reloading of an existing highest issue status of the BOM, although reservations and/or issues have already been done. The check determines the highest issue status on a node, and it determines the next lower issue status on a node. It transfers site quantities recorded against positions in the highest issue status to matching positions in the next lower issue status. If for such a position no matching position exists in the next lower issue status, a "dummy" position with quantity 0 is created. So, this is the same as the Transfer Site Quantities logic (ZI_OMI_TSQ) in the OMI interface, with the difference that it works in the opposite direction here. References in the Site module to these positions (issues, reservations, and so forth) are remapped to those matching positions in the next lower issue status. Furthermore, after this transfer has been done, the BOM positions in the highest issue status are deleted and already executed Design Change Issue transfer logs are deleted also.

This check is therefore an extension of the logic of the already existing check ISSUE_DEL, which also deletes positions of a specified issue status. However, ISSUE_DEL does not process/delete positions with site quantities, which this ISSUE_REV check does.

Parameters to the ISSUE_REV check: Parameters specified on B.20.01.41 are ignored. Regardless of what is specified as an Issue Status option, or as a List Status option, or additional query conditions, this check always works the same way: it finds the highest and the second highest issue status at a node, and transfers site quantities from the first to the latter, and then deletes the highest issue status.

Error conditions: This transfer (and the subsequent deletion) cannot take place if:

  • There are no positions at this node at all (an obvious case)

  • The node is locked (released_ind = 'Y' on the BOM node)

  • Positions at this node have a locked list status

  • There is only one issue status at this node (that is, there is no lower one to transfer to)

  • Unprocessed Design Change Log entries for this node and the highest issue status exist in the Site > BOM Design Change Log screen; that is, entries exist where the destination warehouse for a DCI has not been specified yet, and thus the DCI quantity could not be transferred.

If any of these error conditions are met, processing is halted for this node, an error log entry is made, and the processing continues with the next node.

PJSPEC (Check Specification): This program iteratively checks the BOM positions data against the assigned specification.

SPEC_UPDT (Spec update): This program updates spec references on the BOM position to the latest issued revision of the spec.

TSQ (Transfer Site Qty for IFC to highest Issue Status at Node): This program can be used on the BOM Import Job Details screen (Start Job). The purpose of this check routine is to transfer Site Quantities (Issued and/or Reserved Quantities) on BOM positions in an "IFC" issue status of a BOM node to the highest existing "Engineering" issue status of that node. Optionally, when ZI_OMI_DCC is set to Y, the OMI Design Change Control processing logic is also applied.

TSQ_CHK (Find Nodes higher IS but not with Issued/Reserved QTYs): This program can be used on the Maintain BOM screen. The purpose of this check routine is to find out all the BOM nodes with the positions in an Issue Status differing from the highest Issue Status and having the site records assigned (issued and/or reserved qty).

UPD_ASSEMB (Update of assembly): The new list check UPD_ASSEMB will check whether the list position is referencing the highest revision of the specification.

If this is not the case, existing assembly children in the list positions will be deleted and the revision of the specification will be updated to the highest available revision.

A find ident verification will then be executed to check whether the ident is still valid and the ident eventually replaced with the correct one.

For the replacement of the ident the same behavior as for the list check UPD_SP_IDT (see note below) is used.

If a new ident is found, the assembly will be exploded for the list position.

The restrictions as for the list check BOM_COPY (existence of the common rule defined in project default ZB_COCP, no processing for positions with existing site quantity) apply.

If the check whether update of the ident is allowed (list position is already used on a requisition, see CIP m_pck_bomcustom.validate_ident_update) fails, the quantity of the list position is set to 0 and a list pos record with the new ident is added to the list node, otherwise the ident is updated in the existing list position.

If a new list position is created, the Pos field is calculated from the values of the project defaults ZB_LP_INC and ZB_LPSTART.

The value of Created by is set to 'VERIFY' for the list pos records created by the UPD_SP_IDT list check.

Find ident will also consider the new CIP VALIDATE_IDENT_UPDATE in package M_PCK_BOM_CUSTOM for allowing the update of list positions and depending on the check create a new position and update the quantity of the old position to 0.

If an ident is not found by the find ident, then the input values of the affected list position will not be changed, only the ident will be removed.

If the Only Endnodes checkbox is selected on Verifications screen, then only the end nodes in the BOM tree hierarchy below the selected start node will be processed.

UPD_SP_IDT (Update of spec ident): This program checks whether the list position is referencing the highest revision of the specification. If this is not the case, the revision will be updated to the highest available revision and the ident will be checked whether it is still valid. In case the ident is not found on the specification anymore, a find ident (see note below for details) is executed and in case a different ident is available, the list position will be updated as follows:

If the check whether update of the ident is allowed (list pos is already used on a requisition, see CIP m_pck_bom_custom.validate_ident_update) fails, the quantity of the list position is set to 0 and a list pos record with the new ident is added to the list node, otherwise the ident is updated in the existing list position. If a new list position is created, the Pos field is calculated from the values of the project defaults ZB_LP_INC and ZB_LPSTART. The value of Created by is set to VERIFY for the list position records created by the UPD_SP_IDT list check.

The find ident in this list check is first run with the complete input information available on the list position. If no ident is found it is run without schedule information. As in the standard find ident list check the input values of the ident are set depending on the project default ZB_FI_SIZE.

VER_IDENT (Verify Ident Prerequisites): This program checks the prerequisites for building idents; that is, it determines whether all commodity rule details that are defined as mandatory are present.