Component Validation in a nutshell

Document ID : KB000018429
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When an element gets moved, component validation ensures that if the element would be generated at the target stage it would have the very same list of input components. To find out more about component validation and how to optionally redefine the search route, read this document!

Solution:

HOW COMPONENT VALIDATION WORKS

When an element gets moved, component validation ensures that if the element would be generated at the target stage it would have the very same list of input components.

When you cast a package, if component validation is active, Endevor examines the source location of all Move actions. Then Endevor builds a list of all the input components for each element being moved. Using the list, Endevor proceeds as follows:

For every input component in the list, Endevor searches the Environment map starting at the source location of the Move action. When Endevor finds the first occurrence of a component, it compares the footprint of that component with the footprint in the component list. If the footprints are the same, the cast is successful, if any footprints are different, Endevor fails the cast.

If Endevor does not find a component after searching the elements and the component's map routes, Endevor issues an error message indicating the element contains one or more components that could not be validated.

To simplify the process lets break component validation down into 2 phases.

Phase 1 of Component Validation:

Endevor searches for the input component from the MAP location (ENV/STG/SYS/SBS) of the used input component. For the first found occurrence, we test if the footprint matches the footprint of the used input component.


 IF FOUND AND MATCHING FOOTPRINT - GO DO PHASE2       
 IF FOUND AND INCORRECT FOOTPRINT - FPVL003 (FOOTPRINT ERROR) 
 IF NOT FOUND - FPVL002 (NO MATCHING C1DFLTS)

Phase 2 of Component Validation:

Endevor will search for the in-between versions of the input component from the Environment/Stage location of the element being moved using the input components System/Subsystem.


 NO IN-BETWEENS FOUND - RC00
 NO MAP ROUTE FOUND, - WILDCARD SBS AND SEARCH AGAIN
 NO MAP ROUTE FOUND, - WILDCARD SYS AND SEARCH AGAIN
 NO MAP ROUTE FOUND - FPVL007E (NO MAP ROUTE)
 IF IN-BETWEEN VERSION IS FOUND - FPVL008E (IN BETWEEN FOUND)

Today, many sites are using parallel or converging system and subsystem map. If the location of the component changes system or subsystem names across your map, the first found logic might not find a component. If you have parallel systems or subsystems that map to one system or subsystem, then component validation checks all map routes. For example, a cast will fail, if your package is moving a modified element that is located in one system or subsystem while a modified input component is located in the same stage but in the other (parallel) system or subsystem.

The administrator can change this default behavior by defining which map routes will be included during the search of components. This option can only be set in the Optional Features table (ENCOPTBL). This feature allows the Endevor Administrator to direct the component validation search to specific inventory locations or away from them. The table is displayed as follows in the optional features table and each is option is described below:


  OPTION                                                             ENV        STG         SYS          SBS
----------------------------------------------------------------------------------------------------------------------------------
COMPONENT_SEARCH=OFF    (DEFAULT)                                    ELM        ELM        COMP          COMP      
  Search from the ELEMENT Environment and Stage using the COMPONENT System and Subsystem  
 
COMPONENT_SEARCH=(ON,1)                                              ELM        ELM        ELM             *     
  Search from the ELEMENT Environment and Stage using the ELEMENT System and Subsystem  
 
COMPONENT_SEARCH=(ON,2)                                              ELM        ELM        ELM             *      AND        
                                                                     ELM        ELM        COMP            *         
  Search from the ELEMENT Environment and Stage using the ELEMENT System, any subsystem, and then the COMPONENT System and any  subsystem        
 
COMPONENT_SEARCH=(ON,3)                                              ELM        ELM        ELM            ELM   
  Search from the ELEMENT Environment and Stage using the ELEMENT System and Subsystem
 
COMPONENT_SEARCH=(ON,4)                                              ELM        ELM        ELM            ELM     AND        
                                                                     ELM        ELM        COMP           COMP           
  Search from the ELEMENT Environment and Stage using the ELEMENT System and Subsystem and also using COMPONENT System and subsystem.  
 
COMPONENT_SEARCH=(ON,5)                                              ELM        ELM         *               *             
  Search from the ELEMENT Environment and Stage using any System and Subsystem combination 
 
COMPONENT_SEARCH=(ON,6)                                              ELM        ELM         *              ELM               
  Search from the ELEMENT Environment and Stage using any System and the ELEMENT Subsystem  
 
NOTE:    ELEMENT (ELM)  = Program be acted on in the package
              COMPONENT (COMP) = Input Component  
               * = Wildcard