BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the  Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

Similar Messages

  • Cannot find the Recv Logical system in Distribution Model

    HI experts,
    Im triying a Idoc to file scenario, the logical system for PI and R3 has been already created and assinged for the appropriate clients.
    and i ve created the port from r3 using tcode we21 and in PI using idx1 and Idx2. The RFC destination also created for PI and R3 system.. when i created the distribution model using BD64 in R2. when i assigning message type i can give the source logical system and i cant find the Receiver logical system...  Also in WE19 i cant find the receiver port (which i created in IDX1 and IDX2)..
    Could u tell me how to solve this prob???
    Regards
    Balaji

    Hii Ravi,
    Thanks for your reply,
    Yes i have created the port (RFC800) idx1 and give RFC destination which points the R3 system.
    I have assigned the meta data to that port using tcode idx2.
    And I have created port with port name "PORT800"  in R3 using we21 and give the RFC destination which points the PI system
    when im using the WE19... i gave source logical system as R3 Logical system and receiver logical system as PI Logical system.
    now im getting error like  "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS".
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM
    Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM

  • Finding "Default Logical System Name Model Instance" in DC Project

    Hi,
    While Creating an Adaptive RFCModel, one defines the
    Default Logical System Name for Model Instance & the
    Default Logical System Name for RFCMetadata.
    In which file can I find these settings at a later stage in the Project File Structure.
    Ofcourse, I can view them in the WedynproContentAdministrator under the Jco Destinations.
    But is there anyway to access them in the NWDS?
    Regards
    MK

    Hello MK,
    You'll find the Logical System Names of the JCo destinations in the file ".wdproperties" under the project structure.
    Bala

  • Changing Default logical system names of a model.

    Hi
        How could i change the
         Default logical system name for model instances:
         Default logical syatem name for RFC metadata:
        values for existing model? without recreating the model.
         Thanx

    Hi shah kond,
    you can change  rfc destinations of model in 2 differnet ways.
    firs one: right clcik on project
              from the context menu select propeties
              it will open a dialogbox from that select dynpro references then click on jco references tab
    by using add and remove buttons u can add and remove joc destnations
    2.expand ur model class double click output class.now seelct properties view.there u can change the jco destination
    hope this will use ful for u
    Regards
    Naidu

  • Changing the default logical system names for adaptive RFC models

    Hello,
    When I create an Adaptive RFC model the dialog that asks me to specify the model name, package, source folder, etc. has default values in the "Default logical system name for model instances" and "... RFC metadata".
    I know I can type in another name there but I'd like to change the default name to something that fits our naming conventions. Can I change that? If so, can someone tell me where?
    Thanks in advance!
    David.

    Suresh,
    Thank you for your response. However, that is not what I was looking for. Sorry if my post was not clear.
    I knew that I could change it AFTER the import. I also know that I can type in something else besides the default DURING the import.
    What I am asking is if there is a way to change some configuration setting so that the 'default' that comes up in the drop down DURING the import is something different than what comes 'out-of-the-box' with NWDS.
    Hope that clears up what I'm looking for.
    David.
    Message was edited by:
            David Z. Pantich

  • Change of logical system name

    Dear Experts,
    I have following situation in ECC 6 EHP4 system:
    a system copy of PRD system was peformed on QAS. POst system copy BDLS was NOT run, and logical system of QAS client was maintained manually.
    Now  client 300 in QAS has logical system as QASCLNT300 (after copy it was PRDCLNT300). The problem is that many accounting documents still point to PRDCLNT300 and hence can not be viewed now since log sys is QASCLNT300 now.
    I can not run bdls now bcoz for BDLS target logical system should be new. Also for last few months new accounting docs has been generated for QASCLNT300.
    Is there any way around? pls suggest
    -Thanks,
    Richa

    This is a situation , where you cannot run BDLS now and you face issues with accounting docs .
    As far as I feel , you will have have to redo the system copy and run BDLS again. The logical system name should never be maintained manually in SCC4.
    Edited by: Ratnajit Dey on Jan 2, 2012 12:16 PM

  • Logical system same in DEV/QAS/PRD for ALE

    Hi friends,
    We haven't used ALE but now need to set it up. Problem is, DEV and QAS are copies of PRD so all three have the same logical system name. I read about how using bdls to rename the logical system can create inconsistencies and am worried it can ruin our transport system.
    Appreciate your comments, thanks & best regards.
    Claudio

    Using BDLSS in comaprsion to BDLS - logical systems can also be converted remotely in all partner system.
    Please refer: SAP notes
    544509 - ALE: Converting the name of the "logical system"
    121163 - BDLS: Converting logical system names
    1478123 - FAQ: Source system
    Divyanshu

  • SetConnectionProvider() vs commond logical system names

    I inherited a project from a student that contains 1 webdynpro DC. There are 7 models defined with multiple RFCs per model.
    Originally they had all their own meta and model data logical system names which resulted in a total of 14 JCOs defined in WebDynPro Content Administrator in Portal (2004s SP13).
    I followed the instructions in the blog "How to change logical system names after model import" (/people/bertram.ganz/blog/2006/01/27/web-dynpro-adaptive-rfc--how-to-change-logical-system-names-after-model-import).
    I did this. I defined one name for the model data and applied it to all 7 models and I defined 1 for the meta data and assigned it to all 7 models (in dictionary).
    I then deployed my application and sure enough only 2 JCOs were created which is what I wanted. I edited them and my application works fine.
    What I am trying to understand is the implication of this approach verus using the setConnectionProvider() method.
    Any feedback would be appreciated. I am suspecting my approach is not really optimizing the # of connections to R/3 even though I have only 2 JCOs instead of 14 originally but I cannot find the info to help me figure this out.

    Hi Dean,
    Each model utilises one jco connection. So, if multiple models can work on single connection (without violation of backend LUWs), then instead of creating n connections, you can share one connection among them using the setConnectionProvider method.
    Therefore, after creation of the the first model, you can pass on this model object to other models through their setConnectionProvider() method passing the first model object.
    Though I've not used it, its clear to work this way when you have related RFCs to run in the same LUW.
    Hope that's clear.
    Regards,
    Rajit

  • Logical  system name to be updated while client copy--URGENT HELP REQUIRED

    Hello All,
       I have a  query regarding the "Logical System name" updation during Client copy.
      When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
      There is  a  std transaction BDLS through whcih w e can change the current Logical system name to  a  new one but this  seems to work fine for System copy but not for Client copy.
      So when i make  a client copy of  SRM masters  for Production system,is there  any other std  way wherein i can change the "Logical system name " for the  backend or  do i have  to write a  CUSTOM program wherein entries  for  the Backend Logical system name in tables like CRMMLSGUID will  be updated  with  the new  Logical system name?
       Any help on this is  appreciated.
    Thanks & Regards,
    Disha.

    Disha,
    Yes, I did it twice and it worked fine.
    The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
    SRM checks this GUID in CRMMLSGUID table.
    If is not the same one, then replication process fails.
    The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
    Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
    The issue is exactly ours: around system/client copy.
    In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
    We have to take some risks sometimes...
    Rgds
    Christophe

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

  • Help for Job BDLS - Logical System Conversion aftrer System Refresh

    hi SAP Basis Gurus,
    We have restored production data to test system. After that we are doing Logical System conversion - Renaming of Logical System Names. For that we are running BDLS job. The program used is IBDLS2LS.
    Now one job is running for more than 200000 seconds.  Job is doing "Sequential Read" on table ZARIXCO40.  The following has been updated in the jobs log:
    01.02.2008 10:20:06 Processing table ZARIXCO40
    02.02.2008 01:59:56 Processing table ZARIXCO40
    02.02.2008 22:26:44 Processing table ZARIXCO40
    02.02.2008 23:04:05 Processing table ZARIXCO40
    So as per above log, it looks like job got stuck in loop for table 01.02.2008 10:20:06 Processing table ZARIXCO40.
    The oracle Session is showing following SQL Statement:
    SELECT
    /*+
      FIRST_ROWS
    FROM
      "ZARIXCO40"
    WHERE
      "MANDT" = :A0 AND "LOGSYSTEM" = :A1 AND ROWNUM <= :A2#
    ~
    Execution Plan is :
    ~
    Execution Plan
    Explain from v$sql_plan: Address: 00000003A2FD5728 Hash_value:  2772869435 Child_number:  0
    SELECT STATEMENT ( Estimated Costs = 4.094.270 , Estimated #Rows = 0 )
            3 COUNT STOPKEY
                2 TABLE ACCESS BY INDEX ROWID ZARIXCO40
                  ( Estim. Costs = 4.094.270 , Estim. #Rows = 32.799.695 )
                    1 INDEX RANGE SCAN ZARIXCO40~0
                      ( Estim. Costs = 418.502 , Estim. #Rows = 65.599.390 )
                      Search Columns: 1
    ~
    Table has been analyzed today. See the details below:
    ~
    Table   ZARIXCO40
    Last statistics date                  02.02.2008
    Analyze Method              mple 16.623.719 Rows
    Number of rows                        65.599.390
    Number of blocks allocated             2.875.670
    Number of empty blocks                     7.912
    Average space                                934
    Chain count                                    0
    Average row length                           313
    Partitioned                                   NO
    UNIQUE     Index   ZARIXCO40~0
    Column Name                     #Distinct
    MANDT                                          1
    KOKRS                                         14
    BELNR                                  2.375.251
    BUZEI                                      1.000
    ~
    Index used for this table is also analyzed today:
    ~
    UNIQUE     Index   ZARIXCO40~0
    Column Name                     #Distinct
    MANDT                                          1
    KOKRS                                         14
    BELNR                                  2.375.251
    BUZEI                                      1.000
    Last statistics date                  02.02.2008
    Analyze Method              mple 24.510.815 Rows
    Levels of B-Tree                               3
    Number of leaf blocks                    418.499
    Number of distinct keys               65.480.722
    Average leaf blocks per key                    1
    Average data blocks per key                    1
    Clustering factor                     40.524.190
    ~
    Can you please let me know what could be the issue and how to resolve this issue so that job gets completed. Normally this job runs for 1,00,000 seconds. I can not afford to cancel this job and run again.
    Any help is Highly appreciated,
    Thanks
    Best Regards,
    Basis CK

    Hi Markus,
    The stastics of the table is already updated today. After that also it is not going faster. It is doing "Sequential Read" for more than 5 hours and then one update is issued. And in the job log, all other tables are preocess only once, only this table is selected to processed 4 times which is very abnormal.
    01.02.2008 07:43:59 Processing table ZARIXCO11
    01.02.2008 07:45:36 Processing table ZARIXCO16
    01.02.2008 10:17:20 Processing table ZARIXCO21
    01.02.2008 10:20:06 Processing table ZARIXCO26
    01.02.2008 10:20:06 Processing table ZARIXCO29
    01.02.2008 10:20:06 Processing table ZARIXCO33
    01.02.2008 10:20:06 Processing table ZARIXCO37
    01.02.2008 10:20:06 Processing table ZARIXCO40
    02.02.2008 01:59:56 Processing table ZARIXCO40
    02.02.2008 22:26:44 Processing table ZARIXCO40
    02.02.2008 23:04:05 Processing table ZARIXCO40
    ~
    I guess this will keep on going like this and not sure when it gets complete. Any other thing you can suggest which help to resolve the issue.
    Thanks
    Best Regards,
    Basis CK

  • Logical system not updated in the business system adapter specific data par

    Hello Guys,
    I changed a logical system name in the sld for a business system and that that is not reflected in the Integration directory adapter specific data tab.
    I did a cache refresh using :
    1) sxi_cache --- Full cache refresh, delta cache refresh
    2) Hard cache refresh
    3) In ID "Cleared SLD data cahe "
    4) Refreshed the exchange profile
    But no use
    Can you please tell how i can get the logical system name for the business system updated in the Integration Directory.

    When you change it in SLD and if not getting replected in the ID...make sure you run the cache again, perofmr the comeplete cache....
    there is an option under the adapter specific mesage attributes compare with SLD you can click that, is nthing happening after clicking it?
    Run the cache in the ID are there any errors there?
    check the RWB cache monitoring is everything green there?

  • 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

  • In CIF customer exit there is no information about the logical system

    Dear All,
    we have a SAP R3 system (ver 4.7) connected to 2 SAP APO systems.
    we need to differentiate the UE code in R3 by APO TARGET SYSTEM.
    In the CIF userexit used:
    EXIT_SAPLCLOC_001
    EXIT_SAPLCSRS_003
    EXIT_SAPLPGS1_001
    EXIT_SAPLCSTK_001
    EXIT_SAPLMEAP_001
    there is no information about the logical system (source, destination
    etc.) The control parameters are not provided to the user exit.
    I found a note 1060634 where the parameter have been added to
    EXIT_SAPLCSLS_002 , but not to all other exits.... do you have any clue on how we can proceed?
    Thank you !!
    Best Regards , Barbara

    Found the answer, to bad i cannot give points to myself :-P
    In the ABAP i use the E_T_RANGE output structure.
    That structure has several fields (sign, opt, low, high).
    In my ABAP i stored the same value in the low and high field.
    This should work fine for normal (flat) characteristic values.
    However, because i use a hierachy i should enter the 0HIER_NODE value in the high field.
    For details see: SAP NOTE: 912473
    Regards

  • Problems with CIF (Logical system not assign to BSG)

    Hello,
    We are sending all master data from ECC to APO. We set up the CIF in DEV and all worked fine. But when we try to send the data from ECC to APO in QA an error appears. It says that the logical system is not assign in the BSG. Apparently the configuration that we have in DEV is the same that we have in QA. The logical systems in all instances (DEV & QA) have the same name. Could this be the problem?
    Thanks,
    David

    Hi David,
    1) Check whether BSG is defined in customisation under the below
    link
    SAP - Implementation Guide > Integration with SAP Components
         >  Integration via APO Core Interface (CIF)    >
        Basic Settings for Creating the System Landscape   > Maintain Business System Group
    2) Check the BSG is assinged to the logical system under the
    spro transaction
    SAP - Implementation Guide > Integration with SAP Components
         >  Integration via APO Core Interface (CIF)    >
        Basic Settings for Creating the System Landscape   >
    Assign Logical System and Queue Type
    3) Check BSG is showing in APO material master for a location
    product under "Properties" tab.
    Regards
    R. Senthil Mareeswaran.

Maybe you are looking for

  • Release Stratey & Open Period

    Hell SAP Gurus Pls clarify the following: 1. I have maintained release strategy for PR & PO     with clasification.  Green light is showing for the strategy which i have maintained.  In which i have selected plant , material group, purch. org, doc ty

  • Gallery does not render online

    I have been testing a gallery using IIS 5.0 on localhost and it works fine. I uploaded the folders to my IIS server at CrystalTech and nothing shows but the outline of the gallery selection folders. You can see the results here - http://www.toastands

  • OpenGL Ps CS5 died after CS6 beta

    Using Ps CS5 12.04 on win7x64, 12GB,  Radeon 6780 1GB, dual HDD and dual monitors since last Oct when I bought this new PC and its always been fine with openGL even with extensions added and dual monitors in workspace setup. Still worked same most of

  • IPad 3 with new iOS 6 cannot determine location.

    I just downloaded iOS 6 for my iPad 3, and Siri, as well as Maps, cannot determine my location. All location features are enabled. Is this just a bug, or am I doing something wrong?

  • Photo Shop CS5.1

    I downloaded Photoshop CS5.1 from Adobe volume licensing portal. It is asking for the cd during the install