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 PM

HI,
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..

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 creating Transfer structures

Dear Gurus,
I get the following error when creating the transfer structure.
Error when creating transfer structure /BIC/CCBD1CL_OMAT002 in source system ERPCLNT400
Message no. R3104
DiagnosisAn error occurred when creating transfer structure /BIC/CCBD1CL_OMAT002 as an IDoc segment in source system ERPCLNT400 .
System Response
The action was terminated. No data was changed.
Procedure
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)

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

Try 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 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. R3104

Hi
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 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.
Gianni

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

Error when activate analytic view (join tables)-Exception during activation

Dear guru,
I suffered an error showed "Exception during activation" when activate a newly created analytic view.
I used two tables, one is NASDAQDAILY, one is NYSEDAILY.
Private attribute are "DATE, STOCK(NYSE.STOCK), STOCK_1(NASDAQ.STOCK"
Measure are "PRICEOPEN(NYSE), PRICEOPEN_1(NASDAQ)"
JOINS are: Left Table-NASDAQ, Left Column-DATE
Right Table-NYSE, Right Column-DATE
Validate is sucessfully.
But when "Save and Activate", it gave below error.
Kindly help me on this. Thank you so much.
com.sap.ndb.studio.sdk.resource.deployment.bi.DeploymentException: Error during deployment
_     at com.sap.ndb.studio.sdk.resource.deployment.bi.cv.CubeElement.processMeasures(CubeElement.java:591)_
_     at com.sap.ndb.studio.sdk.resource.deployment.bi.cv.CubeElement.initialize(CubeElement.java:170)_
_     at com.sap.ndb.studio.sdk.resource.deployment.bi.cv.CubeSchemaRoot.initialize(CubeSchemaRoot.java:80)_
_     at com.sap.ndb.studio.sdk.resource.deployment.bi.DeploymentExecutor.initialize(DeploymentExecutor.java:159)_
_     at com.sap.ndb.studio.sdk.resource.deployment.bi.CubeDimensionDeploymentExecutor.initialize(CubeDimensionDeploymentExecutor.java:78)_
_     at com.sap.ndb.studio.sdk.resource.bi.core.impl.BiResourceImpl.activateObjects(BiResourceImpl.java:236)_
_     at com.sap.ndb.studio.sdk.resource.repository.core.impl.ResourceImpl.activateObjects(ResourceImpl.java:868)_
_     at com.sap.ndb.studio.sdk.resource.repository.core.impl.ResourceImpl.activate(ResourceImpl.java:727)_
_     at com.sap.ndb.studio.sdk.resource.repository.core.impl.ResourceManager.activateAll(ResourceManager.java:166)_
_     at com.sap.ndb.studio.sdk.resource.repository.core.impl.ResourceManager.activateAll(ResourceManager.java:202)_
_     at com.sap.ndb.studio.modeler.job.type.activate.ActivateJob.activateObjects(ActivateJob.java:92)_
_     at com.sap.ndb.studio.modeler.job.type.activate.ActivateJob.run(ActivateJob.java:71)_
_     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)_

Hello,
This issue is resolved now.
The problem was with the file system space on the Unix server(on which portal is installed).
The server administrators and the Basis team extended the disk space and issue got resolved.
Thanks for all your inputs.
Sonali.

Error when activate the Adobe forms

Hi,
I am getting the below error message when activate the adobe forms,and the message tells that to install a forms design tool,please tell me which tool in need to install and where i will get this tool.
Could not start Layout Designer (see long text)
Message no. FPUIFB086
Diagnosis
The forms design tool for developing the form layout could not be started; either it is not installed or there are errors in the installation.
Procedure
Make sure that you have the forms design tool installed on your desktop (the tool is part of the SAPGUI installation).
Also read SAP Note 801524.
Thanks,
Deesanth.

FIrstly, you have posted the question in the wrong forum. There's an entire forum in SCN only for Interactive Forms: .
Secondly, this is a frequently asked question, especially in the Interactive Forms Forum. There's enough information there to get your query solved by searching.
pk

Error when activate Transformation to cube 0IC_C03

Gurus:
I need to activate the 2lis_03_bf_tr transformation to cube 0IC_C03, when I activate the transformation, the system indicate the next error:
"E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter "SOURCE_PACKAGE" is incompatible with the formal parameter "DATA_PACKAGE"."
I made changes in the routine, but the error still happens
Thanks for your help!!!!
César.

It seems like you have migrated the 3.x data source to 7.0x version. And I believe you have added new info objects. In the start routine code add the new info objects to the structure "_ty_s_*_" whenever you add new fields.
In the code in the
"Rule Specific Types"
"Types"
"BEGIN OF tys_*_"
Add the info objects.
*Please assign any rating if you find the answer helpful*
Edited by: ram.pch on Jul 2, 2011 6:02 AM

Error when activate Info Object

Hi everybody.
Maybeyou can help me.
I made a transport to the production system.
The system was disconnected when i made the transfer. The transportation has fail, however, has generated objects in the target system.
In particular I have a problem with a standard InfoObject (0GN_BWBEOTY).
This object was transported to Production environment but has been inactive.
I can not activate it.
I used the transaction RSRV InfoObjetct, to validate integrity and I get the following errors:
CL_RSMD_RS_0GN_BWBEOTY Class, Method IF_RSMD_RS_ACCESSS ~ get_text.
"RSBWBEOTY" is not defined in the ABAP Dictionary as a table.
I tried to move into a new transport order, the only InfoObject but I get error code 12.
Someone has happened, can you give me ideas? what can i can do?
Thank you very much for help me!

Hi!
Thank you for your help.
I still have the problem .
I can not verify whether the information in master data, since the transported infoObjetct not appear in the RSA1 (production) and can not display the master data RSDMD trx.
And i can not activate through RSDG_IOBJ_ACTIVATE. I get the error message detailed in the first post.
This is the transport log:
 | Program terminated (job: RDDEXECL, no.: 15123000)
| See job log
| Execution of programs after import (XPRA)
| End date and time : 20110519151246
| Ended with return code: ===> 12 <===
| ######################################
This is te JOB Log:
19.05.2011
15:12:31
Job started
00
516
S
19.05.2011
15:12:31
Step 001 started (program RDDEXECL, variant , user ID DDIC)
00
550
S
19.05.2011
15:12:31
All DB buffers of application server SFESA-20 were synchronized
PU
170
S
19.05.2011
15:12:36
Internal session terminated with a runtime error (refer to ST22)
00
671
A
|19.05.2011 |15:12:36 |Job cancelled
Any ideas?
Edited by: Javier Sarrelli on May 20, 2011 8:14 PM

Error When Activate Adobe Form?

hi,
          When i save layout and come out from there and than when i am save adobe form and trying to activate form it ask me in the dialog window,
Enter your user name and ID
Resource     AdobeDocumentServices/Con
User name
Password
if i enter my logon id & pwd it shows me status message,
SOAP Framework Error ; SOAP Runtime Error : CSoapExceptionTransport : HTTP Send returned with status code (100,101).
Please try to resolve and get back to me ..
Thanks,
Saurin Shah

Hi,
Please check below link
http://help.sap.com/saphelp_nw70/helpdata/EN/4f/a00d41921bf023e10000000a155106/content.htm
Regards
Jana

Error when activate a SAP source system

Hello Experts,
I have an issue when I try to create a new SAP source system but I cannot complete this operation because a Timeout error occurs when the system made the destiny verification, the source system can be created but not activated, I already create the RFC connection and they are OK, I add the new logical system of the source system in the configuration (SBIW) in the general settings,and the data source tree is show succesfully and sems to work OK and the data sources seems to be OK too.
In the RSA1 transaction, go to source systems tree, choose the SAP source system called: "conexion a dev 200" -> right click and choose activate and the error occurs.
I have a Myself source system already created and activated, I cannot find the source of the problems thata cause the timeout error in the new source system.
Thank you vey much in advance,
Niurka

Yes, I try ti use the create automatically option first but it doesn't work, because says that we system already exists because here exist a myself source system with an RFC to R/# ( I don't know why), so I must use the manually creation option, I put the logical system, and all the requeriments of the screem. The system create the source system but when I try ti activate it, it is impossible to do it....!
I hope that you can give some tips or solution for this issue,
Thanks!

Null Index Error When Sorting Standard Report Column

I have a page in one of my application that contains three reports in three seperate regions within the page. You only see one report at a time, however, and control which one you see based on a sidebar table containing links that call javascript functions to toggle the hiding/showing of each region.
The problem stems from trying to use the standard column sort on any of the columns. When I click the column header in any of the the reports, the page submits the request to sort the column (for example: request="fsp_sort_6", etc...), and then the page refreshes with all three reports displayed. The report for which you actually 'clicked' a column header will be sorted. However the other two will display with an error (code ORA-06502) saying that the report cannot parse the query because of a null key index value in one of the corresponding tables being queried.
The weird thing is - this only happens on other computers - not when I'm on my workstation developing in my apex workspace/schema. I've even given each of the three reports a seperate static ID attribute so that I can identify each using those unique IDs.
I have to say - I am stumped. Any help would be much appreciated. If you need more details, feel free to respond to this thread.
Thanks!

What version of APEX are you using? This was supposed to be fixed in 3.1 however it isn't because we still experience it sometimes, we just have never been able to re-create it in order to raise an SR. Getting to the bottom of this would be fantastic for us as it's the one thing which makes me extremely nervous of implementing new applications which are production-critical. The only workarounds are to flush the SGA or edit the report in production so the query is different (usually just fetch back null somewhere and then hide the column). This clearly isn't acceptable however without a reproducable test case there isn't much which can be done! :(

Error when activate 0DISTR_CHAN

Hi dear all,
I''ve a quesiton urgent in BW3.5, plz.
I've activated IO 0DISTR_CHAN, so his flow before and after. I went to load master data, but I found its 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.
Juan

Hi Sunil,
Thanks a lot.
I can't modify the Communication structure like in SAP note 602318, maybe because it's an InfoSource for InfoObject.
I tried to re-install this business content just with flow before. And It works.
Best regards.
Juan

Error when Activate an DataStoreObject while transport

Hi experts:
I Try to transport an DataStoreObject From QAS to PROD.
1. I transport all Infoobjects from DEV - QAS . PROD OK.
2. I transport an ODSO from DEV - QAS OK.
3. When y try to transport to PRD y have the folowing error:
Error / Warning in progr.activación Dict., Detailed log> Detail
By detail (or the path details -> Log -> Turn Dictionary ABAP) will receive full details of the log module activation.
I dont know where do this.
I need activate this details log error.

Hi,
Yes of course i see the log in se09 and the first error I found is as follow.
Error / Warning in progr.activación Dict., Detailed log> Detail
Failed attempt to execute the SQL statement.
Table / BIC/B0000314000 (failure to adapt the database).
Table / BIC/B0000314000 could not be activated.
Then follow otrers error.

Error when activate standard structure

Similar Messages

Maybe you are looking for