Problem Note 37008: Cannot move products from an existing plan to a new manual plan
 |  |  |  |  |
In SAS® Markdown Optimization, you might not be able to move members from current plans into new active plans. You might see errors similar to the following in your SAS® Merchandise Intelligence middle-tier log:
2009-03-13 14:34:33,948 [RMI TCP Connection(2293)-10.216.2.253] ERROR com.sas.solutions.di.server - Exception thrown during the invocation of method com.sas.solutions.di.server.mdo.MDOService.createPlan. javax.management.MBeanException: Exception thrown in operation createPlan at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java(Compiled Code)) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java(Compiled Code)) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java(Compiled Code)) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java(Compiled Code)) at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sas.solutions.di.server.Server.privateInvoke(Server.java(Compiled Code)) at com.sas.solutions.di.server.Server.invoke(Server.java(Compiled Code)) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java(Compiled Code)) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java(Inlined Compiled Code)) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java(Compiled Code)) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java(Compiled Code)) at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java(Compiled Code)) at sun.rmi.transport.Transport$1.run(Transport.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at sun.rmi.transport.Transport.serviceCall(Transport.java(Compiled Code)) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java(Compiled Code)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java(Compiled Code)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java(Compiled Code)) at java.lang.Thread.run(Thread.java(Compiled Code)) Caused by: com.sas.solutions.di.server.mdo.api.PlanMembershipConflictException: Plan members conflict with existing active plan at com.sas.solutions.di.server.mdo.PlanMembershipFacade.checkMemberConflictsAndThrowException(PlanMembershipFacade.java:415) at com.sas.solutions.di.server.mdo.PlanMembershipFacade.addPlanMembers(PlanMembershipFacade.java:81) at com.sas.solutions.di.server.mdo.PlanFacade.createPlanWithoutPlanLimitCheck(PlanFacade.java:288) at com.sas.solutions.di.server.mdo.PlanFacade.createPlan(PlanFacade.java:255) at com.sas.solutions.di.server.mdo.MDOService.createPlan(MDOService.java:182) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) ... 29 more
This issue prevents geo-prods that exist in deleted active plans from being added to a new plan until after the next weekly batch process (which cleans up the mdo_plan_member table).
Do the following tasks to work around this issue:
- Create a new INACTIVE plan.
- When prompted to move plan members, select Yes.
- Make any necessary changes in the INACTIVE plan.
- Make the plan ACTIVE.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Markdown Optimization | Microsoft Windows 2000 Advanced Server | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft Windows 2000 Datacenter Server | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Server | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Professional | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows NT Workstation | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Standard Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2008 | 3.2 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows XP Professional | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Windows Vista | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled AIX | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
A fix for this issue for SAS Merchandise Intelligence 3.2 is available at:
http://www.sas.com/techsup/download/hotfix/ro32.html#037008| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2009-08-31 16:32:41 |
| Date Created: | 2009-08-27 11:17:31 |