[Statements are taken from PLM XML/ TC XML Export Import Administration PDF]
PLMXML for a standard PLM XML import or export i.e Between Teamcneter Unified sites and non Teamcenter sites
TC XML if you are using Data Exchange to move data between Teamcenter and Teamcenter Enterprise sites.
PLMXML for a standard PLM XML import or export i.e Between Teamcneter Unified sites and non Teamcenter sites
TC XML if you are using Data Exchange to move data between Teamcenter and Teamcenter Enterprise sites.
Transfer mode objects are created in PLM XML/TC XML Export Import Administration and are displayed as options when users import or export objects or system data using one of the Teamcenter applications.
They allow users to export and import data with little knowledge other than the name of the transfer mode object that they should use; for example, ToCompanyA, FromCompanyB,
They allow users to export and import data with little knowledge other than the name of the transfer mode object that they should use; for example, ToCompanyA, FromCompanyB,
or ToCompanyB.
Transfer mode objects are made up of the following items that configure the import or export operation.
• Closure rules
Define the scope of the data translation.
• Filter rules
Use conditions to apply a finer level of control over which data gets translated
along with the primary objects.
• Action rules
Sets of methods that can be called before, during, and after the translation.
• Property sets
Provide a mechanism for PLM XML objects to have arbitrary properties in the form of UserData elements.
Managing closure rules
Closure rules control the scope of the data translation on both input and output.
They specify how the data structure is traversed by specifying which relationships are of interest and what should be done when these relationships are encountered.
Closure rules are comprised of five parts: primary object selector, secondary object selector, relation selector, action, and an optional conditional clause. Closure rules generally come in sets. The closure rule clauses are evaluated in order for each target object. The first applicable rule determines the disposition of the related object.
A rule is applicable only if the target object fits the primary selector, the secondary object fits the secondary selector, the relationship between the two objects fits the relationship selector, and the conditional clause evaluates to TRUE. The action
of the applicable closure rule clause determines how the translator handles the secondary object.
If no rule applies, the object is skipped. If the action is TRAVERSE, the object becomes another target of the translation. If the action is PROCESS, the secondary object is written (into either PLM XML or the Teamcenter database), but no closure rule clauses are applied to the secondary object’s related objects. If the action is
SKIP, nothing is done with the object.
IMPORT EXPORT ITK API Sample refer link
how to revise the item revision through custm handlers TC 11.2
ReplyDeleteYou need to use TCTYPE_create_object API to create the new item revision from existing item revision
ReplyDeleteis there an code for the document example?
ReplyDelete"if the item revision has a UGMASTER dataset, translate it and skip all other datasets; if there is no UGMASTER dataset, export the JT dataset"
While plmxml export listing all the transfer mode in plmxml export window,is there any possibilities to display only required transfer mode can show.
ReplyDeleteHow to get closure rules using using PIE_find_closure_rules2, the second argument is creating problem while linking in BMIDE. I am directly using "PIE_TEAMCENTER", is there anything i am missing?
ReplyDeleteHi Shaffin,
DeleteWere you able to fix this issue? I am also facing the same issue.
Can I export BOM in xml file using TCXml utility?
ReplyDelete