InfoProvider: infoObject (master data attribute and text)

I saw info Object of master data attribute and text in InfoProvider.
are infoObject act like a table when we do query on them.

Hi
Refer to this as down
Custome Infoobjects Tabels:
/BIC/M -- View of Master data Tables
/BIC/P -- Master data Table, Time Independent attributes
/BIC/Q -- Master data Table, Time Dependent attributes
/BIC/X -- SID Table, Time Independent
/BIC/Y -- SID Tabel, Time Dependent
/BIC/T -- Text Table
/BIC/H -- Heirarchy Table
/BIC/K -- Heirarchy SID Table
Standard Infoobjects Tabels(Buss. Content):
Replace "C" with "0" in above tables.
Ex: /BI0/M -- View of Master data Tables

Similar Messages

Load Master data attribute with Text Data (Urgent Please)

Hello Experts,
I created a new navigational attribute to one of the master data object and now I want to load that particular new navigational Attribute from the Master data Text (Medium description).
In brief, I need first 4 letter of master data text (medium description) to load in to the navigational attribute. How
How is this possible? Can you please help me to get it solved.
Thanks and Regards,
Harish Mulaka

Hi Apparrao,
Add this attribute to your infoobject's attributes list.
Make sure it comes in the communication structure for the infoobject.
Then in the transfer rules write a routine. You will have to read the text table to get the medium text(field TXTMD) and pull the 4 characters from the beginning and populate your new attribute.
Do a full load and run the attrbute change run.
Hope that helps.
Regards.

Change dataosurce from master data attributes to text

Hi,
i build data source as master data attributes (in tr sbiw) and i want to change it to text ,
how can i do that?
Regards

Hi....
You can copy it and recreate it as text in RSO2.
Just create a new one... There are max 5 entries in a generic extractor so note them down and recreate...
Regards,
Debjani......

Using Master Data attribute and compounded IO in Transformation

Good day
I have the following issue in a transformation.
I want to u201CRead Master Datau201D from IO u2018ZSIDCONTRu2019 to display data for an attribute u201CContract Durationu201D (Key Figure).
IO u2018ZSIDVEHCNu2019 is also compounded to master data IO u2018ZSIDCONTRu2019.
The Source field of Rule = field u201CID_CONTACTu201D
In my transformation my Rule Type = Read Master Data and the u201CFrom Attrib. ofu201D field = ZSIDCONTR and the IO Assignment is also = u2018ZSIDCONTRu2019.
If I test this rule then the following error message is displayed:
Characteristic ZSIDVEHCN compounded to ZSIDCONTR is missing in
transformation source
How do I add the compounded characteristic ZSIDVEHCN to the transformation rule?
Thanks in advance.
Cj

Hi,
You should add the InfoObject ZSIDVEHCN to your target and define a mapping rule to fill it up from your datasource.
Only when both objects are available in your mapping you will be able to perform a master data selection (since they are compounded).
If this object is not available in your source, you should define a mapping rule to fill it up (constant? ...)
Hope this helps.
Best regards,
Michel Hoefkens

Process chain master data: attributes or Text load first?

Hello
I understand as attributes those characteristics defined as nav. attrib for a characteristic. For example I have char. material with attrib source, destine, manufacturer, country etc. So my understanding was first to load all text (code and description) for each one of the characteristics (inc. attributes) and later load properly for a material X all of its attribute values x1,x2,x3....
I am correct ?
becuase if I load first attributes as I understand them, maybe some codes that I update at posteriori will note have their attribute values loaded
Hope you understand what I mean
Looking forward your replies !
tia

thanks Udo
as of the sequence master first and transact after is clear but allow me to rephrase my question :
when I use a text datasource i will be filling code and descriptive for a characteristic so for my case material will have all codes and descriptives from R/3. (010 - winston, 020 - marlboro, 030 - camel)
The same for loading attributes master data (for me again text: code and descriptive). In my case lets say attribute is factory so will be 001 spain, 002 france, 003 USA, 004 Germany).
later when I use attribute datasources understand that will be loading for each of my products loaded in step 1 the respective values for their attributes. That is for product 010 load their factory lets say 002 ...
I am a beginner so please let me know if I am misunderstanding anything ?

Error loading master data attr and text for 0material

Hi gurus,
I am new to BI, I am getting an error RSDMD- 194 when i am loading 0MATERIAL_ATTR and TEXT.
It is showing for nearly 100 records in the error stack.
Can anyone explain some basics,
1) why do we need to add 0MATERIAL to a particular Info area to start loading its ATTR and TEXT
2) Are the info objects that appear in the attributes tab of 0MATERIAL the same as the fields of 0MATERIAL_ATTR datasource, basically what i don't understand is are we mapping the 0MATERIAL_ATTR datsource fields to the info objects appearing in the attributes tab of 0MATERIAL info object.
3) Also when i added 0MATERIAL to my Info Area , there were some extra info objects that got in, are there any dependent objects that get added ?
<removed by moderator>
Edited by: Siegfried Szameitat on May 19, 2009 11:53 AM

Hi,
"Error RSDMD- 194 when i am loading 0MATERIAL_ATTR and TEXT.RSDMD- 194"
Please check if there is any external characterstic in those 100 records, correct it and load again.
1) why do we need to add 0MATERIAL to a particular Info area to start loading its ATTR and TEXT
It does,t matter where the 0Material is. Info area in kind of Folder to easily locate and put the all the related objects at one place.
2) Are the info objects that appear in the attributes tab of 0MATERIAL the same as the fields of 0MATERIAL_ATTR datasource, basically what i don't understand is are we mapping the 0MATERIAL_ATTR datsource fields to the info objects appearing in the attributes tab of 0MATERIAL info object.
If it is a business content infosource, it will automatically map the attribute to data source field. If you are modifying or creating your own object, you should map it manually based on field name and description.
3) Also when i added 0MATERIAL to my Info Area , there were some extra info objects that got in, are there any dependent objects that get added ?
If you will move any objects all the compounded objects will also come to the info area.
Regards,
Kams

Master data Key and text

hi all ,
we are facing the problem with the master data where if i execute the query and used the master data as characteristi, it dispay key and text but in the scenario where text is not updated but keys are there. in this case, query dispay key and key as text rather than space.
like
region master
001 - gujarat
002 - maharastra
003 -
it display like:
001 - gujarat
002 - maharastra
003 - 003
i want to avoid 003 as text.

Basically, master data text can not be displayed as blank. The reason behind this is,
Lets say tomorrow when user wants to see only text for the same characteristic you mentioned, BEx can not show the value against the blank description. That is the reason, if text is blank the key is copied and displayed in the report.
If you would like to avoid displaying key as text, then try putting a space or . (dot) manually in the text data and save. That would eleminate this text shown as 003.
- Danny

Master data, attributes, texts: ETL process

Hi,
I am new to SAP BW and have a question concerning the difference between master data attributes and texts. I am currently learning with the "sflight" example provided by SAP. There I have, e.g., a table like this:
CARRID CARRNAME          CURRCODE
AA      American Airline   USD
AB      Air Berlin         EUR
AC      Air Canada         CAD
These are my master data because these data won't change often - correct?
What are then my attributes and texts?
Thanks!

Thanks Choudhary.
I am Karthik, new to both, the community and SAP BI. I have a doubt similar to the main question, that goes like this.
CARRID CARRNAME          CURRCODE   TIME             COUNTRIES_OPERATION
AA          American Airline     USD               9:00 AM       America
AB          Air Berlin                EUR             10:00 AM       Germany
AC          Air Canada             CAD             11:00 AM       Canada
Similar to the above table, if suppose there are two other columns TIME and COUNTRIES_OPERATION,
1. Will TIME be included as "attributes" or "time characteristics" as TIME is an additional information of the master data key and there is dimension table where we can define TIME ?
2. Will COUNTRIES_OPERATION be included as "attributes" or can this be included in "hierarchy"
3. If not what can be used into "hierarchy" from the above table.
Kindly excuse if my question is silly or if it does not make sense. I am very new to these terms and still in the learning curve.
Thanking you in advance,
Karthik.

Error while loading Masterdat attributes and text in sap BI 7.0

Hi Guys
Any one help me....Plz
I am new to sap BI, in this my first task and it is loading master data attributes and text into datatargets,I did it in SAP BW 3.5,
It is ok
But i got error in BI 7.0
The error is while loading master data attributes and text in master data targest(using insert charcterstic as a infoprovider)every thing is OK up to infopackage creation step,
Andthe data loaded properly into PSA,
But not into Data targets(i mean here data is not load into datatargets)
After i create infopackage
I created DTP wit settings
Extraction Mode:full
Error handlig: Valid records update,no Reporting(request red)
and i click on activate and on Execute push button
error occurred when i click on "Adminstrative data targets " icon
And the error shows in DTP REQUEST 108 Screen
and it is
**RedColour: updating attributes for infoobject smid_ml1:8->0 Data Records**
**Redcolour: end of master data update**
**Redcolour Message for datarecords saved request is red acc to configuration**
Plese guys let me know this error and give your view
Regards
Venkat
SAP BI consultant

@murali
I click on errorstack push button in DTP error screen But it is not but psa error stack right?
I c'nt get u could plese clear it?
And i also tried on error handling :valid records ...green But no use same error occur
But here i am not using cube to reactive again i send it to you mail my problem as screen shot
Thank u 2 all for ur replies but my problekm is not solved yer

Error while creating Data Source for master data attributes

Hi BI Experts,
Well its been some time for me that I have been part of Extraction in BI.I primarily handled reporting in my last assignments.
I was trying extraction with flat files in SAP BI 7(new to sap bi 7 but very much familiar with BW3.5) but failed in the activity during master data attributes and text upload in infoobject (say IOSP_Mat).
Here is the procedure that I did after creation of characteristic IOSP_Mat.I created a source system for flat file followed by data source for Master data attributes, i selected all the parameters correctly.i.e. csv file format, data seperator as ,
and other settings, now when i am trying to look at the proposed data in the next tab using Load example data.its not showing the desired result.The columns that I have maintained in Flat File is MAT_NUMBER and MAT_NAME (with say 100 data in the file)
same is the result when I am trying to load the text data too columns maintained are
(LANGUAGE MAT_NUMBER Short Description)(same 100 data).
now i used to rsa1old transaction to upload the file using 3.5 version.i created info source for master data/text/hierarchies for IOSP_Mat
now when trying to upload it using info package for master and text data,I observe its(the data) not maintained in the characteristic IOSP_Mat.
When I monitored ,I figured the data has not been even uploaded to the PSA level.
Can you BI experts tell me the answer for this.
Thanks,
Srijith

apologies to all of you for late response,
was busy with some other activities.
I don't remember the exact message,but I remember it was not loaded to even the PSA level.I will try it again and post the exact message.
Thanks again for your quick response.
Once again sorry to all of you for my late response
Thanks,
Sri

Master Data Attributes issue in BEx

Hi Everyone,
I have loaded Master Data Attributes and Texts for 0customer. 0Customer has one Display attribute. I add this into the Bex Query Designer.But the data for the display Attribute(SORT1) is not displayed in the Analyzer. I have maintained everything correctly. The Baclkend BI system has Data for the display attribute.
Do we require to do any additional settings in Query Designer for the dat ato be shown when we drag the display attribute into Query Designer Panel. I have maintained the Display settings correctly in Query Designer
Please Advise.
Regards,
Samir

Hi,
are you able to See no data in Field of Attribute(SORT1) or are you not able to see field Attribute(SORT1) in report?
if you are not able to see field Attribute(SORT1) in report, right click on 0Customer, select property and go to attribute tab. select Attribute(SORT1) from left to right. click ok. you will get field Attribute(SORT1) in report.
you are not able to See no data in Field of Attribute(SORT1). activate master data after maintaning master data and chech value is availble in attribute (SORT1)

Open Hub with Attributes and Texts

Hi,
I´d like to know if it´s possible to have one open hub (database table) with texts and attributes.
There´s no problem when I create it or it´s transformations and DTP´s, but when I try to load texts, after attributes load, it always generates a dump: SAPSQL_ARRAY_INSERT_DUPREC.
I´d like to know a way without using a DSO, any suggestions?!
Kind Regards,
Tomas

Hi,
Pls chk SAP notes system, check SAP note 668466 for some help for this error.
*As according to SAP NOTE ;668466*
Summary
Symptom
You load master data attributes or texts for a characteristic. The loading terminates with runtime errors of the type SAPSQL_ARRAY_INSERT_DUPREC or with error message RSDMD 199. The termination point is in the DBFIRE method of the CL_RSDMD_UPDATE_MASTER_DATA class.
Other terms
Loading master data, attributes, texts, SAPSQL_ARRAY_INSERT_DUPREC, CL_RSDMD_UPDATE_MASTER_DATA, DBFIRE
Reason and Prerequisites
When you load attributes or texts, data records are usually inserted in the master data tables of the characteristic using an array insert statement (P, Q, X, Y, T tables). This results in a SAPSQL_ARRAY_INSERT_DUPREC runtime error if data records that are to be inserted and that relate to the unique primary key of the relevant database table already exist in this table. The following possible reasons are currently known for the occurrence of the SAPSQL_ARRAY_INSERT_DUPREC runtime error:
1. Data inconsistencies in the master data tables of the characteristic
SAPSQL_ARRAY_INSERT_DUPREC runtime errors or RSDMD 199 may occur if the data appears in an inconsistent status in the master data tables of the characteristic before you load attributes or texts. Notes 323140, 566044, 592757 and 599269 describe this (among other things) in more detail.
2. Parallel loading of nondisjunct data packages
If master data attributes are loaded over several dialog processes that are running in parallel, you must guarantee that the data packages of the relevant request are strictly disjunct concerning the characteristic value. This means that all data records that belong to a certain characteristic value may only be contained in a single data package. If data records of a certain characteristic value are distributed over several data packages, this may cause conflicts during the parallel loading of these packages when the master data tables are accessed and this may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors.
The same conditions that apply to loading attributes also apply to loading language-independent master data texts. If language-dependent texts are loaded in parallel, the data packages must be disjunct in relation to the combination of characteristic value and language indicator.
Note 566044 also describes the problematic nature of nondisjunct data packages or duplicate or overlapping data records.
3. Parallel loading of time-dependent attributes or texts
When you load time-dependent attributes or texts, a data record that is to be loaded is assigned to a characteristic value and also specifically to a time interval within which the contained attribute values or texts are valid. For this reason, requests for loading time-dependent attributes or texts typically contain several data records for each characteristic value. If data records of a certain characteristic value or the combination of characteristic value and language indicator are distributed over several data packages, this may (as already explained) cause conflicts when the master data tables are accessed and may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199.
4. Delta update of an ODS object in a characteristic
If you use a delta update from an ODS object to load master data attributes or texts, the activation of the ODS object determines the contents of the data packages that are used for loading the attributes or texts. If all of the ODS loading requests that are used as the data basis for the update into the characteristic are activated together in one step, this guarantees that the system sets up the data packages strictly disjunct in relation to the key fields of the ODS object. If the key fields of the ODS object are displayed one for one on the compounded characteristic value in the update rules, the data may be updated to the characteristic in parallel and by package.
However, if ODS loading requests that were activated at different times appear in the data basis for the update, data records of a certain ODS key or characteristic value may be distributed over several data packages. As already explained, this may cause conflicts when you access master data tables of the characteristic, and it may result in SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199.
This problem is also described in Note 666213.
5. Simultaneous loading of attributes and transaction data
If, when loading attributes of a characteristic, you discover that there are still no entries in the master data tables (P, Q) for a specific characteristic value, the system prepares to insert corresponding data records into these database tables. You can load transaction data into an InfoCube or an ODS object, for example, with the option to create missing master data entries for characteristics that involved during the loading. If a request now creates entries for transaction data in the master data tables (P, Q) of the characteristic before the process has inserted corresponding data records into the master data tables (P, Q) for loading attributes for this characteristic, this may result in a SAPSQL_ARRAY_INSERT_DUPREC runtime error or error message RSDMD 199.
This problem may also occur if you load attributes simultaneously for a characteristic that contains the other characteristic as a navigation attribute or compounding part. If a characteristic is compounded to other characteristics or if it contains characteristics other than the navigation attributes, the system also creates SID values for these dependent characteristics when the attributes are loaded depending on the settings in the InfoPackage.
Solution
To repair a possible inconsistency in the data, implement the RSRV test for master data.
To avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199 when you load master data, carry out the following actions. The actions to be performed in each case depend on which of the above-mentioned reasons is responsible for the runtime error:
1. Data inconsistencies in the master data tables of the characteristic
If data inconsistencies are responsible for the runtime error, you can usually use the tests in transaction RSRV or the RSDMD_CHECKPRG_ALL program to solve this problem. Notes 323140, 566044, 592757 and 599269 describe these (among other things) in more detail. If you cannot implement an automatic correction in this way, you may have to use an ABAP program that is adjusted to the relevant situation to restore the data consistency.
2. Parallel loading of nondisjunct data packages
If the runtime error does not lead back to the parallel loading of nondisjunct data packages, you must identify the duplicate data records that cause the problem. As described in Note 566044, you can change the insertion into master data tables from one array insert to an individual insert statement. If you use a single record insert statement to insert data records, duplicate data records are logged in the monitor by error messages (RSDMD 196). If the data records of a failed request are still available in the PSA, you can also search for duplicate data records directly in the relevant PSA table.
You may also create duplicate data records if key values are changed in the transmission rules or update rules. If relevant rules are defined, you should check these to see if they can possibly create duplicate data records. If this is the case, you must correct the rules accordingly.
3. Parallel loading of time-dependent attributes or texts
The extractors used for loading time-dependent attributes or texts cannot guarantee that all data records assigned to a certain key value are contained together in only one data package. For this reason, to avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199, you should not load time-dependent attributes and texts in parallel. Data packages are processed serially if the 'PSA only' and 'Update Subsequently in Data Targets' settings under 'Processing' are used in the InfoPackage.
4. Delta update of an ODS object in a characteristic
To avoid SAPSQL_ARRAY_INSERT_DUPREC runtime errors or error message RSDMD 199 during the delta update from an ODS object to a characteristic, you must ensure that the data basis used for the update to the characteristic consists exclusively of ODS loading requests that were activated together in one step only. Note 666213 describes in detail how you can ensure this.
5. Simultaneous loading of attributes and transaction data
If the runtime error occurs because another load task creates SID values or master data for the same characteristic at the same time when attributes are loaded, you can only solve the problem by rescheduling. The load task in question must be scheduled in such a way that you can exclude simultaneous processing.
*pls assign points,if info is useful*
Regards
CSM reddy

How to extract master data attribute from r/3 to bw give steps details

how to extract master data attribute from r/3 to bw give steps details screenshots

Hi
Go through the below process to extract Master Data Attribute from R/3
Hi,
Maintaining Generic DataSources
Use
Regardless of the application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any transparent table, database view or SAP Query InfoSet, or using a function module. This allows you to extract data generically.
Procedure
Creating Generic DataSources
1. Select the DataSource type and specify a technical name.
2. Choose Create.
The screen for creating a generic DataSource appears.
3. Choose the application component to which you want to assign the DataSource.
4. Enter the descriptive texts. You can choose any text.
5. Select the datasets from which you want to fill the generic DataSource.
a. Choose Extraction from View if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the database view or transparent table.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
b. Choose Extraction from Query if you want to use a SAP Query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
c. Choose Extraction Using FM if you want to extract data using a function module. Enter the function module and extraction structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process
For information about the function library, see the ABAP Workbench: Tools documentation.
d. With texts you also have the option of extracting from fixed values for domains.
6. Maintain the settings for delta transfer, as required.
7. Choose Save.
When performing extraction, note SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extraction structure contains a key figure field that references a unit of measure or a currency unit field, this unit field has to be included in the same extraction structure as the key figure field.
A screen appears on which you can edit the fields of the extraction structure.
8. Edit the DataSource:
○ Selection
When you schedule a data request in the BI scheduler, you can enter the selection criteria for the data transfer. For example, you can determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
○ Hide field
You set this indicator to exclude an extraction structure field from the data transfer. The field is no longer available in BI when you set the transfer rules or generate the transfer structure.
○ Inversion
Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is marked as an inversion field, for example, the update mode field in DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BI.
If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is transferred to BI in inverted form (multiplied by 1).
○ Field only known in exit
You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed to the extractor from the field list and selection table.
Deselect the Field Only Known in Exit indicator to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list and in the selection table.
9. Choose DataSource ® Generate.
The DataSource is saved in the source system.
Maintaining Generic DataSources
● Change DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component or change the texts of a DataSource. Double-click on the name of the table, view, InfoSet or extraction structure to get to the appropriate maintenance screen. Here you make the changes to add new fields. You can also completely swap transparent tables and database views, though this is not possible with InfoSets. Return to DataSource maintenance and choose Create. The screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BI system, choose DataSource ® Test Extraction.
● Delta DataSource
On the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the corresponding query. If you want to delete a DataSource, make sure it is not connected to a BI system.
NR

Master data attributes with direct update...its very urgent

Hi all,
Could anyone tell me how to laod the master data attributes with direct update in the infopackge..
provide steps to create master data attributes and how to load..
Thanks,
Manjula

Hi Manjula,
Flexible Uploading
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
honor with points if this helps,
Sudhakar

Loading GL Master Data -- Attributes, Text, Hier ; and Transaction Data

Hi all,
Could any one give me the steps individually to load the following type of data in BI 7.0:
1. Master Data with Attributes
2. Master Data with Text
3. Master Data with Hierarchy
4. Transaction Data
Do I have to create the Transformation and DTP's individually to load all the above kind of Data?
Please give me the information as much as you can.
Thanks,

For master data when you create tranformation it will prompt infoobject to act as infoprovider, and then you create DTP to schedule data to it. It works fine with attribute and Texts, though hierarchy dosn;t support much features of 2004s at my side. Like i am not able to migrate Hierarchy datasource to 2004s, and even when i replicate it, it comes as 3.5 datasource only.
For transaction data follow Gokuls step, or try to find on forums you will get lot of discussion on it.

InfoProvider: infoObject (master data attribute and text)

Similar Messages

Maybe you are looking for