Not converting the logical system through BDLS

Hi Experts,
I did the system copy of BI system from production to developemnt
To change the logical system  in RSA1 --> Source systems
I have choose client role as test in scc4 and in tcode BDLS i have given the old logical system name new  logical system name
after completing the job RBDLSMAP i checked in the RSA1 there is no change in logical sytem
i got the following message
SM37 log
Job started
Step 001 started (program RBDLSMAP, variant &0000000000005, user ID ABCD)
Logical system name ABC500-1 does not match SAP's recommendation
Job RBDLSMAP no longer exists
Converted table: 'RSSTATMANSTATUS'; number of changes: ''
Converted table: 'RSSTATMANSTATDEL'; number of changes: ''
Converted table: 'RSSTATMANREQMAP'; number of changes: ''
Converted table: 'RSSTATMANREQMDEL'; number of changes: ''
Converted table: 'RSSTATMANPSA'; number of changes: ''
Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
Job finished
Spool log
Table Name                Field Name       Number of Relevant Entries    Number of Converted Entries
/BI0/ABP_CUST00*          LOGSYS                              0                              0
/BI0/ABP_CUST40*          LOGSYS                              0                              0
/BI0/ABP_VEND00*          LOGSYS                              0                              0
/BI0/ABP_VEND40*          LOGSYS                              0                              0
/BI0/ACDS_DS0400*         LOGSYS                              0                              0
/BI0/ACDS_DS0440*         LOGSYS                              0                              0
/BI0/ACDS_DS0500*         LOGSYS                              0                              0
/BI0/ACDS_DS0540*         LOGSYS                              0                              0
/BI0/ACLM_DS0300*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0340*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0600*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0640*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACRM_CMGL00*         LOGSYS                              0                              0
/BI0/ACRM_CMGL40*         LOGSYS                              0                              0
/BI0/ACSM_LINK00*         LOGSYS                              0                              0
/BI0/ACSM_LINK40*         LOGSYS                              0                              0
/BI0/AGN_BP00*            GN_PAR_LSY                          0                              0
/BI0/AGN_BP40*            GN_PAR_LSY                          0                              0
/BI0/AGN_CONV00*          LOGSYS                              0                              0
/BI0/AGN_CONV40*          LOGSYS                              0                              0
Could any body help me in this
Thanks & Regards,
Arun

Hi experts,
I have done the system copy form Production to Developement.
Transfermations and DTP(Data transfer process) are still connected from Produciton R3 which  should be from developemnt R3.
I have tryied to change the logical sytem name through BDLS. But the logical system name is not changed
i got the job log which is in above conversation in my thread.
Please let me know how to change the logical system name in Transfermations and DTP in RSA1
Thanks & Regards,
Arun

Similar Messages

  • BI 7.0,  BDLS is not converting all logical systems for datasources

    Hello all,
    We have refreshed an ECC system, and during the post steps in BI, we were running into issues.
    We've ran BDLS to convert the logical system from ECCCLNTXXX to ECCCLNTYYY, but it's was not converting for several datasources.
    One in particular was causing several problems, and terminating the conversion.
    0FC_CI_01.  It is still hanging on to the old logical system.  BDLS terminates with the following information:
    Short text:
    Active version of emulated 3.x DataSource 0FC_CI_01 cannot...
    Basically, the exact symptom of Note 936644.
    Eventually, through a series of trials, we discovered we could assign non-active sourcesystem/logical system combinations to the objects.  As a result, we deleted the source systems entirely, ran BDLS to the ECCCLNTYYY, then recreated the sources.
    This finally worked.  What I need now is a root cause.  Why would BI refuse to change the logical system of an object to an active one, but have no problem with an inactive?

    Mike,
    After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
    Refer to the below doc for detail. Also refer to note 886102.
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
    Below note talks about similar issue.
    How to change all infosources to the new source system automatically
    Hope this helps.

  • /SAPAPO/SYSDIR - Entry not found for Logical System

    Hi Guys...
    I have upgraded a new SCM 5.0 box from a database copy of APO Production. Ran the BDLS to convert the logical system pointing to Quality box. The challenge I am facing is to define a Distribution Definition in SPRO for Planned Independent Requirements. One of the values required in the Publication Definition is 'Logical System'. I need to point this APO Quality system to R/3 Quality system.
    Since this happened to be an upgrade from an APO production database, this does not have the R/3 Quality system in the list of Logical Systems when I do the drop down. All it has is the logical system name of the APO Quality System (Self) and R/3 Production System.
    When I create a new entry by manually entering the logical system name of R/3 Quality System, it says no entry found in /SAPAPO/SYSDIR. My question is, how do I populate this directory with the logical system name of R/3 Quality system? Your answer at the earliest will be highly appreciated with correct points.
    Thank you.

    Location in APO is nothing bu the Plant Master Data ( Or Vendor Master, Customer etc)
    Goto Transaction- /sapapo/loc3 to view both the plants JNa and JWA
    I think that you would have to define the integration mdoels which define what data( MASTER and TRNSACTIONAL) has to flow from R3 and APO and vice versa.
    Contact your APO Functional Team to set these up for the new logical system(SCM Quality) in the transactions- CFM1 and CFM2 and define the data which has to flow between the systems ( R3 and APO)
    For your 2 locations:
    Follow these steps in the meanwhile with the help of APO Functional Guy
    (1) Define the CONNECTIVITY steps which I have mentioned in the previous reply in R3 Quality
    (2)Goto transaction- CFM1
    Enter a model name- LOC( Any Name)
    Enter a logical system- SCM Quality
    APO Application- Lo(Any NAme)
    Select PLants check box and
    IN the right hand side- General selection options input the 2 locations- JNA and JWA in the Plant Field
    Save this and execute and then save it.
    (3) Goto CFM2 and automatically you should see the same model as you deifned in CFM1.
    Execute this.
    The above steps make sure that the Location( Or PLant) master data is sent over to APO Quality.
    Now the source system should have been changed on the location masters in APO.
    Hopefully this should resolve the issue and you will be able to enter a publication type for your locations- JNA and JNW
    There are many other steps which you need to do apart from these for your entire setup.
    Good Luck with this problem
    Regards
    Kumar

  • BDLS is not converting DataSource source systems

    After running BDLS on our BW system to convert from logical system DV1220 to ED2CLNT220 we found that the source system assignments for our datasources are not getting converted.  Specifically table RSISOSMAP which holds the mapping between the infosource and the OLTP system. We did check several of our ODS's and Info-cubes and the logical system were changed from DV1220 to ED2CLNT220.
    Any help would be appreciated.
    Regards,
    Mike...

    Mike,
    After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
    Refer to the below doc for detail. Also refer to note 886102.
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
    Below note talks about similar issue.
    How to change all infosources to the new source system automatically
    Hope this helps.

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • This is not the logical system of controlling area 2000

    Hi,
      While creating Activity type / price planning in kp26....i am getting the the information like...
    "This is not the logical system of controlling area 2000"..
      but i am using the company code 3000 which is assigned to the controlling area 2000....
    so...kindly tell me how to come out of this....
    Thanks in advance..

    Hi,
    I assume the error is either KC028 or  COCORE081. In any case: please check if you have activated an ALE scenario for the relevant controlling area in TA OKKP1. Then check if the logical system differs from the system defined for you client in TA SCC4. If this is the case, then that is the reason for the error.
    Regards
    Karl

  • First name is not transmitted to the other system through Idoc

    Hi all,
    Here customer is created in R/3 system & then transmitted to the other system through I doc.
    Issue is first name is not transmitted properly or is transmitted but nit correct value.
    I checked the segments of respective i doc in we05 there i could see right values. But in target system it is totally wrong or the word 'CONSTANT' is coming.
    what could be the reason & where i can find it out.
    Please help me
    Thanks
    JM

    Hi
    The issue should not be in SAP. You need to check with the middleware system which reads the data from SAP and triggers an IDOC and sends it to the other system.
    Regards

  • 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

  • ERROR- "Creating Logical system through BD54"

    Hi,
    I need to create a new client as a copy of an existing client. Before that I need to create a Logical System through DB54. But when I am executing the T-Code BD54 the system gives an information popup saying u201CChanges to Repository or cross-client Customizing are not permittedu201D and there is no new entry tab in BD54. What can be the solution?

    Hi,
    Now when i am clicking on start immediately/schedule as backgroung job the following error appears. I have created the RFC also and its working properly. 600 is the newly created client.
    RFC destination for client copy in systems with Financials Basis
    (FINBASIS) component.
    The system could not find any suitable RFC destination for processing
    for client 001.
    This note also appears if an RFC destination was found but this does not
    work.
    o   RFC destination: FINB_TR_DEST
    o   Error text:
    Proceed as follows to eliminate this error:
    1.  Start the wizard to create a new RFC connection
    or perform the following steps manually:
    1.  Create an RFC destination with the target ZK>source client of client
    What can be the solution?

  • How do you identify the Logical system in start routine of a transformation

    My scenario is this.  I have five r3 systems that I am extracting from.   In the start routine of the transformation from the r3 data source to my data store I  am going to delete data and I need to know the source system id.    How do I identify the logical system or source system id in the transformation.  Is there a system field that contains this information.    I do not want to hard code the source system id in the routine.

    hi
    have a lool at tables rsreqdone and rsbkrequest with a join you should be able to determine the source.
    regards
    Boujema
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).
    Edited by: Boujema Bouhazama on May 9, 2008 12:04 AM

  • Parallel How many times user can login to the SAP system through ITS

    Hello all
    We are using the ITS ---620 and following 46D R/3 system 
    R/3 system details:
    Kernal :
    kernel release :46D
    O/S :SunOS 5.8 Generic_108528-05 sun4us
    We would like to now, At a time How many times user can login to the SAP system through ITS
    Kindly letus know  if any one have idea about parameter which can restrict the end users to u201CNu201D times/ sessions.
    Transaction SITSPMON/SMICM are not working in R/3 system as it is 46D.
    We found that parameter u201Clogin/disable_multi_gui_loginu201D works with SAPgui logons.
    System logons using the Internet Transaction Server (ITS) or Remote Function Call (RFC) are not affected by this Parameter u201Clogin/disable_multi_gui_loginu201D
    I need similar parameter u201Clogin/disable_multi_gui_loginu201D for the ITS users.
    Thanks

    I have searched all docs and notes.
    Everytime the answer is PArameter for multi_gui_logonis not applicable for SAP Gui for HTML ( Browser )
    The functionality does not exist for SAP Gui for HTML.
    Regards,

  • Error in the logical system (BW - R3 connection)

    Hey guys, i need help, actually i created a connection between BW and R3 system, but i think i wrongly assigned the details to another BW system and now whenever i tried to load the data, it's not being processed.
    And i checked and it shows me that the connecetion is between source system (538) and BW (B3T800), though my BW client is BW (BW TEST). so how do you think i can change my background users i assigned while creating the source systems, because i think, while creating the source system, i used wrong background users. So instead of connecting via logical system (BW test), its connecting via (B3T800) to SAP R3 (538).
    --> Also i tried changing the Logical system name, as i checked and showed that for my BW client now it has a entry of the BW system (B3T800) and when i tried chnging it, it let me change that, but when i went to the RSA1, SAP doesn't let me access that, saying a message "your logical system has been changed", so can i change the logical system, do you guys think my problem will be solved?
    Regards,
    Amit Jaidka

    I have checked in SM37 taking that request number and when i checked the job log , its showing
    5 LUWs confirmed and 5 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    Lock table overflow
    Job cancelled after system exception ERROR_MESSAGE
    what is the reason for this termination in R/3.
    Thanks

  • Use and impact of the logical system (SCC4)

    An error has been made in our SAP system (production environment), transaction SCC4. The field «Logicial system» has been changed from «PRD460» to «QAS460». It has been left this way for few weeks and when we realized the mistake, we changed it back from «QAS460» to «PRD460».
    For few hours, the document numbers in MM (t-code MIGO) were generated, but were not found in t-code MB03. We were able to generate them manually in t-code SM13 and the problem was solved.
    What is the use of the «Logicial system» ? What could have been the impact on our database and on the integrity of our system of having the wrong logical system set to our production environment for few weeks ?
    Thanks.

    Hi,
    Logical System Names
    When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.                               
    A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
    Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
    Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
    You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
    Anil

  • To get the logical system names of all the child systems in a CUA envirnmnt

    Hi Gurus ,
    Is there any table where we can find the logical system names of all the child sytems in a CUA environment .
    This is for a requirement that i need to develop an automated process where we can reset the password of all the child system in a CUA environemt when requested by the user at once .
    I found some tables such as V_TBDLS , but they do not contain the exact information what i need .
    Thanks in advance ,
    Harshit Rungta

    Hi,
    You are in the right track. BD54 will show you the logical system name for all the existed systems in CUA.
    Else you can also go to your CUA system and execute t-code SALE --> Basic Setting --->Logical Systems  ---> Assign logical system to client -
    > Display details
    here you can see logical system names for all the clients assigned to CUA.
    Thanks,
    Deb

  • Is it possible to change the Logical System name in ID

    Hi,
    I am doing a file to Idoc scenario. My requirement is to overwrite the logical system name, which is set in SLD for sender (system). Is it possible to overwrite it in ID or in mapping somewhere.
    Thanks,
    Dehra

    Hi Dehra,
           Go through the below help file of SLD. It will give you information regarding logical name as well:
    <a href="http://xiserver:50100/sld/doc/sld.pdf">http://xiserver:50100/sld/doc/sld.pdf</a>
    Regards,
    Subhasha

Maybe you are looking for