Migration of Datasource with routine's

Dear All,
I am in the process of migrating 3.x DataSource to 7.0 and am following the step by step process as suggested.
In doing so transformations are created and proposals are generated where ono-to-one mapping between field and InfoObject are in place.
In case of InfoObject which are populated by routines are not mapped.
For example: for DataSource 2LIS_02_SCL routines are created and mapped for 0Order_val, 0PO_QTY,0TAR_DL_QTY to name a few in the update rules.
My question is how to migrate the routines along with the DataSource for all transformations requiring routines.
or
Is there any other method to migrate the routines
or
Is activating transformation an option?
All suggestions, links, articles, blogs are welcome.
Yours Truly,
K Sengupto

Hi Obaid
I Migrate my data source in Business Content in 3.x and I have my update rule and transfer rule for all ds of purchasing data.
I created a custom cube from 0PUR_C04, I want to enhance the data source 2LIS_02_HDR,
Step by step procedure for creating custom cube ZPUR_C04
1- Select the Cube Standard 0PUR_C04 , Copy
2- Default info cube with name ZPUR_C04
3- Select my new infocube ZPUR_C0
4- Create update rule for the data source 2LIS_02_SCL , 2LIS_02_HDR and 2LIS_02_ITM
With this approach I cant have the update rules routine like standard flow ?
For example 2LIS_02_HDR :
No. of Purch. Orders <-- mm_no_of_po
Number of requests for quotations <-- mm_no_of_rfq
Number of contracts <-- mm_no_of_co
How can do this mapping ? or how can I copy the transformation from standard cube to my custom cube ?
Thanks & Best Reagrds
ILyaebi

Similar Messages

Migration of datasource

Hi All,
I am working on BI7 and SRM standard content. I observe that the hierarchy DataSource are in 3.x version and the classic flow is not coming up after activation.
I have tried to migrate this DataSource to 7.x with the export option but am getting the below error.
" DataSource 0BBP_BIGURE_HIER(SRDCLNT200): Data type H not supported by object type RSDS "
If some one has had this problem below Please help in the resolution.
Kind Regards
Niren

Hi,
We are currently working on BI content 7.0. After transfering we got the 3.5 flow for most of it. Now we are looking for a migration of 3.x flow to 7.x flow. It would be really helpfull If any of you could answer my following queries:
1. How do we migrate queries/workbooks?
2. How much of effort it would be to migrate transformations having routines in it as part of stsandard content . And is it just a copy paste of the ABAP routines or do we need to change it to an Object oriented ABAP?
3. We are having around 100 info providers and 300 master objects. Will it be ok if we come up with a stratergy of migrating the info providers alone and still having 3.x flow for the master info objects.
Thanks and Regards
Niren.

Migration of datasources

hello everyone,
after replicating the data source wen im trying to migrate the datasource from 3.5 to 7 a pop up window opens which says with or without export?
wat does it mean?
thanx in advance

with export - you can recover ur 7.0 datasource back to 3.x one
W/o export - you cant

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Problem in creating a generic datasource with infoset

Dear Expert,
I have to create a generic datasource with infoset. I linked the infoset with a test program below. In the program, I have one selection option, which is s_order. After creating an infoset and a datasource, this selection option 'SELECT_S_ORDER' is added to my extract structure. However, after try filtering with this SELECT_S_ORDER, it doesn't filter data at all. Why? I want to filter data with my s_order.
REPORT ZBI_DS_TEST.
tables: vbak.
* DATA
field-symbols: <vbak> type vbak.
data: t_vbak type table of vbak,
 w_vbak type vbak,
 t_vbak2 type table of vbak,
 w_vbak2 type vbak.
* SELECT-OPTIONS
selection-screen begin of block b1 with frame title text-001.
 select-options: s_order for vbak-vbeln.
selection-screen end of block b1.
 start-of-selection.
* <Query_head>
 perform sub_select_data.
 loop at t_vbak into w_vbak2.
 move-corresponding w_vbak2 to vbak.
* <Query_body>
 endloop.
*& Form sub_select_data
* Select data
FORM sub_select_data .
 select *
 into table t_vbak
 from vbak
 where vtweg = 'IP'.
ENDFORM. " sub_select_data

What do you mean by linking program with infoset?
Do you get the field in your RSA3 Tcode?

Error while migrating the datasource

Hi Guys,
We are using BI 7.0 SP 13 and when we try to migrate a datasource that has been replicated from ECC we encounter an error message as follows
error Message No. RSO404 says "Error when activating Datasource".
Has anyone encountered this issue while activation?
Help is appreciated.
doniv

Hi,
where you are getting error in ECC?. or in BW?. If it is already in use, then you need to clear all Queues and then try to activate it.
Thanks
Reddy

Populating BW datasource with data using Webservice without PI (=XI)

Hi all,
I have got BW datasource and I want to be able to use external Webservice's method to populate my data source with data.
I have created client proxy in BW ( se80 --> Enterprise Services --> Client Proxy ) for my wsdl and logical port in SOAMANGER for my proxy.
I have also created datasource.
Now I need to use one of the methods of the Webservice (proxy ) to populate my datasource with data. This is the bit I am struggling with.
I had a look here on SND but I could not find anything useful. Can you please advice ? Any examples ?
Please let me know whatever you know and maybe helpful.
Feel free to ask questions if I am not detailed enough in my description of the problem.
Regards
Agnieszka Domanska
Edited by: Agnieszka Domanska on Nov 10, 2010 5:41 PM

I have now been able to call a method of the Webservice by writing the simple code:
DATA:
Reference variables for proxy and exception class
lo_clientproxy     TYPE REF TO ZCO_ICAMPAIGN_MASTER_SERVICE,
lo_sys_exception   TYPE REF TO cx_ai_system_fault,
Structures to set and get message content
   ls_request         TYPE ZICAMPAIGN_MASTER_SERVICE_GE25,
   ls_response        TYPE ZICAMPAIGN_MASTER_SERVICE_GE24.
Populate the Request of the SOAP Object
ls_request-CAMPAIGN_ID = '74500'.
****Create the Proxy and Call it.
CREATE OBJECT lo_clientproxy.
TRY.
    CALL METHOD lo_clientproxy->GET_EMAIL_CAMPAIGN_SUMMARY
      EXPORTING
        input = ls_request
      IMPORTING
        output = ls_response.
CATCH cx_ai_system_fault INTO lo_sys_exception.
Error handling
ENDTRY.
COMMIT WORK.

Creation of Remote Partition DB: datasource with ID does not exist in the collection

Hi,
I tried to create remote partitioned DB. Followed the below link to create it.
http://msdn.microsoft.com/en-us/library/ms174751.aspx
In 'partition Type selection' wizard, I selected the remote data source and landed in below error.
'datasource' with 'ID' = 'XXXX' doesn't exist in the collection
Can some one help me to resolve it?

Hi Hsadham,
According to your description, you are creating a remote partition with the error "'datasource' with 'ID' = 'XXXX' doesn't exist in the collection“,
right?
As you can see on that link,
If you get an error indicating the data source does not exist in the collection, you must open the project of the storage database, db-storage, and create a data source that points to the master database, db-master.
So in your scenario, please open the project of the storage database, db-storage, and create a data source that points to the master database, db-master. And then check if this issue persists or not. Besides, please ensure that all the prerequisites had
been done in your environment and the configuration steps are correct.
Regards,
Charlie Liao
TechNet Community Support

The DataSource with the JNDI name: contentDataSource could not be located

Hello,
We try to deploy our system/application to the servers that structed as
Machine one has:
1 administration domain
1 managed domain
Machine two has :
1 managed domain which is administrated by machine one.
I was trying to deploy the UI(portal application) to managed domain under Machine one. I got
error message as following:
Exception:weblogic.management.ApplicationException: activate failed for content.jar Module: content.jar Error: Exception activating module: EJBModule(content.jar,status=PREPARED) Unable to deploy EJB: ValueBean from content.jar: [EJB:011028]The DataSource with the JNDI name: contentDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
I have portalFrameworkPool Data Sources deployed to both managed domains.
when I deploy the application to the server that has one one domain(both adminstrator domain and application domain are in one), it is fine.
Can some one with same experience, or BEA people provide some help on this? Very appreciate any help on this issue.
Thanks in advance.
Christina

:-p
If you go to each Managed Server on the console, you can see the Service tab and then go to JDBC. Under JDBC you can see all the pool connections. Instead of localhost they should be pointing to the specific hostname or ip address of the adminserver and the pointbase port on that server (9093 by default) so the EAR files can be correctly deployed and then the JNDI Tree will look exactly the same on both servers. Change all the connection pools to use the specific hostname instead of localhost. Hope this works for you.

The DataSource with the JNDI name: MyDataSource could not be located.

hi,
I created a connection pool myconnectionpool and i create a data source MyDataSource with jndi name as mydsn.
in my weblogic-cmp-rdbms-jar.xml i gave
<data-source-name>MyDataSource</data-source-name> and
When i deploy the bean i am getting following exception.
Unable to deploy EJB: containerManaged from cmp7.jar:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
 at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:128)
 at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:213)
 at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:185)
 at weblogic.ejb20.manager.DBManager.setup(DBManager.java:160)
 at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:928)
 at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1216)
 at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:850)
 at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:70)
 at weblogic.j2ee.Application.addComponent(Application.java:253)
 at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:144)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:301)
 at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:255)
 at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:206)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:716)
 at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:698)
 at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:380)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:902)
 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:480)
 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:208)
 at $Proxy34.updateDeployments(Unknown Source)
 at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:3724)
 at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1584)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:337)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:233)
 at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:852)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:273)
 at weblogic.Server.main(Server.java:33)
Where i went wrong?
Thanks in advance
phani

Hi ,
I have the same problem .when i look into JNDI tree view the jndi name is listed. but it saying error below listed.
my
ejb-name:=containerManaged
datasourcename=EX_DataSource
jndi-name=EX_JNDI
<Feb 14, 2005 3:10:08 PM IST> <Error> <Deployer> <149231> <The slave deployer was unable to set the activatio
true for the application EX_Container
weblogic.management.ApplicationException: activate failed forEX_Container
Module Name: EX_Container, Error: Exception activating module: EJBModule(EX_Container,status=PREPARED)
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
TargetException:
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1093)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1022)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLife
ava:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
my weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>containerManaged</ejb-name>
<entity-descriptor>
<persistence>
 <persistence-use>
 <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
 <type-version>7.0</type-version>
 <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
 </persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>EX_JNDI</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
weblogic-cmp-rdbms-jar.xml file
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>containerManaged</ejb-name>
<data-source-name>EX_DataSource</data-source-name>
<table-map>
<table-name>ejbAccounts</table-name>
<field-map>
<cmp-field>accountId</cmp-field>
<dbms-column>id</dbms-column>
</field-map>
<field-map>
<cmp-field>balance</cmp-field>
<dbms-column>bal</dbms-column>
</field-map>
<field-map>
<cmp-field>accountType</cmp-field>
<dbms-column>type</dbms-column>
</field-map>
</table-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>DropAndCreateAlways</create-default-dbms-tables>
</weblogic-rdbms-jar>
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>containerManaged</ejb-name>
<home>containerBN.EX.AccountHome</home>
<remote>containerBN.EX.Account</remote>
<ejb-class>containerBN.EX.AccountBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>AccountBean</abstract-schema-name>
<cmp-field>
<field-name>accountId</field-name>
</cmp-field>
<cmp-field>
<field-name>balance</field-name>
</cmp-field>
<cmp-field>
<field-name>accountType</field-name>
</cmp-field>
<primkey-field>accountId</primkey-field>
<query>
<query-method>
<method-name>findBigAccounts</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance > ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findAccount</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance = ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findNullAccounts</method-name>
<method-params>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.accountType IS NULL]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>containerManaged</ejb-name>
 <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EX_Container.jar</ejb-client-jar>
</ejb-jar>
pls lhelp me .
my email id: [email protected]
thanks in advance.
Sudhakar.M

Using DataSource with MS Access

is it possible to use the JDBC DataSource with MS Access? Should I download some .class to register with JNDI?

I've done it with Tomcat, but I've never tried to do it outside of a container. You sound like you want to do it without a servlet or J2EE app server engine acting as the lookup and pool. - MOD

How to set up Tomcat4.1.24 datasource with DB2?

Hi, Guys:
I try to set up datasource with DB2. I got a sample, but
I do not know exactly what some tags mean. Could anyone
who did this show me an example? Thanks a million!
For example, what is path? what is docBase? In
<Resource name="jdbc/DefaultDS", what is jdbc/DefaultDS?
I am using a servlet to call other java classes which
access database. How do I specify these in Tomcat?
server.xml:
<Context path="/test" docBase="test" debug="0"
reloadable="false" override="true">
<Resource name="jdbc/DefaultDS" auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/DefaultDS">
<parameter><name>user</name><value>scott</value></parameter>
<parameter><name>password</name><value>tiger</value></parameter>
<parameter><name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value></parameter>
<parameter>
<name>driverName</name>
<value>jdbc:oracle:thin:@<YOUR HOST NAME>:1521:<YOUR DB NAME></value>
</parameter>
<parameter>
 <name>maxActive</name>
 <value>8</value>
</parameter>
<parameter>
 <name>maxIdle</name>
 <value>4</value>
</parameter>
</ResourceParams>
</Context>
web.xml:
<resource-ref>
<res-ref-name>jdbc/DefaultDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Dear Rick,
The answers to all of your questions are on this page:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html
Enjoy.
Kind regards,
Allan

Cannot create a DataSource with MySql...

Hi all,
I'm trying to create a DataSource with WLS 9.1.
The DataBase I'm using is MySql 4.1.
I have copied the mysql-connector.jar in the "lib" folder of my domain, but when I try to target the DataSource to the Server I get an error that Mysql Driver class is not found.
Should I insert the driver somewhere else ? or should I add manually the file to the server classpath ?
Thanks
Francesco

Francesco Marchioni wrote:
Hi all,
I'm trying to create a DataSource with WLS 9.1.
The DataBase I'm using is MySql 4.1.
I have copied the mysql-connector.jar in the "lib" folder of my domain, but when I try to target the DataSource to the Server I get an error that Mysql Driver class is not found.
Should I insert the driver somewhere else ? or should I add manually the file to the server classpath ?
Thanks
Francescoedit the script that starts WebLogic. You will see a CLASSPATH definition
is constructed and applied to the WebLogic call. Add your jar to that
CLASSPATH.
Joe

Accessing a DataSource with a userid, password.

I am getting an SQL Exception with trying to create a database connection using a datasource with userid and password, I can log in to the database manually with the credentials but when I try to access via the datasource this is the error returned.
java.sql.SQLException: java.sql.SQLException: User: doug, failed to be authenticated.
<code>
//-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
// start getConnection
//-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
* Creates a new connection to the database
* @return the connection object
public Connection getConnection() throws Exception{
Context context = new InitialContext();
DataSource dataSource = (DataSource) context.lookup("JDBC-GSFP_ResourceTracker");
return(dataSource.getConnection("doug","root"));
} // end getConnection
</code>
Any Ideas,

Hi
When you created DataSource in Weblogic Admin Console, at one point, you will give all the db details like DB Host, port, sid and username/password. You can TEST the connection also right there. If it says success, thats it.
Now, on the java side, you do Initial context and do JNDI Lookup for that DataSource and directly get the DataSource. There is no need to pass again username/password from Java Side. Just use dataSource.getConnection() without any arguments.
public Connection getConnection() throws Exception{
Context context = new InitialContext();
DataSource dataSource = (DataSource) context.lookup("JDBC-GSFP_ResourceTracker");
return(dataSource.getConnection());
} // end getConnection
Thanks
Ravi Jegga

Migration of Datasource with routine's

Similar Messages

Maybe you are looking for