SAP Sending IDOCs to DOTNET IDOC Receiver

We are setting up a DOTNET IDOC Receiver to receive IDOC's from our SAP system. While doing a proof of concept today, we tested the case of SAP trying to send the IDOC while the DOTNET IDOC Receiver was not available (I had turned it off). The IDOC status in SAP reported that it had been sent (03). If I turned on the IDOC Receiver (using the sample program), it received the IDOC's with no trouble and the IDOC status in SAP reported sent also.
Questions: Does anyone know why SAP thinks it has sent the IDOC yet when we do a test connection from WE20 it fails?
We need to insure that all IDOC's from SAP have been sent to the IDOC receiver -- any suggestions on how to insure this transfer has taken place?

Hi,
The Spell Checker made some changes in my last response and I have to change the changes:
The status Sent (03) just means that the IDOC has been sent from the ALE/IDOC layer to the communication layer (tRFC). If the IDOC receiver is not available, the sent IDOC will stay in the RFC outbound queue (SM58). If the receiver become available again, the RFC engine will send the IDOC from the tRFC queue to the receiver. After receiving the IDOC, the receiver will in turn send back a confirmation to the tRFC outbound queue. Up to this moment, the status of the IDOC in ALE/IDOC is still 03. Sometime later, a pre-scheduled ABAP report (RBDMOIND)will check the tRFC queue and update the IDOC's status to "Confirmed" (12) if the IDOC has been removed from the tRFC outbound queue. There are also other means can be used to update the final status of the IDOC.
For details about IDOC processing inside SAP, please refer to the related documents.
Hope it somehow helps,
Guangwei

Similar Messages

Party-based IDOC from external SAP sender

Hello experts.
I have PI 7.0
I have a scenario where I receive an IDOC from an external SAP system - that has SID=PRD and client=400
I also have an SAP system in my landscape with SID=PRD and client=400.
when I tried to define a service and edit it's adapter specific identifiers - i received the following error:
Check Result for Object EXT_SRV
SAP system ID PRD and client 400 already exist in service | PRD400
I understood that the PI will not be able to identify the sender if an it will receive an IDOC with SNDPRN=PRD400
When trying to figure out a way to overcome this and be able to receive the IDOC I came across the term:
party-based communication. I understood that I should define a party an in it a service for the external SAP system.
can some one please show me a detailed step by step example of such scenario?
All I found was this: [Java IDoc Adapter Partner Conversion |http://help.sap.com/saphelp_nw73/helpdata/en/7b/ebc8b9e34b434d9f3e80ef6776d77a/content.htm] and it is only valid for PI 7.3
Thank you very much.

Hi ,
In idoc communication few fields play a vital role SNDPRN,SNDPRT,RCVPRN,RCVPRT,SNDPOR and RCVPOR in EDI_DC40 segment. These fields actually identify the sender and receiver systems and ports.
Now in your case as I understood that a new sender SAP system is sending the same idoc to PI server along with an existing one. In this case you need to alter SNDPRN value to a new value, when you are sending the idoc. All other values will retain same values for same idoc (basic type and message type). In ID add a new party in object list with the new SNDPRN value.
In the ID scenario create a copy of each entry in interface determination,receiver determination,sender agreement and receiver agreement. In each of the copy add the new sender/receiver party information SNDPRN value.
This should take care of your problem. No need to do any changes in IR as IR will be common for both the senders, what differs will be the ID. PI server will run different instances of the scenario for different SNDPRN value.
Finally one small request, please kindly if possible close down your threads, in case you got proper and correct solutions to your questions. I noted you closed only one of last five threads you have opened. If you close threads after a solution has worked, then forum users become sure that the solution has worked for your case and therefore is correct.
Regards
Anupam

HOWTO: Process IDocs from non-SAP sender

Hi everybody!
I have a small problem with the following scenario:
There is an external, non-SAP system that is able to send IDocs. Those (customer-) IDocs are as of now processed by an R/3 backend. Now this solution has to be migrated to an XI-based scenario:
 IDoc mult. IDocs
ext.System ---------> XI Integr. Process ---->-->---> R/3
However, all the documentation I found so far is based on an SAP R/3 sender system - and I can't seem to get the configuration for this particular scenatio right. Do any of you have relevant documentation?
Thanx in advance,
Joerg

Hi,
I have to admit - the scenario is somewhat esotheric. But regarding your questions:
Since there has been a communication before, we have the IDoc metadata in the R/3 backend. Using transaction IDX2 I have been able to load the metadata into the XI system w/o problems.
The external system has a certified SAP IDoc "connector" (as they call it) that is able to post the IDoc data- presumably through JAVA JCo or some other method. The only thing that matters to me is that they are right now sending IDocs to the backend directly - without files or something like that.
Now my real problem is that of receiver determination etc. Everytime I send an IDoc to the business process, the external system gets the error message
[code]
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:
No service for system <name of external system>,
client <name of XI client> in Integration Directory.
[/code]
This message occurs although I think I have configured the process correctly. Here I try to supply the pipeline of my process:
[code]
SENDER RECEIVER REC.DET.
<XI system> <business proc.>
 <rec. idoc> <abstr. itf. inp.> n/a
<external system> <business proc.>
 <rec. idoc> <abstr. itf. inp.> n/a
<business proc.> <R/3 backend>
 <abstr. itf. inp.> <send idoc> IDoc
[/code]
(Showing this in HTML is veeerys awkward
But this doesn't seem to work...
Any ideas?
Regards, Joerg

Hi friends, I have file for 10 records (sender),it display 10 idocs(receive

1)I have file for 10 records (sender),it display 10 idocs(receiver) how its possible.

Using XSLT
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Change occurrence of idoc
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Regards,
Prateek

Sending Order Number via IDOC upon creation of Sales Order

Hi Experts,
I have a requirement where i receive an order from an external system to SAP as an IDOC.
Upon arrival, i have to create the Order in SAP and send the Order Number back to the external system in the form of IDOC.
How can i accomplish this? Kindly share your expertise on this with me.
Thanks in advance.
Regards,
Keerthi

Hi Gary,
Now when the Order is posted in SAP, i need a method which will automatically trigger the Outbound IDOC from SAP rather than me doing so manually.
Is there a way i can track the creation of the Order in SAP and somehow configure SAP to trigger the Outbound IDOC with the Order number automatically?
Thanks in advance,
Keerthi

IDoc adapter inbox: IDoc sender partner is initial

Hi,
I have requirement to read the IDOC flat file and post IDOCs to SAP. As suggested in the following guide I am using report RSEINB00 to post IDOCS. This report basically calls the function module IDOC_INBOUND_FROM_FILE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
While executing the IDOC_INBOUND_FROM_FILE I am getting error:
"IDoc adapter inbox: IDoc sender partner is initial".
Please advise.
Thanks
Rajeev Gupta

Hi,
Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
In SAP ECC you need to have this logical system ...to process the received idocs..
thats it... Hope you got
Regards
Rajesh

Getting error while try to send data to matmas05 idoc

hello frnds,
i m working on a scenario in which i m sending data from xml file to matmas05 idoc of R/3. here i have done all the required XI settings. at sender side i have used file adapter and at reciever side IDOC Adapter. while i m executing my schenario at that time i m getting green flag into the sxmb_moni transaction but m not able to see any idoc generated at the receiver R/3.
can anybody tell me that what might be the problem? is it the problem with R/3 receiver or it is the problem with XI configuration itself..
Regards,
Hetal

hi,
if the flag is green you can check in SMQ1, SMQ2
for any waiting entries
I hope you've activated the queues in SXMB_ADM
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Same idoc to multiple EDI receiver system using rule

Dear Friends!
Good day! I am using desadv.delvry03 idoc and I want to send same idoc from same communication component to multiple receiver parties without mapping.
I have created first scenario successfully using idoc, when I create another scenario it gives me message like "Object already exist" . for that I have to use Service interface. I dont want to use service interface for this purpose. In my scenarios mapping is not even required. one idoc to and multiple receivers thats it.
Can you please guide me how to do the above requirement ?
your any help will be appreciated greatly
Thanking you
Regards
Dipen

Hi,
For this... U can create 1 sender agreent for that idoc if necesseary....otherwise we dont required IDOC sender Agreement.
Then Create 1 reciver determination in that u can mention the 2 recivers details...
same thing for interface determination also.
and finally create 2 reciver agreement and 2 reciver communication channels for 2 systems.
Let me know if you require any further information.
Thanks,
Sreenivas

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode IDX2 (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

Problem while sending back ALE audit Idoc

Hi,
I have a scenario in which an idoc is send from R/3 system to file service using XI. Here we have used BPM, in which Integraion process is the receiver of the idoc and then it is send to file system using file adapter. All the business services and Integration processess are created under Party. We expect XI would send implicit ALE audit Idocs to sender R/3 system.
I have created a communication channel pointing to sender R/3 system. After maintaining everything also it is throwing an error saying that unable to convert sender service to an idoc partner or ALE logical system.
Please help me in resolving this issue.
Thanks,
Vijay Kumar T.

Hi,
I have maintained adapter specific parameters for my integration process and those parameters are corresponding to sender business system parameters. As i told, i am using party and corresponding identifiers. My idoc is coming and successfully transmitted to file system but only problem is with acknowledgement that need to reach sender R/3 system.
Thanks,
Vijay Kumar T.

Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .

Hi Buddy's,
Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .And why we create receiver agreements at receiver side bt not sender agreement at sender side.
Wat Is GLOBAL Container ?, where it will Occur & wat is the functionality of that.

Kumar,
1) XI integrattion server - IS expects the messages in XML format. If you see the HTTP request you will see that we pass all the info contained in the Sender areement in the the HTTP request itself , namely - Message interface, message type and the namespace (along with login parameters). For IDOCs the the IDOC- XML are are sent to the IS (through IDOC port configuration at the source system.
2) When send a message to XI the sender knows that XI system parameters, but when at the reciver end there could be any any system that is reciving the IDOc/HTTTp message. you specify those message through a commumication channel and this channel is associated to a receiver agreement.
3) A Global container is like a place holder for variables. You can set a variable here and access it throughout your mapping and hence the name.
A good example for a gloabal container is a counter to countthe number of records in te target side.
Regards,
Arvind ravindran

Error while sending a PO as idoc through message control

hi,
i am getting this error when i manually enter a output type in ME22N transaction. This output type is supposed to send a ALE Orders idoc to the ABC610 system.
Partner ABC610 does not exist for partner function LS
Message no. VN006
Diagnosis
Partner does not exist for the partner function selected for this
transaction.
Procedure
Check your input.
pls help. Points will be awarderd for helpful answers
~Suresh

Hi Naveen,
Yes, Sorry forgot to mention in my previous post. The Partner profile with the same name exists in WE20 and also the outbound parameters are populated correctly to send the IDOC.
I also checked BD64 and the model is defined and distributed successfully.
any other inputs what else to check?
~Suresh
ANy inputs on this?
Edited by: Suresh Reddy on Jan 16, 2008 7:37 PM

Change IDOC Control Record in Receiver system

Hi Guys,
I want to change the inbound IDOC control record,is there any BADI or F.M available ?
My scenario : XI to SAP and its a custom application.
Regards,
Rajesh.

hi Rajesh,
You can refer this wiki link , this will help you out in your problem
https://wiki.sdn.sap.com/wiki/display/ABAP/IDOC+Steps
Regards
Saurabh Goel

Sending Outbound FI Documents IDOC via ALE

Hi all,
We would like to send FI documents via IDOC. However, the message types we found, (FIDCC1,FIDCC2,FIDCMT) do not have outbound function. In addition to that how can we trigger IDOC, after posting FI documents .
Thank you for your help...
Best Regards,
Didem GUNDOGDU
mail: [email protected]

hi, the outbound function for FIDCC1 FIDCC2 is list as followinig:
FIDCC1 FI_IDOC_CREATE_FIDCC1
FIDCC2 FI_IDOC_CREATE_FIDCC2
But still can't find the FIDCMT, maybe you can create a customize function reference to two others.
About trigger the IDOC sending, you can add the call function into a proper user-exits.
Help it can be helpful

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

SAP Sending IDOCs to DOTNET IDOC Receiver

Similar Messages

Maybe you are looking for