Skip to Content
author's profile photo Former Member
Former Member

XI Development

The scenario is that standard IDOC (PEXR2001) will be sent out to XI.

We are planning to create a new adapter which takes this PEXR2001 as an input

and output to and XML format.

In addition to the data present in PEXR2001, this output XML format requires other data from the R/3 system which are not present in the IDOC.

The crucial thing is that no development (eg. user exit ) can be done on the SAP R/3 side to enrich the IDOC or to create customized RFC.

<b>Question 1</b>

Is it technically possible to get specific data from R/3 into XI through the use of SAP standard RFC ?

<b>Question 2</b>

Is it technically possible to program the mapping in such a way that if an element is blank, it will call the necessary RFC in the SAP R/3 and pick up the data from the result return by RFC?

<b>Question 3</b>

In the event that the data we need cannot be retrieved using standard SAP RFC, is there any way we can get the data ?

<b>Question 4</b>

The use of an IDOC is not mandatory. IDOC is used here only because it is the only standard SAP format readily available (without development) that can be exported out of SAP into XI. Is this a correct observation ?

<b>Question 5</b>

What is the extent of XI customized development ? Is it only limited to adapter and mapping development or is will a developer be able to create new transactions and screens in XI ?

Thanks. Please refer to the questions when answering. I will reward points prompty.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 23, 2007 at 08:24 AM

    Hi,

    <b>Question 1</b>

    Is it technically possible to get specific data from R/3 into XI through the use of SAP standard RFC ?

    <b>Ans:</b> For specific data you have to create the custom RFC.

    <b>Question 2</b>

    Is it technically possible to program the mapping in such a way that if an element is blank, it will call the necessary RFC in the SAP R/3 and pick up the data from the result return by RFC?

    <b>Ans:</b> If the element will be blank, then you will not be able to select the data from R/3. But in other way if you have some input from source (file) then by using <b>LOOKUP FUNCTION</b> you can retrive the data from R/3.

    <b>Question 3</b>

    In the event that the data we need cannot be retrieved using standard SAP RFC, is there any way we can get the data ?

    <b>Ans:</b> Use Proxy (Inbound Proxy), Custom RFC & IDOC.

    <b>Question 4</b>

    The use of an IDOC is not mandatory. IDOC is used here only because it is the only standard SAP format readily available (without development) that can be exported out of SAP into XI. Is this a correct observation ?

    <b>Ans:</b> Yes, you can say.

    <b>Question 5</b>

    What is the extent of XI customized development ? Is it only limited to adapter and mapping development or is will a developer be able to create new transactions and screens in XI ?

    <b>Ans:</b> XI customized development means that you will be able to create only data extraction programs, IDOCs, RFCs & Proxies.

    No screen or transaction designing is involved.

    Regards,

    Sarvesh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 23, 2007 at 08:13 AM

    <i>The scenario is that standard IDOC (PEXR2001) will be sent out to XI.

    We are planning to create a new adapter which takes this PEXR2001 as an input

    and output to and XML format.</i>

    >>

    why a new adapter? you can use the Idoc sender to achieve the same.

    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm

    <i>Question 1

    Is it technically possible to get specific data from R/3 into XI through the use of SAP standard RFC ?</i>

    >>>

    in your case get the idoc directly into XI from SAP

    <i>Question 2

    Is it technically possible to program the mapping in such a way that if an element is blank, it will call the necessary RFC in the SAP R/3 and pick up the data from the result return by RFC?

    Question 3

    In the event that the data we need cannot be retrieved using standard SAP RFC, is there any way we can get the data ?</i>

    >>

    you can do a mapping lookup for sure.

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/xi%20mapping%20lookups%20rfc%20api.pdf

    <i>Question 4

    The use of an IDOC is not mandatory. IDOC is used here only because it is the only standard SAP format readily available (without development) that can be exported out of SAP into XI. Is this a correct observation ?</i>

    >>

    since u already have an existing idoc in sap, its better to utilize the same.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 23, 2007 at 09:34 AM

    Hi

    <i>Is it technically possible to get specific data from R/3 into XI through the use of SAP standard RFC ?</i>

    In case there is already an RFC that gets <i>your</i> specific data R/3, you can do so.Otherwise you need to create a custome RFC.Same applies with the IDocs or you need to create Custom IDocs or else go for Proxies.

    <i>Is it technically possible to program the mapping in such a way that if an element is blank, it will call the necessary RFC in the SAP R/3 and pick up the data from the result return by RFC?</i>

    Dont know whether in a mapping program this can be done, but otherwise using JCo, a java code can achieve so.

    <i>In the event that the data we need cannot be retrieved using standard SAP RFC, is there any way we can get the data ?</i>

    Use custom RFC, or IDocs or RFC.

    <i>The use of an IDOC is not mandatory. IDOC is used here only because it is the only standard SAP format readily available (without development) that can be exported out of SAP into XI. Is this a correct observation ?</i>

    Yes, and this applies to both RFC or IDocs that are readily available and can be exported into XI.

    <i>What is the extent of XI customized development ? Is it only limited to adapter and mapping development or is will a developer be able to create new transactions and screens in XI ?</i>

    No customized screen can be created.Adapter Module Development,Java Mappings, XSLT Mappings etc are only possible.

    Looking at the above scenario, creation of a new adapter which takes this PEXR2001 as an input is not required.

    Additional output required for the target can be achieved by having multiple source and a single target.N:1 using BPM.

    And any specific reasons that no development can be done on the SAP R/3 side.

    Creating a customized RFC would be the best solution in case no standard RFC/IDoc exist.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      > Hi

      >

      > <i>Is it technically possible to get specific data

      > from R/3 into XI through the use of SAP standard RFC

      > ?</i>

      > In case there is already an RFC that gets <i>your</i>

      > specific data R/3, you can do so.Otherwise you need

      > to create a custome RFC.Same applies with the IDocs

      > or you need to create Custom IDocs or <b>else go for

      > Proxies.</b>

      Thanks MK. Just a question, what are proxies and how can they be used in this case ?

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.