The following steps describe EBS R12.2 How to register a customized module, refer to the Oracle Support
Creating a customapplication in Oracle e-business Suite Release 12.2 (document ID 1577707.1)
1 download patch 3636980 Span lang= "ZH-CN" style= "Font-family:simsun", copy 3636980\ Izu\admin 3 .txt file to /tmp
such as: Izuprod.txt renamed to Cux Hdprod.txt
Izuterr.txt renamed to Cuxhdterr.txt
2 , modify Newprods.txt content
Product=izu
base_product_top=*appl_top*
Oracle_schema=izu
sizing_factor=100
Main_tspace=user_data
Index_tspace=user_idx
Temp_tspace=temp
Default_tspace=user_data
above is Newprods.txt content, modify the corresponding value for the module to be registered, such as:
Product=cuxhd
base_product_top=*appl_top*
Oracle_schema=cuxhd
sizing_factor=100
Main_tspace=apps_ts_tx_data
Index_tspace=apps_ts_tx_idx
Temp_tspace=temp
Default_tspace=apps_ts_tx_data
Note: In the file Izu modified to CUXHD , Izu modified to CUXHD
3. Modify the Cuxhdprod.txt file
Replace file with Izu to CUXHD, replace ProdID 278 for CUXHD's unique number
Note: The file Izu modified to Cuxhd,izu modified to CUXHD
The following SQL can be used to check if the prodid you want to set is occupied
Select Decode (count,0, ' Selected number is Available ', ' Selected number already on use ') Status,&&enter_custom_ap PlID Selected_number
From
(
Select COUNT (*) as Count from
(
Select ' x ' from Fnd_oracle_userid
where oracle_id= &&enter_custom_applid
Union
Select ' x ' from fnd_application
where Application_id=&&enter_custom_applid
)
);
Run the SQL above and enter the ProdID you want to set
4. Modify the Cuxhdterr.txt file
Replace file in Izu to Cuxhd, modify Oracle_support_diagnostic_tools to Cuxhd_custom_app
Note: The file Izu modified to Cuxhd,izu modified to CUXHD
5. Copy the above three. txt files to $appl_top/admin
6. Run Adsplice command
Adsplice must be run under $appl_top/admin
Run Adsplice
When prompted by the following, the default carriage return
The defaultdirectory is [/u01/vs03/apps/apps_st/appl/admin]:
Please enter thename of your AD splicer control file [Newprods.txt]:
Do you wish toregenerate your environment file [Yes]?
7. Confirm whether the customized module is created in the database
See if there are CUXHD records in Fnd_application
SELECT * Fromfnd_application where application_short_name = ' CUXHD ';
See if there are records in Fnd_product_installations by application_id
SELECT * Fromfnd_product_installations where application_id = 5001;
To see if a database user was created successfully
SELECT * Fromdba_users where username = ' CUXHD ';
[Email protected]]$ sqlplus CUXHD/CUXHD
Re-apply environment variables to confirm $cuxhd_top
[[Email protected] ~] $echo $CUXHD _top
/u01/vs03/apps/apps_st/appl/cuxhd/12.0.0
[Email protected] ~]$ Ls$cuxhd_top
Admin log mesg out SQL
Note: If you previously registered the module with the Fnd_oracle_user_pkg.lod_row API, because these registered passwords will be encrypted, running Adpatch, Adsplice will fail after registering.
Need to use Fndcpass to change password
If your app uses sharedappl_top then you only need to run AutoConfig on the remaining nodes
If the application is using a non-sharedappl_top, then the 5, 6, and 73 steps of the remaining nodes need to be repeated
The following steps operate on demand
1. Create Customized objects
In the $cuxhd_top,
A) $cuxhd_top/forms/us and $CUXHD_TOP/FORMS/ZHS directories can be created for form
b) $cuxhd_top/admin/sql directory can be created for the package
c) $cuxhd_top/reports/us and $CUXHD_TOP/REPORTS/ZHS can be created for the report
.
.
.
2. Grant all client data object permissions to apps users
Sql> Grant Allprivileges on myTable to apps;
Create related synonyms under Apps users
sql>createsynonym myTable for Cuxhd.mytable;>
Problem:
1, the next time using Adop patching, in the prepare phase, will synchronize the operation of Adsplice to another set of FS
If the synchronization process fails, the log $appl_top/admin/$TWO _task/log/adsplicelog appears
Updatefnd_oracle_userid SET read_only_flag = ' A ' WHERE oracle_id
Workaround: Apply Patch18815526:r12. AD. C, restart prepare phase
The following arecurrently known issues:
1. If You is Anupgrade customer with a custom product top on the context file but has not runadsplice, you must remove th E relevant entry from the Fnd_oam_context_customtable and then run AutoConfig on all nodes.
2, the same approach needs to be taken Ifyou has any custom context variables with more than eight characters, as Acustom Schema abbreviation cannot exceed eight charcters.
After performing either of the above steps,you should run Adsplice to add/register the custom product (after applying Thel Atest ad-txk RUP).
Oracle EBS R12.2 Creating a custom module