<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Wrong logical system for partner profile in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146117#M1620897</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDI: Partner profile outbound process code not available&lt;/P&gt;&lt;P&gt;Message no. E0335&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Diagnosis&lt;/P&gt;&lt;P&gt;An outbound partner profile could not be found with the following key:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/MSC_MM_PRD/LS//EF/ZEDI//&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[u2026]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;Please check the outbound partner profiles for the assignment of the process code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone please tell me why SAP uses the old logical system and how I can change that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Alicia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Aug 2011 13:25:38 GMT</pubDate>
    <dc:creator>former_member504446</dc:creator>
    <dc:date>2011-08-12T13:25:38Z</dc:date>
    <item>
      <title>Wrong logical system for partner profile</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146117#M1620897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDI: Partner profile outbound process code not available&lt;/P&gt;&lt;P&gt;Message no. E0335&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Diagnosis&lt;/P&gt;&lt;P&gt;An outbound partner profile could not be found with the following key:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/MSC_MM_PRD/LS//EF/ZEDI//&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[u2026]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;Please check the outbound partner profiles for the assignment of the process code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone please tell me why SAP uses the old logical system and how I can change that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Alicia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 13:25:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146117#M1620897</guid>
      <dc:creator>former_member504446</dc:creator>
      <dc:date>2011-08-12T13:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong logical system for partner profile</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146118#M1620898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The partners should be loaded in the orders by the condition records; have you changed them?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Aug 2011 13:37:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146118#M1620898</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-12T13:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong logical system for partner profile</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146119#M1620899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Alicia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2011 15:08:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146119#M1620899</guid>
      <dc:creator>former_member504446</dc:creator>
      <dc:date>2011-08-15T15:08:20Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong logical system for partner profile</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146120#M1620900</link>
      <description>&lt;P&gt;Hello Alicia.. I know this is very old post but i am facing exact same issue. Can you please tell what did you do in BD64 to make it work. &lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2020 05:38:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/wrong-logical-system-for-partner-profile/m-p/8146120#M1620900</guid>
      <dc:creator>gauravthkkr1311</dc:creator>
      <dc:date>2020-07-30T05:38:05Z</dc:date>
    </item>
  </channel>
</rss>

