Skip to Content
author's profile photo Former Member
Former Member

Idoc to File. Partner type as 'KU' and 'LI'.. Acheivable w/o using Party's?

Hi all,

Idoc to File scenario.

I have the receiver partner type as 'KU' and sender partner type as 'LI'.

I want to create the scenario without using party for these partner Types.

Is it possible for me to create the B2B scenario without using party's?

Is it mandatory that we need to use partys and Identifiers for these kind of scenarios?

Kindly let me know if anyone has idea on this.

Thanks

-Seema

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 05, 2008 at 02:16 PM

    Hi Seema,

    If the outbound Idoc has RCV partner type (RCVPRT) as KU in the control header and Sender Partner Type (SNDPRT) as LI; the inbound Idoc adapter will use these values when normalizing the IDoc into IDoc XML and will look for the corresponding RCVPRN and SNDPRN values in the Party Identifiers, if found will determine the RCV party at that step and add the information to the SOAP header of the XI message. In such case you can choose to use the virtual receiver determination.

    But if you want to configure the scenario without party at the receiver end - that would be possible...........create an Service without Party and use it in the Receiver Determination step...........the scenario will work fine without a Receiver Party. But if SNDPRT is LI - then you need to define a party with proper Party Identifier set for the sender. If the sender partner type is LS then the the entire scenario can be defined without party even if the RCVPRT is KU.

    But theoritically we shouldn't call it a B2B scenario then- if there are no parties involved at all. But you can still do that practically 😊 B2B scenario without party!

    Regards,

    Suddha

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Seema,

      This warning is quite obvious and valid.

      When you look at the party configuration from an outbound scenario perspective: you will think - what's the problem? I can have more than one Identifier Values with the same Agency/Scheme pair. All those numbers as BS_SAPR3 | ALE#KU will resolve to the same party. Yes, that sounds logical.

      But if we think of the same party being used in the Inbound Scenario? Then can you see a big logical conflict while populating the IDoc header for the SNDPRN value for the corresponding Party? For party "ABC" the Agency/Scheme pair BS_SAPR3 | ALE#KU has multiple values!!!!!!!!!!!!! Which one is correct and how would XI make a decision which one to choose?

      So that's quite obvious.

      In this case I will suggest you that, do not bother about Configuring the Receiver Party identifiers for the outbound scenario. Just set for one say 36. For other values, Idoc adapter wouldn't be able to resolve the RCVPRN value into a Receiver Party - but that shouldn't be a problem - you can always specify the Receiver Party in Receiver Determination step. This should work as a solution to your problem in hand.

      Let me know if this one works as well. It's always good to see that my suggestions being helpful to solve others' problems 😊

      Regards,

      Suddha

  • author's profile photo Former Member
    Former Member
    Posted on Aug 05, 2008 at 01:21 PM

    >>Is it possible for me to create the B2B scenario without using party's?

    Well i m working on the same scenario and i m using Party for both KU and LI.

    When we send messages from R/3 you will have sender of type LS so you dont need any party in Integration directory for sender,but if the receiver if of type KU,then this must be defined as of type KU in WE20 and use party(for receiver) in Integration directory.

    So for IDOC to external partner scenario(KU),you wont have any party on sender side but will have 1 party on the receiver side.

    Thanx

    Aamir

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.