Deployment with fairshare rule B

Hi Gurus,
Could anyone please explain me with a example(easily understandable) about the SNP Deployment with fairshare rule B..with an example and how the calculation is done..
Thanks

Hi,
Two cases are explained below to demonstrate FS B behavior.
DC1 :
Demand : 100
Target stock level : 200
Stock : 30
DC2 :
Demand : 120
Target stock level : 100
Stock : 10
Case 1:
Source : ATD qty 100
In this case Deployment will confirm as follows
DC1: 30
DC2: 70
By deploying stocks as above the demand shortfall in both locations is equal (50 nos).
Case 2:
Source : ATD qty 240
In this case Deployment will confirm as follows
DC1: 110 (70 for demand + 40 for SS)
DC2: 130 (110 for demand+ 20 for SS)
Demand met: DC1 = DC2 = 100%
Target stock level: DC1 = DC2 = 20%
In this the demand is first met 100 % for deploying stocks and the rest of the ATD qty (240 - [110+70] = 60) is distributed in such a way that the % target stock level in both locations is the same.
Hope this is clear. Pls let me know if you need further calrifications
regards,
Ashok

Similar Messages

I have updated my BRE with new rule but it is not working.

Hi All,
I have got a requirement to add one more rule into my existing BRE.
Below are the points that I followed :
1).Firstly, I created the new version for my BRE , and added my rule in that.
2). Then I un-deployed the previous version of BRE and Deployed its new version.
3). I did restarted host instances and Rule engine service also.
3). Now, when I am testing the sample consisting of previous rule then it is executing,
But on the other hand when i am testing the sample based on my new rule then BRE is not working.
If BRE is Executing with previous rule then i believe it is working,
Then why it is not working for my new Rule .
4). When i am testing my policy then it is also working well enough .
Note : The Schema path is also correct ,
Any help and suggestion will be appreciated
Kind Regards
Rishi Gaur

Hi Shankycheil,
1). My policy version 1.0 was having 10 rules.
2). Then i copied version 1.0 and added it to my new version 1.1 .
3). Than i added my rule to it only.
After all this I Undeploy version 1.0 and deployed my new version 1.1.
In Admin console I am getting error like you mentioned somewhere about policy not found?

Planning -v11.1.1.1 - Cannot Communicate with Business Rules

Hi,
We are unable to log into Business Rules no matter how many times we recreate users and properly provision them. I found this in the 11.1.1.1 Installation and Configuration Guide but have no idea of where or how to make this change.
Planning
• After you manually deploy Planning, Business Rules does not communicate with Planning. To work around this issue, add the following Java Options:
-DESS_ES_HOME=/hyperion/products/Essbase/eas/server -Dhyperion.home=/hyperion -DHYPERION_HOME=/Hyperion [8622082]
Where exactly would we do this and could it possibly help?

Issue is with SSH the SSH ware running in two sys and conflict issue.
Restored the Open DAP and suggested the client to re start the Service and server ones.
Client can successfully able to log to EAS and to BR now.
Couple of BR access issue is resolved by provision and Refresh of Manage database.

RTP not working with Business Rule

I am trying to create a buisness rule that fixes on a member in a custom dimension based on a run time prompt using Calc Manger (11.1.2.2). I created the variable at the cube level, set it to 'Member' and selected the appropriate dimension, and selected RTP. The FIX statement is very simple FIX("Current",{Contract}). The rule validates and deploys with no problem. When running the rule either on form save or through Business Rules I receive the error: "error parsing formula for [FIX STATEMENT] (line 2): invalid object type. If I change the variable to uncheck 'RTP' and place the same member used previously as the Default value the rule runs no problem. Is there any reason why the rule appears to not be able to read in my RTP selection?
Thanks,
CS

Though this is not a calc manager issue, I am sure the member that Planning is picking up is a member that is set tyo dynamic calc.
You cannot use a member that is set to dynamic calc in a fix.
-Sree Menon

Period account closing bal includes cumul movements, even with a rule.WHY?!

Hello chaps, I've been struggling with this for a few days now and I'm going to have admit defeat. :(
I'm trying to do two things.
1. View periodic balance sheet movements
2. Get the correct custom closing balance to roll up once I've done 1 (in Periodic view)
What I've done.
For Point 1. I use the SwitchTypeForFlow attribute on the flow members. This let's me see the balance sheet movements in Periodic view. Great.
Which leads me onto Point 2. Whilst I can now see the balance sheet movements in Periodic view, the closing balance (the parent of Opening + increases - decreases) does not total correctly. Instead of adding the Opening + increases - decreases for ONE period, It adds them for ALL the previous periods.
Ok, so to get round that, I thought I'd just create a new member called "ClosingBal" and override what HFM is doing. I'll now have two rules. The "OpeningBal" is just the closing balance of last period. "ClosingBal" is just the sum of opening + increases - decreases for the period. So here are the two simple rules
HS.Exp "C1#OpeningBal=C1#ClosingBal.P#Prior"
HS.Exp "C1#ClosingBal=C1#OpeningBal+C1#increases-C1#decreases"
But when I do this, even with the rule, it STILL adds up the cumulative increases and decreases for all prior periods as well, not just the ones for the period. Why is it doing that? All I want is my closing balance in that one period to be equal to opening balance + increases - decreases. It works fine in YTD view, but not Periodic view. I need it to work in Periodic view
any help much appreciated.
Thanks,
Sal

Sal,
There is no solution here that allows the user to simpley change the View member from Periodic to YTD, keeping all else the same, and get your desired result. However, you could create a solution that when a user wants Periodic numbers he/she would select the Periodic View member and then select a unique ClosingBal member (eg. 'ClosingBalPer') and a unique OpenBal member (eg. 'OpenBalPeriodic'). When the user wants YTD numbers he/she would select the YTD View member and then select a different and also unique ClosingBal member (eg. 'ClosingBalYTD') and a different and also unique OpenBal member (eg. 'OpenBalYTD').
Here you would have 2 different rules for you opening balances:
HS.Exp "C1#OpeningBalPer=C1#ClosingBal.P#Prior"
HS.Exp "C1#OpeningBalYTD=C1#ClosingBal.P#Last.Y#Prior"
And your ClosingBal rules would look like this:
HS.Exp "C1#ClosingBalPer=C1#OpeningBalPer+C1#increases-C1#decreases"
HS.Exp "C1#ClosingBalYTD=C1#OpeningBalYTD+C1#increases-C1#decreases"
In regards to the ClosingBal rules, these aren't necessary if you make the ClosingBal member a parent of the other members. If 'decreases' need to be subtracted then they should be flagged as 'SwithSignForFlow'.
With this solution if a user selected YTD with the Periodic members or Periodic with the YTD members then their numbers wouldn't make sense so there would be some user eduction involved with this solution.

List Tile View not working with include rule on iOS?

hi Expert,
I used the List Tile View with include rule in Agentry 6.0 on WinCE before to generate "selected" object list upon different conditions, e.g., assigning tasks based on scenarios.
Currently, I am experimenting the same function on iOS tablet.
On the start screen which is a detailed screen for main object, there is a List Tile View and an include rule. However, the objects in the tile list are not updated correctly when the output of the rule changes. Note that the same include rule works perfectly with a List View for the same collection.
To my observation, the problem seems to associated with "update" of the tiles when result of include rule changes. For example, in scenario 1, there are 5 objects in the list; switching to scenario 2, there are 10 objects. From the No.6 to No.10, the objects are correct. The No.1 to No.5 are still the original 5 objects for scenario 1.
When the user clicks on tiles, it makes the situation worse. Normally, a single object's tile will always be shown in the selected tile regardless which tile is selected from the list.
My development environment is 6.0.40 and the client is 6.0.40 on iPad (iOS 7.1). I would like to know whether this is a known issue before I provide more details.
Thanks.
-Yang

hi experts,
When I asked the question on this list tile view refreshing issue, my dev environment is Agentry 6.0.38.
In Agentry 6.0.40.1's release note, there is a fixed
AG-25821 iOS 7 refresh issue with iPad tile list
However, I currently have Agentry 6.0.42.1 on iPad (iOS 7.1.2). And my editor/server is 6.0.42.0. I still have the list tile view refreshing issue. The same rule can be used on list without any problem. But the list tile still has trouble on display the right set of objects.
My question is is that fix related to the problem I saw?
Thx.
-Yang

Slow Performance with Business Rules

Hello,
Has anyone ever had slow performance with business rules? For example, I attached a calc script to a form and it ran for 20 seconds. I made an exact replica of the calc script in a business rules and it took 30 seconds to run. Also, when creating / modifying business rules in EAS it takes a long time to open or save or attach security - any ideas on things to improve this performance?
Thanks!

If you are having issues with performance of assigning access then I am sure there was patch available, it was either a HSS patch or planning patch.
Cheers
John
http://john-goodwin.blogspot.com/

What's Wrong with These Rules?

I can't see what's wrong with these rules. Does any one see the problem?
Passport data is verified if
Database provides an exact match for the passport number and date of birth.
Photo matching is required if
Passport data is verified.
Passport photo matches evidentiary photo if
Photo matching is required and
Photo match is valid.
Photo match is valid if
Photo matching is required and
user states that photo matches evidentiary photo.
The investigation session asks the question "does Database provide an exact match ..." Response is True.
"Photo matching is request" is set to true because "Passport data is verified" is true.
Then the investigation stops. It doesn't go on and ask if "user states that photo ...". This arrtibute has the value of <unknown>. All the identifiers (red numbers) match up correctly. I just can't see what is wrong.
Thanks,
Terry

Thanks, Brandon,
Your idea was helpful. It was a goal, but not a top level goal. By checking the data at each step, I found that a higher level rule that was dependent on these rules was the culprit. I should have had an "and" when I had wrote the rule with an "or". I don't entirely understand why this higher level rule needed to have "and" instead of "or", but it works now and that's all I care about.
Terry

Java DC not deployed with WebDynPro DC

Hi,
I've been testing the DC functionality and I'm trying to create the following:
1) WebDynPro DC (DCA)
2) Java DC (DCB)
DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
DCA has a small table in the view that I'm filling (or trying to) with data from the database.
DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
Purpose is set to compilation, and there is a
<at-build-time/>
tag in the .dcdef file.
Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
Shortly: how to get DCB to deploy ?
Any help is appreciated here
Kind Regards,
Jari Pakarinen

Hi,
What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
Thank you for your help, I'm not blaming you or anything
Regards,
Jari

How to append calling and called number with translation rules?

Hello,
I have one question about digit manipulations.
How to append calling number and called number with IOS commands?
For example, when 123 dials 45678, translations have to be performed and the new called number to be 12345678.
Thank you,
I will vote this conversation.

It is not possible with translation rules.
However, you can do that with a TCL/IVR script.

How to use MDS deploying with EAR file

Hi everybody.
I would to use MDS in my web application in order to use customization across the sessions. I've performed every step to do this on JDeveloper (11.1.1.3.1). I've tested my application deploying directly from JDeveloper using Application menu > Deploy > "myApp" to "myApplicationServer" (in this way I can choose the repository with a window like this: http://i.stack.imgur.com/Kci9c.png). The repository was prevoiusly registered on the server. In this way my application works fine and they all lived happily ever after.
My problem occurs when I perform the deployment with "myApp to EAR" mode. When I try to install my EAR file in weblogic, it reply me with this error message:
An error occurred during activation of changes, please see the log for details.
+:oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.+
I've looked for a solution around the web (included this forum) and I think that I should modify something in adf-config.xml file (below).
Which steps I have to perform in order to install my application correctly with an EAR file?
Thanks in advance.
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config"
xmlns:ads="http://xmlns.oracle.com/adf/activedata/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="BDO_GC_WEBAPP.bdogc"/>
</adf:adf-properties-child>

<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
<sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"
authenticationRequire="true"/>
</sec:adf-security-child>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
<persistent-change-manager>
<persistent-change-manager-class>
oracle.adf.view.rich.change.MDSDocumentChangeManager
</persistent-change-manager-class>
</persistent-change-manager>
<taglib-config>
<taglib uri="http://xmlns.oracle.com/adf/faces/rich">
<tag name="column">
<attribute name="displayIndex">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="frozen">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="noWrap">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="selected">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="visible">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="width">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
<tag name="table">
<attribute name="filterVisible">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
</taglib>
</taglib-config>
</adf-faces-config>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
<match path="/">
<customization-class name="oracle.adf.share.config.UserCC"/>
</match>
</cust-config>
</mds-config>
</adf-mds-config>
</adf-config>

Any suggestion?

EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

Hi All ,
           I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
     D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
     Deploy finished with warnings.
--- Description:
            S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed:           0
Deployed with warnings:           1
Failed deployments:                0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
     Name:erecapp
     Vendor:asianpaints.com
     Location:J2N_ERECTT_D
     Version:20090217100038
     Deploy status:Warning
     Version:HIGHER
     Description:
          1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

You have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
     <persistence-unit name="YOUR_UNIT">
    <jta-data-source>DSNAME</jta-data-source>
Frank

Error with Statement Rule: Reference is ambiguous

Hello,
Hopefully someone will be able to help me out with this inquiry. I have a configurator model where the BOM has been imported. Within this model, there are two BOM nodes of the same name (Item Number) but they are unique in the model by their effective dates. Basically, I have the following:
Model
__Feature1
____Option1 Eff_In: 1/1/2009 Eff_Out: 9/20/2011
____Option1 Eff_In: 12/21/2011 Eff_Out: 9/21/2090
If I create say a CONTRIBUTE statement rule referencing node 'Option1', I get an error that reads "The reference Option1 is ambiguous". I understand that I am getting this error because Configurator cannot determine which instance of this Option1 I am referring to. Can anyone tell me how I can specify the specific node required? I would have expected that Configurator would always look at the structure effective dates, but it would appear not. I have looked at using full path or properties as part of my node reference, but the effective dates don't appear to be a standard system property that can be referenced (unless I missed something).
Any help would be appreciated.
Thanks,
Paul Wentink

From: Veerendra Singavarapu <veerendra.singavarapu@...>
Sent: Sun Aug 15, 2010 12:50 am
To: [email protected]
RE: [configsig] ambiguity error
Hi Lauree,
As Carole rightly pointed out, this issue has been recently fixed in 11.5.10 branch. This happens only when the ECO change brings one or more item’s attribute changes. i.e. for instance an OC undergone an ECO change, with {min=0 and max=null} prior to ECO change and {min=0 and max=1} after ECO change can cause this issue.
With regards,
Veerendra S.
==========
From: Lauree Swihart [mailto:lswihart@...]
Sent: Friday, August 13, 2010 10:52 PM
To: [email protected]
Subject: RE: [configsig] ambiguity error
Thanks a bunch Carole!
==========
From: [email protected] [mailto:[email protected]] On Behalf Of Landgrebe, Carole
Sent: Friday, August 13, 2010 1:21 PM
To: [email protected]
Subject: RE: [configsig] ambiguity error
Hi Lauree-
This is a known issue, and I had them create a fix for it in 11.5.10 when we were on 25-43A. Now the issue exists in 12 and I haven’t yet logged the TAR for that. We have exactly the same issue as we force all bom changes through ECOs, and even putting effectivity dates on the rules that match the effectivity dates of the BOM does not resolve the issue. Fix was produced off of TAR 7619362.994, looks like bug number was 8737252….not sure what release it was part of, we applied it as a manual fix, a jar file and an update to package body for cz_model_util_pvt.
Holler if you need more info.
Thanks!
Carole
==========
From: [email protected] [mailto:[email protected]] On Behalf Of Reinsch, Ted A (GE Energy)
Sent: Friday, August 13, 2010 1:09 PM
To: [email protected]
Subject: RE: [configsig] ambiguity error
Have you refreshed the model since this change?
The only time I have received this error was if I was using the same component in more than 1 option class or option feature and it tells me that I need to further define the path to the object in the rule such as
'ATO Model Name'.'Option Class 1'.'8003-518.8003-519.8003-502.029-4572-03' or
'ATO Model Name'.'Option Class 2'.'8003-518.8003-519.8003-502.029-4572-03'
==========
From: [email protected] [mailto:[email protected]] On Behalf Of Lauree Swihart
Sent: Friday, August 13, 2010 10:45 AM
To: [email protected]
Subject: [configsig] ambiguity error
I have a component that is currently in a logic rule. When this component is in a logic rule it works.
This same component was changed out on an ECO, causing 2 records in the BOM. One with an end effective date and another with a begin effective date. When I convert my rule to a statement rule, I receive this error. I’ve received this error in the past and normally I thought I’d just changed the effectivity range associated with the rule and that resolved the issue. But, it’s not resolving the issue today.
Is there any other way for me to resolve this without deleting the component in the bom that has been effectively end dated? I don’t want that route because that defeats the purpose of using an ECO and general foundation of why we use ECO’s for our healthcare products.
The reference 8003-518.8003-519.8003-502.029-4572-03 is ambiguous.
Thanks,
Lauree Swihart

Something interesting with check rule for VAT registration no.

Hi Guys,
I found something weird in sap with check rule for VAT registration no.
If I set any of check rules for US and save(tcode oy17), then change the country of a customer from DE to US and save(not change the VAT registration no), the system post error messages "ISO code DE is not correct in the VAT registration number". But if I set rule for AU(australia) with same rule as US, and change the customer's country from DE to AU(not change the VAT no), no error happens and customer can be saved successfully. So anybody can give any explanation on this problem?
Thanks in advance, point will be rewared. Waiting for the comments.
Regards,
Alex

<TABLE align=center border=0 cellPadding=1 cellSpacing=1 width="95%"><tr><td width="15px"><input type="image" src="wwv_flow_file_mgr.get_file?p_security_group_id=1046425373323359&p_fname=add2d1.jpg" name="add_QTB_5174" id="add_QTB_5174" onclick="javascript:addRowToTable('QTB_5174',4,22.5);return false;"/></td><td width="15px"><input type="image" src="wwv_flow_file_mgr.get_file?p_security_group_id=1046425373323359&p_fname=delete2d.gif" alt="delete" name="delete_QTB_5174" id="delete_QTB_5174" onclick="javascript:removeRowFromTable('QTB_5174');return false;"/></td><td><input type="image" src="wwv_flow_file_mgr.get_file?p_security_group_id=1046425373323359&p_fname=edit2d.jpg" alt="edit" name="edit_QTB_5174" id="edit_QTB_5174" onclick="javascript:updateTableRow('QTB_5174',22.5);return false;"/></td></tr></table>
<input type="hidden" value="QTB_5174" id="5174"><TABLE align=center border=0 cellPadding=1 cellSpacing=1 width="95%" id="QTB_5174" name="QTB_5174">
this a sample code. I have marked the name attrib in bold.

Logical M:N Relation with Delete Rule:"NO ACTION" creates "CASCADE" FK

I think I've detected a bug in the generation of FK when we have"N: N" relations, give me idea that the delete rule that is defined in the relationship of logical model is ignored.
So I give you a small example to reproduce it:
I've a simple example of 2 entities:
Logical Model:
Entity_A(#id_a, desc)
Entity_B(#id_b, desc)
M:N Relation between Entity_A and Entity_B (REL_A_B) with Delete Rule: "NO ACTION".
When apply "Engineer to Relational Model" I've as result 3 tables:
Relational Model:
Entity_A(#id_a, desc)
Entity_B(#id_b, desc)
REL_A_B(#id_a, #id_b) but the generated foreign keys are defined using Delete rule "CASCADE".
Is not supposed to have been generated with delete rule "NOT ACTION"?
As result the generation of DDL scripts is creating FKs with the clause " ON DELETE CASCADE", which was not originally intended.
I try to change this value in logical model but I've seen not effect on result.
I hope I have helped!

Hi Ariel,
thanks for reporting the problem. I assume it's for Data Modeler 3.3.
I logged a bug for that.
Philip

Deployment with fairshare rule B

Similar Messages

Maybe you are looking for