Oracle Siebel CRM 8 Developer's Handbook

Creating a child business component on a 1:M extension table

When business requirements dictate the creation of new child entities, developers can rely on 1:M extension tables in order to avoid modifications of the physical schema. 1:M extension tables have been described in the previous chapter. In the following case study example, we will practice the creation of a new child business component based on a 1:M extension table. Later in this chapter, we will learn how to create a new link and insert the new business component in an existing business object using the new link.

Case study example: Creating a custom child business component

As indicated in the description of the Sales—Update Customer business process in Chapter 3, Case Study Introduction ...