AP Technical Reference Mannual

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CAUTION!This document contains proprietary,

confidential information that is the exclusiveproperty of Oracle Corporation.

See back cover forimportant information.

Oracle PayablesApplications TechnicalReference Manual RELEASE 11i

January 2000

Oracle Payables Applications Technical Reference ManualRelease 11i

To order this book, ask for Part No. A8083301

Copyright 1994, 2000. Oracle Corporation. All rights reserved.

Major Contributors: Subir Hira, Noela Nakos, Christina Ravaglia, Lauren Scott, Manish Srivastava, Julie Thai

Contributors: Christopher Andrews, Martin Taylor

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle Corporation; it isprovided under an Oracle Corporation agreement containing restrictions on use and disclosure and is also protected by copyright, patent, andother intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care tosafeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information ora reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the ConfidentialInformation of third parties such as Oracle Corporation and instructing such employees and agents of these requirements for this TRM; (c)restricting disclosure of this TRM to those of your employees who have a need to know consistent with the purposes for which this TRM wasdisclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legendsor markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form orby any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. You should not use thisTRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle Corporation products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter,please report them to us in writing. Oracle Corporation does not warrant that this TRM is errorfree. This TRM is provided to customer asiswith no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracles agreements.

Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with thisTRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licenseesresponsibility to take all appropriate failsafe, backup, redundancy and other measures to ensure the safe use of such applications if thePrograms are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.

Restricted Rights LegendThis TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are commercial computer software anduse, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in theapplicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the FederalAcquisition Regulations are restricted computer software and use, duplication and disclosure of the TRM and the Programs associated with thisTRM shall be subject to the restrictions in FAR 52.22714, Rights in Data General, including Alternate III (June 1987). Oracle Corporation, 500Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark, and CASE*Exchange, Enabling the Information Age, Hyper*SQL, NLS*Workbench, Oracle7, Oracle8, Oracle 8i,Oracle Access, Oracle Application Object Library, Oracle Discoverer, Oracle Financials, Oracle Quality, Oracle Web Customers, Oracle WebEmployees, Oracle Work in Process, Oracle Workflow, PL/SQL, Pro*Ada, Pro*C, Pro*COBOL, Pro*FORTRAN, Pro*Pascal, Pro*PL/I, SmartClient,SQL*Connect, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, and SQL*Report are trademarks or registered trademarks of OracleCorporation. Other names may be trademarks of their respective owners.

TCAUTION

his Technical Reference Manual in any form software orprinted matter contains proprietary, confidential information

that is the exclusive property of Oracle Corporation. If you do nothave a valid contract with Oracle for the use of this Technical ReferenceManual or have not signed a nondisclosure agreement with Oraclecovering this Technical Reference Manual, then you received thisdocument in an unauthorized manner and are not legally entitled topossess or read it.

Use, duplication, and disclosure are subject to restrictions stated inyour contract with Oracle Corporation.

iContents

Oracle Proprietary, Confidential InformationUse Restricted by Contract

Contents

Chapter 1 Introduction 1 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 HighLevel Design 2 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of HighLevel Design 2 2. . . . . . . . . . . . . . . . . . . . . . . . . . . Database Diagrams 2 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Public Table List 2 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web View List 2 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms and Table View List 2 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal View List 2 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single Organization View List 2 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Reporting Currencies View List 2 40. . . . . . . . . . . . . . . . . . . . Module List 2 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 Detailed Design 3 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Detailed Design 3 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table and View Definitions 3 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index

ii Oracle Payables Applications Technical Reference Manual


Readers Comment Form

Oracle Payables Applications Technical Reference ManualA8083301

Oracle Corporation welcomes your comments and suggestions on the quality and usefulnessof this publication. Your input is an important part of the information we use for revision.

Did you find any errors?

Is the information clearly presented?

Do you need more information? If so, where?

Are the examples correct? Do you need more examples?

What features did you like most about this manual? What did you like least about it?If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,and page number below:

Please send your comments to:Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, CA 94065 USAPhone: (650) 5067000 Fax: (650) 5067200

If you would like a reply, please give your name, address, and telephone number below:

Thank you for helping us improve our documentation.

C H A P T E R

1T

1 1Introduction


Introduction

he Oracle Payables Applications Technical Reference Manual providesthe information you need to understand the underlying structure

of Oracle Payables and Oracle Public Sector Payables. After readingthis manual, you should be able to convert your existing applicationsdata, integrate your existing applications with your Oracle Payablesapplication, and write custom reports for your Oracle Payablesapplication, as well as read data that you need to perform other tasks.

This chapter introduces you to the Oracle Payables Applications TechnicalReference Manual, and explains how to use it.

1 2 Oracle Payables Applications Technical Reference Manual


Introduction

At Oracle, we design and build applications using Oracle Designer, oursystems design technology that provides a complete environment tosupport developers through all stages of a systems life cycle. Becausewe use a repositorybased design toolset, all the information regardingthe underlying structure and processing of our applications is availableto us online. Using Oracle Designer, we can present this information toyou in the form of a technical reference manual.

This Oracle Payables Applications Technical Reference Manual containsdetailed, uptodate information about the underlying structure ofOracle Payables and Oracle Public Sector Payables. As we design andbuild new releases of Oracle Payables applications, we update ourOracle Designer repository to reflect our enhancements. As a result,we can always provide you with an Oracle Payables ApplicationsTechnical Reference Manual that contains the latest technical informationas of the publication date. Note that after the publication date we mayhave added new indexes to Oracle Payables and Oracle Public SectorPayables to improve performance.

About this Manual

This manual describes the Oracle Applications Release 11i data model,as used by Payables; it discusses the database we include with a freshinstall of Oracle Applications Release 11i. If you have not yet upgradedto Release 11i, your database may differ from the database wedocument in this book.

If you have upgraded from a previous release, you might find it helpfulto use this manual with the appropriate Oracle Applications ProductUpdate Notes manual. The product update notes list database changesand seed data changes in Oracle Payables and Oracle Public SectorPayables between releases. The Oracle Applications Product Update NotesRelease 11 manual describes the changes between Release 10.7 andRelease 11, and the Oracle Applications Product Update Notes Release 11imanual describes the changes between Release 11 and Release 11i.

You can contact your Oracle representative to confirm that you havethe latest technical information for Payables. You can also useOracleMetaLink which is accessible through Oracles Support WebCenter (http://www.oracle.com/support/elec_sup).

1 3Introduction


Finding the Latest Information

The Oracle Payables Applications Technical Reference Manual contains thelatest information as of the publication date. For the latest informationwe encourage you to use OracleMetaLink which is accessible throughOracles Support Web Center (http://www.oracle.com/support/elec_sup).

Audience

The Oracle Payables Applications Technical Reference Manual providesuseful guidance and assistance to:

Technical End Users

Consultants

Systems Analysts

System Administrators

Other MIS professionals

This manual assumes that you have a basic understanding ofstructured analysis and design, and of relational databases. It alsoassumes that you are familiar with Oracle Application Object Libraryand your Oracle Payables application. If you are not familiar with theabove products, we suggest that you attend one or more of the trainingclasses available through Oracle Education (see: Other InformationSources: page 1 8).

Public Sector and Other Industryspecific Products

For certain products, including Payables, Oracle provides severaldistinct software versions tailored for a specific industry or vertical,containing additional functionality not present in the base ornonverticalspecific product.

The data model for Payables supports a superset of all the functionalityused by a verticalspecific version of Payables, including the OraclePublic Sector Financials version of Payables. Therefore, you can usethis manual in conjunction with Oracle Public Sector General Ledger,Oracle Public Sector Payables, Oracle Public Sector Purchasing, orOracle Public Sector Receivables.



How This Manual is Organized

This manual contains two major sections, HighLevel Design andDetailed Design.

HighLevel Design

This section, Chapter 2, contains database diagrams and lists eachdatabase table and view that Payables uses. This chapter also has a listof modules.

Detailed Design

This section, Chapter 3, contains a detailed description of the Payablesdatabase design, including information about each database table andview you might need for your custom reporting or other datarequirements.

1 5Introduction


How to Use This Manual

The Oracle Payables Applications Technical Reference Manual is a single,centralized source for all the information you need to know about theunderlying structure and processing of your Oracle Payablesapplication. For example, you can use this manual when you need to:

Convert existing application data

Integrate your Payables application with your other applicationssystems

Write custom reports

Define alerts against Oracle Applications tables

Configure your Oracle SelfService Web Applications

Create views for decision support queries using query tools

Create business views for Oracle Discoverer

You need not read this manual cover to cover. Use the table of contentsand index to quickly locate the information you need.

Here is an example of how you might use the Oracle PayablesApplications Technical Reference Manual:

Example

Suppose you are writing a custom application to update the bankaccount information in your Oracle Payables application. Your firststep is to locate a table in the Table List section of Chapter 2 that yourOracle Payables application uses to store bank information. Keep inmind that tables in Oracle Payables applications have intuitive names.You see that there is a table named AP_BANK_ACCOUNTS_ALLwhich contains detailed information about the bank accounts youdefine.

You then refer to the Table and View Definitions section in Chapter 3for a detailed description of the table and its columns. You canexamine the column descriptions and column types to ensure that yourcustom application references the correct columns. Then you can lookat the foreign keys list to identify tables related toAP_BANK_ACCOUNTS_ALL. You can examine the descriptions ofthe related tables to ensure that your custom application referencesthose tables holding information required for bank accounts.



How Not To Use This Manual

Do not use this manual to plan modifications

You should not use this manual to plan modifications to your OraclePayables application. Modifying Oracle Payables and Oracle PublicSector Payables limits your ability to upgrade to future releases of yourPayables application. In addition, it interferes with our ability to giveyou the highquality support you deserve.

We have constructed your Oracle Payables application so that you cancustomize it to fit your needs without programming, and you canintegrate it with your existing applications through interface tables.However, should you require program modifications, you shouldcontact our support team (see: Other Information Sources: page 1 8).They can put you in touch with Oracle Services, the professionalconsulting organization of Oracle. Their team of experiencedapplications professionals can make the modifications you need whileensuring upward compatibility with future product releases.

Do not write data into noninterface tables

Oracle reserves the right to change the structure of Oracle Applicationstables, and to change the meaning of, add, or delete lookup codes anddata in future releases. Do not write data directly into or change datain noninterface tables using SQL*Plus or other programming toolsbecause you risk corrupting your database and interfering with ourability to support you.

Moreover, this version of the Oracle Payables Applications TechnicalReference Manual does not contain complete information about thedependencies between Payables applications tables. Therefore, youshould write data into only those tables we identify as interface tables.If you write data into other noninterface tables, you risk violatingyour data integrity since you might not fulfill all the data dependenciesin your Payables application.

You are responsible for the support and upgrade of the logic within theprocedures that you write, which may be affected by changes betweenreleases of Oracle Applications.

Do not rely on upward compatibility of the data model

Oracle reserves the right to change the structure of Oracle Payablesapplications tables, and to change the meaning of, add, or deletelookup codes and other data in future releases. We do not guarantee

+1 7Introduction


the upward compatibility of the Oracle Payables applications datamodel. For example, if you write a report that identifies concurrentrequests that end in Error status by selecting directly from OracleApplication Object Library tables, we do not guarantee that your reportwill work properly after an upgrade.

About Oracle Application Object Library

The Oracle Payables Applications Technical Reference Manual may containreferences to tables that belong to Oracle Application Object Library.Oracle Application Object Library is a collection of prebuiltapplication components and facilities for building Oracle Applicationsand extensions to Oracle Applications. Oracle Application CodingStandards use the Oracle Application Object Library and containsshared components including but not limited to forms, subroutines,concurrent programs and reports, database tables and objects,messages, menus, responsibilities, flexfield definitions and online help.

Attention: Oracle does not support any customization ofOracle Application Object Library tables or modules, not evenby Oracle consultants. (Oracle Application Object Librarytables generally have names beginning with FND_%.)

Accordingly, this manual does not contain detailed informationabout most Oracle Application Object Library tables used byyour Oracle Payables application.

A Few Words About Terminology

The following list provides you with definitions for terms that we usethroughout this manual:

Relationship

A relationship describes any significant way in which two tables maybe associated. For example, rows in the Journal Headers table mayhave a onetomany relationship with rows in the Journal Lines table.

Database Diagram

A database diagram is a graphic representation of application tablesand the relationships between them.



Module

A module is a program or procedure that implements one or morebusiness functions, or parts of a business function, within anapplication. Modules include forms, concurrent programs and reports,and subroutines.

Application Building Block

An application building block is a set of tables and modules (forms,reports, and concurrent programs) that implement closelyrelateddatabase objects and their associated processing. Said another way, anapplication building block is a logical unit of an application.

QuickCodes

QuickCodes let you define general purpose, static lists of values forwindow fields. QuickCodes allow you to base your program logic onlookup codes while displaying userfriendly names in a list of valueswindow. QuickCodes simplify name and language changes by lettingyou change the names your end users see, while the codes in yourunderlying programs remain the same.

Form

A form is a module comprised of closely related windows that are usedtogether to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window among others. The EnterJournals window is the main window, and from it, you can use buttonsto navigate to other windows in the form. The form name usuallycorresponds to the main window in the form, and is frequently awindow you open directly from the Navigator.

Other Information Sources

There are additional information sources, including otherdocumentation, training and support services, that you can use toincrease your knowledge and understanding of Oracle Designer, OracleApplication Object Library, and your Oracle Payables application. Wewant to make these products easy for you and your staff to understandand use.

1 9Introduction


Oracle Designer Online Documentation

The online help for Oracle Designer describes how you can use OracleDesigner for your development needs.

Oracle Applications Developers Guide

This guide contains the coding standards followed by the OracleApplications development staff. It describes the Oracle ApplicationObject Library components needed to implement the OracleApplications user interface described in the Oracle Applications UserInterface Standards. It also provides information to help you build yourcustom Developer forms so that they integrate with OracleApplications.

Oracle Applications User Interface Standards

This manual contains the user interface (UI) standards followed by theOracle Applications development staff. It describes the UI for theOracle Applications products and how to apply this UI to the design ofan application built using Oracle Forms 6.

Oracle Payables User GuideOracle Public Sector Payables User Guide

Your user guide provides you with all the information you need to useyour Release 11i Payables application. Each user guide is organized forfast, easy access to detailed information in a function andtaskoriented organization.

Oracle Global Financial Applications Technical Reference Manual

This manual describes additional tables and views that have beenadded to support features that meet statutory requirements andcommon business practices in your country or region. The Appendixof this manual also describes how the GLOBAL_ATTRIBUTE columnsof your base product tables are used in your country or region.

CountrySpecific Manuals

Use these manuals to meet statutory requirements and commonbusiness practices in your country or region. They also describeadditional features added to Payables to meet those requirements.Look for a user guide appropriate to your country; for example, see the



Oracle Financials for the Czech Republic User Guide for more informationabout using this software in the Czech Republic.

Oracle SelfService Web Applications Online Documentation

This documentation describes how Oracle SelfService WebApplications enable companies to provide a selfservice and secureWeb interface for employees, customers, and suppliers. Employees canchange their personal status, submit expense reports, or requestsupplies. Customers can check on their orders, and suppliers can shareproduction schedules with their trading partners. This documentationis available in HTML only.

Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and referenceinformation for the Payables implementation team, as well as for usersresponsible for the ongoing maintenance of Oracle Applicationsproduct data. This manual also provides information on creatingcustom reports on flexfields data.

Oracle Workflow Guide

This manual explains how to define new workflow business processesas well as customize existing Oracle Applicationsembedded workflowprocesses. You also use this guide to complete the setup stepsnecessary for any Oracle Applications product that includesworkflowenabled processes.

Oracle Alert User Guide

This manual explains how to define periodic and event alerts tomonitor the status of your Oracle Applications data.

Multiple Reporting Currencies in Oracle Applications

If you use the Multiple Reporting Currencies feature to report andmaintain accounting records in more than one currency, use thismanual before implementing Payables. This manual details additionalsteps and setup considerations for implementing Payables with thisfeature.

1 11Introduction


Multiple Organizations in Oracle Applications

If you use the Oracle Applications Multiple Organization Supportfeature to use multiple sets of books for one Payables installation, usethis guide to learn about setting up and using Payables with thisfeature. This book describes the Oracle Applications organizationmodel, which defines business units and the relationships betweenthem in an arbitrarily complex enterprise. Functional and technicaloverviews of multiple organizations are presented, as well asinformation about how to set up and implement this feature set in therelevant Oracle Applications products.

Oracle Financials Open Interfaces Guide

This book contains a brief summary of all open interface discussions inall Oracle Financial Applications user guides. You can also read aboutthe Payables open interface tables in the appendix of the Oracle PayablesUser Guide.

Oracle Manufacturing, Distribution, Sales and Service OpenInterfaces Manual

This manual contains uptodate information about integrating withother Oracle Manufacturing applications and with your other systems.This documentation includes open interfaces found in OracleManufacturing.

Oracle Applications Messages Manual

The Oracle Applications Messages Manual contains the text ofnumbered error messages in Oracle Applications. (Oracle Applicationsmessages begin with the prefix APP.) It also provides informationon the actions you take if you get a message. Note: This manual isavailable only in HTML format.

Oracle Public Sector Financials Messages Manual

This manual contains the text of numbered error messages in OraclePublic Sector Financials and related Oracle Applications products.(Oracle Applications messages begin with the prefix APP.) It alsoprovides information on the actions you take if you get a message.Note: This manual is available only in HTML format.



Installation and System Administration

Oracle Applications Installation Release Notes

This manual contains a road map to the components of the release,including instructions about where to access the Release 11idocumentation set.

Oracle Applications Concepts

Designed to be the first book the user reads to prepare for aninstallation of Oracle Applications. It explains the technology stack,architecture, features and terminology for Oracle Applications Release11i. This book also introduces the concepts behind and major uses ofApplicationswide features such as MRC, BIS, languages and charactersets (NLS, MLS), BIS, SelfService Web Applications and so on.

Installing Oracle Applications

Describes the OneHour Install process, the method by which Release11i will be installed. This manual includes all howto steps, screenshots and information about Applicationswide postinstall tasks.

Using the AD Utilities

This manual contains howto steps, screen shots and other informationrequired to run the various AD utilities such as AutoInstall, AutoPatch,AD Administration, AD Controller, Relink and so on. It also containsinformation about when and why you should use these utilities.

Upgrading Oracle Applications

This manual contains all the product specific pre and postupgradesteps that are required to upgrade products from Release 10.7 (NCA,SC and charactermode) or Release 11 of Oracle Applications. Thismanual also contains an overview chapter that describes all the tasksnecessary to prepare and complete a upgrade of Oracle Applications.

Oracle Applications System Administrators Guide

This manual provides planning and reference information for theOracle Applications System Administrator. It contains information onhow to define security, customize menus and manage concurrentprocessing.

1 13Introduction


Oracle Applications Product Update Notes

This book contains a summary of each new feature we added sinceRelease 11, as well as information about database changes and seeddata changes that may affect your operations or any custom reportsyou have written. If you are upgrading from Release 10.7 you alsoneed to read Oracle Applications Product Update Notes Release 11.

Oracle SelfService Web Applications Implementation Manual

This manual describes the setup steps for Oracle SelfService WebApplications and the Web Applications Dictionary.

Oracle Applications Implementation Wizard User Guide

If you are implementing more than one Oracle product, you can use theOracle Applications Implementation Wizard to coordinate your setupactivities. This guide describes how to use the wizard.

Other Information

Training

Oracle Education offers a complete set of training courses to help youand your staff master Oracle Applications. We can help you develop atraining plan that provides thorough training for both your projectteam and your end users. We will work with you to organize coursesappropriate to your job or area of responsibility.

Training professionals can show you how to plan your trainingthroughout the implementation process so that the right amount ofinformation is delivered to key people when they need it the most. Youcan attend courses at any one of our many Educational Centers, or youcan arrange for our trainers to teach at your facility. In addition, wecan tailor standard courses or develop custom courses to meet yourneeds.

Support

From onsite support to central support, our team of experiencedprofessionals provides the help and information you need to keep yourOracle Payables application working for you. This team includes yourTechnical Representative, Account Manager, and Oracles large staff ofconsultants and support specialists with expertise in your business



area, managing an Oracle server, and your hardware and softwareenvironment.

1 15Introduction


About Oracle

Oracle Corporation develops and markets an integrated line ofsoftware products for database management, applicationsdevelopment, decision support, and office automation, as well asOracle Applications, an integrated suite of more than 75 softwaremodules for financial management, supply chain management,manufacturing, project systems, human resources, and sales andservice management.

Oracle products are available for mainframes, minicomputers, personalcomputers, network computers, and personal digital assistants,allowing organizations to integrate different computers, differentoperating systems, different networks, and even different databasemanagement systems, into a single, unified computing and informationresource.

Oracle is the worlds leading supplier of software for informationmanagement, and the worlds second largest software company.Oracle offers its database, tools, and applications products, along withrelated consulting, education, and support services, in over 145countries around the world.

Thank You

Thanks for using Oracle Payables applications and this technicalreference manual!

We appreciate your comments and feedback. At the back of thismanual is a Readers Comment Form that you can use to explain whatyou like or dislike about your Oracle Payables application or thistechnical reference manual. Mail your comments to the followingaddress or call us directly at (650) 5067000.

Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, California 94065 U.S.A.

Or, send electronic mail to [email protected].

C H A P T E R

2T

2 1HighLevel Design


HighLevel Design

his chapter presents a highlevel design for Oracle Payables andOracle Public Sector Payables that satisfies the business needs we

specify during Strategy and Analysis. It contains database diagramsfor Oracle Payables and Oracle Public Sector Payables applicationbuilding blocks, lists of database tables and views, and a list ofmodules.



Overview of HighLevel Design

During HighLevel Design, we define the application components(tables, views, and modules) we need to build our application. Wespecify what application components should do without specifying thedetails of how they should do it.

You can refer to this HighLevel Design chapter to quickly acquaintyourself with the tables, views, and modules that comprise Payablesapplications. And, you can prepare yourself to understand the detaileddesign and implementation of Oracle Payables and Oracle Public SectorPayables.

Database Diagrams

The Database Diagrams section graphically represents all Payablesapplications tables and the relationships between them, organized bybuilding block.

Use this section to quickly learn what tables each Payables applicationbuilding block uses, and how those tables interrelate. Then, you canrefer to the Table and View Definitions sections of Chapter 3 for moredetailed information about each of those tables.

Table Lists

The Table List sections list the Payables applications tables. Because aproduct might not include at least one table for each type, thisTechnical Reference Manual might not include each of the followingsections.

Public Tables

Use the Public Table List section to quickly identify the tables you aremost interested in. Then, you can refer to the Table and ViewDefinitions sections of Chapter 3 for more detailed information aboutthose tables.

In addition, this manual may contain full documentation for one ormore of the following Application Object Library tables: FND_DUAL,FND_CURRENCIES, and FND_COMMON_LOOKUPS.

2 3HighLevel Design


Internal Tables

This section includes a list of private, internal tables used by Payables;we do not provide additional documentation for these tables.

View Lists

The View List sections list the Payables views, with one section for eachtype of view. Because a product might not include at least one view foreach type, this Technical Reference Manual might not include each ofthe following sections.

Use this section to quickly identify the views you are most interestedin. Then, you can refer to the Table and View Definitions sections ofChapter 3 for more detailed information about those views.

Public Views

This section lists views that may be useful for your custom reporting orother data requirements. The list includes a description of the view,and the page in Chapter 3 that gives detailed information about thepublic view.

Web Views

This section lists views that you may need to configure yourSelfService Web applications. The list includes a description of theview, and the page in Chapter 3 that gives detailed information aboutthe web view.

Forms and Table Views

This section lists supplementary views that are not essential to theRelease 11i data model, but simplify coding or improve performancefor Oracle Developer.

Internal Views

This section includes each private, internal view that Payables uses.



SingleOrganization Views

This section lists the Payables views that we added to take the place ofvarious tables that are now partitioned by operating unit, to supportmultiple sets of books within a single installation of Payables.

Multiple Reporting Currency Views

This list includes views that were created to support the MultipleReporting Currencies feature.

Module List

The Module List section briefly describes each of the Payablesapplications modules. This section lists forms, reports, and concurrentprograms.

A form is a module comprised of closely related windows that are usedtogether to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window. The Enter Journals window isthe main window, and from it, you can use buttons to navigate to otherwindows in the form. The form name usually corresponds to the mainwindow in the form, and is frequently a window you can open directlyfrom the Navigator.

The Reports and Concurrent Programs lists include processes you cansubmit from the Submit Requests window or other windows, as well asprocesses that are submitted automatically by Payables. Use yourusers guide to learn more about reports and concurrent processes.

2 5HighLevel Design


Database Diagramming Conventions

We use the following notational conventions in our database diagrams:

Figure 2 1Database DiagramConventions

Mandatory and Optional Foreign Keys

A value entered in the column in the foreign keymust match a value in the primary key column.

&$

" !&&$&

&"!

$%("$!)

$

%$

&%%&"!

&$!&"$

"$!)"!%&$!&

%!&"$!) %& &$ $))

$ $))" !

!&"$)" !

Server Model Diagram Elements and Notation

A value entered in the column in the foreign keymust match either a value in the primary key column,or else it must be null.



Tables are the basic unit of storage in the database. A hand symbolpreceding the title in the tables title bar indicates that the table is notowned by this application but shared with another.

Foreign key constraint is a type of referential integrity constraint forchecking the integrity of data entered in a specific column or set ofcolumns. This specified column or set of columns is known as theforeign key.

Delete rule indicator determines the action to be taken when anattempt is made to delete a related row in a join table. A line throughthe foreign key constraint, as shown on the above diagram, indicatesthat this action is restricted.

Arcs specify that, for any given row in a table, a value must beentered in one of the arc columns. The remaining columns within thearc must be null.

2 7HighLevel Design


Database Diagrams

This section graphically represents most of the significant OraclePayables applications tables and the relationships between them. Usethis section to quickly learn what tables your Payables application uses,and how these tables interrelate. Then, you can refer to the Table andView Definitions sections of Chapter 3 for more detailed informationabout each of those tables.

This section contains a database diagram for each of the following areasof your Payables application:

Diagram 1: Invoices and Payments

Diagram 2: Suppliers

Diagram 3: Payment Batches

Diagram 4: Expense Reports

Diagram 5: Recurring Invoices

Diagram 6: Credit Cards

Diagram 7: Purchasing Integration

Diagram 8: General Ledger Integration

Diagram 9: Projects Integration

Diagram 10: Fixed Assets Integration

Invoices and Payments

Diagram 1 shows the tables and relationships associated with Invoicesand Payments a well as Payables accounting entries. This diagramshows all of the most important Payables tables that store the coretransaction data.

Suppliers

Diagram 2 shows the tables and relationships associated with suppliersand supplier sites in your Oracle Payables application. The diagramsalso show some of the setup data that defaults to new suppliers.

Payment Batches

Diagram 3 shows the tables and relationships utilized when you createpayment batches. In particular, this diagram highlights the temporary



tables that Oracle Payables uses when a payment batch has not yetcompleted.

Expense Reports

Diagram 4 shows the tables and relationships related to the entry ofemployee expense reports using the Payables Expense Reports windowor Oracle SelfService Expenses. You create invoices from expensereports using the Payables Invoice Import program.

Recurring Invoices

Diagram 5 shows the tables and relationships utilized when you createrecurring invoices, for example, lease payments. Oracle Payables willcreate invoices based on your definitions of recurring invoices.

Credit Cards

Diagram 6 shows the tables and relationships associated with theProcurement Card Integration feature. You can import transactionsfrom your card issuers, validate and build accounting distributions fortransactions, notify employees and managers of transactions to beverified and approved, and you can automatically create an invoice topay the credit card issuer. The diagram shows all the tables related tosetting up and using the Credit Card Integration features in yourOracle Payables application. The tables store information about howyou define your credit card program, cards assigned to employees, andinformation about transactions from your card issuer.

Purchasing Integration

Diagram 7 shows the tables and relationships utilized when you matchan invoice to one or more purchase orders or receipts.

General Ledger Integration

Diagram 8 shows the tables and relationships that Oracle Payablesapplications use to integrate with Oracle General Ledger to createjournal entries and to drill down from these journal entries to theaccounting entries in your Payables application.

Projects Integration

Diagram 9 shows the tables and relationships utilized when you storeprojectsrelated information for an invoice, whether the invoice was

2 9HighLevel Design


created in Payables or the invoice was created from an expense reportimported from Projects.

Fixed Assets Integration

Diagram 10 shows the tables and relationships utilized when yourecord assets information for invoices. You use the Mass AdditionsCreate program to import assets information from Payables into OracleAssets.



Invoices and Payments

2 11HighLevel Design


Suppliers



Payment Batches



Expense Reports



Recurring Invoices



Credit Cards



Purchasing Integration



General Ledger Integration



Projects Integration



Fixed Assets Integration



Public Table List

This section lists each public database table that Oracle Payables usesand provides a brief description of each of those tables. The pagereference is to the table description in Chapter 3.

Note that public tables are not necessarily intended for write access bycustom code; Oracle Corporation supports write access using onlystandard Oracle Applications forms, reports, and programs, or any SQLwrite access to tables explicitly documented as API tables. For moreinformation, see the How Not To Use This Manual section of this booksIntroduction.

Oracle Payables uses the following Public tables:

Table Name Description

AP_1096_DATA_ALL Summary payment information for 1099 type suppliers (Seepage 3 8)

AP_1099_TAPE_DATA_ALL Supplier payment amounts by MISC type for 1099 reportson magnetic media (See page 3 9)

AP_ACCOUNTING_EVENTS_ALL Accounting events table (See page 3 11)

AP_AE_HEADERS_ALL Accounting entry headers table (See page 3 12)

AP_AE_LINES_ALL Accounting entry lines table (See page 3 14)

AP_AGING_PERIODS Aging period definitions (See page 3 17)

AP_AGING_PERIOD_LINES Individual aging period information (See page 3 19)

AP_AWT_BUCKETS_ALL Summary amount of tax withheld to date for a particularsupplier site (See page 3 21)

AP_AWT_GROUPS Withholding tax groups (See page 3 22)

AP_AWT_GROUP_TAXES_ALL Withholding group taxes (See page 3 23)

AP_AWT_TAX_RATES_ALL Withholding tax rates (See page 3 24)

AP_AWT_TEMP_DISTRIBUTIONS_ALL Withholding tax temporary distributions (See page 3 27)

AP_BANK_ACCOUNTS_ALL Detailed bank account information (See page 3 29)

AP_BANK_ACCOUNT_USES_ALL Information about bank account use by Oracle Payables andOracle Receivables applications (See page 3 34)

AP_BANK_BRANCHES Detailed bank branch information (See page 3 36)



AP_BANK_CHARGES Bank charges definition information (See page 3 40)

AP_BANK_CHARGE_LINES Ranges for bank charges and tolerance limits (See page3 41)

AP_BATCHES_ALL Summary invoice batch information (See page 3 42)

AP_CARDS_ALL Information about credit cards issued to employees (Seepage 3 46)

AP_CARD_CODES_ALL Information for credit card codes that you define (See page3 48)

AP_CARD_CODE_SETS_ALL Descriptive information about credit card code sets assignedto and used by card programs (See page 3 50)

AP_CARD_GL_ACCTS_ALL Information about the GL accounts and descriptions forcredit card GL account sets (See page 3 51)

AP_CARD_GL_SETS_ALL Descriptive information about credit card GL account sets(See page 3 53)

AP_CARD_PROFILES_ALL Information about the profiles assigned to credit cardsdistributed to your employees (See page 3 54)

AP_CARD_PROFILE_LIMITS_ALL Reserved for a future feature (See page 3 56)

AP_CARD_PROGRAMS_ALL Information about credit card programs you have defined(See page 3 58)

AP_CARD_REQUESTS_ALL Reserved for a future feature (See page 3 60)

AP_CHECKRUN_CONC_PROCESSES_ALL Temporary table for tracking payment batch concurrentprograms (See page 3 62)

AP_CHECKRUN_CONFIRMATIONS_ALL Temporary table for payment batch confirmations (See page3 63)

AP_CHECKS_ALL Supplier payment data (See page 3 64)

AP_CHECK_FORMATS Payment document format records (See page 3 72)

AP_CHECK_INTEGERS Temporary table for list of document numbers used by theMissing Documents Report to find gaps in documentnumbers (See page 3 75)

AP_CHECK_STOCKS_ALL Payment document types (See page 3 76)

AP_CHRG_ALLOCATIONS_ALL Charge allocations table (See page 3 79)



AP_CREDIT_CARD_TRXNS_ALL Detailed information about the credit card transactions ofyour employees (See page 3 80)

AP_DISTRIBUTION_SETS_ALL Invoice Distribution Set definitions (See page 3 85)

AP_DISTRIBUTION_SET_LINES_ALL Individual Distribution Set line definitions (See page 3 87)

AP_DOC_SEQUENCE_AUDIT Voucher numbers assigned to invoices and payments (Seepage 3 89)

AP_DUPLICATE_VENDORS_ALL Supplier information used by Supplier Merge (See page3 90)

AP_ENCUMBRANCE_LINES_ALL Encumbrance lines table (See page 3 92)

AP_EXPENSE_FEED_DISTS_ALL Accounting information for credit card transactions (Seepage 3 94)

AP_EXPENSE_FEED_LINES_ALL Detailed information about credit card transactionsimported from the credit card issuer (See page 3 108)

AP_EXPENSE_REPORTS_ALL Descriptive information about expense report templates(See page 3 111)

AP_EXPENSE_REPORT_HEADERS_ALL Header information about employee expense reports (Seepage 3 112)

AP_EXPENSE_REPORT_LINES_ALL Expense item information for employee expense reports(See page 3 119)

AP_EXPENSE_REPORT_PARAMS_ALL Expense type information for expense report templates (Seepage 3 124)

AP_HISTORY_CHECKS_ALL Summary information about purged invoice payments (Seepage 3 126)

AP_HISTORY_INVOICES_ALL Summary information about purged invoices (See page3 127)

AP_HISTORY_INV_PAYMENTS_ALL Relationships between purged invoices and invoicepayments (See page 3 128)

AP_HOLDS_ALL Invoice hold information (See page 3 129)

AP_HOLD_CODES Invoice hold and release codes (See page 3 135)

AP_INCOME_TAX_REGIONS Income tax region information for supplier tax reportingpurposes (See page 3 139)



AP_INCOME_TAX_TYPES 1099 supplier types (See page 3 141)

AP_INTEREST_PERIODS Interest rates and period information used to create Interestinvoices (See page 3 142)

AP_INTERFACE_CONTROLS Temporary table for importing invoices from the openinterface tables (See page 3 143)

AP_INTERFACE_REJECTIONS Information about data that could not be loaded byPayables Open Interface Import (See page 3 144)

AP_INVOICES_ALL Detailed invoice records (See page 3 149)

AP_INVOICES_INTERFACE Information used to create an invoice using Payables OpenInterface Import (See page 3 157)

AP_INVOICE_DISTRIBUTIONS_ALL Invoice distribution line information (See page 3 162)

AP_INVOICE_KEY_IND_ALL Compiled invoice information for Key Indicators Report(See page 3 175)

AP_INVOICE_LINES_INTERFACE Information used to create one or more invoice distributions(See page 3 177)

AP_INVOICE_PAYMENTS_ALL Invoice payment records (See page 3 184)

AP_INVOICE_RELATIONSHIPS Relationships between invoices and interest invoicesautomatically created for overdue invoices (See page3 189)

AP_INV_SELECTION_CRITERIA_ALL Payment batch invoice selection criteria (See page 3 190)

AP_MATCHED_RECT_ADJ_ALL Tracks receipts that have been modified after invoices havebeen matched to them (See page 3 195)

AP_MC_CHECKS Supplier payment data in MRC defined reporting currency(See page 3 196)

AP_MC_INVOICES Detailed invoice records in MRC defined reporting currency(See page 3 198)

AP_MC_INVOICE_DISTS Invoice distribution line information in MRC definedreporting currency (See page 3 199)

AP_MC_INVOICE_PAYMENTS Invoice payment records in MRC defined reportingcurrency (See page 3 201)

AP_OTHER_PERIODS Recurring invoice, key indicator, payment terms, andwithholding tax time period definitions (See page 3 202)



AP_OTHER_PERIOD_TYPES Recurring invoice, key indicator, and withholding taxperiod type definitions (See page 3 204)

AP_PAYMENT_HISTORY_ALL Maturity and reconciliation history for payments (See page3 206)

AP_PAYMENT_KEY_IND_ALL Compiled payment information for Key Indicators Report(See page 3 209)

AP_PAYMENT_PROGRAMS Payment programs used for defining payment formats (Seepage 3 211)

AP_PAYMENT_REP_ITF Payables Interface table for RX payment reports (See page3 212)

AP_PAYMENT_SCHEDULES_ALL Scheduled payment information on invoices (See page3 214)

AP_PBATCH_SETS_ALL Payment batch sets (See page 3 217)

AP_PBATCH_SET_LINES_ALL Payment batch set lines (See page 3 218)

AP_PURGE_INVOICE_LIST Temporary storage of invoice IDs for invoice purgecandidates (See page 3 221)

AP_R115_UPGRADE Release 11i upgrade values for FUTURE DATED andMANUAL FUTURE DATED payment methods (See page3 222)

AP_RECURRING_PAYMENTS_ALL Recurring invoice parameters (See page 3 223)

AP_REPORTING_ENTITIES_ALL Tax identification information for a tax reporting entity (Seepage 3 229)

AP_REPORTING_ENTITY_LINES_ALL Balancing segment information associated with a taxreporting entity (See page 3 231)

AP_SELECTED_INVOICES_ALL Temporary storage of invoices selected for payment in apayment batch (See page 3 232)

AP_SELECTED_INVOICE_CHECKS_ALL Temporary storage of payment information for invoices in apayment batch (See page 3 237)

AP_SUPPLIER_BALANCE_ITF Stores records for the AP Supplier Open Balance Letterreport (See page 3 240)

AP_SYSTEM_PARAMETERS_ALL Payables system defaults and parameters (See page 3 241)

AP_TAX_CODES_ALL Tax code information (See page 3 251)



AP_TAX_RECVRY_RATES_ALL Used to define recovery rates for tax recovery rules (Seepage 3 254)

AP_TAX_RECVRY_RULES_ALL Contains information about tax recovery rules (See page3 257)

AP_TEMP_APPROVAL_ALL Temporary storage of holds placed and released duringApproval (See page 3 259)

AP_TERMS_LINES Detail information about payment terms (See page 3 261)

AP_TERMS_TL Payment term definitions (See page 3 263)

AP_TOLERANCES_ALL Matching and invoice variance testing tolerance levels (Seepage 3 265)

AP_TRIAL_BAL Temporary table that holds outstanding invoice balances forthe Trial Balance Report (See page 3 266)

AP_TRIAL_BALANCE Denormalized information about posted invoices for youraccrual set of books (See page 3 267)

AP_VENDOR_AUDIT_TMP Temporary table for duplicate supplier candidates duringSupplier Merge (See page 3 268)

AP_VENDOR_KEY_IND_ALL Compiled supplier information for the Key IndicatorsReport (See page 3 269)

AP_WEB_SIGNING_LIMITS_ALL Tracks signing limit authority for SelfServiceExpensesentered expense reports (See page 3 273)

AP_WHT_ITF Information for the submission of the AP Withholding Taxextract program (See page 3 274)

ECE_TP_HEADERS Contains information for trading partner address entity.(See page 3 276)

FA_ASSET_INVOICES Accounts payable and purchasing information for eachasset (See page 3 279)

FA_BOOK_CONTROLS Control information that affects all assets in a depreciationbook (See page 3 283)

FA_MASS_ADDITIONS Information about assets that you want to automaticallyadd to Oracle Assets from another system (See page 3 291)

FA_SYSTEM_CONTROLS Systemwide controls that affect all assets (See page 3 300)



FINANCIALS_PURGES Invoice purge selection criteria and purged invoicestatistical data (See page 3 302)

FINANCIALS_SYSTEM_PARAMS_ALL Oracle Financials system parameters and defaults (See page3 305)

FND_APPLICATION Applications registered with Oracle Application ObjectLibrary (No table description)

FND_CONCURRENT_PROGRAMS Concurrent programs (No table description)

FND_CONCURRENT_REQUESTS Concurrent requests information (No table description)

FND_CURRENCIES Currencies enabled for use at your site (See page 3 309)

FND_DOCUMENT_SEQUENCES Document sequences registered with Oracle ApplicationObject Library (No table description)

FND_DOC_SEQUENCE_ASSIGNMENTS Assigns a sequence to a document (No table description)

FND_DOC_SEQUENCE_CATEGORIES Document category definitions (No table description)

FND_DUAL Dummy base table used by a form block that does not havea real base table (for commit purposes) (See page 3 312)

FND_FLEX_VALUES Valid values for flexfield segments (No table description)

FND_FLEX_VALUE_SETS Value sets used by both key and descriptive flexfields (Notable description)

FND_ID_FLEX_SEGMENTS Key flexfield segments setup information andcorrespondences between table columns and key flexfieldsegments (No table description)

FND_ID_FLEX_STRUCTURES Key flexfield structure information (No table description)

FND_LANGUAGES National dialects (No table description)

FND_LOGINS SignOn Audit information about who signs on to anapplication and when (No table description)

FND_PRINTER Printers registered with Oracle Application Object Library(No table description)

FND_PRODUCT_DEPENDENCIES Dependencies of Oracle Applications products installed atyour site (No table description)

FND_PRODUCT_INSTALLATIONS Oracle Applications products installed at your site (No tabledescription)



FND_RESPONSIBILITY Responsibilities (No table description)

FND_SEGMENT_ATTRIBUTE_VALUES Values of flexfield qualifiers for different segments of keyflexfield structures (No table description)

FND_TERRITORIES Territories, also known as countries (No table description)

FND_USER Application users (No table description)

GL_BALANCES Account balances for both detail and summary accounts(See page 3 313)

GL_BC_PACKETS Budgetary control queue table (See page 3 315)

GL_BUDGETS Budget definitions (See page 3 320)

GL_BUDGET_PERIOD_RANGES Status of budget period ranges (open/not open) (See page3 322)

GL_BUDGET_VERSIONS Budget version definitions (See page 3 323)

GL_CODE_COMBINATIONS Account combinations (See page 3 325)

GL_DAILY_CONVERSION_TYPES Foreign currency daily conversion rate types (See page3 330)

GL_DAILY_RATES Daily conversion rates for foreign currency transactions (Seepage 3 331)

GL_ENCUMBRANCE_TYPES Encumbrance type definitions (See page 3 333)

GL_IMPORT_REFERENCES Crossreferences between subledgers and Oracle GeneralLedgers Journal Entries (See page 3 334)

GL_INTERCOMPANY_ACCOUNTS Assignments of intercompany due to and due fromaccounts to a source, category, and balancing segment value.(See page 3 336)

GL_INTERFACE Import journal entry batches (See page 3 338)

GL_INTERFACE_CONTROL Journal import execution control (See page 3 342)

GL_JE_BATCHES Journal entry batches (See page 3 343)

GL_JE_CATEGORIES_TL Journal entry categories (See page 3 347)

GL_JE_HEADERS Journal entry headers (See page 3 348)

GL_JE_LINES Journal entry lines (See page 3 353)

GL_JE_SOURCES_TL Journal entry sources (See page 3 357)



GL_PERIODS Calendar period definitions (See page 3 359)

GL_PERIOD_SETS Calendar definitions (See page 3 361)

GL_PERIOD_STATUSES Calendar period statuses (See page 3 362)

GL_PERIOD_TYPES Calendar period types (See page 3 364)

GL_SETS_OF_BOOKS Set of books definitions (See page 3 365)

GL_STAT_ACCOUNT_UOM Statistical units of measure (See page 3 369)

GL_SUSPENSE_ACCOUNTS Additional suspense accounts for source/categorycombinations (See page 3 370)

GL_TRANSACTION_RATE_EXCEPTIONS Feeder system journal transaction rate exceptions (See page3 371)

GL_TRANSLATION_RATES Foreign currency translation rates (See page 3 373)

GL_USSGL_TRANSACTION_CODES USSGL transaction codes (See page 3 375)

GL_WEIGHTED_AVG_DETAILS Feeder system journal details calculated using weightedaverage rates (See page 3 376)

HR_LOCATIONS_ALL Work location definitions. (See page 3 378)

MRP_ITEM_PURCHASE_ORDERS Purchase orders and purchase requisitions (See page3 381)

MTL_CATEGORY_SETS_B Category Sets (See page 3 384)

MTL_DEFAULT_CATEGORY_SETS Default category set for a particular functional area (Seepage 3 386)

MTL_MATERIAL_TRANSACTIONS Material transaction table (See page 3 388)

MTL_SUPPLY Stores incoming supply information (See page 3 395)

MTL_SYSTEM_ITEMS_B Inventory item definitions (See page 3 400)

ORG_FREIGHT_TL Freight codes (See page 3 420)

PAY_EXTERNAL_ACCOUNTS Bank account details that enable payments to be made. (Seepage 3 422)

PA_EXPENDITURE_TYPES Implementationdefined classifications of expenditurescharged to projects and tasks (See page 3 424)

PA_EXP_ORGS_IT Information about expenditure organizations for OracleProject Analysis Collection Pack (See page 3 426)



PA_PROJECTS_ALL Information about projects (See page 3 427)

PA_TASKS Userdefined subdivisions of project work (See page3 435)

PO_ACCEPTANCES Purchase order acceptances (See page 3 442)

PO_ACTION_HISTORY Document approval and control action history table (Seepage 3 444)

PO_DISTRIBUTIONS_ALL Purchase order distributions (See page 3 446)

PO_HEADERS_ALL Document headers (for purchase orders, purchaseagreements, quotations, RFQs) (See page 3 452)

PO_HEADERS_ARCHIVE_ALL Archived purchase orders (See page 3 459)

PO_HISTORY_POS_ALL Purged purchase orders (See page 3 465)

PO_HISTORY_RECEIPTS Purged receipts (See page 3 467)

PO_HISTORY_REQUISITIONS_ALL Purged requisitions (See page 3 468)

PO_HISTORY_VENDORS Purged suppliers (See page 3 469)

PO_LINES_ALL Purchase document lines (for purchase orders, purchaseagreements, quotations, RFQs) (See page 3 470)

PO_LINES_ARCHIVE_ALL Archived purchase order lines (See page 3 476)

PO_LINE_LOCATIONS_ALL Document shipment schedules (for purchase orders,purchase agreements, quotations, RFQs) (See page 3 482)

PO_LINE_LOCATIONS_ARCHIVE_ALL Archived purchase order shipments (See page 3 490)

PO_LINE_TYPES_B Line types (See page 3 497)

PO_NOTES No longer used (See page 3 499)

PO_NOTE_REFERENCES Document/notes references (See page 3 501)

PO_NOTIFICATIONS_ALL Notifications (See page 3 503)

PO_ONLINE_REPORT_TEXT Online report errors (See page 3 504)

PO_PURGE_PO_LIST Purchase order candidates for purging (See page 3 506)

PO_PURGE_REQ_LIST Requisition candidates for purging (See page 3 507)

PO_PURGE_VENDOR_LIST Supplier candidates for purging (See page 3 508)



PO_RELEASES_ALL Purchase order releases (See page 3 509)

PO_REQEXPRESS_LINES_ALL Template lines for express requisitions (See page 3 514)

PO_REQUISITION_HEADERS_ALL Requisition headers (See page 3 517)

PO_REQUISITION_LINES_ALL Requisition lines (See page 3 521)

PO_REQ_DISTRIBUTIONS_ALL Requisition distributions (See page 3 528)

PO_RFQ_VENDORS Suppliers on an RFQ (See page 3 531)

PO_SYSTEM_PARAMETERS_ALL Purchasing options (See page 3 533)

PO_UNIQUE_IDENTIFIER_CONT_ALL Purchase order document number control (See page 3 538)

PO_USAGES Note usages (See page 3 539)

PO_VENDORS Suppliers (See page 3 540)

PO_VENDOR_CONTACTS Supplier contacts (See page 3 547)

PO_VENDOR_LIST_ENTRIES RFQ supplier list entries (See page 3 549)

PO_VENDOR_LIST_HEADERS RFQ supplier list headers (See page 3 551)

PO_VENDOR_SITES_ALL Supplier sites (See page 3 553)

RA_CUSTOMERS Customer information (See page 3 558)

RA_SITE_USES_ALL Business purpose of a customer address (See page 3 563)

RCV_LOTS_SUPPLY Receiving lots supply (See page 3 568)

RCV_LOT_TRANSACTIONS Receiving lots transactions (See page 3 570)

RCV_PARAMETERS Organizationlevel receiving controls (See page 3 571)

RCV_ROUTING_HEADERS Receiving routing headers (See page 3 574)

RCV_SERIALS_SUPPLY Receiving serial supply (See page 3 575)

RCV_SERIAL_TRANSACTIONS Receiving serial transactions (See page 3 576)

RCV_SHIPMENT_HEADERS Shipment and receipt header information (See page 3 577)

RCV_SHIPMENT_LINES Receiving shipment line information (See page 3 581)

RCV_TRANSACTIONS Receiving transactions (See page 3 585)

RCV_TRANSACTIONS_INTERFACE Receiving transactions interface table (See page 3 591)



WIP_OPERATIONS Operations necessary for jobs and schedules (See page3 599)



Web View List

This section lists each view we created to simplify access from OracleSelfService Web Applications, and it provides a brief description ofeach of those views. The page reference is to the view description inChapter 3.

Payables uses the following Web views:

View Name Description

AP_EXPENSE_FEED_DISTS_OPEN_V Verify Open Transactions in SelfService Expenses is basedon this view (See page 3 96)

AP_EXPENSE_FEED_DISTS_V View Transaction History in SelfService Expenses is basedon this view (See page 3 102)

AP_WEB_PA_PROJECTS_TASKS_V The View Projects and Tasks function and the Task Numberlist of values in Oracle SelfService Expenses are based onthis view (See page 3 270)

AP_WEB_PA_PROJECTS_V The Project Number list of values in Oracle SelfServiceExpenses is based on this view (See page 3 272)



Forms and Table View List

This section lists supplementary views that are not essential to theRelease 11 data model, but simplify coding or improve performance ofDeveloper/2000. For example, many of these views are used as basetables in Payables forms.

Warning: We do not recommend you query or alter data usingthese views. Furthermore, these views may changedramatically in subsequent minor or major releases of Payables.

Payables uses the following Forms and Table views:

AP_APPLY_PREPAYS_FR_PREPAY_V

AP_APPLY_PREPAYS_V

AP_AWT_BUCKETS_V

AP_AWT_TEMP_DISTRIBUTIONS_V

AP_BANK_ACCOUNT_USES_V

AP_BATCHES_V

AP_CARDS_V

AP_CHARGE_ALLOCATIONS_V

AP_CHECKS_V

AP_CHECKS_WWW_V

AP_CHECK_STOCKS_ACTIVE_V

AP_CHECK_STOCKS_V

AP_DISTRIBUTION_SETS_DSN_V

AP_DISTRIBUTION_SET_LINES_V

AP_DUPLICATE_VENDORS_V

AP_ENCUMBRANCE_LINES_V

AP_EXPENSE_FEED_LINES_V

AP_EXPENSE_REPORT_HEADERS_V

AP_HOLDS_HOLD_NAME_V

AP_HOLDS_OVERVIEW_V

AP_HOLDS_RELEASE_NAME_V

AP_HOLDS_V

AP_HOLD_CODES_HOLD_NAME_V



AP_HOLD_CODES_V

AP_INTERFACE_REJECTIONS_V

AP_INVOICES_DERIVED_V

AP_INVOICES_INTERFACE_V

AP_INVOICES_READY_TO_PAY_V

AP_INVOICES_UNION_PREPAYS_V

AP_INVOICES_V

AP_INVOICES_WWW_V

AP_INVOICE_DISTRIBUTIONS_V

AP_INVOICE_DISTS_INQUIRY_V

AP_INVOICE_LINES_INTERFACE_V

AP_INVOICE_PAYMENTS_V

AP_INVOICE_PAYMENTS_WWW_V

AP_INVOICE_PAYMENT_HISTORY_V

AP_INVOICE_PREPAYS_V

AP_INV_SELECTION_CRITERIA_V

AP_LC_INVOICE_TYPES_DB_V

AP_LC_INVOICE_TYPES_V

AP_LC_PAYMENT_METHODS_V

AP_LC_QUICK_RELEASES_V

AP_OTHER_PERIODS_PN_V

AP_OTHER_PERIODS_V

AP_OTHER_PERIOD_TYPES_PT_V

AP_PAYMENT_SCHEDULES_V

AP_PBATCH_SETS_V

AP_PBATCH_SET_LINES_V

AP_PO_USRDEF_LOOKUP_CODES_V

AP_RECURRING_PAYMENTS_V

AP_TAX_CODES_ACTIVE_V

AP_TAX_CODES_NAMES_V



AP_TAX_CODES_TN_V

AP_TAX_CODES_V

AP_TAX_CODES_VAL_V

AP_TAX_LINES_SUMMARY_V

AP_TERMS_BAT_PAY_TERMS_V

AP_TERMS_V

AP_TERMS_VAL_V

AP_UNAPPLY_PREPAYS_FR_PREPAY_V

AP_UNAPPLY_PREPAYS_V

AP_VENDORS_V

AP_VENDOR_DISP_V

AP_VENDOR_SITES_V

AP_WEB_SIGNING_LIMITS_V

FINANCIALS_PURGES_V

FND_DOCUMENT_SEQUENCES_AP_V

FND_DOC_SEQ_CATEGORIES_AP_V

FND_ID_SEGMENT_NAME_AP_V

GL_JE_BATCHES_AP_V

HR_EMPLOYEES

HR_EMPLOYEES_CURRENT_V

ORG_ORGANIZATION_DEFINITIONS

PA_EXPENDITURE_TYPES_AP_V

PA_PROJECTS_AP_V

PA_PROJECT_TASKS_AP_V

PA_TASKS_AP_V

PO_VENDORS_ACTIVE_AP_V

PO_VENDORS_ALL_V

PO_VENDORS_AP_V

PO_VENDOR_SITES_ALL_V

PO_VENDOR_SITES_PAY_AP_V



Internal View List

This section lists each private, internal view that Payables uses.

Warning: Oracle Corporation does not support access to OracleApplications data using these views, except from standardOracle Applications forms, reports, and programs.

Payables uses the following internal views:

AP_AEL_GL_INV_V

AP_AEL_GL_PAY_V

AP_AEL_SL_INV_V

AP_AEL_SL_PAY_V

AP_AEL_SL_V

AP_AE_HEADERS_V

AP_AE_LINES_V

AP_BANK_BRANCHES_V

AP_CARD_NOTIFICATIONS_V

AP_CHARGES_V

AP_JE_CATEGORIES_V

AP_LOOKUP_CODES

AP_LOOKUP_TYPES

AP_SOB_INFO_V

AP_SRS_ACCTG_CURR_V

AP_SRS_REGION_NAMES_V

AP_SRS_SOB_NAME_V

AP_TEMP_APPROVAL

AP_TERMS_VL

AP_WEB_APPROVER_LOV_V

AP_WEB_DFLEX_LOV_V

PO_DISTRIBUTIONS_AP_V

PO_VENDOR_SITES_AP_V



Single Organization View List

MultiOrganization Support is a feature that allows you to implementmultiple sets of books within a single installation of Oracle Payables,Oracle Receivables, Oracle Purchasing, and Oracle OrderEntry/Shipping. Instead of using multiple installations to provide datasecurity, data is secured by operating unit.

In Release 10.7, we added a column, ORG_ID, to each base table thatrequires partitioning by operating unit, including all transaction tablesand many reference tables, then renamed these tables to end with thesuffix _ALL. Then, to take the place of the renamed table, we create aview (named like the Release 10.6 or earlier table) containing a WHEREclause that automatically restricts data to a single operating unit. TheWHERE clause relies upon the value of an Oracle global variable toindicate the current organization.

If you want to retrieve all information, regardless of operating unit,query the _ALL table. For example, if you are running acrossorganization report, you probably want to query the _ALL table.

However, if you want to report against only a single organization oroperating unit, query the corresponding crossorganizational view,using the familiar 10.6style table name. The view definition willautomatically retrieve only data for your current operating unit.

Additional Information: Multiple Organizations in OracleApplications

Payables uses the following Single Organization views:

AP_1096_DATA

AP_1099_TAPE_DATA

AP_ACCOUNTING_EVENTS

AP_AE_HEADERS

AP_AE_LINES

AP_AWT_BUCKETS

AP_AWT_GROUP_TAXES

AP_AWT_TAX_RATES

AP_AWT_TEMP_DISTRIBUTIONS

AP_BANK_ACCOUNTS

AP_BANK_ACCOUNT_USES



AP_BATCHES

AP_CARDS

AP_CARD_CODES

AP_CARD_CODE_SETS

AP_CARD_GL_ACCTS

AP_CARD_GL_SETS

AP_CARD_PROFILES

AP_CARD_PROFILE_LIMITS

AP_CARD_PROGRAMS

AP_CARD_REQUESTS

AP_CHECKRUN_CONC_PROCESSES

AP_CHECKRUN_CONFIRMATIONS

AP_CHECKS

AP_CHECK_STOCKS

AP_CHRG_ALLOCATIONS

AP_CREDIT_CARD_TRXNS

AP_DISTRIBUTION_SETS

AP_DISTRIBUTION_SET_LINES

AP_DUPLICATE_VENDORS

AP_ENCUMBRANCE_LINES

AP_EXPENSE_FEED_DISTS

AP_EXPENSE_FEED_LINES

AP_EXPENSE_REPORTS

AP_EXPENSE_REPORT_HEADERS

AP_EXPENSE_REPORT_LINES

AP_EXPENSE_REPORT_PARAMS

AP_FLEX_SEGMENT_MAPPINGS

AP_HISTORY_CHECKS

AP_HISTORY_INVOICES

AP_HISTORY_INVOICE_PAYMENTS



AP_HOLDS

AP_INVOICES

AP_INVOICE_DISTRIBUTIONS

AP_INVOICE_KEY_IND

AP_INVOICE_PAYMENTS

AP_INVOICE_PREPAYS

AP_INVOICE_SELECTION_CRITERIA

AP_MATCHED_RECT_ADJ

AP_PAYMENT_DISTRIBUTIONS

AP_PAYMENT_HISTORY

AP_PAYMENT_KEY_IND

AP_PAYMENT_SCHEDULES

AP_PBATCH_SETS

AP_PBATCH_SET_LINES

AP_RECON_DISTRIBUTIONS

AP_RECURRING_PAYMENTS

AP_REPORTING_ENTITIES

AP_REPORTING_ENTITY_LINES

AP_SELECTED_INVOICES

AP_SELECTED_INVOICE_CHECKS

AP_SYSTEM_PARAMETERS

AP_TAX_CODES

AP_TAX_RECVRY_RATES

AP_TAX_RECVRY_RULES

AP_TOLERANCES

AP_VENDOR_KEY_IND

AP_WEB_SIGNING_LIMITS

FINANCIALS_SYSTEM_PARAMETERS



Multiple Reporting Currencies View List

This section lists each view that Payables uses to support the MultipleReporting Currencies (MRC) feature. These views, under certaincircumstances, replace the corresponding transaction tables but retrievecurrencysensitive information expressed in the reporting currencyrather than in the functional currency for the associated set of books.That is, when you access a transaction table from the APPS_MRCschema, an MRC synonym redirects your query to the correspondingMRC view; this MRC view ensures you retrieve currency amountsexpressed in the currency associated with the reporting set of books, asindicated by the userenv variable.

If you have not installed Multiple Reporting Currencies, you do notneed to use these views. If you do use MRC, standard product formsand reports automatically access data using these views whenever yousign on using a reporting currency responsibility.

Additional Information: Multiple Reporting Currencies,Oracle Applications Installation Manual, Volume 1: Architecture andConcepts; and Multiple Reporting Currencies in Oracle Applications

Payables uses the following Multiple Reporting Currencies views:

AP_CHECKS_ALL_MRC_V

AP_CHECKS_MRC_V

AP_INVOICES_ALL_MRC_V

AP_INVOICES_MRC_V

AP_INVOICE_DISTS_ALL_MRC_V

AP_INVOICE_DISTS_MRC_V

AP_INVOICE_PAYMENTS_ALL_MRC_V

AP_INVOICE_PAYMENTS_MRC_V

AP_PAYMENT_HISTORY_MRC_V

AP_PAYMENT_HIST_ALL_MRC_V

AP_SYSTEM_PARAMETERS_MRC_V

AP_SYSTEM_PARAMS_ALL_MRC_V

AP_TRIAL_BALANCE_MRC_V

FINANCIALS_SYSTEM_PARAMS_MRC_V

FIN_SYSTEM_PARAMS_ALL_MRC_V



Module List

This section lists each form, report and concurrent program comprisingOracle Payables.

Forms

APXALLOC Charge Allocations

APXAMDOP Special Calendar

APXCUMSP Payables Options

APXEDSUF Account Segments for Expense Reporting

APXIIFIX Open Interface Invoices

APXIISIM Invoice Gateway

APXINAWT Projected Withholding Tax

APXINWKB Invoice Workbench

APXIWALL Invoice Overview

APXPAWKB Payment Workbench

APXPBSET Payment Batch Sets

APXPGSUB Submit Purge

APXPMTCH Match to Purchase Orders

APXPWALL Payment Overview

APXRICAD Recurring Invoices

APXRMTCH Match to Receipts

APXSPDPF Payment Formats

APXSSFSO Financials Options

APXSSSOB Choose Set of Books

APXSUAPL Aging Periods

APXSUDAP Automatic Payment Programs

APXSUDBC Bank Charges

APXSUDCC Countries and Territories

APXSUDIP Payment Interest Rates

APXSUIAC Invoice Approvals

APXSUMBA Banks



APXSUMDS Distribution Sets

APXSUMMT Invoice Tolerances

APXSUMPS Control Payables Periods

APXSUMVT Payment Terms

APXTADRR Tax Recovery Rules

APXTADTC Tax Codes

APXTADTR Income Tax Regions

APXTBCKT View PeriodToDate Withheld Amounts

APXTCERT Withholding Tax Certificates and Exceiptions

APXTGRPS Withholding Tax Groups

APXTRDRE Reporting Entity

APXUPDAE Update Accounting Entries

APXVDDUP Supplier Merge

APXVDMVD Supplier

APXVWENC View Encumbrances

APXWCARD Credit Cards

APXWCODE Credit Card Code Sets

APXWCTRX Credit Card Transactions

APXWGSET Credit Card GL Account Sets

APXWPROF Credit Card Profiles

APXWPROG Credit Card Programs

APXWSLMT Signing Limits

APXXXDER Expense Report Templates

APXXXEER Expense Report

FNDFFMCV Define CrossValidation Rule

FNDFFMDC Define Descriptive Flexfield Segments

FNDFFMIS Define Key Flexfield Segments

FNDFFMSA Define Shorthand Aliases

FNDFFMSV Define Segment Values

FNDFFMVS Define Value Set

FNDFFSRA Assign Security Rules

FNDFFSRN Define Security Rule



FNDNLDCX Define Currency

FNDPOMSV Update Personal Profile Values

FNDRSRUN Run Reports

FNDRSSET Administer Report Sets

GLXACCMB GL Accounts

GLXRTDLY Daily Rates

GLXRTTYP Conversion Rate Types

GLXSTBKS Set of Books

GLXSTCAL Accounting Calendar

GLXSTPTY Period Types

XLAIQACL View Accounting Lines

Reports

APGVEDPR SF 1166EDP Voucher and Schedule of Payments

APGVOCRR SF 1166OCR Voucher and Schedule of Payments

APGVQPRO Sales Tax and Freight Proration Report

APPAYDIS Payment Distribution Report

APXACPAY Japanese Actual Payment Report

APXAECTR Payables Accounting Entries Report

APXBABAL Bank Account Listing

APXBCACN Bank Charge Accounting Upon Notification Report

APXBCACP Bank Charge Accounting Upon Payment Report

APXBCOBN Batch Control Report by Batch Name

APXBCOEB Batch Control Report by Entered By

APXBCRPT Bank Charges Report

APXCHCCG Missing Document Numbers Report

APXCHCCR Payment Batch Control Report

APXCHECC Payment Exceptions Report

APXCMINV Credit Memo Matching Report

APXCRRCR Cash Requirement Report

APXCRUGL Unrealized Gain/Loss Report



APXEDSRS Expense Distribution Detail Report

APXEMELR Employee Listing

APXFPMDR Future Payment Maturity Date Report

APXGDGDL Distribution Set Listing

APXINAGE Invoice Aging Report

APXINDIA Discounts Available Report

APXINDTL Discounts Taken and Lost Report

APXINDUP Invoice Audit Report

APXINHAP Quick Release Report

APXINHIS Invoice History Report

APXINLST Invoice Audit Listing

APXINMHD Matching Hold Detail Report

APXINPIR Posted Invoice Register

APXINPRT Print Invoice Report

APXINPSR Prepayments Status Report

APXINREV Open Items Revaluation Report

APXINRIR Invoice Register

APXINROH Invoice on Hold Report

APXINSWP Unposted Invoice Sweep Program

APXINUTR Use Tax Liability Report

APXINVAD Invoice Audit Listing by Voucher Number

APXINVPH Supplier Paid Invoice History

APXINVTC Japanese Invoice Transaction Check Report

APXJEHIS Journal with GL Details Report

APXKIRKI Key Indicators Report

APXMHLET Matching Hold Agent Notice

APXMTDCR Payment Register

APXPAYAD Payment Audit by Voucher Number

APXPAYGL Payment Gain/Loss Report

APXPAYSC Japanese Scheduled Payment Report

APXPBFPR Final Payment Register

APXPBPPR Preliminary Payment Register



APXPBSRA Separate Remittance Advice

APXPCEMP Distribute Employee Card Transaction Verifications

APXPCMAN Distribute Manager Card Transactions Approvals

APXPGDEL AP/PO Purge Deletion Routine

APXPGLIS Purge Report Listings

APXPPHIS Supplier Payment History

APXPPREM Prepayments Remittance Report

APXPPSPR Stopped Payments Report

APXPTDCR Posted Payment Register

APXPTPTR Payment Terms Listing

APXQCQCL Lookups Listing

APXRPRPR Recurring Invoices Report

APXRTB Accounts Payable Trial Balance

APXTARRL Tax Recovery Rules Listing

APXTATAT Tax Audit Trail

APXTATCL Tax Codes Listing

APXTAVAR IntraEU VAT Audit Trail

APXTRINE 1099 Invoice Exceptions Report

APXTRRVT 1099 Payments Report

APXTRSWP Unaccounted Transactions Report

APXTRUTT Update Income Tax Details Utility

APXTRVEE 1099 Supplier Exceptions Report

APXTRXRN Transaction Reconciliation Report

APXVCHCR Void Payment Register

APXVDDUP.RDF Supplier Audit Report

APXVDLBL Supplier Mailing Labels

APXVDLET Invalid PO Supplier Notice

APXVDRAL Receiving Hold Requestor Notice

APXVDREV Supplier Balance Revaluation Report

APXVDTIN Tax Information Verification Letter

APXVDVSR Suppliers Report

APXVSRPT New Supplier/New Supplier Site Listing



APXWTCER Withholding Tax Certificate Listing

APXWTINV Withholding Tax by Invoice Report

APXWTPAY Withholding Tax by Payment Report

APXWTSRA Withholding Tax Authority Remittance Advice

APXWTTXA Withholding Tax by Tax Authority Report

APXWTVND Withholding Tax by Supplier Report

APXXPXPL Expense Report Templates Listing

APYRLLVR Tax D

AP Technical Reference Mannual

Documents

Transcript of AP Technical Reference Mannual