cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP Adapter and DUNS scheme - possible bug ?

Steven_UM
Contributor
0 Kudos

Hi Folks,

I am using the HTTP adapter for posting an XML message which is then redirected towards IDOC adapter ... nothing special here ...

I am using the scheme 'DUNS' and agency '016' to pass along the partner identification when calling the HTTP adapter ...

The HTTP adapter tries to match the given partner information and finds the proper XI Party ... BUT ... it overwrites the DUNS number value with the XI Party but leaves the agency and scheme pointing to DUNS ...

An example

Going IN:

Party = 12345789, Agency = 016, Scheme = DUNS

After conversion

Party = MyPartner, Agency = 016, Scheme = DUNS

So the receiver determination works fine and then we go to the IDOC adapter when stuff goes into error as it cannot convert the given sender information into a proper IDOC partner ...

The whole thing works fine when I am passing along

Party = MyPartner, Agency = http://sap.com ..., Scheme = XIParty

then the IDOC is created and send towards SAP ...

I am thinking that the Sender determination in the HTTP adapter goes wrong as the combination

Party = MyPartner, Agency = 016, Scheme = DUNS

is clearly wrong ... Furthermore I have lost my original DUNS number ( so it cannot be used for example in mappings, etc ... )

Anyone had similar issues or problems with this ?

Regards,

Steven

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_grube
Active Contributor
0 Kudos

> I am using the scheme 'DUNS' and agency '016' to pass

> along the partner identification when calling the

> HTTP adapter ...

> The HTTP adapter tries to match the given partner

> information and finds the proper XI Party ... BUT ...

> it overwrites the DUNS number value with the XI Party

> but leaves the agency and scheme pointing to DUNS

Apply note 954645. This should solve the issue.

> Furthermore I have lost my

> original DUNS number ( so it cannot be used for

> example in mappings, etc ... )

The DUNS must be provided in the message payload as well.

Usually the party normalization is done by the adapters in a very specific way. So the RNIF adapter takes the DUNS out of the message payload of the RosettaNet message and does the party normalization with that DUNS.

In the HTTP adapter there is no need for a party normalization as you provide a URL for the HTTP client where you can add the party in the query string.

Regards

Stefan