ORACLE.APPS.R12.

PURCHASING

Course Outlines: CLASS-I-27-JUL-2017

1. PO Matching Rules.
2. Internal Requisition to Internal Sales Order.
3. Position based Approval Hierarchy.
4. Types of Purchase order
5. Purchasing Options.
6. Document type.
7. Blanket Purchase agreement.
8. Purchasing Key tables and their functionalities.

-------------------------------------------------------------------------------------------------------------------------

PO Matching Rules

PO Matching Rules will be set at Purchase Order (PO) level. PO Matching

Rules are used to validate AP Invoices before making the payment to
suppliers.

PO Matching rules can be set at five different levels to default them on to

purchase order. Once matching rule is defaulted on to PO we have the
option to override them as needed.

In the list below, a setting at any level will override the settings above it.
1. Oracle Purchasing Options
a. Navigate to: Setup > Organizations > Purchasing Options
b. Select Default Alternative Region
2. Supplier Information
a. Navigate to: Supply Base > Suppliers
b. Query on specific supplier
c. Click on Open
d. Select Receiving Alternative Region
3. Line Types
a. Navigate to: Setup > Purchasing > Line Types
b. In the Receipt Required field: Yes = 3-way, No = 2-way
4. Items
a. Navigate to: Items > Master Items
b. Query on specific item
c. Select Purchasing Alternative Region
d. In the Invoice Matching section: Yes = 3-way, No = 2-way
5. Purchase Order Shipments
a. Navigate to: Purchase Orders > Purchase Orders
b. Enter (header and) line information
c. Click on Shipments button
d. Select More Alternative Region
In general Oracle ERP doesnt let you make payments without validating
the invoice. (There is a workaround to turn this off). Usually no
organization want to turn-off matching rules because they want to ensure
the payment is going out for the right reason.

2-Way:
In 2- way, we will compare two documents PO and Invoice.

Invoice Price < = Purchase Order Price

Invoice Quantity < = Purchase Order Quantity

3-Way:
In 3-Way you will compare 3 documents i.e PO+reciept+Invoice.

3-way matching verifies that the receipt and invoice information match
with the quantity tolerances defined:

Invoice Price < = Purchase Order Price

Invoice Quantity < = Purchase Order Quantity

Invoice Quantity < = Received Quantity

4-Way:
In 4-Way you will compare 4 documents i.e
PO+Receipt+Invoice+Inspection.
4-way matching verifies that acceptance documents and invoice
information match within the quantity tolerances defined
Invoice Price < = Purchase Order Price

Invoice Quantity < = Purchase Order Quantity

Invoice Quantity < = Received Quantity

Invoice Quantity < = Accepted Quantity

Internal Requisition to Internal Sales Order (IR to ISO)

Companies might have to transfer material from one warehouse
(inventory organization) to other warehouse depending on the current on-
hand stock and demand at each location. Oracle ERP provides a couple of
ways to achieve this requirement.

1) Internal requisition to internal sales order

2) Inter Organization Transfer ( I have covered this in another article)
Normally Internal requisition will be created by the destination
organization who wishes to receive the material from source organization.
Now a days companies being so global we may not have people assigned
dedicatedly to work on individual warehouse so internal requisitions can
be created by a planner (employee / person) who is responsible for
planning on-hand quantities at different warehouses.

First, Start with creating internal requisition. Make sure requisition type is
selected as Internal requisition.

Source Organization is the warehouse where we have ample inventory

stock and ready to give.

Destination organization is the requesting warehouse where material is

required.
 Go for Approve here

Submit requisition for approval.

If it has a approval gr setup then we need to forward it

Make sure requisition is approved.

Go to View > Requests > Submit a New Request

Submit Create Internal Orders concurrent program for the operating
unit in which our requisition is created.
Switch responsibility to Order Management responsibility.

View > Requests > Submit a New Request

Run Order Import concurrent program with Order source as internal and
order reference as requisition number.
Parameters needed as it is

Make sure Order Import concurrent program is completed.

Navigate to Order Organizer and search input Order Source as Internal

and Order Source reference is your requisition number.
Order source reference is not PO Number here

Click Find to get your sales order.

Observer that the customer that is populated will be your internal
customer
If you would like confirm the Sales order link with requisition you can
navigate to Others tab and at the bottom you can see the requisition
number in Order source reference column.

Position Based Approval Hierarchy in Purchasing

Approval hierarchies let you automatically route documents for approval.

There are two kinds of approval hierarchies in Purchasing: position
hierarchy and employee/supervisor relationships.

If an employee/supervisor relationship is used, the approval routing

structures are defined as you enter employees using the Enter Person
window. In this case, positions are not required to be setup.

If you choose to use position hierarchies, you must set up positions. Even
though the position hierarchies require more initial effort to set up, they
are easy to maintain and allow you to define approval routing structures
that remain stable regardless of how frequently individual employees
leave your organization or relocate within it.
Setups required for Position hierarchy in detail:
Say we want to implement the below position hierarchy for the
Requisition Document approval routing in Purchasing (Each rectangle
represents a Position), below are the setups required:

1) Enable the check box Use Approval Hierarchies

Navigation: Purchasing Responsibility > Setup > Organizations >

Financial Options

Click Human Resources tab. to use positions and position hierarchies to

determine approval paths for your documents within Purchasing. (Disable
this option if you want approval paths based on the supervisor structure)

2) Create Positions S20, MGR, DIR based on the above hierarchy in HR.
Navigation: Human Resources responsibility > Work Structures > Position
> Description

Click on New Button and enter the required fields.

Similarly create MGR and DIR positions.

3) Assign the positions created to the Employees who fall under the
portfolio. Each position can be assigned to more than one employee.
Navigation: Human Resources responsibility > People > Enter and
Maintain

Query for the Employee Name. Click on Find Button.

Click on Assignment button

Enter the desired value in the Position field.

Save the work.

4) Create the Position hierarchy

Navigation: Human Resources Responsibility > Work Structures > Position

> Hierarchy

Enter Hierarchy Name Save

Enter the From Date Save
Click in the POSITION field and query the position you would like to
be your Top position. In our example you would query for DIR.
After the Position is selected Press the Down Key. Your cursor will
now be in the subordinate region, choose the position MGR to go under
DIR position.
Again hit the Blue Down Arrow. You will now see the Subordinate
position shift to where the Top Position was located. Add a new
Position S20.
Save the work.
5) Create Approval groups for each Position.

Approval Groups window lets you define the Approval limits for a
particular group which will be assigned to a position.

As per our example, we will create three Approval Groups S20, MGR, DIR
and define the limits.

Navigation: Purchasing Responsibility > Setup > Approvals > Approval

Groups

Enter the Name of the approval group

Select Enabled to permit the approval group to be assigned to a position

in the Approval Assignments window.

Choose one of the following Objects:

Account Range (Required) You enter the accounting flexfields for the
Low and High

Values.

Document Total (Required) The document total refers to the monetary

limit on an individual document.
Item Category Range You enter the purchasing category flexfields for
the Low and High Values.

Item Range For this option, you enter the item flexfields for the Low
and High Values. Location The location refers to the deliver-to location
on a requisition as well as the ship-to location on purchase orders and
releases.

Select the rule Type: Include or Exclude indicates whether to allow

objects that fall within the selected range.

Enter the Amount Limit. This is the maximum amount that a control group
can authorize for a particular object range.

Enter the Low Value. This is the lowest flexfield (accounting, purchasing
category, or item) in the range pertinent to this rule. When the object is
Location, enter the location. You cannot enter this field when the object is
Document Total.

Enter the High Value. This is the highest flexfield (accounting, purchasing
category, or item) in the range pertinent to this rule. You cannot enter
this field when the object is Location or Document Total.

Save your work.

6) Assign the Approval groups to the Position

Navigation: Purchasing Responsibility > Setup > Approvals > Approval

Assignments

Query the Position for which you want to assign the Approval group.

Select the Document type you want to assign to this position or job (As
per our example we will choose Approve Purchase Requisition)

Enter the approval group that you want to assign to the selected position
or job. The list of values includes only enabled approval groups with at
least one approval rule. (Assign it to the approval group DIR as per our
example)

Enter the Start Date and End Date for the assignment.

Save your work.

Similarly assign the Approval groups MGR and S20 to the positions MGR
and S20 respectively for the document type Approve Purchase
Requisition.

7) Assign the Position hierarchy created to the desired Document Type.

Document Types window can be used to define access, security, and

control specifications for all Purchasing documents.

Navigation: Purchasing Responsibility > Setup > Purchasing > Document

Types

Find Document Types window appears. Select the document type

Requisition .
 Enter your Document Name for the document. The description must
be unique for the given document type.
Check Owner Can Approve to indicate that document preparers can
approve their own documents.
Check Approver Can Modify to indicate that document approvers
can modify documents. Check Can Change Forward-To to indicate that
users can change the person the document is forwarded to.
Check Can Change Forward-From to indicate that users can change
the name of the document creator. This field is applicable only when
the Document Type is Requisition.
Check Can Change Approval Hierarchy to indicate that approvers
can change the approval hierarchy in the Approve Documents window.
This field is not applicable when the Document Type is Quotation
or RFQ.
Check Disable to disable a document type.
For Purchase requisitions only, select Use Contract Agreements for
Auto Sourcing to require the requisition creation autosourcing logic to
include approved contract purchase agreements.
Include Non-Catalog Requests For Oracle iProcurement only, this
checkbox is used in conjunction with the Use Contract Agreements for
Auto Sourcing. Select this checkbox to enable the use of contract
purchase agreements when autosourcing non-catalog requisitions.
Choose one of the following options:
Hierarchy Only the document owner and users above the owner in
the defined purchasing security hierarchy may access these
documents.

Private Only the document owner may access these documents.

Public Any user may access these documents.

Purchasing Only the document owner and users listed as buyers in the
Define Buyers window may access these documents.

Choose one of the following Access Level options:

Full Users can view, modify, cancel, and final close documents.

Modify Users can only view and modify documents.

View Only Users can only view documents.

Choose one of the following options:

Direct The default approver is the first person in the preparers approval
path that has sufficient approval authority.

Hierarchy The default approver is the next person in the preparers

approval path regardless of authority. (Each person in the approval path
must take approval action until the person with sufficient approval
authority is reached.)

Choose the Position Hierarchy that we have created previously

Purchasing Approval Test as the Default Hierarchy field.
8) Run the Fill Employee Hierarchy Request

Navigation: Purchasing Responsibility > View Requests

Click on Submit a New Request button and select Single Request.

Approval routing explanation based on the example hierarchy:

1. Say the S20 position creates a Purchase Order for $4,000 and submits
for Approval.

2. The system will look at which Approval Hierarchy to be used from the
Document

Types window. Since in our example Owner Can Approve is not

checked, it will try

to determine what the Approval group is for the position MGR as MGR is
the next Position in our hierarchy.

3. Once the Approval Group is located, the rules will then be considered
one at a time, from first to last.
4. If all rules are satisfied, the Purchase Order will be forwarded to the
Manager for Approval.

If a rule cannot be satisfied, the Purchase Order will be forwarded to the

next position (DIR) in the Hierarchy. Whoever is assigned to that position
will then need to take action on the Purchase Order.

In release 11.0, when attempting to Approve a Purchase Order, if the

system doesnt find any of the positions defined in the hierarchy to have
the authority to Approve, then the Document will remain Incomplete
without any warnings instead of In Process.

Purchase Order Types

Purchasing provides the following purchase order types: Standard

Purchase Order, Planned Purchase Order, Blanket Purchase Agreement,
and Contract Purchase Agreement. You can use the Document Name field
in the Document Types window to change the names of these documents.
For example, if you enter Regular Purchase Order in the Document Name
field for the Standard Purchase Order type, your choices in the Type field
in the Purchase Orders window will be Regular Purchase Order, Planned
Purchase Order, Blanket Purchase Agreement, and Contract Purchase
Agreement.

Standard Purchase Orders

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

Blanket Purchase Agreements

You create blanket purchase agreements when you know the detail of the
goods or services you plan to buy from a specific supplier in a period, but
you do not yet know the detail of your delivery schedules. You can use
blanket purchase agreements to specify negotiated prices for your items
before actually purchasing them.

Blanket Releases
You can issue a blanket release against a blanket purchase agreement to
place the actual order (as long as the release is within the blanket
agreement effectivity dates). If you use encumbrance accounting, you can
encumber each release.

Contract Purchase Agreements

You create contract purchase agreements with your suppliers to agree on
specific terms and conditions without indicating the goods and services
that you will be purchasing. You can later issue standard purchase orders
referencing your contracts, and you can encumber these purchase orders
if you use encumbrance accounting.

Planned Purchase Orders

A planned purchase order is a long-term agreement committing to buy
items or services from a single source. You must specify tentative delivery
schedules and all details for goods or services that you want to buy,
including charge account, quantities, and estimated cost.

Scheduled Releases
You can issue scheduled releases against a planned purchase order to
place the actual orders. If you use encumbrance accounting, you can use
the planned purchase order to reserve funds for long term agreements.
You can also change the accounting distributions on each release and the
system will reverse the encumbrance for the planned purchase order and
create a new encumbrance for the release.

Purchase Order Types Summary

Standard Planned Blanket Purchase Contract Purchase

Purchase Order Purchase Order Agreement Agreement

Terms and Yes Yes Yes Yes

Conditions Known
Goods or Services Yes Yes Yes No
Known
Pricing Known Yes Yes Maybe No
Quantity Known Yes Yes No No
Account Yes Yes No No
Distributions Known
Delivery Schedule Yes Maybe No No
Known
Can Be Encumbered Yes Yes No No
Can Encumber N/A Yes Yes N/A
Releases

Oracle Apps R12 Purchasing Financials Options

Financials Options:
Use the Financials Options window to define the options and defaults that
you use for your Oracle Financial Application(s). Values you enter in this
window are shared by Oracle Payables, Oracle Purchasing, and Oracle
Assets. You can define defaults this window to simplify supplier entry,
requisition entry, purchase order entry, invoice entry, and automatic
payments. Depending on your application, you may not be required to
enter all fields.

Although you only need to define these options and defaults once, you
can update them at any time. If you change an option and it is used as a
default value elsewhere in the system, it will only be used as default for
subsequent transactions. For example, if you change the Payment Terms
for Immediate to Net 30, Net 30 will be used as default for any new
suppliers you enter, but the change will not affect the payment Terms of
existing suppliers.
N: Setup> Organizations > Financial Options
Click on Find
Accounting Financials Options:

Future Periods: Payable displays the number of future periods you use in
your set of books. Payables use this value to limit the number of future
periods you can maintain in the control Payables Periods window. You can
enter invoices in future periods.
GL Accounts
Liability:
Payables assign this account as the default Liability Account for all new
suppliers you enter. You can override this value during supplier entry. If
you use Accrual Basis accounting, then the Liability Account for any
invoice determines the liability account(s) charged when you create
accounting entries for invoices.
Prepayment:
The Prepayment account and description for a supplier sites invoices. The
financials Option value defaults to new suppliers and the supplier value
defaults to new supplier sites.
Future Dated Payment: If you use future dated payments, then enter a
value for Future Dated Payment account. This value defaults to all new
suppliers and new bank accounts. The supplier value defaults to all new
supplier sites. The bank account value defaults to new payment
documents.
When Payables accounts for future date payments, it uses the Future
Dated Payment Account from either the supplier site or the payment
document, depending on the Option you select in the Payment Accounting
region of the Payables Options window.
If you relive liability payment time, this should be an asset account. If you
relieve liability at future date payment maturity, then this should be a
liability account.
Discount Taken:
If you choose to distribute your discounts to the system Discount Taken
Account, Payables uses this account to record the discounts you take on
payments. Use the Payables Options window to select your method for
distributing discounts for your invoices.
PO Rate Variance Gain/Loss: Payables uses these accounts to record the
exchange rate variance gains/losses for your inventory items. The
variance is calculated between the invoice and either the purchase order
or the receipt, depending on how you matched the invoice. These
accounts are not used to record variances for your expense items. Any
exchange rate variance for your expense items is recorded to the charge
account of the purchase order. Payables calculate these accounts during
Payables Invoice Validation.
Expenses Clearing:
This account is required when you use the Company Pay payment option
of Oracle Internet Expenses. Payables uses this as a temporary account to
record credit card transactions activity. Payables debit this account when
you create an invoice to pay a credit card issuer for credit card
transactions. Payables credit s this account with offsets to the original
debits entries when you submit Expense Report Import for an employee
expense report entered in Internet Expenses that has credit card
transactions on it.
Miscellaneous:
Used only when importing invoices submitted via iSupplier Portal or XML
Gateway.
If you enter a value here then the system uses this account for all
Miscellaneous charges on invoices your suppliers enter in iSupplier Portal.
If you do not enter a value here then the system prorates miscellaneous
charges across Item lines on iSupplier Portal invoices.
The system also uses this value for any miscellaneous charges your
suppliers send in XML invoices. If you do not enter a value here then
import prorates miscellaneous charges across Item lines for XML invoices.
Supplier Purchasing Financials Options:
The options you define in this region, except for Inventory Organization,
are used s default values for the Purchasing region of the supplier
window. The supplier values default to new supplier sites for the supplier,
which default to new purchasing documents for the supplier site.
Note: If you use the Multiple Organizations Support feature, values you
enter in this window will default to both the supplier and Supplier Site.
You can override defaulted values during entry of the supplier, supplier
site, and purchasing documents.

Ship-To / Bill-To Location:

The name of the ship-to/Bill-to Location for the system default value. If
the name you want does not appear in the list of values, use the location
window to enter a new location.
Inventory Organization:
You need to choose an inventory organization if you use Purchasing. You
can associate each of your Purchasing operating units with one inventory
item master organization. When you associate your purchasing unit with
an inventory organization, items you define in this organization become
available in Purchasing. You can only choose an inventory organization
that uses that same set of books as your purchasing Operating unit. Do
not change the inventory organization after you have already assigned
one to Purchasing.

Encumbrance Financials Options:

To use encumbrance accounting or budgetary control, you must install
Payables, purchasing, and general Ledge. Use this region to enable
encumbrance accounting and to specify the default encumbrance types
Payables assigns to your invoices, and Purchasing assigns to your
requisitions and purchase orders.
If you enable encumbrance accounting or budgetary control, Purchasing
creates encumbrances when you reserve funds for a requisition or
purchase order. If you use the perpetual accrual method in Purchasing,
Purchasing reverses purchase order encumbrances when you inspect,
accept and deliver the units. If you are using the periodic accrual method
in Purchasing, Payables reverses the purchase order encumbrances when
you create accounting entries for invoices.
Payables creates encumbrances when there is a variance between a
matched invoice and the purchase order to which it is matched, and when
the invoice encumbrance type is different from the Purchasing
encumbrance type.
Oracle Financials provides two predefined encumbrance types that you
can use to identify requisition, purchase order, and invoice
encumbrances: Commitment and Obligation. You can define additional
encumbrance types in Order General Ledger in the Encumbrance Types
window.

Use Requisition Encumbrance:

Enable this option to encumber funds for requisitions. If you enable this
option, Purchasing creates journal entries and transfers them to General
Ledger to encumber funds for purchase requisitions.
Encumbrance Type:
If you enable Use Requisition Encumbrance, you must select an
encumbrance type by which you can identify your requisition
encumbrance journal entries. Purchasing assigns this encumbrance type
to the encumbrance journal entries it creates for purchase requisitions.
Reserve at Completion: If you enable Use Requisition Encumbrance,
indicate whether you want requisition preparers to have the option to
reserve funds. If you do not enable option, only requisition approvers will
have the option to reserve funds.
Use PO Encumbrance:
Enable this option to encumber funds for purchase orders, purchase order
receipt matched invoices, and basic invoices (not matched). If you enable
this option, Purchasing encumbers funds for purchase orders and
Payables encumbers funds for variance during Payables Invoice Validation
for purchase order and receipt matched invoices. If you enable this option
and enter a non-purchase order matched invoice, Payables will encumber
funds for it during Payables Invoice Validation. All Payables encumbrances
are reversed when you create accounting entries. If you enable Use
Requisition Encumbrance, you must also enable this option.
PO Encumbrance Type:
If you enable Use Purchase Order Encumbrance, select a purchase order
encumbrance type by which you can identify your purchase order
encumbrance journal entries. Purchasing assigns this encumbrances type
to the encumbrance journal entries it creates for purchase requisitions
and purchase orders.
Invoice Encumbrance Type:
If you use purchase order encumbrance, select an invoice encumbrance
type by which you can identify your invoice encumbrance journal entries.
Payables assign this encumbrance type to the encumbrance journal
entries that it creates. We recommend that you use an encumbrance type
different from the Purchasing encumbrance types so you can identify
invoice encumbrances.
Tax Financials Options:

Member state:
The location of your company or organization. Payables use this country
name to determine if your company or organization is located in a
member state of the European Union (EU).
VAT Registration Number:
The Value-Added Tax (VAT) registration number for your organization.
Your organization is assigned a VAT Registration Number if you register to
pay VAT. The first two characters of a VAT registration number are the
country code for the country or state where the registered company or
organization is located. Payables print this number on the header of the
Intra-EU VAT Audit Trail Report.
Human Resources Financials Options:
Use this region to enter the options and defaults for entering employee
information in the Enter Person window.
 Business Group:
Enter the name of the business group that you want to associate with
Purchasing. If you use Purchasing jointly with Oracle Human Resources,
you must reference the business group that you define in oracle Human
Resource. If you use Purchasing without Human Resources, you can use
the default value. The default for this field is the Human Resources default
of Setup Business Group.
The business group determines which employees you can use in
Purchasing. In Purchasing, you can see only the employees in this
business group.
Expense Reimbursement Address:
Select the default address you want to use payments for employee
expense reports: Home or Office. The system uses this default for each
new employee you enter. You can override this default during employee
entry or expense report entry.
Use Approval Hierarchies:
Enable this option to use positions and position hierarchies to determine
approval paths for your documents within purchasing. Disable this option
of you want approval paths based on the supervisor structure.
Employee Numbering Method:
You can enter your employee numbers manually or let the system
generate sequential employee numbers. The system prevents you from
entering a value in this field if you install Oracle Human Resources or
Oracle Payroll. You can change the numbering method at any time.
o Automatic: The system automatically assigns a unique sequential
number to each employee when you enter a new employee.
o Manual: You enter the employee number when you enter an employee.
o Use National Identifier Number: The system automatically enters the
employees National Identifier Number as the employee number. For
example, a Social Security number for a United States employee.
Attention:
Be Careful if you switch from manual to automatic entry. The employee
number must be unique. When you use manual entry, you can assign any
number and in any order. If you switch to automatic after having entered
employee number manually, the system many try to assign a number
 that you already assigned. If you switch from manual to automatic entry,
make sure the next available number for automatic entry is larger than
the largest number you have already recorded.
Next Automatic Number: If you select the Automatic Employee
Numbering method, enter the starting value you want the system to use
for gathering unique sequential employee numbers, After you enter a
number and save your changes, the system displays the number that it
will assign to the next new employee you enter.

Blanket PO
1.Blancket Purchase agreement is a contractual agreement between a
supplier and a customer whereby the customer agrees to purchase a
certain quantity or dollar volume of goods from the supplier over a
certain length of time
(typically in exchange, the customer gets a price break)

2. The exact dates and quantities of the deliveries need not be specified
when a blanket PO is created.

3. As and when the customer needs the goods, he/she will create a
Release
against the Blanket. The release will specify the delivery date and
quantity for the delivery.

4. A revision number is a mechanism to keep track of changes made to

the
purchase order. It is not the same thing as the release number.

Oracle Purchasing Key Tables and their functionalities

PO_REQUISITION_HEADERS_ALL

PO_REQUISITION_HEADERS_ALL stores information about requisition headers. You need one row
for each requisition header you create. Each row contains the requisition number, preparer, status, and
description. REQUISITION_HEADER_ID is the unique systemgenerated requisition number.
REQUISITION_HEADER_ID is invisible to the user. SEGMENT1 is the number you use to identify the
requisition in forms and reports. Oracle Purchasing generates SEGMENT1 using the
PO_UNIQUE_IDENTIFIER_CONTROL table if you choose to let Oracle Purchasing generate
requisition numbers for you. PO_REQUISITION_HEADERS_ALL is one of three tables storing
requisition information. PO_REQUISITION_HEADERS_ALL corresponds to the Header region of the
Requisitions window.SEGMENT1 provides unique values for each row in the table in addition to
REQUISITION_HEADER_ID.

PO_REQUISITION_LINES_ALL

PO_REQUISITION_LINES stores information about requisition lines. You need one row for each
requisition line you create. Each row contains the line number, item number, item category, item
description, needby date, deliverto location, item quantities, units, prices, requestor, notes, and
suggested supplier information for the requisition line. LINE_LOCATION_ID identifies the purchase
order shipment line on which you placed the requisition. LINE_LOCATION_ID is null if you have not
placed the requisition line on a purchase order. BLANKET_PO_HEADER_ID and
BLANKET_PO_LINE_NUM store the suggested blanket purchase agreement or catalog quotation line
information for the requisition line. PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID
from the original requisition line if you exploded or multisourced this requisition line.
PO_REQUISITION_LINES is one of three tables storing requisition information. This table corresponds
to the Lines region of the Requisitions window.

PO_REQ_DISTRIBUTIONS_ALL

PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated

with each requisition line. Each requisition line must have at least one accounting distribution.
You need one row for each requisition distribution you create. Each row includes the Accounting
Flexfield ID and requisition line quantity. PO_REQ_DISTRIBUTIONS_ALL is one of three
tables storing your requisition information. This table corresponds to the requisition
Distributions window, accessible through the Requisitions window.

PO_DISTRIBUTIONS_ALL

PO_DISTRIBUTIONS_ALL contains accounting distribution information for a purchase order

shipment line. You need one row for each distribution line you attach to a purchase order
shipment. There are four types of documents using distributions in Oracle Purchasing:

Standard Purchase Orders

Planned Purchase Orders
Planned Purchase Order Releases
Blanket Purchase Order Releases

Each row includes the destination type, requestor ID, quantity ordered and deliverto
location for the distribution. Oracle Purchasing uses this information to record accounting
and requisition information for purchase orders and releases. PO_DISTRIBUTIONS_ALL is
one of five tables storing purchase order and release information. Some columns in
PO_DISTRIBUTIONS_ALL contain information only if certain conditions exist:

If you autocreate this accounting distribution from a requisition,

REQ_DISTRIBUTION_ID corresponds to the ID of the requisition distribution you copy on
the purchase order.
If you use a foreign currency on your purchase order,Oracle Purchasing stores currency
conversion information in RATE and RATE_DATE.
If you use encumbrance, GL_ENCUMBERED_DATE and
GL_ENCUMBERED_PERIOD_NAME contain encumbrance information Oracle Purchasing
uses to create journal entries in Oracle General Ledger.
If you do not autocreate the purchase order from online requisitions,
REQ_LINE_REFERENCE_NUM and REQ_HEADER_REFERENCE_NUM contain the
requisition number and requisition line number of the corresponding paper requisition.
These two columns are not foreign keys to another table.
If the distribution corresponds to a blanket purchase order release, PO_RELEASE_ID
identifies this release.
If SOURCE_DISTRIBUTION_ID has a value, the distribution is part of a planned purchase
order release. If you cancel the distribution, Oracle Purchasing automatically updates
QUANTITY_CANCELLED or GL_CANCELLED_DATE. Oracle Purchasing also enters
UNENCUMBERED_AMOUNT if you use encumbrance.

PO_HEADERS_ALL

PO_HEADERS_ALL contains header information for your purchasing documents. You need
one row for each document you create. There are six types of documents that use
PO_HEADERS_ALL:

RFQs
Quotations
Standard purchase orders
Planned purchase orders
Blanket purchase orders
Contracts

Each row contains buyer information, supplier information, brief notes, foreign currency
information, terms and conditions information, and the status of the document.

Oracle Purchasing uses this information to record information that is related to a complete
document. PO_HEADER_ID is the unique systemgenerated primary key and is invisible
to the user. SEGMENT1 is the systemassigned number you use to identify the document
in forms and reports.

Oracle Purchasing generates SEGMENT1 using the

PO_UNIQUE_IDENTIFIER_CONT_ALL table if you choose to let Oracle Purchasing
generate document numbers for you. SEGMENT1 is not unique for the entire table. Different
document types can share the same numbers. You can uniquely identify a row in
PO_HEADERS_ALL using SEGMENT1 and TYPE_LOOKUP_CODE or using
PO_HEADER_ID. If APPROVED_FLAG is Y, the purchase order is approved. If your
document type is a blanket purchase order, contract purchase order,RFQ, or quotation,
Oracle Purchasing uses START_DATE and END_DATE to store the valid date range for the
document.

Oracle Purchasing only uses BLANKET_TOTAL_AMOUNT for blanket purchase orders or

contract purchase orders. If you autocreate a quotation from an RFQ using the Copy
Document window, Oracle Purchasing stores the foreign key to your original RFQ in
FROM_HEADER_ID. Oracle Purchasing also uses FROM_TYPE_LOOKUP_CODE to
indicate that you copied the quotation from an RFQ.

PO_LINES_ALL

PO_LINES_ALL stores current information about each purchase order line. You need one
row for each line you attach to a document. Thereare five document types that use lines:

RFQs
Quotations
Standard purchase orders
Blanket purchase orders
Planned purchase orders

Each row includes the line number, the item number and category, unit, price, tax
information, matching information, and quantity ordered for the line. Oracle Purchasing
uses this information to record and update item and price information for purchase orders,
quotations, and RFQs.

PO_LINE_ID is the unique systemgenerated line number invisible to the user.

LINE_NUM is the number of the line on the purchase order.
Oracle Purchasing uses CONTRACT_NUM to reference a contract purchase order from a
standard purchase order line. Oracle Purchasing uses ALLOW_PRICE_OVERRIDE_FLAG,
COMMITTED_AMOUNT, QUANTITY_COMMITTED, MIN_RELEASE_AMOUNT only for
blanket and planned purchase order lines. The QUANTITY field stores the total quantity of
all purchase ordershipment lines (found in PO_LINE_LOCATIONS_ALL).
PO_VENDORS

PO_VENDORS stores information about your suppliers. You need one row for each supplier
you define. Each row includes the supplier name as well as purchasing, receiving, payment,
accounting, tax, classification, and general information.

Oracle Purchasing uses this information to determine active suppliers. VENDOR_ID is the
unique systemgenerated receipt header number invisible to the user. SEGMENT1 is the
systemgenerated or manually assigned number you use to identify the supplier in forms
and reports.
Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONTROL
table if you choose to let Oracle Purchasing generate supplier numbers for you. This table is
one of three tables that store supplier information. PO_VENDORS corresponds to the
Suppliers window.

PO_VENDOR_SITES_ALL

PO_VENDOR_SITES_ALL stores information about your supplier sites. You need a row for
each supplier site you define. Each row includes the site address, supplier reference,
purchasing, payment, bank, and general information. Oracle Purchasing uses this
information to store supplier address information. This table is one of three tables that store
supplier information. PO_VENDOR_SITES_ALL corresponds to the Sites region of the
Suppliers window.