Professional Documents
Culture Documents
Applies to:
SAP BW 3.x & SAP BI Net Weaver 2004s. For more information, visit the EDW homepage.
Summary
In BW 7.3 we are getting a very handy option of Copy Data Flow .We use this function to copy Data Warehouse objects and processes belonging to a data flow or process chain. In the subsequent sections we will try to understand in detail the functionality of Copy Data Flow and how to use the copy data Flow in BW 7.3. Author: Company: Created on: Vikram Srivastava Infosys Technologies Limited 09 December 2010
Author Bio
Vikram Srivastava is working as a Technology Analyst with Infosys Technologies Limited. He has got a rick experience on various BW Implementation/Support Projects in both SAP BW 3.5 and SAP BW 7.0.
Table of Contents
Introduction: ........................................................................................................................................................ 3 Step by Step approach to use copy Data Flow: ................................................................................................. 4 Step 1:Start ......................................................................................................................................................... 5 Step 2: Template ................................................................................................................................................ 7 Step 3: Number of copies ................................................................................................................................... 7 Step 4: Objects that cannot be copied ................................................................................................................ 8 Step 5: Process Chains ...................................................................................................................................... 8 Step 6: Source Systems ..................................................................................................................................... 9 Point to remember for Copy Source Systems: ............................................................................................... 9 Step 7:DataSources .......................................................................................................................................... 11 Step 8:InfoProvider ........................................................................................................................................... 12 Point to remember for Copy InfoProvider: .................................................................................................... 14 Step 9:Transformations: ................................................................................................................................... 14 Point to remember for Copy Transformations: .............................................................................................. 15 Step 10:Directly Dependent Processes: ........................................................................................................... 15 Step 11 & 12:Indirectly Dependent Processes and Other Processes: ............................................................. 16 Step 13:End Process: ....................................................................................................................................... 16 Related Content ................................................................................................................................................ 19 Disclaimer and Liability Notice .......................................................................................................................... 20
Introduction:
In BW 7.3 we are getting a very handy option of Copy Data Flow .We use this function to copy Data Warehouse objects and processes belonging to a data flow or process chain. In the subsequent sections we will try to understand in detail the functionality of Copy Data Flow and how to use the copy data Flow in BW 7.3. The data flow copy supports various scenarios: We can use a data flow or a process chain as a master template for other data flows or process chains. We can take a data flow or process chain from BI Content, copy it and then modify the copy according to the requirements. We can take a data flow or process chain for one source system from BI Content and then copy it for the other source systems we need. We can copy a data flow or process chain that is dependent on source system A for source system B or various other source systems we need. We create the copies in the development system and transport them to the production system. After creating a 1:1 copy. we can also create multiple copies (1:n copy) from a template. As the development system generally contains fewer source systems - and different ones - than the production system, we can create dummy source systems and use these for the copies. In the production system, we then assign the dummy source systems to the target source systems as original source systems. Unlike when assigning one original source system to multiple target source systems in the production system, the simplification is made already in the development system when using a 1:n copy with dummy source systems in the data flow copy. Instead of it being applied just to the source systemspecific objects, it is applied to non source-system specific objects in the data flow or process chain.
Step 1:Start
Go to RSA1, right click in the data flow we want to copy. We will get the option of Copy Data Flow.
Click on copy Data Flow, we will get the below screen which gives us an option to select Upwards, Downwards and Upwards and Downwards data flow to select for copy for the data flow.
Once we select the data flow system performs a dependency analysis and gives us an option of collecting DTP and InfoPackages of the data flow.
After this we come to the Data Flow copy wizard which allows us to collect and copy the objects (starting from the chosen start objects) belonging to a data flow, or to collect and copy a process chain together with its processes and objects.
For moving to next step, click on Continue. Also as stated earlier at this point of time we come to know the actual number of steps that will be required to copy this data flow. These numbers of steps will change on depending the flow which is being copied. E.g , in this demonstration we are getting below steps. In order to get a complete understanding of copy data flow we will discuss all the 13 steps in this article.
We can get the status of copy process by usual Traffic light signal used in BW.
Step 2: Template
If one or more copy processes already exist for the start object, we can select a copy process as a template for the current one. The wizard then takes over various settings from the template, the number of copies for example. SAP recommend using a template if we want to keep the target objects from the template in the
Point to remember for Copy Source Systems: Source systems cannot be created or changed for a copy. However, we can map a different source system (as a target object) to a original source system and then copy DataSources between these source systems in the next step. This also allows us to change the type of the source system, for example to create an identical file DataSource for an ERP DataSource or to create a copy of the DataSource in a dummy of the original system. To do this, we need to select the copy type for every original object by clicking on the symbol in the column Type and mapping a target object if required. Note the following: The wizard only displays the possible copy types for the relevant original object. New GUIDs are only created during copying. For a 1:n copy: Use the placeholder & in the technical object name.
The following additional functions are available in the wizard: If the column Check Result (Column next to Target Object in the above Diagram) displays a yellow or red traffic light, we can display errors and warnings by clicking on the column. We can use the checkbox Display Technical Object Name to switch between the technical object name and the object description. Entries for original objects that are automatically mapped to a target object (where no user interaction is possible or necessary) are hidden by default. We can use the checkbox Display Unchangeable Rows to hide these entries.
If we want to go to the next step, all the errors and warnings of this step are displayed. If we have not selected a valid copy type or a valid target object for an original object, this is evaluated as an error. Once we have corrected the errors, we can continue with the next step. Point to be noted is that the warnings are not displayed again when the copy process is completed in the last step. For moving to next step, click on Continue.
Step 7:DataSources
We can copy Data-Sources within a single source system or between different source systems. If the target source system is an SAP system, the copy is created using metadata replication, if this Data-Source is in the target system. It is otherwise not possible to copy.
Now we need to select the copy type for every original object by clicking on the symbol in the column Type and mapping a target object if required. On clicking the copy type we will get the below option for the Input Value of the copy type. We can choose the correct option based on our need for the copy flow.
Then we can specify the target object name for both description and technical name. If we dont select any input value for copy type by default system will take the Use Original option.
Step 8:InfoProvider
We can copy InfoProviders or map them to an existing InfoProvider. The InfoObjects used in the original object are not copied over. For the target object mapping, it is therefore important to have as much agreement as possible between the original object and the target object, in order to have an accurate copy of the transformations.
Now, same as above, we need to select the copy type for every original object by clicking on the symbol in the column Type and mapping a target object if required. On clicking the copy type we will get the below option for the Input Value of the copy type. We can choose the correct option based on our need for the copy flow.
Then we can specify the target object name for both description and technical name. If we dont select any input value for copy type by default system will take the Use Original option.
Point to remember for Copy InfoProvider: If we overwrite an existing InfoProvider, the target object is modified accordingly in order to avoid data loss. So if we have removed fields from the original object, for example, this change is not included in the overwrite. The following applies to the existing target InfoProvider: We cannot overwrite an existing InfoProvider, as data could be lost. Therefore the copy type Overwrite is not available. Instead we can use the copy type Merge which only transfers compatible changes from the original object to the target object. So if we have removed fields from the original object, for example, this change is not included in the merge. However the fields that exist in the original object are filled in the target object.
Step 9:Transformations:
In this step Transformations of source will be copied. When copying transformations, individual rules are only copied if their source and target fields are contained in the target objects
Select the copy type for every original object by clicking on the symbol in the column Type and mapping a target object if required. On clicking the copy type we will get the below option for the Input Value of the copy type. We can choose the correct option based on our need for the copy flow. Please note the difference in the option for input vales that we get in Transformations.
Point to remember for Copy Transformations: When copying transformations, individual rules are only copied if their source and target fields are contained in the target objects. During the copy process, if a different object is used instead of the source or target of the original transformation, it may be the case that an individual rule is not copied because the source field or target field of this individual rule is missing. The sequence of the steps from 7 to 9 i.e from Copy DataSource till Copy Transformations is defined by the dependency relationship between the objects. As transformations are dependent on their source and target objects, the steps for copying the possible source and target objects from transformations (DataSources and InfoProviders) appear before the step for copying transformations. Hence If we want to copy the source and target object of a transformation, the copy of the transformation relates to the copy of the source and target object rather than the source and target object of the original transformation.
Now in order to trigger the copy process in this step, we need to click on Finish. Once we click on Finish. We get a popup where we can define whether we want to run the copy process in the background or in the Dialog.
In order to display the status of Data flow copy Process , click on Yes.
Again we can get the status of copy process by usual Traffic light indicator used in BW. Just before clicking on Finish on the End Process we will get the below Status shown (RHS one) if everything of Copy Process is correct till now.
Related Content
www.help.sap.com www.sdn.sap.com www.service.sap.com