BMXAA4107E -- Because of an implementation or customization problem, the system cannot determine how the attributes of object {2} correspond to the attributes {3} of object {0}. You might need to populate the MAXLOOKUPMAP table and restart the server.

The specified attributes must have an entry in the MAXLOOKUPMAP table or be mapped in the field validation class of {2}.{1}.
In order to add MAXLOOKUPMAP there are two ways 
Through DB 
insert into maxlookupmap (target,lookupattr,targetattr,sourcekey,seqnum,allownull,source,maxlookupmapid)
values ('target','lookupattr','targetattr','sourcekey',1,0,'source',maxlookupmapseq.nextval); 
commit; 

(for db2) 
insert into maxlookupmap
(target,lookupattr,targetattr,sourcekey,seqnum,allownull,source,maxlookupmapid)
values
('target','lookupattr','targetattr','sourcekey',1,0,'source',nextval for maxlookupmapseq ) ;

Through the front End 
Identify the attribute on which maxlookupmap need to insert 
Click on maxlookupmap icon as shown 
 

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgX7dJyNwgEDmjDJA1YkPz3rBDvc4myYy46porQ0xAL3W2pK8PR7NG2h0m0wQMQeF03v2IKKHTuPgN1_2DrMx3tWOMdFc0kQpNNaqvHEuREESDq04RTOj5tHfP7WR7BXvnAsSfdL4FlMH0/s320/fgh.jpg

Enter the required details such as target and source and etc. as shown. For example refer CONTRACTREFNUM attribute of PO object 

Restart the application server to reflect the changes
The above Error occurs only when the JVM heap size greater than the memory resources available.

 

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.