Oracle EBS R12.2 create a custom module, ebsr12.2

Oracle EBS R12.2 create a custom module, ebsr12.2

The following steps describe how to register a custom module in EBS R12.2. Refer to Oracle support

Creating a CustomApplication in Oracle E-Business Suite Release 12.2 (Document ID 1577707.1)

 

1. Download patch 3636980 and copy 3. txt files under the 3636980 \ izu \ admindirectory to the/tmp directory for modification.

For example, change izuprod.txtto cuxhdprod.txt.

Izuterr.txtrename cuxhdterr.txt

 

2nd 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

 

Change the content of newprods.txt to the value of the module to be registered, for example:

Product = cuxhd

Base_product_top = * APPL_TOP *

Oracle_schema = cuxhd

Sizing_factor = 100

Main_tspace = pai_ts_tx_data

Index_tspace = pai_ts_tx_idx

Temp_tspace = TEMP

Default_tspace = pai_ts_tx_data

Note: In the file, change izu to cuxhd and IZU to CUXHD.

3366modify the cuxhdprod.txt File

Replace izu with cuxhd, and prodid 278 with the unique number of cuxhd.

 

Note: In the file, change izu to cuxhd and IZU to CUXHD.

 

Run the following SQL statement to check whether the prodid you want to set is occupied:

Select decode (count, 0, 'selected number is Available ', 'selected number already in use') Status, & enter_custom_applID 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 preceding SQL statement and enter the prodid you want to set.

 

4、modify the cuxhdterr.txt File

Replace izu with cuxhd, and change Oracle_Support_Diagnostic_Tools to cuxhd_custom_app.

Note: In the file, change izu to cuxhd and IZU to CUXHD.

 

5. Upload the three. txt files to $ APPL_TOP/admin.

 

6. Run the adsplice command

Adsplice must run under $ APPL_TOP/admin

Run adsplice

If the following prompt is displayed, press enter by default.

The defaultdirectory is [/u01/VS03/apps/pai_st/appl/admin]:

 

Please enter thename of your AD Splicer control file into newprods.txt]:

 

Do you wish toregenerate your environment file [Yes]?

 

7. Check whether the custom module is created in the database.

 

Check whether there are CUXHD records in fnd_application

Select * fromfnd_application where application_short_name = 'cuxhd ';

Use application_id to check whether there are records in fnd_product_installations.

Select * fromfnd_product_installations where APPLICATION_ID = 5001;

Check whether the database user is successfully created

Select * fromdba_users where username = 'cuxhd ';

 

[Appl03 @ vs006admin] $ sqlplus cuxhd/cuxhd

 

Re-apply the environment variable and confirm $ CUXHD_TOP

[Appl03 @ vs006 ~] $ Echo $ CUXHD_TOP

/U01/VS03/apps/apps_st/appl/cuxhd/12.0.0

 

[Appl03 @ vs006 ~] $ Ls $ CUXHD_TOP

Admin log mesg out SQL

 

Note: If you have previously used the fnd_oracle_user_pkg.lod_row API to register a module, the registered passwords will be encrypted and an error will occur when you run adpatch and adsplice after registration.

Use FNDCPASS to change the password

 

If the application uses sharedAPPL_TOP, you only need to run autoconfig on the remaining nodes.

If the application uses non-sharedAPPL_TOP, repeat the preceding steps 5, 6, and 7 on the remaining nodes.

Follow these steps:

 

1. Create a custom object

 

In $ CUXHD_TOP,

A) You can create $ CUXHD_TOP/forms/US and $ CUXHD_TOP/forms/ZHS directories for form.

B) You can create the $ CUXHD_TOP/admin/SQL directory for the package.

C) You can create $ CUXHD_TOP/reports/US and $ CUXHD_TOP/reports/ZHS for the report.

.

.

.

 

2. Grant all custom data object permissions to APPS users

 

SQL> grant allprivileges on myTable to apps;

 

Create synonyms for APPS users

SQL> createsynonym myTable for CUXHD. myTable;>

 

 

Problem:

1. When adop is used for patching, In the prepare phase, the adsplice operation will be synchronized to another FS

 

If the synchronization fails, the log $ APPL_TOP/admin/$ TWO_TASK/log/adsplicelog appears.

UPDATEFND_ORACLE_USERID SET READ_ONLY_FLAG = 'A' WHERE ORACLE_ID

 

Solution: Apply Patch18815526: R12.AD. C and restart prepare phase.

 

 

The following arecurrently known issues:

1. If you are anupgrade customer with a custom product top in the context file but have not runadsplice, you must remove the relevant entry from the FND_OAM_CONTEXT_CUSTOMtable and then run AutoConfig on all nodes.

2. The same approach needs to be taken ifyou have any custom context variables with more than eight characters, as acustom schema abbreviation cannot exceed eight charcters.

 

After creating Ming either of the above steps, you should run adsplice to add/register the custom product (after applying thelatest AD-TXK RUP ).