Replicate MetaData to BI

Hi
I am new in BI. Can anyone help on the differences on below options when I tried to replicate Metadata to BI? There are 4 options available when I replicate Metadata. System prompt that how do you want to create the object in BI for Generic DataSource.
1) as DataSource (RSDS)
2) as 3.x DataSource (ISFS)
3) this and following 1 as DataSource (RSDS)
4) this and following 1 as 3.x DataSource (ISFS)
Thanks,
Kang Ring

Hi Kang,
1) as DataSource (RSDS)
--> Replicated datasource as BI7 for transformations.
2) as 3.x DataSource (ISFS)
--> Replicates as 3.X datasource, can create transfer and update rules,
3) this and following 1 as DataSource (RSDS)
--> Same as point 1, applies for current and next datasource
4) this and following 1 as 3.x DataSource (ISFS)
--> Same as point 2, applies for current and next datasource while replicating.
Check: [Replication of DataSources|http://help.sap.com/saphelp_nw70/helpdata/EN/43/5fc0680a876b7de10000000a422035/frameset.htm]
Hope it Helps
Srini

Similar Messages

Replicate metadata in productive

Hi Gurus.
I need to replicate metadata a data source to synchronize the time stamp, when I replicate the data source in productive system, generates the following message:
Changes to Repository or cross-client Customizing are not permitted
and does not allow replication.
Does anyone have a solution to replicate without open the productive system?
Thanks.

Hello,
Try to see if you can execute the report RSDS_DATASOURCE_ACTIVATE_ALL under the transaction SE38, to see if activating the datasource it will replicate it and will synchronize the time stamp.
Hope this helps,
Regards,
Diogo.

Problem in Replicate Metadata in BIW

Dear All,
Can anyone help me in Replicate Metadata in BIW.
Datasorce are active. LBWE activity is also done and the Extration can be seen in Sandbox..
But while we do a Replicate Metadata in RSA1in BIW then its now showing all the moudules ex: Sales and Distribution or Purchasing etc
Thanks in advance
Regards,
Mayur

Hi,
Don't directly do Replicate datsources on source system.
Select the source system from the Modeling tab, right click and select Display Datsource Tree.
Select the Required Application compnent ie SD , right click on it and select Replicate Metadata.
No only SD related Datasources will be replicated.
REDDY

Replicate Metadata

Hi,
Recently we upgraded the R/3 from 4.6C to ECC6.0. As we trying to connect ECC6 from BW, we faced some RFC problem & managed to resolve. While resolving, we accidently deleted the source system. The system is prompting for
Replicate Metadat. Should we replicate Metadat?
Thanks,
BW Baby

Hi,
so, now your source system is completely changed...(from 4.6 to ECC) so, definetly you need to do REPLICATE METADATA ... betyter to do that Replicate Datasources also...
regards
@jay

Replicate metadata error.

Hi gurus,
When I replicated metadata from source system(SAP R3 46c),some error occured.
Error Message is :RSAR 314 and RSAR 315.
Can you help me?
Thanks in advance.
Lykin.

There should be some program error, you need to find the problem if it is throwing any short dumps, if not I would do replication for specific data source or specific application and figure out which one actually throwing the error. Another thing you could do is, verify the source system connection is fine by doing check on the source system, also make sure the RFC is fine too in sm59.
If the error is happening to specific data source, then you need to see what is actually happening to this ds.
thanks.
Wond

Metadata replication popup when installing BI content in 7.4

When I select an object to install with grouping "Data Flow Before", I am constantly presented with the attached window, which I either have to cancel or accept, during the object collection process. This occurs multiple times (up to 20, 30, or more) depending on the complexity of the data flow of the object, regardless of whether I accept, cancel, or accept with different options. My guess is that I'm being prompted for each DataSource that is encountered in the collection process, but the window only indicates the source system. Is there some setting or note I need to apply so that I can just accept once - it is making the content installation process take a lot longer than I had expected. Just to emphasize, this is on the object collection step and not the actual installation.
I am on BW 7.4 SP7 with BI Content 757 installed. I have replicated all datasources from my ECC source system (content and active).
Any tips or suggestions are appreciated.

Hi Nathan,
Even i faced this issue and searched online but did not get the answer so for others who face same issue, try out below process to resolve it.
The metadata from SAP source systems is independent of BW metadata. There is no implicit assignment of objects using same names. In the source system, information is only retained if it is required for data extraction. Replication allows you to make the relevant metadata known in BW so that data can be read more quickly. The assignment of source system objects to BW objects takes place exclusively and centrally in BW.
While creating Sap Src system connection in BW a popup would be encountered whether to replicate Metadata or only activate the connection.In your case the replication was not chosen and only activation was done hence encountering the error.The solution would be, under sap src system context menu, choose activate and when the same popup appears choose replicate as well. This will resolve the issue.

Replicate datasource from SRM source system

Hi,
I need to replicate datasource from SRM source system I am able to see datasource under application component in RSA6 when I tried to replicate those component In BI by selecting Replicate Tree Metadata I am not able to see any application component in RSA1 .
Thanks,
Senthil

Hi Senthil,
i know your issue. the problem is when you are going to do replication in first time you dont find any application components.
so what you have to do is go to the BI SYSTEM and go to your SRM Source system and select and right click and select Replicate Datasources.
if you are doing first time replication it takes a quite long time.
so once its replicated then u will b able to see the datasources as well as the corresponding application components.
next time in SRM if you enhance the datasource you can directly select the datasource and right click say replicate metadata.
once solved get back to me
HOPE THIS HELPS YOU
regards
vadlamudi

Adding new field to Remote Cube

Hello,
We have an existing remote cube that we are trying to add a new field to in 7.0. I've already added the field to the datasource, unhidden it, and tested it in RSA3. Now i'm trying to bring it into BW and add it to the remote cube. I right clicked on the source system under the data target and chose Replicate Metadata however the new field does not show up anywhere. What am i doing wrong? Does a remote cube work differently? How do i get my new field over from R3?
Regards,
TMS

That's the problem. The R3 field does not show up in the datasource in BW so it can be moved over to the transfer structure. As you know when you replicate metadata, the new datasource fields appear and can be mapped into the transfer structure. That is not the case for this remote cube. The new field is not there.

Warning message in RSA6

Hello Experts,
In rsa6 when I transport the Data source, iam facing the below message.... ignored the warning transported and replicated in BI system but its not reflected in BI system...help me out.
The even-numbered length of the DEC field D_UNITS can lead to problems
Message no. R8569
Diagnosis
You want to use the field D_UNITS in the extract structure for DataSource 0CFM_DELTA_POSITIONS. This field has a field of type 'DEC' (or 'CURR' or 'QUAN') with an even number of characters.
This can create problems since the length resulting from calculations in ABAP (for example, in extractors or Customer Exits for extraction) is too large to be inserted in the database later (PSA in BW), causing a short dump.
Procedure
This warning is only relevant when the maximum length of this field is exceeded during extraction, for example when the field is expanded in the Customer Exit through a calculation.
More information and a remedy can be found in SAP Note 641744.

Hi KV........
Hav u checked the correct Application component after Replication..........is it popping any error message...........After replication u hav to activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL ...........Warning cannot be the reason........as per my understanding........First go to RSA1 >> go to source system >> Right click on the desired source system >> Display datasource tree >> then go to the correct Application Component >> Then right click >> Replicate metadata........
Hav u checked the SAP Note 641744..........given in the Error message.......For ur reference.......
Symptom
The following symptoms can occur:
1a: When you transfer a DataSource from the Business Content, a warning is displayed, stating that the even numbered length of the DEC field <Fieldname> can cause problems (message: R8 569).
1b: When you generate DataSources using transaction RSO2, the warning R8 569 is issued.
2: When you load extracted data to the PSA, a short dump 'DBIF_RSQL_SQL_ERROR' is generated. (In this case, the above message appears if the DataSource is checked in the source system in transaction RSA6.)
Other terms
OLTP, extractor, data extraction, DataSource, service API, SAPI, S-API
R8569, ORA1438,
Reason and Prerequisites
The DataSource contains fields of the 'DEC' DDIC type (also:'CURR' or 'QUAN') with an exact-number-of-places.
You should only expect problems if calculations are made with the above field types using the value read by the database.
Example:
The value '9999' is read by the database from a DEC field of length 4.
At runtime, this is treated as an internal ABAP type 'P' (length 3) that can, however, have the maximum value '99999'.If the read value is now increased by an arithmetic operation - for example, by adding '1' - the resulting value '10000' cannot be written to the PSA that was also generated on the basis of the DEC field of the extract structure with a length of 4.
Result: A short dump 'DBIF_RSQL_SQL_ERROR', 'CX_SY_OPEN_SQL_DB', is issued when you write to the PSA in BW using the INSERT_ODS routine.
Solution
If the field is not manipulated in the customer exit or elsewhere, no processing is required.
If you change the field, the following possible solutions are available:
You can make sure that the number of the characters does not increase after the manipulation.
If you can change the extract structure of the DataSource without affecting other scenarios (for example, if it was generated in transaction RSO2), you can increase the length of the DEC field (or CURR, QUAN) there to the next odd character (in the example above: from DEC 4 on DEC 5).
If neither of these solutions are possible, you can use a customer append that contains a relevant DEC field (or CURR, QUAN) with the next highest odd length. This can be used for the result of the calculations. This means that you do not have to manipulate the previous field.
Regards,
Debjani.........

Adding a new field to a Z table

We have a Z table on which we have created a datasource. We have created a virtual cube on this datasource and queries are built on this cube. This setup is present on Dev, Quality and Prod environment.
Now we have added a new field to the Z table in Dev. We will be creating a new Infoobject for this new field and will be adding it in the Virtual Infoprovider and also in the queries.
1. Do we need to replicate the datasource so that newly added field is visible to the datasource? If no, is there any way?
2. When I have to transport this to Quality and Prod, do I have to capture all the components and objects (Table,Datasoure,Virtual Cube Queries)? If no, what should I capture in the transport request?

Hi,
First, you have to regenerate the datasource in order to add the field:
1) Log on to source system (where Z table is stored) and go to transaction RSA6.
2) Select the root node and click Expand (icon with '+' sign).
3) Search for your datasource (you can use the binoculars icon).
4) Click on Change.
5) Verify that the field appears on the list. Make sure that "Hide field" and "Field only known on client exit" options are not marked for this field.
6) Click on Save.
7) Select "Datasource" -> "Generate" (CTRL+S) menu option.
8) Use RSA3 transaction in order to verify the new field appears on test extractions.
Then, to replicate the datasource in BI:
1) Log on to SAP BI and go to RSA1 transaction.
2) Go to "Modeling" -> "DataSources" section.
3) Search for your datasource and right click on it. Select "Replicate metadata" from context menu.
4) Add the new InfoObject to the VirtualProvider.
5) Update the transformation which joins the DataSource to the VirtualProvider.
As far as transport requests are concerned, even though it requires more work, it is a good practice to group objects in different transport requests according to their type:
In the source System (R3 for instance):
1) One transport request with the table.
2) One transport request with the datasource and its structure.
In BI:
1) One transport order with the datasource replica.
2) One transport order with the new InfoObject(s).
3) One transport order with the modified VirtualProvider.
4) One transport order with the modified transformations from the datasource towards the VirtualProvider.
5) One transport order with the Queries and their elements.
I hope this helps you.
Regards,
Maximiliano

Creating Source System in BW

Hi Friends,
We are using BI, i have to create a source system(R3) in BW.
Both sides we have users with enough profiles.
In RSA1 --> Source System --> Create is using to create the sourse system.
I am using automatic function at the time of defining the source system.
It is asking some dialog user from source side, i am giving some dialog user
then i am getting the error user cannot create in source system.
Could you please help me out.. how to create R3 source system in BI.
Thanks in advance
Srinivas

Hi Srini,
                Check u'r partner profiles.if u din't get....
plz follow this....
2.1     SAP R/3
2.1.1     Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu     Define Client Administration (SAP R/3)
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1.     Choose Display  Change.
2.     Confirm the warning message Caution: The table is cross client.
3.     Select your SAP R/3 client and choose Details.
4.     In the Change View Clients: Details screen, activate the following settings:
     Automatic recording of changes
     Changes to Repository and cross-client Customizing allowed
     eCATT and CATT allowed.
5.     Save.
6.     Go back to the SAP Easy Access menu.
2.1.2     Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1.     Define the systems as logical systems.
2.     Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code     SPRO
SAP R/3
IMG Menu     Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2.     Choose New entries.
3.     In the column Log System, enter a name for the logical system that you want to create.
4.     In the column Name, enter a description of the logical system.
Log. System     Name
where      XXX is the system name
and      NNN is the client.
5.     Save your entries.
A transport request for Workbench appears.
6.     Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7.     Select an existing request or create a new request, if necessary.
2.1.3     Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Assign Logical System to Client
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Choose Display ® Change.
3.     Confirm the warning message The table is cross client.
4.     Select your R/3 client and choose Details.
5.     Enter the name of the logical system of your SAP R/3 client.
6.     Save and confirm the warning message Be careful when changing the logical system.
7.     Choose Back twice.
2.1.4     Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Creating an RFC User (SAP R/3)
Transaction Code     SU01
SAP R/3 Menu     Tools  Administration  User Maintenance  Users
2.     In the User field, enter RFCUSER.
3.     Choose Create.
4.     On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type     System
Password     LOGIN
Profile
Profiles     SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language     EN
5.     Save your entries.
2.3     SAP BW
2.3.1     Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1.     To perform this activity, choose one of the following navigation options:
SAP BW Role Menu     Local Settings ® Define Client Administration
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Switch to change mode.
3.     Select your client.
4.     Choose details.
5.     In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6.     In field Client Role enter Customizing
7.     Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2     Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Defining a Logical System for SAP BW (SAP BW)
Transaction Code     SPRO
IMG Menu     SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1.     A dialog box informs you that the table is cross-client. Choose Continue.
2.     On the Change View Logical Systems: Overview screen, choose New entries.
3.     On the New Entries: Overview of Added Entries screen enter the following data:
Field name     Description     R/O/C     User action and values     Note
Log. System     Technical Name of the Logical System          Enter a name for the logical BW system that you want to create
Name     Textual Description of the Logical System          Enter a clear description for the logical BW system
4.     Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3     Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu     Assigning Logical System to Client (SAP BW)
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
1.     In the view Display View "Clients": Overview, choose Display.  Change
2.     Confirm the message.
3.     Select your BW client.
4.     Choose Details.
5.     In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6.     Save the entries and go back.
2.3.4     Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW     Modeling  Administrator Workbench: Modeling
Transaction Code     RSA1
1.     In the Replicate Metadata dialog box, choose Only Activate.
2.     If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5     Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Creating RFC User
Transaction Code     SU01
SAP BW Menu     Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1.     On the User Maintenance: Initial Screen screen:
a.     Enter the following data:
Field      Entry
User     RFCUSER
b.     Choose Create.
2.     On the Maintain User screen:
a.     Choose the Address tab.
b.     Enter the following data:
Field     Entry
Last Name     RFCUSER
Function     Default-User for RFC connection
c.     Choose the Logon data tab.
d.     Enter the following data:
Field     Entry
Password     LOGIN
User type     System
e.     Choose the Profiles tab.
f.     Enter the following data:
Field     Entry
Profiles     SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g.     Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6     Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu     Define RFC-USER as default (SAP BW)
Transaction Code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
1.     On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2.     In the Global Settings/Customizing dialog box choose Glob. Settings.
3.     On the Display View RSADMINA Maintenance View: Details screen:
a.     Choose Display  Change.
b.     Enter RFCUSER in the BW User ALE field.
c.     Choose Save.
Leave the transaction in order to activate the entries you have made.
3.3.2     Creating the Source System in the Administrator Workbench
Procedure
1.     From the SAP Menu in the BW system, choose:
SAP BW Role Menu     Creating the Source System in the Administrator Workbench
Transaction code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
2.     Choose Modeling.
3.     Choose Source Systems.
4.     In the right-hand window mark Source Systems.
5.     Choose the context menu (right mouse click).
6.     Choose Create.
Field name     User action and values
File System, Manual Meta Data, Data Using File...     X
7.     Choose Enter.
Field name     User action and values
Logical source system      FILE
Source system name     File system
8.     Choose Enter.
9.     Choose Back.

DataSource Creation for flatfile in BI 7.0

I am new to BI 7.0. I have worked on BW 3.5. When i rightclick on Appl Comp for creating a datasource in 'Datasources' node, I am not able to find any option except 'Replicate MetaData'. Is there any setting to be made or shall I have to do it differently.
Please let me know.

HI
first create flat file source system under file folder in source system tab
Go to datasource tab click , click on yellow icon and select ur source sytem
then u can create ur application component and datasource under that application component.
http://help.sap.com/saphelp_nw04s/helpdata/en/fc/1251421705be30e10000000a155106/content.htm
Regards
Kiran
Message was edited by:
ravi kiran naalla

Error while loading master data text

Hi all,
I have scheduled my first load into Production for a text datasource which still shows as running but when I looked into the Details tab I found the below error:
Transfer (IDocs and TRFC): Errors occured
- Request IDoc : Application document not posted.
I checked the IDoc in R/3 and found that it is with Status 51 - Application Document not posted. The error it is showing there is "Request REQU_XXXX is not available in target system YYYY".
What could be the reason for this? What shall I do to resolve it?
Best Rgds,
James.

Hi,
right click your source system in BW and perform a check. Most likely the connection is not setup properly.
If this check failed
Check RFC destination:
- from BW, SM59, open your source system destination; test connection and from the menu, test authorizations.
- perform the same from your R3 source system with your BW connection.
If RFC are fine most probably the partner profiles and/or the ports are not configured properly.
Let BW perform this task for you: right click your source system and execute a restore. You will require
- administrative rights on the source system
- open the source system client so that bw can delete and recreate the partner and ports profile (SCC4: automatic recording of changes/ changes to rep and cross client allowed)
- ALE/ALEREMOTE or your communication users passwords...
With this follow the steps proposed by the restore procedure. ; when the system prompts to delete the connection, do so. You replicate metadata at the end as well...
hope this helps,
Olivier.

Extraction of data from ECC to BI

Hi Experts,
I am trying to follow a task assigned to load attribute data from a source sap system for a cost center.
I have followed the following steps:
1: Create a global transfer routine.
2: Created a generic datasource for attributes
2.1: In the source system, using tcode SBIW, under SAP R3 -> CO, I created a node ZBW310-10 and created a datasource for master data attributes ZGR01CC_ATTR. I am specifying view Z_BIW_CSKS(I copied BIW_CSKS to Z view) Fields for selection were also marked.
3: Replicated generic datasource for attributes by specifying "Replicate Metadata"
4. Created the transformation and activated.
5. Created the Infopackage and Attribute data to PSA
Here no records are loaded when I check the dataloading monitor. What might be the issue? All objects are activated. The view mentioned above Z_BIW_CSKS has 82 records in development client of the source system.
Thanks,
Abdullah Ismail

Hi
You dont see the data source in R3? When you created the data source using Tcode RSO2 you would have put the data source under some application like SD, MM etc.
Please check in the respective application for your data source. If still the data source is still not seen, then check whether the data source is active or not.
Hope it helps.
Regards
Sadeesh

Logical Data Base to be used in the QUICKVIEWER

hello Abappers,
My client cannot select text fields using SQVI so he wants me to come up with a way for him to do so. I was thinking of creating a logical data base which can be selected in SQVI. I could build the FM READ_TEXT into the QV but what I need clarification on is outputting the text fields because the logical data base is really a set of table joins and since I am using the QV I do not have the flexibility that I would have if I was using a logical data base in a program.
Please advise if anybody has any ideas on this approach and how I would structure the output.
regards

Hi Santhosh,
Since you say you are a beginner, lets start this way, hopefully U know from what datasources in ECC or R/3 you are supposed to load data from. Once you are sure about it, then follow this steps.
1) Go to RSA5 transaction in ECC or R/3 System ( source system ).
2) Select the specific datasource from which data is to be extracted to BI and press Activate Datasources button on the top right.
3) Then on check whether this datasource is available in RSA6 screen.
4) Come to BI system, there go to the Source Systems screen, there select the specific Source System (ECC or R/3).
Go to U'r specific Infoarea i.e., SCM in that select the datasource for which U are supposed to extract data, right click and select Replicate Metadata.
5) Once replication is done now right click again on datasource and create and run the infopackage , if its BI 7.0 data will be extracted till PSA.
6) After this create Transformation by right clicking on the Datasource again. Since I guess U will be using standard datasource U will get automatic transformations between the source fields and the infoobjects. Activate Transformations.
7) After this Create a DTP process by again right clicking on the Datasource. Here U specify the Data Target to which data is to be loaded.
8) Activate the DTP, once that's done successfully, Execute the DTP by clicking the Execute Button in the DTP.
9) Monitor U'r data loading thru Monitor screen.
Hope this helps.
Regards,
Syed

Replicate MetaData to BI

Similar Messages

Maybe you are looking for