戻る
-
タイトル
Does Stat take care of generating Editioning View (EV) by executing ad_zd_table.upgrade? -
説明
Over the main process listed below, does Stat take care of ad_zd_table.upgrade process to generate Editioning View (EV) ?The below is the process of table creation in R12.2.x:- Creating a table- Connect to the run time edition of the development environment- Create table in the custom schema.- Upgrade the table for online patching using the below commandexec ad_zd_table.upgrade(<table>,<EV Synonym>) <-- This will generate an Editioning View (EV) for the table and then create an APPS synonym that points to the Editioning View.At this point the table is now ready for use from the APPS schema. The generated EV is named and looks exactly like the table. -
原因
In the Sys Admin Guide | Oracle Apps object types is documented the flow cycle but not in detail for each object. -
対策
Solution:Once the table is created and run ad_zd_table.upgrade in the source environment, Stat runs xdfgen.pl to archive the definition for Editioning View from source and it uses xdfcmp.pl to generate the definitions on the target.Basically, you only need to run ad_zd_table.upgrade initially when you create the schema object on the source environment. Once the schema object is created and ad_zd_table.upgrade is run, you can use Stat to archive the definition in an archive set. This is done by running xdfgen.pl in Stat. To deploy that definition on other target environments, Stat then run xdfcmp.pl, which is what a migration is in Stat. Mainly, you just need to use the ‘XDF Editioning View’ object type.