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

Hi dear all,
Thanks!
I tried to re-install this business content just with flow before. And It works.
Best regards.
Juan

Similar Messages

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 Lombardini

Hello 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

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 PM

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

Not possible to edit Comm. Structure or Activate transfer rule

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

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

Unable to activate Transfer Rule

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

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

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)

Error when activating update rule

HI BI Expert,
The original transfer rule for 2LIS_11_VAITM was deleted accidently and I created new one and mapped with the existing infosource. The system always generates the following error at the time of transport to another client.
Error when activating update rule D1GOAPD9O0P9CFOY8KBSOUDFA
Activation of the update rules for ZO_SOP_1 ZT_SOP_SALO_ITM
IC=ZO_SOP_1 IS=ZT_SOP_SALO_ITM error when checking the update rules.
Would you kindly be able to suggest me what steps I need to take so as to correct this issue?
Thanks.

Hi,
When you say that update rule was accidently deleted, was that attached to transport request and transported to your QA & PRD at that time.
Because it may happen that, your old rules are still there in QA & PRD and the new rules are failing to overwrite that.
If it is the case, then you may have to open the client for QA & PRD and delete the existing update rule (doesnt sound good practice though), and then create a fresh update rule and transport.
Rgds,
Vikram.
Rgds,
Vikram.

Error when activating update rule after transporting to QA

Hi,
When we transport Info cubes and update rules along with Process chains. There are the following errors in Transport request(XXXXXXXX).
1. Error when activating update rule 22HSFD3ZMALU46LS0R8PRF2MW
IC=ZSDPCXY2 IS=2LIS_11_VAITM error when checking the update rules
2. Error when activating update rule 7NT4WIDPDCN2ERFDRXIGH95PM
IC=ZSDPCXY2 IS=2LIS_12_VCHDR error when checking the update rules
and etc.
Then we activated and saved all the erroneous update rules in another tranport request(YYYYYYYY) and again we transported alongwith the previous transport request(XXXXXXXX).
The last request(YYYYYYYY)was successfully tranported and still there are same errors in TR(XXXXXXXX).
Quick answers will be highly appreciated.
Regards,
Vijay

Hi Vijay,
Next time you would have transport only (YYYYYYYY). Transport Request (XXXXXXX) was not required to be moved.
Normally Update Rule gets deactivated in QA when any changes to the CUbe/ODS are moved.
Thus either you can transport transport request for only active update rule to QA or activate your UR directly in QA system in case you have authorization to do that.
Regards,
Rohini

Error while activating transfer rules needs help.

The error while activating 0FI_AP_6 transfer rules is listed below.
''InfoObj. 0DEBITOR from fld KUNNR of dataSource 0FI_AR_6 is not active but BCT ex. -> Dtl'' how to resolve this issue and activate transfer rules?

Hi
The problem is with your data source replication.
Activate your data source & replication too.
Activate your transfer atructure through RS_TRANSTRU_ACTIVATE_ALL .
If not so, Activate your transfer rule manually.
Regadrs
Saravanan.ar

Error while migrating transfer rules

Hi all,
When migrating 2LIS_02_SCL transfer rules to transforamtions I got a shotdump "ASSERTION_FAILED in 'CL_RSTRAN_TEMPLATE->CREATE_ROUTINE" for this I have implemented Snote : 986199 after this when I am migrating transforamtions are getting created but showing syntax errors (for this transfer rules there are standard routines ) .Can anyone help me to sort out this issue.
Regards
KK

Hello,
unfortunately not all transfer rules can be migrated automatically.The migration of the business content transformation is done on customer project base. This means some of the adjustments needs to be done manually.
Please adjust the rules to the ABAP OO compliance.
This how to paper should help:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fc61e12d-0a01-0010-2883-e2fc63ef729b
and
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e73bfc19-0e01-0010-23bc-ef0ad53f2fab
I hope this helps.
Michael

Programme to activate transfer rule

Hi Gurus
I am trying to load data to newly transported work from BWD ( infosource 0FI_AA_11 ) but I got some error while loading transactuion data so i was told to run ABAP programme RS_TRANSTRU_ACTIVATE_ALL to activate transfer rules but not sure which transaction I need to use to run this programme .So would you pl tell me the name of the transaction and also tell me the logic behing running this programme?
Thanks as always

Hi Gurus
I have activated all the transfer rules and then try to load the transaction data but its stil;l giving me the same error.
Extraction of 0FI_AA_12 not possible. Extract 0ASSET_AFAB_ATTR first
Errors in source system
I have already loaded the master data and I have replicated the data sources also .So pl tell me what and where I need to check to load the transaction data successfully.

Activate Transfer Rules

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

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

Activate transfer rules - problem

I was creating transfer rules for DSO 0FIGL_O02 for infosources 0FI_GL_4. Activate transfer rules bring me mistake :Data element for InfoObject BELNR 0AC_DOC_NO could not be created.
Information from log:
Data element for InfoObject BELNR 0AC_DOC_NO could not be created
Message no. RSAR274
Diagnosis
Special data elements of the type and length of the source system are required for creating the transfer structure. Errors occurred while creating a data element of this type for InfoObject BELNR 0AC_DOC_NO. The data element should be of type CHAR and length 000010. The technical name of the data element is /BIC/OW_######################.
Procedure
Check the log.
Check data element /BIC/OW_###################### in the repository. Activate data element /BIC/OW_###################### in the repository and check the activation log, if necessary.
0AC_DOC_NO - is important because this is key in DSO. This object have type CHAR and length 10. What i shoult do?

Hi,
Activate the Infoobject 0AC_DOC_NO is not recognizing by system please re-activate this once again and check the transfer rules.
Regards,
Anand Tej.

Error when activate transfer rule 0DISTR_CHAN

Similar Messages

Maybe you are looking for