How to Bypass certain DD Validation like Next Numbering using JDE API jdeDDValidation
Purpose of Document
A certain Data Dictionary (DD) Item may have associated properties and rules (Edit Rule, Next Numbering, Upper Case and so on). This document shows how to bypass a certain DD Specification which are associated with it using API jdeDDValidation.
jdeDDValidation API information
Information of this API, its syntax, parameters, return value etc. can be found in the jdeapis.chm file of your tools release. Look for the following category.
Application Programming Interface
Data Dictionary
jdeDDValidation
Business Scenario:
One of your business party sends you a certain data with address number populated. Based on given information, you want to validate inbound value but you do not want to waste a next number defined in your next number table (F0002).
Consideration:
Data Dictionary item specification for Address Number (Alias: AN8),
Edit Rule : IsColumnInAddressBook (B0100039 - F0101 Get Address Book Description Trigger)
Display Rule : CODE|Z
Next Number : (01|1)
Expectation:
Edit Rule is needed to determine whether input address number is defined or stored in F0101 - Address Book Master table
But you do not wish to call X0010 - X0010GetNextNumber (X0010 - Get Next Number)
Above flag can be used more than once in the following way : (e.g. DD_NO_VISUAL_ASSIST | DD_NO_NEXT_NUMBER)
For this example, &mnAddressHold is memory address for input LPDS
IDERRmnAddressNumber_3 is to set error message
It is important to bypass Next Numbering in validating any DD item with associated next numbering. Otherwise you may experience missing next number because X0010 can be called at the background to get/update next number defined in DD