Note 1478123 - FAQ - Source System

8/13/2019 Note 1478123 - FAQ - Source System

http://slidepdf.com/reader/full/note-1478123-faq-source-system 1/5

SAP Note

Header Data

Symptom

Source system issues. FAQ

Other Terms

RSA1 , Source system, RSBASIDOC, BDLS, System copy, IDoc, RFC, SM59

Reason and Prerequisites

Errors during source system connectivity.

Solution

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

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

l

To check consistency in backend tables and transactions, you can get the details for correct BW source system connection with followingprocedures:

a) Determine the logical system name of the BW and the SAP source system SE16 T000 => Field LOGSYS of the client you are checking b) Check if the BW has a connection to SAP source system and vice versa Connection information is stored in table RSBASIDOC. This

table has the assignment of source system to BW. Some of the important fields are:SLOGSYS: Source system (logical system name of source system) 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 in fields SLOGSYS, RLOGSYS, BIDOCTYP, TSPREFIX andSRCTYPES which is identical 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 as the logical system name of the BW system.On SAP sourcesystem: SM59 -> Double click on the destination Check the target host: Compare the hostname to the server name of the

BW system (SM51) Check the RFC Logon data: Menupath -> Test -> Authorization.In case the maintained user is a DIALOG user you can also perform a remote login. Check if the update user in the BW system has the

authorization 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 sourcesystem RFC -Destination by table RSLOGSYSDEST or function module

RSAR_DESTINATION_GET.To check the authorization, select SM59-> Menupath -> Test -> Authorization . In case the maintained user is a DIALOG user you can also

perform a remote login.Check if the user in the source system has the authorization profile 'S_BI-WX_RFC' (Note 150315)<LOGSYS > _DIALOG destination is necessary for F4 help in the infopackage or for source system calls from monitor.Maintained user has

to be of type DIALOG (check in transaction su01)e) Check the partner definitions: Check the Partner Type LS parameter setting of transaction WE20 in both 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 ' RFC destination ' make sure that this RFC points to the correct source system insm59

Inbound message type: RSINFO RSSEND

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

RSINFO ' double click ' receiver port ' double click ' RFC destination ' make sure that this RFC points to the correct BW system in sm59

1478123 - FAQ: Source system

Version 7 Validity: 16.12.2010 - active Language Anglais

Released On 17.12.2010 10:06:04

Release Status Released for Customer

Component BW-WHM-DST-SRC Source Systems

Priority Recommendations / Additional InfoCategory FAQ



RSSEND ' double click ' receiver port ' double click ' RFC destination ' make sure that this RFC points to the correct BW system in

sm59Inbound Parameter

RSRQST

2. What are the relevant authorizations for background user?

l The RFC user on BW, receiving data from OLTP system, should have profiles: S_BI-WHM_RFC

l The RFC user on OLTP, receiving request from BW system, should have profiles: S_BI-WX_RFC

l Human administrator in both systems with S_RS_ALL

l

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 BW system.

"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 the R3 system, both the system must have same Idoc type. If in thesource system the connection is not known and if the BIDOCTYP of the BW is not used for another connection in the sourcesystrem or if theIDoctype is different due to a system copy try to restore the connection between BW and the relevant source system. You can do this by restoringthe souresystem by:

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

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

4. How to disconnect all obsolete links to BW?

In the R3 system execute the function module RSAP_BIW_DISCONNECT to disconnect all obsolete BW links. Never execute this function modulein a 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 causes the 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 function module

Never execute this function module in a BW system!

5. User and passwordCheck note 807895 especially for connection with different releases where a BASIS release higher 640 is involved. In that case it issuggested to use a password which is not longer than 8 characters and has no lower case letters.

6. Unicode settings for RFC connection

Transaction SM59 -> <LOGSYS> -> go to "MDMP & Unicode tab" > can only 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. Myself connection is created the first time your call the AWB (RSA1). From a

technical point of view, the mySelf connection is a just a standard source system connection pointing to itself. Therefore maintenance of targetsystem, client and user is not necessary in transaction sm59. (note 538052).

Known issue during transports for export datasources: If only client is maintained or if you maintain only user and password but no client.

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 entries in the

partner profile tables (EDP*) but if there are already entries concerning the partner profile, you will get error such as E0412.

Before solving the issue concerning the partner profile, check if an entry exists in table RSBASIDOC for the myself connection.SLOGSYSand RLOGSYS = logical system name of BW Source system SRCTYPE = M

In case of a running BW create an OSS message if there is no entry for the myself connection. The myself connection has to be created indebugging because of the usage of the right prefix.

In case it is the first time you call RSA1 and no transferstructures exist, you can clean the partner profiles by creating manually an entry intransaction we20 for the logical system name of BW and delete afterwards again. In that case the system will delete existing entries from tableEDP* for the myself connection.

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 the logical system name. Check table RSBASIDOC if the connection is using

the logical system name.In order to avoid such errors, please make sure to follow note consulting 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 time Error "DYNPRO_SEND_IN_BACKGROUND" are system is not

open for changes (see point XX ) or for the background not the correct authorization profile has to bee maintained. (see point XX)

The runtime error means that the OLTP systems wanted to send a dynpro, but the output did not work because the user (usually called ALEREMOTE) is no dialog user. If you want to see the message, you can set the remote user temporarily to dialog user.then you can see whichmessage is send by the OLTP system to the 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 objectswill be deleted (infopackages, datasources, transferstructure, Those objects will also not be available if you create a new connection. Onlypossibility in order to avoid manually creation is to create a transport request "SAVE for SYSTEM Copy" in another system and import that requestinto BW. Do not forget to maintain RSLOGSYSMAP in the correct way.

If the source system does not know BW as there is no entry in RSBASIDOC because e.g. you executed function moduleRSAP_BIW_DISCONNECT in the source system, 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

l In transaction WE30:The type Zxxxxx of table RSBASIDOC for the concerning connection must exist in BW and in the source system. It mustbe identical in structure in both systems If it does not exist, create it as a copy of type RSSEND.

l Afterwards, enter the following in the view maintenance of view EDIMSG (trans. SM30):

l Message type RSSEND, IdocType as specified above, Release corresponding to the release you are currently using.

11. System Copy

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

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

a) System copy term definition

Term definition

l Homogeneous system copy:

The operating system and database system are the same for both source and target systems

l 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

l PRD -> PRD: target landscape will replace the previous production (source) landscape and will become the new production landscape.thisapplies for example if the operating system, the database system or some main hardware components of a production system are to bechanged.

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

l new installation: the target NPS landscape does not exist

l Refresh: target NPS landscape does already exist and only the data will 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

l 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, WE215. Adjustment of RSLOGSYSDEST mapping

l 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 the system

copy)Delete all SAP sourcesystems and BW connections in the target BW

1. Technical copy process 2. Reduce number of BTC to 0 in RZ10 3. check RSLOGSYSDEST and change the RFC connection to a non existing 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

l Main procedures: Scenario C

1. Technical copy process 2. Reduce number of BTC to 0 in RZ10 3. Delete obsolete RSBASIDOC-entries via RSAP_BIW_DISCONNECT4. Run BDLS 5. Restore connections in test BW

d) BDLS

BDLS convert tables that have domains LOGSYS and EDI_PARNUM in a system. Execute BDLS first in test run. After this run you get a listof all tables and how manye ntries are to be converted per table.

l Running BDLS in general 4 scenarios can happen:

a)No records for either the old or the new name -> table skippedb)Records with the old name exist -> conversion goes throughc)Records with the new name exist -> table skipped with warning no manual intervention needed, but doublecheck is recommended.In this

case the conversion log shows '<<' at the affected tablesd)Records with the old and the new name coexist -> records are skipped with warning or error (depending on the flag for existence check,

which is always set except in test conversions) you have to analyze the records which hold the old logical name and have their identicalcounterparts holding the new name. In this case the conversion log shows '<<<<' at the affected tables.

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

l Known issues when starting BDLS

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

l 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, delete the old conversion protocol by transaction BDLSS or reportRBDLSMAP_RESET.

Renaming of a productive system is not officially supported!

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (6)

1319517 Unicode Collection Note

140276 Error in source system assignment

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

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

184971 Notes on BW source system connections

886102 System Landscape Copy for SAP NetWeaver BW

1087980 ECC Source systems appearing in BI folder

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

1319517 Unicode Collection Note

886102 System Landscape Copy for SAP NetWeaver BW

1087980 ECC Source systems appearing in BI folder

Documents

Note 1478123 - FAQ - Source System