Problem in Many-to-Many Associations (JBO-27014 error)

Question

I am facing a problem during insertion in an Intersection table.
I have 3 tables Customer, Accounts and Customer_Account. In order to implement the Many to Many relationship between Customer and Accounts, I created an intersection table Customer_Account.
Table Structure
CUSTOMER
Cust_id NUMBER NOT NULL PK
Name VARCHAR2(50) NOT NULL
ACCOUNT
Account_Id NUMBER NOT NULL PK,
Account_number NOT NULL,
Sort_Code NUMBER NOT NULL,
Account_Type VARCHAR2(10) NOT NULL
CUSTOMER_ACCOUNT
Cust_Id NUMBER NOT NULL,
Account_Id NUMBER NOT NULL
I created an Association CustAcctAsso between Customer and Account with Customer_Account as intersection entity. Then created a viewlink CustAcctViewLink with CustomerView as Source entity, AccountView as Destination entity and selected the CustAcctAsso as association.
I included this in the application module using the following steps
Selected AccountView via CustAcctViewLink in the Available view pane and selected CustomerView in Data model pane. Clicked > to add AccountView via CustAcctViewLink as a restricted view.
Also added CustomerView via CustAcctViewLink as a restricted view.
When I tried to insert data through the second restricted view I am getting an JBO 27014 Attribute Sort Code in Account is required.
It would be very helpful if someone gives me a solution quickly.
Thanks
Renuka

Answer 1

Thanks, now I am able to insert data into CUSTOMER and ACCOUNT table, but not in the intersection table.
It seems that we cannot do any insertion into the intersection table. Please advice me, this is urgent.OK here's what you need to do to insert a new row in both ACCOUNT and INTERSECTION tables.
1. Create a new viewobject with a join of INTERSECTION and ACCOUNT tables such that both are updateable but ACCOUNT is reference entity.
-- This is assuming you want to insert a new account when you insert a new account id in the intersection table otherwise, you can make ACCOUNT entity readonly as well.
2. Create a viewlink between Customer viewobject and this NewViewObject (1-* ViewLink).
3. If the assumption in step 1 is NOT to update/insert new Accounts form this VO, then you're done. Add the new viewobject usage in your application module and you should be able to use it to edit/insert intersection details.
Otherwise -
Set the Updateable flag on AccountID (from the Account entity usage in the NewViewObject) to "never" udpateable.
Set the Updateable flag on Other attributes from the Account entity usage in the NewViewObject to udpateable-while-new or always as desired.
4. Select to generate EntityDefImpl subclass for Account table and override the protected method createInstance as below:
  protected EntityImpl createInstance(DBTransaction txn, AttributeList al)
    // TODO:  Override this oracle.jbo.server.EntityDefImpl method
    return super.createInstance(txn, al);
  }5. Select to generate a ViewRowImpl subclass with accessors for this NewViewObject
6. Add the following logic in setAccountID() method (assuming AccountId attribute is editable and from Intersection entity)
(Note you'll also have anothe attribute AccountId1 from Account entity which should be readonly as marked in step 3.)
//get the current intersection entity.
IntersectionImpl intersection = (IntersectionImpl)getEntity(1);
setAttributeInternal(ACCOUNTID1, value);
//if it is same as I added and is not the same as new one
//framework may assign a new intersection entity based on FK.
IntersectionImpl newIntersection = (IntersectionImpl)getEntity(1);
IntersectionDefImpl intersectiondef = (IntersectionDefImpl)IntersectionImpl.getDefinitionObject();
IntersectionEnrollmentImpl myVO = ((IntersectionEnrollmentImpl)getViewObject());
DBTransaction dbtxn = myVO.getDBTransaction();
//see if a intersection exists with this FK
intersection = (IntersectionImpl)intersectiondef.findByPrimaryKey(dbtxn, IntersectionImpl.createPrimaryKey(value));
//if this viewrow created a new intersection earlier which is different from
//the current intersection entity, remove the old one as I created it.
if ((intersectionAdded != null) && (intersection != intersectionAdded || newIntersection != intersectionAdded))
  if (intersection == null)
    //if I added this intersection as new, reuse-it.
    intersection = intersectionAdded;
    intersection.setIntersectionid(value);
  else
    //if I added this intersection as new, remove it.
    System.out.println(">>>>removing :"+intersectionAdded.getAttribute(0));
    intersectionAdded.remove();
    intersectionAdded = null;
if (intersection == null)
  //if new intersection is null = no intersection exists with this key, then create a new one.
  intersection = (IntersectionImpl)intersectiondef.createInstance(dbtxn, new AttributeListImpl());
  intersection.setIntersectionid(value);
  intersectionAdded = intersection;
  setEntity(1, intersection);
  myVO.notifyRowUpdated(findRowSetForRow(this), new ViewRowImpl[]{this}, new int[]{2,3});
else if (intersection != newIntersection)
  //otherwise, create a set the new intersection entity as my intersection entity reference
  setEntity(1, intersection);
  myVO.notifyRowUpdated(findRowSetForRow(this), new ViewRowImpl[]{this}, new int[]{2,3});
}Now when you insert a new row in this NewViewObject, you can either enter a new Account or refer to an existing Account.
The setAccountId() method will automatically bring the Account details for existing accounts or create a new Account entity as in the above logic.