Comprehensive site documentation is not a luxury, but a necessity. Wrong Data Selections are causing many issues and need to be documented and periodically re-viewed.

This intelligently self-configuring software solution provides a very easy way to document Batch Versions' Data Selections (per Section - if multiple Sections have DS overrides, it reports them all), as well as to find any orphaned and/or corrupt specs it finds in the system (hundreds of which are delivered with the default OneWorld/EnterpriseOne software installation):

Extremely easy to use, this software offers a one-button interface with no configuration. It's immediately operational upon an installation. The users will not need to be trained to use this solution. All necessary configuration is read directly from OneWorld/EnterpriseOne.

The easy-to-read color-coded output of this tool is saved in XLS format. A sample report:

The tool identifies any corrupt Data Selections - referring to non-existent Data Structures, missing RI elements, RV's, etc.:

as an example, which would appear in OW as shown below (this is a standard "vanilla" object, out of the box in E810):

It also finds any orphaned data selection records (and there are lots of them in every system). Conceivably, such orphaned Data Selection records could affect the job selection, if EnterpriseOne decides to use them. Making the specs tables smaller will also reduce the package build time and improve the run-time performance of the UBE's. To clean up such orphaned records, it's enough to open the Version in RDA and save it.

And finally, it also finds all Data Selections defined as Section Overrides in Versions, which would not be visible to end-users at all, often creating a great deal of confusion, as to why certain data is never displayed.

This tool is lightning-fast: it only takes a few minutes to report Data Selections for all versions in the system. It has no hardware dependencies, as it does not access any data directly.

Since v. 4.1, DSC takes into account the data selections defined for sections in the versions' templates.

Another tool which may also help to enhace report documentation is Update Queue Names In Versions - it offers the power to bulk-update Batch Versions to print their Data Selection Criteria on the Cover Page every time they run - this way you can collect actual Data Selections used to submit jobs.

A run-time Data Selection lookup software solution is available here. It can be used to see the DS actually used on the Server, as an example.

A Processing Option documentation software counterpart is available here.