4/10/2021 Document 1487424.

1
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

E1: RDA: Frequently Asked Questions on Batch Versions (Doc ID 1487424.1)

In this Document

Purpose
Questions and Answers
Overview
Question 1: What is a Batch Version?
Question 2: Where can I find additional information on Batch Versions?
Question 3: What report properties are stored at the version level?
Question 4: How do I deploy a Batch Version?
Question 5: How is the check-in, check-out and advanced get of Batch Versions different from other objects in
OMW?
Question 6: What is a Web Only Batch Version?
Question 7: With what release level are Full Batch Versions on the Web available
Question 8: How do I retrofit a custom version with event rule overrides after an upgrade or ESU?
Batch Versions Application
Question 1: Why does the Web Batch Versions application not have the option to display only "My Versions"?
Question 2: Why do I receive an error on the "Find Allowed Actions" Business Function when selecting a version in
Batch Versions?
Question 3: User A creates a new batch version on own workstation. User B signs in to own workstation, version
created by User A is not an available version to execute. Why?
Question 4: Why does version in F983051 with VRSAVAIL = N not display in Batch Application?
Version Table F983051
Question 1: When creating a new Batch Version, where is the information stored?
Question 2: How are the columns VRUSER, VRVED, VRUSR0, VRVCD in F983051 populated?
Question 3: On web client, after changing data selection in Batch Versions, User (VRUSR0) and VRVCD (Last
Modified date) are not updated in F983051.
Question 4: F983051 Date Last Executed (VRVED) in target environment is updated when promoting UBE version
Version Security
Question 1: What does the Values in the Security Column mean in Batch Version Application?
Question 2: How do I change the Security on a Batch Version
Question 3: Can a User who created the Report Version be able to Change the Security Level without Checking it
Out?
Question 4: When Version Security is set to '1' (Medium Security), when user Change Processing Options from
Prompt for Values on the Web Client, The "Last Modified By" User is Updated. How to Prevent this?
Question 5: Version Security is set to '1' (Medium) and StrictVersionSecurity is set to '1', the Menu Task Disappears
on the Fat Client but not on the Web Client. Why is there a difference?
Question 6: How can security be defined to prevent user's from executing a version of a report?
Question 7: Is there a way to Mass Update EnterpriseOne Batch Versions to Setup Security so that Users are Not
Allowed to Change or Delete Versions but Allowed to Create Versions for the Same UBE?
Question 8: How to secure Prompt for Values from the Task Menu, but still allow the Versions' Owners to Modify
Processing Options in Batch Version Application?
Version Overrides
Question 1: When in RDA at the Version level, why is the OK button disabled ?
Question 2: Is it possible to produce a report of all versions that have version overrides?
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 1/15
4/10/2021 Document 1487424.1

Question 3: In Batch Versions, which Row Exit affects the Override Version Specifications?
Question 4: Sort Sequence has been overridden in my Level Break Header section, however why am I not able to
change level break items in Version Design?
Question 5: Is there a way to identify versions that are out of sync between central objects and server specs?
Processing Options
Question 1: How do you print the Processing Options of a Batch Version without executing the report and printing
the cover page?
Question 2: Why are Runtime Processing Options saved, but Runtime Data Selection is not?
Question 3: How can I retrieve Processing Options Values of a Version on the report?
Question 4: Why is it not possible to change the prompting field under the version detail when copying a version?
Question 5: UBE version does not retrieve processing options values when submitted from either fat client or from
server via scheduler/runube/runubexml/report interconnect
Version Detail
Question 1: How to print Version Detail text in Report?
Version Submission
Question 1: When submitting a Batch Version from the Web, why do I get the error "Versions with Client Platform
marked as "Client Only" cannot be submitted from the web"?
Question 2: How do I specify a Job Queue for a Batch Version?
References

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version SP24 and later

Information in this document applies to any platform.

PURPOSE

This document provides answers to frequently asked questions on Batch Versions.

QUESTIONS AND ANSWERS

Overview

Question 1: What is a Batch Version?

Answer 1: Batch Versions are required for any report in order to execute the report. Batch versions read the master
specifications from the report template. The sections and fields that you select in the report template appear in the associated
batch versions. However, batch versions typically differ slightly from the report template. You can define different data
selection, data sequencing, and processing options for each batch version.

There are also several report specifications that can be overwritten at the version level, including:

Layout
Data Selection
Data Sequencing
Event Rules
Database Output

Batch versions enable you to preserve template integrity while providing custom processing to meet a specific business need.
Instead of creating a separate report template to provide multiple variations of a report, you can create one report template
with multiple batch versions. For example, you might design a monthly variance report that contains totals for the entire

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 2/15
4/10/2021 Document 1487424.1

company. If you need to run a quarterly variance report that includes only data for the Western region, you can create a
version of the report template and define data selection to meet the requirement.

Batch versions process the specifications read from the report template and any changes that are overwritten in the version.
Batch versions first read the master specifications from the report template, then override these specification with the version
specifications. You can create additional batch versions by either adding a new version or copying an existing version.

When you submit a batch application you must use a batch version. Depending on how the report was designed, when you
submit the batch version you might have the option to override:

Processing option values

Data sequencing
Data selection
Default locations

You must create at least one batch version for each report template before you can process the report. You can create batch
versions automatically in JD Edwards EnterpriseOne Report Design Aid (RDA) using the Report Director. You can create
additional batch versions from the JD Edwards EnterpriseOne Batch Versions application by:

Adding a new batch version

When you add new batch versions, the new versions read the specifications from the associated report template or
master specifications.

Copy an existing batch version

The new version inherits all of the master report specifications and any overrides that are defined in the version that is
copied

Question 2: Where can I find additional information on Batch Versions?

Answer 2: For additional information on Batch Versions, refer to the JD Edwards EnterpriseOne Tools Batch Versions
Guide available to download from JD Edwards EnterpriseOne Documentation.

Question 3: What report properties are stored at the version level?

Answer 3: There are certain report properties that are stored at the version level and when a change is made to the
template, these options do not automatically get updated on an existing version. Any new versions that are created will have
these changes, but the changes are not inherited by the existing versions. When this type of change is made at the report
template level, you also have to go into the existing versions and make the change at the version level as well.

The following are the properties that are NOT inherited by versions when changes are made at the report template level:

1. Report properties
2. Printer setup
3. Font

The following are the properties that are inherited by versions when changes are made at the report template level UNLESS
they are overridden at the version level:

1. Section Layout
2. Section Data Selection
3. Section Event Rules
4. Section Database Output
5. Section Sort Sequence

The following are the properties that cannot be changed at the version level:

1. Processing option template used

Question 4: How do I deploy a Batch Version?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 3/15
4/10/2021 Document 1487424.1

Answer 4: Provided that the report template has already been deployed to the Server,

1. From the Batch Versions application, find and select the Version
2. On the Version Prompting form, click on Form exit - Advanced
3. On Advanced Version Prompting, Turn On "Submit Version Specifications Only"
4. Click OK
5. On Version Prompting, click Submit

This will not run the UBE but will install the Version Specs to the Server. The submitted batch version record is displayed on
the Submitted Job Search screen as a type of 001 instead of UBE. The Queue that the batch version is submitted must be a
valid queue defined in the Server JDE.INI.

NOTE: Starting in EnterpriseOne 8.9 until 8.11SP1, any changes made to version specifications will require that the version
be submitted to server with the advanced execution option of Submit Version Specifications Only. This includes the first
time a new version is created even if no version overrides are specified. If the version specifications are not first submitted
to the enterprise server in this manner, the version will error when executed on the server.

Refer to Doc ID 626532.1 E1: RDA: How To Deploy Batch Version Changes for additional details on deploying Batch Version
changes.

Question 5: How is the check-in, check-out and advanced get of Batch Versions different from other objects in
OMW?

Answer 5: Due to the special considerations involved with batch versions, they are treated differently than other Object
Librarian objects and do not follow only the standard set of activity rules defined in Object Management Configuration
(P98230). Batch Versions work differently depending on whether the version is being checked-in or checked-out.

Check-out of Batch Version

When checking out a batch version the environment you are logged into supersedes the activity rules specified
in Object Management Configuration. The batch version will check-out from the path code for the environment
you are logged into. For example, if you are logged in a production environment, when performing a check-out
on a batch version, the specifications of the version are checked out of the PD Central Objects regardless of the
status of the project and activity rules associated with the check-out function for that project status. This is only
the case for batch versions, not other objects and only during check-out.

Advanced Get of Batch Version

Advanced Get function is disabled for objects which are non Object librarian objects with exception of Batch Versions
which have a specification storage extended to F983051 tables in form of records which is not stored locally but
centrally in version list datasource. Hence Batch Version are a different from other objects and the Batch version
advanced get would cause the specs to be changed locally but Processing Option values are changed for the whole
environment. All other object types will be affected only locally on machine when advanced get is performed.

Check-in of Batch Version

When you check-in a batch version, whether you check it in from Object Management Workbench or from Batch
Versions, the version will be checked into both the path code for the environment you are logged into as well as
the path code that is defined in the activity rules in Object Management Configuration for the check-in action for
your project status. If you are logged into a prototype environment and check-in a version, if the project that the
version belongs to is at a status of 21, the version will check into the prototype path code, based on the
environment you are logged into, as well as the development path code. The development path code is updated
because the standard transfer activity rules for a project status of 21 have the check-in action defined to check-
in the specifications from the local workstation to the development path code.

NOTE: When working with Batch Versions, both the Batch Versions application and Object Management Workbench
(OMW) function in the same manner and follow the same rules. If you check-out an object from within Batch Versions,

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 4/15
4/10/2021 Document 1487424.1

that version will display as checked-out in OMW and vice versa. Either application can be used to work with Batch
Versions.

Question 6: What is a Web Only Batch Version?

Answer 6: Web-Only Batch Versions was a workaround solution for releases Xe, 8.0 and 8.9 - 8.12 and is a feature that
allows users to add and copy versions on the web. The web versions allow for persistent data selection and sequencing to be
modified and deleted. With this feature Web Versions can be added, deleted or created by copying windows (fat-client)
versions. Beginning with the EnterpriseOne release 8.12 and Tools Release 8.98, full Batch Versions are now available on the
Web Client and Web-Only versions are no longer used.

For more information on Web Only Batch Versions, refer to Doc ID 626576.1 E1: RDA: Web-Only Batch Versions for Releases
Xe, ERP 8 and 8.9 - 8.12.

Question 7: With what release level are Full Batch Versions on the Web available

Answer 7: Full Batch Versions on the web are available with the releases EnterpriseOne 8.12 and later. For release
EnterpriseOne 8.12 only, the ESU associated with BUG 10975383 must be applied. Full Batch Versions on the Web also
requires Tools Release 8.98 or later.

For full details on Full Batch Versions on the Web, refer to Doc ID 959516.1.

Question 8: How do I retrofit a custom version with event rule overrides after an upgrade or ESU?

Answer 8: To retrofit a custom version with event rule overrides after an upgrade or ESU has been applied, un-check and
then recheck the Override Specs for Event Rules on each of the sections. This will bring the new event rules from the
Upgrade or ESU into the custom version. Then use the ER Compare tool to compare and retrofit the event rules against the
same version in Central Objects. Refer to Doc ID 637786.1 E1: RDA: How to Retrofit a Custom Version of a Standard UBE
Report after an Upgrade or ESU for more details.

Batch Versions Application

Question 1: Why does the Web Batch Versions application not have the option to display only "My Versions"?

Answer 1:

In both P98305 and P98305W, the default option is to display Available Versions. The option to display "My Versions" is not
available in the Web Batch Versions application (P98305W). This option is only available when you run Batch Version
application (P98305) on the fat client. Enhancement Bug 10963011 P98305W Option "My Versions" has been created to
request this option to be added in P98305W.

Workaround to display "My Versions": In QBE column(User) type in the E1 Login UserID, click Find

Question 2: Why do I receive an error on the "Find Allowed Actions" Business Function when selecting a version in
Batch Versions?

Answer 2: When trying to select a version in Batch Versions, if you receive the following errors:

Error in the jde.log:

3340/5556 Thu Oct 31 13:36:38 2002 jdeknobj.c1758

KNT00000182 - GetProcAddress failed from Lib. COBJLIB.dll for function FindAllowedActions on
server SERVER

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 5/15
4/10/2021 Document 1487424.1

Pop-up error on the screen:

The Business Function FindAllowedActions was not found in the Business Function Library COBJLIB on server
SERVER. Because of the unknown cache state on the server, you must exit this application all the way to the
menu. Please notify your OneWorld System Administrator to have the problem corrected before attempting to run
this Business Function again.

Verify the business function FindAllowedActions (B98223) has a correct OCM mapping. This should be mapped to run locally.
Since business functions typically default to the server, it may be necessary to create an explicit OCM mapping for the
environment and this business function. If this business function does not have a mapping to run locally and attempts to run
on the server, the error encountered above will occur. Create an OCM mapping to run this business function B98223 locally to
resolve the issue.

Question 3: User A creates a new batch version on own workstation. User B signs in to own workstation, version
created by User A is not an available version to execute. Why?

Answer 3: In order for a version to be available for another user to execute on another workstation, the version must be
checked-in. Also, if the version was created in a different environment such as DV and the user is attempting to access the
version in PY, the version must also be promoted through Object Management Workbench (OMW) to the environment that the
user is trying to access it .

Question 4: Why does version in F983051 with VRSAVAIL = N not display in Batch Application?

Answer 4: On entry in Batch Application (P98305) on the fat client, only Available versions are displayed that have been
checked in (i.e. VRSAVAIL = Y). To display version in F983051 with VRSAVAIL=N, go to Form exit > Display > All Versions.
This form exit is only available on the fat client.

Version Table F983051

Question 1: When creating a new Batch Version, where is the information stored?

Answer 1: Batch Version information is stored both in the F983051 Versions List Master Table as well as within the RDA
report specifications. Information including the Version ID, name, user, dates and processing option values are stored within
the F983051 Versions List Master Table.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 6/15
4/10/2021 Document 1487424.1

The report specifications unique to the version are stored within the RDASPEC and RDATEXT specification records. Just like
master report specifications, when you create a batch version on the Windows client, the specification records for that version
exist only on the workstation. To make the version available to other users, you must check in the version. When you check in
batch versions, the system copies the version specifications to the central objects data source (server) according to the path
code of the current environment. When you create batch versions on the web client, starting with Tools Release 8.98 and
later, you do not have to check them in because they are automatically updated to the central objects.

Question 2: How are the columns VRUSER, VRVED, VRUSR0, VRVCD in F983051 populated?

Answer 2: The columns are updated when the following actions are performed:

1. VRUSER is populated once only when the UBE version is first created using Add/Copy
2. VRVED is the date when the UBE version was last run either Locally or on the Server
3. VRUSR0 is the user who last modified the UBE version
4. VRVCD is the date when the UBE version was last modified.

VRUSR0 and VRVCD fields are updated together by any of the following actions on the UBE version :

Clicking OK on Processing Options even if the Processing Option values have not been changed
Check-In in Object Management Workbench (OMW)
Clicking OK when reviewing Version Detail even if no changes have been made
When PO values in F983051.VRPODATA are re-aligned due to a design change in the Processing Option template the
first time the PO values are accessed on web client. This is considered a bug, review Doc ID 2011262.1 E1: FDA: User
and Last Modified Columns in P983051 are Updated Without Any Changes to PO on Web Client.

Based on the results of when these columns are updated, there is no way to find out when the processing options of a UBE
Batch Version have been "truly" modified.

Question 3: On web client, after changing data selection in Batch Versions, User (VRUSR0) and VRVCD (Last
Modified date) are not updated in F983051.

Answer 3: This issue was reported in Bug 18011200 F983051 VRUSR0 VRVCD NOT UPDATED FROM ROW EXIT DATA
SELECTION IN BV P98305W WEB.

However, the reported issue is not considered a bug by development. The F983051 table is used for storing the value of the
processing options. It does not have a relation with data selection. The table is updated when the user checks-in something or
changes the processing option for the report. It is working as per design. Review Enhancement Bug 19424568 UPDATE
DATELASTCHANGED (VRVCD) COLUMN IN F983051 WHEN UBE IS MODIFIED FROM WEB.

Question 4: F983051 Date Last Executed (VRVED) in target environment is updated when promoting UBE version

Answer 4: Issue reported in Bug 24333206 VRVED OVERWRITTEN DURING UBE VERSION PROMOTION BETWEEN
ENVIRONMENTS and fixed in planned tools release 9.2.1.0. Review Doc ID 2164655.1 E1: OMW: F983051 Date Last Executed
(VRVED) in Target Environment is Updated After Promoting UBE Version

Version Security

Question 1: What does the Values in the Security Column mean in Batch Version Application?

Answer 1: The security column (F983051.VREXCL) in the Batch Version application allows you to restrict user access for a
report version.

The valid values of the security version level are:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 7/15
4/10/2021 Document 1487424.1

0 - No security. Anyone can design, change processing option values, change detail values, check in, check out, install,
transfer, copy, delete, or run the version. This is the default when adding a new version.

1 - Medium security. Only the "Last Modified By" user can design, change processing option values, change detail values,
check in, check out, or delete the version. Anyone can install, copy, transfer, or run the version. This is how the JDE Demo
versions are delivered.

2 - Medium to full security. Only the "Last Modified By" user can design, change processing option values, change detail
values, check in, check out, transfer, delete, or run the version. Anyone can install or copy the version.

3 - Full security. Only the "Last Modified By" user can design, change processing option values, change detail values, check
in, check out, install, transfer, copy, delete, or run the version.

The following security level is available in WorldSoftware only. It is not available in EnterpriseOne.

4 - Medium security-extended. Only the "Last Modified By" user can design, change processing option values (including
runtime processing options and data selection), change detail values, check in, check out, or delete the version. Anyone can
install, copy, transfer, or run the version. This is how the JDE Demo versions are delivered.

Question 2: How do I change the Security on a Batch Version

Answer 2: In order to change the security for a version with a security setting other than "0", you need to sign on with the
same User ID as the version is updated with in the User column. This is the last user that modified the version. If this is a
standard EnterpriseOne version, typically this is either the user id JDE or PSFT. Once you have signed-on with the appropriate
User ID value, you would then need to check-out the batch version. The security flag is updated within Version Detail,
however, the fields in Version Detail for a Batch Version cannot be changed until the version has been checked-out. Once you
check-out the version, then select the row exit for Version Detail. After the version has been checked-out, the fields within
Version Detail will be enabled and can be changed. Make the desired change and then check-in the Batch Version.

If it is not possible to sign-on to the EnterpriseOne software as the owner listed on the version, i.e. the owner of the version
has left the organization, the user profile has been deleted, etc., then the workaround is updating the security version level
column (VREXCL) in the F983051 Versions List table to 0. Once this has been updated to a 0, then you can sign-on to the
software and delete the version from your system. It is always recommended to make a backup of a table prior to performing
direct updates to that table.

Question 3: Can a User who created the Report Version be able to Change the Security Level without Checking it
Out?

Answer 3: Users cannot change their own batch version's security without first checking out the version in OMW or Batch
Application on the fat client.

Enhancement Request ENH 23024233 - USER TO BE ABLE TO CHANGE IT'S OWN VERSION SECURITY has been entered for
this request.

User which created the version can do a check-out, change the version security and then check-in the object. If you want any
user to change the version security, that version security needs to be 0 as described in Doc ID 886042.1 E1: OMW: Users
Cannot Check Out Batch Versions with Version Security Set to 1.

Question 4: When Version Security is set to '1' (Medium Security), when user Change Processing Options from
Prompt for Values on the Web Client, The "Last Modified By" User is Updated. How to Prevent this?

The version security level for a version is set to '1' (Medium Security) so that only the "Last Modified By" user can change
processing option values or delete the version. The problem is when users access processing options from the menu using the
Prompt for Values option, the users can still modify processing option values. The "Last Modified By" user is then updated.
How can I prevent that?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 8/15
4/10/2021 Document 1487424.1

Answer 4: In order for the Medium security to be applied correctly on the web client, ensure the following setting is in the
jas.ini [SECURITY] stanza (in Server Manager, Security -> Security Server Configuration) :

StrictVersionSecurity=1

The values are:

When set to '0', version security setting of '1' and '0' are treated the same way
When set to '1', security setting of '1' and '0' are treated differently.
When not present '0' and '1' security settings are treated the same (default)

If StrictVersionSecurity is set to 1 and a version has security setting Medium (1) and the user is not the last modified user for
the version, then the task will appear in the menu, but prompt for values will not appear in the context menu. In addition, if
the task is defined to launch with prompt for values the task in this scenario will instead launch with prompt for versions.

Question 5: Version Security is set to '1' (Medium) and StrictVersionSecurity is set to '1', the Menu Task Disappears
on the Fat Client but not on the Web Client. Why is there a difference?

On the web client, after applying the StrictVersionSecurity=1 setting in jas.ini [SECURITY] stanza, the versions' processing
option are secured as desired. However, on a fat Windows client the menu task disappears when the task is set to blind
execution. Why is this different on the fat Windows client?

Answer 5: The difference in the interpretation of the StrictVersionSecurity setting on the Web and Windows client is a known
issue reported on the following bugs: Bug 10801626 and Bug 10791498. These bugs are closed with a reason provided that a
code change is considered very risky for the whole EnterpriseOne security and Windows user interface.

The following is a summary of the behavior on the Windows fat client when StrictVersionSecurity=1 is in the jde.ini
[SECURITY] stanza :

1. Tasks with version security 2 will be hidden.

2. Tasks with version security 0 will act the same as for the version owner.
3. Tasks with version security 1 behave differently, as follows:

Task disappears from Solution Explorer when the task is set to blind execution.

Interactive Applications:
With "Prompt for Values", the system will display only Prompt for Versions in the context menu and will display a "User
is Not Authorized" message when user attempt to run the application other than with "Prompt for Versions" context
menu.

Batch Applications:
With "Prompt for Values", "Prompt for Data Selection", or "Prompt for Data Selection and Values", system will display
only "Prompt for Versions" in the context menu and will display a "User is Not Authorized" message when user attempt
to run the UBE other than with "Prompt for Versions" context menu.

The conclusion is that in order for the users to be able to run versions from the menu in the fat Windows client, set the task to
"Prompt for Versions" thus forcing the user to open an additional screen with Version Selection.

Question 6: How can security be defined to prevent user's from executing a version of a report?

Answer 6: Rather than using the version security setting on the version, define Application Security using Security Workbench
(P00950) at the version level. Application Security will allow you to define security on specific versions of a UBE Report to
secure the versions from being submitted. When defining Application Security at the version level, it will prevent the user
from executing the version from the menu, from a row or form exit, from a report interconnect or from Batch Versions. This is
the best way to define security at the version level.

For more information on defining Application Security for a version, refer to Doc ID 1367482.1 E1: SEC: Overview of
Application Security Defined Within The Security Workbench Application (P00950).

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 9/15
4/10/2021 Document 1487424.1

Question 7: Is there a way to Mass Update EnterpriseOne Batch Versions to Setup Security so that Users are Not
Allowed to Change or Delete Versions but Allowed to Create Versions for the Same UBE?

Is there a way to mass update EnterpriseOne batch versions, or to setup security such that users are are not allowed to make
changes or delete some batch versions while at the same time they are allowed to run and to create their own versions of the
same UBE?

Answer 7: The following are the methods you can use to setup security on Batch Versions:

Application security in Security Workbench, where you can specifically prevent users from running given UBE versions

Version security, set at the version detail level, where you can set individual versions to security levels 1, 2 or 3: (from
Interactive Help, on column "Security" in Batch Version Application)

0: No Security: This options means anyone can design, change processing option values, change detail values, check
in, check out, install, transfer, copy, delete or run the version. This is the default value when adding a version.

1: Medium Security: This option means that only the “Last Modified By” user can design, change processing option
values, check in, check out, or delete the version. Anyone can install, copy, transfer, or run the version.

2: Medium to Full Security: Only the “Last Modified By” user can design, change processing option values, check in,
check out, transfer, delete, or run the version. Anyone can install or copy the version.

3: Full Security: Only the “Last Modified By” user can design, change processing option values, change detail values,
check in, check out, install, transfer, copy, delete, or run the version.

Unfortunately there is not a way to update many versions at once. Theoretically you could set this security flag directly in table
F983051, column EXCL, however this is not recommended. We had enhancement Bug 10791453 CHANGING VER SEC THRU
AN APP, but it was closed by development as not planned.

What you can do is to identify all the batch applications (UBEs) users typically work with and then use either application
security (to completely deny access to) or version security (Full Security). This will need to be done one version at a time.

Question 8: How to secure Prompt for Values from the Task Menu, but still allow the Versions' Owners to Modify
Processing Options in Batch Version Application?

When the "Prompt for Values" security is set for an application at the whole application level in P00950-Security Workbench
application, the "Change" checkbox is automatically checked as well. Users cannot view and modify processing option values.
The problem is the user is not even allowed to change the processing option values for their own versions in Batch Version
application.

How can I secure Prompt for Values from the task menu, but still allow the versions' owners to be able to modify processing
options in the Batch Version application?

Answer 8: The Processing Option Security in Security Workbench was designed specifically to prevent the user/role from
displaying/changing the PO values anywhere in EnterpriseOne including the Batch Version application or in Object
Management Workbench (OMW) if the user goes to Version design. Any security type within the Security Workbench is
intended to act as a global security enforced in all the places within the system.

The desired outcome is not possible by applying Processing Options security on the whole application. Bug 10801658 is raised
to address this issue.

In the releases XE, ERP8.0 and 8.10 and higher (except for 8.9 release), processing option security can be applied to specific
versions instead of the whole application. See the related document Doc ID 1137370.1 E1: SEC: Frequently Asked Questions
on Processing Option and Data Selection Security.
Applying processing option security at the version level will allow for specific versions to be secured, but still allow for changing
processing option values on some versions.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 10/15
4/10/2021 Document 1487424.1

Version Overrides

Question 1: When in RDA at the Version level, why is the OK button disabled ?

Answer 1: When in Version Design, in order to make any change, you must select Override Version Specifications (right click
on the Section) and choose the part of the section you wish to override :

Section Layout
Section Data Selection
Section Event Rules
Section Database Output
Section Sort Sequence

When a Section is overridden at the Version level, any change made to the same section in the report template does not carry
over. Only those options that apply to the change being made should be checked as an override selection.

Question 2: Is it possible to produce a report of all versions that have version overrides?

Answer 2: There is not a field in the Versions List Table (F983051) that is updated for versions with version
overrides. Instead; the RDASPEC information is updated locally when the version override is created and then in Central
Objects when the version is checked-in.

Whenever a new version is created, if no overrides are performed, only one RDASPEC record is created with a Record Type of
'1'. If additional overrides are performed on the version, then additional RDASPEC records are created. For example, if the
user performs data selection overrides, then records are created in the RDASPEC for that report/version with record type 7
with the selection overrides for the version. If section layout overrides are performed, multiple records with record type 3 are
created in the RDASPECS. If data sequencing changes are made, then record type 6 records are created in the local RDASPEC
and if event rule overrides are performed, record type 16 records are created.

This same information can be seen in the Central Objects when the version has been checked in. If no overrides exist for the
version, there will be only one record in the F98761 RDASPEC central object table with the report name in RSOBNM, the
version name in RSVERS and a record type RSRCRDTP of '1'. However, for additional overrides, additional records are written
to the central object table with the corresponding record type for the type of override.

At runtime the system looks at the RDASPEC for the version and, depending on the records that exist for the version, it knows
what overrides have occurred on the version and pulls the appropriate override information. Any record types that do not
exist at the version level are then pulled from the report template RDASPEC information.

There is not a standard report or simple inquiry that can be performed to see all versions with overrides. The easiest way to
determine this information would be to look at the F98761 table in the Central Objects data source and find all records with a
specific version name that have record types other then just 1. This would indicate some type of override was performed on
the object. Depending on the value in the record type field (RSRCRDTP) you can determine what type of override exists for
the version. You can also use the Universal Table Browser (UTB) and add the setting of TAMMENUS=Show in the
[INTERACTIVE RUNTIME] section of the jde.ini to be able to view local RDASPEC information and central object information
from UTB.

Based on testing and review of the RDASPEC records, the record types are the following:

Definition
Record Type

1 Base Record

2 Sections (will have one type 2

record for each section of a
report)

3 Report objects (one record for

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 11/15
4/10/2021 Document 1487424.1

each report variable and

constant on the report

4 Column calculation defined on

tabular sections

5 Subsection join (defines join

information between sections)

6 Data Sequencing (will have one

record for each data item
included in data sequencing)

7 Data Selection (will have one

record for each data item
included in data selection)

8 Database output (one record

indicating destination for output
-file name)

9 Database output (one record

for each mapping in database
output)

10 Row on tabular section (one

record for each row)

11 Cell on tabular section (one

record for each cell)

13 Row calculation defined on

tabular section

16 Event rule overrides performed

at version level

17 Row on tabular section (record

for defined row criteria)

18 Cell on tabular section (record

for defined cell criteria)

19 Column data selection on

tabular section

20 Column and row overrides

(tabular section only)

Question 3: In Batch Versions, which Row Exit affects the Override Version Specifications?

Answer 3: To make changes available in the row exits, the version must first be checked out to the workstation.

Version Detail-Cover Page = Version Design, under Report Properties|Cover Page Options, check box for Cover Page
Clicking OK in Data Selection = Version Design, Section|Override Version Specifications, check box for Section Data
Selection
Clicking OK in Data Sequencing = Version Design, Section|Override Version Specifications, check box for Section Sort
Sequence.

Question 4: Sort Sequence has been overridden in my Level Break Header section, however why am I not able to
change level break items in Version Design?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 12/15
4/10/2021 Document 1487424.1

Answer 4: In order to make level break changes in Report Version design, besides overriding sort sequence in the Level
Break section,"Section Layout" and "Section Sort Sequence" must be overridden in the Parent Section . Go to the Parent
section of the level break header section and make sure you have selected to override the parent section "Section Layout" and
"Section Sort Sequence".

Question 5: Is there a way to identify versions that are out of sync between central objects and server specs?

Answer 5: There is no standard option available at this time identify versions that are out of sync between central objects
and server specs. Enhancement Bug 16700834 PROGRAM TO LIST THE VERSIONS WITH SPECS MISMATCH BETWEEN
SERVER AND CENTRAL requests this functionality.

Processing Options

Question 1: How do you print the Processing Options of a Batch Version without executing the report and printing
the cover page?

Answer 1:

From P98305 Batch Versions of a Windows client, highlight the Version and click on the Row exit (Print Options). This executes
the report R98306 PO Values and Text UBE and will print the Processing Option values for the report and version selected
within the Batch Versions application.

In App.Release 9.1 Bug 16417975 PRINT OPTIONS AND BV removed row exit 'Print Options' in P98305 (Fat Client) and
P98305W (Wev Client)

In App.Release 9.2 row exit "Print Processing Opt" is available to print processing options of selected batch version in P98305
and P98305W. Row exit calls UBE R98306. Apply ESU for Bug 28334833.

WORKAROUND: Submit UBE R98306 with data selection on specific batch version

To print Processing Options for ALL versions of a specific report, submit R98306 with data selection on BC Program ID
(F983051) = Report Name entered as a literal (i.e. R014052)

Question 2: Why are Runtime Processing Options saved, but Runtime Data Selection is not?

Answer 2: This functions as designed. Runtime Data Selection, Data Sequencing and Processing Options are saved with the
Server job when a report is submitted to the server, but the Processing Option values are also updated for the Version in the
Versions List table (F983051) when OK is clicked on the Processing Options prompting window. Enhancement BUG 12571251
RUNTIME PROCESSING OPTIONS SHOULD NOT BE SAVED opened

Question 3: How can I retrieve Processing Options Values of a Version on the report?

Answer 3: They are stored in the column VRPODATA in the Version List table F983051. This column is encoded in a binary
format and therefore, cannot be retrieved by using Event Rules functions. The following are ways to print the Processing
Option Values for Report Version:

1. Print the Cover Page for only Processing Options. For more detail, refer to Doc ID 642916.1 E1: RDA: How to Print the
Cover Page for a Report
2. Use the Version Reporting UBE (R01RS005) to generate a CSV file containing the processing options and data selection
values of interactive or batch versions. For more detail, refer to Doc ID 1311055.1 E1: SOLEXP: Using P01RS01
Configuration Utilities outside of Oracle Business Accelerator Methodology.

Question 4: Why is it not possible to change the prompting field under the version detail when copying a version?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 13/15
4/10/2021 Document 1487424.1

Answer 4: When copying a version, the prompting field under the version detail screen is automatically populated with a
blank, and it is grayed out. This field is related to Processing Options. If the report in question has processing options, the
prompting field automatically populate with a 2 but and it will be possible to change the value then. If the report does not
have any processing options then it will default to blank and will be disabled.

Question 5: UBE version does not retrieve processing options values when submitted from either fat client or from
server via scheduler/runube/runubexml/report interconnect

Answer 5: Review Doc ID 1946673.1 E1: RDA: After Adding PO Template To Existing Report, Processing Options Are Ignored
When Report Version Is Submitted From Fat Client Or From Server (RUNUBE, RUNUBEXML, Scheduler, Report Interconnect)

Version Detail

Question 1: How to print Version Detail text in Report?

There is no standard business function to retrieve version detail text (stored in rdatext) when running the ube on server. On
fat client in Batch Versions > Version Detail, the version detail text is retrieved using business function (bsfn) X983052 Version
List Local Lookup. Since X983052 is client-only bsfn, it can run on fat client only and cannot be called in UBE running on
server. The issue has been reported in Enhancement Bug 10932103 PRINT VERSION DETAIL TEXT ON REPORT.

Version Submission

Question 1: When submitting a Batch Version from the Web, why do I get the error "Versions with Client Platform
marked as "Client Only" cannot be submitted from the web"?

Answer 1: The error occurs when the report version is launched from a task on the EnterpriseOne Menu. The error occurs
because the Version is defined with a Client Platform of Client Only within the Version Detail OR the prompting option is set
incorrectly on the task OR the Version is blank or does not exist in F983051.

The error can be corrected by following these steps:

On the Windows client,

1. Go to Batch Versions of the report and highlight the version with the problem
2. Click on row exit Advanced and click on the row exit Check Out Version to check-out the Version.
3. Press Cancel to return to the Batch Versions form.
4. Click on the row exit Version Detail, in the Client Platform box, select the Blank code with description Both Web and
Client from the Visual Assist so that this UBE version can be submitted from both the Windows and Web client, click OK.
5. Click on the row exit Advanced, click on the row exit Erase Check Out, press Cancel. Since the "Client Platform" value is
stored in column VRVCC1 of F983051, it is not necessary to check in the version because no changes have been made
to the version RDA specs.

If the issue is with the Task, go into Task Revisions of the task, in the Executable tab, verify that the entry in the Version
contains a valid report version name that exists in table F983051. If the Version is blank with an option code other than
Prompt for Version, it is an invalid combination. Either change the option code to "Prompt for Version" with a blank entry in
the Version or select a version name from the Visual Assist of the Version and choose any option code except "Prompt for
Version". Refresh the EnterpriseOne Menu cache.

Enhancement Bug 20839197 opened to display a correct message when the task contains an invalid UBE version.

Question 2: How do I specify a Job Queue for a Batch Version?

Answer 2: To hard code the job queue for an existing version, go into Batch Versions and check-out the version. Then select
the version and choose the row exit for Version Detail. Within the Version Detail screen, you can specify the job queue where

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 14/15
4/10/2021 Document 1487424.1

the version should execute. After making the change, you need to check-in the version and deploy it in an update package to
the workstations and Enterprise Server. You can do a Submit Version Specifications to update the Enterprise Server
specifications as well.

For more details, refer to Doc ID 644305.1 E1: RDA: How to Specify a Job Queue for a Report Version.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the Design Tools & Output Technologies - JDE1 Community

To look at upcoming or archived Advisor Webcasts review Doc ID 1450327.1 Advisor Webcast JD Edwards EnterpriseOne
Schedule and Archived Recordings. If your topic is not currently scheduled please suggest it.

REFERENCES

NOTE:2011262.1 - E1: DSTR: User and Last Modified Columns in P983051/P98305W are Updated Without Any Change to
Processing Option (PO) on Web Client
NOTE:959516.1 - E1: RDA: Frequently Asked Questions on Full Batch Versions on the Web Client Beginning with Tools Release
8.98
NOTE:626576.1 - E1: RDA: Web-Only Batch Versions for Releases Xe, ERP 8 and 8.9 - 8.12
NOTE:626563.1 - E1: RDA: Frequently Asked Questions on the EnterpriseOne Report Design Aid
BUG:16700834 - PROGRAM TO LIST THE VERSIONS WITH SPECS MISMATCH BETWEEN SERVER AND CENTRAL
NOTE:1946673.1 - E1: RDA: After Adding PO Template To Existing Report, Processing Options Are Ignored When Report
Version Is Submitted From Fat Client Or From Server (RUNUBE, RUNUBEXML, Scheduler, Report Interconnect)
BUG:18277900 - F983051 RECORD IS UPDATED WITHOUT MAKING ANY CHANGES TO PROCESSING OPTION VALUES
BUG:24333206 - VRVED OVERWRITTEN DURING UBE VERSION PROMOTION BETWEEN ENVIRONMENTS
BUG:18011200 - F983051 VRUSR0 VRVCD NOT UPDATED FROM ROW EXIT DATA SELECTION IN BV P98305W WEB
NOTE:626532.1 - E1: UBE: How to Deploy Batch Version Changes
NOTE:1367482.1 - E1: SEC: Overview of Application Security Defined Within The Security Workbench Application (P00950).
NOTE:644305.1 - E1: RDA: How to Specify a Job Queue for a Report Version
BUG:19424568 - UPDATE DATELASTCHANGED COLUMN IN F983051 WHEN UBE IS MODIFIED FROM WEB
NOTE:637786.1 - E1: RDA: How to Retrofit a Custom Version of a Standard UBE Report after an Upgrade or ESU
NOTE:2164655.1 - E1: OMW: F983051 Date Last Executed (VRVED) in Target Environment is Updated After Promoting UBE
Version
NOTE:1450327.1 - Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xpnvx277i_675&id=1487424.1 15/15