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

Similar Messages

  • Error when activate transfer structure

    Dear Experts
    I Have problem with transfer structure activation with start routine
    If I check the start routine it's ok, no error
    but if i activate transfer routine, there is an error bellow:
    Syntax error "' '" and "TRAN_STRUCTURE" are not comparable in U in row 627 position 2
    Message no. RSAA350
    Diagnosis
    A syntax error occurred.
    System Response
    Error message "' '" and "TRAN_STRUCTURE" are not comparable in U in line 627
    Procedure
    Repair your routine.
    but if i delete transfer routine, activation it's ok, there is no error
    how to activation transfer structure with start routine ?
    really appreciate your help
    Best Regards
    Jeiming

    hi Sale
    Thanks for your reply
    how to check if any short dump during activation ?
    the start routine only have 547 rows
    these are the start routine :
    PROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
    Declaration of transfer structure (selected fields only)
    TYPES: BEGIN OF TRANSFER_STRUCTURE ,
      Record number to be filled in case of adding row(s)
      to enable 'error handling'
        record      TYPE rsarecord,
      InfoObject ZGECRE: DATS - 000008
        ZGECRE TYPE D,
      InfoObject ZSALESORG: CHAR - 000004
        ZSALESORG(000004) TYPE C,
      InfoObject ZBILLNUM: CHAR - 000010
        ZBILL_NUM(000010) TYPE C,
      InfoObject 0BILL_ITEM: NUMC - 000006
        ZBILL_ITEM(000006) TYPE N,
      InfoObject 0CREATEDON: DATS - 000008
        ZCREATEDON TYPE D,
      InfoObject 0CALDAY: DATS - 000008
        ZBILL_DATE TYPE D,
      InfoObject 0ACT_GI_DTE: DATS - 000008
        ZACT_GI_DTE TYPE D,
      InfoObject ZCOMMAMT: CURR - 000017
        ZCOMMAMT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZAPPIT: CHAR - 000004
        ZAPPIT(000004) TYPE C,
      InfoObject ZGSM: DEC - 000017
        ZBASISWGT TYPE P,
      InfoObject ZBL_DATE: DATS - 000008
        ZBL_DATE TYPE D,
      InfoObject ZBILLPR: CURR - 000017
        ZBILLPR(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBILLPRTO: CURR - 000017
        ZBILLPRTON(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBILL_TO: CHAR - 000010
        ZBILL_TO(000010) TYPE C,
      InfoObject ZBP_MT: CURR - 000017
        ZBP_MT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBP_UN: CURR - 000017
        ZBP_UN(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBRAND: CHAR - 000030
        ZBRAND(000030) TYPE C,
      InfoObject ZCOLOR: CHAR - 000030
        ZCOLOR(000030) TYPE C,
      InfoObject ZCOMPANY: CHAR - 000004
        ZCOMPANY(000004) TYPE C,
      InfoObject 0COST: CURR - 000017
        ZCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOST_LOC: CURR - 000017
        ZCOST_LOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOST_USD: CURR - 000017
        ZCOST_USD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject 0DOC_CURRCY: CUKY - 000005
        ZDOC_CURRCY(000005) TYPE C,
      InfoObject  : CUKY - 000005
        ZGRPCURR(000005) TYPE C,
      InfoObject 0CUST_GROUP: CHAR - 000020
        ZCUST_GROUP(000020) TYPE C,
      InfoObject ZREQ_DATE: DATS - 000008
        ZREQ_DATE TYPE D,
      InfoObject ZDOC2USD: FLTP - 000016
        ZDOC2USD TYPE F,
      InfoObject ZFIN_CHG: CURR - 000017
        ZFIN_CHG(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFOB_UN: CURR - 000017
        ZFOB_UN(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFRACT: CURR - 000017
        ZFRACT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFRACTLOC: CURR - 000017
        ZFRACLOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFRACTUSD: CURR - 000017
        ZFRACUSD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFR_COST: CURR - 000017
        ZFR_COST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFR_LOC: CURR - 000017
        ZFR_LOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFR_USD: CURR - 000017
        ZFR_USD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject 0INCOTERMS: CHAR - 000003
        ZINCOTERMS(000003) TYPE C,
      InfoObject ZGRAIN: CHAR - 000001
        ZGRAIN(000001) TYPE C,
      InfoObject 0LOC_CURRCY: CUKY - 000005
        ZLOC_CURRCY(000005) TYPE C,
      InfoObject ZMFCMILL: CHAR - 000010
        ZMFCMILL(000010) TYPE C,
      InfoObject ZMTCLASS: CHAR - 000018
        ZMTCLASS(000018) TYPE C,
      InfoObject ZMATERIAL: CHAR - 000030
        ZMATERIAL(000030) TYPE C,
      InfoObject ZMILL: CHAR - 000004
        ZMILL(000004) TYPE C,
      InfoObject ZNFOB_UN: CURR - 000017
        ZNFOB_UN(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZFOBV: CURR - 000017
        ZFOBV(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZNFOBV: CURR - 000017
        ZNFOBV(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject 0NET_WGT_DL: QUAN - 000017
        ZNET_WGT_DL(000009) TYPE P
                                            DECIMALS 000003,
      InfoObject ZNWDLKG: QUAN - 000017
        ZNWDLKG(000009) TYPE P
                                            DECIMALS 000003,
      InfoObject  : UNIT - 000003
        ZUNIT_KG(000003) TYPE C,
      InfoObject ZNO_INV: CHAR - 000001
        ZNO_INV(000001) TYPE C,
      InfoObject ZDOC_DATE: DATS - 000008
        ZDOC_DATE TYPE D,
      InfoObject 0INV_QTY: QUAN - 000017
        ZINV_QTY(000009) TYPE P
                                            DECIMALS 000003,
      InfoObject ZPMNTTRMS: CHAR - 000004
        ZPMNTTRMS(000004) TYPE C,
      InfoObject ZPO_DATE: DATS - 000008
        ZPO_DATE TYPE D,
      InfoObject ZPO_NO: CHAR - 000020
        ZPO_NO(000020) TYPE C,
      InfoObject ZPRTDISCH: CHAR - 000040
        ZPRTDISCH(000040) TYPE C,
      InfoObject ZPRT_LOAD: CHAR - 000040
        ZPRT_LOAD(000040) TYPE C,
      InfoObject 0COND_UNIT: CHAR - 000002
        ZCOND_UNIT(000002) TYPE C,
      InfoObject ZPRODFORM: CHAR - 000002
        ZPRODFORM(000002) TYPE C,
      InfoObject 0SALES_DIST: CHAR - 000006
        ZSALES_DIST(000006) TYPE C,
      InfoObject 0DOC_NUMBER: CHAR - 000010
        ZDOC_NUMBER(000010) TYPE C,
      InfoObject 0S_ORD_ITEM: NUMC - 000006
        ZS_ORD_ITEM(000006) TYPE N,
      InfoObject ZSLSEMPLY: CHAR - 000010
        ZSALESEMPLY(000010) TYPE C,
      InfoObject 0SALES_GRP: CHAR - 000003
        ZSALES_GRP(000003) TYPE C,
      InfoObject 0SALES_OFF: CHAR - 000004
        ZSALES_OFF(000004) TYPE C,
      InfoObject  : CHAR - 000020
        ZSALESTYP(000020) TYPE C,
      InfoObject 0SALES_UNIT: UNIT - 000003
        ZSALES_UNIT(000003) TYPE C,
      InfoObject 0NETVAL_INV: CURR - 000017
        ZNETVAL_INV(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZNVI_LOC: CURR - 000017
        ZNVI_LOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZNVI_USD: CURR - 000017
        ZNVI_USD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSELVIDOC: CURR - 000017
        ZSELVIDOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSELVILOC: CURR - 000017
        ZSELVILOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSELVIUSD: CURR - 000017
        ZSELVIUSD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSELLPRTO: CURR - 000017
        ZSELLPRTO(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSDTGRP: CHAR - 000001
        ZSDTGRP(000001) TYPE C,
      InfoObject ZSELLPR: CURR - 000017
        ZSELLPR(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSELV1USD: CURR - 000017
        ZSELVI1US(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSHIP_TO: CHAR - 000010
        ZSHIP_TO(000010) TYPE C,
      InfoObject ZSHPCOND: CHAR - 000002
        ZSHPCOND(000002) TYPE C,
      InfoObject ZSIZE: CHAR - 000030
        ZSIZE(000030) TYPE C,
      InfoObject ZSOLD_TO: CHAR - 000010
        ZSOLD_TO(000010) TYPE C,
      InfoObject ZLASTCHG: DATS - 000008
        ZSSCHG TYPE D,
      InfoObject 0TAX_AMOUNT: CURR - 000017
        ZTAX_AMOUNT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZDISCAMT: CURR - 000017
        ZDISCAMT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject 0GRS_WGT_DL: QUAN - 000017
        ZGRS_WGT_DL(000009) TYPE P
                                            DECIMALS 000003,
      InfoObject ZTRADING: CHAR - 000010
        ZTRADING(000010) TYPE C,
      InfoObject ZTT_AMT: CURR - 000017
        ZTT_AMT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject 0UNIT_OF_WT: UNIT - 000003
        ZUNIT_OF_WT(000003) TYPE C,
      InfoObject 0DELIV_NUMB: CHAR - 000010
        ZDEL_NUMBER(000010) TYPE C,
      InfoObject ZQLTYGR: CHAR - 000001
        ZQLTYGR(000001) TYPE C,
      InfoObject ZORDCRDT: DATS - 000008
        ZORDCRDT TYPE D,
      InfoObject ZDSTCTRY: CHAR - 000003
        ZDESTCTRY(000003) TYPE C,
      InfoObject ZSLSAGNT1: CHAR - 000010
        ZSLSAGNT1(000010) TYPE C,
      InfoObject ZSLSAGNT2: CHAR - 000010
        ZSLSAGNT2(000010) TYPE C,
      InfoObject ZBILLTYPE: CHAR - 000004
        ZBILL_TYPE(000004) TYPE C,
      InfoObject ZCCLDOCNO: CHAR - 000010
        ZCCLDOCNO(000010) TYPE C,
      InfoObject ZCRTBY: CHAR - 000012
        ZCRTBY(000012) TYPE C,
      InfoObject ZDOC_TYPE: CHAR - 000004
        ZDOC_TYPE(000004) TYPE C,
      InfoObject ZMTGROUP: CHAR - 000009
        ZMTGROUP(000009) TYPE C,
      InfoObject ZPAYER: CHAR - 000010
        ZPAYER(000010) TYPE C,
      InfoObject ZPLANT2: CHAR - 000004
        ZPLANT(000004) TYPE C,
      InfoObject ZCCLFLAG: CHAR - 000001
        ZCCLFLAG(000001) TYPE C,
      InfoObject ZLOADDATE: DATS - 000008
        ZLOADDT TYPE D,
      InfoObject ZBATCHNO: CHAR - 000010
        ZBATCHNO(000010) TYPE C,
      InfoObject ZBPO_UN: CURR - 000017
        ZBPO_UN(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBP_LOC: CURR - 000017
        ZBP_LOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBP_USD: CURR - 000017
        ZBP_USD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBP_VAL: CURR - 000017
        ZBP_VAL(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZDISTCHAN: CHAR - 000002
        ZDISTCHA(000002) TYPE C,
      InfoObject ZHGLVIB: NUMC - 000006
        ZHGLVIB(000006) TYPE N,
      InfoObject ZINACT: CURR - 000017
        ZINACT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZINACTLOC: CURR - 000017
        ZINACTLOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZINACTUSD: CURR - 000017
        ZINACTUSD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZMACHID: CHAR - 000001
        ZMACHID(000001) TYPE C,
      InfoObject ZORDRLDT: DATS - 000008
        ZORDRLDT TYPE D,
      InfoObject ZDELCRDT: DATS - 000008
        ZDELCRDT TYPE D,
      InfoObject ZNEGODATE: DATS - 000008
        ZNEGODATE TYPE D,
      InfoObject ZPPLPRDT: DATS - 000008
        ZPPLPRDT TYPE D,
      InfoObject ZDELITM: NUMC - 000006
        ZS_DEL_ITEM(000006) TYPE N,
      InfoObject ZCONTPRSN: CHAR - 000010
        ZCONTPRS(000010) TYPE C,
      InfoObject ZENDCUST: CHAR - 000010
        ZENDCUST(000010) TYPE C,
      InfoObject ZDELVDT: DATS - 000008
        ZDELVDT TYPE D,
      InfoObject ZANFOB: CURR - 000017
        ZANFOB(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZINVNDOC: CURR - 000017
        ZNETWR(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZINVNLOC: CURR - 000017
        ZNETWRLOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZINVNUSD: CURR - 000017
        ZNETWRUSD(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZADUTDOC: CURR - 000017
        ZADUTDOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZSINTDOC: CURR - 000017
        ZSINTDOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZREPOFF2: CHAR - 000010
        ZREPOFF(000010) TYPE C,
      InfoObject ZMKTSFDOC: CURR - 000017
        ZMKTSFDOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZHRSLSEMP: CHAR - 000010
        ZHRSLSEMP(000010) TYPE C,
      InfoObject ZBOCMDOC: CURR - 000017
        ZBOCMDOC(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZTRDPART2: CHAR - 000010
        ZTRDPART(000010) TYPE C,
      InfoObject ZFORWAGT: CHAR - 000010
        ZFORWAGT(000010) TYPE C,
      InfoObject ZCARRNAM: CHAR - 000010
        ZCARRNAM(000010) TYPE C,
      InfoObject ZACTSHPDT: CHAR - 000010
        ZACTSHPDT(000010) TYPE C,
      InfoObject ZTKNUM: CHAR - 000010
        ZTKNUM(000010) TYPE C,
      InfoObject ZFKNUM: CHAR - 000010
        ZFKNUM(000010) TYPE C,
      InfoObject ZCOFRCUS: CURR - 000017
        ZCOFRCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOBLCUS: CURR - 000017
        ZCOBLCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOTHCUS: CURR - 000017
        ZCOTHCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOWRSKUS: CURR - 000017
        ZCOWARSK(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOPEAKUS: CURR - 000017
        ZCOPEAK(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCODDUUS: CURR - 000017
        ZCODDU(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCOOTHUS: CURR - 000017
        ZCOOTH(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCITRCKLC: CURR - 000017
        ZCITRUCK(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCIHNDLLC: CURR - 000017
        ZCIHANDL(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCICOOLLC: CURR - 000017
        ZCICOOLGL(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCISTVDLC: CURR - 000017
        ZCISTVDOR(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCICRGOLC: CURR - 000017
        ZCICARGO(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCIWRFGLC: CURR - 000017
        ZCIWHARFG(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCIFMGTLC: CURR - 000017
        ZCIFUMIGT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZCIOTHLC: CURR - 000017
        ZCIOTH(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOFRCUS: CURR - 000017
        ZBOFRCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOBLCUS: CURR - 000017
        ZBOBLCOST(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOHNDLUS: CURR - 000017
        ZBOHANDL(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOSTRGUS: CURR - 000017
        ZBOSTORG(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOTRSHUS: CURR - 000017
        ZBOTRNSH(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBODDUUS: CURR - 000017
        ZBODDU(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBOOTHUS: CURR - 000017
        ZBOOTH(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBITRCKLC: CURR - 000017
        ZBITRUCK(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBIHNDLLC: CURR - 000017
        ZBIHANDL(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBIDFEELC: CURR - 000017
        ZBIDOCFEE(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBISTVDLC: CURR - 000017
        ZBISTVDOR(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBICRGOLC: CURR - 000017
        ZBICARGO(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBIWRFGLC: CURR - 000017
        ZBIWHARFG(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBISTRGLC: CURR - 000017
        ZBISTORG(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBIFMGTLC: CURR - 000017
        ZBIFUMIGT(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZBIOTHLC: CURR - 000017
        ZBIOTH(000009) TYPE P
                                            DECIMALS 000002,
      InfoObject ZLFDAT: DATS - 000008
        ZLFDAT TYPE D,
      InfoObject ZDELAYRS: CHAR - 000004
        ZDELAYRS(000004) TYPE C,
      InfoObject ZCLEARDT: DATS - 000008
        ZCLEAR_DATE TYPE D,
      InfoObject ZINV_DUE: DATS - 000008
        ZINV_DUE TYPE D,
      InfoObject ZBRSLSPR: CHAR - 000010
        ZBRSLSPR(000010) TYPE C,
      InfoObject ZMLSLSSP: CHAR - 000010
        ZMILSLSSP(000010) TYPE C,
      InfoObject  : CHAR - 000006
        ZDISPID(000006) TYPE C,
      InfoObject  : CHAR - 000006
        ZLOAPID(000006) TYPE C,
      InfoObject ZOITMFRS: DEC - 000001
        ZOITMFRS TYPE P,
      InfoObject ZOEACCS: DEC - 000001
        ZOEACCS TYPE P,
      InfoObject ZINVACCS: DEC - 000001
        ZINVACCS TYPE P,
      InfoObject ZBILPSTS: DEC - 000001
        ZBILPSTS TYPE P,
      InfoObject ZDOCPROS: DEC - 000001
        ZDOCPROS TYPE P,
      InfoObject ZCNTORD: NUMC - 000001
        ZCNTORD(000001) TYPE N,
      InfoObject ZCNTORDI: DEC - 000001
        ZCNTORDI TYPE P,
      InfoObject ZTRDPART: CHAR - 000003
        ZSOURCE(000003) TYPE C,
      InfoObject ZATA: DATS - 000008
        ZATA TYPE D,
      InfoObject ZRRD: DATS - 000008
        ZRRD TYPE D,
      InfoObject ZRAD: DATS - 000008
        ZRAD TYPE D,
      InfoObject ZCUOBJ: NUMC - 000018
        ZCUOBJ(000018) TYPE N,
      InfoObject ZIDR2USD: FLTP - 000016
        ZIDR2USD TYPE F,
      InfoObject ZPRCDAT: DATS - 000008
        ZEXCRDAT TYPE D,
      InfoObject ZNEGOTYP: CHAR - 000003
        ZNEGOTYP(000003) TYPE C,
      InfoObject ZDLYNRSN: CHAR - 000004
        ZDLYNRSN(000004) TYPE C,
      InfoObject ZADLYNRS: CHAR - 000070
        ZADLYNRS(000070) TYPE C,
      InfoObject ZDOCCRDT: DATS - 000008
        ZDOCCRDT TYPE D,
      InfoObject ZBLEDDDT: DATS - 000008
        ZBLEDDDT TYPE D,
      InfoObject ZDOCSDDT: DATS - 000008
        ZDOCSDDT TYPE D,
      InfoObject ZPAIDDOC: CURR - 000017
        ZPAIDAMT(000009) TYPE P
                                            DECIMALS 000002,
    END OF TRANSFER_STRUCTURE .
    Declaration of Datapackage
    TYPES: TAB_TRANSTRU type table of TRANSFER_STRUCTURE.
    Global code used by conversion rules
    $$ begin of global - insert your declaration only below this line  -
    TABLES: /bic/pzmtclass, /bic/azods_sr00,
            /bic/pzsalesorg, /bic/pzbilltype,
            /bic/pzdoc_type, /bic/pzpmnttrms,
            /bic/pzplant2,
            t006.
    data : begin of IT_VC occurs 0,
              ZSALESORG LIKE /BIC/AZODS_SO00-/BIC/ZSALESORG,
              ZDOC_NUMB LIKE /BIC/AZODS_SO00-DOC_NUMBER,
              ZDOC_ITEM LIKE /BIC/AZODS_SO00-S_ORD_ITEM,
              ZCUOBJ    LIKE /BIC/AZODS_SO00-/BIC/ZCUOBJ,
              ZATNAM    LIKE /BIC/AZODS_VC00-/BIC/ZATNAM,
              ZATWRT    LIKE /BIC/AZODS_VC00-/BIC/ZATWRT,
           end of IT_VC.
    DATA:   D like SY-DATUM,
            l_calmonth(7) type C,
            F_V1(16) type P decimals 3,
            F_V2(16) type P decimals 3,
            F_V3(16) type P decimals 3,
            F_TMP(16) type P decimals 3,
            f_tmp2(16) type p decimals 2,
            slsorg(10) value '0000000000',
            uomtmp like t006-MSEHI,
            ag_bill like /bic/pzcustomer-accnt_grp,
            ag_ship like /bic/pzcustomer-accnt_grp,
            shell like /bic/pzcustomer-/bic/zshell,
            zflg1 like /bic/pzcustomer-/bic/zflag1,
            mtltype like /bic/pzmtclass-matl_type,
            mtlclass like /bic/pzmtclass-/bic/zmtclass,
            mtlgroup like /bic/pzmtgroup-/bic/ZMTGROUP,
            org1 like /bic/pzsalesorg-/bic/zslsorg_1,
            vmillalc like /bic/pzsalesorg-/bic/zmillalc,
            gecre like /bic/azods_sr00-/bic/zgecre,
            mtgrptmp(9) value '000000000',
            vmfcmill like /bic/pzmaterial-/bic/zmfcmill,
            vsalesorg like /bic/pzplant2-/bic/zsalesorg,
            vtmp type I.
    $$ end of global - insert your declaration only before this line   -
    FORM STARTROUTINE
      USING    G_S_MINFO TYPE RSSM_S_MINFO
      CHANGING DATAPAK type TAB_TRANSTRU
               G_T_ERRORLOG TYPE rssm_t_errorlog_int
               ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
    $$ begin of routine - insert your code only below this line        -
    DATA: l_s_datapak_line type TRANSFER_STRUCTURE,
          l_s_errorlog TYPE rssm_s_errorlog_int.
    abort <> 0 means skip whole data package !!!
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.

  • Error when trying to activate transfer structure

    Dear experts
    I got this error when activating the Transfer Structure in the Data Souce:
       Table is not yet classified                                            
       Field /BIC/ZPRCH026 is too long (Specify a length between 1 and 255)   
       Flag: 'incorrect extension category' cannot be updated                 
       Table /BIC/B0002707000 was not activated                               
    FYI, the lenght of the info Object /BIC/ZPRCH026 is 1000, as per other similar DataSource.
    What should I do to remove this error?
    Your help is greatly appreciated

    Hi
    I thought i have managed to reactivate the transfer structure. This was how i did it:
    1. I went to SE11 and opened table structure /BIC/B0002707000 as per the error
    2. I changed the character limit of ZPRCH026 to 255
    3. I reactivated the table.
    Then, I went to rsa1 to see the DataSource (which contains the Transfer Structure) and see that it is now activated.
    I proceeded to create an Info Package under the DataSource, because I need to initialiase a delta queue.
    Here are my config (in the info package):
    1. In Update tab, I selected "Initialixe Delta Process" and check "Initialize without data transfer"
    2. I select "Always update data, even if no master data exists for a characteristic"
    3. In Schedule tab, I started the load immediately ("Start Data Load Immediately")
    But then I got a message "No Transfer Structure Available D09_010 6AZPR034 (SY-SUBRC=5)"
    FYI, D09_010 is the source system, 6AZPR034 should be the data source.
    Could anyone advise me what went wrong?
    Your kind help is highly appreciated
    Many thanks
    Wan

  • Unable to activate Transfer Rule

    Hello Experts,
    I am not able to activate Transfer Rule in my System ( BW 3.0).
    I have written one routine and then when I am trying to activate I am getting below error messageu201D
    Object 0NOTIFICATN_ATTR object version not found in table.
    My Data Source name is 0NOTIFICATN_ATTR.
    I have also tried to activate by using   RS_TRANSTRU_ACTIVATE_ALL but still no luck.
    I also checked table TADIR and I can see entry over there.
    Regards,
    Pankaj Naik.

    Hi Pankaj,
    Try to activate the transfer rules by executing the SE38 report  - RS_TRANSTRU_ACTIVATE_ALL.
      Also check the note - 884385 , For 'RSAR' errors while activating update and transfer rules.
    Regards,
    Lokesh

  • Unable to Activate iPhone 5s for Sprint in store pick up

    I was one of the lucky few who preordered the iPhone 5S at BestBuy.com, but when I came in to the store to pick it up, the employees were unable to activate the phone. Sprint had a notice posted on the Best Buy register about an issue with invalid IMEI numbers and that the problem was being fixed ASAP. Hours have passed and I haven't been able to find out anything new. I had to leave my phone at the Best Buy and was told to try back later.
    Does anyone know if the issue has been fixed yet?

        Hello willreinking! I am sorry to hear that you're having issues getting your phone activated. The first thing to do is to make sure that the SIM card number has been updated on your account, so your device is able to program. You can update it on My Verizon. http://bit.ly/xB4iTc  If it's correct, the next step is to remove/reinsert the SIM card to start the activation again. Please let us know if this continues, so we can get it fixed for you.
    Thank you,
    MichelleH_VZW
    Follow us on Twitter @VZWSupport

  • Unable to activate deletion flag for production order

    Hi Experts,
    I have created production order with reference to sales order. Now status of production order is REL PRC CSER GMPS MACM RESA SETC.
    I have already done goods issue & Goods receipt for this order and reversed the same all GI & GR.
    Now balance on order is also zero.
    My query is that I trying to activate deletion flag for this order but I found option of Activate is disable.
    Pls help.
    Regards,
    Rajesh

    Hello
    Probably, this is an assembly order. The deletion flag cannot be set manually for static assembly orders.
    A production order is recognized by the system as an assembly order because of the internal system I0170 on table JEST. Whenever this status is set for the order, the deletion flag can't be removed from the order on transaction CO02.
    See question 8 of the FAQ note 540834:
    8.  Question:
        When are the deletion flags for assembly orders set?
        Answer:
        You cannot manually set the deletion flag for static assembly
        orders. Instead, the system automatically sets the deletion flag
        when the corresponding sales order item:
        o  is completed (only for static assembly orders),
        o  is canceled,
        o  or is deleted.
        The deletion flag for assembly orders with dynamic assembly is set
        automatically if the corresponding sales order item:
        o  is canceled,
        o  or is deleted.
        You can set the deletion flag manually using the archiving PP_ORDER
        and, as of Note 1628094, using the transaction for changing the
        order.
    BR
    Caetano

  • Error while activating transfer structure for 0MATERIAL_ATTR

    I am trying to activate the transfer rules of 0MATERIAL_ATTR, but when activating the process end with the following message:
    Error generating program
    Message no. RSAR245
    Diagnosis
    An error occurred in the program generation:
    Program / Template:   RSTMPL80
    Error code / Action: 6
    Row:        1,792
    Message:    The data object "P_S_COMM" has no component called
    I cannot activate the transfer rules of 0MATERIAL_ATTR and 0MATERIAL_TEXT because of the same problem. Could anyone please help me...
    Thanks in advance for your valuable help.
    Regards
    Carlos España.

    Ron Silberstein:
    I really appreciate your help, thank you very much.
    I saw your profile, and i saw that you are an expert in BI.
    Congratulations, your help was very important for me.
    CONTINUE HELPING OTHER PEOPLE!!!!! T H A N K S!!
    God Bless you.
    Regards
    Carlos España.

  • Field in Append Structure for Generic Datasource

    Hi:
    I created a Generic Datasource based on a view. After that, I created an Append to the Extraction Structure to include a field not originally on the view (and not related to any table in the view) to be calculated using customer exit in CMOD.
    At the moment of activating the Datasource, this new field doesn't appear in the selection window but in RSA6 it shows there with options "Hide Field" and "Field only Known in Customer Exit" checked.
    Again, I try to edit the Datasource but this field is not in the list to change those two checks.
    Any idea?
    Thanks.
    Luis Sales

    Dear Luis Sales,
    I was having the same requirement. I tried it hard for removing the tick mark on the HIDE option. But it was not working at all.
    I tried these steps.
    1. From RSO2 went to Extract structure. Edit Mode-> append structure.
    2. Appended required fields and activated both append structure and extract structure.
    3. Back to datasource and Save it.
    4. Came out of transaction RSO2. ( latter Logged of system )
    5. after re login - RSA6 selected given Datasource and change. there I could change the selection of HIDE field. ( Even earlier I was not able to do that)
    May be these steps help you out.

  • Transfer Checkbox for 2LIS_02_ITM datasource

    Hi Experts,
    On enhancing 2LIS_02_ITM with 2 Z-fields and replicating to BI side, the transfer checkbox (5th column on fields tab of datasource display) in datasource is not enabled for these 2 fields and hence these fields are not available to be mapped to infosource.
    Any ideas as to how to enable the checkbox.?
    rgds
    Deepak

    Hi.
      Please use RSA6 to edit the datasource 2lis_02_scl and uncheck those 2 fileds you added in.
    Best Regards
    Martin Xie

  • 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

  • Not possible to edit Comm. Structure or Activate transfer rule

    Hello Experts,
    Do you know what is causing the problem in development box we facing? We are neither able to edit Comm. Structure nor activate transfer rule for myself data mast data sources in BW. Basically, it doesn't let us go in edit mode when we open communication/transfer rule screen on workbench (RSA1). This should be something basic problem but I can not think of anything now? Do you have any suggest about what to check?
    Thanks,
    Nimesh

    I agree, Raj.
    Details of what I have repeated (multiple times so far) in system:
    Regenerated data source from ODS. Replicated data source to info source and then activated by program Teja suggested (that's where I am having trouble because I can not go to edit mode within transfer structure details screen). I tried loading data with init. request from ODS to Cube and failed with time stamp error of data source.
    Issue is still unresolve?
    Nimesh

  • Activate Transfer Rules

    BW Experts,
    I am trying to activate transfer rules for 0MAT_PLANT. I get an error saying "Error while activating DDIC "
    The diagnosis says the following
    <b>/BIC/CABK0MAT_PLANT_ATTR-LOSFX (combination reference table/field /BIC/CABK0MAT_PLANT_ATTR-WAERS does not exist)
    Message no. AD855
    Diagnosis
    The reference field specified for the field does not exist in the specified reference table.
    Procedure
    Check the reference field and reference table for this field in the single field maintenance of the corresponding table.</b>
    Any Idea what has to be done. Help is appreciated.
    Thanks
    Ashwin

    hi Aswhin,
    0mat_plant_attr is business content datasource, seems this should not happen, if the waers not exist then the datasource should can be activated, perhaps metadata inconsistency (ddic error), try to replicate datasource again from bw.
    or do you add fields (no access to system to cross check the datasource in r/3),
    as mentioned check in r/3 rsa6, datasource 0mat_plant_attr, double click the 'extract structure', check if losfx has waers, if no exist, and you have no enhancement, try to transfer again with rsa5. then replicate datasource again from bw and try activate transfer rules.
    hope this helps.

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

  • Error while activating Transfer Structure

    Hi Expert,
    we have upgraded BW3.1 to BI 7.0, we are getting error while activating transfer structure for 0mat_sales_attr and 0mat_sales_text.
    Error is Error while creating table 'EDISEGMENT' entry '/BIC/CIOD0MAT_SALES_TEXT'
    Message no. EA201
    Diagnosis
    An attempt was made to create the entry '/BIC/CIOD0MAT_SALES_ATTR' in table 'EDISEGMENT'. The attempt failed.
    System Response
    The operation was canceled.
    Procedure
    Please check whether the relevant entry already exists
    I have tried report RS_TRANSTRU_ACTIVATE_ALL also, but no success.
    I have checked table and entry is there. i have checked we31 for segment there also segment is existing.
    Regards,

    Hi Dubey,
    I am facing the same issue when i transport the datasource from DEV to QA.i applied the OSS Note 493422 ,But could not resolve the issue.Pls let me know the solution to fix  this.
    Thanks,
    Renu

  • Error "No extraction structure for event I3" running set up 2LIS_17_I3HDR

    Hi, Experts:
    I am trying to activate and run set up datasource for PM 2LIS_17_I3HDR, so that data can be extracted from R/3 into BW 3.5 system.
    In R/3 environment, we have 2 clients. client 200 for configurations but has no data, and client 230 has data but can not change configurations.
    I have done the following in client 200:
    - Activated datasources for for PM 2LIS_17_I3HDR in RSA5.  
    - Made selection in RSA6.
    - Activated extract structures and datasource for application 17 in LBWE and also ran job control. Now I can see the extract structures for application 17 are active in client 200 only, but inactive in client 230. I tried to turn then active in client 230 but got error "Client 230 has status not modifiable".
    - I assume I should run set up tables in client 230 because it is the client with data in tables? But when run set up in OLIIBW, I got the error "
       No extraction structure for event I3: Messages active
       Message no. MCEX106
       Diagnosis
       You called the setup for the extractor structures of application '17' (Plant Maintenance). However no extractor structure is active for event I3 (messgaes).
       System Response
       Data for event I3 is not transferred to the BW interface.
       Procedure
       First activate the desired extractor structures for application '17' using the Customizing Cockpit and then start the setup again."
    - I can not manually activate extract structures in client 230 because it is not modifiable. I tried moving transports, the path is not set up. I see extract structures for other applications like 11, 13 are active. So I guess there may be other ways to activate the extract structures in client 230.
    - I also tried to run set up in client 200, which has extract structures for 17 in active status. But got the same error as client 230.
    Would anyone please help me with what to do to fix this?
    Thanks,
    Jenny
    Edited by: Jenny Chen on Oct 29, 2009 6:38 AM

    Hi, thanks for the reply!
    Just update for what we did to solve this. Both clients are for development. Client 200 is only for configuration but no data. Client 230 has data but not modifiable. Usually, when we create a structure, table, program, or active anything in 200. We will see it in 230 right away without transports. But this is not the case for activating extract structure for datasource from Business Content. We end up having Basis guy manually activate the structure for us directly in client 230 with transaction LBWE. That worked.
    Thanks,
    Jenny

Maybe you are looking for

  • Viewable area is scrunched to the top while a blank no man's land covers 90% of the screen at teh bottom.

    The database I am trying to work work with shows up fine on teh computers at work. On my laptop at home with Firefox, there is a horizontal scroll bar about 90% of the way up that is immovable. I cannot grab the bar in any way shape or form to move i

  • HP 3650 deskjet will not print in Windows 7

    New pc w/ Windows 7. My HP deskjet 3650 will not print PDF, Quicken, Website selections, etc. HELP!

  • Enabling Single Item Recovery per databse

    Hello, I am trying to find a command that will set "Single Item Recovery" to be true for all mailboxes in a database. I know how to set it for a single mailbox but I can't seem to find the correct syntax to make it work for each mailbox in a particul

  • Update 4.1.2

    Is it my imagination or is GarageBand starting MUCH quicker after the 4.1.2 update? Seems like it took 15 seconds to start before, now, around 5 seconds! This is great.

  • Missing drivers PCI\VEN_1180--..please help

    Missing drivers PCI\VEN_1180--..Help!!!! After upgrading to Windows 8.1 from Vista: I am missing the following drivers for Base System Device here is the information for the driver. I am unable to use my Built in Camera, CD/ROM Drive, System speakers