1 / 22

Approvals Management with TCA Hierarchy

Approvals Management with TCA Hierarchy. Ajoy A. Devadawson Oracle Corporation - Consulting . INTRODUCTION. About Oracle Consulting Profile of Project Organization Purpose of CRM - Service. 1. Enterprise Architecture. Consolidate Supply Chain applications

norm
Download Presentation

Approvals Management with TCA Hierarchy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Approvals Management with TCA Hierarchy Ajoy A. Devadawson Oracle Corporation - Consulting

  2. INTRODUCTION • About Oracle Consulting • Profile of Project Organization • Purpose of CRM - Service 1 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  3. Enterprise Architecture • Consolidate Supply Chain applications • Capacity Planning of organization, people and materials for deployment • Customer Units to generate Demand, going away from supply chain functions which reduce effectiveness • Focused on Field Service and Mobile Field Service • Requests for Supply, Maintenance and Service routed to back end modules • Service Request Charges functionality used to route to Order Management module • Tracking Customer Items through Install Base 2 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  4. Trading Community Architecture (TCA) • Data Structure for Customers, Partners, Vendors and their Employees • Customer Data Management(CDM) with Customers Online, Customer Data Librarian and Customer Data Hub • Organizations, People and Groups as Parties • Party Relationships (hierarchical & lateral) for Organizations and People • Relationships for Customer Items in Install Base • Third party integration with D&B • eLocations Spatial Data Integration ( in R12) 3 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  5. Marketing • Prospect Leads • Target Offers and Promotions • Customer Preferences & Behavior • Customer Profitability • Customer Survey Detail • Service • Customer Products • Service Requests • Service Contracts • Warranties • Entitlements • Interaction History • Fulfillment History • Sales • Opportunities • Prospect Profiles • Quotes • Proposals • Interaction History • Collateral History • Account Contacts • Customer • Customer Accounts • Customer Profiles • Demographic Data • Customer Financial Information • Party Relationships • Trading Partners • Accounts • Receivable • Invoices • Payments • Credits • Order • Management • Pricing • Orders • Returns (RMA) • Configure/BOM • Products • Product Configuration • Estimates • Customization (ECO) Integrated View of Customer Model through TCA 4 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  6. ORGANIZATION Relationships(Hierarchical and Lateral) 5 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  7. PERSON Relationship to Organization 6 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  8. User Management (UMX) Roles 7 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  9. Service Request – Field Service 8 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  10. Overview of AME • Highly extensible approval rules engine • Design approval rules without/minimal code • Integrated into eBusiness Suite • Dynamically regenerate approval list • Maintains history of approval status 9 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  11. How does AME work? Start - AME - Workflow Final Approver? Yes No Get Next Approver End (Approved) Yes Approve? Notify Next Approver No End (Rejected) 10 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  12. AME Architecture with TCA / ROLES 11 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  13. AME Administrator Dashboard 12 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  14. Components of AME • Attributes (e.g., UMX_ROLE) • Conditions (e.g., UMX_ROLE in (‘XXMC SR Approver A’) • Action Types (e.g., ‘Approval-group chain of Authority’, ‘HR Position’) • Action Handler ( program to build Approver Group based on Action Type) • Approver Groups ( list of approvers who have to approve notifications) • Rules ( link Conditions to Approver Groups) 13 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  15. AME Attribute 14 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  16. AME Condition 15 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  17. AME Action Type 16 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  18. AME Approver Group 17 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  19. Custom Action Handler The Custom Handler has the following features: • Builds Approver Groups of People attached to organizations in TCA • Recognizes Roles assigned to People • Callable from within AME module, thereby integrating TCA and UMX modules • Can climb TCA hierarchy to find next approver who could be in requestor’s org or in a higher level org • Can find another approver who is in another org attached to requestor’s org through a relationship 18 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  20. AME Rule 19 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  21. Useful References • Approvals Management Responsibilities and Setup in AME.B – Metalink Note # 434567.1 • FAQ on AME – Note # 431815.1 • AME Developer’s / Implementation Guide – Note # 289927.1 • TCA Documentation Resources, R12 – Note # 396778.1 • Oracle TCA Best Practices – Note # 269124.1 • Oracle Customer Data Hub Implementation Concepts and Strategies – Note # 312811.1 • Email: ajoy.devadawson@oracle.com 20 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

  22. Q & A 21 CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

More Related