This document outlines the infrastructure and maintenance process for a CZ Gold Configurator system connected to Oracle EBS instances. It describes how the GoldCZ instance is used for model development and should not be refreshed from other instances. It also describes how the bill of materials (BOM) source is the Oracle Production EBS instance and how BOM/UDA data is published from GoldCZ to EBS instances for testing. Periodic purging of configurator tables is recommended in GoldCZ and Production EBS to clean up orphan records.

1. CZ Gold Concept
-Gaurav

2. Infrastructure (Configurator)
Oracle PROD EBS
(BOM Source)
Oracle EBS Test/QA
(Publication Target-BOM/UDA
upto date)
Oracle EBS DEV
(Publication Target-BOM/UDA upto
date)
CZ GOLD (GOLDCZ)
(Model Development)
Import BOM
Publish
Publish Publish
CZGOLD
•Oracle EBS Instance
•Never Refreshed
•Hosts Configurator
•Clone/Rapid Install
•Remote Links set up
PROD TEST DEV

3. Infrastructure (Configurator)
• Product Data Changes maintenance
1. GoldCZ instance should not be refreshed from any other instance
2. BOM Source is connected to Prod EBS and Configurable BOM/UDA
should be refresh/populate from ProdEBS and maintain the BOM Source
as ProdEBS instance to avoid data corruptions
3. To make any changes in Configurable BOM/UDA values should be made
in ProdEBS instance and refresh the data in GOLDCZ for model
maintenances
4. Publish the Model to ProdEBS from GOLDCZ after the model changes
and verified
5. Maintain the same ProdEBS BOM/UDA changes in other EBS instances
such (Dev or Test ) in order to publish the Model from GOLDCZ to the
Target instances ( Dev or Test) to conduct testing. This helps to identify
any other EBS extensions, standard process and UAT purposes

4. Infrastructure (Configurator)
Instance maintenance
1. Execute Purge Configurator Tables Concurrent programs in GOLDCZ, ProdEBS instance perodically
based on number of publication during 6 month period. This program delete orphan records in CZ
schema and clean
2. In case clone of ProdEBS instance in to DEV, Test (already connected against GOLDCZ), Execute
“Synchronize cloned Target data” concurrent Job in GOLDCZ against cloned target instance (Dev or
Test) to reconcile the Publication under line data before make any publication from GOLDCZ
Refer to this document for details: ( same available in sharepoint as well)