Queryable Extended Attributes not Queryable

Hey All,
I added a queryable attribute 'Username' to IDM. I set it up under the config -> attributes page. I then added it to the UserUIConfig to the SummaryAttrNames, QueryableAttrNames and the RepoIndexAttrs lists. I then edited the User Search Defaults object and added the attribute to the getSearchableAttrs Function. I then added it to the tabbed user form as a text field on the attributes page. I named the field accounts[Lighthouse].Username. I can update and modify the value through the userform fine. It saves changes etc. However, when I search for a value using the find user form, nothing comes up. I can set a users Username to 'abc', then do a find user that starts with 'a' or contains 'b' and I get nothing. Does anyone know what I am missing to make the query work?

reply to "What happens if you add more then two items and it takes you over the 5 item limit? Are the extra attributes just ignored? Are the RepoIndexAttrs the only attributes with a limit of 5? Can I still do searches for more attributes in QueryableAttrNames?
I have more then 5 in the RepoIndex, but one of the other attributes is searchable in the find user interface. The attribute that is working is also beyond the 5 attribute limit in the RepoIndexAttrs list.."
I believe you can have more than 5 queriable attributes, but IdM only indexes 5. Indexed searches are faster than unindexed searches that is the only difference. If its queryable then you can query on it (indexed or not).

Similar Messages

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

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

Resource Attributes not saving in Queriable User Extended Attributes

Howdy,
I added a few queriable user extended attributes to IDM. I originally added them in through the configure user attributes interface. I then edited the UserUIConfig to specify that they were queryable. I then edited the User Search Defaults form's getSearchableAttrs function to include these attributes. My added attributes now show up in the search user form, etc., just like I expected them to. Next I configured a new resource adapter for a database table that contained some values I wanted to use to populate these queriable attributes. I wrote a correlation rule, and ran reconciliation on the new resource. It matched up the account entries and automatically matched and linked the account information. So far so good. However, the user extended attributes I defined are not getting populated with the data from the new resource. The mapped resource attributes are treated as part of the user view, but only under the given resource, not as a queriable attribute. I really want to be able to use the find user interface with these datafields. Does anyone know why my data is ot making it into the queriable fields? Do I need to write another rule or workflow? Any advice would be most helpful.
Thanks!
Jim

Queryable attributes refer to attributes stored in the IDM user object, and so need to be referenced as such.
If you want attribute 'foo' in resource 'bar' to be stored as a Queryable attribute, you need to define it like so in your User Form :
<Field name='accounts[Lighthouse].foo'>
    <Expansion>
          <ref>accounts[bar].foo</ref>
    </Expansion>
</Field>This should pull the value from the resource attribute and put it in the IDM attribute. If you refer to it as a global.foo everywhere, that might work (but I find globals to be problematic).
Let me know if it works...
Jason

Snow Leopard (10.6+) - could not copy extended attributes to *

I have a NAS device running Samba version 3.0.26a.
Many files I download with Safari, view with iPhoto, or use in many other OS X applications, get extended attributes added to them.
These extended attributes "cannot" be copied to my network devices using the Finder copy dialog. Finder will copy the file, report it failed to copy extended attribs, then delete the file!
However, the cp and rsync commands work, but cp complains about the extended attributes. But at least it actually copies, and leaves the file on my network appliance!
Here is a summary of the log:
mbp-stnt-09-01:Desktop josh_miller$ cp LexmarkX940eX.dmg /Volumes/projects/_Software/
cp: LexmarkX940eX.dmg: could not copy extended attributes to /Volumes/projects/Software/Lexmark_X940eX.dmg: Operation not permitted
Here is an example of an Extended attrib on that file:
mbp-stnt-09-01:Desktop josh_miller$ xattr LexmarkX940eX.dmg
com.apple.diskimages.recentcksum
All other OS X versions back as far as I can see, work fine. This is a new issue with Snow Leopard and I'd very much like it corrected!
Message was edited by: JoshMillerGNWC

If you want to report this issue to Apple's engineering, send a bug report or an enhancement request via its Bug Reporter system. To do this, join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report or enhancement request. The nice thing with this procedure over posting here or submitting feedback is that you get a response and a follow-up number; thus, starting a dialog with engineering.

I don't find User Extended attributes in IDM 8

Hi all,
I have installed idm8 and I need to extend the user attributes, but I can't find the User Extended Attributes object (or Extended User Attributes). Can anyone help me?

From the release notes :
Identity Manager 8.0 consolidates the locations where an administrator specifies extended,
queryable, and summary attributes for user objects into the new
IDM Schema Configuration object. (ID-17784) In prior versions of Identity Manager, an administrator
edited the User Extended Attributes configuration object to add extended attributes for
user objects and the UserUIConfig configuration object to specify additional queryable or
summary attributes for user objects. An administrator now edits the IDM Schema Configuration
object for these purposes.

How can i extended attribute of user and add attribute to ldap

how can i extended attribute of user and add attribute to ldap
1.
i use spe to modified "Default User Library":add Field like
title:nation name:accounts[Lighthouse].nation
2.
modified "IDM Schema Configuration"
add <IDMAttributeConfiguration name='nation' description='default attribute from UserExtendedAttributes/UserUIConfig' syntax='STRING'/>
in <IDMAttributeConfigurations>
and
add <IDMObjectClassAttributeConfiguration name='nation' queryable='true' summary='true'/> in<IDMObjectClassConfiguration>
there is extended attribute when i create new user
3.
i create new resource to ldap,and i add nation in "Account Attributes" tab
but the new attribute not add to ldap
i am beginner,how to extended attirbute add add to ldap attribute?

So, if I want to fill in blanks on a form where I need to add more pages to fill history, what program do I need? In Adobe Reader, I can edit and fill in blanks, but I cannot duplicate more blank pages.

User Extended Attributes in IDM 7

Has the set up changed? I imported all my objects from 6.0 and the user extended attributes aren't there. I imported the UserUIConfig object, so I would think they would be present. I noticed that the attributes tab moved in the new version, have the methods of defining them changed much?

User Extended Attributes are typically defined in the object Configuration:User Extended Attributes. UserUIConfig is used e.g. to define if the attribute should be "Queryable" -but yes its a correct observation that the UserUIConfig is changing shapes...

When I restore my Mac with Time Machine and then want to partition my disk, Disk Utility always says incorrect number of extended attributes

When I need to restore my Mac from a time machine backup and then partition my hard disk (the disk inside the computer not the time machine disk), Disk Utility always says "Incorrect Number of Extended Attributes". I then boot into Recovery HD and run disk repair. The result? "The volume Macintosh HD appears to be OK". So then I reboot into normal OS and try the partition again, still Incorrect number of extended attributes. I have even tried /sbin/fsck -fy in single-user mode but it still says the volume is ok. I have tried partition my disk in the recovery HD and it still fails.
Can anyone please help me solve this problem?

Try something stronger, such as DiskWarrior or TechTool Pro.
iMac refurb (27-inch Mid 2011), OS X Mavericks (10.9.4), SL & ML, G4 450 MP w/Leopard, 9.2.2

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

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported. Is this a bug in Mavericks?

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported.
This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks). So far as I know, all of the kit I am using is in good order (despite the file corruption reports). So I am beginning to wonder if it could be due to a bug in Mavericks? Both SSD drives have been formatted to MacOS Extended (journaled) format. Should I have used a different format, I wonder?
Has anyone else encountered this issue?
Does anyone have a solution?
Or an explanation that might help my investigation of the issue?
Thanks guys,

I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs.
I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try.

Can't repair Macintosh HD in Disk Utility (extended attributes)

Hi all,
I have a Retina Macbook Pro with one of them new fancy SSDs in it. I'm running 10.9.3 all up-to-date and am a bit computer-savvy, but I'm more than puzzled by what my Mac has been doing as of late.
When trying to install Windows via Bootcamp, I ran into an error message in the Partitioning step of the process. I hopped into Disk Utility, figuring I could simply partition from there (something in me trusts Disk Utility more than the Boot Camp Assistant). Partition failed!
I then executed the "Verify Disk" command in Disk Utility, only to be told I needed to restart from the Recovery Partition and use the "Repair Disk" function of Disk Utility then. Log of this whole event is at the end of this post, but the offending line seems to be
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
I then restarted and followed these instructions. "Verify Disk" found no errors, nor did "Repair Disk." I rebooted, only to be met with the same problem!
Is there some sort of lower-level command I can use to repair my disk if I boot in Single User mode or something?
Thanks,
Nathan
2014-06-12 20:58:30 -0400: Disk Utility started.
2014-06-12 20:58:36 -0400: Verifying partition map for “APPLE SSD SD512E Media”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking prerequisites
2014-06-12 20:58:36 -0400: Checking the partition list
2014-06-12 20:58:36 -0400: Checking for an EFI system partition
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s size
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s file system
2014-06-12 20:58:36 -0400: Checking all HFS data partition loader spaces
2014-06-12 20:58:36 -0400: Checking booter partitions
2014-06-12 20:58:36 -0400: Checking booter partition disk0s3
2014-06-12 20:58:36 -0400: Checking file system
2014-06-12 20:58:36 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:36 -0400: Checking extents overflow file.
2014-06-12 20:58:36 -0400: Checking catalog file.
2014-06-12 20:58:36 -0400: Checking multi-linked files.
2014-06-12 20:58:36 -0400: Checking catalog hierarchy.
2014-06-12 20:58:36 -0400: Checking extended attributes file.
2014-06-12 20:58:36 -0400: Checking volume bitmap.
2014-06-12 20:58:36 -0400: Checking volume information.
2014-06-12 20:58:36 -0400: The volume Recovery HD appears to be OK.
2014-06-12 20:58:36 -0400: Checking Core Storage Physical Volume partitions
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:36 -0400: Checking volume
2014-06-12 20:58:36 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:36 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:36 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:36 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:36 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:36 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:36 -0400: Load and verify Segment Headers
2014-06-12 20:58:36 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:36 -0400: Load and verify Transaction Segment
2014-06-12 20:58:36 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:36 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:36 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:36 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:36 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:36 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:36 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:36 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:36 -0400: Load and verify Freespace Summary
2014-06-12 20:58:36 -0400: Load and verify Block Accounting
2014-06-12 20:58:36 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:36 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:36 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:36 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:36 -0400: The partition map appears to be OK
2014-06-12 20:58:36 -0400:
2014-06-12 20:58:36 -0400: Verifying volume “Macintosh HD”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:37 -0400: Checking volume
2014-06-12 20:58:37 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:37 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:37 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:37 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:37 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:37 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:37 -0400: Load and verify Segment Headers
2014-06-12 20:58:37 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:37 -0400: Load and verify Transaction Segment
2014-06-12 20:58:37 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:37 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:37 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:37 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:37 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:37 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:37 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:37 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:37 -0400: Load and verify Freespace Summary
2014-06-12 20:58:37 -0400: Load and verify Block Accounting
2014-06-12 20:58:37 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:37 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:37 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:37 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:37 -0400: Checking file system
2014-06-12 20:58:37 -0400: Performing live verification.
2014-06-12 20:58:37 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:37 -0400: Checking extents overflow file.
2014-06-12 20:58:37 -0400: Checking catalog file.
2014-06-12 20:58:59 -0400: Checking multi-linked files.
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
2014-06-12 20:59:30 -0400: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
2014-06-12 20:59:30 -0400:
2014-06-12 20:59:30 -0400: Disk Utility stopped verifying “Macintosh HD”: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
2014-06-12 20:59:30 -0400:

I'm having a similar problem with my G4 Desktop.
I have a 2nd internal hard drive and 2 FW Drives.
None of them are able to be verified or repaired using DU.
I get the following message: "Verify volume failed with error Could not unmount disk." And then some message about "make sure that all your files are closed."
I tried soft-booting by holding the shift-key down just as a trouble-shooting idea and I was able to verify and the drives were working well. However, when I restarted in normal mode I was not able to verify or repair.
What is my G4's problem? Why does it need to use that secondary drive in order to operate? What do I need to do to fix it?
Any suggestions?
G4 Dual 1.42 Mac OS X (10.4.6) 1 Gig Ram / 2 Internal Hard Drives

No permission to copy file (to NAS with AFP support) - extended attributes?

For certain files that I copy from one of my drives to the NAS here (Synology 206j), ever since upgrading to Snow Leopard, Finder's behaviour has changed. It will simply refuse to copy the file, stating that "The operation can’t be completed because you don’t have permission to access some of the items."
The source is an external USB drive in Mac OS Extended format, I do have full permissions on the files and in any case the drive is set to ignore ownership.
The target is, like most NASes, in EXT3 format. It's sharing via its own AFP implementation.
I'd have tried repairing permissions, but for whatever reason, it's greyed out on my external drives. Since then I've figured that it was probably not that anyway, which will become apparent:
I tried copying the file via the terminal and it actually worked, but also gave an error: "cp: myfile: could not copy extended attributes to /Volumes/media backup/myfile: Operation not permitted"
This suggests to me that, as expected, the target volume doesn't support extended attributes. But rather than popping up with the message that Leopard did (something along the lines of "your target volume doesn't support extended attributes so your file's metadata may be lost, do you wish to continue") it just aborts instead.
I'm not sure if this is a Snow Leopard problem or a change that Synology need to catch up with. A workaround is to compress the file to ZIP first.
Thought I'd mention it here before trying to report it as a bug somewhere. Anyone else having similar issues, either with a NAS or some other storage, in which case please specify?
Message was edited by: Cloudane

Thanks guys, yeah I've been monitoring the netatalk mailing list myself: they're onto the same problem, have come to the same conclusions about it being Extended Attributes and have much better proof of such than I
It looks like they're currently debating the best way to fix it (pretending to support EAs but sending them to a black hole being the quick and dirty way, but I suspect they'll go for implementation)
It'll be a while for sure, but the Synology guys are very good with Mac support so I'm sure they'll apply the update fairly quickly once the netatalk crew get something public. FWIW, I did detect a certain sense of urgency from the netatalk discussions.
Although it's essentially answered, I'll leave the question marked as unanswered in case Apple come up with a better one
Message was edited by: Cloudane

Display non extended attribute in a Custom Report

Hi,
Is it possible to query external attributes (that are not set as extended attributes) in a user report ?
I read in this forum that reports are just meant to query IDM repository, is it still true ?
Thanks,
Ben

Hello Sandra,
Thanks for your reply, but eventhen it fails to load the pdf. Is ADS required to be installed for this?
Can I just pass the pdf_fsize imported from CONVERT_OTF which is of type i.
CALL FUNCTION 'CONVERT_OTF'
    EXPORTING
      FORMAT                = 'PDF'
    IMPORTING
      BIN_FILESIZE          = PDF_FSIZE
bin_file              = pdfxstring
    TABLES
      OTF                   = L_JOB_OUTPUT_INFO-OTFDATA
      LINES                 = LT_PDF
    EXCEPTIONS
      ERR_MAX_LINEWIDTH     = 1
      ERR_FORMAT            = 2
      ERR_CONV_NOT_POSSIBLE = 3
      OTHERS                = 4.
CALL METHOD G_HTML_CONTROL->LOAD_DATA(
     EXPORTING
       TYPE         = 'application' "'text' " 'application'
       SUBTYPE      = 'pdf' "'html' "'pdf'
       size           = PDF_FSIZE
     IMPORTING
       ASSIGNED_URL         = lv_URL
     CHANGING
       DATA_TABLE           = LT_DATA "i_html "LT_DATA
     EXCEPTIONS
       DP_INVALID_PARAMETER = 1
       DP_ERROR_GENERAL     = 2
       CNTL_ERROR           = 3
       OTHERS               = 4 ).
Thanks,
Jaya.

To change the approval limit for Extended attribute PO Value limits

Hi,
We are on SRM 4.0, in PPOMA_BBP for a local purchasing organisation we want to change the approval limit let us say from 100 to 50 but the system is presenting this field as non editable( In stabdard values sub screen)
In Extended attribute tab in organisation structure after selecting the PO Value limits in SRM 4.0 we see two sub screens
a) Standard values
b) Local values
We want to change the approval limit in standard values sub screen from 1000 to 500, which system is presenting as noneditable.
Regrds
Vivek

Hi
Refer these links.
http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/fa/fa7d3cb7f58910e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/7f/0fea380bfe6161e10000000a11402f/frameset.htm
Incase it does not helps, pls let me know.
Regards
- Atul

Queryable Extended Attributes not Queryable

Similar Messages

Maybe you are looking for