on 05-14-2013 3:03 PM
Hello everyone,
I’m beginning to research for a client project that requires conversion of an XML file to something compatible with SAP ERP. My thought is we would use PI to convert the XML to IDoc and then pass it on to the ERP system. Am I on the right track here?
There is also a requirement to convert documents from the ERP system into flat files for use in legacy systems at this client location. Is PI also the best choice for this scenario?
This would be a brand new PI system. I guess I am looking for recommendations on what technologies and components inside PI are the recommended route for doing these types of conversions.
Sorry I’m a total PI newbie, I deal mostly with the Server/Basis side of SAP.
Thanks!
Hi Thomas,
If you want to convert XML to Compatible format of ERP, we have 3 options.
We can use either IDOC/RFC/Proxies.
so you can go for File to IDOC or File to RFC or File To Proxy
To covert ERP content to flat file
So you can use either IDOC to FILE or RFC to File or Proxy to File.
As per view proxy will give better performance than the other adapters.
Before going to that adapter check the feasibility at ERP side and ask them which one will they support.
Refer below links for your reference
File--> PI --> IDOC
http://saptechnical.com/Tutorials/XI/FileToIDoc/Index.htm
File --> PI--> RFC
http://saptechnical.com/Tutorials/XI/FiletoRFC/BPM.htm
IDOC -->PI --> File
http://saptechnical.com/Tutorials/XI/IDocToFile/IDocToFile1.htm
File --> PI--> IDOC
http://saptechnical.com/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm
Proxy
http://saptechnical.com/Tutorials/XI/ABAPClientProxy/page1.htm
Step by step guides
Hope it will helpful
Regards
Bhargava krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
*go for ABAP Proxy if XML is high volume data.
*if very small data you can opt RFC.
*if low volume and asynchronous, then go for IDOC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
Simple search in SCN(file to IDoc scenarion) will give you many links.
Thank you,
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
I want to add couple of points:
I’m beginning to research for a client project that requires conversion of an XML file to something compatible with SAP ERP. My thought is we would use PI to convert the XML to IDoc and then pass it on to the ERP system. Am I on the right track here?
First you need to find out whether any Standard IDoc or Function Module/Bapi (as RFC) available at SAP can achieve your requirement. If not and you want to go for custom development, use Proxy communication. If available go for Standard IDoc / RFC.
There is also a requirement to convert documents from the ERP system into flat files for use in legacy systems at this client location. Is PI also the best choice for this scenario?
Between your SAP ERP and PI you have better communication processes like IDoc / RFC / Proxy than File. But you are really specific to File, thats also OK. PI has in depth and very stable functionality for these requirements and I will always recommend PI.
This would be a brand new PI system. I guess I am looking for recommendations on what technologies and components inside PI are the recommended route for doing these types of conversions.
PI platform comes with all the default features to implement Middle ware solutions. Which core PI components you need to use will depend very much specific to any Interface Architecture. You can describe if you have anything in mind.
Let us know for any more information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
In my opinion PI is the best tool for the situations you laid out.
Proxy may offer better performance, but you may be happier if there is a standard inbound IDOC which meets your needs. You can implement that quickly, and it can handle a very high volume. Also some people are more comfortable troubleshooting when a standard IDOC won't post, vs a custom proxy interface.
You would not need any extra PI product or add-ons for the situations you've mentioned. You could go dual stack or single java stack, though I'm not sure how mature the IDOC adapters are on the Java only stack.
Doing this yourself without PI training or background in the product may be a daunting task. You might want a consultant to help you get the basic configurations hammered out and show you how to monitor the messages.
Good luck!
Aaron
Yes. you are on the right track
other than the above suggested links..you can refer to the below links for your scenarios.
http://saptechnical.com/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm
http://saptechnical.com/Tutorials/XI/IDocToFile/IDocToFile1.htm
Regards,
Hareesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomaz,
See the links:
PI Best Practices Naming Conventions
PI Best Practices: Sizing and Performance Tuning
SAP R3 (Idocs) To XI -- Steps Summarized
How to Sample IDoc-XI (Exchange Infrastructure) Scenarios (NW7.0)
How to Send Multiple IDocs Within One Exchange Infrastructure Message (NW7.0)
How to Handle Acknowledgments for IDoc (NW7.0)
Why naming conventions are important to SAP PI
Regards,
Pedro Baroni
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Best way to go ahead...follow below help link, you will get almost all answers (conceptual as well as technical), u want to know.
SAP NetWeaver Process Integration - SAP Library
Hope it helps.!
Regards,
Sunil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.