Please send the details of Notes-note-184754,407485

Question

Hai
Please send the details of Notes-note-184754,407485 to [email protected]
I will assing the points
kumar

Answer 1

Hi check it here.
<b>184754</b>
Summary
Symptom
CAUTION: THIS NOTE WAS REPLACED. FOR MORE UP-TO-DATE, COMPREHENSIVE INFORMATION SEE NOTE 886102.
You want to copy a single BW System of a system group using a database copy. After the copy, you want to have a functional BW source system connection.
Refer to Note 325525. This helps you to select the correct procedure for your scenario. Also note that there are several ways to carry out the actual copy procedure. This is not covered in this note. Refer instead to the URL http://service.sap.com/solutionmanagerbp.
Other terms
Database copy, source system, BW, connection, refresh
Reason and Prerequisites
There are three scenarios:
1. You want to install a new BW (referred to below as "target BW") by copying an existing BW (referred to below as "original BW"). That is, you import the copy onto an empty computer.
2. You want to replace an existing BW (henceforth "old BW"), by copying a different BW (henceforth "original BW"). That is, a BW was already installed on the target host (the old BW). We will call the copy of the original BW "target BW". There are two different scenarios here:
a) You are still in the planning phase of this step, that is, you have not yet made the copy.
b) You have already overwritten the old BW with the copy of the other BW.
Solution
You must perform ONLY THE STEPS required for YOUR SCENARIO.
Scenario 1): In 1.2B, create a transport request in the original BW that contains all source system-dependent objects for all R/3 and DataMart source systems. The object types are ISMT, ISTT and ISTS. Note that the ISTS object (the transfer structure) may contain routines that must be transported as separate objects (Object Type ROUT).
           As of BW 2. 0A, you are supported by the BW transport link, grouping "Backup for system copy". Select the R/3 and DataMart source systems in the source system filter and collect the source systems using the Drag and Drop function.
           If you use type PSADELETE processes, also add these to the transport request.
Scenario 2)a): Create the described transport request in the old BW.
Scenario 2)a): In the old BW, delete all R/3 and DataMart source systems in the Administrator Workbench source system tree.
Scenario 1), 2)a) and 2)b): Import the copy.
Scenario 1), 2)a) and 2)b): In the target BW, change the contents of the "target host" field in all RFC connections (destinations) for R/3 and DataMart source systems (Transaction SM59) to a nonsensical, nonexistent address (such as 'nowhere'). Then, delete ALL R/3 and DataMart source systems in the Administrator Workbench source system tree. Caution: This step deletes all PSA tables of these source systems - the data is lost. A message is generated stating that the source system cannot be accessed (since you deleted the host of the RFC connection). Select "Ignore".
Scenario 2)b): Change to the source systems connected to the old BW and THERE delete the connection (in the source system) to BW. To do this, change to Transaction SE37 - RSAP_BIW_DISCONNECT function module  Sngl. test. Parameter I_BIW_LOGSYS = <name of BW>, I_OLTP_LOGSYS = <name of the source system>, I_FORCE_DELETE = 'X'.
Scenario 1): If you want to connect the target BW to one or more source systems that are also connected to the original BW, assign a new logical system name (Table T000) to the target BW. However, we recommend that you follow Note 184447 when designing the system environment.
Scenario 2)a) and 2)b): Assign the same name to the target BW system that was assigned to the old BW system (logical system name, Table T000).
Scenario 1), 2)a) and 2)b): If you have just renamed the BW, execute Transaction BDLS to convert all relevant tables to the new logical system name. To do this, refer to Notes 121163 and 369758.
Scenario 1): Connect the required source systems. (Administrator Workbench - Source systems)
Scenario 2)a) and 2)b): Connect the source systems, that were connected to the old BW. (Administrator Workbench - Source systems)
Scenario 1) and 2)a): Import the request created above. Bear in mind the special CTS features for the source system-dependent objects (system changeability in connected systems; View V_RSLOGSYSMAP).
Scenario 2)b): Recreate the transfer structures/transfer rules and activate them.
Header Data
Release Status: Released for Customer
Released on: 20.03.2007  15:58:10
Priority: Correction with medium priority
Category: Consulting
Primary Component: BW-WHM-DST-SRC Source Systems
Releases
Release Independant
Related Notes
886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
733623 - Oracle export/import for BW system copies
524554 - Storing destinations in the BW environment
369758 - BDLS: New functions and better performance
325525 - Copying and renaming systems in a BW environment
127326 - CTS for InfoSources, update rules ...
121163 - BDLS: Converting logical system names
<b>
40785</b>
Summary
Symptom
You are transporting BW objects that are heavily linked with each other so that several requests are necessary.Objects of a request are using objects which are locked on other requests.
In the target system, errors arise during the method execution of requests with BW objects (return code 8).The messages indicate that objects are required which do not exist in the target system and are also not contained on the request.
For example, you transport an object with attributes, but the attributes are not transported nor are they available in the system.In the log, message R7322 appears: 'Attribute &1 from characteristic &2 not (actively) available'. As a result, an InfoCube cannot be activated if InfoObjects are missing and so forth.
Additional key words
CTS, transport link, AWB, object collector
Cause and prerequisites
You collect objects with the transport link of the Administrator Workbench and then write these to a transport request.In the process, all objects which have not yet been transported are marked (development class $TMP). Or you install Business Content and write the installed objects directly to a request.
Objects with a different development class (not $TMP) are also gathered but they are not marked because the system assumes that these have already been transported and are then subject to automatic recording.If you are not sure whether these objects already exist in the target system, you can mark the objects.The system then writes them to the request and transports them (once again).
It could happen that objects that are locked on another request have been collected.You can recognize this by the column "Transport request" in the window with the collected objects (you may have to expand the tree with the collected objects completely). You should always release the requests beforehand, that means prior to the request that is being compiled.
This is because these objects are needed by objects that the system is now collecting, but do not yet reside in the target system or do not yet reside there in their most current version. If you import the request which the system is collecting prior to the other request, then the errors described in the symptom section of this note.
Solution
Proceed as follows if you are using the object collector:
Collect the objects
expand the tree with the collected objects completely
Release all requests that are displayed in the 'transport request' column.
Only then release the request with the objects that are being currently collected.
As of Support Package 16 this approach is simplified even further.In this case, a log with the following messages is displayed after writing the collected objects:
'Objects which are locked on a different transport request' (Message RS0305).If you expand this message, you receive a list of all objects which are locked on other requests.
'Transport requests which must be released first' (Message RS0306).If you expand this message, you receive a clear summary of the requests which must be released before the request currently being compiled.Here the system simply summarizes the requests from the previous list that still contain dependent objects.
Thus, as of Support Package 16 you no longer have to expand the tree completely and search for linked requests.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 05.09.2001  22:00:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BW-SYS Basis System and Installation
Secondary Components: BW-BEX Business Explorer
BW-WHM Data Warehouse Management
Releases
Release Independant
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_BW 20B SAPKW20B19
SAP_BW 20B SAPKW20B20
Related Notes
125499 - Activation error after transport of BW objects
<b></b>