Skip to main content
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
October 28, 2025
Solved

Sending to multiple distribution targets with ERP Connector

  • October 28, 2025
  • 2 replies
  • 444 views

Thinking ahead to a multi-site, multiple SAP plant configuration which might be possible in the future. I am currently using the ERP connector and we have a custom integration on the SAP side to read in the ERP Connector output files. Obviously, the concept of a Plant comes with the use of a SAP type distribution target which from what I gather requires the fully licensed ESI package. I have only 1 target right now so very simple to Send to DT and away it goes. SAP has been configured to accept information and load to only 1 plant that we default to. 

If we bring in another site, they will likely have a different SAP plant and I would want their data to go to their plant. Ideally, our data would be separated in difference product contexts but I do not see options in configuration to have it map a default Distribution Target by Product Context. It seems to be restricted to the Site and Org level. So how is the mapping done?

If I was using SAP ESI DT, do I have to publish to all plants? Where is the logic to choose DT 1 vs DT2? Can this be defaulted by context to indicate all these contexts go to DT1  and these others go to DT2?

Ideally, if I was able to get this to work using the ERP Connector, it would save me a ton of rework to existing process. Very easy for me to have SAP watch a diffent folder for XML files and map those folders to specific plants.

Best answer by avillanueva

Thanks @Marco_Tosin and @Fadel , I see the View Version mapping but that is not quite the kind of mapping I am trying to do. Each site would just use MFG view to send BOMs but there is also Parts and changes that publish as well. However, the docs do point to preferences for customization:

https://support.ptc.com/help/windchill/r13.1.1.0/zh_TW/index.html#page/Windchill_Help_Center/erp_admin/ERPChanging_Default_Dist_Tar_Assignment_Strategy.html#

avillanueva_0-1761659855353.png

I think I can use this to create me own logic here. I have the view mapping set to no since I am not publishing different BOM views to different plants. Its each site maps to a plant and their data goes to a different plant in SAP. I should be able to write a class that can use the product context and a mapping to determine the right distribution target. 

2 replies

Marco Tosin
21-Topaz I
Marco Tosin21-Topaz I
21-Topaz I
October 28, 2025

We have a different view for each division, which corresponds to the relevant Distribution Target.

 

With customization, each WTPart is automatically linked to a distribution target based on the Plant view that is created.

 

When the code is sent to SAP, the system already knows which division to call.

 

Marco
Fadel
Fadel23-Emerald I
23-Emerald I
October 28, 2025

take a look at https://support.ptc.com/help/windchill/r13.1.1.0/zh_TW/index.html#page/Windchill_Help_Center/erp_admin/ERPAssigningDistTarBasedonPlantData.html  

Buiꓘa
avillanueva
23-Emerald I
avillanueva23-Emerald IAuthorAnswer
23-Emerald I
October 28, 2025

Thanks @Marco_Tosin and @Fadel , I see the View Version mapping but that is not quite the kind of mapping I am trying to do. Each site would just use MFG view to send BOMs but there is also Parts and changes that publish as well. However, the docs do point to preferences for customization:

https://support.ptc.com/help/windchill/r13.1.1.0/zh_TW/index.html#page/Windchill_Help_Center/erp_admin/ERPChanging_Default_Dist_Tar_Assignment_Strategy.html#

avillanueva_0-1761659855353.png

I think I can use this to create me own logic here. I have the view mapping set to no since I am not publishing different BOM views to different plants. Its each site maps to a plant and their data goes to a different plant in SAP. I should be able to write a class that can use the product context and a mapping to determine the right distribution target. 

Terms & ConditionsCookie settingsAccessibility statement