Reduce E1EDKA1 in IDoc regarding partner type

Hi,
im looking for an "non SAP XI" way to reduce the E1EDKA1 in the ORDERS IDoc.
I want the following:
IF E1EDKA1 PARVW = AG then the segment shouldn´t be reduced.
IF E1EDKA1 PARVW = WE then the segment shouldn´t be reduced.
IF E1EDKA1 PARVW = ZZ then the segment muste be reduced.
any ideas to realize that ?
I tried with BD56  and filtering technics but without success
Thx,
Gordon

Hi,
It can be done with user exit "EXIT_SAPLIEDP_902"
Regards,
Aubin

Similar Messages

  • Idoc Scenario Partner type not LS

    Hi experts ,
    we have gone through  https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a&overridelayout=true for idoc scenario where idoc partner type is not a logical system .Now we are working on case2 scenario in above document.we have some confusion in the configurations at R/3 side.Can somebody explain the step by step configuration at R/3 side.
    Thanks.

    Hi Mark,
    For your requirement you, create partner profile for LS with following steps :
    Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
    Message Type      : INVOIC
    Under Outbound Option u2013 Tab
    Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
    Pack Size           : 1
    Transfer IDoc Immediately (Select)
    Basic Type           : INVOIC02
    Cancel Processing After Syntax Error (Select)
    Under Message Control - Tab
    Application           : V3
    Message Type      : RD00
    Process Code           : SD09
    Hope, your problem will get resolve.
    Regards..
    Imran

  • Regarding Partner Type LI (Vendor) configuration

    Hi All,
    My scenario is File > XI> IDOC (INVOIC02 Idoc) Partner Type LI
    I had configured WE20 in receiving System for Partner Type LI and given the Process code details.
    Now in XI what are the steps that i need to configure( For Partner Type LI Vendor Only)?
    DO we need to create Parties for both Sender System and Recieving System?
    Please suggest with the various steps to be done for Hanling Partner Type LI in XI .
    And i think in receiveing SAP system only WE20 is enough for Partner Type LI ... correct me if i am wrong.
    Thanks and Regards,
    Sridhar Reddy

    Sridhar,
    I don't think because of change in partner types whether LI or KU...etc settings at xi will chnage :
    It is going to be same :
    1. Idoc Import .- through IR
    2. RFC destination pointing to R3
    3.  Port creation - IDX1 using the rfc destination created at step 2.
    Apart from this partner profiles needs to created at r/3 end .
    Regards

  • Outbound INVOIC idoc to partner type LS

    Hello,
    We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02)  to a 3rd party who will be doing the billing on our behalf.  We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
    We can create the idocs if we setup our partner as a KU customer.  However, given that we are sending these to a 3rd party system, it seems that we should be using LS.  Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
    Thanks in advance.
    Mark Monroe

    Hi Mark,
    For your requirement you, create partner profile for LS with following steps :
    Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
    Message Type      : INVOIC
    Under Outbound Option u2013 Tab
    Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
    Pack Size           : 1
    Transfer IDoc Immediately (Select)
    Basic Type           : INVOIC02
    Cancel Processing After Syntax Error (Select)
    Under Message Control - Tab
    Application           : V3
    Message Type      : RD00
    Process Code           : SD09
    Hope, your problem will get resolve.
    Regards..
    Imran

  • Regarding Partner types LI and KU in WE20 transaction

    Hi,
    I want to send a purchase order to a particular vendor through EDI. When ever I create a PO if the customer is CUST1(for example) and vendor is VEND1(for example) then only EDI should trigger. Pls give me the possible configuration steps. <b>Is it possible by using LI and KU partner types in WE20.</b>
    Points will be awarded for all helpful points.
    Thanks&Regards
    Giridhar Karnam

    Hi Giridhar,
    Please check the tab Permitted agent that might be used for specifying the vendor name.
    I think these validatikons can be carried out while executing the Function Module.
    Regards,
    Ravi G

  • Posting IDOCs with partner type SP ?

    We have to post IDOCs to SAP where the partner type is SP . How do we configure XI to achieve this ?
    We are disabling the control record and so not looking at the option of hardcoding the EDI_DC record.
    I understand we need to specify Alternate identifiers in IDOC channel and also choose header mapping in receiver agreement, however am not very clear on the steps.
    Can neone help me with the steps.
    Thanks
    Saravana

    I need values something like below to be in the control record of the IDOC and could not find a way of doing it
      <SNDPOR>PORT1</SNDPOR>
      <SNDPRT>SP</SNDPRT>
      <SNDPRN>ServiceProvider1</SNDPRN>
      <RCVPOR>SAPS32</RCVPOR>
      <RCVPRT>SP</RCVPRT>
      <RCVPRN>ServiceProvider2</RCVPRN>
    By default , the SNDPRT & RCVPRT carry the constant "LS"(i still do not get y this is enforced by the IDOC adapter). Our sender system is a FTP server & receiever is SAP system. We have the Business Systems defined as service without party.
    I tried hardcoding the values in EDI_DC40 in message mapping, but the IDOC adapter removes(!!) it and creates its own header(inspite of the chk box being unchecked or checked!!?? in the communication channel configuration)
    Christoph , i could not make out much out of the thread u ve pointed to.
    Thanks
    Saravana

  • Partner types

    Hi all,
                I need some clarifications regarding partner types .i am sending a IDOC ORDERS.ORDERS04 purchase order and recieving   ORDERS.ORDERS04  as sales order .in this two cases in partner profile what showuld i configured.
    and what would be the process code.
    Regards
    Rao

    Rao,
    As you mentioned <b><i am sending a IDOC ORDERS.ORDERS04 purchase order and recieving ORDERS.ORDERS04 as sales order ></b>
    So according to this it is related with SD Module, So Process code to be used in this will be <b>ME10</b>.
    <b><I need some clarifications regarding partner types></b>
    In this case your parner types will be <b>LI</b>.
    Regards,
    Sarvesh
    Message was edited by:
            Sarvesh Singh

  • IDOC-XI-EDI : Sender Party in IDOC with LS Partner Type

    Hi
    Does anyone know of a way to have IDOCs sent from SAP to XI to arrive with a sender party. <b>Note</b> The Partner Type of the original IDOC is LS. [I know how to do this with e.g. KU Partner Type.]
    Thx, Duncan

    Duncan,
    Normally when the partner type is LS there is no need for a Party?
    Can you let us know why you want to configure a party when the Sender Partner type is LS?
    Meanwhile, thought I have never given this a shot, in the party why dont you try adding the agency , scheme and identifier with the corresponding scheme as ALE#LS . If it works well then the target is achieved but if it does not , then I dont think for LS this is possible.
    Regards
    Bhavesh

  • 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

    Hi Seema,
    I appreciate that you chose to go with the parties
    That should be called a good design decision.......
    Now answering your query regarding the party identifiers
    Idoc to File :
    <SNDPOR>SAPDL1</SNDPOR>
    <SNDPRT>LI</SNDPRT>
    <SNDPRN>90000</SNDPRN>
    <RCVPOR>SAPXI</RCVPOR>
    <RCVPRT>KU</RCVPRT>
    <RCVPFC>SP</RCVPFC>
    <RCVPRN>36</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency : LD1_001
    Scheme: ALE#LI
    Name: 90000  (vendor number set in WE20 in the R/3)
    For Receiver Party (say party EXTERNAL)
    Agency: LDI_001 (SID_<client> BS as defined in SLD)
    Scheme: ALE#KU#AG  (AG for partner function SP)
    Name: 36  (customer number set in WE20 in the R/3
    This will resolve the IDoc header data into the following XI SOAP header information:
    Sender Party - INTERNAL
    Sender Service - LD1_001 (say this is the business system defined for logical system SAPLD1
    Receiver Party - EXTERNAL.
    Though, you can determine the receiver party alongwith the Receiver Service later at RCV DETERMINATION step, as I have said earlier.
    Yes, for outbound you have to maintain the identifiers for Sender Party type LI, but you can still skip the Receiver KU type and update the SOAP header at RCV DET step.
    File to Idoc:
    <SNDPOR>SAPXI</SNDPOR>
    <SNDPRT>KU</SNDPRT>
    <SNDPRN>36</SNDPRN>
    <SNDPFC>SP</SNDPFC>
    <RCVPOR>SAPDL1</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPRN>MAINSAP</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency: LD1_001 (SID_<client>)
    Scheme: ALE#KU#AG
    Name: 36
    For Receiver Party (say party EXTERNAL)
    Because the RCVPRT value is LS , no need to set the Receiver Party for that.
    But if you want to have some Receiver Party value for the same you can use Header Mapping in receiver agreement.
    Mandatory Setup in Receiver IDoc Adapter:
    Set the indicator -  Apply Control Record Values from Payload
    Remember to set the Identifiers in the Identifiers Tab in Idoc channel.
    Sender:
    Agency : LD1_001       Scehma : ALE#KU#AG
    Receiver:
    Agency: LD1_001        Schema : ALE#LS
    I am not sure why this ALE#LS entry is required, but according to my experience if we don't have that entry, the Idoc Adapter throws error while converting the Receiver Party (considering you use party in the ID configuration for both Sender and Receiver).
    Yes you are right, you can hard code the SNDPRN, RCVPRN values in the mapping and can take the values from payload...........for that set the following Indicators in Idoc channel:
    Take Sender from Payload
    Take Receiver from Payload
    Let me know if you have any concerns or any additional observation you make while configuring the scenarios. Thanks.
    Regards,
    Suddha

  • Wrong Partner Type in IDoc with message type REMADV

    Dear all,
       We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
    Does anyone know how to change the partner type from the Idoc generationg?
    Many thanks,
    Ronny

    Hi,
    Welcome to SDN.
    Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
    Regards,
    Ferry Lianto

  • IDoc Acknowledgement -  ALEAUDIT for partner type B

    Hi,
    I have a scenario where ALEAUD ack required for partner type B instead of LS.
    What are the ways by which i can configure ALEAUD ack for partner type B?
    Regards,
    Anurag

    Hi Anurag,
    ALE AUDIT is the technique of using IDocs for communication.
    ALE Audit it is used to check the cross-system IDoc flow and posting the data in the partner system.
    please gone through this related blog blog , it may be helpful for you.
    http://wiki.sdn.sap.com/wiki/display/Snippets/ALEAuditfor+DEBMAS
    Regards,
    Sudeepth

  • Idoc partner type LI to File Scenario.

    Hello Experts .
    I have the following scenario.
    IDOC partner type LI to xml (file).
    So we are not atlking about logical system here and we may have to use parties.
    But I am not sure as to how to go about this approach.
    For now we have Idoc coming into XI but failing after that .(Outbinding) error in reciver agreement (not to be confused with a cache issue .).
    But I understand it is because of the parties not defined properly.
    So I have defined a party and assigned my ECC system to the same.File was basically a service.Do I need to define another party for it or several other identifier
    Tried to follow How Tou2026
    Sample IDoc-XI
    Scenarios  document but it is to confusing.
    Kindly help

    Thanks for your reply.
    Well I have already tried this approach.
    That is
    Created a party :Sender_party.
    Identifiers :
    <sapid><client>   :*ALE#LI*  :<venderno>   actually ALE#LI #LF "otherwise I end up with party service not found.
    Receiver determination:
    sender party
    <BS/service> i.e. <sapid><client>     to  mail_service (for testing to see if I recieve a payload)
    <interface>
    <urn>
    Interafce determination
    sender party
    <BS/service> i.e. <sapid><client>     amd   <interface>  interface mapping
    <urn>
    Reciever agreement.
    mail_service  : reciever mail adapter.
    Error recieved.
    <!--  Technical Routing
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>-DMGCLNT400</SAP:P1>
      <SAP:P2>Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver agreement found for sender -DMGCLNT400 to receiver Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Kindly note nothing is wrong with cache .
    It is strange DMGCLNT400  is already assigned to the party . .

  • IDOC sender/receiver partner type LS?

    Hi,
    I am in need of advise if SAP 5.0 can be configured for ORDERS outbound (PO NEU) to pick up receiver (KU) partner type by standard config?
    I understand that there's exit available but would like to utilise standard application config method.
    Regards,
    Viv
    will definitely award points for the help!!

    if i understood u right this might help you
    1. /people/shabarish.vijayakumar/blog/2006/09/13/wanna-party
    2. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

  • IDOC-File  Can Partner Type be KU or LI ?

    Hi All
    I am sending IDOC from R/3 system to XI.
    Can partner type for XI be LI or KU?
    What my assumption is,  whenever R/3 sends IDOC to XI, it treats XI as LS always. So partner profile configured for XI will be under partner type LS
    Please correct me if I have any misconcept.
    Thanks in Advance.
    Mugdha Kulkarni

    You are correct.
    Mudit

  • Partner type -only logical system?

    Hi!
    I have a scenario where I want to send an idoc to SAP using XI idoc adapter. It works fine using a partner type "logical system" (LS). But now i would like a scenario where the partner i a type "customer" (KU). I have defined a new business system in the SLD as a sender (just in case) and the partner of course exist in SAP under customers). I have also mapped the korrekt values to the IDOC (sndprt, sndpor and so on) -but these are of course overwritten using the values from the SLD (which only operates using logical system). Is there a way to integrate using a partner of type customer? I have made a similar scenario work using the Business Connector -what is the missing link to make it work in XI?
    best regards

    Hi Martin,
    > I have a scenario where I want to send an idoc to SAP
    > using XI idoc adapter. It works fine using a partner
    > type "logical system" (LS). But now i would like a
    > scenario where the partner i a type "customer" (KU).
    This is not foreseen in XI 2.0. You need to wait for XI 3.0, there it will be possible.
    Regards
    Stefan

Maybe you are looking for

  • How to do custom miro for import purchase ?

    Hi All I want to know what is the process for doing custom miro for import purchase, In my case for some of the excise elements we get credit, so while doing miro how to take care of this ? Thanks Rashid.

  • What is better/newer than SSL3?

    My bank sent me this message: Due to the recently announced POODLE malware, Dollar Bank will turn off access to Online Banking, Cash ANALYZER, loan applications and deposit account opening via our website on October 23, 2014 for visitors utilizing br

  • Too many SMTP connections kills server?

    I have a client who until recently had an old G4 server running 10.2.8. This server crashed regularly, usually when they sent out their email mailshot. I recently put in a new G5 running server 10.4.5 and all seemed well until they sent out the next

  • Abt module pool

    Hi,      can i declare a selection screen in module pool program?      can i use at selection-screen event in module pool program?

  • Exporting movies from FCP to go into Avid

    I've just been told that the guy making the actual DVD of my current programme is using Avid - so I need to export my finished movies in the best format for him to import. Which format should I choose for maximum quality and minimum hassle at his end