Source System in an ABAP Landscape

We are relatively new to SAP. Back when we initially architected the landscape we had many consultants in, including several Platinum consultants from SAP. At the time they emphasized the special nature of the "source system" in an ABAP landscape, and how it should never be refreshed and how we should not change which system in considered the source in our landscape. "Once the source always the source."
Now we are being asked to change the source system, but we do not have the background as to why the source system is so special and why it should not be refreshed or changed.
Would you be willing to share your opinion on the matter? Pros/Cons/Costs of Changing/Costs of Refreshing.
Thank you very much.

There is a SAP Note 130906 for this. Pasting few lines from note for your referance. Please ref Note for details.
Symptom
You want to copy the versions of the repository objects from one R/3 system into another, for example because you are planning to copy your production system to your development system.
Such a procedure does not correspond to the strategy recommended by SAP, to always retain the development system.

Similar Messages

ABAP CODE TO POPULATE LOGICAL SOURCE SYSTEM

Hi Friends please help me with the below
1. Requirement : to Populate The system Date , Source System
in BI for Each load request.
1 Solution: I thought of writing the Start Routine for this but it is giving me error
syntax Error: END METHOD MISSING?????
2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
Thanks
Poonam Roy
ABAP Code.
I have the End Method. what more to do.
METHOD start_routine.
*=== Segments ===
FIELD-SYMBOLS:
<SOURCE_FIELDS> TYPE tys_SC_1.
DATA:
MONITOR_REC TYPE rstmonitor.
$$ begin of routine - insert your code only below this line -
... "insert your code here
FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TRANSTRU
ABORT LIKE SY-SUBRC.
DATA: ZLOAD_DAT LIKE SY-DATUM
ZZSOURSYS TYPE RSLOGSYS
IF G_S_MINFO-DATAPAKID=1
SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
ENDIF.
ABORT = 0.
ENDFORM.
ENDMETHOD.
ENDCLASS.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD.

You have to write the code (in BI/BW) in the transfer rule (between Datasource transfer structure and infosource/info object)
There the FORM begin with
[code]USING RECORD_NO LIKE SY-TABIX
 TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
 G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OIPERSON
 G_T_ERRORLOG TYPE rssm_t_errorlog_int
 RETURNCODE LIKE SY-SUBRC
 ABORT LIKE SY-SUBRC. set ABORT <> 0 to cancel datapackag[/code]
GS_MIN_INFO structure RSSM_S_MINFO contains information on the request being processed.
G_S_MINFO. This passes technical information about the data load request,
such as requesting user, request date and time, update mode, the handling of
duplicate records, error handling flags, parallel processing flags, and what data
targets to update.
If tou want to use start-routine for optimization reasons and fill an empty field in transfer structure, the structure G_S_MINFO is available too.
[code]USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TAB_TRANSTRU
 G_T_ERRORLOG TYPE rssm_t_errorlog_int
 ABORT LIKE SY-SUBRC. set ABORT <> 0 to cancel datapackage[/code]
And stay in FORM between limits :
[code]$$ begin of routine
$$ end of routine[/code]
Update RESULT in first case, and field(s) of DATAPAK in second case.
[code]RESULT = G_S_MINFO-LOGSYS.[/code] or
[code]LOOP AT DATAPAK INTO l_s_datapak_line.
l_s_datapak_line-zzsourcsys = G_S_MINFO-LOGSYS.
MODIFY DATAPAK FROM l_s_datapak_line.
ENDLOOP.[/code]
Regards

ABAP logical source system

dear all,
how can i get the logical source system using abap into my update rule?

Hello,
I believe is SY-SYSID.
Diogo.

Configuration Wizard-NW:BI-AS ABAP(Connectivity of BI and Source System): M

Hi friends,
I´m configuring the (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain) in NWA using Configuration Wizard.
But there is the error in step (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain > Scenario UI: NW_BI_ABAP_DEFAULT > Scenario Process: Abap Server Integration to BI > Configuration Process > Configuration Unit: Initialize > Config Unit BI System: Initialize > Customizing: Assign Logical System to Client > Write Customizing data to Table T000)
Below error log:
*Write Customizing data to Table T000*
Description:
Exception in step "WriteProfile_1223390220410"
Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Exception during the import of the profile!
State
Step finished with error
Support Information
Type of Action
WriteProfile
Debug Events
WriteProfile:Write Customizing data to Table T000
Library: sap.com/tclmconfig~bs
SourcePath ./com_sap_nw_bi_abap_default_maintain/ext_12064772269223/ext_1206447991146/Process_1207123636083/proc_1196064316796/Process_1204300420808/proc_1204300371034/WriteProfile_1223390220410
Time 2011/11/03 at 15:36:57
Schema content/NetWeaver/Common/Customizing/Clients/T000.xsd
Type : View Maintenance
Input
<TABLE_T000 xmlns:expr="http:/sap.com/ctc/expressions"><T000><MANDT>100</MANDT><LOGSYS>SOLCLNT100</LOGSYS></T000></TABLE_T000>
Schema
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:vma="http://www.sap.com/ctc/vma"
elementFormDefault="qualified"> <xsd:element name="TABLE_T000" type="TABLE_T000"></xsd:element> <xsd:complexType name="TABLE_T000"> <xsd:sequence> <xsd:element name="T000" type="T000"> <xsd:annotation> <xsd:appinfo
source="http://www.sap.com/ctc"> <vma:vmacontext table="T000" isupdate="false"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="T000"> <xsd:sequence> <xsd:element name="MANDT" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="MANDT"/> </xsd:appinfo>
</xsd:annotation> </xsd:element> <xsd:element name="LOGSYS" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="LOGSYS"></vma:vmaproperty> </xsd:appinfo> </xsd:annotation> </xsd:element
</xsd:sequence> </xsd:complexType> </xsd:schema>
Destination parameters
user : SOLMAN_ADMIN
password : % secure content %
host : cdsolman
sysnr : 01
client : 100
language : en
Stack Trace
Caused by: com.sap.tc.lm.ctc.cul.api.CULServiceException: Exception during the import of the profile!
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:98)
 at com.sap.tc.lm.ctc.cul.serviceimpl.process.WriteProfileControllerImpl.execute(WriteProfileControllerImpl.java:160)
 ... 16 more
Caused by: com.sap.tc.lm.ctc.cul.cpi.context.ConfigurationBrokerException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='xml_parsing_exception', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key xml_parsing_exception
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:79)
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:95)
 ... 17 more
Caused by: com.sap.tc.lm.ctc.provider.vmaprovider.exceptions.VMAProviderBaseException: Incorrect XML
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:349)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.setXmlValue(VMAUtil.java:250)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeContext(JCOProfileExecutorImpl.java:310)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeChildNode(JCOProfileExecutorImpl.java:183)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeProfile(JCOProfileExecutorImpl.java:129)
 at com.sap.tc.lm.ctc.provider.vmaprovider.VMAWriteProfile.writeProfile(VMAWriteProfile.java:59)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:144)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:73)
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)(:main:, row=1, col=637) -> com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:341)
Caused by: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:209)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
 at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
All the others steps were finished successfully
Only this step is with error. I don´t know that to do.
Regards,
Ricardo Arriado
Edited by: Ricardo Arriado on Nov 4, 2011 6:24 PM

Hi,
Please double check the JCO user and the authorization.
Or
Apply these two notes, it should resolve ur issue
1493124 CTC: Check table existence before table whitelist
1471762 CTC: Automated Configuration:
Hope this helps u.
Best Regards
Vijay K

How to Stop at Source System's Abap Code from BI Infopackage Trigger

Hi Experts,
I have enahanced 2 fields to some standard data source, that fields data is comiong fine to RSA3 in Source system.
i am not getting 2 fields data to BI PSA, but that 2 fields data i am getting at in RSA3 Tcode source system.
i have tried all the ways to get data to BI PSA, but no luck.
so, while running infopacke from BI i need to stop at Source System's Abap code where i have wriiten the code for those 2 fields.
so, please any one can explain, how to stop at source system's Abap Code once i trigger infopackage from BI.
Regards,
Nagaraju K.

Hi,
which data source on your working?
master data or transaction data
enter the TCODE- CMOD
choose the project
select the funciton exit - EXIT_SAPLRSAP_001 - Transaction data
                                    EXIT_SAPLRSAP_002 - master data attr
                                    EXIT_SAPLRSAP_003 - mster data text
                                    EXIT_SAPLRSAP_004 - master data hier.
choose the include program - ZXRSAU01.
go to source code tab -> go to change mode -> find the code will start form here
EX- : when " ZLIS_13_VDITM
if not required don't put break-point .
just comment it code.
Thanks,
Phani.

Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14

Hello SAP Friends! Our NW admin did a dual stack system copy where the ABAP server came from system 1 and the Java server came from system 2. This worked fine for ABAP (duh it was installed first), but the Java system copy was a disaster. the server started but many key services did not.
Why?
Many of the configuration entries were not generated properly. For example, a new, unknown SID was created, and many entries referenced System 1 (the ABAP source, not even the Java source). We were able to find and fix some incorrect config entries, but we still couldn't get all of the services we needed to work.
I think NW is so complicated that such a configuration is probably impossible, but maybe I am wrong.
Does anyone have tips? Or can confirm that this would never work?
The current plan is to install the Java Server from scratch as an add-in, which is less effort than searching through all the config files without any certainty that it will work. Hopefully it will work.
Many thanks in advance.

Hi Matt,
What kind of infos are you looking for? I didn't perform the copy, have just been trying to figure out how to get all of the Java stack's services to start properly. As far as I know, it was done using the standard System Copy wizard. The ABAP server was done as a central instance and then the Java server was copied and installed as a java add-in.
I have asked the admin to post the details to this thread, but it would be helpful if you could mention what types of info and details you are looking for.
Thanks and Best Regards,
John

Finding messages sent through ABAP proxy in the source system

Hi All,
I have a Proxy to HTTP scenario, wherein the messages are landing up in error at reciever for some value in the payload.
I tried to look for the messages in XI, hwever they have been successful thru it and are deleted now.
Also I tried to look for the messages in the sender R/3 system in SXI_MONITOR, hwever i dont have the access to this tcode there.
Is there any other way these messages can be looked for in the R/3 system?
Regards,
Diptee

Hi All,
I could not find the messages in the source system, they seem to have got deleted (as they are old).
Also i was trying to achieve the requried in the production environment, and so needed to know if the messages can be looked for by any means other than the report 'Monitor for Processes XML messages'.
Thanks a lot.
regards,
Diptee

What are the changes to be done on BW end during hardware change of source system?

Hello Gurus,
There is some hardware changes happening and I need help in certain things which I need to do from BW point of view. First of all, I have attached a figure showing my system landscape. I would kindly request you to go though the fig first.
For QA, initially we were using AG3 as the source system, now they have made the hardware changes, made a system copy of AG3 into the new system AEQ. We have connected our BW QA system to this new system AEQ. Now when I check the system, there are no data in set up tables (I am using SD and MM), but there are data in tables. But when I replicate data sources from AEQ to BW QA, the existing transformations and DTPs will disappear. So, that left me with 2 options-
1. Either transport old transformation and DTP from BW DEV to BW QA
2. Or create new transformation and DTP in BW QA system.
Can you experts please suggest me what should be the solution?
Also, please note that, the basis team started the hardware changes with ECC QA system for some reason. Once ECC QA is fine, they are planning to make the changes in ECC DEV system (from AG2 to AED). Currently, AG2 is connected to BW DEV and AEQ is connected to BW QA.
Can you please suggest me whether there will be any issue if we opt to transport transformation and DTP from BW DEV to BW QA when BW DEV is still connected to old source system? Or, is there any other easy way to sort this out? Please suggest?
Thanks a lot
Rakesh

Hi,
1. Either transport old transformation and DTP from BW DEV to BW QA?
Yes, better to transport from bw dev to bw qa
2. Or create new transformation and DTP in BW QA system?
at BW Quality, creation may not be possible. Better to transport from bw dev to bwq.
or use standard abap program to activate transformations and dtp.
When changes are applying at source then you just need to take care the delta queues
clear all queues by running related V3 jobs and delta info packs. make them as 0 count.
once basis team was done changes later try to check your delta loads at bwq .
Thanks

Start Routine to populate the Logical Source System

Hi Friends please help me with the below
1. Requirement : to Populate The system Date , Source System
in BI for Each load request.

1 Solution: I thought of writing the Start Routine for this but it is giving me error
syntax Error: END METHOD MISSING?????
2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
Thanks
Poonam Roy
ABAP Code.
I have the End Method. what more to do.
METHOD start_routine.
*=== Segments ===
 FIELD-SYMBOLS:
 <SOURCE_FIELDS> TYPE tys_SC_1.
 DATA:
 MONITOR_REC TYPE rstmonitor.

$$ begin of routine - insert your code only below this line -
... "insert your code here

FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TRANSTRU
ABORT LIKE SY-SUBRC.
DATA: ZLOAD_DAT LIKE SY-DATUM
ZZSOURSYS TYPE RSLOGSYS
IF G_S_MINFO-DATAPAKID=1
SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
ENDIF.
ABORT = 0.
ENDFORM.
ENDMETHOD.
ENDCLASS.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
 raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD.

Hi,
Check whether the formula is useful here than Routine. Because you can see the Sy-datum , source system( I Guess) fields as avaialable formula elements .
With rgds,
Anil Kumar Sharma .P

Job terminated in source system -- Request set to red

Hi Developers and supporters can you any one help me.
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
Date        Time      Message
13.10.2010 16:48:01 Job started
13.10.2010 16:48:01 Step 001 started (program SBIE0001, variant &0000000024579, user ID RFCUSR)
13.10.2010 16:48:01 DATASOURCE = 0ACTIVITY_ATTR
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 *          Current Values for Selected Profile Parameters               *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 * abap/heap_area_nondia......... 2000683008                              *
13.10.2010 16:48:01 * abap/heap_area_total.......... 2000683008                              *
13.10.2010 16:48:01 * abap/heaplimit................ 40894464                                *
13.10.2010 16:48:01 * zcsa/installed_languages...... 6EDGIJL                                 *
13.10.2010 16:48:01 * zcsa/system_language.......... E                                       *
13.10.2010 16:48:01 * ztta/max_memreq_MB............ 256                                     *
13.10.2010 16:48:01 * ztta/roll_area................ 6500352                                 *
13.10.2010 16:48:01 * ztta/roll_extension........... 2000683008                              *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 17:57:09 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
13.10.2010 17:57:09 Job cancelled

Hi SUSUSU,
The dump is related to temp table space issue.check the space for PSATEMP table.
Use tcode DB02 to check the table spaces, in the tree diaplayed on you left. try to see the % used for your ODS & FACT tablespaces. Incase the % are too high like 99% etc, get in touch with you BASIS team.
Request your basis team to increase the PSATEMP table space.
Or
Decrease the data packet size and run the info package.
to decreae the packet size -- in the IP screen menu --> schedular -->Datasource setting for sending data --> there change the parameter Maximum size of a data packet in kByte.
down you can find the area to enter the data packet size .
for ex if it is 20000 decrease it to 10000 and run the info package

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

Multiple rows in BI Infocube/or DSO for one row in source system

Hi Gurus,
I have a typical scenario where in I have a ztable in R/3 system and it contains some custome transaction data.
The business scenario wants it to split into multiple records in BI ( ofcourse keys for each records in BI would be unique). Either infocube or DSO can be used to store the data in BI.
Is it possible to do that. As far as my knowledge goes( I have limited BI exposure) one record from source system ( read row) is transformed into one record ( row) in BI in simple transformation.
Please give me some rough idea if its possible how can we achieve it.
I know we can write an ABAP program and create a ztable to do it and use the ztable as source for incube/dso. But I want to use this as last option.
Thanks
Sumit

Hi,
An ODS will be better.
Use a start routine.
data-package --> package2
create your own package with your rules.
update.insert.modify.append....
package2 --> data_package
and from 1 row, you create n row as your rules would like..
Regards,

Source system assignment while transporting to quality

Hi Guys,
I have the following landscape.
I have created 2 source system ECCDEV and CRMDEV for my BIDEV.
Now I wish to do transport to Quality box and i want to know what should be the source system assignment , I should maintain in rsa1->transport connection -> conversion of logical system name.
When I maintain ECCDEV -
> ECCQUA
I get the error : ECCQUA entry does not exist in TBDLS.
Do I have to maintain source system ECCQUA(Quality) in BIDEV(Development) itself?
-Amit

Hi Rakesh,
Let me know if my understanding is correct.
In DEV BI, I create a connection to DEV ECC.
Also, I create source system ID's for source system.
In the QUA BI, I create a connection with QUA ECC.
and assign source system connection (source and target) i.e. DEVECC and QUAECC.
Then I transport requests(activated datasources) from DEVECC to QUAECC and replicate the datasource in QUABI.
Please Confirm.
-Amit

Source system ECQCLNT320 does not exist in BI Production

Hi,
When i am transporting the BI objects along with the datasources it is giving the following error.
our system Landscape:
BI Dev. & BI Qty Same Box
ECC Dev.
ECC Qty
ECC Prd.
in our landscape BI dev and BI Quality are the same Box, i am transporting BI cube objects along with ECC quality system datasources from BI dev. system. But when we import the cube request the following error is occuring.
Please help me as i am in typical stage.
ERROR: Start of the after-import method RS_RSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mode)
Source system ECQCLNT320 does not exist
Can we transport the ECQ datasources from BI dev system where i am using them.
Thanks,
Baswa

Hi,
RC on ECQCLNT320 check the source connection under sourcesystem tab in Rsa1,it might having issue else
Check in the RSA6 (Sourcesystem) wether DataSource is active mode or not ,
Go to Tcode RSDS for Replication of DataSource in BW system .
Regards,
Satya

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.

Source System in an ABAP Landscape

Similar Messages

Maybe you are looking for