Showing posts with label AP. Show all posts
Showing posts with label AP. Show all posts

Thursday, 26 September 2019

Oracle APPS R12 Query to find PAYMENT AGAINST INVOICE

24 comments
SELECT b.segment1 vendor_number,
       b.vendor_name vendor_name,
       c.vendor_site_code,
       c.pay_group_lookup_code,
       a.invoice_num invoice_number,
       a.invoice_date,
       a.gl_date,
       d.due_date,
       a.invoice_currency_code,
       a.invoice_amount,
       a.amount_paid,
       a.pay_group_lookup_code,
       d.payment_priority,
       (SELECT MAX (check_date)
          FROM ap_checks_all aca, ap_invoice_payments_all aip
         WHERE aca.CHECK_ID = aip.CHECK_ID AND aip.invoice_id = a.invoice_id)
          "Last Payment Made on",
          a.cancelled_date
  FROM apps.ap_invoices_all a,
       apps.ap_suppliers b,
       apps.ap_supplier_sites_all c,
       apps.ap_payment_schedules_all d,
       apps.ap_invoice_payments_all ap,
       ap_checks_all ac
WHERE     a.vendor_id = b.vendor_id
       AND a.vendor_site_id = c.vendor_site_id
       AND b.vendor_id = c.vendor_id
       AND a.invoice_id = d.invoice_id
       AND ap.invoice_id = a.invoice_id
       AND ac.CHECK_ID = ap.CHECK_ID
       and ac.STATUS_LOOKUP_CODE <> 'VOIDED'
       AND a.org_id = 89
       and a.invoice_id= 1234
       AND a.pay_group_lookup_code IN ('DISTRIBUTOR')
       AND ac.check_date BETWEEN TO_DATE ('01-Apr-2014', 'DD-MON-YYYY') AND TO_DATE ('30-Jun-2014 23:59:59', 'DD-MON-YYYY HH24:MI:SS')


Thanks
Amar Alam

Friday, 23 August 2013

SQL Query to Link GL Journal and SLA Tables for 'Misc Receipts','Receipts' and 'Reconciled Payments'

3 comments

SELECT  ada.line_id, jh.je_category Category,
  jh.period_name Period_Name,
  NULL Invoice_No_or_Memo_No,
  nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0) Amount_journal,
  NVL(xal.entered_dr,0)-NVL(xal.entered_cr,0) Amount_Xla,
  NVL(ada.amount_dr,0)-NVL(ada.amount_cr,0) Amount_Receivables,
  DECODE(jh.ledger_id,2027,'USD',2029,'EUR',2023,'USD') Currency_Code,
   xdl.source_distribution_type,
  jh.ledger_id Book
FROM gl_je_headers jh,
  gl_je_lines jl,
  gl_code_combinations gcc,
  gl_import_references gir,
  xla_ae_lines xal,
  XLA_DISTRIBUTION_LINKS xdl,
  xla_ae_headers xah,
  AR_DISTRIBUTIONS_ALL ada
WHERE 1                    =1
AND jh.je_header_id        =jl.je_header_id
AND jl.code_combination_id =gcc.code_combination_id
AND gir.je_header_id       =jh.je_header_id
AND gir.je_line_num        =jl.je_line_num
AND gir.gl_sl_link_id      =xal.gl_sl_link_id
and xah.ae_header_id=xal.ae_header_id
and xal.application_id = xdl.application_id
and xah.ae_header_id = xdl.ae_header_id
and xal.ae_line_num = xdl.ae_line_num
and xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'
and xdl.source_distribution_id_num_1 = ada.line_id
AND gcc.code_combination_id=46032
and jh.period_name like '13-Jun'
and jh.je_category in ('Misc Receipts','Receipts')
and abs(nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0))<> abs(NVL(ada.amount_dr,0)-NVL(ada.amount_cr,0))
and abs(NVL(xal.entered_dr,0)-NVL(xal.entered_cr,0)) <> abs(NVL(ada.amount_dr,0)-NVL(ada.amount_cr,0))
and jh.ledger_id = '2029';



SELECT  jh.name,jh.je_category Category,
  jh.period_name Period_Name,
  NULL Invoice_No_or_Memo_No,
  abs(nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0)) Amount_journal,
  abs (NVL(xal.accounted_dr,0)-NVL(xal.accounted_cr,0)) Amount_Xla,
  abs(sum(aphd.amount)) amount_payment,
    DECODE(jh.ledger_id,2027,'USD',2029,'EUR',2023,'USD') Currency_Code,
   xdl.source_distribution_type,
  jh.ledger_id Book
FROM gl_je_headers jh,
  gl_je_lines jl,
  gl_code_combinations gcc,
  gl_import_references gir,
  xla_ae_lines xal,
  XLA_DISTRIBUTION_LINKS xdl,
  xla_ae_headers xah,
  AP_PAYMENT_HIST_DISTS aphd
WHERE 1                    =1
AND jh.je_header_id        =jl.je_header_id
AND jl.code_combination_id =gcc.code_combination_id
AND gir.je_header_id       =jh.je_header_id
AND gir.je_line_num        =jl.je_line_num
AND gir.gl_sl_link_id      =xal.gl_sl_link_id
and xah.ae_header_id=xal.ae_header_id
and xal.application_id = xdl.application_id
and xah.ae_header_id = xdl.ae_header_id
and xal.ae_line_num = xdl.ae_line_num
AND gcc.code_combination_id=46032
and xdl.source_distribution_type = 'AP_PMT_DIST'
and xdl.source_distribution_id_num_1 = aphd.payment_hist_dist_id
and jh.je_category in ('Reconciled Payments')
and jh.ledger_id ='2029'
and jh.period_name like '13-Jun'
--and abs (nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0))  <> abs(sum(aphd.amount) )
--and NVL(xal.accounted_dr,0)-NVL(xal.accounted_cr,0) <> abs(sum(aphd.amount)),
 group by  jh.name,jh.je_category,
  jh.period_name,
   nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0),
  NVL(xal.accounted_dr,0)-NVL(xal.accounted_cr,0),
     DECODE(jh.ledger_id,2027,'USD',2029,'EUR',2023,'USD'),
   xdl.source_distribution_type,
  jh.ledger_id
  having --abs (nvl(jl.entered_dr,0)-nvl(jl.entered_cr,0))  <> abs(sum(aphd.amount) );
abs( NVL(xal.accounted_dr,0)-NVL(xal.accounted_cr,0)) <> abs(sum(aphd.amount));



Ur's
AmarAlam

Wednesday, 14 August 2013

Puchasing and Payables Module: Technical Details

1 comments
PO_VENDORS
This table stores information about your suppliers. Oracle Purchasing uses this information to determine active suppliers. The primary key is VENDOR_ID.

PO_VENDOR_SITES_ALL
This table stores information about supplier sites. Oracle Purchasing uses this information to store supplier address information. The primary key is VENDOR_SITE_ID.

PO_VENDOR_CONTACTS
This table stores information about supplier site contacts. The primary key is VENDOR_CONTACT_ID.

PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_HEADERS_ALL stores information about requisition headers. Each row contains the requisition number, preparer status, and description. It is one of three tables that stores requisition information. The primary key is REQUISITION_HEADER_ID.

PO_REQUISITION_LINES_ALL
This table stores information about requisition lines. Each row contains the line number, item number, item category, item description, need-by date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested supplier information for the requisition line. This table is one of three tables that stores requisition information. The primary key is REQUISITION_LINE_ID.

PO_REQ_DISTRIBUTIONS_ALL
PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated with each requisition line. Each requisition line must have at least one accounting distribution. Each row includes the Accounting Flex field ID and requisition line quantity. This table is one of three tables that stores requisition information. The primary key is DISTRIBUTION_ID.

PO_HEADERS_ALL
PO_HEADERS_ALL contains information for your purchasing documents. Each row contains buyer information, supplier information, notes, foreign currency information, terms and conditions information, and the document status. Oracle Purchasing uses this information to record information related to a complete document. The primary key is PO-HEADER_ID.

PO_LINES_ALL
PO_LINES_ALL stores current information about each purchase order line. You need one row for each line you attach to a document. Each row includes the line number, item number and category unit, price, tax information, and quantity ordered for the line. Oracle Purchasing uses this information to record and update item and price information for purchase orders, quotations, and RFQs. The primary key is PO_LINE_ID.

PO_LINE_LOCATIONS_ALL
This table contains information about purchase order shipment schedules and blanket agreement price breaks. You must have one row for each schedule or price break you attach to a document line. Each row contains the location, quantity, and dates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information for purchase orders and price break information for blanket purchase orders, quotations, and RFQs. The primary key is LINE_LOCATION_ID.

PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALL contains accounting information for a purchase order shipment line. Oracle Purchasing uses this information to record accounting and requisition information for purchase orders and releases. It is one of five tables that stores purchase orders and releases. The primary key is PO_DISTRIBUTION_ID.

RCV_SHIPMENT_HEADERS
This table stores common information about the source of your receipts or expected receipts. You group your receipts by the source type and the source of the receipt. Oracle Purchasing does not allow you to group receipts from different sources under one receipt header. The primary key is SHIPMENT_HEADER_ID.

RCV_SHIPMENT_LINES
This table stores information about items that have been shipped or received from a specific receipt source. This table also stores information about the default destination for in-transit shipments. The primary key is SHIPMENT_LINE_ID.

RCV_TRANSACTIONS
This table stores historical information about receiving transactions that you have performed. When you enter a receiving transaction and the receiving transaction processor processes your transaction, the transaction is recorded in this table.
Once a row has been inserted into this table, it will never be updated. When you correct a transaction, the net transaction quantity is maintained in RCV_SUPPLY. The original transaction does not get updated. You can only delete rows from this table using the Purge feature of Oracle Purchasing. The primary key is TRANSACTION_ID.

PO_RELEASES_ALL
This table contains information about blanket and planned purchase order releases. You need one row for each release you issue for a blanket or planned purchase order. Each row includes the buyer, date, release status, and release number. Each release must have at least one purchase order shipment (PO_LINE_LOCATIONS_ALL). The primary key is PO_RELEASE_ID.

AP_INVOICES_ALL
This table contains records for supplier invoices and has one row for each invoice.
To pass Invoice Validation, the INVOICE_AMOUNT in the AP_INVOICES_ALL table must equal the sum of the AMOUNT columns in the AP_DISTRIBUTIONS_ALL table. The primary key is INVOICE_ID.

AP_INVOICE_DISTRIBUTIONS_ALL
This table holds the distribution line information.
There is a row for each invoice distribution. If matching is used, distribution information is copied from PO_DISTRIBUTIONS_ALL during the matching process.

AP_PAYMENT_SCHEDULES_ALL
This table contains information about scheduled payments for an invoice.
Oracle Payables uses this information to determine when to make payments on an invoice and how much to pay in an automatic payment batch.

AP_HOLDS_ALL
This table contains a record for each hold placed on an invoice.
An invoice might have multiple records in this table.
An invoice cannot be paid until all holds placed on it have been released.

AP_CHECKS_ALL
This table stores information about payments issued to suppliers.
Each row includes the supplier name, address, and bank account name for auditing purposes, in case any of them change after you make the payment.
If the payment is electronic, the supplier bank account information is stored in the payment record.

AP_INVOICE_PAYMENTS_ALL
This table provides the link between a payment (CHECK_ID) and the invoice(s) paid by that payment.
This table contains records of invoice payments that you make to suppliers. Oracle Payables updates this table when you confirm an automatic payment batch, enter a manual payment, or process a Quick Payment. This table contains one row for each payment made for each invoice.
Void payments are also entered into this table as a negative record of the original payment line.

AP_BANK_ACCOUNTS_ALL
This table stores information about your bank accounts and your suppliers’ and customers’ bank accounts. This table contains one row for every bank account, whether it is an internal (supplier) or external (customer) account.

AP_BANK_BRANCHES
This table stores information about the bank branches and details about the branches.



Ur's
Amar Alam

Types of Invoices in Oracle Payables

1 comments
Types of Invoices in AP:

The different types of invoices available in Payables are:

1. Standard Invoices: Standard invoices are the invoices issued by a supplier to the buyer, representing the amount due for the products or services the supplier has provided to the buyer.

Standard invoices can be either matched to a purchase order or not matched.

A standard invoice must be positive amount.

2. Mixed Invoices: Mixed invoices are the invoices which can have either positive or negative amounts and can be matched to both purchase orders and invoices.

For example, if there is a mixed invoice for $-1000, you can either match it to an invoice with $-1000 or to a purchase order with an amount $1000.

3. Credit Memo: Credit memo is an invoice raised by the supplier to the buyer with negative amount. It reduces the supplier balance and reduces the liability.

For example the customer has returned some of the goods that he purchased, the supplier sends a credit memo to the buyer to adjust the balance.

4. Debit Memo: Debit memo is an invoice raised by the customer to supplier with negative amount.

The functionality of Debit Memo is same as Credit Memo. Both are to reduce the liability.

The purpose of Debit Memos is to record a credit for a supplier who does not send you a credit memo.

Unlike in AR, both Credit memo and Debit memo are with negative signs in Payables.

5. Prepayment: Prepayments are the invoices raised to record advance payments to a supplier or employee.

6. Expense Reports: Expense reports are the invoices that represent amount due to an employee for all his business related expenses.

7. Retainage Release Invoices: Retainage release is the act of releasing, or paying, that portion of a payment that was withheld until a substantial portion or all of the service procurement work is completed. The amounts retained during the life of the contract must be released and paid to the supplier or sub-contractor once all or a substantial portion of the work is completed.

Oracle Payables uses the Retainage Release Request to create a type of invoice called Retainage Release. A retainage release invoice has lines, which are copied from the original standard progress invoices, which show an amount left to be released.

Retainage release invoices can only be entered manually in the Invoice Workbench window.


8. Withholding Tax:  After you apply withholding tax to an invoice, you can optionally create invoices to remit withheld tax to the tax authority.
                         
Payables can automatically create withholding tax invoices, or you can perform this
task manually. If you choose to automatically create withholding tax invoices, you must choose whether to do this during Invoice Validation or during payment processing.


9. PO Price Adjustment Invoices:  PO Price Adjustment Invoices are used for recording the difference in price between the original invoice and the new purchase order price.

For example, If a supplier sends an invoice for a change in unit price for an invoice you have matched to a purchase order, PO Price Adjustment Invoices can be used to adjust the invoiced unit price of previously matched purchase order shipments or distributions without adjusting the quantity billed.


PO price adjustment invoices can be matched to both purchase orders and invoices.

10. Quick invoices: Used for quick, high-volume invoice entry for invoices that do not require extensive validation and defaults. After entry, you import these into the Payables system. Validation and defaulting occur during import


Ur's
Amar Alam

Thursday, 4 July 2013

Accounts Payable Interview Questions In R12

1 comments
1.Explain about Accounts Payable. 
Ans)The Accounts Payable application component records and manages accounting data for all
vendors. It is also an integral part of the purchasing system: Deliveries and invoices are
managed according to vendors. The system automatically triggers postings in response to the
operative transactions. In the same way, the system supplies the Cash Management application
component with figures from invoices in order to optimize liquidity planning.


2.What is the meaning of invoice?
Ans)An invoice or bill is a commercial document issued by a seller to the buyer, indicating the products, quantities, and agreed prices for products or services the seller has provided the buyer. An invoice indicates the buyer must pay the seller, according to the payment terms.

In the rental industry, an invoice must include a specific reference to the duration of the time being billed, so rather than quantity, price and discount the invoicing amount is based on quantity, price, discount and duration. Generally speaking each line of a rental invoice will refer to the actual hours, days, weeks, months etc being billed.


3) Can you give a sample Process Flow for Procure to Pay Cycle?

Ans) Process flow for Procure to pay will go through two departments
(Commercial & Finance)
Procure - Commercial Department The following steps invovle to prcure any item
1. Received Requsition from concern Department
2. Request for Quotation from Suppliers at least three
3. Finalize the best Quotation by keeping in mind about our companies standard
4. Check the Budget for the same
5. Negociate with supplier for more economic pricing and finalize the payment terms
6. Process the PO and forward to the supplier to supply the goods and services

Pay Cycle - Finance Department 
The following steps need to be fulfil
1. Invoice should be match with PO
2. Invoice should has all the supporting documents such as PO copy,Delivery note duly signed by reciever (our staff who authorized to received goods / store keeper)
3. If the invoice is for services then it should be forwarded to the concern department head or project manager for his confirmation of work done and his approval
4. Even if it not the services invoice, it should forwarded to the concern person's approval who request the PO for the same
5. Finance can reject the invoice if it is not budgeted and ask for the reasons.
6. After receiving all the confirmation and approvals from the concern department heads the invoice will be update in to the accounting system first in order to avoid any duplication of Invoice and PO (it shown on accounting package if the invoice is duplicate if not, altelast it tells you if the PO already used or cancel)
7. Finance approved the invoice and process the payment base on payment terms with the supplier.


4)What are the journals entries in Procure to Pay Cycle.
Ans)

Description                                                                             DR                                  CR

A) Po creation                                                                    No Entry                          No Entry

B)  While Receiving the goods                                       Material Receiving            Ap Accurval

C) While Inspection                                                        No Entry                            No Entry

D) While Trans ford the good to Inventory               Inv Org Material              Material Receiving
                                                                                     Purchase price Varience

F) While Po Is Matching to Invoices                         Ap Accurval                        Liability


G) While Making the Payment                                 Liability                               Cash Clearing


 H) Ofter Reconciliation                                           Cash Clearing                     Cash



 I) Final Entry                                                            Inv Org Material                Cash



5)What is the difference between EFT & Wire?
Ans)EFT and WIRE are the most popular form of electronic payment method. EFT stands for electronic fund transfer and it is one of the fastest mode of electronic payment after WIRE. EFT is a batch oriented mechanism for transfering funds from one bank to another because of which clearing & settlement takes around 2 to 4 days. On the other hand, WIRE is a RTGS i.e. real time gross settlement system of making the fund transfer on real time and gross basis. Clearing and settlement happens on the same day. WIRE is more expensive and faster than EFT.

6) WHAT IS MEANT BY DISTRIBUTION SETS:

 Ans)You can use a Distribution Set to automatically enter distributions for an invoice when you are not matching it to a purchase order. For example, you can create for an advertising supplier a Distribution Set that allocates advertising expense on an invoice to four advertising departments.
You can assign a default Distribution Set to a supplier site so Payables will use it for every invoice you enter for that supplier site. If you do not assign a default Distribution Set to a supplier site, you can always assign a Distribution Set to an invoice when you enter it.

Use Full Distribution Sets to create distributions with set percentage amounts, or use Skeleton Distribution Sets to create distributions with no set distribution amounts. For example, a Full Distribution Set for a rent invoice assigns 70% of the invoice amount to the Sales facility expense account and 30% to the Administration facility expense account. A Skeleton Distribution Set for the same invoice would create one distribution for the Sales facility expense account and one distribution for the Administration facility expense account, leaving the amounts zero. You could then enter amounts during invoice entry depending on variables such as that month's headcount for each group.

7)What is the meaning of GRN? 
Ans) Goods Receipt Note Means It Proves That Material Is Delivered At Stores Department. Grn Is The Base Document And Important Documents For Proof Of Receipt Of Material At Ware House.This Can Be Prepared By Stores Department And Approved By Plant Head. Grn Contains Ordered Qty,Received Qty And Accepted Qty. Bill Will Be Passed Based The Grn Note. Once The Grn Is Prepared Automatically Inventory Will Be Updated And Accordingly Payment Will Be Released To The Vendor.

GRN contains the following details.

1.Ordered quantity .
2.Received Quantity.
3.Defective quantity in received quantity .
4.Quality standards details.

8) How does the payment mechanism work?
Ans) The open items of an account can only be cleared once you post an identical offsetting amount to the account. In other words, the balance of the items assigned to each other must equal zero.During clearing, the system enters a clearing document number and the clearing date in these items. In this way, invoices in a vendor account are indicated as paid, and items in a bank clearing account are indicated as cleared.

You generally use the payment program to clear invoices. Manual clearing of open items is therefore not usually necessary. However, you will sometimes have to clear items manually if, for example, you receive a refund from your vendor or you have set up a direct debit procedure.


9) Difference between interface tables and base tables?
Ans)   The difference between the interface and base tables is as below

Interface table: is the table where the data gets validated before data get posted to the base tables. There are many interfaces which are seeded with Oracle. You can consider as the entry point of the data, and the interface checks the sanity of data.

Base tables: As told earlier once the data is validated will get updated in the base tables, and is considered as the data which is in the base table is accurate and used in many ways. (Reporting..etc..)


The base tables in AP are as follows:

1) ap_invoices_all

2) ap_invoice_payments_all

3) ap_invoice_distibutions_All

4) ap_payment_schdules

5) ap_payment_dustributions_all

6) ap_checks_all

7) ap_accounting_events_all

8) ap_bank_accounts_all

9) ap_bank_accounts_uses_all
 

10) What is the process of creating an Invoices and transferring it to GL?
Ans)
 1. create batch
2. create invoice
3. create distribution
4. validate the invoice
5. actions -à approve
6. if individual create accounting click ok
7. If batch go to batch create accounting.
8. Create accounting hits Payable Accounting(Transfer) ??Program which will create accounting.
9. Run Transfer to GL Concurrent Program
10. Journal Import
11. Post journals
12. Hits balances.

11) How do u Transfer from AP to GL? 
Ans)“Payables transfer to GL program” is used to transfer from AP to GL.




12) How many types of invoices are there in AP.
Ans)
1. Standarad invoice
2. Debit Memo
3. Credit Memo
4. Mixed Invoice
5. Retain age Invoice
6. Transportation invoice
7. Prepayment invoice
8. Expenses Report Invoice
9. Payment Request Invoice
10. Po default

13) How many types of purchase order types/agreements are there?

A) Standard Purchase Order: You generally create standard purchase orders for one-time purchase of various items. You create standard purchase orders when you know the details of the goods or services you require, estimated costs, quantities, delivery schedules, and accounting distributions. If you use encumbrance accounting, the purchase order may be encumbered since the required information is known

B) Planned PO : A planned purchase order is a long-term agreement committing to buy it
items or services from a single source. You must specify tentative delivery schedules and all details for goods or services that you want to buy, including charge account, quantities and estimated cost.
EX: Buying goods for Christmas from a specific dealer.

C) Contract PO : You create contract purchase agreement with your supplier to agree on specific terms and conditions without indicating the goods and services that you will be purchasing i.e. for $ amount you must supply this much quantity. You can later issue standard PO referencing your contracts and you can encumber these purchase orders if you use encumbrance accounting.

D) Blanket PO : You create blanket purchase agreements when you know the detail of goods or services you plan to buy from a specific supplier in a period , but you do not yet know the detail of your delivery schedules. You can use blanket purchase agreements to specify negotiated prices for your items before actually purchasing them.
A Blanket Purchase Agreement is a sort of contract between the you and ur supplier about the price at which you will purchase the items from the supplier in future. Here you enter the price of the item not the quantity of the items. When you create the release you enter the quantity of the items. The price is not updatable in the release. The quantity * price makes the Released Amount. Now suppose your contract with your supplier is such that you can only purchase the items worth a fixed amount against the contract.


14.Payment Method:


A funds disbursement payment method is a medium by which the first party payer, or deploying company, makes a payment to a third party payee, such as a supplier. You can use a payment method to pay one or more suppliers. Oracle Payments supports several payment methods for funds disbursement, including the following:

Check
Electronic
wire
Clearing
Check:

You can pay with a manual payment, a Quick payment, or in a payment batch.


Electronic:

Electronic An electronic funds transfer to the bank of a supplier.You create electronic payments either through the e- Commerce Gateway, or by delivering a payment batch file to your bank. For both methods, Payable's creates a file during payment batch creation. If you are using the e-Commerce Gateway to create the file of payments, an EDI translator is required to create the EDI Formatted file prior to delivering it to your bank.For electronic funds transfers, the file is formatted and delivered to your ap.out directory for delivery to your bank.

Wire:

Wire Funds transfer initiated be contacting the bank and requesting wire payment to the bank of a suplier.A payment method where you pay invoices outside of Payables by notifying your bank that you want to debit your account and credit your supplier’s account with appropriate funds. You provide your bank with your supplier’s bank information, and your bank sends you confirmation of your transaction. Your supplier’s bank sends your supplier confirmation of the payment. You then record the transaction manually.

Clearing:

Clearing Payment for invoices transferred from another entity within the company without creating a payment document.Payment method you use to account for inter company expenses when you do not actually disburse funds through banks. You do not generate a payment document with the Clearing payment method. When you enter the invoice, you enter Clearing for the payment method.You can record a Clearing payment using a Manual type payment only.

15.What id recurring invoices? What are AP setup steps? 
 
Ans) some times suppliers would not be sending any invoices. but still the payment have to made to home: rent, lease rentals. in this situation we have to create invoice every period wise. For that purpose we have to create one recurring invoice template. Template means with one master copy creating the multiple invoices is called template. Here we are creating the one invoice master copy is formally known as recurring invoice or recurring invoice template.

 SET UP:
 1)we have to create one special calendar
2)we have to create one full distribution set
3)we have to enter payment terms in the recurring invoice window
4)enter the template no, first invoice amount, special invoice amounts


Ur's
AmarAlam

Tuesday, 18 June 2013

What are Interface table in AP, AR,GL ?

2 comments
AP INTERFACE TABLE: 1). AP_INTERFACE_CONTROLS.
                    2). AP_INTERFACE_REJECTIONS
                    3). AP_INVOICE_INTERFACE
                    4). AP_INVOICE_LINES_INTERFACE.

AR INTERFACE TABLE: 1). AR_PAYMENTS_INTERFACE_ALL
                    2). AR_TAX_INTERFACE
                    3). HZ_PARTY_INTERFACE
                    4). HZ_PARTY_INTERFACE_ERRORS
                    5). RA_CUSTOMERS_INTERFACE_ALL
                    6). RA_INTERFACE_DISTRIBUTIONS_ALL
                    7). RA_INTERFACE_ERRORS_ALL
                    8). RA_INTERFACE_LINES_ALL
                    9). RA_INTERFACE_SALESCREDITS_ALL

GLINTERFACE TABLE:  1). GL_BUDGET_INTERFACE
                    2). GL_DAILY_RATES_INTERFACE
                    3). GL_IEA_INTERFACE
                    4). GL_interface
                    5). GL_INTERFACE_CONTROL
                    6). GL_INTERFACE_HISTORY


Ur's
AmarAlam

Tuesday, 4 June 2013

1 comments
-- Search Supplier Contact
SELECT DISTINCT asu.party_id, asu.segment1 Supp_Num
,asu.vendor_name
,hpc.party_name Contact_Name
,hpr.primary_phone_country_code cnt_cntry
,hpr.primary_phone_area_code cnt_area
,hpr.primary_phone_number cnt_phone
,assa.vendor_site_code
,assa.vendor_site_id
,asco.vendor_contact_id
FROM
 hz_relationships hr
,ap_suppliers asu
,ap_supplier_sites_all assa
,ap_supplier_contacts asco
,hz_org_contacts hoc
,hz_parties hpc
,hz_parties hpr
,hz_contact_points hpcp
WHERE hoc.party_relationship_id = hr.relationship_id
AND hr.subject_id = asu.party_id
AND hr.relationship_code = 'CONTACT'
AND hr.object_table_name = 'HZ_PARTIES'
AND asu.vendor_id = assa.vendor_id
AND hr.object_id = hpc.party_id
AND hr.party_id = hpr.party_id
AND asco.relationship_id  = hoc.party_relationship_id
AND assa.party_site_id = asco.org_party_site_id
AND hpr.party_type='PARTY_RELATIONSHIP'
AND hpr.party_id = hpcp.owner_table_id
AND hpcp.owner_table_name = 'HZ_PARTIES';


Ur's
AmarAlam

Thursday, 16 May 2013

AP Supplier Conversion using bulk collect

1 comments

Create table for supplier site

create table XXAP_SUPPLIER_SITE_STAGE
(
SUPPLIER_NAME                      VARCHAR2(100)
,SUPP_SITE_CODE                    VARCHAR2(100)
,ADDRESS1                          VARCHAR2(100)
,ADDRESS2                          VARCHAR2(100)
,CITY                              VARCHAR2(50)
,COUNTRY                           VARCHAR2(50)
,CURRENCY_CODE                     VARCHAR2(50)
,PHONE_NUMBER                      VARCHAR2(50)
,FAX                               VARCHAR2(50)
,EMAIL                             VARCHAR2(50)
,VENDOR_INTERFACE_ID               NUMBER(15)
,AREA_CODE                         VARCHAR2(15)
,FIRST_NAME_ALT                    VARCHAR2(200)
,LAST_NAME_ALT                     VARCHAR2(200)
,FIRST_NAME                        VARCHAR2(20)
,LAST_NAME                         VARCHAR2(20)
);


load data
infile '------------------------------------------------------'
insert into table XXAP_SUPPLIER_SITE_STAGE
fields terminated by ','
optionally enclosed by '"'
trailing nullcols
(SUPPLIER_NAME
   ,SUPP_SITE_CODE
   ,ADDRESS1
   ,ADDRESS2
   ,CITY
   ,COUNTRY
   ,CURRENCY_CODE
   ,PHONE_NUMBER
   ,FAX
   ,EMAIL
   ,VENDOR_INTERFACE_ID
   ,AREA_CODE
   ,FIRST_NAME_ALT
   ,LAST_NAME_ALT
   ,FIRST_NAME
   ,LAST_NAME)

Create a procedure for SUPPLIER LOAD:

CREATE OR REPLACE PROCEDURE XXAP_SUPPLIER_LOAD(x_errbuf OUT VARCHAR2,
                                                    x_retcode OUT NUMBER,
                                                    p_array_size IN PLS_INTEGER DEFAULT 300)
IS
TYPE test_array IS TABLE OF xxap_supplier_site_stage%ROWTYPE  INDEX BY BINARY_INTEGER;
      --v_vendor_interface_id                         test_array;
     -- v_supplier_name                                 test_array;
   v_vendors                              test_array ;
      v_vendor_type                       VARCHAR2(30);
      v_interface_id                         NUMBER;

  BEGIN
   SELECT *  BULK COLLECT INTO v_vendors FROM  xxap_supplier_site_stage ORDER BY supp_site_code;
  FOR i IN  1..v_vendors.COUNT

  LOOP
  SELECT ap_suppliers_int_s.NEXTVAL INTO v_interface_id  FROM dual;

  INSERT INTO ap_suppliers_int (vendor_interface_id,vendor_name) VALUES (v_interface_id ,INITCAP(v_vendors(i).supplier_name));
  END LOOP;
     
  END ;
/

create a procedure for SUPPLIERS CONTACT LOAD:

CREATE OR REPLACE PROCEDURE XXAP_SUPPLIERS_CONTACT_LOAD(x_errbuf OUT VARCHAR2, x_retcode OUT NUMBER)
IS
TYPE test_array IS TABLE OF xxap_supplier_site_stage%ROWTYPE  INDEX BY BINARY_INTEGER;
  v_vendor_id                          VARCHAR2(30);
  v_vendor_int_id                      VARCHAR2(30);
   v_vendors                              test_array ;
   --v_vendor_site_id                       number;


BEGIN
--open c1;
SELECT *  BULK COLLECT INTO v_vendors FROM  xxap_supplier_site_stage ORDER BY supp_site_code;
FOR i IN  1..v_vendors.COUNT
 LOOP
                    BEGIN
                    SELECT vendor_site_code
                    INTO   v_vendor_int_id
                                        FROM   ap_supplier_sites_int a
                    WHERE a. vendor_site_code = v_vendors(I).supp_site_code;
                              EXCEPTION WHEN OTHERS THEN
                        NULL;
                   END;
                   --SELECT ap_sup_site_contact_int_seq.NEXTVAL INTO v_vendor_site_id  FROM dual;
  INSERT INTO ap_sup_site_contact_int
(vendor_site_code
,first_name
,last_name
,area_code
,phone
,first_name_alt
,last_name_alt
,email_address
,fax
,org_id
--,vendor_id
--creation_date
)
VALUES
(
  v_vendor_int_id
  ,v_vendors(i).first_name                  
  ,v_vendors(i).last_name                    
  ,v_vendors(i).area_code                    
  ,v_vendors(i).phone_number                      
  ,v_vendors(i).first_name_alt                
  ,v_vendors(i).last_name_alt                
  ,v_vendors(i).email              
  ,v_vendors(i).fax
  ,104
  --,v_vendor_id  
  --SYSDATE
  );
  END LOOP;
  END;
/

create a procedure for SUPPLIER SITE LOAD:


CREATE OR REPLACE PROCEDURE XXAP_SUPPLIER_SITE_LOAD(x_errbuf OUT VARCHAR2, x_retcode OUT NUMBER)
IS
TYPE test_array IS TABLE OF xxap_supplier_site_stage%ROWTYPE  INDEX BY BINARY_INTEGER;
  v_vendor_id                          VARCHAR2(100);
  v_vendor_int_id                      VARCHAR2(100);
  v_vendors                            test_array ;

  --vv_vendor_interface_id                number;
 -- CURSOR C1
 -- IS
 -- SELECT *
 -- FROM    xxap_supplier_site_stage
 -- order by SUPP_SITE_CODE;
BEGIN
--open c1;
SELECT *  BULK COLLECT INTO v_vendors FROM  xxap_supplier_site_stage ORDER BY supp_site_code;
FOR i IN  1..v_vendors.COUNT
 LOOP
                   BEGIN
                    SELECT   vendor_id
                    INTO     v_vendor_id
                    FROM     po_vendors
                    WHERE    UPPER(vendor_name) = UPPER(v_vendors(i).supplier_name);
                   EXCEPTION WHEN OTHERS THEN
                         NULL;
               
                   END;
               
                  /* BEGIN
                    SELECT vendor_interface_id
                    INTO   v_vendor_int_id
                    FROM   ap_suppliers_int
                    WHERE  UPPER(vendor_name) = UPPER(v_vendors(I).supplier_name);
                    EXCEPTION WHEN OTHERS THEN
                        NULL;
                   END;*/

--v_vendor_id(C_REC):=vv_vendor_id;
--v_VENDOR_INT_ID(C_REC):= vv_VENDOR_INT_ID;

 --end loop;

                   --BEGIN
                  -- open C_REC;
                  -- FETCH  C_REC  BULK COLLECT INTO v_vendor_id,v_VENDOR_INT_ID;
                  -- for i in 1 .. v_VENDOR_INT_ID.count
                  -- LOOP
       -- SELECT ap_supplier_sites_int_s.NEXTVAL INTO v_vendor_int_id  FROM dual;

    INSERT INTO ap_supplier_sites_int
    (vendor_interface_id
    --,vendor_site_interface_id
    ,vendor_id
    ,vendor_site_code
    ,address_line1
    ,address_line2
    ,city
    ,country
    ,phone
    ,fax
    ,email_address
    ,invoice_currency_code
    ,payment_currency_code
    ,org_id
    ,pay_site_flag
    ,purchasing_site_flag
    )
    VALUES
    ( v_vendors(i).VENDOR_INTERFACE_ID                                                          
    --,ap_suppliers_int_s.nextval
    ,v_vendor_id
    ,v_vendors(i).supp_site_code
    ,v_vendors(i).address1
    ,v_vendors(i).address2
    ,v_vendors(i).city
    ,v_vendors(i).country
    ,SUBSTR(v_vendors(i).phone_number,1,15)
    ,SUBSTR(v_vendors(i).fax,1,15)
    ,v_vendors(i).email
    ,'USD'                                          --C_REC.CURRENCY_CODE
    ,'USD'                               --C_REC.CURRENCY_CODE
    ,104
    ,'Y'
    ,'Y'
    );
    END LOOP;
   -- close C1;
  COMMIT;
  EXCEPTION
  WHEN too_many_rows THEN
      v_vendor_id :=NULL;
  WHEN no_data_found THEN
    v_vendor_id :=NULL;
   -- END LOOP;
  --  END;
END;
/


Ur's
AmarAlam

Saturday, 4 May 2013

Account Payable (AP) Flow

1 comments

PO -> Receipt -> AP -? GL

Invoice ->; Payments->; Move Transactions from AP to GL In AP there are 2 Thumb rules.

• Without supplier there is no invoice.
• Without invoice there is no payment.

How many types of Invoices and What are Invoice Types:
1. Standard: We will make all the payments based on the standard invoice. It will have the information of Invoice Number, Invoice Date, Invoice Amount, and Currency.
2. Credit Memo: We will create credit memo invoice whenever supplier is giving the discount and it will be adjusted in standard invoice. It is always negative amount.
3. Debit Memo: Sometimes Company will deduct some amount from the invoice amount. This will be adjusted in standard invoice. It is always negative amount.
4. With-Holding TAX: This type of invoice will be created to make the invoice tax to the Govt. on behalf of supplier.
5. Pre-Payment: If we want to make some payments to the supplier in advance then we create the Pre-Payment invoice.
6. PO Default: If we want to make the invoice as per the PO then we create PO default. We will give Po Number. System will pick up the complete PO information.
7. Mixed: Includes both positive and negative amount. We can match this invoice with PO’s and other invoices.
8. Expense Report: This will be applicable for the employees who are working in the Company where Payable and internet expense and project account. Expense will be included.
9. Recurring invoice: We can enter invoice for periodic expense for which we may not receive. Invoice from supplier. To create a Recurring invoice first we will take template.
As per that we will create the invoice.Once the invoice is successfully completed, we can go for payments. It is of 3 types.

Manual Payment: Here we will be mentioning the Invoice Number, Bank Account, and Document Number, Payment Date and Currency.

Refund payment: This is used for Employee expenses and for adjusting the Supplier account,

Quick payment: In this payment, system will automatically generate checks. To print Checks there will be a concurrent program for each check format.Once the payment was done, we will move all the transactions to GL.

Wo is Suppliers:
Set up suppliers in the Suppliers window to record information about individuals and companies from whom you purchase goods and services. You can also enter employees whom you reimburse for expense reports. When you enter a supplier that does business from multiple locations, you store supplier information only once, and enter supplier sites for each location. You can designate supplier sites as pay sites, purchasing sites, RFQ only sites, or procurement card sites. For example, for a single supplier, you can buy from several different sites and send payments to several different sites. Most supplier information automatically defaults to all supplier sites to facilitate supplier site entry. However, you can override these defaults and have unique information for each site. The system uses information you enter for suppliers and supplier sites to enter default values when you later enter transactions for a supplier site. Most information you enter in the Suppliers window is used only to enter defaults in the Supplier Sites window. When the system enters that information in a later transaction, it only uses supplier site information as a default, even if the supplier site value is null and the supplier has a value. If you update information at the supplier level, existing supplier sites are not updated. When you enter a supplier, you can also record information for your own reference, such as names of contacts or the customer number your supplier has assigned to you.

What is Invoices:
Invoice Type (LOV): The type of invoice. Standard and Credit are the only invoice types you can enter in this window. If you do not enter a value for this field then a value will be assigned during import based on the amount of the invoice.

Standard: A trade invoice you receive from a supplier. The amount of a Standard invoice must be zero or greater.

Credit: Credit Memo. A negative amount invoice you receive from a supplier representing a credit for goods or services purchased. Note that in the Invoice Gateway you can match a credit memo to a purchase order to perform a price correction, but you cannot match a credit memo to an invoice. If you want to match to an invoice, then use the Invoice Workbench.

Debit Memo: Negative amount invoice created by you and sent to a supplier to notify the supplier of a credit you are recording. Usually send with a note explaining the debit memo. Purchase Order Matched Invoices: You can match Payables invoices to purchase orders to ensure that you pay only for the goods that you have ordered, or you can match to purchase order receipts to ensure that you pay only for goods that you have received. Purchase order matched invoices are invoices that you match to any of the following:
• Purchase order shipments
• Purchase order receipts
• Purchase order receipt lines
• Purchase order distributions

Foreign Currency Invoices: When you enter an invoice in a currency other than your functional currency, Payables uses an exchange rate to convert the invoice and invoice distributions into your functional currency for creating journal entries. You define your functional currency during setup for your set of books.
Mixed Invoices: Mixed Invoices are invoices or credit/debit memos for which you can perform both positive and negative matching to purchase orders and to other invoices. For example, you can enter an invoice for –$100 with Invoice Type Mixed. You can match to an invoice for $–200, and match to a purchase order for $100.

Prepayments: A prepayment is a type of invoice you enter to make an advance payment to a supplier or employee. For example, you need to pay a deposit on a lease, or pay an employee an advance for travel expenses. You can later apply the prepayment to one or more invoices or expense reports you receive from the supplier or employee to offset the amount paid to them. The supplier might send an invoice that references a prepayment. The supplier has reduced the invoice amount by the amount of the prepayment and associated tax. You can use the Prepayment on Invoice feature to enter the invoice.
You can enter two types of prepayments:
Temporary prepayments can be applied to invoices or expense reports you receive. For example, you use a Temporary prepayment to pay a hotel a catering deposit. When the hotel’s invoice arrives, apply the prepayment to the invoice to reduce the invoice amount you pay.
Permanent prepayments cannot be applied to invoices. For example you use a Permanent prepayment to pay a lease deposit for which you do not expect to be invoiced.

What are types of Matching? 
2–way matching: The process of verifying that purchase order and invoice information matches within accepted tolerance levels. Payables use the following criteria to verify two–way matching: Invoice price <- billed="" order="" ordered="" p="" price="" quantity="">
3–way matching: The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Payables use the following criteria to verify three–way matching: Invoice price <- billed="" order="" ordered="" p="" price="" purchase="" quantity="" received.="">
4–way matching: The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Payables use the following criteria to verify four–way matching:
Invoice price  => Order price

Quantity billed => Quantity ordered

Quantity billed => Quantity received

Quantity billed= > Quantity accepted


What is FOB (Free On Board): The point or location where the ownership title of goods is transferred from the seller to the buyer. This indicates that delivery of a shipment will be made on board or into a carrier by the shipper without charge, and is usually followed by a shipping point or destination (e.g. ’FOB Our warehouse in New York’). The FOB code is currently available only for reference purposes. Revenue and cost recognition is not currently determined by the value entered in this field. (Receivables Lookup)

What is Purge : An Oracle Receivables Process, where you identify a group of records for Receivables to delete from the database. Receivables purge each record and its related records. Receivables maintain summary data for each record it purges.


Ur's
AmarAlam