Database Table Structure

[IanWexler]

Is there a mapping or list of the tables for Windchill 10? We are implementing an ERP system and want to have the system grab data from Windchill so as to enter the data only once. Any help in pointing me to some data would be appreciated.

Ian Wexler

[MikeLockwood]

Don't even consider going down that path. Use ESI instead.

[IanWexler]

Mike,

Thanks for responding, what is ESI?

Ian

[MikeLockwood · Accepted solution]

http://www.ptc.com/product/windchill/enterprise

Very mature software for communicating with ERP systems. Can use "open ended" to just output files if desired.

This takes care of all needed relative to extracting objects rather than database table info.

[IanWexler]

Awesome, thanks!

[dkahlon]

Why not?

We are also looking at 'interfacing' Windchill (as ready-only of course) with other systems - not just ERP.

Even reporting - being 'pressured' into purchasing Cognos (at extra cost of course!) when we could simply use our existing Crystal Reports if we knew Windchill table structures.

I too would like to know more about ESI - is it another option that comes at a cost?

We have Windchill 10.1 M030 by the way.

[SimonHeath]

We have clients that use Crystal reports and Windchill and use it with some custom webservices which it supports. Direct access to the database using Crytsal is possible via JDBC and the data model is not that hard to understand as there is a one to one object relational mapping, so it you look at the table it has an object with exactly the same name in the API (found here codebase\wt\clients\library\api\index.html). The advantage of webservices is that they go through the API layer adding authentication and therefore access control. Note that webservices have an additional license cost.

Simon

[dkahlon]

Hi.

I can currently connect and 'see' the database via general ODBC using the 'Microsoft ODBC for Oracle' driver and can pull simple data into Excel very easily (and hence Crystal Reports).

But without a full database table structure with a definition of the fields and relationships, building a report would be like looking for a needle in a haystack!

If PTC would release this database information then customers like ourselves could save substantial amounts of money by creating our our interfaces/reports. Like in our case using Crystal Reports (which we already have) to build custom reports. The connection to Windchill would only ever be READ-ONLY.

[SimonHeath]

I agree a full db description would be great to have, it is painful to work it all out especially in the more complex areas such a change and effectivity which are often important in ERP interfaces. Another trick is to create your report in Query Builder (aka report manager) this has some in built knowledge of the db structure and then export the QML. The QML contains sort of readable information to help you trace it onto the real tables.