Some client operations, like pegging Purchase Order lines from Available Source Lines on the Incoming Dispatch Advice screen, need parameter values (like a message ID and delivery note number) that aren't actually present in the underlying view your custom logic is built against. The Debug Console shows these values are read directly from client-side form controls instead. Can values fetched this way from client controls be used inside custom PL/SQL, even when they aren't part of any database view?

Question

Accepted Answer

Yes — use the Debug Console to identify exactly which client-side field/control values a given operation actually reads from at runtime, shown as fully-qualified paths like i_hWndParent.frmSomeForm.dfnSomeField. Since these client-side references are fetched directly from the client and aren't bound to any particular database view, they can be referenced directly inside a custom PL/SQL block using bind-variable syntax, for example p0_ := :i_hWndParent.frmSomeForm.dfnSomeField;, pulling the live on-screen value straight into a PL/SQL variable, even when that value isn't present as a column in whatever view your custom logic is otherwise built against.

Answer