4.1.2.2.2 Develop Custom PLSQL Extensions
Customers to develop Custom PLSQL extensions as per their business / functional requirements on the sandbox database schema which was created by using the Starter Kit. Customers to test the developed extensions in their sandbox database schema with test data. Generate Custom PLSQL Archives using the Starter Kit bundled archival scripts. Custom PLSQL extensions are validated by the Archive Validation Scripts during the archival process.
Archives are generated with a Project ID or Project name, which is accepted as an input parameter during the archival script execution. The Project ID or name will be used while baselining the scripts by Oracle.
Customers should submit the full archive, including all earlier Custom extensions, every time against a project ID; Oracle will not merge one archive with previous archive submissions (if any) for a project ID.
Rules to be followed while developing custom PL/SQL extension objects are listed below:
- Naming Conventions to be followed while developing Custom PLSQL Extensions.
- Tables should not be altered or dropped.
- Seeded Data that should not be altered or deleted.
See the following table for more details.
Table 4-3 Rules
| SL No. | Rules | Details |
|---|---|---|
| 1 | Naming Conventions to be used while creating Custom Extensions |
Please use a suffix while naming the PLSQL objects with “_CUSTOM” Example: FN_UPD_FSI_D_ASSETS_CUSTOM |
| 2 | Operations Allowed on Starter Kit Objects | Refer Appendix Section B |
| 6 | Creation of Global Temporary Tables (Dynamic Tables within Custom PLSQLs using execute immediate) | Allowed |
| 7 | Creation of Views | Allowed |
| 8 | Creation of Synonyms | Allowed |
| 9 | Creation of Functions | Allowed |
| 10 | Creation of Procedures | Allowed |
| 11 | Creation of Packages | Allowed |
| 12 | Creation of Materialized Views | Not Allowed |
For more details on the process of submitting the archive, see Appendix 5.1.1.