Reading the BOP for the Specified Standard Operation Along with the Associated Standalone and In Context SCCs
This example shows how to read the contents of the bill of process for the specified standard operation along with the associated standalone and In Context SCCs.
 |
• An operationPath parameter is required for retrieving an In Context SCC object associated with a standard operation, a standard buy-off operation, or a standard data collection operation.
• For retrieving an In Context SCC object associated with a standard operation usage, a valid operation path traverses from its immediate parent operation holder to the standard operation usage.
Alternatively, a valid operation path is the usage link that exists between the standard operation usage and its immediate parent operation holder in the structure.
• The same standard operation usage and its associated SCCs can exist at multiple levels under different operation holders in a structure.
To retrieve an In Context SCC object associated with a given standard operation usage in the structure, you can provide only the valid operation path of the standard operation usage, as the value of the operationPath attribute.
|
Consider a process plan (PP001) structure as below:
PP001
op0010
stdop009
SCC002
SCC001
op0040
stdop009
SCC003
SCC001
op0010
stdop009
SCC002
SCC001
op0040
stdop009
SCC003
SCC001
The structure consists of two operations op0010 and op0040. The same standard operation stdop009 exists under both op0010 and op0040 with consumed SCCs associated with it.
• SCC001 is a standalone SCC directly associated with stdop009.
• SCC002 and SCC003 are In Context SCCs, each associated with its corresponding stdop009 usage existing in different contexts.
◦ SCC002 is associated with the stdop009 usage in context of operation op0010.
The valid operation path for the stdop009 usage in context of operation op0010 is the path that traverses from op0010 to stdop009 as operation op0010 is the immediate parent operation holder of stdop009.
◦ SCC003 is associated with the stdop009 usage in context of operation op0040.
The valid operation path for the stdop009 usage in context of operation op0040 is the path that traverses from op0040 to stdop009 as operation op0040 is the immediate parent operation holder of stdop009.
The following example demonstrates how you can retrieve the standalone SCC001 and In Context SCC002 associated with stdop009 in context of operation op0010.
You can retrieve the In Context SCC002 by specifying the usage link OID that corresponds to the valid operation path of stdop009 in context of operation op0010, 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:302009')/PTC.MfgProcMgmt.GetBOP?$expand=Components($levels=max;$expand=ConsumedStandardCCs($expand=OperationToStandardCCLink,StandardCC))
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
{
"processPlanNavigationCriteriaId" : "OR:wt.filter.NavigationCriteria:48796487",
"relatedAssemblyNavigationCriteriaId" : "OR:wt.filter.NavigationCriteria:48796488",
"operationPath": [
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282498"
]
}
"processPlanNavigationCriteriaId" : "OR:wt.filter.NavigationCriteria:48796487",
"relatedAssemblyNavigationCriteriaId" : "OR:wt.filter.NavigationCriteria:48796488",
"operationPath": [
"OR:com.ptc.windchill.mpml.processplan.operation.MPMOperationUsageLink:282498"
]
}
The request returns the bill of process for the specified standard operation along with the standalone SCC001 and In Context SCC002 associated with the stdop009 usage in context of operation op0010.
|
|
Similarly, you can retrieve the standalone and In Context SCCs associated with a standard buy-off operation or a standard data collection operation using the corresponding request URI with the request body.
|