EnterpriseOne (E1) Version Promotion With Security

The other day our development manager came to me and stated that she could not promote a version to production.

In order to take any security out of the picture, I tried to promote it with my admin id.  I received the same error: "General error promoting object".  As with most E1 error messages, this was not real helpful. 

I then looked at the object in the Batch Versions application and happened to notice that the version that was causing the issue had version security set to 2.  According to the the documentation a "2" in the version security options:

2 (medium to full security)  This level allows all users to install or copy the version, but lets only the "Last Modified By" user complete all the tasks.

NOTE: The broken-English is the documentation’s not mine.

Because of this setting I was unable to make any changes to this security through the application.  Instead, I used SQL:

update codv811/f983051
set vrexcl='1'
where vrpid = 'xxxxxx'
and vrvers = 'xxxxxx'      

Hope this helps!

Hey, have you ever had trouble with this or something similar?  If so, how did you get things to work again?

Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - SQLs, jd edwards, jde, oracle, peoplesoft, security, sql, version, versions

Related posts

• You’re Fired! …But You’re Still Here? – Cleaning EnterpriseOne (E1) Orphaned Records After Deleting a User Profile (0)
• Problems Deleting An EnterpriseOne (E1) Custom Object (0)
• iSeries JDBC jt400.jar – {note to self} (0)
• Introduction to Me (1)
• How To Get A Date… Out Of E1 Part 2 (0)