PO_REQ_DISTRIBUTIONS_ALL

R12
Click on Distributions to View the charge Account.
Save and Submit for Approval
Check the status of the Requisition.
Query for the Requisition Number and click Find.
Here for our example purpose, I kept the submitted and approved person has same and hence it
shows the status as approved.
To see the approval status, please follow the below navigation.

Note:
1. Without changing Responsibility and without closing windows buyers will now be able
to view consolidated requisition demand spanning multiple operating units.
2. The operating units that buyers can transact on behalf of will be controlled by the
security profile associated with their responsibilities.
3. Operating Unit extra field in the R12 forms due to MOAC.
4. Base tables are same as 11i but more than 15 extra columns in R12 for the table
PO_REQUISTION_HEADERS_ALL, PO_REQUISTION_LINES_ALL
and PO_REQ_DISTRIBUTIONS_ALL for tax etc.
The Supplier Details in R12 : Many changes were happened in supplier details in R12.
Suppliers into TCA - Architecture in R12 :

Prior to R12 the supplier’s information is stored in PO_VENDORS. From R12 onwards supplier has
been moved in to the TCA Data Model.

HZ_PARTIES : This is the master table for suppliers.

HZ_PARTY_USG_ASSIGNMENTS : This table stores the Party Usages, for example, for the
suppliers it captures the fact that the given party_id is of type
SUPPLIER. HZ_ORGANIZATION_PROFILES : This table captures additional Supplier information,
for example, credit scoring details of Supplier or the Number of Employees working in Supplier
Organization.
IBY_EXTERNAL_PAYEES_ALL : It captures payment related details of the supplier. Like how
should the supplier's remittance advice must be sent, default Payment method Code for this supplier,
Who bears the bank charges when lets say SWIFT payment is made?

Note : This information can be set up at the supplier level or supplier site level.

AP_SUPPLIERS : This is another master table that replaces the PO_VENDORS table. It stores the
supplier specific attributes.
POS_SUPPLIER_MAPPINGS : This table holds the mapping between the
AP_SUPPLIERS.VENDOR_ID and HZ_PARTIES.PARTY_ID.
This is useful in cases whereby two vendors effectively belong the same HZ_Party Record.
ZX_PARTY_TAX_PROFILE : The taxation related details like Tax Codes, and Tax Accounts etc have
been moved from AP into ZX.
ZX is the name of a new Application "E-Business Tax".
PO_VENDORS : PO_VENDORS is a view in R12, that joins AP_SUPPLIERS & HZ_PARTIES.
Similarly, PO_VENDOR_SITES and PO_VENDOR_SITES_ALL are also views based upon
AP_SUPPLIER_SITES_ALL.

2) Create Purchase Order

11i

There are 4 types of Purchase Orders:

1. Standard PO: A Standard PO is created for onetime purchase of various items

2. Planned PO: A Planned PO 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.
3. Blanket agreement: A Blanket PO is created 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 know the detail of your delivery
schedules.
4. Contract agreement: Contract purchase agreements are created with your suppliers to agree
on specific terms and conditions without indicating the goods and services that you will be purchasing
Navigation for creating a standard PO:
Purchase Orders > Purchase Orders
Choose type as Standard Purchase Order. Enter the Supplier, Buyer. In the Lines tab, specify the
line number, line type, Item, quantity, price etc.

Click Terms to enter terms, conditions, and control information for purchase orders.

Click Currency button to enter and change currency information for purchase orders, RFQs, and
quotations.

Click Shipments button to enter multiple shipments for standard and planned purchase order lines
Purchase order shipment specifies the quantity, shipto organization and location, date you want your
supplier to deliver the items on a purchase order line, and country of origin for the items. When you
save, Purchasing creates distributions depending on the default information available.

To enter more shipment information, select the More tab.

1. Enter the Receipt Close Tolerance percent, Invoice Close Tolerance percent to set the receiving
and
invoice close point.
2. Select one of the following options for Match Approval Level:
TwoWay: Purchase order and invoice quantities must match within tolerance before the
corresponding
Invoice can be paid.
ThreeWay: Purchase order, receipt, and invoice quantities must match within tolerance before the
Corresponding invoice can be paid.

FourWay: Purchase order, receipt, accepted, and invoice quantities must match within tolerance
before the corresponding invoice can be paid.

1. Select an Invoice Match Option:

Purchase Order: Payables must match the invoice to the purchase order.
Receipt: Payables must match the invoice to the receipt.
Save the work.

Click the Receiving Controls button to enter receiving control information for purchase orders.

-Enter the maximum acceptable number of Days Early and Days Late for receipts.

-Enter the Action for receipt date control.

-Enter the maximum acceptable over receipt Tolerance percent (receipts that exceed the
quantity received tolerance).

-Enter the Action for Overreceipt Quantity.

-Select Allow Substitute Receipts to indicate that receivers can receive substitute items in place
of ordered items.

-Enter the default Receipt Routing that you assign goods: Direct Delivery, Inspection Required,
or Standard Receipt.

-Enter the Enforce Ship To location option to determine whether the receiving location must be
the same as the shipto location.

Save the work.

Click Distributions button to enter distributions for the shipments.

Select more tab to enter more details and the requisition number (optional).
Save the work.

Click on the Approve button to initiate the Approval process.

Underlying Tables:

PO_HEADERS_ALL
PO_LINES_ALL