Business object naming, WebSphere Adapter for Oracle E-Business Suite

IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Oracle E-Business Suite > Reference > Business object information
Naming conventions

When the external service wizard generates a business object, it provides a name for the business object that reflects the naming convention for the adapter. Typically, the business object name indicates the structure of the business object.

When the external service wizard creates names for a business object, it replaces any special character except the underscore (_) in the business object name with U followed by its Unicode number.
For example, the business object name for the Order_Item table in the database is Order_Item. The business object name for the Shipping-Address table is ShippingU45Address.
Business object names have no semantic value to the adapter or the database; that is, they derive no information nor meaning from the business object name. If one name is replaced by another, the adapter behavior remains the same.
Business object names can carry database-specific metadata. A name can use a string like Oracle or % AppName% as a prefix to help distinguish between two types of business objects: application-specific and generic. The remainder of the name can describe the table or stored procedure that the business object represents.
For example, if the business object definition is generated for the Employee Table in a database application, such as Human Resources (HR), then the respective business object name is HREmployee.
For business objects that do not correspond to database objects, such as business objects for database queries, if you give the business object the same name as a table or stored procedure business object, a different number is appended at the end of each name to differentiate them and avoid overwriting.
Globalized characters are supported in any business object name.
You can rename business objects by using the refactoring functionality in IBM Integration Designer. For more details, refer to the IBM Integration Designer documentation.
The following table describes the naming conventions that the wizard uses for the business object.

Business object naming conventions
Element Naming convention
Business graph
The business graph that contains the parent business object is named for the contained business object, followed by the string "BG"; for example, the business graph that contains the SalesCustomer business object is named SalesCustomerBG.
Business objects for:

Tables
Views
Stored procedures
Stored functions
Synonyms and nicknames

For those business objects that are based on tables, views, stored procedures, and synonyms and nicknames, the external service wizard generates the name of the business object in the form of Prefix + SchemaName + ObjectName, where:

Prefix is the value as specified in the external service connection property named Prefix. A prefix is not required, and if not specified, no prefix is added to the business object name.
SchemaName is the name of the schema to which the object belongs.
ObjectName is the name of the table, view, stored procedure, stored function, or synonym/nickname. A number is appended if necessary to differentiate the business object from another business object with the same name.

For example, using the prefix Campaign12 for the Customer table in the Sales schema, the business object name is Campaign12SalesCustomer.
Query business objects
For query business objects, the external service wizard generates the name of the business object in the form of Prefix + QueryBOName, where:

Prefix is the prefix you specify in the wizard. A prefix is not required, and if not specified, no prefix is added to the business object name.
QueryBOName is the value you specified when you configured the business object in the wizard. A number is appended if necessary to differentiate the business object from another business object with the same name.

Business object information

Related tasks:

Setting connection properties for the external service wizard

Element	Naming convention
Business graph	The business graph that contains the parent business object is named for the contained business object, followed by the string "BG"; for example, the business graph that contains the SalesCustomer business object is named SalesCustomerBG.
Business objects for: Tables Views Stored procedures Stored functions Synonyms and nicknames	For those business objects that are based on tables, views, stored procedures, and synonyms and nicknames, the external service wizard generates the name of the business object in the form of Prefix + SchemaName + ObjectName, where: Prefix is the value as specified in the external service connection property named Prefix. A prefix is not required, and if not specified, no prefix is added to the business object name. SchemaName is the name of the schema to which the object belongs. ObjectName is the name of the table, view, stored procedure, stored function, or synonym/nickname. A number is appended if necessary to differentiate the business object from another business object with the same name. For example, using the prefix Campaign12 for the Customer table in the Sales schema, the business object name is Campaign12SalesCustomer.
Query business objects	For query business objects, the external service wizard generates the name of the business object in the form of Prefix + QueryBOName, where: Prefix is the prefix you specify in the wizard. A prefix is not required, and if not specified, no prefix is added to the business object name. QueryBOName is the value you specified when you configured the business object in the wizard. A number is appended if necessary to differentiate the business object from another business object with the same name.