cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Inbound AS2 Scenario - Wrong MDN

Go to solution
Former Member

on ‎02-06-2012 6:45 PM

0 Kudos

Hello Experts,

we have an AS2 Scenario with incoming INVOIC and we send MDN back to our partner.

The message exchange works fine, but the structure of our MDN is wrong. The MDN contains only this sentence:

"SEEBURGER AS2 Controller

AS2 message successfully received. "

Where can I configure the MDN structure?

Thanks

Tobias

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
‎02-06-2012 7:23 PM
0 Kudos

>>but the structure of our MDN is wrong.

Seeburger adapters create standard MDN message which should be accepted by the partners. Did your partner complain abaout the structure?

Regards,

Prateek Raj Srivastava

Show replies
Show replies
Former Member
‎02-07-2012 9:56 AM
0 Kudos

Hello Prateek,

our partner gets this message as mdn back. If their any possibilities to configure the MDN. Do we need a separate communication channel for the MDN? Does that its message protocol 'AS2' or 'reports'?

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">

<head>

<title>AS2 Controller</title>

</head>

<body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="#551a8b">

<table cellpadding="0" cellspacing="0" border="0" width="100%" bgcolor="#dc4560">

<tbody>

<tr><td>&nbsp;</td></tr>

<tr>

<td>&nbsp;</td>

<td valign="middle">

<h3>

<font face="sans-serif" color="#ffffff">SEEBURGER AS2 Controller</font>

</h3>

</td>

</tr>

</tbody>

</table>

<br/>

<font face="sans-serif" size="-1">

<b>

AS2 message successfully received.

</b>

</font>

<br/>

</body>

</html>

kind regards

Tobias

Former Member
‎02-07-2012 10:09 AM
0 Kudos

Hi,

Yes you have to create the AS2 sender Communicational channel with Transport protocol as HTTP and message protocol as Reports.

Regards,

Venkata Ramesh

prateek
Active Contributor
‎02-08-2012 12:36 AM
0 Kudos

@Venkat "Yes you have to create the AS2 sender Communicational channel with Transport protocol as HTTP and message protocol as Reports."

Report channels although capture MDN information, they have to be configured for the receiver side AS2 scenario.

Tobias, you may try to configure Report channel but in the recommended configuration, you don't need that. The report channel has its message structure with root node name "dtReport". You may ask your partner if this is what they expect. Ask them for the entire structure they expect if possible. Again, MDN created by Seeburger adapters are generic and should work without any additional configuration unless there is some problem at partner's end.

Regards,

Prateek Raj Srivastava

Former Member
‎02-08-2012 6:04 AM
0 Kudos

Prateek,

Thank you very much for your information

Regards,

VR

Former Member
‎02-10-2012 12:38 PM
0 Kudos

Hello Prateek

"... Again, MDN created by Seeburger adapters are generic and should work without any additional configuration unless there is some problem at partner's end..."

I understand, but how can the partner validate which INVOIC is successfully received? Is there a reference to the invoic?

Kind regards

Tobias Landbeck

prateek
Active Contributor
‎02-10-2012 5:17 PM
0 Kudos

Unfortunately there is no such reference. But this is not the purpose of MDN. MDN is to acknowledge that the message sent is received successfully by partner. Based on the configuratoin, it just specifies that the message has been transferred to the partner without any modification, the partner can decrypt/decompress it. Its more of technical communication aspect than the business functionality.

Regards,

Prateek Raj Srivastava

Answers (0)

Ask a Question