02-R12 TCA

Copyright © 2006, Oracle. All rights reserved.

Release 12 Field Readiness Workshop

TCA

Trading Community Architecture

Copyright © 2006, Oracle. All rights reserved.2

Purpose:This document provides an overview of features and enhancements included in Release 12. It is intended solely to help you assess the business benefits of upgrading to Release 12.

Disclaimer:This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.


Data Management with TCALeveraging centralized data model

Oracle Fusion MiddlewareOracle Fusion Middleware



ERPERP CRMCRM 3rd Party3rd Party

PayablePayabless

PayablePayablessPurchasiPurchasi

ngngPurchasiPurchasi

ngng

Global Global TaxTax

PaymentPaymentss

Suppliers

Geographies Party Informati

on

Cash Cash ManagemeManageme

ntntBanks and

Branches


Data Management with TCA

TCA Party base for• Legal Entities and Establishments• Suppliers, Customers, Students• Banks and Bank Branches• Intercompany Parties

TCA Relationship Model• Parent Suppliers for subsidiaries or franchises• Intercompany Parties mapped to Legal Entities• Inter/Intracompany trading partners (customers/suppliers)

TCA Geography Model• Simple eBTax rules

– Group countries– Compound rates for state, county, city


Note 417511.1

Projects Uptake of the TCA Architecture in Release 12

This note is intended for anyone who must upgrade queries or customizations from 11i which refer to any of the following views or anyone who requires an understanding of the TCA architecture to create new queries or customizations:

RA_CUSTOMERS RA_ADDRESSES RA_SITE_USES RA_CONTACTS RA_CONTACT_ROLES


Note 454662.1

R12: How to Link Supplier And Supplier Banks?

Solution

The link between PO_VENDORS and HZ_PARTIES is PO_VENDORS.party_id. The link betweenPO_VENDOR_SITES_ALL and HZ_PARTY_SITES is PO_VENDOR_SITES_ALL.party_site_id.When a Supplier is created Record will be Inserted in HZ_PARTIES. When the Supplier Site is created Record will be Inserted in HZ_PARTY_SITES. When Address is created it will be stored in HZ_LOCATIONSWhen a bank Is Created, the banking information will be stored in IBY_EXT_BANK_ACCOUNTS IBY_EXT_BANK_ACCOUNTS.BANK_id = hz_paties.party_idWhen the Bank is assigned to Vendors then it will be updated in HZ_CODE_ASSIGNMENTS.HZ_CODE_ASSIGNMENTS.owner_table_id = IBY_EXT_BANK_ACCOUNTS.branch_id.


Note 459896.1

How to designate a Bank Account as Internal or external?

Solution

The Bank Accounts created in Cash Management are created as Internal Bank Accounts, the bankaccounts created in the Supplier form or customer form are created as External Bank Accounts.

When the user define a new bank account in the supplier form the information is stored in the IBY_EXT_BANK_ACCOUNTS.

The internal bank accounts are stored in the CE_BANK_ACCOUNT.


Thank You

Thank You

Documents

02-R12 TCA