Modifying emulated DataSource 3.x

Hello,
I'm working with SAP BW Netweaver 2004s, and I have a DataSource 3.x with an InfoPackage and a Transfer rule. I need to add some fields into DataSource 3.x, but when I tried to change to Modify View of the DataSource appears a message telling me that a DataSource 3.x is only be able change updating the Transfer rule, and ask me if I want to update it.
What Should I do to modify the DataSource 3.x? What is that I must modify first?
Thank you
Cris.

Hi Cristina,
the DataSource and the transfer structure are objects from the source system.
What you want to do? Why you want append a field?
1. When you want append a DataSource. Then this mean: you want deliver a field from source system. Then you must fill it with data. You must extent the coding in the R/3-System. The new data are saved in the database of the R/3-System, you must read it from there.
2. Or you want transform the received in the BW-System. Then extent the communication structure (in infosource maintain screen: the upper table). Then you can do your coding in the transfer rule or update rule.
Sven

Similar Messages

Migration of emulated datasource from 3.5 to BI 7

Hi Experts,
    For a requirement I want to migrate a emulated datasource 0material_attr   to bi 7.Previously some one already developed complete dataflow in 3.x, now i need to migrate every thing in bi 7.In order to make sure do i need to follow any sequence for this migration ( means first transferrule and then updaterule and then datasource) or I can directly migrate datasouce in BI 7 and then create transformation.Please any body suggest me.
Thanks & Regards
Vinod Kumar

Hi,
1.     Migrate all UpdateRules
Select the UpdateRule and press the right mouse button to get the context menu.
Choose u201CAdditional Functionsu201D and select u201CCreate Transformationu201D.
The UpdateRule is based on a 3.x InfoSource. The Transformation has to be created on a InfoSource (called u201CNew InfoSourceu201D ). A pop-up will ask you if you want to create a new InfoSource as a copy of the existing 3.x InfoSource. We need to have the new InfoSource, therefore choose u201CCopy InfoSource 3.x to New InfoSourceu201D and press enter.
2.     Migrate all TransferRules, for each relevant Source System Release
The migration of TransferRules is almost the same as the migration of UpdateRules. The main difference is, that you should not create a new InfoSource during the migration process. You have created the InfoSource already in the first step during the migration of the UpdateRule. Reuse the already existing InfoSource. Otherwise the link to the Transformation created before is missing.
Please have in mind that a transformation is source system dependent. Therefore the shadow table logic is the same as already known for the TransferRules. Be aware that you have to build a transformation pointing to a DataSource for each source system release which is needed (Basis release e.g. 620,640,700u2026) .
In order to perform the migration as described at the beginning of this chapter all TransferRules for the required SourceSystem relations must be active in the system.
3.     Migrate the DataSource. Make sure, that no TransferRule is still using the DataSource .
The migration of the DataSource is the last step which is needed to migrate the whole dataflow. Please make sure that not TransferRules pointing to this DataSource are still in use. How this can be done will be added later to the document.
TransferRules will be deleted when the DataSource is getting migrated. Choose the DataSource and select the Entry u201CMigrateu201D in the context menu.
4.     Test if everything is ok.
5.     Delete the UpdateRules and the 3.x InfoSource if the InfoSource in not used by still existing UpdateRules.
Best regards,
Frank

Updaing 2 schema's in 1 db = non-emulated datasource

When updating two databases from within a single tx, you must use a non-emulated datasource (i.e. JTA support is required).
Is this true of updating two database schema's (same database) in the same tx as well ? The Oracle documentation seems not to discuss this.
Regards,
Manoj.

Manoj -- My apologies. I misread the question. If you reference another schema but only use a single data source definition then it is a 1 PC. You only need to configure 2 PC if you will be creating transactions across two different data sources and you want true 2 PC semantics. In fact, I'm not sure if in the pure Oracle database view of the world you wouldn't have to do the same thing but it has just been a while since I looked at that. Don't forget that you can also use basic database mechanisms like synonyms and views to reference the other schema.
Thanks -- Jeff

Emulation Datasource

hi
I am a bit confused with term EMULATION.
In help doc
If the 3.x DataSource already exists in a data flow based on the old concept, you use emulation first to model the data flow with transformations and data transfer processes and then test it. During migration you can delete the data flow you were using before, along with the metadata objects.
In the above statement: you use emulation first to model the data flow with transformations .
Here i am in 7.0 version and using 3.X features. Now i want them to convert into 7.0 by doing transformations. I am on dev server, transferrules, updaterules, transfer structure exist for the datasource.
Can anyone tell me in simple terms what is the meaning of emulated datasource Q2. what is emulation and purpose of emulation?
Q3. How can i achieve perfect migration by using emulation?
REgards
Annie

Hi Annie,
Emulation of DataSource enables you to create Transformations & DTP for a 3.x (R3TR ISFS) DataSource, without migrating it to the 7.0 (R3TR RSDS).
Meaning of Emulation: You can use error stack with an emulated DataSource. In general, migrating to the new DataSource form ensures you have completely moved to the new dataflow concept in a consistent manner. The new dataflow has good advantages from a performance standpoint, in that you can parallelize the data load. The error stack is a big advantage from a data quality standpoint. The overall approach using DTP's is a step forward in that the dataflow occurs in a more transparent manner in process chains and monitoring.
More on it, you dont have to Migrate the DataSource so the existing UR & TR are not requierd to be deleted.
Please read below on Migration(3.x to 7.x) & also restoration(7.x to 3.x) of DataSources.
Migration: -
When a DataSource 3.x (R3TR ISFS) is migrated, it is deleted and transferred to the DataSource (R3TR RSDS).
The dependent 3.x objects mapping (R3TR ISMP) and transfer structure (R3TR ISTS) are deleted, if they exist, (R3TR ISIP) and the PSA with requests that have already been loaded are transferred into the DataSource. The 3.x objects can also be exported as part of the migration process. This means it is possible to recover the metadata objects DataSource 3.x, the mapping and the transfer structure.
Restoration:
It is only possible to recover a DataSource 3.x if it was migrated with export. This allows the objects DataSource 3.x (R3TR ISFS), mapping (R3TR ISMP), and transfer structure (R3TR ISTS) to recover the same status as they had before the migration.
During the recovery the DataSource (R3TR RSDS) is deleted. The system tries to retain the PSA. This is, however, not possible if the PSA was initially generated for the DataSource because either there was no active transfer structure for DataSource 3.x or it was loaded using IDoc.
The dependent objects transformation (R3TR TRFN), Data transfer process (R3TR DTPA), and InfoPackage (R3TR ISIP) are retained. If you want to delete them, you must do this manually.
Thanks for any points you choose to assign.

How to delete modified version datasource

I have a datasource in M version and A version. I am getting datasource activation error in BI 7.0
Please let me know how to delete Modified version.
Thanks
Liza

I removed a field from LO datasource 2LIS_11_VAITM , activated, tested successfully in R/3.
I replicated the datasource successfully in BW. But when activate the data source I am getting short dump ST22 ,the error message is " The ASSERT condition was violated". I am BI 7.0.
BW side in datasouece I found a not equal to sign ( which means M version is not equal to A version) and datasource is inactive.
ST22 -
Short text
    The ASSERT condition was violated.
Error analysis
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
Thanks
Liza

Configuring Non-emulated dataSources

I have try to configure a non-emulated data source because my emulated data source complains about open connections (see earlier posting), but when I start up the server it throws an exception:
DataSource logwriter activated...
java.lang.ClassCastException: oracle.jdbc.pool.OracleXAConnectionCacheImpl
at com.evermind.server.Application.initDataSource(Application.java:1360)
at com.evermind.server.Application.initDataSources(Application.java:1842
at com.evermind.server.Application.preInit(Application.java:388)
at com.evermind.server.Application.setConfig(Application.java:126)
at com.evermind.server.Application.setConfig(Application.java:111)
at com.evermind.server.ApplicationServer.initializeApplications(Applicat
ionServer.java:1316)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.jav
a:1087)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLa
uncher.java:65)
at java.lang.Thread.run(Thread.java:484)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:47)
My data-sources.xml file contains the following:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE data-sources PUBLIC "Orion data-sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
 <data-source
 class="com.evermind.sql.OrionCMTDataSource"
 name="OracleDS"
 location="jdbc/OracleCMTDS1"
 connection-driver="oracle.jdbc.driver.OracleDriver"
 username="sym"
 password="drive"
 url="jdbc:oracle:thin:@eureka:1521:sym"
 inactivity-timeout="30"
 />
</data-sources>
Also in the example in the spec no ejb-location or xa-location is defined for the non-emulated data source, are these required.
My bean transactions are container managed.
Thanks in advance

Hi Paul,
What's an "emulated data source"?
The only things I changed in the "data-sources.xml" file were the "username",
"password" and "url" attributes -- and I am using the default "data-sources.xml"
file that came with my copy of OC4J version 1.0.2.2 (which I run on a
SUN Solaris 7 with Oracle 8.1.7.2)
Despite the portability claims, I don't think that Weblogic apps can
be ported unmodified to OC4J.
Unfortunately I can't offer anything else because of the lack of information
you have supplied. What environment are you using and what are you trying
to do?
Currently I have successfully deployed and executed a J2EE application
(to OC4J -- version details above), consisting of a java client that
modifies the database via a BMP entity bean.
I can only suggest that you look at the following web sites which
may give you some more insight into how to develop, deploy and execute
J2EE applications using OC4J (not in any particular order):
http://www.atlassian.com
http://www.orionserver.com
http://www.orionsupport.com
http://www.elephantwalker.com
Good Luck,
Avi.

Does DTP work on emulated 3.x DataSource

I wanted to know if a DTP can be used to transfer data from an emulated 3.x datasource to say an ODS or cube.
Thanks

Yes and below is the rationale..
You want to evaluate the new loading method in your project and you use the emulated DataSource, that is, the DataSource has not yet been migrated and it is displayed as a 3.x DataSource.
As a prerequisite you have already created a new transformation that links the DataSource to the target. It is also assumed that you want to write the data from the PSA to the target in delta mode, meaning that not all data in the PSA should always be transferred by Data Transfer Protocol (DTP) but only the newly added data.
First phase: Creating a DTP
You define and activate a delta DTP that links a particular DataSource to a particular target. At this point, the source/target combination is no longer available in an InfoPackage. If an InfoPackage had transported data to this target from the DataSource concerned, from now on you can no longer select this target in the 'Update' tab page. The corresponding checkbox is not ready for input.
Second phase: Data transfer using DTP
You transfer data from the DTP into the target. Ensure that the system only reads the PSA requests that were not already transferred using the InfoPackage.
Third phase: Resetting the DTP and switching to InfoPackage
If you are not satisfied with the results of the data transfer using DTP, you can switch back to the previous loading method:
1. Delete all delta requests in the target that were transferred using DTP. This is a prerequisite for the next step.
2. Delete the DTP (this is a prerequisite for the next step).
You do not have to delete the transformation.
3. Enter the target in the 'Update' tab page of the InfoPackage
4. You can use the InfoPackage again to load data.
If you want to change to DTP again, continue with the first phase.
A future Support Package provides better support for the migration described above in the UI. You can also change to the loading method using the InfoPackage without deleting data from the target
Note 920644 - Date store with emulated DataSource: InfoPackage/DTP
Hope it Helps
Chetan
@CP..

Specific Datasource in a source system : how to modify the delta process ?

Hello,
I have a specific datasource in a Sap CRM5.0 system that sends sales data by year and Business Partner to a Sap BI7 system.
The Delta Process used (AIE After-Images Via Extractor (FI-GL/AP/AR)) do not manage the deletion : if you delete the 2009 sales data for a Business Partner, these data won't be in the CRM system anymore, but they'll remain in the Sap BI7 system after the delta.
My client would like to change the delta process to send the deletions in CRM to BW.
In CRM, when i use the RSA2 transaction, i can display the delta process, but apparently, there's no way to modify it
Moreover, the RSA6 and RSO2 transactions are usefull to modify my datasource, but not directly its delta process.
I found the RSOOSOURCE table where i could manually modify the delta process for my datasource, but it doesn't seem right to do it that way.
Can anyone help ? Is there anyway to modify the delta process for my datasource ? Or will i have to create a new one ?

You have to create new one
check these links
Changing Delta Process of DataSource
Changing Delta Process Type
Rgds
sateesh

How do I create an Emulated 3.5 DataSource in BI 7.0?

Hi everyone!
Can anybody please instruct me how to create the 3.5 DataSource in BI 7.0?
Thank you!
Philips Manalaysay

Hi,
Emulated datasource is not a type of DS. It is indeed a 3.5 datasource which you view with BI 7 Interface by using display option from the context menu of a 3.5 DS.
Creating a BI 7 DS:
Goto the datasource tree in the data warehousing workbench. Select the appliation component and from the context menu, choose create datasource of your choice (standard, web service).
Thanks

Problem in updating datasource in 3x flow

I have a 3x flow and made the datasource via infosource. Transfer rules are made but the problem is that
when i try to modify the datasource for flat file inclusion (path of ff) it is not taking and is showing that i have to come through transfer rule maintenance interface. I am getting this.....kindly help

Hi,
Since you are using the 3.x dataflow, make the changes in the appropriate infosource in RSA1old. Then save and activate the infosource. This should do the trick.
Regards.

Datasource activation in BI

Hi Experts,
We have issues in activating the datasource after transport. It works fine as expected in dev and test environment but it's not active in BI production environment.
We tried to execute ABAP report RSDS_DATASOURCE_ACTIVATE_ALL to activate the datasource in BI but we are getting error if we run this in dialog mode
1-
DataSource could not be activated Message no. RSDS106
2-
Error when resetting DataSource Message no. RSO410
and no error if we execute the same report in background. finally our datasource in still inactive.
Any suggestions will be greatly appreciated.
Thanks

Hello,
Is the DataSource 7.0 version or emulated datasource.
Can you please make sure the replication has been done, and also it would be helpful if you can let us know what exactly is the process you are following in terms of what are the contents of the transport.
Where is the datasource mapped to, any special code you put in place for routines and so on.
Thanks
Dharma.

DataSources in BI 7.0

Hello All,
We are just beginning to implement a BI solution in our landscape and would like to know the following:
1) Which DataSource should we be using 3.x or 7.0? What are pros/cons of using one over the another?
2) I replicate 0PLANT_ATTR datasource and BI shows that as an Emulated 3.x datasource. Is that by default or is there some way I can replicate that as a 7.0 datasource (without having to migrate the replicated 3.x datasource in BI)? I read some posts where during replication you have an option of chosing 3.x or 7.0 replication but that option does not seem to show up in my case.
3) If I have to migrate the replicated ds, is there any downside to always migrating it "With Export"?
Thanks,
Asheesh

Hi,
1.Actually if there are 3.x data sources available its the best practice to use them.
2.An emulated data source means
3.x DataSources (object type R3TR ISFS) exist in the BI database in the metadata tables that were available in releases prior to SAP NetWeaver 7.0.
The emulation permits you to display and use the DataSource 3.x using the interfaces of the new DataSource concept. The DataSource (R3TR RSDS) is instantiated from the metadata tables of the DataSource 3.x.
You can display a 3.x DataSource as an emulated DataSource in DataSource maintenance in BI. You can also model the data flow with transformations for an emulated DataSource if there are already active transfer rules and a transfer structure and a PSA for the 3.x DataSource. Once you have defined the objects of the data flow, you can set the processes for data transfer (loading process using InfoPackage and data transfer process), along with other data processing processes in BI. We recommend that you use process chains.
Emulation and definition of the objects and processes of the data flow that are based on the emulation in accordance with the new concept are a preparatory step in migrating the DataSource.
If you use an emulated DataSource 3.x, note that the InfoPackage does not use all of the settings defined in the 3.x data flow because in the new data flow it only loads the data into the PSA. To prevent problems arising from misunderstandings about using the InfoPackage, we recommend that you only use the emulation in development and test systems.
Using Emulated data sources
http://help.sap.com/saphelp_nw70/helpdata/en/42/fda7cf2a5f517be10000000a1553f6/frameset.htm
Migrating 3.x DataSources
1. In the original system (development system), in the Data Warehousing Workbench, choose Migrate in the context menu of the 3.x DataSource.
 2. If you want to restore the 3.x DataSource at a later time, choose With Export on the next screen.
 3. Specify a transport request.
 4. Transport the migrated DataSource to the target system (quality system, productive system).
 5. Activate the DataSource in the target system.
Migrating 3.x DataSources (UD Connect, Web Service)
http://help.sap.com/saphelp_nw70/helpdata/en/42/fda7cf2a5f517be10000000a1553f6/frameset.htm
Hope this helps
Regards
Karthik

DataSource - difference between ejb-location and location

Hi,
Does anyone know difference between ejb-location and location attribute specified in datasources.xml for an emulated datasource.
There are few connection leakage errors reported in log files though the connection and other database objects have been closed in finally block in all places.
So just wanted to find out whether specifying the same value for location as well as ejb-location is not the root cause of connection leakage errors.
Thanks in advance for any help.
Regards,
Smita

Smita,
Personally, I think you should make sure that all locations (in your "data-sources.xml" file) should be different -- although I can't tell you why.
According to the documentation, the "ejb-location" uses a connection pool and I exclusively use the "ejb-location".
Good Luck,
Avi.

Modify selection data in an infopackage

Hi:
I have to add a field into the data selection to make an initial delta load. When try to check the new field by transaccion RSO2 in my source system they appear all de fields disabled.
Do I have to make this modification by other transaccin? Or do I have to delete the infopackage in order to modify the datasource?
Any clue will be great!
Points for helpfull answers

Is your Datasource is custom Data source or Standard..?
If its custom datasource then goto RSO2 change mode from there you shud be able to change the selections..
In order to make changes your user name shud be registered as Developer, other wise it wont allow you to change and you can only see display mode.
Jagadeesh

Datasource 2LIS_04_P_MATNR inactive

Hi Experts,
We changed a data flow with DSO instead of Cube. I have created a DSO with Datsource 2LIS_04_P_MATNR and it was good. While creating, I have activated update rules which was not required in 7.0 flow. So I deleted that DSO and while deleting deleted the update rules and transfer rules for the datasource 2LIS_04_P_MATNR in Dev and released teh request to Quality. Now I see the datasource 2LIS_04_P_MATNR inactive in Dev and there are no infopackages under it. When I try to create infopackage , it says, No active transfer rule for DS 2LIS_04_P_MATNR and source system DU6CLNT010; create first... How to go about this and activate datasource? Or if I transport the request backwards from Quality to Dev, will it work? Please advice.
Thanks,
Chandra.

Hi Vidya Sagar,
Thanks for your response. It's a 3.x emulated Data source, now when I try to create Info package, it pops up a message :
No active transfer rule for DS 2LIS_04_P_MATNR and source system DU6CLNT010; create first...
If so , how to create transfer rules for an 3.x emulated Datasource, I didn't experience this? Kindly do suggest?
Thanks,
Chandra.

Modifying emulated DataSource 3.x

Similar Messages

Maybe you are looking for