OPA 10.4 "Inferred Entity Instances", possible to integrate with Siebel?

Hi,
In OPA 10.4, I found a new feature "Inferred Entity Instances" using which we can create benefit plans, Opportunities, Service Request,Order lines using only rules.
Does it mean we can create an Opportunity/Service Request/Order line by writing the information only in the rule when OPA 10.4 is integrated with Siebel?
Thanks,
Subhradeep

The current Siebel Connector only supports OPA 10.3, which does not have inferred entity instances.
The upcoming release of the Siebel Connector will support new 10.4 OPA features including inferred entities.
Cheers
Frank

Similar Messages

  • Clarify a Limitation for Inferred Entity Instances

    Hi,
    Under the section "Write rules that infer relationships and entities" in the User Guide there is the
    Notes /Limitations
    1) Combining manually created instances with inferred instances is not allowed.
    2) Combining inferred entity instances with temporal values is not supported.
    3) Only a single attribute of the entity instance can be inferred as a part of the entity rule. For example, the type of benefit ("unemployment benefit") can be set but the amount of the benefit would have to be set via a separate rule.
    4) Inferred entity instances may not contain base level attributes.
    5) A relationship that participates in an inferred entity instance rule is considered to be an inferred relationship. This means that an inferred relationship rule cannot be used to prove the same relationship used in an inferred entity instance rule.
    Can number 4 be explained in a little more detail?
    Thanks

    I'm not sure I understand the question so I'm going to guess what you're asking by suggesting a business scenario and talk about how that would work. It is always much easier to talk about a specific business requirement you have rather than product features in general - so if you have a specific requirement I strongly recommend sharing it as you'll get better quality help.
    Anyway, if we keep our existing example of an inferred entity "the product" (has attributes: the name of the product, the price of the product). Say we want to know want the price of the most expensive product you have selected (a concept which would be represented by an attribute at the global level).
    You can do that. The rules to do that are just the same as the rules you'd use if instead of inferring the products and prices you instead asked the user to provide them (ie instancemaximum across a relationship). I'd send an example showing these rules - but it's not possible to attach files to this forum. You use inferred entities in the rest of your rules as if they had been input by a user - there's no difference. The key difference between an inferred entity and a non-inferred entity is that you can't collect more information about it (ie it can't have any base level attributes).
    You can use any attribute in a rule so long as the usage of the attribute matches the entity level of the conclusion. ie You couldn't use "the price of the product" directly in a rule with a conclusion at the global level - because you revert to the problem of "the price of which product?".
    On the off chance that this is somehow a "programmer" question (ie you're trying to understand how OPA works by treating it the same as another method for creating programs, for example a programming language like Java) - attributes in OPA don't have a concept of "private" and "public". If I tried to put OPA In those terms (and it's a stretch because OPA is not Java) - in OPA: everything is public (declare once use everywhere). An entity model in OPA is different thing to a class hierarchy.

  • Creating infered entity instances

    How can I create infered entity instances..in opa 10.4.
    When I am trying to write rule using the "exists" keyword.. its not compiling as "Infered
    Instance" but it compiles as normal conclusion.
    and how can I create inferred instances conditionally..

    Sorry for the long delay in replying Rajan, I missed your request to elaborate.
    To be specific:
    When an entity instance is inferred that means that every attribute in it must also be inferred. The rule engine cannot cope with logic like: "this entity might or might not exist, but if it does, we need to ask for more information about it"
    There are a few ways to deal with setting information in an inferred entity:
    - most obviously infer any values from other entiy attributes in the session.
    - set attribute values on related, non-inferred entities and then use rules infer those attributes on the inferred entity.
    Its worth having a think about what the inferred entity instances means. If you want to use the rules as a convenient way to create an entity instance and you still need to set non-inferred attributes, then you are better off using an inferencing listener to create the instances.
    If the instances are truly derivable from rules, then any attribute values of those instances are probably also derivable.
    Cheers
    Frank

  • Return value of inferred entity instance from relationship in SOAP Determinations

    Hey,
    I had an original thread open which indicates the problem I was trying to solve (Multiple Conclusion based on input values ). My rule base now behaves as expected and I can test it in the debugger as expected, only now I can't get the actual identifying values back I want using the determinations web service.
    I get a whole bunch of inferred entity instances back from an inferred relationship the same as the situation/screen shot at the bottom of the "Investigate an inferred relationship" page on the Oracle Policy Automation Cloud Service User Guide, but in my SOAP response I only get the instances with hashed IDs. I want the actual identifying value of the entity.
    e.g. Currently get this:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:i18n="http://www.w3.org/2005/09/ws-i18n" xmlns:typ="http://oracle.com/determinations/server/11.0/rulebase/assess/types">
       <SOAP-ENV:Header>
          <i18n:international>
             <i18n:locale>en_GB</i18n:locale>
             <i18n:tz>GMT-0500</i18n:tz>
          </i18n:international>
       </SOAP-ENV:Header>
       <SOAP-ENV:Body>
          <typ:assess-response>
             <typ:global-instance>
                <typ:attribute id="course_code" type="text">
                   <typ:text-val>AHPY</typ:text-val>
                </typ:attribute>
                <typ:entity id="the_supplementary_documents" inferred="true">
                   <typ:instance id="0x608c2dc220e15d8c"></typ:instance>
                   <typ:instance id="0x5b7e2d02e8780325"></typ:instance>
                </typ:entity>
                <typ:entity id="the_informational_documents" inferred="true">
                   <typ:instance id="0x19387621439a43c7"></typ:instance>
                </typ:entity>
             </typ:global-instance>
          </typ:assess-response>
       </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    But I want something like below and I'm having a lot of trouble figuring out how to actually do this. Also is there anywhere that defines the meaning of errors you get from OPA? I have tried to modify my rulebase and I got a few OPA-EXXXXX errors but apart from the description you get in OPM, I can't find anywhere that gives more detail on these and explains what they mean/how to fix it.
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:i18n="http://www.w3.org/2005/09/ws-i18n" xmlns:typ="http://oracle.com/determinations/server/11.0/rulebase/assess/types">
       <SOAP-ENV:Header>
          <i18n:international>
             <i18n:locale>en_GB</i18n:locale>
             <i18n:tz>GMT-0500</i18n:tz>
          </i18n:international>
       </SOAP-ENV:Header>
       <SOAP-ENV:Body>
          <typ:assess-response>
             <typ:global-instance>
                <typ:attribute id="course_code" type="text">
                   <typ:text-val>AHPY</typ:text-val>
                </typ:attribute>
                <typ:entity id="the_supplementary_documents" inferred="true">
                   <typ:instance id="http://mydomain.com/mydocument.pdf">
                   </typ:instance>
                   <typ:instance id="http://mydomain.com/mydocument.pdf"></typ:instance>
                </typ:entity>
                <typ:entity id="the_informational_documents" inferred="true">
                   <typ:instance id="http://mydomain.com/mydocument.pdf"></typ:instance>
                </typ:entity>
             </typ:global-instance>
          </typ:assess-response>
       </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

    I managed to get this working by referring to this thread: Inferred Entity Instances IDs in output response
    I had tried something similar but not quite the same. In the end my request looked something like this:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://oracle.com/determinations/server/11.0/rulebase/assess/types">
       <soapenv:Header/>
       <soapenv:Body>
          <typ:assess-request>
             <typ:config>
               <typ:outcome>
              <typ:entity id="the_supplementary_documents">
                <typ:attribute-outcome id="supplementary_documents" outcome-style="value-only"/>
              </typ:entity>
              <typ:entity id="the_informational_documents">
                <typ:attribute-outcome id="informational_documents" outcome-style="value-only"/>
              </typ:entity>
           </typ:outcome>
             </typ:config>
             <typ:global-instance>
                <typ:attribute id="course_code">
                <typ:text-val>AHPY</typ:text-val>
       </typ:attribute>
              </typ:global-instance>
          </typ:assess-request>
       </soapenv:Body>
    </soapenv:Envelope>

  • Batch Processor, WIA and Inferred entity instances

    Hi All,
    I'm playing around with the new OPA 10.4. I bumped into an error in What-If-Analysis document when I tried to add a new worksheet for an inferred entity. Is this not possible in WIA? Does it mean it will not work as well with Batch Processor.
    Here's my data model:
    global
    --- the applicant
    --- --- the qualification
    --- --- --- the exempted course (inferred instances from 'the qualification' attributes)
    Thank you in advance!
    Regards,
    Jerome

    Brad Tuckett wrote:
    Jerome wrote:
    Is there a possible workaround right now in 10.4 to persist inferred instances in Batch Processor?The Batch Processor will not output any inferred instances in 10.4
    One more thing, I'm also using 10.2 and have implemented InferencingListener to create instances, would you happen to know if I will bump on the same issue with DSC?
    There probably isn't a way of having any entity instances created by an event listener appear in the Batch Processor output for database or CSV.
    However, you may be able to set the output to saved sessions. Although this isn't explicitly supported, I would expected that any instances you have created would show up in the exported sessions, which will be xml files in the xds format. This will create one session file for each case.
    You can set the output to be exported sessions by using "--export <dir>" in the command line or use the xml configuration for the Batch Processor.
    When 10.4.1 is released you should be able to switch to using inferred entities which will be compatible with the Batch Processor.

  • Creating New Entity Instances within OPA

    This is another one that I think I know the answer to, but I think it is best to confirm.
    In prior versions, it was not possible to create entity instances within RuleBurst/Haley Office Rules. Is that still the case in OPA?
    For example, my rules are determining the status of a case and the reason(s) why that status was determined. The case status may be Denied and the reasons may be "invalid customer Id", "expenses to income ratio too high", "primary customer not employed long enough", etc. I want to return all the reasons for the status. While the list of reasons is pre-determined, the ones that apply to a particular case are dynamic, as any, but not all can apply.
    Given this situation using a database, I would create an instance of reason for each applicable one and link it to the case. In the past, with OPA's predecessor(s), it was not possible to create new instances from within. They either had to all be passed into the rulebase or a list of all allowable reasons attributes had to be created and then set to true for the ones that applied.
    My preference is to create the instances inside OPA. Is that functionality provided in the current version?
    Thanks,
    Terry

    Hi Terry,
    Michael is correct that you can't write rules at design time which will dynamically create new entity instances at runtime. However, perhaps the new inferred relationships functionality in v10 could address what you're trying to do.
    You can write rules which conclude membership of an inferred relationship. So you might always have, say, 10 instances of 'the reason' in every case, but as for which of those instances apply in any particular case, it depends on the details of the case. You could use an inferred relationship to collect up the entity instances which apply in the case.
    First you'd need to set up a regular one-to-many relationship to instantiate the 10 instances at runtime - this would be done in the usual way. Then you'd also need to set up an inferred relationship and write rules to conclude the members of the inferred relationship. The instances which are members of the inferred relationship are then effectively the list of entity instances you wanted to create in your example above.
    Have a look at this OPM Help article: http://www.oracle.com/technology/products/applications/policy-automation/help/opm10_1/Content/Rules%20using%20entity%20instances/Reason_about_relship_between_2_entities.htm
    Cheers,
    Jasmine

  • OPA Siebel Error - Entity instance does not exist

    Hi
    We have installed Siebel OPA connector in our environment and want to have a rule base based on below entities
    Opportunity(S_OPTY) and Opportunity Product(S_REVN)
    Created new Entities : dealProduct (1 to M) to Global
    Added attributes in dealProduct entity as below
    ao_fast_track – Text
    customizable – text
    fast_track _ Text
    Product_id - Identifying attribute
    Logic: Based on few field values in Opportunity Product we want to pass a value to Opportunity entity to display a message in UI.
    Created the rule and run in debug mode all works fine (created instances manually) but when we invoke the same rule base getting below error message
    [1]Error invoking service 'Policy Automation Determination Server', method 'Assess' at step 'Call Determination Server'.
    (SBL-BPR-00162)[2]Operation 'Assess' of Web Service 'http://oracle.com/determinations/server/10.0/server/types.DeterminationServer' at port
    'NonFastTRackDeal' failed with the following explanation: "Entity instance 'dealproduct[deal Product-1-7IGVAU]' does not exist.".(SBL-EAI-04308)
    I have checked the record with Id'1-7IGVAU' is available in the database , Please let me know if I am missing any thing here.
    Please find the details of the changes in siebel.
    1. Add a button to existing applet and added the relevant code to invoke the rule base web service.
    2. Create New Mapping as below
    Mapping Name:NonFastTRackDeal
    Business Object:Opportunity
    Default Value:UnKnown
    Outbound Poart:NonFastTRackDeal
    Created below 2 Entity Attributes:
    deal Product BC Opportunity Product
    global BC Opportunity
    Relation Ships
    Name: dealproduct(same as public name of Forward relationship)
    Source:global
    Target:deal Product
    Outcomes for global entity: deal_type
    Attributes for deal Product
    Prod_id(identify Attribute): Row Id(Opportunity Product Row Id)
    mapped to corresponding fields for below attributes
    ao_fast_track:
    customizable
    fast_track
    Please let me know if I am missing any thing here.
    Regards
    CRT

    Kristy,
    First thank you for the assisance. The Instances are create when the screen is submitted to the session. We save the session to XDS and reconstitue the session before the next screen for the first instance is submitted (instance#1 of employer type), so i would think it would not be treated as inferred ?
    Return (screen.GetInteractiveSession().Submit(screen))"entity instance whose values can be modified via the interview, you must use the facilities provided by the Interview API."
    Is there a C# example of using the Interview API with multiple instances?
    Thanks
    Alex

  • Validation in entity instance collection page

    I have a requirement where I have a page on our OPA interview page which collects entity instance.In this page there are two fields person contacted and contact date.I have to validate that the contact date is one per week.Please advice how can I achieve this requirement.

    There is no standard definition, nor function for "the same week" - e.g. does that mean a week starts on a Sunday or Monday, or within 1 week in either direction?. In other words, you will need to express the specific logic you desire for "during the same week" in terms of the available functions such as those that can determine the day of the week and/or those that return the date plus/minus a number of days and/or the difference in days between two dates. Some suggestions on simplifying the logic ... two dates that are more than 7 days apart can't occur during the same week so only worry about <= 7 days apart, two dates which are the same day of the week and different dates can't be within the same week, so your logic should only need to deal two dates are different days of the week and are less than 7 days apart. In that case, you will need to express exactly what you mean by during the same week. (e.g. is a Sun and Sat that are 1 day apart within the same week or not?) Your logic should reduce to a rule table dealing with each day of the week and a range of days before/after that define "within the same week".

  • Explaining a WD Error: "Entity Instance Does Not Match Expected Entity"

    Hello,
    I'm wondering if someone can help me understand what is causing a persistent web server error that seems to be related to entities and/or instance creation. Lately, after building with screens and clicking on the top-level goal, I'll get this generic error:
    An error occurred trying to process your request.
    This error has been logged and is available in the application logs.
    For support and assistance please contact [email protected].
    I then check the Embedded Web Server Output, and see the text pasted at the bottom of this post - the key error seeming to be "java.lang.IllegalArgumentException: Entity instance does not match expected entity".
    Observations:
    - It seems to occur after I've made some significant changes to my data model: merging two entities, or switching relationships to being inferred.
    - There are no errors or warnings in the "Error List" and all documents are compiling successfully.
    - It only happens when I build with screens. I can 'build', or 'build and debug' without screens successfully.
    - The most recent occurrence was after I had converted a few relationships to "Inferred" and resolved all compiling errors.
    - It only occurs after clicking on the top-level goal, and sometimes a few screens afterwards. By switching most of my relationships back to non-inferred (except for one), I've been able to get some of the screens working - up until I arrive at the screen that involves creating instances for the second entity involved in the remaining inferred relationship.
    - The remaining inferred relationship that I was suspecting as a cause seems to be working correctly (i.e. I can see that the instances were connected in the Data tab, even after the error has appeared in the web output).
    I would be very grateful for any assistance with this error, as it's become somewhat of a time sink and I've already tried a few angles for troubleshooting it.
    Thanks!
    - Patrick
    Embedded Web Server Output:
    Deploying application
    Jul 18, 2011 2:35:18 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
    INFO: validateJarFile(C:\projects\[project name]\Release\web-determinations\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
    Server startup complete!
    OK - Tomcat server started
    4 [http-127.0.0.1-9000-Processor4] ERROR com.oracle.determinations.web.platform.servlet.WebDeterminationsServletUtility - java.lang.IllegalArgumentException: Entity instance does not match expected entity
    java.lang.IllegalArgumentException: Entity instance does not match expected entity
         at com.oracle.determinations.engine.local.RelationshipRule.backwardChainInternalItem(RelationshipRule.java:209)
         at com.oracle.determinations.engine.local.RelationshipRule.backwardChainRelationshipItem(RelationshipRule.java:132)
         at com.oracle.determinations.engine.local.eval.RelationshipExpression.backwardChain(RelationshipExpression.java:216)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleTableValue.backwardChain(RuleTableValue.java:264)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleTableValue.backwardChain(RuleTableValue.java:264)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleTableValue.backwardChain(RuleTableValue.java:264)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleSimpleValue.backwardChain(RuleSimpleValue.java:212)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.RelationshipExpression.backwardChain(RelationshipExpression.java:223)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleSimpleValue.backwardChain(RuleSimpleValue.java:211)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.ExpressionScopeSelect.backwardChain(ExpressionScopeSelect.java:40)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleTableValue.backwardChain(RuleTableValue.java:264)
         at com.oracle.determinations.engine.local.eval.ExpressionAttributeRef.backwardChain(ExpressionAttributeRef.java:122)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.RelationshipExpression.backwardChain(RelationshipExpression.java:223)
         at com.oracle.determinations.engine.local.eval.SimpleExpression.backwardChain(SimpleExpression.java:101)
         at com.oracle.determinations.engine.local.eval.ExpressionEvaluation.backwardChain(ExpressionEvaluation.java:102)
         at com.oracle.determinations.engine.local.RuleSimpleValue.backwardChain(RuleSimpleValue.java:211)
         at com.oracle.determinations.engine.local.LocalAttribute.backwardChain(LocalAttribute.java:562)
         at com.oracle.determinations.engine.local.LocalAttribute.getRelevanceReport(LocalAttribute.java:515)
         at com.oracle.determinations.interview.engine.local.AttributeGoal.getNextScreen(AttributeGoal.java:113)
         at com.oracle.determinations.interview.engine.local.LocalInterviewSession.getNextScreen(LocalInterviewSession.java:213)
         at com.oracle.determinations.web.platform.controller.actions.InvestigateAction.submit(InvestigateAction.java:99)
         at com.oracle.determinations.web.platform.servlet.WebDeterminationsServlet.doPost(WebDeterminationsServlet.java:102)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
         at com.oracle.determinations.web.platform.util.CharsetFilter.doFilter(CharsetFilter.java:46)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)
         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
         at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
         at java.lang.Thread.run(Unknown Source)
    Edited by: Patrick Devine on Jul 18, 2011 3:23 PM

    Hi Patrick,
    The bad news is that your issue is due to a bug in the Determinations Engine. The good news is that there is a workaround. Basically there’s an implied directionality for all relationships which, for inferred relationships is defined by the direction in which you declared the relationship in the properties file. The problem only happens if you write your membership rule in the reverse direction to the one in which it was originally declared. In your case because your membership rule concludes the relationship ‘the benefits of the benefit plan’ you need to make sure that your relationship was declared in that direction as well. To do that, you’ll need to delete your existing relationship in the properties file and then create it as follows:
    Source: the benefit plan
    Target: the benefit
    Relationship Type: Inferred (Many to Many)
    Text: the benefits of the benefit plan
    Reverse Text: the benefit plan of the benefit
    We will fix the issue in the next release.
    Thanks,
    Kristy

  • Entity Instances created from backend inaccessible during interview session

    Hi,
    Is it possible to access entity instances which are created from back end, during an interview session?
    I am creating the entity instances and setting some of its attributes from the back end. But when I try to access these instances on screen to set the rest of its attributes, I get the following error -
    com.oracle.determinations.interview.engine.exceptions.InterviewEngineException: Entity Instance does not exist in model

    Yes it is possible to access the entity instances held in the session. However, in an interview session you should never change the state of the session directly, but rather use the setData methods provided by the Interview API or write a data adaptor plugin. The error message you are receiving is cause by the reason it states, namely the entity instance you're asking for does not exist in the session. If you are adding entity instances by modifying the session directly rather than using the Interview API, it's likely that those entities their associated attributes are being lost and hence the error.
    If you can provide more details on what it is that you are trying to do I can help point you in the right direction.
    Thanks,
    Kristy

  • How to Compare entity instances's attribute and find the latest one.

    Hi,
    Below is my data model
    entities: the person, the job
    Relationships: the person-> the job (the person's job) 1 to M (reverse: the person's job's person)
    the person ->the job (the person's favorite job) M to M (inferred)
    Now, the job entity has below attributes: (only important ones are listed)
    1. the job's id
    2. the job's end date
    3 the job's person id
    the person entity has below attributes:(only important ones are listed)
    1. the person's id
    2. the person's most recent job id
    Using the "member of" operator I am assigning the entity instances to "the person's favourite job". Upto this things are working fine.
    Now the problem is I want to determine -"the person's most recent job id" by comparing the entity instance's attribute "the job's end date" and then getting the job Id of the same entity instance.
    Can someone help me in this..?
    thanks,

    Hi,
    Just be aware that if you had two jobs ending at the same time, then InstanceValueIf would return uncertain (perhaps they had two jobs at the same company...?) so just make sure you handle that.
    consider renaming the relationship to the plural... "the person's favourite jobs".
    I am assuming that your system only handles jobs that have ended, as things would be much more complicated if they could have multiple jobs (which could overlap) or jobs with start dates that haven't ended yet.
    Thanks,
    Ben

  • JBO-25017:Error occurred while creating a new entity instance (URGENT)

    Hello, can anybody help me?
    We have a project that uses BC4J business components and UIX-based web tier. The entity object that causes this problem is based on Oracle table with 'ID' key field, the value is generated by means of 'before_ins' trigger that inserts appropriate sequence's next value.
    In the java EntityImpl-based class we redefine protected 'create' method of the base class:
    protected void create(AttributeList attributeList)
    super.create(attributeList);
    SequenceImpl idSeq = new SequenceImpl("SEQ_CATPARAMETERS", getDBTransaction());
    setId( idSeq.getSequenceNumber() );
    The fault is in the third line - setId(...) causes the exception.
    The only description of JBO-25017 I found is
    http://www.ffpmp.ru/doc/rt/oracle/jbo/CSMessageBundle.html#EXC_ENTITY_ROW_CREATE, this one don't throw any light on the problem.
    Oracle server version - 9.2.0.1
    Oracle JDeveloper version - 9.0.3.10.35,
    BC4J version - 9.0.3.10.7
    Any ideas?

    Roman,
    It looks like you're trying to assign the Id in two places.
    EITHER:
    Override the create method to assign an Id when a new entity instance is created....
    OR:
    Define a database trigger to insert the Id (and set the "refresh after insert" attribute to true).
    [Maybe the error is thrown because you're attempting to set a field which is set to refresh?]
    Does that make any sense?
    Mike

  • ASE instance not available *** ERROR:ASE instance possibly left running when system went down(system crash?). Notify Database Administrator

    Hi Gurus,
    I made some changes in rz10 for client copy like:
    icm/host_name_full [email protected]
    login/accept_sso2_ticket 1
    login/create_sso2_ticket 2
    icm/server_port_1
    PROT=HTTPS,PORT=443$$,PROCTIMEOUT=600,TIMEOUT=600
    icm/server_port_0
    PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
    login/no_automatic_user_sapstar 0
    After to make changes effective, i stopsap & startsap.
    But unfortunately db is not coming up. I checked startdb.log it showing
    error as " ASE instance not available
    *** ERROR:ASE instance possibly left running when system
    went down(system crash?).
    Notify Database Administrator."
    Please help us to resolve this issue, i have also added startdb.log for
    your reference.
    Regards,
    Piyush

    Hi Piyush,
    Did you solved this issue.
    We are facing the same issue and only this thread is there in SCN for this issue.
    If you solved this issue,Kindly share the solution.
    Thanks and Regards,
    Mathan A

  • Is it possible to integrate multiple instances with single OAM (Oracle Acce

    Hi All,
    Please could anyone clarify,is it possible to integrate multiple instance with single OAM(Oracle Access Manager).
    We have two instance in development environment, Among them one is already integrated with OAM 11g,Now we want to integrate the second one with OAM 11g. For this already configured OAM is enough or we need to configure the another OAM separately.
    Application Version is 12.1.1
    Database Version : 11.1.0.7
    OS : RHEL 5.3 64 bit
    Thanks in advance.

    Hi Hussein ,
    I Ran below script,
    ant -f txkEBSAuth.xml \
    -Dwlshosturl=appora.corp.hexaware.com:7021 \
    -Dwlsuser=weblogic \
    -Dwlspwd=password1 \
    -DuseDefaults=true \
    -DforceDataSource=true \
    -DdataSourceName=DEV \
    -DdataSourceJNDIName=jndi/DEV \
    -DasadminUser=SSO11GLOGIN \
    -DasadminPassword=welcome1 \
    -DdbcFile=/u06/oamfmw/Middleware/appsutil/accessgate/DEV/DEV.dbc \
    -DserverName=AdminServer \
    -DdeploymentName=ebsauth_DEV \
    -DfndauthWarFile=/u06/oamfmw/Middleware/appsutil/accessgate/DEV/fndauth.war \
    -DplanPath=/u06/oamfmw/Middleware/appsutil/accessgate/DEV/plan/plan.xml \
    -DforceDeployment=true \
    -DSSOServerRelease=11 \
    -DSSOServerURL=http://appora.corp.hexaware.com:14100 \
    -DWebgateLogoutURL=http://appora.corp.hexaware.com:7780/public/oacleanup.html \
    -DlogConfigfile=/u06/oamfmw/Middleware/appsutil/accessgate/DEV/sample/logging.properties
    -bash: ant: command not found
    Thanks in advance

  • Dynamic creation of entity instances

    Hi,
    I create a custom function which dynamic create some entity instances and relationships.
    The base attributes of the entity intstances are filled with values. Running in debug mode
    with screens everything looks ok.
    Unfortunately the rules which operate on the entity instances are not triggered.
    Please help,
    Johan van der Graaf

    Hi Johan,
    as Davin mentioned it is really not advised to use custom functions to try to do this. What is the technical/business driver for doing this via a custom function rather than any of the other options that Davin suggests?
    The rules will be evaluated if there is enough information for it to be evaluated - the problem when you try to mess with the data set outside the inference cycle (which is what you're doing with a custom function to creeate entity instances) is that it doesn't know it knows the infromation - all it knows is the result returned from the custom function.
    At a high level: it's particularly awkward because you are asking it to set values behind the scenes - creating entity instances, properly setting up the relationships between those entity instances and then (I'd imagine) also populating the entity instances with their relevant values. You need to check that you are actually setting up all of those things properly.
    As I suggested before, you can see if it's a problem with the custom function not setting the values correctly or if it's a question of that need to make the engine know that you've added these values by going to the conclusion that you think should be evaulating in the debugger and specifically investigating it (right-click "Investigate") - you'll then be taken to the "decision" tab from where you can see what extra information the conclusion thinks it needs.
    If all of the data needed is actually already known then you'll get a result when you do this. If not then it will tell you what the extra information you need is and you can judge whether that's reasonable or because the custom function isn't actually setting up everything properly.
    If your custom function is setting everything outside the inference cycle then there are techniques you can use (basically relying on the result value for the custom function) to try to get the rule to evaluate, however these makes for some quite complex, non-intuitive rules which are awkard to maintain and the implementation of which often leads to people creating logical loops in their rules. It really would be best to look and see if there are other options availabel to achieve the same functional end.
    Have you investigated using the other options Davin has suggested? If so, we'd really appreciate knowing why you decided they weren't suitable as this will help us move the product forward in the future.
    Cheers,
    Sean.

Maybe you are looking for

  • Using bapi how to upload the data into sap database?

    hi dear all,               im facing problem with bapi ? let me edcuate on bapi .. i will be  waiting for reply. my e-id :[email protected] thanks&regards shiva.

  • How to show incoming mails in CRM Interaction Center?

    Experts, how can we show incomming ele. letter  for m.-direction of CRM USER in Interaction center. An example: I am interaction center agent. I am sending a correspondence to my client. In my user (SU01) i have saved my direction. The client receive

  • DNG CONVERTER:Which version of Camera Raw should I choose?

    What I need to uinderstand, is what are the real benefits of converting RAW files into DNG for the newest version of Camera Raw( not compatible with older versions)? ( dng CONVERTER/ PREFFERENCES) If I convert a RAW file for use in older versions of

  • Library corruption after moving images from one project to another.

    Hi, I have Aperture 1.5 running on a PowerMac G5. I'm using an external disk (via FW800) for the library. The disk catalog has no problems. Today I want to reduce the number of projects and move a few images between projects. There is one project wit

  • LACP or not in vPC?

    hi out there I have defined a vPC between 2 sets of nexus boxes: nx51 ----vpc11--><--------vpc21--------nx53 II II vpc10 peerlink vpc20 peerlink II II nx52-----vpc11--><---------vpc21------nx54 vpc10 & vpc20 is running lacp but vpc11 & 21 are not - I