Partner Profile for IDOC - configuration

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Thanks
Rishi

hI,
     Please use transaction code WE20 to generate inbound partner profile
Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.
Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation
<b>*Reward points</b>
Regards

Similar Messages

  • Partner profile for INBOUND IDOC

    Dear experts,
    Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken  to b configure the partner profile  in the R/3 system for the inbound idoc?
    Thanks,
    Priyanka

    Hi
    This is not the right location to post this question.
    You got to post this query in Data transfers section of SDN ABAP Development forums
    Now regarding your question,
    You need to create a Logical System with the help of the transaction SALE.
    Assign the created LS to the client with the help of same transaction
    Go to WE20 and create the partner with the same Logical System name
    Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
    Before doing the above step, you got to create the connection between SAP and Non-SAP System.
    Use transaction SM59 to do this. Type of connection would be R/3 I guess
    Thanks
    Hope it helps.

  • Idoc setup::Partner profile for Logical system

    HI All,
    I am using Idocs to transmit my invoice details from ECC to PI, but every time I do this for a new customer I have to setup a partner profile for the customer whose invoice is to be sent. I setup the partner profile using WE20, I setup the partner profile for partner type KU(Customer) in the we20,
    Is there any way we can setup partner profile for LS(Logical system) in we20 & I don't have to setup partner profile for each & every customer for which Idoc is to be generated.
    Please provide some useful information/help to handle this business scenario.
    Regards, 
    Saurav Singh

    Hi Saurabh,
    Please refer SAP Note 1103146 and check.
    Please also refer the below link:-
    http://www.sapgeek.net/2011/07/sap-idoc-tutorial-maintain-partner-profile/
    Thanks & regards,
    Rahul Verulkar

  • LSMW: ALE/IDOC, getting the Create a partner profile for message type

    Hi Gurus,
    In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
    when i'm generating the idoc in the 13th step, its posing the information message stating that:
    Create a partner profile for message type 'ZEMP_MSG'
    In partner profile i already assigned the message type .
    How to solve this issue, <inappropriate urgency removed by moderator>
    Thnks&regards,
    sree
    Edited by: Thomas Zloch on May 13, 2011 9:55 AM

    This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

  • 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

  • Just one partner profile for SAP XI?!

    Hi,
    well i have some thoughts concerning configuring the partner profile on sender side.
    I have different systems to which e.g. IDocs will be send to. Therefore i was thinking to set one partner profile for each connected system.
    But on the other hand it is also possible to just configure one partner profile, e.g. called SAP XI, and seperate the different IDocs inside this partner profile because of different Message-Types of the Outb-parameters, and inside this because of the IDoc-Type.
    So what is the most propriate way to solve this, is there a suggestion by SAP?!
    thx in advance, Jens

    Hey guys,
    Just thought I'd add my experiences here.
    In one of our implementations we created partner profiles with respect to XI. We had multiple source systems , but the Target ECC team was like, we do not care who sends the data to XI, as far as we are concerned we get data from XI. So we create only one partner profile. We agreed to this and so all Idoc's posting from XI had the XI as the sender partner name. The project went into production and things were fine.
    Then comes the next release. And what do we realise, that the same Idoc will not be posted from XI but for different source systems with different formats. The Inbound processing for the idoc was also being changed stating that Idoc from Source system A  needs to be processed with this T code and Idoc's from System B with this code. reason was different bsuiness rules across different geographies.
    Now, at this juncture we realised in vain that it would have been better had we maintained the partner profiles with respect to the End Systems . having it with respect to XI caused issues in the fact that we are unableto trace out which Idoc belonged to which system.
    Since, then we always recommend all partner profiles with respect to End Systems and not with respect to XI. Helps the business also understand how many idoc's were posted for which source system and so on.
    Just my 2 cents and experience here. Would love to heard more on this topic as well.
    Regards
    Bhavesh

  • Error MSG : Create a partner profile for message type 'MATMAS'

    Getting Error MSG : Create a partner profile for message type 'MATMAS'
    While running LSMW Idoc generation process

    See the below link and it has all screen shots how to configure ALE like partner profile,logical systems,RFC
    http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html

  • EDI: partner profile for shipping point or plant

    I want to issue idocs for delivery notes based on shipping point or plant, not shipto party as is usual.
    How can I go about this?
    It looks like I need to create a new partner type. Or can I use logical systems?
    If logical system is used, then how do I make the connection document->LS?
    The external system uses the RCVPRN to determine which warehouse to handle the delivery for.
    I am changing the RCVPRN in a user exit now, but this still requires creating/ changing all partner profiles for shipto parties.
    Any ideas? previous experiences?
    Thanks,
    phillip

    Hi Phillip,
    it looks like I need to create a new partner type. Or can I use logical systems?
    > Yes, you can use LS
    If logical system is used, then how do I make the connection document->LS?
    > You can use FM: MASTER_IDOC_DISTRIBUTE to send the outbound IDOC...
    Regards,
    Hendy

  • How can we transport the partner profiles and Port configurations

    Hi everybody,
    How can we transport the partner profiles and Port configurations. While creating these , system will not ask for Dev class and we cant assign any Transport request number. Then How can we transport these settings?
    Your replies are really apreciable.
    Thanks and Regards,
    Vijay.

    Hi,
    please have a look of the OSS note: 182172
    >>
    The partner profiles are stored in the following tables:
    Table EDPP1: General partner profile
    Table EDP12: Partner profile outbound, additional data NAST
    Table EDP13: Partner profile outbound
    Table EDP21: Partner profile inbound
    Table EDIPHONE: Connection to SAP telephony (optional)
    You can use R3TR TABU to manually set the tables into a Customizing request (as of Release 46, into a SYST-type request).
    <<
    Rgd
    Frédéric

  • Create a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'

    Hi
    I am trying to create IDOC generateion through LSMW.
    i AM GETTING THE MESSAGEcreate a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'
    How do I create this profile??????

    Hi,
    Execute transaction BD64.
    Identify you distribution Model,
    Select the leaf node, and from menu select
    Environment->Generate Partner Profile
    Here in you specify 'Output mode' and 'Processing Mode'.
    Click on Execute.
    Check if any error occurs (Marked with Red color).
    Try creating the IDOCs
    Best Regards,
    Pratik Patel
    Reward with points if it is of any help to you!

  • Partner profile for message type.

    Dear All,
    I am using bapi in lsmw for data conversion.
    I am getting error in 13th step of lsmw, ie, when I execute Start Idoc Generation, it's saying,
    Create a partner profile for message type - MATERIALVALUATION_PRICECHANGE.
    I already created a partner profile and assigned in the initial screen of lsmw.
    Kindly let me know where I am missing.
    Thanks in Advance,
    Ranjan

    See if any of the follwing helps:
    1. The port used in the partner profile should be a file port, not tRFC.
    2. The checkbox 'Unicode Format' for the port LSMW in WE21 should remain unchecked.

  • Could any body tell me the significance of Partner Profiles in IDOC PROCESS

    Hi,
    Could any body tell me the significance of Partner Profiles in IDOC process.
    Thanks in Advance,
    BSV.

    Hi,
    The partner profile is used to validate the sender and receiver system for a given message type and to assign to the correspondence process code (function module) to post the IDoc to application system.
    This applies for both Inbound and Outbound IDOC's.
    Also please check this link for more information.
    http://help.sap.com/saphelp_46c/helpdata/en/dc/6b803343d711d1893e0000e8323c4f/frameset.htm
    Regards,
    Ferry Lianto

  • Creation of a partner profile for an non sap system

    hi,
    I need to create a partner profile for an non sap system(SQL Server).
    step by step procedure will be useful.

    Hi,
    1>goto SM59 create R/2 connections and give the connection type as 2 and give the receiver address.
    2>create port in we21 tcode.
    3>create partner  profiles in we20 and give the receiver system (LS).
    Regards,
    nagaraj

  • Partner profiles for EDI

    What is the "Partner Profiles for Logical Systems" when maintaining partner profiles for EDI.
    Which kind of partner profile we use when sending payments like wire and ach through bank. Don't we use partner type B for bank or do we use partner tupe LS (logical systesm)?????

    Hi
    LS - Logical system is used for ALE interface , That is interaction with SAP clicnets whether in the Same Server or External servers.
    Main usage is in Intercompany billing where the Different copmnay codes are maintained in different clients
    Each clicent in SAP has a Logical system Defined to it.
    Thanks & Regards
    Kishore

  • Partner Profile for file to IDOC scenario

    Hi experts,
    I am doing file to Idoc scenario. I did the ALE configuration steps between XI and r/3. For sender (ThirdParty) system, I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
    Thanks
    Manoj

    Hi,
    >>I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
    in most cases you will only use one logical system in WE20
    this will be XI's logical system - and you can route all the traffic
    via this logicail system - this is the most popular case
    for more about IDOCs and XI have a look at my book:
    Mastering IDoc Business Scenarios with the SAP XI
    http://www.sap-press.com/product.cfm?account=&product=H1935
    Regards,
    Michal Krawczyk
    http://mypigenie.com - XI/PI FAQ

Maybe you are looking for