TAL a Part-to-Part Relationship Bundle
In addition to bundles published from the content authored in Windchill Service Information Manager, you can also TAL bundles containing third party content, such as part-to-part relationships.
Part-to-part relationships are contained in SAP bundles. This type of bundle does not require any special handling. A bundle contains a manifest file named BUNDLE.mf. PTC Arbortext Content Delivery can recognize an SAP bundle from the information in that file and TAL the bundle accordingly.
Following is an excerpt from the BUNDLE.mf file that identifies an SAP bundle:
Bundle-Id: SAP-000001
Bundle-Category: SAP
Bundle-type: full
Bundle-Version: 1.0
Bundle-source: SAP
Bundle-Publish-Date: 11/24/2021 08:00:00
family-Name: All
Contents: associatedParts.dat relatedParts.dat
The Bundle-Category setting in the file identifies this as an SAP bundle.
Configuring Part Relations
To configure part relations for third party content in an SAP bundle, you must add a file named relatedParts.dat to the bundle. That file must contain a series of lines that provide the required information for the part relationship.
The below structure is followed for defining the parts relation:
structure:source part | organization name | relationship | organization name | target part | creation date | modification date | type | load action
You can define the following relationships:
• Supersession — supersession
• xref — cross reference
• alternate — alternate
The following load actions can be performed:
• DEFAULT
• UPDATE
• DELETE
Organization name should be taken from IS bundle PublishInfo.xml, field orgName
The following is the example of part relation from this file:
0000019474 AMP_Org supersession AMP_Org 0000014770 [...]
The following parts of the line define the part relationship:
• 0000019474 — the source part
• AMP_Org — the organization name
• supersession — the part relationship
• 0000014770 — the target part
When you load the bundle containing the relatedParts.dat file, the specified part relationships appear in the user interface.
Configuring Part Reference
To configure part references for third party content in an SAP bundle, you must add a file namedreferencePart.dat to the bundle. That file must contain a series of lines that provide the required information for the part references.
The below structure is followed for defining the parts relation:
structure :- AGGREGATEDTIMESTAMP | DATASOURCE | HASALTERNATES (not required, empty space|tab) | HASSUPERSESSION(not required, empty space|tab) | HASXREF (not required, empty space|tab)| orgName | PARTNAME | objNumber | SERVICEABLE (1=true) | SOURCENAME | DOMAINPATH (not required, empty tab) | CREATEDDATE | MODIFIEDDATE |TYPE |SOURCEDESCRIPTION (not required, empty space|tab) | SOURCEIDENTIFIER (not required, empty spacde|tab) | EXTRACTSESSIONID (can be whatever number) | LOADACTION
Following is an example of the part reference from this file:
KM246785 Org supersession Org KM246785-2 24-NOV-21 04.34.24.2770410 PM GMT 24-NOV-21 04.34.24.2770410 PM GMT com.ptc.sc.parts.SCSupersededPart DEFAULT
For CSV bundles, part relationships are defined n the
part_relations.csv file. Refer to
CSV File Format for more information about this file.