R/3 to R/3 IDOC Sending with HTTP

Hello everybody,
I'm trying to send an Idoc from one R/3 System to another, I'm trying to use the function module IDOCS_OUTPUT_VIA_XML_HTTP and it requires an XML HTTP port in we21, now I'm trying to create an HTTP RFC connection but I'm lost with the path refix parameter, can anyone tell me what should be in that field?
Regards,
Julio

hi,
problem with path prefix conform with u r basis guy he will help u .the path may like this /AdobeDocumentServices/Config?style=rpc.
if any queries let me know .
~linganna

Similar Messages

IDoc_02_Error passing data to port-Communication error when sending with HTTP

Hello All,
We are receiving the error "02_Error passing data to port-Communication error when sending with HTTP", when sending the idoc to PI from ECC system.
Observation:
1. Some idocs are failing and immediately after sometime the same type of idocs with different idoc numbers are getting successful.
Eg: Orders. One purchase order is failing at one point of time. later another purchase order is getting successful after some time to the same partner.
2. If i perform the reset of idoc, then it is getting delivered during next scheduled job run.
please help me in resolving the issue.
Regards,
Ch. Venkat.

status 02 is Error passing data to port ...it simply means your port setting has some problem. do configure your port setting and also in partner profile
Thanx and Regards
Arpan Maheshwari

SOAP Sender with HTTP(with SSL)=HTTPS with Client Authentication config

Hi All,
I have a Web-service-XI-Proxy scenario where we use SOAP Sender Adapter with HTTPs. Double authentication (client- server) sertificate shall be used.
Testing simple HTTP and XI user name/password works fine.
Now I installed requred sertificates in TrustedCA and ssl-provider in VIsualadmin.
But i can't see how i can configure certificates in SOAP sender Adapter. I've just did SOAP receiver for another scenario and there I could give keystore entry.
I also doesn't know how to disable asking for name/password. I am using XI 7.0.
Please advise.
Thanks,
Nataliya

Hi Nataliya,
Go to SOAP Adapter> Inbound Security Checks-> HTTP Security Level--> Here you can specify option "HTTP with Client Authentication.
One more thing HTTP Security level option is always available in Sender Adapter.
For more clarity about HTTPS find below link.
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
To enable the TrustedCA in SOAP Sender adapter. Go SOAP Sender> Security Parameter> Security Profile--> Web Service
security. Then go to sender agreement there you need to give key store entry.

XI3.0: Soap Sender with HTTPS

I have enabled HTTPS on our J2EE stack.
We have a soap sender which works fine using http and username/password authentication.
When I switch "HTTP Security level" on the SOAP sender to "HTTPS without client authentication" and sends the SOAP request to the HTTPS port XI (j2ee) returns a HTTP errorcode 403 Forbidden. No explanation, and I can't find any traces in the logs.
Please help/advise!
-AD

The solution was very simple!
The client accessing XI was using a .NET application which picked up Internet explorer's proxy settings, even if the .NET application it self activly set NO proxy!,...and that proxy did not allow https
Nothing to do with XI at all. Everything worked as soon as we got rid of that.
-AD

Need Help for SOAP sender with HTTPS protocol

Hi Team
We have a scenario where the sender is a 3P system and they will be sending the message using web service.They will send the data using SSL ( HTTPS) using certificates.
In the sender soap adapter , I have two options
1. HTTPS with client Authorization
2. HTTPS without client Authorization
I think I need to use the first option. But I have doubt regarding certificates
1. Who is going to provide the certificate? is it PI Team or the third party team.
2. Once we have the certificate where we need to store it in NWA? is it in the TrustedCA keystore view or service_ssl keystore view.

Hi Indrajit,
Krupa already shared a valuable resource on how to set up on Double Stack PI, so I'll focus on what's left to deal with / open questions.
Indrajit Sarkar wrote:
In the sender soap adapter , I have two options
1. HTTPS with client Authorization
2. HTTPS without client Authorization
I think I need to use the first option. But I have doubt regarding certificates
1. HTTPS with client authorization means that the 3rd party would not give username / password to authenticate to your PI but present a certificate you are trusting. You can think of this as an admission ticket to communicate with your PI server
2. HTTPS without client authorization means they will authenticate with username password.
In both cases the caller (3rd party) would need to trust your PI server. Most commonly this trust is established by not trusting your PI server's explicit certificate but in trusting the CA that issued your PI server's certificate. This CA can very well be a company internal CA. That way, if you happen to need changing the hostname of the server some time in the future, trust situation is still valid.
In case of 1. (HTTPS with client authorization) your PI server in turn would also need to trust the 3rd party caller. This is often done in such ways that the interal CA on your side issues a client certificate with the CN of the caller. The caller presents this certificate to your server upon making a call (see here for a picture https://help.sap.com/saphelp_nw74/helpdata/en/43/dc1fa58048070ee10000000a422035/content.htm). You will also need to back up this process on your PI server by mapping the certificate to a specific user.
--> Option 2 is the more polished one with ability to withdraw a certificate and the like. However it does result in some overhead setting it up so I personally would go with Option 1 if there's no business need / security policy enforcing so.
HTH
Cheers Jens

IDOC send step not running with exception in BPM?

Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
Dirk

Hello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk

Oyput- IDoc- 3 send with application own transaction

Dear All,
How is system generating IDoc when the Despatch time has been set as "3 send with application own transaction" in the output type setup?
because in my system,no idoc is generating.
Kindly provide your views.
Thanks.

Hi,
When the Despatch time has been set as "3 send with application own transaction" in the output type,
It means the IDoc will be processed by an local 'z' program based upon NAST entries.
You have to develop an Z program with help of ABAPer to generate the IDoc based upon table 'NAST' entires.
regards
Vivek.

IDOC Sender

hi all
Am doing a scenario with Idoc as sender. I ve send the IDoc successfully from r/3 system. But nothing is reaching xi. Is there nythin to be done at xi part. Any port to be created . Please help me

Hi,
For sender case u just need to create RFC destination with that R/3 system on XI box.
Got to tcode SM59 create RFC destination then go to R/3 system resend IDOC and then go to tcode IDX5 in XI and then check if there is any inbound iDOC entry in XI.
If it is there then create port with tcode IDX1 and check IDOC metadata with tcode IDX2.
Thanks.

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) 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 XI 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.

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

IDoc packing with PI 7.1 EHP1

Hello,
how does IDoc packing (EHP1) work within a IDoc sender channel? Has anybody already tried it? Can I simply recieve "collected" IDoc from ECC (e.g. invoic IDocs) which are not splitted by IDoc adapter? So that I do not have to use a collect BPM any more?
Thanks!
Christoph

> that means I have to "create" an IDoc sender channel to receive IDocs from ECC? How can I define whether IDocs should be received via this IDoc sender channel or via the "standard" IDoc adapter?
>
Yes, you do have to create an IDOC sender channel. The IDOC packaging option in the CC distinguishs a standard idoc channel from idoc channel with packaging.
> How to define the IDoc package size when I don't know how many IDocs will be sent from ECC to PI?
I would recommend you to watch the below video from the timeslot 00:45, you will http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/40a412a0-9501-2c10-cb83-f124e23d5373&overridelayout=true
Pooja

IDoc to IDoc Scenario with High Volumes

We have requirement to load around 2.4 million idocs using XI from source SAP to target SAP system in ~8 hours. It's a IDoc to IDoc scenario with simple mapping involved.
I Have looked at various weblogs with the design optons such as BPM collect pattern, collect pattern using IDoc XML file and IDoc Packaging.
I am looking for inputs from real time experiences on such scenarios...i.e performanace statstics, best practices to handle such scenarios, hardware, XI basis tuning etc...
Please share any experiences on the same...
Regrads
Anand

Thanks Michal and Chandra...
Chandra,
I have looked into the weblog mentioned( option 2 - collecting idocs using IDoc XML port).
I undersatnd that performance would also depened on hardware,tuning, idoc size, mapping complexity etc, but just get a rough idea and to decide on the design I was looking for stats, approaches followed in other projects and past experiences in such scenarios.
Michal,
I cannot avoid collection of idocs as sending idoc's individually from source to target will have performance problems.
I can avoid BPM by using IDoc XML port collection ( option 2).
2.4 million idocs in 8 hours would mean that XI needs to process 300K idocs per hour. I guess I need to try option 2 and check the performance.
Regards
Anand

R/3 to R/3 IDOC Sending with HTTP

Similar Messages

Maybe you are looking for