Transfer structure prefix error

Hi all,
When i active the transfer structure of any infosource of Ecc5.0.,I got an error message 'Transfer structure prefix for source system T90CLNT090 is not defined'. The source system T90CLNT090 is the current client of bw system.Any one who met the problem before,or have some idea about this,appreciate for sharing your experience.
best regard,
Eric

Hi Natovian,
Thanks again for ur time replying me!
I tried to follow what ever u said.. but still unsuccessful.
The Following is the screen that appears after I used SE37--> RSAP_BIW_DISCONNECT:
http://farm1.static.flickr.com/212/495977912_6f890cad34_o.jpg
I tried to see the entries for SLOGSYS & RLOGSYS using the TCODE SE16, following is the RSBASIDOC table screen which appears as:
http://farm1.static.flickr.com/208/495995911_2213885c8e_o.jpg
From the above table(screen) which combination do I have to use as entries to the following Screen(Using SE37 RSAP_BIW_CONNECT) :
http://farm1.static.flickr.com/226/495977908_9c0ee51f29_o.jpg
D I have to enter an entry for the RFC target system:??
Note: I am Using SAP ECC 5.0 IDES version; have 3 source systems defined
1. Source system T90CLNT090 with clinet 800 ( through which I run rsa1 to move on to BW 3.5 Administrator Work Bench screen) .Its a Combined Client I guess!! But basically I enter into R/3 System first before I jusm onto BW screens
 2 nd and 3rd are the Flat File Source Systems(SS_DEMOFF & SS_ODSFLAT) which I created by my own. and My use ID is SAPUSER for 800 Client to enter SAP.
Do I have to have a BW source System as well do make this work??
I have selecetd and tried the folloowing entries from the RSBASIDOC table :
http://farm1.static.flickr.com/191/495977906_e10a056721_o.jpg
and in the result, it says that the logical system already exists.
I even tried using the flat table combination but the follwing is the result screen:
http://farm1.static.flickr.com/226/495977956_073272c7ab_o.jpg
I tried my level best to actually let you know, whats really happenening with my issue.
Hope u will have a clear picture of my problem.
Awaiting for ur precioius reply!!
Vamsi.
I tried defining a BW source system but got stuck in the middle filling up those details.
Thanks

Similar Messages

PlzzReply.. rlly Urgent:Transfer Struct. Prefix Error while Activating ODS

Hello BW Gurus,
When I am trying to activate my newly created ODS , the following error is one among the 3-4 errors : "Transfer Structure prefix is not defined for T90CLNT090 system". I am using ECC 5.0:BW 3.5
I followed the steps provided in the following link, but not successfull.
Transfer structure prefix error
I dont find any entries in SLOGSYS(T90CLNT90) & in RLOGSYS(T90CLNT90)..
I need to resolve this error as soon as possible as we dont have the Basis guy at the moment. (as it is not letting me activate the newly created ODS to load the data in it)
Not an issue awarding points.
Thanks,
Vamsi.

Hello Mr.Cora,
Thanks again for ur time in relpying me. And Extremely sorry for my late response. I am not in the City these four days.
I guess whatever u have observed is merely correct.
I am in BW learner and I am using an IDES version which is installed in my PC called ECC 5.0 (which should resemble the features related to NetWeaver 2004 and I heard ECC 6.0 should be resembling NetWeaver 2004s)
So ECC 5.0 is a combined package which has SAP R/3BW 3.5mySAP Components etc..
I Login using SAPUSER as my user ID and 800 as my client with a certain password and enter into SAP environment and then I use RSA1 to enterinto BW Administartor Work Bench (we could fix a transaction to directly switch to that screen though soon after we login)
I did not do any system copy and I dont have a specific separate landscape system and as u said mine should be Development system as My Application Server's name is: SAP_DEV_00.
I have 3 logical Source Systems defined:
1. It is the main ID i.e., T90CLNT090 with 800 Client( which is defined at the time of Installation of ECC 5.0)
2nd and 3rd are the Flat file source system which are defined by myself for my flat file loading purposes.
Note: I have Database, Application and Presentation layers in only one CPU(i.e., in my PC alone)
And Mr. Cora plz let me know the Following:
1.The conventional Landscapes and their logical names (for Non-Netweaver versions like SAP R/3 till 4.6X versions and for Netweaver 2004 &2004s versions). and
2. Does the Different landscape environments eg; DEV, QA,PROD have same Logical Sorce systems defined?? or Different ones??
Hope now u have a good idea about what I have it with my PC.
As I am not able to activate my ODS .. I am not able to load my flat data or any data.. so that I could move on with my preparation!!
Any kind of help in this reagard is more than a help for me..
thanks,
Vamsi.

Transfer Structure Error

Hi Guys,
I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.
Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130
Message no. R3104
Diagnosis
An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .
System response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.
I am using PSA as the transfer method. Any help is appreciated.
Thanks.

Hi Govind,
To implement what is said in the note IS VERY EASY!
I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.
So, here is a way to implement the program.
- In the text tabstrip of the note click on 'Correction Instructions' tabstrip.
- Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).
- Click on a report name 'z_rs_scrsystem_r3_check'.
- In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.
- Enter program description, choose 'executable' option.
- Into the screen of ABAP Editor copy-paste the code from the note correction instructions.
- Click on 'Check', then 'Activate' icons.
- If everything is OK, press F8 (execute).
Then follow the note:
"These programs have the following input parameters:
SLOGSYS Specify the logical system name of your source system here
RLOGSYS Specify the logical system name of the BW system here
If you enter nothing here, all existing BW source system connections are processed.
Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.
2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.
3. If the error continues to occur:
Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.
After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.
We recommend that you use the PSA transfer method."
Best regards,
Eugene
Message was edited by: Eugene Khusainov

Error while creating table 'EDISEGMENT' entry for Transfer Structures

Hi Guyz...
I've been facing a few issues regarding activation of transfer structures.
I'll explain the whole process...so it makes sense to you guys.
I've initially activated the Transfer Structures in BI Content for Master Data. Later on we faced some issues in the DEV server. So we had to transport all the objects and store them locally on a temporary location. When the BI DEV sever, was up and running, we transported all the objects back to the server.
Now while moving the objects back to the sever. We had an errors in the Master Data Request (Log- Method Execution). After going into the log...this is what I found.
Error while creating table 'EDISEGMENT' entry '/BIC/CIIA0DIVISION_TEXT'
Error while creating table 'EDISEGMENT' entry '/BIC/CIIA0DISTR_CHAN_TEXT'
Error while creating table 'EDISEGMENT' entry '/BIC/CIIA0MATL_TYPE_TEXT'
Error while creating table 'EDISEGMENT' entry '/BIC/CIIA0SALESORG_TEXT'
Error while creating table 'EDISEGMENT' entry '/BIC/CIIA0SALES_GRP_TEXT'
I hope, I am clear here.
Any suggestions, guys...
Thanks,
Regards,
G

Hi,
Please check this link:
Error while creating table EDISEGMENT entry
Hope it helps.
Thanks and Regards,
MuraliManohar.

Error in transfer structure while activating the business content

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

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

Error while activating Transfer Structure

Hi Expert,
we have upgraded BW3.1 to BI 7.0, we are getting error while activating transfer structure for 0mat_sales_attr and 0mat_sales_text.
Error is Error while creating table 'EDISEGMENT' entry '/BIC/CIOD0MAT_SALES_TEXT'
Message no. EA201
Diagnosis
An attempt was made to create the entry '/BIC/CIOD0MAT_SALES_ATTR' in table 'EDISEGMENT'. The attempt failed.
System Response
The operation was canceled.
Procedure
Please check whether the relevant entry already exists
I have tried report RS_TRANSTRU_ACTIVATE_ALL also, but no success.
I have checked table and entry is there. i have checked we31 for segment there also segment is existing.
Regards,

Hi Dubey,
I am facing the same issue when i transport the datasource from DEV to QA.i applied the OSS Note 493422 ,But could not resolve the issue.Pls let me know the solution to fix this.
Thanks,
Renu

Error while activating transfer structure and communication structure.

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

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

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 in Order Settlement (KO88) Complete PA transfer structure A1

Dear Gurus,
In order to close a Production Order
I am trying to Settle the order using KO88 after determining Variances using KKS2.
The System is showing Error "Complete PA transfer structure A1".
Pls guide what to do?
Himanshu

Go to KEI2 and assign any unassigned cost element used in the settlement to a CAOP value field for transfer structure A1

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

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 in Transporting the Transfer structure

Hi can any body tell me . Iam getting this error while transporting from BW System the transfer structure for 0HR_PY_1_CE.
1. Transfer structure 0HR_PY_1_CE_LA does not exist.
2. Error RSAR 440 during after import handling of objects with type(s) ISTS
3. Errors occurred during post-handling RS_AFTER_IMPORT for ISCS L
I have activated the transfer structure through this programme - program RS_TRANSTRU_ACTIVATE_ALL.

Check the below notes:
Note 1009638 - RSAR 440 when you activate transfer rules applicable for BI7.0 Less than SP12.
Note 736668 - RSAR 440: Transfer structure & does not exist Applicable for 3.x system.
Please check the above Notes and based on your system patch level and issue you need to choose the right one. Second one deals with the Hierarchy.
Hope this helps..
Murali

Error when trying to activate transfer structure

Dear experts
I got this error when activating the Transfer Structure in the Data Souce:
   Table is not yet classified
   Field /BIC/ZPRCH026 is too long (Specify a length between 1 and 255)
   Flag: 'incorrect extension category' cannot be updated
   Table /BIC/B0002707000 was not activated
FYI, the lenght of the info Object /BIC/ZPRCH026 is 1000, as per other similar DataSource.
What should I do to remove this error?
Your help is greatly appreciated

Hi
I thought i have managed to reactivate the transfer structure. This was how i did it:
1. I went to SE11 and opened table structure /BIC/B0002707000 as per the error
2. I changed the character limit of ZPRCH026 to 255
3. I reactivated the table.
Then, I went to rsa1 to see the DataSource (which contains the Transfer Structure) and see that it is now activated.
I proceeded to create an Info Package under the DataSource, because I need to initialiase a delta queue.
Here are my config (in the info package):
1. In Update tab, I selected "Initialixe Delta Process" and check "Initialize without data transfer"
2. I select "Always update data, even if no master data exists for a characteristic"
3. In Schedule tab, I started the load immediately ("Start Data Load Immediately")
But then I got a message "No Transfer Structure Available D09_010 6AZPR034 (SY-SUBRC=5)"
FYI, D09_010 is the source system, 6AZPR034 should be the data source.
Could anyone advise me what went wrong?
Your kind help is highly appreciated
Many thanks
Wan

Error when 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)

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.

Transfer structure prefix error

Similar Messages

Maybe you are looking for