Inherited Validations -  Validations On Hierarchy

Please confirm my understanding related to Validations in DRM
- What is the difference between a Validation which has its Inherited+ Check box Checked and Validation that I apply on the Hierarchy (Right click Hierarchy and apply) ??
My understanding-
When a Validation is Marked Inherited+ then - At real time when the Validation Runs on the current node it also runs on its descendants, --Please confirm this point_+
whereas if it is not Inherited and the Validation is Applied on the hierarchy, at Real Time the Validation Runs only on the current Node
Or- There is No difference in the above mentioned scenarios

You are correct that when inherited is set the validation will run for any descendant nodes as well. The inherited atrribute makes it easy to control if a validation runs for an entire hierarchy, only a branch (or sub-branch), or a particular node.

Similar Messages

  • Vertical Inheritance with Application ID Hierarchy

    Hello,
    I want to implement Vertical Inheritance with Application ID Hierarchy,
    using a HyperSonic-Database. The essential code is appended.
    The following test-application leads to an exception. Things work fine,
    if I use one ID-class for all persistent classes; a similar attempt with
    horizontal inheritance did work, too.
    String attr1Val = getUniqueString();
    String attr2Val = getUniqueString();
    // ... get PersistenceManager, etc.
    // Write something into DB
    pm.currentTransaction().begin();
    Parent p = new Parent();
    p.setattr1("attr1Value");
    Child c = new Child();
    c.setattr1("qwerty");
    c.setattr2(attr2Val);
    pm.makePersistent(c);
    pm.currentTransaction().commit();
    // Query
    Query query = pm.newQuery(Child.class,"attr2 == param");
    query.declareParameters("String param");
    Collection results = (Collection)query.execute(attr2Val);
    kodo.util.FatalUserException: Duplicate object ids have been assigned to
    two different objects: the identity "1" of class "class foo.Child$ID" was
    assigned to both "foo.Child@1f4cbee" and "foo.Child@787d6a". This can
    occur when a horizontally or vertically mapped class uses application
    identity with an auto-increment field and does not use a hierarchy of
    application identity classes.[foo.Child$ID-1]
    Can anyone help ?
    Thanks.
    Lutz
    code-pieces:
    parent.java:
    public class Parent implements Serializable,InstanceCallbacks
    private transient PersistenceManager pm = null;
    public Long ObjId;
    public void setObjId(Long value)
    ObjId = value;
    // application identity class for Manager; represented as
    // a static inner class for the persistable class
    public static class ID implements Serializable
    static
    { // register persistent class in JVM
    Class c = foo.Parent.class;
    public Long ObjId;
    public ID ()
    public ID (String str)
    fromString (str);
    public String toString ()
    return String.valueOf (ObjId);
    public int hashCode ()
    return ((ObjId == null) ? 0 : ObjId.hashCode ());
    public boolean equals (Object obj)
    if (this == obj)
    return true;
    if (obj == null || obj.getClass () != getClass ())
    return false;
    ID other = (ID) obj;
    return ((ObjId == null && other.ObjId == null) ||
    (ObjId != null && ObjId.equals (other.ObjId)));
    private void fromString (String str)
    if ("null".equals (str))
    ObjId = null;
    else
    ObjId = new Long (str);
    private String attr1;
    public Parent()
    public void jdoPreStore()
    // Some Action that needs to be done before data is flushed to
    datastore...
    if (ObjId == null)
    if (pm == null)
    pm = ResourceManager.getPersistenceMgr("test", "sa", "");
    SequenceGenerator gen = KodoHelper.getSequenceGenerator (pm,
    Parent.class);
    setObjId(new Long(gen.getNext().longValue()));
    parent.jdo:
    <jdo>
    <package name="foo">
    <class name="Parent" identity-type="application"
    objectid-class="Parent$ID">
    <field name="ObjId" persistence-modifier="persistent"
    primary-key="true"/>
    <field name="attr1" persistence-modifier="persistent"/>
    </class>
    </package>
    </jdo>
    child.java:
    public class Child extends Parent
    implements Serializable,InstanceCallbacks
    private transient PersistenceManager pm = null;
    public static class ID extends Parent.ID
    static
    { // register persistent class in JVM
    Class c = foo.Child.class;
    public ID()
    super();
    public ID (String str)
    super(str);
    public void jdoPreStore()
    if (ObjId == null)
    if (pm == null)
    pm = ResourceManager.getPersistenceMgr("test", "sa", "");
    SequenceGenerator gen = KodoHelper.getSequenceGenerator (pm,
    Child.class);
    setObjId(new Long(gen.getNext().longValue()));
    child.jdo:
    <jdo>
    <package name="foo">
    <class name="Child" persistence-capable-superclass="foo.Parent"
    identity-type="application" objectid-class="Child$ID">
    <extension vendor-name="kodo" key="jdbc-class-map-name"
    value="vertical">
    <extension vendor-name="kodo" key="table" value="CHILD"/>
    <extension vendor-name="kodo" key="ref-column.OBJID"
    value="OBJID"/>
    </extension>
    <field name="attr2" persistence-modifier="persistent"/>
    </class>
    </package>
    </jdo>
    generated mappings by "mappingtool -a refresh":
    parent.mapping:
    <mapping>
    <package name="foo">
    <class name="Parent">
    <jdbc-class-map type="base" table="PARENT"/>
    <jdbc-version-ind type="version-number" column="JDOVERSION"/>
    <jdbc-class-ind type="in-class-name" column="JDOCLASS"/>
    <field name="ObjId">
    <jdbc-field-map type="value" column="OBJID"/>
    </field>
    <field name="attr1">
    <jdbc-field-map type="value" column="ATTR1"/>
    </field>
    </class>
    </package>
    </mapping>
    child.mapping:
    <mapping>
    <package name="foo">
    <class name="Child">
    <jdbc-class-map type="vertical" ref-column.OBJID="OBJID"
    table="CHILD"/>
    <field name="attr2">
    <jdbc-field-map type="value" column="ATTR2"/>
    </field>
    </class>
    </package>
    </mapping>

    Hello,
    I want to implement Vertical Inheritance with Application ID Hierarchy,
    using a HyperSonic-Database. The essential code is appended.
    The following test-application leads to an exception. Things work fine,
    if I use one ID-class for all persistent classes; a similar attempt with
    horizontal inheritance did work, too.
    String attr1Val = getUniqueString();
    String attr2Val = getUniqueString();
    // ... get PersistenceManager, etc.
    // Write something into DB
    pm.currentTransaction().begin();
    Parent p = new Parent();
    p.setattr1("attr1Value");
    Child c = new Child();
    c.setattr1("qwerty");
    c.setattr2(attr2Val);
    pm.makePersistent(c);
    pm.currentTransaction().commit();
    // Query
    Query query = pm.newQuery(Child.class,"attr2 == param");
    query.declareParameters("String param");
    Collection results = (Collection)query.execute(attr2Val);
    kodo.util.FatalUserException: Duplicate object ids have been assigned to
    two different objects: the identity "1" of class "class foo.Child$ID" was
    assigned to both "foo.Child@1f4cbee" and "foo.Child@787d6a". This can
    occur when a horizontally or vertically mapped class uses application
    identity with an auto-increment field and does not use a hierarchy of
    application identity classes.[foo.Child$ID-1]
    Can anyone help ?
    Thanks.
    Lutz
    code-pieces:
    parent.java:
    public class Parent implements Serializable,InstanceCallbacks
    private transient PersistenceManager pm = null;
    public Long ObjId;
    public void setObjId(Long value)
    ObjId = value;
    // application identity class for Manager; represented as
    // a static inner class for the persistable class
    public static class ID implements Serializable
    static
    { // register persistent class in JVM
    Class c = foo.Parent.class;
    public Long ObjId;
    public ID ()
    public ID (String str)
    fromString (str);
    public String toString ()
    return String.valueOf (ObjId);
    public int hashCode ()
    return ((ObjId == null) ? 0 : ObjId.hashCode ());
    public boolean equals (Object obj)
    if (this == obj)
    return true;
    if (obj == null || obj.getClass () != getClass ())
    return false;
    ID other = (ID) obj;
    return ((ObjId == null && other.ObjId == null) ||
    (ObjId != null && ObjId.equals (other.ObjId)));
    private void fromString (String str)
    if ("null".equals (str))
    ObjId = null;
    else
    ObjId = new Long (str);
    private String attr1;
    public Parent()
    public void jdoPreStore()
    // Some Action that needs to be done before data is flushed to
    datastore...
    if (ObjId == null)
    if (pm == null)
    pm = ResourceManager.getPersistenceMgr("test", "sa", "");
    SequenceGenerator gen = KodoHelper.getSequenceGenerator (pm,
    Parent.class);
    setObjId(new Long(gen.getNext().longValue()));
    parent.jdo:
    <jdo>
    <package name="foo">
    <class name="Parent" identity-type="application"
    objectid-class="Parent$ID">
    <field name="ObjId" persistence-modifier="persistent"
    primary-key="true"/>
    <field name="attr1" persistence-modifier="persistent"/>
    </class>
    </package>
    </jdo>
    child.java:
    public class Child extends Parent
    implements Serializable,InstanceCallbacks
    private transient PersistenceManager pm = null;
    public static class ID extends Parent.ID
    static
    { // register persistent class in JVM
    Class c = foo.Child.class;
    public ID()
    super();
    public ID (String str)
    super(str);
    public void jdoPreStore()
    if (ObjId == null)
    if (pm == null)
    pm = ResourceManager.getPersistenceMgr("test", "sa", "");
    SequenceGenerator gen = KodoHelper.getSequenceGenerator (pm,
    Child.class);
    setObjId(new Long(gen.getNext().longValue()));
    child.jdo:
    <jdo>
    <package name="foo">
    <class name="Child" persistence-capable-superclass="foo.Parent"
    identity-type="application" objectid-class="Child$ID">
    <extension vendor-name="kodo" key="jdbc-class-map-name"
    value="vertical">
    <extension vendor-name="kodo" key="table" value="CHILD"/>
    <extension vendor-name="kodo" key="ref-column.OBJID"
    value="OBJID"/>
    </extension>
    <field name="attr2" persistence-modifier="persistent"/>
    </class>
    </package>
    </jdo>
    generated mappings by "mappingtool -a refresh":
    parent.mapping:
    <mapping>
    <package name="foo">
    <class name="Parent">
    <jdbc-class-map type="base" table="PARENT"/>
    <jdbc-version-ind type="version-number" column="JDOVERSION"/>
    <jdbc-class-ind type="in-class-name" column="JDOCLASS"/>
    <field name="ObjId">
    <jdbc-field-map type="value" column="OBJID"/>
    </field>
    <field name="attr1">
    <jdbc-field-map type="value" column="ATTR1"/>
    </field>
    </class>
    </package>
    </mapping>
    child.mapping:
    <mapping>
    <package name="foo">
    <class name="Child">
    <jdbc-class-map type="vertical" ref-column.OBJID="OBJID"
    table="CHILD"/>
    <field name="attr2">
    <jdbc-field-map type="value" column="ATTR2"/>
    </field>
    </class>
    </package>
    </mapping>

  • Validation in hierarchy table

    Hi Folks'
    i have two requirements:
    1)can i write a validation to meet the hierarchy value requirement? Under "SEVGVS" node there should not be any node with name"SEFLXXXXX".
    If not validation,then how to achieve this?
    2)Can we restrict the user from deleting a record depending on the value of a field? e.g: user x cannot be able to delete the record if the value of field ABC is y.
    Regards,
    Bis

    Hi Bis,
    Restricting a User from Deleting a record based on a Field value is not possible in MDM.
    As far as i know Record Operations like Adding ,Deleting,Modifying etc are specified for a User irrespective of any Field value.Based on his Role and Authorization he can either Delete all record or None records.
    A workaround could be :
    - Use a named Serach for records with Field Value = XYZ eg  that you do not want the user to delete.
    - As it is Named search every time the record has value XYZ in Field it will move to the created Named search
    - And then Constraint the specified user from deleting any records in that named search.
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Setid hierarchy

    Hi Folks,
    My requirement is to get an hierarchy from a setid.I need to display the balances against each company code and the output should look like this.
    Legal
       CA                          A           B             B-A   
          4001         $2000     $4000        $2000
          4002         $3000     $4000        $1000
          4003         $2000     $4000        $2000
         Subtotal                                    $5000 
       NE
          3500         $2000     $4000         $2000
          3501         $2000     $4000         $2000
         Subtotal                                     $4000 
    NY
           2500         $2000     $4000         $2000
         Subtotal                                     $2000 
    Total                                               $11000
    The values are taken from different tables.
    The hierarchy is from a setid (transaction code:GS03)
    This is an alv report i guess and there will be a drilldown option in the next stage.
    Please provide me any sample code if possible.
    Thanks and regards.

    this is hierarchy compare report...Change it according to ur requirement.
    REPORT  y_hierarchies_in_tables
            NO STANDARD PAGE HEADING.
    PARAMETER: g_group TYPE grpname.  " DEFAULT 'Z_GLAB0000'.
    DATA:
          g_setid TYPE setid,
          g_class TYPE setclass.
    DATA: lt_hier      TYPE STANDARD TABLE OF sethier,
          lt_val       TYPE STANDARD TABLE OF setvalues.
    DATA: hier    LIKE sethier   OCCURS 0 WITH HEADER LINE,
          val     LIKE setvalues OCCURS 0 WITH HEADER LINE,
          setinfo LIKE setinfo   OCCURS 0 WITH HEADER LINE.
    DATA: zaccbas(20) TYPE c OCCURS 0 WITH HEADER LINE.
    DATA: miss_val LIKE setvalues-from OCCURS 0 WITH HEADER LINE.
    DATA: table_name TYPE tabname,
          field_name TYPE setfld.
    DATA: ambiguity_flag TYPE c.
    Ambiguity check
    PERFORM ambiguity_check.
    Display Records
    PERFORM display_records.
    *&      Form  AMBIGUITY_CHECK
          Ambiguity check
    FORM ambiguity_check .
      DATA: it_abaplist LIKE abaplist OCCURS 0 WITH HEADER LINE.
      DATA: BEGIN OF it_ascilist OCCURS 0,
              zeile(256) TYPE c,
            END OF it_ascilist.
      DATA: flag.
      SUBMIT rgsovl00 "VIA SELECTION-SCREEN
             WITH p_shrtn = g_group
             WITH path    = 'X'
             EXPORTING LIST TO MEMORY
             AND RETURN.
      CALL FUNCTION 'LIST_FROM_MEMORY'
        TABLES
          listobject = it_abaplist
        EXCEPTIONS
          not_found  = 1
          OTHERS     = 2.
      CALL FUNCTION 'LIST_TO_ASCI'
        TABLES
          listasci                 = it_ascilist
          listobject               = it_abaplist
       EXCEPTIONS
         empty_list               = 1
         list_index_invalid       = 2
         OTHERS                   = 3 .
      LOOP AT it_ascilist.
        IF it_ascilist-zeile = text-001.
          flag = 'X'.
        ENDIF.
        IF flag = 'X' AND
           it_ascilist-zeile = text-002.
          ambiguity_flag = 'X'.
          CLEAR flag.
        ENDIF.
      ENDLOOP.
      FREE MEMORY.
    ENDFORM.                    " AMBIGUITY_CHECK
    *&      Form  DISPLAY_RECORDS
          Display the Records
    FORM display_records .
      PERFORM get_records.
      PERFORM header_data.
      PERFORM item_data.
    ENDFORM.                    " DISPLAY_RECORDS
    *&      Form  GET_RECORDS
          Get all the Node values
    FORM get_records .
    Get the ID name for the Hierarchy
      CALL FUNCTION 'G_SET_GET_ID_FROM_NAME'
        EXPORTING
          shortname = g_group
          setclass  = g_class
          old_setid = g_setid
        IMPORTING
          new_setid = g_setid.
    Get the Table and Field name for the Top Node
      CALL FUNCTION 'G_SET_GET_INFO'
        EXPORTING
          setname          = g_setid
          no_set_title     = 'X'
          use_table_buffer = 'X'
        IMPORTING
          info             = setinfo.
      table_name = setinfo-tabname.
      field_name = setinfo-fld.
    Get all the Nodes for the Hierarchy
      CALL FUNCTION 'G_SET_TREE_IMPORT'
        EXPORTING
          no_descriptions = ' '
          no_rw_info      = 'X'
          setid           = g_setid
        TABLES
          set_hierarchy   = lt_hier
          set_values      = lt_val.
      hier[] = lt_hier.
      val[]  = lt_val.
      SELECT (field_name) FROM (table_name) INTO TABLE zaccbas.
      LOOP AT zaccbas.
        READ TABLE val WITH KEY FROM = zaccbas.
        IF sy-subrc = 0.
          DELETE zaccbas.
          CLEAR  zaccbas.
          DELETE val INDEX sy-tabix.
          CLEAR  val.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " GET_RECORDS
    *&      Form  HEADER_DATA
          Header Data
    FORM header_data .
      DATA: desc TYPE settext.
      READ TABLE hier WITH KEY fieldname = field_name
                               shortname  = g_group.
      IF sy-subrc = 0.
        desc =  hier-descript.
      ENDIF.
      SKIP.
      WRITE: 'Node        :',g_group.
      WRITE:75 'User name  :', sy-uname.
      WRITE:/ 'Description :', desc.
      WRITE:75 'Date:', sy-datum.
      WRITE:/ 'Table Name  :' , table_name.
      WRITE:75 'Time:', sy-timlo.
      WRITE:/ 'Field Name  :', field_name.
      write:75 'Client:', SY-MANDT.
      skip.
      IF ambiguity_flag = 'X'.
        WRITE:/ 'Ambiguity Check :'. WRITE: 'Success' COLOR 5.
      ELSE.
        WRITE:/ 'Ambiguity Check :'. WRITE: 'Failed' COLOR 6 .
      ENDIF.
      WRITE:/ sy-uline.
      WRITE:/37 'Validation for Hierarchy'.
      WRITE:/ sy-uline.
    ENDFORM.                    " HEADER_DATA
    *&      Form  ITEM_DATA
          Output Report for Nodes
    FORM item_data .
      IF NOT zaccbas[]  IS INITIAL.
        WRITE:/ 'Missing Records from Hierarchy' COLOR 3.
        LOOP AT zaccbas.
          WRITE:/ zaccbas.
        ENDLOOP.
      ENDIF.
      IF NOT val[] IS INITIAL.
        SKIP 1.
        WRITE:/ 'Additional Records in Hierarchy' COLOR 3.
        LOOP AT val.
          WRITE:/ val-from.  ", 28 val-DESCRIPT.
        ENDLOOP.
      ELSEIF ZACCBAS[] IS INITIAL.
        WRITE:/ 'No Missing Records Found' COLOR 3.
      ENDIF.
    ENDFORM.                    " ITEM_DATA

  • Edit table dialog with inherited privileges

    Hi all,
    Our users had a problem that they are not able to edit table definitions with the dialog (edit option doesn't appear in context menu), although they are able to execute ALTER TABLE statements. This problem occured both in 1.5.5 and 2.1 versions (I'm not sure about older versions).
    I found that the problem is in inherited privileges: CREATE ANY TABLE is granted to top-level role and that role is granted to second role. Top-level role is never granted directly to users. I studied the SQL generated by SQL Developer, and found the query used to determine if user can edit a table:
    SELECT SUM(cnt) privs
    FROM
    (SELECT COUNT(*) cnt
    FROM user_tab_privs
    WHERE owner = :OWNER
    AND table_name = :NAME
    AND privilege = 'ALTER'
    UNION ALL
    SELECT COUNT(*) FROM user_sys_privs WHERE privilege = 'ALTER ANY TABLE'
    UNION ALL
    SELECT COUNT(*)
    FROM all_tab_privs
    WHERE GRANTOR = :OWNER
    AND table_name = :NAME
    AND privilege = 'ALTER'
    AND grantee = 'PUBLIC'
    UNION ALL
    SELECT COUNT(*)
    FROM
    (SELECT privilege
    FROM role_sys_privs
    WHERE role IN
    (SELECT granted_role FROM user_role_privs
    WHERE privilege = 'ALTER ANY TABLE'
    If you look at the last part, it's clear it doesn't handle cases when 'ALTER ANY TABLE' is inherited from a role hierarchy. If I grant the role directly to user, the problem disappears but I would not want to alter our role conventions this way.
    I wonder if others have noticed this also? Is there some reason why the query is written this way?

    I found the guilty statement in \sqldeveloper\extensions\oracle.sqldeveloper.jar\oracle\dbtools\util\objectpriv\source.xml. As workaround you could edit and fix it yourself.
    Have fun,
    K.
    PS: changing any code is of course NOT SUPPORTED by Oracle.

  • Adapter Engine / Integration Server Problem

    Hi,
    I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
    Problem:
    In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
    What I've done & Observations:
    1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
    2. SLDCHECK reveals that the connection to SLD is successful.
    3. RWB component monitoring shows:
        Integration Server - No light (Node cannot be expanded)
        Integration Engines - No light (Node cannot be expanded)
        Non-Central Adapter Engines -
            Adapter Engine ootspdbs02 (Red Light)
              - Self Test Failed - Details: Client 010 is not available in this system.
              - Cache Connectivity Test:
                Attempt to fetch cache data from Integration Directory failed; cache could not be updated
                [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
        J2SE Adapter - No light (Node cannot be expanded)
        Tools
            - System Landscape Directory ootspdbs02 (Green Light)
            - Integration Directory ootspdbs02 (Green Light)
            - Integration Repository ootspdbs02 (Green Light)
            - Runtime Workbench ootspdbs02 (Green Light)
    4. In my SLD - I've defined a business system PI_BS_01
        Role: Integration Server
        Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
        Group - No Group Assigned.
        Client: 001 of PI1
        Technical System: PI1 on ootspdbs02 - Release 700
    Given the above observations, can anyone please point out to me where I went wrong?
    Any advise is greatly appreciated.
    Thank you.
    Best Regards,
    Ron Lai

    Hi Archana,
    The configuration in SLD DataSupplier is:
    Latest Send Activity               
         2007/01/04  09:18:09:564
    Used HTTP Parameters [http host:port] [user] [protocol]     
         [ootspdbs02:50100] [SLDDSUSER] [http]
    Sending Node [nodeID] [hostname]     
         [11621750] [ootspdbs02]
    Send Result     
         Success
    Next Automatic Send Timestamp     
         2007/01/04  21:18:08:189
    Send Type
         Automatic (Time Scheduled)
    Configuration Status     
         Valid
    The hierarchy of this business system is:
    Business System:
       BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
    Technical System:
       TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
    Basically I created product, software component, technical system, business system from scratch.
    I did not put any dependencies to existing products/software components.
    Regards,
    Ron

  • Appset not appearing after import

    Hi Friends,
    We are on bpc75nw sp04.
    Custom appset(A) is correctly imported into target system. I'm able to see in backend(BW), but in fron-end(BPC admin/BPC excel) not appearing. Could any one suggest, what might be reason? How to know install user id of BPC system?
    Basis consultant, tried with different user ids like install user, & other users, but he couldn't see at server level as well client level.
    I checked uje_user table, it shows appset(A) avialable to  USER1.
    I hope with USER1 id only, we are able to see appset (A).
    Regards,
    Naresh

    Log:  import ended with warning.
       Start of the after-import method RS_APPS_AFTER_IMPORT for object type(s) APPS (Activation Mode)
       Start After Import for AppSet XXXX in Client 500 for RFC MDX PARSER
       Import Step UPDPTAB completed without errors
       Import Step ADMIN_DEF_UPD completed without errors
       Import Step APPS_ADD completed without errors
       After Import method for AppSet XXXX finished successfully
       Start of data checker messages
       The file service structure is correct.
    Dimension ACCOUNT's master is empty!
    Dimension ACCT's master is empty!
    Dimension CATEGORY's master is empty!
    Dimension CHANNEL's master is empty!
    Dimension COST_COMP's master is empty!
    Dimension C_ACCT's master is empty!
    Dimension C_CATEGORY's master is empty!
    Dimension TIME's master is empty!
       BPF: Validation error; No template access is defined for template "Sales Flow"
       BPF: Validation error; member item "REGION 2" is not in drive dimension "LOCATION"
       BPF: Validation error; hierarchy "PARENTH1" is not in drive dimension "LOCATION"
       BPF: Validation error; member item "REGION 1" is not in drive dimension "LOCATION"
       BPF: Validation error; hierarchy "PARENTH1" is not in drive dimension "LOCATION"
       BPF: Validation error; member item "REGION 2" is not in drive dimension "LOCATION"
       BPF: Validation error; hierarchy "PARENTH1" is not in drive dimension "LOCATION"
       BPF: Validation error; member item "REGION 1" is not in drive dimension "LOCATION"
       BPF: Validation error; hierarchy "PARENTH1" is not in drive dimension "LOCATION"
       BPF: Validation error; member item "INDIA" is not in drive dimension "LOCATION"
       BPF: Validation error; No template access is defined for template "SALES_PLANNING FLOW"
    End of data checker messages
       End of after import methode RS_APPS_AFTER_IMPORT (Activation Mode) - runtime: 00:19:35
       Start of the after-import method RS_APPS_AFTER_IMPORT for object type(s) APPS (Delete Mode)
       Nothing to delete.
       End of after import methode RS_APPS_AFTER_IMPORT (Delete Mode) - runtime: 00:00:00
       Post-import method RS_AFTER_IMPORT completed for APPS L, date and time: 20110207110512
       Post-import methods of change/transport request BQ1K900069 completed
            Start of subsequent processing ... 20110207104537
            End of subsequent processing... 20110207110512
       Execute reports for change/transport request: BQ1K900069
          on the application server: sparbdb
        Ended with return code:  ===> 4 <===

  • Tree structure in f4 help

    Hi experts,
    can any one give me sample code for providing tree structure in f4help.  like object part field have in iw21 transaction
    Regards
    reddy

    Hi Muttukundu,
    SAP has provided a lot of sample programs for developing tree structures. Just go to SE38, type BCALVTREE and hit F4. You'll get different sample programs with a range of operations on trees
    Go through the link,
    http://www.sapdevelopment.co.uk/reporting/alv/alvtree.htm
    Slowly check this code..you will get idea of how to develop tree structure.
    REPORT y_hierarchies_in_tables
    NO STANDARD PAGE HEADING.
    PARAMETER: g_group TYPE grpname. " DEFAULT 'Z_GLAB0000'.
    DATA:
    g_setid TYPE setid,
    g_class TYPE setclass.
    DATA: lt_hier TYPE STANDARD TABLE OF sethier,
    lt_val TYPE STANDARD TABLE OF setvalues.
    DATA: hier LIKE sethier OCCURS 0 WITH HEADER LINE,
    val LIKE setvalues OCCURS 0 WITH HEADER LINE,
    setinfo LIKE setinfo OCCURS 0 WITH HEADER LINE.
    DATA: zaccbas(20) TYPE c OCCURS 0 WITH HEADER LINE.
    DATA: miss_val LIKE setvalues-from OCCURS 0 WITH HEADER LINE.
    DATA: table_name TYPE tabname,
    field_name TYPE setfld.
    DATA: ambiguity_flag TYPE c.
    Ambiguity check
    PERFORM ambiguity_check.
    Display Records
    PERFORM display_records.
    *& Form AMBIGUITY_CHECK
    Ambiguity check
    FORM ambiguity_check .
    DATA: it_abaplist LIKE abaplist OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF it_ascilist OCCURS 0,
    zeile(256) TYPE c,
    END OF it_ascilist.
    DATA: flag.
    SUBMIT rgsovl00 "VIA SELECTION-SCREEN
    WITH p_shrtn = g_group
    WITH path = 'X'
    EXPORTING LIST TO MEMORY
    AND RETURN.
    CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
    listobject = it_abaplist
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CALL FUNCTION 'LIST_TO_ASCI'
    TABLES
    listasci = it_ascilist
    listobject = it_abaplist
    EXCEPTIONS
    empty_list = 1
    list_index_invalid = 2
    OTHERS = 3 .
    LOOP AT it_ascilist.
    IF it_ascilist-zeile = text-001.
    flag = 'X'.
    ENDIF.
    IF flag = 'X' AND
    it_ascilist-zeile = text-002.
    ambiguity_flag = 'X'.
    CLEAR flag.
    ENDIF.
    ENDLOOP.
    FREE MEMORY.
    ENDFORM. " AMBIGUITY_CHECK
    *& Form DISPLAY_RECORDS
    Display the Records
    FORM display_records .
    PERFORM get_records.
    PERFORM header_data.
    PERFORM item_data.
    ENDFORM. " DISPLAY_RECORDS
    *& Form GET_RECORDS
    Get all the Node values
    FORM get_records .
    Get the ID name for the Hierarchy
    CALL FUNCTION 'G_SET_GET_ID_FROM_NAME'
    EXPORTING
    shortname = g_group
    setclass = g_class
    old_setid = g_setid
    IMPORTING
    new_setid = g_setid.
    Get the Table and Field name for the Top Node
    CALL FUNCTION 'G_SET_GET_INFO'
    EXPORTING
    setname = g_setid
    no_set_title = 'X'
    use_table_buffer = 'X'
    IMPORTING
    info = setinfo.
    table_name = setinfo-tabname.
    field_name = setinfo-fld.
    Get all the Nodes for the Hierarchy
    CALL FUNCTION 'G_SET_TREE_IMPORT'
    EXPORTING
    no_descriptions = ' '
    no_rw_info = 'X'
    setid = g_setid
    TABLES
    set_hierarchy = lt_hier
    set_values = lt_val.
    hier[] = lt_hier.
    val[] = lt_val.
    SELECT (field_name) FROM (table_name) INTO TABLE zaccbas.
    LOOP AT zaccbas.
    READ TABLE val WITH KEY FROM = zaccbas.
    IF sy-subrc = 0.
    DELETE zaccbas.
    CLEAR zaccbas.
    DELETE val INDEX sy-tabix.
    CLEAR val.
    ENDIF.
    ENDLOOP.
    ENDFORM. " GET_RECORDS
    *& Form HEADER_DATA
    Header Data
    FORM header_data .
    DATA: desc TYPE settext.
    READ TABLE hier WITH KEY fieldname = field_name
    shortname = g_group.
    IF sy-subrc = 0.
    desc = hier-descript.
    ENDIF.
    SKIP.
    WRITE: 'Node :',g_group.
    WRITE:75 'User name :', sy-uname.
    WRITE:/ 'Description :', desc.
    WRITE:75 'Date:', sy-datum.
    WRITE:/ 'Table Name :' , table_name.
    WRITE:75 'Time:', sy-timlo.
    WRITE:/ 'Field Name :', field_name.
    write:75 'Client:', SY-MANDT.
    skip.
    IF ambiguity_flag = 'X'.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Success' COLOR 5.
    ELSE.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Failed' COLOR 6 .
    ENDIF.
    WRITE:/ sy-uline.
    WRITE:/37 'Validation for Hierarchy'.
    WRITE:/ sy-uline.
    ENDFORM. " HEADER_DATA
    *& Form ITEM_DATA
    Output Report for Nodes
    FORM item_data .
    IF NOT zaccbas[] IS INITIAL.
    WRITE:/ 'Missing Records from Hierarchy' COLOR 3.
    LOOP AT zaccbas.
    WRITE:/ zaccbas.
    ENDLOOP.
    ENDIF.
    IF NOT val[] IS INITIAL.
    SKIP 1.
    WRITE:/ 'Additional Records in Hierarchy' COLOR 3.
    LOOP AT val.
    WRITE:/ val-from. ", 28 val-DESCRIPT.
    ENDLOOP.
    ELSEIF ZACCBAS[] IS INITIAL.
    WRITE:/ 'No Missing Records Found' COLOR 3.
    ENDIF.
    ENDFORM. " ITEM_DATA
    Reward if found helpfull,
    Cheers,
    Chaitanya.

  • TREE NODE IN F4 SEARCH HELP

    Hi All,
    Can anyone help me to implement Tree node in F4 Search help?
    Thanks
    E Karthikeyan

    SAP has provided a lot of sample programs for developing tree structures. Just go to SE38, type BCALVTREE and hit F4. You'll get different sample programs with a range of operations on trees
    Go through the link,
    http://www.sapdevelopment.co.uk/reporting/alv/alvtree.htm
    Slowly check this code..you will get idea of how to develop tree structure.
    REPORT y_hierarchies_in_tables
    NO STANDARD PAGE HEADING.
    PARAMETER: g_group TYPE grpname. " DEFAULT 'Z_GLAB0000'.
    DATA:
    g_setid TYPE setid,
    g_class TYPE setclass.
    DATA: lt_hier TYPE STANDARD TABLE OF sethier,
    lt_val TYPE STANDARD TABLE OF setvalues.
    DATA: hier LIKE sethier OCCURS 0 WITH HEADER LINE,
    val LIKE setvalues OCCURS 0 WITH HEADER LINE,
    setinfo LIKE setinfo OCCURS 0 WITH HEADER LINE.
    DATA: zaccbas(20) TYPE c OCCURS 0 WITH HEADER LINE.
    DATA: miss_val LIKE setvalues-from OCCURS 0 WITH HEADER LINE.
    DATA: table_name TYPE tabname,
    field_name TYPE setfld.
    DATA: ambiguity_flag TYPE c.
    Ambiguity check
    PERFORM ambiguity_check.
    Display Records
    PERFORM display_records.
    *& Form AMBIGUITY_CHECK
    Ambiguity check
    FORM ambiguity_check .
    DATA: it_abaplist LIKE abaplist OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF it_ascilist OCCURS 0,
    zeile(256) TYPE c,
    END OF it_ascilist.
    DATA: flag.
    SUBMIT rgsovl00 "VIA SELECTION-SCREEN
    WITH p_shrtn = g_group
    WITH path = 'X'
    EXPORTING LIST TO MEMORY
    AND RETURN.
    CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
    listobject = it_abaplist
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CALL FUNCTION 'LIST_TO_ASCI'
    TABLES
    listasci = it_ascilist
    listobject = it_abaplist
    EXCEPTIONS
    empty_list = 1
    list_index_invalid = 2
    OTHERS = 3 .
    LOOP AT it_ascilist.
    IF it_ascilist-zeile = text-001.
    flag = 'X'.
    ENDIF.
    IF flag = 'X' AND
    it_ascilist-zeile = text-002.
    ambiguity_flag = 'X'.
    CLEAR flag.
    ENDIF.
    ENDLOOP.
    FREE MEMORY.
    ENDFORM. " AMBIGUITY_CHECK
    *& Form DISPLAY_RECORDS
    Display the Records
    FORM display_records .
    PERFORM get_records.
    PERFORM header_data.
    PERFORM item_data.
    ENDFORM. " DISPLAY_RECORDS
    *& Form GET_RECORDS
    Get all the Node values
    FORM get_records .
    Get the ID name for the Hierarchy
    CALL FUNCTION 'G_SET_GET_ID_FROM_NAME'
    EXPORTING
    shortname = g_group
    setclass = g_class
    old_setid = g_setid
    IMPORTING
    new_setid = g_setid.
    Get the Table and Field name for the Top Node
    CALL FUNCTION 'G_SET_GET_INFO'
    EXPORTING
    setname = g_setid
    no_set_title = 'X'
    use_table_buffer = 'X'
    IMPORTING
    info = setinfo.
    table_name = setinfo-tabname.
    field_name = setinfo-fld.
    Get all the Nodes for the Hierarchy
    CALL FUNCTION 'G_SET_TREE_IMPORT'
    EXPORTING
    no_descriptions = ' '
    no_rw_info = 'X'
    setid = g_setid
    TABLES
    set_hierarchy = lt_hier
    set_values = lt_val.
    hier[] = lt_hier.
    val[] = lt_val.
    SELECT (field_name) FROM (table_name) INTO TABLE zaccbas.
    LOOP AT zaccbas.
    READ TABLE val WITH KEY FROM = zaccbas.
    IF sy-subrc = 0.
    DELETE zaccbas.
    CLEAR zaccbas.
    DELETE val INDEX sy-tabix.
    CLEAR val.
    ENDIF.
    ENDLOOP.
    ENDFORM. " GET_RECORDS
    *& Form HEADER_DATA
    Header Data
    FORM header_data .
    DATA: desc TYPE settext.
    READ TABLE hier WITH KEY fieldname = field_name
    shortname = g_group.
    IF sy-subrc = 0.
    desc = hier-descript.
    ENDIF.
    SKIP.
    WRITE: 'Node :',g_group.
    WRITE:75 'User name :', sy-uname.
    WRITE:/ 'Description :', desc.
    WRITE:75 'Date:', sy-datum.
    WRITE:/ 'Table Name :' , table_name.
    WRITE:75 'Time:', sy-timlo.
    WRITE:/ 'Field Name :', field_name.
    write:75 'Client:', SY-MANDT.
    skip.
    IF ambiguity_flag = 'X'.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Success' COLOR 5.
    ELSE.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Failed' COLOR 6 .
    ENDIF.
    WRITE:/ sy-uline.
    WRITE:/37 'Validation for Hierarchy'.
    WRITE:/ sy-uline.
    ENDFORM. " HEADER_DATA
    *& Form ITEM_DATA
    Output Report for Nodes
    FORM item_data .
    IF NOT zaccbas[] IS INITIAL.
    WRITE:/ 'Missing Records from Hierarchy' COLOR 3.
    LOOP AT zaccbas.
    WRITE:/ zaccbas.
    ENDLOOP.
    ENDIF.
    IF NOT val[] IS INITIAL.
    SKIP 1.
    WRITE:/ 'Additional Records in Hierarchy' COLOR 3.
    LOOP AT val.
    WRITE:/ val-from. ", 28 val-DESCRIPT.
    ENDLOOP.
    ELSEIF ZACCBAS[] IS INITIAL.
    WRITE:/ 'No Missing Records Found' COLOR 3.
    ENDIF.
    ENDFORM. " ITEM_DATA
    Thanks,
    Sakthi C
    *Rewards if useful*

  • BIB-9509

    I´m trying to create a crostab with one fact and 6 dimensions. i[m using Jdeveloper 9.0.3.10.90 and Oracle9i Enterprise Edition Release 9.2.0.4.0.
    In Query builder in the dimensions tab, when i select one of my dimensions, just that one, i cant pass the members of that dimensions and the wizard ends with the next error:
    BIB-9509 Oracle OLAP no ha creado el cursor.
    class: OLAPI
    Server error descriptions:
    DPR: No se ha podido crear el cursor del servidor, Genérico at TxsOqDefinitionManagerSince9202::crtCurMgrWthInputTypes
    OES: ORA-01722: invalid number
    Genérico at TxsRdbSelectStatement:execute()
    can anyone help me?
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    I found this script in metalink
    set echo on
    set linesize 135
    set pagesize 50
    set serverout on size 100000
    exec cwm2_olap_manager.set_echo_on;
    spool D:\jos\Pemex\Inconformidades\validate.log
    exec cwm2_olap_validate.validate_all_cubes('OLAP API');
    PROMPT exec cwm2_olap_validate.validate_all_dimensions('OLAP API');
    execute cwm2_olap_manager.End_Log;
    execute cwm2_olap_manager.Set_Echo_Off;
    spool off
    and the output for this script is:
    SQL> PROMPT exec cwm2_olap_validate.validate_all_cubes('OLAP API');
    exec cwm2_olap_validate.validate_all_cubes('OLAP API')
    SQL> exec cwm2_olap_validate.validate_all_dimensions('OLAP API');
    .Validate All Dimensions
    .Validate Dimension: DMCGC0.D_ACTUACION_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_ACTUACION_I_DIM VALID Default Display Hierarchy: "H_ACTUACION".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . Hierarchy H_ACTUACION VALID
    . Level L_ACTUACION VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_ACTUACION_I
    - .A_ID_ACTUACION".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_ACTUACION_I
    - .A_DESC_ACTUACION".
    .Validate Dimension: DMCGC0.D_AREA_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_AREA_I_DIM VALID Default Display Hierarchy: "H_AREA".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_AREA VALID
    . Level UNIDAD VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREA_I.UC_ID_UNIDAD".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I
    - .UC_DESC_UNIDAD_COMP".
    . Level GERENCIA VALID Hierarchy Depth: 2.
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREA_I.G_ID_GERENCIA".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I.G_DESC_GERENCIA".
    . Level SUBDIR VALID Hierarchy Depth: 3.
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREA_I
    - .SD_ID_SUBDIRECCION".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I
    - .SD_DESC_SUBDIRECCI".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I
    - .SD_CVE_SUBDIRECCION".
    . Level DIRECCION VALID Hierarchy Depth: 4.
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREA_I.D_ID_DIRECCION".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I.D_DESC_DIRECCION".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I.D_CVE_DIRECCION".
    . Level ORGANISMO VALID Hierarchy Depth: 5 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREA_I.O_ID_ORGANISMO".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I.O_DESC_ORGANISMO".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREA_I.O_CVE_ORGANISMO".
    .Validate Dimension: DMCGC0.D_AREAS_TURNADAS_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_AREAS_TURNADAS_I_DIM VALID Default Display Hierarchy: "H_AREA_TURNADA".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_AREA_TURNADA VALID
    . Level L_AREA_TURNADA VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .AT_ID_AREA_TURNADA".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .AT_DESC_AREA_TURNA".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .AT_CVE_AREA_TURNADA".
    . Level L_ORGANISMO VALID Hierarchy Depth: 2 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .O_ID_ORGANISMO".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .O_DESC_ORGANISMO".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_AREAS_TURNADAS_I
    - .O_CVE_ORGANISMO".
    .Validate Dimension: DMCGC0.D_CABECERO_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_CABECERO_I_DIM VALID Default Display Hierarchy: "H_CABECERO".
    . DimensionAttribute CONCLUIDOS VALID
    . DimensionAttribute EN PROCESO VALID
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SUBTOTAL VALID
    . DimensionAttribute TRIMESTRE ACTUAL VALID
    . DimensionAttribute TRIMESTRE ANTERIOR VALID
    . Hierarchy H_CABECERO VALID
    . Level L_CABECERO VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_CABECERO_I
    - .C_ID_CABECERO".
    . LevelAttribute CONCLUIDOS VALID DimensionAttribute: "CONCLUIDOS".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I.C_CONCLUIDOS".
    . LevelAttribute EN PROCESO VALID DimensionAttribute: "EN PROCESO".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I.C_EN_PROCESO".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I
    - .C_DESCRIPCION".
    . LevelAttribute SUBTOTAL VALID DimensionAttribute: "SUBTOTAL".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I.C_SUBTOTAL".
    . LevelAttribute TRIMESTRE ACTUAL VALID DimensionAttribute: "TRIMESTRE ACTUAL".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I
    - .C_TRIMESTRE_ACTUAL".
    . LevelAttribute TRIMESTRE ANTERIOR VALID DimensionAttribute: "TRIMESTRE ANTERIOR".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_CABECERO_I
    - .C_TRIMESTRE_ANTERIOR".
    .Validate Dimension: DMCGC0.D_EVENTO_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_EVENTO_I_DIM VALID Default Display Hierarchy: "H_EVENTO".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_EVENTO VALID
    . Level L_EVENTO VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_EVENTO_I.E_ID_EVENTO".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_EVENTO_I.E_DESC_EVENTO".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_EVENTO_I.E_CVE_EVENTO".
    .Validate Dimension: DMCGC0.D_INCONFORME_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_INCONFORME_I_DIM VALID Default Display Hierarchy: "H_INCONFORME".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . Hierarchy H_INCONFORME VALID
    . Level L_INCONFORME VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_INCONFORME_I
    - .I_ID_INCONF".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_INCONFORME_I
    - .I_DESC_INCONF".
    .Validate Dimension: DMCGC0.D_PROVEEDOR_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_PROVEEDOR_I_DIM VALID Default Display Hierarchy: "H_PROVEEDOR".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . Hierarchy H_PROVEEDOR VALID
    . Level L_PROVEEDOR VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_PROVEEDOR_I
    - .P_ID_PROVEEDOR".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_PROVEEDOR_I
    - .P_DESC_PROVEEDOR".
    .Validate Dimension: DMCGC0.D_TIEMPO_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIEMPO_DIM VALID Dimension Type: "Time".
    - Default Display Hierarchy: "TIME_HIER".
    . DimensionAttribute END DATE VALID DimensionAttribute Type: "End Date".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute TIME SPAN VALID DimensionAttribute Type: "Time Span".
    . Hierarchy TIME_HIER VALID
    . Level TIME_DATE VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.F_ID_FECHA".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.F_FIN_FECHA".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.F_DESC_FECHA".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.F_DURACION_FECHA".
    . Level TIME_DAY VALID Hierarchy Depth: 2.
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.D_ID_DIA".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.D_FIN_DIA".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.D_DESC_DIA".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.D_DURACION_DIA".
    . Level TIME_MON VALID Hierarchy Depth: 3.
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.X_ID_MES".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.X_FIN_MES".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.X_DESC_MES".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.X_DURACION_MES".
    . Level TIME_QTR VALID Hierarchy Depth: 4.
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.T_ID_TRIM".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.T_FIN_TRIM".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.T_DESC_TRIM".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.T_DURACION_TRIM".
    . Level TIME_SEM VALID Hierarchy Depth: 5.
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.S_ID_SEM".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.S_FIN_SEM".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.S_DESC_SEM".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.S_DURACION_SEM".
    . Level TIME_YEAR VALID Hierarchy Depth: 6 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIEMPO.A_ID_ANIO".
    . LevelAttribute END DATE VALID DimensionAttribute: "END DATE".
    - LevelAttribute Type: "End Date".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.A_FIN_ANIO".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.A_DESC_ANIO".
    . LevelAttribute TIME SPAN VALID DimensionAttribute: "TIME SPAN".
    - LevelAttribute Type: "Time Span".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIEMPO.A_DURACION_ANIO".
    .Validate Dimension: DMCGC0.D_TIPO_CONTRAT_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIPO_CONTRAT_I_DIM VALID Default Display Hierarchy: "H_TIPO_CONTRAT".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_TIPO_CONTRAT VALID
    . Level L_TIPO_CONTRAT VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_CONTRAT_I
    - .TP_ID_TIPO_CONTRAT".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_CONTRAT_I
    - .TP_DESC_TIPO_CONTR".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_CONTRAT_I
    - .TP_CVE_TIPO_CONTRAT".
    . Level L_TIPO_LEY VALID Hierarchy Depth: 2 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_CONTRAT_I
    - .TL_ID_TIPO_LEY".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_CONTRAT_I
    - .TL_DESC_TIPO_LEY".
    .Validate Dimension: DMCGC0.D_TIPO_LEY_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIPO_LEY_I_DIM VALID Default Display Hierarchy: "H_TIPO_LEY".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . Hierarchy H_TIPO_LEY VALID
    . Level L_TIPO_LEY VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_LEY_I
    - .TL_ID_TIPO_LEY".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_LEY_I
    - .TL_DESC_TIPO_LEY".
    .Validate Dimension: DMCGC0.D_TIPO_PROC_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:10 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIPO_PROC_I_DIM VALID Default Display Hierarchy: "H_TIPO_PROC".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_TIPO_PROC VALID
    . Level L_TIPO_PROC VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_PROC_I
    - .TP_ID_TIPO_PROC".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_PROC_I
    - .TP_DESC_TIPO_PROC".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_PROC_I
    - .TP_CVE_TIPO_PROC".
    .Validate Dimension: DMCGC0.D_TIPO_RESOL_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:11 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIPO_RESOL_I_DIM VALID Default Display Hierarchy: "H_TIPO_RESOL".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . DimensionAttribute SHORT DESCRIPTION VALID DimensionAttribute Type: "Short Description".
    . Hierarchy H_TIPO_RESOL VALID
    . Level L_RESOLUCION VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_ID_RESOL".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_DESC_RESOL".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_CVE_RESOL".
    . Level L_TIPO_RESOL VALID Hierarchy Depth: 2 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_ID_TIPO_RESOL".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_DESC_TIPO_RESOL".
    . LevelAttribute SHORT DESCRIPTION VALID DimensionAttribute: "SHORT DESCRIPTION".
    - LevelAttribute Type: "Short Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_I
    - .TR_CVE_TIPO_RESOL".
    .Validate Dimension: DMCGC0.D_TIPO_RESOL_IMPUG_I_DIM Type of Validation: OLAP API Verbose Report: YES
    .Validating Dimension Metadata in OLAP Catalog 2 Date: 2004 JUNIO 08 Time: 10:55:11 User: DMCGC0 030715
    .ENTITY TYPE ENTITY NAME STATUS COMMENT
    . Dimension DMCGC0.D_TIPO_RESOL_IMPUG_I_DIM VALID Default Display Hierarchy: "H_TIPO_RESOL_IMPUG".
    . DimensionAttribute LONG DESCRIPTION VALID DimensionAttribute Type: "Long Description".
    . Hierarchy H_TIPO_RESOL_IMPUG VALID
    . Level L_RESOLUCION_IMPUG VALID Hierarchy Depth: 1 (Lowest Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_IMPUG_I
    - .RI_ID_RESOL_IMPUG".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_IMPUG_I
    - .RI_DESC_RESOL_IMPUG".
    . Level L_TIPO_RESOL_IMPUG VALID Hierarchy Depth: 2 (Top Level).
    . LevelMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_IMPUG_I
    - .TRI_ID_TIPO_RESOL_IMPUG".
    . LevelAttribute LONG DESCRIPTION VALID DimensionAttribute: "LONG DESCRIPTION".
    - LevelAttribute Type: "Long Description".
    . LevelAttributeMap VALID Mapped Column: "DMCGC0.D_TIPO_RESOL_IMPUG_I
    - .TRI_DESC_TIPO_RESOL".
    PL/SQL procedure successfully completed.
    SQL> execute cwm2_olap_manager.End_Log;
    PL/SQL procedure successfully completed.
    SQL> execute cwm2_olap_manager.Set_Echo_Off;
    PL/SQL procedure successfully completed.
    SQL> spool off

  • Questions about trees

    There will be several different trees in an application I will begin developing shortly and I want to understand, if the tree of HTML_DB helps or not. And any help on how I could implement those trees otherwise would be also of help.
    1) Is it possible to make a tree out of different tables? * For one there are main services, that may contain several subservices, which of themselves can be part of any number of main services. So the mapping of subservisces to main services is done in a separate table (not by having the table refer to itself), but the client wants to see them compactly in one tree (so that every main service has its subservices below it, the subservice ight be in a tree more than once).
    * Another problem is that there is a view, where all of the jobs for one main service are shown and there has to be several jobs to be done for each subservice. It would be convenient to show those jobs in a tree as leafs of subservices, so its always seen, which service is completed by a job; you can collapse the services you dont want to see, etc...
    2) Is it possible to expand dynamically one or more 'folders' in a tree, when I link to a page? Sometimes when user goes to tree page, it is already known, where his target node might belong into, so it would be easier for the user to see that category already opened.
    it seems to be all for now, but I am sure, there will be more.

    hi kaja--
    1) so long as you can write view of your services and subservices that has a valid recursive hierarchy in it, you should be fine to base your tree off of that view.
    2) you might already know this, but it's a pretty simple matter to have your tree start from a dynamically set TREE_ROOT value. so you could pretty easily set that root to be whatever category you need. if you want to show a category expanded but not as the root of your tree, i've this semi-hack: if you expand and contract the nodes of any tree in HTML DB, you'll see that fourth value being passed through in the URL is our :REQUEST value (you can read up on our URL syntax in our online doc if you'd like, at http://htmldb.oracle.com/i/doc/mvl_fund005.htm#sthref445 ). anyhow, you can set that value manually (again via the URL, for example) in those cases where you know you want to a specific category to already be opened.
    hope this helps,
    raj

  • Monitoring tool for performance focused for Ebusiness.

    Hi partners,
    We are going to evaluate some "monitoring" performance tools for an Ebusiness environment, so I would like to know if you can give any recommendations about any tool focused for Ebusiness environment.
    Any advice will be really appreciated.
    Thanks in advance.
    Francisco Mtz.

    &#20108;&#12289;     The following includes SGAgent for Oracle E-Business Suite Enterprise Edition monitor KPIs click here &#12290;
    1.     SGAgent can monitor all KPIs those Oracle standard edition includes&#65307;
    2.     SGAgent can monitor more Oracle Instances &#12289;more type database(Like DB2 MS SQL Server Sybase)&#12289;more Oracle E-Business Suite Instances at the same time and the same screen&#65307;
    3.     Oracle EBS Patch Monitor&#65288;KPI&#65306;Username&#12289;Patch Name&#12289;Patch type&#12289;language&#12289;Patch created date&#12289;last updated date&#65289;&#65307;
    4.     Oracle EBS Profile Parameters monitor&#65288;KPI&#65306;Application username who updated the profile last&#12289;Last updated date&#12289;Application name&#12289;Profile Parameter name&#12289;Profile Parameter description&#12289;Language&#12289;Profile Value&#12289;Level ID&#12289;SQL Validation&#12289;Hierarchy type&#12289;Write allowed flag&#12289;Read allowed flag&#12289;last update by userid&#65289;&#65307;
    5.     Oracle EBS Application users login monitor&#65288;KPI&#65306;Login ID&#12289;Oracle application login username&#12289;Login user description&#12289;Application users email address&#12289;Login start time&#12289;Login End time&#12289;login type&#12289;Operation system Session ID&#65289;&#65307;Operation: Can kill user directly&#12290;
    6.     Oracle EBS Application users Activity&#65288;KPI&#65306;Program ID&#12289;Program type&#65288;Forms or Concurrent Programs&#65289;&#12289;Program name&#12289;Running Program Username&#12289;user description&#12289;Program start time&#12289;Program end time&#12289;cost time (Second)&#12289;Application User Email Address&#65289;&#65307; Operation:Kill the running program&#65288;e.g. Forms ,Concurrent Programs, Concurrent Requests&#65289;&#12290;
    7.     Oracle EBS Discoverer Reports Top 10 running times per month&#65288;KPI&#65306;Instance name&#12289;month&#12289;Discoverer Report Name&#12289;Running times&#65289;;
    8.     Oracle EBS Discoverer Reports Activity &#65288;KPI&#65306;SID&#65292;Serial#&#12289;Execute times&#12289;Oracle username&#12289;machine&#12289;os username&#12289;Program type&#12289;SQL&#12289;CPU Time &#12289;PGA-ALLOCATED&#12289;PGA USED&#12289;PGA Freeable&#65289;&#65307; Operation&#65306;kill the running Discoverer Reports directly&#12290;
    9.     Online realtime Suport&#65306;SGAgent user can press the button in the top menu&#65292;chat with TechWiz Engineers directly using text words&#12290;
    10.     Store and analyze Historical data
    11.     Remote monitor &#65306;SGAgent can send its output by FTP to a public IP. Then the clients can monitor his organization from the web with any device that support web browsing.
    Add my MSN&#65307;[email protected]

  • Where can I configure the naming rule for child columns?

    I have the following logical model:
    https://www.dropbox.com/s/1eux01rrkmcn84f/child_logical.png
    When I engineer it I get the following physical model:
    https://www.dropbox.com/s/pwl2zxkvuigdr5q/child_physical.png
    How can I configure that no entity name prefix should be added to the column name?
    The columns should be named create_ts, modify_ts, delete_ts and attribute_1. (all upcase is ok).
    I tried to change the naming standard template for attribute relations but it has no effect.
    Can anybody give me a hint?

    I used the older SQL Developer modeler and by setting the SUPER and SUB TYPE and Naming Standards I was able to generate the columns without doing post relational model generation activity. I have documented the steps to do the same it taking many steps and generates misbehaves.
    Another problem I face is having to get the SUB TYPES generated as SINGLE TABLE.  If you have more than one SUPER and SUB Type usage it confuses the generator.
    Kindly let me know if there are better ways or fixes coming in soon, if not I would like to revert back to older version.
    1) Created two entities one a super type "SuperEntity" and another sub type "SubEntity"
    Entity name: SuperEntity
    Short name:  SUP
    Attributes:
    Super Entity UID - Primary Key
    Total
    UID - named as SUPER_PK
    Sub-Type implementation
    References - Identifying
    Attribute Inheritance - Primary attribute only
    Entity name: SubEntity
    Short name:  SUB
    Attributes:
    Flag
    Sub-Type implementation
    References - Identifying
    Attribute Inheritance - Primary attribute only
    Hierarchy Key (Foreign key) : named as SUPER_SUB_FK
    2) Generated the Relational Model - the entity SHORT NAME was pre-fixed automatically
       The Sub Typed entity inherits the Foreign key as Primary Key
    CREATE TABLE SuperEnity
        SUP_Super_Entity_UID NUMBER NOT NULL ,
        SUP_Total            NUMBER (8,2) NOT NULL
    CREATE UNIQUE INDEX SuperEnity_PKX ON SuperEnity
      (    SUP_Super_Entity_UID ASC  )  ;
      ALTER TABLE SuperEnity ADD CONSTRAINT SuperEnity_PK PRIMARY KEY
      (    SUP_Super_Entity_UID  )  ;
    CREATE TABLE SubEntity
        SUP_Super_Entity_UID NUMBER NOT NULL ,  -- Inherited from supertype
        SUB_Flag             VARCHAR2 (1) NOT NULL
    CREATE UNIQUE INDEX SubEntity_PKX ON SubEntity
      (    SUP_Super_Entity_UID ASC  )  ;
      ALTER TABLE SubEntity ADD CONSTRAINT SubEntity_PK PRIMARY KEY
      (    SUP_Super_Entity_UID  )  ;
    ALTER TABLE SubEntity ADD
    CONSTRAINT FK_ASS_2 FOREIGN KEY ( SUP_Super_Entity_UID )
    REFERENCES SuperEnity ( SUP_Super_Entity_UID ) ;
    3) Apply the custom transformation script to remove the table abbreviation from column (provided by SQL Developer)
       NOTE: The prefix (abbreviation) is removed in SUPER type attributes.
           : However the SUB type retains the columns, key inherited before
    CREATE TABLE SuperEnity
        Super_Entity_UID NUMBER NOT NULL ,
        Total            NUMBER (8,2) NOT NULL
    CREATE UNIQUE INDEX SuperEnity_PKX ON SuperEnity
      (    Super_Entity_UID ASC  )  ;
      ALTER TABLE SuperEnity ADD CONSTRAINT SuperEnity_PK PRIMARY KEY
      (    Super_Entity_UID  )  ;
    CREATE TABLE SubEntity
        SUP_Super_Entity_UID NUMBER NOT NULL ,  -- The column name did not change based on SUPER TYPE
        Flag                 VARCHAR2 (1) NOT NULL
    CREATE UNIQUE INDEX SubEntity_PKX ON SubEntity
      (    SUP_Super_Entity_UID ASC  )  ;
    ALTER TABLE SubEntity ADD CONSTRAINT SubEntity_PK PRIMARY KEY
      (    SUP_Super_Entity_UID  )  ;
    ALTER TABLE SubEntity ADD
    CONSTRAINT FK_ASS_2 FOREIGN KEY ( SUP_Super_Entity_UID )
    REFERENCES SuperEnity ( Super_Entity_UID ) ;
    4) Applied Naming Standards Specifically on the SUB TYPE table (SubEntity) as
    COLUMN FOREIGN KEY : {ref column abbr}
    CREATE TABLE SubEntity
        Super_Entity_UID NUMBER NOT NULL ,  -- Name follows the SUPER TYPE
        Flag             VARCHAR2 (1) NOT NULL
    CREATE UNIQUE INDEX SubEntity_PKX ON SubEntity
      (    Super_Entity_UID ASC  )  ;  -- Name follows the column/attribute name
      ALTER TABLE SubEntity ADD CONSTRAINT SubEntity_PK PRIMARY KEY
      (    Super_Entity_UID  )  ; -- Name follows the column/attribute name
      ALTER TABLE SubEntity ADD
      CONSTRAINT FK_ASS_2 FOREIGN KEY  (    Super_Entity_UID  ) -- Name follows the column/attribute name
      REFERENCES SuperEnity  (    Super_Entity_UID  )  ;

  • LVOOP code distribution

    Semi-hypothetical question.
    If I have a hierarchy of LVOOP classes which provide a certain functionality, what's the best way to go about distributing the code with an eye on preventing further inheritance from the entire hierarchy.
    In other words, how can I stop anyone from using my code base and extending it willy-nilly (and possibly doing something I don't want them to do).
    Do I need to use a constructor which is set to "Community" scope?
    Does anyone have experience of inputs on this?
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

    Static list is unattractive. to say the least.
    Like I said it's semi-hypothetical.
    One possible scenario would be having a toolkit and offering free and extended versions of it.  From a code maintenance point of view, it would be good to have a shared base but to have the extended features only available in the paid-for version.  If the product was based around the fact that the majority of the blood sweat and tears were spent impelmenting the base class then the entire marketing would be built up on the premise that the ability to USE the code would be free, but the ability to use the extended version or to extend it yourself is something which is reserved for paying customers.  This way you build up a market with the users of the free version, thus driving demand for the paid-for version.  AFAIK this is technically very difficult with LV.
    I don't believe it's contradictory to the ideas of OOP at all.  I'm pretty sure most modern programs are written in OOP but they're not generally exposing their class structures the way compiled LV code does.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • Error: No valid application component hierarchy exists in RSA5

    Hi Gurus,
    We have recently installed SAP R/3 for BW. when i get in to RSA5 i am getting error message "no valid application component hierarchy exists" .  Do i need to do any settings here. When click enter later on, i can see all the data sources under new_hier_root.
    And under new_hier_root i have unassinged notes
    New_Hier_root -> unassigned notes -> application components.
    Thanks in Advance,
    Jameel

    Jameel,
    first we need to transfer application hierarchy.
    try this one SBIW>Business Content DS>Transfer Application Component Hierarchy or RSA9.
    Hope this help.
    Regards,
    Nagesh Ganisetti.

Maybe you are looking for

  • Why won't my Macbook Pro Retina not hook up to Air Play Via Apple TV

    So I want to hook up my laptop to the TV. Now Everything is up to date and my model is 2013 computer and the latest addition of the Apple TV Product. I have the top icon on my screen and click on my name, enter my password, but then it says it cannot

  • Can't find my iTunes library on my laptop.

    Can't find iTunes library on my laptop. Daughter's library is there, but mine doesn't seem to be. When I plugged my ipod in, got a message indicatng my ipod was synced to another library and asking if I wanted to erase it and sync with this one.  Can

  • Can't get rid of login screen on initial startup.  Any Idea's?

    I have an iMac with a 21.5 inch screen, recently upgraded to Lion.  The problem is when I power up in the morning I get a grey screen wanting my password, and below that, the option to sleep, restart or shutdown.  If I restart, it comes right back to

  • Oracle XMLType deleteXML problem

    Hi, I am new using oracle xmltype, got a idiot problem when call deleteXML with xpath. I am hoping I can get help here. Code below describes how I did and what is the problem/ BTW, My oracle is Oracle Database 11g Enterprise Edition Release 11.2.0.2.

  • Calendar events showing every day

    Hi all, Recently it seems that when my Calendar app is displaying month view, every day has a little square in it - the one that indicates an event. However, about half of my days have no events at all. I have repeating events set every eight days fo