sapnote_0001478123.pdf

08.04.2013 of 10

SAP Note 1478123 - FAQ: Source system

Note Language: English Version: 7 Validity: Valid Since 16.12.2010

Summary

SymptomSource system issues. FAQ

Other termsRSA1 , Source system, RSBASIDOC, BDLS, System copy, IDoc, RFC, SM59

Reason and PrerequisitesErrors during source system connectivity.

Solution

1. How to check if the source system connection is proper?

o In the BW administrator workbench (RSA1), select the context menuof relevant source system and select check. You should get themessage 'Source system connection <LOGSYS > ok.

o To check consistency in backend tables and transactions, you canget the details for correct BW source system connection withfollowing procedures:

a) Determine the logical system name of the BW and the SAP sourcesystem SE16 T000 => Field LOGSYS of the client you are checking

b) Check if the BW has a connection to SAP source system and viceversa Connection information is stored in table RSBASIDOC. Thistable has the assignment of source system to BW. Some of theimportant fields are:

SLOGSYS: Source system (logical system name of sourcesystem)

RLOGSYS: Receiver system (logical system name of BW system)

OBJSTAT: Object Status

BIDOCTYP: Basic type

TSPREFIX: Transfer structure prefix for a source system

SRCTYPE: Type of the source system

There must be exactly one entry in table RSBASIDOC, which exists infields SLOGSYS, RLOGSYS, BIDOCTYP, TSPREFIX and SRCTYPES which isidentical in BW and in the source system.

Manual changes in table RSBASIDOC are not allowed!

c) Check the RFC destination in the SAP sourcesystem:

On the SAP sourcesystem the RFC-Destination has the same name asthe logical system name of the BW system.

08.04.2013 of 10


On SAP sourcesystem: SM59 -> Double click on the destination Checkthe target host: Compare the hostname to the server name of the BWsystem (SM51) Check the RFC Logon data: Menupath -> Test ->Authorization.

In case the maintained user is a DIALOG user you can also perform aremote login. Check if the update user in the BW system has theauthorization profile : 'S_BI-WHM_RFC' (Note 150315)

d) Check the RFC destination in the BW system:

On the BW system you can get the name of the SAP sourcesystemRFC-Destination by table RSLOGSYSDEST or function moduleRSAR_DESTINATION_GET.

To check the authorization, select SM59-> Menupath -> Test ->Authorization . In case the maintained user is a DIALOG user youcan also perform a remote login.

Check if the user in the source system has the authorizationprofile 'S_BI-WX_RFC' (Note 150315)

<LOGSYS >_DIALOG destination is necessary for F4 help in theinfopackage or for source system calls from monitor.Maintained userhas to be of type DIALOG (check in transaction su01)

e) Check the partner definitions:

Check the Partner Type LS parameter setting of transaction WE20 inboth systems and search the logical system name in Partner Type LS:

BW system: search for the logical system name of the partner system

Outbound message type:

RSRQST ' double click ' receiver port ' double click ' RFCdestination ' make sure that this RFC points to the correctsource system in sm59

Inbound message type:

RSINFORSSEND

Source system: search for the logical system name of the BW system

Outbound parameter

RSINFO ' double click ' receiver port ' double click ' RFCdestination ' make sure that this RFC points to the correct BWsystem in sm59

RSSEND ' double click ' receiver port ' double click ' RFCdestination ' make sure that this RFC points to the correct BWsystem in sm59

08.04.2013 of 10


Inbound Parameter

RSRQST

2. What are the relevant authorizations for background user?

o The RFC user on BW, receiving data from OLTP system, should haveprofiles: S_BI-WHM_RFC

o The RFC user on OLTP, receiving request from BW system, should haveprofiles: S_BI-WX_RFC

o Human administrator in both systems with S_RS_ALL

o See Note 150315

XX. system changeability during creation of sourcesystem connection

+ changeability in transaction scc4

- Client-independent customizing and repository changes

+ object changeability in SE06

- Changes in the customer namespace- Changes in the local namespace

3. How to correct the error related to IDOC mismatch between source and BWsystem.

"BI unknown in source system"."BI Idoc type<XXXXXX> is not the same as source system".

Note the BIDOCTYP field entry in table RSBASIDOC in BW and in theR3 system, both the system must have same Idoc type. If in thesource system the connection is not known and if the BIDOCTYP ofthe BW is not used for another connection in the sourcesystrem orif the IDoctype is different due to a system copy try to restorethe connection between BW and the relevant source system. You cando this by restoring the souresystem by:

RSA1 -> Source system <xxxx> Select "Restore" from context menu.

When you were asked if you want to delete the source system duringrestore procedure, please select delete option; the source systemwill be rebuilt after the restore.

4. How to disconnect all obsolete links to BW?

In the R3 system execute the function module RSAP_BIW_DISCONNECT todisconnect all obsolete BW links. Never execute this function module in a

08.04.2013 of 10


BW system!

Go to Transaction SE37 - function module RSAP_BIW_DISCONNECT >Single Test. Parameter

I_BIW_LOGSYS = <RLOGSYS> of RSBASIDOC

I_OLTP_LOGSYS =<SLOGSYS> of RSBASIDOC

I_FORCE_DELETE = 'X'.

DO NOT enter a value in the "RFC target sys" field. If you do, this causesthe function module to run in the system specified there.

Conditions for the function module:

1.RFC connection to RLOGSYS is ok; check transaction SM59

2.SLOGSYS = logical system name where you execute the functionmodule

Never execute this function module in a BW system!

5. User and password

Check note 807895 especially for connection with different releaseswhere a BASIS release higher 640 is involved. In that case it issuggested to use a password which is not longer than 8 charactersand has no lower case letters.

6. Unicode settings for RFC connection

Transaction SM59 -> <LOGSYS> -> go to "MDMP & Unicode tab" > canonly be changed or is relevant in a Unicode system. This setting isirrelevant on the Non-Unicode system.

XX. Myself connection

Needed for data distribution within a BW System. Myselfconnection is created the first time your call the AWB (RSA1).From a technical point of view, the mySelf connection is a justa standard source system connection pointing to itself.Therefore maintenance of target system, client and user is notnecessary in transaction sm59. (note 538052).

Known issue during transports for export datasources:

If only client is maintained or if you maintain only user andpassword but no client.

08.04.2013 of 10


7. RSA1 Logon issues

When you try to logon to RSA1 you see the error"Entry in inbound table already exist"

The "Myself" system is created the first time you call the AWB(RSA1). In case of inconsistency the system tries to create entriesin the partner profile tables (EDP*) but if there are alreadyentries concerning the partner profile, you will get error such asE0412.

Before solving the issue concerning the partner profile, check ifan entry exists in table RSBASIDOC for the myselfconnection.SLOGSYS and RLOGSYS = logical system name of BW Sourcesystem SRCTYPE = M

In case of a running BW create an OSS message if there is no entryfor the myself connection. The myself connection has to be createdin debugging because of the usage of the right prefix.

In case it is the first time you call RSA1 and notransferstructures exist, you can clean the partner profiles bycreating manually an entry in transaction we20 for the logicalsystem name of BW and delete afterwards again. In that case thesystem will delete existing entries from table EDP* for the myselfconnection.

8.Restore or creation issues

a)Sometimes you get message like 'Source system does not exist'(Message no.RSAR175)

Follow the procedure to analyze the issue

Check in the source system table T000 or transaction scc4 for thelogical system name. Check table RSBASIDOC if the connection isusing the logical system name.

In order to avoid such errors, please make sure to follow noteconsulting 886102 when doing system copy or renaming systems.

b)Error in source system <LOGSYS > (RSAR502)

The main problems, if you get the message "RSAR502" or/and run timeError "DYNPRO_SEND_IN_BACKGROUND" are system is not open forchanges (see point XX ) or for the background not the correctauthorization profile has to bee maintained. (see point XX)

The runtime error means that the OLTP systems wanted to send a

08.04.2013 of 10


dynpro, but the output did not work because the user (usuallycalled ALEREMOTE) is no dialog user. If you want to see themessage, you can set the remote user temporarily to dialoguser.then you can see which message is send by the OLTP system tothe BW system.

9.Source system deletion and reconstruction

If you delete a source system from context menu of RSA1 from the BW system,restore is not possible. Also all source system dependent objects will bedeleted (infopackages, datasources, transferstructure, Those objects willalso not be available if you create a new connection. Only possibility inorder to avoid manually creation is to create a transport request "SAVE forSYSTEM Copy" in another system and import that request into BW. Do notforget to maintain RSLOGSYSMAP in the correct way.

If the source system does not know BW as there is no entry in RSBASIDOCbecause e.g. you executed function module RSAP_BIW_DISCONNECT in the sourcesystem, restoring via context menu in BW and RSA1 is possible.

10.IDoc issue

You may get the error

"IDoc type Zxxxxx could not be found / Basic type Zxxxxxx does not exist"

Follow the steps given below

o In transaction WE30:The type Zxxxxx of table RSBASIDOC for theconcerning connection must exist in BW and in the source system. Itmust be identical in structure in both systems If it does notexist, create it as a copy of type RSSEND.

o Afterwards, enter the following in the view maintenance of viewEDIMSG (trans. SM30):

o Message type RSSEND, IdocType as specified above, Releasecorresponding to the release you are currently using.

11. System Copy

Follow the consulting note given below before doing any system copy orrefresh.

886102 System Landscape Copy for SAP NetWeaver BW1406273 Consulting: BDLS in BW

a) System copy term definition

08.04.2013 of 10


Term definition

o Homogeneous system copy:

The operating system and database system are the same for bothsource and target systems

o Heterogeneous system copy:

The operating system or database systemof the target system is different from the source system (also called OS/DB migration)

b) System copy scenario terminology

Scenario terminology according to consulting note 886102

o PRD -> PRD: target landscape will replace the previous production(source) landscape and will become the new productionlandscape.this applies for example if the operating system, thedatabase system or some main hardware components of a productionsystem are to be changed.

o PRD -> NPS: The production system landscape is copied (cloned) ontoa non-productive landscape, for example for creating a testenvironment

o new installation: the target NPS landscape does not exist

o Refresh: target NPS landscape does already exist and only the datawill be refreshed.

c) System copy scenario

BW landscape scenarios according to note 886102

Scenario A: Both system BW and source system are copied at the same time

Scenario B:Only BW is copied

Scenario C:Only source system is copied

o Main procedures: Scenario A

1.Technical copy process

2.Correction of the RFC connections in both systems

3.BDLS for own system and also in the copied connected system

4.Re-activation of the partner profiles in WE20, WE21

5.Adjustment of RSLOGSYSDEST mapping

08.04.2013 of 10


o Main procedures: Scenario B

PREPARATIONS

Transport request for system copy (optional, can be created e.g.on productive system or when deleting the sourcesystem after thesystem copy)

Delete all SAP sourcesystems and BW connections in the target BW


2.Reduce number of BTC to 0 in RZ10

3.check RSLOGSYSDEST and change the RFC connection to a nonexisting host in sm59

4.Delete source system connection with ignore

5.Run BDLS before RSA1 initially started

6.Create R/3 connections again, adjust RSLOGSYSMAP

7.Import transport request for system copy

o Main procedures: Scenario C


2.Reduce number of BTC to 0 in RZ10

3.Delete obsolete RSBASIDOC-entries via RSAP_BIW_DISCONNECT

4.Run BDLS

5.Restore connections in test BW

d) BDLS

BDLS convert tables that have domains LOGSYS and EDI_PARNUM in asystem. Execute BDLS first in test run. After this run you get alist of all tables and how manye ntries are to be converted pertable.

o Running BDLS in general 4 scenarios can happen:

a)No records for either the old or the new name -> table skipped

b)Records with the old name exist -> conversion goes through

c)Records with the new name exist -> table skipped with warning nomanual intervention needed, but doublecheck is recommended.In this

08.04.2013 of 10


case the conversion log shows '<<' at the affected tables

d)Records with the old and the new name coexist ->records areskipped with warning or error (depending on the flag for existencecheck, which is always set except in test conversions) you have toanalyze the records which hold the old logical name and have theiridentical counterparts holding the new name. In this case theconversion log shows '<<<<' at the affected tables.

BDLS log can be analysed in the application log (transaction SLG1).Select the following parameter:

Object CALESubobject LOGSYSNAME

o Known issues when starting BDLS

Information messages in the status line like "the new logicalsystem name XXX is assigned to the current client YYY" or "Thelogical system name XXX already exists" means that the logicalsystem name has already been changed (transaction scc4) . Press"enter" when this message appears and BDLS should continue with theconversion.

o Error message in the status line:

Another Process is Running for Conversion <LOGSYS > -> <LOGSYS >(Message no. B1668

Check if BDLS is still running. If no conversion is running, deletethe old conversion protocol by transaction BDLSS or reportRBDLSMAP_RESET.

Renaming of a productive system is not officially supported!

Header Data

Release Status: Released for CustomerReleased on: 17.12.2010 09:06:04Master Language: EnglishPriority: Recommendations/additional infoCategory: FAQPrimary Component: BW-WHM-DST-SRC Source Systems

08.04.2013 of 10


The Note is release-independent

Related Notes

Number Short Text

1319517 Unicode Collection Note

1087980 ECC Source systems appearing in BI folder

886102 System Landscape Copy for SAP NetWeaver BW

184971 Notes on BW source system connections

161570 User ALEREMOTE in the BW: Dialog user or system user?

150315 BW-Authorizations for Remote-User in BW and OLTP

140276 Error in source system assignment

sapnote_0001478123.pdf

Documents

Transcript of sapnote_0001478123.pdf