Skip to Content
author's profile photo Former Member
Former Member

Console Security

MDM Experts,

I have query regardind the constraints tht appear in Console.

Why in the Console’s security tabs constraints appear only for certain tables?

Kindly share views,

Krutarth

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 08:45 AM

    hi,

    For Certain tables only (upto SP5 version), constraints funcationality is available.

    Futher more you see in release notes in SP6.

    follow the link:

    SAP MDM 5.5 SP06 Release Notes ( https://service.sap.com/~sapidb/011000358700001124542007E )

    hope this may help you,

    Regards

    srinivas

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Krutarth

      check 134 and 135 pages of SAP MDM Console Document.

      The record constraints for a role are displayed in the Constraints column of the grid within the Tables and Fields tab,

      Record constraints are selections of masks and/or other lookup table records that allow you to create virtual subset catalogs on a per role basis. These subsets are dynamic in that they can be based not only on

      masks but also on lookup values. Only main table records that fall within the constrained record set will ever be visible or known to the role. For the Masks table and for each lookup table that is referenced by at

      least one single-valued lookup field and no multi-valued lookup fields, you can specify constraints by selecting which masks or lookup values – and therefore which main table records – should be visible and

      accessible for the role. For each table for which you can assign constraints, the value in the

      Constraints column is as follows:

      • [ALL] – table not constrained

      • [n] – table constrained to include ‘n’ selected records

      NOTE ►► You cannot manually create the [0] case (i.e. ‘n’ equals 0), which sometimes occurs if all the records to which a role is constrained are replaced or deleted. This prevents the role from gaining full access to the entire set of records in the table. Also, if the role had access to all replaced records, it will have access to all replacement records.You add constraints by selecting one or more values from the dual-list drop-down control for multiple-item selection in the Constraints column, as described below.

      �� To specify constraints for a table:

      1. In the Tables and Fields tab, double-click on the corresponding cell in the Constraints column.

      2. MDME opens a dual-list drop-down control for multiple-item selection. Select or deselect mask or lookup record values from the drop-down list or hierarchy, as follows:

      �� To add Available value(s) to the Selected values list, highlight them and click the Add button.

      �� To remove values from the Selected values list, highlight them and click the Remove button.

      �� To add all of the values to the Selected values list, click All.

      �� To remove all of the values from the Selected values list, click None.

      3. Press Enter or click on the up triangle to close the drop-down control.

      4. To save the new Constraints, right-click on the Tables and Fields tab and choose Save Role from the context menu, or press Shift+Enter.

      Catalog Security

      NOTE ►► MDME indicates that the table has constraints in the Tables and Fields tab by replacing [ALL] in the Constraints column with the number of selected record values in square brackets ([n]).

      NOTE ►► The available values appear as a list for flat lookup tables and as a hierarchy for the Masks table and hierarchy lookup tables.

      TIP ►► When you add constraints for a table, the values that you select become the unconstrained values and the values that you do not select become the constrained values.

      NOTE ►► When you add constraints for a table, the set of selected (unconstrained) values always implicitly includes the NULL value.

      NOTE ►► Constraints are combined just as normal search selections are combined (OR within fields; AND between fields).

      NOTE ►► Specifying constraints is like specifying search selections that are always in effect even when you reset the search, permanently limiting the set of visible records in the main table to: (1) those that are in the selected masks; and/or (2) those whose lookup values are set to the selected (unconstrained) values.

      NOTE ►► Whereas adding search selections in a search tab limits the set of values in every other search tab but does not self-limit the set of values in that search tab, adding constraints does self-limit the set of search tab values to just the selected (unconstrained) values.

      NOTE ►► In addition to limiting the main table records and selflimiting the set of search tab values, specifying constraints also limits:

      (1) the set of visible lookup table records when the current table is the lookup table; and (2) the set of visible lookup table values in the Record Detail tab when the current table is the main table.

      NOTE ►► Whereas the set of main table records limited by a mask is static until you explicitly change the set of records in the mask, the set of main table records limited by a constraint changes automatically when lookup field values change in the underlying records.

      NOTE ►► In fact, constraints work on the entire lookup table hierarchy, including nested lookup tables, and the available list of tables to constrain is determined by the single-valued use of a table in the lookup hierarchy. For example, if Manufacturers had a singlevalued lookup into States, constraining the user to a particular state would only show manufacturers in that state, and only products for those manufacturers.

      Regards

      Hari

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 08:33 AM

    HI Krutharth

    Reagarding this Constraints Please gothrough the document SAP MDM Console document page no 134 and 135 from this u can gain good knowledge about Constraints..

    IF NOT COME BACK TO ME .

    Regards

    Hari

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 08:51 AM

    hi,

    MDM Server and MDM Console

    o Roles may include constraints based on Named Searches.

    o The Relationships table in the MDM Console now contains the Code field.

    o The default Remote System is created as type Inbound/Outbound (previously

    Inbound).

    o Austrian German is available as a data language.

    More information: MDM 5.5 SP06 – Console Reference Guide.

    the above points given in the release notes.

    hope this may help you,

    Regards,

    Srinivas

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.