1. St. Jude Medical IncSt. Jude Medical Inc
Windchill and SAPWindchill and SAP
IntegrationIntegration
10.2MO30

2. 2nd
Phase Success story
• 2nd
Phase success story board.
• 2nd
Phase went Go-Line on june-2014.
• Part, BOM and ECN are successfully published.
• Still now no Windchill and SAP integration errors.
• ZERO errors as of now.

3. Windchill ESI case study
• Web Services – Part Number
• SAP is the master system for part numbers
• If “PLM Only” is selected as “No” or blank a SAP Part number will be retrieved
during part creation from SAP using the object initialization rules of part
type.
• Object Initialization Rules (OIR) in Windchill will be used to fetch the part
number from SAP during the part creation process in Windchill
• Based on the “PLM_only” attribute value to “No”, the rule will invoke a SOAP
call to a TIBCO process to fetch SAP part number.
• Created new log service for part Number generator in Tibco.

4. Windchill ESI case study
• Auto Assign Plants ( DTs) to Parts and BOM based SJM requirements.
• Object filtered to publish to SAP which are PLM only “No”.
• Tibco will allow to publish SELECTED Parts only.
• Some of the parts and BOMs are filtered out based on Material Type.
• Tibco prevented to publish some of Parts and some of BOMs to SAP.
• Republishing same ECN multiple times to SAP.
• Windchill ESI service is republishing same ECN again and again to SAP with
new Date Effectivity.
• Tibco Reset ECN effectivity date in SAP if ECN is changed ECN.

5. Windchill ESI case study
• More Part custom attributes published to SAP
• More BOM custom attributes published to SAP
• Windchill publishing EBOM , MBOM and PBOM to SAP.

6. Windchill ESI case study
• Automatic Assign Distribution Targets
• Windchill ESI services automatically assign the distribution Targets to Parts
based on Part type.
• Auto Publish Parts and BOMs to SAP
• Windchill ESI service automatically publish Parts and BOMs to SAP based on
Lifecycle State.
• Prevented unchanged components to republish.

7. Migration & Upgrade
• Windchill ESI ( SAP) 10.1 is migrated and upgrade to 10.2 MO 30.
• All ESI 10.2 MO 30 functional is carried.
• All existing ESI customization applied on 10.2 MO 30.
• New enhancement and customization done in 10.2 MO 30.
• New version of Tibco and Adapters are used which provided by PTC.

8. 3rd
Phase Go-Live
June 28rd 2015
is
3rd
Phase
10.2MO3010.2MO30
Go-LiveGo-Live