Removing Multiple Made From Associations
A Made From association (Made From Link) exists between a revision of parent finished part or Made From Set and the main Made From Part associated with it.
You can remove single or multiple Made From Parts (Raw Materials) associated with single or multiple finished parts or Made From Sets by specifying the finished part or Made From Set OIDs and the Made From Part OIDs in the request body.
You must have Modify permissions to the Made From Parts and to the finished part or Made From Set for which you want to remove the Made From Parts.
|
|
• When you remove a Made From Link, only the link between the specified revision of a finished part or Made From Set object and the specified Made From Part is removed.
◦ The Made From Links between other revisions of the same finished part or Made From Set object and the same Made From object are not removed.
• The parent finished part or Made From Set object is not iterated when the associated Made From Part is removed.
|
You can also choose to remove the Made From Parts in the context of Change (change task or change notice). You must first reserve the Change object for Edit. You must have Modify permissions to the Change object and Manufacturing History objects.
|
|
• When the Track “Made From” History Through Change Notice preference is set to Yes, you must specify the ChangeOid attribute and its value.
• When the preference is set to Yes, Manufacturing History Objects are added in the UI in the Resulting Objects table of the Change object specified in the ChangeOid attribute value.
|
Example: Removing Made From Parts Associated with Multiple Finished Parts
This example shows you how to remove two Made From Parts each associated with two different finished part objects. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/BomTransformation/RemoveMadeFromAssociations
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"MadeFromAssociations": [
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:114532')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:172827')"
},
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:115467')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:172477')"
}
]
}
Similarly, you can remove Made From Parts associated with different Made From Set objects by specifying the Made From Set OIDs in the request body.
Example: Removing Made From Parts Associated with the Same Finished Part Object
This example shows you how to remove two Made From Parts each associated with the same finished part object. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/BomTransformation/RemoveMadeFromAssociations
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"MadeFromAssociations": [
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:114542')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:172927')"
},
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:114542')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:172486')"
}
]
}
Similarly, you can remove Made From Parts associated with the same Made From Set object by specifying the Made From Set OID in the request body.
Example: Removing Multiple Made From Links with “ChangeOid” Specified
This example shows you how to remove two Made From Links for the same finished part in the context of Change. In this example, the Track “Made From” History Through Change Notice preference is set to Yes. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/BomTransformation/RemoveMadeFromAssociations
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"MadeFromAssociations": [
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:194093')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:194168')"
},
{
"Makes@odata.bind": "Parts('OR:wt.part.WTPart:194093')",
"MadeFrom@odata.bind": "Parts('VR:wt.part.WTPart:194972')"
}
],
"ChangeOid": "VR:wt.change2.WTChangeOrder2:196476"
}
The request adds the parent finished part and the Manufacturing History objects in the Resulting Objects table of the Change object specified in ChangeOid.
