Extended Attributes and Custom Sections

Hi,
When we update formulation specifications we are finding that the extended attributes and custom sections are not automatically updating in the ingredient output. Is this how the system is designed? Is it possible to get the ingredient outputs to update automatically?
Thanks.

Hey Belinda,
Can you provide a more detailed scenario of what you are trying to accomplish?
For example,
If extended attribute "Brix" exists on the raw material specification (in the simple extended attributes grid or inside a custom section) and is tagged as "distinct" and "Is Design Attribute" on the Extended Attribute template in ADMN then anytime you use that raw material in a formulation "Brix" will appear on the Ext Data tab > Extended Attributes section of the output popup. When multiple raw materials contain the "Brix" extended attribute then the Brix value displayed on the output popup will be calculated by the system.
A few key points that may be causing your problem:
1. Custom Sections on the raw material are not automatically pulled and placed on the output popup. Only distinct attributes are pulled out and placed in the simple attributes grid on the output popup.
2. Custom data is not pulled from raw materials and placed onto the formulation specification > ext data tab. Calculation of theoretical values only occurs on the output popup
3. When an input is used inside a formulation we take a snapshot of that material, this allows you to perform "what if" scenarios. If changes are made to the raw material (for example an extended attribute was added or a nutrient value was edited), the formulation specification must be refreshed so it will pull the new updated values.
Version 6.1.0.x allows for specification templates that will help with the auto creation of custom data on the formulation specification, output popup and output material specification.
Thanks
Kelly
Edited by: user754372 on Oct 16, 2012 10:12 AM

Similar Messages

Extend material and customer to other sales areas

can u please let me know?
How to extend material and customer to other sales areas? To extend material one plant to another plant what are the configuration you done in your project?

<b>To Extend Customer master: T.code - XD01:</b>
In XD01, enter Account Group, Customer Code, Company Code, Sales Organization, Distribution Channel & Divission. Also ensure to maintain reference Customer, reference Company Code, reference Sales Organization, reference Distribution Channel & reference Division --> Enter. Most of the fields will be copied by default, but some fields will not be copied & they have to be maintained in the same manner how we create a new customer.
<b>To Extend Material Master: T.Code - MM01:</b>
In MM01, Enter the Material Code & reference Material Code --> Enter.
Select the Tab pages to be maintained & go to organization data & maintain the details like Delivering Plant & Reference plant, Storage location & reference storage location, Sales Organization & reference Sales Organization, Distribution Channel & reference Distribution channel & so on ... --> Enter. Most of the fields will be copied by default, but some fields will not be copied & they have to be maintained in the same manner how we create a new material.
Regards,
Rajesh Banka
reward point if helpful.

Update marketing attribute and customer master data via Survey Response

Hi,
I am creating a marketing survey. I have come to a point where I am able to get the reponses posted by the business partners.
Now I would like to update the BP's directly when they respond. The challenge here is I want to update both Marketing attribute and Customer master.
Is this possible with standard function modules. I am using version 4.0. Please let me know.
Regards,
Hemanth

Hello Hemanth,
Check my last response in the below thread, it could be a reason.
update marketing attributes in BP via survey
Thanks
Raja Pamireddy
CRM Marketing Forum Moderator.

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

Backup all metadata, custom icons, ACLs, extended attributes?

As a programming project I am looking at backing up absolutely everything associated with files and directories so that it can be restored perfectly. This would include associated metadata, resource fork, custom icon, permissions, access control list, extended attributes, and probably stuff I don't even know exists. Since this is just an experiment, I will be using a scripting language. Performance is not an issue so I'm willing to make system calls to gather the information.
Is there a one-stop solution or would I need to use a mix of command line tools to gather this data?
I've read up a bit about xattr, GetFileInfo/SetFile but I hope there's an easier and/or more comprehensive way. I've tried Googling some of this, but this presupposed I even know what to search for. I'm guessing I'm only getting partial information.
Can anyone point me to the definitive procedure to backup and restore OS X files in all their glory? The script would need to run automatically with admin or root privileges to access everything.
Many thanks.

Doesn't sound like there is any corruption going on to me. It may change the date modified, but that should be expected since you modified the file.

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

Can rsync filter on extended attributes?

Hi there,
I've been using rsync for quite a while now to perform various backups on my network, and it's been working without issue.
What I'm wondering today is if it's possible to create an rsync job that can filter on the colour label value of a folder? Bascially I'd like a job that essentially does
"IF this folder IS red OR orange THEN rsync it"
I've google for a while now and while I see that the -E filter preserves extended attributes, and the filter command can filter on file/folder name attributes, I can't seem to figure out a way to filter based on extended attributes.
Is there a way?
...Mike

This is not going to be pretty.
bash doesn't look to have a direct path into Finder's sort-of-private extended attribute information, save via some "creativity" involving xargs and xattr.
There are also paths into the extended attributes via Perl and via [Python xattr calls|http://www.entropy.ch/blog/Developer>.
Invoking osascript to script Finder via AppleScript can be be a path.
I'd probably [customize some C code|http://www.mactech.com/articles/mactech/Vol.21/21.05/ACLs/index.html] to fetch the attributes, and call that from within the bash script. (These APIs are documented, if you're comfortable coding in C.)
The "sneaky" or "clever" approach would be a customized rsync; tweak the file selection logic to do what you want.
Have a look at [updating rsync 3.0|http://patternbuffer.wordpress.com/2008/01/04/rsync-30-looking-very-promisi ng> and (for testing) the [backup bouncer|http://www.n8gray.org/code/backup-bouncer> tool.
But none of this is particularly pretty.

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

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

User Error Needs Help Correcting - Repeatable Tag on Custom Section Attribute

OK, I have v.6111. Today I am manually putting the supplier_eq_create tag on all the the existing attributes in our custom sections so suppliers can add them when we send eQs. Unfortuately, I accidently clicked on the Repeatable tag instead of Supplier_EQ_Create in a couple of instances in our Export/Staging Environment. When I try to remove the Repeatable tag, I get the error that says " row's Repeatable status cannot be altered after the row has been activated" ... we have not actually used the repeatable functionality of the tag. I need to know how I can remove this tag from active attributes due to human error before I import to PROD. Can the forum help me?
Best, Beckie

Hi Beckie,
As long as you are sure that no-one has consume this you can remove this tag with a database script.
As with every script make sure that you backup your data.
With the following script you can find the rows that contain repeatable tag for a particular section template
select rowTemplate.* from eaSectionDynamicTagJoins rowTTagjoin
inner join commonEARowTemplate rowTemplate on rowTemplate.pkid = rowTTagjoin.fkEAS
inner join commonLookups tag on tag.pkid = rowTTagjoin.fkTag
inner join commonEASectionTemplate sectionTemplate on sectionTemplate.pkid = rowTemplate.fkSectionTemplate
where tag.Name = 'Repeatable' and langID = 0 and Category = 'EASRowDynamicTag'
and sectionTemplate.id = '<custom section id>';
Tags are linked to custom section row templates using eaSectionDynamicTagJoins table.
You can remove the tag from a specific row using the following script
delete from eaSectionDynamicTagJoins
where fkEAS = '<pkid of the row>';
Hope this helps. Let me know if you have any questions,
Dmitriy

Custom report Extended Attribute

Hi,
On my user selection screen I just need a multiple selection box and user related data needs to be populated in it, can anybody guide me on this.
Thanx

Open BPE --
click File - >
--> OpenRepository Object
---> Forms
--->EndUserMenu
you can have a look at EndUserMenu
if you want to display custom forms then you need
login as configurator to administrator module
Click configure Tab
--->Forms and Process Mapping
you can find EndUserMenu
change the name of the EndUserMenu to your form name(should be uploaded to the IDM)
for adding attributes to your User Object
login to your http:\\localhost:8080\idm\debug pages then select
ListObjects -->configuraton
from the list of values select the User Extended Attributes for edit
then you can add your Extended Attributes here. eg PassportNo
<List>
<String>firstname</String>
<String>PassportNo</String>
</List>
</List>

Where to configure extended attributes (for cases and alerts)

Hi,
Re. http://docs.oracle.com/cd/E48549_01/index.htm (referred to by the Online Help under Applications > Case Management > Case Management concepts > Extended attribute) please can you advise where one should make the Configuration changes described on the Windows platform.
This document says "The complete set of Case Management extended attributes that are used on an Oracle Enterprise Data Quality (EDQ) server are configured in a file named flags.xml in the oedq_localhome/casemanagement directory. This file must be modified to add new extended attributes"
On my Windows installation I do not have that flags.xml file under C:\ProgramData\Oracle\Enterprise Data Quality\oedq_local_home\casemanagement
I do however have the file under C:\ProgramData\Oracle\Enterprise Data Quality\oedq_home\casemanagement however I am not able to modify it.
Please could you confirm how to proceed.
Also, generally what is the usage of the oedq_local_home and oedq_home directories.
Thanks, Nik

Hi Nik,
From section 1.4.2 of the install guide.
https://docs.oracle.com/middleware/1213/edq/DQINS/planning.htm#DQINS5205
EDQ Configuration Directories
EDQ requires two configuration directories, which are separate from the EDQ Home (installation) directory that contains the program files. The configuration directories are:
The base configuration directory: This directory contains default configuration data. Once EDQ is installed, the files in the base configuration directory must not be altered, renamed, or moved.
The local configuration directory: This directory contains overrides to the default configuration. EDQ looks for overrides in this directory first, before looking in the base configuration directory. Files in the local configuration directory can be modified to customize or extend EDQ.
The names and locations of the configuration directories are as follows:
If you are using Oracle WebLogic Server, the Oracle installation wizard automatically creates and populates the configuration directories in the EDQ domain with the names of oedq.home (base configuration directory) and oedq.local.home (local configuration directory). An example installation path is: WLS_HOME/user_projects/domains/edq_domain/edq/oedq.home
WLS_HOME/user_projects/domains/edq_domain/edq/oedq.local.home
If you are using Apache Tomcat, you create the configuration directories manually in any location, with any names, and the configuration utility will populate them. You are prompted to create the directories during the installation instructions.
Just copy flags.xml from your oedq.home casemanagement folder to your oedq.local.home casemanagement folder and edit the file accordingly.
thanks,
Nick

Is there a recommended limit on the number of custom sections and the cells per table so that there are no performance issues with the UI?

Is there a recommended limit on the number of custom sections and the cells per table so that there are no performance issues with the UI?

Thanks Kelly,
The answers would be the following:
1200 cells per custom section (NEW COUNT), and up to 30 custom sections per spec.
Assuming all will be populated, and this would apply to all final material specs in the system which could be ~25% of all material specs.
The cells will be numeric, free text, drop downs, and some calculated numeric.
Are we reaching the limits for UI performance?
Thanks

Problem with setting custom attribute and it being searchable

I'm having an issue with setting a custom attribute and having it be searchable using Portal 10.1.4. The situation that we have is that we initially added a bunch of files to Oracle Portal using webdrive. Later on, we decided that we needed another custom attribute called "Pinned Item" that will be used for searching (boolean value) and gave it a default value of false. The attribute was then added to the "File" item type in the "Shared Objects" group.
It appears that since this attribute wasn't initially available on the file object, we couldn't search on it so we decided to set it programatically. First, I tried using wwsbr.set_attribute but it errored out seemingly because the value wasn't set in the first place. If I set a value first by using the web front end, I could then use the set_attribute procedure.
So, I moved on to using wwsbr_api.modify_item and it appears to set it (although everything is being set to false until I changed it to "text" instead of "boolean" which is OK because that's what I wanted anyway... see metalink bug 390618.1). I'm using the method outlined in metalink doc 413079.1. When I do set it to a "1", and edit the item the check box is checked indicating that it is set correctly. And if I just click "OK" to save the attributes after I open it everything works like it should.
However, the advanced search (and custom search portlet) and the search APIs are not picking it up. I'm not sure if I'm hitting Metalink bug ID 5592472 or not as that's using the "set_attribute" procedure instead of the modify_item procedure. And their "workaround" of setting the attribute in the UI isn't really feasible for a couple thousand files.
So far I've tried the following things to get it working:
1. I am calling wwpro_api_invalidation.execute_cache_invalidation
2. I have executed wwv_context.sync
3. I cleared the page group cache
4. I invalidated all of the web cache
Does anyone else have any other suggestions?

I'm having an issue with setting a custom attribute and having it be searchable using Portal 10.1.4. The situation that we have is that we initially added a bunch of files to Oracle Portal using webdrive. Later on, we decided that we needed another custom attribute called "Pinned Item" that will be used for searching (boolean value) and gave it a default value of false. The attribute was then added to the "File" item type in the "Shared Objects" group.
It appears that since this attribute wasn't initially available on the file object, we couldn't search on it so we decided to set it programatically. First, I tried using wwsbr.set_attribute but it errored out seemingly because the value wasn't set in the first place. If I set a value first by using the web front end, I could then use the set_attribute procedure.
So, I moved on to using wwsbr_api.modify_item and it appears to set it (although everything is being set to false until I changed it to "text" instead of "boolean" which is OK because that's what I wanted anyway... see metalink bug 390618.1). I'm using the method outlined in metalink doc 413079.1. When I do set it to a "1", and edit the item the check box is checked indicating that it is set correctly. And if I just click "OK" to save the attributes after I open it everything works like it should.
However, the advanced search (and custom search portlet) and the search APIs are not picking it up. I'm not sure if I'm hitting Metalink bug ID 5592472 or not as that's using the "set_attribute" procedure instead of the modify_item procedure. And their "workaround" of setting the attribute in the UI isn't really feasible for a couple thousand files.
So far I've tried the following things to get it working:
1. I am calling wwpro_api_invalidation.execute_cache_invalidation
2. I have executed wwv_context.sync
3. I cleared the page group cache
4. I invalidated all of the web cache
Does anyone else have any other suggestions?

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

Extended Attributes and Custom Sections

Similar Messages

Maybe you are looking for