Skip to Content

SAP B2B inbound scenario to use same EDI separator channel for Different parties and interfaces

HI Experts,

I'm new to SAP B2B. Could you please clarify the below points. It would be so much helpful to me.

1) Since sender and receiver id are maintained in the channel but not in the TPM this will leads to create multiple edi separator channels whenever party is changed. Can't i use the single EDI separator sender channel for different parties for same 945 inbound channel ? Please clarify

2) If the option 1 is not possible can't i use the same edi separator sender channel for a single party for all the ANSI transactions like for 810, 850, 945? Please clarify.

If both the options are not possible please suggest me any other approach instead of creating different EDI separator sender channels for different parties and for different interfaces.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jan 04 at 04:32 PM

    Hi Satish,

    We use the one you have presented in option #1 but we have a separate channel per transaction set so we don't mix different types of processing into one larger flow. Not all of our flows have the separator in use but we are currently using it for 867 and 997 transaction sets without any issues.

    Regards,

    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 05 at 04:41 AM

    Hello Sathish,

    A single EDI channel can process multiple partner files of 945 if you maintain .*

    It all depends on requirement better way is to define one channel for one party(with each unique identifiers).

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 05 at 10:07 AM

    HI Raghuram and Ryan,

    Thanks for your inputs. I'm able to achieve both the functionalities by Keeping the * wherever possible.

    1) My first point in the question is Generic to Party and Specific to Transaction set i can achieve this by keeping the Sender id, Identifier and receiver id, identifier as * and mentioning the transaction set identifier code as 945.

    2) My second point in the question is specific to party and generic to Transaction set i can achieve this by keeping the Transaction set as * and filling the other details in the EDI Separator sender communication channel.

    Thanks,

    Satish.

    Add comment
    10|10000 characters needed characters exceeded