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

<Insert Picture Here>

Approvals Management with TCA HierarchyAjoy A. DevadawsonOracle Corporation - Consulting

CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract

INTRODUCTION

•About Oracle Consulting •Profile of Project Organization

•Purpose of CRM - Service

1


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


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


Integrated View of Customer Model through TCA

Customer• Customer Accounts• Customer Profiles• Demographic Data• Customer Financial Information• Party Relationships • Trading Partners

Marketing• Prospect Leads

• Target Offers and Promotions

• Customer Preferences & Behavior

• Customer Profitability

• Customer Survey Detail

Sales

• Opportunities

• Prospect Profiles

• Quotes

• Proposals

• Interaction History

• Collateral History

• Account Contacts

Service

• Customer Products

• Service Requests

• Service Contracts

• Warranties

• Entitlements

• Interaction History

• Fulfillment History

OrderManagement

• Pricing• Orders• Returns (RMA)

AccountsReceivable

• Invoices• Payments• Credits

Configure/BOM• Products• Product Configuration• Estimates• Customization (ECO)

4


ORGANIZATION Relationships(Hierarchical and Lateral)

5


PERSON Relationship to Organization

6


User Management (UMX) Roles

7


Service Request – Field Service

8


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


How does AME work?

Notify Next Approver

Get Next Approver End (Approved)

End (Rejected)

Start

Approve?

FinalApprover?

- AME

- Workflow

Yes

No

No

Yes

10


AME Architecture with TCA / ROLES

TCA---------

OrganizationsPersonsRelationships

ROLES------------

Assign Roles to ApproversEligibility check during

AME runtime

AME---------

Dynamically build Approver GroupsLinking Conditions and Approver Groups in a AME RuleCustom Action Handler

WORKFLOW

11


AME Administrator Dashboard

12


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


AME Attribute

14


AME Condition

15


AME Action Type

16


AME Approver Group

17


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


AME Rule

19


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: [email protected]

20


Q & A

21

Documents

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