Sie sind auf Seite 1von 5

R12 Table Changes

Suppliers: New R12 tables -> Old 11i Tables AP_SUPPLIERS - replaces PO_VENDORS AP_SUPPLIER_SITES_ALL- replaces PO_VENDOR_SITES_ALL Additional supplier related tables in IBY (Payments) and HZ (TCA): IBY_EXTERNAL_PAYEES_ALL - stores Payee(supplier) information. HZ_PARTIES - Party data for the suppliers. HZ_PARTY_SITES - Party site data for the supplier sites. Invoices: Additional table in R12: AP_INVOICE_LINES_ALL Allocations - AP_CHRG_ALLOCATIONS_ALL is obsolete in R12 Taxes: Functionality provided by E-Business Tax New tables in R12 ZX_LINES - Detailed Tax lines for the invoice (trx_id = invoice_id) ZX_LINES_SUMMARY - Summary tax lines for the invoice (trx_id = invoice_id) ZX_REC_NREC_DIST - Tax distributions for the invoice (trx_id = invoice_id) ZX_LINES_DET_FACTORS - Tax determination factors for the invoice (trx_id = invoice_id) Payments: Functionality moved to central Payments (IBY) New IBY tables in R12: IBY_PAY_SERVICE_REQUESTS - Payment Process Request information Accounting: Functionality moved to SubLedger Accounting (SLA) New R12 tables: XLA_EVENTS -> replaces AP_ACOCUNTING_EVENTS_ALL XLA_AE_HEADERS -> replaces AP_AE_HEADERS_ALL XLA_AE_LINES-> replaces AP_AE_LINES_ALL XLA_DISTRIBUTION_LINKS Trial Balance: New R12 Table XLA_TRIAL_BALANCES AP_LIABILITY_BALANCE-> not used in new R12 transactions

AP_TRIAL_BALANCE -> not used in new R12 transactions Bank Accounts: Functionality moved to Cash Management. CE_BANK_ACCOUNTS -> replaces AP_BANK_ACCOUNTS_ALL CE_BANK_ACCT_USES_ALL -> replaces AP_BANK_ACCOUNT_USES_ALL CE_PAYMENT_DOCUMENTS -> AP_CHECK_STOCKS_ALL

- IBY_EXTERNAL_PAYEES_ALL : This stores supplier information and customer information - IBY_EXT_BANK_ACCOUNTS : This storage for bank accounts - IBY_EXT_PARTY_PMT_MTHDS : This storage for payment method usage rules. - IBY_CREDITCARD : stores the credit card information for a customer - IBY_EXT_BANK_ACCOUNTS :This Stores external bank accounts . These records have bank_account_type = Supplier - IBY_ACCOUNT_OWNERS :stores the joint account owners of a bank account - IBY_PMT_INSTR_USES_ALL : This stores data from AP_BANK_ACCOUNT_USES_ALL for payment instruments assignments .This information is stored in the following iPayment (IBY) tables:

MOAC (Multi Org Access Control)


1) R12 offers true Multi-Org Access. Responsibilities are assigned with a Security profile which is a group of operating Units. Assignment is through the profile option 'MO: Security Profile' set at the Responsibility Level. 2) Security Profile is setup from HR Responsibility. The Security List Maintenance concurrent program must be run each time you add or change Security Profiles. So from one responsibility you can perform transactions and report on transactions from multiple operating units 3) Pre-R12 you could set your SQL session context for multi-org with the following, Or you could have used FND_GLOBAL.APPS_INITIALIZE to set your context. BEGIN dbms_application_info.set_client_info (2); END;

4) In R12 you can set your SQL session context for a single OU with the following: BEGIN Execute mo_global.set_policy_context ('S', 2); END; The S means Single Org Context 2 is the ORG_ID I want set 5) Also in R12 you can set your SQL session context for multiple OUs with the following: BEGIN Execute mo_global.set_org_access (NULL, 64, 'ONT'); END; 64 is the Security Profile you want to use ONT is the application short name associated with the responsibility you will be using 6) The following SQL will dump out the Security Profiles and Operating Unit Names assigned to them SELECT psp.SECURITY_PROFILE_NAME, psp.SECURITY_PROFILE_ID, hou.NAME, hou.ORGANIZATION_ID FROM PER_SECURITY_PROFILES psp, PER_SECURITY_ORGANIZATIONS pso, HR_OPERATING_UNITS hou WHERE pso.SECURITY_PROFILE_ID = psp.SECURITY_PROFILE_ID AND pso.ORGANIZATION_ID = hou.ORGANIZATION_ID; 7) There are three Profile Options you need to be aware of related to Multi-Org that should be set at the Responsibility Level: MO: Security Profile- Always evaluated first. MO: Operating Unit- Secondary priority being evaluated after MO: Security Profile MO: Default Operating Unit- Sets the default Operating Unit for transactions when running under a Security Profile

R12 SLA (Subledger Accounting)


1) All accounting performed before transfer to the GL. Accounting data generated and stored in Accounting Events tables prior to transfer to GL 2) Run Create Accounting to populate accounting events (SLA) tables. User can View Accounting only after Create Accounting is run. Create Accounting

process Applies accounting rules Loads SLA tables, GL tables Creates detailed data per accounting rules, stores in SLA distribution links table 3) Below are the key tables for SLA in R12 XLA_AE_HEADERS xah XLA_AE_LINES xal XLA_TRANSACTION_ENTITIES xte XLA_DISTRIBUTION_LINKS xdl GL_IMPORT_REFERENCES gir Below are the possible joins between these XLA Tables xah.ae_header_id = xal.ae_header_id xah.application_id = xal.application_id xal.application_id = xte.application_id xte.application_id = xdl.application_id xah.entity_id = xte.entity_id xah.ae_header_id = xdl.ae_header_id xah.ae_line_num = xdl.ae_line_num xah.event_id = xdl.event_id xal.gl_sl_link_id = gir.gl_sl_link_id xal.gl_sl_link_table = gir.gl_sl_link_table xah.application_id = (Different value based on Module) xte.entity_code = 'TRANSACTIONS' or 'RECEIPTS' or 'ADJUSTMENTS' or 'PURCHASE_ORDER' or 'AP_INVOICES' or 'AP_PAYMENTS' or 'MTL_ACCOUNTING_EVENTS' or 'WIP_ACCOUNTING_EVENTS' xte.source_id_int_1 = 'INVOICE_ID' or 'CHECK_ID' or 'CUSTOMER_TRX_ID' XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types xdl.source_distribution_type = 'AP_PMT_DIST '

and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id --------------xdl.source_distribution_type = 'AP_INV_DIST' and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id --------------xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL' and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id and AR_DISTRIBUTIONS_ALL.source_id = AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id --------------xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL' and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id --------------xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS' and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id --------------xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS' and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id --------------xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER' and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id

Das könnte Ihnen auch gefallen