Referencing dba_objects in a trigger.

Somehow, I am unable to compile a trigger referencing dba_objects view. Oracle gives me 'Invalid object' message. I am able to query dba_objects from the user session. Dose this mean dba_* views are not allowed in Triggers?

Most likely, your account has been granted access to SELECT from DBA_OBJECTS via a role rather than as a direct grant. If you want to reference an object using a named PL/SQL block (i.e. a procedure, a trigger, etc.) using definer's rights (the default), the owner of the object needs to have been given a direct grant on the object in question. The grant cannot come via a role.
In SQL*Plus, if you
SQL> set role noneI'll wager that you won't be able to query DBA_OBJECTS which would confirm my suspicion.
Justin

Similar Messages

Created date of a trigger

I was trying to find the date of creation of a trigger in the database. But the detail is not in all_triggers view. Is there any other dictionary view, in which I can find this?

select created, last_ddl_time from dba_objects where object_type='TRIGGER';
good luck

ORA-01031: insufficient privileges While Trying to Create a Trigger

Hi
I am trying to create a trigger on one of the table in the database schema :
CREATE OR REPLACE TRIGGER Trigger_Name
BEFORE INSERT ON table_name
FOR EACH ROW
---Trigger Body...
However I am getting the following error : ORA-01031: insufficient privileges
I have tried to check the status of the trigger with the following script :
SELECT object_name
FROM dba_objects
WHERE object_type = 'TRIGGER'
AND status = 'INVALID';
and it is showing its status as "INVALID".
Can anybody please suggest me how to proceed on this?

Hi,
If the trigger exists than you have privilieges to create trigger but you need some privilieges needed to compile it.
Check all commands and objects you are referring to inside trigger body. Maybe you are trying select table without proper priviliege...?
Bartek

Need help in deleting multiple tables

Hi,
In one of my scenario i want to delete One record from the table, but there are some child and sub child exist for the table. And the on delete cascade is not set fro any of the table.
Structure of my table,
Table-1
tab1_pk
tab1_name
Table-2
tab2_pk
tab1_pk
Table-3
tab3_pk
tab2_pk
i want to delete the record from Table-1 and all the related record of Table-2 and Table-3 in a single query.
Plz help

Dear 786725,
What has just came to my mind at first sight is that you can create a trigger for your approach. I don't think that a single query will delete some rows from more than one table.
Please go to the http://tahiti.oracle.com , select your database version and search for the after trigger. Hint: You may need to use the FOR EACH ROW clause and you again may need to use :old :new parameters in the trigger to have the information of what has just been deleted from the relevant table.
Hope That Helps.
Ogan
Edited by: Ogan Ozdogan on 05.Ağu.2010 19:00
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7004.htm#SQLRF01405
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b31695/dialogs.htm#sthref454
4.24 Create Trigger
The following information applies to a trigger, which is which is a stored PL/SQL block associated with a table, a schema, or the database, or an anonymous PL/SQL block or a call to a procedure implemented in PL/SQL or Java. The trigger is automatically executed when the specified conditions occur.
Schema: Database schema in which to create the trigger.
Name: Name of the trigger. Must be unique within the database.
Add New Source in Lowercase: If this option is checked, new text is entered in lowercase regardless of the case in which you type it. This option affects only the appearance of the code, because PL/SQL is not case sensitive in its execution.
Trigger tab
Trigger Type: The type of object on which to create the trigger: TABLE, VIEW, SCHEMA, or DATABASE. (The remaining items depend on the type of trigger.)
Table Owner or View Owner: For a trigger on a table or a view, the name of the owner of the table or the view.
Table Name or View Name : For a trigger on a table or a view, the name of the table or the view.
Before or After: For a trigger on a table, select Before to cause the database to fire the trigger before executing the triggering event, or select After to cause the database to fire the trigger after executing the triggering event.
Statement Level or Row Level: For a trigger on a table, Statement Level fires the trigger once before or after the triggering statement that meets the optional trigger constraint defined in the WHEN condition; Row Level fires the trigger once for each row that is affected by the triggering statement and that meets the optional trigger constraint defined in the WHEN condition.
Insert, Update, Delete: For a trigger on a table or a view, Insert fires the trigger whenever an INSERT statement adds a row to a table or adds an element to a nested table; Update fires fire the trigger whenever an UPDATE statement changes a value in one of the columns specified in Selected Columns (or in any column if no columns are specified); Delete fires the trigger whenever a DELETE statement removes a row from the table or removes an element from a nested table.
Referencing - Old: For a trigger on a table, the correlation names in the PL/SQL block and WHEN condition of a row trigger to refer specifically to old value of the current row.
Referencing - New: For a trigger on a table, the correlation names in the PL/SQL block and WHEN condition of a row trigger to refer specifically to new value of the current row.
Available Columns: For a trigger on a table, lists the columns from which you can select for use in an Update trigger definition.
Selected Columns: For a trigger on a table, lists the columns used in an Update trigger definition.
When: For a trigger on a table, an optional trigger condition, which is a SQL condition that must be satisfied for the database to fire the trigger. This condition must contain correlation names and cannot contain a query.
Schema: For a trigger on a schema, the name of the schema on which to create the trigger.
Available Events: For a trigger on a schema or database, lists events from which you can select for use in the trigger definition.
Selected Events: For a trigger on a schema or database, lists events used in the trigger definition.
DDL tab
This tab contains a read-only display of a SQL statement that reflects the current definition of the trigger.
"

Errors while upgrading from 9i to 11gR1 during catuprd.sql

Hi,
I am very new into the world of databases and am learning it the hard way. Testing all sorts of work on my home PC. I am in the process of upgrading my Win 32 9.2.0.8 to 11gR1 and am at the stage of running catupgrd.sql. The SQL ran for hours and completed. However, when i go to the second step as per Oracle upgrade guide- that is running utl111s.sql, i get the following errors.
ERROR at line 1:
ORA-04045: errors during recompilation/revalidation of SYS.DBMS_REGISTRY_SYS
ORA-04098: trigger 'SYS.CDC_ALTER_CTABLE_BEFORE' is invalid and failed
re-validation
ORA-06508: PL/SQL: could not find program unit being called:
"SYS.DBMS_REGISTRY_SYS"
ORA-06512: at "SYS.DBMS_REGISTRY", line 1797
ORA-06512: at line 110
ORA-04045: errors during recompilation/revalidation of SYS.DBA_OBJECTS
ORA-04098: trigger 'SYS.CDC_ALTER_CTABLE_BEFORE' is invalid and failed
re-validation
The log file for catupgrd shows several instances of the following errors
ORA-29537: class or resource cannot be created or dropped directly
ORA-06512: at "SYS.INITJVMAUX", line 32
ORA-06512: at line 37
Oracle Database Java Packages
. ORA-20000: JServer has not been correctly loaded into the database.
. ORA-06512: at line 3
ERROR at line 1:
ORA-20000: JServer has not been correctly loaded into the database.
ORA-06512: at line 3
I tried running utlrp.sql to compile all invalid objects but, that too gave the trigger error mentioned above. I had fixed all the warnings pointed out by the pre-upgrade script.
I also tried disabling the trigger and running utlrp.sql, but it was of no use.
Any pointers in this regard will be welcome.
Thanks,
Jithin

Srini, This is a play instance, and I have VM snapshots as well as backups of the database at various stages of the upgrade process.
I tried to load JAVA manually into the db by following Metalink Note 457279.1. I ran the full_rmjvm.sql and it errored out in the catnojav.sql saying "ORA-20000: JServer is not operational in the database; JServer is required to remove CATJAVA from the database."
So, looks like I'm trying to remove JVM with no JServer operational .
My Catupgrd.sql log said two things that I now noticed
JServer JAVA Virtual Machine
. ORA-29537: class or resource cannot be created or dropped directly
. ORA-06512: at "SYS.INITJVMAUX", line 32
. ORA-06512: at line 37
. UPGRADING 9.2.0.8.0 00:16:38
and
Oracle Database Java Packages
. ORA-20000: JServer has not been correctly loaded into the database.
. ORA-06512: at line 3
. LOADING 9.2.0.8.0 00:00:11
All the other components are shown to have version 11.1.0.6.0
So I guess the error is in 9i itself? JAVA, or one of its needed components, was not installed correctly in the 9i database. I have the VM snapshots so I could go back in time a bit and do some R&D. What do you suggest?
PS: I spend 9-6 at office tuning the SQL and then 8-2 at home fixing this upgarde. It has sure go me hooked. I even let go the IPL for this. Hoping to wrap up the upgrade by sunday.
Thanks,
Jithin

The Size of prddata increasing with great speed . dbf files are increasing

Hi
the Size of prddata increasing with great speed . dbf files are increasing which result in 100 % space utilization.
can I delete temp01.dbf files.what is possible solution for this as dbf files are increasing with unexpected great speed.
Thanks
Rahul

db version is 9.2.0.6.0
Application 11.5.10.2
Allert.log is showing error
ORA-04098: trigger 'APPS.XXXX_APPS_LOGON_TRG' is invalid and failed re-validation
output of query
select object_name
from dba_objects
where object_type = 'TRIGGER'
and status = 'INVALID';
OBJECT_NAME
AX_AP_CHECKS_ARU1
AX_AP_CHECKS_ARU2
AX_AP_CHECKS_BRI1
AX_AP_HOLDS_ARI1
AX_AP_HOLDS_ARU1
AX_AP_HOLD_CODES_ARU1
AX_AP_INVOICES_ARU1
AX_AP_INVOICES_ARU2
AX_AP_INVOICES_ARU3
AX_AP_INVOICES_BRDI1
AX_AP_INVOICE_DIST_ARDI1
OBJECT_NAME
AX_AP_INVOICE_DIST_ARDI2
AX_AP_INVOICE_DIST_ARU1
AX_AP_INVOICE_DIST_ARU2
AX_AP_INVOICE_PAY_ARDI1
AX_DOCUMENT_STATUSES_BRU1
AX_DOCUMENT_STATUSES_BRU2
BEN_EXT_ADD_EVT
FF_GLOBALS_F_BRI
GHR_PER_ADDRESSES_AFIUD
HRI_EDW_CMPSTN_SNPSHT_DTS_WHO
HRI_EDW_USER_PERSON_TYPES_WHO
OBJECT_NAME
HRI_GEN_HRCHY_SUMMARY_WHO
HRI_INV_SPRTN_RSNS_WHO
HRI_MB_WMV_WHO
HRI_ORG_HRCHY_SUMMARY_WHO
HRI_ORG_PARAMS_WHO
HRI_ORG_PARAM_LIST_WHO
HRI_PRIMARY_HRCHYS_WHO
HRI_RECRUITMENT_STAGES_WHO
HRI_SERVICE_BANDS_WHO
HRI_SUPV_HRCHY_SUMMARY_WHO
HR_ORG_INFO_BRI
OBJECT_NAME
HR_PAY_IF_ASG_COST_BRD
HR_PAY_IF_ELE_ENT_ASD
HR_PAY_IF_PERSON_ARU
HR_PAY_IF_PPM_BRD
HR_PAY_IF_PPM_NO_UPDATE2_ARU
HR_PAY_IF_PPM_NO_UPDATE_ARU
HR_PA_MAINTAIN_ORG_HIST_BRI
HXC_ALIAS_DEFINITIONS_WHO
HXC_ALIAS_TYPES_WHO
HXC_ALIAS_TYPE_COMPONENTS_WHO
HXC_ALIAS_VALUES_WHO
OBJECT_NAME
HXC_APPROVAL_COMPS_WHO
HXC_APPROVAL_PERIOD_COMPS_WHO
HXC_APPROVAL_PERIOD_SETS_WHO
HXC_APPROVAL_STYLES_WHO
HXC_BLD_BLK_INFO_TYPE_USAG_WHO
HXC_DATA_APP_RULE_USAGES_WHO
HXC_DEPOSIT_PROCESSES_WHO
HXC_ENTITY_GROUPS_WHO
HXC_ENTITY_GROUP_COMPS_WHO
HXC_ERRORS_WHO
HXC_LAYOUTS_WHO
OBJECT_NAME
HXC_LAYOUT_COMPONENTS_WHO
HXC_LAYOUT_COMP_DEFINITION_WHO
HXC_LAYOUT_COMP_PROMPTS_WHO
HXC_LAYOUT_COMP_QUALIFIERS_WHO
HXC_LAYOUT_COMP_QUAL_RULES_WHO
HXC_MAPPINGS_WHO
HXC_MAPPING_COMPONENTS_WHO
HXC_MAPPING_COMP_USAGES_WHO
HXC_PREF_DEFINITIONS_WHO
HXC_PREF_HIERARCHIES_WHO
HXC_RECURRING_PERIODS_WHO
OBJECT_NAME
HXC_RESOURCE_RULES_WHO
HXC_RETRIEVAL_PROCESSES_WHO
HXC_RETRIEVAL_RANGES_WHO
HXC_RETRIEVAL_RULES_WHO
HXC_RETRIEVAL_RULE_COMPS_WHO
HXC_TIME_BUILDING_BLOCKS_WHO
HXC_TIME_CATEGORIES_WHO
HXC_TIME_CATEGORY_COMPS_WHO
HXC_TIME_ENTRY_RULES_WHO
HXC_TIME_RECIPIENTS_WHO
HXC_TIME_SOURCES_WHO
OBJECT_NAME
HXC_TK_GROUPS_WHO
HXC_TK_GROUP_QUERIES_WHO
HXC_TK_GROUP_QUERY_CRITERI_WHO
HXC_TRANSACTIONS_WHO
HXC_TRANSACTION_DETAILS_WHO
HXT_ADD_ASSIGN_INFO_F_WHO
HXT_ADD_ELEM_INFO_F_WHO
HXT_DET_HOURS_WORKED_F_WHO
HXT_EARNING_POLICIES_WHO
HXT_EARNING_RULES_WHO
HXT_EARN_GROUPS_WHO
OBJECT_NAME
HXT_EARN_GROUP_TYPES_WHO
HXT_ERRORS_F_WHO
HXT_HOLIDAY_CALENDARS_WHO
HXT_HOLIDAY_DAYS_WHO
HXT_HOUR_DEDUCTION_RULES_WHO
HXT_HOUR_DEDUCT_POLICIES_WHO
HXT_PREM_ELIGBLTY_POLICIES_WHO
HXT_PREM_ELIGBLTY_POL_RULE_WHO
HXT_PREM_ELIGBLTY_RULES_WHO
HXT_PREM_INTERACT_POLICIES_WHO
HXT_PREM_INTERACT_RULES_WHO
OBJECT_NAME
HXT_PROJECTS_WHO
HXT_ROTATION_PLANS_WHO
HXT_ROTATION_SCHEDULES_WHO
HXT_SHIFTS_WHO
HXT_SHIFT_DIFF_POLICIES_WHO
HXT_SHIFT_DIFF_RULES_WHO
HXT_SUM_HOURS_WORKED_F_WHO
HXT_TASKS_WHO
HXT_TIMECARDS_F_WHO
HXT_VARIANCES_WHO
HXT_WEEKLY_WORK_SCHEDULES_WHO
OBJECT_NAME
HXT_WORK_SHIFTS_WHO
OTA_ACTIVITY_DEFINITIONS_WHO
OTA_BOOKING_DEALS_WHO
OTA_BOOKING_STATUS_HISTORI_WHO
OTA_CATEGORY_USAGES_WHO
OTA_COMPETENCE_LANGUAGES_WHO
OTA_CROSS_CHARGES_WHO
OTA_DELEGATE_BOOKINGS_WHO
OTA_EVENT_ASSOCIATIONS_WHO
OTA_FINANCE_HEADERS_WHO
OTA_FINANCE_LINES_WHO
OBJECT_NAME
OTA_HR_GL_FLEX_MAPS_WHO
OTA_ILN_XML_PROCESSES_WHO
OTA_NOTRNG_HISTORIES_WHO
OTA_PRICE_LISTS_WHO
OTA_PRICE_LIST_ENTRIES_WHO
OTA_RESOURCE_ALLOCATIONS_WHO
OTA_RESOURCE_DEFINITIONS_WHO
OTA_RESOURCE_USAGES_WHO
OTA_SKILL_PROVISIONS_WHO
OTA_SUPPLIABLE_RESOURCES_WHO
OTA_TRAINING_PLANS_WHO
OBJECT_NAME
OTA_TRAINING_PLAN_COSTS_WHO
OTA_TRAINING_PLAN_MEMBERS_WHO
OTA_VENDOR_SUPPLIES_WHO
PAY_ASSIGNMENT_ACTIONS_BRD
PAY_ASSIGNMENT_ACTIONS_BRU
PAY_BALANCE_BATCH_LINES_BRIUD
PAY_BALANCE_FEEDS_ARD
PAY_BALANCE_FEEDS_ARI
PAY_BALANCE_FEEDS_ARU
PAY_DEFINED_BALANCES_ARI
PAY_DEFINED_BALANCES_BRD
OBJECT_NAME
PAY_ELEMENT_LINKS_T1
PAY_ELEMENT_TYPES_T1
PAY_ORG_PAYMENT_METHODS_F_OVN
PAY_PAYMIX_LINE_INSERT
PAY_PAYROLL_ACTIONS_BRD
PAY_PAYROLL_ACTIONS_BRU
PAY_PERSONAL_PAYMENT_METHO_OVN
PAY_PERSONAL_PAY_METHODS_BRUI
PAY_RUN_RESULTS_BRD
PAY_TRIGGER_EVENTS_ARD
PAY_ZA_TEMP_BRANCH_DETAILS_ARD
OBJECT_NAME
PAY_ZA_TEMP_BRANCH_DETAILS_ARI
PAY_ZA_TEMP_BRANCH_DETAILS_ASI
PA_MAINTAIN_ORG_HIST_BRD
PER_ABV_OVN
PER_ALL_ASSIGNMENTS_F_OVN
PER_ALL_PEOPLE_F_ARIU
PER_ALL_PEOPLE_F_OVN
PER_ESTABLISHMENT_ATTN_CHLG
PER_JOB_REQUIREMENTS_OVN
PER_ORG_STRUCTURE_ELEMENTS_OVN
PER_ORS_OVN
OBJECT_NAME
PER_OSV_OVN
PER_PAY_PROPOSALS_CHLG
PER_PAY_PROPOSALS_OVN
PER_PERIODS_OF_SERVICE_OVN
PER_POS_STRUCTURE_ELEMENTS_OVN
PER_PROPOSAL_COMPS_OVN
PER_QUERY_CRITERIA_OVN
PER_RECRUITMENT_ACTIVITIES_OVN
PER_REC_ACTIVITY_FOR_OVN
PER_REQUISITIONS_OVN
PER_VALID_GRADES_OVN
OBJECT_NAME
SET_HXT_BATCH_STATES_INS
SSP_DEL_ORPHANED_ROWS
SSP_MEDICALS_WHO
SSP_STOPPAGES_WHO
SSP_WITHHOLDING_REASONS_WHO
BEN_ABR_EXTRA_INFO_WHO
BEN_ABR_INFO_TYPES_WHO
BEN_ACRS_PTIP_CVG_F_WHO
BEN_BENEFICIARIES_F_WHO
BEN_ACTL_PREM_VRBL_RT_RL_F_WHO
BEN_ACTN_TYP_WHO
OBJECT_NAME
BEN_COVERED_DEPENDENTS_F_WHO
BEN_VALID_DEPENDENT_TYPES_WHO
BEN_ACTY_BASE_RT_CTFN_F_WHO
BEN_ACTY_BASE_RT_F_WHO
BEN_ACTY_RT_PYMT_SCHED_F_WHO
BEN_ACTY_VRBL_RT_F_WHO
BEN_AGE_FCTR_WHO
BEN_AGE_RT_F_WHO
BEN_APLCN_TO_BNFT_POOL_F_WHO
OTA_ANNOUNCEMENTS_WHO
BEN_APLD_DPNT_CVG_ELIG_PRF_WHO
OBJECT_NAME
BEN_BATCH_BNFT_CERT_INFO_WHO
BEN_BATCH_COMMU_INFO_WHO
BEN_BATCH_LER_INFO_WHO
BEN_BATCH_PARAMETER_WHO
HXT_TIMECLOCK_ERRORS_WHO
BEN_BNFT_POOL_RLOVR_RQMT_F_WHO
BEN_BNFT_PRVDR_POOL_F_WHO
BEN_BNFT_VRBL_RT_F_WHO
BEN_BNFT_VRBL_RT_RL_F_WHO
FF_FORMULAS_F_WHO
FF_ROUTE_PARAMETER_VALUES_WHO
OBJECT_NAME
BEN_CMBN_PLIP_F_WHO
HXC_LOCKING_RULES_WHO
GHR_COMPLAINTS2_WHO
BEN_CM_TYP_F_WHO
GHR_COMPL_AGENCY_APPEALS_WHO
GHR_COMPL_CA_DETAILS_WHO
GHR_COMPL_CA_HEADERS_WHO
GHR_CPDF_TEMP_WHO
GHR_DUAL_ACTIONS_WHO
GHR_DUAL_PROC_METHODS_WHO
HXC_SEEDDATA_BY_LEVEL_WHO
OBJECT_NAME
GHR_DUTY_STATIONS_F_WHO
GHR_GROUPBOX_USERS_WHO
BEN_CM_TYP_USG_F_WHO
BEN_DED_SCHED_PY_FREQ_WHO
BEN_DPNT_CVG_RQD_RLSHP_F_WHO
GHR_POIS_WHO
GHR_POSITION_DESCRIPTIONS_WHO
BEN_DPNT_CVRD_ANTHR_PL_CVG_WHO
GHR_PREMIUM_PAY_INDICATORS_WHO
GHR_PROCESS_LOG_WHO
OTA_IMPORT_HISTORIES_WHO
OBJECT_NAME
GHR_RESTRICTED_PROC_METHOD_WHO
OTA_LEARNING_PATHS_WHO
GHR_RIF_REGISTERS_WHO
BEN_DPNT_OTHR_PTIP_RT_F_WHO
GHR_ROUTING_GROUPS_WHO
GHR_ROUTING_LISTS_WHO
GHR_ROUTING_LIST_MEMBERS_WHO
BEN_DSBLD_RT_F_WHO
BEN_DSGNTR_ENRLD_CVG_F_WHO
BEN_DSGN_RQMT_RLSHP_TYP_WHO
BEN_EE_STAT_RT_F_WHO
OBJECT_NAME
BEN_ELCTBL_CHC_CTFN_WHO
BEN_ELIGY_PRFL_RL_F_WHO
BEN_ELIG_AGE_CVG_F_WHO
BEN_ELIG_COMPTNCY_PRTE_F_WHO
BEN_ELIG_NO_OTHR_CVG_PRTE_WHO
HR_CANVAS_PROPERTIES_WHO
BEN_ELIG_PRTT_ANTHR_PL_PRT_WHO
HR_COMMENTS_WHO
HR_DE_LIABILITY_PREMIUMS_F_WHO
BEN_ELIG_PSTN_PRTE_F_WHO
BEN_ELIG_PYRL_PRTE_F_WHO
OBJECT_NAME
BEN_ELIG_QUAL_TITL_PRTE_F_WHO
HR_DM_APPLICATION_GROUPS_WHO
BEN_ELIG_SCHEDD_HRS_PRTE_F_WHO
HR_DM_DATABASES_WHO
BEN_ELIG_SP_CLNG_PRG_PRTE_WHO
HR_DM_DT_DELETES_WHO
BEN_ELIG_STDNT_STAT_CVG_F_WHO
HR_DM_EXP_IMPS_WHO
BEN_ELIG_SUPPL_ROLE_PRTE_F_WHO
HR_DM_GROUPS_WHO
BEN_ELIG_SVC_AREA_PRTE_F_WHO
OBJECT_NAME
BEN_ELIG_TBCO_USE_PRTE_F_WHO
HR_DM_HIERARCHIES_WHO
HR_DM_LOADER_PARAMS_WHO
BEN_ELIG_TO_PRTE_RSN_F_WHO
BEN_ELIG_TTL_CVG_VOL_PRTE_WHO
HR_DM_LOADER_PHASE_ITEMS_WHO
BEN_ELIG_TTL_PRTT_PRTE_F_WHO
HR_DM_MIGRATIONS_WHO
HR_DM_MIGRATION_RANGES_WHO
HR_DM_MIGRATION_REQUESTS_WHO
HR_DM_PHASE_ITEMS_WHO
OBJECT_NAME
BEN_ENRLD_ANTHR_OIPL_RT_F_WHO
BEN_ENRLD_ANTHR_PLIP_RT_F_WHO
HR_DM_SEQUENCE_DEFINITIONS_WHO
HR_DM_SEQUENCE_RANGES_WHO
BEN_ENRT_BNFT_WHO
OTA_TEST_QUESTIONS_WHO
BEN_ENRT_PREM_WHO
BEN_ENRT_PREM_RBV_WHO
HR_EFC_ACTIONS_WHO
OTA_UTEST_QUESTIONS_WHO
OTA_UTEST_RESPONSES_WHO
OBJECT_NAME
BEN_ENRT_RT_WHO
HR_EFC_ROUNDING_ERRORS_WHO
BEN_ENRT_RT_RBV_WHO
HR_EFC_WORKER_AUDITS_WHO
BEN_EXTRA_INPUT_VALUES_WHO
HR_EXCEPTION_USAGES_WHO
BEN_EXT_CHG_EVT_LOG_WHO
HR_FORM_CANVASES_B_WHO
BEN_EXT_CRIT_CMBN_WHO
BEN_EXT_CRIT_PRFL_WHO
BEN_EXT_CRIT_TYP_WHO
OBJECT_NAME
BEN_EXT_CRIT_VAL_WHO
BEN_EXT_DATA_ELMT_WHO
BEN_EXT_DATA_ELMT_DECD_WHO
BEN_EXT_DATA_ELMT_IN_RCD_WHO
BEN_EXT_DFN_WHO
BEN_EXT_FILE_WHO
BEN_EXT_FLD_WHO
HR_FORM_DATA_GROUPS_B_WHO
BEN_EXT_INCL_CHG_WHO
BEN_EXT_INCL_DATA_ELMT_WHO
BEN_EXT_RCD_WHO
OBJECT_NAME
BEN_EXT_RCD_IN_FILE_WHO
BEN_EXT_RSLT_WHO
BEN_EXT_RSLT_DTL_WHO
BEN_EXT_RSLT_ERR_WHO
BEN_EXT_WHERE_CLAUSE_WHO
BEN_FL_TM_PT_TM_RT_F_WHO
BEN_GD_OR_SVC_TYP_WHO
BEN_GNDR_RT_F_WHO
BEN_GRADE_RT_F_WHO
HR_FORM_DATA_GROUP_ITEMS_WHO
BEN_HRLY_SLRD_RT_F_WHO
OBJECT_NAME
HR_FORM_ITEMS_B_WHO
BEN_HRS_WKD_IN_PERD_FCTR_WHO
BEN_HRS_WKD_IN_PERD_RT_F_WHO
BEN_JOB_RT_F_WHO
BEN_LBR_MMBR_RT_F_WHO
BEN_LEE_RSN_F_WHO
BEN_LEE_RSN_RL_F_WHO
BEN_LER_BNFT_RSTRN_CTFN_F_WHO
BEN_LER_BNFT_RSTRN_F_WHO
BEN_LER_CHG_DPNT_CVG_CTFN_WHO
BEN_LER_CHG_DPNT_CVG_F_WHO
OBJECT_NAME
BEN_LER_CHG_OIPL_ENRT_F_WHO
BEN_LER_CHG_OIPL_ENRT_RL_F_WHO
BEN_LER_CHG_PGM_ENRT_F_WHO
BEN_LER_CHG_PLIP_ENRT_F_WHO
BEN_LER_CHG_PLIP_ENRT_RL_F_WHO
BEN_LER_CHG_PL_NIP_ENRT_F_WHO
BEN_LER_CHG_PL_NIP_RL_F_WHO
BEN_LER_CHG_PTIP_ENRT_F_WHO
BEN_LER_ENRT_CTFN_F_WHO
BEN_LER_EXTRA_INFO_WHO
BEN_LER_F_WHO
OBJECT_NAME
HR_FORM_PROPERTIES_WHO
HR_FORM_TAB_PAGES_B_WHO
BEN_LER_INFO_TYPES_WHO
BEN_LER_PER_INFO_CS_LER_F_WHO
BEN_LER_RLTD_PER_CS_LER_F_WHO
BEN_LER_RQRS_ENRT_CTFN_F_WHO
BEN_LE_CLSN_N_RSTR_WHO
BEN_LGL_ENTY_RT_F_WHO
HR_FORM_TAB_STACKED_CANVAS_WHO
BEN_LOS_RT_F_WHO
HR_FORM_TEMPLATES_B_WHO
OBJECT_NAME
BEN_NO_OTHR_CVG_RT_F_WHO
BEN_OIPLIP_F_WHO
BEN_OPT_INFO_TYPES_WHO
BEN_ORG_UNIT_PRDCT_F_WHO
BEN_PAIRD_RT_F_WHO
BEN_PCT_FL_TM_FCTR_WHO
BEN_PCT_FL_TM_RT_F_WHO
BEN_PER_CM_F_WHO
BEN_PER_CM_F_RBV_WHO
BEN_PL_GD_R_SVC_CTFN_F_WHO
BEN_PL_PCP_WHO
OBJECT_NAME
BEN_PL_R_OIPL_PREM_BY_MO_F_WHO
BEN_PL_TYP_F_WHO
BEN_POPL_ENRT_TYP_CYCL_F_WHO
BEN_POPL_ORG_F_WHO
BEN_PPL_GRP_RT_F_WHO
HR_KI_CONTEXTS_WHO
BEN_PRTN_ELIG_PRFL_F_WHO
HR_KI_HIERARCHIES_WHO
BEN_PRTT_ANTHR_PL_RT_F_WHO
BEN_PRTT_ASSOCD_INSTN_F_WHO
BEN_PRTT_CLM_GD_OR_SVC_TYP_WHO
OBJECT_NAME
BEN_PRTT_ENRT_ACTN_F_WHO
BEN_PRTT_ENRT_CTFN_PRVDD_F_WHO
BEN_PRTT_ENRT_RSLT_F_RBV_WHO
BEN_PRTT_PREM_BY_MO_F_WHO
BEN_PRTT_PREM_F_WHO
BEN_PRTT_REIMBMT_RECON_WHO
BEN_PRTT_REIMBMT_RQST_F_WHO
BEN_PRTT_RMT_APRVD_FR_PYMT_WHO
BEN_PRTT_RMT_RQST_CTFN_PRV_WHO
BEN_PRTT_RT_VAL_CTFN_PRVDD_WHO
BEN_PRTT_RT_VAL_RBV_WHO
OBJECT_NAME
BEN_PSTL_ZIP_RT_F_WHO
BEN_PSTN_RT_F_WHO
BEN_PTD_BAL_TYP_F_WHO
BEN_PTD_LMT_F_WHO
BEN_PTIP_DPNT_CVG_CTFN_F_WHO
HR_KI_HIERARCHY_NODE_MAPS_WHO
HR_KI_INTEGRATIONS_WHO
BEN_PTIP_F_WHO
BEN_PTNL_LER_FOR_PER_WHO
BEN_PTNL_LER_FOR_PER_RBV_WHO
BEN_PYMT_CHECK_DET_WHO
OBJECT_NAME
BEN_PYMT_SCHED_PY_FREQ_WHO
BEN_PYRL_RT_F_WHO
BEN_PY_BSS_RT_F_WHO
BEN_QUAL_TITL_RT_F_WHO
BEN_QUA_IN_GR_RT_F_WHO
BEN_REGN_F_WHO
BEN_REGN_FOR_REGY_BODY_F_WHO
HR_KI_OPTIONS_WHO
BEN_REPORTING_WHO
BEN_RLTD_PER_CHG_CS_LER_F_WHO
BEN_ROLL_REIMB_RQST_WHO
OBJECT_NAME
BEN_RPTG_GRP_WHO
HR_KI_SESSIONS_WHO
HR_KI_TOPICS_WHO
BEN_SCHEDD_ENRT_RL_F_WHO
BEN_SCHEDD_HRS_RT_F_WHO
HR_LEGISLATION_INSTALLATIO_WHO
HR_LEGISLATION_SUB_INST_WHO
BEN_STARTUP_CM_TYP_WHO
HR_LOCATION_INFO_TYPES_WHO
BEN_STARTUP_LERS_WHO
BEN_STARTUP_REGN_WHO
OBJECT_NAME
BEN_SVC_AREA_F_WHO
BEN_TTL_CVG_VOL_RT_F_WHO
BEN_TTL_PRTT_RT_F_WHO
BEN_VRBL_RT_PRFL_RL_F_WHO
BEN_WTHN_YR_PERD_WHO
HR_PATTERN_EXCEPTIONS_WHO
BEN_WV_PRTN_RSN_CTFN_PL_F_WHO
HR_PATTERN_PURPOSES_WHO
HR_PATTERN_PURPOSE_USAGES_WHO
BEN_WV_PRTN_RSN_PL_F_WHO
BEN_WV_PRTN_RSN_PTIP_F_WHO
OBJECT_NAME
HR_PUMP_BATCH_HEADERS_WHO
BEN_YR_PERD_WHO
HR_PUMP_BATCH_LINE_USER_KE_WHO
HR_PUMP_DEFAULT_EXCEPTIONS_WHO
HR_PUMP_MAPPING_PACKAGES_WHO
HR_PUMP_MODULE_PARAMETERS_WHO
HR_QUEST_ANSWERS_WHO
HR_QUEST_ANSWER_VALUES_WHO
HR_QUEST_FIELDS_WHO
HR_REPORT_LOOKUPS_WHO
HR_SOFT_CODING_KEYFLEX_WHO
OBJECT_NAME
HR_SOURCE_FORM_TEMPLATES_WHO
HR_SUMMARY_WHO
HR_TAB_PAGE_PROPERTIES_B_WHO
HR_TEMPLATE_CANVASES_B_WHO
HR_TEMPLATE_DATA_GROUPS_WHO
HR_TEMPLATE_ITEMS_B_WHO
HR_TEMPLATE_ITEM_CONTEXTS_WHO
HR_TEMPLATE_ITEM_CONTEXT_P_WHO
HR_TEMPLATE_ITEM_TAB_PAGES_WHO
HR_TEMPLATE_TAB_PAGES_B_WHO
HR_TEMPLATE_WINDOWS_B_WHO
OBJECT_NAME
HR_WINDOW_PROPERTIES_B_WHO
HR_WIP_LOCKS_WHO
HR_WIP_TRANSACTIONS_WHO
IRC_ALL_RECRUITING_SITES_WHO
IRC_ASSIGNMENT_STATUSES_WHO
IRC_DEFAULT_POSTINGS_WHO
IRC_DOCUMENTS_WHO
IRC_NOTIFICATION_PREFERENC_WHO
IRC_POSTING_CONTENTS_WHO
IRC_REC_TEAM_MEMBERS_WHO
IRC_REFERENCES_WHO
OBJECT_NAME
IRC_VACANCY_CONSIDERATIONS_WHO
IRC_VAC_ALLOWED_STATUS_TYP_WHO
IRC_VARIABLE_COMP_ELEMENTS_WHO
PAY_ACCRUAL_BANDS_WHO
PAY_ACTION_INFORMATION_WHO
PAY_ALL_PAYROLLS_F_WHO
PAY_AU_MODULES_WHO
PAY_AU_MODULE_PARAMETERS_WHO
PAY_AU_PROCESS_MODULES_WHO
PAY_BALANCE_CATEGORIES_F_WHO
PAY_BALANCE_CLASSIFICATION_WHO
OBJECT_NAME
PAY_BALANCE_FEEDS_F_WHO
PAY_BALANCE_TYPES_WHO
PAY_BAL_ATTRIBUTE_DEFINITI_WHO
PAY_CALENDARS_WHO
PAY_CA_EMP_FED_TAX_INFO_F_WHO
PAY_COST_ALLOCATION_KEYFLE_WHO
PAY_DATETRACKED_EVENTS_WHO
PAY_DEFINED_BALANCES_WHO
PAY_DIMENSION_ROUTES_WHO
PAY_ELEMENT_CLASSIFICATION_WHO
PAY_ELEMENT_SETS_WHO
OBJECT_NAME
PAY_ELEMENT_SPAN_USAGES_WHO
PAY_ELEMENT_TEMPLATES_WHO
PAY_ELEMENT_TYPE_EXTRA_INF_WHO
PAY_ELEMENT_TYPE_INFO_TYPE_WHO
PAY_ELEMENT_TYPE_USAGES_F_WHO
PAY_ELE_CLASSIFICATION_RUL_WHO
PAY_EVENT_QUALIFIERS_F_WHO
PAY_EVENT_UPDATES_WHO
PAY_EVENT_VALUE_CHANGES_F_WHO
PAY_EXTERNAL_ACCOUNTS_WHO
PAY_FORMULA_RESULT_RULES_F_WHO
OBJECT_NAME
PAY_FREQ_RULE_PERIODS_WHO
PAY_FUNCTIONAL_USAGES_WHO
PAY_GROSSUP_BAL_EXCLUSIONS_WHO
PAY_IE_PAYE_DETAILS_F_WHO
PAY_INPUT_VALUES_F_WHO
PAY_ITERATIVE_RULES_F_WHO
PAY_JP_BANKS_WHO
PAY_LEG_SETUP_DEFAULTS_WHO
PAY_SHADOW_BALANCE_FEEDS_WHO
PAY_SHADOW_BALANCE_TYPES_WHO
PAY_TRIGGER_COMPONENTS_WHO
OBJECT_NAME
PAY_TRIGGER_EVENTS_WHO
PAY_USER_ROWS_F_WHO
PAY_US_CONTRIBUTION_HISTOR_WHO
PAY_US_GARN_FEE_RULES_F_WHO
PAY_US_GARN_LIMIT_RULES_F_WHO
PAY_ZA_CDV_PARAMETERS_WHO
PER_ABSENCE_ATTENDANCES_WHO
PER_ABSENCE_ATTENDANCE_TYP_WHO
PER_ABS_ATTENDANCE_REASONS_WHO
PER_ASSESSMENT_TYPES_WHO
PER_ASSIGNMENT_BUDGET_VALU_WHO
OBJECT_NAME
PER_ASSIGN_PROPOSAL_ANSWER_WHO
PER_BF_BALANCE_AMOUNTS_WHO
PER_BF_BALANCE_TYPES_WHO
PER_BF_PAYROLL_RUNS_WHO
PER_BF_PROCESSED_ASSIGNMEN_WHO
PER_BOOKINGS_WHO
PER_BUDGETS_WHO
PER_BUDGET_ELEMENTS_WHO
PER_BUDGET_VALUES_WHO
PER_BUDGET_VERSIONS_WHO
PER_CAGR_APIS_WHO
OBJECT_NAME
PER_CAGR_API_PARAMETERS_WHO
PER_CAGR_ENTITLEMENTS_WHO
PER_CAGR_ENTITLEMENT_ITEMS_WHO
PER_CAGR_ENTITLEMENT_LINES_WHO
PER_CAGR_ENTITLEMENT_RESUL_WHO
PER_CAGR_GRADES_WHO
PER_CAGR_GRADES_DEF_WHO
PER_CAGR_GRADE_STRUCTURES_WHO
PER_CAGR_LOG_WHO
PER_CAGR_RETAINED_RIGHTS_WHO
PER_CALENDAR_ENTRIES_WHO
OBJECT_NAME
PER_CAL_ENTRY_VALUES_WHO
PER_CAREER_PATHS_WHO
PER_CAREER_PATH_ELEMENTS_WHO
PER_CHECKLIST_ITEMS_WHO
PER_COBRA_COVERAGE_BENEFIT_WHO
PER_COBRA_COVERAGE_PERIODS_WHO
PER_COBRA_COVERAGE_STATUSE_WHO
PER_COBRA_COV_ENROLLMENTS_WHO
PER_COBRA_DEPENDENTS_F_WHO
PER_COBRA_QFYING_EVENTS_F_WHO
PER_COLLECTIVE_AGREEMENTS_WHO
OBJECT_NAME
PER_COMPETENCES_WHO
PER_COMPETENCE_DEFINITIONS_WHO
PER_COMPETENCE_ELEMENTS_WHO
PER_CONTACT_EXTRA_INFO_F_WHO
PER_CONTACT_INFO_TYPES_WHO
PER_CONTRACTS_F_WHO
PER_DEPLOYMENT_FACTORS_WHO
PER_DISABILITIES_F_WHO
PER_ELECTIONS_WHO
PER_ELECTION_CANDIDATES_WHO
PER_ELECTION_CONSTITUENCYS_WHO
OBJECT_NAME
PER_EMPDIR_ASSIGNMENTS_WHO
PER_EMPDIR_IMAGES_WHO
PER_EMPDIR_PEOPLE_WHO
PER_EMPDIR_PHONES_WHO
PER_ESTABLISHMENTS_WHO
PER_ESTABLISHMENT_ATTENDAN_WHO
PER_GEN_HIERARCHY_WHO
PER_GEN_HIERARCHY_NODES_WHO
PER_GEN_HIERARCHY_VERSIONS_WHO
PER_GEN_HIER_NODE_TYPES_WHO
PER_GRADES_WHO
OBJECT_NAME
PER_GRADE_DEFINITIONS_WHO
PER_GRADE_SPINES_F_WHO
PER_HTML_TOOLKIT_REC_TYPES_WHO
PER_JOB_EVALUATIONS_WHO
PER_JOB_EXTRA_INFO_WHO
PER_JOB_GROUPS_WHO
PER_JOB_INFO_TYPES_WHO
PER_JOB_REQUIREMENTS_WHO
PER_JP_ADDRESS_LOOKUPS_WHO
PER_JP_BANK_LOOKUPS_ALL_WHO
PER_JP_POSTAL_CODES_WHO
OBJECT_NAME
PER_KR_GRADES_WHO
PER_KR_GRADE_AMOUNT_F_WHO
PER_KR_G_POINTS_WHO
PER_KR_G_POINT_AMOUNT_F_WHO
PER_MEDICAL_ASSESSMENTS_WHO
PER_MM_VALID_GRADES_WHO
PER_NL_ABSENCE_ACTIONS_WHO
PER_OBJECTIVES_WHO
PER_ORGANIZATION_STRUCTURE_WHO
PER_ORG_HRCHY_SUMMARY_WHO
PER_ORG_STRUCTURE_ELEMENTS_WHO
OBJECT_NAME
PER_PARENT_SPINES_WHO
PER_PARTICIPANTS_WHO
PER_PAY_BASES_WHO
PER_PAY_PROPOSAL_COMPONENT_WHO
PER_PEOPLE_INFO_TYPES_WHO
PER_PERFORMANCE_RATINGS_WHO
PER_PERFORMANCE_REVIEWS_WHO
PER_PERIODS_OF_PLACEMENT_WHO
PER_PERSON_DLVRY_METHODS_WHO
PER_PERSON_TYPE_USAGES_F_WHO
PER_POSITION_DEFINITIONS_WHO
OBJECT_NAME
PER_POSITION_EXTRA_INFO_WHO
PER_POSITION_INFO_TYPES_WHO
PER_POS_STRUCTURE_ELEMENTS_WHO
PER_POS_STRUCTURE_VERSIONS_WHO
PER_PREVIOUS_EMPLOYERS_WHO
PER_PREVIOUS_JOBS_WHO
PER_PREVIOUS_JOB_USAGES_WHO
PER_PREV_JOB_EXTRA_INFO_WHO
PER_PREV_JOB_INFO_TYPES_WHO
PER_PROPOSAL_CATEGORY_MEMB_WHO
PER_PROPOSAL_CATEGORY_TYPE_WHO
OBJECT_NAME
PER_PROPOSAL_OFFER_PARAGRA_WHO
PER_PROPOSAL_QUESTIONS_ADV_WHO
PER_PROPOSAL_QUESTION_MEMB_WHO
PER_PROPOSAL_QUESTION_TYPE_WHO
PER_PROPOSAL_TEMPLATES_WHO
PER_QUALIFICATION_TYPES_WHO
PER_QUICKPAINT_INVOCATIONS_WHO
PER_QUICKPAINT_RESULT_TEXT_WHO
PER_RATING_LEVELS_WHO
PER_RATING_SCALES_WHO
PER_RECRUITMENT_ACTIVITIES_WHO
OBJECT_NAME
PER_RECRUITMENT_ACTIVITY_F_WHO
PER_REQUISITIONS_WHO
PER_RI_DEPENDENCIES_WHO
PER_RI_REQUESTS_WHO
PER_RI_SETUP_SUB_TASKS_WHO
PER_RI_SETUP_TASKS_WHO
PER_RI_VIEW_REPORTS_WHO
PER_RI_WORKBENCH_ITEMS_WHO
PER_ROLES_WHO
PER_SCHED_COBRA_PAYMENTS_WHO
PER_SECONDARY_ASS_STATUSES_WHO
OBJECT_NAME
PER_SECURITY_ORGANIZATIONS_WHO
PER_SECURITY_PROFILES_WHO
PER_SECURITY_USERS_WHO
PER_SHARED_TYPES_WHO
PER_SOLUTION_TYPES_WHO
PER_SPINAL_POINT_PLACEMENT_WHO
PER_STANDARD_HOLIDAYS_WHO
PER_TIME_PERIODS_WHO
PER_TIME_PERIOD_RULES_WHO
PER_WORK_INCIDENTS_WHO
PER_ZA_AREAS_OF_ASSESSMENT_WHO
OBJECT_NAME
PER_ZA_QUALIFICATION_TYPES_WHO
PER_ZA_TRAINING_WHO
PQH_ATTRIBUTE_RANGES_WHO
PQH_BDGT_CMMTMNT_ELMNTS_WHO
PQH_BUDGET_DETAILS_WHO
PQH_BUDGET_ELEMENTS_WHO
PQH_BUDGET_FUND_SRCS_WHO
PQH_BUDGET_GL_FLEX_MAPS_WHO
PQH_BUDGET_POOLS_WHO
PQH_BUDGET_SETS_WHO
PQH_COPY_ENTITY_CONTEXTS_WHO
OBJECT_NAME
PQH_COPY_ENTITY_FUNCTIONS_WHO
PQH_COPY_ENTITY_TXNS_WHO
PQH_CORPS_DEFINITIONS_WHO
PQH_DE_CASE_GROUPS_WHO
PQH_DE_ENT_MINUTES_WHO
PQH_DE_OPERATION_GROUPS_WHO
PQH_DE_RESULT_SETS_WHO
PQH_DE_WRKPLC_VLDTN_JOBS_WHO
PQH_DE_WRKPLC_VLDTN_LVLNUM_WHO
PQH_DE_WRKPLC_VLDTN_VERS_WHO
PQH_DFLT_BUDGET_ELEMENTS_WHO
OBJECT_NAME
PQH_DFLT_BUDGET_SETS_WHO
PQH_DOCUMENT_ATTRIBUTES_F_WHO
PQH_ELEMENT_COMMITMENTS_WHO
PQH_FR_GLOBAL_INDICES_F_WHO
PQH_FR_STAT_SITUATION_RULE_WHO
PQH_FR_VALIDATIONS_WHO
PQH_GL_INTERFACE_WHO
PQH_PROCESS_LOG_WHO
PQH_ROLE_INFO_TYPES_WHO
PQH_SS_STEP_HISTORY_WHO
PQH_TABLE_ROUTE_WHO
OBJECT_NAME
PQH_TEMPLATES_WHO
PQH_TEMPLATE_ATTRIBUTES_WHO
PQH_TJR_SHADOW_WHO
PQH_TRANSACTION_CATEGORIES_WHO
PQH_TRANSACTION_TEMPLATES_WHO
PQH_TXN_CATEGORY_ATTRIBUTE_WHO
PQH_TXN_CATEGORY_DOCUMENTS_WHO
PQH_TXN_JOB_REQUIREMENTS_WHO
PQH_WIZARD_CANVASES_WHO
PQH_WORKSHEETS_WHO
PQH_WORKSHEET_BDGT_ELMNTS_WHO
OBJECT_NAME
PQH_WORKSHEET_BUDGET_SETS_WHO
PQH_WORKSHEET_DETAILS_WHO
PQH_WORKSHEET_FUND_SRCS_WHO
PQH_WORKSHEET_PERIODS_WHO
PQP_ALIEN_STATE_TREATIES_F_WHO
PQP_ALIEN_TRANSACTION_DATA_WHO
PQP_ANALYZED_ALIEN_DATA_WHO
PQP_ANALYZED_ALIEN_DETAILS_WHO
PQP_ASSIGNMENT_ATTRIBUTES_WHO
PQP_CONFIGURATION_VALUES_WHO
PQP_EXCEPTION_REPORTS_WHO
OBJECT_NAME
PQP_EXCEPTION_REPORT_GROUP_WHO
PQP_EXCEPTION_REPORT_SUFFI_WHO
PQP_EXTRACT_ATTRIBUTES_WHO
PQP_EXT_CROSS_PERSON_RECOR_WHO
PQP_GAP_ABSENCE_PLANS_WHO
PQP_GAP_DAILY_ABSENCES_WHO
PQP_PENSION_TYPES_F_WHO
PQP_SERVICE_HISTORY_PERIOD_WHO
PQP_VEHICLE_ALLOCATIONS_F_WHO
PQP_VEHICLE_DETAILS_WHO
PQP_VEHICLE_REPOSITORY_F_WHO
OBJECT_NAME
PQP_VEH_ALLOC_EXTRA_INFO_WHO
PQP_VEH_ALLOC_INFO_TYPES_WHO
PQP_VEH_REPOS_EXTRA_INFO_WHO
PQP_VEH_REPOS_INFO_TYPES_WHO
PAY_EXTERNAL_ACCOUNTS_ARUD
PAY_ORG_PAYMENT_METHODS_F_ARIU
PAY_US_EMP_STATE_TAX_RULES_WHO
PER_PHONES_WHO
PER_TIME_PERIOD_TYPES_WHO
HXC_ALIAS_DEFINITION012501_WHO
OTA_ACTIVITY_DEFINIT012501_WHO
OBJECT_NAME
OTA_ACTIVITY_VERSION012509_WHO
HXC_TRANSACTION_DETAILS_BK_WHO
OTA_OFFERINGS_TL012523_WHO
HRI_ARCHIVE_EVENTS_WHO
OTA_SUPPLIABLE_RESOU012528_WHO
BEN_ACTN_TYP_TL012642_WHO
DT_DATE_PROMPTS_TL012652_WHO
DT_TITLE_PROMPTS_TL012653_WHO
BEN_CM_TYP_F_TL012655_WHO
GHR_COMPL_AGENCY_COSTS_WHO
GHR_MASS_SALARY_CRITERIA_E_WHO
OBJECT_NAME
GHR_MTS_TEMP_WHO
HR_ALL_ORGANIZATION_012716_WHO
HR_ALL_POSITIONS_F_T012716_WHO
HR_FORM_CANVASES_TL012728_WHO
HR_FORM_DATA_GROUPS_012729_WHO
BEN_EXT_FLD_TL012730_WHO
HR_FORM_ITEMS_TL012730_WHO
HR_FORM_TAB_PAGES_TL012731_WHO
HR_FORM_TEMPLATES_TL012732_WHO
HR_FORM_WINDOWS_TL012733_WHO
HR_ITEM_PROPERTIES_T012734_WHO
OBJECT_NAME
HR_KI_HIERARCHIES_TL012736_WHO
BEN_LER_F_TL012736_WHO
HR_KI_INTEGRATIONS_T012736_WHO
HR_KI_OPTION_TYPES_T012737_WHO
HR_KI_TOPICS_TL012738_WHO
HR_NAVIGATION_UNITS_012740_WHO
HR_ORG_INFORMATION_T012741_WHO
HR_TAB_PAGE_PROPERTI012748_WHO
BEN_RPTG_GRP_TL012758_WHO
PAY_CUSTOM_RESTRICTI012802_WHO
PAY_ORG_PAYMENT_METH012813_WHO
OBJECT_NAME
PER_ASSIGNMENT_STATU012832_WHO
PER_COMPETENCES_TL012842_WHO
PAY_ACTION_PARAMETERS_ARI
PAY_ACTION_PARAMETERS_ARU
PA_MAITN_ORG_UPDATE_BEST
PA_MAITN_ORG_UPDATE_BEROW
JA_IN_57F4_FORM_NUMBER_AIU_TRG
XXXX_APPS_LOGON_TRG
767 rows selected.

JBO-27022 within ADF Module, JHeadstart 10

(oracle.jbo.AttributeLoadException) JBO-27022: Failed to load value at index 4 with java object of type java.lang.String due to java.sql.SQLException.
LEVEL 1: DETAIL 0
(java.sql.SQLException) Fail to convert to internal representation
The above is the error message received from within the ADF Module executed with Test. Using JDeveloper 10.1.3 4 with the latest Jheadstart 10 release. The application and ADF definitions are simple - one entity and six views of that entity differing only on a where clause which has the same form in all cases: "where status_ind = 'value'".
It is failing attempting to read the 10th record, having successfully read the first 9 records. For testing purposes (to isolate this problem) I constructed the test data from the original data. Using the original data, the test of the module failed on the 5th record. The original records contains a single integer surrogate key that is populated via an Oracle sequence number referenced within an Insert Trigger on the database. To determine if the failure was based on the record or the number of records read, I constructed the test data such that from the original data as follows:
Record 1, record 1, record 2, record 2, record 3, record 3, record 4, record 4, record 5, record 5 ...., where the record # refers to the original data. The Test of the Module again fails on the 5th record's data, but it read the 1st Record 5 correctly, while failing on the 2nd Record 5. Since these records are or should be identical, except for the integer sequence number field (which is in index 10 -- that is the key is not in index position 4).
The field in Index 4 is a varchar2(30) and whose value is BAV (that is, only 3 characters long, no padding). The base classes remain the standard oracle.jbo.xxxx classes and not any jhs classes.
I'm at a loss why the exception, especially since the fields contents are the same between Record 9 and Record 10, with the primary key of integer 9 and 10 respectively.
NB: Running under Mac OSX 10.5.7 and latest JVM 1.5 from Apple

Hi,
Jhsadfrt contains all the runtime components for JHS. For the model layer, this includes the JhsApplicationModuleImpl (which will be used as the superclass for your appmodule) and the JhsModelService, which will be used as a nested application module within your applicaton module. The last one will only be used when you use database-dynamic options such as flex fields, custom security and database-based internationalization. In those cases, JHeadstart provides its own screens which will use these business components to display their data.
Libraries such as Commons Logging, Oracle Intermedia and SQLJ Runtime (allthough I'm not 100% sure of the last) are used by these JHeadstart extensions to the model. So you will need them, otherwise your project might fail to run.
Hope this answers your question.
Regards,
Evert-Jan de Bruin
JHeadstart Team

System.trigger_item

I tried to catch the name of block ,record and item from which the trigger fire .I wrote the following on the form level :
message(:system.trigger_block||' _ '||:system.trigger_record || ' _ '||:system.trigger_item);
it displayed the block and record names only but nothing for item name .In the other hand it displayed the name of the item with when mouse click.I wonder why it works with this trigger while it didn't with on-error trigger .
Any help would be thinkfull

This is from the Forms on-line help:
SYSTEM.CURSOR_ITEM - represents the name of the block and item, block.item, where the input focus (cursor) is located.
SYSTEM.TRIGGER_ITEM - represents the item (BLOCK.ITEM) in the scope for which the trigger is currently firing. When referenced in a key trigger, it represents the item where the cursor was located when the trigger began. The value is always a character string.
SYSTEM.TRIGGER_ITEM remains the same from the beginning to the end of given trigger. This differs from SYSTEM.CURSOR_ITEM, which may change within a given trigger when navigation takes place.

Use of "DBA_OBJECTS" in "AFTER CREATE" Trigger

Hi,
We would like to store some extra information about our objects we have in the database. To do so we tought of the idea of creating a 'documenting' table containing an object_id that references to the object_id from the view dba_views.
Now we want to automatically create a new record in our documenting table when a new object is created, in the first stage this should only contain the object_id
To accomplish this we are using an 'AFTER CREATE' trigger, but when this trigger fires and the code searches for the new object_id in dba_objects, it does not return any records and generates an error. Likely because when the trigger is executed, the view is not yet updated?
create or replace
TRIGGER TRG_TEST
AFTER CREATE ON SCOTT.SCHEMA
DECLARE
tmp VARCHAR2(50);
BEGIN
dbms_output.put_line(ora_dict_obj_name);
select object_id
into tmp
from dba_objects
where object_name = ora_dict_obj_name;
dbms_output.put_line(tmp);
END;
Error report:
ORA-04088: Fout bij uitvoering van trigger 'SCOTT.TRG_TEST'.
ORA-01403: Geen gegevens gevonden.
ORA-06512: in regel 6
04088. 00000 - "error during execution of trigger '%s.%s'"
*Cause:    A runtime error occurred during execution of a trigger.
*Action:   Check the triggers which were involved in the operation.
It's in dutch, so I'll have a go at translating:
Error report:
ORA-04088: Exception while executing trigger 'SCOTT.TRG_TEST'.
ORA-01403: No data found
ORA-06512: in rule 6
04088. 00000 - "error during execution of trigger '%s.%s'"
*Cause:    A runtime error occurred during execution of a trigger.
*Action:   Check the triggers which were involved in the operation.
Does anyone have an idea of how I can accomplish what I'm trying to do here.. Or maybe something I'm doing wrong?
Thanks in advance!
Davy

What is "ora_dict_obj_name" defined as?
Another option might be to setup a DBMS_SCHEDULER job to run the following insert
firstly though, create the following table ;
create document_table as (select * from dba_objects where rownum < 1)and then setup a DBMS_SCHEDULER job to run the following:
begin
insert into document_table
(select dbo.*
   from   dba_objects    dbo
         ,document_Table dtb
   where dbo.Object_ID = dtb.Object_ID(+)
   and    dtb.Object_ID is null);
   commit;
   exception
    when others then
      rollback;
      -- log a message somewhere with the error, i.e. SQLERRM
end;
/Note, I specified all columns, but you'll probably specify explicitly which column you require, in which case the CREATE table would change as well.
Then you won't have a need for any trigger, and can better manage when you want your documentation to be updated.
Another option might be to use COMMENT, which can be used on tables, views, materialized views, but won't cover all objects
to the extent you might want.
SQL> desc emp2
Name
EMPNO
JOB
START_DATE
SAL
DEPT
END_DATE
SQL> comment on column emp2.sal is 'Existing Salary of employee as paid at most recent month end';

Trigger & Mutating Tables (Parent-Child relationship, Referencing Constraint related)

Dear Sir,
Wish you a very Happy New Year !!!
I am facing a problem related to Database Trigger.
Sir, I have two tables Cust and Sick.
Cust is having the following fields :
SDF_CUST_BRCD NOT NULL NUMBER(5)
CUST_CUSTID NOT NULL VARCHAR2(6)
UCD_CUST_SEGMENTCODE NOT NULL VARCHAR2(7)
CUST_FIRSTBORROWER NOT NULL VARCHAR2(30)
UCD_CUST_CONSTORGCODE NOT NULL VARCHAR2(7)
VLGC_CUST_VILLAGECODE VARCHAR2(4)
CUST_PAN VARCHAR2(20)
UCD_CUST_STAFFCODE VARCHAR2(7)
CUST_RESIDENTSTATFLAG VARCHAR2(1)
CUST_BKGSINCEDATE DATE
UCD_CUST_SICKUNITCODE VARCHAR2(7)
Cust's Primary Key is the combination of Brcd, CustId
And Sick Table Structure is as under :
PRDT_SICK_REPORTDATE NOT NULL DATE
CUST_SICK_BRCD NOT NULL NUMBER(5)
CUST_SICK_CUSTID NOT NULL VARCHAR2(6)
UCD_SICK_REASONCODE NOT NULL VARCHAR2(7)
SICK_SINCEDATE NOT NULL DATE
SICK_LOSSMAKINGDATE DATE
SICK_ACCMLOSSAMT NUMBER(16,2)
UCD_SICK_VIABILITYCODE NOT NULL VARCHAR2(7)
UCD_BIFR_STATUS_CODE VARCHAR2(7)
SICK_BIFRDATE DATE
SICK_REHABSANCDATE DATE
CUST_SICK_SICKUNITCODE VARCHAR2(7)
Sick's Primary Key is the combination of ReportDate, BrCD, Custid
Sick's (Brcd and Custid) referencing to Cust (BrCd, CustId).
I want to insert/update into the sick table corrponding to Cust
Insertion/Updation.
I have written a trigger on Cust which is working fine provided
that foreign key constraint
is diabled. As soon as constraint is enabled the trigger is
giving error
ORA-04091: table CIS.CUST is mutating, trigger/function may not
see it
Sir, It is also working fine if the record is already exist in
Sick table.
Is is not working in 2 cases :
1. While entering a new record into the Cust with
SICKUNIT_CODE='SW00001'
2. If we are changing the SickUnit_Code in Cust and correponding
record doesn't exist in Sick.
Please write me the solution.
Thanking you
yours sincerely
Rajesh Kumar Jain
Trigger Text is
create or replace trigger tr_cust_sick
after insert or update on Cust for each row
declare
Fn_Return boolean;
Tr_Exception Exception;
begin
Fn_Return := Fn_cust_sick
(:new.UCD_CUST_SICKUNITCODE,:new.SDF_CUST_BRCD,:new.CUST_CUSTID,I
NSERTING,UPDATING,DELETING);
If Not Fn_Return then
Raise Tr_Exception;
End if;
exception
when Tr_Exception then
Dbms_output.put_line('Tr_Exception ' ||Sqlerrm);
When others then
Dbms_output.put_line(Sqlerrm);
end;
Function Text is :
$$$$$$$$$
create or replace function fn_cust_sick
(SickUnitCode_in In Cust.Ucd_Cust_SickunitCode%Type,Brcd_in In
Sdf.Sdf_Brcd%Type,Custid_in In Cust.Cust_Custid%
Type,Inserting_in In Boolean ,Updating_in In Boolean,Deleting_in
In Boolean)
return boolean is
ddate date default '01-Jul-1955';
repdate ppar.ppar_reportdate%type default '31-Mar-2001';
viabcode sick.ucd_sick_viabilitycode%type default 'VI00000';
ReasonCD sick.ucd_sick_reasoncode%type default 'SK00000';
Ret_Flag Boolean := False;
begin
if Updating_in then
begin
update sick
set CUST_SICK_SICKUNITCODE = SickUnitCode_in
where prdt_sick_reportdate = repdate and
cust_sick_brcd = Brcd_in and
Cust_Sick_CustId = Custid_in;
     Ret_Flag := True;
if sql%notfound then
if To_Number(Substr(SickUnitCode_in,3)) > 0 then
insert into sick
(PRDT_SICK_REPORTDATE,
CUST_SICK_BRCD,
CUST_SICK_CUSTID,
UCD_SICK_REASONCODE,
SICK_SINCEDATE,
UCD_SICK_VIABILITYCODE,
CUST_SICK_SICKUNITCODE,
          SUBO_SICK_SICKBORRCODE)
values
(repdate,
Brcd_in,
Custid_in,
reasoncd,
ddate,
viabcode,
SickUnitCode_in,
          'SB00001');
Ret_Flag := True;
     Return(Ret_Flag);
     end if;
end if;
exception
when others then
dbms_output.put_line('Exception Update '|| Sqlerrm);
return(Ret_Flag);
end;
elsif Inserting_in then
begin
if To_Number(Substr(SickUnitCode_in,3)) > 0 then
insert into sick
(PRDT_SICK_REPORTDATE,
CUST_SICK_BRCD,
CUST_SICK_CUSTID,
UCD_SICK_REASONCODE,
SICK_SINCEDATE,
UCD_SICK_VIABILITYCODE,
CUST_SICK_SICKUNITCODE,
          SUBO_SICK_SICKBORRCODE)
values
(repdate,
Brcd_in,
Custid_in,
reasoncd,
ddate,
viabcode,
SickUnitCode_in,
          'SB00001');
Ret_Flag := True;
end if;
     Return(Ret_Flag);
exception
when others then
dbms_output.put_line('Exception Insert '|| Sqlerrm);
return(Ret_Flag);
end;
end if;
return(Ret_Flag);
exception
when Others then
dbms_output.put_line('Main Exception '|| Sqlerrm);
return(Ret_Flag);
end;
$$$$$$$$$$$

Hi,
double click the Application Module to open the AM editor. Select the data Model category. On the right hand side you see what is selected for use in an application, on the left hand side is what you have available as View Object. To create T1-->T2-->T3, you
- Select T1 and move it to the right
- Select T2 under T1 on the left and move it to the right under T1
- Select T3 under T2 on the left and move it under T2 in T1 on the right
Frank

Create trigger if referenced column from other db not exists

I have such scenario: there are two databases DB1 and DB2.
DB1 has table MyTable and new column was added NewCol.
On the DB2 table a trigger was created that updates DB1.MyTable.NewCol.
Both scripts generated by SSDT are correct but the problem is during deployment. I have an automation tool which executes publish scripts in a predefined order. In this case DB2 is executed first and the scripts fails because referenced column from DB1 doesn't
exist yet.
Do you have any idea how to overcome this issue? Off course I could change an order in which scripts are executed and create DB1 before DB2. But in other scenario I could have a cross reference dependency and I am afraid there is no use for SSDT in such
case.

I found a workaround. The solution is to handle it manually in an pre-deployment script.
In this scenario I added pre-deployment script for DB2 to check if new column exists in DB1 and if not then create it.
IF (OBJECT_ID('ATC.dbo.tblDisplayStatusOverview') IS NOT NULL)
BEGIN
   PRINT 'Checking if columns exists ATC.tblDisplayStatusOverview.IPAddress...'
   IF (COL_LENGTH('ATC.dbo.tblDisplayStatusOverview', 'IPAddress') IS NULL)
   BEGIN
       PRINT 'Adding column ATC.tblDisplayStatusOverview.IPAddress...'
       ALTER TABLE ATC.dbo.tblDisplayStatusOverview
           ADD [IPAddress] VARCHAR (15) NULL;
   END
END

REFERENCING PARENT clause of CREATE TRIGGER

Hi All-
I have a mystery. Create Trigger, described in my "Oracle 8i: The Complete Reference" (Pg 1046-7 in my) book includes a syntax diagram which shows
REFERENCING OLD AS ...
REFERENCING NEW AS ...
REFERENCING PARENT AS ...
All as valid referencing clauses. OLD and NEW are discussed in the text, but PARENT is not.
What does this do? I am trying to solve a problem and this may apply.
Thanks for any advice!!!
David
luked(at--no spam please)bigfoot.com

Hi
'If the trigger is defined on a nested table, OLD and NEW refer to the row of the
nested table, and PARENT refers to the current row of the parent table.'
This sentence is from SQL Reference. I never used parent in my practice.
Regards
null

Referencing the entire row in an insert trigger

I am trying to replace having to do the following sort of queries repeatedly by using a trigger to handle the second 2:
My first query inserts a row and the following 2 queries insert a reference to that row into 2 other tables
so I want to create a trigger which will insert the reference into the 2 other tables.
my problem: how do I get this reference in the trigger? I know I can get individual values using :NEW.Column but I can't seem to figure out how to get the whole row.
I can't select the row because its inside the trigger responding to it being inserted so I'd get that mutator error.

Not sure why I sql*plus gives those errors. I get the same.
When I tried to use
print_obj(:new.object_value);
heres the results
SQL> CREATE OR REPLACE TRIGGER TR_BOOKING_INS AFTER INSERT ON BOOKING
2 FOR EACH ROW
3 DECLARE
4 ecode NUMBER(38);
5 thisproc CONSTANT VARCHAR2(50) := 'trap_errmesg';
6
7 BEGIN
8 print_obj(:new.object_value);
9 EXCEPTION
10 WHEN OTHERS THEN
11 ecode := SQLCODE;
12 dbms_output.put_line(thisproc || ' - ' || ecode);
13 dbms_output.put_line('fucking errors');
14 END TR_BOOKING_INS;
15 /
Warning: Trigger created with compilation errors.
SQL> show err
Errors for TRIGGER TR_BOOKING_INS:
LINE/COL ERROR
6/5 PL/SQL: Statement ignored
6/5 PLS-00201: identifier 'PRINT_OBJ' must be declared
heres the results from 2 trigger attempts where I'm trying to do what I am wanting to do
SQL> CREATE OR REPLACE TRIGGER TR_BOOKING_INS
2 AFTER INSERT ON BOOKING
3 FOR EACH ROW
4 BEGIN
5 INSERT INTO TABLE(SELECT G.BOOKED_FOR FROM GUEST G WHERE G.GUEST_NO = :
NEW.GUEST_NO)
6 VALUES (:new.object_value);
7 EXCEPTION
8 WHEN OTHERS THEN
9 raise_application_error(-20001, 'Database Error');
10 END TR_BOOKING_INS;
11 /
Warning: Trigger created with compilation errors.
SQL> show err
Errors for TRIGGER TR_BOOKING_INS:
LINE/COL ERROR
2/5 PL/SQL: SQL Statement ignored
3/16 PL/SQL: ORA-00932: inconsistent datatypes: expected REF
DANIEL.BOOKING_TY got DANIEL.BOOKING_TY
SQL> CREATE OR REPLACE TRIGGER TR_BOOKING_INS
2 AFTER INSERT ON BOOKING
3 FOR EACH ROW
4 BEGIN
5 INSERT INTO TABLE(SELECT G.BOOKED_FOR FROM GUEST G WHERE G.GUEST_NO = :
NEW.GUEST_NO)
6 VALUES (REF(:new.object_value));
7 EXCEPTION
8 WHEN OTHERS THEN
9 raise_application_error(-20001, 'Database Error');
10 END TR_BOOKING_INS;
11 /
Warning: Trigger created with compilation errors.
SQL> show err
Errors for TRIGGER TR_BOOKING_INS:
LINE/COL ERROR
2/5 PL/SQL: SQL Statement ignored
3/19 PL/SQL: ORA-01747: invalid user.table.column, table.column, or
column specification
SQL>

Insert old missing data from one table to another(databaase trigger)

Hello,
i want to do two things
1)I want to insert old missing data from one table to another through a database trigger but it can't be executed that way i don't know what should i do in case of replacing old data in table_1 into table_2
2)what should i use :NEW. OR :OLD. instead.
3) what should i do if i have records exising between the two dates
i want to surpress the existing records.
the following code is what i have but no effect occured.
CREATE OR REPLACE TRIGGER ATTENDANCEE_FOLLOWS
AFTER INSERT ON ACCESSLOG
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
DECLARE
V_COUNT       NUMBER(2);
V_TIME_OUT    DATE;
V_DATE_IN     DATE;
V_DATE_OUT    DATE;
V_TIME_IN     DATE;
V_ATT_FLAG    VARCHAR2(3);
V_EMP_ID      NUMBER(11);
CURSOR EMP_FOLLOWS IS
SELECT   EMPLOYEEID , LOGDATE , LOGTIME , INOUT
FROM     ACCESSLOG
WHERE    LOGDATE
BETWEEN TO_DATE('18/12/2008','dd/mm/rrrr')
AND      TO_DATE('19/12/2008','dd/mm/rrrr');
BEGIN
FOR EMP IN EMP_FOLLOWS LOOP
SELECT COUNT(*)
INTO V_COUNT
FROM EMP_ATTENDANCEE
WHERE EMP_ID    = EMP.EMPLOYEEID
AND    DATE_IN   = EMP.LOGDATE
AND    ATT_FLAG = 'I';
IF V_COUNT = 0 THEN
INSERT INTO EMP_ATTENDANCEE (EMP_ID, DATE_IN ,DATE_OUT
                            ,TIME_IN ,TIME_OUT,ATT_FLAG)
     VALUES (TO_NUMBER(TO_CHAR(:NEW.employeeid,99999)),
             TO_DATE(:NEW.LOGDATE,'dd/mm/rrrr'),       -- DATE_IN
             NULL,
             TO_DATE(:NEW.LOGTIME,'HH24:MI:SS'),      -- TIME_IN
             NULL ,'I');
ELSIF   V_COUNT > 0 THEN
UPDATE EMP_ATTENDANCEE
    SET DATE_OUT       = TO_DATE(:NEW.LOGDATE,'dd/mm/rrrr'), -- DATE_OUT,
        TIME_OUT       =   TO_DATE(:NEW.LOGTIME,'HH24:MI:SS'), -- TIME_OUT
        ATT_FLAG       =   'O'
        WHERE EMP_ID   =   TO_NUMBER(TO_CHAR(:NEW.employeeid,99999))
        AND   DATE_IN <= (SELECT MAX (DATE_IN )
                           FROM EMP_ATTENDANCEE
                           WHERE EMP_ID = TO_NUMBER(TO_CHAR(:NEW.employeeid,99999))
                           AND   DATE_OUT IS NULL
                           AND   TIME_OUT IS NULL )
AND   DATE_OUT IS NULL
AND   TIME_OUT IS NULL ;
END IF;
END LOOP;
EXCEPTION
WHEN OTHERS THEN RAISE;
END ATTENDANCEE_FOLLOWS ;
                        Regards,
Abdetu..

INSERT INTO SALES_MASTER
   ( NO
   , Name
   , PINCODE )
   SELECT SALESMANNO
        , SALESMANNAME
        , PINCODE
     FROM SALESMAN_MASTER;Regards,
Christian Balz

Using if statement in a trigger to prevent autoincrement for a restore

I use the following trigger to simulate an autoincrement on the primary key id, each time a row is inserted:
CREATE OR REPLACE TRIGGER "ITPLAN".BI_VORHABEN BEFORE INSERT ON VORHABEN REFERENCING NEW AS NEW FOR EACH ROW
DECLARE
nKey NUMBER;
BEGIN
SELECT seq_vorhaben.NEXTVAL INTO nKey FROM dual;
:NEW.ID := nKey;
END;
now for a restore procedure, I want to keep the id of all rows, that are restored from an archive table. this trigger however will increment the value with each insert. Therefor I want to insert a condition that applies the trigger only if the ID value is null:
if (vorhaben.id is null) then :NEW.ID := nKey
unfortunately I get a compilation error. thanks for any help.

How about ...
CREATE OR REPLACE TRIGGER "ITPLAN".BI_VORHABEN
BEFORE INSERT ON VORHABEN
REFERENCING NEW AS NEW
FOR EACH ROW
WHEN (new.id IS NULL)
DECLARE
nKey NUMBER;
BEGIN
SELECT seq_vorhaben.NEXTVAL INTO nKey FROM dual;
:NEW.ID := nKey;
END;
/Actually, I'm not sure that the variable is needed, is it? Can you just do ...
CREATE OR REPLACE TRIGGER "ITPLAN".BI_VORHABEN
BEFORE INSERT ON VORHABEN
REFERENCING NEW AS NEW
FOR EACH ROW
WHEN (new.id IS NULL)
BEGIN
SELECT seq_vorhaben.NEXTVAL INTO :NEW.ID FROM dual;
END;
/

Referencing dba_objects in a trigger.

Similar Messages

Maybe you are looking for