Connect Eigner PLM/Teamcenter to R/3 by XI

[tobiasberneck]

Hi,

I'm looking for any informations regarding the connection of Eigner PLM/Teamcenter to a R/3 system by XI (exchange of material data/documents/BOM's). AT the moment the systems are connected by an self written RFC client which is executed on the PLM server and which is calling FUBA's in the R/3 system. We want to get rid of this mechanism and want to implement a smarter solution.

Can anyone give me some informations regarding this topic (Does the transfer by XI make sense?/Is there any usable documentation regarding this topic?/What other possibilities are available?/Has anyone experience in this implementation). At the moment we know about xPLM as another possibility to connect PLM systems to R/3, but this means an additional middleware system with additional administration effort.

Thanks,

Tobi.

[Former Member · Accepted solution]

We are facing the same integration scenario, and are currently beginning a new project.  We are an Aerospace & Defense company, and have very strict integration requirements to our ECC system.  We must integrate via PI.

SIEMENS has provided two integration alternatives - Teamcenter Gateway for SAP & PLM Integrator.

TG4S is a collaborative framework between Teamcenter and SAP for full bi-directional information exchange.  This solution can be used with or without SAP PI for integration.  So, if you do not have a middleware component, it can still be used. It is:

Developed by TESIS PLMware

Sold by Siemens PLM Software

Certified by SAP

The second option is PLM Integrator for SAP.  This is a specific component to be used with SAP PI for integration with SAP ECC.  The system specific PLM Integrator supports all important business objects and services of the relevant PDM/PLM system after a standard installation. Thanks to his generic adapter concept he can be easily adjusted to customized system enhancements (objects, relations, services) by retrieving describing data out of the system repository.

While orchestrating PLM services provided by PLM Integrator within the Process Integration (PI) the information and data flow across multiple enterprise departments speeds up and gets controlled automatically according to ever changing business rules:

 In time information regarding upcoming engineering changes of products

 Seamless cooperation across departments without changing user interfaces

 Fast alignment to customer specific requirements within the sales acquisition

 Tight cooperation of engineering labs with the purchasing and external suppliers

 Reliable technical details on customer equipments for the field service

 Integrated project management for internal and external engineering labs

[tobiasberneck · Accepted solution]

This question has been created a very long time ago....

In the meantime we have implemented an solution based on SAP PI which is developed completly on our own.

[former_member206743 · Accepted solution]

Could you please provide detail of the solution developed by your own.? I am looking for best possible way to integrate with PLM using SAP PO.

Thanks

Jaideep

[tobiasberneck · Accepted solution]

Hi,

the connection was implemented by using PI standard SOAP adapter and an self written webservice running on teamcenter. The webservice is providing metadata of teamcenter objects and is called synchronously from a PI SOAP channel.

For starting a transfer an HTTP trigger sender has been implented on teamcenter. This is sending "trigger" message to a PI SOAP sender channel.

For keeping the order of transfer triggers are forwarded to queuing table at PI and fetched from there EOIO.

Regards,

Tobi.