Object Structure Creations; Required Object Determinations; Building The Object Structure - IBM BJ0NJML - Service And Asset Management Integration Manual

Object Structure Creations

Object Structure Creations

Required Object Determinations

Building the Object Structure

230
The integration framework provides predefined object structures for enterprise
services, publish channels, and invocation channels across multiple functional
areas. The functional areas include purchasing, work management, and
inventory. You can create an object structure, an enterprise service, and a publish
channel to support the exchange of data to and from the integration framework.
To determine what data to include in an object structure, you need some
knowledge of the system applications and objects. Begin by examining the data
model of an application to determine which objects, database tables, and views
contain the data that you must transfer to and from an external system.
You must find out which objects populate the system tables. Generally, a one-to-
one relationship exists between an object and a database table. However, in some
cases, multiple objects write data to a single table.
For example, assume that you must send a person object to and from the system,
but the system does not provide a predefined object structure with person data
(the system does provide a predefined purchase requisition object structure,
MXPERSON). After you use the person application, you determine that the data
that you need resides in the following tables: PERSON, PHONE, EMAIL, SMS.
The tables have the same name as the corresponding objects. Include the
PERSON, PHONE, EMAIL, and SMS objects in the object structure that you
create. The resulting enterprise service and publish channel contain the data fields
in those objects.
After you identify the necessary objects, create the object structure on the Object
Structure tab in the Object Structures application. Perform the following activities
to build an object structure that contains the person object.
This procedure creates a standard, hierarchical object structure. An object
structure can have the same object more than once in its definition. However, the
objects must have a valid parent-child relationship, and you cannot reference the
object more than once in the same hierarchical structure.
XML requires that the name of the object structure must begin with an alphabetic
character.
1
Enter PERSON as the primary (top-level) source object, then PHONE as the
child object. PERSON becomes the parent of PHONE.
2
Select the predefined object relationship that contains the appropriate
WHERE clause that links the PERSON and PHONE object. If multiple
relationships exist, select the WHERE clause that applies to the relationship
that you are creating.
Integration Guide