4
Using J.D. Edwards OneWorld XE Datatypes

This chapter provides information on J.D. Edward One World XE datatypes. This chapter discusses the following topics:

Business Functions

The Oracle Application Server Integration Adapter for J.D. Edwards OneWorld XE provides access to J.D. Edwards OneWorld XE Business Functions. Metadata about Business Functions is read using a Business Function interface to find a list of Business Functions and associated data structures. Metadata is strongly typed in all cases for all Business Function methods.

Table 4-1 describes the list of basic types in J.D. Edwards and how they map to XML Schema types in Oracle Application Server ProcessConnect. The xsd prefix stands for the namespace http://www.w3.org/2001/XMLSchema.

Table 4-1 Business Function Datatypes

J.D. Edwards	Oracle Application Server ProcessConnect	Description
char	xsd:string of 1	Character string
int	xsd:short	A short integer
long	xsd:short	A long integer
MATH_NUMERIC	xsd:string of 32	J.D. Edwards special implementation of floating point numbers, including currency values
JDEDATE	xsd:date	J.D. Edwards special implementation of dates
BYTE	xsd:string of 1	A single unsigned character
BOOL	xsd:boolean	A boolean value
ID	xsd:string	An unsigned long integer
HWND	Not supported.	Not supported

Handling String Values

The following describes how to configure certain string arguments as right-justified (and left-padded). Oracle Application Server Integration Adapter for J.D. Edwards OneWorld XE exposes two kinds of string values through its interoperability layer:

char--A single character.
maximum length string--A null terminated string with a maximum length.

J.D. Edwards OneWorld XE uses Hungarian notation to name the arguments of these types in the Business Functions. For example, arguments of these types begin with:

For nearly all arguments of the sz type, maximum length string or char array, J.D. Edwards OneWorld XE expects a left-justified value. For a street address line, which is of max length 40, J.D. Edwards OneWorld XE expects:

"701 North Shoreline Blvd"

padded to length 40 with blanks. It is not necessary for you to enter the padding, because the Oracle Application Server Integration Adapter for J.D. Edwards OneWorld XE provides this for you. You only need to enter "701 North Shoreline Blvd" in your client code.

For some subset of values for this type, the dialog expects values that are right justified with padding on the left. For example, for Business Functions in the B4200310 source module, the argument szBusinessUnit is of length 12. This argument represents a plant, such as a production facility. For a plant number of 30, J.D. Edwards OneWorld XE expects a value of:

"          30"

The following values are not valid:

"30"
"30 "

To make it easier for you to submit these values, you can take advantage of an Oracle Application Server Integration Adapter for J.D. Edwards OneWorld XE feature. It is possible for you to enter a list of parameters so that they are automatically right-justified and padded on the left with blanks. In this way, the following value would be valid for the szBusinessUnit value:

"30"

This value is automatically formatted correctly if you take advantage of this feature. You must create a text file with entries describing these parameters. This file, if created, is called ORACLE_HOME/ip/adapters/config/JDE/jdearglist.txt.

If this file does not exist, or is empty, an informational message appears in the Oracle Application Server Integration Adapter for J.D. Edwards OneWorld XE log when you first load the adapter.

The following is an example of the format for entries in the jdearglist.txt file:

SourceModule.BusinessFunction.Argument

For example:

B4200310.F4211FSBeginDoc.szBusinessUnit

For a set of Business Functions belonging to the same business module, like-named arguments (of the same type) are shared across some or all of the Business Functions. You can use the asterisk (*) wildcard character instead of the Business Function name. For example:

B4200310.*.szBusinessUnit

You must copy jdearglist.txt manually when importing an Oracle Application Server ProcessConnect J.D. Edwards OneWorld XE business process to another machine.

Using the MATH_NUMERIC Type

The following describes the MATH_NUMERIC type and details:

How exponents are handled
The maximum number of digits
The maximum number of decimal digits

The MATH_NUMERIC type is a numeric string type. To use it, enter parameter values of the following format:

OptionalSign IntegerAndFractionalPart OptionalExponentPart

Where

OptionalSign can be + or -. + is the default.
IntegerAndFractionalPart is a maximum of 32 significant digits, not counting the decimal symbol. The decimal symbol is locale-specific to the J.D. Edwards OneWorld XE installation--typically a period (.) or a comma (,). The digits may be all integer, all fraction, or part integer and part fraction, but cannot exceed 32.
OptionalExponentPart is in turn made up of:
```
'e' OptionalSign ExponentDigits
```
where:
- OptionalSign can be + (plus) or - (minus). + (plus) is the default.
- ExponentDigits are at most two digits. You are permitted values between 63 and -63 excluding 0 (zero).

Examples of valid MATH_NUMERIC values include:

123.045
4089 (note there is no comma for thousands)
-9084
-230.75
0.010503
1.023e-10 which is equivalent to 0.0000000001023
0.097e5 or 0.097e+5 which is equivalent to 9700
1.0e-32 which is equivalent to 0.00000000000000000000000000000001

(This is valid because in this case the integral 0 * (zero) is ignored, 32 significant fractional digits)

Examples of invalid MATH_NUMERIC values include:

1034.00000000000000000000000000001023--Too many significant digits.
1.023e-64--The exponent is too small.
0.00317e64--The exponent is too large.

Any nonnumeric characters other than those appropriate for signs and decimal symbols result in an invalid value.

Exponents

Exponents are provided by the J.D. Edwards OneWorld XE MATH_NUMERIC as a convenience for entering values. However, most values return without exponents (with all 32 significant digits visible).

Invalid Values

Invalid values depend on the kind of value. A decimal fraction that is too small is interpreted as zero (all significant digits are lost).

An integer that has too many significant digits causes unexpected results. J.D. Edwards OneWorld XE does not always raise an error condition in this case.

An exponent that is too large or too small returns as an invalid value.

Precision for Operations

If an operation results in loss of precision, rounding occurs. For example:

1.9e-31 / 10.0 = 0.00000000000000000000000000000002
1.9e-31 / 100.0 = 0.00000000000000000000000000000000

In other cases, unpredictable results occur, as when a very large positive value is multiplied by another.

1.01e32 * 2.053e32 does not yield reliable results and does not raise an error.

For most foreseeable business scenarios, these ranges are not exceeded.

Currency

When a J.D. Edwards OneWorld XE Business Function expects a currency value, the Business Function has a separate parameter for a four-character currency code. It is not necessary to pass in this code unless you are using a currency other than the default configured for the J.D. Edwards OneWorld XE system.

4 Using J.D. Edwards OneWorld XE Datatypes