AP R12 Techincal

Slide 1

Oracle Payables technical ChangesProduct Overview PresentationEntities in Payables2MOAC ConsiderationAP-InvoicesAP-PaymentsAP-SuppliersPayment banks

New and changed componentsUser InterfacesNew User InterfacesNew FormsNew HTML PagesChanges User InterfacesChanged formsChanged HTML FormsObsoleted User InterfacesObsolete formsObsoleted HTML pages3New user Interfaces4New Forms

New HTML PagesNone

Form nameFunction NamePayables System SetupAPXSYSOPChanged user InterfacesChanged Forms

5Form NameFunction Name Brief Description of Change InvoicesAPXINWKBAdded the Operating Unit field in various windows related to entering invoices (required), and in Find windows.Invoice Batches APXINWKBAdded the Operating Unit field (optional).Quick InvoicesAPXIISIMAdded the Operating Unit field (required).Recurring InvoicesAPXRICADAdded the Operating Unit field (required).Open Interfaces InvoiceAPXIIFIXAdded the Operating Unit field (optional).Payment WorkbenchAPXPAWKBAdded the Operating Unit field (required).Control Payables PeriodAPXSUMPSAdded the Ledger field (required) in the Find window.Distribution SetAPXSUMDSAdded the Operating Unit field (required).Expense Report TemplatesAPXXXDERAdded the Operating Unit field (required).Reporting EntityAPXTRDREAdded the Operating Unit field (required).Withholding Tax Certificates and ExceptionsAPXTCERTAdded the Operating Unit field (required).Changed user InterfacesForm NameFunction Name Brief Description of Change Withholding Tax Certificates and ExceptionsAPXTCERTAdded the Operating Unit field (required).Withholding Tax GroupsAPXTGRPSAdded the Operating Unit field (required).Withholding Tax DetailsAPXTADTCAdded the Operating Unit field (required).Financials OptionAPXSSFSOAdded the Operating Unit field (required) in the Find window.Payables OptionAPXCUMSPAdded the Operating Unit field (required) in the Find window.6Changed user InterfacesChanged HTML PagesNoneObsoleted User InterfacesObsoleted FormsNoneObsoleted HTML PagesNone

7Reports and XML PublisherReportsNew ReportsChanged ReportsObsolete ReportsXML PublisherNew XML Publisher ComponentsChanges XML Publisher ComponentsObsolete XML Publisher Components

8ReportsNew ReportsNoneChanges Reports

9Report NameReport Files Brief Description of Change Invoice Validation APAPRVL.rdfYou can run this report for one or multiple operating units (OUs).Open Interface ImportAPXIIMPT.rdf/apiimpts.pls/apiimptb.pls/apiimvts.pls/apiimvtb.pls/apiimuts.pls/apiimutb.plsYou can run this report for one or multiple OUs.Mass Additions CreateAPMACRThis report runs for all of the OUs of the security profile.Create Adjusting Documents in Payables program APXCADIP.rdfThis report runs for one or multiple OUs depending on whether the PO number parameter is provided or not.Supplier MergeAPXINUPD.rdfThis report runs for the one OU.ReportsReport NameReport Files Brief Description of Change Sweep ProgramAPXTRSWP.rdfThis 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 StatusAPXAPRST.rdfThis report runs for a ledger (Primary/Secondary/ALC) or an OU. Depending on the user security profile, the report may represent partial data.Trial BalanceXDF extractThis report runs for a ledger (Primary/Secondary/ALC) or an OU. Depending on the user security profile, the report may represent partial data.10XML PublisherNew XML Publisher ComponentsNoneChanged XML Publisher ComponentsNoneObsoleted XML Publisher ComponentsNone

11Interfaces and ConfigurationWorkflows 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

12Interfaces and ConfigurationSQL 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

13WorkflowsNew WorkflowsNoneChanged WorkflowsNoneObsoleted WorkflowsNone

14Public APIsNew Public APIsNoneChanged Public APIsNoneObsoleted/Deprecated Public APIsNone

15ProgramsNew ProgramsNone Changed ProgramsNoneObsoleted ProgramsNone16SQL Loader FilesNew SQL Loader FilesNoneChanged SQL Loader FilesNoneObsoleted SQL Loader Files

17FlexfieldsNew FlexfieldsNoneChanged FlexfieldsNoneObsoleted FlexfieldsNone

18Profile OptionsNew Profile Options

Changed Profile OptionsNoneObsoleted Profile OptionsNone

19Profile Option NameFeature AreaMO: Security ProfileMulti-Org Access ControlMO: Default Operating UnitMulti-Org Access Control for operating unit defaultingTables and ViewsTables 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

20TablesNew Tables

Changed TablesNoneObsoleted TablesNone

21Table Name Feature Area AP_PRODUCT_SETUPSProduct 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.ViewsNew ViewsNone Changed ViewsNoneObsoleted ViewsNone

22Synonym with PoliciesNew Synonyms with Policies

Changed Synonyms with PoliciesNoneObsoleted Synonyms with PoliciesNone

23Synonym NamePolicy NamePackage NameFunction NameDML Operations (Select, Update, Insert, Delete)All the existing multi-org views are replaced by the same name synonym.org_secPatch/115/sql/apmoconv.sqlSelect/Update/Insert/DeletebanksNew and changed componentsUser InterfacesNew User InterfacesNew FormsNew HTML PagesChanges User InterfacesChanged formsChanged HTML FormsObsoleted User InterfacesObsolete formsObsoleted HTML pages25New user Interfaces26New FormsNoneNew HTML PagesHTML Page Name Function Name Manage Bank and Branches Bank and Bank Branch MaintenanceChanged user InterfacesChanged FormsNoneChanged HTML PagesNone. Obsoleted User InterfacesObsoleted Forms

Obsoleted HTML PagesNone.

27Form Name Function Name APXSUMBAAP_APXSUMBAAPXSPDPFAP_APXSPDPFAPXSUADP will still be used by ARAP_APXSUADP will still be used by ARReports and XML PublisherReportsNew ReportsChanged ReportsObsolete ReportsXML PublisherNew XML Publisher ComponentsChanges XML Publisher ComponentsObsolete XML Publisher Components

28ReportsNew ReportsNone. Changed ReportsNone. Obsolete ReportsNone.

29XML PublisherNew XML Publisher ComponentsNoneChanged XML Publisher ComponentsNoneObsoleted XML Publisher ComponentsNone




33Public APIsNew Public APIs

Changed Public APIsNoneObsoleted/Deprecated Public APIsNone

34Public API Name Feature Area IBY_DISBURSEMENT_COMP_PUB. Get_Applicable_Payee_BankAcctsFor deriving applicable external bank accounts IBY_DISBURSEMENT_COMP_PUB. Get_Default_Payee_Bank_AccFor deriving default External Bank Accounts IBY_DISBURSEMENT_COMP_PUB. Get_Default_Payment_AttributesFor deriving default Payment AttributesProgramsNew ProgramsNone Changed ProgramsNoneObsoleted ProgramsNone35SQL Loader FilesNew SQL Loader FilesNoneChanged SQL Loader FilesNoneObsoleted SQL Loader FilesNone


37Profile OptionsNew Profile OptionsNoneChanged Profile OptionsNoneObsoleted Profile OptionsNone

38Tables and ViewsTables 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

39TablesNew Tables

40Table Name Feature Area CE_BANK_ACCOUNTSInternal Bank AccountsCE_PAYMENT_DOCUMENTSPayment Documents to be used for Printed type PaymentsIBY_EXTERNAL_PAYEES_ALLPayee (Trading Partner Info for paying invoicesIBY_PMT_INSTR_USES_ALLUsed for Remit to Bank AccountsTablesChanged Tables

41Table Name Feature Area Brief Description of Change AP_CHECKS_ALLPayables Payments DataSome 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.TablesObsoleted Tables42Table Name Feature Area Replaced By AP_BANK_BRANCHESBank/Bank BranchesCE_BANK_BRANCHES_VAP_BANK_ACCOUNTS_ALLBank Accounts including Internal and ExternalCE_BANK_USES_OU_V/IBY_EXT_BANK_ACCOUNTS_VAP_BANK_ACCOUNTS_USES_ALLRemit to Bank Account Uses ViewsNew Views

Obsoleted Views

43View Name Feature Area CE_BANK_BRANCHES_VBank/Branches InfoCE_BANK_ACCT_USES_OU_VInternal Bank Account Uses InfoIBY_EXT_BANK_ACCOUNTS_VRemit to Bank Account InfoView Name Feature Area AP_BANK_ACCOUNTSInternal/External Bank Accounts Multi-Org ViewAP_BANK_ACCOUNT_USESExternal Bank Account Uses Multi-Org ViewAP_BANK_ACCOUNT_USES_VExternal Bank Accounts Uses Reference ViewSynonym with PoliciesNew Synonyms with PoliciesNoneChanged Synonyms with PoliciesNoneObsoleted Synonyms with PoliciesNone

44SuppliersFunctional OverviewInformation 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.

46SuppliersIn 11iSuppliers defined in AP. Supplier contacts replicated for each supplier site.

In R12Supplier 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.

47Technical OverviewSupplier 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_SUPPLIERSAP_SUPPLIER_SITES_ALLAP_SUPPLIER_CONTACTSViews are provided PO_VENDORSPO_VENDOR_SITES_ALLPO_VENDOR_CONTACTS

48Technical OverviewSuppliers -- 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.

49Technical OverviewSuppliers APIA 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

50Technical OverviewSupplier Open InterfaceSupplier 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

51Technical OverviewSupplier MergeThe 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

52Suppliers53

New and changed componentsUser InterfacesNew User InterfacesNew FormsNew HTML PagesChanges User InterfacesChanged formsChanged HTML FormsObsoleted User InterfacesObsolete formsObsoleted HTML pages54New user Interfaces55New FormsNoneNew HTML PagesHTML Page Name Function Name Suppliers PagePOS_HT_SP_B_SUPPObseleted user InterfacesObsoleted User InterfacesObsoleted Forms

Obsoleted HTML PagesNone.

56Form Name Description APXVDMVDSuppliers Create and Inquire forms are obsoleted and the user interface is replaced by a OA Framework user interface created by Oracle iSupplier PortalReports and XML PublisherReportsNew ReportsChanged ReportsObsolete ReportsXML PublisherNew XML Publisher ComponentsChanges XML Publisher ComponentsObsolete XML Publisher Components

57ReportsNew ReportsNone. Changed ReportsNone. Obsolete ReportsNone.

58XML PublisherNew XML Publisher ComponentsNoneChanged XML Publisher ComponentsNoneObsoleted XML Publisher ComponentsNone




62Public APIsNew Public APIs

63Package File Package.Procedure/Function Name Descriptionapvndrs.plsapvndrb.plsAP_VENDOR_PUB_PKG. Create_VendorThis 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 APIs64Package File Package.Procedure/Function Name DescriptionAP_VENDOR_PUB_PKG. Update_VendorThis 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_SiteThis 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.65Public APIs65Package File Package.Procedure/Function Name DescriptionAP_VENDOR_PUB_PKG. Update_Vendor_SiteThis 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_ALLAP_VENDOR_PUB_PKG. Create_Vendor_ContactThis 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_CONTACTSPublic APIsChanged Public APIsNoneObsoleted/Deprecated Public APIsNone

66ProgramsNew ProgramsNone Changed Programs

67Concurrent Program Short Name Program Name DescriptionAPXSUIMP Supplier Open Interface ImportSupplier 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.ProgramsConcurrent Program Short Name Program Name DescriptionAPXSSIMP 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. 68SQL Loader FilesNew SQL Loader FilesNoneChanged SQL Loader FilesNoneObsoleted SQL Loader FilesNone


70Profile OptionsNew Profile OptionsNoneChanged Profile OptionsNoneObsoleted Profile OptionsNone

71Tables and ViewsTables 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

72TablesNew Tables

73Table Name Feature Area AP_SUPPLIERS SuppliersAP_SUPPLIER_SITES_ALL Supplier SitesAP_SUPPLIER_CONTACTS Supplier ContactsAP_SUPPLIER_INT_REJECTIONSSupplier interface rejectionsTablesChanged TablesNoneObsoleted Tables

74Table NameReplaced by PO_VENDORSPO_VENDORS_OBSPO_VENDOR_SITES_ALLPO_VENDOR_SITES_OBSPO_VENDOR_CONTACTS PO_VENDOR_CONTACTS_OBSTablesObsoleted Tables75Table Name PO_VENDORSPO_VENDOR_SITES_ALLPO_VENDOR_CONTACTS ViewsNew Views

76View Name Feature Area PO_VENDORSBank/Branches InfoPO_VENDOR_SITES_ALLInternal Bank Account Uses InfoPO_VENDOR_CONTACTS Remit to Bank Account InfoSynonym with PoliciesNew Synonyms with PoliciesNoneChanged Synonyms with PoliciesNoneObsoleted Synonyms with PoliciesNone

7778

79

80

81AP_SUPPLIERSAP_SUPPLIER_SITES_ALLAP_SUPPLIER_CONTACTSHZ_PARTIESHZ_PARTIES_SITESHZ_LOCATIONSHZ_CONTACT_POINTSHZ_PARTIES_SITES_USESHZ_ORG_CONTACTSHZ_RELATIONSHIPSpersonRelationshipORGORGORGCONTACTCONTACTSCONTACTSAP OBJECTSTCA OBJECTSSUPPLIERS/SITES MAPPING TO TCA OBJECTS---------NEW RELATIONSHIP-----------------------------------TCA RELATIONSHIP-----------------Invoices83Brief Description of Changes in R12Degree of Impact on Existing Reports and Customizations(High/Low/Medium)Reason For Rating ImpactNo 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.HIGHAs 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.84Brief Description of Changes in R12Degree of Impact on Existing Reports and Customizations(High/Low/Medium)Reason For Rating ImpactNo 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.HIGHAs 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 Changes85Brief Description of Changes in R12Degree of Impact on Existing Reports and Customizations(High/Low/Medium)Reason For Rating ImpactInvoice 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.MEDIUMAs 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.paymentsAP-PaymentsEntity AP_Payments Stores payment related information.Key tables involved are :AP_INVOICE_PAYMENTS_ALLAP_CHECKS_ALLAP_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.netSafe HarborThis 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.govThank YouAppendix-APPAYKey Tables and Relationships for Invoices

AP_INVOICE_PAYMENTS_ALL It contains records of invoice payments made to suppliers. There is one row for each payment that is made for each invoice. There is one payment and one invoice for each payment in this table. Payables application updates this table when an automatic payment batch is confirmed, a manual payment is entered, or a Quick payment is processed. When a payment is void, Payables application inserts an additional payment line that is the negative of the original payment line. Values for POSTED_FLAG will be 'Y' for accounted payments and 'N' for unaccounted payments. Values for ACCRUAL_POSTED_FLAG will be 'Y' for accounted payments and 'N' for unaccounted payments under accrual basis accounting; values for CASH_POSTED_FLAG will be 'Y' for accounted payments or 'N' for unaccounted payments under cash basis accounting. The key columns are: 1. AMOUNT (Payment Amount)2. CHECK_ID (Payment Identifier) 3. PAYMENT_NUM(Payment Number), PERIIOD_NAME(Period Name) BANK_ACCOUNT_NUM(Bank Account Number) 4. BANK_ACCOUNT_TYPE(Bank Account Type Code)5. BANK_NUM(Bank Number)6. DISCOUNT_TAKEN(Amount of Discount Taken) 7. EXCHANGE_RATE (Exchange Rate)8. INVOICE_PAYMENT_TYPE (Payment Creation Method) 9. REVERSAL_FLAG (Reversal Flag)The primary key for invoice payment is INVOICE_PAYMENT_ID.New Columns in AP_INVOICE_PAYMENTS_ALL (RELEASE 12)

1. INVOICING_PARTY_ID(Original party id for third party payment)2. INVOICING_PARTY_SITE_ID(Original party id site for third party payment)3. INVOICING_PARTY_SITE_ID(Original vendor site id for third party payment)AP_CHECKS_ALL This table stores information about payments issued to suppliers or refunds received from suppliers. One row is needed for each payment issued to a supplier or refund received from a supplier. Payables application uses this information to record payments made to suppliers or refunds received from suppliers. Payables application stores the supplier name and bank account name for auditing purposes, in case either one is changed after creation of the payment. Address information for all payments is stored. If there are changes to the supplier payment address on manual payments or Quick payments, Payables application maintains the new address information in this table. BANK_ACCOUNT_NUM, BANK_NUM, and BANK_ACCOUNT_TYPE is used for the supplier's bank information when you use the Electronic payment method. The key columns are: 1. AMOUNT (Payment Amount) 2. BANK_ACCOUNT_NAME (Bank Account Name) 3. CHECK_DATE(Payment Date) 4. CHECK_ID (Payment Identifier) 5. CHECK_NUMBER (Payment Number) 6. PAYMENT_METHOD_LOOKUP_CODE (Name of Payment Method)7. CHECKRUN_NAME (Payment Batch Name) 8. CLEARED_AMOUNT (Payment Cleared Amount)The primary key for Payables Checks is CHECK_ID.New Columns in AP_CHECKS_ALL (RELEASE 12)

1. CE_BANK_ACCT_USE_ID (Bank account identifier)2. PAYMENT_METHOD_CODE (Payment method identifier)3. PARTY_ID (Party identifier)4. PARTY_SITE_ID (Party Site identifier)5. PAYMENT_PROFILE_ID (Payment process profile identifier)6. SETTLEMENT_PRIORITY (The priority with which the financial institution or payment system should settle payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY')7. BANK_CHARGE_BEARER (Bearer of bank charge cost)8. LEGAL_ENTITY_ID (Legal entity identifier)9. PAYMENT_DOCUMENT_ID (Payment document identifier)10. COMPLETED_PMTS_GROUP_ID (Completed payments group identifier)11. PAYMENT_ID (Oracle Payments payment identifier)12. PAYMENT_INSTRUCTION_ID (Payment Instruction Identifier)AP_PAYMENT_SCHEDULES_ALL It contains information about scheduled payments for an invoice. One row is created for each time you intend to make a payment on an invoice. This information is used to determine when to make payments on an invoice and how much to pay in an automatic payment batch. Values for HOLD_FLAG may be 'Y' to place a hold on the scheduled payment, or 'N' not to do so. Values for PAYMENT_STATUS_FLAG may be 'Y' for fully paid payment schedules, 'N' for unpaid scheduled payments, or 'P' for partially paid scheduled payments. For converted records, enter a value for AMOUNT_REMAINING. The key columns are: 1. AMOUNT_REMAINING (Amount Remaining for Payment)2. DISCOUNT_DATE (Discount Date)3. GROSS_AMOUNT (Gross amount due for payment) PAYMENT_METHOD_LOOKUP_CODE (Payment Method4. PAYMENT_PRIORITY (Payment Priority (1 to 99)) 5. PAYMENT_STATUS_FLAG (Status of Payment (Y/N/P) The primary key for Payment Schedules is combination of INVOICE_ID and PAYMENT_NUM.New Columns in AP_PAYMENT_SCHEDULES_ALL (RELEASE 12)

1. IBY_HOLD_REASON (Payment schedule hold reason)2. PAYMENT_METHOD_CODE (Payment method identifier)3. REMITTANCE_MESSAGE1 (Remittance message for use in payment processing)4. REMITTANCE_MESSAGE2 (Remittance message for use in payment processing)5. REMITTANCE_MESSAGE3 (Remittance message for use in payment processing)