Form not committing the data

Question

I'm a newbie in Apex development.
We are working in Apex 4.0.
I have created a form on a table with report.
Form updates work fine with automated row processing(DML) but when I replace
this process with a PL/SQL process (calling our internal procedures to handle the
journalling, replication etc.) then form does not commit the new field values.
My Pl/SQL block is something like this
DECLARE
v_rec_sid NUMBER := 0;
v_sqlcode NUMBER := 0;
v_sqlerrm VARCHAR2(132) := NULL;
BEGIN
v_rec_sid := :P11_REC_SID;
P_TABLE
, IO_REC_SID => v_rec_sid
, O_SQLCODE => v_sqlcode
, O_SQLERRM => v_sqlerrm
, I_FORENAME => :P11_FORENAME
, I_LOGIN_ID => :P11_LOGIN_ID
, I_MIDDLE_NAMES => :P11_MIDDLE_NAMES
, I_SURNAME => :P11_SURNAME
, I_TITLE => :P11_TITLE
-- Report any problem
IF v_sqlcode <> 0 THEN
htp.p('PV - ' || to_char(v_sqlcode)||': '||substr(v_sqlerrm,1,80));
END IF;
:P11_REC_SID := v_rec_sid;
EXCEPTION
WHEN OTHERS THEN
htp.p('Error - ' || TO_CHAR(SQLCODE)||': '||substr(SQLERRM,1,80));
htp.nl;
END;
This process is 'On Submit-After Computations and Validations' and while running the form
it shows the Process Success Message but when it goes back to report page it shows that it
has not updated the data.
When I compared the session state between automated row processing and my process the difference
is that the status of all page parameters (except the primary key which shows the actual value)
is 'blank' for automated row processing and 'Reset to Null' for my process.
When I print the page parameters value (after header section) it shows the value in all parameters.
I have tried using the COMMIT inside my pl/sql block but it does not make any difference.
What am I missing.
Thanks
Dino

Answer 1

910226 wrote:
I'm a newbie in Apex development.Welcome to the forum: please read the FAQ and forum sticky threads (if you haven't done so already), and ensure you've updated your profile with a real handle instead of "910226".
We are working in Apex 4.0.You'll get a faster, more effective response to your questions by including as much relevant information as possible upfront. This should include:
<li>Full APEX version
<li>Full DB/version/edition/host OS
<li>Web server architecture (EPG, OHS or APEX listener/host OS)
<li>Browser(s) and version(s) used
<li>Theme
<li>Template(s)
<li>Region/item type(s)
With APEX we're fortunate to have a great resource in apex.oracle.com where we can reproduce and share problems. Reproducing things there is the best way to troubleshoot most issues, especially those relating to layout and visual formatting. If you expect a detailed answer then it's appropriate for you to take on a significant part of the effort by getting as far as possible with an example of the problem on apex.oracle.com before asking for assistance with specific issues, which we can then see at first hand.
My Pl/SQL block is something like thisAlways post code wrapped in tags<tt>\...\</tt> tags to preserve formatting and special characters.
DECLARE
  v_rec_sid     NUMBER        := 0;
  v_sqlcode     NUMBER        := 0;
  v_sqlerrm     VARCHAR2(132) := NULL;
BEGIN
    v_rec_sid := :P11_REC_SID;
P_TABLE
, IO_REC_SID            =&gt;  v_rec_sid
, O_SQLCODE             =&gt;  v_sqlcode
, O_SQLERRM             =&gt;  v_sqlerrm
, I_FORENAME                =&gt;  :P11_FORENAME
, I_LOGIN_ID                =&gt;  :P11_LOGIN_ID
, I_MIDDLE_NAMES            =&gt;  :P11_MIDDLE_NAMES
, I_SURNAME                 =&gt;  :P11_SURNAME
, I_TITLE                   =&gt;  :P11_TITLE
:P11_REC_SID := v_rec_sid;To find out what's going on, get rid of this</a>:
  --  Report any problem
  IF v_sqlcode &lt;&gt; 0 THEN
      htp.p('PV  - ' || to_char(v_sqlcode)||': '||substr(v_sqlerrm,1,80));
  END IF;
EXCEPTION
  WHEN OTHERS THEN
      htp.p('Error - ' || TO_CHAR(SQLCODE)||': '||substr(SQLERRM,1,80));
      htp.nl;http://tkyte.blogspot.com/2008/01/why-do-people-do-this.html
END;