Scripts required for 12.2.X custom

1) For new table creations - after creating the table in custom schema execute below script to generate editoning view and synonym for it in APPS schema.

exec AD_ZD_TABLE.UPGRADE('XXCUST','XX_CUST_TBL1');

2) For table alteratuons - after running the DDL run below script to regenerate the editioning view for syncing any table changes.

exec AD_ZD_TABLE.PATCH('XXCUST','XX_CUST_TBL1')

3) Table grants must be done through API to avoid invalids.

exec AD_ZD.GRANT_PRIVS('SELECT','XX_CUST_TBL1','XX_ROLE0')

4) To view objects in all editions..add _ae to the data dictionary views

select * from user_objects_ae;

5) To update seed data tables in Patch edition, execute prepare command.

example:
exec ad_zd_seed.prepare('WF_MESSAGES');

6)exec AD_ZD.compile ('') -- to compile the objects

The prepare will create a edition based storage for the run edition data for which the updates will be made. During cutover, the run time data will be synced using forward/reverse cross edition triggers.

How to Add a Column:

Altering a table – Adding Columns and Indexes

1. Alter table in custom schema the usual way.
alter table cust_table add cust_info varchar2(1) NOT NULL;

Regenerate the editioning view using AD_ZD_TABLE.PATCH
SQL> exec ad_zd_table.patch(table_owner, table_name);

NB: Once the table is altered with the table name, “exec ad_zd_table.patch(‘XXSDS’, ‘cust_table’)” needs to be applied every time

Then:
exec ad_zd_table.upgrade(table_owner, table_name);

RUN EBS Online Patching Database Compliance Checker"(ADZDDBCC.sql)

file location $AD_TOP/sql

for reference check
https://smartdogservices.com/navigating-the-new-waters-of-r12-2-development-customization-part-2/