Source system R33CLNT100 is marked as inactive in BI.

Dear Experts
When I do a source system check via RSA1 > Source systems > SAP folder > right-click the R/3 system ID and select Check function,
the system throws as error as shown :
"Source system R33CLNT100 is marked as inactive in BI."
"Procedure
    If you have upgraded to BW 2.0, activate the source system.
    With other errors connected to this source system, choose Restore   the
    source system from the source system tree in the Data Warehousing
    Workbench. This regenerates the source system, merges the relevant
    communication parameters, and replicates the DataSources in BI.
and
"BI IDoc type ZZZZ011 is not the same as source system IDoc type ZSSS021     RSAR     371
There was a system Refresh from Production R/3 46C to QA system R/3 46C.
We did the BDLS but the IDOC seems to have got overwritten by R/3 Production's, obviously , due to refresh.
Any idea how to resolve this?
It seems like I need to re-create manually the idoc but I am not expert in this area.
I do know there are standard IDOC aspects for BI 7.
But how to re-create the relevant IDOC settings or configurations ? Need to do this in both BI and R/3 ?
Best regards
Pascal

Hi pascal ,
Seems to be connectivity between the source system and the Bi system it will be restore by basis team only. Couple of tings that you can do at your end will make their work at ease
i) check the RFC connection between the Source system and the Bi system in Sm59.
ii)Make sure the user ALERMOTE and SAPCPIC are unlock in ecc side
Now for configuring the source system by urself follow the below points :
1. In BW, call TA RSA1.
2. In the left hand column, choose "Source systems".
3. In the column Source systems, right click on the respective source system and choose "Restore".
4. A popup "Create R/3 source system" appears. Enter the passwords for user SAPCPIC. Hit enter.
5. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
6. A logon screen of the child system appears. Enter your user and password and hit enter.
7. A popup "New source system connection" appears. Hit "Continue".
8. A popup "Check RFC destination" appears. Hit "Check".
9. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
10. The popup "Check RFC destination" appears again. Now hit "Use".
11. A popup "Connection can not be used" appears. Hit "Delete".
12. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
13. A logon screen of the child system appears. Enter your user and password and hit enter.
14. A popup "New source system connection" appears. Hit "Continue".
15. A popup "Check RFC destination" appears. Hit "Check".
16. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
17. The popup "Check RFC destination" appears again. Now hit "Use".
18. A popup "Replicate Metadata?" appears. Hit "Only Activate".
19. If popup "Do you want to reactivate all transfer structures and DataSources?" appears. Hit "No". If "Display activation log" popup appears - press "No" (that message may appear several times).
20. Press "Back" if "Analyze application logs" screen appears
Source -->http://forums.sdn.sap.com/thread.jspa?threadID=1892011
Thanks,
Deepak

Similar Messages

Source System Connection Issue after BI 7 Upgrade

Hi all,
We have just upgraded from BW 3.1 to BI 7.
After the upgrade, I checked the connection to our R3 4.6 source system.
It is now saying the following message:
Source system XXX is marked as inactive in BI.
Check failed for RFC connection XXX ; check destination
After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
The thing is that our name & password ARE correct definitely.
Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
Any ideas?
Thank you
chris

Hi,
as from NW7.0, passwords are case-sensitive.
If you define the passwords in the RFC in uppercase, it will work.
This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

DW Workbench - Source System : Object Information

I recently applied some bi support packs through spam, and I realize now in my BW Workbench Source Systems
under Modeling, the active/inactive sign under Source System : Object Information column is no longer showing,
which, usually indicate whether the connection to the source system is ok or not.
Does anyone know what configuration is changed?
Thanks.
Edited by: BI Junior on Jul 16, 2009 8:04 PM
Edited by: BI Junior on Jul 17, 2009 2:36 AM

Thanks Mohan Kumar,
I check the source system, it is ok.
However, under that column, I used to have a active/inactive symbol which will tell me whether
the connection is ok or not, now the symbol is gone, so I have to check to see whether the
related source system ok or not.
Could you see the symbol in your system? My BI7 ides was SP70009, now I updated to SP70016...

Source System inactive in Quality

Hi Experts,
I need to load the data from flat file to ods but my source system is inactive in Quality server when i double click on source system it is not showing any active button in quality server, but the same source system is active in development server.
Please can any one solve my problem.
Many Thanks in advance
David

Hi Srinivas,
Thanks for your answer, and one of my source system is still inactive for this i follow the below steps,
1) Run the program in se 38 RS_TRANSTRU_ACTIVATE_ALL
2) RSA1- source system_ right click on source system - activate..
but still my source system is inactive so how can i solve my problem... please give me solution.
Daivd

BAdI implementation FIAA_BW_DELTA_UPDATE inactive in source system DEV

Hi all.
I'm trying to execute an infopackage to get 0ASSET (texts delta initialization). But it shows me the next error message: "BAdI implementation FIAA_BW_DELTA_UPDATE inactive in source system DEV".
But when I look at this BADI implementation in the source system (Transaction code se19) there are no errors on it.
"BAdI implementation FIAA_BW_DELTA_UPDATE does not contain any errors".
Do somebody knows what's happenning?

Hi,
If you are in version 3.1, then this BADI has an issue.
Kindly refer to the following note:
[SAP Note 590034 Deactivating implementation FIAA_BW_DELTA_UPDATE|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bct/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d353930303334%7d]
Cheers...

BI is flagged as inactive in BI source system

Dear All,
BI Consultants are facing error on RSA1 tranaction in the Source system .
RSA1 -source system - select Sources system -right click - click check . they are getting the below error .
BI is flagged as inactive in BI source system
Diagnosis
     BI is flagged as inactive in BI source system .
Procedure
     If you have upgraded to BW 2.0, activate the source system.
     With other errors connected to this source system, choose Rest
     source system from the source system tree in the Data Warehous
     Workbench. This regenerates the source system, merges the rele
     communication parameters, and replicates the DataSources in BI
Kindly advise to resolve the issue.

Hi,
Have you ever checked the thread, below? It's been solved, previously
BW Issue
Best regards,
Orkun Gedik

How to set source system inactive

Hi experts,
Can someone please tell me how to turn a source system to inactive???
Thanks!
Artur.

Hi
You cannot Inactivate the Source System -- Try removing the RFC connectivity between the systems
In BI, SM59, delete your R/3's connection entries.
In R/3, SM59, delete your BI's connection entries.

Source system Inactive

I created a source system for our R/3 QA client. The RFC connection works ok between R/3 and BW. I've done the following steps:
Define client administration
Define Logical System
Assign Logical system to client
Create RFC User
Connecting BW with R/3
In the last step I selected Replicate Metadata and chose Only Activate
I get the following error message:
No metadata upload since upgrade RSAR 672
Detailed description:
Diagnosis
     DataSource replication has not been performed since the source system
     upgrade.
System Response
     The Content that is assigned to this source system is obsolete.
Procedure
     Refresh the metadata completely for this source system.
Procedure for System Administration

Michail,
I do have an answert to Your question, but a small request. Could you please send me the step-by-step guide on "How to create RFC connection".
Thanks in anticipation,
Kind Regards
Paddy

"Conversion of Source System names after the transport" : O

Experts:
Environment : BI 7.0 and SP 12
Tranports related to transformation rules are failing with inactive status...
Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
Everything looks fine to me with reference to actual techinical names of source/target system...
My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
OR do i need to create another entry with same source/target system and check the 7.0 box.
OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
Finally, please advise the exact steps that need to be taken here...pros and cons
Your inputs will be of great help....
Thanks,
BI
Message was edited by:
B I

Hi,
Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if your client is modifiable, if not you need to transport the setting from DEV. Go to
SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
you also need to maintain the Source system IDs .
Hope it helps.

Unable to 'set the default source system' to Install Business Content

Hi,
Maars here. This is my first post hoping that in future ones I'll also be lending a helping hand.
I am trying to 'Install Business Content' under the BUSINESS CONTENT section in txn RSA1. I am doing this after 'Transfer Data Sources' in R/3 and I can now see all the data sources (under the application component hierarchy) for the source system. But I am not able to see the Info Objects in the Business Content.
When I try to set R/3 as the default source system (got this screen after clicking a icon in the standard tool bar), BW is not saving the settings ie., I set the R/3 as the default and then click on OK. If I go back to the same screen again, I find that my settings were NOT saved.
Could you please help me out?
Thank you.

Hi,
It seems to be a bug in version 3.5.
Do like this:
After you open the screen to choose the dafault source system
Clcik on 3rd button(F6) available in the bottom of the scrreen.
And then select teh tick mark for required system.
And then click on Continue button
You have do this step before you drop the cube to right side of the cube.
Ok, even after all these steps , if you reopen the screen you would not see Tick mark u have done just before. DONOT WORRY ABT it.
Drag and drop required cube with dat flow before.
Now you can see the Transfer rules with selected Source system only in the collected Objects.
With rgds,
Anil Kumar Sharma .P

Source system error - RFC connection failed

Hi Gurus,
I have installed ECC6 on my PC but not when i am trying to created the DS its not allowing me its saying appl comp hierarchy for source susyem "T90*" doesnt not exist.
so tried going to source system -> done a check for my source system then i got the following errors
Source system "T90*" is inactive
Entry in outbound table not found
Entry in inbound table not found
Basic type does not exist
Check failed for RFC connection T90CLNT090 ; check destination
can any one tell me how to fix this issue?
Regards,
Ravi

Hi Ravi,
Did you run appication component hierarchy in source system(TX-RSA9)
then activate your data source
then replicate in BW system.
Check here for BW connectivity with source system.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bi/stepbyStepBusinessIntelligence
Thanks,
Vijay.

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.

ERROR with Source System in BI

Hi,
I replicated the datasources from DEV to BI. They replicated just fine. I can even see it in BI. I then tried to activate the datasource (i created the datasource from a view ) but it gave me a run time error :
ASSIGN_LENGTH_0 Short dump has not been completely restored..too big.
I then tried to go into the source system and tried to activate that and it said:
Source System DEV300 is inactive
BI Unknown in system
BI IDoc type ZSBC019 is not the same as source system IDoc type
The following errors occured in the source syaytem:
Entry in inbound table not found
Entry in outbound table not found
Result of the destination check: No authorization to logon as trusted system
What could have went wrong?
Thanks

Did you try activating the source system in RSA1 ..right click and choose active.
if this doesnt work then you might want to check the inbound and outbound entries in we20 transaction code for the source system. If you have authorization. Or you need to check with your BASIS to set that up for you.

RFC connection to source system is damaged , no Metadata uploaded

Hello Friends,
I need your help to understand and rectify why my transport is failing again and again.
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata upload
Environment - Production Support (Dev - Quality - Testing - Production)
Alive scenario - Need to create two InfoObject and incorporate the fields in to data targets and reports.
What we have did?
1st request - We have created new request and captured two Infoobjects in to the request.
2nd Request - We have captured the replicated Datasource along with that the below sequence displayed by default in the same package.
Communication structure
DataSource Replica
Transfer Rules
InfoSource transaction data
Transfer structure
3rd Request - we have captured DSO and Cube only in this request.
4th Request - Captured 2 update rules (ODS) Update Rule (Cube)
The above 3rd request failed in the testing system (successful in Quality System) and ODS is inactive in the Testing system.
Testing system Error Message:
The creation of the export DataSource failed
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
Error when creating the export DataSource and dependent Objects
Error when activating ODS Object ZEOINV09
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/AZEOINV0900)
Table /BIC/AZEOINV0900 could not be activated
Return code..............: 8
Following tables must be converted
DDIC Object TABL /BIC/AZEOINV0900 has not been activated
Error when resetting ODS Object ZEOINV09 to the active version
So we have captured the data mart Datasource and created a new( 5th ) request (transported only 5th request )and transported in the below sequence
Communication structure
Datasource Replica
Transfer Rules
Infosource transaction data
Transfer structure
development to Quality - Successfully
Failed in testing system again.
How to rectify this error, please help us
Thanks,
Nithi.

Hello All,
*Question -1*
I have checked the connections and typed the steps below - what i have seen in the screen.
Steps :
R/3 Connection - I have double clicked on the BT1CLNTXXX and tested the connections.
Connection Type :
Logon - 0KB , 10 KB , 20KB, 30 KB
R/3 connection:
5 msec, 0msec, 1msec,1msec,1msec
Please let me know whether RFC connection is OK or not.
Question - 2
I want to know is there is any option to check before transporting the TR from Developement to Quality - "Preview Check " the sequence , so that we can avoid the Transport failure because of TR sequence.
Regards,
Nithi.

Creation of Source System(R/3)

Hi,
I'm trying to create R/3 source system in BW(RSA1->Source system->Create) but it fails to create.
I have created RFC Destination on both BW & R/3 systems.
I tested them for 1) Test connection 2)Remote connection.
Sucessfully able to remotely login to each other systems.
But when i create from RSA1 its failing.
Any help please ?????????
Regards
prabhakar

Prabhakar,
while creating the Source System, if you right click on source system and go with check...it will give you the error. if you click on Question Mark or Help Ocon. it will what you need to do in order to get rid of this problem.
you need to create a entry in the RSADMIN table. check for RSA1> tools> there is an option that will update the table RSADMIN.
In furture, if you come accross any such problems with Source system... go with check.
all the best.
Regards,
Nagesh Ganisetti.

Source system R33CLNT100 is marked as inactive in BI.

Similar Messages

Maybe you are looking for