Problem Note 44568: 'Import Failed. Nothing was imported.' when importing SAS® Financial Management adjustment rule
When importing adjustment rules, you might encounter a message similar to:
Import Failed. Nothing was imported.
in SAS Financial Management Studio.
You might also see messages similar to the following in the <SASFinancialManagement5.x> log:
ERROR AbstractFlushingEventListener Could not synchronize database state with
session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC
batch update...
Caused by: java.sql.BatchUpdateException: Duplicate entry '105-0' for key 2...
ERROR MemberGroupHome get failed
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC
batch update...
ERROR RuleManagerBean createRule() - u:sasdemo - Error
creating Rule MOVE_AMA1b
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC
batch update...
ERROR ResultRuleManagerBean appendRule() - u:sasdemo - Error
appending rule MOVE_AMA1b to result 5
javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception
is: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC
batch update...
And you might see messages similar to the following in the SAS Financial Management Client log file:
[ModalContext][DEBUGExceptionWrapper] - Allocating buffer for
exception of size 9387
[ModalContext][DEBUGExceptionWrapper] - Could not deserialize
Exception:
java.lang.ClassNotFoundException:
javax.ejb.TransactionRolledbackLocalException...
[ModalContext][DEBUGExceptionWrapper] - Returned stack trace
of:java.lang.reflect.InvocationTargetException...
Caused by: java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested
exception is: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ;
nested exception is: org.hibernate.exception.ConstraintViolationException: Could
not execute JDBC batch update...
Caused by: java.sql.BatchUpdateException: Duplicate entry '104-0' for key 2...
[ModalContext][DEBUGTransportManagerHttpService] - Return
result:
[ModalContext][DEBUGTransportManagerHttpService] -
java.lang.reflect.InvocationTargetException toString()
java.lang.reflect.InvocationTargetException
[main][ERRORImportRulesWizard] -
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException...
If you are unable to export certain adjustment rules, try to determine whether the problematic rules were originally imported from another environment.
We have found that this situation might occur if there are more Analysis dimension members in the Source environment that in the Target environment. When the import process looks up the Analysis member codes on the Target environment, some member codes are not found. If the Analysis member codes are not found, the system sets the member ID to 0. If there is more than a single instance of Analysis member codes not found, the rule import process fails.
To workaround this issue, remove the 'extra' Analysis dimension members from the Source system model before exporting the adjustment rules. Once you do that, the Analysis dimension members should all match, and the rule import process should complete on the Target system.
This is marked as fixed in SAS Financial Management 5.3.
For the default location of SAS Financial Management log files, please refer to SAS Note 20058.
Operating System and Release Information
| SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Windows Vista | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Windows Vista for x64 | 5.1 | 5.3 | 9.2 TS2M0 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
This problem might occur for certain rules, but not for all rules.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2011-10-06 12:54:46 |
| Date Created: | 2011-10-06 11:55:11 |
