0%(1)0% menganggap dokumen ini bermanfaat (1 suara)
313 tayangan88 halaman
ORACLE PAYABLES TECHNICAL Changes PRODUCT OVERVIEW PRESENTATION ENTITIES AP-Invoices AP-Payments AP-Suppliers Payment banks NEW AND CHANGED COMPONENTS User Interfaces - NEW USER INTERFACES New Forms New HTML Pages Changed HTML forms Added the Operating Unit field in various windows related to entering invoices (required), and in Find windows.
ORACLE PAYABLES TECHNICAL Changes PRODUCT OVERVIEW PRESENTATION ENTITIES AP-Invoices AP-Payments AP-Suppliers Payment banks NEW AND CHANGED COMPONENTS User Interfaces - NEW USER INTERFACES New Forms New HTML Pages Changed HTML forms Added the Operating Unit field in various windows related to entering invoices (required), and in Find windows.
ORACLE PAYABLES TECHNICAL Changes PRODUCT OVERVIEW PRESENTATION ENTITIES AP-Invoices AP-Payments AP-Suppliers Payment banks NEW AND CHANGED COMPONENTS User Interfaces - NEW USER INTERFACES New Forms New HTML Pages Changed HTML forms Added the Operating Unit field in various windows related to entering invoices (required), and in Find windows.
NEW AND CHANGED COMPONENTS User Interfaces New User Interfaces New Forms New HTML Pages Changes User Interfaces Changed forms Changed HTML Forms Obsoleted User Interfaces Obsolete forms Obsoleted HTML pages 3 NEW USER INTERFACES 4 New Forms
New HTML Pages None
Form name Function Name Payables System Setup APXSYSOP CHANGED USER INTERFACES Changed Forms
5 Form Name Function Name Brief Description of Change Invoices APXINWKB Added the Operating Unit field in various windows related to entering invoices (required), and in Find windows. Invoice Batches APXINWKB Added the Operating Unit field (optional). Quick Invoices APXIISIM Added the Operating Unit field (required). Recurring Invoices APXRICAD Added the Operating Unit field (required). Open Interfaces Invoice APXIIFIX Added the Operating Unit field (optional). Payment Workbench APXPAWKB Added the Operating Unit field (required). Control Payables Period APXSUMPS Added the Ledger field (required) in the Find window. Distribution Set APXSUMDS Added the Operating Unit field (required). Expense Report Templates APXXXDER Added the Operating Unit field (required). Reporting Entity APXTRDRE Added the Operating Unit field (required). Withholding Tax Certificates and Exceptions APXTCERT Added the Operating Unit field (required). CHANGED USER INTERFACES Form Name Function Name Brief Description of Change Withholding Tax Certificates and Exceptions APXTCERT Added the Operating Unit field (required). Withholding Tax Groups APXTGRPS Added the Operating Unit field (required). Withholding Tax Details APXTADTC Added the Operating Unit field (required). Financials Option APXSSFSO Added the Operating Unit field (required) in the Find window. Payables Option APXCUMSP Added the Operating Unit field (required) in the Find window. 6 CHANGED USER INTERFACES Changed HTML Pages None Obsoleted User Interfaces Obsoleted Forms None Obsoleted HTML Pages None
7 REPORTS AND XML PUBLISHER Reports New Reports Changed Reports Obsolete Reports XML Publisher New XML Publisher Components Changes XML Publisher Components Obsolete XML Publisher Components
8 REPORTS New Reports None Changes Reports
9 Report Name Report Files Brief Description of Change Invoice Validation APAPRVL.rdf You can run this report for one or multiple operating units (OUs). Open Interface Import APXIIMPT.rdf /apiimpts.pls/apiimptb. pls/apiimvts.pls /apiimvtb.pls/apiimuts. pls/apiimutb.pls You can run this report for one or multiple OUs. Mass Additions Create APMACR This report runs for all of the OUs of the security profile. Create Adjusting Documents in Payables program APXCADIP.rdf This report runs for one or multiple OUs depending on whether the PO number parameter is provided or not. Supplier Merge APXINUPD.rdf This report runs for the one OU. REPORTS Report Name Report Files Brief Description of Change Sweep Program APXTRSWP.rdf This report runs for a ledger (Primary/Secondary/ALC) or an OU. Depending on the user security profile, the report may represent partial data. Invoice Approval Status APXAPRST.rdf This report runs for a ledger (Primary/Secondary/ALC) or an OU. Depending on the user security profile, the report may represent partial data. Trial Balance XDF extract This report runs for a ledger (Primary/Secondary/ALC) or an OU. Depending on the user security profile, the report may represent partial data. 10 XML PUBLISHER New XML Publisher Components None Changed XML Publisher Components None Obsoleted XML Publisher Components None
11 INTERFACES AND CONFIGURATION Workflows New Workflows Changed Workflows Obsoleted Workflows Public APIs New Public APIs Changed Public APIs Obsoleted/Deprecated Public APIs Programs New Programs Changed Program Obsoleted Programs
12 INTERFACES AND CONFIGURATION SQL Loader Files New SQL Loader Files Changed SQL Loader Files Obsoleted SQL Loader Files Flexfields New Flexfields Changed Flexfields Obsoleted Flexfields Profile Options New Profile Options Changed Profile Options Obsoleted Profile Options
19 Profile Option Name Feature Area MO: Security Profile Multi-Org Access Control MO: Default Operating Unit Multi-Org Access Control for operating unit defaulting TABLES AND VIEWS Tables New Tables Changed Tables Obsoleted Tables Views New Views Changed Views Obsoleted Views Synonyms with Policies New Synonyms with Policies Changed Synonyms with Policies Obsoleted Synonyms with Policies
20 TABLES New Tables
Changed Tables None Obsoleted Tables None
21 Table Name Feature Area AP_PRODUCT_SETUPS Product level setup for Oracle Payables. Some of the options which used to be at the organization level have now been moved to the product level setup table. VIEWS New Views None Changed Views None Obsoleted Views None
22 SYNONYM WITH POLICIES New Synonyms with Policies
Changed Synonyms with Policies None Obsoleted Synonyms with Policies None
23 Synonym Name Policy Name Package Name Function Name DML Operations (Select, Update, Insert, Delete) All the existing multi-org views are replaced by the same name synonym. org_sec Patch/115/sql/ap moconv.sql Select/Update/I nsert/Delete BANKS NEW AND CHANGED COMPONENTS User Interfaces New User Interfaces New Forms New HTML Pages Changes User Interfaces Changed forms Changed HTML Forms Obsoleted User Interfaces Obsolete forms Obsoleted HTML pages 25 NEW USER INTERFACES 26 New Forms None New HTML Pages HTML Page Name Function Name Manage Bank and Branches Bank and Bank Branch Maintenance CHANGED USER INTERFACES Changed Forms None Changed HTML Pages None. Obsoleted User Interfaces Obsoleted Forms
Obsoleted HTML Pages None.
27 Form Name Function Name APXSUMBA AP_APXSUMBA APXSPDPF AP_APXSPDPF APXSUADP will still be used by AR AP_APXSUADP will still be used by AR REPORTS AND XML PUBLISHER Reports New Reports Changed Reports Obsolete Reports XML Publisher New XML Publisher Components Changes XML Publisher Components Obsolete XML Publisher Components
29 XML PUBLISHER New XML Publisher Components None Changed XML Publisher Components None Obsoleted XML Publisher Components None
30 INTERFACES AND CONFIGURATION Workflows New Workflows Changed Workflows Obsoleted Workflows Public APIs New Public APIs Changed Public APIs Obsoleted/Deprecated Public APIs Programs New Programs Changed Program Obsoleted Programs
31 INTERFACES AND CONFIGURATION SQL Loader Files New SQL Loader Files Changed SQL Loader Files Obsoleted SQL Loader Files Flexfields New Flexfields Changed Flexfields Obsoleted Flexfields Profile Options New Profile Options Changed Profile Options Obsoleted Profile Options
38 TABLES AND VIEWS Tables New Tables Changed Tables Obsoleted Tables Views New Views Changed Views Obsoleted Views Synonyms with Policies New Synonyms with Policies Changed Synonyms with Policies Obsoleted Synonyms with Policies
39 TABLES New Tables
40 Table Name Feature Area CE_BANK_ACCOUNTS Internal Bank Accounts CE_PAYMENT_DOCUMENTS Payment Documents to be used for Printed type Payments IBY_EXTERNAL_PAYEES_ALL Payee (Trading Partner Info for paying invoices IBY_PMT_INSTR_USES_ALL Used for Remit to Bank Accounts TABLES Changed Tables
41 Table Name
Feature Area
Brief Description of Change
AP_CHECKS_ALL Payables Payments Data Some new columns are added to AP_CHECKS_ALL table for maintaining real time synchronization with Oracle Payments and Cash Managements. Some existing columns from the same tables have been made obsolete. TABLES Obsoleted Tables 42 Table Name Feature Area
Replaced By
AP_BANK_BRANCHES Bank/Bank Branches CE_BANK_BRANCHES_V AP_BANK_ACCOUNTS_ALL Bank Accounts including Internal and External CE_BANK_USES_OU_V/IBY _EXT_BANK_ACCOUNTS_V AP_BANK_ACCOUNTS_USES _ALL Remit to Bank Account Uses
VIEWS New Views
Obsoleted Views
43 View Name Feature Area CE_BANK_BRANCHES_V Bank/Branches Info CE_BANK_ACCT_USES_OU_V Internal Bank Account Uses Info IBY_EXT_BANK_ACCOUNTS_V Remit to Bank Account Info View Name Feature Area AP_BANK_ACCOUNTS Internal/External Bank Accounts Multi- Org View AP_BANK_ACCOUNT_USES External Bank Account Uses Multi-Org View AP_BANK_ACCOUNT_USES_V External Bank Accounts Uses Reference View SYNONYM WITH POLICIES New Synonyms with Policies None Changed Synonyms with Policies None Obsoleted Synonyms with Policies None
44 SUPPLIERS FUNCTIONAL OVERVIEW Information about the Supplier (name, legal information), Address, and Contact information is replicated in Trading Community Architecture. Attributes that represent the terms and conditions, defaulting information such as payment terms and accounts is maintained in the Supplier/Sites tables. Due to other initiatives such as introduction of Oracle Payments, Oracle E-Business Tax, Oracle Applications Multiple Organizations Access Control, and others, some of the payments and tax related information is migrated to the appropriate products and the related columns are obsoleted from the Suppliers/Sites tables. Supplier API is extended to support creation of TCA entities while creating suppliers. Supplier Merge and the TCA's Party/Party Site merge are modified. Supplier Open Interface processes are enhanced to support creation of TCA entities while importing suppliers and the creation of Supplier Bank Accounts is supported from the Supplier Open Interface.
46 SUPPLIERS In 11i Suppliers defined in AP. Supplier contacts replicated for each supplier site.
In R12 Supplier becomes as TCA Party. Suppliers Sites as TCA Party Site for each distinct address. Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU A single change to an address can be seen instantly by all OUs No longer need to manually push updates across OUs.This can be best understood by the figure below.
47 TECHNICAL OVERVIEW Supplier information is used by over 80 different products within Oracle E-Business Suite. The Supplier, Sites/Locations, and their Contact information are migrated to TCA. Three new tables introduced. AP_SUPPLIERS AP_SUPPLIER_SITES_ALL AP_SUPPLIER_CONTACTS Views are provided PO_VENDORS PO_VENDOR_SITES_ALL PO_VENDOR_CONTACTS
48 TECHNICAL OVERVIEW Suppliers -- With the new architecture, the Supplier entity will represent the supplier account for a party record in TCA. The Suppliers table will be updated with the unique Party identifier for reference purposes. Supplier Sites -- The supplier sites table will store the Site account attributes per Operating Unit, which will default into transactions. Contacts -- Contacts are modeled as a child entity to Supplier Sites in Release 12. Since the Supplier Sites are striped by Operating Unit, the contact records are implicitly striped by Operating Unit. This required our customers to enter/maintain the same contact information more than once if the implementing company did business with the same Supplier Site in more than one Operating Unit.
49 TECHNICAL OVERVIEW Suppliers API A new Suppliers API has been created to support the creation of the TCA objects during the creation of the Suppliers, Sites, and Contacts. The related old public API is obsoleted in Release 12. Also, this API has been extended to create the supplier bank account information in the new Oracle Payments Supplier Banks model. These APIs only support creation of the TCA objects and creation and update of the Payables objects
50 TECHNICAL OVERVIEW Supplier Open Interface Supplier open interface tables are extended to add the necessary information to capture the information to create parties, locations, and contacts in TCA. The import programs are modified to call the new version of the API to create TCA objects and Supplier Bank Accounts in Oracle Payments. We have added a new rejection table to the suppliers open interface tables to capture all the rejections tied to an interface record during the import validation. The import programs will no longer stop on the first rejection that it had encountered
51 TECHNICAL OVERVIEW Supplier Merge The Supplier Merge process has minimal impact in TCA. Each Supplier is associated with a particular Party and each Supplier Site is associated with a particular Party Site. When a Supplier/Supplier Site is merged, the associated Party/Party Site does not change. When Supplier Sites are merged, the associated Party Site also does not change. However, in the Supplier Merge process, when a Supplier Site is Copied from one Supplier to a different Supplier, a new Supplier Site must be created and therefore, a new Party Site must also be generated
52 SUPPLIERS 53 NEW AND CHANGED COMPONENTS User Interfaces New User Interfaces New Forms New HTML Pages Changes User Interfaces Changed forms Changed HTML Forms Obsoleted User Interfaces Obsolete forms Obsoleted HTML pages 54 NEW USER INTERFACES 55 New Forms None New HTML Pages HTML Page Name Function Name Suppliers Page POS_HT_SP_B_SUPP OBSELETED USER INTERFACES Obsoleted User Interfaces Obsoleted Forms
Obsoleted HTML Pages None.
56 Form Name Description APXVDMVD Suppliers Create and Inquire forms are obsoleted and the user interface is replaced by a OA Framework user interface created by Oracle iSupplier Portal REPORTS AND XML PUBLISHER Reports New Reports Changed Reports Obsolete Reports XML Publisher New XML Publisher Components Changes XML Publisher Components Obsolete XML Publisher Components
58 XML PUBLISHER New XML Publisher Components None Changed XML Publisher Components None Obsoleted XML Publisher Components None
59 INTERFACES AND CONFIGURATION Workflows New Workflows Changed Workflows Obsoleted Workflows Public APIs New Public APIs Changed Public APIs Obsoleted/Deprecated Public APIs Programs New Programs Changed Program Obsoleted Programs
60 INTERFACES AND CONFIGURATION SQL Loader Files New SQL Loader Files Changed SQL Loader Files Obsoleted SQL Loader Files Flexfields New Flexfields Changed Flexfields Obsoleted Flexfields Profile Options New Profile Options Changed Profile Options Obsoleted Profile Options
63 Package File Package.Procedure/Functi on Name Description apvndrs.pls apvndrb.pls AP_VENDOR_PUB_PKG. Create_Vendor This is the new public API to create new vendors in Release 12. This procedure takes a vendor record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_rec_type. If the TCA Party ID is provided in the record type, the system will validate and only create the record in AP_SUPPLIERS, otherwise the system will call the TCA API to create Party and then will create the record in AP_SUPPLIERS. PUBLIC APIS 64 Package File Package.Procedure/ Function Name Description AP_VENDOR_PUB_PKG . Update_Vendor This is the new public API to update vendors in Release 12. This procedure takes a vendor record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_rec_type. The Payables API will not update the party record in TCA. It will only update the supplier attributes in AP_SUPPLIERS. AP_VENDOR_PUB_PKG . Create_Vendor_Site This is the new public API to create new vendor sites in Release 12. This procedure takes a vendor site record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_site_rec_type. If the TCA LocationID/PartySiteID is provided in the record type, the system will validate and only create the record in AP_SUPPLIER_SITES_ALL, otherwise the system will call the TCA API to create Location and Party Site, and then will create the record in AP_SUPPLIER_SITES_ALL. 65 PUBLIC APIS 65 Package File Package.Procedure/Func tion Name Description AP_VENDOR_PUB_PKG. Update_Vendor_Site This is the new public API to update vendor sites in Release 12. This procedure takes a vendor site record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_site_rec_type. The Payables API will not update the Location/Party Site records in TCA. It will only update the supplier site attributes in AP_SUPPLIER_SITES_ALL AP_VENDOR_PUB_PKG. Create_Vendor_Contact This is the new public API to create new vendor site contacts in Release 12. This procedure takes a vendor site contact record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_contact_rec_type. This API creates the necessary records in HZ_PERSON_PROFILES, HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_PARTY_SITES, and HZ_CONTACT_POINTS, and creates a record in AP_SUPPLIER_CONTACTS PUBLIC APIS Changed Public APIs None Obsoleted/Deprecated Public APIs None
66 PROGRAMS New Programs None Changed Programs
67 Concurrent Program Short Name Program Name Description APXSUIMP Supplier Open Interface Import Supplier Open Interface Import program is extended to create Parties in TCA when creating the suppliers based on the information in AP_SUPPLIERS_INT. If records are populated in the IBY External Payee Accounts table, then the program will call the necessary APIs from Oracle Payments to create the Supplier Bank Accounts. PROGRAMS Concurrent Program Short Name Program Name Description APXSSIMP Supplier Sites Open Interface Import Supplier Sites Open Interface Import program is extended to create Locations, Party Sites, and Party Site Uses in TCA based on the information provided in AP_SUPPLIER_SITES_INT. If records are populated in the Payments External Payee Accounts table, then the program will call the necessary APIs from Oracle Payments to create the Supplier Bank Accounts for the site. APXSCIMP Supplier Site Contacts Open Interface Import Supplier Sites Contacts Open Interface Import program is extended to create Person Parties, Contact Relationships, Org Contacts, Contact Party Sites, and Contact Points in TCA based on the information provided in AP_SUPPLIER_SITES_ INT. 68 SQL LOADER FILES New SQL Loader Files None Changed SQL Loader Files None Obsoleted SQL Loader Files None
71 TABLES AND VIEWS Tables New Tables Changed Tables Obsoleted Tables Views New Views Changed Views Obsoleted Views Synonyms with Policies New Synonyms with Policies Changed Synonyms with Policies Obsoleted Synonyms with Policies
74 Table Name Replaced by PO_VENDORS PO_VENDORS_OBS PO_VENDOR_SITES_ALL PO_VENDOR_SITES_OBS PO_VENDOR_CONTACTS PO_VENDOR_CONTACTS_OBS TABLES Obsoleted Tables 75 Table Name PO_VENDORS PO_VENDOR_SITES_ALL PO_VENDOR_CONTACTS VIEWS New Views
76 View Name Feature Area PO_VENDORS Bank/Branches Info PO_VENDOR_SITES_ALL Internal Bank Account Uses Info PO_VENDOR_CONTACTS Remit to Bank Account Info SYNONYM WITH POLICIES New Synonyms with Policies None Changed Synonyms with Policies None Obsoleted Synonyms with Policies None
77 78 79 80 81 AP_SUPPLIERS AP_SUPPLIER_SITES_ALL AP_SUPPLIER_CONTACTS HZ_PARTIES HZ_PARTIES_SITES HZ_LOCATIONS HZ_CONTACT _POINTS HZ_PARTIES_ SITES_USES HZ_ORG_CONT ACTS HZ_RELATIONSHI PS person R e l a t i o n s h i p
ORG CONTACT CONTACTS CONTACTS AP OBJECTS TCA OBJECTS SUPPLIERS/SITES MAPPING TO TCA OBJECTS ---------NEW RELATIONSHIP------------- ----------------------TCA RELATIONSHIP----------------- INVOICES 83 Brief Description of Changes in R12 Degree of Impact on Existing Reports and Customizations(Hig h/Low/Medium) Reason For Rating Impact No changes in Column names/Size/Type, column usages and view definitions of AP_INVOICES_ALL Now we can capture additional information like quick credit for Debit Memo, and control amount for cross checking the calculated tax. There are few new columns added in AP_INVOICES_ALL. HIGH As there are changes in table structures especially adding Invoice Lines (AP_INVOICE_LINES_ALL) table, thorough testing is required., Impact on the related custom reports and customizations would be high. All the related custom reports/ customizations will require complete modification and many of them may need to be recreated in order to make them work as before. 84 Brief Description of Changes in R12 Degree of Impact on Existing Reports and Customizations(High/ Low/Medium) Reason For Rating Impact No changes in Column names/Size/Type, column usages and view definitions of AP_INVOICES_ALL Now we can capture additional information like quick credit for Debit Memo, and control amount for cross checking the calculated tax. There are few new columns added in AP_INVOICES_ALL. HIGH As there are changes in table structures especially adding Invoice Lines (AP_INVOICE_LINES_ALL) table, thorough testing is required., Impact on the related custom reports and customizations would be high. All the related custom reports/ customizations will require complete modification and many of them may need to be recreated in order to make them work as before. AP-INVOICES INTERFACE CHANGES 85 Brief Description of Changes in R12 Degree of Impact on Existing Reports and Customizations (High/ Low/Medium) Reason For Rating Impact Invoice lines concept is introduced. Column re- mapping is required to utilize new features in Invoice level. Many new columns related to tax and credit card are added. Few new columns are added in AP_INVOICES_INTERFACE. New columns are added in AP_INVOICE_LINES_INTERFACE . MEDIUM As a new base table AP_INVOICE_LINES is introduced, the impact on the technical architectural changes in the Interface programs is medium, which may result in recreation of some of the custom objects based on the analysis. PAYMENTS AP-PAYMENTS Entity AP_Payments Stores payment related information. Key tables involved are : AP_INVOICE_PAYMENTS_ALL AP_CHECKS_ALL AP_PAYMENT_SCHEDULES_ALL
Some new columns have been added in all the payments table as the payment data model is now a shared across modules. As the existing payables objects pertaining to payments has minimal changes, this has a relatively low impact on related CEMLI components.
Refer document attached below for delta changes to data model.
87 mahindrasatyam.net Safe Harbor This document contains forward-looking statements within the meaning of section 27A of Securities Act of 1933, as amended, and section 21E of the Securities Exchange Act of 1934, as amended. The forward-looking statements contained herein are subject to certain risks and uncertainties that could cause actual results to differ materially from those reflected in the forward-looking statements. Satyam undertakes no duty to update any forward-looking statements. For a discussion of the risks associated with our business, please see the discussions under the heading Risk Factors in our report on Form 6-K concerning the quarter ended September 30, 2008, furnished to the Securities and Exchange Commission on 07 November, 2008, and the other reports filed with the Securities and Exchange Commission from time to time. These filings are available at http://www.sec.gov THANK YOU