[Ask] EDW & Source Systems

The shop where I am a player (in the PM team) is implementing a data warehouse migration from data center A to B.
Overall Landcape:
* There are multiple projects in flight in the DW ecosystem which must be unimpacted (to the extent possible) during the migration.
Overall Manadate:
"Preserve status quo during the migration (*) while not impacting user experience.. (* : no major reengineering efforts from DW context)
Current State:
* Large knowledge gap of the current infrastructure in data center A. No documentation. Lack of tribal knowledge. Shop is filled with vendors (via staff augmentation). Frequent attrition of full-time employees, contributing partially to the knowledge gap.
*ASK*:
Is there a comprehensive way, via a (semi-)automated tool (either at the app layer or network layer) to identify all the source systems from which data is pulled into the landing zone of the DW?
If not, what is a structured process to systematically accomplish this (without managing by "wandering around")?
Thanks for any feedback.

1. What is the Informatica query for determing all the source system connections (coming into the Landing Zone)?
2. How should one go about determining all the source systems in the current DW infrastructure?
What are other precision questions that need to be answered so that one can assess and determine the bandwidth requirements of a dedicated network pipe (*) that needs to be transport mechanism connecting the various source systems and the Landing Zone?
(* : in order to impact the corporate WAN)

Similar Messages

BW linked to two ECC source systems

Hi,
We are planning to create a sceneraio in whih our BW quality (client 350) will be linked to two different ECC clients (550 & 590).
Earlirer 350 was linked to 550 only.
Now the question is while transporting request from BW development (client 310) to BW Quality (350), will it ask the source system??
For which source sytem request will be transported, 550 or 590???
Pls. clear the concept.
Thanks in advance
Shilpi Gupta

Hi Shilpi,
It seems you are bit confused about the connection and the transport.Let me try to add some more points.
Your source system is ECCDEV (540) and the target source system is ECCQUALOTY (590) . Your BW Quality is 350.
BW quality is connected with two source system (590 and 550).
All your BW objects are source system independent other than Transfer rules. So whenver you transport any objects from BW development to Quality (like InfoObjects,InfoSource,InfoCube ,ODS,update rules etc) there is no problem with the source system connection. It just appears in your BW Quality .But your transfer rules is dependent on the source system. So when you transport the transfer rules,you need to make sure that which source system (Qty) should carry that changes i.e.transfer rule mappings.
So you need to maintain this settings in the above mentioned transaction code,even if you use only one source system.
Then only your transport changes will appear in your quality transfer rules.Even though your quality BW system is assigned to two source system ,only one system will carry that transfer rule mappings.Hence this mapping is required for any case.
You can change the mapping anytime (from 590 to 540) using this tcode to get the transfer rule mappings for the other system.
Thanks.

How to design EDW for source systems from different Time-Zones

How to design EDW for source systems from different Time-Zones?
Suppose IT landscape has a global BW in New York, and source systems in americas, europe and asia, then how the time-zones effect on time related things like delta selections on date or timestamp etc.

As you said BW is global in NY, your source system must be global too. People from various locations can connect to same source system and thus timestamps for delta is always maintained as 1 single time. We have same scenario in our project. Our R/3 system is used by users in US and Europe. So we run deltas twice in day to make sure we got deltas from both locations.
If scenarios was such that all locations connect to separate R/3 system, then obviously you have multiple queues. That is unique delta queue for each source system so deltas will be pulled as per data in respective queues.
Abhijit

Create SAP Source System Failed

Hi all,
We are using NetWeaver 2004s BI and try to connect to ECC 5.0. I tried to create SAP source system but got error message saying "RFC user logon failed". When I check RFC destination in ECC 5.0 for BI, the test connection is ok, but the remote logon will pop up another logon screen asking for id and password. I am pretty sure that the id and password in RFC destination is correct. The RFC destination in BI is ok. Can you help me out with this? Thanks a lot in advance.

Hi,
Check the Default Logon Client for ECC 5.0
and verifiy that the User is in the Same Client
Each RFC destination has a mapped user for specific Client..Check the Client and User in the same client
regards
Happy Tony
Message was edited by: Happy Tony

Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_

Hi All,
can any one help on this issue.
I run the BI statistics in production and found out the error while triggering the delta's
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Error msg : Job terminated in source system --> Request set to red
Message no. RSM078
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS = BCLNT300
REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE = D
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 2147483648 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000320 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
But delta laoding for same is working in DEV...but not in prod...
Please suggest
Regards
Shweta

Swetha
finally found out the notes.
Please look into them and ask you basis to implemnt,
1161940
1106569
1145041
1146851
Please have a look and ask for implemtation in your system which are suitable for you
We also faced the same issue job termination in source system for BI Statistics
Regards#
Srini

Source System Error While transporting

Hi SDN,
We are transporting requests to a deployment test box SN1 and we are getting this error message while we never got this error message transporting to QAS and in QAS we did not need to create DEV010 as a source system - setting up RFC connection was sufficient.
Any thoughts?
===========================================================
Source system DEV010 does not exist
Message no. RSAR409
Diagnosis
Source system DEV010 is not known.
System response
The imported data for data source 8ZM_C42 was deleted again as the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP to an available productive source system.
Procedure
Create the referenced source system in the Administrator Workbench or define a mapping to a known source system in table RSLOGSYSMAP.
You get to the maintenance using Tools -> Conversion of the logical system names.

Speak to your basis team and ask them to make entries in table:
RSLOGSYSMAP .
Are you trying to transport info source or any source system dependt object? If so, this error is understandable.
This has been discussed several times and pl search the forum.
Ravi Thothadri

How can i create source system in BI

Hi gurus,
I am using BI 7.0, its SRM addon.
in that i used source sytem sub functional for creating flatfile.
there i got folder like BI, SAP, EXTERNAL SYSTEM, FILE, DB CONNECT, UD CONNECT, WEBSERVICE.
so i trying to create PC souce sytem by right click on FILE folder,
it popups window with
Logical system nae---i have given current client
type and release---What is that?? which one i have to select...it shows as ORA, TLF, XPD.
I dont know for flat file source sytem why they are asking the above stuff, even we select ORA it shows error as "source system has same name as BI"
pls hep me out on creation of the source system'
pls reply as early as possible
if anyone unable to understand pls tell me
Thanks in Advance

Hi Dae,
Thanks for reply, i will give points tp you, before that let me know the below one.
I am trying to load master data then Transaction data to cube from flat file.
For that I have created infoObjects, insource with those objects, and infocube.
now how can i give the connections in between them like as 3.X, let me know with steps for loading Master and transaction data to Cube.
Thanks in advance

Error while loading source system data

BW unknown in source system
The BW IDoc type ZSBA003 is not the same as the source system IDoc type
The following errors occurred in the source system:
EDI: Partner profile not available
Entry in inbound table not found
Entry in outbound table not found
Entry in outbound table not found

hi Steve,
check with transaction we20, if your bw myself source system exist under 'partner type ls' (ls = logical system).
it should exist with
outbound parameter
message type-RSRQST
inbound parameter
message type-RSINFO RSSEND
check also for r/3 source system
you may ask basis for help.

Error after restoring source system in SAP BI side

Dear all,
i am getting issue while restoring sap source system through sap bI
"Connection LA is used in the 'LD1CLNT010'
source system as a connection 'LB1CLNT400' to BW."
Do you want to delete this connection in the source system?
Connection Is Restored After It Has Been Deleted Successfully
it asked me delete or do not delete
what to do next

hi,
you need to ensure that source system to BW is restored properly .
check in TABLE RSBASIDOC in BW through transaction se11/se16.every source system entry must be here with repect to BW.
If source system entry is missing then there are issues.Normally BASIS Team makes entry.restores system
you cn also check in RSA1-->SOURCE SYSTEM.Here u must find your R3 system name.
hope it helps
thanks,
nilesh

Creating Source System in BW

Hi Friends,
We are using BI, i have to create a source system(R3) in BW.
Both sides we have users with enough profiles.
In RSA1 --> Source System --> Create is using to create the sourse system.
I am using automatic function at the time of defining the source system.
It is asking some dialog user from source side, i am giving some dialog user
then i am getting the error user cannot create in source system.
Could you please help me out.. how to create R3 source system in BI.
Thanks in advance
Srinivas

Hi Srini,
                Check u'r partner profiles.if u din't get....
plz follow this....
2.1     SAP R/3
2.1.1     Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu     Define Client Administration (SAP R/3)
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1.     Choose Display  Change.
2.     Confirm the warning message Caution: The table is cross client.
3.     Select your SAP R/3 client and choose Details.
4.     In the Change View Clients: Details screen, activate the following settings:
     Automatic recording of changes
     Changes to Repository and cross-client Customizing allowed
     eCATT and CATT allowed.
5.     Save.
6.     Go back to the SAP Easy Access menu.
2.1.2     Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1.     Define the systems as logical systems.
2.     Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code     SPRO
SAP R/3
IMG Menu     Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2.     Choose New entries.
3.     In the column Log System, enter a name for the logical system that you want to create.
4.     In the column Name, enter a description of the logical system.
Log. System     Name
where      XXX is the system name
and      NNN is the client.
5.     Save your entries.
A transport request for Workbench appears.
6.     Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7.     Select an existing request or create a new request, if necessary.
2.1.3     Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Assign Logical System to Client
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Choose Display ® Change.
3.     Confirm the warning message The table is cross client.
4.     Select your R/3 client and choose Details.
5.     Enter the name of the logical system of your SAP R/3 client.
6.     Save and confirm the warning message Be careful when changing the logical system.
7.     Choose Back twice.
2.1.4     Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Creating an RFC User (SAP R/3)
Transaction Code     SU01
SAP R/3 Menu     Tools  Administration  User Maintenance  Users
2.     In the User field, enter RFCUSER.
3.     Choose Create.
4.     On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type     System
Password     LOGIN
Profile
Profiles     SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language     EN
5.     Save your entries.
2.3     SAP BW
2.3.1     Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1.     To perform this activity, choose one of the following navigation options:
SAP BW Role Menu     Local Settings ® Define Client Administration
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Switch to change mode.
3.     Select your client.
4.     Choose details.
5.     In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6.     In field Client Role enter Customizing
7.     Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2     Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Defining a Logical System for SAP BW (SAP BW)
Transaction Code     SPRO
IMG Menu     SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1.     A dialog box informs you that the table is cross-client. Choose Continue.
2.     On the Change View Logical Systems: Overview screen, choose New entries.
3.     On the New Entries: Overview of Added Entries screen enter the following data:
Field name     Description     R/O/C     User action and values     Note
Log. System     Technical Name of the Logical System          Enter a name for the logical BW system that you want to create
Name     Textual Description of the Logical System          Enter a clear description for the logical BW system
4.     Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3     Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu     Assigning Logical System to Client (SAP BW)
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
1.     In the view Display View "Clients": Overview, choose Display.  Change
2.     Confirm the message.
3.     Select your BW client.
4.     Choose Details.
5.     In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6.     Save the entries and go back.
2.3.4     Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW     Modeling  Administrator Workbench: Modeling
Transaction Code     RSA1
1.     In the Replicate Metadata dialog box, choose Only Activate.
2.     If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5     Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Creating RFC User
Transaction Code     SU01
SAP BW Menu     Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1.     On the User Maintenance: Initial Screen screen:
a.     Enter the following data:
Field      Entry
User     RFCUSER
b.     Choose Create.
2.     On the Maintain User screen:
a.     Choose the Address tab.
b.     Enter the following data:
Field     Entry
Last Name     RFCUSER
Function     Default-User for RFC connection
c.     Choose the Logon data tab.
d.     Enter the following data:
Field     Entry
Password     LOGIN
User type     System
e.     Choose the Profiles tab.
f.     Enter the following data:
Field     Entry
Profiles     SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g.     Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6     Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu     Define RFC-USER as default (SAP BW)
Transaction Code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
1.     On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2.     In the Global Settings/Customizing dialog box choose Glob. Settings.
3.     On the Display View RSADMINA Maintenance View: Details screen:
a.     Choose Display  Change.
b.     Enter RFCUSER in the BW User ALE field.
c.     Choose Save.
Leave the transaction in order to activate the entries you have made.
3.3.2     Creating the Source System in the Administrator Workbench
Procedure
1.     From the SAP Menu in the BW system, choose:
SAP BW Role Menu     Creating the Source System in the Administrator Workbench
Transaction code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
2.     Choose Modeling.
3.     Choose Source Systems.
4.     In the right-hand window mark Source Systems.
5.     Choose the context menu (right mouse click).
6.     Choose Create.
Field name     User action and values
File System, Manual Meta Data, Data Using File...     X
7.     Choose Enter.
Field name     User action and values
Logical source system      FILE
Source system name     File system
8.     Choose Enter.
9.     Choose Back.

RFC destination BW could not be created in the source system R3073

I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
RFC destination BW could not be created in the source system message number R3073
Why is this happening? The connection tests just fine.
I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
Any ideas?
thanks

Hi,
I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
Create your BWDEV RFCDEST manually in your BWQA .
Perform test and authorization test within SM59 from both sys.
When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
hope this helps...
Olivier.

Creation of Source System

Dear all,
i am new to BI 7.0. can you help me how to create source system.

Hi,
You can actually create many type of source systems depending on your business requirements.
Go to RSA1 transaction in BI.
choose Source system. Depending on the type of system you require, right click and choose create.
then you have to follow the procedure it says.
As in case of SAP source sytem you have to give the R/3 system name/ID etc and user name/password to connect to and from R/3 system.
For this you have to maintain RFC destination to communicate to and from R/3 system to BI system. Then it will login to the R/3 system and will comeback to BI and start transferring matadata and BI contents from R/3, choose without dialog option when it ask you otherwise it will ask you every time it will transfer new object.
Assign points if it helps..........

Connecting SAP BW to SAP R/3 : Creating source system manually/automaticall

Hello All,
I have created the RFC connection between R/3 and BW system .The message types also have been defined and partner profiles have been generated.
When I am trying to create SAP source system in RSA1 --> Source system it asks me for the SAP Target server name, system ID and System number. After providing this it asks for ALEREMOTE users password in source system and target system.
Shouldnt this be blank!!!
Should this be provided separately by BASIS or shoudl it be the once we define while creating RFC Connections?
Kindly reply.
Regards,
NIKEKAB

Hello,
I used my user id to login. I recieved a message :
User already exists in source system I continue:
Anothre window pops up : "Check RFC connection" and it asks
'RFC connection already exists in source system . Do you want to check, use or cancel source system connection'
Here I select Use - but i get an error : Error in source system'.
how can i track down this error.
Kindly inform.
Regards,
Nikekab

Probelm in creating R/3 source system in BW 3.5!

Hi,
steps i did for the creation of source system in BW are as follows!
1) crated RFC destinations in each of the system (BW3.5 and R/3 4.7 IDES)
2) created logical systems in each of the systems and assigned the client to the respective logical systems
3) created back ground user in BW (Back ground user was already there in BW side, namely ALEREMOTE)
4) and in RSA1 screen when i attempt to create source system, it is asking for RFC destination and Logical system which i did . and after that, i am seeing neither the source name created nor any other next screen .
am i missing some thing here?
do suggest me the steps furthur for creating source system
Thanks,
Ravi

Hi Dinesh,
Thanks for ur reply!
now i did just as u told to me to do in automatic creation of source system!
i am getting the following info on the pop up window :
BW LS1 is already known T90CLNT090 in the source system
do you want to delete this connection in source system?
connection is restored after it has been deleted successfully
which option shud i use delete or dont delete?
if i am selecting "don`t delete" option iam getting the message as source system cannot be created with any of the proposed connections!
and i donno what wud be the effect if i select delete option!
pls suggest me on this !

Source system creation

hi experts,
this is the first time i am creating source system
i am have requirement to load data one bw system to another bi system,
so, to do that i defined and created logical system in bw for bi system and
i created same for bw in bi system also and everything is ok.
i guess my next step is to create source system(my self) for bw in bi .
when i am trying to create it is showing that it is already exists.and here what type of source system i need to choose. i am not founding any my self bw data mart
status symbol under source system creation node and what type of the source system i need to choose and whether it is manually or automatically.if i choose automatically it is asking create new destination ,create back ground user and connection of source system to bw (it is asking to fill all fields),for manual system creation only logical system and rfc destination. is it required to creat source system or not because my self bw data mart symbol is present in bw system and bi system also.please correct me if anything wrong
thanks
venu

hi chandra shekhar &chitrat,
thanks for your quick reply,when i choose sap business information symbol
it is asking to fill all the entries like crate new destination under this i provided
target computer in this i provided ip address of bi system( i am creating in bw system),system id & system number,and back groung user in source system and
password ,connection to the source system ,target system for back ground user
and connection to the source system what i need to provide
thanks
venu

[Ask] EDW & Source Systems

Similar Messages

Maybe you are looking for