Reading the BOP with Inline Navigation Criteria for the Specified Standard Operation Along with the Associated Consumed Parts
This example shows you how to read the contents of the bill of process (BOP) with inline navigation criteria for the specified standard operation along with the associated consumed parts.
 |
• The same standard operation can exist at multiple levels under different operation holders (process plan, sequence, operation) in the structure. Thus, the same standard operation can have more than one usage links in the structure.
• A valid operation path traverses from the specified standard operation with consumed parts to its immediate parent operation holder, which is not a standard operation.
• Using this request, you can optionally retrieve the consumed parts associated with one or more usages of the same standard operation.
|
Consider a process plan (pp001) structure as below:
pp001
op0010
stdop009
part001
part002
op0040
stdoper0050
stdop009
part003
op0010
stdop009
part001
part002
op0040
stdoper0050
stdop009
part003
The structure consists of two operations op0010 and op0040, and the standard operation stdoper0050 as the child of op0040. A standard operation stdop009 exists under op0010 and stdoper0050 with one or more consumed parts associated with each usage of stdop009.
Here, the valid path for the stdop009 usage under the standard operation, stdoper0050 is the path that traverses from stdop009 to op0040. This is because operation, op0040 is considered as the immediate parent operation holder of stdop009.
The valid path for the stdop009 usage under op0010 is the path that traverses from stdop009 to op0010. This is because operation, op0010 is considered as the immediate parent operation holder of stdop009.
This example demonstrates how you can retrieve the consumed parts part001 and part002 existing under one usage and the consumed part part003 existing under the other usage of the standard operation stdop009. In this example, you can retrieve the associated consumed parts by specifying:
• The OID of the stdop009 standard operation in the request URI.
• Two usage link OIDs that correspond to the valid paths of stdop009 in the request body.
|
|
• The operationPath array parameter is an optional parameter.
• For a given standard operation, you can instead specify a usage path that traverses from the usage to the root of the structure. This too is considered as a valid value that you can specify for a usage link while using this request.
• You can specify one or more usage links of the same standard operation in the request body.
|
Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/MfgProcMgmt/Operations('OR:com.ptc.windchill.mpml.processplan.operation.MPMStandardOperation:200875')/PTC.MfgProcMgmt.GetBOPWithInlineNavCriteria?$expand=ConsumedParts,Components($expand=Components($expand=ConsumedParts))
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"relatedAssemblyNavigationCriteria": {
"ApplyToTopLevelObject": false,
"Name": "Part01",
"UseDefaultForUnresolved": false,
"ApplicationName": "Test1",
"SharedToAll": true,
"HideUnresolvedDependents": true,
"Centricity": true,
"ApplicableType": "PTC.MfgProcMgmt.ProcessPlan",
"ConfigSpecs": [
{
"@odata.type": "#PTC.NavCriteria.WTPartEffectivityDateConfigSpec",
"EffectiveDate": "2021-12-09T23:00:00Z",
"EffectiveContext": null,
"View": "Design",
"Variation1": null,
"Variation2": null
}
],
"Filters": [
{
"Filter": "string"
}
]
},
"processPlanNavigationCriteria": {},
"operationPath": [
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282450",
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282477"
]
}
"relatedAssemblyNavigationCriteria": {
"ApplyToTopLevelObject": false,
"Name": "Part01",
"UseDefaultForUnresolved": false,
"ApplicationName": "Test1",
"SharedToAll": true,
"HideUnresolvedDependents": true,
"Centricity": true,
"ApplicableType": "PTC.MfgProcMgmt.ProcessPlan",
"ConfigSpecs": [
{
"@odata.type": "#PTC.NavCriteria.WTPartEffectivityDateConfigSpec",
"EffectiveDate": "2021-12-09T23:00:00Z",
"EffectiveContext": null,
"View": "Design",
"Variation1": null,
"Variation2": null
}
],
"Filters": [
{
"Filter": "string"
}
]
},
"processPlanNavigationCriteria": {},
"operationPath": [
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282450",
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282477"
]
}
The request returns the bill of process with inline navigation criteria for the stdop009 standard operation. The request also returns the consumed parts part001 and part002 and part003 associated with the corresponding usages of stdop009.