AS2 common practices and party definitions

[Former Member]

Dear reader,

I've a question about AS2 identifiers and common practices as is explained in more detail below:

<b>Context</b>

We have implemented Seeburger AS2 adapter on SAP XI.

In our SAP XI environment we have depict parties in SAP R/3 (customers vendors etc) in SAP XI as well to enable clear depiction of message flows.

For large companies we may find several SAP XI parties because the company may have and an office in Canada and an office in the US. (These are two parties in the SAP R/3 system as well)

The company uses <u>one</u> AS2 server to communicate.

Seeburger AS2 adapter allows <u>one</u> AS2 identifier to be defined for <u>one</u> SAP XI party. It is not possible to define the same AS2 identifier for two SAP XI parties.

<b>Questions</b>

Is it common practice for large company to use <u>one</u> AS2 identifier for all their offices? Can we expect to have <u>several</u> AS2 identifiers, one per office?

If large companies only use one AS2 identifier is it wise to introduce a new SAP XI party specifically for AS2 communications and tigh the AS2 identifier to this party?

Note the questions above only apply to inbound processing. For outbound processing the sender and receiver party (AS2 identifier) can be set using a header map in an receiver agreement.

Your help is appriciated.

Best Regards,

Harald Kastelijn

Message was edited by:

Harald Kastelijn

[Former Member]

Harald,

I think that the best way is to create different services for every division under the party (company) with multiple divisions. (Exp. for Party BMW you can have services BMW_DE and BMW_USA). AS2 ID is unique and even for large companies (if they have one IT department) is possible using of the same AS2 ID.

Regards

Naycho