Transfer Structure - Transport Problem

Hi Experts,
I am transporting infosource from BW DEV to BW QA ( Datasource is transported and it is replicated) but when the request is imported in QA it gives me error saying " Transfer structure does not exist " . This Infosource is used for Remote Cube .
Could anyone help me in this as in QA I see Infosource in Deactivated state even though remote cube( based on this Infosource) is active .
Regards,
Vijay.

hi Vijay,
seems transfer structure not collected, maybe source system not choose/assigned. try in bw dev, with infosource selected for transport, choose grouping 'in dataflow before' and collection mode 'manual', click 'source system assignment' and make sure your source system is marked. then execute to collect objects. after finished, expand the infosource, and make sure there is transfer structure and marked. then create transport request, stms and transport again. hope this helps.

Similar Messages

  • Transfer structure Activation Problem

    hi guys...
    i've just installed new bw system and done all post processing steps correctly...
    while working in this bw...
    if i try to activate any Transfer structure, it is giving an error with the message...
    'no ddic tabel /bic/000004000... exists...'
    if i go to detailed message...
    it is saying that this table shud be created by the system automatically.. otherwise create one in the database utility(se14)...
    what does it mean... i'm not understanding what table is this and y i'm being asked for this...???
    pl tell me the solution how to rectify this problem...
    thank you all
    regards
    nithin

    hi...
    verson is 30B
    if i try to activate again the tabel number in the error message is changing...like /bic/00005000... some number...
    is it any problem of any number ranges or what...???
    regards..
    nithin

  • Transfer structure Transport ?

    Hello Experts,
    Transport from System1 to System2.
    Transfer structure, data source, transfer rules, infosource are already present in the target system system2.
    I made modifications to the transfer structure in system1 and added just the transfer structure to the transport request to system2. It failed with these messages. Highly appreciate your suggestions.
    Error: "There is no Datasource with these attributes"
    Warning: "Reference to transfer structure ABC_AB not available. No activation possible".
    Wondering if I have to include the datasources in the transport request along with the modified transfer structure. 
    Thanks,
    Sweatha.

    Hello Sweatha,
    If you have made changes in the Transfer Structure and the transfer rules, I would advice you to transport the entire infosource to system2.
    Hope it helps.
    Ravin

  • Error in Transporting the Transfer structure

    Hi can any body tell me . Iam getting this error  while transporting from BW System the transfer structure for 0HR_PY_1_CE.
      1. Transfer structure 0HR_PY_1_CE_LA does not exist.
      2. Error RSAR 440 during after import handling of objects with type(s) ISTS
      3. Errors occurred during post-handling RS_AFTER_IMPORT for ISCS L
    I have  activated the transfer structure  through this programme - program RS_TRANSTRU_ACTIVATE_ALL.

    Check the below notes:
    Note 1009638 - RSAR 440 when you activate transfer rules    applicable for BI7.0 Less than SP12.
    Note 736668 - RSAR 440: Transfer structure & does not exist   Applicable for 3.x system.
    Please check the above Notes and based on your system patch level and issue you need to choose the right one. Second one deals with the Hierarchy.
    Hope this helps..
    Murali

  • Unable to activate Transfer Structure for Generated Datasource in BW3.5

    HI Experts,
    We have a scenario where the data needs to moved from DSO A to Cube B
    we have clicked the Export datasource and created 8(ODS A)
    when created IP for this it gave us all selection in selection screen but we required only 3 Characters
    <br> so we maintained the export datasource and saved it when we again tried to generate datasource it went to short dump       
    <br> with following messages:
    <br>  Short text of error message:                                               
    <br>  Serious internal error:              <br>   
    <br><h4> Transfer structure got deactivated and we are unable to activate it again even by RS_TRANSTRU_ACTIVATE_ALL <br>
    </h2>
    <br>                                                                               
    <br>Technical information about the message:                                   
    <br>  Diagnosis                                                                 
    <br>     A serious internal error occurred. It could not be corrected.         
    <br>  Procedure                                                                 
    <br>      The following information is available on this error:                 
    <br>      1.                                                                    
    <br>       2.                                                                    
    <br>      3.                                                                    
      <br>     4.   OSS note                                                         
       <br>    Check the OSS for corresponding notes and create a new problem        
    <br>      message if necessary.                                                 
    <br>  Message classe...... "RSAR"                                                
    <br>  Number.............. 001                                                   
    <br>  Variable 1.......... " "                                                   
    <br>  Variable 2.......... " "                                                                               
    <br>Source Code Extract                                                                               
    <br>Line  SourceCde                                                                               
    <br> 514         IF g_subrc NE 0.                                                 
    <br>  515           MESSAGE x001.                                                  
    <br>  516         ENDIF.                                                           
    <br>  517 *       Check new version neccessary                                     
    <br>  518         l_curr_version = c_s_is_admin-odsversion.                        
    <br> 519                                                                          
    <br>  520         IF l_new_version EQ rs_c_true.                                   
    <br>  521           IF i_without_versioning EQ rs_c_true.                          
    <br>  522             MESSAGE e023 WITH c_s_is_admin-odsname_tech                  
    <br>  523                               c_s_is_admin-isource                       
    <br>  524                     RAISING no_psa_version_allowed.                      
    <br>  525 *         ELSEIF i_without_versioning EQ 'C' AND                         
    <br>  526 *                i_without_transport  EQ rs_c_true.                      
    <br>  527 *--         special handling for migration.                              
    <br>  528 *-          current system is target system no transport request         
    <br>  529 *-          necessary if a new version is needed                         
    <br>  530           ELSEIF i_without_versioning EQ 'C'        AND                  
    <br>  531                  i_without_transport  EQ rs_c_false.                     
    <br>  532             RAISE inconsistency.                                         
    <br>  533           ENDIF.                   .                                     
    <br> 534                                                                          
    <br>  535           IF i_objtype = rsa_c_istype-data.                              
    <br>  536 *           check type of InfoSource first                               
    <br>  537             SELECT SINGLE issrctype FROM rsis                            
    <br>  538                            INTO l_isrctype                               
    <br>  539                           WHERE isource = c_s_is_admin-isource           
    <br>  540                             AND objvers = rs_c_objvers-active.           
    <br> 541             IF sy-subrc <> 0 OR l_isrctype = rsarc_c_issrctype-ods.          
    <br> 542 *             if generated ODS InfoSource,                                   
    <br> 543 *             no PSA versioning possible                                     
    <br>>>>>               MESSAGE x001.                                                  
    <br> 545             ENDIF.                                                           
    <br> 546           ENDIF.                                                             
    <br> 547           l_next_version = l_curr_version + 1.                               
    <br>548           c_s_is_admin-odsversion = l_next_version.                          
    <br> 549           l_transtru_odsname+13(3) = l_next_version.                         
    <br> 550 *         Don't use old progname but create new one                          
    <br> 551           CLEAR l_progname_ods.                                              
    <br> 552         ELSE.                                                                
    <br> 553           l_next_version = l_curr_version.                                   
    <br>554         ENDIF.                                                               
    <br>555                                                                               
    <br> 556       ENDIF.                                                                 
    <br> 557 *     set transtru_names for IDoc                                            
    <br> 558       c_s_is_admin-odsname       = i_transtru_name.                          
    <br>559       c_s_is_admin-odsname_tech  = l_transtru_odsname.                       
    <br>560     WHEN OTHERS.                                                             
    <br> 561   ENDCASE.                                                                   
    <br> 562
    Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 8:59 AM
    Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 9:03 AM

    Hi,
    Delete all the DS and try creating from starting, to export DS, with correct selections, and then Activate the Transfer Structure..
    Hope Helps,
    Regards,
    Laj

  • Transport Problem  - flow from one DSO to another DSO.

    Hi all experts,
    I am loading one DSO from program.  And based on first DSO, I am loading second DSO.
    In other words, second DSO is getting loaded from first one.
    While transporting from dev to quality system do i need to activate and include info-source of first DSO in the request ?
    <b>or</b>
    mere activation of both DSOs and update rules will be sufficient ?
    Waiting for your reply..
    Regards
    Vinay

    Thanks Patric.
    I am facing one problem.
    In one single request I have included two DSOs. ( One DSO is loading second DSO. ) Also I have included Info-source (generated from first DSO, commn structure and transfer structure).
    I also activated the update rules. But transport is getting failed showing error as below
    Start of the after-import method RS_UPDR_AFTER_IMPORT for object type(s) UPDR (Activation Mode)
    Update rules {tech name of update rules} read in version M
    Error when activating update rule {tech name of update rules}
    Activation of the update rules for {second dso} { 8first dso }
    IC={second dso} IS={ 8first dso } error when checking the update rules
    Can you help in this issue ?
    Regards
    Vinay

  • Copy transfer structure transfer rules from one client to other client

    Hi
    Our R3 client 100 is mapped to BW client 100.
    R3 client 100 is source system in BW.
    As the master data is created by users in R3 client 200 we want to get the data from client 200 to BW. We dont want to replicate each datasource and do all stuff form scratch for client 200.
    Now the question is as we need to create transfer rules, transfer structure for all master data objects for client 200 in BW.
    1. Going to create R3 200 client in BW.--this is possible.
    2.Like create a transport connection in BW for client 200 for all master data infoobjects transfer rules transfer structure,process chain, infopackages..etc
    3.Do the source system mapping for new client 200.
    4.and then execute the process chain..
    What are the best ways to achieve this.
    creating all transfer structure and transfer rules only for those we are loading daily ..rather than all active ones.. How can I get the list of that master data that is loading daily.. and how easily can I create transfer structure..etc dependent objects in one go than manually.
    Any help or thoughts are appreciated..
    can anyone throw some light please....

    Hi,
    BW is not client dependent!!! When you sign on to BW, you have the client required. However, this field does not appear in any table (master data, ODS, cubes, whatever).
    This means that a same BW server with a single client can have multiple R/3 connections (for multiple R/3 clients).
    The database do not care about the client in BW. The data will be consolidated.
    So, you do not need any new client in BW, just two R/3 connections for your two clients.
    Regards,

  • Transfer structure have two different tech names?

    Hi BW experts,
    we got issue in transfer structure which have two different technical names:
    ZCUSTOMER_DC and
    ZCUSTOMER_PS
    where zcustomer is the info source name.
    The impact: PSA data can't be accessed ...
    Any help and feedback is highly appreciated!
    Regards,
    Lilly

    Hi Dinesh,
    Thanks for your feedback.
    Unfortunately, this issue is thru our system landscape incl. production. If I try to delete the DS assignment I will lose data in the PSA, right?
    However, I did try to delete the DS assignment and delete the info source (the one which is available on dev only), failed, the message I get is info object xyz still being used in communication structure (I believe it must the TS with old prefix), deletion not possible.
    The problem is I am not able to delete the TS with old prefix , because it is not visible in system (AWB).
    Any further feedback appreciated

  • Transfer structure copied into another structure ?

    Hello ,
    Iam trying to transport an transfer structure and iam getting an error and when i looked into the SE09 log i noticed somethng strange .
    I am not understanding why a transfer structure is copied into another structure as shown below in Bold  while transporting ??? is this somethng normal or somehtng happening strangely in my system ?
    "   Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
      <b>Transfer structure 80MATERIALM_CB activated under the name 80MATERIALM_CA</b>
      It is not necessary to copy dependent objects for transfer structure 80MATERIALM_CA
      <b>Object 80MATERIALM object version   not found in table</b>
      Activating Transfer Rules 80MATERIALM_CA ...
      3 Transfer Rule(s) of the transfer structure 80MATERIALM_CA removed from control table
      3 InfoObject(s) of the transfer structure 80MATERIALM_CA removed from control table
      Formulas have been saved
      Saving Structure /BIC/CACA80MATERIALM ...
      Activating Structure /BIC/CACA80MATERIALM ...
      Saving Structure /BIC/CCCA80MATERIALM ...
      Activating Structure /BIC/CCCA80MATERIALM ...
      Saving Structure /BIC/B0000015000 ...
      Activating Structure /BIC/B0000015000 ...
    <b> Object 80MATERIALM object version   not found in table</b>
      Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Delete Mode)
      Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Delete Mode)
      Start of the after-import method RS_ISFS_AFTER_IMPORT for object type(s) ISFS (Delete Mode)
      Start of the after-import method RS_ROUT_AFTER_IMPORT for object type(s) ROUT (Delete Mode)
      Errors occurred during post-handling RS_AFTER_IMPORT for ISFS L
      The errors affect the following components:
         BW-WHM (Warehouse Management)
      Post-import methods of change/transport request CD3K900107 completed
           Start of subsequent processing ... 20060821140054
           End of subsequent processing... 20060821140146"
    Your inputs are highly appreciated !!

    Gimmo,
    Do u mean i need to install and transport 0material to test system ??? coz currently i didnt install 0material in dev also thnking i dont need coz its an export datasource .
    Regards
    Deenu

  • Transfer structure  0BUS_AREA_TEXT_HA does not exist

    We are transporting InfoCube - 0FIGL_C10. which we had collected in a transport request with grouping as in Data Flow Before. This request ended with return code 12 with error message "Transfer structure 0BUS_AREA_TEXT_HA does not exist, Error RSAR 440 when handling objects with type R3TR ISTS"
    After this I collected the transfer rules of 0BUS_AREA_Text with grouping as dataflow before and after. the transport of this request also failed with return code 12 with the same error message "Transfer structure 0BUS_AREA_TEXT_HA does not exist, Error RSAR 440 when handling objects with type R3TR ISTS"
    has any one faced this error, please suggest the corrective action to be taken,

    hi all,
    I'm now getting the same error when I try to activate a created "transfer rules" for any type of DataSource of my cProject.
    "Transfer structure 0DPR_***********_DA does not exist
    Message no. RSAR440"
    please show me on step by step because I'm a new guy of this SAP.
    Thanks,
    Chuong Hoang
    R&D engineer of global cybersoft - vn

  • Transfer structure prefix error

    Hi all,
       When i active the transfer structure of any infosource of Ecc5.0.,I got an error message 'Transfer structure prefix for source system T90CLNT090 is not defined'. The source system T90CLNT090 is the current client of bw system.Any one who met the problem before,or have some idea about this,appreciate for sharing your experience.
    best regard,
    Eric

    Hi Natovian,
    Thanks again for ur time replying me!
    I tried to follow what ever u said.. but still unsuccessful.
    The Following is the screen that appears after I used SE37--> RSAP_BIW_DISCONNECT:
    http://farm1.static.flickr.com/212/495977912_6f890cad34_o.jpg
    I tried to see the entries for SLOGSYS & RLOGSYS using the TCODE SE16, following is the RSBASIDOC table screen which appears as:
    http://farm1.static.flickr.com/208/495995911_2213885c8e_o.jpg
    From the above table(screen) which combination do I have to use as entries to the following Screen(Using SE37 RSAP_BIW_CONNECT) :
    http://farm1.static.flickr.com/226/495977908_9c0ee51f29_o.jpg
    D I have to enter an entry for the RFC target system:??
    <b>Note:</b> I am Using SAP ECC 5.0  IDES version; have 3 source systems defined
            <b>1.</b> Source system T90CLNT090 with clinet 800 ( through which I run rsa1 to move on to BW 3.5 Administrator Work Bench screen) .Its a Combined Client I guess!! But basically I enter into R/3 System first before I jusm onto BW screens
           <b> 2 nd</b> and <b>3rd</b> are the Flat File Source Systems(SS_DEMOFF & SS_ODSFLAT) which I created by my own. and My use ID is SAPUSER for 800 Client to enter SAP.
    Do I have to have a BW source System as well do make this work??
    I have selecetd and tried the folloowing entries from the RSBASIDOC table :
    http://farm1.static.flickr.com/191/495977906_e10a056721_o.jpg
    and in the result, it says that the logical system already exists.
    I even tried using the flat table combination but the follwing is the result screen:
    http://farm1.static.flickr.com/226/495977956_073272c7ab_o.jpg
    I tried my level best to actually let you know, whats really happenening with my issue.
    Hope u will have a clear picture of my problem.
    Awaiting for ur precioius reply!!
    Vamsi.
    I tried defining a BW source system but got stuck in the middle filling up those details.
    Thanks
    <u></u><u></u>

  • Transfer structure not active after runing RS_TRANSTRU_ACTIVATE_ALL

    Hi BW Experts,
    we are having a migration and just after migration we are finding the the transfer structure is not active. Hence in order to activate the same we ran <b>RS_TRANSTRU_ACTIVATE_ALL</b> program but still in the job log finding some problems like <b>0BP_RELTYPES_TEXT</b> is not available in source system. Kindly help in this regard since this is a critical issue and we are not able to run our daily loads because of this.
    Can any one also tell me if it is a migration problem?
    Thanks and have a nice day.
    Warm Regards,
    Akilesh

    Hi Sriram,
    This is the First time ur loading data from that system, If yes u need to do full extraction steps like transfer data source in RSA5 ..etc.
    After that u need to replicate those DS from their respective sources systems in BW.
    After doing those all actions, then u need to run the program 'RS_TRANSTRU_ACTIVATE_ALL'.
    If u have multiple TS to be activated from one source system ---> u can enter Source system name and put * in Info source column after executing the program, it will activate all transfer structures which are linked to that source system at a time.
    Hope this will help...if you have any plz reply.
    Thanks
    Raja Reddy.

  • Transfer Structure 2LIS_03_BX_QB does not exist

    Hi all,
    I got the following error message when transporting infosource 2LIS_03_BX.
    "Transfer Structure 2LIS_03_BX_QB does not exist"
    Maybe somebody can help me.
    Thanks and appreciate that,
    -Martin-

    hi Martin,
    try in dev rsa1->transport connection with infosource 2lis_03_bx as starting point, collection mode 'manual', grouping 'in dataflow before', and click 'source system assignment' (yellow box with x) and make sure r/3 source system is marked. then click execute. it will collect objects, after finish, make sure transfer rules, transf structure and datasource are marked following the infosource. create request and transport.

  • Transfer Structure activation

    Hi all
    I need to execute a specific Infopackage in the Quality System . However , When i try to open the infopackage it gives a message saying " transfer structure not yet active " . When I go to the Transfer structure and try to activate it , i get a message saying " Cross Client customising not allowed " .
    Can anyone please help me resolve this issue . I am pretty new to BIW .
    Thanks & Regards ,

    hi,
    you have to transport the transfer structure/rule from Dev system. your QA is set to not allowed changes.
    to transport, logon to Dev system, transaction rsa1 >> transport connection >> choose 'object types' in left frame then find 'infosource' in middle frame and expand, click 'select object' and entry your infosource where the trasnfer structure belongs to. make sure the source system is marked in 'source system assignment' (click yellow box with X), choose 'in dataflow before' for grouping and collection mode 'manual'. expand the infosource, make sure the transfer structure is there and marked. create request and transport.
    hope this helps.

  • Transfer Structure Error

    Hi Guys,
    I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.
    Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130
    Message no. R3104
    Diagnosis
    An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .
    System response
    The action was terminated. No data was changed.
    Procedure
    Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.
    I am using PSA as the transfer method. Any help is appreciated.
    Thanks.

    Hi Govind,
    To implement what is said in the note IS VERY EASY!
    I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.
    So, here is a way to implement the program.
    - In the text tabstrip of the note click on 'Correction Instructions' tabstrip.
    - Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).
    - Click on a report name 'z_rs_scrsystem_r3_check'.
    - In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.
    - Enter program description, choose 'executable' option.
    - Into the screen of ABAP Editor copy-paste the code from the note correction instructions.
    - Click on 'Check', then 'Activate' icons.
    - If everything is OK, press F8 (execute).
    Then follow the note:
    "These programs have the following input parameters:
    SLOGSYS Specify the logical system name of your source system here
    RLOGSYS Specify the logical system name of the BW system here
    If you enter nothing here, all existing BW source system connections are processed.
    Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.
    2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.
    3. If the error continues to occur:
    Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.
    After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.
    We recommend that you use the PSA transfer method."
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov

Maybe you are looking for