Source System create - RSAR 374 Error

Hi,
in RSA1 when deleting source system , which caused info objects/PSA tables for the particular source system deleted. Now, when creating new source system, it fails, It times out.
It stops at "write version D" and times-out . Is there anyway, it could be fixed,.
Error:
The following errors occurred in the source system: RSAR 37 4
Result of the destination check: Timeout RSAR 37 5
Thanks,
Usha
Edited by: Usha4sap on Jun 11, 2010 9:39 PM

Hi Usha,
Check if the RFC connection is established between the R/3 and BW system. If not, speak to the BASIS team.
rgds,
Sree

Similar Messages

Collection in source system ended-Process chain error

Hi friends,
I have got a PC which failed due to error : Collection in source system ended.
My flow of PC is .
start--
       --Load IP 1
      ---Load IP2
      _--load Ip 3
Load IP4
      ---Load Ip 5.
I got this error at IP2 and so my pc fail .
can i manually upload this IP2 and make the process chain OK?
what are the steps involved in rectifying this?
regards,
siddartha

First try to find out the reason for the load failure. Once you fix this, do a manual run of the infopackage and when successful you can continue with the rest of process chain.
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.

Problem Activating Source system RSAR 374, RSAR 375

Hi all,
Hoping you can help me with this issue. I have two
systems,one R/3 4.7 system and another BW 3.0B system.Both are recently installed. created user in client 800 on R/3. created user in client 100 on BW. i established RFC destination between both, Logical source system assignments and definitions of logical source systems on both. They are working correctly, But i couldnot succeed in creation of the source system. it gets created but it is not activated and ends with the following errors.
Message and the id next to it
1) The following errors occured in the source system. RSAR 374.
2) Result of the destination check: timeout . RSAR 375 .
when i try to activate it by right clicking on it , it does give these errors and activation gets terminated.
Can anyone pleaseeeeeeeeeeee with this. Thanks a lottttttt........
kishore karnati

Hi Kishore and Edwin,
I have exactly the same problem described here, except I am creating an ECC 6 source system in BI 7.
Therefore, I am wondering if you guys can elaborate on your experience.
I get the same error message RSAR 374 and RSAR 375.
I did both connection and authorization tests for the RFC in SM59 and it's OK.
What do you mean by the "basic concept of BWREMOTE AND ALEREMOTE background users."???
Please advise.
Cheers,
SJ

Urgent ......Problem........Error RSAR 374, RSAR 375

Hi all,
Hoping you can help me with this issue. I have two
systems,one R/3 4.7 system and another BW 3.0B system.Both are recently installed. created user in client 800 on R/3. created user in client 100 on BW. i established RFC destination between both, Logical source system assignments and definitions of logical source systems on both. They are working correctly, But i couldnot succeed in creation of the source system. it gets created but it is not activated and ends with the following errors.
Message and the id next to it
1) The following errors occured in the source system. RSAR 374.
2) Result of the destination check: timeout . RSAR 375 .
when i try to activate it by right clicking on it , it does give these errors and activation gets terminated.
Can anyone pleaseeeeeeeeeeee with this. Thanks a lottttttt........
kishore karnati

Hi,
The R/3 system should be open for changes. See OSS Note #184586 - "System change option and BW". So, its description somewhat different from your situation, I got the same error while tried to create a source system until R/3 was open for changes.
Best regards,
Eugene

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 not available error

If the error message is teling as source system not available
so what can be the reasons for that and tell me the solution also.
data cllection is incorrect
so what can i do i have checked trfc connections every thing but every thing is fine
so any body help me out in this.
your suggstions will be rewarded.
Regards.
Vikram.

Hi Vikram,
Try the below mentioned steps:
1. Check the connections on BW sysetem and R/3 system.
Use the tcodes: sm58 and sm59. On the context menu of the source system created, check the option for conections. If connections are not fine, contact the basis team
2. Go to 'source systems' select you source system and right click and select 'Repicate Data Sources' , then try replicating the the infosource for that
appilication at the top node level as a whole, the try replicating the Data source
with in your infoarea..
Hope it would help ..if yes..assign points.
Regards,
Manu.

BE3.5 : Error from the source system while activating the transfer rule

When I was trying to activate the transfer rule for one info object( charateristic with master data) , I got the following error in [[ ]]
Error when creating transfer structure /BIC/CCPIZGR00CC_ATTR in source system CI2220
Diagnosis
An error occurred when creating transfer structure /BIC/CCPIZGR00CC_ATTR as an IDoc segment in source system CI2220 .
System response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system CI2220 to identify the error, and remove the cause.
CI2220 is the backend R/3 system, I had no issue in replicating the data source etc. this error occurred while trying to activate the transfer rule after assigning the info source to the replicated datasource in BW.
Can anybody tell me how to view( what transaction etc) the generation log to understand the issue?
Thanks in advance
Arunabha

Hi Arunabha,
I would confrim that there is no issue with the datasource in your r/3 system. Can you run the datasource on your r/3 system with no errors using RSA3?
If the datasource is ok, then I would check out the error message number in OSS or SDN. I have seen this error before, I just cannot recall what the fix was.
Cheers!

How to create Source Systems in BI or RFC ??

Hi Gurus,
I want to load data from an R/3 connection to BI.
Now i have modified my Datasources in R/3 side.
Question is how i connect R/3 to BI ?
I will have to create RFC Connection , Yes ?
I did following steps , so far, PLEASE LET ME KNOW WHAT ELSE TO DO ???
1 To call the RFC we have to create destination.
Means Source system and Target system.
Source System: From where we are calling the RFC i.e. Source system. = R/3
Target System: To where it is calling i.e. Target system. = BI
2. In Source System, create DESTINATION
Goto SM59 to Create a RFC Destination.
3. In SM59 First screen you will get list of RFC Destions
Select R/3 Connections and Click on list(+)symbol it will gives already created Destions, Select R/3 Connections click on Create buttion, it will takes you into another screen to create Destionation.
Name, Password, Logon details.
once it is saved you can test it. Click on Test Connection Button
if it is executed successfully your destinatio is established
NOW WHAT DO I HAVE TO DO IN BI SIDE ????
i went to RSA1 -> source systems
Here i dont see my R/3 in source systems...
please give me step by step instructions.

Hi
See SAP Help
http://help.sap.com/saphelp_nw2004s/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/content.htm
Connecting ECC6.0 and SAP BI
Setting-Up a Connection between BW and R/3 for Data Load
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/908836c3-7f97-2b10-4cb8-e6790361c152&overridelayout=true
Configuring RFC in BI7 for connecting ECC6 server:
Connecting ECC6.0 and SAP BI
Thanks
Reddy

Creating source system in RSA1

Hi guys,
Im trying to create a source system in the TC RSA1 between R/3 PRO y BW PRO. But at the end of the process it sent me the message Source system already exists. There is no other source system for R/3 created. What can it be?
Thanks a lot
Regards,
Vic

Hi Vic,
Goto sm59 and delete the logical system for the R/3 system and retry the steps again.
Check this doc:
http://help.sap.com/bp_biv135/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
The steps for creating source system (automatic option in RSA1)is as follows:
1.Create remote logons in both the systems.
2.RSA1 -> Source system -> Create source system -> automatic creation
3. Enter the details of the R/3 system and the Remote logon ids of both the system. In case you are using BI 3.5 or greater + R/3 4.7 or greater the password is "case sensitive" hence have all the passwords in CAPS.
4. Now the system would create a remote logon and show up the remote logon screen. In that screen -> "logon and security" -> enter the remote logon id and password and save. Now the remote logon should not work from there.
The connection is established.
Bye
Dinesh

How To create a new R/3 source System ?

Hello,
Can somebody guide me to a white paper or something related which explains in detail how to create a new R/3 source System in BW?

hi jay,
while i don't have a white paper, it was as simple as right-clicking the source systems tree in AWB and creating a new one - the process is simplified if you're using release 3.0E up, but i can't help you much if not. but you basically have to create an RFC connection to the source system, create a BW user, assign the IDOCs properly (this one i don't know how to do), and linking them all up together in one source system.
if i come across any notes, i'd be more than happy to help.
i'll try asking our Basis people too, just in case they know of anything i could point you at.
ryan.

Create ECC source systems to talk to BI

I am a developer and the system that I am working with do not have the source systems created. There is no Basis support here yet. Would someone help by listing the steps to create the source systems, so that the ECC systems can talk to the BI NW2004s system? I want to be able to load data.

Hi,
Please check these links.
Connection between Source Systems and BW
http://help.sap.com/saphelp_nw70/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
Creating SAP Source Systems
http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
BW connectivity(.doc)
http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
hope this helps
Regards.

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

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, <b>if you right click on source system and go with check</b>...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 <b>RSADMIN</b> 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.

Multiple usage of Source System is not possible with installed DMIS version on source

Hello folks!
I`ve got a problem trying to adjust the Data Replication to SAP BW (on HANA) using SAP LT Replication Server.
I`ve deleted one connection and after that I`m trying to create new one through Configuration & Monitoring Dashboard (transaction LTR) with the same source / target systems.
As result when on the second step (Specify Source System) I specify RFC destination of the source system it appears an error with text
"Multiple usage of Source System is not possible with installed DMIS version on source".
But there`s no any adjusted connection in system now..
Please, help me to understand how to fix that problem, I can`t find a solution

Hi,
When you say that you 'deleted one connection', did you delete the RFC connection or the SLT Configuration? If it is not a real multiple usage scenario, then deactivate the 'allow multiple usage' flag, else install the correct DMIS version on both SLT and source.
Thanks
kris

DELETE OLD SOURCE SYSTEM IN BW

Hello.
We have one source system created a few years ago but source system physically doesn´t exits.
I tried to delete it in RSA1, but we got many errors causes there´s not any system whith this physicall and logical name.
I can execute function RSAP_BIW_DISCONNECT and disconnect it, but I have a lot of entries of that system in tables like RSISOSMAP. I think that we have many transfer rules and PSA tables with this system
Are there any procedure to delete an old source system manually?
Kind regards.
Marta

Thank you Manga.
But I have a question...
If I execute function, what happens with transfer rules and PSA tables?
We want to clean about this old source system data.
Thank you

Source System create - RSAR 374 Error

Similar Messages

Maybe you are looking for