Professional Documents
Culture Documents
1) Create Requisition:
Requisition is nothing but a formal request to buy something (like Inventory material, office
supplies etc) needed for the enterprise. Only an employee can create one. There are two
types of requisitions:
Internal Requisition: Internal requisitions provide the mechanism for requesting and
transferring material from one inventory to other inventory.
Purchase requisition: Unlike Internal requisitions, Purchase requisitions are used for
requesting material from suppliers.
Underlying Tables:
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.
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.
Ketul Patel
Ketul Patel
Ketul Patel
3) Create Receipt:
A receipt is a written acknowledgment that a specified article or sum of money has been
received. A receipt records the purchase of goods or service. It is not the same as an
invoice.
Create a receipt to receive the items in the Purchase Order.
Receipt Tables are:
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_HEADERS stores common information about the source of your receipts
or expected receipts. You group your receipts by the source type and the source of the
receipt. Oracle Purchasing does not allow you to group receipts from different sources under
one receipt header.
There are two receipt source types, Supplier and Internal Order, that you need to use when
receiving against different source document types. You use a receipt source type of
Supplier when receiving items that you ordered from an external supplier using a purchase
order. When you receive items that are part of an interorganization transfer, or when
receiving items that you request from your inventory using an internal requisition, the receipt
type would be Internal Order. The Internal Order receipt source type populates the
ORGANIZATION_ID column.
Oracle Purchasing creates a receipt header when you are entering your receipts or when
you perform interorganization transfers using Oracle Inventory. When Oracle Inventory
creates a receipt header for an in-transit shipment, the receipt number is not populated until
you receive the shipment.
RCV_SHIPMENT_LINES (Lines Table has PO_HEADER_ID)
RCV_SHIPMENT_LINES stores information about items that have been shipped and/or
received from a specific receipt source. RCV_SHIPMENT_LINES also stores information
about the default destination for in-transit shipments.
Ketul Patel
Ketul Patel
Payment Tables:
AP_INVOICE_PAYMENTS_ALL
AP_INVOICE_PAYMENTS_ALL contains records of invoice payments that you made to
suppliers. There is one row for each payment you make for each invoice. There is one
payment and one invoice for each payment in this table. Your Oracle Payables application
updates this table when you confirm an automatic payment batch, enter a manual payment,
or process a Quick payment. When you void a payment, your Oracle Payables application
inserts an additional payment line that is the negative of the original payment line.
For manual payments and Quick payments, this table corresponds to the Select Invoices
window in the Payment workbench.
AP_PAYMENT_SCHEDULES_ALL
AP_PAYMENT_SCHEDULES_ALL contains information about scheduled payments for an
invoice. You need one row for each time you intend to make a payment on an invoice. Your
Oracle Payables application uses this information to determine when to make payments on
an invoice and how much to pay in an automatic payment batch.
Values for HOLD_FLAG may be Y to place a hold on the scheduled payment, or N not to
do so. Values for PAYMENT_STATUS_FLAG may be Y for fully paid payment schedules,
N for unpaid scheduled payments, or P for partially paid scheduled payments. For
converted records, enter a value for AMOUNT_REMAINING.
This table corresponds to the Scheduled Payments window.
AP_CHECKS_ALL
AP_CHECKS_ALL stores information about payments issued to suppliers or refunds received
from suppliers. You need one row for each payment you issue to a supplier or refund received
from a supplier. Your Oracle Payables application uses this information to record payments you
make to suppliers or refunds you receive from suppliers.
AP_CHECK_FORMATS
AP_BANK_ACCOUNTS_ALL
AP_BANK_BRANCHES
AP_TERMS
Ketul Patel