your PERSON_STATE table doesn't show any foreign key to the Person table. So this needs to be provided. You then create a view link based on this reference. Alternatively you can create a ViewObject based on the two entities (Person and Person_State) to show both information in the same table. For both implementations you need to have a primary key in the PERSON table and a foreign key attribute in the PERSON_STATE table
Thanks for your reply.
The second alternative works, but I would be interested in the first one (using a view link).
The foreign key is defined properly:
PERSON.PERSON_CODE is a primary key.
PERSON.PERSON_COD_STATE is a foreign key.
PERSON_STATE.PERSON_COD_STATE is a primary key.
I have created a view link based on that foreign key.
When usign af:table to show the records of PERSON table, all the data of PersonView is properly shown. But the STATE of the person is not ok. It seems as the view link is not working.
Your scenario should be dealt with with a join sql (VO on two EOs) not with a master-detail relationship. The table won't be able to iterate through the details for each master record at stamping time.
Thanks for your answer. I was starting to think what you have told me: "table won't be able to iterate through the details for each master record at stamping time"