IDOC versus Proxy - many standard-Prozesses

Hallo everybody,
this topic is discussed already quite often. Anyway one more point:
Following situation: SAP/R3 implementation basing on ERP2004 using many standard process. It is to implemente an interface to a storage system, so many standard information like delivery, material master, goods movements and so on have to be transferred. The easy possiblity would be to use the standard idocs and expand them with some customer specific fields und use the message control to send the idocs in dependence from certain process steps.
Alternatively I could develop proxies with all the known advantages (performance, overhead etc.).
The proxies could use BAPIs and so the development effort would be ok, but what about the processing of the proxy? Do I have to implement this manually or trigger them by a workflow-event? What about reprocessing? If an proxy message could not be executed because of professional incorrect data (for example EDI-Data coming from customer have incorrect material number, etc.)? This check can only be done by SAP/R3 backend and not XI. Idocs could be reprocessed manually after correcting the data.
Has anybody of you some experience or some recommendation for me? Prefering IDOC with Adapter?? Thank you very much!

hi,
>>>>Do I have to implement this manually or trigger them by a workflow-event?
yes
>>>This check can only be done by SAP/R3 backend and not XI. Idocs could be reprocessed manually after correcting the data.
not true, you can do it in the XI and restart the process in the XI (we19 = test tab in rwb)
(both are not recommended)
BTW
if you're using a storage system (some sofr of a warehouse ) then
DWMS scenario (based on idocs) seems to be
the best solution and it's a very well known standard
Regards,
michal

Similar Messages

IDOC or Proxy

R/3 to XI to Vendors
We are going to send atleast 40K documents every day from our R/3 systems to our Vendors. We are on Web 6.40, R/3 4.7c. XI 3.0 , SP 14.
In the above case should I need to go for Proxy on the R/3 side, because we are dealing with high volume of documents or should I go with IDOC communication channel? (No need to configure Sender IDOC). What are all the Pluses and Minuses?

Hi Rohini,
1) If there is no Idoc exists i.e standard then you can go for Proxy interface.
Because, in this proxy configuration, there is little more ABAP development involved..
Proxies communicate with the XI server by means of native SOAP calls over HTTP . But Idoc adapter requires , idoc xml conversion. anyway taken care by Idoc adapter. In sender side it is implicit
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again..
About Idoc, you need to port maintenance,logical system Metadata maintenance etc. But even in proxy also, you need to create RFC destinations.
And one more thing, if you want send package of idocs, then you need to use BPM etc in the XI.. But if you use Proxy, you can directly put entire data as one message into XI..
Hope this helps,
Regards,
Moorthy

Why is a sender communication channel not required for IDOC and PROXY ?

Hello,
In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..) when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
Though this might be a regular question, I am not able to find a proper reason.
Please let me know the reason for the above request.
Thanks & Regards.

You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
Regards,
Raj

Idoc to proxy scenario with an acknowledgment

Hi ;
I have to implement a IDoc to abapProxy scenario but an application acknowledgment must be return so IDOC status will be set.
How can i understand whether an application error exists while abapProxy is executing or not in status of IDOC?
Do I need to create and sent back new IDOC to the sender system in abapProxy code?
Thanks.

Hi,
See if you just want the ack for your IDOC coming from r/3 to XI, then you can use ALEAUD01 IDOC and you can configure it by running report IDX_NOALE in XI system..........
But if you want status change for appl error occuring in ABAP proxy system, then i think you will have to use a BPM for it.........you will have a recive step for getting your IDOC, then a transforamtion step for IDOC to proxy mapping, then a synch send step for sending proxy req and getting proxy response, then a transformaton step for mapping the proxy response to SYSTAT01 IDOC in r/3 for changing the IDOC status depending on success or error for your proxy response, then a send step to send this IDOC to r/3 system...............keep teh IDOC number in proxy req and proxy response so that you can use it in SYSTAT01 IDOC for sending it to r/3 and changing your IDOC status.
Regards,
Rajeev Gupta

Idoc Vs Proxy

Hi Experts,
I have a scenario like i want to transfer the Idoc data from One sap system to another sap system through XI. So What is the best option to do this useing IDoc or Proxy?
Can you please breiefly explain me above Adavantage & Disadvanctage of these ways and Which one is best for me in this scenario.
Thanks in Advance,
Points rewared for each valuable answers.
Best Regards,
Vijay

Hi,
It all depends upon the business Scenerio..
Proxies can be used when data is huge and it is quite fast in action and you can trigger when ever you want...
Assume if the data has to be updated immediately to the receiver system in that case IDOC is fine...once the Idoc is created we can trigger it by settings or thru by back ground job and by Tcode we02 we can find the status of the IDOC
Regards
Agasthuri Doss

How to do idoc to proxy scenario

Hi There,
As per requirement i am doing IDOC TO PROXY scenario. Can any one Pls help me how to do this configuration briefly.
with regards,
Naresh.K

Hi,
This is a Server Proxy Scenario.
To trigger the IDoc maintain necessary configuraions in R/3 and XI like.
1) RFC Destination (SM59) [XI & R/3]
2) Create Port (IDX1) [XI]
3) Load Meta Data for IDOC (IDX2) [XI]
3) Create Partner Profile (WE20) [R/3]
2) Create Port (We21) [R/3]
Also go thru this blog....<a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
There is no need to create sender IDoc communication channel and Sender Aggrement...
Go thru this blog for creating <a href="/people/siva.maranani/blog/2005/04/03/abap-server-proxies Server Proxies</a> by Siva Maranani
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

How many standard business roles are there in CRM

Hi Experts,
I had a question in one of my exam.. please answer it
question:- How many standard business roles are there in CRM?
options were:- 2,3,4,5
I think the options does not have the right answer , upto my knowledge it is more than 5. please help me with the appropriate answer
Thanks
Rahul Mathur

Hi,
There are approximately 40 standard business roles available in the latest version ehp3.
As the version changes the business roles increases. Initially there are only 3 std business roles..
1.sales pro 2. marketing pro 3. service pro and along with IC Agent.
Each BR above is loaded with huge no of transactions even though our aim is to for ex: create sales order...we use sales pro but all the sales related operations(transactions) are being loaded in to the system so along with the version improvements/releases SAP have divided each of these std BR as much as they can and thus the no of operations or transactions per BR is decreasing with each release....
Thanks & Regards,
Malleswar.

Idoc to Proxy Scenario

Hi,
I am working on a Idoc (ECC) to proxy (SRM) scenario , I am triggering the Idoc message from RWB, when I am trying so, message is getting pushed and it shows a success message in PI Moni. But it failes in the SRM system and the error message is as follows, Please provide me with some inputs. Also the Idoc message is not directly getting posted from ECC system.
Note: Logical system already exists in PI, ECC and also in SRM systems, Let me know should I check anything else.
Error Message:
==================
<?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>XIProxy</SAP:Category><SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code><SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1><SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2><SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Error during proxy processing
An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause
Application Error
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
Trace message is:
============================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 782464</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<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 = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:49:46Z 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>
<Trace level="1" type="T">Message-GUID = F506D1E488E811E0AF6B0000089A81FE</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>
<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>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</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>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface </Trace>
<Trace level="1" type="T">select interface namespace </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </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 action for sender or receiver 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>
<Trace level="1" type="T">Work Process ID: 786562</Trace>
<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>
<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 = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:55:09Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<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>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="Inbound Framework"></Trace>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><CX_ERROR href="#o93"/></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="o93"><CX_ROOT><TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID><PREVIOUS href="#o92"/><KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1580</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="o92"><CX_ROOT><TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID><PREVIOUS/><KERNEL_ERRID/><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1754</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>Error in an XI interface:
Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data
Program: 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>
<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"></Trace>
</SAP:Trace>
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on May 28, 2011 8:08 AM

Hi,
 In service marketplace, try searching for notes related to SRM PI scenarios or the particular scenario you are imlementing. For exmaple, if you are implementing the scanerio for Invoice processing, try searching with this.
When we implemented the standard scenarios for SRM, found that they were quite a few notes for the individual scenarios that had to be implemented for the scenarios to run successfully. Most of these were on the ECC or SRM side.
Also, by the looks of your error message, seems the sender system (not PI) is not defined in SUS.
Might be that the logical system for ECC is not set up in SUS. Also check your SPRO settings in 'Define Backend Systems'.
Have a look at the following links which had a similar error :
Vendor replication from SRM 7.0 EBP to SUS via PI 7.0
Vendor Replication in SUS scenario
Regards

Idoc to Proxy code..

Hi,
Currently, one of my client is using Idoc's to load data (from sender file) into R/3 but becuase of Idoc's we are facing some performance issues.
My question is that
1. is it possible to convert the Idoc processing logic into a code, which can be used inside server proxy.
2. How much performance is going t improve using such a methodology.'
Thanks....

Hi,
What should be the basis to decide when to use proxies, RFC adapter and idoc adapter.
We have to first check for our scenario do we have the standard IDOC or not.If we have the IDOC then we have to go with the IDOC.
If client need some validation and need to add some fields. that can be done by extending the IDOC and we can copy the standard IDOC and we can modify the code in the funtion module.
Next we have to go with RFC when we require the responce back from the target system. we have to check is there any standard BAPI or not.If u dont find then u can do customize RFC according to client requirement.
We have to go with Proxy if we dont find the Standard IDOC.
and if we have to RFC to be called at a time.
Suppoce if ur doing a scenario were u have to create a production order in this case we can go with RFC but after creating we have to commit the BAPI that cant be done in one process. we have to go with BPM and again performance issue.
In this type of cases we go with proxy scenario.if cleint require any data validation we ca do it.
If we want to reporcess the error date we ca do it. we ca send an intimation mail from proxy to user. this all can be done in proxy scenario.
Thanks and regards,
Phani

IDOC-XI-Proxy(CRM) scenario

Hi Xi experts..
I am new in XI with ABAP background. I have give a project in XI to design and implement a scenaio. The scenarion is this one:
ECC5 to XI then XI to Proxy(CRM).
In functional specs of this following diagram is mention :
ECC5(ALE)-->IDOC( XI)--
> XI -
> Proxy(CRM).
(ORDERS.ORDERS05) (XI SOAP ORDERS)
Please help me out.
Points will be awarder sure.
regards
Santosh Khare

Hi Santosh,
Following are the Links:
https://www.sdn.sap.com/irj/sdn?blog=/pub/wlg/1819; [original link is broken] [original link is broken] [original link is broken]
Z Inbound Proxy Class
Please go through the 'HOW to guides' for IDOCs if you have service marketplace user ID:
Click on Exchange Infrastructure in the menu on left side
and select How to sample Idocs within XI.
https://websmp201.sap-ag.de/nw-howtoguides
I hope it helps,
Thanks,
Varun

IDOC and Proxy to R/3 System.

Hi I am working on a scenario where a file is read and IDOCS are sent to SAP system.
My requirement is to create a proxy with a few fields like interface id, wait time and idoc type and trigger the proxy to SAP system as soon as the IDOCS are sent to SAP system. This is because I want to track the status of the IDOCS if they are successfully processed or errored out. We have defined some alerts in SAP and alert function modules in SAP which send out the EMAILS with relevant messages.
Can anyone please suggest the design that we need to have for this scenario?
In a nut shell: A proxy has to be triggered immediately after IDOCS are sent to SAP system.

Hi All,
The scenario is fixed.
We have defined the proxy and in the mapping gave the message read from file as a source message and the target as proxy message. Though there was no fields directly mapped from source message to proxy, this served as a trigger to proxy into SAP. And rest all in the configuration was similar to what we do in case of a proxy interface under the same namespace of the IDOC scenario.
Thanks & Regards,

Regarding Error handling and customisation in RFC, Idocs and Proxy

Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
Sampada

Hi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Vinod.

IDOC and Proxy

Hi friends,
I am having a doubt regarding IDOC, RFC and Proxies.
Now-a-days in real time ,which are in use IDOC Adapter or proxies....
in case of communicating between two SAP systems.

Hi raju
Adapters
 Connect existing (legacy) systems to XI
 Specific wire protocol
 Interface semantics externally pre-defined
Outside-in development approach
Proxies
Connect new SAP applications to XI
Native connectivity to Application system (adapter-less)
Interfaces designed centrally in Integration Repository
Inside-out development approach
c) RFC adapter- Remote funtion call maps RFC to Xml message and viceversa
In XI 3.1 we can use RFC.
>= Netweaver AS 6.2 we can use proxy in XI
Proxies are mostly used to communicate with two SAP system
with regards
Gabriel

Idoc to Proxy Scnerio

Dear All ,
We are having one ECC--PI-SUS Scneriao . We triggering an Idoc from ECC named "Z_CREMAS_SUSMM.CREMAS03" and on receiver side having Inbound Proxy. Idoc is getting successfully trnasfered from ECC to Pi but in PI Sxmb_moni we are getting below error "<SAP:Code
area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code">.
When we test the payload in INtegratation Directory using test configuration it successfully passes all the steps mention.
Please help.

Hi,
Have you gone thru these links below?
error message : RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC
RCVR_DETERMINATION - NO_RECEIVER_CASE_ASYNC
NO_RECEIVER_CASE_ASYNC
NO_RECEIVER_CASE_ASYNC
RCVR_DETERMINATION
RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC
Please also search SCN before asking this commonly asked question. If you did search. Copy the links that you used and which links did not resolve your issue.
Regards,
Jannus Botha

Idoc in proxy

Hi,
i want to update the data in idoc,can i do it using proxy?can i use idoc in server proxy?
Regards,
rao

Hi Rao,
yes, you can do that but it will require unnecessary coding effort.
When you already have a idoc its preferable to use idoc..
And if yours is a specific case which cannot be addressed by Idoc or idoc(customizing), then am afraid you are forced to use the proxy.
Hope the answer to you Q.
rgds,
chemz

IDOC versus Proxy - many standard-Prozesses

Similar Messages

Maybe you are looking for