Mandatory Data Selection

Have you ever had data corruptions or performance issues, due to Batch Versions submitted with incorrect Data Selections?

If you answered yes, then this solution is for you.

MANDATORY_DS is a set of native JDE Objects, controlling the quality of your Batch Jobs' Data Selections, accordingly to your custom rules.

This new enhanced edition adds a few new control options, so that now, you will be able to stop Batch Jobs in any of the following specific cases of Data Selection:

if there is no selection set on a specific Table/Column;
if there are any "OR" comparisons in the entire DS block;
if any specified Table/Column is compared with too many values;
if any DS row contains a comparison with a NULL value.

All these conditions are configured and checked per UBE|VER. If the custom configuration table is mapped to the System DSN, then the same rules apply in all Environments, if it's mapped to the Default Business Data DSN's in each Environment, then the configurations are different per Environment.

This software contains the following native JDE Objects:

A custom table to store your Mandatory Data Selection definitions, plus the "Active Y/N" flag to easily turn the definitions On and Off.
A custom Interactive Program to enter / maintain these definitions.
Custom code to check, if the Job was submitted with the Data Selections that fully satisfy the list of your custom Mandatory Data Selections - the code takes into account the effective DS at run-time, even if the DS were manually overwritten, when the Version was submitted.
A few auxilliary Objects to support this software, including DSTR's, a BSVW, BSFN's, etc.
No modifications to any existing programs or versions - the code that controls this functionality is entirely external to the UBE's.

Scenario:

1. You postulate, that when some XJDE0001 version of some RXXXXXXX program is submitted, it must have Data Selection defined on an XXX field of some FYYYY table (eg.: AT1 field of F0101 table).

2. To enforce this, you define a Mandatory Data Selection which would look like:

UBE Name:	Version Name:	Table Name:	Column DD Alias:	Active (Y/N):
RXXXXXXX	XJDE0001	FYYYY	XXX	Y

3. When this Version is submitted with any Data Selection, which does not include a row for the YYY field of the FXXXX table, then the code in this software solution fires and the Job will fail before it is executed - a few messages to that effect will also be generated to provide meaningful feedback to the user. Otherwise, if there was some DS defined for this field, it will run as always.

The error will be reported in two ways:

A JDE.LOG error on the Server, which you can access through the View Logs exit of the Submitted Reports program, like this:

2576/2468 Thu Nov 20 12:37:49 2003 b59mndds.c99
ERROR: This Mandatory DS was NOT present. The Job will be terminated with an error.

In the Work Center, in the Submitted Jobs queue, there will be a message, with the UBE name as the name, stating the reason, like this:

Multiple Mandatory Data Selections can be defined for the same Version.

It can be used with any OW Release from XE to E811 SP1 . If you prefer, you can think of it as a significant piece of custom development work, available for only a fraction of the price it would take you to develop it in-house, already tested and packaged neatly in a file and ready to be installed in minutes and configured in hours or days.

Because all the coding was done in OneWorld/EnterpriseOne® and, of course, you are getting all the source code as well, this code can be modified, if necessary, to suit your specific requirements, or used as a template for more complex development.

Most OneWorld/EnterpriseOne® sites need this functionality.

There is no expensive consulting necessary on top of this. You can easily install it yourself. Just follow the instructions included in the Package. No user training is required either. Estimated time it takes to install this Package is 5 minutes, plus some additional time to build and deploy an Update Package with a few Objects.