122 Aprg

Oracle® Payables
Reference Guide
Release 12.2
Part No. E48763-03
August 2016
Oracle Payables Reference Guide, Release 12.2
Part No. E48763-03
Copyright © 1998, 2016, Oracle and/or its affiliates. All rights reserved.
Primary Author: Sudha Seshadri
Contributing Author: Jayanta Bhowmik, Robert MacIsaac, Christine Monk, Carol-Ann Lapeyrouse,
Ramasubramanian Balasundaram, Mary Kalway, Brent Bosin, Melanie Featherstone, Manoj Swaminathan,
Ping Feng, Goutham Bellary, Biplob Ghose
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.
Contents
Send Us Your Comments
Preface
1 Expense Reports and Credit Cards

Payables Procurement Card Transactions Interface Table ......................................................1-1
A Payables Open Interface Tables

Payables Open Interface Tables............................................................................................... A-1
Understanding the Invoice Open Interface Tables.............................................................. A-2
Understanding the Suppliers Open Interface Tables........................................................... A-3
Payables Open Interface Table Descriptions....................................................................... A-5
Sequential Numbering During Import............................................................................ A-143
Account Overlay in Payables Open Interface Import...................................................... A-143
How the Quick Invoices Window Populates the Payables Open Interface Tables.......... A-145
B Purchase Order Matching Database Tables

Purchase Order Matching Database Tables............................................................................. B-1
Understanding the Matching Tables................................................................................... B-2
Table Descriptions............................................................................................................... B-3
Matching to Purchase Orders............................................................................................ B-13
Using Invoice Validation................................................................................................... B-15
Using Encumbrance Accounting with Purchasing............................................................ B-16
Purging Purchasing Information....................................................................................... B-17
iii
C Predefined Setup for Oracle Subledger Accounting
Data that Oracle Payables Predefines for Oracle Subledger Accounting............................... C-1
Index
iv
Send Us Your Comments
Oracle Payables Reference Guide, Release 12.2

Part No. E48763-03
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
v
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle Payables Reference Guide.
This guide assumes you have a working knowledge of the following:
• The principles and customary practices of your business area.
• Computer desktop application usage and terminology.
If you have never used Oracle E-Business Suite, we suggest you attend one or more of
the Oracle Applications training classes available through Oracle University.
See Related Information Sources on page viii for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.
Structure
1 Expense Reports and Credit Cards
A Payables Open Interface Tables
vii
B Purchase Order Matching Database Tables
C Predefined Setup for Oracle Subledger Accounting
Related Information Sources

This book is included in the Oracle E-Business Suite Documentation Library, which is
supplied in the Release 12.2 Media Pack. If this guide refers you to other Oracle
E-Business Suite documentation, use only the latest Release 12.2 versions of those
guides.
Online Documentation
All Oracle E-Business Suite documentation is available online (HTML or PDF).
• Online Help - Online help patches (HTML) are available on My Oracle Support.
• PDF Documentation - See the Oracle E-Business Suite Documentation Library for
current PDF documentation for your product with each release.
• Release Notes - For information about changes in this release, including new
features, known issues, and other details, see the release notes for the relevant
product, available on My Oracle Support.
• Oracle Electronic Technical Reference Manual - The Oracle Electronic Technical

Reference Manual (eTRM) contains database diagrams and a detailed description of
database tables, forms, reports, and programs for each Oracle E-Business Suite
product. This information helps you convert data from your existing applications
and integrate Oracle E-Business Suite data with non-Oracle applications, and write
custom reports for Oracle E-Business Suite products. The Oracle eTRM is available
on My Oracle Support.
Related Guides
You should have the following related books on hand. Depending on the requirements
of your particular installation, you may also need additional manuals or guides.
Oracle Alert User's Guide
This guide explains how to define periodic and event alerts to monitor the status of
your Oracle E-Business Suite data.
Oracle Application Framework Developer's Guide
This guide contains the coding standards followed by the Oracle E-Business Suite
development staff to produce applications built with Oracle Application Framework.
This guide is available in PDF format on My Oracle Support and as online
documentation in JDeveloper 10g with Oracle Application Extension.
Oracle Application Framework Personalization Guide
This guide covers the design-time and run-time aspects of personalizing applications
built with Oracle Application Framework.
viii
Oracle Fusion Middleware Adapter for Oracle Applications User's Guide (Oracle
Application Server Adapter for Oracle Applications User's Guide)
This guide covers the use of Adapter for Oracle Applications in developing integrations
between Oracle E-Business Suite and trading partners.
Please note that the user's guide can be found in the following documentation libraries:
• As part of the Oracle Fusion Middleware and SOA Suite in 11g, Oracle Fusion
Middleware Adapter for Oracle Applications User's Guide is available in the Oracle
Fusion Middleware 11g Documentation Library.
• As part of the Oracle Application Server in 10g, Oracle Application Server Adapter for
Oracle Applications User's Guide is available in the Oracle Application Server 10g
Documentation Library.
Oracle Diagnostics Framework User's Guide

This manual contains information on implementing and administering diagnostics tests
for Oracle E-Business Suite using the Oracle Diagnostics Framework.
Oracle E-Business Suite Concepts
This book is intended for all those planning to deploy Oracle E-Business Suite Release
12.2, or contemplating significant changes to a configuration. After describing the
Oracle E-Business Suite architecture and technology stack, it focuses on strategic topics,
giving a broad outline of the actions needed to achieve a particular goal, plus the
installation and configuration choices that may be available.
Oracle E-Business Suite CRM System Administrator's Guide
This manual describes how to implement the CRM Technology Foundation (JTT) and
use its System Administrator Console.
Oracle E-Business Suite Desktop Integration Framework Developer's Guide
Oracle E-Business Suite Desktop Integration Framework is a development tool that lets
you define custom integrators for use with Oracle Web Applications Desktop
Integrator. This guide describes how to define and manage integrators and all
associated supporting objects, as well as how to download and upload integrator
definitions.
Oracle E-Business Suite Developer's Guide
This guide contains the coding standards followed by the Oracle E-Business Suite
development staff. It describes the Oracle Application Object Library components
needed to implement the Oracle E-Business Suite user interface described in the Oracle
E-Business Suite User Interface Standards for Forms-Based Products. It provides information
to help you build your custom Oracle Forms Developer forms so that they integrate
with Oracle E-Business Suite. In addition, this guide has information for customizations
in features such as concurrent programs, flexfields, messages, and logging.
Oracle E-Business Suite Flexfields Guide
ix
This guide provides flexfields planning, setup, and reference information for the Oracle
E-Business Suite implementation team, as well as for users responsible for the ongoing
maintenance of Oracle E-Business Suite product data. This guide also provides
information on creating custom reports on flexfields data.
Oracle E-Business Suite Installation Guide: Using Rapid Install
This book is intended for use by anyone who is responsible for installing or upgrading
Oracle E-Business Suite. It provides instructions for running Rapid Install either to carry
out a fresh installation of Oracle E-Business Suite Release 12.2, or as part of an upgrade
to Release 12.2.
Oracle E-Business Suite Maintenance Guide
This guide contains information about the strategies, tasks, and troubleshooting
activities that can be used to help ensure an Oracle E-Business Suite system keeps
running smoothly, together with a comprehensive description of the relevant tools and
utilities. It also describes how to patch a system, with recommendations for optimizing
typical patching operations and reducing downtime.
Oracle E-Business Suite Security Guide
This guide contains information on a comprehensive range of security-related topics,
including access control, user management, function security, data security, and
auditing. It also describes how Oracle E-Business Suite can be integrated into a single
sign-on environment.
Oracle E-Business Suite Setup Guide
This guide contains information on system configuration tasks that are carried out
either after installation or whenever there is a significant change to the system. The
activities described include defining concurrent programs and managers, enabling
Oracle Applications Manager features, and setting up printers and online help.
Oracle E-Business Suite User's Guide
This guide explains how to navigate, enter data, query, and run reports using the user
interface (UI) of Oracle E-Business Suite. This guide also includes information on setting
user profiles, as well as running and reviewing concurrent requests.
Oracle E-Business Suite User Interface Standards for Forms-Based Products
This guide contains the user interface (UI) standards followed by the Oracle E-Business
Suite development staff. It describes the UI for the Oracle E-Business Suite products and
how to apply this UI to the design of an application built by using Oracle Forms.
Oracle E-Business Suite Integrated SOA Gateway User's Guide
This guide describes the high level service enablement process, explaining how users
can browse and view the integration interface definitions and services residing in
Oracle Integration Repository.
Oracle E-Business Suite Integrated SOA Gateway Implementation Guide
This guide explains how integration repository administrators can manage and
x
administer the Web service activities for integration interfaces including native
packaged integration interfaces, composite services (BPEL type), and custom
integration interfaces. It also describes how to invoke Web services from Oracle
E-Business Suite by employing the Oracle Workflow Business Event System, and how
to manage Web service security, configure logs, and monitor SOAP messages.
Oracle E-Business Suite Integrated SOA Gateway Developer's Guide
This guide describes how system integration developers can perform end-to-end service
integration activities. These include orchestrating discrete Web services into meaningful
end-to-end business processes using business process execution language (BPEL), and
deploying BPEL processes at run time.
This guide also explains how to invoke Web services using the Service Invocation
Framework. This includes defining Web service invocation metadata, invoking Web
services, and testing the Web service invocation.
Oracle e-Commerce Gateway User's Guide
This guide describes the functionality of Oracle e-Commerce Gateway and the
necessary setup steps in order for Oracle E-Business Suite to conduct business with
trading partners through Electronic Data Interchange (EDI). It also describes how to run
extract programs for outbound transactions, import programs for inbound transactions,
and the relevant reports.
Oracle e-Commerce Gateway Implementation Guide
This guide describes implementation details, highlighting additional setup steps needed
for trading partners, code conversion, and Oracle E-Business Suite. It also provides
architecture guidelines for transaction interface files, troubleshooting information, and a
description of how to customize EDI transactions.
Oracle iSetup Developer's Guide
This manual describes how to build, test, and deploy Oracle iSetup Framework
interfaces.
Oracle iSetup User's Guide
This guide describes how to use Oracle iSetup to migrate data between different
instances of the Oracle E-Business Suite and generate reports. It also includes
configuration information, instance mapping, and seeded templates used for data
migration.
Oracle Report Manager User's Guide
Oracle Report Manager is an online report distribution system that provides a secure
and centralized location to produce and manage point-in-time reports. Oracle Report
Manager users can be either report producers or report consumers. Use this guide for
information on setting up and using Oracle Report Manager.
Oracle Web Applications Desktop Integrator Implementation and Administration
Guide
Oracle Web Applications Desktop Integrator brings Oracle E-Business Suite
xi
functionality to a spreadsheet, where familiar data entry and modeling techniques can
be used to complete Oracle E-Business Suite tasks. You can create formatted
spreadsheets on your desktop that allow you to download, view, edit, and create Oracle
E-Business Suite data, which you can then upload. This guide describes how to
implement Oracle Web Applications Desktop Integrator and how to define mappings,
layouts, style sheets, and other setup options.
Oracle Workflow Administrator's Guide
This guide explains how to complete the setup steps necessary for any product that
includes workflow-enabled processes. It also describes how to manage workflow
processes and business events using Oracle Applications Manager, how to monitor the
progress of runtime workflow processes, and how to administer notifications sent to
workflow users.
Oracle Workflow Developer's Guide
This guide explains how to define new workflow business processes and customize
existing Oracle E-Business Suite-embedded workflow processes. It also describes how
to define and customize business events and event subscriptions.
Oracle Workflow User's Guide
This guide describes how users can view and respond to workflow notifications and
monitor the progress of their workflow processes.
Oracle Workflow API Reference
This guide describes the APIs provided for developers and administrators to access
Oracle Workflow.
Oracle Workflow Client Installation Guide
This guide describes how to install the Oracle Workflow Builder and Oracle XML
Gateway Message Designer client components for Oracle E-Business Suite.
Oracle XML Gateway User's Guide
This guide describes Oracle XML Gateway functionality and each component of the
Oracle XML Gateway architecture, including Message Designer, Oracle XML Gateway
Setup, Execution Engine, Message Queues, and Oracle Transport Agent. It also explains
how to use Collaboration History that records all business transactions and messages
exchanged with trading partners.
The integrations with Oracle Workflow Business Event System, and the
Business-to-Business transactions are also addressed in this guide.
Oracle XML Publisher Report Designer's Guide
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Using Microsoft Word or Adobe Acrobat as the design tool, you can
create pixel-perfect reports from the Oracle E-Business Suite. Use this guide to design
your report layouts.
xii
This guide is available through the Oracle E-Business Suite online help.
Oracle XML Publisher Administration and Developer's Guide
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and
EFT transactions). Oracle XML Publisher can be used to generate reports based on
existing Oracle E-Business Suite report data, or you can use Oracle XML Publisher's
data extraction engine to build your own queries. Oracle XML Publisher also provides a
robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP,
printer, WebDav, and more. This guide describes how to set up and administer Oracle
XML Publisher as well as how to use the Application Programming Interface to build
custom solutions.
This guide is available through the Oracle E-Business Suite online help.
Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to 12.2:
This guide provides information for DBAs and Applications Specialists who are
responsible for upgrading Release 12.0 and 12.1 Oracle E-Business Suite system
(techstack and products) to Release 12.2. In addition to information about applying the
upgrade driver, it outlines pre-upgrade steps and post-upgrade steps, and provides
descriptions of product-specific functional changes and suggestions for verifying the
upgrade and reducing downtime.
Oracle Advanced Global Intercompany System User's Guide:
This guide describes the self service application pages available for Intercompany users.
It includes information on setting up intercompany, entering intercompany
transactions, importing transactions from external sources and generating reports.
Oracle Advanced Collections User Guide:
This guide describes how to use the features of Oracle Advanced Collections to manage
your collections activities. It describes how collections agents and managers can use
Oracle Advanced Collections to identify delinquent customers, review payment history
and aging data, process payments, use strategies and dunning plans to automate the
collections process, manage work assignments, and handle later-stage delinquencies.
Oracle Advanced Collections Implementation Guide:
This guide describes how to configure Oracle Advanced Collections and its integrated
products. It contains the steps required to set up and verify your implementation of
Oracle Advanced Collections.
Oracle Assets User Guide:
This guide provides you with information on how to implement and use Oracle Assets.
Use this guide to understand the implementation steps required for application use,
including defining depreciation books, depreciation method, and asset categories. It
also contains information on setting up assets in the system, maintaining assets, retiring
and reinstating assets, depreciation, group depreciation, accounting and tax accounting,
xiii
budgeting, online inquiries, impairment processing, and Oracle Assets reporting. The
guide explains using Oracle Assets with Multiple Reporting Currencies (MRC). This
guide also includes a comprehensive list of profile options that you can set to customize
application behavior.
Oracle Bill Presentment Architecture User's Guide:
This guide provides you information on using Oracle Bill Presentment Architecture.
Consult this guide to create and customize billing templates, assign a template to a rule
and submit print requests. This guide also provides detailed information on page
references, seeded content items and template assignment attributes.
Oracle Cash Management User Guide:
This guide describes how to use Oracle Cash Management to clear your receipts, as well
as reconcile bank statements with your outstanding balances and transactions. This
manual also explains how to effectively manage and control your cash cycle. It provides
comprehensive bank reconciliation and flexible cash forecasting.
Oracle Credit Management User Guide:
This guide provides you with information on how to use Oracle Credit Management.
This guide includes implementation steps, such as how to set up credit policies, as well
as details on how to use the credit review process to derive credit recommendations
that comply with your credit policies. This guide also includes detailed information
about the public application programming interfaces (APIs) that you can use to extend
Oracle Credit Management functionality.
Oracle Customer Data Librarian User Guide:
This guide describes how to use Oracle Customer Data Librarian to establish and
maintain the quality of the Trading Community Architecture Registry, focusing on
consolidation, cleanliness, and completeness. Oracle Customer Data Librarian has all of
the features in Oracle Customers Online, and is also part of the Oracle Customer Data
Management product family.
Oracle Customer Data Librarian Implementation Guide:
This guide describes how to implement Oracle Customer Data Librarian. As part of
implementing Oracle Customer Data Librarian, you must also complete all the
implementation steps for Oracle Customers Online.
Oracle Customers Online User Guide:
This guide describes how to use Oracle Customers Online to view, create, and maintain
your customer information. Oracle Customers Online is based on Oracle Trading
Community Architecture data model and functionality, and is also part of the Oracle
Customer Data Management product family.
Oracle Customers Online Implementation Guide:
This guide describes how to implement Oracle Customers Online.
Oracle E-Business Suite Multiple Organizations Implementation Guide:
xiv
This guide describes the multiple organizations concepts in Oracle E-Business Suite. It
describes in detail on setting up and working effectively with multiple organizations in
Oracle E-Business Suite.
Oracle E-Business Tax User Guide:
This guide describes the entire process of setting up and maintaining tax configuration
data, as well as applying tax data to the transaction line. It describes the entire
regime-to-rate setup flow of tax regimes, taxes, statuses, rates, recovery rates, tax
jurisdictions, and tax rules. It also describes setting up and maintaining tax reporting
codes, fiscal classifications, tax profiles, tax registrations, configuration options, and
third party service provider subscriptions. You also use this manual to maintain
migrated tax data for use with E-Business Tax.
Oracle E-Business Tax Implementation Guide:
This guide provides a conceptual overview of the E-Business Tax tax engine, and
describes the prerequisite implementation steps to complete in other applications in
order to set up and use E-Business Tax. The guide also includes extensive examples of
setting up country-specific tax requirements.
Oracle E-Business Tax Reporting Guide:
This guide explains how to run all tax reports that make use of the E-Business Tax data
extract. This includes the Tax Reporting Ledger and other core tax reports,
country-specific VAT reports, and Latin Tax Engine reports.
Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System
Implementation Guide
This guide explains how to setup and use the services of third party tax service
providers for US Sales and Use tax. The tax service providers are Vertex Q-Series and
Taxware Sales/Use Tax System. When implemented, the Oracle E-Business Tax service
subscription calls one of these tax service providers to return a tax rate or amount
whenever US Sales and Use tax is calculated by the Oracle E-Business Tax tax engine.
This guide provides setup steps, information about day-to-day business processes, and
a technical reference section.
Oracle Embedded Data Warehouse User Guide:
This guide describes how to use Embedded Data Warehouse reports and workbooks to
analyze performance.
Oracle Embedded Data Warehouse Implementation Guide:
This guide describes how to implement Embedded Data Warehouse, including how to
set up the intelligence areas.
Oracle Embedded Data Warehouse Install Guide:
This guide describes how to install Embedded Data Warehouse, including how to create
database links and create the end user layer (EUL).
Oracle Financial Accounting Hub Implementation Guide:
xv
This guide provides detailed implementation information that leverages the features of
Oracle Subledger Accounting to generate accounting.
Oracle Financial Services Reference Guide:
This guide provides reference material for Oracle Financial Services applications in
Release 12, such as Oracle Transfer Pricing, and includes technical details about
application use as well as general concepts, equations, and calculations.
Oracle Financial Services Implementation Guide:
This guide describes how to set up Oracle Financial Services applications in Release 12.
Oracle Financial Services Reporting Administration Guide:
This guide describes the reporting architecture of Oracle Financial Services applications
in Release 12, and provides information on how to view these reports.
Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to
Release 12:
This guides provides detailed information about the functional impacts of upgrading
Oracle Financials and Oracle Procurement products from Release 11i to Release 12. This
guide supplements the Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to 12.2
.
Oracle Financials Concepts Guide:
This guide describes the fundamental concepts of Oracle Financials. The guide is
intended to introduce readers to the concepts used in the applications, and help them
compare their real world business, organization, and processes to those used in the
applications.
Oracle Financials Country-Specific Installation Supplement:
This guide provides general country information, such as responsibilities and report
security groups, as well as any post-install steps required by some countries.
Oracle Financials for the Americas User Guide:
This guide describes functionality developed to meet specific business practices in
countries belonging to the Americas region. Consult this user guide along with your
financial product user guides to effectively use Oracle Financials in your country.
Oracle Financials for Asia/Pacific User Guide:
countries belonging to the Asia/Pacific region. Consult this user guide along with your
Oracle Financials for Europe User Guide:
countries belonging to the European region. Consult this user guide along with your
Oracle Financials for India User's Guide:
xvi
This guide provides information on how to use Oracle Financials for India. Use this
guide to learn how to create and maintain setup related to India taxes, defaulting and
calculation of taxes on transactions. This guide also includes information about
accounting and reporting of taxes related to India.
Oracle Financials for India Implementation Guide:
This guide provides information on how to implement Oracle Financials for India. Use
this guide to understand the implementation steps required for application use,
including how to set up taxes, tax defaulting hierarchies, set up different tax regimes,
organization and transactions.
Oracle Financials Glossary:
The glossary includes definitions of common terms that are shared by all Oracle
Financials products. In some cases, there may be different definitions of the same term
for different Financials products. If you are unsure of the meaning of a term you see in
an Oracle Financials guide, please refer to the glossary for clarification. You can find the
glossary in the online help or in the Oracle Financials Implementation Guide.
Oracle Financials Implementation Guide:
This guide provides information on how to implement the Oracle Financials E-Business
Suite. It guides you through setting up your organizations, including legal entities, and
their accounting, using the Accounting Setup Manager. It covers intercompany
accounting and sequencing of accounting entries, and it provides examples.
Oracle Financials RXi Reports Administration Tool User Guide:
This guide describes how to use the RXi reports administration tool to design the
content and layout of RXi reports. RXi reports let you order, edit, and present report
information to better meet your company's reporting needs.
Oracle General Ledger Implementation Guide:
This guide provides information on how to implement Oracle General Ledger. Use this
guide to understand the implementation steps required for application use, including
how to set up Accounting Flexfields, Accounts, and Calendars.
Oracle General Ledger Reference Guide
This guide provides detailed information about setting up General Ledger Profile
Options and Applications Desktop Integrator (ADI) Profile Options.
Oracle General Ledger User's Guide:
This guide provides information on how to use Oracle General Ledger. Use this guide
to learn how to create and maintain ledgers, ledger currencies, budgets, and journal
entries. This guide also includes information about running financial reports.
Oracle Incentive Compensation Implementation Guide:
This guide provides Compensation Administrators with guidance during
implementation of Oracle Incentive Compensation. The procedures are presented in the
recommended order that they should be performed for successful implementation.
xvii
Appendixes are included that describe system profiles, lookups, and other useful
information.
Oracle Incentive Compensation User Guide:
This guide helps Compensation Managers, Compensation Analysts, and Plan
administrators to manage Oracle Incentive Compensation on a day-to-day basis. Learn
how to create and manage rules hierarchies, create compensation plans, collect
transactions, calculate and pay commission, and use Sales Credit Allocation.
Oracle Internet Expenses Implementation and Administration Guide:
This book explains in detail how to configure Oracle Internet Expenses and describes its
integration with other applications in the E-Business Suite, such as Oracle Payables and
Oracle Projects. Use this guide to understand the implementation steps required for
application use, including how to set up policy and rate schedules, credit card policies,
audit automation, and the expenses spreadsheet. This guide also includes detailed
information about the client extensions that you can use to extend Oracle Internet
Expenses functionality.
Oracle iAssets User Guide
This guide provides information on how to implement and use Oracle iAssets. Use this
setting up Oracle iAssets rules and related product setup steps. It explains how to
define approval rules to facilitate the approval process. It also includes information on
using the Oracle iAssets user interface to search for assets, create self-service transfer
requests and view notifications.
Oracle iProcurement Implementation and Administration Guide:
This manual describes how to set up and administer Oracle iProcurement. Oracle
iProcurement enables employees to requisition items through a self–service, Web
interface.
Oracle iReceivables Implementation Guide:
This guide provides information on how to implement Oracle iReceivables. Use this
how to set up and configure iReceivables, and how to set up the Credit Memo Request
workflow. There is also a chapter that provides an overview of major features available
in iReceivables.
Oracle iSupplier Portal User Guide:
This guide contains information on how to use Oracle iSupplier Portal to enable secure
transactions between buyers and suppliers using the Internet. Using Oracle iSupplier
Portal, suppliers can monitor and respond to events in the procure-to-pay cycle.
Oracle iSupplier Portal Implementation Guide:
This guide contains information on how to implement Oracle iSupplier Portal and
enable secure transactions between buyers and suppliers using the Internet.
Oracle Loans User Guide:
xviii
This guide describes how to set up and use Oracle Loans. It includes information on
how to create, approve, fund, amortize, bill, and service extended repayment plan and
direct loans.
Oracle Partner Management Implementation and Administration Guide:
This guide helps Vendor administrators to set up and maintain relationships and
programs in the Partner Management application. The main areas include setting up
the partner and channel manager dashboards, partner setup, partner programs and
enrollment, opportunity and referral management, deal registration, special pricing
management, and partner fund management.
Oracle Partner Management Vendor User Guide:
This guide assists vendor users in using Partner Management on a daily basis. This
includes interaction with the partner and channel manager dashboards, working with
partners and partner programs, managing opportunities and referrals, registering deals,
and working with special pricing and partner funds.
Oracle Payables User's Guide:
This guide describes how to use Oracle Payables to create invoices and make payments.
In addition, it describes how to enter and manage suppliers, import invoices using the
Payables open interface, manage purchase order and receipt matching, apply holds to
invoices, and validate invoices. It contains information on managing expense reporting,
procurement cards, and credit cards. This guide also explains the accounting for
Payables transactions.
Oracle Payables Implementation Guide:
This guide provides you with information on how to implement Oracle Payables. Use
this guide to understand the implementation steps required for how to set up suppliers,
payments, accounting, and tax.
Oracle Payables Reference Guide:
This guide provides you with detailed information about the Oracle Payables open
interfaces, such as the Invoice open interface, which lets you import invoices. It also
includes reference information on purchase order matching and purging purchasing
information.
Oracle Payments Implementation Guide:
This guide describes how Oracle Payments, as the central payment engine for the
Oracle E-Business Suite, processes transactions, such as invoice payments from Oracle
Payables, bank account transfers from Oracle Cash Management, and settlements
against credit cards and bank accounts from Oracle Receivables. This guide also
describes how Oracle Payments is integrated with financial institutions and payment
systems for receipt and payment processing, known as funds capture and funds
disbursement, respectively. Additionally, the guide explains to the implementer how to
plan the implementation of Oracle Payments, how to configure it, set it up, test
transactions, and how use it with external payment systems.
xix
Oracle Payments User's Guide:
This guide describes how Oracle Payments, as the central payment engine for the
Oracle E-Business Suite, processes transactions, such as invoice payments from Oracle
Payables, bank account transfers from Oracle Cash Management, and settlements
against credit cards and bank accounts from Oracle Receivables. This guide also
describes to the Payment Administrator how to monitor the funds capture and funds
disbursement processes, as well as how to remedy any errors that may arise.
Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout:
This guide contains necessary information for customers implementing remote catalog
content on a supplier's Web site or on Oracle Exchange.
Oracle Procurement Contracts Online Help:
This guide is provided as online help only from the Oracle Procurement Contracts
application and includes information about creating and managing your contract terms
library.
Oracle Procurement Contracts Implementation and Administration Guide:
This guide describes how to set up and administer Oracle Procurement Contracts.
Oracle Procurement Contracts enables employees to author and maintain complex
contracts through a self–service, Web interface.
Oracle Public Sector Financials User Guide:
This guide describes how to set up and administer Oracle Public Sector Advanced
Features. It describes Encumbrance Reconciliation Reports, GASB 34/35 Asset
Accounting, and Funds Available Enhancements.
Oracle Purchasing User's Guide:
This guide describes how to create and approve purchasing documents, including
requisitions, different types of purchase orders, quotations, RFQs, and receipts. This
guide also describes how to manage your supply base through agreements, sourcing
rules, and approved supplier lists. In addition, this guide explains how you can
automatically create purchasing documents based on business rules through integration
with Oracle Workflow technology, which automates many of the key procurement
processes.
Oracle Receivables User Guide:
This guide provides you with information on how to use Oracle Receivables. Use this
guide to learn how to create and maintain transactions and bills receivable, enter and
apply receipts, enter customer information, and manage revenue. This guide also
includes information about accounting in Receivables. Use the Standard Navigation
Paths appendix to find out how to access each Receivables window.
Oracle Receivables Implementation Guide:
This guide provides you with information on how to implement Oracle Receivables.
Use this guide to understand the implementation steps required for application use,
including how to set up customers, transactions, receipts, accounting, tax, and
xx
collections. This guide also includes a comprehensive list of profile options that you can
set to customize application behavior.
Oracle Receivables Reference Guide:
This guide provides you with detailed information about all public application
programming interfaces (APIs) that you can use to extend Oracle Receivables
functionality. This guide also describes the Oracle Receivables open interfaces, such as
AutoLockbox which lets you create and apply receipts and AutoInvoice which you can
use to import and validate transactions from other systems. Archiving and purging
Receivables data is also discussed in this guide.
Oracle Sourcing Implementation and Administration Guide:
This guide contains information on how to implement Oracle Sourcing to enable
participants from multiple organizations to exchange information, conduct bid and
auction processes, and create and implement buying agreements. This allows
professional buyers, business experts, and suppliers to participate in a more agile and
accurate sourcing process.
Oracle Subledger Accounting Implementation Guide:
This guide provides setup information for Oracle Subledger Accounting features,
including the Accounting Methods Builder. You can use the Accounting Methods
Builder to create and modify the setup for subledger journal lines and application
accounting definitions for Oracle subledger applications. This guide also discusses the
reports available in Oracle Subledger Accounting and describes how to inquire on
subledger journal entries.
Oracle Supplier Scheduling User's Guide:
This guide describes how you can use Oracle Supplier Scheduling to calculate and
maintain planning and shipping schedules and communicate them to your suppliers.
Oracle iProcurement Implementation and Administration Guide:
This manual describes how to set up and administer Oracle iProcurement. Oracle
iProcurement enables employees to requisition items through a self–service, Web
interface.
Oracle Procurement Contracts Implementation and Administration Guide:
This manual describes how to set up and administer Oracle Procurement Contracts.
Oracle Procurement Contracts enables employees to author and maintain complex
contracts through a self–service, Web interface.
Oracle Trading Community Architecture User Guide:
This guide describes the Oracle Trading Community Architecture (TCA) and how to
use features from the Trading Community Manager responsibility to create, update,
enrich, and cleanse the data in the TCA Registry. It also describes how to use Resource
Manager to define and manage resources.
Oracle Trading Community Architecture Administration Guide:
xxi
This guide describes how to administer and implement Oracle Trading Community
Architecture (TCA). You set up, control, and manage functionality that affects data in
the TCA Registry. It also describes how to set up and use Resource Manager to manage
resources.
Oracle Trading Community Architecture Reference Guide:
This guide contains seeded relationship types, seeded Data Quality Management data,
D&B data elements, Bulk Import interface table fields and validations, and a
comprehensive glossary. This guide supplements the documentation for Oracle Trading
Community Architecture and all products in the Oracle Customer Data Management
family.
Oracle Trading Community Architecture Technical Implementation Guide:
This guide explains how to use the public Oracle Trading Community Architecture
application programming interfaces (APIs) and develop callouts based on Oracle
Workflow Business Events System (BES). For each API, this guide provides a
description of the API, the PL/SQL procedure, and the Java method, as well as a table of
the parameter descriptions and validations. For each BES callout, this guide provides
the name of the logical entity, its description, and the ID parameter name. Also
included are setup instructions and sample code.
Oracle U.S. Federal Financials User's Guide:
This guide describes the common concepts for an integrated financial management
solution for federal agencies to comply with the requirements of the U.S. Federal
government. It describes the product architecture and provides information on Budget
Execution, Prompt Payment, Treasury payments, Third party payments, Interagency
transactions, Receivables management, Federal reports, CCR Integration, and Year End
Closing.
Oracle U.S. Federal Financials Implementation Guide:
This guide describes the common concepts for an integrated financial management
solution for federal agencies. It includes a consolidated setup checklist by page and
provides detailed information on how to set up, maintain, and troubleshoot the Federal
Financial application for the following functional areas: Sub Ledger Accounting, Budget
Execution, Prompt Payment, Treasury payments, Third party payments, Interagency
transactions, Receivables management, Federal reports, CCR Integration, and Year End
Closing.
Oracle Projects Documentation Set
Oracle Projects Implementation Guide:
Use this guide to implement Oracle Projects. This guide also includes appendixes
covering function security, menus and responsibilities, and profile options.
Oracle Project Costing User Guide:
Use this guide to learn detailed information about Oracle Project Costing. Oracle Project
Costing provides the tools for processing project expenditures, including calculating
xxii
their cost to each project and determining the General Ledger accounts to which the
costs are posted.
Oracle Project Billing User Guide:
This guide shows you how to use Oracle Project Billing to define revenue and invoicing
rules for your projects, generate revenue, create invoices, and integrate with other
Oracle Applications to process revenue and invoices, process client invoicing, and
measure the profitability of your contract projects.
Oracle Project Management User Guide:
This guide shows you how to use Oracle Project Management to manage projects
through their lifecycles - from planning, through execution, to completion.
Oracle Project Portfolio Analysis User Guide:
This guide contains the information you need to understand and use Oracle Project
Portfolio Analysis. It includes information about project portfolios, planning cycles, and
metrics for ranking and selecting projects for a project portfolio.
Oracle Project Resource Management User Guide:
This guide provides you with information on how to use Oracle Project Resource
Management. It includes information about staffing, scheduling, and reporting on
project resources.
Oracle Grants Accounting Documentation
Oracle Grants Accounting User Guide:
This guide provides you with information about how to implement and use Oracle
Grants Accounting. Use this guide to understand the implementation steps required for
application use, including defining award types, award templates, allowed cost
schedules, and burden set up. This guide also explains how to use Oracle Grants
Accounting to track grants and funded projects from inception to final reporting.
Oracle Property Manager Documentation
Oracle Property Manager User Guide:
Use this guide to learn how to use Oracle Property Manager to create and administer
properties, space assignments, and lease agreements.
Oracle Property Manager Implementation Guide:
Use this guide to learn how to implement Oracle Property Manager and perform basic
setup steps such as setting system options and creating lookup codes, contacts,
milestones, grouping rules, term templates, and a location hierarchy. This guide also
describes the setup steps that you must complete in other Oracle applications before
you can use Oracle Property Manager.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
xxiii
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As
your instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xxiv
1
Expense Reports and Credit Cards
Payables Procurement Card Transactions Interface Table
Payables Procurement Card Transactions Interface Table Column Descriptions

The following table lists the columns in the Payables Procurement Card Transactions
Interface Table and indicates which columns require values for importing into Payables.
See also: Oracle Payables eTRM.
AP_EXPENSE_FEED_LINES_ALL
Column Name Null Type Comments
EMPLOYEE_ID NUMBER(15) Required Foreign key:

HR_EMPLOYEES_
CURRENT_V
CARD_ID NUMBER(15) Foreign key
CARD_PROGRAM_I NOT NULL NUMBER(15) Required; Foreign key

D
CARD_NUMBER NOT NULL VARCHAR2(80) Required
FEED_LINE_ID NOT NULL NUMBER(15) Required; Primary

key
REFERENCE_NUMB VARCHAR2(240) Unique

ER
Expense Reports and Credit Cards 1-1

ALT_REFERENCE_ VARCHAR2(240)
NUMBER
CUSTOMER_CODE VARCHAR2(240)
AMOUNT NOT NULL NUMBER Required (must load

as either positive or
negative number)
ORIGINAL_CURRE NUMBER
NCY_AMOUNT
ORIGINAL_CURRE VARCHAR2(15)
NCY_CODE
POSTED_CURRENC VARCHAR2(15)
Y_CODE
CURRENCY_CONVE NUMBER
RSION_RATE
TRANSACTION_DA DATE
TE
POSTED_DATE NOT NULL DATE
RECORD_TYPE VARCHAR2(25)
CREATE_DISTRIBUT VARCHAR2(1)
ION_FLAG
MERCHANT_NAME VARCHAR2(80)
MERCHANT_NUMB VARCHAR2(80)
ER
CARD_CODE_VALU VARCHAR2(80)
E
CODE_ID NUMBER(15) Foreign key
1-2 Oracle Payables Reference Guide

INDUSTRY_CODE1 VARCHAR2(80)
INDUSTRY_CODE2 VARCHAR2(80)
ALT_MERCHANT_N VARCHAR2(80)
UMBER
MERCHANT_ADDR VARCHAR2(35)
ESS1
ESS2
ESS3
ESS4
MERCHANT_CITY VARCHAR2(25)
MERCHANT_PROVI VARCHAR2(25)
NCE_STATE
MERCHANT_POSTA VARCHAR2(25)
L_CODE
MERCHANT_COUN VARCHAR2(25)
TRY
MERCHANT_PHON VARCHAR2(25)
E
SHIP_FROM_POSTA VARCHAR2(25)
L_CODE
SHIP_FROM_COUN VARCHAR2(25)
TRY
SHIP_TO_POSTAL_C VARCHAR2(25)
ODE

SHIP_TO_COUNTRY VARCHAR2(25)
MERCHANT_TAX_I VARCHAR2(80)
D_NUMBER
TAX_PAID_FLAG VARCHAR2(1)
TAX_AMOUNT NUMBER
TAX_RATE NUMBER
TAX_TYPE VARCHAR2(25)
ALT_MERCHANT_T VARCHAR2(80)
AX_ID
ALT_TAX_PAID_FL NUMBER
AG
ALT_TAX_AMOUNT NUMBER
ALT_TAX_RATE NUMBER
ALT_TAX_TYPE VARCHAR2(25)
FREIGHT_AMOUNT NUMBER
DUTY_AMOUNT NUMBER
MERCHANT_BUSIN VARCHAR2(80)
ESS_ TYPE
MERCHANT_OWNE VARCHAR2(80)
R_TYPE
PRODUCT_CODE VARCHAR2(80)
ITEM_DESCRIPTION VARCHAR2(240)
ITEM_QUANTITY NUMBER
1-4 Oracle Payables Reference Guide

ITEM_UOM VARCHAR2(80)
EXTENDED_ITEM_ NUMBER
AMOUNT
DISCOUNT_INDICA VARCHAR2(1)
TOR
DISCOUNT_AMOU NUMBER
NT
EMPLOYEE_VERIFI NUMBER(15)
CATION_ID
DESCRIPTION VARCHAR2(240)
ORG_ID NUMBER(15)
LAST_UPDATE_DA NOT NULL DATE

TE
LAST_UPDATED_BY NOT NULL NUMBER(15)
LAST_UPDATE_LO NUMBER(15)
GIN
CREATION_DATE DATE
CREATED_BY NUMBER(15)
ATTRIBUTE VARCHAR2(150) Optional

CATEGORY
ATTRIBUTE 1 - 30 VARCHAR2(150) Optional

A
Payables Open Interface Tables
Payables Open Interface Tables

The Payables Open Interface tables store invoice and supplier information for import
into Payables base tables.
The Invoice Open Interface Import program builds Payables invoices based on the
invoice records in the Payables Open Interface tables. After the import program builds
the invoices, they can be viewed, modified, and validated in the Invoice Workbench.
The invoice data includes EDI and XML invoices from your suppliers, invoice records
that you entered in the Quick Invoices window, invoices that you loaded with Oracle
SQL*Loader, lease invoices that were transferred from Property Manager, credit card
transaction data, and invoices that your suppliers entered and submitted online via
Oracle iSupplier Portal.
The Suppliers Open Interface Import, Supplier Sites Open Interface Import, and
Supplier Sites Contacts Open Interface Import process supplier information and load
them into the appropriate tables.
This discussion includes the following topics:
• Understanding the Invoice Open Interface Tables, page A-2
• Understanding the Suppliers Open Interface Tables, page A-3
• Table Descriptions, page A-5
• Account Overlay in Payables Open Interface Import, page A-143
• Sequential Numbering During Import, page A-143
• How the Quick Invoices Window Populates the Payables Open Interface Tables,
page A-145
Payables Open Interface Tables A-1

Related Topics
Payables Open Interface Import, Oracle Payables User Guide
Create Procurement Card Issuer Invoice, Oracle Payables User Guide
Understanding the Invoice Open Interface Tables

Use the Quick Invoices window, Oracle e-Commerce Gateway, the Credit Card Invoice
Interface Summary, Property Manager, the Oracle Assets Export Lease Payments to
Payables process, Oracle XML Gateway, or SQL*Loader to load invoice information into
the interface tables: AP_INVOICES_INTERFACE and
AP_INVOICE_LINES_INTERFACE.
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.
The interface tables include columns, which Payables uses to categorize and store
specific invoice information. For example, invoice source information is stored in the
column called SOURCE in AP_INVOICES_INTERFACE. Columns may have the
following attributes:
NOT NULL Columns

You must enter values for all NOT NULL columns in the interface tables to successfully
save your invoice data in the interface tables. If you do not enter a value in a NOT
NULL column, then you cannot save the record in the interface table.
Required Columns
If you do not enter a valid value in a Required field, then the record will be rejected
during import.
NULL Columns
Leave these columns null or the import process will fail. For example, during import
Payables Open Interface Import updates the values of the STATUS and REQUEST_ID
columns to create invoices. Payables does not support importing any data from these
columns and you should leave these columns null for the records you load in the table.
A-2 Oracle Payables Reference Guide

Conditionally Required Columns
Payables requires you to enter values in a conditionally required column only if you
have entered a value in another column on which the conditionally required column is
dependent.
Optional Columns
You can use some columns in the interface tables to import additional invoice
information for the invoices created by Payables Open Interface Import. Payables Open
Interface Import imports the data that you load into these optional columns, provided
that the information passes the validation checks during Payables Open Interface
Import.
Internal ID Columns
These columns contain values that Payables uses internally and the user never sees. You
can obtain these values only by looking in Payables tables. These ID columns
correspond to other columns in the interface table. You do not need to enter a value for
any of these ID columns if you enter a value in the corresponding column. For example,
if you enter the TERMS_NAME you do not need to enter the TERMS_ID.
If you enter values for both columns and the values do not match, the record will be
rejected during import. For example, if you enter a TERMS_NAME and a TERMS_ID,
and the TERMS_ID corresponds to a different TERMS_NAME, then the record will be
rejected during import.
Note that when you enter invoice records in the Quick Invoices window that Payables
populates the ID columns. This enables faster processing of your invoice records.
Tip: If you are manually entering records: the import process will work
faster if you provide values for the internal ID columns instead of the
corresponding columns.
Understanding the Suppliers Open Interface Tables

The Supplier Open Interface Import, Supplier Sites Open Interface Import and Supplier
Site Contacts Open Interface Import process the information that the user loads into
AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT
tables respectively. When all validations are passed, records are inserted into
PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS respectively.
AP_SUPPLIERS_INT holds Supplier information that is loaded by the user for import.
The columns in the table map to the corresponding columns in the PO_VENDORS
table. Payables uses this information to create a new Supplier record when the Supplier
Open Interface Import program is submitted.
AP_SUPPLIER_SITES_INT holds Supplier Site information that is loaded by the user

for import. The columns in the table map to corresponding columns in the
PO_VENDOR_SITES_ALL table. Payables uses this information to create a new
Supplier Site record when the Supplier Sites Open Interface Import program is
submitted.
AP_SUP_SITE_CONTACT_INT holds Supplier Site Contact data that is loaded by the
user for import. The columns in the table map to corresponding columns in the
PO_VENDOR_CONTACTS table. Payables uses this information to create a new
Supplier Site Contact record when the Supplier Site Contacts Open Interface Import
program is submitted.
Each row in the table will be joined to the appropriate Supplier Site using the
VENDOR_SITE_CODE and ORG_ID and/or the VENDOR_SITE_CODE_ID.
Columns may have the attributes listed in the Understanding the Invoice Open
Interface Tables section.
Users may find it helpful to review the Entering Suppliers and Supplier Sites Window
Reference sections.
When loading existing supplier data into the interface tables, the following checks are
performed to ensure data is valid:
Changes to Supplier Sites Open Interface Import

When importing supplier sites using Supplier Sites Open Interface import, if data is
NULL in any of the following columns of supplier site interface table
(AP_SUPPLIER_SITES_INT), then the values for these columns are populated from the
values defined in the Supplier Tab of Payables Options:
• INVOICE_CURRENCY_CODE
• TERMS_DATE_BASIS
• PAY_GROUP_LOOKUP_CODE
• TERMS_ID or TERMS_NAME
• PAY_DATE_BASIS_LOOKUP_CODE
During import if no value is found both in AP_SUPPLIER_SITES_INT and Payables

Options, then the import program must default as per the current logic.
Defaults
The intent of the Supplier Open Interface Import is to emulate the entry of Suppliers,
Sites, and Contacts through the Supplier Entry form as closely as possible. As such,
there are many values that will be automatically defaulted if not provided by the user.
These defaults for Suppliers can come from AP_SYSTEM_PARAMETERS_ALL,
FINANCIALS_SYSTEM_PARAMS_ALL, PO_SYSTEM_PARAMETERS.ALL,

RCV_PARAMETERS, or hard-coded values. As these source tables are organized by
operating unit and the supplier data is not, the Suppliers Open Interface Import
program assigns a default organization to each run based on the responsibility of the
user initiating the concurrent request. This is necessary in order to determine which
default values to assign to supplier records.
The defaults for Supplier Sites generally come from the Supplier record. However, in
certain cases due to multiple organizations considerations, it is necessary to default
values for Supplier Sites from AP_SYSTEM_PARAMETERS_ALL or
FINANCIALS_SYSTEM_PARAMS_ALL.
Validations
As with defaults, the validations performed by the Suppliers Open Interface Import
program are intended to emulate the processing done by the Supplier Entry form. In
addition to checks done at the database level for correct data types, these validations
include checks performed against existing lookup values or values derived from other
tables. When these types of validations are done, a check is performed to make sure that
the value supplied is that of an active record, a record that has not been end-dated or
disabled. Details of the validations performed can be found in the descriptions for the
AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT
tables.
Rejections
If an invalid value is encountered when the concurrent process is evaluating each row,
the 'REJECT_CODE' column is populated with the relevant rejection message and the
'STATUS' is updated to 'REJECTED'. Processing on that row then stops and the
program moves on to the next row.
Payables Open Interface Table Descriptions

The Payables Open Interface table descriptions list the columns in the
AP_INVOICES_INTERFACE table, the AP_INVOICE_LINES_ INTERFACE table, the
AP_SUPPLIERS_INT table, the AP_SUPPLIER_SITES_INT table, and the
AP_SUP_SITE_CONTACT_INT table. Although columns are validated against columns
in other tables, the tables have no foreign key relationships.
AP_INVOICES_INTERFACE
The following table summarizes the AP_INVOICES_INTERFACE table.

INVOICE_ID NOT NULL NUMBER(15) Required, Primary

key. This value is
assigned in the Quick
Invoices window by
the AP_INVOICES_
INTERFACE_S
sequence.
INVOICE_NUM VARCHAR2(50) Required if there is

more than one
invoice for the
supplier during
import
INVOICE_TYPE_ VARCHAR2(25) Optional

LOOKUP_CODE
INVOICE_DATE DATE Optional
PO_NUMBER VARCHAR2(20) Validated against:

PO_HEADERS.SEGM
ENT1
VENDOR_ID NUMBER(15) Internal ID Validated

against:
PO_VENDORS.VEN
DOR_ID One of the
following is required
unless you match to a
PO: VENDOR_ID,
VENDOR_NUM,
VENDOR_NAME
VENDOR_NUM VARCHAR2(30) One of the following

is required unless you
match to a PO:
VENDOR_ID,
VENDOR_NUM,
VENDOR_NAME

VENDOR_NAME VARCHAR2(80) One of the following

is required:
VENDOR_ID,
VENDOR_NUM,
VENDOR_NAME
VENDOR_SITE_ID NUMBER(15) Internal ID
Validated against:
PO_VENDOR_SITES.
VENDOR_SITE_ID
VENDOR_SITE_COD VARCHAR2(15) N/A

E
INVOICE AMOUNT NUMBER Required
INVOICE_CURRENC VARCHAR2(15) Optional

Y_CODE
Validated against:
FND_CURRENCIES.
CURRENCY_CODE
EXCHANGE_RATE NUMBER Validated against:

GL_DAILY_CONVE
RSION_TYPES.
CONVERSION_TYPE
EXCHANGE_RATE_ VARCHAR2(30) Conditionally

TYPE required
EXCHANGE_DATE DATE Conditionally

required

TERMS_ID NUMBER(15) Internal ID

TERMS_NAME or
TERMS_ID required
if no terms are
available through
matching or at the
supplier site.
Validated against:
AP_TERMS.TERMS_I
D
TERMS_NAME VARCHAR2(50) TERMS_NAME or

TERMS_ID required
if no terms are
available through
matching or at the
supplier site.
DESCRIPTION VARCHAR2(240) Optional
AWT_GROUP_ID NUMBER(15) Internal ID Validated

against:
AP_AWT_GROUPS.
AWT_GROUP_ID
AWT_GROUP_NAM VARCHAR2(25) Optional

E
LAST_UPDATE_DA DATE Optional

TE
LAST_UPDATED_BY NUMBER(15) Optional
LAST_UPDATE_LO NUMBER(15) Optional

GIN
CREATION_DATE DATE Optional
CREATED_BY NUMBER(15) Optional
ATTRIBUTE_CATEG VARCHAR2(150) Optional

ORY

ATTRIBUTE [1-15] VARCHAR2(150) Optional
GLOBAL_ VARCHAR2(150) Optional

ATTRIBUTE_CATEG
ORY
GLOBAL_ATTRIBUT VARCHAR2(150) Optional

E [1-20]
STATUS VARCHAR2(25) N/A
SOURCE VARCHAR2(80) Required
GROUP_ID VARCHAR2(80) Optional
REQUEST_ID NUMBER N/A
PAYMENT_CROSS_ VARCHAR2(30) N/A

RATE_ TYPE
PAYMENT_CROSS_ DATE N/A

RATE_ DATE
PAYMENT_CROSS_ NUMBER N/A

RATE
PAYMENT_CURREN VARCHAR2(15) N/A

CY_CODE
WORKFLOW_FLAG VARCHAR2(1) N/A
DOC_CATEGORY_C VARCHAR2(30) Optional if Sequential

ODE Numbering Profile
option is "Partial" or
"Always"
VOUCHER_NUM VARCHAR2(50) N/A
PAYMENT_METHO VARCHAR2(25) Validated against

D_ LOOKUP_CODE AP_LOOKUP_CODE
S

PAY_GROUP_LOOK VARCHAR2(25) Validated against:

UP_CODE PO_LOOKUP_CODE
S
GOODS_RECEIVED_ DATE N/A

DATE
INVOICE_RECEIVE DATE N/A

D_DATE
GL_DATE DATE N/A
ACCTS_PAY_CODE_ NUMBER(15) N/A

COMBINATION_ID
USSGL_TRANSACTI VARCHAR2(30) N/A

ON_ CODE
EXCLUSIVE_PAYME VARCHAR2(1) N/A

NT_FLAG
ORG_ID NUMBER(15) N/A
AMOUNT_APPLICA NUMBER Optional

BLE_
TO_DISCOUNT
PREPAY_NUM VARCHAR2(50) Validated against

AP_INVOICES_ALL.I
NVOICE_NUM
PREPAY_DIST_NUM NUMBER(15) N/A
PREPAY_APPLY_A NUMBER N/A

MOUNT
PREPAY_GL_DATE DATE N/A
INVOICE_INCLUDE VARCHAR2(1) N/A

S_PREPAY_FLAG

NO_XRATE_BASE_A NUMBER Used only if Payables

MOUNT option Calculate User
Exchange Rate is
enabled
VENDOR_EMAIL_A VARCHAR2(2000) Supplier e-mail

DDRESS address for XML
invoice rejections
TERMS_DATE DATE N/A
REQUESTER_ID NUMBER(10) N/A
INVOICE_ID
Unique identifier for this invoice within this batch. You assign the same value to the
invoice's lines in the AP_INVOICE_LINES_INTERFACE table to identify the data as
belonging to the same invoice.
Validation: None
Destination: None
INVOICE_NUM
Enter the invoice number that you want to assign to the invoice created in Payables
from this record. If you do not enter a value, then during import, Payables uses the
system date at the time of import as a default.
Validation: Must be a unique number for the supplier. If you assign a
duplicate number for the supplier, Payables Open Interface
Import does not create an invoice from this record.
Destination: AP_INVOICES_ALL.INVOICE_NUM
INVOICE_TYPE_LOOKUP_CODE
Type of invoice: Credit or Standard. If you do not enter a value, the system assigns a
value during Payables Open Interface Import based on the value of
INVOICE_AMOUNT. If INVOICE_AMOUNT is less than zero, the invoice will be
Credit. If INVOICE_AMOUNT is zero or greater, the invoice will be Standard. When
using the Service Procurement, you can import prepayments using the Payables Open
Interface Import program.

Validation: The value must be Credit or Standard. The invoice type
must correspond to the invoice amount if it is Credit or
Standard. For example, a Credit invoice must have an
invoice amount that is less than zero.
Destination: AP_INVOICES_ALL.INVOICE_TYPE_LOOKUP_ CODE
INVOICE_DATE
Date of the invoice. If you do not enter a value, the system uses the date you submit
Payables Open Interface Import as the invoice date.
Payables may use the Invoice Date as the Terms Date and the GL Date for an invoice,
depending on your system setup. If your GL Date Basis is Invoice Date, then the Invoice
Date must be in an open or future period.
Validation: The value must be in valid date format.
Destination: AP_INVOICES_ALL.INVOICE_DATE
PO_NUMBER
Number of the purchase order to which you are matching the invoice. If you match the
invoice to a purchase order by entering a value here, during Payables Open Interface
Import the system uses purchase order information to create distributions and populate
various columns in the AP_INVOICE_DISTRIBUTIONS_ALL table. If you do not use
Quick Invoices, and if you do not specify a supplier in the AP_INVOICES_INTERFACE
table, then the PO_NUMBER value is used to derive
AP_INVOICES_ALL.VENDOR_ID, and if you do not specify the supplier site, the
PO_NUMBER value could be used to derive AP_INVOICES_ALL.VENDOR_SITE_ID.
To match an invoice to a purchase order, you do not need to enter a value here at the
invoice header level if you enter a value at the line level,
AP_INVOICE_LINES_INTERFACE.PO_NUMBER.
Validation: This value must match a valid, approved, open purchase
order for the same supplier. The purchase order must not
be final matched. You can obtain a list of valid values from
PO_HEADERS.SEGMENT1. If the source is e-Commerce
Gateway, Payables will import invoices only if they are
within the quantity and price tolerance you have specified
in the Invoice Tolerances window. For other invoice
sources, tolerances are checked at Invoice Validation time.
Destination: None

VENDOR_ID
The internal supplier identifier for the supplier. You must identify the supplier by
entering a value for one of the following columns in this table: VENDOR_ID,
VENDOR_NUM, VENDOR_SITE_ID, or PO_NUMBER. If you have not yet entered the
supplier in the Suppliers window, enter it before import.
Validation: The ID you enter must be for an existing, valid supplier.
You can obtain a list of valid values from
PO_VENDORS.VENDOR_ID.
Destination: AP_INVOICES_ALL.VENDOR_ID
VENDOR_NUM
Supplier number. You must identify the supplier by entering a value for one of the
following columns in this table: VENDOR_ID, VENDOR_NUM, VENDOR_SITE_ID,
VENDOR_SITE CODE, or PO_NUMBER. If you have not yet entered the supplier in the
Suppliers window, then enter it before import.
Validation: The number must be for an existing, valid supplier. You
can obtain a list of valid values from
PO_VENDORS.SEGMENT1.
Destination: None. This value is used to enter

AP_INVOICES_ALL.VENDOR_ID.
VENDOR_NAME
Name of the supplier. You must identify the supplier by entering a value for one of the
following columns in this table: VENDOR_ID, VENDOR_NUM, VENDOR_SITE_ID,
VENDOR_SITE CODE, or PO_NUMBER. If you have not yet entered the supplier in the
Suppliers window, then enter it before import.
Validation: This must be an existing, valid, active supplier. You can
obtain a list of valid values from
PO_VENDORS.VENDOR_NAME.

AP_INVOICES_ALL.VENDOR_ID.
VENDOR_SITE_ID
Internal supplier site identifier.
If you do not provide a valid value to identify the pay site in VENDOR_SITE_CODE or
VENDOR_SITE_ID then import searches for a valid supplier pay site in the following
order:

• primary pay site for supplier
• single existing pay site for supplier
• derived from PO Number matched at the header level
Import rejects the invoice if it cannot identify a valid supplier site.

Validation: The ID you enter must be for an existing, valid supplier site
for the supplier you specify (VENDOR_NUM or
VENDOR_ID). You can obtain a list of valid values from
PO_VENDOR_SITES.VENDOR_SITE_ID. The site must
also be a pay site.
Destination: AP_INVOICES_ALL.VENDOR_SITE_ID
VENDOR_SITE_CODE
Supplier site name.
If you do not provide a valid value to identify the pay site in VENDOR_SITE_CODE or
VENDOR_SITE_ID then import searches for a valid supplier pay site in the following
order:
• primary pay site for supplier
• single existing pay site for supplier
• derived from PO Number matched at the header level
Import rejects the invoice if it cannot identify a valid supplier site.

Validation: This must be a valid, active supplier site for the supplier
you specify (VENDOR_NUM or VENDOR_ID). You can
obtain a list of valid values from
PO_VENDORS.VENDOR_SITE_CODE. The site must also
be a pay site.

AP_INVOICES_ALL.VENDOR_SITE_ID.
INVOICE_AMOUNT
Amount of the invoice. Do not exceed the precision of the currency of for the invoice.
For example, if you are entering an amount in US dollars, then do not enter more than
two numbers after the decimal point.
Validation: This value must equal the sum of the AMOUNT values in
the AP_INVOICE_LINES_INTERFACE table for lines with

the same INVOICE_ID. The amount must correspond to
the invoice type. For example, Standard invoices must have
an amount of zero or greater.
Destination: AP_INVOICES_ALL.INVOICE_AMOUNT
INVOICE_CURRENCY_CODE
Currency code for the invoice. If you do not enter a value, then the supplier site value
defaults during import.
Note: When the invoice currency and payment currency are associated
fixed-rate currencies the PAYMENT_CROSS_RATE_TYPE,
PAYMENT_CROSS_RATE, and PAYMENT_CROSS_RATE_DATE are
not imported to AP_INVOICES_ALL
Validation: If you enter a code in a foreign currency, you must enter a

valid, active currency code from
FND_CURRENCIES.CURRENCY_CODE.
Destination: AP_INVOICES_ALL.INVOICE_CURRENCY_ CODE
EXCHANGE_RATE
Invoice exchange rate for a foreign currency invoice.
If the Payables option Require Exchange Rate Entry is enabled, then you must provide
either an exchange rate or sufficient information for Payables to derive the exchange
rate during import. If EXCHANGE_RATE_TYPE is User, then you must provide a
value for EXCHANGE_RATE (or, if the Payables option Calculate User Exchange Rate
is enabled, then you can provide a value for NO_XRATE_BASE_AMOUNT instead).
If you did not enter the invoice record in the Quick Invoices window, and if you enter
SPOT or CORPORATE as the EXCHANGE_RATE_TYPE, then the import program
supplies the exchange rate value, and you should leave this column null.
If the invoice currency has a fixed rate to your functional currency, then during import
Payables overwrites any value you enter with the fixed rate. You can see any
occurrences of Payables overwriting the exchange rate by reviewing the log file for the
import.
Validation: If you entered the invoice record in the Quick Invoices
window, then do not overwrite the value that the Quick
Invoices window provided or import will reject the invoice
record.
Destination: AP_INVOICES_ALL.EXCHANGE_RATE

EXCHANGE_RATE_TYPE
Type of exchange rate used to calculate the exchange rate between the invoice currency
and your functional currency. If the value in the INVOICE_CURRENCY_CODE column
is a foreign currency code, then enter a value in this column to indicate which exchange
rate type you are using. You can enter a predefined or user-defined exchange rate type.
If the invoice record has a foreign currency and you do not enter a value for
EXCHANGE_RATE_TYPE, then during import the system uses the Exchange Rate
Type selected in the Payables Options window. If the invoice currency and your
functional currency are associated fixed-rate currencies, such as euro and another EMU
currency, then enter EMU Fixed.
Validation: Payables uses five types of exchange rates: User, Spot,
Corporate, EMU Fixed, and user-defined. If you use Spot,
Corporate, or any user-defined rate type, the value you
enter here is validated against the GL Daily Rates table. If
you use EMU Fixed, Payables provides the exchange rate
during import. If you use User as the exchange rate type,
you must either enter a value for EXCHANGE_RATE or, if
the Payables Option Calculate User Exchange Rate is
enabled, you can enter a value for
NO_XRATE_BASE_AMOUNT instead.
Destination: AP_INVOICES_ALL.EXCHANGE_RATE_TYPE
EXCHANGE_DATE
Enter a value in this column if you enter a foreign currency code in the
CURRENCY_CODE column. The date you enter determines the exchange rate for a
foreign currency invoice with a Spot, Corporate, or user-defined rate type. If you leave
this column null, Payables uses the the invoice GL Date.
Validation: Must be in valid date format.
Destination: AP_INVOICES_ALL.EXCHANGE_DATE
TERMS_ID
Internal identifier for the payment terms. You maintain payment terms in the Payment
Terms window. If you want to specify payment terms you need to enter a value in only
one of the following columns: TERMS_NAME or TERMS_ID.
The import process searches the following sources in the following order for payment
terms and uses the first terms it finds:
1. invoice record header (TERMS_ID or TERMS_NAME)
2. purchase order terms for the purchase order in the invoice header (if the invoice

record is purchase order matched at the header level)
3. purchase order terms for the purchase orders to which one or more lines are
matched directly, or indirectly through a receipt (if not more than one set of terms is
represented)
4. supplier site
If none of these sources has a value for payment terms, then the invoice record is
rejected.
If you use calendar-based payment terms and no calendar period is defined for the
terms date, then the system uses the terms date as the due date when it creates the
scheduled payment.
Validation: Terms must be valid terms in the AP_TERMS table.
Destination: AP_INVOICES_ALL.TERMS_ID.
TERMS_NAME
Payment terms. You maintain payment terms in the Payment Terms window. If you
want to specify payment terms you need to enter a value in only one of the following
columns: TERMS_NAME or TERMS_ID.
The import process searches the following sources in the following order for payment
terms and uses the first terms it finds:
1. invoice record header (TERMS_ID or TERMS_NAME)
2. purchase order terms for the purchase order in the invoice header (if the invoice
record is purchase order matched at the header level)
3. purchase order terms for the purchase orders to which one or more lines are
matched directly, or indirectly through a receipt (if not more than one set of terms is
represented)
4. supplier site
If none of these sources has a value for payment terms, then the invoice record is
rejected.
If you use calendar-based payment terms and no calendar period is defined for the
terms date, then the system uses the terms date as the due date when it creates the
scheduled payment.
Validation: Terms must be valid, active terms in the AP_TERMS table.
Destination: None. This value may be used to enter a value for

AP_INVOICES_ALL.TERMS_ID.

DESCRIPTION
Enter the description that you want to assign to the invoice created from this record. If
you are matching to a purchase order and you do not enter a value here, then during
Payables Open Interface Import the system will assign to
AP_INVOICES_ALL.DESCRIPTION the Item Description from the purchase order line.
Validation: None
Destination: AP_INVOICES_ALL.DESCRIPTION
AWT_GROUP_ID
Internal identifier for Automatic Withholding Tax Group. The withholding tax group
you identify in this table (AWT_GROUP_ID or AWT_GROUP_NAME) is used to assign
a withholding tax group to a line only if you do not identify one for the invoice in one
of the following columns: AP_INVOICE_LINES_INTERFACE.AWT_GROUP_ID or
AP_INVOICE_LINES_INTERFACE.AWT_GROUP_NAME.
Validation: If this value is used during import, it must be a valid value
in AP_AWT_GROUPS.
Destination: AP_INVOICES_ALL.AWT_GROUP_ID, only if you do not

enter another value for
AP_INVOICE_LINES_INTERFACE.AWT_GROUP_ID or
AP_INVOICE_LINES_INTERFACE.AWT_GROUP_NAME
.
AWT_GROUP_NAME
Automatic Withholding Tax Group. If you identify a withholding tax group in this table
(AWT_GROUP_ID or AWT_GROUP_NAME), it is used only if you do not identify a
withholding tax group for the invoice lines in the
AP_INVOICE_LINES_INTERFACE.AWT_GROUP_ID or
AP_INVOICE_LINES_INTERFACE.AWT_GROUP_NAME column. You maintain
withholding tax groups in the Withholding Tax Groups window.
Validation: Value must be valid and active in AP_AWT_GROUPS
Destination: None
LAST_UPDATE_DATE
Enter the last update date for this record (usually the same date as CREATION_DATE).
Payables uses this date for reference and audit purposes only.

Destination: AP_INVOICES_ALL.LAST_UPDATED_DATE,
AP_PAYMENT_SCHEDULES.LAST_UPDATED_ DATE
LAST_UPDATED_BY
Enter the userid of the person who last updated this record (usually the same value as
CREATED_BY). If you do not enter a value here, then during Payables Open Interface
Import the system will use the userid of the person who submits Payables Open
Interface Import.
Validation: None
Destination: AP_INVOICES_ALL.LAST_UPDATED_BY, AP_

PAYMENT_SCHEDULES.LAST_UPDATED_BY
LAST_UPDATE_LOGIN
The last date for this record. Usually the same date as the CREATION_DATE. If you
enter a value in this column, the system uses it to populate
AP_INVOICES_ALL.AP_LAST_UPDATE_LOGIN. If you do not enter a value, then
during Payables Open Interface Import the system will use the system date.
Validation: None
Destination: AP_INVOICES_ALL.AP_LAST_UPDATE_LOGIN,AP_PA
YMENT_SCHEDULES.AP_LAST_UPDATE_LOGIN
CREATION_DATE
Enter the date on which you load this record into the interface table. Payables uses this
date for reference and audit purposes. When Payables Open Interface Import creates an
invoice from this record, it does not use this date as the creation date for the invoice; it
uses the system date at the time you submit Payables Open Interface Import.
Destination: AP_INVOICES_ALL.CREATION_DATE,
AP_PAYMENT_SCHEDULES.CREATION_DATE
CREATED_BY
Enter the userid of the person that loads this record into the table. Payables Open
Interface Import transfers this ID to the AP_INVOICES_ALL and
AP_PAYMENT_SCHEDULES tables during import so that the creator of the record
becomes the invoice and scheduled payment creator. If you do not enter a value, then
during Payables Open Interface Import the system will use the userid of the person who
submits Payables Open Interface Import.

Validation: None
Destination: AP_INVOICES_ALL.CREATED_BY,
AP_PAYMENT_SCHEDULES.CREATED_BY
ATTRIBUTE_CATEGORY
Enter the descriptive flexfield category for the descriptive flexfield information you
want to import.
Validation: None
Destination: AP_INVOICES_ALL.ATTRIBUTE_CATEGORY
ATTRIBUTE [1-15]
Enter descriptive flexfield information that you want to import for an invoice. The
structure of the information you enter in these columns (datatypes, value sets) must
match the structure of the descriptive flexfield segments you have defined for your
invoices or you will experience validation problems when you try to access the
information in the invoice windows.
Validation: None
Destination: AP_INVOICES_ALL.ATTRIBUTE[1-15]
GLOBAL_ATTRIBUTE_CATEGORY
Enter the descriptive flexfield category for the descriptive flexfield information you
want to import.
Validation: None
Destination: AP_INVOICES_ALL.GLOBAL_ATTRIBUTE_ CATEGORY
GLOBAL_ATTRIBUTE [1-20]
Validation: If you are using a localization, you must enter appropriate
values in this flexfield or the invoice will be rejected during
import. For more information, see you localization user's
guide.

Destination: AP_INVOICES_ALL.GLOBAL_ATTRIBUTE[1-20]
STATUS
Do not enter a value in this field. It is for internal use only.
Validation: None
Destination: None
SOURCE
Source of the invoice data. Examples include Quick Invoices, EDI Gateway
(e-Commerce Gateway), Credit Card, Oracle Assets, Oracle Property Manager, ERS
(Evaluated Receipt Settlement), RTS (Return to Supplier), XML Gateway, and
user-defined.
You define additional values for Source in the Oracle Payables Lookups window. If you
have defined additional sources, you should use a source name for only one type of
source. For example, do not use the same source name for invoices that you enter in
Quick Invoices, and invoices you load with SQL*Loader.
The Source name also determines which records will be selected for import or purge.
You specify a Source name when you submit Payables Open Interface Import or Purge
Payables Open Interface.
Validation: If you do not use a predefined source you must enter the
name exactly as you have defined the lookup value in the
Oracle Payables Lookups window, or Payables Open
Interface Import will not create an invoice from the record.
The lookup value must have the Type SOURCE. See:
Lookups, Oracle Payables Implementation Guide.
Destination: AP_INVOICES_ALL.SOURCE
GROUP_ID
Identifier for this batch. When you submit Payables Open Interface Import or Purge
Payables Open Interface, you must specify a Source and you can optionally specify a
Group. Processing records by Group allows you to concurrently import or purge
subsets of records for the same Source. You may want to assign a Group ID if you are
processing a large number of records, for example, importing legacy data. For invoice
records entered in the Quick Invoices window, this value is the Quick Invoices Batch
Name.
Validation: None
Destination: None

REQUEST_ID
The system populates this field with the concurrent request ID number for the Payables
Open Interface Import process. Leave this column null.
Validation: None
Destination: None
PAYMENT_CROSS_RATE_TYPE
If the invoice currency and payment currency are associated fixed-rate currencies, enter
EMU FIXED. Otherwise, leave this value null.
Validation: If the invoice currency and payment currencies are
different fixed-rate currencies, then during import,
Payables will overwrite whatever value you enter here
with EMU FIXED. If the invoice and payment currencies
are the same, this value must be null.
Destination: AP_INVOICES_ALL.PAYMENT_CROSS_RATE_ TYPE
PAYMENT_CROSS_RATE
If the invoice currency and payment currency are different currencies and are both
associated fixed-rate currencies (for example, euro and another EMU currency), you can
enter the fixed cross rate. If you leave this value null, Payables will provide the cross
rate during import.
Validation: If this value is different from the cross rate in the
GL_DAILY_RATES table, the fixed rate in the
GL_DAILY_RATES table will be used, and the system will
ignore the value you provided. If the invoice currency and
payment currency are the same, you can enter 1 as the
value.
Destination: AP_INVOICES_ALL.PAYMENT_CROSS_RATE
PAYMENT_CROSS_RATE_DATE
Date cross rate between invoice currency and payment currency is effective.
Validation: This value must be the exact cross rate in the
GL_DAILY_RATES table. If the values for
PAYMENT_CURRENCY_CODE and
INVOICE_CURRENCY_CODE are different, you must
enter a value for PAYMENT_CROSS_RATE_DATE, and
the two currencies must have a fixed rate effective as of the

cross rate date or the invoice will be rejected.
Destination: AP_INVOICES.PAYMENT_CROSS_RATE_DATE
PAYMENT_CURRENCY_CODE
Currency code for the payment. If you do not provide a value, then during import
PAYMENT_CURRENCY_CODE will be set to the same value as the
INVOICE_CURRENCY_CODE, the PAYMENT_CROSS_RATE will be set to 1, and the
PAYMENT_CROSS_RATE_TYPE and the PAYMENT_CROSS_RATE_DATE will both
be null.
Validation: If the invoice currency is not a fixed rate currency, this
value must be the same as INVOICE_CURRENCY_CODE.
If the invoice currency is a fixed-rate currency, such as
Euro or an EMU national currency, you can enter an
associated fixed-rate currency. This must be a valid, active
currency code from
Destination: AP_INVOICES_ALL.PAYMENT_CURRENCY_ CODE
WORKFLOW_FLAG
Payables Open Interface Workflow status of the invoice record. You submit this
workflow before import.
If you are using the Payables Open Interface Workflow and you want Workflow to
process this record, enter Y. If you enter D, Workflow will not process this record. See:
Payables Open Interface Import Workflow, Oracle Payables Implementation Guide.
• Y. To Be Processed. Invoice record will be processed by workflow. The import
program will not process invoice records with this status.
• S. Processing. Workflow is currently processing invoice record. The import

program will not process invoice records with this status.
• D. Processed. Workflow has processed the invoice record and it is ready for import.
• Null. Not Applicable. Invoice record is ready for import.

Validation: None
Destination: None
DOC_CATEGORY_CODE
If you are using automatic sequential numbering, then Payables Open Interface Import

uses this column to assign a document category to the invoice it creates.
If the Sequential Numbering profile value is "Always" and you do not enter a value in
this column, then during import Payables will use STANDARD as the category if the
invoice amount is zero or positive, and CREDIT if the invoice amount is negative. We
assume that a valid automatic sequence exists for such categories.
If you enable the Allow Document Category Override Payables option, you can enter
the document category you want Payables Open Interface Import to assign to the
invoice created from this record, instead of the Standard or Credit document category.
Validation: The value is a valid value in
AP_INVOICES_ALL.FND_DOC_SEQUENCE_
CATEGORIES. Do not enter a value in this column unless
the Sequential Numbering profile option is set to Partial or
Always, and the Allow Document Category Override
Payables option is enabled. If you enter the value of
Standard, then the invoice amount must be positive, and if
you enter the value of Credit, then the invoice amount
must be negative.
If you enter a document category, it must have an active,
automatic sequence assigned to it.
Destination: AP_INVOICES_ALL.DOC_CATEGORY_CODE
VOUCHER_NUM
If you use manual sequential numbering, then enter a unique value for the voucher
number you want to apply to the invoice created from this record. The number should
not exceed nine digits or you will have problems processing the invoice in Payables.
Validation: If you use manual sequential numbering, the system
validates the voucher number for uniqueness. If you use
automatic sequential numbering, Payables ignores any
value you load into this column and instead selects the next
available number for the numbering sequence assigned to
the document category for imported invoices.
Destination: AP_INVOICES_ALL.VOUCHER_NUM
PAYMENT_METHOD_LOOKUP_CODE
Method that will be used to pay the invoice.
Validation: The value must be a valid value for the
PAYMENT_METHOD lookup code. Payment Methods are
user defined in Oracle Payments

PAY_GROUP_LOOKUP_CODE
Pay Group to which the invoice will be assigned. If you do not enter a value, the value
will default from the supplier site. If the supplier site does not have a value for Pay
Group, then the value will default from the supplier. If neither the supplier nor the
supplier site has a value, the system uses the default Pay Group Payables option.
Validation: The value must be a valid and active value in
AP_LOOKUP_CODES.LOOKUP_CODE, with a
LOOKUP_TYPE value of PAYGROUP.
Destination: AP_INVOICES_ALL.PAY_GROUP_ LOOKUP_CODE
GOODS_RECEIVED_DATE
If you do not provide a value for TERMS_DATE, and if your Terms Date Basis Payables
option is set to Goods Received, then if you provide a value here, Payables will use this
value as the terms date.
Validation: The value must have a valid date format.
Destination: AP_INVOICES_ALL.GOODS_RECEIVED_DATE
INVOICE_RECEIVED_DATE
If you do not provide a value for TERMS_DATE, and if your Terms Date Basis Payables
option is set to Invoice Received, then if you provide a value here, Payables will use the
value as the terms date.
Validation: The value must have a valid date format.
Destination: AP_INVOICES_ALL.INVOICE_RECEIVED_DATE
ORG_ID
Organization identifier.
Quick Invoices records are assigned the ORG_ID associated with the user's
responsibility. If this column has no value then the system uses the ORG_ID associated
with the responsibility used to submit import. Must be a valid organization. Purchase
order matched invoices must use an organization consistent with the purchase order.
Validation: Must be a valid organization. Purchase order matched
invoices must use an organization consistent with the
purchase order.
Destination: AP_INVOICES_ALL.ORG_ID

GL_DATE
The GL Date for the invoice distributions. The date must be in an open or future period.
During import, Payables looks for a GL Date value to assign to the invoice distribution.
Payables assigns a value from the first source it finds, and it searches the following
sources in the following order: invoice record line, invoice record header, GL Date
parameter from import submission, GL Date Basis Payables option.
Note: The following occurs if the system searches at the GL Date Basis
level: If the GL Date Basis option is set to Goods Received/Invoice Date,
then Payables uses the Goods Received Date, if it is populated. If not,
then Payables uses the Invoice Date. If the GL Date Basis option is set to
Goods Received/System Date, then Payables uses the Goods Received
Date, if it is populated. If it is not, then Payables uses the system date at
time of import.
If the GL Date of an invoice is in a future period in Payables, you can account for the
invoice but you cannot pay it.
Important: If you are using encumbrance accounting, you must enter a

GL Date in a period that is within the latest open encumbrance year.
(See also: Budgetary Control In Payables).
Validation: Must be in valid date format. The date
must be in an open or future accounting
period.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.
ACCOUNTING_DATE (if no value is
provided at line level)
ACCTS_PAY_CODE_COMBINATION_ID
Liability account. Payables defaults this value to invoice distributions during import.
Payables uses the liability account when you create accounting entries for your invoices
if you use accrual basis accounting. Payables credits the liability account in an amount
equal to the sum of your invoice distributions. If you do not provide a value, the system
uses the account from the supplier site.
Validation: Must be a valid account in your chart of accounts.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.ACCTS_
PAY_CODE_COMBINATION_ID

USSGL_TRANSACTION_CODE
Enter the default transaction code you want to assign to an invoice.
Open Interface Import imports any USSGL information that you load into the interface
tables and assigns the information to the invoices it creates.
Validation: None
Destination: AP_INVOICES_ALL.USSGL_TRANSACTION_ CODE
EXCLUSIVE_PAYMENT_FLAG
Pay Alone flag. A pay alone invoice is paid with its own payment document without
including other invoices for the supplier.
Validation: None
Destination: AP_INVOICES_ALL.EXCLUSIVE_PAYMENT_ FLAG
ORG_ID
Quick Invoices invoice records are assigned the ORG_ID associated with the user's
responsibility. If this column has no value then the system uses the ORG_ID associated
with the responsibility used to submit import.
Validation: Must be a valid organization. Purchase order matched
invoices must use an organization consistent with the
purchase order.
This value must be consistent with the ORG_ID value at
the invoice header.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.ORG_ID
AMOUNT_APPLICABLE_TO_DISCOUNT
Invoice amount applicable to discount.
Validation: None
Destination: AP_INVOICES_ALLAMOUNT_APPLICABLE_TO_DISCO
UNT.
PREPAY_NUM
Invoice number of a specific prepayment that you want to apply. Leave this column
null to apply all available prepayments in chronological order, starting with the oldest

prepayment first, up to the prepayment amount.
If the PREPAY_APPLY_AMOUNT exceeds the amount available on the specified
prepayment, then import applies the specified prepayment first, then applies remaining
available prepayments (oldest first) up to the specified PREPAY_APPLY_AMOUNT.
For more information see: Applying Prepayments to Invoices in the Open Interface,
Oracle Payables User Guide.
Validation: The prepayment has a settlement date on or before the
system date, is fully paid, is type Temporary, has the same
invoice and payment currency as the invoice, and has not
been fully applied.
Destination: None. Import uses this information to populate

AP_INVOICES_DISTRIBUTIONS_ALL.
PREPAY_DISTRIBUTION_ID
PREPAY_DIST_NUMBER
Distribution number of a specific Item distribution on the specified prepayment that
you want to apply. Leave this field blank to apply all available prepayment Item
distributions, starting with the lowest distribution number first, up to the amount of the
invoice.
Validation: Must be a valid distribution number on the prepayment,
must be an Item distribution, and cannot be a reversal
distribution.
PREPAY_DISTRIBUTION_ID
PREPAY_APPLY_AMOUNT
If you are applying prepayments, the maximum currency amount of the prepayments
you want to apply to the invoice. Payables ensures that the prepayment amount does
not exceed the invoice amount.
Validation: Must not exceed unpaid invoice amount or amount of
available prepayments. Cannot be zero or a negative
number.
PREPAY_APPLY_AMOUNT
PREPAY_GL_DATE
Accounting date for the application of the prepayment. This will be the GL date on the
new Prepayment type distribution on the imported invoice. If you do not enter a value,

then import will use the system date as the prepayment accounting date.
Validation: The date must be in an open or future period.
Destination: AP_INVOICES_DISTRIBUTIONS_ALL.
ACCOUNTING_DATE
INVOICE_INCLUDES_PREPAY_FLAG
A value of Y indicates that the invoice amount has been reduced by a prepayment.
When the invoice is imported the amount paid on the invoice will not be reduced by the
prepayment applied to it. For more information see: Entering Invoices that Reference
Prepayments, Oracle Payables User Guide.
Validation: None
Destination: AP_INVOICES_DISTRIBUTIONS_ALL.
INVOICE_INCLUDES_PREPAY_FLAG
NO_XRATE_BASE_AMOUNT
Invoice functional currency amount. Used only if the Payables option Calculate User
Exchange Rate is enabled and if the exchange rate type is User. Import uses this value
and the INVOICE_AMOUNT to calculate and enter the invoice exchange rate.
Validation: If you provide a value for NO_XRATE_BASE_AMOUNT
the Payables option Calculate User Exchange Rate must be
enabled; and the exchange rate type must be User. If the
Payables option Calculate User Exchange Rate is enabled,
and if the exchange rate type is User, then you are required
to enter a value for either NO_XRATE_BASE_AMOUNT or
EXCHANGE_RATE. If you enter values for both
NO_XRATE_BASE_AMOUNT and EXCHANGE_RATE,
then you must provide the correct exchange rate or import
will reject the invoice.
Destination: AP_INVOICES_ALL.BASE_AMOUNT
VENDOR_EMAIL_ADDRESS
Supplier e-mail address.
Oracle XML Gateway populates this column when it loads XML invoice records to
Payables. Certain invoice import failures will cause a workflow notification of the
problem to be sent to the supplier at this specified e-mail address. For a list of these
import rejections, see: Processing Oracle XML Gateway Invoice Records, Oracle Payables
Implementation Guide.

Validation: None
Destination: None
TERMS_DATE
Date that Payables uses as the payment terms start date. If you leave this value blank
then the system derives the value based on the Terms Date Basis Payables option if you
have provided a value for the corresponding column.
Validation: The value must be in a valid date format.
Destination: AP_INVOICES_ALL.TERMS_DATE
REQUESTER_ID
ID of person who requested the goods or services on the invoice. If you use Invoice
Approval Workflow, then you can define rules that use this value to generate a
hierarchical list of approvers for the invoice.
Validation: This ID must correspond to a valid, existing employee.
Destination: AP_INVOICES_ALL.REQUESTER_ID
EXTERNAL_DOC_REF
Identifier your supplier assigns to this invoice record. Payables uses this value only
when it sends error notifications to the supplier for XML invoices.
Validation: None
Destination: None
AP_INVOICE_LINES_INTERFACE
INVOICE_ID NOT NULL NUMBER(15) Required
Validated against:
AP_INVOICES_INTE
RFACE

INVOICE_LINE_ID NUMBER(15) Internal ID. Required.

Value provided by
the
AP_INVOICE_LINES
_INTERFACE_S
sequence. Primary
key. Must be unique
for the INVOICE_ID.
LINE_NUMBER NUMBER(15) Required
LINE_TYPE_LOOKU VARCHAR2(25) Required

P_CODE
LINE_GROUP_NUM NUMBER Optional

BER
AMOUNT NUMBER Required
ACCOUNTING_DAT DATE N/A

E
DESCRIPTION VARCHAR2(240) Optional
PRORATE_ACROSS_ VARCHAR2(1) Optional

FLAG
TAX_CODE VARCHAR2(15) Validated against:

AP_TAX_CODES.NA
ME
FINAL_MATCH_FL VARCHAR2(1) N/A

AG
PO_HEADER_ID NUMBER Internal ID
Validated against:
PO_HEADERS.PO_H
EADER_ID

PO_NUMBER VARCHAR2(20) Optional
Validated against:
PO_HEADERS.SEGM
ENT1
PO_LINE_ID NUMBER Internal ID
Validated against:
PO_LINES.PO_LINE
_ID
PO_LINE_NUMBER NUMBER Optional
Validated against:
PO_LINES.PO_LINE
_NUM
PO_LINE_LOCATIO NUMBER Internal ID

N_ID
Validated against:
PO_LINE_LOCATIO
NS.LINE_LOCATIO
N_ID
PO_SHIPMENT_NU NUMBER Optional

M
Validated against:
PO_LINE_LOCATIO
NS.SHIPMENT_NU
M
PO_DISTRIBUTION_ NUMBER Internal ID

ID
Validated against:
PO_DISTRIBUTIONS
.PO_DISTRIBUTION
_ID

PO_DISTRIBUTION_ NUMBER Optional

NUM
Validated against:
PO_DISTRIBUTIONS
.PO_DISTRIBUTION
_NUM
INVENTORY_ITEM_ NUMBER Optional

ID
Validated against:
MTL_SYSTEM_ITEM
S.INVENTORY_ITE
M_ID
ITEM_DESCRIPTION VARCHAR2(240) Optional
QUANTITY_INVOIC NUMBER Optional

ED
SHIP_TO_LOCATIO VARCHAR2(25) N/A

N_CODE
UNIT_PRICE NUMBER Optional
DISTRIBUTION_SET NUMBER(15) Internal ID

_ID
Validated against:
AP_DISTRIBUTION_
SETS.
DISTRIBUTION_SET
_ID
DISTRIBUTION_SET VARCHAR2(50) Optional

_NAME
DIST_CODE_CONC VARCHAR2(250) Optional

ATENATED

DIST_CODE_COMBI NUMBER(15) Internal ID

NATION_ID
Validated against:
GL_CODE_COMBIN
ATIONS.
CODE_COMBINATI
ON_ID
AWT_GROUP_ID NUMBER(15) Internal ID
Validated against:
AP_AWT_GROUPS.
GROUP_ID
AWT_GROUP_NAM VARCHAR2(25) Optional

E
LAST_UPDATED_BY NUMBER(15) Optional
LAST_UPDATE_DA DATE Optional

TE
LAST_UPDATE_LO NUMBER(15) Optional

GIN
CREATED_BY NUMBER(15) Optional
CREATION_DATE DATE Optional
ATTRIBUTE VARCHAR2(150) Optional

CATEGORY
ATTRIBUTE [1-15] VARCHAR2(150) Optional

E CATEGORY

E [1-20]

PO_RELEASE_ID NUMBER Optional
Validated against:
PO_RELEASES_ALL
RELEASE_NUM NUMBER Optional
ACCOUNT_SEGME VARCHAR2(25) Optional

NT
BALANCING_SEGM VARCHAR2(25) Optional

ENT
COST_CENTER_SEG VARCHAR2(25) Optional

MENT
PROJECT_ID NUMBER(15) Internal ID Validated

against:
PA_PROJECTS
TASK_ID NUMBER(15) Internal ID Validated

against: PA_TASKS
EXPENDITURE_TYP VARCHAR2(30) Validated against:

E PA_EXPENDITURE_
TYPES
EXPENDITURE_ITE DATE Validated against:

M_DATE PA_EXPENDITURE_
TYPES
EXPENDITURE_ NUMBER(15) Validated against

ORGANIZATION_ID
PER_ORGANIZATIO
N_UNITS.
EXPENDITURE_ORG
ANIZATION_ID
PA_ADDITION_FLA VARCHAR2(1) Projects

G
PA_QUANTITY NUMBER Projects

USSGL_TRANSACTI VARCHAR2(30) General Ledger

ON_CODE
STAT_AMOUNT NUMBER N/A
TYPE_1099 VARCHAR2(10) N/A
INCOME_TAX_REGI VARCHAR2(10) N/A

ON
ASSETS_TRACKING VARCHAR2(1) N/A

_FLAG
TAX_CODE_ID NUMBER(15) N/A
PRICE_CORRECTIO VARCHAR2(1) N/A

N_FLAG
ORG_ID NUMBER(15) Organization

identifier
RECEIPT_NUMBER VARCHAR2(30) Validated against

RCV_SHIPMENT_H
EADERS.RECEIPT_N
UM
RECEIPT_LINE_NU VARCHAR2(25) N/A

MBER
MATCH_OPTION VARCHAR2(25) N/A
PACKING_SLIP VARCHAR2(25) N/A
RCV_TRANSACTIO NUMBER N/A

N_ID
PA_CC_AR_INVOIC NUMBER(15) Identifier of the

E_ID corresponding
receivable
intercompany invoice
in Oracle Receivables

PA_CC_AR_INVOIC NUMBER(15) Identifier of the

E_LINE_NUMBER corresponding
receivable
intercompany invoice
in Oracle Receivables
REFERENCE_1 VARCHAR2(30) Projects
REFERENCE_2 VARCHAR2(30) Projects
PA_CC_PROCESSED VARCHAR2(1) N/A

_CODE
NUMBER(15) Credit card

CREDIT_CARD_TRX transaction ID if the
_ID line is a credit card
charge.
AWARD_ID NUMBER(15) Grants requirement

to store award.
VENDOR_ITEM_NU VARCHAR(25) Optional. Validated

M against PO_LINES_
ALL.VENDOR_PRO
DUCT_NUM
TAXABLE_FLAG VARCHAR2(1) Value of Y indicates

that the line is
taxable.
PRICE_CORRECT_I VARCHAR2(50) N/A

NV_NUM
VARCHAR2(240) Internal document

EXTERNAL_DOC_LI reference number
NE_REF from Accounts
Receivables system.
Used for XML
Invoices.
SERIAL_NUMBER VARCHAR2(35) Serial number for

item.

MANUFACTURER VARCHAR2(30) Name of the

manufacturer.
MODEL_NUMBER VARCHAR2(40) Model information.
WARRANTY_NUMB VARCHAR2(15) Warranty number.

ER
VARCHAR2(1) Flag that indicates

DEFERRED_ACCTG whether to generate
_FLAG deferred accounting
for this line.
DATE The start date of the

DEF_ACCTG_START deferred expense
_DATE period.
DATE The end date of the

DEF_ACCTG_END_ deferred expense
DATE period.
NUMBER Number of periods

DEF_ACCTG_NUMB to generate deferred
ER_OF_PERIODS expenses. Used in
combination with
PERIOD_TYPE.
Alternative to
END_DATE.
DEF_ACCTG_PERIO VARCHAR2(15) Period type used in

D_TYPE combination with
NUMBER_OF_PERIO
DS to generate
deferred expenses.
Validated against
XLA_LOOKUPS with
lookup type
XLA_DEFERRED_PE
RIOD_TYPE.

UNIT_OF_MEAS_LO VARCHAR2(25) Unit of Measure for

OKUP_CODE quantity invoiced.
Validated against
MTL_UNITS_OF_ME
ASURE.UNITS_OF_
MEASURE
PRICE_CORRECT_I NUMBER Invoice line subject to

NV_LINE_NUM the price correction.
ASSET_BOOK_TYPE VARCHAR2(15) Asset Book Defaults

_CODE to the distributions
candidate for transfer
to Oracle Assets.
ASSET_CATEGORY_ NUMBER(15) Asset Category

ID Defaults to the
distributions
candidate for transfer
to Oracle Assets.
REQUESTER_ID VARCHAR2(15) Requester identifier.

Valid values from
active HR employees.
Validated against
PER_ALL_PEOPLE_F
.PERSON_ID
REQUESTER_FIRST_ VARCHAR2(150) The first name of the

NAME employee who
requested goods or
services on the
invoice line. This
value is used to
derive the requester
ID. If you use the
Invoice Approval
Workflow then you
can define rules that
use the requester ID
to generate a
hierarchical list of
approvers for the line.

REQUESTER_LAST_ VARCHAR2(150) The last name of the

NAME employee who
requested goods or
services on the
invoice line. This
value is used to
ID. If you use the
Invoice Approval
Workflow then you
to generate a
REQUESTER_EMPL VARCHAR2(30) The employee

OYEE_NUM number of the
employee who
requested goods or
services on the
invoice line. This
value is used to
ID. If you use the
Invoice Approval
Workflow then you
to generate a
APPLICATION_ID NUMBER(15) Application identifier.
PRODUCT_TABLE VARCHAR2(30) Product source table

name.
REFERENCE_KEY1 VARCHAR2(150) Primary key

information that will
uniquely identify a
record in other
products view.


uniquely identify a
record in other
products view.

uniquely identify a
record in other
products view.

uniquely identify a
record in other
products view.

uniquely identify a
record in other
products view.
PURCHASING_CAT VARCHAR2(2000) Item category

EGORY concatenated
segments.
PURCHASING_CAT NUMBER(15) Item category unique

EGORY_ID ID
COST_FACTOR_ID NUMBER(15) Identifier of the cost

component class.
Used to identify the
individual buckets or
component costs that
make up the total cost
of an item for
example, direct
material costs, freight
costs, labor costs,
production or
conversion costs and
so on.

COST_FACTOR_NA VARCHAR2(80) Cost component class

ME name. Used to
identify the
individual buckets or
component costs that
make up the total cost
of an item for
example, direct
material costs, freight
costs, labor costs,
production or
conversion costs and
so on.
CONTROL_AMOUN NUMBER Optional,

T user-enterable value
to ensure that the
calculated tax will be
the same as on the
physical document.
ASSESSABLE_VALU NUMBER User enterable

E amount to be used as
taxable basis.
DEFAULT_DIST_CCI NUMBER(15) Already addressed

D by lines project Tax
Driver: Code
combination
identifier of the GL
account associated
with the transaction
line. Note that this is
necessary to support
the Account Method
VAT feature.
PRIMARY_INTENDE VARCHAR2(30) Tax Driver: The

D_USE purpose for which the
product may be used.
The actual use will be
stored at the
distribution level.

SHIP_TO_LOCATIO NUMBER(15) Tax Driver: Ship to

N_ID location ID. Value
entered by user only
if line is not PO
matched.
PRODUCT_TYPE VARCHAR2(240) Tax Driver: Type of

product. Possible
values are: Goods,
Service. This value
will default from
Inventory Item
attributes. Otherwise,
value will be entered
by user.
PRODUCT_CATEGO VARCHAR2(240) Tax Driver: Product

RY category.
PRODUCT_FISC_CL VARCHAR2(240) Tax Driver: Product

ASSIFICATION fiscal classification.
USER_DEFINED_FIS VARCHAR2(240) Tax Driver: Fiscal

C_CLASS Classification.
TRX_BUSINESS_CAT VARCHAR2(240) Tax Driver:

EGORY Transactoins category
assigned by user.
TAX_REGIME_COD VARCHAR2(30) Tax Regime Code:

E The set of tax rules
that determines the
treatment of one or
more taxes
administered by a tax
authority.
TAX VARCHAR2(30) A classification of a

charge imposed by a
government through
a fiscal or tax
authority.

TAX_JURISDICTION VARCHAR2(30) Internal ID of the Tax

_CODE Jurisdiction.
TAX_STATUS_CODE VARCHAR2(30) Tax status code.
TAX_RATE_ID NUMBER(15)) Internal identifier for

tax rate effective on
the invoice date.
TAX_RATE_CODE VARCHAR2(150) Tax rate name

associated with tax
rate identifier.
TAX_RATE_ID is
unique while the
TAX_RATE_CODE
may have different
tax rates based on
date ranges.
TAX_RATE NUMBER The rate specified for

a tax status in effect
for a period of time.
INCL_IN_TAXABLE_ VARCHAR2(1) Flag to indicate if the

LINE_FLAG amount in the tax line
is included or not in
the taxable line.
CALC_TAX_DURIN VARCHAR2 (1) Indicates whether tax

G_IMPORT_FLAG should be calculated
or not for the
imported invoice.
SOURCE_APPLICAT NUMBER Source document

ION_ID application identifier.
SOURCE_ENTITY_C VARCHAR2(30) Source document

ODE entity code.
SOURCE_EVENT_CL VARCHAR2(30) Source document

ASS_CODE event class code.

SOURCE_TRX_ID NUMBER Source document

transaction identifier.
SOURCE_LINE_ID NUMBER Identifier of the

lowest level for which
tax is calculated.
SOURCE_TRX_LEVE VARCHAR2(30) Source document

L_TYPE transaction level type.
TAX_CLASSIFICATI VARCHAR2(30) Tax classification

ON_CODE code.
INVOICE_ID
Enter the INVOICE_ID of the corresponding invoice in the
AP_INVOICES_INTERFACE table. This value is used only to assign lines in this table to
invoices in the AP_INVOICES_INTERFACE table. If this value does not match a value
in AP_INVOICES_INTERFACE.INVOICE_ID, this row (invoice line record) will not be
imported and it will not appear on the Open Interface Rejections Report.
Validation: This must match a value in
AP_INVOICES_INTERFACE.INVOICE_ID or the line will
not be imported.
Destination: None
INVOICE_LINE_ID
This value is not required in this table. You can enter a unique number for each invoice
line of an invoice. This column is populated by the
AP_INVOICE_LINES_INTERFACE_S sequence.
Validation: The value must be a number.
Destination: None
LINE_NUMBER
You can enter a unique number to identify the line.
Validation: This value should be a number.

Destination: None. The import program automatically generates the
values for AP_INVOICE_LINES_ALL.LINE_NUMBER.
LINE_TYPE_LOOKUP_CODE
Enter the lookup code for the type of invoice distribution that you want Payables Open
Interface Import to create from this record.
Validation: The code you enter must be ITEM, TAX,
MISCELLANEOUS, or FREIGHT. These lookup codes are
stored in the AP_LOOKUP_CODES table. AWT is not an
acceptable value here.
Destination: AP_INVOICE_LINES_ALL.LINE_TYPE_LOOK UP_CODE
LINE_GROUP_NUMBER
If you want to prorate a charge to a group of lines, enter an identical line group number
value for each Item line to which you want to prorate the charge. For example, if you
want to prorate tax across two Item lines, enter the same line group number for the two
Item lines and the Tax line.
Validation: This value must be a positive whole number.
Destination: AP_INVOICE_LINES_ALL.LINE_GROUP_NUMBER
AMOUNT
The invoice distribution amount. If you are matching to a purchase order, the
AMOUNT = QUANTITY_INVOICED x UNIT PRICE.
Validation: If the total amount of all the invoice lines does not equal
the amount of the invoice header that has the same
INVOICE_ID, then Payables Open Interface Import will
reject the invoice.
Destination: AP_INVOICE_LINES_ALL.AMOUNT
ACCOUNTING_DATE
The GL Date for the invoice distributions. The date must be in an open or future period.
During import, Payables looks for a GL Date value to assign to the invoice distribution.
Payables assigns a value from the first source it finds, and it searches the following
sources in the following order: line of the invoice record, header of the invoice record,
GL Date parameter from import submission, GL Date Basis Payables option.

Note: The following occurs if the system searches at the GL Date Basis
level: If the GL Date Basis option is set to Goods Received/Invoice Date,
then Payables uses the Goods Received Date, if it is populated. If not,
then Payables uses the Invoice Date. If the GL Date Basis option is set to
Goods Received/System Date, then Payables uses the Goods Received
Date, if it is populated. If it is not, then Payables uses the system date at
time of import.
If the GL Date of an invoice is in a future period in Payables, you can account for the
invoice but you cannot pay it.
Note: Note the system searches at the GL Date Basis level and the GL
Date Basis option is set to Invoice Received Date, then Payables uses
the Invoice Date, and if the GL Date Basis option is set to Goods
Received Date, then Payables uses the system date at time of import.
Important: If you are using encumbrance accounting, you must enter a

GL Date in a period that is within the latest open encumbrance year.
(See also: Budgetary Control In Payables).
Validation: Must be in valid date format. The date
must be in an open accounting period.
ACCOUNTING_DATE
DESCRIPTION
Enter a description that you want to assign to the invoice distribution created from this
record. If you do not enter a value, and you match to a purchase order, then during
import the system uses the item description on the purchase order line to populate
AP_INVOICE_DISTRIBUTIONS_ALL.DESCRIPTION.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL. DESCRIPTION
PRORATE_ACROSS_FLAG
If you set this column to Y and this is a non-Item type line (Tax, Miscellaneous, or
Freight), then Payables will prorate the charge to all Item type lines with the same
LINE_GROUP_NUMBER as this line. If no line group number is specified, Payables
will prorate the charge to all Item lines. If this column is set to N, then Payables will not
prorate the cost and will create only one distribution.

Payables prorates tax for Tax type lines, freight for Freight type lines, and miscellaneous
for Miscellaneous type lines. Payables creates a distribution line for each line you
prorate the charge to. The system assigns the expense account of the Item line to the
new invoice distribution.
Validation: Line type is not Item.
Destination: None
FINAL_MATCH_FLAG
If you are certain that this is a final match against the purchase order, enter Y. Once you
validate a final matched invoice distribution, you cannot update the Final Match check
box in the Distributions window. Since you cannot final close purchase orders when
you are matching to receipts, if the invoice is matched to a receipt then import ignores
any value in this column.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.FINAL_
MATCH_FLAG
PO_HEADER_ID
If you enter the record in the Quick Invoices window, then you must provide a value
for this column by entering a value in the PO Number field, and you must specify the
supplier.
Internal identifier for the purchase order number. To match to a purchase order you can
enter either the PO_HEADER_ID or the PO_NUMBER.
Validation: This must be a valid value in
PO_HEADERS.PO_HEADER_ID. It must be for the same
supplier and cannot be final matched.
Destination: None
PO_NUMBER
Enter a purchase order number if you are matching to a purchase order. If you are
matching to a purchase order, you must enter the PO_NUMBER or the
PO_HEADER_ID.
If you match the invoice to a purchase order by entering a value here, then during
Payables Open Interface Import the system uses purchase order information to create
distributions and populate various columns in the
AP_INVOICE_DISTRIBUTIONS_ALL table. If you do not specify a supplier in the
AP_INVOICE_LINES_INTERFACE table, the PO_NUMBER value is used to derive
AP_INVOICE_DISTRIBUTIONS_ALL.VENDOR_ID, and if you do not specify the

supplier site, the PO_NUMBER value can be used to derive
AP_INVOICE_DISTRIBUTIONS_ALL.VENDOR_SITE_ID. If you enter supplier
information in another column and enter a value for PO_NUMBER, then the system
will use the supplier on the purchase order and ignore any other supplier information
you have entered.
Validation: This must be a valid purchase order number for the same
supplier, and the purchase order cannot be final matched
or inactive. If you specified a purchase order in
AP_INVOICES_INTERFACE, it must match this purchase
order number. The match option for the purchase order
shipment must be set to purchase order.

AP_INVOICES_ALL.PO_HEADER_ID.
PO_LINE_ID
Internal identifier for the purchase order line number. If you are matching to a purchase
order line you can enter either the PO_LINE_ID or the PO_LINE_NUMBER.
Validation: This must be a valid value for PO_LINES.PO_LINE_ID.
Destination: None
PO_LINE_NUMBER
If you want to match to a purchase order line, enter a value for PO_LINE_NUMBER or
PO_LINE_ID.
Alternatively, you can identify a purchase order line number by entering only an
ITEM_ID or an ITEM_DESCRIPTION. If you do this, the value you enter must exactly
match the ITEM_ID or ITEM_DESCRIPTION of exactly one purchase order line for the
PO_NUMBER. For example, you can match to a line by entering the
ITEM_DESCRIPTION "books" for an invoice that has exactly one line with an
ITEM_DESCRIPTION of "books".
Validation: This must be a valid value for PO_LINES.PO_LINE_NUM.
Destination: None
PO_LINE_LOCATION_ID
Internal identifier for purchase order shipment.
PO_LINE_LOCATIONS.LINE_LOCATION_ID for the
purchase order. PO shipment cannot be finally closed.

Destination: None
PO_SHIPMENT_NUM
Number of the purchase order shipment. If you are matching to a purchase order
shipment, enter a value for either PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID.
Alternatively, you can enter a value for SHIP_TO_LOCATION_CODE if exactly one
shipment on the purchase order has the SHIP_TO_LOCATION_CODE you specify. For
example, you enter a SHIP_TO_LOCATION_CODE of "Taipei" for a purchase order
with exactly one shipment with the location value of "Taipei".
Validation: This must be a valid value for
PO_LINE_LOCATIONS.SHIPMENT_NUM. PO shipment
cannot be finally closed.
Destination: None
PO_DISTRIBUTION_ID
Internal identifier for purchase order distribution number. If you are matching to a
purchase order distribution you can enter a value for PO_DISTRIBUTION_ID or
PO_DISTRIBUTION_NUM.
INVOICE_DISTRIBUTIONS.PO_DISTRIBUTION_ ID
Destination: None
PO_DISTRIBUTION_NUM
Purchase order distribution number. If you are matching to a distribution, you must
enter a value for PO_DISTRIBUTION_NUM or PO_DISTRIBUTION_ID.
Validation: Value must match a distribution number on the purchase
order and must be a valid value for
PO_DISTRIBUTIONS.PO_DISTRIBUTION_NUM.
Destination: None
INVENTORY_ITEM_ID
Inventory item identifier on the purchase order. Used during purchase order matching.
If you have limited purchase order information, you can enter an inventory item
number, and the system will attempt to match the invoice to a purchase order line. For
example, a supplier has one purchase order for PCs, that includes a single line for
monitors. If you want to match to the line with monitors and you don't know the
purchase order number, enter the proper INVENTORY_ITEM_ID for the monitors. The

system will match to the correct purchase order line for the monitors during import.
Validation: This value must match the purchase order
MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID for exactly
one line.
Destination: None
ITEM_DESCRIPTION
Exact description of the item on the purchase order. Used during purchase order line
matching.
If you have limited purchase order information, you can enter a description in the
column, and the system will attempt to match the invoice to a purchase order line. For
example, if a purchase order has one line for books and one line for software, but you
don't know the line number, you can enter the exact description for the books, and the
system will match to the correct purchase order line.
Validation: The description must match
PO_LINES.ITEM_DESCRIPTION.
Destination: None
QUANTITY_INVOICED
Number of units invoiced. Used for purchase order matching. For example if there are 5
chairs on the invoice, enter 5. If you enter a value for UNIT_PRICE and do not enter a
value for QUANTITY_INVOICED, the system will derive a value for
QUANTITY_INVOICED during Payables Open Interface Import
(QUANTITY_INVOICED = AMOUNT / UNIT PRICE).
If the Invoice Match option on the purchase order shipment is Receipt, Import reviews
all receipts that have unbilled quantities for the purchase order shipment. Import then
matches the billed quantity on the invoice to these receipts starting with the oldest
receipt that has an unbilled quantity. Import then fills each unbilled receipt quantity up
to the amount of the invoice billed quantity. If the invoice quantity exceeds all available
unbilled receipt quantities for the purchase order shipment, import overbills the newest
unbilled quantity by the remaining amount.
Validation: This value must be a positive number if AMOUNT for this
line is positive, and a negative number if AMOUNT is
negative.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.QUANTITY_INVOI
CED

SHIP_TO_LOCATION_CODE
If you want to match to a purchase order shipment and have not entered a value for
either PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID, you can enter a value for
SHIP_TO_LOCATION_CODE if exactly one shipment on the purchase order has the
SHIP_TO_LOCATION_CODE you specify. For example, you enter a
SHIP_TO_LOCATION_CODE of "Taipei" for a purchase order with exactly one
shipment with the value "Taipei".
Validation: This must be an existing, active value for
PO_LINE_LOCATIONS.SHIP_TO_LOCATION_ID
Destination: None
UNIT_PRICE
Unit price of the distribution line item(s). Used for purchase order matching. If you
enter a value for UNIT_PRICE and do not enter a value for QUANTITY_INVOICED,
the system will derive a value for QUANTITY_INVOICED during Payables Open
Interface Import (QUANTITY_INVOICED = AMOUNT / UNIT PRICE).
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.UNIT_ PRICE
DISTRIBUTION_SET_ID
Internal identifier for the Distribution Set. If you enter a value for
DISTRIBUTION_SET_NAME or DISTRIBUTION_SET_ID, then during import Payables
automatically creates distributions for you based on the Distribution Set.
Do not enter a value here if you are matching this line to a purchase order, if you are
prorating, or if you enter an account.
AP_DISTRIBUTION_SETS.DISTRIBUTION_SET_ ID
Destination: None
DISTRIBUTION_SET_NAME
Name of the Distribution Set. You define Distribution Sets in the Distribution Sets
window. If you enter a Distribution Set name, then during Payables Open Interface
Import, Payables automatically creates distributions for you based on the Distribution
Set. If you enter a value here, you do not need to enter the corresponding value for
DISTRIBUTION_SET_ID.
Do not enter a value in this column if you are matching to a purchase order, if you are
prorating, or if you provide an account.

AP_DISTRIBUTION_SETS.DISTRIBUTION SET_NAME. If
you are matching to a purchase order and you enter a
value in this column, Payables Open Interface Import will
reject the invoice.
Destination: None
DIST_CODE_CONCATENATED
The GL account to which the distribution amount will be charged.
For information on how Payables Open Interface Import builds an account based on the
value you enter here, see: Account Overlay in Payables Open Interface Import, page A-
143.
Validation: The account code combination must be valid and in the
exact flexfield structure you have defined for your Set of
Books, and must match a value for
GL_CODE_COMBINATIONS.CODE_
COMBINATION_ID.
Destination: None. This value may be used to enter a value for

AP_INVOICE_DISTRIBUTIONS_ALL.DIST_
CODE_COMBINATION_ID
DIST_CODE_COMBINATION_ID
Internal identifier for GL account to which the distribution amount will be charged.
If you enter Projects information in the Quick Invoices, the Quick Invoices window will
automatically build the account for you. If you enter records in any way other than the
Quick Invoices window, you must provide this value.
For information on how Payables Open Interface Import builds an account based on the
value you enter here, see: Account Overlay in Payables Open Interface Import, page A-
143.
Validation: The account code combination must be valid and in the
exact flexfield structure you have defined for your Set of
Books.
Destination: AP_INVOICES_ALL.DIST_CODE_ COMBINATION_ID
AWT_GROUP_ID
Internal identifier associated with the automatic withholding tax group name. If you
want to assign a withholding tax group to the line, you do not need to enter a value
here if you enter a value for AWT_GROUP_NAME.

Validation: This must be a valid, active value in
AP_AWT_GROUPS.GROUP_ID
Destination: None
AWT_GROUP_NAME
Automatic withholding tax group name. When you enter a withholding tax group for a
line, then all the withholding taxes in the group are applied to the line. You define
automatic withholding tax group names in the Withholding Tax Groups window. If
you do not enter a value for this column, then during Payables Open Interface Import
the system will use the value you entered for
AP_INVOICES_INTERFACE.AWT_GROUP_NAME. If you did not enter a value, then
the system uses the supplier site value if there is one.
Validation: This must be a valid, active value in
AP_AWT_GROUPS.NAME
Destination: None
LAST_UPDATED_BY
Enter the ID of the person who last updated this record (usually the same value as
CREATED_BY).
If you do not enter a value here, then during Payables Open Interface Import the system
will use the userid of the person who submits Payables Open Interface Import.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.LAST_
UPDATED_BY
LAST_UPDATE_DATE
Enter the last update date for this record (usually the same date as CREATION_DATE).
Payables uses this date for reference and audit purposes only. When the import
program creates an invoice from a record in this table, it does not use this date as the
last update date for the invoice; it uses the system date at the time you submit Payables
Open Interface Import.
Destination: None
LAST_UPDATE_LOGIN
The last update date for this record. Usually the same date as the CREATION_DATE. If

you enter a value in this column, the system uses it to populate
AP_INVOICE_DISTRIBUTIONS_ALL.AP_LAST_ UPDATE_LOGIN. If you do not
enter a value, then during Payables Open Interface Import, the system will use the
system date.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.AP_LAST_UPDATE
_LOGIN
CREATED_BY
Enter the userid of the person or organization who loads this record into the table.
Payables Open Interface Import transfers this userid to the
AP_INVOICE_DISTRIBUTIONS_ALL table during import so that the creator of the
record becomes the invoice and scheduled payment creator. If you do not enter a value,
then during import the system will use the userid of the person who submits Payables
Open Interface Import.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.CREATED_BY
CREATION_DATE
Enter the date on which you load this record into the table. Payables uses this date for
reference and audit purposes. When Payables Open Interface Import creates an invoice
from this record, it does not use this date as the creation date for the invoice
distributions; it uses the system date at the time you submit Payables Open Interface
Import.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.CREATION_DATE
ATTRIBUTE_CATEGORY
Enter the Descriptive Flexfield category for the Descriptive Flexfield information you
want to import for an invoice distribution.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.ATTRIBUTE_CATE
GORY
ATTRIBUTE [1-15]
Enter Descriptive Flexfield information that you want to import for an invoice

distribution. The structure of the information you enter in these columns (datatypes,
value sets) must match the structure of the Descriptive Flexfield segments you have
defined for your invoice distributions or you will experience validation problems when
you try to access the information in the invoice windows.
If you are using a Distribution Set that has a descriptive flexfield, any data you enter
here will overwrite the descriptive flexfield on the Distribution Set.
If a line is purchase order matched and the Transfer PO Descriptive Flexfield
Information Payables option is enabled, then import uses the purchase order values for
any corresponding open interface attribute columns that are null. However, if you enter
data for any open interface attribute then that value is used on the invoice instead of the
purchase order value.
If the Transfer PO Descriptive Flexfield Information Payables option is disabled, then
the purchase order flexfield values are ignored during import.
The interface program inserts invoice data into the AP_INVOICE_LINES_ALL table
after import.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.ATTRIBUTE [1-15]

AP_INVOICE_LINES_ALL.ATTRIBUTE [1-15]
Enter the Descriptive Flexfield category for the descriptive flexfield information you
want to import.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.GLOBAL_
ATTRIBUTE_CATEGORY
GLOBAL ATTRIBUTE [1-20]

Validation: If you are using a localization, you must enter appropriate
values in this flexfield or the invoice will be rejected by
import. For more information, see your localization user's
guide.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.GLOBAL_

ATTRIBUTE[1-20]
PO_RELEASE_ID
Internal identifier for a purchase order release number. If you want to match to a
blanket purchase order you must supply either the RELEASE_NUM or the
PO_RELEASE_ID, and provide a shipment number. You can also optionally provide a
line number.
Validation: This value must match a valid value in
PO_RELEASES.PO_RELEASE_ID.
Destination: None
RELEASE_NUM
Release number of a blanket purchase order. Used during purchase order matching. If
you want to match to a blanket purchase order you must supply either the
RELEASE_NUM or the PO_RELEASE_ID.
PO_RELEASES.RELEASE_NUM.
Destination: None
ACCOUNT_SEGMENT
If you want to override the account segment in the account for this line, enter a value
here. Payables will override the account segment with this value during import. See:
Account Overlay in Payables Open Interface Import, page A-143.
Validation: The new account code must be valid.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.CODE_
COMBINATION_ID
BALANCING_SEGMENT
If you want to override the balancing segment in the account, enter a value here.
Payables will override the balancing segment with this value during import. See:
Account Overlay in Payables Open Interface Import, page A-143.
Validation: The account code must be valid.
COMBINATION_ID

COST_CENTER_SEGMENT
If you want to override the cost center in the account, enter a value here. Payables will
override the cost center with this value during import. See: Account Overlay in
Payables Open Interface Import, page A-143.
Validation: The account code must be valid.
COMBINATION_ID
Projects Columns
Enter project information from Oracle Projects in the following columns if you want to
associate the invoice distribution (created from this record) with a project in Oracle
Projects. If Projects is installed and you provide information for the projects columns,
then Projects will build the expense account based on this information.
If the invoice is matched to a purchase order and the purchase order has project related
information, then during import Payables automatically populates the Projects related
columns in AP_INVOICES and AP_INVOICE_DISTRIBUTIONS_ALL.
• PROJECT_ID
• TASK_ID
• EXPENDITURE_TYPE
• EXPENDITURE_ITEM_DATE
• EXPENDITURE_ORGANIZATION_ID
• PA_ADDITION_FLAG
In addition, Oracle Projects uses the following columns to transfer invoice data:
• PA_QUANTITY
• PA_CC_AR_INVOICE_ID
• PA_CC_AR_INVOICE_LINE_NUM
• REFERENCE_1
• REFERENCE_1
• PA_CC_PROCESSED_CODE
Validation: The information provided in these columns is

validated against Oracle Projects.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.[Projects
Columns]
USSGL_TRANSACTION_CODE
Enter the default transaction code you want to assign to an invoice.
Open Interface Import imports any USSGL information that you load into the interface
tables and assigns the information to the invoices it creates.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.USSGL_
TRANSACTION_CODE
STAT_AMOUNT
Statistical quantity based on the unit of measure. For example, if your unit of measure is
barrels, you can enter the number of barrels here. See also: Invoice Distribution
Statistics in Oracle General Ledger.
Validation: You must also enter a valid value for
PO_UNIT_OF_MEASURE.
Destination: AP_INVOICES_DISTRIBUTIONS_ALL.STAT_ AMOUNT
TYPE_1099
Income tax type, for a United States 1099 reportable supplier. You define a supplier as
federally reportable by enabling the Federal option in the Suppliers window. Enter a
1099 Miscellaneous Tax Type.
See:Entering Invoices for Suppliers Subject to Income Tax Reporting Requirements,
Oracle Payables User Guide
If you leave this value null and match to a purchase order, then this value always
defaults from the purchase order (even if that value is null and the supplier now has a
value).
For unmatched invoices, if you do not use a Distribution Set to create invoice
distributions, Payables uses the supplier's income tax type as the default value. If you
use a Distribution Set to create invoice distributions, Payables uses the default income
tax type from the Distribution Set as the default value. You can enter this field
regardless of whether the supplier is defined as a 1099 supplier. Payables uses this
information when you submit the 1099 Payments Report and the 1099 Form Reports.
See also: 1099 Reporting Overview, Oracle Payables User Guide.
You can update this field of the imported invoice in the Distributions window even

after you have accounted for a distribution. You can use the Update Income Tax Details
Utility to make adjustments to many distributions at once. See: Update Income Tax
Details Utility and Report, Oracle Payables User Guide.
Validation: The value must be a valid and active value in the
AP_INCOME_TAX_TYPES table (MISC types 1-14, except
MISC9, MISC11 and MISC12), and the supplier for this
record must be defined as federally reportable.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.TYPE_1099
INCOME_TAX_REGION
If the supplier is a 1099 supplier, enter the supplier's reporting region. If you do not
enter a value, and you have enabled the Use Pay Site Tax Region Payables option, then
during import the system uses the income tax region of the supplier site. If you do not
enter a value and you have instead entered a value for the Income Tax Region Payables
option, then during import the system will use that value as the default.
Validation: You must also enter a value for INCOME_TAX_TYPE.
Destination: AP_INVOICES_DISTRIBUTIONS.INCOME_TAX_REGIO
N
ASSETS_TRACKING_FLAG
Enter Y if the invoice distribution should be imported into Oracle Assets using the
Create Mass Additions for Assets program. If you do not enter a value, and the line has
an Asset type account entered for it, then Payables will automatically set this value to Y
during import.
Validation: The account must be set up as an existing asset category,
and it must be either an asset clearing account or a
construction-in-progress (CIP) clearing account.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.ASSETS_
TRACKING_FLAG
PRICE_CORRECTION_FLAG
Use a price correction when a supplier sends an invoice for a change in unit price for an
invoice that you have matched to a purchase order. You record a price correction by
entering a Standard or Credit invoice, setting this flag to Y, and entering the
base-matched invoice in the PRICE_CORRECT_INV_NUM column.
Payables records and updates the invoiced unit price of previously matched purchase
order shipment or distributions without adjusting the quantity billed so you can track
price variances. Payables also updates the amount billed on the originally matched

purchase order distributions.
See also: Price Corrections, Oracle Payables User Guide.
Validation: None
Destination: None
ORG_ID
Validation: None
Destination: None
RECEIPT_NUMBER
If you are matching to a purchase order receipt, then enter the receipt number.
Validation: A purchase order and receipt for the same supplier,
supplier site, and currency as the invoice you are entering
must be approved and open. Also, the Invoice Match
option for the purchase order shipment you are matching
to is set to Receipt.
Destination: This value is used to enter:

AP_INVOICE_DISTRIBUTIONS_ALL.
RCV_TRANSACTION_ID
RECEIPT_LINE_NUMBER
If you are matching to a purchase order receipt, then you can specify the receipt line
you are matching to.
Validation: A purchase order and receipt for the same supplier,
supplier site, and currency as the invoice you are entering
must be approved and open. Also, the Invoice Match
option for the purchase order shipment you are matching
to is set to Receipt. This must be a valid line number for the
receipt.
Destination: None
MATCH_OPTION
Indicates if a match is to a purchase order or receipt. When you match to a purchase
order or receipt in the Quick Invoices window, then the system populates this field
based on the value of the purchase order shipment.

Validation: The value must match the value specified in
PO_SHIPMENTS.MATCH_OPTION.
Destination: None
PACKING_SLIP
This column is not currently used.
Validation: None
Destination: None
RCV_TRANSACTION_ID
This value specifies a receipt record for matching.This value is used to match Oracle
e-Commerce Gateway invoices to receipts.
Validation: This value must be a valid, existing value for
RCV_TRANSACTIONS. RCV_TRANSACTION_ID
RCV_TRANSACTION_ID
PA_CC_AR_INVOICE_ID
Identifier of the corresponding receivable intercompany invoice in Oracle Receivables
Validation: None
Destination: None
PA_CC_AR_INVOICE_LINE_NUM
Line number of the corresponding receivable intercompany invoice in Oracle
Receivables
Validation: None
Destination: None
REFERENCE_1 - 2
These columns references records in another application
Validation: None
Destination: None

PA_CC_PROCESSED_CODE
This column indicates the processing status of this invoice line by Oracle Projects in the
Receiver Operating Unit.
Validation: None
Destination: None
TAX_CODE_ID
Internal identifier for the tax code. You can enter a value for either the TAX_CODE or
TAX_CODE_ID.
Validation: This must be a valid value for
AP_TAX_CODES_ALL.TAX_ID. Further validations are
the same as those for TAX_CODE.
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.TAX_CODE_ID
CREDIT_CARD_TRX_ID
This column is populated when credit card transactions for expense reports entered in
Oracle Internet Expenses are imported to Payables.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL.CREDIT_
CARD_TRX_ID
AWARD_ID
This value is used only if you use Oracle Grants Management.
Validation: None
Destination: AP_INVOICE_DISTRIBUTIONS_ALL. AWARD_SET_ID
VENDOR_ITEM_NUM
Supplier item number on the purchase order. Used during purchase order matching. If
you have limited purchase order information, you can enter a supplier item number in
the column and the system will attempt to match the invoice to a purchase order line.
PO_LINES_ALL.VENDOR_PRODUCT_NUM for exactly
one line.

Destination: None
TAXABLE_FLAG
Y indicates that the line is taxable. Import uses this value for invoices from XML
Gateway
Validation: None
Destination: None
PRICE_CORRECT_INV_NUM
If you have set the PRICE_CORRECTION_FLAG to Y to indicate that this is a price
correction, then you must enter the number of the base-matched invoice here. For more
information, see: Price Corrections, Oracle Payables User Guide.
Validation: This value must be a valid purchase order matched invoice
with a type of either Standard or Mixed. You must provide
sufficient purchase order information for the system to
identify the purchase order amount that you want to
update.
Destination: We use this to derive

AP_INVOICE_DISTRIBUTIONS.PRICE_CORRECT_INV_I
D
EXTERNAL_DOC_LINE_REF
This column is an internal document reference number from Accounts Receivables
system. Used for XML invoices.
Validation: None
Destination: None
SERIAL_NUMBER
This column is the serial number for an item.
Validation: None
Destination: None
MANUFACTURER
This column is the name of the manufacturer.

Validation: None
Destination: None
MODEL_NUMBER
This column is the model information.
Validation: None
Destination: None
WARRANTY_NUMBER
This column is a warranty number.
Validation: None
Destination: None
DEFERRED_ACCTG_FLAG
This column is a flag that indicates whether to generate deferred accounting for this
line.
Validation: None
Destination: None
DEF_ACCTG_START_DATE
This column is the start date of the deferred expense period.
Validation: None
Destination: None
DEF_ACCTG_END_DATE
This column is the end date of the deferred expense period.
Validation: None
Destination: None
DEF_ACCTG_NUMBER_OF_PERIODS
This column is the number of periods to generate deferred expenses. Used in
combination with PERIOD_TYPE. Alternative to END_DATE

Validation: None
Destination: None
DEF_ACCTG_PERIOD_TYPE
This column is the period type used in combination with NUMBER_OF_PERIODS to
generate deferred expenses.
Validation: XLA_LOOKUPS with lookup type
XLA_DEFERRED_PERIOD_TYPE
Destination: None
UNIT_OF_MEAS_LOOKUP_CODE
This column is the Unit of Measure for quantity invoiced.
Validation: MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE
Destination: None
PRICE_CORRECT_INV_LINE_NUM
This column is the invoice line subject to the price correction.
Validation: None
Destination: None
ASSET_BOOK_TYPE_CODE
This column is the Asset Book Defaults to the distributions candidate for transfer to
Oracle Assets
Validation: None
Destination: None
ASSET_CATEGORY_ID
This column is the Asset Category Defaults to the distributions candidate for transfer to
Oracle Assets
Validation: None
Destination: None

REQUESTER_ID
This column is the Requester identifier. Valid values from active HR employees.
Validation: PER_ALL_PEOPLE_F.PERSON_ID
Destination: None
REQUESTER_FIRST_NAME
This column is the first name of the employee who requested goods or services on the
invoice line. This value is used to derive the requester ID. If you use Invoice Approval
Workflow then you can define rules that use therequester ID to generate a hierarchical
list of approvers for the line
Validation: None
Destination: None
REQUESTER_LAST_NAME
This column is the last name of the employee who requested goods or services on the
invoice line. This value is used to derive the requester ID. If you use Invoice Approval
Workflow then you can define rules that use therequester ID to generate a hierarchical
list of approvers for the line
Validation: None
Destination: None
REQUESTER_EMPLOYEE_NUM
This column is the employee number of the employee who requested goods or services
on the invoice line. This value is used to derive the requester ID. If you use Invoice
Approval Workflow then you can define rules that use therequester ID to generate a
hierarchical list of approvers for the line
Validation: None
Destination: None
APPLICATION_ID
This column is the Application Identifier
Validation: None
Destination: None

PRODUCT_TABLE
This column is the Product source table name,
Validation: None
Destination: None
REFERENCE_KEY1 - 5
These columns are primary keys that will uniquely identify a record in other products
view
Validation: None
Destination: None
PURCHASING_CATEGORY
This column is the item category concatenated segments
Validation: None
Destination: None
PURCHASING_CATEGORY_ID
This column is the item category unique identifier
Validation: None
Destination: None
COST_FACTOR_ID
This column is the identifier of the cost component class. Cost Component Classes are
used to identify the individual buckets or component costs that make up the total cost
of an item, for example, direct material costs, freight costs, labor costs, production or
conversion costs and so on.
Validation: None
Destination: None
COST_FACTOR_NAME
This column is the cost component class name. Cost Component Classes are used to
identify the individual buckets or component costs that make up the total cost of an
item, for example, direct material costs, freight costs, labor costs, production or

conversion costs and so on.
Validation: None
Destination: None
CONTROL_AMOUNT
This column is an optional, user-enterable value to ensure that the calculated tax will be
the same as on the physical document.
Validation: None
Destination: None
ASSESSABLE_VALUE
This column is the user-enterable amount to be used as taxable basis
Validation: None
Destination: None
DEFAULT_DIST_CCID
This column is a Tax Driver. It is a code combination identifier of the GL account
associated with the transaction line. Note that this is necessary to support the Account
Method VAT feature.
Validation: None
Destination: None
PRIMARY_INTENDED_USE
This column is a Tax Driver. It is the purpose for which a product may be used. The
actual use will be stored at the distribution level.
Validation: None
Destination: None
SHIP_TO_LOCATION_ID
This column is a Tax Driver. It is the ship to location ID. Value entered by user only if
line is not PO matched.
Validation: None

Destination: None
PRODUCT_TYPE
This column is a Tax Driver. It is the type of product. Possible values are: Goods,
Service. This value will default from Inventory Item attributes. Otherwise, value will be
entered by user.
Validation: None
Destination: None
PRODUCT_CATEGORY
This column is a Tax Driver. It is a product category.
Validation: None
Destination: None
PRODUCT_FISC_CLASSIFICATION
This column is a Tax Driver. It is a Product Fiscal Classification.
Validation: None
Destination: None
USER_DEFINED_FISC_CLASS
This column is a Tax Driver. It is a Fiscal Classification.
Validation: None
Destination: None
TRX_BUSINESS_CATEGORY
This column is a Tax Driver. It is a transactions category assigned by user.
Validation: None
Destination: None
TAX_REGIME_CODE
This column is a Tax Regime Code. The set of tax rules that determines the treatment of
one or more taxes administered by a tax authority. e.g., VAT Regime in Argentina.

Validation: None
Destination: None
TAX
This column is a classification of a charge imposed by a government through a fiscal or
tax authority.
Validation: None
Destination: None
TAX_JURISDICTION_CODE
This column is the Internal ID of the Tax Jurisdiction
Validation: None
Destination: None
TAX_STATUS_CODE
This column is the Tax status code. e.g., taxable standard rate, zero rated, exempt,
non-taxable.
Validation: None
Destination: None
TAX_RATE_ID
This column is the Internal identifier for tax rate effective on the invoice date
Validation: None
Destination: None
TAX_RATE_CODE
This column is the tax rate name associated with tax rate identifier. Tax_rate_id is
unique while a tax_rate_code may have different tax rates based on date ranges.
Validation: None
Destination: None

TAX_RATE
This column is the rate specified for a tax status in effect for a period of time.
Validation: None
Destination: None
INCL_IN_TAXABLE_LINE_FLAG
This column is the flag to indicate if the amount in the tax line is included or not in the
taxable line.
Validation: None
Destination: None
CALC_TAX_DURING_IMPORT_FLAG
This column is the flag to indicate whether tax should be calculated or not for the
imported invoice.
Validation: None
Destination: None
SOURCE_APPLICATION_ID
This column is the source document application identifier
Validation: None
Destination: None
SOURCE_ENTITY_CODE
This column is the source document entity code
Validation: None
Destination: None
SOURCE_EVENT_CLASS_CODE
This column is the source document event class code
Validation: None
Destination: None

SOURCE_TRX_ID
This column is the source document transaction identifier
Validation: None
Destination: None
SOURCE_LINE_ID
This column is the identifier of the lowest level for which Tax is calculated
Validation: None
Destination: None
SOURCE_TRX_LEVEL_TYPE
This column is the source document transaction level type
Validation: None
Destination: None
TAX_CLASSIFICATION_CODE
This column is the Tax Classification Code
Validation: None
Destination: None
AP_SUPPLIERS_INT
VENDOR_INTERFA NOT NULL NUMBER(15) Required

CE_ID
VENDOR_NAME VARCHAR2(240) Required
VENDOR_NAME_A VARCHAR2(320) N/A

LT
SEGMENT1 VARCHAR2(30) Conditionally

required

SUMMARY_FLAG VARCHAR2(1) N/A
ENABLED_FLAG VARCHAR(1) Column used by

Oracle Purchasing
EMPLOYEE_ID NUMBER N/A
VENDOR_TYPE_LO VARCHAR2(30) N/A

OKUP_CODE
CUSTOMER_NUM VARCHAR2(25) N/A
ONE_TIME_FLAG VARCHAR2(1) N/A
MIN_ORDER_AMO NUMBER N/A

UNT
SHIP_TO_LOCATIO NUMBER N/A

N_ID

N_CODE
BILL_TO_LOCATIO NUMBER N/A

N_ID
BILL_TO_LOCATIO VARCHAR2(60) N/A

N_CODE
SHIP_VIA_LOOKUP VARCHAR2(25) N/A

_CODE
FREIGHT_TERMS_L VARCHAR2(25) N/A

OOKUP_CODE
FOB_LOOKUP_COD VARCHAR2(25) N/A

E
TERMS_ID NUMBER N/A
TERMS_NAME VARCHAR2(50) N/A

SET_OF_BOOKS_ID NUMBER N/A
ALWAYS_TAKE_DIS VARCHAR2(1) N/A

C_FLAG
PAY_DATE_BASIS_L VARCHAR2(25) Required but will

OOKUP_CODE default
PAY_GROUP_LOOK VARCHAR2(25) N/A

UP_CODE
PAYMENT_PRIORIT NUMBER Required but will

Y default
INVOICE_CURRENC VARCHAR2(15) N/A

Y_CODE

CY_CODE
INVOICE NUMBER N/A

_AMOUNT_LIMIT
HOLD_ALL_PAYME VARCHAR2(1) N/A

NTS_FLAG
HOLD_FUTURE_PA VARCHAR2(1) N/A

YMENTS_FLAG
HOLD_REASON VARCHAR2(240) N/A
DISTRIBUTION_SET NUMBER N/A

_ID
DISTRIBUTION_SET VARCHAR2(50) N/A

_NAME
ACCTS_PAY_CODE_ NUMBER N/A

COMBINATION_ID
PREPAY_CODE_CO NUMBER N/A

MBINATION_ID

NUM_1099 VARCHAR2(30) N/A
ORGANIZATION_T VARCHAR2(25) N/A

YPE_LOOKUP_COD
E
VAT_CODE VARCHAR2(15) N/A
START_DATE_ACTI DATE N/A

VE
END_DATE_ACTIVE DATE N/A
MINORITY_GROUP_ VARCHAR2(25) N/A

LOOKUP_CODE
PAYMENT_METHO VARCHAR2(25) Required but will

D_LOOKUP_CODE default
WOMEN_OWNED_F VARCHAR2(1) N/A

LAG
SMALL_BUSINESS_F VARCHAR2(1) N/A

LAG
STANDARD_INDUS VARCHAR2(25) N/A

TRY_CLASS
HOLD_FLAG VARCHAR2(1) N/A
PURCHASING_HOL VARCHAR2(240) N/A

D_REASON
HOLD_BY NUMBER(9) N/A
HOLD_DATE DATE N/A
TERMS_DATE_BASI VARCHAR2(25) Required but will

S default

INSPECTION_REQU VARCHAR2(1) N/A

IRED_FLAG/RECEIP
T_REQUIRED_FLAG
QTY_RCV_TOLERA NUMBER(25) Column used by

NCE Oracle Purchasing
QTY_RCV_EXCEPTI VARCHAR2(25) Column used by

ON_CODE Oracle Purchasing
ENFORCE_SHIP_TO VARCHAR2(25) Column used by

_LOCATION_CODE Oracle Purchasing
DAYS_EARLY_RECE NUMBER Column used by

IPT_ALLOWED Oracle Purchasing
DAYS_LATE_RECEI NUMBER Column used by

PT_ALLOWED Oracle Purchasing
RECEIPT_DAYS_EX VARCHAR2 Column used by

CEPTION_CODE Oracle Purchasing
RECEIVING_ROUTI NUMBER Column used by

NG_ID Oracle Purchasing
ALLOW_SUBSTITUT VARCHAR2(1) Column used by

E_RECEIPTS_FLAG Oracle Purchasing
ALLOW_UNORDER VARCHAR2(1) Column used by

ED_RECEIPTS_FLAG Oracle Purchasing
HOLD_UNMATCHE VARCHAR2(1) N/A

D_INVOICES_FLAG

NT_FLAG
AP_TAX_ROUNDIN VARCHAR2(1) N/A

G_RULE
AUTO_TAX_CALC_ VARCHAR2(1) N/A

FLAG


OVERRIDE
AMOUNT_INCLUD VARCHAR2(1) N/A

ES_TAX_FLAG
TAX_VERIFICATIO DATE N/A

N_DATE
NAME_CONTROL VARCHAR2(4) N/A
STATE_REPORTABL VARCHAR2(1) N/A

E_FLAG
FEDERAL_REPORT VARCHAR2(1) N/A

ABLE_FLAG
ATTRIBUTE_CATEG VARCHAR2(30) N/A

ORY
ATTRIBUTES (1-15) VARCHAR2(150) N/A
VAT_REGISTRATIO VARCHAR2(20) N/A

N_NUM
AUTO_CALCULATE VARCHAR2(1) N/A

_INTEREST_FLAG
EXCLUDE_FREIGHT VARCHAR2(1) N/A

_FROM_DISCOUNT
TAX_REPORTING_N VARCHAR2(80) N/A

AME
ALLOW_AWT_FLA VARCHAR2(1) N/A

G
AWT_GROUP_ID NUMBER(15) N/A
AWT_GROUP_NAM VARCHAR2(25) N/A

E

GLOBAL_ATTRIBUT VARCHAR2(150) N/A

ES (1-20)

E_CATEGORY
EDI_TRANSACTION VARCHAR2(25) N/A

_HANDLING
EDI_PAYMENT_ME VARCHAR2(25) N/A

THOD
EDI_PAYMENT_FOR VARCHAR2(25) N/A

MAT
EDI_REMITTANCE_ VARCHAR2(25) N/A

METHOD
EDI_REMITTANCE_I VARCHAR(256) N/A

NSTRUCTION
BANK_CHARGE_BE VARCHAR2(1) Conditionally

ARER required
MATCH_OPTION VARCHAR2(1) Required but will

default
FUTURE_DATED_P NUMBER(15) N/A

AYMENT_CCID
CREATE_DEBIT_ME VARCHAR2(25) N/A

MO_FLAG
OFFSET_TAX_FLAG VARCHAR2(1) N/A
REJECT_CODE VARCHAR2(2000) N/A

ECE_TO_LOCATION VARCHAR2(60) Trading partner

_CODE location code for
e-Commerce
Gateway
IBY_BANK_CHARG VARCHAR2(30) Bearer of bank charge

E_BEARER cost.
BANK_INSTRUCTIO VARCHAR2(30) Code of first bank

N1_CODE instruction
BANK_INSTRUCTIO VARCHAR2(30) Code of second bank

N2_CODE instruction
BANK_INSTRUCTIO VARCHAR2(255) Additional bank

N_DETAILS instruction details
PAYMENT_REASON VARCHAR2(30) Payment reason code.

_CODE
PAYMENT_REASON VARCHAR2(240) Fee text field

_COMMENTS available for entering
a reason.
PAYMENT_TEXT_M VARCHAR2(150) Text message for use

ESSAGE1 in payment
processing.

ESSAGE2 in payment
processing.

ESSAGE3 in payment
processing.
DELIVERY_CHANN VARCHAR2(30) Default delivery

EL_CODE channel code.
PAYMENT_FORMA VARCHAR2(150) Default delivery

T_CODE channel code.

SETTLEMENT_PRIO VARCHAR2(30) Priority for payments.

RITY
PAYMENT_METHO VARCHAR2(30) Settlement payment

D_CODE method identifier.
VENDOR_INTERFACE_ID
This is the unique identifier for records in this table. A value is required in this column
and should be derived from AP_SUPPLIERS_INT_S.
Validation: N/A
Destination: None
VENDOR_NAME
This is the unique name used to identify the supplier. You must provide a value for this
column.
Validation: Check perfomed for duplicates against
PO_VENDORS.VENDOR_NAME.
Destination: PO_VENDORS.VENDORS_NAME
VENDOR_NAME_ALT
This is the alternate name by which the supplier is identified. This column was
designed for use in Japan for the entry of both Kanji and Kana values for the supplier
name.
Validation: None
Destination: PO_VENDORS.VENDOR_NAME_ALT
SEGMENT1
This is the Supplier Number. If the Supplier Number entry option in the Financials
Options window is set to 'Automatic', the Suppliers Open Interface Import Program
assigns the number. Please note that if a value is provided in the interface table, this
value will be ignored and the next automatic number will be assigned to the supplier.
Validation: If 'Manual' option is used, check is performed for duplicate
against PO_VENDOR.SEGMENT1.

Destination: PO_VENDORS.SEGMENT1
SUMMARY_FLAG
This column is used internally and defaults to 'N'.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'
Destination: PO_VENDORS.SUMMARY_FLAG
ENABLED_FLAG
This column is used by some Oracle Purchasing routines to determine if a supplier is
enabled and defaults to 'Y'.
Destination: PO_VENDORS.ENABLED_FLAG
EMPLOYEE_ID
This is the internal identifier for the employee that corresponds to an 'EMPLOYEE' type
supplier. A value for this field is valid if VENDOR_TYPE_LOOKUP_CODE =
'EMPLOYEE'
Validation: HR_EMPLOYEES_CURRENT_V.PERSON_ID
Destination: PO_VENDORS.EMPLOYEE_ID
VENDOR_TYPE_LOOKUP_CODE
This is the type of supplier.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'VENDOR
TYPE'
Destination: PO_VENDORS.VENDOR_TYPE_LOOKUP_CODE
CUSTOMER_NUM
This is the number by which the supplier identifies the user's enterprise.
Validation: None
Destination: PO_VENDORS.CUSTOMER_NUM
ONE_TIME_FLAG
This flag is enabled if repeat business is not anticipated with the supplier. Defaults to

'N'.
Destination: PO_VENDORS.ONE_TIME_FLAG
MIN_ORDER_AMOUNT
This is the minimum purchase order amount for the supplier.
Validation: None
Destination: PO_VENDORS.MIN_ORDER_AMOUNT
SHIP_TO_LOCATION_ID
This is the unique identifier for the location where the supplier sends shipments for
goods and services. This corresponds to SHIP_TO_LOCATION_CODE. A value can be
provided for either or both columns. If both are provided, the system will check to
ensure that the values match a valid 'ID-CODE' combination. This identifier defaults
from FINANCIALS_SYSTEM_PARAMS_ALL.SHIP_TO_LOCATION_ID.
Validation: HR_LOCATIONS_ALL.LOCATION_ID. The
HR_LOCATIONS_ALL.SHIP_TO_SITE_FLAG must be Y.
Destination: PO_VENDORS.SHIP_TO_LOCATION_ID
This is the location where the supplier sends shipments for goods and services. This
corresponds to SHIP_TO_LOCATION_ID. A value can be provided for either or both
columns. If both are provided, the system will check to ensure that the values match a
valid 'ID-CODE' combination.
Validation: HR_LOCATIONS_ALL.LOCATION_CODE.
HR_LOCATIONS_ALL. SHIP_TO_SITE_FLAG must be 'Y'.
Destination: None. The value of

PO_VENDORS.SHIP_TO_LOCATION_ID may be derived
from this column.
BILL_TO_LOCATION_ID
This is the unique identifier for the location where the supplier sends invoices for goods
and services. This corresponds to BILL_TO_LOCATION_CODE. A value can be
ensure that the values match a valid 'ID-CODE' combination. This identifier defaults
from FINANCIALS_SYSTEM_PARAMS_ALL.BILL_TO_LOCATION_ID.

HR_LOCATIONS_ALL.BILL_TO_SITE_FLAG must be 'Y'.
Destination: PO_VENDORS.BILL_TO_LOCATION_ID
BILL_TO_LOCATION_CODE
This is the location where the supplier sends invoices for goods and services. This
corresponds to BILL_TO_LOCATION_ID. A value can be provided for either or both
valid ID-CODE combination.
Validation: HR_LOCATIONS_ALL.LOCATION_CODE. The

PO_VENDORS.BILL_TO_LOCATION_ID may be derived
from this column.
SHIP_VIA_LOOKUP_CODE
This is the default freight carrier that is used with the supplier. This value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.SHIP_VIA_LOOKUP_CODE.
Validation: ORG_FREIGHT.FREIGHT_CODE where
ORGANIZATION_ID = (SELECT
INVENTORY_ORGANIZATION_ID FROM
FINANCIALS_SYSTEM_PARAMS_ALL WHERE ORG_ID
= &DEFAULT_ORGID)
Destination: PO_VENDORS.SHIP_VIA_LOOKUP_CODE
FREIGHT_TERMS_LOOKUP_CODE
This is the default freight terms that have been negotiated with the supplier. This value
defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.FREIGHT_TERMS_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'FREIGHT
TERMS'
Destination: PO_VENDORS.FREIGHT_TERMS_LOOKUP_CODE
FOB_LOOKUP_CODE
This is the Free on Board (FOB) code for the supplier. This value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.FOB_LOOKUP_CODE.

Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'FOB'
Destination: PO_VENDORS.FOB_LOOKUP_CODE
TERMS_ID
This is the unique identifier for the terms on invoices from the supplier. This
corresponds to TERMS_NAME. A value can be provided for either or both columns. If
both are provided, the system will check to ensure that the values match a valid
ID-NAME combination. This value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.TERMS_ID.
Validation: AP_TERMS_TL.TERMS.ID
Destination: PO_VENDORS.TERMS_ID
TERMS_NAME
This is the name for the default terms used on invoices from the supplier. This
corresponds to TERMS_ID. A value can be provided for either or both columns. If both
are provided, the system will check to ensure that the values match a valid ID-NAME
combination.
Validation: AP_TERMS_TL_TERMS_NAME
Destination: None. The value of PO_VENDORS.TERMS_ID may be

derived from this column.
SET_OF_BOOKS_ID
This value defaults from the set of books associated with the user submitting the
concurrent request. This is derived from the System Profile Options: GL Set of Books ID.
Validation: GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID
Destination: PO_VENDORS.SET_OF_BOOKS_ID
ALWAYS_TAKE_DISC_FLAG
Enable this option if all payments for the supplier will be paid less the discount. This
values defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.ALWAYS_TAKE_DISC_FLAG
Destination: PO_VENDORS.ALWAYS_TAKE_DISC_FLAG

PAY_DATE_BASIS_LOOKUP_CODE
The Pay Date Basis determines the pay date for the supplier's invoice: Discount or Due.
This value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.PAY_DATE_BASIS_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAY DATE
BASIS'. Valid values are: 'DISCOUNT' or 'DUE'
Destination: PO_VENDORS.PAY_DATE_BASIS_LOOKUP_CODE
This is the Pay Group for the supplier. This can be used in payment batch processing for
grouping categories of suppliers. This value is defaulted from
AP_SYSTEM_PARAMETERS_ALL.PAY_GROUP_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAY GROUP'
Destination: PO_VENDORS.PAY_GROUP_LOOKUP_CODE
PAYMENT_PRIORITY
A number between 1 and 99 which represents the payment priority for the supplier.
This value defaults to 99.
Validation: Must be a number from 1 to 99.
Destination: PO_VENDORS.PAYMENT_PRIORITY
This is the default currency for Purchasing documents and Payables transactions from
the supplier. This value is defaulted from
AP_SYSTEM_PARAMETERS_ALL.INVOICE_CURRENCY_CODE.
Validation: FND.CURRENCIES.CURRENCY_CODE. This value must
match
AP_SUPPLIERS_INT.PAYMENT_CURRENCY_CODE
unless currency is EMU derived.
Destination: PO_VENDORS.INVOICE_CURRENCY_CODE
This is the default currency for Payments to this supplier. This value is derived from
AP_SYSTEM_PARAMETERS_ALL.INVOICE_CURRENCY_CODE.

match
AP_SUPPLIERS_INT.INVOICE_CURRENCY_CODE
Destination: PO_VENDORS.PAYMENT_CURRENCY_CODE
INVOICE_AMOUNT_LIMIT
Validation: Must be a number.
Destination: PO_VENDORS.INVOICE_AMOUNT_LIMIT
HOLD_ALL_PAYMENTS_FLAG
Enable if payments for the supplier are to be held. This value defaults to 'N'.
Destination: PO_VENDORS.HOLD_ALL_PAYMENTS_FLAG
HOLD_FUTURE_PAYMENTS_FLAG
Enable if unvalidated invoices for the supplier should be held. This value defaults to
'N'.
Destination: PO_VENDORS.HOLD_FUTURE_PAYMENTS_FLAG
HOLD_REASON
The reason invoices from the supplier are being held.
Validation: None
Destination: PO_VENDORS.HOLD_REASON
DISTRIBUTION_SET_ID
This column is valid at the supplier level only in a Non Multi-Org environment. This
column is the unique identifier for the distribution set that will be applied to invoices
from the supplier. This corresponds to DISTRIBUTION_SET_NAME. A value can be
ensure that the values represent a valid ID-NAME combination.
Validation: AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET_ID

Destination: PO_VENDORS.DISTRIBUTION_SET_ID
This column is valid at the supplier level only in a Non Multi-Org environment. This is
the name for the distribution set that will be applied to invoices from this supplier. A
value can be provided for either or both columns. If both are provided, the system will
check to ensure that the values represent a valid ID-NAME combination.
Validation: AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET_NA
ME
Destination: None. The value for

PO_VENDORS.DISTRIBUTION_SET_ID may be derived
from this column.
will be the default liability account for supplier sites from the supplier. If a value for this
column is entered into the interface table in a multi-org environment, that value will be
ignored and not brought into the PO_VENDORS table.
Validation: GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
where ACCOUNT_TYPE = 'L' and
CHART_OF_ACCOUNTS_ID = (SELECT
CHART_OF_ACCOUNTS_ID FROM
GL_SETS_OF_BOOKS where SET_OF_BOOKS_ID =
&DEFAULT_SET_OF_BOOKS_ID)
Destination: PO_VENDORS.ACCTS_PAY_CODE_COMBINATION_ID
PREPAY_CODE_COMBINATION_ID
This column is valid at the supplier level only in a Non Multi-Org environment. This is
the account that will be used for Prepayment Item distributions entered on invoices for
the supplier. If a value for this column is entered into the interface table in a mulit-org
environment, that value will be ignored and not brought into the PO_VENDORS table.
where CHART_OF_ACCOUNTS_ID = (SELECT
Destination: PO_VENDORS.PREPAY_CODE_COMBINATION_ID

NUM_1099
Supplier Tax Identification Number (TIN).
Validation: None
Destination: PO_VENDORS.NUM_1099
TYPE_1099
This is the income tax type for a United States 1099 reportable supplier.
Validation: AP_INCOME_TAX_TYPES.INCOME_TAX_TYPE. Value
in this field is only valid if
AP_SUPPLIERS_INT.FEDERAL_REPORTABLE_FLAG =
'Y'.
Destination: PO_VENDORS.TYPE_1099
ORGANIZATION_TYPE_LOOKUP_GUIDE
This is the type of enterprise for the supplier.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE =
'ORGANIZATION TYPE'. Valid values are:
'CORPORATION', 'FOREIGN CORPORATION',
'FOREIGN GOVERNMENT AGENCY', 'FOREIGN
INDIVIDUAL', 'FOREIGN PARTNERSHIP',
'GOVERNMENT AGENCY', 'INDIVIDUAL',
'PARTNERSHIP'
Destination: PO_VENDORS.ORGANIZATION_TYPE_LOOKUP_CODE
VAT_CODE
will be the default tax code for invoices entered for the supplier. In Non Multi-Org
enviroments, this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.VAT_CODE.
Validation: AP_TAX_CODES_ALL.NAME and
AP_TAX_CODES_ALL.TAX_TYPE cannot be 'OFFSET'.
Destination: PO_VENDORS.VAT_CODE
START_DATE_ACTIVE
This is the date on which the supplier will appear on supplier lists of values.

Validation: Must be in valid format.
Destination: PO_VENDORS.START_DATE_ACTIVE
END_DATE_ACTIVE
This is the date on which the supplier will no longer appear on any supplier list of
values.
Validation: Must be in valid format.
Destination: PO_VENDORS.END_DATE_ACTIVE
MINORITY_GROUP_LOOKUP_CODE
If the supplier is a minority-owned business, enter the minority group in this column.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'MINORITY
GROUP'
Destination: PO_VENDORS.MINORITY_GROUP_LOOKUP_CODE
This is the default payment method for the supplier.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAYMENT
METHOD'. Payment methods are user defined in Oracle
Payments
WOMEN_OWNED_FLAG
Indicates if the supplier is a woman-owned business. This value defaults to 'N'.
Destination: PO_VENDORS.WOMEN_OWNED_FLAG
SMALL_BUSINESS_FLAG
Indicates if the supplier is a small business. This value defaults to 'N'.
Destination: PO_VENDORS.SMALL_BUSINESS_FLAG
STANDARD_INDUSTRY_CLASS
Standard Industry Code (SIC).

Validation: None
Destination: PO_VENDORS.STANDARD_INDUSTRY_CLAS
HOLD_FLAG
Indicates whether the supplier is on purchasing hold. Purchase orders can be entered
for the supplier but not approved. This value defaults to 'N'.
Destination: PO_VENDORS.HOLD_FLAG
PURCHASING_HOLD_REASON
The reason purchase orders for this supplier cannot be approved.
Validation: None
Destination: PO_VENDORS.PURCHASING_HOLD_REASONS_FLAG
HOLD_BY
This is the unique identifier of the employee who placed the supplier on purchasing
hold.
Validation: PER_ALL_PEOPLE_F.PERSON_ID
Destination: PO_VENDORS.HOLD_BY
HOLD_DATE
The date the supplier was placed on purchasing hold.
Destination: PO_VENDORS.HOLD_DATE
TERMS_DATE_BASIS
The date from which Payables calculates a scheduled payment. This value defaults to
AP_SYSTEM_PARAMETERS_ALL.TERMS.DATE_BASIS.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'TERMS
DATE BASIS'. Valid values are: 'CURRENT', 'GOODS
RECEIVED', 'INVOICE', 'INVOICE RECEIVED'.
Destination: PO_VENDORS.TERMS.DATE_BASIS

INSPECTION_REQUIRED_FLAG/ RECEIPT_REQUIRED_FLAG
These columns, taken together, determine the level of match level approval that is
required for invoices matched to purchase orders: 4-way, 3-way, or 2-way. These values
default from PO_SYSTEM_PARAMETERS_ALL.INSPECTION_REQUIRED_FLAG and
PO_SYSTEM_PARAMETERS_ALL.RECEIVING FLAG.
Validation: These columns are evaluated together. Valid combinations
of values are: INSPECTION_REQUIRED_FLAG = 'Y,
RECEIPT_REQUIRED_FLAG = 'Y';
INSPECTION_REQUIRED_FLAG = 'N',
RECEIPT_REQUIRED_FLAG = 'Y'; and
INSPECTION_REQUIRED_FLAG = 'N',
RECEIPT_REQUIRED_FLAG = 'N'
Destination: PO_VENDORS.INSPECTION_REQUIRED_FLAG,
PO_VENDORS.RECEIPT_REQUIRED_FLAG
QTY_RCV_TOLERANCE
Oracle Purchasing uses this column during the receiving process. It identifies the
maximum acceptable quantity received in excess of the quantity ordered on a purchase
order for the supplier. This value defaults from
RCV_PARAMETERS.QTY_RCV_TOLERANCE.
Destination: PO_VENDORS.QTY_RCV_TOLERANCE
QTY_RCV_EXCEPTION_CODE
Oracle Purchasing uses this column to determine the action to be taken when the
quantity-received tolerance is violated during the receiving process. This value defaults
from RCV_PARAMETERS.QTY_RCV_EXCEPTION_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'RCV
OPTION'. Valid values are: 'NONE', 'REJECT', or
'WARNING'.
Destination: PO_VENDORS.QTY_RCV_EXCEPTION_CODE
ENFORCE_SHIP_TO_LOCATION_CODE
Oracle Purchasing uses this column to determine the action to be taken when receiving
location varies from the ship-to location. This value defaults from
RCV_PARAMETERS.ENFORCE_SHIP_TO_LOCATION.

OPTION'. Valid values are 'NONE', 'REJECT', or
'WARNING'.
Destination: PO_VENDORS.ENFORCE_SHIP_TO_LOCATION_CODE
DAYS_EARLY_RECEIPT_ALLOWED
Oracle Purchasing uses this column to determine the maximum number of days items
can be received early. This defaults from
RCV_PARAMETERS.DAYs_EARLY_RECEIPT_ALLOWED.
Destination: PO_VENDORS.DAYS_EARLY_RECEIPT_ALLOWED
DAYS_LATE_RECEIPT_ALLOWED
Oracle Purchasing uses this column to determine the maximum number of days items
can be received late. RCV_PARAMETERS.DAYS_LATE_RECEIPT_ALLOWED.
Destination: PO_VENDORS.DAYS_LATE_RECEIPT_ALLOWED
RECEIPT_DAYS_EXCEPTION_CODE
Oracle Purchasing uses this column to determine the action to be taken when items are
received earlier or later than the allowed number of days specified. This value defaults
from RCV_PARAMETERS.RECEIPT_DAYS_EXCEPTION_CODE.
OPTION'. Valid values are: 'NONE', 'REJECT', or
'WARNING'.
Destination: PO_VENDORS.RECEIPT_DAYS_EXCEPTION_CODE
RECEIVING_ROUTING_ID
This is the receipt routing unique identifier used by Oracle Purchasing.
RCV_PARAMETERS.RECEIVING_ROUTING_ID.
Validation: RCV_ROUTING_HEADERS.ROUTING_HEADER_ID
Destination: PO_VENDORS.RECEIVING_ROUTING_ID
ALLOW_SUBSTITUTE_RECEIPTS_FLAG
Oracle Purchasing uses this column to determine if substitute items can be received in

place of the ordered items. This value defaults from
RCV_PARAMETERS.ALLOW_SUBSTITUTE_RECEIPTS_FLAG.
Destination: PO_VENDORS.ALLOW_SUBSTITUTE_RECEIPTS_FLAG
ALLOW_UNORDERED_RECEIPTS_FLAG
Oracle Purchasing uses this column to determine if unordered receipts are allowed.
This value defaults from
RCV_PARAMETERS.ALLOW_UNORDERED_RECEIPTS_FLAG.
Destination: PO_VENDORS.ALLOW_UNORDERED_RECEIPTS_FLAG
HOLD_UNMATCHED_INVOICES_FLAG
This column indicates if unmatched invoices should be put on hold. If
AP_SUPPLIERS_INT.VENDOR_TYPE_LOOKUP_CODE = 'EMPLOYEE', then this
value defaults from
AP_SYSTEM_PARAMETERS_ALL.HOLD_UNMATCHED_INVOICES_FLAG. If not,
then this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.HOLD_UNMATCHED_INVOICES_FLAG.
Destination: PO_VENDORS.HOLD_UNMATCHED_INVOICES_FLAG
This column indicates whether or not separate payments should be created for each
invoice for the supplier. This value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.EXCLUSIVE_PAYMENT_FLAG.
Destination: PO_VENDORS.EXCLUSIVE_PAYMENT_FLAG
AP_TAX_ROUNDING_RULE
This column determines the rounding rule for tax values. This value defaults from
FINANCIALS_SYSTEM_PARAMETERS_ALL.TAX_ROUNDING_RULE.
'AP_TAX_ROUNDING_RULE'. Valid values are: 'D', 'N',
'U'.

Destination: PO_VENDORS.AP_TAX_ROUNDING_RULE
AUTO_TAX_CALC_FLAG
This column indicates the level for automatic tax calculation for supplier. This value
defaults from AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_FLAG and
cannot be changed in a Multi-Org environment.
Validation: If
AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_O
VERRIDE = 'N', this value must match the value of
AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_FL
AG. Valid values, which are found in
FND_LOOKUP_VALUES.LOOKUP_TYPE =
'AP_TAX_CALCULATION_METHOD', are: 'L', 'N', 'T', 'Y'.
Destination: PO_VENDORS.AUTO_TAX_CALC_FLAG
AUTO_TAX_CALC_OVERRIDE
This indicates if override of tax calculation is allowed at supplier site level. This value
defaults from AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_OVERRIDE and
cannot be changed in a Multi-Org environment.
Validation: If
VERRIDE = 'N', this value must also be 'N'.
Destination: PO_VENDORS.AUTO_TAX_CALC_OVERRIDE
AMOUNT_INCLUDES_TAX_FLAG
This column indicates if amounts on invoices from the supplier include tax. This value
defaults from AP_SYSTEM_PARAMETERS_ALL.AMOUNT_INCLUDES_TAX_FLAG
and cannot be changed in a Multi-Org environment.
Destination: PO_VENDORS.AMOUNT_INCLUDES_TAX_FLAG
TAX_VERIFICATION_DATE
The date tax verification for 1099 reporting purposes was received from the supplier.
Validation: Must be in the valid date format.
Destination: PO_VENDORS.TAX_VERIFICATION_DATE

NAME_CONTROL
This column is the first four characters of the last name of a 1099 reportable supplier.
Validation: Must be upper case letter, number between 0-9, and/or '&'.
Destination: PO_VENDORS.NAME_CONTROL
STATE_REPORTABLE_FLAG
This column indicates participation in the United States Internal Revenue Service
Combined Filing Program and that the supplier is reportable to a state taxing authority.
This value defaults to 'N'.
Destination: PO_VENDORS.STATE_REPORTABLE_FLAG
FEDERAL_REPORTABLE_FLAG
This column indicates that the supplier is reportable to the United States Internal
Revenue Service for 1099 purposes. This value defaults to 'N'.
Destination: PO_VENDORS.FEDERAL_REPORTABLE_FLAG
ATTRIBUTE_CATEGORY
This is the descriptive flexfield category for the descriptive flexfield information for the
supplier.
Validation: None
Destination: PO_VENDORS.ATTRIBUTE_CATEGORY
ATTRIBUTES (1-15)
This is the descriptive flexfield information for the supplier. The import process will not
validate the information entered in these columns. However, the structure of the
information entered (data types, value sets) must match the structure of the descriptive
flexfield segments defined for suppliers or users will experience validation problems
when trying to access the information through the application.
Validation: None
Destination: PO_VENDORS.ATTRIBUTE [1-15]

VAT_REGISTRATION_NUM
Tax registration number.
Validation: None
Destination: PO_VENDORS.VAT_REGISTRATION_NUM
AUTO_CALCULATE_INTEREST_FLAG
This column indicates if interest is to be automatically calculated on past due invoices
for the supplier. This value defaults to 'N'.
Destination: PO_VENDORS.AUTO_CALCULATE_INTEREST_FLAG
EXCLUDE_FREIGHT_FROM_DISCOUNT
This column indicates if the freight amount is to be excluded from the discount on
invoices from the supplier. This value defaults to 'N'.
Destination: PO_VENDORS.EXCLUDE_FREIGHT_FROM_DISCOUNT
TAX_REPORTING_NAME
This is the tax-reporting name for a supplier subject to United States Internal Revenue
Service income tax reporting. This is only necessary if the supplier name is different
from the tax-reporting name.
Validation: None
Destination: PO_VENDORS.TAX_REPORTING_NAME
ALLOW_AWT_FLAG
This column indicates whether or not automatic withholding is allowed for the
supplier. This value defaults to 'N'.
Validation: If
AP_SYSTEM_PARAMETERS_ALL.ALLOW_AWT_FLAG
= 'N', then this option is not available for suppliers.
Destination: PO_VENDORS.ALLOW_AWT_FLAG

AWT_GROUP_ID
The 'ID' is the unique identifier for the Withholding Tax Group that will default to the
supplier sites. This corresponds to AWT_GROUP_NAME. A value can be provided for
either or both columns. If both are provided, the system will check to ensure that the
values match a valide 'ID-NAME' combination.
Validation: AP_AWT_GROUPS.GROUP_ID. Values are only valid if
ALLOW_AWT_FLAG = 'Y'
Destination: PO_VENDORS.AWT_GROUP_ID
AWT_GROUP_NAME
This is the Withholding Tax Group that will default to the supplier sites. This
corresponds to AWT_GROUP_ID. A value can be provided for either or both columns.
If both are provided, the system will check to ensure that the values match a valid
'ID-NAME' combination.
Validation: AP_AWT_GROUP.NAME. Values are only valid if
ALLOW_AWT_FLAG = 'Y'.
Destination: None. Value for PO_VENDORS.AWT_GROUP_ID may be

GLOBAL_ATTRIBUTES (1-20)
This is global descriptive flexfield information for the supplier. The structure of the
information entered in these columns (data types, value sets) must match the structure
of the descriptive flexfield segments defined for suppliers or users will experience
validation problems when trying to access the information through the application.
Validation: None
Destination: PO_VENDORS.GLOBAL_ATTRIBUTES [1-20]
This is the descriptive flexfield category for the descriptive flexfield infomation for
import.
Validation: None
Destination: PO_VENDORS.GLOBAL_ATTRIBUTE_CATEGORY
EDI_TRANSACTION_HANDLING
This is the standard EDI transaction code designating action to be taken by all parties.

Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'EDI
TRANSACTION HANDLING'
Destination: PO_VENDORS.EDI_TRANSACTION_HANDLING
EDI_PAYMENT_METHOD
This indicates how EDI payments will be made.
PAYMENT METHOD'
Destination: PO_VENDORS.EDI_PAYMENT_METHOD
EDI_PAYMENT_FORMAT
This column indicates the type of information being transmitted when EDI Payment
Method is 'ACH'.
Validation: Valid only if EDI_PAYMENT_METHOD = 'ACH'.
Validated against
FND_LOOKUP_VALUES.LOOKUP_TYPE = 'EDI
PAYMENT FORMAT'.
Destination: PO_VENDORS.EDI_PAYMENT_FORMAT
EDI_REMITTANCE_METHOD
This column indicates the party responsible for sending remittance advice to the payee.
REMITTANCE METHOD'
Destination: PO_VENDORS.EDI_REMITTANCE_METHOD
EDI_REMITTANCE_INSTRUCTION
This is the text of electronic payment instructions for a financial institution.
Validation: None
Destination: PO_VENDORS.EDI_REMITTANCE_INSTRUCTION
BANK_CHARGE_BEARER
This column indicates who will pay bank charges assessed on payments to this
supplier. If AP_SYSTEM_PARAMETERS_ALL.USE_BANK_CHARGE_FLAG = 'Y', then
this field defaults from AP_SYSTEM_PARAMETERS_ALL.BANK_CHARGE_BEARER.

Validation: If
AP_SYSTEM_PARAMETERS_ALL.USE_BANK_CHARGE
_FLAG = 'N', then this option is not available for suppliers,
if
S_FLAG = 'Y', validated against FND_LOOKUP_VALUES
where LOOKUP_TYPE = 'BANK CHARGE BEARER'. Valid
values are: 'I', 'N', 'S'.
Destination: PO_VENDORS.BANK_CHARGE_BEARER
MATCH_OPTION
This column indicates whether invoices are matched to a purchase order to a receipt.
This value defaults from FINANCIALS_SYSTEM_PARAMS_ALL.MATCH_OPTION.
Validation: Valid values are: 'P' (meaning: Purchase Order) and 'R'
(meaning: Receipt).
Destination: PO_VENDORS.MATCH_OPTION
FUTURE_DATED_PAYMENT_CCID
Default future dated payments account for sites for this supplier. This column is only
valid at the supplier level in Non Multi-Org environments. If a value for this column is
entered into the interface table in a multi-org environment, that value will be ignored
and not brought into the PO_VENDORS table. If Non Multi-Org, this value defaults
from FINANCIALS_SYSTEM_PARAMS_ALL.FUTURE_DATED_PAYMENT_CCID. If
Multi-Org, the default is NULL.
Destination: PO_VENDORS.FUTURE_DATED_PAYMENT_CCID
CREATE_DEBIT_MEMO_FLAG
This column indicates if a debit memo should be automatically created when goods are
returned to the supplier.
Destination: PO_VENDORS.CREATE_DEBIT_MEMO_FLAG

OFFSET_TAX_FLAG
This column indicates whether or not the supplier uses offset taxes. This is only valid at
the supplier level in Non Multi-Org environments. This value defaults to 'N'.
Validation: Non Multi-Org only:
FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'.
Also, if
AP_SUPPLIER_INT.VENDOR_TYPE_LOOKUP_CODE =
'EMPLOYEE', value cannot be 'Y'.
Destination: PO_VENDORS.OFFSET_TAX_FLAG
STATUS
This column indicates the status of the record in the interface table. The user should
enter 'NEW' as the initial value for this column. After the Suppliers Open Interface
Import Program is run, successfully imported records will be marked as 'PROCESSED'
and records that are not imported will be marked 'REJECTED'.
REJECT_CODE
This column indicates the reason the record has been rejected by the Supplier Open
Interface Import Program. This column is populated by the Supplier Open Interface
Import Program and should not be entered by the user.
Validation: N/A
Destination: None
ECE_TP_LOCATION_CODE
Trading partner location code for e-Commerce Gateway.
Validation: None
Destination: PO_VENDORS_SITES_ALL.ECE_TP_LOCATION_CODE
IBY_BANK_CHARGE_BEARER
This column indicates who will pay bank charges assessed on payments to the supplier.
This value defaults from PO_VENDORS.BANK_CHARGE_BEARER.
Validation: If
_FLAG = 'N', then this option is not available for supplier
sites. If

S_FLAG= 'Y', validated against FND_LOOKUP_VALUES
Destination: PO_VENDOR_SITES_ALL.BANK_CHARGE_BEARER
BANK_INSTRUCTION(1-2)_CODE
These columns indicate the code of first and second bank instructions.
Validation: N/A
Destination: None
BANK_INSTRUCTION_DETAILS
This column are the additional bank instruction details.
Validation: N/A
Destination: None
PAYMENT_REASON_CODE
This column indicates the payment reason code.
Validation: N/A
Destination: None
PAYMENT_REASON_COMMENTS
This column is a free text field available for entering a reason.
Validation: N/A
Destination: None
PAYMENT_TEXT_MESSAGE(1-3)
These columns indicate are text messages for use in payment processing.
Validation: N/A
Destination: None
DELIVERY CHANNEL_CODE
This column is the default delivery channel code.

Validation: N/A
Destination: None
PAYMENT_FORMAT_CODE
This column is the default payment format code.
Validation: N/A
Destination: None
SETTLEMENT_PRIORITY
This column is the priority for payments settlement.
Validation: N/A
Destination: None
PAYMENT_METHOD_CODE
This column is the payment method identifier.
Validation: N/A
Destination: None
AP_SUPPLIER_SITES_INT
VENDOR_INTERFA NUMBER(15) Required if value is

CE_ID not provided for
VENDOR_ID
VENDOR_ID NUMBER Required if value is

not provided for
VENDOR_INTERFA
CE_ID
VENDOR_SITE_COD VARCHAR2(15) Required

E
VENDOR_SITE_COD VARCHAR(320) N/A

E_ALT

PURCHASING_SITE VARCHAR2(1) N/A

_FLAG
RFQ_ONLY_SITE_FL VARCHAR2(1) N/A

AG
PAY_SITE_FLAG VARCHAR2(1) N/A
ATTENTION_AR_FL VARCHAR2(1) N/A

AG
ADDRESS_LINE1 VARCHAR2(240) N/A
ADDRESS_LINE_AL VARCHAR2(560) N/A

T
CITY VARCHAR2(25) N/A
STATE VARCHAR2(150) Conditionally

required
ZIP VARCHAR2(20) N/A
PROVINCE VARCHAR2(150) N/A
COUNTRY VARCHAR2(25) N/A
AREA_CODE VARCHAR2(10) N/A
PHONE VARCHAR(15) N/A
CUSTOMER_NUM VARCHAR(25) N/A
SHIP_TO_LOCATIO NUMBER N/A

N_ID


N_CODE
BILL_TO_LOCATIO NUMBER N/A

N_ID
BILL_TO_LOCATIO VARCHAR2(60) N/A

N_CODE
SHIP_VIA_LOOKUP VARCHAR2(25) N/A

_CODE
FREIGHT_TERMS_L VARCHAR2(25) N/A

OOKUP_CODE
FOB_LOOKUP_COD VARCHAR2(25) N/A

E
SHIPPING_CONTRO VARCHAR2(30) N/A

L
INACTIVE_DATE DATE N/A
FAX VARCHAR2(15) N/A
FAX_AREA_CODE VARCHAR2(10) N/A
TELEX VARCHAR2(15) N/A
PAYMENT_METHO VARCHAR2(25) Required but will

D_LOOKUP_CODE default
TERMS_DATE_BASI VARCHAR2(25) Required but will

S default
VAT_CODE VARCHAR2(20) N/A
DISTRIBUTION_SET NUMBER N/A

_ID

DISTRIBUTION_SET VARCHAR2(50) N/A

_NAME
ACCTS_PAY_CODE_ NUMBER N/A

COMBINATION_ID
PREPAY_CODE_CO NUMBER N/A

MBINATION_ID
PAY_GROUP_LOOK VARCHAR2(25) N/A

UP_CODE
PAYMENT_PRIORIT NUMBER Required but will

Y default
TERMS_ID NUMBER N/A
TERMS_NAME VARCHAR2(50) N/A
INVOICE_AMOUNT NUMBER N/A

_LIMIT
PAY_DATE_BASIS_L VARCHAR2(25) Required but will

OOKUP_CODE default
ALWAYS_TAKE_DIS VARCHAR2(1) N/A

C_FLAG
INVOICE_CURRENC VARCHAR2(15) N/A

Y_CODE

CY_CODE
HOLD_ALL_PAYME VARCHAR2(1) N/A

NTS_FLAG
HOLD_FUTURE_PA VARCHAR2(1) N/A

YMENTS_FLAG
HOLD_REASON VARCHAR2(240) N/A

HOLD_UNMATCHE VARCHAR2(1) N/A

D_INVOICES_FLAG
AP_TAX_ROUNDIN VARCHAR2(1) N/A

G_RULE

FLAG

OVERRIDE
AMOUNT_INCLUD VARCHAR2(1) N/A

ES_TAX_FLAG

NT_FLAG
TAX_REPORTING_SI VARCHAR2(1) Only one site

TE_FLAG required if Federal
Reportable = 'Y'
ATTRIBUTE_CATEG VARCHAR2(30) N/A

ORY
ATTRIBUTES(1-15) VARCHAR2(150) N/A
EXCLUDE_FREIGHT VARCHAR2(1) N/A

_FROM_DISCOUNT
VAT_REGISTRATIO VARCHAR2(20) N/A

N_NUM
ORG_ID NUMBER(15) Required if value is

not provided for
OPERATING_UNIT_
NAME
OPERATING_UNIT_ VARCHAR2(240) Required if value is

NAME not provided for
ORG_ID

COUNTY VARCHAR2(150) N/A
ADDRESS_STYLE VARCHAR2(30) N/A
LANGUAGE VARCHAR2(30) N/A
ALLOW_AWT_FLA VARCHAR2(1) N/A

G
AWT_GROUP_ID NUMBER(1) N/A
AWT_GROUP_NAM VARCHAR2(25) N/A

E

ES(1-20)

E_CATEGORY
EDI_TRANSACTION VARCHAR2(25) N/A

_HANDLING
EDI_ID_NUMBER VARCHAR2(30) N/A
EDI_PAYMENT_ME VARCHAR2(30) N/A

THOD
EDI_PAYMENT_FOR VARCHAR2(25) N/A

MAT
EDI_REMITTANCE_ VARCHAR2(25) N/A

METHOD
BANK_CHARGE_BE VARCHAR2(1) N/A

ARER
EDI_REMITTANCE_I VARCHAR2(256) N/A

NSTRUCTION

PAY_ON_CODE VARCHAR2(25) N/A
DEFAULT_PAY_SIT NUMBER(15) Conditionally

E_ID required
PAY_ON_RECEIPT_ VARCHAR2(25) N/A

SUMMARY_CODE
TP_HEADER_ID NUMBER N/A
ECE_TP_LOCATION VARCHAR2(60) N/A

_CODE
PCARD_SITE_FLAG VARCHAR2(1) N/A
MATCH_OPTION VARCHAR2(25) Required but will

default
COUNTRY_OF_ORI VARCHAR2(25) N/A

GIN_CODE
FUTURE_DATED_P NUMBER(15) N/A

AYMENT_CCID
CREATE_DEBIT_ME VARCHAR2(1) N/A

MO_FLAG
OFFSET_TAX_FLAG VARCHAR2(1) N/A
SUPPLIER_NOTIF_M VARCHAR2(25) N/A

ETHOD
EMAIL_ADDRESS VARCHAR2(2000) N/A
REMITTANCE_EMA VARCHAR2(2000) N/A

IL
PRIMARY_PAY_SITE VARCHAR2(1) N/A

_FLAG

SHIPPING_CONTRO VARCHAR2(30) Indicates the party

L responsible for
arranging
transportation:
Supplier or Buyer.
DUNS_NUMBER VARCHAR2(30) A unique 9-digit

identification number
assigned to all
business entities in
Dun & Bradstreet's
database. Used only
for Federal Financial
installations.
TOLERANCE_ID NUMBER (15) Tolerance Template

identifier
TOLERANCE_NAM VARCHAR2(255) Tolerance Template

E Name
IBY_BANK_CHARG VARCHAR2(30) Bearer of bank charge

E_BEARER cost.
BANK_INSTRUCTIO VARCHAR2(30) Code of first bank

N1_CODE instruction.
BANK_INSTRUCTIO VARCHAR2(30) Code of second bank

N2_CODE instruction.
BANK_INSTRUCTIO VARCHAR2(255) Additional bank

N_DETAILS instruction details.
PAYMENT_REASON VARCHAR2(30) Payment reason code

_CODE
PAYMENT_REASON VARCHAR(240) Free text field

_COMMENTS available for entering
a reason.

DELIVERY_CHANN VARCHAR2(30) Default delivery

EL_CODE channel code.
PAYMENT_FORMA VARCHAR2(150) Default payment

T_CODE format code.
SETTLEMENT_PRIO VARCHAR2(30) Priority for payments

RITY settlement

ESSAGE1 in payment
processing

ESSAGE2 in payment
processing

ESSAGE3 in payment
processing
VENDOR_SITE_INT NUMBER(15) Vendor site interface

ERFACE_ID identifier.
PAYMENT_METHO VARCHAR2(30) Payment method

D_CODE identifier.
RETAINAGE_RATE Number Maximum

percentage that can
be withheld from an
invoice as Retainage.
GAPLESS_INV_NU VARCHAR2(1) Gapless Invoice

M_FLAG Numbering Flag
SELLING_COMPAN VARCHAR2(10) Unique selling

Y_IDENTIFIER company identifier
for supplier.
VENDOR_INTERFACE_ID
This is the unique identifier for AP_SUPPLIERS_INT that joins the supplier to the site in
the interface. The user can determine the value for this column from the

AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID that corresponds to the Supplier Site
record. A user-supplied value is required for either this column or
AP_SUPPLIER_SITES_INT.VENDOR_ID.
Validation: None
Destination: None
VENDOR_ID
This is the unique identifier for the supplier used to join the site to the corresponding
supplier. The VENDOR_ID is a mandatory value for both this field and the
AP_SUPPLIER_SITES_INT.VENDOR_INTERFACE_ID. If the
VENDOR_INTERFACE_ID is provided and the VENDOR_ID is not specified, then the
Supplier Open Interface Import program displays an error.
The Supplier Sites Open Interface Import program displays an exception in the output
report when the VENDOR_ID is missing.
Validation: PO_VENDORS.VENDOR_ID
Destination: PO_VENDOR_SITES_ALL.VENDOR_ID
VENDOR_SITE_CODE
This is the unique name assigned by the user to the supplier site. The user must supply
this value.
Validation: Checks for duplicates against:
PO_VENDOR_SITES_ALL.VENDOR_SITE_CODE and
ORG_ID.
Destination: PO_VENDOR_SITES_ALL.VENDOR_SITE_CODE
VENDOR_SITE_CODE_ALT
This column is the alternate supplier site code used primarily for Kana values.
Validation: None
Destination: PO_VENDOR_SITES_ALL.VENDOR_SITE_CODE_ALT
PURCHASING_SITE_FLAG
This column indicates whether or not purchasing is allowed from the site. This value
defaults to 'Y'.

Destination: PO_VENDOR_SITES_ALL.PURCHASING_SITE_FLAG
RFQ_ONLY_SITE_FLAG
This column indicates whether or not the site only accepts RFQs. This value defaults
from FINANCIALS_SYSTEM_PARAMS_ALL.RFQ_ONLY_SITE_FLAG.
Destination: PO_VENDORS_SITES_ALL.RFQ_ONLY_SITE_FLAG
PAY_SITE_FLAG
This column indicates whether or not payments are allowed to the site. This value
defaults to 'Y'.
Destination: PO_VENDORS_SITES_ALL.PAY_SITE_FLAG
ATTENTION_AR_FLAG
This column indicates if payments are to be sent to the Accounts Receivable department
of the supplier site. This value defaults to 'N'.
Destination: PO_VENDOR_SITES_ALL.ATTENTION_AR_FLAG
ADDRESS_LINE(1 - 3)
This is the first line of supplier site address.
Validation: None
Destination: PO_VENDOR_SITES_ALL.ADDRESS_LINE1
ADDRESS_LINES_ALT
This is the alternate address line for Kana Value of the supplier site address.
Validation: None
Destination: PO_VENDOR_SITES_ALL.ADDRESS_LINES_ALT
CITY
City name.

Validation: None
Destination: PO_VENDOR_SITES_ALL.CITY
STATE
State name or abbreviation.
Validation: If PO.VENDORS.FEDERAL_REPORTABLE_FLAG = 'Y',
and
PO_VENDORS.ORGANIZATION_TYPE_LOOKUP_CODE
not like 'FOREIGN%', then validated against
FND_LOOKUP_VALUES.LOOKUP_TYPE = 'STATE', else
no validation.
Destination: PO_VENDOR_SITES_ALL.STATE
ZIP
Postal code.
Validation: None
Destination: PO_VENDOR_SITES_ALL.ZIP
PROVINCE
Province.
Validation: None
Destination: PO_VENDORS_SITES_ALL.PROVINCE
COUNTRY
Country name. This value defaults from the System Profile Option: Default Country.
Validation: FND_TERRITORIES.TERRITORY_CODE
Destination: PO_VENDORS_SITES_ALL.COUNTRY
AREA_CODE
Telephone area code.
Validation: None
Destination: PO_VENDOR_SITES_ALL.AREA_CODE

PHONE
Telephone number.
Validation: None
Destination: PO_VENDOR_SITES_ALL.PHONE
CUSTOMER_NUM
Customer number with the supplier site. This value defaults from
PO_VENDORS.CUSTOMER_NUM.
Validation: None
Destination: PO_VENDOR_SITES_ALL.CUSTOMER_NUM
SHIP_TO_LOCATION_ID
The 'ID' is the unique identifier for the location where the supplier site sends shipments
for goods/services. This corresponds to SHIP_TO_LOCATION_CODE. A value can be
ensure that the values match a valid 'ID-CODE' combination. This value defaults from
PO_VENDORS.SHIP_TO_LOCATION_ID.
HR_LOCATIONS_ALL.SHIP_TO_SITE_FLAG must be 'Y'.
Destination: PO_VENDOR_SITES_ALL.SHIP_TO_LOCATION_ID
This is the location where the supplier site sends shipments for goods/services. This
corresponds to SHIP_TO_LOCATION_ID. A value can be provided for either or both
HR_LOCATIONS_ALL.SHIP_TO_SITE_FLAG must be 'Y'.

PO_VENDOR_SITES_ALL.SHIP_TO_LOCATION_ID may
be derived from this column.
BILL_TO_LOCATION_ID
The 'ID' is the unique identifier for the location where the supplier site sends invoices
for goods/services. This corresponds to BILL_TO_LOCATION_CODE. A value can be

ensure that the values match a valid 'ID-CODE' combination. This value defaults from
PO_VENDORS.BILL_TO_LOCATION_ID.
Destination: PO_VENDOR_SITES_ALL.BILL_TO_LOCATION_ID
BILL_TO_LOCATION_CODE
This is the location where the supplier sends invoices from goods/services. This
corresponds to BILL_TO_LOCATION_ID. A value can be provided for either or both
Validation: HR_LOCATIONS_ALL.LOCATION_CODE. The
Destination: None The value of

PO_VENDOR_SITES_ALL.BILL_TO_LOCATION_ID may
SHIP_VIA_LOOKUP_CODE
This is the freight carrier that is used with the supplier site. This value defaults from
PO_VENDORS.SHIP_VIA_LOOKUP_CODE if value is in
ORG_FREIGHT.FREIGHT_CODE where ORGANIZATION_ID = (SELECT
INVENTORY_ORGANIZATION_ID FROM FINANCIALS_SYSTEM_PARAMS_ALL
WHERE ORG_ID = &SITE_ORG_ID), else NULL.
Validation: ORG_FREIGHT.FREIGHT_CODE where
ORGANIZATION_ID = (SELECT
INVENTORY_ORGANIZATION_ID FROM
FINANCIALS_SYSTEM_PARAM_ALL WHERE ORG_ID =
&SITE_ORG_ID).
Destination: PO_VENDOR_SITES_ALL.SHIP_VIA_CODE
This column indicates the freight terms that have been negotiated with the supplier site.
This value defaults from PO_VENDORS.FREIGHT_TERMS_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'FREIGHT
TERMS'
Destination: PO_VENDORS_SITES_ALL.FREIGHT_TERMS_LOOKUP_

CODE
FOB_LOOKUP_CODE
This is the Free on Board (FOB) code for the supplier site. This value defaults from
PO_VENDORS.FOB_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'FOB'
Destination: PO_VENDOR_SITES_ALL.FOB_LOOKUP_CODE
SHIPPING_CONTROL
Indicates the party responsible for arranging transportation: supplier or buyer.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'SHIPPING
CONTROL'. Valid values are 'SUPPLIER' or 'BUYER'.
Destination: PO_VENDOR_SITES_ALL.SHIPPING_CONTROL
INACTIVE_DATE
This is the date on which the supplier site will no longer appear on any supplier site list
of values.
Destination: PO_VENDOR_SITES_ALL.INACTIVE_DATE
FAX
Supplier site facsimile number.
Validation: None
Destination: PO_VENDOR_SITES_ALL.FAX
FAX_AREA_CODE
Supplier site area code for facsimile number.
Validation: None
Destination: PO_VENDORS_SITES_ALL.FAX_AREA_CODE
TELEX
Supplier site telex number.

Validation: None
Destination: PO_VENDORS_SITES_ALL.TELEX
This column indicates the default method of payment for the supplier site.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAYMENT
METHOD'. Payment methods are user defined in Oracle
Payments
TERMS_DATE_BASIS
This is the date from which Payables calculates a scheduled payment for the supplier
site. This value defaults from PO_VENDORS.TERMS_DATE_BASIS.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'TERMS
DATE BASIS'. Valid values are: 'Current', 'Goods Received',
'Invoice', 'Invoice Received'.
Destination: PO_VENDOR_SITES_ALL.TERMS.DATE_BASIS
VAT_CODE
This will be the default tax code for invoices entered for the supplier site. If in a
Multi-Org environment, this value defaults from PO_VENDORS.VAT_CODE. If in a
Non Multi-Org environment, this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.VAT_CODE.
Validation: AP_TAX_CODES_ALL.NAME and
AP_TAX_CODES_ALL.TAX_TYPE cannot be 'OFFSET'.
Destination: PO_VENDOR_SITES_ALL.VAT_CODE
DISTRIBUTION_SET_ID
The 'ID' is the unique identifier for the distribution set that will be applied to invoices
from the supplier site. This corresponds to DISTRIBUTION_SET_NAME. A value can
be provided for either or both columns. If both are provided, the system will check to
ensure that the values represent a valid 'ID-NAME' combination. In a Non Multi-Org
environment, this value defaults from PO_VENDORS.DISTRIBUTION_SET_ID. In a
Multi-Org environment, there is no default.
Validation: AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET_ID
Destination: PO_VENDOR_SITES_ALL.DISTRIBUTION_SET_ID

This is the name for the distribution set that will be applied to invoices from the
supplier site. A value can be provided for either or both columns. If both are provided,
the system will check to ensure that the values represent a valid 'ID-NAME'
combination.
Validation: AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET_NA
ME

PO_VENDOR_SITES_ALL.DISTRIBUTION_SET_ID may
This will be the default liability account for invoices from the supplier site. In a Non
Multi-Org environment, this value defaults from
PO_VENDORS.ACCTS_PAY_CODE_COMBINATION_ID. In a Multi-Org
environment, this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.ACCTS_PAY_CODE_COMBINATION_ID.
where ACCOUNT_TYPE = 'L' and
CHART_OF_ACCOUNTS_ID = (SELECT
CHART_OF_ACCOUNTS_ID FROM GL_SETS_OF
BOOKS where SET_OF_BOOKS_ID =
&SITE_ORG_SET_OF_BOOKS_ID).
Destination: PO_VENDOR_SITES_ALL.ACCTS_PAY_CODE_COMBIN
ATION_ID
PREPAY_CODE_COMBINATION_ID
This is the account that will be used for Prepayment Item distributions entered on
invoices for the supplier site. In a Non Multi-Org environment, this value defaults from
PO_VENDORS.PREPAY_CODE_COMBINATION_ID. In a Multi-Org environment,
this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.PREPAY_CODE_COMBINATION_ID.
&SITE_ORG_SET_OF_BOOKS_ID).
Destination: PO_VENDOR_SITES_ALL.PREPAY_CODE_COMBINATI

ON_ID
This is the Pay Group for the supplier site. This can be used in payment batch
processing for grouping categories of suppliers. This value defaults from
PO_VENDORS.PAY_GROUP_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAY GROUP'
Destination: PO_VENDOR_SITES_ALL.PAY_GROUP_LOOKUP_COD
E
PAYMENT_PRIORITY
A number between 1 and 99 that represents the payment priority for the supplier site.
This value defaults from PO_VENDORS.PAYMENT_PRIORITY.
Validation: Must be a number from 1 to 99.
Destination: PO_VENDOR_SITES_ALL.PAYMENT_PRIORITY
TERMS_ID
The 'ID' is the unique identifier for the terms on invoices from the supplier site. This
corresponds to TERMS_NAME. A value can be provided for either or both columns. If
'ID-NAME' combination. This value defaults from PO_VENDORS.TERMS_ID.
Validation: AP_TERMS_TL.TERMS_ID
Destination: PO_VENDORS_SITES_ALL.TERMS_ID
TERMS_NAME
This column is the name of the terms that will default on invoices from the supplier site.
This corresponds to TERMS_ID. A value can be provided for either or both columns. If
'ID-NAME' combination.
Validation: AP_TERMS_TL.TERMS_NAME
Destination: None. The value of PO_VENDOR_SITES_ALL.TERMS_ID

may be derived from this column.
INVOICE_AMOUNT_LIMIT
This is the maximum amount allowed on invoices from the supplier site.

Destination: PO_VENDOR_SITES_ALL.INVOICE_AMOUNT_LIMIT
PAY_DATE_BASIS_LOOKUP_CODE
The Pay Date Basis determines the pay date for the supplier site invoices: Discount or
Due. This value defaults from PO_VENDORS.PAY_DATE_BASIS_LOOKUP_CODE.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'PAY DATE
BASIS'. Valid values are 'DISCOUNT' or 'DUE'.
Destination: PO_VENDOR_SITES_ALL.PAY_DATE_BASIS_LOOKUP_
CODE
ALWAYS_TAKE_DISC_FLAG
Enable this option if all payments for the supplier site will be paid less the discount.
This value defaults from PO_VENDORS.ALWAYS_TAKE_DISC_FLAG.
Destination: PO_VENDOR_SITES_ALL.ALWAYS_TAKE_DISC_FLAG
This is the default currency for Purchasing documents and Payables transactions from
the supplier site. This value defaults from
PO_VENDORS.INVOICE_CURRENCY_CODE.
match
AP_SUPPLIER_SITES_INT.PAYMENT_CURRENCY_COD
E unless currency is EMU derived.
Destination: PO_VENDORS_SITES_ALL.INVOICE_CURRENCY_COD
E
This is the default currency for Payments to the supplier site. This value defaults from
PO_VENDORS.PAYMENT_CURRENCY_CODE.
match
AP_SUPPLIER_SITES_INT.INVOICE_CURRENCY_CODE

Destination: PO_VENDORS_SITES_ALL.PAYMENT_CURRENCY_CO
DE
HOLD_ALL_PAYMENTS_FLAG
Enable if payments for the supplier site are to be held. This value defaults from
PO_VENDORS.HOLD_ALL_PAYMENTS_FLAG.
Destination: PO_VENDOR_SITES_ALL.HOLD_ALL_PAYMENTS_FLA
G
HOLD_FUTURE_PAYMENTS_FLAG
Enable if unvalidated invoices for the supplier site should be held. This value defaults
from PO_VENDORS.HOLD_FUTURE_PAYMENTS_FLAG.
Destination: PO_VENDOR_SITES_ALL.HOLD_FUTURE_PAYMENTS_
FLAG
HOLD_REASON
The reason invoices are being held for the supplier site. This value defaults from
PO_VENDORS.HOLD_REASON.
Validation: None
Destination: PO_VENDOR_SITES_ALL.HOLD_REASON
HOLD_UNMATCHED_INVOICES_FLAG
Indicates if unmatched invoices should be put on hold for the supplier site. This value
defaults from PO_VENDORS.HOLD_UNMATCHED_INVOICES_FLAG.
Destination: PO_VENDOR_SITES_ALL.HOLD_UNMATCHED_INVOI
CES_FLAG
AP_TAX_ROUNDING_RULE
This column determines the rounding rule for tax values on invoices from the supplier
site. If Non Multi-Org, this value defaults from
PO_VENDORS.TAX_ROUNDING_RULE. If Mulit-Org, then this value defaults from
FINANCIALS_SYSTEM_PARAMS_ALL.TAX_ROUNDING_RULE.

'AP_TAX_ROUNDING_RULE'. Valid values are: 'D', 'N',
'U'.
Destination: PO_VENDOR_SITES_ALL.AP_TAX_ROUNDING_RULE
AUTO_TAX_CALC_FLAG
This column indicates the level for automatic tax calculation for the supplier site. If Non
Multi-Org, this value defaults from PO_VENDORS.AUTO_TAX_CALC_FLAG. If
Multi-Org, this value defaults from
AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_FLAG.
Validation: Non Multi-Org environment: If
PO_VENDORS.AUTO_TAX_CALC_OVERRIDE = 'N', this
value must match the value of
PO_VENDORS.AUTO_TAX_CALC_FLAG. Multi-Org
enviroment: If
VERRIDE = 'N', this value must match the value of
AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_FL
AG. Valid values found in
FND_LOOKUP_VALUES.LOOKUP_TYPE =
'AP_TAX_CALCULATION_METHOD'
Destination: PO_VENDOR_SITES_ALL.AUTO_TAX_CALC_FLAG
AUTO_TAX_CALC_OVERRIDE
Allows override of tax calculation for invoice entered for the supplier site. If Non
Multi-Org, then this value defaults from
PO_VENDORS.AUTO_TAX_CALC_OVERRIDE. If Multi-Org, then this value defaults
from AP_SYSTEM_PARAMETERS_ALL.AUTO_TAX_CALC_OVERRIDE.
PO_VENDORS.AUTO_TAX_CALC_OVERRIDE = 'N', this
value must also be 'N'. Mult-Org environment: If
VERRIDE = 'N', this value must also be 'N'.
Destination: PO_VENDOR_SITES_ALL.AUTO_TAX_CALC_OVERRID
E
AMOUNT_INCLUDES_TAX_FLAG
This column indicates if amounts on invoices from the supplier include tax. If Non
Multi-Org, then this value defaults from

PO_VENDORS.AMOUNT_INCLUDES_TAX_FLAG. If Multi-Org, then this value
defaults from AP_SYSTEM_PARAMETERS_ALL.AMOUNT_INCLUDES_TAX_FLAG.
PO_VENDORS.AUTO_TAX_CALC_FLAG = 'Y', this value
cannot be 'Y'. Multi-Org environment: If
AP_SYSTEM_PARAMETERS_ALL
AUTO_TAX_CALC_FLAG = 'Y', this value cannot be 'Y'.
Also, if:
AP_SYSTEM_PARAMETERS_ALL.AMOUNT_INCLUDES
_TAX_OVERRIDE = 'N', this value must match
AP_SYSTEM_PARAMETERS_ALL.AMOUNT_INCLUDES
_TAX_FLAG FND_LOOKUP_VALUES.LOOKUP_TYPE =
'YES/NO'
Destination: PO_VENDORS_SITES_ALL.AMOUNT_INCLUDES_TAX_
FLAG
Indicates whether or not separate payments should be created for each invoice issued
by the supplier site. This value defaults from
PO_VENDORS.EXCLUSIVE_PAYMENT_FLAG.
Destination: PO_VENDORS_SITES_ALL.EXCLUSIVE_PAYMENT_FLA
G
TAX_REPORTING_SITE_FLAG
Indicates whether or not the site is the 1099-reporting site for the supplier. All 1099
reportable suppliers must have one and only one site designated as the tax-reporting
site. This value defaults to 'N'.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO' and
no other site for the supplier is designated as a tax
reporting site.
Destination: PO_VENDOR_SITES_ALL.TAX_REPORTING_SITE_FLAG
ATTRIBUTE_CATEGORY
This is the descriptive flexfield category for the descriptive flexfield information for the
supplier site.
Validation: None

Destination: PO_VENDOR_SITES_ALL.ATTRIBUTE_CATEGORY
ATTRIBUTES (1-15)
These columns are descriptive flexfield information for the supplier site. The import
process will not validate the information entered in these columns. However, the
structure of the information entered (data types, value sets) must match the structure of
the descriptive flexfield segments defined for supplier sites, or users will experience
Validation: None
Destination: PO_VENDOR_SITES_ALL.ATTRIBUTE[1-15]
Validation number.
EXCLUDE_FREIGHT_FROM_DISCOUNT
Indicates if the freight amount is to be excluded from the discount on invoices issued by
the supplier site. This value defaults from
PO_VENDORS.EXCLUDE_FREIGHT_FROM_DISCOUNT.
Destination: PO_VENDORS_SITES_ALL.EXCLUDE_FREIGHT_FROM_
DISCOUNT
VAT_REGISTRATION_NUM
This is the tax registration number for the supplier site. This value defaults from
PO_VENDORS.VAT_REGISTRATION_NUM.
Validation: None
Destination: PO_VENDOR_SITES_ALL.VAT_REGISTRATION_NUM
ORG_ID
This is the unique identifier for the operating unit. This corresponds to the
OPERATING_UNIT_NAME. A value must be provided for at least one of these
valid 'ID-NAME' combination.
Validation: HR_OPERATING_UNITS.ORGANIZATION_ID
Destination: PO_VENDOR_SITES_ALL.ORG_ID

OPERATING_UNIT_NAME
This is the name for the operating unit. This corresponds to the ORG_ID. A value must
be provided for at least one of these columns. If both are provided, the system will
check to ensure that the values match a valid 'ID-NAME' combination.
Validation: HR_OPERATING_UNITS.NAME
Destination: None. The value of PO_VENDOR_SITES_ALL.ORG_ID

may be derived from this column.
ADDRESS_LINE4
This is the fourth line of the supplier site address.
Validation: None
Destination: PO_VENDOR_SITES_ALL.ADDRESS_LINE4
COUNTY
Supplier site county.
Validation: None
Destination: PO_VENDOR_SITES_ALL.COUNTY
ADDRESS_STYLE
This is the address style for the supplier site.
'ADDRESS_STYLE'
Destination: PO_VENDORS_SITES_ALL.ADDRESS_STYLE
LANGUAGE
This is the language for the supplier site.
Validation: FND_LANGUAGE.NLS_LANGUAGE
Destination: PO_VENDORS_SITES_ALL.LANGUAGE
ALLOW_AWT_FLAG
This flag indicates whether automatic withholding is allowed for the supplier site. This
value defaults from PO_VENDORS.ALLOW_AWT_FLAG.

Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'. If
PO_VENDORS.ALLOW_AWT_FLAG is 'N', this option is
not available for Supplier Sites.
Destination: PO_VENDOR_SITES_ALL.ALLOW_AWT_FLAG
AWT_GROUP_ID
This is the unique identifier for the automatic withholding tax group that will default
for supplier site invoices. This corresponds to the AWT_GROUP_NAME. A value can
be provided for either or both columns. If both are provided, the system will check to
ensure that the values match a valid 'ID-NAME' combination. This value defaults from
PO_VENDORS.AWT_GROUP_ID.
Validation: Only allowed if
PO_VENDORS_SITES_ALL.ALLOW_AWT_FLAG = 'Y'.
Validated against: AP_AWT_GROUPS.GROUP_ID
Destination: PO_VENDOR_SITES_ALL.AWT_GROUP_ID
AWT_GROUP_NAME
This is the name for the automatic withholding tax group that will default for supplier
site invoices. This corresponds to the AWT_GROUP_ID. A value can be provided for
either or both columns. If both are provided, the system will check to ensure that the
values match a valid 'ID-NAME' combination.
Validation: Only allowed if
PO_VENDORS_SITES_ALL.ALLOW_AWT_FLAG = 'Y'.
Validated against: AP_AWT_GROUPS.GROUP_NAME.

PO_VENDOR_SITES_ALL.AWT_GROUP_ID may be
GLOBAL_ATTRIBUTES (1-20)
This is the descriptive flexfield information for the supplier site. The structure of the
information entered in these columns (data types, value sets) must match the structure
of the descriptive flexfield segments defined for supplier site, or users will experience
Validation: None
Destination: PO_VENDORS_SITES_ALL.GLOBAL_ATTRIBUTES [1-20]

This is the descriptive flexfield category for the descriptive flexfield information for
import.
Validation: None
Destination: PO_VENDOR_SITES_ALL.GLOBAL_ATTRIBUTE_CATEG
ORY
EDI_TRANSACTION_HANDLING
This is the standard EDI transaction code designating action to be taken by all parties.
This value defaults from PO_VENDORS.EDI_TRANSACTION_HANDLING.
TRANSACTION HANDLING'
Destination: PO_VENDOR_SITES_ALL.EDI_TRANSACTION_HANDL
ING
EDI_ID_NUMBER
This is the EDI trading partner number for the supplier site.
Validation: None
Destination: PO_VENDOR_SITES_ALL.EDI_ID_NUMBER
EDI_PAYMENT_METHOD
This column indicates how EDI payments will be made. This value defaults from
PO_VENDORS.EDI_PAYMENT_METHOD.
PAYMENT METHOD'
Destination: PO_VENDOR_SITES_ALL.EDI_PAYMENT_METHOD
EDI_PAYMENT_FORMAT
This column indicates the type of information being transmitted when EDI Payment
Method is 'ACH'. This value defaults from PO_VENDORS.EDI_PAYMENT_FORMAT.
Validation: Valid only if EDI_PAYMENT_METHOD = 'ACH'.
Validated against
FND_LOOKUP_VALUES.LOOKUP_TYPE = 'EDI
PAYMENT FORMAT'

Destination: PO_VENDORS_SITES_ALL.EDI_PAYMENT_FORMAT
EDI_REMITTANCE_METHOD
This column indicates the party responsible for sending remittance advice to the payee.
This value defaults from PO_VENDORS.EDI_REMITTANCE_METHOD.
REMITTANCE METHOD'
Destination: PO_VENDOR_SITES_ALL.EDI_REMITTANCE_METHOD
BANK_CHARGE_BEARER
This column indicates who will pay bank charges assessed on payments to the supplier
site. This value defaults from PO_VENDORS.BANK_CHARGE_BEARER.
Validation: If
_FLAG = 'N', then this option is not available for supplier
sites. If
S_FLAG= 'Y', validated against FND_LOOKUP_VALUES
Destination: PO_VENDOR_SITES_ALL.BANK_CHARGE_BEARER
EDI_REMITTANCE_INSTRUCTION
This is the text of electronic payment instructions for a financial institution. This value
defaults from PO_VENDORS.EDI_REMITTANCE_INSTRUCTION.
Validation: None
Destination: PO_VENDOR_SITES_ALL.EDI_REMITTANCE_INSTRUC
TION
PAY_ON_CODE
If the Oracle Purchasing 'Self Billing' feature is used, this column indicates when the
invoice is to be created.
Validation: Value for this column is only valid if
AP_SUPPLIER_SITES_INT.PURCHASING_SITE_FLAG =
'Y'. Valid values are 'RECEIPT', 'USE', or
'RECEIPT_AND_USE'.

Destination: PO_VENDOR_SITES_ALL.PAY_ON_CODE
DEFAULT_PAY_SITE_ID
This is the supplier site from which payments will be made for invoices created by the
'Payment on Receipt' process.
Validation: If the current site is not a pay site (PAY_SITE_FLAG = 'N'),
then a valid pay site for the current org must be entered in
this column. Validation is then done against:
AP_SUPPLIER_SITES_ALL.VENDOR_SITE_ID where
VENDOR_ID = &THIS_SUPPLIER, ORG_ID, and
PAY_SITE_FLAG = 'Y'
Destination: PO_VENDOR_SITES_ALL.DEFAULT_PAY_SITE_ID
PAY_ON_RECEIPT_SUMMARY_CODE
This column indicates the level at which invoices will be consolidated for the supplier
site by the 'Payment on Receipt' process. The default value is PAY_SITE.
Validation: Values for this column are allowed only if a valid value is
provided for AP_SUPPLIER_SITES_INT.PAY_ON_CODE.
When AP_SUPPLIER_SITES_INT.PAY_ON_CODE =
'RECEIPT' valid values are: 'PACKING_SLIP', 'PAY_SITE',
or 'RECEIPT'. When
AP_SUPPLIER_SITES_INT.PAY_ON_CODE = USE, valid
values are: 'CONSUMPTION_ADVICE' or 'PAY_SITE'
When AP_SUPPLIER_SITES_INT.PAY_ON_CODE =
RECEIPT_AND_USE, only valid value is: 'PAY_SITE'.
Destination: PO_VENDOR_SITES_ALL.PAY_ON_RECEIPT_SUMMAR
Y_CODE
TP_HEADER_ID
EDI transaction header unique identifier.
Validation: None
Destination: PO_VENDOR_SITES_ALL.TP_HEADER_ID
ECE_TP_LOCATION_CODE
Trading partner location code for e-Commerce Gateway.
Validation: None

Destination: PO_VENDORS_SITES_ALL.ECE_TP_LOCATION_CODE
PCARD_SITE_FLAG
This column indicates whether this supplier site uses the credit card brand used in the
procurement card program of the enterprise or company. This value defaults to 'N'.
Destination: PO_VENDOR_SITES_ALL.PCARD_SITE_FLAG
MATCH_OPTION
This column indicates if invoices are matched to a purchase order or to a receipt. This
value defaults from PO_VENDORS.MATCH_OPTION.
Validation: Valid values are: 'P' (meaning: Purchase Order) and 'R'
(meaning: Receipt).
Destination: PO_VENDOR_SITES_ALL.MATCH_OPTION
COUNTRY_OF_ORIGIN_CODE
This column indicates the country in which goods are manufactured.
Validation: FND_TERRITORIES_TL.TERRITORIES_CODE
Destination: PO_VENDOR_SITES_ALL.COUNTRY_OF_ORIGIN_COD
E
FUTURE_DATED_PAYMENT_CCID
If future dated payments are used, the value entered here will be the account used for
the supplier site. If Non Multi-Org, this value defaults from
PO_VENDORS.FUTURE_DATED_PAYMENT_CCID. If Multi-Org, this value defaults
from FINANCIALS_SYSTEM_PARAMS_ALL.FUTURE_DATED_PAYMENT_CCID.
CHART_OF_ACCOUNTS_ID FROM GL_SET_OF_BOOKS
where SET_OF_BOOKS_ID =
&SITE_ORG_SET_OF_BOOKS_ID)
Destination: PO_VENDOR_SITES_ALL.FUTURE_DATED_PAYMENT_
CCID

CREATE_DEBIT_MEMO_FLAG
This column indicates whether debit memos are to be created automatically when a
Return to Supplier transaction is entered in Oracle Purchasing.
Destination: PO_VENDORS_SITES_ALL.CREATE_DEBIT_MEMO_FLA
G
OFFSET_TAX_FLAG
This column indicates whether offset taxes are allowed on invoices from the supplier
site. This value defaults from PO_VENDORS.OFFSET_TAX_FLAG.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO'.
Also, if PO_VENDORS.VENDOR_TYPE_LOOKUP_CODE
= 'EMPLOYEE', value cannot be 'Y'.
Destination: PO_VENDOR_SITES_ALL.OFFSET_TAX_FLAG
SUPPLIER_NOTIF_METHOD
This column indicates the primary method for sending purchase orders to the supplier
site. This value defaults to 'EMAIL'.
Validation: The following hard-coded values: 'EMAIL', 'PRINT', 'FAX'
Destination: PO_VENDOR_SITES_ALL.SUPPLIER_NOTIF_METHOD
EMAIL_ADDRESS
This is the email address of the supplier site contact.
Validation: None
Destination: PO_VENDOR_SITES_ALL.EMAIL_ADDRESS
REMITTANCE_EMAIL
This is the email address where remittance advice will be sent. Populating this column
activates the E-mail Remittance advice feature in Payables.
Validation: None
Destination: PO_VENDOR_SITES_ALL.REMITTANCE_EMAIL

PRIMARY_PAY_SITE_FLAG
This column indicates the default pay site for the supplier site.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'YES/NO' and
only one site per operating unit can have value = 'Y'.
Destination: PO_VENDORS_SITES_ALL.PRIMARY_PAY_SITE_FLAG
STATUS
This column indicates the current status of the record in the interface table. The user
should enter 'NEW' as the initial value for this column. After the Supplier Sites Open
Interface Import program is run, successfully imported records will be marked as
'PROCESSED' and records that are not imported will be marked 'REJECTED'.
Validation: N/A
Destination: None
REJECT_CODE
This column indicates the reason the record has been rejected by the Supplier Sites
Open Interface Import Program. This column is populated by the Supplier Sites Open
Interface Import Program and should not be entered by the user.
Validation: N/A
Destination: None
SHIPPING_CONTROL
Indicates the party responsible for arranging transportation: supplier or buyer.
Validation: FND_LOOKUP_VALUES.LOOKUP_TYPE = 'SHIPPING
CONTROL'. Valid values are 'SUPPLIER' or 'BUYER'.
Destination: PO_VENDOR_SITES_ALL.SHIPPING_CONTROL
DUNS_NUMBER
This column is A unique 9-digit identification number assigned to all business entities
in Dun & Bradstreet's database. Used only for Federal Financial installations.
Validation: N/A
Destination: None

TOLERANCE_ID
This column is the Tolerance Template Identifier
Validation: N/A
Destination: None
TOLERANCE_NAME
This column is the Tolerance Template Name
Validation: N/A
Destination: None
IBY_BANK_CHARGE_BEARER
This column is the bearer of bank charge cost
Validation: N/A
Destination: None
BANK_INSTRUCTION(1-2)_CODE
These columns are the bank instruction codes.
Validation: N/A
Destination: None
BANK_INSTRUCTION_DETAILS
This column is the additional bank instruction details
Validation: N/A
Destination: None
PAYMENT_REASON_CODE
This column is the payment reason code
Validation: N/A
Destination: None

PAYMENT_REASON_COMMENTS
This column is a free text field available for entering a reason
Validation: N/A
Destination: None
DELIVERY_CHANNEL_CODE
This column is the default delivery channel code
Validation: N/A
Destination: None
PAYMENT_FORMAT_CODE
This column is the default payment format code
Validation: N/A
Destination: None
SETTLEMENT_PRIORITY
This column is the priority for payments settlement
Validation: N/A
Destination: None
PAYMENT_TEXT_MESSAGE(1-3)
These columns are text messages for use in payment processing
Validation: N/A
Destination: None
VENDOR_SITE_INTERFACE_ID
This column is the vendor site interface identifier
Validation: N/A
Destination: None

PAYMENT_METHOD_CODE
This column is the payment method identifier
Validation: N/A
Destination: None
RETAINAGE_RATE
This column is the maximum percentage that can be withheld from an invoice as
Retainage
Validation: N/A
Destination: None
GAPLESS_INV_NUM_FLAG
This column is the Gapless Invoice Numbering Flag
Validation: N/A
Destination: None
SELLING_COMPANY_IDENTIFIER
This column is the Unique Selling Company Identifier for Supplier
Validation: N/A
Destination: None
AP_SUP_SITE_CONTACT_INT
VENDOR_SITE_ID NUMBER Required if value is

not provided for
VENDOR_SITE_COD
E and ORG_ID
and/or
OPERATING_UNIT_
NAME

VENDOR_SITE_COD VARCHAR2(15) Required if value is

E not provided for
VENDOR_SITE_ID
ORG_ID NUMBER(1) A value is required

for this column or
OPERATING_UNIT_
NAME.
OPERATING_UNIT_ NUMBER(1) A value is required

NAME for this column or
ORG_ID.
INACTIVE_DATE DATE N/A
FIRST_NAME VARCHAR2(15) N/A
MIDDLE_NAME VARCHAR2(15) N/A
LAST_NAME VARCHAR2(20) Required
PREFIX VARCHAR2(5) N/A
TITLE VARCHAR2(30) N/A
MAIL_STOP VARCHAR2(35) N/A
AREA_CODE VARCHAR2(10) N/A
PHONE VARCHAR2(15) N/A
CONTACT_NAME_ VARCHAR2(320) N/A

ALT
FIRST_NAME_ALT VARCHAR2(230) N/A
LAST_NAME_ALT VARCHAR2(230) N/A
DEPARTMENT VARCHAR2(230) N/A
EMAIL_ADDRESS VARCHAR2(200) N/A

URL VARCHAR2(2000) N/A
ALT_AREA_CODE VARCHAR2(10) N/A
ALT_PHONE VARCHAR2(15) N/A
FAX_AREA_CODE VARCHAR2(10) N/A
FAX VARCHAR2(15) N/A
VENDOR_SITE_ID
This is the unique identifier for the supplier site. This column is used to join the contact
to the appropriate supplier site. A value must be provided for this column or for the
VENDOR_SITE_CODE and either ORG_ID or OPERATING_UNIT_NAME.
Validation: PO_VENDOR_SITES_ALL.VENDOR_SITE_ID
Destination: PO_VENDOR_CONTACTS.VENDOR_SITE_ID
VENDOR_SITE_CODE
This is the name for a supplier site. This column is used to join the contact to the
appropriate supplier site. A value must be provided for this column along with either
ORG_ID or OPERATING_UNIT_NAME if no value is present for VENDOR_SITE_ID.
Note: The VENDOR_SITE_CODE is not a unique value. More than one

vendor can have a site with the same name. If the
VENDOR_SITE_CODE is shared by more than one VENDOR in the
organization, then you must enter the VENDOR_SITE_ID.
Validation: AP_SUPPLIER_SITES_INT.VENDOR_SITE_CODE
Destination: None
ORG_ID
This is the unique identifier for the operating unit. This corresponds to the

OPERATING_UNIT_NAME. A value must be provided for the ORG_ID or the
OPERATING_UNIT_NAME column, along with the VENDOR_SITE_ID or the
VENDOR_SITE_CODE column. These values are used during the import process to join
the contact with the proper supplier site. If both 'ID' and 'NAME' are provided, the
system will check to ensure that the values match a valid 'ID-NAME' combination.
Additionally, a check will be done to confirm that the VENDOR_SITE_CODE/ORG_ID
combination is also valid.
Validation: HR_OPERATING_UNITS.ORGANIZATION_ID, as well as
PO_VENDOR_SITES_ALL.ORG_ID
Destination: None
OPERATING_UNIT_NAME
This is the name for the operating unit. This corresponds to the ORG_ID. A value must
be provided for the OPERATING_UNIT_NAME or the ORG_ID column, along with the
VENDOR_SITE_ID or the VENDOR_SITE_CODE column. These values are used
during the import process to join the contact with the proper supplier site. If both 'ID'
and 'NAME' are provided, the system will check to ensure that the values match a valid
'ID-NAME' combination. Additionally, a check will be done to confirm that the
VENDOR_SITE_CODE/ORG_ID combination is also valid.
Validation: HR_OPERATING_UNITS.NAME, as well as
PO_VENDOR_SITES_ALL.ORG_ID
Destination: None
INACTIVE_DATE
The date on which the contact is no longer valid.
Destination: PO_VENDOR_CONTACTS.INACTIVE_DATE
FIRST_NAME
This is the first name of the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.FIRST_NAME

MIDDLE_NAME
This is the middle name of the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.MIDDLE_NAME
LAST_NAME
This is the last name of the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.LAST_NAME
PREFIX
This indicates the prefix for the supplier contact (Mr., Mrs., etc.)
Validation: None
Destination: PO_VENDOR_CONTACTS.PREFIX
TITLE
This indicates the title for the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.TITLE
MAIL_STOP
This indicates the mail stop for the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.MAIL_STOP
AREA_CODE
This indicates the area code for the phone number of the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.AREA_CODE

PHONE
This indicates the phone number of the supplier contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.PHONE
CONTACT_NAME_ALT
This is an alternate name for the contact for the supplier site. This column is designed
for entering both Kanji and Kana values.
Validation: None
Destination: PO_VENDOR_CONTACTS.CONTACT_NAME_ALT
FIRST_NAME_ALT
This is an alternate first name for the contact for the supplier site. This column is
designed for entering both Kanji and Kana values.
Validation: None
Destination: PO_VENDOR_CONTACTS.FIRST_NAME_ALT
LAST_NAME_ALT
This is an alternate last name for the contact for the supplier site. This column is
designed for entering both Kanji and Kana values.
Validation: None
Destination: PO_VENDOR_CONTACTS.LAST_NAME_ALT
DEPARTMENT
This is the department for the supplier site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.DEPARTMENT
EMAIL_ADDRESS
Email address for the Supplier Site contact.
Validation: None

Destination: PO_VENDOR_CONTACTS.EMAIL_ADDRESS
URL
URL for the Supplier Site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.URL
ALT_AREA_CODE
Area code for the alternate telephone number for the Supplier Site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.ALT_AREA_CODE
ALT_PHONE
Alternate telephone number for the Supplier Site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.ALT_PHONE
FAX_AREA_CODE
Area code of the facsimile number for the Supplier Site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.FAX_AREA_CODE
FAX
Facsimile number for the Supplier Site contact.
Validation: None
Destination: PO_VENDOR_CONTACTS.FAX
STATUS
Indicates the status of the record in the interface table. The user should enter 'NEW' as
the initial value for this column. After the Supplier Site Contacts Open Interface Import
program is run, successfully imported records will be marked as 'PROCESSED' and
records that are not imported will be marked 'REJECTED'.

Validation: N/A
Destination: None
REJECT_CODE
Indicates the reason the record has been rejected by the Supplier Site Contacts Open
Interface Import Program. This column is populated by the Supplier Sites Open
Interface Import Program and should not be entered by the user.
Validation: N/A
Destination: None
Sequential Numbering During Import

There are two methods you can use for sequential numbering when you use the
Payables Open Interface:
• Manual Entry without Audit. During Payables Open Interface Import, any value
entered in the column AP_INVOICES_INTERFACE.VOUCHER_NUM will be
inserted in AP_INVOICES.VOUCHER_NUM with validation.
• Automatic Voucher Numbering with Audit: A value will be obtained

automatically for the record being imported and will be populated in
AP_INVOICES.DOC_SEQUENCE_VALUE. Also, audit information will be inserted
into the audit table.
If you enter a value for DOC_CATEGORY_CODE, then Payables will ignore any value
you enter for VOUCHER_NUM, so automatic voucher numbering will always
supersede manual entry.
Account Overlay in Payables Open Interface Import

You can use the Account Overlay feature to overwrite one or more account segments of
a line expense or asset account. For example, if you are matching to a purchase order
and you know that the cost center on the purchase order is incorrect, then the Account
Overlay feature can correct this for you automatically during import if you enter a
value for COST_CENTER_SEGMENT.
Note: If a record is matching to a particular shipment and accrued on

receipt and an overlay account exists in any of the overlay segments,
then the invoice will be rejected.
Rejection Text: Line is matched to a shipment, which uses
accrual on receipt, and overlay segment is

specified.
Rejection Reason: Accrual on Receipt

Line is matched to a shipment and uses
accrual on receipt.
There are five ways that an invoice distribution can get accounting information when it
is imported from the Payables Open Interface tables:
• Expense Account in Line (DIST_CODE_COMBINATION_ID in
AP_INVOICE_LINES_INTERFACE)
• Distribution Set
• Purchase order match
• Projects information
• Proration (accounts on non-Item type lines only)
Note: Account Overlay is not implemented with proration of Tax,

Freight, or Miscellaneous lines. The account for these lines comes
from the respective Item line. All other lines not created by
proration can be overlayed. In addition, if an Item line includes tax,
then the tax account will be overlayed according to the overlay
rules of the item.
During Payables Open Interface import, the system uses values in the following
AP_INVOICE_LINES_INTERFACE table columns to overlay the account:
• DIST_CODE_CONCATENATED (Overlay account)
• BALANCING_SEGMENT
• COST_CENTER_SEGMENT
• ACCOUNT_SEGMENT
BALANCING_SEGMENT, COST_CENTER_SEGMENT, and ACCOUNT_SEGMENT

will overlay any values in DIST_CODE_CONCATENATED.
In summary, the hierarchy for overlay is as follows. Import builds the account by
overlaying the account with any values at each successive level:
• Expense/Asset account either entered directly or built by PO matching, proration,
Projects Account Generator in Quick Invoices, or Distribution Set.

(DIST_CODE_COMBINATION_ID)
• Overlay account (DIST_CODE_CONCATENATED. Can include null account

segments)
• Balancing segment, account segment, cost center segment

(BALANCING_SEGMENT, ACCOUNT_SEGMENT, COST_CENTER_SEGMENT)
For example, if you have the following values for a line, then during import, Payables
will create the Invoice Account below for the line:
This table shows how the Account Overlay feature creates an Invoice Account during
the Payables Open Interface Import process. In this example, an invoice has values for
an account, overlay GL account, account segment, cost center segment, and balancing
segment. The resulting invoice account is based on the consecutive overlaying of these
values for the different account segments.
Account 00. 000. 000. 2210. 000. 0000
Overlay 01. . . . 110. 8000

GL
Account
Account 7710
Segment
Cost 120
Center
Segment
Balancing 02
Segment
Invoice 02. 000. 120. 7710. 110. 8000

Account
The final account for the invoice must be a valid account in your chart of accounts or the
invoice will be rejected during import.
How the Quick Invoices Window Populates the Payables Open Interface Tables
If you use the Quick Invoices window to enter invoice records, you may find the
following tables helpful in understanding the Rejections Report. The following tables
shows the column that is populated by each Quick Invoices field. Note that internal ID

columns are populated, when available, to enhance performance.
The following table lists fields in the Quick Invoices header and the corresponding
column in the AP_INVOICES_ INTERFACE table.
Quick Invoices Header Field Corresponding Column in

Withholding Tax Group AWT_GROUP_ID
Description DESCRIPTION
Discountable Amount AMOUNT_APPLICABLE_TO_DISCOUNT
Document Category DOC_CATEGORY_CODE
Exchange Date EXCHANGE_DATE
Exchange Rate EXCHANGE_RATE
Exchange Rate Type EXCHANGE_RATE_TYPE
GL Date GL_DATE
Goods Received Date GOODS_RECEIVED_DATE
Invoice Amount INVOICE_AMOUNT
Invoice_Curr INVOICE_CURRENCY_CODE
Invoice_Date INVOICE_DATE
Invoice Num INVOICE_NUM
Invoice Received Date INVOICE_RECEIVED_DATE
Invoice Type INVOICE_TYPE_LOOKUP_CODE
Liability Account ACCTS_PAY_CODE_COMBINATION_ID
Pay Alone EXCLUSIVE_PAYMENT_FLAG
Payment Curr PAYMENT_CURRENCY_CODE

Quick Invoices Header Field Corresponding Column in
Pay Group PAY_GROUP_LOOKUP_CODE
Payment Method PAYMENT_METHOD_LOOKUP_CODE
Payment Rate PAYMENT_CROSS_RATE
Payment Rate Date PAYMENT_CROSS_RATE_DATE
Payment Rate Type PAYMENT_CROSS_RATE_TYPE
PO Number PO_NUMBER
Prepay Apply Amount PREPAY_APPLY_AMOUNT
Prepayment Distribution PREPAY_DIST_NUM
Prepayment GL Date PREPAY_GL_DATE
Prepayment Number PREPAY_NUM
Site VENDOR_SITE_ID
Supplier VENDOR_ID
Supplier Num VENDOR_ID
Terms TERMS_ID
Transaction Code USSGL_TRANSACTION_CODE
Voucher Num VOUCHER_NUM
(Descriptive Flexfield) ATTRIBUTE [1-15]
(Localization Descriptive Flexfield) GLOBAL_ATTRIBUTE [1-20]
The following table lists display-only fields in the Quick Invoices header and the
corresponding column in the AP_INVOICES_ INTERFACE table.

Quick Invoices Display-Only Header Fields Corresponding Column in
Invoice Total INVOICE_AMOUNT
Source SOURCE
Gateway Batch GROUP_ID
Request ID REQUEST_ID
Status STATUS
The following table lists fields in the Quick Invoices lines region and the corresponding
column in the AP_INVOICE_ LINES_INTERFACE table.
Quick Invoices Field Lines Region Corresponding Column in

1099 Type TYPE_1099
Account DIST_CODE_COMBINATION_ID
Account Segment ACCOUNT_SEGMENT
Amount AMOUNT
Balancing Segment BALANCING_SEGMENT
Cost Center Segment COST_CENTER_SEGMENT
Description DESCRIPTION
Distribution Set DISTRIBUTION_SET_ID
Expenditure Item Date EXPENDITURE_ITEM_DATE
Expenditure Organization EXPENDITURE_ORGANIZATION_ID
Expenditure Type EXPENDITURE_TYPE

Final Match FINAL_MATCH_ID
GL Date ACCOUNTING_DATE
Includes Tax AMOUNT_INCLUDES_TAX_FLAG
Income Tax Region INCOME_TAX_REGION
Line Number INVOICE_LINE_ID
Match Option MATCH_OPTION
Oracle Projects Project PROJECT_ACCOUNTING_CONTEXT
Overlay GL Account DIST_CODE_CONCATENATED
PO Distribution Number PO_DISTRIBUTION_ID
PO Item Description DESCRIPTION
PO Line Number PO_LINE_ID
PO Number PO_HEADER_ID
PO Shipment Number PO_LINE_LOCATION_ID
PO Unit of Measure PO_UNIT_OF_MEASURE
PO Unit Price UNIT_PRICE
Price Correction PRICE_CORRECTION_FLAG
Project PROJECT_ID
Project Quantity PA_QUANTITY
Prorate Across PRORATE_ACROSS_FLAG
Prorate Group LINE_GROUP_NUMBER

Quantity Invoiced QUANTITY_INVOICED
Receipt Number RECEIPT_NUMBER
Recoverable TAX_RECOVERABLE_FLAG
Release Num PO_RELEASE_ID
Ship-To Location PO_LINE_LOCATION_ID
Statistical Quantity TASK_ID
Task TASK_ID
Track as Asset ASSETS_TRACKING_FLAG
Transaction Code USSGL_TRANSACTION_CODE
Type LINE_TYPE_LOOKUP_CODE
(Descriptive Flexfield) ATTRIBUTE [1-15]
(Localization Descriptive Flexfield) GLOBAL_ATTRIBUTE [1-20]

B
Purchase Order Matching Database Tables
Purchase Order Matching Database Tables

Payables provides sophisticated purchase order matching features to ensure that you
only pay for goods and services you ordered, received and accepted. Payables is tightly
integrated with Oracle Purchasing to facilitate paperless matching, but you can take
advantage of matching to purchase orders even if you are using another purchasing
system with Payables. Note that you can match to receipts only if you use Oracle
Purchasing.
This document explains the data necessary to integrate Payables with a non-Oracle
purchasing system and describes how Payables uses the data to perform two-way,
three-way and four-way matching to purchase orders.
Important: We only include descriptions of the required tables and

columns for matching to a non-Oracle purchasing system. For complete
details on all the entities and relationships that Payables uses for
matching, see: Table Definitions Payables Applications Technical Reference
Manual.
This discussion includes the following topics:

• Understanding the Matching Tables, page B-2
• Table Descriptions, page B-3
• Matching to Purchase Orders, page B-13
• Using Invoice Validation, page B-15
• Using Encumbrance Accounting with Purchasing, page B-16
• Purging Purchasing Information, page B-17
Purchase Order Matching Database Tables B-1

Related Topics
Entering Invoices with Matched Purchase Orders in the Invoice Workbench, Oracle
Payables User Guide
Purchasing Integration, Oracle Payables User Guide
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
AutoUpgrade 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
B-2 Oracle Payables Reference Guide

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.
Important: You must populate all NOT NULL columns in the

purchasing tables.
PO_HEADERS_ALL
The following table describes column information for the PO_HEADERS_ALL table.
PO_HEADER_ID NOT NULL NUMBER Primary key
AGENT_ID NOT NULL NUMBER Foreign key:

HR_EMPLOYEES

TYPE_LOOKUP_CO NOT NULL VARCHAR2(25) Foreign Key:

DE PO_LOOKUP_
CODES
LAST_UPDATE_DA NOT NULL DATE N/A

TE
LAST_UPDATED_BY NOT NULL NUMBER N/A
SEGMENT1 NOT NULL VARCHAR2(20) PO number
SUMMARY_FLAG NOT NULL VARCHAR2(1) N
ENABLED_FLAG NOT NULL VARCHAR2(1) Y
VENDOR_ID NUMBER Foreign key:

PO_VENDORS
VENDOR_SITE_ID NUMBER Foreign key:

PO_VENDOR_SITES
TERMS_ID NUMBER N/A
FREIGHT_TERMS_ VARCHAR2(25) Foreign key:

LOOKUP_CODE PO_LOOKUP_
CODES
CURRENCY_CODE VARCHAR2(15) N/A
APPROVED_FLAG VARCHAR2(1) Y
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 defaults this value
during matching of PO Default and Quickmatch invoices in the Invoices window.
Payables Open Interface Import may also use this value as a default for matched
invoices during import.
If you choose to leave this column empty, Payables will not warn you if the purchase
order and invoice payment terms differ.
Enter a value (Lookup Type: FREIGHT TERMS) to identify the freight terms for the
purchase order. See: Lookups, Oracle Payables User Guide.
CURRENCY_CODE
Enter the currency code for the purchase order. You can obtain a list of valid codes from
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_ALL (Blanket Releases)

The following table describes column information for the PO_RELEASES_ALL (Blanket
Releases) table.
PO_RELEASE_ID NOT NULL NUMBER Primary key

TE
PO_HEADER_ID NOT NULL NUMBER Foreign key:

PO_HEADERS
RELEASE_NUM NOT NULL NUMBER Release number
AGENT_ID NOT NULL NUMBER Foreign key:

HR_EMPLOYEES
RELEASE_DATE NOT NULL DATE N/A

PO_LINES_ALL
The following matching to purchase order database table describes column information
for the PO_LINES_ALL table.
PO_LINE_ID NOT NULL NUMBER Primary key

TE

PO_HEADERS
LINE_TYPE_ID NOT NULL NUMBER Foreign key:

PO_LINE_TYPES
LINE_NUM NUMBER Used for Query
ITEM_ID NUMBER Null
ITEM_DESCRIPTION VARCHAR2(240) Display only
UNIT_PRICE NUMBER N/A
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.
See: Entering Invoices for Suppliers Subject to Income Tax Reporting Requirements,
Oracle Payables User Guide.
You can obtain a list of valid types from
AP_INCOME_TAX_TYPES.INCOME_TAX_TYPE.
PO_LINE_LOCATIONS_ALL (PO Shipments)

The following table describes column information for the PO_LINE_LOCATIONS_ALL
(PO Shipments) table.
LINE_LOCATION_I NOT NULL NUMBER Primary key

D

TE

PO_HEADERS
PO_LINE_ID NOT NULL NUMBER Foreign key:

PO_LINES
QUANTITY NUMBER Quantity ordered:

2-way match
QUANTITY_RECEIV NUMBER 3-way match

ED
QUANTITY_ACCEP NUMBER 4-way match

TED

QUANTITY_BILLED NUMBER UPDATED by

Payables
QUANTITY_CANCE NUMBER 0 or Null

LLED
UNIT_MEAS_ VARCHAR2(25) Display only

LOOKUP_CODE
PO_RELEASE_ID NUMBER Foreign key:

PO_RELEASES
SHIP_TO_LOCATIO NUMBER Foreign key:

N_ID HR_LOCATIONS
TAXABLE_FLAG VARCHAR2(1) Y or N (tax matching)
TAX_NAME VARCHAR2(15) Tax code match (TAX

DIFF HOLD)
APPROVED_FLAG VARCHAR2(1) Y
SHIPMENT_NUM NUMBER Shipment number
SHIPMENT_TYPE VARCHAR2(25) Foreign Key:

PO_LOOKUP_CODE
S
INSPECTION_ VARCHAR2(1) Y or N (4-way match)

REQUIRED_FLAG
RECEIPT_ VARCHAR2(1) Y or N (3-way match)

REQUIRED_FLAG
CLOSED_CODE VARCHAR2(1) Null
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 validated),
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.
Important: Invoice Validation 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 Invoice Validation, Payables verifies
that the tax code value for the purchase order shipment matches the tax code value on
the invoice and places a Tax Difference hold on the invoice if the tax code values don't
match.

TAX_NAME
Enter the tax value (tax code or tax group) used to verify that the tax values 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.
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_ALL (Account distribution)

Payables uses a view (PO_DISTRIBUTIONS_AP_V) to the PO_DISTRIBUTIONS_ALL
table to perform purchase order distribution matching. The following table shows
information for PO_DISTRIBUTIONS_ALL.
PO_DISTRIBUTION_ NOT NULL NUMBER Primary key

ID

TE

PO_HEADERS
PO_LINE_ID NOT NULL NUMBER Foreign key:

PO_LINES
LINE_LOCATION_I NOT NULL NUMBER Foreign key:

D PO_LINE_
LOCATIONS
SET_OF_BOOKS_ID NOT NULL NUMBER N/A

CODE_COMBINATI NUMBER Foreign key:

ON_ID GL_CODE_
COMBINATIONS
QUANTITY_ORDER NUMBER N/A

ED
QUANTITY_DELIVE NUMBER Display only

RED
QUANTITY_BILLED NUMBER UPDATED by

Payables
QUANTITY_CANCE NUMBER 0 or Null

LLED
DELIVER_TO_PERS NUMBER Foreign key:

ON_ID HR_EMPLOYEES
RATE NUMBER Foreign currency
AMOUNT_BILLED NUMBER UPDATED by

Payables
ENCUMBERED_AM NUMBER If encumbrance

OUNT accounting enabled
BUDGET_ACCOUN NUMBER N/A

T_ID
ACCRUAL_ACCOU NUMBER N/A

NT_ID
VARIANCE_ACCOU NUMBER N/A

NT_ID
DISTRIBUTION_NU NOT_NULL NUMBER distribution number

M
PROJECT_ID NUMBER Projects
TASK_ID NUMBER Projects

EXPENDITURE_TYP VARCHAR2(30) Projects

E
PROJECT_ VARCHAR2(30) Projects

ACCOUNTING_CO
NTEXT
EXPENDITURE_ NUMBER Projects

ORGANIZATION_ID
EXPENDITURE_ITE DATE Projects

M_ DATE
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.
Important: 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 validated), 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.
Important: Invoice Validation 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 validated),
the system 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 account for an invoice until the invoice is validated.
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
Important: 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. See: Final Matching Invoices and Final Closing Purchase
Orders, Oracle Payables User Guide.
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.
Match a Prepayment Invoice to a Purchase Order

A prepayment invoice is an advance payment. There may or may not be a receipt
available at the time of its payment. Once a purchasing document is prepared, you may
not change the matching option of the reference document as per the invoice type.
Therefore, you can now match a prepayment invoice to a purchase order from all
invoice entry interfaces without any restriction, even when the purchase order
shipment was created with match option as Receipt regardless of the match approval
level. An error displays only in the case of a non-prepayment invoices that it cannot be
matched.
Using Invoice Validation

Invoice Validation is the Payables feature that performs two-, three-, or four-way
matching. An invoice must pass Invoice Validation before you can pay or account for
the invoice. Invoice Validation 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 Invoice Validation for all invoices, not just matched invoices, since it
also checks for distribution variances, tax variances, and exchange rate information.
You can submit Invoice Validation online for an invoice or in batch for a group of
invoices. See also: Invoice Validation, Oracle Payables User Guide.

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.
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 Invoice Validation, 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)
See also: Releasing Holds, Oracle Payables User Guide.
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 Invoice Validation validates 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.
Important: Invoice Validation 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 Invoice Validation.
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. See also:
Encumbrances in Payables, Oracle Payables User Guide.
Budgetary Control
The budgetary control feature does not use purchasing information unless you install
Oracle Purchasing.
Related Topics
Encumbrance Entries in Payables, Oracle Payables User Guide
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. See:
Purging Records, Oracle Payables User Guide.

C
Predefined Setup for Oracle Subledger
Accounting
Data that Oracle Payables Predefines for Oracle Subledger Accounting

Oracle Payables provides predefined data for Oracle Subledger Accounting that you
can use to integrate the two applications. When you run the Create Accounting
program to create draft or final subledger accounting, the program uses the predefined
data to determine how to create the accounting. Payables predefines setup for
Subledger Accounting so that the Create Accounting program accepts the default
accounting information from AutoAccounting without change. Subledger Accounting
transfers the final accounting to Oracle General Ledger.
You can optionally define your own subledger accounting rules to overwrite the default
accounts from the accounting events.
Note: You must use an Oracle Payables responsibility to query

predefined data that is associated with the Oracle Payables application.
The following sections describe the data that Payables predefines in Subledger
Accounting:
• Applications, page C-2
• Event Entities, page C-2
• Event Classes and Event Types, page C-3
• Process Categories, page C-4
• Accounting Event Class Options, page C-4
• Sources, Source Assignments, and Accounting Attribute Assignments, page C-6
Predefined Setup for Oracle Subledger Accounting C-1

• Journal Line Types, page C-6
• Account Derivation Rules, page C-49
• Journal Lines Definitions, page C-53
• Application Accounting Definitions, page C-66
• Subledger Accounting Methods, page C-66
Applications
Oracle Payables predefines one application in Oracle Subledger Accounting named
Oracle Payables. Most of the data that Oracle Payables predefines for Oracle Subledger
Accounting is associated with the Oracle Payables application. The following table shows
the attribute values that Oracle predefines for the Oracle Payables application. The first
column lists the fields and the second column lists the values for each field.
Predefined Oracle Payables Application
Field Value
Application Oracle Payables
Drilldown AP_DRILLDOWN_PUB_PKG.DRILLDOWN
Use Security Yes
Policy Function XLA_SECURITY_POLICY_PKG.MO_POLICY
Journal Source Payables
Third Party Control Account Type Supplier
Subject to Validation No
Calculate Reporting Currency Amounts Yes
Event Entities
The following table lists the setup information that Oracle predefines for the event
entities.
C-2 Oracle Payables Reference Guide

Predefined Event Entities
Application Entity Name Description Gapless Event

Processing
Oracle Payables AP Invoices Invoices No
Oracle Payables AP Payments Payments No
Event Classes and Event Types

Oracle Payables predefines event classes and event types for each event entity that
belongs to the Oracle Payables application.
The following table lists the event classes and event types that Oracle Payables
predefines for the Oracle Payables application.
Predefined Event Classes and Event Types for the Oracle Payables Application
Entity Event Class Name
AP Invoices Credit Memos
AP Invoices Debit Memos
AP Invoices Expense Reports
AP Invoices Invoices
AP Invoices Invoice_Burden
AP Invoices Prepayment Applications
AP Invoices Prepayment Invoices
AP Invoices Prepayments
AP Invoices Prepayment_Burden
AP Invoices Prepay_Application_Burden

Entity Event Class Name
AP Invoices Standard Invoices
AP Payments Future Dated Payments
AP Payments Payments
AP Payments Reconciled Payments
AP Payments Refunds
Process Categories
Oracle Payables predefines the following process categories:
• Invoices
• Payments
• Third Party Merge
Accounting Event Class Options

Accounting event class options define attributes of an event class. Oracle Payables
defines the accounting event class options for each predefined event class.
The following table lists the accounting event class options that Oracle Payables
predefines for the Oracle Payables application.
Predefined Accounting Event Class Options for the Oracle Payables Application
Event Class Process Default Journal Transaction Balance Type

Category Category View
Burden for Invoices Purchase AP_SLA_INVOI Encumbrance

Invoices Invoices CES_TRANSAC
TION_V

Prepayment Invoices CES_TRANSAC
Applications TION_V

Event Class Process Default Journal Transaction Balance Type
Category Category View

Prepayments Invoices CES_TRANSAC
TION_V
Credit Memos Invoices Purchase AP_SLA_INVOI Actual and

Invoices CES_TRANSAC Encumbrance
TION_V
Debit Memos Invoices Purchase AP_SLA_INVOI Actual and

TION_V
Invoices Invoices Purchase AP_SLA_INVOI Actual and

TION_V
Prepayment Invoices Purchase AP_SLA_INVOI Actual and

Applications Invoices CES_TRANSAC Encumbrance
TION_V
Prepayments Invoices Purchase AP_SLA_INVOI Actual and

TION_V
Future Dated Payments Payments AP_SLA_PAYM Actual

Payments ENTS_TRANSA
CTION_V
Payments Payments Payments AP_SLA_PAYM Actual and

ENTS_TRANSA Encumbrance
CTION_V
Reconciled Payments Reconciled AP_SLA_PAYM Actual and

Payments Payments ENTS_TRANSA Encumbrance
CTION_V
Refunds Payments Payments AP_SLA_PAYM Actual and

ENTS_TRANSA Encumbrance
CTION_V

Sources, Source Assignments, and Accounting Attribute Assignments
Oracle Payables predefines sources, source assignments, and accounting attribute
assignments for Oracle Subledger Accounting.
You can use the Accounting Methods Builder to review the sources, source
assignments, and accounting attribute assignments. You must access the Accounting
Methods Builder using an Oracle Payables responsibility if you want to review the
sources, source assignments, and accounting attribute assignments associated with the
Oracle Payables application.
Note: You cannot make changes to predefined sources, source

assignments, or accounting attribute assignments. However, you can
define your own custom sources.
If you choose to define your own journal line types or application
accounting definitions, then you can override the default accounting
attribute assignments.
Oracle Payables provides numerous predefined sources. When you use the Sources
window to review the predefined sources, you can optionally export the queried
sources from the application to a Microsoft Excel spreadsheet.
To export a list of sources:
1. From an Oracle responsibility, navigate to the Sources window.
2. Query the records you want to export.
3. Place your cursor in the multi-row block that contains the records to be exported.
4. Choose Export from the File menu.
See: Exporting Records to a File, Oracle E-Business Suite User's Guide
Journal Line Types

Oracle Payables predefines journal line types for each predefined event class. Oracle
Payables specifies conditions for the use of each journal line type. The following table
lists the journal line types that Oracle predefines for the Oracle Payables application.

Predefined Journal Line Types for the Oracle Payables application
Event Class Name Balance Type Side
Burden for Invoices Burdened Invoice Encumbrance Debit

Encumbrance
Burden for Invoices Burden Invoice Encumbrance Debit

Encumbrance
Burden for Invoices Relieve Project Encumbrance Credit

Encumbrance
Burden for Invoices Reserve Project Encumbrance Debit

Encumbrance
Burden for Invoices Reverse PO Burdened Encumbrance Credit

Encumbrance
Burden for Invoices Reverse PO Burden Encumbrance Credit

Encumbrance
Burden for Invoices Reverse Release Encumbrance Credit

Burdened
Encumbrance
Burden for Invoices Reverse Release Encumbrance Credit

Burden Encumbrance
Burden for Prepayment Encumbrance Credit

Prepayment Application
Applications Burdened
Encumbrance

Prepayment Application Burden
Applications Encumbrance

Applications Encumbrance

Burden for Relieve Project Encumbrance Credit

Prepayment Encumbrance
Applications
Burden for Reserve Project Encumbrance Debit

Prepayment Encumbrance
Applications
Burden for Prepayment Encumbrance Debit

Prepayments Burdened
Encumbrance
Burden for Prepayment Burden Encumbrance Debit

Prepayments Encumbrance
Burden for Prepayment Encumbrance Debit

Burden for Relieve Project Encumbrance Credit

Burden for Reserve Project Encumbrance Debit

Credit Memos Accrual Actual Debit
Credit Memos Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance
Credit Memos Non-Primary Ledger Actual Gain/Loss

Tax Exchange Rate
Variance
Credit Memos Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Credit Memos Encumbrance Encumbrance Debit

Amount Variance

Credit Memos CM PO Encumbrance Encumbrance Credit

for Non-Recoverable
Tax
Credit Memos Credit Memo PO Encumbrance Credit

Encumbrance
Credit Memos Exchange Rate Actual Debit

Variance

Reversal Entry of
Exchange Rate
Variance for Credit
Memo

Exchange Rate
Variance
Credit Memos Freight Expense Actual Debit

Reversal Entry of
Freight Expense
Credit Memos Encumbrance Freight Encumbrance Debit

Expense
Credit Memos Invoice Price Actual Debit

Variance

Reversal Entry of
Invoice Price
Variance
Credit Memos Encumbrance Invoice Encumbrance Debit

Price Variance
Credit Memos Item Expense Actual Debit


Reversal Entry of
Item Expense
Credit Memos Encumbrance Item Encumbrance Debit

Expense
Credit Memos Liability, Basic Actual Credit
Credit Memos Liability with Actual Credit

Automatic Offsets
Account Segment
Credit Memos Liability with Actual Credit

Automatic Offsets
Balancing Segment
Credit Memos Miscellaneous Actual Debit

Expense

Miscellaneous
Expense

Reversal Entry of
Miscellaneous
Expense for Credit
Memo
Credit Memos Non-Recoverable Tax Actual Debit

Accrual
Credit Memos Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax

Non-Recoverable Tax


Reversal Entry of
Quantity Variance

Quantity Variance
Credit Memos Recoverable Tax Actual Debit

Reversal Entry of
Recoverable Tax

Recoverable Tax
Credit Memos Retainage in Accrual Actual Debit

Basis for Credit
Memos

Self-Assessed
Non-Recoverable Tax

Reversal Entry of
Self-Assessed
Non-Recoverable Tax
Credit Memos Self-Assessed Actual Debit

Non-Recoverable Tax

Recoverable Tax
Credit Memos Self-Assessed Tax Actual Credit

Liability

Non-Recoverable Tax
Accrual


Reversal Entry of Tax
Amount Variance
Credit Memos Encumbrance Tax Encumbrance Debit

Amount Variance

Exchange Rate
Variance

Exchange Rate
Variance
Credit Memos Tax Exchange Rate Actual Debit

Variance
Credit Memos Tax Invoice Price Actual Debit

Variance

Invoice Price
Variance

Invoice Price
Variance

Quantity Variance

Quantity Variance
Credit Memos Tax Rate Variance Actual Debit

Rate Variance


Rate Variance
Credit Memos Withholding Tax Actual Debit
Credit Memos Federal Credit Memo Actual Debit

Downward
Anticipated PYA
Credit
Credit Memos Federal Credit Memo Actual Credit

Downward PYA
Debit

Downward
Unanticipated PYA
Credit

Upward PYA Credit
Credit Memos Federal Credit Memo Actual Credit

Upward PYA Debit
Credit Memos Federal Direct Fund Actual Debit

Credit Memos Credit
Credit Memos Federal Direct Fund Actual Credit

Credit Memos Debit
Credit Memos Federal Direct Fund Actual Debit

Reversal Credit
Memos Credit
Credit Memos Federal Direct Fund Actual Credit

Reversal Credit
Memos Debit
Credit Memos Federal Credit Actual Debit

Memos Expenditure
Credit

Credit Memos Federal Credit Actual Credit

Memos Expenditure
Debit
Debit Memos Accrual Actual Debit
Debit Memos Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance
Debit Memos Non-Primary Ledger Actual Gain/Loss

Tax Exchange Rate
Variance
Debit Memos Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Debit Memos Encumbrance Encumbrance Debit

Amount Variance
Debit Memos DM PO Encumbrance Encumbrance Credit

For Non-Recoverable
Tax
Debit Memos Debit Memo PO Encumbrance Credit

Encumbrance
Debit Memos Exchange Rate Actual Debit

Variance

Reversal Entry of
Exchange Rate
Variance

Exchange Rate
Variance
Debit Memos Freight Expense Actual Debit


Reversal Entry of
Freight Expense
Debit Memos Encumbrance Freight Encumbrance Debit

Expense
Debit Memos Invoice Price Actual Debit

Variance

Reversal Entry of
Invoice Price
Variance
Debit Memos Encumbrance Invoice Encumbrance Debit

Price Variance
Debit Memos Item Expense Actual Debit

Reversal Entry of
Item Expense
Debit Memos Encumbrance Item Encumbrance Debit

Expense
Debit Memos Liability, Basic Actual Credit
Debit Memos Liability with Actual Credit

Automatic Offsets
Account Segment
Debit Memos Liability with Actual Credit

Automatic Offsets
Balancing Segment
Debit Memos Miscellaneous Actual Debit

Expense


Reversal Entry of
Miscellaneous
Expense

Miscellaneous
Expense
Debit Memos Non-Recoverable Tax Actual Debit

Accrual
Debit Memos Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax

Non-Recoverable Tax

Reversal Entry of
Quantity Variance

Quantity Variance
Debit Memos Recoverable Tax Actual Debit

Reversal Entry of
Recoverable Tax

Recoverable Tax
Debit Memos Retainage in Accrual Actual Debit

Basis for Debit
Memos


Self-Assessed
Non-Recoverable Tax

Reversal Entry of
Self-Assessed
Non-Recoverable Tax
Debit Memos Self-Assessed Actual Debit

Non-Recoverable Tax

Recoverable Tax
Debit Memos Self-Assessed Tax Actual Credit

Liability

Non-Recoverable Tax
Accrual

Amount Variance
Debit Memos Encumbrance Tax Encumbrance Debit

Amount Variance

Exchange Rate
Variance
Debit Memos Tax Exchange Rate Actual Debit

Variance

Exchange Rate
Variance
Debit Memos Tax Invoice Price Actual Debit

Variance


Invoice Price
Variance

Invoice Price
Variance

Quantity Variance

Quantity Variance
Debit Memos Tax Rate Variance Actual Debit

Rate Variance

Rate Variance
Debit Memos Withholding Tax Actual Debit
Debit Memos Federal Debit Memos Actual Debit

Expenditure Credit
Debit Memos Federal Debit Memos Actual Credit

Expenditure Debit
Debit Memos Federal Debit Memo Actual Debit

Downward
Anticipated PYA
Credit
Debit Memos Federal Debit Memo Actual Credit

Downward PYA
Debit


Downward
Unanticipated PYA
Credit

Upward PYA Credit
Debit Memos Federal Debit Memo Actual Credit

Upward PYA Debit
Debit Memos Federal Direct Fund Actual Debit

Debit Memos Credit
Debit Memos Federal Direct Fund Actual Credit

Debit Memos Debit
Debit Memos Federal Direct Fund Actual Debit

Reversal Debit
Memos Credit
Debit Memos Federal Direct Fund Actual Credit

Reversal Debit
Memos Debit
Future Dated Cash Clearing, Actual Credit

Payments Pooled Bank Account,
Account Segment,
Invoice Exchange
Rate

Balancing
Segment,Invoice
Exchange Rate

Payments Non-Pooled Bank
Account


Account Segment

Balancing Segment

Payments Non-Pooled Bank
Account using
Invoice Exchange
Rate
Future Dated Cash, Non-Pooled Actual Credit

Payments Bank Account
Future Dated Cash, Pooled Actual Credit

Payments Account, Account
Segment
Future Dated Cash, Pooled Actual Credit

Payments Account, Balancing
Segment
Future Dated Interim Tax Line Actual Credit

Payments Reversal at Payment
Maturity
Future Dated Deferred Recoverable Actual Debit

Payments Tax at Payment
Maturity
Future Dated Future Dated Actual Debit

Payments Payment
Future Dated Future Payment Actual Credit

Payments Rounding
Future Dated Non-Primary Ledger Actual Gain/Loss

Payments Gain/Loss

Future Dated Gain Actual Credit

Payments
Future Dated Loss Actual Credit

Payments
Invoices Accrual Actual Debit
Invoices Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance
Invoices Non-Primary Ledger Actual Gain/Loss

Tax Exchange Rate
Variance
Invoices Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Invoices Encumbrance Encumbrance Debit

Amount Variance
Invoices Exchange Rate Actual Debit

Variance

Reversal Entry of
Exchange Rate
Variance

Exchange Rate
Variance
Invoices Freight Expense Actual Debit

Reversal Entry of
Freight Expense

Invoices Encumbrance Freight Encumbrance Debit

Expense
Invoices Invoice Prepay Encumbrance Debit

Encumbrance DR
Invoices Invoice PO Encumbrance Credit

Encumbrance For
Non-Recoverable Tax
Invoices Invoice PO Encumbrance Credit

Encumbrance
Invoices Invoice Price Actual Debit

Variance

Reversal Entry of
Invoice Price
Variance
Invoices Encumbrance Invoice Encumbrance Debit

Price Variance
Invoices Item Expense Actual Debit

Reversal Entry of
Item Expense
Invoices Encumbrance Item Encumbrance Debit

Expense
Invoices Liability, Basic Actual Credit
Invoices Liability with Actual Credit

Automatic Offsets
Account Segment
Invoices Liability with Actual Credit

Automatic Offsets
Balancing Segment

Invoices Miscellaneous Actual Debit

Expense

Reversal Entry of
Miscellaneous
Expense

Miscellaneous
Expense
Invoices Non-Recoverable Tax Actual Debit

Accrual
Invoices Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax

Non-Recoverable Tax

Quantity Variance

Reversal Entry of
Quantity Variance
Invoices Recoverable Tax Actual Debit

Reversal Entry of
Recoverable Tax

Recoverable Tax
Invoices Retainage in Accrual Actual Debit

Basis

Invoices Retainage Release, Actual Debit

Accrual Basis

Self-Assessed
Non-Recoverable Tax

Reversal Entry of
Self-Assessed
Non-Recoverable Tax
Invoices Self-Assessed Actual Debit

Non-Recoverable Tax

Recoverable Tax
Invoices Self-Assessed Tax Actual Credit

Liability

Non-Recoverable Tax
Accrual
Invoices Encumbrance Tax Encumbrance Debit

Exchange Rate
Variance

Amount Variance

Amount Variance

Exchange Rate
Variance
Invoices Tax Exchange Rate Actual Debit

Variance

Invoices Tax Invoice Price Actual Debit

Variance

Invoice Price
Variance

Invoice Price
Variance

Quantity Variance

Quantity Variance
Invoices Tax Rate Variance Actual Debit

Rate Variance

Rate Variance
Invoices Withholding Tax Actual Debit
Invoices Federal Direct Actual Credit

Expenditure Invoice
Credit
Invoices Federal Direct Actual Debit

Expenditure Invoice
Debit
Invoices Federal Invoice Actual Debit

Downward
Anticipated PYA
Credit

Invoices Federal Invoice Actual Credit

Downward PYA
Debit

Downward
Unanticipated PYA
Credit

Upward PYA Credit

Upward PYA Debit

Amount Variance
Credit

Amount Variance
Debit
Invoices Federal Direct Fund Actual Credit

Invoice Credit
Invoices Federal Direct Fund Actual Debit

Invoice Debit
Invoices Federal Invoice Price Actual Debit

Variance Credit
Invoices Federal Invoice Price Actual Credit

Variance Debit

Quantity Variance
Credit

Quantity Variance
Debit


Reverse Invoice
Credit

Reverse Invoice Debit
Invoices Federal Paid Actual Credit

Obligation Expired
Reversal Credit
Invoices Federal Paid Actual Credit

Obligation Reversal
Credit
Invoices Federal Paid Actual Debit

Obligation Reversal
Debit
Invoices Federal Paid Actual Debit

Obligation PYA
Reversal Debit
Payments Accrual Actual Debit
Payments Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance

Tax Exchange Rate
Variance
Payments Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Payments Cash Clearing Actual Debit
Payments Cash Clearing, Actual Credit

Pooled Bank Account
and Automatic
Offsets Account

Payments Cash Clearing, Actual Credit

Pooled Bank Account
and Automatic
Offsets Balancing
Payments Cash Clearing using Actual Credit

Automatic Offsets
Account and Invoice
Exchange Rate
Payments Cash Clearing using Actual Credit

Automatic Offsets
Balancing and Invoice
Exchange Rate
Payments Cash Clearing ( Actual Credit

Invoice Exchange
Rate)
Payments Cash Actual Credit
Payments Cash, Pooled Account Actual Credit

using Automatic
Offsets Account
Payments Cash, Pooled Account Actual Credit

using Automatic
Offsets Balancing
Payments Interim Tax Line Actual Credit

Reversal
Payments Deferred Recoverable Actual Debit

Tax at Payment
Payments Discount - Accrual Actual Credit

Basis
Payments Discount - Cash Basis Actual Credit
Payments Exchange Rate Actual Debit

Variance


Reversal Entry of
Exchange Rate
Variance
Payments Final Payment Actual Credit

Rounding
Payments Freight Expense Actual Debit

Reversal Entry of
Freight Expense
Payments Future Dated Actual Credit

Payment
Payments Future Dated Actual Credit

Payment (Invoice
Exchange Rate)

Gain/Loss
Payments Gain Actual Credit
Payments Interest Expense Actual Debit
Payments Invoice Price Actual Debit

Variance

Reversal Entry of
Invoice Price
Variance
Payments Item Expense Actual Debit

Reversal Entry of
Item Expense

Payments Liabilty for Actual Debit

Withholding at
Payment
Payments Liability Actual Debit
Payments Loss Actual Credit
Payments Miscellaneous Actual Debit

Expense

Reversal Entry of
Miscellaneous
Expense
Payments Non-Recoverable Tax Actual Debit

Accrual
Payments Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax
Payments Prepaid Expense - Actual Debit

Cash Basis

Reversal Entry of
Quantity Variance
Payments Recoverable Tax Actual Debit
Payments Retainage in Cash Actual Debit

Basis at Payment
Payments Retainage Release, Actual Debit

Cash Basis at
Payment


Amount Variance

Exchange Rate
Variance
Payments Tax Exchange Rate Actual Debit

Variance
Payments Tax Invoice Price Actual Debit

Variance

Invoice Price
Variance

Quantity Variance
Payments Tax Rate Variance Actual Debit

Rate Variance
Payments Withholding Tax - Actual Credit

Accrual Basis
Payments Withholding Tax - Actual Credit

Cash Basis
Payments Federal Direct Actual Credit

Expenditure Payment
Credit
Payments Federal Direct Actual Debit

Expenditure Payment
Debit

Payments Federal Payables Actual Credit

Discount Credit
Payments Federal Direct Fund Actual Credit

Payment Credit
Payments Federal Direct Fund Actual Debit

Payment Debit
Payments Federal Treasury Actual Debit

Cash Account - DR
Payments Federal Disbursement Actual Credit

in Transit Account -
CR
Payments Federal Treasury Actual Credit

Confirmation Paid
Account - CR
Payments Federal Treasury Actual Debit

Confirmation Unpaid
Account - DR
Payments Accrual - Prepayment Actual Credit

Clearing Rate
Prepayment Accrual - Prepayment Actual Credit

Applications Payment Rate
Prepayment Non-Primary Ledger Actual Gain/Loss

Applications Exchange Rate
Variance

Applications Tax Exchange Rate
Variance
Prepayment Interim Tax Line Actual Credit

Applications Reversal

Prepayment Deferred Recoverable Actual Debit

Applications Tax at Prepayment
Application
Prepayment Exchange Rate Actual Credit

Applications Variance at
Prepayment Clearing
Rate
Prepayment Exchange Rate Actual Credit

Prepayment Payment
Rate
Prepayment Final Application Actual Credit

Applications Rounding - Accrual
Basis at Prepayment
Rate

Applications Rounding - Cash
Basis at Prepayment
Clearing Rate

Applications Rounding - Cash
Basis at Prepayment
Payment Rate
Prepayment Final Payment Actual Credit

Applications Rounding, Liability
Prepayment Freight Expense - Actual Credit

Applications Prepayment Clearing
Rate
Prepayment Freight Expense at Actual Credit

Applications Prepayment Payment
Rate

Applications Gain/Loss

Prepayment Gain Actual Debit

Applications
Prepayment Invoice Price Actual Credit

Prepayment Clearing
Rate
Prepayment Invoice Price Actual Credit

Prepayment Payment
Rate
Prepayment Item Expense at Actual Credit

Rate
Prepayment Liability Actual Credit

Applications
Prepayment Loss Actual Debit

Applications
Prepayment Miscellaneous Actual Credit

Applications Expense -
Prepayment Clearing
Rate
Prepayment Miscellaneous Actual Credit

Applications Expense at
Prepayment Payment
Rate
Prepayment Non-Recoverable Tax Actual Credit

Applications Accrual - Prepayment
Clearing Rate

Applications Accrual - Prepayment
Payment Rate


Applications at Prepayment
Clearing Rate

Payment Rate
Prepayment Prepaid Expense - Actual Debit

Applications Accrual Basis at
Prepayment Rate

Applications Cash Basis at
Prepayment Clearing
Rate

Prepayment Payment
Rate
Prepayment Encumbrance Encumbrance Credit

Applications Reversal Entry of
Prepayment
Application Prepaid
Expense
Prepayment Encumbrance for Encumbrance Debit

Applications Prepaid Expense
Prepayment
Application
Prepayment Encumbrance PO for Encumbrance Credit

Applications Prepayment
Application
Prepayment Recoverable Tax at Actual Credit

Rate

Prepayment Recoverable Tax at Actual Credit

Rate
Prepayment Retainage Cash Basis Actual Credit

Clearing Rate
Prepayment Retainage Cash Basis Actual Credit

Payment Rate
Prepayment Retainage Release Actual Credit

Prepayment Clearing
Rate
Prepayment Retainage Release Actual Credit

Prepayment Payment
Rate
Prepayment Tax Difference Actual Credit

Applications
Prepayment Tax Exchange Rate Actual Credit

Prepayment Clearing
Rate
Prepayment Tax Exchange Rate Actual Credit

Prepayment Payment
Rate
Prepayment Tax Invoice Price Actual Credit

Prepayment Clearing
Rate

Prepayment Tax Invoice Price Actual Credit

Prepayment Payment
Rate
Prepayment Tax Rate Variance at Actual Credit

Rate
Prepayment Tax Rate Variance at Actual Credit

Rate
Prepayments Accrual Actual Debit
Prepayments Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance
Prepayments Non-Primary Ledger Actual Gain/Loss

Tax Exchange Rate
Variance
Prepayments Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Prepayments Encumbrance Encumbrance Debit

Amount Variance
Prepayments Prepayment Deferred Actual Debit

Recoverable Tax

Reversal Entry of
Exchange Rate
Variance

Exchange Rate
Variance

Prepayments Exchange Rate Actual Debit

Variance

Reversal Entry of
Freight Expense
Prepayments Encumbrance Freight Encumbrance Debit

Expense
Prepayments Freight Expense Actual Debit

Reversal Entry of
Invoice Price
Variance
Prepayments Encumbrance Invoice Encumbrance Debit

Price Variance
Prepayments Invoice Price Actual Debit

Variance

Reversal Entry of
Item Expense
Prepayments Encumbrance Item Encumbrance Debit

Expense
Prepayments Liability, Basic Actual Credit
Prepayments Liability, Automatic Actual Credit

Offsets, Account
Prepayments Liability, Automatic Actual Credit

Offsets, Balancing

Reversal Entry of
Miscellaneous
Expense


Miscellaneous
Expense
Prepayments Miscellaneous Actual Debit

Expense

Reversal Entry of
Non-Recoverable Tax

Non-Recoverable Tax
Prepayments Non-Recoverable Tax Actual Debit
Prepayments Non-Recoverable Tax Actual Debit

Accrual
Prepayments Prepay PO Encumbrance Credit

Encumbrance For
Non-Recoverable Tax
Prepayments Prepaid Expense Actual Debit
Prepayments Prepayment PO Encumbrance Credit

Encumbrance

Reversal Entry of
Quantity Variance

Quantity Variance

Reversal Entry of
Recoverable Tax

Recoverable Tax

Prepayments Recoverable Tax Actual Debit
Prepayments Self-Assessed Encumbrance Debit

Non-Recoverable Tax

Reversal Entry of
Self-Assessed
Non-Recoverable Tax
Prepayments Self-Assessed Actual Debit

Non-Recoverable Tax

Recoverable Tax
Prepayments Self-Assessed Tax Actual Credit

Liability

Non-Recoverable Tax
Accrual

Amount Variance
Prepayments Encumbrance Tax Encumbrance Debit

Amount Variance

Exchange Rate
Variance

Exchange Rate
Variance
Prepayments Tax Exchange Rate Actual Debit

Variance


Invoice Price
Variance

Invoice Price
Variance
Prepayments Tax Invoice Price Actual Debit

Variance

Quantity Variance

Quantity Variance

Rate Variance

Rate Variance
Prepayments Tax Rate Variance Actual Debit
Prepayments Withholding Tax Actual Debit
Reconciled Payments Accrual Actual Debit
Reconciled Payments Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance

Tax Exchange Rate
Variance

Reconciled Payments Encumbrance Encumbrance Credit

Reversal Entry of
Amount Variance
Reconciled Payments Bank Charges Actual Debit
Reconciled Payments Bank Errors Actual Debit
Reconciled Payments Cash - When Actual Credit

Payment Cleared
with Accounting
Done at Payment
Issue and Clearing
Reconciled Payments Cash - Payment Actual Credit

accounted at Clearing
with Automatic
Offsets of Account
Segment
Reconciled Payments Cash - Payment Actual Credit

accounted at Clearing
with Automatic
Offsets of Offsets
Balancing
Reconciled Payments Cash - Clearing Only Actual Credit
Reconciled Payments Cash Clearing Actual Debit
Reconciled Payments Cash Clearing of Bills Actual Debit

Payable
Reconciled Payments Deferred Recoverable Actual Debit

Tax at Payment
Reconciled Payments Interim Tax Reversal Actual Credit

when Payment
Cleared
Reconciled Payments Discount - Accrual Actual Credit

Basis

Reconciled Payments Discount - Cash Basis Actual Credit
Reconciled Payments Exchange Rate Actual Debit

Variance

Reversal Entry of
Exchange Rate
Variance
Reconciled Payments Final Payment Actual Credit

Rounding
Reconciled Payments Freight Expense Actual Debit

Reversal Entry of
Freight Expense
Reconciled Payments Gain - Actual Credit

Invoice/Clearing

Gain/Loss

Maturity/Clearing

Payment/Clearing
Reconciled Payments Interest Expense Actual Debit
Reconciled Payments Invoice Price Actual Debit

Variance

Reversal Entry of
Invoice Price
Variance
Reconciled Payments Item Expense Actual Debit


Reversal Entry of
Item Expense
Reconciled Payments Liabilty for Actual Debit

Withholding When
Payment Cleared
Reconciled Payments Liability Actual Debit
Reconciled Payments Loss - Actual Credit

Invoice/Clearing

Maturity/Clearing

Payment/Clearing
Reconciled Payments Miscellaneous Actual Debit

Expense

Reversal Entry of
Miscellaneous
Expense
Reconciled Payments Non-Recoverable Tax Actual Debit

Accrual
Reconciled Payments Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax
Reconciled Payments Payment to Clearing Actual Debit

Rounding
Reconciled Payments Prepaid Expense Actual Debit


Reversal Entry of
Quantity Variance
Reconciled Payments Recoverable Tax Actual Debit
Reconciled Payments Retainage in Cash Actual Debit

Basis at Clearing
Reconciled Payments Retainage Release, Actual Debit

Cash Basis at
Clearing

Amount Variance

Exchange Rate
Variance
Reconciled Payments Tax Exchange Rate Actual Debit

Variance
Reconciled Payments Tax Invoice Price Actual Debit

Variance

Invoice Price
Variance

Quantity Variance
Reconciled Payments Tax Rate Variance Actual Debit

Rate Variance

Reconciled Payments Withholding Tax - Actual Credit

Accrual Basis
Reconciled Payments Withholding Tax - Actual Credit

Cash Basis
Refunds Accrual Actual Debit
Refunds Non-Primary Ledger Actual Gain/Loss

Exchange Rate
Variance

Tax Exchange Rate
Variance
Refunds Cash Clearing Actual Credit
Refunds Cash Clearing, Actual Credit

Pooled Bank Account,
Account Segment

Balancing

Account Segment,
Invoice Exchange
Rate

Balancing, Invoice
Exchange rate
Refunds Cash Clearing for Actual Credit

Refund Using Invoice
Exchange Rate
Refunds Cash, Non-Pooled Actual Credit

Bank Account

Refunds Cash - for refund Actual Credit

using pooled account,
automatic offsets of
Account Segment
Refunds Cash - Refund Actual Credit

accounted at clearing
with Automatic
Offsets of Balancing
Segment
Refunds Discount - Accrual Actual Credit

Basis
Refunds Discount - Cash Basis Actual Credit
Refunds Exchange Rate Actual Debit

Variance
Refunds Encumbrance Encumbrance Credit

Reversal Entry of
Exchange Rate
Variance for Refunds
Refunds Final Payment Actual Credit

Rounding
Refunds Freight Expense Actual Debit
Refunds Encumbrance Encumbrance Debit

Reversal Entry of
Freight Expense for
Refund

Gain/Loss
Refunds Gain Actual Credit
Refunds Invoice Price Actual Debit

Variance

Refunds Encumbrance Encumbrance Credit

Reversal Entry of
Invoice Price
Refunds Item Expense Actual Debit

Reversal Entry of
Item Expense for
Refund
Refunds Liability Actual Debit
Refunds Loss Actual Credit
Refunds Miscellaneous Actual Debit

Expense

Reversal Entry of
Miscellaneous
Expense for Refund
Refunds Non-Recoverable Tax Actual Debit

Accrual
Refunds Non-Recoverable Tax Actual Debit

Reversal Entry of
Non-Recoverable Tax
for Refunds

Reversal Entry of
Quantity Variance for
Refunds
Refunds Recoverable Tax Actual Debit


Amount Variance for
Refunds

Exchange Rate
Refunds Tax Exchange Rate Actual Debit

Variance
Refunds Tax Invoice Price Actual Debit

Variance

Invoice Price

Quantity Variance for
Refunds
Refunds Tax Rate Variance Actual Debit

Rate Variance for
Refunds
Account Derivation Rules

Oracle Payables predefines account derivation rules. When Oracle Subledger
Accounting uses the predefined account derivation rules that Oracle Payables provides,
it accepts the default accounting that Oracle Payables generates using AutoAccounting
without change.
You can optionally define your own account derivation rules for an Accounting
Flexfield or for a segment. In this case, Oracle Subledger Accounting overrides the
default accounts that Oracle Payables generates, or individual segment values in the

default accounts, when it creates the draft or final subledger accounting.
The name account derivation rules that Oracle Payables predefines for the Oracle
Payables application are as follows:
• Bank Account Bank Charges Account
• Bank Account Bank Charges Natural Account Segment
• Bank Errors Account
• Bank Account Bank Errors Natural Account Segment
• Cash Account
• Cash Natural Account Segment
• Discount Account
• Discount Balancing Segment
• Discount Natural Account Segment
• Exchange Rate Variance Gain/Loss Natural Account Segment
• Exchange Rate Variance Gain/Loss Natural Account Segment for cash basis
• Exchange Rate Variance Gain Natural Account Segment
• Exchange Rate Variance Loss Natural Account Segment
• Exchange Rate and Tax Exchange Rate Variances for Cash Basis
• Exchange Rate and Tax Exchange Rate Variances
• Future Dated Payment Account
• Future Dated Payment Natural Account Segment
• Interest Account
• Interest Natural Account Segment
• Invoice Distribution Account
• Invoice Distribution Natural Account Segment - Matched Item
• Invoice Distribution Natural Account Segment

• Invoice Distribution Balancing Segment
• Liability Account
• Liability Natural Account Segment
• Cash Clearing Account
• Cash Clearing Natural Account Segment
• Purchase Order Charge Account
• Prepay Invoice Distribution Account
• Realized Gain Account
• Realized Gain Natural Account Segment
• Realized Loss Account
• Realized Loss Natural Account Segment
• Recipient Invoice Distribution Account
• Related Distribution Expense Balancing Segment
• Retainage Account
• Retainage Natural Account Segment
• Retainage Related Distribution Balancing Segment
• Rounding Account
• Self-Assessed Tax Account
• Self-Assessed Tax Liability Account
• Recoverable Tax Account
• Tax Difference Account
• Tax Difference Natural Account Segment
• Withholding Distribution Account
• Withholding Related Distribution Balancing Segment

• Federal Unexpended Appropriation Account
• Federal Downward Anticipated PYA Account
• Federal Downward Unanticipated PYA Account
• Federal 465002 Payables
• Federal Allotment Realized Resources Account
• Federal 480101 Payables
• Federal Paid Obligation Reversal Debit Account
• Federal 48X101 Payables
• Federal Delivered Orders Obligation Account
• Federal Downward PYA Debit
• Federal Treasury Payment Obligation Unpaid Account
• Federal Treasury Payment Obligation Paid Account
• Federal Upward PYA USSGL Account CR
• Federal Expended Appropriation Account
• AP Invoice Distribution CCID
• Federal Downward PYA Paid USSGL Account
• Federal Downward PYA Unpaid USSGL Account
• Federal Invoice Payment Account
• Federal Invoices Balancing Segment
• Federal Quantity Variance Account Credit
• Federal Treasury Payment Confirm Cash Account
• Burdened Encumbrance Account Rule
• Burden Encumbrance Account Rule
• Project Prepayment Burdened Encumbrance Account Rule

• Project Prepayment Encumbrance Account Rule
• Project Prepayment Burden Encumbrance Account Rule
Journal Lines Definitions

Oracle Payables predefines journal lines definitions that group the predefined journal
line types and account derivation rules within each of the predefined event types.
Oracle Payables assigns each predefined journal lines definition to all event types
within an event class.
The following table lists the journal lines definitions that Oracle Payables predefines for
the Oracle Payables application.
Predefined Journal Lines Definitions for the Oracle Payables application
Event Class Journal Lines Definitions Journal Line Types

Name
Burden for Invoices Invoice Burden and Project Burden Invoice Encumbrance,
Encumbrance ALL Burdened Invoice
Encumbrance, Relieve Project
Encumbrance, Reserve Project
Encumbrance, Reverse PO
Burden Encumbrance,
Reverse PO Burdened
Encumbrance, Reverse
Release Burden Encumbrance,
Reverse Release Burdened
Encumbrance
Burden for Prepayment Prepayment Application Prepayment Application

Applications Burden and Project Burden Encumbrance,
Encumbrance ALL Prepayment Application
Burdened Encumbrance,
Encumbrance, Relieve Project
Encumbrance, Reserve Project
Encumbrance
Burden for Prepayments Prepayment Burden and Prepayment Burden

Project Encumbrance ALL Encumbrance, Prepayment
Burdened Encumbrance,
Prepayment Encumbrance,
Relieve Project Encumbrance,
Reserve Project Encumbrance

Name
Credit Memos Accrual, Credit Memos All Accrual, Exchange Rate

Variance, Freight Expense,
Invoice Price Variance, Item
Expense, Liability with
Automatic Offsets Account
Segment, Liability with
Automatic Offsets Balancing
Segment, Liability Basic,
Miscellaneous Expense,
Non-Primary Ledger
Exchange Rate Variance,
Non-Primary Ledger Tax
Non-Recoverable Tax,
Non-Recoverable Tax
Accrual, Recoverable Tax,
Retainage in Accrual Basis for
Credit Memos, Self-Assessed
Self-Assessed
Non-Recoverable Tax
Accrual, Self-Assessed
Recoverable Tax,
Self-Assessed Tax Liability,
Tax Exchange Rate Variance,
Tax Invoice Price Variance,
Tax Rate Variance,
Withholding Tax

Name
Credit Memos Encumbrance Credit Memos Encumbrance Amount

All Variance, Encumbrance
Encumbrance Freight
Expense, Encumbrance
Invoice Price Variance,
Encumbrance Item Expense,
Encumbrance
Encumbrance Quantity
Variance, Encumbrance
Recoverable Tax,
Encumbrance Self-Assessed
Encumbrance Tax Amount
Variance, Encumbrance Tax
Encumbrance Tax Invoice
Price Variance, Encumbrance
Tax Quantity Variance,
Encumbrance Tax Rate
Variance, CM PO
Encumbrance For
Non-Recoverable Tax, Credit
Memo PO Encumbrance

Name
Credit Memos Encumbrance Reversal for Encumbrance Reversal Entry

Credit Memo of Recoverable Tax,
Encumbrance Reversal Entry
of Amount Variance,
of Exchange Rate Variance
For Credit Memo,
of Freight Expense,
of Invoice Price Variance,
of Item Expense,
of Miscellaneous Expense for
Credit Memo, Encumbrance
Reversal Entry of
of Quantity Variance,
of Self-Assessed
of Tax Amount Variance,
of Tax Exchange Rate
Reversal Entry of Tax Invoice
Quantity Variance,
of Tax Rate Variance

Name
Credit Memos US Federal Credit Memos All Federal Credit Memo

Downward PYA Debit,
Federal Credit Memo
Downward Anticipated PYA
Credit, Federal Credit Memo
Downward Unanticipated
PYA Credit, Federal Credit
Memo Upward PYA Credit,
Federal Credit Memo Upward
PYA Debit, Federal Credit
Memos Expenditure Credit,
Federal Credit Memos
Expenditure Debit, Federal
Direct Fund Credit Memos
Credit, Federal Direct Fund
Credit Memos Debit, Federal
Direct Fund Reversal Credit
Memos Credit, Federal Direct
Fund Reversal Credit Memos
Debit

Name
Debit Memos Accrual, Debit Memos All Accrual, Exchange Rate

Segment, Liability, Basic,
Non-Primary Ledger
Non-Recoverable Tax
Retainage in Accrual Basis for
Debit Memos, Self-Assessed
Self-Assessed
Non-Recoverable Tax
Recoverable Tax,
Tax Rate Variance,
Withholding Tax

Name
Debit Memos Encumbrance Debit Memos Encumbrance Amount

All Variance, Encumbrance
Encumbrance Freight
Invoice Price Variance,
Encumbrance Item Expense,
Encumbrance Miscellaneous
Recoverable Tax,
Encumbrance Tax Amount
Variance, Encumbrance Tax
Variance, DM PO
Encumbrance For
Non-Recoverable Tax, Debit
Memo PO Encumbrance

Name
Debit Memos Encumbrance Reversal for Encumbrance Reversal Entry

Debit Memos of Exchange Rate Variance,
of Non-Recoverable Tax,
of Recoverable Tax,
of Amount Variance,
of Freight Expense,
of Item Expense,
of Miscellaneous Expense,
of Self-Assessed
Quantity Variance,

Name
Debit Memos US Federal Debit Memos All Federal Debit Memo

Downward PYA Debit,
Federal Debit Memo
Credit, Federal Debit Memo
PYA Credit, Federal Debit
Memo Upward PYA Credit,
Federal Debit Memo Upward
PYA Debit, Federal Debit
Memos Expenditure Credit,
Federal Debit Memos
Expenditure Debit, Federal
Direct Fund Debit Memos
Credit, Federal Direct Fund
Debit Memos Debit, Federal
Direct Fund Reversal Debit
Memos Credit, Federal Direct
Fund Reversal Debit Memos
Debit

Name
Future Dated Payments Accrual, Future Dated Cash Clearing, Non-Pooled

Payments All Bank Account, Cash Clearing,
Non-Pooled Bank Account
using Invoice Exchange Rate,
Cash Clearing, Pooled Bank
Account, Account Segment,
Invoice Exchange Rate, Cash
Clearing, Pooled Bank
Account, Balancing Segment,
Invoice Exchange Rate, Cash,
Non-Pooled Bank Account,
Cash, Pooled Account,
Account Segment, Cash,
Pooled Account, Balancing
Segment, Deferred
Recoverable Tax at Payment
Maturity, Future Dated
Payment, Future Payment
Rounding, Gain, Interim Tax
Line Reversal at Payment
Maturity, Loss, Non-Primary
Ledger Gain/Loss
Future Dated Payments Cash, Future Dated Payments Cash Clearing, Non-Pooled
All Bank Account, Cash Clearing,
Account Segment, Cash
Clearing, Pooled Bank
Cash, Non-Pooled Bank
Account, Cash, Pooled
Cash, Pooled Account,
Balancing Segment, Future
Dated Payment, Future
Payment Rounding, Gain,
Loss, Non-Primary Ledger
Gain/Loss

Name
Invoices Accrual, Invoices All Accrual, Exchange Rate

Segment, Liability, Basic,
Non-Primary Ledger
Non-Recoverable Tax
Retainage Release, Accrual
Basis, Retainage in Accrual
Basis, Self-Assessed
Self-Assessed
Non-Recoverable Tax
Recoverable Tax,
Tax Rate Variance,
Withholding Tax

Name
Invoices Encumbrance for Invoices Encumbrance Amount

Encumbrance Freight
Expense, Invoice Prepay
Encumbrance DR,
Encumbrance Invoice Price
Variance, Encumbrance Item
Encumbrance
Recoverable Tax,
Encumbrance Tax Exchange
Rate Variance, Encumbrance
Tax Amount Variance,
Variance, Invoice PO
Encumbrance, Invoice PO
Encumbrance For
Non-Recoverable Tax

Name
Invoices Encumbrance Reversal for Encumbrance Reversal Entry

Invoices of Non-Recoverable Tax,
of Self-Assessed
of Amount Variance,
of Exchange Rate Variance,
of Freight Expense,
of Item Expense,
of Miscellaneous Expense,
of Recoverable Tax,
Quantity Variance,

Name
Invoices US Federal Invoices All Federal Direct Expenditure

Invoice Credit, Federal Direct
Expenditure Invoice Debit,
Federal Direct Fund Invoice
Debit, Federal Direct Fund
Reverse Invoice Credit,
Federal Direct Fund Reverse
Invoice Debit, Federal Invoice
Amount Variance Credit,
Federal Invoice Amount
Variance Debit, Federal
Invoice Downward PYA
Debit, Federal Invoice
Credit, Federal Invoice
PYA Credit, Federal Invoice
Price Variance Credit, Federal
Invoice Price Variance Debit,
Federal Invoice Quantity
Variance Credit, Federal
Invoice Quantity Variance
Debit, Federal Invoice
Upward PYA Credit, Federal
Invoice Upward PYA Debit,
Federal Paid Obligation
Expired Reversal Credit,
Federal Paid Obligation PYA
Reversal Debit, Federal Paid
Obligation Reversal Credit,
Federal Paid Obligation
Reversal Debit
Application Accounting Definitions

Oracle Payables predefines the Accrual Basis, Encumbrance Accrual, Encumbrance Cash,
and the Cash Basis application accounting definitions.
The following table lists the assignments for the Accrual Basis application accounting
definition that Oracle Payables predefines for the Oracle Payables application.

Assignments for the Predefined Accrual Basis Application Accounting Definition
Event Class Event Type Create Accounting Journal Line

Assignments Assignments Definition
Assignments
Credit Memos All Yes Accrual, Credit

Memos All
Debit Memos All Yes Accrual, Debit

Memos All
Future Dated All Yes Accrual, Future

Payments Dated Payments All
Invoices All Yes Accrual, Invoices All
Payments All Yes Accrual, Payments

All
Prepayment All Yes Accrual, Prepayment

Applications Applications All
Prepayments All Yes Accrual, Prepayments

All
Reconciled Payments All Yes Accrual, Reconciled

Payments All
Refunds All Yes Accrual, Refunds All
The following table lists the assignments for the Encumbrance Basis application
accounting definition that Oracle Payables predefines for the Oracle Payables
application.

Assignments for the Predefined Encumbrance Accrual Application Accounting Definition

Assignments
Burden for Invoices All Yes Invoice Burden and

Project Encumbrance
ALL
Burden for All Yes Prepayment

Applications and Project
Encumbrance ALL
Burden for All Yes Prepayment Burden

Prepayments and Project
Encumbrance ALL
Credit Memos All Yes Accrual, Credit

Memos All;
Encumbrance Credit
Memos All;
Encumbrance
Reversal for Credit
Memo
Debit Memos All Yes Accrual, Debit

Memos All;
Encumbrance Debit
Memos All;
Encumbrance
Reversal for Debit
Memos
Future Dated All Yes Accrual, Future

Payments Dated Payments All
Invoices All Yes Accrual, Invoices All;

Encumbrance for
Invoices;
Encumbrance
Reversal for Invoices
Payments All Yes Accrual, Payments

All

Assignments
Prepayment All Yes Accrual, Prepayment

Applications Applications All;
Encumbrance
Reversal for
Prepayment
Applications;
Encumbrance
Prepayment
Applications
Prepayments All Yes Accrual, Prepayments

All; Encumbrance for
Prepayments All;
Encumbrance
Reversal for
Prepayments
Reconciled Payments All Yes Accrual, Reconciled

Payments All
Refunds All Yes Accrual, Refunds All
The following table lists the assignments for the Encumbrance Cash application
accounting definition that Oracle Payables predefines for the Oracle Payables
application.
Assignments for the Predefined Encumbrance Cash Application Accounting Definition

Assignments
Burden for Invoices All Yes Invoice Burden and

Project Encumbrance
ALL
Burden for All Yes Prepayment

Applications and Project
Encumbrance ALL

Assignments
Burden for All Yes Prepayment Burden

Prepayments and Project
Encumbrance ALL
Credit Memos All Yes Encumbrance Credit

Memos All
Debit Memos All Yes Encumbrance Debit

Memos All
Future Dated All Yes Cash, Future Dated

Payments Payments All
Invoices All Yes Encumbrance for

Invoices
Payments All Yes Cash, Payments All;

Encumbrance
Reversal for
Payments
Prepayment All Yes Encumbrance

Applications Reversal for
Prepayment
Applications; Cash,
Prepayment
Applications All;
Encumbrance
Prepayment
Applications
Prepayments All Yes Encumbrance for

Prepayments All
Reconciled Payments All Yes Cash, Reconciled

Payments All;
Encumbrance
Reversal for
Reconciled Payments

Assignments
Refunds All Yes Cash, Refunds All;

Encumbrance
Reversal for Refunds
The following table lists the assignments for the Cash Basis application accounting
definition that Oracle Payables predefines for the Oracle Payables application.
Assignments for the Predefined Cash BasisApplication Accounting Definition

Assignments
Credit Memos All No
Debit Memos All No
Future Dated All Yes Cash, Future Dated

Payments Payments All
Invoices All No
Payments All Yes Cash, Payments All
Prepayment All Yes Cash, Prepayment

Applications Applications All
Prepayments All No
Reconciled Payments All Yes Cash, Reconciled

Payments All
Refunds All Yes Cash, Refunds All
Subledger Accounting Methods

Oracle Subledger Accounting provides predefined subledger accounting methods that
group the predefined application accounting definitions for subledger applications. You
can optionally create your own subledger accounting methods.

Oracle Payables assigns the predefined application accounting definitions to the
predefined subledger accounting methods as shown in the following table:
Application Accounting Definitions Assigned to Subledger Accounting Methods
Application Accounting Definitions Subledger Accounting Methods
Encumbrance Accrual Accrual with Encumbrance Accounting
Encumbrance Cash Cash with Encumbrance Accounting
Accrual Basis Standard Accrual
Cash Basis Standard Cash
You can assign these subledger accounting methods to your ledger.

Index
A I
account derivation rules, C-49 interface tables
accounting AP_EXPENSE_FEED_LINES_ALL
account derivation rules, C-49 column descriptions, 1-1
accounting event class options, C-4 AP_INVOICE_DISTRIBUTIONS, B-3
application accounting definitions, C-66 AP_INVOICE_LINES_INTERFACE, A-30
applications, C-2 AP_INVOICES, B-3
event classes and types, C-3 AP_INVOICES_INTERFACE, A-5
event entities, C-2 Payables Open Interface
journal lines definitions, C-53 overview, A-1
journal line types, C-6 PO_DISTRIBUTIONS, B-10
process categories, C-4 PO_HEADERS_ALL, B-3
sources and assignments, C-6 PO_LINE_LOCATIONS_ALL, B-7
subledger accounting methods, C-71 PO_LINES_ALL, B-6
accounting event class options, C-4 PO_RELEASES_ALL, B-5
account overlay feature in Payables Open purchase order matching tables, B-1
Interface Import, A-143 invoices
accounts importing from other systems, A-1
account overlay in Payables Open Interface
Import, A-143 J
application accounting definitions, C-66
journal lines definitions, C-53
applications, C-2
journal line types, C-6
E O
EDI inbound invoices
Oracle Subledger Accounting
Payables Open Interface tables, A-1
account derivation rules, C-49
encumbrance
accounting event class options, C-4
purchase orders, B-16
application accounting definitions, C-66
event classes and types, C-3
applications, C-2
event entities, C-2
event classes and types, C-3
event entities, C-2
Index-1
journal lines definitions, C-53
journal line types, C-6 R
process categories, C-4
requester, A-30
sources and assignments, C-6
subledger accounting methods, C-71
S
P sequential numbering
payables open interface import, A-143
Payables Open Interface Import
sources and assignments, C-6
account overlay feature, A-143
Subledger Accounting
table descriptions, A-1
predefined setup, C-1
Payables Open Interface tables
subledger accounting methods, C-71
AP_INVOICE_LINES_INTERFACE table, A-
30
AP_INVOICES_INTERFACE table, A-5
how the Quick Invoices populates, A-145
overview, A-1
payment terms
calendar-based, A-17
PO_HEADERS_ALL table, B-3
PO_LINES_ALL table, B-6
process categories, C-4
purchase order matching
interface tables
purchase order matching, B-1
matching holds, B-16
purchase orders
AP_INVOICE_DISTRIBUTIONS table, B-3
AP_INVOICES table, B-3
encumbrance accounting, B-16
interface tables, B-1
matching, B-13
PO_DISTRIBUTIONS table, B-10
PO_HEADERS_ALL table, B-3
PO_LINE_LOCATIONS_ALL, B-7
PO_LINES_ALL table, B-6
PO_RELEASES_ALL table, B-5
purging information, B-17
table descriptions, B-3
understanding matching tables, B-2
using Invoice Validation, B-15
Q
Quick Invoices window
how values populate the Payables Open
Interface, A-145
Index-2

122 Aprg

Uploaded by

Copyright:

Available Formats

122 Aprg

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

122 Aprg

Uploaded by

Copyright:

Available Formats

Oracle® Payables

Part No. E48763-03

Primary Author: Sudha Seshadri

Send Us Your Comments

1 Expense Reports and Credit Cards

A Payables Open Interface Tables

B Purchase Order Matching Database Tables

Oracle Payables Reference Guide, Release 12.2

• Computer desktop application usage and terminology.

Access to Oracle Support

Related Information Sources

• Oracle Electronic Technical Reference Manual - The Oracle Electronic Technical

Oracle Diagnostics Framework User's Guide

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Payables Procurement Card Transactions Interface Table

Payables Procurement Card Transactions Interface Table Column Descriptions

Column Name Null Type Comments

EMPLOYEE_ID NUMBER(15) Required Foreign key:

CARD_ID NUMBER(15) Foreign key

CARD_PROGRAM_I NOT NULL NUMBER(15) Required; Foreign key

CARD_NUMBER NOT NULL VARCHAR2(80) Required

FEED_LINE_ID NOT NULL NUMBER(15) Required; Primary

REFERENCE_NUMB VARCHAR2(240) Unique

Expense Reports and Credit Cards 1-1

AMOUNT NOT NULL NUMBER Required (must load

POSTED_DATE NOT NULL DATE

CODE_ID NUMBER(15) Foreign key

1-2 Oracle Payables Reference Guide

Expense Reports and Credit Cards 1-3

1-4 Oracle Payables Reference Guide

LAST_UPDATE_DA NOT NULL DATE

LAST_UPDATED_BY NOT NULL NUMBER(15)

ATTRIBUTE VARCHAR2(150) Optional

ATTRIBUTE 1 - 30 VARCHAR2(150) Optional

Expense Reports and Credit Cards 1-5

Payables Open Interface Tables

• Understanding the Suppliers Open Interface Tables, page A-3

• Table Descriptions, page A-5

• Account Overlay in Payables Open Interface Import, page A-143

• Sequential Numbering During Import, page A-143

Payables Open Interface Tables A-1

Understanding the Invoice Open Interface Tables

NOT NULL Columns

A-2 Oracle Payables Reference Guide

Understanding the Suppliers Open Interface Tables

Payables Open Interface Tables A-3

Changes to Supplier Sites Open Interface Import

During import if no value is found both in AP_SUPPLIER_SITES_INT and Payables

A-4 Oracle Payables Reference Guide

Payables Open Interface Table Descriptions

Payables Open Interface Tables A-5

INVOICE_ID NOT NULL NUMBER(15) Required, Primary

INVOICE_NUM VARCHAR2(50) Required if there is

INVOICE_TYPE_ VARCHAR2(25) Optional

INVOICE_DATE DATE Optional

PO_NUMBER VARCHAR2(20) Validated against:

VENDOR_ID NUMBER(15) Internal ID Validated

VENDOR_NUM VARCHAR2(30) One of the following

A-6 Oracle Payables Reference Guide