Skip to Content

BAPI calls via XI

I am trying to position XI in our architecture as a single point for integration. My particular need is some info from those with experience in the following:

(1) is it possible to call a BAPI via XI to retrieve information? For this application for example, I am looking at having a BSP with a drop-down for company code....the company code selection values would be populated from the backend R/3 system via XI. IS this possible? If so, can anyone dsesribe the process there?

(2) If the above is possible, what is the performance difference vs. making the BAPI call to R/3 directly?

Thanks in advance for all info!

C.Solomon

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Apr 05, 2004 at 04:06 PM

    Hallo Christopher,

    from my experience i would say, that it doesn't make sense to redirect a BAPI call from a BSP through XI instead of a direct call to your backend R/3.

    Let me explain why: in NetWeaver there are different layers of integration, where XI clearly focuses on process integration. Portal or any other kind of WebSites (like BSPs) focus on People Integration.

    Process Integration with XI normaly happens between different systems, e.g. where you need to transfer information between a legacy application and SAP without manual interaction. Whereas a BSP is just another kind of GUI as the normal SAP GUI. So you could look at a BSP application in the same way as at any program within your SAP system. For any data selection etc. within your SAP system, you wouldn't use a BAPI call via XI, so it is with your BSP.

    So you have to be carefull which kind of integration you want to achieve and choose the right technology.

    XI is a really good system, but it doesn't make sense to use it in all scenarios.

    Regarding Performance issues: the scenario you described would be significantly slower than a direct communication to R/3 due to the many steps an XI message has to go through. (XI Inbound Adapter, XI Pipeline with Routing and Mapping, XI Outbound Adapter, R/3 Inbound Processing).

    Currently using XI makes most sense in asynchronous scenarios where response time is not a critical issue.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 06, 2004 at 11:16 PM

    Thanks Christine.

    You stated exactly my opinion but I didn't want to lead anyone with their replies. haha However, my client here sees XI as being their single point of integration all around their architecture....and yes, I have tried to explain the "why's and why not's" just as you did. Their arguement is that by everything "going through" XI, they can identify points of failure and trace back easier (for example, not all of the presented info to/from the portal is from a SAP box). Anyways, again, thanks for your feedback. You re-affirmed my "visualization" of XI in the overall scheme of things. I understand what they are looking for as well, but I just don't see XI being that magic bullet.

    Chris

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hallo Christoph,

      seems that problems are the same in most projects. SAPs new integration strategy with NetWeaver (remember this fancy picture with different layers people integr., information integr., process integr.) is not easy to understand for clients with no technical knowledge.

      Discussions after detailed explanation of this seem to lead nowhere. I hope these are just the obstacles at the beginning of the NetWeaver Age and after some time customers will understand what it is about.

      My last resort in this is to say "Best Practices is to ..." or "World class companies in your industry do it like ..." Most companies want to adapt best practices or be world class companies, so they are rather sensitive when it comes to this point. The only difficulty is then, to convince the world class companies 😉

      Good luck

      Christine