ECC 6.0 Source Systems are added to 2 Different Folders - BI and SAP

Hi Experts:
                Our BASIS team added 2 ECC 6.0 Source Systems to BI 7.0. One of the ECC 6.0 System is added under BI Folder ( where DataMart Source stays) and other ECC 6.0 system is added under SAP folder where all other R/3 Source Systems are. I talked to BASIS team and they followed the same configuration in SM59 for both of the RFC connections.
Other peice of Information, Both the ECC 6.0 systems are on same server but just different Client.
This is how it looks:
RSA1 -> SOURCE SYSTEM
              -> BI Folder - 1st ECC 6.0 System
              -> SAPFolder - 2nd ECC 6.0 System
Thanks,
Rez

Following OSS note fixes this:
Note 1087980 - ECC Source systems appearing in BI folder

Similar Messages

How to check how many source systems are connected to my BW system?

Hi friends
how to check how many source systems are connected to my BW system?
Regards
BN

Hi All,
Thanks a lot for your help. its resolved now with your help.
Regards
BN

2 clients of one ECC as a source system for BW

Hi Gurus,
we are asked by a customer to set up a new BW system, which will have 2 source systems, clients 300 and 400 of the same ECC. One client is ment for support team work and the other for project team. I understand that the dataflow is partly different (e.g transfer rules and datasources are source system dependent), but most of the dataflow (extractors, customer exits in ECC, infosources, update rules, cubes, etc) are the same. I am referring to 3.X dataflow as that is what we have mostly in the system, but we are on BI 7.0 already.
Do you see any advantages/disadvantages of this approach?
There are certainly some rules which have to be kept by such an approach (e.g. changing transfer rules for both source systems). What do you suggest, which rules should be kept? Would you do it differently? How?
Thank you for your valuable inpt,
Michal

Ahoj Michal,
your approach sounds feasible. You are already running BW in similar setup?
Yes you need to check and modify all your specific settings according data split from 2 clients: e.g. routines in InfoSources, Update Rules etc...
If I would do this differently? It depends on what purpose the data has in such a BW.
- Do they really need to analyze data from both clients?
- How the data model is setup? Do you have different data InfoProviders per client?
I would consider this for approach....
Vela stastia
m./

Connect one SAP ECC 6.0 source system to 2 SAP BW system

Hi!
I copied SAP BW system (e.g. BW1 --> BW2).
My source SAP BW system "BW1" was connected to SAP source system "MM5" (tcode RSA1).
Now I would like to connect my new SAP BW system "BW2" also to this SAP source system "MM5".
When I do so I get the following error:
Connection cannot be used.
Connection BA is used in the MM5:400
source system as a connection BW1CLNT001 to BW
Do you want to delete this connection in the source system?
Question:
Can one SAP ECC system be connected to 2 SAP BW system?
If yes, what are the steps to do this?
Thank you!

Thank you very much!
The question still is how to proceed with the following dialog screen/warning?
Connection cannot be used.
Connection BA is used in the MM5:400
source system as a connection BW1CLNT001 to BW
Do you want to delete this connection in the source system?
YES or NO
Thank you!

Authorization for user in ECC while creating source system in RSA1 in BW

Hello All..
We are trying to create source system from BW(7.0) system using transaction code rsa1 to R/3 Production server.
After providing details in RSA1->Source system ; Remote logon screen of Production server pops up ...and ask to login thru admistrator Id..
To achieve the above task,, what authorization user should have in R/3 system..
Thanks

Hi,
Hope you are using the RFCUSER with these profile SAP_ALL , SAP_NEW , S_BI-WX_RFC in SAP ECC. Please create the RFCUSER with above profiles in ECC and BW (SAP_ALL , SAP_NEW and S_BI-WHM_RFC).
Pls follow the below steps for source system connection
In ECC side
1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
2.) Define a logical system in ECC
3.) Assign a logical system in ECC
4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WX_RFC
In SAP BI Side
1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
2.) Define a logical system
3.) Assign a logical system
4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WHM_RFC)
5.) Define RFC user as default (Click RSA1> Global Settings/Customizing dialog box> Glob. Settings)
Connection of SAP BI with ECC
RSA1> Source System>SAP>create>Enter the below entries
Target computer (server) Server of the SAP ECC
System ID System ID of the SAP ECC
System number System number of the SAP ECC
Background user in source system RFCUSER
Password for source system Password
Background user in BW RFCUSER (can not be changed in this activity)
Password for BW user Password
Select unicode in RFC destination and don't select the checkbox in logic screen.
On the dialog box Please log on as an basis administrator in the following screen choose Continue.
Log on to the Source System with your administrator user. Choose the correct client.
On the Replicate Metadata dialog box, choose Only Activate.
Make sure ECC client will allow changes in cross customizing client. It is one time activity once success then deselect the entry.
Hope this will help you to connect the system.
Rgs,
Ambuj Kathuria

How many logical systems are required to connect between one XI and R3 sytm

Hi Experts,
I need to know how many Logical systems we need to create when connecting an SAP XI and SAP R3 system.
details wht I configured is as follows :
For XI : LOGSYSXI assigned to 100 client
For R3: LOGSYSR3 assigned to 800 client.
Do I need to create two log'cal systems on one side?
How many logical systems can a Client can support simultaneously? is it only one or more that one?
THANKS IN ADVANCE.
Sunil K Shetty

Hi,
>>>>I need to know how many Logical systems we need to create when connecting an SAP XI and SAP R3 system.
as you've noticed you only need 2 - one for r3 one for XI
this is enough
also shown in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
>>>>How many logical systems can a Client can support simultaneously?
one per client
but you can create as much as you wish
wihtout connecting them to a client
but use one for XI
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Dark areas in photos looks different in Loupe and Develope

First let me say that I´ve created a similar thread in lightroomforums.net.
Let me also add that I´ve made extensive research on the web and also read this post: Why does the color and or tone of my image change after import?
This is my current setup.
I run lightroom 5.6, OSX 10.10.
I have been shooting with a 7D or a EOS M in RAW, Adobe RGB With picture style set to standard and no JPG´s.
I have imported my photos as DNG´s with no develop settings applied and build previews set to 1:1 (I have tried different settings here).
I have my Catalog Settings / Preview Cache set to 2880 pixels, quality: High (I have also tried different settings here) (I have a very big screen)
Now to my problem.
Now when I review my photos in 1:1 (or any other size) the dark areas looks good in develop module but when i go back to Loupe the dark areas have a slightly brighter, less contrast look.
This problem only occurs in the darkest parts and does not effect the rest of the image. The overall picture looks the same except for the very darkest parts.
I have tried different monitor calibration settings but the issue persists.
I have tried to create a new catalog, import some new shots but with no difference.
I have also done the same but instead of import to DNG´s I have copied the CR2´s, no difference.
I have tried to optimized the catalog and I have also "Update DNG previews and metadata", no difference.
When "edit file in photoshop CC" the version of the photo that opens in photoshop is the "Loupe" view.
This only happens with RAW/DNG files and not with TIFF or JPG.
Here is a picture that in my case looks very bad in Loupe view but significantly better in Develop View: Dropbox - IMG_3662.dng
I will also try to post two screendumps at 2:1 from the the two views. The picture with more darks in it is the screendump from the develop module and the less dark is from the loupe view.
Why is this occurring? How can I stop it?
Any help is highly appreciated.
UPDATE:
I have taken 4 new shots with the same setup as described above.
But with different color settings and picture styles.
Adobe RGB - Standard
Adobe RGB - Neutral
sRGB - Standard
sRGB - Neutral
With the same results. Dark areas look darker in Develope module.
Message was edited by: K E I added some extra information

ELBE wrote:
Here's my problem:
Magic Wand is configured like this:
Tolerance: 0
Continuous [sic]: Not active [emphasis added] …
There indeed is your problem. Check the "Contiguous" box:

Multiple Schema Creation with One Source system Via SLT

Hi all,
we have BW on HANA environment at our company premises, with SLT server installed
So, my Question is that is it possible to create more than one schema in HANA system with one Source system
As an example, lets say, ECC (Client 601) Source System has been connected to HANA via SLT and created Schema called SCHEMA_1 and again i want to create SCHEMA_2 by connecting same ECC (Client 601) source System.
please help me to short this out?
Thanks
Mirana

Hi Mirana,
Yes, it is possible to create more than one schema in HANA system with one Source system.
Please go through the Official SAP LT document for more details @ page number 13
http://www.saphana.com/servlet/JiveServlet/previewBody/1811-102-5-5419/SAP_LT_Replication_Server_for_SAP_HANA_SPS05_Over…

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Data load problem - BW and Source System on the same AS

Hi experts,
Im starting with BW (7.0) in a sandbox environment where BW and the source system are installed on the same server (same AS). The source system is the SRM (Supplier Relationship Management) 5.0.
BW is working on client 001 while SRM is on client 100 and I want to load data from the SRM into BW.
Ive configured the RFC connections and the BWREMOTE users with their corresponding profiles in both clients, added a SAP source system (named SRMCLNT100), installed SRM Business Content, replicated the data sources from this source system and everything worked fine.
Now I want to load data from SRM (client 100) into BW (client 001) using standard data sources and extractors. To do this, Ive created an InfoPackage in one standard metadata data source (with data, checked through RSA3 on client 100 source system). Ive started the data load process, but the monitor says that no Idocs arrived from the source system and keeps the status yellow forever.
Additional information:
BW Monitor Status:
Request still running
Diagnosis
No errors could be found. The current process has probably not finished yet.
System Response
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
Current status
No Idocs arrived from the source system.
BW Monitor Details:
0 from 0 records
but there are 2 records on RSA3 for this data source
Overall status: Missing messages or warnings
- Requests (messages): Everything OK
o Data request arranged
o Confirmed with: OK
- Extraction (messages): Missing messages
o Missing message: Request received
o Missing message: Number of sent records
o Missing message: Selection completed
- Transfer (IDocs and TRFC): Missing messages or warnings
o Request IDoc: sent, not arrived ; Data passed to port OK
- Processing (data packet): No data
Transactional RFC (sm58):
Function Module: IDOC_INBOUND_ASYNCHRONOUS
Target System: SRMCLNT100
Date Time: 08.03.2006 14:55:56
Status text: No service for system SAPSRM, client 001 in Integration Directory
Transaction ID: C8C415C718DC440F1AAC064E
Host: srm
Program: SAPMSSY1
Client: 001
Rpts: 0000
System Log (sm21):
14:55:56 DIA 000 100 BWREMOTE D0 1 Transaction Canceled IDOC_ADAPTER 601 ( SAPSRM 001 )
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a termination message from the application (MESSAGE Axxx) or by an error detected by the SAP System due to which it makes no sense to proceed with the transaction. The actual reason for the termination is indicated by the T100 message and the parameters.
Additional documentation for message IDOC_ADAPTER 601 No service for system &1, client &2 in Integration Directory No documentation exists for message ID601
RFC Destinations (sm59):
Both RFC destinations look fine, with connection and authorization tests successful.
RFC Users (su01):
BW: BWREMOTE with profile S_BI-WHM_RFC (plus SAP_ALL and SAP_NEW temporarily)
Source System: BWREMOTE with profile S_BI-WX_RFCA (plus SAP_ALL and SAP_NEW temporarily)
Someone could help ?
Thanks,
Guilherme

Guilherme
I didn't see any reason why it's not bringing. Are you doing full extraction or Delta. If delta extraction please check the extractor is delta enabled or not. Some times this may cause problems.
Also check this weblog on data Load errors basic checks. it may help
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Thanks
Sat

Source systems vanishes from RSA1 after renaming of the LSN after BDLS

Dear BW/BI Experts,
           We are doing BW3.1 upgarde to BI7.0........After system copy there is need of rename of logical system for BP1 to BD1 (Prod. to Dev. and Dev. is our new Target BW system ) and From RP1 to RQ1. Before renaming I checked that all source systems were there in RSA1 i.e. Myself BW system , RP1 source system and Flat file source system as per SAP HOW TO ....System Copy in SAP Business Intelligence Systems Landscapes document. (almost 16 steps)
        But after running renaming program by BDLS , I saw source systems are vanished from RSA1..........and now I am trying to create source systems manually.........system is not allowing the same...........pl suggest...........waiting for your experts opinion......pl help urgently as I am in problem fromn last many days and did system copy more than 2 times considering that there may be system copy problem.......
While RQ1CLNT100 creation i.e.Source system ....I am getting follwoing error.........
Entry in outbound table already exists
Message no. E0404
Diagnosis
A partner profile (outbound paramters) could be found using the following key:
/RQ1CLNT100/LS//RSRQST////
This relates to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST    Test indicator
Procedure
Please check the EDI partner profiles.
and also following error after activation..........
Entry in inbound table not found     E0
Entry in inbound table not found     E0
The BW IDoc type ZSBA014 is not the same as the source system IDoc type ZSBC044     RSAR
The following errors occurred in the source system:     RSAR
Incorrect IDoc type ZSBA005 in the ALE definition of the source system     RSAR
Best Regards,
Sharad

Hi Sharad,
This is a very Basis-oriented task,
can your BD1 system can communicate with your peer ECC/R3 deveopment? you might need to run sm59 to ensure your RFC connection with ECC/R3 deveopment is communicating without problem.
once the RFC is ok, if you are familiar with WE20 and WE21 transactions, these transaction will configure IDoc setting (basis level) where you BI system will talk to, i believe IDoc are using old information copied from BP1 is still pointing to your ECC/R3 productive system at IDoc level. you will need to have Basis guy to help you out. please let me know if you need help on WE20 and 21, if you do, you need to provide me your current settings in BD1 and the peer ECC/R3 development setting as well.
cheers

Source System Creation issue in BI

Hi Everyone,
I have already created RFC Connection in BW and EC(BackGround Users are ALEREMOTE and BWREMOTE). I am able to login using Remote Login from SM59 from BW to ECC and Vice versa. After this , When I try to create a Source System, it asks me to provide the ALEREMOTE and BWREMOTE Passwords along with the Source System Name.
I provide all the details.
Then the System asks me to login as a Administrator into ECC. And Once, I login, it throws up an error RFC Connection failed.
I think I am missing some steps.Please provide your inputs.
Regards,
Samir

Hi Ananda,
Thanks for your response. I did the same. Created Background users and when Try to Create a Source System ,it prompts me to R/3 side and here it is showing as RFC Failed. Remote Logon is working. But when Icreate a source System and provide password details, it fails.
Please advice.Is there any password restrictions for Background users.I maintained it as "init123". Do we need to use Capitals. And once, we provide the initial password, do we need to change it again somewhere?
Thanks and Regards,
Samir

Problem BW : DTP lost source system mapping and new one created?

I had a little question concerning the BI content activation, when you have to activate objects and there are two source systems, one of them already with a flow working. Do you have to check both source systems in your screen of source system selection, if there are shared objects? I was afraid if I only checked the one I wanted the existing one would dissappear? I donu2019t want to touch the existing one as it was a 3.5 flow which has been migrated to 7.0.
I have also another question, which is a worse scenario of what has happened recentlyu2026!! Imagine you have originally one source system in your BW DEV environment (towards QA) with a certain amount of Datasources connected to it as well as some DTPu2019s. A new source system was added to this BW DEV (towards PROD). Do you think adding this new source system could have an impact in the mapping of the DTP towards the Datasources? In fact, some of our DTP have been modified and they are pointing to the incorrect Datasource/Source system. These DTP were created manually as well as the Transformations as it was a former 3.5 flow. Do you know a way to bring it back to itu2019s previous connection. Maybe a table that points to the correct source system or a function module? RSBKDTP and RSBK* tables do not store this info (only descriptions) and RSRV doesnu2019t do it.
Please let me know if you have had a similar case! Points are waiting and the gratitude of my boss...lol

Any ideas?

Source system creation IDoc error

Dear Experts,
While creating the source system I am getting this error "IDoc type ZSDD029 could not be found", if I ignore this error the system creates source system in BI folder instead of making it in SAP folder. I have created IDoc with this name and next time when I create new source system the IDoc type move to ZSDD030, and keep on adding it and gave me this error. Any Idea
Regards,
ray

Hello,
Can you try the following:
1) Tcode WE30: The type ZSDD029 must exist in BW system.
If it does not exist, create it as a copy of type RSSEND.
2) Afterwards, enter the following in the view maintenance of view
EDIMSG (tcode SM30):
Message type RSSEND, IdocType as specified above, Release
corresponding to the release you are currently using.
3) Please make sure your entries for RSBASIDOC are identical in BW.
Regards,
Shashank

Massive copy of BW transformation between different source system

Hi all,
in my BW I have different source systems. I have mapped several objects to one source system.
Now I need to copy all the transformation to other source systems. These source system are different instance of ECCs, there are the same extractor in all the systems.
I can't use the BDLS becouse these move the transformations between the system not copy it.
I try to create a Transport and using the Conversion of Logical System Names but this change only the objects with source sytems dependencies, it don't change the technical name of transformation, and do not create a tranformation to the new system but overwrite the existing one.
Do you know if there are some program or some procedure to copy transformation between sourcesystem in BW?
Thanks in advance
Mario

Hi,
you can do a Retrofit (System copy), Generally, retrofit happens between two different BW systems.
check with your basis team if the retrofit is possible with in the same BW system but for different clients.
Note : System copy will overwrite all the objects.
Regards,
Sudheer

ECC 6.0 Source Systems are added to 2 Different Folders - BI and SAP

Similar Messages

Maybe you are looking for