Quantcast
Channel: SCN : Popular Discussions - Process Integration (PI) & SOA Middleware
Viewing all 971 articles
Browse latest View live

PI 7.0 Proxy to SOAP: SOAP-Fault-handling

$
0
0

Hello,

 

i have some problems handling soap-fault-messages in a proxy-to-soap-scenario.

I have searched the web for about 3 days now and after hours and hours of try-and-error i am running out of ideas.

 

That's why i hope, somebody has got some advice for me...

 

 

Informations about the webservice

 

The webservice is provided by the european community (Documentation, WSDL) and can be used to validate VAT-Numbers.

The request- & response-message-types are defined within the wsdl, but the fault-message-type is not part of the wsdl.

If e.g. a wrong requester-VAT-Number is used, the server does not send a response, but a SOAP-Fault, that is defined within the namespace http://schemas.xmlsoap.org/soap/envelope/.

 

 

What i have done so far

 

I have written a program, that runs on our SAP-Systems. This program is used to check the VAT-Numbers in our system.

 

The communication between our SAP-Server and the server of the european community has to be routed through our PI-System.

The PI should simply forward the webservice-calls of the SAP-System to the EC-Server: No mapping is required.

 

That's why i tried to implement an outside-in-scenario on our PI 7.0.

I imported the WSDL and the XSD-File as external definitions, created 2 message interfaces (sender sync & receiver sync), 3 dummy message mappings (request, response, fault) and an interface mapping (sender->receiver) and set up a configuration scenario.

 

The proxy on our SAP-System was generated from the ESR-data of the PI-Sender-Message-Interface.

 

 

The problem

 

As long as the EC-server replies to our request with an response, everything works fine.

But in some situations, the EC-server sends a SOAP-Fault instead (e.g. when we are sending inconsistent data).

 

These SOAP-Fauls are not forwarded to the SAP-System.

PI is not able to handle the Fault-messages and the proxy on the SAP-System throws an exception of the type cx_ai_system_fault, that has the text "PARSING.ADAPTER.SOAP_EXCEPTION".

 

I need the details of the SOAP-Fault in the SAP-System, that's why i want a SOAPFault to result in an exception of type ZCX_FAULT.

 

mi.png

 

proxy.png

The message-interfaces and the proxy are looking fine to me, but it simply does not work.

 

If anybody has a clue about how to achieve the desired behaviour, any advice would be highly appreciated.

 

 

What i found out so far

 

Using SXMB_MONI, i found out, that PI is trying to handle a SOAPFault as a request

  • The payload shows, that we received a Fault-Message
  • The trace shows, that the mapping of the request is executed

 

fault.png

 

trace.PNG

 

I hope i provided enough information about the problem. If not, just ask and i will add it.

 

 

Regards,

Jörg Neumann


MT940 format sample

$
0
0

Hi,

  Bank statement is comming type MT940 format. can you send me one sample of  MT940 format .and in this format any  attribute like TAG 25 which indicates account number??kindly let me know.

 

Thanks,

Suchitra

ABAP proxy to file

$
0
0

hello everybody,

I'm working with SAP pi 7.1

We designed a interface proxy abap->PI-> file (ftp).

We have some problems with it. Sometimes work, sometimes no. We not implemented ccBPM.

It's necessary use ccBPM in this case? bridge sync - async?

Or maybe exist a more clean solution?

 

thanks in advance

 

Alex

NW BPM in PI7.3.1

$
0
0

Hi Experts,

 

    can i develop the Integration Process (Nw BPM) in ESR instead of NWDA in PI7.31 single Java stack?

 

And, while i am designing i am getting error like "Expression must return the interface type StoresOrder_Asyn_Abs.

 

 

Sceanrio like Mullti file --> IDOC ( external message 0-unbound)

 

Header   --> External Message

Details

 

Message mapping and OM , there is no error ,and designed multimapping.

 

Still i am getting interface type error in my BPM ...Can you please check this ?

 

Regards,

Deva

How to create a REST based webservice in PI?

$
0
0

Hi Expert,

 

   I want to expose my PI interface as REST based web service. I also want to use JSON.

 

   i have already searched the internet but did not get any step by step how to doc or example.

 

   My interface is simple. It contains userid as input.

 

   Web service (REST) -> Pi -> Proxy (SAP R/3)

 

   The user passes the userid as the input to the web service. The PI then calls ABAP proxy in a SAP R/3 system.

   The R/3 returns user details(First name, last name, Age, Address) back.

 

   How my schema should look like in PI interface? What URL I need to send it to calling application (system that calls the web service)?

   What setups I need to do in REST Sender communication channel in order to implement JSON?

 

Thanks

Gopal

Idocs stuck in SM58 in PI - transaction recorded status

$
0
0

Dear Experts,

 

I need your urgent help.

 

I have a file to Idoc scenario in which one file creates two idocs(WGSREQ and WPUBON).We are creating two idocs using 2 message mapping and included in single interface determination. The idocs are set to process immediately in WE20.

For this scenario, the load of messages is very high. High load is generally for Idoc1(WGSREQ). But the other idoc(WPUBON) is important to get posted in SAP before 9pm. But due to high load of first idocs, second idoc messages also get stuck in SM58 coz of which we missed the timelines.

 

Please suggest if we split this one interface into two interfaces, can it solve my problem??

Please suggest any other idea to reslove it.

 

Thanks in advance!!!

Seeburger AS2: Error on send - illegal MDN - content-type not supported

$
0
0

Hi,

 

I build up a connection to a partner to send ORDRSP via AS2.

Unfortunately I'm receiving an error in the Seeburger Workbench:

 

Received illegal MDN - content-type not supported!

 

I set up the content-type: application/EDI-X12. I have already tested different content types, but I always get the error. The whole conficuration is similar to our other partners.

 

Do you know, what this error means and give me an advice please.

 

Thanks a lot

Frank

Empty XML tags in proxy message

$
0
0

Hi All,

 

We have noticed in one of the proxy based interface that the response received from SAP system has empty XML tags in it. However, we expect that there should not be any XML tags for fields where data is not populated. These fields are mandatory and proxy calls should ideally fail in PI with mapping exception, which is not happening currently. Have checked with the ABAP team and they are not passing any value in that field.

In couple of other interfaces, with same ABAP coding, empty XML tags are not getting created.

Has anyone else come across similar problem earlier?

 

Regards,

Sanjeev.


PI 7.31 AEX (SP05): Handle xsi:nil="true" in SOAP response

$
0
0

Hi

 

I'm currently working on sync-proxy to SOAP scenario.

Target webservice expects xsi:nil="true" for a few null fields in the request and in the response also it sends the same for some of the null fields. Source system (ECC) wants blank whereever xsi:nil="true" is present in the response message.

 

I'm using the constant function xsi:nil in message mapping (graphical) and able to send xsi:nil="true" in the request to WS.

In the response mapping, I'm using isNil boolean function. But the SOAP response mapping is failing because webservice sends the namespace associated with xsi (xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance") in the SOAP envelope and PI discards the envelope message.

 

Below is the response sent by webservice.

wsresponse.JPG

  Below is the SOAP response received by PI at mapping step. As xsi namespace is missing in the payload, PI throws mapping error:

Error: The prefix "xsi" for attribute "xsi:nil" associated with an element type "errorField" is not bound.

 

receivedbyPI.JPG

 

  • I've also tried creating an xslt mapping to insert xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" at the root node createWorkOrderResponse. But as the message fails before executing the mapping (while parsing the response xml), it didnt work.
  • I've also used "Do not use SOAP envelope" option and xmlanonymizerbean but nothing worked. The message fails at adapter level.

 

Please let me know my options to resolve this issue. As it's a sync-scenario, I'm trying to implement a simple solution to handle this error.

 

Regards

Praveen.

Content-Transfer-Encoding: quoted-printable in Marketplace Adapter

$
0
0

Hi,

 

I am sending xCBL data to Marketplace using Receiver Marketplace Adapter using HTTPS. We are encrypting the data using PKCS#8 RSA format private key.

 

The Marketplace adapter is generating the MML format data with Header, payload and footer. In the header the Content-Transfer-Encoding it is generating is "quoted-printable". However in the footer it is generating as "7bit".

 

Ideally it should be 7bit even on the header.

 

This is an Inline document. Below is how the document looks like.

 

content-type:application/x-www-form-urlencoded

 

Date: Fri, 12 Apr 2013 13:29:50 1000 (EST)

Message-ID: <1393344183.191.1365737390417.JavaMail.d91adm@pacartspid91>

MIME-Version: 1.0

Content-Type: multipart/related;

boundary="----=_Part_190_722767945.1365737390416"

Content-ID: 3ba05df0-a321-11e2-aa9f-a2825f7dd759

x-Date-Sent: 12 Apr 2013 13:29:50 EST

x-Document-Type: OrderResponse

x-Priority: 5

x-Correlation-Id: 3ba03452-a321-11e2-bdd7-00000010c656

x-Request-Annotation: normal

x-Request-Mode: peer-peer; ack=yes; delivery=express

x-Sender-Id: fc87278c-7a02-1000-9ebe-0a0e06070001

x-Message-Format: Commerce One 1.0 N; owner="Commerce One"; version=1.0; date="June 1999"; variant=N

x-Recipient-Id: 8d3f508a-7a60-1000-aeec-0a0e06070001

x-Message-Id: 3ba05df0-a321-11e2-aa9f-a2825f7dd759

CONTEXT_HANDLE_KEY: CONTEXT_HANDLE_VALUE; sonic_time_to_live_key=0; sonic_sync_queue_correlation_id_key=3ba03452-a321-11e2-bdd7-00000010c656

 

------=_Part_190_722767945.1365737390416

Content-Type: application/xml; owner=x-commerceone; version=1.0;

type=OrderResponse; charset=UTF-8;

ns="urn:x-commerceone:document:com:commerceone:XCBL35:XCBL35.sox$1.0"

Content-Transfer-Encoding: quoted-printable

Content-ID: 3ba05df2-a321-11e2-aa9f-a2825f7dd759

Content-Description: Document

Content-Disposition: inline

 

<?xml version=3D"1.0" encoding=3D"utf-8"?>

<?soxtype urn:x-commerceone:document:com:commerceone:XCBL35:XCBL35.sox$1.0?=

><OrderResponse><OrderResponseHeader><OrderResponseNumber><BuyerOrderRespon=

seNumber>4501022779</BuyerOrderResponseNumber><SellerOrderResponseNumber>00=

00003560</SellerOrderResponseNumber></OrderResponseNumber><OrderResponseIss=

ueDate>20130410T12:00:00+10:00</OrderResponseIssueDate><OrderResponseDocTyp=

eCoded>OrderResponse</OrderResponseDocTypeCoded><OrderReference><Reference>=

<RefNum>4501022779</RefNum><RefDate>20130408T12:00:00+10:00</RefDate></Refe=

rence></OrderReference><SellerParty><Party><PartyID><Identifier><Agency><Ag=

encyCoded>AssignedByBuyerOrBuyersAgent</AgencyCoded></Agency><Ident>6101</I=

dent></Identifier></PartyID></Party></SellerParty><BuyerParty><Party><Party=

 

 

Does the Marketplace adapter generate quoted-printable? My understanding is that it generates 7bit in the header as well.

 

Is there a way by which I can make the header also 7bit instead of quoted-printable? I searched for Module beans, but I could not find any for inline documents using marketplace adapter.

 

This is really urgent.

 

Thanks,

 

Kind Regards,

Mateen

Web Services - How to add namespace to parameter?

$
0
0

Hello,

I`m facing problem with "certification verification failed" during sending signed message via web service.

In my opinion it is because element/parameter SIGNATURE in xml is like:

 

<n2:Signature Id="Signature-0">

 

and should be:

 

 

<n2:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="Signature-0">

 

Originally proxy structure was very complexed element "Signature" so every part we had to put separately.

Now i tried to modify wsdl and set "Signature" as string so we can send only one parameter with correct xml to function module and next to web service.

Now we are able to add everything inside "Signature" but still first element is generated by SAP

 

 

Modified WSDL part is like:

 

 

      <xs:element name="UploadRequest">

        <xs:complexType>

          <xs:sequence>

                              <xs:element minOccurs="0" name="Signature" type="xs:string"/>

          </xs:sequence>

        </xs:complexType>

      </xs:element>

 

 

so in SAP under request parameter we have only Signature type string.

 

 

My question is:

Is it possible to add namespace xmlns:ds="http://www.w3.org/2000/09/xmldsig#" to "Signature"?

If so how can I do this?

 

 

Best regards

Keystoreentry not found in soap receiver channel

$
0
0

Hello experts!

 

I am developing an interface RFC --> SOAP

 

This SOAP call is for an third party web service and my basis team set up a certificate into visual admin in order to be able to communicate with the web service.

 

problem is when i am trying  to configure client certificate authentication in soap receiver channel, i am unable to find the certificate in the  key store Entry list.

 

Can any one tell me what might be the issue?

 

 

Regards,

 

Trinadh

SAP PI Overview 7.1 & 7.3

$
0
0

Hello,

 

i have got two questions right now...

 

1. Are there any presentations giving an overview of the functions that sap pi 7.1 ehp1 provides (not only new features in 7.1)?

Shouldn't be to technical if possible!

 

2. Is there a good website giving proofed information about what new functions are included in sap pi 7.3?

http://www.sdn.sap.com/irj/sdn/nw-soa isn't really useful for that.

 

Thanks in advance!

 

Regards,

Markus

Initial Settings in SAP PI 7.3 after System Installation

$
0
0

Hi,

 

We are installing SAP PI 7.3 here. After media installation by BASIS team, what all other things an SAP PI consultant should maintain/configure(initially before start working on scenarios) ?

Since I have worked on SAP PI scenarios where the SAP PI server was completely ready(set up). This is the 1st time I'm working on completely new SAP PI system.

 

So please guide me at the earliest.

 

Thanks,

Amit Patil

ECC 7.0 implementation

$
0
0

Hi

 

I got an information that SAP has released latest version of ECC 7.0. If it is true then can any one say me where it has implemented upto know

 

Regards

Pavan


MT940 format sample

$
0
0

Hi,

  Bank statement is comming type MT940 format. can you send me one sample of  MT940 format .and in this format any  attribute like TAG 25 which indicates account number??kindly let me know.

 

Thanks,

Suchitra

HTTPIO_PLG_CANCELED in SM59 after upgrade to PI 7.11

$
0
0

Hallo,

 

we upgraded our PI (test) to 7.10 EHP1.

 

When setting up a connection in SM59 we get error code HTTPIO_PLG_CANCELED. When we create this connection on our production PI (without EHP1) we do not get any error.

When we want to send a message to this address, we get <SAP:Stack>Error while receiving by HTTP (error code: 110 , error text:

HTTPIO_PLG_CANCELED)</SAP:Stack> in SXMB_MONI.

 

Can someone tell us how we have to fix this?

 

Greetings.

Kris

PI 7.3 Post Installation steps and configuration.

$
0
0

Hi Experts,

We just had PI 7.3 installed in our landscape. Could someone provide me with documentation on steps and config. to be done on a fresh PI 7.3 machine so that development can be started ?

 

Thanks in advance!

Rasif

SAP PI Transactions

$
0
0

Hi All,

 

Can anyone provide me the list of all the SPA PI Transactions especially those used for Monitoring?

 

Thanks in advance.

How to Delete IDOC

$
0
0

Hi

 

can you tell me how to delete idocs from R/3 system

 

Regards

 

Nawa

Viewing all 971 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>