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.

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

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.

Transfer structure not active

Hi ,
in my process chain , it failed due to error: Transfer structure is not active.
How to correc this?
iam using BI 7.0
regards
sidartha

Hi Siddartha,
Try to activate the transfer structure using Pogram RS_TRANSTRU_ACTIVATE_ALL in SE 38. Give the Infosource & Source system name there & then execute.
Hope this will help.
~!Dpak

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 RS_TRANSTRU_ACTIVATE_ALL program but still in the job log finding some problems like 0BP_RELTYPES_TEXT 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 is not yet active" in each variant of a process chain

I run a big process chain in test environment that I had never run before, but find almost every variant of the process chain show the red error, when I right click the red color variant, get the msg at the status bar that says "Transfer structure is not yet active". Is there a way that can do the mass activation of all master data attributes?
Thanks

Hi I have the same error message
When I intend running the program to Activate Transfer Structures I get the following error messages
@5C\QError@     Activation not possible: Transfer structure contains invalid field LANGU
@5C\QError@     Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@     Activation not possible: Transfer structure contains invalid field NODENAME
@5C\QError@     Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@     Activation not possible: Transfer structure contains invalid field LANGU
@5C\QError@     Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
@5C\QError@     Transfer structure 0MATERIAL_HIER_AB1 NOT activated successfully Activate manually
Please Advise on how to fix it .

Activating Transfer Structure

Hello Experts,
While Activating transfer strucutre. Am getting the below error message for some XXX trnasfer structure -
Error while creating table 'EDISEGMENT' entry '/BIC/XXX
Message no. EA201
Diagnosis
An attempt was made to create the entry '/BIC/XXX' in table 'EDISEGMENT'. The attempt failed.
System Response
The operation was canceled.
Procedure
Please check whether the relevant entry already exists.
Can anyone please guide how to step into further
Warm Regards,
Aluri

Hi Aluri,
Try implementing the fixes and the recommendations in "Note 493422 - Inconsistent IDoc segments/transf. structures in srce system"
I think this is very relevant to your problem.
Good luck,
Ali

Error in transfer structure while activating the business content

Hi all
we got the following error while activating the transfer rules( business content) :
1)error when determining a number from object BI_TSDTEL and number 01
2) object name can only contain characters from syntactical character set.
3) data element for infoobject WAERS 0CURRENCY could not be created.
can anyone please explain what is this error.

Hello Tilak,
Goto SE37 -> RSAR_TRANSTRUCTURE_ACTIVATE -> Transfer Structure Name -> Execute
If the above doesn't fix then try the below
Goto SE14 -> Transfer Structure Name -> Adjust and activate .
This will fix if there is any inconsistency in the transfer structure.
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/]

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 while activating transfer structure and communication structure.

Hi all,
I am getting an error while activating the transfer structure, I have the same datasource comming from a 2nd instance of R/3 and its working fine with the 2nd source.
I mean same datasource comming from two R/3 instances and connecting to one infosource.
Maximum length of segment is 1000 characters, current length is 2567
Please let me know.
thanks,
Sabrina.

Hi Sabrina...
there is an OSS Note (120446) related to your problem, but it seems related to a very old release (what's yours ?)
Anyway, it suggests:
"the transfer method in the transfer rules must be set to TRFC with ODS"
Hope it helps!
Bye,
Roberto

Transfer Structure not Activated

Table /BIC/B0000879000 must be created in the database
I am getting this error when i try to activate the transfer structure for 0material infosource. everything was fine before i tried to restore the R/3 Source Connection from RSA1 and right click on Source system and select Restore.
Its not activating any Transfer Structure now......Says table must be created....Though it should activate itself.....
I checked it in the ABAP Dictionary .. the table is not there at all....
Somebody please help me...

always the Activate the Source system connection after the Restore...
Once thats done.. then try replicating the DS and activate the TS.. and then proceed with the loads..
Let me know if u get the issue again?
thanks
Vishnu

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 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)
Transfer structure 80MATERIALM_CB activated under the name 80MATERIALM_CA
It is not necessary to copy dependent objects for transfer structure 80MATERIALM_CA
Object 80MATERIALM object version not found in table
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 ...
 Object 80MATERIALM object version not found in table
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 Could not be Collected

I am trying to activate some Business Content (CO-OM-CCA Costs & Allocations).
In the Select Object Popup, after selecting the required object and I am pressing the Transfer Selection. Now I am getting the errors as below
1) Object 0VALUATION_TEXT D6B100PCC (Transfer Structure,ISTS) could not be collected for object 0VALUATION_TEXT D6B100PCC (Transfer Rules,ISMP)
2) Object '0VALUATION_TEXT D6B100PCC' (ISTS) of type 'Transfer Structure' is not available in version 'D'
Message no. RSO252
This error is coming even I try to activate some DEMO Content (CO-PA Demo Cube).
I am Grouping the objects with the Option In Dataflow Before and Afterwards with Collection Mode as Collect Automatically
I am following the SAP Best Practices - BW Scenario
https://media.sdn.sap.com/html/submitted_docs/Best_Practices/BW/html/index.htm
Your help will be appreciated

Hi Nathan,
Make sure the objects are active. If so, then goto the infosource -> Extras (from menu) -> Object directory.. -> Transfer rules -> assign the package and it would ask for transfer structure later so assign the package to that as well.
Bye
Dinesh

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:??
Note: I am Using SAP ECC 5.0 IDES version; have 3 source systems defined
 1. 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
 2 nd and 3rd 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

Transfer Structure activation

Similar Messages

Maybe you are looking for