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

Similar Messages

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

Increase max limit of extended attribute characters

I need to be able to save more then 150 characters in an extended attribute. Where can this be configured to allow up to 200 characters?

Hello, we needed to do this for EA Free text field and expand to allow 20000 chars. Oracle gave us this solution:
/****** Object: Index [PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5]    Script Date: 10/12/2011 13:18:33 ******/
IF EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[commonExtendedAttributeText]') AND name = N'PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5')
DROP INDEX [PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5] ON [dbo].[commonExtendedAttributeText] WITH ( ONLINE = OFF )
GO
--Update the database table:
ALTER TABLE commonExtendedAttributeText
ALTER COLUMN AttributeText NVARCHAR(max);
--Add back the index:
/****** Object: Index [PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5]    Script Date: 10/12/2011 13:18:33 ******/
IF NOT EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[commonExtendedAttributeText]') AND name = N'PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5')
CREATE NONCLUSTERED INDEX [PLM4P_COMMONEXTENDEDATTRIBUTETEXT_5] ON [dbo].[commonExtendedAttributeText]
       [fkOwner] ASC,
       [pkid] ASC,
       [fkExtendedAttributeType] ASC,
       [fkRoot] ASC,
       [Comments] ASC
INCLUDE ( [AttributeText]) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
GO
--Update the UI control to allow for the length change:
--Modify \Web\WebCommon\Controls\ExtendedAttributesControls\ExtendedAttributeTextRow.ascx
--By updating the maxlen attribute of the <asp:TextBox to your max value. Eg: … maxlen="8000" />
Hope that helps!

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

Outsmarted by extended attributes

Got my new computer. No clue as to how it happened but in the Finder, /Users/jv doesn't even show up so you can't navigate to it (and consequently, to its Public and Public/Drop Box folders) anymore. In Terminal, /Users/jv directory has an extended attribute "@" appended to the directory "ls -l" output. Found a thread that indicated removexttr command would remove extended attributes. I get "command not found" when I type "removexttr /Users/jv". How do I make /Users/jv behave like all the other /User folders (i.e., be visible and navigable in Finder)?
Equally concerned about a bunch of stuff that has a "+" appended to it (Desktop folder, Documents folder, etc., etc., even the Public folder). How do I make this crap go away?

Where did you see this "removexttr" command? I don't think there is such a thing.
There isn't. When it said 'no such command' I searched through the bowels of the usual suspects, /bin, /sbin, /usr/bin, /usr/sbin, which, naturally, came up empty. Hence, one of the catalysts leading up to my posting here. "removexttr" was mentioned in some post here in, I believe, this forum. Of course, now, despite multiple combinations of search terms, I can't find it. But, it's not important. The poster must have just been writing in a loose vernacular prose.
Being impatient, and also since the new mac didn't have much installed on it yet, nor were the user accounts customized too much yet, I took the "sledgehammer" problem solving approach and reformatted and reinstalled the OS and recreated the accounts, before having seen all these new posts in this thread. Figures... So, anyways, the problem went away, even though it was via the "sledgehammer" approach. I haven't reinstalled a copy of my .ssh directory with dsa keypair and authorized_keys2 (dsa keypairs and .ssh were mentioned in that nebulous post that I alluded to earlier), so who knows? The problem may rear its ugly head once again if/when I do. These new posts, particularly yours here, may very well indeed come to my rescue.
Thanks (to all of you) for taking the time to respond.

Maintain attributes for Approval Limit

Hello friends,
I am Uptaing the USER attributes for Approval Limit, APPRV_LIM.
I am using the FM - BBP_UPDATE_ATTRIBUTES.
I am confused how would I pass the value and the format.
I am passing 123 USD, Its Updating but when I see in T-CODE, pposa_bbp, I see some diffrent value being uploaded.
I mean 123 is converted to 31003200330.02
Any Idea as whats the issue and how should I handle this
Ster.

Hi
What is the input file format you used?
and check any currency definition in CUR (currency) attribute in PPOMA_BBP.
BR
Muthu

Make user extended attribute available on the user report

Hi,
We have created a few user extended attributes for the client. The quyestion is how to make them available for select in a user report. Currently we configured a user report for approvers "approver report" and save the XML as TaskTemplate. How can I modify the xml to display user extended attributes? I tried the following but it did not work:
In the task template xml, add the attribute (e.g., department) into
<Attribute name='attrMapField'>
<Map>
<MapEntry key='attributes.department' value='Department'>
</Map>
</Attribute>
<Attribute name='attrsToDisplay'>
<List>
<String>attributes.department</String>
</List>
</Attribute>
Thank you.

We will need to edit the TaskDefinition object named �User Report� with the id
�#ID#TaskDefinition:UserSummary�.
1) Insert the following xml directly above the field named �queryAttr.MemberObjectGroups.enabled�:
<Field name='queryAttr.employeeId.enabled'>
<Display class='Checkbox'/>
</Field>
<Field name='queryAttr.employeeId.operator'>
<Display class='Select'>
<Property name='title' value='Report only users whose employeeId '/>
<Property name='noNewRow' value='true'/>
<Property name='nullLabel' value='Please Select'/>
<Property name='valueMap'>
<ref>conditionsList</ref>
</Property>
</Display>
<Expansion>
<cond>
<eq>
<ref>queryAttr.employeeId.enabled</ref>
<s>true</s>
</eq>
<ref>queryAttr.employeeId.operator</ref>
<null/>
</cond>
</Expansion>
</Field>
<Field name='queryAttr.employeeId.value'>
<Display class='Text'>
<Property name='noNewRow' value='true'/>
</Display>
<Expansion>
<cond>
<eq>
<ref>queryAttr.employeeId.enabled</ref>
<s>true</s>
</eq>
<ref>queryAttr.employeeId.value</ref>
<null/>
</cond>
</Expansion>
</Field>
2) Inside of the defvar named �attrMap� you will need to insert the following text:
<MapEntry key='attributes.employeeId' value='Employee ID'/>
3) Save the modifications.
4) Check the "User Report" your attr will be available

Impact of deleting 'Prod Cat' from extended attributes on the SC approval

Hi All,
I have one question regarding 'Product Categories' in extended attributes.
We have defined 'Product Categories' as extended attributes at the company level.
The users are able to create SC with the Product Categories which are assigned as Ext attributes of the company.
We wanted to remove one product category from the extended attributes of the company, because we did not want the users to create SC for that product category anymore.
However, the users had already created SC using that Product category and the SC are in approval process.
I want to know that if we remove that product category from the extended attributes, will it affect the existing SC (under approval process) which were created using that product category.
Will there be a problem in SC approval & SRM PO creation, if that product category is removed.
Please help.
Regards,
Ruchika

Hello Ruchika,
As written by Sanjeev, i don't think it will impact flow process for SC or PO.
But, to be sure, make some tests on your development environment:
- create a SC with Product Category to test,
- delete this Product Category from tab "Extended attributes",
- approve/reject the SC,
- when SC approval WF is over, try with a Purchaser from Purchasing Group having responsability for this Product Category to modify PO (if authorized by user profil or customizing),
- order the PO,
- approve/refuse the PO,
- make modifications on PO approved (if authorized by user profil or customizing).
Nevetheless, in case of SC rejection, check if SC creator can delete the SC: maybe not due to Product Category deletion.
Regards.
Laurent.

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.

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

How to get the approval limit of a user

Hi,
Is there any table to get the value of approval limit of a user?
Other than using the FM "BBP_BW_GET_APPR_LIMIT"are there any ways to get the approval limit of a particular user provided his username is given?

Hi Sowmya,
You can use the FM 'BBP_READ_ATTRIBUTES'
Pass the username in IV_USER
IV_SCENARIO will have the value BBP
and the value for IV_ATTR_SINGLE can be taken from the table T77OMATTR.
You can also go thorugh the following link for getting help to call this FM:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/codeSample2-Reporttodisplayuserattributes
Thanks,
Pradeep

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.)

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...

User Extended Attribute maintenance through ActiveSync

Following is happening in the activeSync process.
There is an existing user in IDM with some defined attributes (as per the extended attrs pre-defined).
If any of the user attributes does not have a value in the authoritative source and the user is processed via activeSync then whatever attrs does not hold a value in authoritative source that attr is completely deleted from the userObject xml in IDM
It does not keep a trace in the userObject.
Before the ActiveSync update process UserOBject has the following value.
<Attribute name='Manager' type='string' value='Smith'/>
If in the authoritative source for this user the manager becomes null then
this entire attribute is removed from the xml.
question here is :Is this a normal behaviour w.r.t ActiveSync Process?
Should it not leave the attr trace in UserObject xml in the following way.
<Attribute name='Manager' type='string' >
</Attribute>
If anyone can share their experience in this that would really help.

Any one has noticed this issue in your system? Please help.
Thanks,
Arun

How to Update Extended Attributes For the Users in SRM Organization?

Hi,
I am using 'BBP_UPDATE_ATTRIBUTES' function module to load the Default Attributes for the users in a custom program. I am able to update many attributes like company code, Movement type, catalog id, material usage, shop on behalf of and address ship to. But I am having problem updating extended attributes Plants(Attribute ID 'WRK') and Storage Locations (Attribute ID 'LAG').
Storage location and Plants has many values. Can anyone have experienced this problem before. I appreciate any help I get. I debugged enough and not able to find any other function module to do this.
Thanks and Regards,
Sreeni..

Hi Sreeni,
I'm stuck up in the same problem. Did you get any solution for this? If yes please provide the same.
Regards,
Gajendra
Message was edited by: Gajendra Bhatt

User's Approval Limit in Extended Attributes

Similar Messages

Maybe you are looking for