User Defined Columns#

Features of User Defined Columns#

• Workflow can access and update this data
• Date Sensitive changes will carry forward the values
• Change Audit Logging is supported
• Supported by Object Security and Form Object Security
• Translatable to other languages
• Natively read by report generators like Discoverer
• Faster than User Defined Fields

Steps to Set up a new User Defined Column#

The following steps need to be followed to add a new column.

1. Have all users sign out of system
2. Create the new column on the table. In SQL*Plus as the P2K user:
   • Add the column to the database
     ALTER TABLE P2K_xx_xxxxxx ADD (COLUMN_NAME COLUMN_TYPE);
     • where xx_xxxxxx is the table name
     • where COLUMN_NAME is the new column name
     • where COLUMN_TYPE is the data type of the new column: DATE, NUMBER, NUMBER(10,4), VARCHAR2(30), etc.
       Sample:
       ALTER TABLE P2K_HR_ASSIGNMENT_DETAILS ADD (ANNIVERSARY_MONTH VARCHAR2(16));
   • Multiple columns can be added using this script before running and moving onto the next stage of processing.
   • Run a db_recompile script (@db_recompile)
3. Sign into the eP system
4. In IMCD form – add the new column with a column usage of “User Defined Column”. Ensure that Data Type, Domain Name and Length are all entered at a minimum. Review other columns for samples, as needed.
5. Exit from the eP system
6. Rebuild the workflow triggers. In SQLPlus as P2K user:
   • @seed_create_biud.pls
   • You may now exit SQL*Plus
7. In Oracle Enterprise Manager (OEM), restart the J2EE Server instance. This is required because the column definitions are only loaded at start up.
8. Sign in to the eP system
9. The new column is now available to be used in form definitions (IMFD) or workflow (IMUC) or for any other purpose

BEST PRACTICES for User Defined Columns#

• Create the Column on IMCD with a number range in excess of 9000
• Identify the column in the database with a name prefix that is unique to your organization (.e.g BEN_DUE_DATE rather than just DUE_DATE)
• User Defined Columns are recommended over User Defined Fields if you are going to use them for any processing (where clauses, workflow, approvals, loading, etc.). If you are just storing data to be reported on, user defined fields may be sufficient to the task.
• Lexicons that are associated to a User Defined Column must be prefixed with "X_" (.e.g X_CUST_VALUE rather than CUST_VALUE)

Notes#