Using master data attribute in BEx Query u0096 formula

Hello,
I want to use the master data attribute (Eg. Customer master 0CUSTOMER, 0ALTITUDE (Geo Location Height)) in query formula calculation. How do I do this?
Please help me.
Thank you
Subbu

Hi Subramaniam,
You can definately use the master data attributes in the formula calculation if that is a numeric value (logically u can use a characteristic in formula).
for e.g Net weight from 0MATERIAL can be used through formula variable in formula but Color is a characteristic and there is no point in using that in a formula.

Similar Messages

How to use Master Data Attribute of in Update Rule's Formula

Hi experts.
In update rule, there is an option to use Master Data Attribute of. However, due to user requirement, I need to use that in Formula instead.
Field to update:
Profit Center
Logic:
If Cost Center is empty
Then Profit Center
Else
Master Data Attribute of Cost Center
I use the following formula at the moment but it is not 100% correct.
IF( Cost Center = '', Profit Center, Cost Center )
Appreciate if anyone could help me out.
Thanks!

Hi,
The easier thing to do will be to use a Update Routine.
Logic will be as follows :-
If Cost center iss initial.
Result = Profit Center
else.
result = Cost center.
endif.
Regards
SM

Using "Master Data Attribute of" in the Update Rule

Hi,
In my update rule of, i want to replace the master data attribute of my characteristic instead of using its source characteristic. For example. InfoObject ZSTORECODE has an attribute ZSTORENAME. My objective is to use the Store Name instead of a Store Code.
I initially thought of using "Master Data Attribute of" in the update rules. However, I always end of with having an error of "No Values."

Hope you guys can help me with this!
Thanks,
Raomon

DATA: V_NSTC_SN2,
V_KFC_COSTC LIKE RSGENERAL-CHAVL.
V_KFC_COSTC = DATA_PACKAGE-KFC_COSTC.
CALL FUNCTION 'RSAU_READ_MASTER_DATA'
 EXPORTING
 I_IOBJNM = 'KFC_COSTC'
 I_CHAVL = V_KFC_COSTC
* I_T_CHAVL =
* I_DATE =
* I_FLG_WHOLE_TABLE =
 I_ATTRNM = 'NSTC_SN2'
IMPORTING
* E_STRUCTURE =
* E_TABLE =
 E_ATTRVAL = V_NSTC_SN2
 EXCEPTIONS
 READ_ERROR = 1
 NO_SUCH_ATTRIBUTE = 2
 WRONG_IMPORT_PARAMETERS = 3
 CHAVL_NOT_FOUND = 4
 OTHERS = 5
RESULT = V_NSTC_SN2.
Another Example Code:
index on infoObject

Can't assign an infoobject using master data attribute of

I've added in 0purch_group to my cube and I want to assign it using the master data attribute selection but it doesn't bring back anything to choose from. the attribute is 0mat_plant_purch_group and I've made it navigational. any ideas?

So do you say that you dont have mat_plant included in ur cube.
Then what are trying to get into the field with out a source field. How do you want to fill the value if you dont have mat_plant - i mean which of 100 values of matplant and attribute values should be populated.

Using Master data Attributes

Hi All,
How do I use the attributes of master data in reporting if they are defiend as Keyfigures?
Appreciate your Help in Advance.
Regards,
Harika

Hi
I think I am not much Clear with my question.Let me explain with an example.
I have 0mat_plant for which I have enhanced a zfield (Zverpr). Now that I want this field to be available for reporting.
I want Mat_Plant Zverpr in the report to be displayed.
HArika.

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

Can routine replace "master data attribute of" update rule for performance?

Hi all,
We are working on CRM-BW data modeling, We have to look up agent master data for agent level and position for each transaction data. So now we are using "Master data attribute of" update rule. Can we use routine instead of "Master data Attribute of" ? Will it improve the loading performance? Since we have to load 1 lack transaction records , where as we have 20,000 agent details in agent master data.My understanding is, for each record in data package the system has to go to master data table and bring the agent details & store in cubes. Say one agent created 10 transactions, then this option "master data attribute of" will read the agent master data 10 times even though we are going to pull same details for all 10 transactions from master data. if we use routine, we can pull the agent details& storing in internal table removing all duplicates and in update routine we can read the internal table.
Will this way improve performance?
let me know if you need further info?
Thanks in advance.
Arun Thangaraj

Hi,
your thinking is absolutely right!
I don't recommend to use the standard attribute derivation since it will perform a SELECT to the database for EACH record.
Better implement a sorted table in your start routine; fill it with SELECT <fields> FROM <master_data_table> FOR ALL ENTRIES OF datapak WHERE OBJVERS = 'A' etc...
In your routine perform a READ itab ... BINARY SEARCH.... I believe that you won't be able to go faster...
hope this helps...
Olivier.

Webi error for master data attributes if universe is on top of BI query

Hi All,
We are using BO XI R2 SP5 integrated with SAP BI 7.0.
We have built a universe on top of a BI query and when we try to build a web intelligence report that includes master data attributes like Customer City,Customer Region etc BO throws the following error:
Error 1:
Database error: [SOFA Driver] : Error getting members for hierarchy (level=ZFI_I03/ZFI_I03_Q0003, member=[ZFI_I03___F172], opcode=[ZFI_I03___F172]) . System error in program CL_RSDM_READ_MASTER_DATA and form VALUEREAD-02- (see long text). Contact your Business Objects administrator or database supplier for more information. (Error: WIS 10901)
For a universe built on a different BI query with master data attributes mentioned above,a different error occuring.
Error 2:
Your Web Intelligence session has timed out. Log out and log in again to InfoView. (Error: WIJ 77778)
We have tried:
1) We have executed the function module BAPI_MDPROVIDER_GET_DIMENSIONS with necessary inputs query/cube and we got correct output, like members, optional properties, selected properties and restrictions.But, still our problem remains same.
2) Transaction u201CRSRTu201D and executed the query,transaction RSRV to check SID-tables and the related masterdata.
Above steps we performed in response to SAP tickets 541052 / 2009,541131 / 2009 based on logs generated,but still the error persists.
What is working:
If a universe is built on top af an infocube directly, then there is no problem with master data attributes in webi report.
Please let us know if you need more details to help us resolve this issue.

Hi Naresh,
based on the MDX you can identify that those are navigational attributes and thats why the issue is not happening when talking to the cube directly because when you connect to the cube directly the navigational attributes are not available.
Take a look at note : 996197
not sure if it will solve the problem because there are other notes when you search for the error message but this was most of the times the one that resolved the issue.
the issue is in the BAPI functions
Ingo

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)

Force read/refresh of master data attributes on query

Hi there,
We're having troubles with one input ready query that changes and attribute value (KYF) of one characteristic. That works fines and whe can save changed data on the infoprovider via DTP. Problem is when data is saved we need to refresh query as whe have both values on screen (original value as char attribute on rows) new value as input ready KYF, so after save we would like to see that both values are the same.
Is there any way of force query no to read from caché as whe are changing master data attributes. I read something about IF_RSMD_RS_ACCESS class that can be implemented on Master Data access and force it there but sounds really hard so if this is the way can some of you guys give us some help.
I hope I make myself clear on the explanation...
Thanks in advance,
Regards
Carlos

Dear All,
The recent days that I tried working on changing master data attributes through BPS didn't work out.The Primary reasons was that some of the attributes that I needed to change were not present in the transaction or planning cubes and the characteristics that are not part of your cube on which the planning area is based then you can not do changes on them.
This is my undestanding .Please correct me if I am wrong.
Besides , I was also thinking if we can do the same through portal.i.e retriving the master data infoobject ( based on the value seleceted for that infoobject by the user ) and its attributes in the portal , edit them and save them back so that the updated values goes back to BW master data infoobject data base tables and updates the value.
Eg . I have Natural Account master data infoobject in the BW with attributes fucntional area and expense center.Based on the user selection of any values for the Natural account lets say 01110 , then for 01110 natural account the portal should display the correspoding attributes values of fucntional area and expense center.Lets take this values as 10 , 20 respectively for fucntional area and expense center . What I want to do now is to change these attrbute values to 30 and 40 and I would like to save it back as the changed attribute values for that natural account for 01110 with new attribute values 30 & 40 respectively for fucntional area and expense center .
Is this possible through portal and BW?
Any idea on this would be appriciated.
Regards,
Ankit
Edited by: Ankit Bhandari on Nov 21, 2008 12:21 PM
Edited by: Ankit Bhandari on Nov 21, 2008 12:32 PM

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

Error while trying to retrieve data from BW BEx query

The following error is coming while trying to retrieve data from BW BEx query (on ODS) when the Characters are more than 50.
In BEx report there is a limitation but is it also a limitation in Webi report.
Is there any other solution for this scenario where it is possible to retrieve more than 50 Characters?
A database error occured. The database error text is: The MDX query SELECT { [Measures].[3OD1RJNV2ZXI7XOC4CY9VXLZI], [Measures].[3P71KBWTVNGY9JTZP9FTP6RZ4], [Measures].[3OEAEUW2WTYJRE2TOD6IOFJF4] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [ZHOST_ID2].[LEVEL01].MEMBERS, [ZHOST_ID3].[LEVEL01].MEMBERS ), [ZHOST_ID1].[LEVEL01].MEMBERS ), [ZREVENDDT__0CALDAY].[LEVEL01].MEMBERS ) ........................................................ failed to execute with the error Invalid MDX command with UNSUPPORTED: > 50 CHARACT.. (WIS 10901)

Hi,
That warning / error message will be coming from the MDX interface on the BW server. It does not originate from BOBJ.
This question would be better asked to support component BW-BEX-OT-MDX
Similar discussion can be found using search: Limitation of Number of Objects used in Webi with SAP BW Universe as Source
Regards,
Henry

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

Where to set lock while loading master data attributes

Hello Experts,
I have two different datasources from ECC which loads into 0CUST_SALES attributes. I'm using two different DTP & transformation which are loading data in the this infoobject attributes.
When i try to load data, the DTP fails with an error message at "Updating attributes for InfoObject 0CUST_SALES Processing Terminated" & the job log says: "Lock NOT set for: Loading master data attributes".
Here what exactly LOCK means?
Thanks in advance.
Zakir Khan.

Hi,
The lock means that some program is updating the master data (a table) and at the same time other program can not update that same master data. When the first program completes the updation it will release the lock so that the other program can update this.
In your case you and schedule the DTP one after another.
Thanks

Map My Update Rule from a Master Data Attribute

Hello experts,
I haven't tried this scenario yet, hope you can help me, the Issue is this
I have 2 InfoObjects ZPSCHRCHY and 0PROFIT_CTR from InfoCube WBS cost and allocations I want both the InfoObjects to be mapped to 0PROFIT_CTR attribute of 0WBS_ELEMT master data object, I have tried the Master Data Attribute but only 0PROFIT_CTR is an attribute of the Master Data.how can I mapped ZPSCHRCHY and 0PROFIT_CTR to 0PROFIT_CTR?, Is creating a start routine for it must be used? Thank you very much
Regards and Thanks
Chris

PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TYPES:
BEGIN OF r_MD_WBS_ELEMENT,
 WBS_ELEMT like /BI0/PWBS_ELEMT-WBS_ELEMT,
 OBJVERS like /BI0/PWBS_ELEMT-OBJVERS,
 PROFIT_CTR like /BI0/PWBS_ELEMT-PROFIT_CTR,
END of r_MD_WBS_ELEMENT.
DATA: t_MD_WBS_ELEMENT TYPE STANDARD TABLE OF r_MD_WBS_ELEMENT,
 wa_MD_WBS_ELEMENT TYPE r_MD_WBS_ELEMENT.
$$ end of global - insert your declaration only before this line -
The follow definition is new in the BW3.x
TYPES:
BEGIN OF DATA_PACKAGE_STRUCTURE.
 INCLUDE STRUCTURE /BIC/CS8ZPSG030.
TYPES:
 RECNO LIKE sy-tabix,
END OF DATA_PACKAGE_STRUCTURE.
DATA:
DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
 WITH HEADER LINE
 WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
 MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
 DATA_PACKAGE STRUCTURE DATA_PACKAGE
USING RECORD_ALL LIKE SY-TABIX
 SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
to make monitor entries
REFRESH: t_MD_WBS_ELEMENT.
 SELECT WBS_ELEMT
 OBJVERS
 PROFIT_CTR
 INTO TABLE t_MD_WBS_ELEMENT
 FROM /BI0/PWBS_ELEMT
 FOR ALL ENTRIES IN DATA_PACKAGE
 WHERE WBS_ELEMT = DATA_PACKAGE-WBS_ELEMT.
 IF sy-subrc EQ 0.
 Do nothing
 ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.

Using master data attribute in BEx Query u0096 formula

Similar Messages

Maybe you are looking for