Regarding AS2 seeburger to idoc interface

[Former Member]

Hi Team,

I hope you are doing well.

I am working on as2 seeburger to idoc interface.

what are the steps required for this in IR and ID ?

where can we monitor if we get the error in as2 adapter side?

Regards

ANJAN

[PriyankaAnagani · Accepted solution]

Hi,

>>>what are the steps required for this in IR and ID ?

In ESR:

1.First you need to get the xsd of EDI document and import it into ESR under External definitions and import the IDoc also into ESR.

2. Create a service interface for the EDI document structure.

3.create message mapping between the ED(xsd of EDI doc) and Idoc.

4.Create operation mapping.

In ID:

1.Configure the parties using the AS2 IDs.

2.Create an AS2 sender communication channel(refer the configuration guide that you receive from seeburger).

3.Create an IDOC receiver communication channel.

All the remaining steps are same what we do for normal scenarios like receiver determination,interface determination and agreements.

>>>where can we monitor if we get the error in as2 adapter side?

In Seeburger workbench

Regards,

Priyanka

[Former Member · Accepted solution]

Hi Priyanka,

Thanks for your quick response .

what as2 ids in id part.?

if i want ack from pi how can we configure syn MDN and asy MDN?

Regards

ANJAN

[PriyankaAnagani · Accepted solution]

Hi,

>>>>what as2 ids in id part.?

WAN network no of the partner who is sending/receiving the file or EDI doc

>>>if i want ack from pi how can we configure syn MDN and asy MDN?

In case of AS2 receiver only you'll have MDN mode (sync/async) but not incase of AS2 sender.

If you want ack you can configure functional acknowledgements through 997.

Regards,

Priyanka

[Former Member · Accepted solution]

Hi,

> what as2 ids in id part.?

Every customer has one unique AS2 id, so you can ask your customer to provide his AS2 ID then you can assign the same AS2 ID in Party.

> if i want ack from pi how can we configure syn MDN and asy MDN?

997 is ack but not MDN.

If you want configure MDN we have 2 options.

MDN is Async then it created the new communication connection between partner and your system so in this case you have to give Receiver Address (http(s)://HOST:PORT/SeeburgerAS2/AS2Server). and set MSN time out as 0.

If you are using Sync option then it uses the same connection to get back the MDN.

Regards,

Venkata Ramesh

[Former Member · Accepted solution]

Hi Venkata Ramesh,

Thanks for your quick response.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ac...

I have gone through your blog.The blog explained AS2 sender adapter configuration very well.

as per the blog why your are using SPLIT997 adapter?

what are the steps need to configure AS2 recevier adapter?

Regards

ANJAN

[Former Member · Accepted solution]

chk this for receiver AS2 adapter:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d095b2df-9fa3-2d10-568b-d12d99828...

[Former Member · Accepted solution]

Hi,

> as per the blog why your are using SPLIT997 adapter?

Every document contains 997 (850 doc is combination of 850+997). Once we receive the signal from customer we need to send back 997 to him and we need to process 850 document further, so internally it is 2 scenarios (EDI850 to 997 and 850 to Idoc).

Split997 splits the 850 and 997 documents, after it splits 997 sends back to customer at that time this 997 acts as sender for 850 document.

> what are the steps need to configure AS2 recevier adapter?

For receiver it is direct cinfiguration (in the com channel we can give seeburger modules).

Regards,

Venkata Ramesh

[Former Member · Accepted solution]

again thanks Venkata Ramesh.

if we have MDN s at recevier side (asyn or sync) .

is there any settings we have to do?

BR

ANJAN

[PriyankaAnagani · Accepted solution]

Hi Anjan,

In case of synchronous MDN, If the handle received MDN option is refer to XI system then we need to create a reports channel i.e AS2 with message protocol as reports and agreement. In case of asynchronous MDN irrespective of Handle received MDN option, we need to create a reports channel and agreement for it.

Regards,

Priyanka

[Former Member · Accepted solution]

Hi,

> if we have MDN s at recevier side (asyn or sync) .

> is there any settings we have to do?

Yes, we have to create sender CC and sender agreement for MDN.

Create AS2 sender communication channel with HTTP transport protocol and Reports as Message protocol then we have to give the Message subject (this subject is same as receiver AS2 channel message subject) and create the sender agreement for this CC. In sender agreement we can give dummy interface name.

No need to create RD, ID and RA for MDN.

Regards,

Venkata Ramesh

[Former Member · Accepted solution]

Thanks to Venkata Ramesh,Priyanka and Amit for your quick replies

My problem was solved.

BR

ANJAN

[Former Member]

How to Configure Sender AS2 Adapter in SAP PI

[configuration|http://www.infoclickaway.com/how-to-configure-sender-as2-adapter-in-sap-pi/]

How to Test AS2 Interface using m-e-c AS2

[test|http://www.infoclickaway.com/how-to-test-as2-interface-using-m-e-c-as2/]

please refer below blog then you will get full information & LINKS About AS2 Adapter:

http://forums.sdn.sap.com/thread.jspa?threadID=630603