Microsoft BizTalk Adapter for JD Edwards OneWorld provides access only to JD Edwards OneWorld business functions. Business function metadata is read using a business function interface and used to find a list of business functions and associated data structures. Metadata is strongly typed in all cases for all business function methods.
All business function methods have the same calling convention: three parameters that are system derived, and a pointer to a data structure. The following table shows how the business function data types are represented.
Special implementation of floating point numbers, including currency values.
xsd:string of 32
Byte
Single unsigned character.
xsd:string of 1
The following table contains the list of basic types in JD Edwards OneWorld and how they map to the Microsoft .NET Framework.
Basic types and how they map to the Microsoft .NET Framework
JD Edwards OneWorld XE
.NET Framework
char
String
int
Short
long
Short
String
String
JDEDATE
System.DateTime
MATH_NUMERIC
String
Byte
String
Note
If there is only one argument, and the return argument is void, the holder is replaced by the class, and the out portion becomes the return value. For example:
org.apache.axis.holders.DateHolder becomes a java.util.Date.
In JD Edwards OneWorld, some strings are character-limited. Any extra character causes an error. To see the limit of characters in the strings, you can use the Microsoft Adapter Wizard.
Extended data types (EDTs) and base enumerations (enums) are data types that are created and managed in the development environment. Base enums represent a list of literals, while EDTs are reusable data types that have a specific definition. The Application Object Tree (AOT) in finance and operations apps contains many existing EDTs and base enums that can be extended for use in your project, or you can create new data types. This module will focus on creating new data types.