Ptop Technical Documentaion

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CAUTION!This document contains proprietary,

confidential information that is the exclusiveproperty of Oracle Corporation.

See back cover forimportant information.

Oracle PurchasingApplications TechnicalReference Manual RELEASE 11iVOLUME 1

December 1999

Oracle Purchasing Applications Technical Reference ManualRelease 11iVolume 1

To order this book, ask for Part No. A8084201

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

Major Contributors: Imran Ali, Kareem Benjamin, Rajaram Bhakta, David Chan, Sonal Hede, Diwas Kc, Vijay Pawar, Divya Reddy, AndrewYeung, James Zhang

Contributors: Rachel Haas

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, ConText, 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, OracleWeb Employees, 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 trademarksof Oracle Corporation. 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.

vContents

Oracle Proprietary, Confidential InformationUse Restricted by Contract

Contents

VOLUME 1

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

Chapter 2 HighLevel Design 2 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of HighLevel Design 2 2. . . . . . . . . . . . . . . . . . . . . . . . . . . Summary Database Diagram 2 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Diagrams 2 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Public Table List 2 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Public View List 2 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms and Table View List 2 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal View List 2 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single Organization View List 2 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Reporting Currencies View List 2 44. . . . . . . . . . . . . . . . . . . . Module List 2 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Index

vi Oracle Purchasing Applications Technical Reference Manual


VOLUME 2

Table and View Definitions (continued) 3 311. . . . . . . . . . . . . . . . . . . . .

Index

C H A P T E R

1T

1 1Introduction


Introduction

he Oracle Purchasing Applications Technical Reference Manualprovides the information you need to understand the underlying

structure of Oracle Purchasing and Oracle Public Sector Purchasing.After reading this manual, you should be able to convert your existingapplications data, integrate your existing applications with your OraclePurchasing application, and write custom reports for your OraclePurchasing application, as well as read data that you need to performother tasks.

This chapter introduces you to the Oracle Purchasing ApplicationsTechnical Reference Manual, and explains how to use it.

1 2 Oracle Purchasing 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 Purchasing Applications Technical Reference Manual containsdetailed, uptodate information about the underlying structure ofOracle Purchasing and Oracle Public Sector Purchasing. As we designand build new releases of Oracle Purchasing applications, we updateour Oracle Designer repository to reflect our enhancements. As aresult, we can always provide you with an Oracle PurchasingApplications Technical Reference Manual that contains the latest technicalinformation as of the publication date. Note that after the publicationdate we may have added new indexes to Oracle Purchasing and OraclePublic Sector Purchasing to improve performance.

About this Manual

This manual describes the Oracle Applications Release 11i data model,as used by Oracle Purchasing; it discusses the database we include witha fresh install of Oracle Applications Release 11i. If you have not yetupgraded to Release 11, 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 Purchasing and Oracle Public SectorPurchasing between releases. The Oracle Applications Product UpdateNotes Release 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 Oracle Purchasing. 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 Purchasing Applications Technical Reference Manual containsthe latest information as of the publication date. For the latestinformation we encourage you to use OracleMetaLink which isaccessible through Oracles Support Web Center (http://www.oracle.com/support/elec_sup ).

Audience

The Oracle Purchasing 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 Purchasing application. If you are not familiar withthe above products, we suggest that you attend one or more of thetraining classes available through Oracle Education (see: OtherInformation Sources: page 1 8).

Public Sector and other industryspecific products

For certain products, including Oracle Purchasing, Oracle providesseveral distinct software versions tailored for a specific industry orvertical, containing additional functionality not present in the base ornonverticalspecific product.

The data model for Oracle Purchasing supports a superset of all thefunctionality used by a verticalspecific version of Oracle Purchasing,including the Oracle Public Sector Financials version of OraclePurchasing. Therefore, you can use this manual in conjunction withOracle Public Sector General Ledger, Oracle Public Sector Payables,Oracle Public Sector Purchasing, or Oracle 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 Oracle Purchasing uses. This chapter alsohas a list of modules.

Detailed Design

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

1 5Introduction


How to Use This Manual

The Oracle Purchasing 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 Purchasingapplication. For example, you can use this manual when you need to:

Convert existing application data

Integrate your Oracle Purchasing application with your otherapplications systems

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 PurchasingApplications Technical Reference Manual:

Suppose you are designing a program to load information from yourexisting system into the Oracle Purchasing suppliers table(PO_VENDORS). The first step is to examine the database diagram inChapter 2. Locate the supplier entity in the diagram to determinewhich other tables include references to suppliers. Once you locate thetable PO_VENDORS, then you should examine the description andcolumns of that table to ensure that your conversion program uses thecorrect column names and fills each column with the appropriate typeof data. Be sure to examine the descriptions of the related tables aswell, to ensure that your conversion maintains database integrity.

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 OraclePurchasing application. Modifying Oracle Purchasing and OraclePublic Sector Purchasing limits your ability to upgrade to futurereleases of your Oracle Purchasing application. In addition, it



interferes with our ability to give you the highquality support youdeserve.

We have constructed your Oracle Purchasing application so that youcan customize 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 Purchasing Applications TechnicalReference Manual does not contain complete information about thedependencies between Oracle Purchasing applications tables.Therefore, you should write data into only those tables we identify asinterface tables. If you write data into other noninterface tables, yourisk violating your data integrity since you might not fulfill all the datadependencies in your Oracle Purchasing 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 Purchasingapplications tables, and to change the meaning of, add, or deletelookup codes and other data in future releases. We do not guaranteethe upward compatibility of the Oracle Purchasing 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.

1 7Introduction


About Oracle Application Object Library

The Oracle Purchasing Applications Technical Reference Manual maycontain references to tables that belong to Oracle Application ObjectLibrary. 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 Purchasing 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.

Summary Database Diagram

A summary database diagram shows the most important applicationtables and the relationships between them. It omits tables andrelationships that contribute little to the understanding of theapplication data model. Typically, a summary database diagram showstables that contain key reference and transaction data.



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 Purchasing application.We want to make these products easy for you and your staff tounderstand and 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 Purchasing User GuideOracle Public Sector Purchasing User Guide

Your user guide provides you with all the information you need to useyour Release 11i Oracle Purchasing application. Each user guide isorganized for fast, easy access to detailed information in a functionand taskoriented organization.

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 Configurator User Guide

This guide describes how to improve order taking and fulfillmentproductivity by eliminating errors in new sales orders and bills ofmaterials. You can use Oracle Configurator to verify product



configurations, automatically select configuration options, and generatemanufacturing bills of materials according to configuration constraints.

Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and referenceinformation for the Oracle Purchasing implementation team, as well asfor users responsible for the ongoing maintenance of OracleApplications product data. This manual also provides information oncreating custom 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 Oracle Purchasing. This manual detailsadditional steps and setup considerations for implementing OraclePurchasing with this feature.

Multiple Organizations in Oracle Applications

If you use the Oracle Applications Multiple Organization Supportfeature to use multiple sets of books for one Oracle Purchasinginstallation, use this guide to learn about setting up and using OraclePurchasing with this feature. This book describes the OracleApplications organization model, which defines business units and therelationships between them in an arbitrarily complex enterprise.Functional and technical overviews of multiple organizations arepresented, as well as information about how to set up and implementthis feature set in the relevant Oracle Applications products.

1 11Introduction


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.

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.

1 13Introduction


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 Purchasing application working for you. This team includesyour Technical Representative, Account Manager, and Oracles largestaff of consultants and support specialists with expertise in yourbusiness area, managing an Oracle server, and your hardware andsoftware environment.



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 Purchasing 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 Purchasing 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 Purchasingand Oracle Public Sector Purchasing that satisfies the business

needs we specify during Strategy and Analysis. It contains databasediagrams for Oracle Purchasing and Oracle Public Sector Purchasingapplication building blocks, lists of database tables and views, and alist of modules.



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 OraclePurchasing applications. And, you can prepare yourself to understandthe detailed design and implementation of Oracle Purchasing andOracle Public Sector Purchasing.


The Summary Database Diagram section graphically represents themost important application tables and the relationships between them.It omits tables and relationships that contribute little to theunderstanding of the application data model. Typically, a summarydatabase diagram shows tables that contain key reference andtransaction data.

We prepare a summary database diagram to describe, at a conceptuallevel, the key information on which our business depends. Later, werefine this summary database diagram, breaking it into multipledatabase diagrams (generally, one per application building block) torepresent all the tables and relationships we need to implement ourapplication in the database.

Review the Summary Database Diagram section to see at a glance themajor tables and relationships on which your Oracle Purchasingapplication depends.

Database Diagrams

The Database Diagrams section graphically represents all OraclePurchasing applications tables and the relationships between them,organized by building block.

Use this section to quickly learn what tables each Oracle Purchasingapplication building block uses, and how those tables interrelate. Then,you can refer to the Table and View Definitions sections of Chapter 3for more detailed information about each of those tables.

2 3HighLevel Design


Table Lists

The Table List sections list the Oracle Purchasing applications tables.Because a product might not include at least one table for each type,this Technical Reference Manual might not include each of thefollowing sections.

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.

Internal Tables

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

View Lists

The View List sections list the Oracle Purchasing views, with onesection for each type of view. Because a product might not include atleast one view for each type, this Technical Reference Manual might notinclude each of the 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 Oracle Purchasinguses.

SingleOrganization Views

This section lists the Oracle Purchasing views that we added to take theplace of various tables that are now partitioned by operating unit, tosupport multiple sets of books within a single installation of OraclePurchasing.

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 Oracle Purchasingapplications 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.

2 5HighLevel Design


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 Oracle Purchasing. Useyour users guide to learn more about reports and concurrentprocesses.




This Summary Database Diagram graphically represents the mostimportant Oracle Purchasing applications tables and the relationshipsbetween them. It describes, at a conceptual level, the key informationon which your Oracle Purchasing application depends.

This diagram does not represent the complete database implementationof Oracle Purchasing applications tables. It shows tables that containkey reference and transaction data, and omits tables and relationshipsthat contribute little to the understanding of the Oracle Purchasingapplications data model. For example, a foreign key relationshipshown between two tables may actually be implemented by anintervening table, not shown in this diagram.

For more detailed graphical representations of Oracle Purchasingapplications tables and the relationships between them, see theDatabase Diagrams section in this chapter.

2 7HighLevel 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 9HighLevel Design


Oracle Purchasing Applications Summary Database Diagram



Database Diagrams

This section graphically represents all Oracle Purchasing applicationstables and the relationships between them, organized by buildingblock. Use this section to quickly learn what tables each OraclePurchasing application building block uses, and how these tablesinterrelate. Then, you can refer to the Table and View Definitionssections of Chapter 3 for more detailed information about each of thosetables.

This section contains a database diagram for each of the followingOracle Purchasing application building blocks:

Diagram 1: Requisitions

Diagram 2: Purchase Orders, Requests for Quotations, and Quotations

Diagram 3: Sourcing

Diagram 4: Receiving

Diagram 5: Suppliers

Diagram 6: Items

Diagram 7: Options

Some tables, especially important reference tables, appear in more thanone database diagram. When several building blocks use a table, weshow that table in each appropriate database diagram.

Requisitions

Diagram 1 shows the tables and relationships associated with creatingand maintaining requisitions in your Oracle Purchasing application.Related functions include importing requisitions from other systems,checking funds, and approving requisitions. The tables store preparernames, item types and categories, source details, currency information,and destination information.

Purchase Orders, Requests for Quotations, and Quotations

Diagram 2 shows the tables and relationships associated with creatingand maintaining purchase orders, requests for quotations (RFQs), andquotations. Related functions include entering blanket and contractpurchase agreements, as well as automatically creating purchasingdocuments. The tables store purchase order headers, lines, shipments

2 11HighLevel Design


and distributions, and other information related to purchasing goods orservices from a supplier.

Sourcing

Diagram 4 shows the tables and relationships that store item sourcinginformation. This information includes approved supplier lists, theinventory sourcing hierarchy, RFQs, quotations, and MRP sourcingrules.

Receiving

Diagram 3 shows the tables and relationships that record the receipt ofsupplier shipments and inventory transfers, quality inspections forthese receipts, the final delivery of the items received, and otherinformation related to receiving goods or services from suppliers orinventory organizations.

Suppliers

Diagram 5 shows the tables and relationships that store supplierinformation. This information includes supplier names, sites, contacts,and other supplier defaults that you define.

Items

Diagram 6 shows the tables and relationships associated with items.This information includes items, substitute items, units of measure,item price and purchase history, hazardous materials, and approvedsupplier lists.

Options

Diagram 7 shows the tables and relationships associated with systemoperations. This information includes default information such as linetype, encumbrance type, currency conversion type, numberingconventions, and document reports.



How to Use These Database Diagrams

Here is an example of how you might use these database diagrams:

Suppose you want to write a custom report that summarizes therequisitions made for delivery to each of your seventeen factory andoffice locations. You turn to Diagram 1 to see the table structure for theRequisitions building block. You learn that each line of a requisitionstored in PO_REQUISITION_LINES_ALL is requested for delivery to alocation defined in HR_LOCATIONS. You also see that you canidentify the requisition in PO_REQUISITION_HEADERS_ALL and therequesting employee using HR_EMPLOYEES.

Next, you turn to the Table and View Definitions section in Chapter 3to learn about the columns in each of these tables and determine whichcolumns are required for matching. Using this information, you write areport that shows, for each delivery location, a summary of therequisitioned items to be delivered to that location.



Diagram 1: Requisitions



Diagram 2: Purchase Orders, Requests for Quotations, and Quotations



Diagram 3: Sourcing



Diagram 4: Receiving



Diagram 4: Receiving (continued)



Diagram 5: Suppliers



Diagram 6: Items



Diagram 7: Options



Public Table List

This section lists each public database table that Oracle Purchasing 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 Purchasing uses the following Public tables:

Table Name Description

AP_CHECKS_ALL Supplier payment data (See page 3 8)

AP_DISTRIBUTION_SETS_ALL Invoice Distribution Set definitions (See page 3 16)

AP_HOLDS_ALL Invoice hold information (See page 3 18)

AP_INCOME_TAX_TYPES 1099 supplier types (See page 3 24)

AP_INVOICES_ALL Detailed invoice records (See page 3 25)

AP_INVOICE_DISTRIBUTIONS_ALL Invoice distribution line information (See page 3 33)

AP_INVOICE_PAYMENTS_ALL Invoice payment records (See page 3 46)

AP_TAX_CODES_ALL Tax code information (See page 3 51)

AP_TERMS_TL Payment term definitions (See page 3 54)

BOM_CALENDAR_DATES Workday calendar dates (See page 3 56)

BOM_DEPARTMENTS Departments (See page 3 58)

BOM_RESOURCES Resources, overheads, material cost codes, and materialoverheads (See page 3 60)

BOM_STANDARD_OPERATIONS Standard operations (See page 3 63)

CST_ITEM_COSTS Item cost summary (See page 3 66)

FA_CATEGORIES_B Default financial information for asset categories (base MLStable) (See page 3 68)

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



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

FND_COMPILED_ID_FLEXS Compiled information about key flexfields (No tabledescription)

FND_COMPILED_ID_FLEX_STRUCTS Compiled information about key flexfield structures (Notable 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 76)

FND_DATA_GROUP_UNITS ORACLE accounts for applications assigned to various datagroups (No table description)

FND_DESCR_FLEX_CONTEXTS Structure names for descriptive flexfields (No tabledescription)

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

FND_FLEX_VALIDATION_RULES Key flexfield crossvalidation rules or line detail (No tabledescription)

FND_FLEX_VALIDATION_RULE_LINES Crossvalidation rule elements for key flexfields (No tabledescription)

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

FND_FUNCTION_PARAMETER_MAP No longer used (No table description)

FND_ID_FLEXS Registration information about key flexfields (No tabledescription)

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_NOTIFICATIONS No longer used (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_SHORTHAND_FLEX_ALIASES Alias information for shorthand flexfield entry (No tabledescription)

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 80)

GL_BC_PACKETS Budgetary control queue table (See page 3 82)

GL_BUDGET_VERSIONS Budget version definitions (See page 3 87)

GL_CODE_COMBINATIONS Account combinations (See page 3 89)

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

GL_ENCUMBRANCE_TYPES Encumbrance type definitions (See page 3 95)

GL_INTERFACE Import journal entry batches (See page 3 96)

GL_INTERFACE_CONTROL Journal import execution control (See page 3 100)

GL_JE_BATCHES Journal entry batches (See page 3 101)

GL_JE_CATEGORIES_TL Journal entry categories (See page 3 105)

GL_JE_HEADERS Journal entry headers (See page 3 106)

GL_JE_LINES Journal entry lines (See page 3 111)

GL_JE_SOURCES_TL Journal entry sources (See page 3 115)

GL_PERIODS Calendar period definitions (See page 3 117)

GL_PERIOD_STATUSES Calendar period statuses (See page 3 119)

GL_PERIOD_TYPES Calendar period types (See page 3 121)

GL_SETS_OF_BOOKS Set of books definitions (See page 3 122)



GL_TRANSLATION_RATES Foreign currency translation rates (See page 3 126)

GL_USSGL_TRANSACTION_CODES USSGL transaction codes (See page 3 128)

HR_LOCATIONS_ALL Work location definitions. (See page 3 129)

MRP_SOURCING_RULES Sourcing Rules or Bills of Distribution (See page 3 132)

MRP_SR_ASSIGNMENTS Sourcing assignments (See page 3 133)

MRP_SR_RECEIPT_ORG Receiving Organizations for Sourcing Rules or Bills ofdistribution (See page 3 135)

MRP_SR_SOURCE_ORG Source organization for Sourcing Rules or Bills ofdistribution (See page 3 137)

MTL_CATEGORIES_B Code combinations table for item categories (See page3 139)

MTL_CATEGORY_SETS_B Category Sets (See page 3 141)

MTL_CATEGORY_SET_VALID_CATS Valid categories for category sets (See page 3 143)

MTL_COUNTRY_ASSIGNMENTS stores information concerning the assignment of countriesto economic zones. (See page 3 144)

MTL_CROSS_REFERENCES Assign cross references to items (See page 3 145)

MTL_ECONOMIC_ZONES_B Stores information concerning all the economic zones. (Seepage 3 147)

MTL_ECONOMIC_ZONES_TL Corresponding translation table forMTL_ECONOMIC_ZONES_B (See page 3 148)

MTL_INTERORG_PARAMETERS Interorganization relationships (See page 3 149)

MTL_ITEM_CATEGORIES Define item assignments to categories (See page 3 152)

MTL_ITEM_LOCATIONS Definitions for stock locators (See page 3 154)

MTL_ITEM_LOC_DEFAULTS Inventory item receiving and shipping locator defaultvalues (See page 3 157)

MTL_ITEM_REVISIONS Item revisions (See page 3 158)

MTL_ITEM_SUB_DEFAULTS Inventory item receiving and shipping subinventory defaultvalues (See page 3 160)

MTL_ITEM_SUB_INVENTORIES Itemsubinventory assignments (See page 3 161)



MTL_KANBAN_CARDS Kanban Cards (See page 3 163)

MTL_LE_ECONOMIC_ZONES stores information concerning the assignment of legal entityto economic zones. (See page 3 166)

MTL_LOT_NUMBERS Lot number definitions (See page 3 167)

MTL_MANUFACTURERS Define manufacturers (See page 3 169)

MTL_MATERIAL_TRANSACTIONS Material transaction table (See page 3 170)

MTL_MATERIAL_TRANSACTIONS_TEMP Temporary table for processing material transactions (Seepage 3 177)

MTL_MFG_PART_NUMBERS Define manufacturer part numbers (See page 3 183)

MTL_ONHAND_QUANTITIES FIFO quantities by control level and receipt (See page3 185)

MTL_PARAMETERS Inventory control options and defaults (See page 3 187)

MTL_RELATED_ITEMS Item relationships (See page 3 194)

MTL_SECONDARY_INVENTORIES Subinventory definitions (See page 3 196)

MTL_SECONDARY_LOCATORS Itemsubinventorylocator assignments (See page 3 200)

MTL_SERIAL_NUMBERS Serial number definitions (See page 3 201)

MTL_SERIAL_NUMBERS_TEMP Temporary serial number holding table (See page 3 204)

MTL_STAT_TYPE_USAGES Stores information which determines the statistical typedata for each legal entity. (See page 3 205)

MTL_SUPPLY Stores incoming supply information (See page 3 206)

MTL_SYSTEM_ITEMS_B Inventory item definitions (See page 3 211)

MTL_TRANSACTION_ACCOUNTS Material transaction distributions (See page 3 231)

MTL_TRANSACTION_LOTS_TEMP Temporary lot numbers holding table (See page 3 234)

MTL_TRANSACTION_LOT_NUMBERS Transaction lot numbers (See page 3 236)

MTL_TRANSACTION_REASONS Inventory Transaction Reasons Table (See page 3 237)

MTL_TRANSACTION_TYPES Inventory Transaction Types Table (See page 3 238)

MTL_UNITS_OF_MEASURE_TL Unit of measure definitions (See page 3 240)

MTL_UOM_CLASSES_TL Unit of measure classes (See page 3 242)



MTL_UOM_CLASS_CONVERSIONS Conversions between base units of two different classes (Seepage 3 243)

MTL_UOM_CONVERSIONS Unit of measure conversion table for both default and itemspecific conversions (See page 3 244)

ORG_ACCT_PERIODS Organization accounting period definition table (See page3 246)

ORG_FREIGHT_TL Freight codes (See page 3 248)

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

PA_PROJECTS_ALL Information about projects (See page 3 252)

PA_TASKS Userdefined subdivisions of project work (See page3 260)

PER_POSITION_STRUCTURES Position Hierarchy names (See page 3 269)

POA_BIS_SAVINGS Purchase details and analysis based on contracts (See page3 271)

POA_BIS_SAVINGS_RPT Temporary table for Purchasing Intelligence reports (Seepage 3 273)

POA_BIS_SUPPLIER_PERFORMANCE Summary information to compare suppliers for an item (Seepage 3 278)

PO_ACCEPTANCES Purchase order acceptances (See page 3 284)

PO_ACCRUAL_ACCOUNTS_TEMP_ALL Accrual accounts temporary table (See page 3 286)

PO_ACCRUAL_RECONCILE_TEMP_ALL Accrual Reconciliation Report temporary table (See page3 287)

PO_ACCRUAL_WRITE_OFFS_ALL Accrual writeoffs (See page 3 290)

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

PO_AGENTS Buyers table (See page 3 295)

PO_APPROVAL_LIST_HEADERS Purchasing document approval list (See page 3 297)

PO_APPROVAL_LIST_LINES Purchasing document lines approval list (See page 3 298)

PO_APPROVED_SUPPLIER_LIST Approved supplier list (See page 3 299)



PO_ASL_ATTRIBUTES Approved supplier list attributes (See page 3 301)

PO_ASL_DOCUMENTS Approved supplier list documents (See page 3 303)

PO_ASL_STATUSES Approved supplier list statuses (See page 3 304)

PO_ASL_STATUS_RULES Approved supplier list status rules (See page 3 305)

PO_ATT_TMP_RECORDS No longer used (See page 3 311)

PO_AUTOSOURCE_DOCUMENTS_ALL No longer used (See page 3 312)

PO_AUTOSOURCE_RULES No longer used (See page 3 314)

PO_AUTOSOURCE_VENDORS No longer used (See page 3 316)

PO_CONTROL_FUNCTIONS Control document type functions (See page 3 317)

PO_CONTROL_GROUPS_ALL Document authorization groups (See page 3 319)

PO_CONTROL_RULES Document authorization rules (See page 3 321)

PO_DISTRIBUTIONS_ALL Purchase order distributions (See page 3 326)

PO_DISTRIBUTIONS_ARCHIVE_ALL Archived distributions (See page 3 332)

PO_DISTRIBUTIONS_INTERFACE Interface table for purchase order distributions (See page3 337)

PO_DOCUMENT_TYPES_ALL_B Document types (See page 3 341)

PO_DOCUMENT_TYPES_ALL_TL Translated document types (See page 3 344)

PO_EMPLOYEE_HIERARCHIES_ALL Employee and position hierarchies (See page 3 345)

PO_HAZARD_CLASSES_B Hazardous classes (See page 3 346)

PO_HAZARD_CLASSES_TL Translated hazardous classes (See page 3 347)

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

PO_HEADERS_ARCHIVE_ALL Archived purchase orders (See page 3 355)

PO_HEADERS_INTERFACE Interface table for purchase order headers (See page 3 361)

PO_HISTORY_POS_ALL Purged purchase orders (See page 3 364)

PO_HISTORY_RECEIPTS Purged receipts (See page 3 366)

PO_HISTORY_REQUISITIONS_ALL Purged requisitions (See page 3 367)



PO_HISTORY_VENDORS Purged suppliers (See page 3 368)

PO_INTERFACE_ERRORS Requisition import interface errors (See page 3 369)

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

PO_LINES_ARCHIVE_ALL Archived purchase order lines (See page 3 377)

PO_LINES_INTERFACE Interface table for purchase order lines (See page 3 383)

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

PO_LINE_LOCATIONS_ARCHIVE_ALL Archived purchase order shipments (See page 3 396)

PO_LINE_TYPES_B Line types (See page 3 403)

PO_LINE_TYPES_TL Translated line types (See page 3 405)

PO_LOCATION_ASSOCIATIONS Location associations to customers and customer sites (Seepage 3 406)

PO_MASSCANCEL_INCLUDES_ALL MassCancel rules (See page 3 408)

PO_MASSCANCEL_INTERIM MassCancel temporary table (See page 3 412)

PO_MC_DISTRIBUTIONS Multiple Reporting Currencies (MRC) subtable ofPO_DISTRIBUTIONS_ALL (See page 3 414)

PO_MC_HEADERS MRC subtable of PO_HEADERS (See page 3 415)

PO_NOTES No longer used (See page 3 416)

PO_NOTE_ATTRIBUTES No longer used (See page 3 418)

PO_NOTE_REFERENCES No longer used (See page 3 419)

PO_NOTIFICATIONS_ALL No longer used (See page 3 421)

PO_NOTIFICATION_CONTROLS Blanket agreement and planned purchase order notificationcontrols (See page 3 422)

PO_ONLINE_REPORT_TEXT Online report errors (See page 3 424)

PO_POSITION_CONTROLS_ALL Job/organization and position controls (See page 3 426)

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

PO_PURGE_REQ_LIST Requisition candidates for purging (See page 3 429)



PO_PURGE_VENDOR_LIST Supplier candidates for purging (See page 3 430)

PO_QUALITY_CODES Quality inspection codes (See page 3 431)

PO_QUOTATION_APPROVALS_ALL Quotation approvals (See page 3 432)

PO_RELATED_TEMPLATES Not used in Release 11i (See page 3 434)

PO_RELEASES_ALL Purchase order releases (See page 3 435)

PO_RELEASES_ARCHIVE_ALL Archived releases (See page 3 440)

PO_REQEXPRESS_HEADERS_ALL Template headers for express requisitions (See page 3 445)

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

PO_REQUISITIONS_INTERFACE_ALL Requisition Import interface table (See page 3 450)

PO_REQUISITION_HEADERS_ALL Requisition headers (See page 3 459)

PO_REQUISITION_LINES_ALL Requisition lines (See page 3 463)

PO_REQ_DISTRIBUTIONS_ALL Requisition distributions (See page 3 470)

PO_REQ_DIST_INTERFACE_ALL Interface table for requisition distributions (See page3 473)

PO_RESCHEDULE_INTERFACE Requisition reschedule interface table (See page 3 476)

PO_RFQ_VENDORS Suppliers on an RFQ (See page 3 477)

PO_SUPPLIER_ITEM_CAPACITY Supplier capacity information (See page 3 479)

PO_SUPPLIER_ITEM_TOLERANCE Supplier capacity tolerance information (See page 3 481)

PO_SYSTEM_PARAMETERS_ALL Purchasing options (See page 3 482)

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

PO_UN_NUMBERS_B United Nations numbers (See page 3 488)

PO_UN_NUMBERS_TL Translated United Nations numbers (See page 3 490)

PO_USAGES Note usages (See page 3 491)

PO_USAGE_ATTRIBUTES Note usage attributes (See page 3 492)

PO_VENDORS Suppliers (See page 3 493)

PO_VENDOR_CONTACTS Supplier contacts (See page 3 500)

PO_VENDOR_LIST_ENTRIES RFQ supplier list entries (See page 3 502)



PO_VENDOR_LIST_HEADERS RFQ supplier list headers (See page 3 504)

PO_VENDOR_SITES_ALL Supplier sites (See page 3 506)

PO_WF_CANDIDATE_REQ_LINES_TEMP Temporary table to store requisition lines that can beautomatically created using workflow (See page 3 511)

PO_WF_DEBUG This table is reserved for use by Oracle only (See page3 512)

RA_ADDRESSES_ALL Customer address information (See page 3 513)

RA_CUSTOMERS Customer information (See page 3 518)

RA_RULES Invoicing and accounting rules (See page 3 523)

RA_SALESREPS_ALL Information about salespeople (See page 3 525)

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

RA_TERMS_B Payment Term information (See page 3 533)

RCV_HEADERS_INTERFACE RCV_HEADERS_INTERFACE is the interface table thatstores receiving header information. (See page 3 535)

RCV_LOTS_INTERFACE Receiving lots interface table (See page 3 538)

RCV_LOTS_SUPPLY Receiving lots supply (See page 3 539)

RCV_LOT_TRANSACTIONS Receiving lots transactions (See page 3 541)

RCV_MC_REC_SUB_LEDGER MRC subtable of RCV_RECEIVING_SUB_LEDGER (Seepage 3 542)

RCV_MC_SHIPMENT_HEADERS MRC subtable of RCV_SHIPMENT_HEADERS (See page3 544)

RCV_MC_TRANSACTIONS MRC subtable of RCV_TRANSACTIONS (See page3 545)

RCV_PARAMETERS Organizationlevel receiving controls (See page 3 546)

RCV_RECEIVING_SUB_LEDGER Receiving subledger (See page 3 549)

RCV_ROUTING_HEADERS Receiving routing headers (See page 3 552)

RCV_ROUTING_STEPS Receiving routing steps (See page 3 553)

RCV_SERIALS_INTERFACE Receiving serial interface table (See page 3 555)

RCV_SERIALS_SUPPLY Receiving serial supply (See page 3 556)



RCV_SERIAL_TRANSACTIONS Receiving serial transactions (See page 3 557)

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

RCV_SHIPMENT_LINES Receiving shipment line information (See page 3 562)

RCV_SUB_LEDGER_DETAILS Detailed accounting lines for the receiving transaction (Seepage 3 566)

RCV_SUPPLY Summary information about items in receiving/inspection(See page 3 569)

RCV_TRANSACTIONS Receiving transactions (See page 3 572)

RCV_TRANSACTIONS_INTERFACE Receiving transactions interface table (See page 3 578)

RCV_UPGRADE_STEPS Temporary table for tracking a receiving upgrade fromRelease 9 to Release 10 (See page 3 587)

SO_HEADERS_ALL Order header information (See page 3 588)

SO_HEADERS_INTERFACE_ALL Imported order header information (See page 3 595)

SO_LINES_ALL Order lines (See page 3 601)

SO_LINES_INTERFACE_ALL Imported order line information (See page 3 611)

SO_LINE_DETAILS_INTERFACE Imported order line schedule details (See page 3 618)

SO_ORDER_CANCELLATIONS Order and order line cancellations (See page 3 620)

SO_ORDER_SOURCES_115 Feeder system names for use with OrderImport (See page3 622)

SO_ORDER_TYPES_115_ALL Order types (See page 3 623)

SO_PICKING_LINES_ALL Picking lines (See page 3 627)

SO_PRICE_LISTS_B Price lists (See page 3 630)

SO_SALES_CREDIT_TYPES_115 Sales credit types (See page 3 632)

SO_STANDARD_VALUE_RULE_SETS Standard value rule sets (See page 3 634)

WIP_COST_TXN_INTERFACE Requests to process cost transactions (See page 3 635)

WIP_DISCRETE_JOBS Discrete jobs (See page 3 640)

WIP_ENTITIES Information common to jobs and schedules (See page3 646)



WIP_LINES Production lines (See page 3 648)

WIP_MOVE_TXN_INTERFACE Requests to process shop floor move transactions (See page3 650)

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

WIP_OPERATION_RESOURCES Resources necessary for operations (See page 3 657)

WIP_PARAMETERS WIP specific organization level parameters (See page3 660)

WIP_REPETITIVE_SCHEDULES Repetitive schedules (See page 3 664)

WIP_REQUIREMENT_OPERATIONS Components required by jobs and schedules (See page3 667)

WIP_TRANSACTIONS WIP resource transactions (See page 3 670)

WIP_TRANSACTION_ACCOUNTS Debits and credits due to resource transactions (See page3 674)



Public View List

This section lists each public database view that Oracle Purchasing usesand provides a brief description of each of those views. These viewsmay be useful for your custom reporting or other data requirements.The page reference is to the detailed view description in Chapter 3.

Oracle Purchasing uses the following public views:

View Name Description

MTL_COUNTRY_ASSIGNMENTS_V Joins territories and country assignments

MTL_ECONOMIC_ZONES_VL Joins the base economic zone table and translated economiczone table

MTL_LE_ECONOMIC_ZONES_V Joins the table MTL_LE_ECONOMIC_ZONES, the viewMTL_ECONOMIC_ZONES_VL and HR_LEGAL_ENTITIES

MTL_STAT_TYPE_USAGES_V Joins STAT_TYPE_USAGES, HR Legal Entities, CategorySets, Economic Zones View, and HR Locations

PER_ORGANIZATION_UNITS Lists information about Organization Units (See page3 267)

POA_BIS_SAVINGS_V This view resolves the foreign key references in thePOA_BIS_SAVINGS table. Please refer to the base table forfurther information. (See page 3 275)

POA_BIS_SUPPLIER_PERFORMANCE_V This view is based on thePOA_BIS_SUPPLIER_PERFORMANCE table. Please referto the base view for further information. (See page 3 280)

POA_PURCHASE_SALES_V This view shows purchases and sales amounts forOperating Units (See page 3 282)



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 Oracle Purchasing 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 OraclePurchasing.

Oracle Purchasing uses the following Forms and Table views:

GL_USSGL_TRANSACTION_CODES_V

HR_EMPLOYEES

HR_EMPLOYEES_CURRENT_V

MTL_ITEM_FLEXFIELDS

ORG_FREIGHT_CODE_VAL_V

ORG_ORGANIZATION_DEFINITIONS

POA_BIS_PPS_OPERU_LOV_V

POA_BIS_SAVINGS_BUYER_LOV_V

POA_BIS_SAVINGS_COMM_LOV_V

POA_BIS_SAVINGS_OPERU_LOV_V

POA_BIS_SAVINGS_ORG_LOV_V

POA_BIS_SAVINGS_SUPPLIER_LOV_V

POA_BIS_SUPPERF_CONSUPP_LOV_V

POA_BIS_SUPPERF_ITEM_LOV_V

POA_BIS_SUPPERF_PRESUPP_LOV_V

PO_ACCEPTANCES_V

PO_ACTION_HISTORY_V

PO_AGENTS_NAME_V

PO_AGENTS_V

PO_APPROVED_SUPPLIER_LIST_V

PO_ASL_ATTRIBUTES_V

PO_ASL_DOCUMENTS_V



PO_ASL_ITEMS_V

PO_ASL_STATUS_RULES_V

PO_AUTOSOURCE_DOCUMENTS_V

PO_AUTOSOURCE_RULES_V

PO_BUYERS_ALL_V

PO_BUYERS_VAL_V

PO_CATALOG_QUOTES_ALL_V

PO_CONTROL_GROUPS

PO_DESTINATION_TYPES_ALL_V

PO_DISTRIBUTIONS_INQ_V

PO_DISTRIBUTIONS_V

PO_DOCUMENT_TYPES_V

PO_HAZARD_CLASSES_VAL_V

PO_HEADERS_INQ_V

PO_HEADERS_RFQQT_V

PO_HEADERS_V

PO_HEADER_RELEASE_V

PO_LINES_ALL_V

PO_LINES_INQ_V

PO_LINES_RELEASE_ITEMS_V

PO_LINES_RFQQT_V

PO_LINES_SUPPLIER_ITEMS_ALL_V

PO_LINES_V

PO_LINES_VAL_V

PO_LINE_LOCATIONS_INQ_V

PO_LINE_LOCATIONS_RELEASE_V

PO_LINE_LOCATIONS_V

PO_LINE_TYPES_ALL_V

PO_LINE_TYPES_V

PO_LINE_TYPES_VAL_V



PO_MASSCANCEL_INCLUDES

PO_MASSCANCEL_INTERIM_V

PO_NEGOTIATED_SOURCES_V

PO_POS_ALL_V

PO_POS_VAL_V

PO_PURCHASE_HISTORY_V

PO_QUOTATIONS_TO_APPROVE

PO_QUOTATION_APPROVALS_V

PO_RECEIVED_VIA_VAL_V

PO_RELEASES_ALL_V

PO_RELEASES_V

PO_REQEXPRESS_LINES_V

PO_REQS_IN_POOL_V

PO_REQUISITION_HEADERS_ALL_V

PO_REQUISITION_HEADERS_INQ_V

PO_REQUISITION_HEADERS_V

PO_REQUISITION_LINES_INQ_V

PO_REQUISITION_LINES_V

PO_REQUISITION_TEMPLATES_V

PO_REQ_DISTRIBUTIONS_INQ_V

PO_REQ_DISTRIBUTIONS_V

PO_RFQQT_DOCUMENT_TYPES_ALL_V

PO_RFQS_ALL_V

PO_RFQ_VENDORS_V

PO_SHIPMENTS_ALL_V

PO_SHIP_TO_LOC_ORG_V

PO_SOURCE_SHIPMENT_NUM_V

PO_SUPPLIERS_ALL_V

PO_SUPPLIERS_VAL_V

PO_SUPPLIER_PO_SITES_VAL_V



PO_UNIQUE_IDENTIFIER_CONTROL

PO_UN_NUMBERS_V

PO_UN_NUMBERS_VAL_V

PO_WF_NOTIFICATIONS_V

RCV_CONFIRM_RECEIPT_V

RCV_CORRECTIONS_V

RCV_COR_SUP_LOTS_V

RCV_ENTER_RECEIPTS_V

RCV_MSH_V

RCV_MSL_V

RCV_MUR_V

RCV_RECEIPTS_ALL_V

RCV_RECEIVING_PARAMETERS_V

RCV_RETURNS_V

RCV_SERIAL_CORRECTION_V

RCV_SHIPMENT_HEADERS_V

RCV_SOURCES_BOTH_VAL_V

RCV_TRANSACTIONS_V

RCV_TRX_INT_LOTS_V

RCV_TRX_INT_SERIALS_V

RCV_UNPROCESSED_LOTS_V

RCV_UNPROCESSED_LOT_ISSUES_V

RCV_VIEW_INTERFACE_V

RCV_VRC_HDS_V

RCV_VRC_TXS_V



Internal View List

This section lists each private, internal view that Oracle Purchasing uses.

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

Oracle Purchasing uses the following internal views:

CST_ITEM_COSTS_FOR_GL_VIEW

FND_NOTIFICATIONS_V

HR_EMPLOYEES_ALL_V

MTL_DEFAULT_SETS_VIEW

MTL_ITEM_QUANTITIES_VIEW

PER_POSITION_STRUCTURES_ALL_V

POA_BIS_SAVINGS_RPT_V

PO_832_BATCH_ID_V

PO_ACT_HIST_V

PO_ALERT_BLANKET_VIEW

PO_ALERT_CONTRACT_VIEW

PO_ALERT_CONTRACT_VIEW2

PO_ALERT_PLANNED_VIEW

PO_ALERT_SCHEDULED_VIEW

PO_APPROVED_SUPPLIER_LIS_VAL_V

PO_AP_RECEIPT_MATCH_V

PO_ASL_ATTRIBUTES_VAL_V

PO_ASL_SUPPLIERS_V

PO_AUTOSOURCE_RULES_ALL

PO_AUTOSOURCE_VENDORS_ALL

PO_BUYER_NAME_NUM_V

PO_BY_BUYER_V

PO_CONTRACTS_VAL_V

PO_DESTINATION_TYPES_VAL_V

PO_DISTRIBUTIONS_AP2_V



PO_DISTRIBUTIONS_AP_V

PO_DISTRIBUTIONS_PRINT

PO_DOCUMENT_HEADERS_VIEW

PO_DOCUMENT_TYPES_ALL_VL

PO_DOCUMENT_TYPES_B

PO_DOCUMENT_TYPES_TL

PO_DOCUMENT_TYPES_VL

PO_EMPLOYEE_HIERARCHIES_ALL_V

PO_FOB_VAL_V

PO_FREIGHT_TERMS_VAL_V

PO_HAZARD_CLASSES_ALL_V

PO_HAZARD_CLASSES_VL

PO_HEADERS_AP_V

PO_HEADERS_CHANGE_PRINT

PO_HEADERS_PRINT

PO_HEADERS_VIEW

PO_IMPORT_SOURCES_V

PO_INSPECTION_RESULTS_VAL_V

PO_ITEM_SOURCES

PO_LINES_AP_V

PO_LINES_CHANGE_PRINT

PO_LINES_PRINT

PO_LINE_LOCATIONS_AP_V

PO_LINE_LOCATIONS_CHANGE_PRINT

PO_LINE_LOCATIONS_PRINT

PO_LINE_LOCATIONS_RFQQT_V

PO_LINE_TYPES_VL

PO_LOCATIONS_VAL_V

PO_LOOKUP_CODES

PO_LOOKUP_CODES_PAY_GROUP_AP_V



PO_LOOKUP_TYPES

PO_OWNED_LINES

PO_OWNED_REQUISITION_LINES

PO_OWNED_SHIPMENTS

PO_POSITIONS_VAL_V

PO_PO_SUPPLY_VIEW

PO_PURCHASE_ORDER_V

PO_QUALITY_CODES_VAL_V

PO_RCV_CONTROL_LEVEL_V

PO_RCV_SUPPLY_VIEW

PO_RELEASES_VAL_V

PO_REL_LINE_V

PO_REL_TAX_LINES_SUMMARY_V

PO_REQS_IN_TRANSIT_ALL_V

PO_REQUESTOR_LOCATIONS_V

PO_REQ_DIST_INTERFACE

PO_REQ_SUPPLY_VIEW

PO_REQ_TAX_LINES_SUMMARY_V

PO_RFQQT_DOCUMENT_STATUS_V

PO_RFQS_FOR_QUOTE_ALL_V

PO_RFQS_VAL_V

PO_RFQ_HEADERS_PRINT

PO_RFQ_LINES_PRINT

PO_RFQ_LINE_LOCATIONS_PRINT

PO_SHIPMENTS_AP_V

PO_SHIPMENTS_VAL_V

PO_SHIP_RCV_SUPPLY_VIEW

PO_SHIP_SUPPLY_VIEW

PO_SOURCE_VENDORS_V

PO_SUPPLIER_CONTACTS_VAL_V



PO_SUPPLIER_OPEN_POS_V

PO_SUPPLIER_SITES_ALL_V

PO_SUPPLIER_SITES_VAL_V

PO_TAX_CODES_SUMMARY_V

PO_TAX_DISTRIBUTIONS_DETAIL_V

PO_TAX_HEADERS_DETAIL_V

PO_TAX_LINES_DETAIL_V

PO_TAX_LINES_SUMMARY_V

PO_TAX_SHIPMENTS_DETAIL_V

PO_TRANSACTION_NATURE_ALL_V

PO_UNITS_OF_MEASURE_VAL_V

PO_UN_NUMBERS_VL

PO_VENDORS_VIEW

PO_VENDOR_LIST_ENTRIES_V

RCV_AEL_GL_V

RCV_AEL_SL_V

RCV_DISTRIBUTIONS_PRINT

RCV_PO_ITEMS_V

RCV_RECEIPTS_PRINT

RCV_RECEIVERS_UNORDERED_V

RCV_RECEIVING_ACCT_DISTR_V

RCV_RECEIVING_VALUE_VIEW



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

Oracle Purchasing uses the following Single Organization views:

FINANCIALS_SYSTEM_PARAMETERS

PO_ACCRUAL_ACCOUNTS_TEMP

PO_ACCRUAL_RECONCILE_TEMP

PO_ACCRUAL_WRITE_OFFS

PO_AUTOSOURCE_DOCUMENTS

PO_DISTRIBUTIONS

PO_DISTRIBUTIONS_ARCHIVE

PO_EMPLOYEE_HIERARCHIES

PO_HEADERS

PO_HEADERS_ARCHIVE

PO_HISTORY_POS



PO_HISTORY_REQUISITIONS

PO_ITEM_HISTORY_V

PO_LINES

PO_LINES_ARCHIVE

PO_LINES_SUPPLIER_ITEMS_V

PO_LINE_LOCATIONS

PO_LINE_LOCATIONS_ARCHIVE

PO_NOTIFICATIONS

PO_POSITION_CONTROLS

PO_QUOTATION_APPROVALS

PO_RELEASES

PO_RELEASES_ARCHIVE

PO_REQEXPRESS_HEADERS

PO_REQEXPRESS_LINES

PO_REQUISITIONS_INTERFACE

PO_REQUISITION_HEADERS

PO_REQUISITION_LINES

PO_REQ_DISTRIBUTIONS

PO_SYSTEM_PARAMETERS

PO_VENDOR_SITES



Multiple Reporting Currencies View List

This section lists each view that Oracle Purchasing uses to support theMultiple Reporting Currencies (MRC) feature. These views, undercertain circumstances, replace the corresponding transaction tables butretrieve currencysensitive information expressed in the reportingcurrency rather than in the functional currency for the associated set ofbooks. That is, when you access a transaction table from theAPPS_MRC schema, an MRC synonym redirects your query to thecorresponding MRC view; this MRC view ensures you retrieve currencyamounts expressed in the currency associated with the reporting set ofbooks, as indicated 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

Oracle Purchasing uses the following Multiple Reporting Currenciesviews:

PO_DISTRIBUTIONS_ALL_MRC_V

PO_DISTRIBUTIONS_MRC_V

PO_HEADERS_ALL_MRC_V

PO_HEADERS_MRC_V

PO_REQUISITION_LINES_ALL_MRC_V

PO_REQUISITION_LINES_MRC_V

RCV_AEL_SL_MRC_V

RCV_REC_SUB_LEDGER_MRC_V

RCV_SHIPMENT_HEADERS_MRC_V

RCV_SHIPMENT_LINES_MRC_V

RCV_TRANSACTIONS_MRC_V



Module List

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

Forms

INVIDITM Organization Items

POXACCWO Accrual WriteOffs

POXBWVRP AutoCreate Purchase Orders

POXCPDOC Copy Documents

POXDOAPP Approval Submission Call Form

POXDOCON Control Documents

POXDOFDO Forward Documents

POXDOPRE Purchase Order Preferences

POXITLPI View Price History

POXITPHI View Purchase History

POXLCDLA Define Location Associations

POXPCATN Exceeded Price Tolerance

POXPODMC Define MassCancel

POXPOEAC Enter Acceptances

POXPOEPO Enter Purchase Orders

POXPOERL Enter Releases

POXPORMC Run MassCancel

POXPOVCT Notification Controls

POXPOVPO View Purchase Orders

POXQUEMQ Enter Supplier Lists

POXRQARQ Assign Requisitions

POXRQERQ Enter Requisitions

POXRQTMP Enter ReqExpress Template

POXRQVRQ View Requisitions

POXSCERQ Enter RFQs



POXSCSAQ Approve Quotations By Item

POXSCSIC Sourced Items

POXSTASL Setup Approved Supplier List Statuses

POXSTCPP Control Purchasing Periods

POXSTDBY Define Buyers

POXSTDCG Define Control Groups

POXSTDDT Define Document Controls

POXSTDHC Define Hazard Classes

POXSTDLC Enter Lookup Codes

POXSTDLT Define Line Types

POXSTDPC Define Position Controls

POXSTDPO Define Purchasing Options

POXSTDQC Define Quality Inspection Codes

POXSTDUN Define UN Numbers

POXSVASL Summary of Approved Supplier List

POXTAXCT View Tax Summary

POXTAXDT View Tax Detail

RCVRCERC Enter Receipts

RCVRCMUR Match Unordered Receipts

RCVRCVRC View Shipments/View Receiving Transactions

RCVSHESH Maintain Shipments

RCVSTDRO Define Receiving Options

RCVTXECO Enter Corrections

RCVTXERT Enter Receiving Transactions

RCVTXVTX View Receiving Transaction Status

Reports

POXACRCR Accrual Rebuild Reconciliation Report

POXACREC Accrual Reconciliation Report

POXACTPO Purchasing Activity Register



POXACWRO Accrual WriteOff Report

POXAGLST Buyer Listing

POXBLREL Purchase Order and Releases Detail Report

POXCHORD Printed Change Orders Report

POXCHORL Printed Change Orders Report (Landscape)

POXCONST Contract Status Report

POXDETIT Item Detail Listing

POXDLPDT Receipt Traveler

POXFIPOL Financials/Purchasing Optio

Ptop Technical Documentaion

Documents

Transcript of Ptop Technical Documentaion