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.
Similar Messages
-
Error when creating Transfer structures
Dear Gurus,
I get the following error when creating the transfer structure.
<b>Error when creating transfer structure /BIC/CCBD1CL_OMAT002 in source system ERPCLNT400</b>
Message no. R3104
<b>Diagnosis</b>An error occurred when creating transfer structure /BIC/CCBD1CL_OMAT002 as an IDoc segment in source system ERPCLNT400 .
<b>System Response</b>
The action was terminated. No data was changed.
<b>Procedure</b>
Use the generation log in source system ERPCLNT400 to identify the error, and remove the cause.hi,
Refer OSS Note 147195 --- Error activating the transfer rules
Check the transfer mehtod is PSA ? and Activate Source Sys Conn again
Replicate the DS again and Activate TR (...'also check are there inconsistencies in transfer str) -
Error when creating transfer structure
I am trying to activate a custom Datasource, but get the below error
"An error occurred when creating transfer structure /BIC/CCNAZREPAYMENTS as an IDoc segment in source system"
Message no. R3104Hi
This is the problem. when in try to activate the 7.x Datasource or migratefrom 3.x to 7.x i getthe this error
"An error occurred when creating transfer structure /BIC/CCNAZREPAYMENTS as an IDoc segment in source system"
I need it as a 7.x datasource.
If I replicate as RSDS it comes into BW inactive as soon as I activate I get the above error. -
Error when creating transfer structure in source system
We have just had a copy of the ERP production system done and connected it to our existing QA system (done by our service providers) for a test go-live of our ERP upgrade.
Now I cannot activate the transfer rules as the transfer structure cannot be created in the source system.
I have checked the settings in table RSBASIDOC and they look okay, I can only assume that our wonderful basis people have done everything they should have but cannot be sure they've done it all correctly.
The sourcesystem is active, the RFC's are fine.
And help for a desperate man please. I've got to get this working in 1 day as basis need the system back to do an Oracle upgrade.Hi Jonathan,
Try to replicate the DS once again and the run the program RS_TRANSTRU_ACTIVATE_ALL to activate your transfer structure. Hope it helps.
Thanks and Regards
Subray Hegde -
Error when activate standard structure
Hi guru,
i've a serious problem about the activation of a standard structure,the check (for error) pass without problem, but when I want to activate it there is this exception :
CALL SCREEN (not modal) in modal dialog box not allowed
Anybody can help me ?
Thanks.
Angelo.
Edited by: Angelo Abbasci on Jan 13, 2009 2:52 PMHI,
I try but cant do much as it is a standard structure..
You could try to change the structure save it. The n execute the transaction again and try to activate..
You added the field with Access Key or through Append structure..?
If you get the error again then try and copy paste the error report important parts.. -
Error when activate transfer rule 0DISTR_CHAN
Hi dear all,
I''ve a quesiton urgent, plz.
I've activated IO 0DISTR_CHAN, so his flow before and after. I went to load master data, but I found his transfer rule isn't yet activated. I tried to activated it but a error message like:
Error generating program
Message no. RSAR245
Diagnosis
An error occurred in the program generation:
Program / Template: RSTMPL80
Error code / Action: 6
Row: 49
Message: Statement concluding with "...LIKE" ended unexpect
Procedure
If the problem occurred during the data load or transport, activate the transfer rule.
If the problem persists, search in the SAP note system under 'RSAR 245'.
Please help!
Thanks a lot.
JuanHi dear all,
Thanks!
I tried to re-install this business content just with flow before. And It works.
Best regards.
Juan -
Error occurred when creating transfer structure /BIC/CCGS0EC_PCA_1
Hi Experts,
While activating th transfer structure 0EC_PCA_1 i am getting the below error
Error when creating transfer structure /BIC/CCGS0EC_PCA_1 in source system N6A420
Message no. R3104
Diagnosis
An error occurred when creating transfer structure /BIC/CCGS0EC_PCA_1 as an IDoc segment in source system N6A420 .
Could any one please help
Thanks in Advance,
NityaHi,
I have a similar issue on one of my clients, unfortunately they are using PSA method already, however, somewhat interestingly when I switch to Idoc it activates fine? The log in SLG1 suggests I analyze the log in source system... when I am analyzing the log in the source system?!?!?!?! Is there another log I am missing? Any ideas anyone? I did check note 493422 however as I have other extractors that are working fine connected to the same source system I am a bit loathe to implement a global solution?
Thanks in Advance
Peter -
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 -
Vehicle Scheduling Error:Error when creating transport structures in live C
HI Gurus,
We have one background job defined for Vehicle scheduling, which shows completed successfully but in log it says that :
: Error when creating transport structures in liveCache and Not possible to schedule shipment in the planning horizon.
My planning horizon is for 90 days from current date and demand horizon is for 30 days.
I have checked the VS profile and i dont find any problem with profile.
Can you please help me in finding what exaclty went wrong
Thanks,
AMolTry This..
1. Open the crystal client on your local machine and import that particular report.
2. Do Database -> Verify Database. Then refresh the report on your PC and make sure that it returns data as expected.
3. Export it back to repository and try scheduling it again. You can verify through CMC for Crystal Reports under " Database Configuration" property to make sure it points to the right ODBC.
Let us know. -
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 appreciatedHi
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 -
Error when transporting transfer rules
Hi, i got an error when i transport transfer rules. i got the following errors in various transfer rules:
Mapping between data source 0CUSTOMER_ATTR and source system EMP300 is inconsistent
AND
Reference to transfer structure 0CUSTOMER_ATTR_BB not available. No activation possible.
I tried to activate the data sources and transport them several times, but i got the same errors. Checking manually i can see the data sources active in my source system, in development and productive instances.
Thanks in advance.
Diego LombardiniHello Diego
Do you choose the correct Transfer Structure in DEV?
I mean the one that is assigned to EMP300.
Are you saying that your PROD have the following:
0customer_text_BA
And that your DEV only have the following:
0customer_text_BB
If the answer to the above questions is YES;
Find out if some one has assigned ATTR to 0CUSTOMER directly in PROD or somebody has changed 0CUSTOMER_ATTR in DEV without transporting it to PROD.
I think that one way to resolve this problem is to use the option "overwrite origanls" in STMS.
Use it with caution and do not mass transport when you use this option.
Good luck
/FZA
Message was edited by: Fariborz Zangoui
Message was edited by: Fariborz Zangoui -
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 AMHi,
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 -
Error when activating transfer rules
Dear Experts,
I am getting the following errors when trying to activate my transfer structure. I am working on a system that has been just upgraded. So, any idea of what the problem could be?
Here is the error:
Mapping between data source 0FI_AR_3 and source system AMC_103 is inconsistent
Message no. RSAOLTP380
Thank you very much.Hi venkat
Please check the OSS note 606437
Sriram -
BI Content Error when activating transfer rule / SAPSQL_ARRAY_INSERT_DUPREC
Hello Experts,
when i want to iinstall the transfer rule /CRMBW/OLTP_OPPORTUNITY_ITEM
from Data Source /CRMBW/OLTP_OPPORTUNITY_ITEM to InfoSource
/CRMBW/OPPORTUNITY_I (all Business Content Objects) Iam facing the following situation:
1. When I use "Simulate Installation" i get the warning for all of the fields: Field APP_SERVER is not supported by DataSource /CRMBW/OLTP_OPPORTUNITY_ITEM in source system SLOGICOCRM. Transfer rules were deleted however, delivered.
2. When I use "Installation" i get a dump of the following type:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
Error in the ABAP Application Program
The current ABAP program "CL_RSAR_FORMULAS==============CP" had to be
terminated because it had come across a statement that unfortunately cannot be executed.
More details of the dump are:
Trigger Location of Exception
Program CL_RSAR_FORMULAS==============CP
Include CL_RSAR_FORMULAS==============CM00E
Row 40
Module type (METHOD)
Module Name GENERATE_ACTIVE_VERSION
The problem is, i can not map the transfer rule by myself because the the transfer structure contains some important Routines and Formulas which are missing in thereports and i dont know the source code they are using.
Can anybody help me?
Greetings from Barcelona
Oliver
Edited by: STRATESYS CONSULTING on Jul 23, 2009 2:35 PMHi Oliver,
Can you please check if you can use the SAP notes 1263075 and 985052 to resolve the problem?
Best Regards,
Des -
Error when activate I/O: inconsistency DD - DB
Hello gurus,
I modified the IO 0COSTELMNT in Dev system, I added two custom IO as attributes.
I modified the transfer rule and Communication Structure.
I transported the modify with success and I load the master data in order to populate the new attributes (in Test and then Production system ).
Looking the values I realized that the new attributes were time dependent, maybe by my mistake.
Then in Dev system I deleted the flag "Time dependent" for the two new attributes in the section "Detail/Navigation attributes" of IO 0COSTELMNT.
When I transported this last modify I received the error:
Char. 0COSTELMNT: Attribute ZCOSTELMP is time-dependent (cannot become time-independent)
Message no. R7583
Diagnosis
You have changed the attribute ZCOSTELMP for characteristic 0COSTELMNT from time-dependent to time-independent. An analysis of the master data found that, over time, various values existed for the attribute. The attribute is therefore time-dependent.
System response
You can not change the attribute to time-independent.
Procedure
You first have to delete master data from characteristic 0COSTELMNT so that the ambiguous forms of attribute ZCOSTELMP will disappear over time. Only afterwards can you change the attribute to time-independent.
Then I restore the flag "Time dependent" for the two new attributes in Dev system and I re-trasported the modify in Test system.
I receive this error
No active nametab exists for /BI0/QCOSTELMNT
Termination due to inconsistencies
Table /BI0/QCOSTELMNT (Statements could not be generated)
DDIC Object TABL /BI0/QCOSTELMNT has not been activated
Error when activating InfoObject 0COSTELMNT
Characteristic 0COSTELMNT is blocked by conversion
I check the table /BI0/QCOSTELMNT in the ABAP dictionary, I received thi error
/BI0/QCOSTELMNT : inconsistency DD <-> DB (check table with analysis tool).
How can I resolve this problem? My BW version is 3.50.
GianniThe activation is unable to adjust new columns/attributes with existing ones at DB level....so delete all values in IO tables.
Use se14 to further clean up individual tables.
CAUTION: You might have to make the same clean in PROD....so this will result recomputation on SID...
Maybe you are looking for
-
R12 Payable - Payment Process Request Report
I need to list payments ordered by vendor name in Payment Process Request Report. Currently I don't see any logic how payments are printed in "Payment Process Request" report. Does anyone know how to resort this report? Thanks, Joon
-
I have a very old (by computer standards) MacBook Pro, and a newer one. I've been using the old one mostly for iTunes, into which I have only CD entries. For a long time, years, the old MacBook pro ceased entering the song titles. This is very tim
-
Installed new hard drive, loaded Snow Leopard from disk, how to get back to Lion?
Our 2006 24" iMac, 2.16 C2D (EMC 2111) running the most up to date version of Lion had a hard drive failue. I replaced the hard drive and used the Snow Leopard disk we had to load the OS X. During installation I went through the migration assistant t
-
I just bought a phone off an individual however they did not remove the device from their icloud, find my iphone etc. so i cannot access the phone since i do not have the password and the person is no where to be found. Is there anything I or apple c
-
I can not open multipule windows of firefox, I cannot open a website from an email.
I use to be able to have several windows open and since the most recent update, I cannot. after I have one window open, if I close it I have to restart my computer in order to open the browser again.