In Release 8.5, a master catalog is created when
you define a catalog organization. The master catalog is also marked
as the active selling catalog of the catalog organization.
How it affects you
Run the
automated migration processes to ensure that a master catalog and
active selling catalog are defined for the catalog organization.
Migration strategy
This section
describes the automated and manual migration processes for this functionality.
Automated migration processes
The
enhanced catalog UI functionality has the following automated processes:
- A new record is inserted into YFS_CATEGORY_DOMAIN
for each catalog organization with the following...:
- CATEGORY_DOMAIN_KEY = ORGANIZATION_CODE
- CATEGORY_DOMAIN = ORGANIZATION_CODE + ‘MasterCatalog'
- ORGANIZATION_CODE = ORGANIZATION_CODE
- SHORT_DESCRIPTION = ‘Master Catalog'
- DESCRIPTION = ‘Master Catalog for' + ORGANIZATION_CODE
- Two new records are inserted into YFS_CLASSIFICATION_PURPOSE
for each catalog organization with the following...:
- CLASSIFICATION_PURPOSE_KEY =
- System Timestamp + NEXTVAL for Oracle and DB2®
- CLASSIFICATION_PURPOSE_CODE = 'MasterCatalog'
- ORGANIZATION_CODE = ORGANIZATION_CODE
- CATEGORY_DOMAIN_KEY = CATEGORY_DOMAIN_KEY (from
step 1)
and
- CLASSIFICATION_PURPOSE_KEY =
- System Timestamp + NEXTVAL for Oracle and DB2
- CLASSIFICATION_PURPOSE_CODE = 'SellingCatalog'
- ORGANIZATION_CODE = ORGANIZATION_CODE
- CATEGORY_DOMAIN_KEY = CATEGORY_DOMAIN_KEY (from
step 1.)
Manual migration processes
None.