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

Similar Messages

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

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

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 a new Data Source

All, This is on BI Publisher 11g.
When I create a new data source and supply password and then click "Apply" button on top right corner, i get following error
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
what am i doing wrong?
Thank you for reading this post.
Thanks,
R

The schema/user is system and the password is alpha-numeric, upper/lower case, no special char ...
As a workaround I was able to add the password to the entry in the datasources.xml file and restarted BI Pub.
The JDBC is working ... I can test the connection successfully ... just wont save the entry
Edited by: tread on Oct 17, 2011 11:55 AM

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 Task List: No Consolidation System found

All-
Configuring my Retrofit Scenario. My Project Landscape is maintained as following:
Dev(100) --> QA (200) --> Prod (300) with Retrofit (XXX)
Dev(XXX) --> QA 250
I am getting this error when I try to refresh the project or create a Task List
*No consolidation system found for <SID>-250 (project RETROFIT3)
Message no. /TMWFLOW/TRACK_N806*
If my QA client (250) is already maintained as a QA logical component. What else is missing?

Hi,
I have done something similar and getting error /TMWFLOW/TRACK_N806
My Transport route looks something like
System GND ZGND > 300 System GNQ 300> 300 System GNP
Its a standard 3 system landscape with transport routes configured as mentioned above. I followed the write up as mentioned and have kept only one transport route but how do i create a transport route from GND-140 to GNQ-300 .
The layer ZGND has been associated with client 140 which is the development client here. The layer ZGND is the consolidation layer, how else should i associate it with the client 140.
Please advice.
Regards
Ankan

NA R3104 Error Creating Transfer Structure

Hi all,
After digging around for a while now, I'd better post this question, because I can't figure it out.
I added some fields to datasource 2lis_02_itm in R3. Adjusted user exit to fill them. Generated datasource. Tested functionality with rsa3.
First off I don't see the newly created records here at all (though in debugging it appears as though they are being filled).
Secondly, I'm having trouble (after replicating datasource in BW), activating transfer rules. It keeps giving me the message:
Error when creating transfer structure /bic/ccpc2lis_02_itm in source.
Diagnosis: An error occured when creating transfer structure /bic/ccpc2lis_02_itm as an IDoc segment in source system NTLPSS033.
Using se38, RS_TRANSTRU_ACTIVATE_ALL it tells me:
Transfer structure 2LIS_02_ITM_PC NOT activated successfully
Activate manually
Activating from within the transfer rules doesn't work either.
I tried to change everthing back, but the error messages remain the same!
How can help me out here???
Kind regards,
Aukje

Hi Aukje,
We solved this problem applying SAP Note 493422 in ECC (Inconsistent IDoc segments/transf. structures in srce system). This note has a program (Z_RS_SCRSYSTEM_R3_CHECK) that clean up old IDOC segments and ROOSGEN DDIC structures. This note is for Source System (not BW).
https://websmp230.sap-ag.de/sap/support/notes/convert2pdf/0000493422?sap-language=EN
BR,
Marco Modesto.

Generation Log for Trasfer Structure on Source System

Hey Folks, I'm reciving a weird message at the moment of activate the transfer rules, something like:
Error when creating transfer structure /BIC/CCGO0CO_PC_01 in source system XXXX,An error occurred when creating transfer structure /BIC/CCGO0CO_PC_01 as an IDoc segment in source system XXXX Meesage Number : R3104
Could someone explain where on the source system Side can I check the generation log for this?
Thanks a lot

Hi William,
The problem may be because of some error in connection with Source System . Check all entries in table T000. Note them up in field RLOGSYS and check with RSBASIDOC with fields Rlogsys and Slogsys .
U can see the Source System assignment and IDoc type is the table RSBASIDOC .
Check the field RlOGSYS in the table.The possible cause of error is caused because of renaming the Source System
Check with the assignment in Sourcesystems of BW .
also Check with Transaction RS_LOGSYS_CHECK in R/3 .
U can have more information in the OSS Notes : 140276
Hope it helps.
Thanks,
krish
*Awarding points is a way of saying thanks in SDN
Message was edited by: krishna V

Procurement Coordinator received Authorization Error when creating Bid Inv

Hi All,
In SRM I have an issue Please help me in solving this. Please see below
Procurement Coordinator received Authorization Error when creating Bid Invitation from Sourcing Cockpit. Message states u201CMissing Transaction BBP_BID_EXTSOu201D; however Bid # is still created. User requests that Authorization issue is resolved and Bid # appear for Procurement Coordinators. This problem does not happen for Commodity Managers

Hi
Please do the following steps.
When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT )
ALso pls check the foll:
-->activate the services through SICF tcode.
> Go to SICF transaction and activate the whole tree under the node Deafult host>sap>bc>gui>sap>its.
>Also maintain the settings in SE80>utilities>settings>internet transactuon server-->test service/Publish.
Table TWPURLSVR should have entries for the / SRM server line as well as gui and web server.
Could you please review again the following steps ?
Did you check that ICM was working correctly (TA SMICM) ?
1-Activate the necessary ICF services
With transaction SICF and locate the
services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
2- Publish the IAC Services
With Transaction SE80 locate from
the menu Utilities -> Settings ->
Internet Transaction Server (Tab) ->
Publish (Tab) and set On Selected
Site = INTERNAL.
3- Locate the Internet Services SYSTEM and WEBGUI.
Publish these services with the Context
Menu -> Publish -> Complete Service
4- Browse to http://<server>:<icmport>/sap/bc/gui/
sap/its/webgui/! and login to the
webgui.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Problems Creating R/3 46c Source System in BW3.50

Hello.
Does anyone know if there is a way around opening up your R/3 system when creating it as a Source System in BW? I have no problems when creating the Source System in DEV, but when I attempt to create it in QAS and PRD, I get the message "Changes to Repository or cross-client Customizing are not permitted". Also, short dumps for ALEREMOTE "Dynpro Send In Background" occur in the R/3 system after each attempt.
If there is no way around this, I guess we will just open the systems up to these type of changes and then lock them back down afterwards, but I am hoping there are alternatives.
Thanks for the help.

Hi Mike,
You must open the system for changes, there is no way around this. This is usually not a major issue but if the security people are concerned, you can open a trace on the admin user in the OLTP source system.
I have been involved in cases where the security guys had to open the system and watch the source system creation - not sure they learnt anything but they signed off on it!
Cheers,
Mike.

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

How to Create an R/3 source system and load data from there

Hello All,
Till now I have only worked with Flat files. I want to create an R/3 source system and extract data from there on to my Info Providers.
Does anyone has detailed steps for that. I am using BW 3.5 system
Thanks n Regards,
Abhishek

1. Type Transaction WE30. Check iDoc types
2. Type Transaction SM59. Maintain RFC destinations
a.) Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding yoursource system d.) Logon Information should contain source system client and name & password for you remote logon. We use RFC_SAB for BW logon to R/3 and RFC_AAE for R/3 logon to BW. Password for both is always xxxxxxx. e.) Execute your 'Test Connection' & 'Remote Logon'. You should NOT be prompted for a password, if you are then the logon info is incorrect. f.) Repeat above to verify RFCs for other systems (CRM etc)
3. Type Transaction WE21. iDoc Processing Ports.
a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 version.(BW 2.1C should be release 4.x) d.) RFC Destination should be one created in SM59. If non-existent then create one
4. Type Transaction SE16. Data browser (for R/3  BW Connections)
5. Type Transaction SM30. Msg Types & Assignment to iDocs
Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOCtable for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missingentries.
6. Go to the SM30 main screen. Clients Overview
Enter 'T000' in the Table/View field. Click 'Maintain'. Verify correct Client and Description. If incorrect enter.
8. On BW Type Transaction WE20. Partner Profiles
9. On R/3 Type Transaction WE20. Partner Profiles
10. Check all is correct

Need to create a flat file source system in bi?

Hi all,
i need to load the data from a flat file to an ods? can anyone pls tell me the steps to create the flat file source system in bi?
Thanks

Hello,
http://help.sap.com/saphelp_nw70/helpdata/en/43/01ed2fe3811a77e10000000a422035/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6581e07211d2acb80000e829fbfe/frameset.htm
steps:
create source system file (if you haven't)
- create ods
- create update rules for ods and activate
- create infosource
- assign infosource with datasource (source system file)
- maintain transfer rules - maintain infoobject in sequence as flat file to transfer structure. map infoobject in transfer rules. activate transfer rules
- create update rules ods-infosource and activate
- create infopackage, specify external data path (recommended file put in application server)
hope this helps.
Regards,

Error when creating transfer structure in source system

Similar Messages

Maybe you are looking for