Batch Version (P98305W) Version Error

After our latest tools release update there was a special instruction that I forgot to do on one of the environments.  It was to delete all versions of the Batch Versions (P98305W) application.  Usually, there will be just one version: ZJDE0001.

Well, since I forgot, to the left is the error that you might get if you don’t do it.  The second image is the Interactive Versions screen that you will need to use to delete the version.

Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, jde, Tools Release, Tools Release, version, versions

Quick EnterpriseOne Version Security Solution

Whether you are trying to change the processing options of an interactive version or a batch version.  Sometimes you can run into issues where the application indicates that you do not have authority to change the version like the example to the left.

To quickly get around this error, we can use SQL to change the security setting in the F983051.

 

UPDATE CODV811/F983051
SET VREXCL = 0
WHERE vRPID = 'P03B2002'
AND VRVERS = 'TEST0001' 

Tags: batch version, e1, enterpriseone, EnterpriseOne - Security, EnterpriseOne - SQLs, security, sql, version

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