• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

RE: Advancing Project Status and Transferring Objects

Gergely_Pongracz

Well Known Member
RE: Advancing Project Status and Transferring Objects

Hi!
I did it succesfully some times. I used the standard OMW setup with some
slight modifications. I inserted a new custom status for my own purposes,
where I used different path codes for checkin and checkout. It worked
perfectly. Our system didn't have a CRP (Prototype) Path Code therefore I
inserted a Status Change Rule from development to QA Complete and modified
QA Complete->Procuction Rule so that the transfer rules contained a DEV-PROD
transfer, not a CRP-PROD Transfer...
Some other experiences:
I got General Error in Method, Checkout where the setup was incorrect for
some reason.
I couldn't do any status change as long as I had any object checked out
(quite obvious)
The logging function is quite useful both for projects and objects. For
example checkouts are logged down to the number of spec records and the
names of the required files.
Hope it helps a little bit!
Regards:
Gergely Pongrácz
Synergon, Hungary

> ----------
> From: Moulin, Sylvie[SMTP:sylvie.moulin@eds.com]
> Reply To: jdeowdev@jdelist.com
> Sent: Monday, December 18, 2000 8:02 PM
> To: jdeowdevml@jdelist.com; jdelistml@jdelist.com
> 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: sylvie.moulin@eds.com
>
> 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
> *************************************************************
>
 
Top