Chronological key and hierarchy

Hi Team,
I have few questions on OBIEE can any body reply please
Is it possible to create two hierarchy for one dimension table...?
Can we create one hierarchy for two dimensional table..?
why we have to enable the cronological key for time series functions..?
Thanks in advance,

799666 wrote:
Is it possible to create two hierarchy for one dimension table...?Yes. You can create multiple hierarchies in one dimension. You can even share parent/child level in across multiple hierarchies. For example, you can create 1. Year - Month - Day and 2. Year - Quarter - Month - Week - Day. Here Day is shared leaf level.
799666 wrote:
Can we create one hierarchy for two dimensional table..?I guess not. A dimension can based on only one logical dimension table.
799666 wrote:
why we have to enable the cronological key for time series functions..?Chornological key is to let BI server know which columns can be sorted in a Chronological order. These columns need not restricted to date columns, but can be numbers or even varchars. Examples would be Year (like 2006, 2007, 2008…) or Year-Qtr (like 2006-Q1, 2006-Q2 …). These keys are used by BI server to perform Time Series function such as AGO and TODATE.

Similar Messages

URGENT: Issue with hierarchy level keys and report drill down

Hi,
BASIC STRUCTURE:
I have created a subject area with 3 facts (FACT_A, FACT_B, FACT_C) and 4 dimesnions (TIME_DIM,DIM_2,DIM_3,DIM_4). Each fact table also has additional aggregate tables aggregated along levels of the time dimension. Also our timw dimension has aggregated dimension tables like TIME_DIM_WEEK, TIME_DIM_MONTH, TIME_DIM_QUARTER and TIME_DIm_YEAR.
GOAL:
All 3 facts have the same measures M_1 and M_2 in them but may not have data for the same dimension values selected.
For example
For month JAN 2000 FACT_A.M1=100$ and no data exists for JAN 2000 in FACT_B and FACT_C. Then in the report
for JAN2000 it should show FACT_A.M1= $100, FACT_B.M1 = 0 and FACT_C.M1 =0. In this case I should be able to drill down to the lowest level.
ISSUE:
The time dimension TIME_DIM has the following levels - Total -> Year -> Quarter -> Month -> Week -> Day
However I am having an issue with drill down in the reports whenever I pull metrics from more than 1 fact at a time. I have defined the level keys but not sure if I need to do anything in addition since I am using aggregates.
I have to fix this issue quickly. Please help me.

Alastair,
All the fact tables have aggregated facts as sources.
I have checked the levels set for each of the sources to the time dimesnion table in BMM and they look okay. So the Time dim table in BMM has 4 source tables
Time_Day (level set to day, table key is "day"),
Time_month (level set to month, table key is "Fiscal_Month_Code"),
Time_Quarter(level set to quarter, table key is "Fiscal_Quarter_Code") and
Time_Year(level set to year, table key is :Fiscal_Year_Code").
Note: No time week aggregate added as logical source.
Again the time dim hierarchy based off of this table has levels: Total -> Year ->quarter -> Month -> week -> day
The levels keys set for each level are
Year -> Primary key is Year_Name (YYYY)(Checked as chronological key) and another key is Year_Num (YYYY)(Checked as chronological key)
Quarter->Primary Key is Quarter_Name (YYYY Qn), another key is Quarter_Number (Format n where n can assum values 1,2,3,4). Both keys are set as chronological keys
Month -> Primary key is Month_Name (MON YYYY), another key is Month_Num (Format n where n can assume values from 1 to 12) Both keys are set as chronological keys
Week -> Primary Key is week name (YYYY Wk nn, where nn can have values from 1 to 53), another key is week num (nn, where nn can have values from 1 to 53)
Day -> primary key set to day (date format)
Issue1: When I try to drill to lower levels it throws out an error saying report cannot find any data because filters may be too restrictive even though I see data at higher level
For ex: If I drill down to Year: 2010 and Qtr: 2010 Q2 and M1:$100 when I click on Qtr to drll to month level it throws me the error
Issue2: when I add year and qtr colums to the report I see data as below which is incorrect
Year_Name Qtr_Name data:FACTA_M1 Data: FactB_M1
2009 2009 Q1 $10 $5
2009 2009 Q2 $20 $80
2009 2009 Q3 $20
2009 2009 Q4 $30
2010 2010 Q1 $100
2010 Q2 $101
2010 Q3 $102 $230
2010 Q4 $103
2011 Q1 $10
In the above example year_name is not showing up for 2010 Q2 and after. However if I change the primary key for level 'Quarter' by having key consist of year name and quarter name instead of just quarter name the issue doesnt occur and drill down works great. The only issue is when I drill from qtr it first shows year name and quarter name instead of showing the next level which would be month name.
Sorry about the long message but I thought you might notice something in how I have set up the keys.
Thanks

Primary Key and Chronological Key for Time Dimension

Could someone please shed light whether it's better to use normal PK or Calendar Date (which is a chronological key on the most detailed level). I tried both and haven't noticed any difference. But my understanding is that I still need to have the PK key on the most detailed level in time hierarchy.
Thanks

Matt,
the PK of the Time Dimension is a regular sequence numeric key. I have it defined as a logical PK for the dimension. However, I guess I was talking about hierarchy key. I tested it either way and the query time is the same. So I guess it doesn't really matter.
--------Year
Year (chronological key and primary key)
------------------Quarter
Quarter (key)
Quarter+Year (primary key, chronological key)
---------------------------------Day Detail
PK (key)
Date (primary key , chronological key)
I hope it makes sense.

OBIEE - use of chronological Key

Hi all,
can any body explain in detail what is the use of chronological key and why we need to enable the
time dimension at time of creating a time dimension hierarchy.
Thanks
bharath

HI Bharth,
What is the chronological key use?
A. Typically time dimension differs from all other dimensions in one way and that is,
all other dimensions dont care about the order of the values in it.
e.g. in region_dim the values are north, south, west and east. Here nobody wants to see whether north comes first or south comes first. i.e. no order is required here.
in the case of time dimension there needs to be a particular order for all the values present in it.
e.g. 2010 is earliest and 2004 is older. Dec-10 is earliest and jan-10 is older. i.e. the values in the time dimensiion needs to follow a particular sorting order. So the chronological key is the key which tells the obiee that the data is incrementing based on the chronological column.
Here you may get another doubt. i.e. you are having columns like year, half_year, quarter, month, week and day. Here which one should become the chronolgocial key?
Analyse it yourself. If you kept year as chro key then obiee will be confused whether jan-10 is earliest or feb-10 is earliest. Because it knows only that 2010 is earliest and 2009 is older.
So always it should be the lowest level oif the dimension which needs to be the chronological key. In the abouve case it should be date.
You can select either date or date_id(this could be a sequence generator values).
2. what is the use time dimension?
A.If all you want is to achieve drills from Month, Quarter and Year then treat it as a normal dimension and create the levels. But if you want to do calculations like YTD, QTD and MTD then you need to create a time dimension.
http://oraclebizint.wordpress.com/2007/11/05/oracle-bi-ee-101332-understanding-todate-and-ago-achieving-ytd-qtd-and-mtd/
Refer the above link for time dimension.
Hope this help's
Thanks,
Satya

Display key and text by WAD command in custom structure hierarchy

Hi everybody,
I have a query using a custom structure with hierarchy layout. As usual the structure does only display its text as descriptions but I can enable the display the key in BEx Web by right-click on the analysis item --> Properties --> Characteristic --> Display. Unfortunately these setting can not be defined directly in the structure within the Query Designer.
For a workaround I put the query into a web template, in which I used the Set Presentation (SET_PRESENTATION) command to enable key and text display from the start. Hence I put that command in the wem template parameters Action Before First Rendering (ACTION_BEFORE_FIRST_RENDERING). Everything is working properly and makes me very happy.
But... there is one thing missing, I would like to implement... I want a toggle button, which allows the user to switch between key and text display and text display. Unfortunately setting the same command from Action Before First Rendering (ACTION_BEFORE_FIRST_RENDERING on a various button does not working. The button command only affects data rows of the leaves of the structure hierarchy. All parent nodes do not change their appearance.
Any ideas how to solve this?
Thank you for any helps and comments!
Sebastian

Hi Sebastian,
I have a similar problem. Can you help me? How did you set the entry in Member Presentation of Command SET_PRESENTATION to display key and text? I just found the values to set the only text or only key.
best regards,
Barbara

Time dimension and chronological key

HI ALL
I WORK ON OBIEE 11G REPORTS
WHAT IS THE EXACT USE OF TIME CHECK BOX AND CHRONOLOGICAL KEY??
AND HOW CAN I USE IT
ANY HELP ??

Hi,
What is the chronological key use?
A. Typically time dimension differs from all other dimensions in one way and that is,
all other dimensions dont care about the order of the values in it.
e.g. in region_dim the values are north, south, west and east. Here nobody wants to see whether north comes first or south comes first. i.e. no order is required here.
in the case of time dimension there needs to be a particular order for all the values present in it.
e.g. 2010 is earliest and 2004 is older. Dec-10 is earliest and jan-10 is older. i.e. the values in the time dimensiion needs to follow a particular sorting order. So the chronological key is the key which tells the obiee that the data is incrementing based on the chronological column.
Here you may get another doubt. i.e. you are having columns like year, half_year, quarter, month, week and day. Here which one should become the chronolgocial key?
Analyse it yourself. If you kept year as chro key then obiee will be confused whether jan-10 is earliest or feb-10 is earliest. Because it knows only that 2010 is earliest and 2009 is older.
So always it should be the lowest level oif the dimension which needs to be the chronological key. In the abouve case it should be date.
You can select either date or date_id(this could be a sequence generator values).
2. what is the use time dimension?
A.If all you want is to achieve drills from Month, Quarter and Year then treat it as a normal dimension and create the levels. But if you want to do calculations like YTD, QTD and MTD then you need to create a time dimension.
http://oraclebizint.wordpress.com/2007/11/05/oracle-bi-ee-101332-understanding-todate-and-ago-achieving-ytd-qtd-and-mtd/
Refer the above link for time dimension.
Award points it is useful.
Thanks
satya
Edited by: Satya Ranki Reddy on May 2, 2012 12:29 AM

Chronological Key

Hi friends,
Im trying to do YTD and PTD calculation using the following below links
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540/dimensions.htm#i1023744
By using 'todate' function i can able to do it. But im having a doubt in setting a chronological key. Assume that suppose if im calculating year to date for my Measure column 'Dollars'
ill be taking the following syntax in the expression builder like
todate(dollars, year), but before doing that i need to set an chronological key in the time dimension hierarchy level.
Since im having the following time dimension levels
year
half
quarter
month
week
day
Whether i need to set a chronological key for all the levels, or i need to set only for the lowest level 'day'. For which level i need to set chronological key inorder to get correct results.
Thanks
Brgds,
GTA

Also,You can also set it for all levels except the Grand Total Level to get good performance...so that each time it doesn't goto lowest level even if its not required.
Setting Chronological Keys for Each Level
Designate a chronological key for every level of each dimension hierarchy. This key must meet the requirements of being sequential (the members have a natural order), cardinal (all members are spaced the same distance apart at a given level, such as day or month), and complete (no members missing).
The Oracle BI Server uses the chronological key to create mathematically correct time series predictions, such as Jan + 2 months = Mar. You should set a chronological key for every level (except for the Grand Total level) so that you can perform time series operations on all levels with good performance. This enables you to use an AGO, TODATE, or PERIODROLLING function for any level of any time dimension hierarchy, such as fiscal month ago, calendar year ago, and day ago.
Theoretically, time series functions operate correctly if only the bottom level key in the Logical Dimension is chronological. In practice, however, this causes performance problems because it forces the physical query to use the lowest grain, causing joins of orders of magnitude more rows (for example, 365 times more rows for a "year ago" joining at the "day" grain). It also means higher-level aggregate tables are never selected by the query planner when using the time series functions, which again significantly slows the query.
Hope this helps

Regarding Logical level key and row wise initialization

Hi Gurus,
What is the purpose of row wise initialization in external table authentication and when we have to go for row wise initialization.
Why we have to enable logical level key in hierarchy is this only for getting drill down to the next level if we make two columns as logical level key what will happens. If we want to enable a column as a logical level key what are the character sticks that column should satisfy.
Thanks,

1) Row Wise Initialization used to hold multiple values in a variable. Let says SQL gives 4 rows (A,B,C,D) as output. Now I want to hold 4 value in a variable to get this happen we need to go for RowwiseIniziation. If you do not do this at any point in time Variable holds only value A not others. Simply it works as Array.
2) Level keys define the unique elements in each level and provide the context for drill down. You can make two logical columns as logical key but you need to make sure what to be displayed in your hierarchy by selecting DISPLAY. If you make to as separate logical keys and set Display for both you get two columns in the hierarchy
http://gerardnico.com/wiki/dat/obiee/hierarchy_level_based

Update keys and fields

Hi All,
In my landscape, we have 2 remote systems for mdm. ( say source as BO, target as ECC).
When we import data from BO, we are generating key (based on Account group.) using Remote system key generation technique.
But,at the same time we want to update same key value for the customer field.
Is there any technique we can update key value for the field values?

If I understand correctly, you want to populate both the Remote Key and a customer field with the same value taken from the BO system. In your import map, select the field coming from BO in the Source Hierarchy Pane, right click, and select clone field. You should then be able to map the field from BO to [Remote Key] and the cloned field to the customer field.

A way to distinguish between 'Parent' keys and 'Referential' keys

Hi,
We use referencial keys to specify the FK to a parent table and also link to other tables... I need to write a script that needs to distinguish between a 'Parent' key and and a 'Referential' keys. In the database they both look the same, as they are both foreign keys...
What's the easiest way to determine whether a FK is a link to a parent table or a link to an unrelated table..
I hope this question makes sense...
EDIT:
Here's an example of the tables, and a better explanation
CREATE TABLE PARENT_TABLE(
par_id number PRIMARY key,
par_name varchar2(200)
create TABLE RELATED_TABLE(
rel_id number PRIMARY key,
rel_name varchar2(200)
create TABLE CHILD_TABLE(
kid_id PRIMARY key,
kid_name varchar2(200),
par_id,
rel_id,
CONSTRAINT kid_par_fk FOREIGN KEY(par_id) REFERENCES PARENT_TABLE(par_id),
CONSTRAINT kid_rel_fk FOREIGN KEY (rel_id) REFERENCES RELATED_TABLE(rel_id)
)Ok, as you can see the child table has 2 references but no way to tell which one is the parent table.. In our database we have this hirearchy of parent-child tables (where it's one-to-many relationships) where we consider a table a parent of other.. And also we have a ton of other foreign keys that link to related tables (many-to-many) relationships...
Now i need a clean way of distinguishing between PARENT and RELATED table.. A more elegegant solution to a keeping a hierarchy table of parent, child tables.. I'm sure others have this kind of structure..
let me know if there is more clarification needed.. Sorry for the confusion..
Edited by: wonderboy87 on 23-Jan-2011 4:07 PM
Edited by: wonderboy87 on 23-Jan-2011 5:59 PM
Edited by: wonderboy87 on 23-Jan-2011 6:00 PM

wonderboy87 wrote:
Yes sorry.. I can see how consufing this is. Here goes;
CREATE TABLE PARENT_TABLE(
par_id number PRIMARY key,
par_name varchar2(200)
create TABLE RELATED_TABLE(
rel_id number PRIMARY key,
rel_name varchar2(200)
create TABLE CHILD_TABLE(
kid_id PRIMARY key,
kid_name varchar2(200),
par_id,
rel_id,
CONSTRAINT kid_par_fk FOREIGN KEY(par_id) REFERENCES PARENT_TABLE(par_id),
CONSTRAINT kid_rel_fk FOREIGN KEY (rel_id) REFERENCES RELATED_TABLE(rel_id)
)Ok, as you can see the child table has 2 references but no way to tell which one is the parent table.. You are right. There is no way to tell which one is the "parent". It's only your own business rules and usage that make one of the FK relationships to a "parent" while the other is to .. what, an "uncle"? ;-) Oracle has no way of knowing what your business rules and usage are.
In our database we have this hirearchy of parent-child tables (where it's one-to-many relationships) where we consider a table a parent of other.. And also we have a ton of other foreign keys that link to related tables (many-to-many) relationships...
Now i need a clean way of distinguishing between PARENT and RELATED table.. A more elegegant solution to a keeping a hierarchy table of parent, child tables.. I'm sure others have this kind of structure..
let me know if there is more clarification needed.. Sorry for the confusion..
Edited by: wonderboy87 on 23-Jan-2011 6:00 PM

What is use of chronological key

hi all
when i was trying to perform Time series functions ..why we have to select the chronological key..?
i have created time dimension..and i have created year,month,week,day...levels in year level i have added calendar_yaer and
calendar_year_id,....and i defined two columns as key values.... and calendar_year for drill down...
in that if i use calendar_year as chronological key what would be the result...
if i use caleendar_year_id as chronological key what would be the result....
i tried it and both are giving same result...
i don't under stand why we have to select the chronological key???
please any one tel me about it
Thanks

Typically time dimension differs from all other dimensions in one way and that is,
all other dimensions dont care about the order of the values in it.
e.g. in region_dim the values are north, south, west and east. Here nobody wants to see whether north comes first or south comes first. i.e. no order is required here.
in the case of time dimension there needs to be a particular order for all the values present in it.
e.g. 2010 is earliest and 2004 is older. Dec-10 is earliest and jan-10 is older. i.e. the values in the time dimensiion needs to follow a particular sorting order. So the chronological key is the key which tells the obiee that the data is incrementing based on the chronological column.
Here you may get another doubt. i.e. you are having columns like year, half_year, quarter, month, week and day. Here which one should become the chronolgocial key?
Analyse it yourself. If you kept year as chro key then obiee will be confused whether jan-10 is earliest or feb-10 is earliest. Because it knows only that 2010 is earliest and 2009 is older.
So always it should be the lowest level oif the dimension which needs to be the chronological key. In the abouve case it should be date.
You can select either date or date_id(this could be a sequence generator values).
Hope you understand this.

Blocked and Hierarchial ALV s

Hi Experts,
wht is the use of blocked and hierarchial ALV's.
In which situations are they used? Can u provide any material
Thank You

hi,
<b>Block ALV</b> means more than one list in one screen.
Means u can have many list in one screen at a time.
Like this,
TYPE-POOLS : slis.
TABLES : mara,
         makt.
SELECT-OPTIONS : mat FOR mara-matnr.
DATA : BEGIN OF itab OCCURS 0,
        matnr LIKE mara-matnr,
        maktx LIKE makt-maktx,
        matkl LIKE mara-matkl,
        mtart LIKE mara-mtart,
       END OF itab.
DATA : BEGIN OF itab1 OCCURS 0,
        mtart LIKE mara-mtart,
        count TYPE i,
       END OF itab1.
DATA : BEGIN OF itab1_col OCCURS 0,
        mtart LIKE mara-mtart,
        count TYPE i,
       END OF itab1_col.
DATA : t_fcat1 TYPE slis_t_fieldcat_alv,
       t_fcat2 TYPE slis_t_fieldcat_alv,
       wa_fcat TYPE slis_fieldcat_alv,
       t_eve TYPE slis_t_event,
       wa_eve TYPE slis_alv_event,
       t_layout TYPE slis_layout_alv.
DATA : v_repid LIKE sy-repid,
       t_mat LIKE mara-matnr.
DEFINE create_fcat.
clear wa_fcat.
wa_fcat-fieldname = &1.
wa_fcat-seltext_l = &2.
wa_fcat-outputlen = &3.
append wa_fcat to t_fcat1.
END-OF-DEFINITION.
START-OF-SELECTION.
PERFORM get_data.
PERFORM dis_data.
*&      Form get_data
      text
FORM get_data.
SELECT amatnr bmaktx amtart amatkl INTO CORRESPONDING FIELDS OF TABLE itab
FROM mara AS a INNER JOIN makt AS b ON
amatnr = bmatnr
WHERE a~matnr IN mat.
LOOP AT itab.
    itab1-mtart = itab-mtart.
    itab1-count = 1.
    APPEND itab1.
ENDLOOP.
SORT itab1 BY mtart.
LOOP AT itab1.
    MOVE-CORRESPONDING itab1 TO itab1_col.
    COLLECT itab1_col.
ENDLOOP.
ENDFORM.                    "get_data
*&      Form dis_data
      text
FORM dis_data.
v_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
    EXPORTING
      i_callback_program      = v_repid.
REFRESH t_fcat1.
CLEAR t_fcat1.
REFRESH t_eve.
wa_eve-name = 'TOP_OF_PAGE'.
wa_eve-form = 'TOP_OF_PAGE1'.
APPEND wa_eve TO t_eve.
create_fcat:
'MATNR' 'Material' '10',
'MAKTX' 'Material Description' '40',
'MTART' 'Type' '10',
'MATKL' 'Group' '10'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
    EXPORTING
      is_layout   = t_layout
      it_fieldcat = t_fcat1
      i_tabname   = 'ITAB'
      it_events   = t_eve
    TABLES
      t_outtab    = itab.
REFRESH t_fcat1.
CLEAR t_fcat1.
REFRESH t_eve.
wa_eve-name = 'TOP_OF_PAGE'.
wa_eve-form = 'TOP_OF_PAGE2'.
APPEND wa_eve TO t_eve.
create_fcat:
'MTART' 'Type' '10',
'COUNT' 'Total' '5'.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
    EXPORTING
      is_layout   = t_layout
      it_fieldcat = t_fcat1
      i_tabname   = 'ITAB1_COL'
      it_events   = t_eve
    TABLES
      t_outtab    = itab1_col.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'.
ENDFORM.                    "dis_data
*&      Form top_of_page1
      text
FORM top_of_page1.
FORMAT COLOR COL_POSITIVE.
WRITE:/ 'First Block'.
FORMAT COLOR OFF.
ENDFORM.                    "top_of_page
*&      Form top_of_page2
      text
FORM top_of_page2.
FORMAT COLOR COL_NEGATIVE.
WRITE /5 'Second Block'.
FORMAT COLOR OFF.
ENDFORM.                    "top_of_page
In <b>hierarchical ALV</b> hierarchy will create,
Like This,
TYPE-POOLS : slis.
TABLES : mseg.
DATA : BEGIN OF itab_head OCCURS 0,
        matnr LIKE mseg-matnr,
        werks LIKE mseg-werks,
       END OF itab_head.
DATA : BEGIN OF itab_item OCCURS 0,
        matnr LIKE mseg-matnr,
        werks LIKE mseg-werks,
        mblnr LIKE mseg-mblnr,
        menge LIKE mseg-menge,
       END OF itab_item.
DATA : t_fcat TYPE slis_t_fieldcat_alv,
       key_info TYPE slis_keyinfo_alv,
       t_eve TYPE slis_t_event,
       gt_subtot TYPE slis_t_sortinfo_alv,
       subtot LIKE LINE OF gt_subtot,
       t_listhead TYPE slis_t_listheader,
       st_line TYPE slis_listheader.
DATA : t_mtdoc LIKE mseg-mblnr.
SELECT-OPTIONS : mat FOR mseg-matnr.
INITIALIZATION.
PERFORM build_cat USING t_fcat.
PERFORM build_eve.
START-OF-SELECTION.
PERFORM get_data.
PERFORM dis_data.
*&      Form build_cat
      text
     -->TEMP_FCAT text
FORM build_cat USING temp_fcat TYPE slis_t_fieldcat_alv.
DATA : wa_fcat TYPE slis_fieldcat_alv.
wa_fcat-tabname = 'ITAB_HEAD'.
wa_fcat-fieldname = 'MATNR'.
wa_fcat-seltext_m = 'Material'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB_HEAD'.
wa_fcat-fieldname = 'WERKS'.
wa_fcat-seltext_m = 'Plant'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB_ITEM'.
wa_fcat-fieldname = 'MBLNR'.
wa_fcat-seltext_m = 'Material Doc.'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB_ITEM'.
wa_fcat-fieldname = 'MENGE'.
wa_fcat-seltext_m = 'Quantity'.
wa_fcat-do_sum = 'Y'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
subtot-spos = 1.
subtot-fieldname = 'MATNR'.
subtot-tabname = 'ITAB_HEAD'.
subtot-up = 'X'.
subtot-group = 'X'.
subtot-subtot = 'X'.
subtot-expa = 'X'.
APPEND subtot TO gt_subtot.
ENDFORM.                    "build_cat
*&      Form build_eve
      text
FORM build_eve.
DATA : wa_eve TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
   EXPORTING
     i_list_type           = 0
   IMPORTING
     et_events             = t_eve
EXCEPTIONS
    LIST_TYPE_WRONG       = 1
    OTHERS                = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE t_eve INTO wa_eve WITH KEY name = 'TOP_OF_PAGE'.
IF sy-subrc = 0.
    wa_eve-form = 'TOP_OF_PAGE'.
    MODIFY t_eve FROM wa_eve INDEX sy-tabix.
ENDIF.
ENDFORM.                    "build_eve
*&      Form get_data
      text
FORM get_data.
SELECT matnr werks mblnr menge FROM mseg INTO CORRESPONDING FIELDS OF TABLE itab_item
WHERE matnr IN mat.
ENDFORM.                    "get_data
*&      Form dis_data
      text
FORM dis_data.
key_info-header01 = 'MATNR'.
key_info-item01 = 'MATNR'.
key_info-header02 = 'WERKS'.
key_info-item02 = 'WERKS'.
REFRESH itab_head.
LOOP AT itab_item.
    ON CHANGE OF itab_item-matnr OR itab_item-werks.
      MOVE-CORRESPONDING itab_item TO itab_head.
      APPEND itab_head.
    ENDON.
ENDLOOP.
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
    EXPORTING
      i_callback_program             = 'ZHEIRALV_PRDS'
     i_callback_user_command        = 'USER_COMMAND'
      it_fieldcat                    = t_fcat
      it_sort                        = gt_subtot
      it_events                      = t_eve[]
      i_tabname_header               = 'ITAB_HEAD'
      i_tabname_item                 = 'ITAB_ITEM'
      is_keyinfo                     = key_info
    TABLES
      t_outtab_header                = itab_head
      t_outtab_item                  = itab_item
EXCEPTIONS
PROGRAM_ERROR                  = 1
OTHERS                         = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    "dis_data
*&      Form top_of_page
      text
FORM top_of_page.
CLEAR st_line.
st_line-typ = 'H'.
st_line-info = 'Dhwani Shah'.
APPEND st_line TO t_listhead.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary       = t_listhead
I_LOGO                   =
I_END_OF_LIST_GRID       =
I_ALV_FORM               =
ENDFORM.                    "top_of_page
reward if useful.

What is exactly meant by text and hierarchy??

what is exactly meant by text and hierarchy??
if i have cust_id as characteristic and cust name,address etc as its attributes what will be text and hierarchy in this case??

Hi
There are three different types of master data in BI:
1.       Attributes
Attributes are InfoObjects that are logically subordinate to a characteristic. You cannot select attributes in the query.
You assign the attributes Person responsible for the cost center and Telephone number of the person responsible for the cost center (characteristics as attributes), as well as Size of the cost center in square meters (key figure as attribute) to a Cost Center.
2.       Texts
You can create text descriptions for master data or load text descriptions for master data into BI. Texts are stored in a text table.
In the text table, the Name of the person responsible for the cost center is assigned to the master data Person responsible for the cost center.
3.       Hierarchies
A hierarchy serves as a context and structure for a characteristic according to individual sort criteria. For more detailed information, see Hierarchies.
Features
Time-dependent attributes:
If the characteristic has at least one time-dependent attribute, a time interval is specified for this attribute. Since the time frame for master data on the database must always be between 01.01.1000 and 12.31.1000, the gaps are filled automatically (see Maintaining Time-Dependent Master Data).
Time-dependent texts:
If you create time-dependent texts, the system always displays the text for the key date in the query.
Time-dependent texts and attributes:
If texts and attributes are time dependent, the time intervals do not have to agree.
Language-dependent texts:
In Characteristic InfoObject Maintenance, you specify whether texts are language specific (for example, with product names: German ® Auto, English ® car) or are not language specific (for example, customer names). The system only displays texts in the selected language.
If texts are language dependent, you have to load all texts with a language indicator.
custid as characteristic and cust name,address etc as its attributes what will be text and hierarchy_
Cust name will be text
address will be text
custid will be hirerchy_
Only texts exist:
You can also create texts only for a characteristic, without maintaining attributes. When you load texts, the system automatically generates the entries in the SID table.
Hope it helps
Regards
gaurav

Search for [Remote Key] and [Remote System] in Data Manager

Hello all
I would like to be able to search on the remote key and the remote system in the MDM Data Manager is that not possible? I thought I remembered seeing that possibility under the Free-Form Search but now I can't find it.
I have, however, found this in the Data Manager reference guide:
REMOTE SYSTEM AND REMOTE KEY FIELDS
MDM uses the remote systems defined in the Remote Systems table
within the MDM Console to store and maintain key mapping information
for each record or text attribute. It does this using a virtual key
mapping field that you never see in the MDM Client.
This virtual key mapping field is very much like a qualified lookup field
into a virtual key mapping qualified lookup table.
Key Mapping information stored in virtual lookup field
The Remote System and Remote Key fields are normally not visible;
however, they do appear in several places in the MDM Client.
Specifically, both fields: (1) appear in the File > Export dialogs in Record
mode for exporting value pairs; (2) are recognized by the File > Import
dialog in Record mode for importing value pairs; and (3) appear in the
Edit Key Mappings dialogs in both Record mode and Taxonomy mode,
for viewing and editing value pairs.
Is there any way to search on the value in the remote key from the Data Manager?

Not sure search i think not possible.
But you can see keys as mentioned:
Enable Key mapping in Console.
MDM Client maens MDM Data Manager.
They do appear in several places in the MDM Client or Data Manager. Three different methods to see in DM are given already below:
Specifically, both fields: (1) appear in the File > Export dialogs in Record mode for exporting value pairs; (2) are recognized by the File > Import dialog in Record mode for importing value pairs; and (3) appear in the Edit Key Mappings dialogs in both Record mode and Taxonomy mode, for viewing and editing value pairs.
BR,
Alok

Diff b/w primary key and unique key?

what is the diff b/w primary key and unique key?

Hi,
With respect to functionality both are same.
But in ABAP we only have Primary key for the Database tables declared in the Data Dictionary.
Unique is generally is the term used with declaring key's for internal tables.
Both primary and Unique keys can identify one record of a table.
Regards,
Sesh

Chronological key and hierarchy

Similar Messages

Maybe you are looking for