Distinct count of role-played dimension attribute

Needed distinct count of AccountGroup attribute of AccountB dimension which is a role played dimension of Account.
Added measure distinct count of the dimension attribute (AccountGroup). In dimension usage added the main fact table as intermediate for other dimensions with many2many relationships.
The two role played Account dimensions must be related to the new AccountFact table with fact relationship.
But then how will I be able to count distinct attribute of
certain Account dimension (out of the two role played dimensions)???
Namnami

Thanks for the links, they are useful. But still they do not explain how to manage a distinct count of
certain role played dimension attribute. 
I gave up on this and added that dimension attribute to the fact table so now I do a regular distinct count on a cube fact measure. 
Thanks
Namnami

Similar Messages

  • Many to many relationship does not work on certain role played dimension

    Hi,
    I have a cube with role playing Account dimension, used once as “Account” and once as “Other Account” dimension.
    I’ve added Trip dimension related to the account dimension by a bridge table AccountTrip 
    making a many to many relationship (many accounts can be in one trip and one account can go to many trips).
    When I added the bridge measure group to the cube, I saw in the dimension usage tab that the relationship between the bridge and the Account dimension was done automatically.
     I added the trip dimension with regular relationship to the bridge measure group and many to many relationship to the main fact table using the bridge group.
    All compiled fine and gave correct results. Then I noticed that when slicing the fact table by the Other account dimension I get correct results,
     but when I add the Trip dimension I get the results as if I was slicing by the Account dimension, not by the “Other account” dimension.
    I checked the cube and noticed I did not set the relationship between the bridge to the “Other Account” dimension (role playing). I set it now (regular relationship, same as the account dimension), but still getting the same results.
    Conclusion-  when slicing by the new Trip (M2M) dimension and the “Other Account”
     (role played) dimension I get the results of the “Account” dimension, not those of the “Other Account” dimension.
    I checked the relationships of the “Other Account” dimension in the cube but it looks correctly set (to the external account of the main fact table and to account of the bridge table).
    (Just to note I have two other bridges on the cube which are not related and don’t look like they need to be related, plus two other measure groups of the main fact table used for distinct count which are related appropriately).
    What else should be done???
    I would greatly appreciate your help!
    Thanks
    Namnami

    The update server is down; try this temporary workaround
    App Store>Purchased>Select "All"
    Note: Look out for apps that have the word "Update"
    http://i1224.photobucket.com/albums/ee374/Diavonex/9c256282736869f322d4b3071bbb2 a82_zps51a6f546.jpg

  • Bridge table to Role Playing Dimension

    Hi,
    Fact Sales table has role playing Customer dimension table related to it. For each role it had a relationship in the DSV. One on CustomerA the other on CustomerB.
    Now I have a trip dimension which should have a many to many relationship to the customers table. So I set a bridge table relating trip to customer.
    But when I slice by trip it only displays the sales that have CustomerA in the trip.
    I want it to display the sales that have CustomerB in the trip.
    How can I affect that?
    Thank you
    Namnami

    When you create a M2M relationship, you specify 2 dimensions and one intermediate measure Group.
    Even if the bridge table is loaded once in the DSV (even if you can just duplicate it to simplify its naming), you define two measure groups for the bridge table, one connected to Customer A and Trip A, and the other to Customer B and Trip B. Then, you define
    M2M relationship between Trip A and Customer A using bridgeA as intermediate, and do the same for B.
    Again, please, since M2M require understanding how it works internally, I suggest you to read the White paper I mentioned, because you have all the information there that will allow you to design the model you need. I think it's not a discussion that is
    easy to complete in a forum thread, because M2M involves many side consequences in calculation (e.g. what happen to unrelated dimensions involved in calculation?).
    Marco Russo (Blog,
    Twitter,
    LinkedIn) - sqlbi.com:
    Articles, Videos,
    Tools, Consultancy,
    Training
    Format with DAX Formatter and design with
    DAX Patterns. Learn
    Power Pivot and SSAS Tabular.

  • Automated Duplication for Role Playing Dimensions

    Im wondering if there is way to automate (short cut method) to duplicate the entire Dimension.
    Simply copying and pasting or Duplicating will not create the Hierarchies.
    For Example:
    I have Fact_Transaction (with columns Trx_Id, Trx_Date, Create_Date, Update_Date, Invoice_Date, Amount)
    I have a date dimension joined to this fact in physical layer on the Trx_Date.
    Problem:
    Now if I get a requirement to show the other dates 2 as dimension,
    I need to create alias for the same time dim and manually create the dimensions and hierarchies in the BMM layer.
    Is there any much better way we can do this using some scripts (xudml, /commands, ..etc)
    Thanks
    Kaushik

    Hi,
    I think you have to create it manually...

  • How to create a role-playing Date dimension?

    I have created a date dimension Date_Dim with three levels DayL, MonthL, YearL and one hierarchy YearL-Monthy-DayL. In the fact table, I need to refer to two date dimension: Start_Date and End_Date. For the Start_Date, we can refer it to the created physical date dimension Date_Dim. For the End_date, Ralph Kimball recommended to use a role-playing dimension. That is, create a view End_Date_Vw from the dimension table Date_Dim. My question is how to create it in OWB? Should we need to define the levels and hierarchies for the view in order to leverage the query-rewrite power? How to do that? Any advice or information is appreciated.
    Lushu

    Balaji,
    You can refer to the same dimension more than once in the design of a cube (fact table). In a star schema implementation, you just end up with multiple foreign keys to the same times dimension (table). Once you integrate with a reporting tool, you refer to the same dimension using different names. Warehouse Builder supports this in the integration with Oracle Discoverer. The user's guide tells you how to do this (see http://download-west.oracle.com/docs/html/B12146_01/integrating.htm#sthref3659).
    Thanks,
    Mark.

  • Difference between Conformed dimnesion and Role play dimesion

    hi,
    I am not able to understand difference between Conformed dimension and Role play dimension.. Can anyone please explain the diff between both with real time example.
    I am confused with Date Dimension.
    Here i encountered, Cube dimension and Database dimension,what is that actually.
    Thanks

    Hi DevBi,
    According to your description, you want to know the difference between database dimension and cube dimension. Right?
    A database dimension is a collection of related objects, called attributes, which can be used to provide information about fact data in one or more cubes. What we created in BIDS is database dimension. For example, typical attributes in a product dimension
    might be product name, product category, product line, product size, and product price. These objects are bound to one or more columns in one or more tables in a data source view.
    Cube dimension is an instance of a database dimension in a cube is called a cube dimension and relates to one or more measure groups in the cube. A database dimension can be used multiple times in a cube. Those referenced and renamed for purpose database dimension
    is role-playing dimension. For example, a fact table can have multiple time-related facts, and a separate cube dimension can be defined to assist in analyzing each time-related fact. However, only one time-related database dimension needs to exist, which
    also means that only one time-related relational database table needs to exist to support multiple cube dimensions based on time.
    Reference:
    Role-playing Dimensions
    If you have any question, please feel free to ask.
    Simon Hou
    TechNet Community Support

  • Distinct count of dimension business key in fact table

    In my cube I have a fact table which joins to a patient dimension.  The patient dimension is a type 2.  What I would like to do is get a distinct count of patients who have records in the fact table.   The business key in the patient dimension
    is the PrimaryMrn.  So a SQL query would look like this.
    SELECT count(distinct PrimaryMrn)
    FROM EncounterFact e
    INNER JOIN PatientDim p
    on e.PatientKey = p.PatientKey
    Is it possible to do this via MDX?
    Thanks for the help.

    If you have to distinct count an attribute in a SCD 2, you might choose between:
    Denormalizing that attribute in the fact table, and the create a classical DISTINCT COUNT measure
    Use a many-to-many approach - see the "Distinct Count" scenario in the Many-to-Many White paper here:
    http://www.sqlbi.com/articles/many2many (for both Multidimensional and Tabular
    If you use Tabular, you might want to read also this pattern:
    http://www.daxpatterns.com/distinct-count/
    Marco Russo http://www.sqlbi.com http://www.powerpivotworkshop.com http://sqlblog.com/blogs/marco_russo

  • How to get Distinct Count of Products across two dimensions

    Hi,
    I have two dimensions, Item and Presentations. I need to get distinct count of products for IMD_Id + Merc_Pres_Id. IMD_Id is the lowest member in Item and Merc_Pres_Id is lowest in Presentation. My MDX query is given below but when I apply filters to
    slice it, it does not work and does not give right count. It always gives the count for all.
    /* Last Year Demand - Demand for 12 months back of selected months */
    With
    Member [Measures].[LYDemand]
    as
    Sum(
    Generate(
    EXISTING[All Date].[Fiscal Month Name].[Fiscal Month Name].Members,
    {parallelperiod([All Date].[Fiscal Month Name].[Fiscal Month Name], 12
    ,[All Date].[Fiscal Month Name].CurrentMember)}
    ,[Measures].[Proj Demand]
    /* Last to last Year Demand - Demand for 24 back of selected months */
    Member [Measures].[LLYDemand]
    as
    Sum(
    Generate(
    EXISTING[All Date].[Fiscal Month Name].[Fiscal Month Name].Members,
    {parallelperiod([All Date].[Fiscal Month Name].[Fiscal Month Name], 24
    ,[All Date].[Fiscal Month Name].CurrentMember)}
    ,[Measures].[Proj Demand]
    /* Current Year Active Products */
    Member [Measures].[CYCount]
    as
    CASE
    WHEN
    [Measures].[Proj Demand] > 0
    THEN
    DistinctCount(Existing(([All Items].[IMD Id].[IMD Id],[All Merchandise Presentations].[Merch
    Pres Key].[Merch Pres Key])))
    ELSE
    NULL
    END
    /* Last year Active Products */
    Member [Measures].[LYCount]
    as
    CASE
    WHEN
    [Measures].[LYDemand] > 0
    THEN
    DistinctCount(([All Items].[IMD Id].[IMD Id],[All Merchandise Presentations].[Merch Pres Key].[Merch Pres
    Key], [All Items].[Style Name].CurrentMember, (StrToMember('[All Date].[Fiscal Month Name].&[201401]',CONSTRAINED).Lag(12)
    : StrToMember('[All Date].[Fiscal Month Name].&[201411]',CONSTRAINED).Lag(12))))
    ELSE
    NULL
    END
    /* Last to last Year Active Products */
    Member [Measures].[LLYCount]
    as
    CASE
    WHEN
    [Measures].[LLYDemand] > 0
    THEN
    DistinctCount(([All Items].[IMD Id].[IMD Id],[All Merchandise Presentations].[Merch Pres Key].[Merch Pres
    Key], [All Items].[Style Name].CurrentMember, (StrToMember('[All Date].[Fiscal Month Name].&[201401]',CONSTRAINED).Lag(24)
    : StrToMember('[All Date].[Fiscal Month Name].&[201411]',CONSTRAINED).Lag(24))))
    ELSE NULL END
    SELECT
    [Measures].[CYCount], [Measures].[LYCount], [Measures].[LLYCount],
    [Measures].[Proj Demand],[Measures].[LYDemand],[Measures].[LLYDemand]
    ON
    COLUMNS,
    Non
    Empty([All Items].[Demand Center Name].[Demand Center Name], [All Items].[Style Name].[Style Name])
    ON ROWS
    FROM
    (SELECT (StrToSet('[All Items].[Style].[ALL]'))
    ON COLUMNS
    FROM
    (SELECT (StrToSet('[All Items].[Demand Center].[ALL]'))
    ON COLUMNS
    FROM
    (select (STRTOSET('[All Items].[Merch Group].&[MG-110]'))
    on Columns
    FROM
    (SELECT (StrToSet('[All Merchandise Presentations].[Merch Pres Chnl Dkey].&[MPC-1]'))
    ON COLUMNS
    From
    [FMI Forecasting]
    WHERE {strToMember('[All Date].[Fiscal Month
    Name].&[201401]',CONSTRAINED) :
    StrToMember('[All Date].[Fiscal Month Name].&[201411]',CONSTRAINED)}
    Requirements are as follows:
    1. Distinct Count should not include products where Proj Demand is 0, when I am using Filter function to remove products with 0 demand, query is really slow and execution time goes up from 35- 40 secs to 8-9 Minutes.
    2. When we apply filter (parameters) Distinct Count should be in the context of filters( which are mentioned in the select statement like Style, Demand Center and Merch Group). Currently after applying filters count does not change.
    Thanks for help.

    Hi Skd78,
    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Distinct count mdx fails

    Hi,
    I have a question about performing a distinct count of number of clients in my cube OLAP. 
    My clients-dimension table is populated from 4 different databases, this means that I can find the same clients with different Clients_ID (Natural key), because each client has a different ID in every database.  
    I want to calculate a distinct count on client’s phone number because it’s the same record in all Databases, I always get a big number which is not the right result.  I checked deeply the issue and I found that the query I set seems
    to not perform the distinct count right on the phone number.
    The small test I did with only filters (see screenshot below) let me believe that my query is performing the distinct count on each client ID instead of the phone number.
    Here it is the query I used to perform my distinct count:
    WITH SET MySet AS
    Filter(
    {[Dim Date].[Year].&[2014]} *
    {[DIM FA Clients].[FaCuNumberX].[FaCuNumberX]},[Measures].[QQT - Fact Ventes]>1 or [Measures].[QQT - Fact Ventes]=1)
    MEMBER MEASURES.SETDISTINCTCOUNT AS
    DISTINCTCOUNT(MySet)
    SELECT {MEASURES.SETDISTINCTCOUNT} ON 0
    FROM [CubeAll]
    I don’t know why the filter on this mdx query doesn’t work properly like an SQL group by.
    Thanks for help! 

    Hi Merouane,
    According to your description, you want to calculated to the numbers of client by count distinct Phone Number, right?
    In your scenario, you can add a distinct count measure in your project. Distinctcounts are one of the most demanding requests that can be placed on a MOLAP database, caused by the large number of dimensional attributes that typically exist in a cube. Here
    is a blog which describe several solutions for distinctcount in a SSAS project, please refer to the link below to see the detais.
    http://www.mssqltips.com/sqlservertip/3043/different-options-for-creating-a-distinct-count-measure-in-ssas/
    Regards,
    Charlie Liao
    TechNet Community Support

  • Distinct count for multiple fact tables in the same cube

    I'm fairly new to working with SSAS, but have been working with DW environments for many years.
    I have a cube which has 4 fact tables.  The central fact table is Encounter and then I also have Visit, Procedure and Medication.  Visit, Procedure and Medication all join to Encounter on Encounter Key.  The relationship between Encounter
    and Procedure and Encounter and Medication are both an optional 1 to 1.  The relationship between Encounter and Visit is an optional 1 to many.
    Each of the fact tables join to the Patient dimension on the Patient Key.  The users are looking for a distinct count of patients in all 4 fact tables.  
    What is the best way to accomplish this so that my cube does not talk all day to process?  Please let me know if you need any more information about my cube in order to answer this.
    Thanks for the help,
    Andy

    Hi Andy,
    Each distinct count measure cause an ORDER BY clause in the SELECT sent to the relational data source during processing. In SSAS 2005 or later, it creates a new measure group for each distinct count measure(it's a technique strategy for improving perormance).
    Besides, please take a look at the following distinct count optimization techniques:
    Create Customized Aggregations
    Define a Processing Plan
    Create Partitions of Equal Size
    Use Partitions Comprised of a Distinct Range of Integers
    Distribute the Hash of Your UserIDs
    Modulo Function
    Hash Function
    Choose a Partitioning Strategy
    For more detail information, please refer to the article below:
    Analysis Services Distinct Count Optimization:
    http://www.microsoft.com/en-us/download/details.aspx?id=891
    In addition, here is a good article about SSAS Best Practices for your reference:
    http://technet.microsoft.com/en-us/library/cc966525.aspx
    If you have any feedback on our support, please click
    here.
    Hope this helps.
    Elvis Long
    TechNet Community Support

  • Distinct Count doesn't return the expected results

    Hi All,
    I was fighting a little trying to implement a Distinct Count measure over an account dimension in my cube. I read a couple of posts relateed to that and I followed the steps posted by the experts.
    I could process the cube but the results I'm getting are not correct. The cube is returning a higher value compared to the correct one calculated directly from the fact table.
    Here are the details:
    Query of my fact table:
    select distinct cxd_account_id,
              contactable_email_flag,
              case when recency_date>current_date-365 then '0-12' else '13-24' end RECENCY_DATE_ROLLUP,
              1 QTY_ACCNT
    from cx_bi_reporting.cxd_contacts
    where cxd_account_id<>-1 and recency_date >current_date-730;
    I have the following dimensions:
         Account (with 3 different hierarchies)
         Contactable Email Flag (Just 3 values, Y, N, Unknown)
         Recency_date (Just dimension members)
    All dimensions are sparse and the cube is a compressed one. I defined "MAXIMUM" as aggregate for Contactable Email flag and Recency date and at the end, SUM over Account.
    I saw that there is a patch to fix an issue when different aggregation rules are implemented in a compressed cube and I asked the DBA folks to apply it. They told me that the patch cannot be applied because we have an advanced version already installed (Patch 11.2.0.1 ).
    These are the details of what we have installed:
          OLAP Analytic Workspace       11.2.0.3.0 VALID
          Oracle OLAP API 11.2.0.3.0 VALID
          OLAP Catalog 11.2.0.3.0 VALID
    Is there any other patch that needs to be applied to fix this issue? Or it's already included in the version we have installed (11.2.0.3.0)?
    Is there something wrong in the definition of my fact table and that's why I'm not getting the right results?
    Any help will be really appreciated!
    Thanks in advance,
    Martín

    Not sure I would have designed the dimensions /cubes as you,  but there is another method you can obtain distinct counts.
    Basically relies on using basic OLAP DML Expression language and can be put in a Calculated Measure, or can create two Calculated measures
    to contain each specific result.  I use this method to calculate distinct counts when I want to calculate averages, etc ...
    IF account_id ne -1 and (recency_date GT today-365) THEN -
    CONVERT(NUMLINES(UNIQUELINES(CHARLIST(Recency_date))) INTEGER)-
    ELSE IF account_id ne -1 and (recency_date GT today-730 and recency_date LE today-365) THEN -  
    CONVERT(NUMLINES(UNIQUELINES(CHARLIST(Recency_date))) INTEGER)-
    ELSE NA
    This exact code may not work in your case, but think you can get the gist of the process involved.
    This assumes the aggregation operators are set to the default (Sum), but may work with how you have them set.
    Regards,
    Michael Cooper

  • Distinct Count Calculation

    Hello everybody,
    I have a cube with appointments including dimensions for companies and dates.
    One of my measures is "Appointments" which is the count of all appointments. Another calculated member is "Visits" which is the count of appointments with the type of "Visits".
    This is my MDX epxression for "Visits":
    AGGREGATE([Appointment].[Type].&[Visit], [Measures].[Appointments])
    Now I would like to create a new calculated member "Company Visits" which should be the distinct count of "Visits" by company and date.
    Example: 2 "Visits" in one company on the same day should be 1 "Company Visit"
    In T-SQL this query works:
    COUNT(
    DISTINCT(
    CASE [Type]
    WHEN "Visit" THEN CAST([CompanyID] AS NVARCHAR) + CONVERT(NCHAR(8), CAST([Date] AS NVARCHAR))
    ELSE NULL
    END
    ) AS [Company Visits]
    How can I do this with MDX in calculations?
    Additionally I would like to have a calculated member "Days in Field" as distinct count of dates with "Visits".
    Thanks in advance and best regards
    Lars

    Hi Lars,
    Based on your description, you want to create a new calculated member to calculate the distinct count of "Visit" for each company, right? In this case, you can use DistinctCount to achieve your requirement, here is a sample query about DistinctCount function
    for your reqerence.
    with member [DistCount] as
    distinctcount(exists(Employee.Employee.children,,"Reseller Orders"))
    Select {[Measures].[Reseller Order Count],
    [Measures].[DistCount]} on 0,
    ([Employee].[Gender].children) on 1
    From [AdventureWorks]
    Reference:DistinctCount (MDX)
    Regards,
    Charlie Liao
    TechNet Community Support

  • Distinct Count in Explorer

    This is from BOB post, which was posted in 2008. Now it's 2013 and there is no solution by SAP? We are doing a POC on Explorer, this is probably time to scrap it. Very frustrating! Is there any
    Hi,
    We have 2 tables used in universe "orders" and
    "order_line_product_item" from where we are pulling data in explorer indexes.
    We have issues getting distinct count of
    customers in explorer when we bring data from order line product item level
    facets/dimension.
    Just wondering if anyone else had solution of how to
    handle this on explorer side?
    At universe level we using count (distinct cust key), which is working at
    webintelligence.
    Looks like BO XI R3 further enhanced on handling this kind
    of situation by implementing delegated measures, but don't find anything similar
    to it in BO explorer.
    Occurrences is always getting us count at the lowest grain level(basically row level
    counts, but we are looking for distinct counts though !) .
    Is getting
    distinct counts limitation in explorer?
    Any help will be greatly
    appreciated.
    Thanks,
    ~SK
    Courtesy of Sachin

    Hello,
    So if you have a calculation(Webi) function(Excel) built into the two tables you are using from the data source you might try 'configuring' the data as 'Occurance' from the workspace you created or after the file in index if you're using excel.  If you are using a universe as a data source for the exploration view set you can attempt to drag the 'measure' needed (count) into the workspace option "measure" when creating the workspace.
    I do hope this helps

  • Ignoring role playing relationship

    As is the case in most cubes, I have a role playing Date dimension.  The dimensions are [Date Created] and [Date Snapshot].  [Date Created] is snowflaked off the Ticket dimension using the DateCreatedKey.  [Date Snapshot] is related to my
    fact table using the DateSnapshotKey (the day the snapshot of the fact was taken).
    With this schema, I can find the number of tickets that were created in January 2014.
    SELECT
    [Number of Tickets] ON COLUMNS,
    [Date Created].[Month Year].&[201401] ON ROWS
    FROM
    [MyCube]
    I can also find the number of tickets that were in an Open status in January 2014
    SELECT
    [Number of Tickets] ON COLUMNS,
    [Date Snapshot].[Month Year].&[201401] ON ROWS
    FROM
    (SELECT [Ticket Status].[Ticket Status].&[1]
    ON COLUMNS FROM [MyCube])
    Now what I need to do is the get the number of open tickets in January 2014 (regardless of when they were created) and divide that by the number of new tickets in January 2014.  Here's what I tried
    WITH
    MEMBER OpenTickets AS
    ([Number of Tickets]
    , [Date Snapshot].[Month Year].&[201401])
    SELECT
    {[Number of Tickets], OpenTickets]}
    ON COLUMNS,
    [Date Created].[Month Year].&[201401] ON ROWS
    FROM
    [MyCube]
    However, what I get is the number of tickets created in January 2014 and the number of open tickets that were also created in January 2014.  All other open tickets are ignored.  How do I break that connection between dates so that the open tickets
    doesn't look at the date created?
    Stephanie

    In ssas, you can use the Dimension Usage tab in Cube Designer to view and edit the dimension relationships between cube dimensions and measure groups in the cube. If you break that connection between dates, you can to to the Dimension Usage
    tab to set it.
    http://msdn.microsoft.com/en-us/library/ms183558.aspx

  • 'dimension attribute was not found' error while refresing the cube in Excel

    Dear All,
    Thanks for all your support and help.
    I need an urgent support from you as I am stuck up here from nearly past 2-3 days and not getting a clue on it.
    I have re-named a dimension attribute 'XX' to 'xx' (Caps to small)in my cube and cleared all dependencies (In Attribute relationship tab as well).
    But while refreshing the data in excel client (of course after processing the full cube) I get an error
    'Query (1, 1911) the [Dimension Name].[Hierarchy Name].[Level Name].[XX] dimension attribute was not found' error.
    Here I am trying to re-fresh an existing report without any changes with the new data.
    Does not it re-fresh automatically if we clear the dependencies or there something that I am missing here (Like order of the dependencies).
    Cube processed completely after modifications and able to create new reports without any issues for same data. What else could be the reason?
    Can some one help me here?
    Thanks in Advance and Regards,

    Thnaks alot Vikram,
    In se11  ,when i was trying to activate the  /BIC/FZBKUPC , it is showing the warnings  like
    Key field KEY_ZBKUPCP has num. type INT4: Buffering not possible, Transport restricted.What it means.
    In PErformance Window it is showing like:
    A numeric type was used for a key field. A table of this sort cannot be buffered.When buffering, the table records for numeric values cannot be stored in plain text.
    Procedure
    You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
    If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
    Please adivice with your valueable suggestyions.
    Thanks Vikram.

Maybe you are looking for