Opportunity and Sales Stage have a M:1 relationship according to your business model. You want to show some data from the Sales Stage business component in your Opportunity business component. How would you do this?
-
By creating an implicit join between the Opportunity business component and the S_PARTY table
-
By using the intersection table S_OPTY_STG
-
By creating a link between Opportunity and Sales Stage business components
-
By creating a join from the Opportunity business component to the S_STG table
In a Many-to-One relationship where Opportunity is the 'many' side and Sales Stage is the 'one' side, the Opportunity table already contains a foreign key to the S_STG table. To show Sales Stage data in the Opportunity business component, you create an explicit join from Opportunity BC to the S_STG table using this existing FK relationship. This creates read-only join fields that display the related Sales Stage data. Links connect BCs at the BO level, intersection tables are for M:M relationships, and implicit joins to S_PARTY are unrelated to this scenario.
Because Opportunity-to-Sales-Stage is M:1 (many Opportunities can reference the same Sales Stage), you can pull display-only fields from Sales Stage directly into the Opportunity business component using a join, rather than needing a full Link (which is for 1:M relationships where the child BC has multiple rows per parent) or an intersection table (needed for M:M relationships). A join lets a single row in the child table (S_STG) be referenced by many Opportunity rows and exposes its columns as though they were native fields on the Opportunity BC. The 'implicit join... S_PARTY' option is irrelevant (S_PARTY is for party-model joins, unrelated to sales stages), and there's no M:M intersection table needed here since the relationship is M:1, not M:M.