Oracle s Trading Community Architecture

Slide 1 Oracle s Trading Community Architecture Understanding Parties, Relationships, Sites, and Accounts 2003, FMT Systems Inc. All rights reserved. Slide 2 Introduction Faun dehenry G President and CEO of FMT Systems Inc. G Work during last 20 years involved founding and operating regional consulting organizations G Officer in Business Intelligence/Data Warehouse Special Interest Group G Recognized speaker and trainer on topics including Managing and Sustaining Virtual Teams, Best Practices for Virtual Organizations, Oracle s e-business Suite, and business intelligence Direct: 510.628.0376 e-mail: faun@fmtsystems.com Web: http://www.fmtsystems.com 2002-4, FMT Systems Inc. All rights reserved. 1

Slide 3 Agenda G Introduction G Learning objectives G Trading Community Architecture Relationship to Oracle ebusiness Suite Data model components Parties relationships G Trading Community Manager Responsibility Relationship Manager Customers entry and maintenance Merge G Summary G Questions and answers Slide 4 Learning Objectives At the conclusion of this presentation, you should be able to: Describe a party, party information, and party relationships Explain the difference between party attributes and customer attributes Discuss how the Trading Community Manager responsibility is used Explain the reasons for merging parties 2002-4, FMT Systems Inc. All rights reserved. 2

Slide 5 Trading Community Architecture Business Intelligence Financials Manufacturing Supply Chain Order Fulfillment Human Resources ecommerce Marketing Sales Contracts Service TCA Collaboration Common Application Architecture 9i, ias, Common Infrastructure and Services Slide 6 TCA Data Model Components : Represents any entity that can enter into business relationships with your organization Organization, Person, or Group Relationship: Location: Site: a binary relationship between two parties such as a partnership. For example, Rebecca Morgan is a specific person party and Acme Inc. is an organization party. Rebecca Morgan at Acme Inc. is also treated as a party with the type relationship. A street address Associates a party with a location, indicating that party's usage of the location Contact: Contact Point: A person related to an organization, this can be a relationship between an organization and a person as well as between two people. Your avenue of contacting a party, i.e., a phone number, e-mail address, or fax number. Customer Account: Customer Account Site: Customer Account Contacts: Represents a customer relationship between your organization and a party. A party site that you use in relation to a customer account, i.e., a bill-to or ship-to address A party contact that is used as a means of contacting the customer regarding his/her account 2002-4, FMT Systems Inc. All rights reserved. 3

Slide 7 Organization Person Group Slide 8 Information Acme Inc. Still exists independently attributes include Name Street address DUNS number External credit rating 2002-4, FMT Systems Inc. All rights reserved. 4

Slide 9 Customer Information and Relationship Acme Inc. Still exists independently attributes include Name Street address DUNS number External credit rating Description of your organization s selling relationship with Acme Inc. (account) Account attributes include Payment terms Shipping preferences Billing preferences Internal credit rating Credit limit Slide 10 Relationship Categories G Business relationships G Personal relationships G Organization to organization relationships G Person to organization relationships 2002-4, FMT Systems Inc. All rights reserved. 5

Slide 11 Business Relationships Acme San Diego Hierarchical Hierarchical Business Relationship Slide 12 Organization Relationships Relationship Acme San Diego Acme Inc. Zurich Parent Organization Hierarchical Competitive Relationship Circular Doerr Inc. London Competitor Organization Subsidiary Organization 2002-4, FMT Systems Inc. All rights reserved. 6

Slide 13 Person to Organization Relationship Relationship Acme San Diego Relationship Relationship Slide 14 Sample Scenario Your sales team returns from a trade show after having identified a prospect Acme Inc. This company has its corporate headquarters in New York with additional offices in Dallas and San Francisco. Your company has sales territories for the Northeast, the Southeast, the Midwest, and the West Coast. How many parties would you create for this prospect? 2002-4, FMT Systems Inc. All rights reserved. 7

Slide 15 Sample Scenario [Use this slide to describe how you would model the prospect.] Slide 16 Sample Scenario [Use this slide to describe how you would model the prospect.] 2002-4, FMT Systems Inc. All rights reserved. 8

Slide 17 Managing Relationships (process) Search for View Hierarchy Changes? Yes Select to View No Update relationships by moving parties Yes No Process end View Information? View Relationships Changes? Yes Edit Relationships No Slide 18 Trading Community Manager Responsibility G Relationship Manager G Customers entry and maintenance G Merge 2002-4, FMT Systems Inc. All rights reserved. 9

Slide 23 TCM View Relationships Slide 24 Customer Entry and Maintenance G Enter new customers G Manage your customer relationship and information relationships Third party data (D&B) 2002-4, FMT Systems Inc. All rights reserved. 12

Slide 33 Merge G Consolidate duplicate parties or party sites, i.e., merge Acme Corporation into Acme Corp. G Merge an acquired party into the acquiring party, i.e., merge Looney Tunes Network into Acme Corp. G Combine duplicate party sites for a party. Slide 34 Merge Merge Batch 2002-4, FMT Systems Inc. All rights reserved. 17

Slide 37 Summary During this presentation, we have: Described a party, party information, and party relationships Explained the difference between party attributes and customer attributes Discussed how the Trading Community Manager responsibility is used Explained the reasons for merging parties Slide 38 Questions and Answers 2002-4, FMT Systems Inc. All rights reserved. 19

Slide 39 Oracle s Trading Community Architecture Understanding Parties, Relationships, Sites, and Accounts faun@fmtsystems.com 510.628.0374 2003, FMT Systems Inc. All rights reserved. 2002-4, FMT Systems Inc. All rights reserved. 20