Re: XE: Advancing Project Status and Transferring Objects

Guest

Guest
Re: XE: Advancing Project Status and Transferring Objects

Hi there,

We have successfully done this, transference rules exist to copy the specs
from DV7333 to PY7333 upon change of project status. The error message that
you are getting is very common and so there might be several possible
reasons, but the main possibility is that your setup is not quite right.
Ensure that all objects in the project are checked in, that the rules for
the person trying to advance the project are setup correctly in the user
role allowed actions. One possible gotcha is in the transfer activity
rules: ensure that all object types are defined for transferral such as
APPLVER, UBEVER etc.., also ensure that the UO object type is included and
specify the from and to location (probably Central objects-DV733 --->
Central Objects PY7333 for example).

Other things to check are of course the OCM mappings for the tables that
you have listed below (F987* tables) and the ODBC setup. Good Luck.



Technical Development Specialist
Developing World Systems Ltd
JDE Consulting Partner of the Year 2000 - SUMAH Region
+ 44 (0)1494 896600 Switchboard
+ 44 (0)1494 896603 Direct
+ 44 (0)1494 896611 Fax

[email protected]
Xe SP13, AS400 V4R4,





"Moulin, Sylvie" <[email protected]> on 12/18/2000 05:02:42 PM

Please respond to [email protected]

To: [email protected], [email protected]
cc: (bcc: Andrew Holder/Tamro)
Subject: XE: Advancing Project Status and Transferring Objects




Hello,

Has anybody been able to successfully advance a project to a status that
should transfer objects from one environment to another ?

The setup has been done in Object Transfer Activity Rules. I'm able to
advance a project only if it does not involve any object transfers. In OMW
when I try to advance the status, the error message I get is: Error:
General Error in Method, Status Change.

I found out error messages at different places in the JDEDEBUG.LOG saying:

Dec 18 12:43:57 ** 231/248 The RDBAccess Obj for table, F98752, at
address, 0x429af90, is not allowed to insert any records.
Dec 18 12:43:57 ** 231/248 The RDBAccess Obj for table, F98753, at
address, 0x429c8e0, is not allowed to insert any records.
Dec 18 12:43:57 ** 231/248 The RDBAccess Obj for table, F98750, at
address, 0x429eaf0, is not allowed to insert any records.
Dec 18 12:43:58 ** 231/248 The RDBAccess Obj for table, F98751, at
address, 0x42a0930, is not allowed to insert any records.
Dec 18 12:43:58 ** 231/248 The RDBAccess Obj for table, F98740, at
address, 0x42a2600, is not allowed to insert any records.
Dec 18 12:43:58 ** 231/248 The RDBAccess Obj for table, F98741, at
address, 0x42a40b0, is not allowed to insert any records.
Dec 18 12:44:02 ** 231/248 The RDBAccess Obj for table, F98761, at
address, 0x4292a00, is not allowed to insert any records.
Dec 18 12:44:02 ** 231/248 The RDBAccess Obj for table, F98760, at
address, 0x429bbb0, is not allowed to insert any records.
Dec 18 12:44:09 ** 231/248 The RDBAccess Obj for table, F9860, at
address, 0x428f2b0, is not allowed to update any records.
Dec 18 12:44:09 ** 231/248 The RDBAccess Obj for table, F9861, at
address, 0x42aa0a0, is not allowed to update any records.


I have done OCM mappings for these tables. Denver says it's a security
problem on the SQL server but we don't seem to find were the problem could
be.
Any ideas? Any help would be greatly appreciated.

Thank you,

Sylvie Moulin
EDS
Tel: 514-390-2266
Fax: 514-866-8427
Email: [email protected]

OneWorld XE SP 13
NT
SQL 7




*************************************************************
This is the JDEList One World / XE Developers Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Back
Top