Skip to Content

Party,Business System & EDISeparator in B2B Scenarios

Hi Experts,

Started with my developments in ANSI X12 EDI Transactions.

There are few doubts mentioned below -

OUTBOUND

(Paty? or no Party)|ECC Business System --> PI --> Party|Business Component

We will have a party for the Landscape of our client. But, when I am giving the party with the business system, I am unable to trigger the IDoc from ECC system. Getting the below error -

So, do we require a party or not? If yes, do we need to do some settings in ECC?

INBOUND

Business Component -->PI -->(Paty? or no Party)|(EDISeperator Common)Business Component(Dummy Flow, for all the inbound interface)

(Paty? or no Party)|(EDISeperator Common)Business Component -->PI --> ECC Business System


In this,

1) Do we need a business system or business component for EDISeparater adapter. Which is preferable and why?

2)Is party required or not? As flow will increase if we keep party.

Please suggest.

Thanks,
Nidhi

mlmlmml.png (8.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Apr 04, 2016 at 07:24 PM

    Hello Nidhi,

    for your outbound scenario:

    Nidhi Srivastava wrote:

    OUTBOUND

    (Party? or no Party)|ECC Business System --> PI --> Party|Business Component

    We will have a party for the Landscape of our client. But, when I am giving the party with the business system, I am unable to trigger the IDoc from ECC system. Getting the below error -

    So, do we require a party or not? If yes, do we need to do some settings in ECC?

    You do not require a party. ECC to PI/PO communication via standard settings work without party - as you create a business system within your SLD and import it to your Integration Directory.

    So your communication configuration will look like ECC_BS -> Party|BC

    Nidhi Srivastava wrote:

    INBOUND

    Business Component -->PI -->(Paty? or no Party)|(EDISeperator Common)Business Component(Dummy Flow, for all the inbound interface)

    (Paty? or no Party)|(EDISeperator Common)Business Component -->PI --> ECC Business System


    In this,

    1) Do we need a business system or business component for EDISeparater adapter. Which is preferable and why?

    2)Is party required or not? As flow will increase if we keep party.

    Please suggest.

    1) You are free to use a BS or a BC for your EDI Separator. I prefer to use a BC as I am free to use dummy interfaces for my EDI messages. E.g. I receive X.12, Edifact and Odette messages and I forward them to a common EDI Separator business component with a single dummy interface and a single edi separator receiver channel.

    You can use any BC/BS with a edi separator receiver channel.

    2) It depends on your scenarios. If you use the edi separator sender channels for starting points of your configuration, you will have to use something like parties. E.g. Business Components named like your edi partners, e.g. *|BC_WALMART or *|BS_General_Motors.

    You are free to organize your edi landscape at your needs.

    In my scenarios I use the parties to determine the incoming edi messages by the edi separator channels.

    Kind regards

    Konrad

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Nidhi,

      you do not need a party for inbound communications. However you will need to distinguish between different inbound communication partners - so:

      I recommend to use party in inbound and outbound communications.

      Why?

      - You have an easier monitoring within PO.

      - You can use TPM for inbound and outbound communication.

      - You set up an internal standard for these integration patterns.

      Kind regards,

      Konrad

  • May 26, 2016 at 06:15 AM

    Hi Experts,

    Can you please confirm on my conclusion, is there any risk in this approach?

    Thanks,

    Nidhi

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Nidhi,

      For inbound cases we need to create two ICO's the flow will be

      partner--->EDI receiver (files get splitted based on ST segments)

      EDI sender----> ECC( IDoc's will be posted)

      in order to post the IDOC's than we need to maintain partner profiles in ECC and that corresponding value should be mapped in PI

  • May 27, 2016 at 06:47 AM

    Hi Nidhi,

    kindly refer the below link for sample b2b scenario.

    B2B- EDI Inbound -Step by Step Configuration

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 06, 2016 at 11:42 PM

    Wherever you need an AS2 channel for communication beyond your firewall, see to it that it is tied to a Party representing your Business Partner. Does not matter if the AS2 channel is sender or receiver. Its as simple as that.

    SM.

    Add comment
    10|10000 characters needed characters exceeded