Partner Profile Configuration(Outbound Enteries)

I was trying to make a business partner with the BP Role “Master Tenant with Customer Account”. At the time of saving I got following error:
Entry in Outbound Table not found
Message No E0400
No partner profile(Outbound) could be foundusing following key
This refers to key fields in Table EDP13
RCVPRN  Partner Number
RCVPRT  Partner Type
RCVPFC  Partner Function
MESTYP  Logical Message
MESTYP  Message Code
MESCOD  Message function
TEST        Test indicator
Please check EDI profiles.
And it directed me to transaction code WE20.
Could you please help me in making the desired settings and explain why this needs to be done.

I guess either you are using CRM or Flexible Real Estate Management.
Pl confirm the exact transaction code you are using. Are you using BAPI ?
For creating the Partner profile,
Go to WE20,
Click on Create button.
Give the Partner Number, Give Partner Type as " LS"
User type- US
Agent - Your User ID
Give the Message types in the Outbound/ inbound parameters.
Pl reply for further clarifications

Similar Messages

  • Logical system and partner profile configuration

    I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
    First question is do I have to mention a logical system name for the SQL server Business system too ?
    Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    Thanks in advance.

    Hi Sam,
    > First question is do I have to mention a logical system name for the SQL server Business system too ?
    Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers  you can see logical system name of SQL server business sytem which you defined in SLD.
    > Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
    > Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    In WE20 You have to maintain partner profiles for SQL server Logical system
    For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
    In ECC you have to create logical system as SQLDEVLS and
    Partner profiles for SQLDEVLS in WE20.
    Please let me know if you have any issues.

  • Steps to Configure Port and Partner Profile for Outbound process

    I want to Configure the partner profile and Port definition for outbound Message type REMADV ( for Vendor). 
    Could anyone please tell me the steps to configure.
    Thank you,

    Hi Renu,
    In partner profile we define the system which are going to communicate between themself and send data, here we give some logical name for the system which are going to be partners in data communication.we set it using WE20
    Port is a medium through which we send the data it connect one system with the system in other end its unique, depend on the scenario we use diff ports like file port(EDI) transactoional port(ALE) internet port(for internet apl), like this i dont remember all the name, so according to our application type we select the ports we set port using WE21 usally tport name start with A*** something like this. withour defining a port we cant communicate with other system its the linker b/w the 2 system.
    <b><u>For more information please refer the following links:</u></b>

  • Partner Profile configuration for EDI 810

    I am configuring partner profile for EDI 810 (Invoice). In the message control tab, what values should be entered for
    1. Application
    2. Message Type and
    3. Process Code
    Thank you.

    - Check Transaction NACE to see what applicatios you can use for different objects.
    - Check transaction WE42 for all outbound process codes
    - Check transaction WE41 for all inbound process codes.
    - Check transaction WE64 for inboud / outbound message types and related process codes.
    <b>EDI 850:</b>
    Application - EF
    Process code - ME10
    Message type - NEU ( or your custom message type setup for EDI  )
    IDOC - ORDERS01 to ORDER05
    <b>EDI 810:</b>
    Application - V3
    Process code - SD09
    Message type - RD00 (  or your custom message type setup for EDI  )
    <b>EDI 820:</b>
    i think this is for inbound idoc of  <b>Payment Order/Remittance Advice</b>. When yuo setup inbound partner profile, you do not need to know application
    Process code - LOBX
    Message type - LOCKBX
    IDOC - PEXR2002
    Let me know if you need any other information.

  • IDocs, INVOIC partner profile configuration

    I need to receive the INVOIC IDocs from sender system.
    Sender(S) system is new system
    receiver(R) system is already exisitng system.
    I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
    Now if i configure only partner profiles and distribution model, then is it work.

       INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
    First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
    If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
    If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

  • Creating Partner Profile

    Hi Experts,
    While creating a new partner profile for ALE implementation when i am entering a partner no. as a logical system(i.e 'LS') and other details my system is giving msg invalid partner i have checked it by giving the partner no. as user(i.e 'US')....then it acepted ...
    But my requirement is to create a partner progile under Logical Syatems(i.e 'LS')....
    Plz suggest anybody....

    HI Shrikanth,
    pls refer to this link.
    hope this may useful to you...
    Re: Logical system and partner profile configuration
    how to create partner in idoc

  • Getting EDI:Partner profile not available.

    I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
    <u><b>My Scenario details</b>:</u>
    1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
    2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
    3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
    4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
    5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
    6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
    7. Activated all Standard Change list items.
    The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
    I  have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
    can somebody suggest me solution please.

    <i>6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.</i>
    >>>Check this for Reciever Business System.. not for Sender system..
    BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check  all the data from XI is populated in the idoc structure in SAP R/3 in clicking each segment.. if so, then there is no problem from XI..
    check WE20 ..partner profile configuration in R/3 also check inbound parameters are given

  • Error in Partner Profile

    I have done the partner profile configuration.But still i m getting  the error like this."Partner profile inbound  not available" .
    How to resolve this problem?
    How to configure the Partner profile to resolve the problem?

    Hi Soumya,
    Check this link to configure inbound partner profile....
    Reward points if this helps

  • EDI: Partner profile Error

    Dear All,
             I was trying to load a Hierarchy from R/3 to BI 7.0 . I get an error "EDI: Partner profile not available". When I go to R/3 TC we05 I get under Inbound Docs> RSRQST > status 64 for Idocs specifying this error. I donot find RSRQT partner profile under outbound Docs.
    When I go to BI TC we05 I get Inbound Docs empty and Outbound docs > RSRQT I donot find the above Idoc numbers having status 64.
    What does this mean?How can I successfully load this hierarchy?
    Jack Silverz

    Hi Jack,
    Make sure that logical system name hasn't been changed .
    Check SAP note 325470.
    Hope this helps u...

  • Query on Partner Profile Config

    Hi All,
      I've a basic question in Partner Profile Configuration.
    <b>Case 1.</b> When a file is sent to SAP as an IDoc  (File to Idoc via XI),  which Business System's Logical System Name should be mentioned in the partner profile (WE20)?.
    Is it the Sender's Logical System Name (File System) or the Receiver's Logical System Name (SAP System)?.
    <b>Case 2:</b> When SAP is sending an IDoc to a file system (IDoc to File via XI), which Business System's Logical System Name should be mentioned in the partner profile (WE20) ?.
    Is it the Sender's Logical System Name (SAP System) or the Receiver's Logical System Name (File System)?.
    Please gimme the direct answer not the docs. Bcoz some of the docs says it is sender's and others says it is receiver's. I just wanted to get it clarified.
    Thanks in advance.

    Hi Joe..
    U shud use XI's logical name on partner profile of R/ ur actual sender is nt XI in Message Mapping of XI u can overwrite the name of sender as XI logical name.
    Partner profile is definetly XI as SAP system is sending data to XI & its doesnt know wat happens to data at XI..

  • The change flag in partner profiles and how its used?

    can any one succinctly explain the use and purpose of the change flag in the message control part of the partner profile configuration?

    The value of this field is use internally in FM attached to the process code  for Creation/Change and in case of change, only the relevent changed data is sent ( taken care by attched FM).
    Thanks & Regards,

  • 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,
    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.

  • Partner Profile for IDOC - configuration

    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?

         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>

  • Configuring ALE Logical Systems and Partner Profiles

    Trying to build a scenario which deals with two third party systems transfering XML file from one to another. Sender is using a file adapter. Reciever is using an Idoc adapter. However the pre-requisite mentioned for this exercise are that ALE logical systems and partner profiles must be configured (these steps are not outlined in the exercise) . Could i get help on what steps i need to carry out for sender/reciever to configure logical systems and partner profiles.

    Hi Manpreet
    At the R/3 system the partner profile should be maintained for both the third parties.
    for creating the partner profile go to transaction we20, give the
    partner number :your logical system name or customer number or vendor no
    partner type:LS(logical system)or ku(customer)OR LI(vendor)
    give the message type in the outbound parameters
    after this double click on the message type and give the login deatils for the RFC destination define the port and all
    if you still have problem please reply back

  • 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,

    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).

Maybe you are looking for

  • How to remove prefix namespace in Xml from XmlBean

    I am trying to generate XML from XML Bean but i am getting namespace prefix in all my xml elements. For example <abc:Cutomer xmlns:abc="> <abc:Name> I don't have this namespace prefix in my XSD (imported in Weblogic workshop). I

  • Computer will not install 10.5

    my computer will not install iTunes 10.5.  I have 10.4 currently and it syas that a required file is missing during the 10.5 install and shuts down.  I purchased an iTouch for my daughter and it won't sync with 10.4!  Ugh!!

  • Account detemination possible at sales order level

    Is revenue account detemination possible at sales order level ? When I created the sales order and checked account detrmination analysis, most of the screen is blank. Is it expected to happen at sales order level ?

  • How to get back all the old sync data in new sync version?

    How to get all the back up data from old sync version to the newer sync version?

  • Why does it cut information when converting to Excel?

    Why does it cut the info @ the bottom of the page when converting to Excel - last 6 lines after the negative amount (CLAIM-RFC) is included in the headings of the following page and not included into Excel.. 3723 30273723 769886 INVOICE 10/06/14 6,83