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

Similar Messages

  • ALE Audit for a Partner Type LI (vendor)

    Hi all,
    I'm receiving an invoice from a 3rd party system throgh the inbound Idoc INVOIC01. This Idoc does not work with an Partner type LS (Logical System).
    By the other hand I'm trying to make the configuration to request the acknowledgement through an outbound Idoc (ALEAUD01), I have read that this Idoc is only possible for Idocsof type Logical System (LS).
    Do you know if is possible to use the Idoc ALEAUD01 for a Partner Type LI (vendor)?
    I will appreciate any suggestion, regards!
    Jaime S.

    Yes, standard RBDSTATE program selects idocs from edidc for confirmation based on 'LS' partner.
    SELECT sndprn mestyp mescod mesfct credat cretim docnum status
          FROM edidc INTO TABLE t_idoc_control_all
          WHERE upddat IN s_upddat
            AND sndprt = c_prt_logical_system
            AND sndprn IN s_sndsys
            AND mestyp IN s_mestyp
            AND mescod IN s_mescod
            AND mesfct IN s_mesfct
            AND status <> c_status_in_archive_reload
            AND status <> c_status_in_archived
            AND status <> c_status_in_orig_of_edited
          ORDER BY sndprn mestyp mesfct mescod credat cretim.
    As suggested in separate thread, you can copy RBDSTATE into your own program and change this selection.
    Regards,
    Dominik Modrzejewski

  • 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

  • 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

  • Partner Profile and its configuration.

    Hi all,
    I am creating an SD IDoc using EDI and send it between two servers.
    I need to know what is a partner profile and why should we create it.
    what are the steps to be followed in maintaining a partner profile and its configuration.
    Any pointers will be highly apppreciated.
    Thanks in advance,
    Regards,
    Jose
    Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

    Hi Jose,
    Below is a material you can go through .
    Creating an Outbound Partner Profile
    Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
    If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
    1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
    Key Fields
    2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
    Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type “LI” (vendor) and must choose the Message Control value “VD” (vendor) as the partner function because orders must always be processed using Message Control.
    3. Specify the business process with the “logical” message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type “ORDERS”. You can further divide the message type with the optional fields message code and message function.
    4. Configure the test indicator if you want to send the message as a test.
    Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
    Other Fields
    5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
    6. You have already defined the Recipient port in Port definition.
    7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
    You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
    8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
    9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
    The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
    10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
    11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
    12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
    13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
    14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
    Graphic: Outbound partner profile fields (general)
    Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
    Regards,
    Praveen

  • 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 output type not getting configured in IDoc-File scenario

    Hello
    I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
    1] Created output type
    2] Created partner function as EDI LS for this output type
    3] Configured RSNASTED as Processing Routines for output type
    4] Included this output type in the Header output procedure
    5] Configured XI system as the partner in partner profile with appropriate Message control
    Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
    I checked in SPRO but could not find such flag.
    Does anyone had came across such output type configuration.
    Thanks in advance.
    I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
    Regards
    Rajeev

    Hi,
    Please check the following
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    Copy NEU to ZNEU or YNEU
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
    G.Ganesh Kumar

  • Message "Wrong partner type LS" in message control

    Hi All,
    I am trying to send PO's out to a middleware system. I have configured the middleware system as a LS (logical system) done all the config required for Message control.
    But when I enter Output type = NEU and Medium = A (ALE) and Partner Function = LS and partner name and save the PO, I get the error "Wrong Partner type LS" in the processing log for that message. The details description says "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed.". But i need to send it to partner type LS.
    Am I missing anything. Please Advise.
    Thanks in advance

    Hi!
    'By default' purchase orders can be send to vendors or plants - the two parties in the document. This is linked to the two different partner types KU and LI. Only partners of this type of a purchase order can be used to send data.
    Check, if you can create a partner definition (WE20) for KU (hopefully you have less plants then vendors).
    You also need a partner determination for the document - only out of this partners automatically a message output can be assigned.
    Regards,
    Christian

  • 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

  • Partner Function in Vendor Master With Internal Number Range

    Hello Friends,
    I am creating vendor master record with internal no range.I wanted following clarifications.
    1.In partner function screen, I want to have same vendor no which i am creating to be assigned automatically to VN.OA PI and GS funtions at the time of its master creation.This is not happening in my case
    2.Partner function like VN,OA,PI and GS does not appear automatically whereas i have to select it manually.
    Regards
    Vivek

    Hi,
    During defining the partner Schema, please follow the process:
    a.Create partner Schema
    b.After creation of partner Schema, select your partner Schema and click u201Cpartner roles in schemau201D and you will have next screen
    Now for Partner function like VN,OA,PI and GS as you required and select the check box of mandatory
    and save.
    Now try creating Vendor and you will have Partner function like VN,OA,PI and GS in vendor master.
    Note: The following configuration steps for Vendor master are:
    1. Create Vendor Account Group.OBD3
    2. Maintain Number Ranges from Vendor account Group:XKN1,
    3.Assignment of Number ranges to Account Group,OBAS
    4.Partner Function: SPRO->MM->Purcahsing->Partner Determination-> partner roles->Permissible partner role sper account group
    5.Partner Schema:
    SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Define partner Schema
    6.Assgin partner schema to accont Group
    SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Assgin partner schema to account Group
    Regards,
    Biju K

  • Creation of new partner function for VENDOR

    Hi,
    I've a requirement to create some Partner functions for vendors while creation of vendor. Some Partner functions are available by default and some we need to add. but while doing a BDC we are not able to find how many of them are available or where to put the new Partner function?
    Please let me know, if there is any BAPI availble..
    Regards,
    Anupam

    Try below LSMW batch input method its very esay to upload data
    Object               0040   Vendor master
    Method               0001   Standard
    Program Name         RFBIKR00
    Program Type         B   Batch Input

  • 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

  • Partner Function for Vendor

    Hi Friends,
    I have requirement in partner function, when I configured a new partner function ZH and create vendor it auto picks up the this PF and same vendor number... but my requirement is number needs to blank and it should not be mandatory.. is it possible to achive this
    Thanks in adv
    Bhargava

    Hi
    I require typically like this by default
    PF          Name              Number        name
    VN         Vendor              12546           xxxx
    OA         ordering add     12546        xxxx
    ZH         Head office       ______          
    here for ZH number needs to blank but system expects if some thing is there in the PF then corresponding entry needs to be there in the number column.
    How to achive this
    With regards
    Bhargava
    Edited by: Bhargava ms on Mar 12, 2008 2:29 PM

  • Receiver partner type in control record is default"

    Hi all,
    I am Getting 56 Error"Receiver partner type in control record is default".
    When I go to that perticular IDoc under control record under parter tab I am providing "PARTNER TYP" AND PORT.When I save these details th idoc is getting posted.
    The  port ifo is present in we21.I checked RFC Destination,It is fine.
    Now where to give this information centrally since I have to manually enter this every time.
    Thanks,
    SrinivasaP

    Hi,
    If error is 56.
    Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
    If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
    Please check receiver IDoc Adapter is configured with the said details are not.
    And if possible map the values in EDI_DC40 control record.then you need not to give these details every time.
    Regards
    Chilla..

  • What is the difference between partner function and partner type

    Hi Gurus,
    What is the difference between partner function and partner type?
    Thanks,
    Paul

    Hi John,
    The partner types allow us to distinguish between different business partners such as customer, vendor, employee etc and the partner functions represent the functionality or role each partner plays within the business transaction.
    For example under the partner type Customer, you will find - Sold to party, Ship to party, Bill to party, Payer.
    The business partners that exist in the market place are represented with a partner type in the R/3 system. Examples of business partners are customer, vendor, employee and contact person.
    The following partner types are defined in the partner processing for the sales & distribution module –
    a.     AP – contact person (06)
    b.     KU – customer (07)
    c.     LI – vendor (08)
    d.     PE – employee/personnel (09)
    Assigning the partner functions in the SAP system determines the functions of particular partner in the sales process. One partner may take on several functions also.
    REWARD POINTS IF HELPFUL
    Regards
    Sai

Maybe you are looking for