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.
As indicated in the description of the Sales—Update Customer business process in Chapter 3, Case Study Introduction, AHA wants to store the date, employee, product, and the customer response of each product offering to a customer. The AHA business analyst team has identified the preconfigured S_ORG_EXT_XM table as the best place to store this data.
The analyst...
