APC Search Criteria And Results Format: How Is Customization Code Generated?
(Doc ID 857692.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Product Hub - Version 18.104.22.168 to 22.214.171.124 [Release 11.5]
Information in this document applies to any platform.
This is a consultative question about customizations for Advanced Product Catalog (APC) and Product Lifecycle Management (PLM).
In a company, Users currently use Advanced Product Catalog to allow technicians to create items only based on product catalogs and their own defined rules. For each catalog a set of User-Defined Attributes (UDAs) is created in order to determinate technical features that have to be specified for any item within this catalog.
Using a lot of UDAs, Users may need to perform many customizations, such as defining Search Criteria based on UDAs and Results Format showing the values of the UDA set for each item retrieved.
APC and PLM allows creating them manually in the "Item Catalog Category" window, but since the number of catalogs increases quickly you would like to perform actions to create them automatically.
Is there a tool for this functionality already provided by standard product ?
If Users should create this functionality by new with a custom procedure (using PL-SQL, for example), you need some technical information about how to populate tables. Users see that tables involved are mainly AK_CUSTOMIZATIONS, AK_CUSTOMIZATIONS_TL and EGO_CUSTOMIZATION_EXT. You encountered problems to understand what's the rule to generate the CUSTOMIZATION_CODE (it's a key-field for these tables, so Users would like to understand it).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document