Oracle clearly mandates primary keys for all the tables that are to be used with APEX and they are absolutely right to demand it, to meet the simplicity of the APEX low code application development. Primary keys, constraints, table triggers and all such could make the front end development easier as the database will do the validations and checksums against the data.

Today we will see how to create a Master Details APEX form using the master table that has a primary key column and the details table having only a foreign key reference to the master table. If you refer the Oracle Whitepaper for APEX integration with R12 12.2.x, you will get an idea to circumvent the primary key issues to a certain extend, which is not the topic that I am discussing today.

For this demonstration purpose, I will be using 2 tables that I copied from Northwind Microsoft SQL database which was migrated to Oracle. I dropped all the constraints from these tables and created primary key constraint for the Master table and foreign key for the details table.

I thought of making a video this time as explaining it here looked too hectic.

If you would like to see a text version of the same, do let me know through comments and I will try to update this thread.