Business objects for PeopleSoft Enterprise
To send data or obtain data from PeopleSoft Enterprise, the adapter uses business objects. A business object is a structure that consists of data, the action to be performed on the data, and additional instructions, if any, for processing the data. The data can represent either a business entity, such as an invoice or an employee record, or unstructured text.
How business objects are created
You create business objects by using the Adapter Connection wizard. The wizard connects to the application, discovers data structures in the application, and generates business objects to represent them. It also generates other resources that are needed by the adapter.
Business object structure
The adapter supports business objects that are hierarchically structured. The top-level business object must have a one-to-one correspondence with the PeopleSoft component interface, and collections that occur in the top-level object are children of it. Information about the processed object is stored in the application-specific information for the object and each of its attributes.
The following table describes the attributes that form a business object.
| Attribute property | Description |
|---|---|
| Name | Indicates the name of the business object attribute. |
| Type | Indicates the type of the Business Object attribute.
The adapter uses character mapping between PeopleSoft component property
types and the generated business object attribute types. PeopleSoft
component property types map to generated attribute types in the following
manner: CHAR maps to attribute type String
NUMBER maps to attribute type BigDecimal
LONG maps to attribute type Long
SIGN maps to attribute type BigDecimal
DATE maps to attribute type Date
TIME maps to attribute type Time
DTTM maps to attribute type DateTime
|
| Key | Child business objects have their own keys that have the primary key application-specific information. They also inherit keys from their parent business object. |
| Cardinality | Single cardinality for simple attributes; multiple cardinality for container attributes. |