This content has been marked as final. Show 3 replies
For the most part, category functionality does allow org-specific categories and module specific categories.
1. If you define the category set with control level at "Org Level", then for a given item, you can assign different categories for that category set in diff. orgs.
2. You can do (kinda) module specific categories as follows
a. Define different cateogry flex structures - say, one is called SALES and has 1 segment and the other one is called INVENTORY and has 2 segments
b. Define 2 different value sets for these structures and create valid combinations for these 2 value sets - e.g. SALES has MISC, BRONZE, SILVER and GOLD.
And INVENTORY has MISC.MISC, METAL.BRACKET, METAL.CABINET etc.
3. Use existing Category sets or define new category sets . Enter default category for these category sets if needed.
4. Define Default Category sets for different functional areas
5. Now, when you define items, you can have a different category for INVENTORY and a different category for the SALES.
6. As an added benefit, if an item is not an Salable item (e.g. a phantom item or a bulk item), Oracle will not assign the SALES category to it. Similarly, only INVENTORY items will get the INVENTORY category during creation.
Hope this answers your question.
When we try changing the default Category Set for Purchasing we get this message:
'Purchasing default category set cannot be modified as records exist in purchasing tables that refer to the old category set and the flex structures do not match for the old
and new category set.'
I am wondering that this is because we have transactions that refer to the old Category Set.
You need to make sure that the categories assigned to the old category set are also present in the new category set.