Receiver IDOC

Hi,
I have an idoc coming from xi. The idoc gets generated in SAP but with incorrect receiver partner name and port.
I do believe we fill up some mandatory fieds in xi. One thing i noted is for the logical system, the inbound parameter was not maintained in r,3. Is that a proble for the idoc not getting posted completeley.
Even it gave edi partner profile not found.
Please do give some light on this.

Hi,
>the inbound parameter was not maintained in r,3. Is that a proble for the idoc not getting posted completeley.
Yes, Maintain the Inbound Parameter for the respective Message type and try it out
Regards
Agasthru iDoss

Similar Messages

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <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="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

Adapter Module for receiver IDOC adapter?

Hi,
I have a scenario where i need to do some custom logging in the receiver adapters. For all receiver file adapters, i have written an adapter module which fulfills this custom requirement but how will i do this in the receiver IDOC adapter as its on the ABAP stack? I cannot write a java adapter module for this.
Is there anyway by which i can write a ABAP adapter mosule and deploy it in the IDOC adapter? Or any other way to achive it. the scenario is such that i need to do the logging before the idoc is posted into R/3 system by the idoc adapter.
Please advice.
Regards,
Yash

Hi Chirag,
Yes i have seen that the module tab is disabled for idoc adapter. I have a fin interface where i need to split a incoming file into an idoc and a file. For this purpose i need to log how many records are received by each adapter and the sum of the line items for audit perspose.
any othr way to do it apart from doing it in message mapping. The req is to do in the adapter engine.

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

Receiver IDOC adapter - RFC_NO_Authority

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
Went thru receiver determination, Interface determination, message split, request message mapping, Technical routing and then got stuck at call Adapter stage. Below is the error:
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Runtime error RFC_NO_AUTHORITY has occurred</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Runtime error RFC_NO_AUTHORITY has occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there any step that I may have missed after I created the receiver IDOC Channel?
Could you please shed some light here?

Please, search SDN before posting....
check these link: Runtime error RFC_NO_AUTHORITY has occurred in SM58
What its error?

Idoc packaging for Receiver Idoc adapter in 7.11

We are using PI 7.11. And, I have a File to Idoc scenario. I am trying to find an Idoc packaging option for Receiver Idoc adapter. Any suggestions on how to do configure thi scenario?
Thanks
abhinaya4321
Edited by: abhinaya4321 on Dec 3, 2011 12:15 PM

hi,
We are using PI 7.11. And, I have a File to Idoc scenario. I am trying to find an Idoc packaging option for Receiver Idoc adapter. Any suggestions on how to do configure ?
that is possible with message packaging concept it is suitable for you requirement
go through below links:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?QuickLink=index&overridelayout=true
thanks,

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Receiver Idoc adapter - issue

Hi,
I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
As soon as having done this my IDocs fail in the adapter giving me the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
<Trace level="1" type="T">Convert one IDoc</Trace>
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
<Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
<Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
<Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
<Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
<Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
<Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
<Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
Best regards,
Daniel

Hi,
Thanks for your quick reply.
The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
But to answer your questions:
1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
2. No blank segments are being created
3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
Best Regards,
Daniel

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

Problem with SAPServerHost - Receiver Idoc

Good afternoon!
I am using the component SAP.Net Connector to receive IDOC's from the SAP, for this I created a Windows Service and in the OnStart event I create the SAPServerHost object that will go to talk with the SAP (through the transaction sm59, for example).
It happens that some times the SAP does not obtain to see this object, thus being does not obtain to send the IDOC's for windows service.
Thank you.
Danilo Santos de Oliveira

The SAPServerHost itself doesn't register at the SAP gateway. The actual SAPServer-inherited instances do so. You create them and attach them to the SAPServerHost. The host can control the state of the servers that it hosts, e.g. it can stop, pause and continue them.

Can we go with ALE configuration instead of receiver idoc adapter at target

Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.

Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj

Receiver IDOC

Similar Messages

Maybe you are looking for