12.1.3 & 12.2.4 Diffrence

1)In R12.2 we have two kind of filesystems fs1(run filesystem) and fs2(patch filesystem)
  where as In R12.1.3 we only deal with one application filesystem.

2)In R12.2 we have the Application servers replaced by Weblogic server to manage the technology statck.
  The major change in R12.2 is involvement of Weblogic server to manager all the forms,oacore servers
  where as in R12.1.3 we had the Application server 10.1.3 to manage the web home or Java Home

3)'Apps' user Password change:

The 'apps' user password change involve 3 steps in R12.2.4
1)Change the password with FNDCPASS
2)Change the password in EBS Datasource from Weblogic admin console
3)Run AutoconfigCheck below link from Bala for detail steps:

Where as in R 12.1.3 It only involves 2 steps:
1)Change the password with FNDCPASS
2)Run Autoconfig
5)Log files locations:

All the oacore,forms log files are placed in $EBS_DOMAIN_HOME in R12.2.
Where as in R12.1.3 all the logs for oacore,forms are under $LOG_HOME/ora/10.1.3


12.2.4 Diff

Scripts required for 12.2.X custom table development

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');

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.