Creating UME extended attributes

Hi All,
My requirement is, I have to add few custom attributes like region, area etc as UME extended attributes.
In Sytem admin-> system config-> UM config-> Direct editing tab under "ume.admin.self.addattrs" I have added the custom attributes as comma seperated values. Is this right?
If Yes, Can you please tell me how I should proceed further?
If no, can you please detail me the steps to achieve custom attributes?
This is a very urgent requirement.So, can anyone help me ASAP?
Thanks in advance.
Regards
Deepa

Hi James,
If the datasource is going to be LDAP directory, then will
the extended attributes will get saved in the LDAP directory without any mapping in datasource xml?
Regards
Deepa
Message was edited by: Deepa  Jampunathan

Similar Messages

  • Cannot create or replace : The specified extended attribute name was invalid.

    New problem arrived today. Trying to copy a file from 10.6 server with an XP (SP3) client. I get this error:
    Cannot create or replace (file name here): The specified extended attribute name was invalid.
    The contents of the file can be copied, but not the folder. Other files can be copied. There are no funny characters. The name is not too long. I propogated the permissions on the share and that had no affect. The problem exists on three different XP systems. Can't find extended properties that could be causeing a problem. Any ideas?

    Nikon just released a Firmware update today for the D750

  • CSI: update_item_instance issues while creating extended attributes

    Hello,
    For our customer's data conversion, installed base instances have already been created, there is only need to create extended attributes.
    Issues I have encountered are:
    - Whenever an error is encountered in the API call, all following records are rejected with the same error (even the same instance ID/primary key/attribute ID) as the first error record.
    - Extended attributes are randomly entered in the wrong fields (as if one field had gone missing and the others had been updated)
    - Date formats have been changed from DD/MM/YYYY to DD-MON-YYYY when consulting from Installed Base (but this happened only once)
    Other information: There are 14 extended attributes to be added for each item instance, I removed some of the attributes to make the code more readable.
    I followed the metalink note that shows the implementation method for this API and only added the recursive elements that we needed for the 14 attributes + functions to retrieve item_id and such.
    The "message()" function replaces is defined as FND_FILE.PUT_LINE(which =>fnd_file.log,buff => p_msg);
    PROCEDURE main (errbuf OUT VARCHAR2
                        ,retcode OUT NUMBER
    IS
         vl_status                BOOLEAN;
         vl_item_id                NUMBER;
         vl_instance_id           NUMBER;
         v_count               NUMBER;
         v_err_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_ERROR_REC;
         v_trx_id number ;
         v_ret varchar2(240);
         v_msg_count number;
         v_msg_data varchar2(2000);
         v_date date;
         t_msg_dummy NUMBER;
         t_output VARCHAR2(2000);
         vl_attribute_id NUMBER;
         v_inst_rec csi_datastructures_pub.instance_rec;
         v_ext_attr csi_datastructures_pub.extend_attrib_values_tbl;
         v_party_tbl csi_datastructures_pub.party_tbl;
         v_account_tbl csi_datastructures_pub.party_account_tbl;
         v_pr_tbl csi_datastructures_pub.pricing_attribs_tbl;
         v_org_as s_tbl csi_datastructures_pub.organization_units_tbl;
         v_asset_as s_tbl csi_datastructures_pub.instance_asset_tbl;
         v_trx csi_datastructures_pub.transaction_rec;
         v_inst_id_lst csi_datastructures_pub.id_tbl;
    BEGIN
         APPS.FND_GLOBAL.Apps_Initialize(FND_PROFILE.value('user_id')
    ,FND_PROFILE.value('resp_id')
    ,FND_PROFILE.value('resp_appl_id'));
         IF cur_iea_attributes%ISOPEN
         THEN
              CLOSE cur_iea_attributes;
         END IF;
         IF get_trx_id
         THEN
              message('Transaction ID '||to_char(gv_trx_id));
              FOR v_cur_iea_attributes IN cur_iea_attributes
              LOOP
                   v_count:=0; -- Initialisation du compteur du ligne. Attention, le nb de lignes dans interface = 14 x nb lignes dans stg
                   IF check_unique_serial(v_cur_iea_attributes.numero_serie)
                   -- Recuperation de l'item ID
                   THEN
                        get_item_id(p_serial_number => v_cur_iea_attributes.numero_serie
                                       ,p_item_id => vl_item_id
                                       ,p_status => vl_status
                        message('Resultat get_item_id: '||to_char(vl_item_id));
                        get_instance_id(p_item_id => vl_item_id
                                            ,p_serial_number => v_cur_iea_attributes.numero_serie
                                            ,p_instance_id => vl_instance_id
                                            ,p_status => vl_status
                        IF vl_status
                        THEN
                             v_trx.TRANSACTION_DATE:=trunc(SYSDATE);
                             v_trx.SOURCE_TRANSACTION_DATE:=trunc(SYSDATE);
                             v_trx.TRANSACTION_TYPE_ID:=gv_trx_id;
                             message('Entrance v_count'||to_char(v_count));
                             v_inst_rec.instance_id:=vl_instance_id;
                             v_inst_rec.object_version_number := 1;
                             IF v_cur_iea_attributes.IAE_GUARANTEE_END_DATE IS NOT NULL
                             THEN
                                  v_count:=v_count+1;
                                  v_ext_attr(v_count).instance_id := vl_instance_id;
                                  message('v_ext_attr(v_count).instance_id: '||to_char(v_ext_attr(v_count).instance_id));
                                  message('vl_instance_id: '||to_char(vl_instance_id));
                                  get_attribute_id(p_attribute_code =>'GUARANTEE_END_DATE'
                                                      ,p_attribute_id => vl_attribute_id);
                                  message('vl_attribute_id: '||to_char(vl_attribute_id));
                                  v_ext_attr(v_count).attribute_id := vl_attribute_id;
                                  v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_GUARANTEE_END_DATE ;
                                  message('v_cur_iea_attributes.IAE_GUARANTEE_END_DATE: '||v_cur_iea_attributes.IAE_GUARANTEE_END_DATE);
                                  message('');
                             END IF;
                             IF v_cur_iea_attributes.IAE_LAST_CTRL_DATE IS NOT NULL
                             THEN
                                  v_count:=v_count+1;
                                  message('v_count'||to_char(v_count));
                                  -- Les 6 champs obligatoires a remplir pour un update
                                  v_ext_attr(v_count).instance_id :=vl_instance_id;
                                  get_attribute_id(p_attribute_code =>'LAST_CTRL_DATE'
                                                      ,p_attribute_id => vl_attribute_id);
                                  v_ext_attr(v_count).attribute_id := vl_attribute_id;
                                  v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_LAST_CTRL_DATE ;                    
                             END IF;
                             CSI_ITEM_INSTANCE_PUB.update_item_instance
                                       p_api_version => 1
                                       ,p_commit => fnd_api.g_false
                                       ,p_init_msg_list => fnd_api.g_true
                                       ,p_validation_level => fnd_api.g_valid_level_full
                                       ,p_instance_rec => v_inst_rec
                                       ,p_ext_attrib_values_tbl => v_ext_attr
                                       ,p_party_tbl => v_party_tbl
                                       ,p_account_tbl => v_account_tbl
                                       ,p_pricing_attrib_tbl => v_pr_tbl
                                       ,p_org_assignments_tbl => v_org_ass_tbl
                                       ,p_asset_assignment_tbl => v_asset_ass_tbl
                                       ,p_txn_rec => v_trx
                                       ,x_instance_id_lst => v_inst_id_lst
                                       ,x_return_status => v_ret
                                       ,x_msg_count => v_msg_count
                                       ,x_msg_data => v_msg_data
                                  -- Output the results
                                  if v_msg_count > 0
                                  then
                                       for j in 1 .. v_msg_count
                                       loop
                                            fnd_msg_pub.get ( j , FND_API.G_FALSE , v_msg_data , t_msg_dummy );
                                            t_output := ( 'Msg' || To_Char ( j ) || ': ' || v_msg_data );
                                            message( SubStr ( t_output , 1 , 255 ) );
                                       end loop;
                                  end if;
                        ELSE
                             message('Update not performed for '||v_cur_iea_attributes.numero_serie||' and '||vl_item_id);
                        END IF;
                   ELSE
                        message('Erreur sur '||v_cur_iea_attributes.numero_serie);
                   END IF;
                   commit;
                   message('Commit done for update loop');
              END LOOP;
         ELSE
              message('No Transaction ID - EOP');
         END IF;
    EXCEPTION
         WHEN OTHERS
         THEN
              ROLLBACK;
              message('Error in main program, rolling back');
    END main;
    Thanks!

    Todd
    The issue seems to because this:
    x_instance_rec.inventory_item_id := ib_rec3.inventory_item_id;
    You are selecting the item id from your staging table. But the serial number in the csi_item_instances is associated with the instance is a different item id than ib_rec3.inventory_item_id. Hence this error. You cannot change the item in the IB once the instance is created.
    You have two choices: comment this out or change the inventory_item_id in staging table to match with the csi_item_instances.
    Also a lot depends on what is your serial number uniqueness. If you are using the same serial number for two different items (uniqueness with item_Id) you need to be careful which one you are picking (based on serial number).
    Thanks
    Nagamohan

  • Create a dynamic attribute for each user

    Hi All,
    I request you all to let me know how to give an approach to the following requirement.
    REQUIREMENT: I have to create a dynamic attribute in UME for each user and the read the attribute on lead selection of a table having list of Users.
                             On lead selection, the dynamic attribute value should be either true or false. Based on this value the rest of the application specific operations wil be taken care.
                              If a particular User does not have the dynamic attribute associated to it, then we need to create the same.
    Looking forwarrd for your help.
    Regards
    Dipendra

    //@@begin javadoc:UMSavePropertiesByNode()
         /** Declared method. */
      //@@end
      public boolean UMSavePropertiesByNode( )
        //@@begin UMSavePropertiesByNode()
              try {
                   if (wdContext.currentUserDataElement().getVaIUserMaint().setAttribute("com.sap.security.core.usermanagement", this.getUMPropertyName(null) + ".TableColumns", this.getPropertiesByNode())) {
                        wdContext.currentUserDataElement().getVaIUserMaint().save();
                        wdContext.currentUserDataElement().getVaIUserMaint().commit();
                        msg.reportMessage(IMessageTableUtilsComponent.UMPROPERTY__SAVE__FIELDS__SUCCESS, null, false);
              } catch (UMException ex) {
                   wdContext.currentUserDataElement().getVaIUserMaint().rollback();
                   msg.reportMessage(IMessageTableUtilsComponent.UMPROPERTY__SAVE__FIELDS__ERROR, null, false);
                   return false;
              return true;
        //@@end
      //@@begin javadoc:UMLoadFieldsProperties()
         /** Declared method. */
      //@@end
      public petrobras.com.br.classes.FieldsTable UMLoadFieldsProperties( petrobras.com.br.classes.FieldsTable fields )
        //@@begin UMLoadFieldsProperties()
              String properties[] = wdContext.currentUserDataElement().getVaIUserMaint().getAttribute("com.sap.security.core.usermanagement", this.getUMPropertyName(null) + ".TableColumns");
              if (Compare.getLenght(properties) > 0) {
                   //msg.reportWarning("[UMLoadFieldsProperties]: properties.length = " + properties.length);
                   for (int i = 0; i < properties.length; i++) {
                        int attrPos = Integer.parseInt(properties<i>.substring(properties<i>.indexOf("(") + 1, properties<i>.indexOf(")")));
                        String attrName = (String) properties<i>.substring(properties<i>.indexOf(")") + 1, properties<i>.indexOf("="));
                        int attrValue = Integer.parseInt(properties<i>.substring(properties<i>.indexOf("=") + 1, properties<i>.indexOf(";")));
                        Field item = fields.getField(attrName);
                        if (item != null) {
                             item.setPosition(attrPos);
                             item.setVisibility(WDVisibility.valueOf(attrValue));
                             fields.removeFieldByName(attrName);
                             fields.addField(item);
              return fields;
        //@@end
    regards,
    Angelo

  • "Error writing metadata to" message and extended attributes

    After being frustrated by this error message in Bridge while trying to apply keywords to various image files I finally took the time to investigate, and I think I found the cause of the issue. In a nutshell, if the extend attribute "com.apple.FinderInfo" has not yet been created for a given file, then this message appears.
    The start of the puzzle was that some files would take the keyword and others would not. After observing identical permissions on files that worked and files that did not, I noticed that in a terminal listing of the files in question, some files had extended attributes and some did not (extended attributes are identified by an @ symbol when running ls -la in a terminal window. For example:
    -rw-rw-rw-@   1 mike  staff  26131946 21 Jan 23:56 120114-133059-4612.cr2
    -rw-rw-rw-    1 mike  staff      5710 21 Jan 22:42 120114-133059-4612.xmp
    -rw-rw-rw-@   1 mike  staff  27200794 17 Jan 17:52 120114-133145-4613.cr2
    -rw-rw-rw-    1 mike  staff      5702 21 Jan 22:42 120114-133145-4613.xmp
    -rw-rw-rw-@   1 mike  staff  26973498 21 Jan 23:07 120114-133149-4614.cr2
    -rw-rw-rw-@   1 mike  staff      6648 21 Jan 23:19 120114-133149-4614.xmp
    As you can see, the file called 120114-133145-4613.xmp has not extended attribute, but the file 120114-133149-4614.xmp does. The former throws an error when applying a keyword, the latter does not.
    So I dug a bit further and it appears that when the file attribute called com.apple.FileInfo is missing from an xmp file, metadata cannot be witten. The contents of this extended attribute for a working XMP file look like this
    $ xattr -l 120114-133058-4611.xmp
    com.apple.FinderInfo:
    00000000  54 45 58 54 43 52 61 77 00 00 00 00 00 00 00 00  |TEXTCRaw........|
    00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |................|
    00000020
    According to specs I found googling, the first 4 bits identify the file type (TEXT), and the next four identify the file creator (CRaw). IOW no file-specific info seems to be present.
    So as a test, I simply copied the contents of com.apple.FinderInfo from a file that had it to a file that didn't. Once the file that didn't received the new attribute, metadata writes worked. The command I used for the copy was
    xattr -wx com.apple.FinderInfo "`xattr -px com.apple.FinderInfo 120114-133534-4633.xmp`" 120114-133041-4602.xmp
    It also appears that this metadata is written by Bridge based on some unknown trigger, because occasionally during my investigation a file that previously would not take metadata suddenly did, and once I knew to look for extended attributes, in every case the file in question suddenly had com.apple.FinderInfo extended attribute.
    So...I'm not sure if this is a bug in finder or in bridge, but it is definitely a bug and needs to be addressed.
    ...Mike

    I have tried purging the cache, and also deleting it entirely and starting over, to no effect.
    Mike
    just did a quick try and don't know if it is the right way.
    Using Lightroom 3.6 (not very familiar with Lightroom) and Bridge 4.0.5.11 on MacOSX 10.6.8
    I randomly choose some CR2 files that where somewhere on my system and copied them to a new folder. Imported them in Lightroom and added some rating and a few keywords. (with setting metadata to XMP file active)
    Then went to Bridge and opened the same folder. After caching Bridge showed the info as filed in Lightroom. Added some keywords to all files without problem. Went back to Lightroom (restarted it and had to choose read metadata menu. After this no problem to read new keywords form Bridge. But they only show in Italic because the have not been made persistent in the Bridge keyword list, however this is as expected behavior.
    Tried a develop setting and that was also showing in Bridge correctly. Went a few times back and fort (files in Lightroom showing a memo with Exclamation sign top right of the in Bridge changed thumbnail asking for reading metadata).
    Is this about the way you mean to describe?
    And when having set Automatically export changes to XMP have you set this option in both Lightroom and Bridge (this s to be found in the Camera Raw preferences 'save image settings in: sidecar XMP')
    And there are a few things to refresh also in Bridge besides the deleting of the cache file, you can also delete the Bridge plist file from the user library preferences and restart Bridge holding down option key and chose reset preferences. And did you run the check and repair permissions for your system also?
    I tried to look in terminal but could not find a way to use the ls -la command on the folder with changed files so no comparing on that side I'm afraid.

  • HELP: Extended Attributes Not Appearing In Instances of Custom Content Type

    From Java code I create a custom content type derived from Document and define some extended attributes with default values for that type. All done using the same methodology shown in the Developer's Guide and Oracle example code.
    I start ifsmgr and I can indeed see the content type and the extended attributes.
    If I however create an instance of this (custom) type, either from the Viewer (file Upload) or from Java code (using code simuilar to createDocument from the Oracle ContentModule example), the extended attributes do not appear!
    BUT, if I delete one of the extended attributes using ifsmgr (highlight one of my extened attributes, click on "Remove", and then "Apply"), from that point on the previously missing extended attributes appear (except for the one I deleted of course) when I create files of the custom type from either Java code or the Viewer. Furthermore, once I get ifs to "see" one of these extended attributes in this manner, I can delete the extended attribute and re-create it from Java at will and it will appear in created instances of my custom content type just fine.
    If however I add another new extended attribute to the custom content type, I have to do the "Remove/Apply" drill in ifsmgr to get this new attribute to appear in created files of my custom type.
    I've tried deleting all instances of the custom type and closing both ifsmgr and the Viewer, but unless I delete one of the extended attributes from ifsmgr I cannot get new extended attributes to appear.
    What do I need to do in my 9ifs Java code to get new custom content extended attributes to appear in instances of that custom type?
    Thank you,
    Jeff "Did Kafka Write ifs?" Rininger

    Dear @user10993347,
    As mentioned by @vinod2303, you need to maintain content relationships along with subscriptions.
    Regards,
    Saurabh

  • Error to create a new attribute and modify attribute retriever in weblogic

    Hi Experts
    I have intalled a weblogic server protected by Oracle Entitlements Server, this server contain a web app deployed, this app have policies to restrict the access to resources. For this policies i created an attribute retriever in weblogic console after, i did define an attribute to map this attribute retriever and used in a policy but, I have a problem when i try to create a new attribute or modify an attribute retriever, navigate to Home >Summary of Security Realms >"OES REALM" >Providers >ASIAuthorizationProvider clic on tab "attributes" and appears this errorr:
    Error opening /ext_jsp/security/providers/retrievers/CreateALESAttributes.jsp.
    The source of this error is:
    java.lang.NullPointerException
         at com.bea.retrievers.action.utils.BaseActionUtils.getNonALESAttributeRetrievers(BaseActionUtils.java:370)
         at jsp_servlet._ext_jsp._security._providers._retrievers.__createalesattributes._jspService(__createalesattributes.java:152)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
         at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119)
         at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
         at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:365)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._wlsconsole.__flowlayout._jspService(__flowlayout.java:175)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._wlsconsole.__gridlayout._jspService(__gridlayout.java:219)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._wlsconsole.__twocollayout._jspService(__twocollayout.java:205)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
         at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
         at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
         at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
         at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
         at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    My product versions are:
    Weblogic 10.3.2
    OES WLS-SSM 10.1.4.3 + CP4
    OES Admin 10.1.4.3 + CP4
    DB 11gR1
    Anybody can help me please.
    Regards

    You need to add attribute to User Extended Attributes its an configuration object. After changes you need to restart the App / Web server. Only after restart IDM will start storing the value into repository and you can use them as global.<<attr name>>
    Thanks
    MK

  • Extended Attribute properties

    Hello,
    I have a problem with the property of an Extended Attribute for the Document class.
    If I create a New Extended Attribute and set its properties (Indexed, Settable and ReadOnly), after the Apply the Read Only property is setted, also if I uncheck its checkbox.
    The result is an Exception for a non-updatable attribute if I try to change the attribute's value.
    Any suggestion is appeciated.
    Thanks in advance,
    Maurizio.

    Hello Maurizio!
    Try to set your new extended attribute's UPDATEABLE_ATTRIBUTE also to true.
    Bests,
    Tamas

  • Approval Limit of user - Extended Attributes

    Hello everyone,
           I would like to know the difference between standard values and local values for approval
    limit in extended attributes in PPOSA_BBP.  The standard value has 15000 AUD which is
    inherited by the organization unit under which the user is created.  Local value is 1000 AUD.
    What does this mean?  All users under the organization unit carry the same standard valu for
    approval limit but only head carries the local value which is 1000 AUD.
       Can anyone please answer to this.
    Thanks in Advance.

    Hi Priya,
    Even i checked in my system and i couldn't able to find much importance for standard value...system is considering only local values.....
    if you got the answer then please post it ...
    Thanks
    Ravi

  • User's Approval Limit  in Extended Attributes

    Dear SRMer's,
    System info:
    SRM 4.0.
    Problem Description:
    In PPOMA_BBP, I set my approval limit in the 'PO Value Limits' under Extended attributes to $1000.00 and added an approver for the SLApprover in Attributes tab.
    But when I create a shopping cart with value greater (>) than $1000.00,
    I dont see the SL approver on the approval flow and the approval flow says  no approval required.
    Please help.
    Thanks in advance,
    Best Regards,
    Bob

    Hi Bob,
    Deactivate your workflows for the shopping cart then check again.
    (or)
    follow the link below
    http://help.sap.com/saphelp_srm50/helpdata/en/79/ca013a0c88bc7ce10000000a114084/content.htm
    with regards,
    mahesh

  • How to set Max Rows when I search extended attribute in Admin Setting?

    When I search extended attributes in Admin Setting, the default max row is 500.
    Can I change the Max rows' Setting?
    Thanks

    We don't have a feature config for this in the core application, however you can adjust the 500 limit using a ready report.  Ready Reports is a solution pack that allows you to create saved searches in the form of reports.  You can get the ready reports solution pack in the latest extensibility pack.

  • IdM v7 and User Extended Attributes

    I did a demo install of IdM version 7.1 and when I looked under debug and then list 'Configuration' objects,
    I did not see 'User Extended Attributes' ?
    I thought this comes as part of IdM in a very basic simple format ?
    I've worked with IdM a fair amount, and don't every remember creating this file.
    Can someone confirm this ( one way or the other ) ?
    TIA

    The "IDM Schema Configuration" object is an IDM 8+ object only. The extended attributes have been completely changed between IDM 7 and IDM 8.
    In IDM 7.1 the extended attributes are stored in the Configuration object called "User Extended Attributes". The initial import and set up of your repository should have created it. By default there's a few extended attributes (like idmManager, etc) that are set up. On a fresh install you won't find the file in the sample directory. It's only in the repository. You should be able to see it from the debug page or by extracting the XML object from the repository directly using the lh command line tool. If not then something might have screwed up in the installation.
    However, the fact that you've got attributes called "IDMAttributeConfiguration" and "IDMObjectClassConfigurations" leads me to believe you've actually got an IDM 8 install, not an IDM 7 install. In which case, as Paul pointed out, your attributes are stored in the "IDM Schema Configuration" object. (Again, not found in the sample dir, only in the repository and is created on initial import.)

  • "init failed " error when calling PRIV:UME  privilege for task  Create UME

    Hi All
    as per the document
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/304280b4-25d0-2b10-b6a4-89c27409dea7&overridelayout=true
    I  have done all the settings like this and when I call the privilege
    using PRIV:UME and subsequently the the create Ume, modify ume,delete
    ume tasks are not  working  but is giving  an  error u201C init failedu201D .
    I know the error is because some values should be set as an attribute
    or the repository constants of UME are not passed to these jobs.
    But there is no information on how to pass these values to these pass
    in the attached documentation or anywhere. The documentation you
    released are not complete .
    This is the same case with Create Java user, Modify Java user, delete
    Java user.
    Can any one give how exactly repository and other attributes values can be passed to the PASS of task
    Create UME user etc when we run the task by calling the Privilege.
    Please advice.

    Hi All
    as per the document
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/304280b4-25d0-2b10-b6a4-89c27409dea7&overridelayout=true
    I  have done all the settings like this and when I call the privilege
    using PRIV:UME and subsequently the the create Ume, modify ume,delete
    ume tasks are not  working  but is giving  an  error u201C init failedu201D .
    I know the error is because some values should be set as an attribute
    or the repository constants of UME are not passed to these jobs.
    But there is no information on how to pass these values to these pass
    in the attached documentation or anywhere. The documentation you
    released are not complete .
    This is the same case with Create Java user, Modify Java user, delete
    Java user.
    Can any one give how exactly repository and other attributes values can be passed to the PASS of task
    Create UME user etc when we run the task by calling the Privilege.
    Please advice.

  • Using extended attributes

    Hi Folks,
    I'm new to sun idm and i need to add some new attributes to user object.
    what i have done is updating the idm schema configuration. But what to do next?
    I'm really going insane, read hundreds of pages about forms views and workflows but
    this does not help for me, argh!
    The goal is to be able to enter the values for these new attributes when a user is created.
    So i want to adjust anonymous enrollment and user creation by admin...
    Can someone point out the steps to go on?
    some advice would really be appreciated

    not sure where you extended attribute went; maybe iFS created a DOCUMENT2 class for you by default. anyway, in order to do this the right way:
    first, you need to properly extend the document class, creating a new content class with your extended attributes. for example, create the class ARIDOCUMENT that extends DOCUMENT and adds the TITLE attribute. (look at the developer docs or the sample code to see how to do this. there's a complete example on creating and modifying subclasses in the CMS installation at: 9ifs\samplecode\oracle\ifs\examples\devdoc\subclassing)
    once you do that, in order to create a new document with your custom fields, you need to perform the following steps: create a new document definition, set the standard attributes, apply your custom doctype, and then set the extended attributes. here's a quick snippet:
    // create docdef...
    DocumentDefinition def = new DocumentDefinition(session);
    // set standard attributes...
    def.setAttribute(Document.NAME_ATTRIBUTE, AttributeValue.newAttributeValue("File.txt"));
    def.setAttribute(Document.DESCRIPTION_ATTRIBUTE, AttributeValue.newAttributeValue("A text file."));
    // look up and apply your custom doctype
    ClassObject co = session.getClassObjectByName("ARIDOCUMENT");
    def.setClassObject(co);
    // set extended attributes. note: you can't use the 'Document.' prefix,
    // because TITLE is not a DOCUMENT attr!
    def.setAttribute("TITLE", AttributeValue.newAttributeValue("My Title"));
    // create the aridoc...
    Document aridoc = (Document) session.createPublicObject(def);
    in a nutshell, that's how you do it...
    hope that helps,
    .rich

  • UME User Attribute

    Hi All,
    I want to use a standard UME user attribute which should allows multiple values.  Is there any standard UME attribute allows multiple values.
    I need this functionality to create a Virtual Group.  I have followed the [Help Link|http://help.sap.com/saphelp_nw70/helpdata/en/43/fcfa2942ed7067e10000000a1553f6/content.htm].  to create Virtual Group based on UME department attribute.  Department attribute is not supporting multiple values. 
    I want to achieve this is in Standard Configuration of Portal.
    Can anyone help me or list me the Standard UME attribute which supports multiple values. 
    Thanks in Advance.
    Regards
    Venkatesh. K

    Hi Venkatesh,
    I did a quick search of the online help and found this...
    The user attributes do not support multiple values by default, but if you mapped an attribute to an LDAP attribute with multiple values, you could read for a user the attribute department, which has the values Marketing and Distribution. This user would then belong to both virtual groups Marketing and Distribution.
    It is in the documentation for [configuring virtual groups|http://help.sap.com/saphelp_nwce10/Helpdata/EN/43/fcfa2942ed7067e10000000a1553f6/frameset.htm].
    So it all depends on your data source.
    -Michael

Maybe you are looking for