4.1.2 Steps to introduce Custom PLSQLs

Support for Custom PLSQL is a workflow-based capability.

The different stages involved are:

• Generate, Download and Install the Starter Kit
• Develop Custom PLSQL Extensions
• Extract and Submit the Custom PLSQLs for Oracle Due Diligence
• Request for Archive Deployment of the Custom PLSQLs on the preferred PBSM SaaS Instance
• Access User Extension through Scheduler

• Generate, Download and Install the Starter Kit
  PLSQL Starter Kit can be generated using Cloud Service User Interface located under the LHS menu ‘Admin Tools’. UI has options to Include Custom tables & Include data for all Custom tables as optional selections while generating a Starter Kit. The UI will display the current Status and previously generated Starter Kit Status details. The UI has a Download button using which you can download the generated Starter Kit.
• Develop Custom PLSQL Extensions
  After installing the starter kit, you can develop Custom PLSQL extensions as per your business / functional requirements on the sandbox database schema which was created by using the Starter Kit. You must test the developed extensions in your sandbox database schema with test data. Thereafter, 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.
• Extract and Upload the Custom PLSQL Archive
  
• Submit the Custom PLSQLs for Oracle Due Diligence
  Oracle Due Diligence is an Oracle internal process to validate the submitted archives and confirm that the archives are ready for deployment on a target PBMS SaaS Instance. Refer the PLSQL Archive Summary Submit for Due Diligence section of this document for more details.
• Submit Archive for Deployment
  
• Access User Extension through Scheduler
  You can access the Customer PLSQL Extension using the Scheduler service.