oracle table handlers

This is regarding the custom form which i'll be registering in apps

I have created a form and the base table is a view.
The table is having around 70 columns and i have created view with rowid and all the columns from the base table.

 i'll be displaying only 13 columns in the screen and updating only one column
out of 13 columns some are not null columns and some accept null values alos
I have written two table handlers on the block, on-update and on-lock

my question is how do i need to frame the on-lock procedure logic....
do i need to include all the 70 columns in the lock-row logic
or do i need to check for the 13 columns which are displayed on the screen
or is it enough if i check for the non-null colums in the lock-row procedure..

FYI : i'm following the same steps as mentioned in the oracle applications developer guides ..
topic : Example Client–Side Table Handler  page 4-21
hiswapnaAsked:
Who is Participating?
 
andrewstCommented:
Interesting question.  My initial thought is that you only need to check the 13 columns, because the user is unconcerned with the other 57.  Here's my reasoning:

Suppose you check them all, and find that someone else has changed col66, which your form doesn't use.  The error is raised telling the user the he/she needs to requery the record as it has been changed.  The user requeries the record, which comes back looking exactly the same as before, and then successfully locks it.  So nothing has been gained by the initial lock failure.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.