We use Baan 5C, and have had a functioning RTP since about 2001. We are
transitioning to Baan LN, but that is taking multiple years to do
worldwide.
Using the ESI toolkit from PTC, we use the same basic approach that PTC
recommended back in 2001: a stand alone workflow to send a part version
(item master data) and bill of material (production bill of material) data
to Baan. We have had an attribute in Windchill called Item Group Code
since 2001, originally modeled using a Rose Model extension, but since 9.1
it has been an IBA that we have called "Initial Item Group Code" since we
allow manufacturing engineers to change item group code in Baan without
changing it in Windchill, mostly because we have 2 baan companies, and
after initially setting the item defaults, that code is not useful in
Windchill, while it can change differently in our Baan companies for
reporting and other purposes. If we were to do it all over again starting
in Windchill 10.0 or 10.1, then I would push hard for using the ECN/ECT
process to publish data to Baan, but that boat sailed for us a decade ago,
and it is hard to change long standing practices.
The number of difficulties we have encountered, how we overcame them, and
what compromises we have made to live with a Windchill-Baan RTP is much
too long for a post here without knowing exactly what you are looking for.
If you send me a list of specific questions you are looking for, then I
will answer them off forum.
Al Anderson
Solar Turbines Incorporated
[solutions] - Windchill-ERPLN (Baan) Integration
Yogesh Bajpai
