Error ORA-20512: Invalid action CREATE on this object. (UD)???

Question

Actually, I have two questions:
1.
I can't figure out why I have this error. I have a simple interactive report with form. On this form are 3 fields (a hidden ID field, a message_code field and a message_text field). I have a custom stored procedure to insert a message in the message table. I made a PL/SQL block for this in the page processes and made it conditional when the create button is pressed (process is the first page process). I unchecked the "insert" from Allowed Options in the ARP(DML) process, since I like to use it for the update and delete actions. The stored procedure is actually called, because when I input invalid data (exisiting error code, for example) the custom raise_application_error from the stored procedure is shown in Apex, as it should be.
What could be the problem here?
2.
Actually, what is the function of the "Allowed Operations" option in a DML process? What actually changes when checking or unchecking operations there? If I uncheck the "delete option", I would expect the delete button to dissapear, or at least the delete option would not work anymore, but this is not the case. Even when I uncheck "delete", I can still us the delete button and it still deletes the record. What use is this option then?

Answer 1

Those checkboxes tell you what the permitted operation are for the Data Manipulation Process against that table.
When you create a dml process using the wizard, if by default created the buttons for you. After it has been created, if you remove them, the button will not dissappear. As do they not appear if you didnt select a permitted operation in the wizard and later want to add the operation, so you will have to delete the buttons yourself (or create).
If you for example uncheck 'Delete' as a valid operation, despite the buttons remaining on the page, clicking on the button will not do anything, because you have not permitted that operation.
If you look in the the DML process, you will see:
Valid Update Request Values:     SAVE, APPLY CHANGES, UPDATE, UPDATE ROW, CHANGE, APPLY, APPLY%CHANGES%, GET_NEXT%, GET_PREV%
Valid Insert Request Values:     INSERT, CREATE, CREATE_AGAIN, CREATEAGAIN
Valid Delete Request Values:     DELETE, REMOVE, DELETE ROW, DROPSo, if you didn't un-check 'Delete' from permitted operation, but did delete the page button, I could just go into the address bar and type and of the follwing: javascript:apex.submit('DELETE'); javascript:apex.submit('REMOVE'); javascript:apex.submit('DELETE ROW'); javascript:apex.submit('DROP'); and that current row that I am looking at would be deleted. So it is important, if you don't want users to be able to remove rows, that uncheck that permitted operation as someone with a clue could just do what I have said.
Of course, you could also add conditions to the process that request is contained in: SAVE,CREATE ; and it wouldnt matter if I did do what I suggested above, the condition of the process would not be met, so it would run the delete operation anyway.
Ta,
Trent
Edited by: trent on Dec 10, 2010 4:31 PM