Key Columns; Duplicate Columns And Aliases; Column Name Lengths And Aliases; Format Of Interface Tables - IBM BJ0NJML - Service And Asset Management Integration Manual

Integration guide
Table of Contents

Advertisement

Format of Interface Tables

Key Columns

Duplicate Columns and Aliases

Column Name Lengths and Aliases

Interface Tables
The format of an interface table is the same as the format of the corresponding
object structure. The interface table includes the persistent and nonpersistent
columns that are included in the object structure. The interface table excludes the
columns that are excluded from the object structure.
The interface tables include additional columns that identify the sequence in
which the sending system writes, and the receiving system processes the records
in the various interface tables.
If the interface table represents a hierarchical object structure with parent-child
object relationships, the table does not include any part of the child object key
columns that are included in the parent object key columns.
For example, PERSONID is a key column in the PERSON, PHONE, EMAIL, and
SMS records. The PERSONID column appears only at the parent (PERSON) level
in the MXPERSON_IFACE interface table.
The XML representation of a hierarchical object structure contains duplicate
column names, but interface table and flat file representation do not. If an object
structure has duplicate non-key column names in both a parent object and a child
object, a duplicate column name error occurs when the interface table or a flat file
record is generated.
To resolve the duplicate column name problem, change the system alias for
duplicate column names. Every system database column can have an alias
alternate name. When an alias exists, the system uses the alias when interface
tables and flat files are generated. Change the alias to eliminate the duplicate
column name error.
Most columns do not have an alias, but some columns have aliases that support
the predefined enterprise services or publish channels.
A database column can have only one alias. Ensure that any alias that you assign
to a column is valid for every object structure that uses that column. If multiple
object structures use the object, a change to an alias affects every interface table
that is associated with those object structures.
The columns in the predefined object structures have system-assigned aliases.
Check for duplicates when you create a hierarchical object structure or when you
add an object to a predefined object structure.
The Add/Modify Alias dialog box shows the fields and aliases for the objects in a
selected object structure, and identifies any duplicate alias names with a check in
the duplicate column. If a duplicate alias exists, overwrite its value in the
ALIASNAME column. If a duplicate does not exist, you cannot change the alias.
Format of Interface Tables
99

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents