Category Archives: TCA

Create Customer

Create a New Customer

Navigate to Order Management Super User Vision Operations responsibility and Customers –> Standard.

OTCCust001

Enter a new customer name in the Name field, and press Find.
If the customer name already exists, go back and enter a name that does not already exist.  Press the ‘Create’ button.

OTCCust002

Enter the Customer Information as shown:

OTCCust003

Enter the Account Information as shown:

OTCCust004

Enter Account Site Address:

OTCCust005

Enter Account Site Details:

OTCCust006

Save and Add details:

OTCCust007

Create a New Organization:

OTCCust008

Note: If we have any issue while create a New customer regarding the Amounts then we need to setup the Profile Amounts from Receivables Vision Operations Responsibility and navigate to Customers –> Profile Classes and Modify the Amounts for the Profile class given at Customer Creation. As we took it as DEFAULT we intent to modify the Amounts as shown below:

OTCCust009

Save the Profile class.

Once added we can Modify the Customer to add Ship to Site:

OTCCust010

Goto Site details:

OTCCust011

and Navigate to Business Purpose and Add a New Row as Ship To so the same address is used for both Shipping and Billing.

OTCCust012

Notice the ‘Open’ button in the above screenshot. This is where you can enter additional details specific to the business purpose. So, if the cursor is on the ‘Ship To’ row as seen here, clicking on Open will allow to enter information specific to the Ship To Location. This can be examined further in the Defaulting Rules section.

Make Both Purposes or Site Uses as Primary by Checking the Primary Flag and click on Apply:

OTCCust013

After this we can see the Site has both Ship To and Bill To as its Sites Uses and New record is inserted in HZ_CUST_SITE_USES_ALL.

OTCCust014

Related posts:

Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers, who belong to your commercial community, including organizations, locations, and the network of hierarchical relationships among them using the TCA registry.

TCA registry is the single source of trading community information for Oracle E-Business Suite applications which provide user interfaces, batch data entry functionality, and other features to view, create, and update Registry information.

TCA key entities:

Parties:  Parties are the entities of type person/organization that enter into a business relationship

Party Sites: Addresses of the parties

Customers: Parties with whom you have a selling relationship

Customer Accounts: The business relationships between you and your customers

Customer Account Sites: Address of the party used in the case of customer accounts

Locations: Geo-spatial points, usually defined by an address

Contacts: People who have a contact or employment relationship with an organization or person

Contact Points: Means of contact, for example, phone and e-mail address

Process Flow:

This diagram shows the process flow for managing, searching, creating, and updating customer information.

R12 Trading Community Architecture:

Includes following new trading entities:

  • Bank and Bank Branches
  • Customers
  • Suppliers

TCA-Bank and Bank Branches:

The TCA tables used by Cash Management for modeling Banks and Bank Branches are listed below:

Three key CE tables now as:

    • CE_BANK_ACCOUNTS for bank accounts
    • CE_BANK_ACCT_USES_ALL for account uses by Operating Units & Legal Entities
    • CE_GL_ACCOUNTS_CCID for bank account use accounting data

TCA-Customers:

The word “Customer” is the combination of both the “Party layer” and the “Account layer”.

  • Party layer exists independent of any selling or buying relationship.
  • Customer Account layer exists in the context of a Party and only when a selling      relationship exists.
  • The Party Layer captures intrinsic truths about a person or organization.
  • The Account Layer captures the details describing the Party’s financial relationship with the implementing organization.
  • The Account Layer cannot exist without the Party Layer.

TCA-Suppliers:

Following are the three new AP tables’ technical details for R12 Supplier in TCA. They have the links to TCA tables which are listed below.

  • AP_SUPPLIERS
  1. HZ_PARTIES
  2. HZ_PERSON_PROFILES
  3. HZ_PARTY_USAGE_ASSIGNMENTS
  4. HZ_PARTY_RELATIONSHIPS
  • AP_SUPPLIER_SITES_ALL
  1. HZ_LOCATIONS
  2. HZ_LOCATION_PROFILE
  3. HZ_PARTY_SITES
  4. HZ_PARTY_SITE_USES
  • AP_SUPPLIER_CONTACTS
  1.  HZ_PARTIES
  2.   HZ_RELATIONSHIPS
  3.   HZ_PARTY_SITES
  4.   HZ_ORG_CONTACTS
  5.   HZ_CONTACT_POINTS

TCA ER-Diagram:

TCA1

 

reference: www.docs.oracle.com

Related posts: