Previous Next JavaScript must be enabled to correctly display this content

## 2.4 OBX Maintenance

This topic provides the systematic instructions to execute OBX Maintenance operations.

Before generating the artifact, verify the below items from the base installation.

Items for the base installation verification.

- Verify if the PRODUCT_EXTENDED_LEDGER table exists in the plato-ui-config schema. If it's not present, execute the script below:

      --------------------------------------------------------
      -- DDL for Table PRODUCT_EXTENDED_LEDGER
      --------------------------------------------------------
      CREATE TABLE "PRODUCT_EXTENDED_LEDGER" ("ID" VARCHAR2(20),
      "CCA_NAME"VARCHAR2(100), "CCA_TYPE" VARCHAR2(20), "PARENT_CCA_NAME"
      VARCHAR2(100), "PRODUCT_NAME" VARCHAR2(100))
      --------------------------------------------------------
      -- Constraints for Table PRODUCT_EXTENDED_LEDGER
      --------------------------------------------------------
      ALTER TABLE "PRODUCT_EXTENDED_LEDGER" ADD CONSTRAINT
      "PRODUCT_EXTENDED_LEDGER_PK" PRIMARY KEY ("ID")
      ALTER TABLE "PRODUCT_EXTENDED_LEDGER" MODIFY ("CCA_NAME" NOT NULL
      ENABLE)
      ALTER TABLE "PRODUCT_EXTENDED_LEDGER" MODIFY ("ID" NOT NULL ENABLE)
      ALTER TABLE "PRODUCT_EXTENDED_LEDGER" ADD CONSTRAINT
      "UNIQUES_CCA_NAME" UNIQUE ("CCA_NAME")

- Maintain the product name OBX in the table SMS_TM_APPLICATION inside SMS schema.
- Grant user OBX application access through SMS_TM_USER_APPLICATION or preferred use the UI.

  Figure 2-3 Create User

  Description of "Figure 2-3 Create User"

Parent topic: Welcome to Oracle Banking Extensibility Workbench