Configuring an object structure

You can create new object structures and during that process you can generate schema files, include or exclude fields, and resolve alias conflicts. You can also specify inbound setting restrictions, set advanced configuration properties, and configure application authorization.

Creating object structures
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.
Configuring an alternate key
To configure an alternate key, create a unique index in the Database Configuration application and reference this index as the alternate key for an object structure or for a specific object.
Including nonpersistent fields in the object structure
Business objects use nonpersistent fields for calculations or for temporary storage of data. By default, the nonpersistent fields on a business object are excluded from the object structure definition. You can include data from nonpersistent fields in integration messages.
Excluding persistent fields from the object structure
Business objects use persistent fields to write processing data to a database. By default, persistent fields are included in the object structure definition. You can exclude persistent field data that you do not want to map to an integration message.
Resolving alias conflicts
An object structure that contains multiple objects and supports flat files or interface tables, cannot have duplicate field names for any of the fields in its objects. You must resolve any field name (alias) conflicts before you can generate interface tables and flat file records.
Setting restrictions on fields in inbound messages
Standard integration processing sets the values in object fields with the corresponding values from an inbound message. You can set a field as restricted if you do not want the value to be updated by inbound messages, for example for a field with an internal ID or where a processing class provides the logic to set the field.
Setting advanced configurations for an object structure
You can set advanced configurations for an object structure to change some default processing behavior for integration messages. Advanced configurations include configuring how key fields are processed for child objects, whether an event on a child object activates a corresponding event on the parent object, and whether auto-generated data is deleted.

Feedback