Skip to main content
T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
December 10, 2025
Question

ERP Connector - Initial Seeding

  • December 10, 2025
  • 2 replies
  • 294 views

Version: Windchill 13.0

 

Use Case: Newly configured ERP Connector needs all existing released data in Windchill sent to it.


Description:

How does one send all existing released Windchill data out a newly configured ERP connector connection without altering the existing data in Windchill?  Normally the data will automatically be sent based off a state change or being part of a change notice.  Both of those things require creating or changing existing data in Windchill.  What options exist (if any) to push all existing released data out a newly configured ERP connection without changing states or creating new CNs for millions of existing objects?  Thanks.

2 replies

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
December 10, 2025

I know this. There is a way to bulk load "release" records on items to indicate they are already in your ERP system. 

avillanueva_0-1765379414297.gif

and here it is:

Loading Release History

 

T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
December 10, 2025

Hi @avillanueva,

Sorry to disappoint, but I need to do just the opposite.  I need to mass-push from Windchill to ERP because these objects are not in ERP yet.

T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
December 10, 2025

How do you do this at scale (millions of objects) in some automated fashion?  Is customization the only solution?

T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
December 10, 2025

This is the article PTC sent me:

Article - CS318762 - How to send a part or enterprise data to a distribution target using API in Windchill Enterprise Systems Integration

 

As @Marco_Tosin mentioned, it seems like customization is the only way to mass-push things.

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    December 10, 2025

    Should be easy to write a client to consume a list and ka-chunka-chunka its way through it. Again, my concern would be the overhead and exception you will see when the ESI workflow has an issue. The users will be getting hundreds of workflow tasks to address the ESI failures. 

      Terms & ConditionsCookie settingsAccessibility statement