SAP PO B2B Inbound AS2

[former_member609817]

Hello Experts,

We currently have B2B integration via Seeburger on dual stack PI 7.1 system, and we are trying to move these interfaces to SAP B2B Addon on single stack SAP PO 7.5 system

For inbound interfaces, currently 50+ trading partners are sending multiple incoming messages (invoices, ASNs, etc) via AS2 to a single AS2 endpoint (like as2.companyname.com/as2) where a single AS2 sender communication channel is used to receive these messages and then send to EDI splitter. Authentication and decryption is done at the sender agreement level and so we have a sender agreement for every message type coming from every trading partner.

Going forward in B2B, I understand i need to create 2 ICOs for each incoming interface. First ICO is to send the AS2 message to EDI splitter, and second ICO is from EDI Splitter to ECC IDOC. Also please note, I am not using TPM content extensively.

Now my question related to 1st ICO (from sender AS2 to EDI splitter) is:

1. I am thinking of creating one ICO per message type (INVOIC, ASN etc) per trading partner as we need to authenticate and decrypt incoming AS2 message at the sender AS2 channel level. I cant have a single ICO for all the trading partners as the certificates are different for each trading partner. Is this correct approach?

2. Going forward, trading partners have to send as2 messages to a partner specific AS2 URL (like as2.companyname.com/as2/trading_partner_name). This URL will be used as part of AS2 sender channel (in 1st ICO) for this trading partner in the field "Expected url path" where i specify */trading_partner_name to ensure the incoming message from a trading partner is routed to their corresponding ICO so that authentication and decryption happens. Is this approach correct?

Thanks,

Chandra

[vicky20691]

Hi Chandra,

Both the approaches are correct and will work fine.
but I still recommend you even though you are creating single ICO for each trading partner, use EDISeparator channel for splitting files and handle multiple variants

If there are requirements where encryption/decryption not required you go for single first ICO as optimized development approach.

Regards,

Vikas

[former_member624423]

There is an AS2ID required for B2B process. How to register it?