ALE settings in sapR3 system logical system

Hi People
IN IDoc to File scenario
How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that,  we have to 1st create LS name (for R3 sys & PI sys),   after that we have to assign that name's how to assign that,    PLS can u provide me to with screen shots (if possible) r any links 
Regards
shekar

Hi,
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

Similar Messages

  • What is a R/3 system, logical system, and legacy system...???

    Hi,
    Please throw some light on...What is a R/3 system, logical system, and legacy system...???

    Hi,
    R/3 system is a normal SAP system that stores data.
    A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
    Logical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
    Technical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
    Regards,
    Subhasha

  • ALE - Error - Assign client to logical system

    Hi All,
    When i am working in ALE [SAP IDES]. In SALE transaction when i try to do ' Assign client to logical system' -
    in the second screen 'Change View: clients details' after i give all the details, it's showing error
    'An entry already exists in the same key' & the cursor is in the client field [i entered 800 as i m working in client 800],
    Kindly help.

    Hi,
    You did create a client in SCC4.
    firstly,
    1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
    2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
    If you didn't perform above two things, then please do.
    Hope it works!!
    Regards,
    Amruta

  • Entitlement Systems Logical System Name

    Environment:
    - BusinessObjects Edge Series BI 3.1 (standard packge)
    - Business Objects XI Integration for SAP Solutions
    - Windows Server 2003 x64
    I am trying to configure a Logical System Name in the Entitlement Systems of the BusinessObjects Central Management Console.
    Our BI 7.01 system uses a different naming convention for the logical system name (not the standard <SID>CLNT<client#>
    (i.e. BWQCLNT300).  We use BWQ300.  How would I override the default configuration (put in a different logical system name)  in CMC - SAP Authentication?
    Please advise.  Thank you in advance.
    Francis

    Ingo,
    That is correct.  It generated the logical system name automatically for me. 
    But our BW system have a logical system name of BWQ300 (not BWQCLNT300). 
    How would I override this ?
    Thank you very much for your reply.
    Francis

  • Source System(Logical system) issue

    Hi All,
    Recently we have done QA refresh & copied with production data.
    For 0vendor master data we are extracting data from ECC source system. When I was trying to execute the DTP it is pointing older source system. We tried to create new DTP but when I'm executing still it is showing older system.
    By using RSBKDTP_BDLS  program I forcefully tried to convert old source system to new source system but we are unable to solve this issue.
    Here I'm attaching the issue .Please help on this issue.
    Best Regards,
    Sammar.K

    Hi Ram,
    I have compared Production & QA system entry's in RSLOGSYSMAP Table.
    in prd system
    source       target
    qa6            prb01
    in qa system
    source       target
    qa6             qa6
    we found in qa it is pointing wrong target.
    Regards,
    Sammar.K

  • Unable to convert the sender service to an ALE logical system... Urgent..!!

    Hi,
    Im DOing File to Idoc scenario.
    Firstly i check LS name exist or not in BS.. then i found its not maintained.
    I edited the BS and provided the required LS name.
    and the same has been tested in ID
    Business System -> Service -> Adapter Specific Identifiers .
    Now i got logical system name in "Adapter Specific Identifiers".
    Pressed Apply, save and activate the changes.
    But still it is showing the same error.
    1. Any idea what might have gone wrong??
    2. I need to maintain the
       LS name of R/3 in  XI system? and
       LS name of XI in R/3 system?
        Is it necessary?
    Waiting for your answers.
    Regards
    Seema.
    Edited by: reddy seema on Dec 27, 2007 1:37 AM

    Hi Reddy,
            just mention the logical system name in the  Sender Business system or Service ( click on sender business service> Service(menu)>  Adapter Specific Identifiers--> specify the logical system name  which you configured in R/3  WE20 ..)  in R/3  side  WE20  you need to configure  the Inbound parameters  of your Idoc  .. 
    Here  sender business system and Reciver Business system logical system names are different.. for checking just go to  Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
    try with this option..
    Regards
    @jay

  • Difference between client system and logical system

    Hi all
    Can any one explain about the client system and logical system??
    When this message type will comes in to picture at the time idoc processing??
    Thanks and Regards
    Arun Joseph

    hi Arun,
    I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
    and to know the diffrence between client and logical system very keenly go thru this link
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
    IDOC Administration
    Step 1: Tcode: WE 46
    Setting the Global Parameter for IDOC Interface
    Step 2: Maintaing a Logical System
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Define Logical systems
    Go to Spro transaction
    Step 3: Allocating Logical systems to the Client
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Assign Client to Logical systems
    Go to Spro transaction
    Step 4: Setting up an RFC destination
    Tcode: SM 59
    Path: From the ALE Customizing in IMG, choose Communication, Define RFC
    Destination
    You can also do the Advanced Settings in the RFC Destination
    Step 5: The PORT definition
    TCode: WE 21
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Systems in Network, Asynchronous Processing, Assign Ports, Define Port
    Step 6: Generating Partner Profiles
    TCode: BD 82
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
    Step 7: Distributing the Model
    TCode: BD 64
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, Maintain Distribution Model and Distribute Views
    Technques for Distributing the Master Data:
    Technique 1: The Push Approach
    Executing the Process:
    TCode: BD 10
    Path: from the ALE Main Menu, choose Material Data Distribution, Cross
    Application, Material, Send
    Technique 2: The Change Pointer Technique
    Enable Change Pointers Globally
    TCode: BD 61
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers
    Enable Change Pointers Globally
    TCode: BD 50
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers for Message Type
    Specify the Fields for which Change Pointers are to be written
    TCode: BD 52
    Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
    Change-Relevant Fields
    How the Classification system works:
    Creating a Class Type
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Status for the Class Types:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classification Status:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classes:
    TCode: CL 01 (it is zero)
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
    Allocating classes to the Logical Syatems
    TCode: BD 68
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Assign classes
    to Logical systems
    Filering at the IDOC level:
    Identify the Filter Object:
    TCode: BD 59
    Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
    Type to IDOC Field
    Modify the Distribution model
    How Segment Filtering Works:
    Configuration:
    Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
    TCode: BD 56
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
    The Reduced IDOC Type:
    The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
    The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
    represented by a forward slash(/) in the field.
    TCode: BD 53
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
    Create Reduced Message Type
    IDOC:
    Complete Documentaion on any IDOC using TCode: WE 60
    IDOC Display Tool: TCode: WE 02 or WE 05
    IDOC DEfinition components:
    Segment Components:
    1. Segment Type (E1, Z1)
    2. Segment Definition(E2, Z2)
    3. Segment Documentation(E3, Z3)
    E- SAP Defined
    z- Custom Defined
    IDOC runtime componets:
    control Record:
    Data Record:
    Staus Record:
    First Create the Segments using TCode: WE 31
    and then create the IDOC using TCode: We3 30
    first release the segments and then IDOC.
    Creating a new Basic IDOC Type:
    STEP 1: Analyze the Data:
    STEP 2: Create Data Elements:
    STEP 3: Create Segments:
    STEP 4: Create Basic IDOC Type:
    1. Execute TCode: WE 30
    2. Select the Create new option and enter a description for your basic IDOC type
    3. click the IDOC name, and click the create icon.
    Enter the segment type and its attributes.
    4. Keep on adding the segments as in step 3.
    5. Save the basic IDOC type
    Step 5: Release the Segment Type and Basic IDOC Type
    STEP 6: Transport the Segments and Basic IDOC Type
    Extending a Basic IDOC type:
    STEP 1: Analyze the Data:
    STEP 2: Create Custom Segments:
    STEP 3: Create the IDOC Type:
    STEP 4: Release the custom Segment and IDOC Extension
    Develop the function module for fteching the Data and then inserting the data into IDOC using
    EDIDD(for control Record) and EDIDC table(for DATA Record)
    Configuring the Systen for IDOCs
    Configure an Outboubd Process that uses Message Control
    Step 1: Create a new Message Type
    TCode: We 81
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 2: link the IDOC type to the Message Type
    TCode: We 82
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 3: Create a new Process Code
    TCode: We 41
    Path: From the Area menu of EDI, choose Control,Outbound Process COde
    Step 4: Create or Change a Partner Profile
    TCode: We 41
    Path: From the Area menu of EDI, choose IDOC,Partner Profile
    Configure an Outboubd Process for Stand-Alone Programs
    1. Create a new message type
    2. Link the IDOC type to the Message Type
    3. Add the message to the ALE Distribution Model(use BD 64)
    4. Create or change the Partner Profile
    go through the following site to have screen shots.
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    thanks
    karthik
    reward me points if usefull

  • Logical System Name changing

    Dear Team,
    We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
    copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
    R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
    extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
    Here we are facing a problem with Logical system. While upgrading the
    same logical sys was copied to BW dev copy.
    What is the procedure to change the existing logical system name in BW
    dev copy and establish connectivity with R/3 dev?
    what is the impact if we run BDLS transaction.
    Thanks& Regards,
    Satish.K.Neni

    Hi Satish,
    Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
    That should solve your problem
    Regards
    Juan
    Please reward with points if helpful

  • Cost center integration with HR - logical system for CRT inconsistent

    Hi there,
    we are distributing Cost centers from our SAP ERP system to another SAP HR system via ALE [COSMAS01 basic type].
    The cost center created in target system contains information about source system logical system name - table CSKS, field LOGSYSTEM.
    This is causing problems in Travel Managment in SAP HR system, where we get the error: Logical system for CTR inconsistent.
    Cost centers created/changed in HR system does not contain any value in CSKS-LOGSYSTEM field and work fine.
    Any ideas how to solve this issue?
    For now to fix the issue, user needs to do a phony change in SAP HR system to get rid of original LOGSYSTEM value.
    I am thinking about removing field E1CSKSM-LOGSYSTEM from COSMAS IDoc but I gues there must be simpler soloution.
    Thanks for your advices,
    Igor

    Igor :
    I think this has something to do with matching logical system with controlling area in TKA01. Another option for cc's logical system to have no values when outbound ALE is to config V_TKA01_ALE (so it will be transported to the system that has cc ALE to other systems) to have field 'ALE Distribution Method' blank (No distribution to other system).
    This way, when SAP is creating outbound idoc for COSMAS, field CSKS-logicalsystem will not be populated (logic is in SAP 'MASTERIDOC_CREATE_COSMAS' , around line 86).
    Rgds.

  • How to change or rename the logical system name T90CLNT090 IN BI 7

    HI Expert's,
    i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
    in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
    In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
    because of this i am not able to create the source system between r/3 also.
    so how to change this source system name for T90CLNT090.
    regards
    harikrishna N

    Hi,
    Pls follow this OSS note : 325525.
    Note 325525 - Copying and renaming systems in a BW environment
    Summary
    Symptom WARNING: THIS NOTE HAS BEEN REPLACED.  FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
    You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
    Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
    Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
    Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
    Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
               Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
               Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
               Reactivate all partner agreements that carry the new logical system name after renaming.
    Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
               Solution scenario 2):
    If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                        Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                        Reactivate all partner agreements that carry the new logical system name after renaming.
    Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
    Scenario 3) You want to copy a single BW system of the group by database copy.
    Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                         Solution scenario 3)b): See Note 184754.
    Scenario 4) You want to copy a single source system of the group by database copy.
    Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
               Solution scenario 4)b): See Note 184322.
    Scenario 5) You want to import a client copy in a source system.
               Solution scenario 5): See Note 325470.
    Thanks & Regards,
    Suchitra.V

  • Logical system value in a BAPI

    i am using a BAPI, its asking for logical system . How do i know that value ?

    Logical system- 'logical system' is used to identify an individual client in a system, for ALE
    communication between SAP systems. That's why you see a field for 'logical
    system' in the client master data in SCC4 (table T000). You use logical systems
    in ALE config - this should be documented further in the IMG guide, or SALE and
    BALE transactions.
    Check the link
    http://www.sap-img.com/bc059.htm
    please use Function Modules for this task:
    CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'...
    You can also check the table -
    The field is T000-LOGSYS. (Logical System)
    Regards,
    Amit
    Reward all helpful replies.

  • Assign Logical System both in GTS and R3

    Hello all,
    We are using Two different system for R3 and GTS , and defined logical system both systems ( for R3 QR1CLNT100 and for GTS QG1CLNT100 , now do I need to assign logical system both system for clients in R3 and GTS ( I mean at the time of assignment both clients QR1CLNT100 & QG1CLNT100 i have to assign in both systems  or only one.   For Feeder system only I need to assign GTS system logical system as QG1CLNT100 vice versa ( for GTS system need to only Feeder system logical client QR1CLNT100)
    Thanks in advance for valuable inputs.
    Thanks & Regards
    Tarun

    There are following steps  for doing connection between R/3 and GTS
    1. Define Logical System
      Here you have to define both R/3 logical system as well as  
      GTS logical system.
    2. Assign Logical System.
    Here actually when u get in you will see the physical system
    detail on which you are logged in , suppose you are on R/3 you will find detail of R/3 system with different clients. Some clinet willcome as default like 00 which is waldrof client the SAP client and other are are those which are created at the time of installation.
    Here you have to assign the logical system of R/3 to the physical system client combination on which you looged in.
    you will find a field  of logical system on the top once you get in detail of the client system combination.
    Now here we have assigned the Logical system of R/3 this is required as when GTS will communicate wiht R/3 it willtry to look for  R/3 logical system as for RFC connection we always define logical system to which the system will talk.
    this configuration we do under Maintain RFC connection for RFC call Tcode SM59
    3.  Maintain RFC connection for RFC call Tcode SM59.
       Here we define the Target host, and logon detail like 
       language , client, user passwaord.
       We need to define the detail for GTS for RFC connection and   so we need here the logical system of GTS.
    4. Maintain RF destination for method call
      Here again you will require GTS logical system .
    5. Maintain ALE distribution here you will require both R/3 and GTS logical system.
    Hope it helps
    Kind Regards,
    Sameer

  • Assign a Logical System Name of a production client

    Hi everybody,
    We have an ERP system (now upgraded to ECC 6.0) that is in productive use since 7 years. Until now, no Logical System Name have been assigned to the production client - the field in transaction SCC4 is empty/blank.
    Now we plan to implement a BW, so a test and a productive BW systems have been installed. According to the attached file and content of note 184447 we choose to use "Option 1: Uniform Logical System names clients by system type" for naming convention for LSN's.
    All the systems/clients (BW test and productive, ERP test only) now are assigned with corresponding LSN's, except the production ERP client. It is still without LSN and the client is not defined as Source System for productive BW system.
    So, my question is:
    Should I expect any problems if the LSN of the production client is set up now, after long time, effective productive use?
    I would mention that this is infact initial setup, not a change of LSN. Therefore transaction BDLS is not relevant, I think.
    Thanks in advance

    Hi DB49,
    I already did an initial setup of LSN in the test ERP client (that client is copy of the productive ERP client, i.e. the LSN has not been set). And everything seems to be OK.
    But the documentation says that ".... In a production system, the logical system must not be changed ...".
    "Changed" is not "ïnitial setup" of course, so there will not be any problems I hope, but ...
    SCC4 --> LSN field --> F1 -->
    "System in which applications run integrated on a shared data basis.
    The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
    In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
    The logical system is relevant in the following SAP areas:
    ALE  general: two or more logical systems communicate with one another.
    ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
    Workflow objects: the logical system in which the object is located is always included in an object's key.
    When maintaining the logical system, note the following:
    The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system."

  • How to chage logical system name SYSTEM ECC6.0

    Dear Experts,
    We need one help, in one of our production client which is on ecc6.0 and on oracle. in that when we are executing transaction rsa1. its giving error " logical system name has been change for this system ",
    then later on we have found that the logical system name in table T000 has been changed , so now we need revert back orignal name, so we require your help to do proper step to revert back the name, also we requre what other things we need to change with respect to logical system name...
    Need your help on this issue we request your immediate support for this.
    Regards
    Yogesh

    Hi Yogesh,
    Hi Anil,
    1) Logical System Name can be changed using SALE transaction.  Go to ALE -> Sending and Receiving System -> Logical Systems -> Define Logical Systems.
    2) After changing Logical systems you have to check partner Profile using WE20 and do the necessary modifications. if required
    Hope this solves your issue.
    Regards,
    Karthik

  • Logical System(ORGLOGSY) populating from which table in R/3 system

    Hi Friends,
    I would like to understand about the Logical System(ORGLOGSY) from which table or from where this logical system being populating.
    Because we could see this fields Logical System(ORGLOGSY) exist in PO item, HDR, SGR data sources.
    Can anybody give some idea, how we'll get this source system logical system name into BW system.
    SIRI

    Hi Siri,
    Check here
    V_TBDLS
    TX: RSA13----->Tools -
    >assigment of source system to source system id
    hope this will help you.  
    Thanks,
    Vijay.

Maybe you are looking for

  • Dreamweaver 8

    I'm a designer. I work a lot with CSS so I'm constantly previewing minor changes in my browser. I get the prompt when I go back to DW8, "This file has been modified outside of Dreamweaver.... blah, blah, blah." I almost always say no. When I say yes

  • How to install reader 9.3 on another hd than c:

    The download manager installs Adobe Reader 9.3 on my XP SP3 laptop perfectly. Now I do not want it installed on the default hd C: I want to specify a different location such as E: Nowhere in the process did I notice an option for this and manual down

  • Camera raw 7-2 refuses to install into Photoshop CS6

    trying to install camera raw 7-2 beta release into Photoshop CS6 on MacBook Pro, OSX 10.8.1.  Installation commences, then I get Error Code: U44M2P15. I have tried new downloads of camera raw, restarting the Mac to no avail. Any ideas???   I need thi

  • Video Preview Error: Error Compiling movie. Unknown error.

    Problem in Adobe Premiere Pro CC - Rendering movie prior to Exporting. I have cleared all Temp and Cache files to make sure I have enough space for rendering (126GB free space), but I still get a Video Preview Error message when I try to Render or Ex

  • What is my info web page for security

    When I go to sighn in I am getting a message to go to My Info web site for security information.  What is this?