Package wt.part

Class LoadPart

java.lang.Object
wt.part.LoadPart
public class LoadPart extends Object
Creates and persists part objects based on input from a comma seperated value (csv) file. Method names and parameters are defined in csvmapfile.txt. wt.load.StandardLoadService.load reads records from a .csv file and passes the fields in a hashtable to methods defined in this class.

The load methods use a wt.load.StandardLoadService cache to cache part masters and part version objects to improve performance of creating assemblies and updating attrbiutes. The load methods use wt.doc.LoadDoc to retrieve documents, taking advantage of its internal caching.

Supported API: true

Extendable: false

See Also:
  • StandardLoadService
  • LoadValue
  • LoadDoc

  • Method Details

    • createPart

      public static boolean createPart(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Processes the "csvPart" directive in the XML load file. Creates a part object, persists it in the database, checks it out, applies the default attribute values associated with the specified type definition, persists the part, checks it back in, and caches it in the loader's memory.

      Establishes the part as the CURRENT_CONTENT_HOLDER for use by "ContentFile" lines.

      This format cannot add Soft Attributes(IBA). For that see beginCreateWTPart.

      When using wt.load.LoadFromFile to load parts, end items and serial numbered parts, use the following XML format:

      XML Format

      <csvPart handler="wt.part.LoadPart.createPart" >
       <csvuser> created by user </csvuser>
       <csvpartName> part name </csvpartName>
       <csvpartNumber> part number </csvpartNumber>
       <csvtype> assembly mode </csvtype>
       <csvgenericType> generic type </csvgenericType>
       <csvlogicbasePath> logic base path </csvlogicbasePath>
       <csvsource> source </csvsource>
       <csvfolder> folder </csvfolder>
       <csvlifecycle> lifecycle </csvlifecycle>
       <csvview> view </csvview>
       <csvteamTemplate> team template </csvteamTemplate>
       <csvlifecyclestate> lifecycle state </csvlifecyclestate>
       <csvtypedef> typedef </csvtypedef>
       <csvversion> revision </csvversion>
       <csviteration> iteration </csviteration>
       <csvparentContainerPath>parent container path </csvparentContainerPath>
       <csvenditem> end item </csvenditem>
       <csvtraceCode> trace code </csvtraceCode>
       <csvorganizationName> organization name </csvorganizationName>
       <csvorganizationID> organization id </csvorganizationID>
       <csvcreateTimestamp> creation time stamp </csvcreateTimestamp>
       <csvmodifyTimestamp> modification time stamp </csvmodifyTimestamp>
       <csvminRequired> minumin required </csvminRequired>
       <csvmaxAllowed> maximum allowed </csvmaxAllowed>
       <csvdefaultUnit> default unit </csvdefaultUnit>
      </csvPart>

      Tag Definitions

      created by user This tag allows a user other than the user loading the file to be the creator of this part. This value is optional and defaults to the user loading the file.
        
      part name The name of the part. A value is required for this attribute.
        
      part number The number of the part. This value is optional. If a number is provided, a search will be done to locate a part with this number. If a part is found, a new revision/iteration of the part will be created, and if one is not found, a new part will be created. If a number is not provided, a new part will be created and the next system-generated number will be used.
        
      assembly mode The assembly mode for the part. A value is required for this attribute and must be one of the following:

      • separable
      • inseparable
      • component
      generic type The generic type of the part. This tag is optional. If the tag is used and a value specified, the value must be one of the following:

      • standard
      • generic
      • configurable_generic
      • variant
      If the tag is not used or used but left blank, the default value is standard.
        
      logic base path Path to an XML file with the logic base information for a generic or configurable_generic part. The path is given relative to the location of the file in which the attribute is used. This tag is optional, and if not used or used but left blank, there is no logic base information associated with the generic or configurable generic part.
        
      source The source of the part. A value is required for this attribute and must be one of the following:
      • buy
      • make
      • singlesource
        
      folder The full path to the folder in which the part is created, i.e. /Default/Design. This value is optional and will default to /Default. An error message that this is a required field may appear if left blank, but this message can be ignored.
        
      lifecycle The lifecycle that the part will be created under. This value is optional and defaults to Basic.
        
      view The view that the part will be created under, i.e. Design, Manufacturing. This value is optional. Leave this value blank for serial numbered parts.
        
      team template The team template that the part will be created under. This value is optional and defaults to no team template being associated with the part.
        
      lifecycle state The lifecycle state that the created part will be in. This value is optional and defaults to the initial state of the lifecycle that the part is created under.
        
      typedef This contains the identifier string of a com.ptc.core.meta.common.TypeIdentifier.

      i.e. wt.part.WTPart|com.mycompany.SoftPart2

      This would create a soft typed part. This currently supports the following modeled types:

      • wt.part.WTPart

      This currently does not handle custom modeled types. If there is a need for one of these, then a custom loader needs to be created.

      This value is optional and defaults to wt.part.WTPart.

        
      version The revision of the part. This value is optional and defaults to the latest revision of the part.
        
      iteration The iteration of the part. This value is optional and defaults to the next iteration of the revision of the part.
        
      parent container path DEPRECATED. This property is ignored, although the tag is still required. Instead the parent container is obtained from the CONT_PATH command line argument when running wt.load.LoadFromFile, or from the Load Set data.
        
      end item Whether the part will be created as an end item or not. This tag is optional. The default is that the item is not created as an end item. To create the part as an end item, use this tag and set the value to yes.
        
      trace code The trace code for the part. This tag is optional. If the tag is used and a value specified, the value must be one of the following:

      • O
      • L
      • S
      • X
      These stand for Untraced, Lot, Serial Number, and Lot/Serial Number, respectively.

      If the tag is not used or used but left blank, the default value is O, or Untraced.

        
      organization name The name of the organization that the part will be created under. This is also the organization in which a search for the part will occur if a part number is specified. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.
        
      organization id The id of the organization that the part will be created under. This is also the organization in which a search for the part will occur if a part number is specified. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.
        
      creation time stamp The creation time stamp for the part. This tag is optional and defaults to the modification time stamp, if that value is set, or to the current system time if neither the creation nor modification time stamps are set.
        
      modification time stamp The modification time stamp for the part. This tag is optional and defaults to the creation time stamp, if that value is set, or to the current system time if neither the creation nor modification time stamps are set.
        
      minimum required Minimum number of children to be present to have a valid configuration
      maximum allowed Maximum number of children to be present to have a valid configuration
      part default unit The default unit for the part. This tag is optional and defaults to each. Valid values are ea, kg, m, l, sq_m, cu_m, as_needed.

      Revisions and Iterations

      This method supports a part to being created at a specified revision and iteration. Multiple part revisions imply an "order", i.e. subsequent bulk load runs can "fill in the gaps", but it does so by attaching to the latest iteration of the previous revision. If a newer iteration is added to the previous revision, the new revision will attached to the new latest iteration. For example: Load set 1 (E.1, A.1, C.2) will result in (A.1, C.2, E.1). The predecssors of: C.2 is A.1, E.1 is C.2. Load set 2 (B.1, A.2., C.1, C.3) will result in (A.1, A.2, B.1, C.1, C.2, C.3, E.1). The predecessors of: B.1 is A.2, C.1 is B.1, E.1 is C.3. Any new revision/iterations added will continue to change the predecessor links to the new latest iteration of the previous revision.

      Gaps in the ordering ARE supported.

      Examples of valid revisions/iterations are: (A.1,A.3,B.2,B.5,E.4,E.5)

      NOTE TO USERS OF THE SOURCE CODE: The ability to load part revisions out of order is implemented by using the VersionControlHelper.service.insertNode() method. Calls to this method must not be removed from the code. To turn off this behavior, you should instead set the insert_on_latest_iteration flag to false in the constructPart() method.

      When loading a revision out of sequence and loading relationships to those parts there are a few things that you should understand while ordering your data.

      1. Relationships are copied forward from what is identified as the predecessor to the new revision. So in an ordered case if you create part 1 A.1 that has references or a describe relationship to doc 2. Then you revise to get part 1 B.1, it will have the relationships of A.1 copied to it so it will have the relationship to doc 2 as well.

      2. Relationships are not copied forward if they are created after the new revision has already been created. For example if part 1 A.1 and B.1 are created and then part A.1 has a relationship created to doc 2, part 1 B.1 will not have the relationship to doc 2 copied to it. You must explicitely create that relationship if you want it created.

      3. Relationships from predecessors are not cumulative. This is really just a further clarification of the first point. Relationships are only copied from the one identified predecessor and not the accumulation of predecessors. So if you create part 1 B.1 that is related to doc 2, create part 1 A.1 that is related to doc 3 and then create part 1 C.1 it will inherit the relationship to doc 2 only.

      These are just a few pointers to loading revisions and relationships out of sequence. There are other scenarios given these basic rules that can also be imagined. So order the creation of revisions/iterations and relationship very carefully to get the results that you intend.



      Supported API: true

      Extendable: false

      Parameters:
      nv - Name/Value pairs of part attributes.
      cmd_line - command line argument that can contain supplemental load data
      return_objects - Vector of the object(s) created by this method. Used by wt.load.StandardLoadService for accurate user feedback messages.
      Returns:
      truesuccess
      falsefailure

    • beginCreateWTPart

      public static boolean beginCreateWTPart(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Processes the "csvBeginWTPart" directive in the XML load file.

      Creates a part object, persists it in the database, checks it out, applies the default attribute values associated with the specified type definition, persists the part, checks it back in, and caches it in the loader's memory.

      If a part with this number already exists, the part is looked up and a new iteration of the latest revision is created, unless the revision/iteration are specified using attributes in the the load file.

      Establishes the part as the CURRENT_CONTENT_HOLDER for use by "ContentFile" lines.

      When using wt.load.LoadFromFile to load parts, end items and serial numbered parts, use the following XML format:

      XML Format

      <csvBeginWTPart handler="wt.part.LoadPart.beginCreateWTPart" >
       <csvuser> created by user </csvuser>
       <csvpartName> part name </csvpartName>
       <csvpartNumber> part number </csvpartNumber>
       <csvtype> assembly mode </csvtype>
       <csvgenericType> generic type </csvgenericType>
       <csvlogicbasePath> logic base path </csvlogicbasePath>
       <csvsource> source </csvsource>
       <csvfolder> folder </csvfolder>
       <csvlifecycle> lifecycle </csvlifecycle>
       <csvview> view </csvview>
       <csvteamTemplate> team template </csvteamTemplate>
       <csvlifecyclestate> lifecycle state </csvlifecyclestate>
       <csvtypedef> typedef </csvtypedef>
       <csvversion> revision </csvversion>
       <csviteration> iteration </csviteration>
       <csvenditem> end item </csvenditem>
       <csvtraceCode> trace code </csvtraceCode>
       <csvorganizationName> organization name </csvorganizationName>
       <csvorganizationID> organization id </csvorganizationID>
       <csvcreateTimestamp> creation time stamp </csvcreateTimestamp>
       <csvmodifyTimestamp> modification time stamp </csvmodifyTimestamp>
       <csvminRequired> minimum required </csvminRequired>
       <csvmaxAllowed> maximum allowed</csvmaxAllowed>
       <csvdefaultUnit> part default unit </csvdefaultUnit>
      </csvBeginWTPart >
       
      <csvIBAValue handler="wt.iba.value.service.LoadValue.createIBAValue" >
       ...
      </csvIBAValue >
       
      <csvIBAValue handler="wt.iba.value.service.LoadValue.createIBAValue" >
       ...
      </csvIBAValue >
       
      <csvIBAValue handler="wt.iba.value.service.LoadValue.createIBAValue" >
       ...
      </csvIBAValue >
       
      <csvIBAValue handler="wt.iba.value.service.LoadValue.createIBAValue" >
       ...
      </csvIBAValue >
       
      <csvEndWTPart handler="wt.part.LoadPart.endCreateWTPart" >
       ...
      </csvEndWTPart >

      Tag Definitions

        
      created by user This tag allows a user other than the user loading the file to be the creator of this part. This value is optional and defaults to the user loading the file.
        
      part name The name of the part. A value is required for this attribute.
        
      part number The number of the part. This value is optional. If a number is provided, a search will be done to locate a part with this number. If a part is found, a new revision/iteration of the part will be created, and if one is not found, a new part will be created. If a number is not provided, a new part will be created and the next system-generated number will be used.
        
      assembly mode The assembly mode for the part. A value is required for this attribute and must be one of the following:

      • separable
      • inseparable
      • component
      generic type The generic type of the part. This tag is optional. If the tag is used and a value specified, the value must be one of the following:

      • standard
      • generic
      • configurable_generic
      • variant
      If the tag is not used or used but left blank, the default value is standard.
        
      logic base path Path to an XML file with the logic base information for a generic or configurable_generic part. The path is given relative to the location of the file in which the attribute is used. This tag is optional, and if not used or used but left blank, there is no logic base information associated with the generic or configurable generic part.
        
      source The source of the part. A value is required for this attribute and must be one of the following:
      • buy
      • make
      • singlesource
        
      folder The full path to the folder in which the part is created, i.e. /Default/Design. This value is optional and will default to /Default. An error message that this is a required field may appear if left blank, but this message can be ignored.
        
      lifecycle The lifecycle that the part will be created under. This value is optional and defaults to Basic.
        
      view The view that the part will be created under, i.e. Design, Manufacturing. This value is optional. Leave this value blank for serial numbered parts.
        
      team template The team template that the part will be created under. This value is optional and defaults to no team template being associated with the part.
        
      lifecycle state The lifecycle state that the created part will be in. This value is optional and defaults to the initial state of the lifecycle that the part is created under.
        
      typedef This contains the identifier string of a com.ptc.core.meta.common.TypeIdentifier.

      i.e. wt.part.WTPart|com.mycompany.SoftPart2

      This would create a soft typed part. This currently supports the following modeled types:

      • wt.part.WTPart

      This currently does not handle custom modeled types. If there is a need for one of these, then a custom loader needs to be created.

      This value is optional and defaults to wt.part.WTPart.

        
      revision The revision of the part. This value is optional and defaults to the latest revision of the part.
        
      iteration The iteration of the part. This value is optional and defaults to the next iteration of the revision of the part.
        
      end item Whether the part will be created as an end item or not. This tag is optional. The default is that the item is not created as an end item. To create the part as an end item, use this tag and set the value to yes.
        
      trace code The trace code for the part. This tag is optional. If the tag is used and a value specified, the value must be one of the following:

      • O
      • L
      • S
      • X
      These stand for Untraced, Lot, Serial Number, and Lot/Serial Number, respectively.

      If the tag is not used or used but left blank, the default value is O, or Untraced.

        
      organization name The name of the organization that the part will be created under. This is also the organization in which a search for the part will occur if a part number is specified. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.
        
      organization id The id of the organization that the part will be created under. This is also the organization in which a search for the part will occur if a part number is specified. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.
        
      creation time stamp The creation time stamp for the part. This tag is optional and defaults to the modification time stamp, if that value is set, or to the current system time if neither the creation nor modification time stamps are set.
        
      modification time stamp The modification time stamp for the part. This tag is optional and defaults to the creation time stamp, if that value is set, or to the current system time if neither the creation nor modification time stamps are set.
        
      minimum required Minimum number of children to be present to have a valid configuration
      maximum allowed Maximum number of children to be present to have a valid configuration
      part default unit The default unit for the part. This tag is optional and defaults to each. Valid values are ea, kg, m, l, sq_m, cu_m, as_needed.

      Revisions and Iterations

      This method supports a part to being created at a specified revision and iteration. Multiple part revisions imply an "order", i.e. subsequent bulk load runs can "fill in the gaps", but it does so by attaching to the latest iteration of the previous revision. If a newer iteration is added to the previous revision, the new revision will attached to the new latest iteration. For example: Load set 1 (E.1, A.1, C.2) will result in (A.1, C.2, E.1). The predecssors of: C.2 is A.1, E.1 is C.2. Load set 2 (B.1, A.2., C.1, C.3) will result in (A.1, A.2, B.1, C.1, C.2, C.3, E.1). The predecessors of: B.1 is A.2, C.1 is B.1, E.1 is C.3. Any new revision/iterations added will continue to change the predecessor links to the new latest iteration of the previous revision.

      Gaps in the ordering ARE supported.

      Examples of valid revisions/iterations are: (A.1,A.3,B.2,B.5,E.4,E.5)

      NOTE TO USERS OF THE SOURCE CODE: The ability to load part revisions out of order is implemented by using the VersionControlHelper.service.insertNode() method. Calls to this method must not be removed from the code. To turn off this behavior, you should instead set the insert_on_latest_iteration flag to false in the constructPart() method.

      When loading a revision out of sequence and loading relationships to those parts there are a few things that you should understand while ordering your data.

      1. Relationships are copied forward from what is identified as the predecessor to the new revision. So in an ordered case if you create part 1 A.1 that has references or a describe relationship to doc 2. Then you revise to get part 1 B.1, it will have the relationships of A.1 copied to it so it will have the relationship to doc 2 as well.

      2. Relationships are not copied forward if they are created after the new revision has already been created. For example if part 1 A.1 and B.1 are created and then part A.1 has a relationship created to doc 2, part 1 B.1 will not have the relationship to doc 2 copied to it. You must explicitely create that relationship if you want it created.

      3. Relationships from predecessors are not cumulative. This is really just a further clarification of the first point. Relationships are only copied from the one identified predecessor and not the accumulation of predecessors. So if you create part 1 B.1 that is related to doc 2, create part 1 A.1 that is related to doc 3 and then create part 1 C.1 it will inherit the relationship to doc 2 only.

      These are just a few pointers to loading revisions and relationships out of sequence. There are other scenarios given these basic rules that can also be imagined. So order the creation of revisions/iterations and relationship very carefully to get the results that you intend.



      Supported API: true

      Extendable: false

      Parameters:
      nv - Name/Value pairs of part attributes.
      cmd_line - command line argument that can contain supplemental load data
      return_objects - Vector of the object(s) created by this method. Used by wt.load.StandardLoadService for accurate user feedback messages.
      Returns:
      truesuccess
      falsefailure
      See Also:

    • endCreateWTPart

      public static boolean endCreateWTPart(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Processes the "EndWTPart" directive in the csv load file. Causes the cached part to be checked-out, associates soft attribues from preceding IBAValue load file lines with the part, applies the default attribute values associated with the specified type definition, persists the part, checks it back in, and caches it in the loader's memory.

      Establishes the part as the CURRENT_CONTENT_HOLDER for use by "ContentFile" lines.

      XML Format

      <csvEndWTPart handler="wt.part.LoadPart.endCreateWTPart" >
       <csvparentContainerPath > parent container path </csvparentContainerPath >
      </csvEndWTPart >

      Tag Definitions

      parent container path DEPRECATED. This property is ignored, although the tag is still required. Instead the parent container is obtained from the CONT_PATH command line argument when running wt.load.LoadFromFile, or from the Load Set data.
      Supported API: true

      Extendable: false
      Parameters:
      nv - not used
      cmd_line - command line argument that can contain supplemental load data
      return_objects - Vector of the object(s) created by this method. Used by wt.load.StandardLoadService for accurate user feedback messages.
      See Also:

    • createNewViewVersion

      public static boolean createNewViewVersion(Hashtable nv, Hashtable cmd_line, Vector return_objects) throws WTException
      Processes the "NewViewVersion" directive in the csv load file.

      Creates a new revision of a part from an existing part and assigns it to the specified view (and optionally variations if they are enabled). The new view must be a child view of the view the original was assigned to (or if view variations are enabled it can be a sibling view or the same view with different variations). For example, the part could have been created in the Design view, and this method can be used to create a new revision of the part in the Manufacturing view.

      When using wt.load.LoadFromFile to create a new view version of a part, use the following XML format:

      XML Format

      <csvNewViewVersion handler="wt.part.LoadPart.createNewViewVersion" >
       <csvpartName> part name </csvpartName>
       <csvpartNumber> part number </csvpartNumber>
       <csvpartVersion> part revision </csvpartVersion>
       <csvpartIteration> part iteration </csvpartIteration>
       <csvpartView> part view </csvpartView>
       <csvpartVariation1> part variation1 </csvpartVariation1>
       <csvpartVariation2> part variation2 </csvpartVariation2>
       <csvtype> assembly mode </csvtype>
       <csvgenericType> generic type </csvgenericType>
       <csvlogicbasePath> logic base path </csvlogicbasePath>
       <csvsource> source </csvsource>
       <csvfolder> folder </csvfolder>
       <csvlifecycle> lifecycle </csvlifecycle>
       <csvview> view </csvview>
       <csvvariation1> variation1 </csvvariation1>
       <csvvariation2> variation2 </csvvariation2>
       <csvteamTemplate> team template </csvteamTemplate>
       <csvlifecyclestate> lifecycle state </csvlifecyclestate>
       <csvtypedef> typedef </csvtypedef>
       <csvversion> revision </csvversion>
       <csviteration> iteration </csviteration>
       <csvparentContainerPath>parent container path </csvparentContainerPath>
       <csvorganizationName> organization name </csvorganizationName>
       <csvorganizationID> organization id </csvorganizationID>
      </csvNewViewVersion>

      Tag Definitions

      part name The name of the part. This value is ignored, although the tag is required. The name used for the part in the new view is the same as the original part name.
        
      part number The number of the part. A value is required for this attribute and must be the number of the part for which a new view version is being created.
        
      part revision The revision of the existing part to locate and create the new view version from. This value is optional and defaults to the latest revision of the part.
        
      part iteration The iteration of the existing part to locate and create the new view version from. This value is optional and defaults to the latest iteration of the revision of the part.
        
      part view The view of the existing part to locate and create the new view version from. This value is optional and defaults to the an ancestor view of the new "view" passed in.
        
      part variation1 The variation1 of the existing part to locate and create the new view version from. This value is optional and defaults to null.
        
      part variation2 The variation2 of the existing part to locate and create the new view version from. This value is optional and defaults to null.
        
      assembly mode The assembly mode for the new part version. A value is required for this attribute and must be one of the following:

      • separable
      • inseparable
      • component
      generic type The generic type of the new part. This tag is optional. If the tag is used and a value specified, the value must be one of the following:

      • standard
      • generic
      • configurable_generic
      • variant
      If the tag is not used or used but left blank, the default value is standard.
        
      logic base path Path to an XML file with the logic base information for a generic or configurable_generic part. The path is given relative to the location of the file in which the attribute is used. This tag is optional, and if not used or used but left blank, there is no logic base information associated with the generic or configurable generic part.
        
      source The source of the new part version. A value is required for this attribute and must be one of the following:
      • buy
      • make
      • singlesource
        
      folder The full path to the folder in which the new part version is created, i.e. /Default/Design. This value is optional and will default to /Default. An error message that this is a required field may appear if left blank, but this message can be ignored.
        
      lifecycle The lifecycle that the new part version will be created under. This value is optional and defaults to Basic.
        
      view The view that the new part version will be created under, i.e. Design, Manufacturing. This value is optional. Leave this value blank for serial numbered parts.
        
      variation1 The variation1 that the new part version will be created with. This value is optional and will default to null.
        
      variation2 The variation2 that the new part version will be created with. This value is optional and will default to null.
        
      team template The team template that the new part version will be created under. This value is optional and defaults to no team template being associated with the part.
        
      lifecycle state The lifecycle state that the new part version will be in. This value is optional and defaults to the initial state of the lifecycle that the part is created under.
        
      typedef This contains the identifier string of a com.ptc.core.meta.common.TypeIdentifier.

      i.e. wt.part.WTPart|com.mycompany.SoftPart2

      This would create a soft typed part. This currently supports the following modeled types:

      • wt.part.WTPart

      This currently does not handle custom modeled types. If there is a need for one of these, then a custom loader needs to be created.

      This value is optional and defaults to wt.part.WTPart.

        
      version The revision of the new part. This value is optional and defaults to the next revision of the part.
        
      iteration The iteration of the new part revision. This value is optional and defaults to the next iteration of the new revision of the part.
        
      parent container path DEPRECATED. This property is ignored, although the tag is still required. Instead the parent container is obtained from the CONT_PATH command line argument when running wt.load.LoadFromFile, or from the Load Set data.
        
      organization name The name of the organization that will be searched for the part to create the new view version from. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.
        
      organization id The id of the organization that will be searched for the part to create the new view version from. This tag is optional and defaults to the organization determined by the command line argument CONT_PATH.


      Supported API: true

      Extendable: false
      Parameters:
      nv - Name/Value pairs of part attributes.
      cmd_line - command line argument that can contain supplemental load data
      return_objects - Vector of the object(s) created by this method.
      Throws:
      WTException

    • createProductSerialNumberEffectivity

      public static boolean createProductSerialNumberEffectivity(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Creates Product/Active Serial number effectivity specified on a target, using load files.

      Supported API: true
      Parameters:
      nv -
      cmd_line -
      return_objects -
      Returns:
      true when load effectivities was successful without any error otherwise false

    • createProductLotNumberEffectivity

      public static boolean createProductLotNumberEffectivity(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Creates Product/Active Lot number effectivity specified on a target, using load files.

      Supported API: true
      Parameters:
      nv -
      cmd_line -
      return_objects -
      Returns:
      true when load effectivities was successful without any error otherwise false

    • createProductMSNEffectivity

      public static boolean createProductMSNEffectivity(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Creates Product/Active MSN effectivity specified on a target, using load files.

      Supported API: true
      Parameters:
      nv -
      cmd_line -
      return_objects -
      Returns:
      true when load effectivities was successful without any error otherwise false

    • createProductBlockEffectivity

      public static boolean createProductBlockEffectivity(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Creates Product/Active Block effectivity specified on a target, using load files.

      Supported API: true
      Parameters:
      nv -
      cmd_line -
      return_objects -
      Returns:
      true when load effectivities was successful without any error otherwise false

    • createProductDateEffectivity

      public static boolean createProductDateEffectivity(Hashtable nv, Hashtable cmd_line, Vector return_objects)
      Creates Product/Active Date effectivity specified on a target ,using load files.

      Supported API: true
      Parameters:
      nv -
      cmd_line -
      return_objects -
      Returns:
      true when load effectivities was successful without any error otherwise false

    • getPartMaster

      public static WTPartMaster getPartMaster(String partNumber)
      Queries WTPartMaster table for effectivity context for given part number

      Supported API: true
      Parameters:
      partNumber - :- Number of the part whose Master is required
      Returns:
      WTPartMaster as effectivity context, if exists in system.