Managing WTPart Data Model with Attributes governed by SAP
We are currently planning for WTParts and we are trying to figure out how to manage attributes that are to be governed in SAP.
Our Current Workflow
- Finished Goods (End Items) meetings are held to discuss necessary attributes to be entered into SAP
- An Administrator fills out a spreadsheet with the required new finished goods. Sometimes there can be dozens of finished goods at once (even hundreds).
- The spreadsheet is sent to the SAP team for SAP import and part creation.
Windchill Implementation Assumptions
- Windchill/SAP Integration will be custom, 1 way (still to be developed)
- Some of the attributes for a Finished Good should not be managed in the WTPart, as they should be governed by SAP and any changes in SAP will cause a disconnect with the data in Windchill (due to the custom 1 way SAP Integration).
- We will be converting the current process from Excel and Email to Windchill. All attributes that were sent through Excel will be sent through Windchill.
- Windchill users will never want or need to see these attributes in Windchill
Proposed Worflows
- Option 1
-
Create multiple WTParts at once with the 'New Multiple Parts' tool, with ALL the attributes that will be governed in Windchill & SAP
-All tables and views will not show the SAP attributes -
A change will be created where the process workflow will send the attributes to SAP
-
-
Concern 1
-
A user can add any attribute at any time, to their table view and see the wrong data in Windchill.
-
-
Option 2
-
Create multiple WTParts at once with the 'New Multiple Parts' tool, with ALL the attributes that will be governed in Windchill & SAP
-All tables and views will not show the SAP attributes -
A change will be created where the process workflow will send the attributes to SAP and the workflow would change the SAP attribute to a Value of N/A
-
-
Concern 2
-
The workflow and wtpart editing method/process is unclear and may not be feasible or preferred for unknown data reasons.
-
Questions (Finally 😕)
- How do other companies predominantly handle attributes that should be governed in SAP?
- Are any of the proposed workflows doable or recommended?
- Should any of our assumptions be changed?
- On the flip-side, if we have attributes that we want only in Windchill, but not SAP - how can we modify those Windchill attributes that won't affect downstream teams and vendors.

