Query Based Classification Issue

Hi all,
I have got a scenario where I have to classify some project related documents based on the Project Name, Document Type, Module etc. I believe the best way to do this is using Query Based Taxonomies.
But, If I dont have a naming template for the documents and cant assign predefined propertied to documents, what is the best alternative to get the classification done?
Thanks and Regards,
Ajay.

HI
r u trying to define properties at the document level then it doesnot works because metadata of KM and metadata of document are different.
u can define pre-defined properties at the folder level in KM.
why dont you use example based classification as u train ur taxonomies with example and it inturn index furher document automatically based on your example document.
But it still deponds upon individual requirements.
Regards,
Vijay.

Similar Messages

Query Based Classification & custom properties

Hi all,
Is there a way to build a query based classification with custom properties?
Regards,
Orlando Covault

Hi Frank,
Very cool documentation, Ill give you points for that but my question remains and I think that the answer is no... Theres no way that I could use custom properties in the Query base classification I am waiting for my environment to run some test, but if some one have another comment on this subject Ill appreciated it.
Regards,
Orlando Covault
P.D. I have another question about the taxonomies and is about changes in the taxonomy, What happens if some moment I need to change a Taxonomy, is this supported and completed functional? I mean the classification remains and work fine or is not recommended?

Tip on Using "Folder" for performing Query Based Classification

In setting up a TREX taxonomy for one of our intranet sites we concluded that the folder structure used by the web developers really helped classify the documents at a higher than an 80% level. It seems that in many cases, the intranet, outlook public folders, or LAN folders will be organized such that the title of the folder is very valuable in classifying what is in it.
After many searches and false starts, I found something that is so simple and elegant, I had to share it here.
In the Taxonomy Query Builder there is a property "Folder". Unlike the property "Content" which has a "contains" operator, this one is a "Is" or "Is Not" so it seemed like it might be hard to use.
What I found is that it automatically put an * at the end of whatever we entered and if we put an * in the beginning, it seemed to find the folder consistently.
So for a three level taxonomy such as:
-- Business
Customer Support
   Product information
where you have folders /Business/CustSupport/ProdInfo you use a three level taxonomy.
For the business I put in a Query:
-- Folder is_not PassTheIsNotTestSoEverythingIsClassified
That meant everything was included at the root level no matter what. (i.e. I didn't want 'documents to be classified' to contain anything.)
The query for the Customer Support level of the taxonomy was:
   -- Folder is *CustSupport
which pulls in any document that is in the folder that contains CustSupport
The query for the next level was:
   -- Folder is *ProdInfo
which pulls in any document that is in the folder that contains ProdInfo
As the classification engine works, items that pass all three test are put in the most detailed folder. You can have as many taxonomy nodes at any level as you need and if they don't pass any, they are kept at the root of last level they did pass.
You end up with an amazingly simple classification scheme that can handle a big taxonomy. To the extent your folders are not organized like your taxonomy or are not related logically, they you need to add in other queries using the document contents, or other fields available for indexing.   This is where the 80-20 rule kicks in, you still need to work hard to get that last 20%.
Let me know if this approach helps anyone.

HI
r u trying to define properties at the document level then it doesnot works because metadata of KM and metadata of document are different.
u can define pre-defined properties at the folder level in KM.
why dont you use example based classification as u train ur taxonomies with example and it inturn index furher document automatically based on your example document.
But it still deponds upon individual requirements.
Regards,
Vijay.

Documents in Query-based Taxonomy are not Autoindexing

Hello experts!
I am on EP6.14 with Trex 6. I have a repository with a query-based taxonomy on it and is also part of a regular search index. I have autoclassification on.
On each document I have a couple of properties that are used to match documents in queries in my taxonomy. On the initial set-up and load, everything worked great. Documents went right where they were supposed to. But sometime after we released this to the business, the documents no longer automatically index. If I change a document property or set up a new one, it finds the category but leaves them as "suggested." You then have to go in and accept those suggestions to get the document to the right taxonomy. In short, it acts as if autoclassification is off. I have noticed that the Classification index does not submit a new document if I change a property but the search index does. Not sure if that is applicable but I would think both should do that since it is a change.
I did some research and found that synchronization issues or new folders could cause this problem but I have synchronized with no success. Also, state management is not on for the repository.
Is there any reason why autoclassification would stop on its own? What can I do to get it back on?
Thanks-
J
Many points given for helpful answers!

Hi Frederick-
Thanks for your response-
We have a single CM DB repository. There is a search only index at the root folder and classification index on a folder below the root. Normally, we don't overlap but we wanted only the folders in the lower folder to be part of the taxonomy. I suppose we could just rule out the other documents by not having them match any queries but this way it was guaranteed.
THe search and classifications are working (aren't throwing errors) but like I said, I would think that both would have to push the document through the queue. But I'm only seeing the search index do that. Now if I go and accept the recommended categories, then it goes into the queue for the Classification index.
J

Query based taxonomy from scratch gives NoSuchMethodError...

I'm trying to create a query based taxonomy following the instuctions specified in the help docs: KM Platform -> Admin Guide -> Content Mgmt -> Taxonomies and Classification -> Creating a QBT -> from scratch. I created an index on a newly created (hence empty) folder in the 'documents' repository. So, essentially, the data source points to that folder. Also, I selected 'TREX Classification' on the 'Service' drop-down while creating the index. I left the crwler profile as blank. Then I went on to create a new 'Query Based Taxonomy'. I was able to create it alright, but as soon as I click on it to add folder and the such, I get this error:
java.lang.NoSuchMethodError
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getDocumentTaxRMRids(TaxonomyNamespaceManager.java:1876)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getTaxonomyClassResources(TaxonomyNamespaceManager.java:1831)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.addChildDocuments(TaxonomyNamespaceManager.java:1942)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getChildren(TaxonomyNamespaceManager.java:368)
     at com.sapportals.wcm.repository.CollectionImpl.internalGetChildren(CollectionImpl.java:966)
     at com.sapportals.wcm.repository.CollectionImpl.getChildren(CollectionImpl.java:179)
Any help in solving this is highly apprecaited.
We run EP6 SP2.
I did NOT create a 'crawler profile' for this set up.
thanks,
Biju.

Hi Biju,
re. your NW'04 SP stack 4 migration intention:
NW'04 is still in ramp-up (SP stack 4 is the current shipment bundle of it) so at the current point in time, only participating ramp-up customers can use it.
A migration from EP6.0 SP2 to NW'04 will be possible (but not during the ramp-up phase).
From a Knowledge Management & Collaboration perspective, we will port most of the NW'04 SP stack 4 functions to EP6.0 SP2 as well. These functions will be shipped as EP6.0 SP2 Patch 5 (planned shipment date beginning of Q4 / 2004) so for mid-term, you can also plan to stay on EP6.0 SP2 if you have no other pressing reasons for going to NW'04 (e.g. enhanced Web AS functions).
This feature porting from NW -> EP6.0 SP2 is an 'only-once' action, however, and NetWeaver will be the release for new features in the future.
Regards,
Joerg

Query Based Taxonomy - Dynamic Creation of a Query Problem

Hi,
I'm trying to create new category nodes in a taxonomy and to assing them queries. I know how to do this, but I encountered a strange behavior. Here is the situation:
I have a string property DocumentType. When manualy creating a query, it looks like:
DocumentType CONTAINS "Some string"
But when I do the same using code I get:
DocumentType IS "Some string"
And as a result of this, the taxanomy is not working properly.
Here is the code:
     indexService =
     (IIndexService) ResourceFactory
     .getInstance()
     .getServiceFactory()
     .getService(
     IServiceTypesConst.INDEX_SERVICE);
     //        This kind of classification index offers functionality working with query based taxonomies
     qbcIndex = (IQBClassificationIndex) indexService.getIndex(indexId);
     //        Get a query folder - a query folder is a representation of a query based taxonomies category
     queryFolder = qbcIndex.getQueryFolder(RID.getRID(folder));
     //        List of IQueryEntry objects for the query folder
     queryEntryList = queryFolder.getQuery(context);
     //        Cast the IQBClassificationIndex into a ISearchIndex object
     searchIndex = (ISearchIndex) qbcIndex;
     queryEntry = searchIndex.getNewQueryEntry();
     queryEntry.setRowType(IQueryEntry.ROW_TYPE_ATTRIBUTE);
     queryEntry.setPropertyName(propertyName);
     queryEntry.setPropertyOperator(IQueryEntry.PROPERTY_OPERATOR_EQUAL);
     queryEntry.setValue(propertyValue);
     queryEntry.setTermAction(IQueryEntry.TERM_ACTION_EXACT);
     queryEntryList.add(queryEntry);
     //        Set the query for the query folder
     queryFolder.setQuery(queryEntryList, context);
     qbcIndex.updateCategoryContents("Document_Types", false, context);
Can somebody tell me what am I doing wrong please. Isn't it because of IQueryEntry.PROPERTY_OPERATOR_EQUAL? Is there any substring operator?
Thanks a lot.

Hi, Robert
In this moment, I have a problem with Query Based Taxonomy, maybe could you help me. I insert the query in to the taxonomy from code, but when i use the method
qbcIndex.updateCategoryContents("/taxonomies/borrame5/Prueba2", false, context);
I got the next exception:
#1.5#0014C210F3D1002A000001200000565B000431CC93AD5979#1180654627543#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5#0014C210F3D100310000012B0000565B000431CCC47166AB#1180655445698#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###com.sapportals.wcm.service.indexmanagement.IndexNotReadyException: Some documents are not included in this update because indexing has not been finished yet.#
#1.5#0014C210F3D100310000012C0000565B000431CCC4717417#1180655445701#System.err#sap.com/irj#System.err#dummy01#10241#####SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###     at com.sapportals.wcm.service.indexmanagement.retrieval.trex.AbstractTrexIndex.updateCategoryContents(AbstractTrexIndex.java:2493)#
I have doubt what parameters i need to pass to the method updateCategoryContents,
Let me give some information:
taxonomy:
   /taxonomies/borrame5/Prueba2
repository:
   /documents/Portal_KOF/KM/Pruebas1/Pruebas Versionamiento
classification and search index:
   borrame5
   I can't classify automatically, when i insert the query from code. When I manually insert the query from the portal, automatic classification run perfectly.
Thanks
Greetings
JARO.

Purchase register query based on down payment invoice

Hai All,
I am creating an invoice based on purchase order.The vat tax is being calculated in the downpayment. I want the vat to be displayed in the downpayment invoice as well as the a/p invoice but i m not getting it in the a/p invoice. Pls guide me with the linking of tables to get the query working. I have formatted the fields req but could not link the tables...Pls guide me with that...
Thanks & Regards,
Neela

Hi Neela,
Check the thread.
Re: Purchase register query based on down payment invoice
FROM PCH1 T0
INNER JOIN OPCH T1 ON T0.DocEntry = T1.DocEntry
INNER JOIN OSLP T2 ON T0.SlpCode = T2.SlpCode
LEFT OUTER JOIN PCH12 T3 ON T1.DocEntry = T3.DocEntry
LEFT JOIN ODPI T4 ON T1.CardCode = T4.CardCode
INNER JOIN DPO1 T5 ON T0.ItemCode = T5.ItemCode
Close the thread, if issue solved.
Regards,
Madhan.

How to increase performanceof query based on Infoset?

How to increase the performance of a query based on a Infoset?
As per designing of query, all the necessary fields are placed where they are required.

Hi Akshara ,
To improve performanceof query try to remove unnecessary characteristics, attributes, or key figures ,Superfluous conditions or variables .Large InfoCubes and Complex hierarchies .Variables populated by user exits
For characteristics specify either variables or restrictions .
You can create indexes on DSO and Aggregates on cubes (if any).
Please go through the links :
http://help.sap.com/saphelp_crm40/helpdata/en/77/4a213cc534f20ae10000000a11402f/content.htm
Re: Performance of query built on infoset
Query performance issue - Infoset query
Hope you will find this helpful.
Regards,
Jaya

BEx Analyzer: User ID based performance issue

Hello Ladies and Gents,
<b>The issue:</b>
My BW team just upgraded our system to 2004s and we are experiencing an odd userid based performance issue. If we run a query from the BEx Analyzer with user ID 'A' it takes about 3min for the variable selection screen to appear. If I log into the same machine user ID 'A' was using on my user ID B the query variable selection screen appears within seconds. What could possibly cause this?
<b>What we know so far:</b>
1. Investigated the security roles, seems like that is not the issue.
2. It is PC client independent. Two different user IDs(A and B) on the same machine running the same query in the same way (clicking through the BEx browser) produces different response times for the appearance of the variable selection screen.
Points will be rewarded and help will be greatly appreciated!

User specific personalization is retrieved before displaying the input variables. That might be a possibility, but hard to see it making such a difference. Do you always try the sequence of User A, then User B, or have you confirmed that when you start with User B, it is quick, and tehn slow whne trying User A?
Probably the best approach is to activate Trace and then logon with User A, turn trace off and print or save, then do the same thing for User B and compare. The trace will show you all the various SQL stmts and such that run as part of your trying to launch the query.
Please post back anything you learn.
Some info on Personalization for the Help pages.
Personalization in BEx
Use
This function allows users to fill variables with user-specific values, to save user-specific accesses to BI objects for the history view in the BEx Open dialog box, and to save user-specific start views for Web applications.
Integration
The personalized data is stored in different DataStore objects, according to the personalization area.
·        User-specific variable values are stored in the DataStore object 0Pers_VAR.
·        Personalized data for the history view is stored in the DataStore object 0Pers_BOD.
·        Personalized start views for the Web application are stored in the DataStore object 0Pers_WTE.

Query Region Rendering Issue between RUP4 and RUP5 Env.

Dear OAF gurus
We currently face an issue with a custom built OAF query region, where the regions works perfectly well, i.e. the page renders in a timely fashion with all its fields in one Apps environment (Dev) and then “Hangs and eventually times-out” in another environment (SysTest).
Clearly this leads us to believe that there must be an issue with the environment configuration and/or patch/product levels, namely the OAF tech-stack.
The Development Env. where this is working:
===========================================
OAF Version : 11.5.10 RUP 4.
MDS Version : 9.0.5.4.89 (build 555)
UIX Version : 2.2.24
BC4J Version: 9.0.3.13.93
The System Test Env. where this is NOT working:
===========================================
OAF Version : 11.5.10 RUP 5.
MDS Version : 9.0.5.4.89 (build 555)
UIX Version : 2.2.24.1.0
BC4J Version: 9.0.3.13.97
As you can see there are differences in Rollup Patches and OAF platform.
The System Test Environment is clearly a head of the Development environment and this is where we are facing the issue. If we patch the Development environment to the same level as the Test, then the issue will manifest itself in both environments. The client will be going live with RUP5 or higher.
The offending region is has the following structure:
The parent/root page is : XxxMyQueyRegionRN, which is a “defaultSingleColumn” Region Style with its own controller class.
Immediately under the above region there is a “query” region style child, which has the following attributes:
Construction Mode : resultBasedSearch
Include Simple Panel : False
Include Views Panel : False
Include Advanced Panel : True
Initial Panel : advanced
Show Views Panel Control: True
The above Query Region has underneath it a “table” region style, which essentially is the results table.
This table node has a number of “messageStyledText” fields under it. Each field is mapped to a VO and VO attribute.
A number of these items have their “Search Allowed” property set to True, which means that are search-able fields in the Search Panel.
There is nothing special or extraordinary about the above region and yet it renders in one environment and then hangs (i.e. the page times-out) in another. How do I know it is this specific region that causes the time-out? well when I take it out of the parent Page, the page works fine in both environments and as soon as include it, it times-out.
Has anyone encountered this issue before? Has the OAF technology changed between RUP 4 and RUP5 sufficiently, so that certain custom pages will have to be re-developed?
Any help and Guidance is appreciated.
Thanks
Patrice.

Patrick,
Check the apache log to see if contains any error or whether it lists the process which is taking so much time to lead to timeouts.
In case you have a blind query based search result table population on page rendering, try to render the page without the query execution.
--Shiv

Query based on ODS showing connection time out

Hi,
I have a query based on an ODS. The selection criteria for the query is Country which is a navigational attribute of the ODS. When i exceute the query using a country with lesser volume of data the query runs fine. But when i choose a country that has more number of records the query shows 500 connection timeout error sometimes and sometimes it runs fine for the same country.
I tried to execute the report using country as input variable - First i executed the report using a country with lesser volume of data it worked fine as usual and then i added another country with larger volume of data in the filter criteria and the old problem cropped up.
Could you please suggest a solution?
Appreciate your response.
Thanks
Ashok

Hi,
Its not recommneded to have a query on DSO which gives huge amount of data as output.
For small amount it should not be a problem.
Shift your queries to a multicube as recommended by SAP and build the multicube over the cube which loads from the DSO.
SAP recommends to create queries only on multiproviders.
If not possible then you can try to create indexes on DSO on the characteristics field which are used in filter and global selections in the query.This can improve the query performace.
But this will create performance issue while loading data to the DSO.
So you need to do a trade off.
Thanks
Ajeet

Query Based Taxonomies

Hello,
I've created successfully a query based taxonomy. I also defined the queries to the folders within the taxonomy. Now my problem is, that a document only belongs to one folder. But in some cases, that's not nice, e.g. when you want to navigate through the hierarchy.
Example:
I've got a structure like Folder F1, under that a Folder F2.
For folder F1 I defined a query: property P1 contains value V1.
For folder F2 I defined a query: property P2 contains value V2.
After updating the taxonomy it should now be possible, that documents which are classifications of folder F2 also classify to folder F1.
How to do that?
Help would be appreciated.
Best regards,
Denis

Hello Karin,
thank you for your answer. Does this mean, that a navigation through the taxonomy hierarchy is not possible (e.g. with a km navigation iView?). Taxonomies are stored in KM under /Taxonomies and I thought that a navigation with a km navigation iView is possible. But I think the real benefit of taxonomies is, that the deeper the hierarchy folder is, the more classified and smaller are the results. But when documents get only classified to more folders when the folders are on the same hierarchy level, how should a navigation be realized?
Thanks in advance.
Best regards,
Denis

Query-based taxonomy doesn't work

Hi,
I created a query-based taxonomy in the index of a folder. Then in Content Management - Classification I set the Category and query of the taxonomy. However, documents that meet the query cannot be classified into that category - they are still in Documents to Classify. It's the same with example-based taxonomy.
Am I missing something?
Thanks,
Ray

Hi Ray,
To work with this kind of taxonomy you must do:
1. Create index using classification service.
2. Create taxonomy based in query.
3. If you click in this taxonomy you can create new folders where documents will be stored (as result of classification, logical links).
4. In Content Management->Classification->Taxonomy Query Builder->choose the taxonomy created in step 2 and
create a search query for a category in a query-based taxonomy.
http://help.sap.com/saphelp_nw2004s/helpdata/en/77/49523ec744d947e10000000a114084/frameset.htm
Patricio.

Query based alerts

Hi All,
Like every company we have a situation where we buy item a and item b individually but sell as sets or stand alone as the customer requires. A major problem we have in our current system (not SAP B1) is that the min-max would never trip since it would consider the CURRENT / LIVE / OPEN Purchase orders.
I want to set up a query based alert which tells me to
1) buy item b every time I buy item a, and the quantity should be at least same or more.
2) trip min-max keeping in mind that we need as many item b as the quantity of item a + a buffer stock quantity decided by us.
Any guidance?
Thanks!!
Regards,
YP.

Hi Augusto,
We do not have any links set up for the items. Just by our business dealings, we know that item A needs to be sold with item B, but the customer can choose to buy individually also.
I want to avoid multiple part numbers for same item to cater for different scenarios. Only issue occurs when we are trying to manage the inventory levels and hence the question of query based alert.
Our customer requires us to reflect "item a" and "item b" as part numbers on invoice, so we refrain from introducing a 3rd part number which will be the sales BOM made by using item a and item b as child parts.
Hope I have clarified.
Regards,
Yash

How to deploy configuration manager client package to a query based collection

Hi
I have created one OU based collection.Now i wants to deploy client package to this collection so that the client automatically get installed,whenever a new machine added to the OU and so on to the collection.
But the issue is with configuration manager client package deployment,as we can't deploy the default configuration package to the collection(Deploy option is grayed out). For this i created a new configuration manager client package and deployed this package
to the query based collection.
Now when a new machine added to this collection,the client did not appear to deploy on this machine. Please help

If you want all the devices in the OU to get the client, you can use a Computer Startup Script to deploy it. Everybody just uses Jason's since it does everything and is well documented.
http://blog.configmgrftw.com/configmgr-client-startup-script/
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Query Based Classification Issue

Similar Messages

Maybe you are looking for