Scribd
Upload
100 views

Creating A Custom Application in Oracle E-Business Suite Release 12.1.3 and Above (Doc ID

Uploaded by

Leo Chen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
100 views

Creating A Custom Application in Oracle E-Business Suite Release 12.1.3 and Above (Doc ID

Uploaded by

Leo Chen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 7
Copyright(c) 2023, Oracle Al rlghts reserved, race Confidential Creating a Custom Applicat n in Oracle E-Business Suite Release 12.1.3 and above (Doc ID 1577707.1) In This Document This note describes the basic steps needed to create a custom application in Oracle E-Business Suite Release 12.2. Custom applications are required if you are creating new forms, reports, and so on. They allow you to segregate your custom-written files from the standard seeded functionality that Oracle E-Business Suite provides. Customizations can be preserved when applying patches to your environment, or performing upgrades. Requirements and Defaults + The procedure described in this document should be performed on the run file system, when there is no active patching oye. + This procedure can also be followed to correct the registration of a custom application that was previously created without using AD Splice. However, In such a case some additional preparatory steps are required. ‘+ Custom data and index tablespaces default to APPS_TS_TX_DATA and APPS_TS_TX_IDX respectively There is a change log at the end of this document. + Section 1: Create Custom Application Using AD Splice + Section 2: Verify Creation of Custom Product in the Ds + Section 3: Perform Require 2 Application Tier Ni * Section 4: Create Custom Objects + Section 5: Propagate Changes to Other File System + Section 6: Known Issues + Section 7: References Section 1: Create Custom Application Using AD Splice 1, Download Patch 3636980 from My Oracle Support. (This Support Diagnostics patch for AD Splice can be used with any 12.x release, not just 12.2.) 2, Manually copy the three . xt files from the 3636980\izu\adnia directory to your own temporary directory. 3, Rename icuprod. tice to prod. tae. In this example, we will USE xx 4, Rename szterc.cxt to cerr.txt, In this example, we will Use xxnzteze txt. 5, Open newprods.ext in a text editor, a. Change all references to izu to , and all references to zu to (Le, preserve Note: In this example, we will be changing references of izu to be xxnz and z2v to be xxNz. . Modify any other values as appropriate. In this example, the modified version of the nexprocs.cxt file will look like the following 6. (Conditional) In Release 12.2, any new custom application objects will be stored in APPS_TS_TX_DATA and APPS_TS_TX_IX, regardless of the settings for main. in the newproas. ex: file, AD Splice will ignore any information for these two settings, and will use only the default OATM tablespaces for your new custom ‘objects. For this reason, any new custom schema should use default_tspace as APPS_TS_TX_DATA, pace= and index spa For old custom applications created in Release 11i, update these two values to point to your old custom OFA tablespaces. Only do this if you did not convert to OATM before upgrading to Release 12.2. Note: For more information, refer to Oracle E-Business Suite Maintenance Guide, Chapter 7, "Applications DBA ‘System Maintenance Tasks and Tools", section Managing Files, subsection Adding New Off-Cycle Products, Step 4. Create tablespaces (conditional). ‘This means that AD Splice will take into consideration your custom tablespaces only for old Release 11i custom applications that were never converted to use the OATM model. In such cases, you therefore need to perform the following additional steps: 2. Create the new user account that will own the custom schema, b. Define the default tablespace for the new user to be APPS_TS_TX_DATA. C. Edit newprads.txt to include the following custom information: This should be set to APPS TS 1% DATA, the default tablespace for Do not include the comments, which are preceded by "//" 7. Open xxmzprod.txt in a text editor. 2. Before starting, be aware of the following important point ‘= Ifyou are going to rename the application, you cannot use the old application ID with the new application name. * IF you are going to retain the existing application name, you must use the same application ID when running AD Splice. ‘= Ifyou are upgrading, and the custom application already exists in the database, you should specify the same application 1D. = IF you are performing a new installation, choose an application ID number above 50,000 that is not already in use. b. Change all references to izu to and all references to 1zu to (Le, preserve case sensitivity). Note: In this example, references to ‘2. will be changed to xxm2, and references to zs will be changed to Change all references to prodid 278 to your own application ID, You can run the following SQL to find out if your selected custom application ID number is available: ject decode (count ,0, ‘Selected nunber ie available’, ‘Selected number is already in use") plID selected number sou> from ject count(*) as count from ject 'x! from fnd_oracle userid jct_'x' from fnd_application where application id~ eéenter, custom appl7D , M Note: This example will use @ prodid of 50201. 8, Open xxmzterr.txt in a text editor. SOM MODULE> (ie. preserve ‘a. Change all references to izu to and all references to 12 to case sensitivity). Note: In this example, references to ‘>. will to changed to xxn2, and references to xz will be changed to b. Change the text 101s to be xenz_custom_app, el upport_DiagnostLe 9. Copy the following text files to the saPPL_roP/acnin directory: rode. txt 10, Change directory to the admin directory under saPeL_nor. 11, Run AD Splice Note: In Oracle E-Business Suite Release 12.2, AD Splice first makes the new user edition-enabled, and then enables Edition-Based Redefinition (EBR) for the custom objects. AD Splice must be run from the admin directory under saei, vor, and is invoked by running the command: ‘When prompted for the following, you can press Enter to accept the default location: ppe_st/appl/adnin] ‘When prompted for the following, you can press Enter to accept the default filename: ‘When prompted for the following, you can press Enter to accept the default value and regenerate the environment file: Do you wish ‘AutoConfig will be run automatically as part of this procedure 12. Review the AD Splice log file to ensure the splicing part of the procedure completed successfully 13, Review the AutoConfig log file to ensure the AutoConfig run completed successfully, Note: If you have multiple custom tops, there is no need to create @ full set of individual fles (such as xx woccerr.txt, and newsrods..

You might also like