Logical system and partner profile configuration

Hi,
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.
Cheers,
S

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.
Cheers,
JAG

Similar Messages

  • Configuring ALE Logical Systems and Partner Profiles

    hi,
    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.
    regards,
    Manpreet

    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
    Thanks
    Rinku

  • Multiple Logical Systems in Partner Profile for one instance

    Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System?  If it is possible, can we create Logical System with respect to Plant/Country?

    I am not quite sure if I understood your problem completley. But let's see...
    Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
    You can find more information about it in this guide here on SDN:
    Link: [High Availability;
    More information about High Availability Setups for SAP System can be found here on SDN:
    Link: [High Availability]
    If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
    Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
    Hope this helps.
    Best regards,
    Mathias

  • Wrong logical system for partner profile

    Dear gurus,
    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.
    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).
    After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
    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.).
    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:
    EDI: Partner profile outbound process code not available
    Message no. E0335
    Diagnosis
    An outbound partner profile could not be found with the following key:
    /MSC_MM_PRD/LS//EF/ZEDI//
    [u2026]
    Procedure
    Please check the outbound partner profiles for the assignment of the process code:
    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.
    Can anyone please tell me why SAP uses the old logical system and how I can change that?
    Cheers
    Alicia

    Hi,
    problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
    Cheers
    Alicia

  • "no active plan version exists" while adding system in partner profile

    Hi,
    i am getting "no active plan version exists" while adding logical system in partner profile. while duble click on this it showing "set active plan version".
    Can anyone answer me how to do the set active plan version. I asked my functional team and  they didnt know how to set it.
    Thanks,
    Gowthaman.

    Thanks Sonia,
    in OOAP i could not able to edit so i maintained plan version in OOPV and in sm30 in table T77S0 maintained PLOGI group.
    Now i am getting different error while creating partner profile in we20..
    *Object type US, ID CENTRALADMIN unknown (please observe upper/lower case)*
        *Message no. E0624*
    *Diagnosis*
        *Object CENTRALADMIN of type US is not known in the system.*
    *Procedure*
        *Enter a valid object and check the type.*
        *Make sure upper case and lower case are used correctly.*

  • IDoc Adapter - Logical System - File to IDOC configuration

    I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload'  & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
    Thanks

    Hi,
    Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
    Do let me know why u r going for three different LS.
    In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
    Thnx
    Chirag

  • Regarding ports and partner profiles in ALE.

    Hi All,
    Please tell me how to transport the partner profiles and ports from Development to Quality systems.
    Please reply asap.

    SALE Area Menu for ALE configurations.It includes transactions for
    Logical System definition and linking it to a client, Transactions for
    RFC Destination and Port Definition Etc.
    SM59 RFC Destination
    Here we specify the login settings for the destination including
    the I.P address or Application Server name and the User name and
    password.The information entered here is used to run Remote Function
    Calls(RFC ) on the destination server .We can create number of types
    of RFC Destinations but 3 types are important .
    R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
    The name of the RFC destination should be same as that of Logical
    System as it helps in creation of automatic partner profiles.
    WE21 Port Definition.
    There are 6 types of ports but only 2 types File and Transactional RFC
    types of ports are important.
    We have to specify the RFC Destination before a port can be created.
    WE20 Partner Profile
    Here we create partner profile for each and every partner from / to which
    the messages will be exchanged.There are 6 types of PF generally only
    profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
    We specify the partner number and partner type and the agent and
    the agent type responsible for handling of errors .
    For every message send to the partner we have a outbound record and for
    evry message coming from the partner we have the inbound record .
    We specify the message in the otbound/inbound records ,double
    clicking will take us to the detailed screen where the IDOC Type ,Port
    and whether the IDCO will be immediatelt processed or collected are
    mentioned.
    Reward points if helpful.
    Thanks
    Naveen khan
    Message was edited by:
            Pattan Naveen

  • Logical system and rfc destination

    hello all,
    what is the difference between logical system and RFC destination?
    thanks for ur help in advance.
    regards,
    vikas

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Regards

  • Partner no and partner profile

    Hi,
    Where i have to config partner no in SAP.
    While i am config. partner profile in WE20 system is asking Partner no.
    Please guide me
    Sateesh Kumar

    Hi,
    Thanks for every one.
    My scenario is: Client is asking sending the payment advices through IDoc.
    For that i configured
    1) partner and partner profile.
    2) Activated House Bank for EDI and Data medium exchange
    3) Created partenr profiles for 1 vendor and 1 customer
    4) Assigned partner profiles for House Bank also.
    Still i have to do any configuration settings?
    Please guide me with complete info.
    Sateesh

  • Logical system and business system

    Hi experts, please help me with the below questions---
    1) What is the diff between logical system and business system?
    2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
    3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

    Hi,
    Business System :
    1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
    2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
    Business Service:
    1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
    2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
    3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
    4.Business Service has no SLD Entries and No Assigned Products and SWCV's
    Regards
    Sangeetha

  • AC 5.3  Logical systems and multiple Physical systems

    HI all:
    We have set up a Logical System, and then have hooked up 2 Physical systems to it.  Based on the documentation from SAP, the rule set (and the way we set it up) is at the Logical system level. 
    Physical system #1 is reporting the correct results, however, Physical system #2 results are not complete.  My understanding is that both Physical systems should be drawing from the rule set based in the Logical system.
    Results:  Physical system #1 - correctly identifies 10 risks
                  Physical system #2 - incorrectly only identifies 5 of the expected 10 risks.
    Role assignment to user is exactly same, authorizations are exactly the same.  The User/Role/Profile Full Sync has been repeated as part of troubleshooting.
    Has anyone experienced this?  I'm looking for ideas/options on where to investigate why the results are different.
    Thanks
    Margaret

    HI:
    Thanks for answering!!  I'm having trouble understanding the answers, sorry.
    When you have a logical system...you upload the rules once to that system, and generate them.  Then when you set up a physical system and hook it up to the logical system...the 1st, 2nd or 3rd physical system....they all use the same ruleset.  The whole concept (as I understand) is that the use of Logical and Physical systems...and putting the rule set on the Logical system so you don't have to worry about one rule set taking precedence over another, is an advantage, if this is possible (ie: we don't have multiple rule sets).
    Where should I be checking that the risks are defined properly?  The rule set is the delivered one from SAP.  The functions and risks match what we had (plus more) in the CC 4.0 system.
    The first physical system we set up (example: Development) works fine, and all regular SoD risks are coming up as expected.  When we added another system (example: Test)...the results of SoD analysis were incomplete. 
    Does that help clarify?  Perhaps I'm just missing something?
    Margaret
    Edited by: Margaret Sokolov on Apr 28, 2009 4:34 PM

  • Transaction Launcher Logical Systems and URLs

    Hi,
    I'm facing a problem with Transaction Launcher.
    I've done all the settings specified here: http://help.sap.com/saphelp_crm60/helpdata/en/46/231befc17b5872e10000000a11466f/frameset.htm
    Under section "Define Transaction Launcher Logical Systems and URLs" I've specified the values for Quality System: the ECC system is MQAS200A
    By the way, when I try to access an ERP Sales Order, the transaction CRM_TL_ERP_BUS2032_DISPLAY tries to access system MSVL200A (which is the Development ECC System).
    I cannot change the Logical System within the Transaction Launcher Configuration (currently it is set to ERP), since the Transaction is standard.
    Does anybody know how to map the generic value ERP with the correct value MQAS200A instead of MSVL200A?
    Thanks in advance,
    Regards,
    Andrea Ricci

    Hi,
    You cannot generalize the Logical system name, for the workaround you need to put the logical system for quality and transport it to quality and it should work and to check in dev you need to again change the log. sys to dev and save it but dont transport it. Similarly you can do for production system.
    Regards,
    Shobhit

  • Define Logical Systems and Template Names for BW Reports

    Hi experts
    I would like to know if someone used the mentioned functionality 'Define Logical Systems and Template Names for BW Reports, I would like to know too IF I create a Z REPORT for example in webdynpro and insert it in this configuration it will work and where it will appear in sourcing cockpit?
    sds.
    Javier

    Hello Muthu,
    BW reports will be shown in SRM Box if the corresponding BW roles for SRM are integrated with SRM roles.
    You might to activate the corresponding datasource of this in SRM.
    And since you have to connect the source system to BW, I think you have to define SRM system as logical system in BW.
    Regards,
    Pavan

  • Cdm and partner profiles

    can help me out in,,,,,What are CDM and Partner Profiles in ALE??

    Hi Praveen,
    Chk these links
    <b>ALE/ IDOC</b>
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    <b>ALE</b>
    <b>Outbound:</b>
    Step 1. Application document is created when transaction is saved.
    2. Message control is invoked.
    3. Messages are processed by system.
    4. Messages are Edited (if desired).
    5. Output (ALE / EDI) is checked
    6. Validate against Message control record from Partner Profile
    7. Application Document is saved.
    8. Entry NAST table is created for every selected output program
    along with Medium & Timing.
    9. Check for Process Immediately .
    If (yes)
    Determine Processing Program from TNAPR Table.
    ELSE
    Execute RSNASTED Program.
    10. Read Partner Profile to determine Process Code.
    11. Process Code points to the Function Module & Invoked.
    12. IDoc is generated.
    13. Check for ALE Request.
    if (Yes)
    Perform Filters, Conversions, Version Changes etc.
    Else.
    IDoc is stored in DATABASE.
    <b>INBOUND:</b>
    Step 1. EDI Subsystem creates an IDoc file from EDI Messages
    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
    3. Data in Control Record is validate against the Partner Profile.
    4. IDoc is generated in Database and syntax check is carried out.
    5. IDoc file is deleted once file read.
    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
    7. Check for Process Immediately.
    If NO
    Execute RBDAPP01 Program
    Else
    Read Process Code from Partner Profile
    Process Code Points to Function Module
    Application Document Posted.
    <b>
    ***Reward Points if Useful</b>
    Regards
    Gokul

  • Change log for Distribution model and partner profile

    Hello All,
    Could any one please suggest how to get teh change log of the distribution model and partner profiles in SAP.
    Thank you!
    Arvind

    Hello,
    The documentation says what distribution model is used for. My question is can we have change log for any change in the distribution model like user, time and date.
    In production system if distribution model and partner profiles are changed by someone to a destination which should not be used, then how can we trace who has changed it.
    I hope I am able to explain.
    Arvind

Maybe you are looking for