Could you demonstrate on apex.oracle.com with providing the workspace name and a developer account
Code Review Notes
I can't really do a Code Review because you haven't posted any. But, here are some design issues I've noticed.
Primary Key should only be assigned at time of INSERT. This value should NEVER come from the end-user. (those values are easily hacked)
Also, you should consider moving all of your custom DML code into a Package. Whether you call that Package a Table API (TAPI) or a Transactional API (XAPI) is up to you.
PS - we can't debug we can't see. Please follow Mahmoud's advise. Thanks.
Thank you for your reply on this.
But it actually worked now and I am able to insert and update the data on Page 2 with all the details from Page 1 and Page 2
I actually did not insert the Primary key in the insert statement as it was a sequence generated with a trigger on insert.
About the package, I will make sure of it going forward as its easy to track it.