When you create an object structure, you define a group
of related objects to be part of an integration message that you exchange
with external applications. You can identify data fields for each
business object that determines the content of integration messages.
About this task
During the configuration, you can define the Java classes,
if needed, that process inbound and outbound messages. You also can
define an application that provides authorization rules for the integration
messages processed through the object structure. If the object structure
is intended for querying only and you do not want to use it for updating,
select the Query Only option. If the main
object in the object structure has a relationship to itself as a child
object, set the Self Reference option.
Procedure
- In the Object Structures application, click New
Object Structure.
- In the Object Structure field, specify
an object structure identifier.
- Optional: If you are using the object structure
for query operations, select the Query Only check
box.
- Optional: If you are using interface tables or flat files to exchange data between the integration framework and an external system, select the Support Flat File Structure check box.
- In the Consumed By field, specify the module that uses the object structure.
| Option |
Description |
|---|
| INTEGRATION |
Integration framework |
| MIGRATIONMGR |
Migration manager |
| REPORTING |
Reporting |
| OSLC |
OSLC |
- In the Source Objects table window, click New
Row.
- Enter values in the following fields to create a business
object hierarchy:
- Object
- Parent Object
- Reporting Description
- Relationship
- Object Order
- Click Save Object Structure.
What to do next
If the
Alias Conflict check box is selected on the object structure record, you can add or modify an alias to correct the duplicated field names in your source objects. You can also specify the persistent and nonpersistent fields that you want to exclude and include from the object structure.