AP

All Client payments will be handled by 'Payables'.
For this client will create invoice,validate, pay in full or partial.
Reconcile payments with bank a/c of client.
Create and update of Supplier(Vendor),
setup of payment methods-->Manual,Quick check, Automatic check
setup of terms-->Immediate, net+30, net+45... are necessary.

Steps involved in P2P Cycle:
PO Resp
1.Create requisition from Purchasing or iProcurement module.
2.Create purchase order for the requisition at Purchasing.
Documents-->AutoCreate
3.Create receipt at Purchasing for the PO created in step2

Run "Payon Receipts AutoInvoice" Program to create self billing invoices for receipts.

Payables
4.Create invoice for the PO and match it with receipt at payables
Validate invoice, Create accounting and pay in full for invoice
5.Run 'Transfer Payables to GL' at

Cash Mngt
6. Reconcile payments(Enter bank stmt and clear transaction).

iPayments in 11i turns into Payments Setup Admin.

General Setups Needed:
1.Define which are necessary to creare and pay invoices
Suppliers
Payment terms
Financial and payable options
Banks
Select SOB
Lookup codes
Dff-->
Kff-->

Tables affected by Invoice group:
AP_BATCHES-->batch_id
AP_INVOICES-->Vendor_id & Amount
AP_INVOICE_DISTRIBUTIONS-->CCID & Tax Information
AP_PAYMENT_SCHEDULES-->Due amount and date
Tables affected by Payment Group:
AP_CHECKS-->vendor_id,bank_account_id,amount & check_date
AP_INVOICE_PAYMENTS

R12: Supplier Open Interface
Tables involved are
AP_SUPPLIERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACT_INT

Registry Id is party number from hz_parties.

Tips:
AP_TAX_CODES_ALL is replaced by ZX_RATES_B & ZX_ACCOUNTS.
PO_VENDORS is view in R12 on AP_SUPPLIERS & HZ_PARTIES.
PO_VENDOR_SITES&PO_VENDOR_SITES_ALL are views on AP_SUPPLIER_SITES_ALL.

Receivables AR

RA Tables moved to HZ tables in 11i due to TCA Evaluation.
RA_CUSTOMERS-->HZ_PARRIES, HZ_CUST_ACCOUTNS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES...

Pre 11i there were 11 tables...RA_CUSTOMERS, RA_ADDRESSES....But now in 11i these became views. Now RA_CUSTOMERS is a view which is based on HZ_PARTIES, HZ_CUST_ACCOUNTS.

One party can have multiple customer accounts. One record at HZ_PARTIES can have multiple records at HC_CUST_ACCOUNTS.

Once Party becomes customer, customer information will be stored in HZ_CUST_ACCOUNTS.

Flow of customer Interface:
Feedar System(SQL Loader)-->Staging table(Import, Mapping, Validation)-->Customer Interface(Interfaces-->Customer)-->Customer(HZ) Tables
1.RA_CUSTOMERS_INTERFACE_ALL
2.RA_CUSTOMER_PROFILES_INT_ALL
3.RA_CONTACT_PHONES_INT_ALL
4.RA_CUST_PAY_METHOD_INT_ALL
5.RA_CUSTOMER_BANKS_INT_ALL
Base tables:
All HZ Tables+4 tables(RA_CUST_RECEIPT_METHODS, AP_BANK_ACCOUNTS_ALL,AP_BANK_BRANCHES, AP_BANK_ACCOUNT_USES_ALL)

You have to consider AR Setups while doing Customer Interface:
1.Setups
2.Map the interface tables(5Above) at Import program and validations.
3.Run import program
4.Customer-->Interface
Check output for errors.

Validation errors & tips:
1.Customer Number Automatic-->Check the checkbox at System Options window.
2.Use Bulk collect so that cursor will process 10,000 records at a time
3.Make sure that you are populating correct ORG_ID in interface tables.
4.Checkout few profile options(HZ:%) which will impact Customer interface.
Auto Invoice interface:
RA_INTERFACE_LINES_ALL
RA_INTERAFCE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL
RA_INTERFACE_ERRORS_ALL
Basetables:
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
RA_CUST_TRX_LINE_GL_DIST_ALL
RA_CUST_TRX_TYPES_ALL
Auto Lock Box:
AR_PAYMENTS_INTERFACE_ALL
Basetables:
AR_PAYMENT_SCHEDULES_ALL
AR_CASH_RECEIPTS_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
Interim tables:
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_REPT_LINES_ALL
AR_INTERIM_POSTING
General Setups Needed for AR:
1.Define which are necessary to creare invoices & Receipts
Customers
Payment terms
System options
Auto Accounting
Transaction Type
Transaction Source
Lookup codes
Dff-->
Kff--> Sales tax location and Territory

Few TCA APIs:
hz_cust_account_v2pub.create_account()-->to create party and account
hz_location_v2pub.create_location()-->to create physical location
hz_party_site_v2pub.create_party_site
hz_cust_acct_site_v2pub.create_cust_acct_site()
hz_cust_acct_site_v2pub.create_cust_site_use()

Different statuses of receipts:
Unidentified-->Lack of customer information
UnApplied-->Lack of invoice info
Applied-->All information is set
On-Account-->Lack of sufficient funds

Few validations during interfaces:
1.Address: If interface table is populated by orig_system_address_ref, we should populate RA_ADDRESSES.ADDRESS1-4 fields
2.Location: Populated fields of city,county should be valid with fnd_territories table.
3.Customer Number: It should be null if automatic customer number is enabled, else it should not be null
4.Customer Status: Should be A-->Actice or I-->Inactice
5.Customer Type: Should be one of value from AR_LOOKUPS

Transaction types:
Oracle provides only invoice/credit memo trans types.
Trans type is used to default payment term,account,tax,freight and other receivable information.
Define new trans types at Receivables resp-->setup-->transactions-->transaction types
http://oracle.anilpassi.com/how-to-define-transaction-types-in-oracle-receivables.html

iSupport(IBU)

what is istore?
its a internet based customer support application used to provide online support to customers and employees.
Also provides customers to resolve problems themselves with search functionality.
Provides service profitability by decreasing number of calls to contact center.

It supports these types of users.
1.Primary user
2.Business User
3.Individual User
4.iSupport Admin and etc...

Service Request
After user enters service request will be validated by teleservice and if it valid, provides unique tracking number for future reference.
User can update/cancel/close service request.
User can also attach documents. User can also open closed service requests conditionally.
User can also escalate SR if there is no progress.
User can also create SR templates.

iSupport Additional Features
Knowledge Base: Users can use this using search to resolve issues.
Technical Library: Admin can maintain While papers/Documentation etc
Forums:Online forums to post questions and discuss
Account Mgmt: Users can view orders, invoices,payments and shipping information.