Infosource in BI 7.0 EPH1 - Source to BI

Are company is starting a new install of BI 7.0. We currently have a 3.5 instance as well. I have heard two different arguments when it comes to infosources in BI 7.0 from source to BI. Some people say yes use infosources and other people say no don't use infosources.
Do you know what SAP suggestions is?
Also,
Your insite would be greatly appriciated????
Thank you!
Caroline

Hi,
It depends on the requirements.
1. Let you are having more than one datasource & you are loading data to more than one Infoproviders , in this case you have to keep a Infosource in between datasources & Infoproviders.
2. In normal dataflow(datasource->Infoprovider) it is not required to keep an Infosource. Infosource is optional in this case.
3. When you will install BI Contents, infosources will come in the data flow. Depend on your requirement you can use them.

Similar Messages

Error Infosource is not defined in the source system

I am extracting data into ODS. It was running perfectly till now. But today i am getting this error.and for all packages i run. whether it is transaction data or master data.
I replicated the DataSource and activated all the objects and transfer structure.but still getting the same error.
I even created a new DataSource and infosource but still the error persists. please help me in this matter.
Thanks

the data is extracted from BW system itself (Self System).
there are three tables linked to each other.I have created an infoset query and creted datasource on that infoset query.
the source system is the same bw system.
The detailed error report is -
InfoSource is not defined in the source system.
Message no. R3005
Diagnosis
The InfoSource specified in the data request, is not defined in the source system.
System response
The data transfer is terminated.
Procedure
In the Administrator Workbench of the Business Information Warehouse, update the metadata for this source system, and delete the InfoPackages belonging to InfoSources that no longer existing .

InfoSource is not defined in the source system

Hi,
We are getting error 'InfoSource is not defined in the source system' while extracting data from Planning book to Cube in APO.
Data is coming up to Extrack checker ( RSA3 ) but not comming to PSA.
Please help me.
Thanks
Subba Rao

Hello Subba,
Have you replicated the datasource on the BW side? If you use the 3.x data flow then you also need to assign the datasource to and infosource.
Best Regards,
Des

Infosource it's not in transformation source list

Hi, i'm trying to create a transformation from an infosource (0co_om_cca_1) to an infocube (0cca_c11), but when i display the list of sources availables in the create transformation window, the IS it's not there, if i type it manually says "Source TRCS 0CO_OM_CCA1 not active", if i go to RSIS table i see that the IS has the 2 records 1 for D version and 1 for A version, so it's active!!
in another thread i read that maybe it's because the IS it's in 3.x version, well in my case my source system it's the r3 r.1h so the BI content it's in 3.x version.
please help!!

Hi Sergio
Check the info source 0CO_OM_CCA1, if there is a small box infront of it or not. I suppose there should be one. It means the Info source is in 3.x version and you can not create Transformation for the info source.
What you can you do is to create the whole data flow in BI 7.0 and create the transformation directly from Data source.
Regards,
Kams

Infosource is not defined in source system.

Hello Expert,
We have problem on data upload. The Infosource is ODS object generated. Now through RSMO, message is:
Infosource 8* is not defined in source system.
How to re-define/active this type infosource? Is there any impacts?
BTW, days ago, it ran very well.
Thanks
XY
Edited by: xy chen on Nov 14, 2008 11:47 AM

Hi,
I am also facing the similar error, whne uploading data from an ODS to further data targets.
I did follow th instructions advised, and I tried searching in the Service Market Place with the term,
" " Infosource is not defined in source system " " but couldnot find any correction notes.
Could you let me know the notes, you followed up to resolve this issue,
Thanks in advance,
Cheers,
Neela

Inconsistent Dev System: Infosource assigned to incorrect Source System

Hello all
Our Development box contains inconsistent assignments of infosources to source system.
When I compare the dev, quality and production boxes I find:
> Quality and Prod are consistent and all infosource systems are assigned to correct source systems - all loads execute as expected.
> However I find ips defined in the process chains in Quality and Production under incorrect source systems in the Development box.
> Also, the inconsistencies are varied for ex: SALESORG_ATTR is assigned to source system Y, while SALESORG_TEXT is assigned to source system X, while 0CUSTOMER_ATTR is assigned to source system Z ( where Z is the correct source system).
I have not been able to figure what lead to this inconsistency except that I am aware that there were plugins installed and some refreshes done followed up by BDLS.
I did try having BASIS execute BDLS to convert all logical systems X to Z ( but there were errors in the log stating that destination Z already exists - which is correct since for ex 0CUSTOMER_ATTR is assigned correctly to source system Z)
I was considering the following to rectify this situation:
1> Make the rectifications manually
1a> Identify all the infosources in all the process chains in quality/production
1b>Manually reassign all infsources/datasources to the right source system
1c>Check all the mapping rules (transfer rules) and ensure they are same as quality/production
1d> Activate the transfer rules
1e>Create infopackages
1f> Transport the ips to quality and reassign them to the process chains.
> This is a very labourious task and invovles high risk due to manual effort
2> Refresh from quality into dev
2a> Recreate the transport routes
2b> Resynchronize all the loads with the R3 dev box
> This would cause loss of version history and therefore not recommended by SAP
3> Rollback to a restore point
3a> We would need to find whether we maintain a restore point in the past before which the system were consistent.
3b> Reimport all the transports from the restore point till date
4> Rerun BDLS
4a> This might involve deleting all occurences of source system Z from the dev box
Please advise what would be the best approach / if theres a better way to address this issue.
Thankyou
Edited

Hi,
Goto RSA1 in yy BWQ system.
In the Menu ---> Tools ---> Mapping of Source System Names ( Shift + F6)
Change the Target Source System as BWP server.
Now move the transport to BWQ. Your BWP will be assigned as source system.
Regards,
Balaji V

Transport InfoSources to New Source System

Hi.
When implementing BW in our QA environment, all InfoSources, and their related InfoPackages, Transfer Rules, Update Rules, etc.) were created using a temporary R3 QAS source system mapping (ex.TMP). We are now removing this temporary client and I now need to change my InfoSources (along with customized Start Routines, InfoPackages, etc.) to point to a new QAS source system (ex. PRM).
Note that this new source system is already identified as a source system for BW and all DataSources created on TMP have been transported to PRM. Subsequently, all DataSources have been replicated from PRM to BW.
However, I'm having trouble on the BW end. I can't easily
transfer the InfoSources, etc. to the new source system. I've asked some BW / Basis folks and they suggest transporting the InfoPackages out-of and then back-into the BW QA client. Is this possible? Is there a better way to push my InfoSources, InfoPackages, etc. from the old source client (TMP) to the new one (PRM)? Thanks!

Dear Dave
Please do not attempt to change the logical system name your self, as I feel that you have not tried it before.
This is some thing that your basis people have to do. Depending on the size of database this change can take from 2-24 hours (not exact times, but just some thing to show the magnitude of the task).
Good luck
/FZA
Message was edited by: Fariborz Zangoui

Error while transporting data source

Hello Gurus,
I am trying to transport a DSO, Data source, Transf, DTP in the same request but i am getting error code 8.
Here is the error log.
*Start of the after-import method RSRSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mod
InfoSource ZBIU_OTCSO_TR_VMI_ORDDEL is not available in source system PW2CLNT501
Error when activating DataSource ZBIU_OTCSO_TR_VMI_ORDDEL PW2CLNT501*_
Source system is BI source system and data source is based on a function module which have logic to get data from other DSO's and IO's with BI system.
Why its giving me an error saying Infosource no available in SS when i am transporting.
Did anyone came across similar issue? Any suggestions?
Thank you.

1)Check this infosource ZBIU_OTCSO_TR_VMI_ORDDEL flow in Dev system, where it is been used.. and also check the code in the FM.
2) IF you are trasnporting entirely a new data flow then goto transport connection and check.
3)If you are trasporting the existing flow(may not be entire flow, but like Datasource enhacment ..) cross check with PRD system for the earlier version and chek what are the changes which you are tying to do now.
2)check your Trasport request once again(collected objects)..Activate the FM, DS and then transport.
Hello YJV,
Its a new data flow from DEV to QA and i checked for that infosource in transport connection and there are no hits for that infosource. I found it only in the case of Datasource.
I doubt on the conversion of SS names. Can anyone tell me how I can validate the conversion of Source Systems.
Any suggetions?
Thx.

Transporting Process Chain - error Source system does not exist

Hi,
I tried to transport a local PC by itself (not including its main meta chain) since I have only done modifications in the local PC only. In the PC, there are PSA Processing, ODS Processing, ODS Activation, ABAP Program w/ variants and Infocube Rollup.
However, I got the following transport error: Source system does not exist
=======
Diagnosis
Source system is not known.
System Response
The imported data for DataSource was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
Procedure
Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
You get to maintenance using Tools -> Conversion of the logical system names.
============
I have checked at the table RSLOGSYSMAP and all source system mappings are in order.
And the weird thing is, upon checking the PC itself in the transport-to box, I can activate it without any error.
FYI, we are currently upgrading to BI Accelerator. Am not sure if this could be one of the reasons.
Any inputs and tips are highly appreciated and will be rewarded with points accordingly.
Thanks

Hi,
This error is due to the fact that the
mapping table for the after import (RSLOGSYSMAP) is not correct maintained in PB7 system.
You need to maintain table RSLOGSYSMAP in each system
You can find the steps to do it in the attached note 127326:
o Maintain table 'RSLOGSYSMAP' in the target BW with view
   'V_RSLOGSYSMAP' and enter as 'original source system' the logical name of the source system in the source BW and as 'target source system' the logical name of the source system in the target BW.
   This maintenance is required since it allows the correct source system reference of the InfoSources to be transported.
This source system reference in turn is absolutely necessary to activate the transfer structure.
   Example:
   Source BW with source system AAA.
   Target BW with source system BBB where the source system AAA
   corresponds to the source system BBB.
   Entry in RSLOGSYSMAP in the target BW:
   Original source system: AAA, target source system: BBB.
   Give the DDIC user in the source BW in client 000 the
   authorization profile S_RS_ALL to create BW objects.
Cheers
Rajesh

BI 7.0: How to bring DataSource fields to InfoSource in design

We've replicated the generic datasource from R3 to BW and we have created an InfoSource with blank fields. We remember on BW 3.x version that we could bring Datasource fields to InfoSource by clicking somewhere, but on BI 7.0, we are trying to do the same thing, but can't find some function to do this. Then we try to right click the InfoSource and then select 'Create Transformation', and then to select the source system and the datasource, but of course we would get the error msg like "There are no fields in target TRCS InfoSource_Technical_Name". Any idea on how to bring Datasource fields into the blank InfoSource on BI 7.0?
Thanks!

Hi,
Instead of bringing the DS fields into a blank infosource, ideally, what you can do
is, you can create a new infosource based on your generic data source, which would make your process easy..
cheers,
Pattan.

After transporting I get error "source system does not exist"

Hello all,
I have transported my objetcs to BW quality system and transported the data sources to r/3 quality and everything went fine. But now when I am trying to go through everything my update rules are inactive and when I get to infosource it gives me this error
"Source system ERJ100 does not exist."
Is there any importamnt step that I am missing why are the objects not recognizing the source system?
Thanks,

hi,
check the system mapping in rsal tools system mapping tab as lilly mention. check if the mapping is defined correct. see the link below
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e883de94-0501-0010-7d95-de5ffa503a86
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Might help
Thank you
Qandeel

Generic Data Source Creation Problem....URGENT!!!!!!!!!!!!!

Hello BW Experts...!
I need to create a Generic Data Source out of a table called VBSEGK... I was trying in the usual way with RSO2 , but when I press save button after entering the Table name the following error is coming:
" Invalid Extract Stucture Template VBSEGK of Data Source ZPARK_01"
and when I click on the error message its showing
Diagnosis
You tried to generate an extract structure with the template structure VBSEGK. This operation failed, because the template structure quantity fields or currency fields, for example, field DMBTR refer to a different table.
Procedure
Use the template structure to create a view or DDIC structure that does not contain the inadmissable fields.
VBSEGK is a standard table , so I cant change the Table structure. Can any one give me some idea of how to create Data source with this table ASAP ASAP please....
Please ask me questions if you didnt get this...
thanks

Hi Harish,
Please check OSS note 335342.
Symptom
The creation of a generic DataSource which is extracted from a DDIC view or a transparent table terminates with error message R8359:Invalid extract structure template &2 of Datasource &1
Other terms
OLTP, DataSource, extractor, data extraction, generic extractor
Reason and Prerequisites
The problem is caused by a program error.
Solution
The table or view used for extraction must have currency and unit fields within the field list of the table/view for all currency and quantity key figures.Otherwise the consistency of the extracted data cannot be ensured.To make the generation possible, check whether all key figures of your table refer to unit fields that are within the field list.If this is not the case, there are two possibilities:
1. A table is used for extraction.
Create a view in which you have a currency / unit field contained in the view for each key figure. The currency / unit field from the table must be included in the view to which the key figure actually refers.
Example:
Field WKGBTR of table COEP refers to the unit field WAERS of table TKA01. In a view that contains field COEP-WKGBTR, table TKA01 and field WAERS must be included in the field list.
If the currency or the unit a key figure refers to is not located in a table but in a structure, the key figure has to be removed from the view and read via a customer exit (see below). Structures cannot be included in a view.
ATTENTION!! Often the key of the table in which the referenced unit is located, does not agree with the key in the table with the corresponding key figure. In this case, the join condition of both tables is not unique in the view definition, that means for each key line of the table with the key figure, several lines of the table with the unit may be read: the result is a multiplying of the number of lines in the view by a factor corresponding to the number of lines that fit the key figure, in the unit table. To be able to deliver consistent data to a BW system, check whether the unit of the key figure in question should always have a fixed value. If yes then you can determine that in the view definition via 'GoTo -> Selection conditions'. If no, then you must proceed as follows:
a) Remove the key figure from the view
b) Define the DataSource
c) Enhance the extract structure by key figure and unit for each append (Transaction RSA6)
d) Add the key figure and the unit in a customer exit
2. A view is already used for the extraction
If it is not possible to obtain a unit of measure from a table on which the view is based, the unit field must be deleted from the field list.
A note in relation to the upward compatibility of BW-BCT InfoSources: BW-BCT 1.2B was not yet able to check units and currency fields. For this reason, it is possible that InfoSources which were defined in the source system as of BW-BCT 1.2B must be redefined as of 2000.1 in the manner described above. However, checks are absolutely essential for the consistency of the extracted data.
Regards,
Praveen

Naming of infosource- prefix 8

What is the significance of 8 as a prefix to infosource's technical name, apart from just a naming convention?
I searched a lot but couldn't get the answer...

Hi,
When the data flows within BW, say from ODS to ODS or ODS to Cube, the Infosource gets the name of the source ODS with prefix 8.
For Ex, consider the data flow.
ODS1 --> ODS2 ---> Cube1
The infosource name for ODS2 will 8ODS1
Similarly, the infosource name for Cube1 will 8ODS2.
These are called as Generated Objects ( Data Marts )
All the fields will be automatically mapped, unless you want some routine instead of Direct Mapping.
Regards,
Balaji V

Add new source system to BI

Hello,
Our requirement is to load data from a different R3 client to which we dont have a connection yet.
The idea is to create a new connection but keep the existing one.
Is there any automated tool to do this? We would like to avoid the manual creation of all infosources and transformations from the new source system, but to copy them from the existing one.
We found that there is a tool for replacing the current source system with another one (BDLS), but we just want to create this new one in paralel with the current source.
Thanks!!
Pablo

Hi,
what you can do is, create a transport request containing all source system related things like the infosource/datasource assignment, transfer rules... and import that transport back into your dev system. Before the import you should maintain the settings for source system after transport accordingly.
Siggi

BW 7.0 data source activation - transport?

Hi Folks,
I am a bit confused with BW 7.0 data source. I replicated from my APO system and the data source is created in BW as 7.0 -> I choose background activation.
When I want to create an infopackage for the infosource I tells me that data source is not yet active.
So I went in and activated -> asked for a transport.
Question: do I have to transport the data source / after it is replicated on the next system (TEST)?
Or should the data source be normally active right after the replication?
Best regards,
Axel

yes. we have to transport the data source replica in BW after it is replicated on the next system (TEST).

Infosource in BI 7.0 EPH1 - Source to BI

Similar Messages

Maybe you are looking for