RSTRAN & RSBKDTP doesn't convert source system

Dear All,
after a system copy from BWP to BWT, and the opportune post-activities (BDLS & change of conversion of source system name after transport), there's a problem with the transport from BWS in BWT of transformation and DTP objects that, respect in table RSTRAN (Transformation) and in RSBKDTP (BW: Data Transfer Process Header Data) does not convert the source system.
We transport first the datasource and then the cube destination of the ETL (with RC 0, datasource source system correctly updated from SVICNLT111 to TSTCNLT111).
Then we transport the trasformation and the related DTP (with error, RC 8, because this objects are not avaiable in the source system - and they remains in association with SVI source system).
For example the trasformation "abcdfe" starts in BWS with the correct association of datasource "ghilmno SVICNLT111" but when it arrives in BWT in the table RSTRAN without change the source system but remain the association with datarource "ghilmno SVICNLT111" instead of the correct association datarource "ghilmno TSTCNLT111".
The same thing appened for DTP objects in the table RSBKDTP.
Thank's for help,
best regards
Giorgio - Milan

The solution is descibed within note
http://service.sap.com/sap/support/notes/2009368
Reports:
RSTRAN_BDLS (to correct the transformations so that the DTP is assigned to the correct one)
RSBKDTP_BDLS
RSBK_REPAIR_BDLS (corrects inconsistencies on the RSBKDTP table)

Similar Messages

Transformation issue while connecting multiple source system of same type..

Hi,
I'm working on APO-BW integration project. I want to connect BW QA & BW PROD to APO QA. I've already connected BW QA to APO QA & it is fetching data correctly. RFC part & other BASIS part is already taken care of. I've done export datasource (for mater data, cube etc) in BW PROD & replicated in APO QA. All BW PROD datasources are imported as RSDS (7.X) in APO QA.
Now my question is how to make sure the transformations will take source system as BW PROD too? I want 2 datasources (one from BW QA & other from BW PROD) to connect to same inforprovider in APO. I've transported 7.x datsource from APO DEV to APO QA environment along with transformations. In conversion of logical system names in APO QA I've given source system -BW DEV & target system - BW QA. So the transformation automatically takes data source as BW QA. It doesn't take source-system - BW DEV & target system - BW PROD as it conflicts previous setting.
Is only option that I need to manually maintain transformation from BW PROD datasource or there's another better alternative?

HI,
You are getting multiple IDOCs into BPM. But output you are getting one message right? IF so, your N:1 Mapping is not done correctly.
i.e your target message type should have occurence of 1..n and also the interface mapping. Closely obsever the N:1 mapping done in the BpmPatternCollectMerge.
Also go to SXMB_MONI->PE and check the Technical Details to make sure that, you are getting multiple IDOCs and you are executing the N:1 Transformation step correctly.
Also in the N:1 Mapping, check out the context you used. Make it root . Then test the mapping independently in the Integration Repository.
Hope it helps,
Regards,
Moorthy

Delta in source system doesn't work

I've created delta-enabled generic datasource. The delta field is timestamp field. I've done Initial Delta run, posted couple new records with appropriate timestamps, tried to run delta but it doesn't work. Even on test delta run RSA3 in source system.
Why?

Hi Gediminas,
You need to maintain safety intervals(at least lower limit)
Check: [How tou2026 Create Generic Delta|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Hope it Helps
Srini

BDLS is not converting DataSource source systems

After running BDLS on our BW system to convert from logical system DV1220 to ED2CLNT220 we found that the source system assignments for our datasources are not getting converted. Specifically table RSISOSMAP which holds the mapping between the infosource and the OLTP system. We did check several of our ODS's and Info-cubes and the logical system were changed from DV1220 to ED2CLNT220.
Any help would be appreciated.
Regards,
Mike...

Mike,
After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
Refer to the below doc for detail. Also refer to note 886102.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
Below note talks about similar issue.
How to change all infosources to the new source system automatically
Hope this helps.

Source system conversion doesn't work after transport

Just transported a query to BW Production and found that the source system is still the same as in DEV.
The conversion is there (QAS-->PRD). But the conversion doesn't seem working in the transport.
Can anyone tell me how to troubleshoot this issue?

Hi,
Please check the following:----
1. RSA1->Source Systems --> Select the source system -->Check. It should take you to the correct source system with a Remote logon.
2. Check the logical system mappings in RSLOGSYSMAP table.
3. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70a7b233-8be5-2c10-4190-aed723af5373
Regards,
Suman

0HR_PA_EC_01 Extractor error converting from currency in source system

Hi all,
when I run the standard extractor 0HR_PA_EC_01 , I get the following error message in the source system (application log):
Error converting currency from USD to on 09/03/2008
Message no. HRECM00SERVICE006
Thus, the requst in the PSA in BI / BW is Red.
Any recommendations?
Points will be assigned.
Thanks

Rajan,
You can try this function module for converting currency from one format to another format...
CONVERT_TO_FOREIGN_CURRENCY...
other wise... you can try with this function module..
RSW_CURRENCY_TRANSLATION............ this one i'm not sure abt that will convert ur data into required format..

DataSource for 0SD_C02 doesn't exist in Source System

Hi Friends,
I think the title explain all the problem.
I want to load the 0SD_C02 infocube and I know that I have to do it with the infosource 2LIS_01_S005, but when I go to R/3 to search for it, the system tells me that it doesn't exist.
I've proved with the Tcode RSA3 to verify the extractor and it gives me the same answer "Infosource 2LIS_01_S005 doesn't exist in Source System".
Does anybody know how to load this infocube?
Thanks in advance.
Francis.
Following with the same problem.
I want to load data on 0SD_C02, 0SD_C03 & 0SD_C05. C03 & C05 has datasources named like 2LIS_11/2/3... I have these ones in R/3, but the datasources named like 2LIS_01_* aren't exist in R/3,
How can I load data in these infocubes?
Thanks in advance,
Francis.
Message was edited by:
Francis Estevez

I think you have to install it via RSA5 transaction in your source system...
Hope it helps!
Bye,
Roberto

Doesn't load from source system to PSA and DSO

Hi Gurus,
We have launched a Delta load from Source System (POSDM) to DSO. In the source system there are 5000000 rows but none was loaded into DSO or PSA. The delta load was ok, but any data was loaded.
If the delta load was lunch again, would be loaded those 5000000 rows. Or those 5000000 rows wouldn't be able to load again.
Any idea abut this issue? Any feedback will be really appreciated.
Thanks in advance.

Hi David,
Are you sure this 5 million records are delta records and should be pulled into BW as delta??
did you count the number of records in the underlying tables??
which data source you are using??
Delta loads are suppose to bring the new records or changed records since the last data load and not all the records.
Since the request is green as you said and still it shows 0 records then it is possible that nothing has changed since last delta.try to see the details of the data load... if it failed...may be thats the reason you are not able to see any records.
If you schedule the delta again it will bring the records changed or created after last delta.
If the delta was unsuccessfull then turn the QM status and overall status of request to red manually in the monitor of the request and delete it from PSA and all the targets in which its loaded and schedule the delta again and it should bring the delta.
Thanks
Ajeet
Thanks
Ajeet

Changes in source system dyring Unicode conversion

Hi,
I've upgraded our R/3 non-Unicode installation to ERP 6.0 non-Unicode using CU&UC guide. Now I plan to do the export & import phase to migrate the source system to Unicode.
My question is, does the export phase (where the Unicode conversion actually takes place) do any changes in the source system? It' is a production system, and when something goes wrong or the time exceeds the limit I have for the export, I need to stop the export, put it back to production and try another time. So I need to be sure that the export itself doesn't do any changes to the source system.
Thanks in advance
Tomas

Hi Tomas,
the export simply "copies" the source system (and converts the data to Unicode) - it does not change it.
Therefore you can still use it after the export is finished.
Best regards,
Nils Buerckel
SAP AG

Error while trying to export with Preview: 'unable to convert NSNamedColorSpace System controlColor to Device RGB colorspace'

When I try to export a PDF with preview, the dialog doesn't show and this error appears in the system log.
11/2/13 2:01:01.684 PM Preview[828]: -[NSRemoteView viewDidMoveToWindow] caught non-fatal NSInternalInconsistencyException 'unable to convert NSNamedColorSpace System controlColor to Device RGB colorspace' with backtrace (
          0   CoreFoundation                      0x00007fff8e24d41c __exceptionPreprocess + 172
          1   libobjc.A.dylib                     0x00007fff8a400e75 objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff8e24d1f8 +[NSException raise:format:arguments:] + 104
          3   Foundation                          0x00007fff8be42c61 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189
          4   ViewBridge                          0x00007fff8a08165c -[NSSecureColor initWithColor:] + 724
          5   ViewBridge                          0x00007fff8a08136f +[NSSecureColor secureColorWithColor:] + 48
          6   ViewBridge                          0x00007fff8a0a4cfb -[NSRemoteView sendFontSmoothingBackgroundColorToService:] + 40
          7   ViewBridge                          0x00007fff8a0a5bf5 -[NSRemoteView viewDidMoveToWindow] + 197
          8   AppKit                              0x00007fff881461d0 -[NSView _setWindow:] + 2899
          9   AppKit                              0x00007fff88143804 -[NSView addSubview:] + 364
          10 AppKit                              0x00007fff88157953 -[NSFrameView addSubview:] + 45
          11 AppKit                              0x00007fff88165cb5 -[NSWindow setContentView:] + 511
          12 AppKit                              0x00007fff889cb233 -[NSVBSavePanel init] + 287
          13 AppKit                              0x00007fff8874d5b9 +[NSSavePanel newRemotePanel] + 309
          14 AppKit                              0x00007fff8874d675 +[NSSavePanel _crunchyRawUnbonedPanel] + 120
          15 AppKit                              0x00007fff885a54fc -[NSDocument _preparedSavePanelForOperation:] + 260
          16 AppKit                              0x00007fff885a5f6f __85-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_2 + 320
          17 AppKit                              0x00007fff885d5910 -[NSDocument _commitEditingThenContinue:] + 501
          18 AppKit                              0x00007fff885d5abd -[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:] + 138
          19 AppKit                              0x00007fff885a5e20 __85-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke + 375
          20 AppKit                              0x00007fff885989b8 -[NSDocument _processActivity:blockingMainThread:] + 1373
          21 AppKit                              0x00007fff88599921 -[NSDocument performActivityWithSynchronousWaiting:usingBlock:cancellationHandler:] + 220
          22 AppKit                              0x00007fff885a5c9a -[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:] + 137
          23 Preview                             0x000000010392901b Preview + 917531
          24 AppKit                              0x00007fff8834d3d0 -[NSApplication sendAction:to:from:] + 327
          25 AppKit                              0x00007fff88368348 -[NSMenuItem _corePerformAction] + 394
          26 AppKit                              0x00007fff88368084 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117
          27 AppKit                              0x00007fff883b74dd -[NSMenu _internalPerformActionForItemAtIndex:] + 35
          28 AppKit                              0x00007fff883b7359 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104
          29 AppKit                              0x00007fff8835e176 NSSLMMenuEventHandler + 716
          30 HIToolbox                           0x00007fff8973c6d4 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 892
          31 HIToolbox                           0x00007fff8973bc87 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 385
          32 HIToolbox                           0x00007fff8974fd90 SendEventToEventTarget + 40
          33 HIToolbox                           0x00007fff89785a30 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 420
          34 HIToolbox                           0x00007fff897b8618 SendMenuCommandWithContextAndModifiers + 59
          35 HIToolbox                           0x00007fff897b85c4 SendMenuItemSelectedEvent + 178
          36 HIToolbox                           0x00007fff897b84a5 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 94
          37 HIToolbox                           0x00007fff897c0425 _ZL14MenuSelectCoreP8MenuData5PointdjPP13OpaqueMenuRefPt + 718
          38 HIToolbox                           0x00007fff897c0051 _HandleMenuSelection2 + 446
          39 AppKit                              0x00007fff882d079c _NSHandleCarbonMenuEvent + 284
          40 AppKit                              0x00007fff8812f56e _DPSNextEvent + 2170
          41 AppKit                              0x00007fff8812e8db -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
          42 AppKit                              0x00007fff881229cc -[NSApplication run] + 553
          43 AppKit                              0x00007fff8810d803 NSApplicationMain + 940
          44 libdyld.dylib                       0x00007fff868025fd start + 1
          45 ???                                 0x0000000000000001 0x0 + 1
timestamp: 14:01:01.684 Saturday 02 November 2013
process/thread/queue: Preview (828) / 0x7fff741cc310 / com.apple.main-thread
code: line 607 of /SourceCache/ViewBridge/ViewBridge-46/ViewBridgeUtilities.m in logCaughtException
domain: exceptions

When I try to export a PDF with preview, the dialog doesn't show and this error appears in the system log.
11/2/13 2:01:01.684 PM Preview[828]: -[NSRemoteView viewDidMoveToWindow] caught non-fatal NSInternalInconsistencyException 'unable to convert NSNamedColorSpace System controlColor to Device RGB colorspace' with backtrace (
          0   CoreFoundation                      0x00007fff8e24d41c __exceptionPreprocess + 172
          1   libobjc.A.dylib                     0x00007fff8a400e75 objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff8e24d1f8 +[NSException raise:format:arguments:] + 104
          3   Foundation                          0x00007fff8be42c61 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189
          4   ViewBridge                          0x00007fff8a08165c -[NSSecureColor initWithColor:] + 724
          5   ViewBridge                          0x00007fff8a08136f +[NSSecureColor secureColorWithColor:] + 48
          6   ViewBridge                          0x00007fff8a0a4cfb -[NSRemoteView sendFontSmoothingBackgroundColorToService:] + 40
          7   ViewBridge                          0x00007fff8a0a5bf5 -[NSRemoteView viewDidMoveToWindow] + 197
          8   AppKit                              0x00007fff881461d0 -[NSView _setWindow:] + 2899
          9   AppKit                              0x00007fff88143804 -[NSView addSubview:] + 364
          10 AppKit                              0x00007fff88157953 -[NSFrameView addSubview:] + 45
          11 AppKit                              0x00007fff88165cb5 -[NSWindow setContentView:] + 511
          12 AppKit                              0x00007fff889cb233 -[NSVBSavePanel init] + 287
          13 AppKit                              0x00007fff8874d5b9 +[NSSavePanel newRemotePanel] + 309
          14 AppKit                              0x00007fff8874d675 +[NSSavePanel _crunchyRawUnbonedPanel] + 120
          15 AppKit                              0x00007fff885a54fc -[NSDocument _preparedSavePanelForOperation:] + 260
          16 AppKit                              0x00007fff885a5f6f __85-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_2 + 320
          17 AppKit                              0x00007fff885d5910 -[NSDocument _commitEditingThenContinue:] + 501
          18 AppKit                              0x00007fff885d5abd -[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:] + 138
          19 AppKit                              0x00007fff885a5e20 __85-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke + 375
          20 AppKit                              0x00007fff885989b8 -[NSDocument _processActivity:blockingMainThread:] + 1373
          21 AppKit                              0x00007fff88599921 -[NSDocument performActivityWithSynchronousWaiting:usingBlock:cancellationHandler:] + 220
          22 AppKit                              0x00007fff885a5c9a -[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:] + 137
          23 Preview                             0x000000010392901b Preview + 917531
          24 AppKit                              0x00007fff8834d3d0 -[NSApplication sendAction:to:from:] + 327
          25 AppKit                              0x00007fff88368348 -[NSMenuItem _corePerformAction] + 394
          26 AppKit                              0x00007fff88368084 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117
          27 AppKit                              0x00007fff883b74dd -[NSMenu _internalPerformActionForItemAtIndex:] + 35
          28 AppKit                              0x00007fff883b7359 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104
          29 AppKit                              0x00007fff8835e176 NSSLMMenuEventHandler + 716
          30 HIToolbox                           0x00007fff8973c6d4 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 892
          31 HIToolbox                           0x00007fff8973bc87 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 385
          32 HIToolbox                           0x00007fff8974fd90 SendEventToEventTarget + 40
          33 HIToolbox                           0x00007fff89785a30 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 420
          34 HIToolbox                           0x00007fff897b8618 SendMenuCommandWithContextAndModifiers + 59
          35 HIToolbox                           0x00007fff897b85c4 SendMenuItemSelectedEvent + 178
          36 HIToolbox                           0x00007fff897b84a5 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 94
          37 HIToolbox                           0x00007fff897c0425 _ZL14MenuSelectCoreP8MenuData5PointdjPP13OpaqueMenuRefPt + 718
          38 HIToolbox                           0x00007fff897c0051 _HandleMenuSelection2 + 446
          39 AppKit                              0x00007fff882d079c _NSHandleCarbonMenuEvent + 284
          40 AppKit                              0x00007fff8812f56e _DPSNextEvent + 2170
          41 AppKit                              0x00007fff8812e8db -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
          42 AppKit                              0x00007fff881229cc -[NSApplication run] + 553
          43 AppKit                              0x00007fff8810d803 NSApplicationMain + 940
          44 libdyld.dylib                       0x00007fff868025fd start + 1
          45 ???                                 0x0000000000000001 0x0 + 1
timestamp: 14:01:01.684 Saturday 02 November 2013
process/thread/queue: Preview (828) / 0x7fff741cc310 / com.apple.main-thread
code: line 607 of /SourceCache/ViewBridge/ViewBridge-46/ViewBridgeUtilities.m in logCaughtException
domain: exceptions

Error when activate a SAP source system

Hello Experts,
I have an issue when I try to create a new SAP source system but I cannot complete this operation because a Timeout error occurs when the system made the destiny verification, the source system can be created but not activated, I already create the RFC connection and they are OK, I add the new logical system of the source system in the configuration (SBIW) in the general settings,and the data source tree is show succesfully and sems to work OK and the data sources seems to be OK too.
In the RSA1 transaction, go to source systems tree, choose the SAP source system called: "conexion a dev 200" -> right click and choose activate and the error occurs.
I have a Myself source system already created and activated, I cannot find the source of the problems thata cause the timeout error in the new source system.
Thank you vey much in advance,
Niurka

Yes, I try ti use the create automatically option first but it doesn't work, because says that we system already exists because here exist a myself source system with an RFC to R/# ( I don't know why), so I must use the manually creation option, I put the logical system, and all the requeriments of the screem. The system create the source system but when I try ti activate it, it is impossible to do it....!
I hope that you can give some tips or solution for this issue,
Thanks!

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.

InfoSource 8ODS_SLS is not defined in the source system

Hi Guys,
    When I tried to load data from ODS to Infocube, I am getting the following error.
InfoSource 8ODS_SLS is not defined in the source system
      Source System is not R/3. It is just a flat file and data was uploaded into ODS. When transferring the data from ODS to Infocube, I get this problem. And I have defined the update rules for infocube and also given the infosource name as ODS.
      But the data is not getting uploaded in the Infocube.

First replicate your BWSELF system.
Then, Run this program in SE38:
rs_transtru_activate_all
Enter the source system (your BW system)
Enter the datasource (8ODS_SLS).
If you get an error message immediately, the datasource doesn't exist. If it runs, check and make sure you get no error messages.
/smw

Error while source system creation/Source system transport

Hi,
     In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
     Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
     I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
     Message no. RSAR502
Diagnosis
     With Remote Function Call to system GWPCLNT900 error connection closed
     (no data) ccurred.
Procedure
     Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
Krishna

Hi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier

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

RSTRAN & RSBKDTP doesn't convert source system

Similar Messages

Maybe you are looking for