1 / 28

TCA Customer Components and Best Practices

TCA Customer Components and Best Practices. October 16 , 2012. Contents. TCA Components. Party Layer Components. A Party is an entity that can enter into a business relationship (i.e. person or organization. A Party Relationship is the connection between two entities.

yepa
Download Presentation

TCA Customer Components and Best Practices

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. TCA Customer Components and Best Practices October 16, 2012

  2. Contents

  3. TCA Components

  4. Party Layer Components • A Party is an entity that can enter into a business relationship (i.e. person or organization. • A Party Relationship is the connection between two entities. • For example, John Doe is a Person, Business World is an Organization, and Jim can be a Contact of Business World • In addition, the Business World Handhelds division may be modeled as a Party, whereby Business World HQ is the Parent Company • A Party Relationship can be created to show that Business World Handhelds is a Division of Business World HQ • A Location is an address. Since the Location is physically separated from the Party, a Party Site is created to connect the two to show that a particular Location is valid for a Party. • The PartySite is an intersection between a Party and a Location. • A PartySiteUse denotes how a particular Party Site is to be used throughout the context of E-Business flows. For example, bill to address, ship to address, marketing address, etc.

  5. Account Layer Components • An Account represents the implementing organization’s financial relationship with a Party. • It is the financial intersection touch point between the implementing organization and the party • An Account cannot exist without a Party, nor can any of the Account’s attributes • An AccountSite is a Party Site that is used within the context of an Account. • Create a Party with a Location, and by doing so, a Party Site is created • When a financial relationship is established, this Party Site can be pulled down to the Account level to be used as an Account Site • An AccountSiteUse is given to an Account Site to denote how this particular site will be used throughout the context of Account level transactions. • AccountRelationship are created between Accounts to allow for the sharing of billing, shipping, and pricing information. • One-way or bi-directional • Not used to model a corporate hierarchy, simply 1:1 relationships

  6. Visual Representations of Different Components

  7. TCA - Party In the graphic shown, there are three Parties which can be persons or organizations.

  8. TCA - Locations Locations contain the address of the parties. A party can have one or more address.

  9. TCA – Party Sites When the locations are connected to the party, a Party Site is created. Remember the Party Site is the intersection between the Party and a Location.

  10. TCA – Party Site Usage Party Sites can have one or more Party Site usage. In other words, how do you relate to the customer with that address.

  11. TCA – Party Relationship Party Relationship can be created between the three entities to denote that two of the parties are actually divisions of a parent party.

  12. TCA - Accounts Once a financial arrangement is established with each party, an Account is created.

  13. TCA – Account Sites The Party Site can be pulled into the Account level for use as an Account Site. Note that the location is exactly the same A new location is not being created at the account level Simply using a Party Site in the context of an Account

  14. TCA – Account Site Usage Then assign Account Site usages to each Account Site to denote how the address is used at the account level.

  15. TCA – Account Relationship Now we can create Account Relationships between each account so that one party can be billed and shipped to another party, or, so that one of the division parties can place an order and take advantage of the pricing agreement established at the parent party level.

  16. TCA – Stored Data Elements The following are examples of data elements stored at each level: At the party level, attributes such as the name of the person or organization; taxpayer id or SSN, DUNS number, and year established are all stored At the Account layer, elements such as payment terms, and billing and shipping preferences are stored

  17. Party vs. Account

  18. Parties vs. Accounts Which one is the customer? • Parties represent persons or organizations that may, or may not have purchased from the implementing organization. • Accounts should be created once a party makes a purchase or establishes a financial agreement. • The Answer: The combination of a party and its account(s) is considered a customer.

  19. TCA Customer Modeling

  20. How is TCA Implemented? • The Trading Community Architecture is not a module that is implemented, but an underlying foundation. • Customers and prospects are modeled within TCA. • Modeling is flexible. Customers and prospects can be modeled in a variety of ways: • AR Model • TCA Best Practices model • It is important to note that regardless of how prospects and customers are modeled in TCA, the data still resides within the HZ schema.

  21. TCA Best Practices Model

  22. Best Practices - Party • A Party is a real thing with which you can do business. • A Party Site identifies that a particular location is valid for that party. It is not intended to represent a distinct business entity with which you can do business. • Party Sites should not be used to model an organizational structure • The attributes of a Party are universal: • They are independent of who obtained the information • DUNS, CEO, addresses, SIC code, date established

  23. Best Practices - Account • A real thing (e.g. person/organization) cannot be an Account • An account should have an Account Description to allow users to select which account to work with when multiple Accounts exist for one party (i.e. Business World is both a customer and a partner) • Customer - Business World places an order via their direct account and takes ownership of goods for their facilities. • Partner - Business World purchases equipment via their channel account, which is used for cases where Business World places the order, but the goods are being sent to a 3rd party for use and ownership. • The relationships established at the Account level do not mirror those at the Party level. • Accounts should typically have only one active bill-to site. If an additional bill-to is required, it often means that a new account or new party maybe required for that party (exception: an account has two lockboxes; a new account is not needed).

  24. TCA Best Practices Model Overview • Today, several implementing organizations are not realizing the full benefits or Trading Community Architecture. • Organizations that follow the TCA Best Practices model are able to better sell to, market to, and service their customers. • Organizations that follow the AR Model lose visibility to different business entities within their customer model. • The AR Model is simply a vertical model that is not able to differentiate between an address and an entity, subdivisions, branches, etc. • The TCA Best Practice model allows organizations to generate necessary reporting and obtain better information on their customers to make more informed business decisions.

  25. Multi-Org Customer Structure

  26. Multi-Org Functionality • Multi-Org is a component of E-Business Suite that: • Provides secure access to different organizations of the enterprise • Supports multiple organizations of the enterprise structure in a single database • The organization structure is the relationship of a Set of Books, Legal Entity, Operating Unit, and Inventory Organization that defines a Financial Organization Hierarchy. • The Operating Unit is the primary organization unit through which you secure transaction data, but also create, process, and report on financial applications data. • An Operating Unit can be used to model an autonomous business unit that performs one or more business activities and creates transactions with financial impact. So how does this affect the Trading Community Architecture?

  27. TCA & Multi-Org • When creating an Account Site, the user must specify the Operating Unit. • One party site can be used for multiple Operating Units which results in several Account Sites with the same Location.

  28. TCA & Multi-Org • A Location (address) may be displayed for a customer multiple times, but each location is assigned a different operating unit • The Party Site number is the same, but it has been granted access across multiple organizations.

More Related