IDOC to ABAP Proxy

Now we are sending our PO IDOC from our R/3 box using an IDOC channel to
the XI Box. Our R/3 is sitting on WAS 6.40.
We are planning to migrate from the IDOC to Proxy to send the PO to XI Box.
What are all the modifications and Development steps I will be doing to achieve the above Task?

Hi Pete,
I'm not goint to tell you how to do it but let me point a few reasons why not to do it:
- it's not possible in standard to replace IDOC processing with Proxy right now
so whatever you build it will become very diffcult to maintain
when SAP will relase something in standard to do that - so why do it ?
- if you need to send an attachment with it just do it from XI
(this is how it can be done quite easily)
BTW
the only way to send PO data with proxy (via events)
is described in my blog:
/people/michal.krawczyk2/blog/2006/11/06/xi-bam--episode-i--introduction
Regards,
michal

Similar Messages

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

Idoc to ABAP Proxy with Acknowledgement Coming Back

We are running SAP standard SRM scenario where our ECC systems are posting Idocs to PI which maps and sends to SRM as an ABAP proxy. Can someone please explain to me the best way to have SRM send back an acknowledgement to the sending ECC system when the document has been posted so we can update the Idoc status? We are looking for standard SAP config firstly, then will consider custom development if absolutely necessary.
Thanks in advance!
Peter

Hi Peter,
you can configure the IDOC ack setting and you can getthe idocs for acknowledgement in ECC side.Configure the ALEAUD message type in ECC and configure one Coomunication channel for the ACk in ID.
if this is not clear just giive ur mail id i will send u one pdf or this
Regards

IDoc vs ABAP Proxy

Hi experts,
I have a couple of integration scenarios as such
SAP -> XI -> SOAP
We have a couple of options for the link between SAP -> XI.
1. ABAP Proxy
2. IDoc
These are usually asynchronous updates to the external system, triggered from SAP.
Which method is better in terms of performance, and maintainability point of view.
Currently, I chose the IDOC approach because if we were to go with the ABAP Proxy approach, the SAP system requires an XI ADD-ON, which implies additional risk.
Any advise is greatly appreciated.
Thanks.
Ron

Ron,
Take a look at this blog, it should answer your question of when to choose Idoc's and when to go for proxies,
<a href="/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems">Choose the Right Adapter to integrate with SAP systems</a>
If your load is high, then SAP strictly recommends proxies. If load is not very high and you have standard Idoc's available for this, you might as well go for Idoc's.
Regards
Bhavesh

IDOC or ABAP Proxy

We are currently on WAS 6.40. We have to send the PO's to our Vendor. This is a new functionality that we are trying to add in our R/3 System. Once this is done we will be exchanging the PO's with our vendor.
Now my question is should I need to go for the IDOC or an ABAP Proxy? Which one will suit my situation now and in the future? Why?
Thanks.

Hi,
>>>>So how should I use the correlation here to fetch the file that I want? would you explain me in detail please? Thanks
we do it like this:
a) the file attachment is big
inside a BPM we take the PO numer (which is also the PDF number)
call async java proxy that copies the PDF from our location
to suppliers location (this way we don;t put the attachment
in XI as it's only copied via java proxy)
b)the file attachment is small
inside a BPM we take the PO numer (which is also the PDF number)
call async java proxy that copies the file and calls another async java proxy
to come back to our BPM - then we have the PDF inside XI
but the first way is more prefered as you don't need to store the PDF
inside XI in this case (as you jut copy to destination)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

RFC or IDOC or ABAP Proxy

Hi,
What is the best way(R3 Side) for standardization?
R3 <-> Legacy.
I've read all related article on sdn, but i am not still clear on which best way RFC or ABAP Proxy or IDOC in real life.
if you are, what is suggestion?
thanks
dennis

Ogawa,
There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
---Satish

Choice Between IDOC and ABAP Proxy

Hello All,
We are building a Bi Directional Interface for Business partners between a third Party ERP, XI and SAP CRM.
We are looking for some advise on the best way to go forward between the two options below:
a) Do an ABAP Proxy Call on Fn Module CRMXIF_PARTNER_SAVE from XI
b) Create and IDOC in CRM
( Message Type CRMXIF_PARTNER_SAVE_M )
Not being an XI consultant, my understanding is as follows
Option A : Gives me the flexibility to format my response in the manner we like. But this is a synchronous call. Also this is a generated RFC. So changes in the XIF layer of CRM could be an issue.
Option B : Response can be achieved only through the ALE Audit Functionality, which has a predefined message structure. For Eg: If I wanted to send the response in the same format as the incoming message with an added segment for the error, this is not possible. Ofcourse, I get all the functionalities of monitoring and Handling IDOCs in this option.
Any thoughts on the advantages and disadvantages of each option would be greatly appreciated.
Thanks
Anoop

Anoop,
I probably should have mentioned in the BLOG, that IDOC is good if its a standard IDOC, so that you don't have under go the pain doing the modifications for the custom one.
In your case, PROXY might make more sense as you are saying that you have to do some custom processing as well. So, you can call the BAPI / Function for the standard processing and then do the custom processing in your Proxy code. And more over, if you have want to have a Synch interface, then you cannot use IDOC.
So, the options in this case boil down to PROXY / RFC.
PROXY will definitely have the advantage as its going to bypass the adapter engine and directly interact with the Integration server. And moreover, even if you already have a RFC, you can always call that inside your PROXY. However, the only flip side here compared to IDOC, is that you will have to create all your IR objects manually.
Hope this helps you in making your decision.
regards,
Ravi
Note : Please mark the helpful answers.

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

ABAP Proxy or IDOC Adapter?

Hi all,
In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
1. Oracle ->PI ->SAP R/3
Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
2.VAN->PI->SAP R/3
VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
3.SAP->PI->VAN
Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
Please suggest me which one is better in all the scenarios.
How to decide which is better for the above scenarios?
Thanks In advance
Venkatesh

>
venkatesh bs wrote:
> Hi all,
>
> In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
>
> 1. Oracle ->PI ->SAP R/3
> Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
>
> 2.VAN->PI->SAP R/3
>
> VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
>
> 3.SAP->PI->VAN
> Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
> Please suggest me which one is better in all the scenarios.
> How to decide which is better for the above scenarios?
>
> Thanks In advance
>
> Venkatesh
Material Master - MATMAS
Invoice - INVOIC01
PO - ORDERS
wouldnt the above IDoc suit you?

Wheh to use abap proxy and when to use idoc

Hi All,
Please provide some clarifications for the below points :
What is Sproxy?
2.     Why we are using Sproxy instead of Idocs
3.   When we are going Proxy ?
4.   What are the types of proxy ?
5.   How to Create to Proxy ?
6.   What the Difference between SProxy and Idocs
   7.   What is SOAP file? When we are using SOAP file ?
Thank you.
Regards,
Bharat

Hi Bharat,
You seem to have a range of Questions. I will try and answer as many as possible.
What is Sproxy?
SPROXY is a transaction [T-Code] on the SAP ECC/CRM etc side where you can see the objects designed in SAP PI ESR and develop its corresponding ABAP code. SPROXY T-Code displays the Service Interface. You can read more about it in the following site:
**************** - XI - ABAP Proxy communication
2.     Why we are using Sproxy instead of Idocs
For Certain implementations Standard IDocs may not be available and it is quite tedious to create a Z- IDoC and therefore it is advantageous to use Proxy. You can read more about this doubt in the following links:
Choosing to use IDOC standard or ABAP Proxy?
IDOC vs Proxy
ABAP Proxy Vs IDOC
3. When we are going Proxy ?
When there are no Standard IDocs available. Please refer above links to get an answer for this.
4.   What are the types of proxy ?
5.   How to Create to Proxy ?
Again the following link has the answers for both these questions:
**************** - XI - ABAP Proxy communication
6.   What the Difference between SProxy and Idocs
Difference is in the way the communication happens. Standard Idocs are already provided and you can use them directly while Proxy you will require to write the code on ECC side. You can refer the following link to understand more:
Advantage of ABAP proxy over BAPI
7. What is SOAP file? When we are using SOAP file ?
I have not heard of anything called SOAP file. SOAP is a protocol used for communication and you can send files as attachment in your SOAP to Any(file/idoc/Soap etc) or vice Versa Interfaces. Infact Proxy itself is SOAP based communication with XI 3.0 Protocol.
Please explore SCN to know more about the various scenarios. There are endless possibilities in SAP PI.
Hope this Helps.
Thanks & Regards,
Tejas Bisen

RFC (using AAE) vs IDoc (Using IE) vs ABAP Proxy (using IE) in PI7.1

Hi All,
In previous versions of SAP PI, SAP recommends the use of IDoc or Proxy over RFC mainly due to performance reasons, but with PI 7.1, RFCs can use AAE which significantly boost its processing.
So the question is, with PI 7.1, is the performance of RFC adapter using AAE good enough that is should be considered over IDocs (using IE) & Proxies (using IE)? Please provide elaborate reply.
Thanks,
Rahul

>>>>>So the question is, with PI 7.1, is the performance of RFC adapter using AAE good enough that is should be considered over IDocs (using IE) & Proxies (using IE)? Please provide elaborate reply.
Answer: If your major objective is only the performance factor then you can go for AAE using RFC. But RFC's individual processing performance is slightly lower than idocs and proxy.
Though AAE monitoring is just only in RWB, But due to less persistence steps involved in the entire processing, RFC with AAE supercede other options.
IDOc using IE vs Abap Proxy using IE --- I would recommend only Abap Proxy using IE. Plus you get all the monitoring features here.

ABAP proxy - XI - IDOC

Hi,
I built a new interface: ECC ABAP proxy - XI - CRM IDOC and tested it in DEV systems(ECC, XI, CRM) - it works well. I transport it to QA systems(ECC, XI, CRM). Everything seems OK, but when I do Proxy test from ECC QA system, I don't see message in XI QA. I receive - Services Processed Without Error
This ECC QA client was copied from ECC PROD client.
What definition I have to check in ECC QA system?
Thank you, Natalia.

Hi,
to see where your message is going,
execute the transaction SXMB_ADM,
select Integrtion Engine Configuration and check the RFC details.
The role of business system should be application system
and below that you have the RFC destination for integration system.
Just check if this RFC destination is pointing to XI QA.
I think this solves your problem.
Regards
Pushkar Anand

File to custom IDOC or File to abap proxy

Hi there,
I would like to know best approach for the following scenario.
1) i have file coming from legacy system
2) On target side SAP , I have BAPI's available (Create, Save, Commit )(No standard IDOC available)
I can create Custom IDOC and call those BAPI's in Custom Function Module
or
I can use ABAP proxy and call BAPI's
What is the best way of doing this? and Is there any other way?
Thanks
Kumar

hi,
Abap Proxy is better than RFC in terms of performance.
proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
In your case , if there want to crate idoc from scratch level then we go for proxy and proxy support large volume of data (more than 5 mb).
One more reason is RFC , the data is converted between RFC and XML in RFC adapter. In proxy XI communicates with the R/3 in native XI language (SOAP XML).

Idoc syntx error me21 , abap proxy call transaction

Hi Experts,
I am struck with the below problem, could you please shed some light on the issue, appreciate your help and rewarded.
scenario:
XI sends NEW PO message to abap proxy, in abap proxy we populate bdc_tab
and call ME21 as below
CALL TRANSACTION 'ME21' using bdc_tab mode 'N' update 'S' messages into messtab.
problem:
EKSEKS01 idoc is getting created with syntax error status code :26 in ECC5.0
only 5 sigments are generated in the idocs. the three segments ( E1PISHO, E1PISIO,E1PISSO not generated).
after transaction executed it returns subrc 1001, msgid--> ME, MSGNO --> 218.
Thanks In Advance.
Ranjit.

Hi Atish and Nishant,
Thanks much for the immediate response.
1.Would like to know what is the mandatory data to be passed for PO creation in BDC table.
2. Is there any user exit or where the idoc creation happens during me21 execution.
I have verified the po in we02 , as before mentioned the three sigments are not getting created and i am not sure the reason.
Note: We didnot have any output configured in ECC 5.0 for this idoc to be created.
I am really not able to locate in debug mode FOR ME21, where this ekseks01 idoc getting created and triggered.
Appreciate your help.
Thanks in Advance.
Ranjit.

IDOC to ABAP Proxy

Similar Messages

Maybe you are looking for