Different Sources that can load data into Open invoice import interface tables
  1. Quick Invoices window
  2. Oracle e-Commerce Gateway
  3. Credit Card transaction data
  4. Property Manager
  5. The Oracle Assets Export Lease Payments to Payables process
  6. Oracle XML Gateway
  7. SQL*Loader OR BPEL Interfaces can load invoice information from Legacy Systems
  8.  Invoices that your suppliers entered and submitted online via Oracle iSupplier Portal
Interface Tables:
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
Base Tables:
                AP_INVOICES_ALL
                AP_INVOICE_LINES_ALL
                AP_INVOICE_DISTRIBUTIONS_ALL
                                     (&)
                Payment Tables
Basic Process:
                The Payables Open Interface program validates each record you select for import, and if the record contains valid data, then the program creates a Payables invoice with distributions and scheduled payments based on the invoice header and line information in the record.

Records in the AP_INVOICE_LINES_INTERFACE table create one or more invoice distributions. Note that one row may create more than one distribution. For example, if you enter a Tax line in this table and prorate it across three Item lines, during Open Interface Import the system will create three Tax invoice distributions based on the single Tax line in this table.

Create Accounting

1. What are the Subledger Accounting Setup and Usage FAQ’s?

This Document includes FAQs Customers found when setting up SLA, and issues found when transferring to General Ledger due to product usage:
– How to Transfer Accounting to General Ledger in Release 12
– How to Import and Create accounting definitions
– How to Transfer Invoices with Rules to General Ledger
See Note 559064.1 for more information.

2. What are the FAQ’s for the R12 SLA Pre-Upgrade Process?

1. What is the function of the R12 SLA (Subledger Accounting) Pre-Upgrade program?
2. When and how do I run the R12 SLA Pre-Upgrade program?
3. What table is updated by the R12 Pre-Upgrade program?
4. What are the different status codes in the GL_PERIOD STATUSES table?
5. What criterion does the R12 Pre-Upgrade Program follow?
6. Where can I find the documentation for the R12 Pre-Upgrade Program?
7. What are the Application IDs that are considered by the R12 Pre-Upgrade program?
8. Once I have run the Pre-Upgrade program, can I re-run it with a different set of dates?
9. Where can I find information on the GL_PERIOD_STATUSES table?
10. How do I upgrade the accounting transactions after I have completed the R12 Upgrade?
For answers to these questions and more information, see Note 604893.1.

3. How do you Run the Transaction Objects Diagnostics Program?

The Transaction Objects Diagnostics program basically depends on the Accounting Program for parameter values. Below are the steps to be followed to submit this program:
a. (N) System Administrator Responsibility>Profile>System
Set the Profile, SLA: Enable Diagnostics to Yes at user level.
b. (N) Payables Responsibility>Other>Requests>Run
Submit the Create Accounting program so as to pick some transactions or the problem transactions for accounting.
c. After the Create Accounting program completes, you can run the Transaction Objects Diagnostics program for the Invoice/Payment. Alternatively, you can run this program for the Accounting Program Request ID.
See Note 558196.1 for more information.

4. What are the differences from the Subledger Accounting Methods, Standard Accrual Method and China Standard Accrual?

1. The China Standard Accrual SLAM (JA_CN_STANDARD_ACCRUAL) only has Application Accounting definitions defined for the Payables and Loans applications.
2. The China Standard Accrual SLAM (JA_CN_STANDARD_ACCRUAL) supports Project Number supporting reference on journal lines/headers to meet China localization requirement.
See Note 602109.1 for more information.

5. How to Create A Manual Subledger Journal Entry

Manual entries are adjustments. If the adjustments are due to specific subledger activity such as Payables, then you may want to enter an SLA manual entry instead of a GL entry.
Entries recorded in SLA are tied to the subledger source and therefore provided more accurate subledger accounting reporting.
Enter account, debit, and credit amounts, and accounting class.
Optionally enter third party information, description, and currency details for each line of the subledger journal entry.
View the total accounted amounts of all subledger journal entry lines in the ledger currency.
Navigation: Accounting > Subledger Accounting > Journal Entries
There you can see Create Journal Entry button at the left side after the Advanced Search block.
See Note 452748.1 for more information.

6. How to Correct Invalid Accounts Reported by the Create Accounting Process in R12 Payables

The Update Accounting Entries form was available in earlier releases of R11i to allow update/correction of invalid accounts created by the Payables accounting process. The R11i Update Accounting Entries form is phased out in 11.5.10 and is not available in R12. In R11i version 11.5.10, accounting is not created with invalid accounts; instead the accounting is reported in error and rolled back. The users are required to fix the invalid account referenced in the transaction data at the transaction level. R12 has similar functionality, if an account is invalid, the accounting is created with a status = Invalid. When accounting is created with a status = Invalid due to invalid accounts, the user should correct the transaction data or rule referencing the invalid account and then run the Create Accounting process again. Accounting with status = Invalid and Draft can be recreated each time the Create Accounting process is run. You can modify transaction data and rules to correct and change the accounting until you see accounting status = Final.
See Note 459274.1 for more information.

7. How to Make the ‘About This Page Link’ or ‘Errors Details Link’ Available on R12 OAF Pages

To help diagnose errors in detail or see the About this Page information on an R12 OAF page, set the FND: Diagnostics profile to ‘Yes’ at the site level. The profile controls the display of the ‘About this page’ link. Setting the profile to ‘Yes’ also ensures that a detailed error stack can be viewed to help diagnose unhandled exceptions. When this is set to ‘No’, a simple error message asking the user to contact the System Administrator is shown; the detailed error stack is not accessible.
1. Navigate: System Administrator > Profiles > System
2. Query Profile Name = FND: Diagnostics and set it to ‘Yes’ at the site level.
3. Log out of the application and log back in.
4. Verify the ‘About this Page’ link is now available on R12 OAF pages.
5. Verify the ‘errors detail’ link is now available on R12 OAF page exception messages.
See Note 454759.1 for more information.

GL Transfer

1. SLA: How to Troubleshoot AP TO GL Reconciliation

The purpose of this AP-GL Reconciliation Troubleshooting Guide is to assist the reader with reconciliation issues. In the simplest terms, AP-GL reconciliation means tallying the amounts in Accounts Payable (i.e., AP) for a CCID/Supplier and reconciling it to the figures in the General Ledger (GL).
See Note 605707.1 for more information.

2. How to Setup Transfer to GL in Detail or Summary

Payables Manager responsibility has setup access to subledger options:
Setup #1
1) On the Navigator page, hit CTRL L to get list of forms
2) Select > Accounting Setup Manager Main Page
3) Find the ledger and click Go
4) Click Update Accounting Options
5) Scroll a little down to Primary Ledger heading section
6) Subledger Accounting Options click UPDATE
7) Click Next to find Payables
8) Click Update Accounting Options
9) General Ledger Journal Entry Summarization setup No Summarization
10) Click Apply when done
Setup #2
11) On the Navigator page, Setup > Accounting Setups > Accounting Methods Builder > Journal Entry Setups > Journal Line Type
12) Define how each line type will be transferred to the GL
13) Log out and back into applications
14) Test the Transfer to GL
See Note 564706.1 for more information.

Period Close

1. How to Run the Unaccounted Transactions Sweep Program

See Note 560378.1 for instructions on how to run the Unaccounted Transactions Sweep Program. The information presented is complementary to the Oracle Payables User’s Guide Release 12, Part No. B25454-04.

2. How to Troubleshoot Closing Periods in Payables

A period cannot be closed unless the following criteria is met for ALL operating units assigned to a ledger:
•All payment batches must be confirmed
•All transactions must be accounted
•All accounting entries must be transferred to general ledger
•All future dated payments which have reached maturity in the accounting period must have their status updated to negotiable and be accounted
See Note 437422.1 for steps.

Trial Balance Report

1. How to Run the Accounts Payable Trial Balance Report in R12

Report Definition is required to run the Accounts Payable Trial Balance in R12.
If upgraded from R11i, Report Definitions should have been defined during the upgrade with the following name scheme: Liabilities Payables, i.e. Liabilities Payables, Vision Operations (USA)
If new install of R12, Navigate to: Payables Responsibility > Setup > Accounting Setups> Open Account Balances Listing Definitions
Review the Oracle Subledger Accounting Implementation Guide section on “Creating Open Account Balances Listing Definitions” for instructions on how to setup a new report definition.
See Note 554785.1 for more information.

2. How to Make the R12 Accounts Payable Trial Balance Report Show Detail or Summary Output

The R12 Accounts Payable Trial Balance has 4 templates available that control the output that is
displayed. The four templates available are:
Accounts Payable Trial Balance – Group by Account, Summary
Accounts Payable Trial Balance – Group by Account, Detail
Accounts Payable Trial Balance – Group by Third Party, Summary
Accounts Payable Trial Balance – Group by Third Party, Detail
Do the following to change the template that is used when the report is submitted:
1. Navigate: Payables Responsibility>Other>Request>Run
2. Select the Accounts Payable Trial Balance
3. Enter all of the parameters for the report. DO NOT SUBMIT THE REPORT.
4. Click on the Options button in the Upon Completion section of the Submit Request screen.
5. Select the desired template name.
6. Submit the Trial balance.
Do the following to change the default template used when the report is submitted:
1. Navigate: System Administration Responsibility>Concurrent>Programs
2. Search for:
Application = Payables
Program = Accounts Payable Trial Balance
Click on Go
3. Click on Update for the Accounts Payable Trial Balance program
4. Select the Onsite Setting tab
5. Select the default template from the Template dropdown in the General section.
6. Click on Apply to save the changes.
See Note 444044.1 for more information.

3. How to Have a Text Output for the Accounts Payable Trial Balance

In the Concurrent programs form for APTBRPT program check that ‘Output Format’ is XML.
In submit request form, select Output button in upon completion region, under layout region, choose a format like PDF or RTF.
For more information, see Note 554060.1.

4. How to Create R12 XML Report Output Formatted in Excel Instead of PDF

Do the following to change the Output Format that is created when the report is submitted:
1. Navigate: Payables Responsibility > Other > Request > Run
2. Select the report with XML output i.e. Payables Posted Invoice Register, Create Accounting Process, Accounts Payable Trial Balance, etc…
3. Enter all of the parameters for the report. DO NOT SUBMIT THE REPORT.
4. Click on the Options button in the Upon Completion section of the Submit Request screen.
5. Change the Format from PDF to Excel
6. Submit the report.
Note: XML reports should still be set to create XML output in the Concurrent Program Define form i.e. System Administrator > Concurrent > Program > Define > Set Output set to XML. And review Note 178133.1 “Setting up Word or Excel as a Viewer Option:” to make sure the Viewer Options and System Profile Options are set correctly to view Excel output.
See Note 568031.1 for more information.

5. How to Have a Text Output for the Accounts Payable Trial Balance

In the Concurrent programs form for APTBRPT program, ensure the ‘Output Format’ is XML.
In the submit request form, select the Output button in completion region, under layout region, choose a format like PDF or RTF.
See Note 554060.1 for more information.

6. How to Apply Journal Line Definitions Rules to the Manual Journal Entries

Is it possible to add the seeded Oracle Manual event class to an Application Accounting Definition? This would allow the users to define rules to be applied to manual journal entries in the subledger.
The answer is no. Manual SLA journal does not use rules. In R12, rules do not apply to manual journal entries in the subledger.
Whatever line type/account you enter, the system will take it and create an entry. The System will not consider rules for Manual Journal Entries.
See Note 452739.1 for more information.

ATTENTION: Oracle Payables Community Join our growing Payables Community and learn from your peers and Oracle on how to address your unique issues in AP.

IMPORTANT If you did not find the information you were searching for, please review the following Payables documents:
Note 578232.1 R12 Proactive Intelligence Center: Oracle Payables
Note 396084.1 Oracle Payables Documentation Resources, R12
Note 562887.1 R12 Helpful Tips for a Successful R12 Oracle Payables Implementation
Note 557869.1 EBS R12 Oracle Financials Critical Patches
Note 405627.1 Oracle Payables Release 12 Known Issues
Additional R12 documents:
Note 580299.1 R12 Best Practices for Adopting Oracle E-Business Suite
Note 461705.1 EBusiness R12 Upgrade Guide
Note 602615.1 How to Locate the Latest R12 Product-Specific Information using New MetaLink Features

References

NOTE:437422.1– R12 Troubleshooting Period Close in Payables
NOTE:444044.1– How do you make the R12 Accounts Payable Trial Balance Report show Detail or Summary output?
NOTE:452739.1– R12: How to Apply Journal Line Definitions Rules to the Manual Journal Entries
NOTE:454759.1– How to make the About this Page Link or Errors Details link available on R12 OAF pages
NOTE:458371.1– R12: How to Get the R12 Trace and FND Debug File / FND Log for Payables Processes
NOTE:459274.1– How do you correct invalid accounts reported by the Create Accounting process in R12 Payables?
NOTE:554060.1– R12: How to Have a Text Output for the Accounts Payable Trial Balance
NOTE:554785.1– How do you run the Accounts Payable Trial Balance report in R12?
NOTE:560378.1– Unaccounted Transactions Sweep Program
NOTE:564706.1– R12: How to Setup Transfer to GL in Detail or Summary
NOTE:568031.1– How to Create R12 XML Report Output Formatted in Excel Instead of PDF
NOTE:605707.1– SLA: A TECHNICAL PERSPECTIVE OF THE AP TO GL RECONCILIATION 
Applies to:
Oracle Cost Management – Version: 11.5.10.0 to 12.1.3 – Release: 11.5 to 12.1
Information in this document applies to any platform.
Scripts to Re-open an Inventory Accounting Period that has accidentally been closed.
Goal
If an Inventory Accounting Period has been closed prematurely by accident the following scripts can be used to re-open the accounting period if the corresponding GL period is open.  Re-Opening a closed period will allow transactions to be process for that period.
The re-opening of a closed period should not be used to back date transactions, the system allow back dated transactions but this may cause discrepancies between inventory and GL. Any discrepancies caused by back dated transactions are not supported by Oracle and would have to be resolved with a manual adjustment to the General Ledger.
Solution
DISCLAIMER: THE RE-OPENING OF A CLOSED INVENTORY PERIOD COULD POTENTIALLY CAUSE DATA CORRUPTION AND ANY DATA CORRUPTION CAUSED BY RE-OPENING A CLOSED INVENTORY PERIOD WILL BE THE RESPONSIBILITY OF THE CUSTOMER AND NO DATA FIX WILL BE PROVIDED FOR ANY DATA CORRUPTION THAT HAS BEEN CAUSED BY RE-OPENING A CLOSED PERIOD.
TEST THOROUGHLY ALL SCRIPTS ON A NON-PRODUCTION INSTANCE, FIRST BACKING UP ALL TABLE DATA PRIOR TO IMPLEMENTING IN PRODUCTION.
IF THERE IS CONCERN THAT RE-OPENING A CLOSED PERIOD MAY CAUSE DATA CORRUPTION PLEASE OPEN AN SR WITH ORACLE SUPPORT PRIOR TO RE-OPENING A CLOSED PERIOD.
— A script to list all inventory periods for a specific organization
— A script to reopen closed inventory accounting periods in 11.5.10
— The script will reopen all inventory periods for the specified
— Delete scripts to remove the rows created during the period close process to prevent duplicate rows
— organization starting from the specified accounting period.
— The organization_id can be obtained from the MTL_PARAMETERS table.
— The acct_period_id can be obtained from the ORG_ACCT_PERIODS table. 
   
   
   

SELECT acct_period_id period, open_flag, period_name name, 
      period_start_date, schedule_close_date, period_close_date 
      FROM  org_acct_periods 
      WHERE organization_id = &org_id 
      order by 1,2;

UPDATE org_acct_periods
SET open_flag = ‘Y’,
period_close_date = NULL,
summarized_flag = ‘N’
WHERE organization_id = &&org_id
AND acct_period_id >= &&acct_period_id;

DELETE mtl_period_summary
WHERE organization_id = &org_id
AND acct_period_id >= &acct_period_id;

DELETE mtl_period_cg_summary
WHERE organization_id = &org_id
AND acct_period_id >= &acct_period_id;

DELETE mtl_per_close_dtls
WHERE organization_id = &org_id
AND acct_period_id >= &acct_period_id;

DELETE cst_period_close_summary
WHERE organization_id = &org_id
AND acct_period_id >= &acct_period_id; 

commit

In this post, I tried to explain the required and optional columns in the payables invoice import tables for importing PO Matched Invoices.

 Table:  AP_INVOICE_INTERFACE
  Required Columns

Column Name
Validation
INVOICE_ID                            
Populated from AP_INVOICES_INTERFACE_S.NEXTVAL
INVOICE_NUM                           
Must be unique to the supplier
PO_NUMBER
An approved, not cancelled, not closed or final closed PO
VENDOR_ID or VENDOR_NUM or VENDOR_NAME
An active vendor. Validated against PO_VENDORS
VENDOR_SITE_ID or VENDOR_SITE_CODE
An active pay site. Validated against PO_VENDOR_SITES
INVOICE_AMOUNT                        
Positive amount for ‘STANDARD’ type, Negative amount for ‘CREDIT’ type
ORG_ID                                
Required in Multi-Org Environment. Validated against AP_SYSTEM_PARAMETERS.ORG_ID
SOURCE                                
Must be in
SELECT lookup_code
  FROM ap_lookup_codes
 WHERE lookup_type = ‘SOURCE’;
    
 
Optional Columns
    Column Name
Validation
INVOICE_DATE
Defaulted to SYSDATE
INVOICE_TYPE_LOOKUP_CODE              
Defaulted to ‘STANDARD’. It can be ‘STANDARD’ or ‘CREDIT’
INVOICE_CURRENCY_CODE                 
Defaulted from PO_VENDOR_SITES.
INVOICE_CURRENCY_CODE
EXCHANGE_RATE_TYPE                    
Defaulted from AP_SYSTEM_PARAMETERS.
DEFAULT_EXCHANGE_RATE_TYPE
TERMS_ID or TERMS_NAME                
Defaulted from
 PO_VENDOR_SITES.TERMS_ID
DOC_CATEGORY_CODE                      
Only populated if using automatic voucher number
PAYMENT_METHOD_LOOKUP_CODE
Defaulted from PO_VENDOR_SITES
.PAYMENT_METHOD_LOOKUP_CODE
PAY_GROUP_LOOKUP_CODE
Defaulted from PO_VENDOR_SITES.
PAY_GROUP_LOOKUP_CODE
ACCTS_PAY_CODE_COMBINATION_ID
Defaulted from PO_VENDOR_SITES.
ACCTS_PAY_CODE_COMBINAITON_ID
GROUP_ID
Group identifier. Suggest to use it
STATUS
DO NOT POPULATE IT


Table:  AP_INVOICE_LINES_INTERFACE
 Required Columns 
Column Name
Validation
INVOICE_ID                            
Populated from AP_INVOICES_INTERFACE.INVOICE_ID
INVOICE_LINE_ID                       
Populated from AP_INVOICE_LINES_INTERFACE_S.
NEXTVAL
LINE_NUMBER        
A unique number to the invoice
TAX_CODE or TAX_CODE_ID
Validated against AP_TAX_CODES_ALL
LINE_TYPE_LOOKUP_CODE                 
‘ITEM’
AMOUNT                              
Should be QUANTITY_INVOICED * UNIT_PRICE
If MATCH_OPTION is ‘P’, then populate
RELEASE_NUM or PO_RELEASE_ID              
For Blanket Release only,
 validated against PO_RELEASES_ALL
PO_NUMBER or PO_HEADER_ID
Validated against PO_HEADER_ALL
PO_LINE_NUMBER or PO_LINE_ID
Validated against PO_LINES_ALL
PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID    
Validated against PO_LINE_LOCATIONS_ALL
If MATCH_OPTION is ‘R’, then populate
RECEIPT_NUMBER                            
Validated against RCV_SHIPMENT_HEADERS.RECEIPT_NUM
RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID
Validated against RCV_TRANSACTIONS
Optional Columns
Column Name
Validation
QUANTITY_INVOICED
Populated if different from PO shipment
UNIT_PRICE
Populated if different from PO shipment
MATCH_OPTION
‘P’ or ‘R’ or Defaulted from PO_VENDOR_SITES.MATCH_OPTION
ACCOUNTING_DATE
Defaulted from INVOICE_DATE or SYSDATE
FINAL_MATCH_FLAG
Populated ‘Y’ if it is final matching
INVENTORY_ITEM_ID
Validated against PO_LINES.INVENTORY_ITEM_ID
INVENTORY_DESCRIPTION
Validated against PO_LINES.INVENTORY_ITEM_DESCRIPTION
SHIP_TO_LOCATION_CODE
Populated if different from PO shipment
PRICE_CORRECTION_FLAG
Populated ‘Y’ if it is price correction

Oracle Purchasing Tables

po_requisition_headers_all
po_requisition_lines_all
po_req_distributions_all
po_headers_all
po_lines_all
po_distributions_all
rcv_transactions
po_requisitions_interface_all
po_reschedule_interface
po_headers_interface
po_lines_interface
po_distributions_interface
 
po_vendors
po_vendor_sites_all
po_vendor_contacts

Understanding the Matching Tables

Payables uses several of Oracle Purchasing tables for matching. To implement matching in Payables, you need to load these tables with the data from your non-Oracle purchasing application.

    • PO_HEADERS
    • PO_LINES
    • PO_LINE_LOCATIONS
    • PO_DISTRIBUTIONS
    • PO_DISTRIBUTIONS_AP_V (view of PO_DISTRIBUTIONS)
    • PO_RELEASES (Blanket Purchase Orders)
    • PO_LOOKUP_CODES

AutoInstall automatically installs these and other necessary Oracle Purchasing application tables when you install Payables.

PO_HEADERS

Each record in this table represents a purchase order, which is an order for goods or services from a single supplier. Each purchase order may have multiple lines (PO_LINES). In addition, each blanket purchase order may have multiple blanket releases (PO_RELEASES), which release an amount from the blanket.

PO_LINES

Each record in this table represents a purchase order line, which identifies the items and unit price for the goods ordered on a purchase order. Each purchase order line may have multiple shipments (PO_LINE_LOCATIONS).

PO_LINE_LOCATIONS

Each record in this table represents a purchase order shipment, which identifies the quantity of an item shipped to a buyer location by the supplier. Each purchase order shipment may have multiple accounting distributions (PO_DISTRIBUTIONS).

PO_DISTRIBUTIONS/PO_DISTRIBUTIONS_AP_V

Each record in this table/view represents a purchase order distribution, which identifies the account charged for the items on a purchase order shipment.

PO_RELEASES

Each record in this table represents a blanket release for a purchase order. A blanket release may create multiple shipments.

AP_INVOICES/AP_INVOICE_DISTRIBUTIONS

Each purchase order shipment can be matched to multiple invoices (AP_INVOICES), and a single invoice may be matched to multiple purchase order shipments. When you match an invoice to a purchase order shipment, Payables creates an invoice distribution (AP_INVOICE_DISTRIBUTIONS) from each purchase order distribution on the shipment. When you match an invoice to a single purchase order distribution, Payables creates a single invoice distribution from the purchase order distribution.

Table Descriptions

The following section describes the tables and the columns that Payables supports for matching to purchase orders from your non-Oracle purchase system. We describe how the columns are used and, if a column is required, the values you must load to successfully perform matching. For a complete description of the tables, please consult the Payables Applications Technical Reference Manual.

Attention: You must populate all NOT NULL columns in the purchasing tables.

PO_HEADERS

AGENT_ID

Enter the ID for the agent who created the purchase order. This value is used by the following reports in Payables: Merge Suppliers, Matching Agent Notice and Receiving Hold Requestor Notice.

TYPE_LOOKUP_CODE

Enter BLANKET or STANDARD (Lookup Type: PO TYPE) to identify the type of purchase order.

TERMS_ID

Enter the ID for the payment terms of the purchase order. Payables uses this value during matching to warn you if the payment terms on the purchase order do not match the payment terms on the invoice being matched to the purchase order. If you choose to leave this column empty, Payables will not warn you if the purchase order and invoice payment terms differ.

FREIGHT_TERMS_LOOKUP_CODE

Enter a QuickCode (QuickCode Type: FREIGHT TERMS) to identify the freight terms for the purchase order. See: QuickCodes.

CURRENCY_CODE

Enter the currency code for the purchase order. You can obtain a list of valid codes from FND_CURRENCIES.CURRENCY_CODE. The currency code for the invoice you want to match to this purchase order must be the same as the code you enter here.

PO_RELEASES (Blanket releases)

PO_LINES

LINE_TYPE_ID

Enter the ID for the line type of the purchase order line. You can obtain a list of valid IDs from PO_LINE_TYPES.LINE_TYPE_ID.

ITEM_ID

Do not enter a value in this column. Payables does not allow you to record purchase order lines with Items unless you install Oracle Purchasing.

ITEM_DESCRIPTION

Enter a description for your purchase order line. You can use this column to record information about the item on the purchase order line. Payables displays this description in the Purchase Order Shipments zone during matching.

TYPE_1099

Enter the income tax type for the purchase order line, if the supplier for the purchase order is a 1099 supplier. Payables assigns this type as the default income tax type for each invoice distribution created by matching to this purchase order line. If you leave the column empty, Payables uses the income tax type for the supplier as the default. You can obtain a list of valid types from AP_INCOME_TAX_TYPES.INCOME_TAX_TYPE.

PO_LINE_LOCATIONS (PO Shipments)

QUANTITY

Enter the quantity of goods ordered for the purchase order shipment. Payables uses this amount to match against if you are using 2-way matching. Payables verifies that this quantity matches the invoice quantity within defined tolerance levels and places the invoice on hold if it doesn’t match. In addition, if the quantity of the invoice is greater than the shipment quantity, your Payables warns you during invoice entry that the match will result in an overbill.

QUANTITY_RECEIVED/QUANTITY_ACCEPTED

Enter the quantity of goods received/accepted if you are using 3-way/4-way matching. Payables verifies that the quantity matches the invoice quantity within defined tolerance levels and places the invoice on hold if it doesn’t match.

QUANTITY_BILLED

Do not enter a value in this column, unless you have already matched an invoice to this purchase order shipment. When a match successfully completes (invoice is approved), Payables updates this column with the quantity you specified during matching.

QUANTITY_CANCELLED

Only enter a value in this column if you have cancelled a portion of the purchase order shipment in your non-Oracle purchasing system. The amount you enter reduces the amount that Payables considers to be the outstanding quantity ordered. Payables displays a warning if you try to match to a shipment which has been cancelled. When you cancel a shipment, Oracle Purchasing sets the PO_LINE_LOCATIONS.QUANTITY_CANCELLED to:

    • QUANTITY – QUANTITY_RECEIVED if receipt is required
    • QUANTITY – QUANTITY_BILLED if receipt is not required.

Attention: Approval does all quantity checks assuming the QUANTITY is the actual QUANTITY minus the QUANTITY_CANCELLED.

UNIT_MEAS_LOOKUP_CODE

Payables displays this value in the matching zones, but does not validate the column. You can enter any value into this column; however, you should use the same value that you use in your non-Oracle purchasing system.

TAXABLE_FLAG

Enter Y or N to indicate the purchase order shipment is subject to tax. If you enter Y, enter a value in the TAX_NAME column. During Approval, Payables verifies that the tax name for the purchase order shipment matches the tax name on the invoice and places a Tax Difference hold on the invoice if the tax names don’t match.

TAX_NAME

Enter the tax name used to verify that the tax names on the invoice and purchase order shipment match. You do not need to enter a value if you enter N in the TAXABLE_FLAG column. You can obtain a list of valid tax names from AP_TAX_CODES.NAME.

TYPE_LOOKUP_CODE

Enter BLANKET, STANDARD, or SCHEDULED (Lookup Type: SHIPMENT TYPE) to identify the type of purchase order shipment.

CLOSED_CODE

Do not enter a value in this column if you want to match an invoice to this purchase order shipment. If you enter the values CLOSED, FINALLY CLOSED, or CLOSED FOR INVOICE in the column, Payables warns you that you are matching to a closed purchase order.

PO_DISTRIBUTIONS (Account distribution)

Payables uses a view (PO_DISTRIBUTIONS_AP_V) to this table to perform purchase order distribution matching.

SET_OF_BOOKS_ID

Enter the set of books ID for your purchase order distribution. The ID you enter must be for the set of books you define in the Set of Books window.

CODE_COMBINATION_ID

Enter the Accounting Flexfield ID for the expense account you want to charge for the goods on the purchase order distribution.

QUANTITY_ORDERED

Enter the amount of goods charged to the Accounting Flexfield for this purchase order distribution.

Attention: NOTE: Payables does not validate the following, but assumes it to be true:

Total of PO_DISTRIBUTIONS.QUANTITY_ORDERED for one PO_LINE_LOCATION_ID = PO_LINES_LOCATIONS.QUANTITY (for the same ID).

Payables sometimes prorates the PO_DISTRIBUTION.QUANTITY_ORDERED using the PO_LINES_LOCATIONS.QUANTITY as the total.

BUDGET_ACCOUNT_ID/ACCRUAL_ACCOUNT_ID/ VARIANCE_ACCOUNT_ID

Enter the same Accounting Flexfield ID you entered for the CODE_COMBINATION_ID. Payables allows you to record budget, accrual, and variance (price and exchange rate) amounts for your purchase order distributions, but requires you to charge these amounts to the same expense account for the distribution.

QUANTITY_BILLED

Do not enter a value in this column, unless you have already matched an invoice distribution to this purchase order distribution. When a match successfully completes (invoice is approved), Payables updates this column with the quantity you specified during matching.

QUANTITY_CANCELLED

Enter a value in this column only if you have cancelled a portion of the purchase order distribution in your non-Oracle purchasing system. The amount you enter reduces the amount that Payables considers to be the outstanding quantity ordered. Payables displays a warning if you try to match to a shipment which has been cancelled.

Attention: Approval does all quantity checks assuming the quantity for the distribution is QUANTITY_ORDERED minus QUANTITY_CANCELLED.

AMOUNT_BILLED

Do not enter a value in this column, unless you have already matched an invoice to this purchase order shipment. When a match successfully completes (invoice is approved), Payables updates this column with the amount of the quantity you specified during matching multiplied by the unit price.

Oracle Projects Columns

Enter project information from Oracle Projects if you want to associate the invoice distribution (created through matching) with a project in Oracle Projects. Payables transfers the information into the AP_INVOICE_DISTRIBUTIONS table and uses it to create the default Accounting Flexfield for the invoice distribution. 

Matching to Purchase Orders

Perform the following steps to match invoices to purchase order information from your non-Oracle purchasing system:

Create Flat File with Purchasing Information

To load invoice information into Payables via SQL*Loader, first create a program that produces a flat file containing the information from your non-Oracle purchasing system for the purchase orders you want to match to invoices.

Load Information into Purchasing Tables

Use SQL*Loader to load the required information into the purchasing tables. You will need to create a SQL*Loader control file to format the information you want to load. The file you write will vary greatly depending on the nature and format of the flat file you use. Your control file must populate the purchasing tables as indicated in the previous table descriptions. See also: SQL*Loader (ORACLE8 Server Utilities Guide).

Enter Invoices

You match invoices to purchase order shipments during invoice entry. This online function links an invoice in the database to one or more purchase order shipments you choose. You cannot pay or post an invoice until Approval approves the invoice. You can match any type of invoice to a purchase order, including credit and debit memos.

Match to Purchase Order Shipments and distributions

When you match during invoice entry, you indicate whether you want to match to the purchase order shipment or to specific invoice distributions. You then choose the shipment or distribution you want to match to, and the quantity and price you are matching. Then Payables performs the following for each matched shipment:

    • Update QUANTITY_BILLED and AMOUNT_BILLED in PO_DISTRIBUTIONS
    • Update QUANTITY_BILLED in PO_LINE_LOCATIONS
    • Create one or more AP_INVOICE_DISTRIBUTIONS which record the QUANTITY_INVOICED, UNIT_PRICE, and PO_DISTRIBUTION_ID, in addition to other payables information.

Match to Credit and Debit Memos

Payables lets you enter a credit or debit memo (with a negative amount) and match to a purchase order. You would enter a negative quantity in the Quantity Invoiced field in the Purchase Order Shipment Match zone, thereby matching this credit invoice to one or no purchase order shipment lines. Payables then decreases the quantity billed against the purchase order shipment line(s). When you match a credit invoice to a purchase order shipment line, Payables:

    • Reopens closed shipment lines (sets PO_LINE_LOCATIONS.CLOSED_CODE to NULL)
    • Updates PO_LINE_LOCATIONS.QUANTITY_BILLED
    • Updates PO_DISTRIBUTIONS.QUANTITY_BILLED

Attention: Payables does not update any receiving information. You must install Oracle Purchasing if you want to enter or update receiving information for a purchase order

Close a Purchase Order Shipment

Invoice entry closes a purchase order shipment (sets CLOSED_CODE in PO_LINE_LOCATIONS to ‘CLOSED’) when:

    • QUANTITY_BILLED equals or exceeds QUANTITY_ORDERED (two-way matching), or
    • QUANTITY_ORDERED is less than or equal to QUANTITY_RECEIVED and QUANTITY_RECEIVED is less than or equal to QUANTITY_BILLED

Final Close

Payables does not support finally closing a purchase order if you do not install Oracle Purchasing with Payables. Final close allows you to match an invoice to a purchase order and permanently close the purchase order when you approve the invoice. 

Online Review of Purchasing Information

Without an Oracle Purchasing application, Payables does not allow you to review purchasing information, such as purchase order header and line information, online in the Invoice Workbench.

Using Approval

Approval is the Payables feature that performs two-, three-, or four-way matching. An invoice must pass Approval before you can pay or post the invoice. Approval reviews each invoice and places one or more matching holds on the invoice if the invoice does not meet your matching criteria. It also releases any existing matching holds if you adjust your invoice or purchase order to meet your matching criteria and current information on order, receipt and acceptance prices and quantities. You must submit Approval for all invoices, not just matched invoices, since it also checks for distribution variances, tax variances, and exchange rate information. You can submit Approval online for an invoice or in batch for a group of invoices. See also: Approval.

2-way, 3-way, and 4-way Matching

When you match to a purchase order, Payables automatically checks that the total of PO_DISTRIBUTIONS.QUANTITY_ORDERED = AP_INVOICE_DISTRIBUTIONS.QUANTITY_INVOICED (2-way matching). Payables only checks QUANTITY_RECEIVED (3-way matching) if the RECEIPT_REQUIRED_FLAG is set to Y and only checks QUANTITY_ACCEPTED (4-way matching) if the INSPECTION_REQUIRED_FLAG is set to Y.

Tax Matching

Payables only checks for tax name matching if the Payables option Validate PO Tax Name is enabled and the invoice has distributions with tax names.

Matching Tolerance

You can define percentage and amount tolerances for Matching quantities and price. Payables places a matching hold on an invoice only if the invoice quantity or price is greater than the purchasing quantity or price by more than your tolerance.

Matching Holds

When you submit Approval, Payables places a matching hold on a matched invoice (by inserting one or more rows in AP_HOLDS, one row for each type of hold for each invoice distribution) if:

    • QUANTITY_BILLED > QUANTITY in PO_LINE_LOCATIONS (QTY ORD Hold)
    • UNIT_PRICE in AP_INVOICE_DISTRIBUTIONS > PRICE_OVERRIDE in PO_LINE_LOCATIONS (PRICE Hold)
    • QUANTITY_BILLED > QUANTITY_RECEIVED in PO_LINE_LOCATIONS (QTY REC Hold)
    • QUANTITY_BILLED > QUANTITY_ACCEPTED in PO_LINE_LOCATIONS (QUALITY Hold)
    • TAXABLE_FLAG = NO in PO_LINE_LOCATIONS, but there IS tax recorded on the invoice (TAX DIFFERENCE Hold)
    • TAX_NAME in PO_LINE_LOCATIONS is not equal to VAT_CODE in AP_INVOICE_DISTRIBUTIONS (TAX DIFFERENCE Hold)

Using Encumbrance Accounting with Purchasing

Payables supports using encumbrance accounting with a non-Oracle purchasing system. To use encumbrance accounting, however, you must initially record the encumbered amount for the purchase order to which you want to match an invoice. Then, when Approval approves the invoice, if there is a variance between the invoice and its matched purchase order within the tolerances you define, Payables automatically creates an encumbrance journal entry for the amount of the variance. Payables always creates encumbrance journal entries in detail.

Attention: Approval uses the Payables table, AP_TRANSFER_ENCUMBRANCE, if you enable encumbrance accounting. Payables never drops this table, but deletes the appropriate lines from this table at the beginning of the program each time you submit Approval.

With an Oracle Purchasing application installed, Payables allows you to record these variance encumbrance journal entries to a separate variance account. With a non-Oracle purchasing system, Payables requires you to record the variance amount to the same Accounting Flexfield as the expense Accounting Flexfield for the purchase order distribution.
When you post the invoice to your general ledger, Payables relieves both the original encumbrance journal entries that you created when you encumbered the purchase order and the encumbrance journal entries it automatically created for the variance. Payables then creates actual journal entries for your invoice transaction. Your variance encumbrance journal entries and your actual journal entries update your account balances only when you post the journal entries in your general ledger.

Budgetary Control

The budgetary control feature does not use purchasing information unless you install Oracle Purchasing.

Encumbrance Entries in Payables

If you enable Budgetary Control for a set of books in Oracle General Ledger, you can reserve funds, or encumber them, when you expect an expense so you can avoid overspending a budget and to predict cash outflow. If you enable the PO Encumbrance Financials option, Purchasing and Payables create encumbrances and unencumbrances against the budgets you define in General Ledger. The following equation always holds true:

      Funds Available = Budget – Actuals – Encumbrances

The encumbrances Purchasing and Payables create depends on whether the invoice is purchase order matched, and what accrual method you use in Purchasing:

    • Unmatched Invoice: If you enable the PO Encumbrance Financials option and you enter an unmatched invoice, Payables creates an encumbrance for the expense during Approval, and reverses this encumbrance during posting.
    • Matched Invoice, Receipt Accrual: If you use the On Receipt Accrual Method in Purchasing, Purchasing creates an encumbrance for the goods received at the time of receipt, then reverses that encumbrance when it records the actual expense at the time of delivery of goods. When the invoice is matched to a purchase order and approved in Payables, it is not necessary for Payables to record an encumbrance for the expense. However, Payables will create an encumbrance for an invoice price variance or exchange rate variance, if they exist. Payables does not currently create encumbrances for Quantity variances when you accrue on receipt.
    • Matched Invoice, Period End: If you use the Period End Accrual method for your expense items in Purchasing, Purchasing creates an encumbrance for the goods received at the time of delivery. When the invoice is matched to a purchase order and approved in Payables, it is not necessary for Payables to record an encumbrance for the expense. However, Payables will create an encumbrance for a quantity variance, invoice price variance, or exchange rate variance, if any exist.

Payables reverses all remaining encumbrances for an invoice during Posting, when it records the actual invoice expense. The chart below shows when Payables creates encumbrance entries under the two different Accrual Methods.

Encumbrance with Combined Basis Accounting

If you use the combined basis accounting method, Payables posts encumbrance entries to your primary, accrual set of books only.

Encumbrance with Cash Basis Accounting

If you use the cash basis accounting method, Payables relieves encumbrance entries when you post payments. Payables prorates your encumbrance reversal based on the amount of your invoice payment. 

Purging Purchasing Information

Payables does not allow you to purge purchasing information if you do not have an Oracle Purchasing application installed. When you match an invoice to a purchase order from a non-Oracle purchasing system, you will not be able to purge the invoice because Payables requires that all objects, including matched purchase orders, associated with an invoice must be purgeable before you can purge the invoice.